Public bug report changed:
https://launchpad.net/malone/bugs/36252
Bug watches changed:
+ Bug 319208 [GNOME Bug Tracker]
- Bug 319208 ['Bug tracker at http://bugs.gnome.org/']
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
*** This bug is a duplicate of bug 28840 ***
** This bug has been marked a duplicate of bug 28840
CONFIG_USB_EHCI_SPLIT_ISO not being set causes errors when attempting to
play audio through a usb sound device connected via hub
--
[dapper] Cannot play sound on USB device through a HUB
https:/
** Bug 40623 has been marked a duplicate of this bug
--
CONFIG_USB_EHCI_SPLIT_ISO not being set causes errors when attempting to play
audio through a usb sound device connected via hub
https://launchpad.net/bugs/28840
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubun
I ran into this too when trying to use a USB headset through a hub.
>From the description of the kernel config variable, it seems that this
problem is only triggered when plugging a USB 1.x sound device into a
USB 2.0 hub:
config USB_EHCI_SPLIT_ISO
bool "Full speed ISO transactions (EXPERI
This problem should be solvable by editing the
/usr/share/icons/Human/index.theme file. Currently it contains the
following:
[scalable/filesystems]
Size=48
Context=filesystems
Type=Scalable
MinSize=32
MaxSize=256
So the icon theme code thinks that icons in that directory have a
nominal size of 4
Looks like the change is needed for the [scalable/devices] section too.
The other directories under scalable/ don't contain any icons so don't
really matter right now, but it might be worth changing them to Size=128
too if you are going to use 128x128 for all new scalable icons.
--
Folder icons i
Mark: yes. The icon theming code uses the nominal size to work out a
scaling factor for the icon.
So with the existing Size=48 setting, it would use a scaling factor of
49/48 (102%), so render the icon at 130px.
With Size=128, it would instead use a scaling factor of 49/128 (38%) and
render the
** Bug 46132 has been marked a duplicate of this bug
** Bug 46161 has been marked a duplicate of this bug
** Bug 46127 has been marked a duplicate of this bug
--
Folder icons in 'Human' theme are huge
https://launchpad.net/bugs/46219
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
h
*** This bug is a duplicate of bug 46219 ***
** This bug is no longer a duplicate of bug 46127
Icon too large at 75%
** This bug has been marked a duplicate of bug 46219
Folder icons in 'Human' theme are huge
--
Wrong icon size
https://launchpad.net/bugs/46161
--
desktop-bugs mailing lis
*** This bug is a duplicate of bug 46219 ***
** This bug is no longer a duplicate of bug 46127
Icon too large at 75%
** This bug has been marked a duplicate of bug 46219
Folder icons in 'Human' theme are huge
--
Huge icons when using 75% icon size
https://launchpad.net/bugs/46132
--
desk
*** This bug is a duplicate of bug 46219 ***
** This bug has been marked a duplicate of bug 46219
Folder icons in 'Human' theme are huge
** Changed in: Ubuntu
Sourcepackagename: None => ubuntu-artwork
--
Icon too large at 75%
https://launchpad.net/bugs/46127
--
desktop-bugs mailing list
des
This is again a theme bug.
The emblem icon in question is:
/usr/share/icons/Human/48x48/emblems/emblem-desktop.png
The index.theme section for the 48x48/emblems directory puts the nominal
size at 48, and the icon itself is 48x48.
However, the icons in 48x48/emblems should be sized so that they
There are two points of view expressed in the referenced bug:
1. that the Tango icon theme is broken and provides emblems that are too big
(Federico's comments)
2. that Nautilus is broken and should request a different icon size when
asking for the emblems, and the Tango theme is correct (Jakub
@Jonas: If KDE is launching apps in the same way gnome-shell was, it is
inherently racy. It needs to make sure the child process is in the new
cgroup before executing the application.
Doing the cgroup move after the app is already running causes problems
if the application itself wants to configur
Based on Marco's comment above, I suspect we need to add an AppArmor
profile for gnome-shell-portal-helper.
Using the example in that blog post, this would be the simplest possible
policy:
abi ,
include
/usr/libexec/gnome-shell-portal-helper flags=(default_allow) {
userns,
Public bug reported:
Binary package hint: gnome-control-center
gnome-control-center provides a font thumbnailer for Nautilus (gnome-
thumbnail-font), but it never manages to produce any thumbnails.
The fix for bug 339417 introduced some resource limits to the
thumbnailer, but these appear to be
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1424 is
definitely the culprit here. Snaps depend on access to the abstract
namespace socket to function correctly.
Inside the sandboxes, snaps see a private /tmp that is under their
complete control. So there is no /tmp/.X11-unix directory
Looking at the reasoning behind that change, Mutter introduced lazy
initialisation of Xwayland: binding the two sockets, and starting
Xwayland when someone connected to the abstract namespace socket.
Flatpak apps apparently can't speak to the abstract namespace socket, so
would hang forever when st
I've filed https://gitlab.gnome.org/GNOME/mutter/-/issues/1454 upstream
about this regression.
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1454
https://gitlab.gnome.org/GNOME/mutter/-/issues/1454
--
You received this bug notification because you are a member of Ubuntu
Desktop
I had a go at fixing this in
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1508 -- taking
the patches from that MR and applying them to the Groovy mutter source
package gave me a Wayland session that supported X11 snaps again.
It is probably worth waiting for a review from upstream before
I've updated the description with the SRU bug template. I think this
includes all the relevant info?
** Description changed:
- I'm trying to run chromium installed via snap in Ubuntu 20.10 when
- running Ubuntu Wayland session. Unfortunately, chromium wouldn't start:
+ [Impact]
- > chromium
> Is there any option to do this via portals - ie can evince use
> org.freedesktop.portal.OpenURI to open the URI? Would then this
> allow to avoid going via xdg-open?
Evince is using g_app_info_launch_default_for_uri(), which can use the
portal interface:
https://gitlab.gnome.org/GNOME/evince/-/
Public bug reported:
The xenial backport of the fix for 1781428 malfunctioned due to the use
of snapd-glib behaviour introduced after the version included in xenial:
namely auto-connection (and reconnection) to the snapd socket that was
introduced in snapd-glib 1.24.
With the policy module loaded
I noticed this behaviour on my Ubuntu 18.10 system. It is running the
Wayland session, and I only have the ubuntu-d...@ubuntu.com and ubuntu-
appindicat...@ubuntu.com extensions installed (i.e. no upstream dash-to-
dock).
I looked in the journal and found the attached GJS stack trace, which
seems
The above stack trace seems to be tied to this other message:
Nov 16 11:41:38 scruffy gnome-shell[5626]: Object Meta.WindowActor
(0x560d5092bb00), has been already deallocated — impossible to access
it. This might be caused by the object having been destroyed from C code
using something such as de
Looking at the gnome-shell JS code referenced by the stack trace, it
appears it is indeed disabling extensions when locking the screen.
The screenShield.js code handles the lock screen, and pushes and pops a
"session mode" of "lock-screen". In sessioMode.js, the "lock-screen"
mode is defined with
I've sent our patch upstream to see if we can get a version of it
included. I suspect it'll need some changes in order to be acceptable,
assuming they want it. So I'll try to address that as needed.
** Bug watch added: GNOME Bug Tracker #788216
https://bugzilla.gnome.org/show_bug.cgi?id=78821
So, I don't think there is any problem on the gnome-control-center side:
it just sets the org.gnome.desktop.peripherals.touchpad/send-events
GSetting key to disabled, and that is persisting over sleeps.
The code in mutter watches this key, and calls
MetaInputSettings::set_send_events() on each tou
While looking around for code that might resume the touchpad, I noticed
that the libinput master code was a bit different to the version we
ship: there's a tp_resume_conditional() function that checks sendevents.
And checking the history shows up this patch:
https://cgit.freedesktop.org/wayland/l
** Bug watch added: Red Hat Bugzilla #1448962
https://bugzilla.redhat.com/show_bug.cgi?id=1448962
** Also affects: libinput (Fedora) via
https://bugzilla.redhat.com/show_bug.cgi?id=1448962
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
** Also affects: gnome-control-center (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1720331
Title:
Whoopsie conti
-control-center (Ubuntu)
Assignee: (unassigned) => James Henstridge (jamesh)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1720331
Title:
Whoopsie continually relaunchin
So I think I've got things sorted out by (a) switching to call
SetReportCrashes async to avoid blocking the UI, and (b) not calling
SetReportCrashes if we're asked to set it to the current (cached) value
of the property.
I've noticed that if whoopsie-preferences exits while the privacy panel
is op
** Also affects: whoopsie-preferences (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1720331
Title:
Whoopsie conti
enter (Ubuntu)
Importance: Medium => Low
** Changed in: whoopsie-preferences (Ubuntu)
Assignee: (unassigned) => James Henstridge (jamesh)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ub
I set up a clean VM running up to date artful, which includes
snapd-2.28.5+17.10 (so no copying of policy files or changing channel
for core snap), and couldn't reproduce this. I started gnome-software,
and tried to install the Hiri snap and got the expected polkit prompt.
I did get the following
The "Provided email/password is not correct." part of the error message
appears to be coming through straight from the store. This most likely
means you logged in to gnome-software using Ubuntu One credentials at
some point in the past, and the credentials snapd has stored are no
longer valid.
It
So further investigation, the "cannot authenticate to snap store: " part
of the error is only added by snapd for an unexpected error:
https://github.com/snapcore/snapd/blob/master/store/auth.go#L190-L204
I believe this is being called via the refreshDischarges() method,
intended to keep the store
Discussion started here:
https://forum.snapcraft.io/t/handling-invalid-credentials/2526
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1724316
Title:
"Sorry, something went
** Also affects: snapd
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1724316
Title:
"Sorry, something went wrong cannot authenti
Yep. There is code to prevent refreshing the macaroon if the user has
changed their password since it was created:
http://bazaar.launchpad.net/~canonical-isd-hackers/canonical-identity-
provider/trunk/view/head:/src/identityprovider/auth.py#L661
This should help in reproducing the bug.
--
You
Snapd side changes:
https://github.com/snapcore/snapd/pull/4061
It looks like snapd-glib might need a change too, since it looks like
this will still be mapped to SNAPD_ERROR_FAILED in parse_result() (I
think falling back to treating 401 as SNAPD_AUTH_DATA_REQUIRED will do).
--
You received thi
I've got an (as yet unmerged) snapd branch to help with this:
https://github.com/snapcore/snapd/pull/4055
It got a review yesterday, so should go in the next snapd release.
This is basically doing (1), returning a Forbidden error when the user
dismisses the dialog.
--
You received this bug not
I think last time we had problems like this it was due to changes in the
location of the socket for ibus's private D-Bus bus. Looking into the
glib diffs for clues.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
htt
This seems like the most likely culprit:
https://gitlab.gnome.org/GNOME/glib/-/merge_requests/3005
This basically means that code that would have created an abstract
namespace socket in glib 2.74.x now creates a regular unix domain socket
in 2.75.x. We have AppArmor rules in snapd's desktop-legac
Okay. In a clean Lunar VM with glib 2.75.3 installed and ibus enabled as
described in the bug description, I could reproduce the input problems
in Firefox. I saw the following AppArmor denial in the dmesg logs:
[ +0.343553] audit: type=1400 audit(1678248386.012:62):
apparmor="DENIED" operatio
I've created https://github.com/snapcore/snapd/pull/12627 as a proposed
fix for the issue.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2008279
Title:
glib2.0 2.75.3-3 breaks tex
@Batuhan: it's different code, but looks to be the same type of problem:
https://github.com/KDE/kio/blob/5bda428992cbd168fc1898661d80a089a8217449/src/gui/systemd/scopedprocessrunner.cpp#L13-L41
It's moving the process to a new cgroup after the application has
started executing (so happens without
Another idea for how to synchronise the StartTransientUnit call without
resorting to passing pipe file descriptors to the child: we could simply
have the child_setup_func call kill(getpid(), SIGSTOP). The parent
process can now do the cgroup move at its leisure, and then send a
SIGCONT to the child
> So, I feel snapd tracker should somewhat be able to track that an app
> changed its cgroup and move it back to what it belongs, but as discussed
> in https://github.com/systemd/systemd/issues/26925 there's nothing
> telling us that right now.
There is no "snapd tracker". It's the "snap run" code
I've filed https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6565
upstream to cover the gnome-shell problem.
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #6565
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6565
** Also affects: gnome-shell via
https://gitlab.gnome
I did a search through the KDE bug tracker, and it looks like someone
reported the same root problem back in 2020:
https://bugs.kde.org/show_bug.cgi?id=423756
** Bug watch added: KDE Bug Tracking System #423756
https://bugs.kde.org/show_bug.cgi?id=423756
--
You received this bug notification
*** This bug is a duplicate of bug 1810757 ***
https://bugs.launchpad.net/bugs/1810757
Public bug reported:
When using the desktop portal API to save a file, the xdg-document-
portal service crashes if we try to save to a new file name.
Steps to reproduce:
1. On an Ubuntu 18.10 system, inst
Public bug reported:
I am using gnome-terminal 3.31.90-1ubuntu1 on a Disco desktop. If I
create a gnome-terminal window and add a second tab, the window will
shrink by one line each time I switch tabs.
This seems to be theme related, since it happens with Yaru but not with
Adwaita. Some aspects
At didrocks' request, I've also filed this here:
https://github.com/ubuntu/yaru/issues/1196
** Bug watch added: github.com/ubuntu/yaru/issues #1196
https://github.com/ubuntu/yaru/issues/1196
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subsc
If you are running an X session, then you are running into a different
issue.
The set of circumstances that lead to the problem on Wayland (different
gsettings defaults inside and outside of confinement) do not apply to
X11 where the theme is exposed by the host over XSETTINGS (so sees the
default
Is there some way gnome-software can inform the plugin that it is
performing a non-interactive operation?
If so, then the plugin could use snapd_client_set_allow_interaction() to
suppress any potential pokit dialogs from the operation. It wouldn't
allow the operation to succeed, but it also would
I noticed something like this on my desktop system after upgrading. It
only seems to affect Wayland sessions (i.e. GDM login screen and Ubuntu
on Wayland). The mouse still works (i.e. desktop responds to clicks),
but no cursor is drawn. Everything seems fine on my laptop though.
The main differ
Public bug reported:
When I upgraded my desktop yesterday, I could no longer see the mouse
cursor on the screen. It still responded to mouse clicks (e.g. context
menu on right click, pushing the mouse to the top left and left clicking
went to spread mode, etc).
This only seems to affect the Wayl
** Attachment added: "lspci.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867080/+attachment/5335924/+files/lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/b
I've made some simple UI changes in the following branch forked from
ubuntu-master, based on Robert's patch:
https://code.launchpad.net/~jamesh/gnome-software/+git/gnome-
software/+ref/classic-snap-install
This adds a warning message at the top of the details list when viewing
an snap that is not
I put together a gnome-software patch to use the extra info from mvo's
snapd change:
https://code.launchpad.net/~jamesh/gnome-software/+git/gnome-
software/+ref/pick-launch-app
It still only supports running one application, but it now favours apps
that provide a desktop file, and the snap's main
** Bug watch added: GNOME Bug Tracker #784600
https://bugzilla.gnome.org/show_bug.cgi?id=784600
** Also affects: gnome-software via
https://bugzilla.gnome.org/show_bug.cgi?id=784600
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member
** Bug watch added: GNOME Bug Tracker #784773
https://bugzilla.gnome.org/show_bug.cgi?id=784773
** Also affects: gnome-software via
https://bugzilla.gnome.org/show_bug.cgi?id=784773
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member
** Bug watch added: GNOME Bug Tracker #785117
https://bugzilla.gnome.org/show_bug.cgi?id=785117
** Also affects: network-manager via
https://bugzilla.gnome.org/show_bug.cgi?id=785117
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a membe
anged in: snapd (Ubuntu)
Assignee: (unassigned) => James Henstridge (jamesh)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1581713
Title:
Ubuntu Software always
** Branch linked: lp:~jamesh/gnome-control-center/ubuntu-whoopsie-
support
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1698035
Title:
gnome-control-center lacks any
I'm not sure if it is related, but I've encountered test failures in my
mediascanner2 silo for dbus-cpp code that previously ran without issue:
https://launchpadlibrarian.net/281863370/buildlog_ubuntu-yakkety-
arm64.mediascanner2_0.112+16.10.20160831-0ubuntu1_BUILDING.txt.gz
It also failed on arm
I'm not convinced my bug is the same as this one. That said, the
changes in the latest dbus-cpp package don't look particularly ABI
compatible, which may be the cause of this bug:
https://launchpadlibrarian.net/279409841/dbus-
cpp_5.0.0+15.10.20151022.1-0ubuntu5_5.0.0+16.10.20160809-0ubuntu1.diff
Public bug reported:
When trying to build a new mediascanner2 release, tests failed on a
number of architectures when building under Yakkety. Some relevant
logs:
https://launchpadlibrarian.net/281862518/buildlog_ubuntu-yakkety-armhf.mediascanner2_0.112+16.10.20160831-0ubuntu1_BUILDING.txt.gz
htt
This is looking like a case of the code being miscompiled under
optimisation. To reproduce, build mediascanner2 using the
"RelWithDebInfo" build type and then run:
./test/test_dbus --gtest_filter=*filter_codec
The test program segfaults when calling Variant::as() on a
variant that should hav
This sounds a lot like bug 1422304, by the look of it.
Both QtDBus and dbus-cpp make use of libdbus. Libdbus provides a
dbus_shutdown() function that will release various internal global
state, which can be used to remove those allocation from the report
valgrind produces when analysing your prog
For what it is worth, I managed to catch a segfault on shutdown of
music-app (i.e. swiping vertically in the app spread) on the phone. I
couldn't get a usable apport crash dump, but managed to catch it in gdb.
This is with libdbus-cpp 4.3.0+15.04.20151126-0ubuntu1 and libmedia-hub-
client 4.0.0+1
Here's a debdiff for the Xenial package update based on Robert's work.
I don't have upload rights to upload it myself.
** Patch added:
"gnome-software_3.20.5-0ubuntu0.16.04.7_3.20.5-0ubuntu0.16.04.8.diff"
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1690280/+attachment/503274
** Description changed:
[Impact]
Apps that use classic confinement show up in search results but don't install.
[Test Case]
1. Open GNOME Software
2. Search for a classic snap, e.g. "atom"
3. Install snap
Expected result:
Either:
a) Snap is installed
b) Snap is not instal
One last comment: I tried downloading upstream pygobject 3.20.0 (which
was released two days ago), and the scopes run fine using the Xenial
typelib.
So I think the underlying problem is that we've got a problem of version
skew, with the versions of gobject-introspection and pygobject currently
in
@simosx: I gave this another test on a clean xenial VM with the same
gnome-software version as you. Each time it launched the main
"libreoffice" command (showing a window asking to open recent files or
create a new document in one of the libreoffice applications).
gnome-software continues running
Public bug reported:
When running on a Wayland session, if xdg-desktop-portal-gtk is asked to
display a window on behalf of a Wayland app, it gets disconnected from
gnome-shell with one of these messages:
Gdk-Message: 09:49:31.837: Lost connection to Wayland compositor.
Gdk-Message: 09:50
bionic-proposed has a 3.28.2 package, so this should be resolved for
that release shortly.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1774560
Title:
xdg-desktop-portal-gtk malfu
Public bug reported:
dbus-cpp includes a library, yet the package description still claims it
is a "header-only dbus-binding". This should be updated to reflect the
current state of the package.
** Affects: dbus-cpp (Ubuntu)
Importance: Undecided
Status: New
--
You received this
We use libgnome-menu to build the applications index and watch for
changes, so that is where the bug probably resides.
The configuration we use is in /etc/xdg/menus/unity-lens-
applications.menu and uses the directive to pick
applications directories rather than specify them manually.
Perhaps it
Relinking bug watches.
** Changed in: firefox
Importance: Undecided => Unknown
Bugwatch: None => Mozilla Bugzilla #331716
Status: Fix Released => Unknown
** Changed in: firefox (Debian)
Importance: Undecided => Unknown
Bugwatch: None => Debian Bug tracker #362569
Sta
This bug is certainly not invalid, so please don't mark it as such.
There was ample evidence of the problem.
The firefox in Hardy is not exhibiting this bug. Firefox does appear to
be using ligatures for editable text for fonts that have them. It does
not appear to be using ligatures for other t
John: the upstream tasks are there to track related activity in related
bug trackers. Unlinking them and changing the statuses just gives an
incorrect view of their status there. If you think the upstream firefox
task should be closed, bring that up at bugzilla.mozilla.org. Same goes
for the Deb
John: there are obviously ligatures in the the DejaVu font in Hardy (you
can see other GTK apps using them). We can also see that Firefox is not
misrendering justified text anymore, so it does look like it has been
fixed. We knew that the Firefox guys were rewriting the text rendering
code for 3.
Set status from imported bug 176873
** Changed in: libmms
Status: Unknown => Fix Released
--
[apport] totem crashed with SIGSEGV in strlen()
https://bugs.launchpad.net/bugs/101876
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
Rejecting malone bug task, and refiling on gnome-utils in Ubuntu (the
package containing gnome-panel-screenshot).
** Also affects: gnome-utils (Ubuntu)
Importance: Undecided
Status: Unconfirmed
** Changed in: malone (upstream)
Status: Unconfirmed => Rejected
--
Bug in Screensho
This is an Ubuntu bug -- not a Launchpad bug.
** Also affects: totem (Ubuntu)
Importance: Undecided
Status: Unconfirmed
** Changed in: malone (upstream)
Status: Unconfirmed => Rejected
--
In Feisty, Firefox goes black when playing MPEG in totem-mozilla
https://bugs.launchpad.ne
If the proprietary nvidia drivers hide the problem, it is probably
because of differences in the extensions or visuals/pixel formats
supported by the two drivers.
In a number of cases, Cairo provides fallbacks if the X server doesn't
support a particular feature. So it is likely that different co
After noticing the ubuntulooks_draw_progressbar_trough() call in Søren's
stack trace, I tried switching to another theme.
While the "Human" control theme causes Firefox to crash on startup,
Firefox runs without problems with the Clearlooks and ClearlooksClassic
control themes (which ubuntulooks is
Another data point: I was running my X server in 16-bit graphics mode.
If I switched to 24-bit, the Firefox loads correctly with the Human
theme. My x86 laptop has no problems in either 16-bit or 24-bit depths.
So the requirements to reproduce seem to be:
* x86-64
* 16-bit depth
* Human contro
Attached is a patch against the ubuntulooks engine's
ubuntulooks_progressbar_create_cell() to create a Cairo surface of the
same type as the target rather than an RGB24 image surface. With this
patch applied, Firefox runs starts fine with the Human theme.
The RGB24 image surface was what tipped m
Bruce: there are a few things to keep in mind here:
1. The pango patch is not part of Mozilla's builds. That said, most
Linux distros apply the patch since upstream Firefox fails to render a
number of languages they care about.
2. The version of Firefox in Gutsy uses the same rendering engine as
** Also affects: ubuntulooks (Ubuntu)
Importance: Undecided
Status: New
--
MASTER [GUTSY] firefox crashed [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL
PROTECTED] from libcairo
https://bugs.launchpad.net/bugs/133124
You received this bug notification because you are a member of Ubuntu
Des
Bug #133124 is another firefox bug that is likely to be a duplicate of
this one. The investigation I did seems to match what has been found
out here with a few extra details:
1. The bug is not triggered on x86.
2. The bug is not triggered when the X server was set to 24 bit depth, but
does at
The following Gnome bug report is probably relevant:
http://bugzilla.gnome.org/show_bug.cgi?id=472494
I realise that the original reporter does not have a dual head system,
but I bet the same code is responsible for his symptoms.
--
[gutsy] Totem fullscreen changes monitor refresh rate
https
I have run into similar problems (using totem-gstreamer 2.20.0-0ubuntu1
on Gutsy/AMD64).
I have a dual monitor setup configured using xrandr. When switching to
fullscreen mode in totem, the output to my secondary monitor was disabled.
When exiting fullscreen mode, the second monitor remained p
Chris: looking at the stack trace, your crash looks like a different
bug.
The first few stack frames look similar to bug 103880 though.
--
MASTER [GUTSY] firefox crashed [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL
PROTECTED] from libcairo
https://bugs.launchpad.net/bugs/133124
You received this
** Bug watch removed: SourceForge.net Tracker #343142
http://sourceforge.net/support/tracker.php?aid=343142
** Bug watch added: GNOME Bug Tracker #343142
http://bugzilla.gnome.org/show_bug.cgi?id=343142
--
gnome-sound-properties: No easy way to control volume of system sounds
https://launc
** Bug watch removed: SourceForge.net Tracker #318083
http://sourceforge.net/support/tracker.php?aid=318083
** Bug watch added: GNOME Bug Tracker #318083
http://bugzilla.gnome.org/show_bug.cgi?id=318083
--
Places icon size should be increased
https://launchpad.net/bugs/43376
--
desktop-b
1 - 100 of 128 matches
Mail list logo
