[Touch-packages] [Bug 1391493] Re: Location tagging doesn't work for videos
i have also faced the same kind of my clients site : https://www.snapofficial.net/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1391493 Title: Location tagging doesn't work for videos Status in camera-app: Confirmed Status in camera-app package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Open the Camera application 2. Switch to Video mode 3. Swipe up to reveal the sub-controls 4. Tap on Location 5. Tap On 6. Wait for several minutes to allow a fix to be retrieved 7. Record a short video Expected result: When viewing EXIF data for the video, location information is present Actual result: When viewing EXIF data, location information is not present To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1391493/+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 1830644] [NEW] [MS-7C02, ATI R6xx HDMI, Digital Out, HDMI] No sound at all
Public bug reported: AMD® Ryzen 5 2400g with radeon vega graphics × 8 AMD® Raven GNOME 3.28.2 No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.2 LTS Release:18.04 Codename: bionic ALSA information is located at http://alsa- project.org/db/?f=b100eba8f9d64a684998a23ec864a7449ff2615c After trying every solution and tutorials and reinstalling Ubuntu, I still have not been able to fix the audio issue. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: inanna 1578 F pulseaudio /dev/snd/pcmC1D0c: inanna 1578 F...m pulseaudio /dev/snd/controlC0: inanna 1578 F pulseaudio /dev/snd/pcmC0D3p: inanna 1578 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon May 27 19:24:29 2019 InstallationDate: Installed on 2019-05-27 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: HD-Audio Generic - HD-Audio Generic Symptom_Jack: Digital Out, HDMI Symptom_Type: No sound at all Title: [MS-7C02, ATI R6xx HDMI, Digital Out, HDMI] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.40 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450 TOMAHAWK (MS-7C02) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.40:bd12/19/2018:svnMicro-StarInternationalCo.,Ltd:pnMS-7C02:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnB450TOMAHAWK(MS-7C02):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C02 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1830644 Title: [MS-7C02, ATI R6xx HDMI, Digital Out, HDMI] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: AMD® Ryzen 5 2400g with radeon vega graphics × 8 AMD® Raven GNOME 3.28.2 No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic ALSA information is located at http://alsa- project.org/db/?f=b100eba8f9d64a684998a23ec864a7449ff2615c After trying every solution and tutorials and reinstalling Ubuntu, I still have not been able to fix the audio issue. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: inanna 1578 F pulseaudio /dev/snd/pcmC1D0c: inanna 1578 F...m pulseaudio /dev/snd/controlC0: inanna 1578 F pulseaudio /dev/snd/pcmC0D3p: inanna 1578 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon May 27 19:24:29 2019 InstallationDate: Installed on 2019-05-27 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: HD-Audio Generic - HD-Audio Generic Symptom_Jack: Digital Out, HDMI Symptom_Type: No sound at all Title: [MS-7C02, ATI R6xx HDMI, Digital Out, HDMI] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.40 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450 TOMAHAWK (MS-7C02) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.40:bd12/19/2018:svnMicro-StarInternationalCo.,Ltd:pnMS-7C02:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnB450TOMAHAWK(MS-7C02):rvr1.0:cvn
[Touch-packages] [Bug 1830503] [NEW] [MS-7C02, Realtek ALC892, Red Line Out, Rear] No sound at all
Public bug reported: No sound Motherboard MSI B450 Tomahawnk CPU APU AMD Ryzen 5 2400G-4 Core RX Vega. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: inanna 1251 F pulseaudio /dev/snd/controlC0: inanna 1251 F pulseaudio /dev/snd/pcmC0D3p: inanna 1251 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun May 26 00:08:58 2019 InstallationDate: Installed on 2019-05-22 (3 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic_1 failed Symptom_Card: HD-Audio Generic - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: inanna 1251 F pulseaudio /dev/snd/controlC0: inanna 1251 F pulseaudio /dev/snd/pcmC0D3p: inanna 1251 F...m pulseaudio Symptom_Jack: Red Line Out, Rear Symptom_Type: No sound at all Title: [MS-7C02, Realtek ALC892, Red Line Out, Rear] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.40 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450 TOMAHAWK (MS-7C02) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.40:bd12/19/2018:svnMicro-StarInternationalCo.,Ltd:pnMS-7C02:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnB450TOMAHAWK(MS-7C02):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C02 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1830503 Title: [MS-7C02, Realtek ALC892, Red Line Out, Rear] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: No sound Motherboard MSI B450 Tomahawnk CPU APU AMD Ryzen 5 2400G-4 Core RX Vega. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: inanna 1251 F pulseaudio /dev/snd/controlC0: inanna 1251 F pulseaudio /dev/snd/pcmC0D3p: inanna 1251 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun May 26 00:08:58 2019 InstallationDate: Installed on 2019-05-22 (3 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic_1 failed Symptom_Card: HD-Audio Generic - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: inanna 1251 F pulseaudio /dev/snd/controlC0: inanna 1251 F pulseaudio /dev/snd/pcmC0D3p: inanna 1251 F...m pulseaudio Symptom_Jack: Red Line Out, Rear Symptom_Type: No sound at all Title: [MS-7C02, Realtek ALC892, Red Line Out, Rear] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.40 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450 TOMAHAWK (MS-7C02) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.40:bd12/19/2018:svnMicro-StarInternationalCo.,Ltd:pnMS-7C02:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnB450TOMAHAWK(MS-7C02):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C02 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1830503/+subscriptions -
[Touch-packages] [Bug 1779721] Re: systemd-networkd does not configure DHCPv4
In both cases, no network, no static IP address, .. however, restarting
systemd-networkd instantly brings the configuration up, and communication on
the desired IP address starts.
If anyone face laptop problem gets help from this http://lenovotechsupport.com
--
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/1779721
Title:
systemd-networkd does not configure DHCPv4
Status in netplan.io package in Ubuntu:
Invalid
Status in systemd package in Ubuntu:
Confirmed
Bug description:
I have an up-to-date Ubuntu 18.04 (bionic) server installation (with
systemd 237-3ubuntu10) which has following netplan configuration:
```
root@ubuntu:~# cat /etc/netplan/01-netcfg.yaml
# This file describes the network interfaces available on your system
# For more information, see netplan(5).
network:
version: 2
renderer: networkd
ethernets:
all:
match: {}
dhcp4: yes
root@ubuntu:~# cat /run/systemd/network/10-netplan-all.network
[Match]
[Network]
DHCP=ipv4
[DHCP]
UseMTU=true
RouteMetric=100
```
Despite having DHCPv4 configured, no IPv4 address is configured on the
ethernet device:
```
root@ubuntu:~# ip a show ens6
2: ens6: mtu 64000 qdisc fq_codel state UP
group default qlen 1000
link/ether 02:01:71:8f:cc:72 brd ff:ff:ff:ff:ff:ff
inet6 fe80::1:71ff:fe8f:cc72/64 scope link
valid_lft forever preferred_lft forever
```
The kernel dmesg has no related messages and the journal log also
looks normal:
```
root@ubuntu:~# journalctl -u systemd-networkd
Jul 02 16:36:51 ubuntu systemd[1]: Starting Network Service...
Jul 02 16:36:51 ubuntu systemd-networkd[1790]: ens6: Gained IPv6LL
Jul 02 16:36:51 ubuntu systemd-networkd[1790]: Enumeration completed
Jul 02 16:36:51 ubuntu systemd[1]: Started Network Service.
Jul 02 16:36:51 ubuntu systemd-networkd[1790]: lo: Link is not managed by us
Jul 02 16:36:51 ubuntu systemd-networkd[1790]: lo: Configured
```
Calling dhclient sets up the device correctly:
```
root@ubuntu:~# dhclient ens6
root@ubuntu:~# cat /var/lib/dhcp/dhclient.leases
lease {
interface "ens6";
fixed-address 87.106.172.36;
option subnet-mask 255.255.255.255;
option dhcp-lease-time 600;
option routers 87.106.172.1;
option dhcp-message-type 5;
option domain-name-servers 46.16.74.70,46.16.72.37;
option dhcp-server-identifier 87.106.172.1;
option interface-mtu 64000;
option host-name "ubuntu-18_04-fkb-2018-07-02";
renew 1 2018/07/02 16:46:51;
rebind 1 2018/07/02 16:51:31;
expire 1 2018/07/02 16:52:46;
}
root@ubuntu:~# ip a show ens6
2: ens6: mtu 64000 qdisc fq_codel state UP
group default qlen 1000
link/ether 02:01:71:8f:cc:72 brd ff:ff:ff:ff:ff:ff
inet 87.106.172.36/32 brd 87.106.172.36 scope global ens6
valid_lft forever preferred_lft forever
inet6 fe80::1:71ff:fe8f:cc72/64 scope link
valid_lft forever preferred_lft forever
```
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1779721/+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 1623383] Re: Some restarts fail due to missing base devices
The system LPAR this was seen first was an upgrade from Xenial but since then has been freshly installed with Yakkety. The same behaviour is seen on a zVM guest running Yakkety. If anyone face printer issue click here http://canonprintersupport247.com -- 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/1623383 Title: Some restarts fail due to missing base devices Status in systemd package in Ubuntu: Confirmed Bug description: Arch: s390x Release: Yakkety / 16.10 This happens on some (but not all) system starts with Yakkety. In Xenial (which is using the same 4.4 kernel version the Yakkety systems were using when the problem was first observed) this did not happen. The system (LPAR) this was seen first was an upgrade from Xenial but since then has been freshly installed with Yakkety. The same behaviour is seen on a zVM guest running Yakkety. The attached syslog shows a failed boot, followed by one that did work. Note the "Found device .*(sclp|encc00).*" messages in the good boot. Those are missing in the bad attempt and as a result networking and console fail to be usable. Also note, those boots were 4.8 kernels but we saw this with 4.4 kernels, too. This might be a systemd problem / race, I just filed it into udev for now as that better matches the not finding basic devices symptom. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1623383/+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 1721223] Re: Networkd fail to set ip address between leases if ip address changes on UbuntuCore
you can Add a device, and assign two IPv4 addresses. First one, with a short lease time. Second one, with a different ip and a longer lease time. If anyone face printer issue click here http://HPsupport365.com ** Attachment added: "printer.png" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1721223/+attachment/5223123/+files/printer.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/1721223 Title: Networkd fail to set ip address between leases if ip address changes on UbuntuCore Status in Snappy: Fix Committed Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Status in systemd source package in Zesty: Won't Fix Status in systemd source package in Artful: Fix Released Bug description: [Impact] * networkd fails to renew a lease, specifically it fails to change IPv4 address via DHCP renew/rebind. * networkd relies on a kernel feature to promote secondary IPv4 address to primary, upon primary address lease expiry. * this sysctl tunable was not enabled by default in systemd. [Test Case] Add a device, and assign two IPv4 addresses. First one, with a short lease time. Second one, with a different ip and a longer lease time. Second one should be treated as secondary ip address, and upon expiry of the first one, should be promoted and become primary ip address. The below scripted instructions simulate this: sudo ip link add name testleases type dummy sudo ip address add 192.0.2.10/27 dev testleases \ valid_lft 5 preferred_lft 5 sudo ip address add 192.0.2.11/27 dev testleases \ valid_lft 11 preferred_lft 11 ip address list dev testleases | \ grep -q 'inet 192.0.2.10/27 scope global dynamic testleases' \ && echo ok || echo not ok ip address list dev testleases | \ grep -q 'inet 192.0.2.11/27 scope global secondary dynamic testleases' \ && echo ok || echo not ok sleep 6 ip address list dev testleases | \ grep -q 'inet 192.0.2.11/27 scope global dynamic testleases' \ && echo ok || echo not ok sudo ip link del dev testleases [Regression Potential] * This changes the default kernel behaviour, previously upon expiry of the primary address, secondary addresses were removed as well. Which is imho silly. * comparing networkd renewal with isc-dhcp renewal the semantics are quite different. Upon acquiring new ip address, isc-dhcp would instantly flush existing ip address, and add a new one. Networkd add the new address as secondary, and waits for old one to expire first before promoting / switching to using the new ip address. IMHO kernel should have an API to promote secondary ip address to a primary one. * This update also applies other safe-looking options, which are currently also already applied via sysctls shipped in other packages # Source route verification net.ipv4.conf.default.rp_filter = 1 net.ipv4.conf.all.rp_filter = 1 # Do not accept source routing net.ipv4.conf.default.accept_source_route = 0 net.ipv4.conf.all.accept_source_route = 0 # Enable hard and soft link protection fs.protected_hardlinks = 1 fs.protected_symlinks = 1 * This update also applies the following upstream/bufferbloat.net recommended setting # Fair Queue CoDel packet scheduler to fight bufferbloat net.core.default_qdisc = fq_codel * [~racb] There are complex network setups out there, such as HA with corosync/pacemaker, OpenStack Neutron, and that kind of thing. If this fix were SRU'd, will all of these things in the wild cope with this sysctl change? [Other Info] * Original bug report Hi there, we found a replicable issue that involves the Ubuntu Core networking and causes complete loss of connectivity. We run a custom board with ubuntu core: the architecure is amrhf. We replicated this issue with an official Ubuntu Core image on a Raspberry Pi: other platform was been tested. It shows that it is a snap core problem which interests networkd: we use the default network stack based on networkd + netplan. Below steps to replicate the issue. 1)Setup a dhcp server for lease of about some minutes (i.e 10 minutes). 2)Boot the board and wait for get an ip from dhcp server 3)Before the lease expires, set a reservation for a different ip address Depending on lease duration before the lease expires( for 10 minute we have 2 minutes before ), networkd configure the new address in addition to the previous one. When the lease expire both ip address ( the prevoius and the new one ) disappear from the interested network interface. Depending on lease duration before the second lease expires ( for 10 minure we have 2 minutes before ) networkd configure only the new ip address on the network interface and the ping toward an outside host work properly. During
[Touch-packages] [Bug 1801202] [NEW] Xorg freeze
Public bug reported:
The screen freezes suddenly when i'm trying to play an online video or
when i have too many tabs or folders open.
---
CurrentDmesg.txt:
[ 5465.753948] ata1.00: exception Emask 0x0 SAct 0x1c04 SErr 0x0 action 0x0
[ 5465.753954] ata1.00: irq_stat 0x4008
[ 5465.753959] ata1.00: failed command: READ FPDMA QUEUED
[ 5465.753969] ata1.00: cmd 60/00:10:00:9b:f5/01:00:53:00:00/40 tag 2 ncq dma
131072 in
res 41/40:00:c0:9b:f5/00:01:53:00:00/00 Emask 0x409
(media error)
[ 5465.753973] ata1.00: status: { DRDY ERR }
[ 5465.753976] ata1.00: error: { UNC }
[ 5466.031887] ata1.00: configured for UDMA/133
[ 5466.031915] sd 0:0:0:0: [sda] tag#2 FAILED Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
[ 5466.031921] sd 0:0:0:0: [sda] tag#2 Sense Key : Medium Error [current]
[ 5466.031925] sd 0:0:0:0: [sda] tag#2 Add. Sense: Unrecovered read error -
auto reallocate failed
[ 5466.031932] sd 0:0:0:0: [sda] tag#2 CDB: Read(10) 28 00 53 f5 9b 00 00 01 00
00
[ 5466.031935] print_req_error: I/O error, dev sda, sector 1408605120
[ 5466.031994] ata1: EH complete
---
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
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Nov 2 01:04:22 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
nvidia, 390.77, 4.15.0-36-generic, x86_64: installed
nvidia, 390.77, 4.15.0-38-generic, x86_64: installed
DpkgLog:
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Very infrequently
GraphicsCard:
Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a2e] (rev
09) (prog-if 00 [VGA controller])
Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:382b]
Subsystem: Lenovo GM108M [GeForce 920MX] [17aa:382b]
InstallationDate: Installed on 2018-10-04 (28 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: LENOVO 80QQ
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=it_IT.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic
root=UUID=b0abddd7-646b-4707-bf44-54c3fc3ea828 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/21/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: E0CN63WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: Nano 5B6
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40700 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad 100-15IBD
dmi.modalias:
dmi:bvnLENOVO:bvrE0CN63WW:bd10/21/2016:svnLENOVO:pn80QQ:pvrLenovoideapad100-15IBD:rvnLENOVO:rnNano5B6:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad100-15IBD:
dmi.product.family: IDEAPAD
dmi.product.name: 80QQ
dmi.product.version: Lenovo ideapad 100-15IBD
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
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.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Confirmed
** Affects: xorg-server (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug bionic freeze ubuntu
** Description changed:
The screen freezes suddenly when i'm trying to play an online video or
when i have too many tabs open.
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
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Nov 2 01:04:22 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
- nvidia, 390.77, 4.15.0-36-generic, x86_64: installed
- nvidia, 390.77, 4.15.0-38-generic, x86_64: installed
+ nvidia, 390.77, 4.15.0-36-generic, x86_64: installed
+ nvidia, 390.77, 4.15.0-38-generic, x86_64: installed
DpkgLog:
-
+
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Very infrequently
GraphicsCard:
- Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a2e]
(rev 09) (prog-if 00 [VG
[Touch-packages] [Bug 1153488] Re: Treats bluetooth input device batteries as batteries
https://www.applemacsupportnumbers.com/apple-customer-support/ -- 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/1153488 Title: Treats bluetooth input device batteries as batteries Status in gnome-power-manager package in Ubuntu: Invalid Status in upower package in Ubuntu: Fix Released Status in gnome-power-manager source package in Precise: Invalid Status in upower source package in Precise: Fix Released Status in gnome-power-manager source package in Quantal: Invalid Status in upower source package in Quantal: Won't Fix Status in gnome-power-manager source package in Raring: Invalid Status in upower source package in Raring: Fix Released Status in gnome-power-manager source package in Saucy: Invalid Status in upower source package in Saucy: Fix Released Bug description: [Impact] * There are many Bluetooth devices with battery information inside. When they are treated as system battery, it will make the system poweroff/suspend/hibernate when some Bluetooth device has critical low battery. It is a very annoying behavior for the users. Originally, there is no such Bluetooth battery information until Ubuntu 12.04 brings linux-quantal-lts and linux-raring-lts, so those linux kernels also bring this issue. [Test Case] * Pair some Bluetooth devices, such as Apple Wireless Mouse or Apple Wireless Keyboard. * Click the power indicator and you can find Apple Wireless Mouse is listed as system battery, and there is no Apple Wireless Keyboard. If you open gnome-power-statistics, you can find the 'Supply' field of Apple Wireless Mouse is 'Yes' but it should not be. [Regression Potential] * There is no obvious regression as I know. [Other Info] * Most patches are from upstream, modified to fix the conflicts, and made by the same developer (i.e. fourdollars). * We need another patch from https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d0a934b764c67b4bf626f5b7cf725a6e3066afd2 to make Apple Wireless Keyboard showing. [Original Bug Description] This is a weird one... the system is an HP Pavilion 23 All In One and is powered by a large power supply brick. I currently have an Apple Magic Mouse connected via Bluetooth. As soon as the mouse is connected, the Battery indicator shows up and clicking on that shows that the system is reading my mouse as a battery! See the attached screen shot for what I see in the Power status. Looking at hcitool: ubuntu@201206-11396:~$ hcitool dev Devices: hci0 9C:B7:0D:80:71:DB To make matters even more weird, I actually observed the battery indicator go from full to "Critically Low" and the system suspended itself. Keep in mind, again, that this system has NO battery, it's reading my bluetooth mouse as a battery device. I disconnected the magic mouse and the battery indicator went to Empty Red outline and status showed Battery Disconnected. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.5.0-23-generic 3.5.0-23.35~precise1 ProcVersionSignature: Ubuntu 3.5.0-23.35~precise1-generic 3.5.7.2 Uname: Linux 3.5.0-23-generic x86_64 NonfreeKernelModules: wl fglrx AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25. AplayDevices: List of PLAYBACK Hardware Devices card 0: Generic [HD-Audio Generic], device 0: ALC269VC Analog [ALC269VC Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: Generic [HD-Audio Generic], device 0: ALC269VC Analog [ALC269VC Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1726 F pulseaudio Card0.Amixer.info: Card hw:0 'Generic'/'HD-Audio Generic at 0xfeb4 irq 16' Mixer name : 'Realtek ALC269VC' Components : 'HDA:10ec0269,103c2aee,00100202' Controls : 21 Simple ctrls : 10 Date: Mon Mar 11 03:54:36 2013 HibernationDevice: RESUME=UUID=ccd7a21f-7a71-4fa5-b95d-e2898c3dae24 InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) MachineType: Hewlett-Packard a654 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-23-generic root=UUID=e2a5f4ae-dfa2-40be-a6c5-3ddb85dcf68e ro quiet splash initcall_debug vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.5.0-23-generic N/A linux-backports-modules-3.5.0-23-generic N/A linux-firmware1.79.1 SourcePackage: linux StagingDrivers: rts_pstor UpgradeStatus: No upgrade log present (probably fresh install)
[Touch-packages] [Bug 1721223] Re: Networkd fail to set ip address between leases if ip address changes on UbuntuCore
www.belkinroutersupportnumber.com/ -- 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/1721223 Title: Networkd fail to set ip address between leases if ip address changes on UbuntuCore Status in Snappy: Fix Committed Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Status in systemd source package in Zesty: Won't Fix Status in systemd source package in Artful: Fix Released Bug description: [Impact] * networkd fails to renew a lease, specifically it fails to change IPv4 address via DHCP renew/rebind. * networkd relies on a kernel feature to promote secondary IPv4 address to primary, upon primary address lease expiry. * this sysctl tunable was not enabled by default in systemd. [Test Case] Add a device, and assign two IPv4 addresses. First one, with a short lease time. Second one, with a different ip and a longer lease time. Second one should be treated as secondary ip address, and upon expiry of the first one, should be promoted and become primary ip address. The below scripted instructions simulate this: sudo ip link add name testleases type dummy sudo ip address add 192.0.2.10/27 dev testleases \ valid_lft 5 preferred_lft 5 sudo ip address add 192.0.2.11/27 dev testleases \ valid_lft 11 preferred_lft 11 ip address list dev testleases | \ grep -q 'inet 192.0.2.10/27 scope global dynamic testleases' \ && echo ok || echo not ok ip address list dev testleases | \ grep -q 'inet 192.0.2.11/27 scope global secondary dynamic testleases' \ && echo ok || echo not ok sleep 6 ip address list dev testleases | \ grep -q 'inet 192.0.2.11/27 scope global dynamic testleases' \ && echo ok || echo not ok sudo ip link del dev testleases [Regression Potential] * This changes the default kernel behaviour, previously upon expiry of the primary address, secondary addresses were removed as well. Which is imho silly. * comparing networkd renewal with isc-dhcp renewal the semantics are quite different. Upon acquiring new ip address, isc-dhcp would instantly flush existing ip address, and add a new one. Networkd add the new address as secondary, and waits for old one to expire first before promoting / switching to using the new ip address. IMHO kernel should have an API to promote secondary ip address to a primary one. * This update also applies other safe-looking options, which are currently also already applied via sysctls shipped in other packages # Source route verification net.ipv4.conf.default.rp_filter = 1 net.ipv4.conf.all.rp_filter = 1 # Do not accept source routing net.ipv4.conf.default.accept_source_route = 0 net.ipv4.conf.all.accept_source_route = 0 # Enable hard and soft link protection fs.protected_hardlinks = 1 fs.protected_symlinks = 1 * This update also applies the following upstream/bufferbloat.net recommended setting # Fair Queue CoDel packet scheduler to fight bufferbloat net.core.default_qdisc = fq_codel * [~racb] There are complex network setups out there, such as HA with corosync/pacemaker, OpenStack Neutron, and that kind of thing. If this fix were SRU'd, will all of these things in the wild cope with this sysctl change? [Other Info] * Original bug report Hi there, we found a replicable issue that involves the Ubuntu Core networking and causes complete loss of connectivity. We run a custom board with ubuntu core: the architecure is amrhf. We replicated this issue with an official Ubuntu Core image on a Raspberry Pi: other platform was been tested. It shows that it is a snap core problem which interests networkd: we use the default network stack based on networkd + netplan. Below steps to replicate the issue. 1)Setup a dhcp server for lease of about some minutes (i.e 10 minutes). 2)Boot the board and wait for get an ip from dhcp server 3)Before the lease expires, set a reservation for a different ip address Depending on lease duration before the lease expires( for 10 minute we have 2 minutes before ), networkd configure the new address in addition to the previous one. When the lease expire both ip address ( the prevoius and the new one ) disappear from the interested network interface. Depending on lease duration before the second lease expires ( for 10 minure we have 2 minutes before ) networkd configure only the new ip address on the network interface and the ping toward an outside host work properly. During the test the dhcp server records correctly leases and their duration. We check directly from console the network interface setting with the tool ip, checking continuously the value for ip address and valid_lft fields for the interested network interface. Please note that if the ip address setting are the s
[Touch-packages] [Bug 1721223] Re: Networkd fail to set ip address between leases if ip address changes on UbuntuCore
Follow this instruction hope so you can solve your issue, Setup a DHCP server for the lease of about some minutes. Boot the board and wait to forget an IP from DHCP server. Before the lease expires, set a reservation for a different IP address. If anyone using Belkin router or any other router facing any problem regarding this get help from this Belkin Support Number it really provides the best solution. -- 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/1721223 Title: Networkd fail to set ip address between leases if ip address changes on UbuntuCore Status in Snappy: Fix Committed Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Status in systemd source package in Zesty: Won't Fix Status in systemd source package in Artful: Fix Released Bug description: [Impact] * networkd fails to renew a lease, specifically it fails to change IPv4 address via DHCP renew/rebind. * networkd relies on a kernel feature to promote secondary IPv4 address to primary, upon primary address lease expiry. * this sysctl tunable was not enabled by default in systemd. [Test Case] Add a device, and assign two IPv4 addresses. First one, with a short lease time. Second one, with a different ip and a longer lease time. Second one should be treated as secondary ip address, and upon expiry of the first one, should be promoted and become primary ip address. The below scripted instructions simulate this: sudo ip link add name testleases type dummy sudo ip address add 192.0.2.10/27 dev testleases \ valid_lft 5 preferred_lft 5 sudo ip address add 192.0.2.11/27 dev testleases \ valid_lft 11 preferred_lft 11 ip address list dev testleases | \ grep -q 'inet 192.0.2.10/27 scope global dynamic testleases' \ && echo ok || echo not ok ip address list dev testleases | \ grep -q 'inet 192.0.2.11/27 scope global secondary dynamic testleases' \ && echo ok || echo not ok sleep 6 ip address list dev testleases | \ grep -q 'inet 192.0.2.11/27 scope global dynamic testleases' \ && echo ok || echo not ok sudo ip link del dev testleases [Regression Potential] * This changes the default kernel behaviour, previously upon expiry of the primary address, secondary addresses were removed as well. Which is imho silly. * comparing networkd renewal with isc-dhcp renewal the semantics are quite different. Upon acquiring new ip address, isc-dhcp would instantly flush existing ip address, and add a new one. Networkd add the new address as secondary, and waits for old one to expire first before promoting / switching to using the new ip address. IMHO kernel should have an API to promote secondary ip address to a primary one. * This update also applies other safe-looking options, which are currently also already applied via sysctls shipped in other packages # Source route verification net.ipv4.conf.default.rp_filter = 1 net.ipv4.conf.all.rp_filter = 1 # Do not accept source routing net.ipv4.conf.default.accept_source_route = 0 net.ipv4.conf.all.accept_source_route = 0 # Enable hard and soft link protection fs.protected_hardlinks = 1 fs.protected_symlinks = 1 * This update also applies the following upstream/bufferbloat.net recommended setting # Fair Queue CoDel packet scheduler to fight bufferbloat net.core.default_qdisc = fq_codel * [~racb] There are complex network setups out there, such as HA with corosync/pacemaker, OpenStack Neutron, and that kind of thing. If this fix were SRU'd, will all of these things in the wild cope with this sysctl change? [Other Info] * Original bug report Hi there, we found a replicable issue that involves the Ubuntu Core networking and causes complete loss of connectivity. We run a custom board with ubuntu core: the architecure is amrhf. We replicated this issue with an official Ubuntu Core image on a Raspberry Pi: other platform was been tested. It shows that it is a snap core problem which interests networkd: we use the default network stack based on networkd + netplan. Below steps to replicate the issue. 1)Setup a dhcp server for lease of about some minutes (i.e 10 minutes). 2)Boot the board and wait for get an ip from dhcp server 3)Before the lease expires, set a reservation for a different ip address Depending on lease duration before the lease expires( for 10 minute we have 2 minutes before ), networkd configure the new address in addition to the previous one. When the lease expire both ip address ( the prevoius and the new one ) disappear from the interested network interface. Depending on lease duration before the second lease expires ( for 10 minure we have 2 minutes before ) networkd configure only the new ip address on the network interface a
[Touch-packages] [Bug 1721223] Re: Networkd fail to set ip address between leases if ip address changes on UbuntuCore
Follow this instruction hope so you can solve your issue, Setup a DHCP server for the lease of about some minutes. Boot the board and wait to forget an IP from DHCP server. Before the lease expires, set a reservation for a different IP address. If anyone using Belkin router or any other router facing any problem regarding this get help from this www.belkinroutersupportnumber.com/ it really provides the best solution. -- 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/1721223 Title: Networkd fail to set ip address between leases if ip address changes on UbuntuCore Status in Snappy: Fix Committed Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Status in systemd source package in Zesty: Won't Fix Status in systemd source package in Artful: Fix Released Bug description: [Impact] * networkd fails to renew a lease, specifically it fails to change IPv4 address via DHCP renew/rebind. * networkd relies on a kernel feature to promote secondary IPv4 address to primary, upon primary address lease expiry. * this sysctl tunable was not enabled by default in systemd. [Test Case] Add a device, and assign two IPv4 addresses. First one, with a short lease time. Second one, with a different ip and a longer lease time. Second one should be treated as secondary ip address, and upon expiry of the first one, should be promoted and become primary ip address. The below scripted instructions simulate this: sudo ip link add name testleases type dummy sudo ip address add 192.0.2.10/27 dev testleases \ valid_lft 5 preferred_lft 5 sudo ip address add 192.0.2.11/27 dev testleases \ valid_lft 11 preferred_lft 11 ip address list dev testleases | \ grep -q 'inet 192.0.2.10/27 scope global dynamic testleases' \ && echo ok || echo not ok ip address list dev testleases | \ grep -q 'inet 192.0.2.11/27 scope global secondary dynamic testleases' \ && echo ok || echo not ok sleep 6 ip address list dev testleases | \ grep -q 'inet 192.0.2.11/27 scope global dynamic testleases' \ && echo ok || echo not ok sudo ip link del dev testleases [Regression Potential] * This changes the default kernel behaviour, previously upon expiry of the primary address, secondary addresses were removed as well. Which is imho silly. * comparing networkd renewal with isc-dhcp renewal the semantics are quite different. Upon acquiring new ip address, isc-dhcp would instantly flush existing ip address, and add a new one. Networkd add the new address as secondary, and waits for old one to expire first before promoting / switching to using the new ip address. IMHO kernel should have an API to promote secondary ip address to a primary one. * This update also applies other safe-looking options, which are currently also already applied via sysctls shipped in other packages # Source route verification net.ipv4.conf.default.rp_filter = 1 net.ipv4.conf.all.rp_filter = 1 # Do not accept source routing net.ipv4.conf.default.accept_source_route = 0 net.ipv4.conf.all.accept_source_route = 0 # Enable hard and soft link protection fs.protected_hardlinks = 1 fs.protected_symlinks = 1 * This update also applies the following upstream/bufferbloat.net recommended setting # Fair Queue CoDel packet scheduler to fight bufferbloat net.core.default_qdisc = fq_codel * [~racb] There are complex network setups out there, such as HA with corosync/pacemaker, OpenStack Neutron, and that kind of thing. If this fix were SRU'd, will all of these things in the wild cope with this sysctl change? [Other Info] * Original bug report Hi there, we found a replicable issue that involves the Ubuntu Core networking and causes complete loss of connectivity. We run a custom board with ubuntu core: the architecure is amrhf. We replicated this issue with an official Ubuntu Core image on a Raspberry Pi: other platform was been tested. It shows that it is a snap core problem which interests networkd: we use the default network stack based on networkd + netplan. Below steps to replicate the issue. 1)Setup a dhcp server for lease of about some minutes (i.e 10 minutes). 2)Boot the board and wait for get an ip from dhcp server 3)Before the lease expires, set a reservation for a different ip address Depending on lease duration before the lease expires( for 10 minute we have 2 minutes before ), networkd configure the new address in addition to the previous one. When the lease expire both ip address ( the prevoius and the new one ) disappear from the interested network interface. Depending on lease duration before the second lease expires ( for 10 minure we have 2 minutes before ) networkd configure only the new ip address on the network
[Touch-packages] [Bug 1704570] [NEW] [Inspiron 15-3555, Realtek ALC3234, Mic, Internal] Recording problem
Public bug reported: people over the other side cant hear voice ..something is wrong with input microphone ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67 Uname: Linux 4.4.0-79-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: bismi 1759 F...m pulseaudio /dev/snd/controlC1: bismi 1759 F pulseaudio /dev/snd/controlC0: bismi 1759 F pulseaudio CurrentDesktop: Unity Date: Sat Jul 15 21:05:30 2017 InstallationDate: Installed on 2017-02-15 (149 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic failed Symptom_Card: Built-in Audio - HD-Audio Generic Symptom_Jack: Mic, Internal Symptom_Type: None of the above Title: [Inspiron 15-3555, Realtek ALC3234, Mic, Internal] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/28/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.1 dmi.board.name: Inspiron 15-3555 dmi.board.vendor: Dell Inc. dmi.board.version: 1.0.1 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.0.1:bd01/28/2016:svnDellInc.:pnInspiron15-3555:pvrNotSpecified:rvnDellInc.:rnInspiron15-3555:rvr1.0.1:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 15-3555 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. ** 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/1704570 Title: [Inspiron 15-3555, Realtek ALC3234, Mic, Internal] Recording problem Status in alsa-driver package in Ubuntu: New Bug description: people over the other side cant hear voice ..something is wrong with input microphone ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67 Uname: Linux 4.4.0-79-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: bismi 1759 F...m pulseaudio /dev/snd/controlC1: bismi 1759 F pulseaudio /dev/snd/controlC0: bismi 1759 F pulseaudio CurrentDesktop: Unity Date: Sat Jul 15 21:05:30 2017 InstallationDate: Installed on 2017-02-15 (149 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic failed Symptom_Card: Built-in Audio - HD-Audio Generic Symptom_Jack: Mic, Internal Symptom_Type: None of the above Title: [Inspiron 15-3555, Realtek ALC3234, Mic, Internal] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/28/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.1 dmi.board.name: Inspiron 15-3555 dmi.board.vendor: Dell Inc. dmi.board.version: 1.0.1 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.0.1:bd01/28/2016:svnDellInc.:pnInspiron15-3555:pvrNotSpecified:rvnDellInc.:rnInspiron15-3555:rvr1.0.1:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 15-3555 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1704570/+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 603415] Re: Unity should have a screen magnifier
** Changed in: compiz
Assignee: Eleni Maria Stea (hikiko) => (unassigned)
** Changed in: nux
Assignee: Eleni Maria Stea (hikiko) => (unassigned)
** Changed in: unity
Assignee: Eleni Maria Stea (hikiko) => (unassigned)
** Changed in: compiz (Ubuntu)
Assignee: Eleni Maria Stea (hikiko) => (unassigned)
** Changed in: compiz (Ubuntu Xenial)
Assignee: Eleni Maria Stea (hikiko) => (unassigned)
** Changed in: nux (Ubuntu)
Assignee: Eleni Maria Stea (hikiko) => (unassigned)
** Changed in: nux (Ubuntu Xenial)
Assignee: Eleni Maria Stea (hikiko) => (unassigned)
** Changed in: unity (Ubuntu)
Assignee: Eleni Maria Stea (hikiko) => (unassigned)
** Changed in: unity (Ubuntu Xenial)
Assignee: Eleni Maria Stea (hikiko) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nux in Ubuntu.
https://bugs.launchpad.net/bugs/603415
Title:
Unity should have a screen magnifier
Status in Compiz:
In Progress
Status in Nux:
Triaged
Status in Unity:
Triaged
Status in compiz package in Ubuntu:
In Progress
Status in nux package in Ubuntu:
Confirmed
Status in unity package in Ubuntu:
Triaged
Status in compiz source package in Xenial:
In Progress
Status in nux source package in Xenial:
Confirmed
Status in unity source package in Xenial:
Fix Released
Bug description:
Binary package hint: gnome-control-center
In gnome-keybindings-properties, in the Accessibility section, there
are three entries by default: toggle magnifier, toggle screen reader,
and toggle on-screen keyboard. None of these work, whether or not
Assistive Technologies is currently running and whether or not orca is
currently running.
WHAT I EXPECT TO HAPPEN: I should be able to configure a shortcut to
any of these actions, such as Ctrl-Alt-A to the Toggle magnifier
action. Then, pressing, Ctrl-Alt-A will start the magnifier.
WHAT ACTUALLY HAPPENS: I am able to modify the entry in the gnome-
keybindings-properties window, but pressing the designated key does
not perform any action. That is, the magnifier does not open. Changing
the hotkeys for other actions works okay.
WHY THIS IS BAD: This is confusing and misleading behavior, and can be
especially damaging for people who need the accessibility features.
Ideally, the keybindings should be fixed, but otherwise they should be
removed from the dialog.
This is true under up-to-date Lucid 10.04 tested on several systems.
To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/603415/+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 1467695] Re: Alt-Grave (`) switcher has flickering/pulsing shadow artifacts
** Changed in: unity Assignee: Eleni Maria Stea (hikiko) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nux in Ubuntu. https://bugs.launchpad.net/bugs/1467695 Title: Alt-Grave (`) switcher has flickering/pulsing shadow artifacts Status in Nux: Triaged Status in Unity: Triaged Status in nux package in Ubuntu: Confirmed Status in unity package in Ubuntu: Triaged Status in nux source package in Xenial: Confirmed Status in unity source package in Xenial: Triaged Bug description: 1. Hold down Alt and keep it held down. 2. Press and release the key above Tab (Grave, or `). Keep alt held down. While Alt is held down, the drop shadows for the window or windows of the current application will keep building up and then going back to normal and building up again. It's almost as though the windows are being redrawn may times per second into a buffer without clearing it first each time (but clearing it every second or so). While this is happening, I notice that the drop shadow for the top bar does the same thing. This can also be observed if one uses Alt-Tab to select an app that has multiple windows that then expand out into a similar display. I've observed this on systems with Intel, NVIDIA, and ATI display hardware, so I don't think it's hardware-specific. All my Ubuntu systems have 2 or 3 monitors. I suspect multiple monitors are needed to reproduce this. To manage notifications about this bug go to: https://bugs.launchpad.net/nux/+bug/1467695/+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 1669632] [NEW] package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Public bug reported: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed ProblemType: Package DistroRelease: Ubuntu 16.10 Package: gconf2 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.8.0-39.42-generic 4.8.17 Uname: Linux 4.8.0-39-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 Date: Thu Mar 2 20:56:22 2017 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2016-04-10 (326 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.4 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to yakkety on 2017-03-03 (0 days ago) ** Affects: gconf (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check yakkety -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1669632 Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gconf package in Ubuntu: New Bug description: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed ProblemType: Package DistroRelease: Ubuntu 16.10 Package: gconf2 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.8.0-39.42-generic 4.8.17 Uname: Linux 4.8.0-39-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 Date: Thu Mar 2 20:56:22 2017 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2016-04-10 (326 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.4 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to yakkety on 2017-03-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1669632/+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 1636859] [NEW] I can't install new version 16.04.01
Public bug reported: I can't install new version 16.04.04 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-65.106-generic 3.13.11-ckt26 Uname: Linux 3.13.0-65-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1.8 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Oct 26 14:35:47 2016 DistUpgraded: 2016-10-26 14:21:40,067 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation G86 [GeForce 8300 GS] [10de:0423] (rev a1) (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:2421] InstallationDate: Installed on 2012-03-31 (1670 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) MachineType: Biostar 945GZ Micro 775 SE ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-65-generic root=UUID=41b1e648-a16a-4de6-ac88-ac89b64f11d9 ro splash quiet SourcePackage: xorg UpgradeStatus: Upgraded to vivid on 2016-10-26 (0 days ago) dmi.bios.date: 12/29/2006 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: 945GZ Micro 775 SE dmi.board.vendor: Biostar dmi.chassis.type: 3 dmi.chassis.vendor: Biostar dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd12/29/2006:svnBiostar:pn945GZMicro775SE:pvr:rvnBiostar:rn945GZMicro775SE:rvr:cvnBiostar:ct3:cvr: dmi.product.name: 945GZ Micro 775 SE dmi.sys.vendor: Biostar version.compiz: compiz 1:0.9.12.1+15.04.20150922-0ubuntu1 version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1~vivid2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1~vivid2 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Wed Oct 26 14:31:21 2016 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputSleep Button KEYBOARD, id 8 inputDell Dell USB Optical Mouse MOUSE, id 9 inputAT Translated Set 2 keyboard KEYBOARD, id 10 xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) NOUVEAU(0): [COPY] failed to allocate class. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.17.1-0ubuntu3.1 xserver.video_driver: nouveau ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 ubuntu vivid -- 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/1636859 Title: I can't install new version 16.04.01 Status in xorg package in Ubuntu: New Bug description: I can't install new version 16.04.04 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-65.106-generic 3.13.11-ckt26 Uname: Linux 3.13.0-65-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1.8 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Oct 26 14:35:47 2016 DistUpgraded: 2016-10-26 14:21:40,067 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation G86 [GeForce 8300 GS] [10de:0423] (rev a1) (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:2421] InstallationDate: Installed on 2012-03-31 (1670 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) MachineType: Biostar 945GZ Micro 775 SE ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-65-generic root=UUID=41b1e648-a16a-4de6-ac88-ac89b64f11d9 ro splash quiet SourcePackage: xorg UpgradeStatus: Upgraded to vivid on 2016-10-26 (0 days ago) dmi.bios.date: 12/29/2006 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: 945GZ Micro 775 SE dmi.board.vendor: Biostar dmi.chassis.type: 3 dmi.chassis.vendor: Biostar dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd12/29/2006:svnBiostar:pn945GZMicro775SE:pvr:rvnBiostar:rn945GZMicro775SE:rvr:cvnBiostar:ct3:cvr: dmi.product.name: 945GZ Micro 7
[Touch-packages] [Bug 1278223] Re: Mouse Flickering after adding 3rd Monitor
Having tried many, many solutions -something seems to work! Wait for the OS to boot up completely and then connect the displaylink Docking station attached to monitor! (Easier method is to hook up the docking station and the monitor on same power source and switch ON after the system has booted up!) But the resolution on the 3rd monitor is a low 1280X1024 on Linuxmint 18 Sara - 64bit - Cinnamon edition. -- 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/1278223 Title: Mouse Flickering after adding 3rd Monitor Status in xorg package in Ubuntu: Incomplete Status in xorg package in Fedora: Unknown Bug description: My issues is, after adding a 3rd monitor to Ubuntu 14.04, the mouse flickers (or blinks) when the cursor is on monitors one or two, but not 3. Monitor 1: 1440 x 900 - Laptop's Native Monitor Monitor 2: 1920 x 1080 - Laptop's HDMI Port's External Monitor Monitor 3: 1024 x 768 - SIIG USB 2.0 to VGA Pro Monitor Here's the video card that feeds my laptop's native monitor, monitor 2 (hdmi). lspci | grep 'VGA\|Display' 00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) 00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) The 3rd Monitor is powered through a Display Link certified SIIG USB 2.0 to VGA Pro adapter (A2H1320X1374 - not sure what this number, but it is a sticker on back of the device): lsusb -tv /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 6: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 6: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M dmesg [1.688343] usb 2-1: New USB device found, idVendor=17e9, idProduct=02ee [1.688348] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [1.688351] usb 2-1: Product: VGA Display Adapter [1.688353] usb 2-1: Manufacturer: DisplayLink [1.688356] usb 2-1: SerialNumber: 119785 Additionally, unity-control-center crashes sometimes after I "Restore previous settings", after selecting a resolution too high. This freezed my laptop, requiring a hard reboot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-control-center 14.04.1-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 9 18:43:13 2014 InstallationDate: Installed on 2014-02-02 (7 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140202) SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1278223/+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 1574042] Re: package python-minimal 2.7.11-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Changed in: python-defaults (Ubuntu) Status: New => Invalid ** Converted to question: https://answers.launchpad.net/ubuntu/+source/python-defaults/+question/292047 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1574042 Title: package python-minimal 2.7.11-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in python-defaults package in Ubuntu: Invalid Bug description: During upgrade my Ubuntu 15.10 to the new 16.04 LTS i take a few errors talking about python-minimal 2.7.11-1 saying failed to install/upgrade. For now the problem is: my unity not appear. Sorry for my bad English and thank you for help me. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-minimal 2.7.11-1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sat Apr 23 11:45:08 2016 DuplicateSignature: Setting up python-minimal (2.7.11-1) ... dpkg: error processing package python-minimal (--configure): subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-08-07 (260 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: python-defaults Title: package python-minimal 2.7.11-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2016-04-23 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1574042/+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 1574042] [NEW] package python-minimal 2.7.11-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: During upgrade my Ubuntu 15.10 to the new 16.04 LTS i take a few errors talking about python-minimal 2.7.11-1 saying failed to install/upgrade. For now the problem is: my unity not appear. Sorry for my bad English and thank you for help me. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-minimal 2.7.11-1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sat Apr 23 11:45:08 2016 DuplicateSignature: Setting up python-minimal (2.7.11-1) ... dpkg: error processing package python-minimal (--configure): subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-08-07 (260 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: python-defaults Title: package python-minimal 2.7.11-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2016-04-23 (0 days ago) ** Affects: python-defaults (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 python-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1574042 Title: package python-minimal 2.7.11-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in python-defaults package in Ubuntu: New Bug description: During upgrade my Ubuntu 15.10 to the new 16.04 LTS i take a few errors talking about python-minimal 2.7.11-1 saying failed to install/upgrade. For now the problem is: my unity not appear. Sorry for my bad English and thank you for help me. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-minimal 2.7.11-1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sat Apr 23 11:45:08 2016 DuplicateSignature: Setting up python-minimal (2.7.11-1) ... dpkg: error processing package python-minimal (--configure): subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-08-07 (260 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: python-defaults Title: package python-minimal 2.7.11-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2016-04-23 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1574042/+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 1313446] Re: window disappears on toggle shade
Hello, I am currently investigating this bug (and a list of other important bugs/features we have as well so, there's a lot of work to be done). When I or someone else in our team have a fix for it, the related branch will be linked to the bug report and every user who is subscribed will be notified. Please, be patient, it's in our priority list.. :) ** Changed in: unity Importance: Medium => Critical ** Changed in: unity (Ubuntu) Importance: Medium => Critical -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1313446 Title: window disappears on toggle shade Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: I used Unity Tweak Tool to enable Toggle Shade using middle click. When I click to top of the window, it rolls up and disappears. A "ghost" outline of the window appears and the only way to get the window back is by using Alt-tab. Sometimes, when reselecting the window using Alt-tab, Ubuntu freezes (crashes) and an internal error is generated. It seems to be related to Compiz but I'm not sure. An error report was generated and sent. Description: Ubuntu 14.04 LTS (64-bit) Release: 14.04 unity-tweak-tool 0.0.6ubuntu1 I expected the window would "roll up" and I'd be left with the window's top bar like with previous versions of Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1313446/+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 732784] Re: Moving window in Workspace Switcher doesn't work when gtk-recordmydesktop is running
** Changed in: gtk-recordmydesktop Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/732784 Title: Moving window in Workspace Switcher doesn't work when gtk- recordmydesktop is running Status in Compiz: Confirmed Status in gtk-recordmydesktop: Confirmed Status in Unity Foundations: Confirmed Status in compiz package in Ubuntu: Confirmed Status in gtk-recordmydesktop package in Ubuntu: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Ubuntu Natty alpha 3, all updates installed 1. Launch Desktop Recorder and choose "Record". 2. In the launcher, click "Workspace Switcher". 3. Try to drag any window to move it between workspaces. What happens: The window highlights but does not move. What should happen: The window moves, just like it would if Desktop Recorder wasn't running. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/732784/+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 1313446] Re: window disappears on toggle shade
** Changed in: unity Assignee: (unassigned) => Eleni Maria Stea (hikiko) ** Changed in: unity (Ubuntu) Assignee: (unassigned) => Eleni Maria Stea (hikiko) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1313446 Title: window disappears on toggle shade Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: I used Unity Tweak Tool to enable Toggle Shade using middle click. When I click to top of the window, it rolls up and disappears. A "ghost" outline of the window appears and the only way to get the window back is by using Alt-tab. Sometimes, when reselecting the window using Alt-tab, Ubuntu freezes (crashes) and an internal error is generated. It seems to be related to Compiz but I'm not sure. An error report was generated and sent. Description: Ubuntu 14.04 LTS (64-bit) Release: 14.04 unity-tweak-tool 0.0.6ubuntu1 I expected the window would "roll up" and I'd be left with the window's top bar like with previous versions of Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1313446/+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 732784] Re: Moving window in Workspace Switcher doesn't work when gtk-recordmydesktop is running
sorry correction: the screen was grabbed not the mouse -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/732784 Title: Moving window in Workspace Switcher doesn't work when gtk- recordmydesktop is running Status in Compiz: Confirmed Status in gtk-recordmydesktop: New Status in Unity Foundations: Confirmed Status in compiz package in Ubuntu: Confirmed Status in gtk-recordmydesktop package in Ubuntu: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Ubuntu Natty alpha 3, all updates installed 1. Launch Desktop Recorder and choose "Record". 2. In the launcher, click "Workspace Switcher". 3. Try to drag any window to move it between workspaces. What happens: The window highlights but does not move. What should happen: The window moves, just like it would if Desktop Recorder wasn't running. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/732784/+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 732784] Re: Moving window in Workspace Switcher doesn't work when gtk-recordmydesktop is running
Still present in wily and it seems that when I open the workspace switcher the mouse is grabbed and I can't switch back to the desktop mode. ** Changed in: unity (Ubuntu) Status: Invalid => Confirmed ** Changed in: compiz Importance: Undecided => Medium ** Changed in: compiz (Ubuntu) Importance: Undecided => Medium ** Changed in: unity (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/732784 Title: Moving window in Workspace Switcher doesn't work when gtk- recordmydesktop is running Status in Compiz: Confirmed Status in gtk-recordmydesktop: New Status in Unity Foundations: Confirmed Status in compiz package in Ubuntu: Confirmed Status in gtk-recordmydesktop package in Ubuntu: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Ubuntu Natty alpha 3, all updates installed 1. Launch Desktop Recorder and choose "Record". 2. In the launcher, click "Workspace Switcher". 3. Try to drag any window to move it between workspaces. What happens: The window highlights but does not move. What should happen: The window moves, just like it would if Desktop Recorder wasn't running. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/732784/+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 771632] Re: The strange 1px width windows appears after several days of working
We didn't manage to reproduce this bug, which is quite old therefore I changed its status to invalid. If you are having this issue in one of the supported Ubuntu releases (Natty is not supported anymore) please feel free to re-open a bug. Thank you! ** Changed in: compiz Status: Incomplete => Invalid ** Changed in: compiz (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/771632 Title: The strange 1px width windows appears after several days of working Status in Compiz: Invalid Status in Unity: Expired Status in compiz package in Ubuntu: Invalid Status in unity package in Ubuntu: Expired Bug description: After several days of working (with xorg modes switching, suspend-resume cycles) strange window appears in the screen. The window has shadows, but no buttons. The window can be activated, than context menu available (alt+space). Window can be resized and moved. Window has no icon on unity dock or in compiz switch window dialog. If resized - window border appears with buttons and black background. If i close window - unity closes to and restarts after several seconds and without that window. With compiz tools I fetch some info about this window: Window caption - Empty Window class - Empty Window type - "Unity" Window role - Empty Window name - Empty Screen-shoots attached. Systme: Natty (upgraded from maverick), nvidia current driver (gf 8200 mg) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/771632/+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 888872] Re: Unity 3D desktop crashes in Oneiric using ATI Mobility Radeon X1600
We couldn't reproduce this bug + oneiric is not supported anymore, therefore I set the status to Invalid. If you experience the same issue in any of the supported Ubuntu releases please feel free to reopen the bug and update the description. Thank you. ** Changed in: compiz Status: Incomplete => Invalid ** Changed in: unity Status: Incomplete => Invalid ** Changed in: unity (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/72 Title: Unity 3D desktop crashes in Oneiric using ATI Mobility Radeon X1600 Status in Compiz: Invalid Status in Unity: Invalid Status in unity package in Ubuntu: Invalid Status in xserver-xorg-video-ati package in Ubuntu: Expired Bug description: Summary: Unity 3D desktop crashes in Oneiric using ATI Mbility Radeon X1600 Problem: There doesn't seem to be rhyme or reason to this, be it having Firefox running, opening a link in Chromium to open in a new tab or watching a .flv video clip, using the subcontextual menus of Thunderbird, or watching videos in Totem. The desktop crashes bringing one to the login screen. Sometimes the desktop crashes as it's appearing. The last thing one sees is a black screen with text, and something about Pulseaudio, but I'm not sure it's an error as I see no red text (just white), and there's no time to read it before the login screen appears. Steps to reproduce: Login using Unity 3d. Use your system. Results The desktop crashes Login screen appears Expected results: No crashes. Comments: At one point I thought the problem was due to indicator-weather, but I removed it, and although crashes became less frequent, they increased drastically two days ago (after updating). This behaviour was non-existent in Natty. I went a whole day without this behaviour by logging in using Unity 2D, and went along using all the above apps to no crashes. I noticed there is a history of problems with Radeon video drivers, but they didn't describe this type of crash, and they seemed to be fixed in Natty, which makes me think it might not be a regression. The only other issue I can think of that might be related is that turning compiz plugins on and off (Widgets Layer, and Zoom Desktop), presumably the non-default one, crashes Unity. I looked into it and sources say that this could be an issue with my video card, which I find outrageous considering it's only a few years old (well within the 5 year margin for compiz support), which points to a faulty driver and/or lack of proper driver support. System Info lists my graphics support as Gallium 0.4 on ATI RV530. I found that odd. Wikipedia says that the my video card, although based on the RV530, is NOT the ATI RV530. So, I don't know if it's a matter of the wrong driver being assigned and there's no longer a Xorg.conf file to check, so I'm at a loss. Software Release Description: Ubuntu 11.10 Release: 11.10 Compiz Installed: 1:0.9.6+bzr20110929-0ubuntu5 compiz-plugins-main Installed: 1:0.9.6+bzr20110929-0ubuntu5 uname -r 3.0.0-12-generic Hardware First generation (2006) Intel MacBook Pro (Intel Core Duo, aka Yonah based processor) with an ATI Mbility Radeon X1600 video card. --- .tmp.unity.support.test.0: ApportVersion: 1.23-0ubuntu4 Architecture: i386 CompizPlugins: [core,bailer,detection,composite,opengl,decor,resize,imgpng,gnomecompat,place,session,compiztoolbox,snap,move,vpswitch,staticswitcher,regex,mousepoll,wall,animation,expo,fade,workarounds,scale,unityshell] CompositorRunning: None DistUpgraded: Log time: 2011-10-14 01:51:13.254265 DistroCodename: oneiric DistroRelease: Ubuntu 11.10 DistroVariant: ubuntu GraphicsCard: ATI Technologies Inc M56P [Radeon Mobility X1600] [1002:71c5] (prog-if 00 [VGA controller]) Subsystem: Apple Computer Inc. MacBook Pro [106b:0080] InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) MachineType: Apple Computer, Inc. MacBookPro1,1 Package: xserver-xorg-video-ati 1:6.14.99~git20110811.g93fc084-0ubuntu1 PackageArchitecture: i386 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-13-generic root=UUID=9c44e3b1-d6d1-4ca7-a621-c0142ded125a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6 Tags: oneiric ubuntu regression-update Uname: Linux 3.0.0-13-generic i686 UpgradeStatus: Upgraded to oneiric on 2011-10-14 (43 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 10/12/06 dmi.bios.vendor: Apple Computer, Inc. dmi.bios.version: MBP11.88Z.0055.B08.0610121325 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F425BEC8 dmi.board.vendor: Apple Computer, Inc. dmi.board.version: PVT dmi.ch
[Touch-packages] [Bug 943941] Re: GRID plugin very inconsistent and erratic behavior
Thank you for taking the time to report this bug. Since it's quite old and we didn't manage to reproduce it I changed the bug status to Invalid. If you experience the problem in one of the supported Ubuntu releases please feel free to re-open it and update the description. ** Changed in: compiz-plugins-main Status: New => Invalid ** Changed in: unity Status: Incomplete => Invalid ** Changed in: compiz-plugins-main (Ubuntu) Status: Confirmed => Invalid ** Changed in: unity (Ubuntu) Status: Incomplete => Invalid ** Changed in: compiz Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/943941 Title: GRID plugin very inconsistent and erratic behavior Status in Compiz: Invalid Status in Compiz Main Plugins: Invalid Status in Unity: Invalid Status in compiz-plugins-main package in Ubuntu: Invalid Status in unity package in Ubuntu: Invalid Bug description: Grid plugin inst working as it should . The experience is not even close to what we get from other OS ( Ms windows 7 ) . Im speaking like the bug is already confirmed because i got this one in every pc with ubuntu that im using with different hardware configurations. ( nvidia , ati , intel , blah blah ) so i know its there . It was affecting oneiric and still affecting precise. This should be consider as a feature not enabled by default because the experience is very bad (until is fixed). The grid is not enabled every time a window touch an side , it feels very random no matter how fast you are approaching the side or how many pixels are you pushing further of the screen edge. If you can manage to initiate grid most of the time instead of actual maximize the window you are only get the shadow effect maximized and stuck there. Im attaching a video with the problem because its a bit complicate to explain . ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.4.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6 Uname: Linux 3.2.0-17-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.93-0ubuntu2 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,regex,animation,snap,move,place,mousepoll,vpswitch,wall,resize,commands,gnomecompat,workarounds,compiztoolbox,grid,imgpng,expo,fade,ezoom,scale,session,scaleaddon,unityshell] Date: Thu Mar 1 13:32:34 2012 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to precise on 2012-02-16 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/943941/+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 1244225] Re: Display is unrefreshed/corrupted when opening/closing/switching windows and tabs
Thank you for taking the time to report this bug. Since the bug is quite old and we didn't manage to reproduce it, I mark it as invalid. If you still experience the same problem, please feel free to re-open it and update the description. ** Changed in: compiz Status: Incomplete => Invalid ** Changed in: unity Status: Incomplete => Invalid ** Changed in: unity (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1244225 Title: Display is unrefreshed/corrupted when opening/closing/switching windows and tabs Status in Compiz: Invalid Status in Unity: Invalid Status in unity package in Ubuntu: Invalid Bug description: When I switch between windows, or switch between tabs in the same window, or switch desktops, part or all of the affected windows often fail to repaint (or repaint and then revert to "stale" content). Unfocusing/refocusing the affected window usually forces it to repaint again (but may then leave another window "stale"). It doesn't seem toolkit-specific (happens with xchat, firefox, chrome, skype, gnome-terminal, ...). Attached is a screenshot showing an example of corruption after switching between two tabs in xchat. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.2+13.10.20131014.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 319.32 Wed Jun 19 15:51:20 PDT 2013 GCC version: gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu8) .tmp.unity: Error: [Errno 21] Is a directory: '/tmp/unity' .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,compiztoolbox,vpswitch,move,gnomecompat,grid,place,regex,imgpng,resize,annotate,mousepoll,wobbly,session,animation,fade,animationaddon,cube,rotate,workarounds,unitymtgrabhandles,cubeaddon,trailfocus,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu Oct 24 15:15:48 2013 DistUpgraded: 2013-10-18 10:50:28,943 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: nvidia-319, 319.32, 3.11.0-12-generic, x86_64: installedError! Could not locate dkms.conf file. File: does not exist. nvidia-319, 319.32, 3.8.0-31-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 420] [10de:0de2] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. Device [1462:2302] InstallationDate: Installed on 2011-05-11 (896 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) JockeyStatus: kmod:nvidia_319_updates - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) kmod:nvidia_304 - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) kmod:nvidia_304_updates - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) kmod:nvidia_319 - nvidia_319 (Proprietary, Enabled, Not in use) MachineType: Dell Inc. XPS 8300 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=0b19268c-a493-49b7-81d6-7249daf74712 ro quiet splash SourcePackage: unity UpgradeStatus: Upgraded to saucy on 2013-10-18 (6 days ago) dmi.bios.date: 02/15/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0Y2MRG dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd02/15/2011:svnDellInc.:pnXPS8300:pvr:rvnDellInc.:rn0Y2MRG:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: XPS 8300 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouve
[Touch-packages] [Bug 722830] Re: Windows creep cross the screen with ALT+TAB
** Changed in: compiz Status: New => Fix Committed ** Changed in: compiz Status: Fix Committed => Fix Released ** No longer affects: compiz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/722830 Title: Windows creep cross the screen with ALT+TAB Status in Compiz Core: Fix Released Status in Unity: Fix Released Status in unity package in Ubuntu: Fix Released Bug description: Binary package hint: unity ALT+TAB between windows. Observe that windows slowly creep across the screen. Observe attached video. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: unity 3.4.4-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.38-4.31-generic 2.6.38-rc5 Uname: Linux 2.6.38-4-generic x86_64 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,scale,session,unityshell] CompositorRunning: compiz Date: Mon Feb 21 21:42:46 2011 DistUpgraded: Yes, recently upgraded Log time: 2011-01-19 12:33:17.207056 DistroCodename: natty DistroVariant: ubuntu DkmsStatus: vboxhost, 3.2.12, 2.6.37-12-generic, x86_64: installed vboxhost, 3.2.12, 2.6.35-24-generic, x86_64: installed GraphicsCard: nVidia Corporation G71 [GeForce 7900 GT/GTO] [10de:0291] (rev a1) (prog-if 00 [VGA controller]) Subsystem: LeadTek Research Inc. Device [107d:2a62] InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) InstallationMedia_: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) LANG=en_GB.UTF-8 LC_MESSAGES=en_GB.utf8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-4-generic root=UUID=fb22b4e1-1576-4bf8-8272-15300bc7de38 ro quiet splash vt.handoff=7 ProcVersionSignature_: Ubuntu 2.6.38-4.31-generic 2.6.38-rc5 Renderer: Unknown SourcePackage: unity dmi.bios.date: 04/24/2009 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS P5N32-E SLI ACPI BIOS Revision 1801 dmi.board.name: P5N32-E SLI dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 1.XX dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSP5N32-ESLIACPIBIOSRevision1801:bd04/24/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N32-ESLI:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.2.1+glibmainloop4-0ubuntu11 version.libdrm2: libdrm2 2.4.23-1ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.1~git20110215.cc1636b6-0ubuntu2 version.xserver-xorg: xserver-xorg 1:7.6~3ubuntu6 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-1ubuntu9 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110107+b795ca6e-0ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/compiz-core/+bug/722830/+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 741869] Re: Unity/compiz intercepts Super and Alt keypresses from grabbed windows like VMs.
** Changed in: compiz (Ubuntu) Status: Triaged => Won't Fix ** Changed in: compiz Status: Triaged => Won't Fix ** Changed in: compiz Milestone: 0.9.11.0 => None -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/741869 Title: Unity/compiz intercepts Super and Alt keypresses from grabbed windows like VMs. Status in Ayatana Design: Fix Committed Status in Compiz: Won't Fix Status in Compiz Core: Triaged Status in OEM Priority Project: Won't Fix Status in OEM Priority Project precise series: Won't Fix Status in Unity: Fix Released Status in Unity 7.2 series: Fix Released Status in compiz package in Ubuntu: Won't Fix Status in unity package in Ubuntu: Fix Released Status in compiz source package in Trusty: Confirmed Status in unity source package in Trusty: Fix Released Bug description: [Impact] After upgrading from Maverick to Natty, I can no longer use the Super (windows) key in Virtual Machine Manager. Previously, as long as I had the Virtual Machine Manager console window in the foreground, I could press the Super key and the start menu would pop up. Since upgrading to Natty, this no longer works, and the search box appears in the upper left. Also see bug #934921 [Test Case] (1) Install virtualbox or virt-manager and qemu-system, create and boot a virtual machine (2) while in the virtual machine (and it should grab the keyboard), press the Super key Expected Result: the super key acts inside the VM (check by install unity on it or using xev) Buggy Result: the super key acts in the host and the Unity Dash is displayed [regression Potential]This patch plays with key grabs and ungrabs: the most likely potential for regression is (a) the existing grabs continue and no fix obtains or (2) the grab is not resumed when returning control from the VM and the Super key does not invoke the Unity Dash. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/741869/+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 734908] Re: Unity is visible on top of fullscreen apps
** Changed in: compiz (Ubuntu) Status: Confirmed => Invalid ** Changed in: compiz Status: Triaged => Invalid ** Changed in: compiz (Ubuntu Precise) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/734908 Title: Unity is visible on top of fullscreen apps Status in Ayatana Design: Fix Committed Status in Compiz: Invalid Status in Unity: Fix Released Status in Unity 5.0 series: Fix Released Status in Unity Distro Priority: Confirmed Status in compiz package in Ubuntu: Invalid Status in unity package in Ubuntu: Fix Released Status in compiz source package in Precise: Invalid Status in unity source package in Precise: Fix Released Bug description: [Test Case] 1. Start a fullscreen application (e.g. Firefox in Fullscreen mode) -> Verify that the panel is not visible [Regression Potential] Visual regressions, shell drawing problems. Part of a big change, many regression potentials. Original description: NOTE: This bug is only about the single monitor case. If you still have problems with multiple monitors, see bug 748539 instead. ORIGINAL DESCRIPTION: In natty alpha 3 up to date, I cannot get fullscreen in any application. Panels are still visible. Tested with: - totem - vlc - firefox - chrome - geany Unity panel and top bar are always on top. - Desired Solution: - When a window is fullscreen (note: this should not be confused with the *maximised* state) the menu bar should not be displayed. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/734908/+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 993204] Re: bottom of windows are not drawn
*** This bug is a duplicate of bug 981406 *** https://bugs.launchpad.net/bugs/981406 ** No longer affects: unity (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/993204 Title: bottom of windows are not drawn Status in Unity: Confirmed Bug description: Hi, if you open .po file in gtranslator (as maximized), there is place at bottom on screen, which displays window below gtranslator. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/993204/+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 993204] Re: bottom of windows are not drawn
*** This bug is a duplicate of bug 981406 *** https://bugs.launchpad.net/bugs/981406 We can't reproduce this bug or the original (#981406) one anymore and since it is also too old, I marked it as invalid. If you still experience this problem, please feel free to re-open a bug and give us some more information. Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/993204 Title: bottom of windows are not drawn Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Hi, if you open .po file in gtranslator (as maximized), there is place at bottom on screen, which displays window below gtranslator. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/993204/+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 1080619] Re: nux-widgets don't appear correctly
** Changed in: nux (Ubuntu) Status: In Progress => Won't Fix ** Changed in: nux Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nux in Ubuntu. https://bugs.launchpad.net/bugs/1080619 Title: nux-widgets don't appear correctly Status in Nux: Won't Fix Status in Nux Playground: Fix Committed Status in nux package in Ubuntu: Won't Fix Bug description: I built nuxplayground with nux trunk and ran the nux-widgets example: the spin buttons don't appear at all (see attached screenshot) and the buttons on the right side don't have the right appearence... To manage notifications about this bug go to: https://bugs.launchpad.net/nux/+bug/1080619/+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 1446165] Re: the skydome effect of the cube plugin doesn't work with unity 7
** Changed in: compiz Status: New => Fix Released ** Changed in: unity Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1446165 Title: the skydome effect of the cube plugin doesn't work with unity 7 Status in Compiz: Fix Released Status in Unity: Fix Released Status in unity package in Ubuntu: Fix Released Bug description: when running compiz + unity 7 the skydome doesn't appear correctly (looks like it has a weird transformation) screenshot: https://i.imgur.com/nnj4y1f.jpg To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1446165/+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 387828] Re: ALT+TAB with compiz shows really ugly icons for minimized windows
** Changed in: compiz Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/387828 Title: ALT+TAB with compiz shows really ugly icons for minimized windows Status in Ayatana Design: Fix Released Status in Compiz: Fix Released Status in One Hundred Papercuts: Won't Fix Status in Unity: Fix Released Status in compiz package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Status in Fedora: In Progress Bug description: Take a look at the screen-shot attached. When using tab switching, one require a nice icon to display. If those icons are too small, compiz scales them, this results in absolutely hideous icons. It especially happens when one of the application is minimized in the taskbar. This can happen for gnome-do as well at start-up. IMO, this impairs the visual impact, ubuntu wants people to have. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/387828/+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 301174] Re: Use proper sound event instead of system beep
** Changed in: compiz (Ubuntu) Status: Incomplete => Won't Fix ** Changed in: compiz Status: New => Won't Fix -- 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/301174 Title: Use proper sound event instead of system beep Status in Compiz: Won't Fix Status in compiz package in Ubuntu: Won't Fix Status in metacity package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Bug description: Binary package hint: gnome-control-center I installed Intrepid fresh onto this laptop (HP Pavilion dv9540us), and the alert sounds don't play. Instead, whenever I make one of the rather common mistakes that cause an alert sound (such as hitting backspace one too many times), there's a very loud, and very annoying, beep from the internal speaker. If I go to system->preferences->sound, where I would expect to disable the annoying beep, I find that the System Beep tab is now gone. I agree with this decision - this is 2008, we should never be using the internal speaker for anything. Especially not shutdown noises, where it's not even obvious how to disable it. After googling, however, I found that many others have this problem, and strangely enough the solution is to click "disable alert sounds" even though the alert sound itself never plays. So, there are two bugs here then: 1) The nice alert sound isn't used at all. I've never heard it in Ubuntu, only annoying PC speaker beeps. 2) We use the PC speaker instead of the alert sound, and disabling the PC speaker is difficult since we no longer have the system beep tab. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/301174/+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 324854] Re: DRI2: (UXA) white transparency artifacts with compiz [patch]
** No longer affects: compiz -- 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/324854 Title: DRI2: (UXA) white transparency artifacts with compiz [patch] Status in mesa package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Invalid Status in xserver-xorg-video-intel package in Ubuntu: Invalid Bug description: Binary package hint: xserver-xorg-video-intel 2:2.6.1-1ubuntu1 there are compiz issues when runining intel with UXA acceleration method: - when creating popup windows (the menu items) the background is for 1/10 s white and yellow - when running gksudo the screen does not become gray ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 9.04 Package: xserver-xorg-video-intel 2:2.6.1-1ubuntu1 ProcEnviron: LANG=it_IT.UTF-8 SHELL=/bin/bash ProcVersion: Linux version 2.6.28-6-generic (buildd@palmer) (gcc version 4.3.3 (Ubuntu 4.3.3-3ubuntu1) ) #17-Ubuntu SMP Fri Jan 30 15:34:36 UTC 2009 SourcePackage: xserver-xorg-video-intel Uname: Linux 2.6.28-6-generic i686 [lspci] 00:00.0 Host bridge [0600]: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub [8086:2a40] (rev 07) Subsystem: Dell Device [1028:0233] 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) Subsystem: Dell Device [1028:0233] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/324854/+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 1467695] Re: Alt-Grave (`) switcher has flickering/pulsing shadow artifacts
Thank you, the video of #1328053 was really helpful! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1467695 Title: Alt-Grave (`) switcher has flickering/pulsing shadow artifacts Status in Unity: Triaged Status in unity package in Ubuntu: Triaged Bug description: 1. Hold down Alt and keep it held down. 2. Press and release the key above Tab (Grave, or `). Keep alt held down. While Alt is held down, the drop shadows for the window or windows of the current application will keep building up and then going back to normal and building up again. It's almost as though the windows are being redrawn may times per second into a buffer without clearing it first each time (but clearing it every second or so). While this is happening, I notice that the drop shadow for the top bar does the same thing. This can also be observed if one uses Alt-Tab to select an app that has multiple windows that then expand out into a similar display. I've observed this on systems with Intel, NVIDIA, and ATI display hardware, so I don't think it's hardware-specific. All my Ubuntu systems have 2 or 3 monitors. I suspect multiple monitors are needed to reproduce this. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1467695/+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 1485727] Re: Corrupted unity desktop after resizing vbox/vmware window.
** Also affects: compiz Importance: Undecided Status: New ** Changed in: compiz Assignee: (unassigned) => Eleni Maria Stea (hikiko) ** Changed in: compiz Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1485727 Title: Corrupted unity desktop after resizing vbox/vmware window. Status in Compiz: New Status in Unity: In Progress Status in unity package in Ubuntu: In Progress Bug description: Probably it's possible to reproduce this bug even without using vbox/vmware. No problem running compiz witout unity. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1485727/+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 1467695] Re: Alt-Grave (`) switcher has flickering/pulsing shadow artifacts
** Changed in: unity Assignee: (unassigned) => Eleni Maria Stea (hikiko) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1467695 Title: Alt-Grave (`) switcher has flickering/pulsing shadow artifacts Status in Unity: Triaged Status in unity package in Ubuntu: Triaged Bug description: 1. Hold down Alt and keep it held down. 2. Press and release the key above Tab (Grave, or `). Keep alt held down. While Alt is held down, the drop shadows for the window or windows of the current application will keep building up and then going back to normal and building up again. It's almost as though the windows are being redrawn may times per second into a buffer without clearing it first each time (but clearing it every second or so). While this is happening, I notice that the drop shadow for the top bar does the same thing. This can also be observed if one uses Alt-Tab to select an app that has multiple windows that then expand out into a similar display. I've observed this on systems with Intel, NVIDIA, and ATI display hardware, so I don't think it's hardware-specific. All my Ubuntu systems have 2 or 3 monitors. I suspect multiple monitors are needed to reproduce this. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1467695/+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 1417611] [NEW] package libjasper1 1.900.1-debian1-2ubuntu0.1 failed to install/upgrade: unable to stat `./usr/share/doc/libjasper1' (which I was about to install): Input/output e
Public bug reported: Every time I start the computer this error occurs. ProblemType: Package DistroRelease: Ubuntu 14.10 Package: libjasper1 1.900.1-debian1-2ubuntu0.1 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.1 AptOrdering: libjasper1: Install libjasper1: Configure Architecture: amd64 Date: Tue Jan 27 18:17:29 2015 DpkgTerminalLog: Preparing to unpack .../libjasper1_1.900.1-debian1-2ubuntu0.2_amd64.deb ... Unpacking libjasper1:amd64 (1.900.1-debian1-2ubuntu0.2) over (1.900.1-debian1-2ubuntu0.1) ... dpkg: error processing archive /var/cache/apt/archives/libjasper1_1.900.1-debian1-2ubuntu0.2_amd64.deb (--unpack): unable to stat `./usr/share/doc/libjasper1' (which I was about to install): Input/output error DuplicateSignature: package:libjasper1:1.900.1-debian1-2ubuntu0.1:unable to stat `./usr/share/doc/libjasper1' (which I was about to install): Input/output error ErrorMessage: unable to stat `./usr/share/doc/libjasper1' (which I was about to install): Input/output error InstallationDate: Installed on 2014-11-30 (65 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: jasper Title: package libjasper1 1.900.1-debian1-2ubuntu0.1 failed to install/upgrade: unable to stat `./usr/share/doc/libjasper1' (which I was about to install): Input/output error UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: jasper (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to jasper in Ubuntu. https://bugs.launchpad.net/bugs/1417611 Title: package libjasper1 1.900.1-debian1-2ubuntu0.1 failed to install/upgrade: unable to stat `./usr/share/doc/libjasper1' (which I was about to install): Input/output error Status in jasper package in Ubuntu: New Bug description: Every time I start the computer this error occurs. ProblemType: Package DistroRelease: Ubuntu 14.10 Package: libjasper1 1.900.1-debian1-2ubuntu0.1 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.1 AptOrdering: libjasper1: Install libjasper1: Configure Architecture: amd64 Date: Tue Jan 27 18:17:29 2015 DpkgTerminalLog: Preparing to unpack .../libjasper1_1.900.1-debian1-2ubuntu0.2_amd64.deb ... Unpacking libjasper1:amd64 (1.900.1-debian1-2ubuntu0.2) over (1.900.1-debian1-2ubuntu0.1) ... dpkg: error processing archive /var/cache/apt/archives/libjasper1_1.900.1-debian1-2ubuntu0.2_amd64.deb (--unpack): unable to stat `./usr/share/doc/libjasper1' (which I was about to install): Input/output error DuplicateSignature: package:libjasper1:1.900.1-debian1-2ubuntu0.1:unable to stat `./usr/share/doc/libjasper1' (which I was about to install): Input/output error ErrorMessage: unable to stat `./usr/share/doc/libjasper1' (which I was about to install): Input/output error InstallationDate: Installed on 2014-11-30 (65 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: jasper Title: package libjasper1 1.900.1-debian1-2ubuntu0.1 failed to install/upgrade: unable to stat `./usr/share/doc/libjasper1' (which I was about to install): Input/output error UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jasper/+bug/1417611/+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 1383485] [NEW] when a locale is not set unity8-dash fails to start
Public bug reported: I tried to run Unity8 on a system where the LC_ALL locale was not set (LC_ALL=). The dash couldn't be loaded and the initial screen (with the "loading scopes" message) was flickering. When I checked the .cache/upstart/unity8-dash.log there was the following error message: ERROR! Caught unity::scopes::ConfigException: Cannot instantiate run time for client, config file: : unity::scopes::MiddlewareException: cannot initialize zmq middleware for scope c-337f8282: locale::facet::_S_create_c_locale name not When I manually set the locale to en_US.UTF-8 unity8 started normally. ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1383485 Title: when a locale is not set unity8-dash fails to start Status in “unity8” package in Ubuntu: New Bug description: I tried to run Unity8 on a system where the LC_ALL locale was not set (LC_ALL=). The dash couldn't be loaded and the initial screen (with the "loading scopes" message) was flickering. When I checked the .cache/upstart/unity8-dash.log there was the following error message: ERROR! Caught unity::scopes::ConfigException: Cannot instantiate run time for client, config file: : unity::scopes::MiddlewareException: cannot initialize zmq middleware for scope c-337f8282: locale::facet::_S_create_c_locale name not When I manually set the locale to en_US.UTF-8 unity8 started normally. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1383485/+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 1356994] Re: Workspace Switcher: dragging an application window between workspaces locks up
** Changed in: unity Assignee: (unassigned) => Eleni Maria Stea (hikiko) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1356994 Title: Workspace Switcher: dragging an application window between workspaces locks up Status in Unity: New Status in “unity” package in Ubuntu: New Bug description: System: Ubuntu 14.04 amd-64 2GB RAM Linux 3.13.0-34-generic #60-Ubuntu SMP Wed Aug 13 15:45:27 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Bug: When opening the multiple desktops view, attempting to drag an application from one quadrant to another makes the system unresponsive to inputs. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CurrentDesktop: Unity Date: Thu Aug 14 12:10:59 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-08-12 (1 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-08-12 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1356994/+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 1349281] Re: The exposed open windows are displayed in the correct order
** Changed in: unity Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1349281 Title: The exposed open windows are displayed in the correct order Status in Unity: In Progress Status in “unity” package in Ubuntu: New Bug description: When multiple non-maximised windows of the same program are open and one clicks on the icon of the program in the launcher, they are all shown one next to each other but in the wrong order: windows that are in the top-left corner can be shown in the right bottom position or on the top bottom corner. This makes very hard to switch between similarly looking windows like terminals. How to reproduce: * launch four or so terminal windows; * write something different on each of them to be able to tell them apart; * move each window to a different corner, possibly using the auto-resizing feature of Unity; * click on the terminal icon in the launcher; * many terminal windows are displayed; * choose the thumbnail in the right-top corner; * very likely a window that was in another corner has been selected; * try again various time and realize how confusing this all is. The thing that is more strange is that you have to move the mouse pointer to a certain point (let's say "right-top"), then you see the window has appeared far away (let's say "bottom-left") so you have to move your mouse again. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1349281/+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 1349281] Re: The exposed open windows are displayed in the correct order
** Branch linked: lp:~hikiko/unity/unity.1349281 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1349281 Title: The exposed open windows are displayed in the correct order Status in Unity: Confirmed Status in “unity” package in Ubuntu: New Bug description: When multiple non-maximised windows of the same program are open and one clicks on the icon of the program in the launcher, they are all shown one next to each other but in the wrong order: windows that are in the top-left corner can be shown in the right bottom position or on the top bottom corner. This makes very hard to switch between similarly looking windows like terminals. How to reproduce: * launch four or so terminal windows; * write something different on each of them to be able to tell them apart; * move each window to a different corner, possibly using the auto-resizing feature of Unity; * click on the terminal icon in the launcher; * many terminal windows are displayed; * choose the thumbnail in the right-top corner; * very likely a window that was in another corner has been selected; * try again various time and realize how confusing this all is. The thing that is more strange is that you have to move the mouse pointer to a certain point (let's say "right-top"), then you see the window has appeared far away (let's say "bottom-left") so you have to move your mouse again. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1349281/+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 1349281] Re: The exposed open windows are displayed in the correct order
** Changed in: unity Assignee: (unassigned) => Eleni Maria Stea (hikiko) ** Changed in: unity Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1349281 Title: The exposed open windows are displayed in the correct order Status in Unity: Confirmed Status in “unity” package in Ubuntu: New Bug description: When multiple non-maximised windows of the same program are open and one clicks on the icon of the program in the launcher, they are all shown one next to each other but in the wrong order: windows that are in the top-left corner can be shown in the right bottom position or on the top bottom corner. This makes very hard to switch between similarly looking windows like terminals. How to reproduce: * launch four or so terminal windows; * write something different on each of them to be able to tell them apart; * move each window to a different corner, possibly using the auto-resizing feature of Unity; * click on the terminal icon in the launcher; * many terminal windows are displayed; * choose the thumbnail in the right-top corner; * very likely a window that was in another corner has been selected; * try again various time and realize how confusing this all is. The thing that is more strange is that you have to move the mouse pointer to a certain point (let's say "right-top"), then you see the window has appeared far away (let's say "bottom-left") so you have to move your mouse again. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1349281/+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 1373345] Re: Clicking on windows and continuingly pressing menu key on keyboard opens infinite windows and locks all keyboard/mouse clicks
Thanks for the bug report. I can't reproduce this bug, is it possible that you have set some keyboard shortcuts that might cause this behavior? Also, could you explain what you mean by "alignment window"? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1373345 Title: Clicking on windows and continuingly pressing menu key on keyboard opens infinite windows and locks all keyboard/mouse clicks Status in Unity: New Status in “unity” package in Ubuntu: New Bug description: The bug happens when I clicked on desktop and pressed menu bar but pressed too many times and many alignment windows opened on top of right click window. I closed these alignment windows then I realized shortcuts and mouse clicks don't respond but for example holding windows button opens keyboard shortcuts window. Sorry if the attached bug report is not because of this bug but I followed guidelines and generated report using given commands. I can produce the bug whenever I want but whole system locks down and I need to use ctrl alt f1 consoles to restart (yes they work well) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.4 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: Wed Sep 24 12:46:35 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:3501] Subsystem: CLEVO/KAPOK Computer Device [1558:3501] InstallationDate: Installed on 2014-07-08 (77 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: MONSTER ABRA A7 V1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=77f4514d-790c-45aa-8351-3a5c14fc0124 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/08/2014 dmi.bios.vendor: MONSTER dmi.bios.version: ABRA A7 V1 dmi.board.asset.tag: Tag 12345 dmi.board.name: ABRA A7 V1 dmi.board.vendor: MONSTER dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: MONSTER dmi.chassis.version: N/A dmi.modalias: dmi:bvnMONSTER:bvrABRAA7V1:bd04/08/2014:svnMONSTER:pnABRAA7V1:pvrNotApplicable:rvnMONSTER:rnABRAA7V1:rvrNotApplicable:cvnMONSTER:ct9:cvrN/A: dmi.product.name: ABRA A7 V1 dmi.product.version: Not Applicable dmi.sys.vendor: MONSTER version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Wed Sep 24 12:33:00 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id8685 vendor AUO xserver.version: 2:1.15.1-0ubuntu2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1373345/+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 1310518] Re: Touch screen and touchpad lost click function after quickly tapped dash home repeatly by touch screen
My findings about this bug, so far:
The problem is that there's a mouse grab by compiz at some point, that is
caused by the XGrabButton call in updatePassiveButtonGrabs in window.cpp:
[...]
else
{
/* Grab all buttons */
XGrabButton (screen->dpy (),
AnyButton,
AnyModifier,
serverFrame, false,
ButtonPressMask | ButtonReleaseMask | ButtonMotionMask,
GrabModeSync,
GrabModeAsync,
None,
None);
[...]
(I verified that this by replacing the default mouse pointer shape with
the XC_pirate: when the bug occured the pointer changed to a pirate
head.)
This grab is used by compiz for windows that don't have the focus: when
the user clicks inside a window, compiz grabs the mouse so that the
mouse events are handled by compiz and not by the window. That's useful
in case someone needs to raise a window by clicking on it as opposed to
clicking on its frame for example.
The XGrabButton uses the GrabModeSync. According to the XGrabPointer manpage:
if the pointer mode is GrabModeSync the state of the pointer, as seen by client
applications, appears to freeze, and the X server generates no further pointer
events until the grabbing client calls XAllowEvents or until the pointer grab
is released. Actual pointer changes are not lost while the pointer is frozen;
they are simply queued in the server for later processing.
(that's why we can't click anywhere after this grab occurs)
I believe that a race condition related to the grabs/ungrabs is
triggered here and it's difficult to be found because the passive grab
is initiated by the xserver when the conditions set by the XGrabButton
call are satisfied, so backtraces are not really helpful.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1310518
Title:
Touch screen and touchpad lost click function after quickly tapped
dash home repeatly by touch screen
Status in OEM Priority Project:
Triaged
Status in OEM Priority Project precise series:
New
Status in OEM Priority Project trusty series:
New
Status in Unity:
Triaged
Status in Unity 7.2 series:
Triaged
Status in “unity” package in Ubuntu:
Triaged
Bug description:
Touch screen and touchpad lost click function after quickly tapped
dash home repeatly by touch screen, Installed 14.04, still have same
issue.
Quickly tapped dash home more than three times by touch screen.Found
touch screen and touchpad lost click function.
Note:
1.When this issue occured, cursor still can be moved by touch screen/touchpad.
2.When this issue occured ,click/double click by touch screen/touchpad,left
click/right click by touchpad all were not workable.
Steps to Reproduce:
1.install 12.04.4 image or 14.04 image, boot into Ubuntu OS.
2.Quickly tapped dash home more than three times by touch screen.
3.Found touch screen and touchpad lost click function.
This bug is reported from private OEM project, also check
https://launchpad.net/bugs/1297067
==
using xinput --query-state can actually see the button press event
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ syntp id=6[slave pointer (2)]
⎜ ↳ ELAN Touchscreen id=11[slave pointer (2)]
#xinput --query-state 11
2 classes :
ButtonClass
button[1]=up
button[2]=up
button[3]=up
button[4]=up
button[5]=up
ValuatorClass Mode=Absolute Proximity=In
valuator[0]=398
valuator[1]=1652
valuator[2]=5
valuator[3]=3
valuator[4]=0
valuator[5]=399
valuator[6]=1653
#xinput --query-state 6
2 classes :
ButtonClass
button[1]=down
button[2]=up
button[3]=up
button[4]=up
button[5]=up
button[6]=up
button[7]=up
button[8]=up
ValuatorClass Mode=Relative Proximity=In
valuator[0]=1
valuator[1]=394
touchpad's button and touchpanel's
valuator[2] and valuator[3] will changed after we press the button (or
monitor)
Also I found press "super" on keyboard will recover the
touchscreen/touchpad loss.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: unity 5.20.0-0ubuntu3
ProcVersionSignature: Ubuntu 3.11.0-18.32~precise1-generic 3.11.10.4
Uname: Linux 3.11.0-18-generic x86_64
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
CompizPlugins:
[core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
Date: Mon Apr 21 16:50:04 2014
DistributionChannelDescriptor:
# This is a distribution channel descriptor
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-stella-daan2-precise-amd64-20140416-1
InstallationMedia: Ubuntu 12.04 "Precise"
[Touch-packages] [Bug 1310518] Re: Touch screen and touchpad lost click function after quickly tapped dash home repeatly by touch screen
Some additional observations: I usually reproduce this bug on my desktop pc that doesnt have a touchpad/trackball (mouse only) by moving the cursor inside the launcher area while this command from comment #3 is executed: $ sudo evemu-play /dev/input/event# < s.event (the comment: https://bugs.launchpad.net/oem-priority/+bug/1310518/comments/3) i.imgur.com/rtXckuE.jpg In the screenshot above I got the bug while I was switching workspaces and in this case alt+tab doesn't restore the mouse click. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1310518 Title: Touch screen and touchpad lost click function after quickly tapped dash home repeatly by touch screen Status in OEM Priority Project: Triaged Status in OEM Priority Project precise series: New Status in OEM Priority Project trusty series: New Status in Unity: Triaged Status in Unity 7.2 series: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: Touch screen and touchpad lost click function after quickly tapped dash home repeatly by touch screen, Installed 14.04, still have same issue. Quickly tapped dash home more than three times by touch screen.Found touch screen and touchpad lost click function. Note: 1.When this issue occured, cursor still can be moved by touch screen/touchpad. 2.When this issue occured ,click/double click by touch screen/touchpad,left click/right click by touchpad all were not workable. Steps to Reproduce: 1.install 12.04.4 image or 14.04 image, boot into Ubuntu OS. 2.Quickly tapped dash home more than three times by touch screen. 3.Found touch screen and touchpad lost click function. This bug is reported from private OEM project, also check https://launchpad.net/bugs/1297067 == using xinput --query-state can actually see the button press event ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ syntp id=6[slave pointer (2)] ⎜ ↳ ELAN Touchscreen id=11[slave pointer (2)] #xinput --query-state 11 2 classes : ButtonClass button[1]=up button[2]=up button[3]=up button[4]=up button[5]=up ValuatorClass Mode=Absolute Proximity=In valuator[0]=398 valuator[1]=1652 valuator[2]=5 valuator[3]=3 valuator[4]=0 valuator[5]=399 valuator[6]=1653 #xinput --query-state 6 2 classes : ButtonClass button[1]=down button[2]=up button[3]=up button[4]=up button[5]=up button[6]=up button[7]=up button[8]=up ValuatorClass Mode=Relative Proximity=In valuator[0]=1 valuator[1]=394 touchpad's button and touchpanel's valuator[2] and valuator[3] will changed after we press the button (or monitor) Also I found press "super" on keyboard will recover the touchscreen/touchpad loss. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.20.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.11.0-18.32~precise1-generic 3.11.10.4 Uname: Linux 3.11.0-18-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 CompizPlugins: [core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Mon Apr 21 16:50:04 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-daan2-precise-amd64-20140416-1 InstallationMedia: Ubuntu 12.04 "Precise" - Failed to find casper uuid.conf in 'binary/casper/initrd.img-3.11.0-18-generic.old-dkms' LIVE Binary 20140416-06:52 MarkForUpload: True ProcEnviron: LANGUAGE=en_US: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1310518/+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
