[Desktop-packages] [Bug 692568] Re: Printer shouldn't be paused after "hp" CUPS backend failed

2016-06-24 Thread Joe6832
Still present in ubuntu 16.04. Workaround above is not possible in
ubuntu. Please fix the issue.

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

Title:
  Printer shouldn't be paused after "hp" CUPS backend failed

Status in HPLIP:
  Confirmed
Status in hplip package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: cups

  When printing fails for some reason ("backend failed" message),
  printer is paused, and won't resume automatically, even after a
  reboot. This is silly because there's no notice about that in the
  print dialog nor in the print queue: you have to go to
  System->Administration->Printing, and be very clever to understand how
  to re-enable the printer.

  In most cases, the fact that something failed doesn't mean other
  documents won't print, and generally users will figure the error
  better by themselves than with a paused printer.

  This is in Lucid, cups 1.4.3-1ubuntu1.3 (not sure it's the same
  behavior in Maverick).

To manage notifications about this bug go to:
https://bugs.launchpad.net/hplip/+bug/692568/+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 1586539] Re: Major screen flickering in Chromium and Google Chrome

2016-06-08 Thread Joe6832
Affects me too. There are a lot people outside this thread having this
annoying flickering:

https://www.google.de/search?q=--disable-gpu-driver-bug-
workarounds+flicker_rd=ssl#q=%22--disable-gpu-driver-bug-
workarounds%22+flicker+chrome

So i think this bug should categorized to high-prio!

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

Title:
  Major screen flickering in Chromium and Google Chrome

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  On a fresh installation of Ubuntu 16.04 I noticed major screen
  flickering issues in Chromium and Google Chrome browsers. Since this
  never happened in Ubuntu 15.10 with exactly the same Google Chrome
  binary, I believe, bug is caused by something that was added/updated
  in 16.04. I came across some discussions where different people
  suggested that it is related to new X.Org version.

  Here's a video to show what is happening:
  https://youtu.be/l21WsKz3fZc?t=45s

  I could fix this flickering with --disable-gpu-compositing switch, but
  this slows down page drawing significantly so it can't be considered a
  workaround. There is also a Chromium bug report:
  https://bugs.chromium.org/p/chromium/issues/detail?id=606152, but I
  don't think they will fix an Ubuntu-specific bug.

  Update: this indeed happens only when browser window is maximized.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.6.0-040600-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog:

  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat May 28 00:01:20 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   vboxhost, 5.0.20, 4.4.0-22-generic, x86_64: installed
   vboxhost, 5.0.20, 4.6.0-040600-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a2e] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Haswell-ULT Integrated Graphics 
Controller [1043:13bd]
  InstallationDate: Installed on 2016-05-01 (26 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: ASUSTeK COMPUTER INC. UX301LAA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.6.0-040600-generic 
root=UUID=172b2d49-444a-466b-ab91-b74605125b29 ro quiet splash rootfstype=ext4 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX301LAA.211
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX301LAA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX301LAA.211:bd06/05/2015:svnASUSTeKCOMPUTERINC.:pnUX301LAA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX301LAA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX301LAA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sun May 22 23:28:15 2016
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5126
   vendor SHP
  xserver.version: 2:1.18.3-1ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1586539/+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 1255558] Re: Can't type my password after cold boot

2014-03-08 Thread Joe6832
The Problem affects me with every start. I think the Wifi-is-Connected
Message could dissolve the focus of the Password-Field.

It would be nice if the bug will be solved in the next Beta from Trusty
Tahr because this bug could uncertain new users :)

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

Title:
  Can't type my password after cold boot

Status in “unity-greeter” package in Ubuntu:
  Triaged

Bug description:
  Can't type my password after cold boot unless I change my keyboard
  layout to next (or change and then re-change to same layout)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.9.3-0ubuntu1
  ProcVersionSignature: Ubuntu 3.12.0-4.10-generic 3.12.1
  Uname: Linux 3.12.0-4-generic x86_64
  ApportVersion: 2.12.7-0ubuntu1
  Architecture: amd64
  Date: Wed Nov 27 16:27:13 2013
  InstallationDate: Installed on 2013-11-19 (7 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131119)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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