[Desktop-packages] [Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap

[Romano Giannetti]

Still here in 22.04 LTS; the workaround I use is the last one suggested
in https://askubuntu.com/a/1428798/16395 (WARNING; that will allow
evince to launch *any* snap in your system. But otherwise, evince is
severely limited...)

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

Title:
  Clicking a hyperlink in a PDF fails to open it if the default browser
  is a snap

Status in apparmor package in Ubuntu:
  Confirmed
Status in evince package in Ubuntu:
  Triaged
Status in apparmor source package in Jammy:
  Confirmed
Status in evince source package in Jammy:
  Confirmed
Status in evince package in Debian:
  New

Bug description:
  [Impact]

   * Users cannot open a hyperlink in a PDF opened with evince when the default 
browser is a snap.
   * The fix creates a snap_browsers abstraction on AppArmor which can be used 
in a transition for when the browser is executed. The snap_browsers abstraction 
provides the minimal amount of permissions required to execute a browser 
provided through snaps. This is a workaround since AppArmor currently does not 
provide mediation/filtering on enhanced environment variables.

  [Test Plan]

   * Make sure the default browser is provided through the snap store.
   * Open a PDF that contains a hyperlink using evince and click on the URL.
   * The browser should open the requested URL. 

  [Where problems could occur]

   * If the browser or snap core update to have new requirements for
  opening a browser, then the current policy could become obsolete and
  will need to be updated again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+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 381017]

[Romano Giannetti]

I have Manjaro Linux with TB 102, and the problem is still here. When I
do drag-and-drop to a Nemo folder I got the icon copied, and when going
to Nautilus I still have "Drag and drop not supported", "an invalid drag
type was used".

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

Title:
  Cannot drag attachment from mail attachment pane to desktop

Status in One Hundred Papercuts:
  Triaged
Status in SeaMonkey:
  Confirmed
Status in Mozilla Thunderbird:
  Confirmed
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 9.04
  Gnome Desktop 2.26.1
  Thunderbird 2.0.0.21

  This is regression introduced  in Jaunty as it works in Intrepid.
  Dragging an attachment from the attachment pane to the desktop give
  the following error:

  ==
  Error while copying
  There was an error getting information about "fetch>UID>.voicemail>1784".

  The specified location is not supported
  ==

  Mail account is IMAP. This error was shown to seb128 and asac. The
  expected behavior is that the file is copied to the destination onto
  which it is dragged.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/381017/+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 381017]

[Romano Giannetti]

In version 78.7.1 the behavior is better: still not working, but it raises an 
error instead of copying an unusable link.
The error is also ok: "drag and drop not supported".

Definitely better!

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

Title:
  Cannot drag attachment from mail attachment pane to desktop

Status in One Hundred Papercuts:
  Triaged
Status in SeaMonkey:
  Confirmed
Status in Mozilla Thunderbird:
  Confirmed
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 9.04
  Gnome Desktop 2.26.1
  Thunderbird 2.0.0.21

  This is regression introduced  in Jaunty as it works in Intrepid.
  Dragging an attachment from the attachment pane to the desktop give
  the following error:

  ==
  Error while copying
  There was an error getting information about "fetch>UID>.voicemail>1784".

  The specified location is not supported
  ==

  Mail account is IMAP. This error was shown to seb128 and asac. The
  expected behavior is that the file is copied to the destination onto
  which it is dragged.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/381017/+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 381017]

[Romano Giannetti]

Checked right now with thunderbird 68.2.1 --- the bug is still here. The
dropped attachment creates a file which consists of a broken link.

I *suspect* that this bug has been forgot; it seems really strange that,
with all the nice things happened to thunderbird in the last couple of
years, no one fixed this quite gross "feature..."

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

Title:
  Cannot drag attachment from mail attachment pane to desktop

Status in One Hundred Papercuts:
  Triaged
Status in SeaMonkey:
  Confirmed
Status in Mozilla Thunderbird:
  Confirmed
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 9.04
  Gnome Desktop 2.26.1
  Thunderbird 2.0.0.21

  This is regression introduced  in Jaunty as it works in Intrepid.
  Dragging an attachment from the attachment pane to the desktop give
  the following error:

  ==
  Error while copying
  There was an error getting information about "fetch>UID>.voicemail>1784".

  The specified location is not supported
  ==

  Mail account is IMAP. This error was shown to seb128 and asac. The
  expected behavior is that the file is copied to the destination onto
  which it is dragged.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/381017/+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 381017]

[Romano Giannetti]

It seems that the firefox bug (which is listed as a duplicate, I do not
think is 100% correct) #396370 has been marked as fixed. Could this be
the case for thunderbird also? That would be great...

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

Title:
  Cannot drag attachment from mail attachment pane to desktop

Status in One Hundred Papercuts:
  Triaged
Status in SeaMonkey:
  Confirmed
Status in Mozilla Thunderbird:
  Confirmed
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 9.04
  Gnome Desktop 2.26.1
  Thunderbird 2.0.0.21

  This is regression introduced  in Jaunty as it works in Intrepid.
  Dragging an attachment from the attachment pane to the desktop give
  the following error:

  ==
  Error while copying
  There was an error getting information about "fetch>UID>.voicemail>1784".

  The specified location is not supported
  ==

  Mail account is IMAP. This error was shown to seb128 and asac. The
  expected behavior is that the file is copied to the destination onto
  which it is dragged.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/381017/+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 381017]

[Romano Giannetti]

Yes, still here; will not disappear alone.

I still think that the worst problem of this bug is that is _seems_ to
work, and can lead to data loss. It would be much better to forbid the
drag and drop completely, if fixing it is too difficult.

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

Title:
  Cannot drag attachment from mail attachment pane to desktop

Status in One Hundred Papercuts:
  Triaged
Status in SeaMonkey:
  Confirmed
Status in Mozilla Thunderbird:
  Confirmed
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 9.04
  Gnome Desktop 2.26.1
  Thunderbird 2.0.0.21

  This is regression introduced  in Jaunty as it works in Intrepid.
  Dragging an attachment from the attachment pane to the desktop give
  the following error:

  ==
  Error while copying
  There was an error getting information about "fetch>UID>.voicemail>1784".

  The specified location is not supported
  ==

  Mail account is IMAP. This error was shown to seb128 and asac. The
  expected behavior is that the file is copied to the destination onto
  which it is dragged.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/381017/+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 381017] Re: Cannot drag attachment from mail attachment pane to desktop

[Romano Giannetti]

Still here in TB 68.2.1. Must be a record...

Really, I suppose this bug has been forgotten... ;-)

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

Title:
  Cannot drag attachment from mail attachment pane to desktop

Status in One Hundred Papercuts:
  Triaged
Status in SeaMonkey:
  Confirmed
Status in Mozilla Thunderbird:
  Confirmed
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 9.04
  Gnome Desktop 2.26.1
  Thunderbird 2.0.0.21

  This is regression introduced  in Jaunty as it works in Intrepid.
  Dragging an attachment from the attachment pane to the desktop give
  the following error:

  ==
  Error while copying
  There was an error getting information about "fetch>UID>.voicemail>1784".

  The specified location is not supported
  ==

  Mail account is IMAP. This error was shown to seb128 and asac. The
  expected behavior is that the file is copied to the destination onto
  which it is dragged.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/381017/+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 1808702] Re: Bubblewrap integration broke user thumbnailers

[Romano Giannetti]

@c4pp4 --- you're right. So probably the only thing we need is the bind
of /etc/alternatives; upstream seems to agree it's the only way to go:
https://gitlab.gnome.org/GNOME/gnome-desktop/issues/92

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

Title:
  Bubblewrap integration broke user thumbnailers

Status in gnome-desktop3 package in Ubuntu:
  Confirmed

Bug description:
  This bug is related to https://bugs.launchpad.net/ubuntu/+source
  /gnome-desktop3/+bug/1795668 and to the question in Ubuntu
  Stackexchange https://askubuntu.com/questions/1088539/custom-
  thumbnailers-don-t-work-on-ubuntu-18-10-and-18-04

  The recent hardening on thumbnailers by using bubblewrap is causing a
  problem with user-installed thumbnailers. Consider this (for example)
  thumbnailer to add a small Dilbert icon to the GIMP .xcf files:

  
  #!/bin/bash

  tmpfile1=$(tempfile --directory /tmp --prefix xcft --suffix .png)
  trap 'rm -rf $tmpfile1' INT EXIT TERM

  die() {
echo >&2 "$@"
rm -rf $tmpfile1
exit 1
  }
   
  # The script will be called with parameters : -s %s %u %o
  # -s %s: vertical size,  %u: input url, %o: output file

  if [ $1 = "-s" ]; then 
 size=$2
 uin=$3
 fout=$4
  else
 size=32 #default size
 uin=$1
 fout=$2
  fi

  # uin es una url, eliminar "file://"
  fin="${uin#file://*}"

  /usr/bin/gnome-xcf-thumbnailer -s $size "$fin" $tmpfile1 || die 
"gnome-xcf-thumbnailer failed"
  /usr/bin/composite-im6.q16  -gravity southeast  \
 \(  -resize $((size/2))x$((size/2)) /usr/share/gimp/2.0/images/wilber.png 
\) \
 \( -resize $sizex$size $tmpfile1 \)  "$fout" || die "convert failed"

  rm -rf $tmpfile1
  exit 0

  It used to work before the last update to use bubblewrap, and now
  doesn't work anymore. I tried to dig into https://github.com/GNOME
  /gnome-desktop/blob/master/libgnome-desktop/gnome-desktop-thumbnail-
  script.c to see what happens, and I concluded that the "reinforced"
  thumbnail generator do this:

  mkdir /tmp/temporary

  bwrap --ro-bind /usr /usr \
  --ro-bind /etc/ld.so.cache /etc/ld.so.cache \
  --ro-bind /bin /bin \
  --ro-bind /lib64 /lib64 \
  --ro-bind /lib /lib \
  --ro-bind /sbin /sbin \
  --proc /proc  \
  --dev   /dev  \
  --chdir   /  \
  --setenv   GIO_USE_VFS   local  \
  --unshare-all  \
  --die-with-parent  \
  --bind /tmp/temporary /tmp \
  --ro-bind /home/romano/software/thumbnailers/test/rgttiwm.xcf  
/tmp/gnome-desktop-file-to-thumbnail.xcf  \
  /usr/bin/xcf-thumb -s 128 file:///tmp/gnome-desktop-file-to-thumbnail.xcf 
/tmp/gnome-desktop-thumbnailer.png
  #
  cp /tmp/temporary/gnome-desktop-thumbnailer.png test.png

  ...and this way, my thumbnailer did succeed in creating the PNG with
  the correct preview. But when called internally by gnome, it fails,
  and creates a strange "~/.cache/thumbnailer/fail" file containing the
  following:

  �PNG
  
  
IHDR
ĉd�EtEXtThumb::URIfile:///home/romano/software/thumbnailers/test/rgttiwm.xcftEXtThumb::MTime1380735765�y�O
 tEXtSoftwareGNOME::ThumbnailFactoryo 
  [...]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1808702/+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 1808702] Re: Bubblewrap integration broke user thumbnailers

[Romano Giannetti]

@c4pp4, could be, but I think this is already in...

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

Title:
  Bubblewrap integration broke user thumbnailers

Status in gnome-desktop3 package in Ubuntu:
  Confirmed

Bug description:
  This bug is related to https://bugs.launchpad.net/ubuntu/+source
  /gnome-desktop3/+bug/1795668 and to the question in Ubuntu
  Stackexchange https://askubuntu.com/questions/1088539/custom-
  thumbnailers-don-t-work-on-ubuntu-18-10-and-18-04

  The recent hardening on thumbnailers by using bubblewrap is causing a
  problem with user-installed thumbnailers. Consider this (for example)
  thumbnailer to add a small Dilbert icon to the GIMP .xcf files:

  
  #!/bin/bash

  tmpfile1=$(tempfile --directory /tmp --prefix xcft --suffix .png)
  trap 'rm -rf $tmpfile1' INT EXIT TERM

  die() {
echo >&2 "$@"
rm -rf $tmpfile1
exit 1
  }
   
  # The script will be called with parameters : -s %s %u %o
  # -s %s: vertical size,  %u: input url, %o: output file

  if [ $1 = "-s" ]; then 
 size=$2
 uin=$3
 fout=$4
  else
 size=32 #default size
 uin=$1
 fout=$2
  fi

  # uin es una url, eliminar "file://"
  fin="${uin#file://*}"

  /usr/bin/gnome-xcf-thumbnailer -s $size "$fin" $tmpfile1 || die 
"gnome-xcf-thumbnailer failed"
  /usr/bin/composite-im6.q16  -gravity southeast  \
 \(  -resize $((size/2))x$((size/2)) /usr/share/gimp/2.0/images/wilber.png 
\) \
 \( -resize $sizex$size $tmpfile1 \)  "$fout" || die "convert failed"

  rm -rf $tmpfile1
  exit 0

  It used to work before the last update to use bubblewrap, and now
  doesn't work anymore. I tried to dig into https://github.com/GNOME
  /gnome-desktop/blob/master/libgnome-desktop/gnome-desktop-thumbnail-
  script.c to see what happens, and I concluded that the "reinforced"
  thumbnail generator do this:

  mkdir /tmp/temporary

  bwrap --ro-bind /usr /usr \
  --ro-bind /etc/ld.so.cache /etc/ld.so.cache \
  --ro-bind /bin /bin \
  --ro-bind /lib64 /lib64 \
  --ro-bind /lib /lib \
  --ro-bind /sbin /sbin \
  --proc /proc  \
  --dev   /dev  \
  --chdir   /  \
  --setenv   GIO_USE_VFS   local  \
  --unshare-all  \
  --die-with-parent  \
  --bind /tmp/temporary /tmp \
  --ro-bind /home/romano/software/thumbnailers/test/rgttiwm.xcf  
/tmp/gnome-desktop-file-to-thumbnail.xcf  \
  /usr/bin/xcf-thumb -s 128 file:///tmp/gnome-desktop-file-to-thumbnail.xcf 
/tmp/gnome-desktop-thumbnailer.png
  #
  cp /tmp/temporary/gnome-desktop-thumbnailer.png test.png

  ...and this way, my thumbnailer did succeed in creating the PNG with
  the correct preview. But when called internally by gnome, it fails,
  and creates a strange "~/.cache/thumbnailer/fail" file containing the
  following:

  �PNG
  
  
IHDR
ĉd�EtEXtThumb::URIfile:///home/romano/software/thumbnailers/test/rgttiwm.xcftEXtThumb::MTime1380735765�y�O
 tEXtSoftwareGNOME::ThumbnailFactoryo 
  [...]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1808702/+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 1448778] Re: Evince fails to display some fonts (some font thing failed)

[Romano Giannetti]

And by the way, just if somebody is still struggling to find where the
"good" error messages (instead of the surprising useful "some font thing
failed"), grep for apparmor in /var/log/kern.log

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

Title:
  Evince fails to display some fonts (some font thing failed)

Status in evince package in Ubuntu:
  Invalid

Bug description:
  Dear experts,

  Since the upgrade to Ubuntu 15.04, evince fails to display some fonts
  of most of my latex pdfs. I attached an example of the pdf rendered by
  evince, and a screenshot of what it's supposed to look like. The
  console is spammed with errors:

  'some font thing failed'

  The pdf display correctly with xpdf and  okular.

  Thanks

  Description:  Ubuntu 15.04
  Release:  15.04
  evince:
Installed: 3.14.2-0ubuntu2
Candidate: 3.14.2-0ubuntu2
Version table:
   *** 3.14.2-0ubuntu2 0
  500 http://ftp.belnet.be/ubuntu.com/ubuntu/ vivid/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: evince 3.14.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Apr 26 23:15:02 2015
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1448778/+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 1448778] Re: Evince fails to display some fonts (some font thing failed)

[Romano Giannetti]

My solution was to apply this diff:

diff --git a/./etc-apparmor.d-abstractions-fonts 
b/etc/apparmor.d/abstractions/fonts
index 45cdf9a..44c54ac 100644
--- a/./etc-apparmor.d-abstractions-fonts
+++ b/etc/apparmor.d/abstractions/fonts
@@ -51,6 +51,8 @@
 
   /usr/local/share/fonts/   r,
   /usr/local/share/fonts/** r,
+  /home/local/share/fonts/   r,
+  /home/local/share/fonts/** r,
 
   # poppler CMap tables
   /usr/share/poppler/cMap/**r,

...and the reloading the profiles (sudo service apparmor reload). So if
you have symlinked fonts directory, you simply have to add them to the
profile.

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

Title:
  Evince fails to display some fonts (some font thing failed)

Status in evince package in Ubuntu:
  Invalid

Bug description:
  Dear experts,

  Since the upgrade to Ubuntu 15.04, evince fails to display some fonts
  of most of my latex pdfs. I attached an example of the pdf rendered by
  evince, and a screenshot of what it's supposed to look like. The
  console is spammed with errors:

  'some font thing failed'

  The pdf display correctly with xpdf and  okular.

  Thanks

  Description:  Ubuntu 15.04
  Release:  15.04
  evince:
Installed: 3.14.2-0ubuntu2
Candidate: 3.14.2-0ubuntu2
Version table:
   *** 3.14.2-0ubuntu2 0
  500 http://ftp.belnet.be/ubuntu.com/ubuntu/ vivid/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: evince 3.14.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Apr 26 23:15:02 2015
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1448778/+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 1808702] Re: Bubblewrap integration broke user thumbnailers

[Romano Giannetti]

As an aside, can you hint where I can find the messages printed by the
`g_warning()` in the code? I was utterly unable to find them...

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

Title:
  Bubblewrap integration broke user thumbnailers

Status in gnome-desktop3 package in Ubuntu:
  Confirmed

Bug description:
  This bug is related to https://bugs.launchpad.net/ubuntu/+source
  /gnome-desktop3/+bug/1795668 and to the question in Ubuntu
  Stackexchange https://askubuntu.com/questions/1088539/custom-
  thumbnailers-don-t-work-on-ubuntu-18-10-and-18-04

  The recent hardening on thumbnailers by using bubblewrap is causing a
  problem with user-installed thumbnailers. Consider this (for example)
  thumbnailer to add a small Dilbert icon to the GIMP .xcf files:

  
  #!/bin/bash

  tmpfile1=$(tempfile --directory /tmp --prefix xcft --suffix .png)
  trap 'rm -rf $tmpfile1' INT EXIT TERM

  die() {
echo >&2 "$@"
rm -rf $tmpfile1
exit 1
  }
   
  # The script will be called with parameters : -s %s %u %o
  # -s %s: vertical size,  %u: input url, %o: output file

  if [ $1 = "-s" ]; then 
 size=$2
 uin=$3
 fout=$4
  else
 size=32 #default size
 uin=$1
 fout=$2
  fi

  # uin es una url, eliminar "file://"
  fin="${uin#file://*}"

  /usr/bin/gnome-xcf-thumbnailer -s $size "$fin" $tmpfile1 || die 
"gnome-xcf-thumbnailer failed"
  /usr/bin/composite-im6.q16  -gravity southeast  \
 \(  -resize $((size/2))x$((size/2)) /usr/share/gimp/2.0/images/wilber.png 
\) \
 \( -resize $sizex$size $tmpfile1 \)  "$fout" || die "convert failed"

  rm -rf $tmpfile1
  exit 0

  It used to work before the last update to use bubblewrap, and now
  doesn't work anymore. I tried to dig into https://github.com/GNOME
  /gnome-desktop/blob/master/libgnome-desktop/gnome-desktop-thumbnail-
  script.c to see what happens, and I concluded that the "reinforced"
  thumbnail generator do this:

  mkdir /tmp/temporary

  bwrap --ro-bind /usr /usr \
  --ro-bind /etc/ld.so.cache /etc/ld.so.cache \
  --ro-bind /bin /bin \
  --ro-bind /lib64 /lib64 \
  --ro-bind /lib /lib \
  --ro-bind /sbin /sbin \
  --proc /proc  \
  --dev   /dev  \
  --chdir   /  \
  --setenv   GIO_USE_VFS   local  \
  --unshare-all  \
  --die-with-parent  \
  --bind /tmp/temporary /tmp \
  --ro-bind /home/romano/software/thumbnailers/test/rgttiwm.xcf  
/tmp/gnome-desktop-file-to-thumbnail.xcf  \
  /usr/bin/xcf-thumb -s 128 file:///tmp/gnome-desktop-file-to-thumbnail.xcf 
/tmp/gnome-desktop-thumbnailer.png
  #
  cp /tmp/temporary/gnome-desktop-thumbnailer.png test.png

  ...and this way, my thumbnailer did succeed in creating the PNG with
  the correct preview. But when called internally by gnome, it fails,
  and creates a strange "~/.cache/thumbnailer/fail" file containing the
  following:

  �PNG
  
  
IHDR
ĉd�EtEXtThumb::URIfile:///home/romano/software/thumbnailers/test/rgttiwm.xcftEXtThumb::MTime1380735765�y�O
 tEXtSoftwareGNOME::ThumbnailFactoryo 
  [...]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1808702/+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 1808702] Re: Bubblewrap integration broke user thumbnailers

[Romano Giannetti]

Indeed. So it must be something different; the problem with alternative
is real, but nevertheless the aforementioned thumbnailer does not work
even with the absolute path to composite...

Will dig a bit more. The puzzling thing is that using the wrapper script
from http://bernaerts.dyndns.org/linux/74-ubuntu/360-ubuntu-nautilus-
external-thumbnailer-failure *does* fix things...

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

Title:
  Bubblewrap integration broke user thumbnailers

Status in gnome-desktop3 package in Ubuntu:
  Confirmed

Bug description:
  This bug is related to https://bugs.launchpad.net/ubuntu/+source
  /gnome-desktop3/+bug/1795668 and to the question in Ubuntu
  Stackexchange https://askubuntu.com/questions/1088539/custom-
  thumbnailers-don-t-work-on-ubuntu-18-10-and-18-04

  The recent hardening on thumbnailers by using bubblewrap is causing a
  problem with user-installed thumbnailers. Consider this (for example)
  thumbnailer to add a small Dilbert icon to the GIMP .xcf files:

  
  #!/bin/bash

  tmpfile1=$(tempfile --directory /tmp --prefix xcft --suffix .png)
  trap 'rm -rf $tmpfile1' INT EXIT TERM

  die() {
echo >&2 "$@"
rm -rf $tmpfile1
exit 1
  }
   
  # The script will be called with parameters : -s %s %u %o
  # -s %s: vertical size,  %u: input url, %o: output file

  if [ $1 = "-s" ]; then 
 size=$2
 uin=$3
 fout=$4
  else
 size=32 #default size
 uin=$1
 fout=$2
  fi

  # uin es una url, eliminar "file://"
  fin="${uin#file://*}"

  /usr/bin/gnome-xcf-thumbnailer -s $size "$fin" $tmpfile1 || die 
"gnome-xcf-thumbnailer failed"
  /usr/bin/composite-im6.q16  -gravity southeast  \
 \(  -resize $((size/2))x$((size/2)) /usr/share/gimp/2.0/images/wilber.png 
\) \
 \( -resize $sizex$size $tmpfile1 \)  "$fout" || die "convert failed"

  rm -rf $tmpfile1
  exit 0

  It used to work before the last update to use bubblewrap, and now
  doesn't work anymore. I tried to dig into https://github.com/GNOME
  /gnome-desktop/blob/master/libgnome-desktop/gnome-desktop-thumbnail-
  script.c to see what happens, and I concluded that the "reinforced"
  thumbnail generator do this:

  mkdir /tmp/temporary

  bwrap --ro-bind /usr /usr \
  --ro-bind /etc/ld.so.cache /etc/ld.so.cache \
  --ro-bind /bin /bin \
  --ro-bind /lib64 /lib64 \
  --ro-bind /lib /lib \
  --ro-bind /sbin /sbin \
  --proc /proc  \
  --dev   /dev  \
  --chdir   /  \
  --setenv   GIO_USE_VFS   local  \
  --unshare-all  \
  --die-with-parent  \
  --bind /tmp/temporary /tmp \
  --ro-bind /home/romano/software/thumbnailers/test/rgttiwm.xcf  
/tmp/gnome-desktop-file-to-thumbnail.xcf  \
  /usr/bin/xcf-thumb -s 128 file:///tmp/gnome-desktop-file-to-thumbnail.xcf 
/tmp/gnome-desktop-thumbnailer.png
  #
  cp /tmp/temporary/gnome-desktop-thumbnailer.png test.png

  ...and this way, my thumbnailer did succeed in creating the PNG with
  the correct preview. But when called internally by gnome, it fails,
  and creates a strange "~/.cache/thumbnailer/fail" file containing the
  following:

  �PNG
  
  
IHDR
ĉd�EtEXtThumb::URIfile:///home/romano/software/thumbnailers/test/rgttiwm.xcftEXtThumb::MTime1380735765�y�O
 tEXtSoftwareGNOME::ThumbnailFactoryo 
  [...]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1808702/+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 1795668] Re: Enable bubblewrap in gnome-desktop3 for Ubuntu 18.04 LTS

[Romano Giannetti]

...and we have also the huge slowdown, see
https://gitlab.gnome.org/GNOME/gnome-desktop/issues/90

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

Title:
  Enable bubblewrap in gnome-desktop3 for Ubuntu 18.04 LTS

Status in bubblewrap package in Ubuntu:
  Fix Released
Status in gnome-desktop3 package in Ubuntu:
  Fix Released

Bug description:
  Impact
  ==
  gnome-desktop 3.26 hardened the thumbnailers with bubblewrap to mitigate 
several vulnerabilities. Ubuntu had to disable that feature until bubblewrap 
could be promoted to main.

  bubblewrap is now in main for 18.10 and the feature is now enabled
  there. The intention has been for that change to be backported to
  18.04 LTS as a security fix.

  The bubblewrap MIR is https://launchpad.net/bugs/1709164

  We'll need to promote bubblewrap to main before this update should be
  pushed to bionic.

  Can you sponsor directly from the git repo instead of with a debdiff?

  gbp clone https://git.launchpad.net/~ubuntu-desktop/ubuntu/+source
  /gnome-desktop3

  git checkout ubuntu/bionic

  gbp clone https://git.launchpad.net/~ubuntu-
  desktop/ubuntu/+source/bubblewrap

  Testing Done
  
  I test built bubblewrap and its autopkgtest passes:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-jbicha-arch/bionic/amd64/b/bubblewrap/20181002_153548_f5821@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bubblewrap/+bug/1795668/+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 1808702] Re: Bubblewrap integration broke user thumbnailers

[Romano Giannetti]

Ok, the problem is that the commit from:

https://gitlab.gnome.org/GNOME/gnome-
desktop/commit/259e7e4edb0d9b84fb7cf0847149ff8d42ab9a56

should be added, since Ubuntu/Debian has unmerged /usr.

Also, the problem with alternatives still stands, see
https://gitlab.gnome.org/GNOME/gnome-desktop/issues/92

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

Title:
  Bubblewrap integration broke user thumbnailers

Status in gnome-desktop3 package in Ubuntu:
  New

Bug description:
  This bug is related to https://bugs.launchpad.net/ubuntu/+source
  /gnome-desktop3/+bug/1795668 and to the question in Ubuntu
  Stackexchange https://askubuntu.com/questions/1088539/custom-
  thumbnailers-don-t-work-on-ubuntu-18-10-and-18-04

  The recent hardening on thumbnailers by using bubblewrap is causing a
  problem with user-installed thumbnailers. Consider this (for example)
  thumbnailer to add a small Dilbert icon to the GIMP .xcf files:

  
  #!/bin/bash

  tmpfile1=$(tempfile --directory /tmp --prefix xcft --suffix .png)
  trap 'rm -rf $tmpfile1' INT EXIT TERM

  die() {
echo >&2 "$@"
rm -rf $tmpfile1
exit 1
  }
   
  # The script will be called with parameters : -s %s %u %o
  # -s %s: vertical size,  %u: input url, %o: output file

  if [ $1 = "-s" ]; then 
 size=$2
 uin=$3
 fout=$4
  else
 size=32 #default size
 uin=$1
 fout=$2
  fi

  # uin es una url, eliminar "file://"
  fin="${uin#file://*}"

  /usr/bin/gnome-xcf-thumbnailer -s $size "$fin" $tmpfile1 || die 
"gnome-xcf-thumbnailer failed"
  /usr/bin/composite-im6.q16  -gravity southeast  \
 \(  -resize $((size/2))x$((size/2)) /usr/share/gimp/2.0/images/wilber.png 
\) \
 \( -resize $sizex$size $tmpfile1 \)  "$fout" || die "convert failed"

  rm -rf $tmpfile1
  exit 0

  It used to work before the last update to use bubblewrap, and now
  doesn't work anymore. I tried to dig into https://github.com/GNOME
  /gnome-desktop/blob/master/libgnome-desktop/gnome-desktop-thumbnail-
  script.c to see what happens, and I concluded that the "reinforced"
  thumbnail generator do this:

  mkdir /tmp/temporary

  bwrap --ro-bind /usr /usr \
  --ro-bind /etc/ld.so.cache /etc/ld.so.cache \
  --ro-bind /bin /bin \
  --ro-bind /lib64 /lib64 \
  --ro-bind /lib /lib \
  --ro-bind /sbin /sbin \
  --proc /proc  \
  --dev   /dev  \
  --chdir   /  \
  --setenv   GIO_USE_VFS   local  \
  --unshare-all  \
  --die-with-parent  \
  --bind /tmp/temporary /tmp \
  --ro-bind /home/romano/software/thumbnailers/test/rgttiwm.xcf  
/tmp/gnome-desktop-file-to-thumbnail.xcf  \
  /usr/bin/xcf-thumb -s 128 file:///tmp/gnome-desktop-file-to-thumbnail.xcf 
/tmp/gnome-desktop-thumbnailer.png
  #
  cp /tmp/temporary/gnome-desktop-thumbnailer.png test.png

  ...and this way, my thumbnailer did succeed in creating the PNG with
  the correct preview. But when called internally by gnome, it fails,
  and creates a strange "~/.cache/thumbnailer/fail" file containing the
  following:

  �PNG
  
  
IHDR
ĉd�EtEXtThumb::URIfile:///home/romano/software/thumbnailers/test/rgttiwm.xcftEXtThumb::MTime1380735765�y�O
 tEXtSoftwareGNOME::ThumbnailFactoryo 
  [...]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1808702/+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 1795668] Re: Enable bubblewrap in gnome-desktop3 for Ubuntu 18.04 LTS

[Romano Giannetti]

Yep: @nicolas-bernaerts is right. Ubuntu should include this commit:

https://gitlab.gnome.org/GNOME/gnome-
desktop/commit/259e7e4edb0d9b84fb7cf0847149ff8d42ab9a56

since we have unmerged /usr.

Also, the problem with alternatives still stands, see
https://gitlab.gnome.org/GNOME/gnome-desktop/issues/92

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

Title:
  Enable bubblewrap in gnome-desktop3 for Ubuntu 18.04 LTS

Status in bubblewrap package in Ubuntu:
  Fix Released
Status in gnome-desktop3 package in Ubuntu:
  Fix Released

Bug description:
  Impact
  ==
  gnome-desktop 3.26 hardened the thumbnailers with bubblewrap to mitigate 
several vulnerabilities. Ubuntu had to disable that feature until bubblewrap 
could be promoted to main.

  bubblewrap is now in main for 18.10 and the feature is now enabled
  there. The intention has been for that change to be backported to
  18.04 LTS as a security fix.

  The bubblewrap MIR is https://launchpad.net/bugs/1709164

  We'll need to promote bubblewrap to main before this update should be
  pushed to bionic.

  Can you sponsor directly from the git repo instead of with a debdiff?

  gbp clone https://git.launchpad.net/~ubuntu-desktop/ubuntu/+source
  /gnome-desktop3

  git checkout ubuntu/bionic

  gbp clone https://git.launchpad.net/~ubuntu-
  desktop/ubuntu/+source/bubblewrap

  Testing Done
  
  I test built bubblewrap and its autopkgtest passes:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-jbicha-arch/bionic/amd64/b/bubblewrap/20181002_153548_f5821@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bubblewrap/+bug/1795668/+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 1808702] Re: Bubblewrap integration broke user thumbnailers

[Romano Giannetti]

Notice anyway that one of the problems was that originally the
thumbnailer called

 /usr/bin/composite

which, do to the alternative setup in .deb packages, was a link to
/etc/alternatives/composite that pointed back to the real binary;
probably the "/etc/alternatives/" directory should be added to the bind-
ed directories...

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

Title:
  Bubblewrap integration broke user thumbnailers

Status in gnome-desktop3 package in Ubuntu:
  New

Bug description:
  This bug is related to https://bugs.launchpad.net/ubuntu/+source
  /gnome-desktop3/+bug/1795668 and to the question in Ubuntu
  Stackexchange https://askubuntu.com/questions/1088539/custom-
  thumbnailers-don-t-work-on-ubuntu-18-10-and-18-04

  The recent hardening on thumbnailers by using bubblewrap is causing a
  problem with user-installed thumbnailers. Consider this (for example)
  thumbnailer to add a small Dilbert icon to the GIMP .xcf files:

  
  #!/bin/bash

  tmpfile1=$(tempfile --directory /tmp --prefix xcft --suffix .png)
  trap 'rm -rf $tmpfile1' INT EXIT TERM

  die() {
echo >&2 "$@"
rm -rf $tmpfile1
exit 1
  }
   
  # The script will be called with parameters : -s %s %u %o
  # -s %s: vertical size,  %u: input url, %o: output file

  if [ $1 = "-s" ]; then 
 size=$2
 uin=$3
 fout=$4
  else
 size=32 #default size
 uin=$1
 fout=$2
  fi

  # uin es una url, eliminar "file://"
  fin="${uin#file://*}"

  /usr/bin/gnome-xcf-thumbnailer -s $size "$fin" $tmpfile1 || die 
"gnome-xcf-thumbnailer failed"
  /usr/bin/composite-im6.q16  -gravity southeast  \
 \(  -resize $((size/2))x$((size/2)) /usr/share/gimp/2.0/images/wilber.png 
\) \
 \( -resize $sizex$size $tmpfile1 \)  "$fout" || die "convert failed"

  rm -rf $tmpfile1
  exit 0

  It used to work before the last update to use bubblewrap, and now
  doesn't work anymore. I tried to dig into https://github.com/GNOME
  /gnome-desktop/blob/master/libgnome-desktop/gnome-desktop-thumbnail-
  script.c to see what happens, and I concluded that the "reinforced"
  thumbnail generator do this:

  mkdir /tmp/temporary

  bwrap --ro-bind /usr /usr \
  --ro-bind /etc/ld.so.cache /etc/ld.so.cache \
  --ro-bind /bin /bin \
  --ro-bind /lib64 /lib64 \
  --ro-bind /lib /lib \
  --ro-bind /sbin /sbin \
  --proc /proc  \
  --dev   /dev  \
  --chdir   /  \
  --setenv   GIO_USE_VFS   local  \
  --unshare-all  \
  --die-with-parent  \
  --bind /tmp/temporary /tmp \
  --ro-bind /home/romano/software/thumbnailers/test/rgttiwm.xcf  
/tmp/gnome-desktop-file-to-thumbnail.xcf  \
  /usr/bin/xcf-thumb -s 128 file:///tmp/gnome-desktop-file-to-thumbnail.xcf 
/tmp/gnome-desktop-thumbnailer.png
  #
  cp /tmp/temporary/gnome-desktop-thumbnailer.png test.png

  ...and this way, my thumbnailer did succeed in creating the PNG with
  the correct preview. But when called internally by gnome, it fails,
  and creates a strange "~/.cache/thumbnailer/fail" file containing the
  following:

  �PNG
  
  
IHDR
ĉd�EtEXtThumb::URIfile:///home/romano/software/thumbnailers/test/rgttiwm.xcftEXtThumb::MTime1380735765�y�O
 tEXtSoftwareGNOME::ThumbnailFactoryo 
  [...]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1808702/+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 1808702] [NEW] Bubblewrap integration broke user thumbnailers

[Romano Giannetti]

Public bug reported:

This bug is related to https://bugs.launchpad.net/ubuntu/+source/gnome-
desktop3/+bug/1795668 and to the question in Ubuntu Stackexchange
https://askubuntu.com/questions/1088539/custom-thumbnailers-don-t-work-
on-ubuntu-18-10-and-18-04

The recent hardening on thumbnailers by using bubblewrap is causing a
problem with user-installed thumbnailers. Consider this (for example)
thumbnailer to add a small Dilbert icon to the GIMP .xcf files:


#!/bin/bash

tmpfile1=$(tempfile --directory /tmp --prefix xcft --suffix .png)
trap 'rm -rf $tmpfile1' INT EXIT TERM

die() {
  echo >&2 "$@"
  rm -rf $tmpfile1
  exit 1
}
 
# The script will be called with parameters : -s %s %u %o
# -s %s: vertical size,  %u: input url, %o: output file

if [ $1 = "-s" ]; then 
   size=$2
   uin=$3
   fout=$4
else
   size=32 #default size
   uin=$1
   fout=$2
fi

# uin es una url, eliminar "file://"
fin="${uin#file://*}"

/usr/bin/gnome-xcf-thumbnailer -s $size "$fin" $tmpfile1 || die 
"gnome-xcf-thumbnailer failed"
/usr/bin/composite-im6.q16  -gravity southeast  \
   \(  -resize $((size/2))x$((size/2)) /usr/share/gimp/2.0/images/wilber.png \) 
\
   \( -resize $sizex$size $tmpfile1 \)  "$fout" || die "convert failed"

rm -rf $tmpfile1
exit 0

It used to work before the last update to use bubblewrap, and now
doesn't work anymore. I tried to dig into https://github.com/GNOME
/gnome-desktop/blob/master/libgnome-desktop/gnome-desktop-thumbnail-
script.c to see what happens, and I concluded that the "reinforced"
thumbnail generator do this:

mkdir /tmp/temporary

bwrap --ro-bind /usr /usr \
--ro-bind /etc/ld.so.cache /etc/ld.so.cache \
--ro-bind /bin /bin \
--ro-bind /lib64 /lib64 \
--ro-bind /lib /lib \
--ro-bind /sbin /sbin \
--proc /proc  \
--dev   /dev  \
--chdir   /  \
--setenv   GIO_USE_VFS   local  \
--unshare-all  \
--die-with-parent  \
--bind /tmp/temporary /tmp \
--ro-bind /home/romano/software/thumbnailers/test/rgttiwm.xcf  
/tmp/gnome-desktop-file-to-thumbnail.xcf  \
/usr/bin/xcf-thumb -s 128 file:///tmp/gnome-desktop-file-to-thumbnail.xcf 
/tmp/gnome-desktop-thumbnailer.png
#
cp /tmp/temporary/gnome-desktop-thumbnailer.png test.png

...and this way, my thumbnailer did succeed in creating the PNG with the
correct preview. But when called internally by gnome, it fails, and
creates a strange "~/.cache/thumbnailer/fail" file containing the
following:

�PNG

IHDR
ĉd�EtEXtThumb::URIfile:///home/romano/software/thumbnailers/test/rgttiwm.xcftEXtThumb::MTime1380735765�y�O
 tEXtSoftwareGNOME::ThumbnailFactoryo 
[...]

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


** Tags: bubblewrap thumbnails

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

Title:
  Bubblewrap integration broke user thumbnailers

Status in gnome-desktop3 package in Ubuntu:
  New

Bug description:
  This bug is related to https://bugs.launchpad.net/ubuntu/+source
  /gnome-desktop3/+bug/1795668 and to the question in Ubuntu
  Stackexchange https://askubuntu.com/questions/1088539/custom-
  thumbnailers-don-t-work-on-ubuntu-18-10-and-18-04

  The recent hardening on thumbnailers by using bubblewrap is causing a
  problem with user-installed thumbnailers. Consider this (for example)
  thumbnailer to add a small Dilbert icon to the GIMP .xcf files:

  
  #!/bin/bash

  tmpfile1=$(tempfile --directory /tmp --prefix xcft --suffix .png)
  trap 'rm -rf $tmpfile1' INT EXIT TERM

  die() {
echo >&2 "$@"
rm -rf $tmpfile1
exit 1
  }
   
  # The script will be called with parameters : -s %s %u %o
  # -s %s: vertical size,  %u: input url, %o: output file

  if [ $1 = "-s" ]; then 
 size=$2
 uin=$3
 fout=$4
  else
 size=32 #default size
 uin=$1
 fout=$2
  fi

  # uin es una url, eliminar "file://"
  fin="${uin#file://*}"

  /usr/bin/gnome-xcf-thumbnailer -s $size "$fin" $tmpfile1 || die 
"gnome-xcf-thumbnailer failed"
  /usr/bin/composite-im6.q16  -gravity southeast  \
 \(  -resize $((size/2))x$((size/2)) /usr/share/gimp/2.0/images/wilber.png 
\) \
 \( -resize $sizex$size $tmpfile1 \)  "$fout" || die "convert failed"

  rm -rf $tmpfile1
  exit 0

  It used to work before the last update to use bubblewrap, and now
  doesn't work anymore. I tried to dig into https://github.com/GNOME
  /gnome-desktop/blob/master/libgnome-desktop/gnome-desktop-thumbnail-
  script.c to see what happens, and I concluded that the "reinforced"
  thumbnail generator do this:

  mkdir /tmp/temporary

  bwrap --ro-bind /usr /usr \
  --ro-bind /etc/ld.so.cache /etc/ld.so.cache \
  --ro-bind /bin /bin \
  --ro-bind /lib64 /lib64 \
  --ro-bind /lib /lib \
  --ro-bind /sbin /sbin \
  --proc /proc  \
  --dev   /dev  \
  --chdir   /  \
  --setenv   GIO_USE_VFS   local  \
  --unshare-all

[Desktop-packages] [Bug 1795668] Re: Enable bubblewrap in gnome-desktop3 for Ubuntu 18.04 LTS

[Romano Giannetti]

This "enhancement2 broke all my thumbnailers too; unfortunately they are
quite a bit more complex than the one @eros2 commented.

Is there any instruction on how enabling back a personal script for
thumbnails generation after the upgrade? Note that this has been noticed
by users; see for example https://askubuntu.com/questions/1088539
/custom-thumbnailers-don-t-work-on-ubuntu-18-10

Thanks!

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

Title:
  Enable bubblewrap in gnome-desktop3 for Ubuntu 18.04 LTS

Status in bubblewrap package in Ubuntu:
  Fix Released
Status in gnome-desktop3 package in Ubuntu:
  Fix Released

Bug description:
  Impact
  ==
  gnome-desktop 3.26 hardened the thumbnailers with bubblewrap to mitigate 
several vulnerabilities. Ubuntu had to disable that feature until bubblewrap 
could be promoted to main.

  bubblewrap is now in main for 18.10 and the feature is now enabled
  there. The intention has been for that change to be backported to
  18.04 LTS as a security fix.

  The bubblewrap MIR is https://launchpad.net/bugs/1709164

  We'll need to promote bubblewrap to main before this update should be
  pushed to bionic.

  Can you sponsor directly from the git repo instead of with a debdiff?

  gbp clone https://git.launchpad.net/~ubuntu-desktop/ubuntu/+source
  /gnome-desktop3

  git checkout ubuntu/bionic

  gbp clone https://git.launchpad.net/~ubuntu-
  desktop/ubuntu/+source/bubblewrap

  Testing Done
  
  I test built bubblewrap and its autopkgtest passes:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-jbicha-arch/bionic/amd64/b/bubblewrap/20181002_153548_f5821@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bubblewrap/+bug/1795668/+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 1588545] Re: escape doesn't close search bar

[Romano Giannetti]

It seems that CTRL-F does the trick, anyway...

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

Title:
  escape doesn't close search bar

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  You can not leave the search bar just by pressing the escape button
  like it was in all nautilus versions before and after (3.18.5 and
  3.20.0).

  
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1588545/+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 1438510] Re: [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial and 16.10 yakkety

[Romano Giannetti]

As I commented in http://askubuntu.com/a/775524/16395, some people
reported success with the python script at
https://gist.github.com/pylover/d68be364adac5f946887b85e6ed6e7ae --- be
warned, there is a bit of NSFW language there.

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

Title:
  [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial
  and 16.10 yakkety

Status in PulseAudio:
  Unknown
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in bluez source package in Vivid:
  Won't Fix
Status in pulseaudio source package in Vivid:
  Won't Fix

Bug description:
  Just installed 15.04 fresh from the latest ISO (beta2).

  I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems
  to have regressed in functionality.

  In 14.10, I was able to set the output profile either to a2dp or
  hsp/hfp (telephony duplex).

  In 15.04, it only works in telephony duplex mode.  I can't get high
  fidelity sound playback to work at all.

  This thread seems to be related, though the workaround within did not solve 
the problem for me:
  https://bbs.archlinux.org/viewtopic.php?id=194006

  The bug is still present in 16.04 LTS and 16.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1438510/+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 1289047] Re: [Trusty] hostapd package is broken

[Romano Giannetti]

I am still using the pinned-down version hostapd_1.0-3ubuntu2.1 which
(seems to) work. If anyone lands here and it's stuck with the bug, here:
http://www.webupd8.org/2013/06/how-to-set-up-wireless-hotspot-
access.html you have the instruction on how to get it working.

Having it fixed for good would be nice, but the workaround does work, at
least last time I checked.

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

Title:
  [Trusty] hostapd package is broken

Status in One Hundred Papercuts:
  Triaged
Status in wpa package in Ubuntu:
  Triaged

Bug description:
  When trying to create an access point, I am met with a fatal error
  with hostapd:

  nl80211: Could not configure driver mode
  nl80211 driver initialization failed.
  hostapd_free_hapd_data: Interface wlan0 wasn't started

  What worked before no longer works today after a package upgrade.

  After installing hostapd deb from Ubuntu 13.10, it works.

  WORKAROUND: For this to persist through reboots, execute the following in a 
terminal:
  sudo nano /etc/NetworkManager/NetworkManager.conf

  Add the following entry where the x's are replaced with your WiFi MAC 
address, save, and then reboot:
  [keyfile]
  unmanaged-devices=mac:xx:xx:xx:xx:xx:xx

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: hostapd 1:2.1-0ubuntu1
  Uname: Linux 3.14.0-031400rc5-lowlatency x86_64
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  Date: Thu Mar  6 16:57:20 2014
  InstallationDate: Installed on 2014-02-01 (33 days ago)
  InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140121.1)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1289047/+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 1438510] Re: [REGRESSION] bluetooth headset no longer supports a2dp

[Romano Giannetti]

A new error mode is that now the BT device is not connected at all, even
after doing the #5 thing,  with the error:

bluetoothd[984]: Unable to get Headset Voice gateway SDP record: Host is
down

I need to reboot the system, unpair and pair again the device, and then
doing the dance of connecting with low quality, change to the internal
audio, disconnecting the BT device, reconnecting again, switch to A2DP
--- which now works. After 20 minutes.

I think something happened in the last kernel update.

Will start looking in Google for rain dances for the next time... ;-)

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

Title:
  [REGRESSION] bluetooth headset no longer supports a2dp

Status in PulseAudio:
  Unknown
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in bluez source package in Vivid:
  Won't Fix
Status in pulseaudio source package in Vivid:
  Won't Fix

Bug description:
  Just installed 15.04 fresh from the latest ISO (beta2).

  I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems
  to have regressed in functionality.

  In 14.10, I was able to set the output profile either to a2dp or
  hsp/hfp (telephony duplex).

  In 15.04, it only works in telephony duplex mode.  I can't get high
  fidelity sound playback to work at all.

  This thread seems to be related, though the workaround within did not solve 
the problem for me:
  https://bbs.archlinux.org/viewtopic.php?id=194006

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1438510/+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 1448778] Re: Evince fails to display some fonts (some font thing failed)

[Romano Giannetti]

Just to add a note: it happened to me also, because I have /usr/local as
a symlink to /home/local (in a different partition) and evince (or
apparmor) correctly complained.

So all fonts from Microsoft, which are installed in /usr/local/font,
came out blank.

Setting aa-complain solved momentarily the thing, then an edit of the
profiles is recommended.

Now, 'some font thing failed' is not exactly a very informative error
message... ;-)

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

Title:
  Evince fails to display some fonts (some font thing failed)

Status in evince package in Ubuntu:
  Invalid

Bug description:
  Dear experts,

  Since the upgrade to Ubuntu 15.04, evince fails to display some fonts
  of most of my latex pdfs. I attached an example of the pdf rendered by
  evince, and a screenshot of what it's supposed to look like. The
  console is spammed with errors:

  'some font thing failed'

  The pdf display correctly with xpdf and  okular.

  Thanks

  Description:  Ubuntu 15.04
  Release:  15.04
  evince:
Installed: 3.14.2-0ubuntu2
Candidate: 3.14.2-0ubuntu2
Version table:
   *** 3.14.2-0ubuntu2 0
  500 http://ftp.belnet.be/ubuntu.com/ubuntu/ vivid/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: evince 3.14.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Apr 26 23:15:02 2015
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1448778/+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 1568604] Re: Mouse cursor lost when unlocking with Intel graphics

[Romano Giannetti]

Hmm. Using Ubuntu Gnome 16.04 here, intel graphics, no bug. On another
laptop, with Xubuntu, it happens.

I think is more screen-locker related that desktop-flavor related.

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

Title:
  Mouse cursor lost when unlocking with Intel graphics

Status in elementary OS:
  Fix Released
Status in xf86-video-intel:
  Confirmed
Status in xserver-xorg-video-intel package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-intel source package in Xenial:
  Confirmed
Status in xserver-xorg-video-intel package in Debian:
  Fix Released

Bug description:
  [Impact]
  Mouse cursor is no longer visible after VT-switch for systems with Intel 
graphics.

  Switching VTs again may cause the cursor to become visible again.
  - Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7)

  This is often observed in systems that lock the session and return to
  the greeter (including at least Xubuntu, Ubuntu Mate, and elementary
  OS).

  [Test Case]
  (Requires a lightdm-based screen locking solution)
  1. Start a new session.
  2. Lock your screen.
  2a. You are redirected to the lightdm greeter.
  3. Login/Unlock your session.
  4. Cursor is no longer visible.

  [Regression Potential]
  remains to be seen

  ===

  [Original Report]
  Cursor is visible at unlock screen either after returning from suspend or 
just locking.

  After unlocking screen cursor is invisible.

  Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7) cursor
  returns

  

  no matter if you suspend or sleep, to swap or disk when you return
  from it, the mouse cursor is missing.you can still move the mouse
  and you can see (because it highlights the window) as you move it
  around.   But the cursor is not displayed on the screen.

  i am using a lenovo W540 laptop.   I downloaded the latest beta on
  april 8 2016.

  this is xubuntu using the xfce window manager.

  the cursor does return if i log off and log back in, but that actually 
defeats the purpose of going to sleep.
  ---
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-04-08 (2 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  Package: light-locker 1.7.0-2ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/elementaryos/+bug/1568604/+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 1518813] Re: sharing panel fails to properly launch required daemons

[Romano Giannetti]

I can confirm that this bug is still here in 16.04. Under the user point
of view, is as screen sharing is simply not working ( regression from
14.04).

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

Title:
  sharing panel fails to properly launch required daemons

Status in Ubuntu GNOME:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in gnome-user-share package in Ubuntu:
  Fix Released
Status in vino package in Ubuntu:
  Fix Released

Bug description:
  This is caused by outdated gnome-user-share and vino.

  both gnome-user-share (webdav) and vino daemons fail to launch
  properly in a GNOME session via g-s-d sharing plugin

  Caused by code in the daemons, that relies on deprecated "enabled"
  keys, no longer used by g-s-d/g-c-c

  ProblemType: BugDistroRelease: Ubuntu 16.04
  Package: gnome-control-center 1:3.18.2-1ubuntu2
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.2-0ubuntu6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Nov 23 13:23:44 2015
  InstallationDate: Installed on 2012-09-23 (1156 days ago)
  InstallationMedia: Ubuntu GNOME Remix 12.10 "Quantal Quetzal" - Alpha 
amd64(20120922)SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1518813/+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 1297144] Re: [Lenovo ThinkPad X230] Invisible cursor after resume from suspend

[Romano Giannetti]

Possible a duplicate of https://bugs.launchpad.net/ubuntu/+source
/xserver-xorg-video-intel/+bug/1568604.

Check if switching to a VC (Ctrl-Alt-F1) and back (Alt-F7) fixes the
thing.

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

Title:
  [Lenovo ThinkPad X230] Invisible cursor after resume from suspend

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I am using the daily build of Xubuntu 14.04 x64 on a Lenovo Thinkpad
  x230. If I wake up the computer after it spending some time in the
  suspend state, the cursor will be invisible.  The courser still works
  (I can click on stuff and hover the invisible cursor over stuff), but
  the little arrow is not visible.  This bug showed up a few days ago
  after an update.  Putting the computer back in suspend state and
  immediately waking it back up resolves the issue until the next time
  the computer is put in suspend state for an extended period of time.

  It is possible that this bug has something to do with Whisker Menu.
  Sometimes when the courser is invisible it will still show up over
  Whisker Menu.  Most of the time it is invisible there too.

  Description: Ubuntu Trusty Tahr (development branch)
  Release: 14.04
  xfdesktop version 4.11.4, running on Xfce 4.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1297144/+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 1584457] [NEW] gsd-backlight-helper spamming the logs since upate to 16.04

[Romano Giannetti]

Public bug reported:

Since updating to 16.04 from 14.04, I have the syslog spammed by:

SEC: May 22 13:26:43 samsung-romano pkexec[21248]: gdm: Error executing command 
as another user: Not authorized [USER=root] [TTY=unknown] [CWD=/var/lib/gdm3] 
[COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 
1766]
SEC: May 22 13:26:43 samsung-romano pkexec: pam_unix(polkit-1:session): session 
opened for user root by (uid=1153)
SEC: May 22 13:26:43 samsung-romano pkexec: pam_systemd(polkit-1:session): 
Cannot create session: Already running in a session
SEC: May 22 13:26:43 samsung-romano pkexec: pam_ck_connector(polkit-1:session): 
cannot determine display-device
SEC: May 22 13:26:43 samsung-romano pkexec[21249]: romano: Executing command 
[USER=root] [TTY=unknown] [CWD=/home/romano] 
[COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 
4322]
SYS: May 22 13:26:43 samsung-romano gnome-session[1454]: Error executing 
command as another user: Not authorized
SYS: May 22 13:26:43 samsung-romano gnome-session[1454]: This incident has been 
reported.

every couple of seconds or so. There is no really need to change
brightness... how can I stop it?

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


** Tags: gnome-settings-daemon

** Tags added: gnome-settings-daemon

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

Title:
  gsd-backlight-helper spamming the logs since upate to 16.04

Status in gnome-settings-daemon package in Ubuntu:
  New

Bug description:
  Since updating to 16.04 from 14.04, I have the syslog spammed by:

  SEC: May 22 13:26:43 samsung-romano pkexec[21248]: gdm: Error executing 
command as another user: Not authorized [USER=root] [TTY=unknown] 
[CWD=/var/lib/gdm3] 
[COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 
1766]
  SEC: May 22 13:26:43 samsung-romano pkexec: pam_unix(polkit-1:session): 
session opened for user root by (uid=1153)
  SEC: May 22 13:26:43 samsung-romano pkexec: pam_systemd(polkit-1:session): 
Cannot create session: Already running in a session
  SEC: May 22 13:26:43 samsung-romano pkexec: 
pam_ck_connector(polkit-1:session): cannot determine display-device
  SEC: May 22 13:26:43 samsung-romano pkexec[21249]: romano: Executing command 
[USER=root] [TTY=unknown] [CWD=/home/romano] 
[COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 
4322]
  SYS: May 22 13:26:43 samsung-romano gnome-session[1454]: Error executing 
command as another user: Not authorized
  SYS: May 22 13:26:43 samsung-romano gnome-session[1454]: This incident has 
been reported.

  every couple of seconds or so. There is no really need to change
  brightness... how can I stop it?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1584457/+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 1438510] Re: [REGRESSION] bluetooth headset no longer supports a2dp

[Romano Giannetti]

Updated to 16.04, have the same problem. The fix in comment#5 fixes it! 
Thanks!

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

Title:
  [REGRESSION] bluetooth headset no longer supports a2dp

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in bluez source package in Vivid:
  Confirmed
Status in pulseaudio source package in Vivid:
  Confirmed

Bug description:
  Just installed 15.04 fresh from the latest ISO (beta2).

  I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems
  to have regressed in functionality.

  In 14.10, I was able to set the output profile either to a2dp or
  hsp/hfp (telephony duplex).

  In 15.04, it only works in telephony duplex mode.  I can't get high
  fidelity sound playback to work at all.

  This thread seems to be related, though the workaround within did not solve 
the problem for me:
  https://bbs.archlinux.org/viewtopic.php?id=194006

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1438510/+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 1181106] Re: Failed to change profile to Advanced Audio Distribution Profile

[Romano Giannetti]

Update: the workaround listed in
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1438510/comments/5
did work for me.

Hope this helps...

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

Title:
  Failed to change profile to Advanced Audio Distribution Profile

Status in Bluez Utilities:
  New
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in pulseaudio package in Debian:
  Fix Released

Bug description:
  I upgraded to 13.04 recently and my A2DP profile, which had been
  working great under 12.10 is suddenly gone.  Neither my blueman applet
  nor the built-in bluetooth manager applet can connect my external
  bluetooth speaker to the A2DP profile.  They can connect to the
  bluetooth device itself just fine.

  Steps I'm using:

  * using blueman, I can connect to the external bluetooth speaker and view the 
device in the devices listing
  * I can connect the device to the Audio sink and I get a message saying it is 
now connected and will "show in the PulseAudio mixer"
  * After connecting the external speaker to the audio sink, I can also see the 
device in the "Play sound through" listing in the Sound system control panel, 
but the icon has a circle with a line through it.
  * but if I right-click the device and choose "Audio Profile" from the context 
menu and try to select "High Fidelity Playback (A2DP)" as the new profile, I 
get an error message stating "failed to change profile to a2dp"

  I've already added "Enable=Socket" in /etc/bluetooth/audio.conf,
  without that I can't pair my headset. Now I can pair it, but I can't
  activate the A2DP profile.

  When I try to activate it, I see this message in my syslog :
  pulseaudio[2603]: [pulseaudio] module-bluetooth-device.c: Profile has no 
transport

  I tried the kernel 3.9.0 because of a sound problem with my soundcard,
  this kernel fixed my soundcard problem, but A2DP still doesn't work

To manage notifications about this bug go to:
https://bugs.launchpad.net/bluez/+bug/1181106/+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 1181106] Re: Failed to change profile to Advanced Audio Distribution Profile

[Romano Giannetti]

I have the same problem with Xenial, recently upgraded from Trusty. 
In Trusty my BT loudspeaker worked correctly, and now I have

module-bluez5-device.c: Refused to switch profile to a2dp_sink: Not
connected

when I try to switch to A2DP, and in HSP mode the quality is terrible.

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

Title:
  Failed to change profile to Advanced Audio Distribution Profile

Status in Bluez Utilities:
  New
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in pulseaudio package in Debian:
  Fix Released

Bug description:
  I upgraded to 13.04 recently and my A2DP profile, which had been
  working great under 12.10 is suddenly gone.  Neither my blueman applet
  nor the built-in bluetooth manager applet can connect my external
  bluetooth speaker to the A2DP profile.  They can connect to the
  bluetooth device itself just fine.

  Steps I'm using:

  * using blueman, I can connect to the external bluetooth speaker and view the 
device in the devices listing
  * I can connect the device to the Audio sink and I get a message saying it is 
now connected and will "show in the PulseAudio mixer"
  * After connecting the external speaker to the audio sink, I can also see the 
device in the "Play sound through" listing in the Sound system control panel, 
but the icon has a circle with a line through it.
  * but if I right-click the device and choose "Audio Profile" from the context 
menu and try to select "High Fidelity Playback (A2DP)" as the new profile, I 
get an error message stating "failed to change profile to a2dp"

  I've already added "Enable=Socket" in /etc/bluetooth/audio.conf,
  without that I can't pair my headset. Now I can pair it, but I can't
  activate the A2DP profile.

  When I try to activate it, I see this message in my syslog :
  pulseaudio[2603]: [pulseaudio] module-bluetooth-device.c: Profile has no 
transport

  I tried the kernel 3.9.0 because of a sound problem with my soundcard,
  this kernel fixed my soundcard problem, but A2DP still doesn't work

To manage notifications about this bug go to:
https://bugs.launchpad.net/bluez/+bug/1181106/+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 1411174] Re: "open in terminal" does not honour SSH_AUTH_SOCK and GPG_AGENT_INFO environment variables in Ubuntu 14.10

[Romano Giannetti]

@Simon:

I proposed  a workaround (ugly) in http://askubuntu.com/questions/606451
/nautilus-open-in-terminal-extension-will-not-propagate-ssh-auto-sock

A upstream report would be nice; I suspect it could be related to the fact that 
"run in terminal" is hard coded in gnome (see 
https://bugzilla.gnome.org/show_bug.cgi?id=627943 ) or not.
 


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

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

Title:
  "open in terminal" does not honour SSH_AUTH_SOCK and GPG_AGENT_INFO
  environment variables in Ubuntu 14.10

Status in gnome-terminal package in Ubuntu:
  Confirmed
Status in nautilus-open-terminal package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:

  Open a terminal in Unity via the Launcher (or Dash) and ssh into
  something. The ssh-agent unity keyring dialog will popup asking for
  the passphrase. Everything's ok.

  Now open a terminal via nautilus-open-terminal, for example right
  click on Desktop -> Open in Terminal and run env. The SSH_AUTH_SOCK
  and GPG_AGENT_INFO variables are not set. Other env vars are also
  slightly different but this might not be necessarily a problem. The
  problem is that trying to ssh somewhere cannot access the already
  running ssh-agent (unity gnome keyring), ssh will prompt in CLI for
  the passphrase.

  The expected behaviour (at least until 14.04 LTS) was that
  SSH_AUTH_SOCK and GPG_AGENT_INFO were set when opening the terminal
  via nautilus "Open in Terminal".

  
  $ lsb_release -rd
  Description:  Ubuntu 14.10
  Release:  14.10

  $ apt-cache policy nautilus-open-terminal 
  nautilus-open-terminal:
Installed: 0.20-1
Candidate: 0.20-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1411174/+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 1418217] Re: printing a scaled page not in the center

[Romano Giannetti]

If you scale down, say, to 90% a page to make it fits the printing
margins, evince fails to center it and you still have one border cut
off.

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

Title:
  printing a scaled page not in the center

Status in evince package in Ubuntu:
  Confirmed

Bug description:
  When i want to print a zoomed page i choose for example 150% scaling.
  Then i choose also the option  to center the page, but i get a part of
  the zoomed page starting from the upper-left corner. What i expect is
  the center of the zoomed page. Maybe the option to center the page is
  not working properly.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: evince 3.10.3-0ubuntu10.1
  ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
  Uname: Linux 3.13.0-45-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Feb  4 21:37:20 2015
  InstallationDate: Installed on 2014-12-09 (56 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1418217/+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 854833] Re: NM asks for Wi-Fi password every time I log in, or every minute, if "Available to all users" not checked; forgets password too

[Romano Giannetti]

New installation of 14.04.3, still happens. It happens only for
enterprise-type connection (my university and eduroam, both WPA). The
WPA personal connections (where you do not have to put an username) are
ok, remembered and automatically started.

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

Title:
  NM asks for Wi-Fi password every time I log in, or every minute, if
  "Available to all users" not checked; forgets password too

Status in gnome-keyring package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  With an up to date (as of 20 Sept) Oneiric beta, I have to re-enter the 
wireless password for all of my standard networks every time I log in. Expected 
behaviour is that Ubuntu remembers them.  This is a regression from previous 
behaviour
  --- 
  ApportVersion: 1.23-0ubuntu1
  Architecture: amd64
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 11.10
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  IpRoute:
   default via 10.45.43.1 dev eth0  proto static 
   10.45.43.0/24 dev eth0  proto kernel  scope link  src 10.45.43.13 
   10.45.43.0/24 dev wlan0  proto kernel  scope link  src 10.45.43.94 
   169.254.0.0/16 dev eth0  scope link  metric 1000
  Keyfiles: Error: [Errno 2] No such file or directory
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 0.9.0-0ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
  Tags:  oneiric running-unity
  Uname: Linux 3.0.0-11-generic x86_64
  UpgradeStatus: Upgraded to oneiric on 2011-09-07 (13 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/854833/+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 792085] Re: Automatic remount of safely removed drive

[Romano Giannetti]

FYI --- using command line to eject the disk/partiton do work, see
http://askubuntu.com/questions/422481/prevent-usb-drives-from-auto-
remounting-after-remove

On the other hand, I see surprising that this bug is marked Medium. For
non-tech-savy users, can ends in unclean disconnect and even data-loss.
Should be marked as Critical.

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

Title:
  Automatic remount of safely removed drive

Status in nautilus package in Ubuntu:
  Confirmed
Status in thunar package in Ubuntu:
  Confirmed
Status in udev package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: nautilus

  When I choose "Safely remove drive" context menu entry for an external
  USB drive within a nautilus window or directly clicking on the desktop
  icon, after about 10 seconds the drive is automatically remounted and
  a Nautilus window showing the root folder opens.

  I have noticed that similar already happened with a very old Ubuntu
  version - Bug #110589 and as that is so long time ago I thought it is
  better to open a new bug. Reason of the problem might even be
  completely different.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: nautilus 1:2.32.2.1-0ubuntu13
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic-pae 2.6.38.2
  Uname: Linux 2.6.38-8-generic-pae i686
  Architecture: i386
  Date: Thu Jun  2 23:40:08 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/792085/+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 1420698] [NEW] "use network time" is not installing ntp?

[Romano Giannetti]

Public bug reported:

I discovered that, even if I checked "use network time" in the control
panel, the package ntp was not installed (just ntpdate).

This caused a drift in time in my desktop (which is always on); after a
couple of days if I deselect the the option and select it again I have:

SYS: Feb 11 08:47:58 pern kernel: [775917.016524] systemd-timedated[14157]: Set 
NTP to disabled
SYS: Feb 11 08:47:59 pern kernel: [775918.305488] systemd-timedated[14157]: Set 
NTP to enabled
SYS: Feb 11 08:48:59 pern ntpdate[14170]: step time server 91.189.94.4 offset 
53.842810 sec
SYS: Feb 11 08:49:01 pern dovecot: imap: Warning: Time jumped forwards 53 
seconds

I solved it manually by install ntp --- but shouldn't this be
automatically done if I choose "use network time"? It doesn't seem a
"one shot" option at all --- it stays put (it is not like a button to
"read network time now" or similar).

Thanks!

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

** Attachment added: "use network time option"
   
https://bugs.launchpad.net/bugs/1420698/+attachment/4317012/+files/Selection_019.png

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

Title:
  "use network time" is not installing ntp?

Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  I discovered that, even if I checked "use network time" in the control
  panel, the package ntp was not installed (just ntpdate).

  This caused a drift in time in my desktop (which is always on); after
  a couple of days if I deselect the the option and select it again I
  have:

  SYS: Feb 11 08:47:58 pern kernel: [775917.016524] systemd-timedated[14157]: 
Set NTP to disabled
  SYS: Feb 11 08:47:59 pern kernel: [775918.305488] systemd-timedated[14157]: 
Set NTP to enabled
  SYS: Feb 11 08:48:59 pern ntpdate[14170]: step time server 91.189.94.4 offset 
53.842810 sec
  SYS: Feb 11 08:49:01 pern dovecot: imap: Warning: Time jumped forwards 53 
seconds

  I solved it manually by install ntp --- but shouldn't this be
  automatically done if I choose "use network time"? It doesn't seem a
  "one shot" option at all --- it stays put (it is not like a button to
  "read network time now" or similar).

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1420698/+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 1246272] Re: Keyboard layout changing randomly

[Romano Giannetti]

@Mekk I think that you nailed the problem in #77 (and you forgot all the
settings via XKB in xorg.conf hierarchy, and /usr/share/X11/xkb/, and
.Xmodmap, and IBus, and ).

I have the sensation (mind you --- this is not at all an accusation to
anyone; I tried to dig into it and failed) that no one has a clear idea
of how the keyboard is configured, chosen and modyfied.

I found a solution for me (no switching, defined "use system keyboard
layout" in IBus setup AND disabled IBus  --- don't ask, and defininign
my own keyboard). It's viable because I write in three langauges that
have a similar character set; but I imagine that having for example to
write in Russian and English have to be a nightmare.

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

Title:
  Keyboard layout changing randomly

Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in unity-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  Just upgraded from 12.04 (raring) to 12.10 (saucy) and keyboard layout keeps 
changing from pt_br to what I think is en_us.
  It seems random so I don't know what trigger this, but sometimes just 
alt-tabbing is enough to mess with keyboard layout in one of the windows.
  I already removed the en_us from my keyboard sources, double checked the use 
of one source for all windows, and even removed accelerators to switch between 
layouts but none have worked.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-control-center 1:3.6.3-0ubuntu44
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Wed Oct 30 09:12:48 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2013-05-20 (163 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to saucy on 2013-10-22 (8 days ago)
  usr_lib_gnome-control-center:
   activity-log-manager  0.9.7-0ubuntu4
   deja-dup  27.3.1-0ubuntu1
   gnome-control-center-datetime 13.10.0+13.10.20131016.2-0ubuntu1
   gnome-control-center-signon   0.1.7~+13.10.20130724.1-0ubuntu1
   gnome-control-center-unity1.3+13.10.20131004-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1246272/+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 1054808] Re: Default filename for screenshots is problematic

[Romano Giannetti]

Ok, now that the upstream pushed it (and added another patch for gnome-
settings-daemon at https://bugzilla.gnome.org/show_bug.cgi?id=740520 )
for 3.14, with a bit of luck it will percolate to Ubuntu Gnome in a
couple of years ;-).

My suggestion would be to simply ditch the thing and use shutter by
default.


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

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

Title:
  Default filename for screenshots is problematic

Status in Gnome Screenshot:
  Fix Released
Status in “gnome-screenshot” package in Ubuntu:
  Confirmed

Bug description:
  Press "printscreen" and you'll get a default filename of:-

  "Screenshot from -MM-DD HH:MM:SS.png"

  Fine for browsing in nautilus and double clicking on, but this format
  (specifically the colons) has been a bane for me for some time.

  1. 
  Tab completion fails:-
  -rw-rw-r--   1 alan alan  751K Sep 23 01:10 Screenshot from 2012-09-23 
01:10:33.png

  # tab completion works as far as here
  alan@deep-thought:~/Pictures$ scp Screenshot\ from\ 2012-09-2
  Screenshot\ from\ 2012-09-21\ 19\:40\:46.png 
  Screenshot\ from\ 2012-09-23\ 01\:01\:41.png 
  Screenshot\ from\ 2012-09-23\ 01\:10\:33.png 

  # get to here and it won't finish the filename off.
  alan@deep-thought:~/Pictures$ scp Screenshot\ from\ 2012-09-23\ 01\:

  2. scp fails.
  alan@deep-thought:~/Pictures$ scp Screenshot\ from\ 2012-09-23\ 
01\:10\:33.png popey.com:
  ssh: Could not resolve hostname Screenshot from 2012-09-23 01: Name or 
service not known

  3. Ubuntu one file link in thunderbird fails
  See bug 1054803

  Whilst I can see an argument for fixing the bugs in all those other
  applications, wouldn't it make more sense to just not have mad
  filenames created in the first place.

  I propose:-

  "Screenshot_from_-MM-DD_HH-MM-SS.png"

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gnome-screenshot 3.4.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28
  Uname: Linux 3.2.0-31-generic x86_64
  ApportVersion: 2.0.1-0ubuntu13
  Architecture: amd64
  Date: Sun Sep 23 01:15:27 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  SourcePackage: gnome-screenshot
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-screenshot/+bug/1054808/+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 282659] Re: evince print problems for double sided, multiple copies

[Romano Giannetti]

Just to comment, passing by, that this nice bug is still here with us.

Print the attached file and ask for two copies in a printer that default
to double-sided printer. You will have one sheet ready to trash, with
the image on the two sides.

Have a nice day,

** Attachment added: "Example .eps file"
   
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/282659/+attachment/4246894/+files/ne555-internal.eps

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

Title:
  evince print problems for double sided, multiple copies

Status in Evince document viewer:
  Confirmed
Status in “evince” package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: evince

  When I print
  * multiple copies of PDF documents
  * with odd number of pages in the document
  * in double sided format 

  Following happens:
  the back side of the last page on the first copy should be blank! but instead 
the first page of the next copy appears on it.
  No blank pages are printed ==> the documents can not be separated 
(_copy1-last page_  and _copy2-first page_  on the same paper) 

  Software:
  evince doc viewer 2.20.1
  Document Viewer.
  Using poppler 0.6 (cairo)

  Ubuntu 7.10 regularly updated
  Printer:
  Kyocera dn3900fs
  on a CUPS printer server accessed via URL: socket://xxx.xxx.xxx.xxx:9100

  ProblemType: Bug
  Architecture: amd64
  Date: Mon Oct 13 14:06:02 2008
  DistroRelease: Ubuntu 7.10
  ExecutablePath: /usr/bin/yelp
  NonfreeKernelModules: nvidia
  Package: yelp 2.20.0-0ubuntu3.1
  PackageArchitecture: amd64
  ProcCmdline: yelp
  ProcCwd: /media/sda7/home2/rgyz
  ProcEnviron:
   PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: yelp
  Uname: Linux kis1 2.6.22-15-generic #1 SMP Wed Aug 20 15:47:07 UTC 2008 
x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/evince/+bug/282659/+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 366780] Re: Please provide a mechanism whereby Wi-Fi networks can be prioritized

[Romano Giannetti]

@Marius I have exactly the same problem with the University network and
the global EDUROAM network. And no, I can't change the name of any of
them; I just want NM to connect to my local University network whenever
available, even if last time I manually connected to the global EDUROAM
--- because I was in another university campus.

Let me explain exactly the problem:

- I have a wifi account on my university network, let call it UNIWIFI. When I 
am connected to this network I can print (and more, but use that as an 
example). 
- I have an account on EDUROAM, which is broadcast on hundreds of universities, 
included mine. When I am connected with EDUROAM, I cannot print. 

Now I move between my campus and other campuses. So the last connection
could well be EDUROAM, because I was, say, attending a meeting. Or
because I entered the elevator in my campus and the UNIWIFI was lost and
by chance exiting the elevator NM was trying to connect to EDUROAM, and
succeeded.

Summary: I would like to have a way to say that if UNIWIFI is available,
NM should switch to it even if the EDUROAM is available and was
automatically connected (with automatically I mean after  a  connection
loss or reboot or wake-up). I really think that just one bit of priority
is all that is needed. Now I have to check and sometime change manually
my connection every time I have to do a privileged (like printing)
operation...

BTW, this is not a criticism of NM in general. NM is a really
outstanding tool and works perfectly, out of the box, with no help from
the user 98% of the time --- which is almost magical. Simply there are
cases where the heuristic of connection does not work; it would be
really nice if the UNIWIFI AP could send a "this network supersedes
EDUROAM" info in the broadcast, but...

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

Title:
  Please provide a mechanism whereby Wi-Fi networks can be prioritized

Status in NetworkManager:
  In Progress
Status in “network-manager” package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: network-manager

  I've got few wifi network profiles. NM connects to 1st available
  network in alphabetical order. But at my home NM connects to slow and
  unstable free network and I want to connect to my own wifi router. I
  suggest to add some priorities to different networks to set the order
  which network to connect to.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/366780/+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 1059872] Re: Error formatting disk using disk utility

[Romano Giannetti]

Tried to format an USB drive this morning with full update stable
14.04.1 Ubuntu Gnome release, using Disk utility; still no way, timeout
wiping.

Three years after, I have still to use gparted to do it (which works ok,
but you can't say it is exactly user-friendly).

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

Title:
  Error formatting disk using disk utility

Status in “udisks2” package in Ubuntu:
  Invalid
Status in “util-linux” package in Ubuntu:
  Fix Released
Status in “udisks2” source package in Trusty:
  Invalid
Status in “util-linux” source package in Trusty:
  Triaged
Status in “util-linux” package in Debian:
  Fix Released

Bug description:
  Formatting a SD card using the disk utility fails with an error
  message

  "Error formatting disk - Error synchronizing after initial wipe: Timed
  out waiting for object (udisks-error-quark, 0)"

  Steps to repro:
  Launch the disk utility
  Plug a SD card into the computer
  Select the SD card and click on the gears icon at the top right of the 
application
  From the drop down menu, select "Format Disk"
  maintain the default setting and select Format
  Acknowledge warnings
  After format process has been going for a while, the error message shown 
above pops up

  Workaround: 
  After selecting the SD card, instead of clicking the gear icon to format, 
click the partition in the "Volumes" section.
  Delete the partition ("minus" icon)
  Create a new partition

  -

  The underlying problem is that the "wipefs" tool from util-linux does
  not work any more.

  === TEST CASE ===
  $ sudo modprobe scsi_debug dev_size_mb=200
  # this creates a new /dev/sdX, usually /dev/sdb; check dmesg!

  # now create a partition table
  $ cat 

[Desktop-packages] [Bug 1246272] Re: Keyboard layout changing randomly

[Romano Giannetti]

Can anyone confirm that the workaround (setting language -> keyboard
input method to None instead of IBus) breaks the Shift-Ctrl-U method of
inputting Unicode chars?

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

Title:
  Keyboard layout changing randomly

Status in “gnome-settings-daemon” package in Ubuntu:
  Confirmed
Status in “unity-settings-daemon” package in Ubuntu:
  Confirmed

Bug description:
  Just upgraded from 12.04 (raring) to 12.10 (saucy) and keyboard layout keeps 
changing from pt_br to what I think is en_us.
  It seems random so I don't know what trigger this, but sometimes just 
alt-tabbing is enough to mess with keyboard layout in one of the windows.
  I already removed the en_us from my keyboard sources, double checked the use 
of one source for all windows, and even removed accelerators to switch between 
layouts but none have worked.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-control-center 1:3.6.3-0ubuntu44
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Wed Oct 30 09:12:48 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2013-05-20 (163 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to saucy on 2013-10-22 (8 days ago)
  usr_lib_gnome-control-center:
   activity-log-manager  0.9.7-0ubuntu4
   deja-dup  27.3.1-0ubuntu1
   gnome-control-center-datetime 13.10.0+13.10.20131016.2-0ubuntu1
   gnome-control-center-signon   0.1.7~+13.10.20130724.1-0ubuntu1
   gnome-control-center-unity1.3+13.10.20131004-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1246272/+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 295014]

[Romano Giannetti]

I haven't chacked 4.3 --- as anyone checked if this bug is still there?
Thanks!

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

Title:
  [Upstream] Cannot remove highlight from .doc in Word exported from
  Writer

Status in LibreOffice Productivity Suite:
  Confirmed
Status in The OpenOffice.org Suite:
  Confirmed
Status in “libreoffice” package in Ubuntu:
  Triaged
Status in “openoffice.org” package in Ubuntu:
  Won't Fix
Status in “libreoffice” package in Debian:
  New
Status in “libreoffice” package in Fedora:
  Unknown
Status in “libreoffice” package in openSUSE:
  Incomplete

Bug description:
  Binary package hint: openoffice.org-core

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

  2) apt-cache policy libreoffice-writer
  libreoffice-writer:
    Installed: 1:3.3.3-1ubuntu2
    Candidate: 1:3.3.3-1ubuntu2
    Version table:
   *** 1:3.3.3-1ubuntu2 0
  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

  3) What is expected to happen in documented exported from Writer
  opened in Word via the Terminal:

  cd ~/Desktop && wget
  
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/295014/+attachment/410599/+files/test_highlight.doc
  && wine ~/.wine/drive_c/Program\ Files/Microsoft\
  Office/OFFICE11/WINWORD.EXE test_highlight.doc

  click the Highlight button -> No Fill and the highlight is removed.

  4) What happens instead is the highlight is not removed.

  WORKAROUND: In Word click Format -> Boarders and Shading... -> Shading
  tab -> click No Fill button -> under Preview change drop down Apply
  to: text -> OK button

  WORKAROUND: Use AbiWord to export documents with highlighting.

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/295014/+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 1054808] Re: Default filename for screenshots is problematic

[Romano Giannetti]

The problem with ISO8601 is that it uses colons ":" to separate hours, minutes 
and seconds; although ":" are a perfectly valid character for the Unix 
filesystem, they are not accepted in Windows. So you can't put the screenshot 
on a NTFS filesystem nor on a shared filesystem (say, Dropbox) with a Windows 
system. 
The fastest solution to this bug is to switch to shutter, BTW.

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

Title:
  Default filename for screenshots is problematic

Status in Gnome Screenshot:
  New
Status in “gnome-screenshot” package in Ubuntu:
  Confirmed

Bug description:
  Press "printscreen" and you'll get a default filename of:-

  "Screenshot from -MM-DD HH:MM:SS.png"

  Fine for browsing in nautilus and double clicking on, but this format
  (specifically the colons) has been a bane for me for some time.

  1. 
  Tab completion fails:-
  -rw-rw-r--   1 alan alan  751K Sep 23 01:10 Screenshot from 2012-09-23 
01:10:33.png

  # tab completion works as far as here
  alan@deep-thought:~/Pictures$ scp Screenshot\ from\ 2012-09-2
  Screenshot\ from\ 2012-09-21\ 19\:40\:46.png 
  Screenshot\ from\ 2012-09-23\ 01\:01\:41.png 
  Screenshot\ from\ 2012-09-23\ 01\:10\:33.png 

  # get to here and it won't finish the filename off.
  alan@deep-thought:~/Pictures$ scp Screenshot\ from\ 2012-09-23\ 01\:

  2. scp fails.
  alan@deep-thought:~/Pictures$ scp Screenshot\ from\ 2012-09-23\ 
01\:10\:33.png popey.com:
  ssh: Could not resolve hostname Screenshot from 2012-09-23 01: Name or 
service not known

  3. Ubuntu one file link in thunderbird fails
  See bug 1054803

  Whilst I can see an argument for fixing the bugs in all those other
  applications, wouldn't it make more sense to just not have mad
  filenames created in the first place.

  I propose:-

  "Screenshot_from_-MM-DD_HH-MM-SS.png"

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gnome-screenshot 3.4.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28
  Uname: Linux 3.2.0-31-generic x86_64
  ApportVersion: 2.0.1-0ubuntu13
  Architecture: amd64
  Date: Sun Sep 23 01:15:27 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  SourcePackage: gnome-screenshot
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-screenshot/+bug/1054808/+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 366780] Re: Please provide a mechanism whereby Wi-Fi networks can be prioritized

[Romano Giannetti]

The thing could be solved with just one bit of "priority" thing. I
already commented to the upstream bug
https://bugzilla.gnome.org/show_bug.cgi?id=359556 and had no answers.

I imagine that using the NM scripts dispatcher you can implement some 
workaround, though: 
http://askubuntu.com/questions/436943/how-to-run-a-script-when-there-is-a-change-in-your-local-ip
 
 

** Also affects: network-manager via
   https://bugzilla.gnome.org/show_bug.cgi?id=359556
   Importance: Unknown
   Status: Unknown

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

Title:
  Please provide a mechanism whereby Wi-Fi networks can be prioritized

Status in NetworkManager:
  Unknown
Status in “network-manager” package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: network-manager

  I've got few wifi network profiles. NM connects to 1st available
  network in alphabetical order. But at my home NM connects to slow and
  unstable free network and I want to connect to my own wifi router. I
  suggest to add some priorities to different networks to set the order
  which network to connect to.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/366780/+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 1241811] Re: USB disk not automatically mounted after upgrade to 13.10

[Romano Giannetti]

I can confirm that when it happened to me, I had gdm as login manager
and not lightdm.

Since the upgrade to 14.04, it happened just one time in one laptop
(solved by login/logout) with Ubuntu Gnome, and never in my other laptop
which has Xubuntu.

So for me it is happening now very rarely; last time I seen it was more
than a month ago --- I can't remember. My guess is that the DBUS
connection between udidskd and the desktop get lost, or stuck. Probably
related to the DM, yes. Would not be surprising if lightdm and gdm share
some bug.

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

Title:
  USB disk not automatically mounted after upgrade to 13.10

Status in GVFS:
  New
Status in Light Display Manager:
  New
Status in Ubuntu GNOME:
  New
Status in “gvfs” package in Ubuntu:
  Confirmed
Status in “nautilus-udisks” package in Ubuntu:
  Invalid

Bug description:
  Since the upgrade to 13.10, my laptop stopped mounting the USB devices
  (and SD cards too) automatically.

  Inserting the USB I have in the log:

  SYS: Oct 18 13:57:38 samsung-romano kernel: [  167.570340] usb 3-2: new 
high-speed USB device number 3 using xhci_hcd
  SYS: Oct 18 13:57:38 samsung-romano kernel: [  167.593170] usb 3-2: New USB 
device found, idVendor=090c, idProduct=1000
  SYS: Oct 18 13:57:38 samsung-romano kernel: [  167.593181] usb 3-2: New USB 
device strings: Mfr=1, Product=2, SerialNumber=3
  SYS: Oct 18 13:57:38 samsung-romano kernel: [  167.593187] usb 3-2: Product: 
Flash Disk
  SYS: Oct 18 13:57:38 samsung-romano kernel: [  167.593192] usb 3-2: 
Manufacturer: USB
  SYS: Oct 18 13:57:38 samsung-romano kernel: [  167.593196] usb 3-2: 
SerialNumber: FBF1009232400790
  SYS: Oct 18 13:57:38 samsung-romano kernel: [  167.593492] usb 3-2: ep 0x81 - 
rounding interval to 128 microframes, ep desc says 255 microframes
  SYS: Oct 18 13:57:38 samsung-romano kernel: [  167.593501] usb 3-2: ep 0x2 - 
rounding interval to 128 microframes, ep desc says 255 microframes
  SYS: Oct 18 13:57:38 samsung-romano kernel: [  167.595232] scsi7 : 
usb-storage 3-2:1.0
  SYS: Oct 18 13:57:38 samsung-romano mtp-probe: checking bus 3, device 3: 
"/sys/devices/pci:00/:00:1c.4/:04:00.0/usb3/3-2"
  SYS: Oct 18 13:57:38 samsung-romano mtp-probe: bus: 3, device: 3 was not an 
MTP device
  SYS: Oct 18 13:57:39 samsung-romano kernel: [  168.834382] scsi 7:0:0:0: 
Direct-Access USB  Flash Disk   1100 PQ: 0 ANSI: 0 CCS
  SYS: Oct 18 13:57:39 samsung-romano kernel: [  168.835894] sd 7:0:0:0: 
Attached scsi generic sg3 type 0
  SYS: Oct 18 13:57:39 samsung-romano kernel: [  168.836227] sd 7:0:0:0: [sdc] 
3915776 512-byte logical blocks: (2.00 GB/1.86 GiB)
  SYS: Oct 18 13:57:39 samsung-romano kernel: [  168.836910] sd 7:0:0:0: [sdc] 
Write Protect is off
  SYS: Oct 18 13:57:39 samsung-romano kernel: [  168.836926] sd 7:0:0:0: [sdc] 
Mode Sense: 43 00 00 00
  SYS: Oct 18 13:57:39 samsung-romano kernel: [  168.837665] sd 7:0:0:0: [sdc] 
No Caching mode page present
  SYS: Oct 18 13:57:39 samsung-romano kernel: [  168.837676] sd 7:0:0:0: [sdc] 
Assuming drive cache: write through
  SYS: Oct 18 13:57:39 samsung-romano kernel: [  168.843552] sd 7:0:0:0: [sdc] 
No Caching mode page present
  SYS: Oct 18 13:57:39 samsung-romano kernel: [  168.843562] sd 7:0:0:0: [sdc] 
Assuming drive cache: write through
  SYS: Oct 18 13:57:39 samsung-romano kernel: [  168.844609]  sdc: sdc1
  SYS: Oct 18 13:57:39 samsung-romano kernel: [  168.846982] sd 7:0:0:0: [sdc] 
No Caching mode page present
  SYS: Oct 18 13:57:39 samsung-romano kernel: [  168.846990] sd 7:0:0:0: [sdc] 
Assuming drive cache: write through
  SYS: Oct 18 13:57:39 samsung-romano kernel: [  168.846997] sd 7:0:0:0: [sdc] 
Attached SCSI removable disk

  But after that nothing happens. I checked the dconf variables as per
  https://help.ubuntu.com/community/Mount/USB but it's all correctly
  set. I can mount the disk by hand:

  % sudo mount /dev/sdc1 /mnt
  % mount | grep mnt
  /dev/sdc1 on /mnt type vfat (rw)

  ...and it works ok.

  Add: using from command line udisks works, too:

  (0)samsung-romano:~% udisks --mount /dev/sdc1
  Mounted /org/freedesktop/UDisks/devices/sdc1 at /media/PENDRIVE

To manage notifications about this bug go to:
https://bugs.launchpad.net/gvfs/+bug/1241811/+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 381017]

[Romano Giannetti]

If I can chime in with a comment to the developers (if anyone is
listening here): I am used to never use drag and drop of attachment on
TB now, given the really broken behavior.

Suggestion: ditch the thing completely. Remove drag and drop. For good.

It's so broken it is more a danger(1) than any other thing, and it is
not so necessary in the end, you can live with "save as..." and company.
I suppose that a bug like that not fixed in 7 years means it's too
complex to fix; let's accept it and move on. Leaving an half-baked
functionality is much worse than not having it.


(1) because sometime it *seems* to work; it creates an icon from which
the content is not accesible at all, and can lead to data loss for
unsuspecting users.

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

Title:
  Cannot drag attachment from mail attachment pane to desktop

Status in One Hundred Papercuts:
  Triaged
Status in SeaMonkey: all-in-one Internet application suite:
  Confirmed
Status in Mozilla Thunderbird Mail and News:
  Confirmed
Status in “thunderbird” package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 9.04
  Gnome Desktop 2.26.1
  Thunderbird 2.0.0.21

  This is regression introduced  in Jaunty as it works in Intrepid.
  Dragging an attachment from the attachment pane to the desktop give
  the following error:

  ==
  Error while copying
  There was an error getting information about "fetch>UID>.voicemail>1784".

  The specified location is not supported
  ==

  Mail account is IMAP. This error was shown to seb128 and asac. The
  expected behavior is that the file is copied to the destination onto
  which it is dragged.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/381017/+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 1246272] Re: Keyboard layout changing randomly

[Romano Giannetti]

*** This bug is a duplicate of bug 1240198 ***
https://bugs.launchpad.net/bugs/1240198

The all time record being probably bug #295014, with us since 2004 in
its first incarnation... But well, we have to remember that most
developers works on this in their free time, so... There should be a
pledge system for fixing bugs, I for one have a couple of them where I
wouldn't mind to pay to see them fixed.

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

Title:
  Keyboard layout changing randomly

Status in “gnome-settings-daemon” package in Ubuntu:
  Confirmed
Status in “unity-settings-daemon” package in Ubuntu:
  Confirmed

Bug description:
  Just upgraded from 12.04 (raring) to 12.10 (saucy) and keyboard layout keeps 
changing from pt_br to what I think is en_us.
  It seems random so I don't know what trigger this, but sometimes just 
alt-tabbing is enough to mess with keyboard layout in one of the windows.
  I already removed the en_us from my keyboard sources, double checked the use 
of one source for all windows, and even removed accelerators to switch between 
layouts but none have worked.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-control-center 1:3.6.3-0ubuntu44
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Wed Oct 30 09:12:48 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2013-05-20 (163 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to saucy on 2013-10-22 (8 days ago)
  usr_lib_gnome-control-center:
   activity-log-manager  0.9.7-0ubuntu4
   deja-dup  27.3.1-0ubuntu1
   gnome-control-center-datetime 13.10.0+13.10.20131016.2-0ubuntu1
   gnome-control-center-signon   0.1.7~+13.10.20130724.1-0ubuntu1
   gnome-control-center-unity1.3+13.10.20131004-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1246272/+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 1246272] Re: Keyboard layout changing randomly

[Romano Giannetti]

I want to underline that my comment was not *at all* a critic to
developers. There is something pesky going on with keyboards, and
difficult to spot (although I suspect some kind of bad interaction
between {unity,gnome}-control-settings and ibus). The monster bug
#1218322 would have been fixed otherwise, it's one of the hottest bug of
all launchpad. Simply I think that marking this bug low is understating
its importance --- Ubuntu should work all over the planet.

As a data point, I switched my laptop which sports a Spanish keyboard to
Xubuntu (not for this bug, just a matter of usability and too few RAM),
disable system keyboard configuration, no IBUS,  and never had a problem
with the keyboard. Which points to the direction above... from a layman
point-of-view.

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

Title:
  Keyboard layout changing randomly

Status in “gnome-settings-daemon” package in Ubuntu:
  Confirmed
Status in “unity-settings-daemon” package in Ubuntu:
  Confirmed

Bug description:
  Just upgraded from 12.04 (raring) to 12.10 (saucy) and keyboard layout keeps 
changing from pt_br to what I think is en_us.
  It seems random so I don't know what trigger this, but sometimes just 
alt-tabbing is enough to mess with keyboard layout in one of the windows.
  I already removed the en_us from my keyboard sources, double checked the use 
of one source for all windows, and even removed accelerators to switch between 
layouts but none have worked.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-control-center 1:3.6.3-0ubuntu44
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Wed Oct 30 09:12:48 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2013-05-20 (163 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to saucy on 2013-10-22 (8 days ago)
  usr_lib_gnome-control-center:
   activity-log-manager  0.9.7-0ubuntu4
   deja-dup  27.3.1-0ubuntu1
   gnome-control-center-datetime 13.10.0+13.10.20131016.2-0ubuntu1
   gnome-control-center-signon   0.1.7~+13.10.20130724.1-0ubuntu1
   gnome-control-center-unity1.3+13.10.20131004-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1246272/+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 1246272] Re: Keyboard layout changing randomly

[Romano Giannetti]

@Alberto Low? Really?

Since 13.10, between this and https://bugs.launchpad.net/ubuntu/+source
/gnome-settings-daemon/+bug/1218322 Ubuntu has become a PITA if you have
to write in more than one language (and even with just one, if that one
is not en_US).

Your call, but I think this is _at least_ high.

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

Title:
  Keyboard layout changing randomly

Status in “gnome-settings-daemon” package in Ubuntu:
  Confirmed
Status in “unity-settings-daemon” package in Ubuntu:
  Confirmed

Bug description:
  Just upgraded from 12.04 (raring) to 12.10 (saucy) and keyboard layout keeps 
changing from pt_br to what I think is en_us.
  It seems random so I don't know what trigger this, but sometimes just 
alt-tabbing is enough to mess with keyboard layout in one of the windows.
  I already removed the en_us from my keyboard sources, double checked the use 
of one source for all windows, and even removed accelerators to switch between 
layouts but none have worked.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-control-center 1:3.6.3-0ubuntu44
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Wed Oct 30 09:12:48 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2013-05-20 (163 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to saucy on 2013-10-22 (8 days ago)
  usr_lib_gnome-control-center:
   activity-log-manager  0.9.7-0ubuntu4
   deja-dup  27.3.1-0ubuntu1
   gnome-control-center-datetime 13.10.0+13.10.20131016.2-0ubuntu1
   gnome-control-center-signon   0.1.7~+13.10.20130724.1-0ubuntu1
   gnome-control-center-unity1.3+13.10.20131004-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1246272/+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 1215798] Re: losing windows on Ubuntu 13.10

[Romano Giannetti]

Christian Persch [gnome-terminal developer] said on 2014-05-16 17:49:52
UTC, in the upstream bug:

"An essential component in your reproducer is restarting gnome-shell.
Gnome-terminal used to unrealise and re-realise all windows in this case; that
was removed from 3.8. So I think this is fixed in gnome-terminal >= 3.8. If you
do upgrade in the future and can still reproduce this then, please do reopen
the bug; marking OBSOLETE for now."

Sounds reasonable. Could be Remmina doing something similar?


** Also affects: gnome-shell via
   https://bugzilla.gnome.org/show_bug.cgi?id=730261
   Importance: Unknown
   Status: Unknown

** No longer affects: gnome-shell

** Also affects: gnome-terminal via
   https://bugzilla.gnome.org/show_bug.cgi?id=730261
   Importance: Unknown
   Status: Unknown

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

Title:
  losing windows on Ubuntu 13.10

Status in GNOME Terminal:
  Unknown
Status in “gnome-shell” package in Ubuntu:
  Confirmed
Status in “gnome-terminal” package in Ubuntu:
  New

Bug description:
  I found, that gnome-shell lose some windows.

  I see it in two ways:

  1. gnome-terminal: after a restart - with ALT+F2 -> r or kill -HUP
  $(pgrep gnome-shell|head -n1) or resume from suspend - a terminal
  windows can not be opened any more, but is listed in ALT+TAB list (I
  add a video)

  2. remmina: I opened a connection and sometimes the window is just not
  to see any more - also not in ALT+TAB. But it must there, when I open
  a new connection in a other group I get a new window. When I open a
  new connection in the same group as the lost windows (it get normally
  attached as a new tab to the window) it get a connect to the server,
  but not the window. I can see on the terminal server and netstat, that
  the connection is established.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-shell 3.8.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-3.7-generic 3.11.0-rc6
  Uname: Linux 3.11.0-3-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.1-0ubuntu2
  Architecture: amd64
  Date: Fri Aug 23 09:26:56 2013
  DisplayManager: gdm
  GsettingsChanges:
   b'org.gnome.desktop.interface' b'buttons-have-icons' b'true'
   b'org.gnome.desktop.interface' b'gtk-theme' b"'04-Crunchy-grey'"
   b'org.gnome.desktop.interface' b'menus-have-icons' b'true'
  InstallationDate: Installed on 2013-08-19 (3 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Alpha amd64 
(20130724)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-terminal/+bug/1215798/+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 1215798] Re: losing windows on Ubuntu 13.10

[Romano Giannetti]

Tried to report upstream
https://bugzilla.gnome.org/show_bug.cgi?id=730261

Temporary solution: install terminator.


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

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

Title:
  losing windows on Ubuntu 13.10

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

Bug description:
  I found, that gnome-shell lose some windows.

  I see it in two ways:

  1. gnome-terminal: after a restart - with ALT+F2 -> r or kill -HUP
  $(pgrep gnome-shell|head -n1) or resume from suspend - a terminal
  windows can not be opened any more, but is listed in ALT+TAB list (I
  add a video)

  2. remmina: I opened a connection and sometimes the window is just not
  to see any more - also not in ALT+TAB. But it must there, when I open
  a new connection in a other group I get a new window. When I open a
  new connection in the same group as the lost windows (it get normally
  attached as a new tab to the window) it get a connect to the server,
  but not the window. I can see on the terminal server and netstat, that
  the connection is established.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-shell 3.8.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-3.7-generic 3.11.0-rc6
  Uname: Linux 3.11.0-3-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.1-0ubuntu2
  Architecture: amd64
  Date: Fri Aug 23 09:26:56 2013
  DisplayManager: gdm
  GsettingsChanges:
   b'org.gnome.desktop.interface' b'buttons-have-icons' b'true'
   b'org.gnome.desktop.interface' b'gtk-theme' b"'04-Crunchy-grey'"
   b'org.gnome.desktop.interface' b'menus-have-icons' b'true'
  InstallationDate: Installed on 2013-08-19 (3 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Alpha amd64 
(20130724)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  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/1215798/+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 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.

[Romano Giannetti]

Could be this: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-
daemon/+bug/1246272 (and maybe this:
https://bugzilla.gnome.org/show_bug.cgi?id=729423 ) related too?

Seeing the workaround in http://askubuntu.com/questions/459617/keyboard-
layout-isnt-kept-upon-reboot I have a feeling that we could have the
normal `xsetkeyb` and IBUS fighting?


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

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

Title:
  Can't set keyboard layout change to alt+shift, ctrl+shift, etc.

Status in Gnome Settings Daemon:
  Invalid
Status in Ubuntu GNOME:
  Confirmed
Status in “gnome-control-center” package in Ubuntu:
  Fix Released
Status in “gnome-settings-daemon” package in Ubuntu:
  Triaged
Status in “gnome-settings-daemon” source package in Saucy:
  Triaged
Status in “gnome-control-center” package in ALT Linux:
  Unknown
Status in “gnome-control-center” package in Baltix:
  Confirmed
Status in “gnome-control-center” package in Fedora:
  Unknown
Status in “gnome-control-center” package in Gentoo Linux:
  Invalid
Status in “gnome-control-center” package in Mandriva:
  Invalid

Bug description:
  ***
  The old PPA, ppa:attente/1218322 is superceded by the following one. You can 
remove the old repository using ppa-purge.
  ***

  A PPA which should provide some relief for this issue is available at
  https://launchpad.net/~attente/+archive/modifier-only-input-switch. To
  install:

  sudo add-apt-repository ppa:attente/modifier-only-input-switch
  sudo apt-get update
  sudo apt-get upgrade
  (log out, log in)

  If the packages improve the situation for you, you can pin them using:

  sudo apt-mark hold compiz
  sudo apt-mark hold gnome-settings-daemon
  sudo apt-mark hold unity

  If the packages don't work for you, you can purge them using:

  sudo ppa-purge ppa:attente/modifier-only-input-switch

  === compiz ===

  Impact: modifier-only key bindings need to be independent of key-press
  order, there's no support for double tapping two modifier keys of the
  same type

  Test case:
  - add at least two input sources through gnome-control-center's text entry 
settings
  - use gsettings to set the input switching shortcut to ctrl+left shift: 
gsettings set org.gnome.desktop.wm.keybindings switch-input-source 
"['Shift_L']"
  - holding left shift, press and release ctrl
  -> the current input source should change

  Regression potential: possible, but highly unlikely, that some key
  bindings may be triggered due to the removal of some code that would
  normally prevent a possible tap from occurring.

  === unity ===

  Impact: gnome-settings-daemon eats modifier-only shortcuts preventing
  them from propagating down to applications

  Test case:
  - open gnome-control-center's text input settings
  - set the next input source key binding to ctrl+left shift
  - open gnome-terminal
  - press ctrl+shift+t
  -> gnome-terminal should open a new tab

  Regression potential: the additional input switch key bindings could
  collide with other functionality such as opening the dash or hud

  === gnome-control-center ===

  Impact: the UI to change the layout switching keys doesn't work

  Test case:
  - open gnome-control-center's text input settings
  - click on the "next layout key" entry
  - try entering a key combinaison (e.g ctrl-space)
  -> the UI should reflect the new keys

  Regression potential: that UI was not working before, it should only
  be an improvement (some key combos are not working as expected, that's
  another issue and shouldn't be mixed with this one)

  === gnome-settings-daemon ===

  Impact: attempting to change keyboard layouts using only modifier keys
  doesn't work

  Test case:
  - add at least two input sources through gnome-control-center's text entry 
settings
  - use gsettings to set the input switching shortcut to ctrl+left shift: 
gsettings set org.gnome.desktop.wm.keybindings switch-input-source 
"['Shift_L']"
  - press and release ctrl+left shift
  -> the current input source should change

  Regression potential: The input switching shortcut might capture other
  non-modifier shortcuts, but users will need to consider this when
  choosing their switching shortcut anyways. For users this bug affects,
  this represents a working solution for a critical bug.

  --

  Test results for different keyboard layout change hotkeys may be
  viewed and added in the Google Docs table, created by Norbert
  
(https://docs.google.com/spreadsheet/ccc?key=0Ao5e713Ig9g_dEJrX2NRYlpLWWVzSWxsVXU4ck9HYVE&usp=sharing).

  --
  Recent discovered bugs related to keyboard layouts:
     * keyboard layout settings must be consistent between gnome-control-center 
keyboard, indicator-keyboard and gnome-tweak-tool and /etc/default/keyboard 
(bug 12705

[Desktop-packages] [Bug 1246272] Re: Keyboard layout changing randomly

[Romano Giannetti]

There is a possible workaround here:
http://askubuntu.com/questions/459617/keyboard-layout-isnt-kept-upon-
reboot

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

Title:
  Keyboard layout changing randomly

Status in “gnome-settings-daemon” package in Ubuntu:
  Confirmed
Status in “unity-settings-daemon” package in Ubuntu:
  Confirmed

Bug description:
  Just upgraded from 12.04 (raring) to 12.10 (saucy) and keyboard layout keeps 
changing from pt_br to what I think is en_us.
  It seems random so I don't know what trigger this, but sometimes just 
alt-tabbing is enough to mess with keyboard layout in one of the windows.
  I already removed the en_us from my keyboard sources, double checked the use 
of one source for all windows, and even removed accelerators to switch between 
layouts but none have worked.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-control-center 1:3.6.3-0ubuntu44
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Wed Oct 30 09:12:48 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2013-05-20 (163 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to saucy on 2013-10-22 (8 days ago)
  usr_lib_gnome-control-center:
   activity-log-manager  0.9.7-0ubuntu4
   deja-dup  27.3.1-0ubuntu1
   gnome-control-center-datetime 13.10.0+13.10.20131016.2-0ubuntu1
   gnome-control-center-signon   0.1.7~+13.10.20130724.1-0ubuntu1
   gnome-control-center-unity1.3+13.10.20131004-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1246272/+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 1246272] Re: Keyboard layout changing randomly

[Romano Giannetti]

Could be this the upstream report?

https://bugzilla.gnome.org/show_bug.cgi?id=729423

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

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

Title:
  Keyboard layout changing randomly

Status in “gnome-settings-daemon” package in Ubuntu:
  Confirmed
Status in “unity-settings-daemon” package in Ubuntu:
  Confirmed

Bug description:
  Just upgraded from 12.04 (raring) to 12.10 (saucy) and keyboard layout keeps 
changing from pt_br to what I think is en_us.
  It seems random so I don't know what trigger this, but sometimes just 
alt-tabbing is enough to mess with keyboard layout in one of the windows.
  I already removed the en_us from my keyboard sources, double checked the use 
of one source for all windows, and even removed accelerators to switch between 
layouts but none have worked.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-control-center 1:3.6.3-0ubuntu44
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Wed Oct 30 09:12:48 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2013-05-20 (163 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to saucy on 2013-10-22 (8 days ago)
  usr_lib_gnome-control-center:
   activity-log-manager  0.9.7-0ubuntu4
   deja-dup  27.3.1-0ubuntu1
   gnome-control-center-datetime 13.10.0+13.10.20131016.2-0ubuntu1
   gnome-control-center-signon   0.1.7~+13.10.20130724.1-0ubuntu1
   gnome-control-center-unity1.3+13.10.20131004-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1246272/+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 295014]

[Romano Giannetti]

@Björn --- you are right, sorry.

To add something constructive, I mention I have a workaround if the file
is sufficiently simple to be able to save it in RTF:

1) save the file in RTF format 
2) open it with a text editor (vi, gedit) 
3) substitute all occurrences of 

"\chshdng0\chcfpat0\chcbpat7"

   to

 "\highlight7"

4) Save it.

Now Word is (usually) able to edit the highlight in the file. I tested
it only with simple files --- so YMMV.

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

Title:
  [Upstream] Cannot remove highlight from .doc in Word exported from
  Writer

Status in LibreOffice Productivity Suite:
  Confirmed
Status in The OpenOffice.org Suite:
  Confirmed
Status in “libreoffice” package in Ubuntu:
  Triaged
Status in “openoffice.org” package in Ubuntu:
  Won't Fix
Status in “libreoffice” package in Debian:
  New
Status in “libreoffice” package in Fedora:
  Unknown
Status in “libreoffice” package in openSUSE:
  Incomplete

Bug description:
  Binary package hint: openoffice.org-core

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

  2) apt-cache policy libreoffice-writer
  libreoffice-writer:
    Installed: 1:3.3.3-1ubuntu2
    Candidate: 1:3.3.3-1ubuntu2
    Version table:
   *** 1:3.3.3-1ubuntu2 0
  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

  3) What is expected to happen in documented exported from Writer
  opened in Word via the Terminal:

  cd ~/Desktop && wget
  
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/295014/+attachment/410599/+files/test_highlight.doc
  && wine ~/.wine/drive_c/Program\ Files/Microsoft\
  Office/OFFICE11/WINWORD.EXE test_highlight.doc

  click the Highlight button -> No Fill and the highlight is removed.

  4) What happens instead is the highlight is not removed.

  WORKAROUND: In Word click Format -> Boarders and Shading... -> Shading
  tab -> click No Fill button -> under Preview change drop down Apply
  to: text -> OK button

  WORKAROUND: Use AbiWord to export documents with highlighting.

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/295014/+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 295014]

[Romano Giannetti]

We are near to 4.3 release, and this bug is here (or in OO.org or in
various incarnations of the suite) since 2004.

The only thing that happens is that it is marked as a "must have" for
the current version, and never taken care of.

Could a developer comment if this is really impossible to fix? I can
understand that if the internal data representation is completely
different, this thing could be impossible to fix.

It is a show-stopper for LO in my workplace --- I *have* to be able to
interact with MS word and this highlight problem breaks even the
simplest document.

To support the claim that it is a 10-years-old bug:
https://issues.apache.org/ooo/show_bug.cgi?id=24317

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

Title:
  [Upstream] Cannot remove highlight from .doc in Word exported from
  Writer

Status in LibreOffice Productivity Suite:
  Confirmed
Status in The OpenOffice.org Suite:
  Confirmed
Status in “libreoffice” package in Ubuntu:
  Triaged
Status in “openoffice.org” package in Ubuntu:
  Won't Fix
Status in “libreoffice” package in Debian:
  New
Status in “libreoffice” package in Fedora:
  Unknown
Status in “libreoffice” package in openSUSE:
  Incomplete

Bug description:
  Binary package hint: openoffice.org-core

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

  2) apt-cache policy libreoffice-writer
  libreoffice-writer:
    Installed: 1:3.3.3-1ubuntu2
    Candidate: 1:3.3.3-1ubuntu2
    Version table:
   *** 1:3.3.3-1ubuntu2 0
  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

  3) What is expected to happen in documented exported from Writer
  opened in Word via the Terminal:

  cd ~/Desktop && wget
  
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/295014/+attachment/410599/+files/test_highlight.doc
  && wine ~/.wine/drive_c/Program\ Files/Microsoft\
  Office/OFFICE11/WINWORD.EXE test_highlight.doc

  click the Highlight button -> No Fill and the highlight is removed.

  4) What happens instead is the highlight is not removed.

  WORKAROUND: In Word click Format -> Boarders and Shading... -> Shading
  tab -> click No Fill button -> under Preview change drop down Apply
  to: text -> OK button

  WORKAROUND: Use AbiWord to export documents with highlighting.

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/295014/+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 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.

[Romano Giannetti]

@William: I tested the PPA. Remeber, Ubuntu Gnome 14.04; I have just two
keyboard layouts (if you want I can check with three to).

With the PPA:

1. switching to next source works ok if I choose a normal key combo, for
example, Super+Space. On pressing the combo, the layout switches, the
indicator is synchronized, and I have a nice OSD display indicting the
switch.  I cannot set this option with modifiers only keys, as expected.

2. Setting  "Modifiers only switch to next source" to Alt+Shift does not
work. Nothing, no OSD, no switch in the indicator, no switch of layout.

3. Checking more, I discovered that  setting "Modifiers only switch to
next source" to for example Right-Ctrl + Right Shift or Compose *do*
work, and the indicator follow the switch, but there is no OSD display
about the switch. Also Left-Alt + Left-shift works, albeit without OSD
display.

So basically the combination that doesn't work for me are the ones with
plain Alt of Right-Alt involved. Could be because the Right Alt is
mapped to AltGr?

In summary, it's clearly a step in the correct direction. Any idea about
the OSD display not showing?

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

Title:
  Can't set keyboard layout change to alt+shift, ctrl+shift, etc.

Status in Gnome Settings Daemon:
  Invalid
Status in Ubuntu GNOME:
  Confirmed
Status in “gnome-control-center” package in Ubuntu:
  Fix Released
Status in “gnome-settings-daemon” package in Ubuntu:
  Triaged
Status in “gnome-settings-daemon” source package in Saucy:
  Triaged
Status in “gnome-control-center” package in ALT Linux:
  Unknown
Status in “gnome-control-center” package in Baltix:
  Confirmed
Status in “gnome-control-center” package in Fedora:
  Unknown
Status in “gnome-control-center” package in Gentoo Linux:
  Invalid
Status in “gnome-control-center” package in Mandriva:
  Invalid

Bug description:
  ***
  The old PPA, ppa:attente/1218322 is superceded by the following one. You can 
remove the old repository using ppa-purge.
  ***

  A PPA which should provide some relief for this issue is available at
  https://launchpad.net/~attente/+archive/modifier-only-input-switch. To
  install:

  sudo add-apt-repository ppa:attente/modifier-only-input-switch
  sudo apt-get update
  sudo apt-get upgrade
  (log out, log in)

  If the packages improve the situation for you, you can pin them using:

  sudo apt-mark hold compiz
  sudo apt-mark hold gnome-settings-daemon
  sudo apt-mark hold unity

  If the packages don't work for you, you can purge them using:

  sudo ppa-purge ppa:attente/modifier-only-input-switch

  === compiz ===

  Impact: modifier-only key bindings need to be independent of key-press
  order, there's no support for double tapping two modifier keys of the
  same type

  Test case:
  - add at least two input sources through gnome-control-center's text entry 
settings
  - use gsettings to set the input switching shortcut to ctrl+left shift: 
gsettings set org.gnome.desktop.wm.keybindings switch-input-source 
"['Shift_L']"
  - holding left shift, press and release ctrl
  -> the current input source should change

  Regression potential: possible, but highly unlikely, that some key
  bindings may be triggered due to the removal of some code that would
  normally prevent a possible tap from occurring.

  === unity ===

  Impact: gnome-settings-daemon eats modifier-only shortcuts preventing
  them from propagating down to applications

  Test case:
  - open gnome-control-center's text input settings
  - set the next input source key binding to ctrl+left shift
  - open gnome-terminal
  - press ctrl+shift+t
  -> gnome-terminal should open a new tab

  Regression potential: the additional input switch key bindings could
  collide with other functionality such as opening the dash or hud

  === gnome-control-center ===

  Impact: the UI to change the layout switching keys doesn't work

  Test case:
  - open gnome-control-center's text input settings
  - click on the "next layout key" entry
  - try entering a key combinaison (e.g ctrl-space)
  -> the UI should reflect the new keys

  Regression potential: that UI was not working before, it should only
  be an improvement (some key combos are not working as expected, that's
  another issue and shouldn't be mixed with this one)

  === gnome-settings-daemon ===

  Impact: attempting to change keyboard layouts using only modifier keys
  doesn't work

  Test case:
  - add at least two input sources through gnome-control-center's text entry 
settings
  - use gsettings to set the input switching shortcut to ctrl+left shift: 
gsettings set org.gnome.desktop.wm.keybindings switch-input-source 
"['Shift_L']"
  - press and release ctrl+left shift
  -> the current input source should change

  Regression potential: The input switching shortcut might capture other
  non-modifier shortcuts, but users

[Desktop-packages] [Bug 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.

[Romano Giannetti]

@William --- will try again this afternoon; sorry for the delay.

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

Title:
  Can't set keyboard layout change to alt+shift, ctrl+shift, etc.

Status in Gnome Settings Daemon:
  Invalid
Status in Ubuntu GNOME:
  Confirmed
Status in “gnome-control-center” package in Ubuntu:
  Fix Released
Status in “gnome-settings-daemon” package in Ubuntu:
  Triaged
Status in “gnome-settings-daemon” source package in Saucy:
  Triaged
Status in “gnome-control-center” package in ALT Linux:
  Unknown
Status in “gnome-control-center” package in Baltix:
  Confirmed
Status in “gnome-control-center” package in Fedora:
  Unknown
Status in “gnome-control-center” package in Gentoo Linux:
  Invalid
Status in “gnome-control-center” package in Mandriva:
  Invalid

Bug description:
  ***
  The old PPA, ppa:attente/1218322 is superceded by the following one. You can 
remove the old repository using ppa-purge.
  ***

  A PPA which should provide some relief for this issue is available at
  https://launchpad.net/~attente/+archive/modifier-only-input-switch. To
  install:

  sudo add-apt-repository ppa:attente/modifier-only-input-switch
  sudo apt-get update
  sudo apt-get upgrade
  (log out, log in)

  If the packages improve the situation for you, you can pin them using:

  sudo apt-mark hold compiz
  sudo apt-mark hold gnome-settings-daemon
  sudo apt-mark hold unity

  If the packages don't work for you, you can purge them using:

  sudo ppa-purge ppa:attente/modifier-only-input-switch

  === compiz ===

  Impact: modifier-only key bindings need to be independent of key-press
  order, there's no support for double tapping two modifier keys of the
  same type

  Test case:
  - add at least two input sources through gnome-control-center's text entry 
settings
  - use gsettings to set the input switching shortcut to ctrl+left shift: 
gsettings set org.gnome.desktop.wm.keybindings switch-input-source 
"['Shift_L']"
  - holding left shift, press and release ctrl
  -> the current input source should change

  Regression potential: possible, but highly unlikely, that some key
  bindings may be triggered due to the removal of some code that would
  normally prevent a possible tap from occurring.

  === unity ===

  Impact: gnome-settings-daemon eats modifier-only shortcuts preventing
  them from propagating down to applications

  Test case:
  - open gnome-control-center's text input settings
  - set the next input source key binding to ctrl+left shift
  - open gnome-terminal
  - press ctrl+shift+t
  -> gnome-terminal should open a new tab

  Regression potential: the additional input switch key bindings could
  collide with other functionality such as opening the dash or hud

  === gnome-control-center ===

  Impact: the UI to change the layout switching keys doesn't work

  Test case:
  - open gnome-control-center's text input settings
  - click on the "next layout key" entry
  - try entering a key combinaison (e.g ctrl-space)
  -> the UI should reflect the new keys

  Regression potential: that UI was not working before, it should only
  be an improvement (some key combos are not working as expected, that's
  another issue and shouldn't be mixed with this one)

  === gnome-settings-daemon ===

  Impact: attempting to change keyboard layouts using only modifier keys
  doesn't work

  Test case:
  - add at least two input sources through gnome-control-center's text entry 
settings
  - use gsettings to set the input switching shortcut to ctrl+left shift: 
gsettings set org.gnome.desktop.wm.keybindings switch-input-source 
"['Shift_L']"
  - press and release ctrl+left shift
  -> the current input source should change

  Regression potential: The input switching shortcut might capture other
  non-modifier shortcuts, but users will need to consider this when
  choosing their switching shortcut anyways. For users this bug affects,
  this represents a working solution for a critical bug.

  --

  Test results for different keyboard layout change hotkeys may be
  viewed and added in the Google Docs table, created by Norbert
  
(https://docs.google.com/spreadsheet/ccc?key=0Ao5e713Ig9g_dEJrX2NRYlpLWWVzSWxsVXU4ck9HYVE&usp=sharing).

  --
  Recent discovered bugs related to keyboard layouts:
     * keyboard layout settings must be consistent between gnome-control-center 
keyboard, indicator-keyboard and gnome-tweak-tool and /etc/default/keyboard 
(bug 1270574)
     * Ubuntu 14.04 should have gnome-tweak-tool installed by default because 
of many settings that are missed gnome-control-center (bug 1270572)
     * Please add ability to set keyboard shortcuts to unity-control-center 
launched from GNOME session FlashBack (Compiz and Metacity) (bug 1282637)
     * Unable to rename new folder in GtkFileChooserDialog while changing 
keyboard layou

[Desktop-packages] [Bug 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.

[Romano Giannetti]

@William (sorry, got posted too early, a pity launchpad don't let you
edit comments). I read wrongly your comment and thought it would have
been of no use (I use only latin keyboards --- switch between US intl,
US intl AltGr-dead keys, and Spanish), and the name of the PPA is for
"non-latin"...

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

Title:
  Can't set keyboard layout change to alt+shift, ctrl+shift, etc.

Status in Gnome Settings Daemon:
  Invalid
Status in Ubuntu GNOME:
  Confirmed
Status in “gnome-control-center” package in Ubuntu:
  Fix Released
Status in “gnome-settings-daemon” package in Ubuntu:
  Triaged
Status in “gnome-settings-daemon” source package in Saucy:
  Triaged
Status in “gnome-control-center” package in ALT Linux:
  Unknown
Status in “gnome-control-center” package in Baltix:
  Confirmed
Status in “gnome-control-center” package in Fedora:
  Unknown
Status in “gnome-control-center” package in Gentoo Linux:
  Invalid
Status in “gnome-control-center” package in Mandriva:
  Invalid

Bug description:
  ***
  The old PPA, ppa:attente/1218322 is superceded by the following one. You can 
remove the old repository using ppa-purge.
  ***

  A PPA which should provide some relief for this issue is available at
  https://launchpad.net/~attente/+archive/modifier-only-input-switch. To
  install:

  sudo add-apt-repository ppa:attente/modifier-only-input-switch
  sudo apt-get update
  sudo apt-get upgrade
  (log out, log in)

  If the packages improve the situation for you, you can pin them using:

  sudo apt-mark hold compiz
  sudo apt-mark hold gnome-settings-daemon
  sudo apt-mark hold unity

  If the packages don't work for you, you can purge them using:

  sudo ppa-purge ppa:attente/modifier-only-input-switch

  === compiz ===

  Impact: modifier-only key bindings need to be independent of key-press
  order, there's no support for double tapping two modifier keys of the
  same type

  Test case:
  - add at least two input sources through gnome-control-center's text entry 
settings
  - use gsettings to set the input switching shortcut to ctrl+left shift: 
gsettings set org.gnome.desktop.wm.keybindings switch-input-source 
"['Shift_L']"
  - holding left shift, press and release ctrl
  -> the current input source should change

  Regression potential: possible, but highly unlikely, that some key
  bindings may be triggered due to the removal of some code that would
  normally prevent a possible tap from occurring.

  === unity ===

  Impact: gnome-settings-daemon eats modifier-only shortcuts preventing
  them from propagating down to applications

  Test case:
  - open gnome-control-center's text input settings
  - set the next input source key binding to ctrl+left shift
  - open gnome-terminal
  - press ctrl+shift+t
  -> gnome-terminal should open a new tab

  Regression potential: the additional input switch key bindings could
  collide with other functionality such as opening the dash or hud

  === gnome-control-center ===

  Impact: the UI to change the layout switching keys doesn't work

  Test case:
  - open gnome-control-center's text input settings
  - click on the "next layout key" entry
  - try entering a key combinaison (e.g ctrl-space)
  -> the UI should reflect the new keys

  Regression potential: that UI was not working before, it should only
  be an improvement (some key combos are not working as expected, that's
  another issue and shouldn't be mixed with this one)

  === gnome-settings-daemon ===

  Impact: attempting to change keyboard layouts using only modifier keys
  doesn't work

  Test case:
  - add at least two input sources through gnome-control-center's text entry 
settings
  - use gsettings to set the input switching shortcut to ctrl+left shift: 
gsettings set org.gnome.desktop.wm.keybindings switch-input-source 
"['Shift_L']"
  - press and release ctrl+left shift
  -> the current input source should change

  Regression potential: The input switching shortcut might capture other
  non-modifier shortcuts, but users will need to consider this when
  choosing their switching shortcut anyways. For users this bug affects,
  this represents a working solution for a critical bug.

  --

  Test results for different keyboard layout change hotkeys may be
  viewed and added in the Google Docs table, created by Norbert
  
(https://docs.google.com/spreadsheet/ccc?key=0Ao5e713Ig9g_dEJrX2NRYlpLWWVzSWxsVXU4ck9HYVE&usp=sharing).

  --
  Recent discovered bugs related to keyboard layouts:
     * keyboard layout settings must be consistent between gnome-control-center 
keyboard, indicator-keyboard and gnome-tweak-tool and /etc/default/keyboard 
(bug 1270574)
     * Ubuntu 14.04 should have gnome-tweak-tool installed by default because 
of many settings that are missed gnome-control-center (bug 1270572)
     * Pl

[Desktop-packages] [Bug 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.

[Romano Giannetti]

Yes, I can confirm that with more than 2 layouts the thing is even more
broken.

I tried to get a shot to understand better what it's happening, but I
suspect that the thing is **really** complex and we have a lot of
interacting modules and things that (I suspect) no one really grasp ---
the dconf thing, the IBus thing, etc.

I feel really represented by the Steve Taylor's quote at the top of
http://www.charvolant.org/~doug/xkb/html/xkb.html --- go and read it.

At the end, I learned to edit KBD configuration to tailor a personal
keyboard so that I can avoid switching. I imagine this is viable for me
(just using three latin languages), not for people with more complex
need.

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

Title:
  Can't set keyboard layout change to alt+shift, ctrl+shift, etc.

Status in Gnome Settings Daemon:
  Invalid
Status in Ubuntu GNOME:
  Confirmed
Status in “gnome-control-center” package in Ubuntu:
  Fix Released
Status in “gnome-settings-daemon” package in Ubuntu:
  Triaged
Status in “gnome-settings-daemon” source package in Saucy:
  Triaged
Status in “gnome-control-center” package in ALT Linux:
  Unknown
Status in “gnome-control-center” package in Baltix:
  Confirmed
Status in “gnome-control-center” package in Fedora:
  Unknown
Status in “gnome-control-center” package in Gentoo Linux:
  Invalid
Status in “gnome-control-center” package in Mandriva:
  Invalid

Bug description:
  ***
  The old PPA, ppa:attente/1218322 is superceded by the following one. You can 
remove the old repository using ppa-purge.
  ***

  A PPA which should provide some relief for this issue is available at
  https://launchpad.net/~attente/+archive/modifier-only-input-switch. To
  install:

  sudo add-apt-repository ppa:attente/modifier-only-input-switch
  sudo apt-get update
  sudo apt-get upgrade
  (log out, log in)

  If the packages improve the situation for you, you can pin them using:

  sudo apt-mark hold compiz
  sudo apt-mark hold gnome-settings-daemon
  sudo apt-mark hold unity

  If the packages don't work for you, you can purge them using:

  sudo ppa-purge ppa:attente/modifier-only-input-switch

  === compiz ===

  Impact: modifier-only key bindings need to be independent of key-press
  order, there's no support for double tapping two modifier keys of the
  same type

  Test case:
  - add at least two input sources through gnome-control-center's text entry 
settings
  - use gsettings to set the input switching shortcut to ctrl+left shift: 
gsettings set org.gnome.desktop.wm.keybindings switch-input-source 
"['Shift_L']"
  - holding left shift, press and release ctrl
  -> the current input source should change

  Regression potential: possible, but highly unlikely, that some key
  bindings may be triggered due to the removal of some code that would
  normally prevent a possible tap from occurring.

  === unity ===

  Impact: gnome-settings-daemon eats modifier-only shortcuts preventing
  them from propagating down to applications

  Test case:
  - open gnome-control-center's text input settings
  - set the next input source key binding to ctrl+left shift
  - open gnome-terminal
  - press ctrl+shift+t
  -> gnome-terminal should open a new tab

  Regression potential: the additional input switch key bindings could
  collide with other functionality such as opening the dash or hud

  === gnome-control-center ===

  Impact: the UI to change the layout switching keys doesn't work

  Test case:
  - open gnome-control-center's text input settings
  - click on the "next layout key" entry
  - try entering a key combinaison (e.g ctrl-space)
  -> the UI should reflect the new keys

  Regression potential: that UI was not working before, it should only
  be an improvement (some key combos are not working as expected, that's
  another issue and shouldn't be mixed with this one)

  === gnome-settings-daemon ===

  Impact: attempting to change keyboard layouts using only modifier keys
  doesn't work

  Test case:
  - add at least two input sources through gnome-control-center's text entry 
settings
  - use gsettings to set the input switching shortcut to ctrl+left shift: 
gsettings set org.gnome.desktop.wm.keybindings switch-input-source 
"['Shift_L']"
  - press and release ctrl+left shift
  -> the current input source should change

  Regression potential: The input switching shortcut might capture other
  non-modifier shortcuts, but users will need to consider this when
  choosing their switching shortcut anyways. For users this bug affects,
  this represents a working solution for a critical bug.

  --

  Test results for different keyboard layout change hotkeys may be
  viewed and added in the Google Docs table, created by Norbert
  
(https://docs.google.com/spreadsheet/ccc?key=0Ao5e713Ig9g_dEJrX2NRYlpLWWVzSWxsVXU4ck9HYVE&usp=sharing).

  --

[Desktop-packages] [Bug 1318452] [NEW] .Xmodmap should be read after keyboard layout switch

[Romano Giannetti]

Public bug reported:

Using Ubuntu Gnome 14.04, my .Xmodmap is correctly read at startup (at least, 
it seems). 
I have a very simple .Xmodmap: 

! EuroSign is on AltGr-5, eacute is mucho more useful for Spanish
keycode  26 = e E e E eacute Eacute

However, on layout switch, the modification is forgot.

Shouldn't .Xmodmap re-read on keyboard layout switch? Alternatively, is
there a hook for running scripts on the keyboard layout switch?

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

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

Title:
  .Xmodmap should be read after keyboard layout switch

Status in “gnome-settings-daemon” package in Ubuntu:
  New

Bug description:
  Using Ubuntu Gnome 14.04, my .Xmodmap is correctly read at startup (at least, 
it seems). 
  I have a very simple .Xmodmap: 

  ! EuroSign is on AltGr-5, eacute is mucho more useful for Spanish
  keycode  26 = e E e E eacute Eacute

  However, on layout switch, the modification is forgot.

  Shouldn't .Xmodmap re-read on keyboard layout switch? Alternatively,
  is there a hook for running scripts on the keyboard layout switch?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1318452/+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 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.

[Romano Giannetti]

@William, i have a pure Ubuntu Gnome (3) system --- should  I test your
PPA? Keyboard switch with key-combos  is utterly broken on my system, to
the point that the only reliable way to obtain it is using the panel
indicator --- which, by the way, is often than not out of sync  with the
real keymap.

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

Title:
  Can't set keyboard layout change to alt+shift, ctrl+shift, etc.

Status in Gnome Settings Daemon:
  Invalid
Status in Ubuntu GNOME:
  Confirmed
Status in “gnome-control-center” package in Ubuntu:
  Fix Released
Status in “gnome-settings-daemon” package in Ubuntu:
  Triaged
Status in “gnome-settings-daemon” source package in Saucy:
  Triaged
Status in “gnome-control-center” package in ALT Linux:
  Unknown
Status in “gnome-control-center” package in Baltix:
  Confirmed
Status in “gnome-control-center” package in Fedora:
  Unknown
Status in “gnome-control-center” package in Gentoo Linux:
  Invalid
Status in “gnome-control-center” package in Mandriva:
  Invalid

Bug description:
  ***
  The old PPA, ppa:attente/1218322 is superceded by the following one. You can 
remove the old repository using ppa-purge.
  ***

  A PPA which should provide some relief for this issue is available at
  https://launchpad.net/~attente/+archive/modifier-only-input-switch. To
  install:

  sudo add-apt-repository ppa:attente/modifier-only-input-switch
  sudo apt-get update
  sudo apt-get upgrade
  (log out, log in)

  If the packages improve the situation for you, you can pin them using:

  sudo apt-mark hold compiz
  sudo apt-mark hold gnome-settings-daemon
  sudo apt-mark hold unity

  If the packages don't work for you, you can purge them using:

  sudo ppa-purge ppa:attente/modifier-only-input-switch

  === compiz ===

  Impact: modifier-only key bindings need to be independent of key-press
  order, there's no support for double tapping two modifier keys of the
  same type

  Test case:
  - add at least two input sources through gnome-control-center's text entry 
settings
  - use gsettings to set the input switching shortcut to ctrl+left shift: 
gsettings set org.gnome.desktop.wm.keybindings switch-input-source 
"['Shift_L']"
  - holding left shift, press and release ctrl
  -> the current input source should change

  Regression potential: possible, but highly unlikely, that some key
  bindings may be triggered due to the removal of some code that would
  normally prevent a possible tap from occurring.

  === unity ===

  Impact: gnome-settings-daemon eats modifier-only shortcuts preventing
  them from propagating down to applications

  Test case:
  - open gnome-control-center's text input settings
  - set the next input source key binding to ctrl+left shift
  - open gnome-terminal
  - press ctrl+shift+t
  -> gnome-terminal should open a new tab

  Regression potential: the additional input switch key bindings could
  collide with other functionality such as opening the dash or hud

  === gnome-control-center ===

  Impact: the UI to change the layout switching keys doesn't work

  Test case:
  - open gnome-control-center's text input settings
  - click on the "next layout key" entry
  - try entering a key combinaison (e.g ctrl-space)
  -> the UI should reflect the new keys

  Regression potential: that UI was not working before, it should only
  be an improvement (some key combos are not working as expected, that's
  another issue and shouldn't be mixed with this one)

  === gnome-settings-daemon ===

  Impact: attempting to change keyboard layouts using only modifier keys
  doesn't work

  Test case:
  - add at least two input sources through gnome-control-center's text entry 
settings
  - use gsettings to set the input switching shortcut to ctrl+left shift: 
gsettings set org.gnome.desktop.wm.keybindings switch-input-source 
"['Shift_L']"
  - press and release ctrl+left shift
  -> the current input source should change

  Regression potential: The input switching shortcut might capture other
  non-modifier shortcuts, but users will need to consider this when
  choosing their switching shortcut anyways. For users this bug affects,
  this represents a working solution for a critical bug.

  --

  Test results for different keyboard layout change hotkeys may be
  viewed and added in the Google Docs table, created by Norbert
  
(https://docs.google.com/spreadsheet/ccc?key=0Ao5e713Ig9g_dEJrX2NRYlpLWWVzSWxsVXU4ck9HYVE&usp=sharing).

  --
  Recent discovered bugs related to keyboard layouts:
     * keyboard layout settings must be consistent between gnome-control-center 
keyboard, indicator-keyboard and gnome-tweak-tool and /etc/default/keyboard 
(bug 1270574)
     * Ubuntu 14.04 should have gnome-tweak-tool installed by default because 
of many settings that are missed gnome-control-center (bug 1270572)
     

[Desktop-packages] [Bug 1215798] Re: losing windows on Ubuntu 13.10

[Romano Giannetti]

Added gnome-terminal because it really happens reliably just with it.

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

Title:
  losing windows on Ubuntu 13.10

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

Bug description:
  I found, that gnome-shell lose some windows.

  I see it in two ways:

  1. gnome-terminal: after a restart - with ALT+F2 -> r or kill -HUP
  $(pgrep gnome-shell|head -n1) or resume from suspend - a terminal
  windows can not be opened any more, but is listed in ALT+TAB list (I
  add a video)

  2. remmina: I opened a connection and sometimes the window is just not
  to see any more - also not in ALT+TAB. But it must there, when I open
  a new connection in a other group I get a new window. When I open a
  new connection in the same group as the lost windows (it get normally
  attached as a new tab to the window) it get a connect to the server,
  but not the window. I can see on the terminal server and netstat, that
  the connection is established.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-shell 3.8.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-3.7-generic 3.11.0-rc6
  Uname: Linux 3.11.0-3-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.1-0ubuntu2
  Architecture: amd64
  Date: Fri Aug 23 09:26:56 2013
  DisplayManager: gdm
  GsettingsChanges:
   b'org.gnome.desktop.interface' b'buttons-have-icons' b'true'
   b'org.gnome.desktop.interface' b'gtk-theme' b"'04-Crunchy-grey'"
   b'org.gnome.desktop.interface' b'menus-have-icons' b'true'
  InstallationDate: Installed on 2013-08-19 (3 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Alpha amd64 
(20130724)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  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/1215798/+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 1215798] Re: losing windows on Ubuntu 13.10

[Romano Giannetti]

Desktop shot showing the bug.

** Attachment added: "Workspace 2_003.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1215798/+attachment/4106024/+files/Workspace%202_003.png

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

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

Title:
  losing windows on Ubuntu 13.10

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

Bug description:
  I found, that gnome-shell lose some windows.

  I see it in two ways:

  1. gnome-terminal: after a restart - with ALT+F2 -> r or kill -HUP
  $(pgrep gnome-shell|head -n1) or resume from suspend - a terminal
  windows can not be opened any more, but is listed in ALT+TAB list (I
  add a video)

  2. remmina: I opened a connection and sometimes the window is just not
  to see any more - also not in ALT+TAB. But it must there, when I open
  a new connection in a other group I get a new window. When I open a
  new connection in the same group as the lost windows (it get normally
  attached as a new tab to the window) it get a connect to the server,
  but not the window. I can see on the terminal server and netstat, that
  the connection is established.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-shell 3.8.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-3.7-generic 3.11.0-rc6
  Uname: Linux 3.11.0-3-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.1-0ubuntu2
  Architecture: amd64
  Date: Fri Aug 23 09:26:56 2013
  DisplayManager: gdm
  GsettingsChanges:
   b'org.gnome.desktop.interface' b'buttons-have-icons' b'true'
   b'org.gnome.desktop.interface' b'gtk-theme' b"'04-Crunchy-grey'"
   b'org.gnome.desktop.interface' b'menus-have-icons' b'true'
  InstallationDate: Installed on 2013-08-19 (3 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Alpha amd64 
(20130724)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  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/1215798/+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

Re: [Desktop-packages] [Bug 295014]

[Romano Giannetti]

This bug is moving to a release to the next since at least 2004...

(In its various incarnations)

Would be more faithful if some developer acknowledged that it is unfixable
for the different structure of the two programs and mark it wontfix.

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

Title:
  [Upstream] Cannot remove highlight from .doc in Word exported from
  Writer

Status in LibreOffice Productivity Suite:
  Confirmed
Status in The OpenOffice.org Suite:
  Confirmed
Status in “libreoffice” package in Ubuntu:
  Triaged
Status in “openoffice.org” package in Ubuntu:
  Won't Fix
Status in “libreoffice” package in Debian:
  New
Status in “libreoffice” package in Fedora:
  Unknown
Status in “libreoffice” package in openSUSE:
  Incomplete

Bug description:
  Binary package hint: openoffice.org-core

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

  2) apt-cache policy libreoffice-writer
  libreoffice-writer:
    Installed: 1:3.3.3-1ubuntu2
    Candidate: 1:3.3.3-1ubuntu2
    Version table:
   *** 1:3.3.3-1ubuntu2 0
  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

  3) What is expected to happen in documented exported from Writer
  opened in Word via the Terminal:

  cd ~/Desktop && wget
  
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/295014/+attachment/410599/+files/test_highlight.doc
  && wine ~/.wine/drive_c/Program\ Files/Microsoft\
  Office/OFFICE11/WINWORD.EXE test_highlight.doc

  click the Highlight button -> No Fill and the highlight is removed.

  4) What happens instead is the highlight is not removed.

  WORKAROUND: In Word click Format -> Boarders and Shading... -> Shading
  tab -> click No Fill button -> under Preview change drop down Apply
  to: text -> OK button

  WORKAROUND: Use AbiWord to export documents with highlighting.

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/295014/+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 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.

[Romano Giannetti]

On Ubuntu Gnome 14.04, the bug is still there.

I have no PPA related to gnome or this bug installed.

The "modifier only" option for switching, set to whichever option, will
change the keyboard indicated in the panel indicator, but will not
really change the keyboard layout.

Setting the "switch to next source" to a normal combination (for
example, ctrl+0) works.

I am starting to suspect that there is no one around who really
understand what's happening here --- it is so complex.

I confirm that none of the modifier-only combination wrong, trying with
the (should be equivalent):

- gnome (or unity) control center, keyboard -> shortcut -> typing
- gnome-tweak-tool -> typing
- gsetting or gconf-editor on  org.gnome.desktop.input-sources -> xkb-option

So no joy here. Ended up setting the switch to next source to
alt+shift+space which seems to work.

:-(

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

Title:
  Can't set keyboard layout change to alt+shift, ctrl+shift, etc.

Status in Gnome Settings Daemon:
  Invalid
Status in Ubuntu GNOME:
  Confirmed
Status in “gnome-control-center” package in Ubuntu:
  Fix Released
Status in “gnome-settings-daemon” package in Ubuntu:
  Triaged
Status in “gnome-settings-daemon” source package in Saucy:
  Triaged
Status in “gnome-control-center” package in ALT Linux:
  Unknown
Status in “gnome-control-center” package in Baltix:
  Confirmed
Status in “gnome-control-center” package in Gentoo Linux:
  Invalid
Status in “gnome-control-center” package in Mandriva:
  Invalid

Bug description:
  ***
  The old PPA, ppa:attente/1218322 is superceded by the following one. You can 
remove the old repository using ppa-purge.
  ***

  A PPA which should provide some relief for this issue is available at
  https://launchpad.net/~attente/+archive/modifier-only-input-switch. To
  install:

  sudo add-apt-repository ppa:attente/modifier-only-input-switch
  sudo apt-get update
  sudo apt-get upgrade
  (log out, log in)

  If the packages improve the situation for you, you can pin them using:

  sudo apt-mark hold compiz
  sudo apt-mark hold gnome-settings-daemon
  sudo apt-mark hold unity

  If the packages don't work for you, you can purge them using:

  sudo ppa-purge ppa:attente/modifier-only-input-switch

  === compiz ===

  Impact: modifier-only key bindings need to be independent of key-press
  order, there's no support for double tapping two modifier keys of the
  same type

  Test case:
  - add at least two input sources through gnome-control-center's text entry 
settings
  - use gsettings to set the input switching shortcut to ctrl+left shift: 
gsettings set org.gnome.desktop.wm.keybindings switch-input-source 
"['Shift_L']"
  - holding left shift, press and release ctrl
  -> the current input source should change

  Regression potential: possible, but highly unlikely, that some key
  bindings may be triggered due to the removal of some code that would
  normally prevent a possible tap from occurring.

  === unity ===

  Impact: gnome-settings-daemon eats modifier-only shortcuts preventing
  them from propagating down to applications

  Test case:
  - open gnome-control-center's text input settings
  - set the next input source key binding to ctrl+left shift
  - open gnome-terminal
  - press ctrl+shift+t
  -> gnome-terminal should open a new tab

  Regression potential: the additional input switch key bindings could
  collide with other functionality such as opening the dash or hud

  === gnome-control-center ===

  Impact: the UI to change the layout switching keys doesn't work

  Test case:
  - open gnome-control-center's text input settings
  - click on the "next layout key" entry
  - try entering a key combinaison (e.g ctrl-space)
  -> the UI should reflect the new keys

  Regression potential: that UI was not working before, it should only
  be an improvement (some key combos are not working as expected, that's
  another issue and shouldn't be mixed with this one)

  === gnome-settings-daemon ===

  Impact: attempting to change keyboard layouts using only modifier keys
  doesn't work

  Test case:
  - add at least two input sources through gnome-control-center's text entry 
settings
  - use gsettings to set the input switching shortcut to ctrl+left shift: 
gsettings set org.gnome.desktop.wm.keybindings switch-input-source 
"['Shift_L']"
  - press and release ctrl+left shift
  -> the current input source should change

  Regression potential: The input switching shortcut might capture other
  non-modifier shortcuts, but users will need to consider this when
  choosing their switching shortcut anyways. For users this bug affects,
  this represents a working solution for a critical bug.

  --

  Test results for different keyboard layout change hotkeys may be
  viewed and added in the Google Docs table, created by Norbert
  
(htt

[Desktop-packages] [Bug 1184085] Re: Xorg server crashes when drawing dashed circles

[Romano Giannetti]

I can confirm that the bug is fixed in Trusty Thar 14.04.

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

Title:
  Xorg server crashes when drawing dashed circles

Status in “xorg-server” package in Ubuntu:
  Fix Released

Bug description:
  To reproduce:

  install xfig (sudo apt-get install xfig)

  open xfig --- then try to draw a circle with dashed line (choose the
  circle, select the dash line in the row below the main screen, click
  in the canvas to draw). The Xorg ser4ver crashes and You are back to
  login.

  The first time it happened apport created a report, but then did not
  open the browser to submit it --- so I am sending this by hand; will
  attach the report if I can (it's 12M compressed). I am attaching a
  version without core dump, ask me if you need the full one.

  It could be related to bad rendering of filled area:  
https://bugs.launchpad.net/bugs/1177535
  Or maybe a regression: 
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/553647

  All the data in the attached file; nevertheless, this is a -intel
  driver. Ubuntu 13.04 with gnome-shell.

  Thanks
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  DistUpgraded: 2013-05-01 12:26:11,977 DEBUG enabling apt cron job
  DistroCodename: raring
  DistroRelease: Ubuntu 13.04
  DistroVariant: ubuntu
  DkmsStatus:
   vboxhost, 4.2.12, 3.8.0-21-generic, x86_64: installed
   vboxhost, 4.2.12, 3.8.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000]
  InstallationDate: Installed on 2012-12-15 (162 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  MarkForUpload: True
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-21-generic 
root=/dev/mapper/ubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.8.0-21.32-generic 3.8.8
  Tags:  raring ubuntu
  Uname: Linux 3.8.0-21-generic x86_64
  UpgradeStatus: Upgraded to raring on 2013-05-01 (25 days ago)
  UserGroups: adm lpadmin sambashare sudo vboxusers
  dmi.bios.date: 08/23/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F11
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B75M-D3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF11:bd08/23/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB75M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1
  version.ia32-libs: ia32-libs 20090808ubuntu36
  version.libdrm2: libdrm2 2.4.43-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.1-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.1-0ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.7-0ubuntu1
  xserver.bootTime: Sun May 26 13:11:04 2013
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.13.3-0ubuntu6
  xserver.video_driver: intel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1184085/+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 1281250] Re: VNC accessible from non-linux machines only with encryption disabled

[Romano Giannetti]

SSVNC works, although is quite slow with vino. Using x11vnc as server
with -ssl options give a reasonable speed.

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

Title:
  VNC accessible from non-linux machines only with encryption disabled

Status in GNOME Remote Desktop:
  Confirmed
Status in “vino” package in Ubuntu:
  Triaged
Status in “vino” source package in Trusty:
  Triaged
Status in “vino” package in Fedora:
  Unknown

Bug description:
  Since a recent update, it is impossible to connect to my Ubuntu box
  using VNC from a Windows machine unless I disable encryption on the
  vino server.

  I tested up-to-date tightVNC client and TigerVNC client on the Windows
  machine, with the same result. As soon I try to connect, I receive the
  following error:

  [ 5872/ 6448] 2014-01-20 12:11:18:247   List of security type is read
  [ 5872/ 6448] 2014-01-20 12:11:18:247 : Security Types received (1): Unknown 
type (18)
  [ 5872/ 6448] 2014-01-20 12:11:18:247   Selecting auth-handler
  [ 5872/ 6448] 2014-01-20 12:11:18:247 + RemoteViewerCore. Exception: No 
security types supported. Server sent security types, but we do not support any 
of their.

  So it seems that the update changed the security type of vino to a new
  one. I searched for a way to go back to the old one (until the clients
  catches up) with no avail.

  A solution is disabling the encryption completely, by

  gsettings set org.gnome.Vino require-encryption false

  ...but this is subotpimal. Is there a way to switch the encryption
  back to the old one?

To manage notifications about this bug go to:
https://bugs.launchpad.net/vino/+bug/1281250/+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 1281250] Re: VNC accessible from non-linux machines only with encryption disabled

[Romano Giannetti]

** Summary changed:

- VNC accessible for Windows machines only with encryption disabled
+ VNC accessible from non-linux machines only with encryption disabled

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

Title:
  VNC accessible from non-linux machines only with encryption disabled

Status in GNOME Remote Desktop:
  Confirmed
Status in “vino” package in Ubuntu:
  Triaged
Status in “vino” source package in Trusty:
  Triaged
Status in “vino” package in Fedora:
  Unknown

Bug description:
  Since a recent update, it is impossible to connect to my Ubuntu box
  using VNC from a Windows machine unless I disable encryption on the
  vino server.

  I tested up-to-date tightVNC client and TigerVNC client on the Windows
  machine, with the same result. As soon I try to connect, I receive the
  following error:

  [ 5872/ 6448] 2014-01-20 12:11:18:247   List of security type is read
  [ 5872/ 6448] 2014-01-20 12:11:18:247 : Security Types received (1): Unknown 
type (18)
  [ 5872/ 6448] 2014-01-20 12:11:18:247   Selecting auth-handler
  [ 5872/ 6448] 2014-01-20 12:11:18:247 + RemoteViewerCore. Exception: No 
security types supported. Server sent security types, but we do not support any 
of their.

  So it seems that the update changed the security type of vino to a new
  one. I searched for a way to go back to the old one (until the clients
  catches up) with no avail.

  A solution is disabling the encryption completely, by

  gsettings set org.gnome.Vino require-encryption false

  ...but this is subotpimal. Is there a way to switch the encryption
  back to the old one?

To manage notifications about this bug go to:
https://bugs.launchpad.net/vino/+bug/1281250/+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 1281250] Re: VNC accessible for Windows machines only with encryption disabled

[Romano Giannetti]

@nitrogen dream: reading here:
https://sourceforge.net/p/tigervnc/code/HEAD/tree/rfbproto/rfbproto.rst
#vnc-authentication, with type 2 the only thing that is encrypted is the
VNC password, which is,  honestly, my least worry. All the keystrokes in
the session (including your bank password) is then sent unencrypted on
the local wire.

Will check SSVNC; but this is similar to what I am doing now, having a
ssh tunnel in the middle.

But again, the problem is in vino, which is offering as encrypted
transport one that nobody uses --- and that force you to go thru hoops
to have an almost safe connection.

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

Title:
  VNC accessible for Windows machines only with encryption disabled

Status in GNOME Remote Desktop:
  Confirmed
Status in “vino” package in Ubuntu:
  Triaged
Status in “vino” source package in Trusty:
  Triaged
Status in “vino” package in Fedora:
  Unknown

Bug description:
  Since a recent update, it is impossible to connect to my Ubuntu box
  using VNC from a Windows machine unless I disable encryption on the
  vino server.

  I tested up-to-date tightVNC client and TigerVNC client on the Windows
  machine, with the same result. As soon I try to connect, I receive the
  following error:

  [ 5872/ 6448] 2014-01-20 12:11:18:247   List of security type is read
  [ 5872/ 6448] 2014-01-20 12:11:18:247 : Security Types received (1): Unknown 
type (18)
  [ 5872/ 6448] 2014-01-20 12:11:18:247   Selecting auth-handler
  [ 5872/ 6448] 2014-01-20 12:11:18:247 + RemoteViewerCore. Exception: No 
security types supported. Server sent security types, but we do not support any 
of their.

  So it seems that the update changed the security type of vino to a new
  one. I searched for a way to go back to the old one (until the clients
  catches up) with no avail.

  A solution is disabling the encryption completely, by

  gsettings set org.gnome.Vino require-encryption false

  ...but this is subotpimal. Is there a way to switch the encryption
  back to the old one?

To manage notifications about this bug go to:
https://bugs.launchpad.net/vino/+bug/1281250/+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 1311735] Re: vino-server using a lot of CPU and very sluggish after upgrade to 14.04

[Romano Giannetti]

Encryption is already off due to
https://bugs.launchpad.net/ubuntu/+source/vino/+bug/1281250 - otherwise
vino is practically impossible to use (no clients apart from vinagre use
the encryption that vino offer).

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

Title:
  vino-server using a lot of CPU and very sluggish after upgrade to
  14.04

Status in “vino” package in Ubuntu:
  New

Bug description:
  The title says its all.

   PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND  
   8150 romano20   0   64268   8800   5948 R  57.8  0.4 126:57.46 vino-se+ 
   8883 romano20   0  632412  34788   6156 S  31.8  1.7 195:15.26 dropbox  
   1420 root  20   09964   1940940 S   8.5  0.1  36:28.15 cups-br+

  It was working nicely in 13.10; now it feels very sluggish and the CPU usage 
is very high all the time. 
  Connecting with TigerVNC from a Windows machine, but a couple of fast test 
showed the same problem with other clients.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: vino 3.8.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic i686
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Wed Apr 23 09:17:05 2014
  InstallationDate: Installed on 2013-04-30 (358 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
  SourcePackage: vino
  UpgradeStatus: Upgraded to trusty on 2014-04-21 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vino/+bug/1311735/+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 1311735] [NEW] vino-server using a lot of CPU and very sluggish after upgrade to 14.04

[Romano Giannetti]

Public bug reported:

The title says its all.

 PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND  
 8150 romano20   0   64268   8800   5948 R  57.8  0.4 126:57.46 vino-se+ 
 8883 romano20   0  632412  34788   6156 S  31.8  1.7 195:15.26 dropbox  
 1420 root  20   09964   1940940 S   8.5  0.1  36:28.15 cups-br+

It was working nicely in 13.10; now it feels very sluggish and the CPU usage is 
very high all the time. 
Connecting with TigerVNC from a Windows machine, but a couple of fast test 
showed the same problem with other clients.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: vino 3.8.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic i686
ApportVersion: 2.14.1-0ubuntu3
Architecture: i386
CurrentDesktop: XFCE
Date: Wed Apr 23 09:17:05 2014
InstallationDate: Installed on 2013-04-30 (358 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
SourcePackage: vino
UpgradeStatus: Upgraded to trusty on 2014-04-21 (1 days ago)

** Affects: vino (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug i386 trusty

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

Title:
  vino-server using a lot of CPU and very sluggish after upgrade to
  14.04

Status in “vino” package in Ubuntu:
  New

Bug description:
  The title says its all.

   PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND  
   8150 romano20   0   64268   8800   5948 R  57.8  0.4 126:57.46 vino-se+ 
   8883 romano20   0  632412  34788   6156 S  31.8  1.7 195:15.26 dropbox  
   1420 root  20   09964   1940940 S   8.5  0.1  36:28.15 cups-br+

  It was working nicely in 13.10; now it feels very sluggish and the CPU usage 
is very high all the time. 
  Connecting with TigerVNC from a Windows machine, but a couple of fast test 
showed the same problem with other clients.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: vino 3.8.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic i686
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Wed Apr 23 09:17:05 2014
  InstallationDate: Installed on 2013-04-30 (358 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
  SourcePackage: vino
  UpgradeStatus: Upgraded to trusty on 2014-04-21 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vino/+bug/1311735/+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 883319] Re: xrandr --scale restricts area in which mouse moves

[Romano Giannetti]

Can a bug supervisor mark this for Trusty and removing the (wrong) Fix
Released status?

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

Title:
  xrandr --scale restricts area in which mouse moves

Status in X.Org X server:
  Incomplete
Status in “xorg-server” package in Ubuntu:
  Fix Released
Status in “xorg-server” source package in Precise:
  Fix Released
Status in “xorg-server” source package in Quantal:
  Fix Released
Status in “xorg-server” source package in Raring:
  Fix Released

Bug description:
  SRU Request:

  [IMPACT]
  A bug in the version of xorg-server in precise prevents users from scaling 
screen resolution. When attempting to do so, as was possible in Natty and 
earlier, and which is possible in Quantal+, the mouse pointer remains locked 
inside the old resolution. This prevents users of small screens such as 
netbooks from scaling to a greater screen resolution.

  [Test Case]
  - On a netbook with intel chipset, such as a Dell Mini 9 or 10, scale the 
display by using the following command:

  xrandr --output LVDS1 --panning 1280x750 --scale 1.25x1.25

  See if the mouse moves correctly to all screen extremities, and is not
  confined by a transparent border at 1024x600

  [Regression Potential]
  This is fixed with a patch backported from the xorg-server version in 
Quantal. In theory it should just affect screen which are scaled and panned, 
which is uncommon. If so, the patch can be backed out.


  
  Original Bug Description:
  in kubuntu (and ubuntu) 11.04 i used to enlarge my laptop screen like so

  xrandr --output LVDS1 --scale 1.2x1.2

  this worked fine: the desktop scaled to larger size correctly .
   After upgrading to 11.10, in kde the desktop still resizes
  correctly, but the movement of the mouse is restricted to an area equal to
  the screen size *before* issuing the scaling command. .. Ie let's say
  the mode is 1366x768 and I do xrandr --output LVDS1 --scale 1.2x1.2 the
  screen size changes to 1640x922 but the mouse moves in an area the size of
  1366x768 in the top left of the screen and then 'hits a wall' preventing
  it to move. I also tried ubuntu 11.10 with gnome: here the screen also
  resizes, but I have the same issue with the mouse, and the extended area
  of the desktop is black...

  Some time ago there was a similar issue, which was resolved later. Now it 
seems
  to be back...

  jos@samsungsucks:~$ lsb_release -rd
  Description:Ubuntu 11.10
  Release:11.10

  jos@samsungsucks:~$ xrandr --version
  xrandr program version   1.3.5
  Server reports RandR version 1.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/883319/+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 883319] Re: xrandr --scale restricts area in which mouse moves

[Romano Giannetti]

Yes --- I understand. But why the bug is marked "Invalid"? It is quite
easy to reproduce, and difficult to miss (if you ever needed to use the
--scale option).

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

Title:
  xrandr --scale restricts area in which mouse moves

Status in X.Org X server:
  Incomplete
Status in “xorg-server” package in Ubuntu:
  Fix Released
Status in “xorg-server” source package in Precise:
  Fix Released
Status in “xorg-server” source package in Quantal:
  Fix Released
Status in “xorg-server” source package in Raring:
  Fix Released

Bug description:
  SRU Request:

  [IMPACT]
  A bug in the version of xorg-server in precise prevents users from scaling 
screen resolution. When attempting to do so, as was possible in Natty and 
earlier, and which is possible in Quantal+, the mouse pointer remains locked 
inside the old resolution. This prevents users of small screens such as 
netbooks from scaling to a greater screen resolution.

  [Test Case]
  - On a netbook with intel chipset, such as a Dell Mini 9 or 10, scale the 
display by using the following command:

  xrandr --output LVDS1 --panning 1280x750 --scale 1.25x1.25

  See if the mouse moves correctly to all screen extremities, and is not
  confined by a transparent border at 1024x600

  [Regression Potential]
  This is fixed with a patch backported from the xorg-server version in 
Quantal. In theory it should just affect screen which are scaled and panned, 
which is uncommon. If so, the patch can be backed out.


  
  Original Bug Description:
  in kubuntu (and ubuntu) 11.04 i used to enlarge my laptop screen like so

  xrandr --output LVDS1 --scale 1.2x1.2

  this worked fine: the desktop scaled to larger size correctly .
   After upgrading to 11.10, in kde the desktop still resizes
  correctly, but the movement of the mouse is restricted to an area equal to
  the screen size *before* issuing the scaling command. .. Ie let's say
  the mode is 1366x768 and I do xrandr --output LVDS1 --scale 1.2x1.2 the
  screen size changes to 1640x922 but the mouse moves in an area the size of
  1366x768 in the top left of the screen and then 'hits a wall' preventing
  it to move. I also tried ubuntu 11.10 with gnome: here the screen also
  resizes, but I have the same issue with the mouse, and the extended area
  of the desktop is black...

  Some time ago there was a similar issue, which was resolved later. Now it 
seems
  to be back...

  jos@samsungsucks:~$ lsb_release -rd
  Description:Ubuntu 11.10
  Release:11.10

  jos@samsungsucks:~$ xrandr --version
  xrandr program version   1.3.5
  Server reports RandR version 1.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/883319/+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 883319] Re: xrandr --scale restricts area in which mouse moves

[Romano Giannetti]

...checked in 14.04 trusty, still here.

A real PITA because the scaling is really useful with all the
applications (*-tweak-tools, are you listening me?) which are expecting
1600x1200 pixel every time...

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

Title:
  xrandr --scale restricts area in which mouse moves

Status in X.Org X server:
  Incomplete
Status in “xorg-server” package in Ubuntu:
  Fix Released
Status in “xorg-server” source package in Precise:
  Fix Released
Status in “xorg-server” source package in Quantal:
  Fix Released
Status in “xorg-server” source package in Raring:
  Fix Released

Bug description:
  SRU Request:

  [IMPACT]
  A bug in the version of xorg-server in precise prevents users from scaling 
screen resolution. When attempting to do so, as was possible in Natty and 
earlier, and which is possible in Quantal+, the mouse pointer remains locked 
inside the old resolution. This prevents users of small screens such as 
netbooks from scaling to a greater screen resolution.

  [Test Case]
  - On a netbook with intel chipset, such as a Dell Mini 9 or 10, scale the 
display by using the following command:

  xrandr --output LVDS1 --panning 1280x750 --scale 1.25x1.25

  See if the mouse moves correctly to all screen extremities, and is not
  confined by a transparent border at 1024x600

  [Regression Potential]
  This is fixed with a patch backported from the xorg-server version in 
Quantal. In theory it should just affect screen which are scaled and panned, 
which is uncommon. If so, the patch can be backed out.


  
  Original Bug Description:
  in kubuntu (and ubuntu) 11.04 i used to enlarge my laptop screen like so

  xrandr --output LVDS1 --scale 1.2x1.2

  this worked fine: the desktop scaled to larger size correctly .
   After upgrading to 11.10, in kde the desktop still resizes
  correctly, but the movement of the mouse is restricted to an area equal to
  the screen size *before* issuing the scaling command. .. Ie let's say
  the mode is 1366x768 and I do xrandr --output LVDS1 --scale 1.2x1.2 the
  screen size changes to 1640x922 but the mouse moves in an area the size of
  1366x768 in the top left of the screen and then 'hits a wall' preventing
  it to move. I also tried ubuntu 11.10 with gnome: here the screen also
  resizes, but I have the same issue with the mouse, and the extended area
  of the desktop is black...

  Some time ago there was a similar issue, which was resolved later. Now it 
seems
  to be back...

  jos@samsungsucks:~$ lsb_release -rd
  Description:Ubuntu 11.10
  Release:11.10

  jos@samsungsucks:~$ xrandr --version
  xrandr program version   1.3.5
  Server reports RandR version 1.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/883319/+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 881046]

[Romano Giannetti]

Probably this bug has been marked invalid because there is a mix of two
bugs here: one is related to panning (which I do not know if it's fixed
or no), and the other one to mouse constraints when scaling.

I have X.Org X Server 1.14.5 , and if I issue

xrandr --output LVDS1 --scale 2x2

the screen scales correctly, but then the mouse is restricted to the
(original 1x1 viewport) upper left quarter of the screen, making the
scaling completely unuseful.

It is quite easily reproducible.

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

Title:
  Panning in a virtual monitor is not possible after upgrade to Ubuntu
  11.10

Status in X.Org X server:
  Incomplete
Status in “xorg-server” package in Ubuntu:
  Triaged
Status in “xorg-server” source package in Precise:
  Triaged

Bug description:
  When I go  for a virtual monitor by issuing command "xrandr --output
  LVDS1 --fb 1600x1200 --panning 1600x1200" on a monitor working at
  resolution 1024x768 (as I did before upgrading from Ubuntu 11.04 to
  Ubuntu 11.10), the WM bars on top and left side of the screen (in
  Unity) look like extending to the new area, but I cannot move the
  pointer to the new extra area and so I cannot pan. As far as I
  understood by reading around, this *could* be a bug in package "xorg-
  server" rather than in "xrandr" and *could* be related to the
  boundaries set for cursor position.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: xorg 1:7.6+7ubuntu7
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 1.23-0ubuntu3
  Architecture: i386
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,unitymtgrabhandles,scale,session,unityshell]
  CompositorRunning: compiz
  Date: Mon Oct 24 20:40:14 2011
  DistUpgraded: Log time: 2011-10-22 12:17:44.515205
  DistroCodename: oneiric
  DistroVariant: ubuntu
  DkmsStatus:
   dahdi, 2.4.1+dfsg-1ubuntu2, 2.6.38-11-generic, i686: installed (WARNING! 
Diff between built and installed module!)
   dahdi, 2.4.1+dfsg-1ubuntu2, 3.0.0-12-generic, i686: installed (WARNING! Diff 
between built and installed module!)
   dahdi, 2.4.1+dfsg-1ubuntu2, 3.0.0-12-virtual, i686: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller 
[8086:2592] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0182]
 Subsystem: Dell Device [1028:0182]
  MachineType: Dell Inc. Latitude D610
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 3.3V 32-bit PC Card
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   LANGUAGE=it_IT:it:en_GB:en
  ProcKernelCmdLine: root=UUID=35d17829-2597-405b-afdd-6b1d94a4dedd ro quiet 
splash rootdelay=15
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to oneiric on 2011-10-22 (2 days ago)
  dmi.bios.date: 03/02/2005
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.name: 0D4571
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd03/02/2005:svnDellInc.:pnLatitudeD610:pvr:rvnDellInc.:rn0D4571:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Latitude D610
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.6+bzr20110929-0ubuntu3
  version.libdrm2: libdrm2 2.4.26-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3
  version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.14.99~git20110811.g93fc084-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.901-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20110411+8378443-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/881046/+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 883319]

[Romano Giannetti]

Probably this bug has been marked invalid because there is a mix of two
bugs here: one is related to panning (which I do not know if it's fixed
or no), and the other one to mouse constraints when scaling.

I have X.Org X Server 1.14.5 , and if I issue

xrandr --output LVDS1 --scale 2x2

the screen scales correctly, but then the mouse is restricted to the
(original 1x1 viewport) upper left quarter of the screen, making the
scaling completely unuseful.

It is quite easily reproducible.

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

Title:
  xrandr --scale restricts area in which mouse moves

Status in X.Org X server:
  Incomplete
Status in “xorg-server” package in Ubuntu:
  Fix Released
Status in “xorg-server” source package in Precise:
  Fix Released
Status in “xorg-server” source package in Quantal:
  Fix Released
Status in “xorg-server” source package in Raring:
  Fix Released

Bug description:
  SRU Request:

  [IMPACT]
  A bug in the version of xorg-server in precise prevents users from scaling 
screen resolution. When attempting to do so, as was possible in Natty and 
earlier, and which is possible in Quantal+, the mouse pointer remains locked 
inside the old resolution. This prevents users of small screens such as 
netbooks from scaling to a greater screen resolution.

  [Test Case]
  - On a netbook with intel chipset, such as a Dell Mini 9 or 10, scale the 
display by using the following command:

  xrandr --output LVDS1 --panning 1280x750 --scale 1.25x1.25

  See if the mouse moves correctly to all screen extremities, and is not
  confined by a transparent border at 1024x600

  [Regression Potential]
  This is fixed with a patch backported from the xorg-server version in 
Quantal. In theory it should just affect screen which are scaled and panned, 
which is uncommon. If so, the patch can be backed out.


  
  Original Bug Description:
  in kubuntu (and ubuntu) 11.04 i used to enlarge my laptop screen like so

  xrandr --output LVDS1 --scale 1.2x1.2

  this worked fine: the desktop scaled to larger size correctly .
   After upgrading to 11.10, in kde the desktop still resizes
  correctly, but the movement of the mouse is restricted to an area equal to
  the screen size *before* issuing the scaling command. .. Ie let's say
  the mode is 1366x768 and I do xrandr --output LVDS1 --scale 1.2x1.2 the
  screen size changes to 1640x922 but the mouse moves in an area the size of
  1366x768 in the top left of the screen and then 'hits a wall' preventing
  it to move. I also tried ubuntu 11.10 with gnome: here the screen also
  resizes, but I have the same issue with the mouse, and the extended area
  of the desktop is black...

  Some time ago there was a similar issue, which was resolved later. Now it 
seems
  to be back...

  jos@samsungsucks:~$ lsb_release -rd
  Description:Ubuntu 11.10
  Release:11.10

  jos@samsungsucks:~$ xrandr --version
  xrandr program version   1.3.5
  Server reports RandR version 1.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/883319/+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 883319] Re: xrandr --scale restricts area in which mouse moves

[Romano Giannetti]

So basically, the "Fix released" status is incorrect. The bug referred
to the title is still here (at least in Saucy, will test Trusty). Maybe
the other problem (panning, mentioned in the upstream bug, not related
with this bug title) is fixed, but not this one.

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

Title:
  xrandr --scale restricts area in which mouse moves

Status in X.Org X server:
  Incomplete
Status in “xorg-server” package in Ubuntu:
  Fix Released
Status in “xorg-server” source package in Precise:
  Fix Released
Status in “xorg-server” source package in Quantal:
  Fix Released
Status in “xorg-server” source package in Raring:
  Fix Released

Bug description:
  SRU Request:

  [IMPACT]
  A bug in the version of xorg-server in precise prevents users from scaling 
screen resolution. When attempting to do so, as was possible in Natty and 
earlier, and which is possible in Quantal+, the mouse pointer remains locked 
inside the old resolution. This prevents users of small screens such as 
netbooks from scaling to a greater screen resolution.

  [Test Case]
  - On a netbook with intel chipset, such as a Dell Mini 9 or 10, scale the 
display by using the following command:

  xrandr --output LVDS1 --panning 1280x750 --scale 1.25x1.25

  See if the mouse moves correctly to all screen extremities, and is not
  confined by a transparent border at 1024x600

  [Regression Potential]
  This is fixed with a patch backported from the xorg-server version in 
Quantal. In theory it should just affect screen which are scaled and panned, 
which is uncommon. If so, the patch can be backed out.


  
  Original Bug Description:
  in kubuntu (and ubuntu) 11.04 i used to enlarge my laptop screen like so

  xrandr --output LVDS1 --scale 1.2x1.2

  this worked fine: the desktop scaled to larger size correctly .
   After upgrading to 11.10, in kde the desktop still resizes
  correctly, but the movement of the mouse is restricted to an area equal to
  the screen size *before* issuing the scaling command. .. Ie let's say
  the mode is 1366x768 and I do xrandr --output LVDS1 --scale 1.2x1.2 the
  screen size changes to 1640x922 but the mouse moves in an area the size of
  1366x768 in the top left of the screen and then 'hits a wall' preventing
  it to move. I also tried ubuntu 11.10 with gnome: here the screen also
  resizes, but I have the same issue with the mouse, and the extended area
  of the desktop is black...

  Some time ago there was a similar issue, which was resolved later. Now it 
seems
  to be back...

  jos@samsungsucks:~$ lsb_release -rd
  Description:Ubuntu 11.10
  Release:11.10

  jos@samsungsucks:~$ xrandr --version
  xrandr program version   1.3.5
  Server reports RandR version 1.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/883319/+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 883319] Re: xrandr --scale restricts area in which mouse moves

[Romano Giannetti]

I think that the upstream bug is not correct here. The problem is not
with panning; the problem is with scaling and the mouse behavior.

I have  xserver-xorg  1:7.7+1ubuntu6   (X.Org X Server 1.14.5), and if I
issue

xrandr --output LVDS1 --scale 2x2

the screen scales correctly, but then the mouse is restricted to the
(original 1x1 viewport) upper left quarter of the screen, making the
scaling completely unuseful.

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

Title:
  xrandr --scale restricts area in which mouse moves

Status in X.Org X server:
  Incomplete
Status in “xorg-server” package in Ubuntu:
  Fix Released
Status in “xorg-server” source package in Precise:
  Fix Released
Status in “xorg-server” source package in Quantal:
  Fix Released
Status in “xorg-server” source package in Raring:
  Fix Released

Bug description:
  SRU Request:

  [IMPACT]
  A bug in the version of xorg-server in precise prevents users from scaling 
screen resolution. When attempting to do so, as was possible in Natty and 
earlier, and which is possible in Quantal+, the mouse pointer remains locked 
inside the old resolution. This prevents users of small screens such as 
netbooks from scaling to a greater screen resolution.

  [Test Case]
  - On a netbook with intel chipset, such as a Dell Mini 9 or 10, scale the 
display by using the following command:

  xrandr --output LVDS1 --panning 1280x750 --scale 1.25x1.25

  See if the mouse moves correctly to all screen extremities, and is not
  confined by a transparent border at 1024x600

  [Regression Potential]
  This is fixed with a patch backported from the xorg-server version in 
Quantal. In theory it should just affect screen which are scaled and panned, 
which is uncommon. If so, the patch can be backed out.


  
  Original Bug Description:
  in kubuntu (and ubuntu) 11.04 i used to enlarge my laptop screen like so

  xrandr --output LVDS1 --scale 1.2x1.2

  this worked fine: the desktop scaled to larger size correctly .
   After upgrading to 11.10, in kde the desktop still resizes
  correctly, but the movement of the mouse is restricted to an area equal to
  the screen size *before* issuing the scaling command. .. Ie let's say
  the mode is 1366x768 and I do xrandr --output LVDS1 --scale 1.2x1.2 the
  screen size changes to 1640x922 but the mouse moves in an area the size of
  1366x768 in the top left of the screen and then 'hits a wall' preventing
  it to move. I also tried ubuntu 11.10 with gnome: here the screen also
  resizes, but I have the same issue with the mouse, and the extended area
  of the desktop is black...

  Some time ago there was a similar issue, which was resolved later. Now it 
seems
  to be back...

  jos@samsungsucks:~$ lsb_release -rd
  Description:Ubuntu 11.10
  Release:11.10

  jos@samsungsucks:~$ xrandr --version
  xrandr program version   1.3.5
  Server reports RandR version 1.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/883319/+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 1281250] Re: VNC accessible for Windows machines only with encryption disabled

[Romano Giannetti]

@Holger: yes --- I just  noticed it too.

I humbly suggest that Canonical or Redhat help the vino developers to
add a more common encryption type to the vino server. It is the default
(and the facto only) remote vnc server in our system, and in its current
state forces everyone to connect **in clear** on the local network. All
what you type is sent as is.

I have worked around it wrapping the thing in a SSH tunnel, but still,
it's sensible to local attacks and I think it's not a solution for the
average user.

@Sebastian, I am not sure if this is a security thing --- after all,
before the switch, all the connections were silently made without
encryption, but it's scary nevertheless --- sniffing for traffic on port
5900 is easy enough.

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

Title:
  VNC accessible for Windows machines only with encryption disabled

Status in GNOME Remote Desktop:
  Confirmed
Status in “vino” package in Ubuntu:
  Triaged
Status in “vino” source package in Trusty:
  Triaged
Status in “vino” package in Fedora:
  Unknown

Bug description:
  Since a recent update, it is impossible to connect to my Ubuntu box
  using VNC from a Windows machine unless I disable encryption on the
  vino server.

  I tested up-to-date tightVNC client and TigerVNC client on the Windows
  machine, with the same result. As soon I try to connect, I receive the
  following error:

  [ 5872/ 6448] 2014-01-20 12:11:18:247   List of security type is read
  [ 5872/ 6448] 2014-01-20 12:11:18:247 : Security Types received (1): Unknown 
type (18)
  [ 5872/ 6448] 2014-01-20 12:11:18:247   Selecting auth-handler
  [ 5872/ 6448] 2014-01-20 12:11:18:247 + RemoteViewerCore. Exception: No 
security types supported. Server sent security types, but we do not support any 
of their.

  So it seems that the update changed the security type of vino to a new
  one. I searched for a way to go back to the old one (until the clients
  catches up) with no avail.

  A solution is disabling the encryption completely, by

  gsettings set org.gnome.Vino require-encryption false

  ...but this is subotpimal. Is there a way to switch the encryption
  back to the old one?

To manage notifications about this bug go to:
https://bugs.launchpad.net/vino/+bug/1281250/+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 1281250] Re: VNC accessible for Windows machines only with encryption disabled

[Romano Giannetti]

Well, downloaded it (virt-viewer, I mean). Tried to connect to a remote
machine but no dice --- it just show a window, asking for a connection
URI, I tried 200 combinations... No documentation handy available
either. Seems to be thought just for managing virtual machines, so it
doesn't seem a general VNC viewer tool.

So I think that the only option now is

a) having a VNC with almost no  interoperability with Windows

or

b) re-defaulting to no encryption

Really, I do not know which one of the two options is the worst one.

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

Title:
  VNC accessible for Windows machines only with encryption disabled

Status in GNOME Remote Desktop:
  Confirmed
Status in “vino” package in Ubuntu:
  Triaged
Status in “vino” source package in Trusty:
  Triaged
Status in “vino” package in Fedora:
  Unknown

Bug description:
  Since a recent update, it is impossible to connect to my Ubuntu box
  using VNC from a Windows machine unless I disable encryption on the
  vino server.

  I tested up-to-date tightVNC client and TigerVNC client on the Windows
  machine, with the same result. As soon I try to connect, I receive the
  following error:

  [ 5872/ 6448] 2014-01-20 12:11:18:247   List of security type is read
  [ 5872/ 6448] 2014-01-20 12:11:18:247 : Security Types received (1): Unknown 
type (18)
  [ 5872/ 6448] 2014-01-20 12:11:18:247   Selecting auth-handler
  [ 5872/ 6448] 2014-01-20 12:11:18:247 + RemoteViewerCore. Exception: No 
security types supported. Server sent security types, but we do not support any 
of their.

  So it seems that the update changed the security type of vino to a new
  one. I searched for a way to go back to the old one (until the clients
  catches up) with no avail.

  A solution is disabling the encryption completely, by

  gsettings set org.gnome.Vino require-encryption false

  ...but this is subotpimal. Is there a way to switch the encryption
  back to the old one?

To manage notifications about this bug go to:
https://bugs.launchpad.net/vino/+bug/1281250/+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 1281250] Re: VNC accessible for Windows machines only with encryption disabled

[Romano Giannetti]

Upstream comment:

"I think that the TLS security type (18) is rather uncommon, but gtk-vnc
supports it. I think that virt-viewer uses gtk-vnc and should work:

http://virt-manager.org/download/
"

so basically the problem is that vino is using an encryption type which
is supported only by few clients. The optimal solution would be to help
vino developers to add a more common encryption type; for the time
being, I will test the suggested viewer and comment.

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

Title:
  VNC accessible for Windows machines only with encryption disabled

Status in GNOME Remote Desktop:
  Confirmed
Status in “vino” package in Ubuntu:
  Triaged
Status in “vino” source package in Trusty:
  Triaged
Status in “vino” package in Fedora:
  Unknown

Bug description:
  Since a recent update, it is impossible to connect to my Ubuntu box
  using VNC from a Windows machine unless I disable encryption on the
  vino server.

  I tested up-to-date tightVNC client and TigerVNC client on the Windows
  machine, with the same result. As soon I try to connect, I receive the
  following error:

  [ 5872/ 6448] 2014-01-20 12:11:18:247   List of security type is read
  [ 5872/ 6448] 2014-01-20 12:11:18:247 : Security Types received (1): Unknown 
type (18)
  [ 5872/ 6448] 2014-01-20 12:11:18:247   Selecting auth-handler
  [ 5872/ 6448] 2014-01-20 12:11:18:247 + RemoteViewerCore. Exception: No 
security types supported. Server sent security types, but we do not support any 
of their.

  So it seems that the update changed the security type of vino to a new
  one. I searched for a way to go back to the old one (until the clients
  catches up) with no avail.

  A solution is disabling the encryption completely, by

  gsettings set org.gnome.Vino require-encryption false

  ...but this is subotpimal. Is there a way to switch the encryption
  back to the old one?

To manage notifications about this bug go to:
https://bugs.launchpad.net/vino/+bug/1281250/+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 1281250] Re: VNC accessible for Windows machines only with encryption disabled

[Romano Giannetti]

Can please people with the problem state their version? Mine is

[:~] 127 % apt-cache policy vino 
vino:
  Installed: 3.10.0-0ubuntu1~saucy1
  Candidate: 3.10.0-0ubuntu1~saucy1
  Version table:
 *** 3.10.0-0ubuntu1~saucy1 0
500 http://ppa.launchpad.net/gnome3-team/gnome3-staging/ubuntu/ 
saucy/main i386 Packages
100 /var/lib/dpkg/status
 3.6.2-0ubuntu5 0
500 http://archive.ubuntu.com/ubuntu/ saucy/main i386 Packages

Anyone with stock 3.8 version?

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

Title:
  VNC accessible for Windows machines only with encryption disabled

Status in GNOME Remote Desktop:
  Unknown
Status in “vino” package in Ubuntu:
  Triaged
Status in “vino” source package in Trusty:
  Triaged

Bug description:
  Since a recent update, it is impossible to connect to my Ubuntu box
  using VNC from a Windows machine unless I disable encryption on the
  vino server.

  I tested up-to-date tightVNC client and TigerVNC client on the Windows
  machine, with the same result. As soon I try to connect, I receive the
  following error:

  [ 5872/ 6448] 2014-01-20 12:11:18:247   List of security type is read
  [ 5872/ 6448] 2014-01-20 12:11:18:247 : Security Types received (1): Unknown 
type (18)
  [ 5872/ 6448] 2014-01-20 12:11:18:247   Selecting auth-handler
  [ 5872/ 6448] 2014-01-20 12:11:18:247 + RemoteViewerCore. Exception: No 
security types supported. Server sent security types, but we do not support any 
of their.

  So it seems that the update changed the security type of vino to a new
  one. I searched for a way to go back to the old one (until the clients
  catches up) with no avail.

  A solution is disabling the encryption completely, by

  gsettings set org.gnome.Vino require-encryption false

  ...but this is subotpimal. Is there a way to switch the encryption
  back to the old one?

To manage notifications about this bug go to:
https://bugs.launchpad.net/vino/+bug/1281250/+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 1281250] Re: VNC accessible for Windows machines only with encryption disabled

[Romano Giannetti]

Ok, I have reported it upstream at

 https://bugzilla.gnome.org/show_bug.cgi?id=728267

--- but I am unable to add it to the bug. I used to choose älso affect 
distribution"and simply paste the URL, but now I have an error (says I can't 
add another bug to the same distribution and in the dsitribution lists there is 
no "gnome upstream to choose").  How am I supposed to add the upstream bug? 
 

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

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

Title:
  VNC accessible for Windows machines only with encryption disabled

Status in GNOME Remote Desktop:
  Unknown
Status in “vino” package in Ubuntu:
  Triaged
Status in “vino” source package in Trusty:
  Triaged

Bug description:
  Since a recent update, it is impossible to connect to my Ubuntu box
  using VNC from a Windows machine unless I disable encryption on the
  vino server.

  I tested up-to-date tightVNC client and TigerVNC client on the Windows
  machine, with the same result. As soon I try to connect, I receive the
  following error:

  [ 5872/ 6448] 2014-01-20 12:11:18:247   List of security type is read
  [ 5872/ 6448] 2014-01-20 12:11:18:247 : Security Types received (1): Unknown 
type (18)
  [ 5872/ 6448] 2014-01-20 12:11:18:247   Selecting auth-handler
  [ 5872/ 6448] 2014-01-20 12:11:18:247 + RemoteViewerCore. Exception: No 
security types supported. Server sent security types, but we do not support any 
of their.

  So it seems that the update changed the security type of vino to a new
  one. I searched for a way to go back to the old one (until the clients
  catches up) with no avail.

  A solution is disabling the encryption completely, by

  gsettings set org.gnome.Vino require-encryption false

  ...but this is subotpimal. Is there a way to switch the encryption
  back to the old one?

To manage notifications about this bug go to:
https://bugs.launchpad.net/vino/+bug/1281250/+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 1281250] Re: VNC accessible for Windows machines only with encryption disabled

[Romano Giannetti]

Sebastian: no. the default is to use encryption. But after updating vino
(do not remember at which point), vino changed the security type to a
new one (at least, I think); the connection stopped to work with the
error reported above and the only solution to have it back was to
disable encryption.

What I *suppose* happened is that the vino server upgraded the
encryption algorithm and the clients have still to catch up; the problem
is that there seems no way to say vino to use an old encryption --- it
just works with the "type 18" or none.

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

Title:
  VNC accessible for Windows machines only with encryption disabled

Status in GNOME Remote Desktop:
  Unknown
Status in “vino” package in Ubuntu:
  Triaged
Status in “vino” source package in Trusty:
  Triaged

Bug description:
  Since a recent update, it is impossible to connect to my Ubuntu box
  using VNC from a Windows machine unless I disable encryption on the
  vino server.

  I tested up-to-date tightVNC client and TigerVNC client on the Windows
  machine, with the same result. As soon I try to connect, I receive the
  following error:

  [ 5872/ 6448] 2014-01-20 12:11:18:247   List of security type is read
  [ 5872/ 6448] 2014-01-20 12:11:18:247 : Security Types received (1): Unknown 
type (18)
  [ 5872/ 6448] 2014-01-20 12:11:18:247   Selecting auth-handler
  [ 5872/ 6448] 2014-01-20 12:11:18:247 + RemoteViewerCore. Exception: No 
security types supported. Server sent security types, but we do not support any 
of their.

  So it seems that the update changed the security type of vino to a new
  one. I searched for a way to go back to the old one (until the clients
  catches up) with no avail.

  A solution is disabling the encryption completely, by

  gsettings set org.gnome.Vino require-encryption false

  ...but this is subotpimal. Is there a way to switch the encryption
  back to the old one?

To manage notifications about this bug go to:
https://bugs.launchpad.net/vino/+bug/1281250/+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 1281250] Re: VNC accessible for Windows machines only with encryption disabled

[Romano Giannetti]

I reported the thing to TigerVNC bug tracker too:
https://sourceforge.net/p/tigervnc/bug-tracker/148/ let's see if a
solution can be found...

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

Title:
  VNC accessible for Windows machines only with encryption disabled

Status in GNOME Remote Desktop:
  Unknown
Status in “vino” package in Ubuntu:
  Triaged
Status in “vino” source package in Trusty:
  Triaged

Bug description:
  Since a recent update, it is impossible to connect to my Ubuntu box
  using VNC from a Windows machine unless I disable encryption on the
  vino server.

  I tested up-to-date tightVNC client and TigerVNC client on the Windows
  machine, with the same result. As soon I try to connect, I receive the
  following error:

  [ 5872/ 6448] 2014-01-20 12:11:18:247   List of security type is read
  [ 5872/ 6448] 2014-01-20 12:11:18:247 : Security Types received (1): Unknown 
type (18)
  [ 5872/ 6448] 2014-01-20 12:11:18:247   Selecting auth-handler
  [ 5872/ 6448] 2014-01-20 12:11:18:247 + RemoteViewerCore. Exception: No 
security types supported. Server sent security types, but we do not support any 
of their.

  So it seems that the update changed the security type of vino to a new
  one. I searched for a way to go back to the old one (until the clients
  catches up) with no avail.

  A solution is disabling the encryption completely, by

  gsettings set org.gnome.Vino require-encryption false

  ...but this is subotpimal. Is there a way to switch the encryption
  back to the old one?

To manage notifications about this bug go to:
https://bugs.launchpad.net/vino/+bug/1281250/+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 1281250] Re: VNC accessible for Windows machines only with encryption disabled

[Romano Giannetti]

I agree that the best possible solution would be for the Windows clients
(at least TigerVNC and TightVNC) to catch up. Unfortunately this has not
happened; for the time being it would be much better if vino could offer
the option to go back to the previous Security Type when the client does
not support the new one.

The only solution now is disable the encryption completely; I resorted
to a loop back ssh connection so that there is no clear traffic on the
wifi, but I still need to do the local step with vino in clear way ---
almost safe for me because I do not have other local users, but you
never know...

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

Title:
  VNC accessible for Windows machines only with encryption disabled

Status in GNOME Remote Desktop:
  Unknown
Status in “vino” package in Ubuntu:
  Triaged
Status in “vino” source package in Trusty:
  Triaged

Bug description:
  Since a recent update, it is impossible to connect to my Ubuntu box
  using VNC from a Windows machine unless I disable encryption on the
  vino server.

  I tested up-to-date tightVNC client and TigerVNC client on the Windows
  machine, with the same result. As soon I try to connect, I receive the
  following error:

  [ 5872/ 6448] 2014-01-20 12:11:18:247   List of security type is read
  [ 5872/ 6448] 2014-01-20 12:11:18:247 : Security Types received (1): Unknown 
type (18)
  [ 5872/ 6448] 2014-01-20 12:11:18:247   Selecting auth-handler
  [ 5872/ 6448] 2014-01-20 12:11:18:247 + RemoteViewerCore. Exception: No 
security types supported. Server sent security types, but we do not support any 
of their.

  So it seems that the update changed the security type of vino to a new
  one. I searched for a way to go back to the old one (until the clients
  catches up) with no avail.

  A solution is disabling the encryption completely, by

  gsettings set org.gnome.Vino require-encryption false

  ...but this is subotpimal. Is there a way to switch the encryption
  back to the old one?

To manage notifications about this bug go to:
https://bugs.launchpad.net/vino/+bug/1281250/+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 295014]

[Romano Giannetti]

It *has* to be difficult. Otherwise why is it open since 2004? On
december 1st it will be 10 years old...

If I understand the issue, the main problem is that in MS Word there are
different attributes for character background and highlight, while in
LOO/AOO they are considered the same. If this is the case, making the
change and maintaining compatibility with older version of LOO/AOO could
be, well, difficult.

Is my guess correct?

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

Title:
  [Upstream] Cannot remove highlight from .doc in Word exported from
  Writer

Status in LibreOffice Productivity Suite:
  Confirmed
Status in The OpenOffice.org Suite:
  Confirmed
Status in “libreoffice” package in Ubuntu:
  Triaged
Status in “openoffice.org” package in Ubuntu:
  Won't Fix
Status in “libreoffice” package in Debian:
  New
Status in “libreoffice” package in Fedora:
  Unknown
Status in “libreoffice” package in openSUSE:
  Incomplete

Bug description:
  Binary package hint: openoffice.org-core

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

  2) apt-cache policy libreoffice-writer
  libreoffice-writer:
    Installed: 1:3.3.3-1ubuntu2
    Candidate: 1:3.3.3-1ubuntu2
    Version table:
   *** 1:3.3.3-1ubuntu2 0
  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

  3) What is expected to happen in documented exported from Writer
  opened in Word via the Terminal:

  cd ~/Desktop && wget
  
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/295014/+attachment/410599/+files/test_highlight.doc
  && wine ~/.wine/drive_c/Program\ Files/Microsoft\
  Office/OFFICE11/WINWORD.EXE test_highlight.doc

  click the Highlight button -> No Fill and the highlight is removed.

  4) What happens instead is the highlight is not removed.

  WORKAROUND: In Word click Format -> Boarders and Shading... -> Shading
  tab -> click No Fill button -> under Preview change drop down Apply
  to: text -> OK button

  WORKAROUND: Use AbiWord to export documents with highlighting.

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/295014/+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 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.

[Romano Giannetti]

Ok, checked more; color me less happy.

Definitely the layout switch does not work after suspend in the lock
screen. Hope you all people have password that can be typed in all
layouts, otherwise...

Also, with more than two layouts, the switch with the keys happens only
between two of them. The third one is accessible only via the applet
menu.

Sigh. This is the never ending story.

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

Title:
  Can't set keyboard layout change to alt+shift, ctrl+shift, etc.

Status in Gnome Settings Daemon:
  Invalid
Status in Ubuntu GNOME:
  Confirmed
Status in “gnome-control-center” package in Ubuntu:
  Fix Released
Status in “gnome-settings-daemon” package in Ubuntu:
  Triaged
Status in “gnome-settings-daemon” source package in Saucy:
  Triaged
Status in “gnome-control-center” package in ALT Linux:
  Unknown
Status in “gnome-control-center” package in Baltix:
  Confirmed
Status in “gnome-control-center” package in Gentoo Linux:
  Invalid
Status in “gnome-control-center” package in Mandriva:
  Invalid

Bug description:
  ***
  The old PPA, ppa:attente/1218322 is superceded by the following one. You can 
remove the old repository using ppa-purge.
  ***

  A PPA which should provide some relief for this issue is available at
  https://launchpad.net/~attente/+archive/modifier-only-input-switch. To
  install:

  sudo add-apt-repository ppa:attente/modifier-only-input-switch
  sudo apt-get update
  sudo apt-get upgrade
  (log out, log in)

  If the packages improve the situation for you, you can pin them using:

  sudo apt-mark hold compiz
  sudo apt-mark hold gnome-settings-daemon
  sudo apt-mark hold unity

  If the packages don't work for you, you can purge them using:

  sudo ppa-purge ppa:attente/modifier-only-input-switch

  === compiz ===

  Impact: modifier-only key bindings need to be independent of key-press
  order, there's no support for double tapping two modifier keys of the
  same type

  Test case:
  - add at least two input sources through gnome-control-center's text entry 
settings
  - use gsettings to set the input switching shortcut to ctrl+left shift: 
gsettings set org.gnome.desktop.wm.keybindings switch-input-source 
"['Shift_L']"
  - holding left shift, press and release ctrl
  -> the current input source should change

  Regression potential: possible, but highly unlikely, that some key
  bindings may be triggered due to the removal of some code that would
  normally prevent a possible tap from occurring.

  === unity ===

  Impact: gnome-settings-daemon eats modifier-only shortcuts preventing
  them from propagating down to applications

  Test case:
  - open gnome-control-center's text input settings
  - set the next input source key binding to ctrl+left shift
  - open gnome-terminal
  - press ctrl+shift+t
  -> gnome-terminal should open a new tab

  Regression potential: the additional input switch key bindings could
  collide with other functionality such as opening the dash or hud

  === gnome-control-center ===

  Impact: the UI to change the layout switching keys doesn't work

  Test case:
  - open gnome-control-center's text input settings
  - click on the "next layout key" entry
  - try entering a key combinaison (e.g ctrl-space)
  -> the UI should reflect the new keys

  Regression potential: that UI was not working before, it should only
  be an improvement (some key combos are not working as expected, that's
  another issue and shouldn't be mixed with this one)

  === gnome-settings-daemon ===

  Impact: attempting to change keyboard layouts using only modifier keys
  doesn't work

  Test case:
  - add at least two input sources through gnome-control-center's text entry 
settings
  - use gsettings to set the input switching shortcut to ctrl+left shift: 
gsettings set org.gnome.desktop.wm.keybindings switch-input-source 
"['Shift_L']"
  - press and release ctrl+left shift
  -> the current input source should change

  Regression potential: The input switching shortcut might capture other
  non-modifier shortcuts, but users will need to consider this when
  choosing their switching shortcut anyways. For users this bug affects,
  this represents a working solution for a critical bug.

  --

  Test results for different keyboard layout change hotkeys may be
  viewed and added in the Google Docs table, created by Norbert
  
(https://docs.google.com/spreadsheet/ccc?key=0Ao5e713Ig9g_dEJrX2NRYlpLWWVzSWxsVXU4ck9HYVE&usp=sharing).

  --
  Recent discovered bugs related to keyboard layouts:
     * keyboard layout settings must be consistent between gnome-control-center 
keyboard, indicator-keyboard and gnome-tweak-tool and /etc/default/keyboard 
(bug 1270574)
     * Ubuntu 14.04 should have gnome-tweak-tool installed by default because 
of many settings that are missed gnome-control-cen

[Desktop-packages] [Bug 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.

[Romano Giannetti]

I just downloaded and installed in a VirtualBox Ubuntu-Gnome 14.04 beta2
32bit.

Out of the box, I changed the "Switch to next sorce"  to Alt+Shift L and
""alternative character key" to Right Alt and it works ok.

I DID NOT test the plain Ubuntu-Unity installation.

Color me (momentarily) happy.

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

Title:
  Can't set keyboard layout change to alt+shift, ctrl+shift, etc.

Status in Gnome Settings Daemon:
  Invalid
Status in Ubuntu GNOME:
  Confirmed
Status in “gnome-control-center” package in Ubuntu:
  Fix Released
Status in “gnome-settings-daemon” package in Ubuntu:
  Triaged
Status in “gnome-settings-daemon” source package in Saucy:
  Triaged
Status in “gnome-control-center” package in ALT Linux:
  Unknown
Status in “gnome-control-center” package in Baltix:
  Confirmed
Status in “gnome-control-center” package in Gentoo Linux:
  Invalid
Status in “gnome-control-center” package in Mandriva:
  Invalid

Bug description:
  ***
  The old PPA, ppa:attente/1218322 is superceded by the following one. You can 
remove the old repository using ppa-purge.
  ***

  A PPA which should provide some relief for this issue is available at
  https://launchpad.net/~attente/+archive/modifier-only-input-switch. To
  install:

  sudo add-apt-repository ppa:attente/modifier-only-input-switch
  sudo apt-get update
  sudo apt-get upgrade
  (log out, log in)

  If the packages improve the situation for you, you can pin them using:

  sudo apt-mark hold compiz
  sudo apt-mark hold gnome-settings-daemon
  sudo apt-mark hold unity

  If the packages don't work for you, you can purge them using:

  sudo ppa-purge ppa:attente/modifier-only-input-switch

  === compiz ===

  Impact: modifier-only key bindings need to be independent of key-press
  order, there's no support for double tapping two modifier keys of the
  same type

  Test case:
  - add at least two input sources through gnome-control-center's text entry 
settings
  - use gsettings to set the input switching shortcut to ctrl+left shift: 
gsettings set org.gnome.desktop.wm.keybindings switch-input-source 
"['Shift_L']"
  - holding left shift, press and release ctrl
  -> the current input source should change

  Regression potential: possible, but highly unlikely, that some key
  bindings may be triggered due to the removal of some code that would
  normally prevent a possible tap from occurring.

  === unity ===

  Impact: gnome-settings-daemon eats modifier-only shortcuts preventing
  them from propagating down to applications

  Test case:
  - open gnome-control-center's text input settings
  - set the next input source key binding to ctrl+left shift
  - open gnome-terminal
  - press ctrl+shift+t
  -> gnome-terminal should open a new tab

  Regression potential: the additional input switch key bindings could
  collide with other functionality such as opening the dash or hud

  === gnome-control-center ===

  Impact: the UI to change the layout switching keys doesn't work

  Test case:
  - open gnome-control-center's text input settings
  - click on the "next layout key" entry
  - try entering a key combinaison (e.g ctrl-space)
  -> the UI should reflect the new keys

  Regression potential: that UI was not working before, it should only
  be an improvement (some key combos are not working as expected, that's
  another issue and shouldn't be mixed with this one)

  === gnome-settings-daemon ===

  Impact: attempting to change keyboard layouts using only modifier keys
  doesn't work

  Test case:
  - add at least two input sources through gnome-control-center's text entry 
settings
  - use gsettings to set the input switching shortcut to ctrl+left shift: 
gsettings set org.gnome.desktop.wm.keybindings switch-input-source 
"['Shift_L']"
  - press and release ctrl+left shift
  -> the current input source should change

  Regression potential: The input switching shortcut might capture other
  non-modifier shortcuts, but users will need to consider this when
  choosing their switching shortcut anyways. For users this bug affects,
  this represents a working solution for a critical bug.

  --

  Test results for different keyboard layout change hotkeys may be
  viewed and added in the Google Docs table, created by Norbert
  
(https://docs.google.com/spreadsheet/ccc?key=0Ao5e713Ig9g_dEJrX2NRYlpLWWVzSWxsVXU4ck9HYVE&usp=sharing).

  --
  Recent discovered bugs related to keyboard layouts:
     * keyboard layout settings must be consistent between gnome-control-center 
keyboard, indicator-keyboard and gnome-tweak-tool and /etc/default/keyboard 
(bug 1270574)
     * Ubuntu 14.04 should have gnome-tweak-tool installed by default because 
of many settings that are missed gnome-control-center (bug 1270572)
     * Please add ability to set keyboard shortcuts to unity-control-c

[Desktop-packages] [Bug 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.

[Romano Giannetti]

@Norbert, I will try with a new user, but about removing all my hidden
folders... I imagine this is a joke ;-). I have 20+ years of
configurations of my system, ssh keys, applications defaults, qucs and
spice models, vim macros, whatever in it (yes, all of this is regularly
backed up). I *really* prefer using the applet to switch layouts and
waiting for 14.04 or Fedora N+1 than going through a painful piece by
piece bisection of all the dot files.

Which are the hidden conf files that will affect keyboard switching
behavior? Without this information the rest is voodoo.

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

Title:
  Can't set keyboard layout change to alt+shift, ctrl+shift, etc.

Status in Gnome Settings Daemon:
  Invalid
Status in Ubuntu GNOME:
  Confirmed
Status in “gnome-control-center” package in Ubuntu:
  Fix Released
Status in “gnome-settings-daemon” package in Ubuntu:
  Triaged
Status in “gnome-settings-daemon” source package in Saucy:
  Triaged
Status in “gnome-control-center” package in ALT Linux:
  Unknown
Status in “gnome-control-center” package in Baltix:
  New
Status in “gnome-control-center” package in Gentoo Linux:
  Invalid
Status in “gnome-control-center” package in Mandriva:
  Invalid

Bug description:
  ***
  The old PPA, ppa:attente/1218322 is superceded by the following one. You can 
remove the old repository using ppa-purge.
  ***

  A PPA which should provide some relief for this issue is available at
  https://launchpad.net/~attente/+archive/modifier-only-input-switch. To
  install:

  sudo add-apt-repository ppa:attente/modifier-only-input-switch
  sudo apt-get update
  sudo apt-get upgrade
  (log out, log in)

  If the packages improve the situation for you, you can pin them using:

  sudo apt-mark hold compiz
  sudo apt-mark hold gnome-settings-daemon
  sudo apt-mark hold unity

  If the packages don't work for you, you can purge them using:

  sudo ppa-purge ppa:attente/modifier-only-input-switch

  === compiz ===

  Impact: modifier-only key bindings need to be independent of key-press
  order, there's no support for double tapping two modifier keys of the
  same type

  Test case:
  - add at least two input sources through gnome-control-center's text entry 
settings
  - use gsettings to set the input switching shortcut to ctrl+left shift: 
gsettings set org.gnome.desktop.wm.keybindings switch-input-source 
"['Shift_L']"
  - holding left shift, press and release ctrl
  -> the current input source should change

  Regression potential: possible, but highly unlikely, that some key
  bindings may be triggered due to the removal of some code that would
  normally prevent a possible tap from occurring.

  === unity ===

  Impact: gnome-settings-daemon eats modifier-only shortcuts preventing
  them from propagating down to applications

  Test case:
  - open gnome-control-center's text input settings
  - set the next input source key binding to ctrl+left shift
  - open gnome-terminal
  - press ctrl+shift+t
  -> gnome-terminal should open a new tab

  Regression potential: the additional input switch key bindings could
  collide with other functionality such as opening the dash or hud

  === gnome-control-center ===

  Impact: the UI to change the layout switching keys doesn't work

  Test case:
  - open gnome-control-center's text input settings
  - click on the "next layout key" entry
  - try entering a key combinaison (e.g ctrl-space)
  -> the UI should reflect the new keys

  Regression potential: that UI was not working before, it should only
  be an improvement (some key combos are not working as expected, that's
  another issue and shouldn't be mixed with this one)

  === gnome-settings-daemon ===

  Impact: attempting to change keyboard layouts using only modifier keys
  doesn't work

  Test case:
  - add at least two input sources through gnome-control-center's text entry 
settings
  - use gsettings to set the input switching shortcut to ctrl+left shift: 
gsettings set org.gnome.desktop.wm.keybindings switch-input-source 
"['Shift_L']"
  - press and release ctrl+left shift
  -> the current input source should change

  Regression potential: The input switching shortcut might capture other
  non-modifier shortcuts, but users will need to consider this when
  choosing their switching shortcut anyways. For users this bug affects,
  this represents a working solution for a critical bug.

  --

  Test results for different keyboard layout change hotkeys may be
  viewed and added in the Google Docs table, created by Norbert
  
(https://docs.google.com/spreadsheet/ccc?key=0Ao5e713Ig9g_dEJrX2NRYlpLWWVzSWxsVXU4ck9HYVE&usp=sharing).

  --
  Recent discovered bugs related to keyboard layouts:
     * keyboard layout settings must be consistent between gnome-control-center 
keyboard, indicator-keyboard and gn

[Desktop-packages] [Bug 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.

[Romano Giannetti]

...and for me, now Alt+Shift switches the indicator but *not* the
keyboard. I have to switch the layout with the applet.

Is there anyone with a link on documentation on how the keyboard is
managed/configured in Ubuntu (for real)? There is a mix of xkbd, gnome-
settings, xmodmap, gnome-tweak, dbus, etc that makes it a multi-
dimensional maze.

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

Title:
  Can't set keyboard layout change to alt+shift, ctrl+shift, etc.

Status in Gnome Settings Daemon:
  Invalid
Status in Ubuntu GNOME:
  Confirmed
Status in “gnome-control-center” package in Ubuntu:
  Fix Released
Status in “gnome-settings-daemon” package in Ubuntu:
  Triaged
Status in “gnome-settings-daemon” source package in Saucy:
  Triaged
Status in “gnome-control-center” package in ALT Linux:
  Unknown
Status in “gnome-control-center” package in Baltix:
  New
Status in “gnome-control-center” package in Gentoo Linux:
  Invalid
Status in “gnome-control-center” package in Mandriva:
  Invalid

Bug description:
  ***
  The old PPA, ppa:attente/1218322 is superceded by the following one. You can 
remove the old repository using ppa-purge.
  ***

  A PPA which should provide some relief for this issue is available at
  https://launchpad.net/~attente/+archive/modifier-only-input-switch. To
  install:

  sudo add-apt-repository ppa:attente/modifier-only-input-switch
  sudo apt-get update
  sudo apt-get upgrade
  (log out, log in)

  If the packages improve the situation for you, you can pin them using:

  sudo apt-mark hold compiz
  sudo apt-mark hold gnome-settings-daemon
  sudo apt-mark hold unity

  If the packages don't work for you, you can purge them using:

  sudo ppa-purge ppa:attente/modifier-only-input-switch

  === compiz ===

  Impact: modifier-only key bindings need to be independent of key-press
  order, there's no support for double tapping two modifier keys of the
  same type

  Test case:
  - add at least two input sources through gnome-control-center's text entry 
settings
  - use gsettings to set the input switching shortcut to ctrl+left shift: 
gsettings set org.gnome.desktop.wm.keybindings switch-input-source 
"['Shift_L']"
  - holding left shift, press and release ctrl
  -> the current input source should change

  Regression potential: possible, but highly unlikely, that some key
  bindings may be triggered due to the removal of some code that would
  normally prevent a possible tap from occurring.

  === unity ===

  Impact: gnome-settings-daemon eats modifier-only shortcuts preventing
  them from propagating down to applications

  Test case:
  - open gnome-control-center's text input settings
  - set the next input source key binding to ctrl+left shift
  - open gnome-terminal
  - press ctrl+shift+t
  -> gnome-terminal should open a new tab

  Regression potential: the additional input switch key bindings could
  collide with other functionality such as opening the dash or hud

  === gnome-control-center ===

  Impact: the UI to change the layout switching keys doesn't work

  Test case:
  - open gnome-control-center's text input settings
  - click on the "next layout key" entry
  - try entering a key combinaison (e.g ctrl-space)
  -> the UI should reflect the new keys

  Regression potential: that UI was not working before, it should only
  be an improvement (some key combos are not working as expected, that's
  another issue and shouldn't be mixed with this one)

  === gnome-settings-daemon ===

  Impact: attempting to change keyboard layouts using only modifier keys
  doesn't work

  Test case:
  - add at least two input sources through gnome-control-center's text entry 
settings
  - use gsettings to set the input switching shortcut to ctrl+left shift: 
gsettings set org.gnome.desktop.wm.keybindings switch-input-source 
"['Shift_L']"
  - press and release ctrl+left shift
  -> the current input source should change

  Regression potential: The input switching shortcut might capture other
  non-modifier shortcuts, but users will need to consider this when
  choosing their switching shortcut anyways. For users this bug affects,
  this represents a working solution for a critical bug.

  --

  Test results for different keyboard layout change hotkeys may be
  viewed and added in the Google Docs table, created by Norbert
  
(https://docs.google.com/spreadsheet/ccc?key=0Ao5e713Ig9g_dEJrX2NRYlpLWWVzSWxsVXU4ck9HYVE&usp=sharing).

  --
  Recent discovered bugs related to keyboard layouts:
     * keyboard layout settings must be consistent between gnome-control-center 
keyboard, indicator-keyboard and gnome-tweak-tool and /etc/default/keyboard 
(bug 1270574)
 * Ubuntu 14.04 should have gnome-tweak-tool installed by default because 
of many settings that are missed gnome-control-center (bug 1270572)


  Separate bug reports

[Desktop-packages] [Bug 1281250] [NEW] VNC accessible for Windows machines only with encryption disabled

[Romano Giannetti]

Public bug reported:

Since a recent update, it is impossible to connect to my Ubuntu box
using VNC from a Windows machine unless I disable encryption on the vino
server.

I tested up-to-date tightVNC client and TigerVNC client on the Windows
machine, with the same result. As soon I try to connect, I receive the
following error:

[ 5872/ 6448] 2014-01-20 12:11:18:247   List of security type is read
[ 5872/ 6448] 2014-01-20 12:11:18:247 : Security Types received (1): Unknown 
type (18)
[ 5872/ 6448] 2014-01-20 12:11:18:247   Selecting auth-handler
[ 5872/ 6448] 2014-01-20 12:11:18:247 + RemoteViewerCore. Exception: No 
security types supported. Server sent security types, but we do not support any 
of their.

So it seems that the update changed the security type of vino to a new
one. I searched for a way to go back to the old one (until the clients
catches up) with no avail.

A solution is disabling the encryption completely, by

gsettings set org.gnome.Vino require-encryption false

...but this is subotpimal. Is there a way to switch the encryption back
to the old one?

** Affects: vino
 Importance: Unknown
 Status: Unknown

** Affects: vino (Ubuntu)
 Importance: Undecided
 Status: New

** Summary changed:

- VNC accessible for WIndows machine only with encryption disabled
+ VNC accessible for Windows machines only with encryption disabled

** Bug watch added: Red Hat Bugzilla #981984
   https://bugzilla.redhat.com/show_bug.cgi?id=981984

** Also affects: vino via
   https://bugzilla.redhat.com/show_bug.cgi?id=981984
   Importance: Unknown
   Status: Unknown

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

Title:
  VNC accessible for Windows machines only with encryption disabled

Status in GNOME Remote Desktop:
  Unknown
Status in “vino” package in Ubuntu:
  New

Bug description:
  Since a recent update, it is impossible to connect to my Ubuntu box
  using VNC from a Windows machine unless I disable encryption on the
  vino server.

  I tested up-to-date tightVNC client and TigerVNC client on the Windows
  machine, with the same result. As soon I try to connect, I receive the
  following error:

  [ 5872/ 6448] 2014-01-20 12:11:18:247   List of security type is read
  [ 5872/ 6448] 2014-01-20 12:11:18:247 : Security Types received (1): Unknown 
type (18)
  [ 5872/ 6448] 2014-01-20 12:11:18:247   Selecting auth-handler
  [ 5872/ 6448] 2014-01-20 12:11:18:247 + RemoteViewerCore. Exception: No 
security types supported. Server sent security types, but we do not support any 
of their.

  So it seems that the update changed the security type of vino to a new
  one. I searched for a way to go back to the old one (until the clients
  catches up) with no avail.

  A solution is disabling the encryption completely, by

  gsettings set org.gnome.Vino require-encryption false

  ...but this is subotpimal. Is there a way to switch the encryption
  back to the old one?

To manage notifications about this bug go to:
https://bugs.launchpad.net/vino/+bug/1281250/+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 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.

[Romano Giannetti]

New behavior. Resetting the whole thing and choosing again Alt+Shift from the 
control panel works, but the HUD indication of the switch disappeared. 
This is the most desperately Heisenbug I ever found.

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

Title:
  Can't set keyboard layout change to alt+shift, ctrl+shift, etc.

Status in Gnome Settings Daemon:
  Invalid
Status in Ubuntu GNOME:
  Confirmed
Status in “gnome-control-center” package in Ubuntu:
  Fix Released
Status in “gnome-settings-daemon” package in Ubuntu:
  Triaged
Status in “gnome-settings-daemon” source package in Saucy:
  Triaged
Status in “gnome-control-center” package in ALT Linux:
  Unknown
Status in “gnome-control-center” package in Baltix:
  New
Status in “gnome-control-center” package in Gentoo Linux:
  Invalid
Status in “gnome-control-center” package in Mandriva:
  Invalid

Bug description:
  ***
  The old PPA, ppa:attente/1218322 is superceded by the following one. You can 
remove the old repository using ppa-purge.
  ***

  A PPA which should provide some relief for this issue is available at
  https://launchpad.net/~attente/+archive/modifier-only-input-switch. To
  install:

  sudo add-apt-repository ppa:attente/modifier-only-input-switch
  sudo apt-get update
  sudo apt-get upgrade
  (log out, log in)

  If the packages improve the situation for you, you can pin them using:

  sudo apt-mark hold compiz
  sudo apt-mark hold gnome-settings-daemon
  sudo apt-mark hold unity

  If the packages don't work for you, you can purge them using:

  sudo ppa-purge ppa:attente/modifier-only-input-switch

  === compiz ===

  Impact: modifier-only key bindings need to be independent of key-press
  order, there's no support for double tapping two modifier keys of the
  same type

  Test case:
  - add at least two input sources through gnome-control-center's text entry 
settings
  - use gsettings to set the input switching shortcut to ctrl+left shift: 
gsettings set org.gnome.desktop.wm.keybindings switch-input-source 
"['Shift_L']"
  - holding left shift, press and release ctrl
  -> the current input source should change

  Regression potential: possible, but highly unlikely, that some key
  bindings may be triggered due to the removal of some code that would
  normally prevent a possible tap from occurring.

  === unity ===

  Impact: gnome-settings-daemon eats modifier-only shortcuts preventing
  them from propagating down to applications

  Test case:
  - open gnome-control-center's text input settings
  - set the next input source key binding to ctrl+left shift
  - open gnome-terminal
  - press ctrl+shift+t
  -> gnome-terminal should open a new tab

  Regression potential: the additional input switch key bindings could
  collide with other functionality such as opening the dash or hud

  === gnome-control-center ===

  Impact: the UI to change the layout switching keys doesn't work

  Test case:
  - open gnome-control-center's text input settings
  - click on the "next layout key" entry
  - try entering a key combinaison (e.g ctrl-space)
  -> the UI should reflect the new keys

  Regression potential: that UI was not working before, it should only
  be an improvement (some key combos are not working as expected, that's
  another issue and shouldn't be mixed with this one)

  === gnome-settings-daemon ===

  Impact: attempting to change keyboard layouts using only modifier keys
  doesn't work

  Test case:
  - add at least two input sources through gnome-control-center's text entry 
settings
  - use gsettings to set the input switching shortcut to ctrl+left shift: 
gsettings set org.gnome.desktop.wm.keybindings switch-input-source 
"['Shift_L']"
  - press and release ctrl+left shift
  -> the current input source should change

  Regression potential: The input switching shortcut might capture other
  non-modifier shortcuts, but users will need to consider this when
  choosing their switching shortcut anyways. For users this bug affects,
  this represents a working solution for a critical bug.

  --

  Test results for different keyboard layout change hotkeys may be
  viewed and added in the Google Docs table, created by Norbert
  
(https://docs.google.com/spreadsheet/ccc?key=0Ao5e713Ig9g_dEJrX2NRYlpLWWVzSWxsVXU4ck9HYVE&usp=sharing).

  --
  Recent discovered bugs related to keyboard layouts:
     * keyboard layout settings must be consistent between gnome-control-center 
keyboard, indicator-keyboard and gnome-tweak-tool and /etc/default/keyboard 
(bug 1270574)
 * Ubuntu 14.04 should have gnome-tweak-tool installed by default because 
of many settings that are missed gnome-control-center (bug 1270572)


  Separate bug reports for individual layout switching hotkey
  combinations:

  Super+Space and Shift+Super+Space:
     * Unity greeter (bug 1245137);
     * Unit

[Desktop-packages] [Bug 381017]

[Romano Giannetti]

s/discreting/discrediting/ in the last message.

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

Title:
  Cannot drag attachment from mail attachment pane to desktop

Status in One Hundred Papercuts:
  Triaged
Status in SeaMonkey: all-in-one Internet application suite:
  Confirmed
Status in Mozilla Thunderbird Mail and News:
  Confirmed
Status in “thunderbird” package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 9.04
  Gnome Desktop 2.26.1
  Thunderbird 2.0.0.21

  This is regression introduced  in Jaunty as it works in Intrepid.
  Dragging an attachment from the attachment pane to the desktop give
  the following error:

  ==
  Error while copying
  There was an error getting information about "fetch>UID>.voicemail>1784".

  The specified location is not supported
  ==

  Mail account is IMAP. This error was shown to seb128 and asac. The
  expected behavior is that the file is copied to the destination onto
  which it is dragged.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/381017/+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 381017]

[Romano Giannetti]

@Paolo: sadly, it's probably true. I suppose we all got to grip with it
(I just stopped trying it and right-click and save, you know, even in
other mailer) but it is a very nasty (and, let me say, discreting) bug
to have around for so much time.

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

Title:
  Cannot drag attachment from mail attachment pane to desktop

Status in One Hundred Papercuts:
  Triaged
Status in SeaMonkey: all-in-one Internet application suite:
  Confirmed
Status in Mozilla Thunderbird Mail and News:
  Confirmed
Status in “thunderbird” package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 9.04
  Gnome Desktop 2.26.1
  Thunderbird 2.0.0.21

  This is regression introduced  in Jaunty as it works in Intrepid.
  Dragging an attachment from the attachment pane to the desktop give
  the following error:

  ==
  Error while copying
  There was an error getting information about "fetch>UID>.voicemail>1784".

  The specified location is not supported
  ==

  Mail account is IMAP. This error was shown to seb128 and asac. The
  expected behavior is that the file is copied to the destination onto
  which it is dragged.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/381017/+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 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.

[Romano Giannetti]

I can confirm the regression. Alt+shift stopped working for me too and
re-setting it with gnome-tweak-tool does not work.

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

Title:
  Can't set keyboard layout change to alt+shift, ctrl+shift, etc.

Status in Gnome Settings Daemon:
  Invalid
Status in Ubuntu GNOME:
  Confirmed
Status in “gnome-control-center” package in Ubuntu:
  Fix Released
Status in “gnome-settings-daemon” package in Ubuntu:
  Triaged
Status in “gnome-settings-daemon” source package in Saucy:
  Triaged
Status in “gnome-control-center” package in ALT Linux:
  Unknown
Status in “gnome-control-center” package in Baltix:
  New
Status in “gnome-control-center” package in Gentoo Linux:
  Invalid
Status in “gnome-control-center” package in Mandriva:
  Invalid

Bug description:
  ***
  The old PPA, ppa:attente/1218322 is superceded by the following one. You can 
remove the old repository using ppa-purge.
  ***

  A PPA which should provide some relief for this issue is available at
  https://launchpad.net/~attente/+archive/modifier-only-input-switch. To
  install:

  sudo add-apt-repository ppa:attente/modifier-only-input-switch
  sudo apt-get update
  sudo apt-get upgrade
  (log out, log in)

  If the packages improve the situation for you, you can pin them using:

  sudo apt-mark hold compiz
  sudo apt-mark hold gnome-settings-daemon
  sudo apt-mark hold unity

  If the packages don't work for you, you can purge them using:

  sudo ppa-purge ppa:attente/modifier-only-input-switch

  === compiz ===

  Impact: modifier-only key bindings need to be independent of key-press
  order, there's no support for double tapping two modifier keys of the
  same type

  Test case:
  - add at least two input sources through gnome-control-center's text entry 
settings
  - use gsettings to set the input switching shortcut to ctrl+left shift: 
gsettings set org.gnome.desktop.wm.keybindings switch-input-source 
"['Shift_L']"
  - holding left shift, press and release ctrl
  -> the current input source should change

  Regression potential: possible, but highly unlikely, that some key
  bindings may be triggered due to the removal of some code that would
  normally prevent a possible tap from occurring.

  === unity ===

  Impact: gnome-settings-daemon eats modifier-only shortcuts preventing
  them from propagating down to applications

  Test case:
  - open gnome-control-center's text input settings
  - set the next input source key binding to ctrl+left shift
  - open gnome-terminal
  - press ctrl+shift+t
  -> gnome-terminal should open a new tab

  Regression potential: the additional input switch key bindings could
  collide with other functionality such as opening the dash or hud

  === gnome-control-center ===

  Impact: the UI to change the layout switching keys doesn't work

  Test case:
  - open gnome-control-center's text input settings
  - click on the "next layout key" entry
  - try entering a key combinaison (e.g ctrl-space)
  -> the UI should reflect the new keys

  Regression potential: that UI was not working before, it should only
  be an improvement (some key combos are not working as expected, that's
  another issue and shouldn't be mixed with this one)

  === gnome-settings-daemon ===

  Impact: attempting to change keyboard layouts using only modifier keys
  doesn't work

  Test case:
  - add at least two input sources through gnome-control-center's text entry 
settings
  - use gsettings to set the input switching shortcut to ctrl+left shift: 
gsettings set org.gnome.desktop.wm.keybindings switch-input-source 
"['Shift_L']"
  - press and release ctrl+left shift
  -> the current input source should change

  Regression potential: The input switching shortcut might capture other
  non-modifier shortcuts, but users will need to consider this when
  choosing their switching shortcut anyways. For users this bug affects,
  this represents a working solution for a critical bug.

  --

  Test results for different keyboard layout change hotkeys may be
  viewed and added in the Google Docs table, created by Norbert
  
(https://docs.google.com/spreadsheet/ccc?key=0Ao5e713Ig9g_dEJrX2NRYlpLWWVzSWxsVXU4ck9HYVE&usp=sharing).

  --
  Recent discovered bugs related to keyboard layouts:
     * keyboard layout settings must be consistent between gnome-control-center 
keyboard, indicator-keyboard and gnome-tweak-tool and /etc/default/keyboard 
(bug 1270574)
 * Ubuntu 14.04 should have gnome-tweak-tool installed by default because 
of many settings that are missed gnome-control-center (bug 1270572)


  Separate bug reports for individual layout switching hotkey
  combinations:

  Super+Space and Shift+Super+Space:
     * Unity greeter (bug 1245137);
     * Unity session (bug 1245136);
     * lock screen - gnome-screensaver (bug 1245138, bug 

[Desktop-packages] [Bug 295014] Re: [Upstream] Cannot remove highlight from .doc in Word exported from Writer

[Romano Giannetti]

** Attachment added: "Three files, showing the problem. Open .doc or .docx in 
MS word and try to remove the highlight."
   
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/295014/+attachment/3964662/+files/TestInteroperabilityt.zip

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

Title:
  [Upstream] Cannot remove highlight from .doc in Word exported from
  Writer

Status in LibreOffice Productivity Suite:
  Invalid
Status in The OpenOffice.org Suite:
  Confirmed
Status in “libreoffice” package in Ubuntu:
  Triaged
Status in “openoffice.org” package in Ubuntu:
  Won't Fix
Status in “libreoffice” package in Debian:
  New
Status in “libreoffice” package in Fedora:
  Unknown
Status in “libreoffice” package in openSUSE:
  Incomplete

Bug description:
  Binary package hint: openoffice.org-core

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

  2) apt-cache policy libreoffice-writer
  libreoffice-writer:
    Installed: 1:3.3.3-1ubuntu2
    Candidate: 1:3.3.3-1ubuntu2
    Version table:
   *** 1:3.3.3-1ubuntu2 0
  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

  3) What is expected to happen in documented exported from Writer
  opened in Word via the Terminal:

  cd ~/Desktop && wget
  
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/295014/+attachment/410599/+files/test_highlight.doc
  && wine ~/.wine/drive_c/Program\ Files/Microsoft\
  Office/OFFICE11/WINWORD.EXE test_highlight.doc

  click the Highlight button -> No Fill and the highlight is removed.

  4) What happens instead is the highlight is not removed.

  WORKAROUND: In Word click Format -> Boarders and Shading... -> Shading
  tab -> click No Fill button -> under Preview change drop down Apply
  to: text -> OK button

  WORKAROUND: Use AbiWord to export documents with highlighting.

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/295014/+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 295014] Re: [Upstream] Cannot remove highlight from .doc in Word exported from Writer

[Romano Giannetti]

So, as you can see form the attachment, it's still here in 4.2.0.4
(tested in Windows, but still).

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

Title:
  [Upstream] Cannot remove highlight from .doc in Word exported from
  Writer

Status in LibreOffice Productivity Suite:
  Invalid
Status in The OpenOffice.org Suite:
  Confirmed
Status in “libreoffice” package in Ubuntu:
  Triaged
Status in “openoffice.org” package in Ubuntu:
  Won't Fix
Status in “libreoffice” package in Debian:
  New
Status in “libreoffice” package in Fedora:
  Unknown
Status in “libreoffice” package in openSUSE:
  Incomplete

Bug description:
  Binary package hint: openoffice.org-core

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

  2) apt-cache policy libreoffice-writer
  libreoffice-writer:
    Installed: 1:3.3.3-1ubuntu2
    Candidate: 1:3.3.3-1ubuntu2
    Version table:
   *** 1:3.3.3-1ubuntu2 0
  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

  3) What is expected to happen in documented exported from Writer
  opened in Word via the Terminal:

  cd ~/Desktop && wget
  
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/295014/+attachment/410599/+files/test_highlight.doc
  && wine ~/.wine/drive_c/Program\ Files/Microsoft\
  Office/OFFICE11/WINWORD.EXE test_highlight.doc

  click the Highlight button -> No Fill and the highlight is removed.

  4) What happens instead is the highlight is not removed.

  WORKAROUND: In Word click Format -> Boarders and Shading... -> Shading
  tab -> click No Fill button -> under Preview change drop down Apply
  to: text -> OK button

  WORKAROUND: Use AbiWord to export documents with highlighting.

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/295014/+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