Bug 417632 - Please fix this on-going bug as stated in multiple reports! Thanks
Summary: Please fix this on-going bug as stated in multiple reports! Thanks
Status: RESOLVED NOT A BUG
Alias: None
Product: yakuake
Classification: Applications
Component: general (show other bugs)
Version: 3.0.5
Platform: Other Linux
: NOR major
Target Milestone: ---
Assignee: Eike Hein
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-02-14 12:58 UTC by Gregory Ernest
Modified: 2020-02-14 22:16 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
attachment-6892-0.html (2.58 KB, text/html)
2020-02-14 21:13 UTC, Gregory Ernest
Details
attachment-8181-0.html (1.34 KB, text/html)
2020-02-14 21:41 UTC, Gregory Ernest
Details
attachment-8940-0.html (2.66 KB, text/html)
2020-02-14 22:07 UTC, Gregory Ernest
Details
attachment-9126-0.html (1.17 KB, text/html)
2020-02-14 22:16 UTC, Gregory Ernest
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Gregory Ernest 2020-02-14 12:58:30 UTC
SUMMARY
As stated in multiple bug reports,despite of default setting unchanged by me.You have 3 other reports to look at plus a screen shot to show the problem!Is there somthing that I need to do? I have tryed patiently to show and describe in detail what the problem was. This concern may not effect all others but it still is a problem for me. 

STEPS TO REPRODUCE
1. Automatic on it's own. Usually at startup or reboot.
2. I change nothing from default settings, in Manjaro KDE
3. 

OBSERVED RESULT
corrected by going into KDE's ,  system settings>display configuration and changing the resolution from 3840x2160 to 4096x2160 and back again, this needs to be done after each reboot or shutdown! 

EXPECTED RESULT
Manjaro default setting,s in center of screen! Stable!

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 5.18
(available in About System)
KDE Plasma Version:5.18 
KDE Frameworks Version:5.67 
Qt Version: 5.18.1

ADDITIONAL INFORMATIONI Have provided as I stated very detailed reports with no reponse on your end. What is the problem? This has been an issue that I have reported again and agin with no response whatsoever. I appreciate that you are busy ,but come on at least respond to the issue to me by email that it is being taken seriously! If you need anymore details, which I would think not, but if you do please take monemt and email me. Thank you for toing whay you do;
Comment 1 Nate Graham 2020-02-14 20:20:04 UTC
Fix what? I don't see where in this bug report that it's mentioned what you want fixed. :) Did you file other bug reports? Can you clarify what problem you're referring to?
Comment 2 Gregory Ernest 2020-02-14 21:13:15 UTC
Created attachment 126039 [details]
attachment-6892-0.html

Sir I have filed multiple bug reports have given much detail in each have
sent a screenshot with one of them have done it now 4x.
I clarified the information 4x like I said look up the previous times I
filed. You getting all upset does nothing to help the situation. I have not
done anything or asked anything other then looking into the issue i made
perfectly clear 4x,s over the last year at least. With each update of your
program I have been anxious to see if it was addressed! Do not accuse me of
not filing reports that you if you look will and should be connected to my
e-mail account. Again look at all the previous reports filed compile it and
lets see if it can be resolved . Like i stated if there is more information
that you require, I will do my best to get that to you. But frankly you
seem disturbed about this issue without looking into the previous reports.
I do no there are many other things you would rather be doing but, the
reports are quite complete, and speak for themselves. And don't be a hater!

You have a blessed and relaxing day;

Gregory Ernest RN ,BSN

On Fri, Feb 14, 2020 at 3:20 PM Nate Graham <bugzilla_noreply@kde.org>
wrote:

> https://bugs.kde.org/show_bug.cgi?id=417632
>
> Nate Graham <nate@kde.org> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>          Resolution|---                         |WAITINGFORINFO
>              Status|REPORTED                    |NEEDSINFO
>                  CC|                            |nate@kde.org
>
> --- Comment #1 from Nate Graham <nate@kde.org> ---
> Fix what? I don't see where in this bug report that it's mentioned what you
> want fixed. :) Did you file other bug reports? Can you clarify what problem
> you're referring to?
>
> --
> You are receiving this mail because:
> You reported the bug.
Comment 3 Nate Graham 2020-02-14 21:28:40 UTC
I don't know what those bug reports are though. Can you please provide a link to one of them so I can take a look?
Comment 4 Christoph Feck 2020-02-14 21:31:24 UTC
Nate, check here: https://bugs.kde.org/buglist.cgi?email1=EMAIL&emailreporter1=1

replace EMAIL with Gregorys full email address.
Comment 5 Nicolás Alvarez 2020-02-14 21:33:39 UTC
Then this bug should be closed. The actual bug is already reported in those other issues, and this issue adds zero new information. It's just noise.
Comment 6 Christoph Feck 2020-02-14 21:37:08 UTC
I was about to close this, but reading the description of this ticket, it doesn't mention Yakuake, but speaks of changing screen resolutions generally. Confusing.
Comment 7 Gregory Ernest 2020-02-14 21:41:59 UTC
Created attachment 126042 [details]
attachment-8181-0.html

I will provide you with the bug report numbers generated at the time I sent
them: They will be listed below:
415021
415184
416091
417632
Hope this is enough information , please let me know how I can help further.

Have a blessed , quiet stress free day!

Gregory Ernest, RN,BSN


On Fri, Feb 14, 2020 at 4:31 PM Christoph Feck <bugzilla_noreply@kde.org>
wrote:

> https://bugs.kde.org/show_bug.cgi?id=417632
>
> --- Comment #4 from Christoph Feck <cfeck@kde.org> ---
> Nate, check here:
> https://bugs.kde.org/buglist.cgi?email1=EMAIL&emailreporter1=1
>
> replace EMAIL with Gregorys full email address.
>
> --
> You are receiving this mail because:
> You reported the bug.
Comment 8 Nate Graham 2020-02-14 21:45:05 UTC
Thanks!

You don't need to a file a new bug asking us to fix other bugs. :)

Looks like Bug 416090 and Bug 413003 are already fixed, so I assume the issue you were referring to was Bug 415184.

As you have probably noticed, Yakuake development is not very active right now. Would you be interested in submitting a patch to fix the issue?
Comment 9 Gregory Ernest 2020-02-14 22:07:47 UTC
Created attachment 126045 [details]
attachment-8940-0.html

They are all the same issue has been from the start. Never had a problem
until changing from Samsung TV to Toshiba TV. that is when it started. In
one of my bug reports I pointed that out and gave the model # and other
information about this TV. It is a Fire TV I purchased from Amazon, I use
HDMI, and agin it has only occurred with the TV model. Don't have a clue
why, though sending bug reports after each update to Yakuake would be the
fix, but no , it has remained an issue. I also took a screenshot if it can
be found of what I am talking about? Don't know if it is there or not but
can get another if desired. What ever I an supply I will do my darn best to
help you guys out. I hold no bias against any of you. you are overworked
and under paid that is just the facts of the matter. No matter what you
decide I can adjust. Just let me know. I do not know how to summit a patch,
I am a Nurse? Sorry not much I think I can do there, unless you provide me
good instructions on how to do it. I will try hard.

Please have a great weekend, I am fine doing what I am doing to get it to
function.

Gregory Ernest RN,BSN

On Fri, Feb 14, 2020 at 4:45 PM Nate Graham <bugzilla_noreply@kde.org>
wrote:

> https://bugs.kde.org/show_bug.cgi?id=417632
>
> Nate Graham <nate@kde.org> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>              Status|NEEDSINFO                   |RESOLVED
>          Resolution|WAITINGFORINFO              |NOT A BUG
>
> --- Comment #8 from Nate Graham <nate@kde.org> ---
> Thanks!
>
> You don't need to a file a new bug asking us to fix other bugs. :)
>
> Looks like Bug 416090 and Bug 413003 are already fixed, so I assume the
> issue
> you were referring to was Bug 415184.
>
> As you have probably noticed, Yakuake development is not very active right
> now.
> Would you be interested in submitting a patch to fix the issue?
>
> --
> You are receiving this mail because:
> You reported the bug.
Comment 10 Nicolás Alvarez 2020-02-14 22:11:06 UTC
We're not "underpaid", we're volunteers working for free, when we have free time to do so.

Please don't send new bug reports for the same thing if, as you say yourself, it's still the *same* issue.
Comment 11 Gregory Ernest 2020-02-14 22:16:26 UTC
Created attachment 126046 [details]
attachment-9126-0.html

Sorry first time bug reporter! Won't happen again , I promise you.
Sorry you have to volunteer and seem to get little satisfaction from that.
But that is honorable thing to do!

On Fri, Feb 14, 2020 at 5:11 PM Nicolás Alvarez <bugzilla_noreply@kde.org>
wrote:

> https://bugs.kde.org/show_bug.cgi?id=417632
>
> --- Comment #10 from Nicolás Alvarez <nicolas.alvarez@gmail.com> ---
> We're not "underpaid", we're volunteers working for free, when we have free
> time to do so.
>
> Please don't send new bug reports for the same thing if, as you say
> yourself,
> it's still the *same* issue.
>
> --
> You are receiving this mail because:
> You reported the bug.