[KDE Bugtracking System] REMINDER: current Plasma regressions

Please find below a list of the current regressions reported for Plasma. This is a weekly reminder. This search was scheduled by myr...@kde.org. Plasma regressions -- Bug 202336: https://bugs.kde.org/show_bug.cgi?id=202336 Priority: NOR Severity: normal Platform: Gentoo

Re: Re: reflecting on 4.10

On Saturday 12 January 2013 18:45:07 Aaron J. Seigo wrote: > we have 3 repositories which probably should target 4.11: > > * kscreen (playground/base/) > * libkscreen (playground/libs/) > * kio_mtp (playground/base/) > > they have a few things in common: > > * they are all worked on by Alex F. :

Re: Re: Re: reflecting on 4.10

On Saturday 12 January 2013 19:13:29 Martin Gräßlin wrote: > On Saturday 12 January 2013 18:45:07 Aaron J. Seigo wrote: > > if they are targetted for 4.11 (or some future release even?) we'll need > > to > > figure out how to deal with these separate repos. do they end up merged > > into kde-worksp

Re: Re: reflecting on 4.10

On Saturday 12 January 2013 18:54:23 Aaron J. Seigo wrote: > On Saturday, January 12, 2013 18:29:22 Alex Fiestas wrote: > > In the recent past, we have had people giving "ship it" in reviewboard to > > code that was not maintained by them and what is worst modifications that > > broke (or still bre

Re: Re: reflecting on 4.10

On Saturday 12 January 2013 18:54:23 Aaron J. Seigo wrote: > so i'd like to see *more* reviewboard input rather than less. it would be totally awesome if more people would do reviews outside their normal "teritory". E.g. me doing more reviews of Plasma stuff, but also Plasma people doing more re

Re: Re: Review Request: various fix for battery plasmoid

On Saturday 12 January 2013 00:53:10 Xuetian Weng wrote: > > On Jan. 12, 2013, 12:18 a.m., Kai Uwe Broulik wrote: > > > plasma/generic/applets/batterymonitor/contents/code/logic.js, line 97 > > > > > ine97>> > > > > But

Re: Re: reflecting on 4.10

On Saturday 12 January 2013 18:45:07 Aaron J. Seigo wrote: > if they are targetted for 4.11 (or some future release even?) we'll need to > figure out how to deal with these separate repos. do they end up merged into > kde-workspace? do we put them as "child" repos of kde-workspace and rely on > kde

Re: Review Request 108316: Show album art in krunner results.

--- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/108316/#review25310 --- This review has been submitted with commit f74729bd26caff383ad

Re: reflecting on 4.10

On Saturday, January 12, 2013 18:29:22 Alex Fiestas wrote: > In the recent past, we have had people giving "ship it" in reviewboard to > code that was not maintained by them and what is worst modifications that > broke (or still breaks) stuff, we should prevent this from happening. we already gene

Re: reflecting on 4.10

On Saturday, January 12, 2013 18:14:21 Marco Martin wrote: > On Saturday 12 January 2013, Kevin Ottens wrote: > > > actually, i care :) i rather suspected this was the case, given the > > > number of developers i've heard this same kind of story from. the reason > > > for moving to packages varies,

Re: Re: reflecting on 4.10

On Saturday 12 January 2013 17:57:37 Aaron J. Seigo wrote: > On Saturday, January 12, 2013 17:38:03 Marco Martin wrote: > > wonder how much scales for something as big as the kde-workspace repo... > > my experience with plasma-mobile seems to indicate that it is easily done by > one person. i woul

Re: Review Request 107983: Fix KWindowSystem::compositingChanged signal

--- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/107983/#review25307 --- After several days test, so far no problem here. - Xuetian Wen

Re: reflecting on 4.10

On Saturday 12 January 2013, Kevin Ottens wrote: > > actually, i care :) i rather suspected this was the case, given the > > number of developers i've heard this same kind of story from. the reason > > for moving to packages varies, but fewer KDE devs run master than > > probably ever before. it se

Re: reflecting on 4.10

On Saturday, January 12, 2013 17:38:03 Marco Martin wrote: > wonder how much scales for something as big as the kde-workspace repo... my experience with plasma-mobile seems to indicate that it is easily done by one person. i wouldn't want to see one person doing all of kdelibs, kde- runtime, kde-

Re: reflecting on 4.10

On Saturday 12 January 2013 17:36:01 Aaron J. Seigo wrote: > On Saturday, January 12, 2013 16:00:10 Kevin Ottens wrote: > > As already pointed out, this should be a set of people not a single one. > > a bus number greater than 1 is important, but i also think the realities of > doing this job limit

Re: reflecting on 4.10

On Saturday 12 January 2013, Marco Martin wrote: > > yep, it works well on plasma-mobile (and yeah, needs *one* person,first > weeks of it we tried it done by more than one person and uuuh, nope ;)) > > wonder how much scales for something as big as the kde-workspace repo... > coulb be person a r

Re: Review Request 108316: Show album art in krunner results.

--- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/108316/#review25305 --- Ship it! couple minor comments below, but looks ready to be sh

Re: reflecting on 4.10

On Saturday 12 January 2013, Aaron J. Seigo wrote: > * when branches are merged into master (because they've passed whatever > testing set out as required) i send an email to the list noting what has > been merged into master and what is still being merged into integration > > as we don't have for

Re: reflecting on 4.10

On Saturday, January 12, 2013 16:00:10 Kevin Ottens wrote: > As already pointed out, this should be a set of people not a single one. a bus number greater than 1 is important, but i also think the realities of doing this job limits the number of people who can, will and even should be doing it.

Re: reflecting on 4.10

On Saturday, January 12, 2013 17:01:40 Alex Fiestas wrote: > This is my opinion now (no longer what I remember from the sprint). > > On Saturday 12 January 2013 15:54:39 Aaron J. Seigo wrote: > > On Saturday, January 12, 2013 14:08:44 Alex Fiestas wrote: > > > -Master > > > -Integration > > > > t

Re: Re: reflecting on 4.10

This is my opinion now (no longer what I remember from the sprint). On Saturday 12 January 2013 15:54:39 Aaron J. Seigo wrote: > On Saturday, January 12, 2013 14:08:44 Alex Fiestas wrote: > > -Master > > -Integration > > this is what we are doing now in plasma-mobile. it has taken a bit to get >

Re: Review Request 108316: Show album art in krunner results.

> On Jan. 12, 2013, 1:18 a.m., Christoph Feck wrote: > > Regarding the QPixmap thread warning, there is a auxiliary icon engine > > somewhere in the contacts runner, which uses passes QImage data around. > > QImage can be used outside the UI thread. Thank you Christoph. It's not throwing warni

Re: Review Request 108316: Show album art in krunner results.

--- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/108316/ --- (Updated Jan. 12, 2013, 3:46 p.m.) Review request for Plasma. Changes --

Re: Review Request: Show album art in krunner results.

> On Jan. 10, 2013, 10:09 p.m., Aaron J. Seigo wrote: > > very nice idea. > > > > as for the QPixmap error, one option is to do all the pixmap handling in > > the GUI thread by creating an object in the GUI thread and communicating > > with it via slots. the Places runner > > (kde-workspace/p

Re: New lockscreen

Il 10/01/2013 21:57, Aaron J. Seigo ha scritto: [...] disclaimer: i am not the maintainer of this component. i have contributed some minor things to its development. however, i'm obviously vested in the workspace in general. reverting is not going to happen at this point. but what i will do is s

Re: New lockscreen

On Friday 11 of January 2013 10:28:22 Martin Gräßlin wrote: > the implementation has been kept there AFAIK because people complain that we > wanted to remove it. It would be nice if the people who want to have the > old screen savers would step up to support the maintenance. Yes it would > have bee

Re: reflecting on 4.10

On Saturday, January 12, 2013 03:35:22 Christoph Feck wrote: > On Thursday 10 January 2013 22:05:28 Aaron J. Seigo wrote: > > what, if anything, would you like to be done differently in 4.11? > > We should honestly ask ourself, if we still take user feedback > seriously. If there is no maintainer

Re: reflecting on 4.10

On Friday 11 January 2013 22:58:49 Martin Gräßlin wrote: > Back in the days of early 4.x I did rebuild almost every day. To me it's a > sign that our software got better, I don't have the need to rebuild just to > get the latest bug fix and most components are so feature complete that I > don't nee

Re: reflecting on 4.10

On Friday 11 January 2013 17:26:39 Marco Martin wrote: > On Friday 11 January 2013, Marco Martin wrote: > > On Thursday 10 January 2013, Aaron J. Seigo wrote: > > > hello. > > > > > > we're nearly at the point of releasing 4.10. with this development cycle > > > very fresh in mind, it is a reasonbl

Re: Review Request 108355: various fix for battery plasmoid

> On Jan. 12, 2013, 12:18 a.m., Kai Uwe Broulik wrote: > > plasma/generic/applets/batterymonitor/contents/code/logic.js, line 97 > > > > > > But isn't it the dataengine that prematurely triggers a brightnes > > ch

Re: reflecting on 4.10

On Saturday, January 12, 2013 14:08:44 Alex Fiestas wrote: > -Master > -Integration this is what we are doing now in plasma-mobile. it has taken a bit to get used to (mostly for me doing the integration branch; we were already using branches heavily). i think it is working pretty well. i blogged

Re: reflecting on 4.10

On Friday 11 January 2013 13:08:03 Martin Gräßlin wrote: > My personal highlight is the menu in windeco, but that is so hidden, that I > don't expect users will find it. >From my perspective, it's not really a problem. It allows to have the feature maturing through the power users involvement firs

Re: Review Request 108355: various fix for battery plasmoid

--- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/108355/#review25293 --- This review has been submitted with commit 70ed17ef99dd33adda2

Re: Re: reflecting on 4.10

On Friday 11 January 2013 20:37:58 Aaron J. Seigo wrote: > On Friday, January 11, 2013 18:37:44 Alex Fiestas wrote: > > If we want to discuss this, we should start another thread for not going > > off topic. > > imho it's completely on topic. Very well then We talked about quality, reviews and pr

Re: Review Request 108355: various fix for battery plasmoid

> On Jan. 12, 2013, 12:18 a.m., Kai Uwe Broulik wrote: > > plasma/generic/applets/batterymonitor/contents/code/logic.js, line 97 > > > > > > But isn't it the dataengine that prematurely triggers a brightnes > > ch

Re: Review Request 108355: various fix for battery plasmoid

> On Jan. 12, 2013, 12:18 a.m., Kai Uwe Broulik wrote: > > plasma/generic/applets/batterymonitor/contents/code/logic.js, line 97 > > > > > > But isn't it the dataengine that prematurely triggers a brightnes > > ch

Re: Review Request 108355: various fix for battery plasmoid

--- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/108355/#review25275 --- Ship it! mostly looks good, other than a couple of coding styl

Re: reflecting on 4.10

On Friday, January 11, 2013 21:13:58 Mark wrote: > Why don't we use one of the sprints for this? i'd rather use in-person meetings for things that are difficult to do otherwise. testing really should not require being in person, and issues of design and things like large refactorings are extrem

Re: reflecting on 4.10

On Saturday 12 January 2013 08:36:52 Martin Gräßlin wrote: > > OpenSUSE has KDE:Unstable:SC which is made up of (regularly) updated > > snapshots of current git master. > > yes, but you cannot install it into a different directory AFAIK. It > overwrites your stable installation. Hi Martin, This

Re: reflecting on 4.10

In data sabato 12 gennaio 2013 08:36:52, Martin Gräßlin ha scritto: > yes, but you cannot install it into a different directory AFAIK. It > overwrites your stable installation. A few of the openSUSE community are working on live images based on current master (using the same repository). I plan o