[Touch-packages] [Bug 1797717] Re: fstrim -av tries to trim read only mounted ntfs-3g and fails
** Tags added: eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1797717 Title: fstrim -av tries to trim read only mounted ntfs-3g and fails Status in util-linux package in Ubuntu: Confirmed Bug description: If I run sudo fstrim -av I see: /media/SSD_Data: 2 GiB (2145820672 bytes) trimmed fstrim: /media/Win7: FITRIM ioctl failed: Bad file descriptor /: 26.9 GiB (28823887872 bytes) trimmed /media/SSD_Data is read-write mounted NTFS via ntfs-3g, and /media/Win7 is read-only mounted NTFS, also via ntfs-3g. Lines from fstab: UUID=censored /media/SSD_Data ntfs-3g rw,noatime,nofail,big_writes,windows_names,nosuid,nodev,allow_other,hide_hid_files,inherit,noexec 0 0 UUID=censored /media/Win7 ntfs-3g ro,nofail,big_writes,windows_names,nosuid,nodev,allow_other,noexec,hide_hid_files 0 0 If I do sudo umount /media/Win7 and then sudo mount -o rw /media/Win7 then sudo fstrim -av takes longer and succeeds for all filesystems. So, it seems the read only is the problem. This seems cosmetic, but it causes periodic runs of fstrim via systemd to report failures. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: util-linux 2.32-0.1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Oct 13 15:25:41 2018 SourcePackage: util-linux UpgradeStatus: Upgraded to cosmic on 2018-10-11 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1797717/+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 1797717] Re: fstrim -av tries to trim read only mounted ntfs-3g and fails
** Tags added: disco -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1797717 Title: fstrim -av tries to trim read only mounted ntfs-3g and fails Status in util-linux package in Ubuntu: Confirmed Bug description: If I run sudo fstrim -av I see: /media/SSD_Data: 2 GiB (2145820672 bytes) trimmed fstrim: /media/Win7: FITRIM ioctl failed: Bad file descriptor /: 26.9 GiB (28823887872 bytes) trimmed /media/SSD_Data is read-write mounted NTFS via ntfs-3g, and /media/Win7 is read-only mounted NTFS, also via ntfs-3g. Lines from fstab: UUID=censored /media/SSD_Data ntfs-3g rw,noatime,nofail,big_writes,windows_names,nosuid,nodev,allow_other,hide_hid_files,inherit,noexec 0 0 UUID=censored /media/Win7 ntfs-3g ro,nofail,big_writes,windows_names,nosuid,nodev,allow_other,noexec,hide_hid_files 0 0 If I do sudo umount /media/Win7 and then sudo mount -o rw /media/Win7 then sudo fstrim -av takes longer and succeeds for all filesystems. So, it seems the read only is the problem. This seems cosmetic, but it causes periodic runs of fstrim via systemd to report failures. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: util-linux 2.32-0.1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Oct 13 15:25:41 2018 SourcePackage: util-linux UpgradeStatus: Upgraded to cosmic on 2018-10-11 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1797717/+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 1797717] Re: fstrim -av tries to trim read only mounted ntfs-3g and fails
I see the same warnings in systemd log. systemd[1]: fstrim.service: Main process exited, code=exited, status=64/USAGE systemd[1]: fstrim.service: Failed with result 'exit-code'. systemd[1]: Failed to start Discard unused blocks. If I run it manually: $ sudo fstrim -av /home: 9.7 GiB (10445021184 bytes) trimmed fstrim: /mnt/win_c: FITRIM ioctl failed: Bad file descriptor fstrim: /mnt/win_d: FITRIM ioctl failed: Bad file descriptor fstrim: /mnt/win_g: FITRIM ioctl failed: Bad file descriptor fstrim: /mnt/win_e: FITRIM ioctl failed: Bad file descriptor fstrim: /mnt/win_f: FITRIM ioctl failed: Bad file descriptor fstrim: /mnt/win_re: FITRIM ioctl failed: Bad file descriptor /: 2.4 GiB (2608013312 bytes) trimmed with exit status 64. Related mount points: $ mount | grep win /dev/sda4 on /mnt/win_re type fuseblk (ro,noatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096) /dev/sdc1 on /mnt/win_f type fuseblk (ro,noatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096) /dev/sdb1 on /mnt/win_e type fuseblk (ro,noatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096) /dev/sdd1 on /mnt/win_g type fuseblk (ro,noatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096) /dev/sda5 on /mnt/win_d type fuseblk (ro,noatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096) /dev/sda3 on /mnt/win_c type fuseblk (ro,noatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096) /dev/sde1 on /mnt/win_h type fuseblk (ro,noatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1797717 Title: fstrim -av tries to trim read only mounted ntfs-3g and fails Status in util-linux package in Ubuntu: Confirmed Bug description: If I run sudo fstrim -av I see: /media/SSD_Data: 2 GiB (2145820672 bytes) trimmed fstrim: /media/Win7: FITRIM ioctl failed: Bad file descriptor /: 26.9 GiB (28823887872 bytes) trimmed /media/SSD_Data is read-write mounted NTFS via ntfs-3g, and /media/Win7 is read-only mounted NTFS, also via ntfs-3g. Lines from fstab: UUID=censored /media/SSD_Data ntfs-3g rw,noatime,nofail,big_writes,windows_names,nosuid,nodev,allow_other,hide_hid_files,inherit,noexec 0 0 UUID=censored /media/Win7 ntfs-3g ro,nofail,big_writes,windows_names,nosuid,nodev,allow_other,noexec,hide_hid_files 0 0 If I do sudo umount /media/Win7 and then sudo mount -o rw /media/Win7 then sudo fstrim -av takes longer and succeeds for all filesystems. So, it seems the read only is the problem. This seems cosmetic, but it causes periodic runs of fstrim via systemd to report failures. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: util-linux 2.32-0.1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Oct 13 15:25:41 2018 SourcePackage: util-linux UpgradeStatus: Upgraded to cosmic on 2018-10-11 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1797717/+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 1556457] Re: [FFe] Demilight (OS/2 weight=350) confuses fontconfig
Gunnar, could you please check https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1566651 I believe it's related to this fontconfig update. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1556457 Title: [FFe] Demilight (OS/2 weight=350) confuses fontconfig Status in Fontconfig: Fix Released Status in fontconfig package in Ubuntu: Fix Released Status in fontconfig package in Debian: Unknown Bug description: [FFe request comment] Upgrading to fontconfig 2.11.94 is proposed as a fix of this bug, including a fix of certain font weight issues due to the switch from fonts-droid to fonts-noto-cjk for Chinese (discussed at bug #1468027) where we haven't found any way to work around the problem. The proposed upload is available in this PPA: https://launchpad.net/~gunnarhj/+archive/ubuntu/fontconfig-test2 Changes are listed in the attachment upstream_git-log.txt [Original description including updates] See https://bugs.freedesktop.org/show_bug.cgi?id=81453 and bug 1468027. Fontconfig lacks support for many OpenType/TrueType OS/2 font weight values. This causes a bunch of problems, like mixing up Demilight (weight=350) and Regular (weight=400). Although it's possible to write (dirty?) hacks for deb-packed fonts, this still causes problems for otherwise sourced fonts. Archlinux: https://bugs.archlinux.org/task/48550 (fix released, upgraded to 2.11.94) To manage notifications about this bug go to: https://bugs.launchpad.net/fontconfig/+bug/1556457/+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 1566651] Re: Blurry fonts after update to fontconfig 2.11.1-0ubuntu9
** Description changed: I use terminus font in gnome-terminal. After upgrade to the latest fonconfig in xenial my terminal font is blurry. Versions which work as expected: <= 2.11.1-0ubuntu8 Broken versions: >= 2.11.1-0ubuntu9 Screenshots attached. Probably related to this change https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1556457 + + Rollback to the following packages fixes this issue: + + fontconfig_2.11.1-0ubuntu8_amd64.deb + fontconfig-config_2.11.1-0ubuntu8_all.deb + libfontconfig1_2.11.1-0ubuntu8_amd64.deb -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1566651 Title: Blurry fonts after update to fontconfig 2.11.1-0ubuntu9 Status in fontconfig package in Ubuntu: New Bug description: I use terminus font in gnome-terminal. After upgrade to the latest fonconfig in xenial my terminal font is blurry. Versions which work as expected: <= 2.11.1-0ubuntu8 Broken versions: >= 2.11.1-0ubuntu9 Screenshots attached. Probably related to this change https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1556457 Rollback to the following packages fixes this issue: fontconfig_2.11.1-0ubuntu8_amd64.deb fontconfig-config_2.11.1-0ubuntu8_all.deb libfontconfig1_2.11.1-0ubuntu8_amd64.deb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1566651/+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 1566651] Re: Blurry fonts after update to fontconfig 2.11.1-0ubuntu9
** Attachment added: "fontconfig 2.11.1-0ubuntu9" https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1566651/+attachment/4625619/+files/fontconfig_new.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1566651 Title: Blurry fonts after update to fontconfig 2.11.1-0ubuntu9 Status in fontconfig package in Ubuntu: New Bug description: I use terminus font in gnome-terminal. After upgrade to the latest fonconfig in xenial my terminal font is blurry. Versions which work as expected: <= 2.11.1-0ubuntu8 Broken versions: >= 2.11.1-0ubuntu9 Screenshots attached. Probably related to this change https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1556457 Rollback to the following packages fixes this issue: fontconfig_2.11.1-0ubuntu8_amd64.deb fontconfig-config_2.11.1-0ubuntu8_all.deb libfontconfig1_2.11.1-0ubuntu8_amd64.deb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1566651/+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 1566651] [NEW] Blurry fonts after update to fontconfig 2.11.1-0ubuntu9
Public bug reported: I use terminus font in gnome-terminal. After upgrade to the latest fonconfig in xenial my terminal font is blurry. Versions which work as expected: <= 2.11.1-0ubuntu8 Broken versions: >= 2.11.1-0ubuntu9 Screenshots attached. Probably related to this change https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1556457 Rollback to the following packages fixes this issue: fontconfig_2.11.1-0ubuntu8_amd64.deb fontconfig-config_2.11.1-0ubuntu8_all.deb libfontconfig1_2.11.1-0ubuntu8_amd64.deb ** Affects: fontconfig (Ubuntu) Importance: Undecided Status: New ** Tags: xenial ** Attachment added: "fontconfig_old.png" https://bugs.launchpad.net/bugs/1566651/+attachment/4625618/+files/fontconfig_old.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1566651 Title: Blurry fonts after update to fontconfig 2.11.1-0ubuntu9 Status in fontconfig package in Ubuntu: New Bug description: I use terminus font in gnome-terminal. After upgrade to the latest fonconfig in xenial my terminal font is blurry. Versions which work as expected: <= 2.11.1-0ubuntu8 Broken versions: >= 2.11.1-0ubuntu9 Screenshots attached. Probably related to this change https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1556457 Rollback to the following packages fixes this issue: fontconfig_2.11.1-0ubuntu8_amd64.deb fontconfig-config_2.11.1-0ubuntu8_all.deb libfontconfig1_2.11.1-0ubuntu8_amd64.deb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1566651/+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 1226962] Re: Hotkeys not functional in non-latin keyboard layout
@attente works on vivid with super+space switching. -- 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/1226962 Title: Hotkeys not functional in non-latin keyboard layout Status in aptana-studio-installer: New Status in Default settings and artwork for Baltix OS: New Status in LibreOffice Productivity Suite: Fix Released Status in ibus: New Status in Indicator keyboard: Fix Released Status in Inkscape: New Status in monodevelop: New Status in mutter: Fix Released Status in okular: New Status in OpenOffice: New Status in sigram: New Status in Unity: Fix Released Status in gnome-settings-daemon package in Ubuntu: Triaged Status in gnome-terminal package in Ubuntu: Triaged Status in openjdk-7 package in Ubuntu: Incomplete Status in unity package in Ubuntu: Triaged Status in unity-settings-daemon package in Ubuntu: Triaged Status in gnome-shell package in Fedora: Unknown Status in openoffice package in Fedora: Unknown Bug description: New keyboard layout changer in Ubuntu 13.10 introduce old-new bug. Any system or application hotkey witch use char (for example: ctrl+alt+t for terminal or ctrl+t for new tab in browser) become unfunctional when selected non-latin keyboard layout. Hotkeys with F1-12, numbers and other non-character buttons works perfectly. Window manager hotkeys not affected by this bug. All hotkeys in system parameters->keyboard->hotkeys->windows works perfect with any keyboard layout. Workaround for some system hotkeys and two layouts (english and non- latin): rebind all hotkeys in your local layout. For example instead of ctrl+alt+t use ctrl+alt+τ (greek tau). That hotkey still work with english layout. If you use english and two different non-latin layouts this workaround helps only with one of them. Dear Ubuntu users and developers! Please include the following information to your comment about non-latin shortcuts problems: 1. What Ubuntu version do you have (Ubuntu 13.10, Ubuntu 13.10 GNOME, Ubuntu 14.04, Ubuntu 14.04 GNOME and so on), upgraded (describe version) or clean installed 2. What keyboard layout do you have 3. What shortcut for keyboard layout switching do you use 4. On which session you have problems - that is one from Unity, GNOME Shell, GNOME FlashBack/Fallback (Metacity), GNOME FlashBack/Fallback (Compiz) 5. With which program and its version and origin (Ubuntu repositories, PPA, non-deb binary package from some website) you have problems. By providing this information you can make bug-fixing much simpler and may be faster. -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- To manage notifications about this bug go to: https://bugs.launchpad.net/aptana-studio-installer/+bug/1226962/+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 1226962] Re: Hotkeys not functional in non-latin keyboard layout
@zoltor I see issue with Super+A/F/M/C/V starting from 13.10 or 14.04 (don't remember). Some Super+* hotkeys are working, for example Super+W. Also this bug exists even if I boot from live USB so it's clearly not my user profile issue. @Roman sadly but with your patch keyboard behavior is unpredictable. Sometimes it works well w/o this bug, but sometimes I can't even switch keyboard layout. Looks like sort of racing somewhere. -- 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/1226962 Title: Hotkeys not functional in non-latin keyboard layout Status in aptana-studio-installer: New Status in Default settings and artwork for Baltix OS: New Status in LibreOffice Productivity Suite: Fix Released Status in ibus: New Status in Indicator keyboard: Fix Released Status in Inkscape: New Status in monodevelop: New Status in mutter: Fix Released Status in okular: New Status in OpenOffice: New Status in sigram: New Status in Unity: Fix Released Status in gnome-settings-daemon package in Ubuntu: Triaged Status in gnome-terminal package in Ubuntu: Triaged Status in openjdk-7 package in Ubuntu: Incomplete Status in unity package in Ubuntu: Triaged Status in unity-settings-daemon package in Ubuntu: Triaged Status in gnome-settings-daemon package in Fedora: Unknown Status in gnome-shell package in Fedora: Unknown Bug description: New keyboard layout changer in Ubuntu 13.10 introduce old-new bug. Any system or application hotkey witch use char (for example: ctrl+alt+t for terminal or ctrl+t for new tab in browser) become unfunctional when selected non-latin keyboard layout. Hotkeys with F1-12, numbers and other non-character buttons works perfectly. Window manager hotkeys not affected by this bug. All hotkeys in system parameters->keyboard->hotkeys->windows works perfect with any keyboard layout. Workaround for some system hotkeys and two layouts (english and non- latin): rebind all hotkeys in your local layout. For example instead of ctrl+alt+t use ctrl+alt+τ (greek tau). That hotkey still work with english layout. If you use english and two different non-latin layouts this workaround helps only with one of them. Dear Ubuntu users and developers! Please include the following information to your comment about non-latin shortcuts problems: 1. What Ubuntu version do you have (Ubuntu 13.10, Ubuntu 13.10 GNOME, Ubuntu 14.04, Ubuntu 14.04 GNOME and so on), upgraded (describe version) or clean installed 2. What keyboard layout do you have 3. What shortcut for keyboard layout switching do you use 4. On which session you have problems - that is one from Unity, GNOME Shell, GNOME FlashBack/Fallback (Metacity), GNOME FlashBack/Fallback (Compiz) 5. With which program and its version and origin (Ubuntu repositories, PPA, non-deb binary package from some website) you have problems. By providing this information you can make bug-fixing much simpler and may be faster. -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- To manage notifications about this bug go to: https://bugs.launchpad.net/aptana-studio-installer/+bug/1226962/+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 1226962] Re: Hotkeys not functional in non-latin keyboard layout
@Roman that could be the difference since I'm on Vivid x64 and using Unity. -- 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/1226962 Title: Hotkeys not functional in non-latin keyboard layout Status in aptana-studio-installer: New Status in Default settings and artwork for Baltix OS: New Status in LibreOffice Productivity Suite: Fix Released Status in ibus: New Status in Indicator keyboard: Fix Released Status in Inkscape: New Status in monodevelop: New Status in mutter: Fix Released Status in okular: New Status in OpenOffice: New Status in sigram: New Status in Unity: Fix Released Status in gnome-settings-daemon package in Ubuntu: Triaged Status in gnome-terminal package in Ubuntu: Triaged Status in openjdk-7 package in Ubuntu: Incomplete Status in unity package in Ubuntu: Triaged Status in unity-settings-daemon package in Ubuntu: Triaged Status in gnome-settings-daemon package in Fedora: Unknown Status in gnome-shell package in Fedora: Unknown Bug description: New keyboard layout changer in Ubuntu 13.10 introduce old-new bug. Any system or application hotkey witch use char (for example: ctrl+alt+t for terminal or ctrl+t for new tab in browser) become unfunctional when selected non-latin keyboard layout. Hotkeys with F1-12, numbers and other non-character buttons works perfectly. Window manager hotkeys not affected by this bug. All hotkeys in system parameters->keyboard->hotkeys->windows works perfect with any keyboard layout. Workaround for some system hotkeys and two layouts (english and non- latin): rebind all hotkeys in your local layout. For example instead of ctrl+alt+t use ctrl+alt+τ (greek tau). That hotkey still work with english layout. If you use english and two different non-latin layouts this workaround helps only with one of them. Dear Ubuntu users and developers! Please include the following information to your comment about non-latin shortcuts problems: 1. What Ubuntu version do you have (Ubuntu 13.10, Ubuntu 13.10 GNOME, Ubuntu 14.04, Ubuntu 14.04 GNOME and so on), upgraded (describe version) or clean installed 2. What keyboard layout do you have 3. What shortcut for keyboard layout switching do you use 4. On which session you have problems - that is one from Unity, GNOME Shell, GNOME FlashBack/Fallback (Metacity), GNOME FlashBack/Fallback (Compiz) 5. With which program and its version and origin (Ubuntu repositories, PPA, non-deb binary package from some website) you have problems. By providing this information you can make bug-fixing much simpler and may be faster. -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- To manage notifications about this bug go to: https://bugs.launchpad.net/aptana-studio-installer/+bug/1226962/+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 1226962] Re: Hotkeys not functional in non-latin keyboard layout
@Roman thank you, your patch is working. At least it fixes Super+A/F/M/C/V. Not sure about all other issues with openjdk/libreoffice/etc. For people who want fixed version for vivid: https://launchpad.net /~xeron-oskom/+archive/ubuntu/unity-settings-daemon/ -- 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/1226962 Title: Hotkeys not functional in non-latin keyboard layout Status in aptana-studio-installer: New Status in Default settings and artwork for Baltix OS: New Status in LibreOffice Productivity Suite: Fix Released Status in ibus: New Status in Indicator keyboard: Fix Released Status in Inkscape: New Status in monodevelop: New Status in mutter: Fix Released Status in okular: New Status in OpenOffice: New Status in sigram: New Status in Unity: Fix Released Status in gnome-settings-daemon package in Ubuntu: Triaged Status in gnome-terminal package in Ubuntu: Triaged Status in openjdk-7 package in Ubuntu: Incomplete Status in unity package in Ubuntu: Triaged Status in unity-settings-daemon package in Ubuntu: Triaged Status in gnome-settings-daemon package in Fedora: Unknown Status in gnome-shell package in Fedora: Unknown Bug description: New keyboard layout changer in Ubuntu 13.10 introduce old-new bug. Any system or application hotkey witch use char (for example: ctrl+alt+t for terminal or ctrl+t for new tab in browser) become unfunctional when selected non-latin keyboard layout. Hotkeys with F1-12, numbers and other non-character buttons works perfectly. Window manager hotkeys not affected by this bug. All hotkeys in system parameters->keyboard->hotkeys->windows works perfect with any keyboard layout. Workaround for some system hotkeys and two layouts (english and non- latin): rebind all hotkeys in your local layout. For example instead of ctrl+alt+t use ctrl+alt+τ (greek tau). That hotkey still work with english layout. If you use english and two different non-latin layouts this workaround helps only with one of them. Dear Ubuntu users and developers! Please include the following information to your comment about non-latin shortcuts problems: 1. What Ubuntu version do you have (Ubuntu 13.10, Ubuntu 13.10 GNOME, Ubuntu 14.04, Ubuntu 14.04 GNOME and so on), upgraded (describe version) or clean installed 2. What keyboard layout do you have 3. What shortcut for keyboard layout switching do you use 4. On which session you have problems - that is one from Unity, GNOME Shell, GNOME FlashBack/Fallback (Metacity), GNOME FlashBack/Fallback (Compiz) 5. With which program and its version and origin (Ubuntu repositories, PPA, non-deb binary package from some website) you have problems. By providing this information you can make bug-fixing much simpler and may be faster. -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- To manage notifications about this bug go to: https://bugs.launchpad.net/aptana-studio-installer/+bug/1226962/+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 1226962] Re: Hotkeys not functional in non-latin keyboard layout
@Alberto no offense, but for Unity this bug was never fixed, so you can easily add tag "all future Ubuntu releases". Bugs doesn't disappear if no one tries to fix it. And I assume that no one tries because it's 2 years old and affects a lot of people. P.S. I'm talking about this parts of this bug: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1280759 (Super+A/F/M/C/V hotkeys). -- 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/1226962 Title: Hotkeys not functional in non-latin keyboard layout Status in aptana-studio-installer: New Status in Default settings and artwork for Baltix OS: New Status in LibreOffice Productivity Suite: Fix Released Status in ibus: New Status in Indicator keyboard: Fix Released Status in Inkscape: New Status in monodevelop: New Status in mutter: Fix Released Status in okular: New Status in OpenOffice: New Status in sigram: New Status in Unity: Fix Released Status in gnome-settings-daemon package in Ubuntu: Triaged Status in gnome-terminal package in Ubuntu: Triaged Status in openjdk-7 package in Ubuntu: Incomplete Status in unity package in Ubuntu: Triaged Status in unity-settings-daemon package in Ubuntu: Triaged Status in gnome-settings-daemon package in Fedora: Unknown Status in gnome-shell package in Fedora: Unknown Bug description: New keyboard layout changer in Ubuntu 13.10 introduce old-new bug. Any system or application hotkey witch use char (for example: ctrl+alt+t for terminal or ctrl+t for new tab in browser) become unfunctional when selected non-latin keyboard layout. Hotkeys with F1-12, numbers and other non-character buttons works perfectly. Window manager hotkeys not affected by this bug. All hotkeys in system parameters->keyboard->hotkeys->windows works perfect with any keyboard layout. Workaround for some system hotkeys and two layouts (english and non- latin): rebind all hotkeys in your local layout. For example instead of ctrl+alt+t use ctrl+alt+τ (greek tau). That hotkey still work with english layout. If you use english and two different non-latin layouts this workaround helps only with one of them. Dear Ubuntu users and developers! Please include the following information to your comment about non-latin shortcuts problems: 1. What Ubuntu version do you have (Ubuntu 13.10, Ubuntu 13.10 GNOME, Ubuntu 14.04, Ubuntu 14.04 GNOME and so on), upgraded (describe version) or clean installed 2. What keyboard layout do you have 3. What shortcut for keyboard layout switching do you use 4. On which session you have problems - that is one from Unity, GNOME Shell, GNOME FlashBack/Fallback (Metacity), GNOME FlashBack/Fallback (Compiz) 5. With which program and its version and origin (Ubuntu repositories, PPA, non-deb binary package from some website) you have problems. By providing this information you can make bug-fixing much simpler and may be faster. -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- To manage notifications about this bug go to: https://bugs.launchpad.net/aptana-studio-installer/+bug/1226962/+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 1226962] Re: Hotkeys not functional in non-latin keyboard layout
This bug still exists in 15.10. @zoltor thank you for the link, I'll give it a try. -- 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/1226962 Title: Hotkeys not functional in non-latin keyboard layout Status in aptana-studio-installer: New Status in Default settings and artwork for Baltix OS: New Status in LibreOffice Productivity Suite: Fix Released Status in ibus: New Status in Indicator keyboard: Fix Released Status in Inkscape: New Status in monodevelop: New Status in mutter: Fix Released Status in okular: New Status in OpenOffice: New Status in sigram: New Status in Unity: Fix Released Status in gnome-settings-daemon package in Ubuntu: Triaged Status in gnome-terminal package in Ubuntu: Triaged Status in openjdk-7 package in Ubuntu: Incomplete Status in unity package in Ubuntu: Triaged Status in unity-settings-daemon package in Ubuntu: Triaged Status in gnome-settings-daemon package in Fedora: Unknown Status in gnome-shell package in Fedora: Unknown Bug description: New keyboard layout changer in Ubuntu 13.10 introduce old-new bug. Any system or application hotkey witch use char (for example: ctrl+alt+t for terminal or ctrl+t for new tab in browser) become unfunctional when selected non-latin keyboard layout. Hotkeys with F1-12, numbers and other non-character buttons works perfectly. Window manager hotkeys not affected by this bug. All hotkeys in system parameters->keyboard->hotkeys->windows works perfect with any keyboard layout. Workaround for some system hotkeys and two layouts (english and non- latin): rebind all hotkeys in your local layout. For example instead of ctrl+alt+t use ctrl+alt+τ (greek tau). That hotkey still work with english layout. If you use english and two different non-latin layouts this workaround helps only with one of them. Dear Ubuntu users and developers! Please include the following information to your comment about non-latin shortcuts problems: 1. What Ubuntu version do you have (Ubuntu 13.10, Ubuntu 13.10 GNOME, Ubuntu 14.04, Ubuntu 14.04 GNOME and so on), upgraded (describe version) or clean installed 2. What keyboard layout do you have 3. What shortcut for keyboard layout switching do you use 4. On which session you have problems - that is one from Unity, GNOME Shell, GNOME FlashBack/Fallback (Metacity), GNOME FlashBack/Fallback (Compiz) 5. With which program and its version and origin (Ubuntu repositories, PPA, non-deb binary package from some website) you have problems. By providing this information you can make bug-fixing much simpler and may be faster. -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- To manage notifications about this bug go to: https://bugs.launchpad.net/aptana-studio-installer/+bug/1226962/+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 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
** Changed in: linux (Ubuntu) Status: Incomplete => Invalid ** Changed in: upstart Status: Confirmed => Invalid ** Changed in: upstart (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 Status in upstart : Invalid Status in linux package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Fix Released Status in upstart package in Ubuntu: Invalid Bug description: 1. Format and label a target Ext4 partion using Ubuntu 12.04 2. Install 64bit 12.10 OS using that target without reformatting it 3. Shut down 4. Boot an alternate copy of Ubuntu 5. Restart selecting the newly installed OS 6. Login then shutdown 6. Boot an alternate copy of Ubuntu 7.Fsck the newly installed OS allowing corrections to be made Each time the the newly installed OS is executed and then shutdown, even if execution only consists of logging on, a subsequent fsck will FAIL. I used Acronis True Image Home 2013 to create an image of the newly installed 64-bit Ubuntu 12.10, so I can recreate the symptoms of Ext4 filesystem corruption 100% of the time by restoring from the image, booting, logging on and shutting down. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: linux-image-3.5.0-17-generic 3.5.0-17.28 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: aguru 1871 F pulseaudio /dev/snd/controlC0: aguru 1871 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Tue Oct 30 22:24:54 2012 HibernationDevice: RESUME=UUID=f22e3fa5-c5c5-41f1-ae5a-49390547cb67 InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: System manufacturer P5Q-E ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=ef2c78d5-783a-422a-88f7-27ec09dda0d1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.5.0-17-generic N/A linux-backports-modules-3.5.0-17-generic N/A linux-firmware1.95 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/06/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2101 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5Q-E dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2101:bd04/06/2009:svnSystemmanufacturer:pnP5Q-E:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5Q-E dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+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 1226962] Re: Hotkeys not functional in non-latin keyboard layout in 13.10, 14.04, 14.04.1, 14.10
** Tags added: vivid -- 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/1226962 Title: Hotkeys not functional in non-latin keyboard layout in 13.10, 14.04, 14.04.1, 14.10 Status in Aptana Studio Installer: New Status in Default settings for the Baltix GNU/Linux OS and desktop: New Status in LibreOffice Productivity Suite: Fix Released Status in IBus: New Status in Indicator keyboard: Fix Released Status in Inkscape: Vector Graphics Editor: New Status in MonoDevelop: New Status in Mutter: Fix Released Status in KDE document viewer: New Status in The OpenOffice.org Suite: New Status in Sigram: New Status in Unity: Fix Released Status in gnome-settings-daemon package in Ubuntu: Triaged Status in gnome-terminal package in Ubuntu: Triaged Status in openjdk-7 package in Ubuntu: Triaged Status in unity package in Ubuntu: Triaged Status in unity-settings-daemon package in Ubuntu: Triaged Status in gnome-settings-daemon package in Fedora: Unknown Status in gnome-shell package in Fedora: Unknown Bug description: New keyboard layout changer in Ubuntu 13.10 introduce old-new bug. Any system or application hotkey witch use char (for example: ctrl+alt+t for terminal or ctrl+t for new tab in browser) become unfunctional when selected non-latin keyboard layout. Hotkeys with F1-12, numbers and other non-character buttons works perfectly. Window manager hotkeys not affected by this bug. All hotkeys in system parameters-keyboard-hotkeys-windows works perfect with any keyboard layout. Workaround for some system hotkeys and two layouts (english and non- latin): rebind all hotkeys in your local layout. For example instead of ctrl+alt+t use ctrl+alt+τ (greek tau). That hotkey still work with english layout. If you use english and two different non-latin layouts this workaround helps only with one of them. Dear Ubuntu users and developers! Please include the following information to your comment about non-latin shortcuts problems: 1. What Ubuntu version do you have (Ubuntu 13.10, Ubuntu 13.10 GNOME, Ubuntu 14.04, Ubuntu 14.04 GNOME and so on), upgraded (describe version) or clean installed 2. What keyboard layout do you have 3. What shortcut for keyboard layout switching do you use 4. On which session you have problems - that is one from Unity, GNOME Shell, GNOME FlashBack/Fallback (Metacity), GNOME FlashBack/Fallback (Compiz) 5. With which program and its version and origin (Ubuntu repositories, PPA, non-deb binary package from some website) you have problems. By providing this information you can make bug-fixing much simpler and may be faster. -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- To manage notifications about this bug go to: https://bugs.launchpad.net/aptana-studio-installer/+bug/1226962/+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 1446081] Re: Incorrect scaling of launcher icons
One more example of normal icons, launcher size 32. ** Attachment added: launcher_size_32.png https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1446081/+attachment/4379805/+files/launcher_size_32.png ** Description changed: Launcher icons shown w/o issues only on this sizes of launcher: 16, 24, 32, 48, 64. - Screenshot attached. Look at Atom, Sublime, Chrome and Skype icons. - There was no such issue before vivid. + Screenshot attached. Look at Sublime, Chrome and Skype icons. There was + no such issue before vivid. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150410.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3 Uname: Linux 3.19.0-14-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Apr 20 00:26:44 2015 JournalErrors: Error: command ['journalctl', '-b', '--priority', 'warning'] failed with exit code 1: No journal files were found. SourcePackage: unity UpgradeStatus: Upgraded to vivid on 2015-03-27 (23 days ago) -- 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/1446081 Title: Incorrect scaling of launcher icons Status in unity package in Ubuntu: New Bug description: Launcher icons shown w/o issues only on this sizes of launcher: 16, 24, 32, 48, 64. Screenshot attached. Look at Sublime, Chrome and Skype icons. There was no such issue before vivid. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150410.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3 Uname: Linux 3.19.0-14-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Apr 20 00:26:44 2015 JournalErrors: Error: command ['journalctl', '-b', '--priority', 'warning'] failed with exit code 1: No journal files were found. SourcePackage: unity UpgradeStatus: Upgraded to vivid on 2015-03-27 (23 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1446081/+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 1446081] [NEW] Incorrect scaling of launcher icons
Public bug reported: Launcher icons shown w/o issues only on this sizes of launcher: 16, 24, 32, 48, 64. Screenshot attached. Look at Sublime, Chrome and Skype icons. There was no such issue before vivid. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150410.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3 Uname: Linux 3.19.0-14-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Apr 20 00:26:44 2015 JournalErrors: Error: command ['journalctl', '-b', '--priority', 'warning'] failed with exit code 1: No journal files were found. SourcePackage: unity UpgradeStatus: Upgraded to vivid on 2015-03-27 (23 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug launcher vivid ** Attachment added: launcher_size_42.png https://bugs.launchpad.net/bugs/1446081/+attachment/4379797/+files/launcher_size_42.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/1446081 Title: Incorrect scaling of launcher icons Status in unity package in Ubuntu: New Bug description: Launcher icons shown w/o issues only on this sizes of launcher: 16, 24, 32, 48, 64. Screenshot attached. Look at Sublime, Chrome and Skype icons. There was no such issue before vivid. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150410.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3 Uname: Linux 3.19.0-14-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Apr 20 00:26:44 2015 JournalErrors: Error: command ['journalctl', '-b', '--priority', 'warning'] failed with exit code 1: No journal files were found. SourcePackage: unity UpgradeStatus: Upgraded to vivid on 2015-03-27 (23 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1446081/+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 1446081] Re: Incorrect scaling of launcher icons
And this is how they should look like. ** Attachment added: launcher_size_48.png https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1446081/+attachment/4379803/+files/launcher_size_48.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/1446081 Title: Incorrect scaling of launcher icons Status in unity package in Ubuntu: New Bug description: Launcher icons shown w/o issues only on this sizes of launcher: 16, 24, 32, 48, 64. Screenshot attached. Look at Sublime, Chrome and Skype icons. There was no such issue before vivid. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150410.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3 Uname: Linux 3.19.0-14-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Apr 20 00:26:44 2015 JournalErrors: Error: command ['journalctl', '-b', '--priority', 'warning'] failed with exit code 1: No journal files were found. SourcePackage: unity UpgradeStatus: Upgraded to vivid on 2015-03-27 (23 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1446081/+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 1446081] Re: Incorrect scaling of launcher icons
Another example of wrong scaling. ** Attachment added: launcher_size_60.png https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1446081/+attachment/4379802/+files/launcher_size_60.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/1446081 Title: Incorrect scaling of launcher icons Status in unity package in Ubuntu: New Bug description: Launcher icons shown w/o issues only on this sizes of launcher: 16, 24, 32, 48, 64. Screenshot attached. Look at Sublime, Chrome and Skype icons. There was no such issue before vivid. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150410.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3 Uname: Linux 3.19.0-14-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Apr 20 00:26:44 2015 JournalErrors: Error: command ['journalctl', '-b', '--priority', 'warning'] failed with exit code 1: No journal files were found. SourcePackage: unity UpgradeStatus: Upgraded to vivid on 2015-03-27 (23 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1446081/+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 1226962] Re: Hotkeys not functional in non-latin keyboard layout in 13.10, 14.04, 14.04.1, 14.10
Just updated to 15.04 and this bug is still exists. -- 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/1226962 Title: Hotkeys not functional in non-latin keyboard layout in 13.10, 14.04, 14.04.1, 14.10 Status in Aptana Studio Installer: New Status in Default settings for the Baltix GNU/Linux OS and desktop: New Status in LibreOffice Productivity Suite: Fix Released Status in IBus: New Status in Indicator keyboard: Fix Released Status in Inkscape: A Vector Drawing Tool: New Status in MonoDevelop: New Status in Mutter: Fix Released Status in KDE document viewer: New Status in The OpenOffice.org Suite: New Status in Sigram: New Status in Unity: Fix Released Status in gnome-settings-daemon package in Ubuntu: Triaged Status in gnome-terminal package in Ubuntu: Triaged Status in indicator-keyboard package in Ubuntu: Triaged Status in openjdk-7 package in Ubuntu: Triaged Status in unity package in Ubuntu: Triaged Status in unity-settings-daemon package in Ubuntu: Triaged Status in gnome-settings-daemon package in Fedora: Unknown Status in gnome-shell package in Fedora: Unknown Bug description: New keyboard layout changer in Ubuntu 13.10 introduce old-new bug. Any system or application hotkey witch use char (for example: ctrl+alt+t for terminal or ctrl+t for new tab in browser) become unfunctional when selected non-latin keyboard layout. Hotkeys with F1-12, numbers and other non-character buttons works perfectly. Window manager hotkeys not affected by this bug. All hotkeys in system parameters-keyboard-hotkeys-windows works perfect with any keyboard layout. Workaround for some system hotkeys and two layouts (english and non- latin): rebind all hotkeys in your local layout. For example instead of ctrl+alt+t use ctrl+alt+τ (greek tau). That hotkey still work with english layout. If you use english and two different non-latin layouts this workaround helps only with one of them. Dear Ubuntu users and developers! Please include the following information to your comment about non-latin shortcuts problems: 1. What Ubuntu version do you have (Ubuntu 13.10, Ubuntu 13.10 GNOME, Ubuntu 14.04, Ubuntu 14.04 GNOME and so on), upgraded (describe version) or clean installed 2. What keyboard layout do you have 3. What shortcut for keyboard layout switching do you use 4. On which session you have problems - that is one from Unity, GNOME Shell, GNOME FlashBack/Fallback (Metacity), GNOME FlashBack/Fallback (Compiz) 5. With which program and its version and origin (Ubuntu repositories, PPA, non-deb binary package from some website) you have problems. By providing this information you can make bug-fixing much simpler and may be faster. -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- To manage notifications about this bug go to: https://bugs.launchpad.net/aptana-studio-installer/+bug/1226962/+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 1226962] Re: Hotkeys not functional in non-latin keyboard layout in 13.10, 14.04, 14.04.1
14.10 is affected. Super+A/F/M/C/V don't work in russian layout. -- 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/1226962 Title: Hotkeys not functional in non-latin keyboard layout in 13.10, 14.04, 14.04.1 Status in Aptana Studio Installer: New Status in Default settings for the Baltix GNU/Linux OS and desktop: New Status in LibreOffice Productivity Suite: Confirmed Status in IBus: New Status in Indicator keyboard: Fix Released Status in Inkscape: A Vector Drawing Tool: New Status in MonoDevelop: New Status in Mutter: Fix Released Status in The OpenOffice.org Suite: New Status in Unity: Fix Released Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “gnome-terminal” package in Ubuntu: Triaged Status in “indicator-keyboard” package in Ubuntu: Triaged Status in “openjdk-7” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Triaged Status in “unity-settings-daemon” package in Ubuntu: Triaged Status in “gnome-settings-daemon” package in Fedora: Unknown Status in “gnome-shell” package in Fedora: Unknown Bug description: New keyboard layout changer in Ubuntu 13.10 introduce old-new bug. Any system or application hotkey witch use char (for example: ctrl+alt+t for terminal or ctrl+t for new tab in browser) become unfunctional when selected non-latin keyboard layout. Hotkeys with F1-12, numbers and other non-character buttons works perfectly. Window manager hotkeys not affected by this bug. All hotkeys in system parameters-keyboard-hotkeys-windows works perfect with any keyboard layout. Workaround for some system hotkeys and two layouts (english and non- latin): rebind all hotkeys in your local layout. For example instead of ctrl+alt+t use ctrl+alt+τ (greek tau). That hotkey still work with english layout. If you use english and two different non-latin layouts this workaround helps only with one of them. Dear Ubuntu users and developers! Please include the following information to your comment about non-latin shortcuts problems: 1. What Ubuntu version do you have (Ubuntu 13.10, Ubuntu 13.10 GNOME, Ubuntu 14.04, Ubuntu 14.04 GNOME and so on), upgraded (describe version) or clean installed 2. What keyboard layout do you have 3. What shortcut for keyboard layout switching do you use 4. On which session you have problems - that is one from Unity, GNOME Shell, GNOME FlashBack/Fallback (Metacity), GNOME FlashBack/Fallback (Compiz) 5. With which program and its version and origin (Ubuntu repositories, PPA, non-deb binary package from some website) you have problems. By providing this information you can make bug-fixing much simpler and may be faster. -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- To manage notifications about this bug go to: https://bugs.launchpad.net/aptana-studio-installer/+bug/1226962/+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 1012081] Re: util-linux needs updating to 2.24.2
I've rebuilded 2.25-8 from debian. Looks like it somehow works. https://launchpad.net/~xeron-oskom/+archive/ubuntu/util-linux -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1012081 Title: util-linux needs updating to 2.24.2 Status in “util-linux” package in Ubuntu: Triaged Status in “util-linux” source package in Raring: Won't Fix Status in “util-linux” package in Debian: Fix Released Bug description: Applications in the default desktop - specifically gnome-disk-utility - depend on behaviour only introduced in util-linux 2.21+. Specifically if you select Show in user interface in mount options, it adds the mount option x-gvfs-show to the mount options in /etc/fstab. Mounting of this mount point then fails because the option is unrecognised. Also reported bug from the other point of view in bug #1011257 ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: util-linux 2.20.1-1ubuntu3 ProcVersionSignature: Ubuntu 3.4.0-5.11-generic 3.4.0 Uname: Linux 3.4.0-5-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.1.1-0ubuntu2 Architecture: amd64 Date: Tue Jun 12 12:38:02 2012 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: util-linux UpgradeStatus: Upgraded to quantal on 2012-06-09 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1012081/+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
