[Bug 611188] Re: Server disk was reverted as it were 3 months ago. How?

Just curious. Logs for one of the vservers were reseted in strange ways: Jun 21 01:00:01 azul-batch CRON[5607]: pam_unix(cron:session): session opened for user talend by (uid=0) Jun 21 01:17:01 azul-batch CRON[5682]: pam_unix(cron:session): session opened for user root by (uid=0) Jun 21

[Bug 611188] Re: Server disk was reverted as it were 3 months ago. How?

Hardware machine logs are even more strange for me. Kern.log: This is last log before today... There are only those entries in the whole log! Jul 4 00:57:01 azul-manager kernel: [730178.213562] md: data-check of RAID array md0 Jul 4 00:57:01 azul-manager kernel: [730178.213571] md: minimum

[Bug 611188] Re: Server disk was reverted as it were 3 months ago. How?

I've setup sensors to check temperatures... Because numbers afraid me... The room is not cooled and gets warm. -- Server disk was reverted as it were 3 months ago. How? https://bugs.launchpad.net/bugs/611188 You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 611188] Re: Server disk was reverted as it were 3 months ago. How?

I forgot to say that server was down because a power outage. It happend 3 times in the afternoon but the server is backed up by an UPS. The UPS finally went off at 15:10:01 as logs shows off: syslog.1 before and after power outage: Jul 27 15:08:03 azul-manager smartd[1967]: Device: /dev/sdb,

[Bug 611188] Re: Server disk was reverted as it were 3 months ago. How?

File system information about disk recovery after crash: Jul 28 10:12:08 azul-manager kernel: [3.707011] EXT4-fs (sde1): INFO: recovery required on readonly filesystem Jul 28 10:12:08 azul-manager kernel: [3.707015] EXT4-fs (sde1): write access will be enabled during recovery Jul 28

[Bug 611188] Re: Server disk was reverted as it were 3 months ago. How?

Hi Danny, I agree with you. I don't see what can cause disks going 3-4 months ago. About the disk that can fail. It's not related as is a stand alone disk that holds the OS of the hardware machine. I backup configurations just in case it fails to recover the whole thing as fast as possible. So I

[Bug 611188] Re: Server disk was reverted as it were 3 months ago. How?

I forgot to say. About NAS incident (Files not copied there). The only reason can be a NFS error. But I don't understand why the database was copied successfully. If a filesystem export fails then the other should also fail. Strange though -- Server disk was reverted as it were 3 months ago.

[Bug 611188] Re: Server disk was reverted as it were 1 months ago. How?

** Summary changed: - Server disk was reverted as it were 3 months ago. How? + Server disk was reverted as it were 1 months ago. How? ** Summary changed: - Server disk was reverted as it were 1 months ago. How? + Server disk was reverted as it were 1 month ago. How? -- Server disk was

[Bug 611188] Re: Server disk was reverted as it were 1 month ago. How?

Hi Danny, I didn't know that. Then I will take a heavy day looking for the problem. Only KVM problems, filesystem and LVM problems can cause this... I will check them out. If you realize that something can help, please don't doubt to tell me. Thank you. -- Server disk was reverted as it were 1

[Bug 577107] Re: Mouse is lost on X because driver resync

apport information ** Tags added: apport-collected ** Description changed: Sometimes mouse is lost on X. I mean mouse cursor is there and I can move it but buttons got misconfigured/unconfigured. I suffer from this problem since kernel 2.6.8 at least. I never found a reason and the

[Bug 577107] CurrentDmesg.txt

apport information ** Attachment added: CurrentDmesg.txt http://launchpadlibrarian.net/49121644/CurrentDmesg.txt -- Mouse is lost on X because driver resync https://bugs.launchpad.net/bugs/577107 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct

[Bug 577107] Dependencies.txt

apport information ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/49121645/Dependencies.txt -- Mouse is lost on X because driver resync https://bugs.launchpad.net/bugs/577107 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct

[Bug 577107] DkmsStatus.txt

apport information ** Attachment added: DkmsStatus.txt http://launchpadlibrarian.net/49121646/DkmsStatus.txt -- Mouse is lost on X because driver resync https://bugs.launchpad.net/bugs/577107 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct

[Bug 577107] GdmLog.txt

apport information ** Attachment added: GdmLog.txt http://launchpadlibrarian.net/49121648/GdmLog.txt -- Mouse is lost on X because driver resync https://bugs.launchpad.net/bugs/577107 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber.

[Bug 577107] GdmLog1.txt

apport information ** Attachment added: GdmLog1.txt http://launchpadlibrarian.net/49121649/GdmLog1.txt -- Mouse is lost on X because driver resync https://bugs.launchpad.net/bugs/577107 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber.

[Bug 577107] GdmLog2.txt

apport information ** Attachment added: GdmLog2.txt http://launchpadlibrarian.net/49121650/GdmLog2.txt -- Mouse is lost on X because driver resync https://bugs.launchpad.net/bugs/577107 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber.

[Bug 577107] Lspci.txt

apport information ** Attachment added: Lspci.txt http://launchpadlibrarian.net/49121652/Lspci.txt -- Mouse is lost on X because driver resync https://bugs.launchpad.net/bugs/577107 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. --

[Bug 577107] Lsusb.txt

apport information ** Attachment added: Lsusb.txt http://launchpadlibrarian.net/49121653/Lsusb.txt -- Mouse is lost on X because driver resync https://bugs.launchpad.net/bugs/577107 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. --

[Bug 577107] PciDisplay.txt

apport information ** Attachment added: PciDisplay.txt http://launchpadlibrarian.net/49121655/PciDisplay.txt -- Mouse is lost on X because driver resync https://bugs.launchpad.net/bugs/577107 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct

[Bug 577107] ProcCpuinfo.txt

apport information ** Attachment added: ProcCpuinfo.txt http://launchpadlibrarian.net/49121657/ProcCpuinfo.txt -- Mouse is lost on X because driver resync https://bugs.launchpad.net/bugs/577107 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct

[Bug 577107] ProcModules.txt

apport information ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/49121659/ProcModules.txt -- Mouse is lost on X because driver resync https://bugs.launchpad.net/bugs/577107 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct

[Bug 577107] ProcInterrupts.txt

apport information ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/49121658/ProcInterrupts.txt -- Mouse is lost on X because driver resync https://bugs.launchpad.net/bugs/577107 You received this bug notification because you are a member of Ubuntu Bugs, which is a

[Bug 577107] RelatedPackageVersions.txt

apport information ** Attachment added: RelatedPackageVersions.txt http://launchpadlibrarian.net/49121660/RelatedPackageVersions.txt -- Mouse is lost on X because driver resync https://bugs.launchpad.net/bugs/577107 You received this bug notification because you are a member of Ubuntu Bugs,

[Bug 577107] UdevDb.txt

apport information ** Attachment added: UdevDb.txt http://launchpadlibrarian.net/49121662/UdevDb.txt -- Mouse is lost on X because driver resync https://bugs.launchpad.net/bugs/577107 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber.

[Bug 577107] UdevLog.txt

apport information ** Attachment added: UdevLog.txt http://launchpadlibrarian.net/49121663/UdevLog.txt -- Mouse is lost on X because driver resync https://bugs.launchpad.net/bugs/577107 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber.

[Bug 577107] XorgConf.txt

apport information ** Attachment added: XorgConf.txt http://launchpadlibrarian.net/49121664/XorgConf.txt -- Mouse is lost on X because driver resync https://bugs.launchpad.net/bugs/577107 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct

[Bug 577107] XorgLog.txt

apport information ** Attachment added: XorgLog.txt http://launchpadlibrarian.net/49121665/XorgLog.txt -- Mouse is lost on X because driver resync https://bugs.launchpad.net/bugs/577107 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber.

[Bug 577107] XorgLogOld.txt

apport information ** Attachment added: XorgLogOld.txt http://launchpadlibrarian.net/49121666/XorgLogOld.txt -- Mouse is lost on X because driver resync https://bugs.launchpad.net/bugs/577107 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct

[Bug 577107] Xrandr.txt

apport information ** Attachment added: Xrandr.txt http://launchpadlibrarian.net/49121667/Xrandr.txt -- Mouse is lost on X because driver resync https://bugs.launchpad.net/bugs/577107 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber.

[Bug 577107] glxinfo.txt

apport information ** Attachment added: glxinfo.txt http://launchpadlibrarian.net/49121669/glxinfo.txt -- Mouse is lost on X because driver resync https://bugs.launchpad.net/bugs/577107 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber.

[Bug 577107] setxkbmap.txt

apport information ** Attachment added: setxkbmap.txt http://launchpadlibrarian.net/49121671/setxkbmap.txt -- Mouse is lost on X because driver resync https://bugs.launchpad.net/bugs/577107 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct

[Bug 577107] monitors.xml.txt

apport information ** Attachment added: monitors.xml.txt http://launchpadlibrarian.net/49121670/monitors.xml.txt -- Mouse is lost on X because driver resync https://bugs.launchpad.net/bugs/577107 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct

[Bug 577107] xdpyinfo.txt

apport information ** Attachment added: xdpyinfo.txt http://launchpadlibrarian.net/49121672/xdpyinfo.txt -- Mouse is lost on X because driver resync https://bugs.launchpad.net/bugs/577107 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct

[Bug 577107] xkbcomp.txt

apport information ** Attachment added: xkbcomp.txt http://launchpadlibrarian.net/49121673/xkbcomp.txt -- Mouse is lost on X because driver resync https://bugs.launchpad.net/bugs/577107 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber.

[Bug 358054] Re: no block devices found after an upgrade from 8.10 to 9.04 on a soft RAID1 system

This was caused because incorrect metadata in raid. Solution was to delete old metadata and everything worked again. -- no block devices found after an upgrade from 8.10 to 9.04 on a soft RAID1 system https://bugs.launchpad.net/bugs/358054 You received this bug notification because you are a

[Bug 577107] Re: Mouse is lost on X because driver resync

Yes! I'm sorry I was unable to uncheck the box after sending the bug report. I submitted before a kernel panic on other bug (#579171) that was a possible breakin attempt. So the checkbox got marked for this bug also. Sorry for the inconveniences... -- Mouse is lost on X because driver resync

[Bug 351927] Re: Deal with stale network mount points (nfs, fuse, etc)

Hi, I must confirm this problem. I found all my systems inaccessible because a launchpad-sysinfo process is launch on every login as usual. But now the problem is that it hangs 100% of time because stale nfs filesystem and this caused all my systems to be unable to show bash prompt. This is a

[Bug 562962] Re: dmraid is unable to disable a disk after faillure

Hi Phillip, Where do you see that other disk is failing. I can only see part of the ary pdc_cdgeffcac failing that corresponds to disk sdc. About DMRAID, Yes, thank you, you are right. I really realized about this when I saw that BIOS Raid was not able to handle this as needed. I'm waiting for

[Bug 562962] [NEW] dmraid is unable to disable a disk after faillure

Public bug reported: Binary package hint: dmraid Hi there. I found a painfull bug/problem with dmraid. This night a disk of the raid 1 mirror failed. I found that instead of disabling the disk and run on degraded mode the system continued to try to access the disk. This caused lots of pain in

[Bug 562962] Re: dmraid is unable to disable a disk after faillure

I'm sorry, forgot to comment that's it's strange that dmraid shows mirror as ok. It should work in degraded mode as one disk is missing. *** Active Set name : pdc_cdgeffcac size : 976562432 stride : 128 type : mirror status : ok subsets: 0 devs : 1 spares : 0 -- dmraid is unable to disable a

[Bug 562962] Re: dmraid is unable to disable a disk after faillure

Hi Phillip, I post dmsetup. See that it holds also LVM setup info... data_vg-homes: 0 41943040 linear pdc_cdgeffcac: 0 976562432 mirror 2 8:48 8:32 7442/7451 1 RD 1 core pdc_bfhccajjfe: 0 976562432 mirror 2 8:16 8:0 7451/7451 1 AA 1 core data_vg-www--main: 0 83886080 linear pdc_bfhccajjfe1:

[Bug 396078] Re: More on RAID 1 issues (RAID1 + DMRAID) = No boot possible

Yesss!!! That solved the problem. but I was not able to remove only the sil metadata. I had to remove the nvidia first and sil after. I wanted to leave the nvidia metadata to be able to run it as a raid1 in degraded mode. But that was not possible because the erase order. But anyway I can

[Bug 396078] Re: More on RAID 1 issues (RAID1 + DMRAID) = No boot possible

Ok then! Thank you very very much as this was a long standing bug that drove me crazy. Thanks again -- More on RAID 1 issues (RAID1 + DMRAID) = No boot possible https://bugs.launchpad.net/bugs/396078 You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 396078] Re: More on RAID 1 issues (RAID1 + DMRAID) = No boot possible

That's not possible as they were new disks when installed on this computer. Anyway, do you know how to remove those incorrect signatures? Thank you -- More on RAID 1 issues (RAID1 + DMRAID) = No boot possible https://bugs.launchpad.net/bugs/396078 You received this bug notification because you

[Bug 393776] Re: No block devices found problem is really blocking

Yes I'm sorry I lost track of this bug... Too many fronts open. The main cause was solved cause raid is now recognized. I think it was missing module in the initial ramdisk. I recently posted more information about this. I think it can be related. I switched to Lucid to see if it was a software

[Bug 534743] Re: dmraid causes udev event feedback loop in Lucid

Hi there, Not sure if related but my system with 3 disks 2 with dmraid raid-1 takes 5-10 minutes to boot since 8.10 I saw different udevadm settle errors and I post two screenshowts. Also my dmraid -r config looks like this. /dev/sdc: sil and nvidia formats discovered (using nvidia)! /dev/sdc:

[Bug 534743] Re: dmraid causes udev event feedback loop in Lucid

Another screenshot. Before the first one... About 2 minutes before and four after initial load. ** Attachment added: 2010-03-25 11.22.05.jpg http://launchpadlibrarian.net/41940460/2010-03-25%2011.22.05.jpg -- dmraid causes udev event feedback loop in Lucid

[Bug 457089] Re: My files are always set to 0 size when transmitted

** Attachment added: .home.gad..cache.ubuntuone.log.oauth.login.log.txt http://launchpadlibrarian.net/34095905/.home.gad..cache.ubuntuone.log.oauth.login.log.txt ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/34095908/Dependencies.txt ** Attachment added:

[Bug 457089] [NEW] My files are always set to 0 size when transmitted

Public bug reported: Binary package hint: ubuntuone-client The files in the second computer (the one to put in sync) are always set to 0 size. I suppose that a problem in the connection caused this. But the program should be able to detect it and fix it. Also it would be nice to include a

[Bug 422176] [NEW] Ubuntu ONE says it crashed. No more infor given

Public bug reported: Binary package hint: ubuntuone-client Sorry, no further info ProblemType: Bug Architecture: amd64 Date: Mon Aug 31 20:50:02 2009 DistroRelease: Ubuntu 9.10 NonfreeKernelModules: nvidia Package: ubuntuone-client 0.93.1-0ubuntu2 PackageArchitecture: all ProcEnviron:

[Bug 422176] Re: Ubuntu ONE says it crashed. No more infor given

** Attachment added: .home.gad..cache.ubuntuone.log.oauth.login.log.txt http://launchpadlibrarian.net/31084583/.home.gad..cache.ubuntuone.log.oauth.login.log.txt ** Attachment added: .home.gad..cache.ubuntuone.log.syncdaemon.exceptions.log.txt

[Bug 396078] Re: More on RAID 1 issues (RAID1 + DMRAID) = No boot possible

Sorry, I was out of the city for a while. I have to say that I cannot reach gdm if I boot with current kernel config. So I have to do a special mix of old initrd + new kernel. I'm sorry but cannot reformat. I have currently two systems with this problem. Anyway I will put the output.

[Bug 396078] Re: More on RAID 1 issues (RAID1 + DMRAID) = No boot possible

It seems that vmlinuz-2.6.31-2-generic is able to boot after block some minutes with the screen in the screenshot 1. No longer no block devices found message. But something makes the system hang after gdm startup -- More on RAID 1 issues (RAID1 + DMRAID) = No boot possible

[Bug 315735] Re: FakeRAID fails with kernel 2.6.28

Ok. I belive you. I will try to look to another possible bug. I will open right now a new bug. Sorry for any inconvenience. -- FakeRAID fails with kernel 2.6.28 https://bugs.launchpad.net/bugs/315735 You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 396078] [NEW] More on RAID 1 issues (RAID1 + DMRAID) = No boot possible

Public bug reported: Binary package hint: dmraid Hello, I open this bug report to clarify and unify all RAID1 + DMRAID reported problems. I hope this will help to solve the issue. The problem: System cannot boot with recent ubuntu distributions when RAID 1 is the primary partition. My

[Bug 396078] Re: More on RAID 1 issues (RAID1 + DMRAID) = No boot possible

** Attachment added: This screenshots shows sdb? blocked so no raid can be activated http://launchpadlibrarian.net/28729835/2009-07-03%2012.44.44.jpg -- More on RAID 1 issues (RAID1 + DMRAID) = No boot possible https://bugs.launchpad.net/bugs/396078 You received this bug notification

[Bug 396078] Re: More on RAID 1 issues (RAID1 + DMRAID) = No boot possible

** Attachment added: This screenshot shows system booting with my initram but strange dm-linear not found... http://launchpadlibrarian.net/28729869/2009-06-18%2015.56.08.jpg -- More on RAID 1 issues (RAID1 + DMRAID) = No boot possible https://bugs.launchpad.net/bugs/396078 You received this

[Bug 315735] Re: FakeRAID fails with kernel 2.6.28

But I'm even upgraded to Karmic Alpha to get latest packages and the bug is still there... I cannot boot... If you can point me where to look to see if it's fixed then I can check. -- FakeRAID fails with kernel 2.6.28 https://bugs.launchpad.net/bugs/315735 You received this bug notification

[Bug 315735] Re: FakeRAID fails with kernel 2.6.28

Hi all, I'm still having *huge* problems. In both, desktop and server machines. I didn't realized before. But this bug is causing havok in my machines. As I had LVM volumes mounted over the dmraid devices but the dmraid devices are not longer available... This causes LVM go reading and

[Bug 315735] Re: FakeRAID fails with kernel 2.6.28

What's the fix? can we try it? -- FakeRAID fails with kernel 2.6.28 https://bugs.launchpad.net/bugs/315735 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

[Bug 315735] Re: FakeRAID fails with kernel 2.6.28

Still More information... I changed /usr/share/initramfs-tools/scripts/local-top/dmraid : for dev in $(dmraid -r -c); do dmraid-activate $dev done to show for dev in $(dmraid -r -c); do echo Activating $dev... dmraid-activate $dev done And what I got was: Activating

[Bug 393776] [NEW] No block devices found problem is really blocking

Public bug reported: The problem reported as No block devices found is really a *BLOCKING* problem that not only makes the system unusable but may cause loss of information as the RAID-0 RAID-1 systems are not correctly recognized. I think this problem MUST be corrected as is a problem in the

[Bug 391043] [NEW] All applications crash when using combo box

Public bug reported: Hi all, I upgraded to new Alpha release Karmic 9.10 and found a blocker bug in this distribution. Every combo box based on GTK makes the application hang. Every application! I can attach bug report from Eclipse IDE but I found the same in: Evolution, Mozilla, etc. Look

[Bug 391043] Re: All applications crash when using combo box

** Attachment added: Whole bug repport. http://launchpadlibrarian.net/28240626/hs_err_pid7071.log -- All applications crash when using combo box https://bugs.launchpad.net/bugs/391043 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 358054] Re: no block devices found after an upgrade from 8.10 to 9.04 on a soft RAID1 system

I upgraded to ALPHA (Karmic) and the solution is not there... ¡ Do not upgrade ! I had to put the old 2.6.28-kernel image to make the system work a little bit. It seems that mixing 2.6.28-kernel initrd and the kernel 2.6.30 it get so confused that can make the system work. But this is a

[Bug 358054] Re: no block devices found after an upgrade from 8.10 to 9.04 on a soft RAID1 system

For me this does not solve anything. I custom compiled a new kernel and this also does not solve the problem. I have not tried the mdadm solution. Because this is another softraid solution. I want to use the onbios solution. dmrad. -- no block devices found after an upgrade from 8.10 to 9.04

[Bug 358054] Re: no block devices found after an upgrade from 8.10 to 9.04 on a soft RAID1 system

I'm sorry. I wrote incorrect the solution. Correct spelling is dmraid. This need a solution. Cause the whole system is unusable if you have all your disks in RAID-1 configuration. Have one sparse disk saved my life! -- no block devices found after an upgrade from 8.10 to 9.04 on a soft RAID1

[Bug 315735] Re: FakeRAID fails with kernel 2.6.28

Confirmed. It does not work for Jaunty x86 and amd64. Tested today fully updated. I have two disk in raid1. And another alone for the OS. Motherboard only let me select RAID, AHCI and SATA. So eveything is working with RAID. Even the sparse disk. The only way to make the system up is to

[Bug 315735] Re: FakeRAID fails with kernel 2.6.28

Yes. I can say that's not fixed. I mean. i cannot use the RAID1 partition because if I try to setup dmraid the whole system stops working. It even does not boot. So the fixed and cleared it's not really true. Sorry. I attach some hardware information but I think this is not hardware related.

[Bug 258578] Re: gdb crashed with SIGSEGV in iterate_over_threads()

This seems to be related http://lists.busybox.net/pipermail/uclibc/2003-March/005800.html -- gdb crashed with SIGSEGV in iterate_over_threads() https://bugs.launchpad.net/bugs/258578 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. --

[Bug 269904] Re: Screen refresh problems with nvidia on intrepid

I want to join this bug to the compiz I reported some time ago: http://bugs.opencompositing.org/show_bug.cgi?id=1044 -- Screen refresh problems with nvidia on intrepid https://bugs.launchpad.net/bugs/269904 You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 270271] Re: evolution crashed with SIGSEGV in g_signal_emit_valist()

The information reported by Timothy Alexander in bug #290796 works: FYI for future people. To disable accessibility, got to System-Preferences-Assistive Technologies Uncheck the enable assistive technologies box. -- evolution crashed with SIGSEGV in g_signal_emit_valist()

[Bug 287496] [NEW] update-manager fails to update grub - Can't boot

Public bug reported: Hi all... Update manager fails to update grub. It seems that a error in update- grub caused this task to never finish. The result is /boot/grub/menu.lst containing several GB of space. All with repeated entries. I had to kill this process to let the system continue

[Bug 287496] Re: update-manager fails to update grub - Can't boot

I cannot find any log of this but I saw in the terminal a error related to this bug, but will try to post the console output next time it happens. -- update-manager fails to update grub - Can't boot https://bugs.launchpad.net/bugs/287496 You received this bug notification because you are a

[Bug 210506] Re: evolution crashed with SIGSEGV in g_signal_emit_valist()

Confirmed bug in Interpid. Crashes when switching to calendar view. -- evolution crashed with SIGSEGV in g_signal_emit_valist() https://bugs.launchpad.net/bugs/210506 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs

<    1   2   3