Re: [Touch-packages] [Bug 1459799] Re: segfaulting often

2015-06-08 Thread grinch
I tried again and this time it opened in a normal browser, chrome. I
authorized my computer to use my launchpad account. A pop-up came up and so
no additional data

Meanwhile, it's been an interesting day here:

Jun  8 08:30:36 casa kernel: [232828.464221] chrome[11066]: segfault at 0
ip 7fad449e3f58 sp 7fff0c8dc5f0 error 4 in
fglrx_dri.so[7fad4346d000+2338000]
Jun  8 14:54:28 casa kernel: [255855.181136] chrome[16107]: segfault at 0
ip 7fbccb0a2f58 sp 7ffc3dc8db90 error 4 in
fglrx_dri.so[7fbcc9b2c000+2338000]
Jun  8 14:54:37 casa kernel: [255864.274259] chrome[16855]: segfault at 0
ip 7fe983643f58 sp 7ffeea1498a0 error 4 in
fglrx_dri.so[7fe9820cd000+2338000]
Jun  8 14:54:38 casa kernel: [255865.630175] chrome[16882]: segfault at 0
ip 7f4530386f58 sp 7ffd1dad0d40 error 4 in
fglrx_dri.so[7f452ee1+2338000]
Jun  8 16:31:43 casa kernel: [261688.667430] chrome[18522]: segfault at 0
ip 7fe0bffb4f58 sp 7ffee63d54d0 error 4 in
fglrx_dri.so[7fe0bea3e000+2338000]
Jun  8 16:31:49 casa kernel: [261694.718339] chrome[19787]: segfault at 0
ip 7f20a5d71f58 sp 7ffe911df100 error 4 in
fglrx_dri.so[7f20a47fb000+2338000]

On Sat, Jun 6, 2015 at 5:38 PM, Digital Grinch 
wrote:

> not sure what you want me to do with that.
> I am not running in a live environment, I installed to disk
>
> Is there a way to generate the report you need to a file that can be
> attached or uploaded manually instead of trying to open a browser window in
> terminal?
>
> On Fri, Jun 5, 2015 at 2:04 AM, Christopher M. Penalver <
> christopher.m.penal...@gmail.com> wrote:
>
>> grinch, one may run the same command in a live environment via
>> http://cdimage.ubuntu.com/daily-live/current/ .
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1459799
>>
>> Title:
>>   segfaulting often
>>
>> Status in xorg package in Ubuntu:
>>   Incomplete
>>
>> Bug description:
>>   I am getting segfaults, often
>>
>>   May 27 19:17:41 casa kernel: [230291.611961] chromium-browse[25856]:
>> segfault at 0 ip 7ff5f8c72f58 sp 7ffc6ed21ff0 error 4 in
>> fglrx_dri.so[7ff5f76fc000+2338000]
>>   May 27 19:18:32 casa kernel: [230342.593157] chromium-browse[29174]:
>> segfault at 0 ip 7f9e11cf4f58 sp 7ffc677e4e00 error 4 in
>> fglrx_dri.so[7f9e1077e000+2338000]
>>   May 27 19:19:45 casa kernel: [230415.479260] chrome[22826]: segfault at
>> 0 ip 7f5dff1e5f58 sp 7ffc3b3fd380 error 4 in
>> fglrx_dri.so[7f5dfdc6f000+2338000]
>>   May 27 19:54:16 casa kernel: [232485.938279] chrome[29275]: segfault at
>> 0 ip 7fc9d976bf58 sp 7fff279fafa0 error 4 in
>> fglrx_dri.so[7fc9d81f5000+2338000]
>>   May 27 20:03:26 casa kernel: [233035.826317] chrome[30688]: segfault at
>> 0 ip 7f7447b98f58 sp 7ffdb8ae03f0 error 4 in
>> fglrx_dri.so[7f7446622000+2338000]
>>   May 28 11:11:44 casa kernel: [287522.202833] chrome[19799]: segfault at
>> 0 ip 7f58472adf58 sp 7ffc9db94490 error 4 in
>> fglrx_dri.so[7f5845d37000+2338000]
>>
>>   happens when browsing the internet, nothing crazy going on that would
>>   be "pushing" the drivers performance
>>
>>   I can't tell you the last time it worked, because I kept getting
>>   segfaults on older card, thought it was the card. bought new card and
>>   did fresh install, same issue(yes if X were working I could have saved
>>   a video card purchase)
>>
>>   no way to take a screenshot, and even if I did, it would just be a
>> black screen, because thats what happens.
>>   segfault > black screen > no terminals at all
>>   no ctrl+alt+F2 terminals access, etc
>>   I have to magic sysreq the system down with REISUB and that causes data
>> loss
>>
>>   please fix this
>>
>>   ProblemType: Bug
>>   DistroRelease: Ubuntu 15.04
>>   Package: xorg (not installed)
>>   ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
>>   Uname: Linux 3.19.0-18-generic x86_64
>>   NonfreeKernelModules: fglrx
>>   ApportVersion: 2.17.2-0ubuntu1.1
>>   Architecture: amd64
>>   Date: Thu May 28 15:18:39 2015
>>   InstallationDate: Installed on 2015-05-13 (15 days ago)
>>   InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Release amd64
>> (20150422)
>>   ProcEnviron:
>>TERM=screen
>>PATH=(custom, no user)
>>LANG=en_US.UTF-8
>>SHELL=/bin/bash
>>   SourcePackage: xorg
>>   UpgradeStatus: No upgrade log present (probably fresh install)
>>
>> To manage notifications abo

Re: [Touch-packages] [Bug 1459799] Re: segfaulting often

2015-06-06 Thread grinch
not sure what you want me to do with that.
I am not running in a live environment, I installed to disk

Is there a way to generate the report you need to a file that can be
attached or uploaded manually instead of trying to open a browser window in
terminal?

On Fri, Jun 5, 2015 at 2:04 AM, Christopher M. Penalver <
christopher.m.penal...@gmail.com> wrote:

> grinch, one may run the same command in a live environment via
> http://cdimage.ubuntu.com/daily-live/current/ .
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1459799
>
> Title:
>   segfaulting often
>
> Status in xorg package in Ubuntu:
>   Incomplete
>
> Bug description:
>   I am getting segfaults, often
>
>   May 27 19:17:41 casa kernel: [230291.611961] chromium-browse[25856]:
> segfault at 0 ip 7ff5f8c72f58 sp 7ffc6ed21ff0 error 4 in
> fglrx_dri.so[7ff5f76fc000+2338000]
>   May 27 19:18:32 casa kernel: [230342.593157] chromium-browse[29174]:
> segfault at 0 ip 7f9e11cf4f58 sp 7ffc677e4e00 error 4 in
> fglrx_dri.so[7f9e1077e000+2338000]
>   May 27 19:19:45 casa kernel: [230415.479260] chrome[22826]: segfault at
> 0 ip 7f5dff1e5f58 sp 7ffc3b3fd380 error 4 in
> fglrx_dri.so[7f5dfdc6f000+2338000]
>   May 27 19:54:16 casa kernel: [232485.938279] chrome[29275]: segfault at
> 0 ip 7fc9d976bf58 sp 7fff279fafa0 error 4 in
> fglrx_dri.so[7fc9d81f5000+2338000]
>   May 27 20:03:26 casa kernel: [233035.826317] chrome[30688]: segfault at
> 0 ip 7f7447b98f58 sp 7ffdb8ae03f0 error 4 in
> fglrx_dri.so[7f7446622000+2338000]
>   May 28 11:11:44 casa kernel: [287522.202833] chrome[19799]: segfault at
> 0 ip 7f58472adf58 sp 7ffc9db94490 error 4 in
> fglrx_dri.so[7f5845d37000+2338000]
>
>   happens when browsing the internet, nothing crazy going on that would
>   be "pushing" the drivers performance
>
>   I can't tell you the last time it worked, because I kept getting
>   segfaults on older card, thought it was the card. bought new card and
>   did fresh install, same issue(yes if X were working I could have saved
>   a video card purchase)
>
>   no way to take a screenshot, and even if I did, it would just be a black
> screen, because thats what happens.
>   segfault > black screen > no terminals at all
>   no ctrl+alt+F2 terminals access, etc
>   I have to magic sysreq the system down with REISUB and that causes data
> loss
>
>   please fix this
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 15.04
>   Package: xorg (not installed)
>   ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
>   Uname: Linux 3.19.0-18-generic x86_64
>   NonfreeKernelModules: fglrx
>   ApportVersion: 2.17.2-0ubuntu1.1
>   Architecture: amd64
>   Date: Thu May 28 15:18:39 2015
>   InstallationDate: Installed on 2015-05-13 (15 days ago)
>   InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Release amd64
> (20150422)
>   ProcEnviron:
>TERM=screen
>PATH=(custom, no user)
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   SourcePackage: xorg
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1459799/+subscriptions
>

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

Title:
  segfaulting often

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I am getting segfaults, often

  May 27 19:17:41 casa kernel: [230291.611961] chromium-browse[25856]: segfault 
at 0 ip 7ff5f8c72f58 sp 7ffc6ed21ff0 error 4 in 
fglrx_dri.so[7ff5f76fc000+2338000]
  May 27 19:18:32 casa kernel: [230342.593157] chromium-browse[29174]: segfault 
at 0 ip 7f9e11cf4f58 sp 7ffc677e4e00 error 4 in 
fglrx_dri.so[7f9e1077e000+2338000]
  May 27 19:19:45 casa kernel: [230415.479260] chrome[22826]: segfault at 0 ip 
7f5dff1e5f58 sp 7ffc3b3fd380 error 4 in 
fglrx_dri.so[7f5dfdc6f000+2338000]
  May 27 19:54:16 casa kernel: [232485.938279] chrome[29275]: segfault at 0 ip 
7fc9d976bf58 sp 7fff279fafa0 error 4 in 
fglrx_dri.so[7fc9d81f5000+2338000]
  May 27 20:03:26 casa kernel: [233035.826317] chrome[30688]: segfault at 0 ip 
7f7447b98f58 sp 7ffdb8ae03f0 error 4 in 
fglrx_dri.so[7f7446622000+2338000]
  May 28 11:11:44 casa kernel: [287522.202833] chrome[19799]: segfault at 0 ip 
7f58472adf58 sp 7ffc9db94490 error 4 in 
fglrx_dri.so[7f5845d37000+2338000]

  happens when browsing the internet, nothing crazy going on that would
  be "pushing" the drivers performance

  I can't tell you the last time it worked, becau

Re: [Touch-packages] [Bug 1459799] Re: segfaulting often

2015-06-03 Thread grinch
I would like to, but when I tried that, it tried opening a webpage, in my
terminal

On Sun, May 31, 2015 at 3:49 PM, Christopher M. Penalver <
christopher.m.penal...@gmail.com> wrote:

> grinch, thank you for reporting this and helping make Ubuntu better.
> Could you please run the following command from a terminal as it will
> automatically gather and attach updated debug information to this
> report:
>
> apport-collect -p xorg 1459799
>
> Please ensure you have xdiagnose installed, and that you click the Yes
> button for attaching additional debugging information.
>
> ** Changed in: xorg (Ubuntu)
>Importance: Undecided => Low
>
> ** Changed in: xorg (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1459799
>
> Title:
>   segfaulting often
>
> Status in xorg package in Ubuntu:
>   Incomplete
>
> Bug description:
>   I am getting segfaults, often
>
>   May 27 19:17:41 casa kernel: [230291.611961] chromium-browse[25856]:
> segfault at 0 ip 7ff5f8c72f58 sp 7ffc6ed21ff0 error 4 in
> fglrx_dri.so[7ff5f76fc000+2338000]
>   May 27 19:18:32 casa kernel: [230342.593157] chromium-browse[29174]:
> segfault at 0 ip 7f9e11cf4f58 sp 7ffc677e4e00 error 4 in
> fglrx_dri.so[7f9e1077e000+2338000]
>   May 27 19:19:45 casa kernel: [230415.479260] chrome[22826]: segfault at
> 0 ip 7f5dff1e5f58 sp 7ffc3b3fd380 error 4 in
> fglrx_dri.so[7f5dfdc6f000+2338000]
>   May 27 19:54:16 casa kernel: [232485.938279] chrome[29275]: segfault at
> 0 ip 7fc9d976bf58 sp 7fff279fafa0 error 4 in
> fglrx_dri.so[7fc9d81f5000+2338000]
>   May 27 20:03:26 casa kernel: [233035.826317] chrome[30688]: segfault at
> 0 ip 7f7447b98f58 sp 7ffdb8ae03f0 error 4 in
> fglrx_dri.so[7f7446622000+2338000]
>   May 28 11:11:44 casa kernel: [287522.202833] chrome[19799]: segfault at
> 0 ip 7f58472adf58 sp 7ffc9db94490 error 4 in
> fglrx_dri.so[7f5845d37000+2338000]
>
>   happens when browsing the internet, nothing crazy going on that would
>   be "pushing" the drivers performance
>
>   I can't tell you the last time it worked, because I kept getting
>   segfaults on older card, thought it was the card. bought new card and
>   did fresh install, same issue(yes if X were working I could have saved
>   a video card purchase)
>
>   no way to take a screenshot, and even if I did, it would just be a black
> screen, because thats what happens.
>   segfault > black screen > no terminals at all
>   no ctrl+alt+F2 terminals access, etc
>   I have to magic sysreq the system down with REISUB and that causes data
> loss
>
>   please fix this
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 15.04
>   Package: xorg (not installed)
>   ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
>   Uname: Linux 3.19.0-18-generic x86_64
>   NonfreeKernelModules: fglrx
>   ApportVersion: 2.17.2-0ubuntu1.1
>   Architecture: amd64
>   Date: Thu May 28 15:18:39 2015
>   InstallationDate: Installed on 2015-05-13 (15 days ago)
>   InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Release amd64
> (20150422)
>   ProcEnviron:
>TERM=screen
>PATH=(custom, no user)
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   SourcePackage: xorg
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1459799/+subscriptions
>

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

Title:
  segfaulting often

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I am getting segfaults, often

  May 27 19:17:41 casa kernel: [230291.611961] chromium-browse[25856]: segfault 
at 0 ip 7ff5f8c72f58 sp 7ffc6ed21ff0 error 4 in 
fglrx_dri.so[7ff5f76fc000+2338000]
  May 27 19:18:32 casa kernel: [230342.593157] chromium-browse[29174]: segfault 
at 0 ip 7f9e11cf4f58 sp 7ffc677e4e00 error 4 in 
fglrx_dri.so[7f9e1077e000+2338000]
  May 27 19:19:45 casa kernel: [230415.479260] chrome[22826]: segfault at 0 ip 
7f5dff1e5f58 sp 7ffc3b3fd380 error 4 in 
fglrx_dri.so[7f5dfdc6f000+2338000]
  May 27 19:54:16 casa kernel: [232485.938279] chrome[29275]: segfault at 0 ip 
7fc9d976bf58 sp 7fff279fafa0 error 4 in 
fglrx_dri.so[7fc9d81f5000+2338000]
  May 27 20:03:26 casa kernel: [233035.826317] chrome[30688]: segfault at 0 ip 
7f7447b98f58 sp 7ffdb8ae03f0 error 4 in 
fglrx_dri.so[7f7446622000+2338000]
  May 28 11:11:44 casa kernel: [287522.202833] chrome[19799

[Touch-packages] [Bug 1459799] [NEW] segfaulting often

2015-05-28 Thread grinch
Public bug reported:

I am getting segfaults, often

May 27 19:17:41 casa kernel: [230291.611961] chromium-browse[25856]: segfault 
at 0 ip 7ff5f8c72f58 sp 7ffc6ed21ff0 error 4 in 
fglrx_dri.so[7ff5f76fc000+2338000]
May 27 19:18:32 casa kernel: [230342.593157] chromium-browse[29174]: segfault 
at 0 ip 7f9e11cf4f58 sp 7ffc677e4e00 error 4 in 
fglrx_dri.so[7f9e1077e000+2338000]
May 27 19:19:45 casa kernel: [230415.479260] chrome[22826]: segfault at 0 ip 
7f5dff1e5f58 sp 7ffc3b3fd380 error 4 in 
fglrx_dri.so[7f5dfdc6f000+2338000]
May 27 19:54:16 casa kernel: [232485.938279] chrome[29275]: segfault at 0 ip 
7fc9d976bf58 sp 7fff279fafa0 error 4 in 
fglrx_dri.so[7fc9d81f5000+2338000]
May 27 20:03:26 casa kernel: [233035.826317] chrome[30688]: segfault at 0 ip 
7f7447b98f58 sp 7ffdb8ae03f0 error 4 in 
fglrx_dri.so[7f7446622000+2338000]
May 28 11:11:44 casa kernel: [287522.202833] chrome[19799]: segfault at 0 ip 
7f58472adf58 sp 7ffc9db94490 error 4 in 
fglrx_dri.so[7f5845d37000+2338000]

happens when browsing the internet, nothing crazy going on that would be
"pushing" the drivers performance

I can't tell you the last time it worked, because I kept getting
segfaults on older card, thought it was the card. bought new card and
did fresh install, same issue(yes if X were working I could have saved a
video card purchase)

no way to take a screenshot, and even if I did, it would just be a black 
screen, because thats what happens. 
segfault > black screen > no terminals at all
no ctrl+alt+F2 terminals access, etc
I have to magic sysreq the system down with REISUB and that causes data loss

please fix this

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: xorg (not installed)
ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
Uname: Linux 3.19.0-18-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: amd64
Date: Thu May 28 15:18:39 2015
InstallationDate: Installed on 2015-05-13 (15 days ago)
InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Release amd64 (20150422)
ProcEnviron:
 TERM=screen
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug vivid

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

Title:
  segfaulting often

Status in xorg package in Ubuntu:
  New

Bug description:
  I am getting segfaults, often

  May 27 19:17:41 casa kernel: [230291.611961] chromium-browse[25856]: segfault 
at 0 ip 7ff5f8c72f58 sp 7ffc6ed21ff0 error 4 in 
fglrx_dri.so[7ff5f76fc000+2338000]
  May 27 19:18:32 casa kernel: [230342.593157] chromium-browse[29174]: segfault 
at 0 ip 7f9e11cf4f58 sp 7ffc677e4e00 error 4 in 
fglrx_dri.so[7f9e1077e000+2338000]
  May 27 19:19:45 casa kernel: [230415.479260] chrome[22826]: segfault at 0 ip 
7f5dff1e5f58 sp 7ffc3b3fd380 error 4 in 
fglrx_dri.so[7f5dfdc6f000+2338000]
  May 27 19:54:16 casa kernel: [232485.938279] chrome[29275]: segfault at 0 ip 
7fc9d976bf58 sp 7fff279fafa0 error 4 in 
fglrx_dri.so[7fc9d81f5000+2338000]
  May 27 20:03:26 casa kernel: [233035.826317] chrome[30688]: segfault at 0 ip 
7f7447b98f58 sp 7ffdb8ae03f0 error 4 in 
fglrx_dri.so[7f7446622000+2338000]
  May 28 11:11:44 casa kernel: [287522.202833] chrome[19799]: segfault at 0 ip 
7f58472adf58 sp 7ffc9db94490 error 4 in 
fglrx_dri.so[7f5845d37000+2338000]

  happens when browsing the internet, nothing crazy going on that would
  be "pushing" the drivers performance

  I can't tell you the last time it worked, because I kept getting
  segfaults on older card, thought it was the card. bought new card and
  did fresh install, same issue(yes if X were working I could have saved
  a video card purchase)

  no way to take a screenshot, and even if I did, it would just be a black 
screen, because thats what happens. 
  segfault > black screen > no terminals at all
  no ctrl+alt+F2 terminals access, etc
  I have to magic sysreq the system down with REISUB and that causes data loss

  please fix this

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  Uname: Linux 3.19.0-18-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  Date: Thu May 28 15:18:39 2015
  InstallationDate: Installed on 2015-05-13 (15 days ago)
  InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs

[Touch-packages] [Bug 1403542] Re: unity keeps last typed term in dash search

2014-12-19 Thread grinch
No one asked for "configuration for every single thing"

I only asked for a design change to be made a choice, instead of being
forced upon users.

Unity has made a decision to change dash's design and to force that
change to all users, even those who do not want it, and like the old way
better.

I will make a decision as well; Because of numerous bugs
(https://bugs.launchpad.net/unity/+bug/1403553
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1311316) in new
Unity version, including this one, I will switch to GNOME or other
desktop.

At least while Unity gets sorted properly.

You make close/lock this ticket. Thank you.

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

Title:
  unity keeps last typed term in dash search

Status in Unity:
  Incomplete
Status in unity package in Ubuntu:
  Incomplete

Bug description:
  When I click on dash home to search for an application, the previously 
searched term remains, even after I have started original application and the 
dash menu closes.
  The next time I click dash, it has the same term I previously searched for. 

  TEST CASE
  1. Open the dash by either clicking on the icon or by pressing the super key.
  2. Search for terminal, click terminal icon to launch it.
  3. Now again open the dash.
  WHAT HAPPENS
  The last written search term is shown in the search box and the 'searching' 
spinner is still spinning.
  WHAT SHOULD HAPPEN
  When the dash is reopened the search box should be empty.

  It is similar to #825412 from back on 2011 that was supposed to be
  patched

  If this is, for some reason, now the desired operation of dash, where
  do I configure it to stop this behavior? Please don't make uni-lateral
  decisions involving user interface, offer options.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1403542/+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 1403542] Re: unity keeps last typed term in dash search

2014-12-19 Thread grinch
The real problem is that this decision was made uni-laterally. What some see as 
a feature, others see as a flaw or bug. 
There should be a way to disable this "feature" for those that find it a flaw.

I like the old way Unity/Dash search worked.

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

Title:
  unity keeps last typed term in dash search

Status in Unity:
  Incomplete
Status in unity package in Ubuntu:
  Incomplete

Bug description:
  When I click on dash home to search for an application, the previously 
searched term remains, even after I have started original application and the 
dash menu closes.
  The next time I click dash, it has the same term I previously searched for. 

  TEST CASE
  1. Open the dash by either clicking on the icon or by pressing the super key.
  2. Search for terminal, click terminal icon to launch it.
  3. Now again open the dash.
  WHAT HAPPENS
  The last written search term is shown in the search box and the 'searching' 
spinner is still spinning.
  WHAT SHOULD HAPPEN
  When the dash is reopened the search box should be empty.

  It is similar to #825412 from back on 2011 that was supposed to be
  patched

  If this is, for some reason, now the desired operation of dash, where
  do I configure it to stop this behavior? Please don't make uni-lateral
  decisions involving user interface, offer options.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1403542/+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 1403553] Re: Unity does not provide login box when desktop is locked, sometimes

2014-12-18 Thread grinch
unity:
  Installed: 7.2.3+14.04.20140826-0ubuntu1
  Candidate: 7.2.3+14.04.20140826-0ubuntu1
  Version table:
 *** 7.2.3+14.04.20140826-0ubuntu1 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 7.2.2+14.04.20140714-0ubuntu1.1 0
500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
 7.2.0+14.04.20140416-0ubuntu1 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

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

Title:
  Unity does not provide login box when desktop is locked, sometimes

Status in Unity:
  Incomplete
Status in unity package in Ubuntu:
  Incomplete

Bug description:
  Sometimes when I come back to my locked computer, i am not able to login. 
There is no box to login with. 
  I have tried typing login details and tried clicking where login box should 
be, but neither work

  a picture of what is shown may illustrate the issue best. I will
  attach one as a file to this bug report

  Same picture is also hosted 3rd party: http://i.imgur.com/dLB25NY.jpg

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1403553/+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 1403553] Re: Unity does not provide login box when desktop is locked, sometimes

2014-12-17 Thread grinch
Yes. Neither monitor shows login box.
When it is working the login box will switch to whichever monitor has focus, 
which is why I made sure to capture the mouse pointer in my picture, to show 
that monitor had focus

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

Title:
  Unity does not provide login box when desktop is locked, sometimes

Status in Unity:
  Incomplete
Status in unity package in Ubuntu:
  Incomplete

Bug description:
  Sometimes when I come back to my locked computer, i am not able to login. 
There is no box to login with. 
  I have tried typing login details and tried clicking where login box should 
be, but neither work

  a picture of what is shown may illustrate the issue best. I will
  attach one as a file to this bug report

  Same picture is also hosted 3rd party: http://i.imgur.com/dLB25NY.jpg

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