[Touch-packages] [Bug 1180646] Re: cairo-dock rendering issues using openGL backend on intel GPU
** Tags added: bios-outdated-a14 -- 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/1180646 Title: cairo-dock rendering issues using openGL backend on intel GPU Status in Mesa: Fix Released Status in mesa package in Ubuntu: Triaged Bug description: what is this bug ? when i had ubuntu 11.10 , i had a big slow motion that affect even the youtube videos and overall performance . and the error was the opengl, i know that because its version name was missing on 11.10 , any way after upgrade to 12.04 i though the error gone, and it does , my laptop was 10x faster . but i can't run cairo-dock in opengl mode !!!. the ghost came back :( old ubuntu 11.10 bug http://imageshack.us/photo/my-images/259/xorg.png/ new ubuntu 12.04 bug (the one i have right now ) http://imageshack.us/photo/my-images/844/screenshotfrom201305160.png/ my additional drivers pic here before upgrade from ubuntu 11.10 to 12.04 http://img94.imageshack.us/img94/8410/delldrivers.png after the upgrade http://imageshack.us/photo/my-images/39/screenshotfrom201305160.png/ - i have posted on the cairo-dock forums and they responded that this a common eror on hd 4000 and they sent me that link https://bugs.freedesktop.org/show_bug.cgi?id=55036 i looked at it and i found """Component:Drivers/DRI/i965""" i have read some on the report uploaded and i feel like i have mix between i915 and i965 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-43.68-generic 3.2.42 Uname: Linux 3.2.0-43-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu17.2 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,workarounds,scale,expo,ezoom,dbus] CompositorRunning: None Date: Thu May 16 05:17:18 2013 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-oneiric-amd64-2016-1 DistroCodename: precise DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Ivy Bridge Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0569] InstallationMedia: Ubuntu 11.10 "Oneiric" - Build amd64 LIVE Binary 2016-18:24 MachineType: Dell Inc. Inspiron 5520 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-43-generic root=UUID=8b64b4b3-8de9-43d7-b1c8-7f9ff701ac70 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to precise on 2013-05-05 (10 days ago) dmi.bios.date: 08/13/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 04G65K dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A09 dmi.modalias: dmi:bvnDellInc.:bvrA09:bd08/13/2012:svnDellInc.:pnInspiron5520:pvrA09:rvnDellInc.:rn04G65K:rvrA02:cvnDellInc.:ct8:cvrA09: dmi.product.name: Inspiron 5520 dmi.product.version: A09 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.7.12-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.43-0ubuntu0.0.1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.1-0ubuntu1~precise version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental 9.0.1-0ubuntu1~precise version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.1-0ubuntu1~precise version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.13 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1.2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.0-0ubuntu0~precise1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build3 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1180646/+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 1551351] Re: dhclient does not renew leases
@Dough, yes, so basically did not renew but obtained a new lease (which sensibly is the same IP as before). And while the dhcp server still wonders why a client ask for some IP _again_, it also silently marks the lease time as extended for another period. And since the old clients do not die (but play dead), you accumulate a new copy every time you run it (including the initial one). @Seth, thanks for the link. Reading through it I think it is not only potentially but very much the problem we got. The upload of isc-dhcp that started the breakage was very likely the one "no change rebuild" that was done after upgrading to bind9(.19). Sounds like one needs to manually twiddle the build back so isc-dhcp gets a bind9 lib that has threads and epoll disabled (as a work-around). Not sure how quickly that can be done. This may still have problems on terminating the process, so maybe needs adaptation of ifdown hooks as well. But that needs to be seen. First goal is to get dhclient/-server back working. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1551351 Title: dhclient does not renew leases Status in isc-dhcp package in Ubuntu: Confirmed Status in isc-dhcp source package in Xenial: Confirmed Bug description: Release: Xenial I think this only recently started after some bind9 updates triggered a rebuild. When booting dhclient gets started and acquires an IP address, but it does seem to lock up somewhere as it does not renew the lease. In my environment I set the lease time to 5 minutes, so I notice such things rather soon. I looked on the dhcp server side but saw any further dhcp messages come in from the client side. Related bugs: * bug 1551415: systemctl stop networking hang / timeout ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: isc-dhcp-client 4.3.3-5ubuntu8 ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3 Uname: Linux 4.4.0-9-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Mon Feb 29 12:32:52 2016 DhclientLeases: SourcePackage: isc-dhcp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1551351/+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 1176327] Re: Compiz crashes on a daily basis, will not restart
Mikko Rauhala, thank you for reporting this and helping make Ubuntu better. As per https://wiki.ubuntu.com/Releases, Ubuntu 13.04 reached EOL on January 27, 2014. Is this reproducible on a supported release? ** Tags added: bios-outdated-2102 ** Changed in: mesa (Ubuntu) Importance: Undecided => Low ** Changed in: mesa (Ubuntu) Status: Confirmed => Incomplete -- 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/1176327 Title: Compiz crashes on a daily basis, will not restart Status in mesa package in Ubuntu: Incomplete Bug description: After upgrading to 13.04, compiz crashes pretty much on a daily basis. At least once on making mplayer go full screen, and sometimes even when the computer is just left alone (possibly triggered by screensaver). Unity panels disappear as well. I generally have a leftover undecorated terminal to try to do recovery from, but compiz won't even restart, I have to kill my session and start over from scratch (a reboot is not necessary, however). Killing the leftover decorator and *unity* and *indicator* processes had no effect in restarting attempts. Pending a solution, even a hint what needs cleaning up for a clean restart of compiz without having to exit the whole session would be welcome. IIRC I tried to start metacity once and it started, though was less than fully useful. Here's what comes out when trying to restart it; at first it seems to think that Unity isn't hardware supported, but it is, on the radeon driver: OpenGL renderer string: Gallium 0.4 on AMD RV770. That'll get cleared up on killing the decorator. Incidentally, the panel crash indicator asked if I want to report this but then just sat there for a while and quit without doing anything... This is manually through ubuntu-bug. mjr@phantom:~$ compiz & [1] 21295 mjr@phantom:~$ compiz (core) - Info: Loading plugin: core compiz (core) - Info: Starting plugin: core compiz (core) - Info: Loading plugin: ccp compiz (core) - Info: Starting plugin: ccp compizconfig - Info: Backend : gsettings compizconfig - Info: Integration : true compizconfig - Info: Profile : unity compiz (core) - Info: Loading plugin: composite compiz (core) - Info: Starting plugin: composite compiz (core) - Info: Loading plugin: opengl compiz (core) - Info: Unity is not supported by your hardware. Enabling software rendering instead (slow). compiz (core) - Info: Unity is fully supported by your hardware. compiz (core) - Info: Starting plugin: opengl compiz (core) - Info: Loading plugin: decor compiz (core) - Info: Starting plugin: decor compiz (core) - Info: Loading plugin: gnomecompat compiz (core) - Info: Starting plugin: gnomecompat compiz (core) - Info: Loading plugin: grid compiz (core) - Info: Starting plugin: grid compiz (core) - Info: Loading plugin: place compiz (core) - Info: Starting plugin: place compiz (core) - Info: Loading plugin: imgpng compiz (core) - Info: Starting plugin: imgpng compiz (core) - Info: Loading plugin: compiztoolbox compiz (core) - Info: Starting plugin: compiztoolbox compiz (core) - Info: Loading plugin: copytex compiz (core) - Info: Starting plugin: copytex compiz (core) - Info: Loading plugin: session compiz (core) - Info: Starting plugin: session compiz (core) - Info: Loading plugin: mousepoll compiz (core) - Info: Starting plugin: mousepoll compiz (core) - Info: Loading plugin: move compiz (core) - Info: Starting plugin: move compiz (core) - Info: Loading plugin: regex compiz (core) - Info: Starting plugin: regex compiz (core) - Info: Loading plugin: snap compiz (core) - Info: Starting plugin: snap compiz (core) - Info: Loading plugin: resize compiz (core) - Info: Starting plugin: resize compiz (core) - Info: Loading plugin: vpswitch compiz (core) - Info: Starting plugin: vpswitch compiz (core) - Info: Loading plugin: animation compiz (core) - Info: Starting plugin: animation compiz (core) - Info: Loading plugin: unitymtgrabhandles compiz (core) - Info: Starting plugin: unitymtgrabhandles compiz (core) - Info: Loading plugin: workarounds compiz (core) - Info: Starting plugin: workarounds compiz (core) - Info: Loading plugin: wall compiz (core) - Info: Starting plugin: wall compiz (core) - Info: Loading plugin: expo compiz (core) - Info: Starting plugin: expo compiz (core) - Info: Loading plugin: fade compiz (core) - Info: Starting plugin: fade compiz (core) - Info: Loading plugin: scale compiz (core) - Info: Starting plugin: scale compiz (core) - Info: Loading plugin: ezoom compiz (core) - Info: Starting plugin: ezoom compiz (core) - Info: Loading plugin: unityshell compiz (core) - Info: Starting plugin: unityshell WARN 2013-05-04 13:57:50 unity.glib.dbus.server GLibDBusServer.cpp:580 Can't register
[Touch-packages] [Bug 1350598] Re: AppArmor policy compile improvements
It would be ultra-cool to get a solution that has tolerable overhead on first boot. In effect, if we can't touch the apparmor profiles, that means that we can't evolve our code. Not being able to add a new dbus method to a service can be a show stopper for new features, for example. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1350598 Title: AppArmor policy compile improvements Status in AppArmor: Triaged Status in Canonical System Image: Confirmed Status in apparmor package in Ubuntu: Triaged Bug description: apparmor_parser can take a long time to compile policy especially when there is a lot of policy, so we want to utilize compiled cache profile as much as possible. Cache files will have to be regenerated in the following cases: * the kernel .features file is updated (eg, new features are added to apparmor in the new kernel) * apparmor itself is updated * on devices with click packages, apparmor-easyprof-ubuntu and/or click-apparmor is updated As of 2014-10-02, what can be expected is: - Systems with system-image updates (eg, Ubuntu Touch): - First boot will use the precompiled cache files in the rootfs or custom tarball and be fast - Reboots will use the cache files on the device and be fast - First boots after upgrades will use the cache files on the device if the above conditions are not met and be fast - Production devices will not meet any of those conditions except under exceptional and rare circumstances (eg, major OS upgrades like 14.10 to 15.04) and be fast - First boots after upgrades that meet one of the conditions will need to regenerate the cache. This can happen on development releases where the kernel features file, apparmor, apparmor-easyprof-ubuntu or click-apparmor are still under development and getting updates - Systems with apt updates (eg, current Ubuntu Desktop and Server): - First boot will compile cache files - Reboots will use the cache files on the machine and be fast - First boots after upgrades will use the cache files on the machine if the above conditions are not met and be fast - Stable releases of Ubuntu will not meet any of those conditions except under exceptional and rare circumstances (eg, major OS upgrades like 14.10 to 15.04) and be fast - First boots after upgrades that meet one of the above conditions will need to regenerate the cache. This can happen on development releases where the kernel features file, apparmor, apparmor-easyprof-ubuntu or click-apparmor are still under development and getting updates In addition to the above, updates to only apparmor-easyprof-ubuntu will regenerate the cache files for only the policy that is affected (eg, if there is a change to the location policy group in policy version 1.2, only apps using this policy version and this policy group will need to be recompiled). Planned improvements (in order of most likely to be done first): 1. Finetuning the checks to invalidate the cache (eg, .md5sums could only be for /etc/apparmor.d/abstractions, ...): WONTFIX (will want an md5sum on apparmor_parser since it could change the cache and the md5sum will always change. Furthermore, apparmor-easyprof-ubuntu is all policy so there is no gain there. click-apparmor could possibly benefit, but it doesn't change often and when it does, it is typically for policy) 2. Investigate ways to utilize the custom tarball and rootfs precompiled cache files on upgrades when apparmor, apparmor-easyprof-ubuntu and click-apparmor are updated: DONE 3. Improve cache handling for app store apps (eg, having the app store server precompile them so that the device can download them when it needs to rather than having to regenerate them itself): WONTFIX (doesn't scale) 4. For systems with apt upgrades, compile the policy either during install or on kernel upgrade rather than on boot. For systems with read-only fs-style upgrades, compile the policy prior to reboot rather than on boot. 5. Support cache files per kernel .features file (or kernel version). This will allow people to boot into a previous kernel without having to recompile policy 6. Improve parser compile time 7. Investigate how to utilize profile composition and profile stacking to decrease compile and load times (eg, one idea is that the policy template is compiled once and each policy group once such that the parser need only stitch the already compiled bits together) 8. For Ubuntu Touch/Personal system-image based systems, investigate ways to utilize the update tarball and compile policy before rebooting to improve the user experience Work is planned for the medium term for '1-3' with
[Touch-packages] [Bug 1531925] Re: Can't connect Logitech Living Room Keyboard [LE]
Ok, there seems to be another problem I didn't respected yet. Powering a controller with hciconfig will bring it into a state where not all subsystems are initialized required for LE support. We still have a udev rule in our bluez package included which will try to power a bluetooth controller via hciconfig which is really not what we should do as described before. Starting with bluez 5.35/.36 there is a new option bluez itself provides for this which defines a config element in /etc/bluetooth/main.conf to do the same but the right way. I am not sure if this udev rule comes into our way here but it feels a bit like it does. @Pat/Tony: Would be good if you can try the following: sudo mount -o remount,rw / sudo rm /lib/udev/rules.d/50-bluetooth-hci-auto-poweron.rules echo "[Policy]" >> sudo tee -a /etc/bluetooth/main.conf echo "AutoEnable=true" >> sudo tee -a /etc/bluetooth/main.conf I've also pushed this change up at https://code.launchpad.net/~bluetooth/bluez/fix-ctrl-enablement-on- detection as that is something we need to fix anyway. If that doesn't help also try removing all bluetooth state information by sudo rm -rf /var/lib/bluetooth/* and then reboot the device. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1531925 Title: Can't connect Logitech Living Room Keyboard [LE] Status in Canonical System Image: New Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: New Bug description: Cannot connect a Logitech Illuminated Living Room keyboard to a device running bluez5. There are two versions of the keyboard, a unifying receiver version, and a Bluetooth version. The latter has a BT symbol on the 'del' key. To put the BT version in pairing mode, power on the keyboard, then briefly hold the FN and 'del' key together and release. A green LED at the top right of the keyboard should start flashing quickly. Once in pairing mode, the device will become visible on desktop using the BT settings UI, however it's *never* shown in the UI on a device running the latest Touch ( OTA9.1+ ). Note, this includes devices running a silo version of bluez 5.37, including both arale and krillin. On both devices, the keyboard *is* viewable using bluetoothctl. It should be noted that LE keyboard support on touch should be a considered a missing feature. Here's the reported attributes of the device from my macair running 15.10 + bluez 5.37: Device DF:08:A9:A0:13:93 Name: K830 Alias: K830 Appearance: 0x03c1 Icon: input-keyboard Paired: yes Trusted: no Blocked: no Connected: yes LegacyPairing: no UUID: Generic Access Profile (1800--1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) UUID: Device Information (180a--1000-8000-00805f9b34fb) UUID: Battery Service (180f--1000-8000-00805f9b34fb) UUID: Human Interface Device (1812--1000-8000-00805f9b34fb) UUID: Vendor specific (0001--1000-8000-011f246d) Modalias: usb:v046DpB335d0010 From bluetoothctl on both my laptop and my desktop, I'm able to pair, trust and connect the device, and info reflects these changes, however the device never actually connects, it's LED remains blinking fast, and the keyboard cannot be used. Note, before pairing, I issued the command 'agent KeyboardOnly' and 'default-agent'. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1531925/+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 1186662] Re: isc-dhcp-server fails to renew lease file
No, I just tested a proposed update from Jamie Strandboge's PPA. See comment #37 and #41. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1186662 Title: isc-dhcp-server fails to renew lease file Status in isc-dhcp package in Ubuntu: Fix Released Status in isc-dhcp source package in Trusty: Triaged Bug description: After raring upgrade, the dhcp server fails to renew lease file when it tries to (about every hour). The syslog says: dhcpd: Can't create new lease file: Permission denied It looks like a permission problem, because # chown -R dhcpd:dhcpd /var/lib/dhcp the above command temporarily solves the issue, until dhcpd is restarted: at that time, the ownership of the directory and the lease file is set back to root:root. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1186662/+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 1528058] Re: settings not readable from confined app/scope
Setting to triaged for thumbnailer because it's fixed there. For the change to take effect, we also need this to land, which may take quite a while yet: https://code.launchpad.net/~michihenning/apparmor-easyprof-ubuntu/new- thumbnailer-methods/+merge/281712 ** Changed in: thumbnailer (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to thumbnailer in Ubuntu. https://bugs.launchpad.net/bugs/1528058 Title: settings not readable from confined app/scope Status in thumbnailer package in Ubuntu: Triaged Bug description: The trace-client gsetting does not work and always returns false when running under confinement. We need a different way to enable this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thumbnailer/+bug/1528058/+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 1173123] Re: [r300g] Graphical error when pressing the "start" button
panreyes, thank you for reporting this and helping make Ubuntu better. As per https://wiki.ubuntu.com/Releases, Ubuntu 13.04 reached EOL on January 27, 2014. Is this reproducible on a supported release? ** Tags added: bios-outdated-2302 ** Changed in: mesa (Ubuntu) Importance: Undecided => Low ** Changed in: mesa (Ubuntu) Status: Confirmed => Incomplete -- 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/1173123 Title: [r300g] Graphical error when pressing the "start" button Status in mesa package in Ubuntu: Incomplete Bug description: When pressing the start button on this new ubuntu release (13.04), a graphical error happens in my PC. Here is a screenshot: http://www.panreyes.com/ubuntu-error.png And this is the Xorg log: http://www.panreyes.com/ubuntu-error.log The graphic card is an integrated ATI Radeon X1200 (RS690) --- .tmp.unity.support.test.0: ApportVersion: 2.9.2-0ubuntu8 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 CurrentDmesg: DistUpgraded: Fresh install DistroCodename: raring DistroRelease: Ubuntu 13.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices [AMD] nee ATI RS690 [Radeon X1200] [1002:791e] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:826d] MachineType: System manufacturer System Product Name MarkForUpload: True Package: xorg 1:7.7+1ubuntu4 PackageArchitecture: i386 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: root=/dev/nfs boot=casper netboot=nfs nfsroot=192.168.0.148:/home/pixe/tftp initrd=casper/initrd.lz locale=es_ES -- BOOT_IMAGE=casper/vmlinuz ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Tags: raring ubuntu compiz-0.9 Uname: Linux 3.8.0-19-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 10/22/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS M2A-VM ACPI BIOS Revision 2201 dmi.board.name: M2A-VM 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:bvrASUSM2A-VMACPIBIOSRevision2201:bd10/22/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2A-VM: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.9~daily13.04.18.1~13.04-0ubuntu1 version.libdrm2: libdrm2 2.4.43-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.1-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.1-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1 xserver.bootTime: Tue Apr 30 10:30:32 2013 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputAT Translated Set 2 keyboard KEYBOARD, id 8 inputImPS/2 Generic Wheel Mouse MOUSE, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.3-0ubuntu6 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1173123/+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 1171702] Re: Screen freezes when trying to move icons in Unity's launcher
monostel, thank you for reporting this and helping make Ubuntu better. As per https://wiki.ubuntu.com/Releases, Ubuntu 13.04 reached EOL on January 27, 2014. Is this reproducible in a supported release? ** Changed in: mesa (Ubuntu) Importance: Undecided => Medium ** Changed in: mesa (Ubuntu) Status: Confirmed => Incomplete -- 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/1171702 Title: Screen freezes when trying to move icons in Unity's launcher Status in mesa package in Ubuntu: Incomplete Bug description: A recent upgrade of Unity seems to have introduced a crippling bug whereby the screen locks up whenever left-click is held down on an icon in the launcher so that icons can be moved around. The cursor can still move but the rest of the desktop doesn't update, with flickering happening on occasion. Nothing short of forcing a reboot has been able to get around this. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Apr 23 00:41:19 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu ExtraDebuggingInterest: No GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last few days GraphicsCard: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a011] (prog-if 00 [VGA controller]) Subsystem: Device [0537:2852] Subsystem: Device [0537:2852] InstallationDate: Installed on 2013-04-03 (20 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1) MachineType: IEC PineTrail MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=c23d93a2-0f6e-4044-bbfa-7a80b75097eb ro quiet splash SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) XorgLogOld: dmi.bios.date: 10/27/2010 dmi.bios.vendor: IEC dmi.bios.version: 0.08 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Base Board Product Name dmi.board.vendor: IEC dmi.board.version: Base Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnIEC:bvr0.08:bd10/27/2010:svnIEC:pnPineTrail:pvr0.08:rvnIEC:rnBaseBoardProductName:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion: dmi.product.name: PineTrail dmi.product.version: 0.08 dmi.sys.vendor: IEC version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.43-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.1-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.1-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1 xserver.bootTime: Tue Apr 23 00:38:15 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.3-0ubuntu6 xserver.video_driver: intel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1171702/+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 1464917] Re: reboot hangs at 'Reached target Shutdown'
Tried Adam's workaround: if I do swapoff and then shutdown, the system poweroff complete successfully. -- 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/1464917 Title: reboot hangs at 'Reached target Shutdown' Status in systemd: New Status in systemd package in Ubuntu: Confirmed Bug description: I rebooted my 15.04 system, and found it hanging indefinitely at the plymouth shutdown screen. Hitting esc to reveal the console showed a normal set of shutdown messages, ending with 'Reached target Shutdown' (paraphrased from memory). The system never rebooted on its own. I had to use SysRq to finish the shutdown. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu6 ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8 Uname: Linux 3.19.0-20-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Jun 13 11:53:10 2015 InstallationDate: Installed on 2010-09-24 (1723 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) MachineType: LENOVO 2306CTO ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-20-generic root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to vivid on 2014-12-06 (189 days ago) dmi.bios.date: 10/25/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET97WW (2.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2306CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1464917/+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 1551960] Re: lxc-attach does not work any more with input redirection
With that fix applied the adt-virt-lxc tests work fine again, so
removing the autopkgtest task again (I added it in case I need to adjust
something to the new LXC in that regard).
** No longer affects: autopkgtest (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1551960
Title:
lxc-attach does not work any more with input redirection
Status in lxc package in Ubuntu:
Fix Committed
Bug description:
LXC 2.0.0~rc{2,3,4} break autopkgtest's LXC runner. Downgrading to
2.0.0~rc1 works again. The issue is that lxc-attach stops working
properly with input redirection.
# lxc-start -n a
Until 2.0.0~rc1 I could redirect lxc-attach's stdout:
# lxc-attach -n a runlevel /dev/null |cat
N 5
But now this does not work any more:
# lxc-attach -n a runlevel
N 5
# lxc-attach -n a runlevel /dev/null
# lxc-attach -n a runlevel /dev/null | cat
#
I. e. the last two commands don't have any output at all any more.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1551960/+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 1547077] Re: Some glyphs drawn consistently wrong, bug comes and go
I'll try that BIOS test. In the meantime I thought I'd try again nVidia proprietary driver. Installation of package was requested through Ubuntu driver selection GUI. Resulted in 2 new bugs automatically notified and reported: https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1552108 https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-352/+bug/1552109 Have not rebooted yet. Thank you for your attention. -- 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/1547077 Title: Some glyphs drawn consistently wrong, bug comes and go Status in xorg package in Ubuntu: Incomplete Bug description: # Summary * Some glyphs badly drawn at some moments. * When happens, same glyph drawn on various windows shows same corruption. * Problem comes and go. WORKAROUND: Use nvidia drivers. # Context Laptop, using Intel driver. Expected: all glyphs rendered correctly. Observed: some glyphs not rendered correctly * reproducible: sometimes, eventually. Problem comes and go, severity varies from one glyph (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png ) to all text on screen fully unreadable (see 2016y02m10d_18h42m18s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_01.png ) * *some* glyphs are affected. For example, letter 'a' of a certain size will be replaced by colored garbage at many places where it appears (see 2016y02m18d_16h05m35s_0100Z_same_corruption_on_different_windows.png ), but other 'a' with different size, italic, bold, etc will be unaffected. * in some applications (e.g. xfce whisker menu), some glyphs are rendered correctly or not depending on the direction of mouse hovering. See video 2016y02m16d_21h41m14s_0100Z_whisker_menu_missing_glyphs.mp4 . * in menu of gtk application, some glyphs are "fixed" by opening the menu, but not all. For example, in xfce4-terminal, letter A of "Affichage" and its menu content as well as "Aide" is affected. Opening "Affichage" menu does not fix anything. Opening "Aide" menu fixes the "A" of "Aide". Changing window size reactivates the bug on "A" or "Aide". See video 2016y02m18d_16h14m25s_0100Z_glyph-redrawn- bug.mp4 . * text under icons on desktop is affected, but shadows are not. See 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png # Affected applications * xfce whisker menu, * xfce4-terminal (nealy all screenshots) * firefox (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png ), * thunderbird (see 2016y02m16d_21h28m35s_0100Z_x_bug_affects_thunderbird_terminal.png ), * emacs (see 2016y02m10d_18h41m49s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_00.png and subsequent ), * superswitcher ( a gtk/gdk app) * *NOT* affected: xterm, xmessage. Perhaps only gtk/gdk/pango/cairo apps are affected. # Additional information This looks like a cache corruption somewhere. On IRC #pango, someone suggested a bug in Intel driver. Running `xfce4-appearance-settings` and there changing any of: * antialiasing enable/disable, * hinting strength, * subpixel alignment * or dpi immediately cures the bug (see 2016y02m16d_21h31m52s_0100Z_x_bug_disabling_antialias_immediately_cures_problem.png ) Setting back the exact same parameters immediately reactivates the bug (see 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png). It is believed that keeping any new settings for a while will have the bug reoccur. It is not like bug 1536751. That one affects rendering quality of *all* glyphs, at all times, depending on dpi. This is not the case here: *some* glyphs (randomly chosen) are drawn corrupted (replaced by garbage or absent), not always. --- ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.14, 4.4.0-8-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated Graphics Controller [1043:177d] Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:177d] InstallationDate: Installed on 2016-02-03 (26 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160203) MachineType: ASUSTeK COMPUTER INC. N551JK Package: xorg
[Touch-packages] [Bug 1163264] Re: Compiz is using 50-100 % CPU time with Unity
Audrius Meskauskas, thank you for reporting this and helping make Ubuntu better. As per https://wiki.ubuntu.com/Releases, Ubuntu 12.10 reached EOL on May 16, 2014. Is this reproducible in a supported release? ** Tags added: bios-outdated-1302 ** Changed in: mesa (Ubuntu) Importance: Undecided => Low ** Changed in: mesa (Ubuntu) Status: New => Incomplete -- 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/1163264 Title: Compiz is using 50-100 % CPU time with Unity Status in mesa package in Ubuntu: Incomplete Bug description: When in Unity mode, Compiz is usage never drops below 20 % and quite often around 50 %. This disappears when I switch into Gnome Classic no effects mode. This machine is using two monitor dual head with NVidia. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-26.42-generic 3.5.7.6 Uname: Linux 3.5.0-26-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue Apr 2 13:54:33 2013 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: No GraphicsCard: NVIDIA Corporation GK107 [GeForce GT 640] [10de:0fc1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:83f9] InstallationDate: Installed on 2013-02-25 (35 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: System manufacturer System Product Name MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-26-generic root=UUID=51199ff3-65ba-42c8-8be5-cfcfa2aecb52 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0702 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Q77-M dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0702:bd11/08/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Q77-M:rvrRevX.0x: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.8.6-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1163264/+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 1551960] Re: lxc-attach does not work any more with input redirection
I locally applied https://github.com/lxc/lxc/commit/12752e2 to our
current package and built it. Now it looks better:
# lxc-attach -n a runlevel
N 5
# lxc-attach -n a runlevel /dev/null
N 5
# lxc-attach -n a runlevel /dev/null | cat
So redirecting stdin only now does not show this
"lxc_console_cb_tty_master: 683 Bad file" error any more, and
redirecting stderr now works too. But redirecting stdout in addition
still doesn't?
Maybe I'm missing another fix from trunk, though.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1551960
Title:
lxc-attach does not work any more with input redirection
Status in lxc package in Ubuntu:
Fix Committed
Bug description:
LXC 2.0.0~rc{2,3,4} break autopkgtest's LXC runner. Downgrading to
2.0.0~rc1 works again. The issue is that lxc-attach stops working
properly with input redirection.
# lxc-start -n a
Until 2.0.0~rc1 I could redirect lxc-attach's stdout:
# lxc-attach -n a runlevel /dev/null |cat
N 5
But now this does not work any more:
# lxc-attach -n a runlevel
N 5
# lxc-attach -n a runlevel /dev/null
# lxc-attach -n a runlevel /dev/null | cat
#
I. e. the last two commands don't have any output at all any more.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1551960/+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 1551960] Re: lxc-attach does not work any more with input redirection
Nevermind, I built upstream git master, and that lxc-attach works fine.
Thanks Christian!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1551960
Title:
lxc-attach does not work any more with input redirection
Status in lxc package in Ubuntu:
Fix Committed
Bug description:
LXC 2.0.0~rc{2,3,4} break autopkgtest's LXC runner. Downgrading to
2.0.0~rc1 works again. The issue is that lxc-attach stops working
properly with input redirection.
# lxc-start -n a
Until 2.0.0~rc1 I could redirect lxc-attach's stdout:
# lxc-attach -n a runlevel /dev/null |cat
N 5
But now this does not work any more:
# lxc-attach -n a runlevel
N 5
# lxc-attach -n a runlevel /dev/null
# lxc-attach -n a runlevel /dev/null | cat
#
I. e. the last two commands don't have any output at all any more.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1551960/+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 1159947] Re: Using kwin_gles instead of kwin causes freeze after entering KDE
Gannet, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1159947/comments/1 regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find. ** Changed in: mesa (Ubuntu) Status: Confirmed => Invalid -- 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/1159947 Title: Using kwin_gles instead of kwin causes freeze after entering KDE Status in mesa package in Ubuntu: Invalid Bug description: According to KWin developers [https://bugs.kde.org/show_bug.cgi?id=313599] that happen because of configuration issues in video driver. Please look into KWin developers answer here [https://bugs.kde.org/show_bug.cgi?id=313599#c29] to read their opinion about this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1159947/+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 1549894] Re: No audio while recording video
Stefan reported: "You are so right with your advice of the microphone access. On my E5, I had deactivated the option of giving the microphone the permission to work with the camera. Wow, now the audio works fine with recording video." Closing for now. ** Changed in: camera-app (Ubuntu) Status: Incomplete => Invalid ** Changed in: canonical-devices-system-image Status: Confirmed => Invalid -- 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/1549894 Title: No audio while recording video Status in Canonical System Image: Invalid Status in camera-app package in Ubuntu: Invalid Bug description: Using the camera app and recording video, no audio is recorded in the video. I tested on 1080p, 720p and 480p resolution. Ubuntu Phone version: OTA 9.1 Hardware: Aquaris E5 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1549894/+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 1088137] Re: colored snow all over, hangs under compiz
drewp, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1088137/comments/5 regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find. ** Changed in: mesa (Ubuntu) Status: Incomplete => Invalid -- 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/1088137 Title: colored snow all over, hangs under compiz Status in mesa package in Ubuntu: Invalid Bug description: I upgraded to 12.10 successfully and didn't see any graphics problems. Today, after my laptop was on for a while but not in a position where it would overheat, I had random colored pixels on the screen and the mouse position only refreshed a few times. dmesg contains "NVRM: Xid (:01:00): 31, Ch 0001, engmask 0101, intr 1000" but that's all I found. Rebooting didn't fix it; I got a crash soon after login. I went to xorg-edgers and non-compiz desktop, and now I can work but there is still colored snow accumulating all over. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.7.0-4.12-generic 3.7.0-rc7 Uname: Linux 3.7.0-4-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 310.19 Thu Nov 8 00:52:03 PST 2012 GCC version: gcc version 4.7.2 (Ubuntu/Linaro 4.7.2-2ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun Dec 9 00:23:55 2012 DistUpgraded: 2012-11-24 01:14:04,814 DEBUG enabling apt cron job DistroCodename: quantal DistroVariant: ubuntu DkmsStatus: nvidia-current, 310.19, 3.5.0-19-generic, x86_64: installed nvidia-current, 310.19, 3.7.0-4-generic, x86_64: installed virtualbox, 4.1.18, 3.2.0-32-generic, x86_64: installed virtualbox, 4.1.18, 3.5.0-18-generic, x86_64: installed virtualbox, 4.1.18, 3.5.0-19-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation Device [10de:1251] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. Device [1462:10a9] InstallationDate: Installed on 2011-09-08 (457 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) JockeyStatus: kmod:nvidia_experimental_304 - Experimental NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) kmod:nvidia_experimental_310 - Experimental NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) kmod:nvidia_current - nvidia_current (Proprietary, Enabled, Not in use) kmod:nvidia_current_updates - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.7.0-4-generic root=UUID=3efdfb1e-397e-4c2a-ab46-8ec5a1a382d9 ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to quantal on 2012-11-24 (14 days ago) dmi.bios.date: 05/20/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16F2IG6 V3.05 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-16F2 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16F2IG6V3.05:bd05/20/2011:svn:pn:pvrTobefilledbyO.E.M.:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16F2:rvrTobefilledbyO.E.M.:cvnMicro-StarInternational:ct10:cvrTobefilledbyO.E.M.: dmi.product.version: To be filled by O.E.M. version.compiz: compiz 1:0.9.8.4+bzr3412-0ubuntu0.1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.40+git20121123.171666e4-0ubuntu0ricotz2~quantal version.libgl1-mesa-dri: libgl1-mesa-dri 9.1~git20121204.ec83535c-0ubuntu0ricotz~quantal version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx
[Touch-packages] [Bug 1155829] Re: gdm interface doesn't show up
Original reporter -> https://launchpad.net/~gexi-deactivatedaccount ** Changed in: mesa (Ubuntu) Status: Confirmed => Invalid -- 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/1155829 Title: gdm interface doesn't show up Status in mesa package in Ubuntu: Invalid Bug description: just did a fresh install of ubuntu-gnome-daily 13.04 on a thinkpad sl510. though the live-system worked just fine, gdm would show no interface after the installation process (). just the blue-stripes- background. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1155829/+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 1531925] Re: Can't connect Logitech Living Room Keyboard [LE]
I went again through the logs and came across the following: [ 1044.196326] Bluetooth: SMP security requested but not available which is then followed by a lot messages like: Jan 20 08:53:28 samsung930X3G bluetoothd[3988]: Report Map read failed: Attribute requires authentication before read/write Jan 20 08:53:28 samsung930X3G bluetoothd[3988]: Error reading Report value: Attribute requires authentication before read/write What this basically means is that the security checks inside the kernel stack failed and we couldn't build a secured and trusted connection which then in the end means the mouse wont connect properly and fails to work. There is already an upstream bug about this problem at https://bugzilla.kernel.org/show_bug.cgi?id=104011 sadly without an solution other than reverting the change on the kernel side introduced this problem. @Pat: You're seeing this with your MX4 right? I will build a kernel then for it which has the suggested kernel side change reverted just to see if that helps us in this particular situation. ** Bug watch added: Linux Kernel Bug Tracker #104011 http://bugzilla.kernel.org/show_bug.cgi?id=104011 ** Tags added: bluez-touch ** Tags added: bluez-classic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1531925 Title: Can't connect Logitech Living Room Keyboard [LE] Status in Canonical System Image: New Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: New Bug description: Cannot connect a Logitech Illuminated Living Room keyboard to a device running bluez5. There are two versions of the keyboard, a unifying receiver version, and a Bluetooth version. The latter has a BT symbol on the 'del' key. To put the BT version in pairing mode, power on the keyboard, then briefly hold the FN and 'del' key together and release. A green LED at the top right of the keyboard should start flashing quickly. Once in pairing mode, the device will become visible on desktop using the BT settings UI, however it's *never* shown in the UI on a device running the latest Touch ( OTA9.1+ ). Note, this includes devices running a silo version of bluez 5.37, including both arale and krillin. On both devices, the keyboard *is* viewable using bluetoothctl. It should be noted that LE keyboard support on touch should be a considered a missing feature. Here's the reported attributes of the device from my macair running 15.10 + bluez 5.37: Device DF:08:A9:A0:13:93 Name: K830 Alias: K830 Appearance: 0x03c1 Icon: input-keyboard Paired: yes Trusted: no Blocked: no Connected: yes LegacyPairing: no UUID: Generic Access Profile (1800--1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) UUID: Device Information (180a--1000-8000-00805f9b34fb) UUID: Battery Service (180f--1000-8000-00805f9b34fb) UUID: Human Interface Device (1812--1000-8000-00805f9b34fb) UUID: Vendor specific (0001--1000-8000-011f246d) Modalias: usb:v046DpB335d0010 From bluetoothctl on both my laptop and my desktop, I'm able to pair, trust and connect the device, and info reflects these changes, however the device never actually connects, it's LED remains blinking fast, and the keyboard cannot be used. Note, before pairing, I issued the command 'agent KeyboardOnly' and 'default-agent'. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1531925/+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 1125726] Re: boot-time race between /etc/network/if-up.d/ntpdate and "/etc/init.d/ntp start"
This fix is causing problems on Ubuntu 12.04 for me; for both KVM hosts and KVM guests. I see a message like lockfile creation failed: exceeded maximum number of lock attempts On my hosts, it delays boot finishing for several minutes; while some of my guests just never become network accessible. For anyone else bitten by same issue, I am currently using this workaround: chmod -x /usr/sbin/ntpdate-debian -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1125726 Title: boot-time race between /etc/network/if-up.d/ntpdate and "/etc/init.d/ntp start" Status in ntp package in Ubuntu: Fix Released Status in ntp source package in Precise: Fix Released Status in ntp source package in Trusty: Fix Released Bug description: [Impact] * Hardware clocks are not stepped at boot, which can prevent NTP from ever syncing the clock. Incorrect clocks can cause serious issues in distributed systems. * Upstream originally added a lock file to eliminate a race between the ntp service (which keeps the clock synchronized during normal operation) and ntpdate (which is used to step the clock by large intervals at boot time). That change had a flaw which introduced a deadlock. An Ubuntu patch was applied which broke the locking mechanism entirely, reintroducing the race condition. * This change undoes the Ubuntu patch and fixes the deadlock by unlocking before attempting to start the ntp service. [Test Case] * There are two bugs: The race, and the deadlock. To reproduce the race more consistently: - add 'sleep 30' to '/etc/network/if-up.d/ntpdate' on the line preceding '/usr/sbin/ntpdate-debian -s $OPTS 2>/dev/null || :', and comment out 'invoke-rc.d --quiet $service stop >/dev/null 2>&1 || true'. This will reproduce the case where the ntp service starts between the stop command and the ntpdate command. The result will be that the ntpdate command fails. There will be a message in syslog like: 'ntpdate[17660]: the NTP socket is in use, exiting' - Reintroducing the lock brings back the deadlock issue. Both the ntpdate if-up.d script and the ntp init script check the lock file, but the ntpdate script attempted to start the ntp init script before unlocking the lock. Moving the unlock before the init script invocation fixes the deadlock. The original deadlock behavior is described here: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/246203 [Regression Potential] * Low. Out-of-sync clocks could be changed a large amount at boot time, but only for machines with static IP's. The clock is only likely to be in this state if the clock was very skewed at boot time, which is also unlikely since NTP usually keeps the software clock in sync during operation and the hardware clock is updated at shutdown. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1125726/+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 1134974] Re: compiz and other display misbehavior on HD4000 after xatracker/mesa components upgraded to 9.0.2-0ubuntu0.1
Jim Hill, thank you for reporting this and helping make Ubuntu better. As per https://wiki.ubuntu.com/Releases, Ubuntu 12.10 reached EOL on May 16, 2014. Is this reproducible in a supported release? ** Changed in: mesa (Ubuntu) Importance: Undecided => Medium ** Changed in: mesa (Ubuntu) Status: New => Incomplete -- 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/1134974 Title: compiz and other display misbehavior on HD4000 after xatracker/mesa components upgraded to 9.0.2-0ubuntu0.1 Status in mesa package in Ubuntu: Incomplete Bug description: After a recent upgrade the unity launcher autohide lost transparency and other programs began apparently hanging. I saw these upgrade lines in dpkg.log: 2013-02-27 15:14:16 upgrade libgl1-mesa-dri:i386 9.0.2-0ubuntu0.1 9.0-0ubuntu1 2013-02-27 15:14:18 upgrade libgl1-mesa-dri:amd64 9.0.2-0ubuntu0.1 9.0-0ubuntu1 2013-02-27 15:14:22 upgrade libgl1-mesa-dev:amd64 9.0.2-0ubuntu0.1 9.0-0ubuntu1 2013-02-27 15:14:23 upgrade mesa-common-dev:amd64 9.0.2-0ubuntu0.1 9.0-0ubuntu1 2013-02-27 15:14:24 upgrade libgl1-mesa-glx:i386 9.0.2-0ubuntu0.1 9.0-0ubuntu1 2013-02-27 15:14:25 upgrade libgl1-mesa-glx:amd64 9.0.2-0ubuntu0.1 9.0-0ubuntu1 2013-02-27 15:14:26 upgrade libglapi-mesa:amd64 9.0.2-0ubuntu0.1 9.0-0ubuntu1 2013-02-27 15:14:26 upgrade libglapi-mesa:i386 9.0.2-0ubuntu0.1 9.0-0ubuntu1 2013-02-27 15:14:31 upgrade libxatracker1:amd64 9.0.2-0ubuntu0.1 9.0-0ubuntu1 2013-02-27 15:14:32 upgrade libosmesa6:i386 9.0.2-0ubuntu0.1 9.0-0ubuntu1 and backed those out with sudo apt-get install libgl1-mesa-dev:amd64=9.0-0ubuntu1 mesa-common- dev:amd64=9.0-0ubuntu1 libgl1-mesa-dri:amd64=9.0-0ubuntu1 libgl1-mesa- dri:i386=9.0-0ubuntu1 libgl1-mesa-glx:i386=9.0-0ubuntu1 libgl1-mesa- glx:amd64=9.0-0ubuntu1 libglapi-mesa:amd64=9.0-0ubuntu1 libglapi- mesa:i386=9.0-0ubuntu1 libxatracker1:amd64=9.0-0ubuntu1 libosmesa6:i386=9.0-0ubuntu1 now everything works again. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-25.39-generic 3.5.7.4 Uname: Linux 3.5.0-25-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CurrentDmesg: [ 24.724057] init: Failed to spawn setvtrgb main process: unable to execute: No such file or directory Date: Wed Feb 27 16:09:51 2013 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0162] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Biostar Microtech Int'l Corp Device [1565:110d] Advanced Micro Devices [AMD] nee ATI Turks [Radeon HD 6670] [1002:6758] (prog-if 00 [VGA controller]) Subsystem: Hightech Information System Ltd. Device [1787:2012] InstallationDate: Installed on 2013-02-16 (11 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: BIOSTAR Group H61MHB MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-25-generic root=UUID=790b115f-b569-4b96-97d1-0d5aab9f12fc ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/20/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.4 dmi.board.asset.tag: None dmi.board.name: H61MHB dmi.board.vendor: BIOSTAR Group dmi.board.version: 6.0 dmi.chassis.asset.tag: None dmi.chassis.type: 3 dmi.chassis.vendor: BIOSTAR Group dmi.chassis.version: 6.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd12/20/2011:svnBIOSTARGroup:pnH61MHB:pvr6.0:rvnBIOSTARGroup:rnH61MHB:rvr6.0:cvnBIOSTARGroup:ct3:cvr6.0: dmi.product.name: H61MHB dmi.product.version: 6.0 dmi.sys.vendor: BIOSTAR Group version.compiz: compiz 1:0.9.8.6-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 To manage notifications about this bug go to:
[Touch-packages] [Bug 1134557] Re: [xorg-edgers][Unity 7 series]GPU lockup/Screen corruption on drag and drop in launcher
Loris Zinsou, thank you for reporting this and helping make Ubuntu better. As per https://wiki.ubuntu.com/Releases, Ubuntu 12.10 reached EOL on May 16, 2014. Is this reproducible in a supported release? ** Changed in: mesa (Ubuntu) Importance: Undecided => Low ** Changed in: mesa (Ubuntu) Status: New => Incomplete -- 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/1134557 Title: [xorg-edgers][Unity 7 series]GPU lockup/Screen corruption on drag and drop in launcher Status in mesa package in Ubuntu: Incomplete Bug description: My hardware is an Intel HD 3000/i7 GPU. To reproduce this bug : - you have to install the xorg edgers packages (mesa) - you have to run Unity 7 series, either from staging PPA or Raring - try repositioning an icon in Unity launcher by draging and dropping Expected result : - icon repositioning Actual result : - GPU lockup, screen corruption, display flickering - killing Unity process doesn't work (corruption is persisting), you have to restart X. --- ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 DistroCodename: quantal DistroRelease: Ubuntu 12.10 DistroVariant: ubuntu InstallationDate: Installed on 2012-05-05 (298 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20120425-15:28 MarkForUpload: True Package: mesa (not installed) Tags: quantal ubuntu Uname: Linux 3.8.0-030800-generic x86_64 UnreportableReason: Please work this issue through technical support channels first. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1134557/+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 1132418] Re: compiz crashes
Not reproducible in Xenial. ** Changed in: mesa (Ubuntu) Status: New => Invalid -- 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/1132418 Title: compiz crashes Status in mesa package in Ubuntu: Invalid Bug description: compwiz crashes ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-23.35-generic 3.5.7.2 Uname: Linux 3.5.0-23-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz Date: Sun Feb 24 17:57:16 2013 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller]) InstallationDate: Installed on 2013-02-08 (15 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) Lsusb: Bus 002 Device 004: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-23-generic root=UUID=7b787ba5-fa41-442d-a58a-9895e300763b ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz 1:0.9.8.6-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1132418/+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 1142305] Re: Running 32 bit software in 64 bit 12.04.2 with quantal xorg+kernel doesn't work with i965
** No longer affects: xserver-xorg-video-intel-lts-backport-quantal (Ubuntu) -- 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/1142305 Title: Running 32 bit software in 64 bit 12.04.2 with quantal xorg+kernel doesn't work with i965 Status in mesa package in Ubuntu: New Bug description: Running 32 bit software which uses OpenGL doesn't work anymore after updating to quantal kernel+xorg in Ubuntu 12.04.2 64 bit. 64 Bit software work fine. Seems to be a problem with the i965 driver. LIBGL_DEBUG=verbose google-earth ERROR: ld.so: object '/opt/lib/libmediaclient.so' from /etc/ld.so.preload cannot be preloaded: ignored. libGL: OpenDriver: trying /usr/lib/i386-linux-gnu/dri/tls/i965_dri.so libGL: OpenDriver: trying /usr/lib/i386-linux-gnu/dri/i965_dri.so libGL error: dlopen /usr/lib/i386-linux-gnu/dri/i965_dri.so failed (/usr/lib/i386-linux-gnu/dri/i965_dri.so: undefined symbol: drm_intel_gem_bo_map_unsynchronized) libgl1-mesa-dri-lts-quantal:i386: 9.0.2-0ubuntu0.1~precise1 libgl1-mesa-glx-lts-quantal:i386: 9.0.2-0ubuntu0.1~precise1 xserver-xorg-video-intel-lts-quantal: 2:2.20.9-0ubuntu2~precise2 libdrm-intel1:i386: 2.4.39-0ubuntu0.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1142305/+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 1088137] Re: colored snow all over, hangs under compiz
Nope, I think we should close the ticket -- 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/1088137 Title: colored snow all over, hangs under compiz Status in mesa package in Ubuntu: Incomplete Bug description: I upgraded to 12.10 successfully and didn't see any graphics problems. Today, after my laptop was on for a while but not in a position where it would overheat, I had random colored pixels on the screen and the mouse position only refreshed a few times. dmesg contains "NVRM: Xid (:01:00): 31, Ch 0001, engmask 0101, intr 1000" but that's all I found. Rebooting didn't fix it; I got a crash soon after login. I went to xorg-edgers and non-compiz desktop, and now I can work but there is still colored snow accumulating all over. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.7.0-4.12-generic 3.7.0-rc7 Uname: Linux 3.7.0-4-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 310.19 Thu Nov 8 00:52:03 PST 2012 GCC version: gcc version 4.7.2 (Ubuntu/Linaro 4.7.2-2ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun Dec 9 00:23:55 2012 DistUpgraded: 2012-11-24 01:14:04,814 DEBUG enabling apt cron job DistroCodename: quantal DistroVariant: ubuntu DkmsStatus: nvidia-current, 310.19, 3.5.0-19-generic, x86_64: installed nvidia-current, 310.19, 3.7.0-4-generic, x86_64: installed virtualbox, 4.1.18, 3.2.0-32-generic, x86_64: installed virtualbox, 4.1.18, 3.5.0-18-generic, x86_64: installed virtualbox, 4.1.18, 3.5.0-19-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation Device [10de:1251] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. Device [1462:10a9] InstallationDate: Installed on 2011-09-08 (457 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) JockeyStatus: kmod:nvidia_experimental_304 - Experimental NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) kmod:nvidia_experimental_310 - Experimental NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) kmod:nvidia_current - nvidia_current (Proprietary, Enabled, Not in use) kmod:nvidia_current_updates - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.7.0-4-generic root=UUID=3efdfb1e-397e-4c2a-ab46-8ec5a1a382d9 ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to quantal on 2012-11-24 (14 days ago) dmi.bios.date: 05/20/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16F2IG6 V3.05 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-16F2 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16F2IG6V3.05:bd05/20/2011:svn:pn:pvrTobefilledbyO.E.M.:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16F2:rvrTobefilledbyO.E.M.:cvnMicro-StarInternational:ct10:cvrTobefilledbyO.E.M.: dmi.product.version: To be filled by O.E.M. version.compiz: compiz 1:0.9.8.4+bzr3412-0ubuntu0.1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.40+git20121123.171666e4-0ubuntu0ricotz2~quantal version.libgl1-mesa-dri: libgl1-mesa-dri 9.1~git20121204.ec83535c-0ubuntu0ricotz~quantal version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1~git20121204.ec83535c-0ubuntu0ricotz~quantal version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.13.0.902+git20121207+server-1.13-branch.ede07c1a-0ubuntu0ricotz~quantal version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.0.99+git20121207.793e1b0e-0ubuntu0sarvatt version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.15+git20121207.4bfc5e90-0ubuntu0sarvatt~quantal version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
[Touch-packages] [Bug 1102729] Re: compiz crashed with SIGILL
NT Man, thank you for reporting this and helping make Ubuntu better. As per https://wiki.ubuntu.com/Releases, Ubuntu 13.04 reached EOL on January 27, 2014. Is this reproducible on a supported release? ** Changed in: mesa (Ubuntu) Status: Confirmed => Incomplete -- 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/1102729 Title: compiz crashed with SIGILL Status in mesa package in Ubuntu: Incomplete Bug description: Run Unbuntu in Boxes under Fedora 18 ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: compiz-core 1:0.9.9~daily13.01.21-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4 Uname: Linux 3.8.0-1-generic i686 .tmp.unity.support.test.1: ApportVersion: 2.8-0ubuntu2 Architecture: i386 CasperVersion: 1.330 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz Date: Tue Jan 22 02:38:21 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu ExecutablePath: /usr/bin/compiz GraphicsCard: Red Hat, Inc. Device [1b36:0100] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc Device [1af4:1100] LiveMediaBuild: Ubuntu 13.04 "Raring Ringtail" - Alpha i386 (20130121) Lsusb: Bus 002 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Bochs Bochs MarkForUpload: True ProcCmdline: Compiz ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash -- Signal: 4 SourcePackage: compiz StacktraceTop: ?? () ?? () from /usr/lib/i386-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/i386-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/i386-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/i386-linux-gnu/dri/swrast_dri.so Title: compiz crashed with SIGILL UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 01/01/2011 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2011:svnBochs:pnBochs:pvr:cvnBochs:ct1:cvr: dmi.product.name: Bochs dmi.sys.vendor: Bochs version.compiz: compiz 1:0.9.9~daily13.01.21-0ubuntu1 version.libdrm2: libdrm2 2.4.41-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.1-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.1-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.1.901-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.0.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.18-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.6-0ubuntu1 xserver.bootTime: Tue Jan 22 02:38:09 2013 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputQEMU QEMU USB Tablet TOUCHSCREEN, id 7 inputAT Translated Set 2 keyboard KEYBOARD, id 8 inputImExPS/2 Generic Explorer Mouse MOUSE, id 9 xserver.errors: open /dev/dri/card0: No such file or directory open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.13.1.901-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1102729/+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 1103110] Re: supertuxkart crashes with SEGFAULT
** Package changed: mesa (Ubuntu) => supertuxkart (Ubuntu) -- 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/1103110 Title: supertuxkart crashes with SEGFAULT Status in supertuxkart package in Ubuntu: New Bug description: I tried to start supertuxkart and it failed with a sgementation fault. It seems to be different than the one mentioned in the other currently open bug, so I decided to report my own. haver@grobi:~$ supertuxkart Irrlicht Engine version 1.7.2 Linux 3.2.0-36-generic #57-Ubuntu SMP Tue Jan 8 21:44:52 UTC 2013 x86_64 [FileManager] Data files will be fetched from: '/usr/share/games/supertuxkart/' [IrrDriver] Creating NULL device Irrlicht Engine version 1.7.2 Linux 3.2.0-36-generic #57-Ubuntu SMP Tue Jan 8 21:44:52 UTC 2013 x86_64 [IrrDriver] Trying OpenGL rendering. [IrrDriver] Tring to create device with 32 bits [IrrDriver Temp Logger] Level 1: No doublebuffering available. [IrrDriver Temp Logger] Level 2: Fatal error, could not get visual. Speicherzugriffsfehler (Speicherabzug geschrieben) haver@grobi:~$ Installation is in German, that is why the error messages are localized. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/supertuxkart/+bug/1103110/+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 1090107] Re: Long compiz sessions eventually start showing new windows as empty
Ben Gamari, thank you for reporting this and helping make Ubuntu better. As per https://wiki.ubuntu.com/Releases, Ubuntu 12.10 reached EOL on May 16, 2014. Is this reproducible on a supported release? ** Tags added: bios-outdated-a17 ** Changed in: mesa (Ubuntu) Importance: Undecided => Low ** Changed in: mesa (Ubuntu) Status: Confirmed => Incomplete -- 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/1090107 Title: Long compiz sessions eventually start showing new windows as empty Status in mesa package in Ubuntu: Incomplete Bug description: After using a compiz session consistently for a week or so, opening a new window intermittently results in a window frame with no contents. This can be seen in the attached screenshot (the XSane window in the top left hand corner of the screen). While not all new windows will be shown as empty, the probability of this occurring certainly increases in time. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 Uname: Linux 3.7.0-rc6+ x86_64 .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu9 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,imgsvg,text,mousepoll,regex,obs,place,imgpng,animation,expo,neg,ezoom,grid,snap,resize,vpswitch,move,session,wall,unitymtgrabhandles,workarounds,fade,switcher,resizeinfo,scale,unityshell] CompositorRunning: compiz Date: Thu Dec 13 14:43:12 2012 DistUpgraded: 2012-10-09 01:03:44,450 DEBUG enabling apt cron job DistroCodename: quantal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:01fe] Subsystem: Dell Device [1028:01fe] InstallationDate: Installed on 2011-10-19 (421 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MachineType: Dell Inc. Latitude D830 MarkForUpload: True PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.7.0-rc6+ root=UUID=27880cc8-df42-4098-8e07-3c4fb9dba0a5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to quantal on 2012-10-09 (65 days ago) dmi.bios.date: 01/04/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd01/04/2010:svnDellInc.:pnLatitudeD830:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D830 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.8.4+bzr3412-0ubuntu0.1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1090107/+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 1088137] Re: colored snow all over, hangs under compiz
drewp, thank you for reporting this and helping make Ubuntu better. As per https://wiki.ubuntu.com/Releases, Ubuntu 12.10 reached EOL on May 16, 2014. Is this reproducible in a supported release? ** Changed in: mesa (Ubuntu) Importance: Undecided => Medium ** Changed in: mesa (Ubuntu) Status: New => Incomplete -- 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/1088137 Title: colored snow all over, hangs under compiz Status in mesa package in Ubuntu: Incomplete Bug description: I upgraded to 12.10 successfully and didn't see any graphics problems. Today, after my laptop was on for a while but not in a position where it would overheat, I had random colored pixels on the screen and the mouse position only refreshed a few times. dmesg contains "NVRM: Xid (:01:00): 31, Ch 0001, engmask 0101, intr 1000" but that's all I found. Rebooting didn't fix it; I got a crash soon after login. I went to xorg-edgers and non-compiz desktop, and now I can work but there is still colored snow accumulating all over. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.7.0-4.12-generic 3.7.0-rc7 Uname: Linux 3.7.0-4-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 310.19 Thu Nov 8 00:52:03 PST 2012 GCC version: gcc version 4.7.2 (Ubuntu/Linaro 4.7.2-2ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun Dec 9 00:23:55 2012 DistUpgraded: 2012-11-24 01:14:04,814 DEBUG enabling apt cron job DistroCodename: quantal DistroVariant: ubuntu DkmsStatus: nvidia-current, 310.19, 3.5.0-19-generic, x86_64: installed nvidia-current, 310.19, 3.7.0-4-generic, x86_64: installed virtualbox, 4.1.18, 3.2.0-32-generic, x86_64: installed virtualbox, 4.1.18, 3.5.0-18-generic, x86_64: installed virtualbox, 4.1.18, 3.5.0-19-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation Device [10de:1251] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. Device [1462:10a9] InstallationDate: Installed on 2011-09-08 (457 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) JockeyStatus: kmod:nvidia_experimental_304 - Experimental NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) kmod:nvidia_experimental_310 - Experimental NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) kmod:nvidia_current - nvidia_current (Proprietary, Enabled, Not in use) kmod:nvidia_current_updates - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.7.0-4-generic root=UUID=3efdfb1e-397e-4c2a-ab46-8ec5a1a382d9 ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to quantal on 2012-11-24 (14 days ago) dmi.bios.date: 05/20/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16F2IG6 V3.05 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-16F2 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16F2IG6V3.05:bd05/20/2011:svn:pn:pvrTobefilledbyO.E.M.:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16F2:rvrTobefilledbyO.E.M.:cvnMicro-StarInternational:ct10:cvrTobefilledbyO.E.M.: dmi.product.version: To be filled by O.E.M. version.compiz: compiz 1:0.9.8.4+bzr3412-0ubuntu0.1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.40+git20121123.171666e4-0ubuntu0ricotz2~quantal version.libgl1-mesa-dri: libgl1-mesa-dri 9.1~git20121204.ec83535c-0ubuntu0ricotz~quantal version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1~git20121204.ec83535c-0ubuntu0ricotz~quantal version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.13.0.902+git20121207+server-1.13-branch.ede07c1a-0ubuntu0ricotz~quantal version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
[Touch-packages] [Bug 1079801] Re: applications like Google Earth or Second Life do not work
As per https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1079801/comments/15 . ** Tags added: bios-outdated-28.3 ** Changed in: mesa (Ubuntu) Status: Confirmed => Invalid -- 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/1079801 Title: applications like Google Earth or Second Life do not work Status in mesa package in Ubuntu: Invalid Bug description: Neither one of the available 4 different viewers for Second Life nor Google Earth will load. They quit with the command that they fail to load i965. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu6 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz Date: Fri Nov 16 18:51:17 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu DkmsStatus: virtualbox, 4.1.18, 3.5.0-18-generic, i686: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. Device [1462:7680] InstallationDate: Installed on 2012-11-15 (1 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) Lsusb: Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 046d:c062 Logitech, Inc. LS1 Laser Mouse, corded MachineType: ARLT Computer Produkte GmbH Mr. Business PRO SNB MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-18-generic root=UUID=634d3a5a-ca0b-4b91-9821-095392b6ca71 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/14/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V25.4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61M-P25 (MS-7680) dmi.board.vendor: MSI dmi.board.version: 5.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 5.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV25.4:bd02/14/2012:svnARLTComputerProdukteGmbH:pnMr.BusinessPROSNB:pvr5.0:rvnMSI:rnH61M-P25(MS-7680):rvr5.0:cvnMSI:ct3:cvr5.0: dmi.product.name: Mr. Business PRO SNB dmi.product.version: 5.0 dmi.sys.vendor: ARLT Computer Produkte GmbH version.compiz: compiz 1:0.9.8.4+bzr3407-0ubuntu1 version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1079801/+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 1078983] Re: Sharing OpenGL contexts causes crash
Greg Couch, thank you for reporting this and helping make Ubuntu better. As per https://wiki.ubuntu.com/Releases, Ubuntu 12.10 reached EOL on May 16, 2014. Is this reproducible in a supported release? ** Tags added: bios-outdated-5.37 ** Changed in: mesa (Ubuntu) Importance: Undecided => Low ** Changed in: mesa (Ubuntu) Status: New => Incomplete -- 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/1078983 Title: Sharing OpenGL contexts causes crash Status in mesa package in Ubuntu: Incomplete Bug description: In Ubuntu 12.10, the UCSF Chimera molecular graphics program, http://www.cgl.ucsf.edu/chimera/, crashes when the SideView tool is brought up. This was not a problem with Ubuntu 12.04. I have reproduced the bug with Intel Integrated graphics, and have a bug report from a user that it happens with the AMD proprietary driver. So it is probably not the "new and improved" Intel driver (the usual suspect), but something more basic, like compiz/unity or whatever Ubuntu is using now. To reproduce the bug, download and install UCSF Chimera from http://www.cgl.ucsf.edu/chimera/. Then, using the menus, use File / Fetch by ID ... to get the 1yti data set from the PDB (Protein DataBank), and then bring the SideView with Favorites / SideView. On my "Intel Corporation 82G33/G31 Express Integrated Graphics Controller (rev 02)" system, if the SideView is displayed before fetching the data, then it works. That suggests that it is a bug with sharing OpenGL data with a context that already has data in it. Here is the backtrace from gdb: Program terminated with signal 6, Aborted. #0 0xb7732424 in __kernel_vsyscall () (gdb) where 20 #0 0xb7732424 in __kernel_vsyscall () #1 0xb74611df in ?? () #2 0xb75d9000 in ?? () Backtrace stopped: previous frame inner to this frame (corrupt stack?) ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu6 Architecture: i386 CompizPlugins: [core,bailer,detection,composite,opengl,decor,regex,resize,gnomecompat,compiztoolbox,move,grid,animation,mousepoll,workarounds,wall,place,fade,vpswitch,snap,imgpng,scale,session,expo,ezoom,unitymtgrabhandles,unityshell] CompositorRunning: compiz Date: Wed Nov 14 16:53:02 2012 DistUpgraded: 2012-11-14 15:16:36,826 DEBUG enabling apt cron job DistroCodename: quantal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c2] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:2a73] InstallationDate: Installed on 2010-10-18 (758 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) MachineType: Hewlett-Packard HP Compaq dx2400 Microtower MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-18-generic root=UUID=9823d8c7-5498-469e-8bf2-7b8340e9c590 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to quantal on 2012-11-14 (0 days ago) dmi.bios.date: 04/21/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.23 dmi.board.name: 2A73h dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.01 dmi.chassis.asset.tag: MXL8220VQN dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.23:bd04/21/2008:svnHewlett-Packard:pnHPCompaqdx2400Microtower:pvr:rvnPEGATRONCORPORATION:rn2A73h:rvr1.01:cvnHewlett-Packard:ct3:cvrChassisVersion: dmi.product.name: HP Compaq dx2400 Microtower dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.8.4+bzr3407-0ubuntu1 version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1078983/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net
[Touch-packages] [Bug 1069270] Re: [quantal][regression] googleearth 3d graphics don't work with nvidia GeForce4 card
John Harrington, thank you for reporting this and helping make Ubuntu better. As per https://wiki.ubuntu.com/Releases, Ubuntu 12.10 reached EOL on May 16, 2014. Is this reproducible on a supported release? ** Changed in: mesa (Ubuntu) Importance: Undecided => Low ** Changed in: mesa (Ubuntu) Status: New => Incomplete -- 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/1069270 Title: [quantal][regression] googleearth 3d graphics don't work with nvidia GeForce4 card Status in mesa package in Ubuntu: Incomplete Bug description: After upgrade to quantal, which I believe caused an upgrade in mesa from 8.x to 9.0, I can no longer use googleearth. Previously, it worked pretty well using the mesa DRI driver. The only problems were that borders sometimes showed through the earth from over the horizon, and it was necessary to turn off the atmosphere display. After the upgrade, from any altitude the surface of the globe appears as large rectangles, sometimes with various more or less triangular shapes. See attached screen shot. I tried this first with both libgl1-mesa-dri and libgl1-mesa-dri- experimental installed. I then removed libgl1-mesa-dri-experimental, powered off and rebooted. It didn't make a difference. My graphics card is: NVIDIA Corporation NV18 [GeForce4 MX 4000] ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: libgl1-mesa-dri 9.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic i686 ApportVersion: 2.6.1-0ubuntu3 Architecture: i386 Date: Sat Oct 20 23:01:03 2012 InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) SourcePackage: mesa UpgradeStatus: Upgraded to quantal on 2012-10-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1069270/+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 1074824] Re: Mesa 9.0 (quantal) uses LLVMpipe (slow) on ThinkPad L412. Mesa 9.1 solves it.
jmalter, thank you for reporting this and helping make Ubuntu better. As per https://wiki.ubuntu.com/Releases, Ubuntu 12.10 reached EOL as of May 16, 2014. Is this reproducible in a supported release? ** Tags added: bios-outdated-1.39 ** Changed in: mesa (Ubuntu) Importance: Undecided => Low ** Changed in: mesa (Ubuntu) Status: New => Incomplete -- 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/1074824 Title: Mesa 9.0 (quantal) uses LLVMpipe (slow) on ThinkPad L412. Mesa 9.1 solves it. Status in mesa package in Ubuntu: Incomplete Bug description: #803943 is marked as fixed, but it is not fixed. With 12.10 and Intel HD Graphics the problem still persists In idle phase compiz top show 80%-120% cpu and shows load between 1,2 and 2,2 ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: compiz 1:0.9.8.4-0ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,regex,imgpng,grid,place,move,resize,vpswitch,mousepoll,animation,unitymtgrabhandles,gnomecompat,snap,session,workarounds,wall,expo,fade,ezoom,scale,unityshell] CompositorRunning: compiz Date: Sun Nov 4 09:34:10 2012 DistUpgraded: 2012-10-18 21:41:59,032 DEBUG enabling apt cron job DistroCodename: quantal DistroVariant: ubuntu DkmsStatus: vboxhost, 4.2.4: added GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:215a] InstallationDate: Installed on 2012-04-27 (190 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MachineType: LENOVO 44036KG MarkForUpload: True PackageArchitecture: all ProcEnviron: SHELL=/bin/bash TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-17-generic root=UUID=5b92ef9d-8635-498c-b57d-ddf886a440ae ro quiet splash vt.handoff=7 SourcePackage: compiz UpgradeStatus: Upgraded to quantal on 2012-10-18 (16 days ago) dmi.bios.date: 03/28/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 81ET61WW (1.37 ) dmi.board.name: 44036KG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr81ET61WW(1.37):bd03/28/2012:svnLENOVO:pn44036KG:pvrThinkPadL412:rvnLENOVO:rn44036KG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 44036KG dmi.product.version: ThinkPad L412 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.8.4-0ubuntu3 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1074824/+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 1068832] Re: [nouveau] Unity flashing and slow
Williams Costa, thank you for reporting this and helping make Ubuntu better. As per https://wiki.ubuntu.com/Releases, Ubuntu 12.10 is EOL as of May 16, 2014. Is this reproducible in a supported release? ** Tags added: bios-outdated-0120 ** Changed in: mesa (Ubuntu) Importance: Undecided => Low ** Changed in: mesa (Ubuntu) Status: New => Incomplete -- 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/1068832 Title: [nouveau] Unity flashing and slow Status in mesa package in Ubuntu: Incomplete Bug description: 12.10 x64 ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu4 Architecture: amd64 CheckboxSubmission: 3212318c286f3b068b52849bac861aa1 CheckboxSystem: daed2f3d6643b4a84b4520a2427f8c2b CompizPlugins: [core,composite,opengl,compiztoolbox,decor,imgpng,gnomecompat,snap,mousepoll,resize,place,expo,move,vpswitch,scale,grid,unitymtgrabhandles,regex,workarounds,wall,session,ezoom,unityshell] CompositorRunning: compiz Date: Fri Oct 19 17:10:02 2012 DistUpgraded: 2012-10-18 15:18:57,877 DEBUG enabling apt cron job DistroCodename: quantal DistroVariant: ubuntu DkmsStatus: vboxhost, 4.2.0, 3.2.0-31-generic, x86_64: installed vboxhost, 4.2.0, 3.2.0-32-generic, x86_64: installed vboxhost, 4.2.0, 3.5.0-17-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT218 [GeForce 8400 GS] [10de:10c3] (rev a2) (prog-if 00 [VGA controller]) InstallationMedia: This MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=49cdefb4-ddaf-4104-afa4-80e69a53870d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to quantal on 2012-10-18 (1 days ago) dmi.bios.date: 02/18/2011 dmi.bios.vendor: Intel Corp. dmi.bios.version: BEH6110H.86A.0020.2011.0218.1538 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH61BR dmi.board.version: G32662-203 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBEH6110H.86A.0020.2011.0218.1538:bd02/18/2011:svn:pn:pvr:rvn:rnDH61BR:rvrG32662-203:cvn:ct3:cvr: version.compiz: compiz 1:0.9.8.4-0ubuntu3 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1068832/+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 711061] Re: [MIR] openjpeg
I reviewed openjpeg version 1:1.5.2-3.1 as checked into Xenial. This should not be considered a full security audit. Security team NAK for moving openjpeg to main for 16.04. The source is nearly unreadable due to terrible formatting. I could not find any tab-sizes that allowed the code to be legible by any reasonable standard. I strongly recommend upstream should (a) run the entire codebase through indent(1) or a similar tool (b) enforce a standard, any standard. K recommended but really anything beats what this currently has. In one day of fuzzing with my laptop I found eight crashers that caused segmentation violation faults. They may be read-only or perhaps they may allow remote code execution but the source code is so difficult to read that I cannot volunteer my time to discover the causes. cppcheck as packaged with 14.04 LTS issued 21 warnings; almost all represent real bugs in the package. Upstream's 2.1.0 release is a mixed bag -- cppcheck reported 61 warnings; many looked similar to issues from 1.5.2. However, the eight crashing inputs I found no longer crashed the library. Less than four hours of fuzzing on my laptop found an input that crashes. Memory management is sloppy and may in fact provide routes for exploits. Integer types seem very casual; this library was not written with a strong awareness of C's extremely dangerous behaviours around signed integers, the usual integer promotion rules, and sign extension rules. In addition, this looks like a poor library interface -- errors are sent directly to stderr without any attempts to offer client programs any mediation, the error messages never include strerror() reasons meaning users have no feedback on what failed. We cannot support this library as it stands. Before we can support it, the source code layout needs to be addressed, cppcheck should be clean, and gcc warnings should be addressed. I strongly recommend sending this through Coverity as well. Here's a more concrete list of issues I found; I hope these are useful: - applications/codec/j2k_dump.c allocates a hugely oversized block of memory for getting directory listings. If the dirptr or dirptr->filename memory allocations fail, the program dies via NULL pointer write errors. This should instead work on one file at a time and avoid the entire disaster. - applications/codec/j2k_dump.c parameters.outfile misleading error message, the fopen() was for writing, not reading - applications/JavaOpenJPEG/JavaOpenJPEGDecoder.c get_num_images(), load_images() leak dir - Java_org_openJpeg_OpenJPEGJavaDecoder_internalDecodeJ2KtoImage() fails to close 'fsrc' in this error path: if(src == NULL) goto fin - OPJMarkerTree::OnSelChanged() allocates buffer with new[] but deallocates with delete - bmptoimage() never checks getc() error return code - bmptoimage() leaks IN - imagetopgx() leaks name via if (!fdest) error -- memory handling here is far too complicated - applications/codec/image_to_j2k.c main() far too complicated - applications/codec/image_to_j2k.c main() leaks f (not really relevant since the 'return 1' exits, but once this code is broken apart into something legible this will matter more) - yuv_num_frames() leaks f via if (end_of_f < frame_size) error - applications/mj2/mj2_to_frames.c main() far too complicated; leaks frame_codestream in the event of realloc() failure - xml_write_mdia() writes garbage via fprintf() with too few arguments - test_image() calls opj_image_destroy(image); on an image without a valid value via if(cio == NULL) error -- note doubled if(image == NULL) goto fin; checks as well, looks like copy-and-paste errors in this function too - read_siz_marker() does no fread()-related error checking - read_siz_marker() left-shifts plain 'char' values, on platforms with default signed chars this will probably cause a hugely negative value, which when passed to malloc(size_t) will be turned into a hugely positive value - applications/mj2/wrap_j2k_in_mj2.c main() far too complicated - applications/mj2/wrap_j2k_in_mj2.c main() calls free(buf) with undefined 'buf' value via if(cinfo == NULL) error path Notes to the future: Find a jpeg2000 image somewhere (I'll include one in my tarball of crashers) and stick it in fuzz/in/ ccmake to change the CC to /usr/bin/afl-gcc Build with AFL_HARDEN=1 make mkdir -p fuzz/in fuzz/out cd fuzz afl -i in -o out -f foo.j2k ../bin/ -i @@ -o foo.bmp Thanks -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openjpeg in Ubuntu. https://bugs.launchpad.net/bugs/711061 Title: [MIR] openjpeg Status in openjpeg package in Ubuntu: Confirmed Bug description: libopenjpeg should be included in main because compiling poppler with --enable-openjpeg in debian/rules gives poppler greater functionality (please see bug 710412). Since this change to /debian/rules adds libopenjpeg as a build-dep to poppler, which is in main,
[Touch-packages] [Bug 1464917] Re: reboot hangs at 'Reached target Shutdown'
Im also having this problem on 15.04 a fresh install -- 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/1464917 Title: reboot hangs at 'Reached target Shutdown' Status in systemd: New Status in systemd package in Ubuntu: Confirmed Bug description: I rebooted my 15.04 system, and found it hanging indefinitely at the plymouth shutdown screen. Hitting esc to reveal the console showed a normal set of shutdown messages, ending with 'Reached target Shutdown' (paraphrased from memory). The system never rebooted on its own. I had to use SysRq to finish the shutdown. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu6 ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8 Uname: Linux 3.19.0-20-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Jun 13 11:53:10 2015 InstallationDate: Installed on 2010-09-24 (1723 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) MachineType: LENOVO 2306CTO ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-20-generic root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to vivid on 2014-12-06 (189 days ago) dmi.bios.date: 10/25/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET97WW (2.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2306CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1464917/+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 711061] Re: [MIR] openjpeg
** Attachment added: "openjpeg-crashers.tar.gz" https://bugs.launchpad.net/ubuntu/+source/openjpeg/+bug/711061/+attachment/4586223/+files/openjpeg-crashers.tar.gz ** Changed in: openjpeg (Ubuntu) Assignee: Ubuntu Security Team (ubuntu-security) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openjpeg in Ubuntu. https://bugs.launchpad.net/bugs/711061 Title: [MIR] openjpeg Status in openjpeg package in Ubuntu: Confirmed Bug description: libopenjpeg should be included in main because compiling poppler with --enable-openjpeg in debian/rules gives poppler greater functionality (please see bug 710412). Since this change to /debian/rules adds libopenjpeg as a build-dep to poppler, which is in main, libopenjpeg must also be in main. Main inclusion requirements: 1. It is already in the universe. 2. The package is a new build-dep, and has a large user base (think evince). 3. Searching http://secunia.com/advisories/search/ for libopenjpeg gave zero results. 4. Libopenjpeg has no current Ubuntu bugs (https://bugs.launchpad.net/ubuntu/maverick/+source/openjpeg) in the Debian bug tracking system libopenjpeg has 1 open bug (http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=libopenjpeg2), this is an encoding bug, but the main use for this package will be decoding. Libopenjpeg does not require any configuration or debconf questions. 5. N/A 6. All build-deps are already included in main. 7. I am afraid that this is a bit over my head, hopefully someone else could ensure that this package meets the requirments here. Based on its long inclusion in Debian and Ubuntu I think that it should be alright here. 8.This is a fairly simple program not needed too much maintenance, as shown by the bug reports. 9. The package title and description seem to be in order. My only final comments are that I am sorry this may not be quite the normal MIR, but I am just a member of bug control, not a dev. Also, any help and advise along the way would be much appreciated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjpeg/+bug/711061/+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 711061] Re: [MIR] openjpeg
https://github.com/uclouvain/openjpeg/issues/718 -- fuzz-generated inputs https://github.com/uclouvain/openjpeg/issues/719 -- cppcheck issues -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openjpeg in Ubuntu. https://bugs.launchpad.net/bugs/711061 Title: [MIR] openjpeg Status in openjpeg package in Ubuntu: Confirmed Bug description: libopenjpeg should be included in main because compiling poppler with --enable-openjpeg in debian/rules gives poppler greater functionality (please see bug 710412). Since this change to /debian/rules adds libopenjpeg as a build-dep to poppler, which is in main, libopenjpeg must also be in main. Main inclusion requirements: 1. It is already in the universe. 2. The package is a new build-dep, and has a large user base (think evince). 3. Searching http://secunia.com/advisories/search/ for libopenjpeg gave zero results. 4. Libopenjpeg has no current Ubuntu bugs (https://bugs.launchpad.net/ubuntu/maverick/+source/openjpeg) in the Debian bug tracking system libopenjpeg has 1 open bug (http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=libopenjpeg2), this is an encoding bug, but the main use for this package will be decoding. Libopenjpeg does not require any configuration or debconf questions. 5. N/A 6. All build-deps are already included in main. 7. I am afraid that this is a bit over my head, hopefully someone else could ensure that this package meets the requirments here. Based on its long inclusion in Debian and Ubuntu I think that it should be alright here. 8.This is a fairly simple program not needed too much maintenance, as shown by the bug reports. 9. The package title and description seem to be in order. My only final comments are that I am sorry this may not be quite the normal MIR, but I am just a member of bug control, not a dev. Also, any help and advise along the way would be much appreciated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjpeg/+bug/711061/+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 1424263] Re: Broken dependencies
mike@mike-desktop ~ $ sudo apt-get install steam -y Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: steam:i386 : Depends: libgl1-mesa-dri:i386 Depends: libgl1-mesa-glx:i386 E: Unable to correct problems, you have held broken packages. -- 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/1424263 Title: Broken dependencies Status in mesa package in Ubuntu: Confirmed Status in steam package in Ubuntu: Confirmed Bug description: I can not install Steam from Steam website because reported package has broken dependencies. This bug affect any user that will install Ubuntu 14.04.2. Please fix it fast, cause i can not play my games on Linux. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libgl1-mesa-dri:i386 (not installed) ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 346.35 Sat Jan 10 21:27:15 PST 2015 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Unity Date: Sat Feb 21 21:40:49 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: nvidia, 346.35, 3.16.0-30-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GM107 [GeForce GTX 750 Ti] [10de:1380] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:84ac] InstallationDate: Installed on 2015-02-20 (1 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic.efi.signed root=UUID=ea315497-1076-4f76-a2da-dc65caca572f ro quiet splash loglevel=0 vt.handoff=7 SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/09/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.10 dmi.board.name: H87 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd07/09/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH87Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1~ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sat Feb 21 17:22:09 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.16.0-1ubuntu1.2~trusty2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1424263/+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 1441008] Re: under systemd avahi-daemon doesn't stay disabled when .local is detected
** Changed in: avahi (Ubuntu) Assignee: (unassigned) => Trent Lloyd (lathiat) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1441008 Title: under systemd avahi-daemon doesn't stay disabled when .local is detected Status in avahi package in Ubuntu: Triaged Bug description: When avahi daemon detects .local unicast domain, the daemon is disabled. When a user tries to resolve a domain name through nss, the daemon starts up. The root cause is most likely in systemd that starts the daemon when an application tries to access the socket through the systemd managed socket file. This behavior wasn't observed in 14.10 or earlier releases, thus the assumption towards systemd socket activation. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: avahi-daemon 0.6.31-4ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Apr 7 09:51:43 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2013-11-16 (506 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: avahi UpgradeStatus: Upgraded to vivid on 2015-03-18 (19 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1441008/+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 1539009] Re: Mouse cursor is unusably slow in Unity 8 with a 1000Hz mouse
** Also affects: mir/0.20 Importance: Undecided Status: New ** Changed in: mir/0.20 Milestone: None => 0.20.2 ** Changed in: mir/0.20 Status: New => Triaged ** Changed in: mir/0.20 Importance: Undecided => High -- 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/1539009 Title: Mouse cursor is unusably slow in Unity 8 with a 1000Hz mouse Status in Mir: Fix Committed Status in Mir 0.20 series: Triaged Status in QtMir: Invalid Status in mir package in Ubuntu: Triaged Status in qtmir package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Invalid Bug description: Logging in to Unity8 on desktop (xenial) the mouse cursor moves glacially slow. I have to move the mouse across the whole desk to get anywhere. This is surprising given bug 1524145 shows the opposite is happening in the Mir demo servers. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity8 8.11+16.04.20160122-0ubuntu1 ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3 Uname: Linux 4.3.0-7-generic x86_64 ApportVersion: 2.19.4-0ubuntu1 Architecture: amd64 Date: Thu Jan 28 18:32:27 2016 InstallationDate: Installed on 2015-12-03 (56 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151202) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1539009/+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 1536662] Re: [regression] Black screen: Mir hangs and then crashes on startup/login due to reading from /dev/random
** Changed in: mir/0.20 Milestone: None => 0.20.2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1536662 Title: [regression] Black screen: Mir hangs and then crashes on startup/login due to reading from /dev/random Status in Mir: In Progress Status in Mir 0.19 series: Won't Fix Status in Mir 0.20 series: Triaged Status in Unity System Compositor: Fix Committed Status in mir package in Ubuntu: Triaged Status in unity-system-compositor package in Ubuntu: Fix Released Bug description: cookie_factory attempts to read data from /dev/random at boot, and blocks until it has enough random data or timesout after 30 seconds. How I can reproduce 1. Run the Unity8 greeter as a mir server 2. Reboot Expected behavior: Greeter is displayed as mir && USC run happily Actual behavior: Mir throws an exception after 30 seconds Work-around: Before logging in, move the mouse around lots, for at least 20 seconds. And after logging in, while you're looking at a black screen, move the mouse around furiously. This will populate the kernel entropy pool sufficiently to avoid the hang and crash. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1536662/+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 1533544] Re: Cannot select BT speaker mode when a call established with a headset connected
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: dialer-app (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1533544 Title: Cannot select BT speaker mode when a call established with a headset connected Status in dialer-app package in Ubuntu: Confirmed Bug description: current build number: 228 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-01-13 12:16:33 version version: 228 version ubuntu: 20160113 version device: 20160108-efc96d8 version custom: 2015--36-46-vivid Steps: 1.Connect a head to your device through bluetooth 2.Make sure the headset is completely connected (You can play a music file to ensure) 3.Make a incoming call to the DUT and established the call Expectation: After step 3: the sound should come from the headset, when you tap the left icon on the device , you should see 3 options: bluetooth speaker, internal speaker and loud speaker Actual result : The sound comes directly from the device internal speaker , after i tapped the left icon on the phone , there are only two options: internal speaker and loud speaker . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1533544/+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 1552068] [NEW] 5.1 Surround Sound
Public bug reported: Unable to get 5.1 realtek surround sound to work. Changed channels to 6, still no results. Tried to install realtek driver, but kept getting a compile error, unable to locate kernal H please install full version. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Mar 1 22:37:43 2016 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:d606] InstallationDate: Installed on 2016-03-01 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: powerspec B651 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-30-generic root=UUID=a1327e5b-2893-4256-911c-d500d31a4998 ro quiet splash vt.handoff=7 SourcePackage: xorg UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2007 dmi.bios.vendor: Intel Corp. dmi.bios.version: NL94510J.86A.0020.2007.0907.1417 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: D945GCNL dmi.board.vendor: Intel Corporation dmi.board.version: AAD97184-104 dmi.chassis.asset.tag: ps dmi.chassis.type: 2 dmi.chassis.vendor: ps dmi.chassis.version: ps dmi.modalias: dmi:bvnIntelCorp.:bvrNL94510J.86A.0020.2007.0907.1417:bd09/07/2007:svnpowerspec:pnB651:pvr4.5j:rvnIntelCorporation:rnD945GCNL:rvrAAD97184-104:cvnps:ct2:cvrps: dmi.product.name: B651 dmi.product.version: 4.5j dmi.sys.vendor: powerspec version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Tue Mar 1 21:15:15 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 1 vendor GSM xserver.version: 2:1.17.2-1ubuntu9.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu wily -- 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/1552068 Title: 5.1 Surround Sound Status in xorg package in Ubuntu: New Bug description: Unable to get 5.1 realtek surround sound to work. Changed channels to 6, still no results. Tried to install realtek driver, but kept getting a compile error, unable to locate kernal H please install full version. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Mar 1 22:37:43 2016 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:d606] InstallationDate: Installed on 2016-03-01 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: powerspec B651 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-30-generic root=UUID=a1327e5b-2893-4256-911c-d500d31a4998 ro quiet splash vt.handoff=7 SourcePackage: xorg UdevLog: Error: [Errno 2] No such
[Touch-packages] [Bug 1058155] Re: 3d display artefacts and regressions with intel 945gm
Andreas E., thank you for reporting this and helping make Ubuntu better. As per https://wiki.ubuntu.com/Releases, Ubuntu 12.10 reached EOL on May 16, 2014. Is this reproducible in a supported release? ** Changed in: mesa (Ubuntu) Importance: Undecided => Medium ** Changed in: mesa (Ubuntu) Status: New => Incomplete -- 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/1058155 Title: 3d display artefacts and regressions with intel 945gm Status in mesa package in Ubuntu: Incomplete Bug description: When upgrading Ubuntu 12.04 to 12.10 (beta2) there appear artefacts in several applications: In Blender, elements of the user interface appear black or without text. In Google Earth (same install as in 12.04), polylines of country borders get fuzzy and the atmosphere isn't rendered as a smooth gradient. In Trimble SketchUp (running through Wine, same install as before upgrading to 12.10), the "sky" (upper part of the 3d viewport) is black and the 3d viewport freezes after some time. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-15.23-generic 3.5.4 Uname: Linux 3.5.0-15-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.5.2-0ubuntu4 Architecture: i386 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz Date: Fri Sep 28 16:21:05 2012 DistUpgraded: 2012-09-28 00:29:03,753 DEBUG enabling apt cron job DistroCodename: quantal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller]) Subsystem: QUANTA Computer Inc Device [152d:0754] Subsystem: QUANTA Computer Inc Device [152d:0754] InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) MachineType: MAXDATA PRO600IW PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-15-generic root=UUID=735f1559-19fe-448f-ac32-0a823308c88b ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to quantal on 2012-09-27 (0 days ago) dmi.bios.date: 08/25/2006 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: Q3B21 dmi.board.name: PRO600IW dmi.board.vendor: MAXDATA dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrQ3B21:bd08/25/2006:svnMAXDATA:pnPRO600IW:pvr5123660003:rvnMAXDATA:rnPRO600IW:rvrNotApplicable:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: PRO600IW dmi.product.version: 5123660003 dmi.sys.vendor: MAXDATA version.compiz: compiz 1:0.9.8.2+bzr3377-0ubuntu1 version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0~git20120917.7cfd42ce-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0~git20120917.7cfd42ce-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.8-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1058155/+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 1551998] Re: /usr/lib/arm-linux-gnueabihf/thumbnailer/thumbnailer-service:11:__gnu_cxx::new_allocator:std::allocator_traits:std::allocator_traits:std::vector:unity::thumbnailer::
Other than outright memory corruption, the bug is likely caused by a shutdown race of some kind. There does not seem to be any other way for the push_back to fail other than the vector being appended to having disappeared. That would also explain why we see this problem only rarely, once every few days. Memory corruption per se is highly unlikely. We regularly run all the tests with valgrind, and running the service explicitly under valgrind and exercising it with thumbnailer-admin does not show any memory corruption. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to thumbnailer in Ubuntu. https://bugs.launchpad.net/bugs/1551998 Title: /usr/lib/arm-linux-gnueabihf/thumbnailer/thumbnailer- service:11:__gnu_cxx::new_allocator:std::allocator_traits:std::allocator_traits:std::vector:unity::thumbnailer::service::DBusInterface::queueRequest Status in thumbnailer package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding thumbnailer. This problem was most recently seen with version 2.3+16.04.20160108.2-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/8add77002771c6051716699933a723afe033683d contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thumbnailer/+bug/1551998/+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 1551150] Re: devel-proposed - android lxc container fails to start
That part of the init script looks just plain wrong to me... I'm guessing the intent was for /dev/cpuctl to be a bind-mount of /sys/fs/cgroup but that's not at all what the code does. I'll update my local copy here to replace that by a simple symlink from /dev/cpuctl to /sys/fs/cgroup/cpu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1551150 Title: devel-proposed - android lxc container fails to start Status in Canonical System Image: Confirmed Status in lxc package in Ubuntu: New Bug description: Last known good image: ubuntu-touch/devel-proposed/ubuntu/mako 446 ubuntu-touch/devel-proposed/ubuntu/mako 447 (and higher) and equivalent images on other devices do not boot and hang on the boot logo. From the list of changes, it could be lxc: 446: lxc 2.0.0~rc2-0ubuntu2 447: lxc 2.0.0~rc3-0ubuntu1 Latest image with 2.0.0~rc4-0ubuntu1 doesn't boot either. lxc (2.0.0~rc3-0ubuntu1) xenial; urgency=medium * New upstream release (2.0.0~rc3) - Make the cgfs backend and cgns work without cgmanager - Manpage updates - Mark lxc-clone and lxc-start-ephemeral deprecated (still included) * Set --enable-deprecated so we still ship lxc-clone and lxc-start-ephemeral lxc (2.0.0~rc2-0ubuntu3) xenial; urgency=medium * Use versioned dependencies against the various binary packages. * Update lxc-templates to depend on lxc1 not lxc. (LP: #1549136) * Move the lxcfs recommends from lxc-templates to liblxc1. * Drop cgmanager, use the cgfs backend instead. * Have liblxc1 depend on systemd | cgroup-lite for cgfs backend. Device tarballs between 446 and 447 are the same. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+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 1551150] Re: devel-proposed - android lxc container fails to start
Update init script is: http://paste.ubuntu.com/15264484/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1551150 Title: devel-proposed - android lxc container fails to start Status in Canonical System Image: Confirmed Status in lxc package in Ubuntu: New Bug description: Last known good image: ubuntu-touch/devel-proposed/ubuntu/mako 446 ubuntu-touch/devel-proposed/ubuntu/mako 447 (and higher) and equivalent images on other devices do not boot and hang on the boot logo. From the list of changes, it could be lxc: 446: lxc 2.0.0~rc2-0ubuntu2 447: lxc 2.0.0~rc3-0ubuntu1 Latest image with 2.0.0~rc4-0ubuntu1 doesn't boot either. lxc (2.0.0~rc3-0ubuntu1) xenial; urgency=medium * New upstream release (2.0.0~rc3) - Make the cgfs backend and cgns work without cgmanager - Manpage updates - Mark lxc-clone and lxc-start-ephemeral deprecated (still included) * Set --enable-deprecated so we still ship lxc-clone and lxc-start-ephemeral lxc (2.0.0~rc2-0ubuntu3) xenial; urgency=medium * Use versioned dependencies against the various binary packages. * Update lxc-templates to depend on lxc1 not lxc. (LP: #1549136) * Move the lxcfs recommends from lxc-templates to liblxc1. * Drop cgmanager, use the cgfs backend instead. * Have liblxc1 depend on systemd | cgroup-lite for cgfs backend. Device tarballs between 446 and 447 are the same. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+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 1044068] Re: boot stops on Asus Eee x101CH with (l)ubuntu 12.10
michelf41, thank you for reporting this and helping make Ubuntu better. As per https://wiki.ubuntu.com/Releases, Ubuntu 12.10 is EOL as of May 16, 2014. Is this reproducible in a supported release? ** Changed in: mesa (Ubuntu) Importance: Undecided => Low ** Changed in: mesa (Ubuntu) Status: Confirmed => Incomplete -- 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/1044068 Title: boot stops on Asus Eee x101CH with (l)ubuntu 12.10 Status in mesa package in Ubuntu: Incomplete Bug description: After update booting stops at "Starting configure virtual network devices [OK] I noticed that one or two weeks ago, did a complete reinstallation of Lubuntu 12.10 alpha 3 that worked fine until today when I attempted an update hoping the bug had been fixed in between. Making a detour via safe mode and resume, boot stops with "Stopping System V runlevel compatibility [OK]" "Starting [OK]" Note that the first time booting ended with the command line and I could not do anything with it. (I am a layman) Very annoying ! Thanks for your attention Michel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1044068/+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 1041261] Re: [nouveau] Xorg crashed with SIGABRT
As per https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1041261/comments/6 . ** Changed in: mesa (Ubuntu) Status: Confirmed => Invalid -- 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/1041261 Title: [nouveau] Xorg crashed with SIGABRT Status in mesa package in Ubuntu: Invalid Bug description: I don't know further details about the issue. This problem was detected by Ubuntu. However, I've been having tons of problems with graphics, especially Unity Dash, for a couple of months now. Bringing up Unity Dash in 12.04 would scramble all the icons in Unity Panel and the dash as well. Playing videos often causes crashes after seeming to struggle for a while to play the video. I decided to update to Ubuntu 12.10 alpha3 for better graphics, but Unity Dash is unusable - flashing all the time and still scrambling all the icons. I used Ubuntu Tweak to set the Dash to the smaller desktop size (I'm actually using a desktop computer but viewing it on my widescreen TV). Using the smaller Dash stops the flickering most of the time, and the newer graphics don't seem to have anymore trouble playing videos, but there are still random crashes. This particular "crash" being reported here didn't appear to cause any issues though. The crashes I'm talking about aren't reportable because the computer freezes, not even responding to ctrl-alt-f1 or ctrl-alt- backspace, so that I have to use hardware to reboot. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: xserver-xorg-core 2:1.12.99.905-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-11.11-generic 3.5.2 Uname: Linux 3.5.0-11-generic i686 ApportVersion: 2.5.1-0ubuntu2 Architecture: i386 CrashCounter: 1 Date: Fri Aug 24 00:07:02 2012 DistUpgraded: 2012-08-23 14:30:03,347 DEBUG enabling apt cron job DistroCodename: quantal DistroVariant: ubuntu ExecutablePath: /usr/bin/Xorg GraphicsCard: NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. Device [19da:a127] InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) Lsusb: Bus 002 Device 004: ID 0451:2046 Texas Instruments, Inc. TUSB2046 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 005: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for Bluetooth MachineType: Unknow Unknow ProcCmdline: /usr/bin/X :0 -core -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch -background none ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-11-generic root=UUID=e92f6f09-fa78-4288-b695-6f763ae4e38d ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: ?? () from /lib/i386-linux-gnu/libc.so.6 ?? () Title: Xorg crashed with SIGABRT UpgradeStatus: Upgraded to quantal on 2012-08-23 (0 days ago) UserGroups: XorgLogOld: dmi.bios.date: 12/10/2009 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: NF-MCP61 dmi.board.vendor: nVIDIA dmi.chassis.type: 3 dmi.chassis.vendor: nVIDIA dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd12/10/2009:svnUnknow:pnUnknow:pvrUnknow:rvnnVIDIA:rnNF-MCP61:rvr:cvnnVIDIA:ct3:cvr: dmi.product.name: Unknow dmi.product.version: Unknow dmi.sys.vendor: Unknow version.compiz: compiz 1:0.9.8+bzr3319-0ubuntu2 version.libdrm2: libdrm2 2.4.38-0ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.4-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.12.99.905-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120713.6ef1ad6a-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.3-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.1-4~ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1041261/+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 1041770] Re: Weird artefacts on screen (white traces, white boxes around windows)
cagara, as per https://wiki.ubuntu.com/Releases, Ubuntu 12.10 reached EOL on May 16, 2014. Is this reproducible on a supported release? ** Changed in: mesa (Ubuntu) Importance: Undecided => Low ** Changed in: mesa (Ubuntu) Status: New => Incomplete -- 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/1041770 Title: Weird artefacts on screen (white traces, white boxes around windows) Status in mesa package in Ubuntu: Incomplete Bug description: Sometimes when changing the focus between windows a bunch of odd artefacts occur on the screen. Most likely white trails appear on top of the screen or across the firefox toolbar, or big white boxes appear around a window. Those artefacts have in common that they dissapear the moment i change the focus to another window. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: plasma-desktop 4:4.9.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-11.11-generic 3.5.2 Uname: Linux 3.5.0-11-generic x86_64 ApportVersion: 2.5.1-0ubuntu2 Architecture: amd64 Date: Sun Aug 26 09:49:11 2012 InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120824) ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: kde-workspace UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1041770/+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 1043132] Re: compiz crashed closing command window
Peter T Hayward, thank you for reporting this and helping make Ubuntu better. As per https://wiki.ubuntu.com/Releases, Ubuntu 12.10 reached EOL on May 16, 2014. Is this reproducible on a supported release? ** Tags added: bios-outdated-03b ** Changed in: mesa (Ubuntu) Importance: Undecided => Low ** Changed in: mesa (Ubuntu) Status: Confirmed => Incomplete -- 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/1043132 Title: compiz crashed closing command window Status in mesa package in Ubuntu: Incomplete Bug description: Running ubuntu 12.10 on Apple iMac 11,2. Just upgraded (included kernel 3.5.0-13) and rebooted. Ran 'top' in command window and watched compiz CPU level (seems lower now). Quit 'top' with q. Tried to close command window with red X button. No reaction and desktop froze - except for mouse pointer. Gave it a minute and switched to tty1. Switched back to tty7 and after a few seconds the desktop returned. A crash window came up... identifying compiz. I chose to restart compiz. I have had several compiz-related crashes lately, most have been unreportable due to apport not completing its process. One bug title, occuring just after this one I am reporting, was 'compiz crashed with SIGSEGV in TfpTexture::bindTexImage()'. The crash report for that seemed to hang at the web page stage, which is where I got this title. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-13.13-generic 3.5.3 Uname: Linux 3.5.0-13-generic x86_64 ApportVersion: 2.5.1-0ubuntu3 Architecture: amd64 Date: Wed Aug 29 08:27:02 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices [AMD] nee ATI RV730 XT [Mobility Radeon HD 4670] [1002:9488] (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Device [106b:00b6] InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64+mac (20120819) MachineType: Apple Inc. iMac11,2 ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: vmlinuz-3.5.0-13-generic root=UUID=d3dd900b-6717-4b39-838b-a636b460d5df ro nosplash nomodeset initrd=EFI\ubuntu\initrd.img-3.5.0-13-generic SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/11 dmi.bios.vendor: Apple Inc. dmi.bios.version: IM112.88Z.0057.B01.1112090906 dmi.board.name: Mac-F2238AC8 dmi.board.vendor: Apple Inc. dmi.chassis.type: 13 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F2238AC8 dmi.modalias: dmi:bvnAppleInc.:bvrIM112.88Z.0057.B01.1112090906:bd12/09/11:svnAppleInc.:pniMac11,2:pvr1.0:rvnAppleInc.:rnMac-F2238AC8:rvr:cvnAppleInc.:ct13:cvrMac-F2238AC8: dmi.product.name: iMac11,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz 1:0.9.8+bzr3319-0ubuntu3 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.38-0ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0~git20120821.c1114c61-0ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental 9.0~git20120821.c1114c61-0ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 9.0~git20120821.c1114c61-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.12.99.905-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120713.6ef1ad6a-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.3-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.1-4~ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1043132/+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 1042413] Re: compiz crashed with SIGABRT in assert() from intel_resolve_map_set() from brw_draw_prims() from vbo_draw_arrays() from GLWindow::glDrawGeometry()
As per https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1042413/comments/9 . ** Changed in: mesa (Ubuntu) Status: Confirmed => Won't Fix -- 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/1042413 Title: compiz crashed with SIGABRT in assert() from intel_resolve_map_set() from brw_draw_prims() from vbo_draw_arrays() from GLWindow::glDrawGeometry() Status in Unity: Won't Fix Status in mesa package in Ubuntu: Won't Fix Status in unity package in Ubuntu: Won't Fix Bug description: Hi guys, Steps to reproduce: Plug in external monitor cable and wait for this crash. Seems that unity does not work properly with external displays. I use quantal, current/up to date, installation. Cheers, ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: unity 6.2.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-11.11-generic 3.5.2 Uname: Linux 3.5.0-11-generic x86_64 ApportVersion: 2.5.1-0ubuntu2 Architecture: amd64 Date: Mon Aug 27 22:35:26 2012 ExecutablePath: /usr/bin/compiz InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120815) ProcCmdline: compiz ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: unity StacktraceTop: raise () from /lib/x86_64-linux-gnu/libc.so.6 abort () from /lib/x86_64-linux-gnu/libc.so.6 ?? () from /lib/x86_64-linux-gnu/libc.so.6 __assert_fail () from /lib/x86_64-linux-gnu/libc.so.6 intel_resolve_map_set () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so Title: compiz crashed with SIGABRT in raise() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1042413/+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 1032690] Re: couldn't find RGB GLX visual or fbconfig
Rokk, thank you for reporting this and helping make Ubuntu better. Could you please run the following command once from a terminal by ensuring you have the package xdiagnose installed, and that you click the Yes button for attaching additional debugging information: apport-collect -p mesa 1032690 When reporting xorg related bugs in the future, please do so via the above method. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Changed in: mesa (Ubuntu) Importance: Undecided => Low ** Changed in: mesa (Ubuntu) Status: New => Incomplete -- 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/1032690 Title: couldn't find RGB GLX visual or fbconfig Status in mesa package in Ubuntu: Incomplete Bug description: Hi I have some troubles with nvidia and GLX here is the log: Error: couldn't find RGB GLX visual or fbconfig Xlib: extension "GLX" missing on display ":0". Xlib: extension "GLX" missing on display ":0". Xlib: extension "GLX" missing on display ":0". Xlib: extension "GLX" missing on display ":0". Xlib: extension "GLX" missing on display ":0". After the last update I cant start GNOME. Please help To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1032690/+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 1015068] Re: Bastion has lags
Ilmari Rouvinen, thank you for reporting this and helping make Ubuntu better. As per http://www.acer.com/ac/en/US/content/drivers an update to your computer's buggy, insecure, and outdated BIOS is available (3.04). If you update to this following https://help.ubuntu.com/community/BIOSUpdate does it change anything? For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette . Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful. Also, you don't have to create a new bug report. Once the BIOS is updated, if the problem is still reproducible: 1) Please provide the output of the following terminal command (not perform an apport-collect): sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date 2) Please make a comment specifically advising on if there was an improvement or not. 3) Please mark this report Status New. If it's not reproducible, please mark this as Invalid. Thank you for your understanding. ** Tags added: bios-outdated-3.04 ** Changed in: mesa (Ubuntu) Importance: Undecided => Low ** Changed in: mesa (Ubuntu) Status: New => Incomplete -- 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/1015068 Title: Bastion has lags Status in mesa package in Ubuntu: Incomplete Bug description: Bastion(game) worked properly, but after installing an update for it it started to have lags. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19 Uname: Linux 3.2.0-26-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu9 Architecture: i386 CompizPlugins: [core,bailer,detection,composite,opengl,decor,compiztoolbox,resize,gnomecompat,place,move,snap,imgpng,vpswitch,unitymtgrabhandles,mousepoll,regex,grid,session,animation,wall,workarounds,expo,fade,ezoom,scale,unityshell] CompositorRunning: compiz Date: Tue Jun 19 13:43:29 2012 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:010d] Subsystem: Acer Incorporated [ALI] Device [1025:010d] InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) MachineType: Acer TravelMate 6410 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-26-generic root=UUID=2a452751-11c8-4fe3-b7b5-6f674d859241 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/27/06 dmi.bios.vendor: Acer dmi.bios.version: 1.02 dmi.board.name: Coniston dmi.board.vendor: Acer dmi.board.version: Not Applicable dmi.chassis.type: 1 dmi.chassis.vendor: Acer dmi.chassis.version: N/A dmi.modalias: dmi:bvnAcer:bvr1.02:bd09/27/06:svnAcer:pnTravelMate6410:pvrCSR-000F:rvnAcer:rnConiston:rvrNotApplicable:cvnAcer:ct1:cvrN/A: dmi.product.name: TravelMate 6410 dmi.product.version: CSR-000F dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.7.8-0ubuntu1 version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3.1 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1.2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1015068/+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 1164016] Re: restore type-ahead find
** Changed in: nautilus Status: Confirmed => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1164016 Title: restore type-ahead find Status in Nautilus: Expired Status in nautilus package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: GNOME removed type-ahead find in Nautilus 3.6, not without controversy: https://mail.gnome.org/archives/nautilus- list/2012-August/msg2.html Now when you type in a Nautilus window, Nautilus immediately performs a search in the current directory and all its subdirectories. I personally find this annoying. If I want to search, I'll click the search icon. Often I'm looking at a long directory listing and simply want to jump to a certain point in it, and type-ahead find works great for that. Would Ubuntu consider patching type-ahead find back in? To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+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 1031220] Re: intel 965gm driver from xorg-edgers blacks screen with Kubuntu 12.04
HinzundKunz, thank you for reporting this and helping make Ubuntu better. Could you please run the following command once from a terminal by ensuring you have the package xdiagnose installed, and that you click the Yes button for attaching additional debugging information: apport-collect -p xorg 1031220 When reporting xorg related bugs in the future, please do so via the above method. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Package changed: mesa (Ubuntu) => xorg (Ubuntu) ** Changed in: xorg (Ubuntu) Importance: Undecided => Low ** Changed in: xorg (Ubuntu) Status: Confirmed => Incomplete -- 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/1031220 Title: intel 965gm driver from xorg-edgers blacks screen with Kubuntu 12.04 Status in xorg package in Ubuntu: Incomplete Bug description: The latest update of xorg-edgers (yesterday, July 30th, around noon here in Austria) got me into problems - the screen would go black after about 15 minutes or so and would refuse to come back (switching to console wouldn't help either, suspending-resuming does not work, switching off desktop effects doesn help nor prevent the problem). I had to go to the console (CTRL-ALT-F1) blindly and hit CTRL-ALT-DEL to reboot. After three times with trying different things to solve/prevent this behaviour, I had to revert to the standard drivers in the ubuntu repository to be able to keep on working. Steps to reproduce: boot into kde. Work anything. use keyboard, mouse, whatever. Expected behaviour: works, screen does not get blacked out (or, after going into energy saving, will come back if mouse or keyboard is used). Actual behaviour: Screen gets black after some time (~10-15 minutes) and refuses to come back. I'm afraid I can't help with tracking, as I had to revert to the standard drivers to be able to continue work (it's my office machine), but the report still might be helpful? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1031220/+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 984452] Re: [GM965] Poor performance ubuntu 12.04 on Intel® 965GM x86/MMX/SSE2 [8086:2a00]
André Lopes, as per http://www.toshiba.co.uk/innovation/download_bios.jsp?service=UK an update to your computer's buggy, insecure, and outdated BIOS is available (5.60). If you update to this following https://help.ubuntu.com/community/BIOSUpdate does it change anything? For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette . Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful. Also, you don't have to create a new bug report. Once the BIOS is updated, if the problem is still reproducible: 1) Please provide the output of the following terminal command (not perform an apport-collect): sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date 2) Please make a comment specifically advising on if there was an improvement or not. 3) Please mark this report Status New. If it's not reproducible, please mark this as Invalid. Thank you for your understanding. ** Project changed: mesa => mesa (Ubuntu) ** Tags removed: bios-outdated-2.60 ** Tags added: bios-outdated-5.60 ** Changed in: mesa (Ubuntu) Importance: Undecided => Low ** Changed in: mesa (Ubuntu) Status: New => Incomplete -- 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/984452 Title: [GM965] Poor performance ubuntu 12.04 on Intel® 965GM x86/MMX/SSE2 [8086:2a00] Status in mesa package in Ubuntu: Incomplete Bug description: I have experienced some noticeable differences in performance of the graphics card (Intel® 965GM x86/MMX/SSE2) in Ubuntu to compared with Windows XP. In Smokin Guns Game, in lowest graphics, could not more than 60 FPS. In Windows XP, with maximum definition, played games requiring graphics capabilities, such as evalution Pro Soccer 2008 and 2009, FIFA Street, Counter Strike Source, Prince of Persia and GTA San Andreas, and the computer didn't lose performance. In Ubuntu, the simple game, Smokin Guns ( http://forum.smokin- guns.org/ ), play just 40/60 FPS in lower graphics... In higher quality, some 10/20 FPS. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. AplayDevices: List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 ApportVersion: 2.0.1-0ubuntu4 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ze 1838 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfc50 irq 49' Mixer name : 'Realtek ALC268' Components : 'HDA:10ec0268,1179ff02,0013 HDA:11c11040,11790001,00100200' Controls : 17 Simple ctrls : 10 DistroRelease: Ubuntu 12.04 HibernationDevice: RESUME=UUID=37201652-e065-4026-bcfc-f5103aab6b5e InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) MachineType: TOSHIBA Satellite A200 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-23-generic root=UUID=d577e94a-fc7a-4d65-975b-dd18d1f8279c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 RelatedPackageVersions: linux-restricted-modules-3.2.0-23-generic N/A linux-backports-modules-3.2.0-23-generic N/A linux-firmware1.79 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Tags: precise precise Uname: Linux 3.2.0-23-generic i686 UpgradeStatus: Upgraded to precise on 2012-04-08 (9 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 09/27/2007 dmi.bios.vendor: TOSHIBA dmi.bios.version: V1.70 dmi.board.name: ISKAA dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV1.70:bd09/27/2007:svnTOSHIBA:pnSatelliteA200:pvrPSAE3E-03P00MPT:rvnTOSHIBA:rnISKAA:rvr1.00:cvnTOSHIBA:ct10:cvrN/A: dmi.product.name: Satellite A200 dmi.product.version: PSAE3E-03P00MPT dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/984452/+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 984452] Re: [GM965] Poor performance ubuntu 12.04 on Intel® 965GM x86/MMX/SSE2 [8086:2a00]
** Tags added: bios-outdated-2.60 ** No longer affects: mesa (Ubuntu) -- 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/984452 Title: [GM965] Poor performance ubuntu 12.04 on Intel® 965GM x86/MMX/SSE2 [8086:2a00] Status in mesa package in Ubuntu: Incomplete Bug description: I have experienced some noticeable differences in performance of the graphics card (Intel® 965GM x86/MMX/SSE2) in Ubuntu to compared with Windows XP. In Smokin Guns Game, in lowest graphics, could not more than 60 FPS. In Windows XP, with maximum definition, played games requiring graphics capabilities, such as evalution Pro Soccer 2008 and 2009, FIFA Street, Counter Strike Source, Prince of Persia and GTA San Andreas, and the computer didn't lose performance. In Ubuntu, the simple game, Smokin Guns ( http://forum.smokin- guns.org/ ), play just 40/60 FPS in lower graphics... In higher quality, some 10/20 FPS. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. AplayDevices: List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 ApportVersion: 2.0.1-0ubuntu4 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ze 1838 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfc50 irq 49' Mixer name : 'Realtek ALC268' Components : 'HDA:10ec0268,1179ff02,0013 HDA:11c11040,11790001,00100200' Controls : 17 Simple ctrls : 10 DistroRelease: Ubuntu 12.04 HibernationDevice: RESUME=UUID=37201652-e065-4026-bcfc-f5103aab6b5e InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) MachineType: TOSHIBA Satellite A200 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-23-generic root=UUID=d577e94a-fc7a-4d65-975b-dd18d1f8279c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 RelatedPackageVersions: linux-restricted-modules-3.2.0-23-generic N/A linux-backports-modules-3.2.0-23-generic N/A linux-firmware1.79 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Tags: precise precise Uname: Linux 3.2.0-23-generic i686 UpgradeStatus: Upgraded to precise on 2012-04-08 (9 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 09/27/2007 dmi.bios.vendor: TOSHIBA dmi.bios.version: V1.70 dmi.board.name: ISKAA dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV1.70:bd09/27/2007:svnTOSHIBA:pnSatelliteA200:pvrPSAE3E-03P00MPT:rvnTOSHIBA:rnISKAA:rvr1.00:cvnTOSHIBA:ct10:cvrN/A: dmi.product.name: Satellite A200 dmi.product.version: PSAE3E-03P00MPT dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/984452/+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 984452] Re: [GM965] Poor performance ubuntu 12.04 on Intel® 965GM x86/MMX/SSE2 [8086:2a00]
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mesa (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/984452 Title: [GM965] Poor performance ubuntu 12.04 on Intel® 965GM x86/MMX/SSE2 [8086:2a00] Status in mesa package in Ubuntu: Incomplete Bug description: I have experienced some noticeable differences in performance of the graphics card (Intel® 965GM x86/MMX/SSE2) in Ubuntu to compared with Windows XP. In Smokin Guns Game, in lowest graphics, could not more than 60 FPS. In Windows XP, with maximum definition, played games requiring graphics capabilities, such as evalution Pro Soccer 2008 and 2009, FIFA Street, Counter Strike Source, Prince of Persia and GTA San Andreas, and the computer didn't lose performance. In Ubuntu, the simple game, Smokin Guns ( http://forum.smokin- guns.org/ ), play just 40/60 FPS in lower graphics... In higher quality, some 10/20 FPS. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. AplayDevices: List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 ApportVersion: 2.0.1-0ubuntu4 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ze 1838 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfc50 irq 49' Mixer name : 'Realtek ALC268' Components : 'HDA:10ec0268,1179ff02,0013 HDA:11c11040,11790001,00100200' Controls : 17 Simple ctrls : 10 DistroRelease: Ubuntu 12.04 HibernationDevice: RESUME=UUID=37201652-e065-4026-bcfc-f5103aab6b5e InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) MachineType: TOSHIBA Satellite A200 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-23-generic root=UUID=d577e94a-fc7a-4d65-975b-dd18d1f8279c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 RelatedPackageVersions: linux-restricted-modules-3.2.0-23-generic N/A linux-backports-modules-3.2.0-23-generic N/A linux-firmware1.79 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Tags: precise precise Uname: Linux 3.2.0-23-generic i686 UpgradeStatus: Upgraded to precise on 2012-04-08 (9 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 09/27/2007 dmi.bios.vendor: TOSHIBA dmi.bios.version: V1.70 dmi.board.name: ISKAA dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV1.70:bd09/27/2007:svnTOSHIBA:pnSatelliteA200:pvrPSAE3E-03P00MPT:rvnTOSHIBA:rnISKAA:rvr1.00:cvnTOSHIBA:ct10:cvrN/A: dmi.product.name: Satellite A200 dmi.product.version: PSAE3E-03P00MPT dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/984452/+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 1521299] Re: Update to 2.6.3
** Changed in: freetype (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to freetype in Ubuntu. https://bugs.launchpad.net/bugs/1521299 Title: Update to 2.6.3 Status in freetype package in Ubuntu: Triaged Status in freetype package in Debian: Fix Released Bug description: Please update the package to 2.6.3. There's quite a bit of interesting new features and stability fixes via fuzzing since 2.5.x, have a look at www.freetype.org -> "More on the 2.6.2 release for users and developers". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/1521299/+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 955277] Re: screen flickering with RevengeOfTheTitans
Achim, could you please provide the full computer model as noted on the sticker of the computer itself (not from the Bug Description)? ** Changed in: mesa (Ubuntu) Importance: Undecided => Low ** Changed in: mesa (Ubuntu) Status: New => Incomplete -- 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/955277 Title: screen flickering with RevengeOfTheTitans Status in Mesa: Confirmed Status in mesa package in Ubuntu: Incomplete Bug description: I have attached a video which shows the problem. As it seems something is going wrong with rendering in RevengeOfTheTitans and other apps. I also noticed the problem with WorldOfGoo for example. The flickering always happens not only in fullscreen mode. It also happens in unity2d. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libgl1-mesa-dri 8.0.1-0ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-18.29-generic-pae 3.2.9 Uname: Linux 3.2.0-18-generic-pae i686 .tmp.unity.support.test.0: ApportVersion: 1.94.1-0ubuntu2 Architecture: i386 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz Date: Wed Mar 14 18:09:16 2012 DistUpgraded: Log time: 2012-03-12 17:17:59.131744 DistroCodename: precise DistroVariant: ubuntu ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu GraphicsCard: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:01bd] Subsystem: Dell Device [1028:01bd] InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120301) MachineType: Dell Inc. MM061 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-18-generic-pae root=UUID=cc1d049b-4ada-452b-a801-0f99d6874b3c ro quiet splash vt.handoff=7 SourcePackage: mesa UpgradeStatus: Upgraded to precise on 2012-03-12 (2 days ago) dmi.bios.date: 06/13/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0KD882 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd06/13/2007:svnDellInc.:pnMM061:pvr:rvnDellInc.:rn0KD882:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: MM061 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.7.0+bzr3035-0ubuntu1 version.libdrm2: libdrm2 2.4.30-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.1-0ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.1-0ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.99.901+git20120126-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/955277/+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 977440] Re: encountered bug while using openGL plugin in pcsx
Charles Oblender, thank you for reporting this and helping make Ubuntu better. As per https://wiki.ubuntu.com/Releases, Ubuntu 11.10 is EOL as of May 9, 2013. Is this reproducible in a supported release? ** Changed in: mesa (Ubuntu) Importance: Undecided => Low ** Changed in: mesa (Ubuntu) Status: New => Incomplete -- 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/977440 Title: encountered bug while using openGL plugin in pcsx Status in mesa package in Ubuntu: Incomplete Bug description: Tungsten Graphics, Inc. Mesa DRI R100 (RS200 4337) x86/MMX/SSE2 NO-TCL DRI2 *WARN_ONCE* File radeon_swtcl.c function r100_swtcl_flush line 325 Rendering was 1 commands larger than predicted size. We might overflow command buffer. *** drmRadeonCmdBuffer: -22. Kernel failed to parse or rejected command stream. See dmesg for more info. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: xorg 1:7.6+7ubuntu7.1 ProcVersionSignature: Ubuntu 3.0.0-17.30-generic 3.0.22 Uname: Linux 3.0.0-17-generic i686 ApportVersion: 1.23-0ubuntu4 Architecture: i386 Date: Mon Apr 9 14:26:51 2012 EcryptfsInUse: Yes InstallationMedia: ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/977440/+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 984452] [NEW] [GM965] Poor performance ubuntu 12.04 on Intel® 965GM x86/MMX/SSE2 [8086:2a00]
You have been subscribed to a public bug: I have experienced some noticeable differences in performance of the graphics card (Intel® 965GM x86/MMX/SSE2) in Ubuntu to compared with Windows XP. In Smokin Guns Game, in lowest graphics, could not more than 60 FPS. In Windows XP, with maximum definition, played games requiring graphics capabilities, such as evalution Pro Soccer 2008 and 2009, FIFA Street, Counter Strike Source, Prince of Persia and GTA San Andreas, and the computer didn't lose performance. In Ubuntu, the simple game, Smokin Guns ( http://forum.smokin-guns.org/ ), play just 40/60 FPS in lower graphics... In higher quality, some 10/20 FPS. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. AplayDevices: List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 ApportVersion: 2.0.1-0ubuntu4 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ze 1838 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfc50 irq 49' Mixer name : 'Realtek ALC268' Components : 'HDA:10ec0268,1179ff02,0013 HDA:11c11040,11790001,00100200' Controls : 17 Simple ctrls : 10 DistroRelease: Ubuntu 12.04 HibernationDevice: RESUME=UUID=37201652-e065-4026-bcfc-f5103aab6b5e InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) MachineType: TOSHIBA Satellite A200 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-23-generic root=UUID=d577e94a-fc7a-4d65-975b-dd18d1f8279c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 RelatedPackageVersions: linux-restricted-modules-3.2.0-23-generic N/A linux-backports-modules-3.2.0-23-generic N/A linux-firmware1.79 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Tags: precise precise Uname: Linux 3.2.0-23-generic i686 UpgradeStatus: Upgraded to precise on 2012-04-08 (9 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 09/27/2007 dmi.bios.vendor: TOSHIBA dmi.bios.version: V1.70 dmi.board.name: ISKAA dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV1.70:bd09/27/2007:svnTOSHIBA:pnSatelliteA200:pvrPSAE3E-03P00MPT:rvnTOSHIBA:rnISKAA:rvr1.00:cvnTOSHIBA:ct10:cvrN/A: dmi.product.name: Satellite A200 dmi.product.version: PSAE3E-03P00MPT dmi.sys.vendor: TOSHIBA ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: 965gm apport-collected bios-outdated-2.60 performance precise -- [GM965] Poor performance ubuntu 12.04 on Intel® 965GM x86/MMX/SSE2 [8086:2a00] https://bugs.launchpad.net/bugs/984452 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. -- 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 905972] Re: cheese crashed with SIGSEGV in parseOptInfoAttr()
Wim Jansen, thank you for reporting this and helping make Ubuntu better. As per https://wiki.ubuntu.com/Releases, Ubuntu 11.10 reached EOL on May 9, 2013. Is this reproducible on a supported release? ** No longer affects: mesa (Ubuntu) ** Project changed: cheese => mesa (Ubuntu) ** Package changed: mesa (Ubuntu) => mesa ** Changed in: mesa Importance: High => Undecided ** Changed in: mesa Status: Invalid => New ** Changed in: mesa Remote watch: GNOME Bug Tracker #671112 => None ** Project changed: mesa => mesa (Ubuntu) ** Tags added: latest-bios-1005 ** Changed in: mesa (Ubuntu) Importance: Undecided => Medium ** Changed in: mesa (Ubuntu) Status: New => Incomplete -- 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/905972 Title: cheese crashed with SIGSEGV in parseOptInfoAttr() Status in mesa package in Ubuntu: Incomplete Bug description: Additional information foor the Cheese crash report. ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: cheese 3.2.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9 Uname: Linux 3.0.0-14-generic i686 ApportVersion: 1.23-0ubuntu4 Architecture: i386 Date: Sun Dec 18 15:43:28 2011 ExecutablePath: /usr/bin/cheese InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) MachineType: System Manufacturer System Name ProcCmdline: cheese RelatedPackageVersions: cheese3.2.0-0ubuntu2 cheese-common 3.2.0-0ubuntu2 SegvAnalysis: Segfault happened at: 0x723a126: mov0x19c(%eax),%eax PC (0x0723a126) ok source "0x19c(%eax)" (0x019c) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: cheese StacktraceTop: ?? () from /usr/lib/i386-linux-gnu/dri/i915_dri.so ?? () from /usr/lib/i386-linux-gnu/dri/i915_dri.so intelMakeCurrent () from /usr/lib/i386-linux-gnu/dri/i915_dri.so ?? () from /usr/lib/i386-linux-gnu/dri/i915_dri.so ?? () from /usr/lib/i386-linux-gnu/mesa/libGL.so.1 Title: cheese crashed with SIGSEGV in intelMakeCurrent() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 11/28/2003 dmi.bios.vendor: Award Software, Inc. dmi.bios.version: ASUS P4BGL-VM ACPI BIOS Revision 1006 Beta 002 dmi.board.name: P4BGL-VM dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: REV 1.xx dmi.chassis.type: 7 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAwardSoftware,Inc.:bvrASUSP4BGL-VMACPIBIOSRevision1006Beta002:bd11/28/2003:svnSystemManufacturer:pnSystemName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP4BGL-VM:rvrREV1.xx:cvnChassisManufacture:ct7:cvrChassisVersion: dmi.product.name: System Name dmi.product.version: System Version dmi.sys.vendor: System Manufacturer lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 002: ID 04c8:0720 Konica Corp. Digital Color Camera To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/905972/+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 1374759] Re: >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
** Changed in: os-prober (Debian) Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1374759 Title: >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Triaged Status in os-prober package in Ubuntu: Confirmed Status in os-prober package in Debian: Fix Released Bug description: [ 556.734157] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled [ 556.746268] JFS: nTxBlock = 8192, nTxLock = 65536 [ 556.763789] ntfs: driver 2.1.30 [Flags: R/O MODULE]. [ 556.792231] QNX4 filesystem 0.2.3 registered. [ 557.922469] EXT4-fs (sda4): unable to read superblock [ 557.925868] EXT4-fs (sda4): unable to read superblock [ 557.928967] EXT4-fs (sda4): unable to read superblock [ 557.931784] FAT-fs (sda4): bogus number of reserved sectors [ 557.931791] FAT-fs (sda4): Can't find a valid FAT filesystem [ 557.946740] XFS (sda4): Invalid superblock magic number [ 557.951904] FAT-fs (sda4): bogus number of reserved sectors [ 557.951911] FAT-fs (sda4): Can't find a valid FAT filesystem [ 557.959099] MINIX-fs: unable to read superblock [ 557.965712] attempt to access beyond end of device [ 557.965721] sda4: rw=16, want=3, limit=2 [ 557.965725] hfsplus: unable to find HFS+ superblock [ 557.968487] qnx4: no qnx4 filesystem (no root dir). [ 557.971203] You didn't specify the type of your ufs filesystem mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep |nextstep-cd|openstep ... >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old [ 557.974459] hfs: can't find a HFS filesystem on dev sda4 [ 564.034208] EXT4-fs (sda4): unable to read superblock [ 564.040322] EXT4-fs (sda4): unable to read superblock [ 564.043485] EXT4-fs (sda4): unable to read superblock [ 564.047076] FAT-fs (sda4): bogus number of reserved sectors [ 564.047083] FAT-fs (sda4): Can't find a valid FAT filesystem [ 564.059578] XFS (sda4): Invalid superblock magic number [ 564.064473] FAT-fs (sda4): bogus number of reserved sectors [ 564.064489] FAT-fs (sda4): Can't find a valid FAT filesystem [ 564.072080] MINIX-fs: unable to read superblock [ 564.074564] attempt to access beyond end of device [ 564.074571] sda4: rw=16, want=3, limit=2 [ 564.074576] hfsplus: unable to find HFS+ superblock [ 564.076688] qnx4: no qnx4 filesystem (no root dir). [ 564.078847] You didn't specify the type of your ufs filesystem mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep |nextstep-cd|openstep ... >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old [ 564.080902] hfs: can't find a HFS filesystem on dev sda4 [ 570.554296] EXT4-fs (sda4): unable to read superblock [ 570.557647] EXT4-fs (sda4): unable to read superblock [ 570.560516] EXT4-fs (sda4): unable to read superblock [ 570.563451] FAT-fs (sda4): bogus number of reserved sectors [ 570.563460] FAT-fs (sda4): Can't find a valid FAT filesystem [ 570.574953] XFS (sda4): Invalid superblock magic number [ 570.580796] FAT-fs (sda4): bogus number of reserved sectors [ 570.580806] FAT-fs (sda4): Can't find a valid FAT filesystem [ 570.588340] MINIX-fs: unable to read superblock [ 570.590983] attempt to access beyond end of device [ 570.590993] sda4: rw=16, want=3, limit=2 [ 570.590999] hfsplus: unable to find HFS+ superblock [ 570.593321] qnx4: no qnx4 filesystem (no root dir). [ 570.595556] You didn't specify the type of your ufs filesystem mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep |nextstep-cd|openstep ... >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old [ 570.597775] hfs: can't find a HFS filesystem on dev sda4 [ 576.795014] EXT4-fs (sda4): unable to read superblock [ 576.797554] EXT4-fs (sda4): unable to read superblock [ 576.800063] EXT4-fs (sda4): unable to read superblock [ 576.802647] FAT-fs (sda4): bogus number of reserved sectors [ 576.802655] FAT-fs (sda4): Can't find a valid FAT filesystem [ 576.813305] XFS (sda4): Invalid superblock magic number [ 576.820257] FAT-fs (sda4): bogus number of reserved sectors [ 576.820276] FAT-fs (sda4): Can't find a valid FAT filesystem [ 576.830945] MINIX-fs: unable to read superblock [ 576.834108] attempt to access beyond end of device [ 576.834119] sda4: rw=16, want=3, limit=2 [ 576.834125] hfsplus: unable to find HFS+ superblock [ 576.837264] qnx4: no qnx4 filesystem (no root dir). [ 576.840408] You didn't specify the type of your ufs filesystem mount -t ufs -o
[Touch-packages] [Bug 901815] Re: Random image getting rendered in intel i945G graphics card
Prasanna Kumar, thank you for reporting this and helping make Ubuntu better. As per https://wiki.ubuntu.com/Releases, Ubuntu 11.10 reached EOL on May 9, 2013. Is this reproducible on a supported release? ** Changed in: mesa (Ubuntu) Importance: Undecided => Low ** Changed in: mesa (Ubuntu) Status: New => Incomplete -- 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/901815 Title: Random image getting rendered in intel i945G graphics card Status in mesa package in Ubuntu: Incomplete Bug description: Random image is rendered when I am doing normal work (like reading documents, web surfing, etc) with gnome 3 running. I am using ubuntu 11.10 64bit version. When I run gnome 2 (ubuntu classic without effects) no artifacts are there. When running gnome 2 (with compiz enabled) I am getting similar effects. Guess this to be related to OpenGL Mesa package. I am having a Intel 82945G/GZ graphics card. Mine is a fresh installation of ubuntu 11.10. My system is up to date. Output of certain commands that may be helpful: lspci: 00:02.0 VGA compatible controller: Intel Corporation 82945G/GZ Integrated Graphics Controller (rev 02) dmesg | grep drm: [ 19.370851] [drm] Initialized drm 1.1.0 20060810 [ 19.553129] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [ 19.553133] [drm] Driver supports precise vblank timestamp query. [ 19.598520] [drm] initialized overlay support [ 19.767735] fbcon: inteldrmfb (fb0) is primary device [ 19.767915] fb0: inteldrmfb frame buffer device [ 19.767917] drm: registered panic notifier [ 19.767949] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor 0 Things are going fine when there is no compiz (or gnome3). I guess it is because of OpenGL driver (mesa) as running gnome3 (mutter) also has the same effect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/901815/+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 879846] Re: Screen corruption in OpenGL varicad widgets [kubuntu]
Carlos Eduardo de Brito Novaes, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/879846/comments/2 regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find. ** Changed in: mesa (Ubuntu) Status: New => Invalid -- 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/879846 Title: Screen corruption in OpenGL varicad widgets [kubuntu] Status in mesa package in Ubuntu: Invalid Bug description: Varicad is a CAD software (http://varicad.com/en/home/) with an affordable price that I use the free viewer and was spending some time with the trial. I could made it work perfectly (they provide debs for x32 or x64) on Natty but on Oneiric Ocelot I got some screen corruptions on the color selection widgets (both from viewer and from the CAD tool itself). At first I tough that this could be some kind of setting (varicad use opengl for rendering) and tried every configuration that I could find on GUIs from the program and from the system, also tried to change the version of the proprietary nvidia driver (from 173 to current), reboot, but I was not able to get it work. Since the hardware is the same and the program runs very well on Natty, I think its a sort of BUG relative to Oneiric (maybe Xorg, maybe some strange setup on xorg.conf, maybe anything else). I had an image attached, on the left is a screenshot from Natty showing things as they should be and on the right the image from Oneiric. Almost forgot to mention, I tried some other programs like blender and some games and cant notice anything wrong. The problem only happens on varicad, maybe some specific OpenGL command... By now, I am totally clueless on what should I do to track down this behavior. Thank you very much for any help. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: xorg 1:7.6+7ubuntu7 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Sat Oct 22 08:21:21 2011 InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) ProcEnviron: LANGUAGE=pt_BR:pt:en LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/879846/+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 802584] Re: kwin crashes when prompting passwd after screensaver activation
Juan-Carlos Amengual, thank you for reporting this and helping make Ubuntu better. However, your crash report is missing. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. First, execute at a terminal: cd /var/crash && sudo rm * ; sudo apt-get update && sudo apt-get -y dist-upgrade && sudo service apport start force_start=1 If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart. Now reproduce the crash, then open a terminal, navigate to your /var/crash directory and file your report with: sudo ubuntu-bug /var/crash/_my_crash_report.crash where _my_crash_report.crash is the crash you would like to report. By default, this sends the crash to the Ubuntu Error Tracker infrastructure, which is different than Launchpad. For more on this, please see https://wiki.ubuntu.com/ErrorTracker . However, if after doing this you would still like to have a crash report posted to Launchpad, for example to ease triage and add others to your report, one would need to open the following file via a terminal: sudo nano /etc/apport/crashdb.conf and comment out the line: 'problem_types': ['Bug', 'Package'], by changing it to: # 'problem_types': ['Bug', 'Package'], Save, close, and file the crash report via: sudo ubuntu-bug /var/crash/FILENAME.crash Where FILENAME is the actual name of the file found in the folder. However, this report is being closed since the process outlined above will deal with this issue more efficiently. Also, please do not attach your crash report manually to this report and reopen it. Thank you for your understanding. Helpful bug reporting tips: https://wiki.ubuntu.com/ReportingBugs ** Changed in: mesa (Ubuntu) Status: New => Invalid -- 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/802584 Title: kwin crashes when prompting passwd after screensaver activation Status in mesa package in Ubuntu: Invalid Bug description: I have configured screen saver to activate after 15 min. of inactivity and power down screen of the laptop after 25 min. So well, almost always the laptop has activated the screen saver or even the screen is black after a long period of inactivity, when I press a key or move the mouse, a window prompting my pass pops and then kwin crashes. Most of the times, the window announcing the crash emerges (I didn't use to submit the bug report cause I don't have installed the dbg packages due to insufficient disk space in my /usr partition) and kwin is rerun and I can work with my laptop. But another times, the screen remains black or graphics begin to do weird things (windows partially deleted, desktops blinking, etc.). When the screen remains black, I switch to a console (CTRL+ALT+F1) kill the kwin process and when I return back to X (ALT+F7) there is no more black screen (I have my desktop) but there is no window manager, so I have to reboot in order to be able to work with my laptop. This is annoying! Firstly, I thought the bus was in kcometen4, the screen saver I used, but I changed to GLMatrix and problems remain (only slightly better). By the way, I think that the problems I have with laptop suspension and hibernation are related to this bug, because sometimes, when I wake the laptop up after an hibernation or a suspension I got a black screen (after the window prompting my pass pops up) or a crazy X desktop or directly a kwin crash. Please, let me know if I could be of help in some way. Thanks a lot for your work!!! ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: kde-window-manager 4:4.6.2a-0ubuntu5.1 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 Architecture: amd64 Date: Mon Jun 27 17:03:47 2011 InstallationMedia: Kubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427) ProcEnviron: LANGUAGE= PATH=(custom, user) LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: kdebase-workspace UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/802584/+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 853667] Re: ATI Radeon HD 3850 is completely unusable with default configuration due to frequent lockups
As per the Description. ** Changed in: mesa (Ubuntu) Status: New => Invalid -- 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/853667 Title: ATI Radeon HD 3850 is completely unusable with default configuration due to frequent lockups Status in mesa package in Ubuntu: Invalid Bug description: This issue is present in gallium drivers from mesa 7.10.x which are in Ubuntu 11.04. Ubuntu 11.10 is not affected, but the fix should be brought in to Ubuntu 11.04. I have an ATI Radeon 3850. Using the default drivers (xf86-video-ati and gallium for dri), I get lockups within a few seconds of any operation using DRI (compositing, OpenGL, whatever). The issue is fixed in the meas commit ecc051d65b6e17115439fb3609cccfd59f6272bf on master and should be brought in to Ubuntu to address this lockup. Please see this freedesktop bug for further information. https://bugs.freedesktop.org/show_bug.cgi?id=40979 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/853667/+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 905972] [NEW] cheese crashed with SIGSEGV in parseOptInfoAttr()
You have been subscribed to a public bug: Additional information foor the Cheese crash report. ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: cheese 3.2.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9 Uname: Linux 3.0.0-14-generic i686 ApportVersion: 1.23-0ubuntu4 Architecture: i386 Date: Sun Dec 18 15:43:28 2011 ExecutablePath: /usr/bin/cheese InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) MachineType: System Manufacturer System Name ProcCmdline: cheese RelatedPackageVersions: cheese3.2.0-0ubuntu2 cheese-common 3.2.0-0ubuntu2 SegvAnalysis: Segfault happened at: 0x723a126: mov0x19c(%eax),%eax PC (0x0723a126) ok source "0x19c(%eax)" (0x019c) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: cheese StacktraceTop: ?? () from /usr/lib/i386-linux-gnu/dri/i915_dri.so ?? () from /usr/lib/i386-linux-gnu/dri/i915_dri.so intelMakeCurrent () from /usr/lib/i386-linux-gnu/dri/i915_dri.so ?? () from /usr/lib/i386-linux-gnu/dri/i915_dri.so ?? () from /usr/lib/i386-linux-gnu/mesa/libGL.so.1 Title: cheese crashed with SIGSEGV in intelMakeCurrent() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 11/28/2003 dmi.bios.vendor: Award Software, Inc. dmi.bios.version: ASUS P4BGL-VM ACPI BIOS Revision 1006 Beta 002 dmi.board.name: P4BGL-VM dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: REV 1.xx dmi.chassis.type: 7 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAwardSoftware,Inc.:bvrASUSP4BGL-VMACPIBIOSRevision1006Beta002:bd11/28/2003:svnSystemManufacturer:pnSystemName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP4BGL-VM:rvrREV1.xx:cvnChassisManufacture:ct7:cvrChassisVersion: dmi.product.name: System Name dmi.product.version: System Version dmi.sys.vendor: System Manufacturer lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 002: ID 04c8:0720 Konica Corp. Digital Color Camera ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: apport-crash i386 oneiric running-unity -- cheese crashed with SIGSEGV in parseOptInfoAttr() https://bugs.launchpad.net/bugs/905972 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. -- 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 905972] [NEW] cheese crashed with SIGSEGV in parseOptInfoAttr()
You have been subscribed to a public bug: Additional information foor the Cheese crash report. ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: cheese 3.2.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9 Uname: Linux 3.0.0-14-generic i686 ApportVersion: 1.23-0ubuntu4 Architecture: i386 Date: Sun Dec 18 15:43:28 2011 ExecutablePath: /usr/bin/cheese InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) MachineType: System Manufacturer System Name ProcCmdline: cheese RelatedPackageVersions: cheese3.2.0-0ubuntu2 cheese-common 3.2.0-0ubuntu2 SegvAnalysis: Segfault happened at: 0x723a126: mov0x19c(%eax),%eax PC (0x0723a126) ok source "0x19c(%eax)" (0x019c) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: cheese StacktraceTop: ?? () from /usr/lib/i386-linux-gnu/dri/i915_dri.so ?? () from /usr/lib/i386-linux-gnu/dri/i915_dri.so intelMakeCurrent () from /usr/lib/i386-linux-gnu/dri/i915_dri.so ?? () from /usr/lib/i386-linux-gnu/dri/i915_dri.so ?? () from /usr/lib/i386-linux-gnu/mesa/libGL.so.1 Title: cheese crashed with SIGSEGV in intelMakeCurrent() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 11/28/2003 dmi.bios.vendor: Award Software, Inc. dmi.bios.version: ASUS P4BGL-VM ACPI BIOS Revision 1006 Beta 002 dmi.board.name: P4BGL-VM dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: REV 1.xx dmi.chassis.type: 7 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAwardSoftware,Inc.:bvrASUSP4BGL-VMACPIBIOSRevision1006Beta002:bd11/28/2003:svnSystemManufacturer:pnSystemName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP4BGL-VM:rvrREV1.xx:cvnChassisManufacture:ct7:cvrChassisVersion: dmi.product.name: System Name dmi.product.version: System Version dmi.sys.vendor: System Manufacturer lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 002: ID 04c8:0720 Konica Corp. Digital Color Camera ** Affects: mesa (Ubuntu) Importance: High Status: Invalid ** Tags: apport-crash i386 oneiric running-unity -- cheese crashed with SIGSEGV in parseOptInfoAttr() https://bugs.launchpad.net/bugs/905972 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. -- 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 1551982] Re: uncleared pch fifo underrun on pch transcoder A
Scott Stensland, thank you for reporting this and helping make Ubuntu better. To clarify, are there any other further issue, or just as per the Description: >"This appears in dmesg log and for a short while on black ascii screen during >login sequence [ 2.214317] [drm:intel_set_pch_fifo_underrun_reporting [i915]] >*ERROR* uncleared pch fifo underrun on pch transcoder A [ 2.214339] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A FIFO underrun" ** Tags added: latest-bios-406 ** Changed in: xorg (Ubuntu) Importance: Undecided => Low ** Changed in: xorg (Ubuntu) Status: New => Incomplete ** Description changed: - This appears in dmesg log and for a short while on black ascii screen - during login sequence - + After upgrading from 14.04 to 16.04, the following appears in dmesg and for a short while on black ascii screen during login sequence: [2.214317] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder A [2.214339] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A FIFO underrun - - I recently upgraded from 14.04 to 16.04 - - this gist contains output of - - lspci -vvnn - - https://gist.github.com/scottstensland/b9f54a88953d1433228f - - - uname -a - Linux bodhisattva 4.4.0-9-generic #24-Ubuntu SMP Mon Feb 29 19:33:19 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3 Uname: Linux 4.4.0-9-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: - NVRM version: NVIDIA UNIX x86_64 Kernel Module 355.00.26 Sun Feb 14 16:11:36 PST 2016 - GCC version: gcc version 5.3.1 20160225 (Ubuntu 5.3.1-10ubuntu2) + NVRM version: NVIDIA UNIX x86_64 Kernel Module 355.00.26 Sun Feb 14 16:11:36 PST 2016 + GCC version: gcc version 5.3.1 20160225 (Ubuntu 5.3.1-10ubuntu2) ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 1 16:55:32 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: - bbswitch, 0.8, 4.4.0-8-generic, x86_64: installed - bbswitch, 0.8, 4.4.0-9-generic, x86_64: installed - nvidia-355, 355.00.26, 4.4.0-8-generic, x86_64: installed - nvidia-355, 355.00.26, 4.4.0-9-generic, x86_64: installed + bbswitch, 0.8, 4.4.0-8-generic, x86_64: installed + bbswitch, 0.8, 4.4.0-9-generic, x86_64: installed + nvidia-355, 355.00.26, 4.4.0-8-generic, x86_64: installed + nvidia-355, 355.00.26, 4.4.0-9-generic, x86_64: installed GraphicsCard: - Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) -Subsystem: Micro-Star International Co., Ltd. [MSI] 3rd Gen Core processor Graphics Controller [1462:10b8] - NVIDIA Corporation GK107M [GeForce GT 645M] [10de:0fd9] (rev a1) (prog-if 00 [VGA controller]) -Subsystem: Micro-Star International Co., Ltd. [MSI] GK107M [GeForce GT 645M] [1462:10b8] + Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) + Subsystem: Micro-Star International Co., Ltd. [MSI] 3rd Gen Core processor Graphics Controller [1462:10b8] + NVIDIA Corporation GK107M [GeForce GT 645M] [10de:0fd9] (rev a1) (prog-if 00 [VGA controller]) + Subsystem: Micro-Star International Co., Ltd. [MSI] GK107M [GeForce GT 645M] [1462:10b8] InstallationDate: Installed on 2016-02-29 (1 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160228) MachineType: Micro-Star International Co., Ltd. CX61 0NC/CX61 0ND/CX61 0NF/CX61 0NE ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-9-generic root=UUID=7ffdb95a-c39d-4d4a-964a-eebefe28f75b ro quiet splash SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/10/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16GBIMS.406 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-16GB dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: CX61 0NC/CX61 0ND/CX61 0NF/CX61 0NE dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16GBIMS.406:bd10/10/2012:svnMicro-StarInternationalCo.,Ltd.:pnCX610NC/CX610ND/CX610NF/CX610NE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16GB:rvrREV1.0:cvnCX610NC/CX610ND/CX610NF/CX610NE:ct10:cvrN/A: dmi.product.name: CX61 0NC/CX61 0ND/CX61 0NF/CX61 0NE dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz 1:0.9.12.2+16.04.20160209-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri:
[Touch-packages] [Bug 1550706] Re: Thumbnails not working with qrc
Rather than looking at what is necessary to make files compiled into an
executable visible to an external process, could we step back a bit to
find out what we're trying to accomplish?
What do you think will be done differently by having "qrc:///images
/menu-background.jpg" passed through the thumbnailer rather than being
loaded directly by the Image component? If this is just a toy example
and your real use case is a little more complex, could you describe that
instead?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to thumbnailer in Ubuntu.
https://bugs.launchpad.net/bugs/1550706
Title:
Thumbnails not working with qrc
Status in Client Developer Experience:
New
Status in thumbnailer package in Ubuntu:
New
Bug description:
The thumbnailer works only if I load images from the file system, not
from a resource file:
Image {
id: backgroundImage
anchors.fill: parent
sourceSize: Qt.size(parent.width, parent.height)
source: "image://thumbnailer/qrc:///images/menu-background.jpg"
}
The default sdk template uses qrc as template.
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-developer-experience/+bug/1550706/+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 1551150] Re: devel-proposed - android lxc container fails to start
missing android signal was caused by double mounting of cgroup cpu, which was already mounted. Fixing that did take boot further, now lightdm becomes alive, still boot fails, and kills adb in the process... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1551150 Title: devel-proposed - android lxc container fails to start Status in Canonical System Image: Confirmed Status in lxc package in Ubuntu: New Bug description: Last known good image: ubuntu-touch/devel-proposed/ubuntu/mako 446 ubuntu-touch/devel-proposed/ubuntu/mako 447 (and higher) and equivalent images on other devices do not boot and hang on the boot logo. From the list of changes, it could be lxc: 446: lxc 2.0.0~rc2-0ubuntu2 447: lxc 2.0.0~rc3-0ubuntu1 Latest image with 2.0.0~rc4-0ubuntu1 doesn't boot either. lxc (2.0.0~rc3-0ubuntu1) xenial; urgency=medium * New upstream release (2.0.0~rc3) - Make the cgfs backend and cgns work without cgmanager - Manpage updates - Mark lxc-clone and lxc-start-ephemeral deprecated (still included) * Set --enable-deprecated so we still ship lxc-clone and lxc-start-ephemeral lxc (2.0.0~rc2-0ubuntu3) xenial; urgency=medium * Use versioned dependencies against the various binary packages. * Update lxc-templates to depend on lxc1 not lxc. (LP: #1549136) * Move the lxcfs recommends from lxc-templates to liblxc1. * Drop cgmanager, use the cgfs backend instead. * Have liblxc1 depend on systemd | cgroup-lite for cgfs backend. Device tarballs between 446 and 447 are the same. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+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 1551770] Re: Screen corruption
Anand, thank you for reporting this and helping make Ubuntu better. To see if this is already resolved, could you please test http://cdimage.ubuntu.com/daily-live/current/ and advise to the results? ** Tags added: latest-bios-0036 ** Changed in: xorg (Ubuntu) Importance: Undecided => Medium ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- 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/1551770 Title: Screen corruption Status in xorg package in Ubuntu: Incomplete Bug description: I get this very frequently mostly 8-10 times a day. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.2.0-30.36~14.04.1-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.19 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 CurrentDesktop: Unity Date: Tue Mar 1 19:55:42 2016 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:d606] InstallationDate: Installed on 2016-02-22 (8 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 (20160217.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-30-generic root=UUID=bd999da4-3262-4ce3-83ab-f166d1cfdce9 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/31/2009 dmi.bios.vendor: Intel Corp. dmi.bios.version: NL94510J.86A.0036.2009.1231.1407 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: D945GCNL dmi.board.vendor: Intel Corporation dmi.board.version: AAD97184-103 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrNL94510J.86A.0036.2009.1231.1407:bd12/31/2009:svn:pn:pvr:rvnIntelCorporation:rnD945GCNL:rvrAAD97184-103:cvn:ct3:cvr: version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Tue Mar 1 13:36:19 2016 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputSleep Button KEYBOARD, id 7 inputAT Translated Set 2 keyboard KEYBOARD, id 8 inputImPS/2 Logitech Wheel Mouse MOUSE, id 9 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id2151 vendor SAM xserver.version: 2:1.17.2-1ubuntu9.1~trusty1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1551770/+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 1550944] Re: Xorg crash
Tony Morton, thank you for reporting this and helping make Ubuntu better. As per http://www.dell.com/support/home/us/en/19/product-support/product /inspiron-660s/drivers?os=biosa an update to your computer's buggy, insecure, and outdated BIOS is available (A11). If you update to this following https://help.ubuntu.com/community/BIOSUpdate does it change anything? For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette . Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful. Also, you don't have to create a new bug report. Once the BIOS is updated, if the problem is still reproducible: 1) Please provide the output of the following terminal command (not perform an apport-collect): sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date 2) Please make a comment specifically advising on if there was an improvement or not. 3) Please mark this report Status New. If it's not reproducible, please mark this as Invalid. Thank you for your understanding. ** Tags added: bios-outdated-a11 ** Changed in: xorg (Ubuntu) Importance: Undecided => Low ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- 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/1550944 Title: Xorg crash Status in xorg package in Ubuntu: Incomplete Bug description: Since kernel 70.113 came in I have to log in twice at start up. After the first log in the desktop screen appears for a few seconds then crashes back to a black screen and then the log in screen appears again. After the second log in the system works normally. This is Ubuntu 14.04LTS 64 bit version ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-79.123-generic 3.13.11-ckt33 Uname: Linux 3.13.0-79-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Feb 28 15:57:17 2016 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0574] NVIDIA Corporation GF119 [GeForce GT 620 OEM] [10de:1049] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation Device [10de:0977] InstallationDate: Installed on 2014-05-19 (650 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. Inspiron 660s ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-79-generic.efi.signed root=UUID=cc041237-8a22-4bc4-9c3d-e7e4419eb999 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/24/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0478VN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd08/24/2012:svnDellInc.:pnInspiron660s:pvr:rvnDellInc.:rn0478VN:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: Inspiron 660s dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 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.6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sun Feb 28 14:39:14 2016 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 100 vendor ACR xserver.version: 2:1.15.1-0ubuntu2.7 To manage notifications about this bug go to:
[Touch-packages] [Bug 1551450] Re: ich weis nicht
jasmin, thank you for reporting this and helping make Ubuntu better. As per http://support.lenovo.com/us/en/products/Laptops-and- netbooks/Lenovo-G-Series- laptops/Lenovo-G505-Notebook?linkTrack=GPS:Body_Search%20Products=false an update to your computer's buggy, insecure, and outdated BIOS is available (2.04). If you update to this following https://help.ubuntu.com/community/BIOSUpdate does it change anything? For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette . Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful. Also, you don't have to create a new bug report. Once the BIOS is updated, if the problem is still reproducible: 1) Please provide the output of the following terminal command (not perform an apport-collect): sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date 2) Please make a comment specifically advising on if there was an improvement or not. 3) Please mark this report Status New. If it's not reproducible, please mark this as Invalid. Thank you for your understanding. ** Tags added: bios-outdated-204 ** Tags removed: bios-outdated-204 ** Tags added: bios-outdated-2.04 ** Changed in: xorg (Ubuntu) Importance: Undecided => Low ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- 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/1551450 Title: ich weis nicht Status in xorg package in Ubuntu: Incomplete Bug description: hallo ich denke das mein computer hat virus : dailer , proxy , remote virus ,boot virus ,recycle bin ,concurent boot . und magen und darm krebs lol shönen tag ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Feb 29 23:07:04 2016 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8210] [1002:9834] (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3802] InstallationDate: Installed on 2016-02-29 (0 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: LENOVO 20240 ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic root=UUID=feb1a3b2-448e-45cc-9447-409b3eb88dda ro recovery nomodeset Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/27/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 82CN23WW(V2.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo G505 dmi.board.vendor: LENOVO dmi.board.version: 3193Std dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G505 dmi.modalias: dmi:bvnLENOVO:bvr82CN23WW(V2.03):bd09/27/2013:svnLENOVO:pn20240:pvrLenovoG505:rvnLENOVO:rnLenovoG505:rvr3193Std:cvnLENOVO:ct10:cvrLenovoG505: dmi.product.name: 20240 dmi.product.version: Lenovo G505 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Mon Feb 29 22:58:25 2016 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.17.1-0ubuntu3~trusty1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1551450/+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 1552029] Re: Intermittently mouse corrupt on one screen
Jen Hart, thank you for reporting this and helping make Ubuntu better. As per https://us.msi.com/product/motherboard/support/X99A-SLI-PLUS.html #down-bios an update to your computer's buggy, insecure, and outdated BIOS is available (1.9). If you update to this following https://help.ubuntu.com/community/BIOSUpdate does it change anything? For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette . Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful. Also, you don't have to create a new bug report. Once the BIOS is updated, if the problem is still reproducible: 1) Please provide the output of the following terminal command (not perform an apport-collect): sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date 2) Please make a comment specifically advising on if there was an improvement or not. 3) Please mark this report Status New. If it's not reproducible, please mark this as Invalid. Thank you for your understanding. ** Tags added: bios-outdated-1.9 ** Changed in: xorg (Ubuntu) Importance: Undecided => Low ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- 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/1552029 Title: Intermittently mouse corrupt on one screen Status in xorg package in Ubuntu: Incomplete Bug description: Tried Gnome tweaks, tried changing monitors around, primary, (in case it was some how port related) etc. Can not reset the mouse cursor once it corrupts. Only solution I found was a reboot, which can be inconvenient. Might be related to Java applications somehow and their borders? P.S. I think my graphics card is R9 390 and has been picked up wrong by this bug report and by one game I know about (it thinks it is a HD 5600) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.19.0-51.58~14.04.1-generic 3.19.8-ckt13 Uname: Linux 3.19.0-51-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Mar 2 01:20:06 2016 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fglrx-updates-core, 15.201, 3.19.0-49-generic, x86_64: installed fglrx-updates-core, 15.201, 3.19.0-51-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Hawaii PRO [Radeon R9 290] [1002:67b1] (rev 80) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:2015] InstallationDate: Installed on 2015-11-24 (98 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: MSI MS-7885 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-51-generic.efi.signed root=UUID=46953798-0da7-48f9-8837-c446ced8f6f6 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/20/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.80 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X99A SLI PLUS(MS-7885) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.80:bd03/20/2015:svnMSI:pnMS-7885:pvr1.0:rvnMSI:rnX99ASLIPLUS(MS-7885):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7885 dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Tue Mar 1 10:55:41 2016 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory AIGLX error: failed to open
[Touch-packages] [Bug 1550050] Re: repeating phantom key when bt disconnects
** Changed in: mir Milestone: None => 0.21.0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1550050 Title: repeating phantom key when bt disconnects Status in Canonical System Image: Confirmed Status in Canonical Pocket Desktop: New Status in Mir: In Progress Status in bluez package in Ubuntu: Confirmed Status in mir package in Ubuntu: In Progress Bug description: Every now and then when having bt mouse/keyboard connected - you will see when selecting a text box there is a repeating character (there is no specific character, but always repeats) It seems to be related somehow to bt devices disconnecting the only cure is a reboot This was reproduced by turning off the keyboard while holding down a key. We suspect the key up event is never delivered. This mimics the case where the BT connection drops off momentarily or perhaps an event is missed over the BT connection. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1550050/+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 1552029] [NEW] Intermittently mouse corrupt on one screen
Public bug reported: Tried Gnome tweaks, tried changing monitors around, primary, (in case it was some how port related) etc. Can not reset the mouse cursor once it corrupts. Only solution I found was a reboot, which can be inconvenient. Might be related to Java applications somehow and their borders? P.S. I think my graphics card is R9 390 and has been picked up wrong by this bug report and by one game I know about (it thinks it is a HD 5600) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.19.0-51.58~14.04.1-generic 3.19.8-ckt13 Uname: Linux 3.19.0-51-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Mar 2 01:20:06 2016 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fglrx-updates-core, 15.201, 3.19.0-49-generic, x86_64: installed fglrx-updates-core, 15.201, 3.19.0-51-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Hawaii PRO [Radeon R9 290] [1002:67b1] (rev 80) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:2015] InstallationDate: Installed on 2015-11-24 (98 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: MSI MS-7885 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-51-generic.efi.signed root=UUID=46953798-0da7-48f9-8837-c446ced8f6f6 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/20/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.80 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X99A SLI PLUS(MS-7885) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.80:bd03/20/2015:svnMSI:pnMS-7885:pvr1.0:rvnMSI:rnX99ASLIPLUS(MS-7885):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7885 dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Tue Mar 1 10:55:41 2016 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] AIGLX error: failed to open /usr/X11R6/lib/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.17.1-0ubuntu3.1~trusty1 xserver.video_driver: fglrx ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu ** Description changed: Tried Gnome tweaks, tried changing monitors around, primary, (in case it was some how port related) etc. - Can not reset the mouse cursor once it corrupts. Only solution I found was a reboot, which can be inconvenient. + Can not reset the mouse cursor once it corrupts. Only solution I found was a reboot, which can be inconvenient. Might be related to Java applications somehow and their borders? + + P.S. I think my graphics card is R9 390 and has been picked up wrong by + this bug report and by one game I know about (it thinks it is a HD 5600) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.19.0-51.58~14.04.1-generic 3.19.8-ckt13 Uname: Linux 3.19.0-51-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: - + ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CompizPlugins: No value set for
[Touch-packages] [Bug 1540390] Re: Backport more recent driver for SKL, KBL and BXT graphics
** Branch linked: lp:ubuntu/trusty-proposed/linux-lts-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1540390 Title: Backport more recent driver for SKL, KBL and BXT graphics Status in initramfs-tools package in Ubuntu: New Status in linux package in Ubuntu: Fix Committed Bug description: We need to support Skylake (SKL), Kabylake (KBL) and Broxton (BXT) graphics in xenial, but the kernel driver is not fresh enough for proper support. For the kernel the plan is to provide a separate driver module (i915_bpo) like for Skylake/Broadwell/Braswell in vivid. The drm/i915 driver in 4.4 is not recent enough for SKL/KBL/BXT, so pulling the driver from current drm-intel-next branch would provide what'll end up in 4.6. The i915 drivers will be modified so that only i915_bpo loads on SKL/KBL/BXT machines, and only there. The driver will get further updates along the way, and possibly also rebased to a later kernel release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1540390/+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 1539209] Re: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume()
If your acer aspire 7540 have line in, mic and internal mic, do alsa driver disable auto mic selection by create capture source control for selecting input -- 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/1539209 Title: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() Status in pulseaudio package in Ubuntu: Incomplete Bug description: Appears randomly. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:7.1-1ubuntu3 ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3 Uname: Linux 4.3.0-7-generic x86_64 ApportVersion: 2.19.4-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: potato12883 F...m pulseaudio /dev/snd/controlC0: potato12883 F pulseaudio /dev/snd/controlC1: potato12883 F pulseaudio CurrentDesktop: Unity Date: Thu Jan 28 22:16:03 2016 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2016-01-17 (11 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog ProcEnviron: PATH=(custom, no user) SHELL=/bin/bash LANG=ru_RU.UTF-8 LANGUAGE=ru XDG_RUNTIME_DIR= Signal: 6 SourcePackage: pulseaudio StacktraceTop: pa_alsa_path_set_volume () from /usr/lib/pulse-7.1/modules/libalsa-util.so ?? () from /usr/lib/pulse-7.1/modules/libalsa-util.so pa_source_process_msg () from /usr/lib/libpulsecore-7.1.so ?? () from /usr/lib/pulse-7.1/modules/libalsa-util.so ?? () from /usr/lib/libpulsecore-7.1.so Title: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() UpgradeStatus: Upgraded to xenial on 2016-01-28 (0 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 12/07/2009 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: V1.11 dmi.board.name: JV71TR dmi.board.vendor: Acer dmi.board.version: Rev dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: None dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.11:bd12/07/2009:svnAcer:pnAspire7540:pvr0100:rvnAcer:rnJV71TR:rvrRev:cvnAcer:ct10:cvrNone: dmi.product.name: Aspire 7540 dmi.product.version: 0100 dmi.sys.vendor: Acer modified.conffile..etc.pulse.daemon.conf: [modified] mtime.conffile..etc.pulse.daemon.conf: 2016-01-25T21:44:07.089113 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1539209/+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 1374759] Re: >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
update the remote watch ** Bug watch added: Debian Bug tracker #735169 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735169 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1374759 Title: >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Triaged Status in os-prober package in Ubuntu: Confirmed Status in os-prober package in Debian: Unknown Bug description: [ 556.734157] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled [ 556.746268] JFS: nTxBlock = 8192, nTxLock = 65536 [ 556.763789] ntfs: driver 2.1.30 [Flags: R/O MODULE]. [ 556.792231] QNX4 filesystem 0.2.3 registered. [ 557.922469] EXT4-fs (sda4): unable to read superblock [ 557.925868] EXT4-fs (sda4): unable to read superblock [ 557.928967] EXT4-fs (sda4): unable to read superblock [ 557.931784] FAT-fs (sda4): bogus number of reserved sectors [ 557.931791] FAT-fs (sda4): Can't find a valid FAT filesystem [ 557.946740] XFS (sda4): Invalid superblock magic number [ 557.951904] FAT-fs (sda4): bogus number of reserved sectors [ 557.951911] FAT-fs (sda4): Can't find a valid FAT filesystem [ 557.959099] MINIX-fs: unable to read superblock [ 557.965712] attempt to access beyond end of device [ 557.965721] sda4: rw=16, want=3, limit=2 [ 557.965725] hfsplus: unable to find HFS+ superblock [ 557.968487] qnx4: no qnx4 filesystem (no root dir). [ 557.971203] You didn't specify the type of your ufs filesystem mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep |nextstep-cd|openstep ... >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old [ 557.974459] hfs: can't find a HFS filesystem on dev sda4 [ 564.034208] EXT4-fs (sda4): unable to read superblock [ 564.040322] EXT4-fs (sda4): unable to read superblock [ 564.043485] EXT4-fs (sda4): unable to read superblock [ 564.047076] FAT-fs (sda4): bogus number of reserved sectors [ 564.047083] FAT-fs (sda4): Can't find a valid FAT filesystem [ 564.059578] XFS (sda4): Invalid superblock magic number [ 564.064473] FAT-fs (sda4): bogus number of reserved sectors [ 564.064489] FAT-fs (sda4): Can't find a valid FAT filesystem [ 564.072080] MINIX-fs: unable to read superblock [ 564.074564] attempt to access beyond end of device [ 564.074571] sda4: rw=16, want=3, limit=2 [ 564.074576] hfsplus: unable to find HFS+ superblock [ 564.076688] qnx4: no qnx4 filesystem (no root dir). [ 564.078847] You didn't specify the type of your ufs filesystem mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep |nextstep-cd|openstep ... >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old [ 564.080902] hfs: can't find a HFS filesystem on dev sda4 [ 570.554296] EXT4-fs (sda4): unable to read superblock [ 570.557647] EXT4-fs (sda4): unable to read superblock [ 570.560516] EXT4-fs (sda4): unable to read superblock [ 570.563451] FAT-fs (sda4): bogus number of reserved sectors [ 570.563460] FAT-fs (sda4): Can't find a valid FAT filesystem [ 570.574953] XFS (sda4): Invalid superblock magic number [ 570.580796] FAT-fs (sda4): bogus number of reserved sectors [ 570.580806] FAT-fs (sda4): Can't find a valid FAT filesystem [ 570.588340] MINIX-fs: unable to read superblock [ 570.590983] attempt to access beyond end of device [ 570.590993] sda4: rw=16, want=3, limit=2 [ 570.590999] hfsplus: unable to find HFS+ superblock [ 570.593321] qnx4: no qnx4 filesystem (no root dir). [ 570.595556] You didn't specify the type of your ufs filesystem mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep |nextstep-cd|openstep ... >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old [ 570.597775] hfs: can't find a HFS filesystem on dev sda4 [ 576.795014] EXT4-fs (sda4): unable to read superblock [ 576.797554] EXT4-fs (sda4): unable to read superblock [ 576.800063] EXT4-fs (sda4): unable to read superblock [ 576.802647] FAT-fs (sda4): bogus number of reserved sectors [ 576.802655] FAT-fs (sda4): Can't find a valid FAT filesystem [ 576.813305] XFS (sda4): Invalid superblock magic number [ 576.820257] FAT-fs (sda4): bogus number of reserved sectors [ 576.820276] FAT-fs (sda4): Can't find a valid FAT filesystem [ 576.830945] MINIX-fs: unable to read superblock [ 576.834108] attempt to access beyond end of device [ 576.834119] sda4: rw=16, want=3, limit=2 [ 576.834125] hfsplus: unable to find HFS+ superblock [ 576.837264] qnx4: no qnx4 filesystem (no root dir). [ 576.840408] You didn't specify the type of your ufs filesystem
[Touch-packages] [Bug 1545942] Re: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume()
*** This bug is a duplicate of bug 1539209 *** https://bugs.launchpad.net/bugs/1539209 https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1065812 The emulated ac97 codec was used in dell dimension 8400 0-0/0: Analog Devices AD1980 PCI Subsys Vendor: 0x1028 PCI Subsys Device: 0x0177 -- 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/1545942 Title: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() Status in pulseaudio package in Ubuntu: New Bug description: ? ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-5.20-generic 4.4.1 Uname: Linux 4.4.0-5-generic i686 ApportVersion: 2.20-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: halo 3047 F pulseaudio CurrentDesktop: Unity Date: Tue Feb 16 12:12:44 2016 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2016-02-16 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha i386 (20160215) ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog Signal: 6 SourcePackage: pulseaudio StacktraceTop: pa_alsa_path_set_volume () from /usr/lib/pulse-8.0/modules/libalsa-util.so ?? () from /usr/lib/pulse-8.0/modules/libalsa-util.so pa_source_process_msg () from /usr/lib/i386-linux-gnu/pulseaudio/libpulsecore-8.0.so ?? () from /usr/lib/pulse-8.0/modules/libalsa-util.so ?? () from /usr/lib/i386-linux-gnu/pulseaudio/libpulsecore-8.0.so Title: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1545942/+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 1545942] Re: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume()
*** This bug is a duplicate of bug 1539209 *** https://bugs.launchpad.net/bugs/1539209 It seem bug of virtual box 5.0 in emulated three ac97 codecs on ich 80281ab controller which does not support multi channel /codecs 0-0/0: Analog Devices AD1980 PCI Subsys Vendor: 0x1028 PCI Subsys Device: 0x0177 Flags: 12 Revision : 0x00 Compat. Class : 0x00 Subsys. Vendor ID: 0x Subsys. ID : 0x Capabilities : -headphone out- DAC resolution : 16-bit ADC resolution : 16-bit 3D enhancement : No 3D Stereo Enhancement 0-0/1: Analog Devices AD1980 PCI Subsys Vendor: 0x1028 PCI Subsys Device: 0x0177 Flags: 12 Revision : 0x00 Compat. Class : 0x00 Subsys. Vendor ID: 0x Subsys. ID : 0x Capabilities : -headphone out- DAC resolution : 16-bit ADC resolution : 16-bit 3D enhancement : No 3D Stereo Enhancement 0-0/2: Analog Devices AD1980 -- 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/1545942 Title: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() Status in pulseaudio package in Ubuntu: New Bug description: ? ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-5.20-generic 4.4.1 Uname: Linux 4.4.0-5-generic i686 ApportVersion: 2.20-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: halo 3047 F pulseaudio CurrentDesktop: Unity Date: Tue Feb 16 12:12:44 2016 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2016-02-16 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha i386 (20160215) ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog Signal: 6 SourcePackage: pulseaudio StacktraceTop: pa_alsa_path_set_volume () from /usr/lib/pulse-8.0/modules/libalsa-util.so ?? () from /usr/lib/pulse-8.0/modules/libalsa-util.so pa_source_process_msg () from /usr/lib/i386-linux-gnu/pulseaudio/libpulsecore-8.0.so ?? () from /usr/lib/pulse-8.0/modules/libalsa-util.so ?? () from /usr/lib/i386-linux-gnu/pulseaudio/libpulsecore-8.0.so Title: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1545942/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1551976] Re: Headphones not activated after unplugging/plugging-in
Puzzled... Was this instruction for me to do something??? On Wed, Mar 2, 2016 at 12:51 AM, Raymond <1551...@bugs.launchpad.net> wrote: > ports: analog-input-front-mic: Front Microphone (priority 8500, latency > offset 0 usec, available: no) properties: device.icon_name = "audio- > input-microphone" analog-input-rear-mic: Rear Microphone (priority 8200, > latency offset 0 usec, available: no) properties: device.icon_name = > "audio-input-microphone" analog-input-linein: Line In (priority 8100, > latency offset 0 usec, available: no) properties: analog-output-lineout: > Line Out (priority 9900, latency offset 0 usec, available: no) > properties: analog-output-headphones: Headphones (priority 9000, latency > offset 0 usec, available: yes) properties: device.icon_name = "audio- > headphones" iec958-stereo-output: Digital Output (S/PDIF) (priority 0, > latency offset 0 usec, available: unknown) properties: > > Seem no line out plugged, do pulseaudio switch to digial after headphone > is unplugged > > ** Changed in: alsa-driver (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1551976 > > Title: > Headphones not activated after unplugging/plugging-in > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1551976/+subscriptions > -- 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/1551976 Title: Headphones not activated after unplugging/plugging-in Status in alsa-driver package in Ubuntu: Incomplete Bug description: Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 Expected behavior: Sound is played-back via headphones, when they are plugged-in. Observed behavior: Unplugging/plugging-in headphones disables headphones sound. To restore sound, user needs to go to sound settings, and switch "Output" to "Headphones" This is a regression from 15.10. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alexei 1692 F pulseaudio /dev/snd/controlC0: alexei 1692 F pulseaudio CurrentDesktop: Unity Date: Tue Mar 1 22:43:40 2016 InstallationDate: Installed on 2016-01-06 (54 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Green Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [To Be Filled By O.E.M., Realtek ALC892, Green Headphone Out, Front] Playback problem UpgradeStatus: Upgraded to xenial on 2016-02-24 (6 days ago) dmi.bios.date: 09/16/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: HM65-MXM dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd09/16/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM65-MXM:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1551976/+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 1552014] Re: package ntp 1:4.2.6.p5+dfsg-3ubuntu8.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1552014 Title: package ntp 1:4.2.6.p5+dfsg-3ubuntu8.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in ntp package in Ubuntu: New Bug description: error ProblemType: Package DistroRelease: Ubuntu 15.10 Package: ntp 1:4.2.6.p5+dfsg-3ubuntu8.2 ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 Date: Mon Feb 29 19:00:31 2016 DuplicateSignature: package:ntp:1:4.2.6.p5+dfsg-3ubuntu8.2:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2014-10-21 (497 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.2.0-30-generic root=UUID=f072578e-d621-4434-bbe4-383b2b5b7bbf ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.2ubuntu5.1 apt 1.0.10.2ubuntu1 SourcePackage: ntp Title: package ntp 1:4.2.6.p5+dfsg-3ubuntu8.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to wily on 2015-10-24 (129 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1552014/+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 1552014] [NEW] package ntp 1:4.2.6.p5+dfsg-3ubuntu8.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: error ProblemType: Package DistroRelease: Ubuntu 15.10 Package: ntp 1:4.2.6.p5+dfsg-3ubuntu8.2 ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 Date: Mon Feb 29 19:00:31 2016 DuplicateSignature: package:ntp:1:4.2.6.p5+dfsg-3ubuntu8.2:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2014-10-21 (497 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.2.0-30-generic root=UUID=f072578e-d621-4434-bbe4-383b2b5b7bbf ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.2ubuntu5.1 apt 1.0.10.2ubuntu1 SourcePackage: ntp Title: package ntp 1:4.2.6.p5+dfsg-3ubuntu8.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to wily on 2015-10-24 (129 days ago) ** Affects: ntp (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package wily -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1552014 Title: package ntp 1:4.2.6.p5+dfsg-3ubuntu8.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in ntp package in Ubuntu: New Bug description: error ProblemType: Package DistroRelease: Ubuntu 15.10 Package: ntp 1:4.2.6.p5+dfsg-3ubuntu8.2 ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 Date: Mon Feb 29 19:00:31 2016 DuplicateSignature: package:ntp:1:4.2.6.p5+dfsg-3ubuntu8.2:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2014-10-21 (497 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.2.0-30-generic root=UUID=f072578e-d621-4434-bbe4-383b2b5b7bbf ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.2ubuntu5.1 apt 1.0.10.2ubuntu1 SourcePackage: ntp Title: package ntp 1:4.2.6.p5+dfsg-3ubuntu8.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to wily on 2015-10-24 (129 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1552014/+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 1550706] Re: Thumbnails not working with qrc
** Changed in: thumbnailer (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to thumbnailer in Ubuntu.
https://bugs.launchpad.net/bugs/1550706
Title:
Thumbnails not working with qrc
Status in Client Developer Experience:
New
Status in thumbnailer package in Ubuntu:
New
Bug description:
The thumbnailer works only if I load images from the file system, not
from a resource file:
Image {
id: backgroundImage
anchors.fill: parent
sourceSize: Qt.size(parent.width, parent.height)
source: "image://thumbnailer/qrc:///images/menu-background.jpg"
}
The default sdk template uses qrc as template.
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-developer-experience/+bug/1550706/+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 1551998] Re: /usr/lib/arm-linux-gnueabihf/thumbnailer/thumbnailer-service:11:__gnu_cxx::new_allocator:std::allocator_traits:std::allocator_traits:std::vector:unity::thumbnailer::
** Changed in: thumbnailer (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to thumbnailer in Ubuntu. https://bugs.launchpad.net/bugs/1551998 Title: /usr/lib/arm-linux-gnueabihf/thumbnailer/thumbnailer- service:11:__gnu_cxx::new_allocator:std::allocator_traits:std::allocator_traits:std::vector:unity::thumbnailer::service::DBusInterface::queueRequest Status in thumbnailer package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding thumbnailer. This problem was most recently seen with version 2.3+16.04.20160108.2-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/8add77002771c6051716699933a723afe033683d contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thumbnailer/+bug/1551998/+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 1498129] Re: Asus Xonar U7 S/PDIF output not recognized by pulseaudio
Usb audio still not implemented ice958 control to set non audio aes bits for ac3/dts passthrough -- 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/1498129 Title: Asus Xonar U7 S/PDIF output not recognized by pulseaudio Status in alsa-driver package in Ubuntu: New Bug description: The external USB audio card Asus Xonar U7 is capable of both analog and digital output. ALSA name for the digital (S/PDIF) output is hw:1,1, and it is listed in aplay -l output, and aplay can output to it: aplay -D plughw:1,1 sample.wav. So, direct alsa sound works fine. However, pulseadio does not recognize the digital output of Xonar U7, it offers only analog output. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11.1 ProcVersionSignature: Ubuntu 3.13.0-63.103-lowlatency 3.13.11-ckt25 Uname: Linux 3.13.0-63-lowlatency i686 ApportVersion: 2.14.1-0ubuntu3.13 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: aoand 3756 F pulseaudio /dev/snd/controlC0: aoand 3756 F pulseaudio CurrentDesktop: Unity Date: Mon Sep 21 21:29:54 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2011-02-20 (1674 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007.1) SourcePackage: pulseaudio UpgradeStatus: Upgraded to trusty on 2014-05-19 (490 days ago) dmi.bios.date: 11/29/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 7WET71WW (3.21 ) dmi.board.name: 7448CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7WET71WW(3.21):bd11/29/2012:svnLENOVO:pn7448CTO:pvrThinkPadX200Tablet:rvnLENOVO:rn7448CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 7448CTO dmi.product.version: ThinkPad X200 Tablet dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1498129/+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 1551976] Re: Headphones not activated after unplugging/plugging-in
ports: analog-input-front-mic: Front Microphone (priority 8500, latency offset 0 usec, available: no) properties: device.icon_name = "audio- input-microphone" analog-input-rear-mic: Rear Microphone (priority 8200, latency offset 0 usec, available: no) properties: device.icon_name = "audio-input-microphone" analog-input-linein: Line In (priority 8100, latency offset 0 usec, available: no) properties: analog-output-lineout: Line Out (priority 9900, latency offset 0 usec, available: no) properties: analog-output-headphones: Headphones (priority 9000, latency offset 0 usec, available: yes) properties: device.icon_name = "audio- headphones" iec958-stereo-output: Digital Output (S/PDIF) (priority 0, latency offset 0 usec, available: unknown) properties: Seem no line out plugged, do pulseaudio switch to digial after headphone is unplugged ** Changed in: alsa-driver (Ubuntu) Status: New => Incomplete -- 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/1551976 Title: Headphones not activated after unplugging/plugging-in Status in alsa-driver package in Ubuntu: Incomplete Bug description: Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 Expected behavior: Sound is played-back via headphones, when they are plugged-in. Observed behavior: Unplugging/plugging-in headphones disables headphones sound. To restore sound, user needs to go to sound settings, and switch "Output" to "Headphones" This is a regression from 15.10. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alexei 1692 F pulseaudio /dev/snd/controlC0: alexei 1692 F pulseaudio CurrentDesktop: Unity Date: Tue Mar 1 22:43:40 2016 InstallationDate: Installed on 2016-01-06 (54 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Green Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [To Be Filled By O.E.M., Realtek ALC892, Green Headphone Out, Front] Playback problem UpgradeStatus: Upgraded to xenial on 2016-02-24 (6 days ago) dmi.bios.date: 09/16/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: HM65-MXM dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd09/16/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM65-MXM:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1551976/+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 1498129] Re: Asus Xonar U7 S/PDIF output not recognized by pulseaudio
Active Profile: output:analog-stereo+input:iec958-stereo Do you really change since capture device 1 not exist? -- 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/1498129 Title: Asus Xonar U7 S/PDIF output not recognized by pulseaudio Status in alsa-driver package in Ubuntu: New Bug description: The external USB audio card Asus Xonar U7 is capable of both analog and digital output. ALSA name for the digital (S/PDIF) output is hw:1,1, and it is listed in aplay -l output, and aplay can output to it: aplay -D plughw:1,1 sample.wav. So, direct alsa sound works fine. However, pulseadio does not recognize the digital output of Xonar U7, it offers only analog output. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11.1 ProcVersionSignature: Ubuntu 3.13.0-63.103-lowlatency 3.13.11-ckt25 Uname: Linux 3.13.0-63-lowlatency i686 ApportVersion: 2.14.1-0ubuntu3.13 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: aoand 3756 F pulseaudio /dev/snd/controlC0: aoand 3756 F pulseaudio CurrentDesktop: Unity Date: Mon Sep 21 21:29:54 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2011-02-20 (1674 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007.1) SourcePackage: pulseaudio UpgradeStatus: Upgraded to trusty on 2014-05-19 (490 days ago) dmi.bios.date: 11/29/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 7WET71WW (3.21 ) dmi.board.name: 7448CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7WET71WW(3.21):bd11/29/2012:svnLENOVO:pn7448CTO:pvrThinkPadX200Tablet:rvnLENOVO:rn7448CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 7448CTO dmi.product.version: ThinkPad X200 Tablet dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1498129/+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 1551998] [NEW] /usr/lib/arm-linux-gnueabihf/thumbnailer/thumbnailer-service:11:__gnu_cxx::new_allocator:std::allocator_traits:std::allocator_traits:std::vector:unity::thumbnailer
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding thumbnailer. This problem was most recently seen with version 2.3+16.04.20160108.2-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/8add77002771c6051716699933a723afe033683d contains more details. ** Affects: thumbnailer (Ubuntu) Importance: Undecided Status: New ** Tags: vivid xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to thumbnailer in Ubuntu. https://bugs.launchpad.net/bugs/1551998 Title: /usr/lib/arm-linux-gnueabihf/thumbnailer/thumbnailer- service:11:__gnu_cxx::new_allocator:std::allocator_traits:std::allocator_traits:std::vector:unity::thumbnailer::service::DBusInterface::queueRequest Status in thumbnailer package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding thumbnailer. This problem was most recently seen with version 2.3+16.04.20160108.2-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/8add77002771c6051716699933a723afe033683d contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thumbnailer/+bug/1551998/+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 1542743] Re: Bluetooth: Patch file not found ar3k/AthrBT_0x00000200.dfu
This is what Marcel said about it http://www.spinics.net/lists/linux-bluetooth/msg62584.html It does appear that that device had the Rev=00.01 as does this one https://bbs.archlinux.org/viewtopic.php?id=201646 in post 19 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1542743 Title: Bluetooth: Patch file not found ar3k/AthrBT_0x0200.dfu Status in bluez package in Ubuntu: Confirmed Bug description: Since some Versions of Linux Kernel and Ubuntu Releases this problem exists. I am now running ubuntu 16.04 prerelease and still have the same problem. Bluetooth does not work with the atheros device on msi gt 72 2qd notebook. dmesg | grep Bluetooth: [2.655360] Bluetooth: Core ver 2.21 [2.655373] Bluetooth: HCI device and connection manager initialized [2.655377] Bluetooth: HCI socket layer initialized [2.655379] Bluetooth: L2CAP socket layer initialized [2.655385] Bluetooth: SCO socket layer initialized [6.612790] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [6.612794] Bluetooth: BNEP filters: protocol multicast [6.612798] Bluetooth: BNEP socket layer initialized [9.016880] Bluetooth: Patch file not found ar3k/AthrBT_0x0200.dfu [9.016882] Bluetooth: Loading patch file failed hwinfo | grep Bluetooth: <6>[6.612790] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 <6>[6.612794] Bluetooth: BNEP filters: protocol multicast <6>[6.612798] Bluetooth: BNEP socket layer initialized <3>[9.016880] Bluetooth: Patch file not found ar3k/AthrBT_0x0200.dfu <3>[9.016882] Bluetooth: Loading patch file failed 60: USB 00.0: 11500 Bluetooth Device Model: "Atheros AR3012 Bluetooth 4.0" Device: usb 0x3004 "AR3012 Bluetooth 4.0" ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: bluez 5.36-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 Date: Sun Feb 7 00:38:04 2016 ExecutablePath: /usr/lib/bluetooth/bluetoothd InstallationDate: Installed on 2015-10-24 (105 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) InterestingModules: bnep btusb bluetooth MachineType: Micro-Star International Co., Ltd. GT72 2QD ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic root=UUID=f7880b23-39b5-423a-bdbf-62b111783450 ro quiet splash SourcePackage: bluez UpgradeStatus: Upgraded to xenial on 2016-02-02 (4 days ago) dmi.bios.date: 12/19/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1781IMS.10I dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1781 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.C dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1781IMS.10I:bd12/19/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT722QD:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1781:rvrREV0.C:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrToBeFilledByO.E.M.: dmi.product.name: GT72 2QD dmi.product.version: REV:0.C dmi.sys.vendor: Micro-Star International Co., Ltd. hciconfig: rfkill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1542743/+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 1550706] Re: Thumbnails not working with qrc
This looks doable, at least in principle, but raises a few questions.
How does the thumbnailer decide *where* in the file system to write the
file? Note that, if the file gets written somewhere where other
applications can read it, this will potentially allow application B to
see a thumbnail created by application A, provided application B knows
the path name.
How do we clean up the files that are created that way? We could do it
as soon as a thumbnail request for the file completes, but that would
mean that we write the entire file into the file system for each
thumbnail request, which is horribly expensive. It also would
effectively disable caching because inode number and modification time
are part of the lookup key into the cache.
If we don't clean up files immediately, when and how do we do it? One
way might be to have a small persistent cache on the client side that
maps qrc URLs to path names. We could then delete a temporary file when
its entry falls out of the client-side cache. (There are callback hooks
in persistent-cache-cpp that make this possible.) But it feels a bit
hacky. For example, a crash at the wrong moment can mean that we
accidentally leave a file on disk behind, so that we still would have to
add a garbage collector for the temporary files. Sizing the client-side
cache correctly is also problematic. (50 video files are very much
larger than 50 photos.)
I'm not trying to rain on the party here. But we need to have a strategy
for dealing with this before we implement something, only to find out
that it's too expensive or clunky. Part of the problem seems to be that
the qrc files create a virtual file system, instead of having real
things in the real file system. This makes it difficult to leverage
other tools that operate on files.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to thumbnailer in Ubuntu.
https://bugs.launchpad.net/bugs/1550706
Title:
Thumbnails not working with qrc
Status in Client Developer Experience:
New
Status in thumbnailer package in Ubuntu:
New
Bug description:
The thumbnailer works only if I load images from the file system, not
from a resource file:
Image {
id: backgroundImage
anchors.fill: parent
sourceSize: Qt.size(parent.width, parent.height)
source: "image://thumbnailer/qrc:///images/menu-background.jpg"
}
The default sdk template uses qrc as template.
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-developer-experience/+bug/1550706/+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 1551960] Re: lxc-attach does not work any more with input redirection
** Changed in: lxc (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1551960
Title:
lxc-attach does not work any more with input redirection
Status in autopkgtest package in Ubuntu:
New
Status in lxc package in Ubuntu:
Fix Committed
Bug description:
LXC 2.0.0~rc{2,3,4} break autopkgtest's LXC runner. Downgrading to
2.0.0~rc1 works again. The issue is that lxc-attach stops working
properly with input redirection.
# lxc-start -n a
Until 2.0.0~rc1 I could redirect lxc-attach's stdout:
# lxc-attach -n a runlevel /dev/null |cat
N 5
But now this does not work any more:
# lxc-attach -n a runlevel
N 5
# lxc-attach -n a runlevel /dev/null
# lxc-attach -n a runlevel /dev/null | cat
#
I. e. the last two commands don't have any output at all any more.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/1551960/+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 1186662] Re: isc-dhcp-server fails to renew lease file
Has this been pushed as an update for trusty? I'm running 14.04.4 LTS and have isc-dhcp-server 4.2.4-7ubuntu12.4, and I don't see anything else available from the repos. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1186662 Title: isc-dhcp-server fails to renew lease file Status in isc-dhcp package in Ubuntu: Fix Released Status in isc-dhcp source package in Trusty: Triaged Bug description: After raring upgrade, the dhcp server fails to renew lease file when it tries to (about every hour). The syslog says: dhcpd: Can't create new lease file: Permission denied It looks like a permission problem, because # chown -R dhcpd:dhcpd /var/lib/dhcp the above command temporarily solves the issue, until dhcpd is restarted: at that time, the ownership of the directory and the lease file is set back to root:root. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1186662/+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
