[Bug 1449813] [NEW] installer does not use empty space on sda

2015-04-28 Thread mherweg
Public bug reported:


the PC has one disk.
3 partitions are used for Windows7 
behind those there is 40GB unpartitioned space.
the installer does not offer to resize one of the NTFS partitions
or offers to install into th unpartitioned area.
the only coices are: delete all partitions or manual choice.
I did the manual choice, installed into sda4.

It installs  fine but without a grub menu - no way to start windows.
after installation I had to do:

grub-mkconfig -o /boot/grub/grub.cfg 
grub-install


(i will try to add the log later)

** Affects: ubiquity (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1449813

Title:
  installer does not use empty space on sda

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1449813/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1173720] [NEW] flightgear : Depends: libudev0 (= 147) but it is not installable

2013-04-27 Thread mherweg
Public bug reported:

apt-get install flightgear
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 flightgear : Depends: libudev0 (= 147) but it is not installable
E: Unable to correct problems, you have held broken packages.

apt-get install libudev0
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Package libudev0 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'libudev0' has no installation candidate

lsb_release -rd
Description:Ubuntu 13.04
Release:13.04

apt-cache policy flightgear
flightgear:
  Installed: (none)
  Candidate: 2.10.0-1ppa3~raring1
  Version table:
 2.10.0-1ppa3~raring1 0
500 http://ppa.launchpad.net/saiarcot895/flightgear/ubuntu/ raring/main 
i386 Packages
 2.6.0-1build1 0
500 http://si.archive.ubuntu.com/ubuntu/ raring/universe i386 Packages
100 /var/lib/dpkg/status

** Affects: flightgear (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1173720

Title:
  flightgear : Depends: libudev0 (= 147) but it is not installable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flightgear/+bug/1173720/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1077624] Re: Raring: Update Flightgear to version 2.10.0

2013-04-27 Thread mherweg
apt-get install flightgear
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 flightgear : Depends: libudev0 (= 147) but it is not installable
E: Unable to correct problems, you have held broken packages.

apt-get install libudev0
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Package libudev0 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'libudev0' has no installation candidate

lsb_release -rd
Description:Ubuntu 13.04
Release:13.04

apt-cache policy flightgear
flightgear:
  Installed: (none)
  Candidate: 2.10.0-1ppa3~raring1
  Version table:
 2.10.0-1ppa3~raring1 0
500 http://ppa.launchpad.net/saiarcot895/flightgear/ubuntu/ raring/main 
i386 Packages
 2.6.0-1build1 0
500 http://si.archive.ubuntu.com/ubuntu/ raring/universe i386 Packages
100 /var/lib/dpkg/status

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1077624

Title:
  Raring: Update Flightgear to version 2.10.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fgfs-base/+bug/1077624/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 138880] Re: Openchrome driver in Gutsy (on in Fujitsu-Siemens Amilo Pro V2055)

2007-11-15 Thread mherweg
I have a Amilo Pro V2030
It has a 1024x768 LCD and the VIA Technologies, Inc. UniChrome Pro IGP (rev 01)
(PCI-ID 1106:3344 )

the hardware detectiton of the install was not good. The installer chose
vesa @ 800x600

I did use a  self-compiled openchrome driver on Ubuntu 6.06LTS.
Now on Ubuntu 7.10 I use the packages

   libviaxvmc1 libviaxvmcpro1 xserver-xorg-video-openchrome

2D works stable. I did not test much 3D but glxinfo  glxgears look ok.


** Attachment added: my xorg.conf for Amilo Pro V2030
   http://launchpadlibrarian.net/10378541/xorg.conf

-- 
Openchrome driver in Gutsy (on in Fujitsu-Siemens Amilo Pro V2055)
https://bugs.launchpad.net/bugs/138880
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/listinfo/ubuntu-bugs


[Bug 112171] Re: Conflict with firefox not needed

2007-07-12 Thread mherweg
I confirm this problem (kubuntu 7.04)  
when i try to install firefox, apt-get wants to remove hunspell-de-de.
when i try to install hunspell-de-de then apt-get wants to remove firefox

-- 
Conflict with firefox not needed
https://bugs.launchpad.net/bugs/112171
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/listinfo/ubuntu-bugs


Re: [Bug 99594] Re: Installer/partitioner crashes [feisty beta]

2007-04-01 Thread mherweg
*** This bug is a duplicate of bug 95400 ***

Colin Watson schrieb:
 *** This bug is a duplicate of bug 95400 ***

 Thanks for your report. This is also bug 95400; run 'sudo apt-get
 update; sudo apt-get install ubiquity' in a terminal window before
 starting the installer to pick up the fix.

I did . and the installation (manual partitioning) worked this time.

-- 
Installer/partitioner crashes [feisty beta]
https://launchpad.net/bugs/99594

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


Re: [Bug 97034] Re: Ubiquity crashes when scanning existing hard drive partitions

2007-03-28 Thread mherweg
*** This bug is a duplicate of bug 95400 ***

Colin Watson schrieb:
 *** This bug is a duplicate of bug 95400 ***

 Is there any reason you didn't use the crash icon to report this bug?

I can't remember exactly.
I think a crash message appeared and i clicked submit

maybe it failed because of the other bug I filed:
I was not able to set up a static IP , router, DNS with the KDE GUI
so i did it in console later .

-- 
Ubiquity crashes when scanning existing hard drive partitions
https://launchpad.net/bugs/97034

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 96428] feisty beta: wrong screen resolution even when setting it to 1024x768 before boot

2007-03-26 Thread mherweg
Public bug reported:

Binary package hint: xorg

i first tried to set nothing at boot, also tried safe graphics mode
and tried to set it to [EMAIL PROTECTED] before boot - but it did not help: i
alwyas only see the upper left corner (size:1024x768)of a 1600x1200
screen

ProblemType: Bug
Architecture: i386
Date: Mon Mar 26 13:25:37 2007
DistroRelease: Ubuntu 7.04
Uname: Linux ubuntu 2.6.20-12-generic #2 SMP Wed Mar 21 20:55:46 UTC 2007 i686 
GNU/Linux

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: Unconfirmed

-- 
feisty beta: wrong screen resolution even when setting it to 1024x768 before 
boot
https://launchpad.net/bugs/96428

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 96428] Re: feisty beta: wrong screen resolution even when setting it to 1024x768 before boot

2007-03-26 Thread mherweg
[EMAIL PROTECTED]:~# lspci -n
00:00.0 0600: 1106:0314
00:00.1 0600: 1106:1314
00:00.2 0600: 1106:2314
00:00.3 0600: 1106:3208
00:00.4 0600: 1106:4314
00:00.7 0600: 1106:7314
00:01.0 0604: 1106:b198
00:06.0 0200: 168c:0013 (rev 01)
00:0c.0 0607: 104c:8031
00:0c.2 0c00: 104c:8032
00:0f.0 0101: 1106:3149 (rev 80)
00:0f.1 0101: 1106:0571 (rev 06)
00:10.0 0c03: 1106:3038 (rev 81)
00:10.1 0c03: 1106:3038 (rev 81)
00:10.4 0c03: 1106:3104 (rev 86)
00:11.0 0601: 1106:3227
00:11.5 0401: 1106:3059 (rev 60)
00:11.6 0780: 1106:3068 (rev 80)
00:12.0 0200: 1106:3065 (rev 78)
01:00.0 0300: 1106:3344 (rev 01)

01:00.0 VGA compatible controller: VIA Technologies, Inc. UniChrome Pro
IGP (rev 01)

(Fujitsu Siemens Amilo Pro 2030 Notebook)

in xorg.conf:

Section Device
Identifier  Standardgrafikkarte
Driver  vesa
BusID   PCI:1:0:0
EndSection

   DefaultDepth24
  ...
SubSection Display
Depth   24
Modes   1600x1200 (pitch 1600)
EndSubSection

so obviosly the coice from boot was ignored.



** Description changed:

  Binary package hint: xorg
  
  i first tried to set nothing at boot, also tried safe graphics mode
  and tried to set it to [EMAIL PROTECTED] before boot - but it did not help: i
- alwyas only see the upper left corner (size:1024x768)of a 1600x1400
+ alwyas only see the upper left corner (size:1024x768)of a 1600x1200
  screen
  
  ProblemType: Bug
  Architecture: i386
  Date: Mon Mar 26 13:25:37 2007
  DistroRelease: Ubuntu 7.04
  Uname: Linux ubuntu 2.6.20-12-generic #2 SMP Wed Mar 21 20:55:46 UTC 2007 
i686 GNU/Linux

-- 
feisty beta: wrong screen resolution even when setting it to 1024x768 before 
boot
https://launchpad.net/bugs/96428

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 95734] Re: installer: partman_auto.py: need more than 1 value to unpack

2007-03-26 Thread mherweg

** Attachment added: /var/log/syslog
   http://librarian.launchpad.net/6938786/syslog

-- 
installer: partman_auto.py: need more than 1 value to unpack
https://launchpad.net/bugs/95734

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 95734] Re: installer: partman_auto.py: need more than 1 value to unpack

2007-03-26 Thread mherweg

** Attachment added: /var/log/installer/debug  after crash
   http://librarian.launchpad.net/6938762/debug

-- 
installer: partman_auto.py: need more than 1 value to unpack
https://launchpad.net/bugs/95734

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 95734] Re: installer: partman_auto.py: need more than 1 value to unpack

2007-03-26 Thread mherweg

** Attachment added: /var/log/partman
   http://librarian.launchpad.net/6938791/partman

-- 
installer: partman_auto.py: need more than 1 value to unpack
https://launchpad.net/bugs/95734

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 96428] Re: feisty beta: wrong screen resolution even when setting it to 1024x768 before boot

2007-03-26 Thread mherweg

** Attachment added: /var/log/Xorg.0.log
   http://librarian.launchpad.net/6941074/Xorg.0.log

-- 
feisty beta: wrong screen resolution even when setting it to 1024x768 before 
boot
https://launchpad.net/bugs/96428

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 96428] Re: feisty beta: wrong screen resolution even when setting it to 1024x768 before boot

2007-03-26 Thread mherweg

I changed vesa  to via  in xorg.conf and it did not work.
I was not able to test different resolutions  color-depth, because i had no 
text-console in this live CD.

I use the openchrome (kernel+xorg)Driver in kubuntu 6.06 and it is very 
stable. playing videos and using 3D accel. is a bit tricky but works.
http://www.openchrome.org/

-- 
feisty beta: wrong screen resolution even when setting it to 1024x768 before 
boot
https://launchpad.net/bugs/96428

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 95734] installer: partman_auto.py: need more than 1 value to unpack

2007-03-24 Thread mherweg
Public bug reported:

Binary package hint: ubiquity

kubunut 7.04 beta installer Step4 of 6:


Mar 25 00:44:09 ubiquity: Setting keyboard layout: pc105 de nodeadkeys []

QSocketNotifier: Invalid socket 17 and type 'Read', disabling...
QSocketNotifier: Invalid socket 17 and type 'Read', disabling...
QSocketNotifier: Invalid socket 17 and type 'Exception', disabling...
Mar 25 00:44:14 ubiquity: Starting up '['log-output', '-t', 'ubiquity', 
'--pass-stdout', '/bin/partman']' for ubiquity.components.partman.Partman

Mar 25 00:44:14 ubiquity: Watching for question patterns 
^partman-auto/.*automatically_partition$, ^partman-auto/select_disk$, 
^partman-partitioning/new_size$, ^partman/choose_partition$, 
^partman/confirm.*, type:boolean, ERROR, PROGRESS, ^partman/confirm
_new_label$, ^partman/free_space$, ^partman/active_partition$, 
^partman-partitioning/new_partition_(size|type|place)$, 
^partman-partitioning/confirm_resize$, ^partman-partitioning/new_size$, 
^partman-target/choose_method$, ^partman-basicfilesystems/(fat_m
ountpoint|mountpoint|mountpoint_manual)$, ^partman/exception_handler$, 
^partman/exception_handler_note$

Mar 25 00:44:15 ubiquity: Partman: update_partitions = None
Mar 25 00:44:15 ubiquity: Partman: update_partitions = None
Mar 25 00:44:15 ubiquity: Partman: update_partitions = None
Mar 25 00:44:15 ubiquity: Partman: update_partitions = None
Mar 25 00:44:15 ubiquity: Partman: update_partitions = None
Mar 25 00:44:16 ubiquity: Partman: update_partitions = None
Mar 25 00:44:16 ubiquity: Partman: update_partitions = None
Mar 25 00:44:16 ubiquity: Partman: update_partitions = None

Mar 25 00:44:16 ubiquity: Partman: update_partitions = None
Mar 25 00:44:16 ubiquity: Partman: update_partitions = None
Mar 25 00:44:16 ubiquity: Partman: update_partitions = None
Mar 25 00:44:17 ubiquity: Partman: update_partitions = None
Mar 25 00:44:17 ubiquity: Partman: update_partitions = None
Mar 25 00:44:17 ubiquity: Partman: update_partitions = None
Mar 25 00:44:17 ubiquity: Partman: update_partitions = None
Mar 25 00:44:17 ubiquity: Partman: update_partitions = None
Mar 25 00:44:17 ubiquity: Partman: update_partitions = None
Mar 25 00:44:18 ubiquity: Partman: update_partitions = None
Mar 25 00:44:18 ubiquity: Partman: state = [['', None, None]]
Exception in KDE frontend (invoking crash handler):
Traceback (most recent call last):
  File /usr/lib/ubiquity/ubiquity/frontend/kde-ui.py, line 1339, in 
watch_debconf_fd_helper_read
self.debconf_callbacks[source](source, debconf_condition)
  File
/usr/lib/ubiquity/ubiquity/filteredcommand.py, line 176, in process_input
if not self.process_line():
  File /usr/lib/ubiquity/ubiquity/filteredcommand.py, line 110, in 
process_line
return self.dbfilter.process_line()
  File /usr/lib/ubiquity
/ubiquity/debconffilter.py, line 268, in process_line
widget.subst(question, key, value)
  File /usr/lib/ubiquity/ubiquity/components/partman.py, line 228, in subst
PartmanAuto.subst(self, question, key, value)
  File /usr/lib/ubiquity/ubiquit
y/components/partman_auto.py, line 99, in subst
self.resize_min_size = self.parse_size(value)
  File /usr/lib/ubiquity/ubiquity/components/partman_auto.py, line 81, in 
parse_size
(size_int, size_frac) = num.split('.', 1)
ValueError: need more t
han 1 value to unpack



before it did work on the same machine, but the installation crashed later.
fdisk -l
 
Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot  Start End  Blocks   Id  System
/dev/sda1   1243219535008+  83  Linux
/dev/sda22433   19457   136753312+   5  Extended
/dev/sda524333648 9767488+  83  Linux
/dev/sda63649608019535008+  83  Linux
/dev/sda76081   1580678124063+  83  Linux
/dev/sda8   15807   16049 1951866   82  Linux swap / Solaris
/dev/sda9   16050   16657 4883728+  83  Linux
/dev/sda10  16658   17265 4883728+  83  Linux
/dev/sda11  17266   17873 4883728+  83  Linux
/dev/sda12  17874   1945712723448+  83  Linux


sda12 is a dmcrypt-partition

** Affects: ubiquity (Ubuntu)
 Importance: Undecided
 Status: Unconfirmed

-- 
installer: partman_auto.py: need more than 1 value to unpack
https://launchpad.net/bugs/95734

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 95734] Re: installer: partman_auto.py: need more than 1 value to unpack

2007-03-24 Thread mherweg
** Description changed:

  Binary package hint: ubiquity
  
  kubunut 7.04 beta installer Step4 of 6:
  
+ 
+ Mar 25 00:44:09 ubiquity: Setting keyboard layout: pc105 de nodeadkeys []
+ 
+ QSocketNotifier: Invalid socket 17 and type 'Read', disabling...
+ QSocketNotifier: Invalid socket 17 and type 'Read', disabling...
+ QSocketNotifier: Invalid socket 17 and type 'Exception', disabling...
+ Mar 25 00:44:14 ubiquity: Starting up '['log-output', '-t', 'ubiquity', 
'--pass-stdout', '/bin/partman']' for ubiquity.components.partman.Partman
+ 
+ Mar 25 00:44:14 ubiquity: Watching for question patterns 
^partman-auto/.*automatically_partition$, ^partman-auto/select_disk$, 
^partman-partitioning/new_size$, ^partman/choose_partition$, 
^partman/confirm.*, type:boolean, ERROR, PROGRESS, ^partman/confirm
+ _new_label$, ^partman/free_space$, ^partman/active_partition$, 
^partman-partitioning/new_partition_(size|type|place)$, 
^partman-partitioning/confirm_resize$, ^partman-partitioning/new_size$, 
^partman-target/choose_method$, ^partman-basicfilesystems/(fat_m
+ ountpoint|mountpoint|mountpoint_manual)$, ^partman/exception_handler$, 
^partman/exception_handler_note$
+ 
+ Mar 25 00:44:15 ubiquity: Partman: update_partitions = None
+ Mar 25 00:44:15 ubiquity: Partman: update_partitions = None
+ Mar 25 00:44:15 ubiquity: Partman: update_partitions = None
+ Mar 25 00:44:15 ubiquity: Partman: update_partitions = None
+ Mar 25 00:44:15 ubiquity: Partman: update_partitions = None
+ Mar 25 00:44:16 ubiquity: Partman: update_partitions = None
+ Mar 25 00:44:16 ubiquity: Partman: update_partitions = None
+ Mar 25 00:44:16 ubiquity: Partman: update_partitions = None
+ 
+ Mar 25 00:44:16 ubiquity: Partman: update_partitions = None
+ Mar 25 00:44:16 ubiquity: Partman: update_partitions = None
+ Mar 25 00:44:16 ubiquity: Partman: update_partitions = None
+ Mar 25 00:44:17 ubiquity: Partman: update_partitions = None
+ Mar 25 00:44:17 ubiquity: Partman: update_partitions = None
+ Mar 25 00:44:17 ubiquity: Partman: update_partitions = None
+ Mar 25 00:44:17 ubiquity: Partman: update_partitions = None
+ Mar 25 00:44:17 ubiquity: Partman: update_partitions = None
+ Mar 25 00:44:17 ubiquity: Partman: update_partitions = None
+ Mar 25 00:44:18 ubiquity: Partman: update_partitions = None
+ Mar 25 00:44:18 ubiquity: Partman: state = [['', None, None]]
+ Exception in KDE frontend (invoking crash handler):
  Traceback (most recent call last):
File /usr/lib/ubiquity/ubiquity/frontend/kde-ui.py, line 1339, in 
watch_debconf_fd_helper_read
  self.debconf_callbacks[source](source, debconf_condition)
-   File /usr/lib/ubiquity/ubiquity/filteredcommand.py, line 176, in 
process_input
+   File
+ /usr/lib/ubiquity/ubiquity/filteredcommand.py, line 176, in process_input
  if not self.process_line():
File /usr/lib/ubiquity/ubiquity/filteredcommand.py, line 110, in 
process_line
  return self.dbfilter.process_line()
-   File /usr/lib/ubiquity/ubiquity/debconffilter.py, line 268, in 
process_line
+   File /usr/lib/ubiquity
+ /ubiquity/debconffilter.py, line 268, in process_line
  widget.subst(question, key, value)
File /usr/lib/ubiquity/ubiquity/components/partman.py, line 228, in subst
  PartmanAuto.subst(self, question, key, value)
-   File /usr/lib/ubiquity/ubiquity/components/partman_auto.py, line 99, in 
subst
+   File /usr/lib/ubiquity/ubiquit
+ y/components/partman_auto.py, line 99, in subst
  self.resize_min_size = self.parse_size(value)
File /usr/lib/ubiquity/ubiquity/components/partman_auto.py, line 81, in 
parse_size
  (size_int, size_frac) = num.split('.', 1)
- ValueError: need more than 1 value to unpack
+ ValueError: need more t
+ han 1 value to unpack
+ 
+ 
+ 
  
  before it did work on the same machine, but the installation crashed later.
  fdisk -l
   
  Disk /dev/sda: 160.0 GB, 160041885696 bytes
  255 heads, 63 sectors/track, 19457 cylinders
  Units = cylinders of 16065 * 512 = 8225280 bytes
  
 Device Boot  Start End  Blocks   Id  System
  /dev/sda1   1243219535008+  83  Linux
  /dev/sda22433   19457   136753312+   5  Extended
  /dev/sda524333648 9767488+  83  Linux
  /dev/sda63649608019535008+  83  Linux
  /dev/sda76081   1580678124063+  83  Linux
  /dev/sda8   15807   16049 1951866   82  Linux swap / Solaris
  /dev/sda9   16050   16657 4883728+  83  Linux
  /dev/sda10  16658   17265 4883728+  83  Linux
  /dev/sda11  17266   17873 4883728+  83  Linux
  /dev/sda12  17874   1945712723448+  83  Linux
+ 
+ 
+ sda12 is a dmcrypt-partition

-- 
installer: partman_auto.py: need more than 1 value to unpack
https://launchpad.net/bugs/95734

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 89581] Re: Undefined symbol in Xorg tdfx server

2007-03-08 Thread mherweg
I confirm this bug:
It was impossoble to start a a kubuntu 6.10 live/installer CD , the same with 
LinuxMint 2.2 which is based on Ubuntu 6.10:
I tried different boot options but always ended with an X Cursor from the 
X-Server , then black screen and Keyboard  Mous not responding.
After changing Hardware from the Voodoo 3 PCI Card to a modern Nvidia AGP Card 
everything worked fine.


** Description changed:

  Binary package hint: xserver-xorg-video-tdfx
  
  The patch referenced here:
  
  http://lists.freedesktop.org/archives/xorg/2006-August/017472.html
  
  Will fix said server.  Otherwise try booting the normal Edgy install CD
  of any Ubuntu variant on a machine with a 3dfx Voodoo card.  It will
  hang, fail to login, and other such fun stuff.  The patch provides an
  appropriate prototype, and with the patch installed Edgy mostly works.
+ 
+ 
+ I can confirm this bug: 
+ It was impossoble to start a a kubuntu 6.10 live/installer CD , the same with 
LinuxMint 2.2 which is based on Ubuntu 6.10:
+ I tried different boot options but always ended with an X Cursor from the 
X-Server , then black screen and Keyboard  Mous not responding.
+ After changing Hardware from the Voodoo 3 PCI Card to a modern Nvidia AGP 
Card everything worked fine.

** Description changed:

  Binary package hint: xserver-xorg-video-tdfx
  
  The patch referenced here:
  
  http://lists.freedesktop.org/archives/xorg/2006-August/017472.html
  
  Will fix said server.  Otherwise try booting the normal Edgy install CD
  of any Ubuntu variant on a machine with a 3dfx Voodoo card.  It will
  hang, fail to login, and other such fun stuff.  The patch provides an
  appropriate prototype, and with the patch installed Edgy mostly works.
- 
- 
- I can confirm this bug: 
- It was impossoble to start a a kubuntu 6.10 live/installer CD , the same with 
LinuxMint 2.2 which is based on Ubuntu 6.10:
- I tried different boot options but always ended with an X Cursor from the 
X-Server , then black screen and Keyboard  Mous not responding.
- After changing Hardware from the Voodoo 3 PCI Card to a modern Nvidia AGP 
Card everything worked fine.

-- 
Undefined symbol in Xorg tdfx server
https://launchpad.net/bugs/89581

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs