gnome-power-manager quits unexpectedly
by S Baig
Hi,
I just installed Fedora5 Test2 and when I log into Gnome, I immediately get
a message box saying "The Application "gnome-power-manager" has quit
unexpectedly". Then I open a terminal and try running 'gnome-power-manager'
from the command prompt, I get the same message box, but also the following
text is printed on the terminal:
** (gnome-power-manager:6362): WARNING **: main: Unable to determine the
address of the message bus
** ERROR **: This program cannot start until you start the dbus session
daemon
This is usually started in X or gnome startup (depending on distro)
You can launch the session dbus-daemon manually with this command:
eval `dbus-launch --auto-syntax`
I cannot find 'dbus-launch' anywhere in my path, but I verified using
'system-config-services' that the messagebus service is running. Has anyone
else had this problem?
Thanks,
-shez-
18 years, 3 months
Request for volunteers: xfs config corrupted during upgrade - bug 179006
by Mike A. Harris
A couple people have reported a bug in which xfs fails to start
properly due to the config file being corrupted upon install.
Something is causing one of the config file lines later in the
file (default-point-size) to be inserted into the list of font
directories, which of course breaks xfs startup.
My assumption is that chkfontpath is causing this, however if
that turns out to be true, it will be quite odd for this to just
start happening all of a sudden, as chkfontpath hasn't really
changed substantially in a long time.
Another possibility is that rpm post script processing in some
package (or packages) are modifying the xfs config and causing
this to happen, or causing it to be in a state that chkfontpath
never would have encountered before.
Unfortunately, there is no 100% reproduceable test case yet in
order to easily debug the problem, so I would like everyone who
experiences this problem to CC themselves on the master bug that
is tracking this issue, and add any information that might help
to narrow the problem down, as this bug is potentially one of
the nastiest X bugs on the FC5Blocker list, since a non-starting
font server means a non starting X server.
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=179006
I'm going to continue trying to trigger the issue locally, but
any assistance in narrowing down a reproduceable test case and/or
diagnosing the issue is appreciated. You can also find me on
#fedora-x on freenode.
TIA
--
Mike A. Harris * Open Source Advocate * http://mharris.ca
Proud Canadian.
18 years, 3 months
Request for volunteers: xfs config corrupted during upgrade - bug 179006
by Mike A. Harris
A couple people have reported a bug in which xfs fails to start
properly due to the config file being corrupted upon install.
Something is causing one of the config file lines later in the
file (default-point-size) to be inserted into the list of font
directories, which of course breaks xfs startup.
My assumption is that chkfontpath is causing this, however if
that turns out to be true, it will be quite odd for this to just
start happening all of a sudden, as chkfontpath hasn't really
changed substantially in a long time.
Another possibility is that rpm post script processing in some
package (or packages) are modifying the xfs config and causing
this to happen, or causing it to be in a state that chkfontpath
never would have encountered before.
Unfortunately, there is no 100% reproduceable test case yet in
order to easily debug the problem, so I would like everyone who
experiences this problem to CC themselves on the master bug that
is tracking this issue, and add any information that might help
to narrow the problem down, as this bug is potentially one of
the nastiest X bugs on the FC5Blocker list, since a non-starting
font server means a non starting X server.
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=179006
I'm going to continue trying to trigger the issue locally, but
any assistance in narrowing down a reproduceable test case and/or
diagnosing the issue is appreciated. You can also find me on
#fedora-x on freenode.
TIA
--
Mike A. Harris * Open Source Advocate * http://mharris.ca
Proud Canadian.
18 years, 3 months
Automatic module loading for DV camera support
by Matthias Saou
Hi,
The only outstanding issue I see to finally get DV (Digital Video) capture
working right out of the box on Fedora is having the proper modules being
loaded when a camera is connected (through firewire). There is a bit more
detail in this bug report :
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=172105
What would the solution be? Add something like this to modprobe.conf :
alias char-major-171-* video1394 (or just raw1394, which seems sufficient)
Or maybe now in a file inside modprobe.d belonging to some DV package?
Matthias
--
Clean custom Red Hat Linux rpm packages : http://freshrpms.net/
Fedora Core release 4 (Stentz) - Linux kernel 2.6.15-1.1831_FC4
Load : 4.17 3.90 2.39
18 years, 3 months
rawhide report: 20060215 changes
by Build System
Updated Packages:
binutils-2.16.91.0.6-1
----------------------
* Tue Feb 14 2006 Jakub Jelinek <jakub(a)redhat.com> 2.16.91.0.6-1
- update to 2.16.91.0.6
- fix ppc64 --gc-sections
- disassembler fixes for x86_64 cr/debug regs
- fix linker search order for DT_NEEDED libs
* Mon Jan 02 2006 Jakub Jelinek <jakub(a)redhat.com> 2.16.91.0.5-1
- update to 2.16.91.0.5
- don't error about .toc1 references to discarded sectiosn on ppc64
(#175944)
* Wed Dec 14 2005 Jakub Jelinek <jakub(a)redhat.com> 2.16.91.0.3-2
- put .gnu.linkonce.d.rel.ro.* sections into relro region
compat-db-4.2.52-4
------------------
* Tue Feb 14 2006 Jindrich Novy <jnovy(a)redhat.com> 4.2.52-4
- clarify pointer usage in db_load.c (#110697)
gawk-3.1.5-6.2
--------------
* Tue Feb 14 2006 Karel Zak <kzak(a)redhat.com> 3.1.5-6.2
- new version of the gawk-3.1.5-wconcat.patch patch
gcc-4.1.0-0.27
--------------
* Tue Feb 14 2006 Alexandre Oliva <aoliva(a)redhat.com> 4.1.0-0.27
- merge fix by Zdenek Dvorak for regression introduced by patch for PR
tree-optimization/26209
* Tue Feb 14 2006 Jakub Jelinek <jakub(a)redhat.com> 4.1.0-0.26
- update from gcc-4_1-branch (-r110903:110978)
- PRs fortran/20861, fortran/20871, fortran/25059, fortran/25070,
fortran/25083, fortran/25088, fortran/25103, fortran/26038,
fortran/26074, inline-asm/16194, libfortran/24685,
libfortran/25425, target/26141, tree-optimization/26258
- ABI change - revert to GCC 3.3 and earlier behaviour of
zero sized bitfields in packed structs (Michael Matz, PR middle-end/22275)
- fix valarrays vs. non-POD (Paolo Carlini, Gabriel Dos Reis,
PR libstdc++/25626)
- fix C++ duplicate declspec diagnostics (Volker Reichelt, PR c++/26151)
- fix dominance ICE (Zdenek Dvorak, PR tree-optimization/26209)
- add some new Intel {,e,x}mmintrin.h intrinsics (H.J. Lu)
- speedup bitset<>::_M_copy_to_string (Paolo Carlini)
- fix tree_expr_nonzero_p (Jeff Law)
- fix TRUTH_XOR_EXPR handling in VRP (Jeff Law)
kudzu-1.2.29-1
--------------
* Tue Feb 14 2006 Bill Nottingham <notting(a)redhat.com> - 1.2.29-1
- silence!
mkinitrd-5.0.25-1
-----------------
* Tue Feb 14 2006 Peter Jones <pjones(a)redhat.com> - 5.0.25-1
- rework hotplug control fds (#181515)
* Tue Feb 14 2006 Peter Jones <pjones(a)redhat.com> - 5.0.24-1
- use the right nash-dm command to get the device list
- check if a subdevice has the same partition table, not if it starts
at the right place (fixes partition comparison on !mirror devices)
Broken deps for i386
----------------------------------------------------------
GFS-kernel - 2.6.15-4.i686 requires kernel = 0:2.6.15-1.1941_FC5
GFS-kernel - 2.6.15-4.i686 requires /lib/modules/2.6.15-1.1941_FC5
GFS-kernel-smp - 2.6.15-4.i686 requires kernel-smp = 0:2.6.15-1.1941_FC5
GFS-kernel-smp - 2.6.15-4.i686 requires /lib/modules/2.6.15-1.1941_FC5smp
cman-kernel - 2.6.15.0-20051219.162641.FC5.11.4.i686 requires kernel = 0:2.6.15-1.1941_FC5
cman-kernel - 2.6.15.0-20051219.162641.FC5.11.4.i686 requires /lib/modules/2.6.15-1.1941_FC5
cman-kernel-smp - 2.6.15.0-20051219.162641.FC5.11.4.i686 requires kernel-smp = 0:2.6.15-1.1941_FC5
cman-kernel-smp - 2.6.15.0-20051219.162641.FC5.11.4.i686 requires /lib/modules/2.6.15-1.1941_FC5smp
dlm-kernel - 2.6.15.0-20051219.162641.FC5.9.3.i686 requires kernel = 0:2.6.15-1.1941_FC5
dlm-kernel - 2.6.15.0-20051219.162641.FC5.9.3.i686 requires /lib/modules/2.6.15-1.1941_FC5
dlm-kernel-smp - 2.6.15.0-20051219.162641.FC5.9.3.i686 requires kernel-smp = 0:2.6.15-1.1941_FC5
dlm-kernel-smp - 2.6.15.0-20051219.162641.FC5.9.3.i686 requires /lib/modules/2.6.15-1.1941_FC5smp
gnbd-kernel - 2.6.15-3.i686 requires kernel = 0:2.6.15-1.1941_FC5
gnbd-kernel - 2.6.15-3.i686 requires /lib/modules/2.6.15-1.1941_FC5
gnbd-kernel-smp - 2.6.15-3.i686 requires kernel-smp = 0:2.6.15-1.1941_FC5
gnbd-kernel-smp - 2.6.15-3.i686 requires /lib/modules/2.6.15-1.1941_FC5smp
Broken deps for ia64
----------------------------------------------------------
rgmanager - 1.9.31-3.ia64 requires ccs
vconfig - 1.9-1.1.ia64 requires libc.so.6
vconfig - 1.9-1.1.ia64 requires libc.so.6(GLIBC_2.0)
Broken deps for ppc
----------------------------------------------------------
ccs-devel - 1.0.3-0.2.ppc requires ccs = 0:1.0.3-0.2
gulm - 1.0.0-2.ppc requires ccs
Broken deps for ppc64
----------------------------------------------------------
cman - 1.0.3-5.FC5.ppc64 requires cman-kernel-modules >= 0:2.6.11
dlm - 1.0.0-7.FC5.ppc64 requires dlm-kernel-modules >= 0:2.6.11
emacs - 21.4-5.ppc64 requires fonts-xorg-75dpi
gnbd - 1.0.1-2.ppc64 requires gnbd-kernel-modules >= 0:2.6.11
magma-plugins - 1.0.3-1.FC5.ppc64 requires libgulm.so.1()(64bit)
vconfig - 1.9-1.1.ppc64 requires libc.so.6
vconfig - 1.9-1.1.ppc64 requires libc.so.6(GLIBC_2.0)
Broken deps for s390
----------------------------------------------------------
rhythmbox - 0.8.8-2.s390 requires libgstgconf-0.8.so.0
rhythmbox - 0.8.8-2.s390 requires libgstreamer-0.8.so.1
rhythmbox - 0.8.8-2.s390 requires libgstcontrol-0.8.so.1
Broken deps for s390x
----------------------------------------------------------
rhythmbox - 0.8.8-2.s390x requires libgstcontrol-0.8.so.1()(64bit)
rhythmbox - 0.8.8-2.s390x requires libgstreamer-0.8.so.1()(64bit)
rhythmbox - 0.8.8-2.s390x requires libgstgconf-0.8.so.0()(64bit)
Broken deps for x86_64
----------------------------------------------------------
GFS-kernel - 2.6.15-4.x86_64 requires kernel = 0:2.6.15-1.1941_FC5
GFS-kernel - 2.6.15-4.x86_64 requires /lib/modules/2.6.15-1.1941_FC5
cman-kernel - 2.6.15.0-20051219.162641.FC5.11.4.x86_64 requires kernel = 0:2.6.15-1.1941_FC5
cman-kernel - 2.6.15.0-20051219.162641.FC5.11.4.x86_64 requires /lib/modules/2.6.15-1.1941_FC5
dlm-kernel - 2.6.15.0-20051219.162641.FC5.9.3.x86_64 requires kernel = 0:2.6.15-1.1941_FC5
dlm-kernel - 2.6.15.0-20051219.162641.FC5.9.3.x86_64 requires /lib/modules/2.6.15-1.1941_FC5
gnbd-kernel - 2.6.15-3.x86_64 requires kernel = 0:2.6.15-1.1941_FC5
gnbd-kernel - 2.6.15-3.x86_64 requires /lib/modules/2.6.15-1.1941_FC5
18 years, 3 months
Re: Bugzilla dupes attack
by Paul A Houle
At 04:30 PM 2/14/2006, Jeff Spaleta wrote:
>I'm suggesting that there is very little to be learned from the
>specific comparison to google. I'm saying that since we are incapable
>of examining the details of how google search works, there is very
>little to be gleamed from looking at example output from google at
>all. The magic in the google search is the search algorithm which
>produces the results. And its exactly that piece of magic which we
>don't have access to to examine and reuse. Are you really suggesting
>that we blindly reverse-engineer the google search algorithm and apply
>it to bugzilla?
The magic of Google isn't in the ranking algorithm, it's in the
kind and quantity of data that it searches over and the expectations people
have of it.
The problems of information retrieval depend on the scale of your
database. Historically, people have evaluated IR systems based on two
things: precision and recall.
If you've got a database with 10,000 items, and there is 1 item
that matches, there's a lot of risk that that 1 item will be lost if
someone doesn't type in the perfect search term. Recall is the issue, so
it's important to stem words (working -> work), have a system that's smart
about synonyms, etc.
Now, if you're searching a database with 10 billion items, there
will be 1 million hits for a 1:10000 item. The issue is picking out the
best items out of that million items, so there's more stress on precise
phrase matching, things like pagerank. Antispam measures are
essential, and so is the removal of duplicate documents.
Google's trying to do something entirely different from what
bugzilla search is trying to do or, say, beagle should do on your desktop.
18 years, 3 months
re: Update problem
by Gianluca Cecchi
On Tue, 14 Feb 2006 21:27:40 +0100 Truls Gulbrandsen <trulsg broadpark
no> wrote:
> I have the past couple of days tried to update my TC5t2 but it all hangs
Just a try; if you run
yum update yum
does it get updated?
In that case, after upgrade of yum retry the "yum update"...
HIH,
Gianluca
18 years, 3 months
