Public bug reported:
this report is (probably) for either the ntp or the ntpdate package (since
those are the only two ntp related packages installed on my system).
this problem has been around for several iterations of ubuntu and is
still present in the Gutsy incarnation.
when using "settings fo
This is not a bug in the sense that some computer interpreted
instructions are wrong, but it still leads end users astray when
they try to use ubuntu/kubuntu/xubuntu for fun and profit.
By having at least some of the official servers listed we would
be able to provide a better end user experience.
I have a similar problem that has buggered me for the last few weeks
which I have now investigated a little bit more:
ubuntu-desktop, kubuntu-desktop, and xubuntu-desktop all depends on
slocate.
ubuntu-minimal is depending on findutils.
as a normal user probably likes to have one of the above me
As far as the description goes, this is probably not a bug.
Different operating systems, video adapters, and video
drivers all comes with their unique set of timing caracteristics.
To releive end users from constantly having to fiddle the
controls of their video monitors, the leading manufacturers
i have upgraded my system a few times and now i am not
able to reproduce this problem again.
neither with or without kvm.
i will get back _if_ things turn fishy again 8-)
--
cursor disappears frequently in latest Gutsy build
https://bugs.launchpad.net/bugs/140010
You received this bug notificat
sorry for not reporting back in time, it do work now without editing the
inetd.conf.
BTW are things supposed to work with xinetd as well?
--
ltsp-build-client and ltsp-update-image fails if inetd.conf is not cleared
https://bugs.launchpad.net/bugs/138204
You received this bug notification becaus
thank you Scott for your suggestions regarding LDM. Actually I have submitted
logfiles
and error messages for this problem in another bug report; unfortunately I am
not
friendly enough with the launchpad to figure out where, at least it is nowhere
to be
seen on my page with bugs that i have repo
i have tried ldm with several of my thin clients with no luck, with Gutsy,
ldm on feisty worked like charm :-)
i shall try to run more without kvm and report back, but beware:
as the computers are more or less unused while I am out working,
they may be "behind" screen saver all day. my personal th
to clarify upon what i said above:
when i first run into this problem on the 22th (saturday),
i had my screensaver configured to take over after
4 minutes of inactivity. after increasing this time to
10 minutes, the frequency of the problem decreased
drastically.
R.R.
--
cursor disappears frequ
two questions and accordingly two answers:
1. i have tried running without kvm during this day with the screen saver
active all day since i have not been home,
and no, i could not reproduce. but i do think this case is similar to when
running the kvm without switching
like i did above with disap
regardless if you run out of batteries or not, it is, at least in most cases,
stupid to let a background daemon take most of the computers internal
bandwidth. I am running this on my desktop machine and it is almost
useless for several hours after logging into the system. As I sure am
a geek and I
*** This bug is a duplicate of bug 132320 ***
https://bugs.launchpad.net/bugs/132320
no matter if it is beneficial or not having this trackerd track down every
single
bit in every file fast or not, it is definitely not good for anybody if your
systems
feels like you have upgraded to an 1 MHz
the best solution would be an inconsistent solution:
If and only if the user had selected any text, copy that text,
if no text is selected, pretend it is a normal console app and abort.
This will not cater for those cases when the user stumbles on
their mouse and accidentally select some random c
no Feisty fixed this issue for me.
as I now run Gutsy, I have got myself a brand new set of problems 8-)
--
desktop gets stuck when logging out
https://bugs.launchpad.net/bugs/82273
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
Public bug reported:
after doing the latest upgrade (to v 5.0.30 of ltsp-client)
I have been forced to reboot my primary workstation
(a hp 5x00 running ltsp) due to the fact that when I
leave the terminal the cursor disappears without comming
back when I start moving about with the mouse.
Since I
some aditional info:
as I am playing about with Gutsy, it seems like XFCE has started
to be a little bit more LTSP aware:
1. I still get all those confusing options, but now it begs me
for authentication (password) before it starts shutting down things.
2. I do not know if it wants password if I
As you might have already seen from my eager writings on defect #138089,
I do use "ltsp-build-client" from a clean startingpoint.
The interesting thing is that since I now use the CONFIGURE_X=True configuration
as you kindly suggested for #138089, I am not getting the error messages stated
above a
sorry for spamming you all, but if this is not clear from my abundant
reports above:
1. following the advice of Oliver G. above for setting the variable
CONFIGURE_X=True
manually works.
2. the default value for CONFIGURE_X in lts.conf created by ltsp-build-client
is still
CONFIGURE_X=False
And
regardless the quality of any defect report, it is pretty much useless if you
can not
track down which version/configuration that was used when finding the error.
As I have not figured out any better way of providing a complete report of the
system status regarding various packages, I hereby encl
Yes, I know, my previous post was not 100% related to the error report
at hand.
So here I enclose the dmesg output from using startx instead 8-)
Even if the session did start successfully I still get loads of interesting
messages
about various USB devices that should not really excite anybody.
since I got the message of using CONFIGURE_X=True I finally to the plunge and
went
looking for some problems again.
So I did the following steps:
1. removed my /opt/ltsp/i386 tree
2. ran ltsp-build-client (which of course had a few things to complain about
already
having nbdroot configured in i
still, if somebody for administrative reasons, needs to shut down a computer,
reasons ranging from planned power interruptions to office relocations,
it still is nice being able to let somebody shut down the computer in
an orderly fashion.
Hence, the problem was not that a shutdown option was pres
Oliver Grawert wrote:
> did you notice the CONFIGURE_X=False ? ;)
>
Well frankly, I did not have the slightest clue about
what did option actually did do, but as it was configured
this way when I had done my "ltsp-build-client" I did
not touch it.
Why not have a REALLY_SAFE_MODE=True which
refu
Oliver Grawert wrote:
> did you notice the CONFIGURE_X=False ? ;)
> drop that and X will be configured ...
> sorry, thats my fault, we worked initially with the self configuring feature
> of Xorg and omitted the configuration file, thats a leftover in the default
> file that has to go.
>
I may
Hi Jani,
no I am not running kiosk mode, I am running a small office.
But since I found this bug report while looking for something
else I figured that somebody might be interested in some information 8-)
Anyway, when running either gnome or kde, without any
special config, they both figure out t
Public bug reported:
When I run ltsp-build-client or ltsp-update-image, both fails if
the nbdrootd line for port 2000 is not removed.
This is not a big showstopper for me since quick jab with emacs
will help me around it, but I can imagine teachers without
much unix experience not knowing anythin
Public bug reported:
Binary package hint: ltsp-client
this may be related to #138089
when I first updated to Gutsy a few days back the ldm did not
manage to go from text mode to graphical mode on any of our
clients. Since I did not get many messages out of the process
of starting ldm I chose the
** Attachment added: "my lts.conf that tells all 8-)"
http://launchpadlibrarian.net/9188757/lts.conf
--
ltsp ldm does not start properly
https://bugs.launchpad.net/bugs/138200
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
out of pure evilness, I found out that most of the times (in my environment)
the clients survived a server reboot as long as they where at the login prompt.
I know this may not be 100% expected and that this neither may be the
intended way of doing things.
Best,
r.r.
--
rebooting ltsp server le
neither edgy, feisty, nor gutsy recognices that you are running a remote
session.
I can only imagine the horrors of a teacher running xubuntu at school.
with responsible and educated users this is a non issue, but well, the name
edubuntu tells something about some education that needs to be done
Oliver is perfectly right about the gdm, due to my present problems with
using ldm I am very much up to date on how to setup gdm 8-)
Best,
r.r.
--
LDM does not warn when a user is already logged in
https://bugs.launchpad.net/bugs/67366
You received this bug notification because you are a member
Well, to be able to use the startx option I actually have to edit
my lts.conf, otherwise I would never have come to the point
where the starting of X.org fails because there is no valid
configuration. Accordingly, I am enclosing my config file.
Another point of interest, is that if I do log on ma
Sorry guys, credit should be given where it is due:
James A. McQuillan seems to be the author of this
smashing little script.
Anyhow I added the following lines:
# Configure X.org
. /usr/lib/ltsp/configure-x.sh
so that the X.org gets configured before anything
tries to start any X-server.
Best
Public bug reported:
Binary package hint: ltsp-client
as I have problems logging in through ldm since it does not start X.org,
I tried configure
SCREEN_07=startx
in my lts.conf
Unfortunately the startx command got run without anything trying to
configure X.org this time either. So I am st
Dear Olivier,
as I am a very happy end user of the result of your effort making
LTSP a viable option for everyday usage, I have taken the step
upgrading to gutsy. If you need help in testing things I am more than
willing, but, as per how things are right now, ltsp is in an unusable
state on our ma
Public bug reported:
in the source package file:
ltsp-5.0.25/client/screen.d/startx
or if you rather look in your installed package:
/opt/ltsp/i386/usr/lib/ltsp/screen.d/startx
on line 59 there is an if-statement lacking the actual token "if"
add "if" and things will work much better.
** Affe
my changed file with the extra "if " added.
** Attachment added: "startx"
http://launchpadlibrarian.net/9130622/startx
--
xdmcp does not work due to syntax error in shell script
https://bugs.launchpad.net/bugs/137461
You received this bug notification because you are a member of Ubuntu
Bugs,
well, as I am now running Feisty on 3 machines, all with Swedish keyboard
selected,
I can now tell that my brother is right: it finally works!
The keyboard works as described both when using X11 and the console interface.
No need for configuring "Finnish" any more :-)
--
the swedish keyboard la
Roland Ronquist wrote:
> Timothy Smith wrote:
>> Can someone test this under a Feisty build so we can see if this bug
>> still exists?
>>
>> http://cdimage.ubuntu.com/ports/releases/feisty/herd-5/
>>
>
> I will test it this weekend; must burn a cd and di
Timothy Smith wrote:
> Can someone test this under a Feisty build so we can see if this bug
> still exists?
>
> http://cdimage.ubuntu.com/ports/releases/feisty/herd-5/
>
I will test it this weekend; must burn a cd and dig out
the bl*sting machine to test on :-)
Best,
R.
--
install CD does not
As far as I can see the bug is still there, and zip is showing the exact
same behaviour as unzip so maybe we should file yet another bug or stick
to killing 2 birds with one stone.
Maybe even a better suggestion is to go through all
packages and figure out what is needed for UTF-8
compatibility si
My brother installed Feisty and he got no problems
with his keyboard, but I am not sure if he selected
Swedish or if he autodetected the keyboard.
In the later case you will end up with "Finnish".
--
the swedish keyboard layout does not work as printed on the physical keyboard
https://launchpad.n
For your information, IBM says this about the Swedish and
Finnish keyboards that they have been selling for ages:
http://www-306.ibm.com/software/globalization/topics/keyboards/KBD285.jsp
http://www-306.ibm.com/software/globalization/topics/keyboards/KBD153.jsp
--
the swedish keyboard layout do
Having Ubuntu autodetect the "Finnish" layout when
using a Swedish keyboard may be good if you consider
the Finnish origin of Linux.
On the other hand, Linus Torvalds himself is speaking
Swedish as his mother tounge and there are twice
as many people speaking Swedish as those who
speak Finnish. He
Modern Linux distros, like Ubuntu, tend to prefer UTF-8 character
endcoding and legacy operating systems like Windows and Palm OS tend to
go for ISO 8859-1 character encoding when using a Swedish locale.
Some Ubuntu applications convert well (Open Office.Org, and some usually do
not, like Abi Wor
Well physically, Swedish and Finnish keyboards are exactly the same. Many
vendors do label their keyboards for the Swedish market as "Swe/Fi",
"Swedish/Finnish" or something similar. Other do have different labels even
though the actual keyboards do not
differ.
Look at IBM for instance, a well
Public bug reported:
Well I get a crash report from the xfce4-panel but, actually
my thin client locks up; mouse pointer gets stuck, keyboard
does not work etc; though I can log on through SSH so at
least the Linux kernel is working.
With earlier versions (and some specific options in lts.conf)
s
sorry, I have been fooling around a little bit with synaptics, it seems
like xkb-data could be another likely origin for this problem; as I said
I am not so well versed in the actual package layout of the Ubuntu
system since I am only a mere (and happy) user :-)
/r.
--
the swedish keyboard layou
Public bug reported:
Binary package hint: language-pack-sv
please forgive me, I may be barking at the wrong three (package):
language-pack-sv and language-pack-sv-base looks like the obvious
choices to me; but this may be something hidden deep in the soul of
linux:
Due to national pride all comm
Sorry for buggering you guys, but since I have been complaining,
I should also give some credit to you when the problem was not
your's.
Yes, as I said, I have not been able to get ltsp to work "out
of the box" on neither dapper nor edgy. But the problem
was in the sshd end, to many unsuccessful lo
Yes, in most cases we got the same keyboard layout
on all workstations at the same site. Hence that should
be a reasonable default. My first post was only to point
out the fact that all documentation that I have found on
this issue (regardless of LTSP version) has stated that
us keyboard should be
this non-existent lts.conf on a freshly configured system
(after running ltsp-build-client) can be very confusing
to the beginner. (yes, I have been one of them... )
The fact that there are several incompatible versions
of ltsp out in the wild on the internet makes googling
for answers a fruitless
I have got the exact same problem since upgrading from
Dapper. Since I have had insurmountable problems with
the ldm and I do not consider XDMCP being a local
security problem at our site. Hence I have been
doing without ldm until being forced by this problem
with Edgy Eft as described above.
In m
This keymap problem may be cumbersome to work out for many
users, but it still is an intended behaviour and not a bug.
When setting up the clients (/opt/ltsp/i386/etc/lts.conf if you are
running on an x86 processor), you are supposed to declare
which keyboard layout you want on the clients.
If the
yes, I have been searching the web intesively; even if this
is the first formal bug report, it seems like I am far from
the first one to find this problem.
On ubuntuforums, many users have similar experiences.
My belief is that many users consider this kind of old
"junk" more toys than actual too
Public bug reported:
I have tried this using anything from Ubuntu Breezy to Dapper Drake,
and several "flights" in between; unfortunately same problem all the time.
Both CD-R made on the lowest speed that my current system support (10x)
and factoru made dapper install CD:s.
Since this baby is a m
56 matches
Mail list logo
