[Touch-packages] [Bug 1355137] Re: gtk2 theme version improvements for high-dpi screens
The attached files were not submitted as a full patch that solves the problem how to switch between non-hidpi and hidpi systems, but just pointing to the spots where the problematic gtk2 widgets can be multiplied in size. If it is possible to have a switch in gtkrc, someone with gtk2 theming experience (design team?) would need to take a look. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1355137 Title: gtk2 theme version improvements for high-dpi screens Status in ubuntu-themes package in Ubuntu: Incomplete Bug description: GTK2 applications are still widespread and the lack of resolution independence poses significant usability problems, for example for clicking radio buttons or checkboxes. By editing the gtkrc file one can at least mitigate a majority of issues. By doubling dimensions (like widths, heights, not border- widths), the following controls can be made usable: radio buttons, checkboxes, scrollbars, expand/collapse triangles in trees. While this is nothing like complete high-dpi support, still a significant partial improvement can be achieved. Users of high-dpi screens should not have to suffer under the current default, or have to patch the theme manually. It would be good to implement a way that when the scaling factor is >= 2.0, as many GTK 2 widgets as possible are rendered with larger dimensions, be it by theme engine or by switching the theme. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1355137/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1642272] Re: Incorrect UI scale on high-resolution desktop (everything is gigantic)
I discovered: Initially, I had set environment variables in .bashrc for manually triggering the UI scaling of Qt5, Java, etc. During debugging of this issue (as instructed above) I **commented them out** and after loout/login, the incorrect UI scale persisted. Now I noticed that QT_DEVICE_PIXEL_RATIO=2 and QT_AUTO_SCREEN_SCALE_FACTOR=2 were still set automatically during the boot/login process. Instead of commenting them out, I then set them to 1 in ~/.bashrc but they still were overriden. QT_DEVICE_PIXEL_RATIO=1 QT_AUTO_SCREEN_SCALE_FACTOR=1 GRID_UNIT_PX=20 Then I set them in ~/.profile and they were not overriden. Moreover, the unity8 session (8.14+16.10.20160922-0ubuntu2) renders in the correct scale and digikam (5.4.0, Qt 5.7.0) as well. It seems like a Qt API break so that not only these variables are not needed anymore for new programs, but their presence now has the inverse effect. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1642272 Title: Incorrect UI scale on high-resolution desktop (everything is gigantic) Status in Canonical System Image: New Status in Mir: Invalid Status in unity8 package in Ubuntu: Confirmed Bug description: On a hidpi display, the unity8 desktop session in 16.10 has an oversized and inconsistent UI scale. The unity8 session is absolutely not usable for testing (because there is not even enough screen space to display the logout menu item). The shell+cursor is rendered with a UI scale of at least 2× the correct scale (e.g. 4× the scale of a low-dpi display). Due to this the indicator menus collapse immediately after clicking because they are larger than the screen height. The content of the scopes window is rendered with 4× the correct scale, giving space for only one icon. In unity 16.04, the correct scale could be achieved by setting "export GRID_UNIT_PX=16" in .bashrc, however this has no effect anymore when I remove or change it. The issue is also in the guest session. Ubuntu version: 16.10 (fresh install) unity8 version: 8.14+16.10.20160 amd64 physical resolution: 3200×1800 resolution used by unity8: 3200×1800 (at first sight I thought it selected a low resolution, but in fact fonts are very sharp). To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1642272/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1662864] Re: exiv2 fails to read XMP metadata when duplicates present
Upstream bug report: http://dev.exiv2.org/issues/1276 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1662864 Title: exiv2 fails to read XMP metadata when duplicates present Status in exiv2 package in Ubuntu: New Bug description: When reading XMP metadata from image files, exiv2 (and gexiv2) give sometimes no output, although metadata are present. This is the case when duplicate tags are present. While dulicate tags are incorrect and inconsistent, we can not blame some software that did not properly write XMP data, because in real- world scenarios, users DO have image files with duplicate tags, and these files DO contain metadata. Observation: $ exiv2 -px example_duplicate_tags.jpg Error: XMP Toolkit error 203: Duplicate property or field node Warning: Failed to decode XMP metadata. example_duplicate_tags.jpg: (No XMP data found in the file) By contrast, `exiftool example_duplicate_tags.jpg` prints all metadata and ignores duplicates. Expectation: exiv2 should give access to all readable tags. If some XMP tags are inconsistent, it should only be indicated by a warning but not a denial of operation. In case of duplicates the question is open whether to return the last occuring value or the first. Ubuntu 16.10 exiv2 0.25-3 libexiv2-14 0.25-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/1662864/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1662864] Re: exiv2 fails to read XMP metadata when duplicates present
** Summary changed: - exiv2 fails to read xml metadata when duplicates present + exiv2 fails to read XMP metadata when duplicates present -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1662864 Title: exiv2 fails to read XMP metadata when duplicates present Status in exiv2 package in Ubuntu: New Bug description: When reading XMP metadata from image files, exiv2 (and gexiv2) give sometimes no output, although metadata are present. This is the case when duplicate tags are present. While dulicate tags are incorrect and inconsistent, we can not blame some software that did not properly write XMP data, because in real- world scenarios, users DO have image files with duplicate tags, and these files DO contain metadata. Observation: $ exiv2 -px example_duplicate_tags.jpg Error: XMP Toolkit error 203: Duplicate property or field node Warning: Failed to decode XMP metadata. example_duplicate_tags.jpg: (No XMP data found in the file) By contrast, `exiftool example_duplicate_tags.jpg` prints all metadata and ignores duplicates. Expectation: exiv2 should give access to all readable tags. If some XMP tags are inconsistent, it should only be indicated by a warning but not a denial of operation. In case of duplicates the question is open whether to return the last occuring value or the first. Ubuntu 16.10 exiv2 0.25-3 libexiv2-14 0.25-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/1662864/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1662864] [NEW] exiv2 fails to read xml metadata when duplicates present
Public bug reported: When reading XMP metadata from image files, exiv2 (and gexiv2) give sometimes no output, although metadata are present. This is the case when duplicate tags are present. While dulicate tags are incorrect and inconsistent, we can not blame some software that did not properly write XMP data, because in real- world scenarios, users DO have image files with duplicate tags, and these files DO contain metadata. Observation: $ exiv2 -px example_duplicate_tags.jpg Error: XMP Toolkit error 203: Duplicate property or field node Warning: Failed to decode XMP metadata. example_duplicate_tags.jpg: (No XMP data found in the file) By contrast, `exiftool example_duplicate_tags.jpg` prints all metadata and ignores duplicates. Expectation: exiv2 should give access to all readable tags. If some XMP tags are inconsistent, it should only be indicated by a warning but not a denial of operation. In case of duplicates the question is open whether to return the last occuring value or the first. Ubuntu 16.10 exiv2 0.25-3 libexiv2-14 0.25-3 ** Affects: exiv2 (Ubuntu) Importance: Undecided Status: New ** Attachment added: "example image (only downsampled to reduce filesize)" https://bugs.launchpad.net/bugs/1662864/+attachment/4815330/+files/example_duplicate_tags.jpg -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1662864 Title: exiv2 fails to read xml metadata when duplicates present Status in exiv2 package in Ubuntu: New Bug description: When reading XMP metadata from image files, exiv2 (and gexiv2) give sometimes no output, although metadata are present. This is the case when duplicate tags are present. While dulicate tags are incorrect and inconsistent, we can not blame some software that did not properly write XMP data, because in real- world scenarios, users DO have image files with duplicate tags, and these files DO contain metadata. Observation: $ exiv2 -px example_duplicate_tags.jpg Error: XMP Toolkit error 203: Duplicate property or field node Warning: Failed to decode XMP metadata. example_duplicate_tags.jpg: (No XMP data found in the file) By contrast, `exiftool example_duplicate_tags.jpg` prints all metadata and ignores duplicates. Expectation: exiv2 should give access to all readable tags. If some XMP tags are inconsistent, it should only be indicated by a warning but not a denial of operation. In case of duplicates the question is open whether to return the last occuring value or the first. Ubuntu 16.10 exiv2 0.25-3 libexiv2-14 0.25-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/1662864/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1642272] Re: incorrect UI scale on high-resolution desktop
** Attachment added: "unity8.log1-7.zip" https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1642272/+attachment/4780795/+files/unity8.log1-7.zip -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1642272 Title: incorrect UI scale on high-resolution desktop Status in Canonical System Image: Incomplete Status in Mir: Incomplete Status in unity8 package in Ubuntu: Incomplete Bug description: On a hidpi display, the unity8 desktop session in 16.10 has an oversized and inconsistent UI scale. The unity8 session is absolutely not usable for testing (because there is not even enough screen space to display the logout menu item). The shell+cursor is rendered with a UI scale of at least 2× the correct scale (e.g. 4× the scale of a low-dpi display). Due to this the indicator menus collapse immediately after clicking because they are larger than the screen height. The content of the scopes window is rendered with 4× the correct scale, giving space for only one icon. In unity 16.04, the correct scale could be achieved by setting "export GRID_UNIT_PX=16" in .bashrc, however this has no effect anymore when I remove or change it. The issue is also in the guest session. Ubuntu version: 16.10 (fresh install) unity8 version: 8.14+16.10.20160 amd64 physical resolution: 3200×1800 resolution used by unity8: 3200×1800 (at first sight I thought it selected a low resolution, but in fact fonts are very sharp). To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1642272/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1642272] Re: incorrect UI scale on high-resolution desktop
** Attachment added: "unity-system-compositor.log" https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1642272/+attachment/4780796/+files/unity-system-compositor.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1642272 Title: incorrect UI scale on high-resolution desktop Status in Canonical System Image: Incomplete Status in Mir: Incomplete Status in unity8 package in Ubuntu: Incomplete Bug description: On a hidpi display, the unity8 desktop session in 16.10 has an oversized and inconsistent UI scale. The unity8 session is absolutely not usable for testing (because there is not even enough screen space to display the logout menu item). The shell+cursor is rendered with a UI scale of at least 2× the correct scale (e.g. 4× the scale of a low-dpi display). Due to this the indicator menus collapse immediately after clicking because they are larger than the screen height. The content of the scopes window is rendered with 4× the correct scale, giving space for only one icon. In unity 16.04, the correct scale could be achieved by setting "export GRID_UNIT_PX=16" in .bashrc, however this has no effect anymore when I remove or change it. The issue is also in the guest session. Ubuntu version: 16.10 (fresh install) unity8 version: 8.14+16.10.20160 amd64 physical resolution: 3200×1800 resolution used by unity8: 3200×1800 (at first sight I thought it selected a low resolution, but in fact fonts are very sharp). To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1642272/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1642272] Re: incorrect UI scale on high-resolution desktop
I have Qt 5.6.1 installed (and ppa:convergent-apps/testing). xargs -n 1 -0 < /proc/`pidof unity8`/environ | grep GRID_UNIT GRID_UNIT_PX=20 xargs -n 1 -0 < /proc/`pidof unity8`/environ | grep QT_ QT_DEVICE_PIXEL_RATIO=2 QT_IM_MODULE=ibus QT_QPA_PLATFORM=ubuntumirclient ** Attachment added: "unity8.log" https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1642272/+attachment/4780794/+files/unity8.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1642272 Title: incorrect UI scale on high-resolution desktop Status in Canonical System Image: Incomplete Status in Mir: Incomplete Status in unity8 package in Ubuntu: Incomplete Bug description: On a hidpi display, the unity8 desktop session in 16.10 has an oversized and inconsistent UI scale. The unity8 session is absolutely not usable for testing (because there is not even enough screen space to display the logout menu item). The shell+cursor is rendered with a UI scale of at least 2× the correct scale (e.g. 4× the scale of a low-dpi display). Due to this the indicator menus collapse immediately after clicking because they are larger than the screen height. The content of the scopes window is rendered with 4× the correct scale, giving space for only one icon. In unity 16.04, the correct scale could be achieved by setting "export GRID_UNIT_PX=16" in .bashrc, however this has no effect anymore when I remove or change it. The issue is also in the guest session. Ubuntu version: 16.10 (fresh install) unity8 version: 8.14+16.10.20160 amd64 physical resolution: 3200×1800 resolution used by unity8: 3200×1800 (at first sight I thought it selected a low resolution, but in fact fonts are very sharp). To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1642272/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1642272] [NEW] incorrect UI scale on high-resolution desktop
Public bug reported: On a hidpi display, the unity8 desktop session in 16.10 has an oversized and inconsistent UI scale. The unity8 session is absolutely not usable for testing (because there is not even enough screen space to display the logout menu item). The shell+cursor is rendered with a UI scale of at least 2× the correct scale (e.g. 4× the scale of a low-dpi display). Due to this the indicator menus collapse immediately after clicking because they are larger than the screen height. The content of the scopes window is rendered with 4× the correct scale, giving space for only one icon. In unity 16.04, the correct scale could be achieved by setting "export GRID_UNIT_PX=16" in .bashrc, however this has no effect anymore when I remove or change it. The issue is also in the guest session. Ubuntu version: 16.10 (fresh install) unity8 version: 8.14+16.10.20160 amd64 physical resolution: 3200×1800 resolution used by unity8: 3200×1800 (at first sight I thought it selected a low resolution, but in fact fonts are very sharp). ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Attachment added: "photo showing the shell 2× too big and the scopes 4× too big" https://bugs.launchpad.net/bugs/1642272/+attachment/4778139/+files/IMG_20161116_141005.jpg -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1642272 Title: incorrect UI scale on high-resolution desktop Status in unity8 package in Ubuntu: New Bug description: On a hidpi display, the unity8 desktop session in 16.10 has an oversized and inconsistent UI scale. The unity8 session is absolutely not usable for testing (because there is not even enough screen space to display the logout menu item). The shell+cursor is rendered with a UI scale of at least 2× the correct scale (e.g. 4× the scale of a low-dpi display). Due to this the indicator menus collapse immediately after clicking because they are larger than the screen height. The content of the scopes window is rendered with 4× the correct scale, giving space for only one icon. In unity 16.04, the correct scale could be achieved by setting "export GRID_UNIT_PX=16" in .bashrc, however this has no effect anymore when I remove or change it. The issue is also in the guest session. Ubuntu version: 16.10 (fresh install) unity8 version: 8.14+16.10.20160 amd64 physical resolution: 3200×1800 resolution used by unity8: 3200×1800 (at first sight I thought it selected a low resolution, but in fact fonts are very sharp). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1642272/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1633890] [NEW] sudo password field allows other applications to steal focus
Public bug reported: When apport asks for the sudo passwords, other applications or dialogs can steal focus. This is inacceptable because it leads to leaked passwords. Moreover, it is inconvenient because the apport sudo dialog contains possibly a part of the password and the other application the other part, requiring to retype it. observed behavior: 1. apport asks for sudo rights. 2. I start typing the password. 3. network manager has disconnected from wifi and asks for wifi password, with the wifi password dialog getting focussed. 4. The remaining characters that I type go into the second application (network manager) with the enter key causing an unintended action. expected behavior: When typing a password, no other application can be focussed automatically (i.e. not by user action) until I have finished typing the password. This can be implemented as: - in all UI toolkits, if a password input field is focussed and the user is currently typing (timeout after last keys stroke), the application locks focus. - make sudo dialog system-modal, and the window manager does not allow anything else being focussed by non-user action. Ubuntu 16.04 apport-gtk 2.20.1-0ubuntu2.1 ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Description changed: When apport asks for the sudo passwords, other applications or dialogs can steal focus. This is inacceptable because it leads to leaked passwords. Moreover, it is inconvenient because the apport sudo dialog contains possibly a part of the password and the other application the other part, requiring to retype it. observed behavior: 1. apport asks for sudo rights. 2. I start typing the password. 3. network manager has disconnected from wifi and asks for wifi password, with the wifi password dialog getting focussed. 4. The remaining characters that I type go into the second application (network manager) with the enter key causing an unintended action. expected behavior: When typing a password, no other application can be focussed automatically (i.e. not by user action) until I have finished typing the password. This can be implemented as: - in all UI toolkits, if a password input field is focussed and the user is currently typing (timeout after last keys stroke), the application locks focus. - make sudo dialog system-modal, and the window manager does not allow anything else being focussed by non-user action. + + Ubuntu 16.04 + apport-gtk 2.20.1-0ubuntu2.1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1633890 Title: sudo password field allows other applications to steal focus Status in apport package in Ubuntu: New Bug description: When apport asks for the sudo passwords, other applications or dialogs can steal focus. This is inacceptable because it leads to leaked passwords. Moreover, it is inconvenient because the apport sudo dialog contains possibly a part of the password and the other application the other part, requiring to retype it. observed behavior: 1. apport asks for sudo rights. 2. I start typing the password. 3. network manager has disconnected from wifi and asks for wifi password, with the wifi password dialog getting focussed. 4. The remaining characters that I type go into the second application (network manager) with the enter key causing an unintended action. expected behavior: When typing a password, no other application can be focussed automatically (i.e. not by user action) until I have finished typing the password. This can be implemented as: - in all UI toolkits, if a password input field is focussed and the user is currently typing (timeout after last keys stroke), the application locks focus. - make sudo dialog system-modal, and the window manager does not allow anything else being focussed by non-user action. Ubuntu 16.04 apport-gtk 2.20.1-0ubuntu2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1633890/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1581383] Re: mouse cursor missing
It sometimes re-appears after hours suddenly, or sometimes after
logout After each fresh boot, the cursor is invisible.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1581383
Title:
mouse cursor missing
Status in xorg package in Ubuntu:
New
Bug description:
After upgrading from 15.10 to 16.04 ("stable"), the mouse cursor is
missing. This persists after re-login and after reboot and after
changing mouse cursor theme or display resolution.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: unity 7.4.0+16.04.20160415-0ubuntu1
Uname: Linux 4.2.0-040200rc3-generic x86_64
.tmp.unity_support_test.0:
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
BootLog:
Ubuntu: clean, 440558/1024000 files, 3594332/4096000 blocks
[[0;1;31mFAILED[0m] Failed to start PostgreSQL Cluster 9.4-main.
See 'systemctl status postgresql@9.4-main.service' for details.
[[0;32m OK [0m] Started Modem Manager.
[[0;32m OK [0m] Started OpenBSD Secure Shell server.
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Fri May 13 10:48:04 2016
DistUpgraded: 2016-05-12 16:54:01,635 DEBUG Running PostInstallScript:
'./xorg_fix_proprietary.py'
DistroCodename: xenial
DistroVariant: ubuntu
EcryptfsInUse: Yes
GraphicsCard:
Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16]
(rev 09) (prog-if 00 [VGA controller])
Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:3978]
InstallationDate: Installed on 2015-06-06 (341 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: LENOVO 20266
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-040200rc3-generic
root=UUID=8a0dc2f3-fcf3-4e5b-8e23-1441bd36e3dc ro noprompt persistent quiet
splash acpi_backlight=vendor vt.handoff=7
SourcePackage: unity
UpgradeStatus: Upgraded to xenial on 2016-05-12 (0 days ago)
dmi.bios.date: 03/30/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: 76CN43WW
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:bvr76CN43WW:bd03/30/2015:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro:
dmi.product.name: 20266
dmi.product.version: Lenovo Yoga 2 Pro
dmi.sys.vendor: LENOVO
upstart.unity-panel-service-lockscreen.log:
(unity-panel-service:2821): GLib-CRITICAL **: Source ID 4294967295 was not
found when attempting to remove it
(unity-panel-service:7583): GLib-CRITICAL **: Source ID 4294967295 was not
found when attempting to remove it
(unity-panel-service:8651): GLib-CRITICAL **: Source ID 4294967295 was not
found when attempting to remove it
version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20160325-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.12-1build2
xserver.bootTime: Thu May 12 17:28:41 2016
xserver.configfile: /etc/X11/xorg.conf
xserver.errors:
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.3-1ubuntu2
xserver.video_driver: intel
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1581383/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1448982] Re: mouse cursor disappears after standby
After upgrading to Ubuntu 15.04, I still see this happening sometimes (but noticeably less often then in 14.10): - after boot (→ then I reboot) - after standby - after user switching Sometimes the cursor appears again after some action, or after logging in again or after closing the laptop lid (standby) and waking up again. But also often the cursor remains invisible even after logging out or killing Xorg, then I have no other choice than reboot. This is totally indeterministic. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1448982 Title: mouse cursor disappears after standby Status in Unity: New Status in unity package in Ubuntu: New Bug description: After standby, the mouse cursor was not visible anymore. After to subsequent times standby and wakeup, the mouse cursor remains invisible. The mouse cursor does not reappear by doing a dragdrop or switching themes or restarting unity (unity --replace) or restarting the kernel module psmouse. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 Uname: Linux 3.17.1-031701-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Apr 27 12:34:34 2015 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.18, 3.16.0-34-generic, x86_64: installed virtualbox, 4.3.18, 3.16.0-36-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3978] InstallationDate: Installed on 2015-01-13 (103 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: LENOVO 20266 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.17.1-031701-generic root=UUID=8a0dc2f3-fcf3-4e5b-8e23-1441bd36e3dc ro quiet splash acpi_backlight=vendor quiet splash acpi_backlight=vendor vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/31/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN31WW 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:bvr76CN31WW:bd10/31/2013: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.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Wed Apr 22 11:26:09 2015 xserver.configfile: /etc/X11/xorg.conf xserver.errors: [dix] ELAN Touchscreen: unable to find touch point 0 SynPS/2 Synaptics TouchPad: Read error 19 xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.16.0-1ubuntu1.3 xserver.video_driver: intel To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1448982/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1310186] Re: mediascanner prevents unmounting usb device
I wonder what is the benefit of scanning external drives that are mounted only temporarily, especially when connecting other people's USB sticks. Since mediascanner is a process that was not launched manually by the user, the confirmation on removal (device busy) is redundant, instead mediascanner could probably shutdown silently whenever unmounting of the device is requested (ie. unmounting should be done by no more than one click in nautilus sidebar etc.). The risk of bricking your own or even worse other people's USB stick by improper removal (if a process is unperceivedly still running on the drive) is too high so that it is questionable whether mediascanner should run at all on external drives. I think this is a very critical situation. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mediascanner2 in Ubuntu. https://bugs.launchpad.net/bugs/1310186 Title: mediascanner prevents unmounting usb device Status in mediascanner2 package in Ubuntu: Confirmed Bug description: Trying to unmount a block device I just mounted, I get the following error (sorry for not resetting the locale. It says Device is busy): :~$ sudo umount /media/tkluck/tjk-backup umount2: Apparaat of hulpbron is bezig umount: /media/tkluck/tjk-backup: apparaat is bezig (Welke processen het apparaat gebruiken kan mogelijk gevonden worden met behulp van lsof(8) of fuser(1).) umount2: Apparaat of hulpbron is bezig I get the same error in a dialog window when trying to unmount from the file manager. Using lsof shows that the media-scanner daemon is the culprit: tkluck@ultrabook-tjk:~$ lsof /media/tkluck/tjk-backup COMMANDPID USER FD TYPE DEVICE SIZE/OFF NODE NAME mediascan 2898 tkluck 16r DIR 252,3 2498562 /media/tkluck/tjk-backup mediascan 2898 tkluck 17r DIR 252,3 4096 50855937 REDACTED mediascan 2898 tkluck 18r DIR 252,3 4096 39080372 REDACTED mediascan 2898 tkluck 19r DIR 252,312288 39080513 REDACTED mediascan 2898 tkluck 20r DIR 252,320480 39080525 REDACTED mediascan 2898 tkluck 21r DIR 252,3 4096 46792990 REDACTED mediascan 2898 tkluck 22r DIR 252,3 4096 46792991 REDACTED mediascan 2898 tkluck 23r DIR 252,316384 46793749 REDACTED mediascan 2898 tkluck 24r DIR 252,3 4096 47317994 REDACTED mediascan 2898 tkluck 25r DIR 252,3 4096 47317997 REDACTED mediascan 2898 tkluck 26r DIR 252,3 4096 47317999 REDACTED Sending it sudo kill -9 2898 solved this for me. This is on Ubuntu GNOME 14.04. I uninstalled the mediascanner2.0 to solve this once and for all (which has no other impact since I do not use Unity). My guess is that the scan usually finishes quickly after mounting. But because this particular drive contains a big filetree, it doesn't, resulting in the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mediascanner2/+bug/1310186/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1430380] Re: wrong default icon size with user interface scaling
15.04 was released with this newly introduced bug. Is there any hope this will be fixed in the stable version, should I better upgrade to 15.10? Is nobody else using a scaling factor? How can this bug be either a) unnoticed, b) ignored or c) noticed but not relevant? Are there no quality criterias that a release must fulfill? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1430380 Title: wrong default icon size with user interface scaling Status in Unity: New Status in unity package in Ubuntu: New Bug description: When using user interface scaling (like on high-dpi screens) with scale factor 2, gtk3 application toolbars show the icon resource of twice the correct size. The icons are not upsampled, just the too big resource file is chosen (that would fit a scale factor of 4). This was tested with default settings (15.04 iso). This issue did not occur in default settings of older releases (14.10). Ubuntu 15.04 from vivid-desktop-amd64.iso 06-Mar-2015 08:00 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1430380/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1446639] Re: Ubuntu loads configuration incorrectly on high-dpi screen
This is happening regularly during the first boot(s) after kernel or xorg updates. Is it possible it could be related to something like ureadahead? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1446639 Title: Ubuntu loads configuration incorrectly on high-dpi screen Status in unity package in Ubuntu: New Bug description: When booting, unity loads the desktop partially with double the correct size (default setting: scale factor 2, but it loads as if scale factor 4). The launcher, dash, application switcher appear too big while the panel and applications themselves have correct size. After some seconds the screen turns black, the wallpaper appears 4 times and then the wallpaper appears at correct size as well as launcher, dash, application switcher and panel. However, the desktop icons and the window content of gtk3 applications appears too small (as with scale factor 1). This is only true for gtk3 applications, not gtk2, Wine, XUL, Qt, VCL. Also, unity panel uses incorrect (strong) font hinting while font hinting is correct in the rest of the system. Unity dash uses partially a fallback sans serif font instead of Ubuntu font and incorrect character kerning. This is similar as bug #1398208. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 Uname: Linux 3.17.1-031701-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Apr 21 14:43:35 2015 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.18, 3.16.0-34-generic, x86_64: installed virtualbox, 4.3.18, 3.16.0-36-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3978] InstallationDate: Installed on 2015-01-13 (97 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: LENOVO 20266 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.17.1-031701-generic root=UUID=8a0dc2f3-fcf3-4e5b-8e23-1441bd36e3dc ro quiet splash acpi_backlight=vendor quiet splash acpi_backlight=vendor vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/31/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN31WW 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:bvr76CN31WW:bd10/31/2013: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.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Tue Apr 21 14:43:00 2015 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.16.0-1ubuntu1.3 xserver.video_driver: intel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1446639/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1448982] [NEW] mouse cursor disappears after standby
Public bug reported: After standby, the mouse cursor was not visible anymore. After to subsequent times standby and wakeup, the mouse cursor remains invisible. The mouse cursor does not reappear by doing a dragdrop or switching themes or restarting the kernel module psmouse. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 Uname: Linux 3.17.1-031701-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Apr 27 12:34:34 2015 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.18, 3.16.0-34-generic, x86_64: installed virtualbox, 4.3.18, 3.16.0-36-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3978] InstallationDate: Installed on 2015-01-13 (103 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: LENOVO 20266 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.17.1-031701-generic root=UUID=8a0dc2f3-fcf3-4e5b-8e23-1441bd36e3dc ro quiet splash acpi_backlight=vendor quiet splash acpi_backlight=vendor vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/31/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN31WW 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:bvr76CN31WW:bd10/31/2013: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.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Wed Apr 22 11:26:09 2015 xserver.configfile: /etc/X11/xorg.conf xserver.errors: [dix] ELAN Touchscreen: unable to find touch point 0 SynPS/2 Synaptics TouchPad: Read error 19 xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.16.0-1ubuntu1.3 xserver.video_driver: intel ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 third-party-packages ubuntu utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1448982 Title: mouse cursor disappears after standby Status in unity package in Ubuntu: New Bug description: After standby, the mouse cursor was not visible anymore. After to subsequent times standby and wakeup, the mouse cursor remains invisible. The mouse cursor does not reappear by doing a dragdrop or switching themes or restarting the kernel module psmouse. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 Uname: Linux 3.17.1-031701-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Apr 27 12:34:34 2015 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.18, 3.16.0-34-generic, x86_64: installed virtualbox, 4.3.18, 3.16.0-36-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3978] InstallationDate: Installed on 2015-01-13 (103 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: LENOVO 20266 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.17.1-031701-generic
[Touch-packages] [Bug 1448982] Re: mouse cursor disappears after standby
** Description changed: After standby, the mouse cursor was not visible anymore. After to subsequent times standby and wakeup, the mouse cursor remains invisible. The mouse cursor does not reappear by doing a dragdrop or - switching themes or restarting the kernel module psmouse. + switching themes or restarting unity (unity --replace) or restarting the + kernel module psmouse. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 Uname: Linux 3.17.1-031701-generic x86_64 .tmp.unity.support.test.0: - + ApportVersion: 2.14.7-0ubuntu8.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Apr 27 12:34:34 2015 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: - virtualbox, 4.3.18, 3.16.0-34-generic, x86_64: installed - virtualbox, 4.3.18, 3.16.0-36-generic, x86_64: installed + virtualbox, 4.3.18, 3.16.0-34-generic, x86_64: installed + virtualbox, 4.3.18, 3.16.0-36-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: - Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) -Subsystem: Lenovo Device [17aa:3978] + Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) + Subsystem: Lenovo Device [17aa:3978] InstallationDate: Installed on 2015-01-13 (103 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: LENOVO 20266 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.17.1-031701-generic root=UUID=8a0dc2f3-fcf3-4e5b-8e23-1441bd36e3dc ro quiet splash acpi_backlight=vendor quiet splash acpi_backlight=vendor vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/31/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN31WW 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:bvr76CN31WW:bd10/31/2013: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.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Wed Apr 22 11:26:09 2015 xserver.configfile: /etc/X11/xorg.conf xserver.errors: - [dix] ELAN Touchscreen: unable to find touch point 0 - SynPS/2 Synaptics TouchPad: Read error 19 + [dix] ELAN Touchscreen: unable to find touch point 0 + SynPS/2 Synaptics TouchPad: Read error 19 xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.16.0-1ubuntu1.3 xserver.video_driver: intel -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1448982 Title: mouse cursor disappears after standby Status in unity package in Ubuntu: New Bug description: After standby, the mouse cursor was not visible anymore. After to subsequent times standby and wakeup, the mouse cursor remains invisible. The mouse cursor does not reappear by doing a dragdrop or switching themes or restarting unity (unity --replace) or restarting the kernel module psmouse. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 Uname: Linux 3.17.1-031701-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Apr 27 12:34:34 2015 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.18, 3.16.0-34-generic, x86_64:
[Touch-packages] [Bug 1446639] [NEW] Ubuntu loads configuration incorrectly on high-dpi screen
Public bug reported: When booting, unity loads the desktop partially with double the correct size (default setting: scale factor 2, but it loads as if scale factor 4). The launcher, dash, application switcher appear too big while the panel and applications themselves have correct size. After some seconds the screen turns black, the wallpaper appears 4 times and then the wallpaper appears at correct size as well as launcher, dash, application switcher and panel. However, the desktop icons and the window content of gtk3 applications appears too small (as with scale factor 1). This is only true for gtk3 applications, not gtk2, Wine, XUL, Qt, VCL. Also, unity panel uses incorrect (strong) font hinting while font hinting is correct in the rest of the system. Unity dash uses partially a fallback sans serif font instead of Ubuntu font and incorrect character kerning. This is similar as bug #1398208. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 Uname: Linux 3.17.1-031701-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Apr 21 14:43:35 2015 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.18, 3.16.0-34-generic, x86_64: installed virtualbox, 4.3.18, 3.16.0-36-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3978] InstallationDate: Installed on 2015-01-13 (97 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: LENOVO 20266 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.17.1-031701-generic root=UUID=8a0dc2f3-fcf3-4e5b-8e23-1441bd36e3dc ro quiet splash acpi_backlight=vendor quiet splash acpi_backlight=vendor vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/31/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN31WW 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:bvr76CN31WW:bd10/31/2013: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.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Tue Apr 21 14:43:00 2015 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.16.0-1ubuntu1.3 xserver.video_driver: intel ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 third-party-packages ubuntu utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1446639 Title: Ubuntu loads configuration incorrectly on high-dpi screen Status in unity package in Ubuntu: New Bug description: When booting, unity loads the desktop partially with double the correct size (default setting: scale factor 2, but it loads as if scale factor 4). The launcher, dash, application switcher appear too big while the panel and applications themselves have correct size. After some seconds the screen turns black, the wallpaper appears 4 times and then the wallpaper appears at correct size as well as launcher, dash, application switcher and panel. However, the desktop icons and the window content of gtk3 applications appears too small (as with scale factor 1). This is only true for gtk3 applications, not gtk2, Wine, XUL, Qt, VCL. Also, unity panel uses incorrect (strong) font hinting while font hinting is correct in the rest of the system. Unity dash uses partially a fallback sans serif font instead of Ubuntu font and incorrect character
[Touch-packages] [Bug 1416128] Re: Moving the microphone volume slider bounces back
This is happening in stable released 14.10. It appears to happen only when running skype (not tested with other applications that consume microphone input). 1. Open Ubuntu Control Center → Sound → Input 2. Do a Skype call (eg. Echo call) 3. Adjust the microphone volume in Ubuntu Software Center ** Attachment added: Video showing the problem https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1416128/+attachment/4380808/+files/Kazam_screencast_4.mp4 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-sound in Ubuntu. https://bugs.launchpad.net/bugs/1416128 Title: Moving the microphone volume slider bounces back Status in indicator-sound package in Ubuntu: Incomplete Bug description: When moving the microphone slider in the Unity sound menu or in Ubuntu Contorl Center / Sound, it starts moving back to the left and decreases volume again to the original position. As a consequence, it is hard to due phone/skype/hangout calls because the counterpart doesn't understand the recorded sound. This could be a UI issue related to high-dpi (scaling-factor=2), similar to bug #1299054. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Thu Jan 29 22:56:36 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-01-13 (16 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1416128/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1398208] Re: unity fails to load after booting with high-dpi screen
I does not happen anymore with 7.3.1+14.10.20141016-0ubuntu1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1398208 Title: unity fails to load after booting with high-dpi screen Status in Unity: Incomplete Status in unity package in Ubuntu: Incomplete Bug description: After booting, the first login attempt *always* loads Unity with incorrect/inconsistent scaling and many settings fail to load. The panel and window titlebars display correctly at 2× scaling, but the desktop icons (nautilus) and other application content is too small. The user interface font is too small and not the right font-family 'Ubuntu'. Fonts render with inconsistent kerning. The Unity Dash also shows the wrong font. Gtk2 themes don't load. After logging out and in again (sometimes 2 attempty necessary), all configurations load correctly. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Dec 1 23:52:51 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-02-02 (302 days ago) InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140201) SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2014-11-04 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1398208/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1432209] [NEW] ibus-daemon causes high cpu activity in gedit
Public bug reported: When typing text / deleting text via keyboard in gedit, the process ibus-daemon gets high cpu activity (70–100%), causes the fan turning on and in some cases crashes gedit. This is when keyboard input method is set to IBus and more than one input method is enabled (German [active], English USA, Chinese Pinyin). ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ibus 1.5.8-2ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-32.42-generic 3.16.7-ckt7 Uname: Linux 3.16.0-32-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 14 18:50:55 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-01-13 (60 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ibus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1432209 Title: ibus-daemon causes high cpu activity in gedit Status in ibus package in Ubuntu: New Bug description: When typing text / deleting text via keyboard in gedit, the process ibus-daemon gets high cpu activity (70–100%), causes the fan turning on and in some cases crashes gedit. This is when keyboard input method is set to IBus and more than one input method is enabled (German [active], English USA, Chinese Pinyin). ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ibus 1.5.8-2ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-32.42-generic 3.16.7-ckt7 Uname: Linux 3.16.0-32-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 14 18:50:55 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-01-13 (60 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1432209/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1430380] [NEW] wrong default icon size with user interface scaling
Public bug reported: When using user interface scaling (like on high-dpi screens) with scale factor 2, gtk3 application toolbars show the icon resource of twice the correct size. The icons are not upsampled, just the too big resource file is chosen (that would fit a scale factor of 4). This was tested with default settings (15.04 iso). This issue did not occur in default settings of older releases (14.10). Ubuntu 15.04 from vivid-desktop-amd64.iso 06-Mar-2015 08:00 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Attachment added: screenshot. Note: the screen's resolution was bigger than the image's resolution. https://bugs.launchpad.net/bugs/1430380/+attachment/4340095/+files/vivid%20icon%20size.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1430380 Title: wrong default icon size with user interface scaling Status in unity package in Ubuntu: New Bug description: When using user interface scaling (like on high-dpi screens) with scale factor 2, gtk3 application toolbars show the icon resource of twice the correct size. The icons are not upsampled, just the too big resource file is chosen (that would fit a scale factor of 4). This was tested with default settings (15.04 iso). This issue did not occur in default settings of older releases (14.10). Ubuntu 15.04 from vivid-desktop-amd64.iso 06-Mar-2015 08:00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1430380/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1301125] Re: Lock screen after idle time freezes unity
I have 7.3.1+14.10.20141016-0ubuntu1 (unity-proposed and unity-backports enabled). Unfortunately I did not succeed just restarting unity (without restarting Xorg): env DISPLAY=0,0 unity --restart Gives error output (I don't have it kcomplete) with unknown job unity-panel-service. If it can be worked-around, how could it be it done? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1301125 Title: Lock screen after idle time freezes unity Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Hello, I recently upgrade to 14.04. My system uses fglrx provided by 14.04. When I lock manually the screen, I get no problem. I can even sleep the system without problem. However, when the screen is locked by idle time, I cannot unlock it. At this point, I can see the screen but with some kind of translucent panel over it. Mouse also works. I tried to type blink the password but I had no luck. I only get a working system by going text mode (ctrl+alt+f1) and restarting lightdm. No dmesg or Xorg logs seems to indicate any error. The only strange log was in .xsession-errors.old: init: processos unity-settings-daemon main (2495) terminados com status 1 init: processos gnome-session (Unity) main (2539) terminados com status 1 init: processos unity-panel-service main (2572) terminados com status 1 init: processos hud main (2536) terminados com status 1 init: processo indicator-powermain (2740) morto pelo sinal TERM init: processo indicator-datetimemain (2741) morto pelo sinal TERM init: processo indicator-soundmain (2747) morto pelo sinal TERM init: processo indicator-printersmain (2748) morto pelo sinal TERM init: processo indicator-sessionmain (2768) morto pelo sinal TERM init: processo indicator-syncmain (2795) morto pelo sinal TERM init: processo update-notifier-crash (/var/crash/_usr_bin_istanbul.1000.crash)main (4987) morto pelo sinal TERM init: processos unity-panel-service-lockscreen main (7447) terminados com status 1 init: Disconnected from notified D-Bus bus init: processos at-spi2-registryd main (2538) terminados com status 1 But as it has no time info, I cannot tell when they happened. At least another user faces the same problem: http://ubuntuforums.org/showthread.php?t=2214421 And this seems to be different from bug 1283938 as pm sleep/wake works as expected. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140328.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Apr 2 00:01:05 2014 DistUpgraded: 2014-03-31 21:24:46,145 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fglrx-updates, 13.350.1, 3.11.0-18-generic, x86_64: installed fglrx-updates, 13.350.1, 3.13.0-20-generic, x86_64: installed vboxhost, 4.3.10, 3.11.0-18-generic, x86_64: installed vboxhost, 4.3.10, 3.13.0-20-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] [1002:6758] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0012] InstallationDate: Installed on 2012-10-19 (529 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) JockeyStatus: kmod:wl - Broadcom STA wireless driver (Proprietário, Desativado, Não está em uso) [auto-install] kmod:fglrx - Video driver for the AMD graphics accelerators (Proprietário, Desativado, Não está em uso) kmod:fglrx_updates - ATI Fire GL (Proprietário, Habilitado, Não está em uso) MachineType: Dell Inc. XPS 8300 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic root=UUID=6633d579-d782-47ec-ad5a-22abac1412a0 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-04-01 (1 days ago) dmi.bios.date: 10/17/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0Y2MRG dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd10/17/2011:svnDellInc.:pnXPS8300:pvr:rvnDellInc.:rn0Y2MRG:rvrA01:cvnDellInc.:ct3:cvr: dmi.product.name: XPS 8300 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1 version.fglrx-installer:
[Touch-packages] [Bug 1417648] [NEW] greeter: wifi prompt steals focus from user login password input
Public bug reported: In the unity greeter, a user selects an account and types a password and presses or enter to login. While typing the password, sometimes a wifi prompt pops up and steals focus from the password prompt. * It is disruptive and leaves the typed login password incomplete/incorrect. * It is redundant, because when almost having completed the login it is faster to login and let Ubuntu connect to the wifi automatically. * The wifi prompt asks for a wifi password that it never remembers. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Feb 3 17:11:29 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-01-13 (21 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1417648 Title: greeter: wifi prompt steals focus from user login password input Status in unity package in Ubuntu: New Bug description: In the unity greeter, a user selects an account and types a password and presses or enter to login. While typing the password, sometimes a wifi prompt pops up and steals focus from the password prompt. * It is disruptive and leaves the typed login password incomplete/incorrect. * It is redundant, because when almost having completed the login it is faster to login and let Ubuntu connect to the wifi automatically. * The wifi prompt asks for a wifi password that it never remembers. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Feb 3 17:11:29 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-01-13 (21 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1417648/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1301125] Re: Lock screen after idle time freezes unity
This happens to me at least once every day, each time the whole session, open windows and unsaved documents lost (I save, yes, but the fact that at any time things can be lost makes this a critical issue for me). Is there a chance this can be fixed? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1301125 Title: Lock screen after idle time freezes unity Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Hello, I recently upgrade to 14.04. My system uses fglrx provided by 14.04. When I lock manually the screen, I get no problem. I can even sleep the system without problem. However, when the screen is locked by idle time, I cannot unlock it. At this point, I can see the screen but with some kind of translucent panel over it. Mouse also works. I tried to type blink the password but I had no luck. I only get a working system by going text mode (ctrl+alt+f1) and restarting lightdm. No dmesg or Xorg logs seems to indicate any error. The only strange log was in .xsession-errors.old: init: processos unity-settings-daemon main (2495) terminados com status 1 init: processos gnome-session (Unity) main (2539) terminados com status 1 init: processos unity-panel-service main (2572) terminados com status 1 init: processos hud main (2536) terminados com status 1 init: processo indicator-powermain (2740) morto pelo sinal TERM init: processo indicator-datetimemain (2741) morto pelo sinal TERM init: processo indicator-soundmain (2747) morto pelo sinal TERM init: processo indicator-printersmain (2748) morto pelo sinal TERM init: processo indicator-sessionmain (2768) morto pelo sinal TERM init: processo indicator-syncmain (2795) morto pelo sinal TERM init: processo update-notifier-crash (/var/crash/_usr_bin_istanbul.1000.crash)main (4987) morto pelo sinal TERM init: processos unity-panel-service-lockscreen main (7447) terminados com status 1 init: Disconnected from notified D-Bus bus init: processos at-spi2-registryd main (2538) terminados com status 1 But as it has no time info, I cannot tell when they happened. At least another user faces the same problem: http://ubuntuforums.org/showthread.php?t=2214421 And this seems to be different from bug 1283938 as pm sleep/wake works as expected. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140328.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Apr 2 00:01:05 2014 DistUpgraded: 2014-03-31 21:24:46,145 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fglrx-updates, 13.350.1, 3.11.0-18-generic, x86_64: installed fglrx-updates, 13.350.1, 3.13.0-20-generic, x86_64: installed vboxhost, 4.3.10, 3.11.0-18-generic, x86_64: installed vboxhost, 4.3.10, 3.13.0-20-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] [1002:6758] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0012] InstallationDate: Installed on 2012-10-19 (529 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) JockeyStatus: kmod:wl - Broadcom STA wireless driver (Proprietário, Desativado, Não está em uso) [auto-install] kmod:fglrx - Video driver for the AMD graphics accelerators (Proprietário, Desativado, Não está em uso) kmod:fglrx_updates - ATI Fire GL (Proprietário, Habilitado, Não está em uso) MachineType: Dell Inc. XPS 8300 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic root=UUID=6633d579-d782-47ec-ad5a-22abac1412a0 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-04-01 (1 days ago) dmi.bios.date: 10/17/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0Y2MRG dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd10/17/2011:svnDellInc.:pnXPS8300:pvr:rvnDellInc.:rn0Y2MRG:rvrA01:cvnDellInc.:ct3:cvr: dmi.product.name: XPS 8300 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1
[Touch-packages] [Bug 1416128] [NEW] Moving the microphone volume slider bounces back
Public bug reported: When moving the microphone slider in the Unity sound menu or in Ubuntu Contorl Center / Sound, it starts moving back to the left and decreases volume again to the original position. As a consequence, it is hard to due phone/skype/hangout calls because the counterpart doesn't understand the recorded sound. This could be a UI issue related to high-dpi (scaling-factor=2), similar to bug #1299054. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Thu Jan 29 22:56:36 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-01-13 (16 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1416128 Title: Moving the microphone volume slider bounces back Status in unity package in Ubuntu: New Bug description: When moving the microphone slider in the Unity sound menu or in Ubuntu Contorl Center / Sound, it starts moving back to the left and decreases volume again to the original position. As a consequence, it is hard to due phone/skype/hangout calls because the counterpart doesn't understand the recorded sound. This could be a UI issue related to high-dpi (scaling-factor=2), similar to bug #1299054. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Thu Jan 29 22:56:36 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-01-13 (16 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1416128/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1355137] Re: gtk2 theme version improvements for high-dpi screens
Not being a developer I don't have enough knowledge to do a patch that can be integrated and packaged. These modified files reduce the problem significantly, but only: • for the Ambiance theme, if another theme is applied the benefits are lost • for a UI scaling factor of 2 There would be a switch needed which files to use depending on the integer value of the UI scaling factor. Ideally it would be patched in the software that reads these gtkrc files, and apply integer scaling to these dimensions (size, width, height, length). ** Attachment added: patched files of the /usr/share/Ambiance/gtk2.0 folder https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1355137/+attachment/4300156/+files/Ambiance_gtk-2.0.zip -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1355137 Title: gtk2 theme version improvements for high-dpi screens Status in ubuntu-themes package in Ubuntu: New Bug description: GTK2 applications are still widespread and the lack of resolution independence poses significant usability problems, for example for clicking radio buttons or checkboxes. By editing the gtkrc file one can at least mitigate a majority of issues. By doubling dimensions (like widths, heights, not border- widths), the following controls can be made usable: radio buttons, checkboxes, scrollbars, expand/collapse triangles in trees. While this is nothing like complete high-dpi support, still a significant partial improvement can be achieved. Users of high-dpi screens should not have to suffer under the current default, or have to patch the theme manually. It would be good to implement a way that when the scaling factor is = 2.0, as many GTK 2 widgets as possible are rendered with larger dimensions, be it by theme engine or by switching the theme. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1355137/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1355137] Re: gtk2 theme version improvements for high-dpi screens
** Attachment added: patched files of the /usr/share/Radiance/gtk2.0 folder https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1355137/+attachment/4300157/+files/Radiance_gtk-2.0.zip -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1355137 Title: gtk2 theme version improvements for high-dpi screens Status in ubuntu-themes package in Ubuntu: New Bug description: GTK2 applications are still widespread and the lack of resolution independence poses significant usability problems, for example for clicking radio buttons or checkboxes. By editing the gtkrc file one can at least mitigate a majority of issues. By doubling dimensions (like widths, heights, not border- widths), the following controls can be made usable: radio buttons, checkboxes, scrollbars, expand/collapse triangles in trees. While this is nothing like complete high-dpi support, still a significant partial improvement can be achieved. Users of high-dpi screens should not have to suffer under the current default, or have to patch the theme manually. It would be good to implement a way that when the scaling factor is = 2.0, as many GTK 2 widgets as possible are rendered with larger dimensions, be it by theme engine or by switching the theme. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1355137/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1374785] Re: Screen-saver fade-to-black does not cover entire screen on HiDPI
Is it planned for this to appear in the current release (utopic proposed), or is the only option to upgrade at this early stage already to 15.04? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1374785 Title: Screen-saver fade-to-black does not cover entire screen on HiDPI Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [ Impact ] When display scaling is set to 2x or greater the fade-to-black animation when the screen saver is invoked covers only a fraction of the screen. [ Test Case ] Requires a display with 2x UI scaling (works best with a high-DPI display). The fade-to-black which occurs prior to the screen shutting off only covers the top left quarter of the screen. When scaling is set to 1x, the entire screen fades to black. [ Regression Potential ] An invalid scaling calculation (or rounding error) could result in writing outside the screen buffer bounds with resulting unknown impact. Inpspection and code review shows this not to be the case wit this patch. [ Other Info ] The Ubuntu 14.04 LTS SRU was cherry-picked from upstream Unity where it has been in production use in Ubuntu 'Vivid Vervet' for some time and has not shown ergressions. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1374785/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1405926] [NEW] screen darkening does not work correctly on high-dpi screen
Public bug reported: When Control Center → Brightness and Lock → Darken the screen to save energy is set, the screen fades slowly into black after a certain time of inactivity. On a high-dpi screen, it fades only the upper left quarter of the screen and keeps the rest visible. The same is the case when a password is required or before and after stand-by, that means a view of the personal desktop is partly (3/4) exposed even before the owner types the password. (Apart from that it looks embarrassing.) ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 Uname: Linux 3.18.0-031800-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 BootLog: URfkill[517]: Starting urfkilld version 0.6.0 * Setting up X socket directories... [400G [394G[ OK ] CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Dec 27 11:09:30 2014 DistUpgraded: 2014-11-04 18:35:56,188 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.18, 3.16.0-25-generic, x86_64: installed virtualbox, 4.3.18, 3.16.0-28-generic, x86_64: installed virtualbox, 4.3.18, 3.18.0-031800-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3978] InstallationDate: Installed on 2014-02-02 (327 days ago) InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140201) MachineType: LENOVO 20266 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-031800-generic root=UUID=4bfb3686-b9f7-487d-81f6-eceb41097ad9 ro quiet splash acpi_backlight=vendor vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2014-11-04 (52 days ago) dmi.bios.date: 10/31/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN31WW 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:bvr76CN31WW:bd10/31/2013: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.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Fri Dec 26 19:39:15 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: [dix] ELAN Touchscreen: unable to find touch point 0 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16970 vendor SDC xserver.version: 2:1.16.0-1ubuntu1.2 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 third-party-packages ubuntu utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1405926 Title: screen darkening does not work correctly on high-dpi screen Status in unity package in Ubuntu: New Bug description: When Control Center → Brightness and Lock → Darken the screen to save energy is set, the screen fades slowly into black after a certain time of inactivity. On a high-dpi screen, it fades only the upper left quarter of the screen and keeps the rest visible. The same is the case when a password is required or before and after stand-by, that means a view of the personal desktop is partly (3/4) exposed even before the owner types the password. (Apart from that it looks embarrassing.) ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 Uname: Linux 3.18.0-031800-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 BootLog: URfkill[517]: Starting urfkilld version 0.6.0 * Setting up X socket directories... [400G [394G[ OK ] CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
[Touch-packages] [Bug 1301125] Re: Lock screen after idle time freezes unity
I was able to install compiz-core-dbgsym=1:0.9.12+14.10.20140918-0ubuntu1 and have been trying to do sudo gdb `pidof compiz` but it gives me (2380 is the pid of compiz): 2380: File or directory not found (gdb) bt full No stack. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1301125 Title: Lock screen after idle time freezes unity Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Hello, I recently upgrade to 14.04. My system uses fglrx provided by 14.04. When I lock manually the screen, I get no problem. I can even sleep the system without problem. However, when the screen is locked by idle time, I cannot unlock it. At this point, I can see the screen but with some kind of translucent panel over it. Mouse also works. I tried to type blink the password but I had no luck. I only get a working system by going text mode (ctrl+alt+f1) and restarting lightdm. No dmesg or Xorg logs seems to indicate any error. The only strange log was in .xsession-errors.old: init: processos unity-settings-daemon main (2495) terminados com status 1 init: processos gnome-session (Unity) main (2539) terminados com status 1 init: processos unity-panel-service main (2572) terminados com status 1 init: processos hud main (2536) terminados com status 1 init: processo indicator-powermain (2740) morto pelo sinal TERM init: processo indicator-datetimemain (2741) morto pelo sinal TERM init: processo indicator-soundmain (2747) morto pelo sinal TERM init: processo indicator-printersmain (2748) morto pelo sinal TERM init: processo indicator-sessionmain (2768) morto pelo sinal TERM init: processo indicator-syncmain (2795) morto pelo sinal TERM init: processo update-notifier-crash (/var/crash/_usr_bin_istanbul.1000.crash)main (4987) morto pelo sinal TERM init: processos unity-panel-service-lockscreen main (7447) terminados com status 1 init: Disconnected from notified D-Bus bus init: processos at-spi2-registryd main (2538) terminados com status 1 But as it has no time info, I cannot tell when they happened. At least another user faces the same problem: http://ubuntuforums.org/showthread.php?t=2214421 And this seems to be different from bug 1283938 as pm sleep/wake works as expected. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140328.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Apr 2 00:01:05 2014 DistUpgraded: 2014-03-31 21:24:46,145 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fglrx-updates, 13.350.1, 3.11.0-18-generic, x86_64: installed fglrx-updates, 13.350.1, 3.13.0-20-generic, x86_64: installed vboxhost, 4.3.10, 3.11.0-18-generic, x86_64: installed vboxhost, 4.3.10, 3.13.0-20-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] [1002:6758] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0012] InstallationDate: Installed on 2012-10-19 (529 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) JockeyStatus: kmod:wl - Broadcom STA wireless driver (Proprietário, Desativado, Não está em uso) [auto-install] kmod:fglrx - Video driver for the AMD graphics accelerators (Proprietário, Desativado, Não está em uso) kmod:fglrx_updates - ATI Fire GL (Proprietário, Habilitado, Não está em uso) MachineType: Dell Inc. XPS 8300 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic root=UUID=6633d579-d782-47ec-ad5a-22abac1412a0 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-04-01 (1 days ago) dmi.bios.date: 10/17/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0Y2MRG dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd10/17/2011:svnDellInc.:pnXPS8300:pvr:rvnDellInc.:rn0Y2MRG:rvrA01:cvnDellInc.:ct3:cvr: dmi.product.name: XPS 8300 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1
[Touch-packages] [Bug 1399900] [NEW] screen brightness cannot be changed anymore
Public bug reported: The screen brightness does not reliably respond to adjustments anymore since 14.10 release. Previously in 14.04 it was adjustable via a slider in Ubuntu Control Center and via the keyboard buttons (so there is driver and keyboard support for this laptop). Now the keyboard buttons as well as the slider have no effect and the brightness defaults to 100% which is on this device about five times brighter than the comfortable level, and strains the battery. However about 1 in 20 bootups/logins, the brightness is adjustable, but when I logout/login again in the user session, it might again become locked to 100%. I have the suspicion that it depends on the loading of desktop configs or the time I wait before typing my password to login. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Dec 6 12:20:50 2014 DistUpgraded: 2014-11-04 18:35:56,188 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.18, 3.16.0-24-generic, x86_64: installed virtualbox, 4.3.18, 3.16.0-25-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3978] InstallationDate: Installed on 2014-02-02 (306 days ago) InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140201) MachineType: LENOVO 20266 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic.efi.signed root=UUID=4bfb3686-b9f7-487d-81f6-eceb41097ad9 ro quiet splash acpi_backlight=vendor vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2014-11-04 (31 days ago) XorgConf: dmi.bios.date: 10/31/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN31WW 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:bvr76CN31WW:bd10/31/2013: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.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Sat Dec 6 12:19:59 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16970 vendor SDC xserver.version: 2:1.16.0-1ubuntu1 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 third-party-packages ubuntu utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1399900 Title: screen brightness cannot be changed anymore Status in unity package in Ubuntu: New Bug description: The screen brightness does not reliably respond to adjustments anymore since 14.10 release. Previously in 14.04 it was adjustable via a slider in Ubuntu Control Center and via the keyboard buttons (so there is driver and keyboard support for this laptop). Now the keyboard buttons as well as the slider have no effect and the brightness defaults to 100% which is on this device about five times brighter than the comfortable level, and strains the battery. However about 1 in 20 bootups/logins, the brightness is adjustable, but when I logout/login again in the user session, it might again become locked to 100%. I have the suspicion that it depends on the loading of desktop configs or the time I wait before typing my password to login. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1
[Touch-packages] [Bug 1399906] [NEW] guest session does not start with Xorg
Public bug reported: When choosing the guest session from the login screen, the screen freezes. `pidof Xorg` gives no running process of the x server. When being logged into a user account and switching to a guest session, it returns after some time to the lock screen of the logged in user. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sat Dec 6 12:51:14 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-02-02 (306 days ago) InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140201) SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2014-11-04 (31 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1399906 Title: guest session does not start with Xorg Status in unity package in Ubuntu: New Bug description: When choosing the guest session from the login screen, the screen freezes. `pidof Xorg` gives no running process of the x server. When being logged into a user account and switching to a guest session, it returns after some time to the lock screen of the logged in user. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sat Dec 6 12:51:14 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-02-02 (306 days ago) InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140201) SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2014-11-04 (31 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1399906/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1301125] Re: Lock screen after idle time freezes unity
Can you give the exact compiz debug package? compiz-dbg does not exist, and following the wiki instructions can also not find the package: sudo apt-get install compiz-dbgsym=1:0.9.12+14.10.20140918-0ubuntu1 This is a quite serious issue to me, is there no other way to close the lockscreen from tty without killing the session and all work? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1301125 Title: Lock screen after idle time freezes unity Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Hello, I recently upgrade to 14.04. My system uses fglrx provided by 14.04. When I lock manually the screen, I get no problem. I can even sleep the system without problem. However, when the screen is locked by idle time, I cannot unlock it. At this point, I can see the screen but with some kind of translucent panel over it. Mouse also works. I tried to type blink the password but I had no luck. I only get a working system by going text mode (ctrl+alt+f1) and restarting lightdm. No dmesg or Xorg logs seems to indicate any error. The only strange log was in .xsession-errors.old: init: processos unity-settings-daemon main (2495) terminados com status 1 init: processos gnome-session (Unity) main (2539) terminados com status 1 init: processos unity-panel-service main (2572) terminados com status 1 init: processos hud main (2536) terminados com status 1 init: processo indicator-powermain (2740) morto pelo sinal TERM init: processo indicator-datetimemain (2741) morto pelo sinal TERM init: processo indicator-soundmain (2747) morto pelo sinal TERM init: processo indicator-printersmain (2748) morto pelo sinal TERM init: processo indicator-sessionmain (2768) morto pelo sinal TERM init: processo indicator-syncmain (2795) morto pelo sinal TERM init: processo update-notifier-crash (/var/crash/_usr_bin_istanbul.1000.crash)main (4987) morto pelo sinal TERM init: processos unity-panel-service-lockscreen main (7447) terminados com status 1 init: Disconnected from notified D-Bus bus init: processos at-spi2-registryd main (2538) terminados com status 1 But as it has no time info, I cannot tell when they happened. At least another user faces the same problem: http://ubuntuforums.org/showthread.php?t=2214421 And this seems to be different from bug 1283938 as pm sleep/wake works as expected. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140328.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Apr 2 00:01:05 2014 DistUpgraded: 2014-03-31 21:24:46,145 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fglrx-updates, 13.350.1, 3.11.0-18-generic, x86_64: installed fglrx-updates, 13.350.1, 3.13.0-20-generic, x86_64: installed vboxhost, 4.3.10, 3.11.0-18-generic, x86_64: installed vboxhost, 4.3.10, 3.13.0-20-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] [1002:6758] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0012] InstallationDate: Installed on 2012-10-19 (529 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) JockeyStatus: kmod:wl - Broadcom STA wireless driver (Proprietário, Desativado, Não está em uso) [auto-install] kmod:fglrx - Video driver for the AMD graphics accelerators (Proprietário, Desativado, Não está em uso) kmod:fglrx_updates - ATI Fire GL (Proprietário, Habilitado, Não está em uso) MachineType: Dell Inc. XPS 8300 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic root=UUID=6633d579-d782-47ec-ad5a-22abac1412a0 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-04-01 (1 days ago) dmi.bios.date: 10/17/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0Y2MRG dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd10/17/2011:svnDellInc.:pnXPS8300:pvr:rvnDellInc.:rn0Y2MRG:rvrA01:cvnDellInc.:ct3:cvr: dmi.product.name: XPS 8300 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1 version.fglrx-installer:
[Touch-packages] [Bug 1398208] [NEW] unity fails to load after booting with high-dpi screen
Public bug reported: After booting, the first login attempt *always* loads Unity with incorrect/inconsistent scaling and many settings fail to load. The panel and window titlebars display correctly at 2× scaling, but the desktop icons (nautilus) and other application content is too small. The user interface font is too small and not the right font-family 'Ubuntu'. Fonts render with inconsistent kerning. The Unity Dash also shows the wrong font. Gtk2 themes don't load. After logging out and in again (sometimes 2 attempty necessary), all configurations load correctly. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Dec 1 23:52:51 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-02-02 (302 days ago) InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140201) SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2014-11-04 (27 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages utopic ** Attachment added: screenshot https://bugs.launchpad.net/bugs/1398208/+attachment/4272485/+files/unity-login-configs.jpg -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1398208 Title: unity fails to load after booting with high-dpi screen Status in unity package in Ubuntu: New Bug description: After booting, the first login attempt *always* loads Unity with incorrect/inconsistent scaling and many settings fail to load. The panel and window titlebars display correctly at 2× scaling, but the desktop icons (nautilus) and other application content is too small. The user interface font is too small and not the right font-family 'Ubuntu'. Fonts render with inconsistent kerning. The Unity Dash also shows the wrong font. Gtk2 themes don't load. After logging out and in again (sometimes 2 attempty necessary), all configurations load correctly. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Dec 1 23:52:51 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-02-02 (302 days ago) InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140201) SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2014-11-04 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1398208/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1301125] Re: Lock screen after idle time freezes unity
This started to happen for me occasionally after the upgrade to 14.10 (so it did not happen for me in 14.04). Either the lockscreen does not yet appear (and it shows a frozen buffer of the last view of the desktop), or it shows the lockscreen, but doesn't respond to keyboard (password input) or mouse clicks. Closing the laptop lid does not go back to stand-by but keeps the frozen screen on. I have to do ctrl+alt+f1 and restart the session. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1301125 Title: Lock screen after idle time freezes unity Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: Hello, I recently upgrade to 14.04. My system uses fglrx provided by 14.04. When I lock manually the screen, I get no problem. I can even sleep the system without problem. However, when the screen is locked by idle time, I cannot unlock it. At this point, I can see the screen but with some kind of translucent panel over it. Mouse also works. I tried to type blink the password but I had no luck. I only get a working system by going text mode (ctrl+alt+f1) and restarting lightdm. No dmesg or Xorg logs seems to indicate any error. The only strange log was in .xsession-errors.old: init: processos unity-settings-daemon main (2495) terminados com status 1 init: processos gnome-session (Unity) main (2539) terminados com status 1 init: processos unity-panel-service main (2572) terminados com status 1 init: processos hud main (2536) terminados com status 1 init: processo indicator-powermain (2740) morto pelo sinal TERM init: processo indicator-datetimemain (2741) morto pelo sinal TERM init: processo indicator-soundmain (2747) morto pelo sinal TERM init: processo indicator-printersmain (2748) morto pelo sinal TERM init: processo indicator-sessionmain (2768) morto pelo sinal TERM init: processo indicator-syncmain (2795) morto pelo sinal TERM init: processo update-notifier-crash (/var/crash/_usr_bin_istanbul.1000.crash)main (4987) morto pelo sinal TERM init: processos unity-panel-service-lockscreen main (7447) terminados com status 1 init: Disconnected from notified D-Bus bus init: processos at-spi2-registryd main (2538) terminados com status 1 But as it has no time info, I cannot tell when they happened. At least another user faces the same problem: http://ubuntuforums.org/showthread.php?t=2214421 And this seems to be different from bug 1283938 as pm sleep/wake works as expected. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140328.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Apr 2 00:01:05 2014 DistUpgraded: 2014-03-31 21:24:46,145 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fglrx-updates, 13.350.1, 3.11.0-18-generic, x86_64: installed fglrx-updates, 13.350.1, 3.13.0-20-generic, x86_64: installed vboxhost, 4.3.10, 3.11.0-18-generic, x86_64: installed vboxhost, 4.3.10, 3.13.0-20-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] [1002:6758] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0012] InstallationDate: Installed on 2012-10-19 (529 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) JockeyStatus: kmod:wl - Broadcom STA wireless driver (Proprietário, Desativado, Não está em uso) [auto-install] kmod:fglrx - Video driver for the AMD graphics accelerators (Proprietário, Desativado, Não está em uso) kmod:fglrx_updates - ATI Fire GL (Proprietário, Habilitado, Não está em uso) MachineType: Dell Inc. XPS 8300 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic root=UUID=6633d579-d782-47ec-ad5a-22abac1412a0 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-04-01 (1 days ago) dmi.bios.date: 10/17/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0Y2MRG dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd10/17/2011:svnDellInc.:pnXPS8300:pvr:rvnDellInc.:rn0Y2MRG:rvrA01:cvnDellInc.:ct3:cvr: dmi.product.name: XPS 8300
[Touch-packages] [Bug 1390625] Re: mouse cursor gets corrupted
** Description changed: In Ubuntu 14.10, the mouse cursor graphic gets corrupted under certain occasions. It then looks flipped, sheared or shows fragments of a - previews cursor. + previous cursor. * when switching the cursor them forth and back in Gnome Tweak Tool * when dragdropping a document icon Maybe related, the cursor does not always show the correct image scale on a high-dpi display (this was working right in 14.04). For example after login, or when hovering specific areas, or on mouse down to start a dragdrop, the cursor appears 1/4 the expected size. Attached is a photo of a corrupted cursor (whereas a screenshot with Gimp showed the uncorrupted cursor). ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 .tmp.unity.support.test.0: - + ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 BootLog: - * Setting up X socket directories... [400G + * Setting up X socket directories... [400G [394G[ OK ] CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Nov 7 22:12:52 2014 DistUpgraded: 2014-11-04 18:35:56,188 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: - Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) -Subsystem: Lenovo Device [17aa:3978] + Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) + Subsystem: Lenovo Device [17aa:3978] InstallationDate: Installed on 2014-02-02 (278 days ago) InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140201) MachineType: LENOVO 20266 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed root=UUID=4bfb3686-b9f7-487d-81f6-eceb41097ad9 ro quiet splash acpi_backlight=vendor SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2014-11-04 (3 days ago) dmi.bios.date: 10/31/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN31WW 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:bvr76CN31WW:bd10/31/2013: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.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Fri Nov 7 14:54:59 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: [dix] ELAN Touchscreen: unable to find touch point 1 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: - product id 16970 - vendor SDC + product id 16970 + vendor SDC xserver.version: 2:1.16.0-1ubuntu1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1390625 Title: mouse cursor gets corrupted Status in “unity” package in Ubuntu: Confirmed Bug description: In Ubuntu 14.10, the mouse cursor graphic gets corrupted under certain occasions. It then looks flipped, sheared or shows fragments of a previous cursor. * when switching the cursor them forth and back in Gnome Tweak Tool * when dragdropping a document icon Maybe related, the cursor does not always show the correct image scale on a high-dpi display (this was working right in 14.04). For example after login, or when hovering specific areas, or on mouse down to start a dragdrop, the cursor appears 1/4 the expected size. Attached is a photo of a corrupted cursor (whereas a screenshot with Gimp showed the uncorrupted cursor). ProblemType: Bug
[Touch-packages] [Bug 1390625] [NEW] mouse cursor gets corrupted
Public bug reported: In Ubuntu 14.10, the mouse cursor graphic gets corrupted under certain occasions. It then looks flipped, sheared or shows fragments of a previews cursor. * when switching the cursor them forth and back in Gnome Tweak Tool * when dragdropping a document icon Maybe related, the cursor does not always show the correct image scale on a high-dpi display (this was working right in 14.04). For example after login, or when hovering specific areas, or on mouse down to start a dragdrop, the cursor appears 1/4 the expected size. Attached is a photo of a corrupted cursor (whereas a screenshot with Gimp showed the uncorrupted cursor). ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 BootLog: * Setting up X socket directories... [400G [394G[ OK ] CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Nov 7 22:12:52 2014 DistUpgraded: 2014-11-04 18:35:56,188 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3978] InstallationDate: Installed on 2014-02-02 (278 days ago) InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140201) MachineType: LENOVO 20266 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed root=UUID=4bfb3686-b9f7-487d-81f6-eceb41097ad9 ro quiet splash acpi_backlight=vendor SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2014-11-04 (3 days ago) dmi.bios.date: 10/31/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN31WW 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:bvr76CN31WW:bd10/31/2013: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.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Fri Nov 7 14:54:59 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: [dix] ELAN Touchscreen: unable to find touch point 1 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16970 vendor SDC xserver.version: 2:1.16.0-1ubuntu1 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 third-party-packages ubuntu utopic ** Attachment added: photo of a corrupted cursor https://bugs.launchpad.net/bugs/1390625/+attachment/4255470/+files/20141107_171621.jpg -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1390625 Title: mouse cursor gets corrupted Status in “unity” package in Ubuntu: New Bug description: In Ubuntu 14.10, the mouse cursor graphic gets corrupted under certain occasions. It then looks flipped, sheared or shows fragments of a previews cursor. * when switching the cursor them forth and back in Gnome Tweak Tool * when dragdropping a document icon Maybe related, the cursor does not always show the correct image scale on a high-dpi display (this was working right in 14.04). For example after login, or when hovering specific areas, or on mouse down to start a dragdrop, the cursor appears 1/4 the expected size. Attached is a photo of a corrupted cursor (whereas a screenshot with Gimp showed the uncorrupted cursor). ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 .tmp.unity.support.test.0:
[Touch-packages] [Bug 1299054] Re: resizing loop on high-dpi screen
This does still occurs frequently in Ubuntu 14.10 official release with Unity 7.3.1+14.10.20141016-0ubuntu1. Some application windows freeze and shrink slowly for 10-30 seconds while turning the cpu up to 100%. When these windows have reached the smallest possible size, they remain unusable. When trying to resize them to a usable size, they continue freezing and shrinking. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1299054 Title: resizing loop on high-dpi screen Status in Unity: New Status in “unity” package in Ubuntu: New Bug description: When the global scaling factor is set to 2, some dialogs occasionally start changing their window size causing very high CPU activity. This occurs for example in dconf-editor while searching: It appears dconf-editor tries to adjust the window dimensions to the size of the content and reduces the window size until it is unusable. This causes very high CPU activity and freezes the window content. It also happens when (then) resizing the window width (→) or height (↓) afterwards, it tries to revert to the previous window size. However, the only way to resize the window back so that it doesn't reduce its size is by dragging the window corner (↓→). This issue happens also in other applications, for example in apport- dialogs when expanding the collapsed details view. This does not happen when the global scaling factor is set to 1. It could be related to the new window resizing method that updates the window content. org.gnome.desktop.interface.scaling-factor = 2 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140321-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Mar 28 16:07:47 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-02-02 (53 days ago) InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140201) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1299054/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1072191] Re: Preview ignores EXIF Orientation tag for jpegs
Still an issue in 14.04 / Unity 7.2.3 For me all thumbnails in the dash (in both file and photo lense) have the correct orientation, only when clicking on an item to open the larger preview, the preview has wrong orientation. See the attached screenshot. ** Attachment added: screenshot of preview (wrong orientation) and thumbnail (right orientation) https://bugs.launchpad.net/unity/+bug/1072191/+attachment/4231870/+files/dash-preview-orientation.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1072191 Title: Preview ignores EXIF Orientation tag for jpegs Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: Ubuntu 12.10 (quantal), Unity 6.8.0-0ubuntu2 Many (most?) cameras detect when a photo was taken while the camera was rotated, and store this in the JPEG EXIF Orientation tag. The preview view does not check the Orientation tag so many photographs, typically those in portrait format, are not rotated correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1072191/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1283415] Re: 1px gap between launcher and dash on high-dpi screen
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1283415 Title: 1px gap between launcher and dash on high-dpi screen Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Trusty: Fix Committed Bug description: [Impact] When desktop scaling is enabled, there is a 1px gap between the launcher and the dash. org.gnome.desktop.interface.scaling-factor = 2 org.gnome.desktop.interface.text-scaling-factor = 1.0 [Test case] 1. From Unity Control Center - Displays - Change the monitor scaling to a value bigger than 1.5 (best at 2.0 or more) 2. Open the dash 3. There should be no fully transparent gab between dash and launcher (as shown in this image https://launchpadlibrarian.net/167262841/unity-dash-dpi.png [Regression Potential] Nothing known, dash borders might be distorted ProblemType: BugDistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140220-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Feb 22 12:41:11 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.6, 3.13.0-11-generic, x86_64: installed virtualbox, 4.3.6, 3.13.0-8-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3978] InstallationDate: Installed on 2014-02-02 (19 days ago) InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140201) MachineType: LENOVO 20266 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-11-generic.efi.signed root=UUID=4bfb3686-b9f7-487d-81f6-eceb41097ad9 ro quiet splash vt.handoff=7SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/31/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN31WW 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:bvr76CN31WW:bd10/31/2013: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+14.04.20140218-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc1-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0~rc1-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu6 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-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sat Feb 22 12:08:14 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.0-1ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1283415/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1299054] Re: resizing loop on high-dpi screen
Does nobody else experience this, or does nobody else have a high resolution device for being able to experience it? I get this issue also in the daily utopic unicorn (28.7.) with Unity 7.3. I believe it is due to some flexible box gtk component, but I don't have enough technical knowledge for a better guess. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1299054 Title: resizing loop on high-dpi screen Status in Unity: New Status in “unity” package in Ubuntu: New Bug description: When the global scaling factor is set to 2, some dialogs occasionally start changing their window size causing very high CPU activity. This occurs for example in dconf-editor while searching: It appears dconf-editor tries to adjust the window dimensions to the size of the content and reduces the window size until it is unusable. This causes very high CPU activity and freezes the window content. It also happens when (then) resizing the window width (→) or height (↓) afterwards, it tries to revert to the previous window size. However, the only way to resize the window back so that it doesn't reduce its size is by dragging the window corner (↓→). This issue happens also in other applications, for example in apport- dialogs when expanding the collapsed details view. This does not happen when the global scaling factor is set to 1. It could be related to the new window resizing method that updates the window content. org.gnome.desktop.interface.scaling-factor = 2 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140321-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Mar 28 16:07:47 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-02-02 (53 days ago) InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140201) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1299054/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351591] [NEW] menus on wrong monitor in multi-monitor layout with scaling
Public bug reported: The panel menus (from network to system) open on the wrong display in a multi monitor setup under the following circumstances: * left display has UI scaling 2.0 * right display has UI scaling 1.0 * menu is clicked on the left display The menu flies out on the right display although it was clicked on the left one. This does not happen when the non-scaled display is on the left, or when the menu is clicked on the right display. ubuntu: utopic unicorn (daily from 28.7) unity: 7.3 tested in VirtualBox ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Attachment added: screenshot of the situation https://bugs.launchpad.net/bugs/1351591/+attachment/4167956/+files/menus-multi-monitor-with-scaling.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1351591 Title: menus on wrong monitor in multi-monitor layout with scaling Status in “unity” package in Ubuntu: New Bug description: The panel menus (from network to system) open on the wrong display in a multi monitor setup under the following circumstances: * left display has UI scaling 2.0 * right display has UI scaling 1.0 * menu is clicked on the left display The menu flies out on the right display although it was clicked on the left one. This does not happen when the non-scaled display is on the left, or when the menu is clicked on the right display. ubuntu: utopic unicorn (daily from 28.7) unity: 7.3 tested in VirtualBox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1351591/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1349376] [NEW] vector graphic thumbnails blurry in dash on high-dpi screen
Public bug reported: Thumbnails used in the dash are blurry for small svg images. In contrast to that the previews in the dash are specifically rendered for the dash and show in correct resolution. Nautilus is setup to display icons in 100% zoom level (default). In Nautilus or on the desktop, svg thumbnails of 24×24px svg images are smaller than the maximum available thumbnail area and are displayed in screen pixels (which is very tiny, could also be a bug). It appears the Unity dash looks up if a thumbnail exists for a specific file in ~/.cache/thumbnails/normal, chooses that thumbnail and stretches it to the maximum available thumbnail area in the dash. This makes vector graphics appear like they where raster graphics and look very blurry. Ubuntu: 14.04 unity: 7.2.2+14.04. amd64 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Attachment added: screenshot of the thumbnail as shown in the dash (behind: the desktop with the same file) https://bugs.launchpad.net/bugs/1349376/+attachment/4164278/+files/unity-hidpi-thumbnail-dash.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1349376 Title: vector graphic thumbnails blurry in dash on high-dpi screen Status in “unity” package in Ubuntu: New Bug description: Thumbnails used in the dash are blurry for small svg images. In contrast to that the previews in the dash are specifically rendered for the dash and show in correct resolution. Nautilus is setup to display icons in 100% zoom level (default). In Nautilus or on the desktop, svg thumbnails of 24×24px svg images are smaller than the maximum available thumbnail area and are displayed in screen pixels (which is very tiny, could also be a bug). It appears the Unity dash looks up if a thumbnail exists for a specific file in ~/.cache/thumbnails/normal, chooses that thumbnail and stretches it to the maximum available thumbnail area in the dash. This makes vector graphics appear like they where raster graphics and look very blurry. Ubuntu: 14.04 unity: 7.2.2+14.04. amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1349376/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1349376] Re: vector graphic thumbnails blurry in dash on high-dpi screen
** Attachment added: same file as shown in Nautilus and on the desktop https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1349376/+attachment/4164279/+files/unity-hidpi-thumbnail-desktop.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1349376 Title: vector graphic thumbnails blurry in dash on high-dpi screen Status in “unity” package in Ubuntu: New Bug description: Thumbnails used in the dash are blurry for small svg images. In contrast to that the previews in the dash are specifically rendered for the dash and show in correct resolution. Nautilus is setup to display icons in 100% zoom level (default). In Nautilus or on the desktop, svg thumbnails of 24×24px svg images are smaller than the maximum available thumbnail area and are displayed in screen pixels (which is very tiny, could also be a bug). It appears the Unity dash looks up if a thumbnail exists for a specific file in ~/.cache/thumbnails/normal, chooses that thumbnail and stretches it to the maximum available thumbnail area in the dash. This makes vector graphics appear like they where raster graphics and look very blurry. Ubuntu: 14.04 unity: 7.2.2+14.04. amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1349376/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1348101] [NEW] system dialogs lost by showing desktop
Public bug reported: By system dialog I mean an error popup after booting (apport?) or a dialog about low battery power or required reboot etc., that is not attached to an application and has no distinct icon in the launcher. When a system dialog opens, and you show the desktop, all windows are hidden. You can then use Super+W, Alt+Tab or Show desktop again to access all other windows that belong to applications, but the system dialogs remain inaccessible. Either system dialogs should be associated with an icon in the launcher or Alt+Tab, or at least the window overview Super+W should show all windows, including those not belonging to an application. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.1+14.04.20140513-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Jul 24 11:15:08 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10, 3.13.0-29-generic, x86_64: installed virtualbox, 4.3.10, 3.13.0-30-generic, x86_64: installed virtualbox, 4.3.10, 3.13.0-32-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3978] InstallationDate: Installed on 2014-02-02 (171 days ago) InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140201) MachineType: LENOVO 20266 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic.efi.signed root=UUID=4bfb3686-b9f7-487d-81f6-eceb41097ad9 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/31/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN31WW 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:bvr76CN31WW:bd10/31/2013: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.1+14.04.20140701-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.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 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 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Thu Jul 24 09:49:51 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 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 gnome3-ppa third-party-packages trusty ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1348101 Title: system dialogs lost by showing desktop Status in “unity” package in Ubuntu: New Bug description: By system dialog I mean an error popup after booting (apport?) or a dialog about low battery power or required reboot etc., that is not attached to an application and has no distinct icon in the launcher. When a system dialog opens, and you show the desktop, all windows are hidden. You can then use Super+W, Alt+Tab or Show desktop again to access all other windows that belong to applications, but the system dialogs remain inaccessible. Either system dialogs should be associated with an icon in the launcher or Alt+Tab, or at least the window overview Super+W should show all windows, including those not belonging to an application. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.1+14.04.20140513-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: No value set for
