[Bug 1939455] Re: Upgrading from 20.0.4-2ubuntu1 to 21.0.3-0ubuntu0.2~20.04.1 breaks vlc video output
For the benefit of others I had a similar problem with Kaffeine 2.0.18 on Lubuntu 20.04.3, no video with DVB-T broadcast and only audio working. The upgrade to 21.0.3 broke a system that was stable for about a year. Also Kaffeine will crash changing channels. Running Kaffeine from command prompt shows unable to decode video messages type messages. Finally tracked down this ticket and down leveling to 20.0.4 solved problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939455 Title: Upgrading from 20.0.4-2ubuntu1 to 21.0.3-0ubuntu0.2~20.04.1 breaks vlc video output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1939455/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779092] Re: [regression] cyclic reboot caused by the amd microcode updater
Thank you Steve, that has resolved the problem. Tony. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779092 Title: [regression] cyclic reboot caused by the amd microcode updater To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amd64-microcode/+bug/1779092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779092] Re: [regression] cyclic reboot caused by the amd microcode updater
FYI. I am hit by this problem too. Updated system in Synaptic on 26th which included Upgrade: amd64-microcode:amd64 (2.20131007.1+really20130710.1, 3.20180524.1~ubuntu0.14.04.1) Had previously installed (2 weeks ago) linux-image- extra-3.13.0-151-generic:amd64 (3.13.0-151.201) Now system hangs with black screen. Running in recovery mode the last two lines are x86: Booting SMP configuration: node #0: CPUs #1 Booting back in 3.13.0-149 works fine. smpboot: CPU0: AMD Athlon(tm) II X4 600e Processor (fam: 10, model: 05, stepping: 02) Gigabyte Technology Co., Ltd. GA-MA785GM-US2H/GA-MA785GM-US2H, BIOS F12a 07/08/2010 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/1779092 Title: [regression] cyclic reboot caused by the amd microcode updater To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amd64-microcode/+bug/1779092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 534070] Re: u3-tool 0.3 fails on cruzer 2GB stick
I pulled my USB stick apart and got the chipset numbers CBM2090. Then I was able to Google a piece of windows software to manage the drive, doesnt appear to have given me a virus :-). I was able to change the drive sizes, format and write to both partions. U3-tool still gives me this error with the new layout:- username@ZZZ:~$ sudo u3-tool -D /dev/sde [sudo] password for username: u3_partition_info() failed: Device reported command failed: status 1 u3_data_partition_info() failed: Device reported command failed: status 1 u3_chip_info() failed: Device reported command failed: status 1 u3_read_device_property() failed for property 0x03: Header of property 0x0003 could not be read. u3_read_device_property() failed for property 0x0C: Header of property 0x000C could not be read. Neither Kingston or Scandisk software work with my USB stick since they only work with there own devices. Tony. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/534070 Title: u3-tool 0.3 fails on cruzer 2GB stick To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/u3-tool/+bug/534070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 534070] Re: u3-tool 0.3 fails on cruzer 2GB stick
Hi, I am having the same or similar problems with Ubuntu 10.04 LTS (32bit). I have a generiac U3 flash drive of unkown make/chipset. Here are the system message when I plug it in and some u3-tool output Jun 11 17:39:19 ZZZ kernel: [ 75.976025] usb 2-5: new high speed USB device using ehci_hcd and address 2 Jun 11 17:39:19 ZZZ kernel: [ 76.109747] usb 2-5: configuration #1 chosen from 1 choice Jun 11 17:39:19 ZZZ kernel: [ 76.139346] Initializing USB Mass Storage driver... Jun 11 17:39:19 ZZZ kernel: [ 76.139513] scsi8 : SCSI emulation for USB Mass Storage devices Jun 11 17:39:19 ZZZ kernel: [ 76.139634] usbcore: registered new interface driver usb-storage Jun 11 17:39:19 ZZZ kernel: [ 76.139637] USB Mass Storage support registered. Jun 11 17:39:24 ZZZ kernel: [ 81.137439] scsi 8:0:0:0: Direct-Access CBM Flash Disk 5.00 PQ: 0 ANSI: 2 Jun 11 17:39:24 ZZZ kernel: [ 81.137801] scsi 8:0:0:1: Direct-Access CBM Flash Disk 5.00 PQ: 0 ANSI: 2 Jun 11 17:39:24 ZZZ kernel: [ 81.138214] sd 8:0:0:0: Attached scsi generic sg5 type 0 Jun 11 17:39:24 ZZZ kernel: [ 81.138328] sd 8:0:0:1: Attached scsi generic sg6 type 0 Jun 11 17:39:24 ZZZ kernel: [ 81.139795] sd 8:0:0:0: [sdd] 123800 512-byte logical blocks: (63.3 MB/60.4 MiB) Jun 11 17:39:24 ZZZ kernel: [ 81.141872] sd 8:0:0:1: [sde] 907880 512-byte logical blocks: (464 MB/443 MiB) Jun 11 17:39:24 ZZZ kernel: [ 81.143129] sd 8:0:0:0: [sdd] Write Protect is on Jun 11 17:39:24 ZZZ kernel: [ 81.143822] sd 8:0:0:1: [sde] Write Protect is off Jun 11 17:39:24 ZZZ kernel: [ 81.146671] sdd: Jun 11 17:39:24 ZZZ kernel: [ 81.147168] sde: sdd1 Jun 11 17:39:24 ZZZ kernel: [ 81.148668] sde1 Jun 11 17:39:24 ZZZ kernel: [ 81.154431] sd 8:0:0:0: [sdd] Attached SCSI removable disk Jun 11 17:39:24 ZZZ kernel: [ 81.154917] sd 8:0:0:1: [sde] Attached SCSI removable disk Jun 11 17:39:25 ZZZ kernel: [ 81.669336] EXT4-fs (sde1): mounted filesystem with ordered data mode username@ZZZ:~$ u3-tool -V u3-tool 0.3 subsystem: sg Copyright (C) 2009 This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. username@ZZZ:~$ mount ... /dev/sde1 on /media/New Volume type ext4 (rw,nosuid,nodev,uhelper=udisks) /dev/sdd1 on /media/DISK_IMG type vfat (ro,nosuid,nodev,uhelper=udisks,uid=1000,gid=1000,shortname=mixed,dmask=0077,utf8=1,flush) username@ZZZ:~$ sudo u3-tool -i /dev/sdd Error opening device: Read-only file system username@ZZZ:~$ sudo u3-tool -i /dev/sde u3_partition_info() failed: Device reported command failed: status 1 username@ZZZ:~$ sudo u3-tool -D /dev/sdd Error opening device: Read-only file system username@ZZZ:~$ sudo u3-tool -D /dev/sde u3_partition_info() failed: Device reported command failed: status 1 u3_data_partition_info() failed: Device reported command failed: status 1 u3_chip_info() failed: Device reported command failed: status 1 u3_read_device_property() failed for property 0x03: Header of property 0x0003 could not be read. u3_read_device_property() failed for property 0x0C: Header of property 0x000C could not be read. username@ZZZ:~$ Any suggestions? Thank you, Tony. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/534070 Title: u3-tool 0.3 fails on cruzer 2GB stick To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/u3-tool/+bug/534070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 534070] Re: u3-tool 0.3 fails on cruzer 2GB stick
ps it is the latest svn, downloaded 1-june-2012 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/534070 Title: u3-tool 0.3 fails on cruzer 2GB stick To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/u3-tool/+bug/534070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 433142] Re: geode driver do not display 1024x600 on (K)UNR Karmic
the below workaround is posted elsewhere (in pieces), but may be useful for those experiencing this bug: I finally came to use it for an old machine (otherwise working karmic perfectly of course) with an old D1751 17 ATT monitor, after lots of research # use 'cvt' to get the modeline below to set for YOUR machine # commands to set the screen to 1024 X 768 with xrandr, only on the machine required xrandr --newmode 1024x768_60.00 63.50 1024 1072 1176 1328 768 771 775 798 -hsync +vsync xrandr --addmode VGA1 1024x768_60.00 xrandr -s 2 # xrandr seems to work around the issue of the 'barebones' xorg.conf -- geode driver do not display 1024x600 on (K)UNR Karmic https://bugs.launchpad.net/bugs/433142 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 293814] Re: denemo crashed with SIGSEGV
comment #5 is probably closer related to bug #3858. Reinstallation NOT specifying JACK now allows me to execute denemo. Under karmic (9.10) denemo 0.8.6 : The behavior is now such that 1) selecting Csound preferences causes crash (reported as a different bug) I use ALSA, not CSound, but merely selecting the wrong 'emulation' should not crash the program, IMHO 2) the Timidity external causes no audio output (still researching it) -- denemo crashed with SIGSEGV https://bugs.launchpad.net/bugs/293814 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 293814] Re: denemo crashed with SIGSEGV
Was editing a simple score as well; My actions: saved the file updated the option to connect to JACK server (ok, I think I use ALSA instead) checked the option to update menus from the Internet behavior now is: the GNU Denemo window-outline now flashes on the screen as if it's going to start, then doesn't from the CLI, it looks like it can't connect to JACK (ok, maybe my fault) the Internet-file-updates and local comparisons seem to go ok, but it doesn't start THX -- denemo crashed with SIGSEGV https://bugs.launchpad.net/bugs/293814 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
