Based on the upstream bug report, it looks like a new version of libical
must be installed, as well as a patch being applied to Evolution. What
are the next steps for getting this fix into current Ubuntu releases?
Since it causes a crash, I think it's a good candidate for a release in
-updates.
-
I can confirm that this still occurs in Evolution 2.30 on Ubuntu 10.10
x86_64.
--
evolution crashed with SIGSEGV in comp_subject()
https://bugs.launchpad.net/bugs/442627
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mai
I am seeing the same issue in 2.68-0ubuntu1.1, disconnecting and
reconnecting seems to have fixed it, but the first time byobu is called,
the symlink is invalid.
--
byobu breaks ssh-agent SSH_AUTH_SOCK
https://bugs.launchpad.net/bugs/549091
You received this bug notification because you are a mem
I have this problem after installing vim with aptitude install vim nd
using update-alternatives --config editor to select vim.
Only crontab -e doesn't work, visudo opens vim as expected.
--
sudo crontab -e uses wrong vi version
https://bugs.launchpad.net/bugs/372588
You received this bug notifi
I'd be happy to test the env var solution. What file should I add it to?
--
libvirt sometimes hangs when using pulseaudio
https://bugs.launchpad.net/bugs/453453
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
This affects me on 2 computers, 100% of the time, and finding
information about the problem was quite hard. If this isn't going to be
fixed, perhaps a warning that having a soundcard in the VM may cause
libvirt to hang would be a good idea.
Interestingly, the exact same VM booted directly with th
Backtrace with the latest up-to-date karmic-amd64 packages.
** Attachment added: "gdb-xchat.txt"
http://launchpadlibrarian.net/34072776/gdb-xchat.txt
--
xchat freezes when trying to connect to a server
https://bugs.launchpad.net/bugs/274799
You received this bug notification because you are a
It still happens for me. I will attempt to get a backtrace ASAP
--
xchat freezes when trying to connect to a server
https://bugs.launchpad.net/bugs/274799
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubun
I realized my previous comment about the Win2k3 server might be
confusing. To be clear, I started a KVM instance using virt-manager
before (accidentally) hitting the power button and clicking Hibernate.
--
[Dell Inc. Studio XPS 1340] hibernate/resume failure [non-free: nvidia wl]
https://bugs.la
Public bug reported:
Booted, started a Win2k3R2 Server, hit hibernate, waited for it to turn
off (screen was corrupted from the time X stopped to when the computer
shut off), turned it back on, waited for grub to choose the default
entry, it came back up without resuming. All packages were up-to-
** Attachment added: "AlsaDevices.txt"
http://launchpadlibrarian.net/33647921/AlsaDevices.txt
** Attachment added: "AplayDevices.txt"
http://launchpadlibrarian.net/33647922/AplayDevices.txt
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/33647923/BootDmesg.txt
** Att
If you don't want to disable pulseaudio, I found an alternate
workaround:
In CIV4 at least, simply editing /etc/pulse/client.conf and setting
"disable-shm = yes" instead of "disable-shm = no" eliminates crashing.
then run:
$ killall pulseaudio && start-pulseaudio-x11
or reboot to activate the cha
This appears to have been fixed in Intrepid as of the beta.
** Changed in: gdm (Ubuntu)
Status: Confirmed => Fix Released
--
gdm uses incorrect resolution
https://bugs.launchpad.net/bugs/216871
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
This seems to be fixed for me too. I installed the Intrepid beta and
GDM showed the correct resolution once I set up my xorg file (my monitor
is not detected properly). I'll mark as fixed.
--
gdm uses incorrect resolution
https://bugs.launchpad.net/bugs/216871
You received this bug notification
This bug affects me as well. I rebooted after a bunch of updates on
Intrepid beta (amd64) and Apport told me compiz.real had crashed. I am
however using the intel driver, not nvidia. The crash doesn't appear to
affect the session in any way. Compiz works properly and the session
starts up fine.
I can confirm that this still occurs on Hardy x86_64
** Attachment added: "1second.png"
http://launchpadlibrarian.net/15693269/1second.png
--
Network history display incorrect
https://bugs.launchpad.net/bugs/78201
You received this bug notification because you are a member of Ubuntu
Bugs, whi
This still occurs on Hardy (x86_64)
** Changed in: gnome-system-monitor (Ubuntu)
Status: Invalid => Confirmed
--
Network history display incorrect
https://bugs.launchpad.net/bugs/78201
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
I can no longer reproduce this bug, and I do not have access to the
computer that it happened on (a Vista box), and although I tried to
reproduce the environment on another system (a WinXP box), it may have
been Vista specific problem or something. I will have access to the
system a week from Wedn
Setting this as affecting GDM, although it might well be an xorg (or
some config package) issue, as I figure the GDM people will know if it's
really their job.
** Changed in: gdm (Ubuntu)
Sourcepackagename: None => gdm
--
gdm uses incorrect resolution
https://bugs.launchpad.net/bugs/216871
You r
** Attachment added: "xorg.conf"
http://launchpadlibrarian.net/13410322/xorg.conf
--
gdm uses incorrect resolution
https://bugs.launchpad.net/bugs/216871
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ub
Public bug reported:
I'm having a similar issue to the one described in #146828, but with
Hardy.
My monitor's native resolution is 1600x1200. When I installed hardy
(console-based net-install), my monitor (Samsung SyncMaster213T) and/or
video card (Intel GMA33 onboard) did not get autodetected p
I'm having a similar issue with Hardy. GDM displays at 1280x1024 but
when I log in, the Gnome desktop shows up at the correct 1600x1200
resolution. My monitor (Samsung SyncMaster213T) and/or video card Intel
GMA33 onboard do not get autodetected properly under Hardy, so I had to
manually configur
** Visibility changed to: Public
--
nautilus crashed with SIGSEGV
https://bugs.launchpad.net/bugs/215395
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/m
Confirmed on hardy alpha 6 with the current updates and nvidia driver.
i386.
--
displayconfig-gtk crashed with IndexError in _syncXorgConfig()
https://bugs.launchpad.net/bugs/147721
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubu
*** This bug is a duplicate of bug 96114 ***
https://bugs.launchpad.net/bugs/96114
Since this is not bug-related, let's take the discussion to the ubuntu
forums, where we don't bother the package maintainers, and other people
with similar issues can easily find the info. Post a new thread
des
*** This bug is a duplicate of bug 96114 ***
https://bugs.launchpad.net/bugs/96114
virag, the network card in the DG33FB is not supported by kernel 2.6.20.
Your problems are not related to the fact that lspci doesn't know the
name of the card. In order to use the onboard network card, you nee
I might as well post the output of lspci now:
00:00.0 Host bridge: Intel Corporation 82G33/G31/P35/P31 Express DRAM
Controller (rev 02)
00:02.0 VGA compatible controller: Intel Corporation 82G33/G31 Express
Integrated Graphics Controller (rev 02)
00:03.0 Communication controller: Intel Corporati
That fixes the problem for me in Feisty, I can assume it does in Gutsy
as well, although I downgraded to 7.04 for stability.
--
Intel G33/P35 (ICH9) not reported correctly by lspci
https://bugs.launchpad.net/bugs/131268
You received this bug notification because you are a member of Ubuntu
Bugs, w
The same is true for my Intel DG33FB board with a G33 chipset.
00:00.0 Host bridge: Intel Corporation Unknown device 29c0 (rev 02)
00:02.0 VGA compatible controller: Intel Corporation Unknown device 29c2 (rev
02)
00:03.0 Communication controller: Intel Corporation Unknown device 29c4 (rev 02)
00:
29 matches
Mail list logo
