Announcement

**SheeEttin** · Jun 14, 2007, 02:20 PM

Re: Beryl Issue

Well, the first place to check would be in the trash, assuming you didn't clear it recently.

After that, you could just create an empty file in the place of your RC and just reconfigure from there.

**STEVE555** · Jun 14, 2007, 03:20 PM

Re: Beryl Issue

Hi SheeEttin,
Thank you for your quick response.I did a search for the .xcompmgrrc file in find files&folders,but to no avial(Unfortunetly I don't have a trash icon on my desktop).

So here's what I did.I did a Goolge search for the file,I found someone had posted the contents of their .xcompmgrrc file.I ran sudo kwrite /home/steve/.xcompmgrrc and copied and pasted the contents into the .xcompmgrrc file I had created and saved it.Luckily,When I ran beryl-manager from konsole,it had found the file.When I run beryl-manager form konsole,I get no output,but the Beryl icon appears,but I don't get the floaty effects.I then right-clicked on the Beryl icon and selected the window manager as Beryl,I get this output from konsole:

steve@mernivia:~$ beryl-manager
steve@mernivia:~$ ************************************************** ************
* Beryl system compatiblity check *
************************************************** ************

Detected xserver : NVIDIA

Checking Display :0.0 ...

Checking for XComposite extension : passed (v0.3)
Checking for XDamage extension : passed
Checking for RandR extension : passed
Checking for XSync extension : passed

Checking Screen 0 ...

Checking for GLX_SGIX_fbconfig : passed
Checking for GLX_EXT_texture_from_pixmap : passed
Checking for non power of two texture support : passed
Checking maximum texture size : passed (4096x4096)

beryl: Another composite manager is already running on screen: 0
beryl: No manageable screens found on display :0.0
trying '/home/steve/.xcompmgrrc' as configfile

finished parsing the config file

I hope someone can help me with this one.

Regards,
STEVE555

**SheeEttin** · Jun 14, 2007, 05:30 PM

Re: Beryl Issue

Well, I was suspecting that that wouldn't help.

Anyway, like it says, you've already got a composite manager running. That'd be kwin.

You can kill kwin by issuing "killall kwin". If you need to get it back, just switch to a terminal (Alt+F1), log in, and execute "kwin --display :0 &".

**STEVE555** · Jun 15, 2007, 02:13 AM

Re: Beryl Issue

Hi SheeEttin,
Thanks for the advice.I've just tried in konsole "killall kwin" and then ran "beryl-manager",but exactly the same thing happens in my last post.

Here is my xorg.conf:

Code:

# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig: version 1.0 (buildmeister@builder3) Mon Feb 26 23:38:46 PST 2007

# /etc/X11/xorg.conf (xorg X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the xorg.conf(5) manual page.
# (Type "man xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
# sudo dpkg-reconfigure -phigh xserver-xorg
#Section "InputDevice"
#  Identifier  "stylus"
#  Driver    "wacom"
#  Option    "Device" "/dev/input/wacom"
#  Option    "Type" "stylus"
#  Option    "ForceDevice" "ISDV4"# Tablet PC ONLY
#EndSection
#Section "InputDevice"
#  Identifier  "eraser"
#  Driver    "wacom"
#  Option    "Device" "/dev/input/wacom"
#  Option    "Type" "eraser"
#  Option    "ForceDevice" "ISDV4"# Tablet PC ONLY
#EndSection
#Section "InputDevice"
#  Identifier  "cursor"
#  Driver    "wacom"
#  Option    "Device" "/dev/input/wacom"
#  Option    "Type" "cursor"
#  Option    "ForceDevice" "ISDV4"# Tablet PC ONLY
#EndSection

Section "ServerLayout"

#  InputDevice  "stylus" "SendCoreEvents"
#  InputDevice  "cursor" "SendCoreEvents"
#  InputDevice  "eraser" "SendCoreEvents"
  Identifier  "Default Layout"
  Screen   0 "Default Screen" 0 0
  InputDevice  "Generic Keyboard"
  InputDevice  "Configured Mouse"
EndSection

Section "Files"

 # path to defoma fonts
  FontPath    "/usr/share/fonts/X11/misc"
  FontPath    "/usr/share/fonts/X11/cyrillic"
  FontPath    "/usr/share/fonts/X11/100dpi/:unscaled"
  FontPath    "/usr/share/fonts/X11/75dpi/:unscaled"
  FontPath    "/usr/share/fonts/X11/Type1"
  FontPath    "/usr/share/fonts/X11/100dpi"
  FontPath    "/usr/share/fonts/X11/75dpi"
  FontPath    "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
EndSection

Section "Module"
  Load     "i2c"
  Load     "bitmap"
  Load     "ddc"
  Load     "extmod"
  Load     "freetype"
  Load     "int10"
  Load     "vbe"
  Load     "glx"
  Load     "v4l"
EndSection

Section "InputDevice"
  Identifier  "Generic Keyboard"
  Driver    "kbd"
  Option    "CoreKeyboard"
  Option    "XkbRules" "xorg"
  Option    "XkbModel" "pc105"
  Option    "XkbLayout" "gb"
  Option    "XkbOptions" "lv3:ralt_switch"
EndSection

Section "InputDevice"
  Identifier  "Configured Mouse"
  Driver    "mouse"
  Option    "CorePointer"
  Option    "Device" "/dev/input/mice"
  Option    "Protocol" "ImPS/2"
  Option    "ZAxisMapping" "4 5"
  Option    "Emulate3Buttons" "true"
EndSection

Section "Monitor"
  Identifier  "Generic Monitor"
  VendorName  "Generic"
  ModelName   "1280x1024 @ 60 Hz"
  HorizSync   31.5 - 64.3
  VertRefresh  50.0 - 70.0
  Gamma     1
  ModeLine   "640x480@60" 25.2 640 656 752 800 480 490 492 525 -hsync -vsync
  ModeLine   "800x600@56" 36.0 800 824 896 1024 600 601 603 625 +hsync +vsync
  ModeLine   "800x600@60" 40.0 800 840 968 1056 600 601 605 628 +hsync +vsync
  ModeLine   "1024x768@70" 75.0 1024 1048 1184 1328 768 771 777 806 -hsync -vsync
  ModeLine   "1024x768@60" 65.0 1024 1048 1184 1344 768 771 777 806 -hsync -vsync
  ModeLine   "1280x960@60" 102.1 1280 1360 1496 1712 960 961 964 994 -hsync +vsync
  ModeLine   "1280x1024@60" 108.0 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync
EndSection

Section "Monitor"

 #
  Identifier  "monitor1"
  VendorName  "Plug 'n' Play"
  ModelName   "Plug 'n' Play"
  Gamma     1
  ModeLine   "640x480@60" 25.2 640 656 752 800 480 490 492 525 -hsync -vsync
EndSection

Section "Device"
  Identifier  "nVidia Corporation NV40 [GeForce 6800 GT]"
  Driver    "nvidia"
  VendorName  "NVIDIA"
  BoardName   "NVIDIA GeForce 6800 (generic)"
  BusID     "PCI:1:0:0"
  Screen     0
EndSection

Section "Device"

 #
  Identifier  "device1"
  Driver    "nvidia"
  VendorName  "NVIDIA"
  BoardName   "NVIDIA GeForce 6800 (generic)"
  BusID     "PCI:1:0:0"
  Screen     1
EndSection

Section "Screen"
  Identifier  "Default Screen"
  Device    "nVidia Corporation NV40 [GeForce 6800 GT]"
  Monitor    "Generic Monitor"
  DefaultDepth  24
  Option    "AddARGBGLXVisuals" "True"
  Option    "RenderAccel" "True"
  Option    "AllowGLXWithComposite" "True"
  SubSection  "Display"
    Virtual  1280 1024
    Depth   24
    Modes   "1280x1024@60" "1280x960@60" "1024x768@60" "1024x768@70" "800x600@60" "800x600@56" "640x480@60"
  EndSubSection
EndSection

Section "Screen"

 #
  Identifier  "screen1"
  Device    "device1"
  Monitor    "monitor1"
  DefaultDepth  24
  SubSection  "Display"
    Depth   24
    Modes   "640x480@60"
  EndSubSection
EndSection

Section "Extensions"
  Option    "Composite" "Enable"
  Option    "RENDER" "Enabled"
  Option    "DAMAGE" "Enabled"
EndSection

Regards,
STEVE555

**mchuskie** · Jun 15, 2007, 03:16 AM

Re: Beryl Issue

This is, I suspect, not the problem.

You should start "beryl" AND "beryl-manager" - otherwise X continues quite happily to use kwin, and beryl-manager can't manage any screens because beryl isn't running. Hence:

Code:

beryl: Another composite manager is already running on screen: 0
beryl: No manageable screens found on display :0.0

I wouldn't explicitly kill kwin; rather, start Beryl, and it should automatically replace kwin as the active window manager.

**STEVE555** · Jun 15, 2007, 03:45 AM

Re: Beryl Issue

Hi JamesM,
Thank you for your advice.I've ran Beryl form the console and here's the output:

Code:

steve@mernivia:~$ beryl
**************************************************************
* Beryl system compatiblity check              *
**************************************************************

Detected xserver                : NVIDIA

Checking Display :0.0 ...

Checking for XComposite extension        : passed (v0.3)
Checking for XDamage extension         : passed
Checking for RandR extension          : passed
Checking for XSync extension          : passed

Checking Screen 0 ...

Checking for GLX_SGIX_fbconfig         : passed
Checking for GLX_EXT_texture_from_pixmap    : passed
Checking for non power of two texture support  : passed
Checking maximum texture size          : passed (4096x4096)

Relaunching beryl with __GL_YIELD="NOTHING"
**************************************************************
* Beryl system compatiblity check              *
**************************************************************

Detected xserver                : NVIDIA

Checking Display :0.0 ...

Checking for XComposite extension        : passed (v0.3)
Checking for XDamage extension         : passed
Checking for RandR extension          : passed
Checking for XSync extension          : passed

Checking Screen 0 ...

Checking for GLX_SGIX_fbconfig         : passed
Checking for GLX_EXT_texture_from_pixmap    : passed
Checking for non power of two texture support  : passed
Checking maximum texture size          : passed (4096x4096)

Reloading options

but I get the classic no title-bar on top of my windows,and no beryl icon on the taskbar.

I then ran beryl-manager,but I get this output:

Code:

beryl-manager
X connection to :0.0 broken (explicit kill or server shutdown).
steve@mernivia:~$
steve@mernivia:~$ beryl-manager
steve@mernivia:~$

I hope that helps.

Regards,
STEVE555

**dibl** · Jun 15, 2007, 05:07 AM

Re: Beryl Issue

You're close, steve. What Nvidia chip are you using?

Here are a couple of points:
- the lack of window tops and sides is not, strictly speaking, a Beryl problem, although it shows up when Beryl doesn't find a suitable "window decorator" -- this is fixable when Beryl is installed

- the lack of a Beryl icon on your taskbar indicates that it is not running -- that's a problem

- I'd recommend verifying that your Nvidia driver is fully and correctly installed first. In a konsole, enter

Code:

nvidia-settings

you should get the Nvidia utility panel, under "X Screen 0" the fifth item down is "OpenGL/GLX Information". You should be able to click on that and see that a lot of GLX functions are shown. If this all looks good, then

- I'd recommend running

Code:

sudo nvidia-xconfig --add-argb-glx-visuals --composite

which will rebuild your xorg.conf file for optimal use of the 3D acceleration capability of your Nvidia chip.

HTH!

**STEVE555** · Jun 16, 2007, 05:02 PM

Re: Beryl Issue

Hi dibl,
Thank you very much for your response.I have been trying to upload my errors from nvidia-settings from konsole,but I get this message:

Code:

The upload folder is full. Please try a smaller file and/or contact an administrator.

The file is only 4kb in size and I've saved it as a text file with a .txt extension.

Regards,
STEVE555

**dibl** · Jun 16, 2007, 05:55 PM

Re: Beryl Issue

Hmmm -- well, the file size limit for an uploaded file is very small, even when the uploader isn't full. Is the text too much to paste directly into a post? If nvidia-settings is generating errors just when you try to run it, then that suggests problems with the driver installation, to me. Your xorg.conf file looks pretty good --- I'm not familiar with those last two options, "Render" and "Damage" -- what are they supposed to do?

**STEVE555** · Jun 16, 2007, 06:12 PM

Re: Beryl Issue

Hi dibl,
Here is the errors from nvidia-stteings from konsole(my drivers are nvidia-glx-new version 1.0-9755 from the Feisty repo's)

Code:

steve@mernivia:~$ nvidia-settings

ERROR: Cannot open display 'mernivia:0.0'.

ERROR: Unable to assign attribute DigitalVibrance specified on line 19 of configuration file '/home/steve/.nvidia-settings-rc' (no Display connection).

ERROR: Unable to assign attribute ImageSharpening specified on line 20 of configuration file '/home/steve/.nvidia-settings-rc' (no Display connection).

ERROR: Unable to assign attribute SyncToVBlank specified on line 21 of configuration file '/home/steve/.nvidia-settings-rc' (no Display connection).

ERROR: Unable to assign attribute AllowFlipping specified on line 22 of configuration file '/home/steve/.nvidia-settings-rc' (no Display connection).

ERROR: Unable to assign attribute LogAniso specified on line 23 of configuration file '/home/steve/.nvidia-settings-rc' (no Display connection).

ERROR: Unable to assign attribute FSAA specified on line 24 of configuration file '/home/steve/.nvidia-settings-rc' (no Display connection).

ERROR: Unable to assign attribute TextureSharpen specified on line 25 of configuration file '/home/steve/.nvidia-settings-rc' (no Display connection).

ERROR: Unable to assign attribute ForceGenericCpu specified on line 26 of configuration file '/home/steve/.nvidia-settings-rc' (no Display connection).

ERROR: Unable to assign attribute CursorShadow specified on line 27 of configuration file '/home/steve/.nvidia-settings-rc' (no Display connection).

ERROR: Unable to assign attribute CursorShadowXOffset specified on line 28 of configuration file '/home/steve/.nvidia-settings-rc' (no Display connection).

ERROR: Unable to assign attribute CursorShadowYOffset specified on line 29 of configuration file '/home/steve/.nvidia-settings-rc' (no Display connection).

ERROR: Unable to assign attribute CursorShadowAlpha specified on line 30 of configuration file '/home/steve/.nvidia-settings-rc' (no Display connection).

ERROR: Unable to assign attribute CursorShadowRed specified on line 31 of configuration file '/home/steve/.nvidia-settings-rc' (no Display connection).

ERROR: Unable to assign attribute CursorShadowGreen specified on line 32 of configuration file '/home/steve/.nvidia-settings-rc' (no Display connection).

ERROR: Unable to assign attribute CursorShadowBlue specified on line 33 of configuration file '/home/steve/.nvidia-settings-rc' (no Display connection).

ERROR: Unable to assign attribute FSAAAppControlled specified on line 34 of configuration file '/home/steve/.nvidia-settings-rc' (no Display connection).

ERROR: Unable to assign attribute LogAnisoAppControlled specified on line 35 of configuration file '/home/steve/.nvidia-settings-rc' (no Display connection).

ERROR: Unable to assign attribute RedBrightness specified on line 36 of configuration file '/home/steve/.nvidia-settings-rc' (no Display connection).

ERROR: Unable to assign attribute GreenBrightness specified on line 37 of configuration file '/home/steve/.nvidia-settings-rc' (no Display connection).

ERROR: Unable to assign attribute BlueBrightness specified on line 38 of configuration file '/home/steve/.nvidia-settings-rc' (no Display connection).

ERROR: Unable to assign attribute RedContrast specified on line 39 of configuration file '/home/steve/.nvidia-settings-rc' (no Display connection).

ERROR: Unable to assign attribute GreenContrast specified on line 40 of configuration file '/home/steve/.nvidia-settings-rc' (no Display connection).

ERROR: Unable to assign attribute BlueContrast specified on line 41 of configuration file '/home/steve/.nvidia-settings-rc' (no Display connection).

ERROR: Unable to assign attribute RedGamma specified on line 42 of configuration file '/home/steve/.nvidia-settings-rc' (no Display connection).

ERROR: Unable to assign attribute GreenGamma specified on line 43 of configuration file '/home/steve/.nvidia-settings-rc' (no Display connection).

ERROR: Unable to assign attribute BlueGamma specified on line 44 of configuration file '/home/steve/.nvidia-settings-rc' (no Display connection).

ERROR: Unable to assign attribute OpenGLImageSettings specified on line 45 of configuration file '/home/steve/.nvidia-settings-rc' (no Display connection).

ERROR: Unable to assign attribute XVideoTextureSyncToVBlank specified on line 46 of configuration file '/home/steve/.nvidia-settings-rc' (no Display connection).

ERROR: Unable to assign attribute XVideoBlitterSyncToVBlank specified on line 47 of configuration file '/home/steve/.nvidia-settings-rc' (no Display connection).

ERROR: Unable to assign attribute XVideoSyncToDisplay specified on line 48 of configuration file '/home/steve/.nvidia-settings-rc' (no Display connection).

steve@mernivia:~$

I am sorry it is so long,hence why I wanted to attach the errors in a text file.
Anyway,the nvidia-settings panel still shows up after the output is finished.

Regards,
STEVE555

**dibl** · Jun 16, 2007, 06:42 PM

Re: Beryl Issue

OK, Steve, here's approximately what you should be seeing in the .nvidia-settings-rc file:

Code:

#
# /home/don/.nvidia-settings-rc
#
# Configuration file for nvidia-settings - the NVIDIA X Server Settings utility
# Generated on Fri Jun 15 14:31:16 2007
#

# ConfigProperties:

RcFileLocale = en_US.UTF-8
ToolTips = Yes
DisplayStatusBar = Yes
SliderTextEntries = Yes
IncludeDisplayNameInConfigFile = No
ShowQuitDialog = Yes

# Attributes:

0/DigitalVibrance[CRT-1]=0
0/ImageSharpening[CRT-1]=0
0/SyncToVBlank=0
0/AllowFlipping=1
0/LogAniso=0
0/FSAA=0
0/TextureSharpen=0
0/ForceGenericCpu=0
0/CursorShadow=0
0/CursorShadowXOffset=4
0/CursorShadowYOffset=2
0/CursorShadowAlpha=64
0/CursorShadowRed=0
0/CursorShadowGreen=0
0/CursorShadowBlue=0
0/FSAAAppControlled=1
0/LogAnisoAppControlled=1
0/RedBrightness=0.000000
0/GreenBrightness=0.000000
0/BlueBrightness=0.000000
0/RedContrast=0.000000
0/GreenContrast=0.000000
0/BlueContrast=0.000000
0/RedGamma=1.000000
0/GreenGamma=1.000000
0/BlueGamma=1.000000
0/OpenGLImageSettings=1
0/XVideoTextureSyncToVBlank=1
0/XVideoBlitterSyncToVBlank=0
0/XVideoSyncToDisplay=2

I'm not enough of a guru to know exactly where or how this file comes to be -- I take it that it is written during installation or configuration of the Nvidia driver.

Since it's puking up such an error from "nvidia-settings", I'm going to speculate that your driver is not correctly installed, and suggest that you need to return to "go", and install the nvidia driver again. I don't know how you installed it -- the means by which you uninstall it are kinda dependent on how you did it. But I think you need to uninstall it completely -- maybe go back to a "VESA" display, and from there do a clean installation of the Nvidia driver, and then see if we can get nvidia-settings, nvidia-xconfig, and glx working from that point. Sorry it can't be better news ....

**SheeEttin** · Jun 16, 2007, 06:59 PM

Re: Beryl Issue

A bit off-topic, but I thought I might inform you that in place of posting, you might consider a pastebin-type service.

**STEVE555** · Jun 17, 2007, 06:43 AM

Re: Beryl Issue

Hi SheeEttin,
Thank you very much for the info,I've saved the site as a bookmark for future reference.
I installed my nvidia-glx-new drivers using Manage Packages (Adept Manager) from the system menu.
After I removed it,I rebooted and when the Kubuntu progress bar had finished,instead of the login screen,I got the kubuntu splash screen again,but no activity.Then the screen went blank for a few seconds and I got the dreaded blinking cursor at the top-left hand side of the screen

.

I then pressed left Crtl+Alt+F3 to get to the root prompt.After I logged in,I typed

Code:

sudo apt-get install nvidia-glx-new

after I gave my password,apt downloaded and installed the nvidia-glx-new driver again.I then ran:

Code:

sudo reboot

and Kubuntu rebooted.After it had re-booted,luckily the login screen presented itself again

and I was able to login normally.I ran nvidia-settings again to see what happens,but alas,I was getting the same error messages again.

I hope that helps.

Regards,
STEVE555

**dibl** · Jun 17, 2007, 06:48 AM

Re: Beryl Issue

Originally posted by STEVE555

luckily the login screen presented itself again

OK, right before the login screen came up, did you see the big green and black Nvidia splash screen?

Announcement

Beryl Issue

Beryl Issue

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment