Hi Alessio
The later -rt kernels, .31-4, .31-5, in Karmic don't boot with nvidia
drivers at all, so I can't test if this has been resolved in the newer
releases. This bug is reported elsewhere.
--
suspend/resume failure [non-free: nvidia]
https://bugs.launchpad.net/bugs/408344
You received this
By the way, unlike @Ketil Wendelbo Aanensen I don't have a Flickr
account to delete...
--
Main Gwibber window is blank
https://bugs.launchpad.net/bugs/437562
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
gwibber:
Installed: 2.0.0~bzr465-0ubuntu1
Candidate: 2.0.0~bzr465-0ubuntu1
Version table:
*** 2.0.0~bzr465-0ubuntu1 0
100 /var/lib/dpkg/status
2.0.0~bzr449-0ubuntu1 0
500 http://au.archive.ubuntu.com karmic/universe Packages
I can confirm this problem: The output from
I can confirm the error @Iain Buclaw above, with the 2.6.31-5-rt kernel
in the repositories. The patch is the same as the initial fix, and leads
to a failure to boot.
The failure can take the form of:
- kernel panic
- computer reset
- blank screen and system halt (occasionally so hard that
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/32256986/BootDmesg.txt
** Attachment added: CoreDump.gz
http://launchpadlibrarian.net/32256987/CoreDump.gz
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/32256988/CurrentDmesg.txt
** Attachment
I can confirm a similar issue affecting linux-image-2.6.31-2-rt and this
nvidia-180 version, as well as the updated 185.18.36 driver.
Log lines:
/var/lib/dkms/nvidia/185.18.36/build/nv.c: In function nv_alloc_file_private:
/var/lib/dkms/nvidia/185.18.36/build/nv.c:1897: error: implicit
Public bug reported:
Description:Ubuntu karmic (development branch)
Release:9.10
linux-rt:
Installed: 2.6.29.6.1.1
Candidate: 2.6.29.6.1.1
Version table:
*** 2.6.29.6.1.1 0
500 http://au.archive.ubuntu.com karmic/multiverse Packages
100 /var/lib/dpkg/status
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/29822542/Dependencies.txt
** Attachment added: ProcMaps.txt
http://launchpadlibrarian.net/29822543/ProcMaps.txt
** Attachment added: ProcStatus.txt
http://launchpadlibrarian.net/29822544/ProcStatus.txt
** Attachment
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/29788692/BootDmesg.txt
** Attachment added: CoreDump.gz
http://launchpadlibrarian.net/29788693/CoreDump.gz
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/29788694/CurrentDmesg.txt
** Attachment
Update: This bug does not appear when using the previous 2.6.29.5-2-rt
kernel.
--
WPA/WPA2 networks not accessible with kernel 2.6.29-6-1-rt
https://bugs.launchpad.net/bugs/401688
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Public bug reported:
Description:Ubuntu karmic (development branch)
Release:9.10
linux-image-2.6.29.6-1-rt:
Installed: 2.6.29.6-1.3
Candidate: 2.6.29.6-1.3
Version table:
*** 2.6.29.6-1.3 0
500 http://au.archive.ubuntu.com karmic/universe Packages
100
Uh... What buttons? As in the screenshot, there AREN'T any buttons in
the main window. A click-and-guess approach seems to apply to where the
buttons might be, so i think unusable is pretty fair, actually.
--
[Jaunty] qjackctl has no buttons in its window or close button in title bar
Public bug reported:
Binary package hint: qjackctl
Description:Ubuntu jaunty (development branch)
Release:9.04
qjackctl:
Installed: 0.3.4-0ubuntu2
Candidate: 0.3.4-0ubuntu2
Version table:
*** 0.3.4-0ubuntu2 0
500 http://au.archive.ubuntu.com jaunty/universe Packages
** Attachment added: Screenshot-1.png
http://launchpadlibrarian.net/23161497/Screenshot-1.png
--
[Jaunty] qjackctl has no buttons in its window or close button in title bar
https://bugs.launchpad.net/bugs/335212
You received this bug notification because you are a member of Ubuntu
Bugs,
*** This bug is a duplicate of bug 331324 ***
https://bugs.launchpad.net/bugs/331324
confirmed here, too. Christian's workaround above works on i386.
--
[Jaunty] gdmgreeter crashed with SIGSEGV in __libc_start_main()
https://bugs.launchpad.net/bugs/331439
You received this bug notification
Hi Daniel
Yes, I have - with identical results...
--
fw-host0: Iso Xmit 0 Context died
https://bugs.launchpad.net/bugs/232490
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
Hi Stefan
I'm not sure it would be applicable - I'm using the realtime kernel
which has PREEMPT...
In any case, is it fixable? I'd really like to use my Saffire!
--
fw-host0: Iso Xmit 0 Context died
https://bugs.launchpad.net/bugs/232490
You received this bug notification because you are a
*** This bug is a duplicate of bug 232490 ***
https://bugs.launchpad.net/bugs/232490
** This bug has been marked a duplicate of bug 232490
fw-host0: Iso Xmit 0 Context died
--
jackd crashes using freebob and firewire devices
https://bugs.launchpad.net/bugs/231085
You received this bug
*** This bug is a duplicate of bug 232490 ***
https://bugs.launchpad.net/bugs/232490
** This bug is no longer a duplicate of bug 231085
jackd crashes using freebob and firewire devices
** This bug has been marked a duplicate of bug 232490
fw-host0: Iso Xmit 0 Context died
--
jackd
confirmed on i386.
This bug renders Ardour unusable.
** Attachment added: Screenshot.png
http://launchpadlibrarian.net/18756478/Screenshot.png
--
Ardour import file dialog broken
https://bugs.launchpad.net/bugs/279723
You received this bug notification because you are a member of Ubuntu
Tested using local directory - still crashes.
** Visibility changed to: Public
--
sbackupd.py crashed with NotPermittedError in delete()
https://bugs.launchpad.net/bugs/283257
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Sorry! This screenshot should be better!
as you can (now) see, there's several events missing from the Evolution
view - the 1:30-2:30 and 2:00-4:00 events (this is a conference
schedule)
To reproduce this, used New Calendar, created a Google calendar
instance (using a private calendar).
Public bug reported:
Binary package hint: evolution
Description:Ubuntu intrepid (development branch)
Release:8.10
evolution:
Installed: 2.23.91-0ubuntu1
Candidate: 2.23.91-0ubuntu1
Version table:
*** 2.23.91-0ubuntu1 0
500 http://au.archive.ubuntu.com intrepid/main
** Attachment added: Evolution Screenshot
http://launchpadlibrarian.net/17671482/evo-screenshot.png
--
[intrepid] Google Calendar sync to Evolution does not sync all events
https://bugs.launchpad.net/bugs/271177
You received this bug notification because you are a member of Ubuntu
Bugs,
** Attachment added: Google Calendar Screenshot - same calendar, same day
http://launchpadlibrarian.net/17671487/gcalscreenshot.png
--
[intrepid] Google Calendar sync to Evolution does not sync all events
https://bugs.launchpad.net/bugs/271177
You received this bug notification because you
From experimentaion with 64Studio, I can add that the jackd process is
zombifiying,
Is there anyone who can help me triage this problem?
** Changed in: libfreebob (Ubuntu)
Status: New = Confirmed
** Changed in: jack-audio-connection-kit (Ubuntu)
Status: New = Confirmed
--
jackd,
Please delete this bug. Ricoh chipset is known not to work with audio on
all platforms.
I'm still having issues with the Saffire LE, not that anyone has ever
paid attention to this bug. Cheers, guys.
--
jackd crashes using freebob and Focusrite Saffire LE
https://bugs.launchpad.net/bugs/231085
Public bug reported:
The saga continues.
Having purchased an Expresscard/34 with Texas Instruments ieee1394a
(Firewire 400) chipset, as recommended here:
http://www.ffado.org/?q=node/251 for my Focusrite Saffire LE, which has
been reported by many users as working perfectly with Ubuntu - and
Also, note that this is NOT a duplicate of Bug #231085, which refers to
the inbuilt RICOH chipset in my Dell XPS M1210 laptop and the same card.
Which never garnered a damn reply, so I don't even know why I mention
it.
--
jackd, freebob, Focusrite Saffire LE, TI ieee1394 chipset FAIL
@Pierre-Antoine: I haven't been through my logs for the error - mainly
because a reboot or two is a workaround, but the symptoms you describe
are almost exactly similar. By all means, report the bug (as you have
more technical info than I do) and I'll confirm.
--
[hardy] Black X screen and
@Lorenzo: I have the same problem - one reboot in five, or thereabouts,
compiz chokes and hits 100%+ of cpu - but I had it with the Beta driver
as well, so I suspect it may actually be compiz that has the issue.
Unfortunately, it locks up the system enough to make it very difficult
to isolate the
I've got $600 worth of kit sitting idle and it doesn't rate a mention?
--
fw-host0: Iso Xmit 0 Context died
https://bugs.launchpad.net/bugs/232490
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
The 173-series drivers are now available from Nvidia at
http://www.nvidia.com/object/linux_display_ia32_173.14.05.html
This driver works with the -rt kernel (as reported earlier, while the
driver was in beta) They should be packaged for 8.04 TO RESOLVE THIS
BUG!
That's if Ubuntu is serious about
Public bug reported:
Binary package hint: linux-image
Description:Ubuntu 8.04
Release:8.04
2.6.24-16-rt #1 SMP PREEMPT RT Thu Apr 10 15:15:40 UTC 2008 i686
GNU/Linux
Using a Firewire sound card (Focusrite Saffire LE, supported by FreeBoB)
with the following Ricoh iee1394 interface
Public bug reported:
Description:Ubuntu 8.04
Release:8.04
uname: 2.6.24-16-rt #1 SMP PREEMPT RT Thu Apr 10 15:15:40 UTC 2008 i686
GNU/Linux
I have recently purchased a Focusrite Saffire LE firewire audio
interface, which is supposedly supported by both freeBoB and FFADO,
however I
Public bug reported:
Description:Ubuntu 8.04
Release:8.04
uname: 2.6.24-16-rt #1 SMP PREEMPT RT Thu Apr 10 15:15:40 UTC 2008 i686
GNU/Linux
I have recently purchased a Focusrite Saffire LE firewire audio
interface, which is supposedly supported by both freeBoB and FFADO,
however I
Double-submitted. Sorry. Bug #231085 is a duplicate of this bug.
--
jackd crashes using freebob and Focusrite Saffire LE
https://bugs.launchpad.net/bugs/231085
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
*** This bug is a duplicate of bug 231085 ***
https://bugs.launchpad.net/bugs/231085
** This bug has been marked a duplicate of bug 231085
jackd crashes using freebob and Focusrite Saffire LE
--
jackd crashes using freebob and Focusrite Saffire LE
https://bugs.launchpad.net/bugs/231083
Public bug reported:
Description:Ubuntu 8.04
Release:8.04
uname: 2.6.24-16-rt #1 SMP PREEMPT RT Thu Apr 10 15:15:40 UTC 2008 i686
GNU/Linux
Package versions:
jackd:
Installed: 0.109.2-1ubuntu1
Candidate: 0.109.2-1ubuntu1
Version table:
*** 0.109.2-1ubuntu1 0
500
Tried removing the complete -rt package, rebooting and reinstalling,
then rebooting again and enabling the nvidia driver. Still no go.
--
[hardy] Black X screen and system halt after installing linux-rt
https://bugs.launchpad.net/bugs/197130
You received this bug notification because you are a
some users in the forum are reporting that manually installing the nvidia
driver from nvidia.com resolves this issue
http://ubuntuforums.org/showthread.php?t=736984
However, note that the user reporting that fix has an SLI system, and
reports that the -12 revision of the -rt kernel worked for
Has anyone made any progress with this? Does anyone know what the heck
is going on here? I mean, a bug caused by and XFiles fansite, Bug
#212648, is listed at Medium priority whereas this bug, which knocks out
a whole class of users, is undecided. I'm doing my best to diagnose the
cause but I
Public bug reported:
Binary package hint: conduit
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=8.04
DISTRIB_CODENAME=hardy
DISTRIB_DESCRIPTION=Ubuntu 8.04
Conduit crashes while synchronising folder-to-usb-disk
ProblemType: Crash
Architecture: i386
Date: Mon Apr 21 20:50:32 2008
DistroRelease: Ubuntu 8.04
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/13595280/Dependencies.txt
** Attachment added: ProcMaps.txt
http://launchpadlibrarian.net/13595281/ProcMaps.txt
** Attachment added: ProcStatus.txt
http://launchpadlibrarian.net/13595282/ProcStatus.txt
** Attachment
Can you attach your xorg.conf, please, mimp? I want to check
something...
Not that I can fix the bug or anything...
--
[hardy] Black X screen and system halt after installing linux-rt
https://bugs.launchpad.net/bugs/197130
You received this bug notification because you are a member of Ubuntu
Well, I think I've fairly comprehensively proved that it's an actual
bug, given that the symptoms seem reproducible on several systems. It's
also been present (for me) in every revision of the -rt kernel from -12.
I have tried the EnvyNG installer (with the -12 and -14 revisions) which
also
Yes, I've reinstalled. Same error.
There's been an nvidia-glx-new update in the last couple of days, i
think? Because the behaviour's changed in -15. The laptop no longer
hard-locks, but X crashes - log attached.
Note:
(**) NVIDIA(0): Use of NVIDIA internal AGP requested
(II) NVIDIA(0): Support
** Attachment added: xorg.conf
http://launchpadlibrarian.net/13351818/xorg.conf
--
[hardy] Black X screen and system halt after installing linux-rt
https://bugs.launchpad.net/bugs/197130
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Actually, there's another nvidia-glx-new update in my update-manager
(although I'm being warned of a partial upgrade right now so I'll leave
it...)
--
[hardy] Black X screen and system halt after installing linux-rt
https://bugs.launchpad.net/bugs/197130
You received this bug notification
@Alessio
dpkg -l | grep \-rt
ii linux-image-2.6.24-12-rt 2.6.24-12.22
Linux kernel image for version 2.6.24 on Ing
ii linux-image-2.6.24-14-rt 2.6.24-14.25
Linux kernel image for version 2.6.24
@Alessio
Done. Fresh install, then update, then install linux-rt results in a
return to the previous hard-lock behaviour. I have to force the laptop
to power down by holding the power button.
** Attachment added: Xorg.0.log
http://launchpadlibrarian.net/13373175/Xorg.0.log
--
[hardy] Black
Default xorg.conf from the new installation
** Attachment added: xorg.conf
http://launchpadlibrarian.net/13373198/xorg.conf
--
[hardy] Black X screen and system halt after installing linux-rt
https://bugs.launchpad.net/bugs/197130
You received this bug notification because you are a member
*** This bug is a duplicate of bug 197130 ***
https://bugs.launchpad.net/bugs/197130
Marked as a duplicate of Bug #197130
** This bug has been marked a duplicate of bug 197130
[hardy] Black X screen and system halt after installing linux-rt
--
nvidia-glx-new crashes when using rt kernel
Bug #208247 is a duplicate of this bug. Can someone please set this to a
higher priority? Clearly it is not possible to use UbuntuStudio with an
nvidia card, which is a blocker for anyone with that configuration...
--
[hardy] Black X screen and system halt after installing linux-rt
OK. I'm really not convinced that this is a linux-restricted-modules
bug, as the update to the -15 kernel produces the same error. Now what?
--
[hardy] Black X screen and system halt after installing linux-rt
https://bugs.launchpad.net/bugs/197130
You received this bug notification because you
OK. I've added this to xorg-xserver, because I think that's the actual
location of the bug.
** Changed in: xorg-server (Ubuntu)
Sourcepackagename: None = xorg-server
Status: Invalid = New
** Changed in: xorg-server (Ubuntu)
Status: New = Confirmed
--
[hardy] Black X screen and
I'm experiencing the same problem. I don't even have Tomboy installed -
why am I subscribed to this bug?
--
Tomboy.exe crashed with SIGSEGV in exit()
https://bugs.launchpad.net/bugs/199496
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm listed as subscibed through a duplicate - I'm not subscribed to any
duplicates of this bug. I'm getting notices from every damn duplicate,
and every time a duplicate of this bug is entered I start getting
messages from that, too. The unsubscribe option doesn't work, and
whether I have Tomboy
*** This bug is a duplicate of bug 197130 ***
https://bugs.launchpad.net/bugs/197130
Marking as a duplicate of https://bugs.launchpad.net/ubuntu/+source
/linux-restricted-modules-2.6.24/+bug/197130
** This bug has been marked a duplicate of bug 197130
[hardy] Black X screen and system
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-
modules-2.6.24/+bug/205927 is a duplicate of this bug
--
[hardy] Black X screen and system halt after installing linux-rt
https://bugs.launchpad.net/bugs/197130
You received this bug notification because you are a member of Ubuntu
Bugs,
*** This bug is a duplicate of bug 197130 ***
https://bugs.launchpad.net/bugs/197130
This bug is a duplicate of https://bugs.launchpad.net/ubuntu/+source
/linux-restricted-modules-2.6.24/+bug/197130
** This bug has been marked a duplicate of bug 197130
[hardy] Black X screen and system
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-
modules-2.6.24/+bug/206207 is a duplicate of this bug
** Changed in: linux-restricted-modules-2.6.24 (Ubuntu)
Status: New = Confirmed
--
[hardy] Black X screen and system halt after installing linux-rt
On second viewing, this is not a duplicate, as the user can use
keystrokes to restart. This is not the case in Bug #197130
** This bug is no longer a duplicate of bug 197130
[hardy] Black X screen and system halt after installing linux-rt
--
Black screen on UbuntuStudio (2.6.24-12-rt) when
Well, to be honest the submitter of Bug #205927 hasn't provided X.org
logs for verification, so I'm probably a bit pre-emptive in marking it
anything other than incomplete... The description is eerily similar, so
I'll leave it duped until proven otherwise...
You're right though - Bug #206207
The NvAGP option sets whether or not the xserver will use the NVIDIA AGP
module instead of the kernel agpgart module - see
ftp://download.nvidia.com/solaris/1.0-8178/README/appendix-f.html
Since commenting here, though, I've discovered that my problem seems to be in
the NV-GLX extension for
Xorg.log from booting with the -generic kernel
** Attachment added: Xorg.0.log.old
http://launchpadlibrarian.net/12737596/Xorg.0.log.old
--
[hardy] Black X screen and system halt after installing linux-rt
https://bugs.launchpad.net/bugs/197130
You received this bug notification because you
Xorg.log from booting with the -rt kernel
** Attachment added: Xorg.0.log
http://launchpadlibrarian.net/12737599/Xorg.0.log
--
[hardy] Black X screen and system halt after installing linux-rt
https://bugs.launchpad.net/bugs/197130
You received this bug notification because you are a member
I've located the problem - note the following:
From the Xorg.log when booting the -rt kernel, the last few lines read
(II) NVIDIA(0): Initialized GPU GART.
(II) NVIDIA(0): ACPI display change hotkey events enabled: the X server is new
(II) NVIDIA(0): enough to receive ACPI display change
This looks a lot like my bug - a
href=https://bugs.launchpad.net/ubuntu/+source/linux-restricted-
modules-2.6.24/+bug/197130?https://bugs.launchpad.net/ubuntu/+source
/linux-restricted-modules-2.6.24/+bug/197130/a?
--
[nvidia-glx-new] Nvidia restricted driver locks system with xserver launch
Reinstalled, using the Alpha 6 LiveCD for i386, and the same problem
occurs.
--
[hardy] Black X screen and system halt after installing linux-rt
https://bugs.launchpad.net/bugs/197130
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Applies to 2.6.24-10-rt, 2.6.24-11-rt and now 2.6.24.12-rt
Seriously, guys, how can I help you out here? I'm going crazy!
--
[hardy] Black X screen and system halt after installing linux-rt
https://bugs.launchpad.net/bugs/197130
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 199083 ***
https://bugs.launchpad.net/bugs/199083
Public bug reported:
Binary package hint: totem
Not sure what caused this error - I wasn't running totem at the time!
ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Sun Mar 9 12:23:56 2008
*** This bug is a duplicate of bug 199083 ***
https://bugs.launchpad.net/bugs/199083
** Attachment added: CoreDump.gz
http://launchpadlibrarian.net/12524569/CoreDump.gz
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/12524570/Dependencies.txt
** Attachment added:
** Changed in: xorg (Ubuntu)
Sourcepackagename: linux-meta = xorg
** Changed in: ubuntu
Sourcepackagename: gdm = None
--
[hardy] Black X screen and system halt after installing linux-rt
https://bugs.launchpad.net/bugs/197130
You received this bug notification because you are a member of Ubuntu
After some fiddling and tweaking, this seems to be an xserver-xorg
problem. To reiterate:
Booting from the -10 AND -11 realtime kernels, and attempting to use the
non-free nvidia driver results in a total lockup of the PC. IT is a Dell
XPS m1210 with an Nvidia GeForce Go 7400 card and I'm running
OK. Marked incomplete. Cool - what do I need to add?
--
[hardy] Black X screen and system halt after installing linux-rt
https://bugs.launchpad.net/bugs/197130
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Also affects: gdm (Ubuntu)
Importance: Undecided
Status: New
--
[hardy] Black X screen and system halt after installing linux-rt
https://bugs.launchpad.net/bugs/197130
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
This bug is present on a fresh install of hardy, without any prior
installation of Tab Mix, etc. (Alpha 5 X86_64)
The Firefox error console reports:
SessionStore: The session file is invalid: TypeError:
this._initialState.windows[0] is undefined
In about:config
This xserver log (from booting with the -rt kernel) shows that the
nvidia driver is not loaded
** Attachment added: Xorg.0.log.old
http://launchpadlibrarian.net/12344537/Xorg.0.log.old
--
[hardy] Black X screen and system halt after installing linux-rt
https://bugs.launchpad.net/bugs/197130
This is from booting with the -generic kernel
** Attachment added: Xorg.0.log
http://launchpadlibrarian.net/12344542/Xorg.0.log
--
[hardy] Black X screen and system halt after installing linux-rt
https://bugs.launchpad.net/bugs/197130
You received this bug notification because you are a
Public bug reported:
Binary package hint: linux-rt
System: Dell XPS M1210, Nvidia GeForce Go 7400
OS: Ubuntu 8.04 Hardy Heron Alpha 5 x86_64
Kernel: Tested with linux-image-2.6.24-8-rt and linux-image-2.6.24-10-rt
After installing a realtime kernel using the linux-rt metapackage,
rebooting the
** Attachment added: syslog
http://launchpadlibrarian.net/12335514/syslog
--
[hardy] Black X screen and system halt after installing linux-rt
https://bugs.launchpad.net/bugs/197130
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Confirmed in Tribe 5, upgraded from Feisty. This is on a Dell XPS M1210
I get no sound from hda-intel, and no sound from external USB device
(Behringer U-Control UCA202)
Both worked perfectly in Feisty.
The error given when testing in Sound Preferences is
audiotestsrc wave=sine freq=512 !
*** This bug is a duplicate of bug 69334 ***
https://bugs.launchpad.net/bugs/69334
at least partially confirmed on a new install of edgy:
My notes are as follows:
libnss-ldap does not appear to work correctly with
debconf: the line
base dc=your,dc=base,dc=name
is set to dc=padl,dc=com
Public bug reported:
Binary package hint: rtfm
This package is a component module of request-tracker3.4 and therefore
should install its html files to the same location as that package,
/usr/share/request-tracker3.4
Instead, the html files are installed to /usr/share/request-tracker3,
which
"006792";
google_color_url = "006792";
google_color_text = "00";
//-->
[Bug 246894] Re: [needs packaging] FFADO FreeBob - Firewire Mixer Audio Drivers
prismatic7
[Bug 246894] Re: [needs packaging] FFADO FreeBob - Firewire Mixer Audio Drivers
Tree MendUs
86 matches
Mail list logo
