Announcement

Collapse
No announcement yet.

Error on X or kdm (apparently) after upgrade to intrepid

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Error on X or kdm (apparently) after upgrade to intrepid

    I just decided to upgrade from kubuntu 8.04 kde4 (working perfectly) to Intrepid.

    The upgrade process occurred with no errors, but when i reboit i got some problems...

    First: when kdm loaded, i got an error about "no greeter plugin".
    Then, i felt on console, logged in and tried "startx" (with and without "sudo"). The X server loaded (i got that black and white screen with the x mouse pointer) but it crashed with messages about problems on keyboard configurations, involving xkbcomp.

    Does anybody have some suggestion?

    My computer is a Dell Vostro 1000 with ATI-radeon.
    Kubuntu 15.10 - Asus All-in-one (i3, 4GB ram)
    Tags: None
    • Top
    • Bottom
    #2
    Re: Error on X or kdm (apparently) after upgrade to intrepid

    I am trying!

    I attached the Xorg log file, but i could not gt information from it by myself...
    Attached Files
    Kubuntu 15.10 - Asus All-in-one (i3, 4GB ram)
    • Top
    • Bottom

    Comment

      #3
      Re: Error on X or kdm (apparently) after upgrade to intrepid

      I tried to reinstall the driver of my ATI using the latest version but, then, i got this error:

      Verifying archive integrity... All good.
      Uncompressing ATI Proprietary Linux Driver-8.542...
      ==================================================
      ATI Technologies Linux Driver Installer/Packager
      ==================================================

      Error: ./default_policy.sh does not support version
      default:v286_64:lib32::none:2.6.27-7-generic; make sure that the version is being
      correctly set by --iscurrentdistro

      Removing temporary directory: fglrx-install.DX8767
      Moreover, the following quotation is from the log file of kdm with my last boot try:

      ************************************************** ******************************
      Note that your system uses syslog. All of kdm's internally generated messages
      (i.e., not from libraries and external programs/scripts it uses) go to the
      daemon.* syslog facility; check your syslog configuration to find out to which
      file(s) it is logged. PAM logs messages related to authentication to authpriv.*.
      ************************************************** ******************************

      X.Org X Server 1.5.2
      Release Date: 10 October 2008
      X Protocol Version 11, Revision 0
      Build Operating System: Linux 2.6.24-16-server x86_64 Ubuntu
      Current Operating System: Linux doleo 2.6.27-7-generic #1 SMP Fri Oct 24 06:40:41 UTC 2008 x86_64
      Build Date: 24 October 2008 09:06:49AM
      xorg-server 2:1.5.2-2ubuntu3 (buildd@crested.buildd)
      Before reporting problems, check http://wiki.x.org
      to make sure that you have the latest version.
      Module Loader present
      Markers: (--) probed, (**) from config file, (==) default setting,
      (++) from command line, (!!) notice, (II) informational,
      (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
      (==) Log file: "/var/log/Xorg.0.log", Time: Wed Oct 29 23:35:25 2008
      (==) Using config file: "/etc/X11/xorg.conf"
      (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:0:0) found
      (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:1:0) found
      (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:5:0) found
      (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:6:0) found
      (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:18:0) found
      (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:19:0) found
      (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:19:1) found
      (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:19:2) found
      (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:19:3) found
      (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:19:4) found
      (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:19:5) found
      (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:0) found
      (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:1) found
      (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:2) found
      (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:3) found
      (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:4) found
      (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:0:0) found
      (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:1:0) found
      (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:5:0) found
      (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:6:0) found
      (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:18:0) found
      (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:19:0) found
      (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:19:1) found
      (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:19:2) found
      (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:19:3) found
      (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:19:4) found
      (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:19:5) found
      (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:0) found
      (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:1) found
      (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:2) found
      (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:3) found
      (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:4) found
      FATAL: Module fglrx not found.
      (EE) fglrx(0): atiddxDriScreenInit failed, GPS not been initialized.
      (EE) fglrx(0): XMM failed to open CMMQS connection.
      The XKEYBOARD keymap compiler (xkbcomp) reports:
      > Warning: Duplicate shape name "RTRN"
      > Using last definition
      > Warning: Duplicate shape name "RTSH"
      > Using last definition
      > Warning: Don't know how to merge sections yet
      > Warning: Don't know how to merge sections yet
      > Warning: Don't know how to merge sections yet
      > Warning: Don't know how to merge sections yet
      > Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
      > Ignoring extra symbols
      Errors from xkbcomp are not fatal to the X server
      The XKEYBOARD keymap compiler (xkbcomp) reports:
      > Warning: Duplicate shape name "RTRN"
      > Using last definition
      > Warning: Duplicate shape name "RTSH"
      > Using last definition
      > Warning: Don't know how to merge sections yet
      > Warning: Don't know how to merge sections yet
      > Warning: Don't know how to merge sections yet
      > Warning: Don't know how to merge sections yet
      > Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
      > Ignoring extra symbols
      Errors from xkbcomp are not fatal to the X server
      Any idea?
      Kubuntu 15.10 - Asus All-in-one (i3, 4GB ram)
      • Top
      • Bottom

      Comment

        #4
        Re: Error on X or kdm (apparently) after upgrade to intrepid

        As i got no solution, just installed Intrepid from zero and everything is fine now.
        Kubuntu 15.10 - Asus All-in-one (i3, 4GB ram)
        • Top
        • Bottom

        Comment

        Previous template Next
        Working...
        X