[solved] Problems with display after kernel update.

After using pacman -Syu and getting the newest kernel and Nvidia drivers I experience some major problems.
My Arch freezes when I try to run some apps. Firefox, konqueror and some others work fine, but when I type "glxinfo | grep direct" or try to execute something using wine the problems begin. Terminal doesn't return any errors (it doesn't get a chance to do so, freeze is instant).
Edit:
I've used script from nvidia.com
Last edited by dcfighter (2008-08-11 00:42:51)

I examined /etc/fonts/conf.avail and found 2 files
70-no-bitmaps.conf and
70-yes-bitmaps.conf
But the content of this files the same! Defined value was set to "false"
I delete "no" file and correct "yes" file
<fontconfig>
<Accept>
<selectfont>
<acceptfont>
<pattern>
<patelt><bool>true</bool></patelt>
</pattern>
</acceptfont>
</selectfont>
</fontconfig>
After this, Helvetica fonts became more likely

Similar Messages

  • Problem with firewire (since kernel-update?) [solved]

    Hi,
    since i have updated my system, i am unable to connect my dv-camcorder to my firewire-card.
    when i power on my dv-camcorder dmesg says:
    firewire_core: phy config: card 0, new root=ffc1, gap_count=5
    firewire_core: phy config: card 0, new root=ffc1, gap_count=5
    firewire_core: created new fw device fw1 (0 config rom retries, S100)
    ieee1394: raw1394: /dev/raw1394 device initialized
    NOTE: The dv1394 driver is unsupported and may be removed in a future Linux rele
    ase. Use raw1394 instead.
    firewire_core: giving up on config rom for node id ffc1
    If i then disconnect and reconnect it, dmesg says the following:
    firewire_core: BM lock failed, making local node (ffc0) root.
    firewire_core: phy config: card 0, new root=ffc0, gap_count=5
    firewire_core: phy config: card 0, new root=ffc1, gap_count=5
    firewire_core: phy config: card 0, new root=ffc1, gap_count=5
    firewire_core: phy config: card 0, new root=ffc1, gap_count=5
    firewire_core: created new fw device fw1 (0 config rom retries, S100)
    I have tried a canon mv700 as well as a canon xm1, both lead to the same problem. I have tried to connect my camcorder also to my notebook which also runs the latest version of arch, but leads to the same problem too.
    I think there is a problem with the new kernel or something. Two weeks ago, before updating my system, everything works well.
    Any suggestions or ideas?
    Anyone with similar problems?
    Greets,
    smove
    Last edited by smove (2008-05-06 19:32:14)

    I solved this problem. Since kernel 2.6.22 there is a new firewire-stack available called 'juju'. Because of it´s experimental state it is not recommend to use it. In the current kernel-package the old and the new firewire-modules are included but the new instable ones are used by default. To fix the problem you have to blacklist the new firewire-modules.
    Create the following file:
    /etc/modprobe.d/newfw_blacklist:
    blacklist firewire-ohci
    blacklist firewire-sbp2
    Reboot your system and try to use your firewire again. Look if the old modules are loaded instead of the new firewire-* ones. I dont understand why the new firewire-modules are used by default in the new kernel-packages. Refering to http://wiki.linux1394.org/JujuMigration … 857ee71b93 it is not recommended to use the new modules yet.

  • [SOLVED]problem with Bumblebee and Kernel 3.11-1-2

    Hi!
    I'm having problems with Bumblebee from Kernel 3.10 but I read that Kernel 3.11 solved the problem, I searched and tried possible solutions to my problem unsuccessfully
    The message shows me when I run "optirun":
    [ 5454.262739] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) No devices detected.
    [ 5454.262776] [ERROR]Aborting because fallback start is disabled.
    I've tried with wiki's solutions, forums solutions...
    Configurations files:
    /etc/bumblebee/bumblebee.conf:
    # Configuration file for Bumblebee. Values should **not** be put between quotes
    ## Server options. Any change made in this section will need a server restart
    # to take effect.
    [bumblebeed]
    # The secondary Xorg server DISPLAY number
    VirtualDisplay=:8
    # Should the unused Xorg server be kept running? Set this to true if waiting
    # for X to be ready is too long and don't need power management at all.
    KeepUnusedXServer=false
    # The name of the Bumbleblee server group name (GID name)
    ServerGroup=bumblebee
    # Card power state at exit. Set to false if the card shoud be ON when Bumblebee
    # server exits.
    TurnCardOffAtExit=false
    # The default behavior of '-f' option on optirun. If set to "true", '-f' will
    # be ignored.
    NoEcoModeOverride=false
    # The Driver used by Bumblebee server. If this value is not set (or empty),
    # auto-detection is performed. The available drivers are nvidia and nouveau
    # (See also the driver-specific sections below)
    Driver=
    # Directory with a dummy config file to pass as a -configdir to secondary X
    XorgConfDir=/etc/bumblebee/xorg.conf.d
    ## Client options. Will take effect on the next optirun executed.
    [optirun]
    # Acceleration/ rendering bridge, possible values are auto, virtualgl and
    # primus.
    Bridge=virtualgl
    # The method used for VirtualGL to transport frames between X servers.
    # Possible values are proxy, jpeg, rgb, xv and yuv.
    VGLTransport=proxy
    # List of paths which are searched for the primus libGL.so.1 when using
    # the primus bridge
    PrimusLibraryPath=/usr/lib/primus:/usr/lib32/primus
    # Should the program run under optirun even if Bumblebee server or nvidia card
    # is not available?
    AllowFallbackToIGC=false
    # Driver-specific settings are grouped under [driver-NAME]. The sections are
    # parsed if the Driver setting in [bumblebeed] is set to NAME (or if auto-
    # detection resolves to NAME).
    # PMMethod: method to use for saving power by disabling the nvidia card, valid
    # values are: auto - automatically detect which PM method to use
    # bbswitch - new in BB 3, recommended if available
    # switcheroo - vga_switcheroo method, use at your own risk
    # none - disable PM completely
    # https://github.com/Bumblebee-Project/Bumblebee/wiki/Comparison-of-PM-methods
    ## Section with nvidia driver specific options, only parsed if Driver=nvidia
    [driver-nvidia]
    # Module name to load, defaults to Driver if empty or unset
    KernelDriver=nvidia
    PMMethod=auto
    # colon-separated path to the nvidia libraries
    LibraryPath=/usr/lib/nvidia:/usr/lib32/nvidia
    # comma-separated path of the directory containing nvidia_drv.so and the
    # default Xorg modules path
    XorgModulePath=/usr/lib/nvidia/xorg/,/usr/lib/xorg/modules
    XorgConfFile=/etc/bumblebee/xorg.conf.nvidia
    ## Section with nouveau driver specific options, only parsed if Driver=nouveau
    [driver-nouveau]
    KernelDriver=nouveau
    PMMethod=auto
    XorgConfFile=/etc/bumblebee/xorg.conf.nouveau
    /etc/bumblebee/xorg.conf.nvidia
    Section "ServerLayout"
    Identifier "Layout0"
    Option "AutoAddDevices" "false"
    Option "AutoAddGPU" "false"
    EndSection
    Section "Device"
    Identifier "DiscreteNvidia"
    Driver "nvidia"
    VendorName "NVIDIA Corporation"
    # If the X server does not automatically detect your VGA device,
    # you can manually set it here.
    # To get the BusID prop, run `lspci | egrep 'VGA|3D'` and input the data
    # as you see in the commented example.
    # This Setting may be needed in some platforms with more than one
    # nvidia card, which may confuse the proprietary driver (e.g.,
    # trying to take ownership of the wrong device). Also needed on Ubuntu 13.04.
    BusID "PCI:01:00.0"
    # Setting ProbeAllGpus to false prevents the new proprietary driver
    # instance spawned to try to control the integrated graphics card,
    # which is already being managed outside bumblebee.
    # This option doesn't hurt and it is required on platforms running
    # more than one nvidia graphics card with the proprietary driver.
    # (E.g. Macbook Pro pre-2010 with nVidia 9400M + 9600M GT).
    # If this option is not set, the new Xorg may blacken the screen and
    # render it unusable (unless you have some way to run killall Xorg).
    Option "ProbeAllGpus" "false"
    Option "NoLogo" "true"
    Option "UseEDID" "false"
    Option "UseDisplayDevice" "none"
    EndSection
    lspci |grep NVIDIA:
    01:00.0 VGA compatible controller: NVIDIA Corporation GK107M [GeForce GT 640M] (rev a1)
    I hope can help me
    Thanks!
    Last edited by surrealistic (2013-11-04 18:46:35)

    My /var/log/Xorg.8.log:
    [ 337.161]
    X.Org X Server 1.14.4
    Release Date: 2013-10-31
    [ 337.161] X Protocol Version 11, Revision 0
    [ 337.161] Build Operating System: Linux 3.11.6-1-ARCH x86_64
    [ 337.161] Current Operating System: Linux h131h-laptop 3.11.6-1-ARCH #1 SMP PREEMPT Fri Oct 18 23:22:36 CEST 2013 x86_64
    [ 337.161] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=4eb69984-2228-4aba-9863-28a7fa854e51 rw quiet
    [ 337.161] Build Date: 01 November 2013 05:10:48PM
    [ 337.161]
    [ 337.161] Current version of pixman: 0.30.2
    [ 337.161] Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    [ 337.161] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    [ 337.161] (==) Log file: "/var/log/Xorg.8.log", Time: Mon Nov 4 14:20:04 2013
    [ 337.161] (++) Using config file: "/etc/bumblebee/xorg.conf.nvidia"
    [ 337.161] (++) Using config directory: "/etc/bumblebee/xorg.conf.d"
    [ 337.161] (==) ServerLayout "Layout0"
    [ 337.161] (==) No screen section available. Using defaults.
    [ 337.161] (**) |-->Screen "Default Screen Section" (0)
    [ 337.161] (**) | |-->Monitor "<default monitor>"
    [ 337.161] (==) No device specified for screen "Default Screen Section".
    Using the first device section listed.
    [ 337.161] (**) | |-->Device "DiscreteNvidia"
    [ 337.161] (==) No monitor specified for screen "Default Screen Section".
    Using a default monitor configuration.
    [ 337.161] (**) Option "AutoAddDevices" "false"
    [ 337.161] (**) Option "AutoAddGPU" "false"
    [ 337.161] (**) Not automatically adding devices
    [ 337.161] (==) Automatically enabling devices
    [ 337.161] (**) Not automatically adding GPU devices
    [ 337.161] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
    [ 337.162] Entry deleted from font path.
    [ 337.162] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
    [ 337.162] Entry deleted from font path.
    [ 337.162] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
    [ 337.162] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
    [ 337.162] Entry deleted from font path.
    [ 337.162] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
    [ 337.162] (==) FontPath set to:
    /usr/share/fonts/misc/,
    /usr/share/fonts/TTF/,
    /usr/share/fonts/Type1/
    [ 337.162] (++) ModulePath set to "/usr/lib/nvidia/xorg/,/usr/lib/xorg/modules"
    [ 337.162] (==) |-->Input Device "<default pointer>"
    [ 337.162] (==) |-->Input Device "<default keyboard>"
    [ 337.162] (==) The core pointer device wasn't specified explicitly in the layout.
    Using the default mouse configuration.
    [ 337.162] (==) The core keyboard device wasn't specified explicitly in the layout.
    Using the default keyboard configuration.
    [ 337.162] (II) Loader magic: 0x7fdc20
    [ 337.162] (II) Module ABI versions:
    [ 337.162] X.Org ANSI C Emulation: 0.4
    [ 337.162] X.Org Video Driver: 14.1
    [ 337.162] X.Org XInput driver : 19.1
    [ 337.162] X.Org Server Extension : 7.0
    [ 337.162] (II) xfree86: Adding drm device (/dev/dri/card1)
    [ 337.162] (II) xfree86: Adding drm device (/dev/dri/card0)
    [ 337.162] setversion 1.4 failed
    [ 337.163] (--) PCI:*(0:1:0:0) 10de:0fd2:1025:0648 rev 161, Mem @ 0xb2000000/16777216, 0xa0000000/268435456, 0xb0000000/33554432, I/O @ 0x00002000/128
    [ 337.163] Initializing built-in extension Generic Event Extension
    [ 337.163] Initializing built-in extension SHAPE
    [ 337.163] Initializing built-in extension MIT-SHM
    [ 337.163] Initializing built-in extension XInputExtension
    [ 337.163] Initializing built-in extension XTEST
    [ 337.163] Initializing built-in extension BIG-REQUESTS
    [ 337.163] Initializing built-in extension SYNC
    [ 337.163] Initializing built-in extension XKEYBOARD
    [ 337.163] Initializing built-in extension XC-MISC
    [ 337.163] Initializing built-in extension SECURITY
    [ 337.163] Initializing built-in extension XINERAMA
    [ 337.163] Initializing built-in extension XFIXES
    [ 337.163] Initializing built-in extension RENDER
    [ 337.163] Initializing built-in extension RANDR
    [ 337.164] Initializing built-in extension COMPOSITE
    [ 337.164] Initializing built-in extension DAMAGE
    [ 337.164] Initializing built-in extension MIT-SCREEN-SAVER
    [ 337.164] Initializing built-in extension DOUBLE-BUFFER
    [ 337.164] Initializing built-in extension RECORD
    [ 337.164] Initializing built-in extension DPMS
    [ 337.164] Initializing built-in extension X-Resource
    [ 337.164] Initializing built-in extension XVideo
    [ 337.164] Initializing built-in extension XVideo-MotionCompensation
    [ 337.164] Initializing built-in extension XFree86-VidModeExtension
    [ 337.164] Initializing built-in extension XFree86-DGA
    [ 337.164] Initializing built-in extension XFree86-DRI
    [ 337.164] Initializing built-in extension DRI2
    [ 337.164] (II) LoadModule: "glx"
    [ 337.164] (II) Loading /usr/lib/nvidia/xorg/modules/extensions/libglx.so
    [ 337.172] (II) Module glx: vendor="NVIDIA Corporation"
    [ 337.172] compiled for 4.0.2, module version = 1.0.0
    [ 337.172] Module class: X.Org Server Extension
    [ 337.172] (II) NVIDIA GLX Module 325.15 Wed Jul 31 18:12:00 PDT 2013
    [ 337.172] Loading extension GLX
    [ 337.172] (II) LoadModule: "nvidia"
    [ 337.172] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
    [ 337.172] (II) Module nvidia: vendor="NVIDIA Corporation"
    [ 337.172] compiled for 4.0.2, module version = 1.0.0
    [ 337.172] Module class: X.Org Video Driver
    [ 337.172] (II) LoadModule: "mouse"
    [ 337.172] (II) Loading /usr/lib/xorg/modules/input/mouse_drv.so
    [ 337.172] (II) Module mouse: vendor="X.Org Foundation"
    [ 337.172] compiled for 1.14.0, module version = 1.9.0
    [ 337.172] Module class: X.Org XInput Driver
    [ 337.172] ABI class: X.Org XInput driver, version 19.1
    [ 337.172] (II) LoadModule: "kbd"
    [ 337.173] (WW) Warning, couldn't open module kbd
    [ 337.173] (II) UnloadModule: "kbd"
    [ 337.173] (II) Unloading kbd
    [ 337.173] (EE) Failed to load module "kbd" (module does not exist, 0)
    [ 337.173] (II) NVIDIA dlloader X Driver 325.15 Wed Jul 31 17:50:57 PDT 2013
    [ 337.173] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
    [ 337.173] (--) using VT number 1
    [ 337.173] (II) Loading sub module "fb"
    [ 337.173] (II) LoadModule: "fb"
    [ 337.173] (II) Loading /usr/lib/xorg/modules/libfb.so
    [ 337.173] (II) Module fb: vendor="X.Org Foundation"
    [ 337.173] compiled for 1.14.4, module version = 1.0.0
    [ 337.173] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 337.173] (WW) Unresolved symbol: fbGetGCPrivateKey
    [ 337.173] (II) Loading sub module "wfb"
    [ 337.173] (II) LoadModule: "wfb"
    [ 337.173] (II) Loading /usr/lib/xorg/modules/libwfb.so
    [ 337.173] (II) Module wfb: vendor="X.Org Foundation"
    [ 337.173] compiled for 1.14.4, module version = 1.0.0
    [ 337.173] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 337.173] (II) Loading sub module "shadow"
    [ 337.173] (II) LoadModule: "shadow"
    [ 337.173] (II) Loading /usr/lib/xorg/modules/libshadow.so
    [ 337.173] (II) Module shadow: vendor="X.Org Foundation"
    [ 337.173] compiled for 1.14.4, module version = 1.1.0
    [ 337.173] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 337.173] (II) Loading sub module "ramdac"
    [ 337.173] (II) LoadModule: "ramdac"
    [ 337.173] (II) Module "ramdac" already built-in
    [ 337.174] (II) NVIDIA(0): Creating default Display subsection in Screen section
    "Default Screen Section" for depth/fbbpp 24/32
    [ 337.174] (==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
    [ 337.174] (==) NVIDIA(0): RGB weight 888
    [ 337.174] (==) NVIDIA(0): Default visual is TrueColor
    [ 337.174] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
    [ 337.174] (**) NVIDIA(0): Option "NoLogo" "true"
    [ 337.174] (**) NVIDIA(0): Option "ProbeAllGpus" "false"
    [ 337.174] (**) NVIDIA(0): Option "UseEDID" "false"
    [ 337.174] (**) NVIDIA(0): Option "UseDisplayDevice" "none"
    [ 337.174] (**) NVIDIA(0): Enabling 2D acceleration
    [ 337.174] (**) NVIDIA(0): Ignoring EDIDs
    [ 337.174] (**) NVIDIA(0): Option "UseDisplayDevice" set to "none"; enabling NoScanout
    [ 337.174] (**) NVIDIA(0): mode
    [ 341.309] (EE) NVIDIA(0): Failed to initialize the NVIDIA GPU at PCI:1:0:0. Please
    [ 341.309] (EE) NVIDIA(0): check your system's kernel log for additional error
    [ 341.309] (EE) NVIDIA(0): messages and refer to Chapter 8: Common Problems in the
    [ 341.309] (EE) NVIDIA(0): README for additional information.
    [ 341.309] (EE) NVIDIA(0): Failed to initialize the NVIDIA graphics device!
    [ 341.309] (EE) NVIDIA(0): Failing initialization of X screen 0
    [ 341.309] (II) UnloadModule: "nvidia"
    [ 341.309] (II) UnloadSubModule: "shadow"
    [ 341.309] (II) UnloadSubModule: "wfb"
    [ 341.309] (II) UnloadSubModule: "fb"
    [ 341.309] (EE) Screen(s) found, but none have a usable configuration.
    [ 341.309] (EE)
    Fatal server error:
    [ 341.309] (EE) no screens found(EE)
    [ 341.309] (EE)
    Please consult the The X.Org Foundation support
    at http://wiki.x.org
    for help.
    [ 341.309] (EE) Please also check the log file at "/var/log/Xorg.8.log" for additional information.
    [ 341.309] (EE)
    [ 341.309] (EE) Server terminated with error (1). Closing log file.
    dmesg |grep bbswitch:
    [ 13.570577] bbswitch: version 0.7
    [ 13.570585] bbswitch: Found integrated VGA device 0000:00:02.0: \_SB_.PCI0.GFX0
    [ 13.570591] bbswitch: Found discrete VGA device 0000:01:00.0: \_SB_.PCI0.PEG0.PEGP
    [ 13.570687] bbswitch: detected an Optimus _DSM function
    [ 13.570741] bbswitch: Succesfully loaded. Discrete card 0000:01:00.0 is on
    [ 13.572354] bbswitch: disabling discrete graphics
    [ 261.419114] bbswitch: enabling discrete graphics
    [ 278.445698] bbswitch: disabling discrete graphics
    [ 279.055257] bbswitch: enabling discrete graphics
    [ 286.292315] bbswitch: disabling discrete graphics
    [ 291.911052] bbswitch: enabling discrete graphics
    [ 310.011289] bbswitch: disabling discrete graphics
    [ 336.982794] bbswitch: enabling discrete graphics
    [ 349.526470] bbswitch: enabling discrete graphics
    I used "rcutree" option as shown in the post that you put, but I've deleted all changes made to use default configurations, because the solution of the post didn't work

  • Problem with Java after Software Update to 10.5.7

    Hi,
    I am facing problem with Java after having run Software upgrades.
    Here is the whole story. I recently moved to iMac 10.5.6 from PowerPc 10.4. On this new machine I was having problem running a 3rd party application, which requires JVM. As this application worked well on Tiger, I decided to upgrade JVM on my iMAC using Software Upgrade(was I insane!!). As I like my systems to be updated (as with linux on my personal machine) I clicked "install all". As a result I have the following upgrades run on my machine:
    2009-05-20 13:12:01 +0200: Installed "Mac OS X Update Combined" (10.5.7)
    2009-05-20 13:12:10 +0200: Installed "Remote Desktop Client Update" (3.2.2)
    2009-05-20 13:12:26 +0200: Installed "Java For Mac OS X 10.5 Update 2" (1.0)
    2009-05-20 13:58:36 +0200: Installed "Java for Mac OS X 10.5 Update 3" (1.0)
    2009-05-20 13:58:44 +0200: Installed "AirPort Utility Software Update 2009-001" (5.4.1)
    2009-05-20 13:59:07 +0200: Installed "QuickTime" (7.6)
    2009-05-20 13:59:22 +0200: Installed "iPhoto Update" (7.1.5)
    2009-05-20 13:59:28 +0200: Installed "iLife Support" (9.0.2)
    2009-05-20 13:59:38 +0200: Installed "iDVD Update" (7.0.3)
    2009-05-20 13:59:58 +0200: Installed "iTunes" (8.1.1)
    But now, simply running $java on the prompt hangs, i.e. it takes no action.
    $ which java
    /usr/bin/java
    $ ls -ltr /usr/bin/java
    May 20 15:09 /usr/bin/java -> /System/Library/Frameworks/JavaVM.framework/Versions/Current/Commands/java
    $java (no response)
    Here is the output of $ top
    PID COMMAND %CPU TIME #TH #PRTS #MREGS RPRVT RSHRD RSIZE VSIZE
    703 java 98.8% 0:38.54 3 110 72 480K 184K 1964K 40M
    Any clues?
    Details of JavaVM on my machine
    $ pwd
    /System/Library/Frameworks/JavaVM.framework/Versions
    $ ls -ltr
    total 56
    drwxr-xr-x 3 root wheel 102 Dec 2 2007 1.3.1
    lrwxr-xr-x 1 root wheel 3 Aug 31 2008 1.4.1 -> 1.4
    drwxr-xr-x 8 root wheel 272 Aug 31 2008 1.4.2
    drwxr-xr-x 8 root wheel 272 Aug 31 2008 1.5.0
    lrwxr-xr-x 1 root wheel 5 May 20 13:12 1.3 -> 1.3.1
    lrwxr-xr-x 1 root wheel 5 May 20 13:12 1.4 -> 1.4.2
    lrwxr-xr-x 1 root wheel 5 May 20 13:12 1.5 -> 1.5.0
    drwxr-xr-x 8 root wheel 272 May 20 13:12 1.6.0
    lrwxr-xr-x 1 root wheel 5 May 20 13:12 1.6 -> 1.6.0
    drwxr-xr-x 8 root wheel 272 May 20 13:12 A
    lrwxr-xr-x 1 root wheel 1 May 20 14:57 Current -> A
    lrwxr-xr-x 1 root wheel 3 May 20 14:59 CurrentJDK -> 1.5
    Any suggestions? Is there a cleaner approach to uninstall Java on Mac then a simpl "move to thrash"!
    cheers

    Hi,
    I am facing problem with Java after having run Software upgrades.
    Here is the whole story. I recently moved to iMac 10.5.6 from PowerPc 10.4. On this new machine I was having problem running a 3rd party application, which requires JVM. As this application worked well on Tiger, I decided to upgrade JVM on my iMAC using Software Upgrade(was I insane!!). As I like my systems to be updated (as with linux on my personal machine) I clicked "install all". As a result I have the following upgrades run on my machine:
    2009-05-20 13:12:01 +0200: Installed "Mac OS X Update Combined" (10.5.7)
    2009-05-20 13:12:10 +0200: Installed "Remote Desktop Client Update" (3.2.2)
    2009-05-20 13:12:26 +0200: Installed "Java For Mac OS X 10.5 Update 2" (1.0)
    2009-05-20 13:58:36 +0200: Installed "Java for Mac OS X 10.5 Update 3" (1.0)
    2009-05-20 13:58:44 +0200: Installed "AirPort Utility Software Update 2009-001" (5.4.1)
    2009-05-20 13:59:07 +0200: Installed "QuickTime" (7.6)
    2009-05-20 13:59:22 +0200: Installed "iPhoto Update" (7.1.5)
    2009-05-20 13:59:28 +0200: Installed "iLife Support" (9.0.2)
    2009-05-20 13:59:38 +0200: Installed "iDVD Update" (7.0.3)
    2009-05-20 13:59:58 +0200: Installed "iTunes" (8.1.1)
    But now, simply running $java on the prompt hangs, i.e. it takes no action.
    $ which java
    /usr/bin/java
    $ ls -ltr /usr/bin/java
    May 20 15:09 /usr/bin/java -> /System/Library/Frameworks/JavaVM.framework/Versions/Current/Commands/java
    $java (no response)
    Here is the output of $ top
    PID COMMAND %CPU TIME #TH #PRTS #MREGS RPRVT RSHRD RSIZE VSIZE
    703 java 98.8% 0:38.54 3 110 72 480K 184K 1964K 40M
    Any clues?
    Details of JavaVM on my machine
    $ pwd
    /System/Library/Frameworks/JavaVM.framework/Versions
    $ ls -ltr
    total 56
    drwxr-xr-x 3 root wheel 102 Dec 2 2007 1.3.1
    lrwxr-xr-x 1 root wheel 3 Aug 31 2008 1.4.1 -> 1.4
    drwxr-xr-x 8 root wheel 272 Aug 31 2008 1.4.2
    drwxr-xr-x 8 root wheel 272 Aug 31 2008 1.5.0
    lrwxr-xr-x 1 root wheel 5 May 20 13:12 1.3 -> 1.3.1
    lrwxr-xr-x 1 root wheel 5 May 20 13:12 1.4 -> 1.4.2
    lrwxr-xr-x 1 root wheel 5 May 20 13:12 1.5 -> 1.5.0
    drwxr-xr-x 8 root wheel 272 May 20 13:12 1.6.0
    lrwxr-xr-x 1 root wheel 5 May 20 13:12 1.6 -> 1.6.0
    drwxr-xr-x 8 root wheel 272 May 20 13:12 A
    lrwxr-xr-x 1 root wheel 1 May 20 14:57 Current -> A
    lrwxr-xr-x 1 root wheel 3 May 20 14:59 CurrentJDK -> 1.5
    Any suggestions? Is there a cleaner approach to uninstall Java on Mac then a simpl "move to thrash"!
    cheers

  • HUGES problems with display after waking up from hibernate mode

    Hello everybody,
    I hope that somebody can help me soon, because in the last 15 days I'm reaaaaallly annoyed with MAC's issues.
    In the last 15 days it seemd I had to reboot it a lot of times, because it freezes, it crashes, etc...
    Neverthless what happened today it passes all the limits: in the last period, because of these often crashes, I turn the mac off at night, on the other hand when I go to work I simply close the display and let it hibernates.
    Today when I came back after work I opened it and it was amazing:
    it has a different desktop!! With different icons in the dock, diferent icons in the top-right part, and it was freezed! I had to force it to shut down, restart it...and since then, I had huge problem with display.
    It shakes everything while scrolling mails, web pages or icons in the dock. If I scroll between desktops, it takes year lights more than yesterday!!
    Nothing happen if I restart as many time as I want.
    In my simple opinion it seems a virus issue, but..as far as I know, there is no need to install an AV on a mac, right???
    I tried to record some of these probls with the QT, but when you start recording all the desktop, it seems A LITTLE better, smoothing all these shaking effects. NEverthless they are still noticeable.
    I'll try to attach a video as a dropbox link, 'cause I can't attach it on the message (it is denied)
    PLEASE HELP MEEEEE!!!!
    https://www.dropbox.com/s/r1mlpjo5x8g1tkj/scrolling%20problems.mov
    https://www.dropbox.com/s/g1ey1xrheo9mvti/scrolling%20problems2.mov
    https://www.dropbox.com/s/ljtm53go8ywt9fs/scrolling%20prob3.mov

    I am going to add my problem to this as I believe it fits and may add to the conversation.
    I have a MacBook Pro, am using Parallels, and have an issue waking it up from sleep.
    Circumstances:
    I close the lid and walk away from the device in my office. When I return, (over night or an hour later) I open the lid, and if nothing happens swipe the touchpad or press a key, the power light changes from pulsating to steady. then in less than 15 seconds it goes back to pusating. The display never energizes, only remain black.
    I usually try opening and closing several times, and occaisionally that will work. Other times, I hold the power key until I hear the drive halt, then turn it on. The grey screen will display, then blue, then just before it gets to the log in, the screen goes black (not energized) and the light pulsates.
    I have tried the PRAM reset and Safe Mode starts with no luck.
    *Now the really wierd thing.* I decieded to contact Apple support on line and pay for help (yes that is weird in an of itself for me). As I began the process it came to the part for me to enter my serial number. With the lid open, I turned the MacBook on its side to try to read the number and the screen energized and the password unlock prompt was waiting for me to enter the password.
    Observations
    I had read where the light sensor could be blocked by dirt or the light in the room was too dim, but I clean the screen and there is plenty of light. Dales Post is the first that I have seen Parallels and the Sudden Motion Sensor. That makes some sense to me because of what happened when I turned it on its side. I have verified that it happens regardless of using Parallels. as teh last time I did it I had closed out of all my VMs and I believe exited Parallels.
    I am going to try the deleting the power preferences file and will report back.

  • [Enlightenment E17] Problems with EFM after last Update [solved]

    Hello Folks!
    I'm having some very ugly problems with my Enlightenment E17 Desktop after the last full system upgrade. This problem has already been reported to the German Arch Linux community, but no response yet, but I can't figure out that nobody else troubles the same probs.
    This is the following what I get when running pacman -Ss e17-svn
    community/e-svn 42849-1 (e17-svn)
    Enlightenment window manager DR17 (aka e17)
    community/e_dbus-svn 42682-1 (e17-libs-svn e17-svn)
    dbus abstraction layer for e17
    community/ecore-svn 42854-1 (e17-libs-svn e17-svn)
    Ecore is an abstraction layer for e17
    community/edje-svn 42794-1 (e17-libs-svn e17-svn)
    A graphical design and layout library based on Evas
    community/eet-svn 42851-1 (e17-libs-svn e17-svn)
    A data storage and compression library
    community/efreet-svn 42759-1 (e17-libs-svn e17-svn)
    freedesktop.org specifications for e17
    community/eina-svn 42822-1 (e17-libs-svn e17-svn)
    E17 file chunk reading/writing library
    community/embryo-svn 42739-1 (e17-libs-svn e17-svn)
    implementation of a C like scripting language for e17
    community/evas-svn 42855-1 (e17-libs-svn e17-svn)
    A hardware-accelerated canvas API for X-Windows
    The problems that occur to me are following: I'm using EFM as file manager. It's not the best one, but it fits into the E17 concept - simple, lightweight, fast - and thats what I like. But, after the latest update, when I click a folder on my desktop, EFM now comes up in a stupid very tiny window. The window is so small, that I need to resize it every time to see any content. Before the update, everything worked fine, the EFM windows came up as they should.
    Another problem I'm having with some applications, e.g. the Okular-Viewer, is that I'm not able to size down the window - it is always in full screen, and there's no chance to move it up (even not on the desktop preview widget) to move it down. Okular is always 100% filling my screen (over the height, only), and I'm not able to size it down. In the previous version, I didn't got this problems.
    My question is now: is there any way to install the previous Enlightenment E17 packages? They where much better that this one... or will another update come out soon??
    Thanks in advance for any help, any help is appreciated!
    beachcoder
    Last edited by beachcoder (2009-10-09 09:04:21)

    Have you tried starting with a clean config and the default theme, it helps sometimes after big code changes?
    If that doesn't help...
    beachcoder wrote:My question is now: is there any way to install the previous Enlightenment E17 packages? They where much better that this one... or will another update come out soon??
    If you find some mirror which keeps outdated packages that should not be a problem. Be sure to downgrade all of e17 packages (also some packages were deprecated and thus removed from the server during the last upgrade so you'd need to have those as well. You may still have those on your system though)
    About a quick update, depends if Ican replicate it and if there is an easy fix. These things happen now and then with pre-alpha software when they do make major code changes.  I try to test every update locally before putting it live but I of course can't test every single feature.
    Last edited by pressh (2009-10-09 06:03:31)

  • Problems with Macbook after Software Update

    I haven't updated my Macbook in a long time, so I decided it was time I probably did. Software Update had updates for iTunes, Quicktime, and a 2009-Security Update. Everything seemed to be going okay. After the downloading and installing finished, it said the Security Update couldn't be installed and moved it to the trash. Then it prompted me to restart my computer because the other two installed okay.
    After restart, when my computer started back up, my Macbook is messed up. The doc is missing. I open a finder window, and it shows the main folders, but all the things on the right (where it shows the drive, applications, and such) is missing. I tried to back up my files, but it can't even read there is a blank disc inserted (keeps asking me to insert a blank disc). And it wont let me shut down my computer, or restart it. I click restart, and it seems like it accepts it, but it just doesn't do anything. The dashboard wont show up when you hit F12. This mac is all messed up.
    I don't know what happened here, all I installed was iTunes and Quicktime from the Software Update (security update didn't install), and all this happened. Any idea what happened and how I can fix this?
    I'm using Mac OSX Tiger 10.4.11.

    Welcome to Apple Discussions.
    There's a variety of things you could try, but first as to why it is doing this. Probably your drive was slightly corrupted. If it was minor you might not have noticed it, but when the updates tried to install, the whole thing compounded and led to a whole bunch of things missing.
    First, try to repair your drive. Boot from the System installer disc that came with your computer or is the one for the version you currently have on there, select language if applicable, choose utilities, run Disk Utility and verify (and repair if necessary) the drive. You can verify a drive from DU on your main drive while booted but I have found this can result in incorrect reporting of errors. To repair your drive you have to run it from a drive other than the boot drive anyway.
    Next, boot from your drive in [Safe Mode|http://docs.info.apple.com/article.html?artnum=107393] and repair permissions. You can repair permissions while booted from the installer disc but this uses the permissions configuration on the installer disc which may be out of date if you have run any updates on your computer. Booting your computer to Safe Mode restricts the number of things running on your computer while permissions are being run and does a bit of spring cleaning at the same time.
    Reading
    [Resolve startup issues and perform disk maintenance with Disk Utility and fsck|http://docs.info.apple.com/article.html?artnum=106214]
    [Using Disk Utility in Mac OS X 10.4.3 or later|http://docs.info.apple.com/article.html?artnum=302672]
    [Disk Utility's Repair Disk Permissions|http://docs.info.apple.com/article.html?artnum=25751]
    +Summary of above from BDaqua+ (couldn't have said it better):
    "Try Disk Utility
    1. Insert the Mac OS X Install disc that came with your computer (Edit: Do not use this disc if it is not the same general version as what you have currently on your computer, e.g. use a Tiger disc for a Tiger drive, not a Panther disc), then restart the computer while holding the C key.
    2. When your computer finishes starting up from the disc, choose Disk Utility from the Installer menu. (In Mac OS X 10.4 or later, you must select your language first.)
    Important: Do not click Continue in the first screen of the Installer. If you do, you must restart from the disc again to access Disk Utility.
    3. Click the First Aid tab.
    4. Click the disclosure triangle to the left of the hard drive icon to display the names of your hard disk volumes and partitions.
    5. Select your Mac OS X volume.
    6. Click Repair. Disk Utility checks and repairs the disk.
    Then Safe Boot, (holding Shift key down at bootup), run Disk Utility in Applications>Utilities, then highlight your drive, click on Repair Permissions, reboot when it completes."
    Report back after you have done this. It may be that you have to use a more powerful utility such as Diskwarrior.
    Once the drive is repaired you can try re-applying the two updates, though often it takes a full archive and install, plus re-application of all updates, to get everything working again.
    [Mac OS X: About the Archive and Install feature|http://support.apple.com/kb/HT1710]
    [Apple document about A&I in Tiger (10.4)|http://support.apple.com/kb/HT1545]
    [X-Lab Archive and install|http://www.thexlab.com/faqs/archiveinstall.html]
    [Kappy's A&I instructions|http://discussions.apple.com/thread.jspa?threadID=1823034]
    *In most cases _make sure_ you select "Preserve Users & Settings"*
    Finally, on updating:
    Updating
    Certain steps appear to minimize the risk of an update producing problems.
    Number one is to make sure you have a bootable clone backup of your computer in case you do need to back out of it again. This is the only guaranteed way of not having to worry about the results of an update.
    Some like to boot from their installer discs or an external backup and verify (and if necessary repair) their internal drives as well as drive permissions. This is done with Disk Utility. You can verify a drive while booted from the same drive but sometimes this produces spurious errors. Repairing a drive (if necessary) has to be done while booted from another disk.
    [Resolve startup issues and perform disk maintenance with Disk Utility and fsck|http://docs.info.apple.com/article.html?artnum=106214]
    [Using Disk Utility in Mac OS X 10.4.3 or later|http://docs.info.apple.com/article.html?artnum=302672]
    [Disk Utility's Repair Disk Permissions|http://docs.info.apple.com/article.html?artnum=25751]
    You can also go to the step of booting into safe mode to do the install.
    [Mac OS X: Starting up in Safe Mode|http://docs.info.apple.com/article.html?artnum=107393]
    [What is Safe Boot, Safe Mode? (Mac OS X)|http://docs.info.apple.com/article.html?artnum=107392]
    [Safe Boot takes longer than normal startup|http://docs.info.apple.com/article.html?artnum=107394]
    I like to download the update onto my computer and install it from there rather than let Software Update do it. I know a few people who had problems with doing the update via software updater found a manual install to work.
    Repair permissions again afterward.
    It helps to only install one update at a time and to run the computer for a while to make sure it is behaving well.
    The more cautious even like to unplug third party peripherals (see [comment by BDaqua|http://discussions.apple.com/message.jspa?messageID=9040746#9040746]).
    Almost all of the above steps (except backup) have been questioned (e.g., [Permissons repair|http://www.macworld.com/article/52220-3/2006/08/repairpermissions.html] as to necessity. Probably many people have done successful updates without doing them. I say they can't hurt, they can very likely do good (especially if your computer isn't regularly maintained), so why not do them to be safe?
    [BDaqua's comments on updating problems|http://discussions.apple.com/message.jspa?messageID=8948595#8948595]
    [Baby Boomer's comments on updating problems|http://discussions.apple.com/message.jspa?messageID=9025760#9025760]
    [Klaus1's post on updating and removing updates|http://discussions.apple.com/message.jspa?messageID=10257902] and [another one|http://discussions.apple.com/message.jspa?messageID=10402175]

  • Problems with waking after firmware update ...

    Hi ya'll - quick question.
    Did the latest firmware update last night and have noticed that waking the computer from sleep has become a problem, maybe once every three times I try to wake it? The backlight visibly turns on and illuminates the black screen, but the password box dosen't ever pop up, leaving me with a plain cursor. I'll try to hit random buttons (not that I think it'll help, but you know) and the 'Funk' sound plays, so I know the computer is working and is on. I have to hold the power button and restart it everytime. Any reason this might be happening now, after the update? It used to every now and then, and had sllooow wake times before the update, the latter of which has been fixed. The update was performed right and completed itself, etc.
    Thanks for any help!

    i also have problems waking it up since the efi firmware update! i primarily use the macbook only with an exernal display and wake it up by plugging in the power, lan, display and usb connectors, i.e. quite often, i don't even open the lid. since the firmware update, i regularly get a light blue screen and nothing happens. i then have to restart it through the power button as well.

  • Big problem with Z2 after the update to Firmware 17.1.1.A.0.402

    what can i do with my Z2 after the update to Firmware 17.1.1.A.0.402 
    the contact's app has stopped working everytime when i need too call someone on my contacts
    on the screen i recieve messages ' android.process.com ' has stopped working , or process.contact.com has stopped working , etc. ...
    i'm desperate , please help me !

    switch of device via holding the power button and up vol button wait till it vibrates 3 times then switch on the device once powered on , turn off normally then switch on again and all should be fine 

  • [Solved-ish] problem with autologin after xorg update

    Hi
    I use auto login like described on "Automatic login to virtual console", with the exception that i login as user on VT7 rather than VT1.
    Then execute startx on VT7 from zprofile, as shown in Start X at Login.
    After updating xorg this morning, I was on VT1 after boot. The screen was kind of blinking once a second, and totally unresponsive.
    Booting from the install image on an USB-stick, I commented startx in ~/.zprofile.
    After that I was again on VT1 but able to login and then run startx on VT1. Later I found out that I had a login on VT7 and was able to run startx there as well.
    Why wouldn't startx run automatically, when it runs fine manually.
    This is my [email protected]/autologin.conf
    nagual% cat [email protected]/autologin.conf
    [Service]
    ExecStart=
    ExecStart=-/sbin/agetty --autologin leo --noclear %I 38400 linux
    Type=simple
    startx is run from zprofile with:
    #[[ -z $DISPLAY && $XDG_VTNR == 7 ]] && exec startx -- vt$XDG_VTNR
    could it be because the display doesn't change to VT7, and why would an xorg update change that?
    Last edited by Leo Laursen (2014-07-30 17:54:14)

    mrunion wrote:When the upgrade to xorg-server occurred there was a warning about X starting on the appropriate VT. There was also news on the Arch Linux front page (https://www.archlinux.org/news/xorg-ser … available/). You may want to read that news and then look into an xorg.wrap file if necessary.
    Thanks. I did see this. As far as I can tell, it shouldn't matter in my case, but of course I could be wrong. I'm starting X on VT7, same as the login. I don't do any redirecting of stderr.
    And it is very curious that auto login is affected.

  • [SOLVED] Problem with murmur after upgrading to 1.2.3-4

    I've been running Murmur on my server for a long time without problems. The last version I had running was 1.2.3-3. After upgrading to 1.2.3-4, the already-running murmurd process crashed after a while (some hours after the upgrade, after constant use) and I'm unable to restart it. The message I get is:
    :: Starting murmur [BUSY]
    <W>2012-01-07 22:06:11.133 Initializing settings from /etc/murmur.ini (basepath /etc)
    <W>2012-01-07 22:06:11.134 OpenSSL: OpenSSL 1.0.0f 4 Jan 2012
    <W>2012-01-07 22:06:11.134 SSL: Adding recommended CA StartCom Certification Authority
    <W>2012-01-07 22:06:11.134 SSL: Adding recommended CA AAA Certificate Services
    <W>2012-01-07 22:06:11.135 SSL: Adding recommended CA UTN-USERFirst-Client Authentication and Email
    <C>2012-01-07 22:06:11.135 Successfully switched to uid 1007
    <F>2012-01-07 22:06:11.230 ServerDB: Failed initialization: unable to open database file Error opening database
    [DONE]
    and in murmur.log nothing gets written. Downgrading to 1.2.3-3 works, but I thought I'd look for the cause of the problem.
    After poking around a bit, I noticed that my murmur database (/var/lib/murmur/murmur.sqlite) belongs to a nonexistent user with a UID of 86 and a GID of 86, as well as the whole /var/log/murmur/ directory. I also noticed that a new murmur user and group with UID and GID of 1007 and 1000 exists on the system now. It seems that running:
    sudo chown -R murmur:murmur /var/lib/murmur/ /var/log/murmur/
    fixes the problem. Perhaps the update deleted my pre-existing murmur user and group and recreated them?
    Edit: Guess I should mark this as [SOLVED].
    Edit edit:
    Also turns out the whole /var/lib/murmur/ directory has to belong to murmur, not just the sqlite file.
    Last edited by n17ikh (2012-01-08 03:22:39)

    I had the same problem and fixed it like you.

  • Problem with N73 after firmware update

    Recently I tried to update the firmware on my Nokia n73. Somehow the cable got disconnected and the phone died. I read everything on the topic here and went directly to the nearest NCS. There they repaired my phone and updated the firmware to V3.0638.0.0.30 (everything else shown after *#0000# is: 30-10-2006, RM-133, Nokia N73 (05)). But after that, I noticed that when I press the multimedia button, it opens directly the music player, instead of a list of applications. Also when I hold down the menu button it shows both the standby icon and the music one. My problem is that I mostly use the camera, not the music player, and it seems (to me) that it slows the phone down (especially when going through the image gallery). So I was wondering if anyone can tell me how to close the music player, or at least how to change back the multimedia button to a list of applications. I am using the standard 128mb miniSD. Thanks in advance and cheers from Bulgaria.
    "Two things are infinite: the universe and human stupidity; and I'm not sure about the universe."
    Albert Einstein

    don't mean to be rude, but where are those Multimedia options? i tried settings, profiles...and besides that when i press the multimedia button i end up at a screen with "Now Playing" on top and when i Press "back" two times i go to "Music menu" from where i have either
    OPTIONS ->
    - Go to now playing
    - Go to Music shop
    - Refresh music library
    - Music library details
    - Help
    or
    PHONE which brings me to the standby display...Message Edited by radi78231 on 12-Jan-2007
    04:43 PM
    "Two things are infinite: the universe and human stupidity; and I'm not sure about the universe."
    Albert Einstein

  • Problems with startup after software update

    I have just done a software update on my system, and now going back to my computer 2 hours later and turning it on, all I get is the grey screen with the apple and dial spinning...........
    Also the fans in the tower are going nuts.
    Is this normal for updates since leopard, seeing as I have never had this happen to me before

    No, that's not normal. It could be hardware. Shutdown.
    Run Apple Hardware Test:
    1. Disconnect all external devices from your iMac except the keyboard and mouse.
    If you have an Ethernet cable connected, disconnect it.
    2. Insert the Mac OS X Install Disc 1 that came with your iMac.
    3. Restart your iMac and hold down the D key as your iMac starts up.
    4. When the Apple Hardware Test chooser screen appears, select the language
    appropriate for your location.
    5. Press the Return key or click the right arrow button.
    6. When the Apple Hardware Test main screen appears (after about 45 seconds), follow
    the onscreen instructions.
    7. Apple Hardware Test displays an error code if it detects a problem. Make a note of the
    error code before pursuing support options.
    Let us know.
    -mj

  • [solved] problems with pacman after upgrading to 2.6.27-ARCH

    i'm not sure if my problem is related with the new version of software or the fact that i ran out of space during the upgrade. but once i restarted after the upgrade i was not able to boot into the system and the error i would get was:
    ERROR: Failed to parse block device name for '/dev/sda3'
    unknown
    ERROR: root fs cannot be detected. Try using the rootfstype= kernel parameter.
    i followed what some other people did and i booted with livecd, chrooted and regenerated mkinitcpio. since i saw some other people having the same problems here is what i used:
    http://wiki.archlinux.org/index.php/Boo … omplicated
    http://wiki.archlinux.org/index.php/Mki … ng_presets
    and just for good measure i decided to run fsck:
    http://wiki.archlinux.org/index.php/Fsck
    i was still seeing some segmentation faults so i decided to re-install all of the packages installed:
    http://wiki.archlinux.org/index.php/Pac … re_Restore
    now everything seems to work OK except when i run pacman. here is what i get:
    /sbin/ldconfig: /usr/lib/libgettextpo.so is not an ELF file - it has the wrong magic bytes at the start.
    /sbin/ldconfig: /usr/lib/libwiretap.so.0.0.1 is not an ELF file - it has the wrong magic bytes at the start.
    /sbin/ldconfig: /usr/lib/libasprintf.so.0 is not an ELF file - it has the wrong magic bytes at the start.
    /sbin/ldconfig: /usr/lib/libasprintf.so.0.0.0 is not an ELF file - it has the wrong magic bytes at the start.
    /sbin/ldconfig: /usr/lib/libsigc-2.0.so is not an ELF file - it has the wrong magic bytes at the start.
    /sbin/ldconfig: /usr/lib/libasprintf.so is not an ELF file - it has the wrong magic bytes at the start.
    /sbin/ldconfig: /usr/lib/libwiretap.so is not an ELF file - it has the wrong magic bytes at the start.
    /sbin/ldconfig: /usr/lib/libgettextpo.so.0.4.0 is not an ELF file - it has the wrong magic bytes at the start.
    /sbin/ldconfig: /usr/lib/libgettextsrc.so is not an ELF file - it has the wrong magic bytes at the start.
    /sbin/ldconfig: /usr/lib/libsigc-2.0.so.0 is not an ELF file - it has the wrong magic bytes at the start.
    /sbin/ldconfig: /usr/lib/libgettextsrc-0.17.so is not an ELF file - it has the wrong magic bytes at the start.
    /sbin/ldconfig: /usr/lib/libgettextpo.so.0 is not an ELF file - it has the wrong magic bytes at the start.
    /sbin/ldconfig: /usr/lib/libgettextlib-0.17.so is not an ELF file - it has the wrong magic bytes at the start.
    /sbin/ldconfig: /usr/lib/libsigc-2.0.so.0.0.0 is not an ELF file - it has the wrong magic bytes at the start.
    /sbin/ldconfig: /usr/lib/libwiretap.so.0 is not an ELF file - it has the wrong magic bytes at the start.
    /sbin/ldconfig: /usr/lib/libgettextlib.so is not an ELF file - it has the wrong magic bytes at the start.
    packages are still installed but i would like to get to the bottom of this and get it fixed. any ideas what went wrong (well... besides me running out of disk space!) and how to get it fixed?
    Last edited by djidji (2008-10-24 17:49:14)

    thanks for the reply. i tried finding out what packages these libraries beling to but for every single one of these listed i get an error saying that "No packages owns...". could it be something with ldconfig?
    EDIT:
    so i figured out that one of the files was related to wireshark. i tried re-installing wireshark and here is what i got:
    : sudo pacman -Sy wireshark
    :: Synchronizing package databases...
    core 31.4K 229.6K/s 00:00:00 [#############################################################################################] 100%
    extra 413.1K 508.9K/s 00:00:01 [#############################################################################################] 100%
    community 356.3K 298.9K/s 00:00:01 [#############################################################################################] 100%
    resolving dependencies...
    looking for inter-conflicts...
    Targets (1): wireshark-1.0.4-1
    Total Download Size: 11.89 MB
    Total Installed Size: 51.80 MB
    Proceed with installation? [Y/n]
    :: Retrieving packages from extra...
    wireshark-1.0.4-1-i686 11.9M 455.5K/s 00:00:27 [#############################################################################################] 100%
    checking package integrity...
    (1/1) checking for file conflicts [#############################################################################################] 100%
    error: could not prepare transaction
    error: failed to commit transaction (conflicting files)
    wireshark: /usr/bin/capinfos exists in filesystem
    wireshark: /usr/bin/dftest exists in filesystem
    wireshark: /usr/bin/dumpcap exists in filesystem
    wireshark: /usr/bin/editcap exists in filesystem
    wireshark: /usr/bin/idl2wrs exists in filesystem
    wireshark: /usr/bin/mergecap exists in filesystem
    wireshark: /usr/bin/randpkt exists in filesystem
    wireshark: /usr/bin/rawshark exists in filesystem
    wireshark: /usr/bin/text2pcap exists in filesystem
    wireshark: /usr/bin/tshark exists in filesystem
    wireshark: /usr/bin/wireshark exists in filesystem
    wireshark: /usr/lib/libwireshark.so exists in filesystem
    wireshark: /usr/lib/libwireshark.so.0 exists in filesystem
    wireshark: /usr/lib/libwireshark.so.0.0.1 exists in filesystem
    wireshark: /usr/lib/libwiretap.so exists in filesystem
    wireshark: /usr/lib/libwiretap.so.0 exists in filesystem
    wireshark: /usr/lib/libwiretap.so.0.0.1 exists in filesystem
    wireshark: /usr/share/man/man1/capinfos.1 exists in filesystem
    wireshark: /usr/share/man/man1/dumpcap.1 exists in filesystem
    wireshark: /usr/share/man/man1/editcap.1 exists in filesystem
    wireshark: /usr/share/man/man1/idl2wrs.1 exists in filesystem
    wireshark: /usr/share/man/man1/mergecap.1 exists in filesystem
    wireshark: /usr/share/man/man1/rawshark.1 exists in filesystem
    wireshark: /usr/share/man/man1/text2pcap.1 exists in filesystem
    wireshark: /usr/share/man/man1/tshark.1 exists in filesystem
    wireshark: /usr/share/man/man1/wireshark.1 exists in filesystem
    wireshark: /usr/share/man/man4/wireshark-filter.4 exists in filesystem
    wireshark: /usr/share/wireshark/AUTHORS-SHORT exists in filesystem
    wireshark: /usr/share/wireshark/COPYING exists in filesystem
    wireshark: /usr/share/wireshark/capinfos.html exists in filesystem
    wireshark: /usr/share/wireshark/cfilters exists in filesystem
    wireshark: /usr/share/wireshark/colorfilters exists in filesystem
    wireshark: /usr/share/wireshark/dfilters exists in filesystem
    wireshark: /usr/share/wireshark/diameter/Ericsson.xml exists in filesystem
    wireshark: /usr/share/wireshark/diameter/TGPPGmb.xml exists in filesystem
    wireshark: /usr/share/wireshark/diameter/TGPPSh.xml exists in filesystem
    wireshark: /usr/share/wireshark/diameter/chargecontrol.xml exists in filesystem
    wireshark: /usr/share/wireshark/diameter/dictionary.dtd exists in filesystem
    wireshark: /usr/share/wireshark/diameter/dictionary.xml exists in filesystem
    wireshark: /usr/share/wireshark/diameter/etsie2e4.xml exists in filesystem
    wireshark: /usr/share/wireshark/diameter/gqpolicy.xml exists in filesystem
    wireshark: /usr/share/wireshark/diameter/imscxdx.xml exists in filesystem
    wireshark: /usr/share/wireshark/diameter/mobileipv4.xml exists in filesystem
    wireshark: /usr/share/wireshark/diameter/nasreq.xml exists in filesystem
    wireshark: /usr/share/wireshark/diameter/sip.xml exists in filesystem
    wireshark: /usr/share/wireshark/diameter/sunping.xml exists in filesystem
    wireshark: /usr/share/wireshark/dtds/dc.dtd exists in filesystem
    wireshark: /usr/share/wireshark/dtds/itunes.dtd exists in filesystem
    wireshark: /usr/share/wireshark/dtds/mscml.dtd exists in filesystem
    wireshark: /usr/share/wireshark/dtds/pocsettings.dtd exists in filesystem
    wireshark: /usr/share/wireshark/dtds/presence.dtd exists in filesystem
    wireshark: /usr/share/wireshark/dtds/reginfo.dtd exists in filesystem
    wireshark: /usr/share/wireshark/dtds/rlmi.dtd exists in filesystem
    wireshark: /usr/share/wireshark/dtds/rss.dtd exists in filesystem
    wireshark: /usr/share/wireshark/dtds/smil.dtd exists in filesystem
    wireshark: /usr/share/wireshark/dtds/watcherinfo.dtd exists in filesystem
    wireshark: /usr/share/wireshark/dtds/xcap-caps.dtd exists in filesystem
    wireshark: /usr/share/wireshark/dtds/xcap-error.dtd exists in filesystem
    wireshark: /usr/share/wireshark/dumpcap.html exists in filesystem
    wireshark: /usr/share/wireshark/editcap.html exists in filesystem
    wireshark: /usr/share/wireshark/help/capture_filters.txt exists in filesystem
    wireshark: /usr/share/wireshark/help/capturing.txt exists in filesystem
    wireshark: /usr/share/wireshark/help/display_filters.txt exists in filesystem
    wireshark: /usr/share/wireshark/help/faq.txt exists in filesystem
    wireshark: /usr/share/wireshark/help/getting_started.txt exists in filesystem
    wireshark: /usr/share/wireshark/help/overview.txt exists in filesystem
    wireshark: /usr/share/wireshark/help/toc exists in filesystem
    wireshark: /usr/share/wireshark/idl2wrs.html exists in filesystem
    wireshark: /usr/share/wireshark/manuf exists in filesystem
    wireshark: /usr/share/wireshark/mergecap.html exists in filesystem
    wireshark: /usr/share/wireshark/radius/dictionary exists in filesystem
    wireshark: /usr/share/wireshark/radius/dictionary.3com exists in filesystem
    wireshark: /usr/share/wireshark/radius/dictionary.3gpp exists in filesystem
    wireshark: /usr/share/wireshark/radius/dictionary.3gpp2 exists in filesystem
    wireshark: /usr/share/wireshark/radius/dictionary.acc exists in filesystem
    wireshark: /usr/share/wireshark/radius/dictionary.alcatel exists in filesystem
    wireshark: /usr/share/wireshark/radius/dictionary.alteon exists in filesystem
    wireshark: /usr/share/wireshark/radius/dictionary.altiga exists in filesystem
    wireshark: /usr/share/wireshark/radius/dictionary.aptis exists in filesystem
    wireshark: /usr/share/wireshark/radius/dictionary.ascend exists in filesystem
    wireshark: /usr/share/wireshark/radius/dictionary.bay exists in filesystem
    wireshark: /usr/share/wireshark/radius/dictionary.bintec exists in filesystem
    wireshark: /usr/share/wireshark/radius/dictionary.bristol exists in filesystem
    wireshark: /usr/share/wireshark/radius/dictionary.cablelabs exists in filesystem
    wireshark: /usr/share/wireshark/radius/dictionary.cabletron exists in filesystem
    wireshark: /usr/share/wireshark/radius/dictionary.cisco exists in filesystem
    wireshark: /usr/share/wireshark/radius/dictionary.cisco.bbsm exists in filesystem
    wireshark: /usr/share/wireshark/radius/dictionary.cisco.vpn3000 exists in filesystem
    wireshark: /usr/share/wireshark/radius/dictionary.cisco.vpn5000 exists in filesystem
    wireshark: /usr/share/wireshark/radius/dictionary.colubris exists in filesystem
    wireshark: /usr/share/wireshark/radius/dictionary.columbia_university exists in filesystem
    wireshark: /usr/share/wireshark/radius/dictionary.compat exists in filesystem
    wireshark: /usr/share/wireshark/radius/dictionary.cosine exists in filesystem
    wireshark: /usr/share/wireshark/radius/dictionary.ericsson exists in filesystem
    wireshark: /usr/share/wireshark/radius/dictionary.erx exists in filesystem
    wireshark: /usr/share/wireshark/radius/dictionary.extreme exists in filesystem
    wireshark: /usr/share/wireshark/radius/dictionary.foundry exists in filesystem
    wireshark: /usr/share/wireshark/radius/dictionary.freeradius exists in filesystem
    wireshark: /usr/share/wireshark/radius/dictionary.gandalf exists in filesystem
    wireshark: /usr/share/wireshark/radius/dictionary.garderos exists in filesystem
    wireshark: /usr/share/wireshark/radius/dictionary.gemtek exists in filesystem
    wireshark: /usr/share/wireshark/radius/dictionary.itk exists in filesystem
    wireshark: /usr/share/wireshark/radius/dictionary.juniper exists in filesystem
    wireshark: /usr/share/wireshark/radius/dictionary.karlnet exists in filesystem
    wireshark: /usr/share/wireshark/radius/dictionary.livingston exists in filesystem
    wireshark: /usr/share/wireshark/radius/dictionary.localweb exists in filesystem
    wireshark: /usr/share/wireshark/radius/dictionary.merit exists in filesystem
    wireshark: /usr/share/wireshark/radius/dictionary.microsoft exists in filesystem
    wireshark: /usr/share/wireshark/radius/dictionary.mikrotik exists in filesystem
    wireshark: /usr/share/wireshark/radius/dictionary.navini exists in filesystem
    wireshark: /usr/share/wireshark/radius/dictionary.netscreen exists in filesystem
    wireshark: /usr/share/wireshark/radius/dictionary.nokia exists in filesystem
    wireshark: /usr/share/wireshark/radius/dictionary.nomadix exists in filesystem
    wireshark: /usr/share/wireshark/radius/dictionary.propel exists in filesystem
    wireshark: /usr/share/wireshark/radius/dictionary.quintum exists in filesystem
    wireshark: /usr/share/wireshark/radius/dictionary.redback exists in filesystem
    wireshark: /usr/share/wireshark/radius/dictionary.redcreek exists in filesystem
    wireshark: /usr/share/wireshark/radius/dictionary.shasta exists in filesystem
    wireshark: /usr/share/wireshark/radius/dictionary.shiva exists in filesystem
    wireshark: /usr/share/wireshark/radius/dictionary.sonicwall exists in filesystem
    wireshark: /usr/share/wireshark/radius/dictionary.springtide exists in filesystem
    wireshark: /usr/share/wireshark/radius/dictionary.t_systems_nova exists in filesystem
    wireshark: /usr/share/wireshark/radius/dictionary.telebit exists in filesystem
    wireshark: /usr/share/wireshark/radius/dictionary.trapeze exists in filesystem
    wireshark: /usr/share/wireshark/radius/dictionary.tunnel exists in filesystem
    wireshark: /usr/share/wireshark/radius/dictionary.unisphere exists in filesystem
    wireshark: /usr/share/wireshark/radius/dictionary.unix exists in filesystem
    wireshark: /usr/share/wireshark/radius/dictionary.usr exists in filesystem
    wireshark: /usr/share/wireshark/radius/dictionary.valemount exists in filesystem
    wireshark: /usr/share/wireshark/radius/dictionary.versanet exists in filesystem
    wireshark: /usr/share/wireshark/radius/dictionary.wispr exists in filesystem
    wireshark: /usr/share/wireshark/radius/dictionary.xedia exists in filesystem
    wireshark: /usr/share/wireshark/rawshark.html exists in filesystem
    wireshark: /usr/share/wireshark/services exists in filesystem
    wireshark: /usr/share/wireshark/smi_modules exists in filesystem
    wireshark: /usr/share/wireshark/text2pcap.html exists in filesystem
    wireshark: /usr/share/wireshark/tpncp/tpncp.dat exists in filesystem
    wireshark: /usr/share/wireshark/tshark.html exists in filesystem
    wireshark: /usr/share/wireshark/wimaxasncp/dictionary.dtd exists in filesystem
    wireshark: /usr/share/wireshark/wimaxasncp/dictionary.xml exists in filesystem
    wireshark: /usr/share/wireshark/wireshark-filter.html exists in filesystem
    wireshark: /usr/share/wireshark/wireshark.html exists in filesystem
    wireshark: /usr/share/wireshark/ws.css exists in filesystem
    Errors occurred, no packages were upgraded.
    i'm hoping there is a way to sort this out. i'm loving the way my laptop is set up and would have re-install everything...
    Last edited by djidji (2008-10-24 01:27:00)

  • HELP! Problems with MacBook after software updates install.

    Hi Guys,
    I have a friend of mine that has a MacBook. After a while without doing the software updates she connected her MacBook on the internet and there was a lot of software updates to do, so she went on and install everything. She describes me that the problem was with Tiger 10.4.11, it pop up a "Warning Sign - Error" and freezes she says.
    She re-start the computer and It get stuck on the gray window with the Apple with the lil circle spinning endless.
    Is there any tip or something that I can help her?...
    [Sorry about my english... lol)

    Hello coreanomac!
    The following Apple Support article is good for working through the problem. Based on your explanation of what happened, follow the advice of the "Try a different software update source" and "Installation fails during 'optimization'" paragraphs of the "Troubleshooting an unsuccessful installation" section:
    Mac OS X: Troubleshooting installation and software updates
    Also reading the "Before Installing" section may be useful, as well.

Maybe you are looking for