[opensuse-factory] I think they found the solution! [Re: Bug 431880 closed as duplicate of 431542 - which is marked as private]
On Mon, Oct 6, 2008 at 4:42 PM, Hans-Peter Holler
We need a compatible "solution" for this, not singing a big cry. Sorry, yes: solution is needed, but no: without crying you will reach nothing. Hope: aj, cthiel, maybe coolo.
I reported 434541[1], which is a duplicate of 433553 [2]. 433553 is marked private.
------- Comment #1 From JP Rosevear 2008-10-15 10:18:38 MDT ------- Dupe of 433553, but can't be duped.
Now my question is, was the ability to duplicate for a private bug disabled, or is this just a new policy? I don't understand what has to be so secret about the volume keys on a laptop. Pressing a key generates an event, which simply needs to be tacked on to the current OSD function that is already present. [1] https://bugzilla.novell.com/show_bug.cgi?id=434541 [2] https://bugzilla.novell.com/show_bug.cgi?id=433553 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Wednesday 15 October 2008 09:31:29 am Andrew Joakimsen wrote:
On Mon, Oct 6, 2008 at 4:42 PM, Hans-Peter Holler
wrote: We need a compatible "solution" for this, not singing a big cry.
Sorry, yes: solution is needed, but no: without crying you will reach nothing. Hope: aj, cthiel, maybe coolo.
I reported 434541[1], which is a duplicate of 433553 [2]. 433553 is marked private.
------- Comment #1 From JP Rosevear 2008-10-15 10:18:38 MDT ------- Dupe of 433553, but can't be duped.
Now my question is, was the ability to duplicate for a private bug disabled, or is this just a new policy? I don't understand what has to be so secret about the volume keys on a laptop. Pressing a key generates an event, which simply needs to be tacked on to the current OSD function that is already present.
[1] https://bugzilla.novell.com/show_bug.cgi?id=434541 [2] https://bugzilla.novell.com/show_bug.cgi?id=433553
What I don't get is why they didn't ask the guy any more information regarding Desktop environment, etc etc. I know in KDE4 it doesn't work, but in 3.5 it does. I'd imagine it works in GNOME also. KDE4 seems to pick up the wrong master volume device for me. Ben -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
I reported 434541[1], which is a duplicate of 433553 [2]. 433553 is marked private.
------- Comment #1 From JP Rosevear 2008-10-15 10:18:38 MDT ------- Dupe of 433553, but can't be duped.
Now my question is, was the ability to duplicate for a private bug disabled, or is this just a new policy? Yes, seems to be a new policy. See https://bugzilla.novell.com/show_bug.cgi?id=435214#c5 and https://bugzilla.novell.com/show_bug.cgi?id=435214#c6 I don't understand what has to be so secret about the volume keys on a laptop. Pressing a key generates an event, which simply needs to be tacked on to the current OSD function that is already present. It's not the bug content. It's the way SLE-bugs are created: non-public. And when those meet public ones you need a clever bugzilla, a clever bug assignee and a well known policy.
The only thing we can do is to cry every time such a accident happens. Hans-Peter -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Wed, 2008-10-15 at 21:03 +0200, Hans-Peter Holler wrote:
I reported 434541[1], which is a duplicate of 433553 [2]. 433553 is marked private.
------- Comment #1 From JP Rosevear 2008-10-15 10:18:38 MDT ------- Dupe of 433553, but can't be duped.
Now my question is, was the ability to duplicate for a private bug disabled, or is this just a new policy? Yes, seems to be a new policy. See https://bugzilla.novell.com/show_bug.cgi?id=435214#c5 and https://bugzilla.novell.com/show_bug.cgi?id=435214#c6 I don't understand what has to be so secret about the volume keys on a laptop. Pressing a key generates an event, which simply needs to be tacked on to the current OSD function that is already present. It's not the bug content. It's the way SLE-bugs are created: non-public. And when those meet public ones you need a clever bugzilla, a clever bug assignee and a well known policy.
Actually it is the content, I have opened SLE bugs in the past, but
can't if it contains information from a customer.
I also dupe the SLE bug on the openSUSE bug if the openSUSE bug has more
information (did maybe 5-10 this way last week). However in this case
investigation already began in the SLE bug before the openSUSE one was
reported, so we arrived at an awkward circumstance. I kept the other
one open not wanting to dupe it to something the reporter couldn't read,
not a perfect solution of course, but hopefully reduces the issues.
-JP
--
JP Rosevear
* JP Rosevear
I also dupe the SLE bug on the openSUSE bug if the openSUSE bug has more information (did maybe 5-10 this way last week). However in this case investigation already began in the SLE bug before the openSUSE one was reported, so we arrived at an awkward circumstance. I kept the other one open not wanting to dupe it to something the reporter couldn't read, not a perfect solution of course, but hopefully reduces the issues.
why not supercede the *private* but with the open report and reference both in each? Then close the private report as superceded. -- Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://counter.li.org -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
participants (5)
-
Andrew Joakimsen
-
Ben Kevan
-
Hans-Peter Holler
-
JP Rosevear
-
Patrick Shanahan