** Attachment added: "partman from crash of installer"
http://librarian.launchpad.net/5763186/partman
--
Installer crashed in partitioning in feisty herd 2
https://launchpad.net/bugs/79456
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubu
** Attachment added: "syslog from crash of installer"
http://librarian.launchpad.net/5763170/syslog
--
Installer crashed in partitioning in feisty herd 2
https://launchpad.net/bugs/79456
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubunt
Public bug reported:
Binary package hint: ubiquity
While running the installer in Ubuntu, I got to the part where it was
running the partitioner and it crashed before even presenting any
choices.
Traceback (most recent call last):
File "/usr/lib/ubiquity/bin/ubiquity", line 185, in ?
main(
I have this same problem importing my Thawte freemail cert. Also,
kmail, doesn't seem to check the status of certs that other people sign
their email with even if I have their public cert imported into
kleopatra. I am running up to date ubuntu dapper 6.06.1 LTS with the
latest KDE 3.5.5 packages.
I installed the above package, then dropped to CLI and did aptitude
forbid-version hal. That stopped aptitude from complaining about it.
Then I opened synaptic and locked the version of hal to the one I
installed. I haven't booted back into KDE yet to see if adept complains
after I've locked it i
I also have this issue. I will just mirror the above comments and add
that this is happening on two of my machines. One a whitebox AMD with a
USB2.0 external hard drive and the other an Dell Inspiron 9100 laptop
with an iomega USB2.0 hard drive, a Fuji F700 Camera, and a Sandisk
Cruzer flash driv
I'm seeing this behaviour as well. This makes things very difficult to
have a consistent mount point between GNOME and KDE. I use this with an
external hard drive that I don't have plugged in all the time but do use
between GNOME and KDE.
--
Ugly mount point name used for removable media
https:
I can confirm that this is an issue still in the latest Dapper with the
latest ksynaptics package and synaptics driver. It appears that the
problem is that ksynaptics requires a later driver than ubuntu provides
and therefore cannot actually control the touchpad. I would love to have
this working a
I can confirm that this is an issue still in the latest Dapper with the
latest ksynaptics package and synaptics driver. It appears that the
problem is that ksynaptics requires a later driver than ubuntu provides
and therefore cannot actually control the touchpad. I would love to
have this working
