[Desktop-packages] [Bug 1932066] [NEW] PulseAudio Preferences searches for libraries in incorrect location

2021-06-15 Thread Will Palmer 
Public bug reported:

PulseAudio Preferences (paprefs) appears to be searching for modules in
the wrong location.

Specifically, the "install" button appears when modules relevant modules
cannot be found by paprefs.


paprefs is searching for modules in the location: /usr/lib/pulse-13.99/modules/
the modules are actually located in: /usr/lib/pulse-13.99.1/modules/

The specifics of this were determined via `strace paprefs`, which (among
a lot of other things), produces:

access("/usr/lib/pulse-13.99/modules/module-esound-protocol-tcp.so", F_OK) = -1 
ENOENT (No such file or directory)
access("/usr/lib/pulse-13.99/modules/module-native-protocol-tcp.so", F_OK) = -1 
ENOENT (No such file or directory)
access("/usr/lib/pulse-13.99/modules/module-zeroconf-publish.so", F_OK) = -1 
ENOENT (No such file or directory)
access("/usr/lib/pulse-13.99/modules/module-zeroconf-discover.so", F_OK) = -1 
ENOENT (No such file or directory)
access("/usr/lib/pulse-13.99/modules/module-raop-discover.so", F_OK) = -1 
ENOENT (No such file or directory)
access("/usr/lib/pulse-13.99/modules/module-rtp-recv.so", F_OK) = -1 ENOENT (No 
such file or directory)
access("/usr/lib/pulse-13.99/modules/module-rtp-send.so", F_OK) = -1 ENOENT (No 
such file or directory)
access("/usr/lib/pulse-13.99/modules/module-rygel-media-server.so", F_OK) = -1 
ENOENT (No such file or directory)


creating a symlink from /usr/lib/pulse-13.99.1 to /usr/lib/pulse-13.99 resolves 
the issue.

paprefs should perhaps be updated to match the version of the pulseaudio
package.

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

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

Title:
  PulseAudio Preferences searches for libraries in incorrect location

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  PulseAudio Preferences (paprefs) appears to be searching for modules
  in the wrong location.

  Specifically, the "install" button appears when modules relevant
  modules cannot be found by paprefs.

  
  paprefs is searching for modules in the location: 
/usr/lib/pulse-13.99/modules/
  the modules are actually located in: /usr/lib/pulse-13.99.1/modules/

  The specifics of this were determined via `strace paprefs`, which
  (among a lot of other things), produces:

  access("/usr/lib/pulse-13.99/modules/module-esound-protocol-tcp.so", F_OK) = 
-1 ENOENT (No such file or directory)
  access("/usr/lib/pulse-13.99/modules/module-native-protocol-tcp.so", F_OK) = 
-1 ENOENT (No such file or directory)
  access("/usr/lib/pulse-13.99/modules/module-zeroconf-publish.so", F_OK) = -1 
ENOENT (No such file or directory)
  access("/usr/lib/pulse-13.99/modules/module-zeroconf-discover.so", F_OK) = -1 
ENOENT (No such file or directory)
  access("/usr/lib/pulse-13.99/modules/module-raop-discover.so", F_OK) = -1 
ENOENT (No such file or directory)
  access("/usr/lib/pulse-13.99/modules/module-rtp-recv.so", F_OK) = -1 ENOENT 
(No such file or directory)
  access("/usr/lib/pulse-13.99/modules/module-rtp-send.so", F_OK) = -1 ENOENT 
(No such file or directory)
  access("/usr/lib/pulse-13.99/modules/module-rygel-media-server.so", F_OK) = 
-1 ENOENT (No such file or directory)

  
  creating a symlink from /usr/lib/pulse-13.99.1 to /usr/lib/pulse-13.99 
resolves the issue.

  paprefs should perhaps be updated to match the version of the
  pulseaudio package.

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

Re: [Desktop-packages] [Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows

2019-10-13 Thread Scott Palmer 
I can confirm that I am still having this issue on 3.34 as well
(Manjaro).

This is shocking to me that anyone using Gnome to develop doesn't
encounter this bug at minimum of 5x per day.  Or are Gnome developers
using MacOS and MBPs to develop like those in the lol "Linux"
Foundation.


+Scott


‐‐‐ Original Message ‐‐‐
On Sunday, October 13, 2019 7:42 AM, kohey  wrote:

> Yes, the issue still happens with 3.34.
> My work around is to trigger the following script through a keyboard shortcut.
> gsettings set org.gnome.desktop.peripherals.touchpad send-events disabled
> sleep 1
> gsettings set org.gnome.desktop.peripherals.touchpad send-events enabled
> gsettings set org.gnome.desktop.peripherals.touchpad tap-to-click false
> sleep 1
> gsettings set org.gnome.desktop.peripherals.touchpad tap-to-click true
>
> -
>
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1181666
>
> Title:
> gnome-shell randomly blocks mouse clicks from working in app windows
>
> Status in GNOME Shell:
> Confirmed
> Status in Ubuntu GNOME:
> Confirmed
> Status in gnome-shell package in Ubuntu:
> Confirmed
> Status in mutter package in Ubuntu:
> Confirmed
>
> Bug description:
> Under GNOME 3, the use of the mouse-click stops occasionally, though I
> can still move the mouse around and can still click on items in the
> Activities screen and the top-bar.
>
> I can use alt-tab to cycle windows and can still type into already-
> active textboxes in windows, but I cannot click within the windows,
> and the mouse is not picked up at all by the windows.
>
> I can open the alt-f2 "run command" dialogue, but cannot type into it.
>
> The workaround I'm using is to open terminal (ctrl-alt-T) and run
> "gnome-shell -r", and restarting that command every time I have the
> problem again.
>
> Please ask if there's anything I forgot to mention.
>
> ADDITIONAL: The error tends to happen randomly, but it seems to happen
> upon opening a new window, changing windows, closing windows, or
> opening the activities pane (whether a change of window is thus
> instigated or not)
>
> ADDITIONAL 2: (sorry, it's early) The other workaround is to log out
> and to log in again, but that is also less than ideal
>
> ProblemType: Bug
> DistroRelease: Ubuntu 13.04
> Package: gnome-shell 3.6.3.1-0ubuntu6
> ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11
> Uname: Linux 3.8.0-22-generic x86_64
> ApportVersion: 2.9.2-0ubuntu8
> Architecture: amd64
> Date: Sun May 19 07:02:18 2013
> DisplayManager: gdm
> GsettingsChanges:
>  b'org.gnome.desktop.interface' b'clock-show-date' b'true'
>  b'org.gnome.desktop.interface' b'clock-show-seconds' b'true'
>  b'org.gnome.desktop.interface' b'document-font-name' b"'Sans 10'"
>  b'org.gnome.desktop.interface' b'font-name' b"'Cantarell 10'"
>  b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 12'"
> InstallationDate: Installed on 2013-05-04 (14 days ago)
> InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 
> (20130424)
> MarkForUpload: True
> ProcEnviron:
>  LANGUAGE=en_GB:en
>  PATH=(custom, no user)
>  XDG_RUNTIME_DIR=
> LANG=en_GB.UTF-8
>  SHELL=/bin/bash
> SourcePackage: gnome-shell
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gnome-shell/+bug/1181666/+subscriptions

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

Title:
  gnome-shell randomly blocks mouse clicks from working in app windows

Status in GNOME Shell:
  Confirmed
Status in Ubuntu GNOME:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Under GNOME 3, the use of the mouse-click stops occasionally, though I
  can still move the mouse around and can still click on items in the
  Activities screen and the top-bar.

  I can use alt-tab to cycle windows and can still type into already-
  active textboxes in windows, but I cannot click within the windows,
  and the mouse is not picked up at all by the windows.

  I can open the alt-f2 "run command" dialogue, but cannot type into it.

  The workaround I'm using is to open terminal (ctrl-alt-T) and run
  "gnome-shell -r", and restarting that command every time I have the
  problem again.

  Please ask if there's anything I forgot to mention.

  ADDITIONAL: The error tends to happen randomly,

[Desktop-packages] [Bug 220263] Re: Bad Firefox integration with dark themes

2019-05-25 Thread Scott Palmer 
For those that run linux and want to update their Firefox icon so it
automatically launches with GTK_THEME="Adwaita:light" firefox %u instead
(band-aid work around that shouldn't need to be).

$ cp /usr/share/applications/firefox.desktop ~/.local/share/applications
$ gedit ~/.local/share/applications/firefox.desktop

Change the "Exec=" line to read:

Exec=bash -c "GTK_THEME=\"Adwaita:light\" firefox %u &"

Save and Exit.  
Now your Firefox icon should start using the Adwaita:light theme without a 
lingering terminal window.

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

Title:
  Bad Firefox integration with dark themes

Status in Mozilla Firefox:
  Fix Released
Status in XULRunner:
  Confirmed
Status in firefox package in Ubuntu:
  Triaged

Bug description:
  I'm using Mozilla Firefox 3 Beta 5 on Ubuntu 8.04 with a dark theme.
  Now I see all the input boxes and buttons filled with grey colour.
  This happened even with Firefox 2, but I solved that problem with a
  quick guide under the comment "firefox fix" by Proton at the bottom of
  this page: http://www.gnome-
  look.org/content/show.php/Grey+Neu?content=60824

  In Firefox 3 I can't correct this problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/220263/+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 220263] Re: Bad Firefox integration with dark themes

2019-05-25 Thread Scott Palmer 
I am having this issue with Firefox 66.0.3 using Ubuntu 19.04 (Gnome
3.32 using Adwaita dark).

This release seems to ignore:

  widget.content.allow-gtk-dark-theme in about:config is set to default / false
  widget.chrome.allow-gtk-dark-theme in about:config is also default /false

I came back to Firefox after running Brave for a bit only to find this
Is this just another Mozilla blunder?  Time to install Brave again.

** Attachment added: "Screenshot from 2019-05-25 13-20-00.png"
   
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/220263/+attachment/5266533/+files/Screenshot%20from%202019-05-25%2013-20-00.png

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

Title:
  Bad Firefox integration with dark themes

Status in Mozilla Firefox:
  Fix Released
Status in XULRunner:
  Confirmed
Status in firefox package in Ubuntu:
  Triaged

Bug description:
  I'm using Mozilla Firefox 3 Beta 5 on Ubuntu 8.04 with a dark theme.
  Now I see all the input boxes and buttons filled with grey colour.
  This happened even with Firefox 2, but I solved that problem with a
  quick guide under the comment "firefox fix" by Proton at the bottom of
  this page: http://www.gnome-
  look.org/content/show.php/Grey+Neu?content=60824

  In Firefox 3 I can't correct this problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/220263/+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 1828649] Re: Wayland session freezes

2019-05-17 Thread Scott Palmer 
I believe I made a mistake in the steps taken above.

I believe I rebooted my computer once after the `journalctl --vacuum-
time=1s`

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

Title:
  Wayland session freezes

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  When I switch to wayland the gnome desktop locks up before I see my desktop.
  It doesn't lock up when I have my laptop closed and only one display 
connected.
  When I connect up the second display, it locks up every time.
  I tried deleting my monitors.xml file..  that doesn't make any difference.

  I was able to get it to work by connecting one display via DisplayPort.
  When I connect the second display, via active HDMI to DisplayPort on dock, it 
doesn't work if I select Wayland.  This wire configuration works fine with Xorg.

  Additionally, when I lift my laptop screen, one of my monitors goes
  out and re-enabling it causes another to go off.  Linux kernel is not
  smart enough to drive the 3 displays.  I am able to drive two monitors
  and have my laptop screen open in Windows just fine.

  Of importance is that my DisplayPort to HDMI adaptor is ACTIVE.  If I
  was to use a PASSIVE adaptor, I cannot drive two external displays and
  the laptop display.

  With my laptop screen closed, I was able to drive both displays in
  Wayland just fine in 18.10 so this is a regression.  The GNU/Linux
  kernel has always (as far as I know) been lacking in smarts to drive
  all three displays.

  This work system is has Intel 4000 Integrated video (Lenovo ThinkPad
  laptop).

  Main screen is 2560x1600 via DisplayPort to laptop.
  Secondary screen is 1920x1200 via DisplayPort to laptop dock.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 10 16:55:27 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: This is the first time
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:2203]
  InstallationDate: Installed on 2019-03-25 (46 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190325)
  MachineType: LENOVO 343522U
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=7e84182c-37f4-407a-91ca-1b6bbec80a00 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/15/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GCETB2WW (2.72 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 343522U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGCETB2WW(2.72):bd11/15/2018:svnLENOVO:pn343522U:pvrThinkPadX230Tablet:rvnLENOVO:rn343522U:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230 Tablet
  dmi.product.name: 343522U
  dmi.product.sku: LENOVO_MT_3435
  dmi.product.version: ThinkPad X230 Tablet
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1828649/+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 1828649] Re: Wayland session freezes

2019-05-17 Thread Scott Palmer 
# journalctl rotate
# journalctl --vacuum-time=1s





journalctl -b-1 --no-pager > prevboot.txt

** Attachment added: "prevboot.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1828649/+attachment/5264569/+files/prevboot.txt

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

Title:
  Wayland session freezes

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  When I switch to wayland the gnome desktop locks up before I see my desktop.
  It doesn't lock up when I have my laptop closed and only one display 
connected.
  When I connect up the second display, it locks up every time.
  I tried deleting my monitors.xml file..  that doesn't make any difference.

  I was able to get it to work by connecting one display via DisplayPort.
  When I connect the second display, via active HDMI to DisplayPort on dock, it 
doesn't work if I select Wayland.  This wire configuration works fine with Xorg.

  Additionally, when I lift my laptop screen, one of my monitors goes
  out and re-enabling it causes another to go off.  Linux kernel is not
  smart enough to drive the 3 displays.  I am able to drive two monitors
  and have my laptop screen open in Windows just fine.

  Of importance is that my DisplayPort to HDMI adaptor is ACTIVE.  If I
  was to use a PASSIVE adaptor, I cannot drive two external displays and
  the laptop display.

  With my laptop screen closed, I was able to drive both displays in
  Wayland just fine in 18.10 so this is a regression.  The GNU/Linux
  kernel has always (as far as I know) been lacking in smarts to drive
  all three displays.

  This work system is has Intel 4000 Integrated video (Lenovo ThinkPad
  laptop).

  Main screen is 2560x1600 via DisplayPort to laptop.
  Secondary screen is 1920x1200 via DisplayPort to laptop dock.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 10 16:55:27 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: This is the first time
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:2203]
  InstallationDate: Installed on 2019-03-25 (46 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190325)
  MachineType: LENOVO 343522U
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=7e84182c-37f4-407a-91ca-1b6bbec80a00 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/15/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GCETB2WW (2.72 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 343522U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGCETB2WW(2.72):bd11/15/2018:svnLENOVO:pn343522U:pvrThinkPadX230Tablet:rvnLENOVO:rn343522U:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230 Tablet
  dmi.product.name: 343522U
  dmi.product.sku: LENOVO_MT_3435
  dmi.product.version: ThinkPad X230 Tablet
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1828649/+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 1828649] [NEW] Wayland freeze

2019-05-10 Thread Scott Palmer 
Public bug reported:

When I switch to wayland the gnome desktop locks up before I see my desktop.
It doesn't lock up when I have my laptop closed and only one display connected.
When I connect up the second display, it locks up every time.
I tried deleting my monitors.xml file..  that doesn't make any difference.

I was able to get it to work by connecting one display via DisplayPort.
When I connect the second display, via active HDMI to DisplayPort on dock, it 
doesn't work if I select Wayland.  This wire configuration works fine with Xorg.

Additionally, when I lift my laptop screen, one of my monitors goes out
and re-enabling it causes another to go off.  Linux kernel is not smart
enough to drive the 3 displays.  I am able to drive two monitors and
have my laptop screen open in Windows just fine.

Of importance is that my DisplayPort to HDMI adaptor is ACTIVE.  If I
was to use a PASSIVE adaptor, I cannot drive two external displays and
the laptop display.

With my laptop screen closed, I was able to drive both displays in
Wayland just fine in 18.10 so this is a regression.  The GNU/Linux
kernel has always (as far as I know) been lacking in smarts to drive all
three displays.

This work system is has Intel 4000 Integrated video (Lenovo ThinkPad
laptop).

Main screen is 2560x1600 via DisplayPort to laptop.
Secondary screen is 1920x1200 via DisplayPort to laptop dock.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri May 10 16:55:27 2019
DistUpgraded: Fresh install
DistroCodename: disco
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GpuHangFrequency: This is the first time
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:2203]
InstallationDate: Installed on 2019-03-25 (46 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190325)
MachineType: LENOVO 343522U
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=7e84182c-37f4-407a-91ca-1b6bbec80a00 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/15/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: GCETB2WW (2.72 )
dmi.board.asset.tag: Not Available
dmi.board.name: 343522U
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrGCETB2WW(2.72):bd11/15/2018:svnLENOVO:pn343522U:pvrThinkPadX230Tablet:rvnLENOVO:rn343522U:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad X230 Tablet
dmi.product.name: 343522U
dmi.product.sku: LENOVO_MT_3435
dmi.product.version: ThinkPad X230 Tablet
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug disco freeze ubuntu

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

Title:
  Wayland freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  When I switch to wayland the gnome desktop locks up before I see my desktop.
  It doesn't lock up when I have my laptop closed and only one display 
connected.
  When I connect up the second display, it locks up every time.
  I tried deleting my monitors.xml file..  that doesn't make any difference.

  I was able to get it to work by connecting one display via DisplayPort.
  When I connect the second display, via active HDMI to DisplayPort on dock, it 
doesn't work if I select Wayland.  This wire configuration works fine with Xorg.

  Additionally, when I lift my laptop screen, one of my monitors goes
  out and re-enabling it causes another to go off.  Linux kernel is not
  smart enough to drive the 3 displays.  I am able to drive two monitors
  and have my laptop screen open in Windows just fine.

  Of importance

Re: [Desktop-packages] [Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows

2019-02-10 Thread Scott Palmer 
The solution until this is solved is to use something other than gnome
shell as far as I know.  Mint Cinnamon and Elementary are both popular
alternatives.

On Sun, Feb 10, 2019, 1:29 PM Adrian <1181...@bugs.launchpad.net wrote:

> I am facing the same issue in Ubuntu 18.10. The super key randomly stops
> working and I loose control of all windows except for the active window,
> which in some cases also stops working and cannot even do clicks there.
> The workaround I found is to close all windows, lock the screen and the
> problem solves for 5-10 min or so. But this is clearly impractical and I
> can't really go on like this any further. I re-installed the OS but it
> didn't solve the issue. I have a Lenovo T430s if that helps. Does anyone
> found a solution to this yet? I'd appreciate it very much!
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1181666
>
> Title:
>   gnome-shell randomly blocks mouse clicks from working in app windows
>
> Status in GNOME Shell:
>   Confirmed
> Status in Ubuntu GNOME:
>   Confirmed
> Status in gnome-shell package in Ubuntu:
>   Confirmed
> Status in mutter package in Ubuntu:
>   Confirmed
>
> Bug description:
>   Under GNOME 3, the use of the mouse-click stops occasionally, though I
>   can still move the mouse around and can still click on items in the
>   Activities screen and the top-bar.
>
>   I can use alt-tab to cycle windows and can still type into already-
>   active textboxes in windows, but I cannot click within the windows,
>   and the mouse is not picked up at all by the windows.
>
>   I can open the alt-f2 "run command" dialogue, but cannot type into it.
>
>   The workaround I'm using is to open terminal (ctrl-alt-T) and run
>   "gnome-shell -r", and restarting that command every time I have the
>   problem again.
>
>   Please ask if there's anything I forgot to mention.
>
>   ADDITIONAL: The error tends to happen randomly, but it seems to happen
>   upon opening a new window, changing windows, closing windows, or
>   opening the activities pane (whether a change of window is thus
>   instigated or not)
>
>   ADDITIONAL 2: (sorry, it's early) The other workaround is to log out
>   and to log in again, but that is also less than ideal
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 13.04
>   Package: gnome-shell 3.6.3.1-0ubuntu6
>   ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11
>   Uname: Linux 3.8.0-22-generic x86_64
>   ApportVersion: 2.9.2-0ubuntu8
>   Architecture: amd64
>   Date: Sun May 19 07:02:18 2013
>   DisplayManager: gdm
>   GsettingsChanges:
>b'org.gnome.desktop.interface' b'clock-show-date' b'true'
>b'org.gnome.desktop.interface' b'clock-show-seconds' b'true'
>b'org.gnome.desktop.interface' b'document-font-name' b"'Sans 10'"
>b'org.gnome.desktop.interface' b'font-name' b"'Cantarell 10'"
>b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono
> 12'"
>   InstallationDate: Installed on 2013-05-04 (14 days ago)
>   InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64
> (20130424)
>   MarkForUpload: True
>   ProcEnviron:
>LANGUAGE=en_GB:en
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_GB.UTF-8
>SHELL=/bin/bash
>   SourcePackage: gnome-shell
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gnome-shell/+bug/1181666/+subscriptions
>

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

Title:
  gnome-shell randomly blocks mouse clicks from working in app windows

Status in GNOME Shell:
  Confirmed
Status in Ubuntu GNOME:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Under GNOME 3, the use of the mouse-click stops occasionally, though I
  can still move the mouse around and can still click on items in the
  Activities screen and the top-bar.

  I can use alt-tab to cycle windows and can still type into already-
  active textboxes in windows, but I cannot click within the windows,
  and the mouse is not picked up at all by the windows.

  I can open the alt-f2 "run command" dialogue, but cannot type into it.

  The workaround I'm using is to open terminal (ctrl-alt-T) and run
  "gnome-shell -r", and restarting that command every time I have the
  problem again.

  Please ask if there's anything I forgot to mention.

  ADDITIONAL: The error tends to happen randomly, but it seems to happen
  upon opening a new window, changing windows, closing windows, or
  opening the activities pane (whether a change of window is thus
  instigated or not)

  ADDITIONAL 2: (sorry, it's early) The other workaround is to log out
  and to log in again, but that is also less than ideal

  ProblemType: Bug

[Desktop-packages] [Bug 1706097] Re: gvfsd-mtp crashed with SIGSEGV

2018-10-21 Thread Scott Palmer 
Don't get too excited..
https://gitlab.gnome.org/GNOME/nautilus/issues/703

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

Title:
  gvfsd-mtp crashed with SIGSEGV

Status in gvfs:
  Unknown
Status in gvfs package in Ubuntu:
  Fix Released
Status in gnome-shell package in Fedora:
  Unknown

Bug description:
  I get this every day when I have connected my Android phone for
  charging its battery.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gvfs-backends 1.32.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Mon Jul 24 11:29:55 2017
  ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
  InstallationDate: Installed on 2015-04-30 (816 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.6 /org/gtk/gvfs/exec_spaw/8
  ProcEnviron:
   LANG=en_US.UTF-8
   LANGUAGE=en_US
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x7fea768b6cc9:mov0x18(%rax),%rax
   PC (0x7fea768b6cc9) ok
   source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gvfs
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gvfsd-mtp crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo 
wireshark

To manage notifications about this bug go to:
https://bugs.launchpad.net/gvfs/+bug/1706097/+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 1799061] Re: Corruption at GDM screen

2018-10-21 Thread Scott Palmer 
** Attachment added: "the horizontal band"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1799061/+attachment/5203629/+files/20181020_172736.jpg

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

Title:
  Corruption at GDM screen

Status in xorg package in Ubuntu:
  New

Bug description:
  Video does not appear to be getting set correctly for GDM but seems
  "corrected" after I login.

  I have attached some screenshots.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 21 08:01:42 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 550 640SP / RX 
560/560X] [1002:67ff] (rev cf) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Baffin [Radeon RX 550 
640SP / RX 560/560X] [1462:8a91]
  InstallationDate: Installed on 2018-10-20 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=31f5be02-c37e-43e6-96f2-8c912726514e ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2104
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH Z77
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2104:bd08/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHZ77:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1799061/+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 1799061] Re: Corruption at GDM screen

2018-10-21 Thread Scott Palmer 
** Attachment added: "the bright box"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1799061/+attachment/5203630/+files/20181020_172739.jpg

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

Title:
  Corruption at GDM screen

Status in xorg package in Ubuntu:
  New

Bug description:
  Video does not appear to be getting set correctly for GDM but seems
  "corrected" after I login.

  I have attached some screenshots.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 21 08:01:42 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 550 640SP / RX 
560/560X] [1002:67ff] (rev cf) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Baffin [Radeon RX 550 
640SP / RX 560/560X] [1462:8a91]
  InstallationDate: Installed on 2018-10-20 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=31f5be02-c37e-43e6-96f2-8c912726514e ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2104
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH Z77
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2104:bd08/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHZ77:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1799061/+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 1799061] Re: Corruption at GDM screen

2018-10-21 Thread Scott Palmer 
Also note that the screen jitters at the GDM login screen.

My video card does not exhibit have any of these issues when I boot into
Windows 10.

Sometimes logging in doesn't fix the jittering so I reboot into Windows
10.

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

Title:
  Corruption at GDM screen

Status in xorg package in Ubuntu:
  New

Bug description:
  Video does not appear to be getting set correctly for GDM but seems
  "corrected" after I login.

  I have attached some screenshots.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 21 08:01:42 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 550 640SP / RX 
560/560X] [1002:67ff] (rev cf) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Baffin [Radeon RX 550 
640SP / RX 560/560X] [1462:8a91]
  InstallationDate: Installed on 2018-10-20 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=31f5be02-c37e-43e6-96f2-8c912726514e ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2104
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH Z77
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2104:bd08/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHZ77:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1799061/+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 1799061] [NEW] Corruption at GDM screen

2018-10-21 Thread Scott Palmer 
Public bug reported:

Video does not appear to be getting set correctly for GDM but seems
"corrected" after I login.

I have attached some screenshots.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: xorg 1:7.7+19ubuntu8
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct 21 08:01:42 2018
DistUpgraded: Fresh install
DistroCodename: cosmic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 550 640SP / RX 
560/560X] [1002:67ff] (rev cf) (prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] Baffin [Radeon RX 550 
640SP / RX 560/560X] [1462:8a91]
InstallationDate: Installed on 2018-10-20 (0 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=31f5be02-c37e-43e6-96f2-8c912726514e ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/13/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2104
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: SABERTOOTH Z77
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2104:bd08/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHZ77:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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


** Tags: amd64 apport-bug corruption cosmic ubuntu wayland-session

** Attachment added: "20181020_172728.jpg"
   
https://bugs.launchpad.net/bugs/1799061/+attachment/5203613/+files/20181020_172728.jpg

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

Title:
  Corruption at GDM screen

Status in xorg package in Ubuntu:
  New

Bug description:
  Video does not appear to be getting set correctly for GDM but seems
  "corrected" after I login.

  I have attached some screenshots.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 21 08:01:42 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 550 640SP / RX 
560/560X] [1002:67ff] (rev cf) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Baffin [Radeon RX 550 
640SP / RX 560/560X] [1462:8a91]
  InstallationDate: Installed on 2018-10-20 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=31f5be02-c37e-43e6-96f2-8c912726514e ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2104
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH Z77
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias:

[Desktop-packages] [Bug 23001] Re: Copying using ctrl +c doesn't copy in file-roller

2018-09-13 Thread Scott Palmer 
Copy and Paste is not working for me on a freshly installed copy of 18.04.1 
using Wayland.
Is this regression from 3 years ago still not resolved?

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

Title:
  Copying using ctrl +c doesn't copy in file-roller

Status in File Roller:
  Expired
Status in file-roller package in Ubuntu:
  Fix Released

Bug description:
  Reproduce: 
   Open an archive and copy one or more files using ctrl+c

  Expected result:
   The selected file(s) should be copied to clipboard

  Actual result:
   No files are copied to the clipboard

  http://bugzilla.gnome.org/show_bug.cgi?id=143195:
  http://bugzilla.gnome.org/show_bug.cgi?id=143195

To manage notifications about this bug go to:
https://bugs.launchpad.net/file-roller/+bug/23001/+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 1354086] Re: [i5-3230] Tight pyopencl.clmath loops cause out-of-memory system hang

2018-07-16 Thread Rebecca Palmer 
** Patch added: "eventchain-memory-leak.patch"
   
https://bugs.launchpad.net/ubuntu/+source/pyopencl/+bug/1354086/+attachment/5164304/+files/eventchain-memory-leak.patch

** Changed in: beignet (Ubuntu)
   Status: New => In Progress

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

Title:
  [i5-3230] Tight pyopencl.clmath loops cause out-of-memory system hang

Status in beignet package in Ubuntu:
  In Progress
Status in mesa package in Ubuntu:
  New
Status in pyopencl package in Ubuntu:
  Invalid

Bug description:
  In beignet (not pocl), tight loops involving OpenCL array creation and
  destruction, eg. repeated bCL=aCL+bCL (or other pyopencl.clmath
  operations) or repeated pyopencl.enqueue_copy(cq0,bCL.data,aCL.data),
  often hang the whole system, after a number of operations consistent
  with memory exhaustion.

  As waiting for queued operations to finish
  (pyopencl.enqueue_barrier(cq0).wait()) before attempting more avoids
  the bug, but dependencies between the operations (as in the
  bCL=aCL+bCL example) do not, this is probably a result of the
  "allocate memory" step being separate from, and faster than, the "do
  the operation" step, so being able to run ahead until it uses up all
  the memory.

  (Note that while the above wait() can be used as a workaround for this
  bug, it is usually faster to avoid frequent memory allocation
  altogether, by reusing existing arrays; for pyopencl.clmath, this
  means using pyopencl.tools.MemoryPool.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/beignet/+bug/1354086/+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 1354086] Re: [i5-3230] Tight pyopencl.clmath loops cause out-of-memory system hang

2018-07-16 Thread Rebecca Palmer 
There are actually three separate issues here, but as (a) is already
known and (b) is not a bug, I define this bug to be (c).

To understand them, it is necessary to know that OpenCL computations are
asynchronous: a clmath expression like "aCL=bCL+cCL" places this
operation in a CommandQueue and returns without waiting for it to
finish.  (This is to allow the CPU to do other work during the GPU
computation.)

(a) Running out of memory can hang the entire system, rather than ending
just the OpenCL application with CL_OUT_OF_RESOURCES.

This is probably the same long-standing issue (e.g. bug 620074, bug
1504914, bug 1592813) that makes Linux out-of-memory conditions in
general do this.  (The integrated GPUs supported by beignet share the
host's memory.)

(b) In both beignet and pocl (probably all ICDs), a long sequence of
allocate/deallocate operations (e.g. clmath creating a new array each
operation) *without* waiting for results uses up memory, but regularly
waiting for results avoids this.

This is because allocating memory (clCreateBuffer) happens immediately,
but the actual computations are queued, and memory can't be freed until
the computations using it have finished.  Hence, if many operations are
queued without waiting for a result, memory allocation can run far ahead
of computation, filling up the memory.

This is not a bug: don't do that.  Either wait for results often enough
that this doesn't build up to the point of running out of memory, or
(better for performance) re-use existing memory objects instead of
allocating/deallocating.  (To do the latter with clmath, use
pyopencl.tools.MemoryPool.)

While investigating this I discovered that all beignet queues are out-
of-order execution even if the user requested in-order, which is a bug,
but is not the cause of this issue.

(c) In beignet but not pocl, a long sequence of clmath operations leaks
memory, even with regular waits.

To ensure that intermediate results are calculated before they are used,
clmath arrays use Event objects to track dependencies.  A beignet event
includes references to the event(s) it depends on
(https://sources.debian.org/src/beignet/1.3.2-2/src/cl_event.h/?hl=47#L40),
and continues to hold these as long as the event object exists, even if
it has completed and been waited for.  As OpenCL objects are freed by
reference counting, this means that as long as the last event in a
dependency tree exists, the whole tree of (recursive) dependencies also
exists, taking up memory (~20kB per event).

pocl avoids this by dropping these references after completion (
https://sources.debian.org/src/pocl/1.1-5/lib/CL/devices/common.c/?hl=722#L714
); the attached patch makes beignet do so.  Checking the source suggests
mesa is also affected (
https://sources.debian.org/src/mesa/18.1.3-1/src/gallium/state_trackers/clover/core/event.hpp/?hl=84#L34
), but I don't have the hardware to try it.  (The OpenCL part of mesa is
AMD/Radeon only.)


** Also affects: mesa (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: pyopencl (Ubuntu)
   Status: New => Invalid

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

Title:
  [i5-3230] Tight pyopencl.clmath loops cause out-of-memory system hang

Status in beignet package in Ubuntu:
  In Progress
Status in mesa package in Ubuntu:
  New
Status in pyopencl package in Ubuntu:
  Invalid

Bug description:
  In beignet (not pocl), tight loops involving OpenCL array creation and
  destruction, eg. repeated bCL=aCL+bCL (or other pyopencl.clmath
  operations) or repeated pyopencl.enqueue_copy(cq0,bCL.data,aCL.data),
  often hang the whole system, after a number of operations consistent
  with memory exhaustion.

  As waiting for queued operations to finish
  (pyopencl.enqueue_barrier(cq0).wait()) before attempting more avoids
  the bug, but dependencies between the operations (as in the
  bCL=aCL+bCL example) do not, this is probably a result of the
  "allocate memory" step being separate from, and faster than, the "do
  the operation" step, so being able to run ahead until it uses up all
  the memory.

  (Note that while the above wait() can be used as a workaround for this
  bug, it is usually faster to avoid frequent memory allocation
  altogether, by reusing existing arrays; for pyopencl.clmath, this
  means using pyopencl.tools.MemoryPool.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/beignet/+bug/1354086/+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 1709399] Re: LLVM symbols should be versioned to avoid crashing applications that load mesa's swrast and also use a different libLLVM

2018-07-07 Thread Rebecca Palmer 
Current llvm-toolchain-* packages do have versioned symbols (since
3.8.1-22 / 3.9.1-8 / 4.0-5: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=849098), but this 3.8 has not been backported.

Note that loading the *same* LLVM version twice can also crash, for a
different reason: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=852746

** Bug watch added: Debian Bug tracker #849098
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849098

** Bug watch added: Debian Bug tracker #852746
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852746

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

Title:
  LLVM symbols should be versioned to avoid crashing applications that
  load mesa's swrast and also use a different libLLVM

Status in llvm-toolchain-3.8 package in Ubuntu:
  Confirmed

Bug description:
  The libgl1-mesa-dri-lts-xenial package depend on libLLVM-3.8.so.1 from
  the libllvm3.8v4 package; this library gets used when using software
  OpenGL rendering on a remote display. As a result, applications based
  on Qt5 that also use libLLVM features provided by another (newer) LLVM
  version will crash when invoked from a remote X terminal.

  Example: KDevelop5 uses libclang (and this libLLVM) for C/C++ parsing;
  I build it to use the LLVM/Clang 4.0 packages from llvm.org (and self-
  built Qt5 and KF5 libraries) and can thus not render to a remote X
  server (XQuartz on my Mac).

  There is an upstream LLVM patch which solves the issue by adding
  versioning info to libLLVM:

  https://bugs.kde.org/show_bug.cgi?id=373614
  https://reviews.llvm.org/D31524

  Please consider backporting this patch to LLVM 3.8 (or rebuilding the
  mesa package to use a (much) more recent LLVM version that already
  contains the patch).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-3.8/+bug/1709399/+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 1724921] Re: VLANs get incorrectly listed under Bluetooth

2018-07-05 Thread Scott Palmer 
This also affects 18.04 (updated to July 5, 2018)

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

Title:
  VLANs get incorrectly listed under Bluetooth

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in network-manager-applet package in Ubuntu:
  Confirmed

Bug description:
  I expected them to show up under Wired because the VLANs' associated
  adapter is wired.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager-gnome 1.8.4-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 11:25:17 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  IpRoute:
   default via 192.168.50.253 dev vlan757 proto static metric 400 
   169.254.0.0/16 dev vlan757 scope link metric 1000 
   192.168.50.0/24 dev vlan757 proto kernel scope link src 192.168.50.222 
metric 400
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager-applet
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE   STATE
  ACTIVE-PATH SLAVE 
   VLAN Camera 1a430a37-b4b3-461c-87bd-d60b547dd369  vlan
1508437383  Thu 19 Oct 2017 11:23:03 AM PDT  yes  0 
no/org/freedesktop/NetworkManager/Settings/4  yes vlan757  
activated  /org/freedesktop/NetworkManager/ActiveConnection/8  --
   Wired connection 1  23ca82a4-d9c5-3d59-ac84-56db17873201  802-3-ethernet  
1508433170  Thu 19 Oct 2017 10:12:50 AM PDT  no   4294966297
no/org/freedesktop/NetworkManager/Settings/1  no  --   --   
  --  --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1724921/+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 1780360] [NEW] Wayland session doesnt work with Monitor in either Portrait mode

2018-07-05 Thread Scott Palmer 
Public bug reported:

When I use a Wayland session I am unable to use either Portrait mode.

I have the same problem at work using my Intel Integrated Video on my
Lenovo X230 laptop.

Given that both AMD and Intel are broken, it looks to be a regression of
some sort.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_23_25_generic_40
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
Date: Thu Jul  5 17:29:56 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.2.10, 4.15.0-22-generic, x86_64: installed
 virtualbox, 5.2.10, 4.15.0-23-generic, x86_64: installed
DpkgLog:
 
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Polaris11] [1002:67ff] (rev cf) 
(prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] Baffin [Radeon RX 560] 
[1462:8a91]
InstallationDate: Installed on 2018-05-27 (39 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: System manufacturer System Product Name
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=0c69e0ec-e162-4882-aa5d-337219c7f2c8 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/13/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2104
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: SABERTOOTH Z77
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2104:bd08/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHZ77:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic ubuntu wayland-session

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

Title:
  Wayland session doesnt work with Monitor in either Portrait mode

Status in xorg package in Ubuntu:
  New

Bug description:
  When I use a Wayland session I am unable to use either Portrait mode.

  I have the same problem at work using my Intel Integrated Video on my
  Lenovo X230 laptop.

  Given that both AMD and Intel are broken, it looks to be a regression
  of some sort.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_23_25_generic_40
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Thu Jul  5 17:29:56 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.10, 4.15.0-22-generic, x86_64: installed
   virtualbox, 5.2.10, 4.15.0-23-generic, x86_64: installed
  DpkgLog:
   
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Polaris11] [1002:67ff] (rev 
cf) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Baffin [Radeon RX 560] 
[1462:8a91]
  InstallationDate: Installed on 2018-05-27 (39 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=

[Desktop-packages] [Bug 1683512] Re: No libcuda.so.1 after upgrading to 381-driver

2018-05-06 Thread Rebecca Palmer 
('invalid' as in 'not our (theano's) bug')

Where did you obtain nvidia-381 (Ubuntu itself went straight from -375
to -384)? the Nvidia website? a PPA?

nvidia-graphics-drivers-384 is now available in xenial-updates: is that
any better?

(libcudata.so.8 is probably a different library, not the file you want.)

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

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

Title:
  No libcuda.so.1 after upgrading to 381-driver

Status in nvidia-graphics-drivers package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Confirmed
Status in theano package in Ubuntu:
  Invalid

Bug description:
  I had a problem with window edges after waking from suspend - see
  here: https://askubuntu.com/questions/896221/strange-artifacts-along-
  window-borders-after-waking-computer-from-sleep-mode/

  For this reason I upgraded to the newer driver, from 375.39 to 381.09.

  I have posted this question on AskUbuntu, with some extra information!
  
https://askubuntu.com/questions/905993/missing-libcuda-so-1-file-after-upgrading-to-newest-nvidia-driver

  Since upgrading, I have had to reinstall the Cuda Toolkit 8.0 (and CUDNN 
v5.1), however there seems to be a driver file missing, which prevents me from 
installing both Tensorflow and the gputools package in R, which build upon the 
Cuda Toolkit, which in turn needs the missing libcuda.so.1 file.
  Neither Tensorflow no gputools are able to locate the file: libcuda.so.1.
  Here is a similar issue, but with older drivers involved:  
https://github.com/tensorflow/tensorflow/issues/4078

  I have read that I could possibly create this file as it is a symlink, 
however I would prefer not to, as I do not know what other dependencies exist.
  Example of possible workaround:   
http://stackoverflow.com/questions/41890549/tensorflow-cannot-open-libcuda-so-1

  I am running Ubuntu 16.04.

  Can somebody see why this file is missing or propose a stable
  solution?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1683512/+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 1710754] Re: [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at all

2018-03-17 Thread Scott Palmer 
Also note that this problem also affects Bionic 18.04 users with
4.15.0-12-generic

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

Title:
  [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at
  all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  When I start my computer I have no sound.  If I unplug my line out and
  plug it in again sound works fine. In Windows 10 this unplug and
  replug is not required (the jack is fine).

  Running:
   $ amixer -c0 contents
  so I can compare the non working state with the working state, the following 
differences exist:

  Non Working:
  numid=43,iface=CARD,name='Line Out Front Jack'
; type=BOOLEAN,access=r---,values=1
: values=off
  numid=35,iface=MIXER,name='IEC958 Playback Switch'
; type=BOOLEAN,access=rw--,values=1
: values=on

  Working:
  numid=43,iface=CARD,name='Line Out Front Jack'
; type=BOOLEAN,access=r---,values=1
: values=on
  numid=35,iface=MIXER,name='IEC958 Playback Switch'
; type=BOOLEAN,access=rw--,values=1
: values=off

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
  Uname: Linux 4.11.0-13-generic x86_64
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  scott  1154 F pulseaudio
   /dev/snd/controlC1:  scott  1154 F pulseaudio
  CurrentDesktop: GNOME
  Date: Mon Aug 14 19:05:12 2017
  InstallationDate: Installed on 2017-08-07 (8 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful
  Symptom_Card: Built-in Audio - HDA Intel MID
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  scott  1154 F pulseaudio
   /dev/snd/controlC1:  scott  1154 F pulseaudio
  Symptom_Jack: Green Line Out, Rear
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1807
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P7P55D DELUXE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1807:bd07/22/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55DDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1710754/+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 1710754] Re: [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at all

2018-03-17 Thread Scott Palmer 
** Attachment added: "Fresh boot -- after re-plug -- woking sound from rear 
green jack"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1710754/+attachment/5082539/+files/alsa-info-after.txt

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

Title:
  [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at
  all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  When I start my computer I have no sound.  If I unplug my line out and
  plug it in again sound works fine. In Windows 10 this unplug and
  replug is not required (the jack is fine).

  Running:
   $ amixer -c0 contents
  so I can compare the non working state with the working state, the following 
differences exist:

  Non Working:
  numid=43,iface=CARD,name='Line Out Front Jack'
; type=BOOLEAN,access=r---,values=1
: values=off
  numid=35,iface=MIXER,name='IEC958 Playback Switch'
; type=BOOLEAN,access=rw--,values=1
: values=on

  Working:
  numid=43,iface=CARD,name='Line Out Front Jack'
; type=BOOLEAN,access=r---,values=1
: values=on
  numid=35,iface=MIXER,name='IEC958 Playback Switch'
; type=BOOLEAN,access=rw--,values=1
: values=off

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
  Uname: Linux 4.11.0-13-generic x86_64
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  scott  1154 F pulseaudio
   /dev/snd/controlC1:  scott  1154 F pulseaudio
  CurrentDesktop: GNOME
  Date: Mon Aug 14 19:05:12 2017
  InstallationDate: Installed on 2017-08-07 (8 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful
  Symptom_Card: Built-in Audio - HDA Intel MID
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  scott  1154 F pulseaudio
   /dev/snd/controlC1:  scott  1154 F pulseaudio
  Symptom_Jack: Green Line Out, Rear
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1807
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P7P55D DELUXE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1807:bd07/22/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55DDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1710754/+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 1710754] Re: [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at all

2018-03-17 Thread Scott Palmer 
** Attachment added: "Fresh boot -- no sound from rear green jack"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1710754/+attachment/5082538/+files/alsa-info-before.txt

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

Title:
  [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at
  all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  When I start my computer I have no sound.  If I unplug my line out and
  plug it in again sound works fine. In Windows 10 this unplug and
  replug is not required (the jack is fine).

  Running:
   $ amixer -c0 contents
  so I can compare the non working state with the working state, the following 
differences exist:

  Non Working:
  numid=43,iface=CARD,name='Line Out Front Jack'
; type=BOOLEAN,access=r---,values=1
: values=off
  numid=35,iface=MIXER,name='IEC958 Playback Switch'
; type=BOOLEAN,access=rw--,values=1
: values=on

  Working:
  numid=43,iface=CARD,name='Line Out Front Jack'
; type=BOOLEAN,access=r---,values=1
: values=on
  numid=35,iface=MIXER,name='IEC958 Playback Switch'
; type=BOOLEAN,access=rw--,values=1
: values=off

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
  Uname: Linux 4.11.0-13-generic x86_64
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  scott  1154 F pulseaudio
   /dev/snd/controlC1:  scott  1154 F pulseaudio
  CurrentDesktop: GNOME
  Date: Mon Aug 14 19:05:12 2017
  InstallationDate: Installed on 2017-08-07 (8 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful
  Symptom_Card: Built-in Audio - HDA Intel MID
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  scott  1154 F pulseaudio
   /dev/snd/controlC1:  scott  1154 F pulseaudio
  Symptom_Jack: Green Line Out, Rear
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1807
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P7P55D DELUXE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1807:bd07/22/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55DDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1710754/+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 1756484] Re: Screen flickers and small moving artifacts

2018-03-16 Thread Scott Palmer 
I believe I have corrected this by changing my refresh rate from 59.99
Hz to 59.86 Hz.

Is this a requirement for 2560x1600 resolution on DL-DVI?  Should this
perhaps be communicated upstream to someone who knows better?

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

Title:
  Screen flickers and small moving artifacts

Status in xorg package in Ubuntu:
  New

Bug description:
  This is likely a wayland issue.  I can't bear the tearing if I don't
  use wayland.

  I get screen flickering (approximately every 5 seconds) and some
  windows seem to bring up some mis-colored moving artifacts that clear
  when the window is closed.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 16 20:07:47 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Barts PRO [Radeon HD 6850] 
[1002:6739] (prog-if 00 [VGA controller])
 Subsystem: XFX Pine Group Inc. Barts PRO [Radeon HD 6850] [1682:3112]
  InstallationDate: Installed on 2018-03-17 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180310)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic 
root=UUID=7cf929d1-3748-4cac-bd67-e25c2fdf0038 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLogOld:
   
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1807
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P7P55D DELUXE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1807:bd07/22/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55DDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1756484/+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 1710752] Re: Intel HDA Audio doesn't work

2018-03-16 Thread Scott Palmer 
I just installed the 18.04 daily and formatted a fresh partition (no
prior home directory or any existing data used) and this is still an
issue in 4.15.0-12-generic.

Can I run a command to manually turn on this jack at startup or force it
to recheck that input to see if something is plugged in?

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

Title:
  Intel HDA Audio doesn't work

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I get no sound on most boots.  In Sound settings the default Output device is 
HDMI / DisplayPort -
   Built-in Audio and there is no option to select anything else.  If I unplug 
my line out and plug it in again it shows up in the list, automatically sets 
itself as default and sound works fine. In Windows 10 this unplug and replug is 
not required (the jack is fine).

  Running:
   $ amixer -c0 contents
  so I can compare the non working state with the working state, the following 
differences exist:

  Non Working:
  numid=43,iface=CARD,name='Line Out Front Jack'
; type=BOOLEAN,access=r---,values=1
: values=off
  numid=35,iface=MIXER,name='IEC958 Playback Switch'
; type=BOOLEAN,access=rw--,values=1
: values=on

  Working:
  numid=43,iface=CARD,name='Line Out Front Jack'
; type=BOOLEAN,access=r---,values=1
: values=on
  numid=35,iface=MIXER,name='IEC958 Playback Switch'
; type=BOOLEAN,access=rw--,values=1
: values=off

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1710752/+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 1756484] [NEW] Screen flickers and small moving artifacts

2018-03-16 Thread Scott Palmer 
Public bug reported:

This is likely a wayland issue.  I can't bear the tearing if I don't use
wayland.

I get screen flickering (approximately every 5 seconds) and some windows
seem to bring up some mis-colored moving artifacts that clear when the
window is closed.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
Uname: Linux 4.15.0-12-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 16 20:07:47 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Barts PRO [Radeon HD 6850] [1002:6739] 
(prog-if 00 [VGA controller])
   Subsystem: XFX Pine Group Inc. Barts PRO [Radeon HD 6850] [1682:3112]
InstallationDate: Installed on 2018-03-17 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180310)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic 
root=UUID=7cf929d1-3748-4cac-bd67-e25c2fdf0038 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
XorgLogOld:
 
dmi.bios.date: 07/22/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1807
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P7P55D DELUXE
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1807:bd07/22/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55DDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.90-1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic reproducible ubuntu wayland-session

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

Title:
  Screen flickers and small moving artifacts

Status in xorg package in Ubuntu:
  New

Bug description:
  This is likely a wayland issue.  I can't bear the tearing if I don't
  use wayland.

  I get screen flickering (approximately every 5 seconds) and some
  windows seem to bring up some mis-colored moving artifacts that clear
  when the window is closed.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 16 20:07:47 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Barts PRO [Radeon HD 6850] 
[1002:6739] (prog-if 00 [VGA controller])
 Subsystem: XFX Pine Group Inc. Barts PRO [Radeon HD 6850] [1682:3112]
  InstallationDate: Installed on 2018-03-17 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180310)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic 
root=UUID=7cf929d1-3748-4cac-bd67-e25c2fdf0038 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLogOld:
   
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1807
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P7P55D DELUXE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias:

[Desktop-packages] [Bug 1725532] Re: wired network ignores auto connect setting and does not auto connect

2017-10-29 Thread Scott Palmer 
The other bug was closed.  Here is the correct one.

https://bugzilla.gnome.org/show_bug.cgi?id=789626

** Bug watch added: GNOME Bug Tracker #789626
   https://bugzilla.gnome.org/show_bug.cgi?id=789626

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

Title:
  wired network ignores auto connect setting and does not auto connect

Status in network-manager-applet package in Ubuntu:
  New

Bug description:
  My onboard Intel network adapter has [X] Connect automatically but
  when I start my Gnome session, I always have to tell it to Connect
  which it does without error.

  You can't see it in the Gnome dialog windows but this connection is
  set to also connect to a VPN.  I setup this connection with nm-
  connection-editor.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager-gnome 1.8.4-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 20 17:26:18 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-10-03 (17 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RfKill:
   
  SourcePackage: network-manager-applet
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1725532/+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 1723815] Re: Unable to show files on MTP connection

2017-10-29 Thread Scott Palmer 
https://gitlab.gnome.org/GNOME/nautilus/issues/91

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

Title:
  Unable to show files on MTP connection

Status in gvfs package in Ubuntu:
  New

Bug description:
  Opening "Samsung_Android\Card\DCIM\Camera" folder with many images
  gets stuck at "Loading..." and never shows anything.  I have waited 10
  minutes.  There is no error and not a single icon shows.

  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
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 15 16:36:50 2017
  InstallationDate: Installed on 2017-10-03 (12 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1723815/+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 1725532] Re: wired network ignores auto connect setting and does not auto connect

2017-10-29 Thread Scott Palmer 
I tried to file a bug report here:

https://gitlab.gnome.org/GNOME/Infrastructure/issues/50

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

Title:
  wired network ignores auto connect setting and does not auto connect

Status in network-manager-applet package in Ubuntu:
  New

Bug description:
  My onboard Intel network adapter has [X] Connect automatically but
  when I start my Gnome session, I always have to tell it to Connect
  which it does without error.

  You can't see it in the Gnome dialog windows but this connection is
  set to also connect to a VPN.  I setup this connection with nm-
  connection-editor.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager-gnome 1.8.4-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 20 17:26:18 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-10-03 (17 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RfKill:
   
  SourcePackage: network-manager-applet
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1725532/+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 1710754] Re: [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at all

2017-10-28 Thread Scott Palmer 
This was fixed for a while by an update that came in, but now this
problem has come back.

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

Title:
  [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at
  all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  When I start my computer I have no sound.  If I unplug my line out and
  plug it in again sound works fine. In Windows 10 this unplug and
  replug is not required (the jack is fine).

  Running:
   $ amixer -c0 contents
  so I can compare the non working state with the working state, the following 
differences exist:

  Non Working:
  numid=43,iface=CARD,name='Line Out Front Jack'
; type=BOOLEAN,access=r---,values=1
: values=off
  numid=35,iface=MIXER,name='IEC958 Playback Switch'
; type=BOOLEAN,access=rw--,values=1
: values=on

  Working:
  numid=43,iface=CARD,name='Line Out Front Jack'
; type=BOOLEAN,access=r---,values=1
: values=on
  numid=35,iface=MIXER,name='IEC958 Playback Switch'
; type=BOOLEAN,access=rw--,values=1
: values=off

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
  Uname: Linux 4.11.0-13-generic x86_64
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  scott  1154 F pulseaudio
   /dev/snd/controlC1:  scott  1154 F pulseaudio
  CurrentDesktop: GNOME
  Date: Mon Aug 14 19:05:12 2017
  InstallationDate: Installed on 2017-08-07 (8 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful
  Symptom_Card: Built-in Audio - HDA Intel MID
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  scott  1154 F pulseaudio
   /dev/snd/controlC1:  scott  1154 F pulseaudio
  Symptom_Jack: Green Line Out, Rear
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1807
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P7P55D DELUXE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1807:bd07/22/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55DDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1710754/+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 1724977] Re: two mouse cursors visible at the same time

2017-10-22 Thread Scott Palmer 
It could be related to this bug:

See Comment #62   https://bugzilla.gnome.org/show_bug.cgi?id=745079#c62

** Bug watch added: GNOME Bug Tracker #745079
   https://bugzilla.gnome.org/show_bug.cgi?id=745079

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

Title:
  two mouse cursors visible at the same time

Status in xorg package in Ubuntu:
  New

Bug description:
  When my 2nd Asus (Ancor) display is in portrait mode and is set to be
  to the left of my centered landscape display in extended mode, moving
  the mouse to roughly the left 20% of my landscape display will show a
  mouse cursor on my landcape display AND portrait display at the same
  time.  Oddly moving a window into this area only shows on the
  landscape display.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 13:43:30 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:2203]
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 343522U
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=df6662ff-9496-4ff5-8165-82efdbf0b335 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/28/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GCET99WW (2.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 343522U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGCET99WW(2.59):bd05/28/2014:svnLENOVO:pn343522U:pvrThinkPadX230Tablet:rvnLENOVO:rn343522U:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230 Tablet
  dmi.product.name: 343522U
  dmi.product.version: ThinkPad X230 Tablet
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1724977/+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 1093129] Re: system settings -> printer is not able to delete not started print jobs

2017-10-22 Thread Scott Palmer 
Also, The Active Jobs window does not seem to ever update / refresh
itself.

I accidentally printed the same document two times.  My printer wasn't
plugged in so I just went to the Active Jobs window and clicked the [X]
button to delete the "Pending" entry.  It did nothing.  I plugged in my
printer and both jobs printed.  Unexpectedly, both jobs are still listed
in Active Jobs.  The top entry still says "Processing" and the second
entry still says "Pending".

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

Title:
  system settings ->  printer is not able to delete not started print
  jobs

Status in gnome-control-center package in Ubuntu:
  Confirmed

Bug description:
  System settings -> Printer -> Jobs

  shows correct all print jobs, but it is not able to delete them.

  The pause and stop buttons are availabe and clickable, but do not take
  any action on the print jobs.

  
  Steps to reproduce(not tested):

  1.Send a print job from firefox(html)
  2.Send a second print job from evince(pdf)
  3.Call System Settings -> Printers -> Jobs
  4.Try to stop the second not started print job with the buttons for that
  5.See that failing
  6.Have a not wanted print.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-control-center 1:3.6.3-0ubuntu9
  ProcVersionSignature: Ubuntu 3.7.0-7.15-generic 3.7.0
  Uname: Linux 3.7.0-7-generic x86_64
  ApportVersion: 2.7-0ubuntu2
  Architecture: amd64
  Date: Sat Dec 22 17:03:57 2012
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2012-07-22 (152 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120722)
  MarkForUpload: True
  ProcEnviron:
   PATH=(custom, no username)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to raring on 2012-11-15 (36 days ago)
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu6.1
   deja-dup25.3-0ubuntu1
   gnome-control-center-signon 0.1.2bzr12.12.05-0ubuntu1
   indicator-datetime  12.10.3daily12.11.23-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1093129/+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 1093129] Re: system settings -> printer is not able to delete not started print jobs

2017-10-22 Thread Scott Palmer 
Oh!  I should also note that I am running Ubuntu 17.10.
Printer is a Samsung C460.

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

Title:
  system settings ->  printer is not able to delete not started print
  jobs

Status in gnome-control-center package in Ubuntu:
  Confirmed

Bug description:
  System settings -> Printer -> Jobs

  shows correct all print jobs, but it is not able to delete them.

  The pause and stop buttons are availabe and clickable, but do not take
  any action on the print jobs.

  
  Steps to reproduce(not tested):

  1.Send a print job from firefox(html)
  2.Send a second print job from evince(pdf)
  3.Call System Settings -> Printers -> Jobs
  4.Try to stop the second not started print job with the buttons for that
  5.See that failing
  6.Have a not wanted print.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-control-center 1:3.6.3-0ubuntu9
  ProcVersionSignature: Ubuntu 3.7.0-7.15-generic 3.7.0
  Uname: Linux 3.7.0-7-generic x86_64
  ApportVersion: 2.7-0ubuntu2
  Architecture: amd64
  Date: Sat Dec 22 17:03:57 2012
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2012-07-22 (152 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120722)
  MarkForUpload: True
  ProcEnviron:
   PATH=(custom, no username)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to raring on 2012-11-15 (36 days ago)
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu6.1
   deja-dup25.3-0ubuntu1
   gnome-control-center-signon 0.1.2bzr12.12.05-0ubuntu1
   indicator-datetime  12.10.3daily12.11.23-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1093129/+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 1725532] [NEW] wired network ignores auto connect setting and does not auto connect

2017-10-20 Thread Scott Palmer 
Public bug reported:

My onboard Intel network adapter has [X] Connect automatically but when
I start my Gnome session, I always have to tell it to Connect which it
does without error.

You can't see it in the Gnome dialog windows but this connection is set
to also connect to a VPN.  I setup this connection with nm-connection-
editor.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: network-manager-gnome 1.8.4-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 20 17:26:18 2017
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2017-10-03 (17 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
RfKill:
 
SourcePackage: network-manager-applet
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled

** Affects: network-manager-applet (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful

** Tags removed: wayland-session

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

Title:
  wired network ignores auto connect setting and does not auto connect

Status in network-manager-applet package in Ubuntu:
  New

Bug description:
  My onboard Intel network adapter has [X] Connect automatically but
  when I start my Gnome session, I always have to tell it to Connect
  which it does without error.

  You can't see it in the Gnome dialog windows but this connection is
  set to also connect to a VPN.  I setup this connection with nm-
  connection-editor.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager-gnome 1.8.4-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 20 17:26:18 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-10-03 (17 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RfKill:
   
  SourcePackage: network-manager-applet
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1725532/+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 1724977] Re: two mouse cursors visible at the same time

2017-10-19 Thread Scott Palmer 
I have attached a photo of my screen showing this behavior.

Notice how the icon is shown with correct orientation but the mouse
cursor has landscape orientation.

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

Title:
  two mouse cursors visible at the same time

Status in xorg package in Ubuntu:
  New

Bug description:
  When my 2nd Asus (Ancor) display is in portrait mode and is set to be
  to the left of my centered landscape display in extended mode, moving
  the mouse to roughly the left 20% of my landscape display will show a
  mouse cursor on my landcape display AND portrait display at the same
  time.  Oddly moving a window into this area only shows on the
  landscape display.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 13:43:30 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:2203]
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 343522U
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=df6662ff-9496-4ff5-8165-82efdbf0b335 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/28/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GCET99WW (2.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 343522U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGCET99WW(2.59):bd05/28/2014:svnLENOVO:pn343522U:pvrThinkPadX230Tablet:rvnLENOVO:rn343522U:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230 Tablet
  dmi.product.name: 343522U
  dmi.product.version: ThinkPad X230 Tablet
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1724977/+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 1724977] Re: two mouse cursors visible at the same time

2017-10-19 Thread Scott Palmer 
Oops, I attached the wrong picture.  This one is correct.

** Attachment added: "20171019_140503.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1724977/+attachment/4976890/+files/20171019_140503.jpg

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

Title:
  two mouse cursors visible at the same time

Status in xorg package in Ubuntu:
  New

Bug description:
  When my 2nd Asus (Ancor) display is in portrait mode and is set to be
  to the left of my centered landscape display in extended mode, moving
  the mouse to roughly the left 20% of my landscape display will show a
  mouse cursor on my landcape display AND portrait display at the same
  time.  Oddly moving a window into this area only shows on the
  landscape display.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 13:43:30 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:2203]
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 343522U
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=df6662ff-9496-4ff5-8165-82efdbf0b335 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/28/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GCET99WW (2.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 343522U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGCET99WW(2.59):bd05/28/2014:svnLENOVO:pn343522U:pvrThinkPadX230Tablet:rvnLENOVO:rn343522U:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230 Tablet
  dmi.product.name: 343522U
  dmi.product.version: ThinkPad X230 Tablet
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1724977/+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 1724977] Re: two mouse cursors visible at the same time

2017-10-19 Thread Scott Palmer 
I have attached a copy of a monitor.xml file I can use that will yield
this behavior.

** Attachment added: "monitors.xml"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1724977/+attachment/4976873/+files/monitors.xml-order_and_rotation_correct

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

Title:
  two mouse cursors visible at the same time

Status in xorg package in Ubuntu:
  New

Bug description:
  When my 2nd Asus (Ancor) display is in portrait mode and is set to be
  to the left of my centered landscape display in extended mode, moving
  the mouse to roughly the left 20% of my landscape display will show a
  mouse cursor on my landcape display AND portrait display at the same
  time.  Oddly moving a window into this area only shows on the
  landscape display.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 13:43:30 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:2203]
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 343522U
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=df6662ff-9496-4ff5-8165-82efdbf0b335 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/28/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GCET99WW (2.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 343522U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGCET99WW(2.59):bd05/28/2014:svnLENOVO:pn343522U:pvrThinkPadX230Tablet:rvnLENOVO:rn343522U:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230 Tablet
  dmi.product.name: 343522U
  dmi.product.version: ThinkPad X230 Tablet
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1724977/+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 1724979] [NEW] system freeze when activating my 3rd display

2017-10-19 Thread Scott Palmer 
Public bug reported:

On Windows I use all three displays without issue, but I can only seem
to activate any 2 of my 3 displays in Ubuntu.  The moment I activate the
3rd, the system freezes.

It may also be worth noting that due to this I have been disabling my
built-in laptop display and leaving my two larger desktop displays
active.  When I open my laptop the whole system freezes and has to be
power cycled.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 19 13:48:32 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:2203]
InstallationDate: Installed on 2017-10-19 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
MachineType: LENOVO 343522U
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=df6662ff-9496-4ff5-8165-82efdbf0b335 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/28/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: GCET99WW (2.59 )
dmi.board.asset.tag: Not Available
dmi.board.name: 343522U
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrGCET99WW(2.59):bd05/28/2014:svnLENOVO:pn343522U:pvrThinkPadX230Tablet:rvnLENOVO:rn343522U:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad X230 Tablet
dmi.product.name: 343522U
dmi.product.version: ThinkPad X230 Tablet
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug artful ubuntu wayland-session

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

Title:
  system freeze when activating my 3rd display

Status in xorg package in Ubuntu:
  New

Bug description:
  On Windows I use all three displays without issue, but I can only seem
  to activate any 2 of my 3 displays in Ubuntu.  The moment I activate
  the 3rd, the system freezes.

  It may also be worth noting that due to this I have been disabling my
  built-in laptop display and leaving my two larger desktop displays
  active.  When I open my laptop the whole system freezes and has to be
  power cycled.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 13:48:32 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:2203]
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 343522U
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=df6662ff-9496-4ff5-8165-82efdbf0b335 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/28/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GCET99WW (2.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 343522U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias:

[Desktop-packages] [Bug 1724977] [NEW] two mouse cursors visible at the same time

2017-10-19 Thread Scott Palmer 
Public bug reported:

When my 2nd Asus (Ancor) display is in portrait mode and is set to be to
the left of my centered landscape display in extended mode, moving the
mouse to roughly the left 20% of my landscape display will show a mouse
cursor on my landcape display AND portrait display at the same time.
Oddly moving a window into this area only shows on the landscape
display.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 19 13:43:30 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:2203]
InstallationDate: Installed on 2017-10-19 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
MachineType: LENOVO 343522U
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=df6662ff-9496-4ff5-8165-82efdbf0b335 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/28/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: GCET99WW (2.59 )
dmi.board.asset.tag: Not Available
dmi.board.name: 343522U
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrGCET99WW(2.59):bd05/28/2014:svnLENOVO:pn343522U:pvrThinkPadX230Tablet:rvnLENOVO:rn343522U:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad X230 Tablet
dmi.product.name: 343522U
dmi.product.version: ThinkPad X230 Tablet
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug artful ubuntu wayland-session

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

Title:
  two mouse cursors visible at the same time

Status in xorg package in Ubuntu:
  New

Bug description:
  When my 2nd Asus (Ancor) display is in portrait mode and is set to be
  to the left of my centered landscape display in extended mode, moving
  the mouse to roughly the left 20% of my landscape display will show a
  mouse cursor on my landcape display AND portrait display at the same
  time.  Oddly moving a window into this area only shows on the
  landscape display.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 13:43:30 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:2203]
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 343522U
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=df6662ff-9496-4ff5-8165-82efdbf0b335 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/28/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GCET99WW (2.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 343522U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGCET99WW(2.59):bd05/28/2014:svnLENOVO:pn343522U:pvrThinkPadX230Tablet:rvnLENOVO:rn343522U:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family:

[Desktop-packages] [Bug 1724966] [NEW] Settings - Display - Primary Display selection does not allow selection of available entries

2017-10-19 Thread Scott Palmer 
Public bug reported:

Settings - Display - Primary Displayoffers me a choice of 3 displays.
Clicking on any of the non checked displays does nothing.

NOTE: My other 2 displays are currently disabled and likely shouldn't be
showing up in this list.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 19 13:27:08 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:2203]
InstallationDate: Installed on 2017-10-19 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
MachineType: LENOVO 343522U
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=df6662ff-9496-4ff5-8165-82efdbf0b335 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/28/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: GCET99WW (2.59 )
dmi.board.asset.tag: Not Available
dmi.board.name: 343522U
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrGCET99WW(2.59):bd05/28/2014:svnLENOVO:pn343522U:pvrThinkPadX230Tablet:rvnLENOVO:rn343522U:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad X230 Tablet
dmi.product.name: 343522U
dmi.product.version: ThinkPad X230 Tablet
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug artful ubuntu

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

Title:
  Settings - Display - Primary Display selection does not allow
  selection of available entries

Status in xorg package in Ubuntu:
  New

Bug description:
  Settings - Display - Primary Displayoffers me a choice of 3 displays.
  Clicking on any of the non checked displays does nothing.

  NOTE: My other 2 displays are currently disabled and likely shouldn't
  be showing up in this list.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 13:27:08 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:2203]
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 343522U
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=df6662ff-9496-4ff5-8165-82efdbf0b335 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/28/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GCET99WW (2.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 343522U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGCET99WW(2.59):bd05/28/2014:svnLENOVO:pn343522U:pvrThinkPadX230Tablet:rvnLENOVO:rn343522U:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230 Tablet
  dmi.product.name: 343522U
  dmi.product.version: ThinkPad X230 Tablet
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri

[Desktop-packages] [Bug 1724955] [NEW] unable to drag monitors in Display Arrangement

2017-10-19 Thread Scott Palmer 
Public bug reported:

I am unable to drag the displays in the Display Arrangement section.  I
have a dual monitor setup and they are in the reverse order.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 19 13:12:07 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:2203]
InstallationDate: Installed on 2017-10-19 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
MachineType: LENOVO 343522U
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=df6662ff-9496-4ff5-8165-82efdbf0b335 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/28/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: GCET99WW (2.59 )
dmi.board.asset.tag: Not Available
dmi.board.name: 343522U
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrGCET99WW(2.59):bd05/28/2014:svnLENOVO:pn343522U:pvrThinkPadX230Tablet:rvnLENOVO:rn343522U:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad X230 Tablet
dmi.product.name: 343522U
dmi.product.version: ThinkPad X230 Tablet
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug artful ubuntu wayland-session

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

Title:
  unable to drag monitors in Display Arrangement

Status in xorg package in Ubuntu:
  New

Bug description:
  I am unable to drag the displays in the Display Arrangement section.
  I have a dual monitor setup and they are in the reverse order.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 13:12:07 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:2203]
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 343522U
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=df6662ff-9496-4ff5-8165-82efdbf0b335 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/28/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GCET99WW (2.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 343522U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGCET99WW(2.59):bd05/28/2014:svnLENOVO:pn343522U:pvrThinkPadX230Tablet:rvnLENOVO:rn343522U:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230 Tablet
  dmi.product.name: 343522U
  dmi.product.version: ThinkPad X230 Tablet
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A

[Desktop-packages] [Bug 1724926] [NEW] No button to launch nm-connection-editor for Advanced functionality like VLANs

2017-10-19 Thread Scott Palmer 
Public bug reported:

Gnome removed the ability to add/remove VLANs.  When people ask /
complain about how this is to be accomplished, they are usually referred
to nm-connection-editor.

Can a Gnome developer please add an "Advanced Configuration" button that
launches nm-connection-editor?

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: network-manager-gnome 1.8.4-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 19 11:38:58 2017
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2017-10-19 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
IpRoute:
 default via 192.168.50.253 dev vlan757 proto static metric 400 
 169.254.0.0/16 dev vlan757 scope link metric 1000 
 192.168.50.0/24 dev vlan757 proto kernel scope link src 192.168.50.222 metric 
400
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
SourcePackage: network-manager-applet
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con:
 NAMEUUID  TYPE
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE   STATE
  ACTIVE-PATH SLAVE 
 VLAN Camera 1a430a37-b4b3-461c-87bd-d60b547dd369  vlan
1508438283  Thu 19 Oct 2017 11:38:03 AM PDT  yes  0 
no/org/freedesktop/NetworkManager/Settings/4  yes vlan757  
activated  /org/freedesktop/NetworkManager/ActiveConnection/8  --
 Wired connection 1  23ca82a4-d9c5-3d59-ac84-56db17873201  802-3-ethernet  
1508433170  Thu 19 Oct 2017 10:12:50 AM PDT  no   4294966297
no/org/freedesktop/NetworkManager/Settings/1  no  --   --   
  --  --
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled

** Affects: network-manager-applet (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful

** Tags removed: wayland-session

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

Title:
  No button to launch nm-connection-editor for Advanced functionality
  like VLANs

Status in network-manager-applet package in Ubuntu:
  New

Bug description:
  Gnome removed the ability to add/remove VLANs.  When people ask /
  complain about how this is to be accomplished, they are usually
  referred to nm-connection-editor.

  Can a Gnome developer please add an "Advanced Configuration" button
  that launches nm-connection-editor?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager-gnome 1.8.4-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 11:38:58 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  IpRoute:
   default via 192.168.50.253 dev vlan757 proto static metric 400 
   169.254.0.0/16 dev vlan757 scope link metric 1000 
   192.168.50.0/24 dev vlan757 proto kernel scope link src 192.168.50.222 
metric 400
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager-applet
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE   STATE
  ACTIVE-PATH SLAVE 
   VLAN Camera 1a430a37-b4b3-461c-87bd-d60b547dd369  vlan
1508438283  Thu 19 Oct 2017 11:38:03 AM PDT  yes  0 
no/org/freedesktop/NetworkManager/Settings/4  yes vlan757  
activated  /org/freedesktop/NetworkManager/ActiveConnection/8  --
   Wired connection 1  23ca82a4-d9c5-3d59-ac84-56db17873201  802-3-ethernet  
1508433170  Thu 19 Oct 2017 10:12:50 AM PDT  no   4294966297
no/org/freedesktop/NetworkManager/Settings/1  no  --   --   
  --

[Desktop-packages] [Bug 1724921] [NEW] VLANs get incorrectly listed under Bluetooth

2017-10-19 Thread Scott Palmer 
Public bug reported:

I expected them to show up under Wired because the VLANs' associated
adapter is wired.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: network-manager-gnome 1.8.4-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 19 11:25:17 2017
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2017-10-19 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
IpRoute:
 default via 192.168.50.253 dev vlan757 proto static metric 400 
 169.254.0.0/16 dev vlan757 scope link metric 1000 
 192.168.50.0/24 dev vlan757 proto kernel scope link src 192.168.50.222 metric 
400
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
SourcePackage: network-manager-applet
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con:
 NAMEUUID  TYPE
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE   STATE
  ACTIVE-PATH SLAVE 
 VLAN Camera 1a430a37-b4b3-461c-87bd-d60b547dd369  vlan
1508437383  Thu 19 Oct 2017 11:23:03 AM PDT  yes  0 
no/org/freedesktop/NetworkManager/Settings/4  yes vlan757  
activated  /org/freedesktop/NetworkManager/ActiveConnection/8  --
 Wired connection 1  23ca82a4-d9c5-3d59-ac84-56db17873201  802-3-ethernet  
1508433170  Thu 19 Oct 2017 10:12:50 AM PDT  no   4294966297
no/org/freedesktop/NetworkManager/Settings/1  no  --   --   
  --  --
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled

** Affects: network-manager-applet (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful

** Attachment added: "Screenshot from 2017-10-19 11-18-44.png"
   
https://bugs.launchpad.net/bugs/1724921/+attachment/4976422/+files/Screenshot%20from%202017-10-19%2011-18-44.png

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

Title:
  VLANs get incorrectly listed under Bluetooth

Status in network-manager-applet package in Ubuntu:
  New

Bug description:
  I expected them to show up under Wired because the VLANs' associated
  adapter is wired.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager-gnome 1.8.4-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 11:25:17 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  IpRoute:
   default via 192.168.50.253 dev vlan757 proto static metric 400 
   169.254.0.0/16 dev vlan757 scope link metric 1000 
   192.168.50.0/24 dev vlan757 proto kernel scope link src 192.168.50.222 
metric 400
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager-applet
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE   STATE
  ACTIVE-PATH SLAVE 
   VLAN Camera 1a430a37-b4b3-461c-87bd-d60b547dd369  vlan
1508437383  Thu 19 Oct 2017 11:23:03 AM PDT  yes  0 
no/org/freedesktop/NetworkManager/Settings/4  yes vlan757  
activated  /org/freedesktop/NetworkManager/ActiveConnection/8  --
   Wired connection 1  23ca82a4-d9c5-3d59-ac84-56db17873201  802-3-ethernet  
1508433170  Thu 19 Oct 2017 10:12:50 AM PDT  no   4294966297
no/org/freedesktop/NetworkManager/Settings/1  no  --   --   
  --  --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled

[Desktop-packages] [Bug 1724923] [NEW] VLANs are not always listed in Settings - Network

2017-10-19 Thread Scott Palmer 
Public bug reported:

Sometimes when I open Settings - Network I see my VLANs, sometimes I
don't.  I don't think changes made in nm-connection-editor are being
properly recognized by Gnome.

I use nm-connection-editor to add and configure VLANs.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: network-manager-gnome 1.8.4-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 19 11:33:19 2017
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2017-10-19 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
IpRoute:
 default via 192.168.50.253 dev vlan757 proto static metric 400 
 169.254.0.0/16 dev vlan757 scope link metric 1000 
 192.168.50.0/24 dev vlan757 proto kernel scope link src 192.168.50.222 metric 
400
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
SourcePackage: network-manager-applet
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con:
 NAMEUUID  TYPE
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE   STATE
  ACTIVE-PATH SLAVE 
 VLAN Camera 1a430a37-b4b3-461c-87bd-d60b547dd369  vlan
1508437983  Thu 19 Oct 2017 11:33:03 AM PDT  yes  0 
no/org/freedesktop/NetworkManager/Settings/4  yes vlan757  
activated  /org/freedesktop/NetworkManager/ActiveConnection/8  --
 Wired connection 1  23ca82a4-d9c5-3d59-ac84-56db17873201  802-3-ethernet  
1508433170  Thu 19 Oct 2017 10:12:50 AM PDT  no   4294966297
no/org/freedesktop/NetworkManager/Settings/1  no  --   --   
  --  --
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled

** Affects: network-manager-applet (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful wayland-session

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

Title:
  VLANs are not always listed in Settings - Network

Status in network-manager-applet package in Ubuntu:
  New

Bug description:
  Sometimes when I open Settings - Network I see my VLANs, sometimes I
  don't.  I don't think changes made in nm-connection-editor are being
  properly recognized by Gnome.

  I use nm-connection-editor to add and configure VLANs.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager-gnome 1.8.4-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 11:33:19 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  IpRoute:
   default via 192.168.50.253 dev vlan757 proto static metric 400 
   169.254.0.0/16 dev vlan757 scope link metric 1000 
   192.168.50.0/24 dev vlan757 proto kernel scope link src 192.168.50.222 
metric 400
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager-applet
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE   STATE
  ACTIVE-PATH SLAVE 
   VLAN Camera 1a430a37-b4b3-461c-87bd-d60b547dd369  vlan
1508437983  Thu 19 Oct 2017 11:33:03 AM PDT  yes  0 
no/org/freedesktop/NetworkManager/Settings/4  yes vlan757  
activated  /org/freedesktop/NetworkManager/ActiveConnection/8  --
   Wired connection 1  23ca82a4-d9c5-3d59-ac84-56db17873201  802-3-ethernet  
1508433170  Thu 19 Oct 2017 10:12:50 AM PDT  no   4294966297
no/org/freedesktop/NetworkManager/Settings/1  no  --   --   
  --  --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI

[Desktop-packages] [Bug 1724442] [NEW] Search feature returns seemingly unrelated results

2017-10-17 Thread Scott Palmer 
Public bug reported:

This bug should actually be linked to ubuntu software, not gnome
software.


Search for "libre"

1. yacas 
2. wormhole
.
.
.

I can't even find "libre" in the package name, nor the description of
the first few pages of results.

Way down on the list is "libreoffice" but even it isn't grouped with
"LibreOffice Writer", "LibreOffice Calc" which are several pages lower.

What is the order of results?

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: ubuntu-software 3.26.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 17 21:10:29 2017
InstallationDate: Installed on 2017-10-03 (14 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
InstalledPlugins:
 gnome-software-plugin-flatpak N/A
 gnome-software-plugin-limba   N/A
 gnome-software-plugin-snap3.26.1-0ubuntu1
PackageArchitecture: all
SourcePackage: gnome-software
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-software (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful wayland-session

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

Title:
  Search feature returns seemingly unrelated results

Status in gnome-software package in Ubuntu:
  New

Bug description:
  This bug should actually be linked to ubuntu software, not gnome
  software.

  
  Search for "libre"

  1. yacas 
  2. wormhole
  .
  .
  .

  I can't even find "libre" in the package name, nor the description of
  the first few pages of results.

  Way down on the list is "libreoffice" but even it isn't grouped with
  "LibreOffice Writer", "LibreOffice Calc" which are several pages
  lower.

  What is the order of results?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ubuntu-software 3.26.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 17 21:10:29 2017
  InstallationDate: Installed on 2017-10-03 (14 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.26.1-0ubuntu1
  PackageArchitecture: all
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1724442/+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 1723824] [NEW] Unable to scroll down to all photos

2017-10-15 Thread Scott Palmer 
Public bug reported:

Shotwell would not let my scroll down any further to select some photoss
on the bottom row.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: shotwell 0.26.3-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct 15 17:54:26 2017
InstallationDate: Installed on 2017-10-03 (12 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
SourcePackage: shotwell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug artful wayland-session

** Attachment added: "Notice the scrollbar is all the way down and there are 
still photos below"
   
https://bugs.launchpad.net/bugs/1723824/+attachment/4972338/+files/cannot_scroll_down.png

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

Title:
  Unable to scroll down to all photos

Status in shotwell package in Ubuntu:
  New

Bug description:
  Shotwell would not let my scroll down any further to select some
  photoss on the bottom row.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: shotwell 0.26.3-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 15 17:54:26 2017
  InstallationDate: Installed on 2017-10-03 (12 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: shotwell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1723824/+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 1723815] [NEW] Unable to show files on MTP connection

2017-10-15 Thread Scott Palmer 
Public bug reported:

Opening "Samsung_Android\Card\DCIM\Camera" folder with many images gets
stuck at "Loading..." and never shows anything.  I have waited 10
minutes.  There is no error and not a single icon shows.

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
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct 15 16:36:50 2017
InstallationDate: Installed on 2017-10-03 (12 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug artful wayland-session

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

Title:
  Unable to show files on MTP connection

Status in nautilus package in Ubuntu:
  New

Bug description:
  Opening "Samsung_Android\Card\DCIM\Camera" folder with many images
  gets stuck at "Loading..." and never shows anything.  I have waited 10
  minutes.  There is no error and not a single icon shows.

  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
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 15 16:36:50 2017
  InstallationDate: Installed on 2017-10-03 (12 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  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/1723815/+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 1722987] [NEW] screen brightness control is backwards

2017-10-11 Thread Scott Palmer 
Public bug reported:

Increase brightness key on my keyboard (func-f3) makes the screen more dim.
Decrease brightness key on my keyboard (func-f2) makes the screen more bright.
The gnome-shell on-screen display of brightness is backwards also.

I see on google search results that this was a problem with older
kernels. I guess the problem is back / possible regression.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
Uname: Linux 4.13.0-15-generic x86_64
ApportVersion: 2.20.7-0ubuntu2
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 11 20:52:44 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Atom Processor Z36xxx/Z37xxx Series 
Graphics & Display [103c:2209]
InstallationDate: Installed on 2017-10-08 (3 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 005: ID 0cf3:3121 Atheros Communications, Inc. 
 Bus 001 Device 003: ID 1a40:0101 Terminus Technology Inc. Hub
 Bus 001 Device 002: ID 05c8:036e Cheng Uei Precision Industry Co., Ltd 
(Foxlink) Webcam
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Hewlett-Packard HP Pavilion 11 x360 PC
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-15-generic.efi.signed 
root=UUID=3db6d4f1-3d95-4b8c-93d1-ab9465947670 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/11/2014
dmi.bios.vendor: Insyde
dmi.bios.version: F.15
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 2209
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 57.37
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.15:bd11/11/2014:svnHewlett-Packard:pnHPPavilion11x360PC:pvr096F100800405F00010420180:rvnHewlett-Packard:rn2209:rvr57.37:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=MIN
dmi.product.name: HP Pavilion 11 x360 PC
dmi.product.version: 096F100800405F00010420180
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug artful ubuntu wayland-session

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

Title:
  screen brightness control is backwards

Status in xorg package in Ubuntu:
  New

Bug description:
  Increase brightness key on my keyboard (func-f3) makes the screen more dim.
  Decrease brightness key on my keyboard (func-f2) makes the screen more bright.
  The gnome-shell on-screen display of brightness is backwards also.

  I see on google search results that this was a problem with older
  kernels. I guess the problem is back / possible regression.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 11 20:52:44 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Atom Processor Z36xxx/Z37xxx Series 
Graphics & Display [103c:2209]
  InstallationDate: Installed on 2017-10-08 (3 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 0cf3:3121 Atheros Communications, Inc. 
   Bus 001 Device 003: ID 1a40:0101 Terminus Technology Inc. Hub
   Bus 001 Device 002: ID 05c8:036e Cheng Uei Precision Industry Co., Ltd 
(Foxlink) Webcam
   Bus 001 Device

[Desktop-packages] [Bug 1711037] Re: Screen intermittently flickers

2017-10-08 Thread Scott Palmer 
These seems to be related to what is in monitors.xml.
When I deleted that file the flickering was gone but my monitors were out of 
order and alignment.

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

Title:
  Screen intermittently flickers

Status in xorg package in Ubuntu:
  New

Bug description:
  Using both my nvidia and radeon cards my 2560x1600 display flickers.
  The screen is fine in Windows.  This only seems to happen when I run
  the open source driver.

  Additionally, if I drop that screen to a lower 16:10 resolution like
  1920x1200 it goes black.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
  Uname: Linux 4.11.0-13-generic x86_64
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Tue Aug 15 22:32:41 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.11.0-10-generic, x86_64: installed
   bbswitch, 0.8, 4.11.0-13-generic, x86_64: installed
   nvidia-384, 384.59, 4.11.0-10-generic, x86_64: installed
   nvidia-384, 384.59, 4.11.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Polaris11] [1002:67ff] (rev 
cf) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Baffin [Polaris11] 
[1462:8a91]
  InstallationDate: Installed on 2017-08-07 (9 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170805)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-13-generic 
root=UUID=adb3a033-d515-4dfb-97d6-7c0ef12879cf ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1807
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P7P55D DELUXE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1807:bd07/22/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55DDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.82-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.1.4-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.1.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Mon Aug 14 07:40:51 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.3-1ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1711037/+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 1721160] Re: [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at all

2017-10-08 Thread Scott Palmer 
Some updates must have come in, in the last few days that fixed this.
Close the bug.

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

Title:
  [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at
  all

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  If I unplug the green plug to my speakers after my computer finishes
  booting and then immediately plug it back in again, sound works
  correctly.

  Prior to the unplug / replug trick the Line-out is missing from Sound 
settings.
  After the unplug / replug trick the Line-out is correctly listed in Sound 
settings.

  I will attach screenshots.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  scott  1272 F pulseaudio
   /dev/snd/controlC1:  scott  1272 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  3 17:21:49 2017
  InstallationDate: Installed on 2017-10-03 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful
  Symptom_Card: Built-in Audio - HDA Intel MID
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm 926 F pulseaudio
scott  1272 F pulseaudio
   /dev/snd/controlC1:  gdm 926 F pulseaudio
scott  1272 F pulseaudio
  Symptom_Jack: Green Line Out, Rear
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1807
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P7P55D DELUXE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1807:bd07/22/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55DDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1721160/+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 1721674] [NEW] Scan All Pages From Feeder action scans the first page and feeds the rest without scanning

2017-10-05 Thread Scott Palmer 
Public bug reported:

"Scan All Pages From Feeder" action scans the first page and feeds the
rest without scanning them.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: simple-scan 3.26.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct  5 18:31:19 2017
InstallationDate: Installed on 2017-10-03 (2 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic 
root=UUID=a393d6b9-0886-4a0a-b2be-5111bfcf9ada ro quiet splash
SimpleScanLog:
 
SourcePackage: simple-scan
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/22/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1807
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P7P55D DELUXE
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1807:bd07/22/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55DDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

** Affects: simple-scan (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful wayland-session

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

Title:
  Scan All Pages From Feeder action scans the first page and feeds the
  rest without scanning

Status in simple-scan package in Ubuntu:
  New

Bug description:
  "Scan All Pages From Feeder" action scans the first page and feeds the
  rest without scanning them.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: simple-scan 3.26.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct  5 18:31:19 2017
  InstallationDate: Installed on 2017-10-03 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic 
root=UUID=a393d6b9-0886-4a0a-b2be-5111bfcf9ada ro quiet splash
  SimpleScanLog:
   
  SourcePackage: simple-scan
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1807
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P7P55D DELUXE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1807:bd07/22/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55DDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1721674/+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 1721430] Re: connection missing in gui when created using nmcli

2017-10-04 Thread Scott Palmer 
** Attachment added: "Screenshot from 2017-10-04 19-45-09.png"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1721430/+attachment/4962439/+files/Screenshot%20from%202017-10-04%2019-45-09.png

** Description changed:

- When I create a new connection using `sudo nmcli` the entry is missing
- in Network settings but exists in the popup.  Also the name used to
- create the connection is not displayed.  (see screenshots attached)
+ When I create a new connection using nmcli the entry is missing in
+ Network settings but exists in the popup.  Also the name used to create
+ the connection is not displayed.  (see screenshots attached)
  
  The commands used to create the connection are basically:
  
- VPN_NAME="Sample VPN"
- VPN_REMOTE="somewhere.inter.net"
- VPN_USERNAME="somebody"
- VPN_CA="/home/$TARGET_USER/.config/ca-sample.crt"
- nmcli con add type vpn ifname -- con-name "\"$VPN_NAME\"" vpn-type 
openvpn 
- nmcli con mod "\"$VPN_NAME\"" connection.autoconnect yes
- nmcli con mod "\"$VPN_NAME\"" connection.permissions "user:$TARGET_USER"
- nmcli con mod "\"$VPN_NAME\"" vpn.data "port = 1195, proto-tcp = yes, ca 
= $VPN_CA, password-flags = 1, connection-type = password, remote = 
$VPN_REMOTE, username = $VPN_USERNAME"
- nmcli con mod "\"$VPN_NAME\"" +ipv4.routes "192.168.50.0/24 0.0.0.0"
- nmcli con mod "\"$VPN_NAME\"" +ipv4.routes "192.168.51.0/24 0.0.0.0"
- nmcli con mod "\"$VPN_NAME\"" ipv4.never-default yes
+ VPN_NAME="Sample VPN"
+ VPN_REMOTE="somewhere.inter.net"
+ VPN_USERNAME="somebody"
+ VPN_CA="/home/$TARGET_USER/.config/ca-sample.crt"
+ nmcli con add type vpn ifname -- con-name "\"$VPN_NAME\"" vpn-type openvpn
+ nmcli con mod "\"$VPN_NAME\"" connection.autoconnect yes
+ nmcli con mod "\"$VPN_NAME\"" connection.permissions "user:$TARGET_USER"
+ nmcli con mod "\"$VPN_NAME\"" vpn.data "port = 1195, proto-tcp = yes, ca 
= $VPN_CA, password-flags = 1, connection-type = password, remote = 
$VPN_REMOTE, username = $VPN_USERNAME"
+ nmcli con mod "\"$VPN_NAME\"" +ipv4.routes "192.168.50.0/24 0.0.0.0"
+ nmcli con mod "\"$VPN_NAME\"" +ipv4.routes "192.168.51.0/24 0.0.0.0"
+ nmcli con mod "\"$VPN_NAME\"" ipv4.never-default yes
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager-openvpn-gnome 1.2.10-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct  4 19:40:41 2017
  InstallationDate: Installed on 2017-10-03 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: network-manager-openvpn
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  connection missing in gui when created using nmcli

Status in network-manager-openvpn package in Ubuntu:
  New

Bug description:
  When I create a new connection using nmcli the entry is missing in
  Network settings but exists in the popup.  Also the name used to
  create the connection is not displayed.  (see screenshots attached)

  The commands used to create the connection are basically:

  VPN_NAME="Sample VPN"
  VPN_REMOTE="somewhere.inter.net"
  VPN_USERNAME="somebody"
  VPN_CA="/home/$TARGET_USER/.config/ca-sample.crt"
  nmcli con add type vpn ifname -- con-name "\"$VPN_NAME\"" vpn-type openvpn
  nmcli con mod "\"$VPN_NAME\"" connection.autoconnect yes
  nmcli con mod "\"$VPN_NAME\"" connection.permissions "user:$TARGET_USER"
  nmcli con mod "\"$VPN_NAME\"" vpn.data "port = 1195, proto-tcp = yes, ca 
= $VPN_CA, password-flags = 1, connection-type = password, remote = 
$VPN_REMOTE, username = $VPN_USERNAME"
  nmcli con mod "\"$VPN_NAME\"" +ipv4.routes "192.168.50.0/24 0.0.0.0"
  nmcli con mod "\"$VPN_NAME\"" +ipv4.routes "192.168.51.0/24 0.0.0.0"
  nmcli con mod "\"$VPN_NAME\"" ipv4.never-default yes

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager-openvpn-gnome 1.2.10-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct  4 19:40:41 2017
  InstallationDate: Installed on 2017-10-03 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: network-manager-openvpn
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1721430/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to :

[Desktop-packages] [Bug 1721430] [NEW] connection missing in gui when created using nmcli

2017-10-04 Thread Scott Palmer 
Public bug reported:

When I create a new connection using nmcli the entry is missing in
Network settings but exists in the popup.  Also the name used to create
the connection is not displayed.  (see screenshots attached)

The commands used to create the connection are basically:

VPN_NAME="Sample VPN"
VPN_REMOTE="somewhere.inter.net"
VPN_USERNAME="somebody"
VPN_CA="/home/$TARGET_USER/.config/ca-sample.crt"
nmcli con add type vpn ifname -- con-name "\"$VPN_NAME\"" vpn-type openvpn
nmcli con mod "\"$VPN_NAME\"" connection.autoconnect yes
nmcli con mod "\"$VPN_NAME\"" connection.permissions "user:$TARGET_USER"
nmcli con mod "\"$VPN_NAME\"" vpn.data "port = 1195, proto-tcp = yes, ca = 
$VPN_CA, password-flags = 1, connection-type = password, remote = $VPN_REMOTE, 
username = $VPN_USERNAME"
nmcli con mod "\"$VPN_NAME\"" +ipv4.routes "192.168.50.0/24 0.0.0.0"
nmcli con mod "\"$VPN_NAME\"" +ipv4.routes "192.168.51.0/24 0.0.0.0"
nmcli con mod "\"$VPN_NAME\"" ipv4.never-default yes

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: network-manager-openvpn-gnome 1.2.10-0ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct  4 19:40:41 2017
InstallationDate: Installed on 2017-10-03 (1 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
SourcePackage: network-manager-openvpn
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: network-manager-openvpn (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful wayland-session

** Attachment added: "Screenshot from 2017-10-04 19-43-35.png"
   
https://bugs.launchpad.net/bugs/1721430/+attachment/4962434/+files/Screenshot%20from%202017-10-04%2019-43-35.png

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

Title:
  connection missing in gui when created using nmcli

Status in network-manager-openvpn package in Ubuntu:
  New

Bug description:
  When I create a new connection using nmcli the entry is missing in
  Network settings but exists in the popup.  Also the name used to
  create the connection is not displayed.  (see screenshots attached)

  The commands used to create the connection are basically:

  VPN_NAME="Sample VPN"
  VPN_REMOTE="somewhere.inter.net"
  VPN_USERNAME="somebody"
  VPN_CA="/home/$TARGET_USER/.config/ca-sample.crt"
  nmcli con add type vpn ifname -- con-name "\"$VPN_NAME\"" vpn-type openvpn
  nmcli con mod "\"$VPN_NAME\"" connection.autoconnect yes
  nmcli con mod "\"$VPN_NAME\"" connection.permissions "user:$TARGET_USER"
  nmcli con mod "\"$VPN_NAME\"" vpn.data "port = 1195, proto-tcp = yes, ca 
= $VPN_CA, password-flags = 1, connection-type = password, remote = 
$VPN_REMOTE, username = $VPN_USERNAME"
  nmcli con mod "\"$VPN_NAME\"" +ipv4.routes "192.168.50.0/24 0.0.0.0"
  nmcli con mod "\"$VPN_NAME\"" +ipv4.routes "192.168.51.0/24 0.0.0.0"
  nmcli con mod "\"$VPN_NAME\"" ipv4.never-default yes

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager-openvpn-gnome 1.2.10-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct  4 19:40:41 2017
  InstallationDate: Installed on 2017-10-03 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: network-manager-openvpn
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1721430/+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 1721160] Re: [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at all

2017-10-03 Thread Scott Palmer 
** Attachment added: "Screenshot from 2017-10-03 17-18-29.png"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1721160/+attachment/4961790/+files/Screenshot%20from%202017-10-03%2017-18-29.png

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

Title:
  [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at
  all

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  If I unplug the green plug to my speakers after my computer finishes
  booting and then immediately plug it back in again, sound works
  correctly.

  Prior to the unplug / replug trick the Line-out is missing from Sound 
settings.
  After the unplug / replug trick the Line-out is correctly listed in Sound 
settings.

  I will attach screenshots.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  scott  1272 F pulseaudio
   /dev/snd/controlC1:  scott  1272 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  3 17:21:49 2017
  InstallationDate: Installed on 2017-10-03 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful
  Symptom_Card: Built-in Audio - HDA Intel MID
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm 926 F pulseaudio
scott  1272 F pulseaudio
   /dev/snd/controlC1:  gdm 926 F pulseaudio
scott  1272 F pulseaudio
  Symptom_Jack: Green Line Out, Rear
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1807
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P7P55D DELUXE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1807:bd07/22/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55DDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1721160/+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 1721160] [NEW] [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at all

2017-10-03 Thread Scott Palmer 
Public bug reported:

If I unplug the green plug to my speakers after my computer finishes
booting and then immediately plug it back in again, sound works
correctly.

Prior to the unplug / replug trick the Line-out is missing from Sound settings.
After the unplug / replug trick the Line-out is correctly listed in Sound 
settings.

I will attach screenshots.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: pulseaudio 1:10.0-2ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  scott  1272 F pulseaudio
 /dev/snd/controlC1:  scott  1272 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct  3 17:21:49 2017
InstallationDate: Installed on 2017-10-03 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
SourcePackage: pulseaudio
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful
Symptom_Card: Built-in Audio - HDA Intel MID
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gdm 926 F pulseaudio
  scott  1272 F pulseaudio
 /dev/snd/controlC1:  gdm 926 F pulseaudio
  scott  1272 F pulseaudio
Symptom_Jack: Green Line Out, Rear
Symptom_PulsePlaybackTest: PulseAudio playback test failed
Symptom_Type: No sound at all
Title: [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/22/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1807
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P7P55D DELUXE
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1807:bd07/22/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55DDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-bug artful wayland-session

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

Title:
  [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at
  all

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  If I unplug the green plug to my speakers after my computer finishes
  booting and then immediately plug it back in again, sound works
  correctly.

  Prior to the unplug / replug trick the Line-out is missing from Sound 
settings.
  After the unplug / replug trick the Line-out is correctly listed in Sound 
settings.

  I will attach screenshots.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  scott  1272 F pulseaudio
   /dev/snd/controlC1:  scott  1272 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  3 17:21:49 2017
  InstallationDate: Installed on 2017-10-03 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful
  Symptom_Card: Built-in Audio - HDA Intel MID
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm 926 F pulseaudio
scott  1272 F pulseaudio
   /dev/snd/controlC1:  gdm 926 F pulseaudio
scott  1272 F pulseaudio
  Symptom_Jack: Green Line Out, Rear
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1807
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P7P55D DELUXE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias:

[Desktop-packages] [Bug 1721160] Re: [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at all

2017-10-03 Thread Scott Palmer 
** Attachment added: "Screenshot from 2017-10-03 17-18-43.png"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1721160/+attachment/4961791/+files/Screenshot%20from%202017-10-03%2017-18-43.png

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

Title:
  [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at
  all

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  If I unplug the green plug to my speakers after my computer finishes
  booting and then immediately plug it back in again, sound works
  correctly.

  Prior to the unplug / replug trick the Line-out is missing from Sound 
settings.
  After the unplug / replug trick the Line-out is correctly listed in Sound 
settings.

  I will attach screenshots.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  scott  1272 F pulseaudio
   /dev/snd/controlC1:  scott  1272 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  3 17:21:49 2017
  InstallationDate: Installed on 2017-10-03 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful
  Symptom_Card: Built-in Audio - HDA Intel MID
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm 926 F pulseaudio
scott  1272 F pulseaudio
   /dev/snd/controlC1:  gdm 926 F pulseaudio
scott  1272 F pulseaudio
  Symptom_Jack: Green Line Out, Rear
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1807
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P7P55D DELUXE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1807:bd07/22/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55DDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1721160/+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 1711037] [NEW] Screen intermittently flickers

2017-08-15 Thread Scott Palmer 
Public bug reported:

Using both my nvidia and radeon cards my 2560x1600 display flickers.
The screen is fine in Windows.  This only seems to happen when I run the
open source driver.

Additionally, if I drop that screen to a lower 16:10 resolution like
1920x1200 it goes black.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu1
ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
Uname: Linux 4.11.0-13-generic x86_64
ApportVersion: 2.20.6-0ubuntu5
Architecture: amd64
CompositorRunning: None
CurrentDesktop: GNOME
Date: Tue Aug 15 22:32:41 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.11.0-10-generic, x86_64: installed
 bbswitch, 0.8, 4.11.0-13-generic, x86_64: installed
 nvidia-384, 384.59, 4.11.0-10-generic, x86_64: installed
 nvidia-384, 384.59, 4.11.0-13-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Polaris11] [1002:67ff] (rev cf) 
(prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] Baffin [Polaris11] 
[1462:8a91]
InstallationDate: Installed on 2017-08-07 (9 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170805)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-13-generic 
root=UUID=adb3a033-d515-4dfb-97d6-7c0ef12879cf ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/22/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1807
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P7P55D DELUXE
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1807:bd07/22/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55DDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.82-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.1.4-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.1.4-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Mon Aug 14 07:40:51 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.19.3-1ubuntu2

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


** Tags: amd64 apport-bug artful reproducible ubuntu wayland-session

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

Title:
  Screen intermittently flickers

Status in xorg package in Ubuntu:
  New

Bug description:
  Using both my nvidia and radeon cards my 2560x1600 display flickers.
  The screen is fine in Windows.  This only seems to happen when I run
  the open source driver.

  Additionally, if I drop that screen to a lower 16:10 resolution like
  1920x1200 it goes black.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
  Uname: Linux 4.11.0-13-generic x86_64
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Tue Aug 15 22:32:41 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.11.0-10-generic, x86_64: installed
   bbswitch, 0.8, 4.11.0-13-generic, x86_64: installed
   nvidia-384, 384.59, 4.11.0-10-generic, x86_64: installed
   nvidia-384, 384.59, 4.11.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Polaris11] [1002:67ff] (rev 
cf) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Baffin [Polaris11] 
[1462:8a91]
  InstallationDate: Installed on 2017-08-07 (9 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170805)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-13-generic 
root=UUID=adb3a033-d515-4dfb-97d6-7c0ef12879cf ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom:

[Desktop-packages] [Bug 1710754] [NEW] [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at all

2017-08-14 Thread Scott Palmer 
Public bug reported:

When I start my computer I have no sound.  If I unplug my line out and
plug it in again sound works fine. In Windows 10 this unplug and replug
is not required (the jack is fine).

Running:
 $ amixer -c0 contents
so I can compare the non working state with the working state, the following 
differences exist:

Non Working:
numid=43,iface=CARD,name='Line Out Front Jack'
  ; type=BOOLEAN,access=r---,values=1
  : values=off
numid=35,iface=MIXER,name='IEC958 Playback Switch'
  ; type=BOOLEAN,access=rw--,values=1
  : values=on

Working:
numid=43,iface=CARD,name='Line Out Front Jack'
  ; type=BOOLEAN,access=r---,values=1
  : values=on
numid=35,iface=MIXER,name='IEC958 Playback Switch'
  ; type=BOOLEAN,access=rw--,values=1
  : values=off

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
Uname: Linux 4.11.0-13-generic x86_64
ApportVersion: 2.20.6-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  scott  1154 F pulseaudio
 /dev/snd/controlC1:  scott  1154 F pulseaudio
CurrentDesktop: GNOME
Date: Mon Aug 14 19:05:12 2017
InstallationDate: Installed on 2017-08-07 (8 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170805)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful
Symptom_Card: Built-in Audio - HDA Intel MID
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  scott  1154 F pulseaudio
 /dev/snd/controlC1:  scott  1154 F pulseaudio
Symptom_Jack: Green Line Out, Rear
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: No sound at all
Title: [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/22/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1807
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P7P55D DELUXE
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1807:bd07/22/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55DDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful wayland-session

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

Title:
  [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at
  all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  When I start my computer I have no sound.  If I unplug my line out and
  plug it in again sound works fine. In Windows 10 this unplug and
  replug is not required (the jack is fine).

  Running:
   $ amixer -c0 contents
  so I can compare the non working state with the working state, the following 
differences exist:

  Non Working:
  numid=43,iface=CARD,name='Line Out Front Jack'
; type=BOOLEAN,access=r---,values=1
: values=off
  numid=35,iface=MIXER,name='IEC958 Playback Switch'
; type=BOOLEAN,access=rw--,values=1
: values=on

  Working:
  numid=43,iface=CARD,name='Line Out Front Jack'
; type=BOOLEAN,access=r---,values=1
: values=on
  numid=35,iface=MIXER,name='IEC958 Playback Switch'
; type=BOOLEAN,access=rw--,values=1
: values=off

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
  Uname: Linux 4.11.0-13-generic x86_64
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  scott  1154 F pulseaudio
   /dev/snd/controlC1:  scott  1154 F pulseaudio
  CurrentDesktop: GNOME
  Date: Mon Aug 14 19:05:12 2017
  InstallationDate: Installed on 2017-08-07 (8 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful
  Symptom_Card: Built-in Audio - HDA Intel MID
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  scott  1154 F pulseaudio
   /dev/snd/controlC1:  scott  1154 F pulseaudio
  Symptom_Jack: Green Line Out, Rear
  Symptom_PulsePlaybackTest: PulseAudio playback test

[Desktop-packages] [Bug 1710752] [NEW] Intel HDA Audio doesn't work

2017-08-14 Thread Scott Palmer 
Public bug reported:

I get no sound on most boots.  In Sound settings the default Output device is 
HDMI / DisplayPort -
 Built-in Audio and there is no option to select anything else.  If I unplug my 
line out and plug it in again it shows up in the list, automatically sets 
itself as default and sound works fine. In Windows 10 this unplug and replug is 
not required (the jack is fine).

Running:
 $ amixer -c0 contents
so I can compare the non working state with the working state, the following 
differences exist:

Non Working:
numid=43,iface=CARD,name='Line Out Front Jack'
  ; type=BOOLEAN,access=r---,values=1
  : values=off
numid=35,iface=MIXER,name='IEC958 Playback Switch'
  ; type=BOOLEAN,access=rw--,values=1
  : values=on

Working:
numid=43,iface=CARD,name='Line Out Front Jack'
  ; type=BOOLEAN,access=r---,values=1
  : values=on
numid=35,iface=MIXER,name='IEC958 Playback Switch'
  ; type=BOOLEAN,access=rw--,values=1
  : values=off

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Intel HDA Audio doesn't work

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I get no sound on most boots.  In Sound settings the default Output device is 
HDMI / DisplayPort -
   Built-in Audio and there is no option to select anything else.  If I unplug 
my line out and plug it in again it shows up in the list, automatically sets 
itself as default and sound works fine. In Windows 10 this unplug and replug is 
not required (the jack is fine).

  Running:
   $ amixer -c0 contents
  so I can compare the non working state with the working state, the following 
differences exist:

  Non Working:
  numid=43,iface=CARD,name='Line Out Front Jack'
; type=BOOLEAN,access=r---,values=1
: values=off
  numid=35,iface=MIXER,name='IEC958 Playback Switch'
; type=BOOLEAN,access=rw--,values=1
: values=on

  Working:
  numid=43,iface=CARD,name='Line Out Front Jack'
; type=BOOLEAN,access=r---,values=1
: values=on
  numid=35,iface=MIXER,name='IEC958 Playback Switch'
; type=BOOLEAN,access=rw--,values=1
: values=off

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1710752/+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 1709159] Re: Mouse cursor stuck on primary monitor on dual monitor system

2017-08-14 Thread Scott Palmer 
I just changed my video card to a Radeon RX 560 using the open source
driver and the same problem exists.

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

Title:
  Mouse cursor stuck on primary monitor on dual monitor system

Status in gnome-session package in Ubuntu:
  New

Bug description:
  I am running a Wayland session with Nouveau drivers on an NVIDIA GeForce GTS 
450.
  I have a dual monitor setup with my primary on the right.
  My primary display is slightly higher than my secondary on the left as 
configured in Displays.

  When I play a video full screen on the left monitor and then bring my
  mouse cursor back to my primary on the right, the mouse cursor often
  refuses to go back onto the left monitor (as if I only had one
  monitor).  Once I switch to overview mode, it will let the mouse go
  back over to the left monitor again.  The mouse will continue working
  across both monitors now.

  I go back into the video and toggle out of full screen and then back
  to full screen and bring my mouse back over to the right monitor.  It
  is now stuck on the right monitor again.

  So..  activation of full screen on the left secondary monitor and then
  moving the mouse cursor onto the right primary is enough to reproduce
  the bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-session-wayland (not installed)
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Aug  7 12:02:43 2017
  InstallationDate: Installed on 2017-08-07 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170805)
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1709159/+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 1628153] Re: [W65_67SF, VIA VT1802, Speaker, Internal] No sound at all on most restarts

2017-08-13 Thread Scott Palmer 
I am getting similar behaviour on 17.10.  If I unplug my line out and
plug it in again it works fine.  In Windows 10 this unplug and replug is
not required (the jack is fine).


Running:
 $ amixer -c0 contents
so I can compare the non working state with the working state, the following 
differences exist:


Non Working:
numid=43,iface=CARD,name='Line Out Front Jack'
  ; type=BOOLEAN,access=r---,values=1
  : values=off
numid=35,iface=MIXER,name='IEC958 Playback Switch'
  ; type=BOOLEAN,access=rw--,values=1
  : values=on


Working:
numid=43,iface=CARD,name='Line Out Front Jack'
  ; type=BOOLEAN,access=r---,values=1
  : values=on
numid=35,iface=MIXER,name='IEC958 Playback Switch'
  ; type=BOOLEAN,access=rw--,values=1
  : values=off

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

Title:
  [W65_67SF, VIA VT1802, Speaker, Internal] No sound at all on most
  restarts

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On the vast majority of restarts of Ubuntu 16.04 I get no internal
  sound at all.

  There are no reported issues in system settings on the only sound card
  I have. The volume is not muted.

  On an estimated 1 in 10 restart, the sound works, and both the test
  sounds get played and other applications work fine.

  There is no reported errors or messages on the restarts when the sound
  has failed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   tony  16160 F...m pulseaudio
   /dev/snd/controlC1:  tony  16160 F pulseaudio
   /dev/snd/controlC0:  tony  16160 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Sep 27 15:56:02 2016
  InstallationDate: Installed on 2015-10-29 (334 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   tony  16160 F...m pulseaudio
   /dev/snd/controlC1:  tony  16160 F pulseaudio
   /dev/snd/controlC0:  tony  16160 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [W65_67SF, VIA VT1802, Speaker, Internal] No sound at all
  UpgradeStatus: Upgraded to xenial on 2016-08-13 (45 days ago)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.03.03
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W65_67SF
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.03.03:bd04/01/2014:svnNotebook:pnW65_67SF:pvrNotApplicable:rvnNotebook:rnW65_67SF:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: W65_67SF
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1628153/+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 1709159] [NEW] Mouse cursor stuck on primary monitor on dual monitor system

2017-08-07 Thread Scott Palmer 
Public bug reported:

I am running a Wayland session with Nouveau drivers on an NVIDIA GeForce GTS 
450.
I have a dual monitor setup with my primary on the right.
My primary display is slightly higher than my secondary on the left as 
configured in Displays.

When I play a video full screen on the left monitor and then bring my
mouse cursor back to my primary on the right, the mouse cursor often
refuses to go back onto the left monitor (as if I only had one monitor).
Once I switch to overview mode, it will let the mouse go back over to
the left monitor again.  The mouse will continue working across both
monitors now.

I go back into the video and toggle out of full screen and then back to
full screen and bring my mouse back over to the right monitor.  It is
now stuck on the right monitor again.

So..  activation of full screen on the left secondary monitor and then
moving the mouse cursor onto the right primary is enough to reproduce
the bug.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-session-wayland (not installed)
ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
Uname: Linux 4.11.0-10-generic x86_64
ApportVersion: 2.20.6-0ubuntu4
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Aug  7 12:02:43 2017
InstallationDate: Installed on 2017-08-07 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170805)
SourcePackage: gnome-session
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-session (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful wayland-session

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

Title:
  Mouse cursor stuck on primary monitor on dual monitor system

Status in gnome-session package in Ubuntu:
  New

Bug description:
  I am running a Wayland session with Nouveau drivers on an NVIDIA GeForce GTS 
450.
  I have a dual monitor setup with my primary on the right.
  My primary display is slightly higher than my secondary on the left as 
configured in Displays.

  When I play a video full screen on the left monitor and then bring my
  mouse cursor back to my primary on the right, the mouse cursor often
  refuses to go back onto the left monitor (as if I only had one
  monitor).  Once I switch to overview mode, it will let the mouse go
  back over to the left monitor again.  The mouse will continue working
  across both monitors now.

  I go back into the video and toggle out of full screen and then back
  to full screen and bring my mouse back over to the right monitor.  It
  is now stuck on the right monitor again.

  So..  activation of full screen on the left secondary monitor and then
  moving the mouse cursor onto the right primary is enough to reproduce
  the bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-session-wayland (not installed)
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Aug  7 12:02:43 2017
  InstallationDate: Installed on 2017-08-07 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170805)
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1709159/+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 1582496] Re: GLib-GObject-CRITICAL failures during Ubuntu 16.04 bootup

2016-09-06 Thread Mike Palmer 
** Changed in: gnome-session (Ubuntu)
 Assignee: ega (egagoodoodle) => (unassigned)

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

Title:
  GLib-GObject-CRITICAL failures during Ubuntu 16.04 bootup

Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  I submitted this question a week but did not receive an answer or
  advice to solving them. https://answers.launchpad.net/ubuntu/+source
  /gnome-session/+question/293479

  These failures are still plaguing my syslog every time I activate
  Nautilus.

  Appreciate help to resolve these failures.

  
   Earlier question 
  After a recent updating, I notice these failures in the systemlogs. 

  May  9 16:34:59 Eliot gnome-session[1562]: gnome-session-binary[1562]: 
GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
  May  9 16:34:59 Eliot gnome-session-binary[1562]: GLib-GObject-CRITICAL: 
g_object_unref: assertion 'G_IS_OBJECT (object)' failed
  May  9 16:34:59 Eliot gnome-session[1562]: gnome-session-binary[1562]: 
GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
  May  9 16:34:59 Eliot gnome-session-binary[1562]: GLib-GObject-CRITICAL: 
g_object_unref: assertion 'G_IS_OBJECT (object)' failed
  May  9 16:34:59 Eliot gnome-session[1562]: gnome-session-binary[1562]: 
GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
  May  9 16:34:59 Eliot gnome-session-binary[1562]: GLib-GObject-CRITICAL: 
g_object_unref: assertion 'G_IS_OBJECT (object)' failed
  May  9 16:34:59 Eliot gnome-session[1562]: gnome-session-binary[1562]: 
GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
  May  9 16:34:59 Eliot gnome-session-binary[1562]: GLib-GObject-CRITICAL: 
g_object_unref: assertion 'G_IS_OBJECT (object)' failed
  May  9 16:34:59 Eliot gnome-session[1562]: gnome-session-binary[1562]: 
GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
  May  9 16:34:59 Eliot gnome-session-binary[1562]: GLib-GObject-CRITICAL: 
g_object_unref: assertion 'G_IS_OBJECT (object)' failed
  May  9 16:34:59 Eliot gnome-session[1562]: gnome-session-binary[1562]: 
GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
  May  9 16:34:59 Eliot gnome-session-binary[1562]: GLib-GObject-CRITICAL: 
g_object_unref: assertion 'G_IS_OBJECT (object)' failed
  May  9 16:35:01 Eliot org.gnome.zeitgeist.Engine[1400]: 
(zeitgeist-daemon:2197): GLib-GObject-CRITICAL **: g_object_unref: assertion 
'object->ref_count > 0' failed
  May  9 16:42:54 Eliot gnome-session[1576]: (nautilus:2606): 
GLib-GObject-CRITICAL **: g_signal_connect_object: assertion 
'G_TYPE_CHECK_INSTANCE (instance)' failed
  May  9 16:59:53 Eliot gnome-session[1576]: (nautilus:2842): 
GLib-GObject-CRITICAL **: g_signal_connect_object: assertion 
'G_TYPE_CHECK_INSTANCE (instance)' failed
  May  9 17:00:19 Eliot gnome-session[1576]: (nautilus:2857): 
GLib-GObject-CRITICAL **: g_signal_connect_object: assertion 
'G_TYPE_CHECK_INSTANCE (instance)' failed

  The last three failures appears whenever I activate nautilus.
  Nautilus will appear and work as usual.

  How can I resolve these failure notices?  Thanks in advance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1582496/+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 1333417] Re: [regression] [Dell Latitude E6520] [NVS 4200M] Hangs on resume from suspend

2015-09-27 Thread Rebecca Palmer 
I no longer have the affected hardware.

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

Title:
  [regression] [Dell Latitude E6520] [NVS 4200M] Hangs on resume from
  suspend

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

Bug description:
  In Trusty with the Nouveau driver selected, the system hangs on resume
  from suspend, sometimes showing some or all of the pre-suspend screen
  contents, and sometimes a "boot messages" screen.

  The system log shows activity after resume, and sometimes (not always) 
contains the error
  nouveau E[Xorg[1185]] failed to idle channel 0x0001 [Xorg[1185]]

  This problem did not exist in Saucy (though the random crash bug
  1244312 did).  It cannot be tested with the nvidia-331 driver because
  bug 1333431 prevents suspend with that.

  Possibly relevant: this system has an outdated BIOS because the
  updater requires Windows (see bug 1244312).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.38  Wed Jan  8 19:32:30 
PST 2014
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  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: Mon Jun 23 21:36:37 2014
  DistUpgraded: 2014-04-29 18:46:17,249 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.13.0-27-generic, x86_64: installed
   bbswitch, 0.7, 3.13.0-29-generic, x86_64: installed
   nvidia-331, 331.38, 3.13.0-29-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GF119M [NVS 4200M] [10de:1056] (rev a1) (prog-if 00 [VGA 
controller])
 Subsystem: Dell Device [1028:0494]
  InstallationDate: Installed on 2012-01-25 (880 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MachineType: Dell Inc. Latitude E6520
  PlymouthDebug: Error: [Errno 13] Permission denied: 
'/var/log/plymouth-debug.log'
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic 
root=UUID=b491a34a-6045-4ad4-a2b8-b9ca018c5d41 ro quiet reboot=p
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: Upgraded to trusty on 2014-04-29 (55 days ago)
  dmi.bios.date: 10/18/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0J4TFW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd10/18/2011:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0J4TFW:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6520
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon Jun 23 20:07:29 2014
  xserver.configfile: default
  xserver.errors: open /dev/fb0: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.15.1-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1333417/+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 1437482] [NEW] Installer issue

2015-03-27 Thread Jeff Palmer 
Public bug reported:

I'm installing 15.04 on a 2013 Macbook Pro, 13 retina.

It looks like each 'screen' in the process is displayed in a pane or
window, that you can drag around to relocate. One of the panes is
titled Install )as superuser) Preparing to Install Ubuntu' and the
checkmarks for free space, plugged into power source, and connection to
the internet are checked.   Upong clicking 'continue' in this pane,  I
initially thought the installer hung.  I waited for nearly 30 minutes,
and it never progressed to the next screen. I tried movint that pane
around with the mouse, as it seemed.. odd, like it was off center, and
something was 'off the screen' below the visible area. However, the
mouse was unable to move the 'pane'

Upon a second install attempt,  before it got to this point again, I
moved the pane to the top left corner, as far as I could.  when I got to
the same point mentioned above, I clicked continue. After a few moments,
a UEFI warning popped up, telling me that some OS is set to bios
compatibility mode.  I suspect that it was actually this prompt that was
below the visible screen real estate, and caused the assumed 'hang'.

After having relocated the menu, and accepting the UEFI warning, the
installation proceeded.  However, it also popped that same UEFI warning
up approximately 4 additional times during the install process.  This
seems a bit excessive, as once should be enough. I'm not sure if the
repeated prompting is intended, or a bug.  But if it's intended, I would
vote that it's a bit.. excessive.

I'll reinstall this evening after I get home, and attach some
screenshots to this report, as I think that would do better than trying
to explain what I mean by a 'pane

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
Uname: Linux 3.19.0-10-generic x86_64
NonfreeKernelModules: wl
.tmp.unity.support.test.0:
 
ApportVersion: 2.16.2-0ubuntu5
Architecture: amd64
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: Fri Mar 27 16:05:28 2015
DistUpgraded: Fresh install
DistroCodename: vivid
DistroVariant: ubuntu
DkmsStatus: bcmwl, 6.30.223.248+bdcom, 3.19.0-10-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Device [8086:0a2e] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Apple Inc. Device [106b:011a]
InstallationDate: Installed on 2015-03-27 (0 days ago)
InstallationMedia: Ubuntu 15.04 Vivid Vervet - Beta amd64 (20150326)
MachineType: Apple Inc. MacBookPro11,1
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-10-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/07/2015
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP111.88Z.0138.B14.1501071216
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-189A3D4F975D5FFC
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro11,1
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-189A3D4F975D5FFC
dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP111.88Z.0138.B14.1501071216:bd01/07/2015:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC:
dmi.product.name: MacBookPro11,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
version.compiz: compiz 1:0.9.12.1+15.04.20150303-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.59-0ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.0-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.0-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2build1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
xserver.bootTime: Fri Mar 27 16:03:14 2015
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   40992 
 vendor APP
xserver.version: 2:1.17.1-0ubuntu3

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


** Tags: amd64 apport-bug compiz-0.9 install ubuntu vivid

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

Title:
  Installer issue

Status in xorg package in

[Desktop-packages] [Bug 1437482] Re: Installer issue

2015-03-27 Thread Jeff Palmer 
After reading this again, I don't think I'm accurately describing the
pane

I'm not referring to each screen during the install,  but more..  the
frame  or screen that the install screen is being drawn onto.  the
window you can drag around with the mouse.  maybe a better name would
be.. modal?

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

Title:
  Installer issue

Status in xorg package in Ubuntu:
  New

Bug description:
  I'm installing 15.04 on a 2013 Macbook Pro, 13 retina.

  It looks like each 'screen' in the process is displayed in a pane or
  window, that you can drag around to relocate. One of the panes is
  titled Install )as superuser) Preparing to Install Ubuntu' and the
  checkmarks for free space, plugged into power source, and connection
  to the internet are checked.   Upong clicking 'continue' in this pane,
  I initially thought the installer hung.  I waited for nearly 30
  minutes, and it never progressed to the next screen. I tried movint
  that pane around with the mouse, as it seemed.. odd, like it was off
  center, and something was 'off the screen' below the visible area.
  However, the mouse was unable to move the 'pane'

  Upon a second install attempt,  before it got to this point again, I
  moved the pane to the top left corner, as far as I could.  when I got
  to the same point mentioned above, I clicked continue. After a few
  moments, a UEFI warning popped up, telling me that some OS is set to
  bios compatibility mode.  I suspect that it was actually this prompt
  that was below the visible screen real estate, and caused the assumed
  'hang'.

  After having relocated the menu, and accepting the UEFI warning, the
  installation proceeded.  However, it also popped that same UEFI
  warning up approximately 4 additional times during the install
  process.  This seems a bit excessive, as once should be enough. I'm
  not sure if the repeated prompting is intended, or a bug.  But if it's
  intended, I would vote that it's a bit.. excessive.

  I'll reinstall this evening after I get home, and attach some
  screenshots to this report, as I think that would do better than
  trying to explain what I mean by a 'pane

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.16.2-0ubuntu5
  Architecture: amd64
  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: Fri Mar 27 16:05:28 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  DkmsStatus: bcmwl, 6.30.223.248+bdcom, 3.19.0-10-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:0a2e] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Apple Inc. Device [106b:011a]
  InstallationDate: Installed on 2015-03-27 (0 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Beta amd64 (20150326)
  MachineType: Apple Inc. MacBookPro11,1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-10-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/07/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP111.88Z.0138.B14.1501071216
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-189A3D4F975D5FFC
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-189A3D4F975D5FFC
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP111.88Z.0138.B14.1501071216:bd01/07/2015:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC:
  dmi.product.name: MacBookPro11,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz 1:0.9.12.1+15.04.20150303-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.59-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.0-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.0-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2build1

[Desktop-packages] [Bug 1437482] Re: Installer issue

2015-03-27 Thread Jeff Palmer 
This is after I drag the screen to the upper left.  Notice how the
underlying pane that the installation step is redrawn onto..  extends
past the bottom of the screen you normally see displayed?   I suspect
the UEFI warning is being drawn below that,  so if you don't drag it
up.. the UEFI screen is never viewable.

For what it's worth, I installed this into a VM as well, and the
installation screens look as you'd expect. So this appears to be
isolated to this laptop, or display resolution in some way.


** Attachment added: IMG_20150327_155952.jpg
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1437482/+attachment/4358231/+files/IMG_20150327_155952.jpg

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

Title:
  Installer issue

Status in xorg package in Ubuntu:
  New

Bug description:
  I'm installing 15.04 on a 2013 Macbook Pro, 13 retina.

  It looks like each 'screen' in the process is displayed in a pane or
  window, that you can drag around to relocate. One of the panes is
  titled Install )as superuser) Preparing to Install Ubuntu' and the
  checkmarks for free space, plugged into power source, and connection
  to the internet are checked.   Upong clicking 'continue' in this pane,
  I initially thought the installer hung.  I waited for nearly 30
  minutes, and it never progressed to the next screen. I tried movint
  that pane around with the mouse, as it seemed.. odd, like it was off
  center, and something was 'off the screen' below the visible area.
  However, the mouse was unable to move the 'pane'

  Upon a second install attempt,  before it got to this point again, I
  moved the pane to the top left corner, as far as I could.  when I got
  to the same point mentioned above, I clicked continue. After a few
  moments, a UEFI warning popped up, telling me that some OS is set to
  bios compatibility mode.  I suspect that it was actually this prompt
  that was below the visible screen real estate, and caused the assumed
  'hang'.

  After having relocated the menu, and accepting the UEFI warning, the
  installation proceeded.  However, it also popped that same UEFI
  warning up approximately 4 additional times during the install
  process.  This seems a bit excessive, as once should be enough. I'm
  not sure if the repeated prompting is intended, or a bug.  But if it's
  intended, I would vote that it's a bit.. excessive.

  I'll reinstall this evening after I get home, and attach some
  screenshots to this report, as I think that would do better than
  trying to explain what I mean by a 'pane

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.16.2-0ubuntu5
  Architecture: amd64
  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: Fri Mar 27 16:05:28 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  DkmsStatus: bcmwl, 6.30.223.248+bdcom, 3.19.0-10-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:0a2e] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Apple Inc. Device [106b:011a]
  InstallationDate: Installed on 2015-03-27 (0 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Beta amd64 (20150326)
  MachineType: Apple Inc. MacBookPro11,1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-10-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/07/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP111.88Z.0138.B14.1501071216
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-189A3D4F975D5FFC
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-189A3D4F975D5FFC
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP111.88Z.0138.B14.1501071216:bd01/07/2015:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC:
  dmi.product.name: MacBookPro11,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz 1:0.9.12.1+15.04.20150303-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.59-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.0-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx:

[Desktop-packages] [Bug 1437482] Re: Installer issue

2015-03-27 Thread Jeff Palmer 
** Attachment added: 1
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1437482/+attachment/4358230/+files/IMG_20150327_155934.jpg

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

Title:
  Installer issue

Status in xorg package in Ubuntu:
  New

Bug description:
  I'm installing 15.04 on a 2013 Macbook Pro, 13 retina.

  It looks like each 'screen' in the process is displayed in a pane or
  window, that you can drag around to relocate. One of the panes is
  titled Install )as superuser) Preparing to Install Ubuntu' and the
  checkmarks for free space, plugged into power source, and connection
  to the internet are checked.   Upong clicking 'continue' in this pane,
  I initially thought the installer hung.  I waited for nearly 30
  minutes, and it never progressed to the next screen. I tried movint
  that pane around with the mouse, as it seemed.. odd, like it was off
  center, and something was 'off the screen' below the visible area.
  However, the mouse was unable to move the 'pane'

  Upon a second install attempt,  before it got to this point again, I
  moved the pane to the top left corner, as far as I could.  when I got
  to the same point mentioned above, I clicked continue. After a few
  moments, a UEFI warning popped up, telling me that some OS is set to
  bios compatibility mode.  I suspect that it was actually this prompt
  that was below the visible screen real estate, and caused the assumed
  'hang'.

  After having relocated the menu, and accepting the UEFI warning, the
  installation proceeded.  However, it also popped that same UEFI
  warning up approximately 4 additional times during the install
  process.  This seems a bit excessive, as once should be enough. I'm
  not sure if the repeated prompting is intended, or a bug.  But if it's
  intended, I would vote that it's a bit.. excessive.

  I'll reinstall this evening after I get home, and attach some
  screenshots to this report, as I think that would do better than
  trying to explain what I mean by a 'pane

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.16.2-0ubuntu5
  Architecture: amd64
  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: Fri Mar 27 16:05:28 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  DkmsStatus: bcmwl, 6.30.223.248+bdcom, 3.19.0-10-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:0a2e] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Apple Inc. Device [106b:011a]
  InstallationDate: Installed on 2015-03-27 (0 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Beta amd64 (20150326)
  MachineType: Apple Inc. MacBookPro11,1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-10-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/07/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP111.88Z.0138.B14.1501071216
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-189A3D4F975D5FFC
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-189A3D4F975D5FFC
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP111.88Z.0138.B14.1501071216:bd01/07/2015:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC:
  dmi.product.name: MacBookPro11,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz 1:0.9.12.1+15.04.20150303-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.59-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.0-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.0-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
  xserver.bootTime: Fri Mar 27 16:03:14 2015
  xserver.configfile: default
  xserver.errors:

[Desktop-packages] [Bug 1079011] Re: stellarium assert failure: nv10_state_fb.c:50: get_rt_format: Assertion `0' failed.

2015-03-07 Thread Rebecca Palmer 
As nobody has been able to test this in flightgear, assuming it's the
same really-in-mesa problem.  (It's also likely that this hardware
wouldn't run flightgear at a usable speed anyway.)

** Changed in: flightgear (Ubuntu)
   Status: Incomplete = Invalid

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

Title:
  stellarium assert failure:  nv10_state_fb.c:50: get_rt_format:
  Assertion `0' failed.

Status in flightgear package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Confirmed
Status in stellarium package in Ubuntu:
  Invalid

Bug description:
  Stellarium crashes a few seconds after displaying the startup screen
  with this message in terminal:

  nv10_state_fb.c:50: get_rt_format: Assertion `0' failed.

  I have an nvidia GeForce4 MX 4000 video card, and have installed
  libgl1-mesa-dri and libgl1-mesa-dri-experimental, version
  9.0-0ubuntu1.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: stellarium 0.11.3-1
  ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
  Uname: Linux 3.5.0-18-generic i686
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: i386
  Date: Wed Nov 14 22:52:36 2012
  InstallationDate: Installed on 2012-04-05 (224 days ago)
  InstallationMedia: Xubuntu 11.10 Oneiric Ocelot - Release i386 (20111012)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: stellarium
  UpgradeStatus: Upgraded to quantal on 2012-10-20 (25 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flightgear/+bug/1079011/+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 1079011] Re: stellarium assert failure: nv10_state_fb.c:50: get_rt_format: Assertion `0' failed.

2015-02-15 Thread Rebecca Palmer 
Assigning a bug to yourself means intending to fix it, which given that
you can;t do anything was probably not what you meant.

If your system does not work, please file a new bug stating exactly what
is wrong: https://help.ubuntu.com/community/ReportingBugs

If you are looking for general help with using Ubuntu, please use
http://www.ubuntuforums.org/ or http://askubuntu.com/

** Changed in: flightgear (Ubuntu)
 Assignee: sidlwebb (sidlwebb) = (unassigned)

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

Title:
  stellarium assert failure:  nv10_state_fb.c:50: get_rt_format:
  Assertion `0' failed.

Status in flightgear package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Confirmed
Status in stellarium package in Ubuntu:
  Invalid

Bug description:
  Stellarium crashes a few seconds after displaying the startup screen
  with this message in terminal:

  nv10_state_fb.c:50: get_rt_format: Assertion `0' failed.

  I have an nvidia GeForce4 MX 4000 video card, and have installed
  libgl1-mesa-dri and libgl1-mesa-dri-experimental, version
  9.0-0ubuntu1.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: stellarium 0.11.3-1
  ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
  Uname: Linux 3.5.0-18-generic i686
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: i386
  Date: Wed Nov 14 22:52:36 2012
  InstallationDate: Installed on 2012-04-05 (224 days ago)
  InstallationMedia: Xubuntu 11.10 Oneiric Ocelot - Release i386 (20111012)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: stellarium
  UpgradeStatus: Upgraded to quantal on 2012-10-20 (25 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flightgear/+bug/1079011/+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 830663] Re: default window size is too small

2014-12-01 Thread Gary Palmer 
I just installed Inkscape on Mavericks on an iMac for the first time.
The Inkscape window opens and it is easy to expand the page to full
screen, but the apparent work page is a very small rectangle within a
much larger work space. Is one supposed to work within the tiny window
or ignore it, in which case it would be distracting? Or is it just badly
sized for my screen,and if so, is there a fix? I have included a screen
capture of the window shrunk to a small portion of the screen, but the
size of the work page remains the same inadequate size. Ideally, the
work page would take up most of the screen.

Also, why does the application label say X11 rather than Inkscape?

** Attachment added: tiff file of inkscape window
   
https://bugs.launchpad.net/inkscape/+bug/830663/+attachment/4272482/+files/inkscape_window.tiff

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

Title:
  default window size is too small

Status in Inkscape: A Vector Drawing Tool:
  Fix Committed
Status in inkscape package in Ubuntu:
  Triaged

Bug description:
  The default window size for Inkscape is too small. Attached is a
  screenshot showing how it starts for me every time. It would be nice
  if Inkscape started maximised or at least a whole lot bigger than it
  is now, so it can be useful immediately.

To manage notifications about this bug go to:
https://bugs.launchpad.net/inkscape/+bug/830663/+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 1079011] Re: stellarium assert failure: nv10_state_fb.c:50: get_rt_format: Assertion `0' failed.

2014-11-25 Thread Rebecca Palmer 
The error occurs because nv10 (the driver used for this card) declares
VBO support (extension GL_ARB_vertex_buffer_object) but only supports
VBOs of int8, int16 and float (not double) types, and the application is
trying to draw data of type double.  Given that the double type is part
of the OpenGL spec, that would appear to be a bug in mesa, not the
application.

The easy fix would be don't declare VBO support on those cards, but
that would slow down many other applications, and break any that require
this feature.

An alternative would be a software fallback that reads back the VBO data
and draws it as either a client-side array or individual primitives
(which would probably be even slower, but only applications that
actually use doubles would take the penalty), but that might be more
work than is reasonable to do for little benefit: stellarium and other
QtOpenGL applications will lose OpenGL 1 support in the upcoming Qt 5
transition anyway, and flightgear would probably be unusably slow on
such old hardware even if it didn't crash.

As an immediate workaround, you can use software rendering with
LIBGL_ALWAYS_SOFTWARE=1 stellarium
(perhaps the error message should suggest that?), but expect that to be slow.

I will report this upstream.

** Changed in: stellarium (Ubuntu)
   Status: Confirmed = Invalid

** Changed in: flightgear (Ubuntu)
   Status: New = Incomplete

** Changed in: mesa (Ubuntu)
   Status: Incomplete = Confirmed

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

Title:
  stellarium assert failure:  nv10_state_fb.c:50: get_rt_format:
  Assertion `0' failed.

Status in “flightgear” package in Ubuntu:
  Incomplete
Status in “mesa” package in Ubuntu:
  Confirmed
Status in “stellarium” package in Ubuntu:
  Invalid

Bug description:
  Stellarium crashes a few seconds after displaying the startup screen
  with this message in terminal:

  nv10_state_fb.c:50: get_rt_format: Assertion `0' failed.

  I have an nvidia GeForce4 MX 4000 video card, and have installed
  libgl1-mesa-dri and libgl1-mesa-dri-experimental, version
  9.0-0ubuntu1.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: stellarium 0.11.3-1
  ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
  Uname: Linux 3.5.0-18-generic i686
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: i386
  Date: Wed Nov 14 22:52:36 2012
  InstallationDate: Installed on 2012-04-05 (224 days ago)
  InstallationMedia: Xubuntu 11.10 Oneiric Ocelot - Release i386 (20111012)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: stellarium
  UpgradeStatus: Upgraded to quantal on 2012-10-20 (25 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flightgear/+bug/1079011/+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 1079011] Re: stellarium assert failure: nv10_state_fb.c:50: get_rt_format: Assertion `0' failed.

2014-11-25 Thread Rebecca Palmer 
Sorry, upstream explicitly don't want bug reports for cards older than
nv30 (yours is nv18, current is ~nv120):
http://nouveau.freedesktop.org/wiki/MesaDrivers/

Changing the error message (at
http://sources.debian.net/src/mesa/10.3.2-1/src/mesa/drivers/dri/nouveau/nv10_render.c/#L104
) to something more useful, e.g.

-  assert(0);
+  assert(0  This application requires GLdouble vertex buffers, which your 
graphics card does not support.  Try software rendering 
(LIBGL_ALWAYS_SOFTWARE=1 application).);

is probably about all that is reasonable to do as a Debian/Ubuntu patch.

** Tags removed: quantal third-party-packages
** Tags added: patch

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

Title:
  stellarium assert failure:  nv10_state_fb.c:50: get_rt_format:
  Assertion `0' failed.

Status in “flightgear” package in Ubuntu:
  Incomplete
Status in “mesa” package in Ubuntu:
  Confirmed
Status in “stellarium” package in Ubuntu:
  Invalid

Bug description:
  Stellarium crashes a few seconds after displaying the startup screen
  with this message in terminal:

  nv10_state_fb.c:50: get_rt_format: Assertion `0' failed.

  I have an nvidia GeForce4 MX 4000 video card, and have installed
  libgl1-mesa-dri and libgl1-mesa-dri-experimental, version
  9.0-0ubuntu1.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: stellarium 0.11.3-1
  ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
  Uname: Linux 3.5.0-18-generic i686
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: i386
  Date: Wed Nov 14 22:52:36 2012
  InstallationDate: Installed on 2012-04-05 (224 days ago)
  InstallationMedia: Xubuntu 11.10 Oneiric Ocelot - Release i386 (20111012)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: stellarium
  UpgradeStatus: Upgraded to quantal on 2012-10-20 (25 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flightgear/+bug/1079011/+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 1079011] Re: stellarium assert failure: nv10_state_fb.c:50: get_rt_format: Assertion `0' failed.

2014-11-24 Thread Rebecca Palmer 
(Sorry about the repeated questions: that's the nature of debugging a
problem that only happens on hardware I don't have.)

That looks like either a bad GLcontext (at the error location it is only
looking at this internal structure, not the objects to be drawn), or an
attempt to use VBO (an OpenGL 1.5 feature) on an OpenGL 1.2 card.

Can you try this, preferably in a terminal with unlimited scrollback (Edit  
Profile Preferences  Scrolling) as there may be a lot of output:
$ sudo apt-get install libqt4-dbg mesa-utils
$ glxinfo 
$ gdb --args stellarium
(gdb) run
[wait for crash, Alt+Tab back to terminal]
[all this is at the (gdb) prompt, writing it without prompts so you can cut and 
paste it]
set pagination 0
thread apply all bt full
frame 9
print *ctx
print *nctx
frame 10
print *vbo
print *exec

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

Title:
  stellarium assert failure:  nv10_state_fb.c:50: get_rt_format:
  Assertion `0' failed.

Status in “flightgear” package in Ubuntu:
  New
Status in “mesa” package in Ubuntu:
  Incomplete
Status in “stellarium” package in Ubuntu:
  Confirmed

Bug description:
  Stellarium crashes a few seconds after displaying the startup screen
  with this message in terminal:

  nv10_state_fb.c:50: get_rt_format: Assertion `0' failed.

  I have an nvidia GeForce4 MX 4000 video card, and have installed
  libgl1-mesa-dri and libgl1-mesa-dri-experimental, version
  9.0-0ubuntu1.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: stellarium 0.11.3-1
  ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
  Uname: Linux 3.5.0-18-generic i686
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: i386
  Date: Wed Nov 14 22:52:36 2012
  InstallationDate: Installed on 2012-04-05 (224 days ago)
  InstallationMedia: Xubuntu 11.10 Oneiric Ocelot - Release i386 (20111012)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: stellarium
  UpgradeStatus: Upgraded to quantal on 2012-10-20 (25 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flightgear/+bug/1079011/+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 1079011] Re: stellarium assert failure: nv10_state_fb.c:50: get_rt_format: Assertion `0' failed.

2014-11-23 Thread Rebecca Palmer 
 stellarium: 
 ../../../../../../../src/mesa/drivers/dri/nouveau/nv10_render.c:104: 
 get_hw_format: Assertion `0' failed.
That also appears to mean invalid format, so is probably the same bug.

 For whatever it's worth, I did the routine you described. The Stellarium 
 startup screen appeared but didn't disappear.
That's expected when something crashes under a debugger: please switch back to 
the debugger window (Alt+Tab), type thread apply all bt full and post the 
output.  (You can then close the debugger and program with quit.)

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

Title:
  stellarium assert failure:  nv10_state_fb.c:50: get_rt_format:
  Assertion `0' failed.

Status in “flightgear” package in Ubuntu:
  New
Status in “mesa” package in Ubuntu:
  Incomplete
Status in “stellarium” package in Ubuntu:
  Confirmed

Bug description:
  Stellarium crashes a few seconds after displaying the startup screen
  with this message in terminal:

  nv10_state_fb.c:50: get_rt_format: Assertion `0' failed.

  I have an nvidia GeForce4 MX 4000 video card, and have installed
  libgl1-mesa-dri and libgl1-mesa-dri-experimental, version
  9.0-0ubuntu1.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: stellarium 0.11.3-1
  ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
  Uname: Linux 3.5.0-18-generic i686
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: i386
  Date: Wed Nov 14 22:52:36 2012
  InstallationDate: Installed on 2012-04-05 (224 days ago)
  InstallationMedia: Xubuntu 11.10 Oneiric Ocelot - Release i386 (20111012)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: stellarium
  UpgradeStatus: Upgraded to quantal on 2012-10-20 (25 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flightgear/+bug/1079011/+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 1079011] Re: stellarium assert failure: nv10_state_fb.c:50: get_rt_format: Assertion `0' failed.

2014-11-19 Thread Rebecca Palmer 
** Also affects: mesa (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  stellarium assert failure:  nv10_state_fb.c:50: get_rt_format:
  Assertion `0' failed.

Status in “flightgear” package in Ubuntu:
  New
Status in “mesa” package in Ubuntu:
  New
Status in “stellarium” package in Ubuntu:
  Confirmed

Bug description:
  Stellarium crashes a few seconds after displaying the startup screen
  with this message in terminal:

  nv10_state_fb.c:50: get_rt_format: Assertion `0' failed.

  I have an nvidia GeForce4 MX 4000 video card, and have installed
  libgl1-mesa-dri and libgl1-mesa-dri-experimental, version
  9.0-0ubuntu1.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: stellarium 0.11.3-1
  ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
  Uname: Linux 3.5.0-18-generic i686
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: i386
  Date: Wed Nov 14 22:52:36 2012
  InstallationDate: Installed on 2012-04-05 (224 days ago)
  InstallationMedia: Xubuntu 11.10 Oneiric Ocelot - Release i386 (20111012)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: stellarium
  UpgradeStatus: Upgraded to quantal on 2012-10-20 (25 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flightgear/+bug/1079011/+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 1079011] Re: stellarium assert failure: nv10_state_fb.c:50: get_rt_format: Assertion `0' failed.

2014-11-19 Thread Rebecca Palmer 
That message means invalid/unsupported buffer format (
http://sources.debian.net/src/mesa/10.3.2-1/src/mesa/drivers/dri/nouveau/nv10_state_fb.c
), and as it appears to refer to an internal nouveau buffer rather than
a passed-in texture, I suspect this is actually a mesa/nouveau bug.

As I do not have the hardware to test this myself, please do (in a
terminal):

$ sudo apt-get install libgl1-mesa-dri-dbg gdb
$ gdb --args fgfs
[or gdb --args stellarium, whichever is easier to reproduce the crash in]
(gdb) set pagination 0
(gdb) run
[wait for crash]
(gdb) thread apply all bt full

and post the ouput here.

** Changed in: mesa (Ubuntu)
   Status: New = Incomplete

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

Title:
  stellarium assert failure:  nv10_state_fb.c:50: get_rt_format:
  Assertion `0' failed.

Status in “flightgear” package in Ubuntu:
  New
Status in “mesa” package in Ubuntu:
  Incomplete
Status in “stellarium” package in Ubuntu:
  Confirmed

Bug description:
  Stellarium crashes a few seconds after displaying the startup screen
  with this message in terminal:

  nv10_state_fb.c:50: get_rt_format: Assertion `0' failed.

  I have an nvidia GeForce4 MX 4000 video card, and have installed
  libgl1-mesa-dri and libgl1-mesa-dri-experimental, version
  9.0-0ubuntu1.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: stellarium 0.11.3-1
  ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
  Uname: Linux 3.5.0-18-generic i686
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: i386
  Date: Wed Nov 14 22:52:36 2012
  InstallationDate: Installed on 2012-04-05 (224 days ago)
  InstallationMedia: Xubuntu 11.10 Oneiric Ocelot - Release i386 (20111012)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: stellarium
  UpgradeStatus: Upgraded to quantal on 2012-10-20 (25 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flightgear/+bug/1079011/+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 1315156] Re: nvidia-331 selected but nouveau loads

2014-07-13 Thread Rebecca Palmer 
The full workaround sequence is the one I posted in the updated
description, not the comments.  (There's no such package as just
nouveau, so sudo apt-get remove nouveau won't do anything, and the
drivers dialog does  a remove not the here-required purge.)

I also have the nouveau W[ PFIFO][:01:00.0] INTR 0x0100:
0x0005 messages when running nouveau, sometimes ending in a crash
(bug 1243557), and can't suspend with either driver (bug 1333417 / bug
1333431).  I don't have HDMI sound so can't test that, but would suggest
filing a separate bug for that problem.

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

Title:
  nvidia-331 selected but nouveau loads

Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  Confirmed
Status in “xserver-xorg-video-nouveau” package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to Trusty, I briefly used the nouveau driver to check
  whether bug 1243557 still existed; after finding that it did, I
  switched back to nvidia-331.

  However since then, frequently (50% but not always), the system loads
  nouveau first, then fails to load nvidia-331 because of this:

  Apr 30 08:00:29 lap14 kernel: [   17.789267] nouveau  [  
DEVICE][:01:00.0] BOOT0  : 0x0d9160a1
  Apr 30 08:00:29 lap14 kernel: [   17.789269] nouveau  [  
DEVICE][:01:00.0] Chipset: GF119 (NVD9)
  Apr 30 08:00:29 lap14 kernel: [   17.789271] nouveau  [  
DEVICE][:01:00.0] Family : NVD0
  [...]
  Apr 30 08:00:32 lap14 kernel: [   21.574983] NVRM: The NVIDIA probe routine 
was not called for 1 device(s).
  Apr 30 08:00:32 lap14 kernel: [   21.574987] NVRM: This can occur when a 
driver such as: 
  Apr 30 08:00:32 lap14 kernel: [   21.574987] NVRM: nouveau, rivafb, nvidiafb 
or rivatv 
  Apr 30 08:00:32 lap14 kernel: [   21.574987] NVRM: was loaded and obtained 
ownership of the NVIDIA device(s).

  WORKAROUND: at a text terminal:
  sudo apt-get purge nvidia-331
  sudo apt-get install nvidia-331
  sudo update-initramfs -u
  sudoedit /etc/default/grub
  #remove 'splash' from GRUB_CMDLINE_LINUX_DEFAULT, and save with the default 
name
  sudo update-grub
  #reboot the system

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331 331.38-0ubuntu7
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu May  1 22:08:36 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-01-25 (827 days ago)
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  SourcePackage: nvidia-graphics-drivers-331
  UpgradeStatus: Upgraded to trusty on 2014-04-29 (2 days ago)
  modified.conffile..etc.modprobe.d.nvidia.331.hybrid.conf: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1315156/+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 1243557]

2014-07-01 Thread Rebecca Palmer 
Created attachment 101990
kernel log 3.15rc-Jun-27

This bug still exists in drm-nouveau-next (commit
242a42eadfc17448a0d5b2ffc0cb191c8b51971a) with Ubuntu 14.04 userspace.
The error message has changed to E[   PFIFO][:01:00.0] INTR
0x0080, and some of the INTR 0x0100: 0x0005 warnings now
come _after_ it.

In Ubuntu 14.04 (not 13.10) with either this git kernel or its standard
3.13, there is also a hang on resume from suspend
(https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
nouveau/+bug/1333417), but it is not clear whether this is a driver or
BIOS problem.

In the attached, the original bug is at 08:09:47 and 08:20:06, the
resume failure (which can log GPU lockup, failed to idle chanel
0x0001 [Xorg[1185]], or nothing) is at 08:14:53.

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

Title:
  10de:1056 [Dell Latitude E6520] [NVS 4200M] X freeze, unhandled
  status 0x0080

Status in Accelerated Xorg driver for nVidia cards:
  Confirmed
Status in “xserver-xorg-video-nouveau” package in Ubuntu:
  Triaged

Bug description:
  With the Nouveau driver selected, my system freezes within a few
  minutes of boot if on battery, but only on heavy graphics load
  (flightgear in maximized window) if on mains. The mouse pointer still
  moves at first, but often freezes later; the keyboard LEDs do not
  react. Sounds already playing continue until finished, but don't
  repeat if set to (i.e. applications are frozen). Alt+SysRq works
  (provided bug 1244312 is fixed first).

  The kernel log nearly always contains the line
  nouveau ![   PFIFO][:01:00.0] unhandled status 0x0080

  and sometimes other errors as well, while the Xorg log often contains
  EQ overflow errors; the full logs are attached.

  WORKAROUND: This does not occur with the nvidia-319 driver.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  319.32  Wed Jun 19 15:51:20 
PDT 2013
   GCC version:  gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu8)
  .tmp.unity.support.test.0:

  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Oct 23 08:19:06 2013
  DistUpgraded: 2013-10-21 23:03:05,341 DEBUG enabling apt cron job
  DistroCodename: saucy
  DistroVariant: ubuntu
  DkmsStatus: nvidia-319, 319.32, 3.11.0-12-generic, x86_64: installed
  EcryptfsInUse: Yes
  GraphicsCard:
   NVIDIA Corporation GF119M [NVS 4200M] [10de:1056] (rev a1) (prog-if 00 [VGA 
controller])
     Subsystem: Dell Device [1028:0494]
  InstallationDate: Installed on 2012-01-25 (636 days ago)
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  JockeyStatus:
   kmod:nvidia_319_updates - NVIDIA binary Xorg driver, kernel module and VDPAU 
library (Proprietary, Disabled, Not in use)
   kmod:wl - Broadcom STA wireless driver (Proprietary, Disabled, Not in use) 
[auto-install]
   kmod:nvidia_304 - NVIDIA binary Xorg driver, kernel module and VDPAU library 
(Proprietary, Disabled, Not in use)
   kmod:nvidia_304_updates - NVIDIA binary Xorg driver, kernel module and VDPAU 
library (Proprietary, Disabled, Not in use)
   kmod:nvidia_319 - nvidia_319 (Proprietary, Enabled, Not in use)
  MachineType: Dell Inc. Latitude E6520
  MarkForUpload: True
  PlymouthDebug: Error: [Errno 13] Permission denied: 
'/var/log/plymouth-debug.log'
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=b491a34a-6045-4ad4-a2b8-b9ca018c5d41 ro quiet splash
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: Upgraded to saucy on 2013-10-21 (1 days ago)
  XorgConf:
   Section Device
    Identifier  Default Device
    Option  NoLogoTrue
   EndSection
  dmi.bios.date: 10/18/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0J4TFW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd10/18/2011:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0J4TFW:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6520
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz

[Desktop-packages] [Bug 1263355] Re: Unable to directly access files of any smartphone from Ubuntu

2014-06-23 Thread Alex Palmer 
I am on Ubuntu 14.04

I have the same problem with a Samsung Galaxy S3 Mini on Android 4.1
but on a Galaxy Nexus with Android 4.3 I do not see the problem and can access 
files directly.
Both phones are setup with MTP enabled in USB settings.

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

Title:
  Unable to directly access files of any smartphone from Ubuntu

Status in “libmtp” package in Ubuntu:
  Confirmed

Bug description:
  Unable to access files of Samsung Trend from Nautilus, when you
  connect device a problem happens: Unable to mound Android, Unable to
  open MTP device '[usb:003,003]' 

  If i try to access files such music or pictures in Android device, i
  get some errors.

  I can copy files from Android device, and paste to a home folder, like
  Pictures or Documents, and it's possible to see images or listen
  musics in this way, for example.

  The expected behavior is to see an ask window, and I could choose what
  I do with the device (open with Nautilus, Rhythmbox, Image viewer,
  Gthumb...).

  lsusb
  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 004: ID 04f2:b3aa Chicony Electronics Co., Ltd 
  Bus 001 Device 023: ID 0489:e062 Foxconn / Hon Hai 
  Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 002: ID 090c:1000 Silicon Motion, Inc. - Taiwan (formerly 
Feiya Technology Corp.) Flash Drive
  Bus 003 Device 004: ID 04e8:6860 Samsung Electronics Co., Ltd GT-I9100 Phone 
[Galaxy S II], GT-I9300 Phone [Galaxy S III], GT-P7500 [Galaxy Tab 10.1]
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libmtp-runtime 1.1.6-20-g1b9f164-1ubuntu2
  ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
  Uname: Linux 3.12.0-7-generic x86_64
  ApportVersion: 2.12.7-0ubuntu3
  Architecture: amd64
  CasperVersion: 1.336ubuntu1
  Date: Sat Dec 21 17:09:49 2013
  LiveMediaBuild: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131221)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libmtp
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libmtp/+bug/1263355/+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 1333417] [NEW] [regression] [Dell Latitude E6520] [NVS 4200M] Hangs on resume from suspend

2014-06-23 Thread Rebecca Palmer 
Public bug reported:

In Trusty with the Nouveau driver selected, the system hangs on resume
from suspend, sometimes showing some or all of the pre-suspend screen
contents, and sometimes a boot messages screen.

The system log shows activity after resume, and sometimes (not always) contains 
the error
nouveau E[Xorg[1185]] failed to idle channel 0x0001 [Xorg[1185]]

This problem did not exist in Saucy (though the random crash bug 1244312
did).

Possibly relevant: this system has an outdated BIOS because the updater
requires Windows (see bug 1244312).

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
Uname: Linux 3.13.0-29-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
.proc.driver.nvidia.registry: Binary: 
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.38  Wed Jan  8 19:32:30 
PST 2014
 GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
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: Mon Jun 23 21:36:37 2014
DistUpgraded: 2014-04-29 18:46:17,249 DEBUG enabling apt cron job
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.7, 3.13.0-27-generic, x86_64: installed
 bbswitch, 0.7, 3.13.0-29-generic, x86_64: installed
 nvidia-331, 331.38, 3.13.0-29-generic, x86_64: installed
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GF119M [NVS 4200M] [10de:1056] (rev a1) (prog-if 00 [VGA 
controller])
   Subsystem: Dell Device [1028:0494]
InstallationDate: Installed on 2012-01-25 (880 days ago)
InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
MachineType: Dell Inc. Latitude E6520
PlymouthDebug: Error: [Errno 13] Permission denied: 
'/var/log/plymouth-debug.log'
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic 
root=UUID=b491a34a-6045-4ad4-a2b8-b9ca018c5d41 ro quiet reboot=p
SourcePackage: xserver-xorg-video-nouveau
UpgradeStatus: Upgraded to trusty on 2014-04-29 (55 days ago)
dmi.bios.date: 10/18/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A08
dmi.board.name: 0J4TFW
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd10/18/2011:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0J4TFW:rvrA01:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E6520
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Mon Jun 23 20:07:29 2014
xserver.configfile: default
xserver.errors: open /dev/fb0: No such file or directory
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.15.1-0ubuntu2

** Affects: xserver-xorg-video-nouveau (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu

** Attachment added: syslog; bug is at Jun 23 19:55:17 and Jun 23 19:58:31
   https://bugs.launchpad.net/bugs/1333417/+attachment/4137694/+files/syslog

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

Title:
  [regression] [Dell Latitude E6520] [NVS 4200M] Hangs on resume from
  suspend

Status in “xserver-xorg-video-nouveau” package in Ubuntu:
  New

Bug description:
  In Trusty with the Nouveau driver selected, the system hangs on resume
  from suspend, sometimes showing some or all of the pre-suspend screen
  contents, and sometimes a boot messages screen.

  The system log shows activity after resume, and sometimes (not always) 
contains the error
  nouveau E[Xorg[1185]] failed to idle channel 0x0001 [Xorg[1185]]

  This problem did not exist in Saucy (though the random crash bug
  1244312 did).

  Possibly relevant: this system has an outdated BIOS because the
  updater requires Windows (see bug 1244312).

[Desktop-packages] [Bug 1333417] Re: [regression] [Dell Latitude E6520] [NVS 4200M] Hangs on resume from suspend

2014-06-23 Thread Rebecca Palmer 
** Description changed:

  In Trusty with the Nouveau driver selected, the system hangs on resume
  from suspend, sometimes showing some or all of the pre-suspend screen
  contents, and sometimes a boot messages screen.
  
  The system log shows activity after resume, and sometimes (not always) 
contains the error
  nouveau E[Xorg[1185]] failed to idle channel 0x0001 [Xorg[1185]]
  
  This problem did not exist in Saucy (though the random crash bug 1244312
- did).
+ did).  It cannot be tested with the nvidia-331 driver because bug
+ 1333431 prevents suspend with that.
  
  Possibly relevant: this system has an outdated BIOS because the updater
  requires Windows (see bug 1244312).
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.38  Wed Jan  8 19:32:30 
PST 2014
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  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: Mon Jun 23 21:36:37 2014
  DistUpgraded: 2014-04-29 18:46:17,249 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.13.0-27-generic, x86_64: installed
   bbswitch, 0.7, 3.13.0-29-generic, x86_64: installed
   nvidia-331, 331.38, 3.13.0-29-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GF119M [NVS 4200M] [10de:1056] (rev a1) (prog-if 00 [VGA 
controller])
 Subsystem: Dell Device [1028:0494]
  InstallationDate: Installed on 2012-01-25 (880 days ago)
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  MachineType: Dell Inc. Latitude E6520
  PlymouthDebug: Error: [Errno 13] Permission denied: 
'/var/log/plymouth-debug.log'
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic 
root=UUID=b491a34a-6045-4ad4-a2b8-b9ca018c5d41 ro quiet reboot=p
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: Upgraded to trusty on 2014-04-29 (55 days ago)
  dmi.bios.date: 10/18/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0J4TFW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd10/18/2011:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0J4TFW:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6520
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon Jun 23 20:07:29 2014
  xserver.configfile: default
  xserver.errors: open /dev/fb0: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.15.1-0ubuntu2

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

Title:
  [regression] [Dell Latitude E6520] [NVS 4200M] Hangs on resume from
  suspend

Status in “xserver-xorg-video-nouveau” package in Ubuntu:
  New

Bug description:
  In Trusty with the Nouveau driver selected, the system hangs on resume
  from suspend, sometimes showing some or all of the pre-suspend screen
  contents, and sometimes a boot messages screen.

  The system log shows activity after resume, and sometimes (not always) 
contains the error
  nouveau E[Xorg[1185]] failed to idle channel 0x0001 [Xorg[1185]]

  This problem did not exist in Saucy (though the random crash bug
  1244312 did).  It cannot be tested with the nvidia-331 driver because
  bug 1333431 prevents suspend with that.

  Possibly relevant: this system has an

[Desktop-packages] [Bug 1333431] Re: [regression] [Dell Latitude E6520] [NVS 4200M] Screen won't turn off, and isn't redrawn on resume

2014-06-23 Thread Rebecca Palmer 
** Attachment added: partly redrawn screen
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1333431/+attachment/4137728/+files/IMG_20140623_222930.jpg

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

Title:
  [regression] [Dell Latitude E6520] [NVS 4200M] Screen won't turn off,
  and isn't redrawn on resume

Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  New

Bug description:
  In Trusty with the nvidia-331 (default) driver selected, the system
  won't suspend, and won't turn the screen off when powersave activates;
  the screen instead briefly blanks, flashes the Nvidia logo, then goes
  to the password entry box.

  On unlocking the system after this has happened (but not after a screen lock 
too brief to reach the powersave timeout), the screen goes black, then 
reappears in pieces as applications redraw.
  (Workaround for this part: opening and closing the Dash (Windows key twice) 
redraws the whole screen.)

  This did not happen in Saucy (nvidia-319); it also doesn't happen with
  the Nouveau driver (though bug 1333417 does, so that's not a
  workaround).

  Possibly relevant: this system has an outdated BIOS because the
  updater requires Windows (see bug 1244312).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331 331.38-0ubuntu7
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jun 23 21:57:54 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-01-25 (880 days ago)
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  SourcePackage: nvidia-graphics-drivers-331
  UpgradeStatus: Upgraded to trusty on 2014-04-29 (55 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1333431/+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 1333431] [NEW] [regression] [Dell Latitude E6520] [NVS 4200M] Screen won't turn off, and isn't redrawn on resume

2014-06-23 Thread Rebecca Palmer 
Public bug reported:

In Trusty with the nvidia-331 (default) driver selected, the system
won't suspend, and won't turn the screen off when powersave activates;
the screen instead briefly blanks, flashes the Nvidia logo, then goes to
the password entry box.

On unlocking the system after this has happened (but not after a screen lock 
too brief to reach the powersave timeout), the screen goes black, then 
reappears in pieces as applications redraw.
(Workaround for this part: opening and closing the Dash (Windows key twice) 
redraws the whole screen.)

This did not happen in Saucy (nvidia-319); it also doesn't happen with
the Nouveau driver (though bug 1333417 does, so that's not a
workaround).

Possibly relevant: this system has an outdated BIOS because the updater
requires Windows (see bug 1244312).

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: nvidia-331 331.38-0ubuntu7
ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
Uname: Linux 3.13.0-29-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Jun 23 21:57:54 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2012-01-25 (880 days ago)
InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
SourcePackage: nvidia-graphics-drivers-331
UpgradeStatus: Upgraded to trusty on 2014-04-29 (55 days ago)

** Affects: nvidia-graphics-drivers-331 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug trusty

** Attachment added: syslog; bug is at Jun 23 20:09:20 and Jun 23 20:10:02
   https://bugs.launchpad.net/bugs/1333431/+attachment/4137723/+files/syslog

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

Title:
  [regression] [Dell Latitude E6520] [NVS 4200M] Screen won't turn off,
  and isn't redrawn on resume

Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  New

Bug description:
  In Trusty with the nvidia-331 (default) driver selected, the system
  won't suspend, and won't turn the screen off when powersave activates;
  the screen instead briefly blanks, flashes the Nvidia logo, then goes
  to the password entry box.

  On unlocking the system after this has happened (but not after a screen lock 
too brief to reach the powersave timeout), the screen goes black, then 
reappears in pieces as applications redraw.
  (Workaround for this part: opening and closing the Dash (Windows key twice) 
redraws the whole screen.)

  This did not happen in Saucy (nvidia-319); it also doesn't happen with
  the Nouveau driver (though bug 1333417 does, so that's not a
  workaround).

  Possibly relevant: this system has an outdated BIOS because the
  updater requires Windows (see bug 1244312).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331 331.38-0ubuntu7
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jun 23 21:57:54 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-01-25 (880 days ago)
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  SourcePackage: nvidia-graphics-drivers-331
  UpgradeStatus: Upgraded to trusty on 2014-04-29 (55 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1333431/+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 1315156] Re: nvidia-331 selected but nouveau loads

2014-05-07 Thread Rebecca Palmer 
I've found out how /etc/modprobe.d/nvidia-331_hybrid.conf disappeared:
nvidia-331's postrm explicitly deletes it, but as it's a conffile
reinstalling nvidia-331 doesn't put it back.  However, having it present
doesn't fix the main bug.

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

Title:
  nvidia-331 selected but nouveau loads

Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  New
Status in “xserver-xorg-video-nouveau” package in Ubuntu:
  New

Bug description:
  After upgrading to Trusty, I briefly used the nouveau driver to check
  whether bug 1243557 still existed; after finding that it did, I
  switched back to nvidia-331.

  However since then, frequently (50% but not always), the system loads
  nouveau first, then fails to load nvidia-331 because of this:

  Apr 30 08:00:29 lap14 kernel: [   17.789267] nouveau  [  
DEVICE][:01:00.0] BOOT0  : 0x0d9160a1
  Apr 30 08:00:29 lap14 kernel: [   17.789269] nouveau  [  
DEVICE][:01:00.0] Chipset: GF119 (NVD9)
  Apr 30 08:00:29 lap14 kernel: [   17.789271] nouveau  [  
DEVICE][:01:00.0] Family : NVD0
  [...]
  Apr 30 08:00:32 lap14 kernel: [   21.574983] NVRM: The NVIDIA probe routine 
was not called for 1 device(s).
  Apr 30 08:00:32 lap14 kernel: [   21.574987] NVRM: This can occur when a 
driver such as: 
  Apr 30 08:00:32 lap14 kernel: [   21.574987] NVRM: nouveau, rivafb, nvidiafb 
or rivatv 
  Apr 30 08:00:32 lap14 kernel: [   21.574987] NVRM: was loaded and obtained 
ownership of the NVIDIA device(s).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331 331.38-0ubuntu7
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu May  1 22:08:36 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-01-25 (827 days ago)
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  SourcePackage: nvidia-graphics-drivers-331
  UpgradeStatus: Upgraded to trusty on 2014-04-29 (2 days ago)
  modified.conffile..etc.modprobe.d.nvidia.331.hybrid.conf: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1315156/+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 1315156] Re: nvidia-331 selected but nouveau loads

2014-05-07 Thread Rebecca Palmer 
Found how nouveau was being loaded while blacklisted: it's in the
initramfs and nvidia-331_hybrid.conf wasn't.

This can be fixed by updating the initramfs (sudo update-initramfs -u,
assuming the kernel you are currently running is the one you want to use
nvidia-331 with), but my system also seems to have forgotten that
nvidia-* needs the text-only splash screen (bug 1063969), causing it to
drop into a low resolution graphics mode.  This can be worked around by
disabling the splash screen entirely (remove splash from the kernel
command line in /etc/default/grub then run update-grub).

** Description changed:

  After upgrading to Trusty, I briefly used the nouveau driver to check
  whether bug 1243557 still existed; after finding that it did, I switched
  back to nvidia-331.
  
  However since then, frequently (50% but not always), the system loads
  nouveau first, then fails to load nvidia-331 because of this:
  
  Apr 30 08:00:29 lap14 kernel: [   17.789267] nouveau  [  
DEVICE][:01:00.0] BOOT0  : 0x0d9160a1
  Apr 30 08:00:29 lap14 kernel: [   17.789269] nouveau  [  
DEVICE][:01:00.0] Chipset: GF119 (NVD9)
  Apr 30 08:00:29 lap14 kernel: [   17.789271] nouveau  [  
DEVICE][:01:00.0] Family : NVD0
  [...]
  Apr 30 08:00:32 lap14 kernel: [   21.574983] NVRM: The NVIDIA probe routine 
was not called for 1 device(s).
  Apr 30 08:00:32 lap14 kernel: [   21.574987] NVRM: This can occur when a 
driver such as: 
  Apr 30 08:00:32 lap14 kernel: [   21.574987] NVRM: nouveau, rivafb, nvidiafb 
or rivatv 
  Apr 30 08:00:32 lap14 kernel: [   21.574987] NVRM: was loaded and obtained 
ownership of the NVIDIA device(s).
  
+ WORKAROUND: at a text terminal:
+ sudo apt-get purge nvidia-331
+ sudo apt-get install nvidia-331
+ sudo update-initramfs -u
+ sudoedit /etc/default/grub
+ #remove 'splash' from GRUB_CMDLINE_LINUX_DEFAULT, and save with the default 
name
+ sudo update-grub
+ #reboot the system
+ 
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331 331.38-0ubuntu7
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu May  1 22:08:36 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-01-25 (827 days ago)
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  SourcePackage: nvidia-graphics-drivers-331
  UpgradeStatus: Upgraded to trusty on 2014-04-29 (2 days ago)
  modified.conffile..etc.modprobe.d.nvidia.331.hybrid.conf: [deleted]

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

Title:
  nvidia-331 selected but nouveau loads

Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  New
Status in “xserver-xorg-video-nouveau” package in Ubuntu:
  New

Bug description:
  After upgrading to Trusty, I briefly used the nouveau driver to check
  whether bug 1243557 still existed; after finding that it did, I
  switched back to nvidia-331.

  However since then, frequently (50% but not always), the system loads
  nouveau first, then fails to load nvidia-331 because of this:

  Apr 30 08:00:29 lap14 kernel: [   17.789267] nouveau  [  
DEVICE][:01:00.0] BOOT0  : 0x0d9160a1
  Apr 30 08:00:29 lap14 kernel: [   17.789269] nouveau  [  
DEVICE][:01:00.0] Chipset: GF119 (NVD9)
  Apr 30 08:00:29 lap14 kernel: [   17.789271] nouveau  [  
DEVICE][:01:00.0] Family : NVD0
  [...]
  Apr 30 08:00:32 lap14 kernel: [   21.574983] NVRM: The NVIDIA probe routine 
was not called for 1 device(s).
  Apr 30 08:00:32 lap14 kernel: [   21.574987] NVRM: This can occur when a 
driver such as: 
  Apr 30 08:00:32 lap14 kernel: [   21.574987] NVRM: nouveau, rivafb, nvidiafb 
or rivatv 
  Apr 30 08:00:32 lap14 kernel: [   21.574987] NVRM: was loaded and obtained 
ownership of the NVIDIA device(s).

  WORKAROUND: at a text terminal:
  sudo apt-get purge nvidia-331
  sudo apt-get install nvidia-331
  sudo update-initramfs -u
  sudoedit /etc/default/grub
  #remove 'splash' from GRUB_CMDLINE_LINUX_DEFAULT, and save with the default 
name
  sudo update-grub
  #reboot the system

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331 331.38-0ubuntu7
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu May  1 22:08:36 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-01-25 (827 days ago)
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  SourcePackage: nvidia-graphics-drivers-331
  UpgradeStatus: Upgraded to trusty on 2014-04-29 (2 days ago)
  modified.conffile..etc.modprobe.d.nvidia.331.hybrid.conf: [deleted]

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1315156] Re: nvidia-331 selected but nouveau loads

2014-05-06 Thread Rebecca Palmer 
The NVRM log messages stopped after reinstalling nvidia-331, but the
system continued to use nouveau, and hence to crash (bug 1243557).

 modified.conffile..etc.modprobe.d.nvidia.331.hybrid.conf: [deleted]

I don't know how that (which blacklists nouveau) came to be missing, but
purging and re-installing nvidia-331 put it back but didn't stop nouveau
loading.

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

Title:
  nvidia-331 selected but nouveau loads

Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  New
Status in “xserver-xorg-video-nouveau” package in Ubuntu:
  New

Bug description:
  After upgrading to Trusty, I briefly used the nouveau driver to check
  whether bug 1243557 still existed; after finding that it did, I
  switched back to nvidia-331.

  However since then, frequently (50% but not always), the system loads
  nouveau first, then fails to load nvidia-331 because of this:

  Apr 30 08:00:29 lap14 kernel: [   17.789267] nouveau  [  
DEVICE][:01:00.0] BOOT0  : 0x0d9160a1
  Apr 30 08:00:29 lap14 kernel: [   17.789269] nouveau  [  
DEVICE][:01:00.0] Chipset: GF119 (NVD9)
  Apr 30 08:00:29 lap14 kernel: [   17.789271] nouveau  [  
DEVICE][:01:00.0] Family : NVD0
  [...]
  Apr 30 08:00:32 lap14 kernel: [   21.574983] NVRM: The NVIDIA probe routine 
was not called for 1 device(s).
  Apr 30 08:00:32 lap14 kernel: [   21.574987] NVRM: This can occur when a 
driver such as: 
  Apr 30 08:00:32 lap14 kernel: [   21.574987] NVRM: nouveau, rivafb, nvidiafb 
or rivatv 
  Apr 30 08:00:32 lap14 kernel: [   21.574987] NVRM: was loaded and obtained 
ownership of the NVIDIA device(s).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331 331.38-0ubuntu7
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu May  1 22:08:36 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-01-25 (827 days ago)
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  SourcePackage: nvidia-graphics-drivers-331
  UpgradeStatus: Upgraded to trusty on 2014-04-29 (2 days ago)
  modified.conffile..etc.modprobe.d.nvidia.331.hybrid.conf: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1315156/+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 1315156] [NEW] nvidia-331 selected but nouveau loads

2014-05-01 Thread Rebecca Palmer 
Public bug reported:

After upgrading to Trusty, I briefly used the nouveau driver to check
whether bug 1243557 still existed; after finding that it did, I switched
back to nvidia-331.

However since then, frequently (50% but not always), the system loads
nouveau first, then fails to load nvidia-331 because of this:

Apr 30 08:00:29 lap14 kernel: [   17.789267] nouveau  [  DEVICE][:01:00.0] 
BOOT0  : 0x0d9160a1
Apr 30 08:00:29 lap14 kernel: [   17.789269] nouveau  [  DEVICE][:01:00.0] 
Chipset: GF119 (NVD9)
Apr 30 08:00:29 lap14 kernel: [   17.789271] nouveau  [  DEVICE][:01:00.0] 
Family : NVD0
[...]
Apr 30 08:00:32 lap14 kernel: [   21.574983] NVRM: The NVIDIA probe routine was 
not called for 1 device(s).
Apr 30 08:00:32 lap14 kernel: [   21.574987] NVRM: This can occur when a driver 
such as: 
Apr 30 08:00:32 lap14 kernel: [   21.574987] NVRM: nouveau, rivafb, nvidiafb or 
rivatv 
Apr 30 08:00:32 lap14 kernel: [   21.574987] NVRM: was loaded and obtained 
ownership of the NVIDIA device(s).

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: nvidia-331 331.38-0ubuntu7
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
Date: Thu May  1 22:08:36 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2012-01-25 (827 days ago)
InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
SourcePackage: nvidia-graphics-drivers-331
UpgradeStatus: Upgraded to trusty on 2014-04-29 (2 days ago)
modified.conffile..etc.modprobe.d.nvidia.331.hybrid.conf: [deleted]

** Affects: nvidia-graphics-drivers-331 (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: xserver-xorg-video-nouveau (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug trusty

** Also affects: xserver-xorg-video-nouveau (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  nvidia-331 selected but nouveau loads

Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  New
Status in “xserver-xorg-video-nouveau” package in Ubuntu:
  New

Bug description:
  After upgrading to Trusty, I briefly used the nouveau driver to check
  whether bug 1243557 still existed; after finding that it did, I
  switched back to nvidia-331.

  However since then, frequently (50% but not always), the system loads
  nouveau first, then fails to load nvidia-331 because of this:

  Apr 30 08:00:29 lap14 kernel: [   17.789267] nouveau  [  
DEVICE][:01:00.0] BOOT0  : 0x0d9160a1
  Apr 30 08:00:29 lap14 kernel: [   17.789269] nouveau  [  
DEVICE][:01:00.0] Chipset: GF119 (NVD9)
  Apr 30 08:00:29 lap14 kernel: [   17.789271] nouveau  [  
DEVICE][:01:00.0] Family : NVD0
  [...]
  Apr 30 08:00:32 lap14 kernel: [   21.574983] NVRM: The NVIDIA probe routine 
was not called for 1 device(s).
  Apr 30 08:00:32 lap14 kernel: [   21.574987] NVRM: This can occur when a 
driver such as: 
  Apr 30 08:00:32 lap14 kernel: [   21.574987] NVRM: nouveau, rivafb, nvidiafb 
or rivatv 
  Apr 30 08:00:32 lap14 kernel: [   21.574987] NVRM: was loaded and obtained 
ownership of the NVIDIA device(s).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331 331.38-0ubuntu7
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu May  1 22:08:36 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-01-25 (827 days ago)
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  SourcePackage: nvidia-graphics-drivers-331
  UpgradeStatus: Upgraded to trusty on 2014-04-29 (2 days ago)
  modified.conffile..etc.modprobe.d.nvidia.331.hybrid.conf: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1315156/+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 1315156] Re: nvidia-331 selected but nouveau loads

2014-05-01 Thread Rebecca Palmer 
** Attachment added: kern.log
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1315156/+attachment/4102693/+files/kern.log

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

Title:
  nvidia-331 selected but nouveau loads

Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  New
Status in “xserver-xorg-video-nouveau” package in Ubuntu:
  New

Bug description:
  After upgrading to Trusty, I briefly used the nouveau driver to check
  whether bug 1243557 still existed; after finding that it did, I
  switched back to nvidia-331.

  However since then, frequently (50% but not always), the system loads
  nouveau first, then fails to load nvidia-331 because of this:

  Apr 30 08:00:29 lap14 kernel: [   17.789267] nouveau  [  
DEVICE][:01:00.0] BOOT0  : 0x0d9160a1
  Apr 30 08:00:29 lap14 kernel: [   17.789269] nouveau  [  
DEVICE][:01:00.0] Chipset: GF119 (NVD9)
  Apr 30 08:00:29 lap14 kernel: [   17.789271] nouveau  [  
DEVICE][:01:00.0] Family : NVD0
  [...]
  Apr 30 08:00:32 lap14 kernel: [   21.574983] NVRM: The NVIDIA probe routine 
was not called for 1 device(s).
  Apr 30 08:00:32 lap14 kernel: [   21.574987] NVRM: This can occur when a 
driver such as: 
  Apr 30 08:00:32 lap14 kernel: [   21.574987] NVRM: nouveau, rivafb, nvidiafb 
or rivatv 
  Apr 30 08:00:32 lap14 kernel: [   21.574987] NVRM: was loaded and obtained 
ownership of the NVIDIA device(s).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331 331.38-0ubuntu7
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu May  1 22:08:36 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-01-25 (827 days ago)
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  SourcePackage: nvidia-graphics-drivers-331
  UpgradeStatus: Upgraded to trusty on 2014-04-29 (2 days ago)
  modified.conffile..etc.modprobe.d.nvidia.331.hybrid.conf: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1315156/+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 1174205] Re: Using pyopencl doesn't work and spits our ImportError

2014-05-01 Thread Rebecca Palmer 
Fixed in Trusty: pyopencl now depends on a new virtual libopencl-1.2-1,
which forces selection of a libopencl1 it will work with.  (opencl-icd
still needs to be chosen manually to match the hardware, but that's bug
1264844)

** Changed in: pyopencl (Ubuntu)
   Status: Confirmed = Fix Released

** Changed in: nvidia-graphics-drivers-319 (Ubuntu)
   Status: Confirmed = Fix Released

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

Title:
  Using pyopencl doesn't work and spits our ImportError

Status in “fglrx-installer” package in Ubuntu:
  Confirmed
Status in “nvidia-graphics-drivers-319” package in Ubuntu:
  Fix Released
Status in “pyopencl” package in Ubuntu:
  Fix Released

Bug description:
  Pyopencl doesn't work on raging, the following error message is
  generated:

  Python 2.7.4 (default, Apr 19 2013, 18:32:33)
  [GCC 4.7.3] on linux2
  Type help, copyright, credits or license for more information.
   import pyopencl
  Traceback (most recent call last):
    File stdin, line 1, in module
    File /usr/lib/python2.7/dist-packages/pyopencl/__init__.py, line 4, in 
module
  import pyopencl._cl as _cl
  ImportError: /usr/lib/python2.7/dist-packages/pyopencl/_cl.so: symbol 
clRetainDevice, version OPENCL_1.2 not defined in file libOpenCL.so.1 with link 
time reference

  I am using the following drivers:
  adrian@toad:~$ dpkg -l | grep nvidia
  ii  nvidia-304-updates304.88-0ubuntu2 
i386 NVIDIA binary Xorg driver, kernel module and VDPAU 
library
  ii  nvidia-cg-dev:i3863.1.0013-1  
i386 Cg Toolkit - GPU Shader Authoring Language (headers)
  ii  nvidia-cg-toolkit 3.1.0013-1  
i386 Cg Toolkit - GPU Shader Authoring Language
  ii  nvidia-common 1:0.2.76
i386 transitional package for ubuntu-drivers-common
  ii  nvidia-settings-304-updates   304.88-0ubuntu1 
i386 Tool for configuring the NVIDIA graphics driver


  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: python-pyopencl 2012.1-1ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  Uname: Linux 3.8.0-19-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: i386
  Date: Mon Apr 29 09:56:38 2013
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_ZA.UTF-8
   SHELL=/bin/bash
  SourcePackage: pyopencl
  UpgradeStatus: Upgraded to raring on 2013-04-27 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1174205/+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 1243557]

2014-03-31 Thread Rebecca Palmer 
Created attachment 96611
Xorg log 3.14rc-Mar-26

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

Title:
  10de:1056 [Dell Latitude E6520] [NVS 4200M] X freeze, unhandled
  status 0x0080

Status in Accelerated Xorg driver for nVidia cards:
  Confirmed
Status in “xserver-xorg-video-nouveau” package in Ubuntu:
  Triaged

Bug description:
  With the Nouveau driver selected, my system freezes within a few
  minutes of boot if on battery, but only on heavy graphics load
  (flightgear in maximized window) if on mains. The mouse pointer still
  moves at first, but often freezes later; the keyboard LEDs do not
  react. Sounds already playing continue until finished, but don't
  repeat if set to (i.e. applications are frozen). Alt+SysRq works
  (provided bug 1244312 is fixed first).

  The kernel log nearly always contains the line
  nouveau ![   PFIFO][:01:00.0] unhandled status 0x0080

  and sometimes other errors as well, while the Xorg log often contains
  EQ overflow errors; the full logs are attached.

  WORKAROUND: This does not occur with the nvidia-319 driver.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  319.32  Wed Jun 19 15:51:20 
PDT 2013
   GCC version:  gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu8)
  .tmp.unity.support.test.0:

  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Oct 23 08:19:06 2013
  DistUpgraded: 2013-10-21 23:03:05,341 DEBUG enabling apt cron job
  DistroCodename: saucy
  DistroVariant: ubuntu
  DkmsStatus: nvidia-319, 319.32, 3.11.0-12-generic, x86_64: installed
  EcryptfsInUse: Yes
  GraphicsCard:
   NVIDIA Corporation GF119M [NVS 4200M] [10de:1056] (rev a1) (prog-if 00 [VGA 
controller])
     Subsystem: Dell Device [1028:0494]
  InstallationDate: Installed on 2012-01-25 (636 days ago)
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  JockeyStatus:
   kmod:nvidia_319_updates - NVIDIA binary Xorg driver, kernel module and VDPAU 
library (Proprietary, Disabled, Not in use)
   kmod:wl - Broadcom STA wireless driver (Proprietary, Disabled, Not in use) 
[auto-install]
   kmod:nvidia_304 - NVIDIA binary Xorg driver, kernel module and VDPAU library 
(Proprietary, Disabled, Not in use)
   kmod:nvidia_304_updates - NVIDIA binary Xorg driver, kernel module and VDPAU 
library (Proprietary, Disabled, Not in use)
   kmod:nvidia_319 - nvidia_319 (Proprietary, Enabled, Not in use)
  MachineType: Dell Inc. Latitude E6520
  MarkForUpload: True
  PlymouthDebug: Error: [Errno 13] Permission denied: 
'/var/log/plymouth-debug.log'
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=b491a34a-6045-4ad4-a2b8-b9ca018c5d41 ro quiet splash
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: Upgraded to saucy on 2013-10-21 (1 days ago)
  XorgConf:
   Section Device
    Identifier  Default Device
    Option  NoLogoTrue
   EndSection
  dmi.bios.date: 10/18/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0J4TFW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd10/18/2011:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0J4TFW:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6520
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.46-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.9-2ubuntu1

[Desktop-packages] [Bug 1243557]

2014-03-31 Thread Rebecca Palmer 
This bug still exists in 3.14rc commit
f217c44ebd41ce7369d2df07622b2839479183b0 (26 Mar Linus' tree, Ubuntu
userspace; as the nouveau/master branch hasn't been used for 5 months,
should we stop suggesting that people test with it?).

Is there anything else I can do to help?  I will probably only have this
machine for a few more months.

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

Title:
  10de:1056 [Dell Latitude E6520] [NVS 4200M] X freeze, unhandled
  status 0x0080

Status in Accelerated Xorg driver for nVidia cards:
  Confirmed
Status in “xserver-xorg-video-nouveau” package in Ubuntu:
  Triaged

Bug description:
  With the Nouveau driver selected, my system freezes within a few
  minutes of boot if on battery, but only on heavy graphics load
  (flightgear in maximized window) if on mains. The mouse pointer still
  moves at first, but often freezes later; the keyboard LEDs do not
  react. Sounds already playing continue until finished, but don't
  repeat if set to (i.e. applications are frozen). Alt+SysRq works
  (provided bug 1244312 is fixed first).

  The kernel log nearly always contains the line
  nouveau ![   PFIFO][:01:00.0] unhandled status 0x0080

  and sometimes other errors as well, while the Xorg log often contains
  EQ overflow errors; the full logs are attached.

  WORKAROUND: This does not occur with the nvidia-319 driver.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  319.32  Wed Jun 19 15:51:20 
PDT 2013
   GCC version:  gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu8)
  .tmp.unity.support.test.0:

  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Oct 23 08:19:06 2013
  DistUpgraded: 2013-10-21 23:03:05,341 DEBUG enabling apt cron job
  DistroCodename: saucy
  DistroVariant: ubuntu
  DkmsStatus: nvidia-319, 319.32, 3.11.0-12-generic, x86_64: installed
  EcryptfsInUse: Yes
  GraphicsCard:
   NVIDIA Corporation GF119M [NVS 4200M] [10de:1056] (rev a1) (prog-if 00 [VGA 
controller])
     Subsystem: Dell Device [1028:0494]
  InstallationDate: Installed on 2012-01-25 (636 days ago)
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  JockeyStatus:
   kmod:nvidia_319_updates - NVIDIA binary Xorg driver, kernel module and VDPAU 
library (Proprietary, Disabled, Not in use)
   kmod:wl - Broadcom STA wireless driver (Proprietary, Disabled, Not in use) 
[auto-install]
   kmod:nvidia_304 - NVIDIA binary Xorg driver, kernel module and VDPAU library 
(Proprietary, Disabled, Not in use)
   kmod:nvidia_304_updates - NVIDIA binary Xorg driver, kernel module and VDPAU 
library (Proprietary, Disabled, Not in use)
   kmod:nvidia_319 - nvidia_319 (Proprietary, Enabled, Not in use)
  MachineType: Dell Inc. Latitude E6520
  MarkForUpload: True
  PlymouthDebug: Error: [Errno 13] Permission denied: 
'/var/log/plymouth-debug.log'
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=b491a34a-6045-4ad4-a2b8-b9ca018c5d41 ro quiet splash
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: Upgraded to saucy on 2013-10-21 (1 days ago)
  XorgConf:
   Section Device
    Identifier  Default Device
    Option  NoLogoTrue
   EndSection
  dmi.bios.date: 10/18/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0J4TFW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd10/18/2011:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0J4TFW:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6520
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.46-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu2
  version.xserver-xorg-input-evdev:

[Desktop-packages] [Bug 1243557]

2014-03-31 Thread Rebecca Palmer 
Created attachment 96610
kernel log 3.14rc-Mar-26

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

Title:
  10de:1056 [Dell Latitude E6520] [NVS 4200M] X freeze, unhandled
  status 0x0080

Status in Accelerated Xorg driver for nVidia cards:
  Confirmed
Status in “xserver-xorg-video-nouveau” package in Ubuntu:
  Triaged

Bug description:
  With the Nouveau driver selected, my system freezes within a few
  minutes of boot if on battery, but only on heavy graphics load
  (flightgear in maximized window) if on mains. The mouse pointer still
  moves at first, but often freezes later; the keyboard LEDs do not
  react. Sounds already playing continue until finished, but don't
  repeat if set to (i.e. applications are frozen). Alt+SysRq works
  (provided bug 1244312 is fixed first).

  The kernel log nearly always contains the line
  nouveau ![   PFIFO][:01:00.0] unhandled status 0x0080

  and sometimes other errors as well, while the Xorg log often contains
  EQ overflow errors; the full logs are attached.

  WORKAROUND: This does not occur with the nvidia-319 driver.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  319.32  Wed Jun 19 15:51:20 
PDT 2013
   GCC version:  gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu8)
  .tmp.unity.support.test.0:

  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Oct 23 08:19:06 2013
  DistUpgraded: 2013-10-21 23:03:05,341 DEBUG enabling apt cron job
  DistroCodename: saucy
  DistroVariant: ubuntu
  DkmsStatus: nvidia-319, 319.32, 3.11.0-12-generic, x86_64: installed
  EcryptfsInUse: Yes
  GraphicsCard:
   NVIDIA Corporation GF119M [NVS 4200M] [10de:1056] (rev a1) (prog-if 00 [VGA 
controller])
     Subsystem: Dell Device [1028:0494]
  InstallationDate: Installed on 2012-01-25 (636 days ago)
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  JockeyStatus:
   kmod:nvidia_319_updates - NVIDIA binary Xorg driver, kernel module and VDPAU 
library (Proprietary, Disabled, Not in use)
   kmod:wl - Broadcom STA wireless driver (Proprietary, Disabled, Not in use) 
[auto-install]
   kmod:nvidia_304 - NVIDIA binary Xorg driver, kernel module and VDPAU library 
(Proprietary, Disabled, Not in use)
   kmod:nvidia_304_updates - NVIDIA binary Xorg driver, kernel module and VDPAU 
library (Proprietary, Disabled, Not in use)
   kmod:nvidia_319 - nvidia_319 (Proprietary, Enabled, Not in use)
  MachineType: Dell Inc. Latitude E6520
  MarkForUpload: True
  PlymouthDebug: Error: [Errno 13] Permission denied: 
'/var/log/plymouth-debug.log'
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=b491a34a-6045-4ad4-a2b8-b9ca018c5d41 ro quiet splash
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: Upgraded to saucy on 2013-10-21 (1 days ago)
  XorgConf:
   Section Device
    Identifier  Default Device
    Option  NoLogoTrue
   EndSection
  dmi.bios.date: 10/18/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0J4TFW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd10/18/2011:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0J4TFW:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6520
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.46-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.9-2ubuntu1

[Desktop-packages] [Bug 1243557]

2014-01-20 Thread Rebecca Palmer 
Created attachment 92127
kernel log 3.13rc+firmware

What does not in the initrd mean?  The files were in
/lib/firmware/nouveau with the names the script gave them (nvd9_fuc*).

The errors with kernel 3.13-rc7 (attached) are similar:
Jan 13 22:47:57 lap14 kernel: [1.653189] nouveau  [  PGRAPH][:01:00.0] 
using external firmware
Jan 13 22:47:57 lap14 kernel: [1.653203] nouveau :01:00.0: Direct 
firmware load failed with error -2
Jan 13 22:47:57 lap14 kernel: [1.653204] nouveau :01:00.0: Falling back 
to user helper
Jan 13 22:47:57 lap14 kernel: [1.653447] nouveau :01:00.0: Direct 
firmware load failed with error -2
Jan 13 22:47:57 lap14 kernel: [1.653452] nouveau :01:00.0: Falling back 
to user helper
Jan 13 22:47:57 lap14 kernel: [1.653651] nouveau E[  PGRAPH][:01:00.0] 
failed to load fuc409c
Jan 13 22:47:57 lap14 kernel: [1.653658] nouveau E[  DEVICE][:01:00.0] 
failed to create 0x1800d916, -22
Jan 13 22:47:57 lap14 kernel: [1.653663] nouveau E[ DRM] failed to 
create 0x8080, -22
Jan 13 22:47:57 lap14 kernel: [1.654258] nouveau: probe of :01:00.0 
failed with error -22

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

Title:
  10de:1056 [Dell Latitude E6520] [NVS 4200M] X freeze, unhandled
  status 0x0080

Status in Accelerated Xorg driver for nVidia cards:
  Confirmed
Status in “xserver-xorg-video-nouveau” package in Ubuntu:
  Triaged

Bug description:
  With the Nouveau driver selected, my system freezes within a few
  minutes of boot if on battery, but only on heavy graphics load
  (flightgear in maximized window) if on mains. The mouse pointer still
  moves at first, but often freezes later; the keyboard LEDs do not
  react. Sounds already playing continue until finished, but don't
  repeat if set to (i.e. applications are frozen). Alt+SysRq works
  (provided bug 1244312 is fixed first).

  The kernel log nearly always contains the line
  nouveau ![   PFIFO][:01:00.0] unhandled status 0x0080

  and sometimes other errors as well, while the Xorg log often contains
  EQ overflow errors; the full logs are attached.

  WORKAROUND: This does not occur with the nvidia-319 driver.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  319.32  Wed Jun 19 15:51:20 
PDT 2013
   GCC version:  gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu8)
  .tmp.unity.support.test.0:

  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Oct 23 08:19:06 2013
  DistUpgraded: 2013-10-21 23:03:05,341 DEBUG enabling apt cron job
  DistroCodename: saucy
  DistroVariant: ubuntu
  DkmsStatus: nvidia-319, 319.32, 3.11.0-12-generic, x86_64: installed
  EcryptfsInUse: Yes
  GraphicsCard:
   NVIDIA Corporation GF119M [NVS 4200M] [10de:1056] (rev a1) (prog-if 00 [VGA 
controller])
     Subsystem: Dell Device [1028:0494]
  InstallationDate: Installed on 2012-01-25 (636 days ago)
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  JockeyStatus:
   kmod:nvidia_319_updates - NVIDIA binary Xorg driver, kernel module and VDPAU 
library (Proprietary, Disabled, Not in use)
   kmod:wl - Broadcom STA wireless driver (Proprietary, Disabled, Not in use) 
[auto-install]
   kmod:nvidia_304 - NVIDIA binary Xorg driver, kernel module and VDPAU library 
(Proprietary, Disabled, Not in use)
   kmod:nvidia_304_updates - NVIDIA binary Xorg driver, kernel module and VDPAU 
library (Proprietary, Disabled, Not in use)
   kmod:nvidia_319 - nvidia_319 (Proprietary, Enabled, Not in use)
  MachineType: Dell Inc. Latitude E6520
  MarkForUpload: True
  PlymouthDebug: Error: [Errno 13] Permission denied: 
'/var/log/plymouth-debug.log'
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=b491a34a-6045-4ad4-a2b8-b9ca018c5d41 ro quiet splash
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: Upgraded to saucy on 2013-10-21 (1 days ago)
  XorgConf:
   Section Device
    Identifier  Default Device
    Option  NoLogoTrue
   EndSection
  dmi.bios.date: 10/18/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0J4TFW

[Desktop-packages] [Bug 1243557]

2014-01-20 Thread Rebecca Palmer 
Your script, and kernel 3.13-rc7 with either the nvd9 or nvd7
firmware also gives a blank screen.

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

Title:
  10de:1056 [Dell Latitude E6520] [NVS 4200M] X freeze, unhandled
  status 0x0080

Status in Accelerated Xorg driver for nVidia cards:
  Confirmed
Status in “xserver-xorg-video-nouveau” package in Ubuntu:
  Triaged

Bug description:
  With the Nouveau driver selected, my system freezes within a few
  minutes of boot if on battery, but only on heavy graphics load
  (flightgear in maximized window) if on mains. The mouse pointer still
  moves at first, but often freezes later; the keyboard LEDs do not
  react. Sounds already playing continue until finished, but don't
  repeat if set to (i.e. applications are frozen). Alt+SysRq works
  (provided bug 1244312 is fixed first).

  The kernel log nearly always contains the line
  nouveau ![   PFIFO][:01:00.0] unhandled status 0x0080

  and sometimes other errors as well, while the Xorg log often contains
  EQ overflow errors; the full logs are attached.

  WORKAROUND: This does not occur with the nvidia-319 driver.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  319.32  Wed Jun 19 15:51:20 
PDT 2013
   GCC version:  gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu8)
  .tmp.unity.support.test.0:

  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Oct 23 08:19:06 2013
  DistUpgraded: 2013-10-21 23:03:05,341 DEBUG enabling apt cron job
  DistroCodename: saucy
  DistroVariant: ubuntu
  DkmsStatus: nvidia-319, 319.32, 3.11.0-12-generic, x86_64: installed
  EcryptfsInUse: Yes
  GraphicsCard:
   NVIDIA Corporation GF119M [NVS 4200M] [10de:1056] (rev a1) (prog-if 00 [VGA 
controller])
     Subsystem: Dell Device [1028:0494]
  InstallationDate: Installed on 2012-01-25 (636 days ago)
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  JockeyStatus:
   kmod:nvidia_319_updates - NVIDIA binary Xorg driver, kernel module and VDPAU 
library (Proprietary, Disabled, Not in use)
   kmod:wl - Broadcom STA wireless driver (Proprietary, Disabled, Not in use) 
[auto-install]
   kmod:nvidia_304 - NVIDIA binary Xorg driver, kernel module and VDPAU library 
(Proprietary, Disabled, Not in use)
   kmod:nvidia_304_updates - NVIDIA binary Xorg driver, kernel module and VDPAU 
library (Proprietary, Disabled, Not in use)
   kmod:nvidia_319 - nvidia_319 (Proprietary, Enabled, Not in use)
  MachineType: Dell Inc. Latitude E6520
  MarkForUpload: True
  PlymouthDebug: Error: [Errno 13] Permission denied: 
'/var/log/plymouth-debug.log'
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=b491a34a-6045-4ad4-a2b8-b9ca018c5d41 ro quiet splash
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: Upgraded to saucy on 2013-10-21 (1 days ago)
  XorgConf:
   Section Device
    Identifier  Default Device
    Option  NoLogoTrue
   EndSection
  dmi.bios.date: 10/18/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0J4TFW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd10/18/2011:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0J4TFW:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6520
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.46-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2
  version.xserver-xorg-video-nouveau:

[Desktop-packages] [Bug 1243557]

2014-01-20 Thread Rebecca Palmer 
It still doesn't find the firmware after updating the initramfs (sudo
update-initramfs -u -k all), whether it is placed at
/lib/firmware/nouveau/nvd9_fuc*, /lib/firmware/nouveau/fuc*,
/lib/firmware/kernel_version/nouveau/nvd9_fuc* or
/lib/firmware/kernel_version/nouveau/fuc*.  (The script uses nvd9_fuc*
but http://nouveau.freedesktop.org/wiki/NVC0_Firmware/ says just fuc*
for pre-NVE0 cards.)

My 3.13-rc7 test kernel was compiled with the procedure in 
https://wiki.ubuntu.com/KernelTeam/GitKernelBuild; the .config lines containing 
nouveau are
CONFIG_DRM_NOUVEAU=m
CONFIG_NOUVEAU_DEBUG=5
CONFIG_NOUVEAU_DEBUG_DEFAULT=3
CONFIG_DRM_NOUVEAU_BACKLIGHT=y
and kernel/drivers/gpu/drm/nouveau/nouveau.ko is on the modules.order list, not 
the modules.builtin list.

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

Title:
  10de:1056 [Dell Latitude E6520] [NVS 4200M] X freeze, unhandled
  status 0x0080

Status in Accelerated Xorg driver for nVidia cards:
  Confirmed
Status in “xserver-xorg-video-nouveau” package in Ubuntu:
  Triaged

Bug description:
  With the Nouveau driver selected, my system freezes within a few
  minutes of boot if on battery, but only on heavy graphics load
  (flightgear in maximized window) if on mains. The mouse pointer still
  moves at first, but often freezes later; the keyboard LEDs do not
  react. Sounds already playing continue until finished, but don't
  repeat if set to (i.e. applications are frozen). Alt+SysRq works
  (provided bug 1244312 is fixed first).

  The kernel log nearly always contains the line
  nouveau ![   PFIFO][:01:00.0] unhandled status 0x0080

  and sometimes other errors as well, while the Xorg log often contains
  EQ overflow errors; the full logs are attached.

  WORKAROUND: This does not occur with the nvidia-319 driver.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  319.32  Wed Jun 19 15:51:20 
PDT 2013
   GCC version:  gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu8)
  .tmp.unity.support.test.0:

  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Oct 23 08:19:06 2013
  DistUpgraded: 2013-10-21 23:03:05,341 DEBUG enabling apt cron job
  DistroCodename: saucy
  DistroVariant: ubuntu
  DkmsStatus: nvidia-319, 319.32, 3.11.0-12-generic, x86_64: installed
  EcryptfsInUse: Yes
  GraphicsCard:
   NVIDIA Corporation GF119M [NVS 4200M] [10de:1056] (rev a1) (prog-if 00 [VGA 
controller])
     Subsystem: Dell Device [1028:0494]
  InstallationDate: Installed on 2012-01-25 (636 days ago)
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  JockeyStatus:
   kmod:nvidia_319_updates - NVIDIA binary Xorg driver, kernel module and VDPAU 
library (Proprietary, Disabled, Not in use)
   kmod:wl - Broadcom STA wireless driver (Proprietary, Disabled, Not in use) 
[auto-install]
   kmod:nvidia_304 - NVIDIA binary Xorg driver, kernel module and VDPAU library 
(Proprietary, Disabled, Not in use)
   kmod:nvidia_304_updates - NVIDIA binary Xorg driver, kernel module and VDPAU 
library (Proprietary, Disabled, Not in use)
   kmod:nvidia_319 - nvidia_319 (Proprietary, Enabled, Not in use)
  MachineType: Dell Inc. Latitude E6520
  MarkForUpload: True
  PlymouthDebug: Error: [Errno 13] Permission denied: 
'/var/log/plymouth-debug.log'
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=b491a34a-6045-4ad4-a2b8-b9ca018c5d41 ro quiet splash
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: Upgraded to saucy on 2013-10-21 (1 days ago)
  XorgConf:
   Section Device
    Identifier  Default Device
    Option  NoLogoTrue
   EndSection
  dmi.bios.date: 10/18/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0J4TFW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd10/18/2011:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0J4TFW:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6520
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1

[Desktop-packages] [Bug 1243557]

2014-01-13 Thread Rebecca Palmer 
Created attachment 91782
Ubuntu 14.04 (Linux 3.13.0) log

This bug is easier to trigger in Ubuntu Trusty (kernel 3.13.0, libdrm-
nouveau2 2.4.50, xserver-xorg-video-nouveau 1.0.10, mesa 10.0.1),
occurring immediately on heavy graphics load and within a few minutes
even in ordinary use.

The attached log contains more instances of the warning than were normal
in 13.10, but not the final error (I suspect it wasn't synced to disk).

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

Title:
  10de:1056 [Dell Latitude E6520] [NVS 4200M] X freeze, unhandled
  status 0x0080

Status in Accelerated Xorg driver for nVidia cards:
  Confirmed
Status in “xserver-xorg-video-nouveau” package in Ubuntu:
  Triaged

Bug description:
  With the Nouveau driver selected, my system freezes within a few
  minutes of boot if on battery, but only on heavy graphics load
  (flightgear in maximized window) if on mains. The mouse pointer still
  moves at first, but often freezes later; the keyboard LEDs do not
  react. Sounds already playing continue until finished, but don't
  repeat if set to (i.e. applications are frozen). Alt+SysRq works
  (provided bug 1244312 is fixed first).

  The kernel log nearly always contains the line
  nouveau ![   PFIFO][:01:00.0] unhandled status 0x0080

  and sometimes other errors as well, while the Xorg log often contains
  EQ overflow errors; the full logs are attached.

  WORKAROUND: This does not occur with the nvidia-319 driver.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  319.32  Wed Jun 19 15:51:20 
PDT 2013
   GCC version:  gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu8)
  .tmp.unity.support.test.0:

  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Oct 23 08:19:06 2013
  DistUpgraded: 2013-10-21 23:03:05,341 DEBUG enabling apt cron job
  DistroCodename: saucy
  DistroVariant: ubuntu
  DkmsStatus: nvidia-319, 319.32, 3.11.0-12-generic, x86_64: installed
  EcryptfsInUse: Yes
  GraphicsCard:
   NVIDIA Corporation GF119M [NVS 4200M] [10de:1056] (rev a1) (prog-if 00 [VGA 
controller])
     Subsystem: Dell Device [1028:0494]
  InstallationDate: Installed on 2012-01-25 (636 days ago)
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  JockeyStatus:
   kmod:nvidia_319_updates - NVIDIA binary Xorg driver, kernel module and VDPAU 
library (Proprietary, Disabled, Not in use)
   kmod:wl - Broadcom STA wireless driver (Proprietary, Disabled, Not in use) 
[auto-install]
   kmod:nvidia_304 - NVIDIA binary Xorg driver, kernel module and VDPAU library 
(Proprietary, Disabled, Not in use)
   kmod:nvidia_304_updates - NVIDIA binary Xorg driver, kernel module and VDPAU 
library (Proprietary, Disabled, Not in use)
   kmod:nvidia_319 - nvidia_319 (Proprietary, Enabled, Not in use)
  MachineType: Dell Inc. Latitude E6520
  MarkForUpload: True
  PlymouthDebug: Error: [Errno 13] Permission denied: 
'/var/log/plymouth-debug.log'
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=b491a34a-6045-4ad4-a2b8-b9ca018c5d41 ro quiet splash
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: Upgraded to saucy on 2013-10-21 (1 days ago)
  XorgConf:
   Section Device
    Identifier  Default Device
    Option  NoLogoTrue
   EndSection
  dmi.bios.date: 10/18/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0J4TFW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd10/18/2011:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0J4TFW:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6520
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.46-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A

[Desktop-packages] [Bug 1243557]

2014-01-13 Thread Rebecca Palmer 
Created attachment 91842
kernel log 3.13rc7 and 3.11+firmware

The 3.13-rc7 upstream kernel in Ubuntu 13.10 also sometimes crashes, but
not as often as the near-identical kernel in Trusty; this might mean the
regression is in userspace, or might be the same persistence (presumably
a left-behind configuration change from 3.12) we saw earlier.

The blob firmware (in the standard 3.11 kernel) turns the login screen
blank, with no recognisable error in the log.

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

Title:
  10de:1056 [Dell Latitude E6520] [NVS 4200M] X freeze, unhandled
  status 0x0080

Status in Accelerated Xorg driver for nVidia cards:
  Confirmed
Status in “xserver-xorg-video-nouveau” package in Ubuntu:
  Triaged

Bug description:
  With the Nouveau driver selected, my system freezes within a few
  minutes of boot if on battery, but only on heavy graphics load
  (flightgear in maximized window) if on mains. The mouse pointer still
  moves at first, but often freezes later; the keyboard LEDs do not
  react. Sounds already playing continue until finished, but don't
  repeat if set to (i.e. applications are frozen). Alt+SysRq works
  (provided bug 1244312 is fixed first).

  The kernel log nearly always contains the line
  nouveau ![   PFIFO][:01:00.0] unhandled status 0x0080

  and sometimes other errors as well, while the Xorg log often contains
  EQ overflow errors; the full logs are attached.

  WORKAROUND: This does not occur with the nvidia-319 driver.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  319.32  Wed Jun 19 15:51:20 
PDT 2013
   GCC version:  gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu8)
  .tmp.unity.support.test.0:

  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Oct 23 08:19:06 2013
  DistUpgraded: 2013-10-21 23:03:05,341 DEBUG enabling apt cron job
  DistroCodename: saucy
  DistroVariant: ubuntu
  DkmsStatus: nvidia-319, 319.32, 3.11.0-12-generic, x86_64: installed
  EcryptfsInUse: Yes
  GraphicsCard:
   NVIDIA Corporation GF119M [NVS 4200M] [10de:1056] (rev a1) (prog-if 00 [VGA 
controller])
     Subsystem: Dell Device [1028:0494]
  InstallationDate: Installed on 2012-01-25 (636 days ago)
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  JockeyStatus:
   kmod:nvidia_319_updates - NVIDIA binary Xorg driver, kernel module and VDPAU 
library (Proprietary, Disabled, Not in use)
   kmod:wl - Broadcom STA wireless driver (Proprietary, Disabled, Not in use) 
[auto-install]
   kmod:nvidia_304 - NVIDIA binary Xorg driver, kernel module and VDPAU library 
(Proprietary, Disabled, Not in use)
   kmod:nvidia_304_updates - NVIDIA binary Xorg driver, kernel module and VDPAU 
library (Proprietary, Disabled, Not in use)
   kmod:nvidia_319 - nvidia_319 (Proprietary, Enabled, Not in use)
  MachineType: Dell Inc. Latitude E6520
  MarkForUpload: True
  PlymouthDebug: Error: [Errno 13] Permission denied: 
'/var/log/plymouth-debug.log'
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=b491a34a-6045-4ad4-a2b8-b9ca018c5d41 ro quiet splash
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: Upgraded to saucy on 2013-10-21 (1 days ago)
  XorgConf:
   Section Device
    Identifier  Default Device
    Option  NoLogoTrue
   EndSection
  dmi.bios.date: 10/18/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0J4TFW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd10/18/2011:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0J4TFW:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6520
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.46-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3
  version.nvidia-graphics-drivers:

[Desktop-packages] [Bug 1243557] Re: [NVS 4200M] X freeze, unhandled status 0x00800000

2014-01-09 Thread Rebecca Palmer 
It's worse in Trusty, occurring immediately on heavy graphics load and
within a few minutes even in ordinary use.

The attached is the output of apport-bug xserver-xorg-video-nouveau
--save (apport-collect isn't installed by default) after rebooting, and
contains more instances of the warning than were normal in 13.10, but
not the final error (I suspect it wasn't synced to disk).

It also displayed a send problem report? on reboot, which I OK'd but
suspect is essentially the same information.

** Attachment added: xcrash-14_04-log.txt
   
https://bugs.launchpad.net/nouveau/+bug/1243557/+attachment/3944673/+files/xcrash-14_04-log.txt

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

Title:
  [NVS 4200M] X freeze, unhandled status 0x0080

Status in Accelerated Xorg driver for nVidia cards:
  Confirmed
Status in “xserver-xorg-video-nouveau” package in Ubuntu:
  Incomplete

Bug description:
  With the Nouveau driver selected, my system freezes within a few
  minutes of boot if on battery, but only on heavy graphics load
  (flightgear in maximized window) if on mains.

  The mouse pointer still moves at first, but often freezes later; the
  keyboard LEDs do not react.  Sounds already playing continue until
  finished, but don't repeat if set to (i.e. applications are frozen).
  Alt+SysRq works (provided bug 1244312 is fixed first).

  The kernel log nearly always contains the line

  nouveau ![   PFIFO][:01:00.0] unhandled status 0x0080

  and sometimes other errors as well, while the Xorg log often contains
  EQ overflow errors; the full logs are attached.

  This does not occur with the nvidia-319 driver; the apport logs in
  comment 1 are with nvidia-319, in comments 3-30 (with some duplication
  because apport-collect itself crashed) are with nouveau.

  I first noticed it after upgrading to 13.10, but suspect this was
  because I'd never done the above in Nouveau before, not an actual
  regression.

  Possibly related to bug 1241595.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  319.32  Wed Jun 19 15:51:20 
PDT 2013
   GCC version:  gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu8)
  .tmp.unity.support.test.0:

  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Oct 23 08:19:06 2013
  DistUpgraded: 2013-10-21 23:03:05,341 DEBUG enabling apt cron job
  DistroCodename: saucy
  DistroVariant: ubuntu
  DkmsStatus: nvidia-319, 319.32, 3.11.0-12-generic, x86_64: installed
  EcryptfsInUse: Yes
  GraphicsCard:
   NVIDIA Corporation GF119M [NVS 4200M] [10de:1056] (rev a1) (prog-if 00 [VGA 
controller])
     Subsystem: Dell Device [1028:0494]
  InstallationDate: Installed on 2012-01-25 (636 days ago)
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  JockeyStatus:
   kmod:nvidia_319_updates - NVIDIA binary Xorg driver, kernel module and VDPAU 
library (Proprietary, Disabled, Not in use)
   kmod:wl - Broadcom STA wireless driver (Proprietary, Disabled, Not in use) 
[auto-install]
   kmod:nvidia_304 - NVIDIA binary Xorg driver, kernel module and VDPAU library 
(Proprietary, Disabled, Not in use)
   kmod:nvidia_304_updates - NVIDIA binary Xorg driver, kernel module and VDPAU 
library (Proprietary, Disabled, Not in use)
   kmod:nvidia_319 - nvidia_319 (Proprietary, Enabled, Not in use)
  MachineType: Dell Inc. Latitude E6520
  MarkForUpload: True
  PlymouthDebug: Error: [Errno 13] Permission denied: 
'/var/log/plymouth-debug.log'
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=b491a34a-6045-4ad4-a2b8-b9ca018c5d41 ro quiet splash
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: Upgraded to saucy on 2013-10-21 (1 days ago)
  XorgConf:
   Section Device
    Identifier  Default Device
    Option  NoLogoTrue
   EndSection
  dmi.bios.date: 10/18/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0J4TFW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias:

[Desktop-packages] [Bug 1174205] Re: Using pyopencl doesn't work and spits our ImportError

2013-11-25 Thread Rebecca Palmer 
This is partially fixed in Trusty (nvidia-graphics-drivers-331): nvidia-
libopencl1-331 is now a separate package which the main driver only
Recommends:, so co-installing ocl-icd-libopencl1 and nvidia-331 is now
allowed, but as virtual packages aren't versioned, pyopencl will still
think nvidia-libopencl1-331 satisfies its libopencl1 dependency.

There are a few obvious solutions, but none of them are neat:
-Have pyopencl Depend: specifically on ocl-icd-libopencl1.  The maintainer has 
previously said he doesn't want to do that:  
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682435
-Have nvidia-libopencl1-* not Provide: libopencl1 (effectively defining the 
libopencl1 virtual package to be at least OpenCL 1.2).
-Remove the Recommends: nvidia-libopencl1-331 from nvidia-331, allowing 
pyopencl's preference for ocl-icd-libopencl1 (Depends: ocl-icd-libopencl1 | 
libopencl1) to take effect.  Possibly replace it with a Recommends: 
ocl-icd-libopencl1 to retain has OpenCL by default.

** Bug watch added: Debian Bug tracker #682435
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682435

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

Title:
  Using pyopencl doesn't work and spits our ImportError

Status in “fglrx-installer” package in Ubuntu:
  Confirmed
Status in “nvidia-graphics-drivers-319” package in Ubuntu:
  Confirmed
Status in “pyopencl” package in Ubuntu:
  Confirmed

Bug description:
  Pyopencl doesn't work on raging, the following error message is
  generated:

  Python 2.7.4 (default, Apr 19 2013, 18:32:33)
  [GCC 4.7.3] on linux2
  Type help, copyright, credits or license for more information.
   import pyopencl
  Traceback (most recent call last):
    File stdin, line 1, in module
    File /usr/lib/python2.7/dist-packages/pyopencl/__init__.py, line 4, in 
module
  import pyopencl._cl as _cl
  ImportError: /usr/lib/python2.7/dist-packages/pyopencl/_cl.so: symbol 
clRetainDevice, version OPENCL_1.2 not defined in file libOpenCL.so.1 with link 
time reference

  I am using the following drivers:
  adrian@toad:~$ dpkg -l | grep nvidia
  ii  nvidia-304-updates304.88-0ubuntu2 
i386 NVIDIA binary Xorg driver, kernel module and VDPAU 
library
  ii  nvidia-cg-dev:i3863.1.0013-1  
i386 Cg Toolkit - GPU Shader Authoring Language (headers)
  ii  nvidia-cg-toolkit 3.1.0013-1  
i386 Cg Toolkit - GPU Shader Authoring Language
  ii  nvidia-common 1:0.2.76
i386 transitional package for ubuntu-drivers-common
  ii  nvidia-settings-304-updates   304.88-0ubuntu1 
i386 Tool for configuring the NVIDIA graphics driver


  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: python-pyopencl 2012.1-1ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  Uname: Linux 3.8.0-19-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: i386
  Date: Mon Apr 29 09:56:38 2013
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_ZA.UTF-8
   SHELL=/bin/bash
  SourcePackage: pyopencl
  UpgradeStatus: Upgraded to raring on 2013-04-27 (1 days ago)

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

  1   2   >