Debian :: Window Manager (compiz) Needs To Be Reloaded On Boot?
Jan 29, 2011I use compiz but when I boot I need to reset the windowanager for it to function correctly :'(. It is not the end of the world, but it is annoying
View 14 RepliesI use compiz but when I boot I need to reset the windowanager for it to function correctly :'(. It is not the end of the world, but it is annoying
View 14 RepliesI spent *#@$ hours trying to figure out how to change my default window manager to "compiz-manger".I tried using gconf-editor and .gnomercAnybody has an idea how to do this?
View 8 Replies View RelatedI recently upgraded the motherboard/processor on my computer (as in quadrupled the processor and octupled the ram). The new board has a built in GPU (intel) and from searching the forums, I think this is part of the problem. Every time I boot up the computer, I need to open the Compiz icon and use it to reload the window manager before I see any title bars, borders, etc. 've tried the .bashrc hack (metacity --replace), but that doesn't do anything. In fact, whenever I open the terminal, I need to have two tabs open in order to use it, and when I close it all the borders go away again (even when I haven't done anything). Also, the onboard sound card (intel) doesn't work, but that's another task (I at least have a compatible card for that).
View 9 Replies View RelatedI'm trying to make Compiz activate at bootup, but I can't seem to get it to work. Basically, I'd like to make Compiz the default Window Manager in Kubuntu Lucid. How to accomplish this?
View 1 Replies View RelatedI finally waded through all the graphical issues that have been reported when upgrading 10.10 to 11.04. I've managed to get the nvidia drivers installed and working (even though Jockey still reports that nvidia-current is installed but has not been activated).Whenever I log into an Ubuntu Classic session, GNOME defaults to using metacity as the window manager. In order to get my compiz effects working, I have to open a terminal and do "compiz --replace". After that, everything appears to work normally including on screen notifications, the cube, etc.
I've though of including a "compiz --replace" script in Startup Applications as a possible workaround, but is there a better way to handle not having compiz started by default? Is there something in gconf-editor or similar that I can edit in order to make GNOME default to using compiz?
I'm thinking about switching from Ubuntu 11.04 classic to Xubuntu 11.04. My main priority is to have compiz running.
However, though I know how to get it running, I want to be able to use it without using the
Code:
Code every startup.
I know how to make it default in GNOME, however not in XFCE.
i found this http://crunchbanglinux.org/forums/to...indow-manager/ it has screenshots of exactly what i'm looking for, but i cant actually get it to work when following their instructions. i create the fusion.desktop file and the start-fusion.sh file, but they do not show up in xwmconfig or KDM. is there something in particular for slackware that i have to do to add the .desktop entry to my list of sessions?
View 4 Replies View RelatedI just recently discovered flubox, it's a window manager right"? like gnome? or is it like compiz fusion? if so, it is better than compiz fusion? can i use it in conjunction with compiz fusion?
View 1 Replies View RelatedI have been experiencing this peculiar issue with Ubuntu 9.10. Whenever the system boots, the audio doesn't work but when I do a 'sudo alsa force-reload', the volume icon gets muted and on unmuting it the audio works. This is the information regarding the audio device I get on doing lspci
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03)
I`ve triple checked this and every time I run compiz any window opened has no minimise maximize or any other buttons for some reason but I don`t know why.If I exit compiz from the icon there are still no window buttons until I log out and then back in again. I can`t find this mentioned elsewhere but it`s happening every time in Squeeze AMD64 fresh installation having only downloaded AWN and compiz (tried this without AWN running and same result).It seems to have a drawing issue as if I run AWN then only three icons can show up on the dock any others are just thin white lines but I have no idea why my buttons dissappear. Anyone able to enlighten me?EDIT: Well I realised that by default the window decorations bit was not enabled, enabling it solves the first issue so the white lines instead of icons in AWN can`t be related so will look into that seperately.
View 3 Replies View RelatedHow would I boot into an application on X without using a window manager?
View 1 Replies View RelatedIs there some way top stop the "blind effect" of compiz so that when you double click the top title bar of a window that it maximizes the window instead of the rolling up type effect? Also when i place my mouse on the top right of the screen it brings it to a choosing window type mode where you can pick which window you would like to open, is it possible to get this on the top left of the screen instead? Lastly when I use Kdebluetooth4 to send a file to my computer where does that file save to?
View 2 Replies View RelatedXP and Ubuntu are on different drives and they were booting ok prior the the reformatting. With the Ubuntu drive selected as the 1st hd boot device in Bios: I can boot into Ubuntu ok if I select it in the Grub2 menu If I select XP in the Grub menu I get:
"error:no such device c8e4918ce4917cfe"
If I select the XP drive as the 1st hd boot device in Bios I can boot straight into XP.So that is ok. This thread: [URL] has given me a clue that: "The UUID listed in grub.cfg is wrong In some cases the UUID in the above search line in grub.cfg is wrong. This can for example happen if the UUID has changed due to formatting or partitioning. Bugs The "search" function is plagued by various bugs (see [1], [2]), causing the search to fail."
However the fix in that thread gives me this result: "At the grub menu at boot up (you might have to hold the "shift" key or press "Esc" to get to the Grub menu) select the OS you are trying to boot. But do not press "enter", press "e" instead to edit the menuentry. Delete the line
search --no-floppy --fs-uuid --set 86d32ee3-aec6-490b-8dab-e5cfff9c7af9
and then press "Ctrl+X". This should boot your OS. If you were not able to boot into you OS, you are infected by a different problem and should not continue this howto." My Boot info script results are:
Code:
============================= Boot Info Summary: ==============================
=> Windows is installed in the MBR of /dev/sda
=> Grub 2 is installed in the MBR of /dev/sdb and looks on the same drive in
[code]....
I have installed Debian Lenny on my AMD Phenom PC. Now I had installed it through debian-503-amd64-i386-powerpc-netinst.iso which I burned on a CD and installed on my Hard Disk. Now I would like to easily install x window and kde window manager on this system.
Can anybody tell me
1. What exactly I will have to download extra.
2. How to install it on my system.
3. If necessary how to configure it.
I am setting up a thin client boot (over NFS) with x2go thinclient. So far everything works, the client boots over PXE, mounts the NFS dir on the server. But the x2go thinclient system does not install properly. I end up with a CLI prompt, to log in. It does not start X, not does it start the x2go client in a window managerless X session.
X2go is, in case you don't know it yet, a cool Linux X terminal session system, very much like Nomachines NXserver. I like it very much, since my experience, especially with freenx has not been good.
Now I am missing some Linux knowhow here: I know that after startup (the CLI part), the display manager is started (GDM or KDM), which starts the X server and shows the graphical login. Now since X2go does not properly setup and there is no documentation about the thinclient part, I will set it up myself.
I need the system to boot up, startx and then immediately start an X program (x2goclient), without having to log in before.
I found that putting a .xsession file in to the users home dir causes that script to be run when you invoke startx.But when I put startx in a script that runs as the last one in the runlevel (as in S05startx), it does not run at all.
What is the proper way to run X and a program on it directly, right at startup?
I have a troubling issue. I log into Linux Mint 9 (fully up-to-date) on my Samsung Q320 laptop with power connected and after a few minutes it seems like the entire X session dies, I am logged out, all processes are killed and I am presented with the normal GDM login screen. When I first installed Linux Mint, this never happened. I have the NVidia closed-source driver installed and when the system logs me out, it immediately restarts X loading the NVidia driver which flashes the logo on screen. This all happens instantaneously, so it is not a reboot of the machine, just a restart of the display manager it seems.
There does not seem to be any cause for this. I have disabled all screen saver and power management settings that may lead my system to auto-logout of Gnome. The system log doesn't indicate anything unusual happening. Confused about where to to take it from here bar and fresh install of the OS. Perhaps there are some X11 logs I should be checking.
Update: Moved to Ubuntu 10.10 and its recommended NVidia driver and have not experienced this problem since.
I compiled QLWM window manager but it's not in GDM's session menu. How do i add it there?
View 1 Replies View Relatedxdm which refuses to load a window manager. I run Debian squeeze. xdm tries to execute /etc/X11/xdm/Xsession, which is actually an empty file, and fails with the error 'too many open files'. Afterwards xdm terminates the session and executes Xreset. Here the entries from the log:
Sat May 22 11:27:19 2010 xdm info (pid 2246): sourcing /etc/X11/xdm/Xsetup
Sat May 22 11:27:23 2010 xdm info (pid 2246): sourcing /etc/X11/xdm/Xstartup
Sat May 22 11:27:23 2010 xdm info (pid 2275): executing session /etc/X11/xdm/Xsession
[code]....
I was unable to find anything valuable concerning this problem. This is kind of annoying because I always have to switch to a console, stop X and startx X manually using startx. Then everything works out just fine. Unfortunately I am not yet that familiar with the setup process of X.
I did remake my minimal installation. My window manager produces no background picture else I did add someone. So i will do it using xorg-xli. I did find the (in other cases usual) xinitrc as /etc/X11/xinit/xinitrc but in only refers to an other script
and the other script (/etc/X11/Xsession) does not include some usuable steps to include easily supplementary starting commands.
Where is to do that in Debian SID actually?
I have installed the debian lenny base system in my old pc. I want only a minimal system with a small window manager like icewm and firefox to surf the web. What I need to write now in text mode to install this minimal system?
View 9 Replies View RelatedI installed jessie 8.1 and wmii ( Version: 3.10~20120413+hg2813-8) and I use a basic wmiirc.
Code: Select all:~/.wmii-3.10$ ls -la wmiirc
-rwxr-xr-x 1 root root 8033 août 1 17:28 wmiirc
If I want to run wmii the system says:Code: Select all:~$ wmii
wmii: fatal: another window manager is already running
Some information :
Code: Select all~$ update-alternatives --config x-window-manager
Il existe 3 choix pour l'alternative x-window-manager (qui fournit /usr/bin/x-window-manager).
Sélection Chemin Priorité État
------------------------------------------------------------
0 /usr/bin/wmii 60 mode automatique
1 /usr/bin/metacity 60 mode manuel
2 /usr/bin/mutter 60 mode manuel
* 3 /usr/bin/wmii 60 mode manuel
I installed debian with minimal packages (without an any X components). Later I installed xserver-xorg-video-intel , xserver-xorg-input-mouse, xserver-xorg-input-kbd ... and other X components through apt-get. Created a Xorg.conf file.
On execution of X, I see black screen without cursor. What are the other minimal packages that I need to install in order to run any window-manager like openbox.. ?
In the murky world of X11, window managers, session managers and desktop environments I cannot seem to figure out how to achieve the following in Squeeze:
1. Leave Gnome installed, but prevent it from launching when typing startx
2. Have both X11 and my prefered default window manager (blackbox) startup when I type startx (or similar)
My ultimate goal is to leave Gnome installed but "dormant" and when I do a remote ssh -X be able to use X11 forwarding with blackbox.
How would I add a window manager to the gnome sessions menu on debian squeeze please? The window manager has been compiled from sources.
View 2 Replies View RelatedSome of my applications use different window types for pull-down menus than what compiz window animation think. This means that I get normal open window animation on these pull-down menus instead of the menu-theme. Inside the CompizConfig you can specify exactly which window types the different animations apply to, and you can use "grab" to probe your window for this info. My problem is that I can't "grab" the info for the pull-down, since it leaves "grab" mode once I try to open the menu (and grabs the info for the parent window instead of the menu). How do I get to know the window properties of the pull-downs, so that I can map them to the relevant window animation theme?
View 5 Replies View RelatedI like to start Emacs as part of a login script and leave it running for the duration of my login session (which is typically weeks).
I have scripts to call emacs-client which will allow me to use a file-manager or Windows Explorer to locate files and right-click to edit them in Emacs.
I often end up with a lot of emacs windows (frames) open and I like to just be able to close them by clicking on the MS-Windows or KDE X button at the top-right.
The trouble is, if the window is the last one, this will shut down emacs which will lose all kinds of interesting history information.
As a work-around I use C-x 5 0 which won't let me close the last frame but this is often not as convenient as using the mouse
Does anyone know how to configure Emacs so that it can intercept the Window-Close button of the last frame to either request confirmation or simply disallow it?
On MS-Windows, disallowing closing of the last window may cause logoff to hang if emacs is still running but I'm not too worried about that.
Has this feature been removed from the version of Compiz that comes with 10.04?I was running 9.10 for a few months and I configured a feature for zooming out windows into a kind of preview mode.I remember setting up a key combo and when I clicked on any window and pressed the combo, it would cycle between 2 preview sizes of around 25% and 10% and then back to it's normal size.I could drag a zoomed-out window around the desktop but obviously it would not be usable until it was restored to normal size.
The window contents would still update though and it was a great way of keeping an eye on many windows at once.I have looked at every single setting in CompizConfig Settings Manager but it's nowhere to be found and I really miss it!
I couldn't find a section for visual customization. Is it possible to make it so that windows not being used have a certain opacity, and windows being used have another? Also, how can you change the opacity of menus? I used to be able to do this, but it seems I've forgotten.
View 3 Replies View Relatedi just reinstalled compiz and nvidia drivers and i dont have the compiz window borders.
i have tried
Code:
compiz --replace
emerald --replace
emerald --replace &
with no change in borders.
I setup fedora 14 64 bit today itself and am loving it! But the problem i am facing is in compiz! When i enable desktop effects from System/Prefrences/Desktop Effects, everything works absolutely fine. All the effects... But when i try to resize a window, Compiz crashes and all the borders of the window disappear. The ABRT shows an error. Here is what it says
Package: compiz-0.8.6-3.fc14
Latest Crash:Sun 09 Jan 2011 05:44:37 PM
Command: compiz --ignore-desktop-hints glib gconf gnomecompat --replace
Reason: Process /usr/bin/compiz was killed by signal 11 (SIGSEGV)
Comment: None
Bug Reports: