[Bug 763485] Re: unable to configure two and three finger tapping
Didn't make it clear, but two finger tap and two finger scroll work perfectly. Although ppl say three finger tap moves windows, I just dont see anything happen when three finger tapping. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/763485 Title: unable to configure two and three finger tapping To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/763485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 763485] Re: unable to configure two and three finger tapping
Same problem. Three finger tap not working on 11.10 on HP dm1z with either xserver-xorg-input-synaptics_1.3.99 or with xserver-xorg-input- synaptics_1.4.1-1ubuntu2+clkpad2_amd64.deb which I got from a ppa. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/763485 Title: unable to configure two and three finger tapping To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/763485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 360975] Re: Please add nf_conntrack_pptp and nf_conntrack_netbios_ns to IPT_MODULES
I have fumbled around with this issue for HOURS until I came across this by accident reading through a 2 year old mailing list. This actually isn´t only a problem with samba, it renders WINS hostname resolving impossible! I could not ping hostname. I never thought ufw could be causing problems with hostname resolving, since I had opened up ports 137-139 and 445 as I found somewhere, but after trying ALL kinds of stuff like installing winbind, editing nsswitch.conf, smb.conf, etc. I finally got hostname resolving to work (and therefore being able to access windows share using samba by hostname in Nautilus) by adding nf_conntrack_netbios_ns to IPT_MODULES in /etc/default/ufw.Of course, disabling UFW also works. PS: Maybe we could change this bug report´s name? This is impossible to find for people trying to get hostname resolving to work, samba shares browsable by Nautilus, etc. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/360975 Title: Please add nf_conntrack_pptp and nf_conntrack_netbios_ns to IPT_MODULES -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 360975] Re: Please add nf_conntrack_pptp and nf_conntrack_netbios_ns to IPT_MODULES
I have fumbled around with this issue for HOURS until I came across this by accident reading through a 2 year old mailing list. This actually isn´t only a problem with samba, it renders WINS hostname resolving impossible! I could not ping hostname. I never thought ufw could be causing problems with hostname resolving, since I had opened up ports 137-139 and 445 as I found somewhere, but after trying ALL kinds of stuff like installing winbind, editing nsswitch.conf, smb.conf, etc. I finally got hostname resolving to work (and therefore being able to access windows share using samba by hostname in Nautilus) by adding nf_conntrack_netbios_ns to IPT_MODULES in /etc/default/ufw.Of course, disabling UFW also works. PS: Maybe we could change this bug report´s name? This is impossible to find for people trying to get hostname resolving to work, samba shares browsable by Nautilus, etc. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/360975 Title: Please add nf_conntrack_pptp and nf_conntrack_netbios_ns to IPT_MODULES -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 528887] Re: maximus does not give default focus to newly started apps in combination with efl launcher
I have this issue in Lucid 10.04 LTS UNR edition. I am running on an Asus 1005HA. Every time I open a PNG file by double click (invokes Eye of Gnome), the window is not activated, so the title bar keeps saying Nautilus. If I push the close button I close the Nautilus window, just like in commentary #7. However, in my case, this happens EVERY time. Secondly, the Eye Of Gnome window will not automatically maximize about 30% of times. netbook-launcher-efl -V Version: 0.2.6 -- maximus does not give default focus to newly started apps in combination with efl launcher https://bugs.launchpad.net/bugs/528887 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 528887] Re: maximus does not give default focus to newly started apps in combination with efl launcher
Oh, yeah, I only see this behaviour with Eye Of Gnome windows... -- maximus does not give default focus to newly started apps in combination with efl launcher https://bugs.launchpad.net/bugs/528887 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 392122] Re: dim display when idle only dims but doesn't restore the previous value when not idle anymore
I have similar problems.The problems started when I DISABLED dim when idle. Now, independently of whether I have dim when idle enabled or not, the screen dims every 1-2 minutes, and sometimes it does not dim when idle, but dims when I move the mouse I am on a Asus 1005HA. -- dim display when idle only dims but doesn't restore the previous value when not idle anymore https://bugs.launchpad.net/bugs/392122 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 373245] Re: karmic: wakeups kernel core : hrtimer_start_range_ns (tick_sched_timer)
Same thing on a Asus 1005HA. Don´t know enough to say if this bug is the cause but battery life of 4.5 hours versus 7 hours in Win XP is frustrating... I am using 2.6.31-17-generic. -- karmic: wakeups kernel core : hrtimer_start_range_ns (tick_sched_timer) https://bugs.launchpad.net/bugs/373245 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 373245] Re: karmic: wakeups kernel core : hrtimer_start_range_ns (tick_sched_timer)
CnAvg residency P-states (frequencies) C0 (cpu running)(43.6%) 1.60 Ghz 0.0% C00.0ms ( 0.0%) 1333 Mhz 0.0% C1 mwait 0.0ms ( 0.0%) 1067 Mhz 0.0% C2 mwait 1.4ms ( 2.2%) 800 Mhz 100.0% C4 mwait 1.5ms (54.2%) Wakeups-from-idle per second : 372.1interval: 10.0s Power usage (ACPI estimate): 9.1W (1.8 hours) (long term: 10.8W,/1.5h) Top causes for wakeups: 46.7% (314.0) kernel core : hrtimer_start_range_ns (tick_sched_timer) 12.8% ( 86.4) kernel IPI : Rescheduling interrupts 9.8% ( 66.2) interrupt : ath 8.5% ( 57.4) interrupt : PS/2 keyboard/mouse/touchpad 4.3% ( 28.9) interrupt : ahci 3.3% ( 22.5)deluge : hrtimer_start_range_ns (hrtimer_wakeup) ** Changed in: linux (Ubuntu) Status: New = Confirmed -- karmic: wakeups kernel core : hrtimer_start_range_ns (tick_sched_timer) https://bugs.launchpad.net/bugs/373245 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 373245] Re: karmic: wakeups kernel core : hrtimer_start_range_ns (tick_sched_timer)
Removed Ubuntu One, turned on laptop_mode, laptop_mode_tools, got following results (this is while running Firefox and Deluge, just as in the powertop results posted above): CnAvg residency P-states (frequencies) C0 (cpu running)( 7.7%) 1.60 Ghz 0.0% polling 0.0ms ( 0.0%) 1333 Mhz 0.0% C1 mwait 0.0ms ( 0.0%) 1067 Mhz 0.0% C2 mwait 3.5ms ( 3.2%) 800 Mhz 100.0% C4 mwait 2.1ms (89.1%) Wakeups-from-idle per second : 433.1interval: 10.0s Power usage (ACPI estimate): 7.6W (1.9 hours) (long term: 8.6W,/1.7h) Top causes for wakeups: 24.3% ( 92.8) interrupt : ath 21.5% ( 82.1) kernel core : hrtimer_start_range_ns (tick_sched_timer) 13.1% ( 50.0) interrupt : extra timer interrupt 7.2% ( 27.4) kernel IPI : Rescheduling interrupts 6.7% ( 25.7)deluge : hrtimer_start_range_ns (hrtimer_wakeup) 5.3% ( 20.3) deluged : hrtimer_start_range_ns (hrtimer_wakeup) -- karmic: wakeups kernel core : hrtimer_start_range_ns (tick_sched_timer) https://bugs.launchpad.net/bugs/373245 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
