[Bug 1740869] Re: is not respoding window is constantly showing when debugging a program in Eclipse
To update my own workaround, I have switched to LXDE for now (installed lubuntu-desktop). It's pretty drastic, but it completely sidesteps mutter. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1740869 Title: is not respoding window is constantly showing when debugging a program in Eclipse To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1740869/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1780520] [NEW] fwupd fails to refresh because of badly encoded data
Public bug reported: I see the following in my logs several times a day: Jul 5 20:35:45 hostname fwupd[14510]: (fwupd:14510): Fu-WARNING **: FuMain: failed to load AppStream data: Failed to parse /var/cache/app-info/xmls/fwupd.xml file: Erreur à la ligne 265 : L’entité ne se termine pas par un point-virgule ; vous avez probablement utilisé une esperluette sans intention d’écrire une entité — échappez l’esperluette avec & Jul 5 20:36:07 hostname dbus[1044]: [system] Failed to activate service 'org.freedesktop.fwupd': timed out and I get the following message when I run `apt update`: Réception de:18 http://security.ubuntu.com/ubuntu xenial-security/main amd64 DEP-11 Metadata [67,7 kB] Réception de:19 http://security.ubuntu.com/ubuntu xenial-security/main DEP-11 64x64 Icons [68,0 kB] Réception de:20 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 DEP-11 Metadata [107 kB] Réception de:21 http://security.ubuntu.com/ubuntu xenial-security/universe DEP-11 64x64 Icons [142 kB] 1 841 ko réceptionnés en 1s (1 128 ko/s) AppStream cache update completed, but some metadata was ignored due to errors. According to the fwupd author, this is a problem ib appstream-glib and the fix should be backported in 16.04: https://github.com/hughsie/fwupd/issues/565#issuecomment-402541089 There are also a number of reports on ask.ubuntu.com: https://askubuntu.com/questions/1051536/appstreamcli-appstream-system-cache-was-updated-but-problems-were-found-metad?noredirect=1&lq=1 https://askubuntu.com/questions/943463/library-corruption-error-during-apt-get-update ** Affects: appstream-glib (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to appstream-glib in Ubuntu. https://bugs.launchpad.net/bugs/1780520 Title: fwupd fails to refresh because of badly encoded data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream-glib/+bug/1780520/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1779637] Re: Password visible at login screen
** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1779637 Title: Password visible at login screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1779637/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1780507] [NEW] /usr/lib/gvfs/gvfsd-smb-browse:6:talloc_abort:talloc_abort_magic:talloc_chunk_from_ptr:_talloc_free:tevent_req_received
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gvfs. This problem was most recently seen with package version 1.36.1-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/af52d7207f6a2f59968d052220c0a3e453aa40e4 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: gvfs (Ubuntu) Importance: Undecided Status: New ** Tags: artful bionic trusty xenial yakkety zesty -- 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/1780507 Title: /usr/lib/gvfs/gvfsd-smb- browse:6:talloc_abort:talloc_abort_magic:talloc_chunk_from_ptr:_talloc_free:tevent_req_received To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1780507/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1762595] Re: Thunar incorrectly thinks USB storage device hasn't finished ejecting
This bug was fixed in the package gvfs - 1.36.1-0ubuntu3 --- gvfs (1.36.1-0ubuntu3) cosmic; urgency=medium * d/patches/0010-add-missing-source-tag.patch: - Backport upstream patch for udisks2 to fix detection of an ejected USB device (LP: #1762595) -- Sean Davis Sun, 24 Jun 2018 08:08:52 -0400 ** Changed in: gvfs (Ubuntu Cosmic) Status: Fix Committed => Fix Released -- 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/1762595 Title: Thunar incorrectly thinks USB storage device hasn't finished ejecting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1762595/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1780380] Re: modifying an existing archive changes original permissions
** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1780380 Title: modifying an existing archive changes original permissions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1780380/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 204011] Re: Alternative import structure, based on import rolls
** Changed in: f-spot Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/204011 Title: Alternative import structure, based on import rolls To manage notifications about this bug go to: https://bugs.launchpad.net/f-spot/+bug/204011/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1547770] Re: Vinagre / Remote Desktop Viewer won't exit full screen when launched from command line
I have the same issue on 16.04 LTS. None of the workarounds described here work. Once you're in full screen mode there is no way out. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to vinagre in Ubuntu. https://bugs.launchpad.net/bugs/1547770 Title: Vinagre / Remote Desktop Viewer won't exit full screen when launched from command line To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vinagre/+bug/1547770/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1780475] [NEW] Fatal IO error 11 on startup
Public bug reported: Whenever I try to launch totem, I get the following error: Gdk-Message: 20:51:41.044: totem: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. Then, it just crashes. This bug only occurs when using the Nvidia binary driver. However, even using the Nvidia binary driver, it doesn't occur on VLC. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: totem 3.26.0-0ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Jul 6 20:52:08 2018 InstallationDate: Installed on 2018-05-14 (53 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: totem (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1780475 Title: Fatal IO error 11 on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1780475/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows
I found that the "Workspace Indicator" was causing this problem for me. https://extensions.gnome.org/extension/21/workspace-indicator/ Clean install of 18.04 on real hardware. Xorg session. Nvidia 1050 with open source drivers. 2k resolution. Problem did NOT occur for two weeks. Installed "Workspace Indicator" and problem occurred within 24 hours. It reoccurred once or twice every subsequent 24 hours. Uninstalled "Workspace Indicator" and problem has not reoccurred for four days. The problem: gnome shell stops responding to all mouse *clicks* within OS or on gnome shell components. Mouse cursor movement is still possible. All keyboard navigation is still possible. Mouse clicks begin to work again after 5 to 10 minutes. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1181666 Title: gnome-shell randomly blocks mouse clicks from working in app windows To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1181666/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1647187] Re: gnome-software crashed with signal 5 in g_main_context_new()
This happened to me after I installed tuxboot from a deb package using dpkg -i ... . The software installed but claimed to be incomplete because the p7zip-fill package was missing which in turn depended on a i386-library. I declined to install i386 lib on 64-bit system because I was not sure about the effects and te use of it (as a matter of, the installation did not offer to install the mossing package, I just did not do it). After that, my Ubuntu 16.04 issued the message above each time the computer started until I removed tuxboot again using "sudo dpkg -P tuxboot". I found that I was better off without it and managed to create the usb stick I needed using the start media creator tool that comes with Ubuntu (initially I installed tuxboot for that purpose it claimed to be superior to all other tools, which I had unfortunately no chance to confirm) Hope that helps or you found it entertaining at least. Sorry for the damage done to the english language, I am not a native speaker. -- 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/1647187 Title: gnome-software crashed with signal 5 in g_main_context_new() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1647187/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1780468] Re: Blurry titlebar font when window is not maximized
Do you have same problem with metacity? Sounds like you tested only gtk- window-decorator and marco... Can you test also with metacity-theme-viewer? Does it happen also with other themes? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1780468 Title: Blurry titlebar font when window is not maximized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1780468/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1780468] [NEW] Blurry titlebar font when window is not maximized
Public bug reported: What happens I've configured Compiz window manager to use gtk-window-decorator so that it may apply my Metacity theme for the titlebars. With this decorator, I've noticed that Compiz renders slightly blurry titlebar fonts when a window is not maximized. Once the window is maximized, sharp fonts are rendered. When a window is not maximized, the font seems to lack sub-pixel hinting or anti-aliasing, hence the slightly blurry appearance. I zoomed in on the font when the window was maximized and observed bluish lines around the characters. When a window was not maximized, the zoomed-in characters didn't have the bluish lines. I've tested and seen that the Marco window manager and the Emerald decorator (used with Compiz) both render sharp titlebar fonts regardless of whether a window is maximized or not. The image in the below link shows the slight difference in font rendering when Compiz is used with gtk-window-decorator. Firefox's window was maximized, with sharp text, while VLC's window was not maximized, with slightly blurry text. https://i.stack.imgur.com/5BalZ.png Upon switching to Marco window manager, both texts are sharp. https://i.stack.imgur.com/9Gzli.png When the "Compiz with gtk-window-decorator" setup is zoomed-in, blue lines around the maximized Firefox window titlebar text are visible (it looks like sub-pixel rendering to me). The blue lines are completely lacking in the un-maximized VLC window titlebar text. https://i.stack.imgur.com/XDSAU.png What I expect to happen --- The titlebar font rendering should be sharp for both maximized and un-maximized windows. The cause (clip_to_rounded_corners) --- Upon investigating, I've discovered that Compiz's gtk-window-decorator uses the libmetacity library. The clip_to_rounded_corners() function in "meta-theme-metacity.c" is called to draw rounded corners for the un-maximized windows in my theme. It seems the call to draw rounded corners by cairo_arc() in that function somehow affects the font rendering. When windows are maximized, the drawing of rounded corners is not performed, hence the sharp font rendering. I rebuilt the libmetacity library with the clip_to_rounded_corners() call commented out and achieved sharp fonts for un-maximized windows. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: metacity 1:3.28.0-1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: MATE Date: Fri Jul 6 19:52:03 2018 InstallationDate: Installed on 2018-05-06 (61 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: metacity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: metacity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1780468 Title: Blurry titlebar font when window is not maximized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1780468/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1779476] Re: Boot process hangs indefinitely. Never finishes.
To restore the splash I reinstalled the ubuntu plymouth. apt-get install plymouth=0.9.3-1ubuntu7 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1779476 Title: Boot process hangs indefinitely. Never finishes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1779476/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1780267] Re: 3.28.3 stable update
Hello Sebastien, or anyone else affected, Accepted gnome-disk-utility into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome-disk- utility/3.28.3-0ubuntu1~18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: gnome-disk-utility (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1780267 Title: 3.28.3 stable update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1780267/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1769637] Re: Update evolution-data-server to 3.28.3
Hello Jeremy, or anyone else affected, Accepted evolution-data-server into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /evolution-data-server/3.28.3-0ubuntu0.18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: evolution-data-server (Ubuntu Bionic) Status: Triaged => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1769637 Title: Update evolution-data-server to 3.28.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1769637/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1779476] Re: Boot process hangs indefinitely. Never finishes.
@Mark, I just used the browser and let the software installer mime-type binding take care of it. Be warned: after installing this my splash screen was gone (it was using xubuntu theme), so you may need to reconfigure that afterwards -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1779476 Title: Boot process hangs indefinitely. Never finishes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1779476/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1779476] Re: Boot process hangs indefinitely. Never finishes.
After installing plymouth_0.9.3-3_amd64.deb gdm3 STILL DOES NOT START. Without haveged installed lightdm still takes AGES to start. plymouth 0.9.3-3 is NOT a resolution to this. And PLEASE change the title back. The original complaint was: gdm3 does not start, not that the boot process never completed. As I said: "In both cases I can see the X process running (Xwayland or Xorg) but no vt has it." Follow your own advise on comment #19 and do not group the gdm3 issue together with the delay on lightdm -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1779476 Title: Boot process hangs indefinitely. Never finishes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1779476/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1780280] Re: 3.28.2 stable update
Hello Sebastien, or anyone else affected, Accepted gnome-control-center into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /gnome-control-center/1:3.28.2-0ubuntu0.18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: gnome-control-center (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- 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/1780280 Title: 3.28.2 stable update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1780280/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1779476] Re: Boot process hangs indefinitely. Never finishes.
Re. comment #42, how do you install that download package on Ubuntu? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1779476 Title: Boot process hangs indefinitely. Never finishes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1779476/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1779476] Re: Boot process hangs indefinitely. Never finishes.
Why was the title changed? It DOES NOT MATCH AT ALL the symptoms I reported! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1779476 Title: Boot process hangs indefinitely. Never finishes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1779476/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 106060] Re:
http://hope.reshefcpa.com Greg Clark -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/106060 Title: [r128 1002:5446] Selecting the Molecule screensaver makes the PC freeze. It is completely unresponsive. To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-r128/+bug/106060/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1780365] Re: Credentials located in gnome-keyring can be compromised easily
** Description changed: Dear all, I figure out that login credentials, located in gnome-keyring, can be easily compromised. Linux based on Gnome basically uses ‘gnome-keyring’ as their backend to store login credentials in a secure manner. Specifically, google-chrome browser, network-manager and gnome-online-accounts use this as a backend solution to store login credentials. - To use this, authentication is performed together with gnome-keyring as part of ‘pam-gnome-keyring.so’. At this point, it remains unlocked until system is shut down or logged out. In this state, a simple program that uses ‘Secret Service API’ call and their ‘D-Bus’ interface can easily retrieve login credentials from those gnome-keyring without any privilege escalation, listening into the X events going to another window, or installation an application on target computer. + To use this, authentication is performed together with gnome-keyring as part of ‘pam-gnome-keyring.so’. At this point, it remains unlocked until system is shut down or logged out. In this state, a simple program that uses ‘Secret Service API’ call and their ‘D-Bus’ interface can easily retrieve login credentials from those gnome-keyring without any privilege escalation, listening into the X events going to another window, or installation an application on target computer. (please check PoC source https://github.com/sungjungk/keyring_crack and video https://youtu.be/Do4E9ZQaPck) The issue is different from the content shown on the Ubuntu Security FAQ and GnomeKeyring Wiki [1][2]. It was even said that “PAM session is closed via the screensaver, all keyrings are locked, and the ‘login’ keyring is unlocked upon successful authentication to the screensaver”. After trying to crack the keyring, it was far from what they really thought. It is no different than plain text file for login credentials somewhere on disk. To deal with, the root cause of the problem is that ‘Secret Service API’ on anyone can be easily accessed on DBus API. If access control is enabled, only well-known? or authorized processes, such as google- chrome, network-manager, and gnome-online-accounts, will be able to access the login credentials. DBus originally provides capability that is essential to access control of DBus API by defining security policy as a form of *.conf file. Currently, various services based on DBus interface are employing above security policy feature to perform access control. For example, login/system related functions is controlled from ‘login1’ and its security policy is described in “org.freedesktop.login1.conf”. (see https://github.com/systemd/systemd/blob/master/src/core/org.freedesktop.systemd1.conf) Likewise, why don’t we try adopting the access control of secret service API into gnome-keyring environment? Due to the fact that a process with root privilege can access “.conf” file, an approved program may only update the target file during installation process Here is really simple ‘org.freedesktop.secrets.conf’ example. = http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd";> + "http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd";> - + - + + + - - + + - - - - - - + + + = - Many Thanks!! [1] https://wiki.ubuntu.com/SecurityTeam/FAQ#Contact [2] https://wiki.gnome.org/Projects/GnomeKeyring/SecurityPhilosophy ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-keyring 3.28.0.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jul 5 17:45:22 2018 InstallationDate: Installed on 2018-07-06 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) ** Information type changed from Public to Private Security -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1780365 Title: Credentials located in gnome-keyring can be compromised easily To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/178
[Bug 1780444] Re: rhythmbox on Ubuntu 18.04 does not adopt CSD even when default alternative toolbar plugin is ON
But, then again, I can't get CSD to work even after switching Application menu back ON in the top bar. -- 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/1780444 Title: rhythmbox on Ubuntu 18.04 does not adopt CSD even when default alternative toolbar plugin is ON To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1780444/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1780444] Re: rhythmbox on Ubuntu 18.04 does not adopt CSD even when default alternative toolbar plugin is ON
Sorry, I noticed there is another bug filed: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1720649 This is exactly the situation in my case as well. I'm not sure how to delete this bug report. -- 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/1780444 Title: rhythmbox on Ubuntu 18.04 does not adopt CSD even when default alternative toolbar plugin is ON To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1780444/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1780444] [NEW] rhythmbox on Ubuntu 18.04 does not adopt CSD even when default alternative toolbar plugin is ON
Public bug reported: Description:Ubuntu 18.04 LTS Release:18.04 rhythmbox: Installed: 3.4.2-4ubuntu1 Candidate: 3.4.2-4ubuntu1 Version table: *** 3.4.2-4ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status I expect to see GNOME CSD in Rhythmbox, but today I saw that CSD was not being implemented and the old giant titlebar was implemented. Not sure when this change took place, but I noticed it today. I checked the plugins and Alternative Toolbar plugin was turned ON. I'd not touched plugin settings at all since installation. I was using stock Rhythmbox - never touched settings. ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Image showing CSD is not implemented although Alternative Toolbar plugin in ON" https://bugs.launchpad.net/bugs/1780444/+attachment/5160430/+files/Screenshot-20180706152205-1541x743.png -- 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/1780444 Title: rhythmbox on Ubuntu 18.04 does not adopt CSD even when default alternative toolbar plugin is ON To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1780444/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1780442] [NEW] Please backport fix for & in attributes
Public bug reported: [Impact] There are instances of fwupd being unable to run updates on certain devices on Ubuntu 16.04. due to a "&" in metadata. [Test Case] * Try to perform an update on a 8bitdo affected device. [Regression Potential] * Regressions would occur in metadata processing where the fwupd daemon wouldn't be able to process it. [Other Info] This was discussed here: https://github.com/hughsie/fwupd/issues/565#issuecomment-402534337 This has been fixed in appstream-glib to prevent & in the metadata. This fix is already in 18.04 and just needs to be backported to 16.04. https://github.com/hughsie/appstream-glib/commit/6048520484101df5d33f3c852c10640e630d20cf ** Affects: fwupd Importance: Unknown Status: Unknown ** Affects: appstream-glib (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: appstream-glib (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: appstream-glib (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: appstream-glib (Ubuntu) Status: New => Fix Released ** Description changed: - There are instances of fwupd being unable to run updates on certain devices on Ubuntu 16.04. due to a "&" in metadata. + [Impact] + + There are instances of fwupd being unable to run updates on certain + devices on Ubuntu 16.04. due to a "&" in metadata. + + [Test Case] + + * Try to perform an update on a 8bitdo affected device. + + [Regression Potential] + + * Regressions would occur in metadata processing where the fwupd daemon + wouldn't be able to process it. + + [Other Info] + + This was discussed here: https://github.com/hughsie/fwupd/issues/565#issuecomment-402534337 This has been fixed in appstream-glib to prevent & in the metadata. This fix is already in 18.04 and just needs to be backported to 16.04. https://github.com/hughsie/appstream-glib/commit/6048520484101df5d33f3c852c10640e630d20cf ** Bug watch added: github.com/hughsie/fwupd/issues #565 https://github.com/hughsie/fwupd/issues/565 ** Also affects: fwupd via https://github.com/hughsie/fwupd/issues/565 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to appstream-glib in Ubuntu. https://bugs.launchpad.net/bugs/1780442 Title: Please backport fix for & in attributes To manage notifications about this bug go to: https://bugs.launchpad.net/fwupd/+bug/1780442/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 279629] Re: Multilayer TIFFs only show one layer.
** Changed in: f-spot Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/279629 Title: Multilayer TIFFs only show one layer. To manage notifications about this bug go to: https://bugs.launchpad.net/f-spot/+bug/279629/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1748280] Re: 'nova reboot' on arm64 is just 'nova reboot --hard' but slower
** Also affects: nova 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/1748280 Title: 'nova reboot' on arm64 is just 'nova reboot --hard' but slower To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1748280/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1120149] Re: No touchscreen gestures in evince presentation
One observation is that the mode "click = next slide" is a real pain in Evince. It makes impossible to launch external files (movies, etc) while in presentation mode... -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1120149 Title: No touchscreen gestures in evince presentation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1120149/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1087240] Re: A minimized window 'remains' behind on the desktop (Firefox thunderbird libreoffice)
Hello Luxiter, Thank you for submitting this bug and reporting a problem with minimizing windows. You made this bug report in 2012 and there have been several versions of Ubuntu since then. Could you confirm that this is no longer a problem and that we can close the ticket? Or, if it is still a problem, could you run the following (only once): apport-collect 1087240 and upload the updated logs and and any other logs that are relevant for this particular issue. Thank you again for helping make Ubuntu better. G ** Changed in: gnome-session (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1087240 Title: A minimized window 'remains' behind on the desktop (Firefox thunderbird libreoffice) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1087240/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1779846] Re: Pressing Alt+Backslash locks up all windows (no focus)
> First, please try removing these shell extensions: A-Ha! Sorry, i've played with some extensions and never minded about them. I've disabled (it suffices, it was not needed to uninstall them) 'system-monitor' and 'windows-alt-tab' and problem desappear. Many thanks and sorry for that bug report! -- 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/1779846 Title: Pressing Alt+Backslash locks up all windows (no focus) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1779846/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778607] Re: Incorrect licenses listed in the GNOME Software for Snap Apps.
I confirm that now Chromium snap is listed as "free" in the Software Center. However Chroimum "source: local" is still proprietary - https://i.imgur.com/zM5xDSr.png Also, Chromium was one example of such a bug. I see many MIT or GPL3 licencesed software labeled as proprietary in the Software Center.To test install Ulauncher (GPL3) or Stacer (MIT), to name 2 random ones. -- 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/1778607 Title: Incorrect licenses listed in the GNOME Software for Snap Apps. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1778607/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1075286] Re: gnome-settings-daemon crashed with sigabrt in raise()
Sorry Hugo, I meant ...problem with the gnome-settings-daemon package... :) ** Changed in: gnome-settings-daemon (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1075286 Title: gnome-settings-daemon crashed with sigabrt in raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1075286/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1075286] Re: gnome-settings-daemon crashed with sigabrt in raise()
Hello Hugo, Thank you for submitting this bug and reporting a problem with Thunderbird. You made this bug report in 2012 and there have been several versions of Ubuntu and Thunderbird since then. Could you confirm that this is no longer a problem and that we can close the ticket? Or, if it is still a problem, could you run the following (only once): apport-collect 1075286 and upload the updated logs and and any other logs that are relevant for this particular issue. Thank you again for helping make Ubuntu and Thunderbird better. G -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1075286 Title: gnome-settings-daemon crashed with sigabrt in raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1075286/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1779476] Re: Boot process hangs indefinitely. Never finishes.
** Changed in: plymouth (Debian) Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1779476 Title: Boot process hangs indefinitely. Never finishes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1779476/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 398438] Re: f-spot date field is ambigious (and wrong for much of the world)
** Changed in: f-spot Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/398438 Title: f-spot date field is ambigious (and wrong for much of the world) To manage notifications about this bug go to: https://bugs.launchpad.net/f-spot/+bug/398438/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778607] Re: Incorrect licenses listed in the GNOME Software for Snap Apps.
I updated the chromium license to BSD-3-Clause (see https://cs.chromium.org/chromium/src/LICENSE). The snapcraft dashboard allows selecting multiple licenses, but it says "Multiple licenses can be selected to indicate alternative choices", so I don't think that's what we want (chromium code is governed by multiple licenses, but it's not an either/or choice). I verified that, following the change, the chromium snap is listed as free software in gnome-software. -- 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/1778607 Title: Incorrect licenses listed in the GNOME Software for Snap Apps. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1778607/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1780247] Re: Gedit misrecognises encoding on plain ASCII file
Attached an image showing the issue in action. ** Attachment added: "Image showing issue" https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1780247/+attachment/5160311/+files/bugreport.png -- 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/1780247 Title: Gedit misrecognises encoding on plain ASCII file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1780247/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 410636] Re: Right-click should not pre-light first option, too easy to accidentally select the first Context-menu option.
I just discovered that the temporary solution as described in previous post #20 seem to hold only for the current browser window which has been once expanded and bounced up in order to correct the offset, however, opening a new window or right click on a link and selecting "Open link in New Window" will bring the offset anomaly back but only for those new windows opened up, same for when opening up a "New Private Window". -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/410636 Title: Right-click should not pre-light first option, too easy to accidentally select the first Context-menu option. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/410636/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1780390] Re: gedit - incorrect print preview - 2 pages per side
** Attachment added: "print preview" https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1780390/+attachment/5160294/+files/Screenshot%20from%202018-07-06%2009-52-39.png -- 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/1780390 Title: gedit - incorrect print preview - 2 pages per side To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1780390/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1780390] [NEW] gedit - incorrect print preview - 2 pages per side
Public bug reported: Steps: 1. open gedit with text file ( 145 lines - sample attached) 2. menu > print > page setup > pages per side=2; orientation=portrait > Preview Observed: Layout uses only left side of each sheet ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Attachment added: "ubuntu-test-preview.txt" https://bugs.launchpad.net/bugs/1780390/+attachment/5160293/+files/ubuntu-test-preview.txt ** Package changed: splix (Ubuntu) => gedit (Ubuntu) -- 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/1780390 Title: gedit - incorrect print preview - 2 pages per side To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1780390/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
