[Bug 1481360] Re: My screen is shown after lifting lid before it takes me to the locked screen
I have this issue on two different Lenovo laptops (Yoga 13 and Helix) both running 15.10. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1481360 Title: My screen is shown after lifting lid before it takes me to the locked screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1481360/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1419436] Re: tls_socket_read (Decryption has failed.)
After recompiling mutt with openssl instead of gnutls I discovered that openssl was also affected, so I tried another USB ethernet dongle and that seems to have fixed it. At least I can't reproduce the problem with the large IMAP fetch using openssl s_client. I've now blacklisted the module for the onboard ethernet phy_twl4030_usb. Maybe this bug could be reassigned? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1419436 Title: tls_socket_read (Decryption has failed.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnutls26/+bug/1419436/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1419436] Re: tls_socket_read (Decryption has failed.)
Sorry, I spoke too soon, I was just able to reproduce it on the new NIC, but it happens much less often. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1419436 Title: tls_socket_read (Decryption has failed.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnutls26/+bug/1419436/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1227996] Re: [Lenovo IdeaPad Yoga 13] ubuntu doesn't know about Yoga screen rotation keycodes: atkbd serio0: Use 'setkeycodes e03e keycode' to make it known.
I reported a bug similar to this a while ago, and after a firmware upgrade (see below) it was fixed. Recently the stuck keys and the syslog spam about keycode e03e have come back. sudo dmidecode -s bios-version sudo dmidecode -s bios-release-date 66CN55WW 02/28/2013 Linux 3.13.0-35-generic #62-Ubuntu SMP Fri Aug 15 01:58:42 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux As above, it stops when the screen is flipped. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1227996 Title: [Lenovo IdeaPad Yoga 13] ubuntu doesn't know about Yoga screen rotation keycodes: atkbd serio0: Use 'setkeycodes e03e keycode' to make it known. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1227996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1227996] Re: [Lenovo IdeaPad Yoga 13] ubuntu doesn't know about Yoga screen rotation keycodes: atkbd serio0: Use 'setkeycodes e03e keycode' to make it known.
Forgot link to the other bug: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input- evdev/+bug/1238914 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1227996 Title: [Lenovo IdeaPad Yoga 13] ubuntu doesn't know about Yoga screen rotation keycodes: atkbd serio0: Use 'setkeycodes e03e keycode' to make it known. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1227996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1419436] Re: tls_socket_read (Decryption has failed.)
Yes, I realise that now. I've tried on a Raspberry Pi with 2.12.20 (armhf) without problems. What is curious is why it was working before under Ubuntu 12.04. Comparing tag and tag_ptr, I can say that it is in fact the HMAC that differs, and not the padding check. I'll keep debugging. On Mon, Feb 09, 2015 at 06:58:52PM -, Seth Arnold wrote: It appears your patch disables authentication entirely; if I'm correct, a MITM attacker can modify bytes at will and you're unlikely to discover that they have been modified while in transit. I'm sorry that I don't have anything better to recommend; it'd be worth running some stressors on your hardware and seeing if they can run to completion, e.g. kernel compiles or http://kernel.ubuntu.com/~cking /stress-ng/ Thanks -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1419436 Title: tls_socket_read (Decryption has failed.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnutls26/+bug/1419436/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1419436 Title: tls_socket_read (Decryption has failed.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnutls26/+bug/1419436/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1419436] [NEW] tls_socket_read (Decryption has failed.)
Public bug reported: Since moving from Ubunutu 12.04 (armel) to 14.04 (armhf) on a Beagleboard I have a persistent problem using mutt where (especially) larger messages fail to download resulting in the error: tls_socket_read (Decryption has failed.) The failure is reproducable in that I can almost never download messages with attachments larger than 10MB (it will inevitably fail at some point during the transfer). 12.04 (armel) had gnutls26 verison 2.12.14-5ubuntu3.8, and I never had this problem. 14.04 uses 2.12.23-12ubuntu2.1. Strangely enough my amd64 machines which also run 14.04 and 2.12.23-12ubuntu2.1 do not have this problem. In attempting to debug I tried setting GNUTLS_DEBUG_LEVEL=6, which didn't produce any output from libgnutls26. Next I tried forcing mutt to use libgnutls28 (3.2.11-2ubuntu1) with LD_PRELOAD. Then setting GNUTLS_DEBUG_LEVEL=6 and redirecting stderr to a file yields the following log: ... gnutls[4]: REC[0x16cb240]: Expected Packet Application Data(23) gnutls[4]: REC[0x16cb240]: Received Packet Application Data(23) with length: 1395 gnutls[4]: REC[0x16cb240]: Decrypted Packet[4742] Application Data(23) with length: 1371 gnutls[6]: BUF[REC]: Inserted 1371 bytes of Data(23) gnutls[4]: REC[0x16cb240]: SSL 3.3 Application Data packet received. Epoch 0, length: 1395 gnutls[4]: REC[0x16cb240]: Expected Packet Application Data(23) gnutls[4]: REC[0x16cb240]: Received Packet Application Data(23) with length: 1395 gnutls[4]: REC[0x16cb240]: Decrypted Packet[4743] Application Data(23) with length: 1371 gnutls[6]: BUF[REC]: Inserted 1371 bytes of Data(23) gnutls[4]: REC[0x16cb240]: SSL 3.3 Application Data packet received. Epoch 0, length: 1378 gnutls[4]: REC[0x16cb240]: Expected Packet Application Data(23) gnutls[4]: REC[0x16cb240]: Received Packet Application Data(23) with length: 1378 gnutls[4]: REC[0x16cb240]: Decrypted Packet[4744] Application Data(23) with length: 1354 gnutls[6]: BUF[REC]: Inserted 1354 bytes of Data(23) gnutls[4]: REC[0x16cb240]: SSL 3.3 Application Data packet received. Epoch 0, length: 1395 gnutls[4]: REC[0x16cb240]: Expected Packet Application Data(23) gnutls[4]: REC[0x16cb240]: Received Packet Application Data(23) with length: 1395 gnutls[2]: ASSERT: gnutls_cipher.c:951 gnutls[2]: ASSERT: gnutls_cipher.c:199 gnutls[2]: ASSERT: gnutls_record.c:1223 gnutls[1]: Discarded message[4745] due to invalid decryption gnutls[2]: ASSERT: gnutls_record.c:1407 gnutls[2]: ASSERT: gnutls_buffers.c:624 gnutls[4]: REC: Sending Alert[1|0] - Close notify gnutls[4]: REC[0x16cb240]: Preparing Packet Alert(21) with length: 2 and min pad: 0 gnutls[4]: REC[0x16cb240]: Sent Packet[10] Alert(21) in epoch 1 and length: 31 gnutls[2]: ASSERT: gnutls_record.c:1384 gnutls[2]: ASSERT: gnutls_record.c:334 gnutls[4]: REC[0x16cb240]: Start of epoch cleanup gnutls[4]: REC[0x16cb240]: End of epoch cleanup gnutls[4]: REC[0x16cb240]: Epoch #1 freed So this problem (at least on armhf) seems to affect both gnutls26 and gnutls28. ** Affects: gnutls26 (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/1419436 Title: tls_socket_read (Decryption has failed.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnutls26/+bug/1419436/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1238914] Re: Random stuck keys on Lenovo Yoga 13
This problem was fixed (as per the bug in comment #6) by upgrading the firmware of the Yoga to the latest version (66CN55WW). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1238914 Title: Random stuck keys on Lenovo Yoga 13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1238914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1419436] Re: tls_socket_read (Decryption has failed.)
I dug a little deeper and recompiled gnutls28-3.2.11 from sources
provided by apt-get source and commented out the block at
gnutls_cipher.c:951(see snippet below) which caused the first assertion
in the log above. This fixes the problem, that is, I can download
attachments in mutt seemingly without problem.
My question now is, what are the implications of removing this check?
Any idea why this is only happening on armhf?
/* Here there could be a timing leakage in CBC ciphersuites that
* could be exploited if the cost of a successful memcmp is high.
* A constant time memcmp would help there, but it is not easy to maintain
* against compiler optimizations. Currently we rely on the fact that
* a memcmp comparison is negligible over the crypto operations.
*/
// if (unlikely
if (0 unlikely
(memcmp(tag, tag_ptr, tag_size) != 0 || pad_failed != 0)) {
/* HMAC was not the same. */
dummy_wait(params, compressed, pad_failed, pad,
length + preamble_size);
return gnutls_assert_val(GNUTLS_E_DECRYPTION_FAILED);
}
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1419436
Title:
tls_socket_read (Decryption has failed.)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnutls26/+bug/1419436/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1234302] Re: cannot navigate with arrow keys
I noticed this as well. TAB seems to be the way to change tabs now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1234302 Title: cannot navigate with arrow keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/powertop/+bug/1234302/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1216558] Re: [LENOVO 36986CG] suspend/resume failure
l cleared up the reason for case #2 above. This is due to the Intel Rapid Start Technology (IRST) in BIOS. When in sleep mode for a long time (one comment says 3 hours) the Helix will wake up and tell the OS to hibernate. http://forums.lenovo.com/t5/X-Series-Tablet-ThinkPad-Laptops/Helix- shuts-down-while-in-sleep-mode/td-p/1160317 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1216558 Title: [LENOVO 36986CG] suspend/resume failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1216558/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1239990] [NEW] Selecting primary monitor is not intuitive
Public bug reported: Today when I plugged in my external monitor the Activities bar/clock/etc (is there a name for this?) was on the wrong screen. It took me 20 minutes of plugging/unplugging, restarting X, searching and reading forums until I came across this AskUbuntu post [1]. The answer, to drag the black bar to the other display in Settings Displays, had been sitting in front of my eyes all along, but apparently unless you've used a Mac (I haven't) it is unreasonable to assume a user would know to do this. Granted, there is a tooltip that says Drag to change the primary display. but this is only activated once you have already clicked on the tiny black bar. Perhaps a better UI hint would be useful here to say Hey, dumbass, drag that very tiny black bar or something. [1] http://askubuntu.com/questions/113246/permanantly-set-monitor-as- primary ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu43 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Tue Oct 15 10:24:31 2013 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2013-09-27 (17 days ago) InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Alpha amd64 (20130903) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: deja-dup 27.3.1-0ubuntu1 ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1239990 Title: Selecting primary monitor is not intuitive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1239990/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1091464] Re: Unable to chainload Windows 8 with Secure Boot enabled
Same problem with a Lenovo Helix and Ubuntu 13.10. For me, disabling Secure Boot is a workaround. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1091464 Title: Unable to chainload Windows 8 with Secure Boot enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1091464/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1238914] Re: Random stuck keys on Lenovo Yoga 13
Yes, evdev (from /var/log/Xorg.0.log): [17.883] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard' [17.883] (**) AT Translated Set 2 keyboard: always reports core events [17.883] (**) evdev: AT Translated Set 2 keyboard: Device: /dev/input/event3 [17.883] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1 [17.883] (--) evdev: AT Translated Set 2 keyboard: Found keys [17.883] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard [17.883] (**) Option config_info udev:/sys/devices/platform/i8042/serio0/input/input3/event3 [17.883] (II) XINPUT: Adding extended input device AT Translated Set 2 keyboard (type: KEYBOARD, id 11) [17.883] (**) Option xkb_rules evdev [17.883] (**) Option xkb_model pc105 [17.883] (**) Option xkb_layout gb -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1238914 Title: Random stuck keys on Lenovo Yoga 13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1238914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1227996] Re: atkbd serio0: Use 'setkeycodes e03e keycode' to make it known.
I also have a Yoga and have this issue with 13.04 and kernel 3.8.0-30-generic. I use sudo setkeycodes e03e 255 as a workaround to make it stop, but this is obviously does not persist through a reboot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1227996 Title: atkbd serio0: Use 'setkeycodes e03e keycode' to make it known. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1227996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1238914] [NEW] Random stuck keys on Lenovo Yoga 13
Public bug reported: Certain keyboard keys get stuck down seemingly randomly resulting in spurious bursts of key repeats. I have mostly noticed this with the arrow keys, PgUp, PgDn and Delete. I have tried to replicate the behaviour in the console with no luck so I believe this to be specific to xserver. Using xev to debug a bit I can see that upon releasing the key no keyup event is received. The key is not physically stuck. Pressing any key on the keyboard interrupts the keydown repeats. The common scenario is either browsing photos with eog or slides with evince. This can cause data loss because if the move to trash confirmation is disabled in eog you may delete many images without even noticing. A minor annoyance when presenting slides because you suddenly end up at the last slide in the deck, midway through your talk. Description:Ubuntu 13.04 Release:13.04 xserver-xorg-video-intel: Installed: 2:2.21.6-0ubuntu4.1 Candidate: 2:2.21.6-0ubuntu4.1 Version table: *** 2:2.21.6-0ubuntu4.1 0 500 http://ie.archive.ubuntu.com/ubuntu/ raring-updates/main amd64 Packages 100 /var/lib/dpkg/status 2:2.21.6-0ubuntu4 0 500 http://ie.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages ** Affects: xserver-xorg-video-intel (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/1238914 Title: Random stuck keys on Lenovo Yoga 13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1238914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1239004] [NEW] Cannot enter full disk encryption passphrase on Lenovo Helix in tablet mode
Public bug reported: Fresh install of 13.10, selected full disk encryption. The Lenovo Helix turns into a tablet by detaching from the keyboard. If the system is rebooted while you are away from the keyboard (e.g., you leave it at home) you cannot enter the passphrase. I suspect this is or will become a problem for other tablets. I could not find any information about a workaround through searching except for storing a key on a USB stick and modifying initrd to read this at boot. Obviously implementing an onscreen keyboard for the console at boot seems a bit far fetched. Is there any idea for a workaround? Description:Ubuntu Saucy Salamander (development branch) Release:13.10 ** Affects: ubiquity (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/1239004 Title: Cannot enter full disk encryption passphrase on Lenovo Helix in tablet mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1239004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1216558] Re: [LENOVO 36986CG] suspend/resume failure
I am having suspend/resume failures as well with kernel version 3.11. There appears to be two aspects: 1. Keyboard does not work after resume (seemingly random). Reboot required. 2. Suspend does not really suspend, PC remains on and eventually runs out of battery (also random). From my experience, the longer I let it sleep the higher the probability of one of the two (above) happening. For #2, perhaps something is causing the machine to wake up? I am pretty certain nothing touches it and the power button is hard to press even when you really try. uname -a: Linux donn-idi 3.11.0-4-generic #9-Ubuntu SMP Mon Aug 26 15:21:06 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1216558 Title: [LENOVO 36986CG] suspend/resume failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1216558/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1215816] Re: CTRL+ALT+L dont lock screen on Ubuntu 13.10
Installing gnome-screensaver fixed this for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1215816 Title: CTRL+ALT+L dont lock screen on Ubuntu 13.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1215816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 353812] Re: Multiple ATA Exception Emask, NCQ disabled etc during boot
Hi, I am having this issue on an Acer Aspire 1810TZ with a fresh 10.04
install (kernel version 2.6.32-19-generic #28-Ubuntu). Boot is very slow
and dmesg shows it is stuck after mounting the root partition with
messages as described in the original report.
...
[1.452734] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled,
doesn't support DPO or FUA
[1.452925] sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7
[1.516595] sd 0:0:0:0: [sda] Attached SCSI disk
[1.554650] usb 6-2: configuration #1 chosen from 1 choice
[1.772114] ata2: SATA link down (SStatus 0 SControl 300)
[2.108112] ata5: SATA link down (SStatus 0 SControl 300)
[2.444135] ata6: SATA link down (SStatus 0 SControl 300)
[3.272334] EXT4-fs (sda6): mounted filesystem with ordered data mode
[ 33.804129] ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x6 frozen
[ 33.804136] ata1.00: failed command: READ FPDMA QUEUED
[ 33.804146] ata1.00: cmd 60/20:00:3e:7c:96/00:00:06:00:00/40 tag 0 ncq 16384
in
[ 33.804154] res 40/00:08:38:88:17/00:00:24:00:00/40 Emask 0x4
(timeout)
[ 33.804159] ata1.00: status: { DRDY }
[ 33.804166] ata1: hard resetting link
[ 34.288113] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 34.289656] ata1.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device
(Stat=0x51 Err=0x04)
[ 34.289919] ata1.00: ACPI cmd ef/10:01:00:00:00:a0 (SET FEATURES) succeeded
[ 34.290167] ata1.00: ACPI cmd ef/10:02:00:00:00:a0 (SET FEATURES) succeeded
[ 34.290173] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered
out
[ 34.290434] ata1.00: ACPI cmd ef/10:04:00:00:00:a0 (SET FEATURES) succeeded
[ 34.290689] ata1.00: ACPI cmd ef/10:05:00:00:00:a0 (SET FEATURES) rejected
by device (Stat=0x51 Err=0x04)
...
I resolved the problem by changing from AHCI to IDE in the laptop's
BIOS.
--
Multiple ATA Exception Emask, NCQ disabled etc during boot
https://bugs.launchpad.net/bugs/353812
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 121123] Re: maximize/unmaximize doesn't restore window size
*** This bug is a duplicate of bug 137479 *** https://bugs.launchpad.net/bugs/137479 I can confirm this bug on metacity 2.20.0 (Ubuntu Gutsy) on a Lenovo T61 Thinkpad. I've attached the metacity log as requested. It is quite long (~10MB uncompressed), but I stopped it just after I was able to reproduce the bug. In my case, this happens mostly in Firefox and Thunderbird, although I've noticed it with other applications as well. I have a keyboard shortcut mapped to toggle the maximization state of a window, which I use frequently. I've tried to reproduce it but can never get it to happen except by chance. I must add that it is rather annoying. Please re-open this bug. Thank you, Donn ** Attachment added: metacity-18875-debug-log-VA657T.gz http://launchpadlibrarian.net/12585347/metacity-18875-debug-log-VA657T.gz -- maximize/unmaximize doesn't restore window size https://bugs.launchpad.net/bugs/121123 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 118747] Re: [gutsy] VTs unusable
*** This bug is a duplicate of bug 115616 *** https://bugs.launchpad.net/bugs/115616 Hi, I'm also experiencing this problem. It can be worked around by restarting udev. The CPU consumption drops and VTs are usable. It's a bit of a pain to do this for each restart, however. Donn -- [gutsy] VTs unusable https://bugs.launchpad.net/bugs/118747 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
