[Touch-packages] [Bug 1415057] Re: UI has unwanted transitions when receiving a call
It seems we should not be setting default text for the header, but should wait until the correct state and context is known. Lets try to target this first as it seems like an easy fix. Basically don't show No Network or Emergency Calls by default, but rather show a blank header until we know the actual correct state -- 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/1415057 Title: UI has unwanted transitions when receiving a call Status in the base for Ubuntu mobile products: Confirmed Status in Ubuntu UX bugs: Triaged Status in dialer-app package in Ubuntu: New Bug description: When an incoming call is answered when the dialer app is not running I see the following: The lock screen is shown The Phone splashscreen is shown Phone in the header with a blank panel The dialer is shown with calling number in the header the dialer is shown with the contact name in the header What I expect when answering: I go straight to a page that looks like the dialer but is not enabled, or t least does not have a blank panel I go to the dialer page and see the calling contact name on the active call After the call is hungup and the phone is locked, unlock the phone with the dialer app as the active app The dialer panel is seen with the header Emergency callsthen changes to ATT Similar poor transitions are seen when going form a voicemail or missed call notification. In this case I often see No net prior to seeing ATT The experience is better when the app has been run, but we still see the lock screen. It seems we should not be setting default text for the header, but should wait until the correct state and context is known. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1415057/+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 1426307] Re: location is inaccurate
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: location-service (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1426307 Title: location is inaccurate Status in the base for Ubuntu mobile products: Confirmed Status in location-service package in Ubuntu: Confirmed Bug description: current build number: 122 device name: krillin channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/vivid-proposed last update: 2015-02-25 15:06:29 version version: 122 version ubuntu: 20150225 version device: 20150210-95b6a9f version custom: 20150225 Location is inaccurate, it thinks that I'm several kilometres away from my actual location, in the middle of the sea. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: ubuntu-location-service-bin 2.1+15.04.20150126.1-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.16.1-0ubuntu2 Architecture: armhf Date: Fri Feb 27 11:10:42 2015 InstallationDate: Installed on 2015-02-25 (2 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20150225-020204) SourcePackage: location-service UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.init.ubuntu.location.service.conf: 2015-02-10T21:38:59 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1426307/+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 1434151] Re: [system-settings] the user should not need to sign into Ubuntu One in order to update core apps
FWIW these apps are updated via the image update process so in a sense it is already the case that a U1 account is not required. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-download-manager in Ubuntu. https://bugs.launchpad.net/bugs/1434151 Title: [system-settings] the user should not need to sign into Ubuntu One in order to update core apps Status in Ubuntu UX bugs: Triaged Status in ubuntu-download-manager package in Ubuntu: New Status in ubuntu-system-settings package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: Apps that come pre-installed with Ubuntu Touch should not require the user to create an UbuntuOne account in order to receive updates to those apps. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1434151/+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 1072206] Re: [nvidia] Window content is black or transparent
** Changed in: compiz (Ubuntu Trusty) Status: New = In Progress ** Changed in: compiz (Ubuntu Trusty) Importance: Undecided = High ** Changed in: compiz (Ubuntu Trusty) Assignee: (unassigned) = Stephen M. Webb (bregma) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1072206 Title: [nvidia] Window content is black or transparent Status in Compiz: Fix Committed Status in Compiz 0.9.11 series: In Progress Status in NVIDIA Drivers Ubuntu: Invalid Status in Unity: Invalid Status in compiz package in Ubuntu: Fix Released Status in unity package in Ubuntu: Invalid Status in compiz source package in Trusty: In Progress Bug description: [ Impact ] With nVidia hardware from time to time window content is rendered black or transparent. The problem manifests more frequently as session uptime increases. Apparently the problem was caused by textures being cached and not freed, resulting in memory exhaustion conditions. It turns out the texture caching is unnecessary anyway. [ Test Case ] Verification requires an nVidia GPU with proprietary drivers. The problem can not be reproduced at will, only after some time (depending on resident GPU memory and usage) and even then only randomly and unreliably. [ Regression Potential ] It is unlikely this change has the potential to introduce new regressions. [ Other Info ] Fix was cherry-picked from the Ubuntu Vivid Vervet dev relase where it has been in use for some weeks without problem. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1072206/+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 1419001] Re: Reminders trigger at the time of the event and not before by default
** Changed in: qtorganizer5-eds (Ubuntu) Assignee: (unassigned) = Renato Araujo Oliveira Filho (renatofilho) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtorganizer5-eds in Ubuntu. https://bugs.launchpad.net/bugs/1419001 Title: Reminders trigger at the time of the event and not before by default Status in the base for Ubuntu mobile products: Confirmed Status in Calendar application for Ubuntu devices: New Status in qtorganizer5-eds package in Ubuntu: New Bug description: Sync of google calendar. The Google calendar setting is set by default to notify 10 min prior to all meetings. Is it possible to get this default notification time from google with the sync? or can we add a setting for a default notification time in the calendar app? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1419001/+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 1435324] [NEW] qtbase5-dev not installable on Ubuntu 14.04 LTS
Public bug reported: I discovered the problem when I tried to compile a Qt5 QML program firstly. I have an Ubuntu 14.04.2 LTS with all updates, no significant PPAs (only nodejs and owncloud, not affecting this problem here) and with all the -lts-utopic upgrade packages installed. With that system, I tried to install qtbase5-dev, and apt told me: [...] The following packages have unmet dependencies: qtbase5-dev : Depends: libgles2-mesa-dev or libgles2-dev but it is not installable unity-control-center : Depends: libcheese-gtk23 (= 3.4.0) but it is not going to be installed Depends: libcheese7 (= 3.0.1) but it is not going to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. So this package seems to be not installable. This tried in synaptic, it tries to uninstall all -lts-utopic packages (inclusive all xserver*.deb) and install the old ones instead of them. So the problem somewhere lies within the new lts packages that seem not to be compatible with qtbase5-dev (and its dependency: libgles2-mesa-dev - but I am not able to find out further. The problem is: Qt5 development on an Ubuntu 14.04.2 LTS machine is NOT possible without a fix. The make process always complains about not finding gl libraries. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: qtbase5-dev (not installed) ProcVersionSignature: Ubuntu 3.16.0-31.43~14.04.1-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 23 14:01:20 2015 InstallationDate: Installed on 2015-02-25 (26 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) SourcePackage: qtbase-opensource-src UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: qtbase-opensource-src (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1435324 Title: qtbase5-dev not installable on Ubuntu 14.04 LTS Status in qtbase-opensource-src package in Ubuntu: New Bug description: I discovered the problem when I tried to compile a Qt5 QML program firstly. I have an Ubuntu 14.04.2 LTS with all updates, no significant PPAs (only nodejs and owncloud, not affecting this problem here) and with all the -lts-utopic upgrade packages installed. With that system, I tried to install qtbase5-dev, and apt told me: [...] The following packages have unmet dependencies: qtbase5-dev : Depends: libgles2-mesa-dev or libgles2-dev but it is not installable unity-control-center : Depends: libcheese-gtk23 (= 3.4.0) but it is not going to be installed Depends: libcheese7 (= 3.0.1) but it is not going to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. So this package seems to be not installable. This tried in synaptic, it tries to uninstall all -lts-utopic packages (inclusive all xserver*.deb) and install the old ones instead of them. So the problem somewhere lies within the new lts packages that seem not to be compatible with qtbase5-dev (and its dependency: libgles2 -mesa-dev - but I am not able to find out further. The problem is: Qt5 development on an Ubuntu 14.04.2 LTS machine is NOT possible without a fix. The make process always complains about not finding gl libraries. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: qtbase5-dev (not installed) ProcVersionSignature: Ubuntu 3.16.0-31.43~14.04.1-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 23 14:01:20 2015 InstallationDate: Installed on 2015-02-25 (26 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) SourcePackage: qtbase-opensource-src UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1435324/+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 33394] Re: ubuntu-minimal should depend on system-log-daemon
I think there are other means to communicate the supportedness of packages, like the Supported field in the control file. We do have reports of the same effect, that installing syslog-ng is a hassle, just because of the this dependency, like: https://bugs.launchpad.net/ubuntu/+source/syslog-ng/+bug/1242173 Can you pls fix this in one way or the other? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/33394 Title: ubuntu-minimal should depend on system-log-daemon Status in ubuntu-meta package in Ubuntu: Triaged Bug description: The current deps make installing syslog-ng remove ubuntu-minimal. If ubuntu-minimal were to depend on: sysklogd | system-log-daemon then one could install syslog-ng without removing ubuntu-minimal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/33394/+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 1101825] Re: IPv6 static default route added incorrectly by network-manager
I too am seeing this bug but with a slightly different use-case. If a user swaps out their default router, no IPv6 traffic will pass because of the static route installed. I have to disconnect the interface in Ubuntu and then reconnect to clear the static. At that point, the new default-route learnt via RA's takes over. It would be really great to get this one fixed. As IPv6 deployment starts to ramp up it is going to affect more and more people. Thanks, Nick -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1101825 Title: IPv6 static default route added incorrectly by network-manager Status in NetworkManager: Fix Released Status in network-manager package in Ubuntu: Confirmed Bug description: The relevant part of the IPv6 routing table looks like this: fe80::/64 dev wlan0 proto kernel metric 256 default via fe80::5054:ff:fe64:aad0 dev wlan0 proto static metric 1 default via fe80::5054:ff:fe9c:741e dev wlan0 proto kernel metric 1024 expires 8sec default via fe80::5054:ff:fe64:aad0 dev wlan0 proto kernel metric 1024 expires 10sec I believe the proto static metric 1 route is an error, since it persists even when the router stops advertising. This breaks the IPv6 architecture for router redundancy. I am in control of this network and can alter router advertisement parameters if needed. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: network-manager 0.9.6.0-0ubuntu7 ProcVersionSignature: Ubuntu 3.5.0-22.34-generic 3.5.7.2 Uname: Linux 3.5.0-22-generic x86_64 ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Sat Jan 19 10:47:05 2013 InstallationDate: Installed on 2012-11-15 (65 days ago) InstallationMedia: Ubuntu-Server 12.10 Quantal Quetzal - Release amd64 (20121017.2) IpRoute: default via 192.168.4.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.4.0/24 dev wlan0 proto kernel scope link src 192.168.4.64 metric 9 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: Jan 19 10:17:54 pippin wpa_supplicant[1009]: wlan0: WPA: Group rekeying completed with 00:24:a5:f1:08:8e [GTK=CCMP] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2012-11-25T12:30:38.408468 nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.6.0connected enabled enabled enabledenabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1101825/+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 1412758] Re: mirror method should with with file location
Where is the advantage? It's easy enough to host a file these days and without a net connection the whole update business isn't going to work. Not sure if this would be a lot of work to implement. But before anybody goes ahead and thinks about doing that let's make sure this is worth the effort. Please make your case. ** Changed in: apt (Ubuntu) Status: New = Incomplete ** Changed in: apt (Ubuntu) Assignee: (unassigned) = Rolf Leggewie (r0lf) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1412758 Title: mirror method should with with file location Status in apt package in Ubuntu: Incomplete Bug description: It'd be really great if the mirror method could be configured to use a local file for the mirror list. eg in /etc/apt/source.list.d/mysoftware.list deb mirror://file://apt/mirrors/mysoftware.txt trusty main Instead of pulling the file via http (as per current behaviour) and choosing a mirror from that list, apt should read the local file and choose from the list in the same way. Description: Ubuntu 14.04.1 LTS Release: 14.04 apt: Installed: 1.0.1ubuntu2.6 Candidate: 1.0.1ubuntu2.6 Version table: *** 1.0.1ubuntu2.6 0 500 http://mirror.rackspace.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.0.1ubuntu2.5 0 500 http://mirror.rackspace.com/ubuntu/ trusty-security/main amd64 Packages 1.0.1ubuntu2 0 500 http://mirror.rackspace.com/ubuntu/ trusty/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1412758/+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 1435269] [NEW] System does not suspend when lid closed
Public bug reported: Under Utopic closing the laptop lid would suspend the system. Since a Vivid upgrade this no longer happens (the external screen goes blank for about a second, then the desktop comes back as before) The system power settings show When lid is closed: suspend as before, it just gets ignored. The menu suspend option does suspend correctly. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-4ubuntu8 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 23 10:49:19 2015 InstallationDate: Installed on 2014-11-29 (113 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: LENOVO 20344 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-9-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/09/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 96CN25WW(V1.11) dmi.board.asset.tag: 31900058WIN dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 31900058WIN dmi.chassis.asset.tag: 31900058WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 13 dmi.modalias: dmi:bvnLENOVO:bvr96CN25WW(V1.11):bd07/09/2014:svnLENOVO:pn20344:pvrLenovoYoga213:rvnLENOVO:rnINVALID:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga213: dmi.product.name: 20344 dmi.product.version: Lenovo Yoga 2 13 dmi.sys.vendor: LENOVO ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- 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/1435269 Title: System does not suspend when lid closed Status in systemd package in Ubuntu: New Bug description: Under Utopic closing the laptop lid would suspend the system. Since a Vivid upgrade this no longer happens (the external screen goes blank for about a second, then the desktop comes back as before) The system power settings show When lid is closed: suspend as before, it just gets ignored. The menu suspend option does suspend correctly. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-4ubuntu8 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 23 10:49:19 2015 InstallationDate: Installed on 2014-11-29 (113 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: LENOVO 20344 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-9-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/09/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 96CN25WW(V1.11) dmi.board.asset.tag: 31900058WIN dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 31900058WIN dmi.chassis.asset.tag: 31900058WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 13 dmi.modalias: dmi:bvnLENOVO:bvr96CN25WW(V1.11):bd07/09/2014:svnLENOVO:pn20344:pvrLenovoYoga213:rvnLENOVO:rnINVALID:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga213: dmi.product.name: 20344 dmi.product.version: Lenovo Yoga 2 13 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1435269/+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 1406804] UdevDb.txt
apport information ** Attachment added: UdevDb.txt https://bugs.launchpad.net/bugs/1406804/+attachment/4353320/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1406804 Title: Freezes when update to release 14.04 LTS Status in xorg package in Ubuntu: Incomplete Bug description: When updated to release 14.04 LTS something is not working properly, the PC freezes after login and after a few minutes the screen shows crazy colors. I tried it a lot of times, downloading the iso file a few times to check if anything got corrupted. I had to reinstall release 12.04 LTS back. Last note, release 14 freezes even when I lounch live CD, not only installing. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: update-manager 1:0.156.14.17 ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Wed Dec 31 17:31:37 2014 GsettingsChanges: com.ubuntu.update-manager check-new-release-ignore 'trusty' com.ubuntu.update-manager first-run false com.ubuntu.update-manager launch-time 1420053951 InstallationMedia: Ubuntu 12.04.5 LTS Precise Pangolin - Release amd64 (20140807.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: update-manager Symptom: ubuntu-release-upgrader-core UpgradeStatus: No upgrade log present (probably fresh install) --- .proc.driver.nvidia.gpus.0: Error: [Errno 21] É um diretório: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.125 Mon Dec 1 19:58:28 PST 2014 GCC version: versão do gcc 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu17.8 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CurrentDmesg: [ 11.405490] forcedeth :00:07.0 eth0: MSI enabled [ 50.030311] audit_printk_skb: 171 callbacks suppressed [ 50.030316] type=1400 audit(1427111674.315:69): apparmor=DENIED operation=open profile=/usr/lib/telepathy/mission-control-5 name=/usr/share/gvfs/remote-volume-monitors/ pid=2150 comm=mission-control requested_mask=r denied_mask=r fsuid=1000 ouid=0 DistUpgraded: Fresh install DistroCodename: precise DistroRelease: Ubuntu 12.04 DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.125, 3.13.0-32-generic, x86_64: installed nvidia-304, 304.125, 3.13.0-43-generic, x86_64: installed nvidia-304, 304.125, 3.13.0-45-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:83a4] InstallationMedia: Ubuntu 12.04.5 LTS Precise Pangolin - Release amd64 (20140807.1) JockeyStatus: xorg:nvidia_304 - Driver de aceleração de vídeo NVIDIA (Proprietário, Habilitado, Em uso) xorg:nvidia_304_updates - Driver gráfico de aceleração NVIDIA (atualizações pós instalação) (Proprietário, Desativado, Não está em uso) Lsusb: Bus 002 Device 003: ID 1c4f:0003 SiGma Micro HID controller 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: System manufacturer System Product Name MarkForUpload: True NonfreeKernelModules: nvidia Package: xorg 1:7.6+12ubuntu2 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=pt_BR:pt:en TERM=xterm PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic root=UUID=07b50d8a-8bbe-4ec1-a9ea-5293a74a135f ro quiet splash ProcVersionSignature: Ubuntu 3.13.0-45.74~precise1-generic 3.13.11-ckt13 Tags: precise running-unity ubuntu referred-by-support compiz-0.9 Uname: Linux 3.13.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo XorgConf: Section Device Identifier Default Device Option NoLogoTrue EndSection dmi.bios.date: 09/22/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M2N68-AM SE2 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type:
[Touch-packages] [Bug 1406804] nvidia-bug-report.log.gz
apport information ** Attachment added: nvidia-bug-report.log.gz https://bugs.launchpad.net/bugs/1406804/+attachment/4353326/+files/nvidia-bug-report.log.gz -- 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/1406804 Title: Freezes when update to release 14.04 LTS Status in xorg package in Ubuntu: Incomplete Bug description: When updated to release 14.04 LTS something is not working properly, the PC freezes after login and after a few minutes the screen shows crazy colors. I tried it a lot of times, downloading the iso file a few times to check if anything got corrupted. I had to reinstall release 12.04 LTS back. Last note, release 14 freezes even when I lounch live CD, not only installing. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: update-manager 1:0.156.14.17 ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Wed Dec 31 17:31:37 2014 GsettingsChanges: com.ubuntu.update-manager check-new-release-ignore 'trusty' com.ubuntu.update-manager first-run false com.ubuntu.update-manager launch-time 1420053951 InstallationMedia: Ubuntu 12.04.5 LTS Precise Pangolin - Release amd64 (20140807.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: update-manager Symptom: ubuntu-release-upgrader-core UpgradeStatus: No upgrade log present (probably fresh install) --- .proc.driver.nvidia.gpus.0: Error: [Errno 21] É um diretório: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.125 Mon Dec 1 19:58:28 PST 2014 GCC version: versão do gcc 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu17.8 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CurrentDmesg: [ 11.405490] forcedeth :00:07.0 eth0: MSI enabled [ 50.030311] audit_printk_skb: 171 callbacks suppressed [ 50.030316] type=1400 audit(1427111674.315:69): apparmor=DENIED operation=open profile=/usr/lib/telepathy/mission-control-5 name=/usr/share/gvfs/remote-volume-monitors/ pid=2150 comm=mission-control requested_mask=r denied_mask=r fsuid=1000 ouid=0 DistUpgraded: Fresh install DistroCodename: precise DistroRelease: Ubuntu 12.04 DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.125, 3.13.0-32-generic, x86_64: installed nvidia-304, 304.125, 3.13.0-43-generic, x86_64: installed nvidia-304, 304.125, 3.13.0-45-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:83a4] InstallationMedia: Ubuntu 12.04.5 LTS Precise Pangolin - Release amd64 (20140807.1) JockeyStatus: xorg:nvidia_304 - Driver de aceleração de vídeo NVIDIA (Proprietário, Habilitado, Em uso) xorg:nvidia_304_updates - Driver gráfico de aceleração NVIDIA (atualizações pós instalação) (Proprietário, Desativado, Não está em uso) Lsusb: Bus 002 Device 003: ID 1c4f:0003 SiGma Micro HID controller 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: System manufacturer System Product Name MarkForUpload: True NonfreeKernelModules: nvidia Package: xorg 1:7.6+12ubuntu2 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=pt_BR:pt:en TERM=xterm PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic root=UUID=07b50d8a-8bbe-4ec1-a9ea-5293a74a135f ro quiet splash ProcVersionSignature: Ubuntu 3.13.0-45.74~precise1-generic 3.13.11-ckt13 Tags: precise running-unity ubuntu referred-by-support compiz-0.9 Uname: Linux 3.13.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo XorgConf: Section Device Identifier Default Device Option NoLogoTrue EndSection dmi.bios.date: 09/22/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M2N68-AM SE2 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag:
[Touch-packages] [Bug 1186026] Re: Scrolling over the sound icon closes the dash
On 14.04, scrolling over the sound indicator does not close the Dash. Based on the bug description's expected behavior, I say this is fixed. Whether or not if the Dash should close when clicking on indicators should be discussed in a different bug report. Closing Fix Released. ** Changed in: unity Assignee: Brandon Schaefer (brandontschaefer) = (unassigned) ** No longer affects: unity/7.2 ** Changed in: unity (Ubuntu) Assignee: Brandon Schaefer (brandontschaefer) = (unassigned) ** Changed in: unity Status: Triaged = Fix Released ** Changed in: unity (Ubuntu) Status: Triaged = Fix Released ** Changed in: unity Milestone: 7.3.3 = None -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1186026 Title: Scrolling over the sound icon closes the dash Status in Unity: Fix Released Status in unity package in Ubuntu: Fix Released Bug description: 1. open the dash 2. move the mouse of to the indicators area 3. scroll What happens: The dash closes What should happen: The dash should not close. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 7.0.0daily13.04.18~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11 Uname: Linux 3.8.0-22-generic i686 NonfreeKernelModules: wl ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Fri May 31 02:27:56 2013 InstallationDate: Installed on 2013-05-29 (1 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424) MarkForUpload: True SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1186026/+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 1406804] ProcModules.txt
apport information ** Attachment added: ProcModules.txt https://bugs.launchpad.net/bugs/1406804/+attachment/4353319/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1406804 Title: Freezes when update to release 14.04 LTS Status in xorg package in Ubuntu: Incomplete Bug description: When updated to release 14.04 LTS something is not working properly, the PC freezes after login and after a few minutes the screen shows crazy colors. I tried it a lot of times, downloading the iso file a few times to check if anything got corrupted. I had to reinstall release 12.04 LTS back. Last note, release 14 freezes even when I lounch live CD, not only installing. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: update-manager 1:0.156.14.17 ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Wed Dec 31 17:31:37 2014 GsettingsChanges: com.ubuntu.update-manager check-new-release-ignore 'trusty' com.ubuntu.update-manager first-run false com.ubuntu.update-manager launch-time 1420053951 InstallationMedia: Ubuntu 12.04.5 LTS Precise Pangolin - Release amd64 (20140807.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: update-manager Symptom: ubuntu-release-upgrader-core UpgradeStatus: No upgrade log present (probably fresh install) --- .proc.driver.nvidia.gpus.0: Error: [Errno 21] É um diretório: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.125 Mon Dec 1 19:58:28 PST 2014 GCC version: versão do gcc 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu17.8 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CurrentDmesg: [ 11.405490] forcedeth :00:07.0 eth0: MSI enabled [ 50.030311] audit_printk_skb: 171 callbacks suppressed [ 50.030316] type=1400 audit(1427111674.315:69): apparmor=DENIED operation=open profile=/usr/lib/telepathy/mission-control-5 name=/usr/share/gvfs/remote-volume-monitors/ pid=2150 comm=mission-control requested_mask=r denied_mask=r fsuid=1000 ouid=0 DistUpgraded: Fresh install DistroCodename: precise DistroRelease: Ubuntu 12.04 DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.125, 3.13.0-32-generic, x86_64: installed nvidia-304, 304.125, 3.13.0-43-generic, x86_64: installed nvidia-304, 304.125, 3.13.0-45-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:83a4] InstallationMedia: Ubuntu 12.04.5 LTS Precise Pangolin - Release amd64 (20140807.1) JockeyStatus: xorg:nvidia_304 - Driver de aceleração de vídeo NVIDIA (Proprietário, Habilitado, Em uso) xorg:nvidia_304_updates - Driver gráfico de aceleração NVIDIA (atualizações pós instalação) (Proprietário, Desativado, Não está em uso) Lsusb: Bus 002 Device 003: ID 1c4f:0003 SiGma Micro HID controller 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: System manufacturer System Product Name MarkForUpload: True NonfreeKernelModules: nvidia Package: xorg 1:7.6+12ubuntu2 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=pt_BR:pt:en TERM=xterm PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic root=UUID=07b50d8a-8bbe-4ec1-a9ea-5293a74a135f ro quiet splash ProcVersionSignature: Ubuntu 3.13.0-45.74~precise1-generic 3.13.11-ckt13 Tags: precise running-unity ubuntu referred-by-support compiz-0.9 Uname: Linux 3.13.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo XorgConf: Section Device Identifier Default Device Option NoLogoTrue EndSection dmi.bios.date: 09/22/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M2N68-AM SE2 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890
[Touch-packages] [Bug 1406804] UdevLog.txt
apport information ** Attachment added: UdevLog.txt https://bugs.launchpad.net/bugs/1406804/+attachment/4353321/+files/UdevLog.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1406804 Title: Freezes when update to release 14.04 LTS Status in xorg package in Ubuntu: Incomplete Bug description: When updated to release 14.04 LTS something is not working properly, the PC freezes after login and after a few minutes the screen shows crazy colors. I tried it a lot of times, downloading the iso file a few times to check if anything got corrupted. I had to reinstall release 12.04 LTS back. Last note, release 14 freezes even when I lounch live CD, not only installing. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: update-manager 1:0.156.14.17 ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Wed Dec 31 17:31:37 2014 GsettingsChanges: com.ubuntu.update-manager check-new-release-ignore 'trusty' com.ubuntu.update-manager first-run false com.ubuntu.update-manager launch-time 1420053951 InstallationMedia: Ubuntu 12.04.5 LTS Precise Pangolin - Release amd64 (20140807.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: update-manager Symptom: ubuntu-release-upgrader-core UpgradeStatus: No upgrade log present (probably fresh install) --- .proc.driver.nvidia.gpus.0: Error: [Errno 21] É um diretório: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.125 Mon Dec 1 19:58:28 PST 2014 GCC version: versão do gcc 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu17.8 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CurrentDmesg: [ 11.405490] forcedeth :00:07.0 eth0: MSI enabled [ 50.030311] audit_printk_skb: 171 callbacks suppressed [ 50.030316] type=1400 audit(1427111674.315:69): apparmor=DENIED operation=open profile=/usr/lib/telepathy/mission-control-5 name=/usr/share/gvfs/remote-volume-monitors/ pid=2150 comm=mission-control requested_mask=r denied_mask=r fsuid=1000 ouid=0 DistUpgraded: Fresh install DistroCodename: precise DistroRelease: Ubuntu 12.04 DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.125, 3.13.0-32-generic, x86_64: installed nvidia-304, 304.125, 3.13.0-43-generic, x86_64: installed nvidia-304, 304.125, 3.13.0-45-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:83a4] InstallationMedia: Ubuntu 12.04.5 LTS Precise Pangolin - Release amd64 (20140807.1) JockeyStatus: xorg:nvidia_304 - Driver de aceleração de vídeo NVIDIA (Proprietário, Habilitado, Em uso) xorg:nvidia_304_updates - Driver gráfico de aceleração NVIDIA (atualizações pós instalação) (Proprietário, Desativado, Não está em uso) Lsusb: Bus 002 Device 003: ID 1c4f:0003 SiGma Micro HID controller 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: System manufacturer System Product Name MarkForUpload: True NonfreeKernelModules: nvidia Package: xorg 1:7.6+12ubuntu2 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=pt_BR:pt:en TERM=xterm PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic root=UUID=07b50d8a-8bbe-4ec1-a9ea-5293a74a135f ro quiet splash ProcVersionSignature: Ubuntu 3.13.0-45.74~precise1-generic 3.13.11-ckt13 Tags: precise running-unity ubuntu referred-by-support compiz-0.9 Uname: Linux 3.13.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo XorgConf: Section Device Identifier Default Device Option NoLogoTrue EndSection dmi.bios.date: 09/22/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M2N68-AM SE2 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890
[Touch-packages] [Bug 1435311] [NEW] fcitx (the framework) should be seeded in desktop
Public bug reported: As a result of bug #1430893, check-language-support now pulls fcitx IM support for Chinese instead of IBus ditto. However, this is true only if the fcitx package is installed. Consider these steps: * Plain English install - fcitx not installed * Install a Chinese language using Language Support, and find that 1. No IM support gets installed and 2. fcitx is not available as an IM framework option. I think it would make more sense to have the fcitx package installed for all users. ** Affects: ubuntu-meta (Ubuntu) Importance: High Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1435311 Title: fcitx (the framework) should be seeded in desktop Status in ubuntu-meta package in Ubuntu: New Bug description: As a result of bug #1430893, check-language-support now pulls fcitx IM support for Chinese instead of IBus ditto. However, this is true only if the fcitx package is installed. Consider these steps: * Plain English install - fcitx not installed * Install a Chinese language using Language Support, and find that 1. No IM support gets installed and 2. fcitx is not available as an IM framework option. I think it would make more sense to have the fcitx package installed for all users. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1435311/+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 1425991] Re: Networks I have never connected to should be confined to the More Networks folder
Greg, thanks for your suggestion. However, as Shahbaz points out, most of the time, Ubuntu will connect automatically to one of the networks you have connected to before. So most of the time, if you open the menu to connect to a Wi-Fi network, it is to connect to a network that you have *not* connected to before. It would be counterproductive, then, to show by default only networks that you *have* connected to before. Where you have previously connected to more than one of the networks in range, the menu prioritizes showing these ones, ahead of showing networks that you have not connected to before. After that, it prioritizes the strongest other networks, minimizing the probability that the network you want isn't at the top level. https://wiki.ubuntu.com/Networking#wi-fi-menu Shahbaz's proposal eliminates the problem of interleaving known with unknown networks. However, the reverse can also be a problem -- for example, you may not remember whether you used the Wi-Fi the last time you were at this particular cafe/airport/etc, so you may not remember whether the network is known or not. And having two lists of networks, separated by other functional items, would be rather inelegant. Part of adapting the phone Wi-Fi settings to the PC will, I hope, be introducing the ability to arrange previous networks in order of preference. Once that is done, I don't think there will be any point in also letting you confine/blacklist networks. ** Changed in: indicator-network (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1425991 Title: Networks I have never connected to should be confined to the More Networks folder Status in indicator-network package in Ubuntu: Invalid Bug description: When a user clicks the network manager indicator, a dropdown appears and lists wifi networks. This menu should NOT display networks that the user has never connected to. Networks the user has never connected to should only display in the More networks folder. At a mininum, the user should be given the ability to confine unwanted networks in the More networks folder. It is an unproductive design choice to force users to have to wade through networks they have never connected to (networks they will never connect to) in their menu. Numerous reasons exist why a user will not use the Auto-Connect setting for wireless networks. So it makes sense and is more efficient to have the menu only display the networks the user makes active use of and no more. When I click on the Network Manager Indicator and select Edit Connections and then look under the Wifi heading, only a couple networks appear. So why do 5 or more networks (networks I have never connected to, networks I never will connect to) perpetually show in the Network Indicator menu? They should not be displayed like they are. They should be confined to the More networks folder. Alternatively, there should be a way to manually confine/sandbox unwanted networks to this folder so they no longer display in the dropdown menu. In the interest of providing a visual example of what I am talking about, here is a picture of some networks I would like to hide/remove from my Network Indicator menu. http://a.pomf.se/fdqlnn.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1425991/+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 1240848] Re: ~/.cache/upstart takes up around 70GB of space due to unity and mediascanner
Hello! I'm not a Ubuntu pro user, but I'm trying to learn more and more. Yesterday, I experienced the same situation as described here. I work with molecular dynamics simulation, specifically with a program called GROMACS. When I was trying to do a simulation, the program told me it would take about 2 days to complete (weird, because the kind of simulation I had trying usually lasts about 6 hours). It only took a little time for my hard disk free space had being completely consumed (and breaking my simulation). When I used the Baobap to see the disk usage, it took me to this folder .cache/upstart occupying about 70GB! I deleted it, restarted the computer, and my simulation had functioned normally (it took 5 hours to complete), and I didn't have any problems with the .cache. Very strange bug!! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1240848 Title: ~/.cache/upstart takes up around 70GB of space due to unity and mediascanner Status in Unity: Invalid Status in mediascanner package in Ubuntu: Confirmed Status in unity package in Ubuntu: Invalid Bug description: I just noticed that ~/.cache/upstart/ folder on my computer is taking up 69GB of space. Upon further investigation, I found out that mediascanner.log and unity-panel-service.log take 12GB and 54GB of space respectively. I'm not entirely sure if this is related to upstart as I had removed logrotate package because of a conflict. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1240848/+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 1240909] Re: [performance] Restore support for double-buffering by default
** Changed in: mir/0.12 Status: Fix Committed = Won't Fix -- 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/1240909 Title: [performance] Restore support for double-buffering by default Status in Mir: Fix Committed Status in Mir 0.12 series: Won't Fix Status in Mir 0.5 series: Won't Fix Status in mir package in Ubuntu: Triaged Bug description: We really should restore support for double-buffering where possible. Presently we're on triple-buffering all the time. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1240909/+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 1406804] GconfCompiz.txt
apport information ** Attachment added: GconfCompiz.txt https://bugs.launchpad.net/bugs/1406804/+attachment/4353313/+files/GconfCompiz.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1406804 Title: Freezes when update to release 14.04 LTS Status in xorg package in Ubuntu: Incomplete Bug description: When updated to release 14.04 LTS something is not working properly, the PC freezes after login and after a few minutes the screen shows crazy colors. I tried it a lot of times, downloading the iso file a few times to check if anything got corrupted. I had to reinstall release 12.04 LTS back. Last note, release 14 freezes even when I lounch live CD, not only installing. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: update-manager 1:0.156.14.17 ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Wed Dec 31 17:31:37 2014 GsettingsChanges: com.ubuntu.update-manager check-new-release-ignore 'trusty' com.ubuntu.update-manager first-run false com.ubuntu.update-manager launch-time 1420053951 InstallationMedia: Ubuntu 12.04.5 LTS Precise Pangolin - Release amd64 (20140807.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: update-manager Symptom: ubuntu-release-upgrader-core UpgradeStatus: No upgrade log present (probably fresh install) --- .proc.driver.nvidia.gpus.0: Error: [Errno 21] É um diretório: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.125 Mon Dec 1 19:58:28 PST 2014 GCC version: versão do gcc 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu17.8 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CurrentDmesg: [ 11.405490] forcedeth :00:07.0 eth0: MSI enabled [ 50.030311] audit_printk_skb: 171 callbacks suppressed [ 50.030316] type=1400 audit(1427111674.315:69): apparmor=DENIED operation=open profile=/usr/lib/telepathy/mission-control-5 name=/usr/share/gvfs/remote-volume-monitors/ pid=2150 comm=mission-control requested_mask=r denied_mask=r fsuid=1000 ouid=0 DistUpgraded: Fresh install DistroCodename: precise DistroRelease: Ubuntu 12.04 DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.125, 3.13.0-32-generic, x86_64: installed nvidia-304, 304.125, 3.13.0-43-generic, x86_64: installed nvidia-304, 304.125, 3.13.0-45-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:83a4] InstallationMedia: Ubuntu 12.04.5 LTS Precise Pangolin - Release amd64 (20140807.1) JockeyStatus: xorg:nvidia_304 - Driver de aceleração de vídeo NVIDIA (Proprietário, Habilitado, Em uso) xorg:nvidia_304_updates - Driver gráfico de aceleração NVIDIA (atualizações pós instalação) (Proprietário, Desativado, Não está em uso) Lsusb: Bus 002 Device 003: ID 1c4f:0003 SiGma Micro HID controller 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: System manufacturer System Product Name MarkForUpload: True NonfreeKernelModules: nvidia Package: xorg 1:7.6+12ubuntu2 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=pt_BR:pt:en TERM=xterm PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic root=UUID=07b50d8a-8bbe-4ec1-a9ea-5293a74a135f ro quiet splash ProcVersionSignature: Ubuntu 3.13.0-45.74~precise1-generic 3.13.11-ckt13 Tags: precise running-unity ubuntu referred-by-support compiz-0.9 Uname: Linux 3.13.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo XorgConf: Section Device Identifier Default Device Option NoLogoTrue EndSection dmi.bios.date: 09/22/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M2N68-AM SE2 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890
[Touch-packages] [Bug 1406804] BootDmesg.txt
apport information ** Attachment added: BootDmesg.txt https://bugs.launchpad.net/bugs/1406804/+attachment/4353310/+files/BootDmesg.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1406804 Title: Freezes when update to release 14.04 LTS Status in xorg package in Ubuntu: Incomplete Bug description: When updated to release 14.04 LTS something is not working properly, the PC freezes after login and after a few minutes the screen shows crazy colors. I tried it a lot of times, downloading the iso file a few times to check if anything got corrupted. I had to reinstall release 12.04 LTS back. Last note, release 14 freezes even when I lounch live CD, not only installing. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: update-manager 1:0.156.14.17 ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Wed Dec 31 17:31:37 2014 GsettingsChanges: com.ubuntu.update-manager check-new-release-ignore 'trusty' com.ubuntu.update-manager first-run false com.ubuntu.update-manager launch-time 1420053951 InstallationMedia: Ubuntu 12.04.5 LTS Precise Pangolin - Release amd64 (20140807.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: update-manager Symptom: ubuntu-release-upgrader-core UpgradeStatus: No upgrade log present (probably fresh install) --- .proc.driver.nvidia.gpus.0: Error: [Errno 21] É um diretório: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.125 Mon Dec 1 19:58:28 PST 2014 GCC version: versão do gcc 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu17.8 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CurrentDmesg: [ 11.405490] forcedeth :00:07.0 eth0: MSI enabled [ 50.030311] audit_printk_skb: 171 callbacks suppressed [ 50.030316] type=1400 audit(1427111674.315:69): apparmor=DENIED operation=open profile=/usr/lib/telepathy/mission-control-5 name=/usr/share/gvfs/remote-volume-monitors/ pid=2150 comm=mission-control requested_mask=r denied_mask=r fsuid=1000 ouid=0 DistUpgraded: Fresh install DistroCodename: precise DistroRelease: Ubuntu 12.04 DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.125, 3.13.0-32-generic, x86_64: installed nvidia-304, 304.125, 3.13.0-43-generic, x86_64: installed nvidia-304, 304.125, 3.13.0-45-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:83a4] InstallationMedia: Ubuntu 12.04.5 LTS Precise Pangolin - Release amd64 (20140807.1) JockeyStatus: xorg:nvidia_304 - Driver de aceleração de vídeo NVIDIA (Proprietário, Habilitado, Em uso) xorg:nvidia_304_updates - Driver gráfico de aceleração NVIDIA (atualizações pós instalação) (Proprietário, Desativado, Não está em uso) Lsusb: Bus 002 Device 003: ID 1c4f:0003 SiGma Micro HID controller 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: System manufacturer System Product Name MarkForUpload: True NonfreeKernelModules: nvidia Package: xorg 1:7.6+12ubuntu2 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=pt_BR:pt:en TERM=xterm PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic root=UUID=07b50d8a-8bbe-4ec1-a9ea-5293a74a135f ro quiet splash ProcVersionSignature: Ubuntu 3.13.0-45.74~precise1-generic 3.13.11-ckt13 Tags: precise running-unity ubuntu referred-by-support compiz-0.9 Uname: Linux 3.13.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo XorgConf: Section Device Identifier Default Device Option NoLogoTrue EndSection dmi.bios.date: 09/22/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M2N68-AM SE2 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890
[Touch-packages] [Bug 1406804] LightdmLog.txt
apport information ** Attachment added: LightdmLog.txt https://bugs.launchpad.net/bugs/1406804/+attachment/4353314/+files/LightdmLog.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1406804 Title: Freezes when update to release 14.04 LTS Status in xorg package in Ubuntu: Incomplete Bug description: When updated to release 14.04 LTS something is not working properly, the PC freezes after login and after a few minutes the screen shows crazy colors. I tried it a lot of times, downloading the iso file a few times to check if anything got corrupted. I had to reinstall release 12.04 LTS back. Last note, release 14 freezes even when I lounch live CD, not only installing. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: update-manager 1:0.156.14.17 ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Wed Dec 31 17:31:37 2014 GsettingsChanges: com.ubuntu.update-manager check-new-release-ignore 'trusty' com.ubuntu.update-manager first-run false com.ubuntu.update-manager launch-time 1420053951 InstallationMedia: Ubuntu 12.04.5 LTS Precise Pangolin - Release amd64 (20140807.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: update-manager Symptom: ubuntu-release-upgrader-core UpgradeStatus: No upgrade log present (probably fresh install) --- .proc.driver.nvidia.gpus.0: Error: [Errno 21] É um diretório: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.125 Mon Dec 1 19:58:28 PST 2014 GCC version: versão do gcc 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu17.8 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CurrentDmesg: [ 11.405490] forcedeth :00:07.0 eth0: MSI enabled [ 50.030311] audit_printk_skb: 171 callbacks suppressed [ 50.030316] type=1400 audit(1427111674.315:69): apparmor=DENIED operation=open profile=/usr/lib/telepathy/mission-control-5 name=/usr/share/gvfs/remote-volume-monitors/ pid=2150 comm=mission-control requested_mask=r denied_mask=r fsuid=1000 ouid=0 DistUpgraded: Fresh install DistroCodename: precise DistroRelease: Ubuntu 12.04 DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.125, 3.13.0-32-generic, x86_64: installed nvidia-304, 304.125, 3.13.0-43-generic, x86_64: installed nvidia-304, 304.125, 3.13.0-45-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:83a4] InstallationMedia: Ubuntu 12.04.5 LTS Precise Pangolin - Release amd64 (20140807.1) JockeyStatus: xorg:nvidia_304 - Driver de aceleração de vídeo NVIDIA (Proprietário, Habilitado, Em uso) xorg:nvidia_304_updates - Driver gráfico de aceleração NVIDIA (atualizações pós instalação) (Proprietário, Desativado, Não está em uso) Lsusb: Bus 002 Device 003: ID 1c4f:0003 SiGma Micro HID controller 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: System manufacturer System Product Name MarkForUpload: True NonfreeKernelModules: nvidia Package: xorg 1:7.6+12ubuntu2 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=pt_BR:pt:en TERM=xterm PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic root=UUID=07b50d8a-8bbe-4ec1-a9ea-5293a74a135f ro quiet splash ProcVersionSignature: Ubuntu 3.13.0-45.74~precise1-generic 3.13.11-ckt13 Tags: precise running-unity ubuntu referred-by-support compiz-0.9 Uname: Linux 3.13.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo XorgConf: Section Device Identifier Default Device Option NoLogoTrue EndSection dmi.bios.date: 09/22/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M2N68-AM SE2 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890
[Touch-packages] [Bug 1406804] Lspci.txt
apport information ** Attachment added: Lspci.txt https://bugs.launchpad.net/bugs/1406804/+attachment/4353315/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1406804 Title: Freezes when update to release 14.04 LTS Status in xorg package in Ubuntu: Incomplete Bug description: When updated to release 14.04 LTS something is not working properly, the PC freezes after login and after a few minutes the screen shows crazy colors. I tried it a lot of times, downloading the iso file a few times to check if anything got corrupted. I had to reinstall release 12.04 LTS back. Last note, release 14 freezes even when I lounch live CD, not only installing. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: update-manager 1:0.156.14.17 ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Wed Dec 31 17:31:37 2014 GsettingsChanges: com.ubuntu.update-manager check-new-release-ignore 'trusty' com.ubuntu.update-manager first-run false com.ubuntu.update-manager launch-time 1420053951 InstallationMedia: Ubuntu 12.04.5 LTS Precise Pangolin - Release amd64 (20140807.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: update-manager Symptom: ubuntu-release-upgrader-core UpgradeStatus: No upgrade log present (probably fresh install) --- .proc.driver.nvidia.gpus.0: Error: [Errno 21] É um diretório: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.125 Mon Dec 1 19:58:28 PST 2014 GCC version: versão do gcc 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu17.8 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CurrentDmesg: [ 11.405490] forcedeth :00:07.0 eth0: MSI enabled [ 50.030311] audit_printk_skb: 171 callbacks suppressed [ 50.030316] type=1400 audit(1427111674.315:69): apparmor=DENIED operation=open profile=/usr/lib/telepathy/mission-control-5 name=/usr/share/gvfs/remote-volume-monitors/ pid=2150 comm=mission-control requested_mask=r denied_mask=r fsuid=1000 ouid=0 DistUpgraded: Fresh install DistroCodename: precise DistroRelease: Ubuntu 12.04 DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.125, 3.13.0-32-generic, x86_64: installed nvidia-304, 304.125, 3.13.0-43-generic, x86_64: installed nvidia-304, 304.125, 3.13.0-45-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:83a4] InstallationMedia: Ubuntu 12.04.5 LTS Precise Pangolin - Release amd64 (20140807.1) JockeyStatus: xorg:nvidia_304 - Driver de aceleração de vídeo NVIDIA (Proprietário, Habilitado, Em uso) xorg:nvidia_304_updates - Driver gráfico de aceleração NVIDIA (atualizações pós instalação) (Proprietário, Desativado, Não está em uso) Lsusb: Bus 002 Device 003: ID 1c4f:0003 SiGma Micro HID controller 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: System manufacturer System Product Name MarkForUpload: True NonfreeKernelModules: nvidia Package: xorg 1:7.6+12ubuntu2 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=pt_BR:pt:en TERM=xterm PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic root=UUID=07b50d8a-8bbe-4ec1-a9ea-5293a74a135f ro quiet splash ProcVersionSignature: Ubuntu 3.13.0-45.74~precise1-generic 3.13.11-ckt13 Tags: precise running-unity ubuntu referred-by-support compiz-0.9 Uname: Linux 3.13.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo XorgConf: Section Device Identifier Default Device Option NoLogoTrue EndSection dmi.bios.date: 09/22/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M2N68-AM SE2 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3
[Touch-packages] [Bug 1406804] Dependencies.txt
apport information ** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/1406804/+attachment/4353312/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1406804 Title: Freezes when update to release 14.04 LTS Status in xorg package in Ubuntu: Incomplete Bug description: When updated to release 14.04 LTS something is not working properly, the PC freezes after login and after a few minutes the screen shows crazy colors. I tried it a lot of times, downloading the iso file a few times to check if anything got corrupted. I had to reinstall release 12.04 LTS back. Last note, release 14 freezes even when I lounch live CD, not only installing. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: update-manager 1:0.156.14.17 ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Wed Dec 31 17:31:37 2014 GsettingsChanges: com.ubuntu.update-manager check-new-release-ignore 'trusty' com.ubuntu.update-manager first-run false com.ubuntu.update-manager launch-time 1420053951 InstallationMedia: Ubuntu 12.04.5 LTS Precise Pangolin - Release amd64 (20140807.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: update-manager Symptom: ubuntu-release-upgrader-core UpgradeStatus: No upgrade log present (probably fresh install) --- .proc.driver.nvidia.gpus.0: Error: [Errno 21] É um diretório: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.125 Mon Dec 1 19:58:28 PST 2014 GCC version: versão do gcc 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu17.8 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CurrentDmesg: [ 11.405490] forcedeth :00:07.0 eth0: MSI enabled [ 50.030311] audit_printk_skb: 171 callbacks suppressed [ 50.030316] type=1400 audit(1427111674.315:69): apparmor=DENIED operation=open profile=/usr/lib/telepathy/mission-control-5 name=/usr/share/gvfs/remote-volume-monitors/ pid=2150 comm=mission-control requested_mask=r denied_mask=r fsuid=1000 ouid=0 DistUpgraded: Fresh install DistroCodename: precise DistroRelease: Ubuntu 12.04 DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.125, 3.13.0-32-generic, x86_64: installed nvidia-304, 304.125, 3.13.0-43-generic, x86_64: installed nvidia-304, 304.125, 3.13.0-45-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:83a4] InstallationMedia: Ubuntu 12.04.5 LTS Precise Pangolin - Release amd64 (20140807.1) JockeyStatus: xorg:nvidia_304 - Driver de aceleração de vídeo NVIDIA (Proprietário, Habilitado, Em uso) xorg:nvidia_304_updates - Driver gráfico de aceleração NVIDIA (atualizações pós instalação) (Proprietário, Desativado, Não está em uso) Lsusb: Bus 002 Device 003: ID 1c4f:0003 SiGma Micro HID controller 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: System manufacturer System Product Name MarkForUpload: True NonfreeKernelModules: nvidia Package: xorg 1:7.6+12ubuntu2 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=pt_BR:pt:en TERM=xterm PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic root=UUID=07b50d8a-8bbe-4ec1-a9ea-5293a74a135f ro quiet splash ProcVersionSignature: Ubuntu 3.13.0-45.74~precise1-generic 3.13.11-ckt13 Tags: precise running-unity ubuntu referred-by-support compiz-0.9 Uname: Linux 3.13.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo XorgConf: Section Device Identifier Default Device Option NoLogoTrue EndSection dmi.bios.date: 09/22/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M2N68-AM SE2 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890
[Touch-packages] [Bug 1406804] BootLog.gz
apport information ** Attachment added: BootLog.gz https://bugs.launchpad.net/bugs/1406804/+attachment/4353311/+files/BootLog.gz -- 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/1406804 Title: Freezes when update to release 14.04 LTS Status in xorg package in Ubuntu: Incomplete Bug description: When updated to release 14.04 LTS something is not working properly, the PC freezes after login and after a few minutes the screen shows crazy colors. I tried it a lot of times, downloading the iso file a few times to check if anything got corrupted. I had to reinstall release 12.04 LTS back. Last note, release 14 freezes even when I lounch live CD, not only installing. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: update-manager 1:0.156.14.17 ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Wed Dec 31 17:31:37 2014 GsettingsChanges: com.ubuntu.update-manager check-new-release-ignore 'trusty' com.ubuntu.update-manager first-run false com.ubuntu.update-manager launch-time 1420053951 InstallationMedia: Ubuntu 12.04.5 LTS Precise Pangolin - Release amd64 (20140807.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: update-manager Symptom: ubuntu-release-upgrader-core UpgradeStatus: No upgrade log present (probably fresh install) --- .proc.driver.nvidia.gpus.0: Error: [Errno 21] É um diretório: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.125 Mon Dec 1 19:58:28 PST 2014 GCC version: versão do gcc 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu17.8 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CurrentDmesg: [ 11.405490] forcedeth :00:07.0 eth0: MSI enabled [ 50.030311] audit_printk_skb: 171 callbacks suppressed [ 50.030316] type=1400 audit(1427111674.315:69): apparmor=DENIED operation=open profile=/usr/lib/telepathy/mission-control-5 name=/usr/share/gvfs/remote-volume-monitors/ pid=2150 comm=mission-control requested_mask=r denied_mask=r fsuid=1000 ouid=0 DistUpgraded: Fresh install DistroCodename: precise DistroRelease: Ubuntu 12.04 DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.125, 3.13.0-32-generic, x86_64: installed nvidia-304, 304.125, 3.13.0-43-generic, x86_64: installed nvidia-304, 304.125, 3.13.0-45-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:83a4] InstallationMedia: Ubuntu 12.04.5 LTS Precise Pangolin - Release amd64 (20140807.1) JockeyStatus: xorg:nvidia_304 - Driver de aceleração de vídeo NVIDIA (Proprietário, Habilitado, Em uso) xorg:nvidia_304_updates - Driver gráfico de aceleração NVIDIA (atualizações pós instalação) (Proprietário, Desativado, Não está em uso) Lsusb: Bus 002 Device 003: ID 1c4f:0003 SiGma Micro HID controller 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: System manufacturer System Product Name MarkForUpload: True NonfreeKernelModules: nvidia Package: xorg 1:7.6+12ubuntu2 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=pt_BR:pt:en TERM=xterm PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic root=UUID=07b50d8a-8bbe-4ec1-a9ea-5293a74a135f ro quiet splash ProcVersionSignature: Ubuntu 3.13.0-45.74~precise1-generic 3.13.11-ckt13 Tags: precise running-unity ubuntu referred-by-support compiz-0.9 Uname: Linux 3.13.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo XorgConf: Section Device Identifier Default Device Option NoLogoTrue EndSection dmi.bios.date: 09/22/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M2N68-AM SE2 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type:
[Touch-packages] [Bug 1406804] Re: Freezes when update to release 14.04 LTS
apport information ** Tags added: apport-collected compiz-0.9 referred-by-support ubuntu ** Description changed: When updated to release 14.04 LTS something is not working properly, the PC freezes after login and after a few minutes the screen shows crazy colors. I tried it a lot of times, downloading the iso file a few times to check if anything got corrupted. I had to reinstall release 12.04 LTS back. Last note, release 14 freezes even when I lounch live CD, not only installing. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: update-manager 1:0.156.14.17 ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Wed Dec 31 17:31:37 2014 GsettingsChanges: com.ubuntu.update-manager check-new-release-ignore 'trusty' com.ubuntu.update-manager first-run false com.ubuntu.update-manager launch-time 1420053951 InstallationMedia: Ubuntu 12.04.5 LTS Precise Pangolin - Release amd64 (20140807.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: update-manager Symptom: ubuntu-release-upgrader-core UpgradeStatus: No upgrade log present (probably fresh install) + --- + .proc.driver.nvidia.gpus.0: Error: [Errno 21] É um diretório: '/proc/driver/nvidia/gpus/0' + .proc.driver.nvidia.registry: Binary: + .proc.driver.nvidia.version: + NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.125 Mon Dec 1 19:58:28 PST 2014 + GCC version: versão do gcc 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) + .tmp.unity.support.test.0: + + ApportVersion: 2.0.1-0ubuntu17.8 + Architecture: amd64 + CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] + CompositorRunning: compiz + CurrentDmesg: + [ 11.405490] forcedeth :00:07.0 eth0: MSI enabled + [ 50.030311] audit_printk_skb: 171 callbacks suppressed + [ 50.030316] type=1400 audit(1427111674.315:69): apparmor=DENIED operation=open profile=/usr/lib/telepathy/mission-control-5 name=/usr/share/gvfs/remote-volume-monitors/ pid=2150 comm=mission-control requested_mask=r denied_mask=r fsuid=1000 ouid=0 + DistUpgraded: Fresh install + DistroCodename: precise + DistroRelease: Ubuntu 12.04 + DistroVariant: ubuntu + DkmsStatus: + nvidia-304, 304.125, 3.13.0-32-generic, x86_64: installed + nvidia-304, 304.125, 3.13.0-43-generic, x86_64: installed + nvidia-304, 304.125, 3.13.0-45-generic, x86_64: installed + DpkgLog: + + ExtraDebuggingInterest: Yes, if not too technical + GraphicsCard: + NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) (prog-if 00 [VGA controller]) +Subsystem: ASUSTeK Computer Inc. Device [1043:83a4] + InstallationMedia: Ubuntu 12.04.5 LTS Precise Pangolin - Release amd64 (20140807.1) + JockeyStatus: + xorg:nvidia_304 - Driver de aceleração de vídeo NVIDIA (Proprietário, Habilitado, Em uso) + xorg:nvidia_304_updates - Driver gráfico de aceleração NVIDIA (atualizações pós instalação) (Proprietário, Desativado, Não está em uso) + Lsusb: + Bus 002 Device 003: ID 1c4f:0003 SiGma Micro HID controller + 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: System manufacturer System Product Name + MarkForUpload: True + NonfreeKernelModules: nvidia + Package: xorg 1:7.6+12ubuntu2 + PackageArchitecture: amd64 + ProcEnviron: + LANGUAGE=pt_BR:pt:en + TERM=xterm + PATH=(custom, no user) + LANG=pt_BR.UTF-8 + SHELL=/bin/bash + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic root=UUID=07b50d8a-8bbe-4ec1-a9ea-5293a74a135f ro quiet splash + ProcVersionSignature: Ubuntu 3.13.0-45.74~precise1-generic 3.13.11-ckt13 + Tags: precise running-unity ubuntu referred-by-support compiz-0.9 + Uname: Linux 3.13.0-45-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + XorgConf: + Section Device + Identifier Default Device + Option NoLogoTrue + EndSection + dmi.bios.date: 09/22/2009 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 1002 + dmi.board.asset.tag: To Be Filled By O.E.M. + dmi.board.name: M2N68-AM SE2 + 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.:bvr1002:bd09/22/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N68-AMSE2:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: +
[Touch-packages] [Bug 1406804] xdpyinfo.txt
apport information ** Attachment added: xdpyinfo.txt https://bugs.launchpad.net/bugs/1406804/+attachment/4353328/+files/xdpyinfo.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1406804 Title: Freezes when update to release 14.04 LTS Status in xorg package in Ubuntu: Incomplete Bug description: When updated to release 14.04 LTS something is not working properly, the PC freezes after login and after a few minutes the screen shows crazy colors. I tried it a lot of times, downloading the iso file a few times to check if anything got corrupted. I had to reinstall release 12.04 LTS back. Last note, release 14 freezes even when I lounch live CD, not only installing. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: update-manager 1:0.156.14.17 ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Wed Dec 31 17:31:37 2014 GsettingsChanges: com.ubuntu.update-manager check-new-release-ignore 'trusty' com.ubuntu.update-manager first-run false com.ubuntu.update-manager launch-time 1420053951 InstallationMedia: Ubuntu 12.04.5 LTS Precise Pangolin - Release amd64 (20140807.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: update-manager Symptom: ubuntu-release-upgrader-core UpgradeStatus: No upgrade log present (probably fresh install) --- .proc.driver.nvidia.gpus.0: Error: [Errno 21] É um diretório: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.125 Mon Dec 1 19:58:28 PST 2014 GCC version: versão do gcc 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu17.8 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CurrentDmesg: [ 11.405490] forcedeth :00:07.0 eth0: MSI enabled [ 50.030311] audit_printk_skb: 171 callbacks suppressed [ 50.030316] type=1400 audit(1427111674.315:69): apparmor=DENIED operation=open profile=/usr/lib/telepathy/mission-control-5 name=/usr/share/gvfs/remote-volume-monitors/ pid=2150 comm=mission-control requested_mask=r denied_mask=r fsuid=1000 ouid=0 DistUpgraded: Fresh install DistroCodename: precise DistroRelease: Ubuntu 12.04 DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.125, 3.13.0-32-generic, x86_64: installed nvidia-304, 304.125, 3.13.0-43-generic, x86_64: installed nvidia-304, 304.125, 3.13.0-45-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:83a4] InstallationMedia: Ubuntu 12.04.5 LTS Precise Pangolin - Release amd64 (20140807.1) JockeyStatus: xorg:nvidia_304 - Driver de aceleração de vídeo NVIDIA (Proprietário, Habilitado, Em uso) xorg:nvidia_304_updates - Driver gráfico de aceleração NVIDIA (atualizações pós instalação) (Proprietário, Desativado, Não está em uso) Lsusb: Bus 002 Device 003: ID 1c4f:0003 SiGma Micro HID controller 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: System manufacturer System Product Name MarkForUpload: True NonfreeKernelModules: nvidia Package: xorg 1:7.6+12ubuntu2 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=pt_BR:pt:en TERM=xterm PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic root=UUID=07b50d8a-8bbe-4ec1-a9ea-5293a74a135f ro quiet splash ProcVersionSignature: Ubuntu 3.13.0-45.74~precise1-generic 3.13.11-ckt13 Tags: precise running-unity ubuntu referred-by-support compiz-0.9 Uname: Linux 3.13.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo XorgConf: Section Device Identifier Default Device Option NoLogoTrue EndSection dmi.bios.date: 09/22/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M2N68-AM SE2 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890
[Touch-packages] [Bug 1406804] NvidiaBugReportLog.txt
apport information ** Attachment added: NvidiaBugReportLog.txt https://bugs.launchpad.net/bugs/1406804/+attachment/4353316/+files/NvidiaBugReportLog.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1406804 Title: Freezes when update to release 14.04 LTS Status in xorg package in Ubuntu: Incomplete Bug description: When updated to release 14.04 LTS something is not working properly, the PC freezes after login and after a few minutes the screen shows crazy colors. I tried it a lot of times, downloading the iso file a few times to check if anything got corrupted. I had to reinstall release 12.04 LTS back. Last note, release 14 freezes even when I lounch live CD, not only installing. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: update-manager 1:0.156.14.17 ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Wed Dec 31 17:31:37 2014 GsettingsChanges: com.ubuntu.update-manager check-new-release-ignore 'trusty' com.ubuntu.update-manager first-run false com.ubuntu.update-manager launch-time 1420053951 InstallationMedia: Ubuntu 12.04.5 LTS Precise Pangolin - Release amd64 (20140807.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: update-manager Symptom: ubuntu-release-upgrader-core UpgradeStatus: No upgrade log present (probably fresh install) --- .proc.driver.nvidia.gpus.0: Error: [Errno 21] É um diretório: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.125 Mon Dec 1 19:58:28 PST 2014 GCC version: versão do gcc 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu17.8 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CurrentDmesg: [ 11.405490] forcedeth :00:07.0 eth0: MSI enabled [ 50.030311] audit_printk_skb: 171 callbacks suppressed [ 50.030316] type=1400 audit(1427111674.315:69): apparmor=DENIED operation=open profile=/usr/lib/telepathy/mission-control-5 name=/usr/share/gvfs/remote-volume-monitors/ pid=2150 comm=mission-control requested_mask=r denied_mask=r fsuid=1000 ouid=0 DistUpgraded: Fresh install DistroCodename: precise DistroRelease: Ubuntu 12.04 DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.125, 3.13.0-32-generic, x86_64: installed nvidia-304, 304.125, 3.13.0-43-generic, x86_64: installed nvidia-304, 304.125, 3.13.0-45-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:83a4] InstallationMedia: Ubuntu 12.04.5 LTS Precise Pangolin - Release amd64 (20140807.1) JockeyStatus: xorg:nvidia_304 - Driver de aceleração de vídeo NVIDIA (Proprietário, Habilitado, Em uso) xorg:nvidia_304_updates - Driver gráfico de aceleração NVIDIA (atualizações pós instalação) (Proprietário, Desativado, Não está em uso) Lsusb: Bus 002 Device 003: ID 1c4f:0003 SiGma Micro HID controller 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: System manufacturer System Product Name MarkForUpload: True NonfreeKernelModules: nvidia Package: xorg 1:7.6+12ubuntu2 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=pt_BR:pt:en TERM=xterm PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic root=UUID=07b50d8a-8bbe-4ec1-a9ea-5293a74a135f ro quiet splash ProcVersionSignature: Ubuntu 3.13.0-45.74~precise1-generic 3.13.11-ckt13 Tags: precise running-unity ubuntu referred-by-support compiz-0.9 Uname: Linux 3.13.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo XorgConf: Section Device Identifier Default Device Option NoLogoTrue EndSection dmi.bios.date: 09/22/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M2N68-AM SE2 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag:
[Touch-packages] [Bug 1406804] ProcInterrupts.txt
apport information ** Attachment added: ProcInterrupts.txt https://bugs.launchpad.net/bugs/1406804/+attachment/4353318/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1406804 Title: Freezes when update to release 14.04 LTS Status in xorg package in Ubuntu: Incomplete Bug description: When updated to release 14.04 LTS something is not working properly, the PC freezes after login and after a few minutes the screen shows crazy colors. I tried it a lot of times, downloading the iso file a few times to check if anything got corrupted. I had to reinstall release 12.04 LTS back. Last note, release 14 freezes even when I lounch live CD, not only installing. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: update-manager 1:0.156.14.17 ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Wed Dec 31 17:31:37 2014 GsettingsChanges: com.ubuntu.update-manager check-new-release-ignore 'trusty' com.ubuntu.update-manager first-run false com.ubuntu.update-manager launch-time 1420053951 InstallationMedia: Ubuntu 12.04.5 LTS Precise Pangolin - Release amd64 (20140807.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: update-manager Symptom: ubuntu-release-upgrader-core UpgradeStatus: No upgrade log present (probably fresh install) --- .proc.driver.nvidia.gpus.0: Error: [Errno 21] É um diretório: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.125 Mon Dec 1 19:58:28 PST 2014 GCC version: versão do gcc 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu17.8 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CurrentDmesg: [ 11.405490] forcedeth :00:07.0 eth0: MSI enabled [ 50.030311] audit_printk_skb: 171 callbacks suppressed [ 50.030316] type=1400 audit(1427111674.315:69): apparmor=DENIED operation=open profile=/usr/lib/telepathy/mission-control-5 name=/usr/share/gvfs/remote-volume-monitors/ pid=2150 comm=mission-control requested_mask=r denied_mask=r fsuid=1000 ouid=0 DistUpgraded: Fresh install DistroCodename: precise DistroRelease: Ubuntu 12.04 DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.125, 3.13.0-32-generic, x86_64: installed nvidia-304, 304.125, 3.13.0-43-generic, x86_64: installed nvidia-304, 304.125, 3.13.0-45-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:83a4] InstallationMedia: Ubuntu 12.04.5 LTS Precise Pangolin - Release amd64 (20140807.1) JockeyStatus: xorg:nvidia_304 - Driver de aceleração de vídeo NVIDIA (Proprietário, Habilitado, Em uso) xorg:nvidia_304_updates - Driver gráfico de aceleração NVIDIA (atualizações pós instalação) (Proprietário, Desativado, Não está em uso) Lsusb: Bus 002 Device 003: ID 1c4f:0003 SiGma Micro HID controller 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: System manufacturer System Product Name MarkForUpload: True NonfreeKernelModules: nvidia Package: xorg 1:7.6+12ubuntu2 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=pt_BR:pt:en TERM=xterm PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic root=UUID=07b50d8a-8bbe-4ec1-a9ea-5293a74a135f ro quiet splash ProcVersionSignature: Ubuntu 3.13.0-45.74~precise1-generic 3.13.11-ckt13 Tags: precise running-unity ubuntu referred-by-support compiz-0.9 Uname: Linux 3.13.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo XorgConf: Section Device Identifier Default Device Option NoLogoTrue EndSection dmi.bios.date: 09/22/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M2N68-AM SE2 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890
[Touch-packages] [Bug 1406804] nvidia-settings.txt
apport information ** Attachment added: nvidia-settings.txt https://bugs.launchpad.net/bugs/1406804/+attachment/4353327/+files/nvidia-settings.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1406804 Title: Freezes when update to release 14.04 LTS Status in xorg package in Ubuntu: Incomplete Bug description: When updated to release 14.04 LTS something is not working properly, the PC freezes after login and after a few minutes the screen shows crazy colors. I tried it a lot of times, downloading the iso file a few times to check if anything got corrupted. I had to reinstall release 12.04 LTS back. Last note, release 14 freezes even when I lounch live CD, not only installing. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: update-manager 1:0.156.14.17 ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Wed Dec 31 17:31:37 2014 GsettingsChanges: com.ubuntu.update-manager check-new-release-ignore 'trusty' com.ubuntu.update-manager first-run false com.ubuntu.update-manager launch-time 1420053951 InstallationMedia: Ubuntu 12.04.5 LTS Precise Pangolin - Release amd64 (20140807.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: update-manager Symptom: ubuntu-release-upgrader-core UpgradeStatus: No upgrade log present (probably fresh install) --- .proc.driver.nvidia.gpus.0: Error: [Errno 21] É um diretório: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.125 Mon Dec 1 19:58:28 PST 2014 GCC version: versão do gcc 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu17.8 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CurrentDmesg: [ 11.405490] forcedeth :00:07.0 eth0: MSI enabled [ 50.030311] audit_printk_skb: 171 callbacks suppressed [ 50.030316] type=1400 audit(1427111674.315:69): apparmor=DENIED operation=open profile=/usr/lib/telepathy/mission-control-5 name=/usr/share/gvfs/remote-volume-monitors/ pid=2150 comm=mission-control requested_mask=r denied_mask=r fsuid=1000 ouid=0 DistUpgraded: Fresh install DistroCodename: precise DistroRelease: Ubuntu 12.04 DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.125, 3.13.0-32-generic, x86_64: installed nvidia-304, 304.125, 3.13.0-43-generic, x86_64: installed nvidia-304, 304.125, 3.13.0-45-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:83a4] InstallationMedia: Ubuntu 12.04.5 LTS Precise Pangolin - Release amd64 (20140807.1) JockeyStatus: xorg:nvidia_304 - Driver de aceleração de vídeo NVIDIA (Proprietário, Habilitado, Em uso) xorg:nvidia_304_updates - Driver gráfico de aceleração NVIDIA (atualizações pós instalação) (Proprietário, Desativado, Não está em uso) Lsusb: Bus 002 Device 003: ID 1c4f:0003 SiGma Micro HID controller 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: System manufacturer System Product Name MarkForUpload: True NonfreeKernelModules: nvidia Package: xorg 1:7.6+12ubuntu2 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=pt_BR:pt:en TERM=xterm PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic root=UUID=07b50d8a-8bbe-4ec1-a9ea-5293a74a135f ro quiet splash ProcVersionSignature: Ubuntu 3.13.0-45.74~precise1-generic 3.13.11-ckt13 Tags: precise running-unity ubuntu referred-by-support compiz-0.9 Uname: Linux 3.13.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo XorgConf: Section Device Identifier Default Device Option NoLogoTrue EndSection dmi.bios.date: 09/22/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M2N68-AM SE2 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890
[Touch-packages] [Bug 1406804] ProcCpuinfo.txt
apport information ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/1406804/+attachment/4353317/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1406804 Title: Freezes when update to release 14.04 LTS Status in xorg package in Ubuntu: Incomplete Bug description: When updated to release 14.04 LTS something is not working properly, the PC freezes after login and after a few minutes the screen shows crazy colors. I tried it a lot of times, downloading the iso file a few times to check if anything got corrupted. I had to reinstall release 12.04 LTS back. Last note, release 14 freezes even when I lounch live CD, not only installing. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: update-manager 1:0.156.14.17 ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Wed Dec 31 17:31:37 2014 GsettingsChanges: com.ubuntu.update-manager check-new-release-ignore 'trusty' com.ubuntu.update-manager first-run false com.ubuntu.update-manager launch-time 1420053951 InstallationMedia: Ubuntu 12.04.5 LTS Precise Pangolin - Release amd64 (20140807.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: update-manager Symptom: ubuntu-release-upgrader-core UpgradeStatus: No upgrade log present (probably fresh install) --- .proc.driver.nvidia.gpus.0: Error: [Errno 21] É um diretório: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.125 Mon Dec 1 19:58:28 PST 2014 GCC version: versão do gcc 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu17.8 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CurrentDmesg: [ 11.405490] forcedeth :00:07.0 eth0: MSI enabled [ 50.030311] audit_printk_skb: 171 callbacks suppressed [ 50.030316] type=1400 audit(1427111674.315:69): apparmor=DENIED operation=open profile=/usr/lib/telepathy/mission-control-5 name=/usr/share/gvfs/remote-volume-monitors/ pid=2150 comm=mission-control requested_mask=r denied_mask=r fsuid=1000 ouid=0 DistUpgraded: Fresh install DistroCodename: precise DistroRelease: Ubuntu 12.04 DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.125, 3.13.0-32-generic, x86_64: installed nvidia-304, 304.125, 3.13.0-43-generic, x86_64: installed nvidia-304, 304.125, 3.13.0-45-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:83a4] InstallationMedia: Ubuntu 12.04.5 LTS Precise Pangolin - Release amd64 (20140807.1) JockeyStatus: xorg:nvidia_304 - Driver de aceleração de vídeo NVIDIA (Proprietário, Habilitado, Em uso) xorg:nvidia_304_updates - Driver gráfico de aceleração NVIDIA (atualizações pós instalação) (Proprietário, Desativado, Não está em uso) Lsusb: Bus 002 Device 003: ID 1c4f:0003 SiGma Micro HID controller 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: System manufacturer System Product Name MarkForUpload: True NonfreeKernelModules: nvidia Package: xorg 1:7.6+12ubuntu2 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=pt_BR:pt:en TERM=xterm PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic root=UUID=07b50d8a-8bbe-4ec1-a9ea-5293a74a135f ro quiet splash ProcVersionSignature: Ubuntu 3.13.0-45.74~precise1-generic 3.13.11-ckt13 Tags: precise running-unity ubuntu referred-by-support compiz-0.9 Uname: Linux 3.13.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo XorgConf: Section Device Identifier Default Device Option NoLogoTrue EndSection dmi.bios.date: 09/22/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M2N68-AM SE2 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890
[Touch-packages] [Bug 1406804] XorgLogOld.txt
apport information ** Attachment added: XorgLogOld.txt https://bugs.launchpad.net/bugs/1406804/+attachment/4353324/+files/XorgLogOld.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1406804 Title: Freezes when update to release 14.04 LTS Status in xorg package in Ubuntu: Incomplete Bug description: When updated to release 14.04 LTS something is not working properly, the PC freezes after login and after a few minutes the screen shows crazy colors. I tried it a lot of times, downloading the iso file a few times to check if anything got corrupted. I had to reinstall release 12.04 LTS back. Last note, release 14 freezes even when I lounch live CD, not only installing. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: update-manager 1:0.156.14.17 ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Wed Dec 31 17:31:37 2014 GsettingsChanges: com.ubuntu.update-manager check-new-release-ignore 'trusty' com.ubuntu.update-manager first-run false com.ubuntu.update-manager launch-time 1420053951 InstallationMedia: Ubuntu 12.04.5 LTS Precise Pangolin - Release amd64 (20140807.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: update-manager Symptom: ubuntu-release-upgrader-core UpgradeStatus: No upgrade log present (probably fresh install) --- .proc.driver.nvidia.gpus.0: Error: [Errno 21] É um diretório: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.125 Mon Dec 1 19:58:28 PST 2014 GCC version: versão do gcc 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu17.8 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CurrentDmesg: [ 11.405490] forcedeth :00:07.0 eth0: MSI enabled [ 50.030311] audit_printk_skb: 171 callbacks suppressed [ 50.030316] type=1400 audit(1427111674.315:69): apparmor=DENIED operation=open profile=/usr/lib/telepathy/mission-control-5 name=/usr/share/gvfs/remote-volume-monitors/ pid=2150 comm=mission-control requested_mask=r denied_mask=r fsuid=1000 ouid=0 DistUpgraded: Fresh install DistroCodename: precise DistroRelease: Ubuntu 12.04 DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.125, 3.13.0-32-generic, x86_64: installed nvidia-304, 304.125, 3.13.0-43-generic, x86_64: installed nvidia-304, 304.125, 3.13.0-45-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:83a4] InstallationMedia: Ubuntu 12.04.5 LTS Precise Pangolin - Release amd64 (20140807.1) JockeyStatus: xorg:nvidia_304 - Driver de aceleração de vídeo NVIDIA (Proprietário, Habilitado, Em uso) xorg:nvidia_304_updates - Driver gráfico de aceleração NVIDIA (atualizações pós instalação) (Proprietário, Desativado, Não está em uso) Lsusb: Bus 002 Device 003: ID 1c4f:0003 SiGma Micro HID controller 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: System manufacturer System Product Name MarkForUpload: True NonfreeKernelModules: nvidia Package: xorg 1:7.6+12ubuntu2 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=pt_BR:pt:en TERM=xterm PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic root=UUID=07b50d8a-8bbe-4ec1-a9ea-5293a74a135f ro quiet splash ProcVersionSignature: Ubuntu 3.13.0-45.74~precise1-generic 3.13.11-ckt13 Tags: precise running-unity ubuntu referred-by-support compiz-0.9 Uname: Linux 3.13.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo XorgConf: Section Device Identifier Default Device Option NoLogoTrue EndSection dmi.bios.date: 09/22/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M2N68-AM SE2 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890
[Touch-packages] [Bug 1406804] UnitySupportTest.txt
apport information ** Attachment added: UnitySupportTest.txt https://bugs.launchpad.net/bugs/1406804/+attachment/4353322/+files/UnitySupportTest.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1406804 Title: Freezes when update to release 14.04 LTS Status in xorg package in Ubuntu: Incomplete Bug description: When updated to release 14.04 LTS something is not working properly, the PC freezes after login and after a few minutes the screen shows crazy colors. I tried it a lot of times, downloading the iso file a few times to check if anything got corrupted. I had to reinstall release 12.04 LTS back. Last note, release 14 freezes even when I lounch live CD, not only installing. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: update-manager 1:0.156.14.17 ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Wed Dec 31 17:31:37 2014 GsettingsChanges: com.ubuntu.update-manager check-new-release-ignore 'trusty' com.ubuntu.update-manager first-run false com.ubuntu.update-manager launch-time 1420053951 InstallationMedia: Ubuntu 12.04.5 LTS Precise Pangolin - Release amd64 (20140807.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: update-manager Symptom: ubuntu-release-upgrader-core UpgradeStatus: No upgrade log present (probably fresh install) --- .proc.driver.nvidia.gpus.0: Error: [Errno 21] É um diretório: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.125 Mon Dec 1 19:58:28 PST 2014 GCC version: versão do gcc 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu17.8 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CurrentDmesg: [ 11.405490] forcedeth :00:07.0 eth0: MSI enabled [ 50.030311] audit_printk_skb: 171 callbacks suppressed [ 50.030316] type=1400 audit(1427111674.315:69): apparmor=DENIED operation=open profile=/usr/lib/telepathy/mission-control-5 name=/usr/share/gvfs/remote-volume-monitors/ pid=2150 comm=mission-control requested_mask=r denied_mask=r fsuid=1000 ouid=0 DistUpgraded: Fresh install DistroCodename: precise DistroRelease: Ubuntu 12.04 DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.125, 3.13.0-32-generic, x86_64: installed nvidia-304, 304.125, 3.13.0-43-generic, x86_64: installed nvidia-304, 304.125, 3.13.0-45-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:83a4] InstallationMedia: Ubuntu 12.04.5 LTS Precise Pangolin - Release amd64 (20140807.1) JockeyStatus: xorg:nvidia_304 - Driver de aceleração de vídeo NVIDIA (Proprietário, Habilitado, Em uso) xorg:nvidia_304_updates - Driver gráfico de aceleração NVIDIA (atualizações pós instalação) (Proprietário, Desativado, Não está em uso) Lsusb: Bus 002 Device 003: ID 1c4f:0003 SiGma Micro HID controller 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: System manufacturer System Product Name MarkForUpload: True NonfreeKernelModules: nvidia Package: xorg 1:7.6+12ubuntu2 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=pt_BR:pt:en TERM=xterm PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic root=UUID=07b50d8a-8bbe-4ec1-a9ea-5293a74a135f ro quiet splash ProcVersionSignature: Ubuntu 3.13.0-45.74~precise1-generic 3.13.11-ckt13 Tags: precise running-unity ubuntu referred-by-support compiz-0.9 Uname: Linux 3.13.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo XorgConf: Section Device Identifier Default Device Option NoLogoTrue EndSection dmi.bios.date: 09/22/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M2N68-AM SE2 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag:
[Touch-packages] [Bug 1406804] XorgLog.txt
apport information ** Attachment added: XorgLog.txt https://bugs.launchpad.net/bugs/1406804/+attachment/4353323/+files/XorgLog.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1406804 Title: Freezes when update to release 14.04 LTS Status in xorg package in Ubuntu: Incomplete Bug description: When updated to release 14.04 LTS something is not working properly, the PC freezes after login and after a few minutes the screen shows crazy colors. I tried it a lot of times, downloading the iso file a few times to check if anything got corrupted. I had to reinstall release 12.04 LTS back. Last note, release 14 freezes even when I lounch live CD, not only installing. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: update-manager 1:0.156.14.17 ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Wed Dec 31 17:31:37 2014 GsettingsChanges: com.ubuntu.update-manager check-new-release-ignore 'trusty' com.ubuntu.update-manager first-run false com.ubuntu.update-manager launch-time 1420053951 InstallationMedia: Ubuntu 12.04.5 LTS Precise Pangolin - Release amd64 (20140807.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: update-manager Symptom: ubuntu-release-upgrader-core UpgradeStatus: No upgrade log present (probably fresh install) --- .proc.driver.nvidia.gpus.0: Error: [Errno 21] É um diretório: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.125 Mon Dec 1 19:58:28 PST 2014 GCC version: versão do gcc 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu17.8 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CurrentDmesg: [ 11.405490] forcedeth :00:07.0 eth0: MSI enabled [ 50.030311] audit_printk_skb: 171 callbacks suppressed [ 50.030316] type=1400 audit(1427111674.315:69): apparmor=DENIED operation=open profile=/usr/lib/telepathy/mission-control-5 name=/usr/share/gvfs/remote-volume-monitors/ pid=2150 comm=mission-control requested_mask=r denied_mask=r fsuid=1000 ouid=0 DistUpgraded: Fresh install DistroCodename: precise DistroRelease: Ubuntu 12.04 DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.125, 3.13.0-32-generic, x86_64: installed nvidia-304, 304.125, 3.13.0-43-generic, x86_64: installed nvidia-304, 304.125, 3.13.0-45-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:83a4] InstallationMedia: Ubuntu 12.04.5 LTS Precise Pangolin - Release amd64 (20140807.1) JockeyStatus: xorg:nvidia_304 - Driver de aceleração de vídeo NVIDIA (Proprietário, Habilitado, Em uso) xorg:nvidia_304_updates - Driver gráfico de aceleração NVIDIA (atualizações pós instalação) (Proprietário, Desativado, Não está em uso) Lsusb: Bus 002 Device 003: ID 1c4f:0003 SiGma Micro HID controller 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: System manufacturer System Product Name MarkForUpload: True NonfreeKernelModules: nvidia Package: xorg 1:7.6+12ubuntu2 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=pt_BR:pt:en TERM=xterm PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic root=UUID=07b50d8a-8bbe-4ec1-a9ea-5293a74a135f ro quiet splash ProcVersionSignature: Ubuntu 3.13.0-45.74~precise1-generic 3.13.11-ckt13 Tags: precise running-unity ubuntu referred-by-support compiz-0.9 Uname: Linux 3.13.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo XorgConf: Section Device Identifier Default Device Option NoLogoTrue EndSection dmi.bios.date: 09/22/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M2N68-AM SE2 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890
[Touch-packages] [Bug 1406804] Xrandr.txt
apport information ** Attachment added: Xrandr.txt https://bugs.launchpad.net/bugs/1406804/+attachment/4353325/+files/Xrandr.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1406804 Title: Freezes when update to release 14.04 LTS Status in xorg package in Ubuntu: Incomplete Bug description: When updated to release 14.04 LTS something is not working properly, the PC freezes after login and after a few minutes the screen shows crazy colors. I tried it a lot of times, downloading the iso file a few times to check if anything got corrupted. I had to reinstall release 12.04 LTS back. Last note, release 14 freezes even when I lounch live CD, not only installing. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: update-manager 1:0.156.14.17 ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Wed Dec 31 17:31:37 2014 GsettingsChanges: com.ubuntu.update-manager check-new-release-ignore 'trusty' com.ubuntu.update-manager first-run false com.ubuntu.update-manager launch-time 1420053951 InstallationMedia: Ubuntu 12.04.5 LTS Precise Pangolin - Release amd64 (20140807.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: update-manager Symptom: ubuntu-release-upgrader-core UpgradeStatus: No upgrade log present (probably fresh install) --- .proc.driver.nvidia.gpus.0: Error: [Errno 21] É um diretório: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.125 Mon Dec 1 19:58:28 PST 2014 GCC version: versão do gcc 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu17.8 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CurrentDmesg: [ 11.405490] forcedeth :00:07.0 eth0: MSI enabled [ 50.030311] audit_printk_skb: 171 callbacks suppressed [ 50.030316] type=1400 audit(1427111674.315:69): apparmor=DENIED operation=open profile=/usr/lib/telepathy/mission-control-5 name=/usr/share/gvfs/remote-volume-monitors/ pid=2150 comm=mission-control requested_mask=r denied_mask=r fsuid=1000 ouid=0 DistUpgraded: Fresh install DistroCodename: precise DistroRelease: Ubuntu 12.04 DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.125, 3.13.0-32-generic, x86_64: installed nvidia-304, 304.125, 3.13.0-43-generic, x86_64: installed nvidia-304, 304.125, 3.13.0-45-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:83a4] InstallationMedia: Ubuntu 12.04.5 LTS Precise Pangolin - Release amd64 (20140807.1) JockeyStatus: xorg:nvidia_304 - Driver de aceleração de vídeo NVIDIA (Proprietário, Habilitado, Em uso) xorg:nvidia_304_updates - Driver gráfico de aceleração NVIDIA (atualizações pós instalação) (Proprietário, Desativado, Não está em uso) Lsusb: Bus 002 Device 003: ID 1c4f:0003 SiGma Micro HID controller 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: System manufacturer System Product Name MarkForUpload: True NonfreeKernelModules: nvidia Package: xorg 1:7.6+12ubuntu2 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=pt_BR:pt:en TERM=xterm PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic root=UUID=07b50d8a-8bbe-4ec1-a9ea-5293a74a135f ro quiet splash ProcVersionSignature: Ubuntu 3.13.0-45.74~precise1-generic 3.13.11-ckt13 Tags: precise running-unity ubuntu referred-by-support compiz-0.9 Uname: Linux 3.13.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo XorgConf: Section Device Identifier Default Device Option NoLogoTrue EndSection dmi.bios.date: 09/22/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M2N68-AM SE2 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type:
[Touch-packages] [Bug 1424263] Re: Broken dependencies
Suggested by Jim Buzaid command doesn't work for me: The following packages have unmet dependencies: libegl1-mesa : Depends: libgbm1 (= 7.11~1) but it is not going to be installed Recommends: libegl1-mesa-drivers libgl1-mesa-glx-lts-utopic:i386 : Depends: libglapi-mesa-lts-utopic:i386 (= 10.3.2-0ubuntu1~trusty2) but it is not going to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held 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=set 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 1435364] [NEW] Lockscreen unresponsive after starting app from QtC or cmdline
Public bug reported: Steps to reproduce: * Launch an app from QtCreator * close the app again * Lock the screen * try to unlock the screen again = lockscreen unresponsive ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1435364 Title: Lockscreen unresponsive after starting app from QtC or cmdline Status in unity8 package in Ubuntu: New Bug description: Steps to reproduce: * Launch an app from QtCreator * close the app again * Lock the screen * try to unlock the screen again = lockscreen unresponsive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1435364/+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 1422681] Re: split out upstart-sysv
** Branch linked: lp:ubuntu/vivid-proposed/init-system-helpers -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1422681 Title: split out upstart-sysv Status in init-system-helpers package in Ubuntu: New Status in systemd package in Ubuntu: New Status in ubuntu-touch-meta package in Ubuntu: New Status in upstart package in Ubuntu: Triaged Bug description: After switching to systemd permanently (apt get install systemd-sysv) and purging the now not needed upstart package, I tried to boot with the upstart fallback option in grub, just to find out it doesn't work. It looks like important init files are still in the upstart package instead of upstart-bin and should probably be moved there to keep the upstart fallback option working. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1422681/+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 1425362] Re: unity8 crashed with SIGSEGV in QLightDM::GreeterImpl::authenticateWithPam() when logging in
untagging for vivid-stab-candidate, this code should be the same for rtm - and evidence seen and this is only reproducible on vmware desktop (so not priority for mobile devices) -- 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/1425362 Title: unity8 crashed with SIGSEGV in QLightDM::GreeterImpl::authenticateWithPam() when logging in Status in unity8 package in Ubuntu: In Progress Bug description: I'm trying to run unity8 in a vivid vmware session (mir works fine here). But unity8 crashes when logging in, and it happens again everytime I insert my password in the u8 lockscreen. --- The only way to successfully log in unity8 was to add myself to the nopasswdlogin group. This made the unity8 pam module checks, and thus no crash. ProblemType: CrashDistroRelease: Ubuntu 15.04 Package: unity8 8.02+15.04.20150224-0ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Uname: Linux 3.18.0-13-generic x86_64 ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 CrashCounter: 1 Date: Tue Feb 24 18:09:32 2015 ExecutablePath: /usr/bin/unity8 InstallationDate: Installed on 2015-02-25 (0 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150224) ProcCmdline: unity8 SegvAnalysis: Segfault happened at: 0x7fb33b34c3a9 _IO_vfprintf_internal+5561: repnz scas %es:(%rdi),%al PC (0x7fb33b34c3a9) ok source %es:(%rdi) (0x) not located in a known VMA region (needed readable region)! destination %al ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11SourcePackage: unity8 StacktraceTop: _IO_vfprintf_internal (s=s@entry=0x7fb2ea5b69d0, format=optimized out, format@entry=0x7fb2f7a8f2d3 %s(%s:%s):, ap=ap@entry=0x7fb2ea5b6b08) at vfprintf.c:2039 __GI___vasprintf_chk (result_ptr=0x7fb2ea5b6be8, flags=1, format=0x7fb2f7a8f2d3 %s(%s:%s):, args=args@entry=0x7fb2ea5b6b08) at vasprintf_chk.c:66 __asprintf_chk (result_ptr=optimized out, flags=optimized out, format=optimized out) at asprintf_chk.c:32 pam_vsyslog () from /lib/x86_64-linux-gnu/libpam.so.0 pam_syslog () from /lib/x86_64-linux-gnu/libpam.so.0 Title: unity8 crashed with SIGSEGV in _IO_vfprintf_internal() 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/unity8/+bug/1425362/+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 1435368] [NEW] dh_apparmor does not assist postinst scripts that need to run the constrained binary before the postinst completes
Public bug reported: This affects mysql-5.6. mysql-server-5.6.postinst needs to run /usr/sbin/mysqld for bootstrapping purposes before starting the daemon proper. It calls dh_apparmor from dh_override_install in debian/rules. The profile for mysqld has changed between 5.5 and 5.6: it now permits read from /etc/mysql/**, since /etc/mysql/mysql.conf.d/ is now used in addition to the original /etc/mysql/my.cnf, along with some other files. On upgrade from the previous 5.5 packaging, mysql-server-5.6.postinst attempts to run /usr/sbin/mysqld which then fails because the old profile is still active, since dh_apparmor has only added the snippet to the end of the postinst (after this point). It appears to include some logic about /etc/apparmor.d/local/ which I can't easily call from earlier in the postinst instead. Workaround: I added an extra apparmor_parser call when I need it. But this fails if /etc/apparmor.d/local/usr.sbin.mysqld doesn't exist, which is the case on first install of the package. So I have to ignore errors. This isn't ideal though. It would be better if we could somehow arrange dh_apparmor to ensure that the apparmor profile is active earlier, or at least define some way that the maintainer's postinst code can make it happen earlier - for example by wrapping the logic into something the maintainer can call. Or perhaps dh_apparmor should unload the profile in the prerm or something, so that the postinst always runs without the profile loaded (as already happens on first install). ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New -- 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/1435368 Title: dh_apparmor does not assist postinst scripts that need to run the constrained binary before the postinst completes Status in apparmor package in Ubuntu: New Bug description: This affects mysql-5.6. mysql-server-5.6.postinst needs to run /usr/sbin/mysqld for bootstrapping purposes before starting the daemon proper. It calls dh_apparmor from dh_override_install in debian/rules. The profile for mysqld has changed between 5.5 and 5.6: it now permits read from /etc/mysql/**, since /etc/mysql/mysql.conf.d/ is now used in addition to the original /etc/mysql/my.cnf, along with some other files. On upgrade from the previous 5.5 packaging, mysql-server-5.6.postinst attempts to run /usr/sbin/mysqld which then fails because the old profile is still active, since dh_apparmor has only added the snippet to the end of the postinst (after this point). It appears to include some logic about /etc/apparmor.d/local/ which I can't easily call from earlier in the postinst instead. Workaround: I added an extra apparmor_parser call when I need it. But this fails if /etc/apparmor.d/local/usr.sbin.mysqld doesn't exist, which is the case on first install of the package. So I have to ignore errors. This isn't ideal though. It would be better if we could somehow arrange dh_apparmor to ensure that the apparmor profile is active earlier, or at least define some way that the maintainer's postinst code can make it happen earlier - for example by wrapping the logic into something the maintainer can call. Or perhaps dh_apparmor should unload the profile in the prerm or something, so that the postinst always runs without the profile loaded (as already happens on first install). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1435368/+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 1427187] Re: [Wizard] Language dropdown widget changes style after selection
I can reproduce on RTM too. ** Tags removed: vivid-stab-candidate -- 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/1427187 Title: [Wizard] Language dropdown widget changes style after selection Status in unity8 package in Ubuntu: Triaged Bug description: Test case. - Run the wizard. - Go to the language selection page. - Tap to open the list. - Select a language (e.g Spanish). Expected result. - Language is selected and dropdown widget doesn't change its style. Actual result. - After language is selected, widget changes its style. For a moment, the list is no longer transparent, but gray. See screenshot. current build number: 129 device name: krillin channel: ubuntu-touch/devel-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1427187/+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 1404762] Re: apparmor profile usr.sbin.clamd does not allow ScanOnAccess via fanotify
some further info: I now have installed auditd to have the log in /var/log/audit/audit.log. I added to usr.bin.clamd: capability setgid, capability setuid, and used aa-logprof to add some more items: capability chown, capability dac_override, capability fsetid, capability sys_admin, But, after reload apparmor, aa-enforce clamd, and restart clamd I still have ERROR: initgroups() failed at clamd start. It still needs aa-complain clamd to successfully start clamd -- 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/1404762 Title: apparmor profile usr.sbin.clamd does not allow ScanOnAccess via fanotify Status in apparmor package in Ubuntu: Confirmed Bug description: I tried to enable the ScanOnAccess option in /etc/clamav.conf to get on-access scanning. Doing so, /var/log/clamav/clamav.log tells me: ERROR: ScanOnAccess: fanotify_init failed: Operation not permitted ScanOnAccess: clamd must be started by root Setting User to root in /etc/clamav/clamd.conf makes the clamav-daemon to fail with service clamav-daemon start * Starting ClamAV daemon clamd ERROR: initgroups() failed. I had to disable the apparmor.profile with a cd /etc/apparmor.d/disable ln -s ./../usr.sbin.clamd Then, the ERROR: initgroups() failed. disappears. The apparmor itself came via apt-get packages. I did not edit it. Description: Ubuntu 14.04.1 LTS Release: 14.04 apt-cache policy apparmor-profiles apparmor-profiles: Installiert: (keine) Installationskandidat: 2.8.95~2430-0ubuntu5.1 Versionstabelle: 2.8.95~2430-0ubuntu5.1 0 500 http://de.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 2.8.95~2430-0ubuntu5 0 500 http://de.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apparmor-profiles (not installed) ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 Date: Mon Dec 22 01:23:04 2014 InstallationDate: Installed on 2014-11-29 (22 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) ProcEnviron: LANGUAGE=de_DE TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdline: BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-43-generic root=UUID=6408c2d9-1b60-43d7-9a7f-2dceeb40de28 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: apparmor Syslog: UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1404762/+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 1434712] Re: Can't swipe from the right in the setup at first launch
** Branch linked: lp:~mterry/unity8/skip-spread-tutorial-on-desktop -- 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/1434712 Title: Can't swipe from the right in the setup at first launch Status in unity8 package in Ubuntu: Triaged Bug description: Ubuntu 15.04 on a desktop pc with a mouse. Version 8.02+15.04.20150318-0ubuntu1 of the unity8 package. The initial setup when first launching is stuck. Swiping the app launcher from the left works fine, but swiping the app switcher from the right won't work. It's stuck at the screen that says To view open apps Long swipe from the right edge. with an unresponsive wobbly switcher to the right. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1434712/+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 1421623] Re: Welcome wizard claims GPS is less accurate than wifi based location
GPS is most accurate positioning system we have on the phone. However it comes with price, here are some of the bad features of GPS: drains battery, does not work indoors, takes long to get initial location when used first time (or long after last use) Therefore number of supporting used to leverage those bad features of GPS, however those other technologies come at the price. Namely network based location (wifi, GSM cells) is faster and less power hungry than GPS, but it has lot worse accuracy. HERE location service uses network based location in order to show user coarse location quickly, while GPS is working on the background to acquire precise location. This can be observer in here maps when actual circle representing accuracy shrinks in the moment GPS location is acquired. In short we get between 1m to 15m for GPS location, based on number of visible satellites. but 25m to 30km! accuracy for network based location. 30km is extreme with no visible wifi and only one visible GSM cell tower. Still valid example. -- 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/1421623 Title: Welcome wizard claims GPS is less accurate than wifi based location Status in the base for Ubuntu mobile products: New Status in Ubuntu UX bugs: Triaged Status in ubuntu-system-settings package in Ubuntu: Invalid Status in unity8 package in Ubuntu: New Bug description: First boot welcome wizard in location sections claims GPS is less accurate than network based location service from HERE. While this can be theoretically true in some insane corner case, in normal life GPS is far more accurate. To help form correct text here are main differences. GPS - more accurate, but slow to acquire fix, does not work indoors, drains battery more, no need for internet connection, does not send any data out. Network based location - almost instant to get coarse location, works indoors, accuracy depends on network coverage in the area, more power efficient, requires internet connection. To get location data about visible GSM network and wifi networks needs to be send to 3rd party server. tested on krillin vivid-proposed r107 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1421623/+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 1366351] Re: compiz crashed with SIGSEGV in g_closure_invoke() if unity-settings-daemon goes away
I'm still getting this issue, every time the computer turns on. This is Ubunutu 14.04.1 . Attached is my unity7.log . Let me know if there's anything I can do to help ** Attachment added: unity7.log.1.gz https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1366351/+attachment/4353379/+files/unity7.log.1.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1366351 Title: compiz crashed with SIGSEGV in g_closure_invoke() if unity-settings- daemon goes away Status in Compiz: Invalid Status in Unity: Fix Released Status in compiz package in Ubuntu: Invalid Status in unity package in Ubuntu: Fix Released Bug description: Compiz crashes when unity-settings-daemon goes away. Simple reproducer: killall -SEGV unity-settings-daemon. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: compiz-core 1:0.9.12+14.10.20140812-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-13.19-generic 3.16.1 Uname: Linux 3.16.0-13-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Sep 6 10:48:43 2014 Disassembly: = 0x0: Cannot access memory at address 0x0 DistUpgraded: 2014-09-01 18:03:23,330 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu ExecutablePath: /usr/bin/compiz GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Curacao XT [Radeon R9 270X] [1002:6810] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:04a1] InstallationDate: Installed on 2014-03-24 (166 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: MSI MS-7640 ProcCmdline: compiz ProcEnviron: PATH=(custom, no user) SHELL=/bin/bash LD_LIBRARY_PATH=set LANG=en_US.UTF-8 XDG_RUNTIME_DIR=set ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-13-generic root=UUID=2696ea28-d88b-431c-a1fa-1e0f297ee664 ro quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x0: Cannot access memory at address 0x0 PC (0x) not located in a known VMA region (needed executable region)! SegvReason: executing NULL VMA Signal: 11 SourcePackage: compiz StacktraceTop: ?? () g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: compiz crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: Upgraded to utopic on 2014-09-01 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 10/31/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.15 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 890FXA-GD70 (MS-7640) 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.:bvrV1.15:bd10/31/2012:svnMSI:pnMS-7640:pvr1.0:rvnMSI:rn890FXA-GD70(MS-7640):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7640 dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz 1:0.9.12+14.10.20140812-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.6-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.6-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sat Sep 6 10:48:05 2014 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:
[Touch-packages] [Bug 1387691] Re: Media Player should not be visible in the app scope and launcher
The problem with the OnlyShowIn approach is that it is going to create a really odd user experience. Should the app show up in the Launcher? What about the application spread? What if someone pins it on the launcher? Providing something that is both an application in some states but not others is only a route to confusing the user. Along with that, it's really not where we want to go long term. We want to move towards more helpers and less applications for this type of functionality. It breaks the architecture that we're trying to build. I think that CI Train has taught us how long temporary fixes can burn us :-) Perhaps there is a middle ground on trusted session splash screens where it could be at least a black screen so the user can tell *something* is happening. -- 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/1387691 Title: Media Player should not be visible in the app scope and launcher Status in the base for Ubuntu mobile products: In Progress Status in Ubuntu UX bugs: Fix Committed Status in mediaplayer-app package in Ubuntu: In Progress Status in unity8 package in Ubuntu: Invalid Status in url-dispatcher package in Ubuntu: In Progress Status in mediaplayer-app package in Ubuntu RTM: In Progress Status in url-dispatcher package in Ubuntu RTM: In Progress Bug description: The mediaplayer is an 'auxiliary app' in the current design approach. That means that its purpouse it playback media launched by other apps (e.g Messaging) or scopes (e.g. Videos). It should not be launched from the App scopes. However, the 'Update' section System Settings should still display it when an update to mediaplayer is available. Current behaviour - Mediaplayer app displayed in App Scope, Launcher and Settings Desired behaviour - Mediaplayer app not displayed in App Scope or Launcher - Mediaplayer displayed in Settings Update To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1387691/+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 1388278] Re: WiFi randomly disconnects and won't connect again
It's upsetting that I still get this issue :( -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wireless-tools in Ubuntu. https://bugs.launchpad.net/bugs/1388278 Title: WiFi randomly disconnects and won't connect again Status in Broadcom 802.11 Linux STA driver: New Status in The Linux Kernel: New Status in The Linux Mint Distribution: Confirmed Status in LinuxMint Control Center: Confirmed Status in Network Manager GNOME Applet: New Status in Additional Linux Wireless Drivers: Confirmed Status in Wireless Tools - Tools for manipulating Linux Wireless Extensions: New Status in wireless-tools package in Ubuntu: Confirmed Bug description: Something odd that I have only seen in Ubuntu, Debian, and derivatives thereof affects something that most of us use every day, and can be a real hassle to beginners from what I've noticed: Many USB WiFi drivers will connect to an access point like usual and after long periods of inactivity on the network combined with user inactivity on the PC alone is when this problem appears to arise: The WiFi disconnects and does not connect again to the same hotspot using the same USB WiFi dongle unless the computer is restarted or reset, and a lot of the time, that doesn't immediately stop this error and even if so, the computer will disconnect yet again not too long from then. And why does this happen? It puzzles me. Maybe it's the USB chipset inside the WiFi dongle, or maybe it's a communication error between the Linux kernel and the automated firewall systems integrated in most routers and base stations today, it's hard to say. What I know is that this doesn't just happen on my computer, testing done by myself on several other computers in different locations using different WiFi hardware on Ubuntu, Debian, Linux Mint, or derivatives thereof gets the exact same result as I am experiencing now. I have gone digging through Debian, Ubuntu, and Linux Mint forums to try and find the cure patch for my computer or router and the answer as to why this is happening, and the best answer I could find is that within my system's WiFi Settings, I need to set the BSSID of the hotspot I am current using as the MAC address of the router which that hotspot is transmitting. Upon setting my BSSID to a clone of the Router's MAC address followed by a system restart, I noticed instant improvement when it comes to connection reliability, speed, and time to connect, yet after days of having that MAC as the BSSID, things went back to the usual chaos of an unreliable connection that no other device within the household has encountered, not even Android telephones and tablets that use much of the same underlying Linux code. I performed restarts, updates, more updates, resets, and even more derivatives of Debian or Ubuntu and this is still more of an issue than ever. Via further digging and through a process of trial-and-error, I enabled the IPv4 is required for this connection check box along with changing the BSSID to a clone of the router's MAC address in hopes it was a compatibility issue with the newer IPv6 Internet Protocol architecture in an attempt to basically 'force' the machine to get that digital handshake with the router in a more 'legacy' mode with IPv4, at least to get some connection. That worked for a bit as well, but didn't hold up just like before. I am now sitting here at my computer, still experiencing this issue on and off, currently having the issue stabilized and stalled at the moment with the IPv4 is required for this connection check box on, NO BSSID set, NO cloned MAC address, and NO Restrict to Device settings opted-in, hoping this time around this combination of settings will work, but it's a game of trial-and-error for me at this point now, like mentioned before. Has anyone else experienced such terrible connectivity issues only in Debian-based distributions recently? I have been using Linux for ages now and I feel as if this issue is now just arising within the past year, 2014. A HardInfo report generated from my computer is attached to this bug report. I hope we can figure out a solution soon to get pushed to all Debian and Debian-like distros soon! Nobody wants a bad connection. Current OS: Linux Mint 17 Qiana Kernel: Linux 3.13.0-24-generic (x86_64) Processor: AMD Phenom II X4 (850) RAM: 8GB DDR3 IWLIST OUTPUT: jeb@MINT-PARTITION:~ sudo iwlist wlan0 scan [sudo] password for jeb: wlan0 Scan completed : Cell 01 - Address: F8:7B:8C:06:57:8D Channel:6 Frequency:2.437 GHz (Channel 6) Quality=60/70 Signal level=-50 dBm Encryption key:on ESSID:Belkin-EXT Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
[Touch-packages] [Bug 1435353] [NEW] fix patch build failure in trusty
Public bug reported: seen in a test rebuild with a modified toolchain, and in a clean trusty environment = All 34 tests behaved as expected (1 expected failure) = make[5]: Leaving directory `/build/buildd/patch-2.7.1/tests' make[4]: Leaving directory `/build/buildd/patch-2.7.1/tests' make[3]: Leaving directory `/build/buildd/patch-2.7.1/tests' make[3]: Entering directory `/build/buildd/patch-2.7.1' make[3]: Leaving directory `/build/buildd/patch-2.7.1' make[2]: Leaving directory `/build/buildd/patch-2.7.1' make[1]: Leaving directory `/build/buildd/patch-2.7.1' # make sure we call ed as ed [ $(strings -n 2 src/patch | grep -w 'ed$') = ed ] make: *** [build-stamp] Error 1 dpkg-buildpackage: error: debian/rules build gave error exit status 2 As pointed out in https://bugs.debian.org/729132, the ed strings is found more than once for some builds, so just check the config file for the name of ed. The fix is already in current Ubuntu releases To validate; Check that the package builds, and passes the tests. ** Affects: patch (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: patch (Ubuntu Trusty) Importance: Undecided Status: Confirmed ** Tags: ftbfs ** Also affects: patch (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: patch (Ubuntu Trusty) Status: New = Confirmed ** Changed in: patch (Ubuntu Trusty) Milestone: None = trusty-updates ** Changed in: patch (Ubuntu) Status: Confirmed = Fix Released ** Changed in: patch (Ubuntu) Milestone: trusty-updates = None -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to patch in Ubuntu. https://bugs.launchpad.net/bugs/1435353 Title: fix patch build failure in trusty Status in patch package in Ubuntu: Fix Released Status in patch source package in Trusty: Confirmed Bug description: seen in a test rebuild with a modified toolchain, and in a clean trusty environment = All 34 tests behaved as expected (1 expected failure) = make[5]: Leaving directory `/build/buildd/patch-2.7.1/tests' make[4]: Leaving directory `/build/buildd/patch-2.7.1/tests' make[3]: Leaving directory `/build/buildd/patch-2.7.1/tests' make[3]: Entering directory `/build/buildd/patch-2.7.1' make[3]: Leaving directory `/build/buildd/patch-2.7.1' make[2]: Leaving directory `/build/buildd/patch-2.7.1' make[1]: Leaving directory `/build/buildd/patch-2.7.1' # make sure we call ed as ed [ $(strings -n 2 src/patch | grep -w 'ed$') = ed ] make: *** [build-stamp] Error 1 dpkg-buildpackage: error: debian/rules build gave error exit status 2 As pointed out in https://bugs.debian.org/729132, the ed strings is found more than once for some builds, so just check the config file for the name of ed. The fix is already in current Ubuntu releases To validate; Check that the package builds, and passes the tests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/patch/+bug/1435353/+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 1311316] Re: After locking screen there is no input field to type password for unlock
So: $ dpkg -l unity Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-=-===-===-=== ii unity 7.2.3+14.04.2014082 amd64 Interface designed for efficiency of space and interaction. And yet I still have the bug. Should it be reopened? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: Fix Released Status in Unity 7.2 series: Fix Released Status in unity package in Ubuntu: Fix Released Bug description: *** IMPORTANT ** *** The fix is not included in TRUSTY. Will be included with next SRU. *** If you can reproduce this bug please be sure to provide the following info: 1. Do you use a multi-head setup? If yes, using just one monitor fixes the issue? 2. Can you reproduce all the time? 3. Do you use ldap? If yes, using gnome-screensaver fix the issue (see comment #115) can you still reproduce that? 4. Please consider posting /var/log/auth.log (at least part of it, should not contain sensitive information) 5. Please specify the unity version *** END IMPORTANT ** Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+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 1435337] [NEW] Answering sms's from Notifications doesn't send message
Public bug reported: When an sms arrives you can go to the left most Tab named 'Notifications' to see them. When you click on that message you can type a reply, and then click the green send button. However, those messages never get sent Using Ubuntu Touch on the bq device. Apparently according to the about the version is r20 ** Affects: messaging-app (Ubuntu) Importance: Undecided Status: New ** Tags: avengers -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1435337 Title: Answering sms's from Notifications doesn't send message Status in messaging-app package in Ubuntu: New Bug description: When an sms arrives you can go to the left most Tab named 'Notifications' to see them. When you click on that message you can type a reply, and then click the green send button. However, those messages never get sent Using Ubuntu Touch on the bq device. Apparently according to the about the version is r20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1435337/+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 1301394] Re: Launcher damange the left-monitor area also if it's hidden
** Changed in: unity Assignee: Marco Trevisan (Treviño) (3v1n0) = Andrea Azzarone (azzar1) ** Changed in: unity (Ubuntu) Assignee: (unassigned) = Andrea Azzarone (azzar1) ** Changed in: unity Status: Triaged = In Progress ** Changed in: unity (Ubuntu) Status: Confirmed = In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1301394 Title: Launcher damange the left-monitor area also if it's hidden Status in Unity: In Progress Status in unity package in Ubuntu: In Progress Bug description: When in auto-hide mode the launcher damages the area that it would fill when shown, also when hidden. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1301394/+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 1435186] Re: valgrind on armhf fails with with many errors
** Changed in: mir Assignee: (unassigned) = Alexandros Frantzis (afrantzis) ** Changed in: mir Status: New = In Progress -- 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/1435186 Title: valgrind on armhf fails with with many errors Status in Mir: In Progress Status in mir package in Ubuntu: New Bug description: Valgrind is now failing on armhf. Both in CI and when tested manually. This is the first and most obvious error, but there are more... [ RUN ] UdevWrapperDeathTest.DereferencingEndReturnsInvalidObject ==10542== Invalid write of size 4 ==10542==at 0x4ECA00C: ??? (in /lib/arm-linux-gnueabihf/libc-2.21.so) ==10542== Address 0xbdbafa88 is on thread 1's stack ==10542== 16 bytes below stack pointer ==10542== ==10542== Conditional jump or move depends on uninitialised value(s) ==10542==at 0x4ECA118: __udivmoddi4 (in /lib/arm-linux-gnueabihf/libc-2.21.so) ==10542== ==10542== Use of uninitialised value of size 4 ==10542==at 0x4ECA11A: __udivmoddi4 (in /lib/arm-linux-gnueabihf/libc-2.21.so) ==10542== ==10542== Use of uninitialised value of size 4 ==10542==at 0x4ECA018: ??? (in /lib/arm-linux-gnueabihf/libc-2.21.so) ==10542== ==10611== ==10611== Process terminating with default action of signal 11 (SIGSEGV) ==10611== Bad permissions for mapped region at address 0x2CDA000 ==10611==at 0x2CDA000: ??? (in /home/phablet/mir/dev/bin/.mir_unit_tests-uninstalled) ==10611== ==10611== HEAP SUMMARY: ==10611== in use at exit: 392,022 bytes in 7,695 blocks ==10611== total heap usage: 19,288 allocs, 11,593 frees, 1,117,616 bytes allocated ==10611== ==10611== LEAK SUMMARY: ==10611==definitely lost: 0 bytes in 0 blocks ==10611==indirectly lost: 0 bytes in 0 blocks ==10611== possibly lost: 137,447 bytes in 3,483 blocks ==10611==still reachable: 254,507 bytes in 4,211 blocks ==10611== suppressed: 0 bytes in 0 blocks ==10611== Reachable blocks (those to which a pointer was found) are not shown. ==10611== To see them, rerun with: --leak-check=full --show-leak-kinds=all ==10611== ==10611== For counts of detected and suppressed errors, rerun with: -v ==10611== Use --track-origins=yes to see where uninitialised values come from ==10611== ERROR SUMMARY: 55 errors from 4 contexts (suppressed: 6 from 6) To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1435186/+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 1435334] Re: mirror protocol breaks pinning
possibly related: https://bugs.debian.org/701564 ** Bug watch added: Debian Bug tracker #701564 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701564 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1435334 Title: mirror protocol breaks pinning Status in apt package in Ubuntu: New Bug description: I switched all Ubuntu related feeds from the standard http protocol to the mirror protocol deb mirror://oss.leggewie.org/ubuntu-mirrors.php trusty-proposed main That broke my pinning, especially to prevent automatic installations from -proposed and -backports. +--[ /etc/apt/preferences ] | | ## PIN by release ## | Package: * | Pin: release a=*-proposed | Pin-Priority: 98 | | Package: * | Pin: release a=*-backports | Pin-Priority: 97 | +-- This would no longer pin down -proposed and -backports. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1435334/+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 1423185] Re: Calendar app crash
ok to land this crasher fix ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Changed in: canonical-devices-system-image Importance: Undecided = High ** Changed in: canonical-devices-system-image Status: New = In Progress ** Changed in: canonical-devices-system-image Milestone: None = ww13-ota -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtorganizer5-eds in Ubuntu. https://bugs.launchpad.net/bugs/1423185 Title: Calendar app crash Status in the base for Ubuntu mobile products: In Progress Status in Calendar application for Ubuntu devices: In Progress Status in qtorganizer5-eds package in Ubuntu: Fix Released Bug description: Tapping on a day in Year view, crashed calendar app. See attached file. TEST CASE: 1. Switch to 'Year' view 2. Tap on any day 3. Repeat steps 1 and 2 up to 10 times ACTUAL RESULT The app crashes after a few attempts To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1423185/+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 1311316] Re: After locking screen there is no input field to type password for unlock
@Jonathan do you have light-locker installed? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: Fix Released Status in Unity 7.2 series: Fix Released Status in unity package in Ubuntu: Fix Released Bug description: *** IMPORTANT ** *** The fix is not included in TRUSTY. Will be included with next SRU. *** If you can reproduce this bug please be sure to provide the following info: 1. Do you use a multi-head setup? If yes, using just one monitor fixes the issue? 2. Can you reproduce all the time? 3. Do you use ldap? If yes, using gnome-screensaver fix the issue (see comment #115) can you still reproduce that? 4. Please consider posting /var/log/auth.log (at least part of it, should not contain sensitive information) 5. Please specify the unity version *** END IMPORTANT ** Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+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 1435334] [NEW] mirror protocol breaks pinning
Public bug reported: I switched all Ubuntu related feeds from the standard http protocol to the mirror protocol deb mirror://oss.leggewie.org/ubuntu-mirrors.php trusty-proposed main That broke my pinning, especially to prevent automatic installations from -proposed and -backports. +--[ /etc/apt/preferences ] | | ## PIN by release ## | Package: * | Pin: release a=*-proposed | Pin-Priority: 98 | | Package: * | Pin: release a=*-backports | Pin-Priority: 97 | +-- This would no longer pin down -proposed and -backports. ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Tags: regression-release trusty ** Tags added: regression-release ** Description changed: I switched all Ubuntu related feeds from the standard http protocol to the mirror protocol deb mirror://oss.leggewie.org/ubuntu-mirrors.php trusty-proposed main - restricted universe multiverse That broke my pinning, especially to prevent automatic installations from -proposed and -backports. +--[ /etc/apt/preferences ] | | ## PIN by release ## | Package: * | Pin: release a=*-proposed | Pin-Priority: 98 | | Package: * | Pin: release a=*-backports | Pin-Priority: 97 | +-- This would no longer pin down -proposed and -backports. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1435334 Title: mirror protocol breaks pinning Status in apt package in Ubuntu: New Bug description: I switched all Ubuntu related feeds from the standard http protocol to the mirror protocol deb mirror://oss.leggewie.org/ubuntu-mirrors.php trusty-proposed main That broke my pinning, especially to prevent automatic installations from -proposed and -backports. +--[ /etc/apt/preferences ] | | ## PIN by release ## | Package: * | Pin: release a=*-proposed | Pin-Priority: 98 | | Package: * | Pin: release a=*-backports | Pin-Priority: 97 | +-- This would no longer pin down -proposed and -backports. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1435334/+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 1301394] Re: Launcher damange the left-monitor area also if it's hidden
** Branch linked: lp:~azzar1/unity/fix-1301394 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1301394 Title: Launcher damange the left-monitor area also if it's hidden Status in Unity: In Progress Status in unity package in Ubuntu: In Progress Bug description: When in auto-hide mode the launcher damages the area that it would fill when shown, also when hidden. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1301394/+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 1311316] Re: After locking screen there is no input field to type password for unlock
And btw do you need 7.2.4+14.04.20141217-0ubuntu1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: Fix Released Status in Unity 7.2 series: Fix Released Status in unity package in Ubuntu: Fix Released Bug description: *** IMPORTANT ** *** The fix is not included in TRUSTY. Will be included with next SRU. *** If you can reproduce this bug please be sure to provide the following info: 1. Do you use a multi-head setup? If yes, using just one monitor fixes the issue? 2. Can you reproduce all the time? 3. Do you use ldap? If yes, using gnome-screensaver fix the issue (see comment #115) can you still reproduce that? 4. Please consider posting /var/log/auth.log (at least part of it, should not contain sensitive information) 5. Please specify the unity version *** END IMPORTANT ** Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+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 1311316] Re: After locking screen there is no input field to type password for unlock
And btw you need 7.2.4+14.04.20141217-0ubuntu1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: Fix Released Status in Unity 7.2 series: Fix Released Status in unity package in Ubuntu: Fix Released Bug description: *** IMPORTANT ** *** The fix is not included in TRUSTY. Will be included with next SRU. *** If you can reproduce this bug please be sure to provide the following info: 1. Do you use a multi-head setup? If yes, using just one monitor fixes the issue? 2. Can you reproduce all the time? 3. Do you use ldap? If yes, using gnome-screensaver fix the issue (see comment #115) can you still reproduce that? 4. Please consider posting /var/log/auth.log (at least part of it, should not contain sensitive information) 5. Please specify the unity version *** END IMPORTANT ** Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+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 1425297] Re: Sometimes indicator-datetime is not available in the UI after a reboot
This has been in RTM silo 4 since the 18th and is waiting on QA signoff. I'll ping QA and see if we can get this landed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1425297 Title: Sometimes indicator-datetime is not available in the UI after a reboot Status in the base for Ubuntu mobile products: In Progress Status in indicator-datetime package in Ubuntu: Fix Released Status in indicator-datetime package in Ubuntu RTM: In Progress Bug description: current build number: 110 device name: mako channel: ubuntu-touch/vivid-proposed last update: 2015-02-24 04:34:45 version version: 110 version ubuntu: 20150224 version device: 20150210 version custom: 20150224 See the attached picture. The only log entry I have for it: Indicator-Datetime-Message: static gboolean unity::indicator::datetime::LiveClock::Impl::on_timerfd_cond(gint, GIOCondition, gpointer) triggered at 2015-02-24 20:24:48.605449 by GIOCondition 1, read -1 bytes, found 0 interrupts To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1425297/+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 1433324] Re: provide whl packages in trusty to enable pyvenv in python3.4
wheel from utopic seems to build just fine in a trusty chroot. I then used that to build six 1.5.2-1ubuntu1 in trusty, and everything looked fine, including the six wheel. More to follow. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to chardet in Ubuntu. https://bugs.launchpad.net/bugs/1433324 Title: provide whl packages in trusty to enable pyvenv in python3.4 Status in chardet package in Ubuntu: Fix Released Status in distlib package in Ubuntu: Fix Released Status in html5lib package in Ubuntu: Fix Released Status in python-colorama package in Ubuntu: Fix Released Status in python-pip package in Ubuntu: Fix Released Status in python-scripttest package in Ubuntu: Fix Released Status in python-setuptools package in Ubuntu: Fix Released Status in python-urllib3 package in Ubuntu: Fix Released Status in requests package in Ubuntu: Fix Released Status in six package in Ubuntu: Fix Released Status in wheel package in Ubuntu: Fix Released Status in chardet source package in Trusty: New Status in distlib source package in Trusty: New Status in html5lib source package in Trusty: New Status in python-colorama source package in Trusty: New Status in python-pip source package in Trusty: New Status in python-scripttest source package in Trusty: New Status in python-setuptools source package in Trusty: New Status in python-urllib3 source package in Trusty: New Status in requests source package in Trusty: New Status in six source package in Trusty: New Status in wheel source package in Trusty: New Bug description: to enable pyvenv in trusty, we need a number of -whl packages in trusty. For the normal case, this is just adding a new separate binary package, sometimes the build system needs to use setuptools. Other needed changes are described below. The python3.4 update is tracked in lp: #1348954. test criterium for accepting these packages should be a successful build, a check that the original packages are not modified, and the new packages are not empty. The version number may be sometimes odd looking. Packages were prepared in the ubuntu-toolchain-r/ppa, and I'd like to use version number higher than in this PPA. wheel: wheel is not part of trusty, so just take the first upload to utopic. six: Build a -whl package (setuptools is needed to build the wheel package). chardet: 2.0.1 in trusty is not ready for Python3. Backport the package from utopic (source name chardet-whl), and just build the python3-chardet and python-chardet-whl packages (both new in trusty). distlib: Build a -whl package (setuptools is needed to build the wheel package). html5lib: Build a -whl package (setuptools is needed to build the wheel package). Just use the packaging of the next Debian version. python-colorama: Build a -whl package (setuptools is needed to build the wheel package). python-urllib3: Build using setuptools and build a wheel package. Additional patch to not rely on ssl.PROTOCOL_SSLv3 being defined. requests: Build a -whl package python-setuptools: Build a -whl package, and fix an issue with installing the documentation. python-pip: Build a -whl package, don't require the new version of python-scripttest, build succeeds without it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chardet/+bug/1433324/+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 1433324] Re: provide whl packages in trusty to enable pyvenv in python3.4
wheel from utopic seems to build just fine in a trusty chroot. I then used that to build six 1.5.2-1ubuntu1 in trusty, and everything looked fine, including the six wheel. More to follow. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to chardet in Ubuntu. https://bugs.launchpad.net/bugs/1433324 Title: provide whl packages in trusty to enable pyvenv in python3.4 Status in chardet package in Ubuntu: Fix Released Status in distlib package in Ubuntu: Fix Released Status in html5lib package in Ubuntu: Fix Released Status in python-colorama package in Ubuntu: Fix Released Status in python-pip package in Ubuntu: Fix Released Status in python-scripttest package in Ubuntu: Fix Released Status in python-setuptools package in Ubuntu: Fix Released Status in python-urllib3 package in Ubuntu: Fix Released Status in requests package in Ubuntu: Fix Released Status in six package in Ubuntu: Fix Released Status in wheel package in Ubuntu: Fix Released Status in chardet source package in Trusty: New Status in distlib source package in Trusty: New Status in html5lib source package in Trusty: New Status in python-colorama source package in Trusty: New Status in python-pip source package in Trusty: New Status in python-scripttest source package in Trusty: New Status in python-setuptools source package in Trusty: New Status in python-urllib3 source package in Trusty: New Status in requests source package in Trusty: New Status in six source package in Trusty: New Status in wheel source package in Trusty: New Bug description: to enable pyvenv in trusty, we need a number of -whl packages in trusty. For the normal case, this is just adding a new separate binary package, sometimes the build system needs to use setuptools. Other needed changes are described below. The python3.4 update is tracked in lp: #1348954. test criterium for accepting these packages should be a successful build, a check that the original packages are not modified, and the new packages are not empty. The version number may be sometimes odd looking. Packages were prepared in the ubuntu-toolchain-r/ppa, and I'd like to use version number higher than in this PPA. wheel: wheel is not part of trusty, so just take the first upload to utopic. six: Build a -whl package (setuptools is needed to build the wheel package). chardet: 2.0.1 in trusty is not ready for Python3. Backport the package from utopic (source name chardet-whl), and just build the python3-chardet and python-chardet-whl packages (both new in trusty). distlib: Build a -whl package (setuptools is needed to build the wheel package). html5lib: Build a -whl package (setuptools is needed to build the wheel package). Just use the packaging of the next Debian version. python-colorama: Build a -whl package (setuptools is needed to build the wheel package). python-urllib3: Build using setuptools and build a wheel package. Additional patch to not rely on ssl.PROTOCOL_SSLv3 being defined. requests: Build a -whl package python-setuptools: Build a -whl package, and fix an issue with installing the documentation. python-pip: Build a -whl package, don't require the new version of python-scripttest, build succeeds without it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chardet/+bug/1433324/+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 1417037] Re: Upgrade to 7.4.4-1ubuntu2.5 hangs
Same problem here on 14.04.2, Andrei's comment did not help either: root@user:~# /bin/sh /var/lib/dpkg/info/rsyslog.postinst configure 7.4.4-1ubuntu2.3 The user `syslog' is already a member of `adm'. /usr/bin/deb-systemd-helper was not called from dpkg. Exiting. /usr/bin/deb-systemd-helper was not called from dpkg. Exiting. /usr/bin/deb-systemd-helper was not called from dpkg. Exiting. Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd invoke-rc.d: initscript rsyslog, action restart failed. root@user:~# apt-get -f install Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 15 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Setting up rsyslog (7.4.4-1ubuntu2.5) ... The user `syslog' is already a member of `adm'. Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd invoke-rc.d: initscript rsyslog, action restart failed. dpkg: error processing package rsyslog (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: rsyslog E: Sub-process /usr/bin/dpkg returned an error code (1) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1417037 Title: Upgrade to 7.4.4-1ubuntu2.5 hangs Status in rsyslog package in Ubuntu: Confirmed Bug description: I've just ran an update+dist-upgrade which pulled 7.4.4-1ubuntu2.5. It's sat there doing nothing. CTRL+C won't kill it. Htop shows that the last process to be created is stop rsyslog which follows invoke-rc.d rsyslog restart. dpkg.log: 2015-02-02 09:39:10 configure rsyslog:amd64 7.4.4-1ubuntu2.5 none 2015-02-02 09:39:10 status unpacked rsyslog:amd64 7.4.4-1ubuntu2.5 2015-02-02 09:39:10 status unpacked rsyslog:amd64 7.4.4-1ubuntu2.5 2015-02-02 09:39:10 status unpacked rsyslog:amd64 7.4.4-1ubuntu2.5 2015-02-02 09:39:10 status unpacked rsyslog:amd64 7.4.4-1ubuntu2.5 2015-02-02 09:39:10 status unpacked rsyslog:amd64 7.4.4-1ubuntu2.5 2015-02-02 09:39:10 status unpacked rsyslog:amd64 7.4.4-1ubuntu2.5 2015-02-02 09:39:10 status unpacked rsyslog:amd64 7.4.4-1ubuntu2.5 2015-02-02 09:39:10 status unpacked rsyslog:amd64 7.4.4-1ubuntu2.5 2015-02-02 09:39:10 status unpacked rsyslog:amd64 7.4.4-1ubuntu2.5 2015-02-02 09:39:10 status half-configured rsyslog:amd64 7.4.4-1ubuntu2.5 I have KILLed stop rsyslog which then moves on to start rsyslog which I have also had to KILL. Setting up rsyslog (7.4.4-1ubuntu2.5) ... The user `syslog' is already a member of `adm'. Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Terminated Terminated invoke-rc.d: initscript rsyslog, action restart failed. dpkg: error processing package rsyslog (--configure): subprocess installed post-installation script returned error exit status 143 Setting up linux-image-virtual-lts-utopic (3.16.0.30.23) ... Setting up linux-libc-dev:amd64 (3.13.0-45.74) ... Setting up python3-software-properties (0.92.37.3) ... Setting up software-properties-common (0.92.37.3) ... Errors were encountered while processing: rsyslog E: Sub-process /usr/bin/dpkg returned an error code (1) W: Operation was interrupted before it could finish ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: rsyslog 7.4.4-1ubuntu2.5 ProcVersionSignature: Ubuntu 3.16.0-29.39~14.04.1-generic 3.16.7-ckt2 Uname: Linux 3.16.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 Date: Mon Feb 2 09:43:26 2015 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rsyslog UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1417037/+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 1434143] Re: boot script should run aa-profile-hook in addition to aa-clickhook
Update of apparmor-easyprof-ubuntu-snappy should trigger running aa- clickhook. -- 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/1434143 Title: boot script should run aa-profile-hook in addition to aa-clickhook Status in Snappy Ubuntu: Triaged Status in apparmor package in Ubuntu: In Progress Bug description: Summary says it all. aa-profile-hook does the same sort of thing as aa-clickhook and is used on snappy. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy-ubuntu/+bug/1434143/+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 1367792] Re: In landscape mode, photo roll navigation is horizontal
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: camera-app (Ubuntu) Status: New = Confirmed -- 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/1367792 Title: In landscape mode, photo roll navigation is horizontal Status in Camera App: New Status in camera-app package in Ubuntu: Confirmed Bug description: 1. Open camera and take a photo in landscape mode 2. flick down to open Photo Roll 3. Flick down again What happens: Nothing What should happen: Next photo in photo roll should appear, while currently photo roll navigation is horizontal, it should be vertical if in landscape mode. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity8 8.00+14.10.20140908.1-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.7-0ubuntu2 Architecture: armhf Date: Wed Sep 10 19:29:53 2014 InstallationDate: Installed on 2014-09-10 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140910-020205) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1367792/+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 1367792] Re: In landscape mode, photo roll navigation is horizontal
If I am not wrong, this is an issue of this bug (see attached pictures took from krillin/rtm) : https://plus.google.com/u/0/+cmtarudy/posts/HPy8gWa3vLS Or should I open a new bug -- 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/1367792 Title: In landscape mode, photo roll navigation is horizontal Status in Camera App: New Status in camera-app package in Ubuntu: Confirmed Bug description: 1. Open camera and take a photo in landscape mode 2. flick down to open Photo Roll 3. Flick down again What happens: Nothing What should happen: Next photo in photo roll should appear, while currently photo roll navigation is horizontal, it should be vertical if in landscape mode. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity8 8.00+14.10.20140908.1-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.7-0ubuntu2 Architecture: armhf Date: Wed Sep 10 19:29:53 2014 InstallationDate: Installed on 2014-09-10 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140910-020205) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1367792/+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 1275684] Re: i915 driver/i945 hardware: mir_demo_client_eglplasma exits immediately and silently
Confirmed fixed on both machines when upgraded to the latest vivid with Mesa 10.5. They're hopelessly slow to run eglplasma, but they do run it. ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New ** Changed in: mesa (Ubuntu) Status: New = Fix Released ** Changed in: mesa (Ubuntu) Importance: Undecided = Low ** Changed in: mir Status: Triaged = 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/1275684 Title: i915 driver/i945 hardware: mir_demo_client_eglplasma exits immediately and silently Status in Mir: Invalid Status in mesa package in Ubuntu: Fix Released Bug description: On i945 systems (Pentium D and Atom N270 at least), mir_demo_client_eglplasma exits immediately, and silently. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1275684/+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 1430893] Re: [FFe] Install Fcitx for Chinese users
Fcitx is much better than Ibus. This is a good move. However, fcitx-m17n is not working. IBus-m17n works as expected. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1430893 Title: [FFe] Install Fcitx for Chinese users Status in im-config package in Ubuntu: Fix Released Status in language-selector package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Fix Released Bug description: There are currently two main supported input method frameworks available for CJK users: IBus (current default) and Fcitx. Both are mature projects, but Fcitx is better suited to Chinese users than IBus is, and is already the default in Ubuntu Kylin. IBus is increasingly moving in the direction of removing features upstream like tracking input state on a per-context basis. Also, the leading input method provider in China with more than 300 million users, Sogou, only supports Fcitx under Linux. Skinning support is non-existent in IBus. We've added support for Fcitx on the same level as IBus in Unity, so this FFe is a proposal to make Fcitx the default for Chinese locales this cycle, as a transition towards making Fcitx the default for all users next cycle. The changes should simply be seeding Fcitx and its related packages on the CD image, as well as possible changes to im- config. Those who have explicitly selected IBus as their chosen input method should be unaffected; these changes will only affect new users, and users who have never explicitly chosen an input method framework in their language settings. Also, this FFe propose to make language-selector to install more input method packages for Chinese users to their Fcitx equivalents (currently IBus) when adding/completing Chinese language support. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1430893/+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 1405349] Re: switching to activated guest session causes screen blank
Tested with latest Vivid 22-Mar-2015 image, this issue be reproduced too. ** Description changed: Hi, I switch to activated guest session, but the screen remains blank. I have to wake it up with keyboard/mouse action. How to reproduce: 1. login with your account normally. 2. switch to guest session from the panel menu Switch Account... - Guest Session, now it's under guest session and the display is normal. 3. switch back to your user account, then switch to guest session again. 4. The screen remains blank. - P.S: I can't reproduce this issue under Precise. + P.S: I can't reproduce this issue under Precise and Vivid. Package: lightdm 1.10.3-0ubuntu2 unity-settings-daemon-14.04.0+14.10.20140606~0ubuntu1 - --- + --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity DistributionChannelDescriptor: - # This is a distribution channel descriptor - # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor - canonical-oem-stella-datong140729-kylin-trusty-amd64-20150205-2 + # This is a distribution channel descriptor + # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor + canonical-oem-stella-datong140729-kylin-trusty-amd64-20150205-2 DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2015-02-09 (1 days ago) InstallationMedia: Ubuntu 14.04 Trusty - Build amd64 LIVE Binary 20150205-07:08 LightdmConfig: - [SeatDefaults] - autologin-guest=false - autologin-user-timeout=0 - autologin-session=lightdm-autologin + [SeatDefaults] + autologin-guest=false + autologin-user-timeout=0 + autologin-session=lightdm-autologin Package: lightdm 1.10.3-0ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.13.0-38.65stella1-generic 3.13.11.8 Tags: trusty third-party-packages Uname: Linux 3.13.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True ** Description changed: Hi, I switch to activated guest session, but the screen remains blank. I have to wake it up with keyboard/mouse action. How to reproduce: 1. login with your account normally. 2. switch to guest session from the panel menu Switch Account... - Guest Session, now it's under guest session and the display is normal. 3. switch back to your user account, then switch to guest session again. 4. The screen remains blank. - P.S: I can't reproduce this issue under Precise and Vivid. + I can't reproduce this issue under Precise. + Vivid snapshot 22-Mar-2015 can also reproduce this issue. Package: lightdm 1.10.3-0ubuntu2 unity-settings-daemon-14.04.0+14.10.20140606~0ubuntu1 --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-datong140729-kylin-trusty-amd64-20150205-2 DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2015-02-09 (1 days ago) InstallationMedia: Ubuntu 14.04 Trusty - Build amd64 LIVE Binary 20150205-07:08 LightdmConfig: [SeatDefaults] autologin-guest=false autologin-user-timeout=0 autologin-session=lightdm-autologin Package: lightdm 1.10.3-0ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.13.0-38.65stella1-generic 3.13.11.8 Tags: trusty third-party-packages Uname: Linux 3.13.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1405349 Title: switching to activated guest session causes screen blank Status in Light Display Manager: Confirmed Status in OEM Priority Project: Confirmed Status in OEM Priority Project trusty series: Confirmed Status in lightdm package in Ubuntu: Confirmed Status in lightdm source package in Trusty: New Bug description: Hi, I switch to activated guest session, but the screen remains blank. I have to wake it up with keyboard/mouse action. How to reproduce: 1. login with your account normally. 2. switch to guest session from the panel menu Switch Account... - Guest Session, now it's under guest session and the display is normal. 3. switch back to your user account, then switch to guest session again. 4. The screen remains blank. I can't reproduce this issue under Precise. Vivid snapshot 22-Mar-2015 can also reproduce this issue. Package: lightdm 1.10.3-0ubuntu2 unity-settings-daemon-14.04.0+14.10.20140606~0ubuntu1 --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity DistributionChannelDescriptor:
[Touch-packages] [Bug 1435452] Re: dh_apparmor has no dh sequencer support
Hey Robie, I'm not particularly clueful when it comes to debhelper, but I don't really see how to accomplish this given what knowledge dh_apparmor has/doesn't have. It needs to know what profile(s) to create a local file for, as well as to reload; this is why the --profile-name argument is required to be passed to dh_apparmor. I guess one possible way to do it would be to have an expected environment variable to look for, and have the function automatically inserted into the dh sequencer apply the profile based on that, but that wouldn't help the mysql case, as the sequenced dh_apparmor function wouldn't know to only apply the profile to the mysql-server-X.X package. Well, unless we got into complicated environment variables names or representations, which is even less appealing. I guess another option would be some sort of profile manifest file(s) (not easyprof json manifests, but something akin to the .install, .docs, or .manpages manifests). But I'm also not sure how to do so in a backwards compatible way. I'll give it some more thought. -- 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/1435452 Title: dh_apparmor has no dh sequencer support Status in apparmor package in Ubuntu: New Bug description: As dh_apparmor timing is critical (it must run before services are started with dh_installinit), it makes sense to provide direct dh sequencer support so that maintainers don't have to remember to run it directly, and cannot mistakenly call it at the wrong point, as happened with MySQL in bug 1421303). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1435452/+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 1435452] Re: dh_apparmor has no dh sequencer support
To clarify, I mean that the existing dh_apparmor needs to be passed the profile name and potentially the package name as well as it has no means currently of discerning what those might be, which means there's no current way to get around requiring the packager to manually add the dh_apparmor call to the override_dh_install: target. ** Changed in: apparmor (Ubuntu) Status: New = Confirmed -- 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/1435452 Title: dh_apparmor has no dh sequencer support Status in apparmor package in Ubuntu: Confirmed Bug description: As dh_apparmor timing is critical (it must run before services are started with dh_installinit), it makes sense to provide direct dh sequencer support so that maintainers don't have to remember to run it directly, and cannot mistakenly call it at the wrong point, as happened with MySQL in bug 1421303). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1435452/+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 1435342] Re: firefox fails to build in trusty-security on arm64
This bug was fixed in the package gcc-4.8 - 4.8.4-1ubuntu14 --- gcc-4.8 (4.8.4-1ubuntu14) vivid; urgency=medium * [AArch64] Fix output template for Scalar Neon-Neon register move. LP: #1435342. -- Matthias Klose d...@ubuntu.com Mon, 23 Mar 2015 21:18:00 +0100 ** Changed in: gcc-4.8 (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gcc-4.8 in Ubuntu. https://bugs.launchpad.net/bugs/1435342 Title: firefox fails to build in trusty-security on arm64 Status in firefox package in Ubuntu: Fix Released Status in gcc-4.8 package in Ubuntu: Fix Released Status in firefox source package in Trusty: New Status in gcc-4.8 source package in Trusty: New Bug description: see in http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test- rebuild-20150317-security-trusty.html currently can be worked around by building this file / directory with -O1 on arm64. forwarded to https://bugs.linaro.org/show_bug.cgi?id=1373 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1435342/+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 1422681] Re: split out upstart-sysv
This bug was fixed in the package autopkgtest - 3.12ubuntu1 --- autopkgtest (3.12ubuntu1) vivid; urgency=medium * use the upstart path to start an upstart ubuntu touch session (LP: #1422681) -- Didier Roche didro...@ubuntu.com Mon, 23 Mar 2015 18:42:25 +0100 ** Changed in: autopkgtest (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1422681 Title: split out upstart-sysv Status in autopkgtest package in Ubuntu: Fix Released Status in init-system-helpers package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in ubuntu-touch-meta package in Ubuntu: New Status in upstart package in Ubuntu: Fix Released Bug description: After switching to systemd permanently (apt get install systemd-sysv) and purging the now not needed upstart package, I tried to boot with the upstart fallback option in grub, just to find out it doesn't work. It looks like important init files are still in the upstart package instead of upstart-bin and should probably be moved there to keep the upstart fallback option working. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/1422681/+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 1188881] Re: /usr/bin/jackd:8:__udivdi3:Jack::JackFrameTimer::ResetFrameTime:Jack::JackEngineControl::NotifyXRun:Jack::JackEngine::NotifyXRun:Jack::JackDriver::NotifyXRun
This crash can't be found in the current Error Tracker database, presumably it is in one of the off-line ones. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/111 Title: /usr/bin/jackd:8:__udivdi3:Jack::JackFrameTimer::ResetFrameTime:Jack::JackEngineControl::NotifyXRun:Jack::JackEngine::NotifyXRun:Jack::JackDriver::NotifyXRun Status in jackd2 package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/bucket/?id=/usr/bin/jackd:8:__udivdi3:Jack::JackFrameTimer::ResetFrameTime:Jack::JackEngineControl::NotifyXRun:Jack::JackEngine::NotifyXRun:Jack::JackDriver::NotifyXRun To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/111/+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 927745] Re: UnityCore and lenses should provide default file icons
** Changed in: unity Milestone: 7.3.3 = None ** Tags added: backlog -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/927745 Title: UnityCore and lenses should provide default file icons Status in Unity: Triaged Status in unity package in Ubuntu: New Bug description: UnityCore should load a default file icon path from the .lens file for each lens lenses should be updated to include one client side should use that to update rendering To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/927745/+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 1406804] Re: Freezes when update to release 14.04 LTS
Gustavo Fumes Boni, as per http://www.asus.com/in/Motherboards/M2N68AM_SE2/HelpDesk_Download/ an update to your computer's buggy and outdated BIOS is available (1801). If you update to this following https://help.ubuntu.com/community/BIOSUpdate does it change anything? If it doesn't, could you please both specify what happened, and provide the output of the following terminal command: sudo dmidecode -s bios-version sudo dmidecode -s bios-release-date 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. As well, you don't have to create a new bug report. Once the BIOS is updated, and the information above is provided, then please mark this report Status New. Thank you for your understanding. ** Tags added: bios-outdated-1801 -- 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/1406804 Title: Freezes when update to release 14.04 LTS Status in xorg package in Ubuntu: Incomplete Bug description: When updated to release 14.04 LTS something is not working properly, the PC freezes after login and after a few minutes the screen shows crazy colors. I tried it a lot of times, downloading the iso file a few times to check if anything got corrupted. I had to reinstall release 12.04 LTS back. Last note, release 14 freezes even when I lounch live CD, not only installing. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: update-manager 1:0.156.14.17 ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Wed Dec 31 17:31:37 2014 GsettingsChanges: com.ubuntu.update-manager check-new-release-ignore 'trusty' com.ubuntu.update-manager first-run false com.ubuntu.update-manager launch-time 1420053951 InstallationMedia: Ubuntu 12.04.5 LTS Precise Pangolin - Release amd64 (20140807.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: update-manager Symptom: ubuntu-release-upgrader-core UpgradeStatus: No upgrade log present (probably fresh install) --- .proc.driver.nvidia.gpus.0: Error: [Errno 21] É um diretório: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.125 Mon Dec 1 19:58:28 PST 2014 GCC version: versão do gcc 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu17.8 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CurrentDmesg: [ 11.405490] forcedeth :00:07.0 eth0: MSI enabled [ 50.030311] audit_printk_skb: 171 callbacks suppressed [ 50.030316] type=1400 audit(1427111674.315:69): apparmor=DENIED operation=open profile=/usr/lib/telepathy/mission-control-5 name=/usr/share/gvfs/remote-volume-monitors/ pid=2150 comm=mission-control requested_mask=r denied_mask=r fsuid=1000 ouid=0 DistUpgraded: Fresh install DistroCodename: precise DistroRelease: Ubuntu 12.04 DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.125, 3.13.0-32-generic, x86_64: installed nvidia-304, 304.125, 3.13.0-43-generic, x86_64: installed nvidia-304, 304.125, 3.13.0-45-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:83a4] InstallationMedia: Ubuntu 12.04.5 LTS Precise Pangolin - Release amd64 (20140807.1) JockeyStatus: xorg:nvidia_304 - Driver de aceleração de vídeo NVIDIA (Proprietário, Habilitado, Em uso) xorg:nvidia_304_updates - Driver gráfico de aceleração NVIDIA (atualizações pós instalação) (Proprietário, Desativado, Não está em uso) Lsusb: Bus 002 Device 003: ID 1c4f:0003 SiGma Micro HID controller 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: System manufacturer System Product Name MarkForUpload: True NonfreeKernelModules: nvidia Package: xorg 1:7.6+12ubuntu2 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=pt_BR:pt:en TERM=xterm PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic
[Touch-packages] [Bug 1393169] Re: [Toshiba Satellite Pro C650] Double mouse cursor
PS : my touchpad doesnt work at all on my second install. On my first install, it didnt work well. -- 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/1393169 Title: [Toshiba Satellite Pro C650] Double mouse cursor Status in xorg package in Ubuntu: Incomplete Bug description: Last up to date Xubuntu 64 bits installed on a laptop Since 2 days, the mouse cursor is double with only the left part as active and a bar just behing of both arrow (see picture joined). I tried to change the theme but no way to go back to a normal mouse cursor Regards ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Nov 16 11:12:21 2014 InstallationDate: Installed on 2013-01-03 (681 days ago) InstallationMedia: Xubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.1) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: utopic DistroRelease: Ubuntu 14.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:fde0] Subsystem: Toshiba America Info Systems Device [1179:fde0] InstallationDate: Installed on 2013-01-03 (695 days ago) InstallationMedia: Xubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.1) LightdmGreeterLog: ** (lightdm-gtk-greeter:1659): WARNING **: Failed to load background: Impossible d'ouvrir le fichier « /home/christophe/Dropbox/Personnalisation/Fonds d'écran/bleu.jpg » : Permission non accordée ** (lightdm-gtk-greeter:1659): WARNING **: Failed to read wallpaper: /home/christophe/Dropbox/Personnalisation/Fonds d'écran/bleu.jpg g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. LightdmGreeterLogOld: ** (lightdm-gtk-greeter:1641): WARNING **: Failed to load background: Impossible d'ouvrir le fichier « /home/christophe/Dropbox/Personnalisation/Fonds d'écran/bleu.jpg » : Permission non accordée ** (lightdm-gtk-greeter:1641): WARNING **: Failed to read wallpaper: /home/christophe/Dropbox/Personnalisation/Fonds d'écran/bleu.jpg g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. MachineType: TOSHIBA Satellite Pro C650 Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-26-generic root=UUID=7bc86e4b-720d-4f1c-bb66-a4c08ffc1359 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-26.34-generic 3.16.7-ckt1 Tags: utopic ubuntu Uname: Linux 3.16.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/01/2010 dmi.bios.vendor: INSYDE dmi.bios.version: 1.30 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvr1.30:bd07/01/2010:svnTOSHIBA:pnSatelliteProC650:pvrPSC09E-00R01YMV:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Satellite Pro C650 dmi.product.version: PSC09E-00R01YMV dmi.sys.vendor: TOSHIBA version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Fri Nov 28 08:29:52 2014 xserver.configfile: default xserver.errors: xserver.logfile:
[Touch-packages] [Bug 1384357] Re: Current composition is not canceled when a text input field is cleared programmatically
It looks like the blink method we’re interested in listening to is called didUpdateTextOfFocusedElementByNonUserInput(). Apparently this will require patching content::RenderWidget, the current implementation does nothing if !defined(OS_ANDROID). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1384357 Title: Current composition is not canceled when a text input field is cleared programmatically Status in Oxide Webview: Confirmed Status in Ubuntu Keyboard: Invalid Status in Web Browser App: Invalid Status in webbrowser-app package in Ubuntu: Invalid Bug description: Using rtm 122 - start the webbrowser - go on google.com - type ubuntu in the google page text entry - tap the x symbol at the right of the entry - the entry is cleared and then the text is restored once you hit that issue, you can also hit another bug - type the delete key until emptying the entry, then another time - the text is restored and the delete key loop over the content To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1384357/+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 1393169] Re: [Toshiba Satellite Pro C650] Double mouse cursor
Hi have this problem. I wonder if that became when i started change size of the folders in /home (?) Others users here in french : http://forum.ubuntu-fr.org/viewtopic.php?id=1761131 2 installs by unetbootin on a EFI windows 8.1 on a laptop asus X751M :Xubuntu 64 12.04.2 How can i help sending a repport? -- 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/1393169 Title: [Toshiba Satellite Pro C650] Double mouse cursor Status in xorg package in Ubuntu: Incomplete Bug description: Last up to date Xubuntu 64 bits installed on a laptop Since 2 days, the mouse cursor is double with only the left part as active and a bar just behing of both arrow (see picture joined). I tried to change the theme but no way to go back to a normal mouse cursor Regards ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Nov 16 11:12:21 2014 InstallationDate: Installed on 2013-01-03 (681 days ago) InstallationMedia: Xubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.1) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: utopic DistroRelease: Ubuntu 14.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:fde0] Subsystem: Toshiba America Info Systems Device [1179:fde0] InstallationDate: Installed on 2013-01-03 (695 days ago) InstallationMedia: Xubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.1) LightdmGreeterLog: ** (lightdm-gtk-greeter:1659): WARNING **: Failed to load background: Impossible d'ouvrir le fichier « /home/christophe/Dropbox/Personnalisation/Fonds d'écran/bleu.jpg » : Permission non accordée ** (lightdm-gtk-greeter:1659): WARNING **: Failed to read wallpaper: /home/christophe/Dropbox/Personnalisation/Fonds d'écran/bleu.jpg g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. LightdmGreeterLogOld: ** (lightdm-gtk-greeter:1641): WARNING **: Failed to load background: Impossible d'ouvrir le fichier « /home/christophe/Dropbox/Personnalisation/Fonds d'écran/bleu.jpg » : Permission non accordée ** (lightdm-gtk-greeter:1641): WARNING **: Failed to read wallpaper: /home/christophe/Dropbox/Personnalisation/Fonds d'écran/bleu.jpg g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. MachineType: TOSHIBA Satellite Pro C650 Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-26-generic root=UUID=7bc86e4b-720d-4f1c-bb66-a4c08ffc1359 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-26.34-generic 3.16.7-ckt1 Tags: utopic ubuntu Uname: Linux 3.16.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/01/2010 dmi.bios.vendor: INSYDE dmi.bios.version: 1.30 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvr1.30:bd07/01/2010:svnTOSHIBA:pnSatelliteProC650:pvrPSC09E-00R01YMV:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Satellite Pro C650 dmi.product.version: PSC09E-00R01YMV dmi.sys.vendor: TOSHIBA version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel
[Touch-packages] [Bug 1424466] Update Released
The verification of the Stable Release Update for mesa has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1424466 Title: Devel package not installable in 14.04.2 (mesa-lts-utopic Status in mesa package in Ubuntu: Invalid Status in mesa source package in Trusty: Fix Released Bug description: [Impact] * Some -dev packages like ubuntu-sdk and libglew-dev cannot be installed when the lts-utopic stack is used. [Test Case] * Install the lts-utopic stack. * apt-get install ubuntu-sdk * Good: you get a whole list of packages to install. * Bad: apt-get install fails like pasted in the original bug report. * Also test the same without the lts-utopic stack, to make sure there are no regressions. [Regression Potential] * Low, this has been done for precise before, and mesa packaging has to be updated for every LTS release. Unfortunately there are no alternatives. :( [Other Info] * There's probably an apt bug in here too. Nudging the resolver by specifying libgl1-mesa-dev-lts-utopic and libgles2-mesa-dev-lts-utopic works, but I didn't find a good way to express this in the depends, and that would have to be done for every package. [Original bug report] Not the first, likely not the last devel to not be installable in 14.04.2 or any mesa-lts-utopic install Another one is libglew-dev sudo apt-get install freeglut3-dev 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: libcheese-gtk23 : Depends: libclutter-gtk-1.0-0 (= 0.91.8) but it is not going to be installed Depends: libcogl15 (= 1.15.8) but it is not going to be installed libcheese7 : Depends: libclutter-gst-2.0-0 (= 0.10.0) but it is not going to be installed Depends: gstreamer1.0-clutter but it is not going to be installed libclutter-1.0-0 : Depends: libcogl-pango15 (= 1.15.8) but it is not going to be installed Depends: libcogl15 (= 1.15.8) but it is not going to be installed ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: freeglut3-dev (not installed) ProcVersionSignature: Ubuntu 3.16.0-31.41~14.04.1-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 22 18:03:30 2015 InstallationDate: Installed on 2015-02-08 (14 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150203.2) SourcePackage: freeglut UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1424466/+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 1435324] Re: qtbase5-dev not installable on Ubuntu 14.04 LTS
*** This bug is a duplicate of bug 1424466 *** https://bugs.launchpad.net/bugs/1424466 (fix now being published) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1435324 Title: qtbase5-dev not installable on Ubuntu 14.04 LTS Status in qtbase-opensource-src package in Ubuntu: New Bug description: I discovered the problem when I tried to compile a Qt5 QML program firstly. I have an Ubuntu 14.04.2 LTS with all updates, no significant PPAs (only nodejs and owncloud, not affecting this problem here) and with all the -lts-utopic upgrade packages installed. With that system, I tried to install qtbase5-dev, and apt told me: [...] The following packages have unmet dependencies: qtbase5-dev : Depends: libgles2-mesa-dev or libgles2-dev but it is not installable unity-control-center : Depends: libcheese-gtk23 (= 3.4.0) but it is not going to be installed Depends: libcheese7 (= 3.0.1) but it is not going to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. So this package seems to be not installable. This tried in synaptic, it tries to uninstall all -lts-utopic packages (inclusive all xserver*.deb) and install the old ones instead of them. So the problem somewhere lies within the new lts packages that seem not to be compatible with qtbase5-dev (and its dependency: libgles2 -mesa-dev - but I am not able to find out further. The problem is: Qt5 development on an Ubuntu 14.04.2 LTS machine is NOT possible without a fix. The make process always complains about not finding gl libraries. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: qtbase5-dev (not installed) ProcVersionSignature: Ubuntu 3.16.0-31.43~14.04.1-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 23 14:01:20 2015 InstallationDate: Installed on 2015-02-25 (26 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) SourcePackage: qtbase-opensource-src UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1435324/+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 1435324] Re: qtbase5-dev not installable on Ubuntu 14.04 LTS
*** This bug is a duplicate of bug 1424466 *** https://bugs.launchpad.net/bugs/1424466 This is a bug in the 14.04.2 LTS hardware support stack, tracked in bug #1424466 and bug fix should actually already be published to all users but it seems the SRU team has not yet done so. ** This bug has been marked a duplicate of bug 1424466 Devel package not installable in 14.04.2 (mesa-lts-utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1435324 Title: qtbase5-dev not installable on Ubuntu 14.04 LTS Status in qtbase-opensource-src package in Ubuntu: New Bug description: I discovered the problem when I tried to compile a Qt5 QML program firstly. I have an Ubuntu 14.04.2 LTS with all updates, no significant PPAs (only nodejs and owncloud, not affecting this problem here) and with all the -lts-utopic upgrade packages installed. With that system, I tried to install qtbase5-dev, and apt told me: [...] The following packages have unmet dependencies: qtbase5-dev : Depends: libgles2-mesa-dev or libgles2-dev but it is not installable unity-control-center : Depends: libcheese-gtk23 (= 3.4.0) but it is not going to be installed Depends: libcheese7 (= 3.0.1) but it is not going to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. So this package seems to be not installable. This tried in synaptic, it tries to uninstall all -lts-utopic packages (inclusive all xserver*.deb) and install the old ones instead of them. So the problem somewhere lies within the new lts packages that seem not to be compatible with qtbase5-dev (and its dependency: libgles2 -mesa-dev - but I am not able to find out further. The problem is: Qt5 development on an Ubuntu 14.04.2 LTS machine is NOT possible without a fix. The make process always complains about not finding gl libraries. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: qtbase5-dev (not installed) ProcVersionSignature: Ubuntu 3.16.0-31.43~14.04.1-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 23 14:01:20 2015 InstallationDate: Installed on 2015-02-25 (26 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) SourcePackage: qtbase-opensource-src UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1435324/+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 1424466] Re: Devel package not installable in 14.04.2 (mesa-lts-utopic
This bug was fixed in the package mesa - 10.1.3-0ubuntu0.4 --- mesa (10.1.3-0ubuntu0.4) trusty; urgency=medium * Allow unrenamed -dev packages to work with the renamed stack. (LP: #1424466) -- Maarten Lankhorst maarten.lankho...@ubuntu.com Tue, 10 Mar 2015 12:04:39 +0100 ** Changed in: mesa (Ubuntu Trusty) Status: Fix Committed = Fix Released -- 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/1424466 Title: Devel package not installable in 14.04.2 (mesa-lts-utopic Status in mesa package in Ubuntu: Invalid Status in mesa source package in Trusty: Fix Released Bug description: [Impact] * Some -dev packages like ubuntu-sdk and libglew-dev cannot be installed when the lts-utopic stack is used. [Test Case] * Install the lts-utopic stack. * apt-get install ubuntu-sdk * Good: you get a whole list of packages to install. * Bad: apt-get install fails like pasted in the original bug report. * Also test the same without the lts-utopic stack, to make sure there are no regressions. [Regression Potential] * Low, this has been done for precise before, and mesa packaging has to be updated for every LTS release. Unfortunately there are no alternatives. :( [Other Info] * There's probably an apt bug in here too. Nudging the resolver by specifying libgl1-mesa-dev-lts-utopic and libgles2-mesa-dev-lts-utopic works, but I didn't find a good way to express this in the depends, and that would have to be done for every package. [Original bug report] Not the first, likely not the last devel to not be installable in 14.04.2 or any mesa-lts-utopic install Another one is libglew-dev sudo apt-get install freeglut3-dev 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: libcheese-gtk23 : Depends: libclutter-gtk-1.0-0 (= 0.91.8) but it is not going to be installed Depends: libcogl15 (= 1.15.8) but it is not going to be installed libcheese7 : Depends: libclutter-gst-2.0-0 (= 0.10.0) but it is not going to be installed Depends: gstreamer1.0-clutter but it is not going to be installed libclutter-1.0-0 : Depends: libcogl-pango15 (= 1.15.8) but it is not going to be installed Depends: libcogl15 (= 1.15.8) but it is not going to be installed ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: freeglut3-dev (not installed) ProcVersionSignature: Ubuntu 3.16.0-31.41~14.04.1-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 22 18:03:30 2015 InstallationDate: Installed on 2015-02-08 (14 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150203.2) SourcePackage: freeglut UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1424466/+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 1434143] Re: boot script should run aa-profile-hook in addition to aa-clickhook
Thanks, I've updated the apparmor-ubuntu-citrain branch to do that. Test packages are building in https://launchpad.net/~ubuntu-security- proposed/+archive/ubuntu/ppa and will test the changes once they're built. -- 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/1434143 Title: boot script should run aa-profile-hook in addition to aa-clickhook Status in Snappy Ubuntu: Triaged Status in apparmor package in Ubuntu: In Progress Bug description: Summary says it all. aa-profile-hook does the same sort of thing as aa-clickhook and is used on snappy. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy-ubuntu/+bug/1434143/+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 1433324] Re: provide whl packages in trusty to enable pyvenv in python3.4
chardet lgtm -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to chardet in Ubuntu. https://bugs.launchpad.net/bugs/1433324 Title: provide whl packages in trusty to enable pyvenv in python3.4 Status in chardet package in Ubuntu: Fix Released Status in distlib package in Ubuntu: Fix Released Status in html5lib package in Ubuntu: Fix Released Status in python-colorama package in Ubuntu: Fix Released Status in python-pip package in Ubuntu: Fix Released Status in python-scripttest package in Ubuntu: Fix Released Status in python-setuptools package in Ubuntu: Fix Released Status in python-urllib3 package in Ubuntu: Fix Released Status in requests package in Ubuntu: Fix Released Status in six package in Ubuntu: Fix Released Status in wheel package in Ubuntu: Fix Released Status in chardet source package in Trusty: New Status in distlib source package in Trusty: New Status in html5lib source package in Trusty: New Status in python-colorama source package in Trusty: New Status in python-pip source package in Trusty: New Status in python-scripttest source package in Trusty: New Status in python-setuptools source package in Trusty: New Status in python-urllib3 source package in Trusty: New Status in requests source package in Trusty: New Status in six source package in Trusty: New Status in wheel source package in Trusty: New Bug description: to enable pyvenv in trusty, we need a number of -whl packages in trusty. For the normal case, this is just adding a new separate binary package, sometimes the build system needs to use setuptools. Other needed changes are described below. The python3.4 update is tracked in lp: #1348954. test criterium for accepting these packages should be a successful build, a check that the original packages are not modified, and the new packages are not empty. The version number may be sometimes odd looking. Packages were prepared in the ubuntu-toolchain-r/ppa, and I'd like to use version number higher than in this PPA. wheel: wheel is not part of trusty, so just take the first upload to utopic. six: Build a -whl package (setuptools is needed to build the wheel package). chardet: 2.0.1 in trusty is not ready for Python3. Backport the package from utopic (source name chardet-whl), and just build the python3-chardet and python-chardet-whl packages (both new in trusty). distlib: Build a -whl package (setuptools is needed to build the wheel package). html5lib: Build a -whl package (setuptools is needed to build the wheel package). Just use the packaging of the next Debian version. python-colorama: Build a -whl package (setuptools is needed to build the wheel package). python-urllib3: Build using setuptools and build a wheel package. Additional patch to not rely on ssl.PROTOCOL_SSLv3 being defined. requests: Build a -whl package python-setuptools: Build a -whl package, and fix an issue with installing the documentation. python-pip: Build a -whl package, don't require the new version of python-scripttest, build succeeds without it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chardet/+bug/1433324/+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 1430904] Re: toolbar example doesn't work
** Branch linked: lp:~tpeeters/ubuntu-ui-toolkit/removeToolbarExample -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1430904 Title: toolbar example doesn't work Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: Using the current vivid version bzr checkout lp:ubuntu-ui-toolkit/staging; cd staging; qmlscene examples/ubuntu-ui-toolkit-gallery/Toolbar.qml the example has no toolbar showing, it did before the recent uitk update (the toolbar is deprecated in 1.2 but that code imports 0.1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1430904/+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 1435452] [NEW] dh_apparmor has no dh sequencer support
Public bug reported: As dh_apparmor timing is critical (it must run before services are started with dh_installinit), it makes sense to provide direct dh sequencer support so that maintainers don't have to remember to run it directly, and cannot mistakenly call it at the wrong point, as happened with MySQL in bug 1421303). ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New -- 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/1435452 Title: dh_apparmor has no dh sequencer support Status in apparmor package in Ubuntu: New Bug description: As dh_apparmor timing is critical (it must run before services are started with dh_installinit), it makes sense to provide direct dh sequencer support so that maintainers don't have to remember to run it directly, and cannot mistakenly call it at the wrong point, as happened with MySQL in bug 1421303). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1435452/+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 1431877] Re: [FFe] Merge fixes from debian/sid
This bug was fixed in the package apt - 1.0.9.7ubuntu3 --- apt (1.0.9.7ubuntu3) vivid; urgency=medium * test/integration/test-apt-download-progress: - give apt more time to gather download data in test -- Michael Vogt m...@ubuntu.com Mon, 23 Mar 2015 08:56:53 +0100 ** Changed in: apt (Ubuntu) Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1431877 Title: [FFe] Merge fixes from debian/sid Status in apt package in Ubuntu: Fix Released Bug description: I would like to merge the latest fixes from the debian/sid apt branch. Those are. It also includes a fix for #1429041. apt (1.0.9.7) unstable; urgency=medium [ Tomasz Buchert ] * Fix crash in the apt-transport-https when Owner is NULL (Closes: #778375) -- Michael Vogt m...@debian.org Mon, 23 Feb 2015 12:54:03 +0100 apt (1.0.9.6) unstable; urgency=medium [ Michael Vogt ] * Fix missing URIStart() for https downloads * Add regression test for the previous commit [ David Kalnischkies ] * 128 KiB DSC files ought to be enough for everyone (Closes: 774893) * award points for positive dependencies again (Closes: 774924) -- Michael Vogt m...@ubuntu.com Fri, 16 Jan 2015 08:37:25 +0100 apt (1.0.9.5) unstable; urgency=medium [ David Kalnischkies ] * dispose http(s) 416 error page as non-content (Closes: 768797) * do not make PTY slave the controlling terminal (Closes: 772641) * always run 'dpkg --configure -a' at the end of our dpkg callings (Closes: 769609) * pass-through stdin fd instead of content if not a terminal (Closes: 773061) [ James McCoy ] * tighten filtering of kernel images in apt.auto-removal (Closes: 772732) [ Jean-Pierre Giraud ] * French manpages translation update (Closes: 771967) [ Zhou Mo ] * Chinese (simplified) program translation update (Closes: 771982) [ Kenshi Muto ] * Japanese program translation update (Closes: 772678) [ Theppitak Karoonboonyanan ] * Thai program translation update (Closes: 772913) -- David Kalnischkies da...@kalnischkies.de Tue, 23 Dec 2014 13:22:42 +0100 apt (1.0.9.4) unstable; urgency=medium [ David Kalnischkies ] * use 'best' hash for source authentication (LP: 1098738) * deprecate the Section member from package struct * allow options between command and -- on commandline * re-enable support for -s (and co) in apt-get source (Closes: 742578) * change codenames to jessie as stable POV in docs * close leaking slave fd after setting up pty magic (Closes: 767774) * fix PTY interaction on linux and kfreebsd (Closes: 765687) [ James McCoy ] * support long keyids in apt-key del instead of ignoring them (Closes: 754436) [ Michael Vogt ] * Use sysconf(_SC_ARG_MAX) to find the size of Dpkg::MaxArgBytes [ Frans Spiesschaert ] * Dutch program translation update (Closes: 771039) [ Julien Patriarca ] * French program translation update (Closes: 766755) [ Zhou Mo ] * Chinese (simplified) program translation update (Closes: 766170) [ Miroslav Kure ] * Czech program translation update (Closes: 764055) [ Mert Dirik ] * Turkish program translation update (Closes: 763379) [ Kenshi Muto ] * Japanese program translation update (Closes: 763033) [ Manuel Venturi Porras Peralta ] * Spanish program translation update (Closes: 771815) -- David Kalnischkies da...@kalnischkies.de Wed, 03 Dec 2014 14:26:04 +0100 All of those changes are pretty safe and got past the feature freeze of debian 7.0. All tests pass: # ./test/integration/run-tests ... Statistics: 151 tests were run: 151 successfully and 0 failed All tests seem to have been run successfully. What could possibly go wrong? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1431877/+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 1435452] Re: dh_apparmor has no dh sequencer support
To be clear, I'm expecting that a debian/rules file that calls dh should not need to explicitly call dh_apparmor at all, and that AppArmor profiles will end up loaded before any corresponding service installed with dh_installinit is started. -- 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/1435452 Title: dh_apparmor has no dh sequencer support Status in apparmor package in Ubuntu: New Bug description: As dh_apparmor timing is critical (it must run before services are started with dh_installinit), it makes sense to provide direct dh sequencer support so that maintainers don't have to remember to run it directly, and cannot mistakenly call it at the wrong point, as happened with MySQL in bug 1421303). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1435452/+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 1435503] [NEW] glib warning in nm logs
Public bug reported: jlquinn@tiamat:~/x1carbon$ sudo cat /var/log/upstart/network-manager.log (NetworkManager:718): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory. This indicates a bug in someone's code. You must ensure an error is NULL before it's set. The overwriting error message was: Key file does not have group 'connectivity' It seems there's a bug for someone to track down. jlquinn@tiamat:~/x1carbon$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 14.10 Release:14.10 Codename: utopic jlquinn@tiamat:~/x1carbon$ apt-cache policy network-manager network-manager: Installed: 0.9.8.8-0ubuntu28 Candidate: 0.9.8.8-0ubuntu28 Version table: *** 0.9.8.8-0ubuntu28 0 500 http://us.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages 100 /var/lib/dpkg/status jlquinn@tiamat:~/x1carbon$ ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: network-manager 0.9.8.8-0ubuntu28 ProcVersionSignature: Ubuntu 3.16.0-33.44-generic 3.16.7-ckt7 Uname: Linux 3.16.0-33-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 23 15:06:13 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-10-08 (166 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) IpRoute: default via 9.2.60.1 dev wlan0 proto static 9.2.60.0/23 dev wlan0 proto kernel scope link src 9.2.61.144 metric 9 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to utopic on 2015-02-28 (23 days ago) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2014-10-09T20:11:43.150077 nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8connected enabled enabled enabledenabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1435503 Title: glib warning in nm logs Status in network-manager package in Ubuntu: New Bug description: jlquinn@tiamat:~/x1carbon$ sudo cat /var/log/upstart/network- manager.log (NetworkManager:718): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory. This indicates a bug in someone's code. You must ensure an error is NULL before it's set. The overwriting error message was: Key file does not have group 'connectivity' It seems there's a bug for someone to track down. jlquinn@tiamat:~/x1carbon$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 14.10 Release: 14.10 Codename: utopic jlquinn@tiamat:~/x1carbon$ apt-cache policy network-manager network-manager: Installed: 0.9.8.8-0ubuntu28 Candidate: 0.9.8.8-0ubuntu28 Version table: *** 0.9.8.8-0ubuntu28 0 500 http://us.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages 100 /var/lib/dpkg/status jlquinn@tiamat:~/x1carbon$ ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: network-manager 0.9.8.8-0ubuntu28 ProcVersionSignature: Ubuntu 3.16.0-33.44-generic 3.16.7-ckt7 Uname: Linux 3.16.0-33-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 23 15:06:13 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-10-08 (166 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) IpRoute: default via 9.2.60.1 dev wlan0 proto static 9.2.60.0/23 dev wlan0 proto kernel scope link src 9.2.61.144 metric 9 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to utopic on 2015-02-28 (23 days ago) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2014-10-09T20:11:43.150077 nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable
[Touch-packages] [Bug 1435040] Re: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth
I've got the exact same problem when trying to connect to my COMAND APS NTG 2.5 (Mercedes). Also, I cannot connect to my Dell Inspiron 13-7000 running on Ubuntu 14.10. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1435040 Title: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth Status in indicator-bluetooth package in Ubuntu: Confirmed Bug description: With my FORD Focus Car, pairing does not work. The bluetooth system in the car searches for devices and shows Aquaris E4.5 Ubuntu Edition and then prompts me to connect with a 4-digit pin code, but the Ubuntu phone doesn't react at all and after a while the car system says that it failed to connect. image: 20150310-3201c0a KRILIN01A-S15A_BQ_L100EN_2020_150312 OS Build 20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1435040/+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 1410555] Re: /usr/bin/unity8:6:qt_message_fatal:QMessageLogger::fatal:TouchRegistry::requestTouchOwnership:DirectionalDragArea::unownedTouchEvent_undecided:DirectionalDragArea::u
** Changed in: unity8 (Ubuntu) Status: Triaged = In Progress -- 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/1410555 Title: /usr/bin/unity8:6:qt_message_fatal:QMessageLogger::fatal:TouchRegistry::requestTouchOwnership:DirectionalDragArea::unownedTouchEvent_undecided:DirectionalDragArea::unownedTouchEvent Status in unity8 package in Ubuntu: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unity8. This problem was most recently seen with version 8.02+15.04.20150109.2-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/9f73d3bb741923746c43dcd414d8d3e20700283c contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1410555/+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 1417037] Re: Upgrade to 7.4.4-1ubuntu2.5 hangs
I was able to work around the issue by doing apt-get purge rsyslog and then running dist-upgrade, then reinstalling rsyslog. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1417037 Title: Upgrade to 7.4.4-1ubuntu2.5 hangs Status in rsyslog package in Ubuntu: Confirmed Bug description: I've just ran an update+dist-upgrade which pulled 7.4.4-1ubuntu2.5. It's sat there doing nothing. CTRL+C won't kill it. Htop shows that the last process to be created is stop rsyslog which follows invoke-rc.d rsyslog restart. dpkg.log: 2015-02-02 09:39:10 configure rsyslog:amd64 7.4.4-1ubuntu2.5 none 2015-02-02 09:39:10 status unpacked rsyslog:amd64 7.4.4-1ubuntu2.5 2015-02-02 09:39:10 status unpacked rsyslog:amd64 7.4.4-1ubuntu2.5 2015-02-02 09:39:10 status unpacked rsyslog:amd64 7.4.4-1ubuntu2.5 2015-02-02 09:39:10 status unpacked rsyslog:amd64 7.4.4-1ubuntu2.5 2015-02-02 09:39:10 status unpacked rsyslog:amd64 7.4.4-1ubuntu2.5 2015-02-02 09:39:10 status unpacked rsyslog:amd64 7.4.4-1ubuntu2.5 2015-02-02 09:39:10 status unpacked rsyslog:amd64 7.4.4-1ubuntu2.5 2015-02-02 09:39:10 status unpacked rsyslog:amd64 7.4.4-1ubuntu2.5 2015-02-02 09:39:10 status unpacked rsyslog:amd64 7.4.4-1ubuntu2.5 2015-02-02 09:39:10 status half-configured rsyslog:amd64 7.4.4-1ubuntu2.5 I have KILLed stop rsyslog which then moves on to start rsyslog which I have also had to KILL. Setting up rsyslog (7.4.4-1ubuntu2.5) ... The user `syslog' is already a member of `adm'. Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Terminated Terminated invoke-rc.d: initscript rsyslog, action restart failed. dpkg: error processing package rsyslog (--configure): subprocess installed post-installation script returned error exit status 143 Setting up linux-image-virtual-lts-utopic (3.16.0.30.23) ... Setting up linux-libc-dev:amd64 (3.13.0-45.74) ... Setting up python3-software-properties (0.92.37.3) ... Setting up software-properties-common (0.92.37.3) ... Errors were encountered while processing: rsyslog E: Sub-process /usr/bin/dpkg returned an error code (1) W: Operation was interrupted before it could finish ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: rsyslog 7.4.4-1ubuntu2.5 ProcVersionSignature: Ubuntu 3.16.0-29.39~14.04.1-generic 3.16.7-ckt2 Uname: Linux 3.16.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 Date: Mon Feb 2 09:43:26 2015 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rsyslog UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1417037/+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 1396361] Re: Double Mouse Cursor
Fresh Installed Lubuntu 14.10 (x64) has this issue. I consider it to be essentially the same as https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1393169 It happens more frequently in drag operations. This is my mother's old laptop so I won't be able to report any further. Note: The cursor is restored to normal if you get to a terminal (Ctrl+alt+F1) and then return to X (Ctrl+Alt+F7). -- 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/1396361 Title: Double Mouse Cursor Status in xorg package in Ubuntu: Incomplete Bug description: When dragging with the mouse cursor often it creates a double cursor side by side about 10 cm apart on the screen. Only one cursor works. Using print screen does not show the cursor in the resulting image. Rebooting corrects the problem. This is similar to the double mouse cursor reported as a result of flash in a browser, however the current problem will occur without the browser open. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xinput 1.6.1-1 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic i686 ApportVersion: 2.14.7-0ubuntu8 Architecture: i386 CurrentDesktop: LXDE Date: Tue Nov 25 15:58:51 2014 InstallationDate: Installed on 2014-10-24 (32 days ago) InstallationMedia: Lubuntu 14.10 Utopic Unicorn - Release i386 (20141022.1) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xinput UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1396361/+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 1433324] Re: provide whl packages in trusty to enable pyvenv in python3.4
colorama, urllib3 lgtm -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to chardet in Ubuntu. https://bugs.launchpad.net/bugs/1433324 Title: provide whl packages in trusty to enable pyvenv in python3.4 Status in chardet package in Ubuntu: Fix Released Status in distlib package in Ubuntu: Fix Released Status in html5lib package in Ubuntu: Fix Released Status in python-colorama package in Ubuntu: Fix Released Status in python-pip package in Ubuntu: Fix Released Status in python-scripttest package in Ubuntu: Fix Released Status in python-setuptools package in Ubuntu: Fix Released Status in python-urllib3 package in Ubuntu: Fix Released Status in requests package in Ubuntu: Fix Released Status in six package in Ubuntu: Fix Released Status in wheel package in Ubuntu: Fix Released Status in chardet source package in Trusty: New Status in distlib source package in Trusty: New Status in html5lib source package in Trusty: New Status in python-colorama source package in Trusty: New Status in python-pip source package in Trusty: New Status in python-scripttest source package in Trusty: New Status in python-setuptools source package in Trusty: New Status in python-urllib3 source package in Trusty: New Status in requests source package in Trusty: New Status in six source package in Trusty: New Status in wheel source package in Trusty: New Bug description: to enable pyvenv in trusty, we need a number of -whl packages in trusty. For the normal case, this is just adding a new separate binary package, sometimes the build system needs to use setuptools. Other needed changes are described below. The python3.4 update is tracked in lp: #1348954. test criterium for accepting these packages should be a successful build, a check that the original packages are not modified, and the new packages are not empty. The version number may be sometimes odd looking. Packages were prepared in the ubuntu-toolchain-r/ppa, and I'd like to use version number higher than in this PPA. wheel: wheel is not part of trusty, so just take the first upload to utopic. six: Build a -whl package (setuptools is needed to build the wheel package). chardet: 2.0.1 in trusty is not ready for Python3. Backport the package from utopic (source name chardet-whl), and just build the python3-chardet and python-chardet-whl packages (both new in trusty). distlib: Build a -whl package (setuptools is needed to build the wheel package). html5lib: Build a -whl package (setuptools is needed to build the wheel package). Just use the packaging of the next Debian version. python-colorama: Build a -whl package (setuptools is needed to build the wheel package). python-urllib3: Build using setuptools and build a wheel package. Additional patch to not rely on ssl.PROTOCOL_SSLv3 being defined. requests: Build a -whl package python-setuptools: Build a -whl package, and fix an issue with installing the documentation. python-pip: Build a -whl package, don't require the new version of python-scripttest, build succeeds without it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chardet/+bug/1433324/+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 1433324] Re: provide whl packages in trusty to enable pyvenv in python3.4
requests, setuptools, pip lgtm -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to chardet in Ubuntu. https://bugs.launchpad.net/bugs/1433324 Title: provide whl packages in trusty to enable pyvenv in python3.4 Status in chardet package in Ubuntu: Fix Released Status in distlib package in Ubuntu: Fix Released Status in html5lib package in Ubuntu: Fix Released Status in python-colorama package in Ubuntu: Fix Released Status in python-pip package in Ubuntu: Fix Released Status in python-scripttest package in Ubuntu: Fix Released Status in python-setuptools package in Ubuntu: Fix Released Status in python-urllib3 package in Ubuntu: Fix Released Status in requests package in Ubuntu: Fix Released Status in six package in Ubuntu: Fix Released Status in wheel package in Ubuntu: Fix Released Status in chardet source package in Trusty: New Status in distlib source package in Trusty: New Status in html5lib source package in Trusty: New Status in python-colorama source package in Trusty: New Status in python-pip source package in Trusty: New Status in python-scripttest source package in Trusty: New Status in python-setuptools source package in Trusty: New Status in python-urllib3 source package in Trusty: New Status in requests source package in Trusty: New Status in six source package in Trusty: New Status in wheel source package in Trusty: New Bug description: to enable pyvenv in trusty, we need a number of -whl packages in trusty. For the normal case, this is just adding a new separate binary package, sometimes the build system needs to use setuptools. Other needed changes are described below. The python3.4 update is tracked in lp: #1348954. test criterium for accepting these packages should be a successful build, a check that the original packages are not modified, and the new packages are not empty. The version number may be sometimes odd looking. Packages were prepared in the ubuntu-toolchain-r/ppa, and I'd like to use version number higher than in this PPA. wheel: wheel is not part of trusty, so just take the first upload to utopic. six: Build a -whl package (setuptools is needed to build the wheel package). chardet: 2.0.1 in trusty is not ready for Python3. Backport the package from utopic (source name chardet-whl), and just build the python3-chardet and python-chardet-whl packages (both new in trusty). distlib: Build a -whl package (setuptools is needed to build the wheel package). html5lib: Build a -whl package (setuptools is needed to build the wheel package). Just use the packaging of the next Debian version. python-colorama: Build a -whl package (setuptools is needed to build the wheel package). python-urllib3: Build using setuptools and build a wheel package. Additional patch to not rely on ssl.PROTOCOL_SSLv3 being defined. requests: Build a -whl package python-setuptools: Build a -whl package, and fix an issue with installing the documentation. python-pip: Build a -whl package, don't require the new version of python-scripttest, build succeeds without it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chardet/+bug/1433324/+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 91418] Re: Time not updated when daylight savings switch made
Still facing the same issue in Ubuntu 14.10. I live in Milwaukee, USA. Time did not change automatically in Spring. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/91418 Title: Time not updated when daylight savings switch made Status in tzdata package in Ubuntu: Confirmed Bug description: Binary package hint: tzdata March 11, 2007, edgy did not update my clock. I had installed the edgy updates and i do find Adept Manager listing the tzdata_2007b_0ubuntu0.6.10_all.deb as been installed on 03/07/2007. I am using Dell Inspiron 5160, dual booting with XP. $ sudo dpkg -s tzdata Package: tzdata Status: install ok installed Priority: required Section: libs Installed-Size: 5728 Maintainer: Ubuntu Core Developers ubuntu-de...@lists.ubuntu.com Architecture: all Version: 2007b-0ubuntu0.6.10 Replaces: libc0.1, libc0.3, libc6, libc6.1, locales Description: Time Zone and Daylight Saving Time Data This package contains data that represent the history of local time for many representative locations around the globe. It is updated periodically to reflect changes made by political bodies to time zone boundaries, UTC offsets, and daylight-saving rules Original-Maintainer: GNU Libc Maintainers debian-gl...@lists.debian.org $ sudo zdump -v /etc/localtime | grep 2007 /etc/localtime Sun Mar 11 06:59:59 2007 UTC = Sun Mar 11 01:59:59 2007 EST isdst=0 gmtoff=-18000 /etc/localtime Sun Mar 11 07:00:00 2007 UTC = Sun Mar 11 03:00:00 2007 EDT isdst=1 gmtoff=-14400 /etc/localtime Sun Nov 4 05:59:59 2007 UTC = Sun Nov 4 01:59:59 2007 EDT isdst=1 gmtoff=-14400 /etc/localtime Sun Nov 4 06:00:00 2007 UTC = Sun Nov 4 01:00:00 2007 EST isdst=0 gmtoff=-18000 $ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/91418/+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 1393169] Re: [Toshiba Satellite Pro C650] Double mouse cursor
Fresh Installed Lubuntu 14.10 (x64) has this issue. It happens more frequently in drag operations. This is my mother's old laptop so I won't be able to report any further. Note: The cursor is restored to normal if you get to a terminal (Ctrl+alt+F1) and then return to X (Ctrl+Alt+F7). -- 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/1393169 Title: [Toshiba Satellite Pro C650] Double mouse cursor Status in xorg package in Ubuntu: Incomplete Bug description: Last up to date Xubuntu 64 bits installed on a laptop Since 2 days, the mouse cursor is double with only the left part as active and a bar just behing of both arrow (see picture joined). I tried to change the theme but no way to go back to a normal mouse cursor Regards ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Nov 16 11:12:21 2014 InstallationDate: Installed on 2013-01-03 (681 days ago) InstallationMedia: Xubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.1) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: utopic DistroRelease: Ubuntu 14.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:fde0] Subsystem: Toshiba America Info Systems Device [1179:fde0] InstallationDate: Installed on 2013-01-03 (695 days ago) InstallationMedia: Xubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.1) LightdmGreeterLog: ** (lightdm-gtk-greeter:1659): WARNING **: Failed to load background: Impossible d'ouvrir le fichier « /home/christophe/Dropbox/Personnalisation/Fonds d'écran/bleu.jpg » : Permission non accordée ** (lightdm-gtk-greeter:1659): WARNING **: Failed to read wallpaper: /home/christophe/Dropbox/Personnalisation/Fonds d'écran/bleu.jpg g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. LightdmGreeterLogOld: ** (lightdm-gtk-greeter:1641): WARNING **: Failed to load background: Impossible d'ouvrir le fichier « /home/christophe/Dropbox/Personnalisation/Fonds d'écran/bleu.jpg » : Permission non accordée ** (lightdm-gtk-greeter:1641): WARNING **: Failed to read wallpaper: /home/christophe/Dropbox/Personnalisation/Fonds d'écran/bleu.jpg g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. MachineType: TOSHIBA Satellite Pro C650 Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-26-generic root=UUID=7bc86e4b-720d-4f1c-bb66-a4c08ffc1359 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-26.34-generic 3.16.7-ckt1 Tags: utopic ubuntu Uname: Linux 3.16.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/01/2010 dmi.bios.vendor: INSYDE dmi.bios.version: 1.30 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvr1.30:bd07/01/2010:svnTOSHIBA:pnSatelliteProC650:pvrPSC09E-00R01YMV:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Satellite Pro C650 dmi.product.version: PSC09E-00R01YMV dmi.sys.vendor: TOSHIBA version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4.1
[Touch-packages] [Bug 1435040] Re: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: indicator-bluetooth (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1435040 Title: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth Status in indicator-bluetooth package in Ubuntu: Confirmed Bug description: With my FORD Focus Car, pairing does not work. The bluetooth system in the car searches for devices and shows Aquaris E4.5 Ubuntu Edition and then prompts me to connect with a 4-digit pin code, but the Ubuntu phone doesn't react at all and after a while the car system says that it failed to connect. image: 20150310-3201c0a KRILIN01A-S15A_BQ_L100EN_2020_150312 OS Build 20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1435040/+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 1435475] Re: Crash during a calendar event alert
The qt update is a seemingly unrelated single patch and it was unity8 that crashed but no did not look at the crash file -- 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/1435475 Title: Crash during a calendar event alert Status in unity8 package in Ubuntu: New Bug description: An alert sounded for a meeting, The audio alert stopped sounding, but the phone continued to vibrate indefinitely The UI was frozen and the greeter could not be opened The power button did work to turn the screen on and off, but did not show the shutdown dialog. Hard power down mako running rtm 214 with silo 3 Qt patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1435475/+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
