date:20161115

[Ubuntu-x-swat] [Bug 1639663] Re: vdpau permissions incorrect in 304.132-0ubuntu0.16.04.2

2016-11-15 Thread Launchpad Bug Tracker

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: nvidia-graphics-drivers-304 (Ubuntu)
   Status: New => Confirmed

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

Title:
  vdpau permissions incorrect in 304.132-0ubuntu0.16.04.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639663/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1642045] [NEW] Please check about these issues

2016-11-15 Thread giorgio

Public bug reported:

Please check about these issues

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24
Uname: Linux 4.4.0-46-generic i686
NonfreeKernelModules: nvidia_uvm nvidia
.proc.driver.nvidia.gpus..03.00.0: Error: [Errno 21] È una directory: 
'/proc/driver/nvidia/gpus/:03:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86 Kernel Module  340.98  Mon Sep 19 16:44:35 PDT 
2016
 GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Tue Nov 15 21:35:03 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.4.0-46-generic, i686: installed
 bbswitch, 0.8, 4.4.0-47-generic, i686: installed
 nvidia-340, 340.98, 4.4.0-46-generic, i686: installed
 nvidia-340, 340.98, 4.4.0-47-generic, i686: installed
GraphicsCard:
 NVIDIA Corporation C79 [GeForce 9300] [10de:0864] (rev b1) (prog-if 00 [VGA 
controller])
   Subsystem: Hewlett-Packard Company C79 [GeForce 9300] [103c:2a7c]
InstallationDate: Installed on 2016-08-24 (83 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
MachineType: Compaq-Presario NQ918AA-ABZ CQ5023IT
ProcEnviron:
 LANGUAGE=it_IT
 PATH=(custom, no user)
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-46-generic 
root=/dev/mapper/ubuntu--vg-root ro drm.debug=0xe plymouth:debug 
plymouth:debug=1=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/16/2009
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 5.04
dmi.board.name: Newark
dmi.board.vendor: FOXCONN
dmi.board.version: HP P/N
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr5.04:bd01/16/2009:svnCompaq-Presario:pnNQ918AA-ABZCQ5023IT:pvr:rvnFOXCONN:rnNewark:rvrHPP/N:cvnHewlett-Packard:ct3:cvr:
dmi.product.name: NQ918AA-ABZ CQ5023IT
dmi.sys.vendor: Compaq-Presario
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Tue Nov 15 20:17:16 2016
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.18.4-0ubuntu0.2

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


** Tags: apport-bug compiz-0.9 i386 ubuntu xenial

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1642045

Title:
  Please check about these issues

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1642045/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1607240] Re: Unity8 default mouse wheel increment seen by Mir clients is 7.0 (it should be 1.0)

2016-11-15 Thread Launchpad Bug Tracker

This bug was fixed in the package ubuntu-system-settings -
0.4+17.04.20161109.1-0ubuntu1

---
ubuntu-system-settings (0.4+17.04.20161109.1-0ubuntu1) zesty; urgency=medium

  [ Daniel van Vugt ]
  * Allow scroll speed multipliers up to 3.0; since the default speed in
(LP: #1607240, #1627567)

  [ Ken VanDine ]
  * Updated example plugin to work with current SDK
  * Fixed pep8 failure

  [ Timo Jyrinki ]
  * Stop depending on transitional packages. (LP: #1583079) (LP:
#1583079)

  [ jonas-drange ]
  * Drop “at” from “Updated at ” string

 -- Ken VanDine   Wed, 09 Nov 2016 15:27:26
+

** Changed in: ubuntu-system-settings (Ubuntu)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1607240

Title:
  Unity8 default mouse wheel increment seen by Mir clients is 7.0 (it
  should be 1.0)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1607240/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1308105] Re: Xfce resets TV mode to NULL when power cycled

2016-11-15 Thread Bengt Nilsson

I tried xfce4-settings 4.12.1-11 as mentioned in #133 and indeed it "works", X 
does not crash.
However, the set screen resolution is lost. When I turn on the screen again, 
the desktop defaults to the highest possible screen resolution. 
In my case, it means that my desktop menu bar and docky are placed outside the 
screen bounds, tricky to reset.
Better than it was before, but not quite there yet.

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

Title:
  Xfce resets TV mode to NULL when power cycled

To manage notifications about this bug go to:
https://bugs.launchpad.net/mythbuntu/+bug/1308105/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1640451] Re: ksplashqml crashed with SIGABRT in QMessageLogger::fatal()

2016-11-15 Thread Oleksandr Pikozh

** Description changed:

  I'm unable to start plasma after nvidia nvidia-304 package upgrade (and
  reboot).
  
  The related KDE bug report is (at least, KDE crash handler (DrKonqi) 
considered my report a duplicate): https://bugs.kde.org/show_bug.cgi?id=372229.
  However, I discovered that the crash is caused by upgrade to 
nvidia-304=304.132-0ubuntu0.16.04.2 (with nvidia-304=304.131-0ubuntu3 it 
worked).
  
- Current version of packages make my system at all:
+ Current version of packages make my system unusable at all:
  - With nvidia-304, nvidia-opencl-icd-304, nvidia-settings packages installed 
(and xserver-xorg-video-nouveau purged) I perceive the currently described bug.
  - With xserver-xorg-video-nouveau package installed (and nvidia-304, 
nvidia-opencl-icd-304, nvidia-settings purged) the video isn't working at all 
(colorful screen and system hang).
  - With all them purged session starts and seems to work fine, but them 
crashes every 5-20mins (probably, I'll fill a separate report for that).
  
  1) lsb_release -rd
  Description:Ubuntu 16.04.1 LTS
  Release:16.04
  
  2) apt-cache policy plasma-workspace nvidia-304 nvidia-opencl-icd-304 
nvidia-settings
  plasma-workspace:
-   Installed: 4:5.5.5.2-0ubuntu1
-   Candidate: 4:5.5.5.2-0ubuntu1
-   Version table:
-  *** 4:5.5.5.2-0ubuntu1 500
- 500 http://ua.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
- 100 /var/lib/dpkg/status
+   Installed: 4:5.5.5.2-0ubuntu1
+   Candidate: 4:5.5.5.2-0ubuntu1
+   Version table:
+  *** 4:5.5.5.2-0ubuntu1 500
+ 500 http://ua.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
+ 100 /var/lib/dpkg/status
  nvidia-304:
-   Installed: 304.132-0ubuntu0.16.04.2
-   Candidate: 304.132-0ubuntu0.16.04.2
-   Version table:
-  *** 304.132-0ubuntu0.16.04.2 500
- 500 http://ua.archive.ubuntu.com/ubuntu xenial-updates/restricted 
amd64 Packages
- 500 http://security.ubuntu.com/ubuntu xenial-security/restricted 
amd64 Packages
-  304.131-0ubuntu3 500
- 500 http://ua.archive.ubuntu.com/ubuntu xenial/restricted amd64 
Packages
+   Installed: 304.132-0ubuntu0.16.04.2
+   Candidate: 304.132-0ubuntu0.16.04.2
+   Version table:
+  *** 304.132-0ubuntu0.16.04.2 500
+ 500 http://ua.archive.ubuntu.com/ubuntu xenial-updates/restricted 
amd64 Packages
+ 500 http://security.ubuntu.com/ubuntu xenial-security/restricted 
amd64 Packages
+  304.131-0ubuntu3 500
+ 500 http://ua.archive.ubuntu.com/ubuntu xenial/restricted amd64 
Packages
  nvidia-opencl-icd-304:
-   Installed: 304.132-0ubuntu0.16.04.2
-   Candidate: 304.132-0ubuntu0.16.04.2
-   Version table:
-  *** 304.132-0ubuntu0.16.04.2 500
- 500 http://ua.archive.ubuntu.com/ubuntu xenial-updates/restricted 
amd64 Packages
- 500 http://security.ubuntu.com/ubuntu xenial-security/restricted 
amd64 Packages
-  304.131-0ubuntu3 500
- 500 http://ua.archive.ubuntu.com/ubuntu xenial/restricted amd64 
Packages
+   Installed: 304.132-0ubuntu0.16.04.2
+   Candidate: 304.132-0ubuntu0.16.04.2
+   Version table:
+  *** 304.132-0ubuntu0.16.04.2 500
+ 500 http://ua.archive.ubuntu.com/ubuntu xenial-updates/restricted 
amd64 Packages
+ 500 http://security.ubuntu.com/ubuntu xenial-security/restricted 
amd64 Packages
+  304.131-0ubuntu3 500
+ 500 http://ua.archive.ubuntu.com/ubuntu xenial/restricted amd64 
Packages
  nvidia-settings:
-   Installed: 361.42-0ubuntu1
-   Candidate: 361.42-0ubuntu1
-   Version table:
-  *** 361.42-0ubuntu1 500
- 500 http://ua.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
+   Installed: 361.42-0ubuntu1
+   Candidate: 361.42-0ubuntu1
+   Version table:
+  *** 361.42-0ubuntu1 500
+ 500 http://ua.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  
  3) I expected plasma to start normally on system start-up (I use
  autologin) and/or on manual execution of 'sudo service sddm start' in
  first console (assuming sddm was previously shut down).
  
  4) Black screen for a second, then 5 or more cascaded windows of KDE
  crash handler.
  
  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: plasma-workspace 4:5.5.5.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Nov  9 12:17:49 2016
  ExecutablePath: /usr/bin/ksplashqml
  ExecutableTimestamp: 1460701605
  InstallationDate: Installed on 2015-11-10 (364 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151110)
  ProcCmdline: ksplashqml Breeze --pid
  ProcCwd: /home/user
  Signal: 6
  SourcePackage: plasma-workspace
  StacktraceTop:
-  qt_message_fatal (context=..., message=) at 
global/qlogging.cpp:1578
-  QMessageLogger::fatal (this=this@entry=0x7fffdc604b30, 
msg=msg@entry=0x7f92c2e932c5 "%s") at global/qlogging.cpp:781
-

[Ubuntu-x-swat] [Bug 1640451] Re: ksplashqml crashed with SIGABRT in QMessageLogger::fatal()

2016-11-15 Thread Alberto Salvia Novella

** Changed in: nvidia-graphics-drivers-304 (Ubuntu)
   Importance: Undecided => Critical

** Changed in: plasma-workspace (Ubuntu)
   Importance: Medium => Critical

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

Title:
  ksplashqml crashed with SIGABRT in QMessageLogger::fatal()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1640451/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1640451] Re: ksplashqml crashed with SIGABRT in QMessageLogger::fatal()

2016-11-15 Thread lothar4ever

Steps i did to solve this:

1. sudo apt-get install nvidia-304=304.131-0ubuntu3
(it will downgrade to 131)
2. sudo apt-mark hold nvidia-304
(it will prevent future automatic updates)

I don't know if in the future it will be a problem not having it
updated, but for now i can work like this.

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

Title:
  ksplashqml crashed with SIGABRT in QMessageLogger::fatal()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1640451/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1640451] Re: ksplashqml crashed with SIGABRT in QMessageLogger::fatal()

2016-11-15 Thread Launchpad Bug Tracker

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: plasma-workspace (Ubuntu)
   Status: New => Confirmed

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

Title:
  ksplashqml crashed with SIGABRT in QMessageLogger::fatal()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1640451/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1640451] Re: ksplashqml crashed with SIGABRT in QMessageLogger::fatal()

2016-11-15 Thread Launchpad Bug Tracker

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: nvidia-graphics-drivers-304 (Ubuntu)
   Status: New => Confirmed

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

Title:
  ksplashqml crashed with SIGABRT in QMessageLogger::fatal()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1640451/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1640451] Re: ksplashqml crashed with SIGABRT in QMessageLogger::fatal()

2016-11-15 Thread Veress Krisztián

1. Fekete nvidia-304.
sudo apt remove --purge nvidia-304

2. Download nvidia-304.131.0ubuntu3.deb
3. Install nvidia driver
sudo dpkg -i nvidia-304.131.0ubuntu3
deb
4. Reboot

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

Title:
  ksplashqml crashed with SIGABRT in QMessageLogger::fatal()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1640451/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1581560] Re: system crash when attaching external display

2016-11-15 Thread kay

Why did you close the issue? I still have to power off my laptop instead
of suspending.

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1581560

Title:
  system crash when attaching external display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1581560/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1639663] Re: vdpau permissions incorrect in 304.132-0ubuntu0.16.04.2

[Ubuntu-x-swat] [Bug 1642045] [NEW] Please check about these issues

[Ubuntu-x-swat] [Bug 1607240] Re: Unity8 default mouse wheel increment seen by Mir clients is 7.0 (it should be 1.0)

[Ubuntu-x-swat] [Bug 1308105] Re: Xfce resets TV mode to NULL when power cycled

[Ubuntu-x-swat] [Bug 1640451] Re: ksplashqml crashed with SIGABRT in QMessageLogger::fatal()

[Ubuntu-x-swat] [Bug 1640451] Re: ksplashqml crashed with SIGABRT in QMessageLogger::fatal()

[Ubuntu-x-swat] [Bug 1640451] Re: ksplashqml crashed with SIGABRT in QMessageLogger::fatal()

[Ubuntu-x-swat] [Bug 1640451] Re: ksplashqml crashed with SIGABRT in QMessageLogger::fatal()

[Ubuntu-x-swat] [Bug 1640451] Re: ksplashqml crashed with SIGABRT in QMessageLogger::fatal()

[Ubuntu-x-swat] [Bug 1640451] Re: ksplashqml crashed with SIGABRT in QMessageLogger::fatal()

[Ubuntu-x-swat] [Bug 1581560] Re: system crash when attaching external display

11 matches

Site Navigation

Mail list logo

Footer information