I saw this (once) in 22.04 a few days ago. Hence the automatic
confirmation. It was not submitted because it was a dupe.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1660713
Title:
/usr/bin/atril:
For anyone looking for a workaround, thanks to andersk above. I edited
/usr/lib/python3.10/sysconfig.py per this diff:
usr/lib/python3.10$ diff -p sysconfig.py~ sysconfig.py
*** sysconfig.py~ 2022-02-26 03:21:15.0 -0500
--- sysconfig.py2022-03-10 21:09:02.572726493 -0500
Confirmed: I ran into this independently. I tried uninstalling
python3.9-venv, just in case it was interfering, and updating pip with
itself to 22.0.3, and neither helped.
$ python3.10 -mvenv 310
$ python3.9 -mvenv 39
$ ls 310/bin
activate activate.csh activate.fish Activate.ps1 python python
I brought this up on the linux-usb email list and was told it was more
likely to be an issue in the filesystem code. In addition, that code
(and the USB code) don't expect an MSC USB device to behave badly, and
there's no guarantee that if it does, Linux will not crash. In this
case, the filesystem
Thank you. Attaching lspci-v output in preparation for reporting to the
linux-usb mailing list. lsusb -v output is already attached to the first
port.
** Attachment added: "lspci-v.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871143/+attachment/5389646/+files/lspci-v.txt
--
You
I'm wrong, I got this to happen on 4.10, which is quite old, so I'm not
sure if it's worth going back much further in time.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871143
Title:
Kernel crash
I was able to reproduce the problem after a few tries with the
5.7.0-050700-generic kernel. I then started trying older kernels. It
appears the problem started somewhere between 4.10.0 an 4.18.0. But
sometimes it takes several tries to reproduce, so I'll continue some ad-
hoc bisecting to see if I
Thanks for the reply.
TinyUSB runs on the microcontroller board; it is the USB stack
implementation used by the software on the board. So it doesn't touch
the kernel, by definition. It is behaving in some way that is unexpected
to the Linux driver, and causing bad behavior on the part of the drive
Another crash, with a different backtrace. with a different board, but
related USB implementation. Since the report above, the underlying USB
implementation on the boards has changed somewhat, but the circumstances
of the crash are similar:
[40859.232293] usb 1-1.3: USB disconnect, device number 3
Key part of dmesg is:
[76704.227672] cdc_acm 1-1.4:1.0: failed to set dtr/rts
[76704.936301] usb 1-1.4: USB disconnect, device number 11
[76704.951638] blk_update_request: I/O error, dev sdc, sector 1110 op
0x1:(WRITE) flags 0x0 phys_seg 2 prio class 0
[76704.951644] Buffer I/O error on dev sdc1,
Public bug reported:
Device is an Adafruit microcontroller board running
https://github.com/adafruit/circuitpython, using the TinyUSB USB stack:
https://github.com/hathach/tinyusb.
Device presents a composite USB device that includes MSC, CDC, HID, and MIDI
Device was commanded to forcibly reform
Error appeared during latest set of package updates.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860851
Title:
blueman-applet crashed with UnicodeDecodeError: 'utf-8' codec can't
decode byte 0x
>Can we get a title that describes better this bug?
If you are logged in, you can edit the title yourself. Just click the little
circle icon of a pencil to the right of the title.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
To Andrea, Sam, and other developers: The title of this bug is broad and
describes a problem encountered in multiple window managers. That is
what draws people to this bug. I would suggest that you edit the title
and narrow it to describe the manager(s) in which it has been fixed, and
to add text
More on "modprobe xfs" hanging:
Doing strace on "modprobe xfs" shows that it tries to read
/sys/module/xfs/initstate multiple times. Reading it always returns
"coming". modprobe tries a bunch of times and then hangs.
I tried "modprobe -r xfs" to unload xfs and it hangs in the same way.
--
You r
I have the same problem in 10.04. The tree of what's going on:
/usr/bin/dpkg --status-fd 29 --configure linux-image-2.6.32-45-generic
linux-image-generic linux-generic mesa-utils
/usr/bin/perl /var/lib/dpkg/info/linux-image-2.6.32-45-generic.postinst
configure
/bin/sh -e /usr/sbin/grub-
** Summary changed:
- Auto-hidden Unity Launcher will not reveal when mouse pushed to left side in
VirtualBox
+ Auto-hide Unity Launcher will not reveal when mouse pushed to left side in
VirtualBox or VMware
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/905603
Title:
Crash installing Precise alpha1 on VMWare Player 8.0.1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+so
Public bug reported:
Installing Precise 64-bit alpha1 on a fresh VMWare Player VM, got this
crash twice in a row.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: ubiquity 2.9.5
ProcVersionSignature: Ubuntu 3.2.0-2.5-generic 3.2.0-rc3
Uname: Linux 3.2.0-2-generic x86_64
ApportVersion: 1.90-0
My oneiric is completely updated as of today, and I can still generate
this crash (same scenario as comment #7). The python stacktrace is:
$ gedit
Traceback (most recent call last):
File "/usr/lib/gedit/plugins/pythonconsole/__init__.py", line 65, in
do_create_configure_widget
return config
*** This bug is a duplicate of bug 849225 ***
https://bugs.launchpad.net/bugs/849225
Yes, still an issue, see #849225.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/851499
Title:
gedit crashed
*** This bug is a duplicate of bug 511379 ***
https://bugs.launchpad.net/bugs/511379
** This bug has been marked a duplicate of bug 511379
Jockey fails to install Broadcom STA wireless driver (BCM4311)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I was able to tget this working:
1. Ran update-manager to update everything post-beta2, as of Oct 1 evening
(EDT).
2. Used synaptic to purge bcmwl-kernel-source
3. Tried activating driver again. It downloaded, built, and activated correctly.
Omitting step 2 caused jockey to complain after every a
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/864442
Title:
bcmwl-kernel-source 5.100.82.38 bdcom-0ubuntu4: bcmwl kernel module
failed to build
To manage notifications about this bug go to:
https:
Public bug reported:
Installed lubuntu 11.10 beta2 on Dell Mini 9. Tried to activate
restricted driver.
ProblemType: Package
DistroRelease: Ubuntu 11.10
Package: bcmwl-kernel-source 5.100.82.38+bdcom-0ubuntu4
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic i68
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/851499
Title:
gedit crashed with SIGSEGV in g_closure_invoke()
To manage notifications about this bug go to:
https://b
Re #8: I had the same problem (still empty after update), but somehow
managed to get the lenses to populate by searching for "", then hitting
return. I cannot remember the exact sequence, but magically it all
populated. Perhaps it was actually generating the list in the background
while I was fiddl
The symptoms described are due to changes made for bug 432631. Perhaps
this should be marked as a duplicate (though it's kind of an anti-
duplicate!)
The documentation of this change is in
/usr/share/doc/sudo/changelog.Debian.gz:
sudo (1.7.2p1-1ubuntu4) lucid; urgency=low
* env.c: Revert addit
Lucid Lynx Beta1 does not include this fix, because it was assembled
before the fix was released. I successfully installed a recent daily
netbook build of Lucid (http://cdimage.ubuntu.com/ubuntu-netbook/daily-
live/) on a Dell Mini 9 with a stock 4GB STEC SSD. The build I used was
created after the
I believe this is an actual bug. Running jockey-gtk from
System->Administration->Hardware Drivers ignores any proxy setup
specified in synaptic, and there is no visible mechanism for setting a
proxy in the jockey UI.
A workaround is to have proxy setups in environment variables:
(http_proxy, etc.)
To explicate #3: Someone converted this bug to a question. I have
converted it back to a bug.
--
restricted driver downloader ignore proxy settings
https://bugs.launchpad.net/bugs/373795
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
A more thorough discussion of this issue is in yet another Fedora bug:
https://bugzilla.redhat.com/show_bug.cgi?id=498115.
When I installed karmic, I too was falsely alarmed by palimpsest's
warning about a single reallocated bad sector in a disk I've been using
for years. I ran the manufacturer's
@Manoj (2009-07-09): I believe this bug is still present in
2.6.28-13.44, the latest released kernel. Is there any reason to expect
it is fixed in 2.6.28-14.46 (in jaunty proposed)? Do you have a specific
patch in mind?
A colleague had these symptoms on a Dell E6500 (has ICH10 and Nvidia
graphics)
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/27434179/Dependencies.txt
** Also affects: python-imaging (Debian)
Importance: Undecided
Status: New
--
PIL Image.show() using eog doesn't work second time
https://bugs.launchpad.net/bugs/382987
You received this
Public bug reported:
Binary package hint: python-imaging
This reports an issue with a fix for bug #67755. The fix done upstream
in Debian (321658) does not work well for "eog". I attempted to reopen
the Debian bug, but it is archived and cannot be reopened apparently. I
started to reopen 67755, b
Never mind reopening. Filing a new, more precise bug about issues with
eog.
--
im.show fails in absence of xv
https://bugs.launchpad.net/bugs/67755
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs
Reopening. See next comment.
** Changed in: python-imaging (Ubuntu)
Status: Fix Released => New
** Changed in: python-imaging (Ubuntu)
Status: New => Fix Released
--
im.show fails in absence of xv
https://bugs.launchpad.net/bugs/67755
You received this bug notification because yo
On jaunty x86_64 I successfully built and tested OpenCV from its SVN
trunk, as of 2009-05-18 (1765). I did not have to apply any patches or
add links to get it to build. I used the latest ffmpeg -dev libraries
from the jaunty repository.
I originally got the img_convert() undeclared error because
>I think that /etc/default/grub-install should be sourced from grub-
install at its first line and that would be fine.
I see the /etc/default is the right place to remember such an option.
However, all the other files in there just set options, e.g.
UPPERCASE_OPTION=foo
So putting an actual co
I had this problem because of Novell ZENworks. It overwrites sectors in
the "unused" space at the beginning of a disk. This sector is part of
the space where grub writes the stage1.5 files.
For more information about what ZenWorks does, see
http://www.intl.novell.com/communities/node/5839/grub-and
I had the same problem with my C600, which is due to some issue with
recognizing the CD-ROM (removing it is a workaround). I've upgraded to
the Ibex beta as of 2008-10-19, and the problem is fixed. Another
problem I had with stalling while recognizing the primary HDD is also
fixed.
--
Ubuntu fail
41 matches
Mail list logo
