The problem is discussed in
https://github.com/netblue30/firejail/issues/4698 which in turn is
marked as a duplicate of
https://github.com/netblue30/firejail/issues/3219
The patch mentioned there solves the problem:
$ diff /etc/firejail/firefox-common.profile.orig
Same problem here with https://maps.google.com. Works in
/usr/bin/firefox but not in firejail /usr/bin/firefox.
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 20.04.3 LTS
Release:20.04
Codename: focal
$ apt-cache policy firejail
> Then, either do this at the end after the installer has run, or boot
into a live CD environment (e.g. Kubuntu) and do:
The many steps given there are not really necessary. If you installed
without downloading updates the following steps should be easier:
1. The first boot after the
I have used the "cryptsetup luksOpen` work-around successfully already
years ago.
However, when installing 20.04 with the server installer it does no longer work.
Installation aborts; in the log I found the cause to be
raise ValueError("encryption key or keyfile must be specified")
from
> I tried the xubuntu-20.04.2.0
Sorry, that should have been
xubuntu-20.04.2.0 installer
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904270
Title:
ubiquity does not support existing LUKS
Same problem on 16.04 LTS with HWE kernel.
First error is in statement
+ /sbin/tc filter add dev enp30s0 parent 1:0 protocol ip prio 10 u32 match ip
tos 0x10 0xff flowid 1:10
RTNETLINK answers: Invalid argument
We have an error talking to the kernel
--
You received this bug notification
I wrote:
I can confirm [...] the effectiveness of the work-around
"GTK_THEME=adwaita abiword".
With some more testing I have to qualify that statement a bit: With the
adwaita theme the behaviour is clearly improved compared to the default.
I have not seen text flickering so far. But the cursor
Using Xubuntu 16.04 with all updates here.
I can confirm both the original flickering and the effectiveness of the
work-around "GTK_THEME=adwaita abiword".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have the same crash whenever mbrola is called in Xenial. (I use it via
espeak). Debugging shows that the crash is in an exit handler. In Wily
there was no crash.
I looked at the source package and to my big surprise the program is
delivered as a binary from upstream. (Yes, it is declared a
** Summary changed:
- [wily][regression] completely broken by new kernels
+ [wily][regression] systemtap script compilation broken by new kernels
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1545330
Still the same problem on a fully updated xubuntu wily
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 15.10
Release:15.10
Codename: wily
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Old issue, but my favorite search engine seems to find this report more
easily than this upstreaam report
https://bugzilla.gnome.org/show_bug.cgi?id=726264
** Bug watch added: GNOME Bug Tracker #726264
https://bugzilla.gnome.org/show_bug.cgi?id=726264
--
You received this bug notification
Now I came up with an idea how to investigate whether it is a deadlock
between mkfs and the GUI.
Under /proc/pid/stack one can see the call stack in the kernel space
of the process. So if the mkfs process hung in some do_write call and
the log capturing process in some do_read call that would
I wrote:
Obviously the installer cannot do very much if mkfs.ext4 never
completes.
And I intended to write:
So the bug must be in e2fsprogs (or even in the kernel)
However, thinking one more time I don't think either of those statements is
necessarily true.
The output of mkfs is somehow
I get also bitten by this problem when trying to install ubuntu-15.04
-server-amd64.iso in a virtual machine.
If I select LVM the installation hangs when it tries to format /boot as
ext2
If I select full disk without LVM the installation hangs when it tries
to format / (rootfs) as ext4
I can
I cross-checked that the problem does not occur with ubuntu-14.04
-server-amd64.iso (same VM, excactly same virtual disk)
I also found a work-around:
1. When mkfs hangs open a console on virtual console 2
2. Use ps to see how mkfs was called exactly and what's the pid
3. kill -9 pid
4. call the
Above mentioned patch is not enough. More build errors after this. Looks
like they might have been addressed in http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=717165 but they are based on a newer ltt version.
I will look into when I have time, no promises...
** Bug watch added: Debian Bug
After applying 7 patches I got it built and lttng seems to work at least
for some basic tests. My build area is a complete mess, because of
course the final 7 patches were not the first ones I tried. Hope I will
soon have time to clean it up and post the correct patches here.
--
You received
Hmm, downgraded xfce-power-manager to the previously installed version,
didn't help. Same exercise for gnome-settings-manager (which updated at
the same time), did not help. Well, because downgrading did not help, I
upgraded both of them to the current version again. Result: everything
works fine.
It appears that the problem has already been fixed once in
http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-
saucy.git;a=commit;h=984a2d4fe44738ee6fa69d54d418429b52fea991
But maybe the package lttng-modules-dkms is not build from that source?
--
You received this bug notification because you are a
After installing update xfce4-power-manager (1.2.0-2ubuntu1.1) my screen
brightness control is broken. (Well, I installed several updates, but
this one seems to be the most likely culprit to me). I'll try to
downgrade the package again to verify my suspicion. Right now I'm
running on battery, so I
** Bug watch added: KDE Bug Tracking System #267350
https://bugs.kde.org/show_bug.cgi?id=267350
** Also affects: kdegraphics via
https://bugs.kde.org/show_bug.cgi?id=267350
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of
** Summary changed:
- Bad data handling - Security Hole
+ Okular stores form data in a different directory (possible leak of private
data)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
This happens typically if your package index files are not up to date. I
have the feeling that flashplugin-installer is particular sensitive to
this issue, maybe because the code is dowloaded from a different site or
just because it used to be updated more often than many other packages.
Can you
Hmm, fix commited, but what version?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1020196
Title:
Flash videos in browser play at several times normal speed
To manage notifications about this bug
*** This bug is a duplicate of bug 704667 ***
https://bugs.launchpad.net/bugs/704667
** Visibility changed to: Public
** This bug has been marked a duplicate of bug 704667
Update-manager crashes on fresh natty installs-- NotAuthorizedError:
org.freedesktop.PolicyKit.Error.NotAuthorized:
Public bug reported:
Binary package hint: systemtap
Systemtap module compilation fails with
error: ‘param_ops_int64_t’ undeclared here (not in a function)
This has been reported and also fixed upstream:
http://sourceware.org/bugzilla/show_bug.cgi?id=11940
ProblemType: Bug
DistroRelease:
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/721771
Title:
natty: systemtap incompatible with kernel
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Because systemtap package does not declare the dependecy on the kernel
debug info correctly, obviously apport-bug has not included the relevant
info either. But yes I have correct kernel debug info installed:
ii linux-image-2.6.38-4-generic-dbgsym 2.6.38-4.31
Linux kernel debug image for
Commit 75a48ca3 mentioned in the upstream bug report applies cleanly to
the systemtap source in natty and solves the problem with
error: ‘param_ops_int64_t’ undeclared here (not in a function)
I tried 2 simple system tap scripts: 1 succeeded and 1 failed. The new error is:
error:
The second problem
error: 'CLONE_STOPPED’ undeclared here (not in a function)
is fixed by upstream commit b30b7ed1.
All my tests are successful for the moment (that doesn't tell much, I
have used only very simple scripts)
--
You received this bug notification because you are a member of
Problem still exists even after the KDE upgrade
https://bugs.launchpad.net/bugs/691068
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/594966
Title:
[Kubuntu Lucid] Very noisy playback of AAC streams
Short answer: no experience with Maverick 10.10
(long explanation: I stick to LTS for most work. I do have a 1 Kubuntu
10.10 installation but it is very instable (probably because of some
nouveau display driver issue) so I have not used it very much and not
paid attention to kpackagekit's
Excellent!!! After
git checkout 6936fb
and building and starting applications as in comment #42 the problem is
gone.
Tested with running stellarium and resizing glxgears.
--
[radeon][r200] ../../radeon/radeon_cs_gem.c:181: cs_gem_write_reloc: Assertion
`boi-space_accounted' failed.
To clarify: I have only built and tested r200_dri.so on
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon RV250
[Mobility FireGL 9000] (rev 02)
The comment says that the fix is for r200.
No idea whether it helps also for the different card driver mentioned
in #45
--
Now I've built both radeon_dri.so and r200_dri.so for the benfit of
those who are not so familiar with git and building. (or those who just
want to save the time to do it)
1. Extract the attached file.
tar xf mesafix-6936fb.tbz
2, go to the newly created directory
cd mesafix-6936fb
3. run
The problem also affects this card
ATI Technologies Inc Radeon Mobility M7 LW [Radeon Mobility 7500]
which uses /usr/lib/dri/radeon_dri.so
--
[R200] ../../radeon/radeon_cs_gem.c:181: cs_gem_write_reloc: Assertion
`boi-space_accounted' failed.
https://bugs.launchpad.net/bugs/656100
You
As already mentioned in
https://bugs.freedesktop.org/show_bug.cgi?id=29367#c5 the patch in
https://bugs.freedesktop.org/show_bug.cgi?id=21374#c5 does not apply to
current mesa. I searched a bit in the git history and it applies cleanly
e. g. to commit 57f55a. However, this commit is 150 commits
Before reporting upstream, we probably have to try their newest version. In
order to get at all started with that code I first built
the Ubuntu source.
The Maverick debian package builds mesa obviously in 9 configurations
mesa-7.9~git20100924/build/osmesa32-static/config.status
Oops, my investigations obviously took some time. So I posted #39
without reading #38, which had come in the meantime.
--
[R200] ../../radeon/radeon_cs_gem.c:181: cs_gem_write_reloc: Assertion
`boi-space_accounted' failed.
https://bugs.launchpad.net/bugs/656100
You received this bug
I built the latest libdrm from
git clone git://anongit.freedesktop.org/git/mesa/drm
with these options:
./autogen.sh \
'--build=i686-linux-gnu' \
'--enable-udev' \
'--enable-libkms' \
'--enable-vmwgfx-experimental-api' \
'--enable-nouveau-experimental-api' \
'--enable-radeon' \
oops sorry: I meant it works on my ATI Technologies Inc Radeon RV250
[Mobility FireGL 9000] rev 2, cannot speak for others.
--
[M7 LW] [RV250] resolution incorrectly detected on various radeon cards
https://bugs.launchpad.net/bugs/645377
You received this bug notification because you are a
apport information
** Tags added: apport-collected
** Description changed:
1.) $ lsb_release -rd
Description:Ubuntu lucid (development branch)
Release:10.04
2.) $ apt-cache policy openjdk-6-jre
openjdk-6-jre:
Installed: 6b18-1.8-0ubuntu1
Candidate:
Also Maverick is still affected. (I tried to apport-collect this report
but it fails:
Package openjdk-6 not installed and no hook available, ignoring
--
Lucid openjdk cannot verify applet signature (certificate chain not rebuilt)
https://bugs.launchpad.net/bugs/566317
You received this bug
Yes, it works after applying the latest updates. There was no update to
xorg-xserver-video-ati though, so it must have been a bug somewhere
else. I had too many updates at once, cannot guess which one could have
fixed this issue.
--
[M7 LW] [RV250] resolution incorrectly detected on various
I get the same assertio on i386 with ATI Technologies Inc Radeon RV250
[Mobility FireGL 9000] (rev 02) when trying to start stellar
** Summary changed:
- [R200] ../../radeon/radeon_cs_gem.c:181: cs_gem_write_reloc: Assertion
`boi-space_accounted' failed.
+ [R200] [RV250]
Architecture: i386
DRM.card0.DVI.D.1:
status: disconnected
enabled: disabled
dpms: On
modes:
edid-base64:
DRM.card0.LVDS.1:
status: connected
enabled: enabled
dpms: On
modes: 1400x1050 1280x1024 1280x960 1280x854 1280x800 1280x720 1152x768
1024x768 800x600 848x480 720x480 640x480
apport information
** Attachment added: BootDmesg.txt
https://bugs.edge.launchpad.net/bugs/656100/+attachment/1676861/+files/BootDmesg.txt
--
[R200] ../../radeon/radeon_cs_gem.c:181: cs_gem_write_reloc: Assertion
`boi-space_accounted' failed.
https://bugs.launchpad.net/bugs/656100
You
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.edge.launchpad.net/bugs/656100/+attachment/1676862/+files/CurrentDmesg.txt
--
[R200] ../../radeon/radeon_cs_gem.c:181: cs_gem_write_reloc: Assertion
`boi-space_accounted' failed.
https://bugs.launchpad.net/bugs/656100
apport information
** Attachment added: DRM.card0.SVIDEO.1.txt
https://bugs.edge.launchpad.net/bugs/656100/+attachment/1676863/+files/DRM.card0.SVIDEO.1.txt
--
[R200] ../../radeon/radeon_cs_gem.c:181: cs_gem_write_reloc: Assertion
`boi-space_accounted' failed.
apport information
** Attachment added: GdmLog.txt
https://bugs.edge.launchpad.net/bugs/656100/+attachment/1676864/+files/GdmLog.txt
--
[R200] ../../radeon/radeon_cs_gem.c:181: cs_gem_write_reloc: Assertion
`boi-space_accounted' failed.
https://bugs.launchpad.net/bugs/656100
You received
apport information
** Attachment added: GdmLog1.txt
https://bugs.edge.launchpad.net/bugs/656100/+attachment/1676865/+files/GdmLog1.txt
--
[R200] ../../radeon/radeon_cs_gem.c:181: cs_gem_write_reloc: Assertion
`boi-space_accounted' failed.
https://bugs.launchpad.net/bugs/656100
You received
apport information
** Attachment added: GdmLog2.txt
https://bugs.edge.launchpad.net/bugs/656100/+attachment/1676866/+files/GdmLog2.txt
--
[R200] ../../radeon/radeon_cs_gem.c:181: cs_gem_write_reloc: Assertion
`boi-space_accounted' failed.
https://bugs.launchpad.net/bugs/656100
You received
apport information
** Attachment added: Lspci.txt
https://bugs.edge.launchpad.net/bugs/656100/+attachment/1676867/+files/Lspci.txt
--
[R200] ../../radeon/radeon_cs_gem.c:181: cs_gem_write_reloc: Assertion
`boi-space_accounted' failed.
https://bugs.launchpad.net/bugs/656100
You received
apport information
** Attachment added: PciDisplay.txt
https://bugs.edge.launchpad.net/bugs/656100/+attachment/1676868/+files/PciDisplay.txt
--
[R200] ../../radeon/radeon_cs_gem.c:181: cs_gem_write_reloc: Assertion
`boi-space_accounted' failed.
https://bugs.launchpad.net/bugs/656100
You
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.edge.launchpad.net/bugs/656100/+attachment/1676869/+files/ProcCpuinfo.txt
--
[R200] ../../radeon/radeon_cs_gem.c:181: cs_gem_write_reloc: Assertion
`boi-space_accounted' failed.
https://bugs.launchpad.net/bugs/656100
You
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.edge.launchpad.net/bugs/656100/+attachment/1676870/+files/ProcInterrupts.txt
--
[R200] ../../radeon/radeon_cs_gem.c:181: cs_gem_write_reloc: Assertion
`boi-space_accounted' failed.
apport information
** Attachment added: ProcModules.txt
https://bugs.edge.launchpad.net/bugs/656100/+attachment/1676871/+files/ProcModules.txt
--
[R200] ../../radeon/radeon_cs_gem.c:181: cs_gem_write_reloc: Assertion
`boi-space_accounted' failed.
https://bugs.launchpad.net/bugs/656100
You
apport information
** Attachment added: RelatedPackageVersions.txt
https://bugs.edge.launchpad.net/bugs/656100/+attachment/1676872/+files/RelatedPackageVersions.txt
--
[R200] ../../radeon/radeon_cs_gem.c:181: cs_gem_write_reloc: Assertion
`boi-space_accounted' failed.
apport information
** Attachment added: UdevDb.txt
https://bugs.edge.launchpad.net/bugs/656100/+attachment/1676873/+files/UdevDb.txt
--
[R200] ../../radeon/radeon_cs_gem.c:181: cs_gem_write_reloc: Assertion
`boi-space_accounted' failed.
https://bugs.launchpad.net/bugs/656100
You received
apport information
** Attachment added: UdevLog.txt
https://bugs.edge.launchpad.net/bugs/656100/+attachment/1676874/+files/UdevLog.txt
--
[R200] ../../radeon/radeon_cs_gem.c:181: cs_gem_write_reloc: Assertion
`boi-space_accounted' failed.
https://bugs.launchpad.net/bugs/656100
You received
apport information
** Attachment added: XorgLog.txt
https://bugs.edge.launchpad.net/bugs/656100/+attachment/1676875/+files/XorgLog.txt
--
[R200] ../../radeon/radeon_cs_gem.c:181: cs_gem_write_reloc: Assertion
`boi-space_accounted' failed.
https://bugs.launchpad.net/bugs/656100
You received
apport information
** Attachment added: XorgLogOld.txt
https://bugs.edge.launchpad.net/bugs/656100/+attachment/1676876/+files/XorgLogOld.txt
--
[R200] ../../radeon/radeon_cs_gem.c:181: cs_gem_write_reloc: Assertion
`boi-space_accounted' failed.
https://bugs.launchpad.net/bugs/656100
You
apport information
** Attachment added: Xrandr.txt
https://bugs.edge.launchpad.net/bugs/656100/+attachment/1676877/+files/Xrandr.txt
--
[R200] ../../radeon/radeon_cs_gem.c:181: cs_gem_write_reloc: Assertion
`boi-space_accounted' failed.
https://bugs.launchpad.net/bugs/656100
You received
apport information
** Attachment added: peripherals.txt
https://bugs.edge.launchpad.net/bugs/656100/+attachment/1676878/+files/peripherals.txt
--
[R200] ../../radeon/radeon_cs_gem.c:181: cs_gem_write_reloc: Assertion
`boi-space_accounted' failed.
https://bugs.launchpad.net/bugs/656100
You
apport information
** Attachment added: setxkbmap.txt
https://bugs.edge.launchpad.net/bugs/656100/+attachment/1676879/+files/setxkbmap.txt
--
[R200] ../../radeon/radeon_cs_gem.c:181: cs_gem_write_reloc: Assertion
`boi-space_accounted' failed.
https://bugs.launchpad.net/bugs/656100
You
apport information
** Attachment added: xdpyinfo.txt
https://bugs.edge.launchpad.net/bugs/656100/+attachment/1676880/+files/xdpyinfo.txt
--
[R200] ../../radeon/radeon_cs_gem.c:181: cs_gem_write_reloc: Assertion
`boi-space_accounted' failed.
https://bugs.launchpad.net/bugs/656100
You
apport information
** Attachment added: xkbcomp.txt
https://bugs.edge.launchpad.net/bugs/656100/+attachment/1676881/+files/xkbcomp.txt
--
[R200] ../../radeon/radeon_cs_gem.c:181: cs_gem_write_reloc: Assertion
`boi-space_accounted' failed.
https://bugs.launchpad.net/bugs/656100
You received
Oops sorry, I start the program with stellarTAB, but it's of course
called stellarium.
** Summary changed:
- [R200] [RV250] ../../radeon/radeon_cs_gem.c:181: cs_gem_write_reloc:
Assertion `boi-space_accounted' failed.
+ [R200] ../../radeon/radeon_cs_gem.c:181: cs_gem_write_reloc: Assertion
Sorry, I have no idea what is Gallium or the classic driver. Google lead
me to http://www.x.org/wiki/RadeonFeature.
I'm not sure whether I understand the page, but it appears to me that
Gallium applies only to R300 or higher. (#602267 was on R300). However,
here we are talking about R200.
--
This affects also Maverick Release Candidate.
Probably the bug is the same as before, but the effects are now much
worse than before.
The problem seems to occur whenever you change the selection in the left
window (either by scrolling or typing starting letters) before the right
window has been
The problem has now been fixed for the Lucid 10.04.1 Finnish Remix
Desktop CD.
The correct instructions are indeed at
https://help.ubuntu.com/community/LiveCDCustomization
sudo sed -i '/casper/d' extract-cd/casper/filesystem.manifest-desktop
If I read the previous comments correctly, nobody has
Public bug reported:
Binary package hint: ubiquity
If the user during keyboard selection double-clicks into the left list
- the mouse cursor will change to the rotating symbol
- Forward button will be greyed out
- Backward button will be greyed out
After that I did not find any way to complete
CA certificates obviously installed by this package
** Package changed: openjdk-6 (Ubuntu) = ca-certificates-java (Ubuntu)
--
Lucid openjdk/icedtea cannot verify applet signature
https://bugs.launchpad.net/bugs/566317
You received this bug notification because you are a member of Ubuntu
Bugs,
The CA certificates file exists twice on
/usr/share/ca-certificates-java/cacerts
/etc/ssl/certs/java/cacerts
I have not added any certificate in any phase and both files have
identical contents.
(There is also a symbolic link
/usr/lib/jvm/java-6-openjdk/jre/lib/security/cacerts -
Tested today with
$ apt-cache policy ca-certificates-javaca-certificates-java:
Installed: 20100406ubuntu1
Candidate: 20100406ubuntu1
Version table:
*** 20100406ubuntu1 0
500 http://fi.archive.ubuntu.com/ubuntu/ lucid/main Packages
100 /var/lib/dpkg/status
--
Lucid
** Also affects: openjdk-6 (Ubuntu)
Importance: Undecided
Status: New
--
Lucid openjdk/icedtea cannot verify applet signature
https://bugs.launchpad.net/bugs/566317
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Sorry, my conclusions in #5 was incorrect.
The root certificate is indeed in the certificate store. It is
Owner: OU=Class 3 Public Primary Certification Authority, O=VeriSign, Inc., C=
US
Issuer: OU=Class 3 Public Primary Certification Authority, O=VeriSign, Inc., C
=US
Serial number:
For comparison the certificate chain as built by Sun's Java (also on
Lucid) (Sorry, I wasn't able to resize the dialog to show more info)
** Attachment added: cert chain in Sun Java
https://bugs.launchpad.net/ubuntu/+source/openjdk-6/+bug/566317/+attachment/1651116/+files/sampo-cert-sun.png
Options are documented in Lucid at least. (I think it happened already
earlier)
** Changed in: apt (Ubuntu)
Status: New = Fix Released
--
apt-get install option --[no]-install-recommends should be documented
https://bugs.launchpad.net/bugs/310329
You received this bug notification
Yes, this happens from time to time lin Lucid. It looks like a network
error (I guess it fetches the description from a Canonical server). But
it happens at least 10 times more frequently than network errors in
other programs, e.g. Browser. So I'm sure this could be somehow improved
in
Public bug reported:
Binary package hint: kpackagekit
In Lucid kpackagekit shows a fix in the wrong group from time to time.
This is difficult to reproduce, because it depends on the package
versions installed and on the package versions available from the repos.
So in normal usage (i.e. if you
** Attachment added: screenshot
https://bugs.launchpad.net/bugs/649284/+attachment/1645815/+files/kpackagekit.png
** Tags added: apport-collected
** Description changed:
Binary package hint: kpackagekit
In Lucid kpackagekit shows a fix in the wrong group from time to time.
This is
apport information
** Attachment added: Dependencies.txt
https://bugs.edge.launchpad.net/bugs/649284/+attachment/1645860/+files/Dependencies.txt
** Summary changed:
- kpackagekit shows incorrect security classifiaction
+ kpackagekit shows incorrect security classification
--
kpackagekit
Because the linux-generic fix in question was an ABI change, a new
package not previously installed was pulled. However, it was not from
security either:
$ apt-cache policy linux-image-generic
linux-image-generic:
Installed: 2.6.32.25.27
Candidate: 2.6.32.25.27
Version table:
***
Please ignore comment #33. It turned out that my device (D-Link DWA-140
B2) contains an RT3070, not an RT2870. Getting the driver source from
Ralink and building makes it work on Lucid; Maverick not yet tested
Sorry about the noise.
--
USB WiFi adapter with rt2870 chipset won't connect
I just learned that there is an important difference between a DWA-140
and a DWA-140 ver. B2. The DWA-140 contains an RT2870, the DWA-140 B2
contains an RT3070.
The device I have borrowed is a B2, so the apport logs above apply to
RT3070 only.
In Lucid downloading and building the RT3070 driver
Tested as advised by comment #6 (daily build of Sep. 24). It still
doesn't work in Maverick. I'll try to collect some logs.
** Changed in: linux (Ubuntu)
Status: Expired = New
** Summary changed:
- Lucid: Wireless USB DLink DWA-140 does not connect
+ Lucid/Maverick: Wireless USB DLink
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: i386
AudioDevicesInUse:
Cannot stat file /proc/4088/fd/40: Stale NFS file handle
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 2612 F pulseaudio
CRDA: Error: [Errno 2]
apport information
** Attachment added: AcpiTables.txt
https://bugs.edge.launchpad.net/bugs/573905/+attachment/1632480/+files/AcpiTables.txt
--
Lucid/Maverick: Wireless USB DLink DWA-140 does not connect
https://bugs.launchpad.net/bugs/573905
You received this bug notification because you
apport information
** Attachment added: AlsaDevices.txt
https://bugs.edge.launchpad.net/bugs/573905/+attachment/1632481/+files/AlsaDevices.txt
--
Lucid/Maverick: Wireless USB DLink DWA-140 does not connect
https://bugs.launchpad.net/bugs/573905
You received this bug notification because
apport information
** Attachment added: AplayDevices.txt
https://bugs.edge.launchpad.net/bugs/573905/+attachment/1632482/+files/AplayDevices.txt
--
Lucid/Maverick: Wireless USB DLink DWA-140 does not connect
https://bugs.launchpad.net/bugs/573905
You received this bug notification because
apport information
** Attachment added: ArecordDevices.txt
https://bugs.edge.launchpad.net/bugs/573905/+attachment/1632483/+files/ArecordDevices.txt
--
Lucid/Maverick: Wireless USB DLink DWA-140 does not connect
https://bugs.launchpad.net/bugs/573905
You received this bug notification
apport information
** Attachment added: BootDmesg.txt
https://bugs.edge.launchpad.net/bugs/573905/+attachment/1632484/+files/BootDmesg.txt
--
Lucid/Maverick: Wireless USB DLink DWA-140 does not connect
https://bugs.launchpad.net/bugs/573905
You received this bug notification because you
apport information
** Attachment added: Card0.Codecs.codec97.0.ac97.0.0.txt
https://bugs.edge.launchpad.net/bugs/573905/+attachment/1632486/+files/Card0.Codecs.codec97.0.ac97.0.0.txt
--
Lucid/Maverick: Wireless USB DLink DWA-140 does not connect
https://bugs.launchpad.net/bugs/573905
You
apport information
** Attachment added: Card0.Amixer.values.txt
https://bugs.edge.launchpad.net/bugs/573905/+attachment/1632485/+files/Card0.Amixer.values.txt
--
Lucid/Maverick: Wireless USB DLink DWA-140 does not connect
https://bugs.launchpad.net/bugs/573905
You received this bug
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.edge.launchpad.net/bugs/573905/+attachment/1632490/+files/CurrentDmesg.txt
--
Lucid/Maverick: Wireless USB DLink DWA-140 does not connect
https://bugs.launchpad.net/bugs/573905
You received this bug notification because
apport information
** Attachment added: Card0.Codecs.codec97.0.ac97.0.0.regs.txt
https://bugs.edge.launchpad.net/bugs/573905/+attachment/1632487/+files/Card0.Codecs.codec97.0.ac97.0.0.regs.txt
--
Lucid/Maverick: Wireless USB DLink DWA-140 does not connect
apport information
** Attachment added: Lspci.txt
https://bugs.edge.launchpad.net/bugs/573905/+attachment/1632492/+files/Lspci.txt
--
Lucid/Maverick: Wireless USB DLink DWA-140 does not connect
https://bugs.launchpad.net/bugs/573905
You received this bug notification because you are a
apport information
** Attachment added: Lsusb.txt
https://bugs.edge.launchpad.net/bugs/573905/+attachment/1632493/+files/Lsusb.txt
--
Lucid/Maverick: Wireless USB DLink DWA-140 does not connect
https://bugs.launchpad.net/bugs/573905
You received this bug notification because you are a
1 - 100 of 255 matches
Mail list logo
