Thanks for the bug report.
This particular issue has already been reported in our bug tracking system, but please feel free to report any further bugs you find.
In general it is welcome to search for existing reports first to avoid filing duplicates.

Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.

Closing as INSUFFICIENT_DATA.

Keywords: (none) => PATCH, Triaged
Status: NEW => RESOLVED
Resolution: (none) => OLD

reop

Resolution: OLD => (none)
Status: RESOLVED => REOPENED

Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.

Closing as INSUFFICIENT_DATA.

Status: REOPENED => RESOLVED
Resolution: (none) => OLD

reopen

Resolution: OLD => (none)
Status: RESOLVED => REOPENED

new

Status: REOPENED => NEW

Seems good for me.

If you want test: 
install the greacemonkey addon: https://addons.mozilla.org/en-US/firefox/addon/greasemonkey/
then install the script: http://userscripts.org/scripts/show/117441

please feel free to comment / add suggestions ;)

Keywords: PATCH, Triaged => (none)

I'll test, thanks Manuel :)

CC: (none) => marja11, remco

I really like your script, leuhmanu :), It contains a lot more than I had expected, I'll use it from now on.


About the NEEDINFO Reminder:

I think replacing "If you won't reply in one month" with "If you won't reply in to weeks from now" or with "If you won't reply within one month after that question was made", would make more clear when we'll close the bug report.

Resolution: (none) => OLD
Status: NEW => RESOLVED
Keywords: (none) => PATCH, Triaged

reopening

Status: RESOLVED => REOPENED
Resolution: OLD => (none)

new

Status: REOPENED => NEW

(In reply to comment #8)
> 
> About the NEEDINFO Reminder:
> 
> I think replacing "If you won't reply in one month" with "If you won't reply in
> to weeks from now" or with "If you won't reply within one month after that
> question was made", would make more clear when we'll close the bug report.
done 


The strings are just copy paste :)

for other, maybe I can use this one
http://live.gnome.org/Bugsquad/TriageGuide/StockResponses#NEEDINFO_bugs_without_a_response_from_submitter or 
https://wiki.maemo.org/index.php?title=Bugs:Stock_answers
https://fedoraproject.org/wiki/BugZappers/StockBugzillaResponses

I also remix the upstream buttom with remove string and status

Keywords: PATCH, Triaged => (none)

Thanks, Manuel.

One of many things I like in the links you gave, is that the replies often contain a line like "thank you for taking the time to report this bug"

New version, add UPSTREAM and NEEDINFO keyword.
I will see later for fix the "get maintainer"

Hi, thanks for reporting this bug.
We are sorry, but we no longer maintains this version of Mageia. Please upgrade to the latest version and reopen this bug against that version if this bug exists there.
As a result we are setting this bug to CLOSED:WONTFIX

Resolution: (none) => WONTFIX
Status: NEW => RESOLVED

hum

Resolution: WONTFIX => (none)
Assignee: bugsquad => manuel
Status: RESOLVED => REOPENED

Hi, thanks for reporting this bug.
Assigned to the package maintainer.

(Please set the status to 'assigned' if you are working on it)

Keywords: (none) => Triaged

New version 

if there is no packager (or set to nobody), it search in a list of committers 
http://freeshell.de/~manu67/mageia/commits.txt

synced with the version of pterjan or stormi

Oops, I should have clicked the "get maintainer" button.

Anyway, it seems to work fine, but I'll delete all those cc's before adding this comment.

Thx a lot Manuel, :)

test

So new update, the 'Get maintainer' can now get the maintainer for 'complex' rpm name, thanks to pterjan :)

URL: (none) => http://userscripts.org/scripts/show/117441
Source RPM: gdm => java-1.7.0-openjdk-1.7.0.1-2.0.4.mga2.x86_64.rpm

testing no response

Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.

Closing as OLD.

YESS!! It works :)

Resolution: (none) => OLD
Status: REOPENED => RESOLVED

 pk

Source RPM: java-1.7.0-openjdk-1.7.0.1-2.0.4.mga2.x86_64.rpm => udisks
Status: RESOLVED => REOPENED
Resolution: OLD => (none)

test

test

Enhancement request:

Please add this to the QA bit..

selectOption("rep_platform", "All");


It sets the Platform (which is usually i586) to All.

Thanks!

Keywords: (none) => validated_update

(In reply to comment #25)
> Enhancement request:
> 
> Please add this to the QA bit..
> 
> selectOption("rep_platform", "All");
> 
Done in the version 0.8.3. Thanks

Keywords: Triaged, validated_update => (none)
Source RPM: udisks => (none)

Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

go

Severity: normal => enhancement
Status: REOPENED => ASSIGNED
Priority: Normal => Low
Keywords: NEEDINFO => (none)

(In reply to comment #28)

Reporter, could you please reply to the previous question? If you won't reply within two weeks from now, I will have to close this bug as OLD. Thank you.

s/won't/don't/ :)

CC: (none) => zen25000
Keywords: (none) => NEEDINFO, PATCH, Triaged

> s/won't/don't/ :)

Thanks fixed locally

Keywords: NEEDINFO, PATCH, Triaged => (none)

test

@Marja
Can this bug be closed now?

CC: (none) => lewyssmith

(In reply to Lewis Smith from comment #32)
> @Marja
> Can this bug be closed now?

We'll still need it when Leuhmanu's script gets updated, it hasn't worked in cauldron since FF-57, when, as stormi found out, Greasemonkey had to be rewritten entirely to work with FF-57 and, as a consequence, had a backward-incompatible change.
When this was discussed in december 2017, leuhmanu said that tampermonkey was available in firefox too if it works in FF57. I think I missed his comment at that time, but I do remember a comment that I can't find now: that stormi was willing to update leuhman's script.

@ stormi

Have I dreamt that?

@ leuhmanu

Feel free to reassign to BugSquad

CC: misc, remco => (none)
Severity: enhancement => normal
Priority: Low => Normal
Status: ASSIGNED => NEW
Summary: Test bug, greasemonkey script => Greasemonkey BugSquad script needs to be updated or replaced
Source RPM: mplayer totem ( => (none)

@marja I don't remember that discussion about script rewrite

Hi, this script is usefull for Bugsquad.
It worksome for several functions.
Search for maintainer is broken. I had to find elsewhere on our servers.
http://pkgsubmit.mageia.org/data/maintdb.txt

Could it be updated please?

CC: (none) => ouaurelien

Latest version is from 2016, and is here: https://freeshell.de/~manu67/mageia/
Update URL tag with script location.

URL: http://userscripts.org/scripts/show/117441 => https://freeshell.de/~manu67/mageia/

(In reply to Aurelien Oudelet from comment #35)
> Hi, this script is usefull for Bugsquad.
> It worksome for several functions.
> Search for maintainer is broken. I had to find elsewhere on our servers.
> http://pkgsubmit.mageia.org/data/maintdb.txt
> 
> Could it be updated please?

Hi, 

I removed some months ago the stuff (api) for the maintainer function, I can try to add it again

Hi Manuel,

If it is possible, it can be great. But if it is broken or list above is too old... Your script is great for bugsquad, Thank you !

Thanks for the bug report.  We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue.

Please attach your X server config file (/etc/X11/xorg.conf) and X server log file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link below.

Could you please also try to run without any /etc/X11/xorg.conf whatsoever and let X11 autodetect your display and video card? Attach to this bug /var/log/Xorg.0.log from this attempt as well, please.

We will review this issue again once you've had a chance to attach this information.

Thanks in advance.



(Quand je clique sur X)

Keywords: (none) => NEEDINFO

Check ALL FIXME
1) enable the 'core release debug'
2) install the following packages: FIXME-debug
3) run the following command from a terminal:
  gdb -q FIXME 2>&1 | tee debug.txt
4) then type 'run'
(if it ask for missing packages, install them)
5) when it segfaults, type 'bt'
6) attach the file debug.txt to this bug


Début de réponse à modifier.
Clic sur GDB

Thanks for the bug report.
Could you provide the file /root/drakx/report.bug.xz as an attachment ?
If you don't have the file, you can switch to console 2 (by pressing 'Ctrl-Alt-F2') during installation, put a floppy in floppy drive or plug a USB key/stick and type: 'bug' then press Enter. It will put report.bug on the floppy/key.

Installer
Un peu daté sur la disquette...

Reporter, could you please reply to the previous question? If you don't reply within two weeks from now, I will have to close this bug as OLD. Thank you.

Double clique sur NEEDINFO

Keywords: (none) => UPSTREAM

Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest update of our distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.

Closing as OLD.

Status: NEW => RESOLVED
Resolution: (none) => OLD

Hi, thanks for reporting this bug.
We are sorry, but we no longer maintains this version of Mageia. Please upgrade to the latest version and reopen this bug against that version if this bug exists there.
As a result we are setting this bug to RESOLVED:OLD

Hi, thanks for reporting this bug.
Assigned to the package maintainer.

(Please set the status to 'assigned' if you are working on it)

Status: RESOLVED => REOPENED
Keywords: (none) => Triaged
Resolution: OLD => (none)

Hi, thanks for reporting this bug.
As there is no maintainer for this package I added the committers in CC.

(Please set the status to 'assigned' if you are working on it)

Keywords: NEEDINFO, Triaged, UPSTREAM => (none)

Sorry for noise and SPAM.

Status: REOPENED => ASSIGNED
Assignee: manuel.mageia => bugsquad

(In reply to Manuel Hiebel from comment #37)
> (In reply to Aurelien Oudelet from comment #35)
> > Hi, this script is usefull for Bugsquad.
> > It worksome for several functions.
> > Search for maintainer is broken. I had to find elsewhere on our servers.
> > http://pkgsubmit.mageia.org/data/maintdb.txt
> > 
> > Could it be updated please?
> 
> Hi, 
> 
> I removed some months ago the stuff (api) for the maintainer function, I can
> try to add it again

While playing with something else, I just found that tampermonkey works fine (even on firefox), when using the maintdb button it ask if we he can access to the website

On greasemonkey ir didn't work at all.

So everything should still work with tampermonkey

Keywords: (none) => Triaged
Source RPM: (none) => lutris

Yeah, and where can I find tampermonkey?
Thanks!

After all, I use mgarepo commands ;)
Regards,

Keywords: Triaged => NEEDINFO

this https://addons.mozilla.org/fr/firefox/addon/tampermonkey/

Source RPM: lutris => (none)