Per Bothner wrote:
> The Rawhide version of digikam is the very latest (0.10.0-rc1),
> but it fails to find any of the "Kipi plugins", even though I've
> installed the kipi-plugins package. This might be an upstream
> issue, since 0.10.0 is pretty bleeding edge and the kipi-plugins
> may even more bleeding-edge. Gwenview does seem to be see the
> plugins, so I'm wondering if there is there might be a
> Fedora-specific problem before I complain upstream ...
The f10 builds seem to work fine for me (finding the plugins), so perhaps
this is rawhide-specific?
To be clear, digikam's Settings -> configure digikam -> Kipi Plugins is
Damian Menscher <menscher(a)uiuc.edu>@redhat.com on 04/07/2004 04:57:13 PM
> On Wed, 7 Apr 2004, Jeff Elkins wrote:
> > I'm getting failure messages on my nfs mounts i.e. :
> > mount to NFS server 'music.elkins' failed: server is down.
> > nsfd appears to be running and I didn't see anything suspicious in the
> > The servers are up and running and have other clients connected.
> You didn't mention what steps you took to debug it:
> Can you ping the server?
> What is the output of rpcinfo -p servername?
> Does the server have access restrictions (firewall, TCP Wrappers, etc)?
I have the same symptoms...
rpcinfo says that nfs et.al. are running.
Something has changed in test 2, since the same PC running RH9
accesses that host just fine.
I had interesting discussions with Andy Lindeberg and jlaska today about
the semantics of our current Bugzilla - and particularly triage -
We were thinking about the NEW / ASSIGNED dichotomy, and Andy and I came
to the conclusion that it doesn't really make a lot of sense.
Right now, Bugzappers uses it one way, Andy uses it another for
anaconda. In the Bugzappers process, ASSIGNED just means, really,
Triaged: you set a bug to ASSIGNED once the triage process is complete.
For Anaconda, Andy sets bugs to ASSIGNED once they're assigned to the
correct anaconda maintainer (whether or not the rest of triage is yet
Neither case is really terribly problematic, but they also don't make a
whole lot of sense, really. Having 'triage completed' as a status is a
bit arguable; it's not quite in the flow of the statuses, as a bug could
be at a point 'beyond' ASSIGNED but not yet have been triaged, for
instance. And it's also just semantically wrong - the word 'assigned'
does not mean 'triaged'.
In the anaconda case, we just thought about it and decided the use of
ASSIGNED isn't really _achieving_ anything: you can tell whether the
bug's been assigned or not just by looking at who it's assigned to.
We sort of came to the conclusion that it'd probably make the most sense
to have a 'Triaged' keyword that's used to affirm that a bug's been
triaged (in fact there already is one, but it's not officially used in
our current process), and abandon the distinction between NEW and
ASSIGNED. Ideally, the ASSIGNED state would just be removed, but we
could keep it and just note in our workflow / policy that it's not
really used to mean anything in particular.
This could, I think, be implemented quite quickly if desired; I think we
could rig something up to set all bugs in ASSIGNED state (except
anaconda ones) to have the 'Triaged' keyword, that shouldn't be
We'd be interested in thoughts - negative, positive, whatever - on the
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
Is it possible to "preupgrade" to rawhide? I would very much like to
test this, since a "normal" installation won't work on my system. (See
Ian Pilcher arequipeno(a)gmail.com
This has been rather annoying on my laptop, but I am getting constant
kernel oopses with my WiFi and broadband adapters. This is on a ThinkPad
T400. It usually happens when I connect or disconnect USB devices, which
includes my broadband adapter. A trace from an example happening with my
WiFi adapter is below.
Anyone else having these issues, or is it just me and something I may or
may not have done?
Kernel failure message 1:
------------[ cut here ]------------
WARNING: at drivers/net/wireless/iwlwifi/iwl-sta.c:728
iwl_set_dynamic_key+0x1d9/0x443 [iwlcore]() (Not tainted)
Hardware name: 2765T6U
no space for new kewModules linked in: usb_storage aes_x86_64
aes_generic fuse rfcomm bridge stp llc bnep sco l2cap vmnet ppdev
parport_pc parport vmblock vmci vmmon sunrpc ip6t_REJECT
nf_conntrack_ipv6 ip6table_filter ip6_tables ipv6 cpufreq_ondemand
acpi_cpufreq freq_table dm_multipath uinput snd_hda_codec_conexant
snd_hda_intel snd_hda_codec arc4 ecb snd_hwdep iwlagn snd_pcm iwlcore
snd_timer firewire_ohci snd firewire_core lib80211 thinkpad_acpi
soundcore btusb mac80211 yenta_socket i2c_i801 hwmon snd_page_alloc
e1000e crc_itu_t iTCO_wdt rsrc_nonstatic wmi pcspkr bluetooth cfg80211
iTCO_vendor_support joydev i915 drm i2c_algo_bit i2c_core video output
[last unloaded: microcode]
Pid: 11, comm: events/1 Not tainted 188.8.131.52-155.fc11.x86_64 #1
[<ffffffff81186570>] ? selinux_d_instantiate+0x1c/0x1e
[<ffffffff8117f82b>] ? security_d_instantiate+0x24/0x26
[<ffffffff8117f9eb>] ? security_inode_permission+0x21/0x23
[<ffffffffa019202a>] iwl_set_dynamic_key+0x1d9/0x443 [iwlcore]
[<ffffffffa01c7cbd>] iwl_mac_set_key+0x245/0x3a0 [iwlagn]
[<ffffffff8117160f>] ? debugfs_remove+0x16/0x65
[<ffffffffa010cd64>] __ieee80211_key_todo+0x156/0x24b [mac80211]
[<ffffffffa010cf8b>] ? key_todo+0x0/0x10 [mac80211]
[<ffffffffa010cf7d>] ieee80211_key_todo+0x1a/0x28 [mac80211]
[<ffffffffa010cf99>] key_todo+0xe/0x10 [mac80211]
[<ffffffff8105ca4b>] ? autoremove_wake_function+0x0/0x39
[<ffffffff81058ead>] ? worker_thread+0x0/0xfd
[<ffffffff81058ead>] ? worker_thread+0x0/0xfd
[<ffffffff81011f67>] ? restore_args+0x0/0x30
[<ffffffff8105c668>] ? kthread+0x0/0x78
[<ffffffff81012640>] ? child_rip+0x0/0x20
---[ end trace 8824362b81a62bd1 ]---
"Only two things are infinite,
the universe and human stupidity,
and I'm not sure about the former."
-- Albert Einstein
I have this slightly used hard drive which some kind soul (bless you,
sir) popped into a rather thinly padded mailer and tossed in the U. S.
Postal mail. It arrived today in my mailbox, and no doubt experienced
numerous bumps, shoves, crushes, and hard landings between the origin
and destination. Assuming the thing actually works correctly when I plug
it into a system and switch the power on, I'd like to try out Fedora 12.
How do I actually install to the hard drive from rawhide? I don't think
I tried that before.
our guide for livecd creation used for test days  have been
outdated (used F11 packages as a repository). I have rewritten
it to use Rawhide packages for building, which is preferred
for test days. I have also added some info what to do if rawhide
repository is currently broken. Hope that helps.
There is one issue which should be discussed: The default
kickstart scripts remove fedora-logos package because of
trademark issues with non-official spins. I have added it back
for test days spins. Is that ok? If someone thinks it is not,
it's not a problem to modify it, just tell me.
FYI, with current rawhide, Adobe Reader (I tried 9.1.2 and 9.1.3)
crashes on startup. I sent a crash dump to Adobe and suggested that
they might want to try to get it fixed before Fedora 12 is released, but
I'm not holding my breath.