Re: F14: what to do about pino / twitter
by Paul W. Frields
On Mon, Oct 04, 2010 at 11:26:26AM -0400, Eric "Sparks" Christensen wrote:
> On 10/04/2010 11:13 AM, Paul W. Frields wrote:
> > On Fri, Oct 01, 2010 at 11:48:07PM -0400, Matthias Clasen wrote:
> >> On Fri, 2010-10-01 at 16:44 -0400, Paul W. Frields wrote:
> >>> On Fri, Oct 01, 2010 at 01:19:52PM -0700, Adam Williamson wrote:
> >>>> On Fri, 2010-10-01 at 16:07 -0400, Paul W. Frields wrote:
> >>>>
> >>>>>> Yeah, if we want to ship one, gwibber is pretty much the only option,
> >>>>>> since it's most likely too late to fix pino before F14 is released. The
> >>>>>> big cons about gwibber, in my opinion is the fairly poor performance
> >>>>>> I've experienced with it (tho I last used it about 2 months ago) and the
> >>>>>> number of dependencies it would pull into the livecd.
> >>>>>
> >>>>> Doesn't post-Beta seem too late to do this? Better to have people
> >>>>> simply use their browser I'd think.
> >>>>
> >>>> well, we have to make *some* kind of post-beta change here, since as I
> >>>> said the current situation blocks the release. I don't think subbing in
> >>>> gwibber for pino is a particularly scary change, all we'd have to check
> >>>> is if it goes over the size limit, and if it works, which is about half
> >>>> an hour of effort.
> >>>
> >>> Right, the uncertainty I have is really around the functionality of
> >>> the new suggested default client, as opposed to "let's not do
> >>> anything." My preference would be a simple removal of pino for no
> >>> other reason than least disturbance of the Force.
> >>
> >> I agree that removing pino, together with a suitable note in the release
> >> notes, is the safest route at this point.
> >
> > Adding the docs@ list to the cc so that they are aware of the need for
> > a release note for this. Docs folks, feel free to ask questions here
> > on desktop@ as needed to figure out the best text.
> >
>
> So pino needs to be removed and replaced by Gwibber in the Release
> Notes? It will be tight but I think that change can be made. I'd
> appreciate someone to come with the text that needs to be used for this
> replacement.
What is the final decision on this, so Docs can note the change? Pino
will be removed, but will Gwibber be replacing it or not?
--
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
Where open source multiplies: http://opensource.com
13 years, 5 months
Non-default desktop validation testing for F14 final
by Adam Williamson
Hi, folks. Just an update on desktop validation testing for F14 final
(we'll hit the TC stage next week).
I've been chatting to a few people about the idea of having bugs in
desktop validation outside of GNOME block releases, and there turn out
to be quite a lot of questions involved in terms of how exactly the
project as a whole views the various spins and desktops. I'm happy to
discuss this in more detail (oh, so much boring detail) if anyone's
interested, but the upshot is that basically we're going to have to ask
the board for clarification on a few things about the exact status of
non-default desktops and spins.
In the meantime, given the conclusion, I agreed with others in the
release process (QA and releng) that for F14 Final (and we did this for
Beta too) we'll consider failures in the desktop validation testing for
LXDE and XFCE to be nice-to-have bugs under the new NTH process, rather
than blockers. That means we'll take fixes for them through the release
freeze, but won't hold the release for them. Failures in desktop
validation testing for GNOME and KDE will be considered blockers.
Once we have the wider questions sorted out one way or another, we'll
take another look at the status of failures in LXDE and XFCE, and any
other desktops/spins we extend validation testing to for F15 (I'm
looking at Sugar and Meego for that time). But for now, just a heads-up
that we'll be treating XFCE/LXDE validation issues as nice-to-have for
Final. Thanks!
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net
13 years, 5 months
Re: F14: what to do about pino / twitter
by Eric Christensen
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 10/04/2010 11:13 AM, Paul W. Frields wrote:
> On Fri, Oct 01, 2010 at 11:48:07PM -0400, Matthias Clasen wrote:
>> On Fri, 2010-10-01 at 16:44 -0400, Paul W. Frields wrote:
>>> On Fri, Oct 01, 2010 at 01:19:52PM -0700, Adam Williamson wrote:
>>>> On Fri, 2010-10-01 at 16:07 -0400, Paul W. Frields wrote:
>>>>
>>>>>> Yeah, if we want to ship one, gwibber is pretty much the only option,
>>>>>> since it's most likely too late to fix pino before F14 is released. The
>>>>>> big cons about gwibber, in my opinion is the fairly poor performance
>>>>>> I've experienced with it (tho I last used it about 2 months ago) and the
>>>>>> number of dependencies it would pull into the livecd.
>>>>>
>>>>> Doesn't post-Beta seem too late to do this? Better to have people
>>>>> simply use their browser I'd think.
>>>>
>>>> well, we have to make *some* kind of post-beta change here, since as I
>>>> said the current situation blocks the release. I don't think subbing in
>>>> gwibber for pino is a particularly scary change, all we'd have to check
>>>> is if it goes over the size limit, and if it works, which is about half
>>>> an hour of effort.
>>>
>>> Right, the uncertainty I have is really around the functionality of
>>> the new suggested default client, as opposed to "let's not do
>>> anything." My preference would be a simple removal of pino for no
>>> other reason than least disturbance of the Force.
>>
>> I agree that removing pino, together with a suitable note in the release
>> notes, is the safest route at this point.
>
> Adding the docs@ list to the cc so that they are aware of the need for
> a release note for this. Docs folks, feel free to ask questions here
> on desktop@ as needed to figure out the best text.
>
So pino needs to be removed and replaced by Gwibber in the Release
Notes? It will be tight but I think that change can be made. I'd
appreciate someone to come with the text that needs to be used for this
replacement.
- --Eric
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJMqlwzAAoJEDbiLlqcYamxeUYP+wej+K6pL2PMpaFVETxEpiPA
aXw/D945w1+UW+yZYtW04/e/k+Ray84b1vZODSUx9GhOKbSzU0Gfdf9qW7OKS9ro
8qLO4B385kyZObBk+MjDpqlTxwWat0Eo1KvYcSxLsXyNGILTUm6OO0LMfh07H35g
znn90fi/+tNXYR6YB1uwUCxPsbbt+jTW5EP8vz/M9HCM7c2TdZKpYC6ER3erQhFH
HiQCQ3kgcHCbzT1GA5XqJB8wL6+mF6WC0gETuX33Z76I51vYCPZsalJ5JFlC5Bbh
xeqwReuBrNrOCzxIpiMnMN4YGHKK5PHXrkOVHbrGLJRUPXvYSLwIh5LjD7dn5I9z
/9mIYFx5aVRgS7+hsWiXR8JVPHmORyRDXlSglG4i6fvpTIDt8KgcCpzUaaKfBEzD
b480Rr1dmIk24N9DVinN3u/OtBAwMoLV5N+71r/B4iUGiSppxvpFWn+6fii9Xrjo
VdMZ82miIvmQKVNRXeWLPAC6NPrcUgK9E1Va4ICGcovW+kuuE962BzO+LLlqxHzG
fEKSEdKp/eaUULLu/8UTmxt0seSZoWyDpkATVldtxSiIvjpktJGhtDVlCoAx/ni9
tUQ7VVaQTZGHjust6OK6stQVmc+dXRVQmI488bDaS8yWB4QF8CXdRKGDGRHmprO6
mVNg/yDUB9eTjQDtvk0Y
=NG81
-----END PGP SIGNATURE-----
13 years, 5 months
f14 and orca
by Jonathan Nadeau
Hello list,
I just tried out f14 and orca really doesn't work. When you first
start orca it does not go through the set up like it normally does.
Instead it starts right away like it has already been set up and
doesn't let you go through the orca configuration. Orca does start to
talk but you can't move around on the desktop or anywhere like the
gnome menu or any of the panels. When you press a button on the
keyboard orca just says the key you are pressing. It's as if orca
doesn't have focus of the desktop and can't move anywhere. I figured I
would try to erase the config folder in the home folder by going to
the home folder and pressing control h to show the hidden folders and
there was no .orca folder to erase I'm not sure what this means but
this is what I have found. Thanks for your time and help
--Jonathan Nadeau
13 years, 5 months
F14: what to do about pino / twitter
by Adam Williamson
Hi, folks. Just want to flag up this blocker bug:
https://bugzilla.redhat.com/show_bug.cgi?id=629192
as it stands, the whole pino / oauth mess blocks F14 release; apps that
are on the desktop spin / default desktop install which don't basically
work (so that includes pino at present) block the release.
So, as I see it, there's three options here:
* ship a fixed pino
* ship something else
* don't ship a twitter client by default
Just wanted to start a thread to flag up the issue and prompt a
discussion of an appropriate resolution. thanks!
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net
13 years, 5 months
Gnome-Disk-Utility: UI too big
by Gendre Sebastien
Hello everybody. I have a proble with Gnome-Disk-Utility: When I select
the system disk (LVM encrypted), the UI become too big. The UI become
too wide for 1024 px width and too high for 768 px height screen.
It's even more annoying than majority of new laptop have a 1366x768
screen.
I hade created, in May, a bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=596843
I propose a solution for this:
Move the volumes table to the big tree on the left of the UI (like old
UI). Each volumes becomes a node of the tree and have their owner disk
for root node. If you selecte a disk on the tree, you have only options
and informations of this disk and you must to select a volume to have
options and informations of this volume. For don't have a big width
tree, you can hide/show all same level node to their root node.
Exemple:
1/
*********************
*
(-) Disk-00 *
+----- Volume-00 *
+----- Volume-01 *
+----- Volume-01 *
. *
. *
. *
2/ (when you clic on minus button of the node (disk-00))
**************************
*
(+) Disk-00 (3 volumes) *
. *
. *
. *
With this solution, we have 3 levels:
1/ Computer (local or network).
2/ Phisical controllers and LVM.
3/ Phisical disks and LVM logical group.
4/ Phisical volumes and LVM logical volumes.
13 years, 6 months
F14: mDNS port are close
by Gendre Sebastien
Hello everybody.
In Fedora 14, I see the port of mDNS are open, but avahi service are
launched. Is it normal?
--
Gendre Sebastien <korbe(a)romandie.com>
13 years, 6 months
why no new GNOME 3 snapshot in F14?
by Colin Walters
I just had a discussion with Owen about the state of F14+gnome-shell,
and wanted to give an update on why we decided not to try updating it
from the current state (last updated Jul 13), and concentrate on F15
instead.
So most of the development has been happening in git/jhbuild, and we
haven't even managed to get rawhide updated due to the XULRunner
changes (work on rawhide is proceeding now,
https://bugzilla.gnome.org/show_bug.cgi?id=622896 for the curious).
Now, multiple things would need to occur for F14:
- Separate clutter 1.4 parallel install package
Impact on critical path: None. Sort of ugly is the only thing.
- Updated GTK3 package
Impact on critical path: Low/None (some things in F14 oddly
require gtk3 that shouldn't, like seed...needs investigation). But
we'd *also* have to look at either updating packages like
gnome-desktop3 (or removing them).
- gobject-introspection 0.9.5+
This implies simple rebuilds of a lot of packages for the
lookaside GIR/.typelib data, which is straightforward. However,
updating to this version also implies pulling in a new pygobject,
which has had quite a bit of code changes. Upstream feels confident,
but it's just one thing that weighs against an update (a possible
alternative path is to disable introspection from pygobject).
So the alternative here is:
- Add a warning/note to F14 gnome-shell that it's old and to:
- Make it easier and better to run F15/rawhide. Which involves
fixing the problems there, and scripting the rpm/yum foo better to
make the switch, and being a lot more aggressive about preventing
regressions.
13 years, 6 months
RE: HDD bad sectors repair
by Hristo Petkov
Hi,
I am on F11 and the the HDD is Samsung HD320KJ - nothing exotic.
I have bad sectors on my HDD and there is no option to repair them - the S.M.A.R.T. provides only information and an option of erasing the whole disk, and also a notification that my hard disk is sliding down. I disabled the notification, but the problem remains.
I found .iso image of HUTIL on the website of Samsing, burned it on a CD and it detects at the Read Surface Scan test one bad sector, allocated to C:10992 H:1 S:1379 Ecc error
I expect when I write in the linux terminal: badblocks -r /dev/sda:10992 H:1 S:1379
to repair the bad sector, allocating the data somewhere else - however nothing of the kind is anticipated.
Regards
13 years, 6 months