** Changed in: linux (Ubuntu)
Assignee: Ubuntu Kernel Team (ubuntu-kernel-team) => Ubuntu Kernel ACPI
Team (ubuntu-kernel-acpi)
Status: Triaged => In Progress
--
[Hardy] ACPI Embedded Controller (EC) stops boot when kernel boot 'quiet'
option is enabled
https://bugs.launchpad.net/bu
Right, I know what is causing this now. We have a complex interaction of
three things:
1. Early EC initialisation introduced by commit
c04209a7948b95e8c52084e8595e74e9428653d3
2. Timing (especially on multiprocessor / multitasking systems)
3. Possible 'problem' with ACPI DSDT embedded controller
** Bug watch added: Linux Kernel Bug Tracker #10444
http://bugzilla.kernel.org/show_bug.cgi?id=10444
** Also affects: linux via
http://bugzilla.kernel.org/show_bug.cgi?id=10444
Importance: Unknown
Status: Unknown
--
[Hardy] ACPI Embedded Controller (EC) stops boot when kernel boo
I haven't seen this in the daily builds since although I'm tempted to
think it could be related to bug #191137 to which the work-around is
removing the "quiet" kernel boot option.
--
Hardy Beta Live CD Kernel Panic
https://bugs.launchpad.net/bugs/206002
You received this bug notification because
Václav, your result is interesting, thank you. I didn't have time to
endlessly repeat the reboot tests when I did the DSDT patch so it is
possible that it was in some way coincidental that the kernel didn't
crash those times.
Since doing that patch and having time to think about things more I'm
le
Run the program from a terminal and use strace to capture all file
access:
$ strace -o strace.log gnutalk
Close it, then search the strace log for the access to libgail:
$ grep 'libgail' strace.log
You'll see something like this:
access("/home/tj/.gtk-2.0/2.10.0/i486-
Not an issue with Kino, but with the OS device permissions
** Changed in: kino (Ubuntu)
Status: New => Invalid
--
Kino: libraw1394 -> plugdev does not work in Gutsy
https://bugs.launchpad.net/bugs/133862
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This has always been an issue for IEEE 1394 AV/C DV devices on Ubuntu
since Edgy at least. The issue is that the user must have read/write
permissions to /dev/raw1394 and the defaults have been changed to
accommodate disk devices:
$ ls -l /dev/raw1394
crw-rw 1 root disk 171, 0 2007-09-06 05:23
The reason 'disk' doesn't appear in the Gnome > Administration > Users
and Groups "Manage Groups" dialog is that it only lists groups with a
GID of 100 or higher, except for root (GID=0).
'disk' is a system-level group (<100) that shouldn't be available to
users.
I don't think this can be classif
?
** Changed in: linux-source-2.6.22 (Ubuntu)
Assignee: (unassigned) => TJ
** Changed in: linux-source-2.6.22 (Ubuntu)
Importance: Undecided => Low
--
Thinkpad LED does not blink when going to sleep (regression)
https://bugs.launchpad.net/bugs/134739
You received this bug notification b
Confirmed here with Gutsy Tribe-5 64-bit and Firefox.
After installing (no errors or warnings installation) Firefox
about:plugins reported it wasn't installed.
After finding the article at
http://blog.nixternal.com/2007.08.16/flash-and-64-bit-systems/
And doing:
$ nspluginwrapper -i /usr/lib/f
Assigning to MOTU since dpkg-query -s reports "Maintainer: Ubuntu MOTU
Developers <[EMAIL PROTECTED]>". If this is inappropriate,
please re-assign.
** Changed in: flashplugin-nonfree (Ubuntu)
Importance: Undecided => Medium
Assignee: (unassigned) => MOTU
Target: None => ubuntu-7.10-
Public bug reported:
Binary package hint: wine
I was confused at not being able to find Wine in the Gutsy 64-bit
repository, then checked the build log and saw that back in July the
build failed.
https://launchpad.net/ubuntu/+source/wine/0.9.42-0ubuntu1/+build/369432
** Affects: wine (Ubuntu)
*** This bug is a duplicate of bug 43324 ***
https://bugs.launchpad.net/bugs/43324
I neglected to mention since I thought it obvious, but winehq have a a
64-bit build of 0.9.42 for Feisty (which so far has worked without
issues on Gutsy) at:
http://wine.budgetdedicated.com/archive/index.html
*** This bug is a duplicate of bug 43324 ***
https://bugs.launchpad.net/bugs/43324
MOTU-media is listed as the maintainer of the source package in the
source-package portlet at
https://launchpad.net/ubuntu/+source/wine
The bug *is* confirmed since buildd clearly reports "Status: Failed to
b
You probably need to mount using the options -o follow_symlinks and/or
-o transform_symlinks
** Changed in: sshfs-fuse (Ubuntu)
Assignee: (unassigned) => TJ
Status: New => Incomplete
--
symbolic links on remote disk do not work in sshfs
https://bugs.launchpad.net/bugs/1378
I'm re-opening this bug since I can reproduce it repeatedly with Totem
2.19.90 using GStreamer 0.10.14 on Gutsy Tribe-5 64-bit.
Manually ejecting the disc by pressing the drawer button works, as does
"eject /dev/dvd"
Insert DVD (in this case encrypted disks), Totem auto-starts and plays
the disk.
I've tested the new gnome-session patch attached to the upstream bug but
so far it hasn't produced sound, and it seems to lose the Ubuntu
enhanced log-out dialog.
However, with standard Gutsy gnome-session 2.19.92 the sound *is*
played if Accessible Login sound is set:
1. System > Preferences >
This is done in Gutsy.
Both bluetooth-applet and gnome-obex-server are added to the Session
start-up list.
** Changed in: gnome-bluetooth (Ubuntu)
Importance: Undecided => Low
Status: New => Fix Released
--
feisty: gnome-bluetooth installation requires manual addition to session
star
Public bug reported:
Binary package hint: gnome-power-manager
Gutsy Tribe-5 64-bit, Nvidia restricted driver 100.14.11.
On a laptop PC with Nvidia GeForce Go 7600. External display connected
to S-Video port. Xorg configured with two screens.
:0.0 - standard DFP (laptop lid)
:0.1 - S-Video displ
Status: Incomplete => Invalid
** Changed in: sshfs-fuse (Ubuntu)
Assignee: TJ => (unassigned)
--
symbolic links on remote disk do not work in sshfs
https://bugs.launchpad.net/bugs/137875
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug co
Confirming this affects Gutsy Tribe-5 64-bit.
--
GDM Startup Fails With Accessible login
https://bugs.launchpad.net/bugs/107383
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.c
Confirmed on Gutsy Tribe-5 64-bit with snd-hda-intel and SigmaTel
STAC9872AK, Volume applet 2.19.91 using gstreamer 0.10.
Actual mute status of sound card isn't affected, but the applet icon
randomly shows 'muted' status (both Icon and menu-item) in response to
adjusting the slider. The control m
Interesting result: I've built the mixer applet from source and
installed it and can't reproduce the random mute indicator.
I've compared the build logs from buildd and my local build and can't
see anything different in the mixer build. The only thing I can see si
that buildd used gcc 4.2.1 wherea
Confirming John Yate's fix with Gusty Tribe-5 64-bit:
1. Add fbcon to /etc/initramfs-tools/modules
2. Update initrd.img
3. Restart
$ sudo sh -c "echo 'fbcon' >>/etc/initramfs-tools/modules"
$ sudo update-initramfs -u
--
tty[1-6] are active but display nothing in Gutsy
https://bugs.launchpad.net
I compared the initrd image of Feisty with Gutsy:
Feisty /conf/modules:
capability
vesafb
fbcon
dm_mod
unix
Feisty has the drivers:
/lib/modules/2.6.20-16-generic/kernel/drivers/video/vga16fb.ko
/lib/modules/2.6.20-16-generic/kernel/drivers/video/vesafb.ko
/lib/modules/2.6.20-16-generic/kernel/
With Gutsy Tribe-5 64-bit with all updates to 2007-09-10 this now works
here, although I can't explain why! Doubtless one of the countless
recent updates is to thank.
Can others please check and report?
--
Intel HDA No sound after Standby
https://bugs.launchpad.net/bugs/78257
You received this b
If you do Tools/Options OpenOffice.org > Appearance - Custom Colours - Text
Document
and turn off Field-Shadings they remain, so it does look like a bug in OOo, not
some desktop/theme/compiz settings.
--
Unable to disable field shadings
https://bugs.launchpad.net/bugs/134415
You received this b
Confirmed here with openoffice.org-core 1:2.3.0oog680m1-1ubuntu3 and
Writer on Gutsy Tribe-5 64-bit.
--
Unable to disable field shadings
https://bugs.launchpad.net/bugs/134415
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubu
With Gutsy 64-bit Tribe-5 + updates of 10th September 2007 this no
longer appears to be a problem.
--
[gutsy] microphone doesn't work after kernel and kernel-modules update
https://bugs.launchpad.net/bugs/134125
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
Binary package hint: zope2.10
Popular products such as Plone 3 require zope 2.10.4 (released 4th July
2007). Gutsy is going to ship with zope 2.10.3 (released 25th March
2007).
** Affects: zope2.10 (Ubuntu)
Importance: Undecided
Status: New
--
Update to 2.10.
Workaround:
Download zope 2.10.4-final, build it and install over the Ubuntu
package.
$ sudo apt-get install python2.4-dev
$ wget http://www.zope.org/Products/Zope/2.10.4/Zope-2.10.4-final.tgz
$ tar -xzf Zope-2.10.4-final.tgz
$ cd Zope-2.10.4-final
$ ./configure --prefix=/usr/lib/zope.210
$ make
Indeed - I spent several hours trying to determine and fix the issue.
Not being able to use the Alternate installer, I gave up on it.
The problem seemed to be in the initrd trying to mount the hard drives
on the /cdrom mount-point:
mount: Mounting /dev/sda2 on /cdrom failed: No such device
mount:
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => Confirmed
--
while installing gutsy partition manager fails( i386 )
https://bugs.launchpad.net/bugs/123364
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bug
I captured all the logs from this issue and am investigating in as much
as it is possible. I've attached the log tarball to this comment for
anyone else who wants to take a look.
** Attachment added: "Tarball containing all Live environment log files"
http://launchpadlibrarian.net/8528232/gutsy
*** This bug is a duplicate of bug 126964 ***
https://bugs.launchpad.net/bugs/126964
** This bug has been marked a duplicate of bug 126964
gutsy livefs causes random hangs or modprobe crashes
--
Desktop hangs on Gutsy Tribe 3 amd64 Live CD
https://bugs.launchpad.net/bugs/127070
You receiv
Looks okay to me Phillip.
I did four boots with it and each one loaded the Gnome desktop
correctly. There were various errors reported during start-up with udev
and acpi (from scripts) but I suspect they're the result of other
issues. One time Gnome reported HAL failed at start but I suspect that
Nice work-around Willem!
I've enhanced your script to make it more modular. Users can install
this script and not have to check and set the PCI device ID as the
script will figure it out.
#!/bin/bash
# this file is /etc/acpi/resume.d/66-snd-hda-intel.sh
# workaround for HDA resume bug on 2.6.20 (
Martin.
Which kernel version are you using (output from uname -a) ?
I am currently debugging what may be the same issue on a Sony Vaio where
it resumes immediately after suspend. I have a specially built debug
kernel, linux-image-2.6.20-16-generic package (30MB), that reports the
wake-up event im
in: linux-source-2.6.20 (Ubuntu)
Assignee: (unassigned) => TJ
Status: New => In Progress
** Changed in: linux-source-2.6.22 (Ubuntu)
Assignee: (unassigned) => TJ
Status: New => In Progress
** Changed in: linux-source-2.6.20 (Ubuntu)
Assignee: TJ => Ubu
This could be a knock-on effect of other problems with Gutsy. Your other
report ought to be solved first since if Gnome config is broken it is
likely gnome-power-manager isn't operating correctly.
--
[Gutsy] suspend and hibernate don't work with kernel 2.6.22-8.18
https://bugs.launchpad.net/bugs/
Fix applied to Andrew Morton's -mm tree in January 2007
** Changed in: linux-source-2.6.20 (Ubuntu)
Status: In Progress => Fix Released
** Changed in: linux (upstream)
Status: In Progress => Fix Released
--
Disk Read Errors during boot-time caused by probe of invalid partitions
ht
I asked the user to create this report after discussion on IRC #ubuntu
** Changed in: linux-source-2.6.20 (Ubuntu)
Sourcepackagename: None => linux-source-2.6.20
Assignee: (unassigned) => Ubuntu Kernel ACPI Team
--
Hibernate doesn't work
https://bugs.launchpad.net/bugs/128440
You received t
Allocated to xorg since shutting down Gnome prior to halting the system
solves the issue. Reports from other distributions suggest the same
cause.
** Also affects: xorg (Ubuntu)
Importance: Undecided
Status: New
** Changed in: xorg (Ubuntu)
Status: New => Confirmed
--
snd_hda_i
>From working with snd_hda_intel and ACPI I'm reasonably confident this
isn't an ACPI bug.
** Changed in: linux-source-2.6.22 (Ubuntu)
Status: Confirmed => Invalid
--
snd_hda_intel fails to unload (or unload correctly) on shut down; laptop fails
to halt
https://bugs.launchpad.net/bugs/12
Public bug reported:
Binary package hint: hal
On 32-bit Feisty:
$ lshal
lshal: symbol lookup error: lshal: undefined symbol:
libhal_ctx_set_global_interface_lock_acquired
$ lshal --version
lshal version 0.5.9
$ uname -a
Linux bagoas 2.6.20-16-generic #2 SMP Thu Jun 7 20:19:32 UTC 2007 i686 GN
age1
$ apt-get install -t feisty-backports libhal1
** Changed in: feisty-backports (upstream)
Assignee: (unassigned) => TJ
Status: New => Fix Released
** Changed in: hal (Ubuntu)
Assignee: (unassigned) => TJ
Status: New => Fix Released
--
feisty-backp
lib/hal/scripts/linux/hal-luks-setup-linux -
#!/bin/bash
# Copyright (C) 2005 W. Michael Petullo <[EMAIL PROTECTED]>
# Copyright (C) 2006 David Zeuthen <[EMAIL PROTECTED]>
# Copyright (C) 2007 TJ <[EMAIL PROTECTED]>
#
# This program is free software; you can redistrib
Accidentally got the default selection of Baltix in error - please
remove this Distro from the bug
** Changed in: gnome-mount (Baltix)
Status: New => Invalid
--
hal: Patch to auto-mount LUKS key-file encrypted volumes
https://bugs.launchpad.net/bugs/133520
You received this bug notificati
match the UUID, get the target name and the key-file,
and call cryptsetup luksOpen.
- /usr/lib/hal/scripts/linux/hal-luks-setup-linux -
#!/bin/bash
# Copyright (C) 2005 W. Michael Petullo <[EMAIL PROTECTED]>
# Copyright (C) 2006 David Zeuthen <[EMAI
uksOpen.
- /usr/lib/hal/scripts/linux/hal-luks-setup-linux -
#!/bin/bash
# Copyright (C) 2005 W. Michael Petullo <[EMAIL PROTECTED]>
# Copyright (C) 2006 David Zeuthen <[EMAIL PROTECTED]>
# Copyright (C) 2007 TJ <[EMAIL PROTECTED]>
#
# Thi
- /usr/lib/hal/scripts/linux/hal-luks-setup-linux -
#!/bin/bash
# Copyright (C) 2005 W. Michael Petullo <[EMAIL PROTECTED]>
# Copyright (C) 2006 David Zeuthen <[EMAIL PROTECTED]>
# Copyright (C) 2007 TJ <[EMAIL PROTECTED]>
#
# This progr
/usr/lib/hal/scripts/linux/hal-luks-setup-linux -
#!/bin/bash
# Copyright (C) 2005 W. Michael Petullo <[EMAIL PROTECTED]>
# Copyright (C) 2006 David Zeuthen <[EMAIL PROTECTED]>
# Copyright (C) 2007 TJ <[EMAIL PROTECTED]>
#
# This program is f
---
#!/bin/bash
# Copyright (C) 2005 W. Michael Petullo <[EMAIL PROTECTED]>
# Copyright (C) 2006 David Zeuthen <[EMAIL PROTECTED]>
# Copyright (C) 2007 TJ <[EMAIL PROTECTED]>
#
# This program is free software; you can redistribute it and/or modify
# it u
cryptsetup luksOpen.
- /usr/lib/hal/scripts/linux/hal-luks-setup-linux -
#!/bin/bash
# Copyright (C) 2005 W. Michael Petullo <[EMAIL PROTECTED]>
# Copyright (C) 2006 David Zeuthen <[EMAIL PROTECTED]>
# Copyright (C) 2007 TJ <[EMAIL PROT
This is the patch against the gnome-mount-0.5 package (src/Makefile.am
and src/gnome-mount.src)
A new compile flag CRYPTO_KEYFILE is defined to enable the keyfile
support.
** Attachment added: "gnome-mount crypto key-file support"
http://launchpadlibrarian.net/8891314/gnome-mount-0.5-crypto_ke
** Bug watch added: GNOME Bug Tracker #468335
http://bugzilla.gnome.org/show_bug.cgi?id=468335
** Also affects: gnome-mount (upstream) via
http://bugzilla.gnome.org/show_bug.cgi?id=468335
Importance: Unknown
Status: Unknown
--
hal: Patch to auto-mount LUKS key-file encrypted volu
ll match the UUID, get the device name and the key-file,
and call cryptsetup luksOpen.
- /usr/lib/hal/scripts/linux/hal-luks-setup-linux -
#!/bin/bash
# Copyright (C) 2005 W. Michael Petullo <[EMAIL PROTECTED]>
# Copyright (C) 2006 David Zeuthen &l
This looks like a hal script issue. Marking it as 'hal' based on hacking
gnome-mount/cryptsetup/hal scripts recently.
** Also affects: hal (Ubuntu)
Importance: Undecided
Status: New
--
init.d/cryptdisks doesnt create symlinks in /dev/disk/by-*
https://bugs.launchpad.net/bugs/82343
You
Feisty 32-bit, 2.6.20-16-generic with ipw3945 and e100 on a Sony Vaio
VGN-FE41Z.
Using just the ipw3945 wireless connection on a WPA2 network.
After resume from suspend NetworkManager reported no network devices.
Restarting NetworkManager didn't seem to solve it.
The solution was to use mlaverdi
ACEDBYhsfmodem//' snd-hda*
$ sudo depmod -a
$ sudo modprobe snd-hda-intel
** Affects: linux-source-2.6.20 (Ubuntu)
Importance: Undecided
Assignee: TJ
Status: Fix Released
--
snd-hda-intel missing after uninstalling Linuxant softModem driver
https://bugs.launchpad.net/bug
Updated to reflect status of report
** Changed in: linux-source-2.6.20 (Ubuntu)
Assignee: (unassigned) => TJ
Status: New => Fix Released
--
snd-hda-intel missing after uninstalling Linuxant softModem driver
https://bugs.launchpad.net/bugs/124794
You received this bug notifi
I'm not sure if this report needs re-opening or a new one creating.
Using CPU Frequency Scaling Monitor 2.18.0 on Feisty 32-bit with Intel
Core 2 Duo T7200, when I have 2 panel applets active (one for each core)
if a change is made to one core it is applied to both.
Although this seems sensible t
Public bug reported:
Binary package hint: gnome-applets
Feisty 32-bit 2.6.20-16-generic on Sony Vaio VGN-FE41Z with Intel Core 2
Duo T7200.
Using CPU Frequency Scaling Monitor 2.18.0.
With 2 instances of the panel applet active (one for each core), after a
suspend/resume cycle the applet monito
I'm hearing the same problem on a Sony Vaio VGN-FE41Z.
I read where you say "Unloading/reloading the snd-hda-intel module makes
the soundcard work again correctly". I've been unable to do that because
the module is always in-use although I don't know by what:
$ sudo modprobe -r snd-hda-intel
FATA
Re: unloading the module. It was in-use even after I stopped GDM and was
working from a console.
I've been debugging this issue and have made a little progress, albeit
not the kind we want.
The difference in the outputs reported here and in bug #55071 pre- and
post-suspend of codex#0 is not of co
I decided to track the interrupt/DMA enabling/disabling. I'll put my
notes here in case others want to investigate.
I analysed the sequence of operations in hda_intel.c::azx_suspend(),
azx_resume() and the device initialisation functions.
I noticed that azx_suspend() calls snd_hda_suspend() then
Oh cool! Someone else that knows how to hack :)
I've been reading the Intel HDA Programmers Reference Manual
(http://www.intel.com/design/chipsets/hdaudio.htm) and from what I've
learned so far the problem appears to be with the handling of the output
buffers. Here's the description of what should
Funny how you can arrive at the same point from different directions. I
noticed in your tracing that int_cnt had far more interrupts (for the
same file) just after resume than when the module had been freshly
loaded (389 vs 11) and had traced through to the posbuf from struct
azx_dev:
hda_intel.c:
hda_intel.c:1392:
azx_init_stream() {
...
azx_dev->posbuf = (u32 __iomem *)(chip->posbuf.area + i * 8);
--
snd-hda-intel: distorted sound after resume, until the module is reloaded
https://bugs.launchpad.net/bugs/100114
You received this bug notification because you are a member of Ubuntu
B
azx_setup_controller() is called azx_pcm_prepare():
snd_printdd("azx_pcm_prepare: bufsize=0x%x, fragsize=0x%x,
format=0x%x\n",
azx_dev->bufsize, azx_dev->fragsize, azx_dev->format_val);
azx_setup_periods(azx_dev);
azx_setup_controller(chip, azx_dev);
N
Reading this extract from the HDA PRM in conjunction with
azx_setup_controller() (note my ***...*** highlights) might suggest a
problem with "...the hardware may still have pre-fetched descriptors
that will not be flushed when the stream is restarted...":
4.6.6
After the RUN bit has been set, the
Thanks for that report, it was just what I needed. I was already
tracking the various code responsible for updating posbuf and your trace
has confirmed some of what I was expecting. There are several reasons
why posbuf/pos won't be updated so we should try eliminating
possibilities.
In snd_pcm_upd
Yes, I agree. I found some time yesterday to build the alsa-core and
snd-hda modules myself and have been watching the updating of the
hw_ptr_interrupt. I've attached the log. Also, the line
pos -= pos % runtime->min_align;
is, if you read it carefully, not intended to update pos but simply to
en
I'm afraid I'm seeing no difference here. I had previously checked TCSEL
because of the comment in the head of azx_init_chip(), and I had also
made sure that azx_resume() was called, and in-turn was calling
azx_init_chip().
I also put a check of the value of TCSEL in azx_init_chip() to see what
va
Sorry - I pasted the wrong line from 'config'!
I see what you mean about TCSEL being reset to 07 when a sound is
played, and when I do 'hexedt config' and change 0x44 to 0, the sound is
corrected - nice one.
So the question is, is there another chip reset operation between
azx_resume() and playba
OK, it seems we have identified the reason for this problem.
Willem and I worked together on tracing the value of TCSEL after resume.
The code that finally pinpointed the issue was a kernel timer started in
azx_resume() and stopped in azx_pcm_open() with a jiffie interval of 10,
which appears to e
What we should have made clear in the two comments above is that we
found by monitoring the PCI config space when the ALSA drivers weren't
loaded that the TCSEL value was still being changed to 0x07 from 0x0.
That was when we decided to implement a timer to find out when the value
was changing.
--
Is it significant that upon resume the 2nd CPU is resumed *after* PCI
config has been written back to the device and it has been reinitialised
by its driver? When cold-starting the CPU has been started before the
PCI device is configured.
See the attached log-file that compares the relevant sectio
Changed status to "Fix Committed" now cause is known and patch is
available.
** Changed in: linux-source-2.6.20 (Ubuntu)
Status: Confirmed => Fix Committed
--
snd-hda-intel: distorted sound after resume, until the module is reloaded
https://bugs.launchpad.net/bugs/100114
You received this
I've tested the latest Gutsy kernel from git (2.6.22-8.18) and found it
doesn't suffer from this bug. In that, the 2nd CPU is started before the
PCI devices are resumed. After resume the HDA device PCI config shows
the TCSEL register is 0x00.
Therefore I'm attaching a patch against Feisty's 2.6.20
I'm seeing a similar result with Tribe-2 when choosing to do a Manual
Partition on the 30GB PATA IDE drive in a Sony Vaio SRX51 notebook.
Starting from an empty hard disk with no partition table, boot Gutsy
32-bit from LiveCD and choose to Install. When reaching the Partitioner
choose the Manual/A
After configuring the partitions using fdisk I restarted Ubiquity, went
to the Partition Manual stage, and tried to simply assign the mount
points to the existing partitions. It allowed me to set partition #1 to
/boot, but after making the changes for #2 to be / it hung up and needed
killing.
--
I've tried various ways to get around this problem, from trying to
assign the mount-points last-to-first (#4, #3, #2, #1) to doing one,
then backing out to the previous step in Ubiquity, and then advancing
again (trying to do one change at a time) but I've so far found no
solution.
Can I therefore
I've discovered some error-reporting from Ubiquity in user.log:
ubiquity[8942]: Ubiquity 1.5.4
ubiquity[8942]: log-output -t ubiquity laptop-detect
ubiquity[8942]: switched to page stepWelcome
ubiquity[8942]: Step_before = stepWelcome
ubiquity[8942]: debconffilter_done: ConsoleSetup (current: Cons
To compare, I've gone through the same procedure with **Feisty** 32-bit
LiveCD and it works so maybe the problem can be found by comparing the
diffs of the two code-bases.
--
while installing gutsy partition manager fails( i386 )
https://bugs.launchpad.net/bugs/123364
You received this bug notifi
In respect of:
* sound is garbled/loops strangely
I posted a patch to fix this in another bug report:
"snd-hda-intel: distorted sound after resume, until the module is
reloaded"
https://bugs.launchpad.net/ubuntu/+source/linux-
source-2.6.20/+bug/100114
--
Intel HDA busted following resume
Confirmed here with LiveCD daily build of Gutsy 32-bit 20070912.1 on
Sony Vaio PCG-SRX51P.
[ 429.896000] BUG: unable to handle kernel NULL pointer dereference at virtual
address 00a0
[ 429.896000] printing eip:
[ 429.896000] c017ebbe
[ 429.896000] *pde =
[ 429.896000] Oops: 000
Adding linux-source-2.6.22 to this bug to bring attention to it
affecting Gutsy.
Running Gutsy 64-bit Tribe-5 + constant updates the root partition has
just run out of space:
$ df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda7 5977156 5700308 0
I've been waiting to test it on the same hardware but so far Gutsy won't
install. Latest unionfs BUG issue is scheduled to be fixed for Gutsy
Beta... so let's hope :)
--
Crash - playing from iPod and view Source Properties
https://bugs.launchpad.net/bugs/73145
You received this bug notification b
Public bug reported:
Binary package hint: network-manager
Gutsy 64-bit Tribe-5 + updates to 16th September, 2007.
NetworkManager: 0x2b3af925bc7f in waitpid () from
/lib/libpthread.so.0
On startup NetworkManager consistently fails, leaving
NetworkManagerDispatcher running. Once logged into G
Public bug reported:
Binary package hint: network-manager-gnome
Gutsy Tribe-5 64-bit + updates to 16th September, 2007.
nm-applet no longer displays the animated 'connecting' icons ( the two
dots that change to green when WAP connects, and again on DHCP lease).
Instead, When reconnecting it show
** Description changed:
Binary package hint: network-manager
- Gutsy 64-bit Tribe-5 + updates to 16th September, 2007.
+ Gutsy 64-bit Tribe-5 + updates to 16th September, 2007. Recent updates
+ (from /root/.synaptic/log/)
+
+ 2007-09-07.014923.log:26:network-manager (0.6.5-0ubuntu9) to 0.6.5
On a hunch I uninstalled VMware-server-1.0.3-44356 because I noticed it
was reporting a bridge attached to eth1, which is the WiFi interface.
After the first restart NetworkManager doesn't show this failure. I'll
continue to check on this after each restart and update the bug status
as appropriate
+1 on this.
It could do with some more documentation and localisation.
If the device has already been paired gbtsco won't discover it. The bond
needs to be deleted and the device rediscovered by btsco.
There also needs to be guidance on how to enable playback for the
Ubuntu-default players such
VMWare appears not to be the cause.
Starting the PC this morning from cold NetworkManager has consistently
failed to connect to WiFi - in fact I have had to connect a wired
connection to get any network connectivity. The workaround described
above of restarting NetworkManager(Dispatcher) hasn't so
Public bug reported:
Binary package hint: network-manager
Gutsy 64-bit Tribe-5 + updates to 17th September 2007.
network-manager Version: 0.6.5-0ubuntu11
I've been happily running two Linksys Wifi access points (WRT54GL &
WAP54G) with WPA-PSK using the stock Linksys firmware. Because the
WAP54G
*** This bug is a duplicate of bug 140540 ***
https://bugs.launchpad.net/bugs/140540
The problem is gtk2 updates change the default font-rendering size to 50
To correct it, use this command by doing Alt+F2 (or a terminal if you
can see to type) and
$ gconftool --type float --set /desktop/gno
The problem is gtk2 updates change the default font-rendering size to 50
To correct it, use this command by doing Alt+F2 (or a terminal if you
can see to type) and
$ gconftool --type float --set /desktop/gnome/font_rendering/dpi 96
** Changed in: gtk2-engines (Ubuntu)
Sourcepackagename: gnome-t
** Summary changed:
- Gnome terminal doesn't show fonts
+ [Gutsy update] Gnome application font sizes too small to read
--
[Gutsy update] Gnome application font sizes too small to read
https://bugs.launchpad.net/bugs/140540
You received this bug notification because you are a member of Ubuntu
Bu
801 - 900 of 2922 matches
Mail list logo
