When I try to print a test page to an HP 7210 in f14 alpha
from system-config-printer, I get a dialogue saying that "there
was a problem processing document" and a printer state that
says:
Idle: /usr/lib/cups/filter/pstoraster failed
When I try to run hp-setup to add the printer, I get an error
th
The following builds have been pushed to Fedora 14 updates-testing
ORBit-0.5.17-30.fc14
Spawning-0.9.4-2.fc14
banshee-1.7.4-2.fc14
cairo-1.10.0-1.fc14
curl-7.21.0-5.fc14
eigen2-2.0.15-1.fc14
etckeeper-0.48-1.fc14
f-spot-0.7.2-2.fc14
fltk-1.1.10-2.fc14
gdm-2.
The following builds have been pushed to Fedora 12 updates-testing
byobu-3.4-2.fc12
cpuid-20100901-1.fc12
etckeeper-0.48-1.fc12
euca2ools-1.3.1-1.fc12
fuse-encfs-1.7.2-1.fc12
git-1.7.2.3-1.fc12
globus-common-11.5-3.fc12
googsystray-1.2.4-1.fc12
gtk-equinox-engin
#90: Make blocker bug nag mails part of the SOP
--+-
Reporter: jlaska | Owner: poelstra
Type: enhancement | Status: assigned
Priority: major| Milestone: Fedora 14
Compo
#89: Improve tracking blocker review status
--+-
Reporter: jlaska | Owner: poelstra
Type: enhancement | Status: new
Priority: major| Milestone: Fedora 14
Component
On Tue, 2010-09-07 at 14:40 +0100, Adam Williamson wrote:
> On Tue, 2010-09-07 at 14:21 +0100, José Matos wrote:
> > On Tuesday 07 September 2010 13:50:04 Adam Williamson wrote:
> > > I saw the same thing on a live image I just span.
> > > Does /etc/systemd/system/graphical.target.wants contain a s
The following builds have been pushed to Fedora 14 updates-testing
R-Biostrings-2.16.9-1.fc14
R-GenomicRanges-1.0.9-1.fc14
R-IRanges-1.6.16-1.fc14
eclipse-ptp-4.0.3-0.3.RC2c.fc14
fuse-encfs-1.7.2-1.fc14
gcc-4.5.1-3.fc14
git-1.7.2.3-1.fc14
gnome-themes-2.31.90-2.fc14
> Can we get this in bugzilla?
I just added this:
https://bugzilla.redhat.com/show_bug.cgi?id=631271
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
On Tue, Sep 07, 2010 at 12:13:24PM -0400, Tom Horsley wrote:
> On Tue, 7 Sep 2010 17:39:55 +0200
> drago01 wrote:
>
> > > finally squash avahi-daemon :-).
> >
> > What did it ever do to you?
>
> I utterly despise all "helpful" software that automatically
> "discovers" things and triggers annoy
On Tue, Sep 07, 2010 at 05:10:56PM +0100, Daniel P. Berrange wrote:
> libvirtd has never explicitly auto-started avahi. libvirtd uses the
> avahi client library and gives it a callback to be invoked whenever
> a connection to the avahi daemon is established. With the old init
> system, if avahi was
#126: Proposed Test Day - openldap with Mozilla NSS for crypto
-+--
Reporter: rmeggins | Owner:
Type: task | Status: new
Priority: critical
On Tue, 7 Sep 2010 17:39:55 +0200
drago01 wrote:
> > finally squash avahi-daemon :-).
>
> What did it ever do to you?
I utterly despise all "helpful" software that automatically
"discovers" things and triggers annoying sequences of
events on my computer. If something happens, I want it to
be b
On Tue, Sep 07, 2010 at 09:38:15AM -0600, Eric Blake wrote:
> [adding libvir-list]
>
> On 09/07/2010 07:42 AM, Tom Horsley wrote:
> > On Tue, 07 Sep 2010 13:51:09 +0100
> > Adam Williamson wrote:
> >
> >>> I did find a "Should-start: avahi-daemon" comment in the libvirtd
> >>> init script, so mayb
On Tue, Sep 7, 2010 at 3:42 PM, Tom Horsley wrote:
> finally squash avahi-daemon :-).
What did it ever do to you?
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
[adding libvir-list]
On 09/07/2010 07:42 AM, Tom Horsley wrote:
> On Tue, 07 Sep 2010 13:51:09 +0100
> Adam Williamson wrote:
>
>>> I did find a "Should-start: avahi-daemon" comment in the libvirtd
>>> init script, so maybe that is the source.
>>
>> Shouldn't be. 'Should-start' means 'if this othe
Compose started at Tue Sep 7 13:15:51 UTC 2010
Broken deps for x86_64
--
PragmARC-20060427-6.fc13.i686 requires libgnarl-4.4.so
PragmARC-20060427-6.fc13.i686 requires libgnat-4.4.so
PragmARC-20060427-6.fc13.x86_64 req
On Tuesday 07 September 2010 14:40:21 Adam Williamson wrote:
> We've figured this one out now, thanks to Michael Schmidt. See
> https://bugzilla.redhat.com/show_bug.cgi?id=630952 . Running 'systemctl
> enable prefdm.service' as root should fix it. (You'll also probably want
> to do 'systemctl enabl
On Tue, Sep 7, 2010 at 1:01 AM, Jon Hermansen wrote:
> On Mon, Sep 6, 2010 at 3:47 PM, Bob Cochran wrote:
>>
>> I don't even know if the MacBook Pro will show a BIOS screen.
>
> Apple provides BIOS emulation, but I'm not sure if it shows the POST output
> you're probably used to. This is how they
Start End Name
Tue 24-Aug Tue 14-Sep Alpha Testing
Thu 02-Sep Thu 09-Sep Pre-Beta Acceptance Test Plan
Mon 06-Sep Fri 10-Sep Daily Review & Notification of Open Beta Blocker
Bugs
Thu 09-Sep Wed 15-Sep Test Beta 'Test Compose'
Fri 10-Sep Fri 10-Sep Beta Blocker Meeting (f14b
On Tue, 07 Sep 2010 13:51:09 +0100
Adam Williamson wrote:
> > I did find a "Should-start: avahi-daemon" comment in the libvirtd
> > init script, so maybe that is the source.
>
> Shouldn't be. 'Should-start' means 'if this other service is enabled, it
> should be started before this one': it's n
On Tue, 2010-09-07 at 14:21 +0100, José Matos wrote:
> On Tuesday 07 September 2010 13:50:04 Adam Williamson wrote:
> > I saw the same thing on a live image I just span.
> > Does /etc/systemd/system/graphical.target.wants contain a symlink to
> > prefdm.service for you? If not, what does it contain
On Tue, 2010-09-07 at 14:36 +0200, Jan Wildeboer wrote:
> On 09/07/2010 02:32 PM, Adam Williamson wrote:
>
> > It isn't. We can't possibly guarantee suspend/resume will work on all
> > laptops in anything like a reasonable timeframe. if we set this as a
> > release criterion, we would likely never
On Tuesday 07 September 2010 13:50:04 Adam Williamson wrote:
> I saw the same thing on a live image I just span.
> Does /etc/systemd/system/graphical.target.wants contain a symlink to
> prefdm.service for you? If not, what does it contain?
That directory is absent from /etc/systemd/system, the dir
On 09/07/2010 02:45 PM, drago01 wrote:
> http://koji.fedoraproject.org/koji/buildinfo?buildID=193772
>
> This one addresses some suspend issues so it is worth testing.
Bingo! Suspend/resume now works again. (Still have to do a service
NetworkManager restart after resume some times, minor to me)
On Mon, 2010-09-06 at 21:18 -0400, Tom Horsley wrote:
> On Mon, 6 Sep 2010 16:22:50 -0700
> Jon Hermansen wrote:
>
> > What is the parent PID and process name of the running avahi-daemon you
> > found?
>
> I think I looked at that and it was owned by init, but that might
> just mean someone start
On Mon, 2010-09-06 at 18:48 -0500, Mike Chambers wrote:
> On Mon, 2010-09-06 at 18:28 +0100, José Matos wrote:
> > Hi,
> >
> > When I start the computer I am greeted with the console, the graphical
> > display
> > for the desktop manager does not show, be it kdm or gdm.
> >
> > Some more de
On Tue, Sep 7, 2010 at 2:36 PM, Jan Wildeboer wrote:
> On 09/07/2010 02:32 PM, Adam Williamson wrote:
>
>> It isn't. We can't possibly guarantee suspend/resume will work on all
>> laptops in anything like a reasonable timeframe. if we set this as a
>> release criterion, we would likely never relea
On 09/07/2010 02:32 PM, Adam Williamson wrote:
> It isn't. We can't possibly guarantee suspend/resume will work on all
> laptops in anything like a reasonable timeframe. if we set this as a
> release criterion, we would likely never release. So we don't.
Understood. It is however a royal PITA ;-)
On Sun, 2010-09-05 at 13:25 -0400, Jan Wildeboer wrote:
> In my case (F13, x86_64 on a Lenovo X200) the .34 kernel made suspend fail.
> On laptops I think working suspend/resume should be blocker for release. It
It isn't. We can't possibly guarantee suspend/resume will work on all
laptops in any
On Sat, 2010-09-04 at 23:10 -0400, Bill Davidsen wrote:
> If they don't have time to look at everything, then maybe they should stop
> shipping kernels they haven't looked at! Really, people who needed 2.6.34
> could
this is not on topic for this list. please participate in the existing
disc
On 08/30/2010 03:15 PM, Karel Volný wrote:
> On Sunday 29 of August 2010 00:39:52 Rahul Sundaram wrote:
>> Again, the time required to do that is pretty small (maybe as
>> small as ten minutes)
> ... if you already have all the background knowledge, and the
> needed abilities
>
> don't forget ab
Compose started at Tue Sep 7 08:15:37 UTC 2010
Broken deps for x86_64
--
RackTables-0.18.4-1.fc15.noarch requires perl(File::FnMatch)
antlr3-python-3.1.2-7.fc14.noarch requires python(abi) = 0:2.6
claws-mail-plugins-g
On Tue, Sep 7, 2010 at 1:20 PM, Rodd Clarkson wrote:
> , there's no way in hell that anything
> with ~10,000 unreviewed patches
Err they aren't unreviewed as upstream did review them, it just does
not make sense to review every single patch downstream too (besides
obviously there is no man power
Speaking of testing systemd. Are there any tests to see that
the system can be shutdown and reboot cleanly after updates
to things like libc. This was only recently fixed for the
old init scheme, and it would be good not to regress in this
area. It does seem like it might be more complex to do a
cl
On Tue, Sep 7, 2010 at 1:12 PM, Chuck Ebbert wrote:
> On Sat, 04 Sep 2010 23:10:11 -0400
> Bill Davidsen wrote:
>
> > If they don't have time to look at everything, then maybe they should
> stop
> > shipping kernels they haven't looked at! Really, people who needed 2.6.34
> could
> > pull it fro
On Mon, 2010-09-06 at 13:00 -0600, Kevin Fenzi wrote:
> On Mon, 6 Sep 2010 16:33:49 +0100
> Richard Hughes wrote:
>
> > On 6 September 2010 15:51, pbrobin...@gmail.com
> > wrote:
> > > No, its F-14 and had been broken since Aug 31st. The last good
> > > compose of gnome based (as in have gnome c
Attention all Proven Testers (and all testers, too!) Please note this
addition to the proven tester procedure:
https://fedoraproject.org/w/index.php?title=Proven_tester&diff=195994&oldid=193694
basically, an update not fixing a bug it claims to fix is not a cause
for negative karma unless it's th
On Tue, 2010-09-07 at 02:41 +0200, Michał Piotrowski wrote:
> Hi,
>
> I want to compare systemd and upstart boot speed (I don't expect much,
> so I won't be disappointed :))
>
> systemd
> http://i56.tinypic.com/ilk4fq.jpg
>
> upstart
> http://i53.tinypic.com/dnhrvm.png
>
> both starts system in
38 matches
Mail list logo