thats pretty weird, since the ltsp-client-core initscript is supposed to
do this step before even starting the screen session. do you have a
manually created/modified lts.conf file ?
** Changed in: ltsp (Ubuntu)
Assignee: (unassigned) => Oliver Grawert
Status: New => Inco
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.
actually none of the options need to be s
did you just apt-get update/upgrade your cleint chroot for upgrading ?
thats unlikely to bring you all features, we switched to a completely new
underlying arcjhitecture for ltsp (no nfs anymore for example)
https://help.ubuntu.com/community/UbuntuLTSP/LTSPWithoutNFS has some info
if you just upgr
whats the error message and whats your ltsp version ?
the error message was turned into a warning with the 5.0.26 upload (see below)
ltsp (5.0.26) gutsy; urgency=low
[Oliver Grawert <[EMAIL PROTECTED]>]
* new udeb postinst (and new template) added, fixes (LP: #121547)
we hav
using
/var/run/ldm_socket and /var/run/ltspfs_fstab on clients.
(instead of a hidden socket and the clients real fstab)
* make binary-indep a no-op
* UVFe LP: #138048
-- Oliver Grawert <[EMAIL PROTECTED]> Fri, 07 Sep 2007 19:36:54 +0200
** Changed in: ltspfs (
in a second look, that code needs some mode modifications, will be fixed
in the next upload
--
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 because you are a member of Ubuntu
Bugs, which is the
*** This bug is a duplicate of bug 21507 ***
https://bugs.launchpad.net/bugs/21507
** This bug has been marked a duplicate of bug 21507
Disturbing sounds in Skyrocket screensaver
--
Sound in fireworks screensaver
https://bugs.launchpad.net/bugs/133538
You received this bug notification be
so it finally works, good to hear.
the fixed lts.conf isnt uploaded yet, i like to collect several fixes before
doing a new package.
with the next upload lts.conf will be fixed :)
--
ltsp startx option does not work since X.org is not configured
https://bugs.launchpad.net/bugs/138089
You recei
*** This bug is a duplicate of bug 138089 ***
https://bugs.launchpad.net/bugs/138089
** This bug has been marked a duplicate of bug 138089
ltsp startx option does not work since X.org is not configured
--
ltsp ldm does not start properly
https://bugs.launchpad.net/bugs/138200
You received
fixed in the 5.0.28 upload
** Changed in: ltsp (Ubuntu)
Status: In Progress => Fix Released
--
ltsp startx option does not work since X.org is not configured
https://bugs.launchpad.net/bugs/138089
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
fixed in 5.0.28
** Changed in: ltsp (Ubuntu)
Assignee: (unassigned) => Oliver Grawert
Status: New => Fix Released
--
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 because you
i'm seeing the same bug on a via apollo CLE266 based thin client as well
as on a SIS 550 based one now. setting the gconf key
/desktop/gnome/applications/window_manager forcefully to metacity works
around it for me.
--
[gutsy] cannot log in on edubuntu DesktopCD
https://bugs.launchpad.net/bugs/12
** Attachment added: "lspci of the via based client"
http://launchpadlibrarian.net/8633478/lspci_via.out
--
[gutsy] cannot log in on edubuntu DesktopCD
https://bugs.launchpad.net/bugs/122459
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact f
** Attachment added: "lspci of the sis based client"
http://launchpadlibrarian.net/8633757/lspci_sis.out
--
[gutsy] cannot log in on edubuntu DesktopCD
https://bugs.launchpad.net/bugs/122459
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact f
fixed in the 2.19.6-0ubuntu1 upload
** Changed in: gnome-screensaver (Ubuntu)
Assignee: (unassigned) => Oliver Grawert
Status: New => Fix Released
--
Please add this patch to pass gnome-keyring environement trought gdm
https://bugs.launchpad.net/bugs/128935
You received th
Public bug reported:
Binary package hint: linux-source-2.6.22
Many Thin Clients still only have oss supported sound hardware. With the
switch to 2.6.22 ubuntu stopped building oss device drivers. In LTSP we
have a mechanism to manually enable such drivers per client so they can
be blacklisted by
ltsp (5.0.22) gutsy; urgency=low
...
* Closes Launchpad bug 105709: updated 80_ltsp-sound to address unsafe
quoting.
...
** Changed in: ltsp (Ubuntu)
Status: In Progress => Fix Released
--
sound config not reset after thin client usage
https://bugs.launchpad.net/bugs/105709
You receiv
fixed in 5.0.23
** Changed in: ltsp (Ubuntu)
Status: Fix Committed => Fix Released
--
[Gutsy] LDM doesn't disconnect ssh on logout
https://bugs.launchpad.net/bugs/131259
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
u
** Bug watch added: GNOME Bug Tracker #436717
http://bugzilla.gnome.org/show_bug.cgi?id=436717
** Also affects: gnome-power (upstream) via
http://bugzilla.gnome.org/show_bug.cgi?id=436717
Importance: Unknown
Status: Unknown
--
[gutsy] brightness always appears after Idle
https://
hmm
ltsp (5.0.24) gutsy; urgency=low
* fix typo in ltsp-update-sshkeys (Closes LP# 133443)
-- Oliver Grawert <[EMAIL PROTECTED]> Sun, 19 Aug 2007 10:59:59 +0200
i was relying on the automatic bug closing mechanism here, seems that
didnt work...
--
ltsp-update-sshkeys produces
vagrant will want a switch :)
from my POV it could be a default.
--
[Gutsy] Proxy not working with ltsp-build-client
https://bugs.launchpad.net/bugs/132397
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing li
in ltsp5 ltspfs uses the ssh tunnel ldm establishes instead of the
internal xauth mechanism, the -a option is for backwards comaptibility
with ltsp 4.x only
** Changed in: ltsp (Ubuntu)
Status: New => Invalid
--
LTSPFS security is broken
https://bugs.launchpad.net/bugs/133635
You received
to do what ?
connecting to that port is pointless if you dont know the names and paths for
the exported filesystems ltspfsd is offering ...
--
LTSPFS security is broken
https://bugs.launchpad.net/bugs/133635
You received this bug notification because you are a member of Ubuntu
Bugs, which is th
** Changed in: ltsp (Ubuntu)
Status: Fix Released => Invalid
--
Needs to disable graphics-intensive modes for LTSP
https://bugs.launchpad.net/bugs/18595
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
u
exported displays. since fading is a bad idea anyway on LTSP
Clients its disabled completely now if LTSP_CLIENT is set.
-- Oliver Grawert <[EMAIL PROTECTED]> Mon, 20 Aug 2007 17:59:55 +0200
** Changed in: gnome-screensaver (Ubuntu)
Status: Confirmed => Fix Released
--
Needs t
** Changed in: ltsp (Ubuntu)
Target: tribe-5 => tribe-6
--
[Gutsy] LTSP chroot building process hangs at 50% on Tribe1 CD
https://bugs.launchpad.net/bugs/121547
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
reassigned to vesa, even though it might be an issue with teh via
driver, veas as fallback should always work.
** Also affects: xserver-xorg-driver-vesa
Importance: Undecided
Status: New
** Changed in: edubuntu-meta (Ubuntu)
Status: New => Invalid
--
failed load xorg on edubunt
Public bug reported:
Binary package hint: gdm
the session selector in gdm in feisty and gutsy shows an entry for
"XClient script". neither the tooltip nor the entry itself are intuitive
enough to even remotely understand what that would start
** Affects: gdm (Ubuntu)
Importance: Undecided
the proper solution would likely be that the client shuts down properly
as well *before* the server is gone ... we could achieve that by having
an ltsp-server initscript that is run on server shutdown and some yet to
be specced and designed function that can shut down the clients
remotely. marking
i'll happily mege any patches to make it build ...
--
There is no squeak-vm for amd64
https://bugs.launchpad.net/bugs/36806
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://
not really, but i'm currently tackling more basic probs and jetpipe is
lower down on my TODO list ... if anone wants to send me a proper patch
(or even better a bzr branch that has the fix) i'll happily merge it
--
jetpipe crashes on print
https://bugs.launchpad.net/bugs/110609
You received this
i rather meant moving teh close call out of the loop and have a
persistent socket ... indeed that makes more sense but needs some
development.
testing printing is in my personal testplan during edubuntu CD building, so yes
i tested it in feisty as well ...
after setting up the printer i:
a) pr
casper (Ubuntu)
Importance: Undecided => High
Assignee: (unassigned) => Oliver Grawert
--
edubuntu 2007.07.17.1 live cd's stay on gdm
https://bugs.launchpad.net/bugs/126735
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
casper (1.93) gutsy; urgency=low
.
* revert gdm-cdd.conf handling for autologin to the chrooted code
as we had it in feisty. not chrooting brings up problems with the
alternatives system (dead symlinks) used for gdm-cdd.conf
** Changed in: casper (Ubuntu)
Status: Fix Committed
Public bug reported:
Binary package hint: gdm
if you shut down from the gdm menu, gdm and X end.
then gdm respawns with the default gnome theme, sits there for a second and
only then starts the actual shutdown process.
thats on a system installed from edubuntu gutsy tribe3 candidate
** Affects
gnome-power-manager (2.19.92-0ubuntu2) gutsy; urgency=low
* turn -Wcast-align into -Wno-cast-align to work around LP: #138911
and fix ftbfs on sparc
-- Oliver Grawert <[EMAIL PROTECTED]> Wed, 12 Sep 2007 11:46:51 +0200
** Changed in: gnome-power-manager (Ubuntu)
Statu
added gstreamer since its header files seem to cause the FTBFS, build log here:
http://launchpadlibrarian.net/9151644/buildlog_ubuntu-gutsy-sparc.gnome-power-manager_2.19.92-0ubuntu1_FAILEDTOBUILD.txt.gz
--
Cannot install "ubuntu-desktop" on gutsy (kubuntu-desktop works) on SPARC
https://bugs.lau
fix is in my tree, waiting for some more merges before upload
** Summary changed:
- gutsy ltsp extremely slow login
+ SERVER variable not properly detected on nbdroot thin client setups
** Changed in: ltsp (Ubuntu)
Importance: Undecided => High
Assignee: (unassigned) => Oliver G
ltsp (5.0.29) gutsy; urgency=low
[Oliver Grawert <[EMAIL PROTECTED]>]
* fix setting of SERVER with nbd roots, closes LP: #139059
* remove screensaver handling from ldm, gnome-screensaver konws what to do
now
[Scott Balneaves <[EMAIL PROTECTED]>]
* enable compiz by defau
can you attach your /opt/ltsp/i386/etc/lts.conf ?
--
cursor disappears frequently in latest Gutsy build
https://bugs.launchpad.net/bugs/140010
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
[EMAIL PROTECTED]:~$ ldd /usr/lib/gnome-screensaver/gnome-screensaver-dialog
|grep pam
libpam.so.0 => /lib/libpam.so.0 (0xb7b01000)
its like that since we package gnome-screensaver ... we link against
libpam0g-dev ... probably recheck your pam changes ?
--
(gutsy) lock screen doesn't se
** Summary changed:
- (gutsy) lock screen doesn't seem to use pam
+ (gutsy) lock screen doesn't support fingerprint readers driven by thinkfinger
--
(gutsy) lock screen doesn't support fingerprint readers driven by thinkfinger
https://bugs.launchpad.net/bugs/138957
You received this bug notifica
are you sure you have version 5.0.28 or higher installed ? can you post the
output of:
dpkg -l ltsp-server
--
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 because you are a member of Ubuntu
Bu
yup
** Changed in: thin-client-manager (Ubuntu)
Status: Fix Committed => Fix Released
--
glade file links to wrong directory
https://bugs.launchpad.net/bugs/85541
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-b
you have a macbook and can confirm that LCD brigtness control on Thinkpads
doesnt work ???
please open a new bug for that.
--
[Feisty] Thinkpad (all models) LCD brightness control cycles between lowest
settings only
https://bugs.launchpad.net/bugs/81407
You received this bug notification becaus
which version of nbd-server is that ?
--
Segfault
https://bugs.launchpad.net/bugs/134572
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/lis
** Also affects: ltsp (Ubuntu)
Importance: Undecided
Status: New
--
when i run ltsp-update-image, it is aborted
https://bugs.launchpad.net/bugs/134586
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailin
since nbd-server runs from inetd here we should just add an /etc/default
/nbd-server file to the package and have a FROM_INETD (or so) variable
in there.
source that file from the initscript and exit if the variable is set.
--
Segfault
https://bugs.launchpad.net/bugs/134572
You received this bug
could it be that proc was still mounted in the chroot while you ran the
command ?
--
when i run ltsp-update-image, it is aborted
https://bugs.launchpad.net/bugs/134586
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
lets change:
+echo "/proc mounted in chroot ${CHROOT}, Exiting." && \
+exit 1
to be
+echo "/proc mounted in chroot ${CHROOT}, Unmounting." && \
+umount ${CHROOT}/proc
;)
--
when i run ltsp-update-image, it is aborted
https://bugs.launchpad.net/bugs/134586
You r
hmm, seems the -core package needs a
Replaces: ltsp-client (<< 5.0.7)
will fix in the next upload ...
** Changed in: ltsp (Ubuntu)
Assignee: (unassigned) => Oliver Grawert
Status: New => In Progress
--
ltsp-client-core update from feisty to gutsy failed
https://bugs.l
i'm not really sure where that file in /etc comes from as our package
explicitly removes it during build ... intrestingly dpkg claims it
belongs to the current package even though if you run a dpkg -c on the
.deb package you wont find it (and there is no maintainer script
installing anything like i
from /usr/share/doc/util-linux/changelog.gz
arch(1) is deprecated in favor of "uname -m" or arch(1) from coreutils
(>= 6.9+). The util-linux-ng package doesn't build arch by default,
you have to use the option --enable-arch.
--
/bin/arch missing
https://bugs.launchpad.net/bugs/135881
You rece
fixed in 5.0.25
** Changed in: ltsp (Ubuntu)
Status: Fix Committed => Fix Released
--
when i run ltsp-update-image, it is aborted
https://bugs.launchpad.net/bugs/134586
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ub
mksquashfs has a switch to disable using proc, marking as invalid
** Changed in: squashfs (Ubuntu)
Status: New => Invalid
--
when i run ltsp-update-image, it is aborted
https://bugs.launchpad.net/bugs/134586
You received this bug notification because you are a member of Ubuntu
Bugs, whic
fixed in 5.0.25
** Changed in: ltsp (Ubuntu)
Status: Fix Committed => Fix Released
--
copy of kiosk let ltsp-build-client fail
https://bugs.launchpad.net/bugs/114391
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubunt
first half is solved, i got a working prototype that needs to get waved
into teh udeb now
** Changed in: ltsp (Ubuntu)
Status: Confirmed => In Progress
--
[Gutsy] LTSP chroot building process hangs at 50% on Tribe1 CD
https://bugs.launchpad.net/bugs/121547
You received this bug notificati
no upgrades here when it showed
--
gdm spawns a new X server when told to restart the system
https://bugs.launchpad.net/bugs/126797
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
try to run ltsp-buuld-client with the --arch i386 option, see if that
helps
--
segfaults on ltsp in xen dom0
https://bugs.launchpad.net/bugs/134865
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
hmm, i should rather read all of the log before replying, setting arch
wont help, looks like x11-common has a bug in its postinst script here
...
--
segfaults on ltsp in xen dom0
https://bugs.launchpad.net/bugs/134865
You received this bug notification because you are a member of Ubuntu
Bugs, whi
** Summary changed:
- segfaults on ltsp in xen dom0
+ x11-common segfaults in ltsp chroot in xen dom0
--
x11-common segfaults in ltsp chroot in xen dom0
https://bugs.launchpad.net/bugs/134865
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
fixed in the 5.0.22 upload in gutsy
** Changed in: ltsp (Ubuntu)
Status: Confirmed => Fix Released
--
[ltsp] printer prints only once
https://bugs.launchpad.net/bugs/130472
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
turning that into a sync request, full changelog since 2.9.3-3 below,
archive team: please sync 2.9.6-1 from debian sid, all ubuntu changes
are merged upstream.
nbd (1:2.9.6-1) unstable; urgency=low
* New upstream (brown paper bag) release, that really fixes the segfault
this time.
ltsp (5.0.22) gutsy; urgency=low
...
* Closes Launchpad bug # 121254
** Changed in: ltsp (Ubuntu)
Status: Fix Committed => Fix Released
--
ldm only runs "ltspfsmounter all cleanup" when x-session-manager exits without
error
https://bugs.launchpad.net/bugs/121254
You received this bug
fixed in 5.0.22
** Changed in: ltsp (Ubuntu)
Status: Fix Committed => Fix Released
--
delayed_mounter not found
https://bugs.launchpad.net/bugs/127516
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
released with ltsp-client 5.0.22
** Changed in: ltsp (Ubuntu)
Status: In Progress => Fix Released
--
jetpipe crashes on print
https://bugs.launchpad.net/bugs/110609
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu
released in ldm 5.0.22
** Changed in: ltsp (Ubuntu)
Status: Fix Committed => Fix Released
--
ldm does not show any feedback on why login failed
https://bugs.launchpad.net/bugs/34118
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
This behavior got fixed with the edubuntu tribe 4 (7.10) desktop iso.
ubiquity now installs the complete live session desktop.
** Changed in: ubiquity (Ubuntu)
Status: New => Fix Released
--
Edubuntu Feisty Desktop CD install doesn't install the education suite
https://bugs.launchpad.net/
)
Assignee: (unassigned) => Oliver Grawert
Status: New => Invalid
--
Boot configuration setting not tagged as conffile
https://bugs.launchpad.net/bugs/131641
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs m
you need to make sure nbdroot=":" or
nbdport="" is set in the pxe default config if you change the
port so initramfs knows about it on boot ...
--
[gutsy] ltsp-build-client hangs
https://bugs.launchpad.net/bugs/127332
You received this bug notification because you are a member of Ubuntu
Bugs, wh
oh, and did you run ltsp-update-image afterwards ? thats the new command
to use in gutsy to rebuild teh nbd image we use now.
--
delayed_mounter not found
https://bugs.launchpad.net/bugs/127516
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact fo
did you update the client chroot (ldm and ltsp-client-core specifically
here) ?
--
delayed_mounter not found
https://bugs.launchpad.net/bugs/127516
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
)
Assignee: (unassigned) => Oliver Grawert
Status: New => Incomplete
--
ltsp-build-client restart X server of the host
https://bugs.launchpad.net/bugs/131580
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs m
i'm fine with being able to override defaults through config options,
but please dont start bothering teh user with questions if we dont get
options for something, we need to have a sane default instead.
--
[gutsy] ltsp-build-client hangs
https://bugs.launchpad.net/bugs/127332
You received this
IMAGE should be generated from the chroot name properly btw ...
--
[gutsy] ltsp-build-client hangs
https://bugs.launchpad.net/bugs/127332
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@lis
i dont think we should differ from gdm behavior here ... afaik it
automatically warns the user about an existing session with a dialog
that has a button saying "log me in anyway" and afaik its configurable
by the admin if the dialog is shown ... (i have to look, i may be wrong
here)
--
LDM does n
right, feel free to update the wiki if you like ;)
--
Boot configuration setting not tagged as conffile
https://bugs.launchpad.net/bugs/131641
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
: (unassigned) => Oliver Grawert
Status: Unconfirmed => In Progress
--
Screen blanks when watching movies
https://bugs.launchpad.net/bugs/66257
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubunt
well, fixed as far as the menitioned upstream patch goes at least :)
--
Screen blanks when watching movies
https://bugs.launchpad.net/bugs/66257
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-bu
a gpm package with a workaround was uploaded (2.18.2-0ubuntu2) but is
waiting for the release candidate archive freeze to end before it gets
accepted for build. it should be ready soon after RC is out.
** Changed in: hal (Ubuntu)
Status: Confirmed => In Progress
--
Logout screen appears t
i just got told that the proper hal fix is in 0.5.9 (which we dont have
in feisty yet), the link shall be:
http://gitweb.freedesktop.org/?p=hal.git;a=commitdiff;h=f30d5efd1458cc43ec90563ea4028a26fdef7689
--
Logout screen appears twice [Feisty]
https://bugs.launchpad.net/bugs/81227
You received th
no changes in ltsp required
** Changed in: ltsp (Ubuntu)
Status: Confirmed => Rejected
--
[Feisty] LTSP fails on multi-homed server due to network manager touching
predefined static interfaces
https://bugs.launchpad.net/bugs/100021
You received this bug notification because you are a mem
Public bug reported:
if you log in directly on an ltsp server after having used a thin client
on the same server with the same account, the login hangs, apparently
gnome-session cant handle a virtual alsa device that has no backend
connected, a workaround is to use the ltsp-sound script to unset t
Public bug reported:
Binary package hint: debian-installer
in edgy the grub installer used to tell me there is another OS installed
and offered me a dialog (with no input fields) to install grub to the
mbr. in feisty (i386/amd64 edubuntu server) i dont get that dialog, it
seems the existig OS isn
did you use feisty from any herd CD to install ? there was a bug in an
early release of this package where the wrong (debians udev file) file
was installed as /etc/udev/rules.d/40-fuse.rules. the correctd package
in feisty (2.6.3-1ubuntu2) should supply this file corerected with a
sequence number o
even after logging out/in or restarting ? note that after an uipgrade
the old binary still runs in memory
--
Logout screen appears twice [Feisty]
https://bugs.launchpad.net/bugs/81227
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
** Changed in: linux-restricted-modules-2.6.20 (Ubuntu)
Sourcepackagename: gnome-screensaver => linux-restricted-modules-2.6.20
--
[feisty] "black screen" is not black
https://bugs.launchpad.net/bugs/105836
You received this bug notification because you are a member of Ubuntu
Bugs, which is the b
i use an identical testing scheme since breezy, it didnt happen in any
of the former releases if i used manual patitioning and disabled the use
of any of the existing partitions in the partitioner which is always the
first install test i do after exactly the same scheme ... it happens for
i386 and
can everybody who still sees it attach the output of lshal -m while pressing
the power button ?
currently g-p-m is set to ignore all events from and
uid=/org/freedesktop/Hal/devices/acpi_PWRF and only accept the ones from input
devices.
--
Logout screen appears twice [Feisty]
https://bugs.lau
ivoks: no, thats not related ...
+ if (strcmp (type, GPM_BUTTON_POWER) == 0 && \
+ strcmp (udi, "/org/freedesktop/Hal/devices/acpi_PWRF")
== 0) {
+ gpm_debug ("ignoring acpi event in favor of inputdevice event");
+ return;
+ }
+
as you
this doesnt happen with any other graphics driver, not a gss bug, please
file it against the xserver or driver
** Changed in: gnome-screensaver (Ubuntu)
Status: Confirmed => Rejected
--
[feisty] "black screen" is not black
https://bugs.launchpad.net/bugs/105836
You received this bug notif
ati/fglrx, via, sis, s3 and mga, pick one
--
[feisty] "black screen" is not black
https://bugs.launchpad.net/bugs/105836
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[EMAIL PROTECTED]
https://li
i noticed that it takes about a second to draw the screensaver window
inside the gtk window though ... are you sure its not just showng up a
bit delayed ?
--
[feisty] "black screen" is not black
https://bugs.launchpad.net/bugs/105836
You received this bug notification because you are a member of
the final fix will be in hal 0.5.9 in feisty+1 closing with workaround
in g-p-m
gnome-power-manager (2.18.2-0ubuntu3) feisty; urgency=low
.
* fix #81227 harder by matching all acpi power buttons instead of only
these which have an udi with acpi_PWRF
** Changed in: hal (Ubuntu)
St
the ltsp issue is fixed (see bug 100021) with NM respecting static
devices in /etc/network/interfaces again
--
NetworkManager does not allow more than one active NIC
https://bugs.launchpad.net/bugs/96103
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
*** This bug is a duplicate of bug 22930 ***
https://bugs.launchpad.net/bugs/22930
** This bug has been marked a duplicate of bug 22930
Newly-sensitive button ignores clicks until cursor re-enters it
--
forward button problem on hardware database
https://bugs.launchpad.net/bugs/102860
You
creating a proper user on the server and using the matching credentials used
there for LDM_USERNAME/PASSWORD works fine here, i cant reproduce that, sorry
whats happening in /var/log/auth.log if you try to run a client with autologin
?
** Changed in: ltsp (Ubuntu)
Status: New => In
neither human-themes nor human-cursor-themes should be in there ...
whats the version of ltsp-server you have installed (seems your plugin set is
very outdated)
--
[Gutsy] Proxy not working with ltsp-build-client
https://bugs.launchpad.net/bugs/132397
You received this bug notification because
hmm, you should at least see the username in auth.log with either successfull
or failed login, the daemon.log entries are totally fine but dont refer to the
login process at all.
what happens if you enable LDM_USERNAME and LDM_PASSWORD and if you set
LDM_SERVER=192.168.0.254 ?
--
autologin do
i would think thats a udev probelm rather than a pmount one, whats the
exact device you need the disk group for ? if its distinctly owned by
cameras and video devices we could easily add a rule to make it owned by
the video group, if its not exclusively a camera and video device that
might get a mo
801 - 900 of 3807 matches
Mail list logo
