I note this is the same problem indicator-messages had in bug 1843740.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851154
Title:
libindicator ftbfs: G_ADD_PRIVATE
To manage notifications about
Public bug reported:
libindicator fails to build with this error:
../../libindicator/indicator-object.c: In function ‘indicator_object_init’:
../../libindicator/indicator-object.c:307:13: error: G_ADD_PRIVATE [-Werror]
307 | IndicatorObjectPrivate * priv = G_TYPE_INSTANCE_GET_PRIVATE (self,
Comment #96 lists this bug as fixed in release 5.16.0-0ubuntu1, but I
*know* that is not true. As Daniel has pointed out, the underlying issue
is that Unity draws itself above all other windows in X11. Unless this
behavior is changed--and it was not in 5.16.0-0ubuntu1--Unity will
always be visible
Oh how I wish it were possible to edit lauchpad comments...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/905441
Title:
Compiz does not integrate well with the system colour scheme
To manage
I found out what was breaking transparency, sort of; it was not related
to this bug report.
Still, for a while compiz was following my system color scheme for quite
a while, until one day it went back to Ubuntu orange and purple and I've
had to manually set colors ever since.
--
You received
Was this bug resolved?
I ask because I find that compiz usually does follow the system color
scheme lately, though I am at the moment experiencing a bug: the cube
walls will not be transparent (despite transparent Wallpaper and cube)
while at the same time all the compiz components are
Sorry, that was meant to be "See bug 1574136"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1195518
Title:
Window focus wrong after minimizing
To manage notifications about this bug go to:
*** This bug is a duplicate of bug 1574136 ***
https://bugs.launchpad.net/bugs/1574136
** This bug has been marked a duplicate of bug 1574136
Minimized window not loosing focus
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1574136 ***
https://bugs.launchpad.net/bugs/1574136
** This bug is no longer a duplicate of bug 758253
unity-compiz develops focus problems and sends input to minimized windows
when 'Keep previews of minimized windows' is enabled
** This bug has been
*** This bug is a duplicate of bug 1195518 ***
https://bugs.launchpad.net/bugs/1195518
** This bug is no longer a duplicate of bug 859885
Minimizing a window should switch focus to the windows underneath it (breaks
restore)
** This bug has been marked a duplicate of bug 1195518
Window
*** This bug is a duplicate of bug 1195518 ***
https://bugs.launchpad.net/bugs/1195518
** This bug is no longer a duplicate of bug 859885
Minimizing a window should switch focus to the windows underneath it (breaks
restore)
** This bug has been marked a duplicate of bug 1195518
Window
*** This bug is a duplicate of bug 1195518 ***
https://bugs.launchpad.net/bugs/1195518
Marking as duplicate of 1195518, since they have the same symptoms.
** This bug has been marked a duplicate of bug 1195518
Window focus wrong after minimizing
--
You received this bug notification
*** This bug is a duplicate of bug 1195518 ***
https://bugs.launchpad.net/bugs/1195518
** This bug is no longer a duplicate of bug 859885
Minimizing a window should switch focus to the windows underneath it (breaks
restore)
** This bug has been marked a duplicate of bug 1195518
Window
*** This bug is a duplicate of bug 1195518 ***
https://bugs.launchpad.net/bugs/1195518
** This bug is no longer a duplicate of bug 859885
Minimizing a window should switch focus to the windows underneath it (breaks
restore)
** This bug has been marked a duplicate of bug 1195518
Window
*** This bug is a duplicate of bug 1195518 ***
https://bugs.launchpad.net/bugs/1195518
** This bug is no longer a duplicate of bug 859885
Minimizing a window should switch focus to the windows underneath it (breaks
restore)
** This bug has been marked a duplicate of bug 1195518
Window
*** This bug is a duplicate of bug 1195518 ***
https://bugs.launchpad.net/bugs/1195518
** This bug is no longer a duplicate of bug 859885
Minimizing a window should switch focus to the windows underneath it (breaks
restore)
** This bug has been marked a duplicate of bug 1195518
Window
*** This bug is a duplicate of bug 1195518 ***
https://bugs.launchpad.net/bugs/1195518
** This bug is no longer a duplicate of bug 859885
Minimizing a window should switch focus to the windows underneath it (breaks
restore)
** This bug has been marked a duplicate of bug 1195518
Window
Anyone affected by this bug should check if they have "Keep previews of
minimized windows" enabled in the Workarounds plugin. See bug 859885;
perhaps we can narrow this down.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This may be the true nature of bug 1195518. We should check if people
affected by it (or the many, many duplicates) have "Keep previews of
minimized windows" enabled. This can probably be fixed in the
Workarounds plugin.
--
You received this bug notification because you are a member of Ubuntu
>cmc302a
YOu are correct, this bug was not fixed. In fact, not fixed in any version;
ever.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1195518
Title:
Window focus wrong after minimizing
To
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/445849/comments/258
>This issue is fixed since long ago.
I'm inclined to believe that, though to be honest I simply got into the habit
of avoiding changing pulseaudio's main volume.
Does it matter if the fix is done in pulseaudio or the
*** This bug is a duplicate of bug 1167079 ***
https://bugs.launchpad.net/bugs/1167079
** This bug has been marked a duplicate of bug 1167079
GtkScrolledWindow widgets (GTK3) have black or transparent backgrounds with
Ayatana overlay-scrollbar
--
You received this bug notification
*** This bug is a duplicate of bug 1167079 ***
https://bugs.launchpad.net/bugs/1167079
** This bug has been marked a duplicate of bug 1167079
GtkScrolledWindow widgets (GTK3) have black or transparent backgrounds with
Ayatana overlay-scrollbar
--
You received this bug notification
*** This bug is a duplicate of bug 1167079 ***
https://bugs.launchpad.net/bugs/1167079
** This bug is no longer a duplicate of bug 1367764
Themes using overlay scrollbars have to set explicitly set backgrounds on
all scrollable widgets
** This bug has been marked a duplicate of bug
Bug 1367764, seems to have narrowed down the cause and come close to
finding a solution.
** Description changed:
When Ayatana overlay-scrollbar is enabled, GtkScrolledWindow widgets may
be rendered without a background.
Without composting these areas are black (openbox, gnome-shell) and
I note that in 2014 I had this problem with gtk 3.14 and Tim had it with
3.7.12.
Was this working with gtk 3.6?
Also, adding overlay-scrollbar (which actually causes the bug) and
Ayatana Design (because I think the Ayatana overlay scrollbars should
come back).
I also like that that the overlay
** Also affects: ayatana-design
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1167079
Title:
GtkScrolledWindow widgets (GTK3) have black or transparent
I've been using overlay-scrollbars, bzr revision 391 (last to include
GTK3 scrollbars) in Archlinux for a while.
I really prefer Ubuntu's design to Gnome's in the case of scrollbars.
The Ayatana scrollbars allow for complete elimination of the trough and
autohide when not in use. I also like that
** Summary changed:
- some GTK widgets have black backgrounds
+ GtkScrolledWindow widgets (GTK3) have black or transparent backgrounds with
Ayatana overlay-scrollbar
** Description changed:
- Some GTK widgets have a black background. So far I have noticed this
- happening in g-c-c, gedit tab
** Description changed:
Plug in iOS device, and it doesn't show the documents on it.
- Please package the recent fix in libimobiledevice:
+ Please package the recent fix in libimobiledevice*:
+ Vauge discussion that mentions using the latest git HEAD*:
Bringing in bug 1577268 as a duplicate (reported six years later than
this one).
Either my idea caught on or someone came to the same conclusion
independently; the patch resolving this in xenial's version removes the
version check completely (rather than just commenting it out). Not sure
what's
*** This bug is a duplicate of bug 611590 ***
https://bugs.launchpad.net/bugs/611590
** This bug has been marked a duplicate of bug 611590
Brasero keeps on asking for libdvdcss.so.2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
>From bug 734908:
>>vanvugt
>It's impossible for an X app to draw on top of the Unity shell because the
>Unity shell is part of Compiz and designed to always draw after app windows
>(hence appears on top).
This is something I have been waiting to hear for about five years--
confirmation and
>Nazar
Unfortunately not. That package could be recompiled for newer versions of
Ubuntu, but the code itself is from gnome-settings-daemon 3.6.4 and will never
be updated. It should really be released in it's own PPA, but I could never
grasp debian packaging--it is more difficult to package
I think danellisuk's approach is interesting. I wonder if there is any
"null" key they could be redirected to?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/30378
Title:
Joystick activity
>Nazar
Without Unity or Gnome-shell running, nothing is listening for the keys; you
need gnome-fallback-media-keys-helper.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1248368
Title:
Volume
I see..
So any idea why nothing has ever been able to draw on top of unity?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/734908
Title:
Unity is visible on top of fullscreen apps
To manage
Ages ago, someone decided that Unity would need to draw itself while
using plugins like "desktop wall"...
I suspect the solution they came up with was to draw Unity directly into
X11's root window where nothing can ever be drawn on top of it.
--
You received this bug notification because you
No one ever answered my question (#32):
How does unity work around gnome-settings-daemon dropping support for
media keys?
There does appear to be code in unity-settings-daemon for this:
I don't understand this code really:
indicator-applet-developers/notify-osd/trunk/src/defaults.c
gint
defaults_get_on_screen_timeout (Defaults* self)
{
gint on_screen_timeout;
if (!self || !IS_DEFAULTS (self))
return 0;
g_object_get (self, "on-screen-timeout", _screen_timeout, NULL);
return
Just digging around indicator-applet-developers/notify-
osd/trunk/src/display.c
/* if there is already one bubble on display
we don't have room for another one */
if (bubble_is_visible (bubble))
return NULL;
not great, but off topic.
on topic:
if (bubble_is_urgent (bubble))
{
/* pick-up the
Use case: Ubuntu derivative/rebranding diversity.
Derivatives might have different interest in notifications; ie some kind
of kiosk distro could intentionally favor full screen, urgency=normal,
as a default behavior while a multimedia desktop may want something like
elementary's
>mpt
Glad to see this bug is still bothering you, because it still bothers
us.
bug 420583's proposal great, and it's been sitting there for seven
years.
Seven years ago there was an idea that could probably have avoided all
this trouble.
Did the x time per n characters algorithm ever really
>Timeout settings: the time notifications stay should also be
configurable: some people read faster than others, so the very-sensible
default (of x time per n characters) can be good, but some people maybe
like y time per n characters.
That would be wonderful. Implement that; put a high priority
>Alister Hood
Yes it does.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/611590
Title:
Brasero keeps on asking for libdvdcss.so.2
To manage notifications about this bug go to:
Did you package the other .desktop file?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1220257
Title:
openbox 3.5.2-0ubuntu1 package actually contains 3.5.0-1
To manage notifications about this
Is there any aspect of deb package management that isn't broken?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/972077
Title:
apt repository disk format has race conditions
To manage notifications
However, it's the people *not* represented on launchpad that you're
*even more* wrong about.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/390508
Title:
notifyOSD ignores the expire timeout
Perhaps add this line would also be helpful:
MimeType=application/octet-stream;
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/918019
Title:
Firefox does not use default application to open binary
>>mpt
Just because I don't agree with you doesn't mean I don't understand your
lexicon.
I just think you're wrong. The group disproportionately represented on
launchpad is not who you think it is.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I am very, very painfully going through this process right now.
I REALLY need dpkg to stop trying to remove colord and network-manager
(dependent on policykit-1). It would also help if Ubuntu Web Browser
were a little more responsive.. Took 10 minutes to type this far
probably unrelated...
Public bug reported:
I came across this when trying to fix an installation (broken by "apt-
get dist-upgrade") by reinstalling its desktop metapackage (which apt
had removed, in order to remove its dependencies and install conflicting
packages that were neither packages I requested or
Five years later, no one--anywhere--has any idea what causes "Bus error"
or why it ruins everything.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/578928
Title:
package libc-bin 2.11.1-0ubuntu7
Could someone explain to me what the &%$# I am doing here right now?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/558571
Title:
/etc/ld.so.nohwcap missing
To manage notifications about this bug
This is a real problem.
** Changed in: glibc (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/558571
Title:
/etc/ld.so.nohwcap missing
To manage notifications
** Also affects: ayatana-design
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/390508
Title:
notifyOSD ignores the expire timeout parameter
To manage
>People who look for, find, and comment in bug reports are
disproportionately those who notice and are annoyed by software's
current behavior. People who don't notice, don't care about, or agree
with, current behavior don't go looking for bug reports about it.
I strongly disagree.
You aren't
>Martinique
That's a really good idea! This could solve mime association problems
across the board.
I made two slight modifications, one because I quit Ubuntu and the other
is more important:
[Desktop Entry]
Name=Auto-select
Exec=/usr/bin/xdg-open %U
Terminal=false
Type=Application
I have another solution for you.
Like most of you I had libdvdcss installed but brasero refused to
recognize it.
It turns out brasero expects a somewhat specifc, outdated version of
libdvdcss (possibly 1.2.0).
I patched brasero to ignore the version of libdvdcss:
http://pastie.org/10227736
Public bug reported:
Apport told me to do this; Ｉｈａｖｅ ｎｏ ｉｄｅａ．．．
ProblemType: Package
DistroRelease: Ubuntu Kylin 15.04
Package: wine-mono0.0.8 (not installed)
Uname: Linux 3.19.0-pf3-00123-g9c4b8d9 i686
ApportVersion: 2.17.2-0ubuntu1
Architecture: i386
Date: Mon Apr 20 14:50:59 2015
This was handled incorrectly.
There was already a bug report regarding the desktop file that was also
handled incorrectly, bug 1220257
The real problem was that Ubuntu has been packaging an outdated version
of openbox with an incorrect version number (this was actually 3.5.0;
3.5.2's .desktop
No, it wasn't.
Furthermore, I see that in later packages of openbox the .desktop file
has been removed completely.
That was not the correct solution to any problem!
This is the file you need:
http://bazaar.launchpad.net/~vcs-imports/openbox/master/view/head:/data/openbox.desktop
--
You
This was handled incorrectly.
There was already a bug report regarding the desktop file that was also
handled incorrectly, bug 1220257
The real problem was that Ubuntu has been packaging an outdated version
of openbox with an incorrect version number (this was actually 3.5.0;
3.5.2's .desktop
The file made it into the source that saucy supposedly built from:
http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/saucy/openbox/saucy/view/head:/data/openbox.desktop
But the openbox that actually gets packaged, and therefore the .desktop
file as well, is 3.5.0.
Here is the .deb on lauchpad:
mpt
It's pretty clear that the majority opinion is to have this fixed by
IMPLEMENTING the timeout parameter, not sweeping it under the rug.
The #1 reason people end up here is looking for some way to make Notify-
OSD's notifications go away faster.
--
You received this bug notification because
defaria
I think you may have encountered what I was getting at in #32
GNOME has tied hotkey support into gnome-shell, such that hotkeys no
longer work without gnome-shell in any gnome-derivative desktops (like
Unity).
The GNOME team has provided a utility to restore hotkey support without
Public bug reported:
Citing this tragedy: bug 390508
And this travesty: bug 533631
I fail to see a point in notify-osd's continued existence other than
intentionally alienating developers and users.
** Affects: libnotify (Ubuntu)
Importance: Undecided
Status: New
** Description
Looking over the build logs of every openbox package since 3.5.0-8, it
seems as though the correct source code was used to build all of the
3.5.2 packages, yet they all have the 3.5.0 .desktop or none at all.
There's a patch in the 3.5.2-0ubuntu1 debian packaging,
Maybe just the .desktop file is outdated.
Ubuntu has been packaging data/gnome-wm-properties/openbox.desktop but
the correct file is data/openbox.desktop
The other file should be removed from the source tree, but it's probably
been forgotten.
--
You received this bug notification because you
Maybe just the .desktop file is outdated.
Ubuntu has been packaging data/gnome-wm-properties/openbox.desktop but
the correct file is data/openbox.desktop
The other file should be removed from the source tree, but it's probably
been forgotten.
--
You received this bug notification because you
The most likely cause of this is that gnome-settings-daemon no longer
supports media keys.
You can restore functionality with gnome-fallback-media-keys-helper, but
it's only packaged for Zorin OS:
https://launchpad.net/~zorin-
os/+archive/ubuntu/packages/+sourcepub/3778150/+listing-archive-extra
or has that change not hit Ubuntu yet?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1302885
Title:
Media keyboard shortcuts not working
To manage notifications about this bug go to:
How does unity work around gnome-settings-daemon dropping support for
media keys?
Does unity handle these keys itself now?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1302885
Title:
Media
** Summary changed:
- root on RAID:0 fails to boot
+ Installation on RAID or LVM fails to boot
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/931929
Title:
Installation on RAID or LVM fails to boot
** Changed in: ayatana-design
Status: Fix Committed = Opinion
** Changed in: ayatana-design
Status: Opinion = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/734908
Title:
duncan bayne
The bug isn't in notify-send; this is part of libnotify which properly
implements the timeout specification (you can send the timeout
parameter).
The problem is in notify-osd (Canonical's notification front-end) which
does not properly implement the timeout specification (it will
Have I mentioned before that I think this is a layering problem?
I was reading the old xscreensaver (one of many things unity appears on top of)
faq and came a across this:
__
Every few minutes, xscreensaver will raise itself above
Ubuntu still carries this patch (and two more just like it) as of
Utopic.
Was upstream ever contacted?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/328572
Title:
Connecting/disconnecting
Almost a year since the last post, using firefox 30; no overlay-
scrollbars :(
Was there any more progress on this issue?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/767040
Title:
Firefox
Sorry, I ended up changing linux distributions before coming back to
check on this bug.
Not having any trouble with gstreamer1.0 or gstreamer applications in
Archlinux!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
there's also the fact that lacking support for the timeout parameter
allows for notifications that do not reliably disappear, ever.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/390508
Title:
Exactly which package provides the symbol
ubuntu_menu_item_factory_get_type?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1226430
Title:
/usr/sbin/unity-greeter: symbol lookup error:
I'm trying to reconcile the ubuntu gtk3 patches from bzr against gtk3
from git and I've almost got it.
I'm stuck on this one, since GMenuModel (gtkmodelmenu?) is deprecated
for GtkMenuTracker
https://git.gnome.org/browse/gtk+/commit/?id=5617b584202b1f967f287dfd03a4560975f1389b
I've worked out
Besides, the documentation contradicting Ubuntu's implementation at
freedesktop.org isn't outdated.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/390508
Title:
notifyOSD ignores the expire timeout
The people trying to figure out why notifications linger at the top of
the screen for way too long and cause new notifications to come in late
and pile up in a chain that can go on for several minutes are not
reading outdated documentation; they are trying to figure out what is
wrong with this
Townsend
First, thank you for doing the right thing. I haven't tried this feature
yet, since I'm still not using Unity (or even Ubuntu anymore) and I have
a question: does this feature distinguish between focused (to be
minimized) and unfocused (to be focused) state?
--
You received this bug
This is the code I asked about:
=== modified file 'launcher/ApplicationLauncherIcon.cpp'
--- launcher/ApplicationLauncherIcon.cpp2014-03-12 23:46:10 +
+++ launcher/ApplicationLauncherIcon.cpp2014-03-17 20:58:25 +
@@ -399,7 +399,16 @@
{
if (arg.source !=
No longer affects notify-osd?
When is someone with the authority and the ability going to wake up and
realize that this bug needs to be fixed, and the way to fix it is to
implement the expire_timeout parameter as specified.
There are plenty of specific cases pointed out in this report of users
Same problem after upgrade to 13.10 but none of the proposed solutions
work.
Deleting the gstreamer cache only gives me an extra error about setting
GST_PLUGIN_SCANNER
This is the output I usually get from totem (don't worry about the theme
warnings):
:~$ totem
(totem:28893): Gtk-WARNING **:
Public bug reported:
Although all plugins (-base, -good, -bad, -ugly, and some others) are
installed, gst-inspect-1.0 only shows:
:~$ gst-inspect-1.0
coreelements: valve: Valve element
coreelements: multiqueue: MultiQueue
coreelements: typefind: TypeFind
coreelements: tee: Tee pipe fitting
I need a solution that doesn't involve reinstalling the entire operating
system.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1270422
Title:
gstreamer1.0 can't load plugins; all gstreamer
When will this patch be applied to future versions of brasero (ie, 3.8,
which still has this problem)?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1072151
Title:
Cannot burn audio CDs with mp3
Alberto Salvia Novella
Do not change bug status without verification.
This bug has not been fixed anywhere.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1228360
Title:
No clock in menu bar and
One more thing that was broken after upgrading to Saucy.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/983535
Title:
libdvdread: Can't seek to block X
To manage notifications about this bug go
#4
#5
This is unlikely to be the cause of the problem. It looks like
pulseaudio attempts all possible configurations for devices when loading
them to find out which ones work.
I've noticed that I get the same floating point exception when
attempting to use the a52 plugin without pulseaudio
sp:7fff94bff400 error:0 in libavutil.so.51.22.1[7fde05ee9000+1c000]
Could this mean the error originates in libavutil or that something else
caused an error in libavutil?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Here's what gdb has to say about that core dump:
Core was generated by `speaker-test -Da52:CARD=PCH -c6'.
Program terminated with signal 8, Arithmetic exception.
#0 0x7fb3cef10a57 in av_samples_get_buffer_size ()
from /usr/lib/x86_64-linux-gnu/libavutil.so.51
--
You received this bug
core dump generated by `speaker-test -Da52:CARD=PCH -c6'
** Attachment added: core dump
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1242390/+attachment/3951054/+files/speaker-test.core
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
What happened to /usr/lib/indicators3/7/libdatetime.so et al?
These libraries are missing from several of saucy's indicator-*
packages.
Take a look:
http://packages.ubuntu.com/raring/amd64/indicator-datetime/filelist
http://packages.ubuntu.com/saucy/amd64/indicator-datetime/filelist
Is this bug different from bug 1242390?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1241439
Title:
[a52 plugin] no sound/audio, traps: pulseaudio[25921] trap divide
error ip:7fe46a303a57
1 - 100 of 396 matches
Mail list logo
