You are not logged in.

Pages: 1 2

#1 2008-08-10 17:15:53

ralvez
Member
From: Canada
Registered: 2005-12-06
Posts: 1,718
Website

KDE 4.1 and visual effects [UNRESOLVED -- Closed --]

I have an Intel video card (Mobile GM965/GL960 Integrated Graphics Controller) which seems to run fine with i915.
After I installed KDE 4.1 it did not start any effects at all even when I had set the desktop configuration to show them.

Last night I did a small test and in my /etc/X11/xorg.conf I enabled the GLX module and then restarted but not joy ... however, when I disabled KDM and started X from the command line (with startx) I got full effects!!

I have tested with GDM and same thing. It seems that as soon as a desktop manager is added to the equation no visual effects are enabled.

Does anyone have any idea as to why this is ? Is this something  to do with KDE 4.1 or something with the way is is packaged in Arch? If we can say that the former is the reason I could submit a bug with the KDE developers (upstream) and see what happens.

R.

Last edited by ralvez (2008-08-30 17:59:19)

Offline

#2 2008-08-10 18:05:12

dienadel
Member
Registered: 2005-12-23
Posts: 179

Re: KDE 4.1 and visual effects [UNRESOLVED -- Closed --]

I haven't managed to make kwin effects work, nor kdm, nor startx, and i have the same graphics card :-(

Could you paste your xorg.conf?

Offline

#3 2008-08-10 18:21:58

ralvez
Member
From: Canada
Registered: 2005-12-06
Posts: 1,718
Website

Re: KDE 4.1 and visual effects [UNRESOLVED -- Closed --]

OK, this is what I did.
1. Install Intel graphics support (pacman -S xorg-video-drivers) <-- edit: should be pacman -S xf86-video-intel
2. In my /etc/X11/xorg.conf

# File generated by xorgconfig.

#
# Copyright 2004 The X.Org Foundation
#
# Permission is hereby granted, free of charge, to any person obtaining a
# copy of this software and associated documentation files (the "Software"),
# to deal in the Software without restriction, including without limitation
# the rights to use, copy, modify, merge, publish, distribute, sublicense,
# and/or sell copies of the Software, and to permit persons to whom the
# Software is furnished to do so, subject to the following conditions:
# 
# The above copyright notice and this permission notice shall be included in
# all copies or substantial portions of the Software.
# 
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.  IN NO EVENT SHALL
# The X.Org Foundation BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
# WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF
# OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
# SOFTWARE.
# 
# Except as contained in this notice, the name of The X.Org Foundation shall
# not be used in advertising or otherwise to promote the sale, use or other
# dealings in this Software without prior written authorization from
# The X.Org Foundation.
#

# **********************************************************************
# Refer to the xorg.conf(5) man page for details about the format of 
# this file.
# **********************************************************************

# **********************************************************************
# Module section -- this  section  is used to specify
# which dynamically loadable modules to load.
# **********************************************************************
#
Section "Module"

# This loads the DBE extension module.

    Load        "dbe"      # Double buffer extension

# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
    SubSection  "extmod"
      Option    "omit xfree86-dga"   # don't initialise the DGA extension
    EndSubSection

# This loads the font modules
#    Load        "type1"
    Load        "freetype"
#    Load        "xtt"

# This loads the GLX module
    Load       "glx"
# This loads the DRI module
#    Load       "dri"

EndSection

# **********************************************************************
# Files section.  This allows default font and rgb paths to be set
# **********************************************************************

Section "Files"

# The location of the RGB database.  Note, this is the name of the
# file minus the extension (like ".txt" or ".db").  There is normally
# no need to change the default.

#    RgbPath    "/usr/share/X11/rgb"

# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)
# 
# 

    FontPath   "/usr/share/fonts/misc"
    FontPath   "/usr/share/fonts/100dpi:unscaled"
    FontPath   "/usr/share/fonts/75dpi:unscaled"
    FontPath   "/usr/share/fonts/TTF"
    FontPath   "/usr/share/fonts/Type1"
#    FontPath   "/usr/lib/X11/fonts/local/"
#    FontPath   "/usr/lib/X11/fonts/misc/"
#    FontPath   "/usr/lib/X11/fonts/75dpi/:unscaled"
#    FontPath   "/usr/lib/X11/fonts/100dpi/:unscaled"
#    FontPath   "/usr/lib/X11/fonts/Speedo/"
#    FontPath   "/usr/lib/X11/fonts/Type1/"
#    FontPath   "/usr/lib/X11/fonts/TrueType/"
#    FontPath   "/usr/lib/X11/fonts/freefont/"
#    FontPath   "/usr/lib/X11/fonts/75dpi/"
#    FontPath   "/usr/lib/X11/fonts/100dpi/"

# The module search path.  The default path is shown here.

#    ModulePath "/usr/lib/modules"

EndSection

# **********************************************************************
# Server flags section.
# **********************************************************************

Section "ServerFlags"

# Uncomment this to cause a core dump at the spot where a signal is 
# received.  This may leave the console in an unusable state, but may
# provide a better stack trace in the core dump to aid in debugging

#    Option "NoTrapSignals"

# Uncomment this to disable the <Ctrl><Alt><Fn> VT switch sequence
# (where n is 1 through 12).  This allows clients to receive these key
# events.

#    Option "DontVTSwitch"

# Uncomment this to disable the <Ctrl><Alt><BS> server abort sequence
# This allows clients to receive this key event.

#    Option "DontZap"

# Uncomment this to disable the <Ctrl><Alt><KP_+>/<KP_-> mode switching
# sequences.  This allows clients to receive these key events.

#    Option "Dont Zoom"

# Uncomment this to disable tuning with the xvidtune client. With
# it the client can still run and fetch card and monitor attributes,
# but it will not be allowed to change them. If it tries it will
# receive a protocol error.

#    Option "DisableVidModeExtension"

# Uncomment this to enable the use of a non-local xvidtune client. 

#    Option "AllowNonLocalXvidtune"

# Uncomment this to disable dynamically modifying the input device
# (mouse and keyboard) settings. 

#    Option "DisableModInDev"

# Uncomment this to enable the use of a non-local client to
# change the keyboard or mouse settings (currently only xset).

#    Option "AllowNonLocalModInDev"

EndSection

# **********************************************************************
# Input devices
# **********************************************************************

# **********************************************************************
# Core keyboard's InputDevice section
# **********************************************************************

Section "InputDevice"

    Identifier    "Keyboard1"
    Driver    "kbd"

    Option "AutoRepeat" "500 30"

# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
#    Option    "Xleds"      "1 2 3"

#    Option "LeftAlt"     "Meta"
#    Option "RightAlt"    "ModeShift"

# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults).  For example, for a non-U.S.
# keyboard, you will probably want to use:
#    Option "XkbModel"    "pc105"
# If you have a US Microsoft Natural keyboard, you can use:
#    Option "XkbModel"    "microsoft"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
#    Option "XkbLayout"   "de"
# or:
#    Option "XkbLayout"   "de"
#    Option "XkbVariant"  "nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
#    Option "XkbOptions"  "ctrl:swapcaps"

# These are the default XKB settings for Xorg
#    Option "XkbRules"    "xorg"
#    Option "XkbModel"    "pc105"
#    Option "XkbLayout"   "us"
#    Option "XkbVariant"  ""
#    Option "XkbOptions"  ""

#    Option "XkbDisable"

    Option "XkbRules"    "xorg"
    Option "XkbModel"    "pc105"
    Option "XkbLayout"    "us"

EndSection


# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************

Section "InputDevice"

# Identifier and driver

    Identifier    "Mouse1"
    Driver    "mouse"
    Option "Protocol"    "Auto"    # Auto detect
    Option "Device"      "/dev/input/mice"

# Mouse-speed setting for PS/2 mouse.

#    Option "Resolution"    "256"

# Baudrate and SampleRate are only for some Logitech mice. In
# almost every case these lines should be omitted.

#    Option "BaudRate"    "9600"
#    Option "SampleRate"    "150"

# Mouse wheel mapping.  Default is to map vertical wheel to buttons 4 & 5,
# horizontal wheel to buttons 6 & 7.   Change if your mouse has more than
# 3 buttons and you need to map the wheel to different button ids to avoid
# conflicts.

    Option "ZAxisMapping"   "4 5 6 7"

# Emulate3Buttons is an option for 2-button mice
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)

    Option "Emulate3Buttons"
#    Option "Emulate3Timeout"    "50"

# ChordMiddle is an option for some 3-button Logitech mice

#    Option "ChordMiddle"

EndSection


# **********************************************************************
# Other input device sections 
# this is optional and is required only if you
# are using extended input devices.  This is for example only.  Refer
# to the xorg.conf man page for a description of the options.
# **********************************************************************
#
# Section "InputDevice" 
#    Identifier  "Mouse2"
#    Driver      "mouse"
#    Option      "Protocol"      "MouseMan"
#    Option      "Device"        "/dev/mouse2"
# EndSection
#
# Section "InputDevice"
#    Identifier "spaceball"
#    Driver     "magellan"
#    Option     "Device"        "/dev/cua0"
# EndSection
#
# Section "InputDevice"
#    Identifier "spaceball2"
#    Driver     "spaceorb"
#    Option     "Device"        "/dev/cua0"
# EndSection
#
# Section "InputDevice"
#    Identifier "touchscreen0"
#    Driver     "microtouch"
#    Option     "Device"        "/dev/ttyS0"
#    Option     "MinX"          "1412"
#    Option     "MaxX"          "15184"
#    Option     "MinY"          "15372"
#    Option     "MaxY"          "1230"
#    Option     "ScreenNumber"  "0"
#    Option     "ReportingMode" "Scaled"
#    Option     "ButtonNumber"  "1"
#    Option     "SendCoreEvents"
# EndSection
#
# Section "InputDevice"
#    Identifier "touchscreen1"
#    Driver     "elo2300"
#    Option     "Device"        "/dev/ttyS0"
#    Option     "MinX"          "231"
#    Option     "MaxX"          "3868"
#    Option     "MinY"          "3858"
#    Option     "MaxY"          "272"
#    Option     "ScreenNumber"  "0"
#    Option     "ReportingMode" "Scaled"
#    Option     "ButtonThreshold"       "17"
#    Option     "ButtonNumber"  "1"
#    Option     "SendCoreEvents"
# EndSection

# **********************************************************************
# Monitor section
# **********************************************************************

# Any number of monitor sections may be present

Section "Monitor"

    Identifier  "Acer LCD"

# HorizSync is in kHz unless units are specified.
# HorizSync may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY.  REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

    HorizSync   75

#    HorizSync    30-64         # multisync
#    HorizSync    31.5, 35.2    # multiple fixed sync frequencies
#    HorizSync    15-25, 30-50  # multiple ranges of sync frequencies

# VertRefresh is in Hz unless units are specified.
# VertRefresh may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY.  REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

    VertRefresh 60

EndSection


# **********************************************************************
# Graphics device section
# **********************************************************************

# Any number of graphics device sections may be present

# Standard VGA Device:

Section "Device"
    Identifier    "Standard VGA"
    VendorName    "Unknown"
    BoardName    "Unknown"

# The chipset line is optional in most cases.  It can be used to override
# the driver's chipset detection, and should not normally be specified.

#    Chipset    "generic"

# The Driver line must be present.  When using run-time loadable driver
# modules, this line instructs the server to load the specified driver
# module.  Even when not using loadable driver modules, this line
# indicates which driver should interpret the information in this section.

    Driver     "vga"
# The BusID line is used to specify which of possibly multiple devices
# this section is intended for.  When this line isn't present, a device
# section can only match up with the primary video device.  For PCI
# devices a line like the following could be used.  This line should not
# normally be included unless there is more than one video device
# intalled.

#    BusID      "PCI:0:10:0"

#    VideoRam    256

#    Clocks    25.2 28.3

EndSection

# Device configured by xorgconfig:

Section "Device"
    Identifier  "Intel 810"
    Driver      "intel"
    #VideoRam    512
    # Insert Clocks lines here if appropriate
EndSection


# **********************************************************************
# Screen sections
# **********************************************************************

# Any number of screen sections may be present.  Each describes
# the configuration of a single screen.  A single specific screen section
# may be specified from the X server command line with the "-screen"
# option.
Section "Screen"
    Identifier  "Screen 1"
    Device      "Intel 810"
    Monitor     "Acer LCD"
    DefaultDepth 24

    Subsection "Display"
        Depth       8
        Modes       "1440x900" "1024x768"
        ViewPort    0 0
    EndSubsection
    Subsection "Display"
        Depth       16
        Modes       "1440x900" "1024x768"
        ViewPort    0 0
    EndSubsection
    Subsection "Display"
        Depth       24
        Modes       "1440x900" "1024x768"
        ViewPort    0 0
    EndSubsection
EndSection

# **********************************************************************
# ServerLayout sections.
# **********************************************************************

# Any number of ServerLayout sections may be present.  Each describes
# the way multiple screens are organised.  A specific ServerLayout
# section may be specified from the X server command line with the
# "-layout" option.  In the absence of this, the first section is used.
# When now ServerLayout section is present, the first Screen section
# is used alone.

Section "ServerLayout"

# The Identifier line must be present
    Identifier  "Simple Layout"

# Each Screen line specifies a Screen section name, and optionally
# the relative position of other screens.  The four names after
# primary screen name are the screens to the top, bottom, left and right
# of the primary screen.  In this example, screen 2 is located to the
# right of screen 1.

    Screen "Screen 1"

# Each InputDevice line specifies an InputDevice section name and
# optionally some options to specify the way the device is to be
# used.  Those options include "CorePointer", "CoreKeyboard" and
# "SendCoreEvents".

    InputDevice "Mouse1" "CorePointer"
    InputDevice "Keyboard1" "CoreKeyboard"

EndSection

# Section "DRI"
#    Mode 0666
# EndSection

Section "Extensions"
  Option "Composite" "Enable"
EndSection

3. It started to work for me after I did :
a) # This loads the GLX module
    Load       "glx"

b) Section "Extensions"
  Option "Composite" "Enable"
EndSection

c) remove "kdm" from my /etc/rc.conf DAEMONS line

d) added "exec startkde" to my .xinitrc

To me the  mystery is "why only works from the CLI with 'startx' because for all intense purposes  that's what the desktop manager does ... or is there something  else going in in the background when we run KDM or GDM for that matter?

R.

p.s : One more detail.
Make sure you go into System Settings > Desktop > Advanced Options and use Compositing type "XRender" because the OpenGL tends to fail.

Last edited by ralvez (2008-08-10 19:46:35)

Offline

#4 2008-08-10 19:04:28

whargoul
Member
From: Odense, Denmark
Registered: 2005-04-04
Posts: 546

Re: KDE 4.1 and visual effects [UNRESOLVED -- Closed --]

ralvez wrote:

OK, this is what I did.
1. Install Intel graphics support (pacman -S xorg-video-drivers)

Woah! You just need to install xorg-video-intel. The thing you suggest is installing the whole group - there's no need for that.

Oh and back to topic. Do you have this:

Section "ServerLayout"
Option "AIGLX" "true"
EndSection

in xorg.conf?

Arch - It's something refreshing

Offline

#5 2008-08-10 19:18:10

ralvez
Member
From: Canada
Registered: 2005-12-06
Posts: 1,718
Website

Re: KDE 4.1 and visual effects [UNRESOLVED -- Closed --]

@whargoul,

Sorry ... my mistake xf86-video-intel is correct.

As per the Serction AIGLX as you can see in my xorg.conf I do not have that.

R.

Last edited by ralvez (2008-08-10 19:47:27)

Offline

#6 2008-08-10 19:54:12

kishd
Member
Registered: 2006-06-14
Posts: 401

Re: KDE 4.1 and visual effects [UNRESOLVED -- Closed --]

Don't know if this is a problem or not but your xorg.conf file has two device sections one loading the vga driver and another loading the intel driver. Perhaps removing the section that loads vga driver might help.

---for there is nothing either good or bad, but only thinking makes it so....
Hamlet, W Shakespeare

Offline

#7 2008-08-10 20:03:01

ralvez
Member
From: Canada
Registered: 2005-12-06
Posts: 1,718
Website

Re: KDE 4.1 and visual effects [UNRESOLVED -- Closed --]

kishd wrote:

Don't know if this is a problem or not but your xorg.conf file has two device sections one loading the vga driver and another loading the intel driver. Perhaps removing the section that loads vga driver might help.

I do not think it is a problem, I have another box with a similar xorg.conf file, but I'll remove it and will report on any improvements if any.

Thanks.

R,

Offline

#8 2008-08-11 03:01:50

QuimaxW
Member
From: Papua New Guinea
Registered: 2006-12-03
Posts: 228
Website

Re: KDE 4.1 and visual effects [UNRESOLVED -- Closed --]

Just a thought...with my notebook (also i915 chip), I havn't had luck with the xf86-video-intel driver. I don't recal specifically what it was (been a while).

Try the xf86-video-i810 and see what happens.

Last edited by QuimaxW (2008-08-11 03:02:18)

"He is no fool who gives what he cannot keep to gain that which he cannot lose." -Jim Elliot

Offline

#9 2008-08-11 03:14:43

ralvez
Member
From: Canada
Registered: 2005-12-06
Posts: 1,718
Website

Re: KDE 4.1 and visual effects [UNRESOLVED -- Closed --]

@kishd,

As promised I'm reporting back on what I found. The number of sections defined is not a problem.
This is what xorgconfig writes when you create a new file : # Any number of graphics device sections may be present

R.

Offline

#10 2008-08-11 03:15:38

ralvez
Member
From: Canada
Registered: 2005-12-06
Posts: 1,718
Website

Re: KDE 4.1 and visual effects [UNRESOLVED -- Closed --]

QuimaxW wrote:

Just a thought...with my notebook (also i915 chip), I havn't had luck with the xf86-video-intel driver. I don't recal specifically what it was (been a while).

Try the xf86-video-i810 and see what happens.

I'll give it a try and post on the results.

Thanks !!

R.

Offline

#11 2008-08-12 16:13:20

nirvanix
Member
From: Saskatoon
Registered: 2005-01-31
Posts: 193

Re: KDE 4.1 and visual effects [UNRESOLVED -- Closed --]

I have the same problem with an Nvidia 6150 card. It is a problem with KDM or someone else reported that knotify was the culprit.

I don't think you need:

Section "ServerLayout"
Option "AIGLX" "true"
EndSection

unless you are using compiz??? I had everything working fine without this,until I did the latest system upgrade, then kdm hung when trying to start kde.

I've got a lovely bunch of coconuts...

Offline

#12 2008-08-13 00:01:48

ralvez
Member
From: Canada
Registered: 2005-12-06
Posts: 1,718
Website

Re: KDE 4.1 and visual effects [UNRESOLVED -- Closed --]

nirvanix wrote:

I have the same problem with an Nvidia 6150 card. It is a problem with KDM or someone else reported that knotify was the culprit.

I don't think you need:

Section "ServerLayout"
Option "AIGLX" "true"
EndSection

unless you are using compiz??? I had everything working fine without this,until I did the latest system upgrade, then kdm hung when trying to start kde.

You are correct, adding the section does nothing to solve the problem.
I have one of my systems working fine without it. I'm certain the problem is not just KDE but somewhere along the line may also involve the X server. The reason I think so is that if I start X manually and set KDE to use xRender I get some effects to work BUT if I use KDM (in /etc/rc.conf) then the very same settings do nothing. ?? roll

R.

Offline

#13 2008-08-30 17:29:21

brauliobo
Member
Registered: 2008-07-29
Posts: 15

Re: KDE 4.1 and visual effects [UNRESOLVED -- Closed --]

stopped kdm and started X with startx and it didn't help

Offline

#14 2008-08-30 17:58:25

ralvez
Member
From: Canada
Registered: 2005-12-06
Posts: 1,718
Website

Re: KDE 4.1 and visual effects [UNRESOLVED -- Closed --]

Well ... I got so tired of dealing with KDE4 that I moved to e17. It's fantastic.
Even when e17 is considered to be alpha, it is FAR BETTER than KDE 4.1 as a release candidate. I think it is a shame Arch decided to set KDE 4.1RC as its "default" instead of the KDE 3.5x series which is absolutely stable. While I understand the thinking behind the move it does not make it less of a bad choice.

e17 performs faster and it is more stable than KDE4 for sure! The whole thing with KDE has been a real bummer for me sad because it was my favourite DE for the past 8 years... I think I will stay away from KDE 4.x series until it reaches at least a 4.2 status

Offline

#15 2008-08-30 18:02:36

lucke
Member
From: Poland
Registered: 2004-11-30
Posts: 4,018

Re: KDE 4.1 and visual effects [UNRESOLVED -- Closed --]

Well, you still can use KDE 3.5.

Offline

#16 2008-08-30 18:14:50

brauliobo
Member
Registered: 2008-07-29
Posts: 15

Re: KDE 4.1 and visual effects [UNRESOLVED -- Closed --]

fix at http://bugs.archlinux.org/task/11351

Offline

#17 2008-08-30 18:19:01

brauliobo
Member
Registered: 2008-07-29
Posts: 15

Re: KDE 4.1 and visual effects [UNRESOLVED -- Closed --]

ralvez wrote:

Well ... I got so tired of dealing with KDE4 that I moved to e17. It's fantastic.
Even when e17 is considered to be alpha, it is FAR BETTER than KDE 4.1 as a release candidate. I think it is a shame Arch decided to set KDE 4.1RC as its "default" instead of the KDE 3.5x series which is absolutely stable. While I understand the thinking behind the move it does not make it less of a bad choice.

e17 performs faster and it is more stable than KDE4 for sure! The whole thing with KDE has been a real bummer for me sad because it was my favourite DE for the past 8 years... I think I will stay away from KDE 4.x series until it reaches at least a 4.2 status

hey man, it's not a KDE problem. it works on others distributions. it is an arch's xorg-server problem

Offline

#18 2008-08-30 21:14:25

ralvez
Member
From: Canada
Registered: 2005-12-06
Posts: 1,718
Website

Re: KDE 4.1 and visual effects [UNRESOLVED -- Closed --]

brauliobo wrote:

This is the report on the "fix"

although I could fix the problem, KDE with desktop effects is very slow (e.g. firefox scrolling)

So... half a fix is not a fix wink

R.

Offline

#19 2008-08-30 21:15:19

ralvez
Member
From: Canada
Registered: 2005-12-06
Posts: 1,718
Website

Re: KDE 4.1 and visual effects [UNRESOLVED -- Closed --]

lucke wrote:

Well, you still can use KDE 3.5.

Yes ... I could install KDEmod which I do not like.

R.

Offline

#20 2008-08-30 21:19:57

ralvez
Member
From: Canada
Registered: 2005-12-06
Posts: 1,718
Website

Re: KDE 4.1 and visual effects [UNRESOLVED -- Closed --]

brauliobo wrote:

hey man, it's not a KDE problem. it works on others distributions. it is an arch's xorg-server problem

I can appreciate your point but Arch IS my all time favourite distribution and I'm not about to move away just because of some developer's bad choice... in time it will be fixed (I hope wink ) then I'll go back to KDE.

R.

Last edited by ralvez (2008-08-30 21:20:25)

Offline

#21 2008-08-30 23:41:50

luuuciano
Member
Registered: 2007-01-27
Posts: 311

Re: KDE 4.1 and visual effects [UNRESOLVED -- Closed --]

ralvez wrote:
brauliobo wrote:

hey man, it's not a KDE problem. it works on others distributions. it is an arch's xorg-server problem

I can appreciate your point but Arch IS my all time favourite distribution and I'm not about to move away just because of some developer's bad choice... in time it will be fixed (I hope wink ) then I'll go back to KDE.

R.

why do you think that brauliobo recommends you to switch to another distro?

IMO he is just pointing where is the problem... he made a report of it, waiting and looking how to solve it....

I arch, you arch, he arch, she arch, we arch, they arch...

Offline

#22 2008-08-30 23:49:47

brauliobo
Member
Registered: 2008-07-29
Posts: 15

Re: KDE 4.1 and visual effects [UNRESOLVED -- Closed --]

luuuciano, i almost did feed the troll, but I've came back to my self-control smile

Offline

#23 2008-08-30 23:57:46

ralvez
Member
From: Canada
Registered: 2005-12-06
Posts: 1,718
Website

Re: KDE 4.1 and visual effects [UNRESOLVED -- Closed --]

luuuciano,

Yes, you may be correct here, he is not necessarily saying to "go looking for another distro" but it suggests that if I was to use another distro (" ... it works on others distributions. it is an arch's xorg-server problem" ) I would not have the problem since it seems to be only an Arch problem.
His point is valid but I just love my Arch box cool

R.

Offline

#24 2008-08-31 00:00:48

ralvez
Member
From: Canada
Registered: 2005-12-06
Posts: 1,718
Website

Re: KDE 4.1 and visual effects [UNRESOLVED -- Closed --]

brauliobo,

I hope I did not offend you with my comment. As I said, I appreciate your comment and your point is well taken ... I also understand it was posted in the best spirit of helping and I thank you for trying to help.

R.

Offline

#25 2008-08-31 13:56:36

brauliobo
Member
Registered: 2008-07-29
Posts: 15

Re: KDE 4.1 and visual effects [UNRESOLVED -- Closed --]

that's ok ralvez, I like Arch a lot too.
But don't take that love too serious, I did that with Gentoo, and you know... tongue
it just doesn't worth the value, they are just machines smile

see ya

Offline

Pages: 1 2

Board footer

Powered by FluxBB