[opensuse-support] /usr/lib/at-spi2/at-spi2-registryd - Extremely high CPU consuming!
Hello, Recently I noticed an extremely high CPU load with consequent abnormal CPU heating and then I discovered that the cause was /usr/lib/at-spi2/at-spi2-registryd attempting to execute an infinite series of tasks which were failing one after the other. Attempting to uninstall the at-spi2-core was not possible due the fact of hundreds of packages dependencies belong on this single package (reason not understandable by me). To workaround the issue I done: 1 - sudo chmod ugo-x /usr/lib/at-spi2/at-spi2-registryd 2 - sudo rm /usr/share/dbus-1/accessibility-services/org.a11y.atspi.Registry.service Thanks for your attention. Regards, -- Marco Calistri Build: openSUSE Tumbleweed 20191024 Kernel: 5.3.7-1-default - Cinnamon 3.8.9 -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 28/10/2019 16.18, Marco Calistri wrote:
Hello,
Recently I noticed an extremely high CPU load with consequent abnormal CPU heating and then I discovered that the cause was /usr/lib/at-spi2/at-spi2-registryd attempting to execute an infinite series of tasks which were failing one after the other.
Do you see coredumps? Execute first "coredumpctl", see if it produces a list of events that can be related to yours - the high cpu load is typically due to the compression of so many coredumps. Then have a look at the thread initiated by me: [opensuse] Hundreds of coredumps related to tracker in oS 15.1 The actions you need to do are the same. - -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXbclUAAKCRC1MxgcbY1H 1fqwAJ9leJb+Rlab4Kbzt3kRTkX5iLOwrgCeIKK1HU+aDDQHw/FXEX+IDsv/2jM= =sHcg -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
Il 28/10/19 14:28, Carlos E. R. ha scritto:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 28/10/2019 16.18, Marco Calistri wrote:
Hello,
Recently I noticed an extremely high CPU load with consequent abnormal CPU heating and then I discovered that the cause was /usr/lib/at-spi2/at-spi2-registryd attempting to execute an infinite series of tasks which were failing one after the other.
Do you see coredumps?
Execute first "coredumpctl", see if it produces a list of events that can be related to yours - the high cpu load is typically due to the compression of so many coredumps.
Then have a look at the thread initiated by me:
[opensuse] Hundreds of coredumps related to tracker in oS 15.1
The actions you need to do are the same.
- -- Cheers / Saludos,
Carlos E. R. (from 15.1 x86_64 at Telcontar)
Hi Carlos! I ran coredumpctl but I have not any coredumps on my system. After I disabled at-spi2-registryd the CPU load back to normal as well as CPU temp. --------------- sudo coredumpctl [sudo] password di root: No coredumps found. --------------- Thanks and regards, -- Marco Calistri Build: openSUSE Tumbleweed 20191024 Kernel: 5.3.7-1-default - Cinnamon 3.8.9 -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 28/10/2019 21.29, Marco Calistri wrote:
Il 28/10/19 14:28, Carlos E. R. ha scritto:
...
I ran coredumpctl but I have not any coredumps on my system. After I disabled at-spi2-registryd the CPU load back to normal as well as CPU temp.
Ok, that cures the issue, of course. But something else somewhere stops working.
--------------- sudo coredumpctl [sudo] password di root: No coredumps found. ---------------
A bit strange.
Thanks and regards,
You may consider reporting in Bugzilla, tough. - -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXbdR0gAKCRC1MxgcbY1H 1RoKAJ0Qw4msOaFDKDnakykDWjQJEQfCUQCcD3w58AEJRVTQ0u4yx155TVgqPQo= =b4cB -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
Il 28/10/19 17:38, Carlos E. R. ha scritto:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 28/10/2019 21.29, Marco Calistri wrote:
Il 28/10/19 14:28, Carlos E. R. ha scritto:
...
I ran coredumpctl but I have not any coredumps on my system. After I disabled at-spi2-registryd the CPU load back to normal as well as CPU temp.
Ok, that cures the issue, of course. But something else somewhere stops working.
--------------- sudo coredumpctl [sudo] password di root: No coredumps found. ---------------
A bit strange.
Thanks and regards,
You may consider reporting in Bugzilla, tough.
Well honestly I have opened two bugs not so much time ago and so far no I've not get any sort of feedback then I'm not so hopeful that opening a bug being so useful at the end.
- -- Cheers / Saludos,
Carlos E. R. (from 15.1 x86_64 at Telcontar)
Take care! Marco -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
* Marco Calistri <PY1ZRJ@outlook.com> [10-28-19 17:54]:
Il 28/10/19 17:38, Carlos E. R. ha scritto:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 28/10/2019 21.29, Marco Calistri wrote:
Il 28/10/19 14:28, Carlos E. R. ha scritto:
...
I ran coredumpctl but I have not any coredumps on my system. After I disabled at-spi2-registryd the CPU load back to normal as well as CPU temp.
Ok, that cures the issue, of course. But something else somewhere stops working.
--------------- sudo coredumpctl [sudo] password di root: No coredumps found. ---------------
A bit strange.
Thanks and regards,
You may consider reporting in Bugzilla, tough.
Well honestly I have opened two bugs not so much time ago and so far no I've not get any sort of feedback then I'm not so hopeful that opening a bug being so useful at the end.
the "bug" definitely will not be solved w/o someone stepping up to provide the solution and many will not even see the "bug" nor know about it w/o it being publicized. and the accepted way for publicizing is via a bug report. PLUS, it is your way of giving back to the community for the gigantic amount of work performed to provide you with your FREE operating system. but it is not a requirement nor an obligation for you to make a report. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
Op dinsdag 29 oktober 2019 01:28:51 CET schreef Patrick Shanahan:
the "bug" definitely will not be solved w/o someone stepping up to provide the solution and many will not even see the "bug" nor know about it w/o it being publicized. and the accepted way for publicizing is via a bug report. PLUS, it is your way of giving back to the community for the gigantic amount of work performed to provide you with your FREE operating system.
And not even providing the solution is needed. But for the rest: wisdom. -- Gertjan Lettink a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
Il 28/10/19 21:28, Patrick Shanahan ha scritto:
* Marco Calistri <PY1ZRJ@outlook.com> [10-28-19 17:54]:
Il 28/10/19 17:38, Carlos E. R. ha scritto:
You may consider reporting in Bugzilla, tough.
Well honestly I have opened two bugs not so much time ago and so far no I've not get any sort of feedback then I'm not so hopeful that opening a bug being so useful at the end.
the "bug" definitely will not be solved w/o someone stepping up to provide the solution and many will not even see the "bug" nor know about it w/o it being publicized. and the accepted way for publicizing is via a bug report. PLUS, it is your way of giving back to the community for the gigantic amount of work performed to provide you with your FREE operating system.
but it is not a requirement nor an obligation for you to make a report.
Yes I'm confident that the "good user", using an undoubtedly good O.S. as OpenSUSE for FREE, should open a bug report, but let's say I'm not so impulsed to do it, also because hopefully just to signalize a problem, IMHO a list like this one (opensuse-support) should be sufficient. I don't mean to resolve the issue, but at least to make it of public domain. Regards, -- Marco Calistri Build: openSUSE Tumbleweed 20191024 Kernel: 5.3.7-1-default - Cinnamon 3.8.9 -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
* Marco Calistri <PY1ZRJ@outlook.com> [10-29-19 08:53]:
Il 28/10/19 21:28, Patrick Shanahan ha scritto:
* Marco Calistri <PY1ZRJ@outlook.com> [10-28-19 17:54]:
Il 28/10/19 17:38, Carlos E. R. ha scritto:
You may consider reporting in Bugzilla, tough.
Well honestly I have opened two bugs not so much time ago and so far no I've not get any sort of feedback then I'm not so hopeful that opening a bug being so useful at the end.
the "bug" definitely will not be solved w/o someone stepping up to provide the solution and many will not even see the "bug" nor know about it w/o it being publicized. and the accepted way for publicizing is via a bug report. PLUS, it is your way of giving back to the community for the gigantic amount of work performed to provide you with your FREE operating system.
but it is not a requirement nor an obligation for you to make a report.
Yes I'm confident that the "good user", using an undoubtedly good O.S. as OpenSUSE for FREE, should open a bug report, but let's say I'm not so impulsed to do it, also because hopefully just to signalize a problem, IMHO a list like this one (opensuse-support) should be sufficient.
I don't mean to resolve the issue, but at least to make it of public domain.
so you delay the possible solution and provide others with anguish. while you could give back to the community which gives to you. and possibly exerted more effort on this list than required of a bug report. yes, the effort here is to con joule/shame/.... you into making a report. or maybe call it an effort to get you to become part of the community from which you request aid and explanation via this list. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 29/10/2019 14.04, Patrick Shanahan wrote:
* Marco Calistri <> [10-29-19 08:53]:
Il 28/10/19 21:28, Patrick Shanahan ha scritto:
* Marco Calistri <> [10-28-19 17:54]:
Il 28/10/19 17:38, Carlos E. R. ha scritto:
You may consider reporting in Bugzilla, tough.
Well honestly I have opened two bugs not so much time ago and so far no I've not get any sort of feedback then I'm not so hopeful that opening a bug being so useful at the end.
the "bug" definitely will not be solved w/o someone stepping up to provide the solution and many will not even see the "bug" nor know about it w/o it being publicized. and the accepted way for publicizing is via a bug report. PLUS, it is your way of giving back to the community for the gigantic amount of work performed to provide you with your FREE operating system.
but it is not a requirement nor an obligation for you to make a report.
Yes I'm confident that the "good user", using an undoubtedly good O.S. as OpenSUSE for FREE, should open a bug report, but let's say I'm not so impulsed to do it, also because hopefully just to signalize a problem, IMHO a list like this one (opensuse-support) should be sufficient.
I don't mean to resolve the issue, but at least to make it of public domain.
so you delay the possible solution and provide others with anguish. while you could give back to the community which gives to you. and possibly exerted more effort on this list than required of a bug report.
yes, the effort here is to con joule/shame/.... you into making a report. or maybe call it an effort to get you to become part of the community from which you request aid and explanation via this list.
Yes. But his experience has been that he reported things in Bugzilla and were ignored, eventually closed as "too old, install a newer distro release". So why bother, if it will be ignored as well? If we want people to fill bugzillas, someone has to at least read them once. - -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXbg7+QAKCRC1MxgcbY1H 1d+bAKCDi+GeBNCqrtgdAo0C1OxDShMrFQCfRgKwAEUhVuo4kYSrhDWmMMRyTY0= =dj/V -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
* Carlos E. R. <robin.listas@telefonica.net> [10-29-19 09:23]:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 29/10/2019 14.04, Patrick Shanahan wrote:
* Marco Calistri <> [10-29-19 08:53]:
Il 28/10/19 21:28, Patrick Shanahan ha scritto:
* Marco Calistri <> [10-28-19 17:54]:
Il 28/10/19 17:38, Carlos E. R. ha scritto:
You may consider reporting in Bugzilla, tough.
Well honestly I have opened two bugs not so much time ago and so far no I've not get any sort of feedback then I'm not so hopeful that opening a bug being so useful at the end.
the "bug" definitely will not be solved w/o someone stepping up to provide the solution and many will not even see the "bug" nor know about it w/o it being publicized. and the accepted way for publicizing is via a bug report. PLUS, it is your way of giving back to the community for the gigantic amount of work performed to provide you with your FREE operating system.
but it is not a requirement nor an obligation for you to make a report.
Yes I'm confident that the "good user", using an undoubtedly good O.S. as OpenSUSE for FREE, should open a bug report, but let's say I'm not so impulsed to do it, also because hopefully just to signalize a problem, IMHO a list like this one (opensuse-support) should be sufficient.
I don't mean to resolve the issue, but at least to make it of public domain.
so you delay the possible solution and provide others with anguish. while you could give back to the community which gives to you. and possibly exerted more effort on this list than required of a bug report.
yes, the effort here is to con joule/shame/.... you into making a report. or maybe call it an effort to get you to become part of the community from which you request aid and explanation via this list.
Yes. But his experience has been that he reported things in Bugzilla and were ignored, eventually closed as "too old, install a newer distro release". So why bother, if it will be ignored as well?
If we want people to fill bugzillas, someone has to at least read them once.
and if one assumes the attitude that no-one will read them, there will not be any bug reports and probably no openSUSE. but we digress and the topic is not being followed. and this forum is probably not best for discussing the impetus to read or not bug reports. bye -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 29/10/2019 14.27, Patrick Shanahan wrote:
* Carlos E. R. <> [10-29-19 09:23]:
On 29/10/2019 14.04, Patrick Shanahan wrote:
* Marco Calistri <> [10-29-19 08:53]:
Il 28/10/19 21:28, Patrick Shanahan ha scritto:
* Marco Calistri <> [10-28-19 17:54]:
Il 28/10/19 17:38, Carlos E. R. ha scritto:
> > You may consider reporting in Bugzilla, tough. > > Well honestly I have opened two bugs not so much time ago and so far no I've not get any sort of feedback then I'm not so hopeful that opening a bug being so useful at the end.
the "bug" definitely will not be solved w/o someone stepping up to provide the solution and many will not even see the "bug" nor know about it w/o it being publicized. and the accepted way for publicizing is via a bug report. PLUS, it is your way of giving back to the community for the gigantic amount of work performed to provide you with your FREE operating system.
but it is not a requirement nor an obligation for you to make a report.
Yes I'm confident that the "good user", using an undoubtedly good O.S. as OpenSUSE for FREE, should open a bug report, but let's say I'm not so impulsed to do it, also because hopefully just to signalize a problem, IMHO a list like this one (opensuse-support) should be sufficient.
I don't mean to resolve the issue, but at least to make it of public domain.
so you delay the possible solution and provide others with anguish. while you could give back to the community which gives to you. and possibly exerted more effort on this list than required of a bug report.
yes, the effort here is to con joule/shame/.... you into making a report. or maybe call it an effort to get you to become part of the community from which you request aid and explanation via this list.
Yes. But his experience has been that he reported things in Bugzilla and were ignored, eventually closed as "too old, install a newer distro release". So why bother, if it will be ignored as well?
If we want people to fill bugzillas, someone has to at least read them once.
and if one assumes the attitude that no-one will read them, there will not be any bug reports and probably no openSUSE.
but we digress and the topic is not being followed. and this forum is probably not best for discussing the impetus to read or not bug reports. bye
My point is that if there is a duty of users to report issues in bugzilla, others have the duty to read them. It goes both ways. We can not insist on users to report ("con joule/shame/...." as you say), the other part should do the same... why only "con joule/shame/...." users? But as you say, pointless. - -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXbg/oQAKCRC1MxgcbY1H 1Z1TAJ4lT2fJFUkb91LEzoJyVmLjuygxHwCfctobw9J5Lw/un69te3MmBBcjpZQ= =mm0K -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
Il 29/10/19 10:17, Carlos E. R. ha scritto:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 29/10/2019 14.04, Patrick Shanahan wrote:
* Marco Calistri <> [10-29-19 08:53]:
Il 28/10/19 21:28, Patrick Shanahan ha scritto:
* Marco Calistri <> [10-28-19 17:54]:
Il 28/10/19 17:38, Carlos E. R. ha scritto:
You may consider reporting in Bugzilla, tough.
Well honestly I have opened two bugs not so much time ago and so far no I've not get any sort of feedback then I'm not so hopeful that opening a bug being so useful at the end.
the "bug" definitely will not be solved w/o someone stepping up to provide the solution and many will not even see the "bug" nor know about it w/o it being publicized. and the accepted way for publicizing is via a bug report. PLUS, it is your way of giving back to the community for the gigantic amount of work performed to provide you with your FREE operating system.
but it is not a requirement nor an obligation for you to make a report.
Yes I'm confident that the "good user", using an undoubtedly good O.S. as OpenSUSE for FREE, should open a bug report, but let's say I'm not so impulsed to do it, also because hopefully just to signalize a problem, IMHO a list like this one (opensuse-support) should be sufficient.
I don't mean to resolve the issue, but at least to make it of public domain.
so you delay the possible solution and provide others with anguish. while you could give back to the community which gives to you. and possibly exerted more effort on this list than required of a bug report.
yes, the effort here is to con joule/shame/.... you into making a report. or maybe call it an effort to get you to become part of the community from which you request aid and explanation via this list.
Yes. But his experience has been that he reported things in Bugzilla and were ignored, eventually closed as "too old, install a newer distro release". So why bother, if it will be ignored as well?
If we want people to fill bugzillas, someone has to at least read them once.
- -- Cheers / Saludos,
Carlos E. R. (from 15.1 x86_64 at Telcontar)
Carlos, I appreciated your support on this topic. Bugzilla is useless if nobody keep checking the bug-report! -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
Hello, Am Dienstag, 29. Oktober 2019, 14:17:47 CET schrieb Carlos E. R.:
Yes. But his experience has been that he reported things in Bugzilla and were ignored, eventually closed as "too old, install a newer distro release". So why bother, if it will be ignored as well?
If we want people to fill bugzillas, someone has to at least read them once.
Looks like I have to dig out some bugzilla statistics ;-) Over the years, about half of the bugs get/got marked as fixed. The other half is still open or spread across various other resolutions (duplicate, worksforme, wontfix, noresponse etc.). The latest statistics more or less confirms this - from the bugs reported in 2018 (for both Leap and Tumbleweed), 2450 of 5300 bugs are fixed (46%), 1200 (23%) are still open, and the remainder is spread across other resolutions. So far, 4150 bugs were reported in 2019. It shouldn't be a surprise that more of them (1790 / 43%) are still open, but OTOH 1460 (35%) of them are already fixed. Given that this statistics even includes bugs reported today, that number isn't too bad. I know that some bugs get closed as "out of support", and ideally all our developers and packagers would have enough time to avoid this. Nevertheless, the number of these bugs is quite small in comparison to the number of reported bugs. I can't provide exact numbers because "wontfix" also includes bugs that were "manually" marked wontfix for other reasons. In numbers, 430 of the 5300 bugs reported in 2018 and 800 of 4980 bugs from 2017 are marked wontfix - and not all of them were marked as "out of support". To sum it up: not every bug gets fixed, but you roughly have a 50% chance when you report a bug. That's much better than the 0% chance when not reporting it! OTOH, feel free not to report bugs - that increases the chances that _my_ bugreports get handled and fixed ;-)) BTW: You can get alll these statistics yourself using the bugzilla "Reports" page - use "Resolution" for one of the axis, and then filter as you want (for example with a date range). Regards, Christian Boltz -- Ratti schrieb:
Ratti schrieb:
Ratti schrieb:
Bitte vollen Namen einsetzen. Da steht Ratti! Mach selber, Ratti. Das brauch mir keiner sagen, der hier als "Ratti" schreibt Genau! Gruß, Ratti. [Jörg Roßdeutscher aka Ratti in suse-linux]
-- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On Sat, 02 Nov 2019 22:31:05 +0100 Christian Boltz <opensuse@cboltz.de> wrote:
Hello,
Am Dienstag, 29. Oktober 2019, 14:17:47 CET schrieb Carlos E. R.:
Yes. But his experience has been that he reported things in Bugzilla and were ignored, eventually closed as "too old, install a newer distro release". So why bother, if it will be ignored as well?
If we want people to fill bugzillas, someone has to at least read them once.
Looks like I have to dig out some bugzilla statistics ;-)
Over the years, about half of the bugs get/got marked as fixed. The other half is still open or spread across various other resolutions (duplicate, worksforme, wontfix, noresponse etc.).
The latest statistics more or less confirms this - from the bugs reported in 2018 (for both Leap and Tumbleweed), 2450 of 5300 bugs are fixed (46%), 1200 (23%) are still open, and the remainder is spread across other resolutions.
So far, 4150 bugs were reported in 2019. It shouldn't be a surprise that more of them (1790 / 43%) are still open, but OTOH 1460 (35%) of them are already fixed. Given that this statistics even includes bugs reported today, that number isn't too bad.
I know that some bugs get closed as "out of support", and ideally all our developers and packagers would have enough time to avoid this. Nevertheless, the number of these bugs is quite small in comparison to the number of reported bugs. I can't provide exact numbers because "wontfix" also includes bugs that were "manually" marked wontfix for other reasons. In numbers, 430 of the 5300 bugs reported in 2018 and 800 of 4980 bugs from 2017 are marked wontfix - and not all of them were marked as "out of support".
To sum it up: not every bug gets fixed, but you roughly have a 50% chance when you report a bug. That's much better than the 0% chance when not reporting it!
OTOH, feel free not to report bugs - that increases the chances that _my_ bugreports get handled and fixed ;-))
BTW: You can get alll these statistics yourself using the bugzilla "Reports" page - use "Resolution" for one of the axis, and then filter as you want (for example with a date range).
Thanks for some facts, Christian.
Regards,
Christian Boltz
-- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 03/11/2019 12.09, Dave Howorth wrote:
On Sat, 02 Nov 2019 22:31:05 +0100 Christian Boltz <opensuse@cboltz.de> wrote:
...
BTW: You can get alll these statistics yourself using the bugzilla "Reports" page - use "Resolution" for one of the axis, and then filter as you want (for example with a date range).
Thanks for some facts, Christian.
I don't think those stats we can obtain cover the full image. For example, there are the bugs that don't get a reply for months (just the one from triage). Those that never get handled, get closed by a bot when the release is too old. - -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXb64+gAKCRC1MxgcbY1H 1akEAJ9qjVz4hRX/+3qt5dFJjytbR69emQCfWDxB8cB824kATf5gUNwKNh0po9g= =eCDz -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
Hello, Am Sonntag, 3. November 2019, 12:24:44 CET schrieb Carlos E. R.:
On 03/11/2019 12.09, Dave Howorth wrote:
On Sat, 02 Nov 2019 22:31:05 +0100 Christian Boltz wrote: ...
BTW: You can get alll these statistics yourself using the bugzilla "Reports" page - use "Resolution" for one of the axis, and then filter as you want (for example with a date range).
Thanks for some facts, Christian.
I don't think those stats we can obtain cover the full image. For example, there are the bugs that don't get a reply for months (just the one from triage). Those that never get handled, get closed by a bot when the release is too old.
Yes, I know, and - like everybody - I don't like this, and know that it can be demotivating. "At least" the number of bugs that suffer from this problem is not too big. They are part of the "wontfix" bugs, and (as I already mentioned in my previous mail), the amount of wontfix is quite small: - 430 of 5300 bugs reported in 2018 - 800 of 4980 bugs reported in 2017 Now compare that to 2450 (in 2018) and 2460 (in 2017) bugs that were fixed... Note that "wontfix" gets also used if a developer decides not to fix a bug (for whatever reason), so the actual number of bugs that get closed because a release gets out of support is smaller. (Unfortunately, filtering that out isn't easy (you'd have to check the bug comments), therefore I don't have exact numbers.) Even if you assume that all the 800 wontfix bugs from 2017 were closed as "out of support" (which is a wrong and too pessimistic assumption), the chance to get your bug fixed is still 3 times bigger ;-) Regards, Christian Boltz -- Wenn ein Fussel, will man ihn vom Boden aufheben, sich von alleine aus dem Staub macht, ist das kein Grund zur Freude, sondern eine Spinne. [Tina Wirtz auf www.titanic-magazin.de/fachmann/2015/mai/] -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
Thank you Christian, I appreciate the data included and general trends given. It is good to see that the state of the project is not declining, at least not rapidly. There are always different opinions - like: "but things are much worse or better than presented". That is the natural state of statistical trends - there are always lower/higher percentiles. The important question is what we/I can do about making thing better. For most of us users - filing good and reproducible bug reports, and timely and constructively responding to responses is probably the easiest practical difference we can make. Thanks again for the info, Tomas On Sun, 2019-11-03 at 13:21 +0100, Christian Boltz wrote:
Hello,
Am Sonntag, 3. November 2019, 12:24:44 CET schrieb Carlos E. R.:
On 03/11/2019 12.09, Dave Howorth wrote:
On Sat, 02 Nov 2019 22:31:05 +0100 Christian Boltz wrote:
...
BTW: You can get alll these statistics yourself using the bugzilla "Reports" page - use "Resolution" for one of the axis, and then filter as you want (for example with a date range).
Thanks for some facts, Christian.
I don't think those stats we can obtain cover the full image. For example, there are the bugs that don't get a reply for months (just the one from triage). Those that never get handled, get closed by a bot when the release is too old.
Yes, I know, and - like everybody - I don't like this, and know that it can be demotivating. "At least" the number of bugs that suffer from this problem is not too big. They are part of the "wontfix" bugs, and (as I already mentioned in my previous mail), the amount of wontfix is quite small: - 430 of 5300 bugs reported in 2018 - 800 of 4980 bugs reported in 2017
Now compare that to 2450 (in 2018) and 2460 (in 2017) bugs that were fixed...
Note that "wontfix" gets also used if a developer decides not to fix a bug (for whatever reason), so the actual number of bugs that get closed because a release gets out of support is smaller. (Unfortunately, filtering that out isn't easy (you'd have to check the bug comments), therefore I don't have exact numbers.)
Even if you assume that all the 800 wontfix bugs from 2017 were closed as "out of support" (which is a wrong and too pessimistic assumption), the chance to get your bug fixed is still 3 times bigger ;-)
Regards,
Christian Boltz -- Wenn ein Fussel, will man ihn vom Boden aufheben, sich von alleine aus dem Staub macht, ist das kein Grund zur Freude, sondern eine Spinne. [Tina Wirtz auf www.titanic-magazin.de/fachmann/2015/mai/]
-- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
Il 29/10/19 10:04, Patrick Shanahan ha scritto:
* Marco Calistri <PY1ZRJ@outlook.com> [10-29-19 08:53]:
Il 28/10/19 21:28, Patrick Shanahan ha scritto:
* Marco Calistri <PY1ZRJ@outlook.com> [10-28-19 17:54]:
Il 28/10/19 17:38, Carlos E. R. ha scritto:
You may consider reporting in Bugzilla, tough.
Well honestly I have opened two bugs not so much time ago and so far no I've not get any sort of feedback then I'm not so hopeful that opening a bug being so useful at the end.
the "bug" definitely will not be solved w/o someone stepping up to provide the solution and many will not even see the "bug" nor know about it w/o it being publicized. and the accepted way for publicizing is via a bug report. PLUS, it is your way of giving back to the community for the gigantic amount of work performed to provide you with your FREE operating system.
but it is not a requirement nor an obligation for you to make a report.
Yes I'm confident that the "good user", using an undoubtedly good O.S. as OpenSUSE for FREE, should open a bug report, but let's say I'm not so impulsed to do it, also because hopefully just to signalize a problem, IMHO a list like this one (opensuse-support) should be sufficient.
I don't mean to resolve the issue, but at least to make it of public domain.
so you delay the possible solution and provide others with anguish. while you could give back to the community which gives to you. and possibly exerted more effort on this list than required of a bug report.
yes, the effort here is to con joule/shame/.... you into making a report. or maybe call it an effort to get you to become part of the community from which you request aid and explanation via this list.
Patrick, I wont to look this kind of subject as an ethic behavior, I sometimes get astonished that obvious problems occur without nobody highlighting nor reporting it, as if everything always being working perfectly, honestly this kind of behavior from many users of FREE or even not FREE O.S. is worst than to not open a bug report, IMHO. Well, I did believe that opensuse-support could at least be a sort of "gatherer" of issues which in turn could be forwarded to a development verification team, if this is not the case, I will avoid to post newest posts like this on this mailing-list and I will keep attempting to resolve on my own whenever possible, as I done for at-spi2-registryd case. This is not a "sort of rebellion" from my side, just a personal thought in relation of how the things ideally should run, of course in my very personal opinion. I appreciated your suggestions, but I will not open any bug-reports for a so evident issue affecting a specific openSUSE package which inclusive is an essential dependency of hundreds of others packages. With my very best and really respectful regards, Marco -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
participants (7)
-
Carlos E. R. -
Christian Boltz -
Dave Howorth -
Knurpht-openSUSE -
Marco Calistri -
Patrick Shanahan -
tomas.kuchta.lists＠gmail.com