[Bug 1011521] Re: package mumble-server-web 1.2.3-2ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Apparently this bug is present in 13.10 (Saucy) as well. Setting up mumble-django (2.9-2) ... dpkg: error processing mumble-django (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: mumble-django E: Sub-process /usr/bin/dpkg returned an error code (1) Other things to note, this program cannot be purged either, it produces another error. I was attempting to do a full removal to see if the error persists on a clean install. Purging configuration files for mumble-django ... * Reloading web server apache2 * dpkg: error processing mumble-django (--purge): subprocess installed post-removal script returned error exit status 128 Errors were encountered while processing: mumble-django E: Sub-process /usr/bin/dpkg returned an error code (1) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1011521 Title: package mumble-server-web 1.2.3-2ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mumble-django/+bug/1011521/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 272247] Re: System freezes during boot, unless I hold a key down
I feel like a bit of an idiot atm, I left firefox open last night and this morning my laptop was overheating. After I gave it a reboot and checked my email someone had messaged me stating that sometime in Karmic the custom DSDT option was removed, I checked my logs and found that it seems to be true. How ironic :/ At this poing I am going to try what Stefan suggests, starting with 2 and going back to 1 if need be. I guess this teaches me a lesson on not being so lazy, I've had my laptop occasionally overheat (randomly) after Karmic and thought something was just working to hard or firefox was being a hog again. I never thought to check wether or not my DSDT was still active, if I had I might have commented on this thread earlier, sorry guys. There are a few bugs I need to look into and report today as well, seeing as how it's my day off from work I think I will do so.. no more lazy. I will comment back when I get an actual result, whenever that will be. -- System freezes during boot, unless I hold a key down https://bugs.launchpad.net/bugs/272247 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 272247] Re: System freezes during boot, unless I hold a key down
It's actually hard to say at this point. The freezing has disappeared quite a while ago, but there is another problem which I still experience, which seems directly related to what caused the freezes in the first place. This seems to be an issue on certain chipsets not handling IRQ's properly. I think the reason there's been no posts on this as of late is because, while the halting issue is gone, the overheating persists without a custom DSDT file which 67GTA was quite helpful in assisting quite a few of us with. I don't think people are aware that the overheating is from the same issue. Perhaps at this point a new bug should be started or this one renamed? I wouldn't consider the custom DSDT files to be a triage because the are not readily available through updates and aren't something an average user can conjure up themselves very easily. I have been using the custom DSDT file 67GTA assisted me with creating since the Intrepid release, and still use it now in Lucid Alpha 3 (10.04). And without it, yes, my laptop still overheats, sometimes to the point where it slows down so much I have to force a shutdown. Good thing I've been keeping my custom file on a thumb-drive. ** Changed in: linux (Ubuntu) Status: Incomplete = New -- System freezes during boot, unless I hold a key down https://bugs.launchpad.net/bugs/272247 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 515132] Re: K3B Panels can't be resized
I can also confirm the newest lucid release as being bugged: $ apt-cache policy k3b k3b: Installed: 1.70.0~beta1+svn1087124-0ubuntu2 Candidate: 1.70.0~beta1+svn1087124-0ubuntu2 Version table: *** 1.70.0~beta1+svn1087124-0ubuntu2 0 500 http://us.archive.ubuntu.com lucid/main Packages 100 /var/lib/dpkg/status Also, I updated my system this morning and gave it a good ole` reboot before posting this to make sure it was still broken and it is. Perhaps the Fix is committed but it seems if it was released it wouldn't still be broken. Or is there something I am missing? Does anyone have the apt- cache policy on the fixed libs so I can check against what I have? -- K3B Panels can't be resized https://bugs.launchpad.net/bugs/515132 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 515132] Re: K3B Panels can't be resized
I suppose I should have waited a bit longer before I posted that update, I guess my repos` took a while longer to update than some people... i was using 4.6.1 at my previous post, but I just ran update check again and 4.6.2 came up. After updating I can confirm that this is indeed fixed! Thanks to those who helped out and especially to those whom fixed it! -- K3B Panels can't be resized https://bugs.launchpad.net/bugs/515132 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to qt4-x11 in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 515132] [NEW] K3B Panels can't be resized
Public bug reported: Binary package hint: k3b Release: Kubuntu 9.10 (KDE 4.4rc2) $ apt-cache policy k3b k3b: Installed: 1.68.0~alpha3-0ubuntu1 Candidate: 1.68.0~alpha3-0ubuntu1 Version table: *** 1.68.0~alpha3-0ubuntu1 0 500 http://us.archive.ubuntu.com karmic/main Packages 100 /var/lib/dpkg/status This is a strange little bug and it happened in RC1 as well. Whenever I try to resize the panels, the minute I release the mouse button they go back to their original place. I tried turning off the lock panels option and I get the same result. The only way I found to get the panels to stay put was to .. trick them I guess. I found if I resized the panel how I wanted, then, while still holding the left mouse button down, right-clicked, then clicked the lock panels button (usually un- checking it in the process), the window would stay put. However, if you tried to resize it normally afterward, it would go back to it's original position (prior to me resizing in the first place). I did come across a threat on the forums asking about this as well so I know it's not just me. http://kubuntuforums.net/forums/index.php?topic=3109211.0 ** Affects: k3b (Ubuntu) Importance: Undecided Status: New -- K3B Panels can't be resized https://bugs.launchpad.net/bugs/515132 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 430654] Re: udev 147 outputs warnings about default rules
IMO, when using a alpha-state release, one should be glad they are only seeing warnings instead of errors. I've had the same warnings as everyone else and so long as my system is operating properly, I don't care about the warnings so long as I know they will be fixed. As for the off-topic usplash conversation, they are replacing usplash with xsplash. Which I found here: http://digitizor.com/2009/09/19/ubuntu-9-10-does- away-with-the-usplash/ -- udev 147 outputs warnings about default rules https://bugs.launchpad.net/bugs/430654 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 430537] Re: keyboard/mouse doesn't respond under X
I am currently in the same situation. I ran an update yesterday (Sept. 15th), and then switched to windows to do a few things. This morning when I woke up, I tried to reboot back into linux to find that the minute I got to the login screen, my mouse and keyboard were frozen. I am going to connect my laptop directly to my router and boot it to console with net support. Maybe there's an update for this. Also, I checked my kern and xorg logs, nothing out of the ordinary. I will try checking .xsession-errors next boot. -- keyboard/mouse doesn't respond under X https://bugs.launchpad.net/bugs/430537 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 430537] Re: keyboard/mouse doesn't respond under X
Well, at this point, it seems as tho X isn't getting the mouse/keyboard info from udev. I'd love to post some logs, but since I can't seem to get into kde to do so, there is not much I can provide. On a more amusing note, everytime I go from recovery mode to normal boot, fsck throws a fit over time miss-matches, believing it to be In the future. So everytime I try to fix something or run more diagnostics, I have to sit through a manual fsck. ** Changed in: xorg (Ubuntu) Status: New = Confirmed -- keyboard/mouse doesn't respond under X https://bugs.launchpad.net/bugs/430537 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 430537] Re: keyboard/mouse doesn't respond under X
Alright... got my linux working just a moment ago. Not sure if it was one of the few updates (one of which being hal), or if it was upstart not being updated, but I do have full kb/mouse again. Apparently upstart and some init-scripts packages were being kept back. Doing an apt-get -f install upstart fixed it, after that running update again installed the rest. Here's what Xorg gave me: ==) ModulePath set to /usr/lib/xorg/modules (II) Cannot locate a core pointer device. (II) Cannot locate a core keyboard device. (II) The server relies on HAL to provide the list of input devices. If no devices become available, reconfigure HAL or disable AllowEmptyInput. If anyone else is having these problems I'd suggest making sure as of right now all packaged are updated, and that upstart isn't being kept back. I noticed this to be an issue with update apps other than synaptic. Synaptic usually resolves problems and fixes them on it's own. I will provide any other information I can if asked. -- keyboard/mouse doesn't respond under X https://bugs.launchpad.net/bugs/430537 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
Re: [Bug 429003] Re: [karmic] Xorg (and anything GLX) crashes on startup
Confirmed fixed here on my end as well, prior to that I had the package versions locked in synaptic. On Tue, Sep 15, 2009 at 10:42 AM, Eric Casteleijn eric.castele...@canonical.com wrote: Brian: No icons, no taskbars, desktop background is there. When I click somewhere the taskbars seem to appear very briefly and then disappear again, so I guess something's crashing. Will investigate more, and file a new bug, if it's not already there. -- [karmic] Xorg (and anything GLX) crashes on startup https://bugs.launchpad.net/bugs/429003 You received this bug notification because you are a direct subscriber of the bug. Status in “eglibc” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-180” package in Ubuntu: Invalid Status in eglibc in Ubuntu Karmic: Fix Released Status in nvidia-graphics-drivers-180 in Ubuntu Karmic: Invalid Bug description: As of after updates at 2009-09-13 ca. 16:00, Xorg and anything using GLX (eg. glxinfo) crashes on startup. The only thing that seems to have been changed then is the upgrade of libc6 to 2.10.1-0ubuntu11. Log of crashing Xorg run is attached. The corresponding gdb backtrace is: $ gdb /usr/bin/Xorg CoreDump ... (gdb) bt #0 0x278da3c0 in ?? () #1 0x00289d8d in *__GI___backtrace (array=0xbfdab960, size=32) at ../sysdeps/i386/backtrace.c:121 #2 0x08133d1b in xorg_backtrace () at ../../os/backtrace.c:39 #3 0x080c7b95 in xf86SigHandler (signo=11) at ../../../../hw/xfree86/common/xf86Events.c:387 #4 signal handler called #5 *__GI_strtol_l_internal (nptr=0xbfdac02d 001 GLX, endptr=0xbfdac028, base=10, group=0, loc=0x0) at strtol_l.c:246 #6 0x001d6667 in *__GI_strtol (nptr=0xbfdac02d 001 GLX, endptr=0xbfdac028, base=10) at strtol.c:110 #7 0x0807355e in RegisterExtensionNames (extEntry=0x8387690) at ../../dix/registry.c:168 #8 0x0809e33a in AddExtension (name=0x635ebc GLX, NumEvents=17, NumErrors=12, MainProc=0x6135f0, SwappedMainProc=0, CloseDownProc=0x613430, MinorOpcodeProc=0x809da10 StandardMinorOpcode) at ../../dix/extension.c:145 #9 0x006132f5 in ?? () from /usr/lib/xorg/modules/extensions//libglx.so #10 0x00635ebc in ?? () from /usr/lib/xorg/modules/extensions//libglx.so #11 0x0011 in ?? () #12 0x000c in ?? () #13 0x006135f0 in ?? () from /usr/lib/xorg/modules/extensions//libglx.so #14 0x00613560 in ?? () from /usr/lib/xorg/modules/extensions//libglx.so #15 0x00613430 in ?? () from /usr/lib/xorg/modules/extensions//libglx.so #16 0x0809da10 in ?? () at ../../dix/extension.c:219 #17 0x080ec7c5 in InitExtensions (argc=4, argv=0xbfdac2d4) at ../../../../mi/miinitext.c:551 #18 0x080722b8 in main (argc=4, argv=0xbfdac2d4, envp=0xbfdac2e8) at ../../dix/main.c:319 Glxinfo backtrace looks like this: $ unset DISPLAY $ gdb glxinfo ... (gdb) run Starting program: /usr/bin/glxinfo Program received signal SIGSEGV, Segmentation fault. *__GI_strtol_l_internal (nptr=0xb57a \t26782\n, endptr=0x0, base=0, group=0, loc=0x0) at strtol_l.c:246 246 strtol_l.c: No such file or directory. in strtol_l.c (gdb) bt #0 *__GI_strtol_l_internal (nptr=0xb57a \t26828\n, endptr=0x0, base=0, group=0, loc=0x0) at strtol_l.c:246 #1 0x0045b6b6 in *__GI___strtol_internal (nptr=0xb57a \t26828\n, endptr=0x0, base=0, group=0) at strtol.c:99 #2 0x006bac15 in ?? () from /usr/lib/libGL.so.1 #3 0xb57a in ?? () #4 0x in ?? () Note that it crashes at a very early stage, not probably even contacting X server yet (since DISPLAY is unset). Packages: ii libc6 2.10.1-0ubuntu11 GNU C Library: Shared libraries ii libc6-dbg 2.10.1-0ubuntu11 GNU C Library: detached debugging symbols ii libc6-dev 2.10.1-0ubuntu11 GNU C Library: Development Libraries and Hea ii libc6-i6862.10.1-0ubuntu11 GNU C Library: Shared libraries [i686 optimi ii libgl1-mesa-glx 7.6.0~git20090817.7c422387-0ubuntu3A free implementation of the OpenGL API -- G ii mesa-utils 7.6.0~git20090817.7c422387-0ubuntu3Miscellaneous Mesa GL utilities ii mesa-utils-dbgsym 7.6.0~git20090817.7c422387-0ubuntu3debug symbols for package mesa-utils ii nvidia-185-kernel-source 185.18.36-0ubuntu2 NVIDIA binary kernel module source ii nvidia-185-libvdpau 185.18.36-0ubuntu2 Video Decode and Presentation API for Unix ii nvidia-glx-185185.18.36-0ubuntu2 NVIDIA binary Xorg driver ii nvidia-settings 180.25-0ubuntu1 Tool of configuring the NVIDIA graphics driv ii rss-glx 0.9.0-2ubuntu3 Really Slick Screensavers
Re: [Bug 272247] Re: System freezes during boot, unless I hold a key down
I've been playing with Karmic for a while now, and so far for me it's boot on and off battery without requiring a key to be pressed down. However, I have noticed it occasionally overheats.. but so far it only seems to overheat if I leave firefox open and close the lid. When I come back after a few hours it's hot and the fan is blowing in it like mad. On Wed, Jun 17, 2009 at 10:27 AM, Perpetual lando...@yahoo.com wrote: @Ing. Forigua So you are saying it is fixed without touching the DSDT file? Did you try booting on battery power? Thanks! -- System freezes during boot, unless I hold a key down https://bugs.launchpad.net/bugs/272247 You received this bug notification because you are a direct subscriber of the bug. Status in The Linux Kernel: Confirmed Status in Ubuntu Release Notes: Confirmed Status in “linux” source package in Ubuntu: Confirmed Status in “usplash” source package in Ubuntu: Invalid Status in linux in Ubuntu Intrepid: Triaged Status in usplash in Ubuntu Intrepid: Invalid Status in “linux” source package in Mandriva: Invalid Bug description: Once the Ubuntu splash screen loads with the progress bar that moves back and forth, it freezes. Holding down any key unfreezes the system, and it continues loading normally, until I release the key, at which point it freezes again. Holding a key down again unfreezes the system again. Pressing Alt+F1 to show the output also freezes, so I know it isn't just the splash screen freezing, but the entire system. Once X loads, it works perfectly fine though, and I don't have to keep holding a key down. Update : This bug happens with 2.6.26 and 2.6.27 kernels with a computer that has Nvidia MCP67 motherboard. A known workaround that sometimes works is to add nolapic to GRUB boot kernel options. acpi=noirq is also known to work. ProblemType: Bug Architecture: amd64 DistroRelease: Ubuntu 8.10 NonfreeKernelModules: wl nvidia Package: usplash 0.5.23 ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: usplash Uname: Linux 2.6.27-3-generic x86_64 -- Possible systems affected include: Nvidia MCP67 Chipset Compaq Presario F700 Compaq Presario F763NR Sony Vaio PCG-GRT-815E - from the Mandriva errata HP Pavilion DV6545eg Notebook - from duplicate HP Pavilion DV6736nr HP Pavilion DV6745us - from a duplicate HP Pavilion DV6620es HP Pavilion DV9610us HP Pavilion DV9700z HP Pavilion DV6915nr HP Pavilion DV9645ed HP G6062ea -- System freezes during boot, unless I hold a key down https://bugs.launchpad.net/bugs/272247 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 380126] Re: [Karmic] Touchpad not recognised correctly, synaptics driver not in use
Conn, I could not find your full Xorg log, you seem to have only posted your grep via mouse. Could you run the following commands that Andreas had suggested to me previously? grep -c Synaptics /var/log/Xorg.0.log lshal | grep -c input.touchpad If the 2 commands produce a number higher than 1, can you then post the information from the following commands? cat /var/log/Xorg.0.log | grep Synaptics lshal | grep input.touchpad PS: Sorry if we hijacked your bug report, I was under the assumption that you did what I did.. which was assume synaptics would be listed as a mouse and therefore be displayed on a grep. Realizing I had no tap- click or scroll, I decided to run a search for it and found this bug report, ran the same command you did, which produced the same results and never even looked at my whole Xorg.0.log file. If you do not have the synaptics driver at all, perhaps myself or some others can help you out. -- [Karmic] Touchpad not recognised correctly, synaptics driver not in use https://bugs.launchpad.net/bugs/380126 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 380126] Re: [Karmic] Touchpad not recognised correctly, synaptics driver not in use
@Conn, If this is the case.. grab my custom fdi file from the previous post and follow the instructions, if everything works as it should you should have tap-clicking and vertical scrolling re-enabled, I also left the 2 finger scrolling active in case anyone wanted both but you can easily tweak out the file to change the values to false/0/whatever. -- [Karmic] Touchpad not recognised correctly, synaptics driver not in use https://bugs.launchpad.net/bugs/380126 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 384493] Re: wi-fi not work in kubuntu 9.10
This may be a duplicate to: https://bugs.launchpad.net/bugs/339313 -- wi-fi not work in kubuntu 9.10 https://bugs.launchpad.net/bugs/384493 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 339313] Re: Kubuntu Jaunty: Cannot Connect To Wireless Network with WEP shared key
Turns out, here in Karmic I've had the same problem in both the plasmoid and knetworkmanager. It continually attempts to connect over and over to no avail. I rather liked the plasmoid, but to fix the problem (as someone else suggested) I did sudo apt-get install wicd, then gave it a reboot. For those of you unfamilar with wicd, right click on the new icon you have in the tray and click connect. Find your network on the list and click the to bring up more options. Click advanced settings and add type WPA (or whatever enc you are using) key in the box at the bottom. Click OK then click Connect. You should be good to go. On a personal note, I am disappointed that I had to resort to this option, however, I am grateful that I had a (simple) second option. Having no nifty plasmoid is better than no wifi at all, my wife is rather tired of seeing my 50ft bright orange cat5 laying about in the living room. :/ -- Kubuntu Jaunty: Cannot Connect To Wireless Network with WEP shared key https://bugs.launchpad.net/bugs/339313 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 384493] Re: wi-fi not work in kubuntu 9.10
Unless/Until someone marks this as a duplicate, I added this post this morning to the other bug thread on how to gain wifi back. Unfortunately you lose knetworkmanager and the plasmoid applet but you should atleast have wifi (which I personally can't live without on my laptop). https://bugs.launchpad.net/ubuntu/karmic/+source/plasma-widget-network- manager/+bug/339313/comments/61 -- wi-fi not work in kubuntu 9.10 https://bugs.launchpad.net/bugs/384493 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 380126] Re: [Karmic] Touchpad not recognised correctly, synaptics driver not in use
To: Andreas Henriksson Unfortunately in my case (and probably others), the synaptics driver doesn't actually seem to be loading. Typing the options listed in that news file doesn't seem to effect the mouse at all. -- [Karmic] Touchpad not recognised correctly, synaptics driver not in use https://bugs.launchpad.net/bugs/380126 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 380126] Re: [Karmic] Touchpad not recognised correctly, synaptics driver not in use
$ grep -c Synaptics /var/log/Xorg.0.log
15
$ lshal | grep -c input.touchpad
1
This is rather odd.. it seems to actually find my touchpad (which is
good in some respects)..
$ cat /var/log/Xorg.0.log | grep Synaptics
(II) config/hal: Adding input device SynPS/2 Synaptics TouchPad
(II) Synaptics touchpad driver version 1.1.0
(II) SynPS/2 Synaptics TouchPad: x-axis range 1472 - 5472
(II) SynPS/2 Synaptics TouchPad: y-axis range 1408 - 4448
(II) SynPS/2 Synaptics TouchPad: pressure range 0 - 255
(II) SynPS/2 Synaptics TouchPad: finger width range 0 - 0
(II) SynPS/2 Synaptics TouchPad: buttons: left right middle double triple
(--) SynPS/2 Synaptics TouchPad: touchpad found
(**) SynPS/2 Synaptics TouchPad: always reports core events
(II) XINPUT: Adding extended input device SynPS/2 Synaptics TouchPad (type:
TOUCHPAD)
(**) SynPS/2 Synaptics TouchPad: (accel) keeping acceleration scheme 1
(**) SynPS/2 Synaptics TouchPad: (accel) filter chain progression: 2.00
(**) SynPS/2 Synaptics TouchPad: (accel) filter stage 0: 20.00 ms
(**) SynPS/2 Synaptics TouchPad: (accel) set acceleration profile 0
(--) SynPS/2 Synaptics TouchPad: touchpad found
$ lshal | grep input.touchpad
info.capabilities = {'input', 'input.touchpad'} (string list)
$ sudo tpconfig -i
Found Synaptics Touchpad.
Firmware: 8.96 (multiple-byte mode).
Sensor type: unknown (0).
Geometry: rectangular/landscape/up.
Packets: absolute, 80 packets per second.
Corner taps disabled; no tap gestures.
Edge motion: none.
Z threshold: 6 of 7.
2 button mode; corner tap is right button click.
... however, as I stated previously.. using those options found in the
news file didn't allow touch clicking, and my scroll is broken too
(there's a designated area on the right of the touchpad for it). It
seems to me, that while it is detecting it, it's not applying the proper
driver for it. Strange thing is, I've never had this issue in any
previous distro of Kubuntu.
--
[Karmic] Touchpad not recognised correctly, synaptics driver not in use
https://bugs.launchpad.net/bugs/380126
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 375422] Re: apparmor fails to load at startup
Can confirm this is still not fixed as of: 2.6.30-8-generic -- apparmor fails to load at startup https://bugs.launchpad.net/bugs/375422 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 384493] Re: wi-fi not work in kubuntu 9.10
knetworkmanager and the plasma widget both seem to be using the same back-end system which doesn't work properly at current. Like I said, follow that link and try using wicd, if it doesn't work for you, your problem might be completely different. I tried both the plasma applet and knetworkmanager. Neither of those would allow me to connect to a secured wireless network, wicd connected just fine. -- wi-fi not work in kubuntu 9.10 https://bugs.launchpad.net/bugs/384493 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 384493] Re: wi-fi not work in kubuntu 9.10
On a secondary note: the plasma widget and knetwork manager worked for me on intrepid, and jaunty.. as well as karmic until i added pre- released and unsupported repositories in order to play with KDE 4.3beta. So it seems to me that the back-end for knetworkmanager and the plasmoid broke in 4.3 beta specifically. -- wi-fi not work in kubuntu 9.10 https://bugs.launchpad.net/bugs/384493 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 380126] Re: [Karmic] Touchpad not recognised correctly, synaptics driver not in use
There is no reason to be rude here. I was not vague at all, i merely made the assumption that you read the file you suggested other people read in regards to re-enabling tap-clicking, which I stated did not work for me. No, I was not aware that it defaults to mac touchpad behavior, but considering I am not using a mac touch pad, I am rather displeased that it's behavior is being forced on me by default. Yes, I am aware that there is no way to detect a painted scrollbar on my touchpad, however, all laptops I've owned have had this painted scrollbar, and up until now that area on the touchpad has worked as a scroller. Granted, mentioning it was not very useful in any respect, but it was first thing in the morning and I decided to mention it, though I did so in parenthesis to suggest it was a personal note. Considering no official has stepped in to decide whether or not this is a bug, or just new behavior we are supposed to accept as the new standard, I am going to continue treating it like a bug. If there is a way to restore behavior, perhaps you could have mentioned it rather that berate me after I pasted the corresponding information you asked me for? I would think that more people are eventually going to notice this behavior and wish to restore it, so sharing that information would be a nice thing to do, especially for those of us, myself included, who weren't aware that the behavior was completely changed. -- [Karmic] Touchpad not recognised correctly, synaptics driver not in use https://bugs.launchpad.net/bugs/380126 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 380126] Re: [Karmic] Touchpad not recognised correctly, synaptics driver not in use
If I have time later I may pop in my Jaunty live CD, I am unsure of what changed between then and now as far as default configurations are concerned.. however.. after poking around in /etc/hal/fdi/policy/ as well as /usr/share/hal/fdi/policy/20thirdpolicy (some sites suggest the default file is in 10osvendor), I managed to come up with a custom FDI file that restored all my synaptics functions back to the way they were. Andreas will probably slap me for this, as I probably should have checked these earlier, and did not. However, the fdi system is fairly new to some people (myself included), so I am going to attach my custom file in the hopes it will help someone else out and prevent them from also being slapped. As I stated though, it is unclear to me whether this change was intended or not. In the case where it was accidental, I suppose it'd still be considered a bug. If it was intended, I am certain this bug report will eventually be closed. At any rate, the attached file is my fdi policy. The quick instructions are; Download to .. wherever. sudo cp 99-x11-synaptics.fdi /etc/hal/fdi/policy/ reboot I added some comments in the file as to what things are, most are fairly self explanatory. Any questions about it can be emailed to me directly through my profile and I can try to help you out. ** Attachment added: My Custom synaptics FDI profile http://launchpadlibrarian.net/27621327/99-x11-synaptics.fdi -- [Karmic] Touchpad not recognised correctly, synaptics driver not in use https://bugs.launchpad.net/bugs/380126 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 378723] Re: Broadcom Wireless BCM4311 (rev 02) not supported in karmic koala
Did you have pre-release repositories enabled in Jaunty before dist- upgrading? I had this same issue when I tried to do a dist-upgrade. I then decided (since my linux install was minimal), to do a full CD install of karmic. My wifi worked absolutely fine, until I enabled pre- release to get KDE 4.3beta to play with. After reboot, my wifi failed to connect.. it would continually try.. but would fail to hold a connection. After checking dmesg I found my logs littered with these: 39255.154157] wlan0: associated [39261.359027] wlan0: disassociated (Reason: 15) [39262.357046] wlan0: associate with AP 00:21:29:6b:74:45 [39262.557061] wlan0: associate with AP 00:21:29:6b:74:45 [39262.758105] wlan0: associate with AP 00:21:29:6b:74:45 [39262.957027] wlan0: association with AP 00:21:29:6b:74:45 timed out [39263.733729] wlan0: authenticate with AP 00:21:29:6b:74:45 [39263.741198] wlan0: authenticate with AP 00:21:29:6b:74:45 [39263.741825] wlan0: authenticated [39263.741828] wlan0: associate with AP 00:21:29:6b:74:45 [39263.747221] wlan0: RX ReassocResp from 00:21:29:6b:74:45 (capab=0x411 status=0 aid=2) [39263.747224] wlan0: associated [39269.955426] wlan0: disassociated (Reason: 15) [39270.952190] wlan0: associate with AP 00:21:29:6b:74:45 [39271.153039] wlan0: associate with AP 00:21:29:6b:74:45 [39271.352043] wlan0: associate with AP 00:21:29:6b:74:45 [39271.552043] wlan0: association with AP 00:21:29:6b:74:45 timed out [39272.330049] wlan0: authenticate with AP 00:21:29:6b:74:45 [39272.337192] wlan0: authenticate with AP 00:21:29:6b:74:45 [39272.339188] wlan0: authenticated [39272.339197] wlan0: associate with AP 00:21:29:6b:74:45 [39272.342799] wlan0: RX ReassocResp from 00:21:29:6b:74:45 (capab=0x411 status=0 aid=2) it would occasionally ask me to re-enter my password for the router.. but still continually fail until I eventually cancelled it out. I am currently using my 50ft lan cable to keep internet connection on my laptop. -- Broadcom Wireless BCM4311 (rev 02) not supported in karmic koala https://bugs.launchpad.net/bugs/378723 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 380126] Re: [Karmic] Touchpad not recognised correctly, synaptics driver not in use
Can confirm same issue on the HP Pavilion dv9610us. No tap-click, no scroll: ~$ cat /var/log/Xorg.0.log | grep -i mouse (==) NVIDIA(0): Silken mouse enabled (II) config/hal: Adding input device Macintosh mouse button emulation (**) Macintosh mouse button emulation: always reports core events (**) Macintosh mouse button emulation: Device: /dev/input/event4 (II) Macintosh mouse button emulation: Found 3 mouse buttons (II) Macintosh mouse button emulation: Found x and y relative axes (II) Macintosh mouse button emulation: Configuring as mouse (**) Macintosh mouse button emulation: YAxisMapping: buttons 4 and 5 (**) Macintosh mouse button emulation: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200 (II) XINPUT: Adding extended input device Macintosh mouse button emulation (type: MOUSE) (**) Macintosh mouse button emulation: (accel) keeping acceleration scheme 1 (**) Macintosh mouse button emulation: (accel) filter chain progression: 2.00 (**) Macintosh mouse button emulation: (accel) filter stage 0: 20.00 ms (**) Macintosh mouse button emulation: (accel) set acceleration profile 0 -- [Karmic] Touchpad not recognised correctly, synaptics driver not in use https://bugs.launchpad.net/bugs/380126 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 339313] Re: Kubuntu Jaunty: Cannot Connect To Wireless Network with WEP shared key
I seem to be having the same general issue, though I cannot get knetworkmanager to function either. It detects my network, and attempts to connect for what seems like.. ever. Ocassionally it will ask for the wpa-personal passkey again, but again fail. I get these few msg's cycling repeatedly in dmesg: [ 135.322382] wlan0: associated [ 137.268022] wlan0: no IPv6 routers present [ 141.540094] wlan0: disassociated (Reason: 15) [ 142.536042] wlan0: associate with AP 00:21:29:6b:74:45 [ 142.738158] wlan0: associate with AP 00:21:29:6b:74:45 [ 142.936767] wlan0: associate with AP 00:21:29:6b:74:45 [ 143.136046] wlan0: association with AP 00:21:29:6b:74:45 timed out [ 143.925484] wlan0: authenticate with AP 00:21:29:6b:74:45 [ 143.927185] wlan0: authenticated [ 143.927196] wlan0: associate with AP 00:21:29:6b:74:45 [ 143.933198] wlan0: authenticate with AP 00:21:29:6b:74:45 [ 143.937925] wlan0: authenticated [ 143.937937] wlan0: associate with AP 00:21:29:6b:74:45 [ 143.942867] wlan0: RX ReassocResp from 00:21:29:6b:74:45 (capab=0x411 status=0 aid=2) [ 143.942878] wlan0: associated [ 150.138976] wlan0: disassociated (Reason: 15) [ 151.137060] wlan0: associate with AP 00:21:29:6b:74:45 [ 151.336041] wlan0: associate with AP 00:21:29:6b:74:45 [ 151.536037] wlan0: associate with AP 00:21:29:6b:74:45 [ 151.737064] wlan0: association with AP 00:21:29:6b:74:45 timed out [ 152.516062] wlan0: authenticate with AP 00:21:29:6b:74:45 [ 152.517619] wlan0: authenticated [ 152.517626] wlan0: associate with AP 00:21:29:6b:74:45 [ 152.520288] wlan0: RX ReassocResp from 00:21:29:6b:74:45 (capab=0x411 status=0 aid=2) -- Kubuntu Jaunty: Cannot Connect To Wireless Network with WEP shared key https://bugs.launchpad.net/bugs/339313 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
Re: [Bug 272247] Re: System freezes during boot, unless I hold a key down
To 67GTA: I noticed on your post in the ubuntu forums you mentioned acpi_osi=Linux. Has this been known to work without the custom DSDT or is that required? The custom DSDT file seems a bit beyond my range of knowledge. :/ This problem is actually really upsetting, I've noticed my laptop being extremely hot lately, even when closed and idle. On Tue, Apr 28, 2009 at 3:27 PM, Ing. Forigua ingeniero.fori...@gmail.comwrote: I have the same problem on my laptop HP Pavilon dc6809wm thanks -- System freezes during boot, unless I hold a key down https://bugs.launchpad.net/bugs/272247 You received this bug notification because you are a direct subscriber of the bug. Status in The Linux Kernel: Confirmed Status in Ubuntu Release Notes: Confirmed Status in “linux” source package in Ubuntu: Confirmed Status in “usplash” source package in Ubuntu: Invalid Status in linux in Ubuntu Intrepid: Triaged Status in usplash in Ubuntu Intrepid: Invalid Status in “linux” source package in Mandriva: Invalid Bug description: Once the Ubuntu splash screen loads with the progress bar that moves back and forth, it freezes. Holding down any key unfreezes the system, and it continues loading normally, until I release the key, at which point it freezes again. Holding a key down again unfreezes the system again. Pressing Alt+F1 to show the output also freezes, so I know it isn't just the splash screen freezing, but the entire system. Once X loads, it works perfectly fine though, and I don't have to keep holding a key down. Update : This bug happens with 2.6.26 and 2.6.27 kernels with a computer that has Nvidia MCP67 motherboard. A known workaround that sometimes works is to add nolapic to GRUB boot kernel options. acpi=noirq is also known to work. ProblemType: Bug Architecture: amd64 DistroRelease: Ubuntu 8.10 NonfreeKernelModules: wl nvidia Package: usplash 0.5.23 ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: usplash Uname: Linux 2.6.27-3-generic x86_64 -- Possible systems affected include: Nvidia MCP67 Chipset Compaq Presario F700 Compaq Presario F763NR Sony Vaio PCG-GRT-815E - from the Mandriva errata HP Pavilion DV6545eg Notebook - from duplicate HP Pavilion DV6736nr HP Pavilion DV6745us - from a duplicate HP Pavilion DV6620es HP Pavilion DV9610us HP Pavilion DV9700z HP Pavilion DV6915nr HP Pavilion DV9645ed HP G6062ea -- System freezes during boot, unless I hold a key down https://bugs.launchpad.net/bugs/272247 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 272247] Re: System freezes during boot, unless I hold a key down
I just noticed something I haven't before.. I may have previously stated that the new kernels being used in Jaunty fix the issue, but for the first time in a very long time I booted my laptop via battery instead of the power cord and it went back to it's same old shenanigans. I was forced to use the shift key to boot the system, then it locked up (though later I found the lockup was due to a custom setting I was using for my Intuos3 tablet, while the tablet was not connected). I think I will look into this custom DSDT file and see if it resolves the issue for Jaunty as well. This is quite upsetting though, if what 67GTA says is true, this problem is not going to go away for a while. Just when we think Linux is becoming easier to use and thus more widely accepted, someone throws a handful of nails under our wheels. :/ -- System freezes during boot, unless I hold a key down https://bugs.launchpad.net/bugs/272247 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 335811] Re: ImportError: No module named qt
strangely enough, i didnt notice my bluetooth icon was missing until I reinstalled dbus. I was originally trying to fix the update notifier problem, and on reboot... my bluetooth icon showed up. Hah, I still haven't seen the update notifier icon come up with anything new though.. usually (on 8.10) if i did a manual update it'd show up, but nothing now. -- ImportError: No module named qt https://bugs.launchpad.net/bugs/335811 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdebindings in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
Re: [Bug 335879] Re: nvidia driver 180.35 breaks KDE 4, upgrade to 180.37 is needed
I just updated my jaunty release to ensure i got all of alpha 6, and the new drivers were in there.. I have proposed and backports enabled though. On Fri, Mar 13, 2009 at 3:51 PM, Schmirrwurst schmirrwu...@free.fr wrote: when the update is going to be available in the repositories ? - Mail Original - De: Launchpad Bug Tracker 335...@bugs.launchpad.net À: schmirrwu...@free.fr Envoyé: Vendredi 13 Mars 2009 20h40:07 GMT +01:00 Amsterdam / Berlin / Berne / Rome / Stockholm / Vienne Objet: [Bug 335879] Re: nvidia driver 180.35 breaks KDE 4, upgrade to 180.37 is needed This bug was fixed in the package nvidia-graphics-drivers-180 - 180.37-0ubuntu1 --- nvidia-graphics-drivers-180 (180.37-0ubuntu1) jaunty; urgency=low * New upstream release (LP: #335879). - Fixed a problem that caused signals to be blocked in some applications. - Fixed a problem that could cause Xid errors and display corruption in certain cases when OpenGL is used to render to redirected windows, for example when Java2D is used with the -Dsun.java2d.opengl=true option. - glGetStringi(GL_EXTENSIONS, i) no longer returns NULL in OpenGL 3.0 preview contexts. - Fixed a problem that caused the screen to flicker momentarily when OpenGL applications exit unexpectedly on GeForce 6 and 7 series GPUs. - Fixed an X server crash when an X client attempts to draw trapezoids and RenderAccel is disabled. - Improved recovery from certain types of errors. - VDPAU updates: o Fixed corruption on some H.264 clips. o Update documentation. o Fixed VC-1 decoding on 64-bit platforms. o Improved handling of invalid H.264 streams. o Fixed a problem that caused surfaces to be marked as visible too early when the blit presentation queue is in use. * nvidia-glx-VER.preinst: - Remove diversion on /usr/lib32/libGL.so.1.2 to /usr/lib32/nvidia/libGL.so.1.2.xlibmesa instead of /usr/lib32/nvidia/libGL.so.1.2.xserver-xorg-core (LP: #333550). * debian.binary/patches/nvidia-rt-compat.patch: - Restore compatibility with -rt kernels. Thanks to Alessio Igor Bogani for the patch. * debian/dkms.conf.in: - Make sure that the patch for -rt kernels is applied only to 2.6.28.x kernels. -- Alberto Milone alberto.mil...@canonical.com Fri, 13 Mar 2009 09:27:20 +0100 ** Changed in: nvidia-graphics-drivers-180 (Ubuntu) Status: In Progress = Fix Released -- nvidia driver 180.35 breaks KDE 4, upgrade to 180.37 is needed https://bugs.launchpad.net/bugs/335879 You received this bug notification because you are a direct subscriber of a duplicate bug. -- nvidia driver 180.35 breaks KDE 4, upgrade to 180.37 is needed https://bugs.launchpad.net/bugs/335879 You received this bug notification because you are a direct subscriber of the bug. Status in “nvidia-graphics-drivers-180” source package in Ubuntu: Fix Released Bug description: After installing the nvidia driver version 180.35, I can no longer log out of KDE. If I look in the process list I can see a long list of defunct processes that are all children of ksmserver. The only workaround seems to be to log in with an empty session (i.e disable 'Restore Previous session'). It seems that somehow the nvidia driver is causing this problem. There's a long thread on the nvnews forum here : http://www.nvnews.net/vbulletin/showthread.php?t=128992 The cure seems to be to revert back to 180.29, but it's far from obvious how to do this. Needs Package Created for: nvidia driver 180.37 nVidia Driver URL: ftp://download.nvidia.com/XFree86/ -- nvidia driver 180.35 breaks KDE 4, upgrade to 180.37 is needed https://bugs.launchpad.net/bugs/335879 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 341568] Re: update-notifier-kde.py crashed with ImportError in module()
I can both confirm the problem and confirm the fix via reinstalling python-qt4-dbus. update-notifier-kde is now showing up in processes list like it should. Not sure what exactly caused the original problem but since this system was a pure Jaunty alpha 5 install (non-upgrade from any previous version), that would technically mean this problem is most likely plaguing many people. This also explains why I haven't seen an update notification since I installed jaunty, and have had to manually check everyday. ** Changed in: update-notifier-kde (Ubuntu) Status: Incomplete = Confirmed -- update-notifier-kde.py crashed with ImportError in module() https://bugs.launchpad.net/bugs/341568 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to update-notifier-kde in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
Re: [Bug 335879] Re: [needs-packaging] nvidia driver 180.35 breaks KDE 4
Maybe someone should change the importance of this to something more than wishlist. While we all wish this would be fixed, I think it's a bit more important than that since it effects pretty much everyone with an nvidia card. On Mon, Mar 9, 2009 at 6:18 AM, Michael Marley mich...@michaelmarley.comwrote: I am glad that the PPA packages work, but this bug really needs to be fixed in Jaunty. Otherwise, it is going to get alot of trashy reviews and disgruntled users who (not knowing about the Nvidia problem) just think Jaunty stinks and they will go back to Intrepid. -- [needs-packaging] nvidia driver 180.35 breaks KDE 4 https://bugs.launchpad.net/bugs/335879 You received this bug notification because you are a direct subscriber of the bug. Status in “nvidia-graphics-drivers-180” source package in Ubuntu: Confirmed Bug description: After installing the nvidia driver version 180.35, I can no longer log out of KDE. If I look in the process list I can see a long list of defunct processes that are all children of ksmserver. The only workaround seems to be to log in with an empty session (i.e disable 'Restore Previous session'). It seems that somehow the nvidia driver is causing this problem. There's a long thread on the nvnews forum here : http://www.nvnews.net/vbulletin/showthread.php?t=128992 The cure seems to be to revert back to 180.29, but it's far from obvious how to do this. Needs Package Created for: nvidia driver 180.37 nVidia Driver URL: ftp://download.nvidia.com/XFree86/ -- [needs-packaging] nvidia driver 180.35 breaks KDE 4 https://bugs.launchpad.net/bugs/335879 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 335879] Re: nvidia driver 180.35 breaks KDE 4
I added the tag needs-packaging in the hopes it will bring this particular problem to attention. Jaunty really should have this driver updated, while we have a location to retrieve older driver packages and the means to lock them I don't believe that should be considered a triage or fix. To anyone with the means and interested in making the packages themselves: FTP URL: ftp://download.nvidia.com/XFree86/ ** Description changed: After installing the nvidia driver version 180.35, I can no longer log out of KDE. If I look in the process list I can see a long list of defunct processes that are all children of ksmserver. The only workaround seems to be to log in with an empty session (i.e disable 'Restore Previous session'). It seems that somehow the nvidia driver is causing this problem. There's a long thread on the nvnews forum here : http://www.nvnews.net/vbulletin/showthread.php?t=128992 The cure seems to be to revert back to 180.29, but it's far from obvious how to do this. + + Needs Package Created for: nvidia driver 180.37 + nVidia Driver URL: ftp://download.nvidia.com/XFree86/ ** Tags added: needs-packaging -- nvidia driver 180.35 breaks KDE 4 https://bugs.launchpad.net/bugs/335879 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
Re: [Bug 335879] Re: nvidia driver 180.35 breaks KDE 4
Thanks michael, I've been been using the drivers from your repos for about an hour now, and so far they seem to fix the problem .35 produced. Hopefully these will make it into the jaunty repos soon. Until then I think I will be keeping your repos` in my sources list. :) On Sun, Mar 8, 2009 at 12:43 PM, Michael Marley mich...@michaelmarley.comwrote: There are also builds in my PPA for Jaunty and Intrepid. I always try to keep these up-to-date. -- nvidia driver 180.35 breaks KDE 4 https://bugs.launchpad.net/bugs/335879 You received this bug notification because you are a direct subscriber of the bug. Status in “nvidia-graphics-drivers-180” source package in Ubuntu: Confirmed Bug description: After installing the nvidia driver version 180.35, I can no longer log out of KDE. If I look in the process list I can see a long list of defunct processes that are all children of ksmserver. The only workaround seems to be to log in with an empty session (i.e disable 'Restore Previous session'). It seems that somehow the nvidia driver is causing this problem. There's a long thread on the nvnews forum here : http://www.nvnews.net/vbulletin/showthread.php?t=128992 The cure seems to be to revert back to 180.29, but it's far from obvious how to do this. Needs Package Created for: nvidia driver 180.37 nVidia Driver URL: ftp://download.nvidia.com/XFree86/ -- nvidia driver 180.35 breaks KDE 4 https://bugs.launchpad.net/bugs/335879 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
Re: [Bug 335879] Re: nvidia driver 180.35 breaks KDE 4
I agree, Jaunty is still in alpha anyway... they should pop them in untested or something so we can have a crack at them. I doubt they could be any worse than 180.35 anyway. On Sat, Mar 7, 2009 at 12:20 PM, Mark Greenwood fatger...@ntlworld.comwrote: Why not create some packages just for Jaunty, it's still in Alpha? I'll test them - so long as you notify this bug report (I've Pinned my packages to 180.29). -- nvidia driver 180.35 breaks KDE 4 https://bugs.launchpad.net/bugs/335879 You received this bug notification because you are a direct subscriber of the bug. Status in “nvidia-graphics-drivers-180” source package in Ubuntu: Confirmed Bug description: After installing the nvidia driver version 180.35, I can no longer log out of KDE. If I look in the process list I can see a long list of defunct processes that are all children of ksmserver. The only workaround seems to be to log in with an empty session (i.e disable 'Restore Previous session'). It seems that somehow the nvidia driver is causing this problem. There's a long thread on the nvnews forum here : http://www.nvnews.net/vbulletin/showthread.php?t=128992 The cure seems to be to revert back to 180.29, but it's far from obvious how to do this. -- nvidia driver 180.35 breaks KDE 4 https://bugs.launchpad.net/bugs/335879 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
Re: [Bug 335879] Re: nvidia driver 180.35 breaks KDE 4
As soon as the packages pop up I'd be more than happy to test. I don't like manually installing drivers because I don't think they work with dkms, and with all the kernel upgrades kubuntu likes to push out, it's much easier for me to let it do the work itself. My laptop's video is very tempermental, NV drivers don't even work on it.. and my laptop becomes near-unusable unless I custom my xorg file and force it into vesa (hell my ctrl-alt-F? consoles still don't work on multiple distros). So once I see the packages come up, I will be sure to try them out. On Fri, Mar 6, 2009 at 4:25 PM, Aaron Plattner aplatt...@nvidia.com wrote: Please give 180.37 a try. -- nvidia driver 180.35 breaks KDE 4 https://bugs.launchpad.net/bugs/335879 You received this bug notification because you are a direct subscriber of the bug. Status in “nvidia-graphics-drivers-180” source package in Ubuntu: Confirmed Bug description: After installing the nvidia driver version 180.35, I can no longer log out of KDE. If I look in the process list I can see a long list of defunct processes that are all children of ksmserver. The only workaround seems to be to log in with an empty session (i.e disable 'Restore Previous session'). It seems that somehow the nvidia driver is causing this problem. There's a long thread on the nvnews forum here : http://www.nvnews.net/vbulletin/showthread.php?t=128992 The cure seems to be to revert back to 180.29, but it's far from obvious how to do this. -- nvidia driver 180.35 breaks KDE 4 https://bugs.launchpad.net/bugs/335879 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
Re: [Bug 335879] Re: nvidia driver 180.35 breaks KDE 4
I also added this one since it was in the collection of packages provided here, didn't want anything to get screwed up with mismatched versions: Package: nvidia-180-libvdpau Pin: release Pin-Priority: 999 On Thu, Mar 5, 2009 at 8:41 AM, 3vi1 launchpad@eternaldusk.com wrote: As mentioned in my earlier post with the link to the same thread, there's no telling when they will release the next driver. It could be two weeks or two months. My suggestion to hold back 180.35 was thinking about the worst case scenario: Jaunty goes live and 180.35 is still the latest package. In the meantime, I suggest everyone who wants to continue testing the other parts of Jaunty should work around this by pinning the nvidia packages. Adding the following to your /etc/apt/preferences (may need to be created) file will let you get the other updates without worrying about 180.29 getting overwritten by 180.35: Package: nvidia-glx-180 Pin: release Pin-Priority: 999 Package: nvidia-180-kernel-source Pin: release Pin-Priority: 999 Package: nvidia-glx-180-dev Pin: release Pin-Priority: 999 -- nvidia driver 180.35 breaks KDE 4 https://bugs.launchpad.net/bugs/335879 You received this bug notification because you are a direct subscriber of the bug. Status in “nvidia-graphics-drivers-180” source package in Ubuntu: Confirmed Bug description: After installing the nvidia driver version 180.35, I can no longer log out of KDE. If I look in the process list I can see a long list of defunct processes that are all children of ksmserver. The only workaround seems to be to log in with an empty session (i.e disable 'Restore Previous session'). It seems that somehow the nvidia driver is causing this problem. There's a long thread on the nvnews forum here : http://www.nvnews.net/vbulletin/showthread.php?t=128992 The cure seems to be to revert back to 180.29, but it's far from obvious how to do this. -- nvidia driver 180.35 breaks KDE 4 https://bugs.launchpad.net/bugs/335879 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 335879] Re: nvidia driver 180.35 breaks KDE 4
first, I'd like to thank getaceres for providing the 180.29 packages, they fixed all the bugs I currently have with jaunty. Second, I agree with 3vil, they should put .29 back until nvidia fixes the problem because the current drivers break numerous parts of kde4. -- nvidia driver 180.35 breaks KDE 4 https://bugs.launchpad.net/bugs/335879 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 336115] Re: screensaver refuses to exit
This bug is caused by the nvidia drivers as found in this bug: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- drivers-180/+bug/335879 going to mark it as invalid. ** Changed in: kdeartwork (Ubuntu) Status: New = Invalid -- screensaver refuses to exit https://bugs.launchpad.net/bugs/336115 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdeartwork in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 336112] Re: numerous processes show as defunct
Funny you should mention that, I was just about to mark these as invalid (this bug + one with the screensaver's not functioning as intended) because they were both fixed via backing off my nvidia drivers to pre .35 as mentioned in this bug: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- drivers-180/+bug/335879 ** Changed in: kdebase (Ubuntu) Status: Incomplete = Invalid -- numerous processes show as defunct https://bugs.launchpad.net/bugs/336112 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 336112] [NEW] numerous processes show as defunct
Public bug reported: Binary package hint: ksmserver Distributor ID: Ubuntu Description:Ubuntu jaunty (development branch) Release:9.04 Codename: jaunty Linux 2.6.28-8-generic #26-Ubuntu SMP Wed Feb 25 04:28:54 UTC 2009 i686 GNU/Linux I've recently updated to Jaunty alpha 5, while trying to diagnose a few other issues (including screensaver problems, and certain keyboard shortcuts not working), I came across numerous processes coming up defunct, all of which coming from ksmserver. Via ps aux --forest: 1000 6862 0.0 1.6 100800 31124 ?Sl 22:55 0:00 \_ ksmserver 1000 6864 6.7 2.3 108084 46292 ?Sl 22:55 1:50 | \_ kwin -session 10f7149143c50001235878257004375 1000 7471 0.0 0.0 0 0 ?Z23:00 0:00 | | \_ [kwin_killer_hel] defunct 1000 6896 0.0 0.0 0 0 ?Z22:55 0:00 | \_ [nepomukserver] defunct 1000 6906 0.0 0.0 0 0 ?Z22:55 0:00 | \_ [nepomukservices] defunct 1000 6907 0.0 0.0 0 0 ?Z22:55 0:00 | \_ [nepomukservices] defunct 1000 6908 0.0 0.0 0 0 ?Z22:55 0:00 | \_ [nepomukservices] defunct 1000 6909 0.0 0.0 0 0 ?Z22:55 0:00 | \_ [nepomukservices] defunct 1000 6910 0.0 0.0 0 0 ?Z22:55 0:00 | \_ [nepomukservices] defunct 1000 6911 0.0 0.0 0 0 ?Z22:55 0:00 | \_ [kmix] defunct 1000 6913 0.0 0.0 0 0 ?Z22:55 0:00 | \_ [python] defunct 1000 6914 0.0 0.0 0 0 ?Z22:55 0:00 | \_ [python] defunct 1000 6915 0.0 0.0 0 0 ?Z22:55 0:00 | \_ [kwalletmanager] defunct 1000 6917 0.0 0.0 0 0 ?Z22:55 0:00 | \_ [kopete] defunct 1000 6919 0.0 0.0 0 0 ?Z22:55 0:00 | \_ [systemsettings] defunct 1000 6921 0.0 0.0 0 0 ?Z22:55 0:00 | \_ [kblankscrn.kss] defunct 1000 6922 0.0 0.0 0 0 ?Z22:55 0:00 | \_ [konsole] defunct These apps all seem to be working, I have volume control, I have mixer control, wallet is functional, etc. The screensaver issue I will have to report a secondary bug for, but it's in there as well I see. ** Affects: kdebase (Ubuntu) Importance: Undecided Status: New ** Tags: alpha defunct jaunty ksmserver ** Description changed: Binary package hint: ksmserver + + Distributor ID: Ubuntu + Description:Ubuntu jaunty (development branch) + Release:9.04 + Codename: jaunty + + Linux 2.6.28-8-generic #26-Ubuntu SMP Wed Feb 25 04:28:54 UTC 2009 i686 + GNU/Linux I've recently updated to Jaunty alpha 5, while trying to diagnose a few other issues (including screensaver problems, and certain keyboard shortcuts not working), I came across numerous processes coming up defunct, all of which coming from ksmserver. Via ps aux --forest: 1000 6862 0.0 1.6 100800 31124 ?Sl 22:55 0:00 \_ ksmserver 1000 6864 6.7 2.3 108084 46292 ?Sl 22:55 1:50 | \_ kwin -session 10f7149143c50001235878257004375 1000 7471 0.0 0.0 0 0 ?Z23:00 0:00 | | \_ [kwin_killer_hel] defunct 1000 6896 0.0 0.0 0 0 ?Z22:55 0:00 | \_ [nepomukserver] defunct 1000 6906 0.0 0.0 0 0 ?Z22:55 0:00 | \_ [nepomukservices] defunct 1000 6907 0.0 0.0 0 0 ?Z22:55 0:00 | \_ [nepomukservices] defunct 1000 6908 0.0 0.0 0 0 ?Z22:55 0:00 | \_ [nepomukservices] defunct 1000 6909 0.0 0.0 0 0 ?Z22:55 0:00 | \_ [nepomukservices] defunct 1000 6910 0.0 0.0 0 0 ?Z22:55 0:00 | \_ [nepomukservices] defunct 1000 6911 0.0 0.0 0 0 ?Z22:55 0:00 | \_ [kmix] defunct 1000 6913 0.0 0.0 0 0 ?Z22:55 0:00 | \_ [python] defunct 1000 6914 0.0 0.0 0 0 ?Z22:55 0:00 | \_ [python] defunct
[Bug 336115] [NEW] screensaver refuses to exit
Public bug reported: Binary package hint: kscreensaver Distributor ID: Ubuntu Description:Ubuntu jaunty (development branch) Release:9.04 Codename: jaunty Linux 2.6.28-8-generic #26-Ubuntu SMP Wed Feb 25 04:28:54 UTC 2009 i686 GNU/Linux I've been having sketchy behavior with my screensavers. First, selecting a screensaver via: System Settings-Desktop-Screen Saver doesn't show a change in the preview window. When I attempt to test a screensaver, or one comes on by itself, my mouse cursor appears over it but any amount of clicking or button presses will not cancel it out. Nothing short of dropping to console, searching for it, and issuing a kill -9 to the app will stop it. ** Affects: kdeartwork (Ubuntu) Importance: Undecided Status: New -- screensaver refuses to exit https://bugs.launchpad.net/bugs/336115 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
Re: [Bug 272247] Re: System freezes during boot, unless I hold a key down
Tell-tale signs are the apci issues, and the nvidia MCP67 chipset, and it's HP :/ all the Pavilion laptops with the AMD solution instead of Intel seem to be effected. But I believe that but report is geared towards mandriva's kernel, while this one is for ubuntu. I may be wrong tho, but they are essentially the same problem. On Mon, Feb 2, 2009 at 12:18 AM, nitto ni...@simail.it wrote: Is the Bug #254668 a duplicate of this bug? Or vice versa? The description and the behavior look equal to the bug on my laptop No luck with GIT, yet -- System freezes during boot, unless I hold a key down https://bugs.launchpad.net/bugs/272247 You received this bug notification because you are a direct subscriber of the bug. Status in The Linux Kernel: Confirmed Status in Ubuntu Release Notes: New Status in linux source package in Ubuntu: Fix Released Status in usplash source package in Ubuntu: Invalid Status in linux in Ubuntu Intrepid: Triaged Status in usplash in Ubuntu Intrepid: Invalid Status in linux source package in Mandriva: Invalid Bug description: Once the Ubuntu splash screen loads with the progress bar that moves back and forth, it freezes. Holding down any key unfreezes the system, and it continues loading normally, until I release the key, at which point it freezes again. Holding a key down again unfreezes the system again. Pressing Alt+F1 to show the output also freezes, so I know it isn't just the splash screen freezing, but the entire system. Once X loads, it works perfectly fine though, and I don't have to keep holding a key down. Update : This bug happens with 2.6.26 and 2.6.27 kernels with a computer that has Nvidia MCP67 motherboard. A known workaround that sometimes works is to add nolapic to GRUB boot kernel options. acpi=noirq is also known to work. ProblemType: Bug Architecture: amd64 DistroRelease: Ubuntu 8.10 NonfreeKernelModules: wl nvidia Package: usplash 0.5.23 ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: usplash Uname: Linux 2.6.27-3-generic x86_64 -- Possible systems affected include: Nvidia MCP67 Chipset Compaq Presario F700 Compaq Presario F763NR Sony Vaio PCG-GRT-815E - from the Mandriva errata HP Pavilion DV6545eg Notebook - from duplicate HP Pavilion DV6736nr HP Pavilion DV6745us - from a duplicate HP Pavilion DV6620es HP Pavilion DV9610us HP Pavilion DV9700z HP Pavilion DV6915nr HP Pavilion DV9645ed -- System freezes during boot, unless I hold a key down https://bugs.launchpad.net/bugs/272247 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
Re: [Bug 272247] Re: System freezes during boot, unless I hold a key down
If i am not mistaken, the Jaunty alpha series boots from the 2.6.27 kernel series with the problem on install. What actually fixes the problem is the 2.6.28 kernel you can update to. If it doesn't show up in the normal updates, try checking pre-release or unsupported. If people are getting this to work fully feedback would probably be a good idea. As I stated in a previous post, I tried out the new jaunty, and while the 2.6.28 series kernel did fix the boot problem, I experienced erratic behavior with the mousekeyboard. It would act as if keys were being held down and actually would randomly paste things into windows and chats as I was typing, ultimately after not finding where the problem was coming from, I went back to intrepid with the acpi=noirq option which works best for me on my HP dv9610us. On Sun, Feb 1, 2009 at 10:21 AM, Perpetual lando...@yahoo.com wrote: Alpha 3 still requires holding a key during boot. So, if this is now something different...how do I go about figuring out what is the new problem that exhibits the same issue as the bug reported here? -- System freezes during boot, unless I hold a key down https://bugs.launchpad.net/bugs/272247 You received this bug notification because you are a direct subscriber of the bug. Status in The Linux Kernel: Confirmed Status in Ubuntu Release Notes: New Status in linux source package in Ubuntu: Fix Released Status in usplash source package in Ubuntu: Invalid Status in linux in Ubuntu Intrepid: Triaged Status in usplash in Ubuntu Intrepid: Invalid Status in linux source package in Mandriva: Invalid Bug description: Once the Ubuntu splash screen loads with the progress bar that moves back and forth, it freezes. Holding down any key unfreezes the system, and it continues loading normally, until I release the key, at which point it freezes again. Holding a key down again unfreezes the system again. Pressing Alt+F1 to show the output also freezes, so I know it isn't just the splash screen freezing, but the entire system. Once X loads, it works perfectly fine though, and I don't have to keep holding a key down. Update : This bug happens with 2.6.26 and 2.6.27 kernels with a computer that has Nvidia MCP67 motherboard. A known workaround that sometimes works is to add nolapic to GRUB boot kernel options. acpi=noirq is also known to work. ProblemType: Bug Architecture: amd64 DistroRelease: Ubuntu 8.10 NonfreeKernelModules: wl nvidia Package: usplash 0.5.23 ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: usplash Uname: Linux 2.6.27-3-generic x86_64 -- Possible systems affected include: Nvidia MCP67 Chipset Compaq Presario F700 Compaq Presario F763NR Sony Vaio PCG-GRT-815E - from the Mandriva errata HP Pavilion DV6545eg Notebook - from duplicate HP Pavilion DV6736nr HP Pavilion DV6745us - from a duplicate HP Pavilion DV6620es HP Pavilion DV9610us HP Pavilion DV9700z -- System freezes during boot, unless I hold a key down https://bugs.launchpad.net/bugs/272247 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
Re: [Bug 272247] Re: System freezes during boot, unless I hold a key down
In regards to the GIT question, I have not tried it.. but I came across this which might be something for you to look at... it's a zen kernel for 2.6.28. https://wiki.kubuntu.org/ZenKernel On Sun, Feb 1, 2009 at 2:55 PM, Morten Minke mor...@earthrevealed.comwrote: ** Description changed: Once the Ubuntu splash screen loads with the progress bar that moves back and forth, it freezes. Holding down any key unfreezes the system, and it continues loading normally, until I release the key, at which point it freezes again. Holding a key down again unfreezes the system again. Pressing Alt+F1 to show the output also freezes, so I know it isn't just the splash screen freezing, but the entire system. Once X loads, it works perfectly fine though, and I don't have to keep holding a key down. Update : This bug happens with 2.6.26 and 2.6.27 kernels with a computer that has Nvidia MCP67 motherboard. A known workaround that sometimes works is to add nolapic to GRUB boot kernel options. acpi=noirq is also known to work. ProblemType: Bug Architecture: amd64 DistroRelease: Ubuntu 8.10 NonfreeKernelModules: wl nvidia Package: usplash 0.5.23 ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: usplash Uname: Linux 2.6.27-3-generic x86_64 -- Possible systems affected include: Nvidia MCP67 Chipset Compaq Presario F700 Compaq Presario F763NR Sony Vaio PCG-GRT-815E - from the Mandriva errata HP Pavilion DV6545eg Notebook - from duplicate HP Pavilion DV6736nr HP Pavilion DV6745us - from a duplicate HP Pavilion DV6620es HP Pavilion DV9610us HP Pavilion DV9700z HP Pavilion DV6915nr + HP Pavilion DV9645ed -- System freezes during boot, unless I hold a key down https://bugs.launchpad.net/bugs/272247 You received this bug notification because you are a direct subscriber of the bug. Status in The Linux Kernel: Confirmed Status in Ubuntu Release Notes: New Status in linux source package in Ubuntu: Fix Released Status in usplash source package in Ubuntu: Invalid Status in linux in Ubuntu Intrepid: Triaged Status in usplash in Ubuntu Intrepid: Invalid Status in linux source package in Mandriva: Invalid Bug description: Once the Ubuntu splash screen loads with the progress bar that moves back and forth, it freezes. Holding down any key unfreezes the system, and it continues loading normally, until I release the key, at which point it freezes again. Holding a key down again unfreezes the system again. Pressing Alt+F1 to show the output also freezes, so I know it isn't just the splash screen freezing, but the entire system. Once X loads, it works perfectly fine though, and I don't have to keep holding a key down. Update : This bug happens with 2.6.26 and 2.6.27 kernels with a computer that has Nvidia MCP67 motherboard. A known workaround that sometimes works is to add nolapic to GRUB boot kernel options. acpi=noirq is also known to work. ProblemType: Bug Architecture: amd64 DistroRelease: Ubuntu 8.10 NonfreeKernelModules: wl nvidia Package: usplash 0.5.23 ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: usplash Uname: Linux 2.6.27-3-generic x86_64 -- Possible systems affected include: Nvidia MCP67 Chipset Compaq Presario F700 Compaq Presario F763NR Sony Vaio PCG-GRT-815E - from the Mandriva errata HP Pavilion DV6545eg Notebook - from duplicate HP Pavilion DV6736nr HP Pavilion DV6745us - from a duplicate HP Pavilion DV6620es HP Pavilion DV9610us HP Pavilion DV9700z HP Pavilion DV6915nr HP Pavilion DV9645ed -- System freezes during boot, unless I hold a key down https://bugs.launchpad.net/bugs/272247 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
Re: [Bug 272247] Re: System freezes during boot, unless I hold a key down
I actually don't believe this problem is fixed at all. I messed with jaunty when I had heard that this problem was fixed in the 2.6.28 kernel but experienced erratic keyboard/mouse behavior. Might just be me but I never had the problem in intrepid. Now, I am not sure exactly what your problem is with the 32bit version crjackson, I do know (having the dv9610us myself), that it takes a bit of... coaxing... to get it to install out-right. My laptop refused to boot into the GUI until i pulled up a direct console (ctrl-alt-f1), customized the xorg.conf file and added the ' Driver vesa ' for the video display, then did a 'sudo /etc/init.d/kdm restart'. That allowed me to install the OS and actually will copy that xorg.conf to the main drive. After which, I connected it to the net via cat5, installed b43-fwcutter (i believe is the file) which enabled my wireless, then installed nvidia-glx-180 and re-edited my conf file and changed the driver to nvidia. Once all that was done i restarted KDE and was good to go with accelerated drivers. Everything after that is a breeze. On Fri, Jan 30, 2009 at 6:18 PM, crjackson crjack...@carolina.rr.comwrote: Okay, so I have read through the comments and can't get a clear grasp. The status if this bug is Fix Released but it sounds like the problem is still there. I recently convinced my younger brother to convert to Ubuntu and he has one of the affected HP Turion systems. He can't boot a 32-bit distro at all, and can boot the 64-bit distro using the keyboard spacebar method using Intrepid Ibex 64-bit. Is it possible to make this problem go away fairly easily or should he just go with 8.04? Since 8.10 is already installed and works fine short of this issue, 8.10 is preferred. Thanks -- System freezes during boot, unless I hold a key down https://bugs.launchpad.net/bugs/272247 You received this bug notification because you are a direct subscriber of the bug. Status in The Linux Kernel: Confirmed Status in Ubuntu Release Notes: New Status in linux source package in Ubuntu: Fix Released Status in usplash source package in Ubuntu: Invalid Status in linux in Ubuntu Intrepid: Triaged Status in usplash in Ubuntu Intrepid: Invalid Status in linux source package in Mandriva: Invalid Bug description: Once the Ubuntu splash screen loads with the progress bar that moves back and forth, it freezes. Holding down any key unfreezes the system, and it continues loading normally, until I release the key, at which point it freezes again. Holding a key down again unfreezes the system again. Pressing Alt+F1 to show the output also freezes, so I know it isn't just the splash screen freezing, but the entire system. Once X loads, it works perfectly fine though, and I don't have to keep holding a key down. Update : This bug happens with 2.6.26 and 2.6.27 kernels with a computer that has Nvidia MCP67 motherboard. A known workaround that sometimes works is to add nolapic to GRUB boot kernel options. acpi=noirq is also known to work. ProblemType: Bug Architecture: amd64 DistroRelease: Ubuntu 8.10 NonfreeKernelModules: wl nvidia Package: usplash 0.5.23 ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: usplash Uname: Linux 2.6.27-3-generic x86_64 -- Possible systems affected include: Nvidia MCP67 Chipset Compaq Presario F700 Compaq Presario F763NR Sony Vaio PCG-GRT-815E - from the Mandriva errata HP Pavilion DV6545eg Notebook - from duplicate HP Pavilion DV6736nr HP Pavilion DV6745us - from a duplicate HP Pavilion DV6620es HP Pavilion DV9610us HP Pavilion DV9700z -- System freezes during boot, unless I hold a key down https://bugs.launchpad.net/bugs/272247 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
Re: [Bug 280997] Re: solid-bluetooth needs update for bluez 4.x
I am guessing these won't make it into kde 4.2 until the official release? On Thu, Jan 22, 2009 at 7:54 AM, Scott Kitterman ubu...@kitterman.comwrote: It's automatically built. The amd64 buildds are just running a bit behind. -- solid-bluetooth needs update for bluez 4.x https://bugs.launchpad.net/bugs/280997 You received this bug notification because you are a direct subscriber of the bug. Status in KDE Base Components: Confirmed Status in Ubuntu Release Notes: Fix Released Status in kdebase-workspace source package in Ubuntu: Fix Released Status in kdebase-workspace in Ubuntu Intrepid: Fix Committed Status in kdebase-workspace in Ubuntu Jaunty: Fix Released Bug description: Binary package hint: kdebase-workspace Bluetooth still doesn't work after the kdebluetooth fixes. :/usr/bin$ kbluetooth4-devicemanager kbluetooth4-devicemanager(8525) Solid::Control::ManagerBasePrivate::loadBackend: Backend loaded: BlueZ process 8525: arguments to dbus_message_new_method_call() were incorrect, assertion path != NULL failed in file dbus-message.c line 1070. This is normally a bug in some application using the D-Bus library. QDBusConnection: error: could not send message to service org.bluez path interface org.freedesktop.DBus.Introspectable member Introspect kbluetooth4-devicemanager(8525) DeviceMan::DeviceMan: Device Manager - Welcome kbluetooth4-devicemanager(8525) DeviceMan::getConfiguredDevices: Device List Size: 0 kbluetooth4-devicemanager(8525) DeviceMan::slotStartWizard: Starting Wizard kbluetooth4-wizard(8542) Solid::Control::ManagerBasePrivate::loadBackend: Backend loaded: BlueZ process 8542: arguments to dbus_message_new_method_call() were incorrect, assertion path != NULL failed in file dbus-message.c line 1070. This is normally a bug in some application using the D-Bus library. QDBusConnection: error: could not send message to service org.bluez path interface org.freedesktop.DBus.Introspectable member Introspect Object::connect: No such slot BTWizard::slotValidatePage() kbluetooth4-wizard(8542) BTWizard::slotNext: Page ID: 1 kbluetooth4-wizard(8542) BTWizard::slotNext: Page ID: 2 kbluetooth4-wizard(8542) BTWizard::slotNext: page 2 reached! kbluetooth4-wizard(8542) BTWizard::slotSearch: searching... process 8542: arguments to dbus_message_new_method_call() were incorrect, assertion path != NULL failed in file dbus-message.c line 1070. This is normally a bug in some application using the D-Bus library. QDBusConnection: error: could not send message to service org.bluez path interface org.bluez.Adapter member DiscoverDevices TEST CASE: Install KDE 4.1.4 including kdebase-workspace-bin, -data, and -libs4+5 4.1.4-0ubuntu1~intrepid2 (after they are published and built) and the updated kdebluetooth 0.3 from intrepid-proposed. Try bluetooth. If you have any, the test is successful (there is none in the released packages). -- solid-bluetooth needs update for bluez 4.x https://bugs.launchpad.net/bugs/280997 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
Re: [Bug 280997] Re: solid-bluetooth needs update for bluez 4.x
I just updated my packaged for intrepid w/ kde 4.2rc1 and got the app upgrade, seems to be working, I will try to pair it with something later to see if it's fully functional. On Thu, Jan 22, 2009 at 10:48 AM, Scott Kitterman ubu...@kitterman.comwrote: The ones you want are version 4.1.4-0ubuntu1~intrepid3. They are there. Perhaps not on your mirror yet. -- solid-bluetooth needs update for bluez 4.x https://bugs.launchpad.net/bugs/280997 You received this bug notification because you are a direct subscriber of the bug. Status in KDE Base Components: Confirmed Status in Ubuntu Release Notes: Fix Released Status in kdebase-workspace source package in Ubuntu: Fix Released Status in kdebase-workspace in Ubuntu Intrepid: Fix Committed Status in kdebase-workspace in Ubuntu Jaunty: Fix Released Bug description: Binary package hint: kdebase-workspace Bluetooth still doesn't work after the kdebluetooth fixes. :/usr/bin$ kbluetooth4-devicemanager kbluetooth4-devicemanager(8525) Solid::Control::ManagerBasePrivate::loadBackend: Backend loaded: BlueZ process 8525: arguments to dbus_message_new_method_call() were incorrect, assertion path != NULL failed in file dbus-message.c line 1070. This is normally a bug in some application using the D-Bus library. QDBusConnection: error: could not send message to service org.bluez path interface org.freedesktop.DBus.Introspectable member Introspect kbluetooth4-devicemanager(8525) DeviceMan::DeviceMan: Device Manager - Welcome kbluetooth4-devicemanager(8525) DeviceMan::getConfiguredDevices: Device List Size: 0 kbluetooth4-devicemanager(8525) DeviceMan::slotStartWizard: Starting Wizard kbluetooth4-wizard(8542) Solid::Control::ManagerBasePrivate::loadBackend: Backend loaded: BlueZ process 8542: arguments to dbus_message_new_method_call() were incorrect, assertion path != NULL failed in file dbus-message.c line 1070. This is normally a bug in some application using the D-Bus library. QDBusConnection: error: could not send message to service org.bluez path interface org.freedesktop.DBus.Introspectable member Introspect Object::connect: No such slot BTWizard::slotValidatePage() kbluetooth4-wizard(8542) BTWizard::slotNext: Page ID: 1 kbluetooth4-wizard(8542) BTWizard::slotNext: Page ID: 2 kbluetooth4-wizard(8542) BTWizard::slotNext: page 2 reached! kbluetooth4-wizard(8542) BTWizard::slotSearch: searching... process 8542: arguments to dbus_message_new_method_call() were incorrect, assertion path != NULL failed in file dbus-message.c line 1070. This is normally a bug in some application using the D-Bus library. QDBusConnection: error: could not send message to service org.bluez path interface org.bluez.Adapter member DiscoverDevices TEST CASE: Install KDE 4.1.4 including kdebase-workspace-bin, -data, and -libs4+5 4.1.4-0ubuntu1~intrepid2 (after they are published and built) and the updated kdebluetooth 0.3 from intrepid-proposed. Try bluetooth. If you have any, the test is successful (there is none in the released packages). -- solid-bluetooth needs update for bluez 4.x https://bugs.launchpad.net/bugs/280997 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
Re: [Bug 280997] Re: solid-bluetooth needs update for bluez 4.x
I've apparently managed to break it already. I was attempting to pair it with my cellphone when the kbluetooth4-devicemanager crashed. It now refuses to open with the following output: kbluetooth4-devicemanager(8445) Solid::Control::ManagerBasePrivate::loadBackend: Backend loaded: BlueZ kbluetooth4-devicemanager(8445) DeviceMan::DeviceMan: Device Manager - Welcome QDBusObjectPath: invalid path process 8445: arguments to dbus_message_new_method_call() were incorrect, assertion path != NULL failed in file dbus-message.c line 1070. This is normally a bug in some application using the D-Bus library. QDBusConnection: error: could not send message to service org.bluez path interface org.freedesktop.DBus.Introspectable memberIntrospect Object::connect: No such signal Solid::Control::BluetoothRemoteDevice::nodeCreated(QString) Object::connect: No such signal Solid::Control::BluetoothRemoteDevice::nodeRemoved(QString) Object::connect: No such signal Solid::Control::BluetoothRemoteDevice::nodeCreated(QString) Object::connect: No such signal Solid::Control::BluetoothRemoteDevice::nodeRemoved(QString) Object::connect: No such signal Solid::Control::BluetoothRemoteDevice::nodeCreated(QString) Object::connect: No such signal Solid::Control::BluetoothRemoteDevice::nodeRemoved(QString) kbluetooth4-devicemanager(8445) DeviceMan::getConfiguredDevices: Device List Size: 1 kbluetooth4-devicemanager: symbol lookup error: kbluetooth4-devicemanager: undefined symbol: _ZN5Solid7Control21BluetoothRemoteDevice4nameEv --- I believe it's refusing to open again because of a half-entry from the original crash, If I could find the config file where it's stored and wipe it I might have another shot. It may have crashed originally because no obex server was installed yet it was enabled in the menu. Trying to disable the obex without installing the server caused the entire app to crash. If anyone knows where the cfg is stored would you mind letting me know? Thanks. On Thu, Jan 22, 2009 at 5:23 PM, Javier Jardón javierjc1...@gmail.comwrote: Kubuntu 8.10 with 4.1.96 (4.2rc) Pairing and send files to my mobile phone works great here, thank you! -- solid-bluetooth needs update for bluez 4.x https://bugs.launchpad.net/bugs/280997 You received this bug notification because you are a direct subscriber of the bug. Status in KDE Base Components: Confirmed Status in Ubuntu Release Notes: Fix Released Status in kdebase-workspace source package in Ubuntu: Fix Released Status in kdebase-workspace in Ubuntu Intrepid: Fix Committed Status in kdebase-workspace in Ubuntu Jaunty: Fix Released Bug description: Binary package hint: kdebase-workspace Bluetooth still doesn't work after the kdebluetooth fixes. :/usr/bin$ kbluetooth4-devicemanager kbluetooth4-devicemanager(8525) Solid::Control::ManagerBasePrivate::loadBackend: Backend loaded: BlueZ process 8525: arguments to dbus_message_new_method_call() were incorrect, assertion path != NULL failed in file dbus-message.c line 1070. This is normally a bug in some application using the D-Bus library. QDBusConnection: error: could not send message to service org.bluez path interface org.freedesktop.DBus.Introspectable member Introspect kbluetooth4-devicemanager(8525) DeviceMan::DeviceMan: Device Manager - Welcome kbluetooth4-devicemanager(8525) DeviceMan::getConfiguredDevices: Device List Size: 0 kbluetooth4-devicemanager(8525) DeviceMan::slotStartWizard: Starting Wizard kbluetooth4-wizard(8542) Solid::Control::ManagerBasePrivate::loadBackend: Backend loaded: BlueZ process 8542: arguments to dbus_message_new_method_call() were incorrect, assertion path != NULL failed in file dbus-message.c line 1070. This is normally a bug in some application using the D-Bus library. QDBusConnection: error: could not send message to service org.bluez path interface org.freedesktop.DBus.Introspectable member Introspect Object::connect: No such slot BTWizard::slotValidatePage() kbluetooth4-wizard(8542) BTWizard::slotNext: Page ID: 1 kbluetooth4-wizard(8542) BTWizard::slotNext: Page ID: 2 kbluetooth4-wizard(8542) BTWizard::slotNext: page 2 reached! kbluetooth4-wizard(8542) BTWizard::slotSearch: searching... process 8542: arguments to dbus_message_new_method_call() were incorrect, assertion path != NULL failed in file dbus-message.c line 1070. This is normally a bug in some application using the D-Bus library. QDBusConnection: error: could not send message to service org.bluez path interface org.bluez.Adapter member DiscoverDevices TEST CASE: Install KDE 4.1.4 including kdebase-workspace-bin, -data, and -libs4+5 4.1.4-0ubuntu1~intrepid2 (after they are published and built) and the updated kdebluetooth 0.3 from intrepid-proposed. Try bluetooth. If you have any, the test is successful (there is none in the released packages). -- solid-bluetooth needs update for bluez 4.x https://bugs.launchpad.net/bugs/280997 You received this bug notification because you
[Bug 209873] Re: unable to use file sharing through dolphin -- file not found
This glitch is hard to reproduce. My laptop functions fine for whatever reason, it's aware of the existance of ./usr/share/services/fileshare.desktop ; I can even use it in dolphin. System Settings - Advanced - Samba also works perfectly. Here on my desktop neither work, I even tried copying the file over to no avail, I don't think a reboot would be required but I may just go ahead and try it anyway. Funny thing is, both systems are identical accept 1 thing. This desktop was installed via 8.10 CD, and my laptop was installed via 8.10 USB thumb drive. Both have the same repositories setup, and same basic package selections. Both have KDE 4.2rc1, altho... my laptop has had beta 1 and beta 2, this desktop didn't get converted to linux until KDE 4.2rc1. Perhaps there's a link there. -- unable to use file sharing through dolphin -- file not found https://bugs.launchpad.net/bugs/209873 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 209873] Re: unable to use file sharing through dolphin -- file not found
some more wierdness, i installed locate to see where the file exists. It didn't show up in /usr/share/services/ it showed up in /usr/share/kde4/services/ On my desktop: /usr$ find | grep fileshare ./lib/kde4/fileshare_propsdlgplugin.so ./lib/kde4/kcm_fileshare.so ./lib/kde4/libexec/filesharelist ./lib/kde4/libexec/fileshareset ./share/services/fileshare.desktop ./share/locale-langpack/en_GB/LC_MESSAGES/kfileshare.mo ./share/kde4/services/fileshare.desktop ./share/kde4/services/fileshare_propsdlgplugin.desktop ./share/man/man1/filesharelist.1.gz ./share/man/man1/fileshareset.1.gz ./bin/filesharelist ./bin/fileshareset - On my laptop (same cmd:) ./lib/kde4/fileshare_propsdlgplugin.so ./lib/kde4/libexec/filesharelist ./lib/kde4/libexec/fileshareset ./lib/kde4/kcm_fileshare.so ./share/locale-langpack/en_GB/LC_MESSAGES/kfileshare.mo ./share/kde4/services/fileshare_propsdlgplugin.desktop ./share/kde4/services/fileshare.desktop ./share/man/man1/fileshareset.1.gz ./share/man/man1/filesharelist.1.gz ./include/kfileshare.h ./include/kfilesharedialog.h ./include/kfilesharedlg.h ./bin/filesharelist ./bin/fileshareset - At this point I am completely confused... the includes, i'd assume are from -dev packages I don't have over here. Short of that all the file's seem to match up accept the one I copied to /usr/share/services/ despite me copying it FROM my laptop doesn't appear in the laptop's list. -- unable to use file sharing through dolphin -- file not found https://bugs.launchpad.net/bugs/209873 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
Re: [Bug 280997] Re: solid-bluetooth needs update for bluez 4.x
Tried compiling it this morning for intrepid + kde 4.2rc1 and came up with this: [ 3%] Building CXX object src/CMakeFiles/kbluetooth4.dir/agent/agent.o /home/srelysian/kbluetooth4/src/agent/agent.cpp: In member function 'void Agent::Authorize(QDBusObjectPath, const QString)': /home/srelysian/kbluetooth4/src/agent/agent.cpp:75: error: 'class Solid::Control::BluetoothInterface' has no member named 'findBluetoothRemoteDeviceUBI' /home/srelysian/kbluetooth4/src/agent/agent.cpp:76: error: 'class Solid::Control::BluetoothRemoteDevice' has no member named 'name' /home/srelysian/kbluetooth4/src/agent/agent.cpp:77: error: 'class Solid::Control::BluetoothRemoteDevice' has no member named 'address' /home/srelysian/kbluetooth4/src/agent/agent.cpp:84: error: 'class Solid::Control::BluetoothRemoteDevice' has no member named 'setTrusted' /home/srelysian/kbluetooth4/src/agent/agent.cpp:85: error: 'class Solid::Control::BluetoothRemoteDevice' has no member named 'name' /home/srelysian/kbluetooth4/src/agent/agent.cpp: In member function 'QString Agent::RequestPinCode(QDBusObjectPath)': /home/srelysian/kbluetooth4/src/agent/agent.cpp:105: error: 'class Solid::Control::BluetoothInterface' has no member named 'findBluetoothRemoteDeviceUBI' /home/srelysian/kbluetooth4/src/agent/agent.cpp:107: error: 'class Solid::Control::BluetoothRemoteDevice' has no member named 'name' /home/srelysian/kbluetooth4/src/agent/agent.cpp:108: error: 'class Solid::Control::BluetoothRemoteDevice' has no member named 'address' /home/srelysian/kbluetooth4/src/agent/agent.cpp: In member function 'quint32 Agent::RequestPasskey(QDBusObjectPath)': /home/srelysian/kbluetooth4/src/agent/agent.cpp:125: error: 'class Solid::Control::BluetoothInterface' has no member named 'findBluetoothRemoteDeviceUBI' /home/srelysian/kbluetooth4/src/agent/agent.cpp:127: error: 'class Solid::Control::BluetoothRemoteDevice' has no member named 'name' /home/srelysian/kbluetooth4/src/agent/agent.cpp:128: error: 'class Solid::Control::BluetoothRemoteDevice' has no member named 'address' make[2]: *** [src/CMakeFiles/kbluetooth4.dir/agent/agent.o] Error 1 make[1]: *** [src/CMakeFiles/kbluetooth4.dir/all] Error 2 make: *** [all] Error 2 I suppose I will have to wait for someone a bit more skilled than I to throw it up on PPA or something. On Mon, Jan 19, 2009 at 2:33 PM, Michael Marley mich...@michaelmarley.comwrote: You guys rock! -- solid-bluetooth needs update for bluez 4.x https://bugs.launchpad.net/bugs/280997 You received this bug notification because you are a direct subscriber of the bug. Status in KDE Base Components: Confirmed Status in Ubuntu Release Notes: Fix Released Status in kdebase-workspace source package in Ubuntu: Triaged Status in kdebase-workspace in Ubuntu Intrepid: Confirmed Bug description: Binary package hint: kdebase-workspace Bluetooth still doesn't work after the kdebluetooth fixes. :/usr/bin$ kbluetooth4-devicemanager kbluetooth4-devicemanager(8525) Solid::Control::ManagerBasePrivate::loadBackend: Backend loaded: BlueZ process 8525: arguments to dbus_message_new_method_call() were incorrect, assertion path != NULL failed in file dbus-message.c line 1070. This is normally a bug in some application using the D-Bus library. QDBusConnection: error: could not send message to service org.bluez path interface org.freedesktop.DBus.Introspectable member Introspect kbluetooth4-devicemanager(8525) DeviceMan::DeviceMan: Device Manager - Welcome kbluetooth4-devicemanager(8525) DeviceMan::getConfiguredDevices: Device List Size: 0 kbluetooth4-devicemanager(8525) DeviceMan::slotStartWizard: Starting Wizard kbluetooth4-wizard(8542) Solid::Control::ManagerBasePrivate::loadBackend: Backend loaded: BlueZ process 8542: arguments to dbus_message_new_method_call() were incorrect, assertion path != NULL failed in file dbus-message.c line 1070. This is normally a bug in some application using the D-Bus library. QDBusConnection: error: could not send message to service org.bluez path interface org.freedesktop.DBus.Introspectable member Introspect Object::connect: No such slot BTWizard::slotValidatePage() kbluetooth4-wizard(8542) BTWizard::slotNext: Page ID: 1 kbluetooth4-wizard(8542) BTWizard::slotNext: Page ID: 2 kbluetooth4-wizard(8542) BTWizard::slotNext: page 2 reached! kbluetooth4-wizard(8542) BTWizard::slotSearch: searching... process 8542: arguments to dbus_message_new_method_call() were incorrect, assertion path != NULL failed in file dbus-message.c line 1070. This is normally a bug in some application using the D-Bus library. QDBusConnection: error: could not send message to service org.bluez path interface org.bluez.Adapter member DiscoverDevices -- solid-bluetooth needs update for bluez 4.x https://bugs.launchpad.net/bugs/280997 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
[Bug 280997] Re: solid-bluetooth needs update for bluez 4.x
The triage will be broken this month. So far as I've read, kbluetooth4 is the cuplrit, which is why the 3.x drivers work with it. It was only ported and not set up to function on the bluez4 system. Downgrading bluez puts it into a version series it can get along with, but so far as I have been told KDE 4.2 is going to completely break that. The fact that there has been no progress on this saddens me, it's not like they aren't aware of it. Has anyone tried it in Jaunty yet? -- solid-bluetooth needs update for bluez 4.x https://bugs.launchpad.net/bugs/280997 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
Re: [Bug 280997] Re: solid-bluetooth needs update for bluez 4.x
The more I think on this, the more it aggravates me. I was scrolling through the posts earlier to see if any of the dev's have even spoken up about it, and I came across something to the effect of not having time to fix it. This isn't some obscure mouse that for some reason doesn't work, it's an entire system and along with it, an array of devices. Mice, Keyboards, modems, wireless/wired cards, headsets, etc. It's not even a single brand of blue-tooth, but all of them. So far as I have read, it's not working in Jaunty either... which is due in 3 months. How many distro's are we going to go through before Bluetooth becomes important. Alot of people rely on it, I for one have an external logitech BT keyboard I've missed using. And despite what other people think, I don't believe borrowing Gnome packages for a purely KDE distro is a fix. If I had a porche and the engine broke, I'd fix it, I wouldn't replace it with one from a VW Beetle. Not trying to start a flame war over gnome vs kde, but if I wanted to fill my hard-drive with gnome packages, don't you think I would have installed ubuntu instead of kubuntu? On Fri, Jan 16, 2009 at 7:09 AM, frapell frap...@gmail.com wrote: I agree this is a very bad publicity for kde to just leave things broken. I sent an email to Tom Patzig (he mentioned in one answer from 2008-12-19 that he welcome any help on fixing this) offering my help and didn't get any response at all, so dunno exactly wat's going on. -- solid-bluetooth needs update for bluez 4.x https://bugs.launchpad.net/bugs/280997 You received this bug notification because you are a direct subscriber of the bug. Status in KDE Base Components: Confirmed Status in Ubuntu Release Notes: Fix Released Status in kdebase-workspace source package in Ubuntu: Triaged Status in kdebase-workspace in Ubuntu Intrepid: Confirmed Bug description: Binary package hint: kdebase-workspace Bluetooth still doesn't work after the kdebluetooth fixes. :/usr/bin$ kbluetooth4-devicemanager kbluetooth4-devicemanager(8525) Solid::Control::ManagerBasePrivate::loadBackend: Backend loaded: BlueZ process 8525: arguments to dbus_message_new_method_call() were incorrect, assertion path != NULL failed in file dbus-message.c line 1070. This is normally a bug in some application using the D-Bus library. QDBusConnection: error: could not send message to service org.bluez path interface org.freedesktop.DBus.Introspectable member Introspect kbluetooth4-devicemanager(8525) DeviceMan::DeviceMan: Device Manager - Welcome kbluetooth4-devicemanager(8525) DeviceMan::getConfiguredDevices: Device List Size: 0 kbluetooth4-devicemanager(8525) DeviceMan::slotStartWizard: Starting Wizard kbluetooth4-wizard(8542) Solid::Control::ManagerBasePrivate::loadBackend: Backend loaded: BlueZ process 8542: arguments to dbus_message_new_method_call() were incorrect, assertion path != NULL failed in file dbus-message.c line 1070. This is normally a bug in some application using the D-Bus library. QDBusConnection: error: could not send message to service org.bluez path interface org.freedesktop.DBus.Introspectable member Introspect Object::connect: No such slot BTWizard::slotValidatePage() kbluetooth4-wizard(8542) BTWizard::slotNext: Page ID: 1 kbluetooth4-wizard(8542) BTWizard::slotNext: Page ID: 2 kbluetooth4-wizard(8542) BTWizard::slotNext: page 2 reached! kbluetooth4-wizard(8542) BTWizard::slotSearch: searching... process 8542: arguments to dbus_message_new_method_call() were incorrect, assertion path != NULL failed in file dbus-message.c line 1070. This is normally a bug in some application using the D-Bus library. QDBusConnection: error: could not send message to service org.bluez path interface org.bluez.Adapter member DiscoverDevices -- solid-bluetooth needs update for bluez 4.x https://bugs.launchpad.net/bugs/280997 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
Re: [Bug 280997] Re: solid-bluetooth needs update for bluez 4.x
I am actually using KDE 4.2rc1 right now. Unless it sneaks in under the radar at the last minute official release (which should be due by the end of this month), it's doubtful it will make it in. I do understand that they are all working hard, and I was a bit rude about it so I appologize. Just seems to me that while using kde 4.2 (b1-b2-rc1), I've noticed alot of little not-so-important things get fixed, while something as important as an entire hardware system is overlooked :/ I'd gladly trade my spinning cube desktop switcher for fully functional bluetooth :( On Fri, Jan 16, 2009 at 8:00 AM, Niels Ganser ni...@sockgap.de wrote: frapell: It's great that you want to assist in fixing this! You will probably have more success offering your help in https://bugs.kde.org/show_bug.cgi?id=172267 though, as this essentially is a KDE bug. In https://bugs.kde.org/show_bug.cgi?id=172267#c8 Tom references the repository experimental code can be found in that has already partially been ported. It would also help if every one of us voted an the KDE bug so that it gets fixed in the 4.2 release. SRELysian: I guess this bug doesn't really move forward simply because no (K)Ubuntu developer is personally affected. Don't get me wrong, I am as frustrated about this as you are but after all, all our days only have 24 hours so I'm not sure it makes sense to be angry at the developers (be it (K)Ubuntu or KDE). Clearly, this issue sneaked in shortly before the final move to KDE 4 and once it came up, the transition was already too far progressed to stop it with the release coming too soon to fix it in time. So now we're just stuck with it. Hopefully only until KDE 4.2 though :) -- solid-bluetooth needs update for bluez 4.x https://bugs.launchpad.net/bugs/280997 You received this bug notification because you are a direct subscriber of the bug. Status in KDE Base Components: Confirmed Status in Ubuntu Release Notes: Fix Released Status in kdebase-workspace source package in Ubuntu: Triaged Status in kdebase-workspace in Ubuntu Intrepid: Confirmed Bug description: Binary package hint: kdebase-workspace Bluetooth still doesn't work after the kdebluetooth fixes. :/usr/bin$ kbluetooth4-devicemanager kbluetooth4-devicemanager(8525) Solid::Control::ManagerBasePrivate::loadBackend: Backend loaded: BlueZ process 8525: arguments to dbus_message_new_method_call() were incorrect, assertion path != NULL failed in file dbus-message.c line 1070. This is normally a bug in some application using the D-Bus library. QDBusConnection: error: could not send message to service org.bluez path interface org.freedesktop.DBus.Introspectable member Introspect kbluetooth4-devicemanager(8525) DeviceMan::DeviceMan: Device Manager - Welcome kbluetooth4-devicemanager(8525) DeviceMan::getConfiguredDevices: Device List Size: 0 kbluetooth4-devicemanager(8525) DeviceMan::slotStartWizard: Starting Wizard kbluetooth4-wizard(8542) Solid::Control::ManagerBasePrivate::loadBackend: Backend loaded: BlueZ process 8542: arguments to dbus_message_new_method_call() were incorrect, assertion path != NULL failed in file dbus-message.c line 1070. This is normally a bug in some application using the D-Bus library. QDBusConnection: error: could not send message to service org.bluez path interface org.freedesktop.DBus.Introspectable member Introspect Object::connect: No such slot BTWizard::slotValidatePage() kbluetooth4-wizard(8542) BTWizard::slotNext: Page ID: 1 kbluetooth4-wizard(8542) BTWizard::slotNext: Page ID: 2 kbluetooth4-wizard(8542) BTWizard::slotNext: page 2 reached! kbluetooth4-wizard(8542) BTWizard::slotSearch: searching... process 8542: arguments to dbus_message_new_method_call() were incorrect, assertion path != NULL failed in file dbus-message.c line 1070. This is normally a bug in some application using the D-Bus library. QDBusConnection: error: could not send message to service org.bluez path interface org.bluez.Adapter member DiscoverDevices -- solid-bluetooth needs update for bluez 4.x https://bugs.launchpad.net/bugs/280997 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
Re: [Bug 280997] Re: solid-bluetooth needs update for bluez 4.x
You have my (20) vote(s). Hopefully this will change the priority a little. On Fri, Jan 16, 2009 at 8:40 AM, frapell frap...@gmail.com wrote: @Niels Ganser: Yes, that was the answer i was referring to... forgot to add a link there, heh... The mail i sent him was asking how to start, if i should read something first, etc... but i will get the code and see if there's something i can contribute... And yes, is a wonderful idea... everybody that want's this fixed NOW, go to https://bugs.kde.org/show_bug.cgi?id=172267 create an account and give that bug 20 votes :) -- solid-bluetooth needs update for bluez 4.x https://bugs.launchpad.net/bugs/280997 You received this bug notification because you are a direct subscriber of the bug. Status in KDE Base Components: Confirmed Status in Ubuntu Release Notes: Fix Released Status in kdebase-workspace source package in Ubuntu: Triaged Status in kdebase-workspace in Ubuntu Intrepid: Confirmed Bug description: Binary package hint: kdebase-workspace Bluetooth still doesn't work after the kdebluetooth fixes. :/usr/bin$ kbluetooth4-devicemanager kbluetooth4-devicemanager(8525) Solid::Control::ManagerBasePrivate::loadBackend: Backend loaded: BlueZ process 8525: arguments to dbus_message_new_method_call() were incorrect, assertion path != NULL failed in file dbus-message.c line 1070. This is normally a bug in some application using the D-Bus library. QDBusConnection: error: could not send message to service org.bluez path interface org.freedesktop.DBus.Introspectable member Introspect kbluetooth4-devicemanager(8525) DeviceMan::DeviceMan: Device Manager - Welcome kbluetooth4-devicemanager(8525) DeviceMan::getConfiguredDevices: Device List Size: 0 kbluetooth4-devicemanager(8525) DeviceMan::slotStartWizard: Starting Wizard kbluetooth4-wizard(8542) Solid::Control::ManagerBasePrivate::loadBackend: Backend loaded: BlueZ process 8542: arguments to dbus_message_new_method_call() were incorrect, assertion path != NULL failed in file dbus-message.c line 1070. This is normally a bug in some application using the D-Bus library. QDBusConnection: error: could not send message to service org.bluez path interface org.freedesktop.DBus.Introspectable member Introspect Object::connect: No such slot BTWizard::slotValidatePage() kbluetooth4-wizard(8542) BTWizard::slotNext: Page ID: 1 kbluetooth4-wizard(8542) BTWizard::slotNext: Page ID: 2 kbluetooth4-wizard(8542) BTWizard::slotNext: page 2 reached! kbluetooth4-wizard(8542) BTWizard::slotSearch: searching... process 8542: arguments to dbus_message_new_method_call() were incorrect, assertion path != NULL failed in file dbus-message.c line 1070. This is normally a bug in some application using the D-Bus library. QDBusConnection: error: could not send message to service org.bluez path interface org.bluez.Adapter member DiscoverDevices -- solid-bluetooth needs update for bluez 4.x https://bugs.launchpad.net/bugs/280997 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
Re: [Bug 272247] Re: System freezes during boot, unless I hold a key down
I haven't seen the 2.6.28 kernel either, really hoping it makes it in, since it's a ways off before they release Jaunty. I have enough beta'd software on this laptop as it is, I prefer not to make it worse. On Thu, Jan 15, 2009 at 8:58 AM, Perpetual lando...@yahoo.com wrote: Jordan Dunn, which kernel is working for you on 8.10? I did a clean install last night with backports enabled and did not see a 2.6.28 kernel in the updates. -- System freezes during boot, unless I hold a key down https://bugs.launchpad.net/bugs/272247 You received this bug notification because you are a direct subscriber of the bug. Status in The Linux Kernel: Confirmed Status in Ubuntu Release Notes: New Status in linux source package in Ubuntu: Triaged Status in usplash source package in Ubuntu: Invalid Status in linux source package in Mandriva: Invalid Bug description: Once the Ubuntu splash screen loads with the progress bar that moves back and forth, it freezes. Holding down any key unfreezes the system, and it continues loading normally, until I release the key, at which point it freezes again. Holding a key down again unfreezes the system again. Pressing Alt+F1 to show the output also freezes, so I know it isn't just the splash screen freezing, but the entire system. Once X loads, it works perfectly fine though, and I don't have to keep holding a key down. Update : This bug happens with 2.6.26 and 2.6.27 kernels with a computer that has Nvidia MCP67 motherboard. A known workaround that sometimes works is to add nolapic to GRUB boot kernel options. acpi=noirq is also known to work. ProblemType: Bug Architecture: amd64 DistroRelease: Ubuntu 8.10 NonfreeKernelModules: wl nvidia Package: usplash 0.5.23 ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: usplash Uname: Linux 2.6.27-3-generic x86_64 -- Possible systems affected include: Nvidia MCP67 Chipset Compaq Presario F700 Compaq Presario F763NR Sony Vaio PCG-GRT-815E - from the Mandriva errata HP Pavilion DV6545eg Notebook - from duplicate HP Pavilion DV6736nr HP Pavilion DV6745us - from a duplicate HP Pavilion DV6620es HP Pavilion DV9610us HP Pavilion DV9700z -- System freezes during boot, unless I hold a key down https://bugs.launchpad.net/bugs/272247 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
Re: [Bug 272247] Re: System freezes during boot, unless I hold a key down
No offense to you sir, but I really wouldn't consider it fixed when the problem is still present in the current official release. The only ways to fix it are to either A) compile the kernel yourself, or B) dist-upgrade to an Alpha testing release. As well, the distro listed when the bug-report was filed is intrepid, not jaunty. As of now, we don't get the 2.6.28 kernel, thus, it is not really fixed at all. On Thu, Jan 15, 2009 at 10:31 AM, Chris Coulson chrisccoul...@googlemail.com wrote: As it appears that this is fixed in Jaunty, I'm going to mark this as fixed. It has already been nominated for Intrepid, so could somebody please add an Intrepid task which we can keep open? Thanks ** Changed in: linux (Ubuntu) Status: Triaged = Fix Released -- System freezes during boot, unless I hold a key down https://bugs.launchpad.net/bugs/272247 You received this bug notification because you are a direct subscriber of the bug. Status in The Linux Kernel: Confirmed Status in Ubuntu Release Notes: New Status in linux source package in Ubuntu: Fix Released Status in usplash source package in Ubuntu: Invalid Status in linux source package in Mandriva: Invalid Bug description: Once the Ubuntu splash screen loads with the progress bar that moves back and forth, it freezes. Holding down any key unfreezes the system, and it continues loading normally, until I release the key, at which point it freezes again. Holding a key down again unfreezes the system again. Pressing Alt+F1 to show the output also freezes, so I know it isn't just the splash screen freezing, but the entire system. Once X loads, it works perfectly fine though, and I don't have to keep holding a key down. Update : This bug happens with 2.6.26 and 2.6.27 kernels with a computer that has Nvidia MCP67 motherboard. A known workaround that sometimes works is to add nolapic to GRUB boot kernel options. acpi=noirq is also known to work. ProblemType: Bug Architecture: amd64 DistroRelease: Ubuntu 8.10 NonfreeKernelModules: wl nvidia Package: usplash 0.5.23 ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: usplash Uname: Linux 2.6.27-3-generic x86_64 -- Possible systems affected include: Nvidia MCP67 Chipset Compaq Presario F700 Compaq Presario F763NR Sony Vaio PCG-GRT-815E - from the Mandriva errata HP Pavilion DV6545eg Notebook - from duplicate HP Pavilion DV6736nr HP Pavilion DV6745us - from a duplicate HP Pavilion DV6620es HP Pavilion DV9610us HP Pavilion DV9700z -- System freezes during boot, unless I hold a key down https://bugs.launchpad.net/bugs/272247 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
Re: [Bug 272247] Re: System freezes during boot, unless I hold a key down
I suppose I jumped the gun a bit and I appologize, I am sure you understand I myself, as well as many others (as you can see by the growing number of posts in this thread), have been dealing with this issue since 8.04 (if I remember correctly). I was under the impression that now that it is marked as fixed according to Jaunty that we will be neglected and forced to suffer through screwy flag fixes until Jaunty becomes official. There have been quite a few bugs in Intrepid that I over-looked because they intended to fix it eventually (Like bluetooth being completely un-usable unless you install the gnome manager). Seems to me that kernel level bugs effecting an entire chipset, plaguing an entire line of laptops (primarily any HP Pavilion laptop with nvidia on board), would be a priority. So long as we aren't dismissed and forgotten, I am content with waiting. Again, I appologize. On Thu, Jan 15, 2009 at 11:44 AM, Andy Whitcroft a...@canonical.com wrote: @SRElysian, @Joschi Holaubek -- I think you have missunderstood. What has happened is the Linux task has been closed. This task _always_ represents the bugs state in the development release, in this case Jaunty. Which as I understand things has the fixes for this issue. There is a nomination for Intrepid which once accepted will become the status for the onging work on this bug. That one is not closed. -- System freezes during boot, unless I hold a key down https://bugs.launchpad.net/bugs/272247 You received this bug notification because you are a direct subscriber of the bug. Status in The Linux Kernel: Confirmed Status in Ubuntu Release Notes: New Status in linux source package in Ubuntu: Fix Released Status in usplash source package in Ubuntu: Invalid Status in linux in Ubuntu Intrepid: New Status in usplash in Ubuntu Intrepid: Invalid Status in linux source package in Mandriva: Invalid Bug description: Once the Ubuntu splash screen loads with the progress bar that moves back and forth, it freezes. Holding down any key unfreezes the system, and it continues loading normally, until I release the key, at which point it freezes again. Holding a key down again unfreezes the system again. Pressing Alt+F1 to show the output also freezes, so I know it isn't just the splash screen freezing, but the entire system. Once X loads, it works perfectly fine though, and I don't have to keep holding a key down. Update : This bug happens with 2.6.26 and 2.6.27 kernels with a computer that has Nvidia MCP67 motherboard. A known workaround that sometimes works is to add nolapic to GRUB boot kernel options. acpi=noirq is also known to work. ProblemType: Bug Architecture: amd64 DistroRelease: Ubuntu 8.10 NonfreeKernelModules: wl nvidia Package: usplash 0.5.23 ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: usplash Uname: Linux 2.6.27-3-generic x86_64 -- Possible systems affected include: Nvidia MCP67 Chipset Compaq Presario F700 Compaq Presario F763NR Sony Vaio PCG-GRT-815E - from the Mandriva errata HP Pavilion DV6545eg Notebook - from duplicate HP Pavilion DV6736nr HP Pavilion DV6745us - from a duplicate HP Pavilion DV6620es HP Pavilion DV9610us HP Pavilion DV9700z -- System freezes during boot, unless I hold a key down https://bugs.launchpad.net/bugs/272247 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
Re: [Bug 272247] Re: System freezes during boot, unless I hold a key down
That's hard to say, from what I read the .28 kernel has some brand-spanking-new stuff in it. Supposedly, it works in Intrepid as is. I've been poking around on random forums and blogs and found that there are quite a few people now who are temporarily adding the Jaunty repos` just long enough to steal the new kernel and it's been working for them. There are a few other's whom compiled the kernel and had success as well. I also heard there may be problems with that new kernel and nvidia drivers, but it may have been remedied. On Thu, Jan 15, 2009 at 1:44 PM, Polygon auroraborea...@adelieland.euwrote: for this to get fixed in intrepid we need to find out what exactly got applied to the .28 kernel that fixed this issue, so they can just apply that patch to the intrepid kernel. I have no idea how to do this, does anyone here know? -- System freezes during boot, unless I hold a key down https://bugs.launchpad.net/bugs/272247 You received this bug notification because you are a direct subscriber of the bug. Status in The Linux Kernel: Confirmed Status in Ubuntu Release Notes: New Status in linux source package in Ubuntu: Fix Released Status in usplash source package in Ubuntu: Invalid Status in linux in Ubuntu Intrepid: New Status in usplash in Ubuntu Intrepid: Invalid Status in linux source package in Mandriva: Invalid Bug description: Once the Ubuntu splash screen loads with the progress bar that moves back and forth, it freezes. Holding down any key unfreezes the system, and it continues loading normally, until I release the key, at which point it freezes again. Holding a key down again unfreezes the system again. Pressing Alt+F1 to show the output also freezes, so I know it isn't just the splash screen freezing, but the entire system. Once X loads, it works perfectly fine though, and I don't have to keep holding a key down. Update : This bug happens with 2.6.26 and 2.6.27 kernels with a computer that has Nvidia MCP67 motherboard. A known workaround that sometimes works is to add nolapic to GRUB boot kernel options. acpi=noirq is also known to work. ProblemType: Bug Architecture: amd64 DistroRelease: Ubuntu 8.10 NonfreeKernelModules: wl nvidia Package: usplash 0.5.23 ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: usplash Uname: Linux 2.6.27-3-generic x86_64 -- Possible systems affected include: Nvidia MCP67 Chipset Compaq Presario F700 Compaq Presario F763NR Sony Vaio PCG-GRT-815E - from the Mandriva errata HP Pavilion DV6545eg Notebook - from duplicate HP Pavilion DV6736nr HP Pavilion DV6745us - from a duplicate HP Pavilion DV6620es HP Pavilion DV9610us HP Pavilion DV9700z -- System freezes during boot, unless I hold a key down https://bugs.launchpad.net/bugs/272247 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 179250] Re: Mass Storage USB device error
I think my post can be ignored and this can be disabled again, I found out later, that while KDE doesn't recognize my mp3 player as a storage device, Amarok (atleast 2.x) detects and allows me to manage it. So long as I use it through Amarok I can put music on it, though I'd prefer to be able to use it as an actual storage device. -- Mass Storage USB device error https://bugs.launchpad.net/bugs/179250 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 272247] Re: System freezes during boot, unless I hold a key down
** Description changed: Once the Ubuntu splash screen loads with the progress bar that moves back and forth, it freezes. Holding down any key unfreezes the system, and it continues loading normally, until I release the key, at which point it freezes again. Holding a key down again unfreezes the system again. Pressing Alt+F1 to show the output also freezes, so I know it isn't just the splash screen freezing, but the entire system. Once X loads, it works perfectly fine though, and I don't have to keep holding a key down. Update : This bug happens with 2.6.26 and 2.6.27 kernels with a computer that has Nvidia MCP67 motherboard. A known workaround that sometimes works is to add nolapic to GRUB boot kernel options. acpi=noirq is also known to work. ProblemType: Bug Architecture: amd64 DistroRelease: Ubuntu 8.10 NonfreeKernelModules: wl nvidia Package: usplash 0.5.23 ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: usplash Uname: Linux 2.6.27-3-generic x86_64 -- Possible systems affected include: - Nvidia MCP67 - HP Pavilion DV6620es - HP Pavillion DV9700z + Nvidia MCP67 Chipset Compaq Presario F700 Compaq Presario F763NR Sony Vaio PCG-GRT-815E - from the Mandriva errata - HP DV6745us - from a duplicate - HP DV6545eg Notebook - from duplicate - HP DV6736nr + HP Pavilion DV6545eg Notebook - from duplicate + HP Pavilion DV6736nr + HP Pavilion DV6745us - from a duplicate + HP Pavilion DV6620es + HP Pavilion DV9610us + HP Pavilion DV9700z -- System freezes during boot, unless I hold a key down https://bugs.launchpad.net/bugs/272247 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 179250] Re: Mass Storage USB device error
Still not fixed as of kernel 2.6.27-9 ** Changed in: linux (Ubuntu) Status: Invalid = New -- Mass Storage USB device error https://bugs.launchpad.net/bugs/179250 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 179250] Re: Mass Storage USB device error
Info: I have a GoGear SA6145/37, and it is experiencing the same problem. I am currently running Kubuntu 8.10 (Intrepid Ibex). I will post any relevant information. ** Linux 2.6.27-9-generic #1 SMP Thu Nov 20 21:57:00 UTC 2008 i686 GNU/Linux ** I pulled the following from lsusb -v Bus 003 Device 006: ID 0471:2002 Philips Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x0471 Philips idProduct 0x2002 bcdDevice1.00 iManufacturer 1 Philips iProduct2 Philips GoGear SA61XX iSerial 3 3730053B95E208051315010209CB bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 39 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 8 Mass Storage bInterfaceSubClass 6 SCSI bInterfaceProtocol 80 Bulk (Zip) iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 10 Device Qualifier (for other device speed): bLength10 bDescriptorType 6 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 bNumConfigurations 1 Device Status: 0x (Bus Powered) ** Here's tail -f /var/log/kern.log ** Upon Plugging it in Dec 31 16:30:41 apoc-mobile kernel: [258952.312061] usb 3-1: new high speed USB device using ehci_hcd and address 7 Dec 31 16:30:42 apoc-mobile kernel: [258952.521551] usb 3-1: configuration #1 chosen from 1 choice Dec 31 16:30:42 apoc-mobile kernel: [258952.522497] scsi10 : SCSI emulation for USB Mass Storage devices Dec 31 16:30:42 apoc-mobile kernel: [258952.523398] usb-storage: device found at 7 Dec 31 16:30:42 apoc-mobile kernel: [258952.523414] usb-storage: waiting for device to settle before scanning Dec 31 16:30:47 apoc-mobile kernel: [258957.520315] usb-storage: device scan complete Dec 31 16:30:52 apoc-mobile kernel: [258963.132059] usb 3-1: reset high speed USB device using ehci_hcd and address 7 Dec 31 16:31:02 apoc-mobile kernel: [258973.376044] usb 3-1: reset high speed USB device using ehci_hcd and address 7 Dec 31 16:31:19 apoc-mobile kernel: [258989.620046] usb 3-1: reset high speed USB device using ehci_hcd and address 7 Dec 31 16:31:19 apoc-mobile kernel: [258989.868369] usb 3-1: reset high speed USB device using ehci_hcd and address 7 Dec 31 16:31:29 apoc-mobile kernel: [259000.112047] usb 3-1: reset high speed USB device using ehci_hcd and address 7 Dec 31 16:31:29 apoc-mobile kernel: [259000.244900] scsi 10:0:0:0: Device offlined - not ready after error recovery ** Upon Disconnection Dec 31 16:31:49 apoc-mobile kernel: [259019.720454] usb 3-1: USB disconnect, address 7 I doubt it matters in this case, but I am using KDE 4.2b2. Other than that, only recommended updates are enabled. Any idea's would be great, I was really looking forward to managing my mp3 player in linux, I suppose I will have to continue with windows XP for now. -- Mass Storage USB device error https://bugs.launchpad.net/bugs/179250 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 179250] Re: Mass Storage USB device error
** Also from hwinfo --disk 31: USB 00.0: 10600 Disk [Created at usb.122] UDI: /org/freedesktop/Hal/devices/usb_device_471_2002_3730053B95E208051315010209CB_if0 Unique ID: KRJj.mU6_6JUAdE3 Parent ID: uIhY.OqydEZZ981A SysFS ID: /devices/pci:00/:00:02.1/usb3/3-1/3-1:1.0 SysFS BusID: 3-1:1.0 Hardware Class: disk Model: Philips GoGear SA61XX Hotplug: USB Vendor: usb 0x0471 Philips Device: usb 0x2002 Philips GoGear SA61XX Revision: 1.00 Serial ID: 3730053B95E208051315010209CB Driver: usb-storage Driver Modules: usb_storage Speed: 480 Mbps Module Alias: usb:v0471p2002d0100dc00dsc00dp00ic08isc06ip50 Driver Info #0: Driver Status: libusual is active Driver Activation Cmd: modprobe libusual Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #40 (Hub) -- Mass Storage USB device error https://bugs.launchpad.net/bugs/179250 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
Re: [Bug 272247] Re: System freezes during boot, unless I hold a key down
Sorry you feel that way gizmoguy, but I am sorry to say the threats of one person aren't going to change anything. I've been using intrepid since beta, and have been dealing with the problem since then. I've been using a boot variable to get around it and the problem itself doesn't really bother me so long as I CAN boot. I also feel that the ability to run KDE 4.2b2 (which I believe runs far better than 4.0-4.1), far out-weighs a small triagable problem. Also, the reason linux is far more stable than windows as a whole, is because they test things before just releasing them, even if a kernel fix has been found they aren't just going to hand it out to the masses without it being released in testing first. Because fixing 1 little problem someone, and causing it to break for many others is unacceptable. I'd suggest you have a little more patience and appreciation for people whom work hard without getting paid to bring such an excellent operating system. And as someone else stated, if you don't like it, try another distro, this board is for bug reports, save the rants for forum trolling please. -- System freezes during boot, unless I hold a key down https://bugs.launchpad.net/bugs/272247 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 272247] Re: System freezes during boot, unless I hold a key down
Just wanted to say I have this same problem with Toshiba Satellite A35-S139 I tried hpet=disable to no avail. Note I also booted with Fedora 10 live cd and it has the same problem. Try acpi=noirq and see if that helps you.That's the one I've been using on my Pavilion dv9610. -- System freezes during boot, unless I hold a key down https://bugs.launchpad.net/bugs/272247 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 250425] Re: zsnes crashes with buffer overflow on startup
Can confirm that http://launchpadlibrarian.net/18798999/zsnes_1.510-0ubuntu1_i386.deb works perfectly fine, however, it is considered a downgrade. $ sudo dpkg --install zsnes_1.510-0ubuntu1_i386.deb dpkg - warning: downgrading zsnes from 1.510-2.1ubuntu1 to 1.510-0ubuntu1. (Reading database ... 192706 files and directories currently installed.) Preparing to replace zsnes 1.510-2.1ubuntu1 (using zsnes_1.510-0ubuntu1_i386.deb) ... Unpacking replacement zsnes ... Setting up zsnes (1.510-0ubuntu1) ... Processing triggers for man-db ... Processing triggers for menu ... Processing triggers for doc-base ... Processing 1 removed doc-base file(s)... Registering documents with scrollkeeper... -- zsnes crashes with buffer overflow on startup https://bugs.launchpad.net/bugs/250425 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 272247] Re: System freezes during boot, unless I hold a key down
I am going to ask a dumb question here, I've done a bit of research but can't seem to find a good explanation as to what the consequences are so I figured I'd ask here just to get the record straight for myself as well as anyone else with this issue trying to get the same information. So far I've seen a few different options that bypass the problem; acpi=off (disables power management completely and I personally wouldn't suggest) acpi=noirq nolapic Which is best to use? All documentation I've found seems to state these 2 things are not the same. At current, I am using the apci=noirq, but I am not sure what that actually does, and if perhaps nolapic would be better. Just figured I'd get the best solution until this problem can be properly fixed as opposed to triaged. -- System freezes during boot, unless I hold a key down https://bugs.launchpad.net/bugs/272247 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 272247] Re: System freezes during boot, unless I hold a key down
rafaeljcg: thanks for the link, it was full of all sorts of useful information and I have bookmarked it accordingly. I found another issue which I suspect may possibly be a result of this on-going bug, however, since I am not sure I was hoping I could get some insight from a few guys frequenting this but report. Since alot of you with this problem seem to have the same chipset (nvidia), I'd like to ask if any of you also have problem with your consoles. CTRL-ALT-F1 - F6 have not worked for me since I installed Intrepid beta. It actually seems to be erratic, while diagnosing the problem I had a few consoles open, tail -f -ing the following log files: /var/log/Xorg.0.log /var/log/kern.log /home/user/.xsession-errors I could not find anything refecting any sort of error when switching to console, however during repeated tests, the console would randomly start working, and then stop working. After a while my keyboard sort-of went hay-wire out requiring a reboot. It seems to me that this apci/lapic issue is the only one plaguing these laptops and I am curious as to whether or not it might be related. I'd be more than happy to provide any alternative log files and information anyone requires, or a link to another bug or perhaps a general you did this wrong, or forgot to do that. I am fresh out of Ideas. My laptop is: HP Pavilion dv9610us (add that to the list of problematic systems if it isn't already (dv9000 series)) gfxcard: nVidia GeForce 7150M @ 1440x900 cpu: AMD Turion(tm) 64 X2 Mobile Technology TL-58 @ 1.9GHZ -- System freezes during boot, unless I hold a key down https://bugs.launchpad.net/bugs/272247 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 272247] Re: System freezes during boot, unless I hold a key down
It had just dawned on me to test my remote last night to find it worked... litterally... once. I have no idea what the deal is there but judging by the last few messages here n there, it seems that this might be tied in to this same on-going issue. I have the dv9610us (Turion64x2, nVidia, etc), can anyone confirm/deny it works with hpet=disabled or apci=noirq .. I tried both, the noirq option let me use it once, the hpet is a no-go for me. Also, it's become a pain to physically test it since HP just inserted a reciever that ties in to KB control mimicing, I can't seem to find a physical port it's attached to, alteast nothing that's labeled to the degree that I could find it by browsing /dev/ which means irdadump is a no-go and lsinput shows nothing useful. Any ideas would be great... I really hate finding malfunctioning hardware.. especially weeks after initial install. -- System freezes during boot, unless I hold a key down https://bugs.launchpad.net/bugs/272247 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 263041] Re: Wine related applications are in Lost Found in K menu.
I too can confirm this, no Wine menu. All Wine apps show in Lost Found, including itself :/ -- Wine related applications are in Lost Found in K menu. https://bugs.launchpad.net/bugs/263041 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 263041] Re: Wine related applications are in Lost Found in K menu.
I found a way to fix it... it turns out that while kde-applications.menu contains the mergedir option, kde4-applications does not, so, I fixed it like so: sudo nano /etc/xdg/menus/kde4-applications.menu or if you are not a console jockey: alt-f2 kdesudo kate /etc/xdg/menus/kde4-applications.menu All the way at the bottom of the file you should find the item, DefaultMergeDirs/. Directly below that add, MergeDirapplications-merged/MergeDir so it should generally look like this: Include And CategoryKDE/Category CategoryCore/Category /And /Include DefaultMergeDirs/ MergeDirapplications-merged/MergeDir MergeFileapplications-kmenuedit.menu/MergeFile After saving you should pretty much immediately see the new Wine menu and sub menu's. Good luck. -- Wine related applications are in Lost Found in K menu. https://bugs.launchpad.net/bugs/263041 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 294316] Re: Kubuntus login manager can not change theme
I can confirm this problem, I started working on tweaking out my kde desktop this morning. I was changing color schemes, icons, etc and decided to switch my login screen to match. Found a couple I wanted to try out but when I tried to install some behavior became erratic. Sometimes there would be a download status bar, sometimes it would appear and disappear very quickly. When I got back to the selection menu none appeared to be installed. Upon checking the menu to see if they were still installed only one had a uninstall status but again, it was not in the selection menu. -- Kubuntus login manager can not change theme https://bugs.launchpad.net/bugs/294316 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 272247] Re: System freezes during boot, unless I hold a key down
I can confirm that acpi=noirq fixes the problem on the HP Pavilion dv9610us. I am starting to notice a trend, heh. I am actually curious to know how many of these plagued pavilion laptops originally had vista on them :P I know mine did, and I was proud to be rid of it. -- System freezes during boot, unless I hold a key down https://bugs.launchpad.net/bugs/272247 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 272247] Re: System freezes during boot, unless I hold a key down
I noticed this seems to be a plague on HP Pavilion laptops. I've been experiencing the same problem on my dv9610us since the install of 8.10 beta (now official). I tested it with acpi=off to find that it booted just fine but no power management with that option (which is no good for a laptop you intend on actually using portably). I will try the acpi=noirq option and wait out a fix. -- System freezes during boot, unless I hold a key down https://bugs.launchpad.net/bugs/272247 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
