Augustin, unless you update to the latest release, or your request
involves smart things like moving window controls around and then invent
a solution to a problem that didn't exist before so you can implement a
useless feature of the likes of "windicators" just to fill in the void,
well, I guess y
> This issue is resolved for me since today's update.
I can confirm this on Maverick, as well.
--
Totem won't play XVID mpeg 4 files
https://bugs.launchpad.net/bugs/573607
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gstreamer0.10 in
** Changed in: gstreamer0.10 (Ubuntu)
Status: Incomplete => Confirmed
--
Totem won't play XVID mpeg 4 files
https://bugs.launchpad.net/bugs/573607
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gstreamer0.10 in ubuntu.
--
deskto
@madbiologist: I don't think what you ask is a viable option, at least
in my case, for it would mean to upload "2001 A Space Odyssey",
totalling 1,4 GiB. I'm told it's very, very similar to the one that can
be found on The Pirate Bay by the title of "2001 A Space Odyssey
KLAXXON", in case someone w
*** This bug is a duplicate of bug 453863 ***
https://bugs.launchpad.net/bugs/453863
@madbiologist: what's a "problem file"? Please, specify that, and I'll
provide it. Also, I'm not sure the linked bug is really a duplicate. It
doesn't refer what the missing codec is (OK, perhaps it does in th
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 not
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
** 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
Desktop Bugs, which is subscribed t
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
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 comment
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
Desktop Bugs, which is subscribed to totem in ubuntu.
--
desktop-bugs mailing lis
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
Desktop Bugs, which is a direct subscriber.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
htt
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 notificatio
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
... 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
*** 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 conside
*** 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 conside
... 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
Desktop Bugs, which is subscribed to nautilus in ubuntu.
--
desktop-bugs mailing list
deskt
** 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
** Attachm
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
** 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
** Attac
"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 h
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
Desktop Bugs, which is subscribed to nautilus in ubuntu.
--
desktop-bugs mailing list
desktop-b
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
Desktop Bugs, which is subscribed to nautilus in ubuntu.
--
desktop-bugs mai
** 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
** Attachm
** 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
Desktop Bugs, which is subscribed to nautilus in ubuntu.
--
desktop-bugs mailing list
> 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
Desktop Bugs, which i
I see your point now, Saïvann Carignan, I admit the specific issue
reported in the title does not occur anymore: sorry for
misunderstanding, my fault!
However, in these months I had come to experience the issue as a whole,
more as described in comment #13 than in the title. In fact, it was not
onl
It looks pretty pointless to me, it's still the same bug, the fix is
clearly not working on none of my two computers: nothing changed really.
But if you prefer to close a bug just because the fix was officially
released, rather than to listen to users' experience, well, it becomes
pretty pointless
This bug was not fixed, please reconsider its status. After applying the
update nothing changed.
--
Rhythmbox Notification Bubble shows wrong cover art
https://bugs.launchpad.net/bugs/451086
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assigne
*** 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
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 Tra
> 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
> 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,
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
Desktop Bugs, whi
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 n
OK, good work, many thanks Mirco!
--
Notification: no display of no-square covers
https://bugs.launchpad.net/bugs/426256
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https:
I'm no expert, but after using Rhythmbox for 1 year, I've tried Banshee
on Jaunty for more than one month and stopped having this problem
altogether. So, I doubt it has anything to do with the notify-osd. Now
I'm back to using good old RB once again, but I miss Banshee's neat
behaviour on this issu
Not sure what a vt is. And I hadn't got this particular black screen for
a long time, for I don't use the streaming function much. I've also
taken a look at the above link for DebuggingProgramCrush, but personally
found the explanation convoluted. Thanks anyway. But I've learnt that
the right proce
Ok, I see. This time, I navigated to my /var/crash directory and double
clicked on the crash report I wished to submit
(_usr_bin_evolution.1000.crash). The same procedure started, with Apport
asking me whether I wanted to send the report. I agreed, waited for it
to complete the task, then saw the s
> The bug there is not a crash one, are you sure the software is
crashing?
Sorry, I'm new here, and English isn't my first language. Consider it
wrongly phrased, maybe one can just edit the title to "Totem obscures my
screen thus making my computer uttely unusable". Maybe it wasn't a
crash, so you
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 st
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 st
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
** 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
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 b
** 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
--
Evolut
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, s
** 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
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
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
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
52 matches
Mail list logo
