Doesn't work for me with limtp 1.1.4.
Listing raw device(s)
Device 0 (VID=04e8 and PID=6860) is a Samsung GT
P7310/P7510/N7000/I9070/I9100/I9300 Galaxy Tab 7.7/10.1/S2/S3/Nexus/Note/Y.
Found 1 device(s):
Samsung: GT P7310/P7510/N7000/I9070/I9100/I9300 Galaxy Tab
7.7/10.1/S2/S3/Nexus/Note/Y
Have this issue with K400 keyboard (russian)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/995715
Title:
X defaulting keyboard locale to US at login after upgrading
distribution if a Logitech Unif
Same problem on lucid lynx alpha2.
Motherboard ASRock P55 Pro, which has JMB363 PCIe. If it's turned on I have:
$ dmesg | grep ata2
[0.852604] ata2: SATA max UDMA/133 abar m8...@0xf7ffe000 port 0xf7ffe180
irq 19
[1.201805] ata2: SATA link down (SStatus 0 SControl 300)
[1.223457] ata2:
Looks like It's a duplicate of #198871
I had the same errors during boot, and occasional hangings. Check my comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/198871/comments/47
--
message error on boot ata8: COMRESET failed (errno=-32)
https://bugs.launchpad.net/bugs/370731
You receiv
just want to add, that I have the same bug under lucid linx alpha2.
my /dev/sdb is sata dvd-drive.
--
error: cannot open `/dev/sdb' while attempting to get disk size - grub2 update
https://bugs.launchpad.net/bugs/425112
You received this bug notification because you are a member of Ubuntu
Bugs, w
Guys, check right bug (fn for Apple Wireless Keyboard) #499013.
It has solution. Works well for Apple Wireless Keyboard [05ac:023a] - the only
difference is product id.
--
macbook3,1 and apple aluminum keyboards fn key does not work
https://bugs.launchpad.net/bugs/162083
You received this bug no
nope, i installed it from repository.
And on nvidia forum, there was post from developer of AWN about same
problem, but looks like that thread was deleted.
And yes - awn from ubuntu repository has same problems in same
environment (last nvidia driver 177.80 with IPP=2)
--
high cpu load cairo-do
same behavior under interpid.
according to this article:
http://sprayfly.com/2008/08/20/broken-thumbnails-in-kflickr-on-ubuntu-hardy-gnome/
it's dependency issue (kdebase-kio-plugins), But it can't be solved under
interpid, cause ubuntu switched to kde4 and doesn't have kdebase-kio-plugins
(any
Doesn't work for me. I don't have any scroll (horiz/vert), but
gsynaptics says that i should.
$ apt-cache policy xserver-xorg-input-synaptics
xserver-xorg-input-synaptics:
Installed: 0.15.2-0ubuntu1
Candidate: 0.15.2-0ubuntu1
Version table:
*** 0.15.2-0ubuntu1 0
500 http://archive.u
touchpad scrolling doesn't work for me at all (gsynaptics says that its turned
on)
I've got this behavior with update, mentioned before.
--
vertical scrolling area moved to extreme right
https://bugs.launchpad.net/bugs/262305
You received this bug notification because you are a member of Ubuntu
Public bug reported:
my system hangs at starting linux-restricted-modules-common during early
boot (S0 stage). If I disable it (chmod -x) system starts well, nvidia
driver works, etc...
I've checked script - it calls lrm-manager --quick on start.
If I run
$lrm-manager
after some work and updati
Leann Ogasawara,
I'd like to inform about positive changes with 2.7.1, but this is not
about uvesafb. I can't find any contact info\mechanism for it. Point me,
please.
--
Switched from vesafb to uvesafb, but uvesafb can't work without v86d
https://bugs.launchpad.net/bugs/246269
You received this
nothing changed with 2.7.1 about uvesafb:
$ dmesg | grep uvesa
[2.712002] uvesafb: Getting VBE info block failed (eax=0x4f00, err=-3)
[2.712002] uvesafb: vbe_init() failed with -22
[2.712002] uvesafb: probe of uvesafb.0 failed with error -22
--
Switched from vesafb to uvesafb, but uve
one more experiment:
after clean boot I see uvesafb as loaded module (lsmod), but it doesn't
work: I have no /sys/bus/platform/drivers/uvesafb/uvesafb.0 and
/sys/class/graphics/fb0, and all terminals have usual text mode (40x25
or like that)
I can reload uvesafb:
$ sudo modprobe -r uvesafb
$ sudo
~$ dmesg | grep vesa
[2.776166] uvesafb: Getting VBE info block failed (eax=0x4f00, err=-3)
[2.776166] uvesafb: vbe_init() failed with -22
[2.776166] uvesafb: probe of uvesafb.0 failed with error -22
on nvidia 8400gs
$ lsmod | grep vesa
uvesafb34660 0
cn
** Attachment added: "DpkgTerminalLog.gz"
http://launchpadlibrarian.net/16537617/DpkgTerminalLog.gz
--
package digikam-kde4 failed to install/upgrade: rewrite
/usr/share/icons/oxygen/128x128/apps/digikam.png, from kde-icons-oxygen
https://bugs.launchpad.net/bugs/254807
You received this bug
Public bug reported:
Binary package hint: digikam-kde4
Package is trying to install icons, which already present in system.
$ apt-cache policy digikam-kde4
digikam-kde4:
Installed: (none)
Candidate: 0.10.0~beta1-0ubuntu1
Version table:
0.10.0~beta1-0ubuntu1 0
500 http://archiv
One more bug with connections to non-working uvesafb
https://bugs.launchpad.net/ubuntu/+source/usplash/+bug/249037
--
Switched from vesafb to uvesafb, but uvesafb can't work without v86d
https://bugs.launchpad.net/bugs/246269
You received this bug notification because you are a member of Ubuntu
B
It looks like these bugs are the same:
https://bugs.launchpad.net/ubuntu/+source/v86d/+bug/189621
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/246269
The problem is about non-working vesa, if it doesn't work correctly
usplash will not too.
--
After upgrade, nothing shows up on screen dur
ok. it should be installed automatically - this is first bug.
I've installed it by hands (apt-get) and it doesn't work for me. this is second
bug.
--
Switched from vesafb to uvesafb, but uvesafb can't work without v86d
https://bugs.launchpad.net/bugs/246269
You received this bug notification bec
Answer for post https://bugs.launchpad.net/ubuntu/+source/linux-
meta/+bug/189621/comments/16 about this bug:
I've tried move uvesafb options from /etc/initramfs-tools/modules to
/etc/modules - same black blank terminal with errors:
~$ dmesg | grep vesa
[2.412814] uvesafb: Getting VBE info bl
my answers are there: https://bugs.launchpad.net/ubuntu/+source
/initramfs-tools/+bug/246269 ,cause this bug (missing v86d) is already
fixed.
--
v86d missing, needed for uvesafb
https://bugs.launchpad.net/bugs/189621
You received this bug notification because you are a member of Ubuntu
Bugs, whi
currently there is v86d, but still it doesn't work
i think that this bug and https://bugs.launchpad.net/ubuntu/+source
/linux-meta/+bug/189621 is the same on current stage (missing v86d was
fixed)
--
Switched from vesafb to uvesafb, but uvesafb can't work without v86d
https://bugs.launchpad.net/
I've tried same line in /etc/initramfs-tools/modules - the same as it was.
I didn't do anything special about uvesafb. This stuff is coming through
updates. I've tried to figure out what's the problem, but you see...
$ cat /etc/initramfs-tools/modules | grep -v "#"
uvesafb mode=1024x768
$ ls -a
$ apt-cache policy v86d
v86d:
Установлен: 0.1.5-1ubuntu2
Кандидат: 0.1.5-1ubuntu2
Таблица версий:
*** 0.1.5-1ubuntu2 0
500 http://archive.ubuntu.com intrepid/main Packages
100 /var/lib/dpkg/status
with unpacked initrd:
$ find . | grep vesa
./lib/modules/2.6.26-4-generic/init
I use default kernel (iterpid):
$ uname -a
Linux astar-laptop 2.6.26-4-generic #1 SMP Mon Jul 14 18:39:53 UTC 2008 i686
GNU/Linux
my config:
$ cat /boot/config-2.6.26-4-generic | grep VESA
CONFIG_FB_UVESA=m
# CONFIG_FB_VESA is not set
after clean start without any "vga=" or "video=":
$ dmesg |gr
I can reply in return for him.
1. with current interpid kernel (2.6.26-4) vesafb isn't possible - it's absent.
It was replaced with uvesafb, which use another command (according to documents)
In addition. After system load we can see that uvesafb was loaded (lsmod | grep
uvesafb), but it doesn't
** Changed in: linux-meta (Ubuntu)
Status: New => Invalid
--
unable to build kernel from source
https://bugs.launchpad.net/bugs/237528
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.
since nvidia driver was added to repository - I've tried it again.
In default configuration cairo-dock works well
But if we use
$ nvidia-settings -a InitialPixmapPlacement=2
like nvidia recommends for improving performance, we get very high cpu
load of x-server.
--
high cpu load cairo-dock (in
There is problem with uvesafb, which used in 2.6.26-3 kernel.
Check bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/246269
Maybe this is the same bug.
--
v86d missing, needed for uvesafb
https://bugs.launchpad.net/bugs/189621
You received this bug notification because you are a member of
Public bug reported:
Binary package hint: linux-image-2.6.26-3-generic
After grub selection there is no any output to screen till gdm start.
This happens if VESA mode selected in grub command (vga=792 for example). VGA
modes work well.
This problem exists only in 2.6.26-3 kernel.
As I can see k
Public bug reported:
Binary package hint: cairo-dock
cairo-dock is unusable, cause of very high cpu load.
It's very slow.
I've checked last version (1.6.0.2) from developer's repository
(http://repository.cairo-dock.org/ubuntu/) - same problem.
I used it before with ubuntu hardy without any pro
Public bug reported:
Binary package hint: linux-restricted-modules-2.6.26-2-generic
Unable to start nvidia module and as result unable to use nvidia driver
for xorg.
I have all needed packages installed:
$ dpkg -l | grep nvidia
ii nvidia-glx-new169.12+2.6.24.12-16.34
Hmm...
OK. It looks like "well-known" bug, introduced by gcc-4.3 for 2.4.24 kernels
After changing gcc symlinks directly from 4.3 to 4.2 (/usr/bin/gcc and stuff)
build successfully finished (setting CC, HOSTCC, HOSTCXX doesn't help me).
Is it time to close this bug? (till ubuntu switch to 2.6.25
34 matches
Mail list logo
