It's that time again
by Tethys
So here I am, sat with an inbox full of bugs that I reported when F17
came out and now they're being closed as F17 is EOL. Once again,
several of them don't appear to have even been looked over *at all* by
the package maintainer. I wonder why I bother sometimes...
Tet
--
"Java is a DSL for taking large XML files and converting them to stack
traces" -- Bulat Shakirzyanov
10 years, 10 months
Yum + Java
by Timothy Murphy
I noticed today when updating my Fedora-19/KDE laptop:
------------------------
Cleanup : 1:java-1.7.0-openjdk-1.7.0.25-2.3.10.10.fc19.i686
/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25-2.3.10.10.fc19.i386/jre/bin/java
has not been configured as an alternative for java
------------------------
and a few other comments along the same lines.
In spite of this warning I see that
/usr/bin/java -> /etc/alternatives/java
-> /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25-2.3.12.3.fc19.i386/jre/bin/java
So what exactly does the comment/warning mean?
And what should one do about it?
--
Timothy Murphy
e-mail: gayleard /at/ eircom.net
tel: +353-86-2336090, +353-1-2842366
School of Mathematics, Trinity College, Dublin 2, Ireland
10 years, 10 months
I somehow managed to delete /tmp now I get errors when I try to boot and login
by Darlene Wallach
I somehow deleted /tmp when I was deleting files from /tmp to make room
Now I get errors when I boot and try to login
- There is a problem with the configuration server.
(/usr/libexec/gconf-sanity-check-2 exited with status 256)
When I close that, I get:
Install problem!
The configuration defaults for GNOME Power Manager have not been
installed correctly. Please contact your computer administrator.
One time I saw the login options - when I logged in I only saw a black screen.
Other than doing an install, is there a way to recover the files in /tmp?
argh! It pays to be very careful deleting things as root!
A lesson learned the hard way!
Any advice will be greatly appreciated!
Thank you
Darlene Wallach
--
equal justice under law
10 years, 10 months
GUI unusable after upgrade from F 17 to F 19
by Joe Zeff
First off, the upgrade didn't go that well, hanging (with no disk
activity) at about 60%. Ever since, the GUI has been unusable even
after I cleaned up over 1,000 duplicate packages from the CLI. There's
a mouse pointer, but it doesn't move, and the keyboard is ignored. All
I can do is force a reboot with either the reset button or the Magic
SysRq Key. (No, that doesn't get me back the mouse/keyboard.) Looking
through /var/log/Xorg.0.log by ssh from my laptop, I find this:
[ 41.590] (WW) Hotplugging is on, devices using drivers 'kbd',
'mouse' or 'vmmouse' will be disabled.
[ 41.590] (WW) Disabling Mouse0
[ 41.590] (WW) Disabling Keyboard0
and checking through an old log, from before the "upgrade," I see no
mention of Hotplugging. Does anybody here know where to look and how to
fix it without a fresh install, which is an option I won't even consider
as yet because that's just giving up, and I'd rather learn from this.
10 years, 10 months
VirtualBox and the USB flash drive -
by Bob Goodwin
VirtualBox defaults to using the CDROM/DVD drive which is pretty
worthless unless you have a supply of blanks, I don't have many on hand
presently. I have been trying to make the USB function work without much
success.
Googling suggests group/user problems, I have bobg and root listed as
vboxusers.
The GUI has a USB menu which is always grayed, where I can create a
filter, it recognizes the Sandisk flash drive when entered, I click on
OK and nothing is saved apparently.
Now I've run across something in google that suggests an entry in fstab
may be required?
Has any one worked through this maze who can tell me how to make it work?
Bob
--
http://www.qrz.com/db/W2BOD
box10 Fedora-19 Linux/XFCE
10 years, 10 months
Is there a way to force an update/upgrade in yum?
by Joe Zeff
There's one package that I can't get upgraded, and it's driving me up
the wall because every time I run an update via yum or yumex, I have to
remember to exclude it: firefox. Here's the results of my latest try:
Transaction check error:
file /usr/lib/firefox/browser/defaults/preferences from install of
firefox-22.0-1.fc19.i686 conflicts with file from package
firefox-22.0-1.fc17.i686
I tried using swap:
yum swap firefox\*.fc17.i686 firefox\*fc.19.i686
because the man page said that that was simply a short form of
remove/install, but yum interpreted it as an update. Maybe I'll have to
download the file and use rpm to do it, but there should[1] be a way to
force it via yum.
[1]Well, I think there should be; if you disagree, I'd be willing to
discuss it and maybe change my mind if your reason's good enough. Do
note, however, that rpm does allow --force.
10 years, 10 months
Panasonic
by Patrick Dupre
Hello,
On my laptop with fedora 19, I cannot easily transfer my pictures.
The camera does not seem to be recognized.
However,
After a very long time I was able to mount it from /dev/sdb1 and copy
my files. It is not not very convenient!
Any idea? It works fine from another machine (fedora 18).
Here is the output
[12082.009071] usb 1-6: new high-speed USB device number 6 using ehci-pci
[12082.125150] usb 1-6: New USB device found, idVendor=04da, idProduct=2372
[12082.125283] usb 1-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[12082.125402] usb 1-6: Product: DMC-TZ18
[12082.125470] usb 1-6: Manufacturer: Panasonic
[12082.125547] usb 1-6: SerialNumber: 0000000000000000006F1302150801
[12082.126728] usb-storage 1-6:1.0: USB Mass Storage device detected
[12082.128523] usb-storage 1-6:1.0: Quirks match for vid 04da pid 2372: 90
[12082.128691] scsi4 : usb-storage 1-6:1.0
[12083.131193] scsi 4:0:0:0: Direct-Access MATSHITA DMC-TZ18 0110 PQ: 0 ANSI: 2
[12083.132251] sd 4:0:0:0: Attached scsi generic sg3 type 0
[12083.133772] sd 4:0:0:0: [sdc] Adjusting the sector count from its reported value: 15523840
[12083.133926] sd 4:0:0:0: [sdc] 15523839 512-byte logical blocks: (7.94 GB/7.40 GiB)
[12083.134904] sd 4:0:0:0: [sdc] Write Protect is on
[12083.135768] sd 4:0:0:0: [sdc] No Caching mode page present
[12083.135868] sd 4:0:0:0: [sdc] Assuming drive cache: write through
[12114.118152] usb 1-6: reset high-speed USB device number 6 using ehci-pci
[12559.676946] usb 1-6: USB disconnect, device number 6
[12559.680911] sd 4:0:0:0: [sdc] Unhandled error code
[12559.683371] sd 4:0:0:0: [sdc]
[12559.685797] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[12559.688340] sd 4:0:0:0: [sdc] CDB:
[12559.688863] sd 4:0:0:0: [sdc] Attached SCSI removable disk
[12559.693510] Read(10): 28 00 00 00 00 00 00 00 01 00
[12559.696421] end_request: I/O error, dev sdc, sector 0
[12559.699335] Buffer I/O error on device sdc, logical block 0
[12559.704837] sdc: detected capacity change from 7948205568 to 0
Regards.
===========================================================================
Patrick DUPRÉ | | email: pdupre(a)gmx.com
Laboratoire de Physico-Chimie de l'Atmosphère | |
Université du Littoral-Côte d'Opale | |
Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44
189A, avenue Maurice Schumann | | 59140 Dunkerque, France
===========================================================================
10 years, 10 months
RE: VirtualBox wont run -
by Alan Gagne
> On 30/07/13 12:41, Steven Stern wrote:
> >/ If you're using the repo from virtualbox.org*, type
> />/
> />/ sudo /sbin/service vboxdrv setup
> />/
> />/ It will use DKMS to remove the virtual box drivers, recompile them for
> />/ the new kernel, and install them into the active kernel modules.
> />/
> />/ * This may apply to the Fedora repos but I'm not sure. I'm using the one
> />/ from virtualbox.org.Seehttps://www.virtualbox.org/wiki/Linux_Downloads <seehttps://www.virtualbox.org/wiki/Linux_Downloads>
> />/ and scroll down to RPM-based Linux distributions
> />/
> />/
> /
> This is a yum install but I will look into that.
>
> Bob
>
If you have DKMS installed it will automatically update the modules when
a new kernel
in installed. Works great for me.
From the doc referenced above.
*Note:*Users of Fedora/Mandriva might want to install the*dkms*package
(not available on openSUSE) to ensure that the VirtualBox host kernel
modules (/vboxdrv/,/vboxnetflt/and/vboxnetadp/) are properly updated if
the linux kernel version changes during the next kernel update.
Alan
10 years, 10 months
