[Bug 67755] Re: im.show fails in absence of xv
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 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 67755] Re: im.show fails in absence of xv
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@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 382987] [NEW] PIL Image.show() using eog doesn't work second time
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, but decided a more precise bug report would be
better. If this is incorrect protocol, I apologize.
I'm using PIL 1.1.6 on Ubuntu jaunty, and noticed a problem with
invoking im.show() more than once without closing the image viewing
window. On this system, im.show() uses "eog" to view the images. If you
do something like:
>>>im.show() # don't close the eog window
>>>im.show()
then the second im.show() causes an error. The actual images don't
matter: they could be the same or different.
The two im.show() calls invoke Image._showxv() twice, which effectively
does this:
os.system("(eog /tmp/tmp123; rm -f /tmp/tmp123)&")
os.system("(eog /tmp/tmp456; rm -f /tmp/tmp456)&")
However, eog is very clever and tries to reuse its first instance. So
the second instantiation of eog exits immediately after notifying the
first to display /tmp/tmp456. But then the file disappears out from
under it.
The _showxv() code shows a similar problem already came up on OS X, and
a "sleep 20" was inserted before the "rm". For eog, another, perhaps
more elegant solution is to invoke eog as "eog -n", which always starts
a new instance instead of reusing an existing one.
ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
Package: python-imaging 1.1.6-3ubuntu1
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: python-imaging
Uname: Linux 2.6.28-11-generic i686
** Affects: python-imaging (Ubuntu)
Importance: Undecided
Status: New
** Affects: python-imaging (Debian)
Importance: Undecided
Status: New
** Tags: apport-bug i386
--
PIL Image.show() using eog doesn't work second time
https://bugs.launchpad.net/bugs/382987
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 382987] Re: PIL Image.show() using eog doesn't work second time
** 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 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 26058] Re: after boot into Windows XP, grub menu is not displayed and computer reboot
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-zisd . To solve this, I did not use grub-install and did not remove the stage1.5 files as described above. Instead, I started grub (from a rescue disk) and did this: grub> install /boot/grub/stage1 (hd1) /boot/grub/stage2 p /boot/grub/menu.lst This makes stage1 go directly to the stage2 files. "install" is a lower- level command than "setup"; "setup" will use the stage1.5 files if it can find them. I'd have to redo this if grub is updated. I'd like to have grub-install do this automatically, perhaps with a new option. But there needs to be someplace to record that skipping stage1.5 is in effect. I'm not sure where this should be recorded for the benefit of grub-install. My setup: Two SATA disks: /dev/sda: Windows XP with Novell ZENworks installed (not my choice) /dev/sdb: Ubuntu Jaunty I choose which disk to boot from the BIOS menu, not from grub. -- after boot into Windows XP, grub menu is not displayed and computer reboot https://bugs.launchpad.net/bugs/26058 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 26058] Re: after boot into Windows XP, grub menu is not displayed and computer reboot
>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 command line in is a new paradigm. That could be OK, but it is new. You could instead have grub-install read an environment variable: OPTIONS="--ignore-stage1_5" or maybe more specifically: IGNORE_STAGE1_5=true It probably doesn't really matter. I am thinking more about whether more options or variations might want to be set there in the future. The options might be a bit more complicated, and may not be so easily sourced as just giving an alternate command line. -- after boot into Windows XP, grub menu is not displayed and computer reboot https://bugs.launchpad.net/bugs/26058 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 311188] Re: Fails to find ffmpeg headers
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 HAVE_FFMPEG_SWSCALE was not defined, but fixed it by installing libswscale-dev from the jaunty repositories. I also needed various other ffmpeg libraries to get all the features to be included. I built using cmake, not autoconf: I get various errors trying to build with autoconf. -- Fails to find ffmpeg headers https://bugs.launchpad.net/bugs/311188 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 246263] Re: Ubuntu fail to start on a Dell latitude c600
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 to start on a Dell latitude c600 https://bugs.launchpad.net/bugs/246263 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 346691] Re: 2.6.28-11 causes massive data corruption on 64 bit installations
@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). The problem is not as pervasive as that of some of the original reporters, but there has been significant filesystem corruption every few days. We have updated his kernel to a 2.6.29 kernel just today, and hope to see an improvement. -- 2.6.28-11 causes massive data corruption on 64 bit installations https://bugs.launchpad.net/bugs/346691 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 373795] Re: restricted driver downloader ignore proxy settings
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.), and then run "sudo jockey-gtk" from the command line. -- 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 373795] Re: restricted driver downloader ignore proxy settings
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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 445852] Re: devkit-disks-probe-ata-smart causes HSM Violations on SSD, and potential hardware death
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 fix was released. Though I did not have the reported problem, I did have peculiar, similar symptoms with karmic and after. The final test for those of you with problem SSD's, it seems to me, is to install from of the daily-live builds (or wait for Beta2). That will require no patching during the install, and should just work. Before I installed, I booted from a USB stick and did a secure erase of the SSD (see #211 above), which only took a short time. -- devkit-disks-probe-ata-smart causes HSM Violations on SSD, and potential hardware death https://bugs.launchpad.net/bugs/445852 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 556293] Re: sudo does not keep http_proxy environment variable
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 addition of "http_proxy" again. This was an Ubuntu specific EBW hack, caused inconsistencies with other proxy variables (such as https_proxy and ftp_proxy), made sudo incompatible to upstream behaviour/documentation. This is solved in a much better way in apt itself and gnome-network-properties now. (LP: #432631) [changes in intervening versions elided] -- Martin Pitt https://bugs.launchpad.net/bugs/556293 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 412152] Re: gnome-disk-utility nags me too much that my disk is failing
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 test, which said there was no problem. I believe palimpsests's author, as quoted in #7, is not as well as informed as he could be about the non-zero number of failures one typically sees in disks these days. ** Bug watch added: Red Hat Bugzilla #498115 https://bugzilla.redhat.com/show_bug.cgi?id=498115 -- gnome-disk-utility nags me too much that my disk is failing https://bugs.launchpad.net/bugs/412152 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 1860851] Re: blueman-applet crashed with UnicodeDecodeError: 'utf-8' codec can't decode byte 0x8e in position 4: invalid start byte
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 0x8e in position 4: invalid start byte To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/blueman/+bug/1860851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871143] Re: Kernel crash during USB device enumeration or mounting
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 changes abruptly out from under the filesystem code. linux-usb thread: https://marc.info/?l=linux-usb&m=159387610928589&w=2 I suppose you can close this now. I wish Linux were more robust about this, but it appears to be a "won't fix" from their point of view. -- 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 during USB device enumeration or mounting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871143] [NEW] Kernel crash during USB device enumeration or mounting
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 reformat its MSC FAT12 filesystem and then reset, which causes a USB reset and re-enumeration. This causes some USB kernel code to crash, much of the time, though not quite all the time. I work for Adafruit and the maintainer of TinyUSB also works for Adafruit, so we can provide further help to track this down. Attached is the dmesg file for the crash. I tried uploading the dump file from kdump, but launchpad is timing out. The dump file is available at: https://drive.google.com/open?id=1ka3ySSccEMRSmnYgI9X16IndPDmIKTD6 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-21-generic 5.4.0-21.25 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: halbert1857 F pulseaudio /dev/snd/controlC2: halbert1857 F pulseaudio CurrentDesktop: X-Cinnamon Date: Mon Apr 6 11:09:43 2020 HibernationDevice: RESUME=UUID=55694d39-bafe-45f8-ba05-ea5d54a93a85 InstallationDate: Installed on 2017-09-19 (929 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) IwConfig: eno1 no wireless extensions. lono wireless extensions. MachineType: Dell Inc. OptiPlex 7010 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=b3868153-c620-4efe-9dfc-8059dc6288a8 ro quiet splash crashkernel=512M-:192M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 RfKill: 0: hci0: Bluetooth Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-03-08 (28 days ago) dmi.bios.date: 06/28/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A29 dmi.board.name: 0WR7PY dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA29:bd06/28/2018:svnDellInc.:pnOptiPlex7010:pvr01:rvnDellInc.:rn0WR7PY:rvrA01:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 7010 dmi.product.sku: OptiPlex 7010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "dmesg file from kdump" https://bugs.launchpad.net/bugs/1871143/+attachment/5347818/+files/dmesg.202004061013 -- 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 during USB device enumeration or mounting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871143] Re: Kernel crash during USB device enumeration or mounting
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, logical block 1109, lost async page write [76704.951647] Buffer I/O error on dev sdc1, logical block 1110, lost async page write [76704.951656] blk_update_request: I/O error, dev sdc, sector 1128 op 0x1:(WRITE) flags 0x0 phys_seg 2 prio class 0 [76704.951658] Buffer I/O error on dev sdc1, logical block 1127, lost async page write [76704.951661] Buffer I/O error on dev sdc1, logical block 1128, lost async page write [76704.951679] blk_update_request: I/O error, dev sdc, sector 1150 op 0x1:(WRITE) flags 0x0 phys_seg 2 prio class 0 [76704.951682] Buffer I/O error on dev sdc1, logical block 1149, lost async page write [76704.951684] Buffer I/O error on dev sdc1, logical block 1150, lost async page write [76704.951689] blk_update_request: I/O error, dev sdc, sector 1174 op 0x1:(WRITE) flags 0x0 phys_seg 2 prio class 0 [76704.951691] Buffer I/O error on dev sdc1, logical block 1173, lost async page write [76704.951693] Buffer I/O error on dev sdc1, logical block 1174, lost async page write [76704.951717] blk_update_request: I/O error, dev sdc, sector 1194 op 0x1:(WRITE) flags 0x0 phys_seg 2 prio class 0 [76704.951718] Buffer I/O error on dev sdc1, logical block 1193, lost async page write [76704.951719] Buffer I/O error on dev sdc1, logical block 1194, lost async page write [76704.951722] blk_update_request: I/O error, dev sdc, sector 1212 op 0x1:(WRITE) flags 0x0 phys_seg 2 prio class 0 [76704.951734] blk_update_request: I/O error, dev sdc, sector 1232 op 0x1:(WRITE) flags 0x0 phys_seg 2 prio class 0 [76704.951739] blk_update_request: I/O error, dev sdc, sector 1252 op 0x1:(WRITE) flags 0x0 phys_seg 2 prio class 0 [76704.951748] blk_update_request: I/O error, dev sdc, sector 1272 op 0x1:(WRITE) flags 0x0 phys_seg 2 prio class 0 [76704.951751] blk_update_request: I/O error, dev sdc, sector 1290 op 0x1:(WRITE) flags 0x0 phys_seg 2 prio class 0 [76707.579590] usb 1-1.4: new full-speed USB device number 12 using ehci-pci [76707.691410] usb 1-1.4: New USB device found, idVendor=239a, idProduct=8014, bcdDevice= 1.00 [76707.691413] usb 1-1.4: New USB device strings: Mfr=2, Product=3, SerialNumber=1 [76707.691415] usb 1-1.4: Product: Metro M0 Express [76707.691417] usb 1-1.4: Manufacturer: Adafruit Industries LLC [76707.691418] usb 1-1.4: SerialNumber: DFAE9D970323D4050213E2932141E0FF [76707.692717] general protection fault: [#1] SMP PTI [76707.692723] CPU: 3 PID: 75883 Comm: kworker/3:1 Kdump: loaded Not tainted 5.4.0-21-generic #25-Ubuntu [76707.692725] Hardware name: Dell Inc. OptiPlex 7010/0WR7PY, BIOS A29 06/28/2018 [76707.692732] Workqueue: usb_hub_wq hub_event [76707.692738] RIP: 0010:__kmalloc+0xa5/0x270 [76707.692741] Code: 65 49 8b 50 08 65 4c 03 05 40 a0 76 4d 4d 8b 38 4d 85 ff 0f 84 93 01 00 00 41 8b 59 20 49 8b 39 48 8d 4a 01 4c 89 f8 4c 01 fb <48> 33 1b 49 33 99 70 01 00 00 65 48 0f c7 0f 0f 94 c0 84 c0 74 bd [76707.692743] RSP: 0018:a85b4316f6c0 EFLAGS: 00010286 [76707.692745] RAX: af73d556 RBX: af73d556 RCX: 00140e86 [76707.692747] RDX: 00140e85 RSI: 0cc0 RDI: 0002f100 [76707.692749] RBP: a85b4316f6f0 R08: 8ef6ce1af100 R09: 8ef6cc403180 [76707.692751] R10: 0cc0 R11: 01320122 R12: 0cc0 [76707.692752] R13: 00b8 R14: 8ef6cc403180 R15: af73d556 [76707.692755] FS: () GS:8ef6ce18() knlGS: [76707.692757] CS: 0010 DS: ES: CR0: 80050033 [76707.692758] CR2: 7fd69c2ee000 CR3: 000210f8e006 CR4: 001606e0 [76707.692760] Call Trace: [76707.692767] ? usb_alloc_urb+0x29/0x60 [76707.692772] usb_alloc_urb+0x29/0x60 [76707.692779] acm_probe+0x6da/0xdb0 [cdc_acm] [76707.692786] usb_probe_interface+0xed/0x290 [76707.692792] really_probe+0x2b3/0x3e0 [76707.692796] driver_probe_device+0xbc/0x100 [76707.692799] __device_attach_driver+0x71/0xd0 [76707.692803] ? driver_allows_async_probing+0x50/0x50 [76707.692807] bus_for_each_drv+0x84/0xd0 [76707.692810] __device_attach+0xe1/0x160 [76707.692814] device_initial_probe+0x13/0x20 [76707.692817] bus_probe_device+0x8f/0xa0 [76707.692820] device_add+0x3c7/0x6b0 [76707.692825] ? _cond_resched+0x19/0x30 [76707.692828] usb_set_configuration+0x433/0x7d0 [76707.692833] ? kernfs_activate+0x77/0x80 [76707.692836] generic_probe+0x43/0x60 [76707.692839] usb_probe_device+0x31/0x70 [76707.692842] really_probe+0x2b3/0x3e0 [76707.692846] driver_probe_device+0xbc/0x100 [76707.692849] __device_attach_driver+0x71/0xd0 [76707.692853] ? driver_allows_async_probing+0x50/0x50 [76707.692856] bus_for_each_drv+0x84/0xd0 [76707.692860] __device_attach+0xe1/
[Bug 1871143] Re: Kernel crash during USB device enumeration or mounting
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 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 during USB device enumeration or mounting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871143] Re: Kernel crash during USB device enumeration or mounting
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 driver. It is possible this is a timing or kernel driver state machine. These crashes occur when I reset the board. So the USB device is forcibly disconnected, and then immediately tries to re-enumerate. This is much faster than the usual unplug/replug time you might see, if say, you unplugged a replugged a USB keyboard or USB flash drive. Would a USB trace be helpful to you? I can use a Beagle and get a trace file. Is this the right place to continue discussing this bug, or should it be in some Linux kernel bug system? Thanks. -- 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 during USB device enumeration or mounting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871143] Re: Kernel crash during USB device enumeration or mounting
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 can narrow it down. For posterity, here is how I'm reproducing. It may take several tries, but it seems to happen about 1/3 of the time. I don't expect you to need to follow all of this for now: Using CircuitPython 5.3.0 on Adafruit Metro M0 board. Connect to REPL and do: >>> import storage >>> storage.erase_filesystem() can cause an immediate kernel crash, or it might be delayed by several seconds. -- 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 during USB device enumeration or mounting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871143] Re: Kernel crash during USB device enumeration or mounting
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 during USB device enumeration or mounting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871143] Re: Kernel crash during USB device enumeration or mounting
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 34 [40859.250102] FAT-fs (sdc): unable to read boot sector to mark fs as dirty [40862.270362] usb 1-1.3: new full-speed USB device number 35 using ehci-pci [40862.387543] usb 1-1.3: New USB device found, idVendor=239a, idProduct=8014, bcdDevice= 1.00 [40862.387546] usb 1-1.3: New USB device strings: Mfr=2, Product=3, SerialNumber=1 [40862.387548] usb 1-1.3: Product: Metro M0 Express [40862.387550] usb 1-1.3: Manufacturer: Adafruit Industries LLC [40862.387552] usb 1-1.3: SerialNumber: DFAE9D970323D4050213E2932141E0FF [40862.388969] cdc_acm 1-1.3:1.0: ttyACM0: USB ACM device [40862.392200] usb-storage 1-1.3:1.2: USB Mass Storage device detected [40862.392599] scsi host6: usb-storage 1-1.3:1.2 [40862.397276] input: Adafruit Industries LLC Metro M0 Express Keyboard as /devices/pci:00/:00:1a.0/usb1/1-1/1-1.3/1-1.3:1.3/0003:239A:8014.0016/input/input97 [40862.454787] input: Adafruit Industries LLC Metro M0 Express Mouse as /devices/pci:00/:00:1a.0/usb1/1-1/1-1.3/1-1.3:1.3/0003:239A:8014.0016/input/input98 [40862.455133] input: Adafruit Industries LLC Metro M0 Express Consumer Control as /devices/pci:00/:00:1a.0/usb1/1-1/1-1.3/1-1.3:1.3/0003:239A:8014.0016/input/input99 [40862.455322] input: Adafruit Industries LLC Metro M0 Express as /devices/pci:00/:00:1a.0/usb1/1-1/1-1.3/1-1.3:1.3/0003:239A:8014.0016/input/input100 [40862.455689] hid-generic 0003:239A:8014.0016: input,hidraw3: USB HID v1.11 Keyboard [Adafruit Industries LLC Metro M0 Express] on usb-:00:1a.0-1.3/input3 [40863.416330] scsi host6: scsi scan: INQUIRY result too short (5), using 36 [40863.416338] scsi 6:0:0:0: Direct-Access Adafruit Metro M0 Express 1.0 PQ: 0 ANSI: 2 [40863.416732] sd 6:0:0:0: Attached scsi generic sg3 type 0 [40863.418307] sd 6:0:0:0: [sdc] 4089 512-byte logical blocks: (2.09 MB/2.00 MiB) [40863.419611] sd 6:0:0:0: [sdc] Write Protect is off [40863.419615] sd 6:0:0:0: [sdc] Mode Sense: 03 00 00 00 [40863.420650] sd 6:0:0:0: [sdc] No Caching mode page found [40863.420656] sd 6:0:0:0: [sdc] Assuming drive cache: write through [40863.464434] sdc: sdc1 [40863.472071] sd 6:0:0:0: [sdc] Attached SCSI removable disk [40864.285807] FAT-fs (sdc1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. [40866.329111] cdc_acm 1-1.3:1.0: failed to set dtr/rts [40866.349335] general protection fault: [#1] SMP PTI [40866.349339] CPU: 3 PID: 134345 Comm: systemd-udevd Kdump: loaded Not tainted 5.4.0-28-generic #32-Ubuntu [40866.349340] Hardware name: Dell Inc. OptiPlex 7010/0WR7PY, BIOS A29 06/28/2018 [40866.349346] RIP: 0010:kmem_cache_alloc_trace+0x88/0x230 [40866.349348] Code: 65 49 8b 50 08 65 4c 03 05 fd 95 36 60 4d 8b 38 4d 85 ff 0f 84 80 01 00 00 41 8b 59 20 49 8b 39 48 8d 4a 01 4c 89 f8 4c 01 fb <48> 33 1b 49 33 99 70 01 00 00 65 48 0f c7 0f 0f 94 c0 84 c0 74 bd [40866.349349] RSP: 0018:a5f589357bf0 EFLAGS: 00010206 [40866.349350] RAX: 02f74afdcaf6e6c0 RBX: 02f74afdcaf6e6c0 RCX: 001b8e41 [40866.349351] RDX: 001b8e40 RSI: 0dc0 RDI: 0002f100 [40866.349352] RBP: a5f589357c20 R08: 935a0e1af100 R09: 935a0c403180 [40866.349353] R10: 0001 R11: 0006 R12: 0dc0 [40866.349354] R13: 0098 R14: 935a0c403180 R15: 02f74afdcaf6e6c0 [40866.349355] FS: 7f4619b2e880() GS:935a0e18() knlGS: [40866.349356] CS: 0010 DS: ES: CR0: 80050033 [40866.349357] CR2: 55c433bfa8b0 CR3: 000111b80005 CR4: 001606e0 [40866.349358] Call Trace: [40866.349363] ? kernfs_fop_open+0xc2/0x3b0 [40866.349366] kernfs_fop_open+0xc2/0x3b0 [40866.349368] ? kernfs_fop_read+0x1b0/0x1b0 [40866.349372] do_dentry_open+0x143/0x3a0 [40866.349373] vfs_open+0x2d/0x30 [40866.349376] do_last+0x194/0x900 [40866.349392] path_openat+0x8d/0x290 [40866.349394] do_filp_open+0x91/0x100 [40866.349397] ? __alloc_fd+0x46/0x150 [40866.349398] do_sys_open+0x17e/0x290 [40866.349400] __x64_sys_openat+0x20/0x30 [40866.349402] do_syscall_64+0x57/0x190 [40866.349405] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [40866.349407] RIP: 0033:0x7f461a0a3d1b [40866.349409] Code: 25 00 00 41 00 3d 00 00 41 00 74 4b 64 8b 04 25 18 00 00 00 85 c0 75 67 44 89 e2 48 89 ee bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 0f 87 91 00 00 00 48 8b 4c 24 28 64 48 33 0c 25 [40866.349410] RSP: 002b:7ffd5b8a6190 EFLAGS: 0246 ORIG_RAX: 0101 [40866.349411] RAX: ffda RBX: 55c433b7e9b0 RCX: 7f461a0a3d1b [40866.349412] RDX: 0008 RSI: 7ffd5b8a6300 RDI: ff9c [40866.349413] RBP: 7ffd5b8a6300 R08: 000
[Bug 1097519] Re: Wrong driver used for older Broadcom chipsets
>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://bugs.launchpad.net/bugs/1097519 Title: Wrong driver used for older Broadcom chipsets To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1097519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 160311] Re: Resizing windows by grabbing window borders is difficult
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 to the beginning of the description to point to the specific bugs filed for other window managers. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/160311 Title: Resizing windows by grabbing window borders is difficult To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/160311/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 851499] Re: gedit crashed with SIGSEGV in g_closure_invoke()
*** 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 with SIGSEGV in g_closure_invoke() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/851499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 849225] Re: gedit crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()
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_widget.configure_widget() File "/usr/lib/gedit/plugins/pythonconsole/config.py", line 49, in configure_widget self._settings.get_string(self.CONSOLE_KEY_COMMAND_COLOR)) File "/usr/lib/gedit/plugins/pythonconsole/config.py", line 61, in set_colorbutton_color parsed, color = Gdk.color_parse(value) TypeError: 'Color' object is not iterable Segmentation fault -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/849225 Title: gedit crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/849225/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 834571] Re: [dash] Apps lens shows no result by default
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 fiddling. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/834571 Title: [dash] Apps lens shows no result by default To manage notifications about this bug go to: https://bugs.launchpad.net/libunity/+bug/834571/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 971018] Re: Auto-hide Unity Launcher will not reveal when mouse pushed to left side in VirtualBox or VMware
** 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 is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/971018 Title: Auto-hide Unity Launcher will not reveal when mouse pushed to left side in VirtualBox or VMware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/971018/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 905603] [NEW] Crash installing Precise alpha1 on VMWare Player 8.0.1
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-0ubuntu1 Architecture: amd64 CasperVersion: 1.292 Date: Fri Dec 16 22:16:24 2011 LiveMediaBuild: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (2029.1) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise ubiquity-2.9.5 -- 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/+source/ubiquity/+bug/905603/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 905603] Re: Crash installing Precise alpha1 on VMWare Player 8.0.1
-- 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/+source/ubiquity/+bug/905603/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 711650] Re: package grub-pc 1.98-1ubuntu10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 137
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-mkconfig -o /boot/grub/grub.cfg 2.6.32-45-generic /boot/vmlinuz-2.6.32-45-generic /bin/sh -e /etc/grub.d/30_os-prober /bin/sh /usr/bin/os-prober /bin/sh /usr/lib/os-probes/init/10filesystems modprobe xfs I manually tried "modprobe" on all the filesystem types listed in /usr/lib/os-probes/init/10filesystems, and only "modprobe xfs" hangs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/711650 Title: package grub-pc 1.98-1ubuntu10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 137 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/711650/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 711650] Re: package grub-pc 1.98-1ubuntu10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 137
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 received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/711650 Title: package grub-pc 1.98-1ubuntu10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 137 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/711650/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 864442] [NEW] bcmwl-kernel-source 5.100.82.38 bdcom-0ubuntu4: bcmwl kernel module failed to build
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 i686 ApportVersion: 1.23-0ubuntu1 Architecture: i386 DKMSKernelVersion: 3.0.0-11-generic Date: Sat Oct 1 22:53:55 2011 DuplicateSignature: DKMS make.log for bcmwl-5.100.82.38+bdcom for kernel 3.0.0-11-generic (i686) make: Entering directory `/usr/src/linux-headers-3.0.0-11-generic' make: Makefile: No such file or directory make: *** No rule to make target `Makefile'. Stop. make: Leaving directory `/usr/src/linux-headers-3.0.0-11-generic' InstallationMedia: Lubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110921.1) PackageVersion: 5.100.82.38+bdcom-0ubuntu4 SourcePackage: bcmwl Title: bcmwl-kernel-source 5.100.82.38+bdcom-0ubuntu4: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: bcmwl (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 oneiric -- 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://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/864442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 864442] Re: bcmwl-kernel-source 5.100.82.38 bdcom-0ubuntu4: bcmwl kernel module failed to build
-- 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://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/864442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 864442] Re: bcmwl-kernel-source 5.100.82.38 bdcom-0ubuntu4: bcmwl kernel module failed to build
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 attempted activation that there were errors, and to look in /var/log/jockey.log. -- 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://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/864442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 864442] Re: bcmwl-kernel-source 5.100.82.38 bdcom-0ubuntu4: bcmwl kernel module failed to build
*** 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 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://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/864442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 851499] Re: gedit crashed with SIGSEGV in g_closure_invoke()
** 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://bugs.launchpad.net/ubuntu/+source/gedit/+bug/851499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1660713] Re: /usr/bin/atril:11:ev_window_run_presentation:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist:g_signal_emit
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:11:ev_window_run_presentation:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist:g_signal_emit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/atril/+bug/1660713/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962791] Re: python3 -m venv installs pip to incorrect path VENV_ROOT/local/bin/pip
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 python3 python3.10 $ ls 39/bin activate activate.csh activate.fish Activate.ps1 pip pip3 pip3.10 pip3.9 python python3 python3.9 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962791 Title: python3 -m venv installs pip to incorrect path VENV_ROOT/local/bin/pip To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.10/+bug/1962791/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962791] Re: python3 -m venv installs pip to incorrect path VENV_ROOT/local/bin/pip
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 *** def _get_preferred_schemes(): *** 262,268 'user': 'osx_framework_user', } ! if 'real_prefix' in sys.__dict__ or 'VIRTUAL_ENV' in os.environ: # virtual environments prefix_scheme = 'posix_prefix' else: --- 262,270 'user': 'osx_framework_user', } ! # https://bugs.launchpad.net/ubuntu/+source/python3.10/+bug/1962791/comments/4 ! if sys.base_prefix != sys.prefix: ! #if 'real_prefix' in sys.__dict__ or 'VIRTUAL_ENV' in os.environ: # virtual environments prefix_scheme = 'posix_prefix' else: -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962791 Title: python3 -m venv installs pip to incorrect path VENV_ROOT/local/bin/pip To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.10/+bug/1962791/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
