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
5 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
5 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.
5 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
11 years, 1 month
kstartupconfig4 error
by Jim Bevier
I did an i386 upgrade from F11 -> F12 on two different systems using the install
DVD. They both use gnome and kde desktops. After the upgrade, I try to log in
using kde and I get the error: "kstartupconfig4 does not exist or fails. The
error code is 127. Check your installation". After some searching, I found
this same error was present in F10->F11 upgrade. It seems during the upgrade,
libssl.so.8 and libcrypto.so.8 links are removed and kstartupconfig4 can no
longer start. In /usr/lib I did "ln -s libssl.so libssl.so.8" and "ln -s
libcrypto.so libcrypto.so.8". This then allowed kstartupconfig4 to run and kde
worked again. I did not see any mention of this problem on the rawhide list
during beta & RC testing, so I guess nobody did this type of upgrade. Hope this
helps someone.
Jim
11 years, 1 month
Proposal for new QA test for L10N
by Noriko Mizumoto
Hi QA team
I am Noriko Mizumoto, coming from Fedora Localization Project.
As we are in scheduling period, I'd like to propose new QA test to be
created. Here is the detail.
I am quite new to QA activity, so it would be highly appreciated for
your guidance.
[Introduction]
For software translations, FLP translators work on PO file so they never
know where particular string to be appeared in UI. The Build release
packages for review allows translators to review their work in UI with
the aspect of QA and to give a chance for correction.
This event have been proposed by FLSCo and approved by FESCo [1].
[Test Strategy]
This is the course of events order which can be found in the schedule [2].
1) Software String Freeze
(*Request f-dev-announcement for Build F13 pkgs with latest translation
for L10n Review)
2) Software Translation Period (POT to PO)
3) Build F-13 collection packages for all language translators
4) Review and correct software translation in built UI
5) Software: Translation Deadline (PO Files complete)
6) Software: Start Rebuild all translated packages
7) Software: Rebuild all translated packages
8) Beta Freeze
At 3), all F13 packages will be built with latest translation by
packagers. Then at the end of 3), Live Image needs to be crated for QA.
[Test Priority]
n/a
[Scope]
All components (packages) under F13 release [3].
[Test Pass/Fail Criteria]
The test will be completed at the deadline date.
See, 5) Software: Translation Deadline (PO Files complete)
7 Test Deliverables
* High quality of translation
* Bugs will be filed against package(s) which shows problem in
translation [4].
[Test Cases]
"Instruction" for consistent test to be created and posted.
[Test Environment]
n/a
[Responsibilities]
Packagers: Build packages with latest translation
Translators: QA test for translation quality
QA: Create Live image
[Schedule]
See test strategy.
[Risks]
Package not built according to the schedule by packagers.
If this happens, that package will not display latest translation in UI
making unable to review.
To prevent this, the request (shown with bracket in the above) will be
sent to f-devel-announce before 3) Build F-13 collection packages for
all language translators.
[Reviewers]
?
[References]
[1]:https://fedorahosted.org/fesco/ticket/243
[2]:http://poelstra.fedorapeople.org/schedules/f-13/f-13-all-tasks.html
[3]:https://translate.fedoraproject.org/languages/nl/collection/fedora/fed...
[4]:https://fedoraproject.org/wiki/L10N/UpdatePot
Thanks
noriko
11 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
11 years, 1 month
waiting for gstreamer?
by Per Bothner
This is slightly off-topic, as it is about F12, not Rawhide.
However, it's a relatively recent failure in a full-updated D12,
so it's not *too* far off-topic, I hope!
The problem is that neither amarok nor digikam nor rhythmbox
will start up. rhythmbox does nothing. The two KDE application
(run under Gnome and metacity) will put up a splash screen, and
then hang.
In the case of digikam it looks like Phonon is waiting on gstreamer,
based on a gdb stack-trace (with digikam compiled from source):
0 0x00d1a416 in __kernel_vsyscall ()
#1 0x007d2f25 in ppoll () from /lib/libc.so.6
#2 0x01f13e41 in gst_poll_wait () from /usr/lib/libgstreamer-0.10.so.0
#3 0x01f10ab6 in ?? () from /usr/lib/libgstreamer-0.10.so.0
#4 0x01f123b4 in ?? () from /usr/lib/libgstreamer-0.10.so.0
#5 0x01f1cfe9 in gst_update_registry () from
/usr/lib/libgstreamer-0.10.so.0
#6 0x01ec90d2 in ?? () from /usr/lib/libgstreamer-0.10.so.0
#7 0x00e34100 in g_option_context_parse () from /lib/libglib-2.0.so.0
#8 0x01ec86fe in gst_init_check () from /usr/lib/libgstreamer-0.10.so.0
#9 0x027b5362 in ?? ()
from /usr/lib/kde4/plugins/phonon_backend/phonon_gstreamer.so
#10 0x027b5781 in qt_plugin_instance ()
from /usr/lib/kde4/plugins/phonon_backend/phonon_gstreamer.so
#11 0x06133df4 in QPluginLoader::instance() () from /usr/lib/libQtCore.so.4
#12 0x07d0e51b in ?? () from /usr/lib/kde4/plugins/phonon_platform/kde.so
#13 0x07d0f791 in ?? () from /usr/lib/kde4/plugins/phonon_platform/kde.so
#14 0x02513ee4 in ?? () from /usr/lib/libphonon.so.4
#15 0x02514d83 in Phonon::Factory::backend(bool) ()
from /usr/lib/libphonon.so.4
#16 0x0250ec9a in
Phonon::GlobalConfig::audioOutputDeviceListFor(Phonon::Category, int)
const () from /usr/lib/libphonon.so.4
#17 0x0250f500 in
Phonon::GlobalConfig::audioOutputDeviceFor(Phonon::Category, int) const
() from /usr/lib/libphonon.so.4
#18 0x0250a3b6 in ?? () from /usr/lib/libphonon.so.4
#19 0x0251adeb in ?? () from /usr/lib/libphonon.so.4
#20 0x0251b0f1 in Phonon::VideoPlayer::VideoPlayer(Phonon::Category,
QWidget*)
() from /usr/lib/libphonon.so.4
#21 0x082ef06a in Digikam::MediaPlayerView::MediaPlayerView (
this=<value optimized out>, parent=<value optimized out>)
at
/home/bothner/Software/digikam-1.0.0-rc/digikam/mediaplayerview.cpp:107
#22 0x08279ea0 in Digikam::AlbumWidgetStack::AlbumWidgetStack (
this=<value optimized out>, parent=<value optimized out>)
at
/home/bothner/Software/digikam-1.0.0-rc/digikam/albumwidgetstack.cpp:109
#23 0x082aee4e in Digikam::DigikamView::DigikamView (
this=<value optimized out>, parent=<value optimized out>)
at /home/bothner/Software/digikam-1.0.0-rc/digikam/digikamview.cpp:215
#24 0x08295160 in Digikam::DigikamApp::setupView (this=<value optimized
out>)
at /home/bothner/Software/digikam-1.0.0-rc/digikam/digikamapp.cpp:493
#25 0x082a3933 in Digikam::DigikamApp::DigikamApp (this=<value optimized
out>,
__in_chrg=<value optimized out>, __vtt_parm=<value optimized out>)
at /home/bothner/Software/digikam-1.0.0-rc/digikam/digikamapp.cpp:232
#26 0x083a24fa in main (argc=<value optimized out>, argv=<value
optimized out>)
at /home/bothner/Software/digikam-1.0.0-rc/digikam/main.cpp:172
rhythmbox also hangs in gstreamer.
One data-point which might be relevant: I briefly experimented
with xmonad (if it had a less steep learning-curve, including
better mouse support and easier defaults I might have stuck with
it). After than the desktop icons are gone, and I can no longer
open a terminal by right-clicking the desktop (nautilus-open-terminal).
I'm not sure if the these failures predate or postdate the
xmonad experiment, but it's possible that switching to xmodad
might have done something nasty.
--
--Per Bothner
per(a)bothner.com http://per.bothner.com/
11 years, 1 month