[Bug 293485] Re: no working driver, problem with hal
@Timo: The bug was filed against a Ubuntu package, which is actually still alive and well, under active development: https://launchpad.net/ubuntu/+source/xserver-xorg-input-penmount/1:1.4.99+git20101202.6658e9ad-0ubuntu2 While Penmount does supply separate linux drivers, this bug had nothing to do with those and everything to do with the Ubuntu package. So what's with the "invalid" status, it should be left at "fix committed" if that solved the issue, but the bug was very much VALID when opened. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/293485 Title: no working driver, problem with hal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-penmount/+bug/293485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 476924] Re: kdm invokes ksplash for no reason
Can someone please explain why that ksplash invocation exists in the first place? I find it odd that nobody says anything... It must have appeared useful to whoever made the modification... In any case, removing it has no ill effects on the 5 computers I tried -- and yes, it was needed on all of those because I do not use the default kdm theme, and ksplash loading before was extremely annoying. If resources are being devoted to the "flicker-free boot experience" with the likes of Plymouth, this trivial fix should be right up there! -- kdm invokes ksplash for no reason https://bugs.launchpad.net/bugs/476924 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdebase-workspace in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 484408] Re: kdm sometimes tries to login without asking for credentials and then stops at the hard disk icon
*** This bug is a duplicate of bug 476924 *** https://bugs.launchpad.net/bugs/476924 I don't think this bug is really a duplicate, it's just more obvious because of bug 476924. This bug implies that after ksplash starts, kdm never actually gets to show a login box (therefore, apparently kdm crashes on the way). If bug 476924 would be solved, this bug would still happen, but people would see a blankc screen instead of ksplash... P.S.: @Hans -- the flickering is really noticeable if the chosen kdm theme is different from the default ksplash theme, otherwise it's hard to spot. -- kdm sometimes tries to login without asking for credentials and then stops at the hard disk icon https://bugs.launchpad.net/bugs/484408 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdebase-workspace in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 481389] [NEW] KDM - "Kubuntu needs boot splash" unnecessary in /etc/kde4/kdm/Xsetup
Public bug reported: Binary package hint: kdebase-workspace Using: Kubuntu, 9.10, Karmic The file /etc/kde4/kdm/Xsetup contains a line claiming that "Kubuntu needs boot splash starting..." followed by an invocation of ksplashx. This produces a flicker of ksplash right before KDM starts, and gives the appearance of a glitch. Commenting out the lines removes the flicker and afterwards KDM and KDE4 proceed loading witho no issues (tested on 3 different setups), therefore whatever purpose the line served seems no longer relevant. Searching the web for this modification yielded no information whatsoever as to why it was added... IMHO it should be removed in subsequent versions of kdebase-workspace. ** Affects: kdebase-workspace (Ubuntu) Importance: Undecided Status: New -- KDM - "Kubuntu needs boot splash" unnecessary in /etc/kde4/kdm/Xsetup https://bugs.launchpad.net/bugs/481389 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 481382] Re: ODS does not properly work in Amarok 2.2.0 with Karmic
** Package changed: amarok (Ubuntu) => kdebase-workspace (Ubuntu) ** Package changed: kdebase-workspace (Ubuntu) => ubuntu ** Package changed: ubuntu => amarok (Ubuntu) -- ODS does not properly work in Amarok 2.2.0 with Karmic https://bugs.launchpad.net/bugs/481382 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to amarok in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 370932] Re: maradns init script silently fails during the boot, but works when run manually
I can confirm this bug happening on Kubuntu 9.04... The logs do not show any strange messages, and in my case they are identical between the "failed" initial start and the subsequent start at the command line. I think the issue is related to intermittent connections -- probably wireless which is started later in the boot, possibly even after login if useing Networkmanager. Can the previous posters confirm they have such a setup? It is true in my case... Any other ideas and debugging info would be welcome. -- maradns init script silently fails during the boot, but works when run manually https://bugs.launchpad.net/bugs/370932 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 353280] Re: Screen flickers with Nvidia drivers
I can confirm this bug with versions <= 180.44 and a GTX 260 card. The flicker is resolved by using the 185.18.14 driver posted in the PPA above and there are no observable downsides to that version. -- Screen flickers with Nvidia drivers https://bugs.launchpad.net/bugs/353280 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 293485] Re: no working driver, problem with hal
I have the same problem with a Gigabyte M912M netbook. The touchscreen is a Penmount version and it is detected by X.Org and working perfectly, however it lacks calibration. There seems to be no calibration tool or other means of configuration available. The manufacturer provides a (new, closed-source) driver but I haven't used it due to the invasive changes it requires: http://www.penmount.com.tw/down_2_1.php Since the device works well as it is, it should be relatively easy to add calibration tools for it, right? Attached 'lsusb -n' output for the device, will also add 'lspci -vvnn' later. ** Attachment added: "penmount-lsusb.txt" http://launchpadlibrarian.net/21724395/penmount-lsusb.txt -- no working driver, problem with hal https://bugs.launchpad.net/bugs/293485 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 293485] Re: no working driver, problem with hal
** Attachment added: "penmount-lspci.txt" http://launchpadlibrarian.net/21724400/penmount-lspci.txt -- no working driver, problem with hal https://bugs.launchpad.net/bugs/293485 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
