[Desktop-packages] [Bug 1251281] Re: gnome-session-flashback/Unity fails to start without hardware acceleration in cloud/remote environments (Forwarded-X/XRDP/VNC/NX/X2GO/Chromoting)
Hi, Same thing is happening to me in Xubuntu 18.04 with xrdp. Is there any fix for this? Thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1251281 Title: gnome-session-flashback/Unity fails to start without hardware acceleration in cloud/remote environments (Forwarded-X/XRDP/VNC/NX/X2GO/Chromoting) Status in gnome-session: Fix Released Status in gnome-session package in Ubuntu: Fix Released Status in gnome-session source package in Trusty: Fix Released Status in gnome-session source package in Utopic: Fix Released Status in gnome-flashback source package in Vivid: Fix Released Status in gnome-session source package in Vivid: Fix Released Status in gnome-session package in Debian: New Bug description: == Impact == It was impossible to launch a gnome-session-based desktop on a system where hardware accelerations is not available (such as old hardware, or when using a remote desktop). That looks like a quite popular use case — more than a hundred of people marked this bug as affecting them. == Test Case == The original bug description below contains a test case. == Proposed Fix == The fix backports an upstream commit which adds --disable-acceleration-check commandline option, and makes Upstart user session pass that flag to gnome-session when the session is gnome-fallback (aka gnome-flashback-metacity). Of course, that option can be used with other sessions as well. This was fixed in vivid in version 3.14.0-2ubuntu4. == Regression Potential == The option was accepted upstream, and nobody complained so far. So the regression potential should be low. This bug will cause static grey or black screen instead of opening remote session using Forwarded-X/XRDP/VNC/NX/X2GO/Chromoting from x2goclient, rdpclient(reminna/vinagre/mstsc), SSH, VNC, NOMACHINE and etc. == Original Description == 1) lsb_release -rd Description: Ubuntu 14.04 LTS Release: 14.04 2) apt-cache policy gnome-session gnome-session: Installed: 3.9.90-0ubuntu12 Candidate: 3.9.90-0ubuntu12 Version table: *** 3.9.90-0ubuntu12 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status 3) What is expected to happen is when one installs xrdp on the host and attempts to use remmina or vinagre on a Ubuntu 14.04 client to RDP in, it works. 4) What happens instead is it shows a gray static screen as per attached screenshot. This would appear an issue with gnome-session as per client log: cat .xsession-errors.old Script for ibus started at run_im. Script for auto started at run_im. Script for default started at run_im. init: indicator-application main process ended, respawning init: indicator-application main process ended, respawning init: indicator-application respawning too fast, stopped Xsession: X session started for at Sun Jul 20 15:25:59 CDT 2014 X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 109 (X_ChangeHosts) Value in failed request: 0x5 Serial number of failed request: 6 Current serial number in output stream: 8 localuser:moniker being added to access control list X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 109 (X_ChangeHosts) Value in failed request: 0x5 Serial number of failed request: 6 Current serial number in output stream: 8 Script for ibus started at run_im. Script for auto started at run_im. Script for default started at run_im. Script for ibus started at run_im. Script for auto started at run_im. Script for default started at run_im. gnome-session-is-accelerated: No composite extension. gnome-session-check-accelerated: Helper exited with code 256 gnome-session-is-accelerated: No composite extension. gnome-session-check-accelerated: Helper exited with code 256 ** (process:2565): WARNING **: software acceleration check failed: Child process exited with code 1 ** (x-session-manager:2565): CRITICAL **: We failed, but the fail whale is dead. Sorry The following is not a WORKAROUND, create /etc/xorg.conf : Section "Device" Identifier "Intel Graphics" Driver "Intel" Option "DRI" "False" EndSection ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-session 3.9.90-0ubuntu12 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jul 20 15:35:23 2014 InstallationDate: Installed on 2014-06-22 (28 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: gnome-session Up
[Desktop-packages] [Bug 1753509] Re: avahi-daemon adds/installs every printer on network
Same happening for me in 18.04. I just removed cups-browsed service. In localhost:631 those "unwanted" printers are gone, but in the rest of applications (like firefox, chrome, etc), still there. So, no fix for this yet? Thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1753509 Title: avahi-daemon adds/installs every printer on network Status in cups-filters package in Ubuntu: Expired Bug description: When connected to a network, avahi-daemon adds & installs all printer on a network without being prompted. This is not desired behaviour. Discovery of the printers is good, but not automatic installation & addition. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 5 09:29:05 2018 InstallationDate: Installed on 2017-09-29 (157 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: avahi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1753509/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1082297] Re: Wrong permissions when using Save As
*** This bug is a duplicate of bug 1084820 *** https://bugs.launchpad.net/bugs/1084820 This bug still exist in 14.04. Any news or workaround? Thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1082297 Title: Wrong permissions when using Save As Status in evince package in Ubuntu: Confirmed Bug description: Steps to reproduce: === 1. Download a PDF from the internet. 2. When Firefox asks what to do with the file, choose the option to open it in Evince. 3. Once the PDF is open in Evince, do a File > Save as. 4. Observe that the file is created with the permissions 0400. Correct behavior: = Evince should follow the same permissions model as other programs, using the umask to determine the default permissions, which would be 0644 on a default Ubuntu machine. Impact of the bug: == Because of the incorrect permissions, it's impossible to directly overwrite an affected PDF without manually fixing the permissions. It makes no sense not to give the owner write permission by default, as any situations where 0400 permissions were desirable would surely be corner cases. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: evince 3.6.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic i686 ApportVersion: 2.6.1-0ubuntu6 Architecture: i386 Date: Fri Nov 23 18:24:52 2012 EcryptfsInUse: Yes InstallationDate: Installed on 2012-10-23 (30 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1082297/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1050358] Re: emesene crashed with SIGSEGV in tupledealloc.24592()
This is also affecting me. Upgraded today Kubuntu 12.10. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/1050358 Title: emesene crashed with SIGSEGV in tupledealloc.24592() Status in “emesene” package in Ubuntu: Confirmed Status in “pygobject” package in Ubuntu: Confirmed Status in “pygobject-2” package in Ubuntu: Confirmed Bug description: When I try to connect to my msn account emesene crash ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: emesene 2.12.5+dfsg-1ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-14.16-generic 3.5.3 Uname: Linux 3.5.0-14-generic x86_64 ApportVersion: 2.5.1-0ubuntu7 Architecture: amd64 CrashCounter: 1 Date: Thu Sep 13 13:12:08 2012 ExecutablePath: /usr/share/emesene/emesene/emesene InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) InterpreterPath: /usr/bin/python2.7 PackageArchitecture: all ProcCmdline: python /usr/bin/emesene -s SegvAnalysis: Segfault happened at: 0x4b6058: mov0x98(%r13),%eax PC (0x004b6058) ok source "0x98(%r13)" (0x0098) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: emesene StacktraceTop: ?? () ?? () ?? () from /usr/lib/python2.7/dist-packages/glib/_glib.so ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: emesene crashed with SIGSEGV in g_main_context_dispatch() UpgradeStatus: Upgraded to quantal on 2012-04-26 (139 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emesene/+bug/1050358/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
