date:20191015

** Changed in: gdm
   Status: Unknown => New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1652282

Title:
  Xwayland not using XAUTHORITY, prevents root applications from
  connecting

Status in gdm:
  New
Status in GParted:
  Fix Released
Status in Mutter:
  Fix Released
Status in gparted package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  When running wayland, GDM fails to set up an XAUTHORITY file and instead
  relies on the process UID for authentication.  This prevents
  applications run as root, like gparted or synaptic from connecting to
  the server.  GDM needs to set up the XAUTHORITY file when running
  Xwayland just like it does when it runs the conventional Xorg.

  A large list of applications broken by this can be found here:

  https://codesearch.debian.net/search?q=Exec%3Dsu-to-
  root+filetype%3Adesktop+path%3A*%2Fapplications%2F*=1

  openSUSE handles this issue with this patch (from the changelog, it looks 
like they implemented this for their YaST settings app):
  
https://build.opensuse.org/package/view_file/GNOME:Factory/mutter/mutter-xwayland-create-xauthority.patch?expand=1

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/1652282/+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 1848288] Xorg crashed with SIGSEGV when changing volume on speakers

2019-10-15 Thread Apport retracing service

Stacktrace:
 #0  0x7f6b2d60aa5f in ?? ()
 No symbol table info available.
 #1  0x in ?? ()
 No symbol table info available.
StacktraceSource:
 #0  0x7f6b2d60aa5f in ?? ()
 #1  0x in ?? ()
StacktraceTop:
 ?? ()
 ?? ()

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1848288

Title:
  Xorg crashed with SIGSEGV when changing volume on speakers

Status in xorg-server package in Ubuntu:
  New

Bug description:
  When using either a Razer Nommo Pro speaker set or a Steel Series
  Arctis Pro Wireless Headset, when the audio devices are set to USB
  Digital Audio, changing the volume knobs will cause xorg-server to
  crash. When changing the volume via the system volume screen or mobile
  apps, the volume will change as expected and xorg-server will not
  crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperVersion: 1.419
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 16 05:29:09 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation TU102 [GeForce RTX 2080 Ti Rev. A] [10de:1e07] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. TU102 [GeForce RTX 2080 Ti Rev. A] 
[1043:866a]
   NVIDIA Corporation TU102 [GeForce RTX 2080 Ti Rev. A] [10de:1e07] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. TU102 [GeForce RTX 2080 Ti Rev. A] 
[1043:866a]
  LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
  MachineType: System manufacturer System Product Name
  ProcCmdline: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth 
/run/user/999/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed quiet splash ---
  SegvAnalysis:
   Segfault happened at: 0x7f6b2d60aa5f:test   %ebx,0x10(%r15)
   PC (0x7f6b2d60aa5f) ok
   source "%ebx" ok
   destination "0x10(%r15)" (0x00fffce7) not located in a known VMA region 
(needed writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: xorg-server
  StacktraceTop:
   ?? () from /usr/lib/xorg/modules/input/libinput_drv.so
   ?? () from /usr/lib/xorg/modules/input/libinput_drv.so
   ?? ()
   ?? ()
   ?? ()
  Title: Xorg crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 07/31/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2001
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG ZENITH EXTREME ALPHA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2001:bd07/31/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHEXTREMEALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  separator:
   
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1848288/+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 1848288] [NEW] Xorg crashed with SIGSEGV when changing volume on speakers

2019-10-15 Thread Kalani Helekunihi

Public bug reported:

When using either a Razer Nommo Pro speaker set or a Steel Series Arctis
Pro Wireless Headset, when the audio devices are set to USB Digital
Audio, changing the volume knobs will cause xorg-server to crash. When
changing the volume via the system volume screen or mobile apps, the
volume will change as expected and xorg-server will not crash.

ProblemType: Crash
DistroRelease: Ubuntu 19.10
Package: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3
ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
Uname: Linux 5.3.0-10-generic x86_64
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperVersion: 1.419
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 16 05:29:09 2019
DistUpgraded: Fresh install
DistroCodename: eoan
DistroVariant: ubuntu
ExecutablePath: /usr/lib/xorg/Xorg
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 NVIDIA Corporation TU102 [GeForce RTX 2080 Ti Rev. A] [10de:1e07] (rev a1) 
(prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. TU102 [GeForce RTX 2080 Ti Rev. A] 
[1043:866a]
 NVIDIA Corporation TU102 [GeForce RTX 2080 Ti Rev. A] [10de:1e07] (rev a1) 
(prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. TU102 [GeForce RTX 2080 Ti Rev. A] 
[1043:866a]
LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
MachineType: System manufacturer System Product Name
ProcCmdline: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth 
/run/user/999/gdm/Xauthority -background none -noreset -keeptty -verbose 3
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=C.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed 
quiet splash ---
SegvAnalysis:
 Segfault happened at: 0x7f6b2d60aa5f:  test   %ebx,0x10(%r15)
 PC (0x7f6b2d60aa5f) ok
 source "%ebx" ok
 destination "0x10(%r15)" (0x00fffce7) not located in a known VMA region 
(needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: xorg-server
StacktraceTop:
 ?? () from /usr/lib/xorg/modules/input/libinput_drv.so
 ?? () from /usr/lib/xorg/modules/input/libinput_drv.so
 ?? ()
 ?? ()
 ?? ()
Title: Xorg crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 07/31/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2001
dmi.board.asset.tag: Default string
dmi.board.name: ROG ZENITH EXTREME ALPHA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2001:bd07/31/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHEXTREMEALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
separator:
 
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

** Affects: xorg-server (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-crash apport-failed-retrace eoan ubuntu

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1848288

Title:
  Xorg crashed with SIGSEGV when changing volume on speakers

Status in xorg-server package in Ubuntu:
  New

Bug description:
  When using either a Razer Nommo Pro speaker set or a Steel Series
  Arctis Pro Wireless Headset, when the audio devices are set to USB
  Digital Audio, changing the volume knobs will cause xorg-server to
  crash. When changing the volume via the system volume screen or mobile
  apps, the volume will change as expected and xorg-server will not
  crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperVersion: 1.419
  CompositorRunning: None

[Desktop-packages] [Bug 1652282] Re: Xwayland not using XAUTHORITY, prevents root applications from connecting

Launchpad has imported 30 comments from the remote bug at
https://bugzilla.gnome.org/show_bug.cgi?id=776437.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

On 2016-12-23T11:45:26+00:00 Wise Melon wrote:

I have found that after switching from Xorg to Wayland on Ubuntu GNOME
16.10 with GNOME 3.22 that GParted does not run when I try to run it as
root. That is when I click the icon and enter my password nothing
happens. I have found that when running what is run when the icon is
clicked that the output in Terminal is (gparted-pkexec):

Created symlink /run/systemd/system/-.mount → /dev/null.
Created symlink /run/systemd/system/boot-efi.mount → /dev/null.
Created symlink /run/systemd/system/boot.mount → /dev/null.
Created symlink /run/systemd/system/run-user-1000.mount → /dev/null.
Created symlink /run/systemd/system/run-user-120.mount → /dev/null.
Created symlink /run/systemd/system/tmp.mount → /dev/null.
No protocol specified

(gpartedbin:16832): Gtk-WARNING **: cannot open display: :0
Removed /run/systemd/system/-.mount.
Removed /run/systemd/system/boot-efi.mount.
Removed /run/systemd/system/boot.mount.
Removed /run/systemd/system/run-user-1000.mount.
Removed /run/systemd/system/run-user-120.mount.
Removed /run/systemd/system/tmp.mount.

So I am now unable to launch and use GParted as root which is really the
only way I can run it in order to make changes.

I originally reported this issue here:
https://bugs.launchpad.net/ubuntu/+source/gparted/+bug/1652282 But
thought I should also do so upstream.

Reply at: https://bugs.launchpad.net/gparted/+bug/1652282/comments/2

On 2017-01-02T11:20:07+00:00 Mike Fleetwood wrote:

This is a known limitation and design choice that Wayland doesn't allow
root privileged applications to work.

One workaround is to run the following in a terminal before running
GParted to allow root applications to connect to the X server under
Wayland.
  xhost +si:localuser:root

Another workaround it to continue to use the X.org display server rather
than the Wayland display server.

More information can be found in the:
  Common Fedora 25 Bugs / Running graphical apps with root privileges
  (e.g. gparted) does not work on Wayland
  https://fedoraproject.org/wiki/Common_F25_bugs#wayland-root-apps

Reply at: https://bugs.launchpad.net/gparted/+bug/1652282/comments/3

On 2017-01-02T11:21:24+00:00 Mike Fleetwood wrote:

*** Bug 776707 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/gparted/+bug/1652282/comments/4

On 2017-01-04T22:51:55+00:00 Nate Graham wrote:

Those workarounds are fine for now, but the real solution to boldly move
us all into the Wayland future is to make GParted run its main UI as a
normally-privileged user, and only request elevated permissions for
actions that actually require them.

Reply at: https://bugs.launchpad.net/gparted/+bug/1652282/comments/5

On 2017-01-05T16:27:10+00:00 Curtis Gedak wrote:

Hi Nate,

For past discussion on this issue, see also:

Bug 758131 - Don't run GUI as root
 (Was: [wayland] gparted fails to start under wayland)

Curtis

Reply at: https://bugs.launchpad.net/gparted/+bug/1652282/comments/6

On 2017-01-06T03:20:53+00:00 Nate Graham wrote:

> All the code is predicated on a single process querying the storage,
> running the GUI and manipulating the storage.  It would be a very large
> task to change.  For a spare time only hobby this might never get done.

Sadly that will eventually result in GParted dying as more and more
distros move to Wayland. :(

Reply at: https://bugs.launchpad.net/gparted/+bug/1652282/comments/7

On 2017-03-01T20:17:11+00:00 Erkin Alp Güney wrote:

>  For a spare time only hobby this might never get done.

Curtis, transferring maintenance of GParted to GNU or GNOME teams would
solve that. They have long queues for maintenance requests and it is
able to finish the process (find a full time maintainer) in a fortnight.

Reply at: https://bugs.launchpad.net/gparted/+bug/1652282/comments/11

On 2017-05-08T12:35:18+00:00 Gnome-4 wrote:

(In reply to Erkin Alp Güney from comment #6)
> >  For a spare time only hobby this might never get done.
> 
> Curtis, transferring

[Desktop-packages] [Bug 1603600] Re: NetworkManager ignores pushed openvpn routes

2019-10-15 Thread Torsten Bronger

[Re-posted because I accidentally clicked on “Post Comment”. Sorry for
that.]

Confirmed with Ubuntu 19.04. An

push "route 134.94.0.0 255.255.0.0 net_gateway"

is ignored. The pushed route is mentioned in the NetworkManager log:

NetworkManager[893]: […] Data: Static Route: 134.94.0.0/16
Next Hop: 134.94.16.1

(The gateway is even correct.) However, no route is actually added.
Interestingly enough, a

push "route 134.94.0.0 255.255.0.0 vpn_gateway"

*is* added to the routes. I suspect the device is wrong, because a
manual

# route add -net 134.94.0.0/16 gw 134.94.16.1 dev tun0
SIOCADDRT: Network is unreachable

fails obviously. Instead of “tun0”, it must be the normal net device
for which the gateway is valid. Possibly, NetworkManager tries to add
the route to “tun0” always, which would be wrong.

Is there an upstream bug report?

--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-openvpn in Ubuntu.
https://bugs.launchpad.net/bugs/1603600

Title:
NetworkManager ignores pushed openvpn routes

Status in network-manager-openvpn package in Ubuntu:
Confirmed

Bug description:
Relevant information that may or may not have been included by ubuntu-
bug:

Ubuntu release 16.04
Package network-manager 1.2.0-0ubuntu0.16.04.2
Package network-manager-openvpn 1.1.93-1ubuntu1

NetworkManager ignores pushed openvpn routes when "Use this connection
only for resources on its network" is checked. This is a behavior
change since 14.04.

To repeat:

1) Use an OpenVpn server that pushes routes. I suggest using a server
that pushes several routes since this makes their absence obvious.
Set up a NetworkManager VPN of type OpenVpn to this server. Select
"Use this connection only for resources on its network" in the
"Routes" section of the IPV4 options.

2) Set up a raw OpenVpn connection to the same server.

3) Connect to the server using the raw OpenVpn connection. The pushed
routes are all there.

4) Connect to the server using NetworkManager. The only route added
is a n interface level route to the tunnel device network.

Using the same setup on 14.04, all pushed routes are added.

The missing routes are also "Resources on the VPN network", and should be
added in the absence of further direction. Ignoring pushed routes should be
controlled by the "Ignore automatically obtained routes" checkbox.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: network-manager-openvpn 1.1.93-1ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: GNOME-Flashback:Unity
Date: Fri Jul 15 23:12:55 2016
InstallationDate: Installed on 2016-05-04 (72 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
SourcePackage: network-manager-openvpn
UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1603600/+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 1792932] Re: Desktop fails to boot in vbox: Xorg assert failure: Xorg: ../../../../dix/privates.c:384: dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed.

2019-10-15 Thread Gennady

Any fixes/updates for bionic?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1792932

Title:
  Desktop fails to boot in vbox:  Xorg assert failure: Xorg:
  ../../../../dix/privates.c:384: dixRegisterPrivateKey: Assertion
  `!global_keys[type].created' failed.

Status in X.Org X server:
  Unknown
Status in xorg-server package in Ubuntu:
  Fix Released
Status in xorg-server source package in Bionic:
  Confirmed
Status in xorg-server source package in Cosmic:
  Fix Released

Bug description:
  https://errors.ubuntu.com/problem/4ffab1fb339140b2c39fa0d096293706399e7280
  https://errors.ubuntu.com/problem/d18c1a21ca8ed1bb6cca06ddb5350187bed44f80

  ---

  Test Case:
  Boot Ubuntu Cosmic Desktop 20180916 on Virtual Box

  Actual Result
  Black screen or dropped to the login screen if the user skips ubiquity-dm

  Workaround:
  Add nomodeset on the kernel command line or from the boot menu, press F6 then 
select nomodeset

  Possibly a duplicate of bug 1432137

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: xserver-xorg-core 2:1.20.1-1ubuntu2
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  AssertionMessage: Xorg: ../../../../dix/privates.c:384: 
dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed.
  CasperVersion: 1.395
  CompositorRunning: None
  Date: Mon Sep 17 12:42:24 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter 
[80ee:beef] (prog-if 00 [VGA controller])
  LiveMediaBuild: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180916)
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth 
/run/user/999/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcEnviron:

  ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd ---  keyboard-configuration/layoutcode=fr 
keyboard-configuration/variantcode=oss
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
   __GI_abort () at abort.c:79
   __assert_fail_base (fmt=0x7f60fa1e3858 "%s%s%s:%u: %s%sAssertion `%s' 
failed.\n%n", assertion=0x563dbf96db7d "!global_keys[type].created", 
file=0x563dbf96db38 "../../../../dix/privates.c", line=384, function=) at assert.c:92
   __GI___assert_fail (assertion=0x563dbf96db7d "!global_keys[type].created", 
file=0x563dbf96db38 "../../../../dix/privates.c", line=384, 
function=0x563dbf96dde0 "dixRegisterPrivateKey") at assert.c:101
   dixRegisterPrivateKey ()
  Title: Xorg assert failure: Xorg: ../../../../dix/privates.c:384: 
dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.94-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1792932/+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 1603600] Re: NetworkManager ignores pushed openvpn routes

2019-10-15 Thread Torsten Bronger

Confirmed with Ubuntu 19.04. An

push "route 134.94.0.0 255.255.0.0 net_gateway"

is ignored. The pushed route is mentioned in the NetworkManager log:

--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-openvpn in Ubuntu.
https://bugs.launchpad.net/bugs/1603600

Title:
NetworkManager ignores pushed openvpn routes

Status in network-manager-openvpn package in Ubuntu:
Confirmed

Bug description:
Relevant information that may or may not have been included by ubuntu-
bug:

Ubuntu release 16.04
Package network-manager 1.2.0-0ubuntu0.16.04.2
Package network-manager-openvpn 1.1.93-1ubuntu1

NetworkManager ignores pushed openvpn routes when "Use this connection
only for resources on its network" is checked. This is a behavior
change since 14.04.

To repeat:

2) Set up a raw OpenVpn connection to the same server.

3) Connect to the server using the raw OpenVpn connection. The pushed
routes are all there.

4) Connect to the server using NetworkManager. The only route added
is a n interface level route to the tunnel device network.

Using the same setup on 14.04, all pushed routes are added.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1603600/+subscriptions

[Desktop-packages] [Bug 1837757] Re: adding extension caused libreoffice to fail loading on restart

2019-10-15 Thread Launchpad Bug Tracker

[Expired for libreoffice (Ubuntu) because there has been no activity for
60 days.]

** Changed in: libreoffice (Ubuntu)
   Status: Incomplete => Expired

-- 
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/1837757

Title:
  adding extension caused libreoffice to fail loading on restart

Status in libreoffice package in Ubuntu:
  Expired

Bug description:
  I had writer, calc and impress open. I clicked on the Language Tool extension 
here:
  https://extensions.libreoffice.org/extensions/languagetool/4.6

  I took the choice to add it to Libreoffice since it was open.
  The dialogue then said to restart Libroffice. 
  After closing, it would not restart.

  However, I just now clicked and downloaded the extension. After it
  downloaded, libreoffice began to restart.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: libreoffice-writer 1:6.2.5-0ubuntu0.19.04.1
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  Date: Wed Jul 24 11:42:41 2019
  InstallationDate: Installed on 2019-01-11 (194 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: 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/1837757/+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 1652282] Re: Xwayland not using XAUTHORITY, prevents root applications from connecting

** Bug watch added: bugzilla.gnome.org/ #776437
   https://bugzilla.gnome.org/show_bug.cgi?id=776437

** Changed in: gparted
   Importance: High => Unknown

** Changed in: gparted
   Status: Fix Released => Unknown

** Changed in: gparted
 Remote watch: GNOME Bug Tracker #776437 => bugzilla.gnome.org/ #776437

** No longer affects: gdm3 (Ubuntu)

** No longer affects: gnome-shell (Ubuntu)

** Project changed: ubuntu-gnome => ubuntu

** No longer affects: ubuntu

** Bug watch added: gitlab.gnome.org/GNOME/gdm/issues #342
   https://gitlab.gnome.org/GNOME/gdm/issues/342

** Changed in: gdm
   Importance: Medium => Unknown

** Changed in: gdm
   Status: Expired => Unknown

** Changed in: gdm
 Remote watch: GNOME Bug Tracker #789867 => gitlab.gnome.org/GNOME/gdm/issues 
#342

** Changed in: gparted (Ubuntu)
   Status: Invalid => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1652282

Title:
  Xwayland not using XAUTHORITY, prevents root applications from
  connecting

Status in gdm:
  Unknown
Status in GParted:
  Unknown
Status in Mutter:
  Fix Released
Status in gparted package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  When running wayland, GDM fails to set up an XAUTHORITY file and instead
  relies on the process UID for authentication.  This prevents
  applications run as root, like gparted or synaptic from connecting to
  the server.  GDM needs to set up the XAUTHORITY file when running
  Xwayland just like it does when it runs the conventional Xorg.

  A large list of applications broken by this can be found here:

  https://codesearch.debian.net/search?q=Exec%3Dsu-to-
  root+filetype%3Adesktop+path%3A*%2Fapplications%2F*=1

  openSUSE handles this issue with this patch (from the changelog, it looks 
like they implemented this for their YaST settings app):
  
https://build.opensuse.org/package/view_file/GNOME:Factory/mutter/mutter-xwayland-create-xauthority.patch?expand=1

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/1652282/+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 1839016] Re: Suspend process is interrupted by ALT key

2019-10-15 Thread Chih-Hsyuan Ho

** Summary changed:

- Suspend is iterrupted by ALT key
+ Suspend process is interrupted by ALT key

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1839016

Title:
  Suspend process is interrupted by ALT key

Status in OEM Priority Project:
  New
Status in OEM Priority Project bionic series:
  New
Status in gnome-shell package in Ubuntu:
  Fix Released

Bug description:
  When trying to suspend the system via pressing the power button in the
  system tray with ALT key pressed, it is possible to interrupt the
  system to enter sleep mode and fall back to screen lock. While trying
  to unlock the screen, the system goes to sleep immediately.

  Gnome-shell is able to suspend the system by drop-down menu in the
  system tray. By pressing ALT key or long-press the power button until
  it switches to suspend icon. The system will suspend if it is by the
  long-press power button, while with ALT key pressed, there is a
  failure rate that causes the suspend process to be interrupted.

  The second issue is that if the suspend process is interrupted, the
  locked screen is shown. While trying to unlock the screen by inputting
  password, the system will go sleeping after that.

  STEPS TO REPRODUCE:
  1. To suspend system via pressing the power button in the drop-down system 
tray with ALT key pressed.
  2. During system is going to sleep, e.g., screen going dark, emulate a key 
bounce by pressing ALT key again.

  RESULTS:
  The locked screen shows up and goes to sleep after tens of seconds. While 
trying to unlock screen, system enter suspend after unlocking successfully.

  EXPECTED RESULTS:
  The system going to sleep without a problem.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.4-0ubuntu18.04.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1839016/+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 1751593] Re: Weird black border flickers around windows in Wayland sessions

** Changed in: mutter
   Status: Unknown => New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1751593

Title:
  Weird black border flickers around windows in Wayland sessions

Status in GNOME Shell:
  Expired
Status in Mutter:
  New
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  Whenever I open any new window, a black border around the window
  appears for a fraction of a second (like a flicker).

  Although this doesn't happen very frequently, happens around 3-4 times
  out of 10. This is most noticeable when I right click on Desktop and
  click on "Open terminal". I can replicate this bug every time when I
  open terminal this way.

  Also, when I open terminal by pressing Control+Alt+T, the caption
  buttons kind of grey out after the flicker and are un-clickable. They
  look as if the window is not at focus. Workaround is to switch to
  another window (Alt+Tab) and then switch back to terminal.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb 25 19:58:24 2018
  InstallationDate: Installed on 2018-02-13 (11 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-legacy-bugs/+bug/1751593/+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 1751593] Re: Weird black border flickers around windows in Wayland sessions

** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #858
   https://gitlab.gnome.org/GNOME/mutter/issues/858

** Also affects: mutter via
   https://gitlab.gnome.org/GNOME/mutter/issues/858
   Importance: Unknown
   Status: Unknown

** Changed in: mutter (Ubuntu)
   Status: Confirmed => Triaged

** Changed in: gnome-shell (Ubuntu)
   Status: Confirmed => Invalid

** Tags added: eoan

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1751593

Title:
  Weird black border flickers around windows in Wayland sessions

Status in GNOME Shell:
  Expired
Status in Mutter:
  New
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  Whenever I open any new window, a black border around the window
  appears for a fraction of a second (like a flicker).

  Although this doesn't happen very frequently, happens around 3-4 times
  out of 10. This is most noticeable when I right click on Desktop and
  click on "Open terminal". I can replicate this bug every time when I
  open terminal this way.

  Also, when I open terminal by pressing Control+Alt+T, the caption
  buttons kind of grey out after the flicker and are un-clickable. They
  look as if the window is not at focus. Workaround is to switch to
  another window (Alt+Tab) and then switch back to terminal.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb 25 19:58:24 2018
  InstallationDate: Installed on 2018-02-13 (11 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-legacy-bugs/+bug/1751593/+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 1848285] Re: Nvidia Driver 340.107 Build Stalls at 100% (No Crash) for Linux Kernel 5.4.0-rc3

2019-10-15 Thread Ejmarkow

** Description changed:

  When building Nvidia Driver 340.107 for Linux Kernel 5.4.0-rc3, the
  compile permanently stalls on "Building NVIDIA kernel module" at 100%,
  but does not crash or proceed any further.
  
  NOTE: I used the Nvidia binary blob file (after all Ubuntu patches were
- applied) with a custom built Linux Kernel 5.3.0-rc8
+ applied) with a custom built Linux Kernel 5.4.0-rc3.
  
  nvidia-installer.log file is attached.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu.
https://bugs.launchpad.net/bugs/1848285

Title:
  Nvidia Driver 340.107 Build Stalls at 100% (No Crash) for Linux Kernel
  5.4.0-rc3

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  New

Bug description:
  When building Nvidia Driver 340.107 for Linux Kernel 5.4.0-rc3, the
  compile permanently stalls on "Building NVIDIA kernel module" at 100%,
  but does not crash or proceed any further.

  NOTE: I used the Nvidia binary blob file (after all Ubuntu patches
  were applied) with a custom built Linux Kernel 5.4.0-rc3.

  nvidia-installer.log file is attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1848285/+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 1848285] [NEW] Nvidia Driver 340.107 Build Stalls at 100% (No Crash) for Linux Kernel 5.4.0-rc3

2019-10-15 Thread Ejmarkow

Public bug reported:

When building Nvidia Driver 340.107 for Linux Kernel 5.4.0-rc3, the
compile permanently stalls on "Building NVIDIA kernel module" at 100%,
but does not crash or proceed any further.

NOTE: I used the Nvidia binary blob file (after all Ubuntu patches were
applied) with a custom built Linux Kernel 5.4.0-rc3.

nvidia-installer.log file is attached.

** Affects: nvidia-graphics-drivers-340 (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "nvidia-installer.log"
   
https://bugs.launchpad.net/bugs/1848285/+attachment/5297393/+files/nvidia-installer.log

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu.
https://bugs.launchpad.net/bugs/1848285

Title:
  Nvidia Driver 340.107 Build Stalls at 100% (No Crash) for Linux Kernel
  5.4.0-rc3

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  New

Bug description:
  When building Nvidia Driver 340.107 for Linux Kernel 5.4.0-rc3, the
  compile permanently stalls on "Building NVIDIA kernel module" at 100%,
  but does not crash or proceed any further.

  NOTE: I used the Nvidia binary blob file (after all Ubuntu patches
  were applied) with a custom built Linux Kernel 5.4.0-rc3.

  nvidia-installer.log file is attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1848285/+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 1848108] Re: [amdgpu] Screen Glitching & Kernel Panic

That last one in comment #7 does not look GPU related, but just
generally memory related. Maybe do a memtest just to be sure the RAM is
OK...

https://www.memtest.org/
https://www.memtest86.com/

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu.
https://bugs.launchpad.net/bugs/1848108

Title:
  [amdgpu] Screen Glitching & Kernel Panic

Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  I've recently updated to Eoan, but it seems like some nasty bugs came
  with it, particularly from the amdgpu package.

  It started with visual glitches but it would occasionally freeze the
  screen with whatever playing in the background and require me to hard-
  shutdown to escape. Attached is an abridged `journalctl -b -1` showing
  the lines were the kernal panic occurred. I'll probably attach more as
  they occur and if it's not redundant.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CompositorRunning: None
  Date: Mon Oct 14 21:27:34 2019
  DistUpgraded: 2019-10-13 05:03:20,327 DEBUG entry '# deb 
http://linux.teamviewer.com/deb stable main # disabled on upgrade to eoan' was 
disabled (unknown mirror)
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Very infrequently
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c3) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Raven Ridge [Radeon Vega Series / Radeon Vega Mobile 
Series] [17aa:506f]
  InstallationDate: Installed on 2019-03-22 (206 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 003: ID 13d3:56a6 IMC Networks Integrated Camera
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20KVCTO1WW
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-18-generic 
root=/dev/mapper/ubuntu--vg-root ro DEFAULT quiet splash ivrs_ioapic[32]=00:14.0
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to eoan on 2019-10-13 (1 days ago)
  dmi.bios.date: 12/07/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0UET68W (1.48 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KVCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0UET68W(1.48):bd12/07/2018:svnLENOVO:pn20KVCTO1WW:pvrThinkPadE585:rvnLENOVO:rn20KVCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E585
  dmi.product.name: 20KVCTO1WW
  dmi.product.sku: LENOVO_MT_20KV_BU_Think_FM_ThinkPad E585
  dmi.product.version: ThinkPad E585
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848108/+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 1848156] Re: Update gnome-terminal to 3.34.1

2019-10-15 Thread Jeremy Bicha

** Also affects: gnome-terminal (Ubuntu Eoan)
   Importance: Low
   Status: Fix Committed

** Changed in: gnome-terminal (Ubuntu Eoan)
   Status: Fix Committed => Triaged

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1848156

Title:
  Update gnome-terminal to 3.34.1

Status in gnome-terminal package in Ubuntu:
  Triaged
Status in gnome-terminal source package in Eoan:
  Triaged

Bug description:
  Please update to gnome-terminal 3.34.1 (or .2) for eoan.

  Or, at least, cherry-pick this trivial fix:
  https://gitlab.gnome.org/GNOME/gnome-
  terminal/commit/2cbc9e6b9be7f4d6b2d92b40e37ec687d36ce98d

  A change in GTK triggered a bug in Terminal causing a pretty bad user
  experience. A fullscreened terminal under Wayland doesn't retain its
  fullscreen status at certain operations, such as opening/closing a
  second tab, or zooming. Opening a second tab actually further grows
  the window as the tab bar appears, so that the bottom 1 or 2 text rows
  become invisible (out of screen).

  This issue was fixed in 3.34.1, along with two other minor issues and
  many translation updates. 3.34.2 brings another translation update
  only.

  Ubuntu usually aims to ship GNOME x.y.1. I assume there was no
  particular reason for not updating GNOME Terminal to .1 in this cycle,
  other than probably lack of time. I sincerely hope that the
  aforementioned UX regression convinces you to release a last minute
  fix for 19.10, or an update shortly afterwards. Thanks a lot!

  https://gitlab.gnome.org/GNOME/gnome-terminal/compare/3.34.0...3.34.2

  There is a standing microrelease exception for GNOME:
  https://wiki.ubuntu.com/StableReleaseUpdates#GNOME

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1848156/+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 1825741] Re: [upstream] Multiple instances of global menu entries

2019-10-15 Thread Ian Peters

This issue affects LibreOffice 6.3.2.2, the most recent version
available in the Ubuntu MATE 19.10 Beta.

** Attachment added: "Screenshot at 2019-10-15 22-10-36.png"
   
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1825741/+attachment/5297392/+files/Screenshot%20at%202019-10-15%2022-10-36.png

-- 
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/1825741

Title:
  [upstream] Multiple instances  of global menu entries

Status in LibreOffice:
  Fix Released
Status in libreoffice package in Ubuntu:
  Fix Committed

Bug description:
  I see 2 instances of each global menu entries.  It's cluttering up my
  top panel.

  This also happens in Plasma.

  Build ID: libreoffice-6.2.2.2-snap1

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1825741/+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 1847896] Re: Unable to shutdown or restart from log-in screen

** Tags added: fixed-in-243 fixed-upstream

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1847896

Title:
  Unable to shutdown or restart from log-in screen

Status in gnome-shell package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  When selecting the shutdown icon from the log-in screen you are
  prompted with a dialog that allows you to either cancel, restart or
  shutdown.

  It has been noted that the restart and shutdown options no longer
  work.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Oct 13 09:08:23 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-05-17 (148 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517)
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1847896/+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 1848119] Re: gnome-shell infinite error loop when closing app in activities overview: Object St.Button (0x55aeadeca4a0), has been already deallocated ... [workspace.js:695]

** Changed in: gnome-shell (Ubuntu)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

** Changed in: gnome-shell (Ubuntu)
   Status: Confirmed => In Progress

** Tags added: fixed-in-3.34.2 fixed-upstream

** Changed in: gnome-shell (Ubuntu)
   Status: In Progress => Triaged

** Changed in: gnome-shell (Ubuntu)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1848119

Title:
  gnome-shell infinite error loop when closing app in activities
  overview: Object St.Button (0x55aeadeca4a0), has been already
  deallocated ... [workspace.js:695]

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Triaged
Status in gnome-shell package in Fedora:
  Confirmed

Bug description:
  Ubuntu 19.10 on Xorg
  gnome-shell 3.34.1-1ubuntu1

  How to reproduce:
  1) Open terminal and watch journalct -f
  2) Open Files
  3) Close Files in the activities overview
  4) gnome-shell errors in journal non stop.

  Oct 14 23:25:38 titan gnome-shell[9919]: Object St.Button (0x55aeadeca4a0), 
has been already deallocated — impossible to get any property from it. This 
might be caused by the object having been destroyed from C code using something 
such as destroy(), dispose(), or remove() vfuncs.
  Oct 14 23:25:38 titan gnome-shell[9919]: == Stack trace for context 
0x55aead0b5360 ==
  Oct 14 23:25:38 titan gnome-shell[9919]: #0   55aeae6f3910 i   
resource:///org/gnome/shell/ui/workspace.js:695 (7f438c072c10 @ 15)
  Oct 14 23:25:38 titan gnome-shell[9919]: #1   7ffd96c5e360 b   
self-hosted:975 (7f438c12dee0 @ 392)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1848119/+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 1847551] Re: Mutter 3.34.1 broke Night Light, screen color profiles

2019-10-15 Thread Jeremy Bicha

No problem, I changed it back for you. 

** Changed in: mutter (Ubuntu)
   Status: Confirmed => Triaged

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1847551

Title:
  Mutter 3.34.1 broke Night Light, screen color profiles

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  Upgrading Mutter 3.34.0 to 3.34.1 has broken Night Light and screen
  color profile switching.  The commit at fault is
  104bdde746c9ceccd9e9ab09b22ef228b8f7026e “kms: Predict state changes
  when processing update” (which was intended to fix LP bug 1847044).

  Upstream issue: https://gitlab.gnome.org/GNOME/mutter/issues/851

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1847551/+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 1556439] Re: pulseaudio crashed with SIGABRT in pa_sink_input_assert_ref() from pa_sink_input_finish_move() from pa_sink_move_all_finish() from card_set_profile() from pa_card_

2019-10-15 Thread Chris Halse Rogers

Hello Anders, or anyone else affected,

Accepted pulseaudio into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/pulseaudio/1:11.1-1ubuntu7.4 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Tags removed: verification-done-bionic
** Tags added: verification-needed-bionic

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1556439

Title:
  pulseaudio crashed with SIGABRT in pa_sink_input_assert_ref() from
  pa_sink_input_finish_move() from pa_sink_move_all_finish() from
  card_set_profile() from pa_card_set_profile

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  Fix Committed
Status in pulseaudio source package in Cosmic:
  Fix Released
Status in pulseaudio source package in Disco:
  Fix Released
Status in pulseaudio source package in Eoan:
  Fix Released

Bug description:
  [Impact]

  https://errors.ubuntu.com/problem/a83a007593c81501c4fbb4e9ac0f47e0b3880d17

  This is one of the top pulseaudio crashes in Ubuntu 18.04 according to:
  
https://errors.ubuntu.com/?release=Ubuntu%2018.04=pulseaudio=year

  [Test Case]

  No manual test case known. Just watch errors.ubuntu.com to check for
  recurrences.

  [Regression Potential]

  Low. The fix is already in PulseAudio 12 so has been used in Ubuntu
  18.10 and later for a year so far.

  [Original Report]

  Changing between Logitech G933 digital and analog and Logitech G930
  digital and analog

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Uname: Linux 4.4.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset wl nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Mar 12 17:20:34 2016
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2016-02-22 (19 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  ProcEnviron:
   PATH=(custom, no user)
   SHELL=/bin/bash
   LANG=sv_SE.UTF-8
   LANGUAGE=sv
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   pa_sink_input_finish_move () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so
   pa_sink_move_all_finish () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so
   ?? () from /usr/lib/pulse-8.0/modules/module-alsa-card.so
   pa_card_set_profile () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so
   ?? () from /usr/lib/pulse-8.0/modules/libprotocol-native.so
  Title: pulseaudio crashed with SIGABRT in pa_sink_input_finish_move()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 09/30/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2001
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X99-DELUXE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2001:bd09/30/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnX99-DELUXE:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1556439/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   :

[Desktop-packages] [Bug 281053]

2019-10-15 Thread Qa-admin-q

Dear Christopher M. Penalver,

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open,
confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked
on this bug report. During that time, it's possible that the bug has
been fixed, or the details of the problem have changed. We'd really
appreciate your help in getting confirmation that the bug is still
present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of
LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information 
from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to 
RESOLVED-WORKSFORME and leave a comment that includes the information from Help 
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular 
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a 
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your 
bug pertains to a feature added after 3.3) from 
http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: 
https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

-- 
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/281053

Title:
  [Upstream] Math equation editor: "newline" fails after symbols

Status in LibreOffice:
  Confirmed
Status in OpenOffice:
  In Progress
Status in libreoffice package in Ubuntu:
  Confirmed
Status in openoffice.org package in Ubuntu:
  Won't Fix

Bug description:
  1) lsb_release -rd
  Description:  Ubuntu 11.10
  Release:  11.10

  2) apt-cache policy libreoffice-writer
  libreoffice-writer:
    Installed: 1:3.4.3-3ubuntu2
    Candidate: 1:3.4.3-3ubuntu2
    Version table:
   *** 1:3.4.3-3ubuntu2 0
  500 http://us.archive.ubuntu.com/ubuntu/ oneiric/main i386 Packages
  100 /var/lib/dpkg/status

  apt-cache policy libreoffice-math
  libreoffice-math:
    Installed: 1:3.4.3-3ubuntu2
    Candidate: 1:3.4.3-3ubuntu2
    Version table:
   *** 1:3.4.3-3ubuntu2 0
  500 http://us.archive.ubuntu.com/ubuntu/ oneiric/main i386 Packages
  100 /var/lib/dpkg/status

  3) What is expected to happen in LibreOffice Writer via the Terminal:

  cd ~/Desktop && wget
  
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/281053/+attachment/2417117/+files/math_newline_issue.tar.gz
  && file-roller -h math_newline_issue.tar.gz && cd math_newline_issue
  && lowriter -nologo math_newline_issue.odt

  is no upside down question marks are presented in the Math formulas.

  4) What happens is the upside down question marks are present
  erroneously due to "newline" command. If "newline" is preceded or
  followed by some characters (as +, -, =, which are often needed), some
  error marks "¿" are obtained, and perhaps only a single line if
  displayed (it depends on the character and its relative position to
  "newline"). Examples :

  a+b_ij = newline = c+d# single line; error mark
  a+b_ij newline = c+d  # two lines; missing "="; error mark
  a+b_ij newline + c+d  # correct behaviour !!  The "+" sign does fine 
after newline...
  a+b_ij + newline c+d # ... but not before: single line, error mark here
  a+b_ij = newline c+d # single line, error mark. The "=" sign does bad 
whether after or before newline

  WORKAROUND: {} newline {}

  ProblemType: Bug
  Architecture: i386
  Date: Fri Oct 10 03:31:54 2008
  DistroRelease: Ubuntu 8.04
  NonfreeKernelModules: nvidia
  Package: openoffice.org-core 1:2.4.1-1ubuntu2
  PackageArchitecture: i386
  ProcEnviron:
   
PATH=/usr/lib/openoffice/program:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  SourcePackage: openoffice.org
  Uname: Linux 2.6.24-19-rt i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/281053/+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 107854] Re: [upstream] Impress shows black underline in Slide Show despite colored underline

Launchpad has imported 26 comments from the remote bug at
https://bugs.documentfoundation.org/show_bug.cgi?id=37636.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2011-05-26T08:59:30+00:00 Christopher M. Penalver wrote:

Created attachment 47192
underline.odp

Downstream bug may be found at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/107854

OOo bug may be found at:
http://qa.openoffice.org/issues/show_bug.cgi?id=56520

1) lsb_release -rd
Description: Ubuntu 11.04
Release: 11.04

2) apt-cache policy libreoffice-impress
libreoffice-impress:
  Installed: 1:3.3.2-1ubuntu5
  Candidate: 1:3.3.2-1ubuntu5
  Version table:
 *** 1:3.3.2-1ubuntu5 0
500 http://us.archive.ubuntu.com/ubuntu/ natty-updates/main i386 
Packages
100 /var/lib/dpkg/status
 1:3.3.2-1ubuntu4 0
500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages

3) What is expected to happen in LibreOffice Impress via the Terminal:

cd ~/Desktop && wget
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/107854/+attachment/2143745/+files/underline.odp
&& loimpress -nologo underline.odp

the text with colored underlines should remain colored in Slide Show.

4) What happens instead is the underlines are black in Slide Show.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/107854/comments/2


On 2011-05-27T00:12:47+00:00 Tlillqvist-k wrote:

Impress, for Thorsten?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/107854/comments/5


On 2011-06-24T01:40:39+00:00 Libreoffice-z wrote:

[Reproducible] with Daily Build similar to "LibreOffice 3.4.1RC1 - WIN7
Home Premium (64bit) German UI [OOO340m1 (Build:101)]". Also Overlining
is affected as expected.

The problem also is visible for a WRITER text object in Presentation.

I modified Status to Assigned due to facts.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/107854/comments/7


On 2011-07-09T15:17:52+00:00 Cgiraud wrote:

Confirmed with LibreOffice 3.3.3 Impress on Win XP & Linux Mandriva 2010
x86.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/107854/comments/9


On 2011-12-23T13:25:49+00:00 Björn Michaelsen wrote:

Since all new unconfirmed bugs start in state UNCONFIRMED now and old
unconfirmed bugs were moved to NEEDINFO with a explanatory comment, all
bugs promoted above those bug states to NEW and later are automatically
confirmed making the CONFIRMED whiteboard status redundant. Thus it will
be removed.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/107854/comments/12


On 2012-02-28T11:26:44+00:00 Anastasius-zwerg wrote:

Still present in LibreOffice 3.5.0rc3 (Mac OS X 10.6.8 Intel Core i5)
Build ID: 7e68ba2-a744ebf-1f241b7-c506db1-7d53735

On well-designed slides the black underlining can look quite ugly.

Also I use underline colors to provide a visual link to different elements in a 
drawing having the same color; but I have to use color lines instead (which 
have to be modified each time the text is edited and thus shifted) - annoying.
I'd give it a higher priority.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/107854/comments/14


On 2013-01-15T17:17:16+00:00 Mozaic wrote:

Created attachment 73108
View on Slide Show mode: all text are black

Same problem with LibreOffice Version 4.0.0.0.beta2 (Build ID:
4104d660979c57e1160b5135634f732918460a0) on Ubuntu 12.04 x86_64

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/107854/comments/19


On 2013-01-15T17:19:53+00:00 Mozaic wrote:

Created attachment 73109
Noramal view with LibreOffice 4.0: text with color

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/107854/comments/21


On 2013-02-24T10:52:28+00:00 Björn Michaelsen wrote:

This bug seems to be a bit confused:
status ASSIGNED with no assignee is unhelpful, back to new, CC Thorsten.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/107854/comments/23


On 2013-09-18T04:26:44+00:00 chris wrote:

*** Bug 69475 has been marked as a

[Desktop-packages] [Bug 330117] Re: [Upstream] Shift+Tab indented bullet indents further

Launchpad has imported 15 comments from the remote bug at
https://bugs.documentfoundation.org/show_bug.cgi?id=049856.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2012-05-12T17:46:19+00:00 Freedesktop-treblig wrote:

Problem description: 
  When trying to edit a .ppt presentation (even one which was produced by 
libre) shift-tab on a second level bulleted list indents and switches to an odd 
bullet.

  This corresponds to Ubuntu bug: 
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/330117
  and OpenOffice bug : https://issues.apache.org/ooo/show_bug.cgi?id=99843

Steps to reproduce:
1) Open a shell, type libreoffice
2) You see a libreoffice window asking you what type of document you want, 
click 'presentation'
3) You now see an empty document with 'Click to add title' and a centred 'Click 
to add text', on the right there isa series of sections, Master Pages, Layouts, 
table Design. If 'layouts' isn't already open, click on the >Layouts to open it,
4) Click on the left most layout on the 2nd row - if you hover over it it says 
'Title, Content'. When you click the empty document changes so that the 'Click 
to add text' is now at the top left with a round bullet.
5) Click on 'Click to add title', type 'This is a title'
6) Now click on the 'Click to add text' and  and type 'Level 1' hit return
7) Now hit tab and type Level 2 hit return (as you hit tab the bullet changes 
to a -)
8) type More level 2 and hit return and then Yet more level 2
9) Now go to File->Save as, select a Filter: of Microsoft Powerpoint 
97/2000/XP/2003 (.ppt), type a filename (say broken2.ppt) and hit save
10) Convert the 'use Microsoft Powerpoint 97/2000/xp/2003 format' prompt
11) Exit libreoffice (File->Exit, click Discard when it prompts)
12) Now reopen libreoffice (e.g. at the terminal)
13) Use File->Open to open broken2.ppt
14) Click on the L of the 1st line that says Level 2 and then double click, the 
'Level 2' is now inverted to show it's highlighted.
15) Hit shift-tab

step 15 now shows the bug -

Current behavior:
the text incorrectly moves to the right and a bullet >> is shown. 

Expected behavior:
   it should be moving to the left and the bullet should match the 1st level 
bullet. Note this happens if you don't go through a .ppt format at any stage.

Platform (if different from the browser): 
  
Browser: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.19 (KHTML, like Gecko) 
Ubuntu/12.04 Chromium/18.0.1025.168 Chrome/18.0.1025.168 Safari/535.19

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/330117/comments/13


On 2013-04-27T09:15:58+00:00 Stgohi-lobugs wrote:

I am not sure if this is a misunderstanding.  For me it seemed to behave
as normal (with LO 4.0.2.2 [Win7 Home, 64bit]).  If I press the
tabulator key it should move to the right, to the next level with a
bullet.  Why should it therefore move to the left?  Is this maybe a
misunderstanding from side?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/330117/comments/28


On 2013-04-27T15:57:47+00:00 Freedesktop-treblig wrote:

Note step 15 is asking for 'shift tab' - not plain tab
  Plain tab goes to the right,
  Shift-tab should go to the left

Indeed shift-tab works fine in most cases, but this case it doesn't work
and goes the wrong way.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/330117/comments/30


On 2013-04-27T16:38:24+00:00 Stgohi-lobugs wrote:

@Dave: Thank you very much for your hint.

I never used this shortcut key and was not aware of it.  But I tested it
in other presentations and I can confirm if you use Shift Key +
Tabulator Key then it moves left, but in this specific case here it
moves right.

reproducible with LO 4.0.2.2 (Win7 Home, 64bit)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/330117/comments/32


On 2013-04-29T13:39:41+00:00 Itamar Carvalho wrote:

I just tested it in LibreOffice Version 3.6.4.3 (Version ID: 2ef5aff) in
Windows, and I can confirm this version and platform is also affected by
this bug. My version is in Portuguese (Brazil) language.

I know this is not the latest version, there is already the 3.6.6
version in 3.6 branch and that 4.0.2 is already available. I'm
downloading the 4.0.2 version and I will test again, but AFAIK this bug
was not addressed by this release.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/330117/comments/34

[Desktop-packages] [Bug 253670] Re: [upstream] Draw exporting .odg to .eps removes inserted image

Launchpad has imported 9 comments from the remote bug at
https://bugs.documentfoundation.org/show_bug.cgi?id=37773.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2011-05-30T18:40:39+00:00 Christopher M. Penalver wrote:

Created attachment 47344
EPS.odg

Downstream bug may be found at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/253670

OOo bug may be found at:
http://qa.openoffice.org/issues/show_bug.cgi?id=47237

1) lsb_release -rd
Description: Ubuntu 11.04
Release: 11.04

2) apt-cache policy libreoffice-draw
libreoffice-draw:
  Installed: 1:3.3.2-1ubuntu5
  Candidate: 1:3.3.2-1ubuntu5
  Version table:
 *** 1:3.3.2-1ubuntu5 0
500 http://us.archive.ubuntu.com/ubuntu/ natty-updates/main i386 
Packages
100 /var/lib/dpkg/status
 1:3.3.2-1ubuntu4 0
500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages

apt-cache policy unoconv
unoconv:
  Installed: 0.3-6
  Candidate: 0.3-6
  Version table:
 *** 0.3-6 0
500 http://us.archive.ubuntu.com/ubuntu/ natty/universe i386 Packages
100 /var/lib/dpkg/status

3) What is expected to happen in LibreOffice Draw via the Terminal:

cd ~/Desktop && wget
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/253670/+attachment/364486/+files/EPS.odg
&& unoconv --listener && unoconv -f eps EPS.odg && lodraw -nologo
EPS.odg EPS.eps

the two files look the same.

4) What happens instead is the image at the bottom right of EPS.eps
disappears.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/253670/comments/19


On 2011-12-23T12:06:41+00:00 Björn Michaelsen wrote:

[This is an automated message.]
This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it
started right out as NEW without ever being explicitly confirmed. The bug is
changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back
to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 
prereleases.
Details on how to test the 3.5.0 beta1 can be found at:
http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1

more detail on this bulk operation: http://nabble.documentfoundation.org
/RFC-Operation-Spamzilla-tp3607474p3607474.html

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/253670/comments/22


On 2012-01-03T18:55:54+00:00 Christopher M. Penalver wrote:

Reproducible in:
LOdev 3.5.0beta2 
Build ID: 8589e48-760cc4d-f39cf3d-1b2857e-60db978
Microsoft Windows Vista Business 6.0.6002 Service Pack 2 Build 6002

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/253670/comments/23


On 2013-09-01T12:19:03+00:00 Ywd wrote:

Christopher, is this bug still valid / reproducible with the latest LO
release from http://www.libreoffice.org/download/ ?

When I open your example file I have no option to save to .eps file
format. Maybe this option was removed, which would make this bug a
wontfix?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/253670/comments/26


On 2013-09-01T12:50:33+00:00 Christopher M. Penalver wrote:

James, thanks for checking in. Unfortunately, the situation has gotten worse, 
as a regression in displaying the original .odg occurred with:
Microsoft Windows Vista Business x86 6.0.6002 Service Pack 2 Build 6002
Version: 4.1.1.2
Build ID: 7e4286b58adc75a14f6d83f53a03b6c11fa2903

instead of showing a squiggly line at the bottom right, it shows
nothing.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/253670/comments/28


On 2015-04-01T14:42:18+00:00 Qa-admin-q wrote:

** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open,
confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked
on this bug report. During that time, it's possible that the bug has
been fixed, or the details of the problem have changed. We'd really
appreciate your help in getting confirmation that the bug is still
present.

If you have time, please do the following:

   *Test to see if the bug is still present on a currently supported version of 
LibreOffice (4.4.1 or later)
   https://www.libreoffice.org/download/

   *If the bug is present, please leave a comment that includes

[Desktop-packages] [Bug 1834138] Re: PA: Don't restore the streams to sinks/sources with only unavailable ports

2019-10-15 Thread Chris Halse Rogers

Hello Hui, or anyone else affected,

Accepted pulseaudio into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/pulseaudio/1:11.1-1ubuntu7.4 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: pulseaudio (Ubuntu Bionic)
   Status: Incomplete => Fix Committed

** Tags added: verification-needed-bionic

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1834138

Title:
  PA: Don't restore the streams to sinks/sources with only unavailable
  ports

Status in HWE Next:
  New
Status in OEM Priority Project:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  Fix Committed
Status in pulseaudio source package in Disco:
  Fix Committed
Status in pulseaudio source package in Eoan:
  Fix Released

Bug description:
  SRU Document:

  [Impact]

  The Lenovo P520 machine has dual analogue codecs, so there are two
  sinks and two sources in the PA, one has the front headphone and front
  microphone, the other has the rear lineout, linein and rear
  microphone, and the rear microphone always shows up in the gnome-
  sound-setting, When we plug a microphone to front audio jack, there
  are two input devices: rear mic and front mic in the gnome-sound-
  setting, and suppose users select the the front mic to record sound
  via audio app like arecord, the front mic will be bond the arecord,
  after the front mic is unplugged, there is only one rear mic left in
  the gnome-sound-setting, but the binding will not be changed, the
  arecrod still bind to front mic, under this situation if users record
  sound via arecord, they will find they can't record any sound from any
  other input devices even they are listed in the gnome-sound-setting.
  This problem also happens to output devices too.

  [Test Case]

  After applying this patch, I did the same test: unplug the front mic,
  then use the arecord to record sound, the app can record sound from
  rear mic now. After I plug the front mic back, the arecord still
  record from front mic. Also did the similar test for output devices,
  it worked as expected too.

  [Regression Potential]

  Low, Just make a simple check when creating new streams
  (sink_input/source_output), If the restored device (sink/source) has
  ports and all ports are unavialble, it will not restore the binding,
  otherwise it will work as before.

  For the Bionic, This SRU also includes the fix of LP: #1556439, this
  fix is safe and is very low possible to introduce any regression too,
  because it just adds a sink-input/source-output state checking, if the
  sink-input/source-output is unlinking or unlinked, it is useless to
  move it to a new sink/source, furthermore it will trigger an assertion
  that make the pulseaudio crash, adding this check can fix this problem
  (LP: #1556439).

  [Other Info]

  No more info here

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1834138/+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 1093765] Re: [upstream] switching paragraph style changes character orientation

Launchpad has imported 9 comments from the remote bug at
https://bugs.documentfoundation.org/show_bug.cgi?id=58070.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

On 2012-12-10T08:07:33+00:00 Inkbug wrote:

Steps to reproduce:
1. Create new paragraph
2. Change paragraph direction to RTL
3. Change paragraph style to Heading 1

Current Behavior:
The paragraph becomes a heading but switches back to LTR direction.

Expected Behavior:
The paragraph becomes a heading but stays RTL.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1093765/comments/0

On 2013-05-29T11:09:00+00:00 Christopher M. Penalver wrote:

Created attachment 79954
Downstream attachment

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1093765/comments/10

On 2013-05-29T11:27:54+00:00 Christopher M. Penalver wrote:

As per downstream report
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1093765 :

1) lsb_release -rd
Description: Ubuntu 13.04
Release: 13.04

2) apt-cache policy libreoffice-writer
libreoffice-writer:
  Installed: 1:4.0.2-0ubuntu1
  Candidate: 1:4.0.2-0ubuntu1
  Version table:
 *** 1:4.0.2-0ubuntu1 0
500 http://archive.ubuntu.com/ubuntu/ raring/main i386 Packages
100 /var/lib/dpkg/status

3) What is expected to happen in Writer via a terminal:
cd ~/Desktop && wget 
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1093765/+attachment/3688368/+files/test-bug1093765.doc
 && lowriter --nologo test-bug1093765.doc

is select all -> change combo box Apply Style from Text Body to Heading
1 and the text style changes, preserving the character order.

4) What happens instead is:
(Example text=) טקסט לדוגמה

changes to:
טקסט לדוגמה (=Example text)

Microsoft Office Professional Plus 2010 Word Version 14.0.6023.1000 (32-bit) 
changes it to:
=)טקסט לדוגמהExample text(

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1093765/comments/11

On 2015-03-04T02:21:25+00:00 Qa-admin-q wrote:

** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open,
confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked
on this bug report. During that time, it's possible that the bug has
been fixed, or the details of the problem have changed. We'd really
appreciate your help in getting confirmation that the bug is still
present.

If you have time, please do the following:

Test to see if the bug is still present on a currently supported version
of LibreOffice (4.4.1.2 or later): https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the version
of LibreOffice and your operating system, and any changes you see in the
bug behavior

If the bug is NOT present, please set the bug's Status field to
RESOLVED-WORKSFORME and leave a short comment that includes your version
of LibreOffice and Operating System

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular 
meaning that is not appropriate in this case)

Thank you for your help!

-- The LibreOffice QA Team
This NEW Message was generated on: 2015-03-03

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1093765/comments/12

On 2015-03-22T14:12:31+00:00 Beluga wrote:

(In reply to Inkbug from comment #0)
> Steps to reproduce:
> 1. Create new paragraph
> 2. Change paragraph direction to RTL
> 3. Change paragraph style to Heading 1
> 
> Current Behavior:
> The paragraph becomes a heading but switches back to LTR direction.
> 
> Expected Behavior:
> The paragraph becomes a heading but stays RTL.

Reproduced.

Win 7 Pro 64-bit, LibO Version: 4.4.1.2
Build ID: 45e2de17089c24a1fa810c8f975a7171ba4cd432
Locale: fi_FI

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1093765/comments/13

On 2016-01-04T11:39:56+00:00 Beluga wrote:

*** Bug 96859 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1093765/comments/14

On 2017-11-03T01:31:37+00:00 Omer Zak wrote:

Still

[Desktop-packages] [Bug 1349078] Re: [upstream] Impress FORMATTING: Slide master fields are duplicated when saving to .fodp

Launchpad has imported 32 comments from the remote bug at
https://bugs.documentfoundation.org/show_bug.cgi?id=50216.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

On 2012-05-22T08:08:49+00:00 Fritz-paul wrote:

Whenever an Impress presentation with activated header/footer fields
(Daten and time, Footer, and Slide number) is stored, these default
fields are duplicated. This also happened for me to the object area for
Auto Layouts in the slide master. The effect can be seen with a blank
presentation with the fields activated.

It is possible to remove the header/footer fields from the slide master
and use own fields instead. But those can't be modified via the default
menu points and they must be changed for each master slide.

The bug is rather annoying because apart from that, the flat odx formats
help with many small issues in conjunction with Subversion repositories.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1349078/comments/1

On 2012-09-29T10:34:34+00:00 Reisi007 wrote:

Can't confirm it @ Win7 x64 3.6.1.2

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1349078/comments/3

On 2012-10-01T09:30:39+00:00 Fritz-paul wrote:

Created attachment 67915
example odp file

This is the original odp file. Saving this to an .fodp file results in
doubled footer items. Saving the .fodt again results in tripled footer
items.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1349078/comments/5

On 2012-10-01T09:31:57+00:00 Fritz-paul wrote:

Created attachment 67916
fodt file generated by saving the example odt file to fodt

The footer items are doubled.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1349078/comments/7

On 2012-10-01T09:33:38+00:00 Fritz-paul wrote:

(In reply to comment #1)
> Can't confirm it @ Win7 x64 3.6.1.2

Sorry, still doesn't work for me (Win7 x64 3.6.1.2). I added two test
files showing the problem.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1349078/comments/9

On 2012-10-01T10:37:30+00:00 Reisi007 wrote:

Thanks for your quick reply...

Could you rename %appdata%\libreoffice\3\user and restart libo...

If the problem persists: Comment
If not PLEASE Upload the user profile (Keep in mind, there is private data in 
there!)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1349078/comments/11

On 2012-10-02T07:58:48+00:00 Fritz-paul wrote:

(In reply to comment #5)
> Thanks for your quick reply...
> 
> Could you rename %appdata%\libreoffice\3\user and restart libo...
> 
> If the problem persists: Comment
> If not PLEASE Upload the user profile (Keep in mind, there is private data
> in there!)

Sorry, the problem is still there. With the new profile I generated a
new empty presentation, activated the footers and stored it as .fodt
with the same result, duplicated footers.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1349078/comments/13

On 2012-12-17T10:37:24+00:00 Fritz-paul wrote:

The problem still persists in version 3.6.4.3 (Win7, 64). I also find it
in Linux, version 3.5.4.2.

Just open the attached odp file, save it as fodt and do a reload ...

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1349078/comments/15

On 2013-11-13T11:38:37+00:00 Mhossbach wrote:

On Linux 64-bit (Linux 3.10.7-gentoo-r1 x86_64) still present.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1349078/comments/17

On 2013-11-19T18:01:52+00:00 Reisi007 wrote:

Version is OLDEST affected...
Changed platfor as well

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1349078/comments/19

On 2014-07-26T16:38:51+00:00 Ｖ字龍(Vdragon) wrote:

Hi, I can also reproduce this bug on my system(Ubuntu 14.04LTS x86 4.2.4.2)
Adding my own example file and user profile.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1349078/comments/21

On

[Desktop-packages] [Bug 923932] Re: [Classic session] LibreOffice icons are larger than other app's icons

Launchpad has imported 16 comments from the remote bug at
https://bugs.documentfoundation.org/show_bug.cgi?id=53505.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

On 2012-08-14T20:23:30+00:00 Sanchit Gangwar wrote:

Created attachment 65566
Screenshot of icons.

When using gnome-session-fallback (GNOME Classic session / gnome-panel)
then LibreOffice icons are much larger image dimensions than the other
icons in the menu.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/923932/comments/16

On 2012-08-15T14:01:44+00:00 Michael-meeks-1 wrote:

As I recall you(?) were asking on IRC how to help fix it - by installing
smaller icons, or somesuch ?

It's entirely possible that our icons are the same size, and simply fill
the surrounding bbox too well - where other icons leave space for
shadows / other features (?) Or it could be that they are simple larger.

Thoughts / investigation appreciated.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/923932/comments/19

On 2012-08-15T16:09:36+00:00 Stefan K. wrote:

Can confirm on OpenSUSE 12.1... so probably not a Ubuntu packaging bug. We 
probably really lack a certain icon size.
It's also a bit odd that the menu doesn't force the icon into place... so, 
maybe it would be a good idea to file the bug at Gnome additionally.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/923932/comments/21

On 2012-08-15T16:44:05+00:00 Sanchit Gangwar wrote:

(In reply to comment #1)
> As I recall you(?) were asking on IRC how to help fix it - by installing
> smaller icons, or somesuch ?
> 
> It's entirely possible that our icons are the same size, and simply fill the
> surrounding bbox too well - where other icons leave space for shadows / other
> features (?) Or it could be that they are simple larger.
> 
> Thoughts / investigation appreciated.

Yes, I'm the same. In fact, I resized the icons to the appropriate size,
but the guys at Ubuntu told me to send this bug upstream.

As for the problem, yes, it is genuine. The icons available are 16x16,
32x32, 48x48, and so on. The 24x24 icons are missing, hence the gnome-
panel uses 32x32. You need to include 24x24 icons.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/923932/comments/23

On 2012-08-16T04:08:20+00:00 Sanchit Gangwar wrote:

Created attachment 65624
A proposed patch.

Here is the patch, I created.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/923932/comments/26

On 2012-08-16T04:09:20+00:00 Sanchit Gangwar wrote:

Created attachment 65625
24x24 icons

These are the 24x24 icons which are currently missing.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/923932/comments/28

On 2012-09-03T12:11:12+00:00 Stefan K. wrote:

Hi Sanchit,

I am sorry, but your icons are not pixel-aligned -- meaning the horizontal and 
vertical lines in the icons are rather squishy/fuzzy. It is a better idea to 
use the official SVG icons from [1], scale the 32*32 icon down and then make 
sure the everything is aligned neatly. (In Inkscape, you can use the # key to 
enable the pixel raster. Under View > Icon Preview you can also enable a 
smaller preview.)
Can you try reworking those icons in this way?

[1] http://wiki.documentfoundation.org/File:LibreOffice_Initial_Icons-
pre_final.svg

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/923932/comments/31

On 2012-09-03T15:45:51+00:00 Sanchit Gangwar wrote:

Sure I'll submit a patch as soon as possible.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/923932/comments/33

On 2012-09-18T13:06:44+00:00 Sanchit Gangwar wrote:

Created attachment 67327
24x24 hicolor icons

I've added 24x24 icons again. Please have a look.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/923932/comments/35

On 2012-12-20T20:06:25+00:00 Björn Michaelsen wrote:

Comment on attachment 67327
24x24 hicolor icons

@Astron: ping? Could you recheck?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/923932/comments/37

[Desktop-packages] [Bug 1192599] Re: [upstream] writer: zoom fraction changes when clicking on figures

Launchpad has imported 10 comments from the remote bug at
https://bugs.documentfoundation.org/show_bug.cgi?id=36976.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2011-05-08T12:28:59+00:00 G-sh wrote:

Best advice I could find for sending feature request was in a couple
threads saying do it via bug report. If I'm wrong, please forward to the
right recipient.

Using Mac OS 10.6.7

When working with an object--image, frame, or whatever--on a page in any
LO app, activating the object also pops up a toolbar associated with the
object. Sometimes it's across the top or side of the window, other times
it pops up right in front of everything. Most of the time I don't need
the toolbar (just moving or resizing something for example), and it's
distracting and annoying to have these toolbars popping up all over the
place. I know where to go to view Drawing or Picture or Text Object
toolbar, so I'd like to turn off this auto popup. Please add this as an
Option across the suite?

Many thanks for all your great work on LO!

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1192599/comments/12


On 2012-06-17T06:43:47+00:00 aM wrote:

I second that. It's really annoying for me, too.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1192599/comments/17


On 2012-10-05T09:00:51+00:00 Wugs wrote:

I second this. I have tried to make the Summary clearer (no hints about
“Feature request” or “all about the suite” are necessary, this is all
indicated by the Component and Importance fields). Platform should be
All/All.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1192599/comments/26


On 2012-12-22T04:23:05+00:00 Lemoyne-castle wrote:

Must have been feeling it when I assigned this to myself.  Still
interested in this enhancement, but in no way is this area a strong
point for me - crucially, I have not been and will not start working on
this issue right now.  Assigned back to default developer.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1192599/comments/27


On 2013-02-28T06:14:13+00:00 Snlr wrote:

Workaround posted in forums 1): hide the popup in existing toolbar, so
at least it's not too annyoing. Pop up cannot be prevented. This
workaroung does not work when user chose to not display any toolbars.
(Which is different from full screen, because navigator and style window
can still be used).

Workaround posted in forums 2): go to View > Toolbars > disable the
offending toolbar, LO will memorize the setting. Does NOT work, LO does
NOT memorize the setting and pops up the toolbar again. Example:
navigator toolbar. Jumping to an outline pops up the toolbar, user
closes the toolbar, jumps to next outline, toolbar pops up again.

The popping never ends. A setting is needed to ONLY EVER show the
toolbar when the user selected View > Toolbar > activate certain
toolbar, and to NEVER show the toolbar in question when the user
DESELECTED it in View > Toolbar.

The user will then choose freely when to use a toolbar and when not to.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1192599/comments/40


On 2016-06-12T08:48:52+00:00 Heiko-tietze-g wrote:

*** Bug 100314 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1192599/comments/56


On 2017-07-23T23:42:04+00:00 Vstuart-foote wrote:

*** Bug 109291 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1192599/comments/57


On 2017-07-28T20:14:15+00:00 Maartje2405 wrote:

Created attachment 134953
exapmle of navigation toolbar popping up

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1192599/comments/58


On 2018-10-13T14:20:39+00:00 Beluga wrote:

*** Bug 119998 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1192599/comments/59


On 2018-12-13T11:54:33+00:00 Xiscofauli wrote:

*** Bug 34451 has been marked as a duplicate of this bug. ***

Reply at:

[Desktop-packages] [Bug 375395] Re: [Upstream] scrolling only by full line height

Launchpad has imported 13 comments from the remote bug at
https://bugs.documentfoundation.org/show_bug.cgi?id=40917.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2011-09-15T12:20:20+00:00 Коренберг Марк wrote:

If I have spreadsheet document with large, multiline cells, I can't
scroll to distance equal some part of line. full line is scrolled at
once. There is no option in preferences about scrolling by line (as in
Excel) and scrolling by pixels (as in Word). Please add such option, or
tell me where to find it, if it exists.

The original from:
(https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/375395)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/375395/comments/31


On 2011-09-15T22:23:18+00:00 Libreoffice-z wrote:

I believe this is more or less a DUP of "Bug 34689 - UI scroll problem:
Cell with dimensions exceeding screen dimensions impossible to work
with".

@Коренберг Марк:
Do you agree?

Please file Bug reports with status UNCONFIRMED if your are not
absolutely sure that it's not a DUPlicate, that you contributed all
required background information, that the problem will be reproducible
with information you can provide or that your enhancement request will
be accepted! Thank you!

May be you can test
 for submitting
bug reports?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/375395/comments/34


On 2011-09-16T03:00:37+00:00 Коренберг Марк wrote:

Yes, this two bugs are connected. But they are different.

My bug specify that scrolling is always jumpy. 
Bug 34689 is in impossibility to scroll large cells.

If smooth scrolling will be implemented, both bugs will be closed.

Closing Bug 34689 may be implemented in another way.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/375395/comments/35


On 2011-12-23T12:35:20+00:00 Björn Michaelsen wrote:

[This is an automated message.]
This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it
started right out as NEW without ever being explicitly confirmed. The bug is
changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back
to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 
prereleases.
Details on how to test the 3.5.0 beta1 can be found at:
http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1

more detail on this bulk operation: http://nabble.documentfoundation.org
/RFC-Operation-Spamzilla-tp3607474p3607474.html

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/375395/comments/38


On 2011-12-23T17:01:56+00:00 Björn Michaelsen wrote:

needinfo keyword redundant by needinfo status.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/375395/comments/39


On 2012-08-14T14:02:19+00:00 Reisi007 wrote:

Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer
within the last six months, we close all of these bugs.

To keep this message short, more infos are available @
https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that
everything is prepared for developers to fix your problem.

Yours!

Florian

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/375395/comments/42


On 2012-08-14T14:03:19+00:00 Reisi007 wrote:

Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer
within the last six months, we close all of these bugs.

To keep this message short, more infos are available @
https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that
everything is prepared for developers to fix your problem.

Yours!

Florian

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/375395/comments/43


On 2012-08-14T14:07:53+00:00 Reisi007 wrote:

Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer
within the last six months, we close all of these bugs.

To keep this message short, more infos are available @
https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for

[Desktop-packages] [Bug 1133443] Re: LibreOffice loses its settings at every distribution upgrade

Launchpad has imported 4 comments from the remote bug at
https://bugs.documentfoundation.org/show_bug.cgi?id=61509.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2013-02-26T14:00:26+00:00 Teo wrote:

Problem description:

Every damn time I upgrade Ubuntu, I have to carefully tune up LibreOffice Calc 
settings so that I can enter dates as DD/MM/ instead of MM/DD/. I never 
remember how I do it, I always have to figure out
(alse see another bug I reported: the way dates are input should match the way 
they are represented in the cell where you input them).

Then when I upgrade the Ubuntu distribution (e.g. 11.10 to 12.04, 12.04 to 
12.10) this thing gets SYSTEMATICALLY reset and I have to figure it out and 
change the settings again.
Every f***ing time.


Operating System: Ubuntu
Version: unspecified

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1133443/comments/1


On 2013-02-26T14:37:19+00:00 Pje335-lo wrote:

Dear matteo sisti sette I know what you mean and yes it is annoying, but
this isn't our bug because I think LibreOffice is just reinstalt. so I
set it to NOT OUR BUG.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1133443/comments/3


On 2013-02-26T16:36:48+00:00 Teo wrote:

Well, this happens only with LibreOffice and not with other tons of
packages I have installed. None or almost none of them looses its
settings when I do a distribution upgrade.

So I think you need to distribute the updates in the proper manner or
whatever.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1133443/comments/5


On 2013-02-26T16:40:07+00:00 Teo wrote:

I've reported it in the Ubuntu launchpad
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1133443

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1133443/comments/8


** Changed in: df-libreoffice
   Status: Unknown => Won't Fix

** Changed in: df-libreoffice
   Importance: Unknown => Medium

-- 
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/1133443

Title:
  LibreOffice loses its settings at every distribution upgrade

Status in LibreOffice:
  Won't Fix
Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  See this report: https://bugs.freedesktop.org/show_bug.cgi?id=61509

  They say it's not "their bug", so either they are wrong or it's a bug
  in the way it is packaged for/in/with/by Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 3.5.0-25.38-generic 3.5.7.4
  Uname: Linux 3.5.0-25-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu10
  Architecture: i386
  Date: Tue Feb 26 17:37:27 2013
  InstallationDate: Installed on 2010-06-23 (979 days ago)
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to quantal on 2013-01-13 (44 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1133443/+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 1412448] Re: Calc wrap text setting in Cell Formatting not persisted

Launchpad has imported 6 comments from the remote bug at
https://bugs.documentfoundation.org/show_bug.cgi?id=097106.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2016-01-13T18:35:46+00:00 piratemurray wrote:

Created attachment 121905
Example spreadsheet

NB: Originally reported to Ubuntu bug tracker but was asked to post it
upstream.
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1412448

When editing an XLS in Libreoffice Calc, the wrap text automatically
setting in the cell formatting is not persisted across saves. Attached
is a test spreadsheet with a long string of text in cell A1.

Steps to reproduce:
1) Right click cell and go to Format Cells
2) Select Alignment tab
3) Unselect Wrap Text Automatically
4) Press OK
5) Save spreadsheet selecting to keep the XLS format if asked
6) Close spreadsheet
7) Reopen spreadsheet

Expected Result:
When the spreadsheet is reopened cell A1 has remembered that the text is NOT to 
be wrapped.

Actual Result:
Cell A1 is once again wrapped

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1412448/comments/4


On 2016-01-13T19:13:01+00:00 Cno wrote:

Thanks for filing, mez.pahlan.
I confirm the problem.
But it's not wrapping per see that is forgotten, I think.

It looks related to the issues
bug 34717, and bug 32950
Especially the latter looks suspicious. Could it be the same?

Ciao - Cor

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1412448/comments/7


On 2016-01-13T19:58:56+00:00 piratemurray wrote:

Hi Cor

No problem.

Bug 32950 certainly looks very related. I'm afraid I don't know enough
about that bug or the code to say for sure. But on first glance it does.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1412448/comments/9


On 2017-05-22T13:19:50+00:00 Qa-admin-q wrote:

** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open,
confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked
on this bug report. During that time, it's possible that the bug has
been fixed, or the details of the problem have changed. We'd really
appreciate your help in getting confirmation that the bug is still
present.

If you have time, please do the following:

Test to see if the bug is still present on a currently supported version of 
LibreOffice 
(5.2.7 or 5.3.3  https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the version of 
LibreOffice and 
your operating system, and any changes you see in the bug behavior
 
If the bug is NOT present, please set the bug's Status field to 
RESOLVED-WORKSFORME and leave 
a short comment that includes your version of LibreOffice and Operating System

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular 
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a 
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your 
bug pertains to a feature added after 3.3)

http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to "inherited from OOo";
4b. If the bug was not present in 3.3 - add "regression" to keyword


Feel free to come ask questions or to say hello in our QA chat: 
http://webchat.freenode.net/?channels=libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug-20170522

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1412448/comments/10


On 2017-05-24T20:14:56+00:00 piratemurray wrote:

Still present

Ubuntu 17.04

Version: 5.3.3.2
Build ID: 1:5.3.3~rc2-0ubuntu0.17.04.1~lo0
CPU Threads: 4; OS Version: Linux 4.10; UI Render: default; VCL: gtk3; Layout 
Engine: new; 
Locale: en-GB (en_GB.UTF-8); Calc: group

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1412448/comments/11


On 2018-05-25T02:43:20+00:00 Qa-admin-q wrote:

** Please read this

[Desktop-packages] [Bug 903608] Re: [Upstream] LibreOffice text remains superscript if typed right after footnote

Launchpad has imported 10 comments from the remote bug at
https://bugs.documentfoundation.org/show_bug.cgi?id=043763.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2011-12-12T13:15:27+00:00 Ivan Kharlamov wrote:

Problem description:

If you are editing some files which were created in MS Word(it doesn't
matter if you re-save them in .odt or not), which have superscript
position in footnote character styles, text remains in superscript if
inserted right after footnote characters.

Steps to reproduce:
1. Open an attached MS Word file
2. Type text right after footnote, see that it remains superscript

Current behavior:

Text style remains superscript if text is inserted right after footnote.

Expected behavior:

Text style must change to default.

Same issue was reported here by someone else:
http://www.oooforum.org/forum/viewtopic.phtml?t=127834

Platform (if different from the browser): 
  
Browser: Mozilla/5.0 (Ubuntu; X11; Linux x86_64; rv:8.0) Gecko/20100101 
Firefox/8.0

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/903608/comments/0


On 2011-12-12T13:18:03+00:00 Ivan Kharlamov wrote:

Created attachment 54375
Doc file to test the bug

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/903608/comments/1


On 2011-12-12T13:38:18+00:00 Ivan Kharlamov wrote:

Here is a bug screencast:
http://vpk.cloudkill.org/site_media/openoffice_bug.ogv

BTW, having a maximum of 3mb for attachments in bugzilla is very bad for
bug reporting.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/903608/comments/2


On 2011-12-14T02:26:26+00:00 Ivan Kharlamov wrote:

Little bit of history behind my bug report:
Few of my fellows have recently moved from Windows to Linux Mint(11.04). All of 
them say that LibreOffice Writer is a decent editor and they didn't have 
trouble adapting to it, but they are complaining about ONE SINGLE ANNOYANCE 
which is described in this bug report. They have hundreds of footnotes in their 
scientific papers and to change font style after every footnote seems insane. 

I have already installed MS Word via Wine for one of them. The issue is
serious, it is pushing users away from your otherwise good product.
Please, fix it ASAP.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/903608/comments/9


On 2011-12-14T03:02:36+00:00 Christopher M. Penalver wrote:

1) lsb_release -rd
Description: Ubuntu 11.10
Release: 11.10

2) apt-cache policy libreoffice-writer
libreoffice-writer:
  Installed: 1:3.4.4-0ubuntu1
  Candidate: 1:3.4.4-0ubuntu1
  Version table:
 *** 1:3.4.4-0ubuntu1 0
500 http://us.archive.ubuntu.com/ubuntu/ oneiric-updates/main i386 
Packages
100 /var/lib/dpkg/status
 1:3.4.3-3ubuntu2 0
500 http://us.archive.ubuntu.com/ubuntu/ oneiric/main i386 Packages

3) What is expected to happen in LibreOffice Writer importing a Word
created file via the Terminal:

cd ~/Desktop && wget -c
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/903608/+attachment/2630995/+files/footnoteformattingbug_1.doc
-O example.doc && lowriter -nologo example.doc

on page 1 if one clicks immediately after superscript footnote 1 and
begins to type, the characters are not superscript, as it would occur in
Word.

4) What happens instead is the characters are superscript as shown in
https://launchpadlibrarian.net/87353347/libreofficeformattingbug.ogv

WORKAROUND: Click immediately after the footnote and press Ctrl+Shift+P
then begin typing as desired. This is documented at:
http://help.libreoffice.org/Writer/Making_Text_Superscript_or_Subscript

Severity Normal > Minor
quoting from http://wiki.documentfoundation.org/BugReport_Details#Severity
"minor loss of function, or other problem where easy workaround is present"

Importance High > Low
This really should not be high on the developer to do list as the WORKAROUND is 
trivial to perform and well documented.

Platform All All > x86 (IA32) Linux (All)
Only documented test cases up or downstream are Linux, IA32.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/903608/comments/10


On 2011-12-14T04:36:00+00:00 Ivan Kharlamov wrote:

Christopher, thanks for the info about workaround.

However, the bug is all platform and is not architecture dependent. As I
have written, the bug exists in Ubuntu 10.10 (x86_64) (default
packages),

[Desktop-packages] [Bug 1263326] Re: [Upstream] IF function not evaluating correctly with cell borders in .ods

Launchpad has imported 12 comments from the remote bug at
https://bugs.documentfoundation.org/show_bug.cgi?id=072969.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2013-12-22T13:21:33+00:00 Ray DeCampo wrote:

Created attachment 91124
Example spreadsheet as in the bug description

Problem description:

When adding formatting, e.g. borders, to a cell, the string value of the
cell is affected.

Steps to reproduce:

See attached spreadsheet.  The first line has no formatting and behaves
as expected.  The second line has a border on cell B2 and the value of
that cell is affected.

Current behavior:

Cell C2 displays the value "Failed".
If the value of cell B2 is copied and pasted as text the value pasted is 
"foobar ".

Expected behavior:

Cell C2 displays the value "Passed" like the cell C1.  
If the value of cell B2 is copied and pasted as text the value pasted is 
"foobar".


Operating System: Ubuntu
Version: 4.1.3.2 release

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1263326/comments/7


On 2013-12-22T13:23:54+00:00 Ray DeCampo wrote:

I forgot to clarify in the original description, the issue began
manifesting when I upgraded from Ubuntu 13.04 to 13.10.  I believe the
version of LibreOffice for 13.04 is 4.0.2.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1263326/comments/9


On 2013-12-22T17:07:20+00:00 Christopher M. Penalver wrote:

Raymond DeCampo, thank you for reporting this. Would you please be able
to bibisect this problem following
https://wiki.documentfoundation.org/QA/HowToBibisect ? This would help
tremendously in resolving this bug.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1263326/comments/12


On 2014-04-28T22:57:25+00:00 Kohei-d wrote:

I just tested this using the latest versions of 4.1 and 4.2 (and
master), and this no longer happens.

To verify, you need to hit F9 after loading the submitted document
because the formula results are initially cached.  Once the cells get
recalculated, the reported problem no longer happens.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1263326/comments/14


On 2014-04-29T11:33:24+00:00 Christopher M. Penalver wrote:

Kohei Yoshida, thanks for taking a look at this. Unfortunately, the issue noted 
in the Description is reproducible in:
Version: 4.2.3.3
Build ID: 882f8a0a489bc99a9e60c7905a60226254cb6ff0
Microsoft Windows Vista Business x86 6.0.6002 Service Pack 2 Build 6002

As well, F9 does not update the calculation.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1263326/comments/16


On 2014-11-06T00:06:40+00:00 Jmadero-dev wrote:

There is some confusion about this issue as Kohei couldn't reproduce.
Moving to UNCONFIRMED to get fresh eyes on it. Thanks for understanding.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1263326/comments/18


On 2014-11-06T02:04:45+00:00 Christopher M. Penalver wrote:

The steps noted in the Description 
https://bugs.freedesktop.org/show_bug.cgi?id=72969#c0 are still confirmed 
verbatim in MASTER:
Version: 4.4.0.0.alpha1+
Build ID: b7d8a58ff2698ffc6e22943f64aa97c5ea253bd9
TinderBox: Win-x86@42, Branch:master, Time: 2014-11-05_00:40:38
Microsoft Windows Vista Business x86 6.0.6002 Service Pack 2 Build 6002

As I'm a member of LibreOffice QA, I've marked myself the QA contact if
you would have any further questions on the scope of this report.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1263326/comments/20


On 2014-11-06T02:38:31+00:00 Jmadero-dev wrote:

Apologies Christopher - didn't recognize your name :) Thanks for
confirming!

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1263326/comments/22


On 2015-12-20T16:13:39+00:00 Qa-admin-q wrote:

** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open,
confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked
on this bug report. During that time,

[Desktop-packages] [Bug 945448] Re: add toolbar commands pane shrinks, disappears

Launchpad has imported 4 comments from the remote bug at
https://bugs.documentfoundation.org/show_bug.cgi?id=46924.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2012-03-03T02:52:37+00:00 Satchit Bhogle wrote:

Created attachment 57964
Screenshot of problem

Problem description: 
See steps and attached image.

Steps to reproduce:
1. Go to Tools > Customise > Toolbars, and click Add.
2. Move to a toolbar that does not have enough elements to fill the pane, e.g. 
Data. Now back to something that has, e.g. Application.
3. Keep switching between toolbars.
4. Watch the commands pane gradually shrink and then disappear.

Current behavior:
The pane shrinks for toolbars with fewer elements and then stays shrunk when 
going to a toolbar with more elements.

Expected behavior:
The pane remains the same size regardless.


Platform (if different from the browser): 
Ubuntu 11.10 Oneiric stable 32-bit

Browser: Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:10.0.2) Gecko/20100101
Firefox/10.0.2

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/945448/comments/0


On 2012-03-03T06:32:21+00:00 Björn Michaelsen wrote:

_NOT_ reproducable at upstream libreoffice-3-5 branch-off without Ubuntus 
default theme.
reproducable with 1:3.5.0-1ubuntu4 with Ubuntus theme.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/945448/comments/1


On 2012-03-03T07:48:14+00:00 Björn Michaelsen wrote:

Also not reproducable on upstream master 
(1cf3e446744ae679bc89b39dcbbcf6b4e9821f3a) without default Ubuntu theming on 
oneiric.
Also not reproducable on 3.4.5 Ubuntu build on oneiric.

This seems to be a regression between oneiric->precise in either Ubuntus
theme or stack (gtk?)

resolving here as not our bug.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/945448/comments/2


On 2012-03-03T07:59:16+00:00 Björn Michaelsen wrote:

Of course, it could well be that it is a bug in the libreoffice gtk-vcl
plugin which only shows with recent versions of gtk. In that case,
please reopen.

@Fedora, SUSE user: Can you reproduce this with a very new gtk? The
issie is visible here with gtk+-2.24.10-0ubuntu4

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/945448/comments/3


** Changed in: df-libreoffice
   Status: Unknown => Won't Fix

** Changed in: df-libreoffice
   Importance: Unknown => Medium

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk+2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/945448

Title:
  add toolbar commands pane shrinks, disappears

Status in LibreOffice:
  Won't Fix
Status in One Hundred Papercuts:
  Invalid
Status in gtk+2.0 package in Ubuntu:
  New
Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  1) lsb_release -rd
  Description: Ubuntu 11.10
  Release: 11.10

  2) apt-cache policy libreoffice-writer
  libreoffice-writer:
Installed: 1:3.5.0-1ubuntu3~oneiric1
Candidate: 1:3.5.0-1ubuntu3~oneiric1
Version table:
   *** 1:3.5.0-1ubuntu3~oneiric1 0
  500 http://ppa.launchpad.net/libreoffice/ppa/ubuntu/ oneiric/main 
i386 Packages
  100 /var/lib/dpkg/status
   1:3.4.4-0ubuntu1 0
  500 http://in.archive.ubuntu.com/ubuntu/ oneiric-updates/main i386 
Packages
   1:3.4.3-3ubuntu2 0
  500 http://in.archive.ubuntu.com/ubuntu/ oneiric/main i386 Packages

  See attached image.
  Steps to reproduce:
  1. Go to Tools > Customise > Toolbars, and click Add.
  2. Move to a toolbar that does not have enough elements to fill the pane, 
e.g. Data. Now back to something that has, e.g. Application.
  3. Keep switching between toolbars.
  4. Watch the commands pane gradually shrink and then disappear.

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/945448/+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 981606] Re: [Upstream] Printer Language type PostScript Level 3 not persisting when chosen

Launchpad has imported 3 comments from the remote bug at
https://bugs.documentfoundation.org/show_bug.cgi?id=050358.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2012-05-25T10:22:01+00:00 Bernhard Reiter wrote:

Steps to reproduce:
In a blank Writer file, click File -> Print... -> General tab -> button 
Properties... -> Device tab -> Printer Language type, and select PostScript 
Level 3, then press the OK button.

Current behavior:
When navigating to the dialog containing the Printer Language setting again, it 
is set to PostScript Level 2. (If one chose PostScript Level 1, then when one 
returns it would still show Level 1.)

Expected behavior:
PostScript Level 3 should persist as Printer Language setting.
  
Browser/Platform: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.19 (KHTML, 
like Gecko) Ubuntu/11.10 Chromium/18.0.1025.168 Chrome/18.0.1025.168 
Safari/535.19

Downstream bug report at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/981606

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/981606/comments/7


On 2012-12-17T15:53:40+00:00 Ydutrieux wrote:

@bernard,

you can fix this behaviour with the program spdamin located in program
directory of Libo.

here on my Ubuntu 12.04
/opt/lodev4.0/program/spadmin

once fixed in this program, it will be set correctly on file - print.

Ubuntu 12.04 64Bits - Libo 4.0b1

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/981606/comments/10


On 2012-12-30T20:53:01+00:00 Christopher M. Penalver wrote:

Bernhard Reiter, one may use spadmin as noted in 
https://bugs.freedesktop.org/show_bug.cgi?id=50358#c1 to change the default 
settings. In Ubuntu repo LO, one may launch spadmin at a terminal:
sh /usr/lib/libreoffice/program/spadmin

As well, the 3.5.x branch is no longer supported as per
https://wiki.documentfoundation.org/ReleasePlan#3.5_release . If you can
reproduce the problem in a supported branch, please reopen this report.

Thank you for your understanding.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/981606/comments/11


** Changed in: df-libreoffice
   Status: Unknown => Won't Fix

** Changed in: df-libreoffice
   Importance: Unknown => Medium

** Bug watch added: freedesktop.org Bugzilla #50358
   https://bugs.freedesktop.org/show_bug.cgi?id=50358

-- 
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/981606

Title:
  [Upstream] Printer Language type PostScript Level 3 not persisting
  when chosen

Status in LibreOffice:
  Won't Fix
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  1) lsb_release -rd
  Description:  Ubuntu 12.04 LTS
  Release:  12.04

  
  2) apt-cache policy libreoffice-writer
  libreoffice-writer:
Installed: 1:3.5.2-2ubuntu1
Candidate: 1:3.5.2-2ubuntu1
Version table:
   *** 1:3.5.2-2ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ precise/main i386 Packages
  100 /var/lib/dpkg/status

  3) What is expected to happen in, for example a blank Writer file, is
  when one clicks File -> Print... -> General tab -> button
  Properties... -> Device tab -> Printer Language type PostScript Level
  3 -> button OK is when one goes back to Printer Language type it still
  shows the same thing.

  4) What happens instead is it shows PostScript Level 2. If one choose
  PostScript Level 1, then when one returned it would still show Level
  1.

  ---
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 11.10
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  NonfreeKernelModules: nvidia
  Package: libreoffice 1:3.4.5-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.0.0-19.33-generic 3.0.27
  Tags:  oneiric
  Uname: Linux 3.0.0-19-generic x86_64
  UpgradeStatus: Upgraded to oneiric on 2011-11-26 (163 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/981606/+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 1351493] Re: soffice.bin crashed with SIGSEGV in ResMgr::GetLong()

Launchpad has imported 4 comments from the remote bug at
https://bugs.documentfoundation.org/show_bug.cgi?id=82028.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2014-08-01T22:29:24+00:00 Cristian Aravena Romero wrote:

Open bug in launchpad.net :
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1351493

"Print document .odt and crash."

#0  ResMgr::GetLong (pLong=0x0) at 
/build/buildd/libreoffice-4.2.4/tools/source/rc/resmgr.cxx:1177
No locals.
#1  0x7fce2a276f60 in ResMgr::ReadLong (this=0x30d5e80) at 
/build/buildd/libreoffice-4.2.4/tools/source/rc/resmgr.cxx:1562
aGuard = {pT = 0x3174930}
n = 
#2  0x7fce2a6e5212 in ReadLongRes (this=0x36a16b8) at 
/build/buildd/libreoffice-4.2.4/include/tools/rc.hxx:66
No locals.
#3  Window::ImplLoadResHeader (this=this@entry=0x36a16b0, rResId=...) at 
/build/buildd/libreoffice-4.2.4/vcl/source/window/window.cxx:1278
aHeader = {nObjMask = 0, aHelpId = {pData = 0x7fce28074ba4 
}, nRSStyle = 55707120}
#4  0x7fce2a6f7dc2 in Window::ImplLoadRes (this=this@entry=0x36a16b0, 
rResId=...) at /build/buildd/libreoffice-4.2.4/vcl/source/window/window.cxx:1299
bPos = 
bSize = 
nRSStyle = 
aHeader = {nObjMask = 0, aHelpId = {pData = 0x7fce28074ba4 
}, nRSStyle = 55707120}
nObjMask = 
aPos = { = {nA = 6001, nB = 140523450620248}, }
aSize = { = {nA = 57284272, nB = 140735644281360}, }
#5  0x7fce2a677b37 in Dialog::init (this=this@entry=0x36a16b0, 
pParent=pParent@entry=0x0, rResId=...) at 
/build/buildd/libreoffice-4.2.4/vcl/source/window/dialog.cxx:553
nStyle = 0
#6  0x7fce2a6795b9 in ModelessDialog::ModelessDialog (this=0x36a16b0, 
pParent=0x0, rResId=...) at 
/build/buildd/libreoffice-4.2.4/vcl/source/window/dialog.cxx:1359
nStyle = 
#7  0x7fce2a6b132c in vcl::PrintProgressDialog::PrintProgressDialog 
(this=0x36a16b0, i_pParent=0x0, i_nMax=1) at 
/build/buildd/libreoffice-4.2.4/vcl/source/window/printdlg.cxx:1853
No locals.
#8  0x7fce2a623032 in vcl::PrinterController::createProgressDialog 
(this=this@entry=0x4a519d0) at 
/build/buildd/libreoffice-4.2.4/vcl/source/gdi/print3.cxx:1658
bShow = 
pMonitor = 
#9  0x7fce2a723975 in PspSalPrinter::StartJob (this=this@entry=0x51a9ad0, 
i_pFileName=i_pFileName@entry=0x0, i_rJobName=..., i_rAppName=..., 
i_pSetupData=i_pSetupData@entry=0x42e76b0, i_rController=...) at 
/build/buildd/libreoffice-4.2.4/vcl/generic/print/genprnpsp.cxx:1113
bSinglePrintJobs = 0 '\000'
nCopies = 1
aMtfContext = {m_nMaxImageResolution = 0, m_bOnlyLosslessCompression = 
true, m_nJPEGQuality = 90, m_bTransparenciesWereRemoved = false}
aPDFFiles = { >> = {_M_impl = {> = 
{<__gnu_cxx::new_allocator> = {}, }, _M_start = 0x0, _M_finish = 0x0, _M_end_of_storage = 0x0}}, }
pSingleValue = 
bCollate = false
aContext = {URL = {pData = 0x7fce28075040 }, 
BaseURL = {pData = 0x7fce28075040 }, RelFsys = false, 
DefaultLinkAction = vcl::PDFWriter::URIAction, ConvertOOoTargetToPDFTarget = 
false, ForcePDFAction = false, Version = vcl::PDFWriter::PDF_1_4, Tagged = 
false, SubmitFormat = vcl::PDFWriter::FDF, AllowDuplicateFieldNames = false, 
FieldsUseSystemFonts = true, PDFDocumentMode = vcl::PDFWriter::ModeDefault, 
PDFDocumentAction = vcl::PDFWriter::ActionDefault, Zoom = 100, 
HideViewerToolbar = false, HideViewerMenubar = false, HideViewerWindowControls 
= false, FitWindow = false, OpenInFullScreenMode = false, CenterWindow = false, 
DisplayPDFDocumentTitle = true, PageLayout = vcl::PDFWriter::DefaultLayout, 
FirstPageLeft = false, InitialPage = 1, OpenBookmarkLevels = -1, Encryption = 
{Security128bit = true, CanPrintTheDocument = false, CanModifyTheContent = 
false, CanCopyOrExtract = false, CanAddOrModify = false, CanFillInteractive = 
false, CanExtractForAccessibility = true, CanAssemble = false, CanPrintFull = 
false, OValue = { >> = {_M_impl = {> = 
{<__gnu_cxx::new_allocator> = {}, }, _M_start = 0x0, _M_finish = 0x0, _M_end_of_storage = 0x0}}, }, UValue = { >> = {_M_impl = {> = 
{<__gnu_cxx::new_allocator> = {}, }, _M_start = 0x0, _M_finish = 0x0, _M_end_of_storage = 0x0}}, }, EncryptionKey = { >> = {_M_impl = {> 
= {<__gnu_cxx::new_allocator> = {}, }, _M_start = 0x0, _M_finish = 0x0, _M_end_of_storage = 0x0}}, }, DocumentIdentifier = { >> = {_M_impl = {> 
= {<__gnu_cxx::new_allocator> = {}, }, _M_start = 0x0, _M_finish = 0x0, _M_end_of_storage = 0x0}}, }}, DocumentInfo = {Title = {pData = 0x36c9c90}, Author = {pData = 
0x7fce28075040 }, Subject = {pData = 0x7fce28075040 
}, Keywords = {pData = 0x7fce28075040 
}, Creator = {pData = 0x318c9a0}, Producer = {pData = 
0x318c9a0}}, SignPDF = false, SignLocation =

[Desktop-packages] [Bug 1242355] Re: [Upstream] LibreOffice Base connection to mdb via odbc crashes on saving odb file

Launchpad has imported 8 comments from the remote bug at
https://bugs.documentfoundation.org/show_bug.cgi?id=071966.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2013-11-24T14:42:19+00:00 magowiz wrote:

Problem description: 
I'm trying to connect via odbc to a mdb file using the base wizard, all seems 
to go fine, also connection test, but just after I choose where to save the odb 
file and click save, libreoffice crashes, produced file (odb) if opened makes 
libreoffice crash again.
These are version programs and configurations involved :
I was trying to connect to an existing mdb (MS Access) database file using 
unixodbc and libreoffice-base,
I've got unixodbc , undixodbc-bin and libmdbodbc1 packages installed
I set the odbc as following :

/etc/odbc.ini
[Pippo]
Description = mine database
Driver = /usr/lib/x86_64-linux-gnu/odbc/libmdbodbc.so.1
Database = /home/magowiz/pippo.mdb

/etc/odbcinst.ini
[MDBTools]
Description = MDBTools Driver
Driver = /usr/lib/x86_64-linux-gnu/odbc/libmdbodbc.so.1
Setup = /usr/lib/x86_64-linux-gnu/odbc/libmdbodbc.so.1
Usage = 1
FileUsage = 1
UsageCount = 2

I use the connection wizard into libreoffice base : I can successfully
test mine connection but while I'm saving the odb file the whole program
crashes and close itself

It follows distro and software versions :

$ lsb_release -rd
Description: Ubuntu 13.10
Release: 13.10

apt-cache policy libreoffice-base
libreoffice-base:
  Installed: 1:4.1.2~rc3-0ubuntu1
  Candidate: 1:4.1.2~rc3-0ubuntu1

apt-cache policy unixodbc
unixodbc:
  Installed: 2.2.14p2-5ubuntu4
  Candidate: 2.2.14p2-5ubuntu4

apt-cache policy libmdbodbc1
libmdbodbc1:
  Installed: 0.7-3
  Candidate: 0.7-3


Steps to reproduce:
1. configure like described above unixodbc to point to mdb file
2. open libreoffice base and choose to connect via ODBC to db name choosen 
while configurating unixodbc
3. choose where to save the odb file and then click save

Current behavior:
It crashes just after save button is clicked

Expected behavior:
it should open libreoffice base main interface to make me able to work with the 
database

The same file can be opened by libreoffice windows version on windows 7

  
Operating System: Ubuntu
Version: 4.1.3.2 release

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1242355/comments/17


On 2013-12-02T12:12:10+00:00 Lionel Elie Mamane wrote:

Could you please attach the .odb file that makes it crash?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1242355/comments/20


On 2013-12-02T13:13:24+00:00 magowiz wrote:

Created attachment 90103
odb file that points to mdb database

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1242355/comments/22


On 2013-12-02T13:14:16+00:00 magowiz wrote:

Created attachment 90104
mdb file that causes the issue.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1242355/comments/24


On 2013-12-02T13:15:07+00:00 magowiz wrote:

(In reply to comment #1)
> Could you please attach the .odb file that makes it crash?

I attached both mdb and odb file since the odb points to real database :
mdb file.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1242355/comments/26


On 2013-12-02T13:48:26+00:00 Lionel Elie Mamane wrote:

Reproduced on two different machines:
 - libreoffice 4.1.3.2 (Debian package): infinite loop (memory consumption)
 - libreoffice 4.1 my own development tree: segfault in ODBC code

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1242355/comments/28


On 2013-12-02T14:55:15+00:00 Lionel Elie Mamane wrote:

Crash goes away (on Debian) after upgrading unixodbc to 2.3.1-1. So
until hint to the contrary, seems to be a bug in UnixODBC -> NOTOURBUG.

It does not work though, the list of tables is empty. This seems to be a 
mdbtools bug, because isql also cannot get the list of tables. Try:
  echo help | isql Pippo | less -SIM
It "finds" 10 tables, but no info on them (no name, ...).

The SQLTables function seems to be not implemented in mdbtools, or buggy
on your particular example or ... (SQLGetData returns an error code, but
subsequent SQLGetDiagRec returns all-zero SQLSTATE, no error string,
...).

Reply at:

[Desktop-packages] [Bug 885085] Re: [upstream] Formula gets in a way while editing and prevents selection of the adjacent cell.

Launchpad has imported 6 comments from the remote bug at
https://bugs.documentfoundation.org/show_bug.cgi?id=042496.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

On 2011-11-01T23:37:56+00:00 Serhiy Zahoriya wrote:

Created attachment 53034
Screenshot of the long formula that gets in a way

Problem description: I often cannot select the adjacent cell to add it
to the formula when the last one is too long. It depends on the
formatting but I didn't found the formatting that will constrain the
formula within it's cell.

Steps to reproduce:
See the attached screenshot. I cannot add B2 cell to the formula using just a 
pointer.

Expected behavior:
The formula should leave cell boundaries only when the formula bar is not 
visible.

Platform (if different from the browser): 
All platforms
Browser: Mozilla/5.0 (X11; Linux i686; rv:7.0.1) Gecko/20100101 Firefox/7.0.1

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/885085/comments/1

On 2011-11-01T23:40:26+00:00 Serhiy Zahoriya wrote:

(In reply to comment #0)
> didn't found 
*find

> add B2 cell 
*B1

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/885085/comments/3

On 2012-04-19T02:06:27+00:00 Sasha-libreoffice wrote:

Thanks for bugreport
Reproducible in 3.3.4 and 3.5.2 on Fedora 64 bit and Windows 32 bit

Currently it is not a bug but functionality request. Something like this:
If A1 contains long formula, A2 contains some content, we placed cursor into 
formula bar (not into cell), then do not expand formula from A1 to A2.

@ Сергій Загорія
Workaround: According to screenshot, suppose we need add cell B1. First, add 
C1. Then press arrow to left on keyboard, C1 will changed to B1. But do not 
place cursor into formula or it method will not work. This works on Windows and 
Linux.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/885085/comments/7

On 2014-07-22T08:37:00+00:00 chris wrote:

*** Bug 48383 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/885085/comments/9

On 2016-03-14T02:17:26+00:00 TheReaperD wrote:

This becomes more of an issue the longer your formulas are.  With some
of the formulas I am using, it can consume a large portion of the page,
hiding many cells I would like to be able to click on to add to the
formula.  This forces me to save the formula incomplete, lookup the cell
addresses that I need to add and re-edit the formula.  Since some of
them requires 10 cells or more, this is a major pain.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/885085/comments/11

On 2018-03-17T12:47:09+00:00 Severoraz wrote:

This bug is still present in LibreOffice 6.0.2.1.0.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/885085/comments/12

** Changed in: df-libreoffice
   Status: Unknown => Confirmed

** Changed in: df-libreoffice
   Importance: Unknown => Wishlist

-- 
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/885085

Title:
  [upstream] Formula gets in a way while editing and prevents selection
  of the adjacent cell.

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Problem description: I often cannot select the adjacent cell to add it to the
  formula when the last one is too long. It depends on the formatting but I
  didn't find the formatting that will constrain the formula within it's cell.

  Steps to reproduce:
  See the attached screenshot. I cannot add B1 cell to the formula using just a
  pointer.

  Expected behavior:
  The formula should leave cell boundaries only when the formula bar is not
  visible.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: libreoffice-calc 1:3.4.3-3ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic-pae 3.0.4
  Uname: Linux 3.0.0-12-generic-pae i686
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu3
  Architecture: i386
  Date: Wed Nov  2 08:41:20 2011
  ProcEnviron:
   LANGUAGE=uk:en
   PATH=(custom, no user)
   LANG=uk_UA.UTF-8
   LC_MESSAGES=uk_UA.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1598938] Re: soffice.bin crashed with SIGSEGV in IsVertical()

Launchpad has imported 8 comments from the remote bug at
https://bugs.documentfoundation.org/show_bug.cgi?id=0100421.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2016-06-16T09:13:04+00:00 Manuel-defranceschi wrote:

Created attachment 125690
Try to delete the outer table and LO crash.

Description:

If I insert five or more tables 10x15 one inside the other and then
cancel the outer table(or the column or the row which contain the cell
that contain the other tables) LO crashes. It seems that the dimension
influence the problem: for example, at 8x13 with five tables LO doesn't
crash, but with six tables it does, and at 100x10 it doesn't crash at
all.

Steps:
1-Open Writer
2-Insert a table 10x15
3-Repeat step 2 for at least 5 time without change the cursor's position
4-Delete the outer table
At this point LO crash.

Affected version:

Version: 5.0.6.3
Build ID: 490fc03b25318460cfc54456516ea2519c11d1aa
Locale: it-IT (it_IT.UTF-8)
OS: openSUSE Leap 42.1 (x86_64)

Version: 5.1.3.2
Build ID: 644e4637d1d8544fd9f56425bd6cec110e49301b
CPU Threads: 2; UI Render: default; 
Locale: it-IT (it_IT.UTF-8)
OS: openSUSE Leap 42.1 (x86_64)

Version: 5.3.0.0.alpha0+
Build ID: a8bd44573b75d1399257d6f5d052611439607189
CPU Threads: 2; 
UI Render: default; 
TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time: 2016-06-13_23:46:49
Locale: it-IT (it_IT.UTF-8)
OS: openSUSE Leap 42.1 (x86_64)

Not affected version:

Version 3.6.7.2 (Build ID: e183d5b)
OS: openSUSE Leap 42.1 (x86_64)

Versione: 4.4.7.2
Build ID: f3153a8b245191196a4b6b9abd1d0da16eead600
Versione locale: it_IT.UTF-8
OS: openSUSE Leap 42.1 (x86_64)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1598938/comments/0


On 2016-06-17T06:34:49+00:00 Aron Budea wrote:

Thank you for the detailed bug report.
Crash reproduced with LO 5.0.0.5, not reproduced with 4.4.0.3, both in Windows 
7 => regression.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1598938/comments/1


On 2016-06-17T09:08:21+00:00 Caolanm wrote:

bibisecting suggests

commit 135e4d5c730b8b252eab3e375580a3a73d8204e6
Author: Michael Stahl 
Date:   Thu Apr 23 22:52:39 2015 +0200

related: tdf#90820 refactor SwFrm destruction

is the trigger, though I rather feel that's not at fault and we just got
away with things earlier

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1598938/comments/2


On 2016-06-17T09:36:22+00:00 Libreoffice-commits wrote:

Caolán McNamara committed a patch related to this issue.
It has been pushed to "master":

http://cgit.freedesktop.org/libreoffice/core/commit/?id=e41a694c8b4fd1503b31f3a9da326e9f7ddd1b79

Related: tdf#100421 crash in a11y on load of source odt

It will be available in 5.3.0.

The patch should be included in the daily builds available at
http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
http://wiki.documentfoundation.org/Testing_Daily_Builds

Affected users are encouraged to test the fix and report feedback.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1598938/comments/3


On 2016-06-17T09:36:27+00:00 Libreoffice-commits wrote:

Caolán McNamara committed a patch related to this issue.
It has been pushed to "master":

http://cgit.freedesktop.org/libreoffice/core/commit/?id=4561119a8bab986df25a5ce2a544aa96394cbd5d

Resolves: tdf#100421, don't crash on deleting particular table

It will be available in 5.3.0.

The patch should be included in the daily builds available at
http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
http://wiki.documentfoundation.org/Testing_Daily_Builds

Affected users are encouraged to test the fix and report feedback.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1598938/comments/4


On 2016-06-17T15:45:51+00:00 Libreoffice-commits wrote:

Caolán McNamara committed a patch related to this issue.
It has been pushed to "libreoffice-5-2":

http://cgit.freedesktop.org/libreoffice/core/commit/?id=f054ba24056dba34576bc43a86abb0b828917585=libreoffice-5-2

Related: tdf#100421 crash in a11y on load of source odt

It will be available in 5.2.0.1.

The patch should be included in the daily builds available at
http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about

[Desktop-packages] [Bug 863788] Re: [Upstream] Cannot access 'data series' on libreoffice calc chart

Launchpad has imported 19 comments from the remote bug at
https://bugs.documentfoundation.org/show_bug.cgi?id=41394.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2011-10-01T18:03:28+00:00 Colin Church wrote:

Problem description: 'data range' not enabled under format menu

Steps to reproduce:
1. double click chart so as to modify
2. click on format menu
3. 

Current behavior:data range greyed out and not accessible

Expected behavior:
  Be able to modify data used to create chart

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/863788/comments/7


On 2011-10-01T18:05:11+00:00 Colin Church wrote:

It should also be noted that F9 does no longer update charts

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/863788/comments/8


On 2011-11-01T02:48:04+00:00 Bruno-ioda-net wrote:

It's absolutely worse that what is describe on 3.4.3 version

If the document used was created by a previous version, trying to edit
an existing charts remove all references to the data series sources.

The previous data, sometimes exist but as a table, like if they were
copied from the initial data series.

On columns chart type with 3.4.3 the data source is killed, and then
there's no way for the users to retrieve it. Even ctrl+Z doesn't restore
the chart.

-> Data corruption ! You need to use a previous version of the document
if it saved, there's no more data.

See the different print-screen attached.

This as been tested and confirmed under Linux 64bits (openSUSE 11.4 /
12.1 ) + windows 7 64bits, and windows xp 32 bits (legacy LOO.exe
installer)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/863788/comments/12


On 2011-11-01T02:51:26+00:00 Bruno-ioda-net wrote:

Created attachment 52984
Initial source document with charts, which was created by a 3.x version

In this document there several charts and data sources that are used to create 
the chart.
Editing or adding charts with 3.x version of Loo works as expected
Editing or adding a chart with 3.4.3 version crash the column type graph

see other screenshots

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/863788/comments/13


On 2011-11-01T02:57:22+00:00 Bruno-ioda-net wrote:

Created attachment 52985
Editing a curve series (double click + right click ) give good results

If you try to edit the first graph in proposed document
you get the right click menu about editing the data ranges

Have a look how is presented the second graph now.
and check what's happen next screenshot

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/863788/comments/14


On 2011-11-01T03:03:46+00:00 Bruno-ioda-net wrote:

Created attachment 52986
Trying to edit a column chart lead to data source destruction

Now on a column chart, we try what was done previously.
once you double clic on it for editing the chart is exploded.

and in place we have a chart data table ?
The chart is totally destroyed

If the user, or the auto-save function save the document at that time,
the document is destroyed. And need to be recovered from a backup!

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/863788/comments/15


On 2011-11-01T03:04:42+00:00 Bruno-ioda-net wrote:

Created attachment 52987
Resulting source of data : corrupted

Resulting data in the edit mode !
Which is totally wrong

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/863788/comments/16


On 2011-11-01T03:08:17+00:00 Bruno-ioda-net wrote:

I change the level of priority, due to the fact that document is
destroyed and can't be saved.

Now if you try to add a new column chart graph with the wizard it ask
you to select the data ranges. which appear the first time, but if you
click on the tab data series you see all is empty (expected) then you
click back on the range selection and this one is empty too 

If dev can't reproduce it, I can run it on a gdb session and give a traceback
(I've all debuginfo installed)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/863788/comments/17


On 2011-11-01T03:09:08+00:00 Bruno-ioda-net wrote:

modified plateform

[Desktop-packages] [Bug 1126858] Re: [upstream] Search and replace, with tracked changes on, changing only format of text, causes Writer to hang

Launchpad has imported 22 comments from the remote bug at
https://bugs.documentfoundation.org/show_bug.cgi?id=36582.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2011-04-25T06:41:49+00:00 Magnes wrote:

If you turn on recording and showing changes in document find and
replace will replace even things already deleted. Example:

1. Create new document.
2. Write "This is a document".
3. Turn on showing and recording changes.
4. Delete the word "document" so you have "This is a".
5. Replace document with "file".
6. The document will contain: "This is a file." instead of "This is a".

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1126858/comments/0


On 2011-04-25T06:43:03+00:00 Magnes wrote:

PS. In point 5 I mean "Use search and replace to change word 'document'
to 'file'". Sorry for being vague.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1126858/comments/1


On 2011-04-25T11:19:23+00:00 Gleppert-o wrote:

I tested the bug as described. I can confirm the bug on my system.

Furthermore, the bug is even more serious than described:

* First problem as described by Tomasz: The replace deleted word is
active/undeleted after search This actually destroys the
written text.

* Second problem: After hitting "Replace all" a couple of times, it will
keep replacing the deleted text with the new text. The dialog never
displays "Word not found" and hence does not stop.

Due to the reason that data can be actually made unusable/unreadible, I
change the importance to high/major. I hope this is okay.

System: Ubuntu 10.4./Gnome,  LibreOffice 3.3.2 PPA, Intel 32Bit

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1126858/comments/2


On 2011-12-23T12:07:33+00:00 Björn Michaelsen wrote:

[This is an automated message.]
This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it
started right out as NEW without ever being explicitly confirmed. The bug is
changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back
to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 
prereleases.
Details on how to test the 3.5.0 beta1 can be found at:
http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1

more detail on this bulk operation: http://nabble.documentfoundation.org
/RFC-Operation-Spamzilla-tp3607474p3607474.html

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1126858/comments/3


On 2012-02-11T19:30:57+00:00 Chuck598 wrote:

No longer does find & replace work for me.

I have deleted LibeOffice & reinstalled & no change.

Maybe there is a report that I didn't see about this or maybe only me?

I am only a user so not to good & this as this is the first time I have
tried to report a problem.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1126858/comments/4


On 2012-03-19T09:45:16+00:00 Gleppert-o wrote:

This severe regression is still there in LibreOffice 3.5.
I just 'destroyed' a document myself where track changes was activated (and 
extensively used) and I wanted to search something.

Please increase the severity of this bug!

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1126858/comments/5


On 2012-10-15T19:55:15+00:00 Stfhell wrote:

Still a problem in LO 3.6.2.2. In summary: When "Show tracked changes"
is active, "Find" will find text that has been deleted with "track
changes" activated. "Find & replace" will replace already deleted text.
When you do "Find & replace" with activated "track changes", it will
replace the same (already deleted) text again and again. "Replace all"
works insofar as it replaces each occurance only once.

Actually it can be useful if "Find" also searches tracked deletions -
after all you use "track changes" to be able to keep deleted text in the
document. But I think it's usually not what you want. So you would have
to disable "show tracked changes" just to do a "Find". I cannot imagine
a situation where you would like already deleted text to be replaced by
newly inserted text.

It's definitely a bug that LO does not at least move the cursor behind
the replaced text when you choose "Replace" in the "Find & replace"
dialogue with "track changes" activated. That leads to the same text
being replaced again and again.

Reply at:

[Desktop-packages] [Bug 347453] Re: [upstream] Calc Input bar error looses last character of pasted content

Launchpad has imported 18 comments from the remote bug at
https://bugs.documentfoundation.org/show_bug.cgi?id=37864.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2011-06-02T13:40:47+00:00 Christopher M. Penalver wrote:

Downstream bug may be found at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/347453

1) lsb_release -rd
Description: Ubuntu 11.04
Release: 11.04

2) apt-cache policy libreoffice-writer
libreoffice-writer:
  Installed: 1:3.3.2-1ubuntu5
  Candidate: 1:3.3.2-1ubuntu5
  Version table:
 *** 1:3.3.2-1ubuntu5 0
500 http://us.archive.ubuntu.com/ubuntu/ natty-updates/main i386 
Packages
100 /var/lib/dpkg/status
 1:3.3.2-1ubuntu4 0
500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages

3) What is expected to happen is if one copies a cell containing "test",
and paste it into the 'input line' bar, just test is pasted.

4) What happens instead is that a space is appended to the end of test.
If one backspaces or deletes the space, the last character is deleted.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/347453/comments/5


On 2011-06-06T04:31:01+00:00 timar wrote:

It is the same on Windows. Reproduced also in 3.4.0.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/347453/comments/9


On 2011-06-06T04:39:04+00:00 timar wrote:

Kohei, can you please check this?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/347453/comments/11


On 2011-06-18T14:39:24+00:00 Wope-1 wrote:

in LibO 3.3.3 and 3.4.1 it seems to be ok. Please test it.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/347453/comments/13


On 2011-07-21T23:48:53+00:00 Christopher M. Penalver wrote:

Reproduced in LO Calc 3.3.3.

lsb_release -rd
Description:Ubuntu 11.04
Release:11.04

apt-cache policy libreoffice-calc
libreoffice-calc:
  Installed: 1:3.3.3-1ubuntu1
  Candidate: 1:3.3.3-1ubuntu1
  Version table:
 *** 1:3.3.3-1ubuntu1 0
500 http://us.archive.ubuntu.com/ubuntu/ natty-proposed/main i386 
Packages
100 /var/lib/dpkg/status
 1:3.3.2-1ubuntu5 0
500 http://us.archive.ubuntu.com/ubuntu/ natty-updates/main i386 
Packages
 1:3.3.2-1ubuntu4 0
500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/347453/comments/15


On 2013-01-31T22:45:14+00:00 Robert Roth wrote:

Do you

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/347453/comments/18


On 2015-02-09T16:35:19+00:00 Stgohi-lobugs wrote:

Reproducible with LO 4.4.0.3, Win 8.1.

Steps Done:
1. Open CALC
2. Write in cell A1 "test"
3. Select cell A1 and press CTRL + C
4. Select cell B1 and put the cursor in the Input Line below the toolbars at 
the top
5. Press CTRL + V

Interim Result: A space is appended at the end of "test"

6. Press the backspace key to delete this wrongly added space manually
>Take a look at the Input Line and the cell B1 itself<
   Press Enter

Result: In the Input Line only the wrongly added space is deleted, but
in "real" the last character of "test" is deleted -> Result: "tes"

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/347453/comments/19


On 2016-02-21T08:37:41+00:00 Qa-admin-q wrote:

** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open,
confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked
on this bug report. During that time, it's possible that the bug has
been fixed, or the details of the problem have changed. We'd really
appreciate your help in getting confirmation that the bug is still
present.

If you have time, please do the following:

   Test to see if the bug is still present on a currently supported version of 
LibreOffice 
   (5.0.5 or 5.1.0)  https://www.libreoffice.org/download/

   If the bug is present, please leave a comment that includes the version of 
LibreOffice and 
   your operating system, and any changes you see in the bug

[Desktop-packages] [Bug 1430531] Re: FILEOPEN: Opening file from Samba share produce Document in Use dialog (~/.gvfs or mount.cifs)

Launchpad has imported 10 comments from the remote bug at
https://bugs.documentfoundation.org/show_bug.cgi?id=089632.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2015-02-24T20:48:39+00:00 Norbert wrote:

The bug is somehow related to bug#72337.

I'm on Ubuntu 12.04.5 with all updates and LibreOffice Version: 4.4.1.2
Build ID: 40m0(Build:2) (libreoffice 1:4.4.1~rc2-0ubuntu1~precise1) from PPA.

Steps to reproduce:
1. I have shared my Public folder using nautilus-share (0.7.3-1ubuntu2), placed 
test.odt file in it.
2. I navigate Nautilus to smb://localhost, clicked Open in Terminal here (or 
launch terminal and "cd ~/.gvfs/public\ on\ localhost").
3. Run "libreoffice test.odt" in terminal.
4. Got "Document in Use" window with text:

   Document file 'test.odt' is locked for editing by:

   Unknown User

   Open document read-only or open a copy of the document for editing.


   Open Read-Only Open Copy Cancel

5a. If I click 'Open Read-Only' the document is opened in read-only.
5b. If I click 'Open Copy' the "Untitled 1" document is opened.
5c. Cancel closes this window.


Expected results:
   The "test.odt" files is opened in read-write mode, user can edit it.

Actual results:
   User can't edit original document (see pp. 4-5 above).


This functionality is essential. Please fix this bug.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1430531/comments/1


On 2015-02-24T21:24:10+00:00 Norbert wrote:

Bug exists in LibreOffice "Version: 4.3.6.2 Build ID: 430m0(Build:2)"
(1:4.3.6~rc2-0ubuntu1~precise1).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1430531/comments/3


On 2015-02-24T22:54:18+00:00 Björn Michaelsen wrote:

Can this problem be reproduced on a newer Ubuntu version than 12.04
(e.g. on 14.04 or 15.10)? If not, this likely is yet another case of:
https://launchpad.net/bugs/1103953

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1430531/comments/5


On 2015-02-28T21:14:24+00:00 Norbert wrote:

I did some research with different versions of LibO and on different distros.
The test method was as follows: I set Samba public share on my other laptop, 
created document in this share, then connect to it.
Here is a Google Docs Table ( http://goo.gl/jY9Ubj ):
* I got message about repairing only in 12.04.5 with LibO 4.x
* In other distros I got 'Document in Use' very often.

After this research I can't determine why 'Document in Use' message is
produced.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1430531/comments/7


On 2015-03-07T07:26:38+00:00 Norbert wrote:

I did deeper research ( see comment 23 at
https://bugs.documentfoundation.org/show_bug.cgi?id=72337#c23 ).

So for me it seems that there is a difference in communication between
Samba SMB/CIFS (or Windows SMB/CIFS) server and LibreOffice.
I do not know how to debug this. Both SMB/CIFS servers provide full read and
write access on file level (via GVFS and mount.cifs).
Samba SMB/CIFS share was created with nautilus-share addon, without any 
error
messages and non-standard configuration.

My results are summarized in Google Docs table (
http://goo.gl/jY9Ubj ).

I need confirmation from other users.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1430531/comments/9


On 2015-03-15T16:53:42+00:00 Norbert wrote:

Dear Bjorn!
This bug exists in modern versions of Ubuntu too.

I set SMB/CIFS *server* in Ubuntu 14.04.2 and connected to it from other 
*client* distros - I got "Document in Use" very often (see my table -  
http://goo.gl/jY9Ubj , sheet "Ubuntu 14.04 Samba Server").

Please fix this bug.
I'm ready to help, provide more information, to test dev-builds and so on.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1430531/comments/14


On 2016-05-03T07:13:31+00:00 Raal wrote:

Hello Norbert, bug 72337 is fixed. Do you have still the problem in
actual version of LO?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1430531/comments/16


On 2016-05-06T14:02:39+00:00 Beluga wrote:

Set to NEEDINFO.
Change back to UNCONFIRMED, if the problem persists. Change to RESOLVED 
WORKSFORME, if the problem went away.
(Or should

[Desktop-packages] [Bug 1427346] Re: [Upstream] Ambiance wrong color for text toolbar buttons in LibreOffice

Launchpad has imported 44 comments from the remote bug at
https://bugs.documentfoundation.org/show_bug.cgi?id=089760.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2015-03-01T17:38:38+00:00 Thomas Bordfeldt wrote:

Created attachment 113799
Screenshot with "Close Preview"-button

LO 4.4.1.2 on Xubuntu 14.04 64bit

In Print-Preview-Mode in Writer or Calc the "Close Preview"-Button is
active, but greyed out.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1427346/comments/0


On 2015-03-01T17:59:51+00:00 Jmadero-dev wrote:

Cannot confirm:

Ubuntu 14.10 x64
LibreOffice 4.4.1.2 rc

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1427346/comments/1


On 2015-03-01T20:00:50+00:00 Cno wrote:

same issue as the other bugs?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1427346/comments/2


On 2015-03-01T20:25:57+00:00 Raal wrote:

I can confirm with Version: 4.4.2.0.0+
Build ID: 3e3f0f5c3051ea982f8f753e0f3e51441e8f9496
TinderBox: Linux-rpm_deb-x86_64@46-TDF, Branch:libreoffice-4-4, Time: 
2015-02-22_10:24:01
Probably same root cause as in bug 85990

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1427346/comments/3


On 2015-03-28T20:07:35+00:00 Luke wrote:

I CAN confirm:

Ubuntu 14.10 x86
LibreOffice: 4.5.0.0.alpha0+
Build ID: 4ee55eed6a34f6f061a0cd369a30afb464f9fa27

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1427346/comments/7


On 2015-03-29T19:44:54+00:00 Raal wrote:

This appears to have begun at the below commit.

Adding Cc: to meta_...@yahoo.com ; Could you possibly take a look at
this? Thanks

ed815944b5123c83f574bc814c266d1a346af05c is the first bad commit
commit ed815944b5123c83f574bc814c266d1a346af05c
Author: Matthew Francis 
Date:   Sun Mar 15 03:14:10 2015 +0800

source-hash-0ed0974298992ae871a8fbe79f856cf2588aeec6

(Bibisect: Skipped preceding irrelevant commit(s) 
e5bbc721d6bd5536bdd34f33fc79933a379f2919)

commit 0ed0974298992ae871a8fbe79f856cf2588aeec6
Author: Michael Jaumann 
AuthorDate: Tue Sep 23 12:34:54 2014 +
Commit: Samuel Mehrbrodt 
CommitDate: Mon Sep 29 17:44:07 2014 +

fdo#59299 Personas for bottom toolbars

Change-Id: If823964bf3bb67563504db61b6c5d557cab89243
Reviewed-on: https://gerrit.libreoffice.org/11609
Reviewed-by: Samuel Mehrbrodt 
Tested-by: Samuel Mehrbrodt 

:04 04 cbef77b3f28fa181e5bf377bc21d72684b7d8266
4fe9067c423579069e3ca6dafc6a9bf08b3690f5 M  opt

git bisect log
# bad: [cf6ea17155fabb2a120ba07c150735591ac861d7] 
source-hash-3f94c9e9ddfd807b449f3bb9b232cf2041fa12d2
# good: [fc71ac001f16209654d15ef8c1c4018aa55769f5] 
source-hash-c15927f20d4727c3b8de68497b6949e72f9e6e9e
git bisect start 'latest' 'oldest'
# good: [8cf60cc706948588e2f33a6d98b7c55d454e362a] 
source-hash-f340f0454627939f1830826fb5cc53a90e6c62a4
git bisect good 8cf60cc706948588e2f33a6d98b7c55d454e362a
# bad: [7beddf3808dadd525d7e55c00a5a90a2b44c23d3] 
source-hash-2f10386ce577f52e139aa23d41bc787d8e0b4d59
git bisect bad 7beddf3808dadd525d7e55c00a5a90a2b44c23d3
# good: [7d319609d8266af06aa3256fd3773d052b9150dc] 
source-hash-1fec67aab152e0c0ad6dd85082c50f1beff7d520
git bisect good 7d319609d8266af06aa3256fd3773d052b9150dc
# bad: [136c4fdf380a2d05111e313540e4be01a74c4eb6] 
source-hash-7bacb89bb955f4985e435c33dde629099dab744b
git bisect bad 136c4fdf380a2d05111e313540e4be01a74c4eb6
# good: [f3c053a278b473b5029baf72c02bdc3d78289b51] 
source-hash-a37a8733609a59eccabf89b2ff67d5ee6bf194bb
git bisect good f3c053a278b473b5029baf72c02bdc3d78289b51
# good: [30a34b701cf5b78868db5cc5ec7df738a54a5efb] 
source-hash-63ec219eca557c562433c4e9965a6f154e5966b5
git bisect good 30a34b701cf5b78868db5cc5ec7df738a54a5efb
# bad: [9ebfb6380d0d06e5465527738e402cd58bb7c467] 
source-hash-a67e6ae04086f2f60bb9747fbfc09a5a3d303d84
git bisect bad 9ebfb6380d0d06e5465527738e402cd58bb7c467
# good: [b629fd5ebfe6113a8db53ac648ab8b7a936f72da] 
source-hash-c353caee1c86476d98cd483f963f63c4195975f4
git bisect good b629fd5ebfe6113a8db53ac648ab8b7a936f72da
# good: [ca930c01a86e13c009262cc284749154e49721a4] 
source-hash-0b23ac2c9d36c89137feeb82d0aed7a8628a53b7
git bisect good ca930c01a86e13c009262cc284749154e49721a4
# good: [4eb8ac0bf78ea68f9fc0e5bdf0a7e7544aa2a222] 
source-hash-1424a8174eb37d26a2ec41a981a74f34661c0044
git bisect good

[Desktop-packages] [Bug 1619814] Re: [upstream] Can't paste contents from clipboard copied from LibreOffice once it is closed

Launchpad has imported 4 comments from the remote bug at
https://bugs.documentfoundation.org/show_bug.cgi?id=0101868.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2016-09-02T23:04:49+00:00 X-noreply+59396 wrote:

I have found recently that if I copy some text for example from any of
the LibreOffice programs, that if I then paste it into another program
outside of that suite then it pastes it fine. But if I then close
LibreOffice then trying to paste the text does nothing, so closing
LibreOffice also gets rid of the contents in the clipboard from it which
is not ideal.

I am running Ubuntu GNOME 16.04.1 with GNOME 3.20 and LibreOffice
version "5.1.4.2 10m0(Build:2)" (the latest version available from the
official Ubuntu repositories).

I initially reported this issue here:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1619814
However I thought I should also do so upstream.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1619814/comments/1


On 2016-09-03T08:51:09+00:00 thackert wrote:

Hello cooks.go.hungry, *,
I can confirm your bug with

OS: Debian Testing AMD64
DE/DM: XFCE 4.12

but back to
OOo: 3.2.0
OOO320m12 (Build:9483)
(parallel installed, following the instructions from 
https://wiki.documentfoundation.org/Installing_in_parallel/Linux)

As this is the earliest version I have installed and with which I can reproduce 
your bug, I am setting version to "Inherited From OOo" and status to "NEW". 
Interestingly, copying text from Iceweasel / Firefox-esr does not clear the 
clipboard ... ;)
HTH
Thomas.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1619814/comments/2


On 2017-02-06T18:48:21+00:00 Codedoes wrote:

I had a similar bug, however, mine was when I tried copying from one
instance, closing it and pasting to another instance. Causing
libreoffice to crash.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1619814/comments/3


On 2018-02-07T03:33:22+00:00 Qa-admin-q wrote:

** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open,
confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked
on this bug report. During that time, it's possible that the bug has
been fixed, or the details of the problem have changed. We'd really
appreciate your help in getting confirmation that the bug is still
present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of
LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information 
from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to 
RESOLVED-WORKSFORME and leave a comment that includes the information from Help 
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular 
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a 
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your 
bug pertains to a feature added after 3.3) from 
http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: 
https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1619814/comments/4


** Changed in: df-libreoffice
   Status: Unknown => Confirmed

** Changed in: df-libreoffice
   Importance: Unknown => Medium

-- 
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/1619814

Title:
  [upstream] Can't paste contents from clipboard copied from LibreOffice
  once it is closed

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:

[Desktop-packages] [Bug 1641264] Re: libreoffice crashes on startup when using OpenGL rendering and proprietary nvidia driver.

Launchpad has imported 32 comments from the remote bug at
https://bugs.documentfoundation.org/show_bug.cgi?id=097160.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2016-01-15T22:10:51+00:00 Silviu C. wrote:

Trying to run any Writer, Calc, etc with OpenGL enabled causes them to
crash on exit. OpenGL rendering is deselected on subsequent runs, unless
it's forced. Then a profile reset is needed.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1641264/comments/1


On 2016-01-15T22:13:28+00:00 Silviu C. wrote:

Might be related to this bug:
 
https://bugs.documentfoundation.org/show_bug.cgi?id=96546
 
which appears to be fixed on Windows

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1641264/comments/3


On 2016-01-16T10:51:41+00:00 Michael-meeks-1 wrote:

Oooh - nice =) what is the hash of your build from Help->about ? - or is
it RC2 ? Some idea of your GPU would be nice.

Even more ideal would be a windbg stack-trace if we have one - ideally
with symbols (?) =) with that we can nail this down much more quickly
instructions are here:

https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg

Many thanks !

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1641264/comments/5


On 2016-01-16T10:52:44+00:00 Michael-meeks-1 wrote:

Oh - also, bug title says "crash on launch", but bug text says "crash on
exit" - is it launch, or exit ? =) Thanks !

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1641264/comments/7


On 2016-01-16T11:11:49+00:00 Silviu C. wrote:

Oh gosh. I'm sorry. I really should stop writing bug reports at midnight :/
 
Anyway, the crash happens on launch.

LO build info:
Version: 5.1.0.2
Build ID: ecd3574d51754b043f865cf5bafee286d24db7cc
CPU Threads: 4; OS Version: Linux 4.3; UI Render: default; 
Locale: en-US (en_US.UTF-8)
 
I tried with the Jan 15 daily and the same crash on launch happened.
 
My video card is a GTX 660 and I'm using the 352.63 driver (long lived branch)

Could I provide a useful stack-trace using GDB? I'll attach what I got
in the meantime by running soffice --backtrace.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1641264/comments/9


On 2016-01-16T11:13:21+00:00 Silviu C. wrote:

Created attachment 121985
result of running soffice --backtrace

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1641264/comments/11


On 2016-01-16T16:43:03+00:00 thackert wrote:

Hello Silviu, *,
I can confirm it with LO

Version: 5.0.4.2
Build-ID: 00m0(Build:2)
Gebietsschema: de-DE (de_DE.UTF-8)

on Debian Testing AMD64, but not with

Version: 5.1.0.2
Build-ID: ecd3574d51754b043f865cf5bafee286d24db7cc
CPU Threads: 4; OS Version: Linux 4.3; UI Render: GL; 
Gebietsschema: de-DE (de_DE.UTF-8)

(parallel installed, following the instructions from
https://wiki.documentfoundation.org/Installing_in_parallel/Linux) with
de-DE lang- as well as helppack.

My video chip is an Intel HD Graphics 4400 and NVidia GeForce 840M (which I am 
not able to get it work ... :( ). I am using xserver-xorg-video-intel 
2.99.917-2, if this is important ... ;) I will attach a backtrace as well as a 
trace afterwards. If someone here needs any further info, feel free to ask :)
HTH
Thomas.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1641264/comments/13


On 2016-01-16T16:44:59+00:00 thackert wrote:

Created attachment 122001
"soffice --backtrace" output

My "soffice --backtrace" output, after enabling OpenGL in LO's Options
dialog, restarting LO, and starting Writer ...

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1641264/comments/15


On 2016-01-16T16:46:56+00:00 thackert wrote:

Created attachment 122003
zipped trace

Zipped "soffice --strace"log, as the unzipped one is 13MiB in size ...
:(

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1641264/comments/17


On 2016-02-23T18:13:04+00:00 Silviu C. wrote:

Created attachment 122927
backtrace with symbols LO 5.1.0 rc3

As LO 5.1.0 packages hit the official PPA today, I

[Desktop-packages] [Bug 1845801] Re: Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.

2019-10-15 Thread Ted Goddard

Confirmed: the user can successfully log in with auto login turned off.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1845801

Title:
  Automatic login fails and then all subsequent logins fail. Killing
  gnome-session-binary fixes it, or just not using automatic login.

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-session package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM
  login screen (which I shouldn't; I have auto login enabled), and
  logging in just takes me back to the same user selection screen even
  though the password is correct.

  If I switch to a TTY and run `sudo pkill gnome-session-binary`,
  logging in through GDM starts working again.

  I should add that the do-release-upgrade was rocky; I did it in a
  terminal from within gnome, went away for a while, and when I
  returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo
  dpkg --configure -a` and complete the upgrade, but I don't know if
  something's still messed up due to that.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1)
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 28 19:55:42 2019
  DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit()
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4]
  InstallationDate: Installed on 2019-09-14 (13 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: MSI MS-7A67
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic 
root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Default string
  dmi.board.name: H270I GAMING PRO AC (MS-7A67)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7A67
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+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 1845801] Re: Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.

2019-10-15 Thread Ted Goddard

I will test with auto login turned off. Is there a different video
driver setting that might be useful to test, like VGA only?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1845801

Title:
  Automatic login fails and then all subsequent logins fail. Killing
  gnome-session-binary fixes it, or just not using automatic login.

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-session package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM
  login screen (which I shouldn't; I have auto login enabled), and
  logging in just takes me back to the same user selection screen even
  though the password is correct.

  If I switch to a TTY and run `sudo pkill gnome-session-binary`,
  logging in through GDM starts working again.

  I should add that the do-release-upgrade was rocky; I did it in a
  terminal from within gnome, went away for a while, and when I
  returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo
  dpkg --configure -a` and complete the upgrade, but I don't know if
  something's still messed up due to that.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1)
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 28 19:55:42 2019
  DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit()
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4]
  InstallationDate: Installed on 2019-09-14 (13 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: MSI MS-7A67
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic 
root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Default string
  dmi.board.name: H270I GAMING PRO AC (MS-7A67)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7A67
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+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 1845362] Re: gnome-font-viewer crashed with signal 5 in _XEventsQueued()

2019-10-15 Thread Launchpad Bug Tracker

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: gnome-font-viewer (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-font-viewer in Ubuntu.
https://bugs.launchpad.net/bugs/1845362

Title:
  gnome-font-viewer crashed with signal 5 in _XEventsQueued()

Status in gnome-font-viewer package in Ubuntu:
  Confirmed

Bug description:
  Reproducible crash (tested on Ubuntu and Xubuntu) or freezing of
  application during ISO testing of a live-session.

  Application will crash if there is an attempt to close it or scroll
  through fonts. On one occasion my laptop was rendered unusable when
  Firefox was launched while trying to report the crash to Launchpad.

  After the bug report has been sent gnome-font-viewer will freeze when
  automatically restarted. No fonts are displayed.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-font-viewer 3.34.0-1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.416
  CurrentDesktop: XFCE
  Date: Wed Sep 25 17:34:17 2019
  ExecutablePath: /usr/bin/gnome-font-viewer
  LiveMediaBuild: Xubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190925)
  ProcCmdline: gnome-font-viewer
  ProcEnviron:
   LANGUAGE=en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: gnome-font-viewer
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-font-viewer crashed with signal 5 in _XEventsQueued()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-font-viewer/+bug/1845362/+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 1845898] Re: Unable to set touchpad Edge Scrolling in Eoan

2019-10-15 Thread Erick Brunzell

Sorry for the delay. I performed a fresh install of 20191014 last night,
then updated it this AM so we'd be working with an out-of-box
experience. After the update and a reboot I opened System Settings >
Devices > Mouse & Touchpad and changed Natural Scrolling and Tap-to-
click to off while also changing Edge Scrolling to ON.

Opening Test Your Settings indicates that the changes were applied
correctly but immediately after closing System Settings the Edge
Scrolling setting reverts to off. That can be verified both by the
touchpad behavior and reopening the Mouse & Touchpad settings UI. The
other settings changes "stick" as they should.

lance@lance-e6400:~$ journalctl -b 0
-- Logs begin at Mon 2019-10-14 22:46:09 CDT, end at Tue 2019-10-15 15:42:44 CDT
Oct 15 15:33:49 lance-e6400 kernel: microcode: microcode updated early to revisi
Oct 15 15:33:49 lance-e6400 kernel: Linux version 5.3.0-18-generic (buildd@lcy01
Oct 15 15:33:49 lance-e6400 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.3.0
Oct 15 15:33:49 lance-e6400 kernel: KERNEL supported cpus:
Oct 15 15:33:49 lance-e6400 kernel:   Intel GenuineIntel
Oct 15 15:33:49 lance-e6400 kernel:   AMD AuthenticAMD
Oct 15 15:33:49 lance-e6400 kernel:   Hygon HygonGenuine
Oct 15 15:33:49 lance-e6400 kernel:   Centaur CentaurHauls
Oct 15 15:33:49 lance-e6400 kernel:   zhaoxin   Shanghai  
Oct 15 15:33:49 lance-e6400 kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x8
Oct 15 15:33:49 lance-e6400 kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SS
Oct 15 15:33:49 lance-e6400 kernel: x86/fpu: Enabled xstate features 0x3, contex
Oct 15 15:33:49 lance-e6400 kernel: BIOS-provided physical RAM map:
Oct 15 15:33:49 lance-e6400 kernel: BIOS-e820: [mem 0x-0x000
Oct 15 15:33:49 lance-e6400 kernel: BIOS-e820: [mem 0x0009f000-0x000
Oct 15 15:33:49 lance-e6400 kernel: BIOS-e820: [mem 0x0010-0x000
Oct 15 15:33:49 lance-e6400 kernel: BIOS-e820: [mem 0xdd04d400-0x000
Oct 15 15:33:49 lance-e6400 kernel: BIOS-e820: [mem 0xdd04f400-0x000
Oct 15 15:33:49 lance-e6400 kernel: BIOS-e820: [mem 0xf800-0x000
Oct 15 15:33:49 lance-e6400 kernel: BIOS-e820: [mem 0xfec0-0x000
Oct 15 15:33:49 lance-e6400 kernel: BIOS-e820: [mem 0xfed18000-0x000
Oct 15 15:33:49 lance-e6400 kernel: BIOS-e820: [mem 0xfed2-0x000
 
For the rest of this I attached a Logitech M317 mouse. Here's the requested 
output with out-of-box settings:

lance@lance-e6400:~$ sudo libinput list-devices
[sudo] password for lance: 
Device:   Video Bus
Kernel:   /dev/input/event8
Group:1
Seat: seat0, default
Capabilities: keyboard 
Tap-to-click: n/a
Tap-and-drag: n/a
Tap drag lock:n/a
Left-handed:  n/a
Nat.scrolling:n/a
Middle emulation: n/a
Calibration:  n/a
Scroll methods:   none
Click methods:none
Disable-w-typing: n/a
Accel profiles:   n/a
Rotation: n/a

Device:   Power Button
Kernel:   /dev/input/event1
Group:2
Seat: seat0, default
Capabilities: keyboard 
Tap-to-click: n/a
Tap-and-drag: n/a
Tap drag lock:n/a
Left-handed:  n/a
Nat.scrolling:n/a
Middle emulation: n/a
Calibration:  n/a
Scroll methods:   none
Click methods:none
Disable-w-typing: n/a
Accel profiles:   n/a
Rotation: n/a

Device:   Lid Switch
Kernel:   /dev/input/event0
Group:3
Seat: seat0, default
Capabilities: switch
Tap-to-click: n/a
Tap-and-drag: n/a
Tap drag lock:n/a
Left-handed:  n/a
Nat.scrolling:n/a
Middle emulation: n/a
Calibration:  n/a
Scroll methods:   none
Click methods:none
Disable-w-typing: n/a
Accel profiles:   n/a
Rotation: n/a

Device:   Sleep Button
Kernel:   /dev/input/event2
Group:4
Seat: seat0, default
Capabilities: keyboard 
Tap-to-click: n/a
Tap-and-drag: n/a
Tap drag lock:n/a
Left-handed:  n/a
Nat.scrolling:n/a
Middle emulation: n/a
Calibration:  n/a
Scroll methods:   none
Click methods:none
Disable-w-typing: n/a
Accel profiles:   n/a
Rotation: n/a

Device:   HID 413c:8157
Kernel:   /dev/input/event4
Group:5
Seat: seat0, default
Capabilities: keyboard 
Tap-to-click: n/a
Tap-and-drag: n/a
Tap drag lock:n/a
Left-handed:  n/a
Nat.scrolling:n/a
Middle emulation: n/a
Calibration:  n/a
Scroll methods:   none
Click methods:none
Disable-w-typing: n/a
Accel profiles:   n/a
Rotation: n/a

Device:   HDA Intel Dock Mic
Kernel:   /dev/input/event9
Group:6
Seat: seat0, default
Capabilities: 
Tap-to-click: n/a
Tap-and-drag: n/a
Tap drag lock:n/a
Left-handed:  n/a
Nat.scrolling:n/a
Middle emulation: n/a
Calibration:  n/a
Scroll methods:   none
Click methods:none

[Desktop-packages] [Bug 1848210] Re: ghostscript: ensure update of cups-filter

2019-10-15 Thread Eric Desrochers

** Tags added: sts-sponsor-slashd

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups-filters in Ubuntu.
https://bugs.launchpad.net/bugs/1848210

Title:
  ghostscript: ensure update of cups-filter

Status in cups-filters package in Ubuntu:
  New
Status in ghostscript package in Ubuntu:
  Invalid
Status in cups-filters source package in Xenial:
  New
Status in ghostscript source package in Xenial:
  In Progress
Status in cups-filters source package in Bionic:
  New
Status in ghostscript source package in Bionic:
  In Progress

Bug description:
  [Impact]

   * After an update of ghostscript but not cups-filters
     (which is possible; eg unattended-upgrade/landscape)
     users may hit errors printing PDF files (LP#1828401).

   * Landscape and unattended-upgrade allows packages
 updates to security updates / USN-only, thus
     ghostscript is updated for CVE-2019-3839-1 and -2
     (version 9.26~dfsg+0-0ubuntu0.18.04.9 and 16.04.9)
     which may break printing PDF files on cups-filters.

   * So, to ensure that ghostscript and cups-filters are
     both updated, add a versioned 'Breaks:' relationship
     to ghostscript for older cups-filters versions which
     are not yet fixed.

     Per Debian Policy [1]:

   """
   Normally a Breaks entry will have an “earlier than” version clause;
   such a Breaks is introduced in the version ... [that] reveals a bug
   in earlier versions of the broken package ...

   This use of Breaks will inform higher-level package management tools
   that the broken package must be upgraded before the new one.
   """

   * A versioned 'Depends:' relationship is not possible
     as ghostscript doesn't depend on cups-filters, thus
     it's possible to have ghostscript installed without
     cups-filters at all.

  [Test Case]

   * Install cups-filters version without fix for LP#1828401:
     1.20.2-0ubuntu3 in Bionic, and 1.8.3-2ubuntu3.4 in Xenial.

   * Update ghostscript to/later than fix for CVE-2019-3839-1/-2
     9.26~dfsg+0-0ubuntu0.18.04.9 in Bionic / .16.04.9 in Xenial.

   * Notice it does _not_ update cups-filters to version with fix:
     1.20.2-0ubuntu3.1 in Bionic, and 1.8.3-2ubuntu3.5 in Xenial.

   * $ wget -O ppd-with-pdf-support.ppd \
   
'http://www.openprinting.org/ppd-o-matic.php?driver=hl7x0=Brother-HL-1020=1'

   * $ wget -O dummy.pdf \
   https://www.w3.org/WAI/ER/tests/xhtml/testfiles/resources/pdf/dummy.pdf

   * $ foomatic-rip -v --ppd ppd-with-pdf-support.ppd dummy.pdf
     ...
     Filetype: PDF
     GPL Ghostscript 9.26: Unrecoverable error, exit code 1
     Process is dying with "Unable to determine number of pages, page count: -1
     ", exit stat 3
     ...

   * Note it's broken.

   * Install ghostscript (test) packages with the relationships
     'Breaks: cups-filters (<< 1.20.2-0ubuntu3.1)' in Bionic or
     'Breaks: ..., cups-filters (<< 1.8.3-2ubuntu3.5)' in Xenial.

   * Note it _does_ update cups-filters to version with fix.

   * $ foomatic-rip -v --ppd ppd-with-pdf-support.ppd dummy.pdf
     ...
     Filetype: PDF
     File contains 1 pages
     Starting renderer with command: <...>
     ...

   * Note it's now working.

  [Regression Potential]

   * Low.  This only causes an update to cups-filters to a version
     that fixes an already identified/resolved problem (LP#1828401),
     which is available in bionic- & xenial-updates since May 2019.

  [Other Info]

   * This is only required in Xenial and Bionic.

   * Trusty doesn't have the ghostscript update that causes the problem.

   * Disco/Eoan have the cups-filters fix that it requires (1.22.5+).

  [1] https://www.debian.org/doc/debian-policy/ch-relationships.html
  #packages-which-break-other-packages-breaks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1848210/+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 1848279] [NEW] Nautilus GUI does not work

2019-10-15 Thread L_M

Public bug reported:


Dear Nautilus development and bug report staff,

on a fresh Linux install I just used Arduino IDE and Matlab R2019b, then 
attached an external usb hard disk and my smartphone for a file transfer, and 
everything worked. The day after, the white nautilus folder icon on the left 
bar could not make me open the folders, I could do it just from the terminal. 
So I used:

sudo dpkg-reconfigure --default-priority nautilus

and everything seemed to be fine. The day after, the white folder icon
was not working, and the folders that I put on the desktop disappeared.
I then used:

sudo apt-get purge nautilus

then log off, then

sudo apt-get install nautilus

but nothing changed. What can I do to restore the GUI. Now I just can use the 
CLI. 
I have (through lsb_release -rd):
Description:Ubuntu 19.04
Release:19.04

and (through apt-cache policy nautilus:
nautilus:
  Installato: 1:3.32.1-0ubuntu0.19.04.0
  Candidato:  1:3.32.1-0ubuntu0.19.04.0
  Tabella versione:
 *** 1:3.32.1-0ubuntu0.19.04.0 500
500 http://it.archive.ubuntu.com/ubuntu disco-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 1:3.32.0-0ubuntu2 500
500 http://it.archive.ubuntu.com/ubuntu disco/main amd64 Packages


I already looked for similar issues in Ask Ubuntu. Best regards.

** Affects: nautilus (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: desktop folder nautilus ubuntu

-- 
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/1848279

Title:
  Nautilus GUI does not work

Status in nautilus package in Ubuntu:
  New

Bug description:
  
  Dear Nautilus development and bug report staff,

  on a fresh Linux install I just used Arduino IDE and Matlab R2019b, then 
attached an external usb hard disk and my smartphone for a file transfer, and 
everything worked. The day after, the white nautilus folder icon on the left 
bar could not make me open the folders, I could do it just from the terminal. 
  So I used:

  sudo dpkg-reconfigure --default-priority nautilus

  and everything seemed to be fine. The day after, the white folder icon
  was not working, and the folders that I put on the desktop
  disappeared. I then used:

  sudo apt-get purge nautilus

  then log off, then

  sudo apt-get install nautilus

  but nothing changed. What can I do to restore the GUI. Now I just can use the 
CLI. 
  I have (through lsb_release -rd):
  Description:  Ubuntu 19.04
  Release:  19.04

  and (through apt-cache policy nautilus:
  nautilus:
Installato: 1:3.32.1-0ubuntu0.19.04.0
Candidato:  1:3.32.1-0ubuntu0.19.04.0
Tabella versione:
   *** 1:3.32.1-0ubuntu0.19.04.0 500
  500 http://it.archive.ubuntu.com/ubuntu disco-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.32.0-0ubuntu2 500
  500 http://it.archive.ubuntu.com/ubuntu disco/main amd64 Packages

  
  I already looked for similar issues in Ask Ubuntu. Best regards.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1848279/+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 1848277] Re: Won't start, get "cannot open display: :0" message

2019-10-15 Thread SimonWerner

I tested it under wayland and it appears to work fine.

** Description changed:

  When I run the snap store version of gnome-calculator I get the
  following message:
  
  (gnome-calculator:21891): Gtk-WARNING **: 10:14:30.632: cannot open
  display: :0
  
  And gnome-calculator never starts.  I'm running it using an X11 session,
- not wayland.
- 
+ not wayland.  I tested it under wayland and it appears to work fine.
  
  `lsb_release -rd`:
  Description:  Ubuntu 19.10
  Release:  19.10
  
  `gnome-calculator  --version`:
  gnome-calculator 3.34.0
  
  Version according to Software Center:
  3.34.0+git1.822e4b58

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-calculator in Ubuntu.
https://bugs.launchpad.net/bugs/1848277

Title:
  Won't start, get "cannot open display: :0" message

Status in gnome-calculator package in Ubuntu:
  New

Bug description:
  When I run the snap store version of gnome-calculator I get the
  following message:

  (gnome-calculator:21891): Gtk-WARNING **: 10:14:30.632: cannot open
  display: :0

  And gnome-calculator never starts.  I'm running it using an X11
  session, not wayland.  I tested it under wayland and it appears to
  work fine.

  `lsb_release -rd`:
  Description:  Ubuntu 19.10
  Release:  19.10

  `gnome-calculator  --version`:
  gnome-calculator 3.34.0

  Version according to Software Center:
  3.34.0+git1.822e4b58

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1848277/+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 1848277] [NEW] Won't start, get "cannot open display: :0" message

2019-10-15 Thread SimonWerner

Public bug reported:

When I run the snap store version of gnome-calculator I get the
following message:

(gnome-calculator:21891): Gtk-WARNING **: 10:14:30.632: cannot open
display: :0

And gnome-calculator never starts.  I'm running it using an X11 session,
not wayland.  I tested it under wayland and it appears to work fine.

`lsb_release -rd`:
Description:Ubuntu 19.10
Release:19.10

`gnome-calculator  --version`:
gnome-calculator 3.34.0

Version according to Software Center:
3.34.0+git1.822e4b58

** Affects: gnome-calculator (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-calculator in Ubuntu.
https://bugs.launchpad.net/bugs/1848277

Title:
  Won't start, get "cannot open display: :0" message

Status in gnome-calculator package in Ubuntu:
  New

Bug description:
  When I run the snap store version of gnome-calculator I get the
  following message:

  (gnome-calculator:21891): Gtk-WARNING **: 10:14:30.632: cannot open
  display: :0

  And gnome-calculator never starts.  I'm running it using an X11
  session, not wayland.  I tested it under wayland and it appears to
  work fine.

  `lsb_release -rd`:
  Description:  Ubuntu 19.10
  Release:  19.10

  `gnome-calculator  --version`:
  gnome-calculator 3.34.0

  Version according to Software Center:
  3.34.0+git1.822e4b58

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1848277/+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 1848210] Re: ghostscript: ensure update of cups-filter

2019-10-15 Thread Eric Desrochers

I will be more favourable to do the other way around by adding a
"Depends:" in cups-filters package for ghostscript version "X" ?
Especially if cups-filters always needs ghostscript ?

It will force ghostscript to get updated instead of making the package
install to fails/breaks.

At least it's worth testing IMHO that avenue before considering the
current "Breaks:" approach.

- Eric


** Also affects: cups-filters (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ghostscript in Ubuntu.
https://bugs.launchpad.net/bugs/1848210

Title:
  ghostscript: ensure update of cups-filter

Status in cups-filters package in Ubuntu:
  New
Status in ghostscript package in Ubuntu:
  Invalid
Status in cups-filters source package in Xenial:
  New
Status in ghostscript source package in Xenial:
  In Progress
Status in cups-filters source package in Bionic:
  New
Status in ghostscript source package in Bionic:
  In Progress

Bug description:
  [Impact]

   * After an update of ghostscript but not cups-filters
     (which is possible; eg unattended-upgrade/landscape)
     users may hit errors printing PDF files (LP#1828401).

   * Landscape and unattended-upgrade allows packages
 updates to security updates / USN-only, thus
     ghostscript is updated for CVE-2019-3839-1 and -2
     (version 9.26~dfsg+0-0ubuntu0.18.04.9 and 16.04.9)
     which may break printing PDF files on cups-filters.

   * So, to ensure that ghostscript and cups-filters are
     both updated, add a versioned 'Breaks:' relationship
     to ghostscript for older cups-filters versions which
     are not yet fixed.

     Per Debian Policy [1]:

   """
   Normally a Breaks entry will have an “earlier than” version clause;
   such a Breaks is introduced in the version ... [that] reveals a bug
   in earlier versions of the broken package ...

   This use of Breaks will inform higher-level package management tools
   that the broken package must be upgraded before the new one.
   """

   * A versioned 'Depends:' relationship is not possible
     as ghostscript doesn't depend on cups-filters, thus
     it's possible to have ghostscript installed without
     cups-filters at all.

  [Test Case]

   * Install cups-filters version without fix for LP#1828401:
     1.20.2-0ubuntu3 in Bionic, and 1.8.3-2ubuntu3.4 in Xenial.

   * Update ghostscript to/later than fix for CVE-2019-3839-1/-2
     9.26~dfsg+0-0ubuntu0.18.04.9 in Bionic / .16.04.9 in Xenial.

   * Notice it does _not_ update cups-filters to version with fix:
     1.20.2-0ubuntu3.1 in Bionic, and 1.8.3-2ubuntu3.5 in Xenial.

   * $ wget -O ppd-with-pdf-support.ppd \
   
'http://www.openprinting.org/ppd-o-matic.php?driver=hl7x0=Brother-HL-1020=1'

   * $ wget -O dummy.pdf \
   https://www.w3.org/WAI/ER/tests/xhtml/testfiles/resources/pdf/dummy.pdf

   * $ foomatic-rip -v --ppd ppd-with-pdf-support.ppd dummy.pdf
     ...
     Filetype: PDF
     GPL Ghostscript 9.26: Unrecoverable error, exit code 1
     Process is dying with "Unable to determine number of pages, page count: -1
     ", exit stat 3
     ...

   * Note it's broken.

   * Install ghostscript (test) packages with the relationships
     'Breaks: cups-filters (<< 1.20.2-0ubuntu3.1)' in Bionic or
     'Breaks: ..., cups-filters (<< 1.8.3-2ubuntu3.5)' in Xenial.

   * Note it _does_ update cups-filters to version with fix.

   * $ foomatic-rip -v --ppd ppd-with-pdf-support.ppd dummy.pdf
     ...
     Filetype: PDF
     File contains 1 pages
     Starting renderer with command: <...>
     ...

   * Note it's now working.

  [Regression Potential]

   * Low.  This only causes an update to cups-filters to a version
     that fixes an already identified/resolved problem (LP#1828401),
     which is available in bionic- & xenial-updates since May 2019.

  [Other Info]

   * This is only required in Xenial and Bionic.

   * Trusty doesn't have the ghostscript update that causes the problem.

   * Disco/Eoan have the cups-filters fix that it requires (1.22.5+).

  [1] https://www.debian.org/doc/debian-policy/ch-relationships.html
  #packages-which-break-other-packages-breaks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1848210/+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 1848210] Re: ghostscript: ensure update of cups-filter

2019-10-15 Thread Eric Desrochers

I will be more favourable to do the other way around by adding a
"Depends:" in cups-filters package for ghostscript version "X" ?
Especially if cups-filters always needs ghostscript ?

"Depends: ghostscript (>= CUPS_FILTER_VERSION)"

to force ghostscript to get updated instead of making the package
install to fails/breaks.

At least it's worth testing IMHO that avenue before considering the
current "Breaks:" approach.

Eric

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ghostscript in Ubuntu.
https://bugs.launchpad.net/bugs/1848210

Title:
  ghostscript: ensure update of cups-filter

Status in cups-filters package in Ubuntu:
  New
Status in ghostscript package in Ubuntu:
  Invalid
Status in cups-filters source package in Xenial:
  New
Status in ghostscript source package in Xenial:
  In Progress
Status in cups-filters source package in Bionic:
  New
Status in ghostscript source package in Bionic:
  In Progress

Bug description:
  [Impact]

   * After an update of ghostscript but not cups-filters
     (which is possible; eg unattended-upgrade/landscape)
     users may hit errors printing PDF files (LP#1828401).

   * Landscape and unattended-upgrade allows packages
 updates to security updates / USN-only, thus
     ghostscript is updated for CVE-2019-3839-1 and -2
     (version 9.26~dfsg+0-0ubuntu0.18.04.9 and 16.04.9)
     which may break printing PDF files on cups-filters.

   * So, to ensure that ghostscript and cups-filters are
     both updated, add a versioned 'Breaks:' relationship
     to ghostscript for older cups-filters versions which
     are not yet fixed.

     Per Debian Policy [1]:

   """
   Normally a Breaks entry will have an “earlier than” version clause;
   such a Breaks is introduced in the version ... [that] reveals a bug
   in earlier versions of the broken package ...

   This use of Breaks will inform higher-level package management tools
   that the broken package must be upgraded before the new one.
   """

   * A versioned 'Depends:' relationship is not possible
     as ghostscript doesn't depend on cups-filters, thus
     it's possible to have ghostscript installed without
     cups-filters at all.

  [Test Case]

   * Install cups-filters version without fix for LP#1828401:
     1.20.2-0ubuntu3 in Bionic, and 1.8.3-2ubuntu3.4 in Xenial.

   * Update ghostscript to/later than fix for CVE-2019-3839-1/-2
     9.26~dfsg+0-0ubuntu0.18.04.9 in Bionic / .16.04.9 in Xenial.

   * Notice it does _not_ update cups-filters to version with fix:
     1.20.2-0ubuntu3.1 in Bionic, and 1.8.3-2ubuntu3.5 in Xenial.

   * $ wget -O ppd-with-pdf-support.ppd \
   
'http://www.openprinting.org/ppd-o-matic.php?driver=hl7x0=Brother-HL-1020=1'

   * $ wget -O dummy.pdf \
   https://www.w3.org/WAI/ER/tests/xhtml/testfiles/resources/pdf/dummy.pdf

   * $ foomatic-rip -v --ppd ppd-with-pdf-support.ppd dummy.pdf
     ...
     Filetype: PDF
     GPL Ghostscript 9.26: Unrecoverable error, exit code 1
     Process is dying with "Unable to determine number of pages, page count: -1
     ", exit stat 3
     ...

   * Note it's broken.

   * Install ghostscript (test) packages with the relationships
     'Breaks: cups-filters (<< 1.20.2-0ubuntu3.1)' in Bionic or
     'Breaks: ..., cups-filters (<< 1.8.3-2ubuntu3.5)' in Xenial.

   * Note it _does_ update cups-filters to version with fix.

   * $ foomatic-rip -v --ppd ppd-with-pdf-support.ppd dummy.pdf
     ...
     Filetype: PDF
     File contains 1 pages
     Starting renderer with command: <...>
     ...

   * Note it's now working.

  [Regression Potential]

   * Low.  This only causes an update to cups-filters to a version
     that fixes an already identified/resolved problem (LP#1828401),
     which is available in bionic- & xenial-updates since May 2019.

  [Other Info]

   * This is only required in Xenial and Bionic.

   * Trusty doesn't have the ghostscript update that causes the problem.

   * Disco/Eoan have the cups-filters fix that it requires (1.22.5+).

  [1] https://www.debian.org/doc/debian-policy/ch-relationships.html
  #packages-which-break-other-packages-breaks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1848210/+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 1848210] Re: ghostscript: ensure update of cups-filter

The approach to fix/deliver this is under discussion for a bit.
We'll move forward once that's more clearly defined.

** Patch removed: "lp1848210_bionic.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1848210/+attachment/5297380/+files/lp1848210_bionic.debdiff

** Patch removed: "lp1848210_xenial.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1848210/+attachment/5297381/+files/lp1848210_xenial.debdiff

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ghostscript in Ubuntu.
https://bugs.launchpad.net/bugs/1848210

Title:
  ghostscript: ensure update of cups-filter

Status in ghostscript package in Ubuntu:
  Invalid
Status in ghostscript source package in Xenial:
  In Progress
Status in ghostscript source package in Bionic:
  In Progress

Bug description:
  [Impact]

   * After an update of ghostscript but not cups-filters
     (which is possible; eg unattended-upgrade/landscape)
     users may hit errors printing PDF files (LP#1828401).

   * Landscape and unattended-upgrade allows packages
 updates to security updates / USN-only, thus
     ghostscript is updated for CVE-2019-3839-1 and -2
     (version 9.26~dfsg+0-0ubuntu0.18.04.9 and 16.04.9)
     which may break printing PDF files on cups-filters.

   * So, to ensure that ghostscript and cups-filters are
     both updated, add a versioned 'Breaks:' relationship
     to ghostscript for older cups-filters versions which
     are not yet fixed.

     Per Debian Policy [1]:

   """
   Normally a Breaks entry will have an “earlier than” version clause;
   such a Breaks is introduced in the version ... [that] reveals a bug
   in earlier versions of the broken package ...

   This use of Breaks will inform higher-level package management tools
   that the broken package must be upgraded before the new one.
   """

   * A versioned 'Depends:' relationship is not possible
     as ghostscript doesn't depend on cups-filters, thus
     it's possible to have ghostscript installed without
     cups-filters at all.

  [Test Case]

   * Install cups-filters version without fix for LP#1828401:
     1.20.2-0ubuntu3 in Bionic, and 1.8.3-2ubuntu3.4 in Xenial.

   * Update ghostscript to/later than fix for CVE-2019-3839-1/-2
     9.26~dfsg+0-0ubuntu0.18.04.9 in Bionic / .16.04.9 in Xenial.

   * Notice it does _not_ update cups-filters to version with fix:
     1.20.2-0ubuntu3.1 in Bionic, and 1.8.3-2ubuntu3.5 in Xenial.

   * $ wget -O ppd-with-pdf-support.ppd \
   
'http://www.openprinting.org/ppd-o-matic.php?driver=hl7x0=Brother-HL-1020=1'

   * $ wget -O dummy.pdf \
   https://www.w3.org/WAI/ER/tests/xhtml/testfiles/resources/pdf/dummy.pdf

   * $ foomatic-rip -v --ppd ppd-with-pdf-support.ppd dummy.pdf
     ...
     Filetype: PDF
     GPL Ghostscript 9.26: Unrecoverable error, exit code 1
     Process is dying with "Unable to determine number of pages, page count: -1
     ", exit stat 3
     ...

   * Note it's broken.

   * Install ghostscript (test) packages with the relationships
     'Breaks: cups-filters (<< 1.20.2-0ubuntu3.1)' in Bionic or
     'Breaks: ..., cups-filters (<< 1.8.3-2ubuntu3.5)' in Xenial.

   * Note it _does_ update cups-filters to version with fix.

   * $ foomatic-rip -v --ppd ppd-with-pdf-support.ppd dummy.pdf
     ...
     Filetype: PDF
     File contains 1 pages
     Starting renderer with command: <...>
     ...

   * Note it's now working.

  [Regression Potential]

   * Low.  This only causes an update to cups-filters to a version
     that fixes an already identified/resolved problem (LP#1828401),
     which is available in bionic- & xenial-updates since May 2019.

  [Other Info]

   * This is only required in Xenial and Bionic.

   * Trusty doesn't have the ghostscript update that causes the problem.

   * Disco/Eoan have the cups-filters fix that it requires (1.22.5+).

  [1] https://www.debian.org/doc/debian-policy/ch-relationships.html
  #packages-which-break-other-packages-breaks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1848210/+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 1183368] Re: [upstream] EDITING: Find by format doesn't work with non-integer font sizes

2019-10-15 Thread Christopher M. Penalver

EliCoten, this is no longer reproducible in:
Version: 6.3.2.2 (x64)
Build ID: 98b30e735bda24bc04ab42594c85f7fd8be07b9c

Ctrl+H > Format > Size: 11.5 > OK > Find: Hello > Find Next

and the Hello with a 11.5 pt was highlighted.

This is a significant bug in Ubuntu. If you need a fix for the bug in
previous versions of Ubuntu, please perform as much as possible of the
SRU Procedure [1] to bring the need to a developer's attention.

[1]: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure

** No longer affects: libreoffice (Ubuntu)

** Project changed: df-libreoffice => libreoffice (Ubuntu)

** Changed in: libreoffice (Ubuntu)
   Importance: Low => Undecided

** Changed in: libreoffice (Ubuntu)
   Status: Confirmed => New

** Changed in: libreoffice (Ubuntu)
 Remote watch: Document Foundation Bugzilla #64918 => None

** Changed in: libreoffice (Ubuntu)
   Importance: Undecided => Medium

** Changed in: libreoffice (Ubuntu)
   Status: New => Fix Released

-- 
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/1183368

Title:
  [upstream] EDITING: Find by format doesn't work with non-integer font
  sizes

Status in libreoffice package in Ubuntu:
  Fix Released

Bug description:
  1) lsb_release -rd
  Description:  Ubuntu 13.04
  Release:  13.04

  2) apt-cache policy libreoffice-writer
  libreoffice-writer:
Installed: 1:4.0.2-0ubuntu1
Candidate: 1:4.0.2-0ubuntu1
Version table:
   *** 1:4.0.2-0ubuntu1 0
  500 http://archive.ubuntu.com/ubuntu/ raring/main i386 Packages
  100 /var/lib/dpkg/status

  3) What is expected to happen in Writer via a terminal:
  cd ~/Desktop && wget 
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1183368/+attachment/3691990/+files/example.odt
 && lowriter --nologo example.odt

  Ctrl+H -> click dropdown box Search for -> button More Options ->
  button Format... -> in the Text Format(Search) window tab Font in text
  box Size type 11.5 -> button OK and underneath the Search dropdown box
  it notes 11.5, as it does in Microsoft Office Professional Plus 2010
  Word Version 14.0.6023.1000 (32-bit).

  4) What happens instead is it displays 12. However, it still
  successfully searches and finds 11.5 so this is a cosmetic UI issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: libreoffice-writer 1:4.0.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-21.32-generic 3.8.8
  Uname: Linux 3.8.0-21-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Thu May 23 15:01:20 2013
  MarkForUpload: True
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to raring on 2013-04-30 (23 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1183368/+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 1093765] Re: [upstream] switching paragraph style changes character orientation

2019-10-15 Thread Christopher M. Penalver

Reproducible verbatim as per Bug Description in:
Version: 6.3.2.2 (x64)
Build ID: 98b30e735bda24bc04ab42594c85f7fd8be07b9c

Given this is upstreamed already -> Triaged

** Changed in: libreoffice (Ubuntu)
   Importance: Undecided => Medium

** Changed in: libreoffice (Ubuntu)
   Status: Incomplete => Triaged

-- 
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/1093765

Title:
  [upstream] switching paragraph style changes character orientation

Status in LibreOffice:
  Unknown
Status in libreoffice package in Ubuntu:
  Triaged

Bug description:
  1) lsb_release -rd
  Description:  Ubuntu 13.04
  Release:  13.04

  2) apt-cache policy libreoffice-writer
  libreoffice-writer:
Installed: 1:4.0.2-0ubuntu1
Candidate: 1:4.0.2-0ubuntu1
Version table:
   *** 1:4.0.2-0ubuntu1 0
  500 http://archive.ubuntu.com/ubuntu/ raring/main i386 Packages
  100 /var/lib/dpkg/status

  3) What is expected to happen in Writer via a terminal:
  cd ~/Desktop && wget 
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1093765/+attachment/3688368/+files/test-bug1093765.doc
 && lowriter --nologo test-bug1093765.doc

  is select all -> change combo box Apply Style from Text Body to
  Heading 1 and the text style changes, preserving the character order.

  4) What happens instead is:
  (Example text=) טקסט לדוגמה

  changes to:
  טקסט לדוגמה (=Example text)

  Microsoft Office Professional Plus 2010 Word Version 14.0.6023.1000 (32-bit) 
changes it to:
  =)טקסט לדוגמהExample text(

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: libreoffice-core 1:3.6.2~rc2-0ubuntu4
  ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1
  Uname: Linux 3.5.0-21-generic x86_64
  ApportVersion: 2.6.1-0ubuntu9
  Architecture: amd64
  Date: Wed Dec 26 11:20:42 2012
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  MarkForUpload: True
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to quantal on 2012-10-19 (67 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1093765/+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 1848210] Re: ghostscript: ensure update of cups-filter

** Description changed:

  [Impact]
  
   * After an update of ghostscript but not cups-filters
-    (which is possible, including via Landscape tooling)
+    (which is possible; eg unattended-upgrade/landscape)
     users may hit errors printing PDF files (LP#1828401).
  
-  * Landscape allows packages updates to USN-only thus
+  * Landscape and unattended-upgrade allows packages
+updates to security updates / USN-only, thus
     ghostscript is updated for CVE-2019-3839-1 and -2
     (version 9.26~dfsg+0-0ubuntu0.18.04.9 and 16.04.9)
     which may break printing PDF files on cups-filters.
  
   * So, to ensure that ghostscript and cups-filters are
     both updated, add a versioned 'Breaks:' relationship
     to ghostscript for older cups-filters versions which
     are not yet fixed.
  
     Per Debian Policy [1]:
  
   """
   Normally a Breaks entry will have an “earlier than” version clause;
   such a Breaks is introduced in the version ... [that] reveals a bug
   in earlier versions of the broken package ...
  
   This use of Breaks will inform higher-level package management tools
   that the broken package must be upgraded before the new one.
   """
  
   * A versioned 'Depends:' relationship is not possible
     as ghostscript doesn't depend on cups-filters, thus
     it's possible to have ghostscript installed without
     cups-filters at all.
  
  [Test Case]
  
   * Install cups-filters version without fix for LP#1828401:
     1.20.2-0ubuntu3 in Bionic, and 1.8.3-2ubuntu3.4 in Xenial.
  
   * Update ghostscript to/later than fix for CVE-2019-3839-1/-2
     9.26~dfsg+0-0ubuntu0.18.04.9 in Bionic / .16.04.9 in Xenial.
  
   * Notice it does _not_ update cups-filters to version with fix:
     1.20.2-0ubuntu3.1 in Bionic, and 1.8.3-2ubuntu3.5 in Xenial.
  
   * $ wget -O ppd-with-pdf-support.ppd \
   
'http://www.openprinting.org/ppd-o-matic.php?driver=hl7x0=Brother-HL-1020=1'
  
   * $ wget -O dummy.pdf \
   https://www.w3.org/WAI/ER/tests/xhtml/testfiles/resources/pdf/dummy.pdf
  
   * $ foomatic-rip -v --ppd ppd-with-pdf-support.ppd dummy.pdf
     ...
     Filetype: PDF
     GPL Ghostscript 9.26: Unrecoverable error, exit code 1
     Process is dying with "Unable to determine number of pages, page count: -1
     ", exit stat 3
     ...
  
   * Note it's broken.
  
   * Install ghostscript (test) packages with the relationships
     'Breaks: cups-filters (<< 1.20.2-0ubuntu3.1)' in Bionic or
     'Breaks: ..., cups-filters (<< 1.8.3-2ubuntu3.5)' in Xenial.
  
   * Note it _does_ update cups-filters to version with fix.
  
   * $ foomatic-rip -v --ppd ppd-with-pdf-support.ppd dummy.pdf
     ...
     Filetype: PDF
     File contains 1 pages
     Starting renderer with command: <...>
     ...
  
   * Note it's now working.
  
  [Regression Potential]
  
   * Low.  This only causes an update to cups-filters to a version
     that fixes an already identified/resolved problem (LP#1828401),
     which is available in bionic- & xenial-updates since May 2019.
  
  [Other Info]
  
   * This is only required in Xenial and Bionic.
  
   * Trusty doesn't have the ghostscript update that causes the problem.
  
   * Disco/Eoan have the cups-filters fix that it requires (1.22.5+).
  
  [1] https://www.debian.org/doc/debian-policy/ch-relationships.html
  #packages-which-break-other-packages-breaks

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ghostscript in Ubuntu.
https://bugs.launchpad.net/bugs/1848210

Title:
  ghostscript: ensure update of cups-filter

Status in ghostscript package in Ubuntu:
  Invalid
Status in ghostscript source package in Xenial:
  In Progress
Status in ghostscript source package in Bionic:
  In Progress

Bug description:
  [Impact]

   * After an update of ghostscript but not cups-filters
     (which is possible; eg unattended-upgrade/landscape)
     users may hit errors printing PDF files (LP#1828401).

   * Landscape and unattended-upgrade allows packages
 updates to security updates / USN-only, thus
     ghostscript is updated for CVE-2019-3839-1 and -2
     (version 9.26~dfsg+0-0ubuntu0.18.04.9 and 16.04.9)
     which may break printing PDF files on cups-filters.

   * So, to ensure that ghostscript and cups-filters are
     both updated, add a versioned 'Breaks:' relationship
     to ghostscript for older cups-filters versions which
     are not yet fixed.

     Per Debian Policy [1]:

   """
   Normally a Breaks entry will have an “earlier than” version clause;
   such a Breaks is introduced in the version ... [that] reveals a bug
   in earlier versions of the broken package ...

   This use of Breaks will inform higher-level package management tools
   that the broken package must be upgraded before the new one.
   """

   * A versioned 'Depends:' relationship is not possible
     as ghostscript doesn't depend on cups-filters, thus
     it's

[Desktop-packages] [Bug 1183368] [NEW] [upstream] EDITING: Find by format doesn't work with non-integer font sizes

2019-10-15 Thread Launchpad Bug Tracker

You have been subscribed to a public bug:

1) lsb_release -rd
Description:Ubuntu 13.04
Release:13.04

2) apt-cache policy libreoffice-writer
libreoffice-writer:
  Installed: 1:4.0.2-0ubuntu1
  Candidate: 1:4.0.2-0ubuntu1
  Version table:
 *** 1:4.0.2-0ubuntu1 0
500 http://archive.ubuntu.com/ubuntu/ raring/main i386 Packages
100 /var/lib/dpkg/status

3) What is expected to happen in Writer via a terminal:
cd ~/Desktop && wget 
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1183368/+attachment/3691990/+files/example.odt
 && lowriter --nologo example.odt

Ctrl+H -> click dropdown box Search for -> button More Options -> button
Format... -> in the Text Format(Search) window tab Font in text box Size
type 11.5 -> button OK and underneath the Search dropdown box it notes
11.5, as it does in Microsoft Office Professional Plus 2010 Word Version
14.0.6023.1000 (32-bit).

4) What happens instead is it displays 12. However, it still
successfully searches and finds 11.5 so this is a cosmetic UI issue.

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: libreoffice-writer 1:4.0.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-21.32-generic 3.8.8
Uname: Linux 3.8.0-21-generic x86_64
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
Date: Thu May 23 15:01:20 2013
MarkForUpload: True
SourcePackage: libreoffice
UpgradeStatus: Upgraded to raring on 2013-04-30 (23 days ago)

** Affects: libreoffice (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug raring
-- 
[upstream] EDITING: Find by format doesn't work with non-integer font sizes
https://bugs.launchpad.net/bugs/1183368
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to libreoffice in Ubuntu.

-- 
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 1767505] Re: Rhythmbox Radio - Internal Data Stream Error

2019-10-15 Thread Byron

I pulled the source code and fixed it myself. I tried to push it back
up, but I guess they were not interested.

-- 
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/1767505

Title:
  Rhythmbox Radio - Internal Data Stream Error

Status in rhythmbox package in Ubuntu:
  Confirmed

Bug description:
  When trying to play any radio station, I get a dialog that states
  after about 20 seconds of playing:

  Couldn't start playback

  Internal data stream error

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1767505/+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 1848210] Re: ghostscript: ensure update of cups-filter

** Description changed:

  [Impact]
  
   * After an update of ghostscript but not cups-filters
     (which is possible, including via Landscape tooling)
     users may hit errors printing PDF files (LP#1828401).
  
   * Landscape allows packages updates to USN-only thus
     ghostscript is updated for CVE-2019-3839-1 and -2
     (version 9.26~dfsg+0-0ubuntu0.18.04.9 and 16.04.9)
     which may break printing PDF files on cups-filters.
  
   * So, to ensure that ghostscript and cups-filters are
     both updated, add a versioned 'Breaks:' relationship
     to ghostscript for older cups-filters versions which
     are not yet fixed.
+ 
+Per Debian Policy [1]:
+ 
+  """
+  Normally a Breaks entry will have an “earlier than” version clause;
+  such a Breaks is introduced in the version ... [that] reveals a bug
+  in earlier versions of the broken package ...
+ 
+  This use of Breaks will inform higher-level package management tools
+  that the broken package must be upgraded before the new one.
+  """
  
   * A versioned 'Depends:' relationship is not possible
     as ghostscript doesn't depend on cups-filters, thus
     it's possible to have ghostscript installed without
     cups-filters at all.
  
  [Test Case]
  
   * Install cups-filters version without fix for LP#1828401:
     1.20.2-0ubuntu3 in Bionic, and 1.8.3-2ubuntu3.4 in Xenial.
  
   * Update ghostscript to/later than fix for CVE-2019-3839-1/-2
     9.26~dfsg+0-0ubuntu0.18.04.9 in Bionic / .16.04.9 in Xenial.
  
   * Notice it does _not_ update cups-filters to version with fix:
     1.20.2-0ubuntu3.1 in Bionic, and 1.8.3-2ubuntu3.5 in Xenial.
  
   * $ wget -O ppd-with-pdf-support.ppd \
   
'http://www.openprinting.org/ppd-o-matic.php?driver=hl7x0=Brother-HL-1020=1'
  
   * $ wget -O dummy.pdf \
   https://www.w3.org/WAI/ER/tests/xhtml/testfiles/resources/pdf/dummy.pdf
  
   * $ foomatic-rip -v --ppd ppd-with-pdf-support.ppd dummy.pdf
     ...
     Filetype: PDF
     GPL Ghostscript 9.26: Unrecoverable error, exit code 1
     Process is dying with "Unable to determine number of pages, page count: -1
     ", exit stat 3
     ...
  
   * Note it's broken.
  
   * Install ghostscript (test) packages with the relationships
     'Breaks: cups-filters (<< 1.20.2-0ubuntu3.1)' in Bionic or
     'Breaks: ..., cups-filters (<< 1.8.3-2ubuntu3.5)' in Xenial.
  
   * Note it _does_ update cups-filters to version with fix.
  
   * $ foomatic-rip -v --ppd ppd-with-pdf-support.ppd dummy.pdf
     ...
     Filetype: PDF
     File contains 1 pages
     Starting renderer with command: <...>
     ...
  
   * Note it's now working.
  
  [Regression Potential]
  
   * Low.  This only causes an update to cups-filters to a version
     that fixes an already identified/resolved problem (LP#1828401),
     which is available in bionic- & xenial-updates since May 2019.
+ 
+ [1] https://www.debian.org/doc/debian-policy/ch-relationships.html
+ #packages-which-break-other-packages-breaks

** Description changed:

  [Impact]
  
   * After an update of ghostscript but not cups-filters
     (which is possible, including via Landscape tooling)
     users may hit errors printing PDF files (LP#1828401).
  
   * Landscape allows packages updates to USN-only thus
     ghostscript is updated for CVE-2019-3839-1 and -2
     (version 9.26~dfsg+0-0ubuntu0.18.04.9 and 16.04.9)
     which may break printing PDF files on cups-filters.
  
   * So, to ensure that ghostscript and cups-filters are
     both updated, add a versioned 'Breaks:' relationship
     to ghostscript for older cups-filters versions which
     are not yet fixed.
  
-Per Debian Policy [1]:
+    Per Debian Policy [1]:
  
-  """
-  Normally a Breaks entry will have an “earlier than” version clause;
-  such a Breaks is introduced in the version ... [that] reveals a bug
-  in earlier versions of the broken package ...
+  """
+  Normally a Breaks entry will have an “earlier than” version clause;
+  such a Breaks is introduced in the version ... [that] reveals a bug
+  in earlier versions of the broken package ...
  
-  This use of Breaks will inform higher-level package management tools
-  that the broken package must be upgraded before the new one.
-  """
+  This use of Breaks will inform higher-level package management tools
+  that the broken package must be upgraded before the new one.
+  """
  
   * A versioned 'Depends:' relationship is not possible
     as ghostscript doesn't depend on cups-filters, thus
     it's possible to have ghostscript installed without
     cups-filters at all.
  
  [Test Case]
  
   * Install cups-filters version without fix for LP#1828401:
     1.20.2-0ubuntu3 in Bionic, and 1.8.3-2ubuntu3.4 in Xenial.
  
   * Update ghostscript to/later than fix for CVE-2019-3839-1/-2
     9.26~dfsg+0-0ubuntu0.18.04.9 in Bionic / .16.04.9 in Xenial.
  
   * Notice it does _not_ update cups-filters to version with

[Desktop-packages] [Bug 1848210] Re: ghostscript: ensure update of cups-filter

** Patch added: "lp1848210_xenial.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1848210/+attachment/5297381/+files/lp1848210_xenial.debdiff

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ghostscript in Ubuntu.
https://bugs.launchpad.net/bugs/1848210

Title:
  ghostscript: ensure update of cups-filter

Status in ghostscript package in Ubuntu:
  Invalid
Status in ghostscript source package in Xenial:
  In Progress
Status in ghostscript source package in Bionic:
  In Progress

Bug description:
  [Impact]

   * After an update of ghostscript but not cups-filters
     (which is possible, including via Landscape tooling)
     users may hit errors printing PDF files (LP#1828401).

   * Landscape allows packages updates to USN-only thus
     ghostscript is updated for CVE-2019-3839-1 and -2
     (version 9.26~dfsg+0-0ubuntu0.18.04.9 and 16.04.9)
     which may break printing PDF files on cups-filters.

   * So, to ensure that ghostscript and cups-filters are
     both updated, add a versioned 'Breaks:' relationship
     to ghostscript for older cups-filters versions which
     are not yet fixed.

   * A versioned 'Depends:' relationship is not possible
     as ghostscript doesn't depend on cups-filters, thus
     it's possible to have ghostscript installed without
     cups-filters at all.

  [Test Case]

   * Install cups-filters version without fix for LP#1828401:
     1.20.2-0ubuntu3 in Bionic, and 1.8.3-2ubuntu3.4 in Xenial.

   * Update ghostscript to/later than fix for CVE-2019-3839-1/-2
     9.26~dfsg+0-0ubuntu0.18.04.9 in Bionic / .16.04.9 in Xenial.

   * Notice it does _not_ update cups-filters to version with fix:
     1.20.2-0ubuntu3.1 in Bionic, and 1.8.3-2ubuntu3.5 in Xenial.

   * $ wget -O ppd-with-pdf-support.ppd \
   
'http://www.openprinting.org/ppd-o-matic.php?driver=hl7x0=Brother-HL-1020=1'

   * $ wget -O dummy.pdf \
   https://www.w3.org/WAI/ER/tests/xhtml/testfiles/resources/pdf/dummy.pdf

   * $ foomatic-rip -v --ppd ppd-with-pdf-support.ppd dummy.pdf
     ...
     Filetype: PDF
     GPL Ghostscript 9.26: Unrecoverable error, exit code 1
     Process is dying with "Unable to determine number of pages, page count: -1
     ", exit stat 3
     ...

   * Note it's broken.

   * Install ghostscript (test) packages with the relationships
     'Breaks: cups-filters (<< 1.20.2-0ubuntu3.1)' in Bionic or
     'Breaks: ..., cups-filters (<< 1.8.3-2ubuntu3.5)' in Xenial.

   * Note it _does_ update cups-filters to version with fix.

   * $ foomatic-rip -v --ppd ppd-with-pdf-support.ppd dummy.pdf
     ...
     Filetype: PDF
     File contains 1 pages
     Starting renderer with command: <...>
     ...

   * Note it's now working.

  [Regression Potential]

   * Low.  This only causes an update to cups-filters to a version
     that fixes an already identified/resolved problem (LP#1828401),
     which is available in bionic- & xenial-updates since May 2019.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1848210/+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 1848210] Re: ghostscript: ensure update of cups-filter

Test packages used for verification in comments #1 and #2
built successfully on all architectures, ppa:mfo/sf246942 [1].

[1] https://launchpad.net/~mfo/+archive/ubuntu/sf246942

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ghostscript in Ubuntu.
https://bugs.launchpad.net/bugs/1848210

Title:
  ghostscript: ensure update of cups-filter

Status in ghostscript package in Ubuntu:
  Invalid
Status in ghostscript source package in Xenial:
  In Progress
Status in ghostscript source package in Bionic:
  In Progress

Bug description:
  [Impact]

   * After an update of ghostscript but not cups-filters
     (which is possible, including via Landscape tooling)
     users may hit errors printing PDF files (LP#1828401).

   * Landscape allows packages updates to USN-only thus
     ghostscript is updated for CVE-2019-3839-1 and -2
     (version 9.26~dfsg+0-0ubuntu0.18.04.9 and 16.04.9)
     which may break printing PDF files on cups-filters.

   * So, to ensure that ghostscript and cups-filters are
     both updated, add a versioned 'Breaks:' relationship
     to ghostscript for older cups-filters versions which
     are not yet fixed.

   * A versioned 'Depends:' relationship is not possible
     as ghostscript doesn't depend on cups-filters, thus
     it's possible to have ghostscript installed without
     cups-filters at all.

  [Test Case]

   * Install cups-filters version without fix for LP#1828401:
     1.20.2-0ubuntu3 in Bionic, and 1.8.3-2ubuntu3.4 in Xenial.

   * Update ghostscript to/later than fix for CVE-2019-3839-1/-2
     9.26~dfsg+0-0ubuntu0.18.04.9 in Bionic / .16.04.9 in Xenial.

   * Notice it does _not_ update cups-filters to version with fix:
     1.20.2-0ubuntu3.1 in Bionic, and 1.8.3-2ubuntu3.5 in Xenial.

   * $ wget -O ppd-with-pdf-support.ppd \
   
'http://www.openprinting.org/ppd-o-matic.php?driver=hl7x0=Brother-HL-1020=1'

   * $ wget -O dummy.pdf \
   https://www.w3.org/WAI/ER/tests/xhtml/testfiles/resources/pdf/dummy.pdf

   * $ foomatic-rip -v --ppd ppd-with-pdf-support.ppd dummy.pdf
     ...
     Filetype: PDF
     GPL Ghostscript 9.26: Unrecoverable error, exit code 1
     Process is dying with "Unable to determine number of pages, page count: -1
     ", exit stat 3
     ...

   * Note it's broken.

   * Install ghostscript (test) packages with the relationships
     'Breaks: cups-filters (<< 1.20.2-0ubuntu3.1)' in Bionic or
     'Breaks: ..., cups-filters (<< 1.8.3-2ubuntu3.5)' in Xenial.

   * Note it _does_ update cups-filters to version with fix.

   * $ foomatic-rip -v --ppd ppd-with-pdf-support.ppd dummy.pdf
     ...
     Filetype: PDF
     File contains 1 pages
     Starting renderer with command: <...>
     ...

   * Note it's now working.

  [Regression Potential]

   * Low.  This only causes an update to cups-filters to a version
     that fixes an already identified/resolved problem (LP#1828401),
     which is available in bionic- & xenial-updates since May 2019.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1848210/+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 1848210] Re: ghostscript: ensure update of cups-filter

** Patch added: "lp1848210_bionic.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1848210/+attachment/5297380/+files/lp1848210_bionic.debdiff

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ghostscript in Ubuntu.
https://bugs.launchpad.net/bugs/1848210

Title:
  ghostscript: ensure update of cups-filter

Status in ghostscript package in Ubuntu:
  Invalid
Status in ghostscript source package in Xenial:
  In Progress
Status in ghostscript source package in Bionic:
  In Progress

Bug description:
  [Impact]

   * After an update of ghostscript but not cups-filters
     (which is possible, including via Landscape tooling)
     users may hit errors printing PDF files (LP#1828401).

   * Landscape allows packages updates to USN-only thus
     ghostscript is updated for CVE-2019-3839-1 and -2
     (version 9.26~dfsg+0-0ubuntu0.18.04.9 and 16.04.9)
     which may break printing PDF files on cups-filters.

   * So, to ensure that ghostscript and cups-filters are
     both updated, add a versioned 'Breaks:' relationship
     to ghostscript for older cups-filters versions which
     are not yet fixed.

   * A versioned 'Depends:' relationship is not possible
     as ghostscript doesn't depend on cups-filters, thus
     it's possible to have ghostscript installed without
     cups-filters at all.

  [Test Case]

   * Install cups-filters version without fix for LP#1828401:
     1.20.2-0ubuntu3 in Bionic, and 1.8.3-2ubuntu3.4 in Xenial.

   * Update ghostscript to/later than fix for CVE-2019-3839-1/-2
     9.26~dfsg+0-0ubuntu0.18.04.9 in Bionic / .16.04.9 in Xenial.

   * Notice it does _not_ update cups-filters to version with fix:
     1.20.2-0ubuntu3.1 in Bionic, and 1.8.3-2ubuntu3.5 in Xenial.

   * $ wget -O ppd-with-pdf-support.ppd \
   
'http://www.openprinting.org/ppd-o-matic.php?driver=hl7x0=Brother-HL-1020=1'

   * $ wget -O dummy.pdf \
   https://www.w3.org/WAI/ER/tests/xhtml/testfiles/resources/pdf/dummy.pdf

   * $ foomatic-rip -v --ppd ppd-with-pdf-support.ppd dummy.pdf
     ...
     Filetype: PDF
     GPL Ghostscript 9.26: Unrecoverable error, exit code 1
     Process is dying with "Unable to determine number of pages, page count: -1
     ", exit stat 3
     ...

   * Note it's broken.

   * Install ghostscript (test) packages with the relationships
     'Breaks: cups-filters (<< 1.20.2-0ubuntu3.1)' in Bionic or
     'Breaks: ..., cups-filters (<< 1.8.3-2ubuntu3.5)' in Xenial.

   * Note it _does_ update cups-filters to version with fix.

   * $ foomatic-rip -v --ppd ppd-with-pdf-support.ppd dummy.pdf
     ...
     Filetype: PDF
     File contains 1 pages
     Starting renderer with command: <...>
     ...

   * Note it's now working.

  [Regression Potential]

   * Low.  This only causes an update to cups-filters to a version
     that fixes an already identified/resolved problem (LP#1828401),
     which is available in bionic- & xenial-updates since May 2019.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1848210/+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 1848210] Re: ghostscript: ensure update of cups-filter

Testing on Xenial
---

Files)

$ wget -O ppd-with-pdf-support.ppd
'http://www.openprinting.org/ppd-o-matic.php?driver=hl7x0
=Brother-HL-1020=1'

$ wget -O dummy.pdf
https://www.w3.org/WAI/ER/tests/xhtml/testfiles/resources/pdf/dummy.pdf

Test 0) Before updating ghostscript or cups-filters
$ dpkg -s cups-filters ghostscript | grep ^Version:
Version: 1.8.3-2ubuntu3.4
Version: 9.26~dfsg+0-0ubuntu0.16.04.8

$ foomatic-rip -v --ppd ppd-with-pdf-support.ppd dummy.pdf
...
Filetype: PDF
File contains 1 pages
Starting renderer with command: <...>
...


Test 1) After updating ghostscript (not cups-filters)

$ dpkg -s cups-filters ghostscript | grep ^Version:
Version: 1.8.3-2ubuntu3.4
Version: 9.26~dfsg+0-0ubuntu0.16.04.11

$ foomatic-rip -v --ppd ppd-with-pdf-support.ppd dummy.pdf
...
Filetype: PDF
GPL Ghostscript 9.26: Unrecoverable error, exit code 1
Process is dying with "Unable to determine number of pages, page count: -1
", exit stat 3
...


Test 2) Checking before updating ghostscript with test package (thus 
cups-filters too)

Checking update of cups-filters with apt-get and apt:

$ sudo apt-get install --dry-run ghostscript
...
The following packages will be upgraded:
  cups-filters cups-filters-core-drivers ghostscript libgs9 libgs9-common
...
Inst cups-filters [1.8.3-2ubuntu3.4] (1.8.3-2ubuntu3.5 
Ubuntu:16.04/xenial-updates, Ubuntu:16.04/xenial-security [amd64])
Inst ghostscript [9.26~dfsg+0-0ubuntu0.16.04.11] 
(9.26~dfsg+0-0ubuntu0.16.04.11+test20191510b1 mfo-sf246942:16.04/xenial 
[amd64]) []
...

$ sudo apt install --dry-run ghostscript
...
The following packages will be upgraded:
  cups-filters cups-filters-core-drivers ghostscript libgs9 libgs9-common
...
Inst cups-filters [1.8.3-2ubuntu3.4] (1.8.3-2ubuntu3.5 
Ubuntu:16.04/xenial-updates, Ubuntu:16.04/xenial-security [amd64])
Inst ghostscript [9.26~dfsg+0-0ubuntu0.16.04.11] 
(9.26~dfsg+0-0ubuntu0.16.04.11+test20191510b1 mfo-sf246942:16.04/xenial 
[amd64]) []
...


Test 3) After updating ghostscript with test package (thus cups-filters
too)

$ dpkg -s cups-filters ghostscript | grep ^Version:
Version: 1.8.3-2ubuntu3.5
Version: 9.26~dfsg+0-0ubuntu0.16.04.11+test20191510b1

$ foomatic-rip -v --ppd ppd-with-pdf-support.ppd dummy.pdf
...
Filetype: PDF
File contains 1 pages
Starting renderer with command: <...>
...

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ghostscript in Ubuntu.
https://bugs.launchpad.net/bugs/1848210

Title:
  ghostscript: ensure update of cups-filter

Status in ghostscript package in Ubuntu:
  Invalid
Status in ghostscript source package in Xenial:
  In Progress
Status in ghostscript source package in Bionic:
  In Progress

Bug description:
  [Impact]

   * After an update of ghostscript but not cups-filters
     (which is possible, including via Landscape tooling)
     users may hit errors printing PDF files (LP#1828401).

   * Landscape allows packages updates to USN-only thus
     ghostscript is updated for CVE-2019-3839-1 and -2
     (version 9.26~dfsg+0-0ubuntu0.18.04.9 and 16.04.9)
     which may break printing PDF files on cups-filters.

   * So, to ensure that ghostscript and cups-filters are
     both updated, add a versioned 'Breaks:' relationship
     to ghostscript for older cups-filters versions which
     are not yet fixed.

   * A versioned 'Depends:' relationship is not possible
     as ghostscript doesn't depend on cups-filters, thus
     it's possible to have ghostscript installed without
     cups-filters at all.

  [Test Case]

   * Install cups-filters version without fix for LP#1828401:
     1.20.2-0ubuntu3 in Bionic, and 1.8.3-2ubuntu3.4 in Xenial.

   * Update ghostscript to/later than fix for CVE-2019-3839-1/-2
     9.26~dfsg+0-0ubuntu0.18.04.9 in Bionic / .16.04.9 in Xenial.

   * Notice it does _not_ update cups-filters to version with fix:
     1.20.2-0ubuntu3.1 in Bionic, and 1.8.3-2ubuntu3.5 in Xenial.

   * $ wget -O ppd-with-pdf-support.ppd \
   
'http://www.openprinting.org/ppd-o-matic.php?driver=hl7x0=Brother-HL-1020=1'

   * $ wget -O dummy.pdf \
   https://www.w3.org/WAI/ER/tests/xhtml/testfiles/resources/pdf/dummy.pdf

   * $ foomatic-rip -v --ppd ppd-with-pdf-support.ppd dummy.pdf
     ...
     Filetype: PDF
     GPL Ghostscript 9.26: Unrecoverable error, exit code 1
     Process is dying with "Unable to determine number of pages, page count: -1
     ", exit stat 3
     ...

   * Note it's broken.

   * Install ghostscript (test) packages with the relationships
     'Breaks: cups-filters (<< 1.20.2-0ubuntu3.1)' in Bionic or
     'Breaks: ..., cups-filters (<< 1.8.3-2ubuntu3.5)' in Xenial.

   * Note it _does_ update cups-filters to version with fix.

   * $ foomatic-rip -v --ppd ppd-with-pdf-support.ppd dummy.pdf
     ...
     Filetype: PDF
     File contains 1 pages
     Starting renderer with command: <...>
     ...

   * Note it's now working.

  [Regression Potential]

   * Low.  This only causes an update to cups-filters

[Desktop-packages] [Bug 1848210] Re: ghostscript: ensure update of cups-filter

Testing on Bionic
---

Files)

$ wget -O ppd-with-pdf-support.ppd
'http://www.openprinting.org/ppd-o-matic.php?driver=hl7x0
=Brother-HL-1020=1'

$ wget -O dummy.pdf
https://www.w3.org/WAI/ER/tests/xhtml/testfiles/resources/pdf/dummy.pdf


Test 0) Before updating ghostscript or cups-filters

$ dpkg -s cups-filters ghostscript | grep ^Version:
Version: 1.20.2-0ubuntu3
Version: 9.26~dfsg+0-0ubuntu0.18.04.8

$ foomatic-rip -v --ppd ppd-with-pdf-support.ppd dummy.pdf
...
Filetype: PDF
File contains 1 pages
Starting renderer with command: <...>
...


Test 1) After updating ghostscript (not cups-filters)

$ dpkg -s cups-filters ghostscript | grep ^Version:
Version: 1.20.2-0ubuntu3
Version: 9.26~dfsg+0-0ubuntu0.18.04.11

$ foomatic-rip -v --ppd ppd-with-pdf-support.ppd dummy.pdf
...
Filetype: PDF
GPL Ghostscript 9.26: Unrecoverable error, exit code 1
Process is dying with "Unable to determine number of pages, page count: -1
", exit stat 3
...


Test 2) Checking before updating ghostscript with test package (thus 
cups-filters too)

Checking update of cups-filters with apt:

$ sudo apt install --dry-run ghostscript
...
The following packages will be upgraded:
  cups-filters ghostscript libgs9 libgs9-common
...
Inst cups-filters [1.20.2-0ubuntu3] (1.20.2-0ubuntu3.1 
Ubuntu:18.04/bionic-updates, Ubuntu:18.04/bionic-security [amd64])
Inst ghostscript [9.26~dfsg+0-0ubuntu0.18.04.11] 
(9.26~dfsg+0-0ubuntu0.18.04.11+test20191510b1 mfo-sf246942:18.04/bionic 
[amd64]) []
...

Checking update of cups-filters with apt-get:

$ sudo apt-get install --dry-run ghostscript
...
The following packages will be upgraded:
  cups-filters ghostscript libgs9 libgs9-common
...
Inst cups-filters [1.20.2-0ubuntu3] (1.20.2-0ubuntu3.1 
Ubuntu:18.04/bionic-updates, Ubuntu:18.04/bionic-security [amd64])
Inst ghostscript [9.26~dfsg+0-0ubuntu0.18.04.11] 
(9.26~dfsg+0-0ubuntu0.18.04.11+test20191510b1 mfo-sf246942:18.04/bionic 
[amd64]) []
...


Test 3) After updating ghostscript with test package (thus cups-filters too)

$ dpkg -s cups-filters ghostscript | grep ^Version:
Version: 1.20.2-0ubuntu3.1
Version: 9.26~dfsg+0-0ubuntu0.18.04.11+test20191510b1

$ foomatic-rip -v --ppd ppd-with-pdf-support.ppd dummy.pdf
...
Filetype: PDF
File contains 1 pages
Starting renderer with command: <...>
...

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ghostscript in Ubuntu.
https://bugs.launchpad.net/bugs/1848210

Title:
  ghostscript: ensure update of cups-filter

Status in ghostscript package in Ubuntu:
  Invalid
Status in ghostscript source package in Xenial:
  In Progress
Status in ghostscript source package in Bionic:
  In Progress

Bug description:
  [Impact]

   * After an update of ghostscript but not cups-filters
     (which is possible, including via Landscape tooling)
     users may hit errors printing PDF files (LP#1828401).

   * Landscape allows packages updates to USN-only thus
     ghostscript is updated for CVE-2019-3839-1 and -2
     (version 9.26~dfsg+0-0ubuntu0.18.04.9 and 16.04.9)
     which may break printing PDF files on cups-filters.

   * So, to ensure that ghostscript and cups-filters are
     both updated, add a versioned 'Breaks:' relationship
     to ghostscript for older cups-filters versions which
     are not yet fixed.

   * A versioned 'Depends:' relationship is not possible
     as ghostscript doesn't depend on cups-filters, thus
     it's possible to have ghostscript installed without
     cups-filters at all.

  [Test Case]

   * Install cups-filters version without fix for LP#1828401:
     1.20.2-0ubuntu3 in Bionic, and 1.8.3-2ubuntu3.4 in Xenial.

   * Update ghostscript to/later than fix for CVE-2019-3839-1/-2
     9.26~dfsg+0-0ubuntu0.18.04.9 in Bionic / .16.04.9 in Xenial.

   * Notice it does _not_ update cups-filters to version with fix:
     1.20.2-0ubuntu3.1 in Bionic, and 1.8.3-2ubuntu3.5 in Xenial.

   * $ wget -O ppd-with-pdf-support.ppd \
   
'http://www.openprinting.org/ppd-o-matic.php?driver=hl7x0=Brother-HL-1020=1'

   * $ wget -O dummy.pdf \
   https://www.w3.org/WAI/ER/tests/xhtml/testfiles/resources/pdf/dummy.pdf

   * $ foomatic-rip -v --ppd ppd-with-pdf-support.ppd dummy.pdf
     ...
     Filetype: PDF
     GPL Ghostscript 9.26: Unrecoverable error, exit code 1
     Process is dying with "Unable to determine number of pages, page count: -1
     ", exit stat 3
     ...

   * Note it's broken.

   * Install ghostscript (test) packages with the relationships
     'Breaks: cups-filters (<< 1.20.2-0ubuntu3.1)' in Bionic or
     'Breaks: ..., cups-filters (<< 1.8.3-2ubuntu3.5)' in Xenial.

   * Note it _does_ update cups-filters to version with fix.

   * $ foomatic-rip -v --ppd ppd-with-pdf-support.ppd dummy.pdf
     ...
     Filetype: PDF
     File contains 1 pages
     Starting renderer with command: <...>
     ...

   * Note it's now working.

  [Regression Potential]

   * Low.  This only causes an update to cups-filters to a version

[Desktop-packages] [Bug 1767505] Re: Rhythmbox Radio - Internal Data Stream Error

2019-10-15 Thread fig_wright

I also have this...

-- 
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/1767505

Title:
  Rhythmbox Radio - Internal Data Stream Error

Status in rhythmbox package in Ubuntu:
  Confirmed

Bug description:
  When trying to play any radio station, I get a dialog that states
  after about 20 seconds of playing:

  Couldn't start playback

  Internal data stream error

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1767505/+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 1848210] Re: ghostscript: ensure update of cups-filter

** Description changed:

- Add a Breaks: relationship to cups-filter to prevent LP#1828401.
+ [Impact]
  
- Landscape allows packages updates to only USNs, so ghostscript
- can be updated to a version that breaks the older cups-filters.
+  * After an update of ghostscript but not cups-filters
+(which is possible, including via Landscape tooling)
+users may hit errors printing PDF files (LP#1828401).
  
- Patches to be provided shortly.
+  * Landscape allows packages updates to USN-only thus
+ghostscript is updated for CVE-2019-3839-1 and -2
+(version 9.26~dfsg+0-0ubuntu0.18.04.9 and 16.04.9)
+which may break printing PDF files on cups-filters.
+ 
+  * So, to ensure that ghostscript and cups-filters are
+both updated, add a versioned 'Breaks:' relationship
+to ghostscript for older cups-filters versions which
+are not yet fixed.
+ 
+  * A versioned 'Depends:' relationship is not possible
+as ghostscript doesn't depend on cups-filters, thus
+it's possible to have ghostscript installed without
+cups-filters at all.
+ 
+ [Test Case]
+ 
+  * Install cups-filters version without fix for LP#1828401:
+1.20.2-0ubuntu3 in Bionic, and 1.8.3-2ubuntu3.4 in Xenial.
+ 
+  * Update ghostscript to/later than fix for CVE-2019-3839-1/-2
+9.26~dfsg+0-0ubuntu0.18.04.9 in Bionic / .16.04.9 in Xenial.
+ 
+  * Notice it does _not_ update of cups-filters.
+ 
+  * $ wget -O ppd-with-pdf-support.ppd \
+  
'http://www.openprinting.org/ppd-o-matic.php?driver=hl7x0=Brother-HL-1020=1'
 
+ 
+  * $ wget -O dummy.pdf \
+  https://www.w3.org/WAI/ER/tests/xhtml/testfiles/resources/pdf/dummy.pdf
+ 
+  * $ foomatic-rip -v --ppd ppd-with-pdf-support.ppd dummy.pdf
+...
+Filetype: PDF
+GPL Ghostscript 9.26: Unrecoverable error, exit code 1
+Process is dying with "Unable to determine number of pages, page count: -1
+", exit stat 3
+...
+ 
+  * Note it's broken.
+ 
+  * Install ghostscript (test) packages with the relationships
+'Breaks: cups-filters (<< 1.20.2-0ubuntu3.1)' in Bionic or
+'Breaks: ..., cups-filters (<< 1.8.3-2ubuntu3.5)' in Xenial.
+ 
+  * Note it _does_ update cups-filters.
+ 
+  * $ foomatic-rip -v --ppd ppd-with-pdf-support.ppd dummy.pdf
+...
+Filetype: PDF
+File contains 1 pages
+Starting renderer with command: <...>
+...
+ 
+  * Note it's now working.
+ 
+ [Regression Potential]
+ 
+  * Low.  This only causes an update to cups-filters to a version
+that fixes an already identified/resolved problem (LP#1828401),
+which is available in bionic- & xenial-updates since May 2019.

** Description changed:

  [Impact]
  
-  * After an update of ghostscript but not cups-filters
-(which is possible, including via Landscape tooling)
-users may hit errors printing PDF files (LP#1828401).
+  * After an update of ghostscript but not cups-filters
+    (which is possible, including via Landscape tooling)
+    users may hit errors printing PDF files (LP#1828401).
  
-  * Landscape allows packages updates to USN-only thus
-ghostscript is updated for CVE-2019-3839-1 and -2
-(version 9.26~dfsg+0-0ubuntu0.18.04.9 and 16.04.9)
-which may break printing PDF files on cups-filters.
+  * Landscape allows packages updates to USN-only thus
+    ghostscript is updated for CVE-2019-3839-1 and -2
+    (version 9.26~dfsg+0-0ubuntu0.18.04.9 and 16.04.9)
+    which may break printing PDF files on cups-filters.
  
-  * So, to ensure that ghostscript and cups-filters are
-both updated, add a versioned 'Breaks:' relationship
-to ghostscript for older cups-filters versions which
-are not yet fixed.
+  * So, to ensure that ghostscript and cups-filters are
+    both updated, add a versioned 'Breaks:' relationship
+    to ghostscript for older cups-filters versions which
+    are not yet fixed.
  
-  * A versioned 'Depends:' relationship is not possible
-as ghostscript doesn't depend on cups-filters, thus
-it's possible to have ghostscript installed without
-cups-filters at all.
+  * A versioned 'Depends:' relationship is not possible
+    as ghostscript doesn't depend on cups-filters, thus
+    it's possible to have ghostscript installed without
+    cups-filters at all.
  
  [Test Case]
  
-  * Install cups-filters version without fix for LP#1828401:
-1.20.2-0ubuntu3 in Bionic, and 1.8.3-2ubuntu3.4 in Xenial.
+  * Install cups-filters version without fix for LP#1828401:
+    1.20.2-0ubuntu3 in Bionic, and 1.8.3-2ubuntu3.4 in Xenial.
  
-  * Update ghostscript to/later than fix for CVE-2019-3839-1/-2
-9.26~dfsg+0-0ubuntu0.18.04.9 in Bionic / .16.04.9 in Xenial.
+  * Update ghostscript to/later than fix for CVE-2019-3839-1/-2
+    9.26~dfsg+0-0ubuntu0.18.04.9 in Bionic / .16.04.9 in Xenial.
  
-  * Notice it does _not_ update of cups-filters.
+  * Notice it does _not_ update cups-filters to version with fix:
+1.20.2-0ubuntu3.1 in Bionic, and 1.8.3-2ubuntu3.5 in Xenial.
  
-  * $ wget -O

[Desktop-packages] [Bug 36156] Re: [Upstream] [hardy] Writer mis-shifts OLE object in Microsoft Word .doc

Launchpad has imported 9 comments from the remote bug at
https://bugs.documentfoundation.org/show_bug.cgi?id=37152.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2011-05-12T15:05:49+00:00 Christopher M. Penalver wrote:

Created attachment 46649
pd18.doc

Downstream bug may be found at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/36156

OOo bug may be found at:
http://openoffice.org/bugzilla/show_bug.cgi?id=87388

1) lsb_release -rd
Description: Ubuntu 11.04
Release: 11.04

2) apt-cache policy libreoffice-writer
libreoffice-writer:
  Installed: 1:3.3.2-1ubuntu5
  Candidate: 1:3.3.2-1ubuntu5
  Version table:
 *** 1:3.3.2-1ubuntu5 0
500 http://us.archive.ubuntu.com/ubuntu/ natty-proposed/main i386
Packages
100 /var/lib/dpkg/status
 1:3.3.2-1ubuntu4 0
500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages

3) What is expected to happen in LibreOffice Writer via the Terminal:

cd ~/Desktop && wget
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/36144/+attachment/8047/+files/pd18.doc
&& lowriter -nologo pd18.doc

it looks as it does in Word.

4) What happens instead is the OLE object at the top of page 1 is mis-
shifted to the left.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/36156/comments/4


On 2011-12-23T12:02:05+00:00 Björn Michaelsen wrote:

[This is an automated message.]
This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it
started right out as NEW without ever being explicitly confirmed. The bug is
changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back
to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 
prereleases.
Details on how to test the 3.5.0 beta1 can be found at:
http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1

more detail on this bulk operation: http://nabble.documentfoundation.org
/RFC-Operation-Spamzilla-tp3607474p3607474.html

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/36156/comments/8


On 2012-01-03T14:50:13+00:00 Christopher M. Penalver wrote:

Problem reproducible in:
LOdev 3.5.0beta2 
Build ID: 8589e48-760cc4d-f39cf3d-1b2857e-60db978
Microsoft Windows Vista Business 6.0.6002 Service Pack 2 Build 6002

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/36156/comments/10


On 2013-01-20T13:44:40+00:00 Stgohi-lobugs wrote:

reproducible with LO 3.6.4.3. (Win7 Home, 64bit)

The file looks different in LO and in Word 2007: 
on page 1 and 5 and regarding the colour of the footer.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/36156/comments/13


On 2014-07-20T10:44:40+00:00 Alexpikptz wrote:

Created attachment 103135
Comparative screenshot of MS Word 2007 and LO Writer 4.3.0

Reproducible with LibreOffice 4.2.5 and 4.3.0 on Debian and Windows 7. I
attach a screenshot which demonstrates a correct representation and the
issue. I do not see any problem with font clor in a footer.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/36156/comments/15


On 2015-09-04T02:48:02+00:00 Qa-admin-q wrote:

** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open,
confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked
on this bug report. During that time, it's possible that the bug has
been fixed, or the details of the problem have changed. We'd really
appreciate your help in getting confirmation that the bug is still
present.

If you have time, please do the following:

Test to see if the bug is still present on a currently supported version of 
LibreOffice (5.0.0.5 or later)
   https://www.libreoffice.org/download/

   If the bug is present, please leave a comment that includes the version of 
LibreOffice and your operating system, and any changes you see in the bug 
behavior
 
 If the bug is NOT present, please set the bug's Status field to 
RESOLVED-WORKSFORME and leave a short comment that includes your version of 
LibreOffice and Operating System

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this

[Desktop-packages] [Bug 1848210] Re: ghostscript: ensure update of cups-filter

** Summary changed:

- ghostscript: add Breaks: relationship to cups-filter
+ ghostscript: ensure update of cups-filter

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ghostscript in Ubuntu.
https://bugs.launchpad.net/bugs/1848210

Title:
  ghostscript: ensure update of cups-filter

Status in ghostscript package in Ubuntu:
  Invalid
Status in ghostscript source package in Xenial:
  In Progress
Status in ghostscript source package in Bionic:
  In Progress

Bug description:
  Add a Breaks: relationship to cups-filter to prevent LP#1828401.

  Landscape allows packages updates to only USNs, so ghostscript
  can be updated to a version that breaks the older cups-filters.

  Patches to be provided shortly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1848210/+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 1631161] Re: Preferred output device is not remembered between logins

2019-10-15 Thread Sebastien Bacher

@Doug, you should probably open a new bug including details about your
audio configuration, your ubuntu version/desktop and journal log

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1631161

Title:
  Preferred output device is not remembered between logins

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Whenever I reboot anew, pulseaudio has forgotten the correct audio
  port which I have set using the kde pulseaudio tool.

  I use line out, but it defaults to headphones, which is incorrect for
  my current setup. I expect it to remember that I wanted line out every
  time.

  Once selected, everything runs fine for that session, but it doesn't
  get saved and defaults back to the wrong output every time.

  Guessing this is pulseaudio as it happens with the gnome tool also.

  Tested not working in 16.04, 16.10 and Mint 18 (packages from 16.04).

  Policy installed: 1:8.0-0ubuntu3

  Cheers
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   kvd1577 F...m pulseaudio
   /dev/snd/pcmC0D0p:   kvd1577 F...m pulseaudio
   /dev/snd/controlC0:  kvd1577 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Linux 18
  InstallationDate: Installed on 2016-10-02 (5 days ago)
  InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160904
  NonfreeKernelModules: nvidia_uvm nvidia
  Package: pulseaudio 1:8.0-0ubuntu3 [origin: Ubuntu]
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Tags: sarah third-party-packages
  Uname: Linux 4.4.0-38-generic x86_64
  UnreportableReason: This is not an official Linux package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/24/2013
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F5f
  dmi.board.name: GA-770T-USB3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF5f:bd09/24/2013:svnGigabyteTechnologyCo.,Ltd.:pnGA-770T-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-770T-USB3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-770T-USB3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1631161/+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 1847772] Re: E-mail folder names are not localized in thunderbird 68

Launchpad has imported 60 comments from the remote bug at
https://bugzilla.mozilla.org/show_bug.cgi?id=1575512.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2019-08-21T11:09:45+00:00 De-berberich wrote:

Created attachment 9086978
French locale + German language pack.png standard folders stay French

Steps to reproduce:

Download and install French locale of Thunderbird 68.0-candidates/build4.
Install German de.xpi (and/or American-English en-US.xpi or Italian, ...etc) 
language packs.
Open the config editor, create a new string preference, name it 
intl.locale.requested and enter the value "de" (or "en-US" or "it", ...etc) 
without quotation marks.
Restart Thunderbird. 


Actual results :

The Thunderbird GUI now is in German (or English or Italian) excepting
the names of the default folders in Folder Pane.

Expected results:

Folder names should be translated, too.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1847772/comments/0


On 2019-08-21T11:18:49+00:00 Jorg K wrote:

But the localised versions work, right? Just not the changes with the
language pack?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1847772/comments/1


On 2019-08-21T13:30:41+00:00 De-berberich wrote:

Everything in the localized versions works correctly, tool bars and menus in 
Main window, address book and compose windows.
It's just the folder names in the folder pane which resist to translation and 
keep the original French names of my (French) Thunderbird version when I switch 
from French to German or English or Italian.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1847772/comments/2


On 2019-08-21T17:48:54+00:00 Jorg K wrote:

What happens with en-US TB plus language pack? Do the folders remain in
English? (I can try that myself when I find a moment.)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1847772/comments/3


On 2019-08-21T21:40:47+00:00 De-berberich wrote:

I did further tests with the en-US and German versions of TB 68.0 in new 
separate profiles, installing two or three other language packs.
I could not reproduce the issue. Each time I switched to another language and 
restarted TB the folder names would be translated correctly.
Seems to be a problem of the French TB 68.0 version.
I'll continue testing the French version in a new profile without installing 
any add-ons.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1847772/comments/4


On 2019-08-21T21:46:58+00:00 Jorg K wrote:

Thanks for spending time with this issue. So localised to German +
langpack also works. That's good to know.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1847772/comments/5


On 2019-08-22T14:13:46+00:00 De-berberich wrote:

Created attachment 9087406
TB en-US + de.xpi.png folder pane staying in English

Reply at:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1847772/comments/6


On 2019-08-22T14:24:29+00:00 De-berberich wrote:

I continued testing and trying to reproduce this issue. First I recreated a new 
identical profile for the French version with the de.xpi and en-US.xpi language 
packs. After hours of testing I suddenly had the Folder Pane in French after 
switching to German (de) in intl.locale.requested but I still couldn't identify 
what triggered the error.
Then I re-tested the en-US version of Thunderbird with the fr.xpi and de.xpi 
language packs in a new profile.  Eventually with this version I succeeded to 
provoke the same error : the Folder Pane staying in US-English after switching 
to German (de) which I documented in an new screen shot. But as in the other 
profiles I was unable to identify the factor which triggers this error.

I've been working for years with language packs but I've never before
encountered this issue.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1847772/comments/7


On 2019-08-22T18:00:19+00:00 De-berberich wrote:

Created attachment 9087471
TB 69.0b4 fr + de.xpi.png

Reply at:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1847772/comments/8

[Desktop-packages] [Bug 1848108] Re: [amdgpu] Screen Glitching & Kernel Panic

2019-10-15 Thread Jarrod Farrell

I'm using 5.0.0-31-generic at the moment and it seems to have quelled
the issue, including the graphical issues. So I guess the graphical
issues is a symptom of a problem with the kernel baring something else
having a disagreement with it.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu.
https://bugs.launchpad.net/bugs/1848108

Title:
  [amdgpu] Screen Glitching & Kernel Panic

Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  I've recently updated to Eoan, but it seems like some nasty bugs came
  with it, particularly from the amdgpu package.

  It started with visual glitches but it would occasionally freeze the
  screen with whatever playing in the background and require me to hard-
  shutdown to escape. Attached is an abridged `journalctl -b -1` showing
  the lines were the kernal panic occurred. I'll probably attach more as
  they occur and if it's not redundant.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CompositorRunning: None
  Date: Mon Oct 14 21:27:34 2019
  DistUpgraded: 2019-10-13 05:03:20,327 DEBUG entry '# deb 
http://linux.teamviewer.com/deb stable main # disabled on upgrade to eoan' was 
disabled (unknown mirror)
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Very infrequently
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c3) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Raven Ridge [Radeon Vega Series / Radeon Vega Mobile 
Series] [17aa:506f]
  InstallationDate: Installed on 2019-03-22 (206 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 003: ID 13d3:56a6 IMC Networks Integrated Camera
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20KVCTO1WW
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-18-generic 
root=/dev/mapper/ubuntu--vg-root ro DEFAULT quiet splash ivrs_ioapic[32]=00:14.0
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to eoan on 2019-10-13 (1 days ago)
  dmi.bios.date: 12/07/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0UET68W (1.48 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KVCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0UET68W(1.48):bd12/07/2018:svnLENOVO:pn20KVCTO1WW:pvrThinkPadE585:rvnLENOVO:rn20KVCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E585
  dmi.product.name: 20KVCTO1WW
  dmi.product.sku: LENOVO_MT_20KV_BU_Think_FM_ThinkPad E585
  dmi.product.version: ThinkPad E585
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848108/+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 1325931] Re: [upstream] Can't select non-standard paper sizes for Printing

** Summary changed:

- Can't select non-standard paper sizes for Printing
+ [upstream] Can't select non-standard paper sizes for Printing

-- 
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/1325931

Title:
  [upstream] Can't select non-standard paper sizes for Printing

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Problem description: 
  I was trying to print a small compliments slip on a card that was 140mm x 
100mm.

  I set the page size under Format -> Page -> Size to user defined, and
  then entered the width of 14.00cm and height of 10.00cm correctly.

  However, when I came to try to print it, it would not print correctly.
  The print dialog box showed the dimensions of A6 (140mm x 105mm) and I
  couldn't find any way to change this. I tried to print it anyway, but
  it came out wrong.

  To prove that the problem is in LibreOffice and probably not related
  to the driver, I exported the file to a PDF, and was able to print it
  by setting up a Custom Paper size in the printer settings dialog - an
  option which LibreOffice doesn't seem to have.

  Steps to reproduce:
  1. Create a new Document
  2. From the menu, do Format -> Page
  3. From the Format dropdown, select User
  4. Enter a size that is not a standard paper size
  5. Click OK
  6. Attempt to print the document

  Current behavior:
  No matter what combinations of options I tried, I was unable to change the 
Printer paper size to the correct size.
  If I go ahead and click Print, the output is wrong (output not aligned 
correctly on the page).

  Expected behavior:
  Paper size could be set by the selected Page size, or provide some way to 
change the printer paper size.
  Operating System: Ubuntu
  Version: 4.2.3.3 release

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libreoffice 1:4.2.3~rc3-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
  Uname: Linux 3.13.0-27-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jun  3 12:04:40 2014
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to trusty on 2014-05-07 (26 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1325931/+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 1232872] Re: [upstream] NFS / lock problem with LibreOffice wth 13.04

** Summary changed:

- NFS / lock problem with LibreOffice wth 13.04
+ [upstream] NFS / lock problem with LibreOffice wth 13.04

-- 
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/1232872

Title:
  [upstream] NFS / lock problem with LibreOffice wth 13.04

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Hi all,

  I have a problem very similar to what is exposed in question #234375.

  Since I upgraded to Ubuntu 13.04 (host x86_64), I have trouble accessing 
documents via NFS with LibreOffice.
  The slash screen display for about 30s, then there is a popup warning saying 
that another user has opened the file, and offering to open a copy, open as 
readonly or cancel.

  The point is, no other user has opened that file (being the only user
  on my personal PC, but storing my documents on NAS).

  So I tried the suggestion about adding "noauto" in /etc/fstab and
  changing /etc/rc.local, with no luck.

  But the modification of /usr/lib/libreoffice/program/soffice:
  ##

  # 
  STAR_PROFILE_LOCKING_DISABLED=1
  export STAR_PROFILE_LOCKING_DISABLED
  #

  # file locking now enabled by default
  #SAL_ENABLE_FILE_LOCKING=1 # <<- if set to 0 ; same trouble ...
  #export SAL_ENABLE_FILE_LOCKING
  ###

  (That is, uncomment the first 2 lines, and commenting the other 2)
  This works OK.

  If this is the official way of fixing things, then I guess LibreOffice
  deserves an update on Ubuntu at least.

  Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1232872/+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 1619814] Re: [upstream] Can't paste contents from clipboard copied from LibreOffice once it is closed

** Summary changed:

- Can't paste contents from clipboard copied from LibreOffice once it is closed
+ [upstream] Can't paste contents from clipboard copied from LibreOffice once 
it is closed

-- 
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/1619814

Title:
  [upstream] Can't paste contents from clipboard copied from LibreOffice
  once it is closed

Status in LibreOffice:
  Unknown
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  I have found recently that if I copy some text for example from any of
  the LibreOffice programs, that if I then paste it into another program
  outside of that suite then it pastes it fine. But if I then close
  LibreOffice then trying to paste the text does nothing, so closing
  LibreOffice also gets rid of the contents in the clipboard from it
  which is not ideal.

  I am running Ubuntu GNOME 16.04.1 with GNOME 3.20 and LibreOffice
  version "5.1.4.2 10m0(Build:2)".

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1619814/+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 1736176] Re: [upstream] Can't jump between cells when non-english input layout is active

** Summary changed:

- Can't jump between cells when non-english input layout is active
+ [upstream] Can't jump between cells when non-english input layout is active

-- 
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/1736176

Title:
  [upstream] Can't jump between cells when non-english input layout is
  active

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Can't jump between LibreOffice Calc cells by arrow keys when non-
  english input layout is active. It's because Ubuntu is using Scroll
  Lock indicator (LED) to show state of layout switch, but in
  LibreOffice Scroll Lock state is used to switch between page's
  scrolling and jumping on cells.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libreoffice 1:5.4.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec  4 17:25:29 2017
  InstallationDate: Installed on 2017-10-19 (45 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=uk_UA.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1736176/+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 1738251] Re: [upstream] Missing Data when Copying from Clipboard to Writer

** Summary changed:

- Missing Data when Copying from Clipboard to Writer
+ [upstream] Missing Data when Copying from Clipboard to Writer

-- 
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/1738251

Title:
  [upstream] Missing Data when Copying from Clipboard to Writer

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  I have copied and pasted the webpage 
'https://bugs.launchpad.net/ubuntu/+source/msttcorefonts/+bug/1607535' into 
LibreOffice, so as to be able to print and read it. The resulting page is 
incomplete. Thus, for example, at [Workaround 1], where the the following 
command line is specified:
    $ wget http://downloads.sourceforge.net/corefonts/
    {andale32.exe,arial32.exe,arialb32.exe,comic32.exe,courie32.exe,
    georgi32.exe,impact32.exe,times32.exe,trebuc32.exe,verdan32.exe,
    webdin32.exe}
  only the following text appears:
    $ wget http://
    {
    georgi32.
    webdin32.exe}
  The HTML code for that text is:
$ wget http://downloads.sourceforge.net/corefonts/;>http://downloads.sourceforge.net/corefonts/
{andale32.exe,arial32.exe,arialb32.exe,comic32.exe,courie32.exe,
georgi32.exe,impact32.exe,times32.exe,trebuc32.exe,verdan32.exe,
webdin32.exe}
  The problem is triggered by the  tag. Where one of these occurs in the 
HTML, all subsequent text is omitted until either a  or a  tag is 
reached (and of course there may be others).
  As there are 956  tags in this document, much of the text is missing 
after pasting. If the all the  tags are removed from the page, copying 
and pasting works fine.
  I shall be grateful for help with the problem, as it means that that with 
LibreOffice copying and pasting is unreliable.

  Ubuntu Mate 16.04.3
  lsb-release: 9.20160110ubuntu0.2
  LibreOffice Writer: libreoffice-writer 1:5.1.6-rc20ubuntu1-xenial2

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1738251/+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 1793130] Re: [upstream] Wrong alignment while typing RTL text in Calc cell

** Summary changed:

- Wrong alignment while typing RTL text in Calc cell
+ [upstream] Wrong alignment while typing RTL text in Calc cell

-- 
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/1793130

Title:
  [upstream] Wrong alignment while typing RTL text in Calc cell

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Calc normally aligns text cells to the right or to the left based on
  the directionality of the first character of the cell (left-alignment
  with English and right-alignment with Arabic). Unfortunately, this
  assignment happens only when the user has finished typing and pressed
  Enter. While typing, all text cells are aligned to the left, while for
  example numbers are automatically aligned to the right even in the
  typing phase. The same thing happens even when I’m modifying a text
  cell which was already automatically aligned to the right: as soon as
  I double-click on the cell, the text jumps to the left edge of the
  cell, and then I need to visually relocate the exact place I wanted to
  modify.

  As a user, I would expect cells with an RTL character in the beginning
  to get aligned to the right already while the user is typing. This is
  what happens with many other programs, too, such as Firefox when
  filling out an HTML form. See the attached screenshot from Calc for an
  example.

  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

Installed: 1:6.0.3-0ubuntu1
Candidate: 1:6.0.3-0ubuntu1
Version table:
   *** 1:6.0.3-0ubuntu1 500
  500 http://mr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-calc 1:6.0.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 18 11:44:23 2018
  InstallationDate: Installed on 2017-02-13 (582 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to bionic on 2018-05-31 (109 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1793130/+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 1796698] Re: [upstream] Assigns style to columns it cannot handle in .xlsx files

** Summary changed:

- Assigns style to columns it cannot handle in .xlsx files
+ [upstream] Assigns style to columns it cannot handle in .xlsx files

-- 
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/1796698

Title:
  [upstream] Assigns style to columns it cannot handle in .xlsx files

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1) Open LibreOffice Calc
  2) File > New > Spreadsheet
  3) File > Save As, choose name vanilla.xlsx > Save

  Extract contents of vanilla.xlsx file to some directory. In the 
xl/worksheets/sheet1.xml file in the node worksheet/cols/ you'll find node
  

  LibreOffice Calc can handle only 1024 columns, but style says it apply
  to 1025. If such .xlsx document is processed with PhpOffice and single
  cell value is written,  nodes gets expanded, including for . This column cannot be processed by
  LibreOffice Calc and produces warnings that some information is lost.

  Value should be at most 1024 (or whatever limit is in 6.1).

  File produced on my copy of libreoffice is attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-calc 1:6.0.6-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct  8 18:08:43 2018
  InstallationDate: Installed on 2018-04-11 (180 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1796698/+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 1831624] Re: [upstream] ibus-cangjie in libreoffice cannot type Chinese character at end of line

** Summary changed:

- ibus-cangjie in libreoffice cannot type Chinese character at end of line
+ [upstream] ibus-cangjie in libreoffice cannot type Chinese character at end 
of line

-- 
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/1831624

Title:
  [upstream] ibus-cangjie in libreoffice cannot type Chinese character
  at end of line

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  I am using LibreOffice Version: 6.0.7.3, in particular I am using
  LibreOffice Writer.

  I am using ibus-cangjie to input Chinese.

  I cannot input any Chinese characters when I reach the end of a line
  on the screen.

  The expected behavior is that the typed Chinese character simply
  spills over to the next line and I can continue to type without a
  problem.

  If I reach the end of the line with half a space (of full-sized
  Chinese character) available, then I could insert a punctuation mark
  like 。 or 、 even if I use cangjie codes to input them (and then I can
  continue normally).

  if I reach the end of the line with no space available, then I cannot
  insert 。 or 、 when I use cangjie codes to input them (in the ibus-
  cangjie standard input table, 、 = XI)

  In neither case I can type a Chinese character like 日, all the typed
  characters simply disappears from the input queue and is not typed at
  all.  Note that as I type I can see that the candidate Chinese
  characters according to the cangjie codes I input, they just don't get
  sent to the application.

  when I am at the end of the line, I can type as many spaces as I want
  and the problem of being unable to type a Chinese character persists.

  Finally, the bug only triggers when I am at the end of text; if I am
  inserting in the middle of text, even if I am at the linebreak, I can
  type normally and naturally.

  the attached screenshot shows where I am getting my cursor stuck.

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1831624/+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 1793126] Re: [upstream] Automatic cell alignment in Calc breaks with bidi-neutral characters

** Summary changed:

- Automatic cell alignment in Calc breaks with bidi-neutral characters
+ [upstream] Automatic cell alignment in Calc breaks with bidi-neutral 
characters

-- 
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/1793126

Title:
  [upstream] Automatic cell alignment in Calc breaks with bidi-neutral
  characters

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Calc seems to assign the alignment of any particular text cell based
  on the contents of the cell: if the first character is a LTR
  character, the cell is aligned to the left, and if the first character
  is RTL, the cell is aligned to the right. This is desirable behavior
  but it breaks when the first character is neutral, i.e. a character
  that behaves as RTL in an RTL context and as LTR in a LTR context.

  See the attached screenshot where cell A1 "abc" is automatically
  aligned to the left and cell A2 "ابت" to the right. When I surround
  these strings with parentheses, which are bidi-neutral characters, in
  A3 and A4, both are aligned to the left. For some reason, even font
  metrics break with this assignment, as the last character of the
  Arabic string overlaps visually with the closing parenthesis (I think
  this is a separate issue and I’ll file it as such).

  In column C, I have copied the contents of column A but changed the
  directionality setting of cell C4 manually to RTL through Format Cells
  > Text direction. Here the cell is properly aligned to the right and
  the closing parenthesis does not overlap with the last character of
  the string.

  According to the Unicode standard, neutral characters should not
  affect directionality, and that’s what I would expect as a user, too.
  I think the best solution would be for Calc to skip all neutral
  characters in the beginning of the string and just consider the first
  strong character for cell alignment. Even better, Calc could use this
  heuristics to assign full text directionality for the cell, not just
  change alignment. Right now, if you start the cell with an RTL
  character followed by a LTR inset and then continue with RTL again,
  the substrings are ordered as in a LTR context ("FIRST second THIRD"),
  not as in true RTL ("THIRD second FIRST").

  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

Installed: 1:6.0.3-0ubuntu1
Candidate: 1:6.0.3-0ubuntu1
Version table:
   *** 1:6.0.3-0ubuntu1 500
  500 http://mr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-calc 1:6.0.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 18 11:26:18 2018
  InstallationDate: Installed on 2017-02-13 (582 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to bionic on 2018-05-31 (109 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1793126/+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 1796187] Re: [upstream] Writer hangs for over 20 minutes loading a 3MB, 450-page DOCX

** Summary changed:

- Writer hangs for over 20 minutes loading a 3MB, 450-page DOCX
+ [upstream] Writer hangs for over 20 minutes loading a 3MB, 450-page DOCX

-- 
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/1796187

Title:
  [upstream] Writer hangs for over 20 minutes loading a 3MB, 450-page
  DOCX

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Trying to load the attached DOCX results in a hang.  I force-quit
  after 20 minutes.  The DOCX was created in MS Word (2013 I think), and
  is about 450 pages, thousands of footnotes, but no graphics AFAIK.

  I am using the latest package provided by snap. LibreOffice 6.1.2.1.
  Ubuntu 18.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-writer (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct  4 23:50:54 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-06-03 (488 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to bionic on 2018-06-06 (119 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1796187/+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 1192599] Re: writer: zoom fraction changes when clicking on figures

** Bug watch added: Document Foundation Bugzilla #36976
   https://bugs.documentfoundation.org/show_bug.cgi?id=36976

** Changed in: df-libreoffice
   Importance: Medium => Unknown

** Changed in: df-libreoffice
   Status: Invalid => Unknown

** Changed in: df-libreoffice
 Remote watch: Document Foundation Bugzilla #34451 => Document Foundation 
Bugzilla #36976

** Summary changed:

- writer: zoom fraction changes when clicking on figures
+ [upstream] writer: zoom fraction changes when clicking on figures

-- 
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/1192599

Title:
  [upstream] writer: zoom fraction changes when clicking on figures

Status in LibreOffice:
  Unknown
Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  1) lsb_release -rd
  Description:  Ubuntu 13.04
  Release:  13.04

  2) apt-cache policy libreoffice-writer
  libreoffice-writer:
Installed: 1:4.0.2-0ubuntu1
Candidate: 1:4.0.2-0ubuntu1
Version table:
   *** 1:4.0.2-0ubuntu1 0
  500 http://archive.ubuntu.com/ubuntu/ raring/main i386 Packages
  100 /var/lib/dpkg/status

  3) What is expected to happen in Writer via a terminal:
  cd ~/Desktop && wget 
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1192599/+attachment/3707409/+files/lorem_ipsum.odt
 && lowriter --nologo lorem_ipsum.odt

  is when one clicks View -> Zoom -> Fit width and height -> OK click
  the text, then click the picture, the zoom does not change.

  4) What happens instead is it does. All other zoom modes don't exhibit
  this behavior.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: libreoffice 1:3.6.2~rc2-0ubuntu4
  ProcVersionSignature: Ubuntu 3.5.0-34.55-generic 3.5.7.13
  Uname: Linux 3.5.0-34-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu11
  Architecture: amd64
  Date: Wed Jun 19 16:56:17 2013
  InstallationDate: Installed on 2012-11-22 (209 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1192599/+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 1093765] Re: [upstream] switching paragraph style changes character orientation

** Summary changed:

- switching paragraph style changes character orientation
+ [upstream] switching paragraph style changes character orientation

-- 
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/1093765

Title:
  [upstream] switching paragraph style changes character orientation

Status in LibreOffice:
  Unknown
Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  1) lsb_release -rd
  Description:  Ubuntu 13.04
  Release:  13.04

  2) apt-cache policy libreoffice-writer
  libreoffice-writer:
Installed: 1:4.0.2-0ubuntu1
Candidate: 1:4.0.2-0ubuntu1
Version table:
   *** 1:4.0.2-0ubuntu1 0
  500 http://archive.ubuntu.com/ubuntu/ raring/main i386 Packages
  100 /var/lib/dpkg/status

  3) What is expected to happen in Writer via a terminal:
  cd ~/Desktop && wget 
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1093765/+attachment/3688368/+files/test-bug1093765.doc
 && lowriter --nologo test-bug1093765.doc

  is select all -> change combo box Apply Style from Text Body to
  Heading 1 and the text style changes, preserving the character order.

  4) What happens instead is:
  (Example text=) טקסט לדוגמה

  changes to:
  טקסט לדוגמה (=Example text)

  Microsoft Office Professional Plus 2010 Word Version 14.0.6023.1000 (32-bit) 
changes it to:
  =)טקסט לדוגמהExample text(

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: libreoffice-core 1:3.6.2~rc2-0ubuntu4
  ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1
  Uname: Linux 3.5.0-21-generic x86_64
  ApportVersion: 2.6.1-0ubuntu9
  Architecture: amd64
  Date: Wed Dec 26 11:20:42 2012
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  MarkForUpload: True
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to quantal on 2012-10-19 (67 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1093765/+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 1070210] Re: [upstream] Libreoffice always uses "letter" paper

** Summary changed:

- Libreoffice always uses "letter" paper
+ [upstream] Libreoffice always uses "letter" paper

-- 
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/1070210

Title:
  [upstream] Libreoffice always uses "letter" paper

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  For new documents, libreoffice chooses always "letter" paper.  It is
  expected, that documents are in A4 paper, because the locale ist set
  to de_DE.UTF-8.

  LibreOffice settings: 
  Tools --> Options --> Language Settings --> Languages --> Locale stting: 
Default - German (Germany)

  The locale settings are: 
  > locale
  LANG=en_US.UTF-8
  LANGUAGE=
  LC_CTYPE=de_DE.UTF-8
  LC_NUMERIC=de_DE.UTF-8
  LC_TIME=de_DE.UTF-8
  LC_COLLATE=de_DE.UTF-8
  LC_MONETARY=de_DE.UTF-8
  LC_MESSAGES=en_US.UTF-8
  LC_PAPER=de_DE.UTF-8
  LC_NAME=de_DE.UTF-8
  LC_ADDRESS=de_DE.UTF-8
  LC_TELEPHONE=de_DE.UTF-8
  LC_MEASUREMENT=de_DE.UTF-8
  LC_IDENTIFICATION=de_DE.UTF-8
  LC_ALL=

  LibreOffice Version:
  > apt-cache policy libreoffice
  libreoffice:
Installed: 1:3.5.4-0ubuntu1.1
Candidate: 1:3.5.4-0ubuntu1.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1070210/+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 1087739] Re: [upstream] Promoting/demoting items in a bulleted list not working in Impress

** Summary changed:

- Promoting/demoting items in a bulleted list not working in Impress
+ [upstream] Promoting/demoting items in a bulleted list not working in Impress

-- 
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/1087739

Title:
  [upstream] Promoting/demoting items in a bulleted list not working in
  Impress

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  On Ubuntu 12.10 64 bit:

  - create a new empty presentation with Impress
  - create a bulleted list with a few items
  - demote or promote an item by pressing the relative buttons in the toolbar, 
or using the  the keyboard shortcuts (ALT+SHIFT+LEFT, ALT+SHIFT+RIGHT)

  Expected behavior: the item gets promoted or demoted
  What happens instead: nothing, the buttons in the toolbar appear disabled
  --- 
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  DistroRelease: Ubuntu 12.10
  InstallationDate: Installed on 2012-06-13 (177 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328)
  MarkForUpload: True
  Package: libreoffice 1:3.6.2~rc2-0ubuntu4
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7
  Tags:  quantal running-unity
  Uname: Linux 3.5.0-19-generic x86_64
  UpgradeStatus: Upgraded to quantal on 2012-10-30 (38 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1087739/+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 1141034] Re: [upstream] RTL Spreadsheet Insert Cells

** Summary changed:

- RTL Spreadsheet Insert Cells
+ [upstream] RTL Spreadsheet Insert Cells

-- 
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/1141034

Title:
  [upstream] RTL Spreadsheet Insert Cells

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  When using a right-to-left spreadsheet, right clicking and selected
  "insert cells" shows the normal LTR option to shift cells right,
  although when used it actually shifts cells left.

  I believe that shifting cells left is the correct behaviour in this
  case, but the text of the option should be changed to read "shift
  cells left". This was first noticed when using the Hebrew language
  user interface, but the problem is present when using English UI too.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: libreoffice-calc 1:3.5.7-0ubuntu4
  ProcVersionSignature: Ubuntu 3.2.0-38.61-generic 3.2.37
  Uname: Linux 3.2.0-38-generic i686
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: i386
  CheckboxSubmission: ad9a15703e19217cb3448f881e125f6a
  CheckboxSystem: abc83e3988b72e7c3a9b3aa684cb92fd
  Date: Sun Mar  3 00:47:21 2013
  MarkForUpload: True
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to precise on 2012-05-01 (305 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1141034/+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 1126858] Re: Search and replace, with tracked changes on, changing only format of text, causes Writer to hang

Synchronising bug status with upstream.

** Summary changed:

- Search and replace, with tracked changes on, changing only format of text, 
causes Writer to hang
+ [upstream] Search and replace, with tracked changes on, changing only format 
of text, causes Writer to hang

** Bug watch added: Document Foundation Bugzilla #36582
   https://bugs.documentfoundation.org/show_bug.cgi?id=36582

** Changed in: df-libreoffice
 Remote watch: Document Foundation Bugzilla #65056 => Document Foundation 
Bugzilla #36582

-- 
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/1126858

Title:
  [upstream] Search and replace, with tracked changes on, changing only
  format of text, causes Writer to hang

Status in LibreOffice:
  Unknown
Status in libreoffice package in Ubuntu:
  Triaged

Bug description:
  Create new text document with contents "Hello, World".
  Turn on change tracking (under Edit).
  Select Find and Replace (under Edit).
  Put "Hello" (no quotes) in both the find and the replace boxes.
  Click on "More".
  Put cursor in Replace box.
  Click on Format.
  Set it to, say Italic (leave other options empty). Accept.

  And now, for the fatal part: Click "Replace all".
  If you just replace one, you'll see why the latter fails. The replacement 
value gets inserted beofre the original, so then it continues on and sees the 
original again... ad infinitum.

  
  What should happen: If it just put its position after the original text when 
searching and replacing, it wouldn't have this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 3.5.0-23.35-generic 3.5.7.2
  Uname: Linux 3.5.0-23-generic x86_64
  ApportVersion: 2.6.1-0ubuntu10
  Architecture: amd64
  Date: Fri Feb 15 21:37:14 2013
  InstallationDate: Installed on 2012-12-13 (65 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1126858/+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 885085] Re: [upstream] Formula gets in a way while editing and prevents selection of the adjacent cell.

** Summary changed:

- Formula gets in a way while editing and prevents selection of the adjacent 
cell.
+ [upstream] Formula gets in a way while editing and prevents selection of the 
adjacent cell.

-- 
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/885085

Title:
  [upstream] Formula gets in a way while editing and prevents selection
  of the adjacent cell.

Status in LibreOffice:
  Unknown
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Problem description: I often cannot select the adjacent cell to add it to the
  formula when the last one is too long. It depends on the formatting but I
  didn't find the formatting that will constrain the formula within it's cell.

  Steps to reproduce:
  See the attached screenshot. I cannot add B1 cell to the formula using just a
  pointer.

  Expected behavior:
  The formula should leave cell boundaries only when the formula bar is not
  visible.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: libreoffice-calc 1:3.4.3-3ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic-pae 3.0.4
  Uname: Linux 3.0.0-12-generic-pae i686
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu3
  Architecture: i386
  Date: Wed Nov  2 08:41:20 2011
  ProcEnviron:
   LANGUAGE=uk:en
   PATH=(custom, no user)
   LANG=uk_UA.UTF-8
   LC_MESSAGES=uk_UA.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/885085/+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 1417534] Re: [upstream] Calc doesn't merge cells when pasting merged content from HTML

** Summary changed:

- Calc doesn't merge cells when pasting merged content from HTML
+ [upstream] Calc doesn't merge cells when pasting merged content from HTML

-- 
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/1417534

Title:
  [upstream] Calc doesn't merge cells when pasting merged content from
  HTML

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Triaged

Bug description:
  1)  lsb_release -rd
  Description:  Ubuntu 15.10
  Release:  15.10

  2) apt-cache policy libreoffice-calc
  libreoffice-calc:
Installed: 1:5.0.2-0ubuntu1
Candidate: 1:5.0.2-0ubuntu1
Version table:
   *** 1:5.0.2-0ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
  100 /var/lib/dpkg/status

  3) What is expected to happen is when one opens the following URL via Firefox 
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1417534/+attachment/438/+files/table_with_merged_cells_in_first_row.html
 > highlights all content in the top row > paste into Calc then A1 contains:
  Cell1

  and B1 and C1 are merged together containing:
  Cell2 + 3

  as it does in Excel 2013.

  4) What happens instead is that while cell A1 contains Cell1, B1 and
  C1 are not merged, and B1 contains Cell2 + 3.

  Originally reported on LO 4.2, and reported to not exist in LO 3.5.

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1417534/+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 1183368] Re: [upstream] EDITING: Find by format doesn't work with non-integer font sizes

** Summary changed:

-  EDITING: Find by format doesn't work with non-integer font sizes
+ [upstream] EDITING: Find by format doesn't work with non-integer font sizes

-- 
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/1183368

Title:
  [upstream] EDITING: Find by format doesn't work with non-integer font
  sizes

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  1) lsb_release -rd
  Description:  Ubuntu 13.04
  Release:  13.04

  2) apt-cache policy libreoffice-writer
  libreoffice-writer:
Installed: 1:4.0.2-0ubuntu1
Candidate: 1:4.0.2-0ubuntu1
Version table:
   *** 1:4.0.2-0ubuntu1 0
  500 http://archive.ubuntu.com/ubuntu/ raring/main i386 Packages
  100 /var/lib/dpkg/status

  3) What is expected to happen in Writer via a terminal:
  cd ~/Desktop && wget 
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1183368/+attachment/3691990/+files/example.odt
 && lowriter --nologo example.odt

  Ctrl+H -> click dropdown box Search for -> button More Options ->
  button Format... -> in the Text Format(Search) window tab Font in text
  box Size type 11.5 -> button OK and underneath the Search dropdown box
  it notes 11.5, as it does in Microsoft Office Professional Plus 2010
  Word Version 14.0.6023.1000 (32-bit).

  4) What happens instead is it displays 12. However, it still
  successfully searches and finds 11.5 so this is a cosmetic UI issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: libreoffice-writer 1:4.0.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-21.32-generic 3.8.8
  Uname: Linux 3.8.0-21-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Thu May 23 15:01:20 2013
  MarkForUpload: True
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to raring on 2013-04-30 (23 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1183368/+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 1598938] Re: soffice.bin crashed with SIGSEGV in IsVertical()

Synchronising bug status with upstream.

** Changed in: libreoffice (Ubuntu)
   Status: Triaged => Fix Released

-- 
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/1598938

Title:
  soffice.bin crashed with SIGSEGV in IsVertical()

Status in LibreOffice:
  Unknown
Status in libreoffice package in Ubuntu:
  Fix Released

Bug description:
  LibreOffice crashes while I was trying to edit a document; the
  document is a page copy-pasted from Firefox which has quite a big
  amount of nested tables.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: libreoffice-core 1:5.1.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Mon Jul  4 23:29:38 2016
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationDate: Installed on 2014-08-23 (681 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140823)
  ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --writer 
file:///tmp/mozilla_dmitry0/F.NAKV+BB.RU.LTU.dot --splash-pipe=5
  ProcEnviron:
   LANGUAGE=ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f58cd333730 
<_ZNK11SwTableLine16hasSoftPageBreakEv+496>:cmpq   $0x0,0x50(%rax)
   PC (0x7f58cd333730) ok
   source "$0x0" ok
   destination "0x50(%rax)" (0x0050) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: libreoffice
  StacktraceTop:
   SwTableLine::hasSoftPageBreak() const () at 
/usr/lib/libreoffice/program/../program/libswlo.so
   () at /usr/lib/libreoffice/program/../program/libswlo.so
   () at /usr/lib/libreoffice/program/../program/libswlo.so
   () at /usr/lib/libreoffice/program/../program/libswlo.so
   () at /usr/lib/libreoffice/program/../program/libswlo.so
  Title: soffice.bin crashed with SIGSEGV in SwTableLine::hasSoftPageBreak()
  UpgradeStatus: Upgraded to xenial on 2016-04-28 (67 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1598938/+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 1772430] Re: [upstream] Proportional line spacing under 100 % makes first line too low in LibreOffice Writer

** Summary changed:

- Proportional line spacing under 100 % makes first line too low in LibreOffice 
Writer
+ [upstream] Proportional line spacing under 100 % makes first line too low in 
LibreOffice Writer

-- 
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/1772430

Title:
  [upstream] Proportional line spacing under 100 % makes first line too
  low in LibreOffice Writer

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Using proportional line spacing with less than 100 % makes the first
  line of each paragraph and each page considerably lower than all the
  other lines.

  This problem is an issue particularly with fonts designed for Arabic,
  where the default line spacing is very big so as to allow for space
  for optional vowel marks below and above the line. If these marks are
  not used, the space between the lines is often too big. If I change
  line spacing to proportional 80 %, most of the lines look fine but the
  first line of each paragraph and of each page (even without a
  paragraph break) gets crammed into the second line. As a user, I would
  rather expect the first line to have the same visual height as all the
  other lines. See the attached document and screenshots using Noto
  Naskh Arabic and 80 % line spacing.

  Description:  Ubuntu 17.10
  Release:  17.10

  libreoffice-writer:
Installed: 1:5.4.6-0ubuntu0.17.10.1
Candidate: 1:5.4.6-0ubuntu0.17.10.1
Version table:
   *** 1:5.4.6-0ubuntu0.17.10.1 500
  500 http://mr.archive.ubuntu.com/ubuntu artful-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:5.4.5-0ubuntu0.17.10.5 500
  500 http://security.ubuntu.com/ubuntu artful-security/main amd64 
Packages
   1:5.4.1-0ubuntu1 500
  500 http://mr.archive.ubuntu.com/ubuntu artful/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libreoffice-writer 1:5.4.6-0ubuntu0.17.10.1
  ProcVersionSignature: Ubuntu 4.13.0-41.46-generic 4.13.16
  Uname: Linux 4.13.0-41-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 21 14:50:01 2018
  InstallationDate: Installed on 2017-02-13 (462 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to artful on 2017-11-05 (196 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1772430/+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 1774244] Re: [upstream] Rotated Arabic text is displaced in PDF when substitute glyphs are used