[Desktop-packages] [Bug 1835644] Re: CRL files are not accessible for the Verify CRL options

2021-04-30 Thread Shuhao
This seems to also happen when you specify any cert inline in an
imported openvpn config.

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

Title:
  CRL files are not accessible for the Verify CRL options

Status in NetworkManager-OpenVPN:
  Unknown
Status in network-manager-openvpn package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  The Network Manager GUI options 'Verify CRL from file' and 'Verify CRL
  from directory' won't work because the openvpn process cannot access
  the files since being run with chroot, so the connection fails:

  nm-openvpn[5069]: chroot to '/var/lib/openvpn/chroot' and cd to '/' succeeded
  nm-openvpn[6135]: Options error: --crl-verify fails with 
'/var/lib/openvpn/chroot//home/steve/VPN/config/crl.rsa.4096.pem': No such file 
or directory (errno=2)

  Thanks.

  Ubuntu 19.04
  network-manager-openvpn, network-manager-openvpn-gnome 1.8.10-1
  openvpn 2.4.6-1ubuntu3.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-openvpn/+bug/1835644/+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 1903986] Re: Ubuntu 20.04 freezes with remmina in full-screen

2021-01-22 Thread Shuhao
A temporary workaround is to switch to tty via CTRL+ALT+F3 and kill the
remmina process.

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

Title:
  Ubuntu 20.04 freezes with remmina in full-screen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  On Ubuntu 20.04 using Remmina accessing remote Windows session to my
  work and everything was working fine for 5 hours and then suddenly
  Reminna freezes. Mouse pointer still working fine, but Remmina not
  responding and also keyboard not responding (maybe because all of the
  keys are controller by Remmina).

  This problem is now third time the problem appeared:
  - bug 1902051
  - bug 1903710
  with no response. :(

  Work-around: hard press power button to power off  laptop and power on
  it.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: remmina 1.4.2+dfsg-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.11
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 12 12:38:25 2020
  InstallationDate: Installed on 2019-10-23 (386 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  SourcePackage: remmina
  UpgradeStatus: Upgraded to focal on 2020-08-14 (89 days ago)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2020-04-29T17:08:03.553351
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-10-23 (392 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  Tags:  focal
  Uname: Linux 5.4.0-54-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-08-14 (95 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark
  _MarkForUpload: True
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2020-04-29T17:08:03.553351

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1903986/+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 1496542] Re: Running processes left after disabling screen reader

2017-12-12 Thread Shuhao
Do we know what's launching the process? It's not systemd as I checked.
There should be a workaround, no?

I'm going to try to set /usr/bin/speech-dispatcher and the binaries
under /usr/lib/speech-dispatcher-modules with chmod -x to see what
happens.

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

Title:
  Running processes left after disabling screen reader

Status in speech-dispatcher package in Ubuntu:
  Triaged

Bug description:
  After I disabled my screen reader, I noticed that when running "ps xa
  | grep -P 'speech-dispatcher.*\.conf'" I get:

  17906 tty2 Sl+0:09 /usr/lib/speech-dispatcher-modules/sd_espeak 
/etc/speech-dispatcher/modules/espeak.conf
  17911 tty2 Sl+0:01 /usr/lib/speech-dispatcher-modules/sd_cicero 
/etc/speech-dispatcher/modules/cicero.conf
  17915 tty2 Sl+0:01 /usr/lib/speech-dispatcher-modules/sd_generic 
/etc/speech-dispatcher/modules/generic.conf
  17918 tty2 Sl+0:01 /usr/lib/speech-dispatcher-modules/sd_dummy 
/etc/speech-dispatcher/modules/dummy.conf
  24407 pts/0S+ 0:00 grep --color=auto -P speech-dispatcher.*\.conf

  So it seems as though it left some running processes behind after I
  disabled it. I have also attached a screenshot of my Sound settings
  which show that they are still running (Sound_Application_List2.png).

  ---

  OS Information:

  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 15.04
  Release:  15.04
  Codename: vivid

  Package Information:

  speech-dispatcher:
Installed: 0.8.1-0ubuntu1
Candidate: 0.8.1-0ubuntu1
Version table:
   *** 0.8.1-0ubuntu1 0
  500 http://archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: speech-dispatcher 0.8.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Sep 16 20:27:00 2015
  InstallationDate: Installed on 2015-07-29 (49 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  SourcePackage: speech-dispatcher
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1496542/+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 1632027] Re: New Document feature missing from Nautilus 3.20+

2017-11-27 Thread Shuhao
This seems to affect 17.10

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

Title:
  New Document feature missing from Nautilus 3.20+

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu has a patch ( 16_unity_new_documents.patch ) to enable a 'New
  Document' function in the right-click context menu. This patch was not
  ported to Nautilus 3.20 so this Ubuntu-specific feature is missing in
  Ubuntu 16.10.

  https://bazaar.launchpad.net/~ubuntu-
  desktop/nautilus/ubuntu/view/head:/debian/patches/16_unity_new_documents.patch

  While this patch being disabled is noted in the debian/changelog,
  here's a formal bug to document the issue and maybe give it a bit more
  visibility so that it will be fixed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: nautilus 1:3.20.3-1ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Oct 10 12:54:50 2016
  EcryptfsInUse: Yes
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'open-folder-on-dnd-hover' b'false'
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'171'
   b'org.gnome.nautilus.window-state' b'geometry' b"'1106x542+436+438'"
   b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'small'"
  InstallationDate: Installed on 2016-08-11 (59 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Alpha amd64 (20160811)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1632027/+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 1726516] Re: no progress bar while copying files

2017-11-27 Thread Shuhao
I filed an upstream issue:
https://gitlab.gnome.org/GNOME/nautilus/issues/142

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

Title:
  no progress bar while copying files

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  while copying files, it does not show progress or any copy dialogue at
  all. also there is no option to create new file while right clicking

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 23 23:08:22 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-10-23 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   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/1726516/+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 1722103] [NEW] Amazon Fire HD 8 2017 does not get recognized

2017-10-08 Thread Shuhao
Public bug reported:

The version of libmtp included in Xenial does not recognize the Amazon
Fire HD 8 2017 version. This bug seems to have been fixed at least in
1.1.13 (although it does log an error, and that error log is fixed in
1.1.14).

I've tried to backport both 1.1.13 and 1.1.14 to my system (xenial) but
copying files via thunar will occasionally freeze the system, so maybe
something else needs to be updated as well.

Upstream bug URL (can't add this to LP tho):
https://sourceforge.net/p/libmtp/bugs/1718

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

** Description changed:

  The version of libmtp included in Xenial does not recognize the Amazon
  Fire HD 8 2017 version. This bug seems to have been fixed at least in
  1.1.13 (although it does log an error, and that error log is fixed in
  1.1.14).
  
  I've tried to backport both 1.1.13 and 1.1.14 to my system (xenial) but
  copying files via thunar will occasionally freeze the system, so maybe
  something else needs to be updated as well.
+ 
+ Upstream bug URL (can't add this to LP tho):
+ https://sourceforge.net/p/libmtp/bugs/1718

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

Title:
  Amazon Fire HD 8 2017 does not get recognized

Status in libmtp package in Ubuntu:
  New

Bug description:
  The version of libmtp included in Xenial does not recognize the Amazon
  Fire HD 8 2017 version. This bug seems to have been fixed at least in
  1.1.13 (although it does log an error, and that error log is fixed in
  1.1.14).

  I've tried to backport both 1.1.13 and 1.1.14 to my system (xenial)
  but copying files via thunar will occasionally freeze the system, so
  maybe something else needs to be updated as well.

  Upstream bug URL (can't add this to LP tho):
  https://sourceforge.net/p/libmtp/bugs/1718

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libmtp/+bug/1722103/+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 1631964] Re: Password required twice returning from suspend

2016-10-13 Thread Shuhao
I see this on a Intel HD 4000 as well, on xenial. (Thinkpad x230)

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

Title:
   Password required twice returning from suspend

Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed

Bug description:
  Clean install - no updates available. Also present on a previous
  install.

  Suspend machine and restart.

  Lock screen requiring password - enter password and return to
  suspended desktop.

  Within a few seconds machine locks and password is required once more.

  Using the same hardware I've installed nvidia 340.96 and tried to
  reproduce the issue without success.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xserver-xorg-video-nouveau 1:1.0.12-2
  ProcVersionSignature: Ubuntu 4.8.0-21.23-generic 4.8.0
  Uname: Linux 4.8.0-21-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Oct 10 14:59:56 2016
  InstallationDate: Installed on 2016-06-11 (120 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160611)
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1631964/+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 1538712] [NEW] Pidgin crashes occasionally on notification

2016-01-27 Thread Shuhao
Public bug reported:

Occasionally pidgin crashes when I receive a message. Using apport-
retrace it seem to show that it is inside libnotify when this happens.

I've attached the stack-trace.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: pidgin-libnotify 0.14-9ubuntu2
ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
Uname: Linux 4.2.0-25-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CurrentDesktop: XFCE
Date: Wed Jan 27 14:36:39 2016
InstallationDate: Installed on 2015-11-30 (58 days ago)
InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_CA.UTF-8
 SHELL=/bin/zsh
SourcePackage: pidgin-libnotify
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: pidgin-libnotify (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug wily

** Attachment added: "Stack trace of a crash constructed from apport-retrace"
   
https://bugs.launchpad.net/bugs/1538712/+attachment/4557879/+files/pidgin-retrace

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

Title:
  Pidgin crashes occasionally on notification

Status in pidgin-libnotify package in Ubuntu:
  New

Bug description:
  Occasionally pidgin crashes when I receive a message. Using apport-
  retrace it seem to show that it is inside libnotify when this happens.

  I've attached the stack-trace.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: pidgin-libnotify 0.14-9ubuntu2
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  Uname: Linux 4.2.0-25-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Jan 27 14:36:39 2016
  InstallationDate: Installed on 2015-11-30 (58 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/zsh
  SourcePackage: pidgin-libnotify
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pidgin-libnotify/+bug/1538712/+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 1486456] Re: Please set back libvpx1 into Wily archive

2015-10-13 Thread Shuhao
I think this is an oracle fault, no? They should probably be depending
on libvpx1 > 1.0.0 | libvpx2.

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

Title:
  Please set back libvpx1 into Wily archive

Status in libvpx package in Ubuntu:
  Confirmed

Bug description:
  Wanting to install virtualbox 5.0 from  virtualbox.org, as the wily
  archive one (5.02-dfsg-2) has a vboxpci iommu issue.

  but i require libvpx1 to install (and no more available into Wily archive)
  https://launchpad.net/ubuntu/+source/libvpx

  virtualbox-5.0:
   Depends: libvpx1 (>=1.0.0) but it is not installable

  Error with the Wily package:
  dmesg | grep -i iommu
  [0.00] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.2.0-4-generic 
root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro intel_iommu=on
  [0.00] DMAR: IOMMU enabled
  [   32.662814] vboxpci: IOMMU not found (not registered)

  (this is a test with intel_iommu=on kernel parameter, but without i
  get the same result. So i need the version from virtualbox.org)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvpx/+bug/1486456/+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 1369113] Re: Steam game began crashing 2014-09-12 (cross-post Source bugtracker)

2014-11-28 Thread Shuhao
I just got like 2 50GB log files in /tmp and in
~/.cache/upstart/startxfce4.log with this message. It filled my entire
drive.

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

Title:
  Steam game began crashing 2014-09-12 (cross-post Source bugtracker)

Status in steam package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I am cross-posting this issue, which I reported to Valve's Source GIT
  issue tracker, because it was suggested that the regression may be due
  to Ubuntu Xorg changes rather than changes on the Steam end.

  Link: https://github.com/ValveSoftware/Source-1-Games/issues/1822


  Symptom --
  DoD:Source loads normally. But after a few minutes of playing (not a specific 
time as far as I can tell), the game freezes in place. A short clip (maybe a 
quarter of a second) of the last audio that played then repeats over and over 
on a loop. The process has to be killed manually with a QUIT or HUP signal for 
good measure. This is a new issue that just arose today.

  I have included system info, kernel log, and output when game is run
  from terminal and crashes.

  X info --
  X.Org X Server 1.16.0
  Release Date: 2014-07-16
  X Protocol Version 11, Revision 0
  Build Operating System: Linux 3.2.0-61-generic x86_64 Ubuntu
  Current Operating System: Linux adam-x360-lin 3.16.0-14-generic #20-Ubuntu 
SMP Sat Sep 6 23:46:49 UTC 2014 x86_64
  Kernel command line: BOOT_IMAGE=/vmlinuz-3.16.0-14-generic.efi.signed 
root=UUID=5ad8035a-f2a4-4334-84d8-e2a8a7396bf8 ro drm.debug=0xe plymouth:debug
  Build Date: 10 September 2014  01:10:01PM
  xorg-server 2:1.16.0-1ubuntu1 (For technical support please see 
http://www.ubuntu.com/support) 
  Current version of pixman: 0.32.4
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.

  
  System --

  OS: Ubuntu 14.10 (latest updates)
  Kernel: 3.16.0-14-generic #20-Ubuntu SMP Sat Sep 6 23:46:49 UTC 2014 x86_64
  Model: HP Envy x360
  lspci:
  00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 0b)
  00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated 
Graphics Controller (rev 0b)
  00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 
0b)
  00:14.0 USB controller: Intel Corporation 8 Series USB xHCI HC (rev 04)
  00:16.0 Communication controller: Intel Corporation 8 Series HECI #0 (rev 04)
  00:1b.0 Audio device: Intel Corporation 8 Series HD Audio Controller (rev 04)
  00:1c.0 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 1 (rev 
e4)
  00:1c.1 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 2 (rev 
e4)
  00:1c.2 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 3 (rev 
e4)
  00:1c.3 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 4 (rev 
e4)
  00:1d.0 USB controller: Intel Corporation 8 Series USB EHCI #1 (rev 04)
  00:1f.0 ISA bridge: Intel Corporation 8 Series LPC Controller (rev 04)
  00:1f.2 SATA controller: Intel Corporation 8 Series SATA Controller 1 AHCI 
mode
  00:1f.3 SMBus: Intel Corporation 8 Series SMBus Controller (rev 04)
  02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5227 PCI 
Express Card Reader (rev 01)
  08:00.0 Network controller: Intel Corporation Wireless 7260 (rev 9b)
  09:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 10)


  Kernel log excerpt (from game start through crash end) --

  Sep 12 19:11:20 kernel: [ 4443.221907] [drm:i915_gem_open]
  Sep 12 19:11:20 kernel: [ 4443.266851] [drm:i915_gem_context_create_ioctl] HW 
context 1 created
  Sep 12 19:11:21 kernel: [ .169675] [drm:i915_gem_context_destroy_ioctl] 
HW context 1 destroyed
  Sep 12 19:11:21 kernel: [ .486704] [drm:i915_gem_open]
  Sep 12 19:11:21 kernel: [ .550210] [drm:i915_gem_context_create_ioctl] HW 
context 1 created
  Sep 12 19:11:25 kernel: [ 4447.852792] [drm:drm_mode_getconnector] 
[CONNECTOR:14:?]
  Sep 12 19:11:25 kernel: [ 4447.852796] 
[drm:drm_helper_probe_single_connector_modes_merge_bits] [CONNECTOR:14:eDP-1]
  Sep 12 19:11:25 kernel: [ 4447.852800] [drm:intel_dp_detect] 
[CONNECTOR:14:eDP-1]
  Sep 12 19:11:25 kernel: [ 4447.852804] [drm:_edp_panel_vdd_on] Turning eDP 
VDD on
  Sep 12 19:11:25 kernel: [ 4447.852809] [drm:_edp_panel_vdd_on] PP_STATUS: 
0x8008 PP_CONTROL: 0xabcd000f
  Sep 12 19:11:25 kernel: [ 4447.853257] [drm:intel_dp_probe_oui] Sink OUI: 
00e04c
  Sep 12 19:11:25 kernel: [ 4447.853695] [drm:intel_dp_probe_oui] Branch OUI: 
00e04c
  Sep 12 19:11:25 kernel: [ 4447.853708] [drm:drm_edid_to_eld] ELD: no CEA 
Extension found
  Sep 12 19:11:25 kernel: [ 4447.853711] 
[drm:drm_helper_probe_single_connector_modes_merge_bits] [CONNECTOR:14:eDP-1] 
probed modes :
  Sep 12 19:11:25 kernel: [ 4447.853715] 

[Desktop-packages] [Bug 1386388] [NEW] evince zoom option drop down not showing up

2014-10-27 Thread Shuhao
Public bug reported:

Everytime I click the down arrow in the zoom settings to select fit
width, the dropdown doesn't show up.

This is new in 14.10. In 14.04 I had no issues with this.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: evince 3.14.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
Uname: Linux 3.16.0-23-generic x86_64
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
CurrentDesktop: XFCE
Date: Mon Oct 27 15:34:35 2014
InstallationDate: Installed on 2014-10-25 (2 days ago)
InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=en_CA.UTF-8
 SHELL=/bin/zsh
SourcePackage: evince
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug utopic

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

Title:
  evince zoom option drop down not showing up

Status in “evince” package in Ubuntu:
  New

Bug description:
  Everytime I click the down arrow in the zoom settings to select fit
  width, the dropdown doesn't show up.

  This is new in 14.10. In 14.04 I had no issues with this.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: evince 3.14.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Oct 27 15:34:35 2014
  InstallationDate: Installed on 2014-10-25 (2 days ago)
  InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_CA.UTF-8
   SHELL=/bin/zsh
  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/1386388/+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 1317443] Re: mute mic button stopped working after nvidia driver installation

2014-10-17 Thread Shuhao
As a side note, the thinkvantage button also stops working.

The way to solve this problem is to use bumblebee and only turn on the
intel card until you need the nvidia card.

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

Title:
  mute mic button stopped working after nvidia driver installation

Status in “nvidia-graphics-drivers” package in Ubuntu:
  Confirmed

Bug description:
  I took a fresh install of Ubuntu 14.04 on Lenovo Thinkpad T420 with Nvidia NVS
  Mute microphone button works fine. 
  Also muting in the sound settings switches the led indicator on the button on 
and off as expected.

  I installed nvidia driver 331 required by CUDA toolkit.
  Restart.
  System works fine except the microphone mute button. 
  However, muting the mic in the sound settings dialog switches the led 
indicator correctly again.
  It looks like only the button is not sending any event to the sound settings.

  Switching to nouveau driver solves the problem but CUDA will not work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1317443/+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 1351590] Re: Cannot configure wi-fi in a live-session without logging out and back in again

2014-10-17 Thread Shuhao
So the proper way to attempt to reproduce this bug is to get a live disk
and see if the wifi works on the first try? I can try this on 14.10 beta
2 sometime today.

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

Title:
  Cannot configure wi-fi in a live-session without logging out and back
  in again

Status in “network-manager” package in Ubuntu:
  New

Bug description:
  I am using the daily build 20140802 of Xubuntu in a live session and
  cannot setup a wi-fi connection as I am told I do not have the
  authority. See attached screenshot of error.

  If I log out and then back in again I can setup wifi without a
  problem.

  I first saw this problem with 20140801 but did not report it.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: network-manager 0.9.8.8-0ubuntu23
  ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
  Uname: Linux 3.16.0-6-generic x86_64
  ApportVersion: 2.14.5-0ubuntu3
  Architecture: amd64
  CasperVersion: 1.340build1
  CurrentDesktop: XFCE
  Date: Sat Aug  2 10:41:23 2014
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.0.1 dev wlan0  proto static 
   192.168.0.0/24 dev wlan0  proto kernel  scope link  src 192.168.0.10  metric 
9
  LiveMediaBuild: Xubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140802)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RfKill:
   0: samsung-wlan: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
   virginmedia817089421b2f951-16f3-4abf-b20c-90d33ad3caf0   
802-11-wireless   1406976080   Sat 02 Aug 2014 10:41:20 AM UTCyes   
no /org/freedesktop/NetworkManager/Settings/1
   Wired connection 11bcd9f7f-a0b6-421e-aadb-7d200a9e52de   
802-3-ethernet1406975781   Sat 02 Aug 2014 10:36:21 AM UTCyes   
no /org/freedesktop/NetworkManager/Settings/0
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/1  
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1351590/+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 1255280] Re: Update to mesa 9.2.3

2013-12-30 Thread Shuhao
This bug blocks me from upgrading some machines to 13.10. Since 13.10's
support ends before 14.04 comes out, providing an upgrade so that I can
continue to get support is important.

Upgrading to 13.10 without this package will make things more
complicated.

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

Title:
  Update to mesa 9.2.3

Status in “mesa” package in Ubuntu:
  Fix Released
Status in “mesa” source package in Saucy:
  Triaged

Bug description:
  I am quite often getting GPU hangups and machine freezes, and the
  following is in my logs:

  Nov 19 21:17:09 derp kernel: [131426.756136] Watchdog[8655]: segfault at 0 ip 
7fcbb70bc72e sp 7fcba7692650 error 6 in chrome[7fcbb3514000+5eff000]
  Nov 19 21:17:17 derp kernel: [131434.757554] [drm:i915_hangcheck_elapsed] 
*ERROR* stuck on render ring
  Nov 19 21:17:17 derp kernel: [131434.757557] [drm] capturing error event; 
look for more information in /sys/kernel/debug/dri/0/i915_error_state
  Nov 19 21:17:17 derp kernel: [131434.785406] [drm:i915_set_reset_status] 
*ERROR* render ring hung inside bo (0xef56000 ctx 13) at 0xef561c8

  A quick grep for IPEHR in i915_error_state gives the following:

IPEHR: 0x79050005
IPEHR: 0x
IPEHR: 0x0b140001

  Freedesktop.org Bug #70151 says the following:

  Fixed in Mesa 9.2.3 (out today), the upcoming Mesa 10.0 release, or Mesa 
master.
  This fixes the Sandybridge-specific GPU hang where i915_error_state (aka 
/sys/class/drm/card0/error) lists an IPEHR of 0x79050005.

  Therefore I think Mesa should be upgraded to at least 9.2.3 to fix
  this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1255280/+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 1004197] Re: Opening new server opens to black the first time

2013-11-26 Thread Shuhao
I'm trying to connect to Azure and the second and third screen also
shows me black screens. Any ideas?

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

Title:
  Opening new server opens to black the first time

Status in “remmina” package in Ubuntu:
  Confirmed

Bug description:
  When I open a new server from the main Remmina window the first time,
  it opens a window, but only shows black.  Netstat shows a connection
  was established.  But the window consistently stays black.

  If I close the window and try to reopen the connection, the same thing
  happens.

  If I open the first black screen, and then immediately open the second
  screen, the connection works.

  Ubuntu 12.04 LTS

  remmina:
Installed: 1.0.0-1ubuntu6dupondje6
Candidate: 1.0.0-1ubuntu6dupondje6
Version table:
   *** 1.0.0-1ubuntu6dupondje6 0
  500 http://ppa.launchpad.net/dupondje/ppa/ubuntu/ precise/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.0.0-1ubuntu6 0
  500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 
Packages
   1.0.0-1ubuntu5 0
  500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1004197/+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 1004197] Re: Opening new server opens to black the first time

2013-11-26 Thread Shuhao
Never mind my comment, it was an unstable ocnnection

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

Title:
  Opening new server opens to black the first time

Status in “remmina” package in Ubuntu:
  Confirmed

Bug description:
  When I open a new server from the main Remmina window the first time,
  it opens a window, but only shows black.  Netstat shows a connection
  was established.  But the window consistently stays black.

  If I close the window and try to reopen the connection, the same thing
  happens.

  If I open the first black screen, and then immediately open the second
  screen, the connection works.

  Ubuntu 12.04 LTS

  remmina:
Installed: 1.0.0-1ubuntu6dupondje6
Candidate: 1.0.0-1ubuntu6dupondje6
Version table:
   *** 1.0.0-1ubuntu6dupondje6 0
  500 http://ppa.launchpad.net/dupondje/ppa/ubuntu/ precise/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.0.0-1ubuntu6 0
  500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 
Packages
   1.0.0-1ubuntu5 0
  500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1004197/+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 1041790] Re: [snb] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001, workaround i915.semaphores=0

2013-10-04 Thread Shuhao
Does anyone here notice graphics slow down? After a couple minutes of
game play with CSS, my framerate would drop to about 20fps (status of
other activities on the computer will also slowdown).

This did not happen in 13.04 but is occuring with 13.10.

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

Title:
  [snb] GPU lockup  IPEHR: 0x0b160001 IPEHR: 0x0b140001, workaround
  i915.semaphores=0

Status in X.org xf86-video-intel:
  Confirmed
Status in “linux” package in Ubuntu:
  Confirmed
Status in “sandybridge-meta” package in Ubuntu:
  Confirmed
Status in “xserver-xorg-video-intel” package in Ubuntu:
  Triaged

Bug description:
  X locks up periodically for a 2 to ten seconds at a time and this
  crash log gets generated. It's significantly more than several times a
  day but not quite continuous.

  Temporarily disabiling semaphores seems to eliminate the problem.
  E.g.:

  $ sudo -s
  # echo 0  /sys/modules/i915/parameters/semaphores

  [Workaround]
  1.  Edit your /etc/default/grub file.
  2.  Change this line:

  GRUB_CMDLINE_LINUX_DEFAULT=quiet splash

  to

  GRUB_CMDLINE_LINUX_DEFAULT=quiet splash i915.semaphores=0

  3.  Then run

  sudo update-grub

  4.  And reboot

  If you indeed have this bug, that should stop the lockups from happening.
  If it doesn't, then file a new bug report.

  Side Effects:  Rendering throughput is dropped by 10% with SNA, or as
  much as 3x with UXA. OpenGL performance is likely to be reduced by
  about 30%. More CPU time is spent waiting for the GPU with rc6
  disabled, so increased power consumption.

  [Original Report]

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: xserver-xorg-video-intel 2:2.20.3-0ubuntu1
  Uname: Linux 3.6.0-rc3-git-20120826.1015 x86_64
  ApportVersion: 2.5.1-0ubuntu2
  Architecture: amd64
  Chipset: sandybridge-m-gt2
  Date: Sun Aug 26 16:06:32 2012
  DistroCodename: quantal
  DistroVariant: ubuntu
  DuplicateSignature: [sandybridge-m-gt2] GPU lockup  IPEHR: 0x0b160001 IPEHR: 
0x0b140001 Ubuntu 12.10
  EcryptfsInUse: Yes
  ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py
  GpuHangFrequency: Continuously
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120724.2)
  InterpreterPath: /usr/bin/python3.2mu
  MachineType: Dell Inc. Dell System XPS L502X
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py
  ProcEnviron:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.6.0-rc3-git-20120826.1015 
root=UUID=135c8090-427c-460a-909d-eff262cd44b6 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   xserver-xorg 1:7.7+1ubuntu3
   libdrm2  2.4.38-0ubuntu2
   xserver-xorg-video-intel 2:2.20.3-0ubuntu1
  SourcePackage: xserver-xorg-video-intel
  Title: [sandybridge-m-gt2] GPU lockup  IPEHR: 0x0b160001 IPEHR: 0x0b140001
  UdevDb: Error: [Errno 2] No such file or directory: 'udevadm'
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  dmi.bios.date: 05/29/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0NJT03
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd05/29/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System XPS L502X
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1041790/+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