[Desktop-packages] [Bug 1425000] Re: Cannot set right monitor as primary in dual monitor configuration

2016-11-10 Thread Jimmy Pan
Not definitely a bug. But I consider this feature is good and very
important to have.

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

Title:
  Cannot set right monitor as primary in dual monitor configuration

Status in unity-settings-daemon package in Ubuntu:
  Confirmed
Status in xfwm4 package in Ubuntu:
  Confirmed

Bug description:
  Unity always considers the left monitor as the default/primary one when in a 
dual-monitor configuration. By this I mean that:
  - Desktop icons appear only on the left monitor
  - An opened app (eg libreoffice writer) is opened on the left screen, even if 
I launch it via the launcher on the right monitor

  The current configuration can be seen at
  
http://i286.photobucket.com/albums/ll86/wild_oscar/Screenshotfrom2015-02-24100853.png

  The .config/monitors.xml file is shown below. Notice that the HDMI
  display (green in the photo) is set asyes.
  Nevertheless, this seems to be ignored - the behaviour is the one
  mentioned above (desktop icons on the left and writer opening on the
  left) .

  

no

GSM
0x4b7a
0xb13b
1440
900
60
0
0
normal
no
no
no




GSM
0x5a26
0x0008976f
1920
1080
60
1440
0
normal
no
no
yes




  

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1425000/+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 1631236] Re: Xorg freeze with Nvidia 960m on Dell Inspiron 15-7559

2016-11-03 Thread Jimmy Pan
I can never boot with the nvidia drivers. For the latest nvidia-367.75
in the repo, neither. This time, after the boot info shows up, it just
leaved a blinking cursor for a while and then the screen completely went
black.

Without the nvidia driver, it cannot shutdown right. But looks like the
problem is getting better now, I sometimes don't need to press the
powerbutton to shutdown.

This looks like the gtx 960m problem since I found other users not only
on dell 7559 have the problem.

Anyway, hope this problem can be fix soon.

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

Title:
  Xorg freeze with Nvidia 960m on Dell Inspiron 15-7559

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Posted first about this issue at
  https://ubuntuforums.org/showthread.php?t=2339198

  Pasted post below:

  "I installed Ubuntu 16.04 Desktop alongside Windows 10 Home on a Dell
  Inspiron 15-7559 with an Nvidia 960m card and embeded Intel Skylake
  graphics.

  When I first installed Ubuntu and attempted to boot, the display would
  freeze on the Ubuntu splash screen after entering my disk password.
  Strangely, by removing "quiet" and "splash" from my grub configuration
  during my next boot, I was able to finally boot to the login screen
  and access the desktop. I installed the Intel and Nvidia drivers in
  the "Additional Drivers" app and now I can boot to the login screen
  with no issues.

  Now, when closing the laptop lid to suspend the system, it resumes to
  a blank screen and I can't get it to recover from this state without
  holding the power button to force shutdown. I verified that it is a
  display issue because I was able to ssh into the machine while it had
  the blank screen.

  I was able to install and boot into the latest (4.8) mainline kernel,
  which also gave me a warning/error because of my installed proprietary
  drivers. I tried uninstalling the Nvidia drivers to see if Nouveau had
  been fixed/improved, but the previous splash screen freeze returned; I
  was able to reinstall the drivers by booting into 4.8 recovery mode
  and using the Failsafe graphics mode to reinstall the Nvidia drivers.

  Any help on getting Nouveau to work nicely with the 960m so I don't
  have to run proprietary drivers or solve the suspend issue?"

  Now, I sometimes cannot shutdown properly without getting warnings
  about cpu soft lockups from gpu-manager. I also get these when I boot
  without nvidia drivers with "quiet" and "splash" options removed from
  my grub config.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.8.0-040800-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
  Date: Thu Oct  6 20:47:42 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-38-generic, x86_64: installed
   bbswitch, 0.8, 4.8.0-040800-generic, x86_64: installed
   nvidia-361, 361.42: added
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 
00 [VGA controller])
 Subsystem: Dell Skylake Integrated Graphics [1028:0706]
 Subsystem: Dell GM107M [GeForce GTX 960M] [1028:0706]
  InstallationDate: Installed on 2016-09-29 (8 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:07dc Intel Corp. 
   Bus 001 Device 002: ID 1bcf:28b0 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 7559
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-040800-generic 
root=UUID=7dd53585-5dcb-4071-a47a-d1a7fede0e3f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/05/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.3
  dmi.board.name: 0H0CC0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 

[Desktop-packages] [Bug 1449112] Re: can't move files to trash without any owner/permission issues

2016-06-15 Thread Jimmy Pan
I have the same problem in ubuntu 16.04.

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

Title:
  can't move files to trash without any owner/permission issues

Status in Nautilus:
  Unknown
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  This is something that wouldn't happen before upgrading from Ubuntu
  14.10 / Nautilus 3.10 to Ubuntu 15.04 / Nautilus 3.14:

  I have a proper HOME partition and most User folders there (Documents,
  Downloads, Music, Pictures, Videos) are merely SYMLINKS to folders
  with the same names in a DATA partition which is mounted automatically
  at startup with proper options in fstab.

  Now -- unlike before -- when I attempt to delete an item in one of
  these folders after I open it via the SYMLINK I get the message "...
  can't be put in the trash. Do you want to delete it immediately?"
  although it is immediately moved to the Trash after I open the folder
  via the Data partition in the sidebar. (Naturally there are no such
  problems with items in other (real) items in my Home folder.

  Nautilus now seems confused about / not knowing where to move the item
  in question; to the Trash folder in the Home partition (symlink
  location) or the Data partition (real item location).

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1449112/+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 1409032] Re: gvfsd-smb: very high CPU utilisation

2016-06-07 Thread Jimmy Pan
Really annoying bug, I have to remove the exec file of gvfsd-smb-browse

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

Title:
  gvfsd-smb: very high CPU utilisation

Status in gvfs package in Ubuntu:
  Confirmed
Status in samba package in Ubuntu:
  Confirmed
Status in samba package in Fedora:
  Unknown

Bug description:
  Example:

  I use Virtualbox and mount a .vdi on an SMB server. Using gvfsd-smb
  (browsing within Gnome to find the share), gvfsd-smb uses up to 50%
  CPU which slows down the entire system when accessing the network
  share. Mounting using sudo ($ sudo mount -t smbfs -o
  guest,nounix,noperm //server/share /media/share) so that cifs is used
  uses around 8% CPU. The difference is dramatic!

  If I didn't have sudo access my machine would grind to a halt when
  trying to use the remote share.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gvfs-backends 1.12.1-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.11.0-26.45~precise1-generic 3.11.10.12
  Uname: Linux 3.11.0-26-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu17.8
  Architecture: i386
  Date: Fri Jan  9 14:32:20 2015
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gvfs
  UpgradeStatus: Upgraded to precise on 2014-12-07 (33 days ago)

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