I have a machine with two monitors, using Intel Q35
driver with DRI. Gnome 3
works in fallback mode still in FC17 - I was expecting that would not
happen. Did I hope for
Bill Murray ---- ATLAS
STFC RAL at: Bat 161 1-08, CERN,1211 Meyrin, Geneve 23, Switzerland
Tel:- CERN +41 22 7670631 or RAL +44 (0)1235 446256
First, preupgrade-cli does not work, stops in some .py stuff. Can't get
info, b'cause another comp. No problem, pure preupgrade went smoothly
trough, new 17 all ok, so far. When closing comp kernel panic, again
can't produce message here, but remember, that can't find shutdown.sh
script was one of messages... So, my lap lenovo t61 works, but shutdown
has problems... Doomed to be alive for ever? Heh... So have to wait
other comps upgrading, probably near to 18 rc2 or something. One
question, where you guys, who know something about code and so, have
hurry... If you do distro for people, make sure u understand, that
persons like me, 60 old want to use it. KISS, KISS, u make more crowns
just waiting, not with rush. World IS IS and IS, people aren't.
/* Horror, When There is no Electricity */
I've got a fresh, F17 install, running Gnome desktop. Unsurprisingly
gnome-shell crashed at some point. What is surprising though, is that
remote retrace server is no longer available for choosing in abrtd applet.
Has anything changed recently, or am I just missing some package that is
not in the default install?
I have an hp dv9000 laptop. With proprietary nvidia driver, it works correctly.
xdpyinfo says monitor is 371x232mm, which is correct.
using nouveau, xdpyinfo says it's 447x277mm.
Where do I report this bug?
Here is what I tried to workaround:
I made xorg.conf that contains only this:
# HorizSync source: edid, VertRefresh source: edid
HorizSync 30.0 - 75.0
DisplaySize 371 232
This seems to work. I'm hoping nouveau will use automatic settings for
everything else (AFAICT, it is).
Is this the easiest way to do the 1 thing I need done, which is:
DisplaySize 371 232
To understand what happened see my email regarding the JBoss failure. It all started there.
Basically because of that failure I tried to force the JBoss-as package install under f16 kernel boot 3/4 ways through the f17 install. After successfully installing all the rest of the packages using f17 installer process, the install failed due to the rpmdb changing underneath. That was me forcing the JBoss-as installation I guess. So after the installed exited. Reboot shows no beefy miracle in the grub list.
So now it's no longer the offending JBoss-as package it's more a how do I recover from this failure at this point. Or if I can't should I just install f17 from scratch and hope my /home backup will recover nicely into f17.