** Changed in: gdm
Importance: Unknown => Medium
--
login background color is hardcoded
https://bugs.launchpad.net/bugs/132833
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.c
This bug was fixed in the package gdm - 2.20.3-0ubuntu1
---
gdm (2.20.3-0ubuntu1) hardy; urgency=low
* New upstream version:
- Now "Esc" key acts like the "Start Again" button in the greeter program.
- Fix regression in GDM 2.20 that caused the daemon to not read
any [
The bug has been fixed upstream now
** Changed in: gdm (Ubuntu)
Status: Triaged => Fix Committed
--
login background color is hardcoded
https://bugs.launchpad.net/bugs/132833
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
** Changed in: gdm
Status: New => Fix Released
--
login background color is hardcoded
https://bugs.launchpad.net/bugs/132833
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu
the correct way would be to try the change suggested on bugzilla and
comment there
--
login background color is hardcoded
https://bugs.launchpad.net/bugs/132833
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing l
Sebastian: From what I understand, you are saying people should not be
modifying files under /etc/gdm because this will break upgrades. This is
fair enough.
But still no clarity about whether in the short term, Jürgen's fix is
the right way or not.
--
login background color is hardcoded
https://
Those change etc files and will break upgrades
--
login background color is hardcoded
https://bugs.launchpad.net/bugs/132833
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
ht
Sorry, second paragraph in my reply contains "should be" instead of "seems to
be".
My apologies, i'm not a native speaker of the english language.
--
login background color is hardcoded
https://bugs.launchpad.net/bugs/132833
You received this bug notification because you are a member of Ubuntu
D
Hi there,
Most of the solutions here just obscure the bug, Sebastien Bacher is right in
this.
The reason that the "camelcolor" appears is the wrong usage of gdmflexiserver.
The gdmflexiserver -a (authenticate) should be a more direct approach to the
real reason that we all seem to get the "cam
"In my opinion, this is the best solution:
Replace this line in /etc/gdm/PreSession/Default
BACKCOLOR="#dab082"
With this:
BACKCOLOR=`gdmflexiserver --command="GET_CONFIG greeter/BackgroundColor
$DISPLAY"`"
That did not work for me, however.
If I replace the line in /etc/gdm/PreSession/Default
In my opinion, this is the best solution:
Replace this line in /etc/gdm/PreSession/Default
BACKCOLOR="#dab082"
With this:
BACKCOLOR=`gdmflexiserver --command="GET_CONFIG greeter/BackgroundColor
$DISPLAY"`
If you make changes using gdmsetup, won't have to change the file, for
every backcolor ch
Could people stop to apply such workaround? you are breaking next
upgrades this way but will probably not notice for some time until the
configuration change in the package and then you will wondering why the
upgrades are broken
--
login background color is hardcoded
https://bugs.launchpad.net/bu
the new patch is weird, anyway why do you want to remove the default
rather than fixing this bug the correct way?
--
login background color is hardcoded
https://bugs.launchpad.net/bugs/132833
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assign
The fix proposed by eTM in comment #11 is already working perfectly for me, so
I patched the Default file that comes with gdm 2.20.0ubuntu3 using his file.
** Attachment added: "Default.patch"
http://launchpadlibrarian.net/9842505/Default.patch
--
login background color is hardcoded
https
no test patch
** Attachment added: "path.diff"
http://launchpadlibrarian.net/9842477/path.diff
--
login background color is hardcoded
https://bugs.launchpad.net/bugs/132833
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
deskto
the patch doesn't really make sense, you can as well remove the test if
that's to do if color=x then color=x
--
login background color is hardcoded
https://bugs.launchpad.net/bugs/132833
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
Worked here. I've created a patch from what Justin said
** Attachment added: "patch.diff"
http://launchpadlibrarian.net/9839105/patch.diff
--
login background color is hardcoded
https://bugs.launchpad.net/bugs/132833
You received this bug notification because you are a member of Ubuntu
Deskto
Here's how to fix the problem.
open /etc/gdm/PreSession/Default
change the part under the comment "#Default value" from this:
# Default value
if [ "x$BACKCOLOR" = "x" ]; then
BACKCOLOR="#dab082"
fi
To This:
# Default value
if [ "x$BAC
I've also forwarded some informations from the bug upstream now
** Changed in: gdm (Ubuntu)
Status: Confirmed => Triaged
--
login background color is hardcoded
https://bugs.launchpad.net/bugs/132833
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
Could anybody send a patch or debdiff to fix the issue?
--
login background color is hardcoded
https://bugs.launchpad.net/bugs/132833
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubun
It actually works, thanks Jürgen.
I hope the fix will be noticed upstream.
--
login background color is hardcoded
https://bugs.launchpad.net/bugs/132833
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desk
I tried to apply your solution Jurgen, but the color I set appears just
for a second and afterwards it falls back to the hardcoded color.
Here is my /etc/gdm/PreSession/Default
** Attachment added: "Default"
http://launchpadlibrarian.net/9465171/Default
--
login background color is hardcoded
I confirmed the bug and provided a solution.
--
login background color is hardcoded
https://bugs.launchpad.net/bugs/132833
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
http
Affected File (in gutsy):
/etc/gdm/PreSession/Default
Reason:
GDM_GREETER_TYPE is not set, so always fallback to hardcoded color
Fix - add the following lines (after the comment "Set background color"):
GDM_GREETER_TYPE=`gdmflexiserver --command="GET_CONFIG daemon/Greeter $DISPLAY"`
GDM_GREETER_T
** Changed in: gdm (Ubuntu)
Status: Triaged => Confirmed
--
login background color is hardcoded
https://bugs.launchpad.net/bugs/132833
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@li
The regression stil occurs on my gutsty up-to-date and the last comment
upstream is from june.
Here:
http://bugzilla.gnome.org/show_bug.cgi?id=438939#c12
a reversion is suggested to fix the problem, could some expert look if that can
be done without causing incompatibilities?
thanks
--
login b
The same thing happens to my me.
Installed Gutsy Tribe4 updated to 5
--
login background color is hardcoded
https://bugs.launchpad.net/bugs/132833
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bu
** Changed in: gdm
Status: Unknown => New
--
login background color is hardcoded
https://bugs.launchpad.net/bugs/132833
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
not sure of the Ubuntu bug number, it's upstream
http://bugzilla.gnome.org/show_bug.cgi?id=438939, marking Triaged for
now
** Changed in: gdm (Ubuntu)
Status: Invalid => Triaged
** Also affects: gdm (upstream) via
http://bugzilla.gnome.org/show_bug.cgi?id=438939
Importance: Unknown
Thanks for the bug report. This particular bug has already been
reported, but feel free to report any other bugs you find.
** Changed in: gdm (Ubuntu)
Importance: Undecided => Low
Assignee: Q Hartman => Ubuntu Desktop Bugs
Status: Confirmed => Invalid
--
login background color is
This behavior has always existed, AFAIK, but you imply that in Feisty
that background color was synchronized with your GDM choice. Is that the
case? That color you see between login and Gnome is the root X window,
which exists "below" the GDM and typical Gnome Desktop levels. So you
will see it "p
31 matches
Mail list logo
