The following Fedora 16 Security updates need testing:
https://admin.fedoraproject.org/updates/FEDORA-2012-9029/boost-1.47.0-7.fc16
https://admin.fedoraproject.org/updates/FEDORA-2012-9546/vte-0.28.2-6.fc16
https://admin.fedoraproject.org/updates/FEDORA-2012-9371/viewvc-1.1.15-1.fc16
On Wed, Jun 27, 2012 at 11:54 AM, Jóhann B. Guðmundsson
wrote:
> Just bringing this topic to the appropriate mailing list
>
> On the last kernel meeting [1] it was suggested negative karma points should
> be linked to a reported bug which kinda makes sense if you think about it.
>
> What that mean
On Wed, 2012-06-27 at 16:49 +0100, Frank Murphy wrote:
> On 27/06/12 16:32, Andre Robatino wrote:
> > Frank Murphy gmail.com> writes:
>
> >>
> >> If your are using ligthdm, slowness is known:
> >> https://bugzilla.redhat.com/show_bug.cgi?id=834427
> >
> > My Rawhide is a VirtualBox guest (which u
On Wed, 2012-06-27 at 18:34 +, "Jóhann B. Guðmundsson" wrote:
> On 06/27/2012 06:19 PM, Adam Williamson wrote:
> > It's hardly 'sticking their nose in'. The updates policy is owned by
> > FESCo, not by us.
>
> WooT?
>
> > In practice, I'd say the point is kinda moot because
> > this is clea
On 06/27/2012 06:19 PM, Adam Williamson wrote:
It's hardly 'sticking their nose in'. The updates policy is owned by
FESCo, not by us.
WooT?
In practice, I'd say the point is kinda moot because
this is clearly Bodhi 2.0 stuff, and we've been waiting for Bodhi 2.0
forever and a day, and it'll
On Wed, 2012-06-27 at 15:54 +, Jóhann B. Guðmundsson wrote:
> Just bringing this topic to the appropriate mailing list
>
> On the last kernel meeting [1] it was suggested negative karma points
> should be linked to a reported bug which kinda makes sense if you
> think about it.
>
> What that
Bruno Wolff III wolff.to> writes:
> There was recently a bug like that, where I had to set selinux to permissive
> to be able to login in (or see the gdm background screen) as gdm was blocking
> being unable to access a file it needed. This was about 1 to 2 weeks ago
> though, so I don't think
On Wed, Jun 27, 2012 at 4:58 PM, Bruno Wolff III wrote:
> On Wed, Jun 27, 2012 at 15:54:18 +,
> "Jóhann B. Gušmundsson" wrote:
>
>>
>> I myself give +1 to implement this since give negative feedback without
>> linking to an already existing bug report helps no one.
>>
>> There was also ment
On Wed, 2012-06-27 at 16:10 +, Andre Robatino wrote:
> Adam Jackson redhat.com> writes:
>
> > > Should have mentioned that my Rawhide is a VirtualBox 4.1.18 guest (which
> > > uses the vesa driver).
Nope:
> I booted in graphical mode, then when the black screen with the et
On Wed, Jun 27, 2012 at 15:54:18 +,
"Jóhann B. Guðmundsson" wrote:
I myself give +1 to implement this since give negative feedback without
linking to an already existing bug report helps no one.
There was also mentioned on the meeting that reporters seem to be giving
negative karma for b
On Wed, Jun 27, 2012 at 16:10:40 +,
Andre Robatino wrote:
I booted in graphical mode, then when the black screen with the eternal spinning
cursor appeared, switched to VT3 and grabbed Xorg.0.log - see
http://robatino.fedorapeople.org/Xorg.0.log . The file grows gradually, so this
is just a
Adam Jackson redhat.com> writes:
> > Should have mentioned that my Rawhide is a VirtualBox 4.1.18 guest (which
> > uses the vesa driver).
>
> Assuming the guest still brings up networking, you should be able to ssh
> into it and inspect /var/log/Xorg.0.log. Alternatively I assume vbox
> has ser
Just bringing this topic to the appropriate mailing list
On the last kernel meeting [1] it was suggested negative karma points
should be linked to a reported bug which kinda makes sense if you think
about it.
What that means is that you ( as in reporter ) will no longer be able to
provide negati
On Wed, Jun 27, 2012 at 14:48:31 +,
Andre Robatino wrote:
I am not able to boot either of the Rawhide 3.5.0-0.rc4 kernels in runlevel 3
(adding "3" to the boot options). Since booting in default graphical mode has
resulted for me in a black screen immediately after X starts for a long time
On 27/06/12 16:32, Andre Robatino wrote:
Frank Murphy gmail.com> writes:
If your are using ligthdm, slowness is known:
https://bugzilla.redhat.com/show_bug.cgi?id=834427
My Rawhide is a VirtualBox guest (which uses vesa). What happens if you boot
adding the options "xdriver=vesa nomodeset"
On Wed, 2012-06-27 at 15:06 +, Andre Robatino wrote:
> Kevin Martin gmail.com> writes:
>
> > You may be running into the same problem that I have. Check out this
> > bugzilla:
> >
> > https://bugzilla.redhat.com/show_bug.cgi?id=830916
>
> Should have mentioned that my Rawhide is a Virtual
Frank Murphy gmail.com> writes:
> Since booting in default graphical mode has
> > resulted for me in a black screen immediately after X starts for a long time
> > now,
>
> If your are using ligthdm, slowness is known:
> https://bugzilla.redhat.com/show_bug.cgi?id=834427
My Rawhide is a VirtualB
On 27/06/12 15:48, Andre Robatino wrote:
I am not able to boot either of the Rawhide 3.5.0-0.rc4 kernels in runlevel 3
(adding "3" to the boot options).
Both Working fine here KVM Guest qxl graphics option.
Thought there are masses of never-ending systemd-journal spew:
https://bugzilla.redhat.
Andre Robatino fedoraproject.org> writes:
> I am not able to boot either of the Rawhide 3.5.0-0.rc4 kernels in runlevel 3
> (adding "3" to the boot options).
Should have mentioned that what happens when I try this is that I get dropped to
a rescue prompt. Just found that I can sidestep it by boo
Kevin Martin gmail.com> writes:
> You may be running into the same problem that I have. Check out this
> bugzilla:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=830916
Should have mentioned that my Rawhide is a VirtualBox 4.1.18 guest (which uses
the vesa driver).
--
test mailing list
t
On 6/27/2012 10:48 AM, Andre Robatino wrote:
> I am not able to boot either of the Rawhide 3.5.0-0.rc4 kernels in runlevel 3
> (adding "3" to the boot options). Since booting in default graphical mode has
> resulted for me in a black screen immediately after X starts for a long time
> now, this mak
On 06/27/2012 09:48 AM, Andre Robatino wrote:
> I am not able to boot either of the Rawhide 3.5.0-0.rc4 kernels in runlevel 3
> (adding "3" to the boot options). Since booting in default graphical mode has
> resulted for me in a black screen immediately after X starts for a long time
> now, this ma
> From: John Reiser
> Please be more specific. Two monitors on the same graphics card?;
> or: two monitors each on a different backplane graphics card?;
What I need to emulate is a single seat system with two monitors
that form a single desktop. I'm willing to have multiple graphics
emulated gr
I am not able to boot either of the Rawhide 3.5.0-0.rc4 kernels in runlevel 3
(adding "3" to the boot options). Since booting in default graphical mode has
resulted for me in a black screen immediately after X starts for a long time
now, this makes these rc4 kernels unusable (although X apparently
24 matches
Mail list logo
