** Summary changed:
- recurring events not displayed correctly
+ Recurrence rule dialogue is ambiguous
--
Recurrence rule dialogue is ambiguous
https://launchpad.net/bugs/53684
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Yes, I can confirm this. Resuming on a dell inspiron 2200, nm-applet
claims that there are no network devices present but networking works
perfectly fine.
--
Doesn't bring the network back online when resuming from suspend / hibernate
https://launchpad.net/bugs/40125
--
ubuntu-bugs mailing list
After a bit of googling I discovered that I need to comment out all the
entries in /etc/network/interfaces except the loopback interface for
n-m to work correctly. Have done so and n-m now finds interfaces on
resume from suspend. Would be good if the n-m install took care of this
step or at least
I also had this problem. The solution was to comment out all lines in
/etc/network/interfaces except the loopback interface. n-m cannot
control already configured interfaces. If that does not cure the problem
then you should take a look at #40125 and probably mark this bug a
duplicate.
--
No Netw
Correct. #46883 actually describes the problem Ealden and I were having.
Have posted the solution there.
--
Doesn't bring the network back online when resuming from suspend / hibernate
https://launchpad.net/bugs/40125
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.
Could you post the contents of /etc/network/interfaces. Just out of
curiosity, why would you use n-m on a desktop in preference to the
deafult networking configuration?
--
Applet says "Networking disabled" when network is up
https://launchpad.net/bugs/50296
--
ubuntu-bugs mailing list
ubuntu-bug
n-m won't work with a static config; you need to comment out probably
everything but your loopback interface and restart networking for n-m to
work. See:
https://help.ubuntu.com/community/WifiDocs/NetworkManager
I think you can safely close this bug if it works, you don't appear to
be suffering a
Sigh, despite earlier success I faced the same problem this morning
resuming laptop that had been suspended overnight. This bug seems to
depend on how long the laptop is suspended, n-m can cope with being
supended for short periods of time but not several hours - bizarre. Will
now install the scrip
Was delighted to resume my laptop this morning to find n-m behaving
correctly. Then I suspended the thing for 30 mins while I walked my son
to school. Came back and resumed to find ..."no network inerfaces found"
Aaargh!! This thing has a mind of it's own. Will leave John's scripts in
place as they
--
recurring events not displayed correctly
https://launchpad.net/bugs/53684
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Public bug reported:
Binary package hint: evolution
Dapper with Evo 2.6.1-0ubuntu7
I created a recurring event starting on Mon 24/07/06 using this rule:
appointment recurs every 1 week on mon, tue, wed, thur, fri for 4
occurrences.
This should give me a total of 20 events. Only the first 4 ar
view of recurrence dialog
--
recurring events not displayed correctly
https://launchpad.net/bugs/53684
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
--
recurring events not displayed correctly
https://launchpad.net/bugs/53684
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
--
recurring events not displayed correctly
https://launchpad.net/bugs/53684
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
--
recurring events not displayed correctly
https://launchpad.net/bugs/53684
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I also noticed the same problem with Dates and reported a bug in the
Opened Hand bugzilla:
http://bugzilla.openedhand.com/show_bug.cgi?id=128
Following on from that bug report, the Dates developer has closed the
bug as invalid because he believes that Evo is correctly applying the
recurrence rule
Created bug report upstream about recurrence rule dialogue
http://bugzilla.gnome.org/show_bug.cgi?id=348400
Also found this bug which may describe the same problem:
http://bugzilla.gnome.org/show_bug.cgi?id=274514
--
recurring events not displayed correctly
https://launchpad.net/bugs/53684
--
A helpful explanation of how EDS stores calendars on the Opened Hand
bugzilla prompted me to save the calendar as an ics file in Evo and open
it with Mozilla Sunbird on another box. I got the same result as with
Evolution, so it would appear that the problem lies with icalx.com not
Evo.
Can't see
Missed that you had already assigned this bug to the upstream bug I
filed, will edit description to match upstream.
--
recurring events not displayed correctly
https://launchpad.net/bugs/53684
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubun
I left the GNOME bug open because it is a valid feature enhancement
request for an improved recurrence rule dialogue. Has been confirmed
already.
It is not really an upstream version of this bug report, more of an idea
that came out of tracking down what the actual problem was. I was
slightly surp
Public bug reported:
Running edgy on a dell inspiron 2200
I upgraded this morning - the only packages upgraded were the latest
upstart ones - and after a reboot my laptop fails to make it to a login
screen. In recovery mode interspersed among all the kernel messages, I
can see that the following
In recovery mode the last message I got was:
*setting up the console font and keymap ...
then I got a command prompt. It did not seem like the normal terminal
I get in recovery mode though - usually I can logout in recovery mode
and it starts gdm. Have rebooted into X now, do I need to do anyth
Yes, boots fine into X - I am writing this in epiphany right now. Only
the recovery mode seems different.
--
Fails to start
https://launchpad.net/bugs/60389
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
No. I would not have a bug to report if it had ;-)
What were you expecting me to see after making those changes?
Bit of history on the machine in case it helps - it was only upgraded
from dapper yesterday, took a while to sort out all the dep's in
aptitude as I had forgotten I had removed ubuntu-
I did not notice anything particular after changing them, other than
getting further than loading the lp module in recovery mode. No I am not
using cryptsetup.
I commented out the "console owner" line from both files and rebooted, X
works fine. Bizarre.
I will attach the syslog of the first boot
Following up from #60389
** Attachment added: "/var/log/dmesg"
http://librarian.launchpad.net/4272435/dmesg
--
no buffer space available
https://launchpad.net/bugs/57041
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Attachment added: "output of dmidecode"
http://librarian.launchpad.net/4272436/dmidecode
--
no buffer space available
https://launchpad.net/bugs/57041
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Attachment added: "output of lsusb"
http://librarian.launchpad.net/4272438/lsusb
--
no buffer space available
https://launchpad.net/bugs/57041
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Attachment added: "output of lspci"
http://librarian.launchpad.net/4272437/lspci
--
no buffer space available
https://launchpad.net/bugs/57041
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Attachment added: "output of lspci"
http://librarian.launchpad.net/4272439/lspci
--
no buffer space available
https://launchpad.net/bugs/57041
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Attachment added: "/var/log/udev"
http://librarian.launchpad.net/4272440/udev
--
no buffer space available
https://launchpad.net/bugs/57041
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Public bug reported:
This problem only seems to happen with a freshly started machine when I
try and compose a mail immediately after starting evolution.
As soon as I start typing the recipients address the message composition
window freezes as evo tryies to autocomplete the address.
Here is the
I have installed the eds -dbg package and attached gdb to eds as per the
instructions in https://wiki.ubuntu.com/Backtrace
I can recreate the problem with the message composition window freezing
when autocompleting email addresses, gdb's output attached.
** Attachment added: "gdb output"
http:
Public bug reported:
Binary package hint: notecase
Notecase stores its help file as a notecase (.ncd) file at
/usr/share/doc/notecase/help.ncd. The package in feisty installs this
file gzipped which makes it unreadable to Notecase.
Manually gunzip this file after installation as a workaround.
*
I experienced the bug with moving mails ending up in the trash folder
with my webmail.us account for the first time this morning. Previously I
had only experienced that bug with my blueyonder account and was
suspicious this was caused by a blueyonder server problem; I can rule
this out now. log fil
Suspend & Resume with ekiga running and webcam attached triggers this
for me.
ekiga 2.03
kernel 2.6.20-16-generic
Logitech Communicate STX with gspca module
Machine is compaq evo D510 desktop
I am now running with my keyboard and mouse connected via ps/2 (with
adapters) and I can kill ekiga and t
I have the same issue, though in my case resume fails to work with
either the open source ati driver or the binary fglrx driver so maybe
this is a different problem. Hardware is a Compaq Evo 510 desktop and a
Radeon 9550 [RV350 AS] AGP card. Additionally I cannot switch to
Console mode and have to
The problem with the Xorg ati driver appears to be a separate issue. If
I disable dri resume works fine. Will add comment to #23545. Disabling dri has no effect on resuming
from standby with the fglrx driver. Still stuck with that one.
--
Resume from suspend fails with FGLRX
https://bugs.launchp
I have the same issue with feisty/Xorg 7.2. Hardware is a Compaq Evo 510
desktop and a Radeon 9550 [RV350 AS] AGP card. When resuming from
suspend I get a blank (but backlit) screen. I cannot switch to Console
mode and have to reboot. I have tried modifying /etc/default/acpi-
support but it made no
Some further info:
I sent myself several emails from another account for testing purposes
and then proceeded to drag them back and forth between various folders
until I triggered the bug again.
I observed that a move operation in Evo consists of a copy followed by a
delete. Every time a mail is s
Sorry, I should have re-read the entire bug report before posting.
Having done so now it appears that you are experiencing 2 problems,
possibly the same bug, possibly not.
1. You are losing mail when you move it between folders (either manually
or by filter). This might be:
http://bugzilla.gnome.
I can reproduce this bug. In my case the mails are not lost, they end up
in the local trash folder. By that I mean the second trash folder in an
IMAP account folder list (the one that serves no useful purpose
normally, has an icon). Not the one actually on the IMAP server, nor the
one listed under
Whilst reviewing this log this morning I noticed something very strange
at line 212:
received: * LIST (\Marked \HasNoChildren) "/" "Trash/Sent Items"
I don't have a "Sent Items" folder in any of my trash folders.
The message I moved to reproduce the bug is listed at line 618.
--
Loses e-mails
Still present in Gutsy/ Evo 2.12.
I can also confirm the additional problem noted above by Barry Michels,
it seems to be more than a simple locale issue - there is something
seriously flawed with Evo's date calculations. For those of us with a
locale setting that won't permit entering four-digit y
After a bit of playing around with some test contacts it's obvious what
Evolution's Birthdays & Anniversarys Calendar is doing with birthdates
- anyone born before 1970 has the same age regardless of year they were
born and is assumed to have been born in 1970. Attached screenshot
shows 3 test co
Upstream have reported that the birthday calendar age issue is known
about and is being treated as a separate bug:
http://bugzilla.gnome.org/show_bug.cgi?id=300584
It's marked as fixed in 2.11.x but the bug still exists in 2.12.1
Perhaps Ubuntu bug #145657 should be re-opened and an upstream bug
*** This bug is a duplicate of bug 48679 ***
https://bugs.launchpad.net/bugs/48679
This is tracked upstream as a separate problem:
http://bugzilla.gnome.org/show_bug.cgi?id=300584
--
Age of contacts with birthdate <1970 always looks like they were born in 1970
https://bugs.launchpad.net/bug
The issue with Evolution Calendar showing ages incorrectly is known
upstream:
http://bugzilla.gnome.org/show_bug.cgi?id=300584
If that is the only remaining problem then maybe this should be closed
or marked as a dupe of bug #145657?
--
Evolution fails to add certain birthdays to calendar
https
Fixed upstream in 0.9.7, Debian package installs fine in Feisty.
--
cant handle special chars in folder name
https://bugs.launchpad.net/bugs/90147
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-
This bug affects both soundjuicer and rhythmbox in feisty.
As a workaround running gnome-audio-profiles-properties from a terminal
works fine.
--
sound-juicer crashes when "editing profiles"
https://bugs.launchpad.net/bugs/115953
You received this bug notification because you are a member of Ubu
Daniel, I am running dapper,evo 2.8.1 and eds 1.8.1. Will have a look at
the DebuggingProgramCrash page and see what I can do. It is definitely
an ldap problem, I have simply disabled autocompletion from ldap servers
in evo's preferences to make evo usable again.
Jan, I had a look at the upstream
Public bug reported:
Binary package hint: deskbar-applet
Upgraded to feisty yesterday and the deskbar applet is failing to start.
Here's the output from bug-buddy:
Traceback (most recent call last):
File "/usr/lib/python2.4/site-packages/deskbar/ModuleLoader.py", line 157, in
load_all
sel
Having posted a bug report, deskbar has of course worked perfectly since
the last time I logged in. Have not done anything in the way of upgrades
or messing around with config files. The only thing I can think of was
that I ran tracker-search-tool for the first time since upgrading to
feisty, maybe
Spoke too soon, can reproduce this reliably now, pattern is that deskbar
works fine on first login from a freshly booted machine but if I logout
and log back in it fails to start. I am getting error messages twice
about this now, the first one with additional info about .xsession
errors. Attached.
Public bug reported:
Binary package hint: linux-source-2.6.20
Running feisty on a dell inspiron 2200 with intel 915 graphics. I can
only get into X with a 2.6.19 kernel. If I try booting with either of
the 2.6.20 kernels [ -2, -3] my laptop locks up when gdm trys to start.
Booting with quiet and
** Attachment added: "syslog excerpt"
http://librarian.launchpad.net/5581327/syslog
--
X fails to start with 2.6.20
https://launchpad.net/bugs/77784
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I can start in single user mode without problem.
--
X fails to start with 2.6.20
https://launchpad.net/bugs/77784
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
This bug appears to be fixed in both -4 and -5. Thanks!
--
X fails to start with 2.6.20
https://launchpad.net/bugs/77784
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Seems to be working OK apart from this one issue, I have the same
number of dbus processes running in both instances. Are there any
specific tests I can run?
I see the upstream bug report has been rejected because of the same
issue. Maybe reassign to dbus?
--
fails to start after upgrade to fei
59 matches
Mail list logo
