[Touch-packages] [Bug 1816757] [NEW] Facing an issue related to XRDP for RDP thinclients. Only once XRDP login screen appears in thinclient, trying to login session disconnect.

2019-02-20 Thread Mahesh Surwar
Public bug reported:


Facing an issue related to XRDP for RDP thinclients. Only once XRDP
login screen appears in thinclient, trying to login session disconnect.
If want login screen again must restart main system, then only get login
screen, then same issue repeats. Please help me on this issue.

Steps taken to Troubleshoot issue:

Uninstalled XRDP services completely and reinstalled.
Formatted OS and reinstalled XRDP services.

Note: xrdp service tried with the following OS Ubuntu 12.04LTS, Ubuntu
14.04LTS Linux mint 17

** Affects: dbus (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: and xfce4 xrdp

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1816757

Title:
Facing an issue related to XRDP for RDP thinclients. Only once XRDP
  login screen appears in thinclient, trying to login session
  disconnect.

Status in dbus package in Ubuntu:
  New

Bug description:

  Facing an issue related to XRDP for RDP thinclients. Only once XRDP
  login screen appears in thinclient, trying to login session
  disconnect. If want login screen again must restart main system, then
  only get login screen, then same issue repeats. Please help me on this
  issue.

  Steps taken to Troubleshoot issue:

  Uninstalled XRDP services completely and reinstalled.
  Formatted OS and reinstalled XRDP services.

  Note: xrdp service tried with the following OS Ubuntu 12.04LTS, Ubuntu
  14.04LTS Linux mint 17

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1816757/+subscriptions

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


[Touch-packages] [Bug 1787115] [NEW] No display on hdmi1

2018-08-15 Thread Mahesh
Public bug reported:

Hdmi1 and sound on Hdmi1 not working. In ubuntu 16.04 it was working
perfectly.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-31.33-generic 4.15.18
Uname: Linux 4.15.0-31-generic x86_64
NonfreeKernelModules: wl
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.3
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Wed Aug 15 13:14:19 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.30.223.271+bdcom, 4.15.0-29-generic, x86_64: installed
 bcmwl, 6.30.223.271+bdcom, 4.15.0-31-generic, x86_64: installed
 virtualbox, 5.2.10, 4.15.0-26-generic, x86_64: installed
 virtualbox, 5.2.10, 4.15.0-29-generic, x86_64: installed
 virtualbox, 5.2.10, 4.15.0-31-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:3975]
InstallationDate: Installed on 2017-12-31 (226 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
MachineType: LENOVO HuronRiver Platform
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-31-generic 
root=UUID=06c9bcee-717f-4abd-aff0-9f3b1d431be5 ro acpi = force
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/27/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 44CN43WW
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Emerald Lake
dmi.board.vendor: LENOVO
dmi.board.version: FAB1
dmi.chassis.asset.tag: Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: 0.1
dmi.modalias: 
dmi:bvnLENOVO:bvr44CN43WW:bd10/27/2011:svnLENOVO:pnHuronRiverPlatform:pvrLenovoB570:rvnLENOVO:rnEmeraldLake:rvrFAB1:cvnLENOVO:ct10:cvr0.1:
dmi.product.family: HuronRiver System
dmi.product.name: HuronRiver Platform
dmi.product.version: Lenovo B570
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.5-0~b~padoka0
version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.5-0~b~padoka0
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Fri Aug  3 22:21:54 2018
xserver.configfile: /etc/X11/xorg.conf
xserver.devices:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.19.6-1ubuntu4

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


** Tags: amd64 apport-bug bionic third-party-packages ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1787115

Title:
  No display on hdmi1

Status in xorg package in Ubuntu:
  New

Bug description:
  Hdmi1 and sound on Hdmi1 not working. In ubuntu 16.04 it was working
  perfectly.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-31.33-generic 4.15.18
  Uname: Linux 4.15.0-31-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed Aug 15 13:14:19 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-29-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-31-generic, x86_64: installed
   virtualbox, 5.2.10, 4.15.0-26-generic, x86_64: installed
   virtualbox, 5.2.10, 4.15.0-29-generic, x86_64: installed
   virtualbox, 5.2.10, 4.15.0-31-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:3975]
  InstallationDate: Installed on 2017-12-31 (226 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: LENOVO HuronRiver Platform
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.

[Touch-packages] [Bug 1771598] [NEW] package sudo 1.8.21p2-3ubuntu1 failed to install/upgrade: installed sudo package pre-removal script subprocess returned error exit status 1

2018-05-16 Thread Mahesh
Public bug reported:

Hi, I tried editing the sudoers that is located on my Ubuntu setup on
Virtual Box, it didn't allow me to update sudoers due to permission
issues. I changed the permission of sudoers to 777 and was able to add
my user name into it, however after that I was not able to run few
commands hence I got instruction from google to purge and re-install it
however it started throwing error afterwards however I noticed that I
was able to remove my username entries from it before re-installing.
Please suggest if I would need to re-install ubuntu on my virtual box or
the current setup would work as before ?

Thanks,
Mahesh Bhatia

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: sudo 1.8.21p2-3ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
AptOrdering:
 ubuntu-minimal:amd64: Purge
 sudo:amd64: Purge
 NULL: ConfigurePending
 NULL: PurgePending
 NULL: ConfigurePending
Architecture: amd64
Date: Wed May 16 16:17:51 2018
ErrorMessage: installed sudo package pre-removal script subprocess returned 
error exit status 1
InstallationDate: Installed on 2018-05-15 (1 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 
'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] 
failed with exit code 1:", unpackaged
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: sudo
Title: package sudo 1.8.21p2-3ubuntu1 failed to install/upgrade: installed sudo 
package pre-removal script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
VisudoCheck:
 /etc/sudoers: parsed OK
 /etc/sudoers.d/README: parsed OK
mtime.conffile..etc.sudoers: 2018-05-16T16:12:29.233258

** Affects: sudo (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sudo in Ubuntu.
https://bugs.launchpad.net/bugs/1771598

Title:
  package sudo 1.8.21p2-3ubuntu1 failed to install/upgrade: installed
  sudo package pre-removal script subprocess returned error exit status
  1

Status in sudo package in Ubuntu:
  New

Bug description:
  Hi, I tried editing the sudoers that is located on my Ubuntu setup on
  Virtual Box, it didn't allow me to update sudoers due to permission
  issues. I changed the permission of sudoers to 777 and was able to add
  my user name into it, however after that I was not able to run few
  commands hence I got instruction from google to purge and re-install
  it however it started throwing error afterwards however I noticed that
  I was able to remove my username entries from it before re-installing.
  Please suggest if I would need to re-install ubuntu on my virtual box
  or the current setup would work as before ?

  Thanks,
  Mahesh Bhatia

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: sudo 1.8.21p2-3ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  AptOrdering:
   ubuntu-minimal:amd64: Purge
   sudo:amd64: Purge
   NULL: ConfigurePending
   NULL: PurgePending
   NULL: ConfigurePending
  Architecture: amd64
  Date: Wed May 16 16:17:51 2018
  ErrorMessage: installed sudo package pre-removal script subprocess returned 
error exit status 1
  InstallationDate: Installed on 2018-05-15 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 
'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] 
failed with exit code 1:", unpackaged
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: sudo
  Title: package sudo 1.8.21p2-3ubuntu1 failed to install/upgrade: installed 
sudo package pre-removal script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  VisudoCheck:
   /etc/sudoers: parsed OK
   /etc/sudoers.d/README: parsed OK
  mtime.conffile..etc.sudoers: 2018-05-16T16:12:29.233258

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1771598/+subscriptions

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


[Touch-packages] [Bug 706011] Re: gpg --key-gen doesn't have enough entropy and rng-tools install/start fails

2015-02-26 Thread J Phani Mahesh
I should have read the blog post you linked to before posting the
comment. There are no factual errors in the blog post to my knowledge
(I'm no professional cryptographer, just an enthusiast who took a couple
formal courses and tinkered a bit), and the argument is compelling.

My previous comment actually looks silly now, since I talk of "good"
random data that the post disputes. But I stand my ground that using
/dev/urandom for serious business like GPG keys is a bad idea.
/dev/random providess a better guarantee than /dev/urandom regarding the
randomness of data you extract, and many including me are not happy to
give up this guarantee.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnupg in Ubuntu.
https://bugs.launchpad.net/bugs/706011

Title:
  gpg --key-gen doesn't have enough entropy and rng-tools install/start
  fails

Status in gnupg package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: gnupg

  Description:  Ubuntu 10.04.1 LTS
  Release:  10.04

  
  If you install gpg and then type: gpg --gen-key, it 'freezes up' during the 
entropy gathering phase.

  
  We need to generate a lot of random bytes. It is a good idea to perform
  some other action (type on the keyboard, move the mouse, utilize the
  disks) during the prime generation; this gives the random number
  generator a better chance to gain enough entropy.

  Not enough random bytes available.  Please do some other work to give
  the OS a chance to collect more entropy! (Need 278 more bytes)
  
  (freeze here)

  I found some reference on the interwebs suggesting to install rng-
  tools so that the rngd daemon can gather more entropy for the system
  because by default cat /proc/sys/kernel/random/entropy_avail has a
  very very low number.

  Thus, installation of rng-tools, fails to start the rngd daemon...

  Setting up rng-tools (2-unofficial-mt.12-1ubuntu3) ...
  Trying to create /dev/hwrng device inode...
  Starting Hardware RNG entropy gatherer daemon: (failed).
  invoke-rc.d: initscript rng-tools, action "start" failed.

  It is then required to do this: echo "HRNGDEVICE=/dev/urandom" >> 
/etc/default/rng-tools
  and then start rngd: /etc/init.d/rng-tools start

  After this process is done, gpg --gen-key is immediate...

  
  We need to generate a lot of random bytes. It is a good idea to perform
  some other action (type on the keyboard, move the mouse, utilize the
  disks) during the prime generation; this gives the random number
  generator a better chance to gain enough entropy.
  .+
  ...+
  We need to generate a lot of random bytes. It is a good idea to perform
  some other action (type on the keyboard, move the mouse, utilize the
  disks) during the prime generation; this gives the random number
  generator a better chance to gain enough entropy.
  +
  .+

  And cat /proc/sys/kernel/random/entropy_avail has a much higher
  number.

  All in all, I think this process should be simplified by maybe making
  gpg depend on rng-tools. The whole reason why I need to generate a gpg
  key is because I want to sign the .deb debians that I'm creating for
  my repository.

  Thanks for your time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnupg/+bug/706011/+subscriptions

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


[Touch-packages] [Bug 706011] Re: gpg --key-gen doesn't have enough entropy and rng-tools install/start fails

2015-02-26 Thread J Phani Mahesh
Then please do not believe that blog post. Because /dev/urandom is not a
source of entropy and can not be relied upon for any serious business.
It is in a sense a consumer of entropy available from /dev/random, that
does an expansion to provide pseudo random data even when there is no
entropy to produce good random data.

@Jon Stevens:

Crypto should not be messed with. Period. But your frustration is
understandable. Developers do not intend to be hostile to novice users
as you claim, but we have concerns that not all users will not be able
to appreciate. rng-tools has a valid use case, but the workaround
suggested in some comments to use /dev/urandom would scare the crap out
of any cryptographer. I wish it is disallowed altogether.


The most sensible suggestion comes from Alvaro in #25. Why hasn't there been 
more discussion on this? Security can't be compromised, but a better 
explanation to users doees no harm. I am skeptic of allowing a flag, it will be 
suggested as a workaround when it should not be, and users will follow the 
advice.

Rather, only when being run interactively, the user can be prompted
after a timeout if they want to reduce the key size and/or proceed with
just the available entropy, since it is taking long to collect enough
entropy. This option should be unavailable when being run non-
interactively, since I don't see the need and IMO allowing it does more
damage in the long run.

On a sidenote, rng-tools should atleast spit out a warning when
/dev/urandom is being used as a *HARDWARE* random number generator,
which it is not. Does not prevent anyone from creating a new device node
for urandom and using it, and circulating sequence of commands to be run
to accomplish that, but all user stupidity can not be safeguarded
against.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnupg in Ubuntu.
https://bugs.launchpad.net/bugs/706011

Title:
  gpg --key-gen doesn't have enough entropy and rng-tools install/start
  fails

Status in gnupg package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: gnupg

  Description:  Ubuntu 10.04.1 LTS
  Release:  10.04

  
  If you install gpg and then type: gpg --gen-key, it 'freezes up' during the 
entropy gathering phase.

  
  We need to generate a lot of random bytes. It is a good idea to perform
  some other action (type on the keyboard, move the mouse, utilize the
  disks) during the prime generation; this gives the random number
  generator a better chance to gain enough entropy.

  Not enough random bytes available.  Please do some other work to give
  the OS a chance to collect more entropy! (Need 278 more bytes)
  
  (freeze here)

  I found some reference on the interwebs suggesting to install rng-
  tools so that the rngd daemon can gather more entropy for the system
  because by default cat /proc/sys/kernel/random/entropy_avail has a
  very very low number.

  Thus, installation of rng-tools, fails to start the rngd daemon...

  Setting up rng-tools (2-unofficial-mt.12-1ubuntu3) ...
  Trying to create /dev/hwrng device inode...
  Starting Hardware RNG entropy gatherer daemon: (failed).
  invoke-rc.d: initscript rng-tools, action "start" failed.

  It is then required to do this: echo "HRNGDEVICE=/dev/urandom" >> 
/etc/default/rng-tools
  and then start rngd: /etc/init.d/rng-tools start

  After this process is done, gpg --gen-key is immediate...

  
  We need to generate a lot of random bytes. It is a good idea to perform
  some other action (type on the keyboard, move the mouse, utilize the
  disks) during the prime generation; this gives the random number
  generator a better chance to gain enough entropy.
  .+
  ...+
  We need to generate a lot of random bytes. It is a good idea to perform
  some other action (type on the keyboard, move the mouse, utilize the
  disks) during the prime generation; this gives the random number
  generator a better chance to gain enough entropy.
  +
  .+

  And cat /proc/sys/kernel/random/entropy_avail has a much higher
  number.

  All in all, I think this process should be simplified by maybe making
  gpg depend on rng-tools. The whole reason why I need to generate a gpg
  key is because I want to sign the .deb debians that I'm creating for
  my repository.

  Thanks for your time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnupg/+bug/706011/+subscriptions

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


[Touch-packages] [Bug 1400377] Re: snapping to portrait/landscape

2014-12-29 Thread J Phani Mahesh
Won't fix since it can't be "fixed" by unity tweak tool without support
from unity, and our project is limited to presenting various controls
exposed by unity.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1400377

Title:
  snapping to portrait/landscape

Status in Unity Tweak Tool:
  Won't Fix
Status in unity package in Ubuntu:
  New

Bug description:
  We can currently configure window snapping (take half the screen or
  the like) in unity-tweak-tool, this is nice. On a normal display, the
  screen is landscape so pushing window in side of screen split the
  screen in 2 (left/right) and pushing on top maximize the window. But
  on a portrait screen one would most likely want to split in 2
  (top/bottom).

  I would like to be able to configure either per screen or per layout
  (portrait/landscape) ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-tweak-tool/+bug/1400377/+subscriptions

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


[Touch-packages] [Bug 1400377] Re: snapping to portrait/landscape

2014-12-29 Thread J Phani Mahesh
This can be achieved by setting window snapping on chosen trigger eges
to top half and bottom half.

Per screen settings are not supported by unity to the best of my
knowledge, so unfortunately this is not possible right now. If you
manage to find any way this can be done, please inform us and we'll add
the feature after studying how it can be done.

Meanwhile, if you have both a portrait screen and a landscape screen,
and need snapping for top/bottom and left/right,  a workaround is to set
window snapping triggers on all four edges to fill the respective halves
( top edge for top half and so on) and use a corner for maximize.

Unity project may want to look at this feature-request, I am marking as
affects unity and closing for unity tweak tool.

** Also affects: unity (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: unity-tweak-tool
   Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1400377

Title:
  snapping to portrait/landscape

Status in Unity Tweak Tool:
  Won't Fix
Status in unity package in Ubuntu:
  New

Bug description:
  We can currently configure window snapping (take half the screen or
  the like) in unity-tweak-tool, this is nice. On a normal display, the
  screen is landscape so pushing window in side of screen split the
  screen in 2 (left/right) and pushing on top maximize the window. But
  on a portrait screen one would most likely want to split in 2
  (top/bottom).

  I would like to be able to configure either per screen or per layout
  (portrait/landscape) ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-tweak-tool/+bug/1400377/+subscriptions

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


[Touch-packages] [Bug 1309942] Re: Window Controls not functioning.

2014-09-05 Thread J Phani Mahesh
Unless there are changes made in Unity to respect user preferences, we
can not do anything. And it looks unlikely that any changes will happen
in Unity to allow this. Hence wont-fix for now. We'll revisit this when
there's a way to customize window control positions.

** Changed in: unity-tweak-tool
   Status: Triaged => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1309942

Title:
  Window Controls not functioning.

Status in Unity:
  New
Status in Unity Tweak Tool:
  Won't Fix
Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  As mentioned earlier the two key functions of Unity Tweak Tool are not
  working .

  1.Windows Control/ Allignment from left to right .
  2.Show menu button.

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

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