[Bug 314713] Re: linkedin very slow on Firefox Linux only
> Running sudo ifconfig eth0 mtu 1360 did resolve the problem. It didn't on my laptop, nor did Ian's workaround (rule deletion). Plus, while before I could access Linkedin with Konqueror, in the last month it's been behaving like Firefox. -- linkedin very slow on Firefox Linux only https://bugs.launchpad.net/bugs/314713 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 314713] Re: linkedin very slow on Firefox Linux only
Hey Jonas, thank you - you were absolutely right! I gave it for granted that eth0 was the correct interface for me as well, but I was wrong, for it was eth1. It's now working flawlessly, so many thanks, guys! -- linkedin very slow on Firefox Linux only https://bugs.launchpad.net/bugs/314713 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 314713] Re: linkedin very slow on Firefox Linux only
Hi all. Another thing I gave for granted was that this workaround would last after rebooting. Instead, after today's restart, I was back to square one, and had to use the terminal command once again. Is there a way to make the change permanent? Many thanks in advance! -- linkedin very slow on Firefox Linux only https://bugs.launchpad.net/bugs/314713 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 314713] Re: linkedin very slow on Firefox Linux only
Samer Azmy wrote: > Yes from your Linux Distro Network Manager , you can force the MTU value and > that will be valid even after reboot Great, this worked! Thank you, Samer. -- linkedin very slow on Firefox Linux only https://bugs.launchpad.net/bugs/314713 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 364127] Re: Hotkeys for changing volume and muting broken with jaunty (on Thinkpad R60, T40, T43, X41 and T60)
Many thanks to Dominic, whose solution worked better than I first expected! As explained here (http://ubuntuforums.org/showthread.php?p=7357087#post7357087), Dominic's downgrade was indeed an upgrade for me, instead, for things now work as they were supposed to do after upgrading to Jaunty. If I got it right, in fact, the downgrade should have brought back the old visualisations from Intrepid, but this was not the case, for Ubuntu is now using the new notification system properly, like other applications such as Rhythmbox or Pidgin. If I got it wrong, instead, and the new notifications were already part of Dominic's workaround, well, hats off! Your temporary workaround can as well be my permanent solution! =) -- Hotkeys for changing volume and muting broken with jaunty (on Thinkpad R60, T40, T43, X41 and T60) https://bugs.launchpad.net/bugs/364127 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 288939] Re: [Intrepid]Tray bacground transparency problems
*** This bug is a duplicate of bug 247393 *** https://bugs.launchpad.net/bugs/247393 I had this problem (especially with aMSN from repository - but they say the culprit is the panel in Gnome) with Intrepid, and keep having it with Jaunty. Nothing really changed. Any fix would be greatly appreciated. -- [Intrepid]Tray bacground transparency problems https://bugs.launchpad.net/bugs/288939 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 314713] Re: linkedin very slow on Firefox Linux only
Same problem here. I'm running (K)Ubuntu 9.04, using D-Link router (model no. DSL-G624T), and Firofox 3.0.10. Pages with messages from group members load just fine, but if I want to access someone's profile, it takes forever until pages finally time out. I can't remember which version was available when I switched to Ubuntu last October, but I've always had this problem with LinkedIn. However, lately I've noticed that if I use Konqueror 4.2.2 pages load in the blink of an eye. Kind of annoying, for I prefer using Firefox. -- linkedin very slow on Firefox Linux only https://bugs.launchpad.net/bugs/314713 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 459423] Re: Unable to play video from "Youtube plugin" results
Confirmed, the bug is back. Karmic, fully updated. -- Unable to play video from "Youtube plugin" results https://bugs.launchpad.net/bugs/459423 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 459423] Re: Unable to play video from "Youtube plugin" results
Yes, Sir! I see the Ubuntu community is getting lovelier by the day. Oh, and by the way, instead of giving orders and educating people on bug reports, you could have been done it yourself, if you found the time to describe the whole procedure. But you're right, I don't see Mark Shuttleworth commenting that it should be fixed as soon as possible, so I guess no one will jump on his seat and fix it for the next release. In the end, it's not my distro. I merely use it. Maybe your main goal is not to fix bugs, as long as there are buttons to move around, I don't know. Keep your buggy software, man, I'll use the browser next time I want to watch a video on YouTube. Thanks anyway. -- Unable to play video from "Youtube plugin" results https://bugs.launchpad.net/bugs/459423 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 515495] Re: nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()
Thanks Vish. I was asked by a user who wished to follow the bug to switch it to public. Do you think it safer if I switch the duplicates to private as well? -- nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID() https://bugs.launchpad.net/bugs/515495 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 515495] Re: nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()
OK, thanks! -- nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID() https://bugs.launchpad.net/bugs/515495 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 488673] Re: [IBM 1834RTG] suspend/resume failure
On Saturday 24 April 2010 00:49:32 you wrote: > Hi lelamal, > > This bug was reported a while ago and there hasn't been any activity in it > recently. Hi, this is basically because, while bugs kept adding to the original bug, the problem was completely ignored up to the next important release, probably hoping that would solve the issue (as it happens with many unsolved bugs, unfortunately), although a serious kernel problem is involved. As pointed out, however, using the machine in a working environment, I can't afford losing data and wasting time after a broken release which contains several critical regressions. As a result, I switched to another machine, and another flavor (kubuntu), which finally guaranteed me unstopped, reliable work-flow. In addition, many users must have felt the same, and resorted to the same, or other solutions, and this, coupled with lack of serious response from developers in a timely fashion, would finally account for the lack of activity in this bug, recently. > We were wondering if this is still an issue? Can you try with > the latest development release of Ubuntu? ISO CD images are available > from http://cdimage.ubuntu.com/releases/ . I am sorry, but both machines are now on kubuntu (currently, lucid), so I cannot try that now. This bug may even be set to "incomplete", but since it was filed under karmic, I can swear it was still very active till the point I had to switch machine and desktop manager. So, no one actively fixed it. Besides, I do not see a clear point in testing (now!) a development release when all I needed was back then the OS to work in a stable environment and with a stable release. This is a rather convoluted way to fix things, and to those who insist that ubuntu is different from Windows in that you can actually report bugs and have them fixed before a new release comes out I would like to point out that it's not entirely true, and I could verify that numerous times. > If it remains an issue, could you run the following command from a Terminal > (Applications->Accessories->Terminal). It will automatically gather and > attach updated debug information to this report. > > apport-collect -p linux 488673 Sorry, I could not, for I am not running that flavor (and will not anytime soon) and machine anymore. > Also, if you could test the latest upstream kernel available that would be > great. It will allow additional upstream developers to examine the issue. > Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've > tested the upstream kernel, please remove the 'needs-upstream-testing' > tag. This can be done by clicking on the yellow pencil icon next to the > tag located at the bottom of the bug description and deleting the > 'needs-upstream-testing' text. Please let us know your results. For the same reasons already discussed, unfortunately I cannot test my machines with the latest upstream kernel available, because I need a stable working environment, and all my contributions to the ubuntu project may be limited to reporting bugs and to a few translations. Also, note that, as explained in comment #35 at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/485108, I had already done everything I needed to, by mentioning an upstream bug url in my comment and linking it to the bug. I also continued to follow the upstream bug report as I was told to, but there was not much activity either, I must say, so there was nothing you could pull into Ubuntu to take a look at it. So, I was pretty much waiting for developers to look into the issue, and update you on that. Lack of activity on both sides left the bug to stall, and me to pursue stability elsewhere. Just a final, personal thought: chasing change "just for the hell of it", trying "to be different" at all costs at every new release, and releasing twice a year an unstable OS may not the best way forward, if Canonical is seriously considering to fix Bug 1. To me, is more important to have old bugs fixed and no regressions when I upgrade to new versions, rather than having a shiny new piece of OS half-baked twice a year just in time for its schedule just because it had to be released regardless. You can keep pushing dirt under the carpet, but sooner or later someone has to clean underneath. Thanks in advance. [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.] -- [IBM 1834RTG] suspend/resume failure https://bugs.launchpad.net/bugs/488673 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 493505] Re: [IBM 1834RTG] hibernate/resume failure
On Saturday 24 April 2010 01:21:55 you wrote: > Hi lelamal, > > This bug was reported a while ago and there hasn't been any activity in it > recently. Hi, this is basically because, while bugs kept adding to the original bug, the problem was completely ignored up to the next important release, probably hoping that would solve the issue (as it happens with many unsolved bugs, unfortunately), although a serious kernel problem is involved. As pointed out, however, using the machine in a working environment, I can't afford losing data and wasting time after a broken release which contains several critical regressions. As a result, I switched to another machine, and another flavor (kubuntu), which finally guaranteed me unstopped, reliable work-flow. In addition, many users must have felt the same, and resorted to the same, or other solutions, and this, coupled with lack of serious response from developers in a timely fashion, would finally account for the lack of activity in this bug, recently. > We were wondering if this is still an issue? Can you try with > the latest development release of Ubuntu? ISO CD images are available > from http://cdimage.ubuntu.com/releases/ . I am sorry, but both machines are now on kubuntu (currently, lucid), so I cannot try that now. This bug may even be set to "incomplete", but since it was filed under karmic, I can swear it was still very active till the point I had to switch machine and desktop manager. So, no one actively fixed it. Besides, I do not see a clear point in testing (now!) a development release when all I needed was back then the OS to work in a stable environment and with a stable release. This is a rather convoluted way to fix things, and to those who insist that ubuntu is different from Windows in that you can actually report bugs and have them fixed before a new release comes out I would like to point out that it's not entirely true, and I could verify that numerous times. > If it remains an issue, could you run the following command from a Terminal > (Applications->Accessories->Terminal). It will automatically gather and > attach updated debug information to this report. > > apport-collect -p linux 493505 Sorry, I could not, for I am not running that flavor (and will not anytime soon) and machine anymore. > Also, if you could test the latest upstream kernel available that would be > great. It will allow additional upstream developers to examine the issue. > Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've > tested the upstream kernel, please remove the 'needs-upstream-testing' > tag. This can be done by clicking on the yellow pencil icon next to the > tag located at the bottom of the bug description and deleting the > 'needs-upstream-testing' text. Please let us know your results. For the same reasons already discussed, unfortunately I cannot test my machines with the latest upstream kernel available, because I need a stable working environment, and all my contributions to the ubuntu project may be limited to reporting bugs and to a few translations. Also, note that, as explained in comment #35 at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/485108, I had already done everything I needed to, by mentioning an upstream bug url in my comment and linking it to the bug. I also continued to follow the upstream bug report as I was told to, but there was not much activity either, I must say, so there was nothing you could pull into Ubuntu to take a look at it. So, I was pretty much waiting for developers to look into the issue, and update you on that. Lack of activity on both sides left the bug to stall, and me to pursue stability elsewhere. Just a final, personal thought: chasing change "just for the hell of it", trying "to be different" at all costs at every new release, and releasing twice a year an unstable OS may not the best way forward, if Canonical is seriously considering to fix Bug 1. To me, is more important to have old bugs fixed and no regressions when I upgrade to new versions, rather than having a shiny new piece of OS half-baked twice a year just in time for its schedule just because it had to be released regardless. You can keep pushing dirt under the carpet, but sooner or later someone has to clean underneath. Thanks in advance. [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.] -- [IBM 1834RTG] hibernate/resume failure https://bugs.launchpad.net/bugs/493505 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 526369] Re: [ASUSTeK Computer Inc. P4P800] hibernate/resume failure
On Tuesday 27 April 2010 04:55:44 you wrote: > Hi lelamal, > > This bug was reported a while ago and there hasn't been any activity in it > recently. Hi, "merely" two months, but this is basically because, although I made myself available to add any more details about the problem, the problem was completely ignored up to the next important release, probably hoping that would solve the issue (as it happens with many unsolved bugs, unfortunately), although a serious kernel problem is involved. However, using the machine in a working environment, I can't afford losing data and wasting time after a broken release which contains several critical regressions. As a result, I first changed machine, from my previous laptop (see exchange at Bug 488673) to the present desktop, but the issue was still there (see also Bug 562987). Then, lately I uninstalled everything, reformatted, and fresh-installed another flavor (kubuntu), which finally guaranteed me unstopped, reliable work-flow. In addition, many users must have felt the same, and resorted to the same, or other solutions, and this, coupled with lack of serious response from developers in a timely fashion, would finally account for the lack of activity in this bug, recently. > We were wondering if this is still an issue? Can you try with > the latest development release of Ubuntu? ISO CD images are available > from http://cdimage.ubuntu.com/releases/ . I am sorry, but both machines I use are now on kubuntu (currently, lucid), so I cannot try that now. This bug may even be set to "incomplete", but since it was filed under karmic, I can swear it was still very active till the point I had to switch machine, desktop manager, and release (RC). So, no one actively fixed it until RC came out. Besides, I do not see a clear point in testing (now!) a development release when all I needed was (back then!) the OS to work in a stable environment and with a stable release. This is a rather convoluted way to fix things, and to those who insist that ubuntu is different from Windows in that you can actually report bugs and have them fixed before a new release comes out I would like to point out that it's not entirely true, and I could verify that numerous times. > If it remains an issue, could you run the following command from a Terminal > (Applications->Accessories->Terminal). It will automatically gather and > attach updated debug information to this report. > > apport-collect -p linux 526369 Sorry, I could not, for I am not running that flavor (and will not anytime soon) and machine anymore. > Also, if you could test the latest upstream kernel available that would be > great. It will allow additional upstream developers to examine the issue. > Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've > tested the upstream kernel, please remove the 'needs-upstream-testing' > tag. This can be done by clicking on the yellow pencil icon next to the > tag located at the bottom of the bug description and deleting the > 'needs-upstream-testing' text. Please let us know your results. For the same reasons already discussed, unfortunately I cannot test my machines with the latest upstream kernel available, because I need a stable working environment, and all my contributions to the ubuntu project may be limited to reporting bugs and to a few translations. So, I was pretty much waiting for developers to look into the issue, and update you on that. Lack of activity on both sides left the bug to stall, and me to pursue stability elsewhere. Just a final, personal thought: chasing change "just for the hell of it", trying "to be different" at all costs at every new release, and releasing twice a year an unstable OS may not the best way forward, if Canonical is seriously considering to fix Bug 1. To me, is more important to have old bugs fixed and no regressions when I upgrade to new versions, rather than having a shiny new piece of OS half-baked twice a year just in time for its schedule just because it had to be released regardless. You can keep pushing dirt under the carpet, but sooner or later someone has to clean underneath. Thanks in advance. [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.] -- [ASUSTeK Computer Inc. P4P800] hibernate/resume failure https://bugs.launchpad.net/bugs/526369 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 551290] Re: plymouth theme ugly on binary nvidia driver
Hi all, this bug affects also my card: VGA compatible controller: Matrox Graphics, Inc. MGA G400/G450 -- plymouth theme ugly on binary nvidia driver https://bugs.launchpad.net/bugs/551290 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kubuntu-default-settings in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 551290] Re: plymouth theme ugly on binary nvidia driver
Sorry for the consecutive posts, but I realise only now that this bug is filed for Nvidia drivers. So I was wondering, should I file another bug, or is it OK to test this package on my system? -- plymouth theme ugly on binary nvidia driver https://bugs.launchpad.net/bugs/551290 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kubuntu-default-settings in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 551290] Re: plymouth theme ugly on binary nvidia driver
Martin, I tested the package as suggested. As Sel Goona reported in comment #49, it's definitely better looking: please, compare Screenshot1 (before) with Screenshot2 (after). Extreme pixelation disappeared, but still it feels slightly improvable. Also, some comments follow: - cursor keeps blinking on the upper left corner over a black screen, when one would expect the logo to appear instead; - most of the times, the logo in the end doesn't appear at all, there's a short green flash followed instantly by the login screen; - sometimes, while cursor blinks, some information is displayed as shown in Screenshot3 (sorry for the resolution, as the other 2, it's a picture and since this behavior cannot be reproduced at every login, I was unable to take a better shot); - when computer is shut down, on the contrary, the logo seems to be always shown. Anyway, thanks for all your efforts, and good work so far! ** Attachment added: "Screenshot1.JPG" http://launchpadlibrarian.net/46630533/Screenshot1.JPG -- plymouth theme ugly on binary nvidia driver https://bugs.launchpad.net/bugs/551290 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kubuntu-default-settings in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 551290] Re: plymouth theme ugly on binary nvidia driver
Screenshot2 (sorry, I thought I could upload all the attachments in one shot). ** Attachment added: "Screenshot2.JPG" http://launchpadlibrarian.net/46630783/Screenshot2.JPG -- plymouth theme ugly on binary nvidia driver https://bugs.launchpad.net/bugs/551290 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kubuntu-default-settings in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 551290] Re: plymouth theme ugly on binary nvidia driver
Screenshot3 ** Attachment added: "Screenshot3.JPG" http://launchpadlibrarian.net/46630809/Screenshot3.JPG -- plymouth theme ugly on binary nvidia driver https://bugs.launchpad.net/bugs/551290 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 562987] Re: [ASUSTeK Computer Inc. P4P800] late resume failure
On Thursday 06 May 2010 17:02:42 you wrote: > Hi, > > Looking at your Dmesg, we can find > > ACPI Warning: Incorrect checksum in table [OEMB] - D0, should be C1 > 20090521 tbutils-246 > > which is the same as this bug# 133146. Hi Pepe, I've tried to follow that bug, but when it gets too technical it just looses me. What is that string referring to, what does that mean? > Please, update your BIOS or simply ignore this warning. I know that's a dangerous operation that shouldn't be tried unless you want to fix serious issues - is this the case? What improvement may the update bring? Or can I safely ignore this warning? > I'm marking this bug as 'Invalid'. Please feel free to reopen to 'New' > if you feel this is a real bug. It was Apport to think so (I don't even know why it's not a bug anymore, go figure!). -- [ASUSTeK Computer Inc. P4P800] late resume failure https://bugs.launchpad.net/bugs/562987 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 479296] Re: Karmic: frequent freezes
On Wed, 2009-11-18 at 14:36 +, Daniel T Chen wrote: On Wed, Nov 18, 2009 at 8:51 AM, lelamal wrote: > > All in all, I can say things are much better now, although I'm not > > entirely sure that audio was the only cause of the issue, although > > It's unlikely and a red herring. > And a red herring it was, indeed. I had one of those freezes just a couple of hours later. I was transferring MP3 files from an external EXT4 HD to a FAT32 USB pen-drive through Karmic main HD (in EXT4 as well, of course). Music got stuck between two notes, and system became unresponsive. I confess that whenever it happens, the feeling is similar to the one I had with Windows' Blue Screen Of Death, and it isn't pleasant at all. I remember reading somewhere that EXT4 file systems had some issues with FAT and NTFS file systems. I reformatted the pen drive in EXT4, just in case. I don't know what else to think. > Nov 3 02:47:30 ECO pulseaudio[1564]: ratelimit.c: 153 events suppressed > > Nov 3 02:49:19 ECO kernel: [59669.083978] [drm] LVDS-8: set mode 1024x768 d > > Nov 3 02:49:21 ECO kernel: [59671.086380] [drm] DAC-6: set mode 640x480 0 > > Nov 3 02:49:22 ECO kernel: [59671.576399] [drm] DAC-6: set mode 640x480 0 > > Nov 3 02:49:22 ECO kernel: [59672.002693] i2c-adapter i2c-1: unable to read > > EDID block. > > Different subsystem -- graphics: i915/drm/intel X driver. No idea if > it is the culprit; graphics aren't my expertise. > Then might it not be wrong to file the bug under pulseaudio, if we don't even know what causes it exactly? If the solution you proposed didn't bring the expected result, and everybody seems to keep experiencing freezes under Karmic, maybe the culprits have yet to be identified. -- Karmic: frequent freezes https://bugs.launchpad.net/bugs/479296 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 422393] Re: nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()
Despite I read a fix was released last month, Nautilus has just crashed, and I landed here after submitting the required information to the developers through Apport. -- nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID() https://bugs.launchpad.net/bugs/422393 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 479296] Re: Karmic: frequent freezes
OK, sorry, this is going to be a long one. So here is a follow-up, and a possible fix to my problem. Without having identified the culprit, I've tried a number of blind guesses, and this is only the last attempt. I want to stress the issue I reported is inevitably related to MY own hardware, hence what I'm going to report may not work for others. Also, I want to point out that mine are only speculations, and all my conclusions may as well be completely wrong: I'm an ordinary user, I'm no expert. Two days ago I had another freeze. The System Log showed nothing, but a couple of those ratelimit.c: messages, a few minutes earlier. Actually, what I've found out is that these freezes leave no traces in the log, really. However, I originally connected the freezes to those ratelimit.c: messages only because the latter were the last things reported in the Log. In turn, this must have misled Daniel who filed the bug under Pulseaudio. But other times I noticed those messages were reported tens of minutes earlier, and in other occasions preceding messages related to something different entirely. But last freeze actually told me something different... This was a good instance of those classic freezes I was experiencing involving both audio and graphics. I was raising Rhythmbox window to play some music (but no music was playing at that moment), when the system froze between the two notes of the system notification sound. But what was more revealing to me was that it froze while the window was half way, meaning that the default Compiz effect that comes with a normal installation of Karmic was tilting the window upwards (the effect is called "Glide 2"), but couldn't finish the operation. The freezes have got to be connected to graphics, especially Compiz. Being on a Thinkpad R50e, maybe my system is too old for such things, I don't know - though I can't recall any of this on Jaunty, where I even had the cube. In addition, going back to the previous day's freeze, it happened when I was transferring data to a USB pen drive, so I incorrectly connected it to its NTFS file system: instead, it occurred when the small window of the file transfer popped up. In this light, the two freezes together now made much more sense. For all this, I disabled Compiz. I'm back on Metacity, and I've got a feeling things are changing. I enabled compositing_manager in the Configuration Editor for simple effects like shadows, transparency, smoother movements, etc. and do not miss Compiz eye candy effects at all. The system appears much more efficient, things are way quicker. With Compiz Fade effect out, for example, that overall sleepy feeling Ubuntu had acquired has finally gone. Now everything responds immediately, from menus to windows, rather than waiting to show the fading effect first. But what's more important, audio stopped stuttering, and system stopped freezing. Of course I'm aware it's still too early to say, and I myself had decided to report back only after a week, at least. But I thought that maybe other people could be suffering from the same problem, and try this too in the meantime. If this is the fix to the freezes I was experiencing on Karmic, I swear I'll ditch Compiz for good, and stick to Metacity until Gnome 3 is a reality! Still, I wonder why Ubuntu installs Compiz by default, if this can result unstable on so many systems... -- Karmic: frequent freezes https://bugs.launchpad.net/bugs/479296 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 479296] Re: Karmic: frequent freezes
On Sat, 2009-11-21 at 13:51 +, Filofel wrote:
Hi Lelamal,
>
> It's not clear from your message what got you to suspect Compiz, but
> just as a test, I disabled it
Hi Filofel, sorry for my convoluted explanation. What made me suspect
was that the freezes described occurred when a Compiz effect was at
work, either when raising a window ("Glide 2" effect), or popping up a
window during file transfer (same effect, if I remember correctly), or a
drop-down menu ("Fade" effect) - see my original report. Also, having
excluded the ratelimit.c: messages as potential errors following
Daniel's message #18, I'm still left clueless as to why the freezes I
experience involve (most of the times) audio being stuck in an endless
loop. But, let me stress it once again, I'm not sure this switch to
Metacity will help, for I have no clue what's triggering the freezes in
the first place.
--
Karmic: frequent freezes
https://bugs.launchpad.net/bugs/479296
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 459366] Re: telepathy-butterfly crashed with TypeError in emit_signal()
> This crash is so annoying! I keep getting it every 20 seconds, regularly, making it impossible to use Empathy. Ditto. It keeps popping up when chatting. Using updated Karmic. -- telepathy-butterfly crashed with TypeError in emit_signal() https://bugs.launchpad.net/bugs/459366 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 422393] Re: nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()
> I'll make sure I do so, as soon as this happens again. It happened again, I did so: Bug #515495 -- nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID() https://bugs.launchpad.net/bugs/422393 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 515495] Re: nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()
** Visibility changed to: Public -- nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID() https://bugs.launchpad.net/bugs/515495 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 516219] Re: nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()
** Attachment added: "CoreDump.gz" http://launchpadlibrarian.net/38674260/CoreDump.gz ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/38674261/Dependencies.txt ** Attachment added: "Disassembly.txt" http://launchpadlibrarian.net/38674262/Disassembly.txt ** Attachment added: "ProcMaps.txt" http://launchpadlibrarian.net/38674263/ProcMaps.txt ** Attachment added: "ProcStatus.txt" http://launchpadlibrarian.net/38674264/ProcStatus.txt ** Attachment added: "Registers.txt" http://launchpadlibrarian.net/38674265/Registers.txt ** Attachment added: "Stacktrace.txt" http://launchpadlibrarian.net/38674267/Stacktrace.txt ** Attachment added: "ThreadStacktrace.txt" http://launchpadlibrarian.net/38674268/ThreadStacktrace.txt ** Attachment added: "XsessionErrors.txt" http://launchpadlibrarian.net/38674269/XsessionErrors.txt ** Attachment added: "usr_lib_nautilus.txt" http://launchpadlibrarian.net/38674270/usr_lib_nautilus.txt ** Visibility changed to: Public -- nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID() https://bugs.launchpad.net/bugs/516219 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 422393] Re: nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()
And again: Bug #516219 -- nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID() https://bugs.launchpad.net/bugs/422393 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 515495] Re: nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()
Please, also refer to the new Bug #516219 -- nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID() https://bugs.launchpad.net/bugs/515495 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 516364] [NEW] evolution crashed with SIGSEGV in e_error_newv()
Public bug reported: Binary package hint: evolution I was changing folders when Evolution froze for a dozen seconds before crashing. ProblemType: Crash Architecture: i386 Date: Wed Feb 3 01:34:06 2010 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/bin/evolution InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) Package: evolution 2.28.1-0ubuntu2 ProcCmdline: evolution --component=mail ProcCwd: /home/lelamal ProcEnviron: LANGUAGE=en_GB.UTF-8 LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-17.54-generic SegvAnalysis: Segfault happened at: 0x1cb768:movzbl (%edi),%eax PC (0x001cb768) ok source "(%edi)" (0x0018) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: evolution StacktraceTop: ?? () from /usr/lib/evolution/2.28/libeutil.so.0 e_error_newv () from /usr/lib/evolution/2.28/libeutil.so.0 e_error_new () from /usr/lib/evolution/2.28/libeutil.so.0 mail_msg_check_error () ?? () Title: evolution crashed with SIGSEGV in e_error_newv() Uname: Linux 2.6.31-17-generic i686 UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare ** Affects: evolution (Ubuntu) Importance: Undecided Status: New ** Tags: apport-crash i386 -- evolution crashed with SIGSEGV in e_error_newv() https://bugs.launchpad.net/bugs/516364 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 516364] Re: evolution crashed with SIGSEGV in e_error_newv()
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/38684420/Dependencies.txt ** Attachment added: "Disassembly.txt" http://launchpadlibrarian.net/38684421/Disassembly.txt ** Attachment added: "ProcMaps.txt" http://launchpadlibrarian.net/38684423/ProcMaps.txt ** Attachment added: "ProcStatus.txt" http://launchpadlibrarian.net/38684424/ProcStatus.txt ** Attachment added: "Registers.txt" http://launchpadlibrarian.net/38684425/Registers.txt ** Attachment added: "Stacktrace.txt" http://launchpadlibrarian.net/38684426/Stacktrace.txt ** Attachment added: "ThreadStacktrace.txt" http://launchpadlibrarian.net/38684427/ThreadStacktrace.txt ** Attachment added: "XsessionErrors.txt" http://launchpadlibrarian.net/38684428/XsessionErrors.txt -- evolution crashed with SIGSEGV in e_error_newv() https://bugs.launchpad.net/bugs/516364 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 516364] Re: evolution crashed with SIGSEGV in e_error_newv()
Thank you for your reply. I would be very happy to help. However, I have read the page you link several times already, even in the past, and always failed to understand what am I supposed to do. I find the explanation convoluted and unclear. Where it reads: "First, check if there is a package with a -dbg suffix in the main Ubuntu repositories (TODO: Please edit this wiki here to describe how to do this). These are the debug symbol packages, and are equivalent to '-dbgsym' described below. You can safely use either one, but not both at once", I don't know how to proceed. If you can guide me through this whole process, I would be very happy to help. Otherwise, I will try to click on the crash file in var>crash. The reason why I uploaded a short report is that the full report, over 250 MB, always fails in the end alleging some connection problem. If this also fails, you can safely close this bug, for I will not attempt what I did not understand. Thank you. -- evolution crashed with SIGSEGV in e_error_newv() https://bugs.launchpad.net/bugs/516364 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 496232] Re: gwibber-daemon crashed with GError in notify()
*** This bug is a duplicate of bug 478408 *** https://bugs.launchpad.net/bugs/478408 > Please look at > the other bug report to see if there is any missing information that you > can provide, or to see if there is a workaround for the bug. I would like to. Yet, when I click on the link, all I can read is: Not allowed here Sorry, you don't have permission to access this page. You are logged in as lelamal. Any idea why? -- gwibber-daemon crashed with GError in notify() https://bugs.launchpad.net/bugs/496232 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 496356] Re: totem crashed with SIGSEGV
*** This bug is a duplicate of bug 473536 *** https://bugs.launchpad.net/bugs/473536 Yes, but that report read "Incomplete", and incomplete bugs don't get fixed, or do they? Why should (potentially) complete bug reports be considered duplicates of incomplete reports? Or is mine incomplete, as well? Many thanks for any reply! -- totem crashed with SIGSEGV https://bugs.launchpad.net/bugs/496356 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 485108] Re: [IBM 1834RTG] late resume failure
I've browsed the bugzilla.kernel.org database as you suggested, and found this bug: http://bugzilla.kernel.org/show_bug.cgi?id=14640. It was reported on the same day as this one, and it already refers to this page. Since I'm not familiar with Bugzilla, when you say "link the kernel.org bug report to this bug report", do you actually mean to paste a link to this bug report into a comment box as Wayne already did, or is there another way to link it? Please let me know if there is anything else I can do. ** Bug watch added: Linux Kernel Bug Tracker #14640 http://bugzilla.kernel.org/show_bug.cgi?id=14640 -- [IBM 1834RTG] late resume failure https://bugs.launchpad.net/bugs/485108 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 526369] [NEW] [ASUSTeK Computer Inc. P4P800] hibernate/resume failure
Public bug reported: I tried to hibernate my desktop, but failed. HDs sounded like spinning down, but still they could be heard spinning. The display went black and responded to nothing but a cold reboot. After login, Apport told me there was a serious kernel problem that I am here reporting. ProblemType: KernelOops Annotation: This occured during a previous hibernate and prevented it from resuming properly. Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lelamal2228 F pulseaudio /dev/snd/seq:timidity 2027 F timidity CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Live'/'SB Live! Value [CT4670] (rev.8, serial:0x201102) at 0xdf80, irq 21' Mixer name : 'SigmaTel STAC9721,23' Components : 'AC97a:83847609' Controls : 219 Simple ctrls : 42 Date: Tue Feb 23 11:31:52 2010 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/share/apport/apportcheckresume Failure: hibernate/resume HibernationDevice: RESUME=UUID=046961b7-6220-47c8-963f-4f517643c8f3 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) InterpreterPath: /usr/bin/python2.6 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux-image-2.6.31-19-generic 2.6.31-19.56 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-19-generic root=UUID=1c2564b4-9cdf-41ae-9ba9-2a2e5c612e32 ro quiet splash ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume ProcEnviron: PATH=(custom, no user) ProcVersionSignature: Ubuntu 2.6.31-19.56-generic RelatedPackageVersions: linux-backports-modules-2.6.31-19-generic N/A linux-firmware 1.25 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Tags: resume hibernate Title: [To Be Filled By O.E.M. To Be Filled By O.E.M.] hibernate/resume failure Uname: Linux 2.6.31-19-generic i686 UserGroups: dmi.bios.date: 07/21/2003 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1009.008 dmi.board.name: P4P800 dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1009.008:bd07/21/2003:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASUSTeKComputerInc.:rnP4P800:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-kerneloops hibernate i386 resume -- [ASUSTeK Computer Inc. P4P800] hibernate/resume failure https://bugs.launchpad.net/bugs/526369 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 526369] Re: [To Be Filled By O.E.M. To Be Filled By O.E.M.] hibernate/resume failure
** Attachment added: "AlsaDevices.txt" http://launchpadlibrarian.net/39603483/AlsaDevices.txt ** Attachment added: "AplayDevices.txt" http://launchpadlibrarian.net/39603484/AplayDevices.txt ** Attachment added: "ArecordDevices.txt" http://launchpadlibrarian.net/39603485/ArecordDevices.txt ** Attachment added: "BootDmesg.txt" http://launchpadlibrarian.net/39603486/BootDmesg.txt ** Attachment added: "Card0.Amixer.values.txt" http://launchpadlibrarian.net/39603487/Card0.Amixer.values.txt ** Attachment added: "Card0.Codecs.codec97.0.ac97.0.0.txt" http://launchpadlibrarian.net/39603488/Card0.Codecs.codec97.0.ac97.0.0.txt ** Attachment added: "Card0.Codecs.codec97.0.ac97.0.0.regs.txt" http://launchpadlibrarian.net/39603489/Card0.Codecs.codec97.0.ac97.0.0.regs.txt ** Attachment added: "CurrentDmesg.txt" http://launchpadlibrarian.net/39603490/CurrentDmesg.txt ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/39603491/Dependencies.txt ** Attachment added: "IwConfig.txt" http://launchpadlibrarian.net/39603492/IwConfig.txt ** Attachment added: "Lspci.txt" http://launchpadlibrarian.net/39603493/Lspci.txt ** Attachment added: "Lsusb.txt" http://launchpadlibrarian.net/39603494/Lsusb.txt ** Attachment added: "PciMultimedia.txt" http://launchpadlibrarian.net/39603495/PciMultimedia.txt ** Attachment added: "ProcCpuinfo.txt" http://launchpadlibrarian.net/39603497/ProcCpuinfo.txt ** Attachment added: "ProcInterrupts.txt" http://launchpadlibrarian.net/39603498/ProcInterrupts.txt ** Attachment added: "ProcMaps.txt" http://launchpadlibrarian.net/39603499/ProcMaps.txt ** Attachment added: "ProcModules.txt" http://launchpadlibrarian.net/39603500/ProcModules.txt ** Attachment added: "ProcStatus.txt" http://launchpadlibrarian.net/39603501/ProcStatus.txt ** Attachment added: "SleepLog.txt" http://launchpadlibrarian.net/39603502/SleepLog.txt ** Attachment added: "UdevDb.txt" http://launchpadlibrarian.net/39603503/UdevDb.txt ** Attachment added: "UdevLog.txt" http://launchpadlibrarian.net/39603504/UdevLog.txt ** Attachment added: "WifiSyslog.txt" http://launchpadlibrarian.net/39603505/WifiSyslog.txt ** Summary changed: - [To Be Filled By O.E.M. To Be Filled By O.E.M.] hibernate/resume failure + [ASUSTeK Computer Inc. P4P800] hibernate/resume failure -- [ASUSTeK Computer Inc. P4P800] hibernate/resume failure https://bugs.launchpad.net/bugs/526369 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 526369] Re: [ASUSTeK Computer Inc. P4P800] hibernate/resume failure
As you can see, I changed the generic information in the summary with that of my motherboard. I wasn't sure what to write exactly, so please let me know if you need more details about that. -- [ASUSTeK Computer Inc. P4P800] hibernate/resume failure https://bugs.launchpad.net/bugs/526369 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 422393] Re: nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()
I had another crash, and submitted a new report with Apport. Is anyone reading? This bug is not fixed. -- nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID() https://bugs.launchpad.net/bugs/422393 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 485108] Re: [IBM 1834RTG] late resume failure
Hi kwizk, I'm quite happy to know more systems are affected. It means this issue is not isolated and hardware-specific, and hopefully will be tackled more efficiently. Suspend is an important mode, I for one use it extensively on my laptop, so I agree with you when you say it's particularly bothersome. Also, people in the thread mentioned in my original report indicate the following systems as being affected: Sony Vaio VGN-FW139E, Inspiron 600m, Aspice 3690. With regards to the latter, he or she suspects it's the new kernel, because "in Juanty the suspend/hibernation function works fine with 2.6.28, but in other distributions with kernel 2.6.31 (like Mandriva 2010 or Fedora 12) the system freeze too". So, can we get a confirmation from someone up above on this, please? Any sign would be greatly appreciated! Many thanks in advance. -- [IBM 1834RTG] late resume failure https://bugs.launchpad.net/bugs/485108 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 485108] Re: [IBM 1834RTG] late resume failure
Hi rlichter, your comment drew my attention to the frequent freezes you seem to experience, especially to the part where you describe freezes "in the middle of graphic operations", or where mouse movements were still possible but everything else froze. The freezes you describe have been experienced by other users, and are reported in Bug #479296, here https://bugs.launchpad.net/ubuntu/+bug/479296. It never occurred to me to draw a connection between these two bugs, but after your comment I wonder: can the two issues be triggered by a common cause? Can anyone confirm this might be the case, please? -- [IBM 1834RTG] late resume failure https://bugs.launchpad.net/bugs/485108 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 488673] [NEW] [IBM 1834RTG] suspend/resume failure
Public bug reported: After switching my Thinkpad R50e on this morning, it froze exactly at the login window. When I tried to move the mouse, I noticed the pointer wasn't anywhere on the screen. The half-moon-shaped led signalling sleep mode was flashing intermittently, and nothing was responding. The scenario was familiar, and after I was ultimately forced to cold-boot the system, Apport was waiting in the panel to confirm this: please see the attachment. I got the same window before reporting the following bug, a couple of days ago: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/485108. Back then, I surely suspended my laptop, but this wasn't the case today, though the freeze was interpreted as a "suspend/resume failure" (in fact, the bug was named slightly differently). Moreover, both bugs have been reported by Apport as being caused by a SERIOUS (!) Kernel problem. I don't think this leaves any doubt about the connection between this and Bug #485108. Also, as was asked in comment #6 of Bug #485108, the freezes described seem to point to Bug #479296, here https://bugs.launchpad.net/ubuntu/+bug/479296. Can anyone confirm the three bugs have a common origin, please? Can we please finally have an equally SERIOUS (!) answer on this malfunctions? Many thanks! ProblemType: KernelOops Annotation: This occured during a previous suspend and prevented it from resuming properly. Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lelamal1633 F pulseaudio /dev/snd/pcmC0D0p: lelamal1633 F...m pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'I82801DBICH4'/'Intel 82801DB-ICH4 with AD1981B at irq 5' Mixer name : 'Analog Devices AD1981B' Components : 'AC97a:41445374' Controls : 28 Simple ctrls : 20 Date: Thu Nov 26 10:37:52 2009 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=f9146e7a-38fe-4080-ab7d-4f0edf647170 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) InterpreterPath: /usr/bin/python2.6 MachineType: IBM 1834RTG Package: linux-image-2.6.31-15-generic 2.6.31-15.50 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-15-generic root=UUID=48cb8a41-2954-41e2-baaa-990c31d64638 ro quiet splash ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume ProcEnviron: PATH=(custom, no user) ProcVersionSignature: Ubuntu 2.6.31-15.50-generic RelatedPackageVersions: linux-backports-modules-2.6.31-15-generic N/A linux-firmware 1.25 RfKill: SourcePackage: linux Tags: resume suspend Title: [IBM 1834RTG] suspend/resume failure Uname: Linux 2.6.31-15-generic i686 UserGroups: dmi.bios.date: 12/08/2006 dmi.bios.vendor: IBM dmi.bios.version: 1WET90WW (2.10 ) dmi.board.name: 1834RTG dmi.board.vendor: IBM dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: IBM dmi.chassis.version: Not Available dmi.modalias: dmi:bvnIBM:bvr1WET90WW(2.10):bd12/08/2006:svnIBM:pn1834RTG:pvrThinkPadR50e:rvnIBM:rn1834RTG:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable: dmi.product.name: 1834RTG dmi.product.version: ThinkPad R50e dmi.sys.vendor: IBM ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-kerneloops i386 resume suspend -- [IBM 1834RTG] suspend/resume failure https://bugs.launchpad.net/bugs/488673 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 488673] Re: [IBM 1834RTG] suspend/resume failure
** Attachment added: "Kernel problem screenshot" http://launchpadlibrarian.net/36107323/Screenshot.png ** Attachment added: "AlsaDevices.txt" http://launchpadlibrarian.net/36107324/AlsaDevices.txt ** Attachment added: "AplayDevices.txt" http://launchpadlibrarian.net/36107325/AplayDevices.txt ** Attachment added: "ArecordDevices.txt" http://launchpadlibrarian.net/36107326/ArecordDevices.txt ** Attachment added: "BootDmesg.txt" http://launchpadlibrarian.net/36107327/BootDmesg.txt ** Attachment added: "Card0.Amixer.values.txt" http://launchpadlibrarian.net/36107328/Card0.Amixer.values.txt ** Attachment added: "Card0.Codecs.codec97.0.ac97.0.0.txt" http://launchpadlibrarian.net/36107329/Card0.Codecs.codec97.0.ac97.0.0.txt ** Attachment added: "Card0.Codecs.codec97.0.ac97.0.0.regs.txt" http://launchpadlibrarian.net/36107330/Card0.Codecs.codec97.0.ac97.0.0.regs.txt ** Attachment added: "CurrentDmesg.txt" http://launchpadlibrarian.net/36107331/CurrentDmesg.txt ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/36107332/Dependencies.txt ** Attachment added: "IwConfig.txt" http://launchpadlibrarian.net/36107333/IwConfig.txt ** Attachment added: "Lspci.txt" http://launchpadlibrarian.net/36107334/Lspci.txt ** Attachment added: "Lsusb.txt" http://launchpadlibrarian.net/36107335/Lsusb.txt ** Attachment added: "PciMultimedia.txt" http://launchpadlibrarian.net/36107336/PciMultimedia.txt ** Attachment added: "ProcCpuinfo.txt" http://launchpadlibrarian.net/36107337/ProcCpuinfo.txt ** Attachment added: "ProcInterrupts.txt" http://launchpadlibrarian.net/36107338/ProcInterrupts.txt ** Attachment added: "ProcMaps.txt" http://launchpadlibrarian.net/36107339/ProcMaps.txt ** Attachment added: "ProcModules.txt" http://launchpadlibrarian.net/36107340/ProcModules.txt ** Attachment added: "ProcStatus.txt" http://launchpadlibrarian.net/36107341/ProcStatus.txt ** Attachment added: "SleepLog.txt" http://launchpadlibrarian.net/36107342/SleepLog.txt ** Attachment added: "UdevDb.txt" http://launchpadlibrarian.net/36107343/UdevDb.txt ** Attachment added: "UdevLog.txt" http://launchpadlibrarian.net/36107344/UdevLog.txt ** Attachment added: "WifiSyslog.txt" http://launchpadlibrarian.net/36107345/WifiSyslog.txt -- [IBM 1834RTG] suspend/resume failure https://bugs.launchpad.net/bugs/488673 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 488673] Re: [IBM 1834RTG] suspend/resume failure
Sorry, I wasn't clear enough. The attachment I mention in my report is difficult to identify among all the others. It's a screenshot, and is called: Kernel problem screenshot. ** Tags added: kernel-karmic -- [IBM 1834RTG] suspend/resume failure https://bugs.launchpad.net/bugs/488673 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 479296] Re: Karmic: frequent freezes
In my view, the fact that this bug has been reported manually makes it more difficult to identify the culprits. More specifically, the issues described in my original report are quite general, and leave ample room both to interpretations, and to a series of other issues that may well be triggered by different culprits. In turn, this has become an issue report (not different from a forum exchange), rather than a bug report, for the bug itself is rather difficult to pinpoint, and some digging is necessary. This was one thing I wanted to clarify before the following: I have been experiencing a series of other freezes that led me to report a number of other bugs. At first, it didn't occur to me to see similarities between them, but the comments of other users left me wondering whether these freezes are similar indeed, and whether the root cause of them all is a kernel problem. Apport reported those bugs with my laptop model [IBM 1834RTG], but as I understand it this is not hardware-specific. If anyone is interested and is experiencing the same problems, please visit the following pages and comment accordingly: Bug #485108, Bug #488673. Many thanks in advance! -- Karmic: frequent freezes https://bugs.launchpad.net/bugs/479296 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 485108] Re: [IBM 1834RTG] late resume failure
Hi, I suspect this issue is caused by whatever is causing the issue reported at Bug #488673. Apport indicates a serious kernel problem. -- [IBM 1834RTG] late resume failure https://bugs.launchpad.net/bugs/485108 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 372089] Re: Evolution mail dont save password keeps asking
Have been having this bug on Jaunty, and keep having it on Karmic. Following Sebastien Bacher's comment #11, filed a bug upstream here https://bugzilla.gnome.org/show_bug.cgi?id=603855. Anyone still experiencing this issue, please add any useful information there. ** Bug watch added: GNOME Bug Tracker #603855 https://bugzilla.gnome.org/show_bug.cgi?id=603855 -- Evolution mail dont save password keeps asking https://bugs.launchpad.net/bugs/372089 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 493505] Re: [IBM 1834RTG] hibernate/resume failure
** Attachment added: "AlsaDevices.txt" http://launchpadlibrarian.net/36525257/AlsaDevices.txt ** Attachment added: "AplayDevices.txt" http://launchpadlibrarian.net/36525258/AplayDevices.txt ** Attachment added: "ArecordDevices.txt" http://launchpadlibrarian.net/36525259/ArecordDevices.txt ** Attachment added: "BootDmesg.txt" http://launchpadlibrarian.net/36525260/BootDmesg.txt ** Attachment added: "Card0.Amixer.values.txt" http://launchpadlibrarian.net/36525261/Card0.Amixer.values.txt ** Attachment added: "Card0.Codecs.codec97.0.ac97.0.0.txt" http://launchpadlibrarian.net/36525262/Card0.Codecs.codec97.0.ac97.0.0.txt ** Attachment added: "Card0.Codecs.codec97.0.ac97.0.0.regs.txt" http://launchpadlibrarian.net/36525263/Card0.Codecs.codec97.0.ac97.0.0.regs.txt ** Attachment added: "CurrentDmesg.txt" http://launchpadlibrarian.net/36525264/CurrentDmesg.txt ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/36525265/Dependencies.txt ** Attachment added: "IwConfig.txt" http://launchpadlibrarian.net/36525266/IwConfig.txt ** Attachment added: "Lspci.txt" http://launchpadlibrarian.net/36525267/Lspci.txt ** Attachment added: "Lsusb.txt" http://launchpadlibrarian.net/36525268/Lsusb.txt ** Attachment added: "PciMultimedia.txt" http://launchpadlibrarian.net/36525269/PciMultimedia.txt ** Attachment added: "ProcCpuinfo.txt" http://launchpadlibrarian.net/36525270/ProcCpuinfo.txt ** Attachment added: "ProcInterrupts.txt" http://launchpadlibrarian.net/36525271/ProcInterrupts.txt ** Attachment added: "ProcMaps.txt" http://launchpadlibrarian.net/36525272/ProcMaps.txt ** Attachment added: "ProcModules.txt" http://launchpadlibrarian.net/36525273/ProcModules.txt ** Attachment added: "ProcStatus.txt" http://launchpadlibrarian.net/36525275/ProcStatus.txt ** Attachment added: "SleepLog.txt" http://launchpadlibrarian.net/36525276/SleepLog.txt ** Attachment added: "UdevDb.txt" http://launchpadlibrarian.net/36525277/UdevDb.txt ** Attachment added: "UdevLog.txt" http://launchpadlibrarian.net/36525278/UdevLog.txt ** Attachment added: "WifiSyslog.txt" http://launchpadlibrarian.net/36525279/WifiSyslog.txt ** Tags added: kernel-karmic -- [IBM 1834RTG] hibernate/resume failure https://bugs.launchpad.net/bugs/493505 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 493505] [NEW] [IBM 1834RTG] hibernate/resume failure
Public bug reported: Resume from hibernation failed. After startup, Apport indicated a serious kernel problem, exactly as it did for Bug #485108 and Bug #488673 (in the latter, the same window can be seen in attached screenshot, called: Kernel problem screenshot). Can anyone please confirm they all share the same root cause? Is there any foreseeable fix, in the future? I cannot suspend/hibernate or resume anymore, after installing Karmic, and I really need it for work, for I cannot shut down/boot up my machine every day for a number of applications need to stay open and be up and running when I resume my previous session. This is a major regression, it substantially impairs the system reliability for production use. I lost some important data I was working on, this time. This is becoming seriously unpleasant... ProblemType: KernelOops Annotation: This occured during a previous hibernate and prevented it from resuming properly. Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lelamal1334 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'I82801DBICH4'/'Intel 82801DB-ICH4 with AD1981B at irq 5' Mixer name : 'Analog Devices AD1981B' Components : 'AC97a:41445374' Controls : 28 Simple ctrls : 20 Date: Mon Dec 7 10:07:55 2009 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/share/apport/apportcheckresume Failure: hibernate/resume HibernationDevice: RESUME=UUID=f9146e7a-38fe-4080-ab7d-4f0edf647170 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) InterpreterPath: /usr/bin/python2.6 MachineType: IBM 1834RTG Package: linux-image-2.6.31-16-generic 2.6.31-16.52 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-16-generic root=UUID=48cb8a41-2954-41e2-baaa-990c31d64638 ro quiet splash ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume ProcEnviron: PATH=(custom, no user) ProcVersionSignature: Ubuntu 2.6.31-16.52-generic RelatedPackageVersions: linux-backports-modules-2.6.31-16-generic N/A linux-firmware 1.25 RfKill: SourcePackage: linux Tags: resume hibernate Title: [IBM 1834RTG] hibernate/resume failure Uname: Linux 2.6.31-16-generic i686 UserGroups: dmi.bios.date: 12/08/2006 dmi.bios.vendor: IBM dmi.bios.version: 1WET90WW (2.10 ) dmi.board.name: 1834RTG dmi.board.vendor: IBM dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: IBM dmi.chassis.version: Not Available dmi.modalias: dmi:bvnIBM:bvr1WET90WW(2.10):bd12/08/2006:svnIBM:pn1834RTG:pvrThinkPadR50e:rvnIBM:rn1834RTG:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable: dmi.product.name: 1834RTG dmi.product.version: ThinkPad R50e dmi.sys.vendor: IBM ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-kerneloops hibernate i386 kernel-karmic resume -- [IBM 1834RTG] hibernate/resume failure https://bugs.launchpad.net/bugs/493505 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 488673] Re: [IBM 1834RTG] suspend/resume failure
Further to my previous comment, Bug #493505 is joining the list of related bugs. This is getting frustrating. Since the kernel problem reported is serious, can anyone change at least the importance of the bug to medium or higher, please? -- [IBM 1834RTG] suspend/resume failure https://bugs.launchpad.net/bugs/488673 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 485108] Re: [IBM 1834RTG] late resume failure
Further to my previous comment, Bug #493505 is joining the list of related bugs. This is getting frustrating. Since the kernel problem reported is serious, can anyone change at least the importance of the bug to medium or higher, please? -- [IBM 1834RTG] late resume failure https://bugs.launchpad.net/bugs/485108 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 467870] Re: choppy/skipping login sounds upon Karmic boot
I have been getting the same stuttering login on my Thinkpad R50e ever since I did a fresh install of Karmic. libcanberra-pulse is installed. -- choppy/skipping login sounds upon Karmic boot https://bugs.launchpad.net/bugs/467870 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 467870] Re: choppy/skipping login sounds upon Karmic boot
And by the way, just out of curiosity: I remember that at logout/shutdown/restart under Jaunty I got that sort of echoed/reverbered voice saying "Aah!" (should be a keyboard), but haven't heard it in Karmic anymore. Since I haven't read around about its suppression, am I the only one to have lost it, or is it somehow related to this audio problem? Thanks! -- choppy/skipping login sounds upon Karmic boot https://bugs.launchpad.net/bugs/467870 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 422393] Re: nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()
> use apport to open a new bug rather Apport brought me here twice because it identified the problem with this bug, and labelled my bug reports as "nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()" > it might be a different or new issue... If you don't know and Apport can't tell, why and how should I? -- nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID() https://bugs.launchpad.net/bugs/422393 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 422393] Re: nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()
> that's not because the first function matches that the crash is the same I got that the first time. Then again, if Apport brings average users here, they are not aware of the issue at hand, they usually only have a crash and a program to report it that pops up a window with a pre- compiled field. Usually, users tend to trust its ability to identify what caused the crash. If they don't, we may as well doubt every single instance, and report each crash as a separate bug in the event it might be a new issue, regardless of duplicates. > open a new bug and wait for retracing... I'll make sure I do so, as soon as this happens again. These days Ubuntu doesn't fail to crash every other day... -- nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID() https://bugs.launchpad.net/bugs/422393 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 479296] Re: Karmic: frequent freezes
Hi Daniel and all, I'm back just to report that, since I installed linux-backports-modules-alsa-karmic-generic, the issue is no more reproducible at my end. During last week, I only experienced 2 freezes that were somewhat different from those frequent ones already described: one didn't involve any audio, plus I could move the mouse pointer (like described by Simon Nuttall at #7, for example), but nothing else worked; the other happened after logging out, before I could enter my password again (no mouse moving here). No revealing trace was left in the log these times, before freezing. All in all, I can say things are much better now, although I'm not entirely sure that audio was the only cause of the issue, although apparently a major one (at least in my case). Also, I keep reading the same lines in the System Log (as detailed in my report), although I don't worry any longer, after you wrote that the ratelimit messages are not errors. But what about: Nov 3 02:47:30 ECO pulseaudio[1564]: ratelimit.c: 153 events suppressed Nov 3 02:49:19 ECO kernel: [59669.083978] [drm] LVDS-8: set mode 1024x768 d Nov 3 02:49:21 ECO kernel: [59671.086380] [drm] DAC-6: set mode 640x480 0 Nov 3 02:49:22 ECO kernel: [59671.576399] [drm] DAC-6: set mode 640x480 0 Nov 3 02:49:22 ECO kernel: [59672.002693] i2c-adapter i2c-1: unable to read EDID block. They always come together, although I clearly don't understand their origin, nor could I say that they are related to one another. Since 640x480 reminds me of the display resolution (mine is in fact 1024x768), does it have anything to do with the Graphics Device? And may it be responsible for the freezes? Many thanks again. -- Karmic: frequent freezes https://bugs.launchpad.net/bugs/479296 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 352150] Re: ipw2200: Firmware error detected. Restarting
Had this nuisance on Jaunty, and, to my surprise, find it still present on Karmic. Yet it was not on Intrepid. A new release should always bring more improvements than regressions, especially in areas like connectivity where Linux should shine brighter! When you get disconnected every so often, would you call it a stable release? When you're forced to google around for a solution rather than doing your things, would you say it's ready for production? Wouldn't it be better to just wait longer and have everything fixed before every release? -- ipw2200: Firmware error detected. Restarting https://bugs.launchpad.net/bugs/352150 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 485108] [NEW] [IBM 1834RTG] late resume failure
Public bug reported: I have a Thinkpad R50e, and resuming from Suspend mode was a flawless operation under Intrepid and Jaunty. When Karmic was released last October, I did a fresh install, and now my laptop never actually suspends. It tries to, indeed, but then I see the flashing sleep indicator (the half-moon-shaped led) which is already weird per se, for it usually just lit and stay so throughout sleep mode. However, as anticipated, it won't sleep: instead, the fan will continue to run, and overall I can tell all applications are still running there, behind the black screen. Only, I can't access any of them, and the computer never responds to anything but a cold reboot. So, I can't actually suspend nor resume anything. Judging by similar bug reports on Launchpad, and by threads like this one http://ubuntuforums.org/showthread.php?t=1309440, one would think it is an issue mainly affecting Thinkpad/IBM machines. ProblemType: KernelOops Annotation: This occured during a previous suspend and prevented it from resuming properly. The resume processing hung very near the end and will have appeared to have completed normally. Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lelamal1506 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'I82801DBICH4'/'Intel 82801DB-ICH4 with AD1981B at irq 5' Mixer name : 'Analog Devices AD1981B' Components : 'AC97a:41445374' Controls : 28 Simple ctrls : 20 Date: Thu Nov 19 00:53:12 2009 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/share/apport/apportcheckresume Failure: late resume HibernationDevice: RESUME=UUID=f9146e7a-38fe-4080-ab7d-4f0edf647170 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) InterpreterPath: /usr/bin/python2.6 Lsusb: Bus 001 Device 002: ID 0930:6545 Toshiba Corp. Kingston DataTraveler 2.0 Stick (4GB) / PNY Attache 4GB Stick Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: IBM 1834RTG Package: linux-image-2.6.31-14-generic 2.6.31-14.48 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-14-generic root=UUID=48cb8a41-2954-41e2-baaa-990c31d64638 ro quiet splash ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume ProcEnviron: PATH=(custom, no user) ProcVersionSignature: Ubuntu 2.6.31-14.48-generic RelatedPackageVersions: linux-backports-modules-2.6.31-14-generic N/A linux-firmware 1.24 RfKill: SourcePackage: linux Tags: resume suspend resume-late-hang Title: [IBM 1834RTG] late resume failure Uname: Linux 2.6.31-14-generic i686 UserGroups: dmi.bios.date: 12/08/2006 dmi.bios.vendor: IBM dmi.bios.version: 1WET90WW (2.10 ) dmi.board.name: 1834RTG dmi.board.vendor: IBM dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: IBM dmi.chassis.version: Not Available dmi.modalias: dmi:bvnIBM:bvr1WET90WW(2.10):bd12/08/2006:svnIBM:pn1834RTG:pvrThinkPadR50e:rvnIBM:rn1834RTG:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable: dmi.product.name: 1834RTG dmi.product.version: ThinkPad R50e dmi.sys.vendor: IBM ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-kerneloops i386 resume resume-late-hang suspend -- [IBM 1834RTG] late resume failure https://bugs.launchpad.net/bugs/485108 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 485108] Re: [IBM 1834RTG] late resume failure
** Attachment added: "AlsaDevices.txt" http://launchpadlibrarian.net/35839446/AlsaDevices.txt ** Attachment added: "AplayDevices.txt" http://launchpadlibrarian.net/35839447/AplayDevices.txt ** Attachment added: "ArecordDevices.txt" http://launchpadlibrarian.net/35839448/ArecordDevices.txt ** Attachment added: "BootDmesg.txt" http://launchpadlibrarian.net/35839449/BootDmesg.txt ** Attachment added: "Card0.Amixer.values.txt" http://launchpadlibrarian.net/35839450/Card0.Amixer.values.txt ** Attachment added: "Card0.Codecs.codec97.0.ac97.0.0.txt" http://launchpadlibrarian.net/35839451/Card0.Codecs.codec97.0.ac97.0.0.txt ** Attachment added: "Card0.Codecs.codec97.0.ac97.0.0.regs.txt" http://launchpadlibrarian.net/35839452/Card0.Codecs.codec97.0.ac97.0.0.regs.txt ** Attachment added: "CurrentDmesg.txt" http://launchpadlibrarian.net/35839453/CurrentDmesg.txt ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/35839454/Dependencies.txt ** Attachment added: "IwConfig.txt" http://launchpadlibrarian.net/35839455/IwConfig.txt ** Attachment added: "Lspci.txt" http://launchpadlibrarian.net/35839456/Lspci.txt ** Attachment added: "PciMultimedia.txt" http://launchpadlibrarian.net/35839457/PciMultimedia.txt ** Attachment added: "ProcCpuinfo.txt" http://launchpadlibrarian.net/35839458/ProcCpuinfo.txt ** Attachment added: "ProcInterrupts.txt" http://launchpadlibrarian.net/35839459/ProcInterrupts.txt ** Attachment added: "ProcMaps.txt" http://launchpadlibrarian.net/35839460/ProcMaps.txt ** Attachment added: "ProcModules.txt" http://launchpadlibrarian.net/35839461/ProcModules.txt ** Attachment added: "ProcStatus.txt" http://launchpadlibrarian.net/35839462/ProcStatus.txt ** Attachment added: "ResumeHangLog.txt" http://launchpadlibrarian.net/35839463/ResumeHangLog.txt ** Attachment added: "SleepLog.txt" http://launchpadlibrarian.net/35839464/SleepLog.txt ** Attachment added: "UdevDb.txt" http://launchpadlibrarian.net/35839465/UdevDb.txt ** Attachment added: "UdevLog.txt" http://launchpadlibrarian.net/35839466/UdevLog.txt ** Attachment added: "WifiSyslog.txt" http://launchpadlibrarian.net/35839467/WifiSyslog.txt -- [IBM 1834RTG] late resume failure https://bugs.launchpad.net/bugs/485108 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 510443] Re: external usb hard drive unmounts and remounts automatically
I have further tested this issue with no luck, but can exclude the drive is faulty. I can use it satisfactorily for any other purpose (watching films, listening to music, transferring data, etc.) and it never unmounts, not even when not downloading or downloading from aMule only. This is what I attempted so far: - It has an EXT4 file system, checked the disc for bad sectors, but the remapping did not solve the issue. - I removed from Transmission all shared torrents, so that users would download only from the files I was also downloading, thus avoiding to heavily uploads to numerous users connected to me. - I've searched the forums, but it's a mess, and no precisely identifiable pattern is to be found: some say it's a HD failure, some the electrical charge to the USB port, etc. I changed USB port, swapping it with the 2nd external HD, but still it's the one used by Transmission to unmount, so it's not the USB port. - I swapped the USB cables of the two hard-drives: if it was the cable, the HD should have stopped unmounting by itself. But it didn't. Also, one thing I noticed is that when I use the auto-remounted drive, new files and folders are not found unless I hit refresh. And those freshly deleted still are displayed, and if I try to access them then I am presented with an error. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- external usb hard drive unmounts and remounts automatically https://bugs.launchpad.net/bugs/510443 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 510443] Re: external usb hard drive unmounts and remounts automatically
I've just had one of these events, and this is what the System Log says when it happened: Apr 13 12:24:54 EGO kernel: [ 6581.016032] usb 1-4: reset high speed USB device using ehci_hcd and address 8 Apr 13 12:24:54 EGO kernel: [ 6581.148126] usb 1-4: device firmware changed Apr 13 12:24:54 EGO kernel: [ 6581.148209] sd 3:0:0:0: [sdc] Unhandled error code Apr 13 12:24:54 EGO kernel: [ 6581.148213] sd 3:0:0:0: [sdc] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK Apr 13 12:24:54 EGO kernel: [ 6581.148313] sd 3:0:0:0: [sdc] Unhandled error code Apr 13 12:24:54 EGO kernel: [ 6581.148316] sd 3:0:0:0: [sdc] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK Apr 13 12:24:54 EGO kernel: [ 6581.148475] sd 3:0:0:0: [sdc] Unhandled error code Apr 13 12:24:54 EGO kernel: [ 6581.148478] sd 3:0:0:0: [sdc] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK Apr 13 12:24:54 EGO kernel: [ 6581.150660] usb 1-4: USB disconnect, address 8 Apr 13 12:24:54 EGO kernel: [ 6581.202462] JBD2: Detected IO errors while flushing file data on sdc1:8 Apr 13 12:24:54 EGO kernel: [ 6581.329042] usb 1-4: new high speed USB device using ehci_hcd and address 10 Apr 13 12:24:54 EGO kernel: [ 6581.462753] usb 1-4: configuration #1 chosen from 1 choice Apr 13 12:24:54 EGO kernel: [ 6581.465131] scsi5 : SCSI emulation for USB Mass Storage devices Apr 13 12:24:59 EGO kernel: [ 6586.479452] scsi 5:0:0:0: Direct-Access ST336032 0AS PQ: 0 ANSI: 2 CCS Apr 13 12:24:59 EGO kernel: [ 6586.480083] sd 5:0:0:0: Attached scsi generic sg3 type 0 Apr 13 12:24:59 EGO kernel: [ 6586.552303] sd 5:0:0:0: [sde] 703282608 512-byte logical blocks: (360 GB/335 GiB) Apr 13 12:24:59 EGO kernel: [ 6586.553443] sd 5:0:0:0: [sde] Write Protect is off Apr 13 12:24:59 EGO kernel: [ 6586.555047] sde: sde1 Apr 13 12:24:59 EGO kernel: [ 6586.570930] sd 5:0:0:0: [sde] Attached SCSI disk Apr 13 12:25:01 EGO kernel: [ 6588.008735] EXT4-fs (sde1): barriers enabled Apr 13 12:25:04 EGO kernel: [ 6591.195393] kjournald2 starting: pid 5619, dev sde1:8, commit interval 5 seconds Apr 13 12:25:04 EGO kernel: [ 6591.195487] EXT4-fs (sde1): warning: mounting fs with errors, running e2fsck is recommended Apr 13 12:25:04 EGO kernel: [ 6591.199964] EXT4-fs (sde1): internal journal on sde1:8 Apr 13 12:25:04 EGO kernel: [ 6591.199971] EXT4-fs (sde1): delayed allocation enabled Apr 13 12:25:04 EGO kernel: [ 6591.199975] EXT4-fs: file extents enabled Apr 13 12:25:04 EGO kernel: [ 6591.200758] EXT4-fs: mballoc enabled Apr 13 12:25:04 EGO kernel: [ 6591.200783] EXT4-fs (sde1): recovery complete Apr 13 12:25:04 EGO kernel: [ 6591.202730] EXT4-fs (sde1): mounted filesystem with ordered data mode Does anybody know if any of this is useful at all? I can provide any other detail on request. Many thanks. -- external usb hard drive unmounts and remounts automatically https://bugs.launchpad.net/bugs/510443 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 562987] [NEW] [ASUSTeK Computer Inc. P4P800] late resume failure
Public bug reported: After startup and login I received a notification from Apport that informed me of a "serious kernel problem", which I'm now uploading here. Apparently, everything is working fine nonetheless up to now. ProblemType: KernelOops Annotation: This occured during a previous suspend and prevented it from resuming properly. The resume processing hung very near the end and will have appeared to have completed normally. Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lelamal1990 F pulseaudio /dev/snd/seq:timidity 1831 F timidity CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Live'/'SB Live! Value [CT4670] (rev.8, serial:0x201102) at 0xdf80, irq 21' Mixer name : 'SigmaTel STAC9721,23' Components : 'AC97a:83847609' Controls : 220 Simple ctrls : 42 Date: Wed Apr 14 14:13:16 2010 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/share/apport/apportcheckresume Failure: late resume HibernationDevice: RESUME=UUID=046961b7-6220-47c8-963f-4f517643c8f3 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) InterpreterPath: /usr/bin/python2.6 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux-image-2.6.31-20-generic 2.6.31-20.58 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-20-generic root=UUID=fee8967a-0c96-4621-a424-2f3ed9ea5677 ro quiet splash ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume ProcEnviron: PATH=(custom, no user) ProcVersionSignature: Ubuntu 2.6.31-20.58-generic RelatedPackageVersions: linux-backports-modules-2.6.31-20-generic N/A linux-firmware 1.26 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SleepLog: SourcePackage: linux Tags: resume suspend resume-late-hang Title: [To Be Filled By O.E.M. To Be Filled By O.E.M.] late resume failure Uname: Linux 2.6.31-20-generic i686 UserGroups: dmi.bios.date: 07/21/2003 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1009.008 dmi.board.name: P4P800 dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1009.008:bd07/21/2003:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASUSTeKComputerInc.:rnP4P800:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-kerneloops i386 resume resume-late-hang suspend -- [ASUSTeK Computer Inc. P4P800] late resume failure https://bugs.launchpad.net/bugs/562987 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 562987] Re: [ASUSTeK Computer Inc. P4P800] late resume failure
** Attachment added: "AlsaDevices.txt" http://launchpadlibrarian.net/44146414/AlsaDevices.txt ** Attachment added: "AplayDevices.txt" http://launchpadlibrarian.net/44146415/AplayDevices.txt ** Attachment added: "ArecordDevices.txt" http://launchpadlibrarian.net/44146416/ArecordDevices.txt ** Attachment added: "BootDmesg.txt" http://launchpadlibrarian.net/44146417/BootDmesg.txt ** Attachment added: "Card0.Amixer.values.txt" http://launchpadlibrarian.net/44146418/Card0.Amixer.values.txt ** Attachment added: "Card0.Codecs.codec97.0.ac97.0.0.txt" http://launchpadlibrarian.net/44146419/Card0.Codecs.codec97.0.ac97.0.0.txt ** Attachment added: "Card0.Codecs.codec97.0.ac97.0.0.regs.txt" http://launchpadlibrarian.net/44146420/Card0.Codecs.codec97.0.ac97.0.0.regs.txt ** Attachment added: "CurrentDmesg.txt" http://launchpadlibrarian.net/44146421/CurrentDmesg.txt ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/44146422/Dependencies.txt ** Attachment added: "IwConfig.txt" http://launchpadlibrarian.net/44146423/IwConfig.txt ** Attachment added: "Lspci.txt" http://launchpadlibrarian.net/44146424/Lspci.txt ** Attachment added: "Lsusb.txt" http://launchpadlibrarian.net/44146426/Lsusb.txt ** Attachment added: "PciMultimedia.txt" http://launchpadlibrarian.net/44146427/PciMultimedia.txt ** Attachment added: "ProcCpuinfo.txt" http://launchpadlibrarian.net/44146428/ProcCpuinfo.txt ** Attachment added: "ProcInterrupts.txt" http://launchpadlibrarian.net/44146429/ProcInterrupts.txt ** Attachment added: "ProcMaps.txt" http://launchpadlibrarian.net/44146430/ProcMaps.txt ** Attachment added: "ProcModules.txt" http://launchpadlibrarian.net/44146431/ProcModules.txt ** Attachment added: "ProcStatus.txt" http://launchpadlibrarian.net/44146432/ProcStatus.txt ** Attachment added: "ResumeHangLog.txt" http://launchpadlibrarian.net/44146433/ResumeHangLog.txt ** Attachment added: "UdevDb.txt" http://launchpadlibrarian.net/44146434/UdevDb.txt ** Attachment added: "UdevLog.txt" http://launchpadlibrarian.net/44146435/UdevLog.txt ** Attachment added: "WifiSyslog.txt" http://launchpadlibrarian.net/44146436/WifiSyslog.txt -- [ASUSTeK Computer Inc. P4P800] late resume failure https://bugs.launchpad.net/bugs/562987 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 535079] Re: Xorg crashed with SIGSEGV
*** This bug is a duplicate of bug 448864 *** https://bugs.launchpad.net/bugs/448864 > Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. I would, if it wasn't private. -- Xorg crashed with SIGSEGV https://bugs.launchpad.net/bugs/535079 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 1] Re: Microsoft has a majority market share
@lowlux: Amen! My thoughts entirely. Besides, changes like those are no improvement over usability whatsoever, on the contrary, they alienate users (especially newly migrated ones), and ultimately is, in my opinion, a total waste of resources. Fixing bugs would perhaps be a more effective policy, on the long run. -- Microsoft has a majority market share https://bugs.launchpad.net/bugs/1 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1] Re: Microsoft has a majority market share
@»John«: hey man, relax! Insults and verbal aggression are of no use in conversations, and don't add anything to the point you're trying to make. We're all entitled to our opinions, and although also your line of thought may as well sound full of $h:eet to your listeners' ears, well you must still be free to make your point without anyone telling you what to think, what to say, or how many times you should think before you even say that. Besides, we all (well, many of us did, at least) signed Ubuntu Code of Conduct (http://www.ubuntu.com/community/conduct), so we all should be more respectful and learn to consult others when we disagree, because - "surprise" - that may help "resolve disagreements and differing views constructively". Take care (and a deep breath)! -- Microsoft has a majority market share https://bugs.launchpad.net/bugs/1 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 533063] Re: transmission crashed with SIGSEGV in g_signal_emit_valist()
It was a one time shot, as far as I can remember. But then again, I stopped using Transmission, so I can't be sure. -- transmission crashed with SIGSEGV in g_signal_emit_valist() https://bugs.launchpad.net/bugs/533063 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 591849] [NEW] Application calling GLX 1.3 function "glXCreatePixmap" when GLX 1.3 is not supported!
Public bug reported: Binary package hint: metacity After upgrading to Maverick, Compiz stopped working, and Metacity is used as a fallback window manager. From Terminal, I get: compiz --replace WARNING: Application calling GLX 1.3 function "glXCreatePixmap" when GLX 1.3 is not supported! This is an application bug! WARNING: Application calling GLX 1.3 function "glXDestroyPixmap" when GLX 1.3 is not supported! This is an application bug! Launching fallback window manager I believe it's Bug #433488, but I didn't post there because last comment invited to open new bugs since that particular one was fixed. My graphics card is: lspci | grep VGA 00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02) Please, let me know if more details are needed. ** Affects: metacity (Ubuntu) Importance: Undecided Status: New -- Application calling GLX 1.3 function "glXCreatePixmap" when GLX 1.3 is not supported! https://bugs.launchpad.net/bugs/591849 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 485108] Re: [IBM 1834RTG] late resume failure
I upgraded to Lucid, and the suspend issue seemed to have been fixed. However, I cannot be sure, for I couldn't remain on Lucid for long, due to the problems with Intel chipsets best described here: http://www.ubuntugeek.com/ubuntu-10-04-lucid-lynx-and-intel-video- chipsets.html. I was suggested to upgrade to Maverick if I wanted to avoid booting from a regressed kernel, and so I did. That finally solved the black screen issue. But I'm here to report that the issue of the present bug I reported in November against Karmic is still affecting me on Kernel 2.6.35-2, using fully updated Maverick. We would need somebody who was affected on Karmic to report whether it is still occurring on Lucid, so as to understand if this is a regression of the new kernel. Thanks. -- [IBM 1834RTG] late resume failure https://bugs.launchpad.net/bugs/485108 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 485108] Re: [IBM 1834RTG] late resume failure
Oh, and by the way, hibernate mode seems to work properly. -- [IBM 1834RTG] late resume failure https://bugs.launchpad.net/bugs/485108 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 357673] Re: No notification when sliding audio volume, muting volume on ThinkPad X23, X24, X31, X32, X41, X60, T22, T40, T42, T60, R50e, R51, R52
This issue is still active on Maverick, fully up-to-date, kernel 2.6.35-2, on a Thinkpad R50e. -- No notification when sliding audio volume, muting volume on ThinkPad X23, X24, X31, X32, X41, X60, T22, T40, T42, T60, R50e, R51, R52 https://bugs.launchpad.net/bugs/357673 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 510443] Re: external usb hard drive unmounts and remounts automatically
Hi, I think I've solved this issue, at least for me. It's rather silly, and don't fully understand how it works, but actually it does, which is all that matters. I remembered I recently started switching the hard drive off at night, so as to try speeding up booting the following morning, i.e. without the system having to detect external devices in the process, and then to switch it on after login. I wondered if that might be the reason of this issue, and tried not to switch it off anymore. Well, the issue has gone for over a month, and that's remarkable, considering the drive used to unmount on a daily basis. I don't know if it is going to help anybody, for in my case it seems it was hardware-related, but anyway I wanted to share. -- external usb hard drive unmounts and remounts automatically https://bugs.launchpad.net/bugs/510443 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 583891] Re: X.org crashes sometimes. [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -12!
This also happens on Kubuntu, not using firefox. It can happen with different applications showing graphics, such as Akregator, Konqueror, etc. I found that you can actually predict when X is going to crash and bring you straight to login screen, because characters within the window start to be replaced by senseless symbols; or images within the frame of the window turn into thick coloured horizontal stripes. Whenever I see that, I immediately close the window in question, and go check the System log, which invariably shows such messages as: 2010-06-04 14:58:08 EGO kernel [20138.652499] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -12! 2010-06-04 14:58:08 EGO kernel [20139.291065] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -12! 2010-06-04 14:58:09 EGO kernel [20139.797174] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -12! I found that this prevents crashes, and interruption to normal workflow. Still, it's merely a temporary workaround that doesn't solve the issue. -- X.org crashes sometimes. [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -12! https://bugs.launchpad.net/bugs/583891 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 591322] [NEW] empathy_pixbuf_from_icon_name_sized: Error loading icon
Public bug reported: Binary package hint: empathy I've removed indicator-massages from a netbook for I didn't use this feature, so I could save space. Now that Empathy sits in the notification area, whenever I receive a message, its icon starts blinking between the normal icon and an ugly icon, i.e. the icon signaling that an icon is missing (please, see screenshot attached). Empathy debug window shows the following message several times throughout the blinking: empathy_pixbuf_from_icon_name_sized: Error loading icon: Icona «notification-message-im» non presente nel tema which basically means that the theme is missing the indicated icon. The behavior occurs both on Ambiance and on Radiance. ** Affects: empathy (Ubuntu) Importance: Undecided Status: New -- empathy_pixbuf_from_icon_name_sized: Error loading icon https://bugs.launchpad.net/bugs/591322 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 591322] Re: empathy_pixbuf_from_icon_name_sized: Error loading icon
** Attachment added: "Schermata.png" http://launchpadlibrarian.net/49955201/Schermata.png -- empathy_pixbuf_from_icon_name_sized: Error loading icon https://bugs.launchpad.net/bugs/591322 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 1] Re: Microsoft has a majority market share
I'm Italian, and wanted to buy a netbook for my mother. At first, I browsed Dell US Website (don't ask me why), for I thought I could buy it from there and have it shipped. I chose an Inspiron Mini 10, which came nicely with Ubuntu pre-installed (although it was an outdated copy which I had to wipe out anyway). I felt so stupid when, after placing my order, I found out it wasn't possible. So, I set out to see if I could find the same deal on the Italian Website. I searched for the word Ubuntu, and a couple of results came out, among which I could see the netbook I was looking for. But when I clicked on it, I saw that any reference to Ubuntu had disappeared. You could only get it with Windows XP installed, and with no way to customise it. So, even though Dell advertises Ubuntu on their machines, they don't actually keep their word, and their offers force you to pay the Window$ tax nonetheless! You can tell they don't actually care at all about Linux for the way the User Manual is written, too. There's only one mention about Ubuntu regarding the installation of the OS: whilst Windows gets half of the page with detailed guidelines, Ubuntu gets two (!) lines where they suggest to refer to the documents delivered with the computer (are they referring to this manual, or talking to the lucky ones that get Ubuntu pre-installed overseas?). Throughout the rest of the Manual, Ubuntu is not targeted at all, while clear explanations are given about Windows, with graphics and detailed descriptions both for XP and 7. Moreover, all references to diagnostics, troubleshooting, drivers, and various applications that come with the machine imply the installation of a Windows OS, and never take into consideration the possibility that users are really on a a Linux OS (let alone Ubuntu). Last but not least, of course, the hideous Windows sticker and the button on the keyboard: how ugly and useless is that for a Linux user? I read yesterday (can't remember where) a nice comment that said something along the lines of: "the Windows meta key says a lot about producers' attention and care for Linux customers". Alex, you don't say which machine you picked in the end, but if it's an Inspiron Mini all I can tell you is Ubuntu Netbook Edition (Lucid Lynx) works flawlessly on it. The first thing I did, out of revenge, was to wipe out the HD and erase every trace of the OS whose license I was forced to buy. However, my only problem was with the wireless connection, because Ubuntu doesn't ship with pre-installed proprietary drivers, and it's an issue when they're for the Broadcom for you will have to use a wired connection in order to download and activate them. Apart from that, no problem at all compatibility-wise. I do agree with you, though: it's a pity in 2010 we still have to go through Window$ and all these shenanigans to run a Linux distribution. If in order to run Ubuntu my mother has to buy WIndows XP, then the present bug will take decades to be fixed... -- Microsoft has a majority market share https://bugs.launchpad.net/bugs/1 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 510443] Re: external usb hard drive unmounts and remounts automatically
Yeah, this is exactly what happens to me, too. Also, I sometimes use aMule along with Transmission. When the drive unmounts, all active files from both applications give an error message, and can't be reactivated unless the programmes are restarted. When they're restarted, each file must be reactivated manually, for they're all paused or stopped - Transmission will verify all local data for those files. In the end, though, I'm not sure what causes the issue, neither if the P2P apps are the culprits here. -- external usb hard drive unmounts and remounts automatically https://bugs.launchpad.net/bugs/510443 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 473401] Re: Visual effect won't start w/ Matrox G450
Same problem here. Any chance we're finally going to see Compiz effects working on our video cards too for the next release? Please? -- Visual effect won't start w/ Matrox G450 https://bugs.launchpad.net/bugs/473401 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 517851] Re: gwibber crashed with AttributeError in on_clear()
Hey thanks! This was the only crash I had concerning this particular bug, so is any data missing? My report was for Karmic, though, and in Karmic "2.0.0~bzr476-0ubuntu3 (karmic)" is the latest stable version available. So shouldn't it be set back to "New"? Thanks. ** Changed in: gwibber (Ubuntu) Status: Incomplete => New -- gwibber crashed with AttributeError in on_clear() https://bugs.launchpad.net/bugs/517851 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 517851] Re: gwibber crashed with AttributeError in on_clear()
Alright thanks for now, will upgrade to Lucid in April. -- gwibber crashed with AttributeError in on_clear() https://bugs.launchpad.net/bugs/517851 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 517740] Re: nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()
** Attachment added: "CoreDump.gz" http://launchpadlibrarian.net/38801238/CoreDump.gz ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/38801239/Dependencies.txt ** Attachment added: "Disassembly.txt" http://launchpadlibrarian.net/38801240/Disassembly.txt ** Attachment added: "ProcMaps.txt" http://launchpadlibrarian.net/38801241/ProcMaps.txt ** Attachment added: "ProcStatus.txt" http://launchpadlibrarian.net/38801242/ProcStatus.txt ** Attachment added: "Registers.txt" http://launchpadlibrarian.net/38801243/Registers.txt ** Attachment added: "Stacktrace.txt" http://launchpadlibrarian.net/38801244/Stacktrace.txt ** Attachment added: "ThreadStacktrace.txt" http://launchpadlibrarian.net/38801245/ThreadStacktrace.txt ** Attachment added: "XsessionErrors.txt" http://launchpadlibrarian.net/38801246/XsessionErrors.txt ** Attachment added: "usr_lib_nautilus.txt" http://launchpadlibrarian.net/38801247/usr_lib_nautilus.txt ** Visibility changed to: Public -- nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID() https://bugs.launchpad.net/bugs/517740 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 422393] Re: nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()
... and again: Bug #517740 -- nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID() https://bugs.launchpad.net/bugs/422393 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 517740] Re: nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()
*** This bug is a duplicate of bug 515495 *** https://bugs.launchpad.net/bugs/515495 > Thank you for taking the time to report this bug. You're welcome. > However, it is a duplicate of bug #515495. And how would I know? If it was up to me to decide, I would have followed Apport, and considered bug #515495 itself to be a duplicate of Bug #422393. However, I have been told that was not the case for the latter was fixed, so I followed his advice. > Even though Sebastien requested you to report > a new bug instead of reopening the old bug, you don't have to create > three. One is enough. One may be enough now, but not before. Again: how would I know when could that have been enough? I had been instructed to use Apport to open a new bug for it might have been a different or new issue... but then I thought that Apport is the same tool whose precision I had been instructed to question and ignore, so I believed it safer to report each new instance of this particular bug and wait for retraicing. In the end, I am an average user, while Sebastien is the expert, and I would never question his word. Anyway, now that I have an official word on the matter, I know it is useless to keep reporting this bug. -- nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID() https://bugs.launchpad.net/bugs/517740 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 516219] Re: nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()
*** This bug is a duplicate of bug 515495 *** https://bugs.launchpad.net/bugs/515495 > Thank you for taking the time to report this bug. You're welcome. > However, it is a duplicate of bug #515495. And how would I know? If it was up to me to decide, I would have followed Apport, and considered bug #515495 itself to be a duplicate of Bug #422393. However, I have been told that was not the case for the latter was fixed, so I followed his advice. > Even though Sebastien requested you to report > a new bug instead of reopening the old bug, you don't have to create > three. One is enough. One may be enough now, but not before. Again: how would I know when could that have been enough? I had been instructed to use Apport to open a new bug for it might have been a different or new issue... but then I thought that Apport is the same tool whose precision I had been instructed to question and ignore, so I believed it safer to report each new instance of this particular bug and wait for retraicing. In the end, I am an average user, while Sebastien is the expert, and I would never question his word. Anyway, now that I have an official word on the matter, I know it is useless to keep reporting this bug. -- nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID() https://bugs.launchpad.net/bugs/516219 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 515495] Re: nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()
... continued from Bug #516219: > lelamal: The point is that bug #422393 was an old bug that was already marked > as Fix Released when you encountered the issue. I have encountered fixed bugs that get confirmed and reopened, if users report that the bug is reoccurring, without them being asked to report new bugs when they submit evidence that might prove the fix did not work. > You were asked to open a new bug so Apport would upload all the log files and > backtraces to Launchpad, allowing us to compare the difference. I see. Then, this makes me wonder: why does Apport even ask to submit the required information to the developers as first thing after the crash, if when you afterwards land on an existing bug such information is not checked nor stored? Both in comment #10 and #11 of bug #422393 I explain I submitted the necessary information - did anybody read them before ruling out the possibility that the issue was reoccurring? Do the information get stored somewhere at all? Otherwise, if all the log files and backtraces submitted to Launchpad get trashed, would it not make more sense if Apport checked the existing bugs FIRST, and then, as a second phase, asked users if they want to submit their data? Since reports range from a couple of KiB to hundreds of MB, would that not be more reasonable, especially for those users who have limited bandwidth and yet care to participate in making Ubuntu better? > Now there is a new bug report open with the debug information attached we > have enough information to go to the next step in the process and verify > whether the old bug returned, or whether you're reporting something new. Good. Still, if Apport really works the other way around, and uploaded data are inexplicably destroyed, I could have re-uploaded the necessary information in the relevant bug as I have seen users doing many times. I understand opening a new bug might be an easier route, yet, considering my first report last November, the whole process is really time consuming. Retaining submitted data could have provided debug material for the developers to work on already 3 months ago. -- nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID() https://bugs.launchpad.net/bugs/515495 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 515495] Re: nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()
Yeah, I know that. I do it everytime the upload fails - mostly when the report exceeds 200 MB. But what does it have to do with what have been discussed? If your reply refers to comment #3, then please allow me to be clearer: 1. Crash 2. Apport: "Oops, let's upload a report to the developers?". Me: "Yay, why not!" 3. Apport uploads, finishes 4. Bug is checked against database of bugs: it is found to already exist 5. I choose not to open new bug, and comment in existing one 6. I am told to open a new bug nonetheless 7. I do so 8. I am explained the new bug had to be opened to upload its log files and backtraces 9. I wonder: didn't I already upload them back in point 3 (twice)? Does Launchpad trash my data when bug pre-exists? If so, why Apport doesn't check if it pre-exists before point 2 (thus effectively reverting the order of points 2 and 4)? 10. Concise final consideration: if Apport didn't work backwards, or data uploaded to Launchpad wasn't trashed, the whole process would make much more sense, and the 3 months time span between point 3 and point 7 wouldn't have been wasted, for developers would have already had all the necessary information to debug the crash. Many thanks. -- nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID() https://bugs.launchpad.net/bugs/515495 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 34321] Re: should delete the saved session when unmarking automatic session saving option
Apteryx wrote on 2009-08-24: >The bug is still present in Ubuntu 9.10. The procedure to delete the saved session is the same as for Jaunty : rm -R ~/.config/gnome-session /saved-session I thought this was a brilliant solution which finally could help me solve this issue with Tomboy. And probably it is, on others' systems. But unfortunately, it failed like other solutions listed here and in other fora (uninstalling Tomboy included). Then I bumped into this page - http://www.simmerspaintshop.com/forums/blogs/adlabs6/80-tomboy-notes- open-login-startup.html - which let me understood why the hell Tomboy was so stubborn: it was the Deskbar-applet which I added to my panel a couple of weeks ago to fire up Tomboy at login. Once disabled the relevant option in the applet preferences, it finally stopped. This worked in my case, so it might not apply to yours. However, I wanted to share just in case someone could find it helpful. -- should delete the saved session when unmarking automatic session saving option https://bugs.launchpad.net/bugs/34321 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 411504] Re: evolution crashes when trying to save an appoinmment after adding a reccurence
I experience exactly the same behaviour on my system running Jaunty, fully up-to-date. I was about to submit a bug, but then during the procedure I was presented with other instances of the same bug filed (very smart, I had never tried it before!). So I'm here to confirm it. -- evolution crashes when trying to save an appoinmment after adding a reccurence https://bugs.launchpad.net/bugs/411504 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 447140] [NEW] totem crashes when streaming
Public bug reported: Binary package hint: totem I was watching a live event on NASA TV today, and since the video often went black, I wanted to try and play it on Totem (Gstreamer). However, after manually opening Totem, the whole of the screen went just as black, and I couldn't quit it with CTRL+Q, nor with Esc or F11, or anything but a cold restart. I repeated it after reboot, just to reproduce it, and it happened again. If I right-click on the video in Epiphany, and choose "Open with Movie Player (Xine)", then most of the times I am told that there is no suitable plugin, while rarely I can watch the video in the new window. This is all too random for me to get. I have a Thinkpad R50e, running Juanty fully up-to-date. ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 9.04 ExecutablePath: /usr/bin/totem-gstreamer Package: totem-gstreamer 2.26.1-0ubuntu5 ProcEnviron: LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: totem Uname: Linux 2.6.28-15-generic i686 ** Affects: totem (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 -- totem crashes when streaming https://bugs.launchpad.net/bugs/447140 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 447140] Re: totem crashes when streaming
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/33351072/Dependencies.txt ** Attachment added: "ProcMaps.txt" http://launchpadlibrarian.net/33351073/ProcMaps.txt ** Attachment added: "ProcStatus.txt" http://launchpadlibrarian.net/33351074/ProcStatus.txt -- totem crashes when streaming https://bugs.launchpad.net/bugs/447140 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 447196] [NEW] Evolution crashes when setting recurrence for current appointment
Public bug reported: Binary package hint: evolution The bug report I am about to report stems from an exchange began in another report of the same bug that can be found here: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/411504. It seems necessary to open a new report, regardless, so here's mine. Basically, the title above already says it all: whenever an appointment needs to be turned into a recurrent appointment, Evolution crashes as soon as the return key is hit to save it. Using a Thinkpad R50e fully updated running Jaunty. ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 9.04 ExecutablePath: /usr/bin/evolution Package: evolution 2.26.1-0ubuntu2 ProcEnviron: LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: evolution Uname: Linux 2.6.28-15-generic i686 ** Affects: evolution (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 -- Evolution crashes when setting recurrence for current appointment https://bugs.launchpad.net/bugs/447196 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 447196] Re: Evolution crashes when setting recurrence for current appointment
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/33355277/Dependencies.txt ** Attachment added: "ProcMaps.txt" http://launchpadlibrarian.net/33355278/ProcMaps.txt ** Attachment added: "ProcStatus.txt" http://launchpadlibrarian.net/33355279/ProcStatus.txt -- Evolution crashes when setting recurrence for current appointment https://bugs.launchpad.net/bugs/447196 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 411504] Re: evolution crashes when trying to save an appoinmment after adding a reccurence
Hi Robby. I know, I read all this. But when I hit "Report a problem", Apport started the whole procedure by saying first that it was "collecting problem information", then asked me if I wanted to send the problem report to the developers, after which it opened the "report a bug" page, and finally broght me here after I entered the title and was asked whether any of several similar bug reports was actually the one I was trying to enter. Being this my first bug report, I thought Apport had already delivered my problem information to the developers, that it was redundant to file a new bug, and to add my contribution here was more than enough. Since you seem to imply it's not, I'm now filing a new report for the same bug: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/447196. Many thanks! -- evolution crashes when trying to save an appoinmment after adding a reccurence https://bugs.launchpad.net/bugs/411504 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 447463] Re: totem crashes when streaming
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/33370931/Dependencies.txt ** Attachment added: "ProcMaps.txt" http://launchpadlibrarian.net/33370933/ProcMaps.txt ** Attachment added: "ProcStatus.txt" http://launchpadlibrarian.net/33370934/ProcStatus.txt -- totem crashes when streaming https://bugs.launchpad.net/bugs/447463 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 447463] [NEW] totem crashes when streaming
Public bug reported: Binary package hint: totem I was watching a live event on NASA TV today, and since the video often went black, I wanted to try and play it on Totem (Gstreamer). However, after manually opening Totem, the whole of the screen went just as black, and I couldn't quit it with CTRL+Q, nor with Esc or F11, or anything but a cold restart. I repeated it after reboot, just to reproduce it, and it happened again. If I right-click on the video in Epiphany, and choose "Open with Movie Player (Xine)", then most of the times I am told that there is no suitable plugin, while rarely I can watch the video in the new window. This is all too random for me to get. I have a Thinkpad R50e, running Juanty fully up-to-date. ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 9.04 ExecutablePath: /usr/bin/totem-gstreamer Package: totem-gstreamer 2.26.1-0ubuntu5 ProcEnviron: LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: totem Uname: Linux 2.6.28-15-generic i686 ** Affects: totem (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 -- totem crashes when streaming https://bugs.launchpad.net/bugs/447463 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 447463] Re: totem crashes when streaming
Hi Pedro. I'm sure this is an automated message, so I don't know if you'll read this. However, this afternoon I had already reported this bug, and had already got the above message. For this reason, I enabled Apport as indicated, restarted, and reported this very bug. How come my crash report is still "either missing or challenging to deal with as a ".crash" file"? What would that mean, anyway? I followed your steps, andI clearly saw Apport uploading something. Is there any other step I should follow to ensure this bug is properly reported? Many thanks in advance! -- totem crashes when streaming https://bugs.launchpad.net/bugs/447463 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 447196] Re: Evolution crashes when setting recurrence for current appointment
Hi Pedro. I'm sure this is an automated message, so I don't know if you'll read this. However, this afternoon I had already reported this bug, and had already got the above message. For this reason, I enabled Apport as indicated, restarted, and reported this very bug. How come my crash report is still "either missing or challenging to deal with as a ".crash" file"? What would that mean, anyway? I followed your steps, and I clearly saw Apport uploading something. Is there any other step I should follow to ensure this bug is properly reported? Many thanks in advance! -- Evolution crashes when setting recurrence for current appointment https://bugs.launchpad.net/bugs/447196 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 479296] [NEW] Karmic: frequent freezes
Public bug reported: After a fresh install of Karmic I have been experiencing frequent freezes. I haven't applied any workarounds, or added repositories or fancy plugins, and the system is as was out-of-the-box. Most of the times it happens if I listen to music while I do some other operation which involves the use of the mouse and the appearance of some graphical output (a drop-down menu, a new window open, an old one maximised from the system tray, etc.). The combination of these two events most of the times results in the music got stuck on two notes repeated for two or three seconds at short distance intervals, then everything gets back to normal. Other times I'm not so lucky, and the sound (most times music, but can just as well be system notifications or the likes) keeps going on forever in a loop, and the only thing to stop it is a cold reboot. The computer becomes totally unresponsive, nothing works, not even the mouse or the power button (set to Shutdown in the Power Management Preferences). Video itself, however, never gave me problems of any sort, that is I've been playing movies and the system never froze. Anyway, I never had these problems on Intrepid or Jaunty running on the same hardware. In the System Log messages, last entries before freezes usually report variations of the following: Nov 2 12:07:06 ECO pulseaudio[1564]: ratelimit.c: 159 events suppressed Nov 2 12:27:48 ECO pulseaudio[1564]: ratelimit.c: 149 events suppressed Nov 2 12:28:23 ECO pulseaudio[1564]: ratelimit.c: 68 events suppressed Nov 2 13:49:25 ECO pulseaudio[1564]: ratelimit.c: 165 events suppressed Nov 2 14:16:36 ECO pulseaudio[1564]: ratelimit.c: 158 events suppressed Nov 2 14:44:56 ECO pulseaudio[1564]: ratelimit.c: 32 events suppressed Nov 2 14:45:06 ECO pulseaudio[1564]: ratelimit.c: 31 events suppressed Nov 2 14:58:38 ECO pulseaudio[1564]: ratelimit.c: 35 events suppressed Nov 2 15:41:22 ECO pulseaudio[1564]: ratelimit.c: 156 events suppressed Nov 2 15:51:33 ECO pulseaudio[1564]: ratelimit.c: 149 events suppressed Nov 2 15:54:12 ECO pulseaudio[1564]: ratelimit.c: 141 events suppressed Nov 2 16:01:17 ECO pulseaudio[1564]: ratelimit.c: 152 events suppressed Nov 2 16:04:33 ECO pulseaudio[1564]: ratelimit.c: 105 events suppressed Nov 2 16:07:33 ECO pulseaudio[1564]: ratelimit.c: 76 events suppressed Nov 2 16:50:53 ECO pulseaudio[1564]: ratelimit.c: 108 events suppressed Nov 2 17:17:22 ECO pulseaudio[1564]: ratelimit.c: 65 events suppressed Nov 2 17:39:09 ECO pulseaudio[1564]: ratelimit.c: 143 events suppressed Nov 2 17:48:51 ECO pulseaudio[1564]: ratelimit.c: 161 events suppressed Nov 2 18:16:49 ECO pulseaudio[1564]: ratelimit.c: 137 events suppressed Nov 2 18:43:58 ECO pulseaudio[1564]: ratelimit.c: 129 events suppressed Nov 2 18:47:36 ECO pulseaudio[1564]: ratelimit.c: 155 events suppressed Nov 2 19:35:40 ECO pulseaudio[1564]: ratelimit.c: 173 events suppressed Nov 2 19:37:20 ECO pulseaudio[1564]: ratelimit.c: 88 events suppressed Nov 2 19:39:23 ECO pulseaudio[1564]: ratelimit.c: 66 events suppressed Nov 2 20:09:16 ECO pulseaudio[1564]: ratelimit.c: 159 events suppressed Nov 2 22:52:33 ECO pulseaudio[1564]: ratelimit.c: 81 events suppressed Nov 3 00:33:33 ECO pulseaudio[1564]: ratelimit.c: 62 events suppressed Nov 3 00:39:26 ECO pulseaudio[1564]: ratelimit.c: 76 events suppressed Nov 3 02:17:41 ECO pulseaudio[1564]: ratelimit.c: 161 events suppressed Nov 3 02:47:30 ECO pulseaudio[1564]: ratelimit.c: 153 events suppressed Nov 3 02:49:19 ECO kernel: [59669.083978] [drm] LVDS-8: set mode 1024x768 d Nov 3 02:49:21 ECO kernel: [59671.086380] [drm] DAC-6: set mode 640x480 0 Nov 3 02:49:22 ECO kernel: [59671.576399] [drm] DAC-6: set mode 640x480 0 Nov 3 02:49:22 ECO kernel: [59672.002693] i2c-adapter i2c-1: unable to read EDID block. Nov 3 02:49:22 ECO kernel: [59672.002699] i915 :00:02.0: LVDS-1: no EDID data Nov 3 02:49:22 ECO kernel: [59672.073907] [drm] DAC-6: set mode 640x480 0 Nov 3 02:49:23 ECO kernel: [59672.565154] [drm] DAC-6: set mode 640x480 0 Nov 3 02:49:23 ECO kernel: [59673.016260] i2c-adapter i2c-1: unable to read EDID block. Nov 3 02:49:23 ECO kernel: [59673.016265] i915 :00:02.0: LVDS-1: no EDID data Nov 3 02:49:26 ECO kernel: [59675.919048] [drm] DAC-6: set mode 640x480 0 Nov 3 02:49:27 ECO kernel: [59676.409317] [drm] DAC-6: set mode 640x480 0 Nov 3 02:49:27 ECO kernel: [59676.834220] i2c-adapter i2c-1: unable to read EDID block. Nov 3 02:49:27 ECO kernel: [59676.834226] i915 :00:02.0: LVDS-1: no EDID data Nov 3 02:49:27 ECO kernel: [59676.913321] [drm] DAC-6: set mode 640x480 0 Nov 3 02:49:27 ECO kernel: [59677.403661] [drm] DAC-6: set mode 640x480 0 Nov 3 02:49:28 ECO kernel: [59677.829195] i2c-adapter i2c-1: unable to read EDID block. Nov 3 02:49:28 ECO kernel: [59677.829201] i915 :00:02.0: LVDS-1: no EDID data Nov 3 02:49:28 ECO kernel: [59677.941029] [drm] DAC-6: set mode 640x480 0 Nov 3 02:49:29 ECO kernel: [59678.432021] [drm] DAC-6: set mode 640x480 0 Nov 3 02:49:29 ECO k
[Bug 479296] Re: Karmic: frequent freezes
Hi Daniel. If you're asking me, I don't have a clue what "linux- backports-modules-alsa-karmic-generic" is. I've never reproduced an issue, but just reported bugs through Apport. The system just freezes randomly. What should I do exactly? -- Karmic: frequent freezes https://bugs.launchpad.net/bugs/479296 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
