Thanks Jonathan!
For https://bugs.kde.org/enter_bug.cgi?product=ksysguard it's currently
possible to pick from a longer list of versions, e.g. 4.12.0, 5.0.0. Is
this intended?
Regarding reporting bugs in unsupported versions via bugs.kde.org, it might
be frustrating not a find a version
then mentioning the version in the bug report text.
> >
> > Will it be possible to change version number to an older version after
> > the report has been created?
>
> You can always do that when using bugs.kde.org directly. The discussion
> in question only really concerns
go are mostly useless
> duplicates.
>
> Does that seem sane?
>
> Nate
>
>
>
> On 9/9/21 9:27 AM, Jonathan Riddell wrote:
> > I've started marking old versions of plasma products in bugs.kde.org
> > <http://bugs.kde.org> as not active, this means you can
in the bug report text.
Will it be possible to change version number to an older version after
the report has been created?
You can always do that when using bugs.kde.org directly. The discussion
in question only really concerns filing automatic crash reports from
DrKonqi, as it will now preven
On Fri, Sep 10, 2021 at 10:18 AM Alexander Potashev
wrote:
>
> Hi,
>
> If someone wants to report a bug against an older version, what would you
> suggest and/or expect them to do?
First reproduce it on a supported version?
Hi,
If someone wants to report a bug against an older version, what would you
suggest and/or expect them to do?
I can imagine I would still report bugs while setting version number to
"unspecified" and then mentioning the version in the bug report text.
Will it be possible to change version numb
On Thu, Sep 9, 2021 at 4:41 PM Nate Graham wrote:
>
> I would recommend considering the following releases active:
>
> - Current released Plasma release + all of its bugfix releases
> - Previous Plasma release (last bugfix version only)
> - Latest LTS Plasma release (last bugfix version only)
>
>
ns of plasma products in bugs.kde.org
<http://bugs.kde.org> as not active, this means you can't report new
bugs on them. In 5.23 drkonqi will then refuse to file crash reports
and ask the user to upgrade when a version is not marked active. Which
versions should I mark active? Th
I've started marking old versions of plasma products in bugs.kde.org as not
active, this means you can't report new bugs on them. In 5.23 drkonqi will
then refuse to file crash reports and ask the user to upgrade when a
version is not marked active. Which versions should I mark ac
I felt that thing sneaked in release and was very disappointed about that.
so if it really must exist (and is asking for troubles on so many
fronts) it should at least be forced to use bugs.kde.org
On Wed, Mar 3, 2021 at 1:07 PM David Redondo wrote:
>
> Hi,
>
> I think when the gitl
Hi,
I think when the gitlab migration happened, it was agreed that bug tracking
still happens on bugs.kde.org and gitlab issues will eventually replace
phabricator tasks.
The readme of qqc2-breeze-style includes:
> # Bug Reports/Feature Requests/Issues:
>
>File your reports/requ
https://bugs.kde.org/show_bug.cgi?id=429576
Nate Graham changed:
What|Removed |Added
Resolution|WAITINGFORINFO |FIXED
CC
https://bugs.kde.org/show_bug.cgi?id=429576
Ben Cooksley changed:
What|Removed |Added
CC||bcooks...@kde.org
bport created this revision.
bport added reviewers: Plasma, ngraham, apol.
Herald added a project: Plasma.
Herald added a subscriber: plasma-devel.
bport requested review of this revision.
TEST PLAN
Try installing using plasma-changeicons executable (used by discover) and
from discover directly
dy of the summary, no need to write "Resolves
https://bugs.kde.org/show_bug.cgi?id=377994.";, but simply add a line with:
BUG: 377994
which will do the magic when/if the commit is pushed.
REPOSITORY
R102 KInfoCenter
REVISION DETAIL
https://phabricator.kde.org/D5471
To: ngra
anthonyfieroni added a reviewer: Plasma.
REPOSITORY
R102 KInfoCenter
REVISION DETAIL
https://phabricator.kde.org/D5471
To: ngraham, #plasma
Cc: plasma-devel, spstarr, progwolff, lesliezhai, ali-mohamed, jensreuterberg,
abetts, sebas, apol
ngraham created this revision.
Restricted Application added a project: Plasma.
Restricted Application added a subscriber: plasma-devel.
REVISION SUMMARY
Makes `/usr/bin/plasmashell --version` the canonical source of truth for the
Plasma version. Resolves https://bugs.kde.org/show_bug.cgi?id
abondrov added a comment.
In https://phabricator.kde.org/D2283#42745, @mart wrote:
> can you add the BT to that report?
Surely. I added it earlier today.
REVISION DETAIL
https://phabricator.kde.org/D2283
EMAIL PREFERENCES
https://phabricator.kde.org/settings/panel/emailprefer
art with second panel added and crash
BT info provided. Bug report: https://bugs.kde.org/show_bug.cgi?id=366146
can you add the BT to that report?
REVISION DETAIL
https://phabricator.kde.org/D2283
EMAIL PREFERENCES
https://phabricator.kde.org/settings/panel/emailpreferences/
To: mart,
ivan requested changes to this revision.
ivan added a reviewer: ivan.
ivan added a comment.
This revision now requires changes to proceed.
Cool :)
@mart
Can you close this review?
REVISION DETAIL
https://phabricator.kde.org/D2283
EMAIL PREFERENCES
https://phabricator.kde.org/set
mart abandoned this revision.
REVISION DETAIL
https://phabricator.kde.org/D2283
EMAIL PREFERENCES
https://phabricator.kde.org/settings/panel/emailpreferences/
To: mart, #plasma, ivan
Cc: ivan, abondrov, davidedmundson, plasma-devel, jensreuterberg, abetts, sebas
_
these changes. I'll close
the bug ( https://bugs.kde.org/show_bug.cgi?id=365989 ). Thanx again for fixing
it.
REVISION DETAIL
https://phabricator.kde.org/D2283
EMAIL PREFERENCES
https://phabricator.kde.org/settings/panel/emailpreferences/
To: mart, #plasma
Cc: ivan, abondrov, davidedmun
ted Plasma crash which is easy to
reproduce. Download the ISO, install it (or boot in live mode) and try to add
second panel. Plasma will crash, then restart with second panel added and crash
BT info provided. Bug report: https://bugs.kde.org/show_bug.cgi?id=366146
REVISION DETAIL
https://phabri
abondrov added a comment.
@ivan, @mart
> Since you are really helpful and active, I have a couple of things for you
to test :) (please do not kill me)
I'll test it tomorrow. It takes some time to build patched plasma-workspace
package and then build ISO with it.
Thanx for worki
mart added a comment.
so, the patch is in, you can have a defaults file in the rosa lnf that has
the following:
[Desktop][org.kde.plasma.desktop]
Containment=org.kde.plasma.folder
REVISION DETAIL
https://phabricator.kde.org/D2283
EMAIL PREFERENCES
https://phabricator.kde.org/setti
ivan added a comment.
p.s. The step `4` will be made a bit different with Marco's upcoming patch,
but it is the only way ATM to set the default containment plugin.
REVISION DETAIL
https://phabricator.kde.org/D2283
EMAIL PREFERENCES
https://phabricator.kde.org/settings/panel/emailpreferen
ivan added a comment.
@abondrov
Yes, it is a backport of a patch that will be reverted once we deal with 5.7
stuff. We didn't put it in 5.7 branch because it is not really a good patch -
it was supposed to cover the cases when kactivitymanagerd is not installed, but
we need kactivityman
ivan added a comment.
@abondrov
Since you are really helpful and active, I have a couple of things for you to
test :) (please do not kill me)
1. Remove david's patch backported from master (the one that checks against
kamd status being Unknown -
`plasma-workspace-5.7.2-layout-initi
abondrov added a comment.
In https://phabricator.kde.org/D2283#42598, @ivan wrote:
> This one needs to go away, along with making kactivitymanagerd a hard
runtime requirement:
>
> >
https://abf.rosalinux.ru/import/plasma5-workspace/blob/rosa2014.1/plasma-workspace-5.7.2-layout-initia
ivan added a comment.
@abondrov
Thanks.
This one needs to go away, along with making kactivitymanagerd a hard runtime
requirement:
>
https://abf.rosalinux.ru/import/plasma5-workspace/blob/rosa2014.1/plasma-workspace-5.7.2-layout-initialization-2.patch
The load-order one is
abondrov added a comment.
In https://phabricator.kde.org/D2283#42565, @ivan wrote:
> @abondrov
>
> Have you applied any patch other than this one to plasma? Another question,
do you have a repository of what changes your distro is doing during packaging
- maybe we are missing somethi
ivan added a comment.
@mart
The reason why this change fixes the scripting problem I'm working on is that
loadLayout actually calls loadDefaultLayout and this tells the scripting engine
which activities exist, and which are present. That is why adding this above
loadLayout was working t
ivan added a comment.
@abondrov
Have you applied any patch other than this one to plasma? I'm asking since
neither Marco nor I can replicate this on our systems (with empty-config users)
Another question, do you have a repository of what changes your distro is
doing during packaging
abondrov added a comment.
> I have no idea whatsoever, i'm just reporting a patch that the distro
maintainer says it's working, but I don't know why. putting it there to discuss
and trying to understand
It's working because with this patch Plasma doesn't try to delete the
activity it's
mart added a comment.
In https://phabricator.kde.org/D2283#42518, @davidedmundson wrote:
> Why?
I have no idea whatsoever, i'm just reporting a patch that the distro
maintainer says it's working, but I don't know why. putting it there to discuss
and trying to understand
REVISION
mart removed rPLASMAWORKSPACE Plasma Workspace as the repository for this
revision.
mart updated this revision to Diff 5494.
CHANGES SINCE LAST UPDATE
https://phabricator.kde.org/D2283?vs=5491&id=5494
REVISION DETAIL
https://phabricator.kde.org/D2283
AFFECTED FILES
shell/shellcorona.cpp
davidedmundson added a comment.
Why?
REPOSITORY
rPLASMAWORKSPACE Plasma Workspace
REVISION DETAIL
https://phabricator.kde.org/D2283
EMAIL PREFERENCES
https://phabricator.kde.org/settings/panel/emailpreferences/
To: mart, #plasma
Cc: davidedmundson, plasma-devel, jensreuterberg, abetts
://bugs.kde.org/show_bug.cgi?id=365989
REPOSITORY
rPLASMAWORKSPACE Plasma Workspace
REVISION DETAIL
https://phabricator.kde.org/D2283
AFFECTED FILES
"plasma-workspace-5.7.2-pat\321\201hed/shell/shellcorona.cpp"
EMAIL PREFERENCES
https://phabricator.kde.org/settings/panel/emailpreferences/
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/103597/#review9447
---
This review has been submitted with commit
81a13227ed20badd036b
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/103597/#review9431
---
Ship it!
that's a very good catch ;)
yes, that's the way it's s
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/103597/
---
(Updated Dec. 31, 2011, 7:27 a.m.)
Review request for Plasma.
Descriptio
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/103597/
---
Review request for Plasma.
Description
---
For some reason, QGraphics
---
The patch fix/workaround this bug https://bugs.kde.org/show_bug.cgi?id=200981 .
I've added a new slot called existingContainmentAdded in plasmapp.cpp, is
almost like containmentAdded slot but the new one doesn't add the actions.
Then, I've had to create a new signal in corona (k
https://bugs.kde.org/show_bug.cgi?id=200981 .
I've added a new slot called existingContainmentAdded in plasmapp.cpp, is
almost like containmentAdded slot but the new one doesn't add the actions.
Then, I've had to create a new signal in corona (kdelibs) desired to be emmited
when an a
just as a friendly reminder ...
... today i figured i'd had a good enough break from bugs.kde.org to not puke
when i looked at the plasma list ;) the 4.2 bug squashing effort was
monumental indeed, but i figured i was ready for another spin at the wheel.
well ... 551 open reports greet
45 matches
Mail list logo
