I ran "dpkg --configure -a" afterwards, which said "Setting up aiccu",
which took 30 minutes ... !
[EMAIL PROTECTED]:~$ sudo time dpkg --configure -a
Setting up aiccu (20070115-9) ...
Warning: Couldn't find global Tunnel Brokers List, please check your DNS
settings and read the FAQ.
Warning: Coul
Public bug reported:
The 8.04 to 8.10 upgrade-process get blocked while upgrading /
configuring aiccu. I think aiccu-conf want to talk to screen, which is
not succesfull. Or something like that.
Workaround: Ctrl - C
Remark: I've earlier reported a bug with strange (config) aiccu stuff.
See https
Public bug reported:
NetworkManager does not show nor connect to Wifi if/when is turned on
*after* boot
If/when a switch on my wifi switch *after* booting Ubuntu 8.10, the
NetworkManager Applet will not show any wifi functionality nor any
networks nor any connectivity. Turning off and on Wifi doe
** Attachment added: "Screenshot - NetwerkManager does not show wifi -
Ubuntu810.png"
http://launchpadlibrarian.net/19542658/Screenshot%20-%20NetwerkManager%20does%20not%20show%20wifi%20-%20Ubuntu810.png
--
NetworkManager does not show nor connect to Wifi if/when is turned on after boot
htt
dmesg included
** Attachment added: "dmesg.wifi-switched-on-after-boot.txt"
http://launchpadlibrarian.net/19542673/dmesg.wifi-switched-on-after-boot.txt
--
NetworkManager does not show nor connect to Wifi if/when is turned on after boot
https://bugs.launchpad.net/bugs/296415
You received this
I ran "dpkg --configure -a" afterwards, which said "Setting up aiccu",
which took 30 minutes ... !
[EMAIL PROTECTED]:~$ sudo time dpkg --configure -a
Setting up aiccu (20070115-9) ...
Warning: Couldn't find global Tunnel Brokers List, please check your DNS
settings and read the FAQ.
Warning: Coul
** Attachment added: "screendump of the hanging Upgrade process"
http://launchpadlibrarian.net/19517998/Screenshot-Distribution%20Upgrade-3%20-%20hangs%20on%20aiccu%20-%202.png
--
upgrade to 8.10 blocked by aiccu
https://bugs.launchpad.net/bugs/296036
You received this bug notification becau
I can't how long it took before the warnings appeared; during the upgrade I
was doing other things elsewhere.
DNS servers: I don't think it's really related to DNS-servers; they work
fine.
On Mon, Nov 10, 2008 at 22:39, Philipp Kern
<[EMAIL PROTECTED]<[EMAIL PROTECTED]>
> wrote:
> I don't know
This is my current DNS setting:
[EMAIL PROTECTED]:~$ cat /etc/resolv.conf
# Generated by NetworkManager
domain lokaal
search lokaal
nameserver 192.168.1.254
nameserver 195.241.77.55
nameserver 195.241.77.58
[EMAIL PROTECTED]:~$
Is there something I could specifically, as a plain DNS lookup works:
On another 8.10 machine (a fresh install), aiccu behaves the same when
installing (crash of aiccu when filling out incorrect sixxs
username/password, see my older bug report) and hangs for a long time
when running "sudo dpkg --configure aiccu"
So I ran "sudo strace dpkg --configure aiccu" to see w
I don't know whether anybod is investigating this bug. Here's some more
info:
I used 9.04's usb-creator to write the 8.04 iso image to a 1GB usb stick. I
moved the persistent slider completely to the right, resulting in a
persistent space of about 250 MB.
The process seemed to complete to 100%. Ho
I don't know whether anybody is investigating this bug, but here's some
more info:
With 9.04's usb-creator, I wrote the Ubuntu 8.04 iso to a 1 GB USB
Stick, with the persistent slider completely to the right (about 250 MB
space). The writing process seemed to complete to 100%, but trying to
boot f
I tried usb-creator on 9.04 final to create a live 2GB stick with 1.2GB
persistence, and still get bad results:
1) the last percentage I saw, was something like 38%. After that usb-creator
stops and says everything is OK (!)
2) booting that stick only results in a busybox prompt. :-(
So live-boo
Public bug reported:
Jaunty 9.04 i386 running from live-usb-flash could not resume (AFAIK).
Hardware is a Fujitsu Siemens E8110 laptop.
After a cold reboot, the crash report popped up.
ProblemType: KernelOops
Annotation: This occured during a previous suspend and prevented it from
resuming pro
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/26381380/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/26381381/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/26381383/Dependencies.txt
** A
On Sat, Apr 4, 2009 at 20:58, Craig Huffstetler wrote:
> During this installation, once it brings up the command prompt and exits
> install, can you give us the output of 'sudo lspci -vv' and 'sudo lspci
> -vvn' from the Linux kernel. This will help us troubleshoot. Thanks in
> advance!
I don't
I can sort-of confirm Tokenekie's message: When I select 150 MB persistence
instead of 1.1/1.2 GB on a 2 GB stick, everything goes OK.
If I have the time, I can try other persistence sizes ...
ubu...@ubuntu:~$ usb-creator
-- Starting up at 18:32:24 --
[18:32:24] /var/lib/python-support/python2.
A persistent space of 650 MB (on the same 2GB flash drive) goes OK too.
ubu...@ubuntu:~$ usb-creator
-- Starting up at 18:42:52 --
[18:42:52] /var/lib/python-support/python2.6/dbus/connection.py:242:
DeprecationWarning: object.__init__() takes no parameters
super(Connection, self).__init__(*ar
979 MB does NOT go well: after 40-something %, the process stops. Strangely
enought, the CLI output does not suddenly stop like with the 1.2 GB creation
problem.
ubu...@ubuntu:~$ usb-creator
-- Starting up at 18:56:32 --
[18:56:32] /var/lib/python-support/python2.6/dbus/connection.py:242:
Deprec
925 MB does NOT good either: the process stops after 40-something %.
ubu...@ubuntu:~$ usb-creator
-- Starting up at 19:04:30 --
[19:04:31] /var/lib/python-support/python2.6/dbus/connection.py:242:
DeprecationWarning: object.__init__() takes no parameters
super(Connection, self).__init__(*args,
825 MB does NOT go well; it stops at 40-something %
ubu...@ubuntu:~$ usb-creator
-- Starting up at 19:11:30 --
[19:11:30] /var/lib/python-support/python2.6/dbus/connection.py:242:
DeprecationWarning: object.__init__() takes no parameters
super(Connection, self).__init__(*args, **kwargs)
[19:11:
750 MB persistent space does NOT go wel: the GUI stops at 48 / 49%.
ubu...@ubuntu:~$ usb-creator
-- Starting up at 19:38:04 --
[19:38:04] /var/lib/python-support/python2.6/dbus/connection.py:242:
DeprecationWarning: object.__init__() takes no parameters
super(Connection, self).__init__(*args, *
700 MB persistence does NOT go OK: the GUI stops at 50%
ubu...@ubuntu:~$ time usb-creator
-- Starting up at 19:44:38 --
[19:44:38] /var/lib/python-support/python2.6/dbus/connection.py:242:
DeprecationWarning: object.__init__() takes no parameters
super(Connection, self).__init__(*args, **kwargs
Information lover Eva thinks the limit is at 666 MB. So I tried that.
Result: the system fully locks up at 51%. I had to reboot.
Thanks, Eva ... ;-)
--
[jaunty alpha 6+ daily] usb-creator creates incorrect free, persistent space;
to /cdrom not /
https://bugs.launchpad.net/bugs/346700
You receiv
FWIW: with the final release of Jaunty 9.04, the problem is still there.
:-(
--
playing MMS / .ASX with totem needs manual install of codec package
https://bugs.launchpad.net/bugs/350772
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Well, Neil's procedure is what I myself had written as a workaround in my
original bug report. I quote:
/quote
Workaround: manual install of package "Gstreamer plugins for mms,
wavpack, quicktime, ..." via Add/Remove.
/unquote
But I don't consider that to be the solution: totem / Ubuntu will alwa
I was able to successfully install Jaunty to the USB-stick-harddisc by
selecting hda0 (or hda1), ext3 and again no swap.
So could the bug above be caused by selecting hda (without number)
and/or ext4?
--
Unable to install GRUB in /dev/sda: "Cannot find a GRUB drive for /dev/sda1.
Check your de
No, not with me. At first I had the idea it was related to a cold versus a
warm reboot, but now my hypothesis is that the halts happen randomly, with a
50 - 70% chance.
So the workaround of blacklist & modprobe is very useful; it saves a lot a
time.
--
[regression] 2.6.27-7 sometimes fails to bo
On Thu, Oct 16, 2008 at 10:41 AM, Alexey Balmashnov
<[EMAIL PROTECTED]> wrote:
>
> Matt Zimmerman wrote:
> > Can anyone else confirm, as stated in the bug description, that the problem
> > appeared between 2.6.27-1 and 2.6.27-2?
>
> I don't remember that I ever used 2.6.27-1 kernel. Is there a simp
Bryce,
So: if I download the beta of Intrepid
http://releases.ubuntu.com/releases/8.10/ubuntu-8.10-beta-desktop-amd64.iso,
burn it and live-boot it, then activatte fglrx, I should have the new
version that I should test?
Sander
On Wed, Oct 15, 2008 at 12:23 AM, Bryce Harrington <
[EMAIL PROTEC
EnableMask:
1000
[EMAIL PROTECTED]:~$
On Sat, Oct 18, 2008 at 10:42 AM, Sander Jonkers - GMX
<[EMAIL PROTECTED]>wrote:
> Bryce,
>
> So: if I download the beta of Intrepid
> http://releases.ubuntu.com/releases/8.10/ubuntu-8.10-beta-desktop-amd64.iso,
> burn it and live-boot it
s state is not possible at all, or not
useful.
Sander
On Sat, Oct 18, 2008 at 8:42 AM, Sander Jonkers - GMX <[EMAIL PROTECTED]>wrote:
> Bryce,
>
> So: if I download the beta of Intrepid
> http://releases.ubuntu.com/releases/8.10/ubuntu-8.10-beta-desktop-amd64.iso,
> bur
What's "2.6.27-7.12"? Is that an Ubuntu kernel, or a Linux kernel?
I'm now running "2.6.27-7-generic #1 SMP Fri Oct 17 22:24:21 UTC 2008 i686
GNU/Linux" (without the .12), and there are no further updates available. Is
that the version that has fixed the bug for you? I can't tell right away
becaus
*** This bug is a duplicate of bug 263059 ***
https://bugs.launchpad.net/bugs/263059
It indeed looks the same.
Thanks
On Sat, Oct 11, 2008 at 8:32 PM, Achim <[EMAIL PROTECTED]> wrote:
> *** This bug is a duplicate of bug 263059 ***
>https://bugs.launchpad.net/bugs/263059
>
> ** This bu
I tested it a few times, and even with the Wifi switch turned off, the boot
process halts sometimes. :-(
Sander
--
[regression] 2.6.27-7 sometimes fails to boot (iwl3945 issue?)
https://bugs.launchpad.net/bugs/263059
You received this bug notification because you are a member of Ubuntu
Bugs, whi
As described, I blacklisted iwl3945 in /etc/modprobe.d/blacklist and added
the modprobe to /etc/rc.local. Result: 3 succesful boots, no hanging boots.
Does this mean we have a workaround?
If loading of iwl3945 is not a problem in the end of the boot process
(/etc/rc.local), does this mean there is
Sebastian,
If you do not blacklist, do you see errors on the boot screen (the dmesg)?
Because on my setup, the boot progress just stops after loading/activating
the iwl driver; I see no error messages at all.
FWIW: I believe (but I am not yet sure) that when I switch off the wifi
button before an
Public bug reported:
Binary package hint: update-manager
Hi,
The upgrade to 8.10 went wroing, and the upgrade asked me to report this
bug and to include the /var/log/dist-upgrade files (included) ...
** Affects: update-manager (Ubuntu)
Importance: Undecided
Status: New
--
update
** Attachment added: "dist-upgrade-no-so-good-sj.tar.gz"
http://launchpadlibrarian.net/19518069/dist-upgrade-no-so-good-sj.tar.gz
--
update-manager: Could not install the upgrades
https://bugs.launchpad.net/bugs/296037
You received this bug notification because you are a member of Ubuntu
Bugs
... and this is the screendump asking to report this.
Could be related to aiccu blocking the upgrade, see my bug report
https://bugs.launchpad.net/ubuntu/+source/aiccu/+bug/296036
** Attachment added: "Screenshot-Untitled Window - not good.png"
http://launchpadlibrarian.net/19518074/Screensho
I'm using Ubuntu (not Kubuntu) Intrepid alpha 6, so I guess I'm not using
kwd anymore?
Sander
On Sun, Sep 28, 2008 at 2:28 PM, Hew McLachlan <[EMAIL PROTECTED]>wrote:
> Thanks for your report. Do you still experience this issue with
> Intrepid?
>
> ** Changed in: compiz (Ubuntu)
> Status:
On Sun, Sep 28, 2008 at 3:50 PM, Hew McLachlan
<[EMAIL PROTECTED]>wrote:
> Thanks for your response. We are closing this bug report because it
> lacks the information we need to investigate the problem, as described
> in the previous comments.
So, after 15 (!) months of silence after my bug repo
As my machine had become unusable and did not see an update coming in,
I've installed a fresh copy of 8.10 beta, and the mouse is fine now.
--
[intrepid] mouse and keyboard stop working under gdm and gnome
https://bugs.launchpad.net/bugs/254840
You received this bug notification because you are a
Public bug reported:
Ubuntu 8.10 Beta:
With today's 2.6.27-6-generic, my boot halts at:
iwl3945 tunable channels: 13 802.11bg, 23 802.11a channels
iwl3945 :05:00.0: PCI INT A disabled
See included picture of my screen during boot.
With yesterday's 2.6.27-4-generic, everything was OK. I wil
** Attachment added: "2.6.27-6-generic---halts.jpg"
http://launchpadlibrarian.net/18419563/2.6.27-6-generic---halts.jpg
--
8.10 beta 2.6.27-6-generic halts on iwl3945 :05:00.0: PCI INT A disabled
https://bugs.launchpad.net/bugs/281447
You received this bug notification because you are a m
The dmesg of the non-halted, old 2.6.27-4-generic
** Attachment added: "dmesg-2.6.27-4-generic.txt"
http://launchpadlibrarian.net/18419660/dmesg-2.6.27-4-generic.txt
--
8.10 beta 2.6.27-6-generic halts on iwl3945 :05:00.0: PCI INT A disabled
https://bugs.launchpad.net/bugs/281447
You rece
It's my experience with 2.6.27-4-generic that 1) wifi works with WEP, but 2)
Ubuntu does not remember the WEP key: on all (two) WEP networks I connect
to, I have to type the WEP each time after logon, whereas WPA networks
passwords are remembered.
On Fri, Oct 10, 2008 at 10:16 PM, Ralph Janke <[
Update: the halt seems to be a bit random: a 50 - 75% change it halts. I've
seen random halts in the previous weeks, too. So it's not hard-related to
2.6.27-6-generic
I've now been able to boot yesterday's 2.6.27-6-generic. And today's
2.6.27-7-generic works too; no halts so far.
I've removed "qu
After today's 100 MB update, my mouse is intermittently not working
(Ubuntu 8.10 intrepid ibex): I can move the mouse for about 20 - 30
seconds, and then it won't move for a few minutes, after which I can
move the mouse for about 20-30 seconds, etc.
This happens to both my USB mouse and my touchpa
Timo,
I tried booting the older kernels in the GRUB list, with the same
effect.
Do you know the other bug number?
Thanks,
Sander
On Tue, Oct 7, 2008 at 10:39 PM, Timo Aaltonen
<[EMAIL PROTECTED]>wrote:
> sander: that sounds more like a kernel bug to me. This bug has been
> fixed some time ago.
Public bug reported:
Binary package hint: xorg
I'm trying out the live CD of Kubuntu 8.10 64-bit Alpha 5 (Intrepid
Ibex):
With a normal boot, I get the splash screen with the moving progess bar, and
after a few minutes ... nothing. Just a black screen.
With a Safe Graphics boot, I do get a X sc
** Attachment added: "dmesg.kubuntu-8.10-alpha5.txt"
http://launchpadlibrarian.net/17665347/dmesg.kubuntu-8.10-alpha5.txt
--
only X server when booting Safe Graphics Mode with 64-bit Kubuntu 8.10 Alpha 5
Intrepid Ibex
https://bugs.launchpad.net/bugs/271072
You received this bug notification
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/16662190/Dependencies.txt
** Attachment added: "DpkgTerminalLog.gz"
http://launchpadlibrarian.net/16662191/DpkgTerminalLog.gz
--
package aiccu 20070115-7 failed to install/upgrade: subprocess
post-installation script r
Public bug reported:
Binary package hint: aiccu
Ubuntu is telling it's a crash, and thus a halt like in
https://bugs.launchpad.net/ubuntu/+source/aiccu/+bug/104590
The strange thing: afterwards, aiccu is installed.
So doesn't look like a prio 1 bug. ;-)
ProblemType: Package
Architecture: i386
Oh, that's right: I filled out some bogus account info, because all the
correct info was in an aiccu.conf I had saved somewhere else.
And: it's was Ubuntu that said something had crashed and wanted to report
it. I hadn't noticed it myself.
So, as I said, lowest (if any) prio you can imagine.
On
Strange: a did another live boot (without any special boot / graphics
options), and that boot went OK and showed a correct X screen.
More testing to do.
Sander
On Fri, Sep 19, 2008 at 4:05 PM, Timo Aaltonen <[EMAIL PROTECTED]>wrote:
> can you change the VT with ctrl-alt-F1? Do that while uspla
I did two more live boots, and both were successful. So I can't reproduce
the problem. Can I cancel my bug report?
On Mon, Sep 22, 2008 at 12:50 PM, Sander Jonkers - GMX
<[EMAIL PROTECTED]>wrote:
> Strange: a did another live boot (without any special boot / graphics
> option
Jason,
Thanks for this workaround: I can now connect to my WEP AP.
FYI: I installed Ubuntu 8.04.1 which only has the faulty software, so you
can not choose the older kernel anymore to connect to a WEP AO. Quite a
serious Ubuntu bug IMHO.
Sander
[EMAIL PROTECTED]:~$ sudo apt-get install linux-b
Still the same problem with today's newest kernel "Ubuntu 8.04, kernel
2.6.24-19-generic": can't connect to WEP2. I still need to boot into
good old "Ubuntu 8.04, kernel 2.6.22-14-generic" from the boot options
to have my Centrino connected to my WEP AP.
BTW: With kernel 2.6.24-19, the network man
The bug is still there: with today's upgrade to kernel
2.6.24-19-generic, the default boot was incorrectly pointing to memtest
on position 10, which before the kernel upgrade was the pointer to
WindowsXP (which was my default before the kernel upgrade).
[EMAIL PROTECTED]:~$ egrep -i -e default -e
Trying to find a workaround (other than editing /boot/grub/menu.lst) I
tried this:
[EMAIL PROTECTED]:~$ sudo grub-set-default 12
[sudo] password for sander:
Searching for GRUB installation directory ... found: /boot/grub
[EMAIL PROTECTED]:~$
But, alas, that does not work as default stays on 10 an
One more try to find a solution or workaround for this: I changed the
value of the menu.lst parameter "default" from a number to "saved". I
hope that this option will select the Windows XP title as the default
boot option as the Windows XP title has "savedefault" in it's list.
The first boot shows
Public bug reported:
My X server crashed: the screen turned black, there were a few lines of ASCII
output, and then a new X session (including logon) was created. syslog below.
Hardware: Athlon X2, onboard ATI X1250 GPU, running Ubuntu 8.04 64-bit with
proprietary video driver.
[EMAIL PROTECT
** Attachment added: "xorg.conf"
http://launchpadlibrarian.net/15167003/xorg.conf
--
fglrx X crash / restart
https://bugs.launchpad.net/bugs/238763
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-b
Here's /var/log/Xorg.0.log
** Attachment added: "Xorg.0.log"
http://launchpadlibrarian.net/15167027/Xorg.0.log
--
fglrx X crash / restart
https://bugs.launchpad.net/bugs/238763
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubun
and here's /var/log/Xorg.0.log.old
** Attachment added: "Xorg.0.log.old"
http://launchpadlibrarian.net/15167028/Xorg.0.log.old
--
fglrx X crash / restart
https://bugs.launchpad.net/bugs/238763
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
Dereck,
How do you know it's a Compiz problem? I thougth it could be ati-driver or
gdm related?
Sander
On Tue, Jun 10, 2008 at 1:44 PM, Dereck Wonnacott <[EMAIL PROTECTED]>
wrote:
> ** Changed in: compiz (Ubuntu)
> Sourcepackagename: None => compiz
>
> --
> fglrx X crash / restart
> https://bug
On Tue, Jan 6, 2009 at 18:05, Andreas Gnau wrote:
> I can confirm that this is fixed for me (iwl3945) in jaunty, but not in
> intrepid.
So we have this bug since 8.10, thus october 2008. I'm quite suprised to see
it's not yet solved.
Because of this annoying bug I've switched my laptop back to
Same crash while trying to install Jaunty Alpha 6 i386 to a 8 GB USB
stick.
I don't know whether this matters, but: the crash occured 1 second after
clicking the network manager.
--
install.py crashed with TypeError in main()
https://bugs.launchpad.net/bugs/331327
You received this bug notificat
@Martin Pitt:
Is your patch (right?) included in Jaunty Alpha 6? Below you can see
what my Jaunty Alpha 6 has, so it's looks patched, but I still got the
crash.
ubu...@ubuntu:~$ ls -al /usr/share/usb-creator
total 49
drwxr-xr-x 2 root root64 2009-03-12 01:04 .
drwxr-xr-x 318 root root 409
FWIW:
Using usb-creator from Linux Mint 6 (based on Ubuntu 8.10), I was able
to write the Jaunty-Alpha6-iso to a USB stick. I guess that means the
bug was introduced between 8.10 and 9.04.
--
install.py crashed with TypeError in main()
https://bugs.launchpad.net/bugs/331327
You received this bug
Wow, this is fantastic: I tested IPv6 connectivity in Jaunty Alpha 6,
and it works great.
Both tested with a FQDN and with a litteral IPv6 addres [2001:...]: it
just works.
Thank you!
BTW: not related, but nice too: the Remote Desktop Viewable computer is
also announced via avahia / zeroconf / r
PS: one remark: when making your desktop viewable, it will say something
like:
"Your desktop is only reachable over the local network. Others can
access your computer using the address 192.168.1.10 , ubuntu.local."
If there's a public IPv6 address, it would be correct and useful to tell that
IP
Public bug reported:
Binary package hint: vino
Bug: vino-preferences does not report public IPv6 addresses, only IPv4
addresses.
On: Ubuntu 9.04 Jaunty Alpha 6
vino-preferences is now reporting: "Your desktop is only reachable over
the local network. Others can access your computer using the ad
@Emilio:
OK, bug reported here:
https://bugs.launchpad.net/ubuntu/+source/vino/+bug/344489 saying
"vino-preferences does not report public IPv6 addresses"
--
Vinagre can not connect to ipv6 address, only resolving hostnames
https://bugs.launchpad.net/bugs/290394
You received this bug notificati
Public bug reported:
Binary package hint: vuze
On Ubuntu 9.04 Jaunty Alpha 6+, Linux ubuntu 2.6.28-8-generic #26-Ubuntu
SMP Wed Feb 25 04:27:53 UTC 2009 x86_64 GNU/Linux:
vuze 3.1.1.0: "fatal error has been detected by the Java Runtime
Environment:"
Remark: this vuze 3.1.1.0 is quite old. Why n
Public bug reported:
I cannot install python-cheetah on updated (28 Feb 2009) Jaunty Alpha 5:
The following packages have unmet dependencies:
python-cheetah: Depends: python (< 2.6) but 2.6.1-0ubuntu1 is to be installed
E: Broken packages
This is probably caused by the python version, which h
FWIW:
Things seem to be have been solved in Jaunty / 9.04: A friend of mine
live-booted Jaunty Alpha 5 on his eMachines D620 with the Atheros wifi
chipset, and reported:
"Jep, bingo, 9.05 alpha-5 ouf-of-the-box. lsmod shows ath5k."
HTH
--
[Intrepid] Atheros ath5k wireless driver not enabled by
Public bug reported:
Binary package hint: python-yenc
I cannot install python-yenc on Jaunty Alpha 5: unmet dependencies.
Probably caused by python 2.6; the current python-yenc needs python < 2.6, so
python 2.5
(This is a lookalike of
https://bugs.launchpad.net/ubuntu/+source/cheetah/+bug/33619
Public bug reported:
Trying to load the plugin 'Coherence DLNA/UPnP Client' results in an
error and no UPnP plugin loaded: ImportError: No module named
coherence.ui.av_widgets
Ubuntu 9.04 Jaunty Alpha 5 updated until today (2009-03-06)
Full CLI logging:
san...@jaunty:~$ totem
/var/lib/python-su
After installying "python-coherence", the GUI bug stays the same, the
CLI output is more ugly and/or more informative.
san...@jaunty:~$
san...@jaunty:~$
san...@jaunty:~$ totem
/var/lib/python-support/python2.6/gdata/tlslite/utils/cryptomath.py:9:
DeprecationWarning: the sha module is deprecate
Solution (workaround?) found, thanks to Linux genius ArjanW drinking my
Bavaria beer:
As root, create file /usr/share/dbus-1/services/org.Coherence.service
with contents:
[D-BUS Service]
Name=org.Coherence
Exec=/usr/bin/coherence -o use_dbus:yes -o controlpoint:yes
After that, totem's Coherence
And a picture showing that the totem Coherence DLNA UPnP actually works;
it does see the UPnP AV Mediaserver provided by rhythmbox.
** Attachment added: "totem Coherence DLNA UPnP does see the UPnP AV
Mediaserver provided by rhythmbox."
http://launchpadlibrarian.net/23564206/Screenshot-Movie%
Public bug reported:
Binary package hint: ubiquity
Ubuntu-version: 9.04 Jaunty AMD64 ALPHA 5, running from live-CD.
Trying to install to an USB flash stick (4GB) as a normal drive (not the
USB-live-disk option), with ext4 and boot loader (?) checked to install
to /dev/sda, not /dev/hd (!). There
Happens to me too, with a 4GB live-USB-stick.
Further installations (like with 'miredo' below) result in the same exit
status 17. :-(
ubu...@ubuntu:~$ sudo apt-get install miredo
Reading package lists... Done
Building dependency tree
Reading state information... Done
miredo is already the
Public bug reported:
I think it would be better if the 64-bit Ubuntu versions would be called
"x86-64" not "AMD64".
Reason: people with 64-bit Intel processors (Core 2, i7, dual pentium)
are asking in the Ubuntuforum where they get the 'correct version' as
they don't have an AMD64 ... :-(
Yes, I
Great!
Dankjewel, Wouter.
--
[need-packaging] SABnzbd
https://bugs.launchpad.net/bugs/102310
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.ubuntu.com/mailman/list
First results: Installation goes OK, however unrar and par2 don't go
well:
Last warnings (clear)
2009-02-22 14:07:51,726 WARNING unrar binary... NOT found
2009-02-22 14:17:44,647 WARNING [newsunpack] Missing expected file:
blabla.Divx.blabla.avi => unrar error?
http://packages.ubuntu.com/jaunty/
Public bug reported:
On: jaunty alpha 6+ daily dated 20/21 Mar 2009:
usb-creator creates incorrect free, persistent space; the space is
assigned to /cdrom, not to /
Details: on a 8GB USB stick, at the start of installation/creation of the live
USB stick, I've moved the free space slider complet
FYI: on good old 8.10, the same procedure (free space slider to the
right) on a 4GB stick results in the correct space assignment: almost
all to / , and only a litte space extra to /cdrom:
rootfs 3168M 155M 2853M 6% /
/dev/sdb13928M 3917M 11M
Public bug reported:
[Jaunty Beta] usb-creator 0.1.15 results in no usable usb-stick: booting
the usb-stick falls back to BusyBox' CLI.
Long story:
I booted Jaunty Beta from CD, then started usb-creator (0.1.15) to create a
usb-live stick (on a 2 GB device). Somewhere after completing 35-39%, t
Public bug reported:
python-coherence on Ubuntu Jaunty Beta & Daily build March 31 2009:
the file /usr/share/dbus-1/services/org.Coherence.service is missing.
This results in error message like "dbus.exceptions.DBusException:
org.freedesktop.DBus.Error.ServiceUnknown: The name org.Coherence was
n
jruss: thank you. Very good hypothesis. I will check it out.
--
[jaunty alpha 6+ daily] usb-creator creates incorrect free, persistent space;
to /cdrom not /
https://bugs.launchpad.net/bugs/346700
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Well, yes, it is *by subject* a coherence problem. But this bug report
reveals two bugs:
bug 1: the fact that totem offers Coherence DLNA/UPnP, whereas python-coherence
needs to be installed for that, which does not happen.
If is not installed by default due to CD constrains, it should not result
@Sebastien Bacher
What do you mean with "I doubt that will be an highlighted jaunty
option"?
Do you think the coherence plugin is not offered by the totem GUI? If
so, please see the included screendump where coherence is offered,
including the GUI and CLI errors I get by 'checking' on the plugin.
** This bug is no longer a duplicate of bug 338963
Totem: loading "Coherence DLNA/UPnP Client" results in: "ImportError: No
module named coherence.ui.av_widgets"
--
python-coherence: /usr/share/dbus-1/services/org.Coherence.service should be
included
https://bugs.launchpad.net/bugs/352653
Yo
At " *** This bug is a duplicate of bug 338963 ***":
No, it's not a duplicate. Bug
https://bugs.launchpad.net/ubuntu/+source/coherence/+bug/338963 is a
separate bug. As already explained there:
bug 1 (338963): the fact that totem offers Coherence DLNA/UPnP, whereas
python-coherence needs to be i
oops, typo:
"installing python-coherence reveals a bug in bug-python itself"
should read
"installing python-coherence reveals a bug in *python-coherence* itself"
--
python-coherence: /usr/share/dbus-1/services/org.Coherence.service should be
included
https://bugs.launchpad.net/bugs/352653
You
oops, typo:
"installing python-coherence reveals a bug in bug-python itself"
should read
"installing python-coherence reveals a bug in *python-coherence* itself"
--
Totem: loading "Coherence DLNA/UPnP Client" results in: "ImportError: No module
named coherence.ui.av_widgets"
https://bugs.lau
I have not seen it in Jaunty
--
gvfsd-obexftp crashed with SIGSEGV in dbus_g_proxy_end_call()
https://bugs.launchpad.net/bugs/276872
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.co
1 - 100 of 434 matches
Mail list logo
