Public bug reported:
Binary package hint: redboot-tools
redboot tools is needed by flash-kernel on the imx51 architecture to
make installed systems bootable and make kernel/initramfs upgrades work.
it urgently needs to be included into main.
the main inclusion report is at
https://wiki.ubuntu.co
the env vars should be exported by unr-launcher though (instead of
ubuntu-netbook-remix-default-settings), since thats the cause why
composite cant be used, this will also prevent users that install the
launcher separately from the archive from running into the issue
--
usage of notify-osd with m
Public bug reported:
Binary package hint: ubiquity
ubiquity currently does not install an equivalent to the d-i in-target command.
scripts like flash-kernel-installer which usually live in udebs call in-target
for configuration purposes though, so ubiquity should provide in-target or
something
** Attachment added: "Casper.gz"
http://launchpadlibrarian.net/24702141/Casper.gz
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/24702143/Dependencies.txt
** Attachment added: "UbiquityDebug.gz"
http://launchpadlibrarian.net/24702145/UbiquityDebug.gz
** Attachmen
** Attachment added: "lshal.out"
http://launchpadlibrarian.net/24927846/lshal.out
--
udev does not detect eth0 on armel
https://bugs.launchpad.net/bugs/356517
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing li
Public bug reported:
several networking probs on imx51 made me look at dmesg output and
showed an oops directly after the watchdog call on eth0
ProblemType: Bug
Architecture: armel
DistroRelease: Ubuntu 9.04
Lspci:
Error: command ['lspci', '-vvnn'] failed with exit code 1: pcilib: Cannot open
/
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/24931262/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/24931263/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/24931264/Dependencies.txt
** A
the testing here additionally exposed bug 356975
--
udev does not detect eth0 on armel
https://bugs.launchpad.net/bugs/356517
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https
cat /proc/net/dev shows eth0 is existing
sudo ifconfig eth0 up && sudo dhclient eth0
get the interface up properly and assign a dhcp IP ...
--
udev does not detect eth0 on armel
https://bugs.launchpad.net/bugs/356517
You received this bug notification because you are a member of Ubuntu
Bugs, wh
** Attachment added: "syslog"
http://launchpadlibrarian.net/24931191/syslog
--
udev does not detect eth0 on armel
https://bugs.launchpad.net/bugs/356517
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubu
above is the lshal output, i'd like to notice that NM works fine with any wired
USB NIC i attach.
it used to work before with the onboard card (sadly i cant say since when it
changed, there were issues with the payload stability of the onboard driver so
i used USB NICs since a while)
--
udev
ARM boards dont expose a PCI bus (if they even have one) (lscpci on arm is
usually a no-op) so the parent is right here ...
and as i said, it used to work before ...
--
udev does not detect eth0 on armel
https://bugs.launchpad.net/bugs/356517
You received this bug notification because you are a
** Changed in: linux (Ubuntu)
Importance: Undecided => High
--
imx51 oops after watchdog call
https://bugs.launchpad.net/bugs/356975
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu
rebuilding NM with the lp199140_dont_manage_virtual_devices.patch
unapplied makes it work
** Also affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
** Changed in: network-manager (Ubuntu)
Importance: Undecided => High
** Changed in: network-manager (Ubuntu)
Mil
** Attachment added: "dmesg.txt"
http://launchpadlibrarian.net/25017379/dmesg.txt
--
mmcblk0p* don't appear in /sys/block
https://bugs.launchpad.net/bugs/357700
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
** Attachment added: "casper.log"
http://launchpadlibrarian.net/25035886/casper.log
--
Long timeout when trying to mount empty USB to SATA adapter
https://bugs.launchpad.net/bugs/357690
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
NM was compiled in a way that it doesnt ignore virtual devices (our eth0
isnt attched to USB or PCI, so NM currently ignores it)... after
enabling support for devices attached to teh virtual bus in hal (bug
356517) the oops showed up.
running "sudo ifconfig eth0 up" and "sudo dhclient eth0" in a t
gnome-keyring-daemon hangs in --start and never forks to a --daemonize --login
process
sockets for ssh and pkcs11 dont show up in the socket dir
running gnome-keyring-daemon --daemonize --login from a terminal does not
result in 100% CPU usage but still leaves me without more than
/tmp/keyring
i tested with --start --components=ssh as well as --start
--components=pkcs11, neither of them got further in the process so i
assume its not the fault of the backend components
--
[arm] gnome-keyring-daemon eating 100% CPU at login in Jaunty
https://bugs.launchpad.net/bugs/328167
You received th
confirming that the rebuild with -O1 works around the issue
--
[arm] gnome-keyring-daemon eating 100% CPU at login in Jaunty
https://bugs.launchpad.net/bugs/328167
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing l
boot-tools (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: redboot-tools (Ubuntu)
Assignee: (unassigned) => Oliver Grawert (ogra)
--
no way to create initial bootloader configuration on imx51 images
https://bugs.launchpad.net/bugs/348060
You received this bug notification b
fixed with new flash-kernel-installer.postinst code
** Changed in: flash-kernel (Ubuntu Jaunty)
Status: New => Fix Released
--
ubiquity unsets ubiquity/install_bootloader=false at some point during
installation
https://bugs.launchpad.net/bugs/348660
You received this bug notification bec
Public bug reported:
Binary package hint: initramfs-tools
if update-initramfs runs on the ARM architecture, namely on a system
that uses the flash-kernel tool to update kernels and initramfs, there
is no flash-kernel run after update-initramfs finished (i.e. if you
install udev) ... a hook needs
@daniele, did you test this patch ? even though i got the bug assigned
(because i did the last upload of this package during a merge), i dont
own a single irda device to test it. if you can positively confirm it
doesnt introduce any regressions i'm happy to upload it.
--
[Jaunty] modprobe require
the suspend and hibernate options are deliberately omitted in all menus
of the ubuntu desktop as soon as you are logged in from a thin client,
how did you manage enable this mode ?
--
ltsp-client: crash on activating standby modes
https://bugs.launchpad.net/bugs/310251
You received this bug notif
note that we kept the kernel small enough on the nslu2 to finish the
partitioning (if it doesnt, thats indeed a bug). if you select to create
swapspace in the partitioning step the installer will immediately use it
after it created it. so going to the shell should not be necessary.
--
Problems In
*** This bug is a duplicate of bug 203954 ***
https://bugs.launchpad.net/bugs/203954
note that the amd64 CD has no i386 packages available
--
Jaunty: ltsp dhcp.conf on 64bit points to i386 not amd64
https://bugs.launchpad.net/bugs/361940
You received this bug notification because you are a m
*** This bug is a duplicate of bug 203954 ***
https://bugs.launchpad.net/bugs/203954
if you commit that you break all amd64 installs that actually use amd64
clients (yes, we had several in the past years)
** This bug has been marked a duplicate of bug 203954
amd64 server installation has w
as i said in our conversation back thzen, this breaks the CD install for
users with amd64 server and clients we discussed that several times at
several UDSes and teh conclusion was to not change it until we can
actually build i386 chroots by default from an amd64 CD install (even
though it sounds f
** Attachment added: "slug-dmesg.txt"
http://launchpadlibrarian.net/25607528/slug-dmesg.txt
--
ixp4xx hwclock command stopped to work since beta release
https://bugs.launchpad.net/bugs/353196
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
o...@lkgd7f5b4:~$ ls /dev/rtc*
ls: cannot access /dev/rtc*: No such file or directory
--
ixp4xx hwclock command stopped to work since beta release
https://bugs.launchpad.net/bugs/353196
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
from a fresh RC install
o...@lkgd7f5b4:~$ sudo hwclock --show
Cannot access the Hardware Clock via any known method.
Use the --debug option to see the details of our search for an access method.
o...@lkgd7f5b4:~$ sudo hwclock --debug
hwclock from util-linux-ng 2.14.2
hwclock: Open of /dev/rtc
the last alpha i tested before reporting the bug with beta was alpha5
iirc
--
ixp4xx hwclock command stopped to work since beta release
https://bugs.launchpad.net/bugs/353196
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bug
you change a lot more than needed in your patch ... please change only
the actually requested filename
--
[Jaunty] modprobe requires .conf filenames now
https://bugs.launchpad.net/bugs/340873
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
do you have anything but the "lo" device added to
/etc/network/interfaces ?
--
Regression: network-manager sometimes doesn't detect wireless network; race
https://bugs.launchpad.net/bugs/362340
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
something similar to teh above should suffice for a start, problematic
seems to me that update-initramfs -c (creating an initramfs from
scratch) doesnt call a bootloader at all, the run_bootloader() function
is only executed when update-initramfs is called with -u ... though the
same problem is tru
--- /usr/sbin/update-initramfs 2009-03-13 10:57:32.0 +0100
+++ update-initramfs2009-04-10 13:25:25.0 +0200
@@ -184,6 +184,12 @@
lilo
}
+# call flash-kernel
+run_flash_kernel()
+{
+ flash-kernel
+}
+
# check if lilo is on mbr
mbr_check()
{
@@ -262,6 +268,9 @@
confirming the debian fix works fine (tested with apt-get install
--reinstall udev)
--
update-initramfs trigger should run flash-kernel
https://bugs.launchpad.net/bugs/358762
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bug
given that it only shows up if the device is used by NM and a fix for
bug 356517 is pending upload it should be reproducable soon.
--
imx51 oops after watchdog call
https://bugs.launchpad.net/bugs/356975
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
while this is a working workaround, the cause why the file is created
with 000 permissions at all still isnt clear, it would be helpful to dig
deeper here to find the actual bug and fix.
afaik the initscript only creates a resolv.conf if DNS_SERVER and
SEARCH_DOMAIN are set in lts.conf, the creati
in the ltsp-setup initscript i see:
if [ -z "$root_write_method" ]; then
touch / 2> /dev/null || root_write_method="bind_mounts"
fi
[ "$root_write_method" = "bind_mounts" ] && bind_mounts
...
can somebody seeing the issue attach the output if "cat /proc/mounts"
the touch command should probably try to touch a file from the bindfiles
variable instead of trying to touch /
--
jaunty /etc/resolv.conf in chroot has permission-rights 000
https://bugs.launchpad.net/bugs/348305
You received this bug notification because you are a member of Ubuntu
Bugs, which is
worked fine for me with a recent daily on a std slug, did you make sure
to pick swap on the target device during partitioning (else it will
indeed stop right after this step, swap is essential) ?
--
Problems Installing Jaunty On NSLU2
https://bugs.launchpad.net/bugs/336770
You received this bug n
did you use the same NM version with the mentioned patch included to verify
that.
can you please attach more data if you make such assumptions...
if the device is not attached to the computer device in hal, where and how is
it attached in the monolithic 2.6.26 kernel ?
--
NetworkManager does n
the actual fix is to exclude ltsp-client and ldm at build time from
adding their translations to the langpack packages and include all
translations in the ldm/ltsp-client packages directly, there is an easy
fix for this on a packaging level afaik.
--
No LANG set in the chroot (missing /etc/defaul
this seems also to be the case under gdm (moving the mouse to the bottom
right corner makes a white stripe show up at the bottom of the screen)
--
armel Babbage iMX51 line truncation and addition on VGA output
https://bugs.launchpad.net/bugs/358956
You received this bug notification because you a
also looking at the console it seems there is a similar offset, so i
would assume the probelm to be in the linux framebuffer driver itself.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
armel Babbage iMX51 line truncation and addition on VGA output
https://bugs.launchpad.net/b
here are the actual mode settings used for the frambuffer device
o...@babbage:~$ sudo fbset
mode "800x600-60"
# D: 40.000 MHz, H: 37.879 kHz, V: 60.317 Hz
geometry 800 600 800 600 16
timings 25000 88 40 23 1 128 4
hsync high
vsync high
rgba 5/11,6/5,5/0,0/0
endmode
--
arm
i re-ran the install and made sure to only select ext4 this time. i did
get a proper message saying that because i didnt pick to format the
partition, files and directories would be deleted prior installing.
after the interactive part of ubiquity the complaint about /cdrom being
unmountable showed
** Attachment added: "partman.gz"
http://launchpadlibrarian.net/24479068/partman.gz
--
ubiquity does not allow to install to pre-partitioned, pre-formatted device if
the device contains the live filesystem
https://bugs.launchpad.net/bugs/349581
You received this bug notification because you
** Attachment added: "syslog.gz"
http://launchpadlibrarian.net/24479065/syslog.gz
--
ubiquity does not allow to install to pre-partitioned, pre-formatted device if
the device contains the live filesystem
https://bugs.launchpad.net/bugs/349581
You received this bug notification because you ar
** Attachment added: "debug.gz"
http://launchpadlibrarian.net/24479073/debug.gz
--
ubiquity does not allow to install to pre-partitioned, pre-formatted device if
the device contains the live filesystem
https://bugs.launchpad.net/bugs/349581
You received this bug notification because you are
** Attachment added: "USB-errors-syslog"
http://launchpadlibrarian.net/24522199/USB-errors-syslog
--
USB issues with linux-image-2.6.28-11-imx51 fill /var/log
https://bugs.launchpad.net/bugs/348504
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
this is the snippet used in the initial builder script for the live
image, cmdline needs to be changed to use a UUID, fis needs to be used
to determine the actual offset (both are hardcoded values in the image
build script), the dd'ing of the binary blob doesnt need to happen, i'll
rework this bit
here the snippet from the babbage install guide wikipage, a script similar to
the above code needs to go into flash-kernel-installer
--
Now you need to make your SD card a boot device (the babbage currently only
boots from SD) to achieve this, do the following:
Download the redboot tools package
here is a patch that does the necessary bits, though loic just fixed the
need for $initramfs_size which means it will need to be reworked a bit
...
--- flash-kernel-2.13ubuntu2/debian/flash-kernel-installer.postinst
2009-03-31 11:22:17.0 +0200
+++ flash-kernel-installer.postinst 2
** Attachment added: "flash-kernel-installer.patch"
http://launchpadlibrarian.net/24585604/flash-kernel-installer.patch
--
Please add support for the imx51 ARM subarchitecture.
https://bugs.launchpad.net/bugs/345534
You received this bug notification because you are a member of Ubuntu
Bugs, w
i see it on a GM965/GL960, but as for Chris it goes away for me if i
disable compiz.
--
[intrepid] X locks up or crashes when screensaver activates
https://bugs.launchpad.net/bugs/262605
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
following https://wiki.ubuntu.com/MobileAndEmbedded/ImageModification i
see the same behavior in a chrooted call of "apt-get update"
--
`apt-get update` hangs indefinitely when run against the ubuntu-mid daily images
https://bugs.launchpad.net/bugs/264048
You received this bug notification becaus
on a sidenote kill -9 against the process doesnt work either ...
--
`apt-get update` hangs indefinitely when run against the ubuntu-mid daily images
https://bugs.launchpad.net/bugs/264048
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
-
execve("/usr/bin/apt-get", ["apt-get", "update"], [/* 19 vars */]) = 0
brk(0) = 0x8237000
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
mmap2(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb7f34000
access("
the above strace triggered me to look into /var/lib/apt/lists/ ... a
simple ls /var/lib/apt/lists/ reproduces the hang, it seems to be a
filesystem problem (even sudo ls -al /tmp/mergemount/var/lib/apt/
exposes that)
--
`apt-get update` hangs indefinitely when run against the ubuntu-mid daily ima
both uploaded to hardy-proposed now ...
** Changed in: cmpc
Status: New => In Progress
** Also affects: cheese (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cheese (Ubuntu)
Status: New => In Progress
** Also affects: gstreamer0.10 (Ubuntu)
Importance: Unde
correction, teh cheese versioning needs to be ubuntu1.1, debdiff is at
http://people.ubuntu.com/~ogra/cheese_2.22.3-0ubuntu1.1.debdiff
--
Camera application cannot record video
https://bugs.launchpad.net/bugs/258110
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Public bug reported:
Binary package hint: xorg
using Xorg -configure in intrepid breaks with an undefined symbol:
xf86GetPciVideoInfo message as below:
[EMAIL PROTECTED] sudo Xorg -configure :2
This is a pre-release version of the X server from The X.Org Foundation.
It is not supported in
this is on a ltsp client which simply installs the xorg metapackage
(depending on xserver-xorg which in turn pulls in xserver-xorg-video-
all).
--
Xorg -configure breaks on undefined symbol: xf86GetPciVideoInfo
https://bugs.launchpad.net/bugs/265035
You received this bug notification because you
ths looks like you try to install ltsp-client-core directly ... its not
intended to and this is not a bug. it fails to install deliberately and should
have shown your a debconf message that it cant be installed on a normal system
(if that has not been shown please re-open)
ltsp-client-core descr
updated short description, linked ot the right downstream package in
ubuntu and to the LTSP upstream product ... and confirmed ...
** Changed in: ldm (Ubuntu)
Sourcepackagename: ltsp => ldm
Importance: Undecided => Wishlist
** Summary changed:
- LTSP Clients do not offer option to set selecte
removing the vga driver helps a bit, but it chokes on the -nsc driver
now (same error message), removing that one as well makes Xorg
-configure work as expected again.
--
Xorg -configure breaks on undefined symbol: xf86GetPciVideoInfo
https://bugs.launchpad.net/bugs/265035
You received this bu
yes, but that patch also needs the gstreamer fixes that were uploaded...
as outlined on https://wiki.ubuntu.com/StableReleaseUpdates both packages wait
for the quarantaine to expire and two positive comments from testers.
feel free to install them on an image from the hardy-proposed repository an
all in the archive now ...
** Changed in: ubuntu
Importance: Wishlist => Undecided
Status: Confirmed => Fix Released
--
Please package applications from netbook-remix
https://bugs.launchpad.net/bugs/263493
You received this bug notification because you are a member of Ubuntu
Bugs, whic
this is fixed in the upstream ldm branch since ldm was rewritten in the
ssh communication layer
** Also affects: ldm (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ltsp
Status: New => Invalid
--
LDM in Hardy not expiring passwords correctly
https://bugs.launchpad.net
confirming and tagging for hardy SRU
** Changed in: ldm (Ubuntu)
Status: New => Confirmed
** Changed in: ldm (Ubuntu Hardy)
Status: New => Confirmed
--
LDM in Hardy not expiring passwords correctly
https://bugs.launchpad.net/bugs/268550
You received this bug notification because y
hmm, needs actually be set to fix released for intrepid, since that uses
the new upstream code
** Changed in: ldm (Ubuntu)
Status: Confirmed => Fix Released
--
LDM in Hardy not expiring passwords correctly
https://bugs.launchpad.net/bugs/268550
You received this bug notification because y
** Description changed:
Binary package hint: banshee
- currently banshee dies a painful dead on armel devices, below is a log
- captured with:
-
- banshee >banshee.log 2>&1
-
- i will add more debugging info soon...
-
- [Info 14:50:57.585] Running Banshee 1.4.3: [Ubuntu karmic (developmen
** Attachment added: "banshee_debug.txt"
http://launchpadlibrarian.net/28884026/banshee_debug.txt
--
banshee fails to run on arm
https://bugs.launchpad.net/bugs/391588
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs m
Public bug reported:
Binary package hint: gcc-4.4
in
https://edge.launchpad.net/ubuntu/+source/upstart/0.6.0-2/+build/1112005/+files/buildlog_ubuntu-karmic-armel.upstart_0.6.0-2_FAILEDTOBUILD.txt.gz
we see that the buidd appears to time out (in reality its hiding the actual
error).
building tha
different place of the error in a different system with a local build,
it seems to be closely related to the hardware gcc is running on ...
gcc -std=gnu99 -DHAVE_CONFIG_H -DLOCALEDIR="\"/usr/share/locale\"" -I.. -I..
-iquote. -iquote. -I../intl -I/usr/include/dbus-1.0
-I/usr/lib/dbus-1.0/incl
downgrading my local buildsystem to gcc-4.3 i see similar issues
--
gcc-4.4 fails to build upstart 0.6 on armel due to an internal compiler error
https://bugs.launchpad.net/bugs/398403
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
i doubt that its a memory issue and i see it on all SoCs here
i will try building gcc-snapshot and see if it occus with that too ...
for both SoCs i have here, i only have binary kernels, it might be cause by
some ulimit issue ...
there should be enough swap here and the system is running (and
s
** Attachment added: "qemu-kvm_0.11.0~rc1-0ubuntu2.debdiff"
http://launchpadlibrarian.net/29928663/qemu-kvm_0.11.0%7Erc1-0ubuntu2.debdiff
--
please build a static version of qemu-arm 0.11.x in a separate binary deb
https://bugs.launchpad.net/bugs/401782
You received this bug notification beca
note that the same occurs on imx51
--
armel/versatile: unknown HZ value 94
https://bugs.launchpad.net/bugs/364656
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubu
why did you replace jetpipe ? jetpipe changed massively between hardy (8.04)
and jaunty (9.04).
the changes in bug 224259 *only* apply to hardy (8.04)
the lts.conf settings of your second example are from ltsp4.x and dont apply at
all to ltsp5.x as used in ubuntu.
please use the most recent ups
this bug was fixed long ago
** Summary changed:
- ltsp-build-client ignores --base option
+ ltsp-update-image ignores --base option
** Changed in: ltsp (Ubuntu)
Status: Incomplete => Fix Released
--
ltsp-update-image ignores --base option
https://bugs.launchpad.net/bugs/130047
You rec
Public bug reported:
Binary package hint: qemu
qemu 0.11 is supposed to have eabi support in qemu-arm. to easily use a
an armel chroot under x86 similar to the variant described in
https://wiki.ubuntu.com/ARM/BuildEABIChroot the following is necessary:
1) register qemu-arm(-static) with binfmt m
** Also affects: ltsp (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ltsp
Status: New => Invalid
--
Kernel Panic on Clients using Ubuntu 9.04 Jaunty
https://bugs.launchpad.net/bugs/401878
You received this bug notification because you are a member of Ubuntu
Bugs, whi
you already have /usr/share/doc/ltspfs/examples/kde-desktop-icons
installed, quoting from the header of that file:
# to use this hook, install this in /etc/ltspfs/mounter.d/ and mark it as
# executable.
--
Automounted usb drives don't appear on desktop in KDE on ltsp thin clients
https://bugs.la
fixed in 5.1.78-0ubuntu1
** Changed in: ltsp (Ubuntu)
Status: Fix Committed => Fix Released
--
LTSP error: Can not write log, openpty() failed (/dev/pts not mounted?)
https://bugs.launchpad.net/bugs/294403
You received this bug notification because you are a member of Ubuntu
Bugs, which
i revisited the issue today and tested the following:
* we noticed that the issue does not show up in karmic so i rebuilt the
2.27 version of gnome keyring in jaunty, the issue returned with the
newer version as well
* i rebuilt the 2.27 source in jaunty with karmics gcc-4.4, the issue
vanished
Public bug reported:
Binary package hint: binutils
i am not sure how related this is to #385501, seems the testsuite was
completely rewritten between 2.19.51.20090622 and 2.19.51.20090704
though ...
which appears to result in the build failure seen at
http://launchpadlibrarian.net/28683610/build
looking at the debian PTS the same version of binutils seems to build
fine there with the default gcc-4.3
** Bug watch added: Sourceware.org Bugzilla #10385
http://sourceware.org/bugzilla/show_bug.cgi?id=10385
** Also affects: binutils via
http://sourceware.org/bugzilla/show_bug.cgi?id=1038
o...@osiris:~$ dpkg -l evolution-indicator|grep ^ii
ii evolution-indicator0.1.15-0ubuntu1
** Changed in: evolution-indicator (Ubuntu)
Status: New => Confirmed
--
evolution-indicator not working in Karmic
https://bugs.launchpad.net/bugs/390360
You received this bu
while evolution indicator is installed it does not show up in the
evolution plugin list at all. i think the plugin format of evolution
changed in the karmic version and evolution-indicator was not adjusted
to it.
--
evolution-indicator not working in Karmic
https://bugs.launchpad.net/bugs/390360
** Attachment added: "evo_plugins.png"
http://launchpadlibrarian.net/28960412/evo_plugins.png
--
evolution-indicator not working in Karmic
https://bugs.launchpad.net/bugs/390360
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubu
david sugar is currently investigating the gstreamer vorbis "Invalid
number format" error seen in the log so we can make sure banshee is not
dying because of a missing feature in the foundation. he will follow up
with info he found here.
--
banshee fails to run on arm
https://bugs.launchpad.net/b
just set /apps/nautilus/preferences/media_automount in gconf to false as
a systemwide and mandatory key
--
When an USB Drive is inserted into a LTSP Server, all connected clients receive
a mounting error
https://bugs.launchpad.net/bugs/276930
You received this bug notification because you are a
even though configure-x.sh isnt used since ages anymore, i committed the
fix in the upstream branch in case someone wants to make use of the
script (before we actually remove it from the code tree)
** Changed in: ltsp (Ubuntu)
Status: New => Fix Committed
--
configure-x.sh fails to set Ho
** Summary changed:
- result of command "lshal"
+ meta bug to collect lshal touchscreen info
** Summary changed:
- meta bug to collect lshal touchscreen info
+ result of command "lshal"
** Description changed:
- info.subsystem = 'sound' (string)
- info.udi =
'/org/freedesktop/Hal/devic
** Summary changed:
- result of command "lshal"
+ meta bug to collect lshal touchscreen info
--
meta bug to collect lshal touchscreen info
https://bugs.launchpad.net/bugs/317094
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu
Public bug reported:
Binary package hint: openoffice.org
starting an openoffice app on armel only results in a splashscreen
without starting the app, starting the app from commandline gets the
following output:
o...@babbage:~$ oowriter
javaldx: Could not find a Java Runtime Environment!
Please
401 - 500 of 3805 matches
Mail list logo
