[Bug 1965563] Re: gnome-extensions-app fails to start [Error reading events from display: Protocol error]
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 subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1965563 Title: gnome-extensions-app fails to start [Error reading events from display: Protocol error] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965563/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1883013] [NEW] gnome-shell-extensions-prefs does not show any updates
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 I have found to actually update them is using the old Gnome Extensions website. I can still configure, disable, and remove extensions from the app, it just doesn't show any updates. Is this functionality somehow disabled in Ubuntu? gnome-shell-extension-prefs 3.36.2-1ubuntu1~20.04.1 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1883013 Title: gnome-shell-extensions-prefs does not show any updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1883013/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1881851] [NEW] Memory leak from GDM's gnome-shell process
Public bug reported: On my laptop that I keep running but suspend/resume multiple times per day, the gnome-shell process which GDM keeps running in the background has some type of memory leak. It is currently up to 2 GiB after an "uptime" of 28 days. No issues with the actual gnome-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 hackel7553185378 1 80 0 392064 1374538 poll_s May26 ? 02:21:02 /usr/bin/gnome-shell ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.2-1ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Jun 3 00:33:57 2020 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2019-12-03 (182 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-04-24 (39 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1881851 Title: Memory leak from GDM's gnome-shell process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1881851/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1856596] [NEW] gnome-shell freezes and must be killed from console
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 ctrl-alt-Fx to get to another TTY, log in, and at that point I have to kill -9 gnome-shell. When I do this, it seems to take several running processes (like Firefox, slack) with it, but not all of them. When I return to my X VT, gnome-shell restarts and some applications are felt running. I have no idea why. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Dec 16 10:06:17 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2019-12-03 (12 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan third-party-packages -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1856596 Title: gnome-shell freezes and must be killed from console To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1856596/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1825593] Re: Display: 100% scale not remembered when X11 Fractional Scaling is enabled
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 file looks right. -- 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/1825593 Title: Display: 100% scale not remembered when X11 Fractional Scaling is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1825593/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1825593] [NEW] Display: 100% scale not remembered when X11 Fractional Scaling is enabled
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 back to 200% automatically. I only want to use fractional scaling for external monitors. Background: This is on a Dell XPS 9360 with a 1920x1080 ~168 DPI screen. Pretty standard configuration. I have my DisplaySize set to 294x165 in Xorg.conf, Xft.dpi=168, GTK font scaling factor 1.0. I have been unable to find an appropriate combination of settings where 168 DPI is respected for accurate font rendering, while at the same time not scaling up the rest of the UI to unusable proportions. Fractional scaling seems to be the only way to adjust some Gnome UI elements. ** 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/1825593 Title: Display: 100% scale not remembered when X11 Fractional Scaling is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1825593/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1821648] [NEW] Gnome Shell froze GUI entirely with 100% CPU usage
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 again. Possibly a dupe of #1709597 but that is quite old. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.2-0ubuntu1.18.10.1 Uname: Linux 5.0.1-050001-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Mar 25 17:31:56 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2017-12-09 (470 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: gnome-shell UpgradeStatus: Upgraded to cosmic on 2018-10-19 (157 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1821648 Title: Gnome Shell froze GUI entirely with 100% CPU usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1821648/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1637988] Re: gvfsd-nfs not present in gvfs-backends, why?
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). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1637988 Title: gvfsd-nfs not present in gvfs-backends, why? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1637988/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1779189] [NEW] /var/log/journal consumed all available disk space
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 "sudo journalctl --vacuum-files=1" which brought it back down to 25M. My understanding is that the defaults are supposed to prevent this from happening. I'm not familiar enough with systemd to further debug why this might have happened. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1779189 Title: /var/log/journal consumed all available disk space To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1779189/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1759621] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() from ffi_call_unix64()
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 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-28 (11 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True ** Tags added: apport-collected -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1759621 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() from ffi_call_unix64() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1759621/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1759621] ProcCpuinfoMinimal.txt
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. https://bugs.launchpad.net/bugs/1759621 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() from ffi_call_unix64() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1759621/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1759621] ProcEnviron.txt
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. https://bugs.launchpad.net/bugs/1759621 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() from ffi_call_unix64() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1759621/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1759621] GsettingsChanges.txt
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. https://bugs.launchpad.net/bugs/1759621 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() from ffi_call_unix64() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1759621/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1759621] Dependencies.txt
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. https://bugs.launchpad.net/bugs/1759621 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() from ffi_call_unix64() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1759621/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1759621] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() from ffi_call_unix64()
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 huge usability issue! I still suspect it is being caused by some particular combination of gnome-shell extensions that are installed. I've tried (unsuccessfully) to pin down which one it is, but it never seems to work, leading me to believe it must be a combination. I've attached my journalctl output, captured from the moment I resumed my machine. Really hope we can get to the bottom of this! ** Attachment added: "journalctl-gnome-shell.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1759621/+attachment/5136522/+files/journalctl-gnome-shell.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1759621 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() from ffi_call_unix64() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1759621/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1766775] Re: Notifications do not disappear
** 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 => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1766775 Title: Notifications do not disappear To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1766775/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1766775] [NEW] Notifications do not disappear
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 suspend very soon because of inactivity." that never goes away. Presumably, this was shown before my computer went to sleep, and should have disappeared but didn't. I have to either click on the notification, or click on the time to open the notification menu to get it to disappear. Occasionally, the same behaviour occurs with other, random notifications. This is a long-standing issue for me, that I'm just now getting around to reporting. I'm on 17.10, gnome-shell 3.26.2-0ubuntu0.1, and running the gnome-session (not Ubuntu). I don't know if the issue is present on Gnome 3.28, but plan to find out once 18.04 final is released. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1766775 Title: Notifications do not disappear To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1766775/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1745355] Re: gnome-software does not show the right version of a snap when open with xdg-open
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. https://bugs.launchpad.net/bugs/1745355 Title: gnome-software does not show the right version of a snap when open with xdg-open To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1745355/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1723378] Re: gnome-shell crashed with SIGTRAP in g_malloc0() from blur_pixels() from _st_create_shadow_pipeline() from _st_create_shadow_pipeline_from_actor() from st_icon_update_shadow_pipeline(
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 from 2012. As a result, people (or at least me, until now) aren't finding this to report issues as a duplicate, and they are commenting on these really old, unrelated bug reports. It might be a good idea to close out all of those old bugs so as to elevate issues arising now that gnome-shell is the default. I get hit with this bug multiple times a day, so I'm going to just stop reporting it as I'm sure there are plenty of reports here by now, but please let me know if there's anything I can do to assist with debugging this issue. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1723378 Title: gnome-shell crashed with SIGTRAP in g_malloc0() from blur_pixels() from _st_create_shadow_pipeline() from _st_create_shadow_pipeline_from_actor() from st_icon_update_shadow_pipeline() To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1723378/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1726315] Re: gnome-shell crashed with signal 5 in g_malloc0()
*** 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() from st_icon_update_shadow_pipeline() -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1726315 Title: gnome-shell crashed with signal 5 in g_malloc0() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1726315/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1726551] Re: gnome-shell crashed with signal 5 in g_malloc0()
*** 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 g_malloc0() from blur_pixels() from _st_create_shadow_pipeline() from _st_create_shadow_pipeline_from_actor() from st_icon_update_shadow_pipeline() -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1726551 Title: gnome-shell crashed with signal 5 in g_malloc0() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1726551/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1726486] Re: gnome-shell crashed with signal 5 in g_malloc0()
*** 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 g_malloc0() from blur_pixels() from _st_create_shadow_pipeline() from _st_create_shadow_pipeline_from_actor() from st_icon_update_shadow_pipeline() -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1726486 Title: gnome-shell crashed with signal 5 in g_malloc0() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1726486/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1709994] Re: gnome-shell crashes often on unlock / resume from suspend
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. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1709994 Title: gnome-shell crashes often on unlock / resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1709994/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1709994] [NEW] gnome-shell crashes often on unlock / resume from suspend
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 interact with any windows. Eventually gnome-shell restarts itself and the titlebars and functionality are restored. This doesn't happen 100% of the time, and I have not been able to find any correlation. In my syslog, I see lines like: Aug 10 14:30:49 hermes org.gnome.Shell.desktop[5325]: Window manager warning: Failed to set power save mode for output VGA-1: Permission denied Aug 10 14:30:49 hermes org.gnome.Shell.desktop[5325]: Window manager warning: Failed to set power save mode for output eDP-1: Permission denied Aug 10 14:30:58 hermes gnome-session[6503]: gnome-session-binary[6503]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 6 Aug 10 14:30:58 hermes gnome-session-binary[6503]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 6 This is on Ubuntu 17.04, gnome-shell 3.24.2-0ubuntu0.1, under Xorg with Intel HD 4600 graphics. I experience the same crashes under Wayland, making it *completely* unusable. At least under X I can still recover my session. This is particularly annoying because whenever gnome-shell dies, it triggers a separate issue that kills all active Firefox content processes, requiring me to restart Firefox as well. If there's a way to get some better debugging info for this, please let me know. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1709994 Title: gnome-shell crashes often on unlock / resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1709994/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1636646] [NEW] Scrollbar makes it impossible to position cursor at end of line
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 calculation. The scrollbar expands as soon as the mouse cursor approaches the end of line, forcing you to click one digit to the left of the end, manually move to the right with the arrow keys, and then continue to paste or enter more operations. Please fix this by adding a right-hand margin to the input field the width of the hover scrollbar. ** Affects: gnome-calculator (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1636646 Title: Scrollbar makes it impossible to position cursor at end of line To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1636646/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1551623] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed
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 are a member of Ubuntu Desktop Bugs, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1551623 Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1582823] Re: Text not rendering correctly after resume from suspend
** 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 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 affect all gtk apps at least. Chromium renders just fine when this happens, other than the titlebar. Similarly, Cool Retro Term renders correctly, which obviously doesn't use gtk, while Gnome Terminal and Guake do not. This suggests it could be related to framebuffer corruption, but this report was made with a much earlier kernel, and I had no such problems under 15.10. http://askubuntu.com/questions/688306/text-missing- garbled-after-laptop-resumes-from-sleep-mode + libgtk-3-0 3.18.9-1ubuntu3 linux-image-4.4.0-22-generic 4.4.0-22.40 xserver-xorg-core 2:1.18.3-1ubuntu2 xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 lshw -c video - *-display -description: VGA compatible controller -product: 4th Gen Core Processor Integrated Graphics Controller -vendor: Intel Corporation -physical id: 2 -bus info: pci@:00:02.0 -version: 06 -width: 64 bits -clock: 33MHz -capabilities: msi pm vga_controller bus_master cap_list rom -configuration: driver=i915 latency=0 -resources: irq:30 memory:b200-b23f memory:a000-afff ioport:5000(size=64) + *-display + description: VGA compatible controller + product: 4th Gen Core Processor Integrated Graphics Controller + vendor: Intel Corporation + physical id: 2 + bus info: pci@:00:02.0 + version: 06 + width: 64 bits + clock: 33MHz + capabilities: msi pm vga_controller bus_master cap_list rom + configuration: driver=i915 latency=0 + resources: irq:30 memory:b200-b23f memory:a000-afff ioport:5000(size=64) dmesg | grep i915 [1.383957] [drm] Initialized i915 1.6.0 20151010 for :00:02.0 on minor 0 [1.534467] i915 :00:02.0: fb0: inteldrmfb frame buffer device [2.718041] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder A [2.718060] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A FIFO underrun [2.733438] [drm:intel_set_cpu_fifo_underrun_reporting [i915]] *ERROR* uncleared fifo underrun on pipe B [2.733460] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe B FIFO underrun [4.137698] snd_hda_intel :00:03.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 66.585338] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=4267 end=4268) time 282 us, min 1073, max 1079, scanline start 1059, end 1090 [ 277.577183] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=16480 end=16481) time 363 us, min 894, max 899, scanline start 875, end 900 [ 284.581315] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=16900 end=16901) time 358 us, min 894, max 899, scanline start 891, end 905 [ 300.589410] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=18424 end=18425) time 210 us, min 1073, max 1079, scanline start 1070, end 1084 [ 302.574085] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=18544 end=18545) time 338 us, min 1073, max 1079, scanline start 1061, end 1078 [ 470.560521] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=28707 end=28708) time 301 us, min 1073, max 1079, scanline start 1071, end 1091 [ 595.553386] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=36269 end=36270) time 107 us, min 1073, max 1079, scanline start 1056, end 1083 [ 1043.512803] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=63370 end=63371) time 402 us, min 1073, max 1079, scanline start 1058, end 1084 [ 1106.508551] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=66184 end=66185) time 424 us, min 894, max 899, scanline start 876, end 895 ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1582823 Title: Text not rendering correctly after resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1582823/+subscriptions --
[Bug 1582823] [NEW] Text not rendering correctly after resume from suspend
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 affect all gtk apps at least. Chromium renders just fine when this happens, other than the titlebar. Similarly, Cool Retro Term renders correctly, which obviously doesn't use gtk, while Gnome Terminal and Guake do not. This suggests it could be related to framebuffer corruption, but this report was made with a much earlier kernel, and I had no such problems under 15.10. http://askubuntu.com/questions/688306/text-missing- garbled-after-laptop-resumes-from-sleep-mode libgtk-3-0 3.18.9-1ubuntu3 linux-image-4.4.0-22-generic 4.4.0-22.40 xserver-xorg-core 2:1.18.3-1ubuntu2 xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 lshw -c video *-display description: VGA compatible controller product: 4th Gen Core Processor Integrated Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 06 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:30 memory:b200-b23f memory:a000-afff ioport:5000(size=64) dmesg | grep i915 [1.383957] [drm] Initialized i915 1.6.0 20151010 for :00:02.0 on minor 0 [1.534467] i915 :00:02.0: fb0: inteldrmfb frame buffer device [2.718041] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder A [2.718060] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A FIFO underrun [2.733438] [drm:intel_set_cpu_fifo_underrun_reporting [i915]] *ERROR* uncleared fifo underrun on pipe B [2.733460] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe B FIFO underrun [4.137698] snd_hda_intel :00:03.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 66.585338] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=4267 end=4268) time 282 us, min 1073, max 1079, scanline start 1059, end 1090 [ 277.577183] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=16480 end=16481) time 363 us, min 894, max 899, scanline start 875, end 900 [ 284.581315] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=16900 end=16901) time 358 us, min 894, max 899, scanline start 891, end 905 [ 300.589410] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=18424 end=18425) time 210 us, min 1073, max 1079, scanline start 1070, end 1084 [ 302.574085] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=18544 end=18545) time 338 us, min 1073, max 1079, scanline start 1061, end 1078 [ 470.560521] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=28707 end=28708) time 301 us, min 1073, max 1079, scanline start 1071, end 1091 [ 595.553386] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=36269 end=36270) time 107 us, min 1073, max 1079, scanline start 1056, end 1083 [ 1043.512803] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=63370 end=63371) time 402 us, min 1073, max 1079, scanline start 1058, end 1084 [ 1106.508551] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=66184 end=66185) time 424 us, min 894, max 899, scanline start 876, end 895 ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1582823 Title: Text not rendering correctly after resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1582823/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1562158] Re: Package(s) missing from gnome-software
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. https://bugs.launchpad.net/bugs/1562158 Title: Package(s) missing from gnome-software To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1562158/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1518516] Re: ubuntu session option "Show the menus for a window > In the windows title bar" loses menus in gedit
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. https://bugs.launchpad.net/bugs/1518516 Title: ubuntu session option "Show the menus for a window > In the windows title bar" loses menus in gedit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1518516/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1518516] Re: ubuntu session option "Show the menus for a window > In the windows title bar" loses menus in gedit
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. https://bugs.launchpad.net/bugs/1518516 Title: ubuntu session option "Show the menus for a window > In the windows title bar" loses menus in gedit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1518516/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1565363] [NEW] package systemd-sysv 229-3ubuntu2 failed to install/upgrade: pre-dependency problem - not installing systemd-sysv
*** 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 been fixed by an earlier update. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: systemd-sysv 229-3ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6 Uname: Linux 4.4.0-16-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 Date: Fri Apr 1 20:02:35 2016 ErrorMessage: pre-dependency problem - not installing systemd-sysv InstallationDate: Installed on 2014-08-03 (607 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.9 SourcePackage: systemd Title: package systemd-sysv 229-3ubuntu2 failed to install/upgrade: pre-dependency problem - not installing systemd-sysv UpgradeStatus: Upgraded to xenial on 2016-04-02 (0 days ago) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check xenial ** This bug has been marked a duplicate of bug 1560797 package systemd-sysv 225-1ubuntu9.1 failed to install/upgrade: libgcrypt20 was unconfigured -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1565363 Title: package systemd-sysv 229-3ubuntu2 failed to install/upgrade: pre- dependency problem - not installing systemd-sysv To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1565363/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1314556] Re: Unable to mount Android MTP device
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 that I have to clear throughout the day. I haven't been able to isolate the cause, but for example right at this moment, I am unable to reproduce it, even though I just had to clear away a stale error message. I should also add that it works perfectly with ADB, which is what I normally use to transfer files, but I can also turn on MTP. Whenever the phone is plugged-in, it defaults to charging-only mode. I still do get an icon for it, but clicking on it just shows an empty mtp:// folder. I'm able to "mount"/unmount this device, but the folder stays empty—not sure that anything is really happening. If I turn on "Use USB for File transfers" on my device, then the "Internal Storage" icon appears inside the mtp:// folder and I can browse files normally. I just want to isolate / eliminate all the useless error messages. Not sure if this should be split out into a separate bug, since a lot of people seem to be complaining about lack of MTP functionality entirely. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1314556 Title: Unable to mount Android MTP device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1314556/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 912912] Re: rhythmbox power manager plugin doesn't show up in plugins dialog
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: [rb_gpm_plugin_init] rb-power-manager-plugin.c:72: RBGPMPlugin initialising ** Changed in: rhythmbox (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/912912 Title: rhythmbox power manager plugin doesn't show up in plugins dialog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/912912/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1162475] Re: [hostnamed] Changing hostname doesn't update /etc/hosts
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, gnome-control-center (1:3.6.3-0ubuntu54) no longer recommends libnss-myhostname as indicated in #3 above. -- 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/1162475 Title: [hostnamed] Changing hostname doesn't update /etc/hosts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1162475/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1299511] [NEW] Small viewport in Sounds peferences
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 Status: New ** Attachment added: Screenshot from 2014-03-29 11:53:43.png https://bugs.launchpad.net/bugs/1299511/+attachment/4051193/+files/Screenshot%20from%202014-03-29%2011%3A53%3A43.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1299511 Title: Small viewport in Sounds peferences To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1299511/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1299645] [NEW] Unable to add more accounts to publish to
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 **: g_app_info_get_commandline: assertion 'G_IS_APP_INFO (appinfo)' failed (shotwell:324): GLib-CRITICAL **: g_spawn_command_line_async: assertion 'command_line != NULL' failed And immediately close the Shotwell publish dialogue. I assume it is supposed to launch unity-control-center credentials, but this never happens and the user receives no feedback. ** Affects: shotwell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1299645 Title: Unable to add more accounts to publish to To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1299645/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1243806] Re: The names column has its width dictated by other columns
*** 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, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1243806 Title: The names column has its width dictated by other columns To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1243806/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1252961] Re: Rubbish Bin Name Column Too Narrow
*** 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 Nautilus in list view -- 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/1252961 Title: Rubbish Bin Name Column Too Narrow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1252961/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1252957] Re: Column Width Too Limited
*** 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 Nautilus in list view -- 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/1252957 Title: Column Width Too Limited To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1252957/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1257755] Re: nautilus : cannot change the file name column width after a search
*** 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 Nautilus in list view -- 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/1257755 Title: nautilus : cannot change the file name column width after a search To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1257755/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1253750] Re: When a file name is too long, I cannot view other information.
*** 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 Nautilus in list view -- 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/1253750 Title: When a file name is too long, I cannot view other information. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1253750/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1205055] Re: Impossible to change column width of Nautilus in list view
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 results in a Name column with only ellipses and no letters. If I hide the Original Location column, I am able to see the file names and resize all columns as normal. The Original Location and Location columns, at a minimum, need to be set to ellipsize, and the Name column needs a sensible minimum width of 5-6 characters. -- 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/1205055 Title: Impossible to change column width of Nautilus in list view To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1205055/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 843847] Re: /etc/xdg/gnome-power-manager.desktop must be removed
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: - /usr/bin/gnome-power-manager missing from package + /etc/xdg/gnome-power-manager.desktop must be removed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/843847 Title: /etc/xdg/gnome-power-manager.desktop must be removed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/843847/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 912912] Re: rhythmbox power manager plugin doesn't show up in plugins dialog
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 you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/912912 Title: rhythmbox power manager plugin doesn't show up in plugins dialog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/912912/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 8357] Re: Allow to set DPI resolution
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. https://bugs.launchpad.net/bugs/8357 Title: Allow to set DPI resolution To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/8357/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 157398] Re: GNOME default DPI doesn't match X default DPI
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 (as indicated in my Xorg.0.log file). Do I need to start a new bug report for this? -- 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/157398 Title: GNOME default DPI doesn't match X default DPI To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/157398/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 812609] Re: nautilus crashed with SIGSEGV in g_slice_free_chain_with_offset()
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 g_slice_free_chain_with_offset() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/812609/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 774487] Re: Totem goes to background when full-screen and out of focus
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 member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/774487 Title: Totem goes to background when full-screen and out of focus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/774487/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 774487] Re: Totem goes to background when full-screen and out of focus
(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 in Ubuntu. https://bugs.launchpad.net/bugs/774487 Title: Totem goes to background when full-screen and out of focus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/774487/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 742398] Re: Missing icon for bluetooth applet
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 because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/742398 Title: Missing icon for bluetooth applet -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 573576] Re: Mousepointer changes aren't taken over
*** 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. * You can subscribe to bug 86184 by following this link: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/86184/+subscribe -- 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/573576 Title: Mousepointer changes aren't taken over -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 552642] Re: Mouse pointer themes do not work after Lucid upgrade
*** 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. * You can subscribe to bug 86184 by following this link: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/86184/+subscribe -- 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/552642 Title: Mouse pointer themes do not work after Lucid upgrade -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 570940] Re: No remaining time displayed when on battery
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, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/570940 Title: No remaining time displayed when on battery -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 570940] Re: No remaining time displayed when on battery
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 desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 660934] [NEW] Network Manager icon disappears after resume from suspend
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 running. If I remove notification-area and add it back again, the icon is restored. When this happens, it looks like there is a 1-px line just to the right of the notification area grabber. Not sure if that is related to this problem or not. Please let me know what additional information I can provide. gnome-panel 1:2.30.2-1ubuntu3 network-manager-gnome 0.8.1+git.20100809t190028.290dc70-0ubuntu3 ** Affects: gnome-panel (Ubuntu) Importance: Undecided Status: New -- Network Manager icon disappears after resume from suspend https://bugs.launchpad.net/bugs/660934 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 545239] Re: Low battery notification is badly worded when remaining time is unknown
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 https://bugs.launchpad.net/bugs/545239 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 desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 615213] Re: gnome-power-manager fails to estimate battery time remaining
*** 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: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/570940/+subscribe -- gnome-power-manager fails to estimate battery time remaining https://bugs.launchpad.net/bugs/615213 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 desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 570940] Re: No remaining time displayed when on battery
** 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 ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 570940] Re: No remaining time displayed when on battery
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 Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 570940] apport information
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 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-22-lpia-tuxonice root=UUID=5763705e-4aea-499b-a989-6ea89eb69d90 ro splash ProcEnviron: LANG=en_GB.utf8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-22.60~ppa4-lpia-tuxonice Tags: lucid Uname: Linux 2.6.31-22-lpia-tuxonice i686 UserGroups: dmi.bios.date: 12/29/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: CN0J14 dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A04 dmi.modalias: dmi:bvnDellInc.:bvrA04:bd12/29/2008:svnDellInc.:pnInspiron910:pvrA04:rvnDellInc.:rnCN0J14:rvrA04:cvnDellInc.:ct8:cvrA04: dmi.product.name: Inspiron 910 dmi.product.version: A04 dmi.sys.vendor: Dell Inc. -- 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 desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 570940] BootDmesg.txt
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 subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 570940] CurrentDmesg.txt
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 subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 570940] Dependencies.txt
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 subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 570940] DevkitPower.txt
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 subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 570940] GConfNonDefault.txt
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, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 570940] Lspci.txt
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 gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 570940] Lsusb.txt
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 gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 570940] ProcCpuinfo.txt
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 subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 570940] ProcInterrupts.txt
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 is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 570940] ProcModules.txt
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 subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 570940] UdevLog.txt
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 to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 570940] UdevDb.txt
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 to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 570940] gnome-power-bugreport.txt
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 Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 437905] Re: System Administration Services (services-admin) missing (Karmic)
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 because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 392122] Re: dim display when idle only dims but doesn't restore the previous value when not idle anymore
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 attempting to get the current brightness from the same place as Power Manager Brightness Applet, and when it fails, it sets the un-idle brightness to the hard-coded value of 50% (from /apps/gnome- power-manager/backlight/brightness_dim_battery). Unfortunately it's very difficult to test this, because the idle dimming is not triggered every time after 10 seconds (gconf setting) as I would expect. I'm not sure what is going on here. It does seem almost random when it is triggered. For some inexplicable reason, they have removed the setting from G-P-M preferences to control what you want your brightness set to when idle. The gconf setting is not absolute, but rather a percentage of the full brightness setting--this I just think is counter-intuitive. In any case, Some of the problem may also have to do with rounding errors. My computer has 8 brightness levels: 12 24 36 48 60 72 84 100. I have brightness_ac set to 100. Then using the acpi hotkeys, I turn the brightness down 1 level to 84. I unplug my AC cable, and it drops to 48 (42 is halfway between 36 and 48 so it rounds up I guess?). Then, when I plug the cable back in, it gets reset to 72! I cannot explain this at all. It repeats this same pattern for every brightness level below 100, but if it is initially at 100 when I unplug it, it gets restored to 100 just fine. I'm not sure all of this is applicable to this bug, it seems like there are several things all going wrong at once here. And I imagine it's machine-specific as well, leading to quite a wonderful mess! -- dim display when idle only dims but doesn't restore the previous value when not idle anymore https://bugs.launchpad.net/bugs/392122 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 desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 497490] Re: Pidgin crashed with SIGSEGV in gdk_pixbuf_loader_eat_header_write()
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 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 subscribed to gtk+2.0 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 497490] [NEW] Pidgin crashed with SIGSEGV in gdk_pixbuf_loader_eat_header_write()
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 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 subscribed to gtk+2.0 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 497490] Re: Pidgin crashed with SIGSEGV in gdk_pixbuf_loader_eat_header_write()
** 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 subscribed to gtk+2.0 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 439783] Re: Regression: devicekit-power does not display remaining battery time
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. Gnome-power-manager should definitely fall back to this behaviour. All the information is right there in the power history, and it is trivial to calculate--I've got an almost perfectly straight line there, losing approx 7% every 12 minutes. Even this crude estimate would be better than nothing! -- Regression: devicekit-power does not display remaining battery time https://bugs.launchpad.net/bugs/439783 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a subscriber of a duplicate bug. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 310353] Re: Default font size too large if using native DPI
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 #157398, and then hopefully this one as well. :) -- 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 subscribed to libgnome in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 348158] Re: F-Spot Encountered a Fatal Error receiving images from Cheese
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 existing f-spot instance. -- F-Spot Encountered a Fatal Error receiving images from Cheese https://bugs.launchpad.net/bugs/348158 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://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 157398] Re: GNOME default DPI doesn't match X default DPI
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 default DPI https://bugs.launchpad.net/bugs/157398 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://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 360204] [NEW] Unhandled exception while importing photos from SD card
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 F-spot to import photos. I do this, and it begins copying the photos. About 24% into copying, I receive the error message at the end of this post. The photos continue copying, however, and everything seems to run fine. It's possible that this is related to having 2 instances of F-spot running. When importing new photos, a 2nd instance of F-spot should not be launched. I will try to reproduce this reliably when I have more time. I'm using f-spot 0.5.0.3-0ubuntu4 on Ubuntu 8.10 on a Dell MINI running lpia architecture. -- F-Spot Encountered a Fatal Error An unhandled exception was thrown: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus) at ICoreProxy.Import (System.String ) [0x0] at FSpot.Driver.Main (System.String[] args) [0x0] .NET Version: 2.0.50727.42 Assembly Version Information: System.Configuration (2.0.0.0) FSpot.Widgets (0.0.0.0) System.Xml (2.0.0.0) NDesk.DBus.Proxies (0.0.0.0) gconf-sharp (2.20.0.0) System.Data (2.0.0.0) Mono.Data.SqliteClient (2.0.0.0) FSpot.Query (0.0.0.0) gdk-sharp (2.12.0.0) gnome-vfs-sharp (2.20.0.0) NDesk.DBus.GLib (1.0.0.0) NDesk.DBus (1.0.0.0) Mono.Posix (2.0.0.0) Cms (0.0.0.0) System (2.0.0.0) FSpot.Utils (0.0.0.0) FSpot.Core (0.0.0.0) atk-sharp (2.12.0.0) gtk-sharp (2.12.0.0) Mono.Addins (0.3.0.0) Mono.Addins.Setup (0.3.0.0) glib-sharp (2.12.0.0) gnome-sharp (2.20.0.0) f-spot (0.5.0.3) mscorlib (2.0.0.0) Platform Information: Linux 2.6.27-4-lpia i686 unknown GNU/Linux Distribution Information: [/etc/debian_version] lenny/sid [/etc/lsb-release] DISTRIB_ID=Ubuntu DISTRIB_RELEASE=8.10 DISTRIB_CODENAME=intrepid DISTRIB_DESCRIPTION=Ubuntu 8.10 ** Affects: f-spot (Ubuntu) Importance: Undecided Status: New -- Unhandled exception while importing photos from SD card https://bugs.launchpad.net/bugs/360204 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to f-spot in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 310353] Re: Default font size too large if using native DPI
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, unreadable fonts on high-resolution displays like mine (150 dpi). -- 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. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 310353] Re: Default font size too large if using native DPI
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 Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 310353] Re: Default font size too large if using native DPI
** 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. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 310353] Re: Default font size too large if using native DPI
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. ** Changed in: gnome-control-center (Ubuntu) Status: Invalid = New -- 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. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 310353] Re: Default font size too large if using native DPI
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 people using 96 dpi displays, and maybe there is a better solution, but I do believe (as Nicolò's screenshots demonstrate) that 10pt is too large when rendered accurately. Personally, I believe the DPI setting should only be changable via xorg.conf/HAL (for advanced users) and there should be a general UI Scale option for users who simply want things to look bigger or visually impaired, etc. that would scale all UI elements. This is way beyond the scope of this particular bug, though. -- 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. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 157398] Re: GNOME default DPI doesn't match X default DPI
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 understood by users as a physical characteristic of the screen, not merely a font preference. -- GNOME default DPI doesn't match X default DPI https://bugs.launchpad.net/bugs/157398 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://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 75324] Re: Gnome file chooser/selector is way to small
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 https://bugs.launchpad.net/bugs/75324 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://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 75324] Re: 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 this, or expect a solution, unless you can reproduce it without Compiz running. Also, I probably wouldn't expect a fix for this issue in Jaunty, so don't worry about debdiffs or patches or anything of the sort. It will get merged with the next Compiz release. -- Gnome file chooser/selector is way to small https://bugs.launchpad.net/bugs/75324 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://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 75324] Re: 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 this, or expect a solution, unless you can reproduce it without Compiz running. Also, I probably wouldn't expect a fix for this issue in Jaunty, so don't worry about debdiffs or patches or anything of the sort. It will get merged with the next Compiz release. -- Gnome file chooser/selector is way to small https://bugs.launchpad.net/bugs/75324 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://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 75324] Re: Gnome file chooser/selector is way to small
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 about the 2nd issue, that compiz is not *always* following this resize directive. Like you said, maybe it is to avoid window instability or some such, but it's still incorrect. So, in my opinion both issues need to be solved, and it seems like they should be tracked separately. If the gtk issue is solved before the compiz issue, then the compiz issue may continue on unsolved, only to resurface at some later time. I would not expect an issue like this will warrant an update in Intrepid, so we would just have to wait for it to be merged upstream so as to appear in the next release. There seems to be some other factor at work here, because a great number of people are not experiencing this bug, otherwise it would indeed be a higher priority. Could it be screen resolution/DPI? I'm also running 1920x1200 like Christian, at 150 dpi. Perhaps the 2nd resize values is being calculated based on the font size + DPI? I will see if I can reproduce this with a new account at the unfortunate standard of 96 dpi. -- Gnome file chooser/selector is way to small https://bugs.launchpad.net/bugs/75324 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://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 310353] Re: Default font size too large if using native DPI
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 DPI as the monitor itself, which will produce same- sized fonts on all monitors, the font is still too big. I imagine most of the people voting for that Brainstorm Idea--and most average users in general--aren't even aware of the DPI problem in Ubuntu/GNOME. ** Summary changed: - Default font size too large + Default font size too large if using native DPI -- 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 subscribed to gnome-control-center in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 157398] Re: GNOME default DPI doesn't match X default DPI
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 surely couldn't read anything without a magnifying glass! I just wanted to point out the following Brainstorm Ideas in support of this change: 161 votes: http://brainstorm.ubuntu.com/idea/7415/ 136 votes: http://brainstorm.ubuntu.com/idea/3448/ 57 votes: http://brainstorm.ubuntu.com/idea/2921/ Of course there may be some overlap here, but that's over 350 people who support DPI auto-detection. I really think this needs to be re- considered . Even if GNOME doesn't implement it by default, Ubuntu can do so easily with a small patch. I would write it myself if I knew it was going to get applied. The user should not even be allowed to choose DPI him or herself, other than to correct a failed auto-detection, as it is a physical characteristic of the display. We could then use a new UI scale option, but this is a separate issue. -- GNOME default DPI doesn't match X default DPI https://bugs.launchpad.net/bugs/157398 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://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 310353] [NEW] Default font size too large
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. I currently have mine set to 7.5, though perhaps I like it smaller than most, and 8 would be a good default. This issue is not apparent for many users, because they are running on higher DPI screens, but GNOME forces the DPI down to 96 instead of the users actual DPI (see bug #157398), so they see the fonts smaller than they actually should be. Once GNOME defaults to using the actual DPI value, this problem will become much more serious. To see if you agree with me, find your DPI by running xdpyinfo | grep resolution, then set your GNOME DPI to an average of the two values in SystemPrefsAppearanceFontsDetails. Make sure all the GNOME fonts are set to 10pt, and then decide if you think this is usable or if it's too big. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- Default font size too large https://bugs.launchpad.net/bugs/310353 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 253072] Re: wrong dpi value for rendering fonts
*** 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 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://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 157398] Re: GNOME default DPI doesn't match X default DPI
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 !300). Any time a reasonable DPI is detected, it must be used as a default, otherwise the fonts on the desktop look completely wrong. There are many other bugs tied to this 99145, 279195, 253072, etc. At issue is the fact that when 96 is used as a default dpi, then the default font sizes in GNOME and many other applications are all much too large (see bug #310353). Please change the status of this bug to confirmed as a fix is very desperately needed! My last laptop only ran at 1024x768 and had a DPI of 85, and this is quite common for a 15 screen. My current laptop has a DPI of 147, and my netbook is 134. None are 96! Also, DPIs are only going to continue to increase as the technology improves. The desktop needs to react to a variable DPI, and render all fonts the same physical size regardless of screen size or resolution. -- GNOME default DPI doesn't match X default DPI https://bugs.launchpad.net/bugs/157398 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://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 279195] Re: OpenOffice.org uses DPI setting to determine page scaling and Gnome hardcodes 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 resolved when #157398 is fixed. ** This bug has been marked a duplicate of bug 157398 GNOME default DPI doesn't match X default DPI -- OpenOffice.org uses DPI setting to determine page scaling and Gnome hardcodes DPI https://bugs.launchpad.net/bugs/279195 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
