The bug task for the somerville project has been removed by an automated
script. This bug has been cloned on that project and is available here:
https://bugs.launchpad.net/bugs/1305760
** No longer affects: somerville
--
You received this bug notification because you are a member of Ubuntu
Bugs
** Changed in: somerville
Importance: Undecided => High
** Changed in: somerville
Status: New => Fix Released
** No longer affects: dell
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/130450
Worked for me with latest updates.
** Changed in: dell
Status: Confirmed => Fix Released
--
compiz-fusion does not start on login
https://bugs.launchpad.net/bugs/130450
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ub
compiz (1:0.5.2+git20070917-0ubuntu1) gutsy; urgency=low
* new 0.6 branch snapshot
* new ABI version
* debian/compiz.wrapper:
- blacklist the "mga" driver (LP: #122961)
* debian/patches/022_fix_session_managment.patch:
- fix the session managment id (thanks to Keybuk, LP: #130450)
We don't have to care about if the user is using bash or where it is. We
can guarantee it's installed and use it directly and we know where our
package puts it.
** Changed in: compiz (Ubuntu)
Importance: Low => High
Status: Fix Committed => In Progress
--
compiz-fusion does not start o
@mannheim: it isn't recommended for two reasons:
a) the user could use another shell that is not bash
b) there's no guarantee that bash isn't installed elsewhere in the path (for
example, /usr/bin/bash)
Instead /bin/sh is always there and usually a symlink to the current
shell.
Cheers, matteo
-
I didn't realize it was a bash-ism. Is it not allowed to begin the
script with #!/bin/bash ?
--
compiz-fusion does not start on login
https://bugs.launchpad.net/bugs/130450
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu
Unfortunately that only works in bash, not dash (which we use).
--
compiz-fusion does not start on login
https://bugs.launchpad.net/bugs/130450
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bug
Supposing that the wrapper is called "compiz" and the binary is called
"compiz.real", then this can be fixed be ensuring that the wrapper
script ends with something like
exec -a compiz compiz.real $OPTIONS ...
This will exec the binary compiz.real, but compiz.real will run with its
progname set
** Changed in: compiz (Ubuntu)
Status: Confirmed => Fix Committed
--
compiz-fusion does not start on login
https://bugs.launchpad.net/bugs/130450
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
u
** Changed in: dell
Status: New => Confirmed
--
compiz-fusion does not start on login
https://bugs.launchpad.net/bugs/130450
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubun
** Changed in: dell
Importance: Medium => High
--
compiz-fusion does not start on login
https://bugs.launchpad.net/bugs/130450
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu
Worth noting:
- After logging in (after entering password) system takes 2-3 minutes for X
session to start.
- Running "compiz --replace" is the workaround I've used.
Also, the comment above should read "desktop effects", not "desktop
affects".
--
compiz-fusion does not start on login
https://b
I've seen this issue on 3 different systems with Gutsy Tribe-5, with
Intel and nVidia graphic cards. My .xsession-errors file shows the same
messages as indicated here. Happens after I save my session and then
restart GDM.
Not an issue when desktops affects are turned off.
** Also affects: dell
** Changed in: compiz (Ubuntu)
Importance: Undecided => Low
Status: Won't Fix => Confirmed
--
compiz-fusion does not start on login
https://bugs.launchpad.net/bugs/130450
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
I agree, to properly fix the problem it will probably require a good
deal of work (I don't know, but I am assuming, I would have to know more
about the whole indirect thing, is it a driver problem that things have
to be done indirectly, or hardware?). But for now, could a simple patch
against gnome
The problem is that you need LIBGL_ALWAYS_INDIRECT defined to run compiz
but when you do a session save/restore it saves the real compiz program
instead of our wrapper script that sets up the environment so compiz can
run. gnome-session isn't doing anything wrong, compiz isn't doing
anything wrong,
So how about adding a .desktop file in ~/.config/autostart calling "compiz
--replace" if the user selected "normal/extra effects" in the relative
appearance settings tab?
Obviously selecting "no effects" should delete/disable it.
--
compiz-fusion does not start on login
https://bugs.launchpad.n
I think Travis just needs to double check his grammer (I think that is what the
s/you/so/ is about, but many people [myself included] don't understand that).
Question is, why is the session saving compiz.real instead of compiz, and why
is it that that cannot be fixed (it is a technical problem,
Not fixable? I don't understand - I'm happy *personally* to run compiz
each time I log in.
BUT, as usability a issue it seems to be unacceptable that a user
running compiz does not get a window manager when they log in. This can
be a major pain - for example, when I log in the windows (without the
s/you/so/
--
compiz-fusion does not start on login
https://bugs.launchpad.net/bugs/130450
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/li
This problem is not fixable. The session saves 'compiz.real' instead of
'compiz' you the proper environment to run compiz.real is not saved.
** Changed in: compiz (Ubuntu)
Status: Incomplete => Won't Fix
--
compiz-fusion does not start on login
https://bugs.launchpad.net/bugs/130450
You r
I have the same problem running Gutsy Tribe 5.
My ~/xsession-errors attached; compiz related entries are:
grep -i compiz .xsession-errors
/usr/bin/compiz.real (core) - Fatal: GLX_EXT_texture_from_pixmap is missing
/usr/bin/compiz.real (core) - Error: Failed to manage screen: 0
/usr/bin/compiz.rea
I'm seeing the very same thing as Wolfe in my .xsession-errors, but I have an
intel card (an Intel Corporation 82852/855GM).
The strange thing is, if I launch compiz by going to the
gnome-appearance-properties again and then selecting "Normal effects", I read
in a console this output:
No nvidi
interesting
/usr/bin/compiz.real (core) - Fatal: GLX_EXT_texture_from_pixmap is missing
/usr/bin/compiz.real (core) - Error: Failed to manage screen: 0
/usr/bin/compiz.real (core) - Fatal: No manageable screens found on display :0.0
but it works when I go to the appearance applet and go back to no
Thanks for your bugreport.
Can you please attach the file "~/.xsession-errros" after a login with
the described failure?
Thanks,
Michael
** Changed in: compiz (Ubuntu)
Status: New => Incomplete
--
compiz-fusion does not start on login
https://bugs.launchpad.net/bugs/130450
You received
26 matches
Mail list logo
