[colord-kde] [Bug 359677] colord causes crashes in kdeinit5 and kded5 in a Wayland session
https://bugs.kde.org/show_bug.cgi?id=359677 Daniel Nicoletti changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||http://commits.kde.org/colo ||rd-kde/13074b7a1234c9a18275 ||6f2bfba5756bb2283626 --- Comment #3 from Daniel Nicoletti --- Git commit 13074b7a1234c9a182756f2bfba5756bb2283626 by Daniel Nicoletti. Committed on 09/10/2016 at 06:52. Pushed by dantti into branch 'master'. Do not run KDED code on Wayland M +6-0colord-kded/ColorD.cpp http://commits.kde.org/colord-kde/13074b7a1234c9a182756f2bfba5756bb2283626 -- You are receiving this mail because: You are watching all bug changes.
[colord-kde] [Bug 338269] colord-kde does not recognise vendor name
https://bugs.kde.org/show_bug.cgi?id=338269 Daniel Nicoletti changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|UNCONFIRMED |NEEDSINFO --- Comment #1 from Daniel Nicoletti --- Please attach your EDID here, thanks -- You are receiving this mail because: You are watching all bug changes.
[colord-kde] [Bug 332737] EDID strings can be up to 13 bytes
https://bugs.kde.org/show_bug.cgi?id=332737 Daniel Nicoletti changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Latest Commit||http://commits.kde.org/colo ||rd-kde/c7186b7ee73f319e0626 ||45f0ab73a4e0e6c808c3 Resolution|--- |FIXED --- Comment #2 from Daniel Nicoletti --- Git commit c7186b7ee73f319e062645f0ab73a4e0e6c808c3 by Daniel Nicoletti, on behalf of Florian Höch. Committed on 09/10/2016 at 06:43. Pushed by dantti into branch 'master'. EDID strings can be up to 13 bytes The EDID specification allows up to 13 bytes for text blocks. M +2-2colord-kded/Edid.cpp http://commits.kde.org/colord-kde/c7186b7ee73f319e062645f0ab73a4e0e6c808c3 -- You are receiving this mail because: You are watching all bug changes.
[khotkeys] [Bug 370328] New: Khotkeys input text not recognize Shift key
https://bugs.kde.org/show_bug.cgi?id=370328 Bug ID: 370328 Summary: Khotkeys input text not recognize Shift key Product: khotkeys Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@michael-jansen.biz Reporter: i...@trebol-a.com Section "Send input keyboard" (not sure, I have my system in spanish). I want to set "<:p:Shift+<:" for shortcut to "", but khotkeys ignore the Shift order and write " global hotkeys > send keyboard input 3.in action section set "<:p:Shift+<:" 4. set keyboard combination 5. on kwrite press keyboard combination 6. khotkeys write "" Actual Results: Ignore shift key order Expected Results: Simulate pressing Shift key -- You are receiving this mail because: You are watching all bug changes.
[colord-kde] [Bug 350773] There is no colord-kde entry in System Settings
https://bugs.kde.org/show_bug.cgi?id=350773 Daniel Nicoletti changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #2 from Daniel Nicoletti --- colord-kde in Plasma5 needs to be version 0.5.0 which is based on KF5/Qt5 -- You are receiving this mail because: You are watching all bug changes.
[choqok] [Bug 370325] Choqok 1.6 segfaults before displaying any window
https://bugs.kde.org/show_bug.cgi?id=370325 --- Comment #1 from Andrea Scarpino --- Are you using qoauth-qt4 instead of qoauth-qt5? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370327] New: Task preview image doesn't change when moving mouse over the different tasks
https://bugs.kde.org/show_bug.cgi?id=370327 Bug ID: 370327 Summary: Task preview image doesn't change when moving mouse over the different tasks Product: plasmashell Version: 5.8.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Task Manager Assignee: h...@kde.org Reporter: patrick@laposte.net CC: plasma-b...@kde.org Hi, I use Spotify as my main music player, when I go over the task bar to see the preview of this application I see a picture of the current music album. The bug starts when I go over other applications previews after passing over the Spotify one, it keeps the album picture in the preview no matter which other program I'm passing over. That's it. Thanks for the great job done up to now. Reproducible: Always Steps to Reproduce: 1. Start Spotify 2. Start other apps 3. Go over the task bar to see the previews Actual Results: Wrong image preview, keeps the one from the music player Expected Results: specific preview of each application -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 370285] Fails to load configuration when adding default panels
https://bugs.kde.org/show_bug.cgi?id=370285 --- Comment #2 from chocolatesoc...@gmail.com --- (In reply to David Rosca from comment #1) > This should fix it https://phabricator.kde.org/D2985 When I add that then plasmashell either hangs or Quicklaunch does not load the configuration. At least for the software in 16.04/16.10 beta 2. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 351086] Feature to stretch clip for looping
https://bugs.kde.org/show_bug.cgi?id=351086 farid changed: What|Removed |Added CC||snd.no...@gmail.com --- Comment #3 from farid --- This could be very helpful in some circumstances. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 370326] New: Using proxy renders with wrong aspect ratio
https://bugs.kde.org/show_bug.cgi?id=370326 Bug ID: 370326 Summary: Using proxy renders with wrong aspect ratio Product: kdenlive Version: unspecified Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: snd.no...@gmail.com I just tried to render a test based on this report from the forum: https://forum.kde.org/viewtopic.php?f=265&t=136647&p=365376#p365376 If you activate proxy on 16:9 footage and then render, the result which should be 16:9 is maintaining the 4:3 aspect ratio of the proxy. I am using today's compiled sources. Would be good to fix before 16.08.2 release. Reproducible: Always Steps to Reproduce: 1. Add a file and create a proxy of it. 2. Add it to the timeline. 3. Render the project. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 369671] Tone down transparency of kicker/kickoff menu
https://bugs.kde.org/show_bug.cgi?id=369671 Christoph Feck changed: What|Removed |Added CC||cf...@kde.org --- Comment #3 from Christoph Feck --- Kai, with the XRender backend neither of those effects are present. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 370305] Plasma becomes black after resetting default colors in the Colors KCM
https://bugs.kde.org/show_bug.cgi?id=370305 Christoph Feck changed: What|Removed |Added Product|plasmashell |systemsettings CC||cf...@kde.org, ||jpwhit...@kde.org, ||oliv...@churlaud.com Assignee|k...@davidedmundson.co.uk|mwoehlke.fl...@gmail.com Component|general |kcm_colors Target Milestone|1.0 |--- --- Comment #2 from Christoph Feck --- This affects all applications, not only the shell, so the bug is in the code that applies the colors. -- You are receiving this mail because: You are watching all bug changes.
[choqok] [Bug 370325] New: Choqok 1.6 segfaults before displaying any window
https://bugs.kde.org/show_bug.cgi?id=370325
Bug ID: 370325
Summary: Choqok 1.6 segfaults before displaying any window
Product: choqok
Version: unspecified
Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
Severity: crash
Priority: NOR
Component: general
Assignee: mehrdad.mom...@gmail.com
Reporter: sombrag...@sombragris.org
CC: scarp...@kde.org
Using Choqok 1.6.0 under
KDE Frameworks 5.25.0
Qt 5.7.0 (built against 5.7.0)
running on Linux, Slackware64-current
Choqok 1.6.0 compiles ok but it segfaults shortly after OAuth is invoked for
twitter. No window manages to display.
Below is the console output:
[eduardo:~/build/slackbuilds/choqok]$ choqok
org.kde.choqok: Choqok 1.6.0
org.kde.choqok:
org.kde.choqok:
org.kde.choqok:
org.kde.choqok:
org.kde.choqok.lib:
org.kde.choqok.lib:
org.kde.choqok.lib:
org.kde.choqok.lib: ("Account_")
org.kde.choqok.lib: "Account_"
org.kde.choqok.lib: Loading Plugin: "choqok_twitter"
org.kde.choqok.lib:
org.kde.choqok.twitterapi:
org.kde.choqok.twitter:
org.kde.choqok.lib: Successfully loaded plugin ' "choqok_twitter" '
org.kde.choqok.lib: Finding: "*"
org.kde.choqok.lib:
org.kde.choqok.lib:
org.kde.choqok.lib: Wallet successfully opened.
org.kde.choqok.lib: Read password from wallet
org.kde.choqok.lib:
org.kde.choqok.twitterapi:
org.kde.choqok.lib:
org.kde.choqok.lib: Read password from wallet
org.kde.choqok.lib:
org.kde.choqok.lib: Read password from wallet
org.kde.choqok.twitterapi: UsingOAuth: true
org.kde.choqok.twitterapi:
Segmentation fault
[eduardo:~/build/slackbuilds/choqok]$
Previously, 1.5 ran OK.
Thanks,
Eduardo
Reproducible: Always
Steps to Reproduce:
1. Run choqok
2. The program segfaults.
3.
Actual Results:
Segfault before there is even a window displayed
Expected Results:
Program should run correctly
--
You are receiving this mail because:
You are watching all bug changes.
[konsole] [Bug 370309] Idle Crash
https://bugs.kde.org/show_bug.cgi?id=370309 Christoph Feck changed: What|Removed |Added Component|general |general Product|kde |konsole Version|unspecified |16.08.1 Assignee|unassigned-b...@kde.org |konsole-de...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[phonon-backend-vlc] [Bug 335111] vlc crashes phonon by mixing qt4 and qt5
https://bugs.kde.org/show_bug.cgi?id=335111 --- Comment #73 from Christoph Feck --- So we are apparently still seeing this on recent distributions. Can someone who is subscribed to the packagers/distros mailing list please make sure all distributions are getting the VLC plugin mess right? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 370261] segfault on pressing Del key
https://bugs.kde.org/show_bug.cgi?id=370261 Christoph Feck changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #3 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 335111 *** -- You are receiving this mail because: You are watching all bug changes.
[phonon-backend-vlc] [Bug 335111] vlc crashes phonon by mixing qt4 and qt5
https://bugs.kde.org/show_bug.cgi?id=335111 Christoph Feck changed: What|Removed |Added CC||tikan...@gmail.com --- Comment #72 from Christoph Feck --- *** Bug 370261 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 370288] system settings/window decoration - "get new decoration" doesn't work
https://bugs.kde.org/show_bug.cgi?id=370288 Christoph Feck changed: What|Removed |Added CC||cf...@kde.org --- Comment #2 from Christoph Feck --- Could you check if updating to KDE Frameworks to version 5.25.0 fixes the issue? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 370312] New colours KCM needs far too many mouse clicks to change a colour
https://bugs.kde.org/show_bug.cgi?id=370312 Christoph Feck changed: What|Removed |Added CC||cf...@kde.org, ||oliv...@churlaud.com --- Comment #1 from Christoph Feck --- Agreed. During this redesign, the "Current" (unsaved) color scheme setting got lost. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370191] Look and Feel restores user customized desktop
https://bugs.kde.org/show_bug.cgi?id=370191 Janet changed: What|Removed |Added CC||bugzi...@kerridis.de -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 369285] I want to close the icons of upload manager showing on the bottom
https://bugs.kde.org/show_bug.cgi?id=369285 Christoph Feck changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |INVALID --- Comment #3 from Christoph Feck --- No response, changing status. If you can provide the requested information, please add it as a comment. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 370315] update and this
https://bugs.kde.org/show_bug.cgi?id=370315 Christoph Feck changed: What|Removed |Added Resolution|--- |DOWNSTREAM Status|UNCONFIRMED |RESOLVED --- Comment #1 from Christoph Feck --- Could you PLEASE report bugs with 'apt' updates to the bug tracker of you distribution? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 368428] Choose language
https://bugs.kde.org/show_bug.cgi?id=368428 --- Comment #4 from farid --- Wegwerf I installed plasma to see if this works and no success. I don't consider this a resolved issue. If it is a packaging thing then we should state which package gives this functionality... -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 368428] Choose language
https://bugs.kde.org/show_bug.cgi?id=368428 farid changed: What|Removed |Added Ever confirmed|0 |1 Resolution|INVALID |--- Status|RESOLVED|REOPENED -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 370011] url in Chrome doesn't make it to shared clipboard
https://bugs.kde.org/show_bug.cgi?id=370011 --- Comment #2 from Zach --- Yes, Chrome on Android. Its the only app that doesnt seem to work. Maybe it has to do with my slightly older Android version? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 370319] Flatten image crashes Krita
https://bugs.kde.org/show_bug.cgi?id=370319 Tyson Tan changed: What|Removed |Added CC||tyson...@mail.com --- Comment #1 from Tyson Tan --- Same here using krita-3.0.1.90-x86_64.appimage -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 354242] Sound volume level is higher than system sound volume (Pulseaudio)
https://bugs.kde.org/show_bug.cgi?id=354242 Myriam Schweingruber changed: What|Removed |Added Resolution|UNMAINTAINED|INVALID -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 341667] "Organize Files -> Transcode" only rename *.mp3 to *.ogg but do not change the file format in fact
https://bugs.kde.org/show_bug.cgi?id=341667 Myriam Schweingruber changed: What|Removed |Added Resolution|UNMAINTAINED|WORKSFORME --- Comment #15 from Myriam Schweingruber --- Erm, and what makes you think this is unmaintained? Just because your bug is not being fixed? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370324] New: Pager disappears but is not reappearing even though it should
https://bugs.kde.org/show_bug.cgi?id=370324
Bug ID: 370324
Summary: Pager disappears but is not reappearing even though it
should
Product: plasmashell
Version: 5.8.0
Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: Pager
Assignee: h...@kde.org
Reporter: mvourla...@gmail.com
CC: plasma-b...@kde.org
1. The Pager shows 2 desktops
2. we remove a desktop and the pager disappears from the panel
3. we add a desktop from the systems setings (we now have two desktops) but the
pager does not reappear in the panel
4. we unlock the widgets and show the panel's settings window
5. the pager is shown correctly
6. we lock the widgets and pager is shown correctly
it is like the pager's status is not updated from hidden,
that is something I can guess from panel's code line:
-
visible: Qt.binding(function() {
return applet.status !== PlasmaCore.Types.HiddenStatus ||
(!plasmoid.immutable && plasmoid.userConfiguring)
})
-
big possibility, same problem appears in the activity pager also
Reproducible: Always
--
You are receiving this mail because:
You are watching all bug changes.
[okular] [Bug 246196] When filling in forms, make it possible to set the font size of the forms
https://bugs.kde.org/show_bug.cgi?id=246196 --- Comment #9 from Carl-Daniel Hailfinger --- Created attachment 101493 --> https://bugs.kde.org/attachment.cgi?id=101493&action=edit Hardcode a reasonable default max font size for form fields if autosize=on This patch solves the immediate problem for me, but obviously hardcoding a max font size of 12 for all form fields with unspecified font size is not optimal for everyone. Options are either a setting per form field, or a global setting. Given that most forms are designed for uniform font size, a global setting is probably sufficient and simplifies the UI. If anyone knows poppler well enough to make this a settable attribute of the document instead of a hardcoded constant in two functions, please tell me. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370323] New: Auto-hide is broken for touch screens
https://bugs.kde.org/show_bug.cgi?id=370323 Bug ID: 370323 Summary: Auto-hide is broken for touch screens Product: plasmashell Version: 5.8.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: aleix...@kde.org When using a touch events the metaphor doesn't translate. We want to be able to pull the panel from the outside instead of pushing it from the border. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 246196] When filling in forms, make it possible to set the font size of the forms
https://bugs.kde.org/show_bug.cgi?id=246196 --- Comment #8 from Carl-Daniel Hailfinger --- Working on this... right now I can set a max font size for forms where the font size is not specified. No GUI, and still requires recompilation of libpoppler if you want a different size. Then again, that's probably a lot better than nothing. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 368801] Wish: Able to do multiple clip jobs to one clip.
https://bugs.kde.org/show_bug.cgi?id=368801 --- Comment #2 from Evert Vorster --- Not stale at all. Apply speed clip job, get .mlt file in the Project Bin. Try to stabilize the .mlt file. I get an error message: "No valid clip to process" Why can't we stabilize .mlt files? -Evert- -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370322] New: Graphics not working properly 640x480 instead of 1920x900
https://bugs.kde.org/show_bug.cgi?id=370322 Bug ID: 370322 Summary: Graphics not working properly 640x480 instead of 1920x900 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: fr1ve...@web.de CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.5) Qt Version: 5.5.1 Operating System: Linux 4.8.0-1.g55165a4-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: Just starting the PC. Upgraded to Kernel 4.8 in OpenSUse 42.1 with NVidia GTS 450 - Unusual behavior I noticed: Unusal graphic size 640x480 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 0x7f8be6a6b7c0 (LWP 3508))] Thread 7 (Thread 0x7f8b2330b700 (LWP 3538)): #0 0x7f8bdf77bea8 in pthread_getspecific () at /lib64/libpthread.so.0 #1 0x7f8bdc670400 in g_thread_self () at /usr/lib64/libglib-2.0.so.0 #2 0x7f8bdc649ecc in g_main_context_acquire () at /usr/lib64/libglib-2.0.so.0 #3 0x7f8bdc64ad25 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f8bdc64af7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f8be089ad8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f8be0841d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7f8be066361a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7f8be4513282 in () at /usr/lib64/libQt5Quick.so.5 #9 0x7f8be066832f in () at /usr/lib64/libQt5Core.so.5 #10 0x7f8bdf7770a4 in start_thread () at /lib64/libpthread.so.0 #11 0x7f8bdff7602d in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7f8bb27b9700 (LWP 3536)): #0 0x7f8bdf77b03f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f8be614686b in () at /usr/lib64/libQt5Script.so.5 #2 0x7f8be6146899 in () at /usr/lib64/libQt5Script.so.5 #3 0x7f8bdf7770a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f8bdff7602d in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f8bb3fff700 (LWP 3535)): #0 0x7f8bdff69ccd in read () at /lib64/libc.so.6 #1 0x7f8bd810c073 in () at /usr/lib64/tls/libnvidia-tls.so.367.44 #2 0x7f8bdc68bb60 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f8bdc64a999 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #4 0x7f8bdc64adf8 in () at /usr/lib64/libglib-2.0.so.0 #5 0x7f8bdc64af7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #6 0x7f8be089ad8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7f8be0841d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #8 0x7f8be066361a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #9 0x7f8be3977e18 in () at /usr/lib64/libQt5Qml.so.5 #10 0x7f8be066832f in () at /usr/lib64/libQt5Core.so.5 #11 0x7f8bdf7770a4 in start_thread () at /lib64/libpthread.so.0 #12 0x7f8bdff7602d in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f8bb9ada700 (LWP 3534)): #0 0x7f8bdff6dbfd in poll () at /lib64/libc.so.6 #1 0x7f8bdc64ae64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f8bdc64af7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f8be089ad8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f8be0841d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f8be066361a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f8be3977e18 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7f8be066832f in () at /usr/lib64/libQt5Core.so.5 #8 0x7f8bdf7770a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7f8bdff7602d in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f8bc5a73700 (LWP 3525)): #0 0x7f8bdf77d79c in __lll_lock_wait () at /lib64/libpthread.so.0 #1 0x7f8bdf7794a4 in _L_lock_986 () at /lib64/libpthread.so.0 #2 0x7f8bdf779306 in pthread_mutex_lock () at /lib64/libpthread.so.0 #3 0x7f8bdba7a81c in () at /usr/X11R6/lib64/libGL.so.1 #4 0x7f8bdba7f741 in () at /usr/X11R6/lib64/libGL.so.1 #5 0x7f8bdba7fc58 in () at /usr/X11R6/lib64/libGL.so.1 #6 0x7f8bd810c102 in () at /usr/lib64/tls/libnvidia-tls.so.367.44 #7 0x7f8bdc68bb60 in () at /usr/lib64/libglib-2.0.so.0 #8 0x7f8bdc64a999 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #9 0x7f8bdc64adf8 in () at /usr/lib64/libglib-2.0.so.0 #10 0x7f8bdc64af7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #11 0x00
[kdialog] [Bug 340398] Merge features from kcolorchooser
https://bugs.kde.org/show_bug.cgi?id=340398 Eli Green changed: What|Removed |Added CC||e...@develer.com --- Comment #5 from Eli Green --- I've opened a review request on this (ancient) bug as a way of dipping my toes into KDE development. Please let me know if I've done anything incorrectly, whether in the code or process. https://git.reviewboard.kde.org/r/129128/ -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 369349] Low framerate when drawing with the stabilizer
https://bugs.kde.org/show_bug.cgi?id=369349 --- Comment #3 from relativistic.police...@gmail.com --- It occurs with 3.0.1 (and 3.0.1.1) on Windows. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 370321] New: It sometimes changes the tool from brush to zoom when undoing (cmd+z)
https://bugs.kde.org/show_bug.cgi?id=370321 Bug ID: 370321 Summary: It sometimes changes the tool from brush to zoom when undoing (cmd+z) Product: krita Version: 3.0.2 Alpha Platform: Mac OS X Disk Images OS: OS X Status: UNCONFIRMED Severity: normal Priority: NOR Component: shortcuts Assignee: krita-bugs-n...@kde.org Reporter: a.minha.venda.de.gara...@gmail.com If I undo (using cmd+z shortcut) a brush stroke, sometimes the tool changes from Brush to Zoom. It doesn't always happen but is frequent. I then have to press 'z' again (shortcut associated with Zoom) to revert to the Brush tool. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 370320] New: Cannot open Krita files by double clicking
https://bugs.kde.org/show_bug.cgi?id=370320 Bug ID: 370320 Summary: Cannot open Krita files by double clicking Product: krita Version: 3.0.2 Alpha Platform: Mac OS X Disk Images OS: OS X Status: UNCONFIRMED Severity: normal Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: a.minha.venda.de.gara...@gmail.com When I try to open a Krita file by double clicking, it doesn't open the file (Krita opens but the file doesn't). If I want to open a file, I have to use the cmd+o inside Krita. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 370319] New: Flatten image crashes Krita
https://bugs.kde.org/show_bug.cgi?id=370319 Bug ID: 370319 Summary: Flatten image crashes Krita Product: krita Version: 3.0.2 Alpha Platform: Mac OS X Disk Images OS: OS X Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: a.minha.venda.de.gara...@gmail.com Krita always crashes when flattening an image. Either by shortcut (Shift+Cmd+E) or by selecting Layer > Flatten Image from the menu. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 370318] New: Krita crashes frequently when ungrouping a group with filter layers inside
https://bugs.kde.org/show_bug.cgi?id=370318 Bug ID: 370318 Summary: Krita crashes frequently when ungrouping a group with filter layers inside Product: krita Version: 3.0.2 Alpha Platform: Mac OS X Disk Images OS: OS X Status: UNCONFIRMED Severity: crash Priority: NOR Component: Layer Stack Assignee: krita-bugs-n...@kde.org Reporter: a.minha.venda.de.gara...@gmail.com Krita crashes frequently (not always) after ungrouping layers with filter layers applied. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370317] New: [Activity Pager] - can not drag windows anymore from activity to activity
https://bugs.kde.org/show_bug.cgi?id=370317 Bug ID: 370317 Summary: [Activity Pager] - can not drag windows anymore from activity to activity Product: plasmashell Version: 5.8.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Pager Assignee: h...@kde.org Reporter: mvourla...@gmail.com CC: plasma-b...@kde.org When using Activity Pager in order to move a window from activity to activity the window is not moved and the activity is changed... Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 367990] [Activity Pager] - Can not set Vertical Layout properly
https://bugs.kde.org/show_bug.cgi?id=367990 Michail Vourlakos changed: What|Removed |Added Version|5.7.3 |5.8.0 --- Comment #1 from Michail Vourlakos --- remains in Plasma 5.8.0 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 370316] New: Krita crashes when applying a transform mask on image
https://bugs.kde.org/show_bug.cgi?id=370316 Bug ID: 370316 Summary: Krita crashes when applying a transform mask on image Product: krita Version: 3.0.2 Alpha Platform: Mac OS X Disk Images OS: OS X Status: UNCONFIRMED Severity: crash Priority: NOR Component: adjustment layers Assignee: krita-bugs-n...@kde.org Reporter: a.minha.venda.de.gara...@gmail.com Everytime I need to do a transform mask on an image, it crashes. That doesn't happen if I apply a transform mask on a stroke, only happens with images. Reproducible: Always Steps to Reproduce: 1. Open Image 2. Apply a Transform Mask 3. Enter Actual Results: It crashes. Expected Results: It should have done the transform mask without crashing. On OSX El Capitan. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 370314] New: KDevelop crashes after switching debugger plugins
https://bugs.kde.org/show_bug.cgi?id=370314 Bug ID: 370314 Summary: KDevelop crashes after switching debugger plugins Product: kdevelop Version: 5.0.1 Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: aman...@kde.org Application: kdevelop (5.0.1) (Compiled from sources) Qt Version: 5.7.0 Frameworks Version: 5.27.0 Operating System: Linux 4.1.31-30-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: Make sure GBD plugin is enabled and LLDB plugin is disabled. Now disable GDB and enable LLDB, close the config dialog, press Debug for the project: crash. Seems it still holds an invalid reference to the gdb plugin. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f67edd69800 (LWP 14127))] Thread 18 (Thread 0x7f6744bb7700 (LWP 14304)): #0 0x7f67e6b8acb8 in QMutex::unlock() (__m2=std::memory_order_relaxed, __m1=std::memory_order_release, __p2=0x0, __p1=@0x7f6744bb6ae0: 0x1, this=) at /usr/include/c++/4.8/bits/atomic_base.h:844 #1 0x7f67e6b8acb8 in QMutex::unlock() (__p2=0x0, __m=std::memory_order_release, __p1=@0x7f6744bb6ae0: 0x1, this=) at /usr/include/c++/4.8/atomic:445 #2 0x7f67e6b8acb8 in QMutex::unlock() (currentValue=, newValue=0x0, expectedValue=0x1, _q_value=...) at ../../src/corelib/arch/qatomic_cxx11.h:174 #3 0x7f67e6b8acb8 in QMutex::unlock() (currentValue=, newValue=0x0, expectedValue=0x1, this=this@entry=0x5a60cb0) at ../../src/corelib/thread/qbasicatomic.h:261 #4 0x7f67e6b8acb8 in QMutex::unlock() (current=, this=this@entry=0x5a60cb0) at thread/qmutex.h:92 #5 0x7f67e6b8acb8 in QMutex::unlock() (this=this@entry=0x5a60cb0) at thread/qmutex.cpp:277 #6 0x7f67e6d97e85 in postEventSourcePrepare(GSource*, gint*) (this=) at ../../src/corelib/thread/qmutex.h:147 #7 0x7f67e6d97e85 in postEventSourcePrepare(GSource*, gint*) (this=, __in_chrg=) at ../../src/corelib/thread/qmutex.h:141 #8 0x7f67e6d97e85 in postEventSourcePrepare(GSource*, gint*) (this=0x5a60c80) at ../../src/corelib/thread/qthread_p.h:254 #9 0x7f67e6d97e85 in postEventSourcePrepare(GSource*, gint*) (s=0x7f6726cf46b0, timeout=timeout@entry=0x7f6744bb6b64) at kernel/qeventdispatcher_glib.cpp:259 #10 0x7f67daab44ad in g_main_context_prepare (context=context@entry=0x7f672402f120, priority=priority@entry=0x7f6744bb6be8) at gmain.c:3410 #11 0x7f67daab4d80 in g_main_context_iterate (context=context@entry=0x7f672402f120, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3788 #12 0x7f67daab4f7c in g_main_context_iteration (context=0x7f672402f120, may_block=1) at gmain.c:3869 #13 0x7f67e6d97f4b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f6724005990, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #14 0x7f67e6d4789b in QEventLoop::exec(QFlags) (this=this@entry=0x7f6744bb6d20, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210 #15 0x7f67e6b8e02a in QThread::exec() (this=) at thread/qthread.cpp:507 #16 0x7f67e407209a in KDevelop::CompletionWorkerThread::run() () at /opt/kde5/lib64/libKDevPlatformLanguage.so.10 #17 0x7f67e6b92859 in QThreadPrivate::start(void*) (arg=0x4dafd70) at thread/qthread_unix.cpp:344 #18 0x7f67dd03c0a4 in start_thread (arg=0x7f6744bb7700) at pthread_create.c:309 #19 0x7f67e5f8302d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 17 (Thread 0x7f67695b0700 (LWP 14277)): #0 0x7f67e5f7abfd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f67daab4e64 in g_main_context_iterate (priority=2147483647, n_fds=1, fds=0x7f674c003070, timeout=-1, context=0x7f674c000990) at gmain.c:4103 #2 0x7f67daab4e64 in g_main_context_iterate (context=context@entry=0x7f674c000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3803 #3 0x7f67daab4f7c in g_main_context_iteration (context=0x7f674c000990, may_block=1) at gmain.c:3869 #4 0x7f67e6d97f4b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f674c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f67e6d4789b in QEventLoop::exec(QFlags) (this=this@entry=0x7f67695afdd0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210 #6 0x7f67e6b8e02a in QThread::exec() (this=) at thread/qthread.cpp:507 #7 0x7f67e6b92859 in QThreadPrivate::start(void*) (arg=0x7f67ec8bac18 ) at thread/qthread_unix.cpp:344 #8 0x7f67dd03c0a4 in start_thread (arg=0x7f67695b0700) at pthread_create.c:309 #9 0x7f67e5f8302d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 16 (Thread 0x7f676a7fc700 (LWP 14250)): #0 0x7f67a9599dd3 in clang_getCursorLocation ()
[systemsettings] [Bug 370315] New: update and this
https://bugs.kde.org/show_bug.cgi?id=370315 Bug ID: 370315 Summary: update and this Product: systemsettings Version: 5.6.5 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: robledo...@yahoo.com W: Can't drop privileges for downloading as file '/var/cache/apt/archives/partial/libarchive13_3.2.1-2~ubuntu16.04.1_i386.deb' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) Reproducible: Always Actual Results: W: Can't drop privileges for downloading as file '/var/cache/apt/archives/partial/libarchive13_3.2.1-2~ubuntu16.04.1_i386.deb' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) Expected Results: no problems still ongoing issue. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 370307] kstars crash after starting an automated ekos session
https://bugs.kde.org/show_bug.cgi?id=370307 --- Comment #2 from Sebastien --- Yes it's possible. I launched an automatic sequence which contains an astrometry process. I was moving the planetarium in kstars to show where my scope was pointing and the kde crash messagebox appeared. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368818] Panel on wrong position on wrong screen
https://bugs.kde.org/show_bug.cgi?id=368818 --- Comment #7 from Adam --- Created attachment 101492 --> https://bugs.kde.org/attachment.cgi?id=101492&action=edit a screenshot demonstrating the problem (virtual areas in red) I think this is related: when i open a picture in dolphin, the gwenview window is too big. i can't see the title bar on the small screen (see attachment). I can move it with alt and when maximizing the correct size is used. maximizing works normally. the attached screen layout was made automatically when attaching the cable (if it matters: same apple macbook air with thunderbolt / mini display port and intel on board gpu) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365295] The three icons in buttons "Search", "Filter" and "Close" are very small
https://bugs.kde.org/show_bug.cgi?id=365295 --- Comment #12 from Michail Vourlakos --- This can be fixed in my system if at WidgetExplorer.qml:210 (Plasma 5.8.0) I comment the line and do the following that looks a little how activities manager is using height --- //Layout.minimumHeight: Math.max(heading.height, searchInput.height) Layout.fillHeight: true -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 364318] git master: regression: effect is totally "ineffective" (with regression project)
https://bugs.kde.org/show_bug.cgi?id=364318 --- Comment #6 from Wegwerf --- This is with the recent last keyframe fix (commit https://quickgit.kde.org/?p=kdenlive.git&a=commit&h=2c7f4bca78e8b65b339ebdc585637e4c256e3cbe) in place, this does not fix this issue. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 364318] git master: regression: effect is totally "ineffective" (with regression project)
https://bugs.kde.org/show_bug.cgi?id=364318 --- Comment #5 from Wegwerf --- More testing reveals that resizing the clip helps, but only if I resize the clip a lot by dragging the end of the clip, then resize it back to its original size. Next, some "careful research" shows that I need to resize the image clip beyond its current length. When loading, you can see the length of the title clip to be 00:00:12:05. The timeline clip instance starts at position 00:00:03:08 and has a length of 00:00:06:00, giving a total(!) length=end of 00:00:09:08. Now, resize the clip in the timeline only one or two seconds: doesn't change the incorrect blurring. Next, resize beyond a right end of 00:00:12:05, that is, a timeline clip length of around 00:00:12:08. Now the animation gets correctly updated, so scrubbing the timeline shows the proper blur ramp-down. -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 369527] applet should color through system colors
https://bugs.kde.org/show_bug.cgi?id=369527 Alexandr Akulich changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 CC||akulichalexan...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365295] The three icons in buttons "Search", "Filter" and "Close" are very small
https://bugs.kde.org/show_bug.cgi?id=365295 Michail Vourlakos changed: What|Removed |Added Version|5.7.0 |5.8.0 --- Comment #11 from Michail Vourlakos --- This still remains in my system with Plasma 5.8.0 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 364837] High CPU usage when kdenlive window is on top
https://bugs.kde.org/show_bug.cgi?id=364837 --- Comment #17 from Wegwerf --- As JBM just pointed out, the fix hasn't yet landed in Qt, so we'll have to wait. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 246196] When filling in forms, make it possible to set the font size of the forms
https://bugs.kde.org/show_bug.cgi?id=246196 Luigi Toscano changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=363768 CC||luigi.tosc...@tiscali.it --- Comment #7 from Luigi Toscano --- (In reply to Carl-Daniel Hailfinger from comment #6) > In this bug, the form fields have no font size (size 0) specified, and no > prerendered appearance exists for the fields in question. > > Bug #363768 is related. In Bug #363768, the font size in the prerendered > appearance /AP object is not used as a hint for font size selection. Given > that solving this bug #246196 would also allow to work around bug #363768, > I'm setting #246196 as blocker for #363768. They are related, but you can solve 363768 without 246196. So no blocker, but I can fill the "See also" field. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 363768] Font size is changed when form value is modified
https://bugs.kde.org/show_bug.cgi?id=363768 Luigi Toscano changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=246196 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 370313] New: Aurorae doesn't display close button background if theme is named Nomad
https://bugs.kde.org/show_bug.cgi?id=370313 Bug ID: 370313 Summary: Aurorae doesn't display close button background if theme is named Nomad Product: kwin Version: 5.8.0 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: aurorae Assignee: kwin-bugs-n...@kde.org Reporter: uri_herr...@nitrux.in I can't describe the bug better than that. Aurorae refuses to use the close button background if the theme is named Nomad. Changing the name to anything else works fine. Reproducible: Always Steps to Reproduce: 1. Copy an Aurorae theme, rename it Nomad 2. Open system settings and change the theme 3. Close button is invisible Actual Results: Aurorae doesn't display close button background. Expected Results: Aurorae displays close button background. I literally copied a working theme and tested that by changing the name to Nomad and it refused to display the close button background file until I changed back the name. -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 368070] kdesrc-build-setup is still about Qt 4
https://bugs.kde.org/show_bug.cgi?id=368070 --- Comment #4 from Michael Pyne --- Git commit 2e62dc7e15cee8fc881fc5306e42861ce02d912d by Michael Pyne. Committed on 08/10/2016 at 19:39. Pushed by mpyne into branch 'master'. Point CMake to Qt's cmake module directory if different from KF5's I still need to fix kdesrc-build-setup though. :( M +6-10 modules/ksb/BuildSystem.pm M +17 -6modules/ksb/BuildSystem/KDE4.pm M +4-26 modules/ksb/Module.pm M +4-2modules/ksb/l10nSystem.pm http://commits.kde.org/kdesrc-build/2e62dc7e15cee8fc881fc5306e42861ce02d912d -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 366594] can't use ignore-modules in option stanza from config file
https://bugs.kde.org/show_bug.cgi?id=366594 Michael Pyne changed: What|Removed |Added Status|ASSIGNED|RESOLVED Latest Commit||http://commits.kde.org/kdes ||rc-build/14fc9bb282ef1cf5cb ||3b73d2b40083186fd303a1 Resolution|--- |FIXED Version Fixed In||16.08 Latest Commit|http://commits.kde.org/kdes |http://commits.kde.org/kdes |rc-build/14fc9bb282ef1cf5cb |rc-build/c9d32735a4ff11c5a3 |3b73d2b40083186fd303a1 |0654976e2bb539c0886710 Version Fixed In|16.08 |16.10 --- Comment #7 from Michael Pyne --- Git commit 14fc9bb282ef1cf5cb3b73d2b40083186fd303a1 by Michael Pyne. Committed on 08/10/2016 at 19:34. Pushed by mpyne into branch 'master'. Allow module-set validation to pass in 'options' overrides. This show allow 'ignore-modules' to work in 'options' blocks (at least, it does in my testing). FIXED-IN:16.08 M +8-5modules/ksb/Application.pm http://commits.kde.org/kdesrc-build/14fc9bb282ef1cf5cb3b73d2b40083186fd303a1 --- Comment #8 from Michael Pyne --- Git commit c9d32735a4ff11c5a30654976e2bb539c0886710 by Michael Pyne. Committed on 08/10/2016 at 19:38. Pushed by mpyne into branch 'master'. Allow options blocks to override unseen module-sets. In other words, we separate parsing of options blocks from whether existing modules or module-sets have already been seen. Instead we decide later (when expanding module-sets or modules) whether there are any relevant options blocks to apply (this is the 'deferred option' handling). Now you should be able to declare options blocks that contain options appropriate for module-sets, even if no module-set is defined with that name (e.g. if you're doing weirdness with 'include' declarations). This does require that you don't use the same name for modules and for module-sets, but that is essentially already a requirement anyways. There's no good way to always disambiguate that. FIXED-IN:16.10 M +17 -53 modules/ksb/Application.pm M +33 -14 modules/ksb/ModuleResolver.pm http://commits.kde.org/kdesrc-build/c9d32735a4ff11c5a30654976e2bb539c0886710 -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 366594] can't use ignore-modules in option stanza from config file
https://bugs.kde.org/show_bug.cgi?id=366594 Michael Pyne changed: What|Removed |Added Status|ASSIGNED|RESOLVED Latest Commit||http://commits.kde.org/kdes ||rc-build/14fc9bb282ef1cf5cb ||3b73d2b40083186fd303a1 Resolution|--- |FIXED Version Fixed In||16.08 Latest Commit|http://commits.kde.org/kdes |http://commits.kde.org/kdes |rc-build/14fc9bb282ef1cf5cb |rc-build/c9d32735a4ff11c5a3 |3b73d2b40083186fd303a1 |0654976e2bb539c0886710 Version Fixed In|16.08 |16.10 --- Comment #7 from Michael Pyne --- Git commit 14fc9bb282ef1cf5cb3b73d2b40083186fd303a1 by Michael Pyne. Committed on 08/10/2016 at 19:34. Pushed by mpyne into branch 'master'. Allow module-set validation to pass in 'options' overrides. This show allow 'ignore-modules' to work in 'options' blocks (at least, it does in my testing). FIXED-IN:16.08 M +8-5modules/ksb/Application.pm http://commits.kde.org/kdesrc-build/14fc9bb282ef1cf5cb3b73d2b40083186fd303a1 --- Comment #8 from Michael Pyne --- Git commit c9d32735a4ff11c5a30654976e2bb539c0886710 by Michael Pyne. Committed on 08/10/2016 at 19:38. Pushed by mpyne into branch 'master'. Allow options blocks to override unseen module-sets. In other words, we separate parsing of options blocks from whether existing modules or module-sets have already been seen. Instead we decide later (when expanding module-sets or modules) whether there are any relevant options blocks to apply (this is the 'deferred option' handling). Now you should be able to declare options blocks that contain options appropriate for module-sets, even if no module-set is defined with that name (e.g. if you're doing weirdness with 'include' declarations). This does require that you don't use the same name for modules and for module-sets, but that is essentially already a requirement anyways. There's no good way to always disambiguate that. FIXED-IN:16.10 M +17 -53 modules/ksb/Application.pm M +33 -14 modules/ksb/ModuleResolver.pm http://commits.kde.org/kdesrc-build/c9d32735a4ff11c5a30654976e2bb539c0886710 -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 370181] partiotionmanager crashes while opening and scaning device /dev/sda
https://bugs.kde.org/show_bug.cgi?id=370181 hrvo...@jankovci.net changed: What|Removed |Added Product|neon|partitionmanager Version|unspecified |1.2.1 Component|general |general -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 370208] KDE Neon updated to 5.8 - now can't log in (blank screen after splash)
https://bugs.kde.org/show_bug.cgi?id=370208 --- Comment #3 from Avery Freeman --- Hi - Did not do apt-get full-upgrade, just apt-get update && apt-get upgrade Sounds like we are experiencing the same issue. Did not try getting another tty - thanks for mentioning, will be useful for fixing -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 370312] New: New colours KCM needs far too many mouse clicks to change a colour
https://bugs.kde.org/show_bug.cgi?id=370312 Bug ID: 370312 Summary: New colours KCM needs far too many mouse clicks to change a colour Product: systemsettings Version: unspecified Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: kcm_colors Assignee: mwoehlke.fl...@gmail.com Reporter: j...@keelhaul.me.uk CC: jpwhit...@kde.org This KCM (in current plasma-desktop Git master, not sure if it has made it into an official release yet) has been recently redesigned to presumably reduce the complexity and the number of tabs. This, though, has happened at the price of needing an excessive number of mouse clicks just to make a single colour change. In the previous style of KCM (and in KDE4), starting from the KCM being open the sequence of mouse operations to change a single colour of the current scheme is: 1. Select the Colours tab. 2. Click the colour button for the item to change, the colour picker opens. 3. Pick a colour by whatever means is wanted, then OK. 4. Click Apply, the desktop colour scheme changes. In the new KCM the sequence needed is: 1. Assuming that the current colour scheme is selected in the list, click Edit Scheme. 2. In the dialogue that appears, select the Colours tab. 3. Click the colour button for the item to change, the colour picker opens. 4. Pick a colour by whatever means is wanted, then OK. 5. Click Save. 6. Assuming that you don't want to change the name, click OK. 7. Click Overwrite to confirm overwriting the existing scheme. 8. Click Close. 9. Select the scheme name in the list again (since there is now no selection). 10. Click Apply; the desktop colour scheme changes. This needs more than twice as many mouse clicks to perform the equivalent operation, making it more difficult to tweak those colours which are not shown in the preview (e.g. window title bar colours). Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 246196] When filling in forms, make it possible to set the font size of the forms
https://bugs.kde.org/show_bug.cgi?id=246196 Carl-Daniel Hailfinger changed: What|Removed |Added CC||c-d.hailfinger.devel.2006@g ||mx.net --- Comment #6 from Carl-Daniel Hailfinger --- In this bug, the form fields have no font size (size 0) specified, and no prerendered appearance exists for the fields in question. Bug #363768 is related. In Bug #363768, the font size in the prerendered appearance /AP object is not used as a hint for font size selection. Given that solving this bug #246196 would also allow to work around bug #363768, I'm setting #246196 as blocker for #363768. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 353983] Turning off compositing breaks Plasma panel rendering
https://bugs.kde.org/show_bug.cgi?id=353983 --- Comment #40 from Andy --- Yes, this bug is still present with 5.8 but no one seems to care. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 362988] sftp connection win dolphin hangs/stops working after few seconds
https://bugs.kde.org/show_bug.cgi?id=362988 Emmanuel Pescosta changed: What|Removed |Added Component|general |default Version|15.12.3 |unspecified Assignee|dolphin-bugs-n...@kde.org |plasma-de...@kde.org CC||emmanuelpescosta099@gmail.c ||om Product|dolphin |kio-extras -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 368008] Using a DAV filesystem, Dolphin fails to delete a file containing a µ
https://bugs.kde.org/show_bug.cgi?id=368008 Emmanuel Pescosta changed: What|Removed |Added Component|webdav |default Assignee|kdelibs-b...@kde.org|plasma-de...@kde.org Product|kio |kio-extras -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 368008] Using a DAV filesystem, Dolphin fails to delete a file containing a µ
https://bugs.kde.org/show_bug.cgi?id=368008 Emmanuel Pescosta changed: What|Removed |Added Component|general |webdav CC||emmanuelpescosta099@gmail.c ||om Assignee|dolphin-bugs-n...@kde.org |kdelibs-b...@kde.org Product|dolphin |kio --- Comment #1 from Emmanuel Pescosta --- Thanks for the bug report, looks like a regression in the KF5 port of the webdav ioslave. -- You are receiving this mail because: You are watching all bug changes.
[forum.kde.org] [Bug 322866] KDE Identity: knowledge of username is required to reset password and to obtain information about username
https://bugs.kde.org/show_bug.cgi?id=322866 sasha changed: What|Removed |Added CC|sa...@goldnet.ca| -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 348691] Increase transition timings between entries and sub-entries
https://bugs.kde.org/show_bug.cgi?id=348691 --- Comment #14 from Kevin Kofler --- I asked Germano on IRC (in Italian) what he really wants, and he explained that he wants a longer delay for opening submenus on mouseover (because moving the mouse over the menu opens all the submenus, which slows everything down for him, even the highlighting of the menu items under the mouse). I'm not convinced it's a good idea, but that's what this bug is about. I also think this is mainly a driver issue. -- You are receiving this mail because: You are watching all bug changes.
[forum.kde.org] [Bug 322866] KDE Identity: knowledge of username is required to reset password and to obtain information about username
https://bugs.kde.org/show_bug.cgi?id=322866 --- Comment #70 from Ben Cooksley --- Sasha, your username has now been emailed to you. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 370311] New: KDevelop crashed during quit
https://bugs.kde.org/show_bug.cgi?id=370311 Bug ID: 370311 Summary: KDevelop crashed during quit Product: kdevelop Version: 5.0.1 Platform: Mageia RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: piotr.mierzwin...@gmail.com Application: kdevelop (5.0.1) Qt Version: 5.6.1 Frameworks Version: 5.27.0 Operating System: Linux 4.8.1-desktop-1.mga6 x86_64 Distribution: "Mageia 6" -- Information about the crash: - What I was doing when the application crashed: I run application and got message that run is not possible. After that I wanted quit KDevelop and it crashed. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fef60f05800 (LWP 17331))] Thread 5 (Thread 0x7feef37fe700 (LWP 19260)): #0 0x7fef71796c4f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fef6cd4d234 in QTWTF::TCMalloc_PageHeap::scavengerThread() () at /lib64/libQt5Script.so.5 #2 0x7fef6cd4d279 in () at /lib64/libQt5Script.so.5 #3 0x7fef7179166d in start_thread () at /lib64/libpthread.so.0 #4 0x7fef77910ded in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7fef1bfff700 (LWP 17541)): #0 0x7fef77904f9d in poll () at /lib64/libc.so.6 #1 0x7fef70901a54 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7fef70901b5c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7fef7820d3ab in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7fef781b8c9a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7fef77ff237c in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7fef77ff6fb9 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #7 0x7fef7179166d in start_thread () at /lib64/libpthread.so.0 #8 0x7fef77910ded in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7fef52efd700 (LWP 17338)): #0 0x7fef71796ff8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fef77ff7d06 in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #2 0x7fef75a16568 in KDevelop::DUChainPrivate::CleanupThread::run() (this=0x2acb150) at /usr/src/debug/kdevplatform-5.0.1/language/duchain/duchain.cpp:282 #3 0x7fef77ff6fb9 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #4 0x7fef7179166d in start_thread () at /lib64/libpthread.so.0 #5 0x7fef77910ded in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7fef5af91700 (LWP 17334)): #0 0x7fef77904f9d in poll () at /lib64/libc.so.6 #1 0x7fef70901a54 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7fef70901b5c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7fef7820d3ab in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7fef781b8c9a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7fef77ff237c in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7fef7a337615 in QDBusConnectionManager::run() () at /lib64/libQt5DBus.so.5 #7 0x7fef77ff6fb9 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #8 0x7fef7179166d in start_thread () at /lib64/libpthread.so.0 #9 0x7fef77910ded in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7fef60f05800 (LWP 17331)): [KCrash Handler] #6 0x057ae1c0 in () #7 0x7fef752c1376 in NotifyByAudio::~NotifyByAudio() () at /lib64/libKF5Notifications.so.5 #8 0x7fef752c1409 in NotifyByAudio::~NotifyByAudio() () at /lib64/libKF5Notifications.so.5 #9 0x7fef781e45f3 in QObjectPrivate::deleteChildren() () at /lib64/libQt5Core.so.5 #10 0x7fef781ed1a4 in QObject::~QObject() () at /lib64/libQt5Core.so.5 #11 0x7fef752a4bf9 in (anonymous namespace)::Q_QGS_s_self::innerFunction()::Holder::~Holder() () at /lib64/libKF5Notifications.so.5 #12 0x7fef77851478 in __run_exit_handlers () at /lib64/libc.so.6 #13 0x7fef778514c5 in () at /lib64/libc.so.6 #14 0x7fef7783b607 in __libc_start_main () at /lib64/libc.so.6 #15 0x0040c0f9 in _start () at ../sysdeps/x86_64/start.S:118 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 369317] Kwin crash with gles
https://bugs.kde.org/show_bug.cgi?id=369317 --- Comment #10 from Uriy Zhuravlev --- > I guess we need to get distros to switch to the fork. I started - https://bugs.gentoo.org/show_bug.cgi?id=596548 -- You are receiving this mail because: You are watching all bug changes.
[forum.kde.org] [Bug 322866] KDE Identity: knowledge of username is required to reset password and to obtain information about username
https://bugs.kde.org/show_bug.cgi?id=322866 sasha changed: What|Removed |Added CC||sa...@goldnet.ca --- Comment #69 from sasha --- Same here. I do not remember my user name. My email is the same as on this KDE bugs account. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370306] no option to show 12-hour time without displaying the AM/PM part
https://bugs.kde.org/show_bug.cgi?id=370306 --- Comment #3 from Aaron Wolf --- To be clear: I'm asking for this to remain open and be just a request for a checkbox for whether or not to show the AM/PM part of the time. This makes the difference between a usable or unusable digital clock for left or right side panels. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 370310] New: I can't type Chinese characters, and whenever I use multi-line the software crashes.
https://bugs.kde.org/show_bug.cgi?id=370310 Bug ID: 370310 Summary: I can't type Chinese characters, and whenever I use multi-line the software crashes. Product: krita Version: 3.0.1 Platform: Other OS: MS Windows Status: UNCONFIRMED Severity: crash Priority: NOR Component: Text Tool Assignee: krita-bugs-n...@kde.org Reporter: ceriumlithiumsod...@gmail.com I use Bopomofo input for Traditional Chinese typing. The word selections doesn't show up so effectively, I can't type in it. I'm using the Traditional Chinese version of Krita already. This is for when I'm using the Artistic Text tool. I can click on the Multi-line text tool option but when I try to type on actual canvas, a pop-up appears saying "Runtime error". Reproducible: Always Steps to Reproduce: 1. Switch Keyboard to Microsoft Bopomofo, Pinyin input method 2. Open Krita canvas 3. Select Multi-line Text tool / Artistic Text Tool 4. Click on canvas to start writing Actual Results: MULTI-LINE A pop-up appears: "Runtime error" Program shuts down. Can be reopened, everything else works perfectly except for the multi-line text tool. ARTISTIC The first word on the word selection panel is available but I can't select another word. Expected Results: MULTI-LINE Be able to write. ARTISTIC Be able to write and select from a drop-down menu of words. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370306] no option to show 12-hour time without displaying the AM/PM part
https://bugs.kde.org/show_bug.cgi?id=370306 --- Comment #2 from Aaron Wolf --- So, what's the actual solution? I wasn't suggesting my patch as the solution necessarily. I was wanting the problem addressed and just mentioned something that could possibly work. I don't care about my solution being accepted, but I want the issue resolved. Without removing the AM/PM part of 12-hour time, I can't have a readably large time in 12-hour numbers in a panel that is on the left or right side of the screen! -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 366264] Was doing upgrade in Plasma DIscover
https://bugs.kde.org/show_bug.cgi?id=366264 Alexander Potashev changed: What|Removed |Added CC||aspotas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 367883] Discovery crashes on start
https://bugs.kde.org/show_bug.cgi?id=367883 Alexander Potashev changed: What|Removed |Added CC||aspotas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 364837] High CPU usage when kdenlive window is on top
https://bugs.kde.org/show_bug.cgi?id=364837 --- Comment #16 from BobSCA --- Wegwerf, I am not familiar with Qt and don't know if there has been a Qt upgrade. Is there something specific you would like me to check? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370296] Update the KDE widget plasma-applet-socketsentry package (Plasma 4 widget) to the Plasma 5 widget
https://bugs.kde.org/show_bug.cgi?id=370296 Rog131 changed: What|Removed |Added CC||samrog...@hotmail.com --- Comment #1 from Rog131 --- (In reply to Macxi from comment #0) > Update the KDE widget plasma-applet-socketsentry package (Plasma 4 widget) > to the Plasma 5 widget > > This widget is very useful to show the connections of your machine to the > network in real time. > Socket Sentry is a KDE Plasma widget that displays real-time networktraffic > > Reproducible: Always It is a 3rd party plasmoid and not part of the KDE. Please report the problem to its author via https://code.google.com/p/socket-sentry/ . -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 369317] Kwin crash with gles
https://bugs.kde.org/show_bug.cgi?id=369317
Martin Gräßlin changed:
What|Removed |Added
Resolution|--- |UPSTREAM
Status|UNCONFIRMED |RESOLVED
--- Comment #9 from Martin Gräßlin ---
I just had a look at the implementation and alas our code does the correct
checks - see libkwineffects/kwinglutils.cpp method GLVertexBuffer::initStatic
(around like 2290)
In short it's:
if (GLPlatform::instance()->isGLES()) {
GLVertexBufferPrivate::haveSyncFences = hasGLVersion(3, 0);
} else {
GLVertexBufferPrivate::haveSyncFences = hasGLVersion(3, 2) ||
hasGLExtension("GL_ARB_sync");
}
if (GLVertexBufferPrivate::haveBufferStorage &&
GLVertexBufferPrivate::haveSyncFences) {
if (qgetenv("KWIN_PERSISTENT_VBO") != QByteArrayLiteral("0")) {
GLVertexBufferPrivate::streamingBuffer->d->persistent = true;
}
}
Only if the d->persistent is true the glFenceSync is called. Thus the checks
look correct to me. We check for either GLES 3.0, or GL 3.2 or GL_ARB_sync. Our
code cannot do more. If the upstream project is broken in that regard, it's
unfortunate. I guess we need to get distros to switch to the fork.
Ah I'm not happy with that development. That was kind of what I was afraid of
to happen when we switch to epoxy.
--
You are receiving this mail because:
You are watching all bug changes.
[kdenlive] [Bug 364837] High CPU usage when kdenlive window is on top
https://bugs.kde.org/show_bug.cgi?id=364837 --- Comment #15 from Jean-Baptiste Mardelle --- Some update about this: The Qt-bug is not fixed: https://bugreports.qt.io/browse/QTBUG-54676 But I pushed a workaround in master so it shouldn't be a problem anymore. The KDE Frameworks bug is still not fixed despite my patch proposal, I just pinged the Frameworks maintainer: https://git.reviewboard.kde.org/r/128421/ So it still causes CPU usage and prevents going to sleep. I hope we can find a solution for KDE Framewors 5.28. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370143] Desktop Settings doesn't save changes after logout
https://bugs.kde.org/show_bug.cgi?id=370143 Aaron Wolf changed: What|Removed |Added CC||wolft...@gmail.com --- Comment #1 from Aaron Wolf --- confirmed as having the issue here -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 370271] Quickbooks Support Phone Number 1844-722-6675
https://bugs.kde.org/show_bug.cgi?id=370271 Toni Asensi Esteve changed: What|Removed |Added CC||toni.ase...@kdemail.net Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 370309] New: Idle Crash
https://bugs.kde.org/show_bug.cgi?id=370309 Bug ID: 370309 Summary: Idle Crash Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: bugs.kde@queuemail.com Application: kdeinit5 (16.08.1) Qt Version: 5.6.1 Frameworks Version: 5.26.0 Operating System: Linux 4.7.5-200.fc24.x86_64 x86_64 Distribution: "Fedora release 24 (Twenty Four)" -- Information about the crash: - What I was doing when the application crashed: just idling on a few remote servers. had multiple tabs open. multiple windows on different desktops as well. -- Backtrace: Application: Konsole (kdeinit5), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc7fbd27900 (LWP 13608))] Thread 3 (Thread 0x7fc7d7118700 (LWP 13610)): #0 0x7fc7f92a23ed in poll () at /lib64/libc.so.6 #1 0x7fc7f7968a06 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7fc7f7968b1c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7fc7fa0a824b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7fc7fa0575ea in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7fc7f9eb6343 in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7fc7fbde3559 in QDBusConnectionManager::run() () at /lib64/libQt5DBus.so.5 #7 0x7fc7f9eba99a in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #8 0x7fc7f8af15ca in start_thread () at /lib64/libpthread.so.0 #9 0x7fc7f92adf6d in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7fc7dcf5e700 (LWP 13609)): #0 0x7fc7f92a23ed in poll () at /lib64/libc.so.6 #1 0x7fc7fb06ef80 in _xcb_conn_wait () at /lib64/libxcb.so.1 #2 0x7fc7fb070b79 in xcb_wait_for_event () at /lib64/libxcb.so.1 #3 0x7fc7e0b1eda9 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5 #4 0x7fc7f9eba99a in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #5 0x7fc7f8af15ca in start_thread () at /lib64/libpthread.so.0 #6 0x7fc7f92adf6d in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7fc7fbd27900 (LWP 13608)): [KCrash Handler] #6 0x7fc7f91df6f5 in raise () at /lib64/libc.so.6 #7 0x7fc7f91e12fa in abort () at /lib64/libc.so.6 #8 0x7fc7f9ea6471 in () at /lib64/libQt5Core.so.5 #9 0x7fc7fbdef28d in QDBusConnectionPrivate::deliverCall(QObject*, int, QDBusMessage const&, QVector const&, int) () at /lib64/libQt5DBus.so.5 #10 0x7fc7fa081bd9 in QObject::event(QEvent*) () at /lib64/libQt5Core.so.5 #11 0x7fc7fa8ebc0c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #12 0x7fc7fa8f10ef in QApplication::notify(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #13 0x7fc7fa0587aa in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #14 0x7fc7fa05a84f in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /lib64/libQt5Core.so.5 #15 0x7fc7fa0a81b3 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () at /lib64/libQt5Core.so.5 #16 0x7fc7f79686ba in g_main_context_dispatch () at /lib64/libglib-2.0.so.0 #17 0x7fc7f7968a70 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #18 0x7fc7f7968b1c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #19 0x7fc7fa0a822f in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #20 0x7fc7fa0575ea in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #21 0x7fc7fa05f17c in QCoreApplication::exec() () at /lib64/libQt5Core.so.5 #22 0x7fc7e9ba0a23 in kdemain () at /usr/lib64/libkdeinit5_konsole.so #23 0x5577006b9f37 in launch(int, char const*, char const*, char const*, int, char const*, bool, char const*, bool, char const*) () #24 0x5577006bb0e7 in handle_launcher_request(int, char const*) [clone .isra.26] () #25 0x5577006bb9f7 in handle_requests(int) () #26 0x5577006b69ce in main () Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370308] New: plasma crashes on startup!
https://bugs.kde.org/show_bug.cgi?id=370308 Bug ID: 370308 Summary: plasma crashes on startup! 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: marce...@ceschia.de 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: 1) What I was doing when the application crashed: -stating KDE and it crashed 2) Unusual behavior I noticed: - no backound image loaded 3) environment: nvidia driver 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 0x7f8bb58257c0 (LWP 3189))] Thread 8 (Thread 0x7f8af14e4700 (LWP 3597)): #0 0x7f8baed1fbfd in poll () from /lib64/libc.so.6 #1 0x7f8bab3fce64 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f8bab3fcf7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f8baf64cd8b in QEventDispatcherGlib::processEvents (this=0x7f8aec0008f0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7f8baf5f3d53 in QEventLoop::exec (this=this@entry=0x7f8af14e3d10, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7f8baf41561a in QThread::exec (this=) at thread/qthread.cpp:503 #6 0x7f8af2b30cf7 in KCupsConnection::run() () from /usr/lib64/libkcupslib.so #7 0x7f8baf41a32f in QThreadPrivate::start (arg=0x280c4b0) at thread/qthread_unix.cpp:331 #8 0x7f8baa843754 in ?? () from /usr/X11R6/lib64/libGL.so.1 #9 0x7f8bae5290a4 in start_thread () from /lib64/libpthread.so.0 #10 0x7f8baed2802d in clone () from /lib64/libc.so.6 Thread 7 (Thread 0x7f8afbb47700 (LWP 3409)): #0 0x7f8baed1fbfd in poll () from /lib64/libc.so.6 #1 0x7f8bab3fce64 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f8bab3fcf7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f8baf64cd8b in QEventDispatcherGlib::processEvents (this=0x7f8af40008f0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7f8baf5f3d53 in QEventLoop::exec (this=this@entry=0x7f8afbb46cf0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7f8baf41561a in QThread::exec (this=this@entry=0x1ea6e40) at thread/qthread.cpp:503 #6 0x7f8bb32c5282 in QQuickPixmapReader::run (this=0x1ea6e40) at /usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/quick/util/qquickpixmapcache.cpp:760 #7 0x7f8baf41a32f in QThreadPrivate::start (arg=0x1ea6e40) at thread/qthread_unix.cpp:331 #8 0x7f8baa843754 in ?? () from /usr/X11R6/lib64/libGL.so.1 #9 0x7f8bae5290a4 in start_thread () from /lib64/libpthread.so.0 #10 0x7f8baed2802d in clone () from /lib64/libc.so.6 Thread 6 (Thread 0x7f8b83678700 (LWP 3249)): #0 0x7f8bae52d03f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f8bb4ef886b in ?? () from /usr/lib64/libQt5Script.so.5 #2 0x7f8bb4ef8899 in ?? () from /usr/lib64/libQt5Script.so.5 #3 0x7f8baa843754 in ?? () from /usr/X11R6/lib64/libGL.so.1 #4 0x7f8bae5290a4 in start_thread () from /lib64/libpthread.so.0 #5 0x7f8baed2802d in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7f8b89124700 (LWP 3225)): #0 0x7f8bab3fc538 in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #1 0x7f8bab3fcd80 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f8bab3fcf7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f8baf64cd8b in QEventDispatcherGlib::processEvents (this=0x7f8b7c0008f0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7f8baf5f3d53 in QEventLoop::exec (this=this@entry=0x7f8b89123d30, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7f8baf41561a in QThread::exec (this=this@entry=0x1755f20) at thread/qthread.cpp:503 #6 0x7f8bb2729e18 in QQmlThreadPrivate::run (this=0x1755f20) at /usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/qml/ftw/qqmlthread.cpp:141 #7 0x7f8baf41a32f in QThreadPrivate::start (arg=0x1755f20) at thread/qthread_unix.cpp:331 #8 0x7f8baa843754 in ?? () from /usr/X11R6/lib64/libGL.so.1 #9 0x7f8bae5290a4 in start_thread () from /lib64/libpthread.so.0 #10 0x7f8baed2802d in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f8b8a95d700 (LWP 3222)): #0 0x7f8baa83d769 in ?? () from /usr/X11R6/lib64/libGL.so.1 #1 0x7f8baa842766 in ?? () from /usr/X11R6/lib64/libGL.so.1 #2 0x7f8ba6edfbf7 in ?? () from /usr/lib64/tls/libnvidia-tls.so.304.132 #3 0x7f8bab43db60 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7f8ba
[kstars] [Bug 370307] kstars crash after starting an automated ekos session
https://bugs.kde.org/show_bug.cgi?id=370307 --- Comment #1 from Jasem Mutlaq --- Backtrace shows you were trying to solve an image using the online solver? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 370298] Slider behaviour, e.g. in 'local contrast'
https://bugs.kde.org/show_bug.cgi?id=370298 Maik Qualmann changed: What|Removed |Added Ever confirmed|0 |1 CC||metzping...@gmail.com Status|UNCONFIRMED |CONFIRMED --- Comment #1 from Maik Qualmann --- Yes, confirmed. It works well with the Breeze Style. But with the Fusion style it is useless. I will rework the sliders. Maik -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 364837] High CPU usage when kdenlive window is on top
https://bugs.kde.org/show_bug.cgi?id=364837 --- Comment #14 from Wegwerf --- As this is an Qt issue, did you see an Qt upgrade in the meantime? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 364837] High CPU usage when kdenlive window is on top
https://bugs.kde.org/show_bug.cgi?id=364837 --- Comment #13 from BobSCA --- I did an upgrade from the kdenlive-master ppa and found there was no change in CPU usage. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 370301] Auto grouping of any program windows does not work
https://bugs.kde.org/show_bug.cgi?id=370301 Martin Gräßlin changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #4 from Martin Gräßlin --- window grouping is currently not supported. We should hide the UI elements till we get support for it again. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 370307] New: kstars crash after starting an automated ekos session
https://bugs.kde.org/show_bug.cgi?id=370307 Bug ID: 370307 Summary: kstars crash after starting an automated ekos session Product: kstars Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: sebastien.lecler...@gmail.com Application: kstars (2.6.0) Qt Version: 5.5.1 Operating System: Linux 4.2.0-35-generic x86_64 Distribution: Ubuntu 16.04.1 LTS -- Information about the crash: - What I was doing when the application crashed: Starts Kstars, then ekos. Load a session and start it. Crash begin when I moved the planetarium. -- Backtrace: Application: KStars (kstars), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa927a9e8c0 (LWP 9055))] Thread 3 (Thread 0x7fa8f372c700 (LWP 9087)): #0 0x7fa9256e555d in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fa91fae2740 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fa91fa9ee84 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fa91fa9f340 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fa91fa9f4ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fa9241d4a9b in QEventDispatcherGlib::processEvents (this=0x7fa8ec01e790, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #6 0x7fa92417bdea in QEventLoop::exec (this=this@entry=0x7fa8f372bd00, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #7 0x7fa923f988a4 in QThread::exec (this=) at thread/qthread.cpp:503 #8 0x7fa923f9d84e in QThreadPrivate::start (arg=0x90ccb00) at thread/qthread_unix.cpp:331 #9 0x7fa9256dc6fa in start_thread (arg=0x7fa8f372c700) at pthread_create.c:333 #10 0x7fa922e5bb5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7fa913e43700 (LWP 9056)): #0 0x7fa922e4fe8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fa91d904c62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7fa91d9068d7 in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7fa916195629 in QXcbEventReader::run (this=0x280e3c0) at qxcbconnection.cpp:1253 #4 0x7fa923f9d84e in QThreadPrivate::start (arg=0x280e3c0) at thread/qthread_unix.cpp:331 #5 0x7fa9256dc6fa in start_thread (arg=0x7fa913e43700) at pthread_create.c:333 #6 0x7fa922e5bb5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7fa927a9e8c0 (LWP 9055)): [KCrash Handler] #6 0x7fa9241b34de in QObject::connect (sender=sender@entry=0x8e1e7c0, signal=signal@entry=0x7fa925fe4ea3 "2opened()", receiver=receiver@entry=0x133e9840, method=method@entry=0x7fa925fe4e88 "2networkSessionConnected()", type=type@entry=Qt::QueuedConnection) at kernel/qobject.cpp:2625 #7 0x7fa925f3457d in QNetworkAccessManagerPrivate::createSession (this=this@entry=0x13713f80, config=...) at access/qnetworkaccessmanager.cpp:1592 #8 0x7fa925f37e22 in QNetworkAccessManager::createRequest (this=0x133e9840, op=QNetworkAccessManager::PostOperation, req=..., outgoingData=0x140da530) at access/qnetworkaccessmanager.cpp:1179 #9 0x7fa925f332b5 in QNetworkAccessManager::post (this=this@entry=0x133e9840, request=..., data=data@entry=0x140da530) at access/qnetworkaccessmanager.cpp:737 #10 0x7fa925f33321 in QNetworkAccessManager::post (this=0x133e9840, request=..., data=...) at access/qnetworkaccessmanager.cpp:752 #11 0x00782009 in Ekos::OnlineAstrometryParser::authenticate() () #12 0x00786668 in Ekos::OnlineAstrometryParser::startSovler(QString const&, QStringList const&, bool) () #13 0x007676e8 in Ekos::Align::startSolving(QString const&, bool) () #14 0x00767c32 in Ekos::Align::setCaptureComplete() () #15 0x00768180 in Ekos::Align::newFITS(IBLOB*) () #16 0x006766ec in ?? () #17 0x7fa9241acfca in QMetaObject::activate (sender=0x13045b00, signalOffset=, local_signal_index=, argv=) at kernel/qobject.cpp:3713 #18 0x00668992 in ISD::GDInterface::BLOBUpdated(IBLOB*) () #19 0x006b81f8 in ISD::CCD::processBLOB(IBLOB*) () #20 0x006af350 in INDIListener::processBLOB(IBLOB*) () #21 0x00676fd4 in ?? () #22 0x7fa9241adea1 in QObject::event (this=0x86dd9e0, e=) at kernel/qobject.cpp:1239 #23 0x7fa924f5a05c in QApplicationPrivate::notify_helper (this=this@entry=0x27f66f0, receiver=receiver@entry=0x86dd9e0, e=e@entry=0x7fa8e003bf40) at kernel/qapplication.cpp:3716 #24 0x7fa924f5f516 in QApplication::notify (this=0x7fff0709abd0, receiver=0x86dd9e0, e=0x7fa8e003bf40) at kernel/qapplication.cpp:3499 #25 0x7fa92417e62b in QCoreApplication::notifyInternal (this=0x7fff0709abd0, receiver=0
[digikam] [Bug 364258] 4.x application configuration rc files are ignored [patch]
https://bugs.kde.org/show_bug.cgi?id=364258 Paul changed: What|Removed |Added CC||pip@gmx.com --- Comment #27 from Paul --- I've just migrated from digiKam 4.x to 5.2.0 on an openSUSE Tumbleweed system. There appears to be a problem if 'digikamimagewindowui.rc' is copied during the ~/.kde4/share/apps/digikam/ to ~/.local/share/digikam/ migration. It results in the (digiKam) Image Editor losing from the Main Menu the sub-menu entries for: 'Colour', 'Enhance', 'Decorate', and 'Effects'. Please see this topic on the openSUSE user forum: https://forums.opensuse.org/showthread.php/520361-DigiKam-5-2-0-Image-Editor-missing-a-lot-of-functions -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 368515] Kmail crashing some time after start
https://bugs.kde.org/show_bug.cgi?id=368515 Wolfgang Bauer changed: What|Removed |Added CC||wba...@tmo.at --- Comment #5 from Wolfgang Bauer --- It is a bug in nouveau, nouveau doesn't like multi-threading, see also bug#369514. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 368302] Crash when reverting action with split audio
https://bugs.kde.org/show_bug.cgi?id=368302 Wegwerf changed: What|Removed |Added CC||wegwerf-1-...@gmx.de --- Comment #3 from Wegwerf --- I cannot reproduce. When I manually split, then ungroup, then play around, and finally undo, everything works as expected. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 364833] Crash when adding .wtv (Windows Media Center) clip.
https://bugs.kde.org/show_bug.cgi?id=364833 Wegwerf changed: What|Removed |Added CC||wegwerf-1-...@gmx.de --- Comment #3 from Wegwerf --- So I'm seeing the same crash, and the crash happens inside consumer_read_ahead_thread of mlt_consumer. Despite melt playing the same clip fine, I suspect this to be an upstream MLT issue nevertheless. However, I might be wrong here. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 370287] Crash rotating image taken with Casio camera
https://bugs.kde.org/show_bug.cgi?id=370287 --- Comment #4 from Miquel --- Thanks Gilles, but the buf is solved in exiv2, I posted in the middle of the first comment: *** But googling around Ive found this bug (Crash in exiv2 due to assertion when setting rating on jpg with a Casio makernote): http://dev.exiv2.org/issues/1106 I'm using Ubuntu Gnome 16.04 with the packages provided by Philip Johnsson, and I had not installed exiv2. So I tried to install it: $ sudo apt-get install exiv2 $ exiv2 --version exiv2 0.25 001900 (64 bit build) Copyright (C) 2004-2015 Andreas Huggel. and restarted digikam. Now it's working fine! *** So maybe it's the internal exiv2 version that Digikam uses? Before installing exiv2 I got this error (virtual Exiv2::Internal::TiffComponent*) : *** digikam5: tiffcomposite.cpp:749: virtual Exiv2::Internal::TiffComponent* Exiv2::Internal::TiffMnEntry::doAddPath(uint16_t, Exiv2::Internal::TiffPath&, Exiv2::Internal::TiffComponent*, Exiv2::Internal::TiffComponent::AutoPtr): L’asserció «mn_» ha fallat. *** and after installing the package I got no errors, just an ignored warning message: *** digikam.metaengine: Exiv2 ( 2 ) : Directory Casio2 has an unexpected next pointer; ignored. *** Miquel Coll -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 369058] Kenlive crashing when files are imported
https://bugs.kde.org/show_bug.cgi?id=369058 Wegwerf changed: What|Removed |Added Resolution|--- |UPSTREAM Status|CONFIRMED |RESOLVED --- Comment #16 from Wegwerf --- Thank you very much for providing the example clip. I can add it to a project, and play it back, without any problems. This is on Kubuntu 16.04LTS with recent updates, and Kdenlive/MLT from git master Kdenlive ppa repository. So this clearly is not an Kdenlive issue, but a distribution issue, and thus upstream. Unfortunately, there is nothing we can do about it. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 369505] Audio and video clips randomly moves in the timeline after mysterius duplication of clips.
https://bugs.kde.org/show_bug.cgi?id=369505 Wegwerf changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO CC||wegwerf-1-...@gmx.de --- Comment #1 from Wegwerf --- Emanual, this kind of bug is ugly, and as I experienced it myself I can understand your sentiment. In order to track down such timeline corruption issues, we need a (minimized) example project, together with a concise description of the steps required to reproduce. There is no other way we can help you. I know from experience, as I sent in several such bug reports over time, where only the clear step list together with an example project helped the developers to fix those bugs. Thank you very much for your cooperation! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 366646] Rendering window should calculate and display estimated output size
https://bugs.kde.org/show_bug.cgi?id=366646 --- Comment #2 from anewuser --- I see. That's unfortunate. -- You are receiving this mail because: You are watching all bug changes.
