[Desktop-packages] [Bug 1983185] Re: Recent commit breaks /etc/X11/Xsession
This change makes xpra nearly unusable, because Xpra then ends up creating an entire desktop session, forwarding a lot of unwanted taskbars (which you can't close without killing xpra), and it nags about permissions to create a color profile. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1983185 Title: Recent commit breaks /etc/X11/Xsession Status in xorg package in Ubuntu: Confirmed Status in xorg package in Debian: New Bug description: The following command: $/etc/X11/Xsession true opens a dialog with the following error message: "Xsession: unable to launch "true" X session --- "true" not found; falling back to default session." There is a "Okay" button on this message, and clicking it does bad things if one happens to be running Ubuntu 22.04 on Xorg (or running Gnome on Xorg, which is seemingly a different option for the the low latency installation I am running: 5.15.0-43-generic #46-Ubuntu SMP Tue Jul 12 10:30:17 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux). See Brendan O'Dea's related comment about this behavior on debian- bugs-dist: https://www.mail-archive.com/debian-bugs- d...@lists.debian.org/msg1857023.html This has consequences in my use of xpra. For example, if I use xpra via the run_scaled-master script to magnify a single application's interface for a 4K display I get the error dialog mentioned above, often with resulting system instability. This behavior cropped up last month. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.73.05 Sat May 7 05:30:26 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None Date: Sat Jul 30 10:14:43 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.34, 5.15.0-41-lowlatency, x86_64: installed virtualbox/6.1.34, 5.15.0-43-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:3e94] (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2269] NVIDIA Corporation GP104GLM [Quadro P5200 Mobile] [10de:1bb5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GP104GLM [Quadro P5200 Mobile] [17aa:2269] InstallationDate: Installed on 2022-07-13 (16 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 20MBCTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_aze0rg@/vmlinuz-5.15.0-43-generic root=ZFS=rpool/ROOT/ubuntu_aze0rg ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/10/2022 dmi.bios.release: 1.47 dmi.bios.vendor: LENOVO dmi.bios.version: N2CET64W (1.47 ) dmi.board.asset.tag: Not Available dmi.board.name: 20MBCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.16 dmi.modalias: dmi:bvnLENOVO:bvrN2CET64W(1.47):bd06/10/2022:br1.47:efr1.16:svnLENOVO:pn20MBCTO1WW:pvrThinkPadP72:rvnLENOVO:rn20MBCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20MB_BU_Think_FM_ThinkPadP72: dmi.product.family: ThinkPad P72 dmi.product.name: 20MBCTO1WW dmi.product.sku: LENOVO_MT_20MB_BU_Think_FM_ThinkPad P72 dmi.product.version: ThinkPad P72 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau:
[Desktop-packages] [Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
Still broken, 17th September 2022 in Ubuntu 22.04. Evince prints the following message "env: ‘/snap/bin/firefox’: Permission denied" Workaround: https://github.com/popey/unsnap -- 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/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Confirmed Status in evince package in Ubuntu: Triaged Status in apparmor source package in Jammy: Confirmed Status in evince source package in Jammy: Confirmed Status in evince package in Debian: New Bug description: [Impact] * Users cannot open a hyperlink in a PDF opened with evince when the default browser is a snap. * The fix creates a snap_browsers abstraction on AppArmor which can be used in a transition for when the browser is executed. The snap_browsers abstraction provides the minimal amount of permissions required to execute a browser provided through snaps. This is a workaround since AppArmor currently does not provide mediation/filtering on enhanced environment variables. [Test Plan] * Make sure the default browser is provided through the snap store. * Open a PDF that contains a hyperlink using evince and click on the URL. * The browser should open the requested URL. [Where problems could occur] * If the browser or snap core update to have new requirements for opening a browser, then the current policy could become obsolete and will need to be updated again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+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 1923040] Re: en-gb thesaurus is missing
Thanks for your response. I looked a bit more into it, and it seems that the official recommended way of dealing with this problem is the symlink approach, and that en-GB is explicitly provided by the en-US package - the compiler of the thesaurus intentionally combined both languages' spelling variants as synonyms within the same thesaurus. http://astarix.co.uk/2012/06/proper-british-language-tools-libreoffice/ https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749204 https://askubuntu.com/questions/42850/how-do-i-add-english-uk-thesaurus-and-other-locales-to-libreoffice In fact, it even gives the right British-English options. When I test it in LibreOffice, and search for the word "hue", it prompts me with both "color" (USA) and "colour" (GB). Similarly, it offers "aluminium" and "aluminum" as synonyms, and "pavement" and "sidewalk". So, please reconsider - or at least create a metapackage "mythes-en-GB" which depends on "mythes-en" and contains the symlinks. (After all, should a better solution arise i.e. someone compiles a dedicated en-GB thesaurus, we can always improve, but this approach gets 99.9% of the way there, vs. nothing, - and in the unlikely event that the GB-user ends up with a US-english word, such as "color", it is already caught by the GB-english spellchecker). ** Bug watch added: Debian Bug tracker #749204 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749204 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice-dictionaries in Ubuntu. https://bugs.launchpad.net/bugs/1923040 Title: en-gb thesaurus is missing Status in libreoffice-dictionaries package in Ubuntu: Won't Fix Bug description: Problem: The EN-GB thesaurus is missing for LibreOffice. To observe: 1. Fresh install of 21.04, set Location to United Kingdom. 2. Start LibreOffice Writer, choose the Tools menu. 3. The "Thesaurus" item is greyed out. Root cause: there is no mythes-en-gb package available (but there is mythes-en-us). Workaround: Give British English speakers the American English thesaurus i.e. symlink the US thesaurus by the GB one. cd /usr/share/mythes; ln -s th_en_US_v2.dat th_en_GB_v2.dat; ln -s th_en_US_v2.idx th_en_GB_v2.idx; Note: this report and tested workaround is on a fresh install of 21.04, although this problem has been extant for years. There appears to be no GB version of the thesaurus. However, as UK-english and USA- english language is so similar, it would be OK to provide the thesaurus from the US package in the meantime as a symlink. For others who find this bug report while searching the same issue, note that en-us is "english united-states" en-gb is "english great-britain", -ukis "ukraine". (Don't look for "english united-kingdom", en-uk, which doesn't exist). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice-dictionaries/+bug/1923040/+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 1849371] Re: [snap] Cannot run chromium as user www-data because home directory is /var/www
The snap confinement also seems to create a number of other problems. I've also observed: * Webmail - if I receive an attachment of certain types (libreoffice is broken; pdf is OK), then I get a "please confirm you want to allow chromium to open this file" dialog every single time. * password manager (save passwords) is broken - it won't remember passwords I saved, nor does it remember my preference not to save the passwords for web-development on localhost, but prompts every time. * cross site logins are broken (sign into gmail for work, and other sites that use that gmail auth just fail). * some extensions break (e.g. the JSONViewer is silently-non- functional.) All of these are fixed if I download and unzip the binary from here: https://download-chromium.appspot.com/ - though it sacrifices the entire point of running a distro. I understand the rationale for saving developer time, but this is really broken for me and my company. If it would help, we'd happily be invoiced £500 by the Ubuntu project if you could go back to the deb build - even if you chose only to ship alternate releases. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1849371 Title: [snap] Cannot run chromium as user www-data because home directory is /var/www Status in snapd: Confirmed Status in chromium-browser package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Bug description: Since the move to snap, and upgrade to 19.10, I can no longer use headless-chromium to do automated conversions. The script, as currently run by Apache (user www-data) as a back-end server process is: /usr/bin/timeout 60 chromium-browser --no-sandbox --headless --disable-gpu --window-size=2048,1448 --screenshot='dummy.pdf' 'http://localhost/[...]' 2>&1 2>&1 This returns error 1, with: dconf-CRITICAL **: 19:41:17.958: unable to create directory '/var/www/.cache/dconf': Permission denied. dconf will not work properly. WARNING: cannot create user data directory: cannot create "/var/www/snap/chromium/899": mkdir /var/www/snap: permission denied Sorry, home directories outside of /home are not currently supported. See https://forum.snapcraft.io/t/11209 for details. So... how are we supposed to use scripted Chrome for headless work, when the snaps don't support it? This is a major blocker for me, as it completely destroys my ability to do any development work, because the build-toolchain for selftests relies on the ability of chrome to operate headless. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: chromium-browser 77.0.3865.120-0ubuntu1~snap1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: MATE DRM.card0-DP-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: enabled dpms: On status: connected edid-base64: AP///wBMLToINDAxMCsWAQOANCB4KgHxoldSnycKUFS/74BxT4EAgUCBgJUAlQ+pQLMAKDyAoHCwI0AwIDYABkQhAAAa/QA4Sx5REQAKICAgICAg/ABTTVMyNEE0NTAKICAg/wBINE1DQTEzMzYyCiAgAQkCAQQAAjqA0HI4LUAQLEWABkQhAAAeAR0AclHQHiBuKFUABkQhAAAeAR0AvFLQHiC4KFVABkQhAAAejArQkCBAMSAMQFUABkQhAAAYjArQiiDgLRAQPpYABkQhAAAY0g== modes: 1920x1200 1920x1080 1600x1200 1680x1050 1280x1024 1280x1024 1440x900 1440x900 1280x960 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 720x576 720x480 720x480 640x480 640x480 640x480 640x480 640x480 720x400 DRM.card0-HDMI-A-2: enabled: enabled dpms: On status: connected edid-base64: AP///wAlpVNWODYxMB0NAQOBKR//6uWVpVhMlyYeUFS/7wCBgKlAMVlFWWFZgZkBAQEBSD9AMGKwMkAAwAMAmDIRAAAe/QA4VR9cEQAKICAgICAg/wBCSEZGS0I2MzAwMTY4/ABMMjBDTQogICAgICAgAMU= modes: 1600x1200 1280x1024 1280x1024 1280x1024 1024x768 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 800x600 640x480 640x480 640x480 640x480 640x480 720x400 DRM.card0-HDMI-A-3: enabled: enabled dpms: On status: connected edid-base64: AP///wAlpVNWNjIyMB0NAQOBKR//6uWVpVhMlyYeUFS/7wCBgKlAMVlFWWFZgZkBAQEBSD9AMGKwMkAAwAMAmDIRAAAe/QA4VR9cEQAKICAgICAg/wBCSEZGS0I2MzAwMjI2/ABMMjBDTQogICAgICAgAM8= modes: 1600x1200 1280x1024 1280x1024 1280x1024 1024x768 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 800x600 640x480 640x480 640x480 640x480 640x480 720x400 Date: Tue Oct 22 19:48:51 2019 DiskUsage: Filesystem Type Size Used Avail Use% Mounted on /dev/sdb1 ext4 1.8T 491G 1.3T 29% /home tmpfs tmpfs 32G 927M 31G 3% /dev/shm /dev/sdb1 ext4 1.8T
[Desktop-packages] [Bug 1849371] Re: [snap] Cannot run headless chromium as user www-data
Thanks for the suggestion, and you're right, your summary is better. I tried the following (with various permutations). sudo su -l -s /bin/bash www-data mkdir /tmp/chromium-home HOME=/tmp/chromium-home /usr/bin/timeout 60 chromium-browser --no- sandbox --headless --disable-gpu --window-size=2048,1448 --screenshot='/tmp/dummy.pdf' --user-data-dir=/tmp/chromium-home 'http://localhost/...' and this complains in a different way: Sorry, home directories outside of /home are not currently supported. See https://forum.snapcraft.io/t/11209 for details. Before the snap change was made, chromium would run headless without (I think) actually needing any writeable directory at all. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1849371 Title: [snap] Cannot run headless chromium as user www-data Status in chromium-browser package in Ubuntu: New Bug description: Since the move to snap, and upgrade to 19.10, I can no longer use headless-chromium to do automated conversions. The script, as currently run by Apache (user www-data) as a back-end server process is: /usr/bin/timeout 60 chromium-browser --no-sandbox --headless --disable-gpu --window-size=2048,1448 --screenshot='dummy.pdf' 'http://localhost/[...]' 2>&1 2>&1 This returns error 1, with: dconf-CRITICAL **: 19:41:17.958: unable to create directory '/var/www/.cache/dconf': Permission denied. dconf will not work properly. WARNING: cannot create user data directory: cannot create "/var/www/snap/chromium/899": mkdir /var/www/snap: permission denied Sorry, home directories outside of /home are not currently supported. See https://forum.snapcraft.io/t/11209 for details. So... how are we supposed to use scripted Chrome for headless work, when the snaps don't support it? This is a major blocker for me, as it completely destroys my ability to do any development work, because the build-toolchain for selftests relies on the ability of chrome to operate headless. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: chromium-browser 77.0.3865.120-0ubuntu1~snap1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: MATE DRM.card0-DP-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: enabled dpms: On status: connected edid-base64: AP///wBMLToINDAxMCsWAQOANCB4KgHxoldSnycKUFS/74BxT4EAgUCBgJUAlQ+pQLMAKDyAoHCwI0AwIDYABkQhAAAa/QA4Sx5REQAKICAgICAg/ABTTVMyNEE0NTAKICAg/wBINE1DQTEzMzYyCiAgAQkCAQQAAjqA0HI4LUAQLEWABkQhAAAeAR0AclHQHiBuKFUABkQhAAAeAR0AvFLQHiC4KFVABkQhAAAejArQkCBAMSAMQFUABkQhAAAYjArQiiDgLRAQPpYABkQhAAAY0g== modes: 1920x1200 1920x1080 1600x1200 1680x1050 1280x1024 1280x1024 1440x900 1440x900 1280x960 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 720x576 720x480 720x480 640x480 640x480 640x480 640x480 640x480 720x400 DRM.card0-HDMI-A-2: enabled: enabled dpms: On status: connected edid-base64: AP///wAlpVNWODYxMB0NAQOBKR//6uWVpVhMlyYeUFS/7wCBgKlAMVlFWWFZgZkBAQEBSD9AMGKwMkAAwAMAmDIRAAAe/QA4VR9cEQAKICAgICAg/wBCSEZGS0I2MzAwMTY4/ABMMjBDTQogICAgICAgAMU= modes: 1600x1200 1280x1024 1280x1024 1280x1024 1024x768 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 800x600 640x480 640x480 640x480 640x480 640x480 720x400 DRM.card0-HDMI-A-3: enabled: enabled dpms: On status: connected edid-base64: AP///wAlpVNWNjIyMB0NAQOBKR//6uWVpVhMlyYeUFS/7wCBgKlAMVlFWWFZgZkBAQEBSD9AMGKwMkAAwAMAmDIRAAAe/QA4VR9cEQAKICAgICAg/wBCSEZGS0I2MzAwMjI2/ABMMjBDTQogICAgICAgAM8= modes: 1600x1200 1280x1024 1280x1024 1280x1024 1024x768 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 800x600 640x480 640x480 640x480 640x480 640x480 720x400 Date: Tue Oct 22 19:48:51 2019 DiskUsage: Filesystem Type Size Used Avail Use% Mounted on /dev/sdb1 ext4 1.8T 491G 1.3T 29% /home tmpfs tmpfs 32G 927M 31G 3% /dev/shm /dev/sdb1 ext4 1.8T 491G 1.3T 29% /home InstallationDate: Installed on 2017-02-03 (991 days ago) InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64 (20170125) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=6ef42be7-d431-4d0d-bc57-79f7a96980ef ro Snap.ChromeDriverVersion: ERROR: ld.so: object 'libgtk3-nocsd.so.0' from LD_PRELOAD cannot be preloaded (failed to map segment from shared object): ignored. ChromeDriver 77.0.3865.120
[Desktop-packages] [Bug 1849371] [NEW] headless chromium broken (as a consequence of snap)
Public bug reported:
Since the move to snap, and upgrade to 19.10, I can no longer use
headless-chromium to do automated conversions.
The script, as currently run by Apache (user www-data) as a back-end
server process is:
/usr/bin/timeout 60 chromium-browser --no-sandbox --headless --disable-
gpu --window-size=2048,1448 --screenshot='dummy.pdf'
'http://localhost/[...]' 2>&1 2>&1
This returns error 1, with:
dconf-CRITICAL **: 19:41:17.958: unable to create directory
'/var/www/.cache/dconf': Permission denied. dconf will not work
properly.
WARNING: cannot create user data directory: cannot create
"/var/www/snap/chromium/899":
mkdir /var/www/snap: permission denied
Sorry, home directories outside of /home are not currently supported.
See https://forum.snapcraft.io/t/11209 for details.
So... how are we supposed to use scripted Chrome for headless work, when the
snaps don't support it?
This is a major blocker for me, as it completely destroys my ability to do any
development work, because the build-toolchain for selftests relies on the
ability of chrome to operate headless.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: chromium-browser 77.0.3865.120-0ubuntu1~snap1
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
CurrentDesktop: MATE
DRM.card0-DP-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wBMLToINDAxMCsWAQOANCB4KgHxoldSnycKUFS/74BxT4EAgUCBgJUAlQ+pQLMAKDyAoHCwI0AwIDYABkQhAAAa/QA4Sx5REQAKICAgICAg/ABTTVMyNEE0NTAKICAg/wBINE1DQTEzMzYyCiAgAQkCAQQAAjqA0HI4LUAQLEWABkQhAAAeAR0AclHQHiBuKFUABkQhAAAeAR0AvFLQHiC4KFVABkQhAAAejArQkCBAMSAMQFUABkQhAAAYjArQiiDgLRAQPpYABkQhAAAY0g==
modes: 1920x1200 1920x1080 1600x1200 1680x1050 1280x1024 1280x1024 1440x900
1440x900 1280x960 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768
1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 720x576 720x480
720x480 640x480 640x480 640x480 640x480 640x480 720x400
DRM.card0-HDMI-A-2:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAlpVNWODYxMB0NAQOBKR//6uWVpVhMlyYeUFS/7wCBgKlAMVlFWWFZgZkBAQEBSD9AMGKwMkAAwAMAmDIRAAAe/QA4VR9cEQAKICAgICAg/wBCSEZGS0I2MzAwMTY4/ABMMjBDTQogICAgICAgAMU=
modes: 1600x1200 1280x1024 1280x1024 1280x1024 1024x768 1024x768 1024x768
1024x768 832x624 800x600 800x600 800x600 800x600 800x600 640x480 640x480
640x480 640x480 640x480 720x400
DRM.card0-HDMI-A-3:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAlpVNWNjIyMB0NAQOBKR//6uWVpVhMlyYeUFS/7wCBgKlAMVlFWWFZgZkBAQEBSD9AMGKwMkAAwAMAmDIRAAAe/QA4VR9cEQAKICAgICAg/wBCSEZGS0I2MzAwMjI2/ABMMjBDTQogICAgICAgAM8=
modes: 1600x1200 1280x1024 1280x1024 1280x1024 1024x768 1024x768 1024x768
1024x768 832x624 800x600 800x600 800x600 800x600 800x600 640x480 640x480
640x480 640x480 640x480 720x400
Date: Tue Oct 22 19:48:51 2019
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/sdb1 ext4 1.8T 491G 1.3T 29% /home
tmpfs tmpfs 32G 927M 31G 3% /dev/shm
/dev/sdb1 ext4 1.8T 491G 1.3T 29% /home
InstallationDate: Installed on 2017-02-03 (991 days ago)
InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64 (20170125)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic
root=UUID=6ef42be7-d431-4d0d-bc57-79f7a96980ef ro
Snap.ChromeDriverVersion:
ERROR: ld.so: object 'libgtk3-nocsd.so.0' from LD_PRELOAD cannot be preloaded
(failed to map segment from shared object): ignored.
ChromeDriver 77.0.3865.120
(416d6d8013e9adb6dd33b0c12e7614ff403d1a94-refs/branch-heads/3865@{#884})
Snap.ChromiumVersion:
ERROR: ld.so: object 'libgtk3-nocsd.so.0' from LD_PRELOAD cannot be preloaded
(failed to map segment from shared object): ignored.
Chromium 77.0.3865.120 snap
SourcePackage: chromium-browser
UpgradeStatus: Upgraded to eoan on 2019-10-21 (0 days ago)
dmi.bios.date: 05/16/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3805
dmi.board.asset.tag: Default string
dmi.board.name: Z170 PRO GAMING
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr3805:bd05/16/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170PROGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
** Affects: chromium-browser
[Desktop-packages] [Bug 1338177] Re: BUG: soft lockup - CPU#0 stuck for 23s! [Xorg:1295]
Hi Christopher, Is there actually any point doing this? I've had so many experiences where I track down a bug in some detail, file it on Launchpad,, and then it takes a year or more (as in this case) before any developer might actually pay attention to the report - by which time the whole thing is obsolete, either fixed elsewhere, or still present but in newer releases. I often get the feeling that I am simply wasting my time filing bug reports, because, however helpful and detailed they are or try to be, they very rarely get attention beyond: "confirmed/new" "affects multiple users"... [time passes without a fix] "release unsupported" [still present] So it seems more useful to report issues directly upstream. Of course, I realise that developer time is valuable, which is why I'm happy to invest 5+ hours into bug reporting and further diagnosis. But it is just too unrewarding to keep investing time to no effect. Is it unreasonable to expect that if a bug is reported, it should either be closed/invalid, or fixed/deployed within a couple of months, ideally less? Richard -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1338177 Title: BUG: soft lockup - CPU#0 stuck for 23s! [Xorg:1295] Status in fglrx-installer package in Ubuntu: Incomplete Bug description: I've just installed Utopic, and my machine is really slow to boot. WORKAROUND: Use Radeon driver. ProblemType: KernelOops DistroRelease: Ubuntu 14.10 Package: linux-image-3.15.0-6-generic 3.15.0-6.11 [modified: boot/vmlinuz-3.15.0-6-generic] ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0 Uname: Linux 3.15.0-6-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.14.4-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: rjn2642 F pulseaudio /dev/snd/controlC2: rjn2642 F pulseaudio /dev/snd/controlC0: rjn2642 F pulseaudio /dev/snd/controlC1: rjn2642 F pulseaudio Date: Sun Jul 6 00:58:31 2014 DuplicateSignature: BUG: soft lockup - CPU#0 stuck for 23s! [Xorg:1295] RIP: 0010:location location ulReadMmRegisterUlongViaAddr+0xc/0x10 [fglrx] Failure: oops HibernationDevice: RESUME=UUID=dd46a6f0-bcb8-4e75-b77d-6158117027ac InstallationDate: Installed on 2014-07-05 (0 days ago) InstallationMedia: Kubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140703) IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.15.0-6-generic root=UUID=41c3bf4e-49c3-4546-aea6-30a91309679d ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-3ubuntu8 RfKill: SourcePackage: linux Title: BUG: soft lockup - CPU#0 stuck for 23s! [Xorg:1295] UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/21/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0703 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z68-V LX dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0703:bd10/21/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1338177/+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 1338177] Re: BUG: soft lockup - CPU#0 stuck for 23s! [Xorg:1295]
Hello. I'm currently running Wily on the same machine, under kernel: 4.1.0-3-generic #3-Ubuntu SMP Tue Jul 28 12:25:10 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux I'm using the Radeon driver from Xorg (Fglrx isn't even installed), and while the machine is perfectly usable, I still get these errors - the message below is from my dmesg: [81963.477554] compiz[16940]: segfault at 7f2012f642f0 ip 7f20104a61cb sp 7ffcd833e1f0 error 4 in libc-2.21.so[7f2010427000+1c] [81974.077423] [drm:atom_op_jump [radeon]] *ERROR* atombios stuck in loop for more than 5secs aborting [81974.077448] [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing C7E8 (len 62, WS 0, PS 0) @ 0xC804 [81979.088109] [drm:atom_op_jump [radeon]] *ERROR* atombios stuck in loop for more than 5secs aborting [81979.088119] [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing C7E8 (len 62, WS 0, PS 0) @ 0xC804 [81979.088126] [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing BE9C (len 1126, WS 0, PS 0) @ 0xBF2E [81984.114825] [drm:atom_op_jump [radeon]] *ERROR* atombios stuck in loop for more than 5secs aborting [81984.114835] [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing C7E8 (len 62, WS 0, PS 0) @ 0xC804 [81989.125508] [drm:atom_op_jump [radeon]] *ERROR* atombios stuck in loop for more than 5secs aborting [81989.125526] [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing C7E8 (len 62, WS 0, PS 0) @ 0xC804 [81989.125533] [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing BE9C (len 1126, WS 0, PS 0) @ 0xBF2E If you need anything more, let me know. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1338177 Title: BUG: soft lockup - CPU#0 stuck for 23s! [Xorg:1295] Status in fglrx-installer package in Ubuntu: Incomplete Bug description: I've just installed Utopic, and my machine is really slow to boot. WORKAROUND: Use Radeon driver. ProblemType: KernelOops DistroRelease: Ubuntu 14.10 Package: linux-image-3.15.0-6-generic 3.15.0-6.11 [modified: boot/vmlinuz-3.15.0-6-generic] ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0 Uname: Linux 3.15.0-6-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.14.4-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: rjn2642 F pulseaudio /dev/snd/controlC2: rjn2642 F pulseaudio /dev/snd/controlC0: rjn2642 F pulseaudio /dev/snd/controlC1: rjn2642 F pulseaudio Date: Sun Jul 6 00:58:31 2014 DuplicateSignature: BUG: soft lockup - CPU#0 stuck for 23s! [Xorg:1295] RIP: 0010:location location ulReadMmRegisterUlongViaAddr+0xc/0x10 [fglrx] Failure: oops HibernationDevice: RESUME=UUID=dd46a6f0-bcb8-4e75-b77d-6158117027ac InstallationDate: Installed on 2014-07-05 (0 days ago) InstallationMedia: Kubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140703) IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.15.0-6-generic root=UUID=41c3bf4e-49c3-4546-aea6-30a91309679d ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-3ubuntu8 RfKill: SourcePackage: linux Title: BUG: soft lockup - CPU#0 stuck for 23s! [Xorg:1295] UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/21/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0703 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z68-V LX dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0703:bd10/21/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1338177/+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 1464053] Re: ubuntu-bug is broken (only) within Mate, because of gvfs-open.
I just tested this again in my Ubuntu Mate system (Wily, fully updated as of today). Running the command gvfs-open http://www.bbc.co.uk; still results in the same problem - namely a new firefox window that is open at the homepage, not the URL required. The gvfs-open command does what it should when the running-desktop is KDE or Unity - but not when it is Mate. How else can I help debug this? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1464053 Title: ubuntu-bug is broken (only) within Mate, because of gvfs-open. Status in ubuntu-mate: Incomplete Status in apport package in Ubuntu: Invalid Status in gvfs package in Ubuntu: New Bug description: The ubuntu bug reporting system is rather badly broken, because when I run ubuntu-bug/apport-bug, it gathers data, then opens a new blank firefox window, but does not connect to launchpad! The root cause is this one: https://bugs.launchpad.net/ubuntu/+source/exo/+bug/1427144 which basically means that apport needs to invoke firefox with a different set of options. This should be trivial to fix, but I think it's rather important, especially given how hard it is to get a direct report into Launchpad, and all the redirects that emphasise using the ubuntu-bug tool: https://help.ubuntu.com/community/ReportingBugs (I'm reporting this from Ubuntu Wily, though I think I recall seeing it in Vivid) Apport version is: 2.17.3-0ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1464053/+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 1464053] Re: ubuntu-bug is broken (only) within Mate, because of gvfs-open.
** Also affects: gvfs (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1464053 Title: ubuntu-bug is broken (only) within Mate, because of gvfs-open. Status in apport package in Ubuntu: Incomplete Status in gvfs package in Ubuntu: New Bug description: The ubuntu bug reporting system is rather badly broken, because when I run ubuntu-bug/apport-bug, it gathers data, then opens a new blank firefox window, but does not connect to launchpad! The root cause is this one: https://bugs.launchpad.net/ubuntu/+source/exo/+bug/1427144 which basically means that apport needs to invoke firefox with a different set of options. This should be trivial to fix, but I think it's rather important, especially given how hard it is to get a direct report into Launchpad, and all the redirects that emphasise using the ubuntu-bug tool: https://help.ubuntu.com/community/ReportingBugs (I'm reporting this from Ubuntu Wily, though I think I recall seeing it in Vivid) Apport version is: 2.17.3-0ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1464053/+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 1425972] Re: Firefox no longer supports -remote parameter
This also breaks ubuntu-bug/apport-bug itself.
Report filed here: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1464053
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to emacs24 in Ubuntu.
https://bugs.launchpad.net/bugs/1425972
Title:
Firefox no longer supports -remote parameter
Status in GNU Emacs:
Unknown
Status in exo:
Fix Released
Status in The Mozilla Firefox Browser:
Fix Released
Status in Python:
New
Status in emacs24 package in Ubuntu:
Confirmed
Status in exo package in Ubuntu:
Fix Released
Status in firefox package in Ubuntu:
Fix Released
Status in emacs24 source package in Trusty:
Confirmed
Status in exo source package in Trusty:
Fix Released
Status in firefox source package in Trusty:
Fix Released
Status in emacs24 source package in Utopic:
Confirmed
Status in exo source package in Utopic:
In Progress
Status in firefox source package in Utopic:
Fix Released
Status in exo package in Debian:
New
Bug description:
[Impact]
As of Firefox version 36, the -remote commandline parameter was dropped.
This parameter is used in versions of exo prior to 0.10.3. Because of this,
opening any URLs via exo-open will cause a new firefox window to launch at the
home screen.
As reported, this affects the terminal, ubuntu-bug, xchat, and
numerous other applications.
[Test Case]
1. Set Firefox as the default web browser in Preferred Applications.
2. From a terminal, type the following:
exo-open http://www.xfce.org;
Expected: Firefox opens at http://www.xfce.org
Actual: Firefox opens at the home page.
[Regression Potential]
No regressions by this change. This fixes the application call to correctly
open URLs.
---
[Original Report]
When I click a link from an email it does not work any more.
Instead of opening the link in a new tab, Firefox opens a new empty
window and does not follow the link.
If I change the default browser for my desktop from Firefox to Chrome,
then Chrome can open the link fine.
I have started seeing this today since firefox was upgraded from v35
to 36.
My email client is Mozilla thunderbird at the latest stable version.
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: firefox 36.0+build2-0ubuntu0.14.10.4
ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5
Uname: Linux 3.16.0-31-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.14.7-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: dpottage 3729 F pulseaudio
BuildID: 20150224133805
Channel: Unavailable
CurrentDesktop: XFCE
Date: Thu Feb 26 14:30:41 2015
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IncompatibleExtensions:
English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
English (GB) Language Pack - langpack-en...@firefox.mozilla.org
Français Language Pack - langpack...@firefox.mozilla.org
Deutsch (DE) Language Pack - langpack...@firefox.mozilla.org
Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2013-07-02 (604 days ago)
InstallationMedia: Xubuntu 13.04 Raring Ringtail - Release amd64
(20130423.1)
IpRoute:
default via 192.168.1.254 dev eth0 proto static
192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.131 metric
1
MostRecentCrashID: bp-86a16931-63d2-435e-8324-421212140304
Plugins:
Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
LibreOffice Plug-in - /usr/lib/libreoffice/program/libnpsoplugin.so
(browser-plugin-libreoffice)
Java(TM) Plug-in 11.25.2 -
/usr/lib/jvm/java-8-oracle/jre/lib/amd64/libnpjp2.so
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=36.0/20150224133805 (In use)
RelatedPackageVersions: browser-plugin-libreoffice 1:4.3.3-0ubuntu1
RfKill:
0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
RunningIncompatibleAddons: True
SourcePackage: firefox
SubmittedCrashIDs: bp-86a16931-63d2-435e-8324-421212140304
UpgradeStatus: Upgraded to utopic on 2014-10-29 (119 days ago)
dmi.bios.date: 11/23/2012
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A08
dmi.board.name: 0XR1GT
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA08:bd11/23/2012:svnDellInc.:pnVostro270:pvr:rvnDellInc.:rn0XR1GT:rvrA00:cvnDellInc.:ct3:cvr:
dmi.product.name: Vostro 270
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/emacs/+bug/1425972/+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 1464053] [NEW] ubuntu-bug is itself broken
Public bug reported: The ubuntu bug reporting system is rather badly broken, because when I run ubuntu-bug/apport-bug, it gathers data, then opens a new blank firefox window, but does not connect to launchpad! The root cause is this one: https://bugs.launchpad.net/ubuntu/+source/exo/+bug/1427144 which basically means that apport needs to invoke firefox with a different set of options. This should be trivial to fix, but I think it's rather important, especially given how hard it is to get a direct report into Launchpad, and all the redirects that emphasise using the ubuntu-bug tool: https://help.ubuntu.com/community/ReportingBugs (I'm reporting this from Ubuntu Wily, though I think I recall seeing it in Vivid) Apport version is: 2.17.3-0ubuntu4 ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: irony -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1464053 Title: ubuntu-bug is itself broken Status in apport package in Ubuntu: New Bug description: The ubuntu bug reporting system is rather badly broken, because when I run ubuntu-bug/apport-bug, it gathers data, then opens a new blank firefox window, but does not connect to launchpad! The root cause is this one: https://bugs.launchpad.net/ubuntu/+source/exo/+bug/1427144 which basically means that apport needs to invoke firefox with a different set of options. This should be trivial to fix, but I think it's rather important, especially given how hard it is to get a direct report into Launchpad, and all the redirects that emphasise using the ubuntu-bug tool: https://help.ubuntu.com/community/ReportingBugs (I'm reporting this from Ubuntu Wily, though I think I recall seeing it in Vivid) Apport version is: 2.17.3-0ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1464053/+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 782049] Re: firefox tooltip timeout after ~2sec
See also: /etc/default/unclutter: the default (unhelpfully, imho) is that it is autostarted for every X session. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/782049 Title: firefox tooltip timeout after ~2sec Status in “firefox” package in Ubuntu: Confirmed Bug description: Binary package hint: firefox When you want to read a tooltip on a webpage (the title tag in an image) like on xkcd it is impossible because the tooltip disapears after ~2sec ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: firefox 4.0.1+build1+nobinonly-0ubuntu0.11.04.2 ProcVersionSignature: Ubuntu 2.6.38-9.43-generic 2.6.38.4 Uname: Linux 2.6.38-9-generic x86_64 Architecture: amd64 Date: Fri May 13 09:42:23 2011 FirefoxPackages: firefox 4.0.1+build1+nobinonly-0ubuntu0.11.04.2 flashplugin-installer 10.2.159.1ubuntu1 adobe-flashplugin N/A icedtea-plugin N/A InstallationMedia: Ubuntu 11.04 Natty Narwhal - Beta amd64 (20110413) ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/782049/+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 435831] Re: unclutter shouldn't be enabled by default
I agree, the default should be disabled. My rationale: 1. Most users wouldn't necessarily expect the program to be auto-start; rather, they would expect to add it to their own X-startup scripts if they want it. 2. Furthermore, it creates really weird symptoms for those who don't realise what's happening. For example, bug #782049, bug #606565 3. On a multi-user machine, unclutter is a useful tool to have present - but it shouldn't run for everyone. 4. The least-surprise principle: if you want it and it's not running, it's very easy to turn on; whereas if you don't want it, but don't know where to look, it's very hard to turn off. For example, I usually install unclutter, alongside wmctrl, and xmacro, as a standard convenience on systems that I administrate. I want it to be there when I need it, but I don't expect it to run until started. Also, the man page (man unclutter) does not mention the init-script, /etc/X11/Xsession.d/90unclutter nor does it mention /etc/default/unclutter, which makes this more difficult to discover. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unclutter in Ubuntu. https://bugs.launchpad.net/bugs/435831 Title: unclutter shouldn't be enabled by default Status in “unclutter” package in Ubuntu: Confirmed Bug description: Binary package hint: unclutter When you install unclutter it starts automatically every time you boot your computer. This is set in '/etc/default/unclutter'. It can be confusing for many users (it was for me). I believe the default should be changed so that the user has to enable it. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unclutter/+bug/435831/+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 1308125] Re: ERROR:browser_main_loop.cc(240)] Gdk: gdk_window_set_user_time called on non-toplevel
II also see this bug. It's definitely a problem! I suspect that the reason relatively few people are complaining is that (a) The problem is intermittent - the keys come and go, sometimes only a single keystroke is dropped. Sometimes it takes many seconds. (b) Nobody expects a bug of this type - and who would blame the combination of keyboard + browser + input-field. (c) Weirdly, the mouse still works, it's just the keyboard. (d) When the bug occurs, the browser used to report it is broken! Incidentally, I am submitting this bug by copy-pasting into Chrome: middle-click paste still works. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1308125 Title: ERROR:browser_main_loop.cc(240)] Gdk: gdk_window_set_user_time called on non-toplevel Status in “chromium-browser” package in Ubuntu: Confirmed Bug description: Can't input text in input fields, the browser shows an error on the console. It makes the browser unusable. This bug has already been reported here: https://code.google.com/p/chromium/issues/detail?id=360388 But since this was an update from the ubuntu repos, the relase date is almost here, this is an LTS release and the browser is one of the most used programs, I thought it might be worth creating the bug here as well. Maybe revert to version 33 until this is solve?. How to reproduce. An up to date Kubuntu 14.04. Launch cromium-browser, go to any web page with a text field and enter text. As soon as the keys are pressed errors appear in the console. The console output: chromium-browser [4870:4870:0415/173903:ERROR:browser_main_loop.cc(240)] Gdk: gdk_window_set_user_time called on non-toplevel [4870:4870:0415/173908:ERROR:browser_main_loop.cc(240)] Gdk: gdk_window_set_user_time called on non-toplevel [4870:4870:0415/173908:ERROR:browser_main_loop.cc(240)] Gdk: gdk_window_set_user_time called on non-toplevel [4870:4870:0415/173908:ERROR:browser_main_loop.cc(240)] Gdk: gdk_window_set_user_time called on non-toplevel [4870:4870:0415/173908:ERROR:browser_main_loop.cc(240)] Gdk: gdk_window_set_user_time called on non-toplevel [4870:4870:0415/173909:ERROR:browser_main_loop.cc(240)] Gdk: gdk_window_set_user_time called on non-toplevel [4870:4870:0415/173909:ERROR:browser_main_loop.cc(240)] Gdk: gdk_window_set_user_time called on non-toplevel [4870:4870:0415/173909:ERROR:browser_main_loop.cc(240)] Gdk: gdk_window_set_user_time called on non-toplevel [4870:4870:0415/173909:ERROR:browser_main_loop.cc(240)] Gdk: gdk_window_set_user_time called on non-toplevel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1308125/+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 1308125] Re: ERROR:browser_main_loop.cc(240)] Gdk: gdk_window_set_user_time called on non-toplevel
Sorry, forgot to mention, it affects a clean default install of both Saucy and Utopic (as of 19/Jul/2014) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1308125 Title: ERROR:browser_main_loop.cc(240)] Gdk: gdk_window_set_user_time called on non-toplevel Status in “chromium-browser” package in Ubuntu: Confirmed Bug description: Can't input text in input fields, the browser shows an error on the console. It makes the browser unusable. This bug has already been reported here: https://code.google.com/p/chromium/issues/detail?id=360388 But since this was an update from the ubuntu repos, the relase date is almost here, this is an LTS release and the browser is one of the most used programs, I thought it might be worth creating the bug here as well. Maybe revert to version 33 until this is solve?. How to reproduce. An up to date Kubuntu 14.04. Launch cromium-browser, go to any web page with a text field and enter text. As soon as the keys are pressed errors appear in the console. The console output: chromium-browser [4870:4870:0415/173903:ERROR:browser_main_loop.cc(240)] Gdk: gdk_window_set_user_time called on non-toplevel [4870:4870:0415/173908:ERROR:browser_main_loop.cc(240)] Gdk: gdk_window_set_user_time called on non-toplevel [4870:4870:0415/173908:ERROR:browser_main_loop.cc(240)] Gdk: gdk_window_set_user_time called on non-toplevel [4870:4870:0415/173908:ERROR:browser_main_loop.cc(240)] Gdk: gdk_window_set_user_time called on non-toplevel [4870:4870:0415/173908:ERROR:browser_main_loop.cc(240)] Gdk: gdk_window_set_user_time called on non-toplevel [4870:4870:0415/173909:ERROR:browser_main_loop.cc(240)] Gdk: gdk_window_set_user_time called on non-toplevel [4870:4870:0415/173909:ERROR:browser_main_loop.cc(240)] Gdk: gdk_window_set_user_time called on non-toplevel [4870:4870:0415/173909:ERROR:browser_main_loop.cc(240)] Gdk: gdk_window_set_user_time called on non-toplevel [4870:4870:0415/173909:ERROR:browser_main_loop.cc(240)] Gdk: gdk_window_set_user_time called on non-toplevel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1308125/+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 1215449] Re: triple monitor support not working on HD 4600
Re #19: I'm using kernel 3.11.0-8-generic and the Intel Xorg driver 2:2.99.903+git20131001.c724098f-0ubuntu0sarvatt2 I installed saucy alpha a few months ago, and then the xorg-edgers PPA. That works fine, though I haven't updated it in about4 weeks. The trick for me was to use one DVI/VGA adapter, so that only 2 of the monitors have a digital connection. HTH. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1215449 Title: triple monitor support not working on HD 4600 Status in X.org xf86-video-intel: Confirmed Status in “xserver-xorg-video-intel” package in Ubuntu: New Bug description: I have a Gigabyte GA-H87N-wifi motherboard, which explicitly supports 3 monitors at the same time from the motherboards' onboard graphics (2x HDMI, 1x DVI). The CPU is an Intel 4570S with HD4600 graphics (also supporting 3 heads at the same time). However, I can only get 2 monitors (any 2, but not all 3) working. All monitors are identical 1600x1200 (NEC LCD2070NX). The KDE systemsettings GUI helpfully shows icons for all 3 monitors, but one is always greyed out, and attempting to enable it emits Failed to set mode: Invalid argument in Xorg.0.log. Xrandr compians Configure crtc 2 failed. However, it's clear that the graphics hardware can handle 3 outputs, since it refers to pipe 0, pipe 1 and pipe 2 in the logs. Google doesn't show anything very helpful, except to warn that in older graphics hardware (definitely not this motherboard) there may be more output connectors than graphics pipelines, and that in the HD4600 there are only 2x PLL, so 2 of the monitors need to be identically clocked (as they are). This also affects the xorg-edgers packages, as of yesterday, so it seems to be an upstream problem. Xorg.0.log attached. Thanks for your help - please let me know if there's anything I can do to assist in debugging. To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1215449/+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 1242180] Re: saucy regression - three monitors no longer work
FYI, this is an easy way you can test the latest Xorg nightlies: http://www.ubuntuupdates.org/ppa/xorg-edgers -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1242180 Title: saucy regression - three monitors no longer work Status in “xserver-xorg-video-intel” package in Ubuntu: New Bug description: I've just upgraded from raring. There I had 3 monitors attached to my Intel HD Graphics 4000 (i7 3770 cpu) where it all works perfectly. (Two monitors are identical flanking my centre displayport monitor.) In saucy I can get any two monitors working, and any attempt to get all 3 working results in an error about setting crtc with a different number. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xserver-xorg-video-intel 2:2.99.904-0ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Sat Oct 19 14:28:59 2013 MarkForUpload: True SourcePackage: xserver-xorg-video-intel UpgradeStatus: Upgraded to saucy on 2013-10-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1242180/+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 1215449] Re: triple monitor support not working on HD 4600
Filed upstream here: https://bugs.freedesktop.org/show_bug.cgi?id=68485 This feature isn't yet implemented in the Intel Driver. ** Bug watch added: freedesktop.org Bugzilla #68485 https://bugs.freedesktop.org/show_bug.cgi?id=68485 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1215449 Title: triple monitor support not working on HD 4600 Status in “xserver-xorg-video-intel” package in Ubuntu: New Bug description: I have a Gigabyte GA-H87N-wifi motherboard, which explicitly supports 3 monitors at the same time from the motherboards' onboard graphics (2x HDMI, 1x DVI). The CPU is an Intel 4570S with HD4600 graphics (also supporting 3 heads at the same time). However, I can only get 2 monitors (any 2, but not all 3) working. All monitors are identical 1600x1200 (NEC LCD2070NX). The KDE systemsettings GUI helpfully shows icons for all 3 monitors, but one is always greyed out, and attempting to enable it emits Failed to set mode: Invalid argument in Xorg.0.log. Xrandr compians Configure crtc 2 failed. However, it's clear that the graphics hardware can handle 3 outputs, since it refers to pipe 0, pipe 1 and pipe 2 in the logs. Google doesn't show anything very helpful, except to warn that in older graphics hardware (definitely not this motherboard) there may be more output connectors than graphics pipelines, and that in the HD4600 there are only 2x PLL, so 2 of the monitors need to be identically clocked (as they are). This also affects the xorg-edgers packages, as of yesterday, so it seems to be an upstream problem. Xorg.0.log attached. Thanks for your help - please let me know if there's anything I can do to assist in debugging. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1215449/+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 1215449] [NEW] triple monitor support not working on HD 4600
Public bug reported: I have a Gigabyte GA-H87N-wifi motherboard, which explicitly supports 3 monitors at the same time from the motherboards' onboard graphics (2x HDMI, 1x DVI). The CPU is an Intel 4570S with HD4600 graphics (also supporting 3 heads at the same time). However, I can only get 2 monitors (any 2, but not all 3) working. All monitors are identical 1600x1200 (NEC LCD2070NX). The KDE systemsettings GUI helpfully shows icons for all 3 monitors, but one is always greyed out, and attempting to enable it emits Failed to set mode: Invalid argument in Xorg.0.log. Xrandr compians Configure crtc 2 failed. However, it's clear that the graphics hardware can handle 3 outputs, since it refers to pipe 0, pipe 1 and pipe 2 in the logs. Google doesn't show anything very helpful, except to warn that in older graphics hardware (definitely not this motherboard) there may be more output connectors than graphics pipelines, and that in the HD4600 there are only 2x PLL, so 2 of the monitors need to be identically clocked (as they are). This also affects the xorg-edgers packages, as of yesterday, so it seems to be an upstream problem. Xorg.0.log attached. Thanks for your help - please let me know if there's anything I can do to assist in debugging. ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Attachment added: Xorg.0.log https://bugs.launchpad.net/bugs/1215449/+attachment/3782502/+files/Xorg.0.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1215449 Title: triple monitor support not working on HD 4600 Status in “xserver-xorg-video-intel” package in Ubuntu: New Bug description: I have a Gigabyte GA-H87N-wifi motherboard, which explicitly supports 3 monitors at the same time from the motherboards' onboard graphics (2x HDMI, 1x DVI). The CPU is an Intel 4570S with HD4600 graphics (also supporting 3 heads at the same time). However, I can only get 2 monitors (any 2, but not all 3) working. All monitors are identical 1600x1200 (NEC LCD2070NX). The KDE systemsettings GUI helpfully shows icons for all 3 monitors, but one is always greyed out, and attempting to enable it emits Failed to set mode: Invalid argument in Xorg.0.log. Xrandr compians Configure crtc 2 failed. However, it's clear that the graphics hardware can handle 3 outputs, since it refers to pipe 0, pipe 1 and pipe 2 in the logs. Google doesn't show anything very helpful, except to warn that in older graphics hardware (definitely not this motherboard) there may be more output connectors than graphics pipelines, and that in the HD4600 there are only 2x PLL, so 2 of the monitors need to be identically clocked (as they are). This also affects the xorg-edgers packages, as of yesterday, so it seems to be an upstream problem. Xorg.0.log attached. Thanks for your help - please let me know if there's anything I can do to assist in debugging. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1215449/+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 932177] Re: XFCE (and other non-GNOME) desktops do not initialise gnome-keyring correctly / WARNING: gnome-keyring:: couldn't connect to PKCS11
I'd like to confirm this bug for KUbuntu Raring Beta-final. Please fix it; it's most definitely not invalid. To reproduce: 1. Install both sets of desktops: apt-get install ubuntu-desktop kubuntu-desktop 2. Log into a KDE session. 3. launch an application from the terminal eg libre-office. 4. Observe that it complains about WARNING: gnome-keyring:: couldn't connect to PKCS11 To solve it: 1. Edit the file: /etc/xdg/autostart/gnome-keyring-pkcs11.desktop 2. Append KDE to the line: OnlyShowIn=GNOME;Unity;MATE;KDE; or, uninstall gnome-keyring entirely. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/932177 Title: XFCE (and other non-GNOME) desktops do not initialise gnome-keyring correctly / WARNING: gnome-keyring:: couldn't connect to PKCS11 Status in GNOME keyring services: Fix Released Status in Xfce4 session manager: Unknown Status in “gnome-keyring” package in Ubuntu: Invalid Status in “kde-workspace” package in Ubuntu: Confirmed Status in “xfce4-session” package in Ubuntu: Fix Released Status in “gnome-keyring” package in Debian: New Status in “gnome-keyring” package in Fedora: Unknown Status in “gnome-keyring” package in openSUSE: Fix Released Bug description: precise + fluxbox (without gnome-settings-daemon) Postler when sending a message writes: Failed to send a message WARNING: gnome-keyring:: couldn't connect to: /tmp/keyring-rof1VB/pkcs11: No such file or directory In gnome-system-monitor: /usr/bin/gnome-keyring-demon --start --foreground --components=secrets /usr/bin/gnome-keyring-demon --daemonize --login with manual start this: OK /usr/bin/gnome-keyring-daemon --start --components=pkcs11 Is it possible to add a string key '--components=pkcs11', so that the gnome-system-monitor was: /usr/bin/gnome-keyring-demon --start --foreground --components=secrets --components=pkcs11 thanks in advance... ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-keyring 3.2.2-2ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-15.24-generic 3.2.5 Uname: Linux 3.2.0-15-generic x86_64 ApportVersion: 1.91-0ubuntu1 Architecture: amd64 Date: Tue Feb 14 17:47:35 2012 InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100429) ProcEnviron: PATH=(custom, no user) LANG=ru_UA.UTF-8 SHELL=/bin/bash SourcePackage: gnome-keyring UpgradeStatus: Upgraded to precise on 2012-02-10 (3 days ago) mtime.conffile..etc.xdg.autostart.gnome.keyring.gpg.desktop: 2012-02-14T14:17:23.632015 mtime.conffile..etc.xdg.autostart.gnome.keyring.pkcs11.desktop: 2012-02-14T14:17:23.632015 mtime.conffile..etc.xdg.autostart.gnome.keyring.secrets.desktop: 2012-02-14T14:17:23.632015 mtime.conffile..etc.xdg.autostart.gnome.keyring.ssh.desktop: 2012-02-14T14:17:23.636015 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-keyring/+bug/932177/+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
