[Test-Announce] 2014-08-25 @ 15:00 UTC - Fedora QA Meeting
# Fedora Quality Assurance Meeting # Date: 2014-08-25 # Time: 15:00 UTC (https://fedoraproject.org/wiki/Infrastructure/UTCHowto) # Location: #fedora-meeting on irc.freenode.net Greetings testers! It's meeting time tomorrow! Let's call this one the 'get Adam back up to speed' meeting, huh? There's the obvious topic, and maybe we can kick around MozTrap / TCMS stuff for a bit. If there's anything else, please drop a note! == Proposed Agenda Topics == 1. Previous meeting follow-up 2. Fedora 21 status 3. MozTrap / TCMS evaluation 4. Open floor -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net ___ test-announce mailing list test-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/test-announce -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Back to Fedora 20
On Sun, Aug 24, 2014 at 19:42:12 -0700, Chuck Forsberg WA7KGX wrote: I could not get httpd to run. It failed, complaining about not being able to identify its hostname and/or domainname. I started seeing this a few days ago but on omen.com it is a show stopper. I am seeing something that may be related for ssl. When I just ran non-ssl http daemons, things work. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Proposing new dual booting release criteria
On Sun, Aug 24, 2014 at 12:23:55 -0500, Michael Catanzaro wrote: I therefore propose some new release criteria, based on the consensus from the desktop list. It's possible that these new criteria will directly result in further significant delays to the release of F21, since there are four open bugs that would fall under these criteria, but harming the user's previous OS is so severe that we should block on them anyway. Fedora will not become widely popular if it remains dangerous to install. Is this criteria intended for final (as opposed to alpha or beta)? -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Fedora 21 disk system crashes
On 08/24/2014 07:50 PM, Ed Greshko wrote: On 08/25/14 10:11, Chuck Forsberg WA7KGX wrote: For the third or fourth time the hard disk system has crashed at omen.com since putting various incarnations of Fedora 21 on it. This crash seems to be triggered by heavy disk usage. The result of the crash is that any attempted disk access returns an I/O error. Functions that do not require disk access continue to work. The omen.com system runs on an ASUS X79-Deluxe motherboard with 32 GB of memory. This motherboard has a dozen SATA ports, eight 6Gb/s and four 3Gb/s. It also has two power e-SATA ports which I am not using. I hope this provides some useful information and a heads up. What is the bugzilla number for this problem? That is where the useful information goes and where developers can request additional information. Sorry, I'm not a bugzilla expert. Use the information I provided or wait until Fedora 20 general release for others to encounter the problem when they run their systems under load. -- Chuck Forsberg WA7KGX c...@omen.com www.omen.com Developer of Industrial ZMODEM(Tm) for Embedded Applications Omen Technology Inc "The High Reliability Software" 10255 NW Old Cornelius Pass Portland OR 97231 503-614-0430 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Fedora 21 disk system crashes
On 08/25/14 10:11, Chuck Forsberg WA7KGX wrote: > For the third or fourth time the hard disk system has crashed at omen.com > since putting various incarnations of Fedora 21 on it. > > This crash seems to be triggered by heavy disk usage. > The result of the crash is that any attempted disk access returns an I/O > error. > Functions that do not require disk access continue to work. > > The omen.com system runs on an ASUS X79-Deluxe motherboard with > 32 GB of memory. This motherboard has a dozen SATA ports, eight 6Gb/s > and four 3Gb/s. It also has two power e-SATA ports which I am not using. > > I hope this provides some useful information and a heads up. > What is the bugzilla number for this problem? That is where the useful information goes and where developers can request additional information. -- If you can't laugh at yourself, others will gladly oblige. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Back to Fedora 20
On 08/25/14 10:42, Chuck Forsberg WA7KGX wrote: > After rebooting from the crash I ran a YUM update. > After updating a few thousand files YUM started > slowing down and eventually wedged. Apparently > some limit had been reached on the 32 GB system. > > We all know not to stop YUM in the middle of an > operation, but there was no alternative. > > I then did a fresh install of the current Fedora 21. > Two important packages had serious problems. > > I could not get the firewall to enable needed services > on the port facing the internet. > > I could not get httpd to run. It failed, complaining > about not being able to identify its hostname and/or > domainname. I started seeing this a few days ago > but on omen.com it is a show stopper. > > After a while I gave up and did a net install of good old > Heisenbug. My various scripts for setting up Fedora > to my tastes seem to have worked perfectly. Even > /bin/lp works properly! A very smooth install indeed. > > I do miss the new gnome-terminal that rejoins borken > lines when resized. > > Of course you are only testing F21 in the Alpha stage and not trying or even thinking of running it in production. And, of course, you are doing the needful thing and submitting bugzillas for problems you encounter and verify. Right? -- If you can't laugh at yourself, others will gladly oblige. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Back to Fedora 20
After rebooting from the crash I ran a YUM update. After updating a few thousand files YUM started slowing down and eventually wedged. Apparently some limit had been reached on the 32 GB system. We all know not to stop YUM in the middle of an operation, but there was no alternative. I then did a fresh install of the current Fedora 21. Two important packages had serious problems. I could not get the firewall to enable needed services on the port facing the internet. I could not get httpd to run. It failed, complaining about not being able to identify its hostname and/or domainname. I started seeing this a few days ago but on omen.com it is a show stopper. After a while I gave up and did a net install of good old Heisenbug. My various scripts for setting up Fedora to my tastes seem to have worked perfectly. Even /bin/lp works properly! A very smooth install indeed. I do miss the new gnome-terminal that rejoins borken lines when resized. -- Chuck Forsberg WA7KGX c...@omen.com www.omen.com Developer of Industrial ZMODEM(Tm) for Embedded Applications Omen Technology Inc "The High Reliability Software" 10255 NW Old Cornelius Pass Portland OR 97231 503-614-0430 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Fedora 21 disk system crashes
For the third or fourth time the hard disk system has crashed at omen.com since putting various incarnations of Fedora 21 on it. This crash seems to be triggered by heavy disk usage. The result of the crash is that any attempted disk access returns an I/O error. Functions that do not require disk access continue to work. The omen.com system runs on an ASUS X79-Deluxe motherboard with 32 GB of memory. This motherboard has a dozen SATA ports, eight 6Gb/s and four 3Gb/s. It also has two power e-SATA ports which I am not using. I hope this provides some useful information and a heads up. -- Chuck Forsberg WA7KGX c...@omen.com www.omen.com Developer of Industrial ZMODEM(Tm) for Embedded Applications Omen Technology Inc "The High Reliability Software" 10255 NW Old Cornelius Pass Portland OR 97231 503-614-0430 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Fedora 19 updates-testing report
The following Fedora 19 Security updates need testing: Age URL 303 https://admin.fedoraproject.org/updates/FEDORA-2013-19963/openstack-glance-2013.1.4-1.fc19 115 https://admin.fedoraproject.org/updates/FEDORA-2014-5896/nrpe-2.15-2.fc19 66 https://admin.fedoraproject.org/updates/FEDORA-2014-7496/readline-6.2-8.fc19 64 https://admin.fedoraproject.org/updates/FEDORA-2014-7570/asterisk-11.10.2-2.fc19 64 https://admin.fedoraproject.org/updates/FEDORA-2014-6774/claws-mail-3.10.1-1.fc19,claws-mail-plugins-3.10.0-1.fc19,libetpan-1.5-1.fc19 64 https://admin.fedoraproject.org/updates/FEDORA-2014-7610/perl-Email-Address-1.905-1.fc19 55 https://admin.fedoraproject.org/updates/FEDORA-2014-7939/lzo-2.08-1.fc19 31 https://admin.fedoraproject.org/updates/FEDORA-2014-8771/ReviewBoard-1.7.27-1.fc19 17 https://admin.fedoraproject.org/updates/FEDORA-2014-9162/xulrunner-31.0-1.fc19 15 https://admin.fedoraproject.org/updates/FEDORA-2014-9305/krb5-1.11.3-25.fc19 9 https://admin.fedoraproject.org/updates/FEDORA-2014-9350/sks-1.1.5-2.fc19 9 https://admin.fedoraproject.org/updates/FEDORA-2014-9401/ppp-2.4.5-33.fc19 9 https://admin.fedoraproject.org/updates/FEDORA-2014-9399/pixman-0.30.0-5.fc19 9 https://admin.fedoraproject.org/updates/FEDORA-2014-9427/pipelight-0.2.7.3-3.fc19 5 https://admin.fedoraproject.org/updates/FEDORA-2014-9548/mediawiki-1.23.2-1.fc19 5 https://admin.fedoraproject.org/updates/FEDORA-2014-9536/python-pillow-2.0.0-14.gitd1c6db8.fc19 5 https://admin.fedoraproject.org/updates/FEDORA-2014-9544/perl-Plack-1.0031-1.fc19 5 https://admin.fedoraproject.org/updates/FEDORA-2014-9539/jakarta-commons-httpclient-3.1-15.fc19 5 https://admin.fedoraproject.org/updates/FEDORA-2014-9521/subversion-1.7.18-1.fc19 5 https://admin.fedoraproject.org/updates/FEDORA-2014-9534/phpMyAdmin-4.2.7.1-1.fc19 3 https://admin.fedoraproject.org/updates/FEDORA-2014-9646/springframework-security-3.1.7-1.fc19 3 https://admin.fedoraproject.org/updates/FEDORA-2014-9602/polkit-qt-0.112.0-1.fc19 3 https://admin.fedoraproject.org/updates/FEDORA-2014-9624/GraphicsMagick-1.3.20-1.fc19 3 https://admin.fedoraproject.org/updates/FEDORA-2014-9632/distcc-3.2rc1-4.fc19 3 https://admin.fedoraproject.org/updates/FEDORA-2014-9619/ca-certificates-2014.2.1-1.0.fc19 3 https://admin.fedoraproject.org/updates/FEDORA-2014-9629/httpcomponents-client-4.2.5-4.fc19 1 https://admin.fedoraproject.org/updates/FEDORA-2014-9679/php-5.5.16-1.fc19 1 https://admin.fedoraproject.org/updates/FEDORA-2014-9703/cups-1.6.4-9.fc19 The following Fedora 19 Critical Path updates have yet to be approved: Age URL 251 https://admin.fedoraproject.org/updates/FEDORA-2013-22326/fedora-bookmarks-15-5.fc19 177 https://admin.fedoraproject.org/updates/FEDORA-2014-3245/testdisk-6.14-2.fc19.1,ntfs-3g-2014.2.15-1.fc19 9 https://admin.fedoraproject.org/updates/FEDORA-2014-9456/poppler-data-0.4.7-1.fc19 9 https://admin.fedoraproject.org/updates/FEDORA-2014-9453/vim-7.4.402-1.fc19 9 https://admin.fedoraproject.org/updates/FEDORA-2014-9432/selinux-policy-3.12.1-74.29.fc19 9 https://admin.fedoraproject.org/updates/FEDORA-2014-9399/pixman-0.30.0-5.fc19 9 https://admin.fedoraproject.org/updates/FEDORA-2014-9401/ppp-2.4.5-33.fc19 8 https://admin.fedoraproject.org/updates/FEDORA-2014-9513/curl-7.29.0-22.fc19 3 https://admin.fedoraproject.org/updates/FEDORA-2014-9602/polkit-qt-0.112.0-1.fc19 3 https://admin.fedoraproject.org/updates/FEDORA-2014-9619/ca-certificates-2014.2.1-1.0.fc19 1 https://admin.fedoraproject.org/updates/FEDORA-2014-9703/cups-1.6.4-9.fc19 The following builds have been pushed to Fedora 19 updates-testing clamtk-5.08-1.fc19 golang-github-docker-libcontainer-1.1.0-10.gitdb65c35.fc19 openblas-0.2.11-1.fc19 pgp-tools-1.1.5-4.fc19 pynag-0.9.1-1.fc19 python-boto-2.32.1-1.fc19 python-taskw-0.8.6-1.fc19 Details about builds: clamtk-5.08-1.fc19 (FEDORA-2014-9741) Easy to use graphical user interface for Clam anti virus Update Information: Update to 5.08. ChangeLog: * Sun Aug 24 2014 Dave M. - 5.08-1 - Updated to release 5.08. golang-github-docker-libcontainer-1.1.0-10.gitdb65c35.fc19 (FEDORA-2014-9746) Configuration options for containers Update Information: Include syncpipe, system and user dirs missed in previous build ChangeLog:
Fedora 20 updates-testing report
The following Fedora 20 Security updates need testing: Age URL 115 https://admin.fedoraproject.org/updates/FEDORA-2014-5897/nrpe-2.15-2.fc20 64 https://admin.fedoraproject.org/updates/FEDORA-2014-7551/asterisk-11.10.2-2.fc20 64 https://admin.fedoraproject.org/updates/FEDORA-2014-7613/perl-Email-Address-1.905-1.fc20 23 https://admin.fedoraproject.org/updates/FEDORA-2014-9092/libplist-1.11-2.fc20,libusbmuxd-1.0.9-2.fc20,libimobiledevice-1.1.6-2.fc20,usbmuxd-1.0.9-0.4.c24463e.fc20,ifuse-1.1.3-3.fc20,libgpod-0.8.3-2.fc20,upower-0.9.23-3.fc20,gvfs-1.18.3-3.fc20 16 https://admin.fedoraproject.org/updates/FEDORA-2014-9281/drupal6-6.33-1.fc20 9 https://admin.fedoraproject.org/updates/FEDORA-2014-9344/sks-1.1.5-2.fc20 9 https://admin.fedoraproject.org/updates/FEDORA-2014-9476/cinnamon-screensaver-2.2.4-3.fc20 9 https://admin.fedoraproject.org/updates/FEDORA-2014-9474/pipelight-0.2.7.3-3.fc20 5 https://admin.fedoraproject.org/updates/FEDORA-2014-9540/python-pillow-2.2.1-5.fc20 5 https://admin.fedoraproject.org/updates/FEDORA-2014-9542/perl-Plack-1.0031-1.fc20 5 https://admin.fedoraproject.org/updates/FEDORA-2014-9583/mediawiki-1.23.2-1.fc20 5 https://admin.fedoraproject.org/updates/FEDORA-2014-9581/jakarta-commons-httpclient-3.1-15.fc20 3 https://admin.fedoraproject.org/updates/FEDORA-2014-9617/httpcomponents-client-4.2.5-4.fc20 3 https://admin.fedoraproject.org/updates/FEDORA-2014-9648/springframework-security-3.1.7-1.fc20 3 https://admin.fedoraproject.org/updates/FEDORA-2014-9641/polkit-qt-0.112.0-1.fc20 3 https://admin.fedoraproject.org/updates/FEDORA-2014-9596/GraphicsMagick-1.3.20-1.fc20 3 https://admin.fedoraproject.org/updates/FEDORA-2014-9591/distcc-3.2rc1-8.fc20 3 https://admin.fedoraproject.org/updates/FEDORA-2014-9662/cas-client-3.3.3-1.fc20 3 https://admin.fedoraproject.org/updates/FEDORA-2014-9621/ca-certificates-2014.2.1-1.0.fc20 3 https://admin.fedoraproject.org/updates/FEDORA-2014-9636/subversion-1.8.10-1.fc20 1 https://admin.fedoraproject.org/updates/FEDORA-2014-9676/webalizer-2.23_08-1.fc20 1 https://admin.fedoraproject.org/updates/FEDORA-2014-9706/rubygem-activerecord-4.0.0-5.fc20 1 https://admin.fedoraproject.org/updates/FEDORA-2014-9694/smack-3.2.2-5.fc20 1 https://admin.fedoraproject.org/updates/FEDORA-2014-9684/php-5.5.16-1.fc20 The following Fedora 20 Critical Path updates have yet to be approved: Age URL 3 https://admin.fedoraproject.org/updates/FEDORA-2014-9658/libwacom-0.10-1.fc20 3 https://admin.fedoraproject.org/updates/FEDORA-2014-9641/polkit-qt-0.112.0-1.fc20 1 https://admin.fedoraproject.org/updates/FEDORA-2014-9685/cogl-1.16.0-3.fc20 1 https://admin.fedoraproject.org/updates/FEDORA-2014-9673/cups-1.7.5-3.fc20 1 https://admin.fedoraproject.org/updates/FEDORA-2014-9682/selinux-policy-3.12.1-181.fc20 The following builds have been pushed to Fedora 20 updates-testing cdbs-0.4.126-1.fc20 clamtk-5.08-1.fc20 docker-io-1.2.0-2.fc20 golang-github-docker-libcontainer-1.1.0-10.gitdb65c35.fc20 openblas-0.2.11-1.fc20 pynag-0.9.1-1.fc20 python-boto-2.32.1-1.fc20 python-taskw-0.8.6-1.fc20 Details about builds: cdbs-0.4.126-1.fc20 (FEDORA-2014-9738) Common build system for Debian packages Update Information: Update to version 0.4.126, see http://ftp-master.metadata.debian.org/changelogs//main/c/cdbs/cdbs_0.4.126_changelog for details. ChangeLog: * Sat Aug 23 2014 Sandro Mani - 0.4.126-1 - Update to 0.4.126 clamtk-5.08-1.fc20 (FEDORA-2014-9745) Easy to use graphical user interface for Clam anti virus Update Information: Update to 5.08. ChangeLog: * Sun Aug 24 2014 Dave M. - 5.08-1 - Updated to release 5.08. docker-io-1.2.0-2.fc20 (FEDORA-2014-9742) Automates deployment of containerized applications Update Information: Provides docker only for f21 and above Resolves: rhbz#1132824 - update to v1.2.0 ChangeLog: * Sun Aug 24 2014 Lokesh Mandvekar - 1.2.0-2 - Provides docker only for f21 and above * Sat Aug 23 2014 Lokesh Mandvekar - 1
Re: Proposing new dual booting release criteria
On Sun, 24 Aug 2014 12:23:55 -0500 Michael Catanzaro wrote: > We currently do not have any release criterion that applies to dual > booting with other Linux systems. Certainly one thing that could simplify this is an option to go ahead and install the grub rpms and configure the /boot/grub2/grub.cfg file, but don't run grub2-install. That would make it much simpler to dual boot by using a "configfile" option from another already installed grub. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Proposing new dual booting release criteria
Hi all, There's been some discussion on the desktop list, beginning at [1], about Workstation's requirements for dual booting in F21. The Workstation technical specification says the following: "One aspect of storage configuration that will be needed is support for dual-boot setups (preserving preexisting Windows or OS X installations), since e.g. students may be required to run software on those platforms for their coursework." [2] Unfortunately, due to some bugs in anaconda we are not currently meeting the requirement for preserving previous Windows and OS X installations, and the story for preserving previous Linux systems (which is not a requirement) is not any better. A good summary of these bugs is at the bottom of [3]. We think these issues need to be treated very seriously, since we do not expect Workstation users to be able to recover an operating system when it is missing from the boot menu. In short: "No boot entry or nonfunctional boot entry -> user is up a creek -> Fedora Workstation is bad" I therefore propose some new release criteria, based on the consensus from the desktop list. It's possible that these new criteria will directly result in further significant delays to the release of F21, since there are four open bugs that would fall under these criteria, but harming the user's previous OS is so severe that we should block on them anyway. Fedora will not become widely popular if it remains dangerous to install. Windows === Our current release criterion is: "The installer must be able to install into free space alongside an existing clean Windows installation and, when performing a BIOS (not UEFI) installation, install a bootloader which can boot into both Windows and Fedora." I propose the language be amended to the following: "The installer must be able to install into free space alongside an existing clean Windows installation and install a bootloader which can boot into both Windows and Fedora." Rationale: many modern Windows systems no longer have a boot menu that is accessible before the system boots. If Fedora Workstation were installed on such a system, the user would not be able to recover Windows. Open bugs that would be covered by this criterion: https://bugzilla.redhat.com/show_bug.cgi?id=986731 https://bugzilla.redhat.com/show_bug.cgi?id=1010704 OS X We currently do not have any release criterion that applies to dual booting with OS X. Since our Mac support is very poor and has no prospect of near term improvement -- in particular, we have concerns that running Fedora on a Mac has caused at least one Mac to overheat and die -- the consensus seems to be that dual booting with OS X should not be a requirement. However, it's also not OK to destroy the user's OS X without warning. I propose the following final release criterion: "The installer must be able to install into free space alongside an existing clean OS X installation and install a bootloader which can boot into both OS X and Fedora, OR the installer must prominently warn the user that he may be unable to boot OS X after installation, allowing the user to cancel installation and reboot to OS X." I think that requirement should be easy to meet, so I won't include links to the OS X bugs. Linux = We currently do not have any release criterion that applies to dual booting with other Linux systems. Dual booting with other Linux systems is NOT a requirement in the Workstation technical specification, but the consensus seems to be that it should have been. Therefore I propose the following criterion: "The installer must be able to install into free space alongside existing GNU/Linux installations and install a bootloader which can boot into the previously-installed systems and Fedora." I have no doubt that you will need to tweak the wording here, but the intent should be clear. If such a broad requirement isn't technically feasible, then let's discuss what would be. We want the criterion to cover these bugs: https://bugzilla.redhat.com/show_bug.cgi?id=825236 https://bugzilla.redhat.com/show_bug.cgi?id=964828 [1] https://lists.fedoraproject.org/pipermail/desktop/2014-June/009932.html [2] https://fedoraproject.org/wiki/Workstation/Technical_Specification#System_Installer [3] https://lists.fedoraproject.org/pipermail/desktop/2014-June/009953.html signature.asc Description: This is a digitally signed message part -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Abrt errors while analysing gnome-shell
On Sun, 2014-08-24 at 22:02 +0530, Amita Sharma wrote: > Hey Ankur, Hi Amita, > > It seems you just need to update abrt and few other rpms. > Please see https://bugzilla.redhat.com/show_bug.cgi?id=1109697 Thank you for the bug link. Unfortunately, the packages I have installed are newer than the ones suggested in the bug. I've commented on the bug saying so. -- Thanks, Warm regards, Ankur (FranciscoD) http://fedoraproject.org/wiki/User:Ankursinha Join Fedora! Come talk to us! http://fedoraproject.org/wiki/Fedora_Join_SIG signature.asc Description: This is a digitally signed message part -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Abrt errors while analysing gnome-shell
On 08/24/2014 09:27 PM, Ankur Sinha wrote:
Hi,
I'm getting this error repeatedly with abrt:
Hey Ankur,
It seems you just need to update abrt and few other rpms.
Please see https://bugzilla.redhat.com/show_bug.cgi?id=1109697
HTH,
Amita
--- Running report_uReport ---
Server responded with an error: 'Validation failed: Element 'stacktrace' is
invalid: List element is invalid: Element 'frames' is invalid: List element is
invalid: Element 'file_name' is missing'
reporter-ureport failed with exit code 1
('report_uReport' exited with 1)
It's making it slightly difficult to report gnome-shell's crashes. Any
hints on what's causing this? Abrt bug?
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
Abrt errors while analysing gnome-shell
Hi,
I'm getting this error repeatedly with abrt:
> --- Running report_uReport ---
> Server responded with an error: 'Validation failed: Element 'stacktrace' is
> invalid: List element is invalid: Element 'frames' is invalid: List element
> is invalid: Element 'file_name' is missing'
> reporter-ureport failed with exit code 1
> ('report_uReport' exited with 1)
It's making it slightly difficult to report gnome-shell's crashes. Any
hints on what's causing this? Abrt bug?
--
Thanks,
Warm regards,
Ankur (FranciscoD)
http://fedoraproject.org/wiki/User:Ankursinha
Join Fedora! Come talk to us!
http://fedoraproject.org/wiki/Fedora_Join_SIG
signature.asc
Description: This is a digitally signed message part
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
rawhide report: 20140824 changes
Broken deps for i386 -- [APLpy] APLpy-0.9.8-5.fc21.noarch requires pywcs [PyKDE] PyKDE-3.16.6-14.fc20.i686 requires sip-api(10) >= 0:10.0 [PyQuante] PyQuante-libint-1.6.4-11.fc22.1.i686 requires libint(x86-32) = 0:1.1.6-2.fc21 [audtty] audtty-0.1.12-9.fc20.i686 requires libaudclient.so.2 [authhub] authhub-0.1.2-3.fc19.i686 requires libjson.so.0 [aws] aws-devel-3.1.0-6.fc21.i686 requires libgrypt-devel [cduce] cduce-0.6.0-6.fc22.i686 requires ocaml(String) = 0:d3baab1cf7edc2fec1fa9c9217140d10 cduce-0.6.0-6.fc22.i686 requires ocaml(Pervasives) = 0:4329e57fde14cc94b02a739d2595516b cduce-0.6.0-6.fc22.i686 requires ocaml(Location) = 0:0beb1f904f757422c85ea51aae076559 cduce-0.6.0-6.fc22.i686 requires ocaml(Lazy) = 0:65801e9cdbd8c4e82df1f02f97116721 cduce-0.6.0-6.fc22.i686 requires ocaml(Format) = 0:a9de4c8c622e30d6eb221ce41563dbf4 cduce-0.6.0-6.fc22.i686 requires ocaml(Filename) = 0:3b889637b7a18c39de7a0d0f5d10432e cduce-0.6.0-6.fc22.i686 requires ocaml(Array) = 0:9125e0607c9ad02018c9eb4672142241 [compat-gcc-34] compat-gcc-34-c++-3.4.6-29.fc19.i686 requires libstdc++ < 0:4.9.0 [condor] condor-plumage-8.1.4-7.a1a7df5.fc22.i686 requires libmongoclient.so [coq] coq-8.4pl4-12.fc22.i686 requires ocaml(String) = 0:d3baab1cf7edc2fec1fa9c9217140d10 coq-8.4pl4-12.fc22.i686 requires ocaml(Sort) = 0:b2e4998520908a98a1a5086d8f14a029 coq-8.4pl4-12.fc22.i686 requires ocaml(Pervasives) = 0:4329e57fde14cc94b02a739d2595516b coq-8.4pl4-12.fc22.i686 requires ocaml(Lazy) = 0:65801e9cdbd8c4e82df1f02f97116721 coq-8.4pl4-12.fc22.i686 requires ocaml(Format) = 0:a9de4c8c622e30d6eb221ce41563dbf4 coq-8.4pl4-12.fc22.i686 requires ocaml(Filename) = 0:3b889637b7a18c39de7a0d0f5d10432e coq-8.4pl4-12.fc22.i686 requires ocaml(Array) = 0:9125e0607c9ad02018c9eb4672142241 coq-coqide-8.4pl4-12.fc22.i686 requires ocaml(StringLabels) = 0:f87210219611dc47bd0afad43918a08f coq-coqide-8.4pl4-12.fc22.i686 requires ocaml(String) = 0:d3baab1cf7edc2fec1fa9c9217140d10 coq-coqide-8.4pl4-12.fc22.i686 requires ocaml(Pervasives) = 0:4329e57fde14cc94b02a739d2595516b coq-coqide-8.4pl4-12.fc22.i686 requires ocaml(Lazy) = 0:65801e9cdbd8c4e82df1f02f97116721 coq-coqide-8.4pl4-12.fc22.i686 requires ocaml(Format) = 0:a9de4c8c622e30d6eb221ce41563dbf4 coq-coqide-8.4pl4-12.fc22.i686 requires ocaml(Filename) = 0:3b889637b7a18c39de7a0d0f5d10432e coq-coqide-8.4pl4-12.fc22.i686 requires ocaml(BytesLabels) = 0:42a963c0ce495d2588c02f956c7b7bef coq-coqide-8.4pl4-12.fc22.i686 requires ocaml(ArrayLabels) = 0:0bcf9f96a988e637fe53f2fd60aac32f coq-coqide-8.4pl4-12.fc22.i686 requires ocaml(Array) = 0:9125e0607c9ad02018c9eb4672142241 [cp2k] cp2k-2.5.1-8.fc22.i686 requires libint(x86-32) = 0:1.1.6-2.fc21 cp2k-mpich-2.5.1-8.fc22.i686 requires libint(x86-32) = 0:1.1.6-2.fc21 cp2k-openmpi-2.5.1-8.fc22.i686 requires libint(x86-32) = 0:1.1.6-2.fc21 [csound] csound-java-5.19.01-1.fc20.i686 requires libgcj_bc.so.1 csound-java-5.19.01-1.fc20.i686 requires java-gcj-compat csound-java-5.19.01-1.fc20.i686 requires java-gcj-compat csound-java-5.19.01-1.fc20.i686 requires java-1.5.0-gcj csound-tk-5.19.01-1.fc20.i686 requires libtk8.5.so csound-tk-5.19.01-1.fc20.i686 requires libtcl8.5.so [deltacloud-core] deltacloud-core-rackspace-1.1.3-1.fc20.noarch requires rubygem(cloudservers) deltacloud-core-rackspace-1.1.3-1.fc20.noarch requires rubygem(cloudfiles) [docker-registry] docker-registry-0.7.3-1.fc22.noarch requires docker-io [dragonegg] dragonegg-3.4-0.3.rc0.fc21.i686 requires gcc = 0:4.8.2-14.fc21 [edelib] edelib-2.1-5.fc22.i686 requires libedelib.so edelib-devel-2.1-5.fc22.i686 requires libedelib.so [eucalyptus] eucalyptus-common-java-3.3.0-0.5.20130408git32052445.fc20.i686 requires hibernate3-jbosscache >= 0:3.6.10-7 [fatrat] 1:fatrat-1.2.0-0.21.beta2.fc22.i686 requires libtorrent-rasterbar.so.7 [flashrom] flashrom-0.9.6.1-5.svn1705.fc20.i686 requires libftdi.so.1 [flush] flush-0.9.12-10.fc22.i686 requires libtorrent-rasterbar.so.7 [frama-c] frama-c-1.10-13.fc22.i686 requires ocaml(String) = 0:d3baab1cf7edc2fec1fa9c9217140d10 frama-c-1.10-13.fc22.i686 requires ocaml(Pervasives) = 0:4329e57fde14cc94b02a739d2595516b frama-c-1.10-13.fc22.i686 requires ocaml(Lazy) = 0:65801e9cdbd8c4e82df1f02f97116721 frama-c-1.10-13.fc22.i686 requires ocaml(Format) = 0:a9de4c8c622e30d6eb221ce41563dbf4 frama-c-1.10-13.fc22.i686 requires ocaml(Filename) = 0:3b889637b7a18c39de7a0d0f5d10432e frama-c-1.10-13.fc22.i686 requires ocaml(Array) = 0:9125e0607c9ad02018c9eb4672142241 [freesteam] f
F-21 Branched report: 20140824 changes
Compose started at Sun Aug 24 07:15:03 UTC 2014 Broken deps for armhfp -- [APLpy] APLpy-0.9.8-5.fc21.noarch requires pywcs [PyKDE] PyKDE-3.16.6-14.fc20.armv7hl requires sip-api(10) >= 0:10.0 [PyQuante] PyQuante-libint-1.6.4-11.fc21.1.armv7hl requires libint(armv7hl-32) = 0:1.1.6-2.fc21 [audtty] audtty-0.1.12-9.fc20.armv7hl requires libaudclient.so.2 [authhub] authhub-0.1.2-3.fc19.armv7hl requires libjson.so.0 [cp2k] cp2k-2.5.1-8.fc21.armv7hl requires libint(armv7hl-32) = 0:1.1.6-2.fc21 cp2k-mpich-2.5.1-8.fc21.armv7hl requires libint(armv7hl-32) = 0:1.1.6-2.fc21 cp2k-openmpi-2.5.1-8.fc21.armv7hl requires libint(armv7hl-32) = 0:1.1.6-2.fc21 [csound] csound-java-5.19.01-1.fc20.armv7hl requires libgcj_bc.so.1 csound-java-5.19.01-1.fc20.armv7hl requires java-gcj-compat csound-java-5.19.01-1.fc20.armv7hl requires java-gcj-compat csound-java-5.19.01-1.fc20.armv7hl requires java-1.5.0-gcj csound-tk-5.19.01-1.fc20.armv7hl requires libtk8.5.so csound-tk-5.19.01-1.fc20.armv7hl requires libtcl8.5.so [deltacloud-core] deltacloud-core-rackspace-1.1.3-1.fc20.noarch requires rubygem(cloudservers) deltacloud-core-rackspace-1.1.3-1.fc20.noarch requires rubygem(cloudfiles) [docker-registry] docker-registry-0.7.3-1.fc21.noarch requires docker-io [dragonegg] dragonegg-3.4-0.3.rc0.fc21.armv7hl requires gcc = 0:4.8.2-14.fc21 [edelib] edelib-2.1-5.fc21.armv7hl requires libedelib.so edelib-devel-2.1-5.fc21.armv7hl requires libedelib.so [eucalyptus] eucalyptus-common-java-3.3.0-0.5.20130408git32052445.fc20.armv7hl requires hibernate3-jbosscache >= 0:3.6.10-7 [fatrat] 1:fatrat-1.2.0-0.21.beta2.fc21.armv7hl requires libtorrent-rasterbar.so.7 [flashrom] flashrom-0.9.6.1-5.svn1705.fc20.armv7hl requires libftdi.so.1 [flush] flush-0.9.12-10.fc21.armv7hl requires libtorrent-rasterbar.so.7 [freesteam] freesteam-ascend-2.1-6.20140724svn753.fc21.armv7hl requires libascend.so.1 [gcc-python-plugin] gcc-python2-debug-plugin-0.12-18.fc21.armv7hl requires gcc = 0:4.8.2-14.fc21 gcc-python2-plugin-0.12-18.fc21.armv7hl requires gcc = 0:4.8.2-14.fc21 gcc-python3-debug-plugin-0.12-18.fc21.armv7hl requires libpython3.3dm.so.1.0 gcc-python3-debug-plugin-0.12-18.fc21.armv7hl requires gcc = 0:4.8.2-14.fc21 gcc-python3-plugin-0.12-18.fc21.armv7hl requires libpython3.3m.so.1.0 gcc-python3-plugin-0.12-18.fc21.armv7hl requires gcc = 0:4.8.2-14.fc21 [gedit-valencia] gedit-valencia-0.4.0-1.20131223git94442bf.fc21.armv7hl requires libvala-0.24.so.0 [ghc-hint] ghc-hint-devel-0.4.2.0-2.fc21.armv7hl requires ghc-devel(ghc-7.6.3-9662c0f342b2d5c9e1cd2b6330e697bc) [gnome-python2-desktop] gnome-python2-metacity-2.32.0-18.fc21.armv7hl requires libmetacity-private.so.0 [gnome-shell-extension-pomodoro] gnome-shell-extension-pomodoro-0.10.0-4.fc21.armv7hl requires libupower-glib.so.2 [gofer] ruby-gofer-0.77.1-2.fc21.noarch requires rubygem(qpid) >= 0:0.16.0 [hibernate-search] hibernate-search-4.5.1-4.fc21.noarch requires mvn(org.apache.avro:avro) [ice] ice-php-3.5.1-4.fc21.armv7hl requires php(zend-abi) = 0:20121212-32 ice-php-3.5.1-4.fc21.armv7hl requires php(api) = 0:20121113-32 [leiningen] leiningen-1.7.1-7.fc20.noarch requires maven-ant-tasks leiningen-1.7.1-7.fc20.noarch requires classworlds [leksah] ghc-leksah-devel-0.12.1.3-15.fc21.armv7hl requires ghc-devel(ghc-7.6.3-9662c0f342b2d5c9e1cd2b6330e697bc) [leksah-server] ghc-leksah-server-devel-0.12.1.2-15.fc21.armv7hl requires ghc-devel(ghc-7.6.3-9662c0f342b2d5c9e1cd2b6330e697bc) [libghemical] libghemical-2.99.1-24.fc20.armv7hl requires libf77blas.so.3 libghemical-2.99.1-24.fc20.armv7hl requires libatlas.so.3 [libopensync-plugin-irmc] 1:libopensync-plugin-irmc-0.22-7.fc20.armv7hl requires libopenobex.so.1 [libvirt] libvirt-lock-sanlock-1.2.7-2.fc21.armv7hl requires sanlock >= 0:2.4 libvirt-lock-sanlock-1.2.7-2.fc21.armv7hl requires libsanlock_client.so.1 [lirc] lirc-0.9.1a-2.fc21.armv7hl requires libiguanaIR.so.0(IGUANAIR_0) lirc-0.9.1a-2.fc21.armv7hl requires libiguanaIR.so.0 [ltsp] ltsp-client-5.4.5-8.fc21.armv7hl requires fuse-unionfs ltsp-server-5.4.5-8.fc21.armv7hl requires cdialog [meshmagick] meshmagick-0.6.0-20.svn2898.fc21.armv7hl requires libOgreMain.so.1.8.1 meshmagick-libs-0.6.0-20.svn2898.fc21.armv7hl requires libOgreMain.so.1.8.1 [monodevelop-vala] monodevelop-vala-2.8.8.1-6.fc21.armv7hl requires vala < 0:0.25.0 [mpqc] mpqc-2.3.1-26.fc21.armv7hl requires libint(armv7hl-32) = 0:1.1.6-2.fc21 [netdisco] netdisco-1.1-7.fc21.noarch requires perl(SNMP::Info::Layer2::Bay) [openstack-nova]
Can I direct abrt to report a crash to gnome bugzilla instead of the fedora bugzilla?
Hi, I think I jinxed my system when I said F21 was running nice and stable. I've had a myriad of random gnome-shell crashes since then - to the point where I'm finding it slightly difficult to use the system. I've started filing bugs, of course. I was wondering if I can direct abrt to send a bug report to gnome bugzilla straight away instead of the fedora bugzilla. That'll ensure that the bug goes upstream straight away and I won't have to run around doing it manually. -- Thanks, Warm regards, Ankur (FranciscoD) http://fedoraproject.org/wiki/User:Ankursinha Join Fedora! Come talk to us! http://fedoraproject.org/wiki/Fedora_Join_SIG signature.asc Description: This is a digitally signed message part -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
