[Touch-packages] [Bug 1164016] Re: restore type-ahead find

2021-02-08 Thread php4fan
> bug 1751069: restore type-ahead find in nautilus itself

You have linked to the wrong issue.

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

Title:
  restore type-ahead find

Status in Nautilus:
  Expired
Status in nautilus package in Ubuntu:
  Fix Released
Status in ubuntu-settings package in Ubuntu:
  Fix Released

Bug description:
  GNOME removed type-ahead find in Nautilus 3.6, not without
  controversy:

  https://mail.gnome.org/archives/nautilus-
  list/2012-August/msg2.html

  Now when you type in a Nautilus window, Nautilus immediately performs
  a search in the current directory and all its subdirectories.  I
  personally find this annoying.  If I want to search, I'll click the
  search icon.  Often I'm looking at a long directory listing and simply
  want to jump to a certain point in it, and type-ahead find works great
  for that.

  Would Ubuntu consider patching type-ahead find back in?

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1164016/+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 1897284] [NEW] duplicate bluetooth indicator

2020-09-25 Thread php4fan
Public bug reported:

At random times I get two bluetooth indicators on the bottom of the
screen instead of one.

See the screenshot.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: bluetooth (not installed)
ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
Uname: Linux 5.4.0-47-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: X-Cinnamon
Date: Fri Sep 25 15:27:19 2020
InstallationDate: Installed on 2013-10-11 (2540 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: Acer Aspire V3-571G
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic 
root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: Upgraded to focal on 2020-07-12 (74 days ago)
dmi.bios.date: 10/15/2012
dmi.bios.vendor: Acer
dmi.bios.version: V2.07
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: VA50_HC_CR
dmi.board.vendor: Acer
dmi.board.version: Type2 - Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V2.07
dmi.modalias: 
dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07:
dmi.product.family: Type1Family
dmi.product.name: Aspire V3-571G
dmi.product.sku: Aspire V3-_0648_V2.07
dmi.product.version: V2.07
dmi.sys.vendor: Acer
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: A4:17:31:0D:4A:70  ACL MTU: 1022:8  SCO MTU: 183:5
DOWN 
RX bytes:1190 acl:0 sco:0 events:67 errors:0
TX bytes:1076 acl:0 sco:0 commands:67 errors:0

** Affects: bluez (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-bug focal

** Attachment added: "Screenshot from 2020-09-25 15-26-55.png"
   
https://bugs.launchpad.net/bugs/1897284/+attachment/5414167/+files/Screenshot%20from%202020-09-25%2015-26-55.png

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

Title:
  duplicate bluetooth indicator

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  At random times I get two bluetooth indicators on the bottom of the
  screen instead of one.

  See the screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
  Uname: Linux 5.4.0-47-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  Date: Fri Sep 25 15:27:19 2020
  InstallationDate: Installed on 2013-10-11 (2540 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Acer Aspire V3-571G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic 
root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to focal on 2020-07-12 (74 days ago)
  dmi.bios.date: 10/15/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V2.07
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: VA50_HC_CR
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.07
  dmi.modalias: 
dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07:
  dmi.product.family: Type1Family
  dmi.product.name: Aspire V3-571G
  dmi.product.sku: Aspire V3-_0648_V2.07
  dmi.product.version: V2.07
  dmi.sys.vendor: Acer
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: A4:17:31:0D:4A:70  ACL MTU: 1022:8  SCO MTU: 183:5
DOWN 
RX bytes:1190 acl:0 sco:0 events:67 errors:0
TX bytes:1076 acl:0 sco:0 commands:67 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1897284/+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 1895454] Re: ibus indicator is unreadable, and the dropdown doesn't clarify what option is selected

2020-09-15 Thread php4fan
The bug is not invalid. It may belong to ibus or to Cinnamon or to
something else.

Are all icons supposed to have transparent backgrounds? If so, that
would mean that both icons and desktop environments should adhere to
strict color guidelines so that icons are always guaranteed to be
legible. Do such guidelines exist? If so, either (a) this icon does not
have an acceptable color, or (b) Cinnamon's panel does not have an
acceptable background color, or (c) the guidelines are not good enough.

If there are no such guidelines, then icons should never have a
completely transparent background without any border. That is, they
should be designed in whatever way that guarantees that they are visible
on any backround.

So, something is wrong somewhere, either in how the icon is designed, or
in how the desktop environment is designed, or in the the framework
where the desktop and the icons live.

That the user can change the icon color is cool but is not a solution.
The icon must be visible out of the box.


So far, iBus icon is the only one I've ever seen that is practically invisible.
Most icon have bright colors, which seems to suggest that if there is an 
expectation about the background color, it's that it is dark, which my current 
panel background is.

** Changed in: ibus (Ubuntu)
   Status: Invalid => Confirmed

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

Title:
  ibus indicator is unreadable, and the dropdown doesn't clarify what
  option is selected

Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  I don't know exactly what iBus is and what it does, but it has this
  indicator on the bottom-right corner of the screen (whatever that area
  is called) which shows what the currently selected input language is,
  whatever that means. For example, on my system there are two choices
  available: "Spanish - Spanish" and "English - English (US)", and
  therefore the indicator shows either "ES" or "EN" depending on which
  one is selected. Whatever the effect of that is.

  The issue is, this indicator is designed with an idiotic choice of
  colours: a very dark blue text on a very dark gray background, which
  makes it mostly unreadable. I am not color blind nor visually
  impaired, yet both colors are almost undistinguishable to me, and it
  costs me a great effort to tell whether it says "EN" or "ES".

  Additionally, adding to the idiocy, if I click on it to see which one
  is actually selected, a dropdown unfolds where the two options are
  listed, and the currently selected one is not highlighted in any way!!
  It seems that the selected one is always shown first, which, assuming
  it's true, I can only learn by changing the selection back and forth,
  when it could have been as easy as showing the currently selected one
  in bold.

  It looks as if every single possible step had been purposefully taken
  to make this less useful, because even by doing it carelessly and
  without putting any thought into it, it's unlikely that it could turn
  out so ridiculously badly designed.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.22-2ubuntu2.1
  ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
  Uname: Linux 5.4.0-47-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  Date: Sun Sep 13 15:38:34 2020
  InstallationDate: Installed on 2013-10-11 (2528 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: ibus
  UpgradeStatus: Upgraded to focal on 2020-07-12 (62 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1895454/+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 1895454] [NEW] ibus indicator is unreadable, and the dropdown doesn't clarify what option is selected

2020-09-13 Thread php4fan
Public bug reported:

I don't know exactly what iBus is and what it does, but it has this
indicator on the bottom-right corner of the screen (whatever that area
is called) which shows what the currently selected input language is,
whatever that means. For example, on my system there are two choices
available: "Spanish - Spanish" and "English - English (US)", and
therefore the indicator shows either "ES" or "EN" depending on which one
is selected. Whatever the effect of that is.

The issue is, this indicator is designed with an idiotic choice of
colours: a very dark blue text on a very dark gray background, which
makes it mostly unreadable. I am not color blind nor visually impaired,
yet both colors are almost undistinguishable to me, and it costs me a
great effort to tell whether it says "EN" or "ES".

Additionally, adding to the idiocy, if I click on it to see which one is
actually selected, a dropdown unfolds where the two options are listed,
and the currently selected one is not highlighted in any way!! It seems
that the selected one is always shown first, which, assuming it's true,
I can only learn by changing the selection back and forth, when it could
have been as easy as showing the currently selected one in bold.

It looks as if every single possible step had been purposefully taken to
make this less useful, because even by doing it carelessly and without
putting any thought into it, it's unlikely that it could turn out so
ridiculously badly designed.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ibus 1.5.22-2ubuntu2.1
ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
Uname: Linux 5.4.0-47-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: X-Cinnamon
Date: Sun Sep 13 15:38:34 2020
InstallationDate: Installed on 2013-10-11 (2528 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
SourcePackage: ibus
UpgradeStatus: Upgraded to focal on 2020-07-12 (62 days ago)

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


** Tags: amd64 apport-bug focal third-party-packages

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

Title:
  ibus indicator is unreadable, and the dropdown doesn't clarify what
  option is selected

Status in ibus package in Ubuntu:
  New

Bug description:
  I don't know exactly what iBus is and what it does, but it has this
  indicator on the bottom-right corner of the screen (whatever that area
  is called) which shows what the currently selected input language is,
  whatever that means. For example, on my system there are two choices
  available: "Spanish - Spanish" and "English - English (US)", and
  therefore the indicator shows either "ES" or "EN" depending on which
  one is selected. Whatever the effect of that is.

  The issue is, this indicator is designed with an idiotic choice of
  colours: a very dark blue text on a very dark gray background, which
  makes it mostly unreadable. I am not color blind nor visually
  impaired, yet both colors are almost undistinguishable to me, and it
  costs me a great effort to tell whether it says "EN" or "ES".

  Additionally, adding to the idiocy, if I click on it to see which one
  is actually selected, a dropdown unfolds where the two options are
  listed, and the currently selected one is not highlighted in any way!!
  It seems that the selected one is always shown first, which, assuming
  it's true, I can only learn by changing the selection back and forth,
  when it could have been as easy as showing the currently selected one
  in bold.

  It looks as if every single possible step had been purposefully taken
  to make this less useful, because even by doing it carelessly and
  without putting any thought into it, it's unlikely that it could turn
  out so ridiculously badly designed.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.22-2ubuntu2.1
  ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
  Uname: Linux 5.4.0-47-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  Date: Sun Sep 13 15:38:34 2020
  InstallationDate: Installed on 2013-10-11 (2528 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: ibus
  UpgradeStatus: Upgraded to focal on 2020-07-12 (62 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1895454/+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 1892642] [NEW] liveptch indicator icon is broken

2020-08-23 Thread php4fan
Public bug reported:

See the attached screenshot, it speaks for itself

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubuntu-desktop 1.450.1
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: X-Cinnamon
Date: Sun Aug 23 18:58:13 2020
InstallationDate: Installed on 2013-10-11 (2507 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
SourcePackage: ubuntu-meta
UpgradeStatus: Upgraded to focal on 2020-07-12 (41 days ago)

** Affects: ubuntu-meta (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal third-party-packages

** Attachment added: "Screenshot from 2020-08-23 18-37-56.png"
   
https://bugs.launchpad.net/bugs/1892642/+attachment/5403909/+files/Screenshot%20from%202020-08-23%2018-37-56.png

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

Title:
  liveptch indicator icon is broken

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  See the attached screenshot, it speaks for itself

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-desktop 1.450.1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  Date: Sun Aug 23 18:58:13 2020
  InstallationDate: Installed on 2013-10-11 (2507 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: ubuntu-meta
  UpgradeStatus: Upgraded to focal on 2020-07-12 (41 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1892642/+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 1892225] [NEW] apport-gtk consumes 100% CPU for way too long after something crashes

2020-08-19 Thread php4fan
Public bug reported:

Something (related to Cinnamon) crashes, so the usual popup appears
telling me that something crashed, and asking me whether I wanted to
send a report. I choose Send.

Every time this happens, then a process called apport-gtk starts
consuming 100% CPU and it goes on for several minutes, so long that I
end up killing it.

There's no way there is a good reason for consuming so much CPU for so
long. If you need to do such an amount of processing just to generate
and send a bug report, something is deeply broken. But if the operation
actually had to be that computationally expensive, then you must do it
in a less intensive way so that it can go on in the background, for no
matter how long, without rendering me unable to use my  computer.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: apport 2.20.11-0ubuntu27.4
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
NonfreeKernelModules: nvidia
ApportLog:
 ERROR: apport (pid 2908) Wed Aug 19 18:39:29 2020: called for pid 2405, signal 
11, core limit 0, dump mode 1
 ERROR: apport (pid 2908) Wed Aug 19 18:39:29 2020: executable: 
/usr/bin/cinnamon (command line "cinnamon --replace")
 ERROR: apport (pid 2908) Wed Aug 19 18:39:29 2020: debug: session gdbus call: 
(true,)
 
 ERROR: apport (pid 2908) Wed Aug 19 18:39:34 2020: wrote report 
/var/crash/_usr_bin_cinnamon.1000.crash
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
CasperMD5CheckResult: skip
CrashReports:
 640:1000:110:69556:2020-08-19 18:39:33.732794284 +0200:2020-08-19 
18:39:34.732794284 +0200:/var/crash/_usr_bin_cinnamon-launcher.1000.crash
 640:1000:110:15432562:2020-08-19 18:39:34.466977487 +0200:2020-08-19 
18:42:42.722667813 +0200:/var/crash/_usr_bin_cinnamon.1000.crash
CurrentDesktop: X-Cinnamon
Date: Wed Aug 19 18:42:34 2020
InstallationDate: Installed on 2013-10-11 (2503 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: Upgraded to focal on 2020-07-12 (37 days ago)

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


** Tags: amd64 apport-bug focal

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

Title:
  apport-gtk consumes 100% CPU for way too long after something crashes

Status in apport package in Ubuntu:
  New

Bug description:
  Something (related to Cinnamon) crashes, so the usual popup appears
  telling me that something crashed, and asking me whether I wanted to
  send a report. I choose Send.

  Every time this happens, then a process called apport-gtk starts
  consuming 100% CPU and it goes on for several minutes, so long that I
  end up killing it.

  There's no way there is a good reason for consuming so much CPU for so
  long. If you need to do such an amount of processing just to generate
  and send a bug report, something is deeply broken. But if the
  operation actually had to be that computationally expensive, then you
  must do it in a less intensive way so that it can go on in the
  background, for no matter how long, without rendering me unable to use
  my  computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apport 2.20.11-0ubuntu27.4
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia
  ApportLog:
   ERROR: apport (pid 2908) Wed Aug 19 18:39:29 2020: called for pid 2405, 
signal 11, core limit 0, dump mode 1
   ERROR: apport (pid 2908) Wed Aug 19 18:39:29 2020: executable: 
/usr/bin/cinnamon (command line "cinnamon --replace")
   ERROR: apport (pid 2908) Wed Aug 19 18:39:29 2020: debug: session gdbus 
call: (true,)
   
   ERROR: apport (pid 2908) Wed Aug 19 18:39:34 2020: wrote report 
/var/crash/_usr_bin_cinnamon.1000.crash
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashReports:
   640:1000:110:69556:2020-08-19 18:39:33.732794284 +0200:2020-08-19 
18:39:34.732794284 +0200:/var/crash/_usr_bin_cinnamon-launcher.1000.crash
   640:1000:110:15432562:2020-08-19 18:39:34.466977487 +0200:2020-08-19 
18:42:42.722667813 +0200:/var/crash/_usr_bin_cinnamon.1000.crash
  CurrentDesktop: X-Cinnamon
  Date: Wed Aug 19 18:42:34 2020
  InstallationDate: Installed on 2013-10-11 (2503 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to focal on 2020-07-12 (37 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1892225/+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 1535458] Re: [15.10 REGRESSION] Randomly wrongly detects files as binary

2016-02-22 Thread php4fan
For god's sake, this regression is HUGE.
It makes the life of any developer a hell and it's been MONTHS.

Can't you at least release an update rollinb back to a non-broken
version until this is fixed??

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

Title:
  [15.10 REGRESSION] Randomly wrongly detects files as binary

Status in grep package in Ubuntu:
  Confirmed

Bug description:
  I have a folder with a bunch of subfolder and several hundred or
  thousands files, most of them PHP files (obviously text).

  I often use grep recursively, like this:
$ grep -R somepattern *

  Since the upgrade from 15.04 to 15.10, it often happens that a lot of text 
files are wrongly treated as binary. That means that, when a match is found, 
instead of getting the normal output which would show the file name and the 
matching line (with the matching substring highlighted), I get the bogus 
message:
binary file whatever.php matches

  Just to be clear: in one invocation of grep -R, I get mixed output
  with a lot of matches shown in the expected way and quit e a few
  matches shown in the wrong way, even though ALL matching files are
  text files.

  
  This worked as expected before the upgrade from 15.04 and 15.10.

  
  This is a HUGE issue that makes it impossible to do everyday developing work.

  
  Until you fix it, please f***ing roll back grep to the previous version, 
because this sh** is unusable.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: grep 2.21-2
  ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6
  Uname: Linux 4.2.0-23-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jan 18 22:43:51 2016
  InstallationDate: Installed on 2013-10-11 (829 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: grep
  UpgradeStatus: Upgraded to wily on 2016-01-18 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grep/+bug/1535458/+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 1535452] Re: [15.10 REGRESSION] Builtin laptop display doesn't turn back on when external hdmi monitor is unplugged

2016-01-18 Thread php4fan
** Changed in: xorg (Ubuntu)
   Status: New => Confirmed

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

Title:
  [15.10 REGRESSION] Builtin laptop display doesn't turn back on when
  external hdmi monitor is unplugged

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I used to have my display settings so that only one external monitor
  would be used when available, and the laptop's builtin monitor would
  be disabled. When plugging and unplugging the external monitor
  (whether in the VGA or HDMI port), monitors would switch
  automatically, as is obviously expected.

  After upgrading from 15.04 to 15.10, as per bug #1535436, these
  settings were lost, and after reboot, the two monitors were both
  enabled in extended desktop mode (or whatever it's called).

  So I went to Settings -> Displays (while I had an HDMI monitor
  connected), and turned off the builtin display.

  That worked, but when unplugging the HDMI monitor, the builtin one
  remains turned off despite being the only available monitor. No matter
  how many times I plug and unplug the external HDMI monitor, the
  builtin one never turns on (the external one does work).

  This is a HUGE regression as it may leave you without screen.

  By plugging a monitor via the VGA port, it works as expected.

  I'm testing with the same monitors and cables (and computer) as I was
  using in 15.04 when everything worked fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6
  Uname: Linux 4.2.0-23-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.96  Sun Nov  8 22:33:28 
PST 2015
   GCC version:  gcc version 5.2.1 20151010 (Ubuntu 5.2.1-22ubuntu2)
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jan 18 22:18:48 2016
  DistUpgraded: 2016-01-18 11:11:01,146 DEBUG enabling apt cron job
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.19.0-43-generic, x86_64: installed
   bbswitch, 0.7, 4.2.0-23-generic, x86_64: installed
   nvidia-340, 340.96, 3.19.0-43-generic, x86_64: installed
   nvidia-340, 340.96, 4.2.0-23-generic, x86_64: installed
   vboxhost, 4.3.14: added
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Device [1025:0647]
   NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 
620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691]
  InstallationDate: Installed on 2013-10-11 (829 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Acer Aspire V3-571G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-23-generic.efi.signed 
root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to wily on 2016-01-18 (0 days ago)
  dmi.bios.date: 10/15/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V2.07
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: VA50_HC_CR
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.07
  dmi.modalias: 
dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07:
  dmi.product.name: Aspire V3-571G
  dmi.product.version: V2.07
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Mon Jan 18 17:01:13 2016
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   NVIDIA(0): Failed to initiate mode change.
   NVIDIA(0): Failed to complete mode change
   NVIDIA(0): Failed to initiate mode change.
   NVIDIA(0): Failed to complete mode change
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.2-1ubuntu9.1

To