Re: digikam and kipi-plugins?
by Rex Dieter
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
empty?
-- Rex
4 years, 3 months
Mouse Wheel gone
by Christian Menzel
Since the latest xorg-X11 upgrade I receive the already mentioned XKB
error and the mouse wheel is not working anymore.
Has anybody seen this behavior?
Regards
Chris
4 years, 3 months
Re: NFS failure
by Fulko.Hew＠sita.aero
Damian Menscher <menscher(a)uiuc.edu>@redhat.com on 04/07/2004 04:57:13 PM
wrote:
> 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
logs.
> > 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.
4 years, 3 months
Re: Test GIMP 2.7/2.8 ?
by Valent Turkovic
On Fri, 09 Oct 2009 18:34:25 +0000, Valent Turkovic wrote:
> I there a way to test new GIMP 2.7/2.8 in Fedora? I looked in Rawhide
> repos and I still see only 2.6x versions there. Any plans to put 2.7 in
> Rawhide repost for testing purposes?
Should I ask on development channel?
--
pratite me na twitteru - www.twitter.com/valentt
http://kernelreloaded.blog385.com/
linux, blog, anime, spirituality, windsurf, wireless
registered as user #367004 with the Linux Counter, http://counter.li.org.
ICQ: 2125241, Skype: valent.turkovic
10 years, 1 month
Bugzilla semantics: marking bugs as triaged
by Adam Williamson
I had interesting discussions with Andy Lindeberg and jlaska today about
the semantics of our current Bugzilla - and particularly triage -
workflow.
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
fully completed).
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
impossible.
We'd be interested in thoughts - negative, positive, whatever - on the
idea. Thanks!
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net
10 years, 1 month
May I safely execute yum-complete-transaction?
by Clemens Eisserer
Hi,
I had a power shortage while I ran "yum update". After booting up, yum
told me to run yum-complete-transaction.
However yum-complete-transaction reported (see attachement), it would:
Install 7 Package(s)
Upgrade 205 Package(s)
Remove 209 Package(s)
So I canceld, afraid of having a lot of stiff accidentially removed.
Is it safe to let yum-complete-transaction continue?
Thanks, Clemens
10 years, 3 months
some odd package group selections in f12 beta
by Robert P. J. Day
finally getting around to f12 beta, and some of the groupings of
software seem a bit odd.
* wouldn't "publican" make sense under "Authoring and Publishing"?
and perhaps "xmlto"? others?
* under Editors, what about gedit? nano? pico?
* how did minicom end in "Electronic Lab"?
* under Servers, why does "Directory Server" represent samba, while
"Windows File Server" represents system-config-samba? that's just
weird, isn't it?
* i'm sure i'll regret asking this, but why isn't "httpd" listed under
"Web Server"?
you get the idea.
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Kernel Pedantry.
Web page: http://crashcourse.ca
Twitter: http://twitter.com/rpjday
========================================================================
10 years, 3 months
VMware Workstation on F12B...
by Christopher A Williams
For those of you following the story, there is a thread on the VMware
Communities thread about VMware Workstation 7 and it's issues running on
Fedora 12 Beta.
You can find the entire sad story at:
http://communities.vmware.com/thread/239371?tstart=15
and (also referenced in the thread above)
http://communities.vmware.com/thread/229891?tstart=0
It's apparently an issue with glibc versions that is apparently at the
core. Hopefully we'll see this get worked out by the respective Fedora
and VMware teams by the time F12 releases. In the meantime, it looks
like we will have to wait for the zealots on both sides to stop fussing
and actually get to fixing the problem.
Cheers,
Chris
--
=============================
"You see things as they are and ask, 'Why?'
I dream things as they never were and ask, 'Why not?'"
-- George Bernard Shaw
10 years, 3 months
