There's something deeply wrong with the way Ubuntu packages Node.
Here's the NodeJS project's release timeline:
https://nodejs.org/en/about/releases/
Node LTS releases are even-numbered and supported for 30 months.
Node 10 isn't even on there anymore. Node 12 is the oldest currently available,
This is an interaction between a symlink that systemd ships (as
mentioned in https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=627949#10) and the kmod package (which ships the
now-inaccurate /usr/share/man/man5/modules.5.gz).
** Also affects: kmod (Ubuntu)
Importance: Undecided
Status:
Public bug reported:
My systemd-modules-load.service fails to start like this:
● systemd-modules-load.service - Load Kernel Modules
Loaded: loaded (/lib/systemd/system/systemd-modules-load.service; static;
vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2020-10-27
I haven't upgraded to Focal yet, but it's still an open issue upstream:
https://github.com/vim/vim/issues/5237
May 20, 2020 5:49 AM, "Sebastien Bacher" wrote:
> Is that still an issue in focal?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
>
I'm not quite sure how to mark this on Launchpad as a general 20.04
system integration problem, rather than really quite being snap-store's
fault/responsibility.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
When I set my home directory to e.g. /alt/home/$USER, I cannot open
`snap-store`, the new default package manager for 20.04. When starting
it from Gnome, I just get nothing. When starting it from the command
line, I get:
$ snap-store
Sorry, home directories outside of /home
I encountered this when trying to report a bug in the snap-store, which
as far as I can tell is the new default package manager. It looks pretty
silly to see Apport disclaiming responsibility for the package manager.
It knows the snap is published by "canonical". Maybe everything
published by
*** This bug is a duplicate of bug 1861082 ***
https://bugs.launchpad.net/bugs/1861082
Public bug reported:
With the move to package the software center as a Snap in 20.04, I
decided to go fishing for bugs that might manifest on my 18.04 machine
(with a home directory outside of /home),
I did a bisect as asked in the upstream issue I reported at
https://github.com/vim/vim/issues/5237 and I think that
https://github.com/vim/vim/commit/cd142e3369db163a511dbe9907bcd138829c
is the offending commit.
** Summary changed:
- vim-gtk can no longer save to GVFS SFTP mounts in 18.04
+
Sorry, I misremembered my results from yesterday. I just checked again.
The permissions are in fact different: the Nautilus-created files are
644 (because my "New Text Document.txt" template in ~/Templates is 644),
while files created with e.g. touch are 664.
Since both allow me, the owning user,
The permissions and ownership are the same. It seems to persist across
ejecting and remounting the SSH mount. I can see if it persists across a
reboot or magically spreads from one SSH mount to a different mount (via
a different hostname/ip for the same machine), but I suspect it won't.
November
I can actually only get this to manifest *for files created by
Nautilus*. Files that are created from an ssh session or by cd-ing into
the /run/user/1000/... directory are unaffected. So I guess this also
affects Nautilus?
** Also affects: nautilus (Ubuntu)
Importance: Undecided
Status:
*** This bug is a duplicate of bug 1813679 ***
https://bugs.launchpad.net/bugs/1813679
** Description changed:
To reproduce:
1. Have an SSH server you have access to. It could even be localhost.
2. Open "Files" (Nautilus), hit Ctrl+L to get the URL bar, and type in
This is an interaction between vim and GVFS, so I've added GVFS as
affected.
** Also affects: gvfs (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- vim-gtk can no longer save to GVFS STFP mounts in 18.04
+ vim-gtk can no longer save to GVFS SFTP mounts in 18.04
--
*** This bug is a duplicate of bug 1813679 ***
https://bugs.launchpad.net/bugs/1813679
Public bug reported:
To reproduce:
1. Have an SSH server you have access to. It could even be localhost.
2. Open "Files" (Nautilus), hit Ctrl+L to get the URL bar, and type in
"ssh://your.server", and
*** This bug is a duplicate of bug 1813679 ***
https://bugs.launchpad.net/bugs/1813679
Looks like I reported this already ages ago, but as far as I can tell
nobody noticed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
There's not really an applicable Ubuntu kernel to collect logs for; the
problem is only apparent in a container on top of a host that doesn't
run a recognized kernel.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a
I reported this bug from this container running on an Ubuntu-based host
where I built it. When I tried to run ubuntu-bug in the container on the
host where I actually encountered the problem, it refused to report the
bug due to... a non-Ubuntu kernel!
--
You received this bug notification
Public bug reported:
The `perf` profiling tool, and a few other tools, are part of the Linux
project. Ubuntu gets them from a package specific to the running kernel
version, and uses wrapper scripts installed as e.g. /usr/bin/perf to
dispatch to the appropriate version for the running kernel.
Do I have to downgrade my system from Dingo to Cosmic in order to test
this in Cosmic, to keep my bug from being closed?
May 20, 2019 7:02 AM, "Ubuntu Kernel Bot" wrote:
> This bug is awaiting verification that the kernel in -proposed solves
> the problem. Please test the kernel and update this
OK, this second deb seems to solve my problem! The headphone jack state
is detected correctly without the quirk! Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824259
Title:
Headphone jack
Here's the whole `sudo dmidecode` output (attached).
** Attachment added: "Output of sudo dmidecode for the LattePanda"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824259/+attachment/5258402/+files/dmidecode.txt
--
You received this bug notification because you are a member of
Hello,
Thank you for looking into this.
I installed the DKMS module deb (which built itself against kernel
5.0.0-13, which is what the system is now updated to), commented out the
quirk-setting line in my module config file, and rebooted.
I now have no sound; list-cards in pacmd shows me that
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1824259/+attachment/5255466/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824259
Title:
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1824259/+attachment/5255460/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824259
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1824259/+attachment/5255458/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824259
Title:
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1824259/+attachment/5255463/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1824259/+attachment/5255467/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs,
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1824259/+attachment/5255461/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824259
Title:
I set the bug to Confirmed, despite being the original reporter, because
the bot told me to.
The Apport logs I posted are form the system with my workaround enabled.
I also blacklisted the HDMI audio module, since I don't use HDMI audio,
and I thought it might help. It didn't seem to, but I never
apport information
** Tags added: apport-collected
** Description changed:
My machine is a LattePanda board, which uses a "chtrt5645" device as a
sound card. It has a single headphone output jack, which I think is a
TRRS jack, with a mic input, such as is normally used on phones.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1824259/+attachment/5255459/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1824259/+attachment/5255464/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824259
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1824259/+attachment/5255465/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824259
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1824259/+attachment/5255462/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This is actually a kernel bug, in Linux. The issue is the absence of
platform data for this particular board in the snd_soc_rt5645 module.
The issue can be worked around by creating
/etc/modprobe.d/hacksound.conf with the following contents:
# Invert jack detection (1) and use detection mode 2
This may be a kernel driver bug, and a regression from 4.12. See
http://www.lattepanda.com/topic-p24689.html?sid=1fa88916eb19dd9d65e0abd3ecbf6210#p24689
This may be a missing piece of platform data in the kernel that would
tell it to invert jack detection on this particular board. I will try
If I save the ALSA state with the headphones unplugged to a file:
sudo alsactl --file=settings-out.txt store
And then plug in the headphones and restore it:
sudo alsactl --file=settings-out.txt restore
I still get no sound. But then diffing the final state against the
unplugged state did find
Public bug reported:
My machine is a LattePanda board, which uses a "chtrt5645" device as a
sound card. It has a single headphone output jack, which I think is a
TRRS jack, with a mic input, such as is normally used on phones.
When I don't have headphones plugged in, the system thinks headphones
Public bug reported:
In Ubuntu 16.04, with gvim 7.4.1689, I can open files over GVFS SSH
mounts (by going to `ssh://wherever` in the address bar in the file
browser and double-clicking on the file), edit them, and save them.
In Ubuntu 18.04, when I install `vim-gtk` and try to do the same thing,
Public bug reported:
The r8152 Ethernet device in my Lattepanda board just disconnected from
my network while I was uploading some files over the LAN.
dmesg reported this:
[1036155.155084] [ cut here ]
[1036155.155099] NETDEV WATCHDOG: enx00e04c368b17 (r8152): transmit
Public bug reported:
nVidia's proprietary drivers don't work when the kernel is running under
the Xen hypervisor; nVidia knows this and has chosen not to implement
Xen support. However, I did not know this.
On my Ubuntu Xen dom0 system, I went into Ubuntu's "Software & Updates",
on the
I don't seem to have access to change the tag, but I can confirm that
4.15.0-34-generic from -proposed solves the problem. So the tag should
be verification-done-bionic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
OK, I have tested the provided kernel and it works for me under Xen.
Thank you for fixing the bug! I look forward to seeing this in the
real releases.
[anovak@octagon ~]$ uname -a
Linux octagon 4.15.0-31-generic #34~lp1777338 SMP Tue Aug 7 14:57:12
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
On Mon,
Thanks for preparing this kernel; I am downloading it now. What are
the expected hashes of the files, so that I can verify the insecure
downloads?
On Tue, Aug 7, 2018 at 8:49 AM, Joseph Salisbury
wrote:
> I built a test kernel with commit 74899d92e3dc7671a8017b3146dcd4735f3b.
> The test
OK, I grabbed commit 74899d92e3dc7671a8017b3146dcd4735f3b "x86/xen:
Add call of speculative_store_bypass_ht_init() to PV paths" from
g...@github.com:torvalds/linux.git and cherry-picked it on top of the tag
Ubuntu-4.15.0-29.31, and built the kernel, and now it boots fine as
dom0! I think that
I've been advised by Juergen Gross that not having "x86/xen: Add call of
speculative_store_bypass_ht_init() to PV paths" from the mainline kernel
might contribute to this problem. I am trying to pull that in now.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I'm not finding any kernel packages in bionic-proposed; maybe they were
released already?
I've installed and tested 4.15.0-29 from the normal repos; it has the same
null pointer dereference at address 8 issue.
On Tue, Jul 24, 2018, 09:17 Joseph Salisbury
wrote:
> Thanks for finishing up the
OK, I have finished the bisect.
3f6a3b035f91a22c0d3bd27630bf61eac9c8cf6c is the first bad commit. I
tested it and it displays the problem, and I tested
abd39ac1da07b433fc570332ee9ad938b5071760 right before it and that one
boots fine.
On Sat, Jul 21, 2018 at 9:42 AM, Adam Novak wrote:
> That
That one works. On to 5856293c78e552c012835e667d66775bba20b4f7.
I suspect 3f6a3b035f91 and abd39ac1da07 may be the real problem, since
the CPU I am using is an AMD Ryzen chip, and those are tinkering
specifically with how the kernel handles those.
On Fri, Jul 20, 2018 at 10:23 PM, Adam Novak
OK, I tried that one and it still exhibited the issue. I'm going to
try 91762b4035d9da8c266e2cb3dbc552052434bbf0 next.
On Fri, Jul 20, 2018 at 9:08 PM, Adam Novak wrote:
> Thanks!
>
> I have tested this kernel; it doesn't work, so the problem is between
> fc8704280f2ada9f61f08a2d5adc
Thanks!
I have tested this kernel; it doesn't work, so the problem is between
fc8704280f2ada9f61f08a2d5adc0dab169cc207 and
8eca6add0defde203282476d7969a7c13bbd7d91.
I've gotten set up with a kernel build environment; I think I can
finish the git bisect myself, but looking at the commits in that
OK, I've tested this kernel, and it works just fine under Xen, from
what I can tell. The system comes up just fine:
Linux octagon 4.15.0-23-generic #26~lp1777338Commit8eca6add0 SMP Wed
Jun 27 15:50:08 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
The offending commit must be later.
On Thu, Jul 5,
Hello,
Thanks for putting this together. I tried to get the kernels you
built, but I'm having trouble establishing a secure (https) connection
to kernel.ubuntu.com. It looks like the server might not offer https.
Can you give me the expected hashes of the files so I can verify the
downloads?
I updated my BIOS and tested the -24 kernel, as was recommended. It
definitely doesn't work any better. It still has the null dereference
problem, and then it prints a bunch of smp_call_function_too_many errors,
apparently forever.
On Tue, Jun 19, 2018, 08:11 Joseph Salisbury
wrote:
> Can you
This also affects the mainline kernel build 4.17.0-041700.201806041953
that I was testing for another bug.
I've attached a photo of the screen with the issue occurring, in that
version.
Booting not under Xen seems to work around the issue, and the system
comes up, but that's not useful for me
With the demise of Grooveshark, this bug is no longer relevant and
should be closed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1069780
Title:
[needs-packaging] Doesn't work under 12.10
To
The drive that was giving me this problem failed. I got a replacement
(which is notionally the same model, with the same USB ID 0781:5581),
and, on kernel 4.15-22, under Xen, the new drive seems to work fine in
USB 3 ports.
However, I also tested with the latest v4.17 kernel from the given link
Public bug reported:
I went to boot my computer today and it wouldn't boot.
I get an "Unable to handle kernel NULL pointer dereference" message
during the boot process, and, a bit after that, a message from the
kernel watchdog about CPU #0 being stuck. Then the boot process stops
completely.
I
Public bug reported:
I have a 128 GB Sandisk Ultra USB Flash Drive. It works when I plug it
into a USB 2.0 port, or if I partially insert it into a USB 3.0 port (so
the USB 3 pins don't make contact).
Here's what lsusb says about it:
Bus 001 Device 005: ID 0781:5581 SanDisk Corp. Ultra
And
It looks like the drive is replying with an ILLEGAL REQUEST/INVALID
FIELD IN CDB error to all the interesting SCSI commands, and to pretty
much anything hdparm sends it.
I've also tried throwing sdparm at it. The only page sdparm can get out
of it is the basic identification page:
I pulled the hdparm binary from Artful, and it can't spin down the drive
with -y either.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774569
Title:
gsmartcontrol, hdparm, and ZFS all refuse to
Even after rebooting with the drive for the zpool physically removed
from the system, I still had a zpool I couldn't destroy, export, or
otherwise remove from the listing.
Using "sudo zpool status -Pv" I worked out that my ZFS was actually
expecting to find the data on partition 1 of the drive:
Nope, my speculation is definitely wrong. The disk shows up in lsscsi:
[anovak@octagon ~]$ lsscsi
...
[9:0:0:0]diskSeagate Backup+ Hub BK D781 /dev/sdb
Also, it shows up in lsusb -t with a "uas" driver.
Maybe the problem is the uas driver itself?
Here's the full description of the
Public bug reported:
I recently upgraded from 17.10 to 18.04. After the upgrade, I noticed
that my Seagate Backup+ Hub external drive was displaying a series of
puzzling symptoms:
1. gsmartcontrol can't get SMART data from the drive. I am pretty sure
it used to report SMART data? Here's a log of
Public bug reported:
libcurl4-gnutls-dev provides my /usr/bin/curl-config and the static
library (symlink) /usr/lib/x86_64-linux-gnu/libcurl.a -> libcurl-
gnutls.a. I am trying to link statically against that static library.
The right way to do this seems to be to run "curl-config --static-libs"
Public bug reported:
The pkg-config file at /usr/lib/x86_64-linux-
gnu/pkgconfig/gobject-2.0.pc has "-lffi" in its "Libs.private". This
means that when you ask pkg-config how to link statically against
gobject-2.0, with "pkg-config --libs --static gobject-2.0", you get a
series of linker flags
Public bug reported:
The static library for libyajl-dev is installed as /usr/lib/x86_64
-linux-gnu/libyajl_s.a and not /usr/lib/x86_64-linux-gnu/libyajl.a. This
means that static linking with "-lyajl" will not find it; you need to
use "-lyajl_s".
This has not been explained to pkg-config (and I
You need gstreamer1.0-plugins-ugly and/or gstreamer1.0-plugins-bad. Not
the 0.10 versions. I installed them both and it started working for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/47
I don't know if this is expected behavior, but it's certainly annoying
behavior. I'm writing an app that depends on libtcodxx.so, which in turn
depends on libtcod.so. I want to ship them both in the lib directory
next to my app. With RUNPATH as "$ORIGIN/lib", it finds the direct
dependency
This also occurs on Ubuntu MATE 15.04 running cryptsetup 1.6.6-5ubuntu2
(versus the ubuntu1 in the original report).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1481536
Title:
"cryptsetup:
I can confirm that the patch to /usr/bin/dia works on 12.04 as well. Can
we get the maintainer to update the package to include the patch?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1011446
Title:
Public bug reported:
A fully-filled-in IPv6 address is 8 groups of 4 characters each, with 7
colons, for a total of 39 characters. This is much longer than the 4 * 4
+ 3 = 19 characters maximum required to represent an IPv4 address, which
is what the output format that ping6 inherits from ping
I can confirm that the workaround works! You can add the environment
variable to the launcher with the alacarte menu editor, if you want a
GUI for it.
I can now read my gedit again. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Now how do we get this from an attachment back into the official
repositories?
On Feb 11, 2013 2:48 PM, Marcin Jakubowski 1069...@bugs.launchpad.net
wrote:
I have the Untitled icon as well but only when launching the webapp
through its own launcher icon. But the webapp will also come up if it
Public bug reported:
I can run blastn with the option -evalue +inf and, with the default
output format, the program runs fine and prints out everything it finds
with e-values infinity. However, with XML output (-outfmt 5), it
crashes because it refuses to represent an infinite double in its XML
GMail is working for me (it wasn't initially, but after a few minutes I
got prompted to install it), but Grooveshark isn't. No prompt from the
site, no icon or search results from the installed application.
Could it be related to Grooveshark's new UI?
--
You received this bug notification
Public bug reported:
For some Qt apps from PPAs (I have noticed this with Retroshare
0.5.3.5503 from ppa:csoler-users/retroshare-snapshots and Bitcoin
v0.6.3.0-g6e0c5e3-beta from ppa:bitcoin/bitcoin), no menus appear in the
global menu bar (just the application's title). However, the application
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1045640
Title:
Menu not showing up for some Qt apps
To manage notifications about this bug go to:
** Attachment added: The file causing the segfault
https://bugs.launchpad.net/bugs/957668/+attachment/2884434/+files/gedit-segfault.dat
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/957668
Title:
Public bug reported:
I found this (binary) file inside of an app called RetroShare. I tried
to open it in my running gedit window by drag-and-drop, and my gedit
disappeared. I then tried to gedit filename from the command line.
The gedit window opened, was blank for a little bit, and then
Yes, it's my opinion that this is a failure of UI design, and that's a
bug. Has anybody responsible for the package had a look at this?
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to qtcreator in Ubuntu.
Public bug reported:
Creating a new project and specifying that it shuld be put under version
control with Mercurial produces very unhelpful error messages unless the
Mercurial binary path and default user name and e-mail are set in the
Mercurial version control settings tab.
The application
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/954577
Title:
Mercurial configuration difficult
To manage notifications about this bug go to:
Yes, works fine in 11.04 with model=auto. Great job, devs.
On Sat, Apr 30, 2011 at 1:03 PM, Jayendra Rakesh
jayendra.rak...@gmail.com wrote:
just for conformation ...
Has this problem been rectified in 11.04 ??
I would like to upgrade from 10.04 sequentially..
--
You received this bug
Yeah, how do we open an upstream bug for this?
On Sat, Dec 18, 2010 at 5:43 PM, Stephanie Duverge sduve...@gmail.com wrote:
No good, will go back to 2.6.33 or 34.
--
You received this bug notification because you are a direct subscriber
of the bug.
https://bugs.launchpad.net/bugs/662009
I have a workaround!
The 2.6.33-02063307-generic kernel from http://kernel.ubuntu.com
/~kernel-ppa/mainline works with the module=lenovo-sky trick. So the
breaking patch is between it and .35.
--
[Lenovo Y530 - Realtek ALC888] Regression from 10.04: No sound with
snd_hda_intel model=lenovo-sky
I also have this problem. Lenovo y530, installed 10.10 today without
checking the known issues, and now I'm stuck with this bug.
Any ideas? Anyone know how to build/install a kernel with the older
ALSA?
--
[Lenovo Y530 - Realtek ALC888] Regression from 10.04: No sound with
snd_hda_intel
Here's my ALSA info:
http://www.alsa-
project.org/db/?f=d5f25b384ea24d6bcf5014d9098a6cb28c828b2a
Would anything else be useful?
--
[Lenovo Y530 - Realtek ALC888] Regression from 10.04: No sound with
snd_hda_intel model=lenovo-sky
https://bugs.launchpad.net/bugs/662009
You received this bug
The .33 kernel seems OK, but I need to build the nVidia beta driver to
run CUDA applications, and those kernels were built with GCC 4.2.
Maverick has GCC 4.4, and 4.2 doesn't seem to be available anywhere, so
I can't build the nVidia module, so I can't run X. I'll try making some
test sounds with
90 matches
Mail list logo
