GNOME 3 Fallback Mode
by Andrew Haley
I'm trying to run F15 beta LiveCD in a virtual machine, but I get
a complaint that GNOME 3 failed to load and is running in fallback
mode. Is there any way to make it work properly when virtualized?
Andrew.
13 years
Status of pino in F15
by Alex Hudson
Hi all,
I apologise if this sounds like a bit of an extended whinge; it's not
meant to but I'm not sure how better to raise these issues.
I've spent a half-hour this morning going through various bits of pino
and raising appropriate bugs, as I'm now using F15 as my full-time
system (and I'm a heavy user of pino from F14).
Now, pino in F14 wasn't great particularly with the issues around
twitter support. I don't know what has happened since then, though, but
it's basically unusable now. Feel free to go through my bugs, but as
highlights:
* it doesn't minimise anywhere on the gnome3 desktop
* it doesn't automatically refresh
* clicking on friend's names gets a / filesystem listing
In addition, [re] tweeting/denting fails randomly in a pattern I've not
yet been able to nail down for a bug report, there are large chunks of
unfinished UI and stuff which plain doesn't work. I bz'd the missing
menu items; there are also icons and right-click menu items which do
nothing.
Now, pino is currently a default package in the "Graphical Internet". I
would argue that right now, unless there is some super-ninja plan, it
should be demoted to optional at best. It should not be on the live CD
in this state.
I apologise for bringing this up so late in the beta cycle - I'm sure
the beta is spinning as I type - but I honestly don't think it can ship
in this state.
Cheers
Alex.
--
This message was scanned by Better Hosted and is believed to be clean.
http://www.betterhosted.com
13 years
Fedora 15 / Gnome 3 gotchas
by Camilo Mesias
Hi,
I made some noises on IRC about people upgrading to F15 (like myself)
who would all come across the same surprises and would have to find a
way to work around them. I suggested it might help to publish
something like release notes but more user oriented, to help to ease
the pain (and to defuse the many questions that will undoubtedly find
their way to the various support forums). At the time no-one seemed to
pick up on the idea.
I wrote a blog post about it, maybe not the best way to help Fedora
users so feel free to take the idea and the content and repackage it
as appropriate.
http://littlethorpe.net/wordpress/?p=334 "Fedora 15 Gnome 3 gotchas"
If nothing else maybe I have included the right words so that users
can Google for 'what the heck happened to my minimise button' or
whatever and find some help.
-Cam
13 years
Haskell packaging questions
by Andrew McNabb
I recently came across an issue in a package review where I would
appreciate guidance. In particular, I have never dealt with Haskell
packages before, and I haven't been able to find enough detail in the
Haskell Packaging Guidelines to answer my questions:
http://fedoraproject.org/wiki/Packaging/Haskell
It seems that there's a tool called cabal2spec that autogenerates spec
files for Haskell programs. However, the spec files that it outputs are
a little unusual.
The spec file I'm reviewing has no %package sections and no %files
sections. Instead, there is a reference to a "%{?ghc_lib_package}"
macro that implicitly defines the package and two subpackages. The
Haskell Packaging Guidelines don't seem to describe how all of the magic
works, so I'm not quite sure what standards I'm supposed to use in my
review. Here's a link to the package request:
https://bugzilla.redhat.com/show_bug.cgi?id=662258
It looks like other Haskell libraries are packaged in a similar way, but
it's enough different from most packages that the Package Review
Guidelines don't seem to cleanly apply. I would appreciate advice on
how to proceed. Thanks.
--
Andrew McNabb
http://www.mcnabbs.org/andrew/
PGP Fingerprint: 8A17 B57C 6879 1863 DE55 8012 AB4D 6098 8826 6868
13 years
Resetting network devices between ifconfig level and desktop level
by Aaron Gray
Hope no one minds me writing to the devel list but I got no reply on user list.
I have got inconsistent eth devices between what Fedora Gnome Desktop
is telling me and what ifconfig is telling me and what 'service
network restart' is telling me.
Do I have to do a reinstall or is there some way of resetting things ?
Many thanks in advance,
Aaron
13 years
wireless-tools is DEPRECATED
by Xose Vazquez Perez
hi,
wireless-tools is deprecated since time ago. iw/rfkill
should be used instead it.
these packages still depend on it:
conky
dracut-modules-olpc
i3status
knemo
olpc-netutils
python-iwlib
wavemon
weplab
wicd
wifi-radar
wifiroamd
wlassistant
xsupplicant
https://bugzilla.redhat.com/show_bug.cgi?id=687924
--
«Allá muevan feroz guerra, ciegos reyes por un palmo más de tierra;
que yo aquí tengo por mío cuanto abarca el mar bravío, a quien nadie
impuso leyes. Y no hay playa, sea cualquiera, ni bandera de esplendor,
que no sienta mi derecho y dé pecho a mi valor.»
13 years
libevent-1.4.13 compatbility
by Matej Cepl
Hi,
I am trying to package forked-daapd and it depends on libevent 1.4.13.
When asking forked-daapd's maintainer about the compatibility with
libevent2, I've got this into reply:
libevent2 is not and will not be supported; you need to use
libevent 1.4.x.
Which I guess means either I'd have to package libevent1 for Fedora
(which seems to be PITA ... files have same names etc.), or patch
forked-daapd to use libevent2 and maintain the patch.
What's so horrible about libevent2 that the upstream author won't
support it? Is it that difficult to make and maintain the patch for
libevent2 compatiblity?
Non-building experiemntal draft of the package is at
http://mcepl.fedorapeople.org/tmp/forked-daapd-0.14-0.fc15.src.rpm (you
need also avl package from -testing to build it).
Any ideas?
Best,
Matěj
13 years
F15 and Broadcom BCM4313
by Jos Vos
Hi,
I'm testing a netbook using the F15 Beta Live image. That netbook has
a Broadcom BCM4313 wifi chipset, of which I can find several problem
reports and the same number of answers, with or without success reports.
The lspci -v output (I've zeroed the S/N in the output):
02:00.0 Network controller: Broadcom Corporation BCM4313 802.11b/g LP-PHY (rev 01)
Subsystem: Device 1a3b:2047
Flags: bus master, fast devsel, latency 0, IRQ 10
Memory at fbffc000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [40] Power Management version 3
Capabilities: [58] Vendor Specific Information: Len=78 <?>
Capabilities: [48] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [d0] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [13c] Virtual Channel
Capabilities: [160] Device Serial Number 00-00-00-00-00-00-00-00
Capabilities: [16c] Power Budgeting <?>
Two questions:
- Can I get this chip working (as a test) using the Live USB-stick, so
that I can verify the correct working without actually installing
Fedora on the disk? (Wired Ethernet is working to retrieve external
stuff when needed.)
- Is this chipset expected to start working without any additional
tweaks during the F15 life cycle?
Thx,
--
-- Jos Vos <jos(a)xos.nl>
-- X/OS Experts in Open Systems BV | Phone: +31 20 6938364
-- Amsterdam, The Netherlands | Fax: +31 20 6948204
13 years
Avoiding conditioning ignorance towards AutoQA
by Tim Niemueller
Hi fellow Fedorans.
Recently, AutoQA has been introduced to catch typical problems early in
the update process. In general, I appreciate that effort, but currently
I find myself in a phase of conditioning ignorance towards AutoQA,
essentially because it is drowning me in irrelevant information. The
current case why I'm writing is
https://admin.fedoraproject.org/updates/lua-wsapi-1.3.4-4.fc15.
Here are two ideas to make AutoQA relevant, less time-consuming, and
more helpful. In short: good QA is always quiet, only if there is a
problem it communicates.
- Post only errors
It is common, for example, in automated build or continuous integration
systems to send out emails only on errors. Similar goes for Unix tools,
which tend to be quiet if everything is ok, and only bother you with
output if something is not. Therefore, I propose to have AutoQA messages
posted only in case that there has been an error.
- Accumulate error messages
An email is sent for every single comment to Bodhi. In the case of
AutoQA, it causes one email per platform. It increases the load of email
tremendously to deal with, which in turn makes me ignore it. Therefore,
I propose to accumulate messages for all platforms. Combined with the
earlier proposal, the states for all platforms should be collected by an
intermediate node, and if and only if a test failed on any of the
platforms, one message with all status messages is posted to the update.
On a related note: it'd be much appreciated if Bodhi would provide an
option to get a daily digest with all comments of all the packages I'm
involved with.
I hope the fine folks of the AutoQA effort take these proposals into
account when proceeding in the development of the system and help me to
stop ignorance from taking over.
Regards,
Tim
--
Tim Niemueller <tim(a)niemueller.de> www.niemueller.de
=================================================================
Imagination is more important than knowledge. (Albert Einstein)
13 years
