Public bug reported:
Binary package hint: gdm
XDMCP logins work the first time in Lucid, but not the second time due to an
uninitialized structure.
The relevant 2-line patch in
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=579033#61 has been accepted
upstream and is included in Maverick+.
P
Is it possible for gnome-session to return to the parent process a different
exit code based on what the user selected?
E.g.
logout => return 0
reboot => return 1
shutdown => return 2
This way LTSP could look at the exit code and act appropriately...
Or is there another way for LTSP to get noti
** Changed in: gnome-session (Ubuntu)
Status: New => Confirmed
--
gnome-wm erroneously detects card as compiz capable
https://bugs.launchpad.net/bugs/673072
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in ubuntu.
I see that gnome-wm chooses compiz when `xdpyinfo` contains "Composite"
, so I'm also attaching the output of xdpyinfo for that card that indeed
contains "Composite".
So if "Composite" is enough to run compiz, maybe then it's a bug in the
UniChrome module or in compiz itself?
** Attachment added:
** Summary changed:
- gnome-session fails to detect compiz capable card when using ltsp
+ gnome-wm erroneously detects card as compiz capable
--
gnome-wm erroneously detects card as compiz capable
https://bugs.launchpad.net/bugs/673072
You received this bug notification because you are a member
glxinfo for the above openchrome card.
Btw to get past the login screen I replaced "gnome-wm" with "metacity"
using gconftool-2 as specified in the first message.
** Attachment added: "glxinfo"
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/673072/+attachment/1728960/+files/glxi
I just saw that problem in a normal, non-LTSP installation with:
01:00.0 VGA compatible controller [0300]: VIA Technologies, Inc. P4M890 [S3
UniChrome Pro] [1106:3343] (rev 02)
Kernel modules: viafb
If it's a problem with the "detect if compiz can run on that card" code, then
AFAIK it sh
Update OK on Lucid i386, chat fonts seem normal.
--
New Upstream Release 2.30.3
https://bugs.launchpad.net/bugs/623657
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to empathy in ubuntu.
--
desktop-bugs mailing list
desktop-bugs@lists.ub
Is a Lucid backport possible?
The bug is rated as critical, clicking on random points of the window
underneath the active one can cause anything, from loss of data to
security problems...
--
Clicking the title of a window is bringing a window underneath it into focus
https://bugs.launchpad.net/b
@Yannis T:
the method that you described didn't work for me in Lucid, here's a variant
that did work:
wget
http://www.ops.gr/Ergorama/fileUploads/ypiresiaops/prokirikseis/biografiko.zip
LANG=C 7z x -oPATH biografiko.zip
convmv -r --notest -f cp737 -t utf-8 PATH/*
Of course this is only a desper
*** This bug is a duplicate of bug 580961 ***
https://bugs.launchpad.net/bugs/580961
Rolf, thank you, I realized that some hours after I filed the bug, but I didn't
comment on it to minimize clutter.
Also thanks for your interest in fixing this.
--
Please reinclude the patch for codepage-ba
I've uploaded a patched gnome-session package in the Greek schools ppa.
Now the clients properly reboot/shutdown from gnome-panel or from iTalc.
Anyone interested may other add the ppa to his sources and update by doing
`sudo add-apt-repository ppa:ts.sch.gr && sudo apt-get update && sudo apt-ge
Heh, I've just noticed that the upstream bug description is essentially
the same as the way I reproduced it. :)
--
Clicking the title of a window is bringing a window underneath it into focus
https://bugs.launchpad.net/bugs/494096
You received this bug notification because you are a member of Ubu
I've manage to consistently reproduce it:
1) I have 2 windows open. One of them is "restored", i.e. not maximized neither
minimized. The state of the other window doesn't matter.
2) I double click on the title bar of the restored window to maximize it (the
problem doesn't happen if I click on the
I haven't tried the proposed patch, I just want to note something I
noticed today:
Maximized window underneath⎽☐☒
Non-maximized window on top ⎽☐☒
I tried to click on the close button of a not-maximized window. I saw
the close button of the maximized window underneath it getting
highlighted
LXDE has added upstream support for LTSP reboot/shutdown, using the same method
as the patch proposed here.
http://lxde.git.sourceforge.net/git/gitweb.cgi?p=lxde/lxsession;a=commit;h=d2508534100fddbac931fa60e3b989ae54ddf147
Thanks, pcman and vagrantc.
Maybe we'd have better luck trying upstream
why the reboot/shutdown menus in Ubuntu are not working, he may
find one in the PPA for Greek schools:
https://launchpad.net/~ts.sch.gr/+archive/ppa/
** Changed in: ltsp (Ubuntu)
Status: Fix Released => Confirmed
** Changed in: ltsp (Ubuntu)
Assignee: Alkis Georgopoulos (alki
;t used anymore, so
now those menus are there but are just performing "logoff" instead,
confusing the users.
So I'm not aware of any other realistic way to have working
shutdown/reboot menus in LTSP, other than the attached patch.
Kind regards,
Alkis Georgopoulos
Edubuntu/LTSP devel
Thank you, much appreciated.
--
Wrong keyboard settings when console-settings has multiple layouts
https://bugs.launchpad.net/bugs/460328
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.
--
desktop-bugs mailing list
deskto
Before Karmic, I didn't have to configure gnome at all (meaning, all the gconf
settings were working fine if they were empty).
Console-setup was configured to [us,gr], and X would pick it up and let me work
with it, and allow me to switch layouts, no matter if I used an xterm, gnome,
or kde sess
Yes, I believe that all the issues described here are caused by gdm,
which forces (in the gconf key) the first layout that it sees in
console-setup. Please mark it as a duplicate of bug #460328.
It'd be best if an ubiquity task was also registered in #460328, because
the new ubiquity (tested with
I'm attaching a script which should make the situation more bearable for
system admins.
To summarize the problem:
=
* In some countries, two layouts are needed by default.
* Console-setup correctly supports that, e.g. XKBLAYOUT='[us,gr]'.
* Gdm makes the wrong assumption
Yes, it is still an issue in current Lucid, exactly like I describe it
in comment #24, nothing has changed since.
I'd like to emphasize that in the default case, gdm *shouldn't* modify
the system-wide layout defined in /etc/default/console-setup. For me,
that's XKBLAYOUT="us,gr". Yes, two simultan
@mattrenfer: I don't think any graphics driver problems belong in this bug
report.
Please open another bug report for that.
For the teeworlds sound problem, an updated package has become available, so if
you update your system you should have working sound.
If not, please comment on
https://bug
> I can exit from TeeWorlds, which is a plus. But I cannot hear sound at
all now in TeeWorlds.
TeeWorlds has a packaging problem in Lucid, for which I've sent a patch but it
wasn't (yet?) integrated:
https://bugs.launchpad.net/ubuntu/+source/teeworlds/+bug/521633
Try starting with the live cd ag
Thanks, I've forwarded this upstream to
https://bugzilla.gnome.org/show_bug.cgi?id=612190
** Bug watch added: GNOME Bug Tracker #612190
https://bugzilla.gnome.org/show_bug.cgi?id=612190
** Changed in: evolution
Importance: Undecided => Unknown
** Changed in: evolution
Status: New =>
cided
Status: New
** Changed in: ltsp (Ubuntu)
Assignee: (unassigned) => Alkis Georgopoulos (alkisg)
** Changed in: ltsp (Ubuntu)
Status: New => Fix Released
--
Patch for LTSP clients to properly reboot/shutdown
https://bugs.launchpad.net/bugs/491940
You received this bug n
Public bug reported:
Binary package hint: evolution
I've been seeing this for the last 3 years, so it's a long standing bug.
Currently I'm reporting with evolution 2.28.3-0ubuntu3 / Lucid alpha 3.
Steps to reproduce:
1) Copy this email address:
Άλκης Γεωργόπουλος
2) Start writing a new mail an
Kangarooo, I'm not sure what you mean, but when right clicking the keyboard
layout icon, there's no "Properties" menu entry. See the attached picture.
Anyway the change was reverted so everything is OK for now.
** Attachment added: "keyboard-layout.png"
http://launchpadlibrarian.net/40223875/k
Hi Kangarooo, in which settings?
If you're talking about the gconf
/desktop/gnome/peripherals/keyboard/indicator/showFlags key, that doesn't take
effect anymore after today's changes.
The new keyboard icon seems to have replaced all the previous drawing code. It
doesn't even get to switch layou
Ugh for some reason after today's updates I'm seeing a keyboard icon instead of
the layout name.
Please put the layout name back...
--
The keyboard layout icon is empty
https://bugs.launchpad.net/bugs/524136
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, whic
As mentioned in https://bugzilla.gnome.org/show_bug.cgi?id=610544 by
Sergey, the problem can be solved by changing the font in
/desktop/gnome/peripherals/keyboard/indicator/fontFamily from
"Helvetica" to some other font like "Sans" that has a larger unicode
coverage.
Please include the fix for Luc
I tried to disable suspension of my laptop using the methods described
in comments #28 (Martin Pitt), #32 (Cédric Dufour) and #36 (Kjell L.),
but I was unable to. I rebooted after trying each method, but suspension
always worked from the indicator-session menu.
pkcheck --action-id org.freedesktop.
Public bug reported:
Binary package hint: gnome-settings-daemon
gnome-settings-daemon 2.29.90-0ubuntu1 (Lucid i386)
$ killall gnome-settings-daemon
$ LANG=en_US.UTF-8 gnome-settings-daemon
Result (OK): I see the new status icon, with [USA] and [Gre] as the
images.
$ killall gnome-settings-daem
I can confirm this. It started happening in 9.10 for me too, and it's
still happening on my freshly installed Lucid.
It's rather annoying because the "lost clicks" randomly affect the
applications below the focused window: they may e.g. close an
application by hitting its [X] button, or they may e
A much anticipated resolution!
Thank you Daniel :-)
--
libsdl1.2debian-pulseaudio must be installed as default by libsdl1.2debian
https://bugs.launchpad.net/bugs/203158
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs
I uploaded patched gnome-session packages for Lucid in my PPA. So if
anyone wants to test those 4 lines to verify that they solve the
reboot/shutdown problem for thin clients, he just needs to do:
sudo add-apt-repository ppa:ts.sch.gr/proposed &&
sudo apt-get update &&
sudo apt-get dist-upgrade
-
I read in LP #128447 that
* installing libsdl1.2debian-all instead of libsdl1.2debian-pulseaudio,
* and setting SDL_AUDIODRIVER=pulse in the environment
would have about the same results as installing libsdl1.2debian-pulseaudio.
I tried it and it works fine for me.
So maybe instead of requestin
I don't think the new title is appropriate.
Bug #269082 was marked as a duplicate of this one, because both of them
were requesting specifically for SDL to *use* PulseAudio by default, not
just to "work" when PulseAudio is also installed.
In other words: if libsdl1.2debian-alsa is fixed so that i
LDM_LOGOUT_ACTION has been renamed to the more generic
LTSP_LOGOUT_ACTION, in commit http://bazaar.launchpad.net/~ltsp-
upstream/ltsp/ltsp-trunk/revision/1481
So please use the following 4 lines instead:
+ if (g_getenv ("LTSP_CLIENT"))
+ g_spawn_command_line_async("xprop -root -f LTSP_LOGOUT_ACTI
Adding the applet may be an easy thing to do in single user systems,
but it isn't easy when you have hundreds of students in primary or even
secondary schools.
Please add the applet automatically when more than one keyboard layouts
are active.
--
No keyboard indicator applet shown after install
I'm putting gdm in the "Affects" list, as I think that it's a regression caused
by the new gdm that was introduced with Karmic.
Also, when I choose "Greek" in the gdm screen, I properly get a Greek layout,
but that's not the desired behavior, it should by default respect the system
settings.
So
Instead of g_spawn_command_line_async(), the following could also be
used:
gdk_property_change(gdk_get_default_root_window(),
gdk_atom_intern("LDM_LOGOUT_ACTION", FALSE), XA_STRING, 8,
GDK_PROP_MODE_REPLACE, (guchar *) "HALT", strlen("HALT"));
...but that would require #including some additional
In case anyone else wants to test this, I've uploaded updated packages for
gnome-session and LTSP (karmic) to this PPA:
https://launchpad.net/~ts.sch.gr/+archive/proposed
I've also uploaded a modified iTalc package there that calls
gnome.SessionManager.RequestReboot/RequestShutdown via dbus-send
I've uploaded in LTSP-upstream the necessary code to handle this xprop
from the LTSP side:
http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ldm-trunk/revision/1223
http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk/revision/1465
So if the patch above was accepted in gnome-session, LTSP cli
Public bug reported:
Binary package hint: gnome-session
Please consider the following 4 lines for inclusion to
debian/patch/95_dbus_request_shutdown.patch.
Those lines make LTSP clients properly reboot/shutdown.
gboolean
gsm_manager_request_shutdown (GsmManager *manager,
I've forwarded this to gnome:
https://bugzilla.gnome.org/show_bug.cgi?id=603285
** Bug watch added: GNOME Bug Tracker #603285
https://bugzilla.gnome.org/show_bug.cgi?id=603285
--
Regression: "Automatic proxy configuration" + gnome-terminal now breaks
apt-get, curl, wget...
https://bugs.launc
** Also affects: libsoup2.4 (Ubuntu)
Importance: Undecided
Status: New
--
Regression: "Automatic proxy configuration" + gnome-terminal now breaks
apt-get, curl, wget...
https://bugs.launchpad.net/bugs/433827
You received this bug notification because you are a member of Ubuntu
Desktop
Nathaniel thanks again for your input, and sorry for bothering you with
this.
I located the component that inserts that "pac+": it's libsoup-gnome2.4-1.
1) I ran `apt-get source libsoup-gnome2.4-1`
2) I modified "pac+" to "pac+debug" in libsoup/soup-proxy-resolver-gnome.c:
} else if (pr
I think that the "pac+" scheme is added by libproxy0:
>From libproxy/src/plugins/gnome.c:
// Mode is wpad:// or pac+http://...
else if (!strcmp(mode, "auto"))
{
char *tmp = gconf_client_get_string(client,
"/system/proxy/autoconfig_url", NULL);
Maybe I should post the command that I use to work around the problem,
to see if it helps other people here as well:
gconftool-2 --type list --list-type string --set
/desktop/gnome/peripherals/keyboard/kbd/layouts '[us,gr]'
Of course put the layouts for YOUR languages instead of [us,gr]
After th
I'm experiencing the same problem, and I am able to reproduce it even on
clean installations.
1) My layout is [us,gr]:
alk...@alkis:~$ grep XKBLAYOUT /etc/default/console-setup
XKBLAYOUT="us,gr"
2) I clear all my gnome keyboard settings, and logoff:
alk...@alkis:~$ gconftool-2 --recursive-unset
Yup, Panagiotis fixed the bug. A single line that gave people frustration for
more than 5 years!
Please get this into Karmic.
Let me say again that this affects *many* non-English languages (e.g. German,
French, Russian etc), not just Greek and Hebrew as the bug title says.
For anyone interested
Easy test case:
1) Open evolution and create a new mail
2) Edit > Current languages > verify that *any, but at least one*
dictionary, e.g. English is checked. You don't have to install the Greek
dictionary to see the problem.
3) Paste the following two lines:
a
α
Notice that both of them
This bug no longer occurs with the gnome-power-manager provided in
Ubuntu Jaunty 9.04, but I don't know exactly in which version it was
fixed, so I'm marking it as invalid.
** Changed in: ltsp
Status: New => Invalid
--
Server brightness popup window shown in clients
https://bugs.launchpad
This bug no longer occurs with the gnome-power-manager provided in
Ubuntu Jaunty 9.04, but I don't know exactly in which version it was
fixed, so I'm marking it as invalid.
** Changed in: ltsp (Ubuntu)
Status: Incomplete => Invalid
--
Server brightness popup window shown in clients
https:
Evgeny, you're good, you found out that there are two bugs, not one: one
concerning forward scanning of the text, and one concerning backward
scanning (like when you right click in the middle of a word and the
speller needs to find out the beginning and the end of the word).
You may get a better v
> the mistypes I have used for test while I had Greek dictionary installed are
> not shown in F7-run
Evgeny, perhaps you 've added them in the user dictionary?
Have a look at ~/.config/enchant
--
Broken context-sensitive spell check in Evolution (Greek, Hebrew)
https://bugs.launchpad.net/bugs/10
I got something more specific:
Cyrillic а = U+0430 => no suggestion
Cyrillic р = U+0440 => no suggestion
Cyrillic ф = U+0444 => suggestion
Look at the least significant bytes.
ASCII 30 = character 0 => not a letter
ASCII 40 = character @ => not a letter
ASCII 44 = character D => it's a letter
Th
Evgeny, I *did* try with Russian, with the words you posted above:
проверка русской арфографии
The first two words weren't underlined, the third one was.
But *it matters where you click* on the third word. If you click between:
ар => no (spell suggestion)
рф => yes
фо => yes
ог => no
гр => no
ра
It seems that *all* languages that contain non-ascii symbols are affected by
this.
E.g. write Hööörz and click on the middle ö. No spell suggestions.
But if you click on "H" or "rz", you get spell suggestions.
--
Broken context-sensitive spell check in Evolution (Greek, Hebrew)
https://bugs.laun
Spelling suggestion in Greek works for me under special circumstances,
i.e. in fake words like "αβγαnd", with English letters stacked right
before or after the Greek letters. And *only* when I click on these
English letters ("nd") do I get a spelling menu. I don't get a spelling
menu when I click o
see if all gtkhtml
apps are affected?
Kind regards,
Alkis Georgopoulos
--
Broken context-sensitive spell check in Evolution (Greek, Hebrew)
https://bugs.launchpad.net/bugs/10713
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
--
de
*** This bug is a duplicate of bug 10713 ***
https://bugs.launchpad.net/bugs/10713
I later saw that this bug is a duplicate of bug #10713
https://bugs.launchpad.net/ubuntu/+source/gnome-spell/+bug/10713
** This bug has been marked a duplicate of bug 10713
Broken context-sensitive spell che
or gtkhtml - can I check
some other application to see if it affects other gtkhtml-based apps?).
Right now the version of evolution I have is 2.24.0-0ubuntu2.
Kind regards,
Alkis Georgopoulos
** Affects: evolution (Ubuntu)
Importance: Undecided
Status: New
--
No spell
I don't know about the plugin, it's a hand-made minimal example to show the
developers that this line causes the problem:
/Differences [65 /B /C /D /Gamma]
When the text is not selected, the differences array is used, and evince
displays
BCDΓ
When the text is selected, the differences array is n
a ***minimal*** .pdf that reproduces this
bug.
If you open it in Evince and select all the text, the line that contains
BCDΓ
should display
ABC
when selected!
Kind regards,
Alkis Georgopoulos
** Attachment added: "evincebug.pdf"
http://launchpadlibrarian.net/16578432/evincebug.pdf
101 - 167 of 167 matches
Mail list logo
