[Bug 1348930] [NEW] Proxytunnel 1.9.0+svn250-3 unable to establish SSL tunnel
Public bug reported: Upon upgrading to 14.04 from 12.04, proxytunnel stopped working for me: $ proxytunnel -E -p xxx.xxx.xxx.xxx:443 -d 127.0.0.1:22 Via xxx.xxx.xxx.xxx:443 -> 127.0.0.1:22 analyze_HTTP: readline failed: Connection closed by remote host However, a Debian Wheezy box on the same LAN as my Ubuntu one can connect successfully. My currently workaround is to install the Wheezy package (version given as 1.9.0-5) on 14.04, and that works. Both client architectures are amd64. The server is Apache 2.2.22-13+deb7u3 on Debian Wheezy i386 with the mod-proxy-connect patch (the only modification), self-compiled via "the Debian way". A tcpdump -vvv of a *failed* connection (Ubuntu package 1.9.0-svn250-3) is attached. ** Affects: proxytunnel (Ubuntu) Importance: Undecided Status: New ** Attachment added: "proxytunnel-tcpdump.txt" https://bugs.launchpad.net/bugs/1348930/+attachment/4163290/+files/proxytunnel-tcpdump.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1348930 Title: Proxytunnel 1.9.0+svn250-3 unable to establish SSL tunnel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/proxytunnel/+bug/1348930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1348930] Re: Proxytunnel 1.9.0+svn250-3 unable to establish SSL tunnel
** Description changed: Upon upgrading to 14.04 from 12.04, proxytunnel stopped working for me: $ proxytunnel -E -p xxx.xxx.xxx.xxx:443 -d 127.0.0.1:22 Via xxx.xxx.xxx.xxx:443 -> 127.0.0.1:22 analyze_HTTP: readline failed: Connection closed by remote host - However, a Debian Wheezy box on the same LAN can connect successfully. - My currently workaround is to install the Wheezy package (version given - as 1.9.0-5) on 14.04 , and that works. Both client architectures are - amd64. + However, a Debian Wheezy box on the same LAN as my Ubuntu one can + connect successfully. My currently workaround is to install the Wheezy + package (version given as 1.9.0-5) on 14.04, and that works. Both client + architectures are amd64. The server is Apache 2.2.22-13+deb7u3 on Debian Wheezy i386 with the mod-proxy-connect patch (the only modification), self-compiled via "the Debian way". A tcpdump -vvv of a *failed* connection (Ubuntu package 1.9.0-svn250-3) is attached. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1348930 Title: Proxytunnel 1.9.0+svn250-3 unable to establish SSL tunnel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/proxytunnel/+bug/1348930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 996245] Re: [Gigabyte MB: GA-Z77X-UD5H-WB, ALC898] No sound from headphone/line-out jacks
Hi Raül - I'm considering getting the GA-Z77X-UD5H. Can you or anyone else confirm that the headphone outputs (front and rear) all work when using the official Realtek drivers? Do you know which revision of the mobo you have? Apparently, an earlier version had pale blue capacitors and a gap between the memory slots: http://cdn.overclock.net/3/3b/3b4d8b1c_attachment.jpeg The later revision had purple capacitors and no gap: http://cdn.overclock.net/7/7f/7fa1702e_attachment.jpeg It'd be good to know if the updated Realtek driver fixes this issue with both variants of motherboard. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/996245 Title: [Gigabyte MB: GA-Z77X-UD5H-WB, ALC898] No sound from headphone/line- out jacks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/996245/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 996245] Re: [Gigabyte MB: GA-Z77X-UD5H-WB, ALC898] No sound from headphone/line-out jacks
Hi Ivaylo I've gone ahead and bought the GA-Z77X-UD5H (from Amazon UK). I've got the later version (RAM slots equally spaced, purple capacitors and Nvidia SLI and ATI Crossfire logos are near the PCIe slots instead of next to the CPU socket. I'll try using the standard ALSA drivers first, but if I can't get the sound to work properly I'll give the official Realtek drivers a go. Have you tried the Realtek drivers? It will take me a couple of weeks or so to build my new computer and test the drivers and I'll post the results here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/996245 Title: [Gigabyte MB: GA-Z77X-UD5H-WB, ALC898] No sound from headphone/line- out jacks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/996245/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 996245] Re: [Gigabyte MB: GA-Z77X-UD5H-WB, ALC898] No sound from headphone/line-out jacks
I should state that I'm using the non-wifi version of this board. Whether this has any influence on the problem, I don't know. But at least the newer revision of the GA-Z77X-UD5H works with the ALSA drivers - which is no consolation to those of you with other versions/variants of this board... Tested with Ubuntu 12.10 and the default configuration. Rear green line out and front panel headphone sockets work. Sound quality is good. SuSE 12.2 also has no problems. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/996245 Title: [Gigabyte MB: GA-Z77X-UD5H-WB, ALC898] No sound from headphone/line- out jacks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/996245/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1032456] [NEW] Canon i560 prints half a page after 20120801 upgrade to v1.5.3-0ubuntu2
Public bug reported: My Canon i560 was working fine until the update two days ago. Now it fails every single job, printing half a page and then ejecting the page when a USB reset is issued. Same printer works fine when printing through Windows in Virtualbox with USB passthrough. Summary: the USB backend "improvements" have rendered my printer useless with CUPS. Unloading the usblp module makes no difference - the USB reset is what aborts the print job. [ 224.008042] usb 3-1: reset full-speed USB device number 3 using uhci_hcd [ 224.161701] usblp0: USB Bidirectional printer dev 3 if 0 alt 0 proto 2 vid 0x04A9 pid 0x108 Kubuntu 12.04 *** dpkg -l "*cups*"|grep ii ii bluez-cups 4.98-2ubuntu7 Bluetooth printer driver for CUPS ii cups1.5.3-0ubuntu2 Common UNIX Printing System(tm) - server ii cups-bsd1.5.3-0ubuntu2 Common UNIX Printing System(tm) - BSD commands ii cups-client 1.5.3-0ubuntu2 Common UNIX Printing System(tm) - client programs (SysV) ii cups-common 1.5.3-0ubuntu2 Common UNIX Printing System(tm) - common files ii cups-filters 1.0.18-0ubuntu0.1OpenPrinting CUPS Filters ii cups-ppdc 1.5.3-0ubuntu2 Common UNIX Printing System(tm) - PPD manipulation utilities ii ghostscript-cups 9.05~dfsg-0ubuntu4.1 interpreter for the PostScript language and for PDF - CUPS filters ii libcups21.5.3-0ubuntu2 Common UNIX Printing System(tm) - Core library ii libcupscgi1 1.5.3-0ubuntu2 Common UNIX Printing System(tm) - CGI library ii libcupsdriver1 1.5.3-0ubuntu2 Common UNIX Printing System(tm) - Driver library ii libcupsfilters1 1.0.18-0ubuntu0.1OpenPrinting CUPS Filters - Shared library ii libcupsimage2 1.5.3-0ubuntu2 Common UNIX Printing System(tm) - Raster image library ii libcupsmime11.5.3-0ubuntu2 Common UNIX Printing System(tm) - MIME library ii libcupsppdc11.5.3-0ubuntu2 Common UNIX Printing System(tm) - PPD manipulation library ii printer-driver-hpcups 3.12.2-1ubuntu3.1HP Linux Printing and Imaging - CUPS Raster driver (hpcups) ii python-cups 1.9.61-0ubuntu2 Python bindings for CUPS ii python-cupshelpers 1.3.8+20120201-0ubuntu8.1Python modules for printer configuration with CUPS ** ** Affects: cups (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1032456 Title: Canon i560 prints half a page after 20120801 upgrade to v1.5.3-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1032456/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1032456] Re: Canon inkjets (and some other printers) print only half of the last page after 20120801 upgrade to v1.5.3-0ubuntu2
Just another confirmation: my i560 is working perfectly again. Thank you for your work, we appreciate it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1032456 Title: Canon inkjets (and some other printers) print only half of the last page after 20120801 upgrade to v1.5.3-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1032456/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1032456] Re: Canon inkjets (and some other printers) print only half of the last page after 20120801 upgrade to v1.5.3-0ubuntu2
Another test: Canon i560 still working good. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1032456 Title: Canon inkjets (and some other printers) print only half of the last page after 20120801 upgrade to v1.5.3-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1032456/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 784335] Re: Heavy network utilization with r8169 leads to kernel panic
I have been plagued by this too: the kernel's r8169 driver would panic with machine-check-exceptions after about 300KB of transfer, while the Realtek r8168 driver would similarly panic after ~4GB. I'm having good luck so far after adding "nolapic" to my kernel command line, to disable the local APIC. This has no negative side-effects on an MSI MS-1057 notebook (945G/ICH7-M chipset). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/784335 Title: Heavy network utilization with r8169 leads to kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/784335/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 784335] Re: Heavy network utilization with r8169 leads to kernel panic
"nolapic_timer" is the best kernel parameter. It enables SMP, but still stops the MCE panics, "softirq_pending", etc. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/784335 Title: Heavy network utilization with r8169 leads to kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/784335/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 784335] Re: Heavy network utilization with r8169 leads to kernel panic
Subjectively, the system chokes more under load (unresponsive to local
input, etc). nolapic_timer is not a complete fix: I can reproducibly
oops my machine ("transmit queue 0 timed out") in less than a second,
just by using iperf, even with nolapic_timer.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/784335
Title:
Heavy network utilization with r8169 leads to kernel panic
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/784335/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1745694] Re: System will not start after the upgrade of the kernel
Yes. On Thu, Feb 8, 2018 at 9:04 AM, Joseph Salisbury < joseph.salisb...@canonical.com> wrote: > Does this bug go away if you boot back into the prior kernel version? > > ** Changed in: linux (Ubuntu) >Importance: Undecided => High > > ** Tags added: kernel-da-key > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1745694 > > Title: > System will not start after the upgrade of the kernel > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > Ubuntu 16.04 LTS (32 bit kernel) > > After software updates the system will not boot with the new kernel. > > Expected the system to start with the new kernel, end up with a purple > screen with nothing on it. > > ProblemType: Bug > DistroRelease: Ubuntu 16.04 > Package: ubuntu-release-upgrader-core 1:16.04.23 > ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 > Uname: Linux 4.10.0-28-generic i686 > NonfreeKernelModules: wl > ApportVersion: 2.20.1-0ubuntu2.15 > Architecture: i386 > CrashDB: ubuntu > CurrentDesktop: Unity > Date: Fri Jan 26 15:00:52 2018 > InstallationDate: Installed on 2018-01-26 (0 days ago) > InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 > (20170801) > PackageArchitecture: all > SourcePackage: ubuntu-release-upgrader > Symptom: dist-upgrade > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/ > 1745694/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1745694 Title: System will not start after the upgrade of the kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745694/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1745694] [NEW] System will not start after the upgrade of the kernel
Public bug reported: Ubuntu 16.04 LTS (32 bit kernel) After software updates the system will not boot with the new kernel. Expected the system to start with the new kernel, end up with a purple screen with nothing on it. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:16.04.23 ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-28-generic i686 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.15 Architecture: i386 CrashDB: ubuntu CurrentDesktop: Unity Date: Fri Jan 26 15:00:52 2018 InstallationDate: Installed on 2018-01-26 (0 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug dist-upgrade i386 xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1745694 Title: System will not start after the upgrade of the kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1745694/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 552214] Re: No mouse cursor after resuming from suspend during the graphical login prompt.
Same here, no cursor displayed although interface reacts to mouse movements. Switching to VT then back to X makes it appear. Thinkpad T42, no GDM at all (running Xmonad from startx) lspci : 00:00.0 Host bridge: Intel Corporation 82855PM Processor to I/O Controller (rev 03) 00:01.0 PCI bridge: Intel Corporation 82855PM Processor to AGP Controller (rev 03) 00:1d.0 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 01) 00:1d.1 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 01) 00:1d.2 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 01) 00:1d.7 USB Controller: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller (rev 01) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 81) 00:1f.0 ISA bridge: Intel Corporation 82801DBM (ICH4-M) LPC Interface Bridge (rev 01) 00:1f.1 IDE interface: Intel Corporation 82801DBM (ICH4-M) IDE Controller (rev 01) 00:1f.3 SMBus: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) SMBus Controller (rev 01) 00:1f.5 Multimedia audio controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 01) 00:1f.6 Modem: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Modem Controller (rev 01) 01:00.0 VGA compatible controller: ATI Technologies Inc RV350 [Mobility Radeon 9600 M10] 02:00.0 CardBus bridge: Texas Instruments PCI4520 PC card Cardbus Controller (rev 01) 02:00.1 CardBus bridge: Texas Instruments PCI4520 PC card Cardbus Controller (rev 01) 02:01.0 Ethernet controller: Intel Corporation 82540EP Gigabit Ethernet Controller (Mobile) (rev 03) 02:02.0 Network controller: Intel Corporation PRO/Wireless 2200BG [Calexico2] Network Connection (rev 05) -- No mouse cursor after resuming from suspend during the graphical login prompt. https://bugs.launchpad.net/bugs/552214 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 67468] Re: Promise TX4310 FakeRaid Controller without raid 5 functionality
Ok, so I figured out that dm-raid4-5 is now in Intrepid, which would explain why patching with older code would produce those errors. But I still have this error identifying /dev/sdb-e (sda is a separate 40GB boot drive that works just fine). I thought maybe there is a newer dmraid than in the current Intrepid 8.10, which is 1.0.0-rc14. On the debian distribution site, there is dmraid 1.0.0-rc15, which I installed, but still no improvement. -- Promise TX4310 FakeRaid Controller without raid 5 functionality https://bugs.launchpad.net/bugs/67468 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 67468] Re: Promise TX4310 FakeRaid Controller without raid 5 functionality
I submitted this as a bug report to debian for module dmraid. -- Promise TX4310 FakeRaid Controller without raid 5 functionality https://bugs.launchpad.net/bugs/67468 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 67468] Re: Promise TX4310 FakeRaid Controller without raid 5 functionality
Bug was closed in debian - I opened a bug report for Ubuntu 8.10. Bug #367665. https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/367665 -- Promise TX4310 FakeRaid Controller without raid 5 functionality https://bugs.launchpad.net/bugs/67468 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 367665] Re: dmraid does not correctly identify disks under Promise Fasttrak TX4310
This seems to have been around since 2006 (2.6.17). I found a near identical description in Bug #67468 - unfortunately, the reporter never responded to the request to test with Intrepid 8.10 so it was closed. -- dmraid does not correctly identify disks under Promise Fasttrak TX4310 https://bugs.launchpad.net/bugs/367665 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 367665] [NEW] dmraid does not correctly identify disks under Promise Fasttrak TX4310
Public bug reported: Binary package hint: dmraid I am running Ubuntu 8.10 (kernel 2.6.27-11-generic) In trying to solve this I loaded the latest dmraid in testing: Version: 1.0.0.rc15-6 Using Promise Fasttrak TX4310 with 4 Seagate SATA 1.5TB drives ST31500341AS. Booting from separate 40GB ATA disk (sda) without problem. Unable to run dmraid as follows: # dmraid -s ERROR: pdc: identifying /dev/sde, magic_0: 0x2380414/0xab0409, magic_1: 0x2380414/0x0, total_disks: 0 ERROR: pdc: identifying /dev/sdd, magic_0: 0x2380414/0xaa0409, magic_1: 0x2380414/0x0, total_disks: 0 ERROR: pdc: identifying /dev/sdc, magic_0: 0x2370414/0xa90409, magic_1: 0x2370414/0x0, total_disks: 0 ERROR: pdc: identifying /dev/sdb, magic_0: 0x2370414/0xa80409, magic_1: 0x2370414/0x0, total_disks: 0 no raid disks This occurs with any dmraid command that attempts to access the disks (-tay or -r) Vol_id shows the following: # vol_id /dev/sdb ID_FS_USAGE=raid ID_FS_TYPE=promise_fasttrack_raid_member ID_FS_VERSION= ID_FS_UUID= ID_FS_UUID_ENC= ID_FS_LABEL= ID_FS_LABEL_ENC= ID_FS_LABEL_SAFE= I submitted this to debian as a bug, but they closed it saying it should be filed with Ubuntu first. From the debian bug report utility: --- /proc/partitions: major minor #blocks name 8 0 39082680 sda 8 1 37672393 sda1 8 2 1 sda2 8 51405656 sda5 816 1465138584 sdb 832 1465138584 sdc 848 1465138584 sdd 864 1465138584 sde --- initrd.img-2.6.27-11-generic: 48124 blocks lib/modules/2.6.27-11-generic/kernel/drivers/md/dm-mirror.ko lib/modules/2.6.27-11-generic/kernel/drivers/md/dm-log.ko lib/modules/2.6.27-11-generic/kernel/drivers/md/dm-mod.ko --- /proc/modules: dm_raid4_5 73996 0 - Live 0xde863000 dm_region_hash 19456 1 dm_raid4_5, Live 0xde81c000 dm_mem_cache 12800 1 dm_raid4_5, Live 0xde82d000 dm_message 11008 1 dm_raid4_5, Live 0xde829000 dm_mirror 27008 0 - Live 0xde844000 dm_log 17924 3 dm_raid4_5,dm_region_hash,dm_mirror, Live 0xde823000 dm_mod 63432 3 dm_raid4_5,dm_mirror,dm_log, Live 0xde833000 Versions of packages dmraid depends on: ii dmsetup2:1.02.30-3 The Linux Kernel Device Mapper use ii libc6 2.8~20080505-0ubuntu9 GNU C Library: Shared libraries ii libdmraid1.0.0.rc1 1.0.0.rc15-6 Device-Mapper Software RAID suppor ii libselinux12.0.65-2 SELinux shared libraries ii libsepol1 2.0.32-1 Security Enhanced Linux policy lib ii udev 124-9ubuntu0.2rule-based device node and kernel ** Affects: dmraid (Ubuntu) Importance: Undecided Status: New -- dmraid does not correctly identify disks under Promise Fasttrak TX4310 https://bugs.launchpad.net/bugs/367665 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 67468] Re: Promise TX4310 FakeRaid Controller without raid 5 functionality
I am running Ubuntu 8.10 with kernel 2.6.27-11 and the promise TX4310 controller. I get the same error messages from dmraid: # dmraid -tay ERROR: pdc: identifying /dev/sde, magic_0: 0x2380414/0xab0409, magic_1: 0x2380414/0x0, total_disks: 0 ERROR: pdc: identifying /dev/sdd, magic_0: 0x2380414/0xaa0409, magic_1: 0x2380414/0x0, total_disks: 0 ERROR: pdc: identifying /dev/sdc, magic_0: 0x2370414/0xa90409, magic_1: 0x2370414/0x0, total_disks: 0 ERROR: pdc: identifying /dev/sdb, magic_0: 0x2370414/0xa80409, magic_1: 0x2370414/0x0, total_disks: 0 No RAID disks I started going down the path of the dm-raid45_2.6.27_20081027.patch from Heinz Mauelshagen, but after patching, I could no longer run "modprobe dm-raid4-5" - it would say "dm-raid4-5: disagrees about version of symbol...", then it would say "unknown symbol..." (same one), for several dm_* functions. So I went back to the original kernel to see if I could just get the disks recognized. -- Promise TX4310 FakeRaid Controller without raid 5 functionality https://bugs.launchpad.net/bugs/67468 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 1860659] [NEW] 4.15.0-1053 contains fatal nilfs2 kernel bug
Public bug reported: The Bionic 4.15.0-1053 kernel package contains this nilfs2 bug: https://marc.info/?t=15741385112 and it specifically concerns this nilfs2 commit for 5.3 which was apparently backported: https://marc.info/?l=linux-nilfs&m=157423529924889&w=2 My RPi 2B boots fine from nilfs2 on kernel 4.15.0-1052, but kernel -1053 oopses consistently and reproducibly, with exactly the same "nilfs_segctor_do_construct" pattern as in the above bug report. Reverting to -1052 results in a working, bootable system again. The -1053 changelog mentions: "Bionic update: upstream stable patchset 2019-11-21 (LP: #1853519)" which I suspect is the cause. ** Affects: linux-raspi2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860659 Title: 4.15.0-1053 contains fatal nilfs2 kernel bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1860659/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860659] Re: 4.15.0-1053 contains fatal nilfs2 kernel bug
** Attachment added: "linux-raspi2 4.15.0-1054 (bionic-proposed) boot log.txt" https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1860659/+attachment/5322709/+files/linux-raspi2%204.15.0-1054%20%28bionic-proposed%29%20boot%20log.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860659 Title: 4.15.0-1053 contains fatal nilfs2 kernel bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1860659/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860659] Re: 4.15.0-1053 contains fatal nilfs2 kernel bug
Hi. Yes, I get the same crash with the 4.15.0-1054.58 proposed kernel. Log attached. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860659 Title: 4.15.0-1053 contains fatal nilfs2 kernel bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1860659/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1932328] Re: Thunderbird under Wayland does not correctly close (or manage) windows
I had this problem a few weeks ago (21.04) & changed to x11. Additionally I found it sometimes affected nautilus file windows in the dock in the same way. The dock would show dots for windows that did not exist & then new windows could not be opened & reboot was needed. So its more than just a Thunderbird problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1932328 Title: Thunderbird under Wayland does not correctly close (or manage) windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1932328/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754125] Re: Rhythmbox stays running in the background after quit
This is a confusing bug. It appears that the app has quit, but music still plays & it is not obvious how to do anything about it. I have learned now that you can right click the icon IF you have it in the dock, but why does the icon not show the app running? - without a dot under the icon it looks like the app has correctly quit, but it has not. This is a different behaviour from every other app. Suggestions: Quit the app completely when you click X. or show the dot on the dock icon if the app is still running. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754125 Title: Rhythmbox stays running in the background after quit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1754125/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 213053] Re: Totem is 'uninterruptible'
Just wanted to confirm this is happening in other apps, Pidgin in my case. Pidgin 2.4.1 Kernel 2.6.24.19.21 (latest) Ubuntu 8.04 I closed Pidgin using the right-click menu in the panel. After a bit it hadn't closed and I was presented with a box saying the program couldn't shut down, would I like to "wait" or "force quit". I chose "force quit" and locked the computer. Came back 14 hours later and Pidgin is still running, shows as "uninterruptible" in System Monitor". Tried: kill -9 pid killall pidgin Kill from System Monitor End from System Monitor All have no effect -- Totem is 'uninterruptible' https://bugs.launchpad.net/bugs/213053 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 571038] Re: palimpsest crash with libgdu:ERROR:gdu-pool.c:2369:device_recurse: assertion failed: (depth < 100)
Hello, Just created an account here so I could comment. I just started seeing this bug. Don't know if it will still help, but the output of sudo sfdisk -d Warning: extended partition does not start at a cylinder boundary. DOS and Linux will interpret the contents differently. # partition table of /dev/sda unit: sectors /dev/sda1 : start= 2048, size= 2457600, Id= 7, bootable /dev/sda2 : start= 2459648, size=226342912, Id= 7 /dev/sda3 : start=466890752, size= 21504368, Id= 7 /dev/sda4 : start=228802560, size=238088192, Id= 5 /dev/sda5 : start=228804608, size=233887744, Id=83 /dev/sda6 : start=462696448, size= 4192256, Id=82 This is a ThinkPad with Windows 7. The partitions as I understand them (as shown by Paragon and gparted) are as follows: sda1 is NTFS SYSTEM_DRV 1.1 GiB sda2 is NTFS Windows7_OS 107.9 GiB then an extended partition with a 111.5 GiB ext4 partition and 1.9 GiB swap sda3 is Lenovo_Recovery 10.2 GiB Is the issue that the partitions are numbered out of order as they appear on disk? This seems to be the way the ThinkPad came from the factory, although I have added and modified Linux partitions and I admit I don't fully understand how the partition numbers are generated/stored. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/571038 Title: palimpsest crash with libgdu:ERROR:gdu-pool.c:2369:device_recurse: assertion failed: (depth < 100) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-disk-utility/+bug/571038/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 571038] Re: palimpsest crash with libgdu:ERROR:gdu-pool.c:2369:device_recurse: assertion failed: (depth < 100)
OK, managed to fix it following this advice: http://leisurehours.wordpress.com/2010/03/15/partition-table-entries- are-not-in-disk-order-problem/ That required some repair on the GRUB command line, set root and all that, then got my system to boot into Ubuntu and had to do both update- grub and grub install /dev/sda. I now have this: Warning: extended partition does not start at a cylinder boundary. DOS and Linux will interpret the contents differently. # partition table of /dev/sda unit: sectors /dev/sda1 : start= 2048, size= 2457600, Id= 7, bootable /dev/sda2 : start= 2459648, size=226342912, Id= 7 /dev/sda3 : start=228802560, size=238088192, Id= 5 /dev/sda4 : start=466890752, size= 21504368, Id= 7 /dev/sda5 : start=228804608, size=233887744, Id=83 /dev/sda6 : start=462696448, size= 4192256, Id=82 gparted now shows this as /dev/sda1 ntfs SYSTEM_DRV /dev/sda2 ntfs Windows7_OS /dev/sda3 extended /dev/sda5 ext4 / /dev/sda6 linux-swap /dev/sda4 ntfs Lenovo_Recovery So it seems like the issue was that sda3 started after sda4 and when these were put back in disk order, it works OK. It appears that gparted will leave the partition table in this state under some circumstances if you add/remove partitions (at one point this drive had four partitions under sda4 until I removed some unused partitions). Hope this helps. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/571038 Title: palimpsest crash with libgdu:ERROR:gdu-pool.c:2369:device_recurse: assertion failed: (depth < 100) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-disk-utility/+bug/571038/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
