[Bug 71415] Re: Device (ppp0) Not recognized until connecting
Sorry, this bug is ancient to me, I currently have no way to test this. -- Device (ppp0) Not recognized until connecting https://bugs.launchpad.net/bugs/71415 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 47808] Re: if computer hangs, sl-modem-daemon looses internet
I can completely confirm this, WvDial eventually kills with an error 15. --> Disconnecting at Sat Nov 11 17:22:24 2006 --> The PPP daemon has died: Lack of LCP echo responses (exit code = 15) --> man pppd explains pppd error codes in more detail. --> I guess that's it for now, exiting --> Provider is overloaded(often the case) or line problem. --> The PPP daemon has died. (exit code = 15) Now normally it could just be a crappy ISP posing the issue, but it's too conveniently timed after intensive CPU or disk use. this may also have to do with the slmodem-daemon locking up entirely requiring a few lines of command or a restart. -- if computer hangs, sl-modem-daemon looses internet https://launchpad.net/bugs/47808 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 71415] Device (ppp0) Not recognized until connecting
Public bug reported: This should theoretically effect all SL-Modem Dialup users. I found that the device isn't found in, say, Network Monitor 2.12.0. Until it actually is connected (the information send phase.) Where other devices, even as compared to a friend with a hard-modem are recognized all the time. Does it pose much of an issue? Not per se. But for these run on startup (Firewalls and such) It could prove mildly bothersome. ** Affects: sl-modem (Ubuntu) Importance: Undecided Status: Unconfirmed -- Device (ppp0) Not recognized until connecting https://launchpad.net/bugs/71415 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 190615] Re: Sticking Keys
** Changed in: compiz Status: New => Confirmed -- Sticking Keys https://bugs.launchpad.net/bugs/190615 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 193376] [NEW] Init reports 'failed' on boot, but starts properly
Public bug reported: Binary package hint: clutch Pretty simple issue, essentially on boot the Clutch init node will run and report that it has failed, on inspection after boot finishes, you can clearly see that the daemon has in fact started properly. Status works fine, and reports it all fine; presumably it is just an issue with the init script. My best guess being that it checks before the daemon has time to properly start. ** Affects: clutch (Ubuntu) Importance: Undecided Status: Confirmed -- Init reports 'failed' on boot, but starts properly https://bugs.launchpad.net/bugs/193376 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 130325] Re: [nvidia-glx-new] glxgears, 3d apps crash X when using compiz-fusion (gutsy)
Agreed, still broken. -- [nvidia-glx-new] glxgears, 3d apps crash X when using compiz-fusion (gutsy) https://bugs.launchpad.net/bugs/130325 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 130325] Re: [nvidia-glx-new] 3D GL apps crash X when using compiz (gutsy)
Sorry, this was reinstated the *25th*, not the 15th. -- [nvidia-glx-new] 3D GL apps crash X when using compiz (gutsy) https://bugs.launchpad.net/bugs/130325 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 130325] Re: [nvidia-glx-new] 3D GL apps crash X when using compiz (gutsy)
Well this got more complicated... apparently this patch has gone upstream, and is required to make a few new things function. I was skimming the update/patch logs. This patch was removed early July (13th- ish?) and reinstated the 15th "fixed" no specific mentions of nvidia, but it was removed for some compiz issues, and re-added when the compiz issues were supposedly gone. Now this is interesting... short term, we could sort of weigh the options and maybe remove the patch from the build cycle, long term (next release) if this isn't fixed and we get the new upstream with this patch without it being fixed, it's far more annoying. So this is just getting rather crazy... Now when other peopel start using this patch, or start using the new upstream all applicable distros will see it, and no way it'd go unpatched for long. But it comes down to this: It seems like in fixing a bug on our end, we exposed a great nvidia end bug... We could work aroudn this more properly, or we could leave it in the main distro tree to try and pressure nvidia to fix it (they really have no reason to listen, in all honesty) I'm sure nVidia would eventually fix their end of it. But until then... heres what we can do: 1) if the options are weighed in the favor of Compiz support (realistically, almost everyone uses some form of compositing with ubuntu these days, if they can, it's just so easy for light effects to be done) then we will patch this back out of upstream/remove the current patch from the build tree, and there we go. 2) We decide that we shouldn't have to work around somethign we believe to be nvidia end in a grand stance against closed source software! (Sure it'll work well, nvidia will find the err in their ways, and whathaveyou, of course they will) Then I would recommend someone who knows X well to build a semi-official or 3rd party package to fix this (build it without the patch) and distribute it in some repository, and make it accessible, seems like something that might be fit for trevs Gutsy repo (getting in to the whole of package semantics later on) Honestly, It's a big thing to just say "No we won't do things hackishly for you Mr. nVidia!" to essentially break use of Compiz with anything remotely useful in gutsy final. Does anyone have the guts to tell people, specifically new users, that because of politics (mainly anywho), they will have to compile a copy of xserver themselves, or uninstall the current and replace it with an off named X which will crap out their metas, and so on. That's a lot to say! I know it's not *only* politics, the patch was commited for a reason, but there we have it. X crashing Vs. a few things working properly otherwise (from what I hear about the patch, don't quote me on that.) -- [nvidia-glx-new] 3D GL apps crash X when using compiz (gutsy) https://bugs.launchpad.net/bugs/130325 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 130325] Re: glxgears, 3d apps, crash X when using compiz-fusion (gutsy) (nvidia-glx-new 9755)
It's not a nvidia issue really, as using the same version across Feisty and gutsy produce very different results (Feisty works, Gutsy doesn't) So let's dispell that idea now. It's either X itself in some way, or compiz. Most realistically I would say X in some form. -- glxgears, 3d apps, crash X when using compiz-fusion (gutsy) (nvidia-glx-new 9755) https://bugs.launchpad.net/bugs/130325 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 130325] Re: glxgears, 3d apps, crash X when using compiz-fusion (gutsy) (nvidia-glx-new 9755)
Sitsofe: Yea, I meant to cover most of that. That's why I was saying it was most realistically not a Compiz problem, that wouldn't make a ton of sense for it to be. And I'm in the same position, testing across multiple nvidia versions (compatible with the environment of feisty entirely) so that can all but alleviate any thoughts that it might be trouble with the nvidia binary and pretty much throws it to something happening differently in X or in that ballpark. Obviously somehow having to do with rendering opengl separately as compiz is flying. It might ven be an issue of either the resolution of the render (which is odd, not entirely off the hat though), or a matter of how much it renders (which would in part tie in to part a there). I say this becuase it seems smaller render jobs, windowed things even, work to some degree for many people. For me I can play a windowed wine game for the most part fine, where as mythfrontend crashes X, assuming the full 3d game in a window takes more actual rendering I'm leaning towards the weird but not implausible that it's in relation to rendering size (this same game crashing in fullscreen mode.) -- glxgears, 3d apps, crash X when using compiz-fusion (gutsy) (nvidia-glx-new 9755) https://bugs.launchpad.net/bugs/130325 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 130325] Re: [nvidia-glx] 3D GL apps crash X when using compiz due to unmaked ABI change (gutsy)
You miss the point... if we were to work around it on our end it wouldn't be a matter of having a new nvidia driver package, with as much as we can do it has *nothing* to do with the nvidia driver (As said, with as much as we can do, it is a nvidia problem) The only multi package solution would to have xserver-xorg-mobile or something and the mainline not having the patch. Which is only a shortterm fix, as this patch is now upstream. ChrisC wrote: > making compiz enabled by default with this issue *regardless* of blame > would be disastrous and could seriously dent efforts to correct bug #1 > it could even mean Ubuntu becoming a minor bit player of distros... > > Is this *defiantly* an nvidia bug, are people really sure that there isnt > a bug with the clipping patch for xorg? > > Can the clipping patch not be altered to take into account nvidia > drivers? > > theres a legacy nvidia an open source nvidia an older nvidia and > an nividia-glx-new driver why not an nvidia-mobile driver too :o) > > enabling compiz by default with this bug could kill Ubuntu. > This needs sorting *well* before November October is only > a few weeks away... > > 3vi1 wrote: > >> I hope nVidia gets on the ball and releases a new driver in time for >> everyone to test before Gutsy final (now that it has been voted that >> Compiz will be enabled by default). If they don't, I think Gutsy will >> end up looking very unstable to users unfamiliar with the underlying >> causes. >> >> I have this problem on my 7600GT-based system and it's getting annoying >> to switch window managers every time I want to run an OpenGL app. I do >> *not* hope the 'buntu maintainers build Xorg without patch 132 as a >> workaround though, as that completely removes all incentive for nVidia >> to fix the real problem. >> >> In answer to Sitsofe's ABI observation, I would think that nVidia would >> simply put an item in the release notes indicating that the newer driver >> is only for Xorg (insert version # / patch level here) and later. It >> would be up to the repackagers to set dependencies for each version to >> their related Xorg packages. >> >> -J >> >> >> > > -- [nvidia-glx] 3D GL apps crash X when using compiz due to unmaked ABI change (gutsy) https://bugs.launchpad.net/bugs/130325 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 130325] Re: [nvidia-glx] 3D GL apps crash X when using compiz due to unmaked ABI change (gutsy)
What you describe *is* compiz fusion. And it's not that simple, first it's something we added in to fix another issue, second realistically it's nvidia at fault... Do I condone us taking the highroad and leaving it in so nvidia will fix it's issue... I'm torn. I don't think they'll learn anything, but at the same time we shouldn't hack alternate fixes for their blunder. This is an upstream patch now, they have to get their blob to work with it or it simply... well won't work. wgscott wrote: > Even without Compiz (or Beryl), the same problem arises if you turn > desktop effects compositing on (drop shadow on windows and so forth). > > May I humbly suggest the offending patch simply be removed? > > > ChrisC wrote: > >> making compiz enabled by default with this issue *regardless* of blame >> would be disastrous and could seriously dent efforts to correct bug #1 >> it could even mean Ubuntu becoming a minor bit player of distros... >> >> Is this *defiantly* an nvidia bug, are people really sure that there isnt >> a bug with the clipping patch for xorg? >> >> Can the clipping patch not be altered to take into account nvidia >> drivers? >> >> theres a legacy nvidia an open source nvidia an older nvidia and >> an nividia-glx-new driver why not an nvidia-mobile driver too :o) >> >> enabling compiz by default with this bug could kill Ubuntu. >> This needs sorting *well* before November October is only >> a few weeks away... >> >> 3vi1 wrote: >> >>> I hope nVidia gets on the ball and releases a new driver in time for >>> everyone to test before Gutsy final (now that it has been voted that >>> Compiz will be enabled by default). If they don't, I think Gutsy will >>> end up looking very unstable to users unfamiliar with the underlying >>> causes. >>> >>> I have this problem on my 7600GT-based system and it's getting annoying >>> to switch window managers every time I want to run an OpenGL app. I do >>> *not* hope the 'buntu maintainers build Xorg without patch 132 as a >>> workaround though, as that completely removes all incentive for nVidia >>> to fix the real problem. >>> >>> In answer to Sitsofe's ABI observation, I would think that nVidia would >>> simply put an item in the release notes indicating that the newer driver >>> is only for Xorg (insert version # / patch level here) and later. It >>> would be up to the repackagers to set dependencies for each version to >>> their related Xorg packages. >>> >>> -J >>> >>> >>> >> -- >> [nvidia-glx] 3D GL apps crash X when using compiz due to unmaked ABI >> change (gutsy) >> https://bugs.launchpad.net/bugs/130325 >> You received this bug notification because you are a direct subscriber >> of the bug. >> >> > > -- [nvidia-glx] 3D GL apps crash X when using compiz due to unmaked ABI change (gutsy) https://bugs.launchpad.net/bugs/130325 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 130325] Re: [nvidia-glx] 3D GL apps crash X when using compiz due to unmaked ABI change (gutsy)
You used the Bulletproof X Xorg.conf... not a bright idea =] sudo dpkg-reconfigure xserver-xorg Duncan Lithgow wrote: > Okay, so installing xserver-xorg-core-dbg was dumb. Now I've tried > xserver-xorg-core and I'm in real trouble. It lost the screen resolution > and keymap setting (dk). I reinstalled the original xserver-xorg-core > package and put X11's backup (xorg.conf.broken) back in place as > xorg.conf. I still have a resolution of 640xsomething and a broken > keymap. Can someone help me re run the original config script to make my > desktop usable again? Attached is my current xorf.conf file. > > ** Attachment added: "xorg.conf" >http://launchpadlibrarian.net/9293530/xorg.conf > > -- [nvidia-glx] 3D GL apps crash X when using compiz due to unmaked ABI change (gutsy) https://bugs.launchpad.net/bugs/130325 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 130325] Re: [nvidia-glx] Don't enable compiz by default for gutsy
These unrelated problems may happen to you, but things like freezing out temporarily don't happen to everyone.. Your own logic can be turned around.. Those who don't want it can easily turn it off =] This problem will be fixed with the next nvidia release which will most assuredly have to be passed back in to gutsy, even if hardy work has started. David Megginson wrote: > I'm an experienced user (Linux since 1993, Minix before that), but I > lost several hours before I realized that glxgears and FlightGear were > crashing X due to compiz. I *strongly* recommend disabling compiz by > default in gutsy, since it provides nothing but eye candy, and having it > running means that 3D apps will crash X by default in gutsy for all > boxes running new NVIDIA cards -- it's easy enough to enable in the GUI > for people who want it. Functionality should always win over flash. > > Even when I'm not trying to run 3D apps, compiz seems very awkward on my > new HP TX1220 compared with metacity -- there are sometimes freezes of > several seconds, for example, especially when I'm trying to edit in > OpenOffice. It may be cute, but it's not practical. > > -- [nvidia-glx] 3D GL apps crash X when using compiz due to unmaked ABI change (gutsy) https://bugs.launchpad.net/bugs/130325 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 130325] Re: [nvidia-glx] 3D GL apps crash X when using compiz due to unmaked ABI change (gutsy)
Nah most users just disable it rather than uninstall it, as with all of the base system. ChrisC wrote: > Well personally I've enabled the package popularity contest > ( sudo dpkg-reconfigure popularity-contest ) > > and uninstalled compiz completely (the dependencies still > let you for now) *maybe* someone looks at the stats > and *maybe* enough people will get sick of eye candy > killing xwindows and uninstall compiz > > Over the last year Vista has been doing Ubuntu lots of favours > I guess in November its going to be Ubuntu's turn to pay the > favour back > > > Richard Ayotte wrote: > >> I'm also an experienced user with the same problems. Are these problems >> difficult to identify because we don't have the driver source code? >> Either way, the desktop effects are not stable with the current nVidia >> drivers so unless that gets resolved soon, I think that enabling them by >> default is not very wise. >> >> >> > > -- [nvidia-glx] 3D GL apps crash X when using compiz due to unmaked ABI change (gutsy) https://bugs.launchpad.net/bugs/130325 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 130325] Re: [nvidia-glx] 3D GL apps crash X when using compiz due to unmaked ABI change (gutsy)
This is getting rather off topic, this is not a discussion about Compiz Fusion by default, this is a discussion about this issue, and solutions to it. While I would agree it's not outside the scope to talk a bit about how this effects us with compiz by default, your voice will not be heard by the right people here. Kristoffer Lundén wrote: > That's not how it works. This bug will cause loss of work and data to a > large part of the userbase, which may have no clue that this can happen, > why it happens or how to work around it. At the same time, those who > think it is really important to have bling will find and turn this > feature on. I've never understood why a vocal minority that will enable > this manually anyways thinks it's so important that everyone else must > have their pet feature forced on them by default? > > I'm all for composite being the default once it is stable and polished > (not worse than metacity, which it is in many cases right now even > though it is better in other parts). > > Doesn't really matter if this is a closed source issue, people will lose > work and data if this goes out by default as it is now. Is that worth it > so some other people can have a fireworks show? Really? > > -- [nvidia-glx] 3D GL apps crash X when using compiz due to unmaked ABI change (gutsy) https://bugs.launchpad.net/bugs/130325 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 130325] Re: [nvidia-glx] Don't enable compiz by default for gutsy
Again see my last reply there, but this again is straying off topic. My understanding is that the system will actually be checked for proper compatibility before all of this. Worst case, it tries to start up, X dies, and restarts in Compatibility mode, Compiz is disabled, and all's fine, but the regular check should catch most things, so no worries =] David Megginson wrote: > On 17/09/2007, Bryan Haskins <[EMAIL PROTECTED]> wrote: > > >> These unrelated problems may happen to you, but things like freezing out >> temporarily don't happen to everyone.. Your own logic can be turned >> around.. Those who don't want it can easily turn it off =] This problem >> will be fixed with the next nvidia release which will most assuredly >> have to be passed back in to gutsy, even if hardy work has started. >> > > Reversing the logic doesn't work, because in one configuration, gutsy > will won't work out of the box for a lot of people, while in the > second configuration, it will. Why not wait until there are fixed > nvidia drivers in gutsy to make compiz the default? BTW, search for > "compiz freeze" to find people with the other problem -- you don't > need *everyone* to be having the problem, just a significant number, > for Ubuntu to start losing its excellent reputation as the distro that > actually works out of the box. > > Stacked up against all this, what real benefits do we get from forcing > compiz in before the distro is stable with it? Cute window > animations? > > > All the best, > > > David > > -- [nvidia-glx] 3D GL apps crash X when using compiz due to unmaked ABI change (gutsy) https://bugs.launchpad.net/bugs/130325 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 130325] Re: [nvidia-glx] 3D GL apps crash X when using compiz due to unmaked ABI change (gutsy)
Exactly =] But it's unlikely the package will be taken in to gutsy, all it does afaik is remove the patch with causes incompatibility, this patch is needed for mobile devices, as said earlier in the bug chatter. Technically it's not something we should work around. though for the sake of a good user product... well it's complicated. Essentially until nvidia updates you will see user rolled xorg packages floating around, so in main we have the xorg which pressures, to whatever level they choose to ignore, nvidia in to updating. Is it a pita for new users? Totally. But in the end it will get the job done, which is fixing the driver, not working around it to break other things that we've developed. Ralf Nieuwenhuijsen wrote: > Maybe I am missing the point .. > > 1) Compiz is not on by default for NVidia > > But if you own an Nvidia card, then there is no compiz by default! > Why do people insist on claiming that there is? > > You are M-A-N-U-A-L-L-Y installing an U-N-S-U-P-P-O-R-T-E-D driver. > After which compiz is enabled by default, because the driver _claims_ it > supports 3d. > Unfortunately this driver is incompatible with the particular XServer of > Gutsy, hence the driver crashes. > If this is not fixed before gutsy launch, i'm pretty sure nvidia will be on > the blacklist and compiz will not be enabled for Nvidia users. > > No freaking reason to disable compiz for Intel videocards, because > Nvidia won't work. That makes no sense. > > 2) There is test package of xserver that FIXES those issues. If you > bother to read the whole thread you would know that. You can test that > package yourself. The more people that claim that it 'works' .. the more > likely the patch will be included in gutsy. > > When the patch is included in gutsy and it fixes the problem, then > nvidia won't need to be blacklisted. > > 3) There are valid arguments against enabling compiz by default for > anyone. But this aint one of them. This is nvidia-specific crashes, for > which a working patch exists, that have got nothing to do with compiz. > > Stop the FUD please. > > -- [nvidia-glx] 3D GL apps crash X when using compiz due to unmaked ABI change (gutsy) https://bugs.launchpad.net/bugs/130325 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 130325] Re: [nvidia-glx] 3D GL apps crash X when using compiz due to unmaked ABI change (gutsy)
Calm down, we're not here to talk about anything beyond the scope of the bug. None of us mind listening, but you're really not telling the right people. The issue at hand is just a temporary one. (Presumably) when nvidia reaches xorg compatibility this should be no issue now that it's upstream. ChrisC wrote: > I am using said patch, it does *not* solve all the problems > I'm experiencing, I have already posted to say it fixes > *one* problem > > regardless of blame, uninstalling compiz solves all my issues > > Who said anything about intel cards? > > To reiterate the patch (actually 1 less patch in xorg) > doesn't solve *ALL* problems I'm having with > compiz with an nvidia card > > Disabling or uninstalling compiz *does* > > I care not whos "fault" it is or the politics > compiz+xorg+nvidia glx is NOT production ready > > > Ralf Nieuwenhuijsen wrote: > >> Maybe I am missing the point .. >> >> 1) Compiz is not on by default for NVidia >> >> But if you own an Nvidia card, then there is no compiz by default! >> Why do people insist on claiming that there is? >> >> You are M-A-N-U-A-L-L-Y installing an U-N-S-U-P-P-O-R-T-E-D driver. >> After which compiz is enabled by default, because the driver _claims_ it >> supports 3d. >> Unfortunately this driver is incompatible with the particular XServer of >> Gutsy, hence the driver crashes. >> If this is not fixed before gutsy launch, i'm pretty sure nvidia will be on >> the blacklist and compiz will not be enabled for Nvidia users. >> >> No freaking reason to disable compiz for Intel videocards, because >> Nvidia won't work. That makes no sense. >> >> 2) There is test package of xserver that FIXES those issues. If you >> bother to read the whole thread you would know that. You can test that >> package yourself. The more people that claim that it 'works' .. the more >> likely the patch will be included in gutsy. >> >> When the patch is included in gutsy and it fixes the problem, then >> nvidia won't need to be blacklisted. >> >> 3) There are valid arguments against enabling compiz by default for >> anyone. But this aint one of them. This is nvidia-specific crashes, for >> which a working patch exists, that have got nothing to do with compiz. >> >> Stop the FUD please. >> >> >> > > -- [nvidia-glx] 3D GL apps crash X when using compiz due to unmaked ABI change (gutsy) https://bugs.launchpad.net/bugs/130325 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 130325] Re: [nvidia-glx] Don't enable compiz by default for gutsy
Hmm really? I hadn't been testing, it was planned. David Megginson wrote: > On 17/09/2007, Bryan Haskins <[EMAIL PROTECTED]> wrote: > > >> Again see my last reply there, but this again is straying off topic. My >> understanding is that the system will actually be checked for proper >> compatibility before all of this. Worst case, it tries to start up, X >> dies, and restarts in Compatibility mode, Compiz is disabled, and all's >> fine, but the regular check should catch most things, so no worries =] >> > > It's not checked now. Does someone plan to implement that in gutsy in > the next four weeks, or is there already a feature freeze? > > > All the best, > > > David > > -- [nvidia-glx] 3D GL apps crash X when using compiz due to unmaked ABI change (gutsy) https://bugs.launchpad.net/bugs/130325 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 130325] Re: glxgears, 3d apps, crash X when using compiz-fusion (gutsy) (nvidia-glx-new 9755)
The NvAGP idea was no go, though I expected little from that. -- Cheers, Bryan -- glxgears, 3d apps, crash X when using compiz-fusion (gutsy) (nvidia-glx-new 9755) https://bugs.launchpad.net/bugs/130325 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 130914] Re: [Compiz/nvidia-glx-new]Running glxgears while using compiz restarts x
*** This bug is a duplicate of bug 130325 *** https://bugs.launchpad.net/bugs/130325 Now we're getting somewhere. Can we get more conformation from the ATI crowd? If it's occurring across both drivers we can lean more towards my original thought that it's more related to X than the proprietary drivers, if this is happening to anyone using the OSS ATI drivers, that would be good to hear about. -- [Compiz/nvidia-glx-new]Running glxgears while using compiz restarts x https://bugs.launchpad.net/bugs/130914 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 135142] Re: [nvidia-glx] Any glx application make X server crash when compiz is runing [Gutsy][aiglx]
Anyone going to take this up? Much more information in the previously linked Bugs which this is a duplicate of. I'd say X restarting silently for anyone using nVidia and even the lightest default compositing would be a big issue. -- [nvidia-glx] Any glx application make X server crash when compiz is runing [Gutsy][aiglx] https://bugs.launchpad.net/bugs/135142 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 178817] Re: software sticky key issue in x
This is a rather serious bug, it does not only point to wine, but rather X11 as a whole, something is off here causing the issue. I'm refiling this as an X bug, so it can get the proper attention. -- software sticky key issue in x https://bugs.launchpad.net/bugs/178817 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 190615] [NEW] Sticking Keys
Public bug reported: Binary package hint: xorg This was originally filed as a Wine bug, but I have recently determined it to be a more general bug in X, if someone can prove it otherwise, please do, do help narrow things down. Anyway, occasionally when in an OpenGL application, Games, for instance... a Button with magically begin to repeat itself, as if being held down. It could be the up arrow, 1, 2, w, q, z, whatever, it's a general issue. It rarely happens right off, but seems entirely random when it occurs. It has been seen in both native and non-native (non- native-ish (wine)) OpenGL applications, and is becoming a real plague to gaming. I can't offer very much specific information, I mean this is a hard thing to trace. Myself I mainly see it in Wine, but that is where I spend most of my time as far as gaming goes, and it has been witnessed by others in native applications, and found true by myself in trials. After closing the application in question, the key remains repeating, sticking, if you will. For example, if it were the 'up' key, and I made it back to my terminal, the behavior would be scrolling through my type history. you get the idea on how that works most likely. ** Affects: xorg (Ubuntu) Importance: Undecided Status: New -- Sticking Keys https://bugs.launchpad.net/bugs/190615 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 178817] Re: software sticky key issue in x
See https://bugs.edge.launchpad.net/ubuntu/+source/xorg/+bug/190615 -- software sticky key issue in x https://bugs.launchpad.net/bugs/178817 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 190615] Re: Sticking Keys
** Changed in: xorg (Ubuntu) Status: New => Confirmed -- Sticking Keys https://bugs.launchpad.net/bugs/190615 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 190615] Re: Sticking Keys
Makes sense, it's probably not directly an issue with 3D, but simply shows up there more often do to button mashing. Maybe it's something to do with that, as it's almost always my arrow keys while in a game, those are generally pressed frequently, or held for long period of time, most frequently it is "up" which is simply held most times. Assuming your issues are the same, which it seems at least crazily similar, we can rule it out as an nVidia bug. -- Sticking Keys https://bugs.launchpad.net/bugs/190615 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 185697] Re: skydome image not appearing
what type of file is the image? Do you have the corresponding plugin for that image type enabled. -- skydome image not appearing https://bugs.launchpad.net/bugs/185697 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 190615] Re: Sticking Keys
This is *not* a duplicate. the issue is at least similar. the other user experiences sticking that goes away. I've had sticking continue through a several hour session of regular use. At any rate this bug was filed before it (note the bug id), and therefore impossible to be a duplicate. Furthermore, this should not have been marked invalid for compiz. Compiz is the only WM in which this issue occurs, be it another 3D WM, or basic. I cannot verify with all certainty it is a compiz issue, but likewise can no one disprove it yet. ** This bug is no longer a duplicate of bug 194214 Keys get "stuck" down -- Sticking Keys https://bugs.launchpad.net/bugs/190615 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 190615] Re: Sticking Keys
Duplicate status removed. -- Sticking Keys https://bugs.launchpad.net/bugs/190615 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 190615] Re: Sticking Keys
There is no proof thus far that this is not a Compiz issue. (See second to last comment of mine, second paragraph) ** Changed in: compiz Status: Invalid => New ** Changed in: xorg (Ubuntu) Status: New => Confirmed -- Sticking Keys https://bugs.launchpad.net/bugs/190615 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 190615] Re: Sticking Keys
And just to clarify, sorry for the multi-spam, had another thought, Thought this has been reported in WMs other than compiz, it has not yet been confirmed with all certainty. As soon as that happens, more than happy to invalidate that part of the issue. Need some more input. -- Sticking Keys https://bugs.launchpad.net/bugs/190615 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 190615] Re: Sticking Keys
** Changed in: xorg-server (Ubuntu) Status: Incomplete => Fix Released ** Changed in: compiz Status: New => Invalid -- Sticking Keys https://bugs.launchpad.net/bugs/190615 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 117256] Re: Thats What She Said!
No it isn't. -- Thats What She Said! https://bugs.launchpad.net/bugs/117256 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 120681] Re: Google Bookmark don't load with Firefox on Kubuntu Feisty
This also occurs for me on gutsy. I tried removing the extensioon/reinstallling for the sake of argument as well. -- Google Bookmark don't load with Firefox on Kubuntu Feisty https://bugs.launchpad.net/bugs/120681 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 120681] Re: Google Bookmark don't load with Firefox on Kubuntu Feisty
In talking with people it seems as though google has changed the way the data must be called, and hasn't updated their firefox extension yet. This seems like it's nothing to do with us at all now. -- Google Bookmark don't load with Firefox on Kubuntu Feisty https://bugs.launchpad.net/bugs/120681 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 96606] Re: restricted-manager doesn't detect ATI card
This kind of goes under the heading of: https://launchpad.net/ubuntu/+source/restricted-manager/+bug/96500 https://launchpad.net/ubuntu/+source/restricted-manager/+bug/95779 But it's not really a dupe, marking it as a dupe would slide it under the rug, but I suppose the coders for the manager need to know what isn't properly identified or detected. -- restricted-manager doesn't detect ATI card https://launchpad.net/bugs/96606 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 96612] Re: bootchart depends on java-gcj-compat
*** This bug is a duplicate of bug 81431 *** This is actually a dupe of a rather ancient bug. ** This bug has been marked a duplicate of bug 81431 Please add optional dependency on java2-runtime -- bootchart depends on java-gcj-compat https://launchpad.net/bugs/96612 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 96612] Re: bootchart depends on java-gcj-compat
*** This bug is a duplicate of bug 81431 *** I can confirm that as well for Feisty, shouldn't this be a needs x *or* y thing? -- bootchart depends on java-gcj-compat https://launchpad.net/bugs/96612 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 96619] Re: add-on update crashed firefox
That soundsl iek it would be an upstream thing, can anyone confirm? -- add-on update crashed firefox https://launchpad.net/bugs/96619 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 81173] Gaim Beta 6 Crashes Instantly
Public bug reported: Binary package hint: gaim As of 01/22/07 Dist-Upgrade Gaim is broke and crashes instantly on boot with a terminal output of: symbol lookup error: gaim: undefined symbol: gaim_prefs_add_path Applicable upgrades for 01/23/07 don't seem to fix this problem. ** Affects: gaim (Ubuntu) Importance: Undecided Status: Unconfirmed -- Gaim Beta 6 Crashes Instantly https://launchpad.net/bugs/81173 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 81173] Re: Gaim Beta 6 Crashes Instantly
Okay I just tested another compilation of Beta 6 and it does it for me from that too.. So either it's local configuration (not the dot files, tried with and without in home dir), or some type of upstream bug, but the fact that no one has confirmed it and everyone on IRC says it works fine for them, is rather odd. -- Gaim Beta 6 Crashes Instantly https://launchpad.net/bugs/81173 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 81173] Re: Gaim Beta 6 Crashes Instantly
It's not a plugin thing, Like I said I've tried without the dot files, and it doesn't even get to the stage of remaking the config dir. So it's dying at a really early stage. and there is no backtrace output. -- Gaim Beta 6 Crashes Instantly https://launchpad.net/bugs/81173 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 81173] Re: Gaim Beta 6 Crashes Instantly
Rolled back to Beta 5 and it works fine... so that eliminates a lot of possibilities. -- Gaim Beta 6 Crashes Instantly https://launchpad.net/bugs/81173 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 81173] Re: Gaim Beta 6 Crashes Instantly
Nice and long so I'll add my comments beforehand, Reverting to Beta 5 worked fine for me for now, excluding the known upstream bugs in it like the crashes with text floods, etc. But anyway 5 works fine, so unless alot of the structure had changed since then upstream (I tried a 3rd party deb with the same results) I can't really see what's going on. Anyway, the printout: $ ldd $(which gaim) linux-gate.so.1 => (0xe000) libgstreamer-0.10.so.0 => /usr/lib/libgstreamer-0.10.so.0 (0xb7e96000) libXss.so.1 => /usr/lib/libXss.so.1 (0xb7e93000) libgtkspell.so.0 => /usr/lib/libgtkspell.so.0 (0xb7e8d000) libstartup-notification-1.so.0 => /usr/lib/libstartup-notification-1.so.0 (0xb7e85000) liblaunchpad-integration.so.0 => /usr/lib/liblaunchpad-integration.so.0 (0xb7e81000) libgtk-x11-2.0.so.0 => /usr/lib/libgtk-x11-2.0.so.0 (0xb7b29000) libgdk-x11-2.0.so.0 => /usr/lib/libgdk-x11-2.0.so.0 (0xb7aa3000) libatk-1.0.so.0 => /usr/lib/libatk-1.0.so.0 (0xb7a87000) libgdk_pixbuf-2.0.so.0 => /usr/lib/libgdk_pixbuf-2.0.so.0 (0xb7a7) libpango-1.0.so.0 => /usr/lib/libpango-1.0.so.0 (0xb7a32000) libgobject-2.0.so.0 => /usr/lib/libgobject-2.0.so.0 (0xb79f8000) libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0xb7963000) libgaim.so.0 => /lib/libgaim.so.0 (0xb78bc000) libSM.so.6 => /usr/lib/libSM.so.6 (0xb78b2000) libICE.so.6 => /usr/lib/libICE.so.6 (0xb789a000) libX11.so.6 => /usr/lib/libX11.so.6 (0xb77cf000) libpthread.so.0 => /lib/tls/i686/cmov/libpthread.so.0 (0xb77b8000) libm.so.6 => /lib/tls/i686/cmov/libm.so.6 (0xb7791000) libc.so.6 => /lib/tls/i686/cmov/libc.so.6 (0xb765) libgthread-2.0.so.0 => /usr/lib/libgthread-2.0.so.0 (0xb764a000) librt.so.1 => /lib/tls/i686/cmov/librt.so.1 (0xb7641000) libgmodule-2.0.so.0 => /usr/lib/libgmodule-2.0.so.0 (0xb763e000) libdl.so.2 => /lib/tls/i686/cmov/libdl.so.2 (0xb763a000) libxml2.so.2 => /usr/lib/libxml2.so.2 (0xb752) libXext.so.6 => /usr/lib/libXext.so.6 (0xb7512000) libpangocairo-1.0.so.0 => /usr/lib/libpangocairo-1.0.so.0 (0xb7509000) libfontconfig.so.1 => /usr/lib/libfontconfig.so.1 (0xb74de000) libXinerama.so.1 => /usr/lib/libXinerama.so.1 (0xb74db000) libXi.so.6 => /usr/lib/libXi.so.6 (0xb74d3000) libXrandr.so.2 => /usr/lib/libXrandr.so.2 (0xb74d) libXcursor.so.1 => /usr/lib/libXcursor.so.1 (0xb74c6000) libXfixes.so.3 => /usr/lib/libXfixes.so.3 (0xb74c1000) libcairo.so.2 => /usr/lib/libcairo.so.2 (0xb7456000) libXrender.so.1 => /usr/lib/libXrender.so.1 (0xb744e000) libaspell.so.15 => /usr/lib/libaspell.so.15 (0xb7398000) libdbus-glib-1.so.2 => /usr/lib/libdbus-glib-1.so.2 (0xb737c000) libdbus-1.so.3 => /usr/lib/libdbus-1.so.3 (0xb734a000) libnsl.so.1 => /lib/tls/i686/cmov/libnsl.so.1 (0xb7333000) libresolv.so.2 => /lib/tls/i686/cmov/libresolv.so.2 (0xb732) libXau.so.6 => /usr/lib/libXau.so.6 (0xb731d000) libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0xb7317000) /lib/ld-linux.so.2 (0xb7f3e000) libz.so.1 => /usr/lib/libz.so.1 (0xb7303000) libpangoft2-1.0.so.0 => /usr/lib/libpangoft2-1.0.so.0 (0xb72d8000) libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0xb726e000) libexpat.so.1 => /usr/lib/libexpat.so.1 (0xb724f000) libpng12.so.0 => /usr/lib/libpng12.so.0 (0xb722b000) libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0xb7141000) libgcc_s.so.1 => /lib/libgcc_s.so.1 (0xb7136000) Libraries aren't my thing... heh. -- Gaim Beta 6 Crashes Instantly https://launchpad.net/bugs/81173 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
