I don't know if this is helpful, but I had the org.gnome.Extensions
flatpak installed, and it starts just fine under Wayland/nvidia. Only
when I tried to switch to the deb did I get this error.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Public bug reported:
One of the touted features of the GNOME 3.36 release was being able to
update extensions directly from the Extensions app. This doesn't seem
to be working at all on Ubuntu 20.04, however. I regularly receive
update notifications from the Firefox extension, but the only way
nome-shell process I
use at 382M, though it appears to have crashed/restarted more recently.
$ ps -efly
S UID PIDPPID C PRI NI RSSSZ WCHAN STIME TTY
TIME CMD
S gdm 48014325 0 80 0 2069448 3159004 - May05 ?
00:03:07 /usr/bin/gnome-shell
S hackel
Public bug reported:
This has been happening more often recently. I can't point to any
particular thing triggering it. I am hopeful some useful information
will be contained in the debugging info. When this happens, everything
on my screen freezes aside from the mouse cursor. I can use
I just installed 19.10 on a new laptop with a 4K display and am
experiencing this same issue. Once I enable x11-randr-fractional-
scaling, scaling and orientation settings with an external display are
not remembered. I have to set them over again each time I log in. The
~/.config/monitors.xml
Public bug reported:
After upgrading to 19.04, I enabled the experimental 'x11-randr-
fractional-scaling' setting. If I set scaling to 125, 150, or 200%, the
setting is remembered and used the next time I log in. If I set scaling
to 100%, however, the next time I log in the scaling switches
Public bug reported:
Without warning or apparent user action, my entire system froze aside
from the mouse cursor. I was able to switch to a VT to log in and
capture this bug report. After that, I had to `kill -9 gnome-shell`
after which it restarted properly and my session is now working fine
Can't a libgvfs-nfs package be created separate from libgvfs-backends,
the way Fedora does it? (https://apps.fedoraproject.org/packages/gvfs-
nfs) That way it could stay in universe also. (I do think it should be
included by default, but libnfs11 is still stuck in universe as of
18.10).
--
Public bug reported:
Running 18.04, systemd 237-3ubuntu10, and all of my available disk space
on /var (4.3G) just got eaten up by systemd-journald.
/etc/systemd/journald.conf has all the default values (everything
commented out). Processes were starting to crash, and I only recovered
by running
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2017-12-09 (150 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
Package: gnome-shell 3.28.1-0ubuntu2
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1759621/+attachment/5136525/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1759621/+attachment/5136526/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
apport information
** Attachment added: "GsettingsChanges.txt"
https://bugs.launchpad.net/bugs/1759621/+attachment/5136524/+files/GsettingsChanges.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1759621/+attachment/5136523/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
Sadly this is still happening to me on 18.04 as well. Every single time
I resume my machine from suspend. And it's not just that gnome-shell
crashes, but I have to sit for a good 2-3 minutes while apport does its
thing, while the machine is completely frozen from a UI perspective.
This is such a
** Bug watch added: GNOME Bug Tracker #721170
https://bugzilla.gnome.org/show_bug.cgi?id=721170
** Also affects: gnome-shell via
https://bugzilla.gnome.org/show_bug.cgi?id=721170
Importance: Unknown
Status: Unknown
** Changed in: gnome-shell (Ubuntu)
Status: New =>
Public bug reported:
I frequently have notifications that do not disappear after being shown.
This is particularly prevalent with power management notifications.
Most of the time when I wake my computer from suspend, I see the
following notification at the top: "Automatic suspend - Computer will
Interestingly, for a snap installed with --edge, gnome-software is
showing the stable version installed. This integration is clearly
rather broken.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-software in Ubuntu.
I just want to point out that when following the apport bug reporting
process, it initially pulls up a list of existing bugs by searching for
the subject "gnome-shell crashed with signal 5 in g_malloc0()", and this
bug does not show up in that list. In fact, the most recent bug in that
list is
*** This bug is a duplicate of bug 1723378 ***
https://bugs.launchpad.net/bugs/1723378
** This bug has been marked a duplicate of bug 1723378
gnome-shell crashed with SIGTRAP in g_malloc0() from blur_pixels() from
_st_create_shadow_pipeline() from _st_create_shadow_pipeline_from_actor()
*** This bug is a duplicate of bug 1723378 ***
https://bugs.launchpad.net/bugs/1723378
** This bug is no longer a duplicate of bug 1726315
gnome-shell crashed with signal 5 in g_malloc0()
** This bug has been marked a duplicate of bug 1723378
gnome-shell crashed with SIGTRAP in
*** This bug is a duplicate of bug 1723378 ***
https://bugs.launchpad.net/bugs/1723378
** This bug is no longer a duplicate of bug 1726315
gnome-shell crashed with signal 5 in g_malloc0()
** This bug has been marked a duplicate of bug 1723378
gnome-shell crashed with SIGTRAP in
Aha, I was wondering why appport/woopsie wasn't activating for these
crashes. I did find one crash file there from yesterday, even though I
just experienced this issue a few minutes ago when I logged in. I
submitted the report, but I have no idea where it went or how to link it
to this issue.
Public bug reported:
It happens very frequently that, after resuming from suspend, as soon as
I enter my password into GDM, gnome-shell crashes. I initially see my
windows appear for a moment (with titlebars, etc.), then gnome-shell
crashes, the titlebars disappear, and I am unable to do
Public bug reported:
A scrollbar has been added to the text-input section of gnome-
calculator. This makes one of my most frequently used operations
impossible: clicking to position the cursor at the end of the (right-
aligned) input line, in order to enter additional operations after a
Just go this upgrading from 16.04 to 16.10. I had to dismiss 51 (!!!)
identical dialogues about this failure during the upgrade before it
finally quit entirely. It seems to have finished, though, and my system
is up to date and stable so far.
--
You received this bug notification because you
** Attachment added: "Open file dialogue"
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1582823/+attachment/4664796/+files/Screenshot%20from%202016-05-17%2011-59-51.png
** Description changed:
Since upgrading to 16.04, I've been experiencing frequent difficulties
resuming from
Public bug reported:
Since upgrading to 16.04, I've been experiencing frequent difficulties
resuming from suspend, causing text not to be displayed at all, or wrong
characters to be displayed. Please see the attached screenshots.
I don't know what part of the system this lies in. It seems to
What about graphical packages like keepassx, keepass2, galculator, and
all kinds of others that are missing? Do packages have to be manually
whitelisted?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-software in Ubuntu.
Actually, I just tried Petr's suggestion of manually running "unity,"
and Gedit's menus did suddenly start working. Perhaps this is actually
a different issue.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit in Ubuntu.
Are we sure this was actually fixed? I'm running gedit 3.18.3-0ubuntu4,
and have *no* menus whatsoever. There's just a toolbar with Open, New
(+), and Save buttons.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit in Ubuntu.
*** This bug is a duplicate of bug 1560797 ***
https://bugs.launchpad.net/bugs/1560797
Public bug reported:
This is likely a dupe of #1560797 but I wanted to have the bug report
created so as to get any extra debugging info available saved, since in
that report they thought the issue had
I also get this message all the time with my Nexus 5. Typically, I get
the "Unable to mount Android MTP device" error message popping up on my
screen when I plug in my phone, but *not* always. Since I plug/unplug
my phone very often, I typically get 4-5 of these messages hidden behind
windows
Confirming this issue is still present on Rhythmbox 3.0.2-0ubuntu1.
Power Manager does not appear in the UI in the list of plugins, but the
files are still present in the package at /usr/lib/rhythmbox/plugins
/power-manager. When I start Rhythmbox, I do get the following relevant
debug message:
This problem still exists in Ubuntu 14.04. My dmesg contains a bunch of
these errors:
systemd-hostnamed[1487]: Warning: nss-myhostname is not installed.
Changing the local hostname might make it unresolveable. Please install
nss-myhostname!
Running systemd-services 204-5ubuntu13
Also,
Public bug reported:
On the Sounds preferences tab, the viewport for Play sound for events
is tiny, showing only a single item at a time, with a huge amount of
whitespace underneath it. See attached screenshot.
Empathy 3.8.6-0ubuntu7
** Affects: empathy (Ubuntu)
Importance: Undecided
Public bug reported:
Running shotwell 0.18.0-0ubuntu2 on Ubuntu 14.04.
When trying to publish a photo, only Picasa and Piwigo are shown in the
Publish photos to drop down. Clicking Add more accounts... does nothing
except print the following to the console:
(shotwell:324): GLib-GIO-CRITICAL
*** This bug is a duplicate of bug 1205055 ***
https://bugs.launchpad.net/bugs/1205055
** This bug has been marked a duplicate of bug 1205055
Impossible to change column width of Nautilus in list view
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
*** This bug is a duplicate of bug 1205055 ***
https://bugs.launchpad.net/bugs/1205055
** This bug is no longer a duplicate of bug 1243806
The names column has its width dictated by other columns
** This bug has been marked a duplicate of bug 1205055
Impossible to change column width of
*** This bug is a duplicate of bug 1205055 ***
https://bugs.launchpad.net/bugs/1205055
** This bug is no longer a duplicate of bug 1243806
The names column has its width dictated by other columns
** This bug has been marked a duplicate of bug 1205055
Impossible to change column width of
*** This bug is a duplicate of bug 1205055 ***
https://bugs.launchpad.net/bugs/1205055
** This bug is no longer a duplicate of bug 1243806
The names column has its width dictated by other columns
** This bug has been marked a duplicate of bug 1205055
Impossible to change column width of
*** This bug is a duplicate of bug 1205055 ***
https://bugs.launchpad.net/bugs/1205055
** This bug is no longer a duplicate of bug 1243806
The names column has its width dictated by other columns
** This bug has been marked a duplicate of bug 1205055
Impossible to change column width of
Still seeing this behaviour with Nautilus 1:3.10.1-0ubuntu8 on Ubuntu
14.04. I noticed it in my Rubbish Bin... The Original Location column
contains some very long paths which push all other columns to their
minimum widths, which is why they are not apparently resizeable.
Unfortunately this
Still very much present in gnome-power-manager 3.4.0-0ubuntu1.1. This
causes the following error at *every* login.
gnome-session[11158]: WARNING: Failed to start app: Unable to start
application: Failed to execute child process gnome-power-manager (No
such file or directory)
** Summary changed:
Still present with Rhythmbox 2.96-0ubuntu4.2 on 12.04. Can anyone check
on 2.97-1ubuntu5 on 12.10? I am currently using caffeine to pause power
management manually, but an automatic solution would be ideal,
especially since it is supposed to exist!
--
You received this bug notification because
It appears that as of Ubuntu 11.10 there is no longer ANY way to correct
incorrectly detected DPI. This needs to be fixed rather urgently before
12.04 is released...
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to the bug report.
I don't know if it's a bug in GNOME but it's still a bug in Ubuntu! I
just installed 12.04 nightly and I cannot find ANY way to fix the DPI.
It's currently set to 96 instead of 110 on my test machine, and
apparently there is no option anywhere to fix it, in spite of it being
correctly detected
After upgrading to 11.04, I am no longer seeing this issue.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/812609
Title:
nautilus crashed with SIGSEGV in
I believe this is a bug in Unity, not Totem, and likely a dupe of bug
#688825. Unity should detect when an application is full-screen and not
appear above it.
** Also affects: unity (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a
(I noticed this particular issue with mplayer, not Toem, but I believe
it happens with any full-screen application. Another user reported it
happening with the rdesktop client.)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to totem
Please increase the priority for fixing this. The fix is so simple, and
it really gives an unprofessional impression to new Ubuntu users! Even
if people don't use Bluetooth, just seeing the missing icon in the
System Settings I find looks quite bad.
--
You received this bug notification
*** This bug is a duplicate of bug 86184 ***
https://bugs.launchpad.net/bugs/86184
** This bug is no longer a duplicate of bug 459647
Cannot change mouse cursor theme when compiz is enabled
** This bug has been marked a duplicate of bug 86184
Can't change cursor style using Compiz.
*
*** This bug is a duplicate of bug 86184 ***
https://bugs.launchpad.net/bugs/86184
** This bug is no longer a duplicate of bug 459647
Cannot change mouse cursor theme when compiz is enabled
** This bug has been marked a duplicate of bug 86184
Can't change cursor style using Compiz.
*
I would like to report that this is finally fixed for me in Natty beta!
Seems like it's probably more of a coincidence or a kernel improvement,
but as long as it works I'm happy! Can anyone else confirm this?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
FYI still exists in Maverick.
--
No remaining time displayed when on battery
https://bugs.launchpad.net/bugs/570940
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu.
--
desktop-bugs mailing list
Public bug reported:
Binary package hint: gnome-panel
Just upgraded to Maverick, and now very often when I resume from
suspend, the nm-applet icon is missing from the notification area. The
space for it is still there, but there is no icon and I cannot interact
with it. nm-applet is still
The real question is why g-p-m doesn't even estimate the time remaining
on these machines, like my Dell Mini 9.
** Changed in: gnome-power-manager (Ubuntu)
Status: New = Confirmed
--
Low battery notification is badly worded when remaining time is unknown
*** This bug is a duplicate of bug 570940 ***
https://bugs.launchpad.net/bugs/570940
** This bug has been marked a duplicate of bug 570940
No remaining time displayed when on battery
* You can subscribe to bug 570940 by following this link:
** Changed in: gnome-power-manager (Ubuntu)
Status: New = Confirmed
--
No remaining time displayed when on battery
https://bugs.launchpad.net/bugs/570940
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manager in
I have this problem on my Dell Mini 9. Submitting my info, hope it
helps. Would really like to see the estimated time remaining again!
--
No remaining time displayed when on battery
https://bugs.launchpad.net/bugs/570940
You received this bug notification because you are a member of Ubuntu
Architecture: i386
DistroRelease: Ubuntu 10.04
GnomeSessionIdleInhibited: Unknown
GnomeSessionInhibitors: Failed to acquire
GnomeSessionSuspendInhibited: Unknown
MachineType: Dell Inc. Inspiron 910
NonfreeKernelModules: wl
Package: gnome-power-manager 2.30.0-0ubuntu1
PackageArchitecture: i386
apport information
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/52102085/BootDmesg.txt
--
No remaining time displayed when on battery
https://bugs.launchpad.net/bugs/570940
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
apport information
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/52102086/CurrentDmesg.txt
--
No remaining time displayed when on battery
https://bugs.launchpad.net/bugs/570940
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
apport information
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/52102087/Dependencies.txt
--
No remaining time displayed when on battery
https://bugs.launchpad.net/bugs/570940
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
apport information
** Attachment added: DevkitPower.txt
http://launchpadlibrarian.net/52102089/DevkitPower.txt
--
No remaining time displayed when on battery
https://bugs.launchpad.net/bugs/570940
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
apport information
** Attachment added: GConfNonDefault.txt
http://launchpadlibrarian.net/52102091/GConfNonDefault.txt
--
No remaining time displayed when on battery
https://bugs.launchpad.net/bugs/570940
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
apport information
** Attachment added: Lspci.txt
http://launchpadlibrarian.net/52102093/Lspci.txt
--
No remaining time displayed when on battery
https://bugs.launchpad.net/bugs/570940
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
apport information
** Attachment added: Lsusb.txt
http://launchpadlibrarian.net/52102094/Lsusb.txt
--
No remaining time displayed when on battery
https://bugs.launchpad.net/bugs/570940
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
apport information
** Attachment added: ProcCpuinfo.txt
http://launchpadlibrarian.net/52102095/ProcCpuinfo.txt
--
No remaining time displayed when on battery
https://bugs.launchpad.net/bugs/570940
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
apport information
** Attachment added: ProcInterrupts.txt
http://launchpadlibrarian.net/52102097/ProcInterrupts.txt
--
No remaining time displayed when on battery
https://bugs.launchpad.net/bugs/570940
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
apport information
** Attachment added: ProcModules.txt
http://launchpadlibrarian.net/52102100/ProcModules.txt
--
No remaining time displayed when on battery
https://bugs.launchpad.net/bugs/570940
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
apport information
** Attachment added: UdevLog.txt
http://launchpadlibrarian.net/52102105/UdevLog.txt
--
No remaining time displayed when on battery
https://bugs.launchpad.net/bugs/570940
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
apport information
** Attachment added: UdevDb.txt
http://launchpadlibrarian.net/52102103/UdevDb.txt
--
No remaining time displayed when on battery
https://bugs.launchpad.net/bugs/570940
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
apport information
** Attachment added: gnome-power-bugreport.txt
http://launchpadlibrarian.net/52102107/gnome-power-bugreport.txt
--
No remaining time displayed when on battery
https://bugs.launchpad.net/bugs/570940
You received this bug notification because you are a member of Ubuntu
I can't believe Lucid shipped as an LTR with no tool to manage system
services. This is a huge omission. Still hope to see it resolved some
day...
--
System Administration Services (services-admin) missing (Karmic)
https://bugs.launchpad.net/bugs/437905
You received this bug notification
I am experiencing this issue as well. I discovered that the Power
Manager Brightness Applet Cannot get laptop panel brightness, even
though notify-osd correctly displays the brightness when I manually
adjust it (using my laptop's acpi hotkeys). So I am wondering if Gnome
Power Manager is
Ubuntu 9.10, amd64, en_GB.UTF-8
pidgin 1:2.6.4-1ubuntu3~pidgin1.9.10
libgtk2.0-0 2.18.3-1ubuntu2
The problem also occurred with pidgin 1:2.6.2-1ubuntu7 in karmic so I
don't think that is the problem. Any more info or other backtraces I
can provide, let me know.
--
Pidgin crashed with SIGSEGV
Public bug reported:
After I choose an image to use as a buddy icon in Pidgin, it segfaults.
A backtrace is attached.
Originally reported upstream here:
http://developer.pidgin.im/ticket/10990
** Affects: gtk+2.0 (Ubuntu)
Importance: Undecided
Status: New
--
Pidgin crashed with
** Attachment added: gdb-pidgin.txt
http://launchpadlibrarian.net/36876617/gdb-pidgin.txt
--
Pidgin crashed with SIGSEGV in gdk_pixbuf_loader_eat_header_write()
https://bugs.launchpad.net/bugs/497490
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Also seeing this on my Dell Mini 9 after upgrading, and seems like a
dupe of #444881.
I just wanted to add that the powertop utility *does* give an ACPI power
usage time remaining estimate, though it takes a while to get it so I
would guess it is simply calculating the discharge rate manually.
Guys, this fix was *reverted* so Ubuntu is still forcing DPI to 96 DPI
by default instead of using the auto-detected value. Until that fix is
reinstated, this bug is not really relevant. We are basically waiting
for all the issues reported in bug #345189 to be fixed, which will allow
fixing
Since the my original bug report was marked as a duplicate of this, let
me just say that it is definitely valid, and I can reproduce it simply
by importing pictures. It's happened to me twice now, possibly related
to having two instances of f-spot open, because f-spot-import does not
re-use the
I hope you will revert this change as soon as possible for Jaunty+1 in
order to give developers plenty of time to make sure their apps render
properly at native DPIs. It's really disappointing that this fix will
not make it into Jaunty because of this.
--
GNOME default DPI doesn't match X
Public bug reported:
Binary package hint: f-spot
This is the second time I have seen this issue, so I am filing a
separate bug report. It may be a duplicate or related to bugs #339243
or #348158, but the circumstances were not identical.
I inserted an 8GB SD card, and was prompted to launch
Alexander, what you are saying would completely defeat the purpose of
DPI in the first place, which is to ensure that 10pt appears exactly
the same regardless of what screen you are viewing it on. The gconf
defaults should absolutely not have a px suffix, as this would cause
incredibly small,
Similar issues on my system.
** Attachment added: 15.4 1920x1200 147 DPI
http://launchpadlibrarian.net/23230352/Screenshot.png
--
Default font size too large if using native DPI
https://bugs.launchpad.net/bugs/310353
You received this bug notification because you are a member of Ubuntu
** Attachment added: bold font.jpg
http://launchpadlibrarian.net/23230847/bold%20font.jpg
--
Default font size too large if using native DPI
https://bugs.launchpad.net/bugs/310353
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
Nicolò, the DPI is probably correct (you can measure it yourself to be
sure). The problem is that all the default fonts in Ubuntu are way too
big, because previously everyone defaulted to 96 DPI. That is why I
filed this bug, and I am re-opening it now that bug #157398 is fixed in
Jaunty.
**
Exactly, Nicolò.
Sebastien, would changing the default font size really affect anyone
after upgrading? If they already have specified custom fonts, I
certainly don't think they should be overridden upon upgrading. It
should only affect new users. It's true that the fonts would be smaller
for
As long as it sets the default, then I would agree this is fixed, since
it will force developers to re-scale the fonts on their apps to look
right. I see no reason not to let users override it if they want. I
just wish it would be moved out of the Appearance/Fonts control, because
it should be
Does this patch actually fix the problem of the file dialogue resizing
at all (it shouldn't), or does it just make the resizing work properly?
I'm wondering if a separate bug needs to be filed against the resizing
behaviour.
--
Gnome file chooser/selector is way to small
Has anyone experienced this bug who is not running Compiz? I don't
believe this is a gtk issue at all. It seems as if Compiz is somehow
ignoring the window resize that normally occurs. I still think this
behaviour is broken, but that is a totally separate issue. Don't blame
the gtk guys for
Has anyone experienced this bug who is not running Compiz? I don't
believe this is a gtk issue at all. It seems as if Compiz is somehow
ignoring the window resize that normally occurs. I still think this
behaviour is broken, but that is a totally separate issue. Don't blame
the gtk guys for
So you are saying that Metacity simply ignores this bug that gtk is
producing? It seems like two separate issues to me. One issue is that
gtk is resizing the dialogue in the first place. That's not what this
particular report is about, but solving it would probably hide this bug.
This bug is
I don't think the Brainstorm idea was taking into account the use of
accurate DPI settings. When running 96dpi on a 85 dpi monitor, I'm sure
the font size is fine, if not too small. But when running 96dpi on a
150 dpi monitor, the font is way too big. My argument was that when
running the same
What kind of device do you have? Sounds amazing! In any case, I was
only repeating the proposed solution of the GNOME developers. If there
is a better solution, such as a user dialogue or something, that would
be great. I doubt you'll want to run Ubuntu on a .75 display in any
case, as you
Public bug reported:
Binary package hint: gnome-control-center
I realise this is largely a matter of opinion, however I think enough
people might agree with me that I am going to call it a bug. If the DPI
is set correctly in GNOME, then the default font size of 10 is much too
big to be usable.
*** This bug is a duplicate of bug 157398 ***
https://bugs.launchpad.net/bugs/157398
** This bug has been marked a duplicate of bug 157398
GNOME default DPI doesn't match X default DPI
--
wrong dpi value for rendering fonts
https://bugs.launchpad.net/bugs/253072
You received this bug
This is a very critical bug, and won't fix is really not acceptable.
It seems it's been discussed on the GNOME bugzilla that the default
should only revert to 96dpi when the real DPI is not available: that is,
either it's not detected at all, or the detected value is nonsensical
(e.g. 50 ! dpi
*** This bug is a duplicate of bug 157398 ***
https://bugs.launchpad.net/bugs/157398
I marked this as a duplicate of #157398 because that is the source of
the problem. OpenOffice.org is doing the right thing, so this isn't
even really a bug. But the problem the user is experiencing will be
1 - 100 of 128 matches
Mail list logo
