Built a new kernel from the Ubuntu git and applied the patch to intel-
lpss-pci.c and the trackpad works fine again. I hope this gets into
artful very soon.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
What's the current status on this? I updated to artful and expected this
to be fixed but my touchpad no longer works (I'd build a patched 4.10
with the fix on zenial).
Do we still have to build our own kernel on artful? Is there a package
in proposed for artful? I couldn't find one. Is there
Public bug reported:
libvirt is compiled with VirtualBox support turned off by default in
Ubuntu. I grabbed the source with apt-get source libvirt and:
a...@adam-laptop:~/libvirt-0.8.3$ pwd
/home/adam/libvirt-0.8.3
a...@adam-laptop:~/libvirt-0.8.3$ grep vbox debian/rules
--without-vbox
The work around is to unload the intel_ips driver:
$ modprobe -r intel_ips
I put the in /etc/local. Hopefully this gets fixed and I can take
advantage of the driver.
--
Messages log filled with Intel IPS ME failed to update for more than 1s,
likely hung messages
Public bug reported:
libvirt is compiled with VirtualBox support turned off by default in
Ubuntu. I grabbed the source with apt-get source libvirt and:
a...@adam-laptop:~/libvirt-0.8.3$ pwd
/home/adam/libvirt-0.8.3
a...@adam-laptop:~/libvirt-0.8.3$ grep vbox debian/rules
--without-vbox
15 days and no activity on this bug. There's been a couple of kernel
updates but the issue persists:
a...@adam-laptop:~$ uname -a
Linux adam-laptop 2.6.35-22-generic #35-Ubuntu SMP Sat Oct 16 20:36:48 UTC 2010
i686 GNU/Linux
a...@adam-laptop:~$ tail /var/log/messages
Oct 23 21:04:52 adam-laptop
This bug still exists. Tried solutions in comments 65 and 29. Still does
not work. Did a complete removal of gwibber and gwibber-service from
synaptic then did a find . -name *gwibber* and deleted everything on the
machine with gwibber in the name, re-installed gwibber from the software
center,
Public bug reported:
Issue:
Messages log being continuously filled with the following messages:
Oct 11 00:21:18 adam-laptop kernel: [ 3625.690731] intel ips :00:1f.6: ME
failed to update for more than 1s, likely hung
Oct 11 00:21:19 adam-laptop kernel: [ 3626.169839] intel ips :00:1f.6:
Interesting from here:
http://www.mail-archive.com/intel-
g...@lists.freedesktop.org/msg00311.html
+ cur_seqno = (thm_readl(THM_ITV)
ITV_ME_SEQNO_MASK)
+ ITV_ME_SEQNO_SHIFT;
+ if (cur_seqno == last_seqno
+ time_after(jiffies,
*** This bug is a duplicate of bug 522538 ***
https://bugs.launchpad.net/bugs/522538
So I fixed it but killing gwibber and gwibber-service and then
starting gwibber again. Then, after hitting authorize, the oAuth box
came up and it worked. However, I have the something similar happen now
*** This bug is a duplicate of bug 522538 ***
https://bugs.launchpad.net/bugs/522538
This can be closed. I'll address my issues in 522538.
--
Gwibber urllib2.HTTPError: HTTP Error 401: Unauthorized on attempt to add
Twitter account
https://bugs.launchpad.net/bugs/640881
You received this
Public bug reported:
Binary package hint: gwibber
Issue:
- Cannot add Twitter account to Gwibber
- Clicking the Authorize button to Oauth Gwibber results in the following
traceback at the console:
Traceback (most recent call last):
File
As a follow-on: yes, I can add other accounts without issue.
--
Gwibber urllib2.HTTPError: HTTP Error 401: Unauthorized on attempt to add
Twitter account
https://bugs.launchpad.net/bugs/640881
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I was able to get plymouth working via:
$ sudo update-alternatives --auto default.plymouth
$ sudo update-initramfs -u
Works fine now. I wonder if this was just an issue because I had
originally installed on RC1? I have a machine that should be well
supported; Dell Vostro v13 with Intel Graphics.
Public bug reported:
Binary package hint: plymouth
Description:
On boot no Plymouth graphical splash screen is displayed. After BIOS the screen
stays black, then powers off, then powers back on, then text is displayed (at
native resolution indicating KMS is working), and then we fade smoothly
BOOT_IMAGE=/boot/vmlinuz-2.6.32-21-generic
root=UUID=dec89f2a-d547-4c47-a600-e54cbd78b54c ro vga=792 splash quiet
splash
--
No plymouth graphical boot on Intel GPU
https://bugs.launchpad.net/bugs/571678
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Thanks for the quick attention on this! Very impressive.
a...@zylog-vostro:~$ zcat /boot/initrd.img-$(uname -r) | cpio -t | grep plymouth
47145 blocks
I was surprised that it wasn't in the output so I decided to double
check:
a...@zylog-vostro:~$ zcat /boot/initrd.img-$(uname -r) | cpio -t |
17 matches
Mail list logo