[Touch-packages] [Bug 1966203] Re: Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit code 1." in Ubuntu 22.04

2023-09-04 Thread Bernhard Riegler
good catch

I renamed the file '66-snapd-autoimport.rules' to 
'OFF.66-snapd-autoimport.rules.OFF'
and rebooted.

root@prod:/lib/udev/rules.d# journalctl -b |grep 'exit code 1'
root@prod:/lib/udev/rules.d# echo $?
1

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1966203

Title:
  Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with
  exit code 1." in Ubuntu 22.04

Status in snapd:
  Confirmed
Status in snapd package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Configuration:
   OS:jammy-live-server20220320-amd64.iso
   CPU:AMD EPYC 7702 64-Core Processor
   UEFI Version:D8E119A
   BMC Version:D8BT19I
   SSD:Intel 1.60TB NVMe SSD
   Boot mode:legacy
  Reproduce Steps:
   1.Boot into BIOS and set boot mode to legacy
   2.install ubuntu 22.04 on NVMe SSD
   3.Check syslog log
  Current behaviors:
  syslog shows systemd-udevd errors in Ubuntu 22.04
  Feb  9 10:16:19 len systemd-udevd[2837]: nvme0n1: Process '/usr/bin/unshare 
-m /usr/bin/snap auto-import --mount=/dev/nvme0n1' failed with exit code 1.
  Feb  9 10:16:19 len systemd-udevd[2877]: nvme0n1p3: Process '/usr/bin/unshare 
-m /usr/bin/snap auto-import --mount=/dev/nvme0n1p3' failed with exit code 1.
  Feb  9 10:16:19 len systemd-udevd[2876]: nvme0n1p2: Process '/usr/bin/unshare 
-m /usr/bin/snap auto-import --mount=/dev/nvme0n1p2' failed with exit code 1.
  Feb  9 10:16:19 len systemd-udevd[2837]: nvme0n1p1: Process '/usr/bin/unshare 
-m /usr/bin/snap auto-import --mount=/dev/nvme0n1p1' failed with exit code 1.
  Feb  9 10:16:19 len systemd-udevd[2828]: sr0: Process '/usr/bin/unshare -m 
/usr/bin/snap auto-import --mount=/dev/sr0' failed with exit code 1.
  Feb  9 10:16:19 len systemd-udevd[2850]: dm-0: Process '/usr/bin/unshare -m 
/usr/bin/snap auto-import --mount=/dev/dm-0' failed with exit code 1.

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1990755] Re: HYPHEN character escaped in filenames with BACKSLASH

2023-07-06 Thread Bernhard Riegler
Hi Nick,

I disagree with this filesystem name space pollution.

UNIX has a SPACE as parameter separator.
UNIX has a SLASH as filesystem directory separator
DOS  has a BACKSLASH as filesystem directory separator

nowadays are directory_names and file_names with SPACES, causing problems
with CLI shell-scripts and BACKUP programs.

adding escaping into filesystem name space is causing more problems.

I have already shell scripts replacing SPACE with UNDERSCORE
and reporting BACKSPACE in filesystem namespace to keep my filesystems pure and 
clean.
I also monitor UNICODE symbols in filesystem name space.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1990755

Title:
  HYPHEN character escaped in filenames with BACKSLASH

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  current Ubuntu 22.04 LTS shows

  oot@prod:~# find / -xdev -name '*\\x*'
  /usr/lib/systemd/system/system-systemd\x2dcryptsetup.slice
  /etc/systemd/system/snap-gtk\x2dcommon\x2dthemes-1535.mount
  /etc/systemd/system/snap-gnome\x2d3\x2d38\x2d2004-115.mount
  
/etc/systemd/system/multi-user.target.wants/snap-gtk\x2dcommon\x2dthemes-1535.mount
  
/etc/systemd/system/multi-user.target.wants/snap-gnome\x2d3\x2d38\x2d2004-115.mount
  
/etc/systemd/system/multi-user.target.wants/snap-snapd\x2ddesktop\x2dintegration-14.mount
  /etc/systemd/system/multi-user.target.wants/snap-snap\x2dstore-592.mount
  
/etc/systemd/system/multi-user.target.wants/var-snap-firefox-common-host\x2dhunspell.mount
  /etc/systemd/system/multi-user.target.wants/snap-snap\x2dstore-599.mount
  /etc/systemd/system/snap-snapd\x2ddesktop\x2dintegration-14.mount
  /etc/systemd/system/snap-snap\x2dstore-592.mount
  /etc/systemd/system/var-snap-firefox-common-host\x2dhunspell.mount
  /etc/systemd/system/snap-snap\x2dstore-599.mount
  
/etc/systemd/system/default.target.wants/snap-gnome\x2d3\x2d38\x2d2004-115.mount
  /etc/systemd/system/default.target.wants/snap-snap\x2dstore-592.mount
  
/etc/systemd/system/default.target.wants/var-snap-firefox-common-host\x2dhunspell.mount
  /etc/systemd/system/default.target.wants/snap-snap\x2dstore-599.mount

  HYPHEN is normal ASCII character or escaped by "\x2d"
  HYPHEN needs no escape , but the BACKSLASH is making troubles.
  no BACKSLASH allowed in filenames and directory names.
  seems to be a bad habit of "systemd" and "snap"

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1966203] Re: Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit code 1." in Ubuntu 22.04

2023-05-30 Thread Bernhard Riegler
Hi there, I see this with "lunar" Xubuntu 23.04

bernie@prod:~/Desktop$ journalctl -b |grep 'exit code 1'
Mai 30 17:16:45 prod systemd-udevd[246]: sda: Process '/usr/bin/unshare -m 
/usr/bin/snap auto-import --mount=/dev/sda' failed with exit code 1.
Mai 30 17:16:45 prod systemd-udevd[234]: sr0: Process '/usr/bin/unshare -m 
/usr/bin/snap auto-import --mount=/dev/sr0' failed with exit code 1.
Mai 30 17:16:46 prod systemd-udevd[230]: sda2: Process '/usr/bin/unshare -m 
/usr/bin/snap auto-import --mount=/dev/sda2' failed with exit code 1.
Mai 30 17:16:46 prod systemd-udevd[243]: sda11: Process '/usr/bin/unshare -m 
/usr/bin/snap auto-import --mount=/dev/sda11' failed with exit code 1.
Mai 30 17:16:46 prod systemd-udevd[232]: sda9: Process '/usr/bin/unshare -m 
/usr/bin/snap auto-import --mount=/dev/sda9' failed with exit code 1.
Mai 30 17:16:46 prod systemd-udevd[237]: sda7: Process '/usr/bin/unshare -m 
/usr/bin/snap auto-import --mount=/dev/sda7' failed with exit code 1.
Mai 30 17:16:46 prod systemd-udevd[227]: sda4: Process '/usr/bin/unshare -m 
/usr/bin/snap auto-import --mount=/dev/sda4' failed with exit code 1.
Mai 30 17:16:46 prod systemd-udevd[245]: sda10: Process '/usr/bin/unshare -m 
/usr/bin/snap auto-import --mount=/dev/sda10' failed with exit code 1.
Mai 30 17:16:46 prod systemd-udevd[236]: sda6: Process '/usr/bin/unshare -m 
/usr/bin/snap auto-import --mount=/dev/sda6' failed with exit code 1.
Mai 30 17:16:46 prod systemd-udevd[231]: sda3: Process '/usr/bin/unshare -m 
/usr/bin/snap auto-import --mount=/dev/sda3' failed with exit code 1.
Mai 30 17:16:46 prod systemd-udevd[246]: sda1: Process '/usr/bin/unshare -m 
/usr/bin/snap auto-import --mount=/dev/sda1' failed with exit code 1.
Mai 30 17:16:46 prod systemd-udevd[234]: sda5: Process '/usr/bin/unshare -m 
/usr/bin/snap auto-import --mount=/dev/sda5' failed with exit code 1.
Mai 30 17:16:46 prod systemd-udevd[235]: sda8: Process '/usr/bin/unshare -m 
/usr/bin/snap auto-import --mount=/dev/sda8' failed with exit code 1.
bernie@prod:~/Desktop$ cd /etc
bernie@prod:/etc$ ls *rel*
lsb-release  os-release
bernie@prod:/etc$ cat lsb-release 
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=23.04
DISTRIB_CODENAME=lunar
DISTRIB_DESCRIPTION="Ubuntu 23.04"
bernie@prod:/etc$ cat os-release 
PRETTY_NAME="Ubuntu 23.04"
NAME="Ubuntu"
VERSION_ID="23.04"
VERSION="23.04 (Lunar Lobster)"
VERSION_CODENAME=lunar
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/";
SUPPORT_URL="https://help.ubuntu.com/";
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/";
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy";
UBUNTU_CODENAME=lunar
LOGO=ubuntu-logo
bernie@prod:/etc$ uname -a
Linux prod 6.2.0-20-generic #20-Ubuntu SMP PREEMPT_DYNAMIC Thu Apr  6 07:48:48 
UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1966203

Title:
  Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with
  exit code 1." in Ubuntu 22.04

Status in snapd:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Configuration:
   OS:jammy-live-server20220320-amd64.iso
   CPU:AMD EPYC 7702 64-Core Processor
   UEFI Version:D8E119A
   BMC Version:D8BT19I
   SSD:Intel 1.60TB NVMe SSD
   Boot mode:legacy
  Reproduce Steps:
   1.Boot into BIOS and set boot mode to legacy
   2.install ubuntu 22.04 on NVMe SSD
   3.Check syslog log
  Current behaviors:
  syslog shows systemd-udevd errors in Ubuntu 22.04
  Feb  9 10:16:19 len systemd-udevd[2837]: nvme0n1: Process '/usr/bin/unshare 
-m /usr/bin/snap auto-import --mount=/dev/nvme0n1' failed with exit code 1.
  Feb  9 10:16:19 len systemd-udevd[2877]: nvme0n1p3: Process '/usr/bin/unshare 
-m /usr/bin/snap auto-import --mount=/dev/nvme0n1p3' failed with exit code 1.
  Feb  9 10:16:19 len systemd-udevd[2876]: nvme0n1p2: Process '/usr/bin/unshare 
-m /usr/bin/snap auto-import --mount=/dev/nvme0n1p2' failed with exit code 1.
  Feb  9 10:16:19 len systemd-udevd[2837]: nvme0n1p1: Process '/usr/bin/unshare 
-m /usr/bin/snap auto-import --mount=/dev/nvme0n1p1' failed with exit code 1.
  Feb  9 10:16:19 len systemd-udevd[2828]: sr0: Process '/usr/bin/unshare -m 
/usr/bin/snap auto-import --mount=/dev/sr0' failed with exit code 1.
  Feb  9 10:16:19 len systemd-udevd[2850]: dm-0: Process '/usr/bin/unshare -m 
/usr/bin/snap auto-import --mount=/dev/dm-0' failed with exit code 1.

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 2003408] Re: systemd-timesyncd asks only for DNS AAAA records

2023-01-24 Thread Bernhard Riegler
after powering down and up all devices DNS is working again with IPv4 resolution
see appended screenshot with a wireshark trace.

** Attachment added: "wireshark trace with correct DNS resolution of IPv4"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2003408/+attachment/5643141/+files/Screenshot%20from%202023-01-24%2013-57-53.png

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2003408

Title:
  systemd-timesyncd asks only for DNS  records

Status in systemd package in Ubuntu:
  New

Bug description:
  I want to user a time server with IPv4, but systemd-timesyncd only asks for 
DNS  records.
  see the appended screenshot with a wireshark trace.
  the /etc/gai.conf file is ignored.

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 2003408] [NEW] systemd-timesyncd asks only for DNS AAAA records

2023-01-20 Thread Bernhard Riegler
Public bug reported:

I want to user a time server with IPv4, but systemd-timesyncd only asks for DNS 
 records.
see the appended screenshot with a wireshark trace.
the /etc/gai.conf file is ignored.

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

** Attachment added: "wireshark trace for DNS activity"
   
https://bugs.launchpad.net/bugs/2003408/+attachment/5642634/+files/Screenshot%20from%202023-01-20%2008-54-14.png

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2003408

Title:
  systemd-timesyncd asks only for DNS  records

Status in systemd package in Ubuntu:
  New

Bug description:
  I want to user a time server with IPv4, but systemd-timesyncd only asks for 
DNS  records.
  see the appended screenshot with a wireshark trace.
  the /etc/gai.conf file is ignored.

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1990755] Re: HYPHEN character escaped in filenames with BACKSLASH

2022-09-25 Thread Bernhard Riegler
added Package systemd

** Package changed: ubuntu => systemd (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1990755

Title:
  HYPHEN character escaped in filenames with BACKSLASH

Status in systemd package in Ubuntu:
  New

Bug description:
  current Ubuntu 22.04 LTS shows

  oot@prod:~# find / -xdev -name '*\\x*'
  /usr/lib/systemd/system/system-systemd\x2dcryptsetup.slice
  /etc/systemd/system/snap-gtk\x2dcommon\x2dthemes-1535.mount
  /etc/systemd/system/snap-gnome\x2d3\x2d38\x2d2004-115.mount
  
/etc/systemd/system/multi-user.target.wants/snap-gtk\x2dcommon\x2dthemes-1535.mount
  
/etc/systemd/system/multi-user.target.wants/snap-gnome\x2d3\x2d38\x2d2004-115.mount
  
/etc/systemd/system/multi-user.target.wants/snap-snapd\x2ddesktop\x2dintegration-14.mount
  /etc/systemd/system/multi-user.target.wants/snap-snap\x2dstore-592.mount
  
/etc/systemd/system/multi-user.target.wants/var-snap-firefox-common-host\x2dhunspell.mount
  /etc/systemd/system/multi-user.target.wants/snap-snap\x2dstore-599.mount
  /etc/systemd/system/snap-snapd\x2ddesktop\x2dintegration-14.mount
  /etc/systemd/system/snap-snap\x2dstore-592.mount
  /etc/systemd/system/var-snap-firefox-common-host\x2dhunspell.mount
  /etc/systemd/system/snap-snap\x2dstore-599.mount
  
/etc/systemd/system/default.target.wants/snap-gnome\x2d3\x2d38\x2d2004-115.mount
  /etc/systemd/system/default.target.wants/snap-snap\x2dstore-592.mount
  
/etc/systemd/system/default.target.wants/var-snap-firefox-common-host\x2dhunspell.mount
  /etc/systemd/system/default.target.wants/snap-snap\x2dstore-599.mount

  HYPHEN is normal ASCII character or escaped by "\x2d"
  HYPHEN needs no escape , but the BACKSLASH is making troubles.
  no BACKSLASH allowed in filenames and directory names.
  seems to be a bad habit of "systemd" and "snap"

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1884135] [NEW] [LE_WH-1000XM3, playback] Playback problem: BT headset only plays gnome-terminal's bell (Ctrl-G), any media/audio is still output via builtin intel audio

2020-06-18 Thread Bernhard Gabler
Public bug reported:

After today's update, no audio can be played via connected Bluetooth
headset (Sony LE_WH-1000XM3). The sound setting offers internal speakers
or wireless headset, but either way any media (RhythmBox, Web video,
...) plays through the internal speakers.

The notable exception is gnome-console's ping (played as output of a
BELL character, like from hitting the backspace key on an empty bash
command line, or from

  echo -e \\007

which does play through wireless headset (or internal speaker) as set by
the sound setting.


Before today's update, the Bluetooth headset did play audio (yet not 
immediately upon connecting; for though the sound setting had switched to the 
external headset, any sound was still output to via internal speakers. But 
switching once to the internal speakers and back to the BT headset was a viable 
workaround to get sound out to the BT headset.)

>From apt log:
Start-Date: 2020-06-18  17:19:14
Commandline: aptdaemon role='role-commit-packages' sender=':1.315'
Upgrade: bind9-dnsutils:amd64 (1:9.16.1-0ubuntu2.1, 1:9.16.1-0ubuntu2.2), 
alsa-ucm-conf:amd64 (1.2.2-1, 1.2.2-1ubuntu0.1), bind9-host:amd64 
(1:9.16.1-0ubuntu2.1, 1:9.16.1-0ubuntu2.2), dnsutils:amd64 
(1:9.16.1-0ubuntu2.1, 1:9.16.1-0ubuntu2.2), initramfs-tools-bin:amd64 
(0.136ubuntu6, 0.136ubuntu6.1), busybox-static:amd64 (1:1.30.1-4ubuntu6, 
1:1.30.1-4ubuntu6.1), bind9-libs:amd64 (1:9.16.1-0ubuntu2.1, 
1:9.16.1-0ubuntu2.2), initramfs-tools-core:amd64 (0.136ubuntu6, 
0.136ubuntu6.1), initramfs-tools:amd64 (0.136ubuntu6, 0.136ubuntu6.1), 
gnome-shell-extension-ubuntu-dock:amd64 (67ubuntu20.04.5, 68ubuntu1~20.04.1), 
busybox-initramfs:amd64 (1:1.30.1-4ubuntu6, 1:1.30.1-4ubuntu6.1)
Remove: linux-image-5.3.0-55-generic:amd64 (5.3.0-55.49), 
linux-modules-extra-5.3.0-55-generic:amd64 (5.3.0-55.49), 
linux-headers-5.3.0-55-generic:amd64 (5.3.0-55.49), 
linux-modules-5.3.0-55-generic:amd64 (5.3.0-55.49), 
linux-headers-5.3.0-55:amd64 (5.3.0-55.49)
End-Date: 2020-06-18  17:20:14

Could the issue be caused by one of these packages?
  alsa-ucm-conf:amd64 (1.2.2-1, 1.2.2-1ubuntu0.1)
  gnome-shell-extension-ubuntu-dock:amd64 (67ubuntu20.04.5, 68ubuntu1~20.04.1)

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
Uname: Linux 5.4.0-37-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  bernhard   2078 F pulseaudio
 /dev/snd/pcmC0D0c:   bernhard   2078 F...m pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Jun 18 18:42:49 2020
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-12-11 (919 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: LE_WH-1000XM3
Symptom_Type: Only some of outputs are working
Title: [LE_WH-1000XM3, playback] Playback problem
UpgradeStatus: Upgraded to focal on 2020-06-05 (13 days ago)
dmi.bios.date: 09/13/2017
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.01.
dmi.board.name: Woody_KL
dmi.board.vendor: KBL
dmi.board.version: V1.01.
dmi.chassis.type: 31
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.01.
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.01.:bd09/13/2017:svnAcer:pnSpinSP513-52N:pvrV1.01.:rvnKBL:rnWoody_KL:rvrV1.01.:cvnAcer:ct31:cvrV1.01.:
dmi.product.family: Spin 5
dmi.product.name: Spin SP513-52N
dmi.product.sku: 
dmi.product.version: V1.01.
dmi.sys.vendor: Acer
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-06-18T18:32:11.193118

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


** Tags: amd64 apport-bug focal

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

Title:
  [LE_WH-1000XM3, playback] Playback problem: BT headset only plays
  gnome-terminal's bell (Ctrl-G), any media/audio is still output via
  builtin intel audio

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  After today's update, no audio can be played via connected Bluetooth
  headset (Sony LE_WH-1000XM3). The sound setting offers internal
  speakers or wireless headset, but either way any media (RhythmBox, Web
  video, ...) plays through the internal speakers.

  The notable exception is gnome-console's ping (played as output of a
  BELL character, like from hitting the backspace key on an empty bash
  command line, or from

echo -e \\007

  which does play through wireless headset (or internal speaker) as set
  by the sound setting.

  
  Before today's update, the Bluetooth headset did play audio (yet not 
immediately upon co

[Touch-packages] [Bug 49498] Re: With Evince I can't copy text out from PDF documents created with cups-pdf

2019-01-14 Thread Bernhard Schülke
(Ubuntu 18.04)

Evince
Version = 3.28.4-0ubuntu1 
Diodon
Version = 1.8.0-1

Same problem.
When i use atril as pdf-reader, i can copy text to the diodon table. But it 
doesn't work with evince. 

Date today = 2018-01-14.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/49498

Title:
  With Evince I can't copy text out from PDF documents created with
  cups-pdf

Status in Evince:
  Unknown
Status in Poppler:
  Fix Released
Status in poppler package in Ubuntu:
  Fix Released

Bug description:
  When I create PDF documents with the cups-pdf printer, after, I can't select 
text and copy it out from the PDF itself.
  The strange thing is that when I have installed the cups-pdf printer with the 
gnome-cups-manager, I have printed the test page. In this case, and only in 
this case, when I opened the pdf created in Evince I am able to copy the text 
and paste it elsewhere.
  The problem is that when I use the cups-pdf from other tools like gedit, I 
can create PDF documents, but when I open it in Evince, I can't copy text out. 
These documents are like "protected" from copying.

  
  The step to reproduce are:
  1) install cups-pdf
  2) open gnome-cups-manager and install the new printer, then make a test 
pressing the
  "Print a test page" button
  3) open in Evince the just created PDF document and try to copy the text 
> you are able to do
  4) open gedit, write something, and choose to create a PDF with cups-pdf
  5) open in Evince the PDF document just created and try to copy the text 
> you aren't able to do

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1798797] [NEW] Drucker

2018-10-19 Thread Bernhard Jung
Public bug reported:

Kompliziert ... Ich möchte nur den Drucker zum laufen bringen. Zeigt an,
Drucker druckt nicht. Bei Ubuntu 16.4 ist alles einwandfrei gelaufen...

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
CompositorRunning: None
Date: Fri Oct 19 12:21:45 2018
DistUpgraded: 2018-10-17 18:15:17,451 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Kindprozess 
»./xorg_fix_proprietary.py« konnte nicht ausgeführt werden (No such file or 
directory) (8))
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 7340] [1002:9808] 
(prog-if 00 [VGA controller])
   Subsystem: Lenovo Wrestler [Radeon HD 7340] [17aa:365d]
InstallationDate: Installed on 2018-03-08 (224 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: LENOVO 6596
ProcEnviron:
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=ae1dcc47-b3c8-4069-bedd-acb8c12fdbfb ro drm.debug=0xe plymouth:debug
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2018-10-17 (1 days ago)
dmi.bios.date: 08/28/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: EKKT25BUS
dmi.board.name: Remore CRB
dmi.board.vendor: LENOVO
dmi.board.version: Win8 STD MM DPK IPG
dmi.chassis.type: 13
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnLENOVO:bvrEKKT25BUS:bd08/28/2012:svnLENOVO:pn6596:pvrLenovoC445:rvnLENOVO:rnRemoreCRB:rvrWin8STDMMDPKIPG:cvnToBeFilledByO.E.M.:ct13:cvrToBeFilledByO.E.M.:
dmi.product.family: IdeaCentre
dmi.product.name: 6596
dmi.product.version: Lenovo C445
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Wed Oct 17 11:04:23 2018
xserver.configfile: default
xserver.devices:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.4-0ubuntu0.8

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  Drucker

Status in xorg package in Ubuntu:
  New

Bug description:
  Kompliziert ... Ich möchte nur den Drucker zum laufen bringen. Zeigt
  an, Drucker druckt nicht. Bei Ubuntu 16.4 ist alles einwandfrei
  gelaufen...

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CompositorRunning: None
  Date: Fri Oct 19 12:21:45 2018
  DistUpgraded: 2018-10-17 18:15:17,451 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Kindprozess 
»./xorg_fix_proprietary.py« konnte nicht ausgeführt werden (No such file or 
directory) (8))
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 7340] [1002:9808] 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Wrestler [Radeon HD 7340] [17aa:365d]
  InstallationDate: Installed on 2018-03-08 (224 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 6596
  ProcEnviron:
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=ae1dcc47-b3c8-4069-bedd-acb8c12fdbfb ro drm.debug=0xe plymouth:debug
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-10-17 (1 days ago)
  dmi.bios.date: 08/28/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EKKT25BUS
  dmi.board.name: Remore CRB
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 STD MM DPK IPG
  dmi.chassis.type: 13
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvrEKKT25BUS:bd08/28/2012:svnLENOVO:pn6596:pvrLenovoC445:rvnLENOVO:rnRemoreCRB:rvrWin8STDMMDPKIPG:cvnToBeFilledByO.E.M.:ct13:cvrToBeFilledByO

[Touch-packages] [Bug 1798533] [NEW] Drucker

2018-10-18 Thread Bernhard Jung
Public bug reported:

Der Drucker kann nicht installiert werden. Filter fehlt (Fehlermeldung)
?

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
CompositorRunning: None
Date: Thu Oct 18 08:47:12 2018
DistUpgraded: 2018-10-17 18:15:17,451 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Kindprozess 
»./xorg_fix_proprietary.py« konnte nicht ausgeführt werden (No such file or 
directory) (8))
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 7340] [1002:9808] 
(prog-if 00 [VGA controller])
   Subsystem: Lenovo Wrestler [Radeon HD 7340] [17aa:365d]
InstallationDate: Installed on 2018-03-08 (223 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: LENOVO 6596
ProcEnviron:
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=ae1dcc47-b3c8-4069-bedd-acb8c12fdbfb ro drm.debug=0xe plymouth:debug
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2018-10-17 (0 days ago)
dmi.bios.date: 08/28/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: EKKT25BUS
dmi.board.name: Remore CRB
dmi.board.vendor: LENOVO
dmi.board.version: Win8 STD MM DPK IPG
dmi.chassis.type: 13
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnLENOVO:bvrEKKT25BUS:bd08/28/2012:svnLENOVO:pn6596:pvrLenovoC445:rvnLENOVO:rnRemoreCRB:rvrWin8STDMMDPKIPG:cvnToBeFilledByO.E.M.:ct13:cvrToBeFilledByO.E.M.:
dmi.product.family: IdeaCentre
dmi.product.name: 6596
dmi.product.version: Lenovo C445
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Wed Oct 17 11:04:23 2018
xserver.configfile: default
xserver.devices:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.4-0ubuntu0.8

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  Drucker

Status in xorg package in Ubuntu:
  New

Bug description:
  Der Drucker kann nicht installiert werden. Filter fehlt
  (Fehlermeldung) ?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CompositorRunning: None
  Date: Thu Oct 18 08:47:12 2018
  DistUpgraded: 2018-10-17 18:15:17,451 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Kindprozess 
»./xorg_fix_proprietary.py« konnte nicht ausgeführt werden (No such file or 
directory) (8))
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 7340] [1002:9808] 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Wrestler [Radeon HD 7340] [17aa:365d]
  InstallationDate: Installed on 2018-03-08 (223 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 6596
  ProcEnviron:
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=ae1dcc47-b3c8-4069-bedd-acb8c12fdbfb ro drm.debug=0xe plymouth:debug
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-10-17 (0 days ago)
  dmi.bios.date: 08/28/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EKKT25BUS
  dmi.board.name: Remore CRB
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 STD MM DPK IPG
  dmi.chassis.type: 13
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvrEKKT25BUS:bd08/28/2012:svnLENOVO:pn6596:pvrLenovoC445:rvnLENOVO:rnRemoreCRB:rvrWin8STDMMDPKIPG:cvnToBeFilledByO.E.M.:ct13:cvrToBeFilledByO.E.M.:
  dmi.product.family: IdeaCentre
  

[Touch-packages] [Bug 1758655] [NEW] [USB-Audio - USB Device 0xccd:0x77, playback] No sound at all

2018-03-25 Thread Bernhard Schülke
Public bug reported:

like bug https://bugs.launchpad.net/bugs/855567

But with Ubuntu 16.04.3 LTS 64 bit
Kernel: 4.13.0-37-generic
AMD FX(tm)-6350 Six-Core Processor × 6 
GeForce GT 730/PCIe/SSE2
16 GB RAM

pulseaudio is used.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-37-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  bern   5504 F pulseaudio
 /dev/snd/pcmC1D7p:   bern   5504 F...m pulseaudio
 /dev/snd/controlC1:  bern   5504 F pulseaudio
 /dev/snd/controlC0:  bern   5504 F pulseaudio
CurrentDesktop: Unity
Date: Sun Mar 25 13:37:09 2018
InstallationDate: Installed on 2017-08-13 (224 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:U0xccd0x77 failed
Symptom_Card: Aureon Dual USB - USB Device 0xccd:0x77
Symptom_Type: No sound at all
Title: [USB-Audio - USB Device 0xccd:0x77, playback] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/04/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2901
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: SABERTOOTH 990FX R2.0
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2901:bd05/04/2016:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FXR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: To be filled by O.E.M.

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


** Tags: amd64 apport-bug xenial

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

Title:
  [USB-Audio - USB Device 0xccd:0x77, playback] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  like bug https://bugs.launchpad.net/bugs/855567

  But with Ubuntu 16.04.3 LTS 64 bit
  Kernel: 4.13.0-37-generic
  AMD FX(tm)-6350 Six-Core Processor × 6 
  GeForce GT 730/PCIe/SSE2
  16 GB RAM

  pulseaudio is used.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  bern   5504 F pulseaudio
   /dev/snd/pcmC1D7p:   bern   5504 F...m pulseaudio
   /dev/snd/controlC1:  bern   5504 F pulseaudio
   /dev/snd/controlC0:  bern   5504 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Mar 25 13:37:09 2018
  InstallationDate: Installed on 2017-08-13 (224 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:U0xccd0x77 failed
  Symptom_Card: Aureon Dual USB - USB Device 0xccd:0x77
  Symptom_Type: No sound at all
  Title: [USB-Audio - USB Device 0xccd:0x77, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/04/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2901
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH 990FX R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2901:bd05/04/2016:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FXR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1758655/+subscriptions

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

[Touch-packages] [Bug 1754294] Re: After last updated libcurl3 on libcurl4, some apps are removed.

2018-03-10 Thread Bernhard M
I have the same problem with Kopano packeges and php 7.0.

In fact I even don't know why there is a conflict and a problem to solve
this. libсurl3 should install /usr/lib/x86_64-linux-gnu/libcurl.so.3 and
libcurl4 /usr/lib/x86_64-linux-gnu/libcurl.so.4

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to curl in Ubuntu.
https://bugs.launchpad.net/bugs/1754294

Title:
  After last updated libcurl3 on libcurl4, some apps are removed.

Status in curl package in Ubuntu:
  Invalid

Bug description:
  Hi!

  After last updated libcurl3 on libcurl4, system (Kubuntu 18.04 bionic) 
deleted such applications as:
  virtualbox-5.2
  opera-stable
  slack-desktop

  I really need these applications, I installed them with broken
  dependencies, but they are deleted after each update. Is it possible
  to make the dependence of the libcurl3 in libcurl4, and not remove it
  altogether from system?

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1750937] Re: 14.04 Kernel update on 2/21 breaks Nvidia drivers

2018-02-22 Thread Bernhard
It affects me too:

Nvidia NVS 300 and GT 430 . Nvidia 340.x and 384.111

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

Title:
  14.04 Kernel update on 2/21 breaks Nvidia drivers

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Running fine with nvidia-384 until this kernel update came along.
  When booted into the new kernel, got super low resolution and nvidia-
  settings was missing most of its functionality - could not change
  resolution.

  Rebooted into 4.4.0-112 kernel and all was well.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3)
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Feb 21 19:23:39 2018
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 4.4.0-112-generic, x86_64: installed
   bbswitch, 0.7, 4.4.0-116-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-116-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation Device [10de:1c82] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: eVga.com. Corp. Device [3842:6253]
  InstallationDate: Installed on 2015-03-03 (1086 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: ASUSTeK COMPUTER INC. M11AD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=5a88d2a1-0a24-415b-adc2-28435b13248a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/15/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M11AD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: M11AD
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed Feb 21 18:48:14 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.3-1ubuntu2.3~trusty4

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1624320] Re: systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing entries

2017-05-26 Thread Bernhard
Hi,

I just upgraded from Ubuntu 16.10 to 17.04 and observed the following
systemd-resolve behaviour that might be related to this bug:

--> Any domain listed after the "search" keyword in /etc/resolv.conf
stops being resolved by systemd-resolve.

respectively

--> Any domain listed as "DNS Domain:" when querying "systemd-resolve
--status" stops being resolved by systemd-resolve

I confirmed with tcpdump that systemd-resolve will not query my local or
any dnsserver for any subdomains for any domain listed under the
"search" keyword.

Changing the domains after the search keyword in /erc/resolv.conf
immediately changes which domains systemd-resolve will ignore and not
resolve.

The search domain is normally automatically set in response to receiving
an "option domain-name" from the local dhcp server and normally used to
translate requests for www to e.g. www.localdomain.at if localdomain.at
was the domain-name sent by the DHCP server.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1624320

Title:
  systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing
  entries

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  systemd-resolved, or more precisely the hook script
  /lib/systemd/system/systemd-resolved.service.d/resolvconf.conf, causes
  resolvconf to add 127.0.0.53 to the set of nameservers in
  /etc/resolv.conf alongside the other nameservers.  That makes no sense
  because systemd-resolved sets up 127.0.0.53 as a proxy for those other
  nameservers.  The effect is similar to bug 1624071 but for
  applications doing their own DNS lookups.  It breaks any DNSSEC
  validation that systemd-resolved tries to do; applications will
  failover to the other nameservers, bypassing validation failures.  And
  it makes failing queries take twice as long.

  /etc/resolv.conf should have only 127.0.0.53 when systemd-resolved is
  active.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


Re: [Touch-packages] [Bug 1385817] Re: initscripts package fails to upgrade if there are local init scripts on the system with no LSB headers

2017-02-17 Thread Bernhard Nikola
thx for answer.

There are more than one way to install an operation system.
In my opinion it was a -not fixed fault- during installation with a 
non-efi bios.

Bernhard





Am 17.02.2017 um 15:50 schrieb Phillip Susi:
> If this isn't a bug in Ubuntu and there isn't anything we can do about
> it, then why has it not been closed as invalid or wontfix?
>

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sysvinit in Ubuntu.
https://bugs.launchpad.net/bugs/1385817

Title:
  initscripts package fails to upgrade if there are local init scripts
  on the system with no LSB headers

Status in sysvinit package in Ubuntu:
  Triaged

Bug description:
  The dependency-based boot sequencing originally introduced upstream
  with Debian 6.0 is now always enabled in Ubuntu 14.10.

  For optimal sequencing, all init.d scripts should declare their
  dependencies in an LSB header. This is already the case for scripts
  shipped in Ubuntu, but users should check their local scripts and
  consider adding that information.

  For more information on this feature refer to the information
  available in /usr/share/doc/insserv/README.Debian.

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: initscripts-2.88dsf 41ubuntu18
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux x86_64 3.13.0-37-generic
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  Date: Sun October 26 2014 7:52:55
  DuplicateSignature: Package: initscripts: 2.88dsf-41ubuntu18: the 
post-installation script subprocess installed returned error exit status 1
  ErrorMessage: The post-install script subprocess installed returned error 
exit status 1
  InstallationDate: Installed on 2014-08-06 (80 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: sysvinit
  Title: initscripts package 2.88dsf-41ubuntu18 failed to install / upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to utopic on 2014-10-26 (0 days ago)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1655699] [NEW] no sound-card detected after linux-image upgrade

2017-01-11 Thread Bernhard Maechtel
Public bug reported:

aplay: device_list:268: no soundcards found...

00:1f.3 Audio device: Intel Corporation Device 9d70 (rev 21)
Subsystem: Dell Device 06f2
Flags: fast devsel, IRQ 255
Memory at d122 (64-bit, non-prefetchable) [disabled] [size=16K]
Memory at d120 (64-bit, non-prefetchable) [disabled] [size=64K]
Capabilities: 

00:1f.4 SMBus: Intel Corporation Device 9d23 (rev 21)

:~$ sudo apt-get install linux-restricted-modules-`uname -r` linux-generic
Reading package lists... Done
Building dependency tree   
Reading state information... Done
E: Unable to locate package linux-restricted-modules-4.4.0-59-generic
E: Couldn't find any package by regex 'linux-restricted-modules-4.4.0-59-generic

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

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

Title:
  no sound-card detected after linux-image upgrade

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  aplay: device_list:268: no soundcards found...

  00:1f.3 Audio device: Intel Corporation Device 9d70 (rev 21)
Subsystem: Dell Device 06f2
Flags: fast devsel, IRQ 255
Memory at d122 (64-bit, non-prefetchable) [disabled] [size=16K]
Memory at d120 (64-bit, non-prefetchable) [disabled] [size=64K]
Capabilities: 

  00:1f.4 SMBus: Intel Corporation Device 9d23 (rev 21)

  :~$ sudo apt-get install linux-restricted-modules-`uname -r` linux-generic
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  E: Unable to locate package linux-restricted-modules-4.4.0-59-generic
  E: Couldn't find any package by regex 
'linux-restricted-modules-4.4.0-59-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1655699/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1556459] Re: [Lenovo ThinkPad W530] Regression: cannot set up 3 display configuration any more (Optimus)

2016-10-13 Thread Bernhard Zürn
Since a few wweks I am using the Nouveau (OpenSource) NVIDIA driver on
16.04. without those problems. Seems to be only soultion right now.

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

Title:
  [Lenovo ThinkPad W530] Regression: cannot set up 3 display
  configuration any more (Optimus)

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I cannot set up the third monitor any more (it was working beginning
  of March 2016 with Ubuntu 16.04).

  The configuration with NVIDIA Optimus starts with builtin display (of
  Thinkpad W530) and one of (3K) monitors, the second monitor is
  detected, but not used.

  The unity configuration tool shows me two message boxes:

  "The selected configuration for displays could not be applied
  could not set the configuration for CRTC 64"

  and

  "Failed to apply configuration: %s

  
GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._gsd_2drr_2derror_2dquark.Code2: 
could not set the configuration for CRTC 64
  "

  The first one I have seen at boot time on login screen (with 3
  displays) previously, the second one is new.

  The third monitor works if Optimus gets disabled in  BIOS and the
  machine runs with Nvidia only

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Uname: Linux 4.4.0-12-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.20-0ubuntu3
  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: Sat Mar 12 18:44:54 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.16, 4.4.0-10-generic, x86_64: installed
   virtualbox, 5.0.16, 4.4.0-11-generic, x86_64: installed
   virtualbox, 5.0.16, 4.4.0-12-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f5]
   NVIDIA Corporation GK107GLM [Quadro K2000M] [10de:0ffb] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo GK107GLM [Quadro K2000M] [17aa:21f5]
  InstallationDate: Installed on 2016-02-25 (15 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160225)
  MachineType: LENOVO 2447MU0
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-12-generic 
root=UUID=c01ceec8-4b0c-447f-af8f-3e9c4ae90e15 ro rootflags=subvol=@ quiet 
splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/18/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G5ETA3WW (2.63 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2447MU0
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG5ETA3WW(2.63):bd09/18/2015:svnLENOVO:pn2447MU0:pvrThinkPadW530:rvnLENOVO:rn2447MU0:rvr0B98401WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2447MU0
  dmi.product.version: ThinkPad W530
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160209-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.1-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160218-1ubuntu3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sat Mar 12 18:30:45 2016
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.1-1ubuntu4

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1364522] Re: Firefox crashes sometimes when using webgl with nouveau driver

2016-09-14 Thread Bernhard Übelacker
I was probably wrong last year.
- In [1] there are still many crash reports to Mozilla.
- These point very often too to the ~GLContextGLX destructor, similar to 
comment #0.
- Kernels are often Ubuntu kernels.
- Probably just on 14.04 LTS.
- Gallium 0.4 on NV46 or NV4B.

[1] https://crash-
stats.mozilla.com/search/?app_notes=~Mesa%2010.1.3&signature=~nouveau_dri.so&_sort=-date&_facets=signature&_columns=date&_columns=signature&_columns=product&_columns=version&_columns=build_id&_columns=platform
#facet-signature

So probably the patch mentioned in comment #2 could still be worth to be
applied.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1364522

Title:
  Firefox crashes sometimes when using webgl with nouveau driver

Status in firefox package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New

Bug description:
  Visiting with Firefox e.g.
  https://developer.mozilla.org/de/demos/detail/orange-slice/launch
  makes firefox crash.

  Program received signal SIGSEGV, Segmentation fault.
  nouveau_fence_next (screen=screen@entry=0x5a5a5a5a) at 
../../../../../../src/gallium/drivers/nouveau/nouveau_fence.c:226
  226if (screen->fence.current->state < NOUVEAU_FENCE_STATE_EMITTING)
  (gdb) bt
  #0  nouveau_fence_next (screen=screen@entry=0x5a5a5a5a) at 
../../../../../../src/gallium/drivers/nouveau/nouveau_fence.c:226
  #1  0x9b5b7fc0 in nv30_context_kick_notify (push=0x9b8f62b0) at 
../../../../../../src/gallium/drivers/nouveau/nv30/nv30_context.c:48
  #2  0xa0a0ea3e in pushbuf_submit (push=push@entry=0x9b8f62b0, chan=, chan=) at ../../nouveau/pushbuf.c:325
  #3  0xa0a0ed7a in pushbuf_flush (push=push@entry=0x9b8f62b0) at 
../../nouveau/pushbuf.c:402
  #4  0xa0a0faca in nouveau_pushbuf_kick (push=0x9b8f62b0, chan=0xa40c5420) at 
../../nouveau/pushbuf.c:774
  #5  0x9b5b811f in PUSH_KICK (push=) at 
../../../../../../src/gallium/drivers/nouveau/nouveau_winsys.h:56
  #6  nv30_context_flush (pipe=0x9b986000, fence=0x0, flags=0) at 
../../../../../../src/gallium/drivers/nouveau/nv30/nv30_context.c:83
  #7  0x9b4b4e1c in st_flush (st=st@entry=0x989e8000, fence=fence@entry=0x0, 
flags=flags@entry=0) at ../../../../src/mesa/state_tracker/st_cb_flush.c:87
  #8  0x9b4b4e82 in st_glFlush (ctx=0x98844000) at 
../../../../src/mesa/state_tracker/st_cb_flush.c:121
  #9  0x9b3b3065 in _mesa_flush (ctx=ctx@entry=0x98844000) at 
../../../../src/mesa/main/context.c:1691
  #10 0x9b3b3130 in _mesa_make_current (newCtx=newCtx@entry=0x0, 
drawBuffer=drawBuffer@entry=0x0, readBuffer=readBuffer@entry=0x0) at 
../../../../src/mesa/main/context.c:1503
  #11 0x9b4dee74 in st_api_make_current (stapi=0x9b779700 , 
stctxi=0x0, stdrawi=0x0, streadi=0x0) at 
../../../../src/mesa/state_tracker/st_manager.c:746
  #12 0x9b59d9ee in dri_unbind_context (cPriv=0x994e3120) at 
../../../../../../../src/gallium/state_trackers/dri/drm/dri_context.c:215
  #13 0x9b38db93 in driUnbindContext (pcp=0x994e3120) at 
../../../../../../../src/mesa/drivers/dri/common/dri_util.c:578
  #14 0x9b7df149 in dri2_unbind_context (context=0x9b9cbc20, new=0x0) at 
../../../../src/glx/dri2_glx.c:184
  #15 0x9b7b7985 in MakeContextCurrent (dpy=dpy@entry=0xb7191000, 
draw=draw@entry=0, read=read@entry=0, gc_user=gc_user@entry=0x0) at 
../../../../src/glx/glxcurrent.c:245
  #16 0x9b7b7a73 in glXMakeCurrent (dpy=0xb7191000, draw=0, gc=0x0) at 
../../../../src/glx/glxcurrent.c:293
  #17 0xb3d3916d in mozilla::gl::GLXLibrary::xMakeCurrent (this=0xb6e58470 
, display=0xb7191000, drawable=drawable@entry=0, 
context=context@entry=0x0) at 
/build/buildd/firefox-31.0+build1/gfx/gl/GLContextProviderGLX.cpp:525
  #18 0xb3d39d92 in mozilla::gl::GLContextGLX::~GLContextGLX (this=0x988dc800, 
__in_chrg=) at 
/build/buildd/firefox-31.0+build1/gfx/gl/GLContextProviderGLX.cpp:836
  #19 0xb3d39e12 in mozilla::gl::GLContextGLX::~GLContextGLX (this=0x988dc800, 
__in_chrg=) at 
/build/buildd/firefox-31.0+build1/gfx/gl/GLContextProviderGLX.cpp:845
  #20 0xb3d38ea0 in 
mozilla::detail::GenericRefCounted<(mozilla::detail::RefCountAtomicity)0>::Release
 (this=0x988dc800) at ../../dist/include/mozilla/GenericRefCounted.h:95
  #21 0xb3ddc635 in nsRefPtr::assign_assuming_AddRef 
(this=this@entry=0x9b8eb84c, newPtr=newPtr@entry=0x0) at 
../../dist/include/nsAutoPtr.h:882
  #22 0xb4561170 in assign_with_AddRef (rawPtr=0x0, this=0x9b8eb84c) at 
../../../dist/include/nsAutoPtr.h:866
  #23 operator= (rhs=0x0, this=0x9b8eb84c) at 
../../../dist/include/nsAutoPtr.h:964
  #24 mozilla::WebGLContext::DestroyResourcesAndContext 
(this=this@entry=0x9b8eb800) at 
/build/buildd/firefox-31.0+build1/content/canvas/src/WebGLContext.cpp:284
  #25 0xb45611bb in mozilla::WebGLContext::~WebGLContext (this=0x9b8eb800, 
__in_chrg=) at 
/build/buildd/firefox-31.0+build1/content/canvas/src/WebGLContext.cpp:203
  #26 0xb455e330 in mozilla::WebGL1Context::~WebGL1Context (this=0x9b8eb800, 
__in_ch

[Touch-packages] [Bug 1577760] Re: Screen Display 'Apply' fails

2016-08-15 Thread Bernhard Zürn
I also do not have /usr/local/lib/libimobiledevice.so.6 on 16.04 amd64

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1577760

Title:
  Screen Display 'Apply' fails

Status in upower package in Ubuntu:
  Invalid

Bug description:
  Since upgrading to 16.04, when I click on the 'Apply' button of the
  'Screen Display' utility (without setting anything), I get an error
  dialog:

  "Failed to apply configuration: %s
  GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface 
'org.gnome.SettingsDaemon.XRANDR_2' on object at path 
/org/gnome/SettingsDaemon/XRANDR"

  What I expect to be able to configure multiple monitors - though it
  fails even when I have none connected.

  It is a Lenovo X250 with a docking station (though it doesn't make any
  difference if the docking station is used or not).

  WORKAROUND: sudo ln -s /usr/lib/x86_64-linux-gnu/libusbmuxd.so.4.0.0
  /usr/lib/x86_64-linux-gnu/libusbmuxd.so.2

  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: Tue May  3 13:20:37 2016
  DistUpgraded: 2016-04-22 10:05:12,580 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
     Subsystem: Lenovo Broadwell-U Integrated Graphics [17aa:2226]
  InstallationDate: Installed on 2015-05-20 (348 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 20CM001QUK
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (11 days ago)
  dmi.bios.date: 04/06/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N10ET33W (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CM001QUK
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN10ET33W(1.12):bd04/06/2015:svnLENOVO:pn20CM001QUK:pvrThinkPadX250:rvnLENOVO:rn20CM001QUK:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20CM001QUK
  dmi.product.version: ThinkPad X250
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue May  3 12:33:42 2016
  xserver.configfile: default
  xserver.errors:
   intel(0): page flipping failed, on CRTC:25 (pipe=1), disabling synchronous 
page flips
   intel(0): failed to set mode: No such file or directory [2]
   intel(0): Failed to restore display configuration
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1079
   vendor LGD
  xserver.version: 2:1.18.3-1ubuntu2

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1556459] Re: [Lenovo ThinkPad W530] Regression: cannot set up 3 display configuration any more (Optimus)

2016-08-15 Thread Bernhard Zürn
Also affected on Dell 16.04 64bit Nvidia Optimus dmidecode attached

** Attachment added: "dmidecode.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1556459/+attachment/4721575/+files/dmidecode.txt

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

Title:
  [Lenovo ThinkPad W530] Regression: cannot set up 3 display
  configuration any more (Optimus)

Status in xorg package in Ubuntu:
  Triaged

Bug description:
  I cannot set up the third monitor any more (it was working beginning
  of March 2016 with Ubuntu 16.04).

  The configuration with NVIDIA Optimus starts with builtin display (of
  Thinkpad W530) and one of (3K) monitors, the second monitor is
  detected, but not used.

  The unity configuration tool shows me two message boxes:

  "The selected configuration for displays could not be applied
  could not set the configuration for CRTC 64"

  and

  "Failed to apply configuration: %s

  
GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._gsd_2drr_2derror_2dquark.Code2: 
could not set the configuration for CRTC 64
  "

  The first one I have seen at boot time on login screen (with 3
  displays) previously, the second one is new.

  The third monitor works if Optimus gets disabled in  BIOS and the
  machine runs with Nvidia only

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Uname: Linux 4.4.0-12-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.20-0ubuntu3
  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: Sat Mar 12 18:44:54 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.16, 4.4.0-10-generic, x86_64: installed
   virtualbox, 5.0.16, 4.4.0-11-generic, x86_64: installed
   virtualbox, 5.0.16, 4.4.0-12-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f5]
   NVIDIA Corporation GK107GLM [Quadro K2000M] [10de:0ffb] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo GK107GLM [Quadro K2000M] [17aa:21f5]
  InstallationDate: Installed on 2016-02-25 (15 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160225)
  MachineType: LENOVO 2447MU0
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-12-generic 
root=UUID=c01ceec8-4b0c-447f-af8f-3e9c4ae90e15 ro rootflags=subvol=@ quiet 
splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/18/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G5ETA3WW (2.63 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2447MU0
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG5ETA3WW(2.63):bd09/18/2015:svnLENOVO:pn2447MU0:pvrThinkPadW530:rvnLENOVO:rn2447MU0:rvr0B98401WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2447MU0
  dmi.product.version: ThinkPad W530
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160209-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.1-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160218-1ubuntu3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sat Mar 12 18:30:45 2016
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.1-1ubuntu4

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1556459] Re: [Lenovo ThinkPad W530] Regression: cannot set up 3 display configuration any more (Optimus)

2016-08-15 Thread Bernhard Zürn
GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._gsd_2drr_2derror_2dquark.Code2

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

Title:
  [Lenovo ThinkPad W530] Regression: cannot set up 3 display
  configuration any more (Optimus)

Status in xorg package in Ubuntu:
  Triaged

Bug description:
  I cannot set up the third monitor any more (it was working beginning
  of March 2016 with Ubuntu 16.04).

  The configuration with NVIDIA Optimus starts with builtin display (of
  Thinkpad W530) and one of (3K) monitors, the second monitor is
  detected, but not used.

  The unity configuration tool shows me two message boxes:

  "The selected configuration for displays could not be applied
  could not set the configuration for CRTC 64"

  and

  "Failed to apply configuration: %s

  
GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._gsd_2drr_2derror_2dquark.Code2: 
could not set the configuration for CRTC 64
  "

  The first one I have seen at boot time on login screen (with 3
  displays) previously, the second one is new.

  The third monitor works if Optimus gets disabled in  BIOS and the
  machine runs with Nvidia only

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Uname: Linux 4.4.0-12-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.20-0ubuntu3
  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: Sat Mar 12 18:44:54 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.16, 4.4.0-10-generic, x86_64: installed
   virtualbox, 5.0.16, 4.4.0-11-generic, x86_64: installed
   virtualbox, 5.0.16, 4.4.0-12-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f5]
   NVIDIA Corporation GK107GLM [Quadro K2000M] [10de:0ffb] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo GK107GLM [Quadro K2000M] [17aa:21f5]
  InstallationDate: Installed on 2016-02-25 (15 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160225)
  MachineType: LENOVO 2447MU0
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-12-generic 
root=UUID=c01ceec8-4b0c-447f-af8f-3e9c4ae90e15 ro rootflags=subvol=@ quiet 
splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/18/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G5ETA3WW (2.63 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2447MU0
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG5ETA3WW(2.63):bd09/18/2015:svnLENOVO:pn2447MU0:pvrThinkPadW530:rvnLENOVO:rn2447MU0:rvr0B98401WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2447MU0
  dmi.product.version: ThinkPad W530
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160209-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.1-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160218-1ubuntu3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sat Mar 12 18:30:45 2016
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.1-1ubuntu4

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1409166] Re: Popup dialog "could not set the configuration for CRTC 65" steals keyboard, hinders login in 3-monitor configuration

2016-08-15 Thread Bernhard Zürn
Same problem here on Dell and 16.04. but sometimes it works. Very
annoying. What can wie do to help ?

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

Title:
  Popup dialog "could not set the configuration for CRTC 65" steals
  keyboard, hinders login in 3-monitor configuration

Status in xorg package in Ubuntu:
  Triaged

Bug description:
  Every time I boot, while I'm trying to enter my password in the
  initial login screen (from Unity?), a dialog box pops up saying "Could
  not switch the monitor configuration  could not set the configuration
  for CRTC 65".

  The dialog box also steals the keyboard focus, which is very confusing
  if for some reason you're entering the password on an external display
  while the normally unused laptop display is not visible.  For example,
  three times in a row this morning I rebooted and tried unsuccessfully
  to log in.  Since the dialog box is only displayed on the laptop
  display, which I never use when external monitors are available, I had
  no idea why my keyboard seemed broken.

  Background:

  My Lenovo Thinkpad X230 Tablet laptop has a VGA and a DVI connector.
  I have the VGA hooked up to a Viewsonic 1920x1080 monitor, positioned
  above the laptop display.  I have a Samsung monitor to the right of
  the Viewsonic.  Since my laptop seems to only support two displays
  (which also seems true in Windows), I normally disable and totally
  ignore my laptop display, and may have papers propped up in front of
  it etc.

  Note that when I initially configured the third display I saw the
  following highly confusing behavior.  From Settings I tried to add a
  Samsung monitor to the right of the Viewsonic, via a DVI-to-HDMI
  passive connector, and got this dialog box when I hit "Apply":

     The selected configuration for displays could not be applied
     could not set the configuration for CRTC 65

  I clicked "OK" and got another dialog box:
     Failed to apply configuration: %s
     Can't add monitor: 
GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._gnome_2drr_2derror_2dquark.Code2:
 could not set the configuration for CRTC 65

  It works if I disable my laptop monitor, so it looks like the problem
  is with adding a third display.  I would think it would be a pretty
  common use case to use two nice external displays and disable the
  laptop display.

  Even when the hardware can't handle a third display, the error
  messages should not be so confusing, and the login process shouldn't
  result in the keyboard being mysteriously stolen by a dialog box on a
  display which may never be visible.

  This is on Trusty 64-bit, up-to-date with upgrades.

  This bug seems similar to bug 1304627, but it seemed cleanest to get
  all the right information reported via ubuntu-bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Jan  9 15:35:57 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Device [17aa:2203]
  InstallationDate: Installed on 2015-01-01 (8 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: LENOVO 343522U
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-43-generic 
root=UUID=6dce26c4-3d5b-4980-880e-06f249f77c57 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/22/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GCET96WW (2.56 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 343522U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGCET96WW(2.56):bd10/22/2013:svnLENOVO:pn343522U:pvrThinkPadX230Tablet:rvnLENOVO:rn343522U:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 343522U
  dmi.product.version: ThinkPad X230 Tablet
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11.3+14.04.20141104-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1~ubuntu1
  version.libgl1-mesa-dri: libgl1

[Touch-packages] [Bug 1604767] [NEW] PCI/internal sound card not detected

2016-07-20 Thread Bernhard Maechtel
Public bug reported:

Dummy Output
I have tried ALL fixes o the Ubuntu forums (one week now), nothing worked still 
have no sound.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: alsa-base 1.0.25+dfsg-0ubuntu4
ProcVersionSignature: Ubuntu 3.19.0-65.73~14.04.1-generic 3.19.8-ckt22
Uname: Linux 3.19.0-65-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: Unity
Date: Wed Jul 20 05:31:14 2016
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-trusty-amd64-osp1-20150720-0
InstallationDate: Installed on 2016-05-08 (73 days ago)
InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150720-04:06
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Title: PCI/internal sound card not detected
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/17/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.1.4
dmi.board.name: 0T99TM
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.4:bd01/17/2016:svnDellInc.:pnLatitude3470:pvr:rvnDellInc.:rn0T99TM:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude 3470
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug trusty

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

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Dummy Output
  I have tried ALL fixes o the Ubuntu forums (one week now), nothing worked 
still have no sound.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-65.73~14.04.1-generic 3.19.8-ckt22
  Uname: Linux 3.19.0-65-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Wed Jul 20 05:31:14 2016
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-osp1-20150720-0
  InstallationDate: Installed on 2016-05-08 (73 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150720-04:06
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/17/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.4
  dmi.board.name: 0T99TM
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.4:bd01/17/2016:svnDellInc.:pnLatitude3470:pvr:rvnDellInc.:rn0T99TM:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude 3470
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1604767/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1603525] [NEW] PCI/internal sound card not detected

2016-07-15 Thread Bernhard Maechtel
Public bug reported:

This morning (07/15/16) there was a kernel update from Canonical showing
up, after doing this update the sound was gone. I run Ubuntu 14.04, on a
pre-installed Dell Latitude 3470

bernhard@bernhard-Latitude-3470:~$ aplay -l
aplay: device_list:268: no soundcards found...


Audio device: Intel Corporation Device 9d70 (rev 21) Subsystem: Dell Device 06f2

Audio device: Intel Corporation Device 9d70 (rev 21)
Subsystem: Dell Device 06f2
Flags: fast devsel, IRQ 255
Memory at d122 (64-bit, non-prefetchable) [disabled] [size=16K]
Memory at d120 (64-bit, non-prefetchable) [disabled] [size=64K]
Capabilities: [50] Power Management version 3
Capabilities: [60] MSI: Enable- Count=1/1 Maskable- 64bit+


please let me know if you need more info since it's the first time I
report a Bug

Thank you

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: alsa-base 1.0.25+dfsg-0ubuntu4
ProcVersionSignature: Ubuntu 3.19.0-65.73~14.04.1-generic 3.19.8-ckt22
Uname: Linux 3.19.0-65-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: Unity
Date: Fri Jul 15 13:14:55 2016
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-trusty-amd64-osp1-20150720-0
InstallationDate: Installed on 2016-05-08 (68 days ago)
InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150720-04:06
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Title: PCI/internal sound card not detected
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/17/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.1.4
dmi.board.name: 0T99TM
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.4:bd01/17/2016:svnDellInc.:pnLatitude3470:pvr:rvnDellInc.:rn0T99TM:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude 3470
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug trusty

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

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  This morning (07/15/16) there was a kernel update from Canonical
  showing up, after doing this update the sound was gone. I run Ubuntu
  14.04, on a pre-installed Dell Latitude 3470

  bernhard@bernhard-Latitude-3470:~$ aplay -l
  aplay: device_list:268: no soundcards found...

  
  Audio device: Intel Corporation Device 9d70 (rev 21) Subsystem: Dell Device 
06f2

  Audio device: Intel Corporation Device 9d70 (rev 21)
Subsystem: Dell Device 06f2
Flags: fast devsel, IRQ 255
Memory at d122 (64-bit, non-prefetchable) [disabled] [size=16K]
Memory at d120 (64-bit, non-prefetchable) [disabled] [size=64K]
Capabilities: [50] Power Management version 3
Capabilities: [60] MSI: Enable- Count=1/1 Maskable- 64bit+


  please let me know if you need more info since it's the first time I
  report a Bug

  Thank you

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-65.73~14.04.1-generic 3.19.8-ckt22
  Uname: Linux 3.19.0-65-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Fri Jul 15 13:14:55 2016
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-osp1-20150720-0
  InstallationDate: Installed on 2016-05-08 (68 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150720-04:06
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/17/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.4
  dmi.board.name: 0T99TM
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.4:bd01/17/2016:svnDellInc.:pnLatitude3470:pvr:rvnDellInc.:rn0T99TM:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude 3470
  dmi.sys.vendor: Dell Inc.

To

[Touch-packages] [Bug 1562822] Re: Bluetooth Browse Files... not working

2016-05-18 Thread Huck-bernhard
I have install the fix and make a Test

1. Button "Browse File.." is removed in unity-control-center. But in Top Right 
Menu is it still visible. See on Image.
2. Send File is working now with LG L40

** Attachment added: "Bluetoth Browse file.png"
   
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1562822/+attachment/4665710/+files/Bluetoth%20Browse%20file.png

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-bluetooth in
Ubuntu.
https://bugs.launchpad.net/bugs/1562822

Title:
  Bluetooth Browse Files... not working

Status in OEM Priority Project:
  New
Status in indicator-bluetooth package in Ubuntu:
  In Progress
Status in unity-control-center package in Ubuntu:
  Fix Released
Status in indicator-bluetooth source package in Xenial:
  New
Status in unity-control-center source package in Xenial:
  Fix Committed

Bug description:
  * Impact
  The bluetooth settings include a non working "browse files..." items

  * Test case
  connect/pair a phone which does obex, open settings->bluetooth, the only 
action listed should be "send"

  * Regression potential
  none, it's removing a widget which was doing nothing

  --

  Mobile phone: LG L40 Android 4.4.2

  1. Connecting to Phone is successful shown.
  2. Click on Button  "Browse Files... " nothing happen.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity-control-center 15.04.0+16.04.20160315-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 28 13:31:39 2016
  ExecutablePath: /usr/bin/unity-control-center
  InstallationDate: Installed on 2016-02-04 (52 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160204)
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1562822/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1565130] [NEW] package ca-certificates 20160104ubuntu1 failed to install/upgrade: Trigger bilden eine Schleife, aufgegeben

2016-04-01 Thread Bernhard Nikola
Public bug reported:

update started in 16.04 / beta

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: ca-certificates 20160104ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
Uname: Linux 4.4.0-15-generic x86_64
ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
Date: Fri Apr  1 23:57:23 2016
ErrorMessage: Trigger bilden eine Schleife, aufgegeben
InstallationDate: Installed on 2016-02-22 (39 days ago)
InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160221)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1
 apt  1.2.9
SourcePackage: ca-certificates
Title: package ca-certificates 20160104ubuntu1 failed to install/upgrade: 
Trigger bilden eine Schleife, aufgegeben
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ca-certificates (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ca-certificates in Ubuntu.
https://bugs.launchpad.net/bugs/1565130

Title:
  package ca-certificates 20160104ubuntu1 failed to install/upgrade:
  Trigger bilden eine Schleife, aufgegeben

Status in ca-certificates package in Ubuntu:
  New

Bug description:
  update started in 16.04 / beta

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ca-certificates 20160104ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  Date: Fri Apr  1 23:57:23 2016
  ErrorMessage: Trigger bilden eine Schleife, aufgegeben
  InstallationDate: Installed on 2016-02-22 (39 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160221)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.9
  SourcePackage: ca-certificates
  Title: package ca-certificates 20160104ubuntu1 failed to install/upgrade: 
Trigger bilden eine Schleife, aufgegeben
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1565130/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1512956] Re: Update IBus to 1.5.11 on Wily

2015-11-12 Thread Bernhard
I have the Problem too.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1512956

Title:
  Update IBus to 1.5.11 on Wily

Status in ibus package in Ubuntu:
  In Progress

Bug description:
  newest release of Intellj IDEA does shows a warning:
  "IBus prior to 1.5.11 may cause input problems."

  that's why i request for an update of ibus to that version.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1302716] Re: webapp-container crashed with SIGABRT in qt_message_fatal()

2015-07-28 Thread Huck-bernhard
I found this workaround:

https://www.virtualbox.org/ticket/12738

~$ export LIBGL_ALWAYS_SOFTWARE=1 
~$ webbrowser-app

now i can start  webbrowser-app on Ubuntu 15.10 Alpha at Virtualbox 5.0

** Bug watch added: Virtualbox Trac #12738
   http://www.virtualbox.org/ticket/12738

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1302716

Title:
  webapp-container crashed with SIGABRT in qt_message_fatal()

Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  [Errors Bucket]
  https://errors.ubuntu.com/problem/04985f09fd55c083565c82ec0358799c46e5370b
  This is a regularly occurring problem.

  at install Lanchpad with Firefox webapp-container crashed

  ProblemType: CrashDistroRelease: Ubuntu 14.04
  Package: webapp-container 0.23+14.04.20140402-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
  Uname: Linux 3.13.0-8-generic i686
  ApportVersion: 2.14-0ubuntu1
  Architecture: i386
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Fri Apr  4 19:04:01 2014
  ExecutablePath: /usr/bin/webapp-container
  InstallationDate: Installed on 2014-02-14 (48 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20140214)
  ProcCmdline: webapp-container --app-id=Launchpadlaunchpadnet 
--webapp=TGF1bmNocGFk --enable-back-forward
  Signal: 6SourcePackage: webbrowser-app
  StacktraceTop:
   QMessageLogger::fatal(char const*, ...) const () from 
/usr/lib/i386-linux-gnu/libQt5Core.so.5
   ?? () from /usr/lib/i386-linux-gnu/qt5/plugins/platforms/libqxcb.so
   ?? () from /usr/lib/i386-linux-gnu/qt5/plugins/platforms/libqxcb.so
   QOpenGLContext::create() () from /usr/lib/i386-linux-gnu/libQt5Gui.so.5
   BrowserApplication::initialize(QString const&) ()
  Title: webapp-container crashed with SIGABRT in QMessageLogger::fatal()
  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/ubuntu/+source/webbrowser-app/+bug/1302716/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 124440] Re: [enhancement] Ubuntu needs a way to set mouse scrolling speed

2015-07-14 Thread Bernhard Zürn
Is it still gnome control center in unity ? Perhaps thsi "Bug" should go
into another project/tracker ? What are the Parameters to be changed, so
that we can write a small GUI-App to manage them ?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/124440

Title:
  [enhancement] Ubuntu needs a way to set mouse scrolling speed

Status in gnome-control-center:
  Unknown
Status in GTK+:
  Unknown
Status in One Hundred Papercuts:
  Triaged
Status in Mir:
  Triaged
Status in Unity:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in gtk+3.0 package in Ubuntu:
  Triaged

Bug description:
  This has been driving me nuts for a while now. The scroll wheel on my
  desktop mouse (it's an MS wireless optical mouse model 1008) scrolls
  rather fast. Instead of moving a few lines, it scrolls half a page or
  more with a very gentle scroll. The bluetooth mouse I use with my
  laptop does not do this so it's probably somewhat hardware specific.
  However, I'm wondering if there is a way to modify the speed or
  sensitivity. I found an answer here from about a year ago
  (https://answers.launchpad.net/ubuntu/+question/1339) that suggests
  there isn't a way but I'm wondering if anything has changed since
  then. I've also skimmed through synaptic but didn't see anything
  promising (like gsynaptic for touchpads).

  Thanks.

  See https://answers.launchpad.net/ubuntu/+question/9200 for more
  information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/124440/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1364522] Re: Firefox crashes sometimes when using webgl with nouveau driver

2015-07-11 Thread Bernhard Übelacker
For some reason the submission of new crashes at crash-stats.mozilla.com
was stopping at 2015-06-16.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1364522

Title:
  Firefox crashes sometimes when using webgl with nouveau driver

Status in firefox package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New

Bug description:
  Visiting with Firefox e.g.
  https://developer.mozilla.org/de/demos/detail/orange-slice/launch
  makes firefox crash.

  Program received signal SIGSEGV, Segmentation fault.
  nouveau_fence_next (screen=screen@entry=0x5a5a5a5a) at 
../../../../../../src/gallium/drivers/nouveau/nouveau_fence.c:226
  226if (screen->fence.current->state < NOUVEAU_FENCE_STATE_EMITTING)
  (gdb) bt
  #0  nouveau_fence_next (screen=screen@entry=0x5a5a5a5a) at 
../../../../../../src/gallium/drivers/nouveau/nouveau_fence.c:226
  #1  0x9b5b7fc0 in nv30_context_kick_notify (push=0x9b8f62b0) at 
../../../../../../src/gallium/drivers/nouveau/nv30/nv30_context.c:48
  #2  0xa0a0ea3e in pushbuf_submit (push=push@entry=0x9b8f62b0, chan=, chan=) at ../../nouveau/pushbuf.c:325
  #3  0xa0a0ed7a in pushbuf_flush (push=push@entry=0x9b8f62b0) at 
../../nouveau/pushbuf.c:402
  #4  0xa0a0faca in nouveau_pushbuf_kick (push=0x9b8f62b0, chan=0xa40c5420) at 
../../nouveau/pushbuf.c:774
  #5  0x9b5b811f in PUSH_KICK (push=) at 
../../../../../../src/gallium/drivers/nouveau/nouveau_winsys.h:56
  #6  nv30_context_flush (pipe=0x9b986000, fence=0x0, flags=0) at 
../../../../../../src/gallium/drivers/nouveau/nv30/nv30_context.c:83
  #7  0x9b4b4e1c in st_flush (st=st@entry=0x989e8000, fence=fence@entry=0x0, 
flags=flags@entry=0) at ../../../../src/mesa/state_tracker/st_cb_flush.c:87
  #8  0x9b4b4e82 in st_glFlush (ctx=0x98844000) at 
../../../../src/mesa/state_tracker/st_cb_flush.c:121
  #9  0x9b3b3065 in _mesa_flush (ctx=ctx@entry=0x98844000) at 
../../../../src/mesa/main/context.c:1691
  #10 0x9b3b3130 in _mesa_make_current (newCtx=newCtx@entry=0x0, 
drawBuffer=drawBuffer@entry=0x0, readBuffer=readBuffer@entry=0x0) at 
../../../../src/mesa/main/context.c:1503
  #11 0x9b4dee74 in st_api_make_current (stapi=0x9b779700 , 
stctxi=0x0, stdrawi=0x0, streadi=0x0) at 
../../../../src/mesa/state_tracker/st_manager.c:746
  #12 0x9b59d9ee in dri_unbind_context (cPriv=0x994e3120) at 
../../../../../../../src/gallium/state_trackers/dri/drm/dri_context.c:215
  #13 0x9b38db93 in driUnbindContext (pcp=0x994e3120) at 
../../../../../../../src/mesa/drivers/dri/common/dri_util.c:578
  #14 0x9b7df149 in dri2_unbind_context (context=0x9b9cbc20, new=0x0) at 
../../../../src/glx/dri2_glx.c:184
  #15 0x9b7b7985 in MakeContextCurrent (dpy=dpy@entry=0xb7191000, 
draw=draw@entry=0, read=read@entry=0, gc_user=gc_user@entry=0x0) at 
../../../../src/glx/glxcurrent.c:245
  #16 0x9b7b7a73 in glXMakeCurrent (dpy=0xb7191000, draw=0, gc=0x0) at 
../../../../src/glx/glxcurrent.c:293
  #17 0xb3d3916d in mozilla::gl::GLXLibrary::xMakeCurrent (this=0xb6e58470 
, display=0xb7191000, drawable=drawable@entry=0, 
context=context@entry=0x0) at 
/build/buildd/firefox-31.0+build1/gfx/gl/GLContextProviderGLX.cpp:525
  #18 0xb3d39d92 in mozilla::gl::GLContextGLX::~GLContextGLX (this=0x988dc800, 
__in_chrg=) at 
/build/buildd/firefox-31.0+build1/gfx/gl/GLContextProviderGLX.cpp:836
  #19 0xb3d39e12 in mozilla::gl::GLContextGLX::~GLContextGLX (this=0x988dc800, 
__in_chrg=) at 
/build/buildd/firefox-31.0+build1/gfx/gl/GLContextProviderGLX.cpp:845
  #20 0xb3d38ea0 in 
mozilla::detail::GenericRefCounted<(mozilla::detail::RefCountAtomicity)0>::Release
 (this=0x988dc800) at ../../dist/include/mozilla/GenericRefCounted.h:95
  #21 0xb3ddc635 in nsRefPtr::assign_assuming_AddRef 
(this=this@entry=0x9b8eb84c, newPtr=newPtr@entry=0x0) at 
../../dist/include/nsAutoPtr.h:882
  #22 0xb4561170 in assign_with_AddRef (rawPtr=0x0, this=0x9b8eb84c) at 
../../../dist/include/nsAutoPtr.h:866
  #23 operator= (rhs=0x0, this=0x9b8eb84c) at 
../../../dist/include/nsAutoPtr.h:964
  #24 mozilla::WebGLContext::DestroyResourcesAndContext 
(this=this@entry=0x9b8eb800) at 
/build/buildd/firefox-31.0+build1/content/canvas/src/WebGLContext.cpp:284
  #25 0xb45611bb in mozilla::WebGLContext::~WebGLContext (this=0x9b8eb800, 
__in_chrg=) at 
/build/buildd/firefox-31.0+build1/content/canvas/src/WebGLContext.cpp:203
  #26 0xb455e330 in mozilla::WebGL1Context::~WebGL1Context (this=0x9b8eb800, 
__in_chrg=) at 
/build/buildd/firefox-31.0+build1/content/canvas/src/WebGL1Context.cpp:25
  #27 0xb455ebe9 in mozilla::WebGLContext::DeleteCycleCollectable 
(this=0x9b8eb800) at 
/build/buildd/firefox-31.0+build1/content/canvas/src/WebGLContext.cpp:1397
  #28 0xb455ebbb in 
mozilla::WebGLContext::cycleCollection::DeleteCycleCollectable (this=0xb6e2b500 
, p=0x9b8eb800) at 
/build/buildd/firefox-31.0+build1/content/canvas/src/WebGLContext.h:152
  #29 0xb3841504 in SnowWhiteKiller::~SnowWhiteKiller 
(thi

[Touch-packages] [Bug 1421429] Re: [trusty] Frequently no clean shutdown or reboot

2015-06-13 Thread Bernhard
Unfortunately the problem is not gone completely , only not so frequent.

** Changed in: acpid (Ubuntu)
   Status: Fix Released => Confirmed

** Changed in: kde-workspace (Ubuntu)
   Status: Fix Released => Confirmed

** Changed in: upstart (Ubuntu)
   Status: Fix Released => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1421429

Title:
  [trusty] Frequently no clean shutdown or reboot

Status in acpid package in Ubuntu:
  Confirmed
Status in kde-workspace package in Ubuntu:
  Confirmed
Status in upstart package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  on all of my installations of Kubuntu 14.04.x (3 PCs), frequently on a
  shutdown or reboot the PC powers off or reboots without umounting the
  filesystems and terminating the processes.

  There is no message like "Terminating or killing all processes within x 
seconds, umounting filesystems, etc", but immediately the shutdown (power off) 
or reboot of the system, all via KDE. => No clean shutdown.
  (No network shares are mounted.)

  Next boot the fsck is recovering the filesystem/journal, etc

  This behaviour occurred  after the upgrade from 12.04.x to 14.04.x ,
  this was not in 12.04.

  Maybe it is a bug in upstart/systemd init scripts at reboot/shutdown.

  - Reproducible with:
  Download the iso image kubuntu-14.04.2-desktop-amd64.iso and install it, for 
instance as a Virtual Machine. 

  There logon in KDE and use the keyboard shortcut
  "ctl+alt+shift+pageup" (=Reboot) to reboot the machine several times
  until you can see that on the reboot/shutdown process there is no
  clean reboot, but an immediate reboot.

  On the next boot you will see that fsck is recovering the journal
  (inodes cleared/recovered), etc.

  
  Thank you for your support!

  Best regards, Bernhard

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: upstart 1.12.1-0ubuntu4.2
  ProcVersionSignature: Ubuntu 3.16.0-31.41~14.04.1-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Feb 12 22:40:45 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2010-06-02 (1716 days ago)
  InstallationMedia: Kubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427)
  SourcePackage: upstart
  UpgradeStatus: Upgraded to trusty on 2015-01-18 (25 days ago)
  UpstartBugCategory: Session
  UpstartRunningSessionCount: 1
  UpstartRunningSessionVersion: init (upstart 1.12.1)
  UpstartRunningSystemVersion: init (upstart 1.12.1)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1445613] [NEW] package util-linux 2.25.1-3ubuntu4.1 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück

2015-04-17 Thread Bernhard Nikola
Public bug reported:

update failed

ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: util-linux 2.25.1-3ubuntu4.1
ProcVersionSignature: Ubuntu 3.16.0-34.47-generic 3.16.7-ckt8
Uname: Linux 3.16.0-34-generic i686
ApportVersion: 2.14.7-0ubuntu8.3
Architecture: i386
Date: Fri Apr 17 20:37:34 2015
DuplicateSignature: package:util-linux:2.25.1-3ubuntu4.1:Unterprozess 
installiertes post-installation-Skript gab den Fehlerwert 1 zurück
ErrorMessage: Unterprozess installiertes post-installation-Skript gab den 
Fehlerwert 1 zurück
InstallationDate: Installed on 2015-04-11 (6 days ago)
InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Release i386 (20141022.1)
SourcePackage: util-linux
Title: package util-linux 2.25.1-3ubuntu4.1 failed to install/upgrade: 
Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: util-linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 utopic

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1445613

Title:
  package util-linux 2.25.1-3ubuntu4.1 failed to install/upgrade:
  Unterprozess installiertes post-installation-Skript gab den Fehlerwert
  1 zurück

Status in util-linux package in Ubuntu:
  New

Bug description:
  update failed

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: util-linux 2.25.1-3ubuntu4.1
  ProcVersionSignature: Ubuntu 3.16.0-34.47-generic 3.16.7-ckt8
  Uname: Linux 3.16.0-34-generic i686
  ApportVersion: 2.14.7-0ubuntu8.3
  Architecture: i386
  Date: Fri Apr 17 20:37:34 2015
  DuplicateSignature: package:util-linux:2.25.1-3ubuntu4.1:Unterprozess 
installiertes post-installation-Skript gab den Fehlerwert 1 zurück
  ErrorMessage: Unterprozess installiertes post-installation-Skript gab den 
Fehlerwert 1 zurück
  InstallationDate: Installed on 2015-04-11 (6 days ago)
  InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Release i386 (20141022.1)
  SourcePackage: util-linux
  Title: package util-linux 2.25.1-3ubuntu4.1 failed to install/upgrade: 
Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1445613/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1421429] Re: [trusty] Frequently no clean shutdown or reboot

2015-04-17 Thread Bernhard
The problem did not occur anymore, so I set this bug report to fixed. 
I don't know, which updates have solved this problem, but there were many 
updates regarding systemd, upstart, kernel updates, udev, etc .

** Changed in: kde-workspace (Ubuntu)
   Status: New => Fix Released

** Changed in: upstart (Ubuntu)
   Status: New => Fix Released

** Changed in: acpid (Ubuntu)
   Status: New => Fix Released

** Changed in: upstart (Ubuntu)
 Assignee: (unassigned) => Bernhard (baumber)

** Changed in: kde-workspace (Ubuntu)
 Assignee: (unassigned) => Bernhard (baumber)

** Changed in: acpid (Ubuntu)
 Assignee: (unassigned) => Bernhard (baumber)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1421429

Title:
  [trusty] Frequently no clean shutdown or reboot

Status in acpid package in Ubuntu:
  Fix Released
Status in kde-workspace package in Ubuntu:
  Fix Released
Status in upstart package in Ubuntu:
  Fix Released

Bug description:
  Hello,

  on all of my installations of Kubuntu 14.04.x (3 PCs), frequently on a
  shutdown or reboot the PC powers off or reboots without umounting the
  filesystems and terminating the processes.

  There is no message like "Terminating or killing all processes within x 
seconds, umounting filesystems, etc", but immediately the shutdown (power off) 
or reboot of the system, all via KDE. => No clean shutdown.
  (No network shares are mounted.)

  Next boot the fsck is recovering the filesystem/journal, etc

  This behaviour occurred  after the upgrade from 12.04.x to 14.04.x ,
  this was not in 12.04.

  Maybe it is a bug in upstart/systemd init scripts at reboot/shutdown.

  - Reproducible with:
  Download the iso image kubuntu-14.04.2-desktop-amd64.iso and install it, for 
instance as a Virtual Machine. 

  There logon in KDE and use the keyboard shortcut
  "ctl+alt+shift+pageup" (=Reboot) to reboot the machine several times
  until you can see that on the reboot/shutdown process there is no
  clean reboot, but an immediate reboot.

  On the next boot you will see that fsck is recovering the journal
  (inodes cleared/recovered), etc.

  
  Thank you for your support!

  Best regards, Bernhard

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: upstart 1.12.1-0ubuntu4.2
  ProcVersionSignature: Ubuntu 3.16.0-31.41~14.04.1-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Feb 12 22:40:45 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2010-06-02 (1716 days ago)
  InstallationMedia: Kubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427)
  SourcePackage: upstart
  UpgradeStatus: Upgraded to trusty on 2015-01-18 (25 days ago)
  UpstartBugCategory: Session
  UpstartRunningSessionCount: 1
  UpstartRunningSessionVersion: init (upstart 1.12.1)
  UpstartRunningSystemVersion: init (upstart 1.12.1)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1417658] Re: apparmor denied operation file_inherit from networkmanager when using HWE kernel

2015-04-01 Thread Bernhard
Tested packages: amd64
isc-dhcp-client  4.2.4-7ubuntu12.1
isc-dhcp-common   4.2.4-7ubuntu12.1

with kernels: amd64
vivid-lts  3.19.0-10.10
utopic-lts 3.16.0- 34.27

No "apparmor="DENIED" operation"-messages anymore => the patched
packages work.

Thank you for your support!
Best regards, Bernhard

** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1417658

Title:
  apparmor denied operation file_inherit from networkmanager when using
  HWE kernel

Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in isc-dhcp source package in Trusty:
  Fix Committed
Status in isc-dhcp source package in Vivid:
  Fix Released

Bug description:
  [Impact]
  AppArmor denials appear in dhclient when using using HWE kernel on 14.04. 
This can result in incorrect dhcp operation on client systems. The fix is to 
add these rules:
network inet dgram,
network inet6 dgram,

  to the dhclient profile for nm-dhcp-client.action and dhclient-script,
  like we did in 4.2.4-7ubuntu14.

  [Test Case]
  Install HWE kernel and use network manager to obtain an IP address.

  [Regression Potential]
  Extremely low since the update only adds access that dhclient didn't have.

  Original description:

  Hallo,

  on Kubuntu 14.04.x dmesg shows me the following apparmor messages;

  Is this normal or is this a security issue together with network-
  manager?

  [   16.171766] audit: type=1400 audit(1422595680.679:68): apparmor="DENIED" 
operation="file_inherit" 
profile="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=2229 
comm="nm-dhcp-client." lport=10320 family="inet" sock_type="dgram" protocol=17
  [   16.171772] audit: type=1400 audit(1422595680.679:69): apparmor="DENIED" 
operation="file_inherit" 
profile="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=2229 
comm="nm-dhcp-client." lport=21985 family="inet6" sock_type="dgram" protocol=17
  [   16.199936] audit: type=1400 audit(1422595680.707:70): apparmor="DENIED" 
operation="file_inherit" 
profile="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=2246 
comm="nm-dhcp-client." lport=10320 family="inet" sock_type="dgram" protocol=17
  [   16.199943] audit: type=1400 audit(1422595680.707:71): apparmor="DENIED" 
operation="file_inherit" 
profile="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=2246 
comm="nm-dhcp-client." lport=21985 family="inet6" sock_type="dgram" protocol=17
  [   16.201369] audit: type=1400 audit(1422595680.707:72): apparmor="DENIED" 
operation="file_inherit" 
profile="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=2248 
comm="nm-dhcp-client." lport=10320 family="inet" sock_type="dgram" protocol=17
  [   16.201379] audit: type=1400 audit(1422595680.707:73): apparmor="DENIED" 
operation="file_inherit" 
profile="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=2248 
comm="nm-dhcp-client." lport=21985 family="inet6" sock_type="dgram" protocol=17
  [   17.206342] audit: type=1400 audit(1422595681.711:74): apparmor="DENIED" 
operation="file_inherit" 
profile="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=2468 
comm="nm-dhcp-client." lport=10320 family="inet" sock_type="dgram" protocol=17
  [   17.206349] audit: type=1400 audit(1422595681.711:75): apparmor="DENIED" 
operation="file_inherit" 
profile="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=2468 
comm="nm-dhcp-client." lport=21985 family="inet6" sock_type="dgram" protocol=17

  When I logon to KDE, KDE hangs sometimes  for 3sec at the login-
  process , when there is no internet connection (DSL modem did not
  dial-in yet).

  Thanks for your help!
  Best regards, Bernhard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1417658/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1417658] Re: apparmor denied operation file_inherit from networkmanager when using HWE kernel

2015-03-31 Thread Bernhard
Thanks, I will test the patched package, as soon as it will land in
trusty-proposed.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1417658

Title:
  apparmor denied operation file_inherit from networkmanager when using
  HWE kernel

Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in isc-dhcp source package in Trusty:
  In Progress
Status in isc-dhcp source package in Vivid:
  Fix Released

Bug description:
  [Impact]
  AppArmor denials appear in dhclient when using using HWE kernel on 14.04. 
This can result in incorrect dhcp operation on client systems. The fix is to 
add these rules:
network inet dgram,
network inet6 dgram,

  to the dhclient profile for nm-dhcp-client.action and dhclient-script,
  like we did in 4.2.4-7ubuntu14.

  [Test Case]
  Install HWE kernel and use network manager to obtain an IP address.

  [Regression Potential]
  Extremely low since the update only adds access that dhclient didn't have.

  Original description:

  Hallo,

  on Kubuntu 14.04.x dmesg shows me the following apparmor messages;

  Is this normal or is this a security issue together with network-
  manager?

  [   16.171766] audit: type=1400 audit(1422595680.679:68): apparmor="DENIED" 
operation="file_inherit" 
profile="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=2229 
comm="nm-dhcp-client." lport=10320 family="inet" sock_type="dgram" protocol=17
  [   16.171772] audit: type=1400 audit(1422595680.679:69): apparmor="DENIED" 
operation="file_inherit" 
profile="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=2229 
comm="nm-dhcp-client." lport=21985 family="inet6" sock_type="dgram" protocol=17
  [   16.199936] audit: type=1400 audit(1422595680.707:70): apparmor="DENIED" 
operation="file_inherit" 
profile="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=2246 
comm="nm-dhcp-client." lport=10320 family="inet" sock_type="dgram" protocol=17
  [   16.199943] audit: type=1400 audit(1422595680.707:71): apparmor="DENIED" 
operation="file_inherit" 
profile="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=2246 
comm="nm-dhcp-client." lport=21985 family="inet6" sock_type="dgram" protocol=17
  [   16.201369] audit: type=1400 audit(1422595680.707:72): apparmor="DENIED" 
operation="file_inherit" 
profile="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=2248 
comm="nm-dhcp-client." lport=10320 family="inet" sock_type="dgram" protocol=17
  [   16.201379] audit: type=1400 audit(1422595680.707:73): apparmor="DENIED" 
operation="file_inherit" 
profile="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=2248 
comm="nm-dhcp-client." lport=21985 family="inet6" sock_type="dgram" protocol=17
  [   17.206342] audit: type=1400 audit(1422595681.711:74): apparmor="DENIED" 
operation="file_inherit" 
profile="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=2468 
comm="nm-dhcp-client." lport=10320 family="inet" sock_type="dgram" protocol=17
  [   17.206349] audit: type=1400 audit(1422595681.711:75): apparmor="DENIED" 
operation="file_inherit" 
profile="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=2468 
comm="nm-dhcp-client." lport=21985 family="inet6" sock_type="dgram" protocol=17

  When I logon to KDE, KDE hangs sometimes  for 3sec at the login-
  process , when there is no internet connection (DSL modem did not
  dial-in yet).

  Thanks for your help!
  Best regards, Bernhard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1417658/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1314549] Re: USB-headset undetected by Phonon

2015-03-20 Thread Bernhard
I have the same problem with a logitech usb headset.

It sometimes helps to disconnect the usb headset for 30 sec (dbus, phonon, udev 
check interval ??) . 
Then it is listed in the kmix dialog as e.g. headset #8 (it counts up the 
headset, although it is the same headset).  

I think, in the 14.04 release this phonon-/kde-version is buggy and changed 
also the behaviour of the phonon audio device handling.
=> This 30 sec check interval is not on 12.04 and the mixer of the headset 
comes back immediately after suspend or replug of the headset without counting 
up the headset label, "saying" it is a new device.

The KDE-team tried to fix the Master-Channel bugs, but introduced new
bugs and this in the end of the kde4 releases :-(

Furthermore I have to set the Master Channel again on both 12.04 and
14.04 after suspend or replug of the headset, because this never worked
automatically.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1314549

Title:
  USB-headset undetected by Phonon

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  A previously working USB-headset, which has been working flawlessly on 
Kubuntu 12.04 has ceased to work consistently on 14.04, whenever I try to 
connect it.
  While lsusb lists the device as being present and recognised, the Device 
Preference pane in the Audio and Video Settings of KDE keeps displaying the 
device in a greyed out state. In other words, it would appear that phonon 
thinks the device is still missing. Thus, it cannot be used.
  This problem occurs most of the times when I connect the headset to any USB 
port, even directly to the motherboard. Only rarely does Phonon wake up to the 
returned device.

  What I expected to happen was that, after the low-level handshake on the USB 
bus, Phonon would pop up a notification that it is switching to the headset 
because it´s higher on my preferences. (As it did consistently, prior to the 
upgrade from 12.04.)
  Instead, there is no announcement whatsoever. Also, the Select Master Channel 
window of KMix does not list the headset.

  I am running Kubuntu 14.04 LTS.
  The package is version 4:4.13.0-0ubuntu1, which is the current package 
available from the repositories.
  Please note that I am not entirely sure at this time wether kde-runtime is 
the correct package.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: kde-runtime 4:4.13.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: nvidia zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Apr 30 10:58:25 2014
  ExecutablePath: /usr/bin/kcmshell4
  InstallationDate: Installed on 2014-04-24 (5 days ago)
  InstallationMedia: Kubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 
(20140205)
  ProcEnviron:
   LANGUAGE=en_GB
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: kde-runtime
  UpgradeStatus: Upgraded to trusty on 2014-04-27 (2 days ago)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1421429] Re: [trusty] Frequently no clean shutdown or reboot

2015-02-21 Thread Bernhard
** Description changed:

  Hello,
  
  on all of my installations of Kubuntu 14.04.x (3 PCs), frequently on a
  shutdown or reboot the PC powers off or reboots without umounting the
  filesystems and terminating the processes.
  
  There is no message like "Terminating or killing all processes within x 
seconds, umounting filesystems, etc", but immediately the shutdown (power off) 
or reboot of the system, all via KDE. => No clean shutdown.
  (No network shares are mounted.)
  
  Next boot the fsck is recovering the filesystem/journal, etc
  
  This behaviour occurred  after the upgrade from 12.04.x to 14.04.x ,
  this was not in 12.04.
  
  Maybe it is a bug in upstart/systemd init scripts at reboot/shutdown.
+ 
+ - Reproducible with:
+ Download the iso image kubuntu-14.04.2-desktop-amd64.iso and install it, for 
instance as a Virtual Machine. 
+ 
+ There logon in KDE and use the keyboard shortcut "ctl+alt+shift+pageup"
+ (=Reboot) to reboot the machine several times until you can see that on
+ the reboot/shutdown process there is no clean reboot, but an immediate
+ reboot.
+ 
+ On the next boot you will see that fsck is recovering the journal
+ (inodes cleared/recovered), etc.
+ 
  
  Thank you for your support!
  
  Best regards, Bernhard
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: upstart 1.12.1-0ubuntu4.2
  ProcVersionSignature: Ubuntu 3.16.0-31.41~14.04.1-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Feb 12 22:40:45 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2010-06-02 (1716 days ago)
  InstallationMedia: Kubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427)
  SourcePackage: upstart
  UpgradeStatus: Upgraded to trusty on 2015-01-18 (25 days ago)
  UpstartBugCategory: Session
  UpstartRunningSessionCount: 1
  UpstartRunningSessionVersion: init (upstart 1.12.1)
  UpstartRunningSystemVersion: init (upstart 1.12.1)

** Also affects: kde-workspace (Ubuntu)
   Importance: Undecided
   Status: New

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

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

** Tags removed: third-party-packages
** Tags added: regression-release

** Tags added: systemd upstart

** Tags added: precise2trusty

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1421429

Title:
  [trusty] Frequently no clean shutdown or reboot

Status in acpid package in Ubuntu:
  New
Status in kde-workspace package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New
Status in upstart package in Ubuntu:
  New

Bug description:
  Hello,

  on all of my installations of Kubuntu 14.04.x (3 PCs), frequently on a
  shutdown or reboot the PC powers off or reboots without umounting the
  filesystems and terminating the processes.

  There is no message like "Terminating or killing all processes within x 
seconds, umounting filesystems, etc", but immediately the shutdown (power off) 
or reboot of the system, all via KDE. => No clean shutdown.
  (No network shares are mounted.)

  Next boot the fsck is recovering the filesystem/journal, etc

  This behaviour occurred  after the upgrade from 12.04.x to 14.04.x ,
  this was not in 12.04.

  Maybe it is a bug in upstart/systemd init scripts at reboot/shutdown.

  - Reproducible with:
  Download the iso image kubuntu-14.04.2-desktop-amd64.iso and install it, for 
instance as a Virtual Machine. 

  There logon in KDE and use the keyboard shortcut
  "ctl+alt+shift+pageup" (=Reboot) to reboot the machine several times
  until you can see that on the reboot/shutdown process there is no
  clean reboot, but an immediate reboot.

  On the next boot you will see that fsck is recovering the journal
  (inodes cleared/recovered), etc.

  
  Thank you for your support!

  Best regards, Bernhard

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: upstart 1.12.1-0ubuntu4.2
  ProcVersionSignature: Ubuntu 3.16.0-31.41~14.04.1-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Feb 12 22:40:45 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2010-06-02 (1716 days ago)
  InstallationMedia: Kubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427)
  SourcePackage: upstart
  UpgradeStatus: Upgraded to trusty on 2015-01-18 (25 days ago)
  UpstartBugCategory: Session
  UpstartRunningSessionCount: 1
  UpstartRunningSessionVersion: init (upstart 1.12.1)
  UpstartRunningSystemVersion: init (upstart 1.12.1)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Po

[Touch-packages] [Bug 1404696] Re: No vdpau for the utopic xstack in trusty

2015-02-17 Thread Bernhard
Any news regarding the missing decoder capabilities VC1_SIMPLE and
VC1_MAIN?

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1404696

Title:
  No vdpau for the utopic xstack in trusty

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I have tested the utopic xstack in trusty in the Canonical X Staging ppa 
  
https://launchpad.net/~canonical-x/+archive/ubuntu/x-staging?field.series_filter=trusty
 .

  It installs fine with;

  LC_ALL=C apt-get install -V libglapi-mesa-lts-utopic libgl1-mesa-glx-
  lts-utopic xserver-xorg-lts-utopic xserver-xorg-input-all-lts-utopic
  xserver-xorg-video-all-lts-utopic libgl1-mesa-dri-lts-utopic libglapi-
  mesa-lts-utopic:i386 libgl1-mesa-dri-lts-utopic:i386 libgl1-mesa-glx-
  lts-utopic:i386 libgles2-mesa-lts-utopic libglapi-mesa-lts-utopic
  mesa-vdpau-drivers-lts-utopic libegl1-mesa-drivers-lts-utopic
  libwayland-egl1-mesa-lts-utopic

  But under vdpauinfo there are no decoder capabilities for a AMD Radeon
  5550 (r600);

  Decoder capabilities:

  name   level macbs width height
  ---

  With stock xstack;

  Decoder capabilities:

  name   level macbs width height
  ---
  MPEG1 0  9216  2048  1152
  MPEG2_SIMPLE  3  9216  2048  1152
  MPEG2_MAIN3  9216  2048  1152
  H264_BASELINE41  9216  2048  1152
  H264_MAIN41  9216  2048  1152
  H264_HIGH41  9216  2048  1152
  VC1_SIMPLE1  9216  2048  1152
  VC1_MAIN  2  9216  2048  1152
  VC1_ADVANCED  4  9216  2048  1152

  The total output of vdpauinfo is attached.

  Best regards, Bernhard

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1421429] Re: [trusty] Frequently no clean shutdown or reboot

2015-02-15 Thread Bernhard
Frequency ~ every 5 - 10th shutdown/reboot

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1421429

Title:
  [trusty] Frequently no clean shutdown or reboot

Status in upstart package in Ubuntu:
  New

Bug description:
  Hello,

  on all of my installations of Kubuntu 14.04.x (3 PCs), frequently on a
  shutdown or reboot the PC powers off or reboots without umounting the
  filesystems and terminating the processes.

  There is no message like "Terminating or killing all processes within x 
seconds, umounting filesystems, etc", but immediately the shutdown (power off) 
or reboot of the system, all via KDE. => No clean shutdown.
  (No network shares are mounted.)

  Next boot the fsck is recovering the filesystem/journal, etc

  This behaviour occurred  after the upgrade from 12.04.x to 14.04.x ,
  this was not in 12.04.

  Maybe it is a bug in upstart/systemd init scripts at reboot/shutdown.

  Thank you for your support!

  Best regards, Bernhard

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: upstart 1.12.1-0ubuntu4.2
  ProcVersionSignature: Ubuntu 3.16.0-31.41~14.04.1-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Feb 12 22:40:45 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2010-06-02 (1716 days ago)
  InstallationMedia: Kubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427)
  SourcePackage: upstart
  UpgradeStatus: Upgraded to trusty on 2015-01-18 (25 days ago)
  UpstartBugCategory: Session
  UpstartRunningSessionCount: 1
  UpstartRunningSessionVersion: init (upstart 1.12.1)
  UpstartRunningSystemVersion: init (upstart 1.12.1)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1421429] Re: [trusty] Frequently no clean shutdown or reboot

2015-02-15 Thread Bernhard
I have tested this also with a fresh installation of 14.04

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1421429

Title:
  [trusty] Frequently no clean shutdown or reboot

Status in upstart package in Ubuntu:
  New

Bug description:
  Hello,

  on all of my installations of Kubuntu 14.04.x (3 PCs), frequently on a
  shutdown or reboot the PC powers off or reboots without umounting the
  filesystems and terminating the processes.

  There is no message like "Terminating or killing all processes within x 
seconds, umounting filesystems, etc", but immediately the shutdown (power off) 
or reboot of the system, all via KDE. => No clean shutdown.
  (No network shares are mounted.)

  Next boot the fsck is recovering the filesystem/journal, etc

  This behaviour occurred  after the upgrade from 12.04.x to 14.04.x ,
  this was not in 12.04.

  Maybe it is a bug in upstart/systemd init scripts at reboot/shutdown.

  Thank you for your support!

  Best regards, Bernhard

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: upstart 1.12.1-0ubuntu4.2
  ProcVersionSignature: Ubuntu 3.16.0-31.41~14.04.1-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Feb 12 22:40:45 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2010-06-02 (1716 days ago)
  InstallationMedia: Kubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427)
  SourcePackage: upstart
  UpgradeStatus: Upgraded to trusty on 2015-01-18 (25 days ago)
  UpstartBugCategory: Session
  UpstartRunningSessionCount: 1
  UpstartRunningSessionVersion: init (upstart 1.12.1)
  UpstartRunningSystemVersion: init (upstart 1.12.1)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1421429] Re: [trusty] Frequently no clean shutdown or reboot

2015-02-15 Thread Bernhard
The unclean shutdown/reboot is more often now, because I use the nouveau driver 
instead of the nvidia driver. 
But the nouveau driver does not support hibernate (suspend to disk) with my 
graphics card, so I have to shutdown/reboot normally.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1421429

Title:
  [trusty] Frequently no clean shutdown or reboot

Status in upstart package in Ubuntu:
  New

Bug description:
  Hello,

  on all of my installations of Kubuntu 14.04.x (3 PCs), frequently on a
  shutdown or reboot the PC powers off or reboots without umounting the
  filesystems and terminating the processes.

  There is no message like "Terminating or killing all processes within x 
seconds, umounting filesystems, etc", but immediately the shutdown (power off) 
or reboot of the system, all via KDE. => No clean shutdown.
  (No network shares are mounted.)

  Next boot the fsck is recovering the filesystem/journal, etc

  This behaviour occurred  after the upgrade from 12.04.x to 14.04.x ,
  this was not in 12.04.

  Maybe it is a bug in upstart/systemd init scripts at reboot/shutdown.

  Thank you for your support!

  Best regards, Bernhard

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: upstart 1.12.1-0ubuntu4.2
  ProcVersionSignature: Ubuntu 3.16.0-31.41~14.04.1-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Feb 12 22:40:45 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2010-06-02 (1716 days ago)
  InstallationMedia: Kubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427)
  SourcePackage: upstart
  UpgradeStatus: Upgraded to trusty on 2015-01-18 (25 days ago)
  UpstartBugCategory: Session
  UpstartRunningSessionCount: 1
  UpstartRunningSessionVersion: init (upstart 1.12.1)
  UpstartRunningSystemVersion: init (upstart 1.12.1)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1421429] Re: [trusty] Frequently no clean shutdown or reboot

2015-02-13 Thread Bernhard
** Summary changed:

- [trusty] Occasionally no clean shutdown or reboot
+ [trusty] Frequently no clean shutdown or reboot

** Description changed:

  Hello,
  
- on all of my installations of Kubuntu 14.04.x (3 PCs), occasionally on a
+ on all of my installations of Kubuntu 14.04.x (3 PCs), frequently on a
  shutdown or reboot the PC powers off or reboots without umounting the
  filesystems and terminating the processes.
  
  There is no message like "Terminating or killing all processes within x 
seconds, umounting filesystems, etc", but immediately the shutdown (power off) 
or reboot of the system, all via KDE. => No clean shutdown.
  (No network shares are mounted.)
  
  Next boot the fsck is recovering the filesystem/journal, etc
  
  This behaviour occurred  after the upgrade from 12.04.x to 14.04.x ,
  this was not in 12.04.
  
  Maybe it is a bug in upstart/systemd init scripts at reboot/shutdown.
  
  Thank you for your support!
  
  Best regards, Bernhard
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: upstart 1.12.1-0ubuntu4.2
  ProcVersionSignature: Ubuntu 3.16.0-31.41~14.04.1-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Feb 12 22:40:45 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2010-06-02 (1716 days ago)
  InstallationMedia: Kubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427)
  SourcePackage: upstart
  UpgradeStatus: Upgraded to trusty on 2015-01-18 (25 days ago)
  UpstartBugCategory: Session
  UpstartRunningSessionCount: 1
  UpstartRunningSessionVersion: init (upstart 1.12.1)
  UpstartRunningSystemVersion: init (upstart 1.12.1)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1421429

Title:
  [trusty] Frequently no clean shutdown or reboot

Status in upstart package in Ubuntu:
  New

Bug description:
  Hello,

  on all of my installations of Kubuntu 14.04.x (3 PCs), frequently on a
  shutdown or reboot the PC powers off or reboots without umounting the
  filesystems and terminating the processes.

  There is no message like "Terminating or killing all processes within x 
seconds, umounting filesystems, etc", but immediately the shutdown (power off) 
or reboot of the system, all via KDE. => No clean shutdown.
  (No network shares are mounted.)

  Next boot the fsck is recovering the filesystem/journal, etc

  This behaviour occurred  after the upgrade from 12.04.x to 14.04.x ,
  this was not in 12.04.

  Maybe it is a bug in upstart/systemd init scripts at reboot/shutdown.

  Thank you for your support!

  Best regards, Bernhard

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: upstart 1.12.1-0ubuntu4.2
  ProcVersionSignature: Ubuntu 3.16.0-31.41~14.04.1-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Feb 12 22:40:45 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2010-06-02 (1716 days ago)
  InstallationMedia: Kubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427)
  SourcePackage: upstart
  UpgradeStatus: Upgraded to trusty on 2015-01-18 (25 days ago)
  UpstartBugCategory: Session
  UpstartRunningSessionCount: 1
  UpstartRunningSessionVersion: init (upstart 1.12.1)
  UpstartRunningSystemVersion: init (upstart 1.12.1)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1421429] Re: [trusty] Occasionally no clean shutdown or reboot

2015-02-12 Thread Bernhard
And there are no error messages in the logs (syslog and upstart logs).

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1421429

Title:
  [trusty] Occasionally no clean shutdown or reboot

Status in upstart package in Ubuntu:
  New

Bug description:
  Hello,

  on all of my installations of Kubuntu 14.04.x (3 PCs), occasionally on
  a shutdown or reboot the PC powers off or reboots without umounting
  the filesystems and terminating the processes.

  There is no message like "Terminating or killing all processes within x 
seconds, umounting filesystems, etc", but immediately the shutdown (power off) 
or reboot of the system, all via KDE. => No clean shutdown.
  (No network shares are mounted.)

  Next boot the fsck is recovering the filesystem/journal, etc

  This behaviour occurred  after the upgrade from 12.04.x to 14.04.x ,
  this was not in 12.04.

  Maybe it is a bug in upstart/systemd init scripts at reboot/shutdown.

  Thank you for your support!

  Best regards, Bernhard

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: upstart 1.12.1-0ubuntu4.2
  ProcVersionSignature: Ubuntu 3.16.0-31.41~14.04.1-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Feb 12 22:40:45 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2010-06-02 (1716 days ago)
  InstallationMedia: Kubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427)
  SourcePackage: upstart
  UpgradeStatus: Upgraded to trusty on 2015-01-18 (25 days ago)
  UpstartBugCategory: Session
  UpstartRunningSessionCount: 1
  UpstartRunningSessionVersion: init (upstart 1.12.1)
  UpstartRunningSystemVersion: init (upstart 1.12.1)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1421429] [NEW] [trusty] Occasionally no clean shutdown or reboot

2015-02-12 Thread Bernhard
Public bug reported:

Hello,

on all of my installations of Kubuntu 14.04.x (3 PCs), occasionally on a
shutdown or reboot the PC powers off or reboots without umounting the
filesystems and terminating the processes.

There is no message like "Terminating or killing all processes within x 
seconds, umounting filesystems, etc", but immediately the shutdown (power off) 
or reboot of the system, all via KDE. => No clean shutdown.
(No network shares are mounted.)

Next boot the fsck is recovering the filesystem/journal, etc

This behaviour occurred  after the upgrade from 12.04.x to 14.04.x ,
this was not in 12.04.

Maybe it is a bug in upstart/systemd init scripts at reboot/shutdown.

Thank you for your support!

Best regards, Bernhard

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: upstart 1.12.1-0ubuntu4.2
ProcVersionSignature: Ubuntu 3.16.0-31.41~14.04.1-generic 3.16.7-ckt5
Uname: Linux 3.16.0-31-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
CurrentDesktop: KDE
Date: Thu Feb 12 22:40:45 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2010-06-02 (1716 days ago)
InstallationMedia: Kubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427)
SourcePackage: upstart
UpgradeStatus: Upgraded to trusty on 2015-01-18 (25 days ago)
UpstartBugCategory: Session
UpstartRunningSessionCount: 1
UpstartRunningSessionVersion: init (upstart 1.12.1)
UpstartRunningSystemVersion: init (upstart 1.12.1)

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


** Tags: amd64 apport-bug third-party-packages trusty

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1421429

Title:
  [trusty] Occasionally no clean shutdown or reboot

Status in upstart package in Ubuntu:
  New

Bug description:
  Hello,

  on all of my installations of Kubuntu 14.04.x (3 PCs), occasionally on
  a shutdown or reboot the PC powers off or reboots without umounting
  the filesystems and terminating the processes.

  There is no message like "Terminating or killing all processes within x 
seconds, umounting filesystems, etc", but immediately the shutdown (power off) 
or reboot of the system, all via KDE. => No clean shutdown.
  (No network shares are mounted.)

  Next boot the fsck is recovering the filesystem/journal, etc

  This behaviour occurred  after the upgrade from 12.04.x to 14.04.x ,
  this was not in 12.04.

  Maybe it is a bug in upstart/systemd init scripts at reboot/shutdown.

  Thank you for your support!

  Best regards, Bernhard

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: upstart 1.12.1-0ubuntu4.2
  ProcVersionSignature: Ubuntu 3.16.0-31.41~14.04.1-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Feb 12 22:40:45 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2010-06-02 (1716 days ago)
  InstallationMedia: Kubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427)
  SourcePackage: upstart
  UpgradeStatus: Upgraded to trusty on 2015-01-18 (25 days ago)
  UpstartBugCategory: Session
  UpstartRunningSessionCount: 1
  UpstartRunningSessionVersion: init (upstart 1.12.1)
  UpstartRunningSystemVersion: init (upstart 1.12.1)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1417658] [NEW] apparmor denied operation file_inherit from networkmanager

2015-02-03 Thread Bernhard
Public bug reported:

Hallo,

on Kubuntu 14.04.x dmesg shows me the following apparmor messages;

Is this normal or is this a security issue together with network-
manager?

[   16.171766] audit: type=1400 audit(1422595680.679:68): apparmor="DENIED" 
operation="file_inherit" 
profile="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=2229 
comm="nm-dhcp-client." lport=10320 family="inet" sock_type="dgram" protocol=17
[   16.171772] audit: type=1400 audit(1422595680.679:69): apparmor="DENIED" 
operation="file_inherit" 
profile="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=2229 
comm="nm-dhcp-client." lport=21985 family="inet6" sock_type="dgram" protocol=17
[   16.199936] audit: type=1400 audit(1422595680.707:70): apparmor="DENIED" 
operation="file_inherit" 
profile="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=2246 
comm="nm-dhcp-client." lport=10320 family="inet" sock_type="dgram" protocol=17
[   16.199943] audit: type=1400 audit(1422595680.707:71): apparmor="DENIED" 
operation="file_inherit" 
profile="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=2246 
comm="nm-dhcp-client." lport=21985 family="inet6" sock_type="dgram" protocol=17
[   16.201369] audit: type=1400 audit(1422595680.707:72): apparmor="DENIED" 
operation="file_inherit" 
profile="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=2248 
comm="nm-dhcp-client." lport=10320 family="inet" sock_type="dgram" protocol=17
[   16.201379] audit: type=1400 audit(1422595680.707:73): apparmor="DENIED" 
operation="file_inherit" 
profile="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=2248 
comm="nm-dhcp-client." lport=21985 family="inet6" sock_type="dgram" protocol=17
[   17.206342] audit: type=1400 audit(1422595681.711:74): apparmor="DENIED" 
operation="file_inherit" 
profile="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=2468 
comm="nm-dhcp-client." lport=10320 family="inet" sock_type="dgram" protocol=17
[   17.206349] audit: type=1400 audit(1422595681.711:75): apparmor="DENIED" 
operation="file_inherit" 
profile="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=2468 
comm="nm-dhcp-client." lport=21985 family="inet6" sock_type="dgram" protocol=17

When I logon to KDE, KDE hangs sometimes  for 3sec at the login-process
, when there is no internet connection (DSL modem did not dial-in yet).

Thanks for your help!
Best regards, Bernhard

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


** Tags: 14.04 apparmor networkmanager trusty

** Tags added: 14.04 apparmor manager network trusty

** Tags removed: manager network
** Tags added: networkmanager

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1417658

Title:
  apparmor denied operation file_inherit from networkmanager

Status in apparmor package in Ubuntu:
  New

Bug description:
  Hallo,

  on Kubuntu 14.04.x dmesg shows me the following apparmor messages;

  Is this normal or is this a security issue together with network-
  manager?

  [   16.171766] audit: type=1400 audit(1422595680.679:68): apparmor="DENIED" 
operation="file_inherit" 
profile="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=2229 
comm="nm-dhcp-client." lport=10320 family="inet" sock_type="dgram" protocol=17
  [   16.171772] audit: type=1400 audit(1422595680.679:69): apparmor="DENIED" 
operation="file_inherit" 
profile="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=2229 
comm="nm-dhcp-client." lport=21985 family="inet6" sock_type="dgram" protocol=17
  [   16.199936] audit: type=1400 audit(1422595680.707:70): apparmor="DENIED" 
operation="file_inherit" 
profile="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=2246 
comm="nm-dhcp-client." lport=10320 family="inet" sock_type="dgram" protocol=17
  [   16.199943] audit: type=1400 audit(1422595680.707:71): apparmor="DENIED" 
operation="file_inherit" 
profile="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=2246 
comm="nm-dhcp-client." lport=21985 family="inet6" sock_type="dgram" protocol=17
  [   16.201369] audit: type=1400 audit(1422595680.707:72): apparmor="DENIED" 
operation="file_inherit" 
profile="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=2248 

[Touch-packages] [Bug 1404696] Re: No vdpau for the utopic xstack in trusty

2015-01-24 Thread Bernhard
Thanks, now the decoder capabilities are shown (see the attachment), but
two entries are missing;

--- Missing:

VC1_SIMPLE1  9216  2048  1152
VC1_MAIN  2  9216  2048  1152


** Attachment added: "vdpauinfo with the patched utopic xstack"
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1404696/+attachment/4304784/+files/vdpau_1404_utopic_new.txt

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1404696

Title:
  No vdpau for the utopic xstack in trusty

Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  I have tested the utopic xstack in trusty in the Canonical X Staging ppa 
  
https://launchpad.net/~canonical-x/+archive/ubuntu/x-staging?field.series_filter=trusty
 .

  It installs fine with;

  LC_ALL=C apt-get install -V libglapi-mesa-lts-utopic libgl1-mesa-glx-
  lts-utopic xserver-xorg-lts-utopic xserver-xorg-input-all-lts-utopic
  xserver-xorg-video-all-lts-utopic libgl1-mesa-dri-lts-utopic libglapi-
  mesa-lts-utopic:i386 libgl1-mesa-dri-lts-utopic:i386 libgl1-mesa-glx-
  lts-utopic:i386 libgles2-mesa-lts-utopic libglapi-mesa-lts-utopic
  mesa-vdpau-drivers-lts-utopic libegl1-mesa-drivers-lts-utopic
  libwayland-egl1-mesa-lts-utopic

  But under vdpauinfo there are no decoder capabilities for a AMD Radeon
  5550 (r600);

  Decoder capabilities:

  name   level macbs width height
  ---

  With stock xstack;

  Decoder capabilities:

  name   level macbs width height
  ---
  MPEG1 0  9216  2048  1152
  MPEG2_SIMPLE  3  9216  2048  1152
  MPEG2_MAIN3  9216  2048  1152
  H264_BASELINE41  9216  2048  1152
  H264_MAIN41  9216  2048  1152
  H264_HIGH41  9216  2048  1152
  VC1_SIMPLE1  9216  2048  1152
  VC1_MAIN  2  9216  2048  1152
  VC1_ADVANCED  4  9216  2048  1152

  The total output of vdpauinfo is attached.

  Best regards, Bernhard

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1392829] Re: bluez-test-discovery ERROR:dbus.connection:Exception

2014-11-15 Thread Huck-bernhard
addition:

if you call bluez-test-discovery few  times stops discoverry of devices  
complete.
I can see a similar behavior at StartDiscovery  with DBUS "org.bluez.Adapter" 
with QT5 and QDBusInterface
after connecting a device and disconnect because of distance device to long is 
Discovery also stopt. 
after calling: "hciconfig reset"  is Discovery working again.
this error is only at Ubuntu 14.10. with 14.04 is it working

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1392829

Title:
  bluez-test-discovery ERROR:dbus.connection:Exception

Status in “bluez” package in Ubuntu:
  New

Bug description:
  ~$ bluez-test-discovery 
  [ 50:85:69:EF:9B:23 ]
  Trusted = 0
  Class = 0x08043c
  ERROR:dbus.connection:Exception in handler for D-Bus signal:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/dbus/connection.py", line 230, in 
maybe_handle_message
  self._handler(*args, **kwargs)
File "/usr/bin/bluez-test-discovery", line 15, in device_found
  value = unicode(value).encode('ascii', 'replace')
  NameError: name 'unicode' is not defined

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: bluez 4.101-0ubuntu20
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Nov 14 19:24:49 2014
  InstallationDate: Installed on 2014-11-14 (0 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  InterestingModules: btusb rfcomm bnep bluetooth
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 004: ID 0b05:17cb ASUSTek Computer, Inc. 
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic 
root=UUID=22d86bc8-8f82-4594-8e4b-10cd3b3ed488 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 00:02:72:CD:03:2A  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN 
RX bytes:1318 acl:0 sco:0 events:55 errors:0
TX bytes:1016 acl:0 sco:0 commands:47 errors:0
  rfkill:
   1: hci0: Bluetooth
Soft blocked: no
Hard blocked: no

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1392829] Re: bluez-test-discovery ERROR:dbus.connection:Exception

2014-11-14 Thread Huck-bernhard
this error is only at Ubuntu 14.10 at 14.04 is it working

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1392829

Title:
  bluez-test-discovery ERROR:dbus.connection:Exception

Status in “bluez” package in Ubuntu:
  New

Bug description:
  ~$ bluez-test-discovery 
  [ 50:85:69:EF:9B:23 ]
  Trusted = 0
  Class = 0x08043c
  ERROR:dbus.connection:Exception in handler for D-Bus signal:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/dbus/connection.py", line 230, in 
maybe_handle_message
  self._handler(*args, **kwargs)
File "/usr/bin/bluez-test-discovery", line 15, in device_found
  value = unicode(value).encode('ascii', 'replace')
  NameError: name 'unicode' is not defined

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: bluez 4.101-0ubuntu20
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Nov 14 19:24:49 2014
  InstallationDate: Installed on 2014-11-14 (0 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  InterestingModules: btusb rfcomm bnep bluetooth
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 004: ID 0b05:17cb ASUSTek Computer, Inc. 
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic 
root=UUID=22d86bc8-8f82-4594-8e4b-10cd3b3ed488 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 00:02:72:CD:03:2A  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN 
RX bytes:1318 acl:0 sco:0 events:55 errors:0
TX bytes:1016 acl:0 sco:0 commands:47 errors:0
  rfkill:
   1: hci0: Bluetooth
Soft blocked: no
Hard blocked: no

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1392829] [NEW] bluez-test-discovery ERROR:dbus.connection:Exception

2014-11-14 Thread Huck-bernhard
Public bug reported:

~$ bluez-test-discovery 
[ 50:85:69:EF:9B:23 ]
Trusted = 0
Class = 0x08043c
ERROR:dbus.connection:Exception in handler for D-Bus signal:
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/dbus/connection.py", line 230, in 
maybe_handle_message
self._handler(*args, **kwargs)
  File "/usr/bin/bluez-test-discovery", line 15, in device_found
value = unicode(value).encode('ascii', 'replace')
NameError: name 'unicode' is not defined

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: bluez 4.101-0ubuntu20
ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
Uname: Linux 3.16.0-24-generic x86_64
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Nov 14 19:24:49 2014
InstallationDate: Installed on 2014-11-14 (0 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
InterestingModules: btusb rfcomm bnep bluetooth
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 004: ID 0b05:17cb ASUSTek Computer, Inc. 
 Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic 
root=UUID=22d86bc8-8f82-4594-8e4b-10cd3b3ed488 ro quiet splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH
hciconfig:
 hci0:  Type: BR/EDR  Bus: USB
BD Address: 00:02:72:CD:03:2A  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN 
RX bytes:1318 acl:0 sco:0 events:55 errors:0
TX bytes:1016 acl:0 sco:0 commands:47 errors:0
rfkill:
 1: hci0: Bluetooth
Soft blocked: no
Hard blocked: no

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


** Tags: amd64 apport-bug utopic

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1392829

Title:
  bluez-test-discovery ERROR:dbus.connection:Exception

Status in “bluez” package in Ubuntu:
  New

Bug description:
  ~$ bluez-test-discovery 
  [ 50:85:69:EF:9B:23 ]
  Trusted = 0
  Class = 0x08043c
  ERROR:dbus.connection:Exception in handler for D-Bus signal:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/dbus/connection.py", line 230, in 
maybe_handle_message
  self._handler(*args, **kwargs)
File "/usr/bin/bluez-test-discovery", line 15, in device_found
  value = unicode(value).encode('ascii', 'replace')
  NameError: name 'unicode' is not defined

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: bluez 4.101-0ubuntu20
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Nov 14 19:24:49 2014
  InstallationDate: Installed on 2014-11-14 (0 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  InterestingModules: btusb rfcomm bnep bluetooth
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 004: ID 0b05:17cb ASUSTek Computer, Inc. 
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic 
root=UUID=22d86bc8-8f82-4594-8e4b-10cd3b3ed488 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 00:02:72:CD:03:2A  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN 
RX bytes:1318 acl:0 sco:0 events:55 errors:0
TX bytes:1016 acl:0 sco:0 commands:47 errors:0
  rfkill:
   1: hci0: Bluetooth
Soft blocked: no

[Touch-packages] [Bug 1364522] Re: Firefox crashes sometimes when using webgl with nouveau driver

2014-10-04 Thread Bernhard Übelacker
** Also affects: firefox (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1364522

Title:
  Firefox crashes sometimes when using webgl with nouveau driver

Status in “firefox” package in Ubuntu:
  New
Status in “mesa” package in Ubuntu:
  New

Bug description:
  Visiting with Firefox e.g.
  https://developer.mozilla.org/de/demos/detail/orange-slice/launch
  makes firefox crash.

  Program received signal SIGSEGV, Segmentation fault.
  nouveau_fence_next (screen=screen@entry=0x5a5a5a5a) at 
../../../../../../src/gallium/drivers/nouveau/nouveau_fence.c:226
  226if (screen->fence.current->state < NOUVEAU_FENCE_STATE_EMITTING)
  (gdb) bt
  #0  nouveau_fence_next (screen=screen@entry=0x5a5a5a5a) at 
../../../../../../src/gallium/drivers/nouveau/nouveau_fence.c:226
  #1  0x9b5b7fc0 in nv30_context_kick_notify (push=0x9b8f62b0) at 
../../../../../../src/gallium/drivers/nouveau/nv30/nv30_context.c:48
  #2  0xa0a0ea3e in pushbuf_submit (push=push@entry=0x9b8f62b0, chan=, chan=) at ../../nouveau/pushbuf.c:325
  #3  0xa0a0ed7a in pushbuf_flush (push=push@entry=0x9b8f62b0) at 
../../nouveau/pushbuf.c:402
  #4  0xa0a0faca in nouveau_pushbuf_kick (push=0x9b8f62b0, chan=0xa40c5420) at 
../../nouveau/pushbuf.c:774
  #5  0x9b5b811f in PUSH_KICK (push=) at 
../../../../../../src/gallium/drivers/nouveau/nouveau_winsys.h:56
  #6  nv30_context_flush (pipe=0x9b986000, fence=0x0, flags=0) at 
../../../../../../src/gallium/drivers/nouveau/nv30/nv30_context.c:83
  #7  0x9b4b4e1c in st_flush (st=st@entry=0x989e8000, fence=fence@entry=0x0, 
flags=flags@entry=0) at ../../../../src/mesa/state_tracker/st_cb_flush.c:87
  #8  0x9b4b4e82 in st_glFlush (ctx=0x98844000) at 
../../../../src/mesa/state_tracker/st_cb_flush.c:121
  #9  0x9b3b3065 in _mesa_flush (ctx=ctx@entry=0x98844000) at 
../../../../src/mesa/main/context.c:1691
  #10 0x9b3b3130 in _mesa_make_current (newCtx=newCtx@entry=0x0, 
drawBuffer=drawBuffer@entry=0x0, readBuffer=readBuffer@entry=0x0) at 
../../../../src/mesa/main/context.c:1503
  #11 0x9b4dee74 in st_api_make_current (stapi=0x9b779700 , 
stctxi=0x0, stdrawi=0x0, streadi=0x0) at 
../../../../src/mesa/state_tracker/st_manager.c:746
  #12 0x9b59d9ee in dri_unbind_context (cPriv=0x994e3120) at 
../../../../../../../src/gallium/state_trackers/dri/drm/dri_context.c:215
  #13 0x9b38db93 in driUnbindContext (pcp=0x994e3120) at 
../../../../../../../src/mesa/drivers/dri/common/dri_util.c:578
  #14 0x9b7df149 in dri2_unbind_context (context=0x9b9cbc20, new=0x0) at 
../../../../src/glx/dri2_glx.c:184
  #15 0x9b7b7985 in MakeContextCurrent (dpy=dpy@entry=0xb7191000, 
draw=draw@entry=0, read=read@entry=0, gc_user=gc_user@entry=0x0) at 
../../../../src/glx/glxcurrent.c:245
  #16 0x9b7b7a73 in glXMakeCurrent (dpy=0xb7191000, draw=0, gc=0x0) at 
../../../../src/glx/glxcurrent.c:293
  #17 0xb3d3916d in mozilla::gl::GLXLibrary::xMakeCurrent (this=0xb6e58470 
, display=0xb7191000, drawable=drawable@entry=0, 
context=context@entry=0x0) at 
/build/buildd/firefox-31.0+build1/gfx/gl/GLContextProviderGLX.cpp:525
  #18 0xb3d39d92 in mozilla::gl::GLContextGLX::~GLContextGLX (this=0x988dc800, 
__in_chrg=) at 
/build/buildd/firefox-31.0+build1/gfx/gl/GLContextProviderGLX.cpp:836
  #19 0xb3d39e12 in mozilla::gl::GLContextGLX::~GLContextGLX (this=0x988dc800, 
__in_chrg=) at 
/build/buildd/firefox-31.0+build1/gfx/gl/GLContextProviderGLX.cpp:845
  #20 0xb3d38ea0 in 
mozilla::detail::GenericRefCounted<(mozilla::detail::RefCountAtomicity)0>::Release
 (this=0x988dc800) at ../../dist/include/mozilla/GenericRefCounted.h:95
  #21 0xb3ddc635 in nsRefPtr::assign_assuming_AddRef 
(this=this@entry=0x9b8eb84c, newPtr=newPtr@entry=0x0) at 
../../dist/include/nsAutoPtr.h:882
  #22 0xb4561170 in assign_with_AddRef (rawPtr=0x0, this=0x9b8eb84c) at 
../../../dist/include/nsAutoPtr.h:866
  #23 operator= (rhs=0x0, this=0x9b8eb84c) at 
../../../dist/include/nsAutoPtr.h:964
  #24 mozilla::WebGLContext::DestroyResourcesAndContext 
(this=this@entry=0x9b8eb800) at 
/build/buildd/firefox-31.0+build1/content/canvas/src/WebGLContext.cpp:284
  #25 0xb45611bb in mozilla::WebGLContext::~WebGLContext (this=0x9b8eb800, 
__in_chrg=) at 
/build/buildd/firefox-31.0+build1/content/canvas/src/WebGLContext.cpp:203
  #26 0xb455e330 in mozilla::WebGL1Context::~WebGL1Context (this=0x9b8eb800, 
__in_chrg=) at 
/build/buildd/firefox-31.0+build1/content/canvas/src/WebGL1Context.cpp:25
  #27 0xb455ebe9 in mozilla::WebGLContext::DeleteCycleCollectable 
(this=0x9b8eb800) at 
/build/buildd/firefox-31.0+build1/content/canvas/src/WebGLContext.cpp:1397
  #28 0xb455ebbb in 
mozilla::WebGLContext::cycleCollection::DeleteCycleCollectable (this=0xb6e2b500 
, p=0x9b8eb800) at 
/build/buildd/firefox-31.0+build1/content/canvas/src/WebGLContext.h:152
  #29 0xb3841504 in SnowWhiteKiller::~SnowWhiteKiller 
(this=this@entry=0xbfb4

[Touch-packages] [Bug 1044549] Re: The "Access Prompt" randomly pop up!

2014-09-24 Thread Bernhard Schülke
@alcachi: Thanks, it helps. :-)
@Shahar: /home/user/.config/goa-1.0/accounts.config

user: Your username.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gcr in Ubuntu.
https://bugs.launchpad.net/bugs/1044549

Title:
  The "Access Prompt" randomly pop up!

Status in “gcr” package in Ubuntu:
  Triaged

Bug description:
  Access Prompt randomly pop up and prompt you for the password. Have you ever 
when opened  Youtube, Facebook, Launchpad account!n And now opened a picture of 
the computer when  pop up"Access Prompt"
  I use autologin.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: gcr 3.5.90-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3
  Uname: Linux 3.5.0-13-generic x86_64
  ApportVersion: 2.5.1-0ubuntu4
  Architecture: amd64
  Date: Fri Aug 31 22:33:44 2012
  ExecutablePath: /usr/lib/gcr/gcr-prompter
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120724.2)
  SourcePackage: gcr
  UpgradeStatus: No upgrade log present (probably fresh install)
  XsessionErrors:
   (gnome-settings-daemon:1401): libappindicator-WARNING **: Unable to connect 
to the Notification Watcher: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name :1.48 was not 
provided by any .service files
   (gnome-control-center:2016): background-cc-panel-WARNING **: Could not load 
/usr/share/themes/Adwaita/index.theme: Nincs ilyen fájl vagy könyvtár
   (gnome-control-center:2016): GLib-GIO-CRITICAL **: g_settings_set_value: 
assertion `G_IS_SETTINGS (settings)' failed
   (gnome-control-center:2016): Gtk-CRITICAL **: gtk_builder_get_object: 
assertion `GTK_IS_BUILDER (builder)' failed
   (gnome-control-center:2016): Gtk-CRITICAL **: 
gtk_icon_view_get_selected_items: assertion `GTK_IS_ICON_VIEW (icon_view)' 
failed

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1364522] Re: Firefox crashes sometimes when using webgl with nouveau driver

2014-09-02 Thread Bernhard Übelacker
Problem could be reproduced with following graphic adapters:
01:00.0 VGA compatible controller: NVIDIA Corporation NV40 [GeForce 6800] (rev 
a1)
01:00.0 VGA compatible controller: NVIDIA Corporation NV31 [GeForce FX 5600XT] 
(rev a1)

(Firefox probably blacklisted the second card for webgl, to be able to 
investigate on the issue I had to enable manually.)
But the crash happens for the first card with default settings.

As far as I could observe, Firefox creates 3 contexts, then destroys the
last one but then still accesses the freed memory of the destroyed
context.

I believe this crash got fixed by this upstream commit:
http://cgit.freedesktop.org/mesa/mesa/commit/src/gallium/drivers/nouveau/nv30/nv30_context.c?id=c092c46b27c6f6a6674e8d67fb3afdb684811819
Unfortunately this commit got only into 10.2.2.

But as Trusty Tahr is a LTS release it probably will stay a long time with 
users using older graphics cards.
Therefore I ask if this little patch could be added.

--
Building package libgl1-mesa-dri like this makes the crash for me go away:
mkdir -p ~/ubuntu/mesa; cd ~/ubuntu/mesa
apt-get source libgl1-mesa-dri
cd mesa-10.1.3
wget wget 
http://cgit.freedesktop.org/mesa/mesa/patch/src/gallium/drivers/nouveau/nv30/nv30_context.c?id=c092c46b27c6f6a6674e8d67fb3afdb684811819
 -O debian/patches/999-nv30_avoid_dangling_references_to_deleted_contexts.patch
echo "999-nv30_avoid_dangling_references_to_deleted_contexts.patch" >> 
debian/patches/series
patch -p1 < 
debian/patches/999-nv30_avoid_dangling_references_to_deleted_contexts.patch
dpkg-buildpackage
cd ..
# sudo dpkg -i libgl1-mesa-dri_10.1.3-0ubuntu0.1_i386.deb
--

Other references where this bug seems to appear (just for reference):
https://bugzilla.redhat.com/show_bug.cgi?id=1125339
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=661387
https://crash-stats.mozilla.com/report/list?signature=nouveau_dri.so%400x239b79


** Bug watch added: Red Hat Bugzilla #1125339
   https://bugzilla.redhat.com/show_bug.cgi?id=1125339

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1364522

Title:
  Firefox crashes sometimes when using webgl with nouveau driver

Status in “mesa” package in Ubuntu:
  New

Bug description:
  Visiting with Firefox e.g.
  https://developer.mozilla.org/de/demos/detail/orange-slice/launch
  makes firefox crash.

  Program received signal SIGSEGV, Segmentation fault.
  nouveau_fence_next (screen=screen@entry=0x5a5a5a5a) at 
../../../../../../src/gallium/drivers/nouveau/nouveau_fence.c:226
  226if (screen->fence.current->state < NOUVEAU_FENCE_STATE_EMITTING)
  (gdb) bt
  #0  nouveau_fence_next (screen=screen@entry=0x5a5a5a5a) at 
../../../../../../src/gallium/drivers/nouveau/nouveau_fence.c:226
  #1  0x9b5b7fc0 in nv30_context_kick_notify (push=0x9b8f62b0) at 
../../../../../../src/gallium/drivers/nouveau/nv30/nv30_context.c:48
  #2  0xa0a0ea3e in pushbuf_submit (push=push@entry=0x9b8f62b0, chan=, chan=) at ../../nouveau/pushbuf.c:325
  #3  0xa0a0ed7a in pushbuf_flush (push=push@entry=0x9b8f62b0) at 
../../nouveau/pushbuf.c:402
  #4  0xa0a0faca in nouveau_pushbuf_kick (push=0x9b8f62b0, chan=0xa40c5420) at 
../../nouveau/pushbuf.c:774
  #5  0x9b5b811f in PUSH_KICK (push=) at 
../../../../../../src/gallium/drivers/nouveau/nouveau_winsys.h:56
  #6  nv30_context_flush (pipe=0x9b986000, fence=0x0, flags=0) at 
../../../../../../src/gallium/drivers/nouveau/nv30/nv30_context.c:83
  #7  0x9b4b4e1c in st_flush (st=st@entry=0x989e8000, fence=fence@entry=0x0, 
flags=flags@entry=0) at ../../../../src/mesa/state_tracker/st_cb_flush.c:87
  #8  0x9b4b4e82 in st_glFlush (ctx=0x98844000) at 
../../../../src/mesa/state_tracker/st_cb_flush.c:121
  #9  0x9b3b3065 in _mesa_flush (ctx=ctx@entry=0x98844000) at 
../../../../src/mesa/main/context.c:1691
  #10 0x9b3b3130 in _mesa_make_current (newCtx=newCtx@entry=0x0, 
drawBuffer=drawBuffer@entry=0x0, readBuffer=readBuffer@entry=0x0) at 
../../../../src/mesa/main/context.c:1503
  #11 0x9b4dee74 in st_api_make_current (stapi=0x9b779700 , 
stctxi=0x0, stdrawi=0x0, streadi=0x0) at 
../../../../src/mesa/state_tracker/st_manager.c:746
  #12 0x9b59d9ee in dri_unbind_context (cPriv=0x994e3120) at 
../../../../../../../src/gallium/state_trackers/dri/drm/dri_context.c:215
  #13 0x9b38db93 in driUnbindContext (pcp=0x994e3120) at 
../../../../../../../src/mesa/drivers/dri/common/dri_util.c:578
  #14 0x9b7df149 in dri2_unbind_context (context=0x9b9cbc20, new=0x0) at 
../../../../src/glx/dri2_glx.c:184
  #15 0x9b7b7985 in MakeContextCurrent (dpy=dpy@entry=0xb7191000, 
draw=draw@entry=0, read=read@entry=0, gc_user=gc_user@entry=0x0) at 
../../../../src/glx/glxcurrent.c:245
  #16 0x9b7b7a73 in glXMakeCurrent (dpy=0xb7191000, draw=0, gc=0x0) at 
../../../../src/glx/glxcurrent.c:293
  #17 0xb3d3916d 

[Touch-packages] [Bug 1364522] [NEW] Firefox crashes sometimes when using webgl with nouveau driver

2014-09-02 Thread Bernhard Übelacker
Public bug reported:

Visiting with Firefox e.g. https://developer.mozilla.org/de/demos/detail
/orange-slice/launch makes firefox crash.

Program received signal SIGSEGV, Segmentation fault.
nouveau_fence_next (screen=screen@entry=0x5a5a5a5a) at 
../../../../../../src/gallium/drivers/nouveau/nouveau_fence.c:226
226if (screen->fence.current->state < NOUVEAU_FENCE_STATE_EMITTING)
(gdb) bt
#0  nouveau_fence_next (screen=screen@entry=0x5a5a5a5a) at 
../../../../../../src/gallium/drivers/nouveau/nouveau_fence.c:226
#1  0x9b5b7fc0 in nv30_context_kick_notify (push=0x9b8f62b0) at 
../../../../../../src/gallium/drivers/nouveau/nv30/nv30_context.c:48
#2  0xa0a0ea3e in pushbuf_submit (push=push@entry=0x9b8f62b0, chan=, chan=) at ../../nouveau/pushbuf.c:325
#3  0xa0a0ed7a in pushbuf_flush (push=push@entry=0x9b8f62b0) at 
../../nouveau/pushbuf.c:402
#4  0xa0a0faca in nouveau_pushbuf_kick (push=0x9b8f62b0, chan=0xa40c5420) at 
../../nouveau/pushbuf.c:774
#5  0x9b5b811f in PUSH_KICK (push=) at 
../../../../../../src/gallium/drivers/nouveau/nouveau_winsys.h:56
#6  nv30_context_flush (pipe=0x9b986000, fence=0x0, flags=0) at 
../../../../../../src/gallium/drivers/nouveau/nv30/nv30_context.c:83
#7  0x9b4b4e1c in st_flush (st=st@entry=0x989e8000, fence=fence@entry=0x0, 
flags=flags@entry=0) at ../../../../src/mesa/state_tracker/st_cb_flush.c:87
#8  0x9b4b4e82 in st_glFlush (ctx=0x98844000) at 
../../../../src/mesa/state_tracker/st_cb_flush.c:121
#9  0x9b3b3065 in _mesa_flush (ctx=ctx@entry=0x98844000) at 
../../../../src/mesa/main/context.c:1691
#10 0x9b3b3130 in _mesa_make_current (newCtx=newCtx@entry=0x0, 
drawBuffer=drawBuffer@entry=0x0, readBuffer=readBuffer@entry=0x0) at 
../../../../src/mesa/main/context.c:1503
#11 0x9b4dee74 in st_api_make_current (stapi=0x9b779700 , 
stctxi=0x0, stdrawi=0x0, streadi=0x0) at 
../../../../src/mesa/state_tracker/st_manager.c:746
#12 0x9b59d9ee in dri_unbind_context (cPriv=0x994e3120) at 
../../../../../../../src/gallium/state_trackers/dri/drm/dri_context.c:215
#13 0x9b38db93 in driUnbindContext (pcp=0x994e3120) at 
../../../../../../../src/mesa/drivers/dri/common/dri_util.c:578
#14 0x9b7df149 in dri2_unbind_context (context=0x9b9cbc20, new=0x0) at 
../../../../src/glx/dri2_glx.c:184
#15 0x9b7b7985 in MakeContextCurrent (dpy=dpy@entry=0xb7191000, 
draw=draw@entry=0, read=read@entry=0, gc_user=gc_user@entry=0x0) at 
../../../../src/glx/glxcurrent.c:245
#16 0x9b7b7a73 in glXMakeCurrent (dpy=0xb7191000, draw=0, gc=0x0) at 
../../../../src/glx/glxcurrent.c:293
#17 0xb3d3916d in mozilla::gl::GLXLibrary::xMakeCurrent (this=0xb6e58470 
, display=0xb7191000, drawable=drawable@entry=0, 
context=context@entry=0x0) at 
/build/buildd/firefox-31.0+build1/gfx/gl/GLContextProviderGLX.cpp:525
#18 0xb3d39d92 in mozilla::gl::GLContextGLX::~GLContextGLX (this=0x988dc800, 
__in_chrg=) at 
/build/buildd/firefox-31.0+build1/gfx/gl/GLContextProviderGLX.cpp:836
#19 0xb3d39e12 in mozilla::gl::GLContextGLX::~GLContextGLX (this=0x988dc800, 
__in_chrg=) at 
/build/buildd/firefox-31.0+build1/gfx/gl/GLContextProviderGLX.cpp:845
#20 0xb3d38ea0 in 
mozilla::detail::GenericRefCounted<(mozilla::detail::RefCountAtomicity)0>::Release
 (this=0x988dc800) at ../../dist/include/mozilla/GenericRefCounted.h:95
#21 0xb3ddc635 in nsRefPtr::assign_assuming_AddRef 
(this=this@entry=0x9b8eb84c, newPtr=newPtr@entry=0x0) at 
../../dist/include/nsAutoPtr.h:882
#22 0xb4561170 in assign_with_AddRef (rawPtr=0x0, this=0x9b8eb84c) at 
../../../dist/include/nsAutoPtr.h:866
#23 operator= (rhs=0x0, this=0x9b8eb84c) at 
../../../dist/include/nsAutoPtr.h:964
#24 mozilla::WebGLContext::DestroyResourcesAndContext 
(this=this@entry=0x9b8eb800) at 
/build/buildd/firefox-31.0+build1/content/canvas/src/WebGLContext.cpp:284
#25 0xb45611bb in mozilla::WebGLContext::~WebGLContext (this=0x9b8eb800, 
__in_chrg=) at 
/build/buildd/firefox-31.0+build1/content/canvas/src/WebGLContext.cpp:203
#26 0xb455e330 in mozilla::WebGL1Context::~WebGL1Context (this=0x9b8eb800, 
__in_chrg=) at 
/build/buildd/firefox-31.0+build1/content/canvas/src/WebGL1Context.cpp:25
#27 0xb455ebe9 in mozilla::WebGLContext::DeleteCycleCollectable 
(this=0x9b8eb800) at 
/build/buildd/firefox-31.0+build1/content/canvas/src/WebGLContext.cpp:1397
#28 0xb455ebbb in 
mozilla::WebGLContext::cycleCollection::DeleteCycleCollectable (this=0xb6e2b500 
, p=0x9b8eb800) at 
/build/buildd/firefox-31.0+build1/content/canvas/src/WebGLContext.h:152
#29 0xb3841504 in SnowWhiteKiller::~SnowWhiteKiller 
(this=this@entry=0xbfb4273c, __in_chrg=) at 
/build/buildd/firefox-31.0+build1/xpcom/base/nsCycleCollector.cpp:2403
#30 0xb3841d1b in ~RemoveSkippableVisitor (this=0xbfb4273c, 
__in_chrg=) at 
/build/buildd/firefox-31.0+build1/xpcom/base/nsCycleCollector.cpp:2495
#31 nsPurpleBuffer::RemoveSkippable (this=this@entry=0xb71e808c, 
aCollector=aCollector@entry=0xb71e8000, 
aRemoveChildlessNodes=aRemoveChildlessNodes@entry=false, 
aAsyncSnowWhiteFreeing=aAsyncSnowWhiteFreeing@entry=false,  aCb=0xb44dbe35 
) a