NSS libraries prevent prelinking?
by Bill Crawford
I know that libfreebl3.so and libsoftokn3.so have been blacklisted for
prelinking for quite some time now (it's there in F8, and I think earlier) but
now that libcrypt is linked against libfreebl3.so, it seems an increasing
number of other libraries / plugins / programs are now excluded due to the
dependency on libfreebl3.so.
Is there any way to avoid this? As time goes on, more and more programs and
plugins (like the kde address book / calendar) are relying on encryption and /
or signing, and starting to link against nss.
15 years, 1 month
F-Spot error connecting to camera
by Gianluca Cecchi
rawhide x86_64.
Connecting a kodak cx7525 camera to my usb port I get in messages:
Apr 22 15:48:39 localhost kernel: usb 5-1: new full speed USB device
using uhci_hcd and address 3
Apr 22 15:48:39 localhost kernel: usb 5-1: New USB device found,
idVendor=040a, idProduct=0586
Apr 22 15:48:39 localhost kernel: usb 5-1: New USB device strings:
Mfr=1, Product=2, SerialNumber=3
Apr 22 15:48:39 localhost kernel: usb 5-1: Product: KODAK EasyShare
CX7525 Zoom Digital Camera
Apr 22 15:48:39 localhost kernel: usb 5-1: Manufacturer: Eastman Kodak Company
Apr 22 15:48:39 localhost kernel: usb 5-1: SerialNumber: KCKDU51000386
Apr 22 15:48:39 localhost kernel: usb 5-1: configuration #1 chosen from 1 choice
but opening with F-SPot I get an error window saying:
title: error connecting to camera
text: received error "could not lock the device" while connecting to camera
it seems that possible reason is that I was asked two times (so two
windows) about what to do.... and in fact in file browser I have two
lines with it....
retrying, it seems I get, as soon as I plug the usb cable:
1 window with error "unable to mount kodak co cx7525" error
initializing camera: -60: could not lock the device
1 window proposing to open with gthumb image viewer
1 window proposing to open with gthumb image viewer
Gianluca
15 years, 1 month
rawhide report: 20090423 changes
by Fedora compose checker
Compose started at Thu Apr 23 06:15:04 UTC 2009
New package perl-B-Hooks-OP-Check
Wrap OP check callbacks
New package perl-Test-Aggregate
Aggregate C<*.t> tests to make them run faster
New package photoprint
Utility for printing digital photographs
New package python-arm4
Application Reponse Measurement (ARM) V4 Python language bindings
Updated Packages:
deltarpm-3.4-16.fc11
--------------------
* Wed Apr 22 2009 Jonathan Dieter <jdieter(a)gmail.com> - 3.4-16
- Split drpmsync into a separate subpackage (#489231)
desktop-backgrounds-9.0.0-8
---------------------------
* Wed Apr 22 2009 Tom "spot" Callaway <tcallawa(a)redhat.com> - 9.0.0-8
- fix compat subpackage
erlang-R12B-5.7.fc11
--------------------
* Tue Apr 21 2009 Debarshi Ray <rishi(a)fedoraproject.org> R12B-5.7
- Updated rpath patch.
- Fixed configure to respect $RPM_OPT_FLAGS.
fedora-logos-11.0.4-1.fc11
--------------------------
* Wed Apr 22 2009 Tom "spot" Callaway <tcallawa(a)redhat.com> 11.0.3-1
- update to 11.0.3, adds KDE splash
* Wed Apr 22 2009 Tom "spot" Callaway <tcallawa(a)redhat.com> 11.0.4-1
- update to 11.0.4, fix art to actually be in leonidas theme
gdm-2.26.1-3.fc11
-----------------
* Wed Apr 22 2009 Ray Strode <rstrode(a)redhat.com> - 1:2.26.1-3
- Add temporary hack to smack down misbehaving PAM modules
* Tue Apr 21 2009 Ray Strode <rstrode(a)redhat.com> - 1:2.26.1-2
- Stop inactive pam conversations when one succeeds.
Should fix bug 496234
globus-common-10.2-3.fc11
-------------------------
* Tue Apr 21 2009 Mattias Ellert <mattias.ellert(a)fysast.uu.se> - 10.2-3
- Put GLOBUS_LICENSE file in extracted source tarball
* Thu Apr 16 2009 Mattias Ellert <mattias.ellert(a)fysast.uu.se> - 10.2-2
- Remove config.guess file
gnome-power-manager-2.26.0-2.fc11
---------------------------------
* Sat Apr 18 2009 Lubomir Rintel <lkundrak(a)v3.sk> - 2.26.0-2
- Fix broken battery capacity percentage reporting
gnomint-0.9.1-3.fc11
--------------------
* Tue Apr 21 2009 Adam Huffman <bloch(a)verdurin.com> - 0.9.1-3
- fix for bug 496518 - $RPM_OPT_FLAGS not used
javasqlite-20090409-3.fc11
--------------------------
* Mon Apr 20 2009 Ville Skyttä <ville.skytta at iki.fi> - 20090409-3
- Disable extension loading due to security concerns.
leonidas-kde-theme-0.2.2-4.fc11
-------------------------------
* Wed Apr 22 2009 Jaroslav Reznik <jreznik(a)redhat.com> 0.2.2-4
- our own logos for both fedora and generic version
libatasmart-0.12-2.fc11
-----------------------
* Wed Apr 22 2009 Lennart Poettering <lpoetter(a)redhat.com> 0.12-2
- Properly handle some ST and FUJITSU drive attributes. (rhbz 496087, 497107)
libchewing-0.3.2-8.fc11
-----------------------
* Wed Apr 22 2009 Ding-Yi Chen <dchen at redhat dot com> - 0.3.2-8
- Fix [Bug 496968] - libchewing-debuginfo does not contain sources.
pulseaudio-0.9.15-11.fc11
-------------------------
* Wed Apr 22 2009 Warren Togami <wtogami(a)redhat.com> 0.9.15-11
- Bug #497214
Do not start pulseaudio daemon if PULSE_SERVER directs pulse elsewhere.
tsclient-2.0.2-3.fc11
---------------------
* Wed Apr 22 2009 Matthias Clasen <mclasen(a)redhat.com> - 2.0.2-3
- Fix some wrong ids in the glade file to make the ui work (#485976)
wesnoth-1.6.1-2.fc11
--------------------
* Tue Apr 21 2009 Debarshi Ray <rishi(a)fedoraproject.org> - 1.6.1-2
- Respect $RPM_OPT_FLAGS, BZ 496897.
xorg-x11-drv-nouveau-0.0.12-31.20090421git47bb00f.fc11
------------------------------------------------------
* Tue Apr 21 2009 Ben Skeggs <bskeggs(a)redhat.com> 0.0.12-30.20090421git47bb00f
- fix for rh#489101
* Tue Apr 21 2009 Ben Skeggs <bskeggs(a)redhat.com> 0.0.12-31.20090421git47bb00f
- fix for rh#496559
Summary:
Added Packages: 4
Removed Packages: 0
Modified Packages: 16
Broken deps for i386
----------------------------------------------------------
gnome-desktop-sharp-2.26.0-1.fc11.i586 requires libnautilus-burn.so.4
gnome-python2-nautilus-cd-burner-2.26.0-1.fc11.i586 requires libnautilus-burn.so.4
nssbackup-0.2-0.2.rc7.fc10.noarch requires python(abi) = 0:2.5
python-arm4-1.1-3.fc10.i386 requires libpython2.5.so.1.0
python-arm4-1.1-3.fc10.i386 requires python(abi) = 0:2.5
sems-ivr-1.1.0-5.fc10.i386 requires libpython2.5.so.1.0
sems-python-1.1.0-5.fc10.i386 requires libpython2.5.so.1.0
sems-xmlrpc2di-1.1.0-5.fc10.i386 requires libssl.so.7
Broken deps for x86_64
----------------------------------------------------------
gnome-desktop-sharp-2.26.0-1.fc11.x86_64 requires libnautilus-burn.so.4()(64bit)
gnome-python2-nautilus-cd-burner-2.26.0-1.fc11.x86_64 requires libnautilus-burn.so.4()(64bit)
nssbackup-0.2-0.2.rc7.fc10.noarch requires python(abi) = 0:2.5
python-arm4-1.1-3.fc10.x86_64 requires libpython2.5.so.1.0()(64bit)
python-arm4-1.1-3.fc10.x86_64 requires python(abi) = 0:2.5
sems-ivr-1.1.0-5.fc10.x86_64 requires libpython2.5.so.1.0()(64bit)
sems-python-1.1.0-5.fc10.x86_64 requires libpython2.5.so.1.0()(64bit)
sems-xmlrpc2di-1.1.0-5.fc10.x86_64 requires libssl.so.7()(64bit)
Broken deps for ppc
----------------------------------------------------------
fedora-ksplice-0.5-3.fc11.noarch requires ksplice
gnome-desktop-sharp-2.26.0-1.fc11.ppc requires libnautilus-burn.so.4
gnome-python2-nautilus-cd-burner-2.26.0-1.fc11.ppc requires libnautilus-burn.so.4
nssbackup-0.2-0.2.rc7.fc10.noarch requires python(abi) = 0:2.5
python-arm4-1.1-3.fc10.ppc requires libpython2.5.so.1.0
python-arm4-1.1-3.fc10.ppc requires python(abi) = 0:2.5
sems-ivr-1.1.0-5.fc10.ppc requires libpython2.5.so.1.0
sems-python-1.1.0-5.fc10.ppc requires libpython2.5.so.1.0
sems-xmlrpc2di-1.1.0-5.fc10.ppc requires libssl.so.7
Broken deps for ppc64
----------------------------------------------------------
cabal2spec-0.12-1.fc11.noarch requires ghc > 0:6.10.1-7
fedora-ksplice-0.5-3.fc11.noarch requires ksplice
gnome-python2-nautilus-cd-burner-2.26.0-1.fc11.ppc64 requires libnautilus-burn.so.4()(64bit)
kimono-4.2.2-5.fc11.ppc64 requires libmono.so.0(VER_1)(64bit)
kimono-4.2.2-5.fc11.ppc64 requires libmono.so.0()(64bit)
nssbackup-0.2-0.2.rc7.fc10.noarch requires python(abi) = 0:2.5
python-arm4-1.1-3.fc10.ppc64 requires libpython2.5.so.1.0()(64bit)
python-arm4-1.1-3.fc10.ppc64 requires python(abi) = 0:2.5
qyoto-devel-4.2.2-5.fc11.ppc64 requires mono-devel
sems-ivr-1.1.0-5.fc10.ppc64 requires libpython2.5.so.1.0()(64bit)
sems-python-1.1.0-5.fc10.ppc64 requires libpython2.5.so.1.0()(64bit)
sems-xmlrpc2di-1.1.0-5.fc10.ppc64 requires libssl.so.7()(64bit)
sublib-0.9-4.fc11.ppc64 requires mono(mscorlib) = 0:2.0.0.0
sublib-0.9-4.fc11.ppc64 requires mono(System) = 0:2.0.0.0
15 years, 1 month
File system corruption this morning
by Brian Vuyk
Just booted my system this morning to find that it wouldn't boot. It
dumped me to a prompt with a suggestion to run fsck. Running fsck showed
that there was an incorrect free block count (I think). Once the fsck
run was done, I rebooted, and it booted to the login prompt with no issues.
This was for the partition mounting '/', I believe. It's ext4. All my
partitions are set up as LVM logical partitions.
I apologize for not taking note of more detail. My first instinct is to
fix it, and I tend to forget about the details.
--
*Brian Vuyk*
Web Design & Development
T: 613-534-2916
Skype: brianvuyk
brian(a)brianvuyk.com | http://www.brianvuyk.com
15 years, 1 month
Can't Log Into KDE after update.
by Kadon
After updating to these packages I can't login to kde under any user.I
was in kde at first but after update yeah. When I login it just logs me
back out.
Packages Updated:
kdegames-4.2.2-6.fc11.x86_64
compiz-kde-0.7.8-18.fc11.x86_64
kdelibs-4.2.2-5.fc11.x86_64
selinux-policy.noarch 3.6.12-4.fc11
kdebase-workspace-libs.x86_64 4.2.2-3.fc11
plymouth-plugin-pulser.x86_64 0.7.0-0.2009.03.10.3.fc11
kdepim-4.2.2-3.fc11.x86_64
kpartx.x86_64 0.4.8-10.fc11
kdepimlibs-akonadi-4.2.2-3.fc11.x86_64
compiz-0.7.8-18.fc11.x86_64
kdepim-libs-4.2.2-3.fc11.x86_64
kdebase-workspace.x86_64 4.2.2-3.fc11
kdebase-workspace-googlegadgets.x86_64 4.2.2-3.fc11
kde-settings-4.2-5.20090414svn.fc11.noarch
kdm.x86_64 4.2.2-3.fc11
kdegames-libs-4.2.2-6.fc11.x86_64
kde-settings-pulseaudio-4.2-5.20090414svn.fc11.noarch
kdelibs-common-4.2.2-5.fc11.x86_64
kdepimlibs-4.2.2-3.fc11.x86_64
kde-settings-kdm-4.2-5.20090414svn.fc11.noarch
15 years, 1 month
F11 anaconda crash, kernel arch, radeon blank
by Adam Pribyl
I have updated my older Fedora installation with preupgrade to rawhide.
At the end of the update process the anaconda crashed:
https://bugzilla.redhat.com/show_bug.cgi?id=496618
There are already two reports from other people attached within few days.
My previous installation was i386, anaconda decided to use i586, but
installed also i586 kernel, while this is a PIII CPU with PAE extension.
What is the decision mechanism? Is it described somewhere?
I have radeon 9200 using OS driver, but I can not switch to any text
consoles, they are just blank, but mingettys are running. This happened
already during the installation, I guess it's not bind to updated old
system, but xorg radeon driver somehow (init 3 is OK). The are other
unhealthy symptomes of radeon.. and a lot of bugs and fails in Test Day:
Radeon. Is it going to be any better?
Adam Pribyl
15 years, 1 month
vnc in F11
by Joseph L. Casale
I am running rawhide with KDE and have installed tigervnc and have it running fine.
What switch is required to export the actual logged in user's desktop (assuming
that user is configured with a vnc session)?
Thanks!
jlc
15 years, 1 month
Draft email to maintainers regarding Priority / Severity in Bugzilla
by Adam Williamson
Here's my draft of my proposed email to fedora-devel-list concerning the
possibility of us adding Priority and Severity as part of the triage
process. Please send your feedback before I send it to that list :)
thanks!
Feedback request: Priority / Severity use on Bugzilla
Hi, folks. We in the QA and Bugzappers groups have recently been
discussing the use of the Priority and Severity fields in Bugzilla.
At present, the status is that these are more or less ignored by
Bugzappers and most maintainers; some maintainers use and set them for
their own packages according to their own system. The reason for their
neglect, as I see it, is that there's been no convention for their use,
and no overall responsibility in setting them - they're usually set
arbitrarily by reporters, and thus convey no useful information.
We think it may be useful for the Bugzappers group to start setting
these fields as part of the triage process. To address one potential
issue right off the top - this would be *entirely* advisory, like all
the other work of the Bugzappers: it's intended to provide a service to
maintainers, nothing more. It would not be in any way prescriptive - we
don't want any other group to be able to tell maintainers what they
should work on. We simply think that setting these fields consistently
as part of triage might prove useful to some, or all, maintainers.
We have a draft convention for how these fields should be set here:
http://fedoraproject.org/wiki/User:Beland/Bugzilla_Legend#Severity_and_Pr... . As you can see, it basically suggests that the severity field be used to rate the importance of the issue in the context only of the affected package, and priority be used to rate the importance of the issue in the context of the distribution as a whole.
In our proposal, triagers would set these fields in as consistent a
manner as possible as part of the initial triage process. They wouldn't
take any regard of the value initially set by the reporter - so it
wouldn't matter if the reporter set it as Urgent or Low, the triager
would simply evaluate the issue him/herself and re-set both values as
per the policy. That would be it, really. There's no action required or
even suggested of any maintainer for any value of either field - it's
simply there to provide information. We feel that maintainers might then
find it useful to organize their bugs by severity or priority to make it
easier to identify the most urgent issues to address.
A few specifics: the system would happily accommodate maintainers who
have their own systems for using these fields. Triagers would be
specifically instructed not to touch these fields if they had been
previously touched by the maintainer - effectively, maintainer's
decision on these fields is final. So if you disagree with the triager's
opinion, or you have your own system for using these fields, you could
simply set them to whatever you like and the Bugzappers will not change
them back.
Some people raised the possibility that reporters could interfere with
the setting of these fields - they might disagree with a triager who set
their issue to Medium or Low, and set it higher. I've implemented
similar systems before and that hasn't been my experience - I've found
that reporters will often over-rate an issue on initial filing, but few
of them will ever re-rate it once it's been set by a triager or
maintainer. However, if this did prove to be a problem, there's a fairly
simple solution: just restrict the fields, so that only Bugzappers and
maintainers (and other usually empowered folks) can set them. That would
solve that issue, if necessary.
So, really, we just want your feedback: do you think this system might
prove useful to you as a maintainer? Can you see any problems with it,
or potential refinements or improvements? Bugzappers' mission is to ease
the lives of maintainers, so we don't want to put this in place unless
it's seen as beneficial by at least some maintainers. Thanks!
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net
15 years, 1 month
