[Desktop-packages] [Bug 1538471] Re: scope-runner-dbus.py assert failure: *** Error in `/usr/bin/python3': free(): invalid next size (fast): 0x0000000001ca17b0 ***
I ticked the mark to search for online results in Dash, and immediately searched for something in Dash. The I saw the error message. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/1538471 Title: scope-runner-dbus.py assert failure: *** Error in `/usr/bin/python3': free(): invalid next size (fast): 0x01ca17b0 *** Status in Ubuntu Kylin: New Status in libunity package in Ubuntu: Invalid Status in pygobject package in Ubuntu: Fix Committed Bug description: No idea what happened. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: unity-scopes-runner 7.1.4+15.10.20151002-0ubuntu2 ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3 Uname: Linux 4.3.0-7-generic x86_64 ApportVersion: 2.19.4-0ubuntu1 Architecture: amd64 AssertionMessage: *** Error in `/usr/bin/python3': free(): invalid next size (fast): 0x01ca17b0 *** CrashCounter: 1 CurrentDesktop: Unity Date: Wed Jan 27 10:41:54 2016 Dependencies: ExecutablePath: /usr/share/unity-scopes/scope-runner-dbus.py InstallationDate: Installed on 2015-04-30 (271 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) InterpreterPath: /usr/bin/python3.5 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/unity-scopes/scope-runner-dbus.py -s info/calculator.scope Signal: 6 SourcePackage: libunity StacktraceTop: __libc_message (do_abort=do_abort@entry=1, fmt=fmt@entry=0x7fd789926128 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175 malloc_printerr (ptr=, str=0x7fd7899261a0 "free(): invalid next size (fast)", action=1) at malloc.c:4965 _int_free (av=, p=, have_lock=0) at malloc.c:3834 __GI___libc_free (mem=) at malloc.c:2950 ?? () from /usr/lib/python3/dist-packages/gi/_gi.cpython-35m-x86_64-linux-gnu.so SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit code 2: Title: scope-runner-dbus.py assert failure: *** Error in `/usr/bin/python3': free(): invalid next size (fast): 0x01ca17b0 *** UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip libvirtd lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntukylin/+bug/1538471/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1073488] Re: window management - if a window is always on top, it will always get focus after switching between workspaces
Being 'Always On Top' is about being visible, not having the focus. (In fact, we usually use this feature when we want the window to be visible when it does NOT have the focus.) Therefore I definitely think this is a bug, not a feature. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1073488 Title: window management - if a window is always on top, it will always get focus after switching between workspaces Status in Compiz: Triaged Status in compiz package in Ubuntu: Confirmed Bug description: Imagine I have an small terminal window open all the time for doing quick arithmetics. I have set it to be always on top since I need to constantly see it. I have also some other windows open (other terminals, nautilus etc.) on which I am really working and they have the window focus most of the time. What happens: Whenever I switch to another workspace and come back to the current workspace, I see the 'always on top' window gets the focus, even if I left that workspace when another window had the focus. What should happen: When some window has the focus in any workspace, it should keep the focus. By switching to a new workspace, focus of the windows of the old workspace should not change. How to reproduce the bug: Open several windows in a workspace. Make one of the windows 'always on top' from its window accessibility menu (Window 1). Then click on some other window to give it focus (Window 2). Now go to another workspace (by pressing Ctrl+Alt+Left/Right) and then come back. You will see that Window 1 has the focus, instead of Window 2. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.16.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30 Uname: Linux 3.2.0-32-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 295.40 Thu Apr 5 21:37:00 PDT 2012 GCC version: gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu14 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 Date: Wed Oct 31 09:59:56 2012 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu DkmsStatus: nvidia-current, 295.40, 3.2.0-29-generic, x86_64: installed nvidia-current, 295.40, 3.2.0-31-generic, x86_64: installed nvidia-current, 295.40, 3.2.0-32-generic, x86_64: installed ExecutablePath: /usr/bin/compiz GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 440] [10de:0de0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:83b0] InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) JockeyStatus: xorg:nvidia_current - NVIDIA accelerated graphics driver (Proprietary, Enabled, In use) xorg:nvidia_current_updates - NVIDIA accelerated graphics driver (post-release updates) (Proprietary, Disabled, Not in use) xorg:nvidia_experimental_304 - NVIDIA accelerated graphics driver (**experimental** beta) (Proprietary, Disabled, Not in use) xorg:nvidia_experimental_310 - NVIDIA accelerated graphics driver (**experimental** beta) (Proprietary, Disabled, Not in use) MachineType: System manufacturer System Product Name ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-32-generic root=UUID=b8c1967c-1d4e-4034-bed5-3b1357a3d26b ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: Section "Device" Identifier "Default Device" Option "NoLogo""True" EndSection dmi.bios.date: 09/20/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2001 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8P67 REV 3.1 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.:bvr2001:bd09/20/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8P67REV3.1:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.7.8-0ubuntu1.4 version.ia32-libs: ia32-libs N/A version.libdrm
[Desktop-packages] [Bug 1263512] Re: Snapped windows are misplaced upon switching workspaces
** Attachment added: "A video describing the problem."
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1263512/+attachment/4466984/+files/misplaced-snapped-windows.mp4
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to compiz in Ubuntu.
https://bugs.launchpad.net/bugs/1263512
Title:
Snapped windows are misplaced upon switching workspaces
Status in compiz package in Ubuntu:
New
Bug description:
I can't reproduce this bug reliably. Nevertheless it happens a lot. It
happens mostly after few hours of work in the Unity interface.
For reproducing this bug some ingredients are needed:
WHAT YOU NEED:
- You should have enabled workspaces (System Settings > Appearance > Behavior
> Enable workspaces)
- You should have a few windows snapped to different corners of the desktop
(Press Ctrl+Super+Left/Right or Alt+Ctrl+Num (keypad) on different windows and
on different workspaces )
WHAT YOU SHOULD DO:
Since I don't know exactly how to reproduce this bug, I can't tell you
exactly what you should do. This bug shows itself after some time.
It particularly happens when trying to switch to a window that is on a
different workspace by pressing Super+{1..9} shortcut, or by pressing Super+S
shortcut.
WHAT HAPPENS:
- Windows jump to other workspaces (other than one they were originally
snapped to)
Or
- Windows are slightly misplaced from the snapping position, so that the
edges of the window enter the neighboring workspace.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1263512/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1073488] Re: window management - if a window is always on top, it will always get focus after switching between workspaces
Bug exists in Ubuntu 14.04. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1073488 Title: window management - if a window is always on top, it will always get focus after switching between workspaces Status in Compiz: Triaged Status in compiz package in Ubuntu: Confirmed Bug description: Imagine I have an small terminal window open all the time for doing quick arithmetics. I have set it to be always on top since I need to constantly see it. I have also some other windows open (other terminals, nautilus etc.) on which I am really working and they have the window focus most of the time. What happens: Whenever I switch to another workspace and come back to the current workspace, I see the 'always on top' window gets the focus, even if I left that workspace when another window had the focus. What should happen: When some window has the focus in any workspace, it should keep the focus. By switching to a new workspace, focus of the windows of the old workspace should not change. How to reproduce the bug: Open several windows in a workspace. Make one of the windows 'always on top' from its window accessibility menu (Window 1). Then click on some other window to give it focus (Window 2). Now go to another workspace (by pressing Ctrl+Alt+Left/Right) and then come back. You will see that Window 1 has the focus, instead of Window 2. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.16.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30 Uname: Linux 3.2.0-32-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 295.40 Thu Apr 5 21:37:00 PDT 2012 GCC version: gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu14 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 Date: Wed Oct 31 09:59:56 2012 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu DkmsStatus: nvidia-current, 295.40, 3.2.0-29-generic, x86_64: installed nvidia-current, 295.40, 3.2.0-31-generic, x86_64: installed nvidia-current, 295.40, 3.2.0-32-generic, x86_64: installed ExecutablePath: /usr/bin/compiz GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 440] [10de:0de0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:83b0] InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) JockeyStatus: xorg:nvidia_current - NVIDIA accelerated graphics driver (Proprietary, Enabled, In use) xorg:nvidia_current_updates - NVIDIA accelerated graphics driver (post-release updates) (Proprietary, Disabled, Not in use) xorg:nvidia_experimental_304 - NVIDIA accelerated graphics driver (**experimental** beta) (Proprietary, Disabled, Not in use) xorg:nvidia_experimental_310 - NVIDIA accelerated graphics driver (**experimental** beta) (Proprietary, Disabled, Not in use) MachineType: System manufacturer System Product Name ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-32-generic root=UUID=b8c1967c-1d4e-4034-bed5-3b1357a3d26b ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: Section "Device" Identifier "Default Device" Option "NoLogo""True" EndSection dmi.bios.date: 09/20/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2001 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8P67 REV 3.1 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.:bvr2001:bd09/20/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8P67REV3.1:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.7.8-0ubuntu1.4 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.4-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.4-
[Desktop-packages] [Bug 1263512] Re: Snapped windows are misplaced upon switching workspaces
I have this problem in Ubuntu 14.04. I have not yet tested it in newer
Ubuntu versions.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to compiz in Ubuntu.
https://bugs.launchpad.net/bugs/1263512
Title:
Snapped windows are misplaced upon switching workspaces
Status in compiz package in Ubuntu:
New
Bug description:
I can't reproduce this bug reliably. Nevertheless it happens a lot. It
happens mostly after few hours of work in the Unity interface.
For reproducing this bug some ingredients are needed:
WHAT YOU NEED:
- You should have enabled workspaces (System Settings > Appearance > Behavior
> Enable workspaces)
- You should have a few windows snapped to different corners of the desktop
(Press Ctrl+Super+Left/Right or Alt+Ctrl+Num (keypad) on different windows and
on different workspaces )
WHAT YOU SHOULD DO:
Since I don't know exactly how to reproduce this bug, I can't tell you
exactly what you should do. This bug shows itself after some time.
It particularly happens when trying to switch to a window that is on a
different workspace by pressing Super+{1..9} shortcut, or by pressing Super+S
shortcut.
WHAT HAPPENS:
- Windows jump to other workspaces (other than one they were originally
snapped to)
Or
- Windows are slightly misplaced from the snapping position, so that the
edges of the window enter the neighboring workspace.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1263512/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1442053] Re: eog crashes opening a certain png file (attached)
** Attachment added: "png that makes the crash" https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1442053/+attachment/4370317/+files/TUM_IAS_logo.png.gz -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1442053 Title: eog crashes opening a certain png file (attached) Status in eog package in Ubuntu: New Bug description: I open eog file.png from terminal, and this is what I get: ** Gdk:ERROR:/build/buildd/gtk+3.0-3.10.8/./gdk/gdkcairo.c:193:gdk_cairo_surface_paint_pixbuf: assertion failed: (cairo_image_surface_get_format (surface) == CAIRO_FORMAT_RGB24 || cairo_image_surface_get_format (surface) == CAIRO_FORMAT_ARGB32) Aborted (core dumped) The image is made from a pdf file using convert: convert -density 5000 TUM_IAS_logo.pdf TUM_IAS_logo.png Also, nautilus also crashes when trying to make the thumbnail. So as Unity dash. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: eog 3.10.2-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16 Uname: Linux 3.13.0-48-generic x86_64 NonfreeKernelModules: pax ApportVersion: 2.14.1-0ubuntu3.8 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 9 11:57:41 2015 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 InstallationDate: Installed on 2015-03-05 (34 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20130203-13:50 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: eog UpgradeStatus: Upgraded to trusty on 2015-03-10 (29 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1442053/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1442053] Re: eog crashes opening a certain png file (attached)
** Attachment added: "pdf source of the png image" https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1442053/+attachment/4370315/+files/TUM_IAS_logo.pdf.gz -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1442053 Title: eog crashes opening a certain png file (attached) Status in eog package in Ubuntu: New Bug description: I open eog file.png from terminal, and this is what I get: ** Gdk:ERROR:/build/buildd/gtk+3.0-3.10.8/./gdk/gdkcairo.c:193:gdk_cairo_surface_paint_pixbuf: assertion failed: (cairo_image_surface_get_format (surface) == CAIRO_FORMAT_RGB24 || cairo_image_surface_get_format (surface) == CAIRO_FORMAT_ARGB32) Aborted (core dumped) The image is made from a pdf file using convert: convert -density 5000 TUM_IAS_logo.pdf TUM_IAS_logo.png Also, nautilus also crashes when trying to make the thumbnail. So as Unity dash. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: eog 3.10.2-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16 Uname: Linux 3.13.0-48-generic x86_64 NonfreeKernelModules: pax ApportVersion: 2.14.1-0ubuntu3.8 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 9 11:57:41 2015 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 InstallationDate: Installed on 2015-03-05 (34 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20130203-13:50 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: eog UpgradeStatus: Upgraded to trusty on 2015-03-10 (29 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1442053/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1442053] [NEW] eog crashes opening a certain png file (attached)
Public bug reported: I open eog file.png from terminal, and this is what I get: ** Gdk:ERROR:/build/buildd/gtk+3.0-3.10.8/./gdk/gdkcairo.c:193:gdk_cairo_surface_paint_pixbuf: assertion failed: (cairo_image_surface_get_format (surface) == CAIRO_FORMAT_RGB24 || cairo_image_surface_get_format (surface) == CAIRO_FORMAT_ARGB32) Aborted (core dumped) The image is made from a pdf file using convert: convert -density 5000 TUM_IAS_logo.pdf TUM_IAS_logo.png Also, nautilus also crashes when trying to make the thumbnail. So as Unity dash. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: eog 3.10.2-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16 Uname: Linux 3.13.0-48-generic x86_64 NonfreeKernelModules: pax ApportVersion: 2.14.1-0ubuntu3.8 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 9 11:57:41 2015 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 InstallationDate: Installed on 2015-03-05 (34 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20130203-13:50 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: eog UpgradeStatus: Upgraded to trusty on 2015-03-10 (29 days ago) ** Affects: eog (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1442053 Title: eog crashes opening a certain png file (attached) Status in eog package in Ubuntu: New Bug description: I open eog file.png from terminal, and this is what I get: ** Gdk:ERROR:/build/buildd/gtk+3.0-3.10.8/./gdk/gdkcairo.c:193:gdk_cairo_surface_paint_pixbuf: assertion failed: (cairo_image_surface_get_format (surface) == CAIRO_FORMAT_RGB24 || cairo_image_surface_get_format (surface) == CAIRO_FORMAT_ARGB32) Aborted (core dumped) The image is made from a pdf file using convert: convert -density 5000 TUM_IAS_logo.pdf TUM_IAS_logo.png Also, nautilus also crashes when trying to make the thumbnail. So as Unity dash. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: eog 3.10.2-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16 Uname: Linux 3.13.0-48-generic x86_64 NonfreeKernelModules: pax ApportVersion: 2.14.1-0ubuntu3.8 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 9 11:57:41 2015 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 InstallationDate: Installed on 2015-03-05 (34 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20130203-13:50 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: eog UpgradeStatus: Upgraded to trusty on 2015-03-10 (29 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1442053/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1244548] Re: Keyboard shortcut for changing keyboard layout does not work on lock screen
Fixed on the lock screen (yay!), but not fixed on the login screen. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1244548 Title: Keyboard shortcut for changing keyboard layout does not work on lock screen Status in “gnome-screensaver” package in Ubuntu: Confirmed Bug description: Shortcut for changing keyboard layout does not work on lock screen (to change keyboard layout for entering password). - Switch to some non-english layout (otherwise lock screen will not have layout indicator at all) - Lock the screen - Press your shortcut for changing keyboard layout (i.e. ctrl+shift) -- it will not change layout - Clicking layout indicator near password entry box works -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-screensaver 3.6.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Fri Oct 25 11:01:10 2013 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session idle-delay uint32 300 org.gnome.desktop.session session-name 'ubuntu' InstallationDate: Installed on 2013-10-23 (1 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: gnome-screensaver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1244548/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1290104] Re: some shortcuts stopped working
Except one issue, I can confirm that the shortcuts are back. Thank you :) And this is the remaining issue: Previously, the shortcut for zooming in was "Ctrl++". Now, for the same functionality you should press "Ctrl+Shift++". OK, literally speaking, the "+" key always means "Shift+=". But the shortcut was never like this before. In Firefox, for example, both "Ctrl++" and "Ctrl+shift++" work. It is actually more convenient to use the former rather than the latter, since you don't have to hold one extra key. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1290104 Title: some shortcuts stopped working Status in “evince” package in Ubuntu: Fix Released Bug description: Ctrl+PgUp / Ctrl+PgDn: for scrolling to the TOP of the previous / next page of the document. Ctrl++ / Ctrl+-: for zooming in / zooming out. BTW: HUD also doesn't work. HUD shows the entries, but selecting the action in HUD has no effect. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: evince 3.10.3-0ubuntu9 ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5 Uname: Linux 3.13.0-16-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Mar 9 20:36:27 2014 InstallationDate: Installed on 2014-02-15 (21 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140211) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1290104/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1226962] Re: Hotkeys not functional in non-latin keyboard layout in 13.10 and 14.04
Please also take a look at a very similar bug report 1280759. It is not fixed yet. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1226962 Title: Hotkeys not functional in non-latin keyboard layout in 13.10 and 14.04 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 Mutter: Fix Released Status in The OpenOffice.org Suite: New Status in Unity: Fix Committed Status in “gnome-settings-daemon” package in Ubuntu: In Progress Status in “indicator-keyboard” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Fix Released Status in “unity-settings-daemon” package in Ubuntu: Fix Released Status in “gnome-settings-daemon” 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. -- 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/df-libreoffice/+bug/1226962/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1292014] [NEW] Keyboard layout switcher shortcut doesn't work in lock screen
Public bug reported: I know this bug is known, but I couldn't find a report for it. After the big change in the lock-screen (unity greeter instead of GNOME- screensaver) the bug introduced with 13.10 still exists: While in lock screen, you cannot change keyboard layout by the defined shortcut keys. My specific shortcut for switching keyboard layout is Alt+Shift (right/left). This doesn't work when the screen is locked and I want to enter password for unlocking. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140312-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: Thu Mar 13 14:56:23 2014 InstallationDate: Installed on 2014-02-15 (25 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140211) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Summary changed: - Keyboard layout switcher shortcut doesn't work lock screen + Keyboard layout switcher shortcut doesn't work in lock screen -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1292014 Title: Keyboard layout switcher shortcut doesn't work in lock screen Status in “unity” package in Ubuntu: New Bug description: I know this bug is known, but I couldn't find a report for it. After the big change in the lock-screen (unity greeter instead of GNOME-screensaver) the bug introduced with 13.10 still exists: While in lock screen, you cannot change keyboard layout by the defined shortcut keys. My specific shortcut for switching keyboard layout is Alt+Shift (right/left). This doesn't work when the screen is locked and I want to enter password for unlocking. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140312-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: Thu Mar 13 14:56:23 2014 InstallationDate: Installed on 2014-02-15 (25 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140211) 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/1292014/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1290104] [NEW] some shortcuts stopped working
Public bug reported: Ctrl+PgUp / Ctrl+PgDn: for scrolling to the TOP of the previous / next page of the document. Ctrl++ / Ctrl+-: for zooming in / zooming out. BTW: HUD also doesn't work. HUD shows the entries, but selecting the action in HUD has no effect. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: evince 3.10.3-0ubuntu9 ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5 Uname: Linux 3.13.0-16-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Mar 9 20:36:27 2014 InstallationDate: Installed on 2014-02-15 (21 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140211) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1290104 Title: some shortcuts stopped working Status in “evince” package in Ubuntu: New Bug description: Ctrl+PgUp / Ctrl+PgDn: for scrolling to the TOP of the previous / next page of the document. Ctrl++ / Ctrl+-: for zooming in / zooming out. BTW: HUD also doesn't work. HUD shows the entries, but selecting the action in HUD has no effect. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: evince 3.10.3-0ubuntu9 ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5 Uname: Linux 3.13.0-16-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Mar 9 20:36:27 2014 InstallationDate: Installed on 2014-02-15 (21 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140211) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1290104/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1286496] Re: most Nautilus features inaccessible to HUD since no menu
This is great. Thanks to this patch, I can efficiently perform my tasks using HUD. The only missing entry in the menu is "Open in Terminal". This feature is related to the package "nautilus-open-terminal". I don't know if this package is installed by default or not, but it is extremely useful. To have it via HUD would be great. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1286496 Title: most Nautilus features inaccessible to HUD since no menu Status in “nautilus” package in Ubuntu: Invalid Bug description: After GNOME re-design of Nautilus, there is only one menu left in Nautilus, with some rarely used entries like About, Preferences, etc. The rest of the features are move to toolbar button/menus. As a results, many of Nautilus features, like "Open a New Tab", "Sort by Name/Type/Date," and "Open in Terminal" cannot be accessed through HUD. All of them require mouse clicks or shortcut keys. My suggestion is to define new menu entries for Nautilus and populate it with the functionalities that are currently only available via the toolbar buttons. Menu entries like Files, Edit, View, and Help can do the job. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nautilus 1:3.10.1-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4 Uname: Linux 3.13.0-12-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 1 11:11:47 2014 GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2014-02-15 (13 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140211) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1286496/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1286496] [NEW] most Nautilus features inaccessible to HUD since no menu
Public bug reported: After GNOME re-design of Nautilus, there is only one menu left in Nautilus, with some rarely used entries like About, Preferences, etc. The rest of the features are move to toolbar button/menus. As a results, many of Nautilus features, like "Open a New Tab", "Sort by Name/Type/Date," and "Open in Terminal" cannot be accessed through HUD. All of them require mouse clicks or shortcut keys. My suggestion is to define new menu entries for Nautilus and populate it with the functionalities that are currently only available via the toolbar buttons. Menu entries like Files, Edit, View, and Help can do the job. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nautilus 1:3.10.1-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4 Uname: Linux 3.13.0-12-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 1 11:11:47 2014 GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2014-02-15 (13 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140211) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: hud trusty ** Summary changed: - most Nautilus features unavailable to HUD since no menu + most Nautilus features inaccessible to HUD since no menu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1286496 Title: most Nautilus features inaccessible to HUD since no menu Status in “nautilus” package in Ubuntu: New Bug description: After GNOME re-design of Nautilus, there is only one menu left in Nautilus, with some rarely used entries like About, Preferences, etc. The rest of the features are move to toolbar button/menus. As a results, many of Nautilus features, like "Open a New Tab", "Sort by Name/Type/Date," and "Open in Terminal" cannot be accessed through HUD. All of them require mouse clicks or shortcut keys. My suggestion is to define new menu entries for Nautilus and populate it with the functionalities that are currently only available via the toolbar buttons. Menu entries like Files, Edit, View, and Help can do the job. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nautilus 1:3.10.1-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4 Uname: Linux 3.13.0-12-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 1 11:11:47 2014 GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2014-02-15 (13 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140211) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1286496/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1283798] [NEW] Keyboard layout switcher shortcuts stop working after reboot
Public bug reported: HOW TO REPRODUCE - Add a new keyboard shortcut (in my case, Persian layout) from the keyboard indicator -> Text Entry Settings - Assign shortcuts for switching to next/previous source (in my case Shift+Alt L and Alt+Shift R) - Test the new layout and layout switcher shortcuts to check if they work (in my case, yes they do) - Reboot - Log back in - Press the layout switcher shortcuts WHAT HAPPENS Keyboard layout does not change upon pressing the shortcuts WHAT SHOULD HAPPEN Layout should change according to the shortcuts you press ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140218.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sun Feb 23 20:09:45 2014 InstallationDate: Installed on 2014-02-15 (7 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140211) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1283798 Title: Keyboard layout switcher shortcuts stop working after reboot Status in “unity” package in Ubuntu: New Bug description: HOW TO REPRODUCE - Add a new keyboard shortcut (in my case, Persian layout) from the keyboard indicator -> Text Entry Settings - Assign shortcuts for switching to next/previous source (in my case Shift+Alt L and Alt+Shift R) - Test the new layout and layout switcher shortcuts to check if they work (in my case, yes they do) - Reboot - Log back in - Press the layout switcher shortcuts WHAT HAPPENS Keyboard layout does not change upon pressing the shortcuts WHAT SHOULD HAPPEN Layout should change according to the shortcuts you press ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140218.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sun Feb 23 20:09:45 2014 InstallationDate: Installed on 2014-02-15 (7 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140211) 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/1283798/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1280759] [NEW] Shortcuts are defined via keyboard layout, not the keys
Public bug reported: There are shortcuts to open lenses in Unity, for example "Super + A" for App Lens, or "Super + F" for Files Lens, etc. There are also shortcuts in the Launcher "Super + 1 to 9" to launch apps from the Launcher. These shortcuts don't work if the keyboard layout is set to a non-Latin layout, in my case Persian, where almost all the keys are mapped to new characters. HOW TO REPRODUCE: Add a new Persian keyboard layout to the system, in addition to English, via keyboard layout indicator --> Text Entry Settings. Switch to the Persian layout (by clicking on the keyboard layout indicator). Press "Super + F". WHAT HAPPENS: Dash is not open. Nothing happens. WHAT SHOULD HEPPEN: The Files Lens in the dash should open. The shortcuts should be associated with the keys on the keyboard, not to the characters they are associated with (which depends on the active keyboard layout). When I am typing something in Persian, and I want to search for a file, it is not reasonable that I should first switch back to the English layout before I can use a particular shortcut. This problem does not happen in some other apps like gedit or Firefox. COMPARE TO GEDIT: Open gedit text editor. Write something. Switch to the Persian layout. Press "Ctrl + S" (the shortcut to save the document). WHAT HAPPENS, AND WHAT SHOULD HAPPEN: The save dialoge box appears. I think this problem happens for all keyboard layouts that don't use Latin characters. Layout-wise, when I press "Ctrl + S" while Persian layout is active, I am typing "Ctrl + س". But keyboard-wise, I am always pressing the same keyboard binding. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libunity9 7.1.4+14.04.20140210-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 ApportVersion: 2.13.2-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 16 12:04:10 2014 InstallationDate: Installed on 2014-02-15 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140211) SourcePackage: libunity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libunity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dp-libunity https://bugs.launchpad.net/bugs/1280759 Title: Shortcuts are defined via keyboard layout, not the keys Status in “libunity” package in Ubuntu: New Bug description: There are shortcuts to open lenses in Unity, for example "Super + A" for App Lens, or "Super + F" for Files Lens, etc. There are also shortcuts in the Launcher "Super + 1 to 9" to launch apps from the Launcher. These shortcuts don't work if the keyboard layout is set to a non-Latin layout, in my case Persian, where almost all the keys are mapped to new characters. HOW TO REPRODUCE: Add a new Persian keyboard layout to the system, in addition to English, via keyboard layout indicator --> Text Entry Settings. Switch to the Persian layout (by clicking on the keyboard layout indicator). Press "Super + F". WHAT HAPPENS: Dash is not open. Nothing happens. WHAT SHOULD HEPPEN: The Files Lens in the dash should open. The shortcuts should be associated with the keys on the keyboard, not to the characters they are associated with (which depends on the active keyboard layout). When I am typing something in Persian, and I want to search for a file, it is not reasonable that I should first switch back to the English layout before I can use a particular shortcut. This problem does not happen in some other apps like gedit or Firefox. COMPARE TO GEDIT: Open gedit text editor. Write something. Switch to the Persian layout. Press "Ctrl + S" (the shortcut to save the document). WHAT HAPPENS, AND WHAT SHOULD HAPPEN: The save dialoge box appears. I think this problem happens for all keyboard layouts that don't use Latin characters. Layout-wise, when I press "Ctrl + S" while Persian layout is active, I am typing "Ctrl + س". But keyboard-wise, I am always pressing the same keyboard binding. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libunity9 7.1.4+14.04.20140210-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 ApportVersion: 2.13.2-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 16 12:04:10 2014 InstallationDate: Installed on 2014-02-15 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140211) SourcePackage: libunity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1280759/+subscriptio
[Desktop-packages] [Bug 761093] Re: Unity says "Home Folder" no matter where I am
This is fixed for me in 13.10. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/761093 Title: Unity says "Home Folder" no matter where I am Status in Ayatana Design: Fix Committed Status in One Hundred Papercuts: Triaged Status in “nautilus” package in Ubuntu: Triaged Bug description: Binary package hint: nautilus In Ubuntu Unity, Nautilus shows up as "Home Folder" in the launcher (tooltip) and in the panel (application menu) when the window is not maximized. But if I open it, then go anywhere else in the file system, it still says "Home Folder" in both places. It should either say "File Manager", or the name of the folder I'm currently looking at. Desired resolution: - The Nautilus icon in the Launcher should always be titled 'File Manager'. - When a Nautilus window is in the restored state, the global menu should display 'File Manager' (when a Nautilus window is maximised the global menu will display the window title). To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/761093/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 991089] Re: rhythmbox cannot play pls files, but it's assigned to open them
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/991089 Title: rhythmbox cannot play pls files, but it's assigned to open them Status in “rhythmbox” package in Ubuntu: New Bug description: I downloaded a file for an internet radio (http://audiostream.tehransit.com/tunein.php/fusions128/playlist.pls). Then I double-clicked on it, hoping to hear the music. Rhythmbox opened, but it started playing some other mp3 file stored on my system, not the radio. If I open the same pls file by Movie Player (totem), it will play without any problem. How to reproduce: 1. Download this file: http://audiostream.tehransit.com/tunein.php/fusions128/playlist.pls 2. Double-click on the downloaded file. What happens: Rhythmbox opens, but it doesn't play the file. What should happen: Some application (Rhythmbox or Movie Player) should open the file and play it. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: rhythmbox 2.96-0ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 Date: Sun Apr 29 14:37:49 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/991089/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 991089] [NEW] rhythmbox cannot play pls files, but it's assigned to open them
Public bug reported: I downloaded a file for an internet radio (http://audiostream.tehransit.com/tunein.php/fusions128/playlist.pls). Then I double-clicked on it, hoping to hear the music. Rhythmbox opened, but it started playing some other mp3 file stored on my system, not the radio. If I open the same pls file by Movie Player (totem), it will play without any problem. How to reproduce: 1. Download this file: http://audiostream.tehransit.com/tunein.php/fusions128/playlist.pls 2. Double-click on the downloaded file. What happens: Rhythmbox opens, but it doesn't play the file. What should happen: Some application (Rhythmbox or Movie Player) should open the file and play it. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: rhythmbox 2.96-0ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 Date: Sun Apr 29 14:37:49 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/991089 Title: rhythmbox cannot play pls files, but it's assigned to open them Status in “rhythmbox” package in Ubuntu: New Bug description: I downloaded a file for an internet radio (http://audiostream.tehransit.com/tunein.php/fusions128/playlist.pls). Then I double-clicked on it, hoping to hear the music. Rhythmbox opened, but it started playing some other mp3 file stored on my system, not the radio. If I open the same pls file by Movie Player (totem), it will play without any problem. How to reproduce: 1. Download this file: http://audiostream.tehransit.com/tunein.php/fusions128/playlist.pls 2. Double-click on the downloaded file. What happens: Rhythmbox opens, but it doesn't play the file. What should happen: Some application (Rhythmbox or Movie Player) should open the file and play it. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: rhythmbox 2.96-0ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 Date: Sun Apr 29 14:37:49 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/991089/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 970422] Re: system monitor is eating CPU
** Attachment added: "screenshot of g-s-m, while eating 96% of CPU." https://bugs.launchpad.net/bugs/970422/+attachment/2978785/+files/Screenshot%20from%202012-04-01%2000%3A02%3A29.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/970422 Title: system monitor is eating CPU Status in “gnome-system-monitor” package in Ubuntu: New Bug description: It doesn't crash, but it uses a lot of CPU power. Not 100% of CPU, but a lot, like 50% on average, much more than previous releases of Ubuntu. I use Ubuntu since dapper (6.06 LTS). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-system-monitor 3.3.92-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 ApportVersion: 1.95-0ubuntu1 Architecture: amd64 Date: Sun Apr 1 00:05:09 2012 ExecutablePath: /usr/bin/gnome-system-monitor InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328) ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-system-monitor UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/970422/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 970422] [NEW] system monitor is eating CPU
Public bug reported: It doesn't crash, but it uses a lot of CPU power. Not 100% of CPU, but a lot, like 50% on average, much more than previous releases of Ubuntu. I use Ubuntu since dapper (6.06 LTS). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-system-monitor 3.3.92-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 ApportVersion: 1.95-0ubuntu1 Architecture: amd64 Date: Sun Apr 1 00:05:09 2012 ExecutablePath: /usr/bin/gnome-system-monitor InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328) ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-system-monitor UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-system-monitor (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug apport-lpi precise -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/970422 Title: system monitor is eating CPU Status in “gnome-system-monitor” package in Ubuntu: New Bug description: It doesn't crash, but it uses a lot of CPU power. Not 100% of CPU, but a lot, like 50% on average, much more than previous releases of Ubuntu. I use Ubuntu since dapper (6.06 LTS). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-system-monitor 3.3.92-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 ApportVersion: 1.95-0ubuntu1 Architecture: amd64 Date: Sun Apr 1 00:05:09 2012 ExecutablePath: /usr/bin/gnome-system-monitor InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328) ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-system-monitor UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/970422/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 970196] Re: window freeze when setting blank password for default keyring
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/970196 Title: window freeze when setting blank password for default keyring Status in “gnome-keyring” package in Ubuntu: New Bug description: The first time after my fresh install of Ubuntu 12.04 LTS, I entered Wi-Fi password to set up my wireless. Then, as usual, a window popped up for setting up the default keyring. I left it blank, like what I did for previous versions of Ubuntu. Then I got a warning message with the title "Store passwords unencrypted?" with two buttons to click: "Cancel" and "Use unsafe storage" This window is always freezed for me. No part of this window is clickable except close (x) button on top left. Therefore I can't set a blank password for my default keyring. However, if I set a non-blank password, I don't get this message and there is no problem. To reproduce it at a later time: 1. Go to "Password and Keys" (in terminal: seahorse) 2. Right-click on "Passwords: default" and select "Change Password" 3. Fill the "Old Pasword" text-field with something, but leave the other two fields blank. 4. Press "OK" What happens: * A warning message appears, but it is non-functional. What should happen: * A warning message should appear and by clicking "OK" it should go away. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-keyring 3.2.2-2ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 ApportVersion: 1.95-0ubuntu1 Architecture: amd64 Date: Sat Mar 31 18:44:26 2012 ExecutablePath: /usr/lib/gnome-keyring/gnome-keyring-prompt-3 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328) ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/970196/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 970196] [NEW] window freeze when setting blank password for default keyring
Public bug reported: The first time after my fresh install of Ubuntu 12.04 LTS, I entered Wi- Fi password to set up my wireless. Then, as usual, a window popped up for setting up the default keyring. I left it blank, like what I did for previous versions of Ubuntu. Then I got a warning message with the title "Store passwords unencrypted?" with two buttons to click: "Cancel" and "Use unsafe storage" This window is always freezed for me. No part of this window is clickable except close (x) button on top left. Therefore I can't set a blank password for my default keyring. However, if I set a non-blank password, I don't get this message and there is no problem. To reproduce it at a later time: 1. Go to "Password and Keys" (in terminal: seahorse) 2. Right-click on "Passwords: default" and select "Change Password" 3. Fill the "Old Pasword" text-field with something, but leave the other two fields blank. 4. Press "OK" What happens: * A warning message appears, but it is non-functional. What should happen: * A warning message should appear and by clicking "OK" it should go away. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-keyring 3.2.2-2ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 ApportVersion: 1.95-0ubuntu1 Architecture: amd64 Date: Sat Mar 31 18:44:26 2012 ExecutablePath: /usr/lib/gnome-keyring/gnome-keyring-prompt-3 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328) ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-keyring (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/970196 Title: window freeze when setting blank password for default keyring Status in “gnome-keyring” package in Ubuntu: New Bug description: The first time after my fresh install of Ubuntu 12.04 LTS, I entered Wi-Fi password to set up my wireless. Then, as usual, a window popped up for setting up the default keyring. I left it blank, like what I did for previous versions of Ubuntu. Then I got a warning message with the title "Store passwords unencrypted?" with two buttons to click: "Cancel" and "Use unsafe storage" This window is always freezed for me. No part of this window is clickable except close (x) button on top left. Therefore I can't set a blank password for my default keyring. However, if I set a non-blank password, I don't get this message and there is no problem. To reproduce it at a later time: 1. Go to "Password and Keys" (in terminal: seahorse) 2. Right-click on "Passwords: default" and select "Change Password" 3. Fill the "Old Pasword" text-field with something, but leave the other two fields blank. 4. Press "OK" What happens: * A warning message appears, but it is non-functional. What should happen: * A warning message should appear and by clicking "OK" it should go away. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-keyring 3.2.2-2ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 ApportVersion: 1.95-0ubuntu1 Architecture: amd64 Date: Sat Mar 31 18:44:26 2012 ExecutablePath: /usr/lib/gnome-keyring/gnome-keyring-prompt-3 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328) ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/970196/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 927931] Re: RTL (CTL) is expected to be enabled in all cases by RTL users
I agree like hell. CTL support is ESSENTIAL for users of RTL languages like Hebrew, Arabic, and many users don't know how to activate it. This is a real problem I have seen many people have. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/927931 Title: RTL (CTL) is expected to be enabled in all cases by RTL users Status in “libreoffice” package in Ubuntu: Confirmed Bug description: This is concerning the usability issue where an RTL user gets in front of LibreOffice and doesn't find the two directionality buttons in the toolbar (OMG!!!). He won't find them anywhere until he does 8 mouse clicks to turn the RTL feature on: Tools -> Options -> Language Settings -> Languages -> Enabled for complex text layout (CTL) -> CTL: -> OK My mom can't do this :-/ . This is how this happens: CTL is off by default in LibreOffice, and thus RTL is, too. As I've been briefed, this is how it gets turned on for RTL users automatically: 1. RTL locales 2. A language support package of one of the RTL languages is installed The problem is that these two triggers for CTL don't cover all the situations where an RTL user runs LibreOffice. Many RTL users choose a non-RTL locale. They can also choose not to install any of the language support packages. The presence of an RTL language layout is all that indicates their RTL-ness :) Even when RTL users use a friend's/public computer as guests they expect the RTL buttons. Then, why make RTL off by default? Does it cost a lot of memory? Does it have bad Karma? :) The expectation to have those RTL buttons is because they seem to be always there in Microsoft Office since as far as I can remember. I never had to turn anything on. They were always there by default. In order to understand the severity of this issue, let me tell you what users do when they don't find those RTL buttons. They try to configure the toolbar, thinking that they must be disabled there. They find them enabled, actually. Although enabled in the toolbar, they don't appear :-O . After that they're quite lost so they might go to the correct Language Settings -> Languages configuration section. There, they will not find "RTL" or "Left to right". How would they know whether to enable the "Enhanced language support" for Asian languages or for Complex text layout? Most users would lose a few hairs by that point. Thanks and blessings, Shahar ProblemType: BugDistroRelease: Ubuntu 12.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 3.2.0-14.23-generic 3.2.3 Uname: Linux 3.2.0-14-generic x86_64 ApportVersion: 1.91-0ubuntu1 Architecture: amd64 CasperVersion: 1.304 Date: Mon Feb 6 22:14:26 2012 LiveMediaBuild: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120206) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/927931/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 274552] Re: Persian: Change order of characters when opening document
Dear Nahoo! All you need to do is to activate support for "complex text layout," as you can see in this image: http://freeexp.files.wordpress.com/2008/04/ooo_options_dialog_2.png Then you will notice two new buttons are added in the formatting toolbar. To get the right result, you should format your text not only as right-aligned, but also as RTL-directioned (using the new RTL toolbar-button). This is not actually a bug. The point is, while support for complex text layout is essential for Persian/Arabic speakers, this feature is not activated by default in OpenOffice/LibreOffice (probably because most users will never need it). The ideal case would be a world in which LibreOffice activates complex text layout support automatically if it detects a Persian/Arabic/Hebrew/[...] keyboard layout in the system. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/274552 Title: Persian: Change order of characters when opening document Status in The OpenOffice.org Suite: New Status in “libreoffice” package in Ubuntu: Incomplete Status in “openoffice.org” package in Ubuntu: Won't Fix Bug description: Binary package hint: openoffice.org-writer Try to copy the following text into an openoffice-writer window, the last point (last line, right) will apear on the last line, but on the left end. It appears, than all the points appears on the wrong order. My findings, it that the left and right endings of each line are transposed. حمدی نژاد یک دروغ است، دروغی که نه بر اثر گذشت تاریخ، بلکه بسرعت فاش شده است و می شود، آنچه مشکل ماست، نتیجه حضور سه ساله این کوتوله سیاسی در زندگی ملت ایران است، او موفق شده است که تمام بیماری های خود را به جامعه ایران سرایت دهد. او جامعه ایران را بیمار، خودخواه، دروغگو، بی اعتماد و حریص کرده است. شاید این مهم ترین مشکل امروز ایران باشد. مشکلی که بسادگی حل نمی شود. To reproduce the bug, simply open the attached file with openoffice writter. To manage notifications about this bug go to: https://bugs.launchpad.net/openoffice/+bug/274552/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
