[Desktop-packages] [Bug 1297051] [NEW] gnome-terminal doesn't recognise C1 controls

2014-03-24 Thread boon
Public bug reported:

gnome-terminal seems not to recognise the C1 control characters.

The particular character that is a problem for me is CSI. However there
may be a generic issue with non-support of this whole range of
characters.

This range of characters should only be recognised when the encoding is
a character set that is defined to include the C1 control characters
but, at a quick look, that is all of the ISO-8859-x character sets and
Unicode. (C1 control characters require encoding as a 2 byte sequence
when the encoding is UTF-8. As unlikely as this may be to occur in
practice, UTF-8 is not inconsistent with C1 control characters.)

Part of the motivation for raising this bug report is that PuTTY seems
to have declined in reliability recently and so I looked at why I am
using PuTTY as opposed to gnome-terminal. Correct support of C1 control
characters is one reason. This works in PuTTY. It does not appear to
work in gnome-terminal. Perhaps resources would be better spent making
gnome-terminal work as well as PuTTY does, rather than attempting to get
PuTTY fixed.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: gnome-terminal 3.6.1-0ubuntu6
ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4
Uname: Linux 3.11.0-18-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
Date: Tue Mar 25 11:08:00 2014
InstallationDate: Installed on 2011-10-25 (881 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
MarkForUpload: True
SourcePackage: gnome-terminal
UpgradeStatus: Upgraded to saucy on 2013-11-08 (136 days ago)

** Affects: gnome-terminal (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug saucy

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

Title:
  gnome-terminal doesn't recognise C1 controls

Status in “gnome-terminal” package in Ubuntu:
  New

Bug description:
  gnome-terminal seems not to recognise the C1 control characters.

  The particular character that is a problem for me is CSI. However
  there may be a generic issue with non-support of this whole range of
  characters.

  This range of characters should only be recognised when the encoding
  is a character set that is defined to include the C1 control
  characters but, at a quick look, that is all of the ISO-8859-x
  character sets and Unicode. (C1 control characters require encoding as
  a 2 byte sequence when the encoding is UTF-8. As unlikely as this may
  be to occur in practice, UTF-8 is not inconsistent with C1 control
  characters.)

  Part of the motivation for raising this bug report is that PuTTY seems
  to have declined in reliability recently and so I looked at why I am
  using PuTTY as opposed to gnome-terminal. Correct support of C1
  control characters is one reason. This works in PuTTY. It does not
  appear to work in gnome-terminal. Perhaps resources would be better
  spent making gnome-terminal work as well as PuTTY does, rather than
  attempting to get PuTTY fixed.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-terminal 3.6.1-0ubuntu6
  ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4
  Uname: Linux 3.11.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Tue Mar 25 11:08:00 2014
  InstallationDate: Installed on 2011-10-25 (881 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MarkForUpload: True
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to saucy on 2013-11-08 (136 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1297051/+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 1271839] Re: ibus-ui-gtk3 big memory leak

2014-03-04 Thread boon
I too am experiencing this problem (twice so far since upgrading to
13.10 and I don't think I had the problem before that).

The system becomes fairly unresponsive e.g. can't unminimise windows
from the launch bar and it may not even be possible to minimise windows.

I can start System Monitor and it shows that ibus-ui-gtk3 has taken 8GB
of memory (half what I have) and growing quickly. I have not let it get
beyond that. I think that logging out clears the problem.

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

Title:
  ibus-ui-gtk3 big memory leak

Status in “ibus” package in Ubuntu:
  Incomplete

Bug description:
  ubuntu 13.10 64bit
  2gb of memory leak

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1271839/+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 1271839] Re: ibus-ui-gtk3 big memory leak

2014-03-04 Thread boon
PS I don't think this problem should be allowed to expire because of its
"incomplete" status. It seems a fairly serious problem to me.

If you want valgrind information, you are going to have to provide
additional information about how this process gets started - if it is
even possible to use valgrind in this case.

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

Title:
  ibus-ui-gtk3 big memory leak

Status in “ibus” package in Ubuntu:
  Incomplete

Bug description:
  ubuntu 13.10 64bit
  2gb of memory leak

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1271839/+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 1773114] Re: Cannot copy file using 'cp' on a gvfs mount

2019-11-25 Thread boon
As of 18.04 and still as at 19.10, this is all over the place. Errors
left, right and centre.

nautilus gives "Software caused connection abort" copying a file (but
pressing F5 to refresh shows that the copy seemingly worked).

gedit fails intermittently with the same error (possibly only on larger
files, 32KB? not that 32KB is large).

cp gives the error as reported initially above.

I was copying using cp from one gio mount (smb) to another (sftp). Even
gio copy was not a workaround. The only viable workaround that I found
was to gio copy from the smb location to ~ and then copy from ~ to the
sftp location. I was lucky that the file was not very big.

(LibreOffice has its own problems with this setup.)

Virtualisation of file systems is good functionality and I use it a lot
but from 18.04 until now, taking the system as a whole, it has been
badly broken.

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

Title:
  Cannot copy file using 'cp' on a gvfs mount

Status in gvfs package in Ubuntu:
  Confirmed

Bug description:
  On Ubuntu 18.04, I can't anymore copy a file using the 'cp' command on
  a gvfs smb mount.

  For example, If I try to copy the file test.odp on a SMB shared
  folder, like this:

  cp -v test.odp /run/user/1000/gvfs/smb-
  share:domain=X,server=x,share=xxx,user=x/

  I get the following error:

  cp: cannot fstat '/run/user/1000/gvfs/smb-
  share:domain=X,server=x,share=xxx,user=x//test.odp': Invalid argument

  A file 'test.odp' is created, but with size 0.

  I can delete any file on the shared folder using the 'rm' command.

  If I copy the file using the command 'gio copy', then it works as
  expected.

  This used to work in Ubuntu 16.04.

  Of course, I don't know if the problem is in the gvfs package or in
  some underlying component...

  System: Ubuntu 18.04 LTS (Bionic Beaver) 64-bit
  Kernel: 4.15.0-22-generic x86_64
  Package: gvfs 1.36.1-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1773114/+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 1773114] Re: Cannot copy file using 'cp' on a gvfs mount

2019-12-13 Thread boon
>Could you maybe report the issue upstream

Done.

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

Title:
  Cannot copy file using 'cp' on a gvfs mount

Status in gvfs package in Ubuntu:
  Confirmed

Bug description:
  On Ubuntu 18.04, I can't anymore copy a file using the 'cp' command on
  a gvfs smb mount.

  For example, If I try to copy the file test.odp on a SMB shared
  folder, like this:

  cp -v test.odp /run/user/1000/gvfs/smb-
  share:domain=X,server=x,share=xxx,user=x/

  I get the following error:

  cp: cannot fstat '/run/user/1000/gvfs/smb-
  share:domain=X,server=x,share=xxx,user=x//test.odp': Invalid argument

  A file 'test.odp' is created, but with size 0.

  I can delete any file on the shared folder using the 'rm' command.

  If I copy the file using the command 'gio copy', then it works as
  expected.

  This used to work in Ubuntu 16.04.

  Of course, I don't know if the problem is in the gvfs package or in
  some underlying component...

  System: Ubuntu 18.04 LTS (Bionic Beaver) 64-bit
  Kernel: 4.15.0-22-generic x86_64
  Package: gvfs 1.36.1-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1773114/+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 1434986] Re: Not working network connection after boot

2016-06-07 Thread boon
I think I am experiencing the same issue.

This is a brand new desktop PC with 16.04 LTS installed from scratch
i.e. not an upgrade from a previous version.

This is wired ethernet (GbE) i.e. not WiFi.

Immediately after a boot, the user logs in and attempts to access a
computer on the local network (so no possibility of internet problems
and most likely no possibility of DNS problems). The attempt to use the
network fails.

ifconfig appears to show everything normal - ethernet is UP and an IP
address is assigned. Icon at top right of screen appears to show
everything normal (up-arrow-down-arrow icon is present). (IPv4 has an IP
address assigned manually but the same malfunction was occurred when,
initially, it was using DHCP, I think.)

ping of a host on the local network fails.

Wait about 25 seconds though and suddenly it's working.

This is not good user interface because the user has no way of seeing
when the network starts to work. It's not a good user experience either
as the computer is working significantly before the network is usable.

syslog from boot doesn't show anything obviously wrong - NetworkManager
sees the ethernet and appears to bring it up - but then about a minute
after the first message of the boot I see that NetworkManager reports
that the link is disconnected and then connected.

Don't know whether it matters but both IPv4 and IPv6 are in use. IPv6
uses DHCP. Once all the weirdness has finished, both IPv4 and IPv6 work
correctly.

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

Title:
  Not working network connection after boot

Status in NetworkManager:
  Expired
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Directly after boot the network connections are not working. I am
  connected and have an IP address, but I cannot establish a connection
  with any Internet server.

  I have the impression it is related to thee DNS lookup, which waits
  forever for a result.

  Cycling the connection (disconnect->reconnect) seems to fix the
  problem for some time.

  I am reporting this against network-manager, but I am not sure if it is 
directly in network manager or if it is systemd related.
  With 14.10 everything worked perfectly.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu11
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Mar 22 12:38:26 2015
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-01-30 (50 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  IpRoute:
   default via 192.168.1.1 dev eth0  proto static  metric 1024 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.26 
   192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.29
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (3 days ago)
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2015-02-16T00:14:50.662693
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION CON-UUID  CON-PATH   

   eth0ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Kabelnetzwerkverbindung 1  4a581685-6002-4401-a993-49aa649667eb  
/org/freedesktop/NetworkManager/ActiveConnection/4 
   wlan0   wifi  connected  /org/freedesktop/NetworkManager/Devices/1  
4A616E7320574C414E f45aa3a7-fb44-41b7-a02a-ea9720d79414  
/org/freedesktop/NetworkManager/ActiveConnection/3 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/0  --   
  ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1434986/+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 1486059] [NEW] fglrx-updates-core 2:15.200-0ubuntu4: fglrx-updates-core kernel module failed to build

2015-08-18 Thread Boon Hian Tek
Public bug reported:

Not sure what to report. This was generated by an automated task.

ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: fglrx-updates-core 2:15.200-0ubuntu4
ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
Uname: Linux 3.19.0-25-generic x86_64
NonfreeKernelModules: fglrx
.tmp.unity.support.test.0:
 
ApportVersion: 2.17.2-0ubuntu1.2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
DKMSKernelVersion: 3.19.0-26-generic
Date: Tue Aug 18 22:02:50 2015
DistUpgraded: Fresh install
DistroCodename: vivid
DistroVariant: ubuntu
DkmsStatus:
 fglrx-updates-core, 15.200, 3.19.0-23-generic, x86_64: installed
 fglrx-updates-core, 15.200, 3.19.0-25-generic, x86_64: installed
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Tahiti XT [Radeon HD 7970/8970 OEM / R9 
280X] [1002:6798] (prog-if 00 [VGA controller])
   Subsystem: PC Partner Limited / Sapphire Technology Device [174b:3001]
InstallationDate: Installed on 2015-07-13 (35 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
PackageVersion: 2:15.200-0ubuntu4
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-25-generic 
root=UUID=4372c20c-565b-4d1d-8866-1ae830908230 ro nomdmonddf nomdmonisw
RelatedPackageVersions:
 dpkg 1.17.25ubuntu1
 apt  1.0.9.7ubuntu4.1
SourcePackage: fglrx-installer-updates
Title: fglrx-updates-core 2:15.200-0ubuntu4: fglrx-updates-core kernel module 
failed to build
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/23/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.30
dmi.board.name: Z97 Extreme4
dmi.board.vendor: ASRock
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.:bvrP1.30:bd05/23/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
version.fglrx-installer: fglrx-installer N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.60-2
version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
xserver.bootTime: Tue Aug 18 21:52:52 2015
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputSleep Button KEYBOARD, id 8
 inputASUS ASUS Strix Tactic Pro Gaming Keyboard KEYBOARD, id 9
 inputHID 04b3:310dMOUSE, id 10
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.17.1-0ubuntu3
xserver.video_driver: fglrx

** Affects: fglrx-installer-updates (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package ubuntu vivid

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

Title:
  fglrx-updates-core 2:15.200-0ubuntu4: fglrx-updates-core kernel module
  failed to build

Status in fglrx-installer-updates package in Ubuntu:
  New

Bug description:
  Not sure what to report. This was generated by an automated task.

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: fglrx-updates-core 2:15.200-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-25-generic x86_64
  NonfreeKernelModules: fglrx
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.17.2-0ubuntu1.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  DKMSKernelVersion: 3.19.0-26-generic
  Date: Tue Aug 18 22:02:50 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  DkmsStatus:
   fglrx-updates-core, 15.200, 3.19.0-23-generic, x86_64: installed
   fglrx-updates-core, 15.200, 3.19.0-25-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Tahiti XT [Radeon HD 7970/8970 OEM / 
R9 280X] [1002:6798] (prog-if 00 [VGA controller])
 Subsyste