date:20090711

[Bug 63352] Re: Creative labs X-Fi sound card unsupported

2009-07-11 Thread Susan Cragin

Go to the Ubuntu sound problems web site and follow instructions. 
http://ubuntuforums.org/showthread.php?t=205449

If that doesn't work, try the following:

sudo apt-get --purge remove linux-sound-base alsa-base alsa-utils alsa-source
sudo apt-get install build-essential linux-headers-$(uname -r) module-assistant 
alsa-source
sudo dpkg-reconfigure alsa-source
sudo module-assistant a-i   alsa-source
reboot

-- 
Creative labs X-Fi sound card unsupported
https://bugs.launchpad.net/bugs/63352
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/listinfo/ubuntu-bugs

[Bug 397498] Re: package dpkg 1.14.24ubuntu2 failed to install/upgrade:

2009-07-11 Thread Christopher

Update Manager has resumed its normal behavior. Updates, which were
grayed out before, even though they were selected are visible again and
I can scroll down to see them all and check the content.

Unless it re-occurs, this bug can be closed.

-- 
package dpkg 1.14.24ubuntu2 failed to install/upgrade: 
https://bugs.launchpad.net/bugs/397498
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/listinfo/ubuntu-bugs

[Bug 398148] [NEW] .aiff not readable in ubuntu

2009-07-11 Thread tussi

Public bug reported:

Binary package hint: rhythmbox

.aiff files of CD-R not readable

ProblemType: Bug
Architecture: i386
Date: Sat Jul 11 14:49:51 2009
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/rhythmbox
Package: rhythmbox 0.11.5-0ubuntu8
PackageArchitecture: i386
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: rhythmbox
Uname: Linux 2.6.24-24-generic i686

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


** Tags: apport-bug

-- 
.aiff not readable in ubuntu
https://bugs.launchpad.net/bugs/398148
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/listinfo/ubuntu-bugs

[Bug 398148] Re: .aiff not readable in ubuntu

2009-07-11 Thread tussi


** Attachment added: Dependencies.txt
   http://launchpadlibrarian.net/28908595/Dependencies.txt

** Attachment added: ProcMaps.txt
   http://launchpadlibrarian.net/28908596/ProcMaps.txt

** Attachment added: ProcStatus.txt
   http://launchpadlibrarian.net/28908597/ProcStatus.txt

-- 
.aiff not readable in ubuntu
https://bugs.launchpad.net/bugs/398148
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/listinfo/ubuntu-bugs

[Bug 398151] [NEW] nautilus open terminal usability

2009-07-11 Thread Ingo86

Public bug reported:

Binary package hint: nautilus-open-terminal

Hi,
nautilus-open-terminal is really terrible about usability for three main 
reasons:

- There are no shortcuts, already reported here 
https://bugs.launchpad.net/ubuntu/+source/nautilus-open-terminal/+bug/162352
Kde has it, and it's absolutely useful. I think ubuntu team should have to 
search for a shortcut and add this package to the ubuntu default distribution 
(not a detached package as it is now, it's too much useful opening a terminal 
in the correct directory with one click).

- You have to make two clicks to open a terminal. Why it doesn't put an
icon inside the nautilus main toolbar near search? One click to open
the terminal, not more.

- Open inside the terminal is reported under Edit and under File. Why two 
times? One is enough.
Thank you,
Ingo86

** Affects: nautilus-open-terminal (Ubuntu)
 Importance: Undecided
 Status: New

-- 
nautilus open terminal usability
https://bugs.launchpad.net/bugs/398151
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/listinfo/ubuntu-bugs

[Bug 398114] Re: grub-pc fs type warnings (karmic)

2009-07-11 Thread dino99

** Summary changed:

- grub2 fs type warnings (karmic)
+ grub-pc fs type warnings (karmic)

** Description changed:

  Having some problem to boot:
  
- used grub2, os-prober on 3 hdd: 2 pata 1 sata (sdb xp ntfs, sdc
+ used grub-pc, os-prober on 3 hdd: 2 pata 1 sata (sdb xp ntfs, sdc
  jaunty32/karmic32 ext3, sda jaunty64 ext4)
  
  The troubles does not exist before using grub2  os-prober.
  
  When i want to boot , it often fail: grub reboot or it freeze or exit
  with warning (for example: invalid compressed format (err=1) or else)
  or begin to start  fall in a maintenace shell.
  
  Same things if i erase splash or add acpi=off nolapic. Most of the time
  it boot at the third time but always fall in a maintenance shell: need
  to exit from root and then boot correctly from normal boot option
  choice. Need to power off to try booting again.
  
  Investigating, i found that os-prober check for all the non-existing fstype: 
don't know how to stop that. 
  /var/lib/os-prober/ only have 1 file (labels), not subfolder /mount/boot as 
seen in user.log  returned by 50mounted-tests
  
  ProblemType: Bug
  Architecture: i386
  Date: Sat Jul 11 11:54:10 2009
  DistroRelease: Ubuntu 9.10
  HibernationDevice: RESUME=UUID=f4216733-a2b7-4818-9852-9bb41d54d87c
  MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
  NonfreeKernelModules: nvidia
  Package: linux-image-2.6.31-2-generic 2.6.31-2.17
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-2-generic 
root=UUID=f23f677d-7a16-4190-a2fa-c668e9e0a3ac ro quiet splash
  ProcEnviron:
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-2.17-generic
  RelatedPackageVersions: linux-backports-modules-2.6.31-2-generic N/A
  SourcePackage: linux
  Uname: Linux 2.6.31-2-generic i686
  dmi.bios.date: 07/10/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2801
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2801:bd07/10/2008:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

-- 
grub-pc fs type warnings (karmic)
https://bugs.launchpad.net/bugs/398114
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/listinfo/ubuntu-bugs

RE: [Bug 394556] Re: multiple running instances of update-motd cause errors

2009-07-11 Thread Stephen Sentoff

Yes, I was using the lockfile from the procmail package.

But I agree flock should work just as well. I saw both were available
and arbitrarily picked lockfile for my testing.

Thanks for your work.

--
Steve

Date: Fri, 10 Jul 2009 20:14:13 +
From: dustin.kirkl...@gmail.com
To: steve30...@hotmail.com
Subject: [Bug 394556] Re: multiple running instances of update-motd cause
errors

Nevermind, I found flock(1). It's working like a champ ;-)

:-Dustin

** Changed in: update-motd (Ubuntu)
Status: Triaged = In Progress

--
multiple running instances of update-motd cause errors
https://bugs.launchpad.net/bugs/394556
You received this bug notification because you are a direct subscriber
of the bug.

Status in “update-motd” package in Ubuntu: In Progress

Bug description:
Binary package hint: update-motd

Description: Ubuntu 9.04
Release: 9.04
update-motd:
Installed: 1.11.1

When update-motd is executed out of /etc/cron.d, the instances are all set to
run at the same minute (if they run at all). This means that up to five
instances of update-motd can be started simultaneously. This causes two
problems--

1. The method used to lock out simultaneous executions is not very robust.
The $NEW file, which is used as a synchronization lock, is tested early in
the script, but not created until later. This leaves a window open for
multiple scripts to get started, and then collide with each other, ultimately
messing up the resulting message of the day. At least on my machine, this
error happens about half the time on each hour. The code to nice the
process seems to be the part that opens the window the widest. Using
lockfile to create a semaphore for synchronization corrects this flaw. I've
created a modified version of update-motd and included it as an attachment.

2. By design, only one instance of update-motd can run at a time, and others
just exit. However, this means that some of the work scheduled for the same
minute doesn't get done (assuming the synchronization works correctly). But
this isn't really what you want--if both the 10-minute and the hourly script
are scheduled on the hour, you want both to execute serially. I can see two
possible solutions to this:
a) Alter the lockfile code in the attachment to allow retries. Changing -r0
to -r5 in the attached code would allow all the instances that could possibly
be scheduled to take their turns to run. The downside of this solution is
that if update-motd is run manually, it could take up to 40 seconds to fail,
when the lock is in place. Even the 8 second delay for a single retry is
likely to be confusing to the user.
b) Alter the update-motd crontab entry in /etc/cron.d so that the instances
of update-motd don't coincide. For example, one job on the 10-minute
boundaries, one 1 minute after the hour, one 2 minutes after midnight each
day, one 3 minutes after midnight each week, one 4 minutes after midnight
each month. This change would also reduce the likelihood of multiple running
instances to the point that the current method of synchronization with the
$NEW file would rarely cause a problem.

_
Hotmail® has ever-growing storage! Don’t worry about storage limits.
http://windowslive.com/Tutorial/Hotmail/Storage?ocid=TXT_TAGLM_WL_HM_Tutorial_Storage_062009

--
multiple running instances of update-motd cause errors
https://bugs.launchpad.net/bugs/394556
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

< 1 2 3 4 5 6 7 8 9 >

201 - 300 of 809 matches

Mail list logo