I can confirm the the bug descriptions, but not the exchange plugin
depedencies.
--
LDAP fails. Says it can't find the server, but the server is there and spelled
correctly. Works in Windows. Problem is probably with the authentifiaction.
https://bugs.launchpad.net/bugs/123282
You received this
I'm sorry. But I've lost the core dump for this and I cannot retrace
it.
--
evince crashed with SIGSEGV in g_main_context_dispatch()
https://bugs.launchpad.net/bugs/241141
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
I can't agree with you Sebastien, for two reasons.
First, I can assure you that the incorrect text in .gtk-bookmarks was
created somewhere in the normal use/upgrade of Ubuntu. Neither the end
user nor myself even knew of the existence of this file. I certainly did
not edit it (until directed to
Thank you for reporting this bug. I cannot reproduce your problem on my
hardy system.
** Changed in: nautilus (Ubuntu)
Status: New = Incomplete
--
Cannot move any file outside of home folder to trash (ext3)
https://bugs.launchpad.net/bugs/248241
You received this bug notification because
Thank you for reporting this bug. I cannot reproduce your problem on my
hardy system.
** Changed in: nautilus (Ubuntu)
Status: Incomplete = New
--
Cannot move any file outside of home folder to trash (ext3)
https://bugs.launchpad.net/bugs/248241
You received this bug notification because
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately we can't fix it, because your description
didn't include enough information. You may find it helpful to read How
to report bugs effectively [WWW]
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html.
John Gelm wrote on 2008-07-10: (permalink)
Sebastien Bacher wrote on 2008-06-23: (permalink)
did you read the previous comments? the previous setup was not really
secure, you can set a blank password for your gnome-keyring if you don't
careabout security though but ubuntu is not going to
Thank you for reporting this bug. Do you get any error messages? Can you
play other radio streams?
** Changed in: rhythmbox (Ubuntu)
Status: New = Incomplete
--
Can't play radio stations from sr.se
https://bugs.launchpad.net/bugs/248200
You received this bug notification because you are
Public bug reported:
Binary package hint: nautilus
Ein Fehler, der nicht behandelt werden kann, ist aufgetreten: Object
reference not set to an instance of an object
at FileImportBackend.Prepare () [0x0]
at ImportCommand.DoImport (.ImportBackend imp) [0x0]
at
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/16003741/Dependencies.txt
** Attachment added: ProcMaps.txt
http://launchpadlibrarian.net/16003742/ProcMaps.txt
** Attachment added: ProcStatus.txt
http://launchpadlibrarian.net/16003743/ProcStatus.txt
--
F-Spot has
Not sure if this bug is going down a different track from its
'duplicate' 241578?
Just a hint that 241578, as described, worked absolutely fine in the LTS
release of Hardy and stopped working after a specific automatic update.
It might be worth looking at the changes made in that update -
I have to manually install python-coherence in order to enable rhythmbox
upnp plugin. After the installation I can enable the plugin but I cannot
configure it.
--
UPnP plugin fails to load: missing python-coherence
https://bugs.launchpad.net/bugs/160592
You received this bug notification
Evolution crashed while navigating emails.
--
evolution crashed with SIGSEGV in g_main_context_check()
https://bugs.launchpad.net/bugs/202763
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
Public bug reported:
Binary package hint: gnome-control-center
When I click on the 'Detect Displays' button in gnome-display-
properties, only one screen is detected although xrandr reports two (see
screenshot).
** Affects: gnome-control-center (Ubuntu)
Importance: Undecided
** Also affects: f-spot (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nautilus (Ubuntu)
Status: New = Invalid
--
F-Spot has troubles importing JPGs
https://bugs.launchpad.net/bugs/248305
You received this bug notification because you are a member of Ubuntu
Desktop
I'm confirming this bug, because noticed this error message on my system too,
problem isn't in hard disk space, but in calculation of CD-R (media) space -
error message is not enough disc space on media.
AFAIK brasero 0.7 wrongly calculates size of audio CD before burning, I've meet
with this
It seems this bug is related to bug #240500 and Pedro Villavicencio
wrote in comments - bug is likely a known one (wrong calculation).
--
Insufficient space on media when direct copying to blank CD
https://bugs.launchpad.net/bugs/242472
You received this bug notification because you are a member
** Attachment added: Screenshot.png
http://launchpadlibrarian.net/16004105/Screenshot.png
--
gnome-display-properties does not detect external screen
https://bugs.launchpad.net/bugs/248315
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
Accepted into -proposed, please test and give feedback here. Please see
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Changed in: gtkhtml3.14 (Ubuntu Hardy)
Status: Confirmed = Fix Committed
** Tags added:
Accepted into -proposed, please test and give feedback here. Please see
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Tags added: verification-needed
--
Evolution vulnerability via HTML frames
Just some comments in case they are useful.
The program crashes at the line which calls fs-op.destroy in
fuse_fs_destroy.
The ?? in frame 2 is this function. This function must be set by
something that calls the library.
I cannot find any source code for whatever this function is. But it
Nirmisgav wrote on 2008-06-17:
I already ruined 2 disks
You can use CD-RW instead of CD-R for testing - one CD-RW disks cost
like 2 CD-R disk, but in CD-RW disk you can write about 1000 times !
--
brasero - error in burning audio files
https://bugs.launchpad.net/bugs/240500
You received this
Brasero 0.8 final was released, please upload this version instead of
0.7.91-0ubuntu2 into Ubuntu Intrepid.
This version fixes important bugs - see gnome-bugs #508502 (Can't add files
from FAT32 partitions) and #506398 (toc image type not autodetected correctly).
I'm pasting here info from NEWS
You have to create a Module section yourself. The failsafe terminal
session is just like that, a terminal and no window manager. At least
that means X can start up, and that something in the gnome session makes
it crash. Can you please run glxinfo in the failsafe terminal?
--
gnome-session
Well duh. The source code is in gvfs.
And the function is vfs_destroy as shown above.
--
gvfs-fuse-daemon crashed with SIGSEGV in pthread_mutex_lock()
https://bugs.launchpad.net/bugs/235698
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug
I have done the reinstallation of all nautilus packages and as i
expected it didn't work. i insist that the problem is in the samba
packages, very probably in the winbind package.
--
stopped browsing windows shares after windbind security update Ubuntu 8.04
https://bugs.launchpad.net/bugs/244411
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
** Summary changed:
- gnome-session crashed on Intrepid 8.10 alpha 1+
+ gnome-session makes Xorg crash in xf86SetScrnInfoModes
--
gnome-session makes Xorg crash in xf86SetScrnInfoModes
https://bugs.launchpad.net/bugs/247003
You received this bug notification because you are a member of Ubuntu
You have been subscribed to a public bug:
When evince opens in fullscreen, it automatically switch to «not
fullscreen» and resized itself. It's very disturbing because it stays
about 1s in fullscreen, then unfullscreen to have a very small window,
and the user have to re-maximise it.
Stays to
** Changed in: libgweather (Ubuntu)
Status: Confirmed = Triaged
--
missing localities in weather applet
https://bugs.launchpad.net/bugs/188741
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a subscriber of a duplicate bug.
--
desktop-bugs
*** This bug is a duplicate of bug 122505 ***
https://bugs.launchpad.net/bugs/122505
Thanks for the bug report. This particular bug has already been reported
into our bug tracking system, but please feel free to report any further
bugs you find.
** Changed in: gtk+2.0 (Ubuntu)
Intel cards are hit by http://bugs.freedesktop.org/show_bug.cgi?id=15477
but normally only when using compiz, so I don't know if it's related.
One of your xorg.conf's posted use the i810 driver, which I think is
obsolete. You should use intel or better not specify anything. It
should work fine
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
Sorry about all the spam. But it appears that subthread_main_loop has
uninitialised data in it when the g_main_loop_quit() function is called.
From my core file:
(gdb) print *subthread_main_loop
$10 = {context = 0x62696c0062696c2f, is_running = 1600349031, ref_count =
1869819507}
That's a lot
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
I want to unsuscribe myself from the updates. How do I do this? Whenever
I try to do so, I get to a Forbidden page.
--- On Mon, 14/7/08, Austin Lund [EMAIL PROTECTED] wrote:
From: Austin Lund [EMAIL PROTECTED]
Subject: [Bug 235698] Re: gvfs-fuse-daemon crashed with SIGSEGV in
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
Public bug reported:
Binary package hint: gthumb
I tried to scale images that are on windows shared folder and overwrite
the original. After the operation, the images were completely lost.
Gthumb didn't gave any warning message if there is any problem with
writing permissions or something else.
** Summary changed:
- gnome-display-properties does not detect external screen
+ gnome-display-properties does not show external screen
** Description changed:
- Binary package hint: gnome-control-center
-
When I click on the 'Detect Displays' button in gnome-display-
- properties, only one
I´m new to Ubuntu and have installed 8.04.1 on my Gigabyte MA790FX-DS5 /
AMD 2.8 DC x86 and am having the same problems as listed above.
First time I put a new floppy in 8.04.1 it wouldn´t mount, despite the
light being constantly on ? (tried access via Places / Computer). Next
reboot it mounted
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/16005902/Dependencies.txt
** Attachment added: ProcMaps.txt
http://launchpadlibrarian.net/16005903/ProcMaps.txt
** Attachment added: ProcStatus.txt
http://launchpadlibrarian.net/16005904/ProcStatus.txt
--
scaling
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
I'm able to login if I use failsafe mode under select session, but not
otherwise.
--
[Intrepid alpha1] gdmgreeter freezes in VMware Server 1.0.6
https://bugs.launchpad.net/bugs/246969
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
ok nice, closing the bug then, thanks.
** Changed in: gnome-power-manager (Ubuntu)
Status: Incomplete = Invalid
--
Battery may be broken alert appeared twice
https://bugs.launchpad.net/bugs/211511
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
Gareth,
Bug #241578 is marked as a duplicate of bug #207072 because the former
bug is actually fallout from the attempt to fix the latter, in gvfs
0.2.4-0ubuntu2. If you have this version of gvfs installed, please
downgrade to the version of gvfs in hardy-updates, 0.2.4-0ubuntu1.
If your issue
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
1 - 100 of 434 matches
Mail list logo
