Debian Multimedia :: Compiz Refuses To Auto Start Properly (with Gnome)
Apr 16, 2011
How to get compiz to auto-start. What seems to be the generally accepted method (from what a few google searches and the debian wiki tell me) of using gconf-editor and changing the window manager from 'gnome-wm' to 'compiz' in desktop > gnome > session > required_components doesn't change anything. The only method I found that did not involve using a terminal and running 'compiz --replace' every time I boot the computer was to add compiz and fusion-icon to the gnome startup apps, but this causes unwanted flickering (it starts metacity and then replaces it with compiz, ie it's simply automating what I would do with the terminal). Autostarting the fusion-icon alone does not start compiz, although it allows me to start it from it's menu if I right click the icon. Note that I sometimes use fluxbox as well, so starting it on boot isn't really an option either.
Perhaps this can be useful :
compiz:
Installed: 0.8.4-4
Candidate: 0.8.4-4
gnome-session:
Installed: 2.30.2-3
Candidate: 2.30.2-3
I updated my Jessie system today. Nothing crucial in the apt-get list as far as I can see, perhaps it's unrelated. Anyway, now I cannot open the terminal any longer. Launching `gnome-terminal` shows the app name in the menu bar, a spinning wheel, and then after a few seconds nothing. It doesn't appear in the list of processes, either. I can still log into the text shell via ctrl-alt-F1.
I also added `LC_TIME="en_GB.UTF-8"` to `/etc/environment` to get rid of the American date format. Could it be the cause? I just tried to launch the terminal from the JVM. I get this output:
Code: Select all(process:2629): Gtk-WARNING **: Locale not supported by C library. Using the fallback 'C' locale. Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0: Error calling StartServiceByName for org.gnome.Terminal: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.Terminal exited with status 8
I will delete the environment variable again and reboot, but I wonder if I can still have the British date format?
I installed debian and want to install compiz (properly).Read this thread Compiz and followed the instruction to install the packages. It mentions xorg.conf which does not exist where it tells me to look.I can type "compiz --replace" and it does do something but all the window borders disappear. I tried compiz setting manager - still same problem.And no visual effects (presumably due to missing xorg.conf)
Although "Shadow Windows" is set to "any" in CCSM I get no shadow under gnome panels. I tried adding (any) & class=Gnome-panel, but this does neither do anything at all. I'm using Debian Sid amd64, Compiz 0.8.4, X 1.7.7. Video card: ATI Radeon HD4570.
Bought a lovely new Logitech MX3200 keyboard recently, didn't expect to be able to use all the media keys on it. I was surprised, then, when I discovered HIDPoint, some software for configuring the hotkeys on many Logitech keyboards, and more surprised when I saw that mine was on the supported devices list. Anyway, HIDPoint is only available for up to Ubuntu 9.10, and refuses to install properly in 10.04.Here is the output when I try to run the installer:
[Code]....
error while loading shared libraries: libpng.so.3: cannot open shared object file: No such file or directory I can't find libpng.so.3 in Synaptic, so what should I do to get this program to install?
I'm a Karmic user, using a Nvidia Geforce 9500GT video Card.
I'm telling you about my GPU, because since I upgraded to the 190.42 Nvidia "official" new drivers, what's happening is:
My Compiz is no more able to save it's configuration across the sessions, and every time I close my PC or when I simply need to restart my active session, Compiz needs to be started again manually, It do not auto-activate by the compiz setting preferences. Doing: System --> Preferences --> gnome-appearance-properties (TAB: "Visual effects") and click on "normal" checkbox, to activate the compiz visual effects.
Is there anyone able to teach me how to save the compiz activation, in order to avoid the manual, boring, repetitive, activation each time?
I got the nVidia driver and Compiz installed. Everything's running fine . But then I tried crtl+alt+F1 - which worked though the font was way too big - and then crtl+alt+F7 to get back to the Desktop but it went to a black screen and blinking cursor instead. I searched a bit and it seems this was a problem a few years back but nothing recent. FWIW, I don't have this problem with Hardy/nVidia/Compiz on another drive in this same machine. Is there a way to fix this?
I have a Debian testing box with Xfce (no Gnome, no Nautilus). It has all gvfs-related stuff installed, including all backends and fuse interface. But any attempts to gvfs-mount anything (like sftp://... or smb://...) fail with error opening file: Operation not supported, and gigolo shows only 'unix device (file)' in the list of supported protocols.My ~/.gvfs has rwx permissions, and I'm a member of fuse group; other fuse-related stuff works for me.
Well, I initially had quite a lot of trouble getting Compiz to work, but I finally got it to go. I had to use these start-up parameters in order to get it to work: Code: LIBGL_ALWAYS_INDIRECT=true compiz --replace --sm-disable ccp & emerald --replace How in the world do I get Compiz to start up like this on boot up, so I can use it easily?
Linux noob here with a very fresh Debian 5.04 install. Not sure if this is the correct board for this but here goes;*No* programs start in X. Terminal, System Monitor, Epiphany, Gedit, Synaptic Package Manager... They all fail to start.The programs try to start for 15 seconds after which they give up. For example, if I press the Epiphany-icon in the panel I see "Starting Epiphany We..." in the lower-left corner and the mouse cursor changes to the loading animation for 15 seconds but then after that nothing happens and the "Starting Epiphany We..."-icon disappears. I have two users (plus root of course) and the same thing happens with both accounts.
I can start the icons I have on my desktop (Computer, Home folder, Trash and Downloads) and I can Lock the screen/log off/shut down but that's about it. Oh and one more thing; sometimes when I log in everything works just fine, so this whole thing seems a bit random.
I'm using Debian 2.6.32-5-amd64 (testing) for several years now. Initial installation was done at least two years ago, without any issues. I do keep my system up-to-date. However, a few months ago, after an apt-get update/upgrade/system-upgrade, I discovered that, if I try to launch KDE or Gnome, I only see a black screen and I actually need to restart my computer. On some cases the system even froze and needed to hardware reset, and run fsck in recovery mode after rebooting. Really very annoying... Since I don't use KDE or Gnome desktops (just a few applications depending on KDE/Gnome libraries), I didn't bother to figure out what is happening. However, others use my computer occasionally, and I would like to get KDE and Gnome working again. I purged and reinstalled everything that had to do with KDE or Gnome, even deleted KDE/Gnome files in my home directory, but the black screens are still there, everytime I try to start any of those desktops. Note that kdm or gdm don't even mention KDE or Gnome as available sessions, although all necessary packages are installed. I have no idea what to do to fix the problem.
Another question: I recently got rid of gdm because it is buggy and tried wdm instead. However, /etc/profile is not read anymore. Apparently, wdm does not use /etc/profile by default. Is there any way to change this?
I installed jessie from a beta/rc shortly before release on my MacBook Pro 13 Retina and have kept it up to-date with apt-get dist-upgrade. Rcently gdm3/gnome-session have stopped working together. When I log in the screen goes black for a couple of seconds then goes back to the login screen. This happens with "System Default", "GNOME Classic" and "GNOME", but not with "GNOME on Wayland". However, Wayland seems to have some other issues. I haven't tried an alternative dm yet, eg lightdm, but the GNOME desktop does work when started with startx.
I've just used journalctl to get logs of what gdm3 and gnome-session were doing at the time. After booting I waited until the clock reached the next minute (19:55) so I'd know at which point in the logs I'd hit enter on my password. I'll post the gdm log separately in two chunks because the forum server doesn't seem to like text attachments and they're too long for one post.
Log from gnome-session: Code: Select all-- Logs begin at Thu 2015-05-07 19:54:06 CEST, end at Thu 2015-05-07 19:56:41 CEST. -- May 07 19:54:08 jeanette gnome-session[885]: gnome-session[885]: WARNING: Could not parse desktop file caribou-autostart.desktop or it references a not found TryExec binary
I've just installed a new Debian Jessie with gnome from zero, and I have installed Xbmc on it. when I open xbmc on gnome interface, it crash and log out from gnome.
On the xbmc crash log I find several errors, browsing them on the network I didn't find anything.
here the crash log:
Code: Select all ############## XBMC CRASH LOG ############### ################ SYSTEM INFO ################ Date: Mon 14 Sep 00:15:49 CEST 2015 XBMC Options: Arch: x86_64 Kernel: Linux 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1+deb8u3 (2015-08-04) Release: Debian GNU/Linux 8 (jessie) ############## END SYSTEM INFO ##############
i'm using debian 8.3 with gnome 3.14.4.Every time i'm opening a pdf file with evince, either by using terminal or nautilus, i can see as a default the thumbnails sidebar. Is there any option that i can use in the terminal, that can hide thumbnails sidebar at the opening?
I know that i can use F9 shortcut to hide the sidebar after the file opening, but i'm asking for an option so that i will not see the sidebar at all when the pdf file is opening.
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.
I installed compiz on squeeze. I followed the steps on [url] , everything seems fine except my gnome-terminal shows me a white-in-white screen, seems like both the background and foreground are white, I tried to change the gnome-terminal profile, it doesn't work, after I disable compiz, gnome-terminal back to normal. I tried to install xterm, it can work, but it not easy to use for me, I still want to use gnome-terminal,
My laptop is lenovo Thinkpad T400. 01:00.0 VGA compatible controller: ATI Technologies Inc Mobility Radeon HD 3400 Series
Some days ago (2015-09-28) I installed Debian testing amd64. Log in as a user failed and instead of the Gnome UI there was a sad face with the text: „Oh no! Something has gone wrong. A problem occurred and the system can't recover.
All extensions have been disabled as a precaution. Log out“.
The relevant output of journalctl (run as root) said:
etc/gdm3/Xsession[5379]: cannot connect to brltty at :0 - /etc/gdm3/Xsession[5379]: Service 'org.kde.kaccessibleapp' does not exist. - gnome-session[5379]: x-session-manager[5379]: WARNING: Application 'gnome-shell.desktop' killed by signal 5 - gnome-session[5379]: x-session-manager[5379]: WARNING: App 'gnome-shell.desktop' respawning too quickly - x-session-manager[5379]: Unrecoverable failure in required component gnome-shell.desktop
[Code] ...
After some investigating, I found three work-arounds.
(1) Use gdm3-autologin: In /etc/gdm3/daemon.conf, remove the double crosses and insert own user name AutomaticLoginEnable = true AutomaticLogin = <own user name> Disadvantage: Only one user can have access to the Gnome ui. If you log out, you enter the gdm3 greeter and … see above.
(2) Turn off gdm3 by running 'systemctl stop gdm3' as root, log in into a terminal as a user and run startx.
(3) Install package lightdm and make it to the standard display manager with 'dpkg-reconfigure lightdm'. Disadvantage: Energy manager and screensaver settings of the Gnome control center are ignored.
The easiest way, however, especially if there are several users, is logging in via the gdm3 greeter.
I find xcompmgr more than adequate for making a desktop look pretty modern, and I don't like the more extravagentCompiz gimmicks - but there is one thing that irritates when using xcompmgr which someone here might have worked round.
Rounded window borders don't draw and redraw properly when using the Terminal (gnome-terminal and the LXDE and Xfce ones) or system monitor and moving them from their default place. You get this little white botch at the corners. I'm not massively technical and I'm ambivalent about how much more I want to learn as I have plenty of creative outlets already, but I would like to solve this. Somehow xcompmgr is treating these programs as a different class? It's capable of drawing the window borders properly as it is just these two programs that get botched. Possibly this doesn't get noticed as maybe people usually use xcompmgr with openbox and LXDE and their square window borders. I did do a search but there was nothing matching what I saw.
I upgraded to jessie today and I am having problems with my background. When I log in, the background tries to start on the external monitor but then it fails to load. I can change the background in settings but it does not show up. The background just becomes black and I am not sure why.
GNOME 3 Failed to Load Unfortunately GNOME 3 failed to start properly and started in the fallback mode.This most likely means your system (graphics hardware or driver) is not capable of delivering the full GNOME 3 experience.
.The interface is now Gnome 2. I have not change screen resolution 1280�720, now is 1024x768.
Result of xrandr -q
Quote:
xrandr: Failed to get size of gamma for output default Screen 0: minimum 1024 x 768, current 1024 x 768, maximum 1024 x 768 default connected 1024x768+0+0 0mm x 0mm 1024x768 0.0*
Running FF 3.6.13 on Slack 13.1 (32-bit). Every time that I use FF when I close it the processes that are spawned when it starts never end. I have to manually go and kill them. It is pretty annoying more than an inconvenience since I don't normally use FF. Unfortunately I have to use it, every now and then, for some things and if I need to restart it I have to open a terminal and kill the processes.
I've tried re-installing on top of the version that I have there, and actually uninstalling and installing it again (of course making sure that all of the directories are gone), I've also tried renaming my ~/.mozilla directory (in case there is a problem with the profile).
I just moved my / from sda1 to an ide drive, hde1. i dont see how this could have caused any of these issues, but it did.
First my network card failed to start. i added a line in my rc.local file (where i put all of my additional programs, etc i want to start):/etc/rc.d/rc.inet1
The above now starts my network card with my static ip configured. dhcpcd also worked but i wanted this static.
Now samba will not start. i have the following line in my rc.local: /etc/rc.d/init.d/samba start
This used to work just fine. at first i thought that samba may be trying to start before my network card gets an ip, but the line is *after* the network startup line. just to make sure, i made an additional script called startsamba which contained a sleep 60 followed by samba start, to delay the startup of samba even further.
The message samba reports is very vague, something like failed - core dumped. most of the core dump log is garbage characters, but here is the beginning which seems like it might contain some info:
Code:
ERROR: Can't log to stdout (-S) unless daemon is in foreground (-F) or interactive (-i) after the system starts, i can drop to a console and type "/etc/rc.d/init.d/samba start" and the service starts just fine. i've also tried starting samba manually with "smbd -d" which also produces the core dump when started from rc.local, but not when started from a console after startup.
However, it refuses to connect properly. It previously connected, but now whenever I plug it in, nothing happens.
lsusb before:
Code:
lsusb after:
Code:
dmesg error:
Code:
From some other googling, is seemed as if removing "ehci_hcd" or "uhci_hcd" would fix it, however running the following commands does nothing, as shown below:
I have a "time-server". It's sending time to different devices through different ports/protocols. The problem is that it has no operator and that makes some extra difficulties.
Now when i try to start it using terminal Code: Select allsudo ./myprogram works fine and
Code: Select all./myprogram doesn't work.
It is so because without sudo i have no access to ports. As a result If i add my program to System->Preferences->Startup Applications it has the same problem. So i need to start it as root, auto-start, right after auto-login to system but without entering password cause nobody will do it.
Also I need to start ntpd but it also asks password sometimes I've tried googles but it offer a few ways with entering password that isn't suitable for me or writing some scripts/changing system files but with no example I'm afraid to break it all. So is there a way to start Myprogram and NTPD as root with no password entering?
My system is Debian 6.0.10 Squeeze, Kernel 2.6.32-5-686
it happened first after upgrading about a week (|| more) ago. i thought that it's just em.. kinda normal (i'm running debian unstable, so such things are happening often).
but now it became a problem: i've tried reinstalling nvidia's drivers and compiz itself. no effect. also, i can't catch any errors in logs.
I am using Deluge on my Debian server, for a simple auto start at boot I us the following lines in the /etc/rc.localsudo -u User delugedsudo -u User deluge-webDeluge is running after boot but i wane check if its running with User account and not as root.So I did a ps -aux | grep deluge and notice a line that root is trying to run the command sudo -U User deluge-web (i think its trying).
User 1735 1.5 1.0 187680 21604 ? Sl 16:30 0:04 /usr/bin/python /usr/bin/deluged root 1736 0.0 0.0 20924 1168 ? S 16:30 0:00 sudo -u User deluge-web User 1737 1.5 1.1 70400 24084 ? S 16:30 0:04 /usr/bin/python /usr/bin/deluge-web
The question is what does this mean? can i leave it running, is it better to kill it if so how to prevent that it happen on start-up.
I have just did a fresh install debian jessie today in virtualbox, the X window manager is fxce. By default the default runlevel is 5, and I tried to change the /etc/inittab content:
Code: Select allid:3:initdefault:
and reboot, but it didn't effect to the result, the X-window auto loaded again >.<
I need to change it that will boot in to console mode first, and can run startx if necessary, how can I change it permanently?
