gnome-panel icon jumble/failure
by Max Pyziur
Greetings gurus and gearheads,
On startup gnome-panel continues to occasionally fail and/or show icons as
being jumbled.
In those cases, I start an xterm session and issue a kill -9 on the
gnome-panel process. Gnome-panel restarts and functions correctly.
fyi,
Max Pyziur
pyz(a)brama.com
14 years, 8 months
F11 (Thpd T30) : reproducible display loss
by Beartooth
To my great satisfaction, it became possible shortly before the
release of F11 to run two of my four legacy suites of proprietary GPS/
topo map software under wine.The two suites I prefer (Garmin's own and
one of Maptech's) now install, launch, and run -- and most of them
usually do the crucial function, transferring data to and from my GPSs.
(Details in a June 29th post here, titled "Mappery : uncertain
success with Fedora/Wine/Garmin")
There is a snag, though.
Disclaimer : what I know of hardware would go in a gnat's eye,
comfortably.
I have a T30 Thinkpad, into which a hardware-savvy young friend
recently put a new hard drive -- one I had bought from a friend, who
thought it to have 70 GB; df -h tells me it has 228 GB.
The machine is running Fedora 11, on which I have installed
Garmin's TOPOUS2008 under Wine. This combination on three of my four PCs
not only launches and runs, but also transfers data to and from my Garmin
GPSs. It launches and runs on a T42, too -- and used to talk to the GPS,
but doesn't now.
At first, when I launched the map software on the T30, either by
mouse or from the CLI, it churned a moment, then the monitor went black,
and failed to respond discernibly to anything except holding down the
power button.
I've been told I may need to update the BIOS, but I get lost
trying to follow the directions for doing that at
http://www-307.ibm.com/pc/support/site.wss/MIGR-45745.html
(the BIOS update page).
Yesterday evening, I tried launching the map software again
(which is always very slow to launch). I *think* I did it on the
T30, but from the CLI instead of the mouse, by c&p from the launcher
to the CLI; the up arrow gets me the command: env WINEPREFIX="/home/
btth/.wine" wine "C:\Garmin\MapSource.exe"
The screen soon went black. One of the several LEDs near the
power button stayed lit. I thought, wrongly I now believe, that it
simply indicated the presence of wall power. (It looks like a circle
containing either a Z or an N, rotated 45 degrees.)
I waited a while, then hit the power button and waited
again. Nothing visible happened. I held the power button down, for
what seemed a very long time. Finally the LED turned off.
I hit the power button again; nothing happened; I waited a
while, and hit it yet again. This time the T30 booted up. I left it
at the F11 login screen.
This morning, without logging into the T30, I did ssh -X
into it from my #1 PC, the one I'm on now. Then I gave the env
WINEPREFIX="/home/btth/.wine" wine "C:\Garmin\MapSource.exe" command
again -- expecting the T30 to crash, but possibly send me
interesting messages as it did.
It didn't crash. It opened the same map display as on this
machine (which I had opened by c&p with the same command.) It gave
these messages :
[btth@Hbsk2 ~]$ ssh -X 192.168.1.109
btth(a)192.168.1.109's password:
Last login: Sun Jul 5 16:23:53 2009 from 192.168.1.102
[btth@Thpd30 ~]$ env WINEPREFIX="/home/btth/.wine" wine
"C:\Garmin\MapSource.exe"
fixme:bitblt:X11DRV_ClientSideDIBCopy potential optimization: pixel
format conversion
err:imagelist:IMAGELIST_InternalExpandBitmaps creating new image
bitmap (x=23904 y=24)!
fixme:bitblt:X11DRV_ClientSideDIBCopy potential optimization: pixel
format conversion
(Meanwhile, by comparison, PC #1 was showing these messages :
[btth@Hbsk2 ~]$ env WINEPREFIX="/home/btth/.wine" wine
"C:\Garmin\MapSource.exe"
fixme:bitblt:X11DRV_ClientSideDIBCopy potential optimization: pixel
format conversion
fixme:bitblt:X11DRV_ClientSideDIBCopy potential optimization: pixel
format conversion)
I turned on a GPS, which was still connected to the serial
port on the T30, and started trying to transfer data in to the T30.
It didn't see the GPS. I edited preferences, trying com1 through
com8 (!) and the "auto" setting (before and after the com ports); no
joy, and in fact no response, except what I'd've gotten without any
GPS.
But the T30 still didn't crash, and the map display is
still open and working usably on one of my PC#1 workspaces -- just
like the one native to PC #1. I have that open also, on the same
workspace. The only difference I find between them is that the
native one says merely "Untitled - MapSource" across the top, while
the other adds a parenthesis "(on Thpd30.localdomain)"
I took this to mean that it's not the map software itself
that's the problem, but its demands on X. Does that make sense?
After a while, I closed the display from the T30, but not
the ssh -X link -- nor the plain ssh link I also had open to it.
Then I logged into the T30 from its keyboard, and launched the map
program again.
Today, after a reboot, the T30 now does launch and run the topo
software, on its own display. That fails to see either of my GPSs, and to
find them if I tell it to. It does zoom, pan, and do most of its usual
things.
If I try to launch its Celestial Information (showing phase, rise
and set of the moon), the display on the T30 goes black; but I can still
get to it with ssh and also with ssh -X.
If I try to change the size of the map symbols, the T30's display
goes black -- except for the left panel. That also still shows the
cursor, but mouse clicks on launchers do nothing visible.
In this condition, it still lets me in with both plain ssh and
ssh -X. ssh -X can launch the map display -- defectively: it opens a
window on my #1 PC, but leaves a wide swath on the right and another
underneath without the map display. (The swaths show strips of whatever
workspace I click to the map one from.)
I also get error messages in the ssh'ing terminal on my #1 PC
that differ from the earlier ones :
[btth@Thpd30 ~]$ env WINEPREFIX="/home/btth/.wine" wine "C:\Garmin
\MapSource.exe"
X11 connection rejected because of wrong authentication.
X11 connection rejected because of wrong authentication.
Application tried to create a window, but no driver could be loaded.
Make sure that your X server is running and that $DISPLAY is set
correctly.
err:ole:apartment_createwindowifneeded CreateWindow failed with error 0
^C
[btth@Thpd30 ~]$
[btth@Thpd30 ~]$ baobab &
[1] 4162
[btth@Thpd30 ~]$ X11 connection rejected because of wrong authentication.
Inside the display, the usual mouse actions work -- except for
those that don't on the T30 itself, either. Even if I go into the T30
display on PC #1, and click Utilities > Celestial Information, that
works, too (in the useful section of the window with the swaths).
So I'm altogether at sea about what is wrong with the T30 -- the
new hard drive, the old BIOS, its version of X, or what.
--
Beartooth Staffwright, Neo-Redneck Not Quite Clueless Power User
I have precious (very precious!) little idea where up is.
14 years, 8 months
Problem: CUPS re-writing printers.conf
by Timothy Murphy
I am trying to print the CUPS Print Test Page from my laptop
on a printer attached to another machine on my home LAN.
But whenever I do this CUPS adds the line
"AuthInfoRequired username,password" to /etc/cups/printers.conf
on my laptop.
The result is that the job is rejected;
I read in /var/log/cups/error_log on the laptop:
--------------------------------
D [01/Aug/2009:03:11:08 +0100] [Job 24] Set job-printer-state-message to
"Print file was not accepted (The printer or class is not shared!)!",
current level=ERROR
D [01/Aug/2009:03:11:08 +0100] [Job 24] WWW-Authenticate=""
D [01/Aug/2009:03:11:08 +0100] [Job 24]
ATTR: auth-info-required=username,password
D [01/Aug/2009:03:11:08 +0100] [Job 24]
D [01/Aug/2009:03:11:08 +0100] [Job 24] STATE: none
D [01/Aug/2009:03:11:08 +0100] [Job 24] Backend returned status 2
(authentication required)
D [01/Aug/2009:03:11:08 +0100] [Job 24] Job held for authentication.
--------------------------------
If I try to comment out the line in printers.conf
my comment character "# " is removed.
I googled for "CUPS auth-info-required=username,password"
and it seems that this has been a CUPS problem for some time,
although there do not seem any very recent reports.
I am running cups-1.4-0.rc1.10.fc11.i586 on both machines,
under Fedora-11.
Any elucidation of this strange event gratefully received.
--
Timothy Murphy
e-mail: gayleard /at/ eircom.net
tel: +353-86-2336090, +353-1-2842366
s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland
14 years, 8 months
Re: Vonage phone service on a network with Fedora... (MAYBE solved)
by Steven P. Ulrick
On Fri, Jul 31, 2009 at 7:27 PM, Linus Ulrick<meow8282(a)gmail.com> wrote:
> Hello Everyone
> I have just (for now...) signed up for Vonage phone service. My system as is
> was BEFORE I connected the Vonage V-Portal Phone Adapter was like this:
> Two Fedora Linux systems connected to a router that is connected to a cable
> modem that is connected to the Comcast cable that comes out of my wall. We do
> NOT have any other services from Comcast other than cable internet. No TV, No
> Phone, just Internet. I have a dynamic IP address. But, like with many of us,
> it almost never changes.
>
> THEN I connected the Vonage V-Portal Phone Adapter like the instructions
> specify. In short, the adapter goes between the modem and the router. Which I
> am reasonably sure is the cause of my problems.
>
> I discovered after I connected the Vonage device that the IP address
> that I have
> had with Comcast had changed for the first time in a REAL long time. So, in an
> attempt to fix my ability to access the mail server on my Fedora 8
> system from my
> new system (Fedora 11) I changed the IP address on dnsexit.com to match the new
> one. This did not in any way change my situation... So I had an idea: I
> disconnected the Vonage device, probably did a modem/router power cycle and
> rebooted my PC's. Guess What? My IP address changed AGAIN! Any guesses on
> what it changed to? The exact same IP address that I had before I
> connected the
> Vonage adapter... I wasn't exactly too suprised when my email setup started to
> work perfectly again.
>
> So, my question is, has anyone with two or more Fedora/Linux systems on a local
> network that is also running a mail server on one of the systems been able to
> successfully connect the Vonage V-Portal Phone Adapter to their network and
> still have their network function exactly as it did before the adapter was
> installed?
>
> Your help is greatly appreciated!
Hello Everyone :)
First of all, thank you for your help so far. I had the most amazing
thing happen: I called Vonage, and the guy I talked to suggested that
I just plug the adapter directly to the back of our router. I just
had my dad call our Vonage virtual number and not only did caller ID
pick up his name and phone number, but he successfully(?) left a voice
mail.
So, everything is working SO FAR :)
Thanks Again,
Steven P. Ulrick
14 years, 8 months
threading broken in thunderbird-3.0b2 ?
by Lonni J Friedman
Anyone else notice that email threading isn't working right in
thunderbird-3.0b2 ? It worked all the time with the 2.x version from
Fedora10, and now no matter how many times I click the "Click to
display message threads" header button, its all just flat.
14 years, 8 months
Is there a command that knows about my bios?
by Dave Burns
In our shop we have some software running on the windows boxes that
'audits' the machine. Most of the information is easily (and freely)
duplicated on a linux box (mostly by looking in /proc/cpuinfo
/proc/meminfo, /etc/sysconfig/hwconf, even /etc/X11/xorg.conf|), but
I haven't found anything about bios. Anyone have a clue for me, how to
find out?
The windows program outputs stuff like this about bios:
Dell Inc. A06 SMBIOS 2.4 Date: 4/3/2008
As I was about to send this off I found smbios-sys-info, which fits
the bill. And it throws in info about the make and model of the PC for
good measure!
I guess I'll send this out anyhow, in case it helps someone else
googling howto detect bios info on linux or how to see bios info with
linux.
mahalo,
Dave
metadata PC make and model bios smbios linux fedora centos ezaudit audit
14 years, 8 months
gcc/perl/XS
by Patrick Dupre
Hello,
In a c subroutine I have the following code:
for (i = 0 ; i < 5 ; i++) {
floatMatrix new_lines = (floatMatrix) realloc (lines, (nb_lines) * sizeof (lineArray)) ;
lines=new_lines ;
nb_lines++ ;
}
which is called from a perl call through an XS interface.
It work fine with gcc.4.3.2 (32 but arch) machine.
With gcc 4.4.0 on a x86_64 arch it fails (segmentation fault) at the
second reallocation for nb_lines high (10000).
However,
it is OK if nb_lines = 1000, and it is also OK if the same shared
library is linked to a c program calling the same subroutine
I also noticed that the values of the pointer is identical after and
before the realloc call (if not NULL�).
--
---
==========================================================================
Patrick DUPRÉ | |
Department of Chemistry | | Phone: (44)-(0)-1904-434384
The University of York | | Fax: (44)-(0)-1904-432516
Heslington | |
York YO10 5DD United Kingdom | | email: pd520(a)york.ac.uk
==========================================================================
14 years, 8 months
F9: smartd errors, how to fix it?
by Dan Thurman
Is there any way to fix the following problems,
like forcing fsck or something?
I am getting smartd errors as reported:
$ cat /var/log/messages
[...]
{repeated messages of the following}
Aug 1 12:33:26 gold smartd[2820]: Device: /dev/sda, 6 Currently
unreadable (pending) sectors
Aug 1 12:33:26 gold smartd[2820]: Device: /dev/sda, 6 Offline
uncorrectable sectors
$ smartctl -a /dev/sda
smartctl version 5.38 [i386-redhat-linux-gnu] Copyright (C) 2002-8 Bruce
Allen
Home page is http://smartmontools.sourceforge.net/
=== START OF INFORMATION SECTION ===
Model Family: Seagate Barracuda 7200.10 family
Device Model: ST3750640AS
Serial Number: 5QD3HYLF
Firmware Version: 3.AAE
User Capacity: 750,156,374,016 bytes
Device is: In smartctl database [for details use: -P show]
ATA Version is: 7
ATA Standard is: Exact ATA specification draft version not indicated
Local Time is: Sat Aug 1 12:38:15 2009 PDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x82) Offline data collection activity
was completed without error.
Auto Offline Data Collection: Enabled.
Self-test execution status: ( 121) The previous self-test
completed having
the read element of the test failed.
Total time to complete Offline
data collection: ( 430) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 202) minutes.
SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE
UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 120 094 006 Pre-fail
Always - 236188522
3 Spin_Up_Time 0x0003 095 093 000 Pre-fail
Always - 0
4 Start_Stop_Count 0x0032 100 100 020 Old_age
Always - 164
5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail
Always - 0
7 Seek_Error_Rate 0x000f 087 060 030 Pre-fail
Always - 606571888
9 Power_On_Hours 0x0032 092 092 000 Old_age
Always - 7730
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail
Always - 0
12 Power_Cycle_Count 0x0032 100 100 020 Old_age
Always - 169
187 Reported_Uncorrect 0x0032 071 071 000 Old_age
Always - 29
189 High_Fly_Writes 0x003a 100 100 000 Old_age
Always - 0
190 Airflow_Temperature_Cel 0x0022 060 052 045 Old_age
Always - 40 (Lifetime Min/Max 33/48)
194 Temperature_Celsius 0x0022 040 048 000 Old_age
Always - 40 (0 24 0 0)
195 Hardware_ECC_Recovered 0x001a 066 063 000 Old_age
Always - 55842978
197 Current_Pending_Sector 0x0012 100 100 000 Old_age
Always - 6
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age
Offline - 6
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age
Always - 0
200 Multi_Zone_Error_Rate 0x0000 100 253 000 Old_age
Offline - 0
202 TA_Increase_Count 0x0032 100 253 000 Old_age
Always - 0
SMART Error Log Version: 1
ATA Error Count: 30 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.
Error 30 occurred at disk power-on lifetime: 7685 hours (320 days + 5 hours)
When the command that caused the error occurred, the device was active
or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
10 51 00 5c 9d bf e0 Error: IDNF at LBA = 0x00bf9d5c = 12557660
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 30 4b 9d bf e0 00 00:08:21.882 READ DMA EXT
25 00 08 43 9d bf e0 00 00:08:21.869 READ DMA EXT
25 00 28 8b 95 c0 e0 00 00:08:21.862 READ DMA EXT
25 00 08 83 95 c0 e0 00 00:08:21.856 READ DMA EXT
25 00 08 c3 82 c0 e0 00 00:08:21.957 READ DMA EXT
Error 29 occurred at disk power-on lifetime: 7685 hours (320 days + 5 hours)
When the command that caused the error occurred, the device was active
or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 7a dd bf e0 Error: UNC at LBA = 0x00bfdd7a = 12574074
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 20 63 dd bf e0 00 00:05:00.757 READ DMA EXT
27 00 00 00 00 00 e0 00 00:05:00.685 READ NATIVE MAX ADDRESS EXT
ec 00 00 00 00 00 a0 00 00:05:00.683 IDENTIFY DEVICE
ef 03 46 00 00 00 a0 00 00:05:07.849 SET FEATURES [Set transfer
mode]
27 00 00 00 00 00 e0 00 00:05:07.791 READ NATIVE MAX ADDRESS EXT
Error 28 occurred at disk power-on lifetime: 7685 hours (320 days + 5 hours)
When the command that caused the error occurred, the device was active
or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 7a dd bf e0 Error: UNC at LBA = 0x00bfdd7a = 12574074
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 20 63 dd bf e0 00 00:05:00.757 READ DMA EXT
27 00 00 00 00 00 e0 00 00:05:00.685 READ NATIVE MAX ADDRESS EXT
ec 00 00 00 00 00 a0 00 00:05:00.683 IDENTIFY DEVICE
ef 03 46 00 00 00 a0 00 00:05:00.665 SET FEATURES [Set transfer
mode]
27 00 00 00 00 00 e0 00 00:05:00.609 READ NATIVE MAX ADDRESS EXT
Error 27 occurred at disk power-on lifetime: 7685 hours (320 days + 5 hours)
When the command that caused the error occurred, the device was active
or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 7a dd bf e0 Error: UNC at LBA = 0x00bfdd7a = 12574074
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 20 63 dd bf e0 00 00:05:00.757 READ DMA EXT
27 00 00 00 00 00 e0 00 00:05:00.685 READ NATIVE MAX ADDRESS EXT
ec 00 00 00 00 00 a0 00 00:05:00.683 IDENTIFY DEVICE
ef 03 46 00 00 00 a0 00 00:05:00.665 SET FEATURES [Set transfer
mode]
27 00 00 00 00 00 e0 00 00:05:00.609 READ NATIVE MAX ADDRESS EXT
Error 26 occurred at disk power-on lifetime: 7685 hours (320 days + 5 hours)
When the command that caused the error occurred, the device was active
or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 78 dd bf e0 Error: UNC at LBA = 0x00bfdd78 = 12574072
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 20 63 dd bf e0 00 00:04:56.427 READ DMA EXT
27 00 00 00 00 00 e0 00 00:04:56.371 READ NATIVE MAX ADDRESS EXT
ec 00 00 00 00 00 a0 00 00:04:56.368 IDENTIFY DEVICE
ef 03 46 00 00 00 a0 00 00:04:52.800 SET FEATURES [Set transfer
mode]
27 00 00 00 00 00 e0 00 00:04:52.790 READ NATIVE MAX ADDRESS EXT
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining
LifeTime(hours) LBA_of_first_error
# 1 Extended offline Completed: read failure 90%
7689 1455414650
SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
Thanks!
Dan
14 years, 8 months
system-config-display error
by Clodoaldo Neto
Fedora 11 running as guest in a Virtual Box XP host.
# system-config-display &
[1] 2961
[root@f1132 ~]# Traceback (most recent call last):
File "/usr/share/system-config-display/xconf.py", line 376, in <module>
dialog = xConfigDialog.XConfigDialog(hardware_state, xconfig,
rhpxl.videocard.VideoCardInfo())
File "/usr/share/system-config-display/xConfigDialog.py", line 641,
in __init__
if len(self.xconfig.layout[0].adjacencies) > 1:
IndexError: index out-of-bounds
Regards, Clodoaldo
14 years, 8 months