[Kind of Solved] Screen edges in Compiz?

I am using XFCE+Compiz.
When I right-click or scroll on any edge of the screen, nothing happens. I know that this is because of the screen edges set by Compiz.
However, when I installed Compiz in Ubuntu this summer, it didn't have this behavior. What does Ubuntu do to turn off the edges? Is there some compile flag or something?
Last edited by pogeymanz (2009-09-10 22:43:45)

Well, that sucks... I don't know why it doesn't work. I don't think I have anything bound to most edges. I have expo bound at top-left corner and scale bound at top-right.
Ah, okay. It's the Desktop Wall plugin. The edge flipping when you drag a window across veiwports is what was messing it up. So, I at least turned of the top and bottom edges, but I need the left and right to drag windows. It's a lot better now, even if not totally perfect.
Last edited by pogeymanz (2009-09-10 22:41:22)

Similar Messages

How to solve screen resolution in bdc

hi experts,
please tell me how to solve screen resolution in bdc.
regards.
subhasis

Hi,
<b>Pls check other posts in SDN before posting ur thread..there is same thread related to this on this forum on same day.</b>
Screen resolution means different in the screen display depending on ur system screen resolution.
suppose ur system resolution is diff and another's system is different then like in Tcode VA01, there will be 3 lineitems and another there will be 5 lineitems ,
so while doing recording and page down that will bw diff so there will be some problem
So u have to set the screen resolution as default by using CTU parameters..
write this code then
f_option-updmode = 'S'.
f_option-defsize = 'X'.* f
_option-dismode = 'N'.
*call transaction 'VA01' using bdcdata options from f_option messages into bdcerror.
Hope it helps.
Regards,
Sonika

What kind of LCD screen is the MBP display?

I have a 2007 Santa Rosa Macbook Pro. I'm curious what kind of LCD screen the display is. I know TN is the worst, and something like ISPS is better...

The screens in the MBP are provided by one of three manufacturers: Samsung, LG, and Chimei. Although there is a host of debate about which is the best between Samsung and LG, everyone agrees that Chimei screens are the worst.
The Samsung panels tend to be more "vivid" compared to the LG screens (although you'll only notice this difference if you compare the two side by side.) The LG screens tend to be less susceptible to "yellowing." If you get a good, defect-free Samsung panel you hit the jackpot. It's the best of the three.
To find out which one you have, go to System Preferences > Displays > Color > Open Color Profile and scroll down to line 13. Post the code next to "Manufacturer Code." (It should be something like 0000009c68.) Bring it back here and someone will be able to tell you what screen you have.
Of course, unrelated to the screen, the Santa Rosa MacBook Pro was the first to introduce LED backlighting.

JPopupMenu ignores setOpaque(false) near screen edges

Dear group
I try to paint a custom JPopupMenu with transparency, but this is ignored when the popup is opened so it overlaps near screen edges (bottom and right side). This is also the case if the popup overlaps the Microsoft Windows toolbar at the bottom.
I may be able to emulate JPopupMenus using custom components in a JLayeredPane, but can anyone explain the above behaviour?
Thanks and Best Regards,
Aksel, Denmark
Environment: j2sdk-se 1.6.0_10 and windows xp
Example:
import java.awt.Color;
import java.awt.Dimension;
import java.awt.Font;
import java.awt.Rectangle;
import java.awt.Toolkit;
import java.awt.event.MouseAdapter;
import java.awt.event.MouseEvent;
import javax.swing.JFrame;
import javax.swing.JLabel;
import javax.swing.JPopupMenu;
public class TransparencyPopupNearBorderTest {
public static void main(String[] args) {
final JFrame frame = new JFrame();
frame.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
frame.setLocationRelativeTo(null);
Dimension screenSize = Toolkit.getDefaultToolkit().getScreenSize();
frame.setBounds(new Rectangle(screenSize));
frame.setUndecorated(true);
frame.setPreferredSize(screenSize);
frame.addMouseListener(new MouseAdapter() {
@Override
public void mouseReleased(MouseEvent e) {
JPopupMenu popup = new JPopupMenu();
popup.setOpaque(false);
JLabel label = new JLabel("TRANSPARENT");
label.setFont(new Font("Helvetica", Font.PLAIN, 42));
popup.add(label);
popup.setLightWeightPopupEnabled(false);
popup.show(frame, e.getX(), e.getY());
frame.getContentPane().setBackground(Color.BLUE);
frame.pack();
frame.setVisible(true);
}

Don't forget to use the Code Formatting Tags so the posted code retains its original formatting. That is done by selecting the code and then clicking on the "Code" button above the question input area.
I don't know if transparency painting has changed in 1.6.0_10. Prior to that I believe transparency can only be achieved in lightweight components (ie. Swing does all the painting). JFrame, JWindow and JDialog are not lightweight because they use OS components.
In the case of a popup, it is lightweight when entirely contained within its parent frame. But a lightweight popup can not be painted outside the bounds of the frame so a JWindow (I believe) is used as the popup, which can't be transparent.

[solved]screen borders and full sized window emerald compiz

hellos archers! i'm using XFCE and i have i little issue, when i maximize a windows in the bottom left and right sides the window borders disappear, (il also make hard to see the scroll bar) is there a way to set that when i maximize a window the borders does stay in the screen?
Last edited by kandros (2011-10-06 22:29:14)

alphaniner wrote:In Settings -> Window Manager Tweaks -> Accessibility tab there's an option 'Hide frame of windows when maximized'. Uncheck it.
thank you but i use compiz as window manager instead of xfwm4
EDIT: because of your tip i finally remember that there is an option like this in emerald settings... shame on me that i didnt check it
Last edited by kandros (2011-10-06 22:27:49)

[kinda solved] screen hardstatus: right align problem...

hey guys, previously i was using an old monitor at 1024x768 & screen's hardstatus was working fine with that setup. but some days ago i got a new monitor & now at a resolution of 1920x1080, the stuff that is supposed to be at the right most side has got some problem & is appearing abt 200-300px (i guess) before. i have googled it but found nothing.
here's a shot
http://omploader.org/vNWducg
& here's my screenrc
# Basic Settings {{{
nethack on # Fun error messages
deflogin off # All screens are considered logins
autodetach on # Detach on HUP instead of kill
startup_message off # Don't be annoying
vbell off # Don't be annoying
defshell -$SHELL # The dash makes it a login shell
defscrollback 10000 # Remember a lot
nonblock on # Block input from hung applications
defutf8 on # Always use utf8
defflow off # Turn off flow-control
msgwait 5 # Display msgs for N seconds
altscreen on # Enable alternate screen support
defbce on # Erase background with current background color
bell_msg "" # For urgency hints
setenv LC_CTYPE en_US.UTF-8
term rxvt-256color
# Define terminal capabilities {{{
termcapinfo xterm-256color 'Co#256:AB=\E[48;5;%dm:AF=\E[38;5;%dm'
termcapinfo rxvt-256color 'Co#256:AB=\E[48;5;%dm:AF=\E[38;5;%dm'
backtick 1 1800 1800 bday
backtick 2 1800 1800 cat ${HOME}/.weather
sorendition '= dY'
hardstatus alwayslastline '%{= M}%H%{W} | %{= B}%l%{W} | %{G}%1`%{W} | %{C}%2` %= %{= w}%-w%{+b r}%n*%t%{-b r}%{w}%+w'
# Banish screen 0, it sucks {{{
bind c screen 1
bind ^c screen 1
bind 0 select 10
# find the nearest shell
bind s select zsh
screen -t torrents 1 rtorrent
screen -t zsh 2
# Keybinds {{{
# Be lazy and use Fx keys for screen switching
#bindkey -k k1 select 1
#bindkey -k k2 select 2
#bindkey -k k3 select 3
#bindkey -k k4 select 4
#bindkey -k k5 select 5
#bindkey -k k6 select 6
#bindkey -k k7 select 7
#bindkey -k k8 select 8
# Use F11 as escape (for caps-lock mapped to F13)
bindkey -k F1 command
# vim:foldlevel=0
Last edited by vik_k (2010-09-11 09:47:00)

sorry -- I dont have a solution to your problem.
do you know howto get screen to send a command to the bash shell its displaying?
paste seems to do what I want,... if get date command in buffer, C-A ]
will send date, and bash runs date.
but how can I that to loop to automatically simulate activity to prevent ssh timeouts and disconnects

Iphone 6 plus screen edges colorization

Hello community
My ip6 plus has colorization around the edges of the screen in portrait mode. (As the phone is standing). It happens in all the apps I open.
If I don't open an app, i have a solid looking screen.
The colors I see are yellow, red, green, blue and just along the edges.
I am asking if anyone else is having this issue as my last iPhone 5 never had this.
Should I replace it with Apple.
Thank you

Hi there ankenymartialarts,
Welcome to Apple Support Communities.
The article linked below provides troubleshooting suggestions that can help you solve the discolored display issue with your iPhone 6 Plus.
Get help with the screen on your iPhone, iPad, or iPod touch - Apple Support
Ciao,
-Jason

[Solved] Screen blanks out after quitting X

Hello everyone.
I don't use any login manager such as GDM or Slim, I just start X from the terminal when I need it. However, after installing Arch the last time (new hdd), every time I exit X (XFCE 4 is my window manager) the screen blanks out. I know the system is still responsive, because if I type startx or reboot, it works. Calling startx wakes the monitor again. However, I don't need X all the time, sometimes I prefer not to use it.
I haven't dealt with this before and searching for a solution didn't help - nvidia users used to have this issue until a particular driver update.
However, I have an ATI card (HD 5750) and I use the xf86-video-ati driver.
Appending vga=773 to kernel options changes the resolution (of my ttys) but it doesn't solve the issue.
I'm kind of clueless about how to proceed, so any hints and tips would be welcome.
Thanks
Last edited by slapo (2010-05-02 09:50:51)

karol wrote:
I'm not an ATI guru but I hope you're not stuck w/ vesa :-) Surely there must be some other driver you can try.
Edit: http://bbs.archlinux.org/viewtopic.php?id=57084&p=72
It's a long thread, but be sure to read it all carefully <joking>
Thanks, I missed that repo
The catalyst driver doesn't have the issue, so as far as it works, the issue is resolved.

[SOLVED] Screen+wyrd

Hey.
I recently found a great app for my calendar, remind. I also found a curses based frontend for it, wyrd.
I want to run it in screen on my server, but my problem is that wyrd doesn't look the same when opened locally and when opened in screen. You can see the minor differences on the screenshot (local left, screen right). The differences actually limit themselves to the green underline in the top and the gray day splitters in the main window. It's the day splitters I miss the most and I think the problem is screen or terminal related - correct me if I'm wrong.
Can someone please explain this to me and can I solve it?
Last edited by atc (2008-08-29 18:16:39)

byte wrote:Compare the output of 'echo $TERM' in a normal terminal and in screen.
Yipee! Your clue did it for me. The output was "rxvt-256color" locally and "screen" in screen. Adding "term rxvt-256color" solved the problem.
This is great. I had all kinds of workarounds figured out, none giving me the right output. I then resorted to not running my calendar on my server and instead sync the .reminders file. Luckily I'm done with that hazzle now.
Thanks a lot guys.

Halos in my iphone screen edges

I Have tow halos appear in the top of my iphone 5s screen in the edges (right and left)
i did buy from USA in Nov 2013 but i leave in Egypt
knowing that i'm using the original accessories with NO jallpreack
waiting your support

Hi, Thanks Metalace.
I didn't put a magnet on it.
I turning it off, and i let fully drining the battery already.
I been seaching all aroud internet,... and i did not see a picture of an iphone with the same spots like mine.
-Something is wrong here.- (maybe an internal microchip, the screen, the sun)
Someone who forget his iphone under the sun found it 4 hours later with some kind of spots on the screen?
Many thanks

[SOLVED] AMD Catalyst + Xinerama + Compiz

Compiz + xf86-video-ati = works
Compiz + AMD Catalyst = works
AMD Catalyst + Xinerama = works
all three, no so good.
I believe the issue is related to this:
$ compiz-check
Gathering information about your system...
Distribution: Arch Linux
Desktop environment: Xfce
Graphics chip: Advanced Micro Devices [AMD] nee ATI Barts PRO [Radeon HD 6800 Series]
Driver in use: fglrx
Rendering method: None
Checking if it's possible to run Compiz on your system... [SKIP]
Checking for hardware/setup problems... [SKIP]
At least one check had to be skipped:
Error: No rendering method in use (AIGLX, Xgl or Nvidia)
Any idea how I set a rendering method? I did some research with not much luck.
All the other tests pass:
$ fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: Advanced Micro Devices, Inc.
OpenGL renderer string: AMD Radeon HD 6800 Series
OpenGL version string: 4.2.11903 Compatibility Profile Context
02:48:57 Mon Oct 22 crrobi01 ~/Desktop
$ lsmod | grep fglrx
fglrx 4606694 143
amd_iommu_v2 7367 1 fglrx
button 4662 1 fglrx
02:49:11 Mon Oct 22 crrobi01 ~/Desktop
$ glxinfo | grep direct
direct rendering: Yes
GL_AMD_multi_draw_indirect, GL_AMD_name_gen_delete,
GL_ARB_draw_indirect, GL_ARB_draw_instanced,
GL_EXT_copy_buffer, GL_EXT_copy_texture, GL_EXT_direct_state_access,
I've already enabled indirect rendering and generated a xorg.conf via
aticonfig --initial=dual-head --screen-layout=left
Of course after creating the xconf I had to use CCC to switch to xinerama. Is xinerama the only way for me to have a single desktop which spans both my monitors (while using the propriety ATI drivers of course)?
After creating xorg.conf I edited it to include
"Section "Extensions"
Option "Composite" "Enable"
EndSection
and
Section "ServerLayout"
Option "AIGLX" "True"
EndSection
and I restarted X.
Solved:
gksu amdcccle
- Disable Xinerama
- Display Manager > Multi-Display > select "Multi-display desktop with display(s) 2"
- Reboot
Last edited by beardedlinuxgeek (2012-10-22 07:18:52)

From AMD ATI Control Center I have set GPU to intel in order to save battery life and after restarting arch linux, now the error messages below have disappeared.
Only remaining the warning messages but if they are not harmful, then no problem
libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: i965
libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast

[Solved] Screen goes black when I run "xrandr" with displayport connec

I am running Arch on a Dell Latitude E6500 with Xorg, nouveau, and Gnome 3. The graphics chipset is identified by lspci as "01:00.0 VGA compatible controller: NVIDIA Corporation G98M [Quadro NVS 160M] (rev a1)". So far, everything has gone swimmingly with the integrated monitor. Today, I tried to connect an external monitor via DisplayPort. I initially connected the monitor with the system booted and logged in graphically. The external monitor did not receive a signal, so I ran xrandr in an xterm to see if it was being detected. As soon as I ran the command, the laptop screen went black. On a reboot (this time with the DisplayPort cable plugged in from the start), the boot process stopped at the end of the systemd messages (ie, the boot was successful, but X did not appear to start). Connecting to the system via ssh from another machine, I set DISPLAY=:0 and ran xrandr:
Screen 0: minimum 320 x 200, current 1280 x 800, maximum 8192 x 8192
LVDS-1 connected primary 1280x800+0+0 (normal left inverted right x axis y axis) 331mm x 207mm
1280x800 60.03*+ 40.02
1024x768 59.92
800x600 59.86
640x480 59.38
720x400 59.55
640x400 59.95
640x350 59.77
VGA-1 disconnected (normal left inverted right x axis y axis)
DP-1 connected (normal left inverted right x axis y axis)
1920x1200 59.95 +
1600x1200 60.00
1280x1024 75.02 60.02
1152x864 75.00
1024x768 75.08 60.00
800x600 75.00 60.32
640x480 75.00 60.00
720x400 70.08
DP-2 disconnected (normal left inverted right x axis y axis)
So, X does appear to be running, but isn't actually rendering to either monitor. I noted that there is no "*" next to a graphics mode for DP-1, which I took to mean that no mode was selected.
I then ran "xrandr --output DP-1 --auto" in an attempt to wake up the monitor. This had no effect on either monitor (I still had the boot messages on the integrated monitor, and a blank screen on the external), but running xrandr again showed that the default 1920x1200 mode was selected:
Screen 0: minimum 320 x 200, current 3200 x 1200, maximum 8192 x 8192
LVDS-1 connected primary 1280x800+0+0 (normal left inverted right x axis y axis) 331mm x 207mm
1280x800 60.03*+ 40.02
1024x768 59.92
800x600 59.86
640x480 59.38
720x400 59.55
640x400 59.95
640x350 59.77
VGA-1 disconnected (normal left inverted right x axis y axis)
DP-1 connected 1920x1200+1280+0 (normal left inverted right x axis y axis) 519mm x 320mm
1920x1200 59.95*+
1600x1200 60.00
1280x1024 75.02 60.02
1152x864 75.00
1024x768 75.08 60.00
800x600 75.00 60.32
640x480 75.00 60.00
720x400 70.08
DP-2 disconnected (normal left inverted right x axis y axis)
The Xorg log shows the monitor connected through DisplayPort being detected with nothing that immediately looks like an error:
[ 22.289] (II) NOUVEAU(0): EDID for output DP-1
[ 22.289] (II) NOUVEAU(0): Manufacturer: DEL Model: a02b Serial#: 842084435
[ 22.289] (II) NOUVEAU(0): Year: 2009 Week: 7
[ 22.289] (II) NOUVEAU(0): EDID Version: 1.4
[ 22.289] (II) NOUVEAU(0): Digital Display Input
[ 22.289] (II) NOUVEAU(0): 8 bits per channel
[ 22.289] (II) NOUVEAU(0): Digital interface is DisplayPort
[ 22.289] (II) NOUVEAU(0): Max Image Size [cm]: horiz.: 52 vert.: 32
[ 22.289] (II) NOUVEAU(0): Gamma: 2.20
[ 22.289] (II) NOUVEAU(0): DPMS capabilities: Off
[ 22.289] (II) NOUVEAU(0): Supported color encodings: RGB 4:4:4
[ 22.289] (II) NOUVEAU(0): First detailed timing is preferred mode
[ 22.289] (II) NOUVEAU(0): Preferred mode is native pixel format and refresh rate
[ 22.289] (II) NOUVEAU(0): redX: 0.674 redY: 0.319 greenX: 0.188 greenY: 0.706
[ 22.289] (II) NOUVEAU(0): blueX: 0.148 blueY: 0.064 whiteX: 0.313 whiteY: 0.329
[ 22.289] (II) NOUVEAU(0): Supported established timings:
[ 22.289] (II) NOUVEAU(0): 720x400@70Hz
[ 22.289] (II) NOUVEAU(0): 640x480@60Hz
[ 22.289] (II) NOUVEAU(0): 640x480@75Hz
[ 22.289] (II) NOUVEAU(0): 800x600@60Hz
[ 22.289] (II) NOUVEAU(0): 800x600@75Hz
[ 22.289] (II) NOUVEAU(0): 1024x768@60Hz
[ 22.289] (II) NOUVEAU(0): 1024x768@75Hz
[ 22.289] (II) NOUVEAU(0): 1280x1024@75Hz
[ 22.289] (II) NOUVEAU(0): Manufacturer's mask: 0
[ 22.289] (II) NOUVEAU(0): Supported standard timings:
[ 22.289] (II) NOUVEAU(0): #0: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
[ 22.289] (II) NOUVEAU(0): #1: hsize: 1600 vsize 1200 refresh: 60 vid: 16553
[ 22.289] (II) NOUVEAU(0): #2: hsize: 1152 vsize 864 refresh: 75 vid: 20337
[ 22.289] (II) NOUVEAU(0): Supported detailed timing:
[ 22.289] (II) NOUVEAU(0): clock: 154.0 MHz Image Size: 519 x 320 mm
[ 22.289] (II) NOUVEAU(0): h_active: 1920 h_sync: 1968 h_sync_end 2000 h_blank_end 2080 h_border: 0
[ 22.289] (II) NOUVEAU(0): v_active: 1200 v_sync: 1203 v_sync_end 1209 v_blanking: 1235 v_border: 0
[ 22.290] (II) NOUVEAU(0): Serial No: G283H929210S
[ 22.290] (II) NOUVEAU(0): Monitor name: DELL 2408WFP
[ 22.290] (II) NOUVEAU(0): Ranges: V min: 56 V max: 76 Hz, H min: 30 H max: 83 kHz, PixClock max 175 MHz
[ 22.290] (II) NOUVEAU(0): EDID (in hex):
[ 22.290] (II) NOUVEAU(0): 00ffffffffffff0010ac2ba053303132
[ 22.290] (II) NOUVEAU(0): 07130104a534207822b325ac5130b426
[ 22.290] (II) NOUVEAU(0): 105054a54b008180a940714f01010101
[ 22.290] (II) NOUVEAU(0): 010101010101283c80a070b023403020
[ 22.290] (II) NOUVEAU(0): 360007402100001a000000ff00473238
[ 22.290] (II) NOUVEAU(0): 3348393239323130530a000000fc0044
[ 22.290] (II) NOUVEAU(0): 454c4c20323430385746500a000000fd
[ 22.290] (II) NOUVEAU(0): 00384c1e5311010a2020202020200012
[ 22.290] (II) NOUVEAU(0): Printing probed modes for output DP-1
[ 22.290] (II) NOUVEAU(0): Modeline "1920x1200"x60.0 154.00 1920 1968 2000 2080 1200 1203 1209 1235 +hsync -vsync (74.0 kHz eP)
[ 22.290] (II) NOUVEAU(0): Modeline "1600x1200"x60.0 162.00 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (75.0 kHz e)
[ 22.290] (II) NOUVEAU(0): Modeline "1280x1024"x75.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[ 22.290] (II) NOUVEAU(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[ 22.290] (II) NOUVEAU(0): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
[ 22.290] (II) NOUVEAU(0): Modeline "1024x768"x75.1 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.1 kHz e)
[ 22.290] (II) NOUVEAU(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 22.290] (II) NOUVEAU(0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
[ 22.290] (II) NOUVEAU(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 22.290] (II) NOUVEAU(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
[ 22.290] (II) NOUVEAU(0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 22.290] (II) NOUVEAU(0): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
Googling has turned up a number of people having issues with DisplayPort, but in these cases the external monitor simply needs to be enabled (xrandr --auto, a BIOS setting, etc). Has anyone experienced this situation, where the working primary monitor stops working?
Thanks!
Last edited by Gavster (2015-01-25 17:00:50)

I got a displayport -> HDMI cable to try the laptop with my television. This worked seamlessly, with X auto-detecting the new monitor and correctly enabling it with a default of 1920x1080 (interlaced). I also was able to change it to 1280x720 (progressive) with xrandr. Since the monitor I originally tried with straight displayport also has an HDMI input, I tried the new cable there and again was met with success. I'll mark this as solved with the likely culprit being something very strange with my displayport cable (I had ruled the cable out since the EDID was properly reporting the monitor model and supported resolutions).

[Solved] Screen lockup since xorg 1.6.3-4 upgrade (catalyst)

Hey there,
since i yesterday upgradet my system (pacman -Syu) and pacman installed a new xorg-server version (from 1.6.3-3 to 1.6.3-4) and xf86-inpud-evdev my screen gets completely locked up after i start GDM. Only thing that helps is to press the reset button.
Now i went back to the radeonhd driver wich works quiet well so far.
Does anyone know what this could be?
xorg.conf for catalyst:
Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "Files"
RgbPath "/usr/share/X11/rgb"
ModulePath "/usr/lib/xorg/modules"
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"
EndSection
Section "Module"
Load "extmod"
Load "dbe"
Load "xtrap"
Load "record"
Load "dri"
Load "glx"
Load "GLcore"
Load "freetype"
EndSection
Section "ServerFlags"
Option "DontZap" "false"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "evdev"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5 6 7"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
EndSection
Section "Device"
Identifier "Card0"
Driver "fglrx"
VendorName "ATI Technologies Inc"
BusID "PCI:1:0:0"
# Option "RenderAccel" "on"
# Option "EnablePageFlip" "on"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection
Section "DRI"
Mode 0666
EndSection
This one worked until yesterday.
I tried to reinstall catalyst several times but it didnt help.
Thank you for your help
Marcel
Last edited by jack_slayton (2009-08-27 14:40:40)

I have the same problem everytime an update releated to xorg is released. Only reinstalling catalyst doesn't is, but recompiling and installing new(er) catalyst(-utils) packages solves the problem - at least on my pc. Maybe this works for you too.

[SOLVED] Can't start compiz with gnome

When I set up gnome initially, I used the following wiki guide:
https://wiki.archlinux.org/index.php/Co … k_Users.29
I had some issues after upgrading to gnome 3.8 that have now since been solved. I wen't through quite a bit trying to fix it and now somehow compiz isn't starting with my gnome/compiz session. It starts just fine if I run
$ compiz ccp --replace
after logging into the session. I think I'm simply not understanding how this session that I've installed works (or .session files in general).
here is my /usr/share/gnome-session/sessions/gnome-compiz.session:
[GNOME Session]
Name=GNOME Compiz
RequiredComponents=compiz;cairo-dock;gnome-settings-daemon;
RequiredProviders=notifications;
DefaultProvider-windowmanager=compiz
DefaultProvider-notifications=notification-daemon
I tried removing cairo-dock from the above file just to make sure that this is the file actually being used and it did start up without the dock as I guessed. Obviously this file is being used. Why won't compiz start as well? I also tried adding gnome-panel to the file and gnome-panel did not start. Is this because it needs a .desktop file as well? I assume so.
Here is my /usr/share/xsessions/gnome-compiz.desktop:
[Desktop Entry]
Encoding=UTF-8
Name=GNOME/Compiz
Comment=This session logs you into the GNOME desktop environment with Compiz and Cairo-Dock
Exec=/usr/bin/gnome-session --session=gnome-compiz
Icon=compiz
Type=XSession
and here is my /usr/share/applications/compiz.desktop:
[Desktop Entry]
Type=Application
Encoding=UTF-8
Name=Compiz
Exec=bash -c 'compiz --replace --sm-client-id $DESKTOP_AUTOSTART_ID --keep-desktop-hints ccp decoration'
NoDisplay=true
# name of loadable control center module
X-GNOME-WMSettingsModule=compiz
# autostart phase
X-GNOME-Autostart-Phase=WindowManager
X-GNOME-Provides=windowmanager
# name we put on the WM spec check window
X-GNOME-WMName=compiz
# back compat only
X-GnomeWMSettingsLibrary=compiz
Last edited by instantaphex (2013-05-04 20:59:44)

So I started to think that maybe compiz was actually starting up but the ccp argument wasn't taking. I ran
$ pgrep -l compiz
and got no output. So compiz really isn't starting at all. What gives?

|Solved| - Screen resolution and nVidia

I installed arch, xorg, nvidia's drives, openbox and gnome.
I can run gnome and openbox without any problem, however, my screen resolution isn't recognised. Here's my /etc/X11/xorg.conf:
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig: version 1.0 (buildmeister@builder58) Thu Jun 5 00:08:24 PDT 2008
# 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.
# Files section. This allows default font and rgb paths to be set
# Server flags section.
# Input devices
# Core keyboard's InputDevice section
# Core Pointer's InputDevice section
# 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
# Graphics device section
# Any number of graphics device sections may be present
# Standard VGA Device:
# Device configured by xorgconfig:
# 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.
# 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 "DRI"
# Mode 0666
# EndSection
Section "ServerLayout"
# The Identifier line must be present
# 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.
# 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".
Identifier "Simple Layout"
Screen "Screen 1" 0 0
InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard1" "CoreKeyboard"
EndSection
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/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"
FontPath "/usr/share/fonts/misc"
FontPath "/usr/share/fonts/100dpi:unscaled"
FontPath "/usr/share/fonts/75dpi:unscaled"
EndSection
Section "Module"
# This loads the DBE extension module.
# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
# This loads the font modules
# Load "type1"
# This loads the GLX module
# Load "glx"
# This loads the DRI module
# Load "dri"
Load "dbe" # Double buffer extension
SubSection "extmod"
Option "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection
Load "freetype"
# Load "xtt"
Load "glx"
EndSection
Section "InputDevice"
# 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"
Identifier "Keyboard1"
Driver "kbd"
Option "AutoRepeat" "500 30"
# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
Option "XkbRules" "xorg"
Option "XkbModel" "logicd"
Option "XkbLayout" "pt"
Option "XkbVariant" "pt"
EndSection
Section "InputDevice"
# Identifier and driver
# 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.
# 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"
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "Auto" # Auto detect
Option "Device" "/dev/input/mice"
# Mouse-speed setting for PS/2 mouse.
Option "ZAxisMapping" "4 5 6 7"
# Emulate3Buttons is an option for 2-button mice
EndSection
Section "Monitor"
# 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 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.
Identifier "My Monitor"
HorizSync 80.0 - 80.0
VertRefresh 75.0
EndSection
Section "Device"
# 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.
# 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
Identifier "Standard VGA"
Driver "nvidia"
VendorName "Unknown"
BoardName "Unknown"
EndSection
Section "Device"
# unsupported card
#VideoRam 319488
# Insert Clocks lines here if appropriate
Identifier "My Video Card"
Driver "nvidia"
EndSection
Section "Screen"
Identifier "Screen 1"
Device "My Video Card"
Monitor "My Monitor"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 8
Modes "1440x900"
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16
Modes "1440x900"
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1440x900"
EndSubSection
EndSection
If I run "xorgconfig" and after that "nvidia-xconfig", my screen resolution is 1024x860, but after changed very mode to my native resolution ("1440x900"), is changes to "800x600".
Last edited by Nomearod (2008-07-23 09:19:07)

heleos wrote:
Widescreen resolutions are not possible with newest vista and linux drivers if the tft is connected with dvi.
Use an older driver or the vga-port instead.
There are maybe some hacks, but I tried many times in vista and linux. And it's always the same, only 1280x1024.
did some googling:
http://forums.nvidia.com/lofiversion/in … 20005.html
Thanks for the reply, but I don't believe that's the problem since that topic is from 2006 and I didn't had any problems last time I instaled arch (3 months ago).

[Kind of Solved] Screen edges in Compiz?

Similar Messages

Maybe you are looking for