[Desktop-packages] [Bug 1990709] Re: package firefox 104.0+build3-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1

[Kris B.]

When I relogged into the computer (had a broken kernel install and few
other things that failed during upgrade process because of this
exiting), re-ran sudo apt update it managed to finish the update and
install firefox and all the broken packages that were left.  But it did
cancel/abort the system during the do-release-upgrade and gave an
unstable system.

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

Title:
  package firefox 104.0+build3-0ubuntu0.20.04.1 failed to
  install/upgrade: new firefox package pre-installation script
  subprocess returned error exit status 1

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Snap fails to install during do-release-upgrade from 20.04 to 22.04.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: firefox 104.0+build3-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-126.142-generic 5.4.203
  Uname: Linux 5.4.0-126-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kristv  802 F pulseaudio
   /dev/snd/controlC1:  kristv  802 F pulseaudio
  BuildID: 20220818191623
  CasperMD5CheckResult: unknown
  Channel: Unavailable
  Date: Fri Sep 23 22:01:11 2022
  ErrorMessage: new firefox package pre-installation script subprocess returned 
error exit status 1
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-07-28 (1518 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IpRoute:
   default via 192.168.1.1 dev enp2s0 proto dhcp metric 100 
   169.254.0.0/16 dev enp2s0 scope link metric 1000 
   192.168.1.0/24 dev enp2s0 proto kernel scope link src 192.168.1.10 metric 100
  NoProfiles: True
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.7
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Title: package firefox 104.0+build3-0ubuntu0.20.04.1 failed to 
install/upgrade: new firefox package pre-installation script subprocess 
returned error exit status 1
  UpgradeStatus: Upgraded to jammy on 2022-09-24 (0 days ago)
  dmi.bios.date: 02/21/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080015
  dmi.board.name: NC99D3
  dmi.board.vendor: Jetway Information Co., Ltd
  dmi.board.version: 1.0
  dmi.chassis.type: 10
  dmi.chassis.vendor: Jetway Information Co., Ltd
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080015:bd02/21/2012:svnJetwayInformationCo.,Ltd:pnNC99D3:pvr1.0:rvnJetwayInformationCo.,Ltd:rnNC99D3:rvr1.0:cvnJetwayInformationCo.,Ltd:ct10:cvr1.0:
  dmi.product.name: NC99D3
  dmi.product.version: 1.0
  dmi.sys.vendor: Jetway Information Co., Ltd

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1990709/+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 1990709] [NEW] package firefox 104.0+build3-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1

[Kris B.]

Public bug reported:

Snap fails to install during do-release-upgrade from 20.04 to 22.04.

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: firefox 104.0+build3-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.4.0-126.142-generic 5.4.203
Uname: Linux 5.4.0-126-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  kristv  802 F pulseaudio
 /dev/snd/controlC1:  kristv  802 F pulseaudio
BuildID: 20220818191623
CasperMD5CheckResult: unknown
Channel: Unavailable
Date: Fri Sep 23 22:01:11 2022
ErrorMessage: new firefox package pre-installation script subprocess returned 
error exit status 1
ForcedLayersAccel: False
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2018-07-28 (1518 days ago)
InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
IpRoute:
 default via 192.168.1.1 dev enp2s0 proto dhcp metric 100 
 169.254.0.0/16 dev enp2s0 scope link metric 1000 
 192.168.1.0/24 dev enp2s0 proto kernel scope link src 192.168.1.10 metric 100
NoProfiles: True
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.1
 apt  2.4.7
RunningIncompatibleAddons: False
SourcePackage: firefox
Title: package firefox 104.0+build3-0ubuntu0.20.04.1 failed to install/upgrade: 
new firefox package pre-installation script subprocess returned error exit 
status 1
UpgradeStatus: Upgraded to jammy on 2022-09-24 (0 days ago)
dmi.bios.date: 02/21/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080015
dmi.board.name: NC99D3
dmi.board.vendor: Jetway Information Co., Ltd
dmi.board.version: 1.0
dmi.chassis.type: 10
dmi.chassis.vendor: Jetway Information Co., Ltd
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080015:bd02/21/2012:svnJetwayInformationCo.,Ltd:pnNC99D3:pvr1.0:rvnJetwayInformationCo.,Ltd:rnNC99D3:rvr1.0:cvnJetwayInformationCo.,Ltd:ct10:cvr1.0:
dmi.product.name: NC99D3
dmi.product.version: 1.0
dmi.sys.vendor: Jetway Information Co., Ltd

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


** Tags: amd64 apport-package jammy need-duplicate-check

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

Title:
  package firefox 104.0+build3-0ubuntu0.20.04.1 failed to
  install/upgrade: new firefox package pre-installation script
  subprocess returned error exit status 1

Status in firefox package in Ubuntu:
  New

Bug description:
  Snap fails to install during do-release-upgrade from 20.04 to 22.04.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: firefox 104.0+build3-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-126.142-generic 5.4.203
  Uname: Linux 5.4.0-126-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kristv  802 F pulseaudio
   /dev/snd/controlC1:  kristv  802 F pulseaudio
  BuildID: 20220818191623
  CasperMD5CheckResult: unknown
  Channel: Unavailable
  Date: Fri Sep 23 22:01:11 2022
  ErrorMessage: new firefox package pre-installation script subprocess returned 
error exit status 1
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-07-28 (1518 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IpRoute:
   default via 192.168.1.1 dev enp2s0 proto dhcp metric 100 
   169.254.0.0/16 dev enp2s0 scope link metric 1000 
   192.168.1.0/24 dev enp2s0 proto kernel scope link src 192.168.1.10 metric 100
  NoProfiles: True
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.7
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Title: package firefox 104.0+build3-0ubuntu0.20.04.1 failed to 
install/upgrade: new firefox package pre-installation script subprocess 
returned error exit status 1
  UpgradeStatus: Upgraded to jammy on 2022-09-24 (0 days ago)
  dmi.bios.date: 02/21/2012
  

[Desktop-packages] [Bug 1971538] Re: My machine as Wi-Fi Hotspot broken after upgrade to 22.04

[Kris]

** Changed in: network-manager (Ubuntu)
   Status: Incomplete => New

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

Title:
  My machine as Wi-Fi Hotspot broken after upgrade to 22.04

Status in network-manager package in Ubuntu:
  New

Bug description:
  * Impact
  The hotspot feature fails to forward the data to the clients

  * Test case
  - log into an Ubuntu or GNOME session
  - connect the machine to an eth cable for internet
  - go to gnome-control-center -> wifi
  - enable the hotspot from the menu in the headerbar
  - connect another device to the wifi created
  -> the client should connect and access to internet work correctly

  Upon updating to 22.04, none of my machines can use the connection.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1971538/+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 1971538] Re: My machine as Wi-Fi Hotspot broken after upgrade to 22.04

[Kris]

Add logging

** Attachment added: "log"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1971538/+attachment/5588142/+files/log

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

Title:
  My machine as Wi-Fi Hotspot broken after upgrade to 22.04

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  * Impact
  The hotspot feature fails to forward the data to the clients

  * Test case
  - log into an Ubuntu or GNOME session
  - connect the machine to an eth cable for internet
  - go to gnome-control-center -> wifi
  - enable the hotspot from the menu in the headerbar
  - connect another device to the wifi created
  -> the client should connect and access to internet work correctly

  Upon updating to 22.04, none of my machines can use the connection.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1971538/+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 1971538] [NEW] My machine as Wi-Fi Hotspot broken after upgrade to 22.04

[Kris]

Public bug reported:

* Impact
The hotspot feature fails to forward the data to the clients

* Test case
- log into an Ubuntu or GNOME session
- connect the machine to an eth cable for internet
- go to gnome-control-center -> wifi
- enable the hotspot from the menu in the headerbar
- connect another device to the wifi created
-> the client should connect and access to internet work correctly

Upon updating to 22.04, none of my machines can use the connection.

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

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

Title:
  My machine as Wi-Fi Hotspot broken after upgrade to 22.04

Status in network-manager package in Ubuntu:
  New

Bug description:
  * Impact
  The hotspot feature fails to forward the data to the clients

  * Test case
  - log into an Ubuntu or GNOME session
  - connect the machine to an eth cable for internet
  - go to gnome-control-center -> wifi
  - enable the hotspot from the menu in the headerbar
  - connect another device to the wifi created
  -> the client should connect and access to internet work correctly

  Upon updating to 22.04, none of my machines can use the connection.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1971538/+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 1816271] Re: [regression] No sound on ThinkPad T530 until activity at headphone jack(in or out/in) after about 14Feb19

[Kris M]

Yes, indeed, I think that may be it(new alsa config panel). They added boxes 
and the way it works and it seems NOW that if I unplug headphones, and boot, 
then go to settings/sound:
set system vol to full
set output device to "speakers-builtin audio"
set configuration to "analog stereo output"
Then the speakers appear in the test box and all works as it should.
Plug in headphones and the selection changes as it should. And back and forth.

Before, those settings would not hold through a boot, NOW they do.

I did see some more alsa library stuff going in yesterday and today.
Don't know what fixed it but it seems to be fixed.
At the moment, I might guess an error in the new alsa config layout, and not 
pulseaudio.

I did do alsamixer and changed automute (right arrow way over) ena to
disa to ena, with tests interspersed, but that seemed to make no
difference.

Requires that you go to settings/sound and set stuff up correctly the
first time.(I think)

I am guessing that that would be the case after a clean install, but I
will not test that.

I think this should be closed/as solved, but I would like to be able to
re-open it if the problem re-appears.  Many thanks for all your time.

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

Title:
  [regression] No sound on ThinkPad T530 until activity at headphone
  jack(in or out/in) after about 14Feb19

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  19.04,kern 4.19.0-13
  just took update and now does not recognize soundcard or something plugged in 
to headphones jack. pulled bug. Now if I unplug headphones and plug back in, it 
wakes up and recognizes it and works fine. I thought I had this prob a few days 
ago and restored back to the 10th, and updated all but alsa and worked fine. 
This morning I checked and a bunch of alsa stuff was no longer showing in 
updates, took everything, and worked fine. Just took updates (Software 
Updater), and checked speakers and no go. When this happened, it also would not 
allow sound to HDTV via HDMI, no matter what. Just tested and was able to get 
sound via hdmi, but remember, I have already "woken it up" by unplugging and 
plugging headphones (actually sony vaio computer speakers)
  ThinkPad T530-2394-3J8, i5-3380M 2.9GHz, Dual boot (BIOS/MBR): Grub, Ubuntu 
19.04dev / Win7 Pro x64 . 8GB(15GB/s), Sammy 250GB SSD. Fast!

  I expected sound to recognize soundcard/speakers. It did not until I
  unplug/replug headphones.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gstreamer1.0-plugins-good 1.15.1-1ubuntu2
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 16 19:20:26 2019
  InstallationDate: Installed on 2019-02-09 (7 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gst-plugins-good1.0
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kris   1512 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-02-09 (8 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  Package: pulseaudio 1:12.2-2ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Tags:  disco
  Uname: Linux 4.19.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/23/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G4ETB4WW (2.74 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 23943J8
  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:bvrG4ETB4WW(2.74):bd11/23/2018:svnLENOVO:pn23943J8:pvrThinkPadT530:rvnLENOVO:rn23943J8:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T530
  dmi.product.name: 23943J8
  dmi.product.sku: LENOVO_MT_2394
  dmi.product.version: ThinkPad T530
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.ne

[Desktop-packages] [Bug 1816271] Re: [regression] No sound on ThinkPad T530 until activity at headphone jack(in or out/in) after about 14Feb19

[Kris M]

Hardware spec sheet as well as Win7 claim the Realtek codec is ALC3202.
Apparently Ubuntu is seeing it as ALC269VC.

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

Title:
  [regression] No sound on ThinkPad T530 until activity at headphone
  jack(in or out/in) after about 14Feb19

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  19.04,kern 4.19.0-13
  just took update and now does not recognize soundcard or something plugged in 
to headphones jack. pulled bug. Now if I unplug headphones and plug back in, it 
wakes up and recognizes it and works fine. I thought I had this prob a few days 
ago and restored back to the 10th, and updated all but alsa and worked fine. 
This morning I checked and a bunch of alsa stuff was no longer showing in 
updates, took everything, and worked fine. Just took updates (Software 
Updater), and checked speakers and no go. When this happened, it also would not 
allow sound to HDTV via HDMI, no matter what. Just tested and was able to get 
sound via hdmi, but remember, I have already "woken it up" by unplugging and 
plugging headphones (actually sony vaio computer speakers)
  ThinkPad T530-2394-3J8, i5-3380M 2.9GHz, Dual boot (BIOS/MBR): Grub, Ubuntu 
19.04dev / Win7 Pro x64 . 8GB(15GB/s), Sammy 250GB SSD. Fast!

  I expected sound to recognize soundcard/speakers. It did not until I
  unplug/replug headphones.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gstreamer1.0-plugins-good 1.15.1-1ubuntu2
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 16 19:20:26 2019
  InstallationDate: Installed on 2019-02-09 (7 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gst-plugins-good1.0
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kris   1512 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-02-09 (8 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  Package: pulseaudio 1:12.2-2ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Tags:  disco
  Uname: Linux 4.19.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/23/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G4ETB4WW (2.74 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 23943J8
  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:bvrG4ETB4WW(2.74):bd11/23/2018:svnLENOVO:pn23943J8:pvrThinkPadT530:rvnLENOVO:rn23943J8:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T530
  dmi.product.name: 23943J8
  dmi.product.sku: LENOVO_MT_2394
  dmi.product.version: ThinkPad T530
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1816271/+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 1816271] Re: [ALC269VC Analog] No sound on ThinkPad T530 until activity at headphone jack(in or out/in) after about 14Feb19

[Kris M]

to clarify title:
After about 14Feb19 :

When boot, there is no sound: settings/sound does not show any
soundcard.

If I then plug in a headphones to headphone jack, Immediately soundcard
and sound are present.

If I booted with the headphones already plugged in, I must unplug AND
then replug the headphones to get immediately soundcard and sound are
present.

I saw a single pulseaudio update go in at or around 14Feb19.

I can go back to 10Feb and redo updates, but I have also found that
sometimes, even when I don't have something checked in update, it will
update it anyway, so hard to get a system without that specific update
while I am taking other updates. Yes that in itself is a bug but not for
this bug.

hardware: Sony Vaio computer speakers, or Razer headphones. Result same.

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

Title:
  [ALC269VC Analog] No sound on ThinkPad T530 until activity at
  headphone jack(in or out/in) after about 14Feb19

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  19.04,kern 4.19.0-13
  just took update and now does not recognize soundcard or something plugged in 
to headphones jack. pulled bug. Now if I unplug headphones and plug back in, it 
wakes up and recognizes it and works fine. I thought I had this prob a few days 
ago and restored back to the 10th, and updated all but alsa and worked fine. 
This morning I checked and a bunch of alsa stuff was no longer showing in 
updates, took everything, and worked fine. Just took updates (Software 
Updater), and checked speakers and no go. When this happened, it also would not 
allow sound to HDTV via HDMI, no matter what. Just tested and was able to get 
sound via hdmi, but remember, I have already "woken it up" by unplugging and 
plugging headphones (actually sony vaio computer speakers)
  ThinkPad T530-2394-3J8, i5-3380M 2.9GHz, Dual boot (BIOS/MBR): Grub, Ubuntu 
19.04dev / Win7 Pro x64 . 8GB(15GB/s), Sammy 250GB SSD. Fast!

  I expected sound to recognize soundcard/speakers. It did not until I
  unplug/replug headphones.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gstreamer1.0-plugins-good 1.15.1-1ubuntu2
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 16 19:20:26 2019
  InstallationDate: Installed on 2019-02-09 (7 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gst-plugins-good1.0
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kris   1512 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-02-09 (8 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  Package: pulseaudio 1:12.2-2ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Tags:  disco
  Uname: Linux 4.19.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/23/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G4ETB4WW (2.74 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 23943J8
  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:bvrG4ETB4WW(2.74):bd11/23/2018:svnLENOVO:pn23943J8:pvrThinkPadT530:rvnLENOVO:rn23943J8:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T530
  dmi.product.name: 23943J8
  dmi.product.sku: LENOVO_MT_2394
  dmi.product.version: ThinkPad T530
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1816271/+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 1816271] Re: [ALC269VC Analog] No sound on ThinkPad T530 until activity at headphone jack(in/out or out/in) after about 14Feb19

[Kris M]

** Summary changed:

- [ALC269VC Analog] No sound on ThinkPad T530 until headphones are re-plugged in
+ [ALC269VC Analog] No sound on ThinkPad T530 until activity at headphone 
jack(in/out or out/in) after about 14Feb19

** Summary changed:

- [ALC269VC Analog] No sound on ThinkPad T530 until activity at headphone 
jack(in/out or out/in) after about 14Feb19
+ [ALC269VC Analog] No sound on ThinkPad T530 until activity at headphone 
jack(in or out/in) after about 14Feb19

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

Title:
  [ALC269VC Analog] No sound on ThinkPad T530 until activity at
  headphone jack(in or out/in) after about 14Feb19

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  19.04,kern 4.19.0-13
  just took update and now does not recognize soundcard or something plugged in 
to headphones jack. pulled bug. Now if I unplug headphones and plug back in, it 
wakes up and recognizes it and works fine. I thought I had this prob a few days 
ago and restored back to the 10th, and updated all but alsa and worked fine. 
This morning I checked and a bunch of alsa stuff was no longer showing in 
updates, took everything, and worked fine. Just took updates (Software 
Updater), and checked speakers and no go. When this happened, it also would not 
allow sound to HDTV via HDMI, no matter what. Just tested and was able to get 
sound via hdmi, but remember, I have already "woken it up" by unplugging and 
plugging headphones (actually sony vaio computer speakers)
  ThinkPad T530-2394-3J8, i5-3380M 2.9GHz, Dual boot (BIOS/MBR): Grub, Ubuntu 
19.04dev / Win7 Pro x64 . 8GB(15GB/s), Sammy 250GB SSD. Fast!

  I expected sound to recognize soundcard/speakers. It did not until I
  unplug/replug headphones.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gstreamer1.0-plugins-good 1.15.1-1ubuntu2
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 16 19:20:26 2019
  InstallationDate: Installed on 2019-02-09 (7 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gst-plugins-good1.0
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kris   1512 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-02-09 (8 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  Package: pulseaudio 1:12.2-2ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Tags:  disco
  Uname: Linux 4.19.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/23/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G4ETB4WW (2.74 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 23943J8
  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:bvrG4ETB4WW(2.74):bd11/23/2018:svnLENOVO:pn23943J8:pvrThinkPadT530:rvnLENOVO:rn23943J8:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T530
  dmi.product.name: 23943J8
  dmi.product.sku: LENOVO_MT_2394
  dmi.product.version: ThinkPad T530
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1816271/+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 1583801] Re: No sound via headphones (headset) when Ubuntu boots with them plugged in

[Kris M]

These do not install. I tried both deb and ddeb of a few . screen dims
for 20 sec then back. Nothing happens. Also don't know if I should be
using the deb's or the ddeb's (debugging).

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

Title:
  No sound via headphones (headset) when Ubuntu boots with them plugged
  in

Status in PulseAudio:
  Unknown
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/193

  The bug is twofold, first when computer boots if the headset
  (headphones with built-in mic, one audio jack) is plugged in, then
  there is no sound (via headphones or otherwise). If you plug
  headphones out and back in, then it usually works as expected.

  The second scenario is the same, except that plugging out and back in
  again doesn't help. In that case, I just restart the laptop, then plug
  them back in again and it works.

  In all cases, microphone works.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  crunch 3248 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu May 19 22:13:20 2016
  InstallationDate: Installed on 2016-05-07 (12 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  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/controlC0:  crunch 3248 F pulseaudio
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: No sound at all
  Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1583801/+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 1583801] Re: No sound via headphones (headset) when Ubuntu boots with them plugged in

[Kris M]

I tried to install a few of them but all I get is about 20 sec of dim
screen then back with no response. I need to leave this for now.
Tomorrow. Thanks for your help!

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

Title:
  No sound via headphones (headset) when Ubuntu boots with them plugged
  in

Status in PulseAudio:
  Unknown
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/193

  The bug is twofold, first when computer boots if the headset
  (headphones with built-in mic, one audio jack) is plugged in, then
  there is no sound (via headphones or otherwise). If you plug
  headphones out and back in, then it usually works as expected.

  The second scenario is the same, except that plugging out and back in
  again doesn't help. In that case, I just restart the laptop, then plug
  them back in again and it works.

  In all cases, microphone works.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  crunch 3248 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu May 19 22:13:20 2016
  InstallationDate: Installed on 2016-05-07 (12 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  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/controlC0:  crunch 3248 F pulseaudio
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: No sound at all
  Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1583801/+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 1583801] Re: No sound via headphones (headset) when Ubuntu boots with them plugged in

[Kris M]

nevermind - I searched in files and I've got them all. Give me a few.

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

Title:
  No sound via headphones (headset) when Ubuntu boots with them plugged
  in

Status in PulseAudio:
  Unknown
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/193

  The bug is twofold, first when computer boots if the headset
  (headphones with built-in mic, one audio jack) is plugged in, then
  there is no sound (via headphones or otherwise). If you plug
  headphones out and back in, then it usually works as expected.

  The second scenario is the same, except that plugging out and back in
  again doesn't help. In that case, I just restart the laptop, then plug
  them back in again and it works.

  In all cases, microphone works.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  crunch 3248 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu May 19 22:13:20 2016
  InstallationDate: Installed on 2016-05-07 (12 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  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/controlC0:  crunch 3248 F pulseaudio
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: No sound at all
  Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1583801/+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 1583801] Re: No sound via headphones (headset) when Ubuntu boots with them plugged in

[Kris M]

sorry for beginner question - been looking thru my bug but don't see
list of modules.

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

Title:
  No sound via headphones (headset) when Ubuntu boots with them plugged
  in

Status in PulseAudio:
  Unknown
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/193

  The bug is twofold, first when computer boots if the headset
  (headphones with built-in mic, one audio jack) is plugged in, then
  there is no sound (via headphones or otherwise). If you plug
  headphones out and back in, then it usually works as expected.

  The second scenario is the same, except that plugging out and back in
  again doesn't help. In that case, I just restart the laptop, then plug
  them back in again and it works.

  In all cases, microphone works.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  crunch 3248 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu May 19 22:13:20 2016
  InstallationDate: Installed on 2016-05-07 (12 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  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/controlC0:  crunch 3248 F pulseaudio
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: No sound at all
  Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1583801/+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 1583801] Re: No sound via headphones (headset) when Ubuntu boots with them plugged in

[Kris M]

yes, I saw that go by. So how do I install this? download 25 modules and
deb or ddeb install each one? Thanks!

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

Title:
  No sound via headphones (headset) when Ubuntu boots with them plugged
  in

Status in PulseAudio:
  Unknown
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/193

  The bug is twofold, first when computer boots if the headset
  (headphones with built-in mic, one audio jack) is plugged in, then
  there is no sound (via headphones or otherwise). If you plug
  headphones out and back in, then it usually works as expected.

  The second scenario is the same, except that plugging out and back in
  again doesn't help. In that case, I just restart the laptop, then plug
  them back in again and it works.

  In all cases, microphone works.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  crunch 3248 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu May 19 22:13:20 2016
  InstallationDate: Installed on 2016-05-07 (12 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  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/controlC0:  crunch 3248 F pulseaudio
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: No sound at all
  Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1583801/+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 1816271] Re: [ALC269VC Analog] No sound on ThinkPad T530 until headphones are re-plugged in

[Kris M]

*** This bug is a duplicate of bug 1583801 ***
https://bugs.launchpad.net/bugs/1583801

Ok. Thanks for ack. :)

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

Title:
  [ALC269VC Analog] No sound on ThinkPad T530 until headphones are re-
  plugged in

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  19.04,kern 4.19.0-13
  just took update and now does not recognize soundcard or something plugged in 
to headphones jack. pulled bug. Now if I unplug headphones and plug back in, it 
wakes up and recognizes it and works fine. I thought I had this prob a few days 
ago and restored back to the 10th, and updated all but alsa and worked fine. 
This morning I checked and a bunch of alsa stuff was no longer showing in 
updates, took everything, and worked fine. Just took updates (Software 
Updater), and checked speakers and no go. When this happened, it also would not 
allow sound to HDTV via HDMI, no matter what. Just tested and was able to get 
sound via hdmi, but remember, I have already "woken it up" by unplugging and 
plugging headphones (actually sony vaio computer speakers)
  ThinkPad T530-2394-3J8, i5-3380M 2.9GHz, Dual boot (BIOS/MBR): Grub, Ubuntu 
19.04dev / Win7 Pro x64 . 8GB(15GB/s), Sammy 250GB SSD. Fast!

  I expected sound to recognize soundcard/speakers. It did not until I
  unplug/replug headphones.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gstreamer1.0-plugins-good 1.15.1-1ubuntu2
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 16 19:20:26 2019
  InstallationDate: Installed on 2019-02-09 (7 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gst-plugins-good1.0
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kris   1512 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-02-09 (8 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  Package: pulseaudio 1:12.2-2ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Tags:  disco
  Uname: Linux 4.19.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/23/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G4ETB4WW (2.74 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 23943J8
  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:bvrG4ETB4WW(2.74):bd11/23/2018:svnLENOVO:pn23943J8:pvrThinkPadT530:rvnLENOVO:rn23943J8:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T530
  dmi.product.name: 23943J8
  dmi.product.sku: LENOVO_MT_2394
  dmi.product.version: ThinkPad T530
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1816271/+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 1583801] Re: No sound via headphones (headset) when Ubuntu boots with them plugged in

[Kris M]

1816271 I get no sound after boot whether or not headphones are plugged in.
If headphones not plugged in, after boot, plugging them in wakes sound.
If headphones ARE plugged in at boot, must unplug and plug in headphones to 
wake sound.
It's just not waking alsa or pulseaudio. Worked fine until about 14th or 
15th.Feb

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

Title:
  No sound via headphones (headset) when Ubuntu boots with them plugged
  in

Status in PulseAudio:
  Unknown
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/193

  The bug is twofold, first when computer boots if the headset
  (headphones with built-in mic, one audio jack) is plugged in, then
  there is no sound (via headphones or otherwise). If you plug
  headphones out and back in, then it usually works as expected.

  The second scenario is the same, except that plugging out and back in
  again doesn't help. In that case, I just restart the laptop, then plug
  them back in again and it works.

  In all cases, microphone works.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  crunch 3248 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu May 19 22:13:20 2016
  InstallationDate: Installed on 2016-05-07 (12 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  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/controlC0:  crunch 3248 F pulseaudio
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: No sound at all
  Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1583801/+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 1815384] Re: No sound if booted with the headphones plugged in (have to re-plug them to get sound)

[Kris M]

*** This bug is a duplicate of bug 1583801 ***
https://bugs.launchpad.net/bugs/1583801

1816271 I get no sound after boot whether or not headphones are plugged in. 
If headphones not plugged in, after boot, plugging them in wakes sound.
If headphones ARE plugged in at boot, must unplug and plug in headphones to 
wake sound.
It's just not waking alsa or pulseaudio. Worked fine until about 14th or 15th.

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

Title:
  No sound if booted with the headphones plugged in (have to re-plug
  them to get sound)

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  
  I am not sure how to describe the problem.

  If i turn off my laptop with my headphones in, when it boots up (without 
removing the headphones at any times), then no sound is playing on any exits. 
Not on the laptop's speaker, neither on the headphones.

  I am a developer, and I think the issue it's that the hardware is trying to 
play the sound on the headphones (because you restrict playing on both the 
speakers and the headphones at once, without extra custom configurations), 
because playing on headphones is what the hardware remembers, but ubuntu 
forgets that between reboots and it's telling the hardware to play on speakers, 
which the hardware won't do. 

  To fix the problem, i have to unplug my headphones and plug them back
  in. And sometimes that is annoying because some sounds may be too loud
  and i am in a meeting :) .

  Maybe in ubuntu, the audio port is being initialized with speakers at
  boot time, and it is not verifying the aux outputs for listeners, to
  initialize with that.

  Maybe this should be a new feature.

  The feature would be to scan the audio ports at boot time, to see if
  any auxiliary ports are found. Not sure if multiple can be found.
  Initialize with whatever state would be if those auxiliary ports where
  plugged in one at a time, and not found like this. The initial state
  should not always be the default audio port.

  Thank you for understanding, and please let me know if you what i
  mean.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  catalinstan   2906 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb 10 23:02:24 2019
  InstallationDate: Installed on 2018-06-25 (230 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Front
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [Latitude 7490, Realtek ALC3246, Black Headphone Out, Front] Playback 
problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/26/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.2
  dmi.board.name: 0KP0FT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.2:bd11/26/2018:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0KP0FT:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7490
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1815384/+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 1816271] Re: [ALC269VC Analog] No sound on ThinkPad T530 until headphones are re-plugged in

[Kris M]

*** This bug is a duplicate of bug 1583801 ***
https://bugs.launchpad.net/bugs/1583801

note - I get no sound after boot whether or not headphones are plugged
in.

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

Title:
  [ALC269VC Analog] No sound on ThinkPad T530 until headphones are re-
  plugged in

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  19.04,kern 4.19.0-13
  just took update and now does not recognize soundcard or something plugged in 
to headphones jack. pulled bug. Now if I unplug headphones and plug back in, it 
wakes up and recognizes it and works fine. I thought I had this prob a few days 
ago and restored back to the 10th, and updated all but alsa and worked fine. 
This morning I checked and a bunch of alsa stuff was no longer showing in 
updates, took everything, and worked fine. Just took updates (Software 
Updater), and checked speakers and no go. When this happened, it also would not 
allow sound to HDTV via HDMI, no matter what. Just tested and was able to get 
sound via hdmi, but remember, I have already "woken it up" by unplugging and 
plugging headphones (actually sony vaio computer speakers)
  ThinkPad T530-2394-3J8, i5-3380M 2.9GHz, Dual boot (BIOS/MBR): Grub, Ubuntu 
19.04dev / Win7 Pro x64 . 8GB(15GB/s), Sammy 250GB SSD. Fast!

  I expected sound to recognize soundcard/speakers. It did not until I
  unplug/replug headphones.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gstreamer1.0-plugins-good 1.15.1-1ubuntu2
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 16 19:20:26 2019
  InstallationDate: Installed on 2019-02-09 (7 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gst-plugins-good1.0
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kris   1512 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-02-09 (8 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  Package: pulseaudio 1:12.2-2ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Tags:  disco
  Uname: Linux 4.19.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/23/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G4ETB4WW (2.74 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 23943J8
  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:bvrG4ETB4WW(2.74):bd11/23/2018:svnLENOVO:pn23943J8:pvrThinkPadT530:rvnLENOVO:rn23943J8:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T530
  dmi.product.name: 23943J8
  dmi.product.sku: LENOVO_MT_2394
  dmi.product.version: ThinkPad T530
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1816271/+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 1816271] Re: [ALC269VC Analog] No sound on ThinkPad T530 until headphones are re-plugged in

[Kris M]

dpkg -l > allpackages.txt

** Attachment added: "result of dpkg -l > allpackages.txt"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1816271/+attachment/5239570/+files/allpackages.txt

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

Title:
  [ALC269VC Analog] No sound on ThinkPad T530 until headphones are re-
  plugged in

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  19.04,kern 4.19.0-13
  just took update and now does not recognize soundcard or something plugged in 
to headphones jack. pulled bug. Now if I unplug headphones and plug back in, it 
wakes up and recognizes it and works fine. I thought I had this prob a few days 
ago and restored back to the 10th, and updated all but alsa and worked fine. 
This morning I checked and a bunch of alsa stuff was no longer showing in 
updates, took everything, and worked fine. Just took updates (Software 
Updater), and checked speakers and no go. When this happened, it also would not 
allow sound to HDTV via HDMI, no matter what. Just tested and was able to get 
sound via hdmi, but remember, I have already "woken it up" by unplugging and 
plugging headphones (actually sony vaio computer speakers)
  ThinkPad T530-2394-3J8, i5-3380M 2.9GHz, Dual boot (BIOS/MBR): Grub, Ubuntu 
19.04dev / Win7 Pro x64 . 8GB(15GB/s), Sammy 250GB SSD. Fast!

  I expected sound to recognize soundcard/speakers. It did not until I
  unplug/replug headphones.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gstreamer1.0-plugins-good 1.15.1-1ubuntu2
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 16 19:20:26 2019
  InstallationDate: Installed on 2019-02-09 (7 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gst-plugins-good1.0
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kris   1512 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-02-09 (8 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  Package: pulseaudio 1:12.2-2ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Tags:  disco
  Uname: Linux 4.19.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/23/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G4ETB4WW (2.74 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 23943J8
  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:bvrG4ETB4WW(2.74):bd11/23/2018:svnLENOVO:pn23943J8:pvrThinkPadT530:rvnLENOVO:rn23943J8:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T530
  dmi.product.name: 23943J8
  dmi.product.sku: LENOVO_MT_2394
  dmi.product.version: ThinkPad T530
  dmi.sys.vendor: LENOVO

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

[Kris M]

1200 line text file attached:
(boot)
pactl list
aplay -l
-unplug headphones, replug headphones
pactl list
aplay -l

** Attachment added: "txt file copied from terminal"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1816271/+attachment/5239443/+files/sound.txt

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

Title:
  [ALC269VC Analog] No sound on ThinkPad T530 until headphones are re-
  plugged in

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  19.04,kern 4.19.0-13
  just took update and now does not recognize soundcard or something plugged in 
to headphones jack. pulled bug. Now if I unplug headphones and plug back in, it 
wakes up and recognizes it and works fine. I thought I had this prob a few days 
ago and restored back to the 10th, and updated all but alsa and worked fine. 
This morning I checked and a bunch of alsa stuff was no longer showing in 
updates, took everything, and worked fine. Just took updates (Software 
Updater), and checked speakers and no go. When this happened, it also would not 
allow sound to HDTV via HDMI, no matter what. Just tested and was able to get 
sound via hdmi, but remember, I have already "woken it up" by unplugging and 
plugging headphones (actually sony vaio computer speakers)
  ThinkPad T530-2394-3J8, i5-3380M 2.9GHz, Dual boot (BIOS/MBR): Grub, Ubuntu 
19.04dev / Win7 Pro x64 . 8GB(15GB/s), Sammy 250GB SSD. Fast!

  I expected sound to recognize soundcard/speakers. It did not until I
  unplug/replug headphones.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gstreamer1.0-plugins-good 1.15.1-1ubuntu2
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 16 19:20:26 2019
  InstallationDate: Installed on 2019-02-09 (7 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gst-plugins-good1.0
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kris   1512 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-02-09 (8 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  Package: pulseaudio 1:12.2-2ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Tags:  disco
  Uname: Linux 4.19.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/23/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G4ETB4WW (2.74 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 23943J8
  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:bvrG4ETB4WW(2.74):bd11/23/2018:svnLENOVO:pn23943J8:pvrThinkPadT530:rvnLENOVO:rn23943J8:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T530
  dmi.product.name: 23943J8
  dmi.product.sku: LENOVO_MT_2394
  dmi.product.version: ThinkPad T530
  dmi.sys.vendor: LENOVO

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

[Kris M]

some info manually copied:
pulseaudio 1:12.2-2ubuntu1

ALSA version
Driver version: k4.19.0-13-generic
library version 1.1.8
utilities version 1.1.7

loaded ALSA modules
snd_hda_intel

Pulseaudio
installed - yes
running - yes

soundcards recognized by alsa
0[PCH  ]:HDA-intel - HDA Intel PCH
HDA Intel PCH at 0xf253 irq 32

pci soundcards installed on system
00:1b.0 audeo device : intel corp 7 series/C216chipset family

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

Title:
  no sound

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  19.04,kern 4.19.0-13
  just took update and now does not recognize soundcard or something plugged in 
to headphones jack. pulled bug. Now if I unplug headphones and plug back in, it 
wakes up and recognizes it and works fine. I thought I had this prob a few days 
ago and restored back to the 10th, and updated all but alsa and worked fine. 
This morning I checked and a bunch of alsa stuff was no longer showing in 
updates, took everything, and worked fine. Just took updates (Software 
Updater), and checked speakers and no go. When this happened, it also would not 
allow sound to HDTV via HDMI, no matter what. Just tested and was able to get 
sound via hdmi, but remember, I have already "woken it up" by unplugging and 
plugging headphones (actually sony vaio computer speakers)
  ThinkPad T530-2394-3J8, i5-3380M 2.9GHz, Dual boot (BIOS/MBR): Grub, Ubuntu 
19.04dev / Win7 Pro x64 . 8GB(15GB/s), Sammy 250GB SSD. Fast!

  I expected sound to recognize soundcard/speakers. It did not until I
  unplug/replug headphones.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gstreamer1.0-plugins-good 1.15.1-1ubuntu2
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 16 19:20:26 2019
  InstallationDate: Installed on 2019-02-09 (7 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gst-plugins-good1.0
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kris   1512 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-02-09 (8 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  Package: pulseaudio 1:12.2-2ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Tags:  disco
  Uname: Linux 4.19.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/23/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G4ETB4WW (2.74 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 23943J8
  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:bvrG4ETB4WW(2.74):bd11/23/2018:svnLENOVO:pn23943J8:pvrThinkPadT530:rvnLENOVO:rn23943J8:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T530
  dmi.product.name: 23943J8
  dmi.product.sku: LENOVO_MT_2394
  dmi.product.version: ThinkPad T530
  dmi.sys.vendor: LENOVO

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

[Kris M]

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1816271/+attachment/5239416/+files/Dependencies.txt

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

Title:
  no sound

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  19.04,kern 4.19.0-13
  just took update and now does not recognize soundcard or something plugged in 
to headphones jack. pulled bug. Now if I unplug headphones and plug back in, it 
wakes up and recognizes it and works fine. I thought I had this prob a few days 
ago and restored back to the 10th, and updated all but alsa and worked fine. 
This morning I checked and a bunch of alsa stuff was no longer showing in 
updates, took everything, and worked fine. Just took updates (Software 
Updater), and checked speakers and no go. When this happened, it also would not 
allow sound to HDTV via HDMI, no matter what. Just tested and was able to get 
sound via hdmi, but remember, I have already "woken it up" by unplugging and 
plugging headphones (actually sony vaio computer speakers)
  ThinkPad T530-2394-3J8, i5-3380M 2.9GHz, Dual boot (BIOS/MBR): Grub, Ubuntu 
19.04dev / Win7 Pro x64 . 8GB(15GB/s), Sammy 250GB SSD. Fast!

  I expected sound to recognize soundcard/speakers. It did not until I
  unplug/replug headphones.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gstreamer1.0-plugins-good 1.15.1-1ubuntu2
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 16 19:20:26 2019
  InstallationDate: Installed on 2019-02-09 (7 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gst-plugins-good1.0
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kris   1512 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-02-09 (8 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  Package: pulseaudio 1:12.2-2ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Tags:  disco
  Uname: Linux 4.19.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/23/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G4ETB4WW (2.74 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 23943J8
  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:bvrG4ETB4WW(2.74):bd11/23/2018:svnLENOVO:pn23943J8:pvrThinkPadT530:rvnLENOVO:rn23943J8:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T530
  dmi.product.name: 23943J8
  dmi.product.sku: LENOVO_MT_2394
  dmi.product.version: ThinkPad T530
  dmi.sys.vendor: LENOVO

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

[Kris M]

Tried.

DID:
kris@kris-ThinkPad-T530:~$ apport-collect 1816271
The authorization page:
 
(https://launchpad.net/+authorize-token?oauth_token=K44nhP8rLb86KwxBJ2rd_permission=DESKTOP_INTEGRATION)
should be opening in your browser. Use your browser to authorize
this program to access Launchpad on your behalf.
Waiting to hear from Launchpad about your decision...
kris@kris-ThinkPad-T530:~$ 

-I then allowed it for 1HR. Then refreshed page and :

GOT:

Authorize application to access Launchpad on your behalf
Unable to identify application

The information provided by the remote application was incorrect or
incomplete. Because of that we were unable to identify the application
which would access Launchpad on your behalf.

You may have already authorized this application.

See all applications authorized to access Launchpad on your behalf.

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

Title:
  no sound

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  19.04,kern 4.19.0-13
  just took update and now does not recognize soundcard or something plugged in 
to headphones jack. pulled bug. Now if I unplug headphones and plug back in, it 
wakes up and recognizes it and works fine. I thought I had this prob a few days 
ago and restored back to the 10th, and updated all but alsa and worked fine. 
This morning I checked and a bunch of alsa stuff was no longer showing in 
updates, took everything, and worked fine. Just took updates (Software 
Updater), and checked speakers and no go. When this happened, it also would not 
allow sound to HDTV via HDMI, no matter what. Just tested and was able to get 
sound via hdmi, but remember, I have already "woken it up" by unplugging and 
plugging headphones (actually sony vaio computer speakers)
  ThinkPad T530-2394-3J8, i5-3380M 2.9GHz, Dual boot (BIOS/MBR): Grub, Ubuntu 
19.04dev / Win7 Pro x64 . 8GB(15GB/s), Sammy 250GB SSD. Fast!

  I expected sound to recognize soundcard/speakers. It did not until I
  unplug/replug headphones.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gstreamer1.0-plugins-good 1.15.1-1ubuntu2
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 16 19:20:26 2019
  InstallationDate: Installed on 2019-02-09 (7 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gst-plugins-good1.0
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kris   1512 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-02-09 (8 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  Package: pulseaudio 1:12.2-2ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Tags:  disco
  Uname: Linux 4.19.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/23/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G4ETB4WW (2.74 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 23943J8
  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:bvrG4ETB4WW(2.74):bd11/23/2018:svnLENOVO:pn23943J8:pvrThinkPadT530:rvnLENOVO:rn23943J8:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T530
  dmi.product.name: 23943J8
  dmi.product.sku: LENOVO_MT_2394
  dmi.product.version: ThinkPad T530
  dmi.sys.vendor: LENOVO

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

[Kris M]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1816271/+attachment/5239418/+files/PulseList.txt

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

Title:
  no sound

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  19.04,kern 4.19.0-13
  just took update and now does not recognize soundcard or something plugged in 
to headphones jack. pulled bug. Now if I unplug headphones and plug back in, it 
wakes up and recognizes it and works fine. I thought I had this prob a few days 
ago and restored back to the 10th, and updated all but alsa and worked fine. 
This morning I checked and a bunch of alsa stuff was no longer showing in 
updates, took everything, and worked fine. Just took updates (Software 
Updater), and checked speakers and no go. When this happened, it also would not 
allow sound to HDTV via HDMI, no matter what. Just tested and was able to get 
sound via hdmi, but remember, I have already "woken it up" by unplugging and 
plugging headphones (actually sony vaio computer speakers)
  ThinkPad T530-2394-3J8, i5-3380M 2.9GHz, Dual boot (BIOS/MBR): Grub, Ubuntu 
19.04dev / Win7 Pro x64 . 8GB(15GB/s), Sammy 250GB SSD. Fast!

  I expected sound to recognize soundcard/speakers. It did not until I
  unplug/replug headphones.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gstreamer1.0-plugins-good 1.15.1-1ubuntu2
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 16 19:20:26 2019
  InstallationDate: Installed on 2019-02-09 (7 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gst-plugins-good1.0
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kris   1512 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-02-09 (8 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  Package: pulseaudio 1:12.2-2ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Tags:  disco
  Uname: Linux 4.19.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/23/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G4ETB4WW (2.74 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 23943J8
  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:bvrG4ETB4WW(2.74):bd11/23/2018:svnLENOVO:pn23943J8:pvrThinkPadT530:rvnLENOVO:rn23943J8:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T530
  dmi.product.name: 23943J8
  dmi.product.sku: LENOVO_MT_2394
  dmi.product.version: ThinkPad T530
  dmi.sys.vendor: LENOVO

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

[Kris M]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1816271/+attachment/5239417/+files/ProcCpuinfoMinimal.txt

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

Title:
  no sound

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  19.04,kern 4.19.0-13
  just took update and now does not recognize soundcard or something plugged in 
to headphones jack. pulled bug. Now if I unplug headphones and plug back in, it 
wakes up and recognizes it and works fine. I thought I had this prob a few days 
ago and restored back to the 10th, and updated all but alsa and worked fine. 
This morning I checked and a bunch of alsa stuff was no longer showing in 
updates, took everything, and worked fine. Just took updates (Software 
Updater), and checked speakers and no go. When this happened, it also would not 
allow sound to HDTV via HDMI, no matter what. Just tested and was able to get 
sound via hdmi, but remember, I have already "woken it up" by unplugging and 
plugging headphones (actually sony vaio computer speakers)
  ThinkPad T530-2394-3J8, i5-3380M 2.9GHz, Dual boot (BIOS/MBR): Grub, Ubuntu 
19.04dev / Win7 Pro x64 . 8GB(15GB/s), Sammy 250GB SSD. Fast!

  I expected sound to recognize soundcard/speakers. It did not until I
  unplug/replug headphones.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gstreamer1.0-plugins-good 1.15.1-1ubuntu2
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 16 19:20:26 2019
  InstallationDate: Installed on 2019-02-09 (7 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gst-plugins-good1.0
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kris   1512 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-02-09 (8 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  Package: pulseaudio 1:12.2-2ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Tags:  disco
  Uname: Linux 4.19.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/23/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G4ETB4WW (2.74 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 23943J8
  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:bvrG4ETB4WW(2.74):bd11/23/2018:svnLENOVO:pn23943J8:pvrThinkPadT530:rvnLENOVO:rn23943J8:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T530
  dmi.product.name: 23943J8
  dmi.product.sku: LENOVO_MT_2394
  dmi.product.version: ThinkPad T530
  dmi.sys.vendor: LENOVO

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

[Kris M]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1816271/+attachment/5239415/+files/CurrentDmesg.txt

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

Title:
  no sound

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  19.04,kern 4.19.0-13
  just took update and now does not recognize soundcard or something plugged in 
to headphones jack. pulled bug. Now if I unplug headphones and plug back in, it 
wakes up and recognizes it and works fine. I thought I had this prob a few days 
ago and restored back to the 10th, and updated all but alsa and worked fine. 
This morning I checked and a bunch of alsa stuff was no longer showing in 
updates, took everything, and worked fine. Just took updates (Software 
Updater), and checked speakers and no go. When this happened, it also would not 
allow sound to HDTV via HDMI, no matter what. Just tested and was able to get 
sound via hdmi, but remember, I have already "woken it up" by unplugging and 
plugging headphones (actually sony vaio computer speakers)
  ThinkPad T530-2394-3J8, i5-3380M 2.9GHz, Dual boot (BIOS/MBR): Grub, Ubuntu 
19.04dev / Win7 Pro x64 . 8GB(15GB/s), Sammy 250GB SSD. Fast!

  I expected sound to recognize soundcard/speakers. It did not until I
  unplug/replug headphones.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gstreamer1.0-plugins-good 1.15.1-1ubuntu2
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 16 19:20:26 2019
  InstallationDate: Installed on 2019-02-09 (7 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gst-plugins-good1.0
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kris   1512 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-02-09 (8 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  Package: pulseaudio 1:12.2-2ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Tags:  disco
  Uname: Linux 4.19.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/23/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G4ETB4WW (2.74 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 23943J8
  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:bvrG4ETB4WW(2.74):bd11/23/2018:svnLENOVO:pn23943J8:pvrThinkPadT530:rvnLENOVO:rn23943J8:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T530
  dmi.product.name: 23943J8
  dmi.product.sku: LENOVO_MT_2394
  dmi.product.version: ThinkPad T530
  dmi.sys.vendor: LENOVO

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

[Kris M]

apport information

** Tags added: apport-collected

** Description changed:

  19.04,kern 4.19.0-13
  just took update and now does not recognize soundcard or something plugged in 
to headphones jack. pulled bug. Now if I unplug headphones and plug back in, it 
wakes up and recognizes it and works fine. I thought I had this prob a few days 
ago and restored back to the 10th, and updated all but alsa and worked fine. 
This morning I checked and a bunch of alsa stuff was no longer showing in 
updates, took everything, and worked fine. Just took updates (Software 
Updater), and checked speakers and no go. When this happened, it also would not 
allow sound to HDTV via HDMI, no matter what. Just tested and was able to get 
sound via hdmi, but remember, I have already "woken it up" by unplugging and 
plugging headphones (actually sony vaio computer speakers)
  ThinkPad T530-2394-3J8, i5-3380M 2.9GHz, Dual boot (BIOS/MBR): Grub, Ubuntu 
19.04dev / Win7 Pro x64 . 8GB(15GB/s), Sammy 250GB SSD. Fast!
  
  I expected sound to recognize soundcard/speakers. It did not until I
  unplug/replug headphones.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gstreamer1.0-plugins-good 1.15.1-1ubuntu2
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 16 19:20:26 2019
  InstallationDate: Installed on 2019-02-09 (7 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gst-plugins-good1.0
  UpgradeStatus: No upgrade log present (probably fresh install)
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.10-0ubuntu21
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  kris   1512 F pulseaudio
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 19.04
+ InstallationDate: Installed on 2019-02-09 (8 days ago)
+ InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
+ Package: pulseaudio 1:12.2-2ubuntu1
+ PackageArchitecture: amd64
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
+ Tags:  disco
+ Uname: Linux 4.19.0-13-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 11/23/2018
+ dmi.bios.vendor: LENOVO
+ dmi.bios.version: G4ETB4WW (2.74 )
+ dmi.board.asset.tag: Not Available
+ dmi.board.name: 23943J8
+ 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:bvrG4ETB4WW(2.74):bd11/23/2018:svnLENOVO:pn23943J8:pvrThinkPadT530:rvnLENOVO:rn23943J8:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
+ dmi.product.family: ThinkPad T530
+ dmi.product.name: 23943J8
+ dmi.product.sku: LENOVO_MT_2394
+ dmi.product.version: ThinkPad T530
+ dmi.sys.vendor: LENOVO

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1816271/+attachment/5239414/+files/AlsaInfo.txt

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

Title:
  no sound

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  19.04,kern 4.19.0-13
  just took update and now does not recognize soundcard or something plugged in 
to headphones jack. pulled bug. Now if I unplug headphones and plug back in, it 
wakes up and recognizes it and works fine. I thought I had this prob a few days 
ago and restored back to the 10th, and updated all but alsa and worked fine. 
This morning I checked and a bunch of alsa stuff was no longer showing in 
updates, took everything, and worked fine. Just took updates (Software 
Updater), and checked speakers and no go. When this happened, it also would not 
allow sound to HDTV via HDMI, no matter what. Just tested and was able to get 
sound via hdmi, but remember, I have already "woken it up" by unplugging and 
plugging headphones (actually sony vaio computer speakers)
  ThinkPad T530-2394-3J8, i5-3380M 2.9GHz, Dual boot (BIOS/MBR): Grub, Ubuntu 
19.04dev / Win7 Pro x64 . 8GB(15GB/s), Sammy 250GB SSD. Fast!

  I expected sound to recognize soundcard/speakers. It did not until I
  unplug/replug headphones.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gstreamer1.0-plugins-good 1.15.1-1ubuntu2
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  ApportVersion: 2.20.1

[Desktop-packages] [Bug 1816271] Re: no sound

[Kris M]

please note - there has been at least 1 pulseaudio update and many alsa
updates since the 10th Feb.

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

Title:
  no sound

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  19.04,kern 4.19.0-13
  just took update and now does not recognize soundcard or something plugged in 
to headphones jack. pulled bug. Now if I unplug headphones and plug back in, it 
wakes up and recognizes it and works fine. I thought I had this prob a few days 
ago and restored back to the 10th, and updated all but alsa and worked fine. 
This morning I checked and a bunch of alsa stuff was no longer showing in 
updates, took everything, and worked fine. Just took updates (Software 
Updater), and checked speakers and no go. When this happened, it also would not 
allow sound to HDTV via HDMI, no matter what. Just tested and was able to get 
sound via hdmi, but remember, I have already "woken it up" by unplugging and 
plugging headphones (actually sony vaio computer speakers)
  ThinkPad T530-2394-3J8, i5-3380M 2.9GHz, Dual boot (BIOS/MBR): Grub, Ubuntu 
19.04dev / Win7 Pro x64 . 8GB(15GB/s), Sammy 250GB SSD. Fast!

  I expected sound to recognize soundcard/speakers. It did not until I
  unplug/replug headphones.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gstreamer1.0-plugins-good 1.15.1-1ubuntu2
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 16 19:20:26 2019
  InstallationDate: Installed on 2019-02-09 (7 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gst-plugins-good1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

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

[Kris M]

another user's comments:
 Re: Broken output sound

Your screenshots are the same as mines when i've got that issue.
How it had happened on my system:
- a couple days ago, made the usual daily upgrades from 'proposed', 
including gvfs, pulseaudio, alsa and the likes. Sound was working before and 
after the upgrades.
- with the next cold boot, i first upgrade some other releases (bionic, 
cosmic, bulleyes), the sound was was ok on each ones.
- next cold boot on Disco, kernel 13, and that sound issue appeared; i've 
closed and reopened the session, but that did not solved the problem.
- rebooting with the kernel 12 and there the sound was ok; in fact i should 
say that the system had found and well identified the mobo sound chipset.
- since, i have made many cold boots and sound is now always working.

So it looks like the upgrade process has disturbed, at boot time,
the sound chipset discovery; is it the gcc8/9 switch to blame ?

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

Title:
  no sound

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  19.04,kern 4.19.0-13
  just took update and now does not recognize soundcard or something plugged in 
to headphones jack. pulled bug. Now if I unplug headphones and plug back in, it 
wakes up and recognizes it and works fine. I thought I had this prob a few days 
ago and restored back to the 10th, and updated all but alsa and worked fine. 
This morning I checked and a bunch of alsa stuff was no longer showing in 
updates, took everything, and worked fine. Just took updates (Software 
Updater), and checked speakers and no go. When this happened, it also would not 
allow sound to HDTV via HDMI, no matter what. Just tested and was able to get 
sound via hdmi, but remember, I have already "woken it up" by unplugging and 
plugging headphones (actually sony vaio computer speakers)
  ThinkPad T530-2394-3J8, i5-3380M 2.9GHz, Dual boot (BIOS/MBR): Grub, Ubuntu 
19.04dev / Win7 Pro x64 . 8GB(15GB/s), Sammy 250GB SSD. Fast!

  I expected sound to recognize soundcard/speakers. It did not until I
  unplug/replug headphones.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gstreamer1.0-plugins-good 1.15.1-1ubuntu2
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 16 19:20:26 2019
  InstallationDate: Installed on 2019-02-09 (7 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gst-plugins-good1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

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

[Kris M]

** Attachment added: "sound after boot, AFTER I unplug/replug headphones."
   
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good1.0/+bug/1816271/+attachment/5239199/+files/Screenshot%20from%202019-02-16%2019-59-54.png

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

Title:
  no sound

Status in gst-plugins-good1.0 package in Ubuntu:
  New

Bug description:
  19.04,kern 4.19.0-13
  just took update and now does not recognize soundcard or something plugged in 
to headphones jack. pulled bug. Now if I unplug headphones and plug back in, it 
wakes up and recognizes it and works fine. I thought I had this prob a few days 
ago and restored back to the 10th, and updated all but alsa and worked fine. 
This morning I checked and a bunch of alsa stuff was no longer showing in 
updates, took everything, and worked fine. Just took updates (Software 
Updater), and checked speakers and no go. When this happened, it also would not 
allow sound to HDTV via HDMI, no matter what. Just tested and was able to get 
sound via hdmi, but remember, I have already "woken it up" by unplugging and 
plugging headphones (actually sony vaio computer speakers)
  ThinkPad T530-2394-3J8, i5-3380M 2.9GHz, Dual boot (BIOS/MBR): Grub, Ubuntu 
19.04dev / Win7 Pro x64 . 8GB(15GB/s), Sammy 250GB SSD. Fast!
  kris@kris-ThinkPad-T530:~$ lsb_release -rd
  Description:  Ubuntu Disco Dingo (development branch)
  Release:      19.04
  kris@kris-ThinkPad-T530:~$ 

  kris@kris-ThinkPad-T530:~$ uname -a
  Linux kris-ThinkPad-T530 4.19.0-13-generic #14-Ubuntu SMP Thu Feb 7 21:51:25 
UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
  kris@kris-ThinkPad-T530:~$ 

  kris@kris-ThinkPad-T530:~$ apt-cache policy pkgname
  N: Unable to locate package pkgname
  kris@kris-ThinkPad-T530:~$ 

  I expected sound to recognize soundcard/speakers. It did not until I
  unplug/replug headphones.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gstreamer1.0-plugins-good 1.15.1-1ubuntu2
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 16 19:20:26 2019
  InstallationDate: Installed on 2019-02-09 (7 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gst-plugins-good1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good1.0/+bug/1816271/+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 1816271] Re: no sound

[Kris M]

** Attachment added: "sound after boot"
   
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good1.0/+bug/1816271/+attachment/5239198/+files/Screenshot%20from%202019-02-16%2019-59-01.png

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

Title:
  no sound

Status in gst-plugins-good1.0 package in Ubuntu:
  New

Bug description:
  19.04,kern 4.19.0-13
  just took update and now does not recognize soundcard or something plugged in 
to headphones jack. pulled bug. Now if I unplug headphones and plug back in, it 
wakes up and recognizes it and works fine. I thought I had this prob a few days 
ago and restored back to the 10th, and updated all but alsa and worked fine. 
This morning I checked and a bunch of alsa stuff was no longer showing in 
updates, took everything, and worked fine. Just took updates (Software 
Updater), and checked speakers and no go. When this happened, it also would not 
allow sound to HDTV via HDMI, no matter what. Just tested and was able to get 
sound via hdmi, but remember, I have already "woken it up" by unplugging and 
plugging headphones (actually sony vaio computer speakers)
  ThinkPad T530-2394-3J8, i5-3380M 2.9GHz, Dual boot (BIOS/MBR): Grub, Ubuntu 
19.04dev / Win7 Pro x64 . 8GB(15GB/s), Sammy 250GB SSD. Fast!
  kris@kris-ThinkPad-T530:~$ lsb_release -rd
  Description:  Ubuntu Disco Dingo (development branch)
  Release:      19.04
  kris@kris-ThinkPad-T530:~$ 

  kris@kris-ThinkPad-T530:~$ uname -a
  Linux kris-ThinkPad-T530 4.19.0-13-generic #14-Ubuntu SMP Thu Feb 7 21:51:25 
UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
  kris@kris-ThinkPad-T530:~$ 

  kris@kris-ThinkPad-T530:~$ apt-cache policy pkgname
  N: Unable to locate package pkgname
  kris@kris-ThinkPad-T530:~$ 

  I expected sound to recognize soundcard/speakers. It did not until I
  unplug/replug headphones.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gstreamer1.0-plugins-good 1.15.1-1ubuntu2
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 16 19:20:26 2019
  InstallationDate: Installed on 2019-02-09 (7 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gst-plugins-good1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good1.0/+bug/1816271/+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 1816271] [NEW] no sound

[Kris M]

Public bug reported:

19.04,kern 4.19.0-13
just took update and now does not recognize soundcard or something plugged in 
to headphones jack. pulled bug. Now if I unplug headphones and plug back in, it 
wakes up and recognizes it and works fine. I thought I had this prob a few days 
ago and restored back to the 10th, and updated all but alsa and worked fine. 
This morning I checked and a bunch of alsa stuff was no longer showing in 
updates, took everything, and worked fine. Just took updates (Software 
Updater), and checked speakers and no go. When this happened, it also would not 
allow sound to HDTV via HDMI, no matter what. Just tested and was able to get 
sound via hdmi, but remember, I have already "woken it up" by unplugging and 
plugging headphones (actually sony vaio computer speakers)
ThinkPad T530-2394-3J8, i5-3380M 2.9GHz, Dual boot (BIOS/MBR): Grub, Ubuntu 
19.04dev / Win7 Pro x64 . 8GB(15GB/s), Sammy 250GB SSD. Fast!
kris@kris-ThinkPad-T530:~$ lsb_release -rd
Description:Ubuntu Disco Dingo (development branch)
Release:19.04
kris@kris-ThinkPad-T530:~$ 

kris@kris-ThinkPad-T530:~$ uname -a
Linux kris-ThinkPad-T530 4.19.0-13-generic #14-Ubuntu SMP Thu Feb 7 21:51:25 
UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
kris@kris-ThinkPad-T530:~$ 

kris@kris-ThinkPad-T530:~$ apt-cache policy pkgname
N: Unable to locate package pkgname
kris@kris-ThinkPad-T530:~$ 

I expected sound to recognize soundcard/speakers. It did not until I
unplug/replug headphones.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gstreamer1.0-plugins-good 1.15.1-1ubuntu2
ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
Uname: Linux 4.19.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu21
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb 16 19:20:26 2019
InstallationDate: Installed on 2019-02-09 (7 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gst-plugins-good1.0
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gst-plugins-good1.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug disco

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

Title:
  no sound

Status in gst-plugins-good1.0 package in Ubuntu:
  New

Bug description:
  19.04,kern 4.19.0-13
  just took update and now does not recognize soundcard or something plugged in 
to headphones jack. pulled bug. Now if I unplug headphones and plug back in, it 
wakes up and recognizes it and works fine. I thought I had this prob a few days 
ago and restored back to the 10th, and updated all but alsa and worked fine. 
This morning I checked and a bunch of alsa stuff was no longer showing in 
updates, took everything, and worked fine. Just took updates (Software 
Updater), and checked speakers and no go. When this happened, it also would not 
allow sound to HDTV via HDMI, no matter what. Just tested and was able to get 
sound via hdmi, but remember, I have already "woken it up" by unplugging and 
plugging headphones (actually sony vaio computer speakers)
  ThinkPad T530-2394-3J8, i5-3380M 2.9GHz, Dual boot (BIOS/MBR): Grub, Ubuntu 
19.04dev / Win7 Pro x64 . 8GB(15GB/s), Sammy 250GB SSD. Fast!
  kris@kris-ThinkPad-T530:~$ lsb_release -rd
  Description:  Ubuntu Disco Dingo (development branch)
  Release:  19.04
  kris@kris-ThinkPad-T530:~$ 

  kris@kris-ThinkPad-T530:~$ uname -a
  Linux kris-ThinkPad-T530 4.19.0-13-generic #14-Ubuntu SMP Thu Feb 7 21:51:25 
UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
  kris@kris-ThinkPad-T530:~$ 

  kris@kris-ThinkPad-T530:~$ apt-cache policy pkgname
  N: Unable to locate package pkgname
  kris@kris-ThinkPad-T530:~$ 

  I expected sound to recognize soundcard/speakers. It did not until I
  unplug/replug headphones.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gstreamer1.0-plugins-good 1.15.1-1ubuntu2
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 16 19:20:26 2019
  InstallationDate: Installed on 2019-02-09 (7 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gst-plugins-good1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good1.0/+bug/1816271/+subscriptions

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

[Desktop-packages] [Bug 1797945] Re: Lightning incompatible with Thunderbird 60.2.1

[Piraten-Kris Pseudonym]

EN:Correction (DE:Korrektur)

EN: Note: 
This may be fixed in some Weeks, Months, or Years, so maybe you can try first:
 > Thunderbird > Add-Ons > Extensions > Search for: Lightning > Install.
Problem: 
If you use Ubuntu-Linux or another Debian-Derivative, Lightning is not included 
in Thunderbird 60+ and the Update will break your Calendar (incompatible, not 
compatible). xul-ext-lightning is not international. There is no Language-Pack 
for Lightning available. The normal Search for Add-On leads to an incompatible 
Version. Someone told me, the Beta was not recommended.
---
Workaround:
 1.> Lookup your Version of Thunderbird:
   > =Menu > Help > About Mozilla Thunderbird 
 2.> Download the same Version of Thunderbird fitting for you from here:
https://ftp.mozilla.org/pub/thunderbird/releases/
 3.> Open File with an Archive-Program(Unzipper)
   > (Usually just > Double-Click or > Right-Click > open ..)
 4.> Goto > thunderbird > distribution > extensions >
 5.> {e2fda1a4-762b-4020-b5ad-a41df1933103}.xpi (=Lightning) > Extract
 6.> Open your installed Thunderbird > Add-Ons > Extensions
 7.> (Remove unwanted english Version of Lightning: )
   > (Terminal > sudo apt remove xul-ext-lightning)
 8.> Gear-Wheel-Button next to the Search-Box
 9.> Install Add-on From File
 10.> Select Download-Folder and the .XPI-File > Install
=> All your Calendar-Data should be back. :-)
-
DE: Hinweis: 
Dies mag in einigen Wochen, Monaten oder Jahren behoben sein. Probiere zuerst
 > Thunderbird > Add-Ons > Erweiterungen > Suche nach: Lightning > Installieren.
Problem: 
Wenn du Ubuntu-Linux oder einen anderen Debian-Abkömmling benutzt, ist 
Lightning nicht in Thunderbird 60+ enthalten und ein Update wird den Kalender 
abschalten  (inkompatibel, nicht kompatibel). xul-ext-lightning ist nicht 
international. Es ist kein Sprach-Paket für Lightning verfügbar. Die normale 
Suche nach Add-On führt zu einer inkompatiblen Version. Jemand sagte mir, die 
Beta sei nicht empfohlen.
---
Hilfs-Lösung:
 1.> Sieh nach, welche Version von Thunderbird du hast:
   > =Menü > Hilfe > Über Mozilla Thunderbird 
 2.> Lade die selbe Version von Thunderbird passend für dich von dort:
https://ftp.mozilla.org/pub/thunderbird/releases/
 3.> Öffne die Datei mit einem Archiv-Programm(Unzipper) 
   > (normalerweise nur > Doppelklick oder > Rechtsklick > öffnen ..)
 4.> Gehe dort zu > thunderbird > distribution > extensions >
 5.> {e2fda1a4-762b-4020-b5ad-a41df1933103}.xpi (=Lightning) > Entpacken
 6.> Öffne dein installiertes Thunderbird > Add-Ons > Erweiterungen
 7.> (Entferne die unerwünschte englische Version von Lightning:)
   > (Terminal > sudo apt remove xul-ext-lightning)
 8.> Zahnrad-Knopf neben dem Suchfeld
 9.> Add-on aus Datei installieren
 10.> Wähle den Download-Ordner und die .XPI-Datei > Installieren
=> Alle deine Kalender-Daten sollten wieder da sein. :-)

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

Title:
  Lightning incompatible with Thunderbird 60.2.1

Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  Hi

  Today I got the update from Thunderbird 52 to 60.2.1. Unfortunately
  Lightning doesn't work anymore.

  Thunderbird reports that Lightning is incompatible with Thunderbird
  60.2.1.

  Regards,

  Ettore

  --

  WORKAROUNDS:

  Until this is fixed (as per the problems listed in #25), pick an
  answer that works best for you (English vs. other languages) at
  https://askubuntu.com/questions/1084059/latest-update-to-
  thunderbird-60-2-1-on-18-04-lightning-calendar-missing .

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1797945/+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 1798034] Re: Package xul-ext-lightning is in English only

[Piraten-Kris Pseudonym]

*** This bug is a duplicate of bug 545778 ***
https://bugs.launchpad.net/bugs/545778

** This bug has been marked a duplicate of bug 545778
   xul-ext-lightning is only available in English

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

Title:
  Package xul-ext-lightning is in English only

Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  Thunderbird just updated to version 60.2 in Ubuntu 16.04 and I lost
  access to Lightning. I had Lightning 5.4 installed using Thunderbird
  add-ons, but no version compatible with TB 60.2 is available there.

  The package xul-ext-lightning is available and works with TB 60.2, but
  it's in English only.

  Now that Lightning is no longer available otherwise, the package needs
  to come with all the various language versions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1798034/+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 1798102] Re: Lightning no longer in French after upgrading to 60.2.1

[Piraten-Kris Pseudonym]

*** This bug is a duplicate of bug 545778 ***
https://bugs.launchpad.net/bugs/545778

** This bug is no longer a duplicate of bug 1798034
   Package xul-ext-lightning is in English only
** This bug has been marked a duplicate of bug 545778
   xul-ext-lightning is only available in English

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

Title:
  Lightning no longer in French after upgrading to 60.2.1

Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  here is Ubuntu Budgie 18.04

  At first I thought Lightning was broken because I had to uninstall the
  mozilla-addons version of it ( the one found in mozilla addons webpage
  from inside TB ) and then re-install from Ubuntu repository xul-ext-
  lighting to have it upgraded.

  Now Calendar ( lightning ) is no longer displayed in French, but
  English.

  coeur-noir@asgard:~$ dpkg -l | egrep "thunder|xul-ext"
  ii  thunderbird   1:60.2.1+build1-0ubuntu0.18.04.2
amd64Email, RSS and newsgroup client with integrated spam filter
  ii  thunderbird-globalmenu1:60.2.1+build1-0ubuntu0.18.04.2
amd64Email, RSS and newsgroup client (transitional package)
  ii  thunderbird-gnome-support 1:60.2.1+build1-0ubuntu0.18.04.2
amd64Email, RSS and newsgroup client - GNOME support
  ii  thunderbird-locale-en 1:60.2.1+build1-0ubuntu0.18.04.2
amd64English language pack for Thunderbird
  ii  thunderbird-locale-en-us  1:60.2.1+build1-0ubuntu0.18.04.2
all  Transitional English language pack for Thunderbird
  ii  thunderbird-locale-fr 1:60.2.1+build1-0ubuntu0.18.04.2
amd64French language pack for Thunderbird
  ii  xul-ext-calendar-timezones1:60.2.1+build1-0ubuntu0.18.04.2
amd64Calendar Extension for Thunderbird (transitional package)
  ii  xul-ext-gdata-provider1:60.2.1+build1-0ubuntu0.18.04.2
amd64Calendar Extension for Thunderbird (transitional package)
  ii  xul-ext-lightning 1:60.2.1+build1-0ubuntu0.18.04.2
amd64Calendar Extension for Thunderbird
  coeur-noir@asgard:~$

  Same « problem » on Ubuntu Unity 16.04

  [ for reference https://forum.ubuntu-fr.org/viewtopic.php?id=2032006 ]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1798102/+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 545778] Re: xul-ext-lightning is only available in English

[Piraten-Kris Pseudonym]

Note: This may be fixed in some Weeks, Months, or Years, so maybe you can try 
first:
 > Thunderbird > Add-Ons > Extensions > Search for: Lightning > Install.
If you use Ubuntu-Linux or a Derivative, Lightning is not included in 
Thunderbird 60+ and the Update will break your Calendar (incompatible, not 
compatible). xul-ext-lightning is not international. Search for Add-On leads to 
incompatible Version. Someone told, the Beta is not recommended.

Workaround:
 > Download latest Version of Thunderbird fitting for you from here:
https://www.thunderbird.net/en-US/thunderbird/all/
 > Open File with Archive-Program(Unzipper)
 > Goto > thunderbird > distribution > extensions >
 > {e2fda1a4-762b-4020-b5ad-a41df1933103}.xpi (=Lightning) > Extract
 > Open your installed Thunderbird > Add-Ons > Extensions
 > (Remove unwanted english Version of Lightning)
 > Gear-Wheel-Button next to the Search-Box
 > Install Add-on From File
 > Select Download-Folder and the .xpi-File > Install
 => All your Calendar-Data should be back

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

Title:
  xul-ext-lightning is only available in English

Status in One Hundred Papercuts:
  Triaged
Status in Mozilla Thunderbird:
  Invalid
Status in Ubuntu Translations:
  Triaged
Status in lightning-sunbird package in Ubuntu:
  Invalid
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  ***
   ISSUE
  ***

  HOW TO REPRODUCE

  1. Change the user session language to other different than English.
  2. In Thunderbird, open the calendar

  EXPECTED BEHAVIOUR

  - The calendar interface to be in the session language.

  REAL BEHAVIOUR

  - The calendar is in English.

  RELEVANT DETAILS

  - None.

  **
   SOLUTION
  **

  WORK-AROUND

  - None known.

  FIX

  - .

  REGRESSION POTENTIAL

  - Since no code needs to be modified, the regression potential is very
  low.

  
   TECHNICAL INFO
  

  Binary package hint: lightning-extension

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/545778/+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 1797945] Re: Lightning incompatible with Thunderbird 60.2.1

[Piraten-Kris Pseudonym]

Note: This may be fixed in some Weeks, Months, or Years, so maybe you can try 
first:
 > Thunderbird > Add-Ons > Extensions > Search for: Lightning > Install.
If you use Ubuntu-Linux or a Derivative, Lightning is not included in 
Thunderbird 60+ and the Update will break your Calendar (incompatible, not 
compatible). xul-ext-lightning is not international. Search for Add-On leads to 
incompatible Version. Someone told, the Beta is not recommended.

Workaround:
 > Download latest Version of Thunderbird fitting for you from here:
https://www.thunderbird.net/en-US/thunderbird/all/
 > Open File with Archive-Program(Unzipper)
 > Goto > thunderbird > distribution > extensions > 
 > {e2fda1a4-762b-4020-b5ad-a41df1933103}.xpi (=Lightning) > Extract
 > Open your installed Thunderbird > Add-Ons > Extensions 
 > (Remove unwanted english Version of Lightning) 
 > Gear-Wheel-Button next to the Search-Box 
 > Install Add-on From File
 > Select Download-Folder and the .xpi-File > Install
 => All your Calendar-Data should be back

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

Title:
  Lightning incompatible with Thunderbird 60.2.1

Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  Hi

  Today I got the update from Thunderbird 52 to 60.2.1. Unfortunately
  Lightning doesn't work anymore.

  Thunderbird reports that Lightning is incompatible with Thunderbird
  60.2.1.

  Regards,

  Ettore

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1797945/+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 1797945] Re: Lightning incompatible with Thunderbird 60.2.1

[Piraten-Kris Pseudonym]

It _is_ a Bug in Ubuntu, because they do not deliver the 
Standard-Thunderbird-Version with Lightning includes.
It _is_ a Bug in Ubuntu, because Ubuntus xul-ext-lightning is english-only and 
not international (localized).
A compatibel Release-Version of Lightning is already available, it is just, 
that Ubuntu does not include it or offer it.


** Changed in: thunderbird (Ubuntu)
   Status: Invalid => In Progress

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

Title:
  Lightning incompatible with Thunderbird 60.2.1

Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  Hi

  Today I got the update from Thunderbird 52 to 60.2.1. Unfortunately
  Lightning doesn't work anymore.

  Thunderbird reports that Lightning is incompatible with Thunderbird
  60.2.1.

  Regards,

  Ettore

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1797945/+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 1797945] Re: Lightning incompatible with Thunderbird 60.2.1

[Piraten-Kris Pseudonym]

I have to correct myself:
I think, this is a Bug, Ubuntu should care about immediately, because it breaks 
Peoples already installed Calendar by an Ubuntu-Update.


** Changed in: thunderbird (Ubuntu)
   Status: In Progress => Confirmed

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

Title:
  Lightning incompatible with Thunderbird 60.2.1

Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  Hi

  Today I got the update from Thunderbird 52 to 60.2.1. Unfortunately
  Lightning doesn't work anymore.

  Thunderbird reports that Lightning is incompatible with Thunderbird
  60.2.1.

  Regards,

  Ettore

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1797945/+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 1644666] Re: Xorg crash 1: nvidia-304.132-0ubuntu0.16.04.2 => Login-Loop

[Piraten-Kris Pseudonym]

According to 
https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1750937?comments=all
a fix for this Problem has been released.

** Changed in: xorg (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: xorg (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Xorg crash 1: nvidia-304.132-0ubuntu0.16.04.2 => Login-Loop

Status in xorg package in Ubuntu:
  Fix Released

Bug description:

  Ubuntu 16.04.1 (Automatic Upgrade from 14.04)
  My Onboard-Graphics (AMD-System, ASRock N68C-S UCC): 
Nvidia C61 [GeForce 7025 / nForce 630a]
  ---
  In the Past: 
  => System and Apps worked well with Auto-Login enabled.
  To eliminate Hardware-Errors:
  > Memtest
  > Boot with Windows-XP
  => No Problems

  
  Problems in short: Linux 4.4.0-47-generic (systemd) and (upstart)
  -- 
  1. nvidia-304.132-0ubuntu0.16.04.2 => Login-Loop
  2. nouveau, Thunderbird, Firefox => System-(Freeze)-Crash with Stripes-Screen
  ---
  I don't know in which Category to sort the Bugs
  So this one is for the (Nr.1) Login-Loop (from tty-Terminal)
  (I already filed another Bug-Report for the (Nr.2) System-(Freeze)-Crash with 
Stripes-Screen)


  First Problem startet on 2016-Nov-05: => Login-Loop
  ---
  I later found out, that one Day before, the following Auto-Updates had been 
installed:
  ---
  libcurl3-gnutls(7.47.0-1ubuntu2.1, 7.47.0-1ubuntu2.2)
  nvidia304(304.131-0ubuntu3, 304.132-0ubuntu0.16.04.2)
  nvidia-opencl-icd-304 (304.131-0ubuntu3, 304.132-0ubuntu0.16.04.2)
  libcurl3(7.47.0-1ubuntu2.1, 7.47.0-1ubuntu2.2)
  ---
  After Shutdown, the next Computer-Start was stuck in a 
  => Login-Loop: After entering the correct Password, the Screen turns black 
for a Second, then the Login-Form shows up again.
  ---
  I tried a few things, that did not help, like: 
  > CTRL+F2 => Terminal > sudo ..
  > apt autoclean
  > apt clean
  > apt autoremove
  > apt update
  > apt upgrade
  > apt dist-upgrade
  > shutdown -r now
  > mv .Xauthority .Xauthority.alt
  > shutdown -r now
  > service lightdm restart
  > shutdown -r now
  > apt purge lightdm
  > apt install lightdm
  > shutdown -r now
  > .. Boot into different Linux-Kernel, .. (upstart), 
  > .. Boot into Recovery-Mode > .. > Repair > ..
  > .. I also tried to install other nvidia-drivers, which, sadly, i did not 
document. 
  => Did NOT work
  ---
  Only Thing that helped was:
  ---
  > sudo apt purge nvidia-*
  > sudo shutdown -r now
  => (nouveau-Driver was automatically installed)
  => Auto-Login to Desktop

  
  But then there was a second Problem:
  
  When > starting Thunderbird, mostly at once, sometimes after > opening some 
E-Mail-Windows, another Error occurred:
  => System freeze for 3 Seconds, then Screen turned to Stripes-Wallpaper => 
Total (Freeze-)Crash
  --
  Later, even with DISabled Hardware-Acceleration, starting both, Firefox and 
Thunderbird led to the System-Crash.
  (Sometimes, the System with nouveau booted and auto-logined into a Black 
Screen with a Mouse-Pointer. Nevertheless the System seemed to work and could 
be rebooted normally.)
  ---
  > CTRL+ALT+F2 => did NOT work
  > Magic Sys-Request (SysRQ): (ALT+PRINT)+ REISUB => did NOT work
  > ping to IP => unreachable
  ---
  After cold Reboot, i tried again to switch back from nouveau- to 
nvidia-Drivers
  > Additional Drivers > Nvidia-304.132
  => Login-Loop
  ---
  > sudo apt purge nvidia-*
  > sudo apt install --reinstall xserver-xorg-core xserver-xorg-video-nouveau
  => Auto-Login
  >  Firefox / Thunderbird => System-(Freeze)-Crash with Stripes-Screen
  ---
  > .. removed and tried to install the old driver (I probably did wrong):
  > sudo apt purge nvidia-*
  > sudo add-apt-repository ppa:graphics-drivers/ppa
  > sudo apt update
  > sudo apt install nvidia-current=304.131-0ubuntu3
  => Login-Loop
  ---
  > sudo apt purge nvidia-*
  > Additional Drivers > nouveau
  > Boot > Grub-2 > "Erweiterte Optionen für Ubuntu" > "Ubuntu, mit Linux 
4.4.0-47-generic" (NO Option=SYSTEMD?)
  => Auto-Login
  >  Firefox / Thunderbird => System-(Freeze)-Crash with Stripes-Screen
  
  What seemed to help was:
  
  > Boot > Grub-2 > "Erweiterte Optionen für Ubuntu" > "Ubuntu, mit Linux 
4.4.0-47-generic (upstart)" (UPSTART!)
  => Auto-Login
  >  Firefox / Thunderbird => seem to work stable!
  => After half an Hour of testing:
  >  open Firefox (Hardware-Acceleration disabled) 
  => System-(Freeze)-Crash with Stripes-Screen
  -
  Because this is far more stable: 
  Changed Standard-Boot in Grub-2 to UpStart instead of SystemD
  ---
  > Terminal >
  sudo apt install upstart-sysv
  su
  sudo shutdown -r now
 

[Desktop-packages] [Bug 1797945] Re: Lightning incompatible with Thunderbird 60.2.1

[Piraten-Kris Pseudonym]

As defined it is not invalid, because it _is_ a Bug. 
It will be resolved later, when a compatible Version of Lightning will be made 
available at Thunderbird-Add-On-Search.
(I could not chose "Won't fix")
So i changed its Status to "In Progress"

** Changed in: thunderbird (Ubuntu)
   Status: Invalid => In Progress

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

Title:
  Lightning incompatible with Thunderbird 60.2.1

Status in thunderbird package in Ubuntu:
  In Progress

Bug description:
  Hi

  Today I got the update from Thunderbird 52 to 60.2.1. Unfortunately
  Lightning doesn't work anymore.

  Thunderbird reports that Lightning is incompatible with Thunderbird
  60.2.1.

  Regards,

  Ettore

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1797945/+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 545778] Re: xul-ext-lightning is only available in English

[Piraten-Kris Pseudonym]

You can find Workarounds here:
(https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1797945)

If you want the english Version of Lightning, type into a Terminal: 
sudo apt update
sudo apt install xul-ext-lightning

If you want a localized Version of Lightning, at the Moment, you cannot use the 
normal Add-On-Search in Thunderbird (incompatible).
Download manually the latest Beta-Version of Lightining for your System- and 
Language-Version from:
https://archive.mozilla.org/pub/calendar/lightning/candidates/

Open Thunderbird > Add-Ons > Extensions > (Remove unwanted english Version of 
Lightining) >
  > At the top of the page, click the Gear-Wheel-Button next to the Search-Box 
to open a menu
  > Install Add-on From File 
  > Select Download-Folder and the .xpi-File > Install
=> All your Calendar-Data should be back

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

Title:
  xul-ext-lightning is only available in English

Status in One Hundred Papercuts:
  Triaged
Status in Mozilla Thunderbird:
  Invalid
Status in Ubuntu Translations:
  Triaged
Status in lightning-sunbird package in Ubuntu:
  Invalid
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  ***
   ISSUE
  ***

  HOW TO REPRODUCE

  1. Change the user session language to other different than English.
  2. In Thunderbird, open the calendar

  EXPECTED BEHAVIOUR

  - The calendar interface to be in the session language.

  REAL BEHAVIOUR

  - The calendar is in English.

  RELEVANT DETAILS

  - None.

  **
   SOLUTION
  **

  WORK-AROUND

  - None known.

  FIX

  - .

  REGRESSION POTENTIAL

  - Since no code needs to be modified, the regression potential is very
  low.

  
   TECHNICAL INFO
  

  Binary package hint: lightning-extension

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/545778/+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 1797945] Re: Lightning incompatible with Thunderbird 60.2.1

[Piraten-Kris Pseudonym]

This is ridiculous: If you go to https://bugs.launchpad.net
and search for: "Lightning incompatible Thunderbird"
you will only find two many years old bugs, which have never been closed. 

How can launchpad be helpful in any way? I really want to know.

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

Title:
  Lightning incompatible with Thunderbird 60.2.1

Status in thunderbird package in Ubuntu:
  Invalid

Bug description:
  Hi

  Today I got the update from Thunderbird 52 to 60.2.1. Unfortunately
  Lightning doesn't work anymore.

  Thunderbird reports that Lightning is incompatible with Thunderbird
  60.2.1.

  Regards,

  Ettore

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1797945/+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 1797945] Re: Lightning incompatible with Thunderbird 60.2.1

[Piraten-Kris Pseudonym]

Hi Chris Coulson,

you changed it to Invalid which means; "This is not a Bug."
That implies, the Bug does not show up in the Search or in any Users 
Subscription any longer.
Now, nobody can find the Solution anymore for the Problem, which is definitly a 
Bug and no Feature-Request. Duplicate Bug-Entrys are provoked by this. 

Wouldn't it be more appropriate to change the Status to "Won't fix"?
So that Users looking for the Problem will at least find Something and get Help 
by the Workarounds?

Kris

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

Title:
  Lightning incompatible with Thunderbird 60.2.1

Status in thunderbird package in Ubuntu:
  Invalid

Bug description:
  Hi

  Today I got the update from Thunderbird 52 to 60.2.1. Unfortunately
  Lightning doesn't work anymore.

  Thunderbird reports that Lightning is incompatible with Thunderbird
  60.2.1.

  Regards,

  Ettore

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1797945/+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 1797945] Re: Lightning incompatible with Thunderbird 60.2.1

[Piraten-Kris Pseudonym]

Above is the direct Link to the German Version (DE).
Maybe you will have to chose your Language-Version from:
https://archive.mozilla.org/pub/calendar/lightning/candidates/6.2b6-candidates/build1/

Comment to the former Solution:
I did not have installed and did not try xul-ext-lightning.
You cannot find it in the new (Gnome-)Software. It only will show up in the old 
Ubuntu-Software-Center. However, there is a Comment, that this will only 
install the English Version (EN). You can also find this via Terminal > apt 
list xul-ext-lightning 
If you want the english Version of Lightning, type: sudo apt install 
xul-ext-lightning

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

Title:
  Lightning incompatible with Thunderbird 60.2.1

Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  Hi

  Today I got the update from Thunderbird 52 to 60.2.1. Unfortunately
  Lightning doesn't work anymore.

  Thunderbird reports that Lightning is incompatible with Thunderbird
  60.2.1.

  Regards,

  Ettore

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1797945/+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 1797945] Re: Lightning incompatible with Thunderbird 60.2.1

[Piraten-Kris Pseudonym]

Same Problem today after "sudo apt upgrade" => from Thunderbird 52 to 60.2.1 
(64-bit)
In all my 3 Profiles Lightning had stopped working / disappeared. 
The First Profile had Lightning 5.4 installed as Add-On and now showed: 
incompatible .. deaktivated
Second and third Profile: In the Past, Lightning had been automatically 
integrated by clicking "keep it" and now it had disappeared.
Trying to install via search Add-Ons in Thunderbird only led to the 
incompatible 5.4.

Also NOT helpful was:
https://support.mozilla.org/en-US/kb/calendar-updates-issues-thunderbird
(Entry in Config did not exist at all)

There was also no change, when i started Ubuntu-Languages or so (DE:
Sprachen) and let install additional Language-Packages including one for
Thunderbird-EN automatically. (DE, which i use, did not show up as
missing).

What then helped in all 3 Profiles, was the manual Download and Install of a 
Lightning-Beta-XPI into Thunderbird:
https://archive.mozilla.org/pub/calendar/lightning/candidates/6.2b6-candidates/build1/linux-x86_64/lightning-6.2b6.de.xpi

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

Title:
  Lightning incompatible with Thunderbird 60.2.1

Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  Hi

  Today I got the update from Thunderbird 52 to 60.2.1. Unfortunately
  Lightning doesn't work anymore.

  Thunderbird reports that Lightning is incompatible with Thunderbird
  60.2.1.

  Regards,

  Ettore

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1797945/+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 927952] Re: When I press the Print Screen button, it will not appear in "Save Screenshot" window.

[Kris]

this: "because we keep being asked by GNOME upstream and GNOME user to
let their desktop alone and ship it as designed so that's what we try to
do, we stick to upstream behaviour for GNOME environments and take
design decision for Unity", this is BS!

How about all of the Unity users who now are migrating to Gnome desktop
and get productivity decrease because of this limiting new behavior (new
to us). Why not to create a settings somewhere, can be even opt-in, to
use the dialog with screenshot?

On unity I hit prntscr button, copy to clipboard and Ctrl+V into
Telegram/Slack/Goodle Drive/Pinta/LibreImpress/etc. No files to delte
afterwards. Unless I want to save it on disk. Gnome behavior is a
downgrade to us unity users. Please give a choice to us also, not just
gnome users :(

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

Title:
  When I press the Print Screen button, it will not appear in "Save
  Screenshot" window.

Status in Ayatana Design:
  Fix Released
Status in Gnome Screenshot:
  Expired
Status in gnome-screenshot package in Ubuntu:
  Fix Released
Status in gnome-screenshot source package in Precise:
  Fix Released
Status in gnome-screenshot package in Debian:
  Confirmed

Bug description:
  When taking a screenshot with Print Screen or Alt+Print Screen a
  dialog box asking you what and where to save the file no longer
  appears.  So while you hear a camera sound you have no other
  confirmation that a screenshot was really taken.  Additionally, there
  is no way of knowing where the screenshot went.  I'd imagine this will
  be particularly problematic for new users of Ubuntu.

  ProblemType: BugDistroRelease: Ubuntu 12.04
  Package: gnome-screenshot 3.3.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-14.23-generic 3.2.3
  Uname: Linux 3.2.0-14-generic x86_64
  ApportVersion: 1.91-0ubuntu1
  Architecture: amd64
  Date: Mon Feb  6 23:54:17 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 
(2029.1)SourcePackage: gnome-screenshot
  UpgradeStatus: Upgraded to precise on 2012-01-27 (10 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/927952/+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 927952] Re: When I press the Print Screen button, it will not appear in "Save Screenshot" window.

[Kris]

Just recently upgraded to bionic, and after using it for a while I
mostly got used to it, but the one feature that keeps bothering me
painfully is the lack of the printscreen dialog. I understand the
initiative to adopt gnome standards, but this is introducing a big
inconvenience in comparison to how it was functional in the Unity
desktop. It is not just about being able to save printscreens to an
arbitrary location under an arbitrary name. It is even more importantly
being able to copy a printscreen into a clipboard without saving it to a
file on a disk. I used to be able to just copy a printscreen and Ctrl+V
it into a IM window, a email client or any webapp. Now I have to take
additional steps to open file manager, navigate to the Pictures folder,
locate the one printscreen file I need among other ones, and drag
it to where I need it, then, delete it. The functionality and user
experience has decreased significantly for me, and on top of that I get
constantly annoyed by it. I wish Canonical shipped the previous user
experience with the new gnome-desktop based Ubuntu. Even as an opt-in!

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

Title:
  When I press the Print Screen button, it will not appear in "Save
  Screenshot" window.

Status in Ayatana Design:
  Fix Released
Status in Gnome Screenshot:
  Expired
Status in gnome-screenshot package in Ubuntu:
  Fix Released
Status in gnome-screenshot source package in Precise:
  Fix Released
Status in gnome-screenshot package in Debian:
  Confirmed

Bug description:
  When taking a screenshot with Print Screen or Alt+Print Screen a
  dialog box asking you what and where to save the file no longer
  appears.  So while you hear a camera sound you have no other
  confirmation that a screenshot was really taken.  Additionally, there
  is no way of knowing where the screenshot went.  I'd imagine this will
  be particularly problematic for new users of Ubuntu.

  ProblemType: BugDistroRelease: Ubuntu 12.04
  Package: gnome-screenshot 3.3.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-14.23-generic 3.2.3
  Uname: Linux 3.2.0-14-generic x86_64
  ApportVersion: 1.91-0ubuntu1
  Architecture: amd64
  Date: Mon Feb  6 23:54:17 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 
(2029.1)SourcePackage: gnome-screenshot
  UpgradeStatus: Upgraded to precise on 2012-01-27 (10 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/927952/+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 1644661] Re: Xorg crash 2. nouveau, Thunderbird, Firefox => System-(Freeze)-Crash with Stripes-Screen

[Piraten-Kris Pseudonym]

WORKAROUND:
---

Forced Install of older NVIDIA-Graphics-Driver, which worked:
(nvidia-304=304.131-0ubuntu3  +  nvidia-opencl-icd-304=304.131-0ubuntu3)
---
> sudo nano /etc/apt/preferences.d/local-nvidia-quirks
--- Content:
Explanation: Block This Update because it causes a Login-Loop
Package: nvidia-304
Pin: version 304.132-0ubuntu0.16.04.2
Pin-Priority: -10

Explanation: Block This Update because it causes a Login-Loop
Package: nvidia-opencl-icd-304
Pin: version 304.132-0ubuntu0.16.04.2
Pin-Priority: -10
--- End Content
> STRG+o > STRG+x
> sudo apt install nvidia-304=304.131-0ubuntu3 
> nvidia-opencl-icd-304=304.131-0ubuntu3
> sudo shutdown -r now

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

Title:
  Xorg crash 2. nouveau, Thunderbird, Firefox => System-(Freeze)-Crash
  with Stripes-Screen

Status in xorg package in Ubuntu:
  New

Bug description:
  
  Ubuntu 16.04.1 (Automatic Upgrade from 14.04)
  My Onboard-Graphics (AMD-System, ASRock N68C-S UCC): 
Nvidia C61 [GeForce 7025 / nForce 630a]
  ---
  In the Past: 
  => System and Apps worked well with Auto-Login enabled.
  To eliminate Hardware-Errors:
  > Memtest
  > Boot with Windows-XP
  => No Problems

  
  Problems in short: Linux 4.4.0-47-generic (systemd) and (upstart)
  -- 
  1. nvidia-304.132-0ubuntu0.16.04.2 => Login-Loop
  2. nouveau, Thunderbird, Firefox => System-(Freeze)-Crash with Stripes-Screen
  ---
  I don't know in which Category to sort the Bugs
  So this one ist for the (Nr.2) System-(Freeze)-Crash with Stripes-Screen
  I will try to file another Bug-Report for the (Nr.1) Login-Loop (If it works 
from tty-Terminal)

  
  First Problem startet on 2016-Nov-05: => Login-Loop
  ---
  I later found out, that one Day before, the following Auto-Updates had been 
installed:
  ---
  libcurl3-gnutls(7.47.0-1ubuntu2.1, 7.47.0-1ubuntu2.2)
  nvidia304(304.131-0ubuntu3, 304.132-0ubuntu0.16.04.2)
  nvidia-opencl-icd-304 (304.131-0ubuntu3, 304.132-0ubuntu0.16.04.2)
  libcurl3(7.47.0-1ubuntu2.1, 7.47.0-1ubuntu2.2)
  ---
  After Shutdown, the next Computer-Start was stuck in a 
  => Login-Loop: After entering the correct Password, the Screen turns black 
for a Second, then the Login-Form shows up again.
  ---
  I tried a few things, that did not help, like: 
  > CTRL+F2 => Terminal > sudo ..
  > apt autoclean
  > apt clean
  > apt autoremove
  > apt update
  > apt upgrade
  > apt dist-upgrade
  > shutdown -r now
  > mv .Xauthority .Xauthority.alt
  > shutdown -r now
  > service lightdm restart
  > shutdown -r now
  > apt purge lightdm
  > apt install lightdm
  > shutdown -r now
  > .. Boot into different Linux-Kernel, .. (upstart), 
  > .. Boot into Recovery-Mode > .. > Repair > ..
  > .. I also tried to install other nvidia-drivers, which, sadly, i did not 
document. 
  => Did NOT work
  ---
  Only Thing that helped was:
  ---
  > sudo apt purge nvidia-*
  > sudo shutdown -r now
  => (nouveau-Driver was automatically installed)
  => Auto-Login to Desktop

  
  But then there was a second Problem:
  
  When > starting Thunderbird, mostly at once, sometimes after > opening some 
E-Mail-Windows, another Error occurred:
  => System freeze for 3 Seconds, then Screen turned to Stripes-Wallpaper => 
Total (Freeze-)Crash
  --
  Later, even with DISabled Hardware-Acceleration, starting both, Firefox and 
Thunderbird led to the System-Crash.
  (Sometimes, the System with nouveau booted and auto-logined into a Black 
Screen with a Mouse-Pointer. Nevertheless the System seemed to work and could 
be rebooted normally.)
  ---
  > CTRL+ALT+F2 => did NOT work
  > Magic Sys-Request (SysRQ): (ALT+PRINT)+ REISUB => did NOT work
  > ping to IP => unreachable
  ---
  After cold Reboot, i tried again to switch back from nouveau- to 
nvidia-Drivers
  > Additional Drivers > Nvidia-304.132
  => Login-Loop
  ---
  > sudo apt purge nvidia-*
  > sudo apt install --reinstall xserver-xorg-core xserver-xorg-video-nouveau
  => Auto-Login
  >  Firefox / Thunderbird => System-(Freeze)-Crash with Stripes-Screen
  ---
  > .. removed and tried to install the old driver (I probably did wrong):
  > sudo apt purge nvidia-*
  > sudo add-apt-repository ppa:graphics-drivers/ppa
  > sudo apt update
  > sudo apt install nvidia-current=304.131-0ubuntu3
  => Login-Loop
  ---
  > sudo apt purge nvidia-*
  > Additional Drivers > nouveau
  > Boot > Grub-2 > "Erweiterte Optionen für Ubuntu" > "Ubuntu, mit Linux 
4.4.0-47-generic" (NO Option=SYSTEMD?)
  => Auto-Login
  >  Firefox / Thunderbird => System-(Freeze)-Crash with Stripes-Screen
  
  What seemed to help was:
  
  > Boot > Grub-2 > "Erweiterte Optionen für Ubuntu" > "Ubuntu, mit Linux 
4.4.0-47-generic (upstart)" (UPSTART!)
  => Auto-Login
  >  

[Desktop-packages] [Bug 1644666] Re: Xorg crash 1: nvidia-304.132-0ubuntu0.16.04.2 => Login-Loop

[Piraten-Kris Pseudonym]

WORKAROUND:
---

Forced Install of older NVIDIA-Graphics-Driver, which worked:
(nvidia-304=304.131-0ubuntu3  +  nvidia-opencl-icd-304=304.131-0ubuntu3)
---
> sudo nano /etc/apt/preferences.d/local-nvidia-quirks
--- Content:
Explanation: Block This Update because it causes a Login-Loop
Package: nvidia-304
Pin: version 304.132-0ubuntu0.16.04.2
Pin-Priority: -10

Explanation: Block This Update because it causes a Login-Loop
Package: nvidia-opencl-icd-304
Pin: version 304.132-0ubuntu0.16.04.2
Pin-Priority: -10
--- End Content
> STRG+o > STRG+x
> sudo apt install nvidia-304=304.131-0ubuntu3 
> nvidia-opencl-icd-304=304.131-0ubuntu3
> sudo shutdown -r now

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

Title:
  Xorg crash 1: nvidia-304.132-0ubuntu0.16.04.2 => Login-Loop

Status in xorg package in Ubuntu:
  Confirmed

Bug description:

  Ubuntu 16.04.1 (Automatic Upgrade from 14.04)
  My Onboard-Graphics (AMD-System, ASRock N68C-S UCC): 
Nvidia C61 [GeForce 7025 / nForce 630a]
  ---
  In the Past: 
  => System and Apps worked well with Auto-Login enabled.
  To eliminate Hardware-Errors:
  > Memtest
  > Boot with Windows-XP
  => No Problems

  
  Problems in short: Linux 4.4.0-47-generic (systemd) and (upstart)
  -- 
  1. nvidia-304.132-0ubuntu0.16.04.2 => Login-Loop
  2. nouveau, Thunderbird, Firefox => System-(Freeze)-Crash with Stripes-Screen
  ---
  I don't know in which Category to sort the Bugs
  So this one is for the (Nr.1) Login-Loop (from tty-Terminal)
  (I already filed another Bug-Report for the (Nr.2) System-(Freeze)-Crash with 
Stripes-Screen)


  First Problem startet on 2016-Nov-05: => Login-Loop
  ---
  I later found out, that one Day before, the following Auto-Updates had been 
installed:
  ---
  libcurl3-gnutls(7.47.0-1ubuntu2.1, 7.47.0-1ubuntu2.2)
  nvidia304(304.131-0ubuntu3, 304.132-0ubuntu0.16.04.2)
  nvidia-opencl-icd-304 (304.131-0ubuntu3, 304.132-0ubuntu0.16.04.2)
  libcurl3(7.47.0-1ubuntu2.1, 7.47.0-1ubuntu2.2)
  ---
  After Shutdown, the next Computer-Start was stuck in a 
  => Login-Loop: After entering the correct Password, the Screen turns black 
for a Second, then the Login-Form shows up again.
  ---
  I tried a few things, that did not help, like: 
  > CTRL+F2 => Terminal > sudo ..
  > apt autoclean
  > apt clean
  > apt autoremove
  > apt update
  > apt upgrade
  > apt dist-upgrade
  > shutdown -r now
  > mv .Xauthority .Xauthority.alt
  > shutdown -r now
  > service lightdm restart
  > shutdown -r now
  > apt purge lightdm
  > apt install lightdm
  > shutdown -r now
  > .. Boot into different Linux-Kernel, .. (upstart), 
  > .. Boot into Recovery-Mode > .. > Repair > ..
  > .. I also tried to install other nvidia-drivers, which, sadly, i did not 
document. 
  => Did NOT work
  ---
  Only Thing that helped was:
  ---
  > sudo apt purge nvidia-*
  > sudo shutdown -r now
  => (nouveau-Driver was automatically installed)
  => Auto-Login to Desktop

  
  But then there was a second Problem:
  
  When > starting Thunderbird, mostly at once, sometimes after > opening some 
E-Mail-Windows, another Error occurred:
  => System freeze for 3 Seconds, then Screen turned to Stripes-Wallpaper => 
Total (Freeze-)Crash
  --
  Later, even with DISabled Hardware-Acceleration, starting both, Firefox and 
Thunderbird led to the System-Crash.
  (Sometimes, the System with nouveau booted and auto-logined into a Black 
Screen with a Mouse-Pointer. Nevertheless the System seemed to work and could 
be rebooted normally.)
  ---
  > CTRL+ALT+F2 => did NOT work
  > Magic Sys-Request (SysRQ): (ALT+PRINT)+ REISUB => did NOT work
  > ping to IP => unreachable
  ---
  After cold Reboot, i tried again to switch back from nouveau- to 
nvidia-Drivers
  > Additional Drivers > Nvidia-304.132
  => Login-Loop
  ---
  > sudo apt purge nvidia-*
  > sudo apt install --reinstall xserver-xorg-core xserver-xorg-video-nouveau
  => Auto-Login
  >  Firefox / Thunderbird => System-(Freeze)-Crash with Stripes-Screen
  ---
  > .. removed and tried to install the old driver (I probably did wrong):
  > sudo apt purge nvidia-*
  > sudo add-apt-repository ppa:graphics-drivers/ppa
  > sudo apt update
  > sudo apt install nvidia-current=304.131-0ubuntu3
  => Login-Loop
  ---
  > sudo apt purge nvidia-*
  > Additional Drivers > nouveau
  > Boot > Grub-2 > "Erweiterte Optionen für Ubuntu" > "Ubuntu, mit Linux 
4.4.0-47-generic" (NO Option=SYSTEMD?)
  => Auto-Login
  >  Firefox / Thunderbird => System-(Freeze)-Crash with Stripes-Screen
  
  What seemed to help was:
  
  > Boot > Grub-2 > "Erweiterte Optionen für Ubuntu" > "Ubuntu, mit Linux 
4.4.0-47-generic (upstart)" (UPSTART!)
  => Auto-Login
  >  Firefox / Thunderbird => seem to work 

[Desktop-packages] [Bug 1644661] Re: Xorg crash 2. nouveau, Thunderbird, Firefox => System-(Freeze)-Crash with Stripes-Screen

[Piraten-Kris Pseudonym]

I could reproduce the Error on the same Hardware by 
> booting an original Live-CD: c't Security - Desinfec't 2016/17 - based on 
> Ubuntu 16.04.1 LTS
> Open Firefox > Close Firefox
> Open Thunderbird
=> System-(Freeze)-Crash with Stripes-Screen

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

Title:
  Xorg crash 2. nouveau, Thunderbird, Firefox => System-(Freeze)-Crash
  with Stripes-Screen

Status in xorg package in Ubuntu:
  New

Bug description:
  
  Ubuntu 16.04.1 (Automatic Upgrade from 14.04)
  My Onboard-Graphics (AMD-System, ASRock N68C-S UCC): 
Nvidia C61 [GeForce 7025 / nForce 630a]
  ---
  In the Past: 
  => System and Apps worked well with Auto-Login enabled.
  To eliminate Hardware-Errors:
  > Memtest
  > Boot with Windows-XP
  => No Problems

  
  Problems in short: Linux 4.4.0-47-generic (systemd) and (upstart)
  -- 
  1. nvidia-304.132-0ubuntu0.16.04.2 => Login-Loop
  2. nouveau, Thunderbird, Firefox => System-(Freeze)-Crash with Stripes-Screen
  ---
  I don't know in which Category to sort the Bugs
  So this one ist for the (Nr.2) System-(Freeze)-Crash with Stripes-Screen
  I will try to file another Bug-Report for the (Nr.1) Login-Loop (If it works 
from tty-Terminal)

  
  First Problem startet on 2016-Nov-05: => Login-Loop
  ---
  I later found out, that one Day before, the following Auto-Updates had been 
installed:
  ---
  libcurl3-gnutls(7.47.0-1ubuntu2.1, 7.47.0-1ubuntu2.2)
  nvidia304(304.131-0ubuntu3, 304.132-0ubuntu0.16.04.2)
  nvidia-opencl-icd-304 (304.131-0ubuntu3, 304.132-0ubuntu0.16.04.2)
  libcurl3(7.47.0-1ubuntu2.1, 7.47.0-1ubuntu2.2)
  ---
  After Shutdown, the next Computer-Start was stuck in a 
  => Login-Loop: After entering the correct Password, the Screen turns black 
for a Second, then the Login-Form shows up again.
  ---
  I tried a few things, that did not help, like: 
  > CTRL+F2 => Terminal > sudo ..
  > apt autoclean
  > apt clean
  > apt autoremove
  > apt update
  > apt upgrade
  > apt dist-upgrade
  > shutdown -r now
  > mv .Xauthority .Xauthority.alt
  > shutdown -r now
  > service lightdm restart
  > shutdown -r now
  > apt purge lightdm
  > apt install lightdm
  > shutdown -r now
  > .. Boot into different Linux-Kernel, .. (upstart), 
  > .. Boot into Recovery-Mode > .. > Repair > ..
  > .. I also tried to install other nvidia-drivers, which, sadly, i did not 
document. 
  => Did NOT work
  ---
  Only Thing that helped was:
  ---
  > sudo apt purge nvidia-*
  > sudo shutdown -r now
  => (nouveau-Driver was automatically installed)
  => Auto-Login to Desktop

  
  But then there was a second Problem:
  
  When > starting Thunderbird, mostly at once, sometimes after > opening some 
E-Mail-Windows, another Error occurred:
  => System freeze for 3 Seconds, then Screen turned to Stripes-Wallpaper => 
Total (Freeze-)Crash
  --
  Later, even with DISabled Hardware-Acceleration, starting both, Firefox and 
Thunderbird led to the System-Crash.
  (Sometimes, the System with nouveau booted and auto-logined into a Black 
Screen with a Mouse-Pointer. Nevertheless the System seemed to work and could 
be rebooted normally.)
  ---
  > CTRL+ALT+F2 => did NOT work
  > Magic Sys-Request (SysRQ): (ALT+PRINT)+ REISUB => did NOT work
  > ping to IP => unreachable
  ---
  After cold Reboot, i tried again to switch back from nouveau- to 
nvidia-Drivers
  > Additional Drivers > Nvidia-304.132
  => Login-Loop
  ---
  > sudo apt purge nvidia-*
  > sudo apt install --reinstall xserver-xorg-core xserver-xorg-video-nouveau
  => Auto-Login
  >  Firefox / Thunderbird => System-(Freeze)-Crash with Stripes-Screen
  ---
  > .. removed and tried to install the old driver (I probably did wrong):
  > sudo apt purge nvidia-*
  > sudo add-apt-repository ppa:graphics-drivers/ppa
  > sudo apt update
  > sudo apt install nvidia-current=304.131-0ubuntu3
  => Login-Loop
  ---
  > sudo apt purge nvidia-*
  > Additional Drivers > nouveau
  > Boot > Grub-2 > "Erweiterte Optionen für Ubuntu" > "Ubuntu, mit Linux 
4.4.0-47-generic" (NO Option=SYSTEMD?)
  => Auto-Login
  >  Firefox / Thunderbird => System-(Freeze)-Crash with Stripes-Screen
  
  What seemed to help was:
  
  > Boot > Grub-2 > "Erweiterte Optionen für Ubuntu" > "Ubuntu, mit Linux 
4.4.0-47-generic (upstart)" (UPSTART!)
  => Auto-Login
  >  Firefox / Thunderbird => seem to work stable!
  => After half an Hour of testing:
  >  open Firefox (Hardware-Acceleration disabled) 
  => System-(Freeze)-Crash with Stripes-Screen
  -
  Because this is far more stable: 
  Changed Standard-Boot in Grub-2 to UpStart instead of SystemD
  ---
  > Terminal >
  sudo apt install upstart-sysv
  su
  sudo 

[Desktop-packages] [Bug 1644661] Re: Xorg crash 2. nouveau, Thunderbird, Firefox => System-(Freeze)-Crash with Stripes-Screen

[Piraten-Kris Pseudonym]

** Summary changed:

- Xorg crash
+ Xorg crash 2. nouveau, Thunderbird, Firefox => System-(Freeze)-Crash with 
Stripes-Screen

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

Title:
  Xorg crash 2. nouveau, Thunderbird, Firefox => System-(Freeze)-Crash
  with Stripes-Screen

Status in xorg package in Ubuntu:
  New

Bug description:
  
  Ubuntu 16.04.1 (Automatic Upgrade from 14.04)
  My Onboard-Graphics (AMD-System, ASRock N68C-S UCC): 
Nvidia C61 [GeForce 7025 / nForce 630a]
  ---
  In the Past: 
  => System and Apps worked well with Auto-Login enabled.
  To eliminate Hardware-Errors:
  > Memtest
  > Boot with Windows-XP
  => No Problems

  
  Problems in short: Linux 4.4.0-47-generic (systemd) and (upstart)
  -- 
  1. nvidia-304.132-0ubuntu0.16.04.2 => Login-Loop
  2. nouveau, Thunderbird, Firefox => System-(Freeze)-Crash with Stripes-Screen
  ---
  I don't know in which Category to sort the Bugs
  So this one ist for the (Nr.2) System-(Freeze)-Crash with Stripes-Screen
  I will try to file another Bug-Report for the (Nr.1) Login-Loop (If it works 
from tty-Terminal)

  
  First Problem startet on 2016-Nov-05: => Login-Loop
  ---
  I later found out, that one Day before, the following Auto-Updates had been 
installed:
  ---
  libcurl3-gnutls(7.47.0-1ubuntu2.1, 7.47.0-1ubuntu2.2)
  nvidia304(304.131-0ubuntu3, 304.132-0ubuntu0.16.04.2)
  nvidia-opencl-icd-304 (304.131-0ubuntu3, 304.132-0ubuntu0.16.04.2)
  libcurl3(7.47.0-1ubuntu2.1, 7.47.0-1ubuntu2.2)
  ---
  After Shutdown, the next Computer-Start was stuck in a 
  => Login-Loop: After entering the correct Password, the Screen turns black 
for a Second, then the Login-Form shows up again.
  ---
  I tried a few things, that did not help, like: 
  > CTRL+F2 => Terminal > sudo ..
  > apt autoclean
  > apt clean
  > apt autoremove
  > apt update
  > apt upgrade
  > apt dist-upgrade
  > shutdown -r now
  > mv .Xauthority .Xauthority.alt
  > shutdown -r now
  > service lightdm restart
  > shutdown -r now
  > apt purge lightdm
  > apt install lightdm
  > shutdown -r now
  > .. Boot into different Linux-Kernel, .. (upstart), 
  > .. Boot into Recovery-Mode > .. > Repair > ..
  > .. I also tried to install other nvidia-drivers, which, sadly, i did not 
document. 
  => Did NOT work
  ---
  Only Thing that helped was:
  ---
  > sudo apt purge nvidia-*
  > sudo shutdown -r now
  => (nouveau-Driver was automatically installed)
  => Auto-Login to Desktop

  
  But then there was a second Problem:
  
  When > starting Thunderbird, mostly at once, sometimes after > opening some 
E-Mail-Windows, another Error occurred:
  => System freeze for 3 Seconds, then Screen turned to Stripes-Wallpaper => 
Total (Freeze-)Crash
  --
  Later, even with DISabled Hardware-Acceleration, starting both, Firefox and 
Thunderbird led to the System-Crash.
  (Sometimes, the System with nouveau booted and auto-logined into a Black 
Screen with a Mouse-Pointer. Nevertheless the System seemed to work and could 
be rebooted normally.)
  ---
  > CTRL+ALT+F2 => did NOT work
  > Magic Sys-Request (SysRQ): (ALT+PRINT)+ REISUB => did NOT work
  > ping to IP => unreachable
  ---
  After cold Reboot, i tried again to switch back from nouveau- to 
nvidia-Drivers
  > Additional Drivers > Nvidia-304.132
  => Login-Loop
  ---
  > sudo apt purge nvidia-*
  > sudo apt install --reinstall xserver-xorg-core xserver-xorg-video-nouveau
  => Auto-Login
  >  Firefox / Thunderbird => System-(Freeze)-Crash with Stripes-Screen
  ---
  > .. removed and tried to install the old driver (I probably did wrong):
  > sudo apt purge nvidia-*
  > sudo add-apt-repository ppa:graphics-drivers/ppa
  > sudo apt update
  > sudo apt install nvidia-current=304.131-0ubuntu3
  => Login-Loop
  ---
  > sudo apt purge nvidia-*
  > Additional Drivers > nouveau
  > Boot > Grub-2 > "Erweiterte Optionen für Ubuntu" > "Ubuntu, mit Linux 
4.4.0-47-generic" (NO Option=SYSTEMD?)
  => Auto-Login
  >  Firefox / Thunderbird => System-(Freeze)-Crash with Stripes-Screen
  
  What seemed to help was:
  
  > Boot > Grub-2 > "Erweiterte Optionen für Ubuntu" > "Ubuntu, mit Linux 
4.4.0-47-generic (upstart)" (UPSTART!)
  => Auto-Login
  >  Firefox / Thunderbird => seem to work stable!
  => After half an Hour of testing:
  >  open Firefox (Hardware-Acceleration disabled) 
  => System-(Freeze)-Crash with Stripes-Screen
  -
  Because this is far more stable: 
  Changed Standard-Boot in Grub-2 to UpStart instead of SystemD
  ---
  > Terminal >
  sudo apt install upstart-sysv
  su
  sudo shutdown -r now
  ---
  For Roll-Back:
  > Terminal >
  sudo apt install systemd-sysv
  sudo update-initramfs -u
  sudo 

[Desktop-packages] [Bug 1644666] Re: Xorg crash 1: nvidia-304.132-0ubuntu0.16.04.2 => Login-Loop

[Piraten-Kris Pseudonym]

** Summary changed:

- Xorg crash
+ Xorg crash 1: nvidia-304.132-0ubuntu0.16.04.2 => Login-Loop

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

Title:
  Xorg crash 1: nvidia-304.132-0ubuntu0.16.04.2 => Login-Loop

Status in xorg package in Ubuntu:
  New

Bug description:

  Ubuntu 16.04.1 (Automatic Upgrade from 14.04)
  My Onboard-Graphics (AMD-System, ASRock N68C-S UCC): 
Nvidia C61 [GeForce 7025 / nForce 630a]
  ---
  In the Past: 
  => System and Apps worked well with Auto-Login enabled.
  To eliminate Hardware-Errors:
  > Memtest
  > Boot with Windows-XP
  => No Problems

  
  Problems in short: Linux 4.4.0-47-generic (systemd) and (upstart)
  -- 
  1. nvidia-304.132-0ubuntu0.16.04.2 => Login-Loop
  2. nouveau, Thunderbird, Firefox => System-(Freeze)-Crash with Stripes-Screen
  ---
  I don't know in which Category to sort the Bugs
  So this one is for the (Nr.1) Login-Loop (from tty-Terminal)
  (I already filed another Bug-Report for the (Nr.2) System-(Freeze)-Crash with 
Stripes-Screen)


  First Problem startet on 2016-Nov-05: => Login-Loop
  ---
  I later found out, that one Day before, the following Auto-Updates had been 
installed:
  ---
  libcurl3-gnutls(7.47.0-1ubuntu2.1, 7.47.0-1ubuntu2.2)
  nvidia304(304.131-0ubuntu3, 304.132-0ubuntu0.16.04.2)
  nvidia-opencl-icd-304 (304.131-0ubuntu3, 304.132-0ubuntu0.16.04.2)
  libcurl3(7.47.0-1ubuntu2.1, 7.47.0-1ubuntu2.2)
  ---
  After Shutdown, the next Computer-Start was stuck in a 
  => Login-Loop: After entering the correct Password, the Screen turns black 
for a Second, then the Login-Form shows up again.
  ---
  I tried a few things, that did not help, like: 
  > CTRL+F2 => Terminal > sudo ..
  > apt autoclean
  > apt clean
  > apt autoremove
  > apt update
  > apt upgrade
  > apt dist-upgrade
  > shutdown -r now
  > mv .Xauthority .Xauthority.alt
  > shutdown -r now
  > service lightdm restart
  > shutdown -r now
  > apt purge lightdm
  > apt install lightdm
  > shutdown -r now
  > .. Boot into different Linux-Kernel, .. (upstart), 
  > .. Boot into Recovery-Mode > .. > Repair > ..
  > .. I also tried to install other nvidia-drivers, which, sadly, i did not 
document. 
  => Did NOT work
  ---
  Only Thing that helped was:
  ---
  > sudo apt purge nvidia-*
  > sudo shutdown -r now
  => (nouveau-Driver was automatically installed)
  => Auto-Login to Desktop

  
  But then there was a second Problem:
  
  When > starting Thunderbird, mostly at once, sometimes after > opening some 
E-Mail-Windows, another Error occurred:
  => System freeze for 3 Seconds, then Screen turned to Stripes-Wallpaper => 
Total (Freeze-)Crash
  --
  Later, even with DISabled Hardware-Acceleration, starting both, Firefox and 
Thunderbird led to the System-Crash.
  (Sometimes, the System with nouveau booted and auto-logined into a Black 
Screen with a Mouse-Pointer. Nevertheless the System seemed to work and could 
be rebooted normally.)
  ---
  > CTRL+ALT+F2 => did NOT work
  > Magic Sys-Request (SysRQ): (ALT+PRINT)+ REISUB => did NOT work
  > ping to IP => unreachable
  ---
  After cold Reboot, i tried again to switch back from nouveau- to 
nvidia-Drivers
  > Additional Drivers > Nvidia-304.132
  => Login-Loop
  ---
  > sudo apt purge nvidia-*
  > sudo apt install --reinstall xserver-xorg-core xserver-xorg-video-nouveau
  => Auto-Login
  >  Firefox / Thunderbird => System-(Freeze)-Crash with Stripes-Screen
  ---
  > .. removed and tried to install the old driver (I probably did wrong):
  > sudo apt purge nvidia-*
  > sudo add-apt-repository ppa:graphics-drivers/ppa
  > sudo apt update
  > sudo apt install nvidia-current=304.131-0ubuntu3
  => Login-Loop
  ---
  > sudo apt purge nvidia-*
  > Additional Drivers > nouveau
  > Boot > Grub-2 > "Erweiterte Optionen für Ubuntu" > "Ubuntu, mit Linux 
4.4.0-47-generic" (NO Option=SYSTEMD?)
  => Auto-Login
  >  Firefox / Thunderbird => System-(Freeze)-Crash with Stripes-Screen
  
  What seemed to help was:
  
  > Boot > Grub-2 > "Erweiterte Optionen für Ubuntu" > "Ubuntu, mit Linux 
4.4.0-47-generic (upstart)" (UPSTART!)
  => Auto-Login
  >  Firefox / Thunderbird => seem to work stable!
  => After half an Hour of testing:
  >  open Firefox (Hardware-Acceleration disabled) 
  => System-(Freeze)-Crash with Stripes-Screen
  -
  Because this is far more stable: 
  Changed Standard-Boot in Grub-2 to UpStart instead of SystemD
  ---
  > Terminal >
  sudo apt install upstart-sysv
  su
  sudo shutdown -r now
  ---
  For Roll-Back:
  > Terminal >
  sudo apt install systemd-sysv
  sudo update-initramfs -u
  sudo shutdown -r now
  --
  Sorry, don't know, what 

[Desktop-packages] [Bug 1644666] Re: Xorg crash

[Piraten-Kris Pseudonym]

Boot with Linux 4.4.0-47-generic (upstart) instead of (systemd) now led to tty1.
The Login-Screen did not show-up at all. CTRL+ALT+F7 did not react.

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  New

Bug description:

  Ubuntu 16.04.1 (Automatic Upgrade from 14.04)
  My Onboard-Graphics (AMD-System, ASRock N68C-S UCC): 
Nvidia C61 [GeForce 7025 / nForce 630a]
  ---
  In the Past: 
  => System and Apps worked well with Auto-Login enabled.
  To eliminate Hardware-Errors:
  > Memtest
  > Boot with Windows-XP
  => No Problems

  
  Problems in short: Linux 4.4.0-47-generic (systemd) and (upstart)
  -- 
  1. nvidia-304.132-0ubuntu0.16.04.2 => Login-Loop
  2. nouveau, Thunderbird, Firefox => System-(Freeze)-Crash with Stripes-Screen
  ---
  I don't know in which Category to sort the Bugs
  So this one is for the (Nr.1) Login-Loop (from tty-Terminal)
  (I already filed another Bug-Report for the (Nr.2) System-(Freeze)-Crash with 
Stripes-Screen)


  First Problem startet on 2016-Nov-05: => Login-Loop
  ---
  I later found out, that one Day before, the following Auto-Updates had been 
installed:
  ---
  libcurl3-gnutls(7.47.0-1ubuntu2.1, 7.47.0-1ubuntu2.2)
  nvidia304(304.131-0ubuntu3, 304.132-0ubuntu0.16.04.2)
  nvidia-opencl-icd-304 (304.131-0ubuntu3, 304.132-0ubuntu0.16.04.2)
  libcurl3(7.47.0-1ubuntu2.1, 7.47.0-1ubuntu2.2)
  ---
  After Shutdown, the next Computer-Start was stuck in a 
  => Login-Loop: After entering the correct Password, the Screen turns black 
for a Second, then the Login-Form shows up again.
  ---
  I tried a few things, that did not help, like: 
  > CTRL+F2 => Terminal > sudo ..
  > apt autoclean
  > apt clean
  > apt autoremove
  > apt update
  > apt upgrade
  > apt dist-upgrade
  > shutdown -r now
  > mv .Xauthority .Xauthority.alt
  > shutdown -r now
  > service lightdm restart
  > shutdown -r now
  > apt purge lightdm
  > apt install lightdm
  > shutdown -r now
  > .. Boot into different Linux-Kernel, .. (upstart), 
  > .. Boot into Recovery-Mode > .. > Repair > ..
  > .. I also tried to install other nvidia-drivers, which, sadly, i did not 
document. 
  => Did NOT work
  ---
  Only Thing that helped was:
  ---
  > sudo apt purge nvidia-*
  > sudo shutdown -r now
  => (nouveau-Driver was automatically installed)
  => Auto-Login to Desktop

  
  But then there was a second Problem:
  
  When > starting Thunderbird, mostly at once, sometimes after > opening some 
E-Mail-Windows, another Error occurred:
  => System freeze for 3 Seconds, then Screen turned to Stripes-Wallpaper => 
Total (Freeze-)Crash
  --
  Later, even with DISabled Hardware-Acceleration, starting both, Firefox and 
Thunderbird led to the System-Crash.
  (Sometimes, the System with nouveau booted and auto-logined into a Black 
Screen with a Mouse-Pointer. Nevertheless the System seemed to work and could 
be rebooted normally.)
  ---
  > CTRL+ALT+F2 => did NOT work
  > Magic Sys-Request (SysRQ): (ALT+PRINT)+ REISUB => did NOT work
  > ping to IP => unreachable
  ---
  After cold Reboot, i tried again to switch back from nouveau- to 
nvidia-Drivers
  > Additional Drivers > Nvidia-304.132
  => Login-Loop
  ---
  > sudo apt purge nvidia-*
  > sudo apt install --reinstall xserver-xorg-core xserver-xorg-video-nouveau
  => Auto-Login
  >  Firefox / Thunderbird => System-(Freeze)-Crash with Stripes-Screen
  ---
  > .. removed and tried to install the old driver (I probably did wrong):
  > sudo apt purge nvidia-*
  > sudo add-apt-repository ppa:graphics-drivers/ppa
  > sudo apt update
  > sudo apt install nvidia-current=304.131-0ubuntu3
  => Login-Loop
  ---
  > sudo apt purge nvidia-*
  > Additional Drivers > nouveau
  > Boot > Grub-2 > "Erweiterte Optionen für Ubuntu" > "Ubuntu, mit Linux 
4.4.0-47-generic" (NO Option=SYSTEMD?)
  => Auto-Login
  >  Firefox / Thunderbird => System-(Freeze)-Crash with Stripes-Screen
  
  What seemed to help was:
  
  > Boot > Grub-2 > "Erweiterte Optionen für Ubuntu" > "Ubuntu, mit Linux 
4.4.0-47-generic (upstart)" (UPSTART!)
  => Auto-Login
  >  Firefox / Thunderbird => seem to work stable!
  => After half an Hour of testing:
  >  open Firefox (Hardware-Acceleration disabled) 
  => System-(Freeze)-Crash with Stripes-Screen
  -
  Because this is far more stable: 
  Changed Standard-Boot in Grub-2 to UpStart instead of SystemD
  ---
  > Terminal >
  sudo apt install upstart-sysv
  su
  sudo shutdown -r now
  ---
  For Roll-Back:
  > Terminal >
  sudo apt install systemd-sysv
  sudo update-initramfs -u
  sudo shutdown -r now
  --
  Sorry, don't know, 

[Desktop-packages] [Bug 1644666] [NEW] Xorg crash

[Piraten-Kris Pseudonym]

Public bug reported:


Ubuntu 16.04.1 (Automatic Upgrade from 14.04)
My Onboard-Graphics (AMD-System, ASRock N68C-S UCC): 
  Nvidia C61 [GeForce 7025 / nForce 630a]
---
In the Past: 
=> System and Apps worked well with Auto-Login enabled.
To eliminate Hardware-Errors:
> Memtest
> Boot with Windows-XP
=> No Problems


Problems in short: Linux 4.4.0-47-generic (systemd) and (upstart)
-- 
1. nvidia-304.132-0ubuntu0.16.04.2 => Login-Loop
2. nouveau, Thunderbird, Firefox => System-(Freeze)-Crash with Stripes-Screen
---
I don't know in which Category to sort the Bugs
So this one is for the (Nr.1) Login-Loop (from tty-Terminal)
(I already filed another Bug-Report for the (Nr.2) System-(Freeze)-Crash with 
Stripes-Screen)


First Problem startet on 2016-Nov-05: => Login-Loop
---
I later found out, that one Day before, the following Auto-Updates had been 
installed:
---
libcurl3-gnutls(7.47.0-1ubuntu2.1, 7.47.0-1ubuntu2.2)
nvidia304(304.131-0ubuntu3, 304.132-0ubuntu0.16.04.2)
nvidia-opencl-icd-304 (304.131-0ubuntu3, 304.132-0ubuntu0.16.04.2)
libcurl3(7.47.0-1ubuntu2.1, 7.47.0-1ubuntu2.2)
---
After Shutdown, the next Computer-Start was stuck in a 
=> Login-Loop: After entering the correct Password, the Screen turns black for 
a Second, then the Login-Form shows up again.
---
I tried a few things, that did not help, like: 
> CTRL+F2 => Terminal > sudo ..
> apt autoclean
> apt clean
> apt autoremove
> apt update
> apt upgrade
> apt dist-upgrade
> shutdown -r now
> mv .Xauthority .Xauthority.alt
> shutdown -r now
> service lightdm restart
> shutdown -r now
> apt purge lightdm
> apt install lightdm
> shutdown -r now
> .. Boot into different Linux-Kernel, .. (upstart), 
> .. Boot into Recovery-Mode > .. > Repair > ..
> .. I also tried to install other nvidia-drivers, which, sadly, i did not 
> document. 
=> Did NOT work
---
Only Thing that helped was:
---
> sudo apt purge nvidia-*
> sudo shutdown -r now
=> (nouveau-Driver was automatically installed)
=> Auto-Login to Desktop


But then there was a second Problem:

When > starting Thunderbird, mostly at once, sometimes after > opening some 
E-Mail-Windows, another Error occurred:
=> System freeze for 3 Seconds, then Screen turned to Stripes-Wallpaper => 
Total (Freeze-)Crash
--
Later, even with DISabled Hardware-Acceleration, starting both, Firefox and 
Thunderbird led to the System-Crash.
(Sometimes, the System with nouveau booted and auto-logined into a Black Screen 
with a Mouse-Pointer. Nevertheless the System seemed to work and could be 
rebooted normally.)
---
> CTRL+ALT+F2 => did NOT work
> Magic Sys-Request (SysRQ): (ALT+PRINT)+ REISUB => did NOT work
> ping to IP => unreachable
---
After cold Reboot, i tried again to switch back from nouveau- to nvidia-Drivers
> Additional Drivers > Nvidia-304.132
=> Login-Loop
---
> sudo apt purge nvidia-*
> sudo apt install --reinstall xserver-xorg-core xserver-xorg-video-nouveau
=> Auto-Login
>  Firefox / Thunderbird => System-(Freeze)-Crash with Stripes-Screen
---
> .. removed and tried to install the old driver (I probably did wrong):
> sudo apt purge nvidia-*
> sudo add-apt-repository ppa:graphics-drivers/ppa
> sudo apt update
> sudo apt install nvidia-current=304.131-0ubuntu3
=> Login-Loop
---
> sudo apt purge nvidia-*
> Additional Drivers > nouveau
> Boot > Grub-2 > "Erweiterte Optionen für Ubuntu" > "Ubuntu, mit Linux 
> 4.4.0-47-generic" (NO Option=SYSTEMD?)
=> Auto-Login
>  Firefox / Thunderbird => System-(Freeze)-Crash with Stripes-Screen

What seemed to help was:

> Boot > Grub-2 > "Erweiterte Optionen für Ubuntu" > "Ubuntu, mit Linux 
> 4.4.0-47-generic (upstart)" (UPSTART!)
=> Auto-Login
>  Firefox / Thunderbird => seem to work stable!
=> After half an Hour of testing:
>  open Firefox (Hardware-Acceleration disabled) 
=> System-(Freeze)-Crash with Stripes-Screen
-
Because this is far more stable: 
Changed Standard-Boot in Grub-2 to UpStart instead of SystemD
---
> Terminal >
sudo apt install upstart-sysv
su
sudo shutdown -r now
---
For Roll-Back:
> Terminal >
sudo apt install systemd-sysv
sudo update-initramfs -u
sudo shutdown -r now
--
Sorry, don't know, what to try next ..

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
Uname: Linux 4.4.0-47-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  304.132  Fri Sep 16 11:02:09 
PDT 2016
 GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64

[Desktop-packages] [Bug 1644661] [NEW] Xorg crash

[Piraten-Kris Pseudonym]

Public bug reported:


Ubuntu 16.04.1 (Automatic Upgrade from 14.04)
My Onboard-Graphics (AMD-System, ASRock N68C-S UCC): 
  Nvidia C61 [GeForce 7025 / nForce 630a]
---
In the Past: 
=> System and Apps worked well with Auto-Login enabled.
To eliminate Hardware-Errors:
> Memtest
> Boot with Windows-XP
=> No Problems


Problems in short: Linux 4.4.0-47-generic (systemd) and (upstart)
-- 
1. nvidia-304.132-0ubuntu0.16.04.2 => Login-Loop
2. nouveau, Thunderbird, Firefox => System-(Freeze)-Crash with Stripes-Screen
---
I don't know in which Category to sort the Bugs
So this one ist for the (Nr.2) System-(Freeze)-Crash with Stripes-Screen
I will try to file another Bug-Report for the (Nr.1) Login-Loop (If it works 
from tty-Terminal)


First Problem startet on 2016-Nov-05: => Login-Loop
---
I later found out, that one Day before, the following Auto-Updates had been 
installed:
---
libcurl3-gnutls(7.47.0-1ubuntu2.1, 7.47.0-1ubuntu2.2)
nvidia304(304.131-0ubuntu3, 304.132-0ubuntu0.16.04.2)
nvidia-opencl-icd-304 (304.131-0ubuntu3, 304.132-0ubuntu0.16.04.2)
libcurl3(7.47.0-1ubuntu2.1, 7.47.0-1ubuntu2.2)
---
After Shutdown, the next Computer-Start was stuck in a 
=> Login-Loop: After entering the correct Password, the Screen turns black for 
a Second, then the Login-Form shows up again.
---
I tried a few things, that did not help, like: 
> CTRL+F2 => Terminal > sudo ..
> apt autoclean
> apt clean
> apt autoremove
> apt update
> apt upgrade
> apt dist-upgrade
> shutdown -r now
> mv .Xauthority .Xauthority.alt
> shutdown -r now
> service lightdm restart
> shutdown -r now
> apt purge lightdm
> apt install lightdm
> shutdown -r now
> .. Boot into different Linux-Kernel, .. (upstart), 
> .. Boot into Recovery-Mode > .. > Repair > ..
> .. I also tried to install other nvidia-drivers, which, sadly, i did not 
> document. 
=> Did NOT work
---
Only Thing that helped was:
---
> sudo apt purge nvidia-*
> sudo shutdown -r now
=> (nouveau-Driver was automatically installed)
=> Auto-Login to Desktop


But then there was a second Problem:

When > starting Thunderbird, mostly at once, sometimes after > opening some 
E-Mail-Windows, another Error occurred:
=> System freeze for 3 Seconds, then Screen turned to Stripes-Wallpaper => 
Total (Freeze-)Crash
--
Later, even with DISabled Hardware-Acceleration, starting both, Firefox and 
Thunderbird led to the System-Crash.
(Sometimes, the System with nouveau booted and auto-logined into a Black Screen 
with a Mouse-Pointer. Nevertheless the System seemed to work and could be 
rebooted normally.)
---
> CTRL+ALT+F2 => did NOT work
> Magic Sys-Request (SysRQ): (ALT+PRINT)+ REISUB => did NOT work
> ping to IP => unreachable
---
After cold Reboot, i tried again to switch back from nouveau- to nvidia-Drivers
> Additional Drivers > Nvidia-304.132
=> Login-Loop
---
> sudo apt purge nvidia-*
> sudo apt install --reinstall xserver-xorg-core xserver-xorg-video-nouveau
=> Auto-Login
>  Firefox / Thunderbird => System-(Freeze)-Crash with Stripes-Screen
---
> .. removed and tried to install the old driver (I probably did wrong):
> sudo apt purge nvidia-*
> sudo add-apt-repository ppa:graphics-drivers/ppa
> sudo apt update
> sudo apt install nvidia-current=304.131-0ubuntu3
=> Login-Loop
---
> sudo apt purge nvidia-*
> Additional Drivers > nouveau
> Boot > Grub-2 > "Erweiterte Optionen für Ubuntu" > "Ubuntu, mit Linux 
> 4.4.0-47-generic" (NO Option=SYSTEMD?)
=> Auto-Login
>  Firefox / Thunderbird => System-(Freeze)-Crash with Stripes-Screen

What seemed to help was:

> Boot > Grub-2 > "Erweiterte Optionen für Ubuntu" > "Ubuntu, mit Linux 
> 4.4.0-47-generic (upstart)" (UPSTART!)
=> Auto-Login
>  Firefox / Thunderbird => seem to work stable!
=> After half an Hour of testing:
>  open Firefox (Hardware-Acceleration disabled) 
=> System-(Freeze)-Crash with Stripes-Screen
-
Because this is far more stable: 
Changed Standard-Boot in Grub-2 to UpStart instead of SystemD
---
> Terminal >
sudo apt install upstart-sysv
su
sudo shutdown -r now
---
For Roll-Back:
> Terminal >
sudo apt install systemd-sysv
sudo update-initramfs -u
sudo shutdown -r now
--
Sorry, don't know, what to try next ..

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
Uname: Linux 4.4.0-47-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.1
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
Date: Thu Nov 24 23:32:54 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu

[Desktop-packages] [Bug 1621620] Re: Broadwell-U screen stopped working after 14.04 update

[kris van der Merwe]

I have moved to Ubuntu 16.04, the dual screen is working there

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

Title:
  Broadwell-U  screen stopped working after 14.04 update

Status in xserver-xorg-video-intel package in Ubuntu:
  New

Bug description:
  I am on Ubuntu 14.04.5 LTS
  I recently updated my laptop to  vmlinuz-4.4.0-37-generic

  After rebooting, I lost my external Monitor (Display application does not 
even detect it )
  This is my main monitor and is connected via HDMI.

  Ive had error messages with Ubuntu an the external screen on Intel
  "Broadwell-U" but this is the first time it cut me off totally.

  Host bridge: Intel Corporation Broadwell-U Host Bridge -OPI (rev 09)
  VGA compatible controller: Intel Corporation Broadwell-U Integrated Graphics 
(rev 09)

  lshw -c video
*-display UNCLAIMED 
 description: VGA compatible controller
 product: Broadwell-U Integrated Graphics
 vendor: Intel Corporation
 physical id: 2
 bus info: pci@:00:02.0
 version: 09
 width: 64 bits
 clock: 33MHz
 capabilities: msi pm vga_controller bus_master cap_list
 configuration: latency=0
 resources: memory:f000-f0ff memory:e000-efff 
ioport:4000(size=64)

  cat /var/log/Xorg.0.log |grep EE
  [27.266] (EE) No devices detected.
  [27.270] (EE) open /dev/dri/card0: No such file or directory
  [27.270] (EE) open /dev/dri/card0: No such file or directory
  [27.270] (EE) Screen 0 deleted because of no matching config section.
  [27.335] (EE) AIGLX: reverting to software rendering

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1621620/+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 1621620] [NEW] Broadwell-U screen stopped working after 14.04 update

[kris van der Merwe]

Public bug reported:

I am on Ubuntu 14.04.5 LTS
I recently updated my laptop to  vmlinuz-4.4.0-37-generic

After rebooting, I lost my external Monitor (Display application does not even 
detect it )
This is my main monitor and is connected via HDMI.

Ive had error messages with Ubuntu an the external screen on Intel
"Broadwell-U" but this is the first time it cut me off totally.

Host bridge: Intel Corporation Broadwell-U Host Bridge -OPI (rev 09)
VGA compatible controller: Intel Corporation Broadwell-U Integrated Graphics 
(rev 09)

lshw -c video
  *-display UNCLAIMED 
   description: VGA compatible controller
   product: Broadwell-U Integrated Graphics
   vendor: Intel Corporation
   physical id: 2
   bus info: pci@:00:02.0
   version: 09
   width: 64 bits
   clock: 33MHz
   capabilities: msi pm vga_controller bus_master cap_list
   configuration: latency=0
   resources: memory:f000-f0ff memory:e000-efff 
ioport:4000(size=64)

cat /var/log/Xorg.0.log |grep EE
[27.266] (EE) No devices detected.
[27.270] (EE) open /dev/dri/card0: No such file or directory
[27.270] (EE) open /dev/dri/card0: No such file or directory
[27.270] (EE) Screen 0 deleted because of no matching config section.
[27.335] (EE) AIGLX: reverting to software rendering

** Affects: xserver-xorg-video-intel (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Broadwell-U  screen stopped working after 14.04 update

Status in xserver-xorg-video-intel package in Ubuntu:
  New

Bug description:
  I am on Ubuntu 14.04.5 LTS
  I recently updated my laptop to  vmlinuz-4.4.0-37-generic

  After rebooting, I lost my external Monitor (Display application does not 
even detect it )
  This is my main monitor and is connected via HDMI.

  Ive had error messages with Ubuntu an the external screen on Intel
  "Broadwell-U" but this is the first time it cut me off totally.

  Host bridge: Intel Corporation Broadwell-U Host Bridge -OPI (rev 09)
  VGA compatible controller: Intel Corporation Broadwell-U Integrated Graphics 
(rev 09)

  lshw -c video
*-display UNCLAIMED 
 description: VGA compatible controller
 product: Broadwell-U Integrated Graphics
 vendor: Intel Corporation
 physical id: 2
 bus info: pci@:00:02.0
 version: 09
 width: 64 bits
 clock: 33MHz
 capabilities: msi pm vga_controller bus_master cap_list
 configuration: latency=0
 resources: memory:f000-f0ff memory:e000-efff 
ioport:4000(size=64)

  cat /var/log/Xorg.0.log |grep EE
  [27.266] (EE) No devices detected.
  [27.270] (EE) open /dev/dri/card0: No such file or directory
  [27.270] (EE) open /dev/dri/card0: No such file or directory
  [27.270] (EE) Screen 0 deleted because of no matching config section.
  [27.335] (EE) AIGLX: reverting to software rendering

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1621620/+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 1432194] Re: Graphics unstable on Ubuntu 14.04 and 14.10 using Intel HD Graphics 5500

[kris van der Merwe]

Serious bug

Lost my second screen via HDMI on kernel update to
vmlinuz-4.4.0-37-generic

Host bridge: Intel Corporation Broadwell-U Host Bridge -OPI (rev 09)
VGA compatible controller: Intel Corporation Broadwell-U Integrated Graphics 
(rev 09)

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

Title:
  Graphics unstable on Ubuntu 14.04 and 14.10 using Intel HD Graphics
  5500

Status in OEM Priority Project:
  Fix Released
Status in xf86-video-intel:
  Unknown
Status in xserver-xorg-video-intel package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-intel-lts-utopic package in Ubuntu:
  Invalid
Status in xserver-xorg-video-intel-lts-utopic source package in Trusty:
  Fix Released
Status in xserver-xorg-video-intel source package in Utopic:
  Fix Released

Bug description:
  Trying to achieve: Get a more stable graphics environment up and
  running

  Steps to take:  basic ubtuntu 14.04 install.  Boot up and run for a
  few minutes and then ...

  What happens: After running for a few minutes the graphics gets
  flacky.

  What should happen:  Graphics should not get flaky.

  I have just installed ubuntu 14.04 on my new thinkpad t450s.
  Everything basically works, but something is very flaky about my
  keyboard or display or both.  After running for awhile some apps
  (E.g., thunderbird and sometimes emacs for example) will display
  garbage.  If I refresh by moving the screen around or changing
  buffers/tabs/etc. they can often recover.

  I see that there is an [Intel(R) Graphics Installer for Linux*
  1.0.7](https://01.org/linuxgraphics/downloads/2014/intelr-graphics-
  installer-linux-1.0.7). I am leery about just loading this and running
  it.  Any suggestions about how I should proceed?

  $ sudo lshw -c video
*-display
 description: VGA compatible controller
 product: Broadwell-U Integrated Graphics
 vendor: Intel Corporation
 physical id: 2
 bus info: pci@:00:02.0
 version: 09
 width: 64 bits
 clock: 33MHz
 capabilities: msi pm vga_controller bus_master cap_list rom
 configuration: driver=i915 latency=0
 resources: irq:63 memory:e000-e0ff 
memory:d000-dfff ioport:3000(size=64)
  $ modinfo i915 | head
  filename:   
/lib/modules/3.16.0-31-generic/kernel/drivers/gpu/drm/i915/i915.ko
  license:GPL and additional rights
  description:Intel Graphics
  author: Tungsten Graphics, Inc.
  srcversion: 9929027A8A6F05972AD6986
  alias:  pci:v8086d22B3sv*sd*bc03sc*i*
  alias:  pci:v8086d22B2sv*sd*bc03sc*i*
  alias:  pci:v8086d22B1sv*sd*bc03sc*i*
  alias:  pci:v8086d22B0sv*sd*bc03sc*i*
  alias:  pci:v8086d162Dsv*sd*bc03sc*i*
  $ uname -a
  Linux mypad 3.16.0-31-generic #43~14.04.1-Ubuntu SMP Tue Mar 10 20:13:38 
UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1432194/+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 1491249] Re: Regression: Visual new email notification no longer working in 38.2.0

[Kris M]

I wasn't aware it was supposed to change color...  I get a sound and a 
small number in the icon on the Launcher.  Nice.  Thanks!  45.2.0 in 16.04.1

On 09/02/2016 09:39 AM, మంగిపూడి కోదండరామ్ (Mangipudi Kodanda Ram) wrote:
> A fresh install of Ubuntu 16.04.1 yesterday. Completely updated to the
> latest software. Configured mail accounts. Initially the thunderbird
> notification icon color and played a sound when a new mail arrived *and*
> thunderbird window is open. But there was no OSD notification. When the
> thunderbird window is closed, no new email notifications whatsoever (no
> sound, no color change and no OSD). Now it is not changing the color but
> playing the sound when thunderbird is kept open.
>
> I have calendar addon only, no other.
>
> My thunderbird version is 45.2.0.
>
> This is a strange behavior and poor integration into the DE.
> Disappointed to see after my switch from KDE to Unity.
>

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

Title:
  Regression: Visual new email notification no longer working in 38.2.0

Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  One feature of Thunderbird is a notification through the system
  notification system whenever a new email arrives in the inbox. With
  the recent update to version 38.2 this notification no longer works.
  The "new email" sound plays, but the visual notification is no longer
  displayed.

  This is clearly a regression, since it worked with the previous
  versions of Thunderbird.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: thunderbird 1:38.2.0+build1-0ubuntu0.15.04.1
  ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4
  Uname: Linux 3.19.0-26-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.17.2-0ubuntu1.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   jan2434 F...m pulseaudio
   /dev/snd/controlC1:  jan2434 F pulseaudio
   /dev/snd/controlC0:  jan2434 F pulseaudio
  BuildID: 20150818212443
  Channel: Unavailable
  CurrentDesktop: GNOME
  Date: Wed Sep  2 08:35:06 2015
  EcryptfsInUse: Yes
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2015-01-30 (214 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  IpRoute:
   default via 192.168.1.1 dev eth0  proto static  metric 1024 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.30
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-90222358-6460-4247-96c9-9500e2150311
  Plugins: Gnome Shell Integration - 
/usr/lib/mozilla/plugins/libgnome-shell-browser-plugin.so (gnome-shell)
  PrefSources:
   prefs.js
   
[Profile]/extensions/{847b3a00-7ab1-11d4-8f02-006008948af5}/defaults/preferences/enigmail.js
   
[Profile]/extensions/{e2fda1a4-762b-4020-b5ad-a41df1933103}/defaults/preferences/lightning.js
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=38.2.0/20150818212443 (In use)
  RelatedPackageVersions: gnome-shell 3.14.4-0ubuntu1
  RfKill:
   0: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  SubmittedCrashIDs: bp-90222358-6460-4247-96c9-9500e2150311
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/14/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0310JH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd07/14/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1491249/+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 1576163] Re: Libreoffice crashes when opening a dialog

[Kris]

Mattias you are correct about that other bug. A temporary solution that
works is installing xserver-xorg-video-intel.

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

Title:
  Libreoffice crashes when opening a dialog

Status in libreoffice package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  When any type of dialog window opens, libreoffice crashes causing
  lightdm (unity?) to crash aswell.

  Since not only libreoffice crashes, but also lightdm/unity, all
  programs will stop causing work in progress to be lost.

  Ubuntu: Ubuntu 16.04 LTS
  libreoffice: 1:5.1.2

  Relevant dmesg output:
  [91484.085656] drm/i915: Resetting chip after gpu hang
  [91838.035765] [drm] stuck on render ring
  [91838.036466] [drm] GPU HANG: ecode 7:0:0x85dc, in Xorg [24404], reason: 
Ring hung, action: reset
  ...
  [91848.037375] Hardware name: LENOVO 20EF000SMN/20EF000SMN, BIOS GNET73WW 
(2.21 ) 03/12/2015

  Since the gpu hangs, this is likely a problem with intel gfx drivers.
  Should be of high importance since all work in progress is lost dues
  to complete lightdm crash.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1576163/+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 1574266] Re: Xorg freeze [drm] stuck on render ring - gpu hanging too fast, banning

[Kris]

Can confirm: installing xserver-xorg-video-intel solves the problem even
with nvidia  650m optimus (intel running via bumblebee)

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

Title:
  Xorg freeze [drm] stuck on render ring - gpu hanging too fast, banning

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  dmesg output :

  [ 8815.416923] [drm] stuck on render ring
  [ 8815.417367] [drm] GPU HANG: ecode 6:0:0x05b2c6c5, in Compositor [21164], 
reason: Ring hung, action: reset
  [ 8815.419462] drm/i915: Resetting chip after gpu hang
  [ 8821.417592] [drm] stuck on render ring
  [ 8821.418007] [drm] GPU HANG: ecode 6:0:0xfeff, in Xorg [1058], reason: 
Ring hung, action: reset
  [ 8821.420108] drm/i915: Resetting chip after gpu hang
  [ 8827.430254] [drm] stuck on render ring
  [ 8827.430672] [drm] GPU HANG: ecode 6:0:0xfeff, in compiz [3107], 
reason: Ring hung, action: reset
  [ 8827.432786] drm/i915: Resetting chip after gpu hang
  [ 8833.418862] [drm] stuck on render ring
  [ 8833.419454] [drm] GPU HANG: ecode 6:0:0xfeff, in compiz [3107], 
reason: Ring hung, action: reset
  [ 8833.421551] drm/i915: Resetting chip after gpu hang
  [ 8839.419503] [drm] stuck on render ring
  [ 8839.419971] [drm] GPU HANG: ecode 6:0:0xfeff, in Compositor [21164], 
reason: Ring hung, action: reset
  [ 8839.422060] drm/i915: Resetting chip after gpu hang
  [ 8845.432118] [drm] stuck on render ring
  [ 8845.432647] [drm] GPU HANG: ecode 6:0:0xfeff, in Xorg [1058], reason: 
Ring hung, action: reset
  [ 8845.434799] drm/i915: Resetting chip after gpu hang
  [ 8851.432751] [drm] stuck on render ring
  [ 8851.433142] [drm] GPU HANG: ecode 6:0:0xfeff, in compiz [6783], 
reason: Ring hung, action: reset
  [ 8851.435224] drm/i915: Resetting chip after gpu hang
  [ 8857.457381] [drm] stuck on render ring
  [ 8857.457797] [drm] GPU HANG: ecode 6:0:0xfeff, in compiz [6783], 
reason: Ring hung, action: reset
  [ 8857.459883] drm/i915: Resetting chip after gpu hang
  [ 8863.458003] [drm] stuck on render ring
  [ 8863.458555] [drm] GPU HANG: ecode 6:0:0xfeff, in Xorg [1058], reason: 
Ring hung, action: reset
  [ 8863.460640] drm/i915: Resetting chip after gpu hang
  [ 8869.458654] [drm] stuck on render ring
  [ 8869.459001] [drm] GPU HANG: ecode 6:0:0xfeff, in Xorg [1058], reason: 
Ring hung, action: reset
  [ 8869.459095] [drm:i915_set_reset_status [i915]] *ERROR* gpu hanging too 
fast, banning!
  [ 8869.461116] drm/i915: Resetting chip after gpu hang
  [ 8875.435238] [drm] stuck on render ring
  [ 8875.435606] [drm] GPU HANG: ecode 6:0:0xfeff, in Compositor [21164], 
reason: Ring hung, action: reset
  [ 8875.437697] drm/i915: Resetting chip after gpu hang
  [ 8881.447863] [drm] stuck on render ring
  [ 8881.448251] [drm] GPU HANG: ecode 6:0:0xfeff, in Compositor [21164], 
reason: Ring hung, action: reset
  [ 8881.450331] drm/i915: Resetting chip after gpu hang
  [ 8887.436497] [drm] stuck on render ring
  [ 8887.436876] [drm] GPU HANG: ecode 6:0:0xbb88, in compiz [6817], 
reason: Ring hung, action: reset
  [ 8887.438961] drm/i915: Resetting chip after gpu hang
  [ 8893.437078] [drm] stuck on render ring
  [ 8893.437471] [drm] GPU HANG: ecode 6:0:0xfeff, in compiz [6817], 
reason: Ring hung, action: reset
  [ 8893.439562] drm/i915: Resetting chip after gpu hang

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  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: Sun Apr 24 15:57:17 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Intel Corporation 2nd Generation Core Processor Family 
Integrated Graphics Controller [8086:2002]
  InstallationDate: Installed on 2016-04-23 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=45576678-3e92-4769-b6d3-3e3cafa54c2e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel 

[Desktop-packages] [Bug 1491249] Re: Regression: Visual new email notification no longer working in 38.2.0

[Kris M]

I notice this as well.  14.04.3 Ubuntu Unity,  38.4.0 TBird.

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

Title:
  Regression: Visual new email notification no longer working in 38.2.0

Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  One feature of Thunderbird is a notification through the system
  notification system whenever a new email arrives in the inbox. With
  the recent update to version 38.2 this notification no longer works.
  The "new email" sound plays, but the visual notification is no longer
  displayed.

  This is clearly a regression, since it worked with the previous
  versions of Thunderbird.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: thunderbird 1:38.2.0+build1-0ubuntu0.15.04.1
  ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4
  Uname: Linux 3.19.0-26-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.17.2-0ubuntu1.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   jan2434 F...m pulseaudio
   /dev/snd/controlC1:  jan2434 F pulseaudio
   /dev/snd/controlC0:  jan2434 F pulseaudio
  BuildID: 20150818212443
  Channel: Unavailable
  CurrentDesktop: GNOME
  Date: Wed Sep  2 08:35:06 2015
  EcryptfsInUse: Yes
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2015-01-30 (214 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  IpRoute:
   default via 192.168.1.1 dev eth0  proto static  metric 1024 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.30
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-90222358-6460-4247-96c9-9500e2150311
  Plugins: Gnome Shell Integration - 
/usr/lib/mozilla/plugins/libgnome-shell-browser-plugin.so (gnome-shell)
  PrefSources:
   prefs.js
   
[Profile]/extensions/{847b3a00-7ab1-11d4-8f02-006008948af5}/defaults/preferences/enigmail.js
   
[Profile]/extensions/{e2fda1a4-762b-4020-b5ad-a41df1933103}/defaults/preferences/lightning.js
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=38.2.0/20150818212443 (In use)
  RelatedPackageVersions: gnome-shell 3.14.4-0ubuntu1
  RfKill:
   0: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  SubmittedCrashIDs: bp-90222358-6460-4247-96c9-9500e2150311
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/14/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0310JH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd07/14/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1491249/+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 1484380] Re: Xorg regular crash on wily

[Kris Anoikesis]

If anything was hoped to have been fixed with the master branch version of the 
xserver-xorg-video-intel, well, then, it does nothing to address this crash. 
And I got no logs to show.
Is there any way to throttle the log output to a level that would both prevent 
excessive disk usage and preserve the most vital debug info at the same time?

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

Title:
  Xorg regular crash on wily

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

Bug description:
  After upgrading to wily, I started to get regular random Xorg crash
  (and so, session restarting and such). This can happen multiple times
  a day. I've retried installing the latest intel driver from the xorg-
  edgers ppa as Timo recommended, but the crash is still there.

  Attached the stacktrace in gdb.txt

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xserver-xorg-video-intel 
2:2.99.917+git20150810.4cea8037-0ubuntu0sarvatt [origin: unknown]
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.18-0ubuntu6
  Architecture: amd64
  BootLog:
   [FAILED] Failed to start LSB: Start NTP daemon.
   See 'systemctl status ntp.service' for details.
   [  OK  ] Started Detect the available GPUs and deal with any system 
changes.
Starting Light Display Manager...
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Aug 13 08:42:01 2015
  DistUpgraded: 2014-10-31 12:06:43,271 DEBUG enabling apt cron job
  DistroCodename: wily
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:21da]
  InstallationDate: Installed on 2012-05-28 (1171 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  MachineType: LENOVO 4287CTO
  ProcEnviron:
   LANGUAGE=fr_FR
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.1.0-3-generic 
root=UUID=a9f4b475-e4ce-45ed-aa33-9b92e52c49b0 ro quiet splash nomdmonddf 
nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw 
nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf 
nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=7
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to wily on 2014-10-31 (285 days ago)
  dmi.bios.date: 02/14/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET58WW (1.28 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4287CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8DET58WW(1.28):bd02/14/2012:svnLENOVO:pn4287CTO:pvrThinkPadX220:rvnLENOVO:rn4287CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4287CTO
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.1+15.10.20150627.1-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.62-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150810.4cea8037-0ubuntu0sarvatt
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Thu Aug 13 08:16:24 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 728 
   vendor LGD
  xserver.version: 2:1.17.2-1ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1484380/+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 1484380] Re: Xorg regular crash on wily

[Kris Anoikesis]

I installed the test build the other day and no crash thus far. @Timo, does 
this build contain any actual fixes or am I just being lucky?
I gave up on putting up with xorg frantically logging to Xorg.0.log after the 
file exceeded 5GB so I guess I'd rather not rely on my luck...

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

Title:
  Xorg regular crash on wily

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

Bug description:
  After upgrading to wily, I started to get regular random Xorg crash
  (and so, session restarting and such). This can happen multiple times
  a day. I've retried installing the latest intel driver from the xorg-
  edgers ppa as Timo recommended, but the crash is still there.

  Attached the stacktrace in gdb.txt

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xserver-xorg-video-intel 
2:2.99.917+git20150810.4cea8037-0ubuntu0sarvatt [origin: unknown]
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.18-0ubuntu6
  Architecture: amd64
  BootLog:
   [FAILED] Failed to start LSB: Start NTP daemon.
   See 'systemctl status ntp.service' for details.
   [  OK  ] Started Detect the available GPUs and deal with any system 
changes.
Starting Light Display Manager...
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Aug 13 08:42:01 2015
  DistUpgraded: 2014-10-31 12:06:43,271 DEBUG enabling apt cron job
  DistroCodename: wily
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:21da]
  InstallationDate: Installed on 2012-05-28 (1171 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  MachineType: LENOVO 4287CTO
  ProcEnviron:
   LANGUAGE=fr_FR
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.1.0-3-generic 
root=UUID=a9f4b475-e4ce-45ed-aa33-9b92e52c49b0 ro quiet splash nomdmonddf 
nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw 
nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf 
nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=7
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to wily on 2014-10-31 (285 days ago)
  dmi.bios.date: 02/14/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET58WW (1.28 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4287CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8DET58WW(1.28):bd02/14/2012:svnLENOVO:pn4287CTO:pvrThinkPadX220:rvnLENOVO:rn4287CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4287CTO
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.1+15.10.20150627.1-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.62-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150810.4cea8037-0ubuntu0sarvatt
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Thu Aug 13 08:16:24 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 728 
   vendor LGD
  xserver.version: 2:1.17.2-1ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1484380/+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 1484380] Re: Xorg regular crash on wily

[Kris Anoikesis]

Hi all,

The exact same thing started bugging me as well. A handful of data:
Kubuntu 15.10, intel gpu, xserver-xorg-video-intel == 2:2.99.917-1ubuntu1.
Will it do any good to post my logs?

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

Title:
  Xorg regular crash on wily

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

Bug description:
  After upgrading to wily, I started to get regular random Xorg crash
  (and so, session restarting and such). This can happen multiple times
  a day. I've retried installing the latest intel driver from the xorg-
  edgers ppa as Timo recommended, but the crash is still there.

  Attached the stacktrace in gdb.txt

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xserver-xorg-video-intel 
2:2.99.917+git20150810.4cea8037-0ubuntu0sarvatt [origin: unknown]
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.18-0ubuntu6
  Architecture: amd64
  BootLog:
   [FAILED] Failed to start LSB: Start NTP daemon.
   See 'systemctl status ntp.service' for details.
   [  OK  ] Started Detect the available GPUs and deal with any system 
changes.
Starting Light Display Manager...
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Aug 13 08:42:01 2015
  DistUpgraded: 2014-10-31 12:06:43,271 DEBUG enabling apt cron job
  DistroCodename: wily
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:21da]
  InstallationDate: Installed on 2012-05-28 (1171 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  MachineType: LENOVO 4287CTO
  ProcEnviron:
   LANGUAGE=fr_FR
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.1.0-3-generic 
root=UUID=a9f4b475-e4ce-45ed-aa33-9b92e52c49b0 ro quiet splash nomdmonddf 
nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw 
nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf 
nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=7
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to wily on 2014-10-31 (285 days ago)
  dmi.bios.date: 02/14/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET58WW (1.28 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4287CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8DET58WW(1.28):bd02/14/2012:svnLENOVO:pn4287CTO:pvrThinkPadX220:rvnLENOVO:rn4287CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4287CTO
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.1+15.10.20150627.1-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.62-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150810.4cea8037-0ubuntu0sarvatt
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Thu Aug 13 08:16:24 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 728 
   vendor LGD
  xserver.version: 2:1.17.2-1ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1484380/+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 1275164] Re: inkscape crashed with SIGSEGV in sp_ctrlpoint_set_color()

[Kris]

The only thing I could think if is a NULL check on line 143 for item-canvas.
But if this would be the case, is not there a more important underlying issue?

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

Title:
  inkscape crashed with SIGSEGV in sp_ctrlpoint_set_color()

Status in Inkscape: A Vector Drawing Tool:
  Incomplete
Status in inkscape package in Ubuntu:
  New

Bug description:
  it happens sometimes right after the clean empty devs  save 
  Remove a horizontal guide line

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: inkscape 0.48.4-3ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0
  Uname: Linux 3.13.0-6-generic x86_64
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Feb  1 01:42:37 2014
  ExecutablePath: /usr/bin/inkscape
  InstallationDate: Installed on 2013-12-12 (50 days ago)
  InstallationMedia: Kubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  ProcCmdline: /usr/bin/inkscape
  ProcEnviron:
   LANGUAGE=de:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x74cb51 
_Z22sp_ctrlpoint_set_colorP11SPCtrlPointj+33:   cmp(%rdx),%rax
   PC (0x0074cb51) ok
   source (%rdx) (0x) not located in a known VMA region 
(needed readable region)!
   destination %rax ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: inkscape
  StacktraceTop:
   sp_ctrlpoint_set_color(SPCtrlPoint*, unsigned int) ()
   sp_guideline_set_color(SPGuideLine*, unsigned int) ()
   sp_dt_guide_event(SPCanvasItem*, _GdkEvent*, void*) ()
   sp_marshal_BOOLEAN__POINTER ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: inkscape crashed with SIGSEGV in sp_ctrlpoint_set_color()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom debian-tor dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/inkscape/+bug/1275164/+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 810238] Re: inkscape crashed with SIGABRT in raise()

[Kris]

Closing report by lack of feedback.
Feel free to reopen this report when the issue reappears.

** Changed in: inkscape
   Status: Incomplete = Invalid

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

Title:
  inkscape crashed with SIGABRT in raise()

Status in Inkscape: A Vector Drawing Tool:
  Invalid
Status in inkscape package in Ubuntu:
  Confirmed

Bug description:
  Crash when trying to edit a shadow filter

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: inkscape 0.48.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-5.6-generic 3.0.0-rc7
  Uname: Linux 3.0.0-5-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Wed Jul 13 22:19:22 2011
  ExecutablePath: /usr/bin/inkscape
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1)
  ProcCmdline: inkscape
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: inkscape
  StacktraceTop:
   raise () from /lib/x86_64-linux-gnu/libc.so.6
   abort () from /lib/x86_64-linux-gnu/libc.so.6
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   sp_document_maybe_done(SPDocument*, char const*, unsigned int, 
Glib::ustring) ()
  Title: inkscape crashed with SIGABRT in raise()
  UpgradeStatus: Upgraded to oneiric on 2011-07-13 (0 days ago)
  UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare

To manage notifications about this bug go to:
https://bugs.launchpad.net/inkscape/+bug/810238/+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 1170647] Re: Clicking on Nautilus’ launcher icon opens new window instead of restoring the minimized one when browsing external drives/locations

[Kris Rudra]

confirm bug exists. Ubuntu Trusty x64

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

Title:
  Clicking on Nautilus’ launcher icon opens new window instead of
  restoring the minimized one when browsing external drives/locations

Status in “bamf” package in Ubuntu:
  Triaged
Status in “nautilus” package in Ubuntu:
  Triaged
Status in “unity” package in Ubuntu:
  Triaged

Bug description:
  Sometimes left clicking the nautilus launcher icon doesn't bring up a
  minimized nautilus window. Instead of restoring the window a new
  instance of nautilus is showing up.

  Steps to reproduce:

  1. Open a nautilus window by clicking on the launcher icon.
  2. Navigate to a symlinked directory whose target is located on a different 
harddrive (for example: a symlink to a folder on a sd-card).
  3. Minimize the nautilus window.
  4. Try to bring up that window again by clicking the launcher icon.

  What happens:

  1. A new instance (window) of nautilus is opened.
  2. There's no obvious way to access the first window again. The only way is 
ALT+TAB.

  What schould happen:

  If a nautilus window is already open and minimized clicking the
  launcher icon should bring up that window. This was the behavior of
  nautilus windows in Ubuntu 12.10 (quantal).

  Ubuntu 13.04 Raring Ringtail (development branch)
  nautilus 3.6.3-0ubuntu16
  unity 7.0.0daily13.04.18~13.04-0ubuntu1

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: nautilus 1:3.6.3-0ubuntu16
  ProcVersionSignature: Ubuntu 3.8.0-18.28-generic 3.8.6
  Uname: Linux 3.8.0-18-generic i686
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: i386
  Date: Fri Apr 19 11:33:13 2013
  EcryptfsInUse: Yes
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b'814x493+136+38'
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'182'
  InstallationDate: Installed on 2011-07-23 (635 days ago)
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110426)
  MarkForUpload: True
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to raring on 2013-04-14 (4 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bamf/+bug/1170647/+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 1276379] Re: fglrx-installer 2:13.101-0ubuntu0.0.1 fails with some legacy devices (Radeon HD 2000 3000 4000)

[kris van der Merwe]

Same problem since updating to Ubuntu 12.04.4

Overheating 

No 3D acceleration
fglrxinfo
X Error of failed request:  BadRequest (invalid request code or no such 
operation)

HP pavillion

lspci |grep VGA
01:05.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
RS880M [Mobility Radeon HD 4225/4250]
02:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Park 
[Mobility Radeon HD 5430/5450/5470]

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

Title:
  fglrx-installer 2:13.101-0ubuntu0.0.1 fails with some legacy devices
  (Radeon HD 2000 3000 4000)

Status in “fglrx-installer” package in Ubuntu:
  Confirmed

Bug description:
  [Updated description]

  Update of the fglrx-driver (version 2:13.101-0ubuntu0.0.1 on 2014-02-03) 
brought by update-manager (through ubuntu-updates repos) on Precise doesn't 
work on some legacy devices.
  The main symptom is the fallback to unity-2D.
   
  This bug seems target only Precise with no LTS Enablement Stack activated, in 
other words with Linux 3.2.x and XServer 7.6.
  == please : confirm or infirm using:
  uname -rm
  apt-cache policy xserver-xorg

  It may be in relation with #1058040, about non-support for Radeon [Mobility] 
HD 2xxx, 3xxx, 4xxx on Ubuntu 12.10 and higher.
  __

  1)Description:Ubuntu 12.04.4 LTS
  Release:  12.04
  Architecture: amd64

  2) apt-cache policy fglrx fglrx-amdcccle
  fglrx:
    Installé : 2:13.101-0ubuntu0.0.1
    Candidat : 2:13.101-0ubuntu0.0.1
   Table de version :
   *** 2:13.101-0ubuntu0.0.1 0
  500 http://fr.archive.ubuntu.com/ubuntu/ precise-updates/restricted 
amd64 Packages
  100 /var/lib/dpkg/status
   2:8.960-0ubuntu1 0
  500 http://fr.archive.ubuntu.com/ubuntu/ precise/restricted amd64 
Packages
  fglrx-amdcccle:
    Installé : 2:13.101-0ubuntu0.0.1
    Candidat : 2:13.101-0ubuntu0.0.1

  3) I expected that the driver :
   - set up
   - work

  4) It did'nt work :
   - Ubuntu was very slow
   - Unity fall in Unity-2d mode
   - when I taped CTRL+SUPER, desktops appears blue
   - fglrx-amdcccle failed
   - fans were turning at a high speed
   - lots of warning messages as described bellow

  5) Workaround
  I had to downgrade manually the driver to the old 8.960, which works without 
problem.
  You could do it using Synaptics our using the CLI

  I tried to do an apt-get remove fglrx fglrx-amdcccle but apt-get gaves me 
fglrx-updates in replacement , with the same issues. I experimented 
fglrx-update some months (a year?) ago with similar problems, but at that time 
it was a conscient experimentation.
  The 13.101-0ubuntu0.0.1 could maybe stay in fglrx-updates, and no fglrx ?

  

  
  ~$ sudo aticonfig
  aticonfig: No supported adapters detected

  ~$ lspci -nn | grep VGA02:00.0 VGA compatible controller [0300]:
  Advanced Micro Devices, Inc. [AMD/ATI] RV710/M92 [Mobility Radeon HD
  4530/4570/545v] [1002:9553]

   ~$ grep /drivers/ /var/log/Xorg.0.log
  [26.888] (II) Loading 
/usr/lib/x86_64-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so
  [27.015] (II) Loading 
/usr/lib/x86_64-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so
  [27.016] (II) Loading /usr/lib/xorg/modules/drivers/ati_drv.so
  [27.017] (II) Loading /usr/lib/xorg/modules/drivers/radeon_drv.so
  [27.018] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
  [27.019] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
  [27.122] (II) Loading /usr/lib/xorg/modules/drivers/radeon_drv.so

  ~$ dmesg | grep fglrx
  [   28.612217] [fglrx] Maximum main memory to use for locked dma buffers: 
3657 MBytes.
  [   28.613015] [fglrx:firegl_init_device_list] *ERROR* No supported display 
adapters were found
  [   28.613021] [fglrx:firegl_init_module] *ERROR* firegl_init_devices failed
  [   28.775649] [fglrx] Maximum main memory to use for locked dma buffers: 
3657 MBytes.
  [   28.776032] [fglrx:firegl_init_device_list] *ERROR* No supported display 
adapters were found
  [   28.776036] [fglrx:firegl_init_module] *ERROR* firegl_init_devices failed

  ~$ fglrxinfo
  X Error of failed request:  BadRequest (invalid request code or no such 
operation)
    Major opcode of failed request:  153 (GLX)
    Minor opcode of failed request:  19 (X_GLXQueryServerString)
    Serial number of failed request:  12
    Current serial number in output stream:  12

  ~$ glxinfo
  name of display: :0.0
  X Error of failed request:  BadRequest (invalid request code or no such 
operation)
    Major opcode of failed request:  153 (GLX)
    Minor opcode of failed request:  19 (X_GLXQueryServerString)
    Serial number of failed request:  12
    Current serial number in output stream:  12

  
  ProblemType: Bug
  

[Desktop-packages] [Bug 1244338] Re: External tool won't run if Save is set to All documents

[Kris]

I confirm that this fixes the problem, thanks!

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

Title:
  External tool won't run if Save is set to All documents

Status in “gedit” package in Ubuntu:
  Confirmed

Bug description:
  Since upgrading to Ubuntu 13.10/gedit 3.8.3 external tools won't be
  run if the Save option is set to All documents. If the setting it
  to None or Current documents then the tool will run again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1244338/+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 1171342] Re: mouse scroll wheel not working in gedit System Monitor

[Kris]

It seemed that my problem was related to Bug #1200829. For those of you
who experience the same problem I had, the fix is given in the PPA:

ppa:mc3man/test-scroll

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

Title:
  mouse scroll wheel not working in gedit  System Monitor

Status in GTK+ GUI Toolkit:
  Fix Released
Status in X.Org X server:
  Confirmed
Status in “gtk+3.0” package in Ubuntu:
  Fix Released
Status in “xorg-server” package in Ubuntu:
  Triaged

Bug description:
  Open System Monitor

  Using mouse wheel button - scroll up or down - list does not move. If
  Press the wheel button and then scroll up or down the list will move.

  This also occurs in Gedit. Firefox and Terminal work as expected. IE
  do not need to press the wheel and then scroll

  Linux kylea-hpxt 3.8.0-19-generic #29-Ubuntu SMP Wed Apr 17 18:16:28 UTC 2013 
x86_64 x86_64 x86_64 GNU/Linux
  Description:  Ubuntu 13.04
  Release:  13.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1171342/+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 1171342] Re: mouse scroll wheel not working in gedit System Monitor

[Kris]

I'm having the same problem and adding the PPA ppa:townsend/gtk-
testing doesn't help. After I add it and run apt-get update there's
nothing to upgrade.

Also, the title of the bug suggests that there might also be a problem
with System Monitor, but I only experience the issue in gedit. All other
applications are scrolling just fine.

Any ideas? Would this be a separate bug?


I've tried disabling workspace scrolling and switching between overlay/legacy 
scrollbars, but that made no difference.

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

Title:
  mouse scroll wheel not working in gedit  System Monitor

Status in GTK+ GUI Toolkit:
  Fix Released
Status in X.Org X server:
  Confirmed
Status in “gtk+3.0” package in Ubuntu:
  Fix Released
Status in “xorg-server” package in Ubuntu:
  Triaged

Bug description:
  Open System Monitor

  Using mouse wheel button - scroll up or down - list does not move. If
  Press the wheel button and then scroll up or down the list will move.

  This also occurs in Gedit. Firefox and Terminal work as expected. IE
  do not need to press the wheel and then scroll

  Linux kylea-hpxt 3.8.0-19-generic #29-Ubuntu SMP Wed Apr 17 18:16:28 UTC 2013 
x86_64 x86_64 x86_64 GNU/Linux
  Description:  Ubuntu 13.04
  Release:  13.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1171342/+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 1163241] Re: inkscape crashed with SIGSEGV in Inkscape::Preferences::_getNode()

[Kris]

Patch in comment 8 committed to trunk in r12902

** Changed in: inkscape
   Status: In Progress = Fix Committed

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

Title:
  inkscape crashed with SIGSEGV in Inkscape::Preferences::_getNode()

Status in Inkscape: A Vector Drawing Tool:
  Fix Committed
Status in “inkscape” package in Ubuntu:
  Confirmed

Bug description:
  Summary is the same as #837744 but I was not doing the action
  described in that report.

  I had selected several nodes and was using shift+down to move them
  when the crash happened.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: inkscape 0.48.4-0.1ubuntu2
  ProcVersionSignature: Ubuntu 3.8.0-14.24-generic 3.8.4
  Uname: Linux 3.8.0-14-generic x86_64
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  Date: Tue Apr  2 23:54:06 2013
  ExecutablePath: /usr/bin/inkscape
  InstallationDate: Installed on 2013-03-28 (4 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130326)
  MarkForUpload: True
  ProcCmdline: inkscape /home/username/hand.svg
  ProcEnviron:
   LANGUAGE=en_NZ:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_NZ.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x6a8467 
_ZN8Inkscape11Preferences8_getNodeERKN4Glib7ustringEb+71:   mov(%rdi),%rax
   PC (0x006a8467) ok
   source (%rdi) (0x006e) not located in a known VMA region (needed 
readable region)!
   destination %rax ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: inkscape
  StacktraceTop:
   ?? ()
   sp_action_set_name(SPAction*, Glib::ustring) ()
   Inkscape::Verb::name(SPDocument*, Glib::ustring) ()
   Inkscape::EventLog::updateUndoVerbs() ()
   Inkscape::EventLog::notifyUndoCommitEvent(Inkscape::Event*) ()
  Title: inkscape crashed with SIGSEGV in sp_action_set_name()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/inkscape/+bug/1163241/+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 1222524] Re: inkscape crashed with SIGSEGV in IA__gtk_widget_set_sensitive()

[Kris]

Quite probably the underlying issue is the same as in bug #1219264. 
Unfortunately also no extra info here, that helps in checking on how to provoke 
the issue and see if it is fixed.
Hence, I propose to mark it is duplicate of bug #1219264.

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

Title:
  inkscape crashed with SIGSEGV in IA__gtk_widget_set_sensitive()

Status in Inkscape: A Vector Drawing Tool:
  New
Status in “inkscape” package in Ubuntu:
  New

Bug description:
  draw poligon

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: inkscape 0.48.4-1ubuntu3
  ProcVersionSignature: Ubuntu 3.11.0-5.11-generic 3.11.0
  Uname: Linux 3.11.0-5-generic x86_64
  ApportVersion: 2.12.1-0ubuntu3
  Architecture: amd64
  Date: Sun Sep  8 23:05:39 2013
  ExecutablePath: /usr/bin/inkscape
  InstallationDate: Installed on 2013-09-08 (0 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130908)
  MarkForUpload: True
  ProcCmdline: inkscape
  SegvAnalysis:
   Segfault happened at: 0x7faf1d16fb8d gtk_widget_set_sensitive+29:  cmp
%rax,(%rdx)
   PC (0x7faf1d16fb8d) ok
   source %rax ok
   destination (%rdx) (0x) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: inkscape
  StacktraceTop:
   gtk_widget_set_sensitive () from 
/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
   Inkscape::UI::Dialogs::colorItemHandleButtonPress(_GtkWidget*, 
_GdkEventButton*, void*) ()
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: inkscape crashed with SIGSEGV in gtk_widget_set_sensitive()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/inkscape/+bug/1222524/+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 960586] Re: inkscape crashed with signal 7

[Kris]

*** This bug is a duplicate of bug 1172484 ***
https://bugs.launchpad.net/bugs/1172484

Based on the backtrace it is the same issue as tracked in Bug #1172484 .
Please comment and revert bug status if you disagree.

** This bug has been marked a duplicate of bug 1172484
   inkscape crashed with SIGSEGV in sp_ui_menu_item_set_name()

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

Title:
  inkscape crashed with signal 7

Status in Inkscape: A Vector Drawing Tool:
  New
Status in “inkscape” package in Ubuntu:
  New

Bug description:
  inkscape crashed as I tried to change the color of a vector

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: inkscape 0.48.3.1-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-19.30-generic 3.2.11
  Uname: Linux 3.2.0-19-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.94.1-0ubuntu2
  Architecture: amd64
  Date: Tue Mar 20 21:14:34 2012
  ExecutablePath: /usr/bin/inkscape
  ProcCmdline: inkscape /home/username/Dokumente/PRÜFUNG\ Mathe\ 
!!!/Arbeitsblätter/Material/Arbeitsblatt\ 1\ -\ Achsen-\ und\ Drehsymmetrie\ -\ 
leicht.svg
  Signal: 7
  SourcePackage: inkscape
  Stacktrace:
   #0  0x0067dddf in ?? ()
   No symbol table info available.
   Cannot access memory at address 0x7fffbd75e558
  StacktraceTop: ?? ()
  ThreadStacktrace:
   .
   Thread 3 (LWP 4509):
   #0  0x7fed898b6d93 in ?? ()
   No symbol table info available.
   .
  Title: inkscape crashed with signal 7
  UpgradeStatus: Upgraded to precise on 2012-03-13 (7 days ago)
  UserGroups: admin

To manage notifications about this bug go to:
https://bugs.launchpad.net/inkscape/+bug/960586/+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 1047374] Re: inkscape crashed with SIGSEGV in g_type_create_instance()

[Kris]

Closing report because it does not give the required information to
track the bug. If there is still an issue, it is better to open a new
report.

** Changed in: inkscape
   Status: Confirmed = Invalid

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

Title:
  inkscape crashed with SIGSEGV in g_type_create_instance()

Status in Inkscape: A Vector Drawing Tool:
  Invalid
Status in “inkscape” package in Ubuntu:
  Invalid

Bug description:
  Reported on IRC by archannes as follows.  Recreated by me on Ubuntu
  12.10.

  Archlinux
  Linux blackbox 3.5.3-1-ARCH #1 SMP PREEMPT Sun Aug 26 08:15:06 UTC 2012 
i686 GNU/Linux
   
  Inkscape: 0.48.3.1 r9886
  pango: 1.30.1-1
   
  Following steps to reproduce:
  1) open inkscape
  2) In Menu, select: Text  Text and fonts..
   
  The dialog window is shown, at the same time the error message appears, 
saying that inkscape will close now.
   
  lead to:
   
  **
  ERROR:libnrtype/FontFactory.cpp:387:Glib::ustring 
font_factory::ConstructFontSpecification(font_instance*): assertion failed: 
(font)
   
  Emergency save activated!
  Emergency save completed. Inkscape will close now.
  If you can reproduce this crash, please file a bug at www.inkscape.org
  with a detailed description of the steps leading to the crash, so we can 
fix it.
  Abgebrochen

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: inkscape 0.48.3.1-1ubuntu4
  ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3
  Uname: Linux 3.5.0-13-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.5.1-0ubuntu7
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Sep  7 08:34:35 2012
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/inkscape
  InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100429)
  ProcCmdline: inkscape
  ProcEnviron:
   TERM=xterm
   SHELL=/bin/bash
   PATH=(custom, user)
   LANG=en_US.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7fe2f8b86c23:mov0x18(%rax),%r9
   PC (0x7fe2f8b86c23) ok
   source 0x18(%rax) (0x0018) not located in a known VMA region (needed 
readable region)!
   destination %r9 ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: inkscape
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/gtk-2.0/modules/liboverlay-scrollbar.so
   ?? () from /usr/lib/x86_64-linux-gnu/gtk-2.0/modules/liboverlay-scrollbar.so
   g_type_create_instance (type=optimized out) at 
/build/buildd/glib2.0-2.33.12/./gobject/gtype.c:1890
   g_object_constructor (type=optimized out, n_construct_properties=0, 
construct_params=0x0) at /build/buildd/glib2.0-2.33.12/./gobject/gobject.c:1854
   g_object_newv (object_type=object_type@entry=120711056, 
n_parameters=n_parameters@entry=0, parameters=parameters@entry=0x0) at 
/build/buildd/glib2.0-2.33.12/./gobject/gobject.c:1637
  Title: inkscape crashed with SIGSEGV in g_type_create_instance()
  UpgradeStatus: Upgraded to quantal on 2012-01-10 (240 days ago)
  UserGroups: adm admin audio cdrom dialout dip fax floppy fuse libvirtd 
lpadmin netdev plugdev sambashare tape video

To manage notifications about this bug go to:
https://bugs.launchpad.net/inkscape/+bug/1047374/+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 1261918] Re: /usr/bin/inkscape:11:file_save:sp_file_save_dialog:sp_action_perform:g_closure_invoke:signal_emit_unlocked_R

[Kris]

*** This bug is a duplicate of bug 967416 ***
https://bugs.launchpad.net/bugs/967416

** This bug has been marked a duplicate of bug 967416
   inkscape crashed with SIGSEGV in file_save()

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

Title:
  
/usr/bin/inkscape:11:file_save:sp_file_save_dialog:sp_action_perform:g_closure_invoke:signal_emit_unlocked_R

Status in “inkscape” package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding inkscape.  This problem was most recently seen with version
  0.48.4-1ubuntu3, the problem page at
  https://errors.ubuntu.com/problem/ec8613a3dfc65dbfe6ecfbf1522e031699f5c453
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/1261918/+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 837744] Re: inkscape crashed with SIGSEGV in sp_action_set_name()

[Kris]

The document being worked on when the crash occurred does not give me a clue.
With the limited amount of information available, I propose to mark this bug as 
a duplicate of bug 816540 (cfr comment 5).

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

Title:
  inkscape crashed with SIGSEGV in sp_action_set_name()

Status in Inkscape: A Vector Drawing Tool:
  New
Status in “inkscape” package in Ubuntu:
  Expired

Bug description:
  was saving a pdf

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: inkscape 0.48.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-9.14-generic 3.0.3
  Uname: Linux 3.0.0-9-generic i686
  NonfreeKernelModules: fglrx
  Architecture: i386
  CrashCounter: 1
  Date: Tue Aug 30 18:30:44 2011
  ExecutablePath: /usr/bin/inkscape
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1)
  ProcCmdline: inkscape
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/usr/bin/tcsh
  SegvAnalysis:
   Segfault happened at: 0x8290afa: mov(%ebx),%esi
   PC (0x08290afa) ok
   source (%ebx) (0x) not located in a known VMA region (needed 
readable region)!
   destination %esi ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: inkscape
  StacktraceTop:
   ?? ()
   sp_action_set_name(SPAction*, Glib::ustring) ()
   Inkscape::Verb::name(SPDocument*, Glib::ustring) ()
   Inkscape::EventLog::updateUndoVerbs() ()
   Inkscape::CompositeUndoStackObserver::notifyClearUndoEvent() ()
  Title: inkscape crashed with SIGSEGV in sp_action_set_name()
  UpgradeStatus: Upgraded to oneiric on 2011-08-30 (0 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

To manage notifications about this bug go to:
https://bugs.launchpad.net/inkscape/+bug/837744/+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 1163241] Re: inkscape crashed with SIGSEGV in Inkscape::Preferences::_getNode()

[Kris]

** Changed in: inkscape
Milestone: None = 0.91

** Changed in: inkscape
   Status: New = Triaged

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

Title:
  inkscape crashed with SIGSEGV in Inkscape::Preferences::_getNode()

Status in Inkscape: A Vector Drawing Tool:
  Triaged
Status in “inkscape” package in Ubuntu:
  Confirmed

Bug description:
  Summary is the same as #837744 but I was not doing the action
  described in that report.

  I had selected several nodes and was using shift+down to move them
  when the crash happened.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: inkscape 0.48.4-0.1ubuntu2
  ProcVersionSignature: Ubuntu 3.8.0-14.24-generic 3.8.4
  Uname: Linux 3.8.0-14-generic x86_64
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  Date: Tue Apr  2 23:54:06 2013
  ExecutablePath: /usr/bin/inkscape
  InstallationDate: Installed on 2013-03-28 (4 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130326)
  MarkForUpload: True
  ProcCmdline: inkscape /home/username/hand.svg
  ProcEnviron:
   LANGUAGE=en_NZ:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_NZ.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x6a8467 
_ZN8Inkscape11Preferences8_getNodeERKN4Glib7ustringEb+71:   mov(%rdi),%rax
   PC (0x006a8467) ok
   source (%rdi) (0x006e) not located in a known VMA region (needed 
readable region)!
   destination %rax ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: inkscape
  StacktraceTop:
   ?? ()
   sp_action_set_name(SPAction*, Glib::ustring) ()
   Inkscape::Verb::name(SPDocument*, Glib::ustring) ()
   Inkscape::EventLog::updateUndoVerbs() ()
   Inkscape::EventLog::notifyUndoCommitEvent(Inkscape::Event*) ()
  Title: inkscape crashed with SIGSEGV in sp_action_set_name()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/inkscape/+bug/1163241/+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 1163241] Re: inkscape crashed with SIGSEGV in Inkscape::Preferences::_getNode()

[Kris]

No information available to help provoke this bug, nor to check whether it is 
fixed ...
The added null check in this patch should prevent this crash though.

** Patch added: 1163241.patch
   
https://bugs.launchpad.net/inkscape/+bug/1163241/+attachment/3938358/+files/1163241.patch

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

Title:
  inkscape crashed with SIGSEGV in Inkscape::Preferences::_getNode()

Status in Inkscape: A Vector Drawing Tool:
  Triaged
Status in “inkscape” package in Ubuntu:
  Confirmed

Bug description:
  Summary is the same as #837744 but I was not doing the action
  described in that report.

  I had selected several nodes and was using shift+down to move them
  when the crash happened.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: inkscape 0.48.4-0.1ubuntu2
  ProcVersionSignature: Ubuntu 3.8.0-14.24-generic 3.8.4
  Uname: Linux 3.8.0-14-generic x86_64
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  Date: Tue Apr  2 23:54:06 2013
  ExecutablePath: /usr/bin/inkscape
  InstallationDate: Installed on 2013-03-28 (4 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130326)
  MarkForUpload: True
  ProcCmdline: inkscape /home/username/hand.svg
  ProcEnviron:
   LANGUAGE=en_NZ:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_NZ.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x6a8467 
_ZN8Inkscape11Preferences8_getNodeERKN4Glib7ustringEb+71:   mov(%rdi),%rax
   PC (0x006a8467) ok
   source (%rdi) (0x006e) not located in a known VMA region (needed 
readable region)!
   destination %rax ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: inkscape
  StacktraceTop:
   ?? ()
   sp_action_set_name(SPAction*, Glib::ustring) ()
   Inkscape::Verb::name(SPDocument*, Glib::ustring) ()
   Inkscape::EventLog::updateUndoVerbs() ()
   Inkscape::EventLog::notifyUndoCommitEvent(Inkscape::Event*) ()
  Title: inkscape crashed with SIGSEGV in sp_action_set_name()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/inkscape/+bug/1163241/+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 871110] Re: inkscape crashed with SIGABRT in __kernel_vsyscall()

[Kris]

*** This bug is a duplicate of bug 496793 ***
https://bugs.launchpad.net/bugs/496793

Based on backtrace marking as duplicate of bug #496793.
Please comment and revert duplicate status if you disagree.

** This bug has been marked a duplicate of bug 496793
   ctrl c ctrl v of text in edit mode crashes inkscape

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

Title:
  inkscape crashed with SIGABRT in __kernel_vsyscall()

Status in Inkscape: A Vector Drawing Tool:
  Incomplete
Status in “inkscape” package in Ubuntu:
  New

Bug description:
  The crash happened when I was in the middle of editing a layer.

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: inkscape 0.48.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu2
  Architecture: i386
  Date: Sat Oct  8 20:45:21 2011
  ExecutablePath: /usr/bin/inkscape
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1)
  ProcCmdline: inkscape
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: inkscape
  StacktraceTop:
   __kernel_vsyscall ()
   raise () from /lib/i386-linux-gnu/libc.so.6
   abort () from /lib/i386-linux-gnu/libc.so.6
   g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/i386-linux-gnu/libglib-2.0.so.0
  Title: inkscape crashed with SIGABRT in __kernel_vsyscall()
  UpgradeStatus: Upgraded to oneiric on 2011-09-10 (28 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

To manage notifications about this bug go to:
https://bugs.launchpad.net/inkscape/+bug/871110/+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 1261918] Re: /usr/bin/inkscape:11:file_save:sp_file_save_dialog:sp_action_perform:g_closure_invoke:signal_emit_unlocked_R

[Kris]

Based on the function names in the bug title and the backtrace in bug
967416, it seems to be the same issue as already reported in bug 967416.

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

Title:
  
/usr/bin/inkscape:11:file_save:sp_file_save_dialog:sp_action_perform:g_closure_invoke:signal_emit_unlocked_R

Status in “inkscape” package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding inkscape.  This problem was most recently seen with version
  0.48.4-1ubuntu3, the problem page at
  https://errors.ubuntu.com/problem/ec8613a3dfc65dbfe6ecfbf1522e031699f5c453
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/1261918/+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 1216167] Re: inkscape crashed with SIGSEGV in pathv_to_linear_and_cubic_beziers()

[Kris]

** Changed in: inkscape
   Importance: Undecided = High

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

Title:
  inkscape crashed with SIGSEGV in pathv_to_linear_and_cubic_beziers()

Status in Inkscape: A Vector Drawing Tool:
  New
Status in “inkscape” package in Ubuntu:
  New

Bug description:
  :(

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: inkscape 0.48.4-1ubuntu3
  ProcVersionSignature: Ubuntu 3.11.0-3.6-generic 3.11.0-rc6
  Uname: Linux 3.11.0-3-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.12.1-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  Date: Sat Aug 24 02:53:35 2013
  ExecutablePath: /usr/bin/inkscape
  InstallationDate: Installed on 2013-07-27 (27 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MarkForUpload: True
  ProcCmdline: inkscape
  SegvAnalysis:
   Segfault happened at: 0x7c47ed 
_Z33pathv_to_linear_and_cubic_beziersRKSt6vectorIN4Geom4PathESaIS1_EE+45:   
mov(%rsi),%rdi
   PC (0x007c47ed) ok
   source (%rsi) (0x0010) not located in a known VMA region (needed 
readable region)!
   destination %rdi ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: inkscape
  StacktraceTop:
   pathv_to_linear_and_cubic_beziers(std::vectorGeom::Path, 
std::allocatorGeom::Path  const) ()
   Inkscape::UI::PathManipulator::_createControlPointsFromGeometry() ()
   Inkscape::UI::PathManipulator::_externalChange(unsigned int) ()
   
Inkscape::XML::CompositeNodeObserver::notifyAttributeChanged(Inkscape::XML::Node,
 unsigned int, Inkscape::Util::ptr_sharedchar, 
Inkscape::Util::ptr_sharedchar) ()
   Inkscape::XML::SimpleNode::setAttribute(char const*, char const*, bool) ()
  Title: inkscape crashed with SIGSEGV in pathv_to_linear_and_cubic_beziers()
  UpgradeStatus: Upgraded to saucy on 2013-08-04 (19 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/inkscape/+bug/1216167/+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 837744] Re: inkscape crashed with SIGSEGV in sp_action_set_name()

[Kris]

Based on the stacktrace, it might be the same or a related to the issue
of bug 1172484

** Changed in: inkscape
   Status: Invalid = New

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

Title:
  inkscape crashed with SIGSEGV in sp_action_set_name()

Status in Inkscape: A Vector Drawing Tool:
  New
Status in “inkscape” package in Ubuntu:
  Expired

Bug description:
  was saving a pdf

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: inkscape 0.48.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-9.14-generic 3.0.3
  Uname: Linux 3.0.0-9-generic i686
  NonfreeKernelModules: fglrx
  Architecture: i386
  CrashCounter: 1
  Date: Tue Aug 30 18:30:44 2011
  ExecutablePath: /usr/bin/inkscape
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1)
  ProcCmdline: inkscape
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/usr/bin/tcsh
  SegvAnalysis:
   Segfault happened at: 0x8290afa: mov(%ebx),%esi
   PC (0x08290afa) ok
   source (%ebx) (0x) not located in a known VMA region (needed 
readable region)!
   destination %esi ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: inkscape
  StacktraceTop:
   ?? ()
   sp_action_set_name(SPAction*, Glib::ustring) ()
   Inkscape::Verb::name(SPDocument*, Glib::ustring) ()
   Inkscape::EventLog::updateUndoVerbs() ()
   Inkscape::CompositeUndoStackObserver::notifyClearUndoEvent() ()
  Title: inkscape crashed with SIGSEGV in sp_action_set_name()
  UpgradeStatus: Upgraded to oneiric on 2011-08-30 (0 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

To manage notifications about this bug go to:
https://bugs.launchpad.net/inkscape/+bug/837744/+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 1163241] Re: inkscape crashed with SIGSEGV in Inkscape::Preferences::_getNode()

[Kris]

** Changed in: inkscape
   Importance: Undecided = High

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

Title:
  inkscape crashed with SIGSEGV in Inkscape::Preferences::_getNode()

Status in Inkscape: A Vector Drawing Tool:
  New
Status in “inkscape” package in Ubuntu:
  Confirmed

Bug description:
  Summary is the same as #837744 but I was not doing the action
  described in that report.

  I had selected several nodes and was using shift+down to move them
  when the crash happened.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: inkscape 0.48.4-0.1ubuntu2
  ProcVersionSignature: Ubuntu 3.8.0-14.24-generic 3.8.4
  Uname: Linux 3.8.0-14-generic x86_64
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  Date: Tue Apr  2 23:54:06 2013
  ExecutablePath: /usr/bin/inkscape
  InstallationDate: Installed on 2013-03-28 (4 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130326)
  MarkForUpload: True
  ProcCmdline: inkscape /home/username/hand.svg
  ProcEnviron:
   LANGUAGE=en_NZ:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_NZ.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x6a8467 
_ZN8Inkscape11Preferences8_getNodeERKN4Glib7ustringEb+71:   mov(%rdi),%rax
   PC (0x006a8467) ok
   source (%rdi) (0x006e) not located in a known VMA region (needed 
readable region)!
   destination %rax ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: inkscape
  StacktraceTop:
   ?? ()
   sp_action_set_name(SPAction*, Glib::ustring) ()
   Inkscape::Verb::name(SPDocument*, Glib::ustring) ()
   Inkscape::EventLog::updateUndoVerbs() ()
   Inkscape::EventLog::notifyUndoCommitEvent(Inkscape::Event*) ()
  Title: inkscape crashed with SIGSEGV in sp_action_set_name()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/inkscape/+bug/1163241/+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 837744] Re: inkscape crashed with SIGSEGV in sp_action_set_name()

[Kris]

Also related Bug 816540

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

Title:
  inkscape crashed with SIGSEGV in sp_action_set_name()

Status in Inkscape: A Vector Drawing Tool:
  New
Status in “inkscape” package in Ubuntu:
  Expired

Bug description:
  was saving a pdf

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: inkscape 0.48.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-9.14-generic 3.0.3
  Uname: Linux 3.0.0-9-generic i686
  NonfreeKernelModules: fglrx
  Architecture: i386
  CrashCounter: 1
  Date: Tue Aug 30 18:30:44 2011
  ExecutablePath: /usr/bin/inkscape
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1)
  ProcCmdline: inkscape
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/usr/bin/tcsh
  SegvAnalysis:
   Segfault happened at: 0x8290afa: mov(%ebx),%esi
   PC (0x08290afa) ok
   source (%ebx) (0x) not located in a known VMA region (needed 
readable region)!
   destination %esi ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: inkscape
  StacktraceTop:
   ?? ()
   sp_action_set_name(SPAction*, Glib::ustring) ()
   Inkscape::Verb::name(SPDocument*, Glib::ustring) ()
   Inkscape::EventLog::updateUndoVerbs() ()
   Inkscape::CompositeUndoStackObserver::notifyClearUndoEvent() ()
  Title: inkscape crashed with SIGSEGV in sp_action_set_name()
  UpgradeStatus: Upgraded to oneiric on 2011-08-30 (0 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

To manage notifications about this bug go to:
https://bugs.launchpad.net/inkscape/+bug/837744/+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 1219264] Re: inkscape crashed with SIGSEGV in g_type_check_instance_cast()

[Kris]

Should be fixed upstream in trunk with revision 12851 and/or 12838.

** Changed in: inkscape
   Status: New = Fix Committed

** Changed in: inkscape
 Assignee: (unassigned) = Kris (kris-degussem)

** Changed in: inkscape
Milestone: None = 0.91

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

Title:
  inkscape crashed with SIGSEGV in g_type_check_instance_cast()

Status in Inkscape: A Vector Drawing Tool:
  Fix Committed
Status in “inkscape” package in Ubuntu:
  Confirmed

Bug description:
  Just crash

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: inkscape 0.48.4-1ubuntu3
  ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
  Uname: Linux 3.11.0-4-generic x86_64
  ApportVersion: 2.12.1-0ubuntu3
  Architecture: amd64
  Date: Sat Aug 31 13:49:09 2013
  ExecutablePath: /usr/bin/inkscape
  InstallationDate: Installed on 2013-08-01 (29 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130801)
  MarkForUpload: True
  ProcCmdline: inkscape
  SegvAnalysis:
   Segfault happened at: 0x7f987ccff26c g_type_check_instance_cast+28:
mov(%rax),%rdi
   PC (0x7f987ccff26c) ok
   source (%rax) (0x) not located in a known VMA region 
(needed readable region)!
   destination %rdi ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: inkscape
  StacktraceTop:
   g_type_check_instance_cast () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   Inkscape::UI::Dialogs::colorItemHandleButtonPress(_GtkWidget*, 
_GdkEventButton*, void*) ()
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: inkscape crashed with SIGSEGV in g_type_check_instance_cast()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio bluetooth cdrom clamav daemon dip firebird fuse libuuid 
lp lpadmin plugdev pulse sambashare ssh sudo tty uml-net users utempter utmp 
uucp vboxusers video voice www-data

To manage notifications about this bug go to:
https://bugs.launchpad.net/inkscape/+bug/1219264/+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 1172484] Re: inkscape crashed with SIGSEGV in sp_ui_menu_item_set_name()

[Kris]

Fix (in reply 5) committed upstream in inkscape trunk r12853.

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

Title:
  inkscape crashed with SIGSEGV in sp_ui_menu_item_set_name()

Status in Inkscape: A Vector Drawing Tool:
  New
Status in “inkscape” package in Ubuntu:
  New

Bug description:
  No idea what caused the crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: inkscape 0.48.4-0.1ubuntu2
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Wed Apr 24 14:19:16 2013
  ExecutablePath: /usr/bin/inkscape
  InstallationDate: Installed on 2010-09-24 (943 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release amd64 
(20100816.1)
  MarkForUpload: True
  ProcCmdline: inkscape
  SegvAnalysis:
   Segfault happened at: 0x69e537:  cmp0x0(%rbp),%rax
   PC (0x0069e537) ok
   source 0x0(%rbp) (0x0001) not located in a known VMA region (needed 
readable region)!
   destination %rax ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: inkscape
  StacktraceTop:
   ?? ()
   sp_action_set_name(SPAction*, Glib::ustring) ()
   Inkscape::Verb::name(SPDocument*, Glib::ustring) ()
   Inkscape::EventLog::updateUndoVerbs() ()
   Inkscape::EventLog::notifyUndoCommitEvent(Inkscape::Event*) ()
  Title: inkscape crashed with SIGSEGV in sp_action_set_name()
  UpgradeStatus: Upgraded to raring on 2013-01-25 (89 days ago)
  UserGroups: adm admin cdrom dialout libvirtd lpadmin mythtv plugdev 
sambashare src sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/inkscape/+bug/1172484/+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 1172484] Re: inkscape crashed with SIGSEGV in sp_ui_menu_item_set_name()

[Kris]

(bug could also have been fixed previously upstream in trunk r10589)

** Changed in: inkscape
   Status: New = Fix Committed

** Changed in: inkscape
Milestone: None = 0.91

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

Title:
  inkscape crashed with SIGSEGV in sp_ui_menu_item_set_name()

Status in Inkscape: A Vector Drawing Tool:
  Fix Committed
Status in “inkscape” package in Ubuntu:
  New

Bug description:
  No idea what caused the crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: inkscape 0.48.4-0.1ubuntu2
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Wed Apr 24 14:19:16 2013
  ExecutablePath: /usr/bin/inkscape
  InstallationDate: Installed on 2010-09-24 (943 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release amd64 
(20100816.1)
  MarkForUpload: True
  ProcCmdline: inkscape
  SegvAnalysis:
   Segfault happened at: 0x69e537:  cmp0x0(%rbp),%rax
   PC (0x0069e537) ok
   source 0x0(%rbp) (0x0001) not located in a known VMA region (needed 
readable region)!
   destination %rax ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: inkscape
  StacktraceTop:
   ?? ()
   sp_action_set_name(SPAction*, Glib::ustring) ()
   Inkscape::Verb::name(SPDocument*, Glib::ustring) ()
   Inkscape::EventLog::updateUndoVerbs() ()
   Inkscape::EventLog::notifyUndoCommitEvent(Inkscape::Event*) ()
  Title: inkscape crashed with SIGSEGV in sp_action_set_name()
  UpgradeStatus: Upgraded to raring on 2013-01-25 (89 days ago)
  UserGroups: adm admin cdrom dialout libvirtd lpadmin mythtv plugdev 
sambashare src sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/inkscape/+bug/1172484/+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 1222524] Re: inkscape crashed with SIGSEGV in IA__gtk_widget_set_sensitive()

[Kris]

** Changed in: inkscape
   Importance: Undecided = High

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

Title:
  inkscape crashed with SIGSEGV in IA__gtk_widget_set_sensitive()

Status in Inkscape: A Vector Drawing Tool:
  New
Status in “inkscape” package in Ubuntu:
  New

Bug description:
  draw poligon

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: inkscape 0.48.4-1ubuntu3
  ProcVersionSignature: Ubuntu 3.11.0-5.11-generic 3.11.0
  Uname: Linux 3.11.0-5-generic x86_64
  ApportVersion: 2.12.1-0ubuntu3
  Architecture: amd64
  Date: Sun Sep  8 23:05:39 2013
  ExecutablePath: /usr/bin/inkscape
  InstallationDate: Installed on 2013-09-08 (0 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130908)
  MarkForUpload: True
  ProcCmdline: inkscape
  SegvAnalysis:
   Segfault happened at: 0x7faf1d16fb8d gtk_widget_set_sensitive+29:  cmp
%rax,(%rdx)
   PC (0x7faf1d16fb8d) ok
   source %rax ok
   destination (%rdx) (0x) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: inkscape
  StacktraceTop:
   gtk_widget_set_sensitive () from 
/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
   Inkscape::UI::Dialogs::colorItemHandleButtonPress(_GtkWidget*, 
_GdkEventButton*, void*) ()
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: inkscape crashed with SIGSEGV in gtk_widget_set_sensitive()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/inkscape/+bug/1222524/+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 966441] Re: inkscape crashed with SIGSEGV in sp_dtw_color_profile_event()

[Kris]

** Tags removed: backport-proposed

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

Title:
  inkscape crashed with SIGSEGV in sp_dtw_color_profile_event()

Status in Inkscape: A Vector Drawing Tool:
  Fix Committed
Status in “inkscape” package in Ubuntu:
  Confirmed

Bug description:
  inkscape had some documents open over nautilus's ssh mount. i was not
  doing anythin at the time.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: inkscape 0.48.3.1-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12
  Uname: Linux 3.2.0-20-generic x86_64
  ApportVersion: 1.95-0ubuntu1
  Architecture: amd64
  Date: Tue Mar 27 18:50:23 2012
  ExecutablePath: /usr/bin/inkscape
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 
(20120108)
  ProcCmdline: inkscape
  ProcEnviron:
   LANGUAGE=en_GB:en
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: inkscape
  Title: inkscape crashed with SIGSEGV in g_signal_emit_valist()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/inkscape/+bug/966441/+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 166371] Re: Illustrator CS SVG won't load: namespace URIs in entities

[Kris]

** Tags removed: backport-proposed

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

Title:
  Illustrator CS SVG won't load: namespace URIs in entities

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

Bug description:
  Opening an SVG exported from Illustrator CS on Windows
  XP crashes Inkscape on Windows XP with the message:

  inkscape.exe:2296: Warning **: SVGView: error loading
  document

To manage notifications about this bug go to:
https://bugs.launchpad.net/inkscape/+bug/166371/+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 145400] Re: gedit consumes 100% processor with paragraphs 10 lines.

[Kris]

This bug is still present in ubuntu 13.10 (gedit version 3.8.3).

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

Title:
  gedit consumes 100% processor with paragraphs  10 lines.

Status in Light-Weight Text Editor for Gnome:
  Confirmed
Status in “gedit” package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: gedit

  There is a problem with gedit (or maybe even the gtksourcebuffer
  widget) when editing long lines with syntax highlighting.

  Ive seen bug #134352, and it seems to be similar to what I am
  reporting here, but I am creating a new bug report since in the
  original report the problem seems to be minor since only long one-
  liner html files seem to be the issue.

  However, this bug appears even when doing a short document (for
  example your homework) on Latex, and writing a small paragraph (less
  than 10 lines) without using line breaks.

  To reproduce, create a new latex file and open it in gedit, make sure
  gedit correctly detects it as latex file and it is doing syntax
  highlighting on it. Now start typing gibberish (ie. asdf asdf asdf
  asdf asdfasdf asdf), as your paragraph continues and the buffer starts
  to break your line into several lines, you will notice how the
  processor consumption will start going up, by the time you reach 10
  break lines or so (at least on my machine) the processor will reach
  100% usage.

  I think this bug is pretty serious, since having a 10line paragraph
  seems a pretty common use case for a text editor.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gedit/+bug/145400/+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 1172484] Re: inkscape crashed with SIGSEGV in sp_ui_menu_item_set_name()

[Kris]

No information to help provoking the bug, so no possibility to test.
Probably this patch might solve the issue ...

** Patch added: 1172484.patch
   
https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/1172484/+attachment/3897505/+files/1172484.patch

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

Title:
  inkscape crashed with SIGSEGV in sp_ui_menu_item_set_name()

Status in Inkscape: A Vector Drawing Tool:
  New
Status in “inkscape” package in Ubuntu:
  New

Bug description:
  No idea what caused the crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: inkscape 0.48.4-0.1ubuntu2
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Wed Apr 24 14:19:16 2013
  ExecutablePath: /usr/bin/inkscape
  InstallationDate: Installed on 2010-09-24 (943 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release amd64 
(20100816.1)
  MarkForUpload: True
  ProcCmdline: inkscape
  SegvAnalysis:
   Segfault happened at: 0x69e537:  cmp0x0(%rbp),%rax
   PC (0x0069e537) ok
   source 0x0(%rbp) (0x0001) not located in a known VMA region (needed 
readable region)!
   destination %rax ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: inkscape
  StacktraceTop:
   ?? ()
   sp_action_set_name(SPAction*, Glib::ustring) ()
   Inkscape::Verb::name(SPDocument*, Glib::ustring) ()
   Inkscape::EventLog::updateUndoVerbs() ()
   Inkscape::EventLog::notifyUndoCommitEvent(Inkscape::Event*) ()
  Title: inkscape crashed with SIGSEGV in sp_action_set_name()
  UpgradeStatus: Upgraded to raring on 2013-01-25 (89 days ago)
  UserGroups: adm admin cdrom dialout libvirtd lpadmin mythtv plugdev 
sambashare src sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/inkscape/+bug/1172484/+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 1244338] Re: External tool won't run if Save is set to All documents

[Kris]

I experience the same behavior as described above. I've also noticed
that when the external tool is set to save Current document, it
doesn't actually save the current document upon being run.

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

Title:
  External tool won't run if Save is set to All documents

Status in “gedit” package in Ubuntu:
  Confirmed

Bug description:
  Since upgrading to Ubuntu 13.10/gedit 3.8.3 external tools won't be
  run if the Save option is set to All documents. If the setting it
  to None or Current documents then the tool will run again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1244338/+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 785701] Re: Inkscape freezes at opening

[Kris]

based on comment 16, commit 12263 does not seem to help. (@Steve: you've
checked with a good Inscape version)

** Changed in: inkscape
 Assignee: Kris (kris-degussem) = (unassigned)

** Changed in: inkscape
Milestone: 0.49 = None

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

Title:
  Inkscape freezes at opening

Status in Inkscape: A Vector Drawing Tool:
  Triaged
Status in “inkscape” package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: inkscape

  I use Ubuntu 11.04 classic. Very often Inkscape freezes at opening, even if 
empty. We have the same problem in Ubuntu 10.04. Since I hadn't noticed it up 
to recently (1 month or so) it's possible that it is due to a modification in 
another package than Inkscape, for instance a library. But Im' not an intensive 
user of Inkscape.
  Steps to reproduce the problem: choose in the general menu Applications → 
Graphics → Inskape Vector Graphics Editor.
  What happens: Inkscape is launched but, often clicking any button has no 
effect, resizing the window doesn't resize the inside. After a while, 
Inkscape's window is greyished and, if I close it, I first get a The window 
'New document 1 - Inkscape' is not responding. message. Relaunching Inkscape 
never solves the issue. Login out and in sometimes solves it, sometimes not.
  What is expected to happen: that Inkscape respond to clicks.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: inkscape 0.48.1-2ubuntu2
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Fri May 20 19:02:33 2011
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, user)
   LANG=fr_FR.utf8
   LC_MESSAGES=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: inkscape
  UpgradeStatus: Upgraded to natty on 2011-05-01 (19 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/inkscape/+bug/785701/+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 474956] Re: odg export still doesn't work

[Kris]

** Changed in: inkscape
   Status: In Progress = Triaged

** Changed in: inkscape
 Assignee: Kris (kris-degussem) = (unassigned)

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

Title:
  odg export still doesn't work

Status in Inkscape: A Vector Drawing Tool:
  Triaged
Status in “inkscape” package in Ubuntu:
  Triaged
Status in “inkscape” package in Debian:
  Confirmed

Bug description:
  I'm filing a fresh report since the search turned up stuff from 2007.  I'm 
reporting the version of OOO Draw as 3.1.1, and Inkscape is 0.47.
  A binary tree drawing, exported to ODG, has several problems:
 - of the 7 circles in the picture, only one shows.  This could be a 
problem with clones?  Only the original shows and all the copies are missing.
 - the circle that is drawn has the wrong outline (stroke) width
 - the lines I drew are also the wrong stroke width
 - the lines are missing the arrow heads or other start/end markers

  and less critical, it didn't set the page size and drawing position.

  It seems that the SVG importer into Draw isn't working well either.
  It worked better on a slightly older version of Inkscape, so I wonder
  if there are changes in the way it writes things.

To manage notifications about this bug go to:
https://bugs.launchpad.net/inkscape/+bug/474956/+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 474956] Re: odg export still doesn't work

[Kris]

Some more work done on the gradients  in trunk r12286, which does not
lead to correct showing a drawing with gradients (C++-code is improved,
but still something is interfering with correct orientation).

Reference to further improve the code: open document format specification
   
https://www.oasis-open.org/committees/download.php/20847/OpenDocument-v1.1-cs1.pdf

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

Title:
  odg export still doesn't work

Status in Inkscape: A Vector Drawing Tool:
  Triaged
Status in “inkscape” package in Ubuntu:
  Triaged
Status in “inkscape” package in Debian:
  Confirmed

Bug description:
  I'm filing a fresh report since the search turned up stuff from 2007.  I'm 
reporting the version of OOO Draw as 3.1.1, and Inkscape is 0.47.
  A binary tree drawing, exported to ODG, has several problems:
 - of the 7 circles in the picture, only one shows.  This could be a 
problem with clones?  Only the original shows and all the copies are missing.
 - the circle that is drawn has the wrong outline (stroke) width
 - the lines I drew are also the wrong stroke width
 - the lines are missing the arrow heads or other start/end markers

  and less critical, it didn't set the page size and drawing position.

  It seems that the SVG importer into Draw isn't working well either.
  It worked better on a slightly older version of Inkscape, so I wonder
  if there are changes in the way it writes things.

To manage notifications about this bug go to:
https://bugs.launchpad.net/inkscape/+bug/474956/+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 1158096] Re: inkscape crashes at start up

[Kris]

Closing bug by lack of user feedback.

** Changed in: inkscape
   Status: Incomplete = Invalid

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

Title:
  inkscape crashes at start up

Status in Inkscape: A Vector Drawing Tool:
  Invalid
Status in “inkscape” package in Ubuntu:
  New

Bug description:
  This is what I got when I try to read a font named 1979 that I just install 
today.
  I have unistalled the font manager, but I will re-install it later.

  Inkscape encountered an internal error and will close now.
  Automatic backups of unsaved documents were done to the following locations:
  /home/gusduenas/New document 1.2013_03_20_22_41_29.0.svg

  the nI ahve to wait for it to finally close and when submitting the
  report this is what I get:

  
  inkscape crashes with Sigsegv in strlen()

  and a bunch of xsession error.

  the graphic are running like pixelated when moves and they are totally
  slow.

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