[KDE Bugtracking System] REMINDER: current Plasma regressions
Please find below a list of the current regressions reported for Plasma This search was scheduled by myr...@kde.org. Plasma regressions -- Bug 291676: https://bugs.kde.org/show_bug.cgi?id=291676 Priority: NOR Severity: normal Platform: Gentoo Packages Assignee: plasma-b...@kde.org Status: NEW Summary: Device Items resize on hover due to visibility change of the status text Bug 300885: https://bugs.kde.org/show_bug.cgi?id=300885 Priority: NOR Severity: critical Platform: Ubuntu Packages Assignee: plasma-b...@kde.org Status: NEW Summary: Weather widget does not work anymore with bbcuk or wetter.com provider Bug 301424: https://bugs.kde.org/show_bug.cgi?id=301424 Priority: NOR Severity: normal Platform: openSUSE RPMs Assignee: plasma-b...@kde.org Status: NEW Summary: Cannot open battery monitor applet if set to hidden in systray Bug 301533: https://bugs.kde.org/show_bug.cgi?id=301533 Priority: NOR Severity: normal Platform: Other Assignee: plasma-b...@kde.org Status: NEW Summary: Option Show Multiple Batteries does nothing Bug 302331: https://bugs.kde.org/show_bug.cgi?id=302331 Priority: NOR Severity: normal Platform: Ubuntu Packages Assignee: ignat.seme...@blue-systems.com Status: UNCONFIRMED Summary: [post 4.9beta2] Folderview does not show any to activity linked files ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Review Request: change default config of taskmanager
On June 28, 2012, 4:57 p.m., Aaron J. Seigo wrote: Items= is no longer used. individual entries are. so this review is not correct. the prefered items are also indeed removable. that was fixed a while back. are you using kde-workspace from master or some older branch or...? Greg T wrote: ah, I see. Nope, I'm using plain master and that bug is definitely *not* fixed. The preferred filemanager and browser icons keep reappaering on login. The function GroupManagerPrivate::unsaveLauncher can't remove that config entrys because the name of the launcher is i.e. 'firefox' but never 'browser' well, I have updated the patch 1 week ago, +1/-1? :) - Greg --- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/105374/#review15230 --- On June 28, 2012, 7:03 p.m., Greg T wrote: --- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/105374/ --- (Updated June 28, 2012, 7:03 p.m.) Review request for Plasma. Description --- libtaskmanager can't remove those (browser, preferred://browser, , , ) entrys, so I moved them to the Items list. I don't know why they were separated in the first place. That's why I'm opening this review request. This addresses bug 278724. http://bugs.kde.org/show_bug.cgi?id=278724 Diffs - libs/taskmanager/groupmanager.cpp 5ca0159 Diff: http://git.reviewboard.kde.org/r/105374/diff/ Testing --- no regressions noted. Thanks, Greg T ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Please, if you port something to QML, make it at the very least exactly the same as the C++ version!
On Monday 09 July 2012, Mark wrote: Hi folks, I really have to stress this out. It annoys me to even see it since it seems so obvious (to me). When you port some GUI part of KDE from C++ to QML i would expect the porter to keep: - feature parity - visual parity - functional parity So, i just installed KDE 4.9 RC 1 with high hopes of QML in some places thus i happily started testing that. That's when i got some WTF No, you got to be joking! moments. may be better? yes. however this is not the right attitude at all to tackle it, it's not helping anyone. The first thing i tested out was the shutdown dialog which is in QML now. While it may have feature parity, it certainly lacks visual parity and probably some functional parity as well. The first thing i noticed was missing drop down shadows in corners. I leave the rest up to the bug reports i made for it: https://bugs.kde.org/show_bug.cgi?id=303216 just reproduces the old behavior https://bugs.kde.org/show_bug.cgi?id=303215 weird drivers issue, not really reproducible https://bugs.kde.org/show_bug.cgi?id=303214 fixed https://bugs.kde.org/show_bug.cgi?id=303213 old problem in the theme, not a regression, fixed now. Lets make KDE 4.9 rock solid! indeed -- Marco Martin ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Review Request: DrKonqi should report the crashes of kactivitymanagerd to the kactivities product in BKO
--- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/105483/ --- (Updated July 9, 2012, 12:27 p.m.) Review request for KDE Runtime, Plasma, Ivan Čukić, and George Kiagiadakis. Changes --- add plasma into groups Description (updated) --- There is now the kactivities product in BKO (corresponding to the kactivities repository where kactivitymanagerd lives) So I think DrKonqi should forward the crashes of kactivitymanagerd to the kactivies product. Diffs - drkonqi/data/mappings 147bcdc Diff: http://git.reviewboard.kde.org/r/105483/diff/ Testing --- Thanks, Jekyll Wu ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
master pushed to KDE/4.9
Hi, While I was trying to push my commit to KDE/4.9 after pushing to master, I landed pushing all of master to KDE/4.9 branch. I was asked to give a request for reverting this to the project's git maintainers. So can someone please look into this? My apologies for the inconvenience. Cheers, Viranch ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: master pushed to KDE/4.9
On Monday 09 July 2012, Viranch Mehta wrote: Hi, While I was trying to push my commit to KDE/4.9 after pushing to master, I landed pushing all of master to KDE/4.9 branch. I was asked to give a request for reverting this to the project's git maintainers. So can someone please look into this? My apologies for the inconvenience. Cheers, Viranch is it kde-workspace? did you do a merge of master into 4.9? seems there is a merge at 6e34d9b604240bda7d6ebdc46ff12470c8f17b9f -- Marco Martin ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Re: master pushed to KDE/4.9
On Monday 09 July 2012 22:29:59 Marco Martin wrote: On Monday 09 July 2012, Viranch Mehta wrote: Hi, While I was trying to push my commit to KDE/4.9 after pushing to master, I landed pushing all of master to KDE/4.9 branch. I was asked to give a request for reverting this to the project's git maintainers. So can someone please look into this? My apologies for the inconvenience. Cheers, Viranch is it kde-workspace? did you do a merge of master into 4.9? seems there is a merge at 6e34d9b604240bda7d6ebdc46ff12470c8f17b9f no that was my proper merge from 4.9 into master. If you look at git-gui it really looks like master got merged into 4.9 or look at http://quickgit.kde.org/index.php?p=kde- workspace.gita=commith=d7b04c0732c538957aa8a2bf9d53bd98a61eab13 which shows that this commit is currently HEAD of master and KDE/4.9 relevant part of IRC log: [21:35] xardas008 viranch: i think you need to merge it to your local KDE/4.9 branch first before you can push it [21:36] -- notmart has left this server (Quit: notmart terminated!). [21:38] viranch xardas008: git merge master? [21:38] xardas008 viranch: yes [21:39] xardas008 you need to call git checkout KDE/4.9 first [21:39] xardas008 and then the merge [21:39] mgraesslin NOOO [21:39] xardas008 not? [21:39] mgraesslin don't merge master into KDE/4.9 [21:39] -- faichele_ has left this server (Remote host closed the connection). [21:39] xardas008 ok :) [21:40] mgraesslin that would bring everything from master to 4.9 branch [21:40] mgraesslin the proper way would have been to first push to KDE/4.9 and then merge KDE/4.9 into master [21:40] viranch woah!!! [21:41] viranch did it just get pushed?! I still hope my git foo is completely wrong and there is no merge to master :-) Anyway, in case someone wants to fix it: https://condor- wiki.cs.wisc.edu/index.cgi/wiki?p=RevertingBadMerges short summary: just reverting the merge is not enough, won't work and will create even more mess. Probably the only real solution is either revert the individual commits or force push. Cheers Martin signature.asc Description: This is a digitally signed message part. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: kde-workspace KDE/4.9 broken
On Monday, July 09, 2012 22:55:46 Albert Astals Cid wrote: Someone merged master to KDE/4.9, no clue if anyone is working on fixing it, but just thought you'd want to know KDE/4.9 is broken, you probably don't want to commit there untils it's fixed. Fix is being worked on. -- sebas http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9 ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: kde-workspace KDE/4.9 broken
2012/7/9 Martin Klapetek martin.klape...@gmail.com: On Mon, Jul 9, 2012 at 10:55 PM, Albert Astals Cid aa...@kde.org wrote: Someone merged master to KDE/4.9, no clue if anyone is working on fixing it, but just thought you'd want to know KDE/4.9 is broken, you probably don't want to commit there untils it's fixed. Thanks for the info. There's a thread on plasma-devel about it, so they know and hopefully are on it to fix it asap. I have now reset KDE/4.9 to the right commit, removing the bad merge. If you already pulled 4.9 during the breakage, you will have to fix your local branch too, otherwise your next push will re-introduce the bad merge: - Make sure your current branch is KDE/4.9 (or whatever you call your local branch tracking KDE Workspace 4.9) and that you have no unpushed changes (whether they are committed locally or not). - Run git fetch to download from the server. - Run git reset --hard origin/KDE/4.9, to make your local 4.9 branch point at exactly the same commit as the now-fixed remote 4.9 branch. If you do have local changes on 4.9 that you don't want to lose, reply to this thread asking for help; I don't want to make this one post more complicated than it is :) -- Nicolás ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Review Request: Fix for microblog plasma applet not getting authenticated with a twitter account
--- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/105498/#review15594 --- This review has been submitted with commit 28f6d7cee7e81fda9ba396cc6477370a8ed3ada7 by Sebastian Kügler to branch master. - Commit Hook On July 9, 2012, 10:38 p.m., phoenix firebrd wrote: --- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/105498/ --- (Updated July 9, 2012, 10:38 p.m.) Review request for Plasma and Sebastian Kügler. Description --- The microblog plasma applet fails to authenticate with twitter and so the timeline is empty without the post. The problem is in the microblog dataengine in KOAuth::authorize, the user parameter is empty and it overwrites the username already present in d-user. The crash part of plasma-desktop only occurs when the ok button is pressed immediately after the apply button is pressed in the settings ui. This crash is not fixed in here. Only the twitter authentication part is fixed here. This addresses bug https://bugs.kde.org/show_bug.cgi?id=302267. http://bugs.kde.org/show_bug.cgi?id=https://bugs.kde.org/show_bug.cgi?id=302267 Diffs - dataengines/microblog/koauth.cpp 565d79f Diff: http://git.reviewboard.kde.org/r/105498/diff/ Testing --- Tested, twitter account gets aunthenticated and the twitts are displayed properly in the timeline. Thanks, phoenix firebrd ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
