[Desktop-packages] [Bug 1994453] [NEW] Firefox Snap cannot be installed in an LXC Container
Public bug reported: $ sudo snap install firefox error: cannot perform the following tasks: - Run hook connect-plug-host-hunspell of snap "firefox" (run hook "connect-plug-host-hunspell": - update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/cups/doc-root /usr/share/cups/doc-root none bind,ro 0 0): cannot create directory "/usr/share/cups/doc-root": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/gimp/2.0/help /usr/share/gimp/2.0/help none bind,ro 0 0): cannot create directory "/usr/share/gimp/2.0": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/libreoffice/help /usr/share/libreoffice/help none bind,ro 0 0): cannot create directory "/usr/share/libreoffice/help": permission denied error: error running snapctl: cannot start mount unit: systemctl command [start var-snap-firefox-common-host\x2dhunspell.mount] failed with exit status 1: A dependency job for var-snap-firefox-common-host\x2dhunspell.mount failed. See 'journalctl -xe' for details. -) This makes it very difficult to have LXC containers with a GUI (used via VNC), as a web browser is essential. Workaround: - Add the Mozillateam PPA (https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu) - Create /etc/apt/preferences.d/mozilla-firefox with: Package: firefox* Pin: release o=LP-PPA-mozillateam Pin-Priority: 1001 - sudo apt install firefox ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Oct 26 14:16:04 2022 InstallationDate: Installed on 2020-11-02 (722 days ago) InstallationMedia: Ubuntu-Server 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Snap.Changes: no changes found SourcePackage: firefox UpgradeStatus: Upgraded to jammy on 2022-10-03 (22 days ago) ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- 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/1994453 Title: Firefox Snap cannot be installed in an LXC Container Status in firefox package in Ubuntu: New Bug description: $ sudo snap install firefox error: cannot perform the following tasks: - Run hook connect-plug-host-hunspell of snap "firefox" (run hook "connect-plug-host-hunspell": - update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/cups/doc-root /usr/share/cups/doc-root none bind,ro 0 0): cannot create directory "/usr/share/cups/doc-root": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/gimp/2.0/help /usr/share/gimp/2.0/help none bind,ro 0 0): cannot create directory "/usr/share/gimp/2.0": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/libreoffice/help /usr/share/libreoffice/help none bind,ro 0 0): cannot create directory "/usr/share/libreoffice/help": permission denied error: error running snapctl: cannot start mount unit: systemctl command [start var-snap-firefox-common-host\x2dhunspell.mount] failed with exit status 1: A dependency job for var-snap-firefox-common-host\x2dhunspell.mount failed. See 'journalctl -xe' for details. -) This makes it very difficult to have LXC containers with a GUI (used via VNC), as a web browser is essential. Workaround: - Add the Mozillateam PPA (https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu) - Create /etc/apt/preferences.d/mozilla-firefox with: Package: firefox* Pin: release o=LP-PPA-mozillateam Pin-Priority: 1001 - sudo apt install firefox ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Oct 26 14:16:04 2022 InstallationDate: Installed on 2020-11-02 (722 days ago) InstallationMedia: Ubuntu-Server 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Snap.Changes: no changes found SourcePackage: firefox UpgradeStatus: Upgraded to jammy on 2022-10-03 (22 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1994453/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to
[Desktop-packages] [Bug 1806514] Re: Cannot use PyUno connector with Libreoffice snap
The second error message is when specifying the exact path in the script like
this:
lo_proc =
subprocess.Popen(shlex.split("/snap/libreoffice/current/lib/libreoffice/program/soffice
--accept=\"socket,host=localhost,port=2002;urp;\" --norestore --nologo
--nodefault"))
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1806514
Title:
Cannot use PyUno connector with Libreoffice snap
Status in libreoffice package in Ubuntu:
New
Bug description:
It's not possible to use pyoo, which uses the Uno connector to
Libreoffice, on a machine where the Libreoffice Snap is installed. The
pyoo/Uno connector works fine with the libreoffice Apt packages.
To reproduce run this script:
#!/usr/bin/env python3
import pyoo
import subprocess
import time
import shlex
# PyOO needs a running Libreoffice process to do its work
lo_proc = subprocess.Popen(shlex.split("soffice
--accept=\"socket,host=localhost,port=2002;urp;\" --norestore --nologo
--nodefault"))
time.sleep(3) # give Libreoffice time to actually start before trying to
connect to it
lo_instance = pyoo.Desktop('localhost', 2002)
lo_instance.create_spreadsheet()
Expected results (seen with the Libreoffice DEB-packages from Ubuntu):
A new Calc window opens up showing a spreadsheet
Actual results:
$ ./test.py
Traceback (most recent call last):
File "/usr/local/lib/python3.6/dist-packages/pyoo.py", line 1833, in
_get_remote_context
return resolver.resolve(url)
uno.NoConnectException: Connector : couldn't connect to socket (Success)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "./test.py", line 10, in
lo_instance = pyoo.Desktop('localhost', 2002)
File "/usr/local/lib/python3.6/dist-packages/pyoo.py", line 1853, in
__init__
self.remote_context = _get_remote_context(resolver, url)
File "/usr/local/lib/python3.6/dist-packages/pyoo.py", line 1835, in
_get_remote_context
raise IOError(resolver, url)
OSError: [Errno pyuno object
(com.sun.star.uno.XInterface)0x1ff9450{implementationName=com.sun.star.comp.bridge.UnoUrlResolver,
supportedServices={com.sun.star.bridge.UnoUrlResolver},
supportedInterfaces={com.sun.star.lang.XServiceInfo,com.sun.star.bridge.XUnoUrlResolver,com.sun.star.lang.XTypeProvider,com.sun.star.uno.XWeak}}]
uno:socket,host=localhost,port=2002;urp;StarOffice.ComponentContext
Actual results if you specify the path to the soffice binary:
lo_proc = subprocess.Popen(shlex.split("soffice
--accept=\"socket,host=localhost,port=2002;urp;\" --norestore --nologo
--nodefault"))
$ ./test.py
/snap/libreoffice/90/lib/libreoffice/program/soffice.bin: error while loading
shared libraries: libicuuc.so.55: cannot open shared object file: No such file
or directory
Traceback (most recent call last):
File "/usr/local/lib/python3.6/dist-packages/pyoo.py", line 1833, in
_get_remote_context
return resolver.resolve(url)
uno.NoConnectException: Connector : couldn't connect to socket (Success)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "./test.py", line 10, in
lo_instance = pyoo.Desktop('localhost', 2002)
File "/usr/local/lib/python3.6/dist-packages/pyoo.py", line 1853, in
__init__
self.remote_context = _get_remote_context(resolver, url)
File "/usr/local/lib/python3.6/dist-packages/pyoo.py", line 1835, in
_get_remote_context
raise IOError(resolver, url)
OSError: [Errno pyuno object
(com.sun.star.uno.XInterface)0x1b11450{implementationName=com.sun.star.comp.bridge.UnoUrlResolver,
supportedServices={com.sun.star.bridge.UnoUrlResolver},
supportedInterfaces={com.sun.star.lang.XServiceInfo,com.sun.star.bridge.XUnoUrlResolver,com.sun.star.lang.XTypeProvider,com.sun.star.uno.XWeak}}]
uno:socket,host=localhost,port=2002;urp;StarOffice.ComponentContext
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1806514/+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 1806514] [NEW] Cannot use PyUno connector with Libreoffice snap
Public bug reported:
It's not possible to use pyoo, which uses the Uno connector to
Libreoffice, on a machine where the Libreoffice Snap is installed. The
pyoo/Uno connector works fine with the libreoffice Apt packages.
To reproduce run this script:
#!/usr/bin/env python3
import pyoo
import subprocess
import time
import shlex
# PyOO needs a running Libreoffice process to do its work
lo_proc = subprocess.Popen(shlex.split("soffice
--accept=\"socket,host=localhost,port=2002;urp;\" --norestore --nologo
--nodefault"))
time.sleep(3) # give Libreoffice time to actually start before trying to
connect to it
lo_instance = pyoo.Desktop('localhost', 2002)
lo_instance.create_spreadsheet()
Expected results (seen with the Libreoffice DEB-packages from Ubuntu): A
new Calc window opens up showing a spreadsheet
Actual results:
$ ./test.py
Traceback (most recent call last):
File "/usr/local/lib/python3.6/dist-packages/pyoo.py", line 1833, in
_get_remote_context
return resolver.resolve(url)
uno.NoConnectException: Connector : couldn't connect to socket (Success)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "./test.py", line 10, in
lo_instance = pyoo.Desktop('localhost', 2002)
File "/usr/local/lib/python3.6/dist-packages/pyoo.py", line 1853, in __init__
self.remote_context = _get_remote_context(resolver, url)
File "/usr/local/lib/python3.6/dist-packages/pyoo.py", line 1835, in
_get_remote_context
raise IOError(resolver, url)
OSError: [Errno pyuno object
(com.sun.star.uno.XInterface)0x1ff9450{implementationName=com.sun.star.comp.bridge.UnoUrlResolver,
supportedServices={com.sun.star.bridge.UnoUrlResolver},
supportedInterfaces={com.sun.star.lang.XServiceInfo,com.sun.star.bridge.XUnoUrlResolver,com.sun.star.lang.XTypeProvider,com.sun.star.uno.XWeak}}]
uno:socket,host=localhost,port=2002;urp;StarOffice.ComponentContext
Actual results if you specify the path to the soffice binary:
lo_proc = subprocess.Popen(shlex.split("soffice
--accept=\"socket,host=localhost,port=2002;urp;\" --norestore --nologo
--nodefault"))
$ ./test.py
/snap/libreoffice/90/lib/libreoffice/program/soffice.bin: error while loading
shared libraries: libicuuc.so.55: cannot open shared object file: No such file
or directory
Traceback (most recent call last):
File "/usr/local/lib/python3.6/dist-packages/pyoo.py", line 1833, in
_get_remote_context
return resolver.resolve(url)
uno.NoConnectException: Connector : couldn't connect to socket (Success)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "./test.py", line 10, in
lo_instance = pyoo.Desktop('localhost', 2002)
File "/usr/local/lib/python3.6/dist-packages/pyoo.py", line 1853, in __init__
self.remote_context = _get_remote_context(resolver, url)
File "/usr/local/lib/python3.6/dist-packages/pyoo.py", line 1835, in
_get_remote_context
raise IOError(resolver, url)
OSError: [Errno pyuno object
(com.sun.star.uno.XInterface)0x1b11450{implementationName=com.sun.star.comp.bridge.UnoUrlResolver,
supportedServices={com.sun.star.bridge.UnoUrlResolver},
supportedInterfaces={com.sun.star.lang.XServiceInfo,com.sun.star.bridge.XUnoUrlResolver,com.sun.star.lang.XTypeProvider,com.sun.star.uno.XWeak}}]
uno:socket,host=localhost,port=2002;urp;StarOffice.ComponentContext
** Affects: libreoffice (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1806514
Title:
Cannot use PyUno connector with Libreoffice snap
Status in libreoffice package in Ubuntu:
New
Bug description:
It's not possible to use pyoo, which uses the Uno connector to
Libreoffice, on a machine where the Libreoffice Snap is installed. The
pyoo/Uno connector works fine with the libreoffice Apt packages.
To reproduce run this script:
#!/usr/bin/env python3
import pyoo
import subprocess
import time
import shlex
# PyOO needs a running Libreoffice process to do its work
lo_proc = subprocess.Popen(shlex.split("soffice
--accept=\"socket,host=localhost,port=2002;urp;\" --norestore --nologo
--nodefault"))
time.sleep(3) # give Libreoffice time to actually start before trying to
connect to it
lo_instance = pyoo.Desktop('localhost', 2002)
lo_instance.create_spreadsheet()
Expected results (seen with the Libreoffice DEB-packages from Ubuntu):
A new Calc window opens up showing a spreadsheet
Actual results:
$ ./test.py
Traceback (most recent call last):
File "/usr/local/lib/python3.6/dist-packages/pyoo.py", line 1833, in
_get_remote_context
return resolver.resolve(url)
uno.NoConnectException: Connector : couldn't connect to socket (Success)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
Fi
[Desktop-packages] [Bug 1748839] Re: Problem to connect to WPA2/PEAP WIFI - gnome-shell
Fixed for me, I didn't do anything different or change anything, I guess one of the Ubuntu updates must've fixed it -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1748839 Title: Problem to connect to WPA2/PEAP WIFI - gnome-shell Status in network-manager package in Ubuntu: Confirmed Bug description: This problem is also happened on my desktop. After upgrading OS from Ubuntu 16.04 to Ubuntu 18.04.1 LTS, my PC could not connect and authenticate on WiFi with WPA2/PEAP/MSCHAPv2/no CA certificate/true username and password. I tried to solve the problem following URL link; however, it could not help me also. https://askubuntu.com/questions/279762/how-to-connect-to-wpa2-peap-mschapv2-enterprise-wifi-networks-that-dont-use-a-c My PC is HP Compaq Pro 4300, CPU: Intel® Core™ i3-3220 CPU @ 3.30GHz × 4, OS: Ubuntu 18.04.1 (64-bit). root@joe-UBTPC:/root # lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller (rev 09) 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09) 00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04) 00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05) 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05) 00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5) 00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b5) 00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 (rev b5) 00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b5) 00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 5 (rev b5) 00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 6 (rev b5) 00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05) 00:1f.0 ISA bridge: Intel Corporation H61 Express Chipset Family LPC Controller (rev 05) 00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family SATA AHCI Controller (rev 05) 00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 05) 03:00.0 Network controller: Ralink corp. RT5392 PCIe Wireless Network Adapter 06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 07) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1748839/+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 1721537] Re: No sound from headphone jack on xps13 9350 after ubuntu 17.10 dist-upgrade
I found this worked around the problem (Dell XPS 9360): Open alsamixer, enable sound on 'Headphone' (next to 'Master'). If there's a hissing/popping sound in the background but sound at 0 on 'Headphone Mic Boost' -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1721537 Title: No sound from headphone jack on xps13 9350 after ubuntu 17.10 dist- upgrade Status in alsa-driver package in Ubuntu: Confirmed Bug description: I just upgraded from 17.04 to 17.10 on my Dell XPS13 9350. Ever since my headphone jack doesn't output anything. The internal speakers are still working fine, the speakers I connect to the laptop too (tested with my phone). The system does recognize the speakers being connected, since I get the Headpones | Headset | Microphone popup and I can also test left/right speakers in Sound. However, no audio is coming through. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rienheuver 1426 F pulseaudio CurrentDesktop: GNOME Date: Thu Oct 5 14:41:11 2017 InstallationDate: Installed on 2016-11-22 (316 days ago) InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 (20161012.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Front Symptom_Type: No sound at all Title: [XPS 13 9350, Realtek ALC3246, Black Headphone Out, Front] No sound at all UpgradeStatus: Upgraded to artful on 2017-10-05 (0 days ago) dmi.bios.date: 12/18/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.9 dmi.board.name: 07TYC2 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.9:bd12/18/2015:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1721537/+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 969489] Re: lightdm tries (and fails) to start too early?
I run Ubuntu 14.04 and the workaround in #127 seems to have fixed it for me, thanks Ciprian. The fact that this is still happening on Ubuntu 14.04 is pretty shocking - I know LightDM and Upstart are effectively deprecated in favour of SDDM and systemd in the newer versions, but since this is such a high- impact bug affecting so many users it really should be fixed in the LTS versions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/969489 Title: lightdm tries (and fails) to start too early? Status in upstart : Confirmed Status in lightdm package in Ubuntu: Triaged Bug description: Sometimes lightdm comes up fine. Other times it appears to fail. x-0.log shows it tried to load 'nv' (rather than 'nvidia' which is what actually exists). When I then log into console and 'start lightdm', it comes up fine (on :1). I've not had it come up ok today, so I don't know if, when it comes up fine, it starts on :0. No idea if the lightdm.conf needs a change to 'start on'clause, or if this is just a case of a bad shipped config file (for module 'nv'). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: lightdm 1.1.9-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0-0ubuntu1 Architecture: amd64 Date: Fri Mar 30 13:40:27 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120323) ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/969489/+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 1397517] [NEW] Unity Screen Brightness Settings not Preserved on Reboot
Public bug reported: Whenever Unity starts it sets the screen brightness to maximum, even when the laptop is on battery. Lowering the screen brightness doesn't persist across reboots. To reproduce: 1. Start laptop (in this case a Lenovo Yoga 2 Pro) in battery mode (i.e. disconnected from the AC adaptor) 2. Unity will start in maximum brightness. Lower brightness using keyboard brightness keys. 3. Shutdown laptop and start it back up again (still with the AC adapter disconnected) Expected result: The screen brightness settings should be preserved across reboots Actual result: After each new start Unity sets the screen brightness to maximum, meaning the user has to remember to manually reduce it or the battery will be quickly used up ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.3+14.04.20140826-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10 Uname: Linux 3.13.0-40-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,imgpng,mousepoll,vpswitch,unitymtgrabhandles,gnomecompat,regex,move,grid,place,wall,animation,snap,resize,fade,session,expo,workarounds,scale,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Nov 29 11:59:31 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3978] InstallationDate: Installed on 2014-09-16 (73 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: LENOVO 20266 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-40-generic.efi.signed root=/dev/mapper/MainVG-root ro video.use_native_backlight=1 quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN35WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Yoga2 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 Pro dmi.modalias: dmi:bvnLENOVO:bvr76CN35WW:bd03/25/2014:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro: dmi.product.name: 20266 dmi.product.version: Lenovo Yoga 2 Pro dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Fri Nov 28 23:10:38 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16970 vendor SDC xserver.version: 2:1.15.1-0ubuntu2.1 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 third-party-packages trusty ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1397517 Title: Unity Screen Brightness Settings not Preserved on Reboot Status in unity package in Ubuntu: New Bug description: Whenever Unity starts it sets the screen brightness to maximum, even when the laptop is on battery. Lowering the screen brightness doesn't persist across reboots. To reproduce: 1. Start laptop (in this case a Lenovo Yoga 2 Pro) in battery mode (i.e. disconnected from the AC adaptor) 2. Unity will start in maximum brightness. Lower brightness using keyboard brightness keys. 3. Shutdown laptop and start it back up again (still with the AC adapter disconnected) Expected result: The screen brightness settings should be preserved across reboots Actual result: After each new start Unity sets the screen brightness to maximum, meaning the user has to remember to manually reduce it or the battery will be quickly used up ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.3+14.04.20140826-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10 Una
[Desktop-packages] [Bug 1375028] Re: onboard loses the focus when attempting to type in Unity Dash
That's strange, I just tried to reproduce the problem but couldn't. The original problem was that Dash was taking the focus away from onboard, although onboard was still open and visible under Dash. But I can't reproduce this anymore - maybe a recent change in Unity has done something? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to onboard in Ubuntu. https://bugs.launchpad.net/bugs/1375028 Title: onboard loses the focus when attempting to type in Unity Dash Status in Onboard on-screen keyboard: Incomplete Status in “onboard” package in Ubuntu: New Bug description: It's impossible to use Onboard onscreen keyboard to type in the Unity Dash search box unless onboard is set to 'Force Window on Top' in the Onboard preferences. Setting this shouldn't be necessary as onboard should automatically pop-up when the user selects any object that needs text entry. How to reproduce: 1. Start onboard on a computer with a touchscreen with the onboard setting 'Force Window on Top' disabled 2. Touch the Unity 'search your computer and online sources' to open Dash 3. Touch the 'Search your computer and online sources' search field to begin typing Result: Dash takes the focus away from onboard, meaning it's impossible to type in the Dash search field Expected result: I should be able to use onboard to type in the Dash search field, without needing a physical keyboard or other workarounds Workarounds: In Onboard preferences set 'Force Window on Top' Use a physical keyboard (defeats the purpose of Unity as a touch interface) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: onboard 1.0.0-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CurrentDesktop: Unity Date: Sun Sep 28 19:56:37 2014 InstallationDate: Installed on 2014-09-16 (11 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: onboard UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/onboard/+bug/1375028/+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 1375028] Re: onboard loses the focus when attempting to type in Unity Dash
I don't think I changed the 'Force window on top' setting before I used onboard for the first time, but I can't be sure. Maybe there should be a warning pop-up when disabling this option? I guess if there's no other solution with the way Dash works then there's nothing to do. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to onboard in Ubuntu. https://bugs.launchpad.net/bugs/1375028 Title: onboard loses the focus when attempting to type in Unity Dash Status in Onboard on-screen keyboard: Incomplete Status in “onboard” package in Ubuntu: Incomplete Bug description: It's impossible to use Onboard onscreen keyboard to type in the Unity Dash search box unless onboard is set to 'Force Window on Top' in the Onboard preferences. Setting this shouldn't be necessary as onboard should automatically pop-up when the user selects any object that needs text entry. How to reproduce: 1. Start onboard on a computer with a touchscreen with the onboard setting 'Force Window on Top' disabled 2. Touch the Unity 'search your computer and online sources' to open Dash 3. Touch the 'Search your computer and online sources' search field to begin typing Result: Dash takes the focus away from onboard, meaning it's impossible to type in the Dash search field Expected result: I should be able to use onboard to type in the Dash search field, without needing a physical keyboard or other workarounds Workarounds: In Onboard preferences set 'Force Window on Top' Use a physical keyboard (defeats the purpose of Unity as a touch interface) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: onboard 1.0.0-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CurrentDesktop: Unity Date: Sun Sep 28 19:56:37 2014 InstallationDate: Installed on 2014-09-16 (11 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: onboard UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/onboard/+bug/1375028/+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 1375223] [NEW] unity-greeter ignores lightdm display resolution and DPI settings
Public bug reported: I have a laptop with a very high-res screen (Lenovo Yoga 2 Pro with 3200x1600 screen). To make this more usable I set the display to a resolution of 1920x1080 and a higher DPI of 120x120 in the LightDM settings: xserver-command=X -dpi 120 display-setup-script=xrandr --output eDP1 --mode 1920x1080 --primary These settings are ignored or overridden by the unity-greeter. Other greeters, e.g. lightdm-kde-greeter, correctly apply these settings. Steps to reproduce: 1. Change your DPI and resolution settings to be something other than the default for your laptop's display in /etc/lightdm/lightdm.conf, using xserver-command and display-setup-script as above 2. Ensure lightdm is set to use the unity-greeter 2. Restart lightdm or reboot the laptop Expected results: The lightdm Unity login screen is shown with the resolution and DPI you set using xserver-command and display-setup-script in lightdm.conf Actual results: The settings are ignored/overridden and lightdm shows the login screen using the default resolution and DPI for your device Workaround: Use lightdm-kde-greeter: sudo apt-get install lightdm-kde-greeter greeter-session=lightdm-kde-greeter ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-greeter 14.04.10-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CurrentDesktop: Unity Date: Mon Sep 29 12:08:56 2014 InstallationDate: Installed on 2014-09-16 (12 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: unity-greeter UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity-greeter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty ** Description changed: I have a laptop with a very high-res screen (Lenovo Yoga 2 Pro with 3200x1600 screen). To make this more usable I set the display to a resolution of 1920x1080 and a higher DPI of 120x120 in the LightDM settings: xserver-command=X -dpi 120 display-setup-script=xrandr --output eDP1 --mode 1920x1080 --primary These settings are ignored or overridden by the unity-greeter. Other greeters, e.g. lightdm-kde-greeter, correctly apply these settings. Steps to reproduce: 1. Change your DPI and resolution settings to be something other than the default for your laptop's display in /etc/lightdm/lightdm.conf, using xserver-command and display-setup-script as above 2. Ensure lightdm is set to use the unity-greeter 2. Restart lightdm or reboot the laptop Expected results: - The lightdm Unity login screen is shown with the resolution and DPI you set using xserver-command and display-setup-script a + The lightdm Unity login screen is shown with the resolution and DPI you set using xserver-command and display-setup-script in lightdm.conf Actual results: - The settings are ignored/overridden and lightdm shows the login screen using the default resolution and display for your device + The settings are ignored/overridden and lightdm shows the login screen using the default resolution and DPI for your device Workaround: Use lightdm-kde-greeter: sudo apt-get install lightdm-kde-greeter greeter-session=lightdm-kde-greeter ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-greeter 14.04.10-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CurrentDesktop: Unity Date: Mon Sep 29 12:08:56 2014 InstallationDate: Installed on 2014-09-16 (12 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: unity-greeter UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1375223 Title: unity-greeter ignores lightdm display resolution and DPI settings Status in “unity-greeter” package in Ubuntu: New Bug description: I have a laptop with a very high-res screen (Lenovo Yoga 2 Pro with 3200x1600 screen). To make this more usable I set the display to a resolution of 1920x1080 and a higher DPI of 120x120 in the LightDM settings: xserver-command=X -dpi 120 display-setup-script=xrandr --output eDP1 --mode 1920x1080 --primary These settings are ignored or overridden by the unity-greeter. Other greeters, e.g. lightdm-kde-greeter, correctly apply these settings. Steps to reproduce: 1. Change your DPI and resolution settings to be something other than the default for your laptop's display in /etc/lightdm/lightdm.conf, using xserver-command and display-setup-script as above 2. Ensure lightdm is set to use the unity-greeter 2. Restart lightdm or reboo
[Desktop-packages] [Bug 1249825] Re: Cannot type into Unity Dash
Hi Francesco, I think it's actually the same issue as this bug (#1249825), but I couldn't find a way to re-open this bug so I created a new one (#1375028) opened against the onboard version in trusty. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to onboard in Ubuntu. https://bugs.launchpad.net/bugs/1249825 Title: Cannot type into Unity Dash Status in Onboard on-screen keyboard: Fix Released Status in “onboard” package in Ubuntu: Fix Released Bug description: I am running Ubuntu 13.10 with onboard version 0.99.0-0ubuntu1. When attempting to type into the Unity Dash (search bar) the dash closes whenever a key is pressed. This seems to be a regression of Bug #915250. It is not a major issue to me currently as I have found two workarounds that seem to resolve the issue for now: 1. Undock Onboard and set Force to top. 2. Maximize Unity Dash window. To manage notifications about this bug go to: https://bugs.launchpad.net/onboard/+bug/1249825/+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 1375028] [NEW] onboard loses the focus when attempting to type in Unity Dash
Public bug reported: It's impossible to use Onboard onscreen keyboard to type in the Unity Dash search box unless onboard is set to 'Force Window on Top' in the Onboard preferences. Setting this shouldn't be necessary as onboard should automatically pop-up when the user selects any object that needs text entry. How to reproduce: 1. Start onboard on a computer with a touchscreen with the onboard setting 'Force Window on Top' disabled 2. Touch the Unity 'search your computer and online sources' to open Dash 3. Touch the 'Search your computer and online sources' search field to begin typing Result: Dash takes the focus away from onboard, meaning it's impossible to type in the Dash search field Expected result: I should be able to use onboard to type in the Dash search field, without needing a physical keyboard or other workarounds Workarounds: In Onboard preferences set 'Force Window on Top' Use a physical keyboard (defeats the purpose of Unity as a touch interface) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: onboard 1.0.0-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CurrentDesktop: Unity Date: Sun Sep 28 19:56:37 2014 InstallationDate: Installed on 2014-09-16 (11 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: onboard UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: onboard (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to onboard in Ubuntu. https://bugs.launchpad.net/bugs/1375028 Title: onboard loses the focus when attempting to type in Unity Dash Status in “onboard” package in Ubuntu: New Bug description: It's impossible to use Onboard onscreen keyboard to type in the Unity Dash search box unless onboard is set to 'Force Window on Top' in the Onboard preferences. Setting this shouldn't be necessary as onboard should automatically pop-up when the user selects any object that needs text entry. How to reproduce: 1. Start onboard on a computer with a touchscreen with the onboard setting 'Force Window on Top' disabled 2. Touch the Unity 'search your computer and online sources' to open Dash 3. Touch the 'Search your computer and online sources' search field to begin typing Result: Dash takes the focus away from onboard, meaning it's impossible to type in the Dash search field Expected result: I should be able to use onboard to type in the Dash search field, without needing a physical keyboard or other workarounds Workarounds: In Onboard preferences set 'Force Window on Top' Use a physical keyboard (defeats the purpose of Unity as a touch interface) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: onboard 1.0.0-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CurrentDesktop: Unity Date: Sun Sep 28 19:56:37 2014 InstallationDate: Installed on 2014-09-16 (11 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: onboard UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/1375028/+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 1249825] Re: Cannot type into Unity Dash
i can still reproduce the bug in 14.04 with onboard 1.0.0. Unless i have 'force window to top' enabled in preferences opening the dash steals focus from onboard and therefore makes it impossible to type in the dash withput using the physical keyboard. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to onboard in Ubuntu. https://bugs.launchpad.net/bugs/1249825 Title: Cannot type into Unity Dash Status in Onboard on-screen keyboard: Fix Released Status in “onboard” package in Ubuntu: Fix Released Bug description: I am running Ubuntu 13.10 with onboard version 0.99.0-0ubuntu1. When attempting to type into the Unity Dash (search bar) the dash closes whenever a key is pressed. This seems to be a regression of Bug #915250. It is not a major issue to me currently as I have found two workarounds that seem to resolve the issue for now: 1. Undock Onboard and set Force to top. 2. Maximize Unity Dash window. To manage notifications about this bug go to: https://bugs.launchpad.net/onboard/+bug/1249825/+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 1013626] Re: systemsettings crashed with ImportError in /usr/share/kde4/apps/language-selector/language-selector.py: No module named LanguageSelector.qt.QtLanguageSelector
I've opened a new bug report about the fact that in the locale kcm only changes language for KDE applications (and so results in a half-half system where some programs use one language, the others another or the default English). https://bugs.launchpad.net/ubuntu/+source/kde-workspace/+bug/1317115 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1013626 Title: systemsettings crashed with ImportError in /usr/share/kde4/apps /language-selector/language-selector.py: No module named LanguageSelector.qt.QtLanguageSelector Status in “kde-workspace” package in Ubuntu: Opinion Status in “language-selector” package in Ubuntu: Invalid Status in “kde-workspace” source package in Quantal: Opinion Status in “language-selector” source package in Quantal: Invalid Bug description: Crash after opening the localisation panel for completing the installation of French as system language. Note: Partial installation of French. Conf: Kubuntu 12.10 Quantal alpha 1. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: systemsettings 4:4.8.90-0ubuntu1 ProcVersionSignature: Ubuntu 3.4.0-5.11-generic 3.4.0 Uname: Linux 3.4.0-5-generic i686 ApportVersion: 2.2.2-0ubuntu2 Architecture: i386 Date: Fri Jun 15 13:43:01 2012 ExecutablePath: /usr/bin/systemsettings InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120530) ProcCmdline: /usr/bin/systemsettings -caption Configuration\ du\ système --icon preferences-system ProcEnviron: LANGUAGE=fr_FR LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: kde-workspace Title: systemsettings crashed with ImportError in /usr/share/kde4/apps/language-selector/language-selector.py: No module named LanguageSelector.qt.QtLanguageSelector Traceback: Traceback (most recent call last): File "/usr/share/kde4/apps/language-selector/language-selector.py", line 4, in from LanguageSelector.qt.QtLanguageSelector import QtLanguageSelector ImportError: No module named LanguageSelector.qt.QtLanguageSelector UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kde-workspace/+bug/1013626/+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
