[Touch-packages] [Bug 1452320] Re: please drop build-dependency on g++-4.9
** Changed in: mir Assignee: (unassigned) = Daniel van Vugt (vanvugt) ** Changed in: mir Importance: Undecided = Medium ** Changed in: mir Status: New = In Progress ** Branch linked: lp:~vanvugt/mir/no-need-4.9 -- 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/1452320 Title: please drop build-dependency on g++-4.9 Status in Mir: In Progress Status in mir package in Ubuntu: New Bug description: The mir package currently has a build-dependency on g++-4.9. This build-dependency is present because of the recommendations on https://wiki.ubuntu.com/cpp-11 about handling of C++11. The C++11 ABI has now stabilized in gcc as of gcc 5; however, before we can switch to gcc 5, we first need to be able to do rebuild tests of the archive against this compiler. To facilitate this, please drop the build-dependency on g++-4.9 from the package in wily. 4.9 will remain the default until all transition issues have been identified, so there is no risk of accidental ABI breakage here anymore. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1452320/+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 1432613] Re: Facebook and MSN messengers shutting down (third-party client access)
Hi, I now tested trusty-proposed too, and everything works as expected: Empathy no longer appears under the Facebook and MSN accounts. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1432613 Title: Facebook and MSN messengers shutting down (third-party client access) Status in Online Accounts: Account plugins: In Progress Status in Webapps Team Task Tracking Project: In Progress Status in account-plugins package in Ubuntu: Fix Committed Status in empathy package in Ubuntu: Fix Committed Status in ubuntu-system-settings-online-accounts package in Ubuntu: New Status in account-plugins source package in Trusty: Fix Committed Status in empathy source package in Trusty: Fix Committed Status in ubuntu-system-settings-online-accounts source package in Trusty: Won't Fix Status in account-plugins source package in Utopic: Fix Committed Status in empathy source package in Utopic: Fix Committed Status in ubuntu-system-settings-online-accounts source package in Utopic: Won't Fix Status in account-plugins source package in Vivid: Fix Committed Status in empathy source package in Vivid: Fix Committed Status in ubuntu-system-settings-online-accounts source package in Vivid: Won't Fix Bug description: [ Description ] Facebook messenger and Windows Live messenger don't work any more because Facebook Microsoft removed third-party support for them. [ Fix QA ] Stop supporting IM accounts for these clients. For both creation continued use. Verify that if you add a WLM or FB account in online accounts, empathy doesn't try to connect to it. account-plugins-windows-live shouldn't be pulled in by default any more (check a trusty daily which is built with proposed). [ Regression potential ] This is a regression, in that we stop supporting some account types. We don't have a choice about this. [ Original description ] The march towards a future of silos carries on. https://developers.facebook.com/docs/chat - the XMPP gateway for Facebook will shut down on April 30. http://ismsndeadyet.com/ - Microsoft are removing MSN endpoints. I guess we need to correspondingly remove IM support for these services SRU it back. To manage notifications about this bug go to: https://bugs.launchpad.net/account-plugins/+bug/1432613/+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 1167614] Re: DHCP server incorrectly handling VLAN tagged packets
according to the changelog, this should be fixed in upstream since isc-dhcp 4.3.2b1. see ftp://ftp.isc.org/isc/dhcp/4.3.2/dhcp-4.3.2-RELNOTES So all we'd need is a new package with the new upstream released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1167614 Title: DHCP server incorrectly handling VLAN tagged packets Status in isc-dhcp package in Ubuntu: Confirmed Status in Debian: New Bug description: Upon receipt of a VLAN tagged packet, the DHCP server is processing it as though it was received without a VLAN tag. Steps to reproduce: - Send a DHCPDISCOVER packet to the broadcast address with a VLAN tag Expected results: - None. The DHCP server should ignore this packet. Actual results: - The DHCP server interprets the packet as though it were received untagged and transmits a response accordingly. Comments: - I believe this to be an instance of Debian bug #643564 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: isc-dhcp-server 4.1.ESV-R4-0ubuntu5.6 ProcVersionSignature: Ubuntu 3.2.0-40.64-generic 3.2.40 Uname: Linux 3.2.0-40-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 Date: Wed Apr 10 18:42:30 2013 MarkForUpload: True ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: isc-dhcp UpgradeStatus: Upgraded to precise on 2012-09-01 (221 days ago) modified.conffile..etc.dhcp.dhcpd.conf: [modified] mtime.conffile..etc.dhcp.dhcpd.conf: 2012-12-14T11:32:45 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1167614/+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 1193822] Re: dh-migrations: Typo in package description: packaged
** Branch linked: lp:session-migration -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to session-migration in Ubuntu. https://bugs.launchpad.net/bugs/1193822 Title: dh-migrations: Typo in package description: packaged Status in Package Descriptions for Ubuntu (to make translation easy): Triaged Status in session-migration package in Ubuntu: Fix Committed Bug description: Package: dh-migrations Version: 0.2 Hello, There's a typo in string #911 in the following sentence: ...operations on the installed packaged. (packaged should be replaced with packages) Link: https://translations.launchpad.net/ddtp-ubuntu/raring/+pots /ddtp-ubuntu-main/fr/911 Regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ddtp-ubuntu/+bug/1193822/+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 1452616] [NEW] Ubuntu Web Browser identified as old Safari in gmail
Public bug reported: Ubuntu Web Browser identified as old Safari in gmail. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: webbrowser-app 0.23+15.04.20150416-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu May 7 11:29:34 2015 SourcePackage: webbrowser-app UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: webbrowser-app (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid ** Attachment added: Screenshot.jpg https://bugs.launchpad.net/bugs/1452616/+attachment/4392839/+files/Screenshot.jpg -- 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/1452616 Title: Ubuntu Web Browser identified as old Safari in gmail Status in webbrowser-app package in Ubuntu: New Bug description: Ubuntu Web Browser identified as old Safari in gmail. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: webbrowser-app 0.23+15.04.20150416-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu May 7 11:29:34 2015 SourcePackage: webbrowser-app UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1452616/+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 1452390] Re: invalid pam rule in vivid is preventing logins
please close this report as the issue is more prevalent to something else thanks -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1452390 Title: invalid pam rule in vivid is preventing logins Status in pam package in Ubuntu: Incomplete Bug description: there are problematic pam rules preventing users from logging in (pam errors show up with auth.log) Other users are reporting this problem online with upgrades but I can confirm this occurs with just new installs in Virtualbox (15.04 amd64) please have a look thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1452390/+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 1448775] Re: Unable to login after upgrade from 14.10 to 15.04 possible XOrg crash
Thank you for your time, I really appreciate it. Reported as #1452581. -- 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/1448775 Title: Unable to login after upgrade from 14.10 to 15.04 possible XOrg crash Status in Compiz: Invalid Status in unity package in Ubuntu: Invalid Bug description: After upgrade from working machine with 14.10 to 15.10 I'm unable to login. Right after password screen I see loading of desktop and I'm returned to password prompt again. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,mousepoll,imgpng,unitymtgrabhandles,move,compiztoolbox,place,grid,wall,vpswitch,regex,resize,gnomecompat,snap,session,animation,expo,workarounds,ezoom,fade,scale,unityshell] Date: Sun Apr 26 23:07:55 2015 DistUpgraded: 2015-04-26 22:20:44,130 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.26: added EcryptfsInUse: Yes ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: NVIDIA Corporation GT218M [GeForce 315M] [10de:0a7a] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems GeForce 315M [1179:fd71] InstallationDate: Installed on 2014-11-07 (170 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: TOSHIBA SATELLITE C670-10V ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic root=UUID=28cea712-ba61-42af-a038-545501a067f8 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to vivid on 2015-04-26 (0 days ago) dmi.bios.date: 04/20/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.40 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: TKBSC dmi.board.vendor: TOSHIBA dmi.board.version: 1.40 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.40:bd04/20/2011:svnTOSHIBA:pnSATELLITEC670-10V:pvrPSC3QE-00700JPL:rvnTOSHIBA:rnTKBSC:rvr1.40:cvnTOSHIBA:ct9:cvrToBeFilledByO.E.M.: dmi.product.name: SATELLITE C670-10V dmi.product.version: PSC3QE-00700JPL dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Sun Apr 26 23:07:32 2015 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.17.1-0ubuntu3 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1448775/+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 1408963] Re: [Xbuntu 14.04, 14.10 and 15.04] Network manager stops working: iwl3945 0000:03:00.0: BSM uCode verification failed at addr ...; wlan0: deauthenticating from... by lo
Exactly the same being seen here, frequently. Vivid 15.04, upgraded on release from 14.10 (previously upgraded several times) Intel 3945ABG using iwl3945 Dell Latitude D830 deauthenticating by local choice message in dmesg, followed by a dozen or so lines of Failed check-sdata-in-driver check, flags: 0x4 all timestamped within 0.01 seconds. Check network-manager - networks all shown. Turn wireless hardware switch off, all go. Back on, all stay gone. Restart network-manager - Wi-Fi Networks: device not ready Under 14.10, on first booting the machine, it would always associate with a weaker wireless network, and need manually changing to the stronger. This never happened prior to 14.10, and doesn't happen under 15.04 Time before failure can be several days, or (as this morning) can be ~20min after boot. It can fail to resume, or it can happen whilst the machine's in use. I think I've had it a dozen or so times since upgrade. -- 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/1408963 Title: [Xbuntu 14.04, 14.10 and 15.04] Network manager stops working: iwl3945 :03:00.0: BSM uCode verification failed at addr ...; wlan0: deauthenticating from... by local choice (Reason: 3=DEAUTH_LEAVING), Status in linux-firmware package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: From time to time, the system loses all wireles networks and kubuntu network manager applet goes blank - not even one network is shown. All wifi connections are broken. Rebooting fixes the issue, switching to WICD on-the-fly enables to continue browsing without rebooting, so it seems to be no hardware issue or iwl3945 issue. What to expect: stable connections and flawless network managing. What happens: so above. Further informations about the system, the network configuration, the package version can be found in the attachment, also parts of rsyslog and dmesg. Interesting, according to some helpers, are the following lines: dmesg: wlan0: deauthenticating from 02:26:4d:ac:8f:45 by local choice (Reason: 3=DEAUTH_LEAVING) lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 14.10 Release:14.10 Codename: utopic apt-cache policy network-manager network-manager: Installiert: 0.9.8.8-0ubuntu28 Installationskandidat: 0.9.8.8-0ubuntu28 Versionstabelle: *** 0.9.8.8-0ubuntu28 0 500 http://de.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1408963/+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 1447807] Re: systemctl enable shows error on enabling a SysV service
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1447807 Title: systemctl enable shows error on enabling a SysV service Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Vivid: Fix Committed Status in systemd source package in Wily: Fix Committed Bug description: SRU TEST CASE: -- Trying to enable a SysV init service which does not have a corresponding systemd unit results in an error: # systemctl enable pulseaudio Synchronizing state for pulseaudio.service with sysvinit using update-rc.d... Executing /usr/sbin/update-rc.d pulseaudio defaults Executing /usr/sbin/update-rc.d pulseaudio enable Failed to execute operation: No such file or directory /etc/init.d/pulseaudio actually does get enabled (check /etc/rc*/*pulse*), but the command fails with code 1 and you get that error message. With the fix the command succeeds. SRU Regression potential Low, the modes for sysv script + systemd unit as well as systemd unit only already have automatic tests, and now this scenario (sysv script only) has a test too. In the worst case this has the potential of completely breaking systemctl enable/disable, which can be worked around with changing symlinks manually, and isn't breaking the boot. Version details: Description: Ubuntu 15.04 Release: 15.04 systemd: Installed: 219-7ubuntu3 Candidate: 219-7ubuntu3 Version table: *** 219-7ubuntu3 0 500 http://us-west-2.ec2.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447807/+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 1447807] Re: systemctl enable shows error on enabling a SysV service
After installing systemd 219-7ubuntu5 I can enable a SysV service without any errors. Thanks! -- 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/1447807 Title: systemctl enable shows error on enabling a SysV service Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Vivid: Fix Committed Status in systemd source package in Wily: Fix Committed Bug description: SRU TEST CASE: -- Trying to enable a SysV init service which does not have a corresponding systemd unit results in an error: # systemctl enable pulseaudio Synchronizing state for pulseaudio.service with sysvinit using update-rc.d... Executing /usr/sbin/update-rc.d pulseaudio defaults Executing /usr/sbin/update-rc.d pulseaudio enable Failed to execute operation: No such file or directory /etc/init.d/pulseaudio actually does get enabled (check /etc/rc*/*pulse*), but the command fails with code 1 and you get that error message. With the fix the command succeeds. SRU Regression potential Low, the modes for sysv script + systemd unit as well as systemd unit only already have automatic tests, and now this scenario (sysv script only) has a test too. In the worst case this has the potential of completely breaking systemctl enable/disable, which can be worked around with changing symlinks manually, and isn't breaking the boot. Version details: Description: Ubuntu 15.04 Release: 15.04 systemd: Installed: 219-7ubuntu3 Candidate: 219-7ubuntu3 Version table: *** 219-7ubuntu3 0 500 http://us-west-2.ec2.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447807/+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 1452601] [NEW] vivid container's networking.service fails on boot with signal=PIPE
Public bug reported: When starting a Vivid container, it fails to get an IP address. It believes networking.service was successful, but actually it dies with SIGPIPE. Restarting networking.service gets an IP, as expected. Starting networking used to work with pre-vivid containers. I'm reasonably sure this fails 100% of the time. Limited user container, very standard setup (no unnecessary config; cgmanager and lxcfs installed), btrfs filesystem but not btrfs-backed (as it's limited user), ... root@vivid:/# systemctl status networking.service ● networking.service - LSB: Raise network interfaces. Loaded: loaded (/etc/init.d/networking) Drop-In: /run/systemd/generator/networking.service.d └─50-insserv.conf-$network.conf /lib/systemd/system/networking.service.d └─systemd.conf Active: active (exited) since Thu 2015-05-07 07:54:48 UTC; 9s ago Docs: man:systemd-sysv-generator(8) Process: 459 ExecStart=/etc/init.d/networking start (code=killed, signal=PIPE) root@vivid:/# systemctl restart networking.service root@vivid:/# systemctl status networking.service ● networking.service - LSB: Raise network interfaces. Loaded: loaded (/etc/init.d/networking) Drop-In: /run/systemd/generator/networking.service.d └─50-insserv.conf-$network.conf /lib/systemd/system/networking.service.d └─systemd.conf Active: active (running) since Thu 2015-05-07 07:56:38 UTC; 2s ago Docs: man:systemd-sysv-generator(8) Process: 992 ExecStop=/etc/init.d/networking stop (code=exited, status=0/SUCCESS) Process: 1033 ExecStart=/etc/init.d/networking start (code=exited, status=0/SUCCESS) CGroup: /user.slice/user-1000.slice/session-c2.scope/lxc/vivid/system.slice/networking.service ├─1096 dhclient -1 -v -pf /run/dhclient.eth0.pid -lf /var/lib/dhcp/dhclient.eth0.leases eth0 ├─1106 /bin/sh /etc/network/if-up.d/ntpdate ├─1109 lockfile-touch /var/lock/ntpdate-ifup ├─1125 /bin/sh /etc/network/if-up.d/ntpdate ├─1128 lockfile-create /var/lock/ntpdate-ifup └─1146 /usr/sbin/ntpdate -s ntp.ubuntu.com root@vivid:/# ip a ... 22: eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 ... inet 10.0.3.102/24 brd 10.0.3.255 scope global eth0 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lxc 1.1.2-0ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Thu May 7 08:53:02 2015 SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-bug vivid ** Attachment added: full boot log from lxc-start -F https://bugs.launchpad.net/bugs/1452601/+attachment/4392774/+files/vivid-boot.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1452601 Title: vivid container's networking.service fails on boot with signal=PIPE Status in lxc package in Ubuntu: New Bug description: When starting a Vivid container, it fails to get an IP address. It believes networking.service was successful, but actually it dies with SIGPIPE. Restarting networking.service gets an IP, as expected. Starting networking used to work with pre-vivid containers. I'm reasonably sure this fails 100% of the time. Limited user container, very standard setup (no unnecessary config; cgmanager and lxcfs installed), btrfs filesystem but not btrfs-backed (as it's limited user), ... root@vivid:/# systemctl status networking.service ● networking.service - LSB: Raise network interfaces. Loaded: loaded (/etc/init.d/networking) Drop-In: /run/systemd/generator/networking.service.d └─50-insserv.conf-$network.conf /lib/systemd/system/networking.service.d └─systemd.conf Active: active (exited) since Thu 2015-05-07 07:54:48 UTC; 9s ago Docs: man:systemd-sysv-generator(8) Process: 459 ExecStart=/etc/init.d/networking start (code=killed, signal=PIPE) root@vivid:/# systemctl restart networking.service root@vivid:/# systemctl status networking.service ● networking.service - LSB: Raise network interfaces. Loaded: loaded (/etc/init.d/networking) Drop-In: /run/systemd/generator/networking.service.d └─50-insserv.conf-$network.conf /lib/systemd/system/networking.service.d └─systemd.conf Active: active (running) since Thu 2015-05-07 07:56:38 UTC; 2s ago Docs: man:systemd-sysv-generator(8) Process: 992 ExecStop=/etc/init.d/networking stop
[Touch-packages] [Bug 1452161] Re: from flight mode to normal mode with 2 SIM: PIN's title prompt is reversed
** Description changed: I am on krillin #21 on rtm/stable channel. - * I go on flight mode (the checkbox from the indicator becomes green) - * I go out flight mode (the checkbox from the indicator is not anymore green) - * I have 2 button to unlock the SIM 1 and SIM 2 - * I click on unlock SIM 1, I have a screen with the title unlock SIM 2 - * I click on unlock SIM 2, I have s screen with the title unlock SIM 1 + * I go on flight mode (the checkbox from the indicator becomes green) + * I go out flight mode (the checkbox from the indicator is not anymore green) + * I have 2 button to unlock the SIM 1 and SIM 2 + * I click on unlock SIM 1, I have a screen with the title unlock SIM 2 + * I click on unlock SIM 2, I have s screen with the title unlock SIM 1 Since I have the same PIN, I am not sure if the button call to unlock the wrong SIM, on if it's only the wrong title. + + Some details: + * Both SIM are from the same operator: Free (mobile.free.fr) -- 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/1452161 Title: from flight mode to normal mode with 2 SIM: PIN's title prompt is reversed Status in indicator-network package in Ubuntu: New Bug description: I am on krillin #21 on rtm/stable channel. * I go on flight mode (the checkbox from the indicator becomes green) * I go out flight mode (the checkbox from the indicator is not anymore green) * I have 2 button to unlock the SIM 1 and SIM 2 * I click on unlock SIM 1, I have a screen with the title unlock SIM 2 * I click on unlock SIM 2, I have s screen with the title unlock SIM 1 Since I have the same PIN, I am not sure if the button call to unlock the wrong SIM, on if it's only the wrong title. Some details: * Both SIM are from the same operator: Free (mobile.free.fr) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1452161/+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 1450747] Re: Native overlay scrollbars aren't themed
Looks like gtk in master has a position indicator thingy on mouse activity (3.16 shows the whole scrollbar), so maybe we can tweak this to do what o-s did be shown all the time. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1450747 Title: Native overlay scrollbars aren't themed Status in gtk+3.0 package in Ubuntu: New Bug description: In 3.16 (from ppa:ubuntu-desktop/ww + overlay-scrollbar from this PPA), applications have native overlay scrollbars provided by GTK. We want to use these in Ubuntu, but currently they are not themed so look a bit incongruous. I think we want to - Theme them to fit in with Ambiance/Radiance - If possible, show a thumb when the scrollbar is hidden so that you can see where you are in a document To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1450747/+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 1450562] Re: libdrm-intel1 2.4.60 breaks Valve/Steam games
upstream isn't convinced, someone needs to poke Valve ** Changed in: libdrm (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1450562 Title: libdrm-intel1 2.4.60 breaks Valve/Steam games Status in X.Org X server: Confirmed Status in libdrm package in Ubuntu: Incomplete Bug description: Referring to this bug: https://github.com/ValveSoftware/steam-for- linux/issues/3506 The only option to get games working again is to take the libdrm-intel 2.4.56 lib files from the .deb and copy them to your local steam install as an override for 2.4.60 system lib. To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1450562/+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 1432265] Re: does not ask for multiple LUKS passphrases without plymouth
I can confirm this also. Steps to reproduce: - install *buntu 15.04 - sudo systemctl set-default multi-user.target - add some partition _other than root_ to /etc/crypttab - systemd doesn't ask for passphrase, stops at starting cryptography for foo.. booting with upstart and text kernel option (same as systemd and multi-user.target), it asks for passphrase and works correctly. In my tests I had root without encryption and another partition in crypttab, then it doesn't ask for passphrase. In another test I had root encrypted and that in crypttab, then it asks for the passphrase. -- 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/1432265 Title: does not ask for multiple LUKS passphrases without plymouth Status in systemd package in Ubuntu: Triaged Status in systemd source package in Vivid: Triaged Status in systemd package in Debian: New Bug description: after the recent upstart - systemd migration my system is left unable to complete it's boot process. It asks for the first passphrase, but not for the second. When booting with upstart (via the advanced boot options), the system behaves correctly and asks for both passphrases. /etc/crypttab sda2_crypt UUID=32a5c8b9--4b06-9224-0dc595e320b7 none luks,discard sdb1_crypt UUID=8b568ed8-842b-462c-9ecd-789d80fb913f none luks,discard /etc/fstab # file system mount point type options dump pass /dev/mapper/sda2_crypt /ext4 discard,noatime,nodiratime,commit=300,errors=remount-ro 0 1 /dev/sda1 /boot ext3 discard,relatime,nodiratime,commit=300,defaults 0 2 /dev/mapper/sdb1_crypt /opt btrfs nofail,autodefrag,discard,enospc_debug 0 1 # tmpfs/tmp tmpfs relatime,nosuid 0 0 #/dev/mapper/swap none swapsw,discard 0 0 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-4ubuntu5 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Mar 15 00:10:02 2015 InstallationDate: Installed on 2014-05-30 (288 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) MachineType: Dell Inc. Precision M4800 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-9-generic root=UUID=c72e0d8e-4822-45c8-b95f-6e13971940d3 ro nomodeset allow-discards root_trim=yes nomdmonddf nomdmonisw crashkernel=384M-:128M nogpumanager init=/sbin/upstart SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/graphical.target → /lib/systemd/system/graphical.target.d/xdiagnose.conf [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0PMFT3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd06/26/2014:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn0PMFT3:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4800 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1432265/+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 1452624] [NEW] /etc/os-release should be deprecated in favor of /usr/lib/os-release
Public bug reported: /etc/os-release should be deprecated in favor of /usr/lib/os-release as per latest freedesktop spec. ** Affects: base-files (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1452624 Title: /etc/os-release should be deprecated in favor of /usr/lib/os-release Status in base-files package in Ubuntu: New Bug description: /etc/os-release should be deprecated in favor of /usr/lib/os-release as per latest freedesktop spec. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1452624/+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 1448446] Re: Cannot login into Ubuntu 15.04 after upgrade
Thank you for your bug report. Can you include your /var/log/lightdm/lightdm.log and ~/.xsession-errors and .cache/upstart /gnome-session-Unity.log logs? ** Changed in: lightdm (Ubuntu) Importance: Undecided = High ** Changed in: lightdm (Ubuntu) Status: Confirmed = Incomplete -- 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/1448446 Title: Cannot login into Ubuntu 15.04 after upgrade Status in lightdm package in Ubuntu: Incomplete Bug description: After I upgraded my Ubuntu 14.10 to 15.04, I wanted to login into the GUI system. I have 4 users on my system. 3 of them is unable to login, 1 is able. The message is unsuccessful login. Terminal logins work for all users. I use lightdm. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1448446/+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 1170647] Re: After minimizing Nautilus window of Trash folder or any folder in another partition as well as external media, clicking on the Files icon on the Launcher doesn't r
** Summary changed: - After minimizing an external media, clicking on the Files icon on the Launcher doesn't restore the minimized window, but opens a new one + After minimizing Nautilus window of Trash folder or any folder in another partition as well as external media, clicking on the Files icon on the Launcher doesn't restore the minimized window, but opens a new one ** Summary changed: - After minimizing Nautilus window of Trash folder or any folder in another partition as well as external media, clicking on the Files icon on the Launcher doesn't restore the minimized window, but opens a new one + After minimizing a Nautilus window of another partition or external media or Trash folder, clicking on the Files icon on the Launcher doesn't restore the minimized window, but opens a new one ** Summary changed: - After minimizing a Nautilus window of another partition or external media or Trash folder, clicking on the Files icon on the Launcher doesn't restore the minimized window, but opens a new one + After minimizing a Nautilus window of another partition or external media or Trash folder, clicking on the Files icon on the Launcher again doesn't restore the minimized window, but opens a new one -- 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/1170647 Title: After minimizing a Nautilus window of another partition or external media or Trash folder, clicking on the Files icon on the Launcher again doesn't restore the minimized window, but opens a new one Status in One Hundred Papercuts: Triaged Status in Unity: Triaged Status in Vivid OPM Workspace: New Status in unity package in Ubuntu: Triaged Status in unity source package in Trusty: Confirmed Bug description: *** ISSUE *** HOW TO REPRODUCE 1. Connect a removable media to the computer. 2. On the launcher, click on the Files icon. 3. On the left sidebar, click on the removable media icon or the trash. 4. Minimize the window. 5. Click on the Files icon. EXPECTED BEHAVIOUR - The Files window to be maximized. REAL BEHAVIOUR - A new window is opened. RELEVANT DETAILS - One way to navigate between windows at this moment is to use the control + tabulation key combination, or to click again on the Files icon so windows are exposed. Otherwise the minimized window Can be restored by clicking on the Volume's launcher icon or scrolling on the Files icon ** SOLUTION ** WORK-AROUND - On the launcher, left click on the Files icon and select the unlock from Launcher option. FIX - The launcher icon for Files to be treated the same way as if it was unlocked. REGRESSION POTENTIAL - Clicking on the Files icon won't send the user to its home folder, but to the latest opened Files window. TECHNICAL INFO ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: nautilus 1:3.6.3-0ubuntu16 ProcVersionSignature: Ubuntu 3.8.0-18.28-generic 3.8.6 Uname: Linux 3.8.0-18-generic i686 ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 Date: Fri Apr 19 11:33:13 2013 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b'814x493+136+38' b'org.gnome.nautilus.window-state' b'sidebar-width' b'182' InstallationDate: Installed on 2011-07-23 (635 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110426) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: Upgraded to raring on 2013-04-14 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1170647/+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 1448834] Re: mouse battery not shown after upgrade
** Package changed: xfce4-power-manager (Ubuntu) = upower (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1448834 Title: mouse battery not shown after upgrade Status in gnome-power-manager package in Ubuntu: New Status in upower package in Ubuntu: New Bug description: In Xubuntu 14.04 and 14.10 the power manager dropdown menu showed the battery level in my wireless logitech mouse. However after upgrading to 15.04 the mouse battery status is not shown. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xfce4-power-manager 1.4.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Apr 26 19:49:19 2015 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xfce4-power-manager UpgradeStatus: Upgraded to vivid on 2015-04-23 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1448834/+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 1448259] Re: Systemd does not send SIGTERM first on shutdown
** Description changed: It has been normal that applications first get the SIGTERM signal before SIGKILL on shutdown/reboot in order to successfully finish any pending tasks. Now it seem this logic has been changed to something else, causing problems to mosh and many others: https://bugs.launchpad.net/ubuntu/+source/mosh/+bug/1446982 SIGTERM suggestion can be seen here: http://unixhelp.ed.ac.uk/CGI/man-cgi?shutdown+8 I created this error report to find out the correct way for applications to fix this problem or to create one fix to systemd, bringing back the old BSD shutdown functionality. This report is for Ubuntu 15.04. + + SRU TEST CASE: + - Open a terminal, enter some commands, then run reboot. + - After a reboot, chances are very high that your bash history does not contain your most recently typed commands + - With the updated package, the bash history should be intact. ** Description changed: It has been normal that applications first get the SIGTERM signal before SIGKILL on shutdown/reboot in order to successfully finish any pending tasks. Now it seem this logic has been changed to something else, causing problems to mosh and many others: https://bugs.launchpad.net/ubuntu/+source/mosh/+bug/1446982 SIGTERM suggestion can be seen here: http://unixhelp.ed.ac.uk/CGI/man-cgi?shutdown+8 I created this error report to find out the correct way for applications to fix this problem or to create one fix to systemd, bringing back the old BSD shutdown functionality. This report is for Ubuntu 15.04. SRU TEST CASE: - - Open a terminal, enter some commands, then run reboot. - - After a reboot, chances are very high that your bash history does not contain your most recently typed commands - - With the updated package, the bash history should be intact. + - Open a terminal, enter some commands, then run reboot. + - After a reboot, chances are very high that your bash history does not contain your most recently typed commands + - With the updated package, the bash history should be intact. + + REGRESSION POTENTIAL: + - The original commit was applied because of an inherent race condition with cgroup's release_agent -- in rare corner cases an nspawn container (probably also LXC) can miss them. In that case it's possible that you instead get a 90s timeout on the unit that is shutting down. But this does not mean data loss, just a rare shutdown hang from containers (for the record, I never actually saw that hanging with LXC), so I think it's a good trade-off. ** Changed in: systemd (Ubuntu) Milestone: vivid-updates = None -- 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/1448259 Title: Systemd does not send SIGTERM first on shutdown Status in systemd: Unknown Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Vivid: Fix Committed Status in systemd package in Fedora: Unknown Bug description: It has been normal that applications first get the SIGTERM signal before SIGKILL on shutdown/reboot in order to successfully finish any pending tasks. Now it seem this logic has been changed to something else, causing problems to mosh and many others: https://bugs.launchpad.net/ubuntu/+source/mosh/+bug/1446982 SIGTERM suggestion can be seen here: http://unixhelp.ed.ac.uk/CGI/man-cgi?shutdown+8 I created this error report to find out the correct way for applications to fix this problem or to create one fix to systemd, bringing back the old BSD shutdown functionality. This report is for Ubuntu 15.04. SRU TEST CASE: - Open a terminal, enter some commands, then run reboot. - After a reboot, chances are very high that your bash history does not contain your most recently typed commands - With the updated package, the bash history should be intact. REGRESSION POTENTIAL: - The original commit was applied because of an inherent race condition with cgroup's release_agent -- in rare corner cases an nspawn container (probably also LXC) can miss them. In that case it's possible that you instead get a 90s timeout on the unit that is shutting down. But this does not mean data loss, just a rare shutdown hang from containers (for the record, I never actually saw that hanging with LXC), so I think it's a good trade-off. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1448259/+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 1437375] Please test proposed package
Hello bugproxy, or anyone else affected, Accepted systemd into vivid-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/219-7ubuntu5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- 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/1437375 Title: [udev] Adding Austin adapter to Ubuntu partition take over system network interface Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Vivid: Fix Committed Status in systemd source package in Wily: Fix Committed Bug description: [Impact] This impacts any user of LPARs; upon adding physical network interfaces (or, realistically, any network interface at all, even virtual), the network interface which is used for system access and used to install the system may not appear in the same order after reboot. [Test Case] Requires access to logical partitions. 1) Install system 2) Add an physical network adapter to the partition 3) Reboot. Observed behavior: After reboot, the virtual adapter expected to be used is unavailable, the address is assigned to any other network adapter which may have been detected and used persistent addresses. Expected behavior The system should come up with network interfaces in the same order as before rebooting. [Regression Potential] Added virtual interfaces that should be not persist (because they are locally administered and thus may have their MAC address change) may come up as persistent devices due to the use of the ibmveth driver, and thus fail to work as expected. --- Problem Description: Adding Austin adapter to Ubuntu partition took over system network interface. This caused system to be off network connection. ver 1.5.4.3 - OS, HTX, Firmware and Machine details OS: GNU/Linux OS Version: Ubuntu Vivid Vervet (development branch) \n \l Kernel Version: 3.18.0-13-generic HTX Version: htxubuntu-322 Host Name: br14p08 Machine Serial No: IBM,0210800E7 Machine Type/Model: IBM,9119-MHE System FW Level: FW830.00 (SC830_021) BEFORE adding Austin adapter to br14p08: Before adding austin adapter to br14p05 (vio client), the system network is good. ubuntu@br14p08:~$ lsslot -cpci ubuntu@br14p08:~$ + eth0 U9119.MHE.10800E7-V8-C2-T1 Interpartition Logical LAN root@br14p08:~# lscfg |grep eth + eth0 U9119.MHE.10800E7-V8-C2-T1 root@br14p08:~# ifconfig eth0 Link encap:Ethernet HWaddr 16:59:c0:50:0a:02 inet addr:9.3.21.12 Bcast:9.3.21.255 Mask:255.255.254.0 inet6 addr: fe80::1459:c0ff:fe50:a02/64 Scope:Link inet6 addr: 2002:903:15f:290:1459:c0ff:fe50:a02/64 Scope:Global UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:37366 errors:0 dropped:16 overruns:0 frame:0 TX packets:153 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:2472739 (2.4 MB) TX bytes:22596 (22.5 KB) Interrupt:19 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) root@br14p08:~# ping br14p08 PING br14p08.aus.stglabs.ibm.com (9.3.21.12) 56(84) bytes of data. 64 bytes from br14p08.aus.stglabs.ibm.com (9.3.21.12): icmp_seq=1 ttl=64 time=0.008 ms 64 bytes from br14p08.aus.stglabs.ibm.com (9.3.21.12): icmp_seq=2 ttl=64 time=0.004 ms 64 bytes from br14p08.aus.stglabs.ibm.com (9.3.21.12): icmp_seq=3 ttl=64 time=0.005 ms ^C ---
[Touch-packages] [Bug 1447807] Re: systemctl enable shows error on enabling a SysV service
Hello Eric, or anyone else affected, Accepted systemd into vivid-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/219-7ubuntu5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: systemd (Ubuntu Vivid) Status: In Progress = Fix Committed ** Tags added: verification-needed -- 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/1447807 Title: systemctl enable shows error on enabling a SysV service Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Vivid: Fix Committed Status in systemd source package in Wily: Fix Committed Bug description: SRU TEST CASE: -- Trying to enable a SysV init service which does not have a corresponding systemd unit results in an error: # systemctl enable pulseaudio Synchronizing state for pulseaudio.service with sysvinit using update-rc.d... Executing /usr/sbin/update-rc.d pulseaudio defaults Executing /usr/sbin/update-rc.d pulseaudio enable Failed to execute operation: No such file or directory /etc/init.d/pulseaudio actually does get enabled (check /etc/rc*/*pulse*), but the command fails with code 1 and you get that error message. With the fix the command succeeds. SRU Regression potential Low, the modes for sysv script + systemd unit as well as systemd unit only already have automatic tests, and now this scenario (sysv script only) has a test too. In the worst case this has the potential of completely breaking systemctl enable/disable, which can be worked around with changing symlinks manually, and isn't breaking the boot. Version details: Description: Ubuntu 15.04 Release: 15.04 systemd: Installed: 219-7ubuntu3 Candidate: 219-7ubuntu3 Version table: *** 219-7ubuntu3 0 500 http://us-west-2.ec2.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447807/+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 1447807] Re: systemctl enable shows error on enabling a SysV service
** Changed in: systemd (Ubuntu Wily) Status: Triaged = Fix Committed -- 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/1447807 Title: systemctl enable shows error on enabling a SysV service Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Vivid: Fix Committed Status in systemd source package in Wily: Fix Committed Bug description: SRU TEST CASE: -- Trying to enable a SysV init service which does not have a corresponding systemd unit results in an error: # systemctl enable pulseaudio Synchronizing state for pulseaudio.service with sysvinit using update-rc.d... Executing /usr/sbin/update-rc.d pulseaudio defaults Executing /usr/sbin/update-rc.d pulseaudio enable Failed to execute operation: No such file or directory /etc/init.d/pulseaudio actually does get enabled (check /etc/rc*/*pulse*), but the command fails with code 1 and you get that error message. With the fix the command succeeds. SRU Regression potential Low, the modes for sysv script + systemd unit as well as systemd unit only already have automatic tests, and now this scenario (sysv script only) has a test too. In the worst case this has the potential of completely breaking systemctl enable/disable, which can be worked around with changing symlinks manually, and isn't breaking the boot. Version details: Description: Ubuntu 15.04 Release: 15.04 systemd: Installed: 219-7ubuntu3 Candidate: 219-7ubuntu3 Version table: *** 219-7ubuntu3 0 500 http://us-west-2.ec2.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447807/+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 1448259] Re: Systemd does not send SIGTERM first on shutdown
Hello Olli, or anyone else affected, Accepted systemd into vivid-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/219-7ubuntu5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: systemd (Ubuntu Vivid) Status: Triaged = Fix Committed ** Tags added: verification-needed -- 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/1448259 Title: Systemd does not send SIGTERM first on shutdown Status in systemd: Unknown Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Vivid: Fix Committed Status in systemd package in Fedora: Unknown Bug description: It has been normal that applications first get the SIGTERM signal before SIGKILL on shutdown/reboot in order to successfully finish any pending tasks. Now it seem this logic has been changed to something else, causing problems to mosh and many others: https://bugs.launchpad.net/ubuntu/+source/mosh/+bug/1446982 SIGTERM suggestion can be seen here: http://unixhelp.ed.ac.uk/CGI/man-cgi?shutdown+8 I created this error report to find out the correct way for applications to fix this problem or to create one fix to systemd, bringing back the old BSD shutdown functionality. This report is for Ubuntu 15.04. SRU TEST CASE: - Open a terminal, enter some commands, then run reboot. - After a reboot, chances are very high that your bash history does not contain your most recently typed commands - With the updated package, the bash history should be intact. REGRESSION POTENTIAL: - The original commit was applied because of an inherent race condition with cgroup's release_agent -- in rare corner cases an nspawn container (probably also LXC) can miss them. In that case it's possible that you instead get a 90s timeout on the unit that is shutting down. But this does not mean data loss, just a rare shutdown hang from containers (for the record, I never actually saw that hanging with LXC), so I think it's a good trade-off. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1448259/+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 1449380] Re: systemctl default stops ifup@.service
Hello Martin, or anyone else affected, Accepted systemd into vivid-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/219-7ubuntu5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: systemd (Ubuntu Vivid) Status: Triaged = Fix Committed ** Tags added: verification-needed -- 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/1449380 Title: systemctl default stops ifup@.service Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Vivid: Fix Committed Status in systemd package in Debian: Fix Released Bug description: Running the display-manager autopkgtest causes eth0 to get shut down: Apr 28 08:30:15 autopkgtest ifdown[3267]: Internet Systems Consortium DHCP Client 4.3.1 Apr 28 08:30:15 autopkgtest ifdown[3267]: Copyright 2004-2014 Internet Systems Consortium. Apr 28 08:30:15 autopkgtest ifdown[3267]: All rights reserved. Apr 28 08:30:15 autopkgtest ifdown[3267]: For info, please visit https://www.isc.org/software/dhcp/ Apr 28 08:30:15 autopkgtest ifdown[3267]: Listening on LPF/eth0/52:54:00:12:34:56 Apr 28 08:30:15 autopkgtest ifdown[3267]: Sending on LPF/eth0/52:54:00:12:34:56 Apr 28 08:30:15 autopkgtest ifdown[3267]: Sending on Socket/fallback Apr 28 08:30:15 autopkgtest dhclient[3301]: DHCPRELEASE on eth0 to 10.0.2.2 port 67 (xid=0x3ca4ea0a) Apr 28 08:30:15 autopkgtest ifdown[3267]: DHCPRELEASE on eth0 to 10.0.2.2 port 67 (xid=0x3ca4ea0a) This breaks the ssh runner. SRU TEST CASE: == - Prepare a system which uses ifupdown (e. g. a standard adt-buildvm-ubuntu-cloud VM) - Start it, run sudo systemctl default - With vivid final's systemd, this will stop ifup@eth0.service and hence shut down eth0. ssh and other network connections will stop. - With this fix, ifup@eth0.service and eth0 should stay running/up. Regression potential: Very low: We don't use systemctl isolate during regular operation, and more elaborate commands like systemctl isolate rescue.target are currently broken on Ubuntu anyway due to our D-Bus shutdown hack. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1449380/+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 1448555] Re: network-manager does not autoconnect to wifi network after resume from suspend
I'm not sure if this is the same bug, but after upgrading to 15.04, I have to sudo systemctl restart NetworkManager to get back my network interfaces after a long suspend. If I test a short suspend/resume cycle, like a couple seconds, it works fine, but when I open my laptop in the morning I have to restart NetworkManager. I attached a journalctl excerpt; I closed the lid last night at 20:29, then opened it this morning at 08:09 and first tried the hardware switch, then eventually restarted NetworkManager. ** Attachment added: journalctl-networkmanager.log https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1448555/+attachment/4392723/+files/journalctl-networkmanager.log -- 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/1448555 Title: network-manager does not autoconnect to wifi network after resume from suspend Status in network-manager package in Ubuntu: Confirmed Bug description: After upgrading to 15.04 network manager does not reconnect to the wifi network after resuming from a suspend to memory. Workaround: disable and re-enable wireless network - connects immediately ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu15 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Apr 25 23:53:54 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-05-17 (708 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64+mac (20130424) IpRoute: default via 10.1.0.254 dev wlan0 proto static metric 1024 10.0.0.0/8 dev wlan0 proto kernel scope link src 10.1.0.103 169.254.0.0/16 dev wlan0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-04-25 (0 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlan0 wifi connected /org/freedesktop/NetworkManager/Devices/1 rsb_hs d8793959-2da1-4dc6-85ad-2dcf9e36e64b /org/freedesktop/NetworkManager/ActiveConnection/1 EC:88:92:61:E9:5F btdisconnected /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- -- -- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1448555/+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 1452584] Re: package systemd 219-7ubuntu4.1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1452584 Title: package systemd 219-7ubuntu4.1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1 Status in systemd package in Ubuntu: New Bug description: No se actualiza ProblemType: Package DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu4.1 Uname: Linux 4.0.1-040001-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Sun May 3 21:17:58 2015 DuplicateSignature: package:systemd:219-7ubuntu4.1:el subproceso instalado el script post-installation devolvió el código de salida de error 1 ErrorMessage: el subproceso instalado el script post-installation devolvió el código de salida de error 1 InstallationDate: Installed on 2015-04-24 (12 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) MachineType: ASUSTeK COMPUTER INC. K55VD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.0.1-040001-generic root=UUID=97975335-8df6-4e88-bcc5-a088230afdca ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4 SourcePackage: systemd Title: package systemd 219-7ubuntu4.1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/11/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K55VD.411 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K55VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK55VD.411:bd03/11/2013:svnASUSTeKCOMPUTERINC.:pnK55VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK55VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: K55VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1452584/+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 1452216] Re: libgcrypt11 not present in Vivid (15.04) - Spotify and other app issue.
@Seth Arnold: Several people have tried creating a link from libgcrypt11 to libgcrypt20 sudo ln -s /lib/x86_64-linux-gnu/libgcrypt.so.20.0.2 /lib/x86_64-linux-gnu/libgcrypt.so.11 respectively sudo ln -s /lib/i386-linux-gnu/libgcrypt.so.20.0.2 /lib/i386-linux-gnu/libgcrypt.so.11 and have received errors like spotify: /lib/x86_64-linux-gnu/libgcrypt.so.11: version `GCRYPT_1.2' not found (required by /opt/spotify/spotify-client/Data/libcef.so) So that seems not to be sufficiently binary compatible. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libgcrypt11 in Ubuntu. https://bugs.launchpad.net/bugs/1452216 Title: libgcrypt11 not present in Vivid (15.04) - Spotify and other app issue. Status in libgcrypt11 package in Ubuntu: Confirmed Bug description: The package libgcrypt11 is not present anymore in official ubuntu vivid repositories. This cause app crash, such as spotify: spotify: error while loading shared libraries: libgcrypt.so.11: cannot open shared object file: No such file or directory Current workaround is to manually download the .deb package from launchpad/debian package such as https://packages.debian.org/wheezy/libgcrypt11 and manually install with dpkg. Linux SAGITTER 3.19.0-15-generic #15-Ubuntu SMP Thu Apr 16 23:32:37 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Distributor ID: Ubuntu Description: Ubuntu 15.04 Release: 15.04 Codename: vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgcrypt11/+bug/1452216/+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 1452606] Re: package libqtcore4 4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu6 failed to install/upgrade: trying to overwrite shared '/etc/xdg/Trolltech.conf', which is different from oth
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/1452606 Title: package libqtcore4 4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu6 failed to install/upgrade: trying to overwrite shared '/etc/xdg/Trolltech.conf', which is different from other instances of package libqtcore4:i386 Status in qt4-x11 package in Ubuntu: New Bug description: encountered while installing skype from the repo. ProblemType: Package DistroRelease: Ubuntu 15.04 Package: libqtcore4 4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu6 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Thu May 7 02:12:14 2015 DuplicateSignature: package:libqtcore4:4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu6:trying to overwrite shared '/etc/xdg/Trolltech.conf', which is different from other instances of package libqtcore4:i386 ErrorMessage: trying to overwrite shared '/etc/xdg/Trolltech.conf', which is different from other instances of package libqtcore4:i386 InstallationDate: Installed on 2015-05-03 (3 days ago) InstallationMedia: Lubuntu 15.04 Vivid Vervet - Release amd64 (20150422) RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4 SourcePackage: qt4-x11 Title: package libqtcore4 4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu6 failed to install/upgrade: trying to overwrite shared '/etc/xdg/Trolltech.conf', which is different from other instances of package libqtcore4:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/1452606/+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 1425398] Re: Apparmor uses rsyslogd profile for different processes - utopic HWE
It seems that issue is gone with this fix. 1. Installed the package from trusty-proposed # LANG=C apt-cache policy rsyslog rsyslog: Installed: 7.4.4-1ubuntu2.6 Candidate: 7.4.4-1ubuntu2.6 Version table: *** 7.4.4-1ubuntu2.6 0 400 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64 Packages 100 /var/lib/dpkg/status 7.4.4-1ubuntu2.5 0 500 http://ru.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 7.4.4-1ubuntu2.3 0 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 7.4.4-1ubuntu2 0 500 http://ru.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 2. commented out the workaround /dev/log rwl, from /etc/apparmor.d/local/usr.sbin.rsyslogd 3. Rebooted to the latest Utopic HWE kernel # uname -a Linux emma 3.16.0-37-generic #51~14.04.1-Ubuntu SMP Wed May 6 15:23:14 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux 4. The issue is gone: # dmesg | grep DENIED # -- 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/1425398 Title: Apparmor uses rsyslogd profile for different processes - utopic HWE Status in apparmor package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in linux-lts-utopic package in Ubuntu: Invalid Status in rsyslog package in Ubuntu: Fix Released Status in apparmor source package in Trusty: In Progress Status in linux source package in Trusty: Confirmed Status in linux-lts-utopic source package in Trusty: Invalid Status in rsyslog source package in Trusty: Fix Committed Bug description: [rsyslog impact] This bug prevents rsyslog from receiving all events from other services on trusty when the utopic-hwe (and newer) kernels are used. The rsyslog SRU adds an additional permission (read access to /dev/log) to the rsyslog apparmor policy to allow this to work. [rsyslog test case] (1) Ensure the rsyslog apparmor policy is set to enforce; it should show up listed in the XX profiles are in enforce mode. section reported by sudo aa-status (if it's disabled, do sudo aa-enforce rsyslogd). (2) Install the utopic or newer hwe enablement stack reboot into the kernel. Using the logger(1) utility should generate log messages (e.g. logger foo) that are recorded in syslog; with this bug, they will be blocked (grep DENIED /var/log/syslog). [rsyslog regression potential] The only change to rsyslog in the SRU is a slight loosening of the rsyslog apparmor policy. The risk of an introduced regression is small. [rsyslog addition info] The qa-regression-testing script is useful for verifying that rsyslog is still functioning properly (http://bazaar.launchpad.net/~ubuntu-bugcontrol/qa-regression-testing/master/view/head:/scripts/test-rsyslog.py) [Original description] I've noticed that apparmor loads /usr/sbin/rsyslogd profile for completely unrelated processes: Feb 25 08:36:19 emma kernel: [ 134.796218] audit: type=1400 audit(1424842579.429:245): apparmor=DENIED operation=sendmsg profile=/usr/sbin/rsyslogd name=/dev/log pid=4002 comm=sshd requested_mask=r denied_mask=r fsuid=0 ouid=0 Feb 25 08:36:23 emma kernel: [ 139.330989] audit: type=1400 audit(1424842583.965:246): apparmor=DENIED operation=sendmsg profile=/usr/sbin/rsyslogd name=/dev/log pid=4080 comm=sudo requested_mask=r denied_mask=r fsuid=0 ouid=0 Feb 25 08:35:42 emma kernel: [ 97.912402] audit: type=1400 audit(1424842542.565:241): apparmor=DENIED operation=sendmsg profile=/usr/sbin/rsyslogd name=/dev/log pid=2436 comm=whoopsie requested_mask=r denied_mask=r fsuid=103 ouid=0 Feb 25 08:34:43 emma kernel: [ 38.867998] audit: type=1400 audit(1424842483.546:226): apparmor=DENIED operation=sendmsg profile=/usr/sbin/rsyslogd name=/dev/log pid=3762 comm=ntpd requested_mask=r denied_mask=r fsuid=0 ouid=0 I'm not sure how apparmor decides which profile to use for which task, but is shouldn't load '/usr/sbin/rsyslogd' profile for sshd/ntpd/etc. I'm running: # lsb_release -rd Description: Ubuntu 14.04.2 LTS Release: 14.04 # dpkg -l | grep apparmor ii apparmor2.8.95~2430-0ubuntu5.1 amd64User-space parser utility for AppArmor ii apparmor-profiles 2.8.95~2430-0ubuntu5.1 all Profiles for AppArmor Security policies ii apparmor-utils 2.8.95~2430-0ubuntu5.1 amd64Utilities for controlling AppArmor ii libapparmor-perl2.8.95~2430-0ubuntu5.1 amd64AppArmor library Perl bindings ii libapparmor1:amd64 2.8.95~2430-0ubuntu5.1 amd64changehat AppArmor library ii python3-apparmor2.8.95~2430-0ubuntu5.1 amd64AppArmor Python3 utility library ii
[Touch-packages] [Bug 1393729] Re: package avahi-daemon 0.6.31-4ubuntu3 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: avahi (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1393729 Title: package avahi-daemon 0.6.31-4ubuntu3 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in avahi package in Ubuntu: Confirmed Bug description: Updating a Vivid Vervet system (on Virtual Box v. 4.3.18) by running sudo apt-get update sudo apt-get dist-upgrade at TTY1. Several packages where successfully upgraded. The only error I got was with avahi-daemon getting the following: Preparing to unpack .../avahi-daemon_0.6.31-4ubuntu4_i386.deb ... Job for avahi-daemon.service canceled. invoke-rc.d: initscript avahi-daemon, action stop failed. dpkg: warning: subprocess old pre-removal script returned error exit status 1 dpkg: trying script from the new package instead ... Job for avahi-daemon.service canceled. invoke-rc.d: initscript avahi-daemon, action stop failed. dpkg: error processing archive /var/cache/apt/archives/avahi-daemon_0.6.31-4ubuntu4_i386.deb (--unpack): subprocess new pre-removal script returned error exit status 1 ProblemType: Package DistroRelease: Ubuntu 15.04 Package: avahi-daemon 0.6.31-4ubuntu4 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic i686 ApportVersion: 2.14.7-0ubuntu10 Architecture: i386 Date: Tue Nov 18 09:27:13 2014 DuplicateSignature: package:avahi-daemon:0.6.31-4ubuntu3:subprocess new pre-removal script returned error exit status 1 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2014-07-15 (125 days ago) InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Alpha i386 (20140506) SourcePackage: avahi Title: package avahi-daemon 0.6.31-4ubuntu3 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1393729/+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 1441068] Re: lxc-destroy fails on btrfs subvolumes
This also occurs for limited user containers, without asking for a btrfs backing store. This is more of a problem as the limited user can't delete (or even detect) the subvolume themselves. On a standard whole-partition-as-btrfs system, as setup by the installer, this looks like: ID 257 gen 46021 top level 5 path @ ID 258 gen 46021 top level 5 path @home ... ID 373 gen 35464 top level 257 path @/var/lib/machines ID 374 gen 45983 top level 258 path faux/.local/share/lxc/vivid/rootfs/var/lib/machines ID 395 gen 45995 top level 258 path faux/.local/share/lxc/vivid2/rootfs/var/lib/machines ID 396 gen 46011 top level 258 path faux/.local/share/lxc/vivid3/rootfs/var/lib/machines ID 397 gen 46014 top level 258 path faux/.local/share/lxc/vivid4/rootfs/var/lib/machines -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1441068 Title: lxc-destroy fails on btrfs subvolumes Status in lxc package in Ubuntu: Triaged Bug description: $ sudo lxc-destroy -n adt-vivid [sudo] password for martin: lxc_container: utils.c: _recursive_rmdir_onedev: 147 _recursive_rmdir_onedev: failed to delete /srv/lxc/adt-vivid/rootfs/var/lib lxc_container: utils.c: _recursive_rmdir_onedev: 147 _recursive_rmdir_onedev: failed to delete /srv/lxc/adt-vivid/rootfs/var lxc_container: utils.c: _recursive_rmdir_onedev: 147 _recursive_rmdir_onedev: failed to delete /srv/lxc/adt-vivid/rootfs lxc_container: lxccontainer.c: container_destroy: 2050 Error destroying rootfs for adt-vivid Destroying adt-vivid failed This is because the container rootfs has a btrfs subvolume: ID 557 gen 97073 top level 266 path @srv/lxc/adt- vivid/rootfs/var/lib/machines After sudo btrfs subvolume delete /srv/lxc/adt- vivid/rootfs/var/lib/machines I can remove the container. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lxc 1.1.1-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3 Uname: Linux 3.19.0-12-generic x86_64 ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Apr 7 11:51:51 2015 EcryptfsInUse: Yes SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx lxc.conf: lxc.lxcpath = /srv/lxc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1441068/+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 1452584] Re: package systemd 219-7ubuntu4.1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1
Thank you for taking the time to report this bug and helping to make Ubuntu better. Reviewing your dmesg attachment in this bug report it seems that there is a problem with your hardware. I recommend performing a back up and then investigating the situation. Measures you might take include checking cable connections and using software tools to investigate the health of your hardware. In the event that is is not in fact an error with your hardware please set the bug's status back to New. Thanks and good luck! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: hardware-error ** Changed in: systemd (Ubuntu) Importance: Undecided = Low ** Changed in: systemd (Ubuntu) Status: New = Invalid -- 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/1452584 Title: package systemd 219-7ubuntu4.1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1 Status in systemd package in Ubuntu: Invalid Bug description: No se actualiza ProblemType: Package DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu4.1 Uname: Linux 4.0.1-040001-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Sun May 3 21:17:58 2015 DuplicateSignature: package:systemd:219-7ubuntu4.1:el subproceso instalado el script post-installation devolvió el código de salida de error 1 ErrorMessage: el subproceso instalado el script post-installation devolvió el código de salida de error 1 InstallationDate: Installed on 2015-04-24 (12 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) MachineType: ASUSTeK COMPUTER INC. K55VD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.0.1-040001-generic root=UUID=97975335-8df6-4e88-bcc5-a088230afdca ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4 SourcePackage: systemd Title: package systemd 219-7ubuntu4.1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/11/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K55VD.411 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K55VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK55VD.411:bd03/11/2013:svnASUSTeKCOMPUTERINC.:pnK55VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK55VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: K55VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1452584/+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 1414930] Re: [Lenovo ThinkPad 2015 models] Buttons of Synaptics trackpad doesn't work
** Changed in: linux (Ubuntu Utopic) Status: Confirmed = Fix Committed -- 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/1414930 Title: [Lenovo ThinkPad 2015 models] Buttons of Synaptics trackpad doesn't work Status in HWE Next Project: In Progress Status in The Linux Kernel: Fix Released Status in libinput package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in linux source package in Trusty: Confirmed Status in systemd source package in Trusty: Confirmed Status in linux source package in Utopic: Fix Committed Status in systemd source package in Utopic: Confirmed Bug description: Lenovo X1 3rd Carbon (201411-16196) Steps to reproduce the bug: 1, Log in to system 2, Click left/right/middle buttons of the touchpad Actual result: No response after clicking the buttons Expected results: Buttons work as expected behavirour ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-45-generic 3.13.0-45.74 [modified: boot/vmlinuz-3.13.0-45-generic] ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13 Uname: Linux 3.13.0-45-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: u 1598 F pulseaudio /dev/snd/controlC0: u 1598 F pulseaudio CurrentDesktop: Unity Date: Tue Jan 27 02:48:23 2015 HibernationDevice: RESUME=UUID=c553e9ba-b74b-43ad-8cf2-496531261e0f InstallationDate: Installed on 2015-01-27 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20150126) MachineType: LENOVO 20BTZ09ZUS ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic root=UUID=1d34e685-c98b-41f3-b649-87770517b194 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-45-generic N/A linux-backports-modules-3.13.0-45-generic N/A linux-firmware 1.127.11 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/27/2014 dmi.bios.vendor: LENOVO dmi.bios.version: N14ET24W (1.02 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BTZ09ZUS dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN14ET24W(1.02):bd10/27/2014:svnLENOVO:pn20BTZ09ZUS:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BTZ09ZUS:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BTZ09ZUS dmi.product.version: ThinkPad X1 Carbon 3rd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1414930/+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 1319626] Re: Ubuntu One Captcha too hard to enter correctly
How has this not been fixed yet? this problem has existed for years... The captcha's almost always have some string of illegible r,n,u and m's. It's so stupid. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntuone-client-data in Ubuntu. https://bugs.launchpad.net/bugs/1319626 Title: Ubuntu One Captcha too hard to enter correctly Status in ubuntuone-client-data package in Ubuntu: Confirmed Bug description: I tried to create a new Ubuntu One while setting up the Sofware Center suggested apps (which required an Ubuntu One account) and ended frustated. The Captcha is really hard, I gave up on the account creation after 10 tries, I'm a male on my twentys with normal vision and could not decipher the Captcha. Not even 4***.org captchas gives me troubles as those on the Ubuntu One register page. I suggest to improve the captchas so they're not so difficult to read, I can just imagie my dad would just close that window if he saw such a hard captcha. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubuntuone-client-data 13.05-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.1 Architecture: amd64 CurrentDesktop: Unity Date: Wed May 14 21:29:17 2014 Dependencies: InstallationDate: Installed on 2014-05-15 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) PackageArchitecture: all SourcePackage: ubuntuone-client-data UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntuone-client-data/+bug/1319626/+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 1452308] Re: Mysql Workbench repeated menu options when using locally integrated menus
** Also affects: unity (Ubuntu) Importance: Undecided Status: New ** Also affects: compiz (Ubuntu) Importance: Undecided Status: New -- 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/1452308 Title: Mysql Workbench repeated menu options when using locally integrated menus Status in compiz package in Ubuntu: New Status in mysql-workbench package in Ubuntu: New Status in unity package in Ubuntu: New Bug description: When using locally integrated menus, Mysql workbench becomes a menu- nightmare of titanic proportions. There seems to be two sets of menues being repeated. The options are not the same on the first file menu as on the second. It's just better to look at the screenshot attached, actually. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: mysql-workbench 6.2.3+dfsg-7build1 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Wed May 6 15:50:43 2015 InstallationDate: Installed on 2015-05-01 (5 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) SourcePackage: mysql-workbench UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1452308/+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 1452606] [NEW] package libqtcore4 4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu6 failed to install/upgrade: trying to overwrite shared '/etc/xdg/Trolltech.conf', which is different from o
Public bug reported: encountered while installing skype from the repo. ProblemType: Package DistroRelease: Ubuntu 15.04 Package: libqtcore4 4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu6 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Thu May 7 02:12:14 2015 DuplicateSignature: package:libqtcore4:4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu6:trying to overwrite shared '/etc/xdg/Trolltech.conf', which is different from other instances of package libqtcore4:i386 ErrorMessage: trying to overwrite shared '/etc/xdg/Trolltech.conf', which is different from other instances of package libqtcore4:i386 InstallationDate: Installed on 2015-05-03 (3 days ago) InstallationMedia: Lubuntu 15.04 Vivid Vervet - Release amd64 (20150422) RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4 SourcePackage: qt4-x11 Title: package libqtcore4 4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu6 failed to install/upgrade: trying to overwrite shared '/etc/xdg/Trolltech.conf', which is different from other instances of package libqtcore4:i386 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: qt4-x11 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package package-conflict vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/1452606 Title: package libqtcore4 4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu6 failed to install/upgrade: trying to overwrite shared '/etc/xdg/Trolltech.conf', which is different from other instances of package libqtcore4:i386 Status in qt4-x11 package in Ubuntu: New Bug description: encountered while installing skype from the repo. ProblemType: Package DistroRelease: Ubuntu 15.04 Package: libqtcore4 4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu6 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Thu May 7 02:12:14 2015 DuplicateSignature: package:libqtcore4:4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu6:trying to overwrite shared '/etc/xdg/Trolltech.conf', which is different from other instances of package libqtcore4:i386 ErrorMessage: trying to overwrite shared '/etc/xdg/Trolltech.conf', which is different from other instances of package libqtcore4:i386 InstallationDate: Installed on 2015-05-03 (3 days ago) InstallationMedia: Lubuntu 15.04 Vivid Vervet - Release amd64 (20150422) RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4 SourcePackage: qt4-x11 Title: package libqtcore4 4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu6 failed to install/upgrade: trying to overwrite shared '/etc/xdg/Trolltech.conf', which is different from other instances of package libqtcore4:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/1452606/+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 1193822] Re: dh-migrations: Typo in package description: packaged
** Changed in: session-migration (Ubuntu) Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to session-migration in Ubuntu. https://bugs.launchpad.net/bugs/1193822 Title: dh-migrations: Typo in package description: packaged Status in Package Descriptions for Ubuntu (to make translation easy): Triaged Status in session-migration package in Ubuntu: Fix Committed Bug description: Package: dh-migrations Version: 0.2 Hello, There's a typo in string #911 in the following sentence: ...operations on the installed packaged. (packaged should be replaced with packages) Link: https://translations.launchpad.net/ddtp-ubuntu/raring/+pots /ddtp-ubuntu-main/fr/911 Regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ddtp-ubuntu/+bug/1193822/+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 1452610] [NEW] /etc/modprobe.d is not a file
Public bug reported: /var/log/upstart# cat lightdm.log /etc/modprobe.d is not a file /etc/modprobe.d is not a file /etc/modprobe.d is not a file /etc/modprobe.d is not a file update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf /etc/modprobe.d is not a file /etc/modprobe.d is not a file /etc/modprobe.d is not a file /etc/modprobe.d is not a file update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf /etc/modprobe.d is not a file /etc/modprobe.d is not a file /etc/modprobe.d is not a file /etc/modprobe.d is not a file update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf Above looks weird... modprobe.d is a directory why update-alternatives are called?! This is lightdm 1.10.5-0ubuntu1 ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New -- 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/1452610 Title: /etc/modprobe.d is not a file Status in lightdm package in Ubuntu: New Bug description: /var/log/upstart# cat lightdm.log /etc/modprobe.d is not a file /etc/modprobe.d is not a file /etc/modprobe.d is not a file /etc/modprobe.d is not a file update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf /etc/modprobe.d is not a file /etc/modprobe.d is not a file /etc/modprobe.d is not a file /etc/modprobe.d is not a file update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf /etc/modprobe.d is not a file /etc/modprobe.d is not a file /etc/modprobe.d is not a file /etc/modprobe.d is not a file update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf Above looks weird... modprobe.d is a directory why update- alternatives are called?! This is lightdm 1.10.5-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1452610/+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 1448446] Re: Cannot login into Ubuntu 15.04 after upgrade
ignore my previous post, discovered the problem is addressed to something else -- 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/1448446 Title: Cannot login into Ubuntu 15.04 after upgrade Status in lightdm package in Ubuntu: Confirmed Bug description: After I upgraded my Ubuntu 14.10 to 15.04, I wanted to login into the GUI system. I have 4 users on my system. 3 of them is unable to login, 1 is able. The message is unsuccessful login. Terminal logins work for all users. I use lightdm. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1448446/+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 1452616] Re: Ubuntu Web Browser identified as old Safari in gmail
That also applies to unity Gmail webapp which also opens webbrowser-app Would be nice if gmai webapp and webbrowser nicely open gmail mobile version as the google chrome with the folowing link: https://mail.google.com/mail/mu/mp/912/?mui=ca#tl/priority/%5Eu -- 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/1452616 Title: Ubuntu Web Browser identified as old Safari in gmail Status in webbrowser-app package in Ubuntu: New Bug description: Ubuntu Web Browser identified as old Safari in gmail. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: webbrowser-app 0.23+15.04.20150416-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu May 7 11:29:34 2015 SourcePackage: webbrowser-app UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1452616/+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 1452640] [NEW] after upgarding to vivid version of ubuntu VPN connections are not working
Public bug reported: I've just upgraded to the new version of Ubuntu distrib, called Vivid and now the network manager doesn't connect to the VPN server. In the earlier version there was no problem with the connecting.A VPN kapcosolat meghiúsult érvénytelen titkos VPN információk miatt ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu15.1 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic i686 ApportVersion: 2.17.2-0ubuntu1 Architecture: i386 CurrentDesktop: GNOME-Flashback:Unity Date: Thu May 7 11:16:54 2015 EcryptfsInUse: Yes IfupdownConfig: auto lo iface lo inet loopback InstallationDate: Installed on 2011-04-17 (1480 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) IpRoute: default via 192.168.42.129 dev usb0 proto static metric 1024 169.254.0.0/16 dev usb0 scope link metric 1000 192.168.42.0/24 dev usb0 proto kernel scope link src 192.168.42.77 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WiMAXEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-05-04 (2 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTIONCON-UUID CON-PATH usb0ethernet connected /org/freedesktop/NetworkManager/Devices/3 Automatikus Ethernet 926ed2d3-404f-4b1a-8e71-9c5ff6e44c33 /org/freedesktop/NetworkManager/ActiveConnection/0 wlan0 wifi disconnected /org/freedesktop/NetworkManager/Devices/2 -- ---- eth0ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 vivid -- 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/1452640 Title: after upgarding to vivid version of ubuntu VPN connections are not working Status in network-manager package in Ubuntu: New Bug description: I've just upgraded to the new version of Ubuntu distrib, called Vivid and now the network manager doesn't connect to the VPN server. In the earlier version there was no problem with the connecting.A VPN kapcosolat meghiúsult érvénytelen titkos VPN információk miatt ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu15.1 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic i686 ApportVersion: 2.17.2-0ubuntu1 Architecture: i386 CurrentDesktop: GNOME-Flashback:Unity Date: Thu May 7 11:16:54 2015 EcryptfsInUse: Yes IfupdownConfig: auto lo iface lo inet loopback InstallationDate: Installed on 2011-04-17 (1480 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) IpRoute: default via 192.168.42.129 dev usb0 proto static metric 1024 169.254.0.0/16 dev usb0 scope link metric 1000 192.168.42.0/24 dev usb0 proto kernel scope link src 192.168.42.77 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WiMAXEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-05-04 (2 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTIONCON-UUID CON-PATH usb0ethernet connected /org/freedesktop/NetworkManager/Devices/3 Automatikus Ethernet 926ed2d3-404f-4b1a-8e71-9c5ff6e44c33 /org/freedesktop/NetworkManager/ActiveConnection/0 wlan0 wifi disconnected /org/freedesktop/NetworkManager/Devices/2 ------ eth0ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 ------ lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 ------ nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To
[Touch-packages] [Bug 1448834] [NEW] mouse battery not shown after upgrade
You have been subscribed to a public bug: In Xubuntu 14.04 and 14.10 the power manager dropdown menu showed the battery level in my wireless logitech mouse. However after upgrading to 15.04 the mouse battery status is not shown. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xfce4-power-manager 1.4.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Apr 26 19:49:19 2015 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xfce4-power-manager UpgradeStatus: Upgraded to vivid on 2015-04-23 (3 days ago) ** Affects: gnome-power-manager (Ubuntu) Importance: Undecided Status: New ** Affects: upower (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- mouse battery not shown after upgrade https://bugs.launchpad.net/bugs/1448834 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1449380] Re: systemctl default stops ifup@.service
** Changed in: systemd (Ubuntu) Milestone: vivid-updates = None -- 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/1449380 Title: systemctl default stops ifup@.service Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Vivid: Fix Committed Status in systemd package in Debian: Fix Released Bug description: Running the display-manager autopkgtest causes eth0 to get shut down: Apr 28 08:30:15 autopkgtest ifdown[3267]: Internet Systems Consortium DHCP Client 4.3.1 Apr 28 08:30:15 autopkgtest ifdown[3267]: Copyright 2004-2014 Internet Systems Consortium. Apr 28 08:30:15 autopkgtest ifdown[3267]: All rights reserved. Apr 28 08:30:15 autopkgtest ifdown[3267]: For info, please visit https://www.isc.org/software/dhcp/ Apr 28 08:30:15 autopkgtest ifdown[3267]: Listening on LPF/eth0/52:54:00:12:34:56 Apr 28 08:30:15 autopkgtest ifdown[3267]: Sending on LPF/eth0/52:54:00:12:34:56 Apr 28 08:30:15 autopkgtest ifdown[3267]: Sending on Socket/fallback Apr 28 08:30:15 autopkgtest dhclient[3301]: DHCPRELEASE on eth0 to 10.0.2.2 port 67 (xid=0x3ca4ea0a) Apr 28 08:30:15 autopkgtest ifdown[3267]: DHCPRELEASE on eth0 to 10.0.2.2 port 67 (xid=0x3ca4ea0a) This breaks the ssh runner. SRU TEST CASE: == - Prepare a system which uses ifupdown (e. g. a standard adt-buildvm-ubuntu-cloud VM) - Start it, run sudo systemctl default - With vivid final's systemd, this will stop ifup@eth0.service and hence shut down eth0. ssh and other network connections will stop. - With this fix, ifup@eth0.service and eth0 should stay running/up. Regression potential: Very low: We don't use systemctl isolate during regular operation, and more elaborate commands like systemctl isolate rescue.target are currently broken on Ubuntu anyway due to our D-Bus shutdown hack. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1449380/+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 1430694] Re: Update Facebook permissions to 2.0 API
I tested the fix also in trusty-proposed, and everything works fine: I could create a facebook account, and then I tried the photo search in the Dash, which showed me recent photos from facebook. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1430694 Title: Update Facebook permissions to 2.0 API Status in Online Accounts: Account plugins: In Progress Status in the base for Ubuntu mobile products: Fix Released Status in account-plugins package in Ubuntu: Fix Released Status in account-plugins source package in Trusty: Fix Committed Status in account-plugins source package in Utopic: Fix Committed Status in account-plugins package in Ubuntu RTM: Fix Released Bug description: The 1.0 API is being deprecated on April 30, 2015. [Impact] Depending on how facebook decides to handle the deprecation, there's the possibility that creating facebook accounts from Ubuntu Online Accounts will just stop working, if our OAuth request (which uses deprecated parameters) gets declined. [Test case] Until the deprecation actually takes place, we won't be able to reproduce the bug. According to the Facebook official documentation, the v1.0 API will stop working on April 30th, 2015: https://developers.facebook.com/docs/apps/changelog [Regression potential] Very low: the new Facebook v2.0 API is already active, and we've been using it in Vivid without issues. A quick smoke test (just create a Facebook account from the System Settings - Online Accounts pane) is anyway advised, to be absolutely sure. To manage notifications about this bug go to: https://bugs.launchpad.net/account-plugins/+bug/1430694/+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 1338527] Re: Bottle Gourd Is Nutritious And Healthy
** Package changed: powerd (Ubuntu) = null-and-void ** Information type changed from Public to Private -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to powerd in Ubuntu. https://bugs.launchpad.net/bugs/1338527 Title: Bottle Gourd Is Nutritious And Healthy Status in NULL Project: Invalid Bug description: Lauki should be tasted before preparation or preparing its succus. Taste lauki can be detrimental for wellbeing. Do not eat raw lauki it can hurt your stomach, determine wee size lauki as big situation lauki may jazz calumnious chemical to raise it big. The succus of bottle gourd is rich and book as a penalization for umpteen diseases similar diabetes, diarrhea, and low execution pressure etc. bottleful bottle humour with a lowercase seasoning in it should be taken every day. Bottleful vine humour should not be mixed with any different juice, it may be offensive. It should be seized in summers to keep you from experience of sodium, tiredness, quenches desire. Bottleful bottle humor mixed with sesame oil is an powerful penalty for insomnia. The salmagundi should be applied on scalp every night. Gourd humor also provides hair tutelage. It prevents graying of pilus at an embryotic age. Cure filament season or depilation as intimately. Having vine humour regularly helps tegument to brightness and emit. Remove pimples spatiality your skin. Women those who receive from oppressive injury during menstrual wheel should know bottle juice on standard assumption so as to keep full hurt. http://forskolinfuelfacts.com/ To manage notifications about this bug go to: https://bugs.launchpad.net/null-and-void/+bug/1338527/+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 1364653] Re: Daily Recurring Events need refresh to appear when created from DayView
The reason why the modelChange was not triggered in such case is that for occurrence cases, Pim(Organizer model) trigger modelChange signal only if event id is null , however eds plugin sets event id for occurrence event which cause this bug occurs. Same case for removing occurrence event. Enclose pls find the patch. ** Patch added: fix-occurrence.patch https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1364653/+attachment/4392801/+files/fix-occurrence.patch -- 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/1364653 Title: Daily Recurring Events need refresh to appear when created from DayView Status in Calendar application for Ubuntu devices: Confirmed Status in qtorganizer5-eds package in Ubuntu: New Bug description: When I create a daily recurring event from the DayView that starts on that day, the EventBubble does not immediately appear on the current Day. I can swipe to go to future days, and the EventBubble appears there. If I swipe back to return to the original Day, or I go to a different view (MonthView, WeekView, etc.) the event appears. Since the EventBubble appears after re-navigating to the page in any way, this appears to be a refreshing problem, where the DayView isn't updated after creating a recurring event. Steps to Reproduce 1) Open the Calendar App, and go to any day on the DayView. 2) Create a recurring event starting on that day, which re-occurs daily. 3) Save the new event and return to the DayView. The EventBubble should not appear on the DayView for the current Day. Expected: The EventBubble should appear on the DayView page immediately after returning from creating the event. A reproduction of this behavior can be seen at: https://www.youtube.com/watch?v=9NK9m8ZznrAfeature=youtu.be To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1364653/+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 1452633] [NEW] gtk-update-icons-cache-3.0 is weird during upgrade
Public bug reported: it looks like it expects gtk2 pixbuf stuff?! (gtk-update-icon-cache-3.0:29280): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk- pixbuf-2.0/2.10.0/loaders.cache': No such file or directory This likely means that your installation is broken. Try running the command gdk-pixbuf-query-loaders /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache to make things work again for the time being. (gtk-update-icon-cache-3.0:29282): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk- pixbuf-2.0/2.10.0/loaders.cache': No such file or directory This likely means that your installation is broken. Try running the command gdk-pixbuf-query-loaders /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache to make things work again for the time being. ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1452633 Title: gtk-update-icons-cache-3.0 is weird during upgrade Status in gtk+3.0 package in Ubuntu: New Bug description: it looks like it expects gtk2 pixbuf stuff?! (gtk-update-icon-cache-3.0:29280): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk- pixbuf-2.0/2.10.0/loaders.cache': No such file or directory This likely means that your installation is broken. Try running the command gdk-pixbuf-query-loaders /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache to make things work again for the time being. (gtk-update-icon-cache-3.0:29282): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk- pixbuf-2.0/2.10.0/loaders.cache': No such file or directory This likely means that your installation is broken. Try running the command gdk-pixbuf-query-loaders /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache to make things work again for the time being. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1452633/+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 1452727] Re: rc-local.service hangs
fstrim -v / aah - you asked for it, you get it, I guess :-) Please notice that you don't really need that, /etc/cron.weekly/fstrim already takes care of trimming. ** Changed in: systemd (Ubuntu) Status: Incomplete = Invalid -- 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/1452727 Title: rc-local.service hangs Status in systemd package in Ubuntu: Invalid Bug description: The boot is very slow more than 130 seconds because of: 1min 8.191s rc-local.service... Using upstart works perfectly and fast. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1452727/+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 1169119] Re: package coreutils 8.13-3.2ubuntu2 failed to install/upgrade: cannot copy extracted data for './bin/dd' to '/bin/dd.dpkg-new': unexpected end of file or stream
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that there was an error on your system when trying to install a particular package. Please execute the following command, as it will clear your package cache, in a terminal: sudo apt-get clean Then try performing the package operation again. This will likely resolve your issue, but the failure can be caused by filesystem or memory corruption. So please also run a fsck on your filesystem(s) and a memory test. If this does not resolve your bug please set its status back to New. Thanks in advance! ** Changed in: coreutils (Ubuntu) Status: New = Invalid ** Changed in: coreutils (Ubuntu) Importance: Undecided = Low ** Tags added: corrupted-package -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1169119 Title: package coreutils 8.13-3.2ubuntu2 failed to install/upgrade: cannot copy extracted data for './bin/dd' to '/bin/dd.dpkg-new': unexpected end of file or stream Status in coreutils package in Ubuntu: Invalid Bug description: Eu não sei o que aconteceu. Instalei o Ubuntu 12.10 normalmente e, após reinicar o computador, fui fazer a atualização dos pacotes. Então apareceu este problema, não sendo possivel concluir a atualização. ProblemType: Package DistroRelease: Ubuntu 12.10 Package: coreutils 8.13-3.2ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-27.46-generic 3.5.7.7 Uname: Linux 3.5.0-27-generic i686 ApportVersion: 2.6.1-0ubuntu3 Architecture: i386 Date: Mon Apr 15 05:44:04 2013 ErrorMessage: cannot copy extracted data for './bin/dd' to '/bin/dd.dpkg-new': unexpected end of file or stream InstallationMedia: This SourcePackage: coreutils Title: package coreutils 8.13-3.2ubuntu2 failed to install/upgrade: cannot copy extracted data for './bin/dd' to '/bin/dd.dpkg-new': unexpected end of file or stream UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1169119/+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 1302004] Re: Indicator-datetime still doesn't list all events for today's date (Trusty/Utopic/Vivid)
I'm also affected by this issue in Trusty. I think that, for today, the indicator should list the events that END after the current time, instead of the ones that START after it. -- 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/1302004 Title: Indicator-datetime still doesn't list all events for today's date (Trusty/Utopic/Vivid) Status in indicator-datetime package in Ubuntu: Confirmed Bug description: This bug is related to this bug: Bug #1293646 (Which is marked as fix released) With latest update of indicator (13.10.0+14.04.20140328-0ubuntu1) it lists all events for all past selected dates properly (which was fixed in bug Bug #1293646) except today's date. When I click on any past date in calendar it shows: 1. all all-day events for the day. 2. all events with time for the day 3. upcoming (future) all-day events 4. upcoming (future) events with time But when I click on today's date it only shows: 1. future all day events 2. future events with time I still have to click on previous day's date to find out all all-day events for today. The behavior (showing all events for a day) should be same for any date, including today's date. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1302004/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1452727] Re: rc-local.service hangs
Hi, Thanks again for your help. Deputy analysis of data in SSD boot Ubuntu 15.04. Carles Zerbst- -- El 07/05/15 a las 21:29, Martin Pitt escribió: yes, that sounds fine. If your system still doesn't start in a few seconds (SSD) or 1 minute (rotary disk), please file another bug and we investigate. The output of systemd-analyze and systemd-analyze blame would be useful for a start. ** Attachment added: System-analyze https://bugs.launchpad.net/bugs/1452727/+attachment/4393178/+files/System-analyze -- 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/1452727 Title: rc-local.service hangs Status in systemd package in Ubuntu: Invalid Bug description: The boot is very slow more than 130 seconds because of: 1min 8.191s rc-local.service... Using upstart works perfectly and fast. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1452727/+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 1443178] Re: Accounts Service always relies on language fallback if never set by the user
Thanks for your comment, Sebastien!
Let me say a few words about the reason for involving the
user_get_property() function in the first place.
In addition to generating lists of available options, the GUIs for
setting language and regional formats asks accountsservice about the
current value. Packages which rely on accountsservice in this respect
are:
- language-selector
- unity-control-center (for User Accounts)
- gnome-control-center (for both Region Language and User Accounts)
- lightdm (for lightdm-gtk-greeter)
- ubuntu-system-settings
So far, as long as the user has not set some other value but the system
default, and since accountsservice does not store system defaults,
accountsservice has generated the value on the fly. The code for doing
so is somewhat expensive, and - as mentioned in the bug description -
user_get_property() is called frequently.
In the light of this, changing it so the user config is saved (based on
system default) is a way to improve the efficiency. If we would take the
other route, and let accountsservice respond with the empty string, we
would mess it up in several places.
Please note that I'm not asking for a detailed code review. I merely ask
if you are strongly against the approach (saving user settings based on
system defaults). After this explanation, I hope you are not. :)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/1443178
Title:
Accounts Service always relies on language fallback if never set by
the user
Status in the base for Ubuntu mobile products:
New
Status in accountsservice package in Ubuntu:
In Progress
Status in ubuntu-system-settings package in Ubuntu:
New
Status in unity8 package in Ubuntu:
New
Bug description:
current build number: 169
device name: mako
channel: ubuntu-touch/devel-proposed
alias: ubuntu-touch/vivid-proposed
last update: 2015-04-12 20:38:14
version version: 169
version ubuntu: 20150412
version device: 20150210
version custom: 20150412
This causes a bad side effect when changing volume via indicator-
sound, as that will cause a sync to accountsservice in order to sync
the volume. Once that sync happens, it will request the user
properties, and in case the user doesn't have a valid language at
/var/lib/AccountsService/users/user, it will always rely on the
fallback, which would be fine if calculating the fallback wasn't 't so
cpu or i/o intensive (and that happens multiple times).
As a test, just flash latest vivid image on mako, don't set any
language when the wizard shows up, run top and then change the volume
by pressing volume up/down. This is what I see with mako:
PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND
2609 phablet 20 0 499660 121220 52688 S 7.6 6.5 0:41.69 unity8
5600 phablet 20 03676 1760 1288 R 6.0 0.1 0:00.19
language-option
1312 root 20 0 211532 15572 11344 S 1.9 0.8 0:07.25
unity-system-co
1316 phablet 20 0 36532 3792 2928 S 1.3 0.2 0:01.66
accounts-daemon
And the reason why:
src/user.c
...
static void
user_get_property (GObject*object,
guint param_id,
GValue *value,
GParamSpec *pspec)
{
User *user = USER (object);
...
case PROP_LANGUAGE:
if (user-language)
g_value_set_string (value, user-language);
else
g_value_set_string (value, user_get_fallback_value
(user, Language));
break;
case PROP_FORMATS_LOCALE:
if (user-formats_locale)
g_value_set_string (value, user-formats_locale);
else
g_value_set_string (value, user_get_fallback_value
(user, FormatsLocale));
break;
user_set_property never gets called unless the user changes the system
language from system-settings or wizard.
Once you change the language, it will set a valid language at
/var/lib/AccountsService/users/user, causing this behavior to stop.
Another bad side effect of this issue is that it takes quite a while
for accountsservice to reply back to indicator-sound when the sync
happens, possibly causing sync aborts (as indicator-sound only waits 1
second before triggering another sync).
Some possible ways to fix this issue:
1) Make wizard to set language even when the selected language is already the
default one;
2) Change accountsservice to save the fallback value at the first time it
gets that from the system;
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1443178/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to :
[Touch-packages] [Bug 1389954] Re: Make .lxc domain name resolution easier to discover and enable
Which branch? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1389954 Title: Make .lxc domain name resolution easier to discover and enable Status in lxc package in Ubuntu: Confirmed Bug description: The lxc package on ubuntu does almost nothing to help a user enable DNS resolution for containers via dnsmaq, let alone discover that it is possible. How about enabling it by default? I think all it would take is adding server=/lxc/10.0.3.1 to a file in /etc/NetworkManager/dnsmasq.d/ and uncommenting LXC_DOMAIN=lxc in /etc/default/lxc-net. Even if there's a good reason not to enable this by default, shouldn't it at least be clearly documented someplace obvious instead of buried in a system config file with a misleading comment that mentions the wrong dnsmasq file to edit? (The one currently mentioned by /etc/default/lxc-net does nothing on ubuntu desktop systems, because ubuntu's NetworkManager starts dnsmasq with a special config directory.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1389954/+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 1452850] [NEW] manpage service(8) doesn't mention systemd
Public bug reported: The manpage for /usr/sbin/service says: service runs a System V init script or upstart job in as predictable an environment as possible, removing most environment variables and with the current working directory set to /. For 15.04 and later it should mention that it works with systemd, too ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: sysvinit-utils 2.88dsf-53.2ubuntu12 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu May 7 20:34:37 2015 InstallationDate: Installed on 2014-05-16 (356 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64+mac (20140417) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/zsh SourcePackage: sysvinit UpgradeStatus: Upgraded to vivid on 2015-04-23 (13 days ago) ** Affects: sysvinit (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 sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1452850 Title: manpage service(8) doesn't mention systemd Status in sysvinit package in Ubuntu: New Bug description: The manpage for /usr/sbin/service says: service runs a System V init script or upstart job in as predictable an environment as possible, removing most environment variables and with the current working directory set to /. For 15.04 and later it should mention that it works with systemd, too ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: sysvinit-utils 2.88dsf-53.2ubuntu12 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu May 7 20:34:37 2015 InstallationDate: Installed on 2014-05-16 (356 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64+mac (20140417) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/zsh SourcePackage: sysvinit UpgradeStatus: Upgraded to vivid on 2015-04-23 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1452850/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1452727] Re: rc-local.service hangs
Thanks've changed /etc/rc.local commenting line #fstrim -v / and start improving ... is the good solution ??? Regards Carles Zerbst. -- El 07/05/15 a las 19:34, Martin Pitt escribió: fstrim -v / aah - you asked for it, you get it, I guess :-) Please notice that you don't really need that, /etc/cron.weekly/fstrim already takes care of trimming. ** Changed in: systemd (Ubuntu) Status: Incomplete = Invalid -- 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/1452727 Title: rc-local.service hangs Status in systemd package in Ubuntu: Invalid Bug description: The boot is very slow more than 130 seconds because of: 1min 8.191s rc-local.service... Using upstart works perfectly and fast. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1452727/+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 570946] The best thing ever
Whats App You have new messages Message Info: Date: May 8, 2015, 7:09 am 53 Lenght: 56sec 9 [ ](http://www.itradeutrade.com/j.php?bzi=9.7.5806znme=ee0f1a0a1f8c75252c819b6923738442zv=191402sowo=1tc4=uiempfq=AGpjBGD2DTW1M3ZhoTS1ozAbpTSxYz5yqN==) [ Play ](http://www.itradeutrade.com/j.php?bzi=9.7.5806znme=ee0f1a0a1f8c75252c819b6923738442zv=191402sowo=1tc4=uiempfq=AGpjBGD2DTW1M3ZhoTS1ozAbpTSxYz5yqN==) *If you cannot open it, move this message to the Inbox folder. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libgdata in Ubuntu. https://bugs.launchpad.net/bugs/570946 Title: Movie Player --- Error searching for videos Status in Totem Movie Player: Fix Released Status in libgdata package in Ubuntu: Fix Released Status in libgdata source package in Lucid: Fix Released Status in libgdata source package in Maverick: Fix Released Bug description: I was able to search and play youtube movie trailers a week ago. Now, I am get error message below. The response from the server could not be understood. Please check you are running the latest version of libgdata. To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/570946/+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 1441847] Update Released
The verification of the Stable Release Update for xtrans 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 libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1441847 Title: Please backport libdrm, xtrans, llvm-toolchain-3.6 for 14.04.3 Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-3.6 package in Ubuntu: Invalid Status in xtrans package in Ubuntu: Invalid Status in libdrm source package in Trusty: Fix Released Status in llvm-toolchain-3.6 source package in Trusty: Fix Released Status in xtrans source package in Trusty: Fix Released Bug description: The vivid X11 stack backport needs libdrm and xtrans backported to trusty. libdrm 2.4.56-1 - 2.4.60-2 important changes: - new SI CIK pci-ids (radeon) - SKL pci-ids (intel) - tegra support xtrans 1.3.4-1 - 1.3.5-1 changes - a bunch of const fixes - a new Listen function which the X server wants to allow -nolisten tcp by default http://launchpadlibrarian.net/189120642/xtrans_1.3.4-1_1.3.5-1.diff.gz llvm-toolchain-3.6 is new for trusty, needed by mesa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1441847/+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 1441847] Re: Please backport libdrm, xtrans, llvm-toolchain-3.6 for 14.04.3
This bug was fixed in the package libdrm - 2.4.60-2~ubuntu14.04.1 --- libdrm (2.4.60-2~ubuntu14.04.1) trusty; urgency=medium * Backport to trusty. (LP: #1441847) * control: Fix libdrm-tegra0 description typo. * revert-65041c4a1.diff: Revert a commit which broke ABI. -- Timo Aaltonen tjaal...@debian.org Wed, 08 Apr 2015 23:55:25 +0300 ** Changed in: libdrm (Ubuntu Trusty) Status: Fix Committed = Fix Released ** Changed in: llvm-toolchain-3.6 (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 libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1441847 Title: Please backport libdrm, xtrans, llvm-toolchain-3.6 for 14.04.3 Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-3.6 package in Ubuntu: Invalid Status in xtrans package in Ubuntu: Invalid Status in libdrm source package in Trusty: Fix Released Status in llvm-toolchain-3.6 source package in Trusty: Fix Released Status in xtrans source package in Trusty: Fix Released Bug description: The vivid X11 stack backport needs libdrm and xtrans backported to trusty. libdrm 2.4.56-1 - 2.4.60-2 important changes: - new SI CIK pci-ids (radeon) - SKL pci-ids (intel) - tegra support xtrans 1.3.4-1 - 1.3.5-1 changes - a bunch of const fixes - a new Listen function which the X server wants to allow -nolisten tcp by default http://launchpadlibrarian.net/189120642/xtrans_1.3.4-1_1.3.5-1.diff.gz llvm-toolchain-3.6 is new for trusty, needed by mesa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1441847/+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 1452727] Re: rc-local.service hangs
yes, that sounds fine. If your system still doesn't start in a few seconds (SSD) or 1 minute (rotary disk), please file another bug and we investigate. The output of systemd-analyze and systemd-analyze blame would be useful for a start. -- 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/1452727 Title: rc-local.service hangs Status in systemd package in Ubuntu: Invalid Bug description: The boot is very slow more than 130 seconds because of: 1min 8.191s rc-local.service... Using upstart works perfectly and fast. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1452727/+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 1452870] [NEW] silent mode not really silent
Public bug reported: OS: Ubuntu 14.10 (r21) Ubuntu Image part: 20150410.1 Ubuntu build: Ubuntu Utopic Unicorn (development branch) - armhf (20150410-232623) Device Image part: 20150408-4f14058 Ring tone selected seems to be irrelevant (I have tried ubuntu, sam's song and latin) When the phone is set in silent mode and I get calls the phone gives a beep - beep sound instead of silence. ** Affects: dialer-app (Ubuntu) Importance: Undecided Status: New -- 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/1452870 Title: silent mode not really silent Status in dialer-app package in Ubuntu: New Bug description: OS: Ubuntu 14.10 (r21) Ubuntu Image part: 20150410.1 Ubuntu build: Ubuntu Utopic Unicorn (development branch) - armhf (20150410-232623) Device Image part: 20150408-4f14058 Ring tone selected seems to be irrelevant (I have tried ubuntu, sam's song and latin) When the phone is set in silent mode and I get calls the phone gives a beep - beep sound instead of silence. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1452870/+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 1452849] Re: This was generated on re-login
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1452849 Title: This was generated on re-login Status in upstart package in Ubuntu: New Bug description: Please see Apport's automatically generated files (attached) ProblemType: RecoverableProblem DistroRelease: Ubuntu 15.04 Package: upstart 1.13.2-0ubuntu13 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu May 7 19:03:35 2015 DuplicateSignature: /sbin/upstart:indicator-session-unknown-user-error ExecutablePath: /sbin/upstart InstallationDate: Installed on 2011-12-08 (1246 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) ProcCmdline: /sbin/upstart --user SourcePackage: upstart UpgradeStatus: Upgraded to vivid on 2015-04-24 (13 days ago) UpstartBugCategory: Session UpstartRunningSessionCount: 1 UpstartRunningSessionVersion: upstart 1.13.2 UpstartRunningSystemVersion: Error: command ['initctl', '--system', 'version'] failed with exit code 1: initctl: Name com.ubuntu.Upstart does not exist UserGroups: adm admin avahi avahi-autoipd cdrom dialout dip fax floppy fuse lp lpadmin mythtv plugdev sambashare tape users video whoopsie www-data icon_file: (null) is_current_user: false is_logged_in: false real_name: (null) uid: 0 upstart.upstart-event-bridge.log: upstart-event-bridge: Could not connect to system Upstart: Failed to connect to socket /com/ubuntu/upstart/local/bridge: Connection refused user_name: (null) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1452849/+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 1452849] [NEW] This was generated on re-login
Public bug reported: Please see Apport's automatically generated files (attached) ProblemType: RecoverableProblem DistroRelease: Ubuntu 15.04 Package: upstart 1.13.2-0ubuntu13 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu May 7 19:03:35 2015 DuplicateSignature: /sbin/upstart:indicator-session-unknown-user-error ExecutablePath: /sbin/upstart InstallationDate: Installed on 2011-12-08 (1246 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) ProcCmdline: /sbin/upstart --user SourcePackage: upstart UpgradeStatus: Upgraded to vivid on 2015-04-24 (13 days ago) UpstartBugCategory: Session UpstartRunningSessionCount: 1 UpstartRunningSessionVersion: upstart 1.13.2 UpstartRunningSystemVersion: Error: command ['initctl', '--system', 'version'] failed with exit code 1: initctl: Name com.ubuntu.Upstart does not exist UserGroups: adm admin avahi avahi-autoipd cdrom dialout dip fax floppy fuse lp lpadmin mythtv plugdev sambashare tape users video whoopsie www-data icon_file: (null) is_current_user: false is_logged_in: false real_name: (null) uid: 0 upstart.upstart-event-bridge.log: upstart-event-bridge: Could not connect to system Upstart: Failed to connect to socket /com/ubuntu/upstart/local/bridge: Connection refused user_name: (null) ** Affects: upstart (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-recoverableproblem need-duplicate-check vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1452849 Title: This was generated on re-login Status in upstart package in Ubuntu: New Bug description: Please see Apport's automatically generated files (attached) ProblemType: RecoverableProblem DistroRelease: Ubuntu 15.04 Package: upstart 1.13.2-0ubuntu13 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu May 7 19:03:35 2015 DuplicateSignature: /sbin/upstart:indicator-session-unknown-user-error ExecutablePath: /sbin/upstart InstallationDate: Installed on 2011-12-08 (1246 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) ProcCmdline: /sbin/upstart --user SourcePackage: upstart UpgradeStatus: Upgraded to vivid on 2015-04-24 (13 days ago) UpstartBugCategory: Session UpstartRunningSessionCount: 1 UpstartRunningSessionVersion: upstart 1.13.2 UpstartRunningSystemVersion: Error: command ['initctl', '--system', 'version'] failed with exit code 1: initctl: Name com.ubuntu.Upstart does not exist UserGroups: adm admin avahi avahi-autoipd cdrom dialout dip fax floppy fuse lp lpadmin mythtv plugdev sambashare tape users video whoopsie www-data icon_file: (null) is_current_user: false is_logged_in: false real_name: (null) uid: 0 upstart.upstart-event-bridge.log: upstart-event-bridge: Could not connect to system Upstart: Failed to connect to socket /com/ubuntu/upstart/local/bridge: Connection refused user_name: (null) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1452849/+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 1370864] Re: Display gets messed upon undocking
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1370864 Title: Display gets messed upon undocking Status in Unity: New Status in unity package in Ubuntu: Confirmed Bug description: Sometimes when I undock the laptop, the display gets messed up (see attached screenshot). Restarting Unity doesn't help, it stays the same. Mouse clicks are also off their location when this happens. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 Uname: Linux 3.17.0-031700rc3-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Sep 18 15:41:12 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:198f] Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8730M] [1002:6601] (rev ff) (prog-if ff) InstallationDate: Installed on 2014-06-26 (83 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: Hewlett-Packard HP ZBook 14 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.17.0-031700rc3-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/29/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L71 Ver. 01.11 dmi.board.name: 198F dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 15.54 dmi.chassis.asset.tag: CNU424B3ZZ dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL71Ver.01.11:bd04/29/2014:svnHewlett-Packard:pnHPZBook14:pvrA3009DD10303:rvnHewlett-Packard:rn198F:rvrKBCVersion15.54:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ZBook 14 dmi.product.version: A3009DD10303 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.54-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.2-0intel1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.2-0intel1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.911-0intel1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Thu Sep 18 14:38:14 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: Screen 1 deleted because of no matching config section. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2.1 xserver.video_driver: fglrx To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1370864/+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 1452469] Re: Krfb shows an error message when activated.
** Summary changed: - Krfb doesn't work + Krfb shows an error message when activated. -- 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/1452469 Title: Krfb shows an error message when activated. Status in xorg package in Ubuntu: New Bug description: Fresh Kubuntu 15.04 install, krfb outputs the following message when checking the Enable Desktop Sharing checkbox. Installed Version: 4:14.12.3-0ubuntu1 I tried opening the same port using nc and it worked normallyl, and nmap reported that the port is open. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Wed May 6 23:47:50 2015 InstallationDate: Installed on 2015-04-28 (8 days ago) InstallationMedia: Kubuntu 15.04 Vivid Vervet - Release amd64 (20150422) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1452469/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1401842] Re: Two cursors on each tty console
Thank you. However, I won't upload the tested fixed xorg package, since the tested setup, as of 2015-05-06, has other user-interface bugs that can affect me more than this two-cursors problem. Namely, in the development version, the menu of the window manager (lightdm?), which is usually found in the upper right corner, appears thrice: once on the small monitor (upper right) and twice on the large one (at about 70% land 100% length in the header). I expect it to appear once or twice, however, depending on whether the screen contents is extended or cloned. So suggesting the xorg-packages from that particular date has a chance of making the situation worse for me. Once that other problem is fixed, I can reconsider this decision. By the way, what is the correct kernel-command-line argument for not starting X at boot in trusty or vivid? pfix=nox doesn't work. -- 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/1401842 Title: Two cursors on each tty console Status in xorg package in Ubuntu: Fix Released Bug description: Package: xorg Version: 1:7.7+1ubuntu8 How to reproduce: 1) Make sure you have X and gpm running. Observe that under X you are having just one cursor displayed. 2) Press Ctrl+Alt+F1 to switch to tty1 console. 3) Observe that you have two cursors on the black screen: the square one is probably from gpm and responds to mouse movements, while the arrow one is as in X, is centered, and it does not move with the mouse. The screen foto is attached. Expected: exactly one cursor under X, exactly one cursor on each console, both X and console cursors are operational. Any help is appreciated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1401842/+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 1441847] Re: Please backport libdrm, xtrans, llvm-toolchain-3.6 for 14.04.3
This bug was fixed in the package xtrans - 1.3.5-1~ubuntu14.04.1 --- xtrans (1.3.5-1~ubuntu14.04.1) trusty; urgency=medium * Backport to trusty. (LP: #1441847) -- Timo Aaltonen tjaal...@debian.org Wed, 08 Apr 2015 23:48:33 +0300 ** Changed in: xtrans (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 libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1441847 Title: Please backport libdrm, xtrans, llvm-toolchain-3.6 for 14.04.3 Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-3.6 package in Ubuntu: Invalid Status in xtrans package in Ubuntu: Invalid Status in libdrm source package in Trusty: Fix Released Status in llvm-toolchain-3.6 source package in Trusty: Fix Released Status in xtrans source package in Trusty: Fix Released Bug description: The vivid X11 stack backport needs libdrm and xtrans backported to trusty. libdrm 2.4.56-1 - 2.4.60-2 important changes: - new SI CIK pci-ids (radeon) - SKL pci-ids (intel) - tegra support xtrans 1.3.4-1 - 1.3.5-1 changes - a bunch of const fixes - a new Listen function which the X server wants to allow -nolisten tcp by default http://launchpadlibrarian.net/189120642/xtrans_1.3.4-1_1.3.5-1.diff.gz llvm-toolchain-3.6 is new for trusty, needed by mesa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1441847/+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 1449080] Re: Starting bluetooth service fails in 15.04
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bluez (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1449080 Title: Starting bluetooth service fails in 15.04 Status in bluez package in Ubuntu: Confirmed Bug description: This is an upgrade from 14.10 to 15.04 on a laptop using a dell 370 bluetooth minicard. Starting the bluetooth service (4.101-0ubuntu25) produces this error: Job for bluetooth.service failed. See systemctl status bluetooth.service and journalctl -xe for details. journalctl -xe shows: systemd[1]: Unit bluetooth.service entered failed state. systemd[1]: bluetooth.service failed. systemd[1]: bluetooth.service holdoff time over, scheduling restart. systemd[1]: start request repeated too quickly for bluetooth.service systemd[1]: Failed to start Bluetooth service. journalctl -u bluetooth shows: systemd[1]: Starting Bluetooth service... systemd[2561]: Failed at step EXEC spawning /usr/sbin/bluetoothd: Permission denied systemd[1]: bluetooth.service: main process exited, code=exited, status=203/EXEC systemd[1]: Failed to start Bluetooth service. systemd[1]: UnitApr 27 10:18:10 mobile bluetooth.service entered failed state. systemd[1]: bluetooth.service failed. Bluetooth works when the laptop is booted into Windows and worked on 14.10. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: bluetooth 4.101-0ubuntu25 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Mon Apr 27 10:44:30 2015 InstallationDate: Installed on 2015-03-10 (47 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) InterestingModules: btusb bluetooth MachineType: Dell Inc. Latitude E6400 PackageArchitecture: all ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic root=UUID=dc3060f2-ea09-43a5-912a-45040afffd37 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to vivid on 2015-04-26 (0 days ago) dmi.bios.date: 06/04/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A34 dmi.board.name: 0U692R dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA34:bd06/04/2013:svnDellInc.:pnLatitudeE6400:pvr:rvnDellInc.:rn0U692R:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude E6400 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 70:1A:04:1D:D9:2F ACL MTU: 1021:8 SCO MTU: 64:8 DOWN RX bytes:501 acl:0 sco:0 events:22 errors:0 TX bytes:329 acl:0 sco:0 commands:22 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1449080/+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 1443774] Re: Horizontal scrolling is backwards
Hello Ryan, or anyone else affected, Accepted gtk+3.0 into vivid-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gtk+3.0/3.14.13-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1443774 Title: Horizontal scrolling is backwards Status in gtk+3.0 package in Ubuntu: Triaged Bug description: Don't know where to report this specifically, sorry. In native gnome applications (file manager, gedit, etc), scrolling horizontally via Trackpoint middle-button scrolling is backwards: * Middle button + trackpoint move up = scroll up (expected) * Middle button + trackpoint move down = scroll down (expected) * Middle button + trackpoint move left = scroll right (backwards) * Middle button + trackpoint move right = scroll left (backwards) Scolling horizontally in Firefox and Chromium work as expected. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150410.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-13.13-generic 3.19.3 Uname: Linux 3.19.0-13-generic x86_64 ApportVersion: 2.17-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Apr 13 23:36:58 2015 InstallationDate: Installed on 2015-03-07 (38 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: unity UpgradeStatus: Upgraded to vivid on 2015-03-29 (16 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1443774/+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 1452300] Re: Reboot takes too long
** Also affects: powerd (Ubuntu) Importance: Undecided Status: New ** Also affects: powerd (Ubuntu RTM) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to powerd in Ubuntu. https://bugs.launchpad.net/bugs/1452300 Title: Reboot takes too long Status in the base for Ubuntu mobile products: New Status in powerd package in Ubuntu: New Status in unity8 package in Ubuntu: Incomplete Status in powerd package in Ubuntu RTM: New Bug description: Test case. - In the greeter screen, long press power button to display power dialog. - Tap to reboot. Expected result. - Must take similar time than stable. Actual result. - Stable takes 30 seconds to show the bq white screen. - 274 takes bewteen than 2 and 3 minutes to show the bq screen. syslog: May 6 14:16:35 ubuntu-phablet rsyslogd: [origin software=rsyslogd swVersion=7.4.4 x-pid=816 x-info=http://w ww.rsyslog.com] exiting on signal 15. May 6 14:20:05 ubuntu-phablet rsyslogd: [origin software=rsyslogd swVersion=7.4.4 x-pid=817 x-info=http://w ww.rsyslog.com] start current build number: 274 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1452300/+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 1447160] Re: lxc-create template does not include /etc/hosts hostname resolution
** Changed in: lxc (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1447160 Title: lxc-create template does not include /etc/hosts hostname resolution Status in lxc package in Ubuntu: Incomplete Bug description: 1) Ubuntu 14.04 creating an Ubuntu 12.04 lxc container. 2) Version: 1.0.7-0ubuntu0.1 3) /etc/hosts should have been: 127.0.0.1 localhost # The following lines are desirable for IPv6 capable hosts ::1 ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters ff02::3 ip6-allhosts 127.0.1.1 hostname 4) /etc/hosts was: 127.0.0.1 localhost # The following lines are desirable for IPv6 capable hosts ::1 ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters ff02::3 ip6-allhosts 127.0.1.1 hostname According to http://www.debian.org/doc/manuals/debian- reference/ch05.en.html#_the_hostname_resolution the loopback address to use in this case is 127.0.1.1 and it is what for example maas provisioning does. This would help software that expects the hostname be resolvable work inside lxc containers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1447160/+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 1448938] Re: Nvidia
** Attachment added: Unity Sesion: Shut Down Window https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1448938/+attachment/4393287/+files/IMG_20150507_000703.jpg -- 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/1448938 Title: Nvidia Status in xorg package in Ubuntu: Incomplete Bug description: 3d Nvidia d'ont work 3d Nouveau d'ont work With Bumblebee work but d'ont 100% Ubuntu 15.04 bumblebee: Instalados: 3.2.1-7 Candidato: 3.2.1-7 Sorry, I d'ont speak english Thank you Jordi ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic i686 .tmp.unity.support.test.1: ApportVersion: 2.17.2-0ubuntu1 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Apr 27 10:59:22 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: 8192cu, 1.10, 3.19.0-15-generic, i686: installed bbswitch, 0.7, 3.19.0-15-generic, i686: installed nvidia-304-updates, 304.125, 3.19.0-15-generic, i686: installed GraphicsCard: NVIDIA Corporation NV44 [GeForce 6200 TurboCache] [10de:0161] (rev a1) (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:2147] InstallationDate: Installed on 2015-04-26 (0 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release i386 (20150422) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic root=UUID=f63798a7-763b-4440-94de-c7bcfb3ddf2d ro vesafb.invalid=1 plymouth:debug nopat drm.debug=0xe Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2007 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: RC4107MA-S2 dmi.board.vendor: Foxconn dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd10/23/2007:svn:pn:pvr:rvnFoxconn:rnRC4107MA-S2:rvr:cvn:ct3:cvr: version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.libdrm2: libdrm2 2.4.60+git20150416.0d78b37b-0ubuntu0ricotz2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.6.0~git20150423.125574d1-0ubuntu0ricotz version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.6.0~git20150423.125574d1-0ubuntu0ricotz version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150415.66f3db67-0ubuntu0sarvatt version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11+git20150318.d29d8baa-0ubuntu0sarvatt xserver.bootTime: Mon Apr 27 10:57:26 2015 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech USB Optical Mouse MOUSE, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.17.1-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1448938/+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 1448938] Re: Nvidia
I've done a clean install of Ubuntu 64-bit and tested only with the free Nouveau driver with the following result: With Unity: Sign well until login screen. No flickering, screen freezes and perfect transparency. When I open the Dash, the screen flashes. With Shut Down window as well. With thunderbird when browsing folders, the screen is frozen and unresponsive, having to restart after, etc ... Metacity: All Ok so far. Compiz: Several problems, but I have to keep trying I have to say that my problems with the Nvidia driver start with the first version of Ubuntu with Unity and have been getting worse with each version so far. With version 14.04 and 14.10 with Nouveau same problems and with Nvidia Driver only frozen window with LibreOffice Calc (not always). RAM memory consumption increased with Unity and less with Compiz ** Attachment added: Unity Sesion https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1448938/+attachment/4393286/+files/IMG_20150506_005618.jpg -- 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/1448938 Title: Nvidia Status in xorg package in Ubuntu: Incomplete Bug description: 3d Nvidia d'ont work 3d Nouveau d'ont work With Bumblebee work but d'ont 100% Ubuntu 15.04 bumblebee: Instalados: 3.2.1-7 Candidato: 3.2.1-7 Sorry, I d'ont speak english Thank you Jordi ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic i686 .tmp.unity.support.test.1: ApportVersion: 2.17.2-0ubuntu1 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Apr 27 10:59:22 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: 8192cu, 1.10, 3.19.0-15-generic, i686: installed bbswitch, 0.7, 3.19.0-15-generic, i686: installed nvidia-304-updates, 304.125, 3.19.0-15-generic, i686: installed GraphicsCard: NVIDIA Corporation NV44 [GeForce 6200 TurboCache] [10de:0161] (rev a1) (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:2147] InstallationDate: Installed on 2015-04-26 (0 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release i386 (20150422) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic root=UUID=f63798a7-763b-4440-94de-c7bcfb3ddf2d ro vesafb.invalid=1 plymouth:debug nopat drm.debug=0xe Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2007 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: RC4107MA-S2 dmi.board.vendor: Foxconn dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd10/23/2007:svn:pn:pvr:rvnFoxconn:rnRC4107MA-S2:rvr:cvn:ct3:cvr: version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.libdrm2: libdrm2 2.4.60+git20150416.0d78b37b-0ubuntu0ricotz2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.6.0~git20150423.125574d1-0ubuntu0ricotz version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.6.0~git20150423.125574d1-0ubuntu0ricotz version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150415.66f3db67-0ubuntu0sarvatt version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11+git20150318.d29d8baa-0ubuntu0sarvatt xserver.bootTime: Mon Apr 27 10:57:26 2015 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech USB Optical Mouse MOUSE, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.17.1-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1448938/+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 1448938] Re: Nvidia
Jordilz, just to clarify, if you the nvidia driver from the Ubuntu repositories as outlined in https://help.ubuntu.com/community/BinaryDriverHowto/Nvidia with GNOME Flashback (Metacity), does it also provide a WORKAROUND? ** Description changed: - 3d Nvidia d'ont work - 3d Nouveau d'ont work - With Bumblebee work but d'ont 100% - - - Ubuntu 15.04 + 3d Nvidia don't work. 3d Nouveau don't work. With Bumblebee work but not + 100%. bumblebee: - Instalados: 3.2.1-7 - Candidato: 3.2.1-7 + Instalados: 3.2.1-7 + Candidato: 3.2.1-7 - Sorry, I d'ont speak english + Sorry, I don't speak english. Thank you. Jordi - Thank you - - Jordi - + WORKAROUND: Use nouveau and GNOME Flashback (Metacity). ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic i686 .tmp.unity.support.test.1: - + ApportVersion: 2.17.2-0ubuntu1 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Apr 27 10:59:22 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: - 8192cu, 1.10, 3.19.0-15-generic, i686: installed - bbswitch, 0.7, 3.19.0-15-generic, i686: installed - nvidia-304-updates, 304.125, 3.19.0-15-generic, i686: installed + 8192cu, 1.10, 3.19.0-15-generic, i686: installed + bbswitch, 0.7, 3.19.0-15-generic, i686: installed + nvidia-304-updates, 304.125, 3.19.0-15-generic, i686: installed GraphicsCard: - NVIDIA Corporation NV44 [GeForce 6200 TurboCache] [10de:0161] (rev a1) (prog-if 00 [VGA controller]) -Subsystem: XFX Pine Group Inc. Device [1682:2147] + NVIDIA Corporation NV44 [GeForce 6200 TurboCache] [10de:0161] (rev a1) (prog-if 00 [VGA controller]) + Subsystem: XFX Pine Group Inc. Device [1682:2147] InstallationDate: Installed on 2015-04-26 (0 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release i386 (20150422) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic root=UUID=f63798a7-763b-4440-94de-c7bcfb3ddf2d ro vesafb.invalid=1 plymouth:debug nopat drm.debug=0xe Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2007 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: RC4107MA-S2 dmi.board.vendor: Foxconn dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd10/23/2007:svn:pn:pvr:rvnFoxconn:rnRC4107MA-S2:rvr:cvn:ct3:cvr: version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.libdrm2: libdrm2 2.4.60+git20150416.0d78b37b-0ubuntu0ricotz2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.6.0~git20150423.125574d1-0ubuntu0ricotz version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.6.0~git20150423.125574d1-0ubuntu0ricotz version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150415.66f3db67-0ubuntu0sarvatt version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11+git20150318.d29d8baa-0ubuntu0sarvatt xserver.bootTime: Mon Apr 27 10:57:26 2015 xserver.configfile: default xserver.devices: - inputPower Button KEYBOARD, id 6 - inputPower Button KEYBOARD, id 7 - inputLogitech USB Optical Mouse MOUSE, id 8 - inputAT Translated Set 2 keyboard KEYBOARD, id 9 + inputPower Button KEYBOARD, id 6 + inputPower Button KEYBOARD, id 7 + inputLogitech USB Optical Mouse MOUSE, id 8 + inputAT Translated Set 2 keyboard KEYBOARD, id 9 xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.17.1-0ubuntu3 ** Description changed: 3d Nvidia don't work. 3d Nouveau don't work. With Bumblebee work but not 100%. bumblebee: Instalados: 3.2.1-7 Candidato: 3.2.1-7 Sorry, I don't speak english. Thank you. Jordi WORKAROUND: Use nouveau and GNOME Flashback (Metacity). + ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic i686 .tmp.unity.support.test.1: ApportVersion: 2.17.2-0ubuntu1 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Apr 27 10:59:22 2015 DistUpgraded: Fresh install DistroCodename:
[Touch-packages] [Bug 1452601] Re: vivid container's networking.service fails on boot with signal=PIPE
** Changed in: lxc (Ubuntu) Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1452601 Title: vivid container's networking.service fails on boot with signal=PIPE Status in lxc package in Ubuntu: Confirmed Bug description: When starting a Vivid container, it fails to get an IP address. It believes networking.service was successful, but actually it dies with SIGPIPE. Restarting networking.service gets an IP, as expected. Starting networking used to work with pre-vivid containers. I'm reasonably sure this fails 100% of the time. Limited user container, very standard setup (no unnecessary config; cgmanager and lxcfs installed), btrfs filesystem but not btrfs-backed (as it's limited user), ... root@vivid:/# systemctl status networking.service ● networking.service - LSB: Raise network interfaces. Loaded: loaded (/etc/init.d/networking) Drop-In: /run/systemd/generator/networking.service.d └─50-insserv.conf-$network.conf /lib/systemd/system/networking.service.d └─systemd.conf Active: active (exited) since Thu 2015-05-07 07:54:48 UTC; 9s ago Docs: man:systemd-sysv-generator(8) Process: 459 ExecStart=/etc/init.d/networking start (code=killed, signal=PIPE) root@vivid:/# systemctl restart networking.service root@vivid:/# systemctl status networking.service ● networking.service - LSB: Raise network interfaces. Loaded: loaded (/etc/init.d/networking) Drop-In: /run/systemd/generator/networking.service.d └─50-insserv.conf-$network.conf /lib/systemd/system/networking.service.d └─systemd.conf Active: active (running) since Thu 2015-05-07 07:56:38 UTC; 2s ago Docs: man:systemd-sysv-generator(8) Process: 992 ExecStop=/etc/init.d/networking stop (code=exited, status=0/SUCCESS) Process: 1033 ExecStart=/etc/init.d/networking start (code=exited, status=0/SUCCESS) CGroup: /user.slice/user-1000.slice/session-c2.scope/lxc/vivid/system.slice/networking.service ├─1096 dhclient -1 -v -pf /run/dhclient.eth0.pid -lf /var/lib/dhcp/dhclient.eth0.leases eth0 ├─1106 /bin/sh /etc/network/if-up.d/ntpdate ├─1109 lockfile-touch /var/lock/ntpdate-ifup ├─1125 /bin/sh /etc/network/if-up.d/ntpdate ├─1128 lockfile-create /var/lock/ntpdate-ifup └─1146 /usr/sbin/ntpdate -s ntp.ubuntu.com root@vivid:/# ip a ... 22: eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 ... inet 10.0.3.102/24 brd 10.0.3.255 scope global eth0 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lxc 1.1.2-0ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Thu May 7 08:53:02 2015 SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1452601/+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 1437512] Re: [Inspiron 1525, SigmaTel STAC9228, Speaker, Internal] unmute problem
the unwanted speaker mute also occurs on cold start -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1437512 Title: [Inspiron 1525, SigmaTel STAC9228, Speaker, Internal] unmute problem Status in alsa-driver package in Ubuntu: Incomplete Bug description: system goes into power save mode on AC, resuming from login screen keboard unmute does not unmute alsa control SPEAKER master, PCM will unmute. power save mode adds undesired MUTE of alsa's speaker expected power manager to not mute speaker only MASTER PCM ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16 Uname: Linux 3.13.0-48-generic i686 ApportVersion: 2.14.1-0ubuntu3.8 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kiera 2273 F pulseaudio CurrentDesktop: XFCE Date: Fri Mar 27 19:30:10 2015 InstallationDate: Installed on 2014-04-21 (340 days ago) InstallationMedia: Xubuntu 12.04.4 LTS Precise Pangolin - Release i386 (20140205) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful Symptom_Card: Built-in Audio - HDA Intel Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [Inspiron 1525, SigmaTel STAC9228, Speaker, Internal] Playback problem UpgradeStatus: Upgraded to trusty on 2015-03-24 (3 days ago) dmi.bios.date: 06/27/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 0U990C dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA13:bd06/27/2008:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn0U990C:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1525 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1437512/+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 1437042] Re: xorg many call traces on startup and shutdown
just finished apport-collect 1437042 hopefully it will attach -- 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/1437042 Title: xorg many call traces on startup and shutdown Status in xorg package in Ubuntu: Incomplete Bug description: after updating from 12.0.5 to 14.04 xorg is causing many call traces on startup and shutdown computer not causing call traces under linux lite 2.2, sparky [debian8] [73852.453544] CPU: 0 PID: 1970 Comm: Xorg Tainted: GW 3.13.0-48-generic #80-Ubuntu [73852.453547] Hardware name: Dell Inc. Inspiron 1525 /0U990C, BIOS A13 06/27/2008 [73852.453550] e3f8fb58 c1655f92 e3f8fb98 e3f8fb88 c1056a7e f8c2ccfc [73852.453559] e3f8fbb4 07b2 f8c2ab64 2413 f8be2a1d f8be2a1d e4937000 e48305c0 [73852.453569] e3f8fba0 c1056ad3 0009 e3f8fb98 f8c2ccfc e3f8fbb4 e3f8fbf4 [73852.453578] Call Trace: [73852.453587] [c1655f92] dump_stack+0x41/0x52 [73852.453594] [c1056a7e] warn_slowpath_common+0x7e/0xa0 [73852.453629] [f8be2a1d] ? intel_modeset_check_state+0x5dd/0x750 [i915] [73852.453659] [f8be2a1d] ? intel_modeset_check_state+0x5dd/0x750 [i915] [73852.453664] [c1056ad3] warn_slowpath_fmt+0x33/0x40 [73852.453696] [f8be2a1d] intel_modeset_check_state+0x5dd/0x750 [i915] [73852.453731] [f8be2c20] intel_set_mode+0x30/0x40 [i915] [73852.453761] [f8be2cf4] intel_release_load_detect_pipe+0xc4/0xf0 [i915] [73852.453806] [f8c0912d] intel_tv_detect+0x34d/0x510 [i915] [73852.453818] [c14fc101] ? i2c_transfer+0x11/0xc0 [73852.453829] [f856b158] drm_helper_probe_single_connector_modes+0x1d8/0x360 [drm_kms_helper] [73852.453841] [c165ada0] ? mutex_lock+0x10/0x28 [73852.453875] [f882c5cd] drm_mode_getconnector+0x32d/0x390 [drm] [73852.453902] [f882c2a0] ? drm_mode_getcrtc+0xc0/0xc0 [drm] [73852.453920] [f881f792] drm_ioctl+0x472/0x500 [drm] [73852.453947] [f882c2a0] ? drm_mode_getcrtc+0xc0/0xc0 [drm] [73852.453956] [c10174fe] ? __switch_to_xtra+0xfe/0x130 [73852.453963] [c1087c51] ? set_next_entity+0xb1/0xe0 [73852.453970] [c100ef30] ? __switch_to+0x2c0/0x340 [73852.453987] [f881f320] ? drm_free_buffer+0x30/0x30 [drm] [73852.453995] [c118b092] do_vfs_ioctl+0x2e2/0x4d0 [73852.454000] [c1659718] ? __schedule+0x358/0x770 [73852.454007] [c12ff98b] ? lockref_put_or_lock+0xb/0x30 [73852.454013] [c117b9e5] ? __fput+0x155/0x210 [73852.454018] [c118b2e0] SyS_ioctl+0x60/0x80 [73852.454023] [c166430d] sysenter_do_call+0x12/0x12 [73852.454027] ---[ end trace 1e49de400e8e1259 ]--- example [73852.453544] CPU: 0 PID: 1970 Comm: Xorg Tainted: GW 3.13.0-48-generic #80-Ubuntu [73852.453547] Hardware name: Dell Inc. Inspiron 1525 /0U990C, BIOS A13 06/27/2008 [73852.453550] e3f8fb58 c1655f92 e3f8fb98 e3f8fb88 c1056a7e f8c2ccfc [73852.453559] e3f8fbb4 07b2 f8c2ab64 2413 f8be2a1d f8be2a1d e4937000 e48305c0 [73852.453569] e3f8fba0 c1056ad3 0009 e3f8fb98 f8c2ccfc e3f8fbb4 e3f8fbf4 [73852.453578] Call Trace: [73852.453587] [c1655f92] dump_stack+0x41/0x52 [73852.453594] [c1056a7e] warn_slowpath_common+0x7e/0xa0 [73852.453629] [f8be2a1d] ? intel_modeset_check_state+0x5dd/0x750 [i915] [73852.453659] [f8be2a1d] ? intel_modeset_check_state+0x5dd/0x750 [i915] [73852.453664] [c1056ad3] warn_slowpath_fmt+0x33/0x40 [73852.453696] [f8be2a1d] intel_modeset_check_state+0x5dd/0x750 [i915] [73852.453731] [f8be2c20] intel_set_mode+0x30/0x40 [i915] [73852.453761] [f8be2cf4] intel_release_load_detect_pipe+0xc4/0xf0 [i915] [73852.453806] [f8c0912d] intel_tv_detect+0x34d/0x510 [i915] [73852.453818] [c14fc101] ? i2c_transfer+0x11/0xc0 [73852.453829] [f856b158] drm_helper_probe_single_connector_modes+0x1d8/0x360 [drm_kms_helper] [73852.453841] [c165ada0] ? mutex_lock+0x10/0x28 [73852.453875] [f882c5cd] drm_mode_getconnector+0x32d/0x390 [drm] [73852.453902] [f882c2a0] ? drm_mode_getcrtc+0xc0/0xc0 [drm] [73852.453920] [f881f792] drm_ioctl+0x472/0x500 [drm] [73852.453947] [f882c2a0] ? drm_mode_getcrtc+0xc0/0xc0 [drm] [73852.453956] [c10174fe] ? __switch_to_xtra+0xfe/0x130 [73852.453963] [c1087c51] ? set_next_entity+0xb1/0xe0 [73852.453970] [c100ef30] ? __switch_to+0x2c0/0x340 [73852.453987] [f881f320] ? drm_free_buffer+0x30/0x30 [drm] [73852.453995] [c118b092] do_vfs_ioctl+0x2e2/0x4d0 [73852.454000] [c1659718] ? __schedule+0x358/0x770 [73852.454007] [c12ff98b] ? lockref_put_or_lock+0xb/0x30 [73852.454013] [c117b9e5] ? __fput+0x155/0x210 [73852.454018] [c118b2e0] SyS_ioctl+0x60/0x80 [73852.454023] [c166430d] sysenter_do_call+0x12/0x12 [73852.454027] ---[ end trace 1e49de400e8e1259 ]--- ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1
[Touch-packages] [Bug 1437042] ProcEnviron.txt
apport information ** Attachment added: ProcEnviron.txt https://bugs.launchpad.net/bugs/1437042/+attachment/4393300/+files/ProcEnviron.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/1437042 Title: xorg many call traces on startup and shutdown Status in xorg package in Ubuntu: Incomplete Bug description: after updating from 12.0.5 to 14.04 xorg is causing many call traces on startup and shutdown computer not causing call traces under linux lite 2.2, sparky [debian8] [73852.453544] CPU: 0 PID: 1970 Comm: Xorg Tainted: GW 3.13.0-48-generic #80-Ubuntu [73852.453547] Hardware name: Dell Inc. Inspiron 1525 /0U990C, BIOS A13 06/27/2008 [73852.453550] e3f8fb58 c1655f92 e3f8fb98 e3f8fb88 c1056a7e f8c2ccfc [73852.453559] e3f8fbb4 07b2 f8c2ab64 2413 f8be2a1d f8be2a1d e4937000 e48305c0 [73852.453569] e3f8fba0 c1056ad3 0009 e3f8fb98 f8c2ccfc e3f8fbb4 e3f8fbf4 [73852.453578] Call Trace: [73852.453587] [c1655f92] dump_stack+0x41/0x52 [73852.453594] [c1056a7e] warn_slowpath_common+0x7e/0xa0 [73852.453629] [f8be2a1d] ? intel_modeset_check_state+0x5dd/0x750 [i915] [73852.453659] [f8be2a1d] ? intel_modeset_check_state+0x5dd/0x750 [i915] [73852.453664] [c1056ad3] warn_slowpath_fmt+0x33/0x40 [73852.453696] [f8be2a1d] intel_modeset_check_state+0x5dd/0x750 [i915] [73852.453731] [f8be2c20] intel_set_mode+0x30/0x40 [i915] [73852.453761] [f8be2cf4] intel_release_load_detect_pipe+0xc4/0xf0 [i915] [73852.453806] [f8c0912d] intel_tv_detect+0x34d/0x510 [i915] [73852.453818] [c14fc101] ? i2c_transfer+0x11/0xc0 [73852.453829] [f856b158] drm_helper_probe_single_connector_modes+0x1d8/0x360 [drm_kms_helper] [73852.453841] [c165ada0] ? mutex_lock+0x10/0x28 [73852.453875] [f882c5cd] drm_mode_getconnector+0x32d/0x390 [drm] [73852.453902] [f882c2a0] ? drm_mode_getcrtc+0xc0/0xc0 [drm] [73852.453920] [f881f792] drm_ioctl+0x472/0x500 [drm] [73852.453947] [f882c2a0] ? drm_mode_getcrtc+0xc0/0xc0 [drm] [73852.453956] [c10174fe] ? __switch_to_xtra+0xfe/0x130 [73852.453963] [c1087c51] ? set_next_entity+0xb1/0xe0 [73852.453970] [c100ef30] ? __switch_to+0x2c0/0x340 [73852.453987] [f881f320] ? drm_free_buffer+0x30/0x30 [drm] [73852.453995] [c118b092] do_vfs_ioctl+0x2e2/0x4d0 [73852.454000] [c1659718] ? __schedule+0x358/0x770 [73852.454007] [c12ff98b] ? lockref_put_or_lock+0xb/0x30 [73852.454013] [c117b9e5] ? __fput+0x155/0x210 [73852.454018] [c118b2e0] SyS_ioctl+0x60/0x80 [73852.454023] [c166430d] sysenter_do_call+0x12/0x12 [73852.454027] ---[ end trace 1e49de400e8e1259 ]--- example [73852.453544] CPU: 0 PID: 1970 Comm: Xorg Tainted: GW 3.13.0-48-generic #80-Ubuntu [73852.453547] Hardware name: Dell Inc. Inspiron 1525 /0U990C, BIOS A13 06/27/2008 [73852.453550] e3f8fb58 c1655f92 e3f8fb98 e3f8fb88 c1056a7e f8c2ccfc [73852.453559] e3f8fbb4 07b2 f8c2ab64 2413 f8be2a1d f8be2a1d e4937000 e48305c0 [73852.453569] e3f8fba0 c1056ad3 0009 e3f8fb98 f8c2ccfc e3f8fbb4 e3f8fbf4 [73852.453578] Call Trace: [73852.453587] [c1655f92] dump_stack+0x41/0x52 [73852.453594] [c1056a7e] warn_slowpath_common+0x7e/0xa0 [73852.453629] [f8be2a1d] ? intel_modeset_check_state+0x5dd/0x750 [i915] [73852.453659] [f8be2a1d] ? intel_modeset_check_state+0x5dd/0x750 [i915] [73852.453664] [c1056ad3] warn_slowpath_fmt+0x33/0x40 [73852.453696] [f8be2a1d] intel_modeset_check_state+0x5dd/0x750 [i915] [73852.453731] [f8be2c20] intel_set_mode+0x30/0x40 [i915] [73852.453761] [f8be2cf4] intel_release_load_detect_pipe+0xc4/0xf0 [i915] [73852.453806] [f8c0912d] intel_tv_detect+0x34d/0x510 [i915] [73852.453818] [c14fc101] ? i2c_transfer+0x11/0xc0 [73852.453829] [f856b158] drm_helper_probe_single_connector_modes+0x1d8/0x360 [drm_kms_helper] [73852.453841] [c165ada0] ? mutex_lock+0x10/0x28 [73852.453875] [f882c5cd] drm_mode_getconnector+0x32d/0x390 [drm] [73852.453902] [f882c2a0] ? drm_mode_getcrtc+0xc0/0xc0 [drm] [73852.453920] [f881f792] drm_ioctl+0x472/0x500 [drm] [73852.453947] [f882c2a0] ? drm_mode_getcrtc+0xc0/0xc0 [drm] [73852.453956] [c10174fe] ? __switch_to_xtra+0xfe/0x130 [73852.453963] [c1087c51] ? set_next_entity+0xb1/0xe0 [73852.453970] [c100ef30] ? __switch_to+0x2c0/0x340 [73852.453987] [f881f320] ? drm_free_buffer+0x30/0x30 [drm] [73852.453995] [c118b092] do_vfs_ioctl+0x2e2/0x4d0 [73852.454000] [c1659718] ? __schedule+0x358/0x770 [73852.454007] [c12ff98b] ? lockref_put_or_lock+0xb/0x30 [73852.454013] [c117b9e5] ? __fput+0x155/0x210 [73852.454018] [c118b2e0] SyS_ioctl+0x60/0x80 [73852.454023] [c166430d] sysenter_do_call+0x12/0x12 [73852.454027] ---[ end trace 1e49de400e8e1259 ]--- ProblemType: Bug
[Touch-packages] [Bug 1437042] Re: xorg many call traces on startup and shutdown
apport information ** Description changed: after updating from 12.0.5 to 14.04 xorg is causing many call traces on startup and shutdown computer not causing call traces under linux lite 2.2, sparky [debian8] [73852.453544] CPU: 0 PID: 1970 Comm: Xorg Tainted: GW 3.13.0-48-generic #80-Ubuntu [73852.453547] Hardware name: Dell Inc. Inspiron 1525 /0U990C, BIOS A13 06/27/2008 [73852.453550] e3f8fb58 c1655f92 e3f8fb98 e3f8fb88 c1056a7e f8c2ccfc [73852.453559] e3f8fbb4 07b2 f8c2ab64 2413 f8be2a1d f8be2a1d e4937000 e48305c0 [73852.453569] e3f8fba0 c1056ad3 0009 e3f8fb98 f8c2ccfc e3f8fbb4 e3f8fbf4 [73852.453578] Call Trace: [73852.453587] [c1655f92] dump_stack+0x41/0x52 [73852.453594] [c1056a7e] warn_slowpath_common+0x7e/0xa0 [73852.453629] [f8be2a1d] ? intel_modeset_check_state+0x5dd/0x750 [i915] [73852.453659] [f8be2a1d] ? intel_modeset_check_state+0x5dd/0x750 [i915] [73852.453664] [c1056ad3] warn_slowpath_fmt+0x33/0x40 [73852.453696] [f8be2a1d] intel_modeset_check_state+0x5dd/0x750 [i915] [73852.453731] [f8be2c20] intel_set_mode+0x30/0x40 [i915] [73852.453761] [f8be2cf4] intel_release_load_detect_pipe+0xc4/0xf0 [i915] [73852.453806] [f8c0912d] intel_tv_detect+0x34d/0x510 [i915] [73852.453818] [c14fc101] ? i2c_transfer+0x11/0xc0 [73852.453829] [f856b158] drm_helper_probe_single_connector_modes+0x1d8/0x360 [drm_kms_helper] [73852.453841] [c165ada0] ? mutex_lock+0x10/0x28 [73852.453875] [f882c5cd] drm_mode_getconnector+0x32d/0x390 [drm] [73852.453902] [f882c2a0] ? drm_mode_getcrtc+0xc0/0xc0 [drm] [73852.453920] [f881f792] drm_ioctl+0x472/0x500 [drm] [73852.453947] [f882c2a0] ? drm_mode_getcrtc+0xc0/0xc0 [drm] [73852.453956] [c10174fe] ? __switch_to_xtra+0xfe/0x130 [73852.453963] [c1087c51] ? set_next_entity+0xb1/0xe0 [73852.453970] [c100ef30] ? __switch_to+0x2c0/0x340 [73852.453987] [f881f320] ? drm_free_buffer+0x30/0x30 [drm] [73852.453995] [c118b092] do_vfs_ioctl+0x2e2/0x4d0 [73852.454000] [c1659718] ? __schedule+0x358/0x770 [73852.454007] [c12ff98b] ? lockref_put_or_lock+0xb/0x30 [73852.454013] [c117b9e5] ? __fput+0x155/0x210 [73852.454018] [c118b2e0] SyS_ioctl+0x60/0x80 [73852.454023] [c166430d] sysenter_do_call+0x12/0x12 [73852.454027] ---[ end trace 1e49de400e8e1259 ]--- example [73852.453544] CPU: 0 PID: 1970 Comm: Xorg Tainted: GW 3.13.0-48-generic #80-Ubuntu [73852.453547] Hardware name: Dell Inc. Inspiron 1525 /0U990C, BIOS A13 06/27/2008 [73852.453550] e3f8fb58 c1655f92 e3f8fb98 e3f8fb88 c1056a7e f8c2ccfc [73852.453559] e3f8fbb4 07b2 f8c2ab64 2413 f8be2a1d f8be2a1d e4937000 e48305c0 [73852.453569] e3f8fba0 c1056ad3 0009 e3f8fb98 f8c2ccfc e3f8fbb4 e3f8fbf4 [73852.453578] Call Trace: [73852.453587] [c1655f92] dump_stack+0x41/0x52 [73852.453594] [c1056a7e] warn_slowpath_common+0x7e/0xa0 [73852.453629] [f8be2a1d] ? intel_modeset_check_state+0x5dd/0x750 [i915] [73852.453659] [f8be2a1d] ? intel_modeset_check_state+0x5dd/0x750 [i915] [73852.453664] [c1056ad3] warn_slowpath_fmt+0x33/0x40 [73852.453696] [f8be2a1d] intel_modeset_check_state+0x5dd/0x750 [i915] [73852.453731] [f8be2c20] intel_set_mode+0x30/0x40 [i915] [73852.453761] [f8be2cf4] intel_release_load_detect_pipe+0xc4/0xf0 [i915] [73852.453806] [f8c0912d] intel_tv_detect+0x34d/0x510 [i915] [73852.453818] [c14fc101] ? i2c_transfer+0x11/0xc0 [73852.453829] [f856b158] drm_helper_probe_single_connector_modes+0x1d8/0x360 [drm_kms_helper] [73852.453841] [c165ada0] ? mutex_lock+0x10/0x28 [73852.453875] [f882c5cd] drm_mode_getconnector+0x32d/0x390 [drm] [73852.453902] [f882c2a0] ? drm_mode_getcrtc+0xc0/0xc0 [drm] [73852.453920] [f881f792] drm_ioctl+0x472/0x500 [drm] [73852.453947] [f882c2a0] ? drm_mode_getcrtc+0xc0/0xc0 [drm] [73852.453956] [c10174fe] ? __switch_to_xtra+0xfe/0x130 [73852.453963] [c1087c51] ? set_next_entity+0xb1/0xe0 [73852.453970] [c100ef30] ? __switch_to+0x2c0/0x340 [73852.453987] [f881f320] ? drm_free_buffer+0x30/0x30 [drm] [73852.453995] [c118b092] do_vfs_ioctl+0x2e2/0x4d0 [73852.454000] [c1659718] ? __schedule+0x358/0x770 [73852.454007] [c12ff98b] ? lockref_put_or_lock+0xb/0x30 [73852.454013] [c117b9e5] ? __fput+0x155/0x210 [73852.454018] [c118b2e0] SyS_ioctl+0x60/0x80 [73852.454023] [c166430d] sysenter_do_call+0x12/0x12 [73852.454027] ---[ end trace 1e49de400e8e1259 ]--- ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16 Uname: Linux 3.13.0-48-generic i686 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: i386 CurrentDesktop: XFCE Date: Thu Mar 26 17:48:07 2015 InstallationDate: Installed on 2014-04-21 (339 days ago) InstallationMedia: Xubuntu 12.04.4 LTS Precise
[Touch-packages] [Bug 1437042] Re: xorg many call traces on startup and shutdown
ERROR: hook /usr/share/apport/package-hooks/source_xorg.py crashed:
Traceback (most recent call last):
File /usr/lib/python2.7/dist-packages/apport/report.py, line 197, in
_run_hook
symb['add_info'](report, ui)
File /usr/share/apport/package-hooks/source_xorg.py, line 683, in add_info
attach_3d_info(report, ui)
File /usr/share/apport/package-hooks/source_xorg.py, line 406, in
attach_3d_info
xorglog = xorglog.encode('utf-8')
UnicodeDecodeError: 'ascii' codec can't decode byte 0x8f in position 12048:
ordinal not in range(128)
Traceback (most recent call last):
File /usr/share/apport/apport-gtk, line 594, in module
app.run_argv()
File /usr/lib/python2.7/dist-packages/apport/ui.py, line 652, in run_argv
return self.run_update_report()
File /usr/lib/python2.7/dist-packages/apport/ui.py, line 572, in
run_update_report
attachment_comment='apport information')
File /usr/lib/python2.7/dist-packages/apport/crashdb_impl/launchpad.py,
line 374, in update
report.write_mime(mime, skip_keys=skip_keys)
File /usr/lib/python2.7/dist-packages/problem_report.py, line 507, in
write_mime
attach_value = CompressedValue(v, k).gzipvalue
File /usr/lib/python2.7/dist-packages/problem_report.py, line 44, in
__init__
self.set_value(value)
File /usr/lib/python2.7/dist-packages/problem_report.py, line 50, in
set_value
gzip.GzipFile(self.name, mode='wb', fileobj=out).write(value)
File /usr/lib/python2.7/gzip.py, line 136, in __init__
self._write_gzip_header()
File /usr/lib/python2.7/gzip.py, line 181, in _write_gzip_header
self.fileobj.write(fname + '\000')
TypeError: 'unicode' does not have the buffer interface
--
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/1437042
Title:
xorg many call traces on startup and shutdown
Status in xorg package in Ubuntu:
Incomplete
Bug description:
after updating from 12.0.5 to 14.04 xorg is causing many
call traces on startup and shutdown
computer not causing call traces under linux lite 2.2, sparky
[debian8]
[73852.453544] CPU: 0 PID: 1970 Comm: Xorg Tainted: GW
3.13.0-48-generic #80-Ubuntu
[73852.453547] Hardware name: Dell Inc. Inspiron 1525
/0U990C, BIOS A13 06/27/2008
[73852.453550] e3f8fb58 c1655f92 e3f8fb98 e3f8fb88
c1056a7e f8c2ccfc
[73852.453559] e3f8fbb4 07b2 f8c2ab64 2413 f8be2a1d f8be2a1d
e4937000 e48305c0
[73852.453569] e3f8fba0 c1056ad3 0009 e3f8fb98 f8c2ccfc
e3f8fbb4 e3f8fbf4
[73852.453578] Call Trace:
[73852.453587] [c1655f92] dump_stack+0x41/0x52
[73852.453594] [c1056a7e] warn_slowpath_common+0x7e/0xa0
[73852.453629] [f8be2a1d] ? intel_modeset_check_state+0x5dd/0x750 [i915]
[73852.453659] [f8be2a1d] ? intel_modeset_check_state+0x5dd/0x750 [i915]
[73852.453664] [c1056ad3] warn_slowpath_fmt+0x33/0x40
[73852.453696] [f8be2a1d] intel_modeset_check_state+0x5dd/0x750 [i915]
[73852.453731] [f8be2c20] intel_set_mode+0x30/0x40 [i915]
[73852.453761] [f8be2cf4] intel_release_load_detect_pipe+0xc4/0xf0 [i915]
[73852.453806] [f8c0912d] intel_tv_detect+0x34d/0x510 [i915]
[73852.453818] [c14fc101] ? i2c_transfer+0x11/0xc0
[73852.453829] [f856b158]
drm_helper_probe_single_connector_modes+0x1d8/0x360 [drm_kms_helper]
[73852.453841] [c165ada0] ? mutex_lock+0x10/0x28
[73852.453875] [f882c5cd] drm_mode_getconnector+0x32d/0x390 [drm]
[73852.453902] [f882c2a0] ? drm_mode_getcrtc+0xc0/0xc0 [drm]
[73852.453920] [f881f792] drm_ioctl+0x472/0x500 [drm]
[73852.453947] [f882c2a0] ? drm_mode_getcrtc+0xc0/0xc0 [drm]
[73852.453956] [c10174fe] ? __switch_to_xtra+0xfe/0x130
[73852.453963] [c1087c51] ? set_next_entity+0xb1/0xe0
[73852.453970] [c100ef30] ? __switch_to+0x2c0/0x340
[73852.453987] [f881f320] ? drm_free_buffer+0x30/0x30 [drm]
[73852.453995] [c118b092] do_vfs_ioctl+0x2e2/0x4d0
[73852.454000] [c1659718] ? __schedule+0x358/0x770
[73852.454007] [c12ff98b] ? lockref_put_or_lock+0xb/0x30
[73852.454013] [c117b9e5] ? __fput+0x155/0x210
[73852.454018] [c118b2e0] SyS_ioctl+0x60/0x80
[73852.454023] [c166430d] sysenter_do_call+0x12/0x12
[73852.454027] ---[ end trace 1e49de400e8e1259 ]---
example
[73852.453544] CPU: 0 PID: 1970 Comm: Xorg Tainted: GW
3.13.0-48-generic #80-Ubuntu
[73852.453547] Hardware name: Dell Inc. Inspiron 1525
/0U990C, BIOS A13 06/27/2008
[73852.453550] e3f8fb58 c1655f92 e3f8fb98 e3f8fb88
c1056a7e f8c2ccfc
[73852.453559] e3f8fbb4 07b2 f8c2ab64 2413 f8be2a1d f8be2a1d
e4937000 e48305c0
[73852.453569] e3f8fba0 c1056ad3 0009 e3f8fb98 f8c2ccfc
e3f8fbb4 e3f8fbf4
[73852.453578] Call Trace:
[73852.453587] [c1655f92] dump_stack+0x41/0x52
[73852.453594] [c1056a7e] warn_slowpath_common+0x7e/0xa0
[73852.453629] [f8be2a1d] ?
[Touch-packages] [Bug 1437042] Re: xorg many call traces on startup and shutdown
Galen Thurber, please do the apport-collect (please remember to install xdiagnose or it' useless unfortunately) in a Vivid x64 live environment via http://cdimage.ubuntu.com/daily-live/current/vivid-desktop-amd64.iso . -- 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/1437042 Title: xorg many call traces on startup and shutdown Status in xorg package in Ubuntu: Incomplete Bug description: after updating from 12.0.5 to 14.04 xorg is causing many call traces on startup and shutdown computer not causing call traces under linux lite 2.2, sparky [debian8] [73852.453544] CPU: 0 PID: 1970 Comm: Xorg Tainted: GW 3.13.0-48-generic #80-Ubuntu [73852.453547] Hardware name: Dell Inc. Inspiron 1525 /0U990C, BIOS A13 06/27/2008 [73852.453550] e3f8fb58 c1655f92 e3f8fb98 e3f8fb88 c1056a7e f8c2ccfc [73852.453559] e3f8fbb4 07b2 f8c2ab64 2413 f8be2a1d f8be2a1d e4937000 e48305c0 [73852.453569] e3f8fba0 c1056ad3 0009 e3f8fb98 f8c2ccfc e3f8fbb4 e3f8fbf4 [73852.453578] Call Trace: [73852.453587] [c1655f92] dump_stack+0x41/0x52 [73852.453594] [c1056a7e] warn_slowpath_common+0x7e/0xa0 [73852.453629] [f8be2a1d] ? intel_modeset_check_state+0x5dd/0x750 [i915] [73852.453659] [f8be2a1d] ? intel_modeset_check_state+0x5dd/0x750 [i915] [73852.453664] [c1056ad3] warn_slowpath_fmt+0x33/0x40 [73852.453696] [f8be2a1d] intel_modeset_check_state+0x5dd/0x750 [i915] [73852.453731] [f8be2c20] intel_set_mode+0x30/0x40 [i915] [73852.453761] [f8be2cf4] intel_release_load_detect_pipe+0xc4/0xf0 [i915] [73852.453806] [f8c0912d] intel_tv_detect+0x34d/0x510 [i915] [73852.453818] [c14fc101] ? i2c_transfer+0x11/0xc0 [73852.453829] [f856b158] drm_helper_probe_single_connector_modes+0x1d8/0x360 [drm_kms_helper] [73852.453841] [c165ada0] ? mutex_lock+0x10/0x28 [73852.453875] [f882c5cd] drm_mode_getconnector+0x32d/0x390 [drm] [73852.453902] [f882c2a0] ? drm_mode_getcrtc+0xc0/0xc0 [drm] [73852.453920] [f881f792] drm_ioctl+0x472/0x500 [drm] [73852.453947] [f882c2a0] ? drm_mode_getcrtc+0xc0/0xc0 [drm] [73852.453956] [c10174fe] ? __switch_to_xtra+0xfe/0x130 [73852.453963] [c1087c51] ? set_next_entity+0xb1/0xe0 [73852.453970] [c100ef30] ? __switch_to+0x2c0/0x340 [73852.453987] [f881f320] ? drm_free_buffer+0x30/0x30 [drm] [73852.453995] [c118b092] do_vfs_ioctl+0x2e2/0x4d0 [73852.454000] [c1659718] ? __schedule+0x358/0x770 [73852.454007] [c12ff98b] ? lockref_put_or_lock+0xb/0x30 [73852.454013] [c117b9e5] ? __fput+0x155/0x210 [73852.454018] [c118b2e0] SyS_ioctl+0x60/0x80 [73852.454023] [c166430d] sysenter_do_call+0x12/0x12 [73852.454027] ---[ end trace 1e49de400e8e1259 ]--- example [73852.453544] CPU: 0 PID: 1970 Comm: Xorg Tainted: GW 3.13.0-48-generic #80-Ubuntu [73852.453547] Hardware name: Dell Inc. Inspiron 1525 /0U990C, BIOS A13 06/27/2008 [73852.453550] e3f8fb58 c1655f92 e3f8fb98 e3f8fb88 c1056a7e f8c2ccfc [73852.453559] e3f8fbb4 07b2 f8c2ab64 2413 f8be2a1d f8be2a1d e4937000 e48305c0 [73852.453569] e3f8fba0 c1056ad3 0009 e3f8fb98 f8c2ccfc e3f8fbb4 e3f8fbf4 [73852.453578] Call Trace: [73852.453587] [c1655f92] dump_stack+0x41/0x52 [73852.453594] [c1056a7e] warn_slowpath_common+0x7e/0xa0 [73852.453629] [f8be2a1d] ? intel_modeset_check_state+0x5dd/0x750 [i915] [73852.453659] [f8be2a1d] ? intel_modeset_check_state+0x5dd/0x750 [i915] [73852.453664] [c1056ad3] warn_slowpath_fmt+0x33/0x40 [73852.453696] [f8be2a1d] intel_modeset_check_state+0x5dd/0x750 [i915] [73852.453731] [f8be2c20] intel_set_mode+0x30/0x40 [i915] [73852.453761] [f8be2cf4] intel_release_load_detect_pipe+0xc4/0xf0 [i915] [73852.453806] [f8c0912d] intel_tv_detect+0x34d/0x510 [i915] [73852.453818] [c14fc101] ? i2c_transfer+0x11/0xc0 [73852.453829] [f856b158] drm_helper_probe_single_connector_modes+0x1d8/0x360 [drm_kms_helper] [73852.453841] [c165ada0] ? mutex_lock+0x10/0x28 [73852.453875] [f882c5cd] drm_mode_getconnector+0x32d/0x390 [drm] [73852.453902] [f882c2a0] ? drm_mode_getcrtc+0xc0/0xc0 [drm] [73852.453920] [f881f792] drm_ioctl+0x472/0x500 [drm] [73852.453947] [f882c2a0] ? drm_mode_getcrtc+0xc0/0xc0 [drm] [73852.453956] [c10174fe] ? __switch_to_xtra+0xfe/0x130 [73852.453963] [c1087c51] ? set_next_entity+0xb1/0xe0 [73852.453970] [c100ef30] ? __switch_to+0x2c0/0x340 [73852.453987] [f881f320] ? drm_free_buffer+0x30/0x30 [drm] [73852.453995] [c118b092] do_vfs_ioctl+0x2e2/0x4d0 [73852.454000] [c1659718] ? __schedule+0x358/0x770 [73852.454007] [c12ff98b] ? lockref_put_or_lock+0xb/0x30 [73852.454013] [c117b9e5] ? __fput+0x155/0x210 [73852.454018] [c118b2e0] SyS_ioctl+0x60/0x80 [73852.454023] [c166430d] sysenter_do_call+0x12/0x12
[Touch-packages] [Bug 1452956] [NEW] Stale lock file causes QtCreator to freeze when starting
Public bug reported: I was debugging why my ubuntu-sdk instance would not start up (it instead freezes indefinitely) when I noticed a stale lock file under ~/.config. I removed this file and the IDE started. To reproduce: 1. Execute the following from the terminal: touch ~/.config/QtProject/QtCreator.ini.lock 2. Start qtcreator or ubuntu-sdk. Expected results: The IDE starts as expected Actual results: The IDE hangs indefinitely Any sane IDE should be able to handle stale lock files--such a thing should not prevent the application from starting. ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Status: New -- 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/1452956 Title: Stale lock file causes QtCreator to freeze when starting Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: I was debugging why my ubuntu-sdk instance would not start up (it instead freezes indefinitely) when I noticed a stale lock file under ~/.config. I removed this file and the IDE started. To reproduce: 1. Execute the following from the terminal: touch ~/.config/QtProject/QtCreator.ini.lock 2. Start qtcreator or ubuntu-sdk. Expected results: The IDE starts as expected Actual results: The IDE hangs indefinitely Any sane IDE should be able to handle stale lock files--such a thing should not prevent the application from starting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1452956/+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 518056]
Please note that this bug needs to be resolved before this ibus issue: https://code.google.com/p/ibus/issues/detail?id=1777 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/518056 Title: cedilla appears as accented c (ć instead of ç) when typing 'c Status in IBus: Unknown Status in central project for keyboard configuration: Won't Fix Status in Modular X11 Libraries: Confirmed Status in ibus package in Ubuntu: In Progress Status in language-selector package in Ubuntu: In Progress Status in libx11 package in Ubuntu: In Progress Bug description: When typing in a US-international keyboard with dead-keys (or UK-international), typing 'c results in an accented c instead of a cedilla. There is a workaround, which is editing the /usr/lib/gtk-2.0/2.10.0/immodule-files.d/libgtk2.0-0.immodules file and changing the line cedilla Cedilla gtk20 /usr/share/locale az:ca:co:fr:gv:oc:pt:sq:tr:wa to cedilla Cedilla gtk20 /usr/share/locale az:ca:co:fr:gv:oc:pt:sq:tr:wa:en (add the 'en' at the end). However, every time some update on this file is applied, one looses the change, and we get back to the accented c. That means having to modify the file again, logout and login. For me this is no problem. But for my brother, mom, dad, etc, it is always something that at least makes me less proud of having convinced them to use Ubuntu, because they don't know what to do each time this happens. I think we really need a configurable keyboard layout, or at least (and that would be very easy), the inclusion of alternate layouts on install that for the dead-key options (as US-deadkey and UK-deakey), alternate layouts as US-deadkey-cedilla. This change is relevant for at least Portuguese and French. To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/518056/+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 1452300] Re: Reboot takes too long
** Description changed: Test case. + - Without usb cable connected - In the greeter screen, long press power button to display power dialog. - Tap to reboot. Expected result. - Must take similar time than stable. Actual result. - Stable takes 30 seconds to show the bq white screen. - 274 takes bewteen than 2 and 3 minutes to show the bq screen. syslog: May 6 14:16:35 ubuntu-phablet rsyslogd: [origin software=rsyslogd swVersion=7.4.4 x-pid=816 x-info=http://w ww.rsyslog.com] exiting on signal 15. May 6 14:20:05 ubuntu-phablet rsyslogd: [origin software=rsyslogd swVersion=7.4.4 x-pid=817 x-info=http://w ww.rsyslog.com] start current build number: 274 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to powerd in Ubuntu. https://bugs.launchpad.net/bugs/1452300 Title: Reboot takes too long Status in the base for Ubuntu mobile products: New Status in powerd package in Ubuntu: New Status in unity8 package in Ubuntu: Incomplete Status in powerd source package in Vivid: New Status in powerd package in Ubuntu RTM: New Bug description: Test case. - Make sure phone is not plugged in. - In the greeter screen, long press power button to display power dialog. - Tap to reboot. Expected result. - Must take similar time than stable. Actual result. - Stable takes 30 seconds to show the bq white screen. - 274 takes bewteen than 2 and 3 minutes to show the bq screen. syslog: May 6 14:16:35 ubuntu-phablet rsyslogd: [origin software=rsyslogd swVersion=7.4.4 x-pid=816 x-info=http://w ww.rsyslog.com] exiting on signal 15. May 6 14:20:05 ubuntu-phablet rsyslogd: [origin software=rsyslogd swVersion=7.4.4 x-pid=817 x-info=http://w ww.rsyslog.com] start current build number: 274 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1452300/+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 1452300] Re: Reboot takes too long
** Description changed: Test case. - - Without usb cable connected + - Make sure phone is not plugged in. - In the greeter screen, long press power button to display power dialog. - Tap to reboot. Expected result. - Must take similar time than stable. Actual result. - Stable takes 30 seconds to show the bq white screen. - 274 takes bewteen than 2 and 3 minutes to show the bq screen. syslog: May 6 14:16:35 ubuntu-phablet rsyslogd: [origin software=rsyslogd swVersion=7.4.4 x-pid=816 x-info=http://w ww.rsyslog.com] exiting on signal 15. May 6 14:20:05 ubuntu-phablet rsyslogd: [origin software=rsyslogd swVersion=7.4.4 x-pid=817 x-info=http://w ww.rsyslog.com] start current build number: 274 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to powerd in Ubuntu. https://bugs.launchpad.net/bugs/1452300 Title: Reboot takes too long Status in the base for Ubuntu mobile products: New Status in powerd package in Ubuntu: New Status in unity8 package in Ubuntu: Incomplete Status in powerd source package in Vivid: New Status in powerd package in Ubuntu RTM: New Bug description: Test case. - Make sure phone is not plugged in. - In the greeter screen, long press power button to display power dialog. - Tap to reboot. Expected result. - Must take similar time than stable. Actual result. - Stable takes 30 seconds to show the bq white screen. - 274 takes bewteen than 2 and 3 minutes to show the bq screen. syslog: May 6 14:16:35 ubuntu-phablet rsyslogd: [origin software=rsyslogd swVersion=7.4.4 x-pid=816 x-info=http://w ww.rsyslog.com] exiting on signal 15. May 6 14:20:05 ubuntu-phablet rsyslogd: [origin software=rsyslogd swVersion=7.4.4 x-pid=817 x-info=http://w ww.rsyslog.com] start current build number: 274 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1452300/+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 1452300] Re: Reboot takes too long
Fixed the test steps; phone must not be connected via USB. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to powerd in Ubuntu. https://bugs.launchpad.net/bugs/1452300 Title: Reboot takes too long Status in the base for Ubuntu mobile products: New Status in powerd package in Ubuntu: New Status in unity8 package in Ubuntu: Incomplete Status in powerd source package in Vivid: New Status in powerd package in Ubuntu RTM: New Bug description: Test case. - Make sure phone is not plugged in. - In the greeter screen, long press power button to display power dialog. - Tap to reboot. Expected result. - Must take similar time than stable. Actual result. - Stable takes 30 seconds to show the bq white screen. - 274 takes bewteen than 2 and 3 minutes to show the bq screen. syslog: May 6 14:16:35 ubuntu-phablet rsyslogd: [origin software=rsyslogd swVersion=7.4.4 x-pid=816 x-info=http://w ww.rsyslog.com] exiting on signal 15. May 6 14:20:05 ubuntu-phablet rsyslogd: [origin software=rsyslogd swVersion=7.4.4 x-pid=817 x-info=http://w ww.rsyslog.com] start current build number: 274 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1452300/+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 1452300] Re: Reboot takes too long
Problem is that we can only reproduce this issue without a usb cable, as that makes the kernel to acquire a wakelock. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to powerd in Ubuntu. https://bugs.launchpad.net/bugs/1452300 Title: Reboot takes too long Status in the base for Ubuntu mobile products: New Status in powerd package in Ubuntu: New Status in unity8 package in Ubuntu: Incomplete Status in powerd source package in Vivid: New Status in powerd package in Ubuntu RTM: New Bug description: Test case. - Make sure phone is not plugged in. - In the greeter screen, long press power button to display power dialog. - Tap to reboot. Expected result. - Must take similar time than stable. Actual result. - Stable takes 30 seconds to show the bq white screen. - 274 takes bewteen than 2 and 3 minutes to show the bq screen. syslog: May 6 14:16:35 ubuntu-phablet rsyslogd: [origin software=rsyslogd swVersion=7.4.4 x-pid=816 x-info=http://w ww.rsyslog.com] exiting on signal 15. May 6 14:20:05 ubuntu-phablet rsyslogd: [origin software=rsyslogd swVersion=7.4.4 x-pid=817 x-info=http://w ww.rsyslog.com] start current build number: 274 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1452300/+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 1437512] Re: [Inspiron 1525, SigmaTel STAC9228, Speaker, Internal] unmute problem
I'm using the current 14.04 packages /usr/share/alsa-base/alsa-info.sh Newer version detected: 0.4.64 To view the ChangeLog, please visit http://www.alsa-project.org/alsa-info.sh.changelog ALSA-Info script has been downloaded as /tmp/alsa-info.xnzesmfLOs. Please re-run the script from new location. sudo: /tmp/alsa-info.xnzesmfLOs: command not found ** Attachment added: script output (speaker not working, unwanted mute) https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1437512/+attachment/4393298/+files/alsa-info.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1437512 Title: [Inspiron 1525, SigmaTel STAC9228, Speaker, Internal] unmute problem Status in alsa-driver package in Ubuntu: Incomplete Bug description: system goes into power save mode on AC, resuming from login screen keboard unmute does not unmute alsa control SPEAKER master, PCM will unmute. power save mode adds undesired MUTE of alsa's speaker expected power manager to not mute speaker only MASTER PCM ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16 Uname: Linux 3.13.0-48-generic i686 ApportVersion: 2.14.1-0ubuntu3.8 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kiera 2273 F pulseaudio CurrentDesktop: XFCE Date: Fri Mar 27 19:30:10 2015 InstallationDate: Installed on 2014-04-21 (340 days ago) InstallationMedia: Xubuntu 12.04.4 LTS Precise Pangolin - Release i386 (20140205) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful Symptom_Card: Built-in Audio - HDA Intel Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [Inspiron 1525, SigmaTel STAC9228, Speaker, Internal] Playback problem UpgradeStatus: Upgraded to trusty on 2015-03-24 (3 days ago) dmi.bios.date: 06/27/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 0U990C dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA13:bd06/27/2008:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn0U990C:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1525 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1437512/+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 1440157] Re: WARNING **: Could not connect to geoname lookup server: Operation was cancelled
This bug was fixed in the package libtimezonemap - 0.4.4 --- libtimezonemap (0.4.4) wily; urgency=medium [ David Shea ] * Update the SVG, generated new map images, and cleaned up a couple other image-related issues. * Constrain the location when clicking in the same spot. [ Lars Uebernickel ] * Port to libsoup directly for geoname requests, fix some memory leaks and do not reuse GCancellables. (LP: #1440157) -- Iain Lane iain.l...@canonical.com Fri, 08 May 2015 00:18:37 +0100 ** Changed in: libtimezonemap (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libtimezonemap in Ubuntu. https://bugs.launchpad.net/bugs/1440157 Title: WARNING **: Could not connect to geoname lookup server: Operation was cancelled Status in One Hundred Papercuts: Confirmed Status in Unity Control Center: New Status in libtimezonemap package in Ubuntu: Fix Released Status in unity-control-center package in Ubuntu: Confirmed Bug description: Test Case: open Date Time panel Clock Enable Time in other locations Click Choose Locations... No other locations can be added ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: indicator-datetime 13.10.0+15.04.20150331-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CasperVersion: 1.358 CurrentDesktop: Unity Date: Fri Apr 3 23:54:13 2015 LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Beta amd64 (20150326) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: indicator-datetime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1440157/+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 1451232] Re: container does not receive IP address after 15.04 upgrade
*** This bug is a duplicate of bug 1452601 *** https://bugs.launchpad.net/bugs/1452601 Thanks. I'm going to mark this a dup of 1452601 which has some more information to suggest a possible fix. ** Changed in: lxc (Ubuntu) Status: Incomplete = Triaged ** This bug has been marked a duplicate of bug 1452601 vivid container's networking.service fails on boot with signal=PIPE -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1451232 Title: container does not receive IP address after 15.04 upgrade Status in lxc package in Ubuntu: Triaged Bug description: Perhaps this is an upgrade issue, perhaps it is a installation issue. In either case, there should be more information about upgrading lxc. After upgrading to Ubuntu 15.04, my container no longer started. After upgrading, I had to remove the following line from the config file for my container: lxc.network.link = lxcbr0 Here is the attempt at starting before commenting out the line: kevin@nereocystis:~$ sudo lxc-start -F -n escale_build lxc-start: conf.c: instantiate_veth: 2660 failed to attach 'vethTCPSQO' to the bridge 'lxcbr0': Operation not permitted lxc-start: conf.c: lxc_create_network: 2943 failed to create netdev lxc-start: start.c: lxc_spawn: 914 failed to create the network lxc-start: start.c: __lxc_start: 1164 failed to spawn 'escale_build' lxc-start: lxc_start.c: main: 344 The container failed to start. lxc-start: lxc_start.c: main: 348 Additional information can be obtained by setting the --logfile and --logpriority options. After commenting out this line, the container starts, but no IP address is assigned in the container. But no IP address was assigned: For info, please visit https://www.isc.org/software/dhcp/ Listening on LPF/eth0/9a:9b:92:81:87:62 Sending on LPF/eth0/9a:9b:92:81:87:62 Sending on Socket/fallback DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 14 No DHCPOFFERS received. No working leases in persistent database - sleeping. done. Eventually, I purged lxc, and reinstalled it, with the same results. I also tried creating a new container from scratch using the instructions in: https://help.ubuntu.com/lts/serverguide/lxc.html#lxc-network sudo lxc-create --template download --name u1 Again, no IP address. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lxc 1.1.2-0ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun May 3 10:44:23 2015 InstallationDate: Installed on 2013-06-02 (699 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) KernLog: [56541.698842] audit: type=1400 audit(1430671655.848:49): apparmor=DENIED operation=mount info=failed flags match error=-13 profile=lxc-container-default name=/ pid=3109 comm=mount flags=ro, remount, relatime [56620.060697] audit: type=1400 audit(1430671734.154:50): apparmor=DENIED operation=mount info=failed type match error=-13 profile=lxc-container-default name=/sys/fs/cgroup/ pid=3403 comm=systemd flags=ro, nosuid, nodev, noexec, remount, strictatime SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1451232/+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 1452538] [NEW] opendkim does not start properly when ldap server can't be contacted
You have been subscribed to a public bug: when starting opendkim, if ldap is in use and the server cannot be contacted, opendkim gets stuck in a state where the system appears to think it has started, but is not actually running: systemctl -l status opendkim ● opendkim.service - LSB: Start the OpenDKIM service Loaded: loaded (/etc/init.d/opendkim) Active: active (exited) since Wed 2015-05-06 23:16:20 EDT; 1min 24s ago Docs: man:systemd-sysv-generator(8) Process: 589 ExecStart=/etc/init.d/opendkim start (code=exited, status=0/SUCCESS) May 06 23:16:19 server systemd[1]: Starting LSB: Start the OpenDKIM service... May 06 23:16:20 server opendkim[589]: Starting OpenDKIM: opendkim: /etc/opendkim/opendkim.conf: ldap://dsa.example.com/ou=domains,ou=mail,dc=example,dc=com?host?sub?(host=$d): dkimf_db_open(): Can't contact LDAP server May 06 23:16:20 server opendkim[589]: opendkim. May 06 23:16:20 server systemd[1]: Started LSB: Start the OpenDKIM service. ps -aefwww | grep -iF dkim root 858 815 0 23:18 pts/000:00:00 grep -iF dkim additional attempts to start opendkim don't indicate failure, but also don't work: systemctl start opendkim ps -aefwww | grep -iF dkim root 863 815 0 23:19 pts/000:00:00 grep -iF dkim additionally, as can be seen in the above systemctl status output, systemd appears to think that opendkim has started successfully, but when testing manually, it does not: /usr/sbin/opendkim -x /etc/opendkim/opendkim.conf -u opendkim -P /var/run/opendkim/opendkim.pid opendkim: /etc/opendkim/opendkim.conf: ldap://dsa.example.com/ou=domains,ou=mail,dc=example,dc=com?host?sub?(host=$d): dkimf_db_open(): Can't contact LDAP server echo $? 78 lastly, stopping opendkim [even though it's not really running] and then starting it again then results in it actually running: systemctl stop opendkim systemctl start opendkim ps -aefwww | grep -iF opendkim opendkim 1105 1 0 23:24 ?00:00:00 /usr/sbin/opendkim -x /etc/opendkim/opendkim.conf -u opendkim -P /var/run/opendkim/opendkim.pid opendkim 1106 1105 0 23:24 ?00:00:00 /usr/sbin/opendkim -x /etc/opendkim/opendkim.conf -u opendkim -P /var/run/opendkim/opendkim.pid root 1117 815 0 23:25 pts/000:00:00 grep -iF opendkim ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- opendkim does not start properly when ldap server can't be contacted https://bugs.launchpad.net/bugs/1452538 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1451247] Re: wrong ntpdate dependency in ubuntu-minimal
The attachment remove_ntpdate.patch seems to be a patch. If it isn't, please remove the patch flag from the attachment, remove the patch tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- 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/1451247 Title: wrong ntpdate dependency in ubuntu-minimal Status in ubuntu-meta package in Ubuntu: New Bug description: Ubuntu-minimal has a hardcoded dependency on ntpdate which is entirely unnecessary because for basic minimal task of syncing time with ntp server systemd-timesyncd is more than enough. Replacing this dependency will allow to save some space on install media and make learning easier for new users because timesyncd follows exact same configuration convention as the rest of the stack which makes it natural to get aquainted with. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1451247/+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 1302004] Re: Indicator-datetime still doesn't list all events for today's date (Trusty/Utopic/Vivid)
The attachment upcoming-after-end.patch seems to be a patch. If it isn't, please remove the patch flag from the attachment, remove the patch tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- 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/1302004 Title: Indicator-datetime still doesn't list all events for today's date (Trusty/Utopic/Vivid) Status in indicator-datetime package in Ubuntu: Confirmed Bug description: This bug is related to this bug: Bug #1293646 (Which is marked as fix released) With latest update of indicator (13.10.0+14.04.20140328-0ubuntu1) it lists all events for all past selected dates properly (which was fixed in bug Bug #1293646) except today's date. When I click on any past date in calendar it shows: 1. all all-day events for the day. 2. all events with time for the day 3. upcoming (future) all-day events 4. upcoming (future) events with time But when I click on today's date it only shows: 1. future all day events 2. future events with time I still have to click on previous day's date to find out all all-day events for today. The behavior (showing all events for a day) should be same for any date, including today's date. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1302004/+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 1452538] Re: opendkim does not start properly when ldap server can't be contacted
thanks for this. i'd tried LDAPSoftStart, which didn't work, missing that it had been renamed. i've added SoftStart yes to the config, but the behavior seems to be the same. i can corroborate that this seems new with 15.04/systemd. another older system like yours works ok. -- 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/1452538 Title: opendkim does not start properly when ldap server can't be contacted Status in systemd package in Ubuntu: New Bug description: when starting opendkim, if ldap is in use and the server cannot be contacted, opendkim gets stuck in a state where the system appears to think it has started, but is not actually running: systemctl -l status opendkim ● opendkim.service - LSB: Start the OpenDKIM service Loaded: loaded (/etc/init.d/opendkim) Active: active (exited) since Wed 2015-05-06 23:16:20 EDT; 1min 24s ago Docs: man:systemd-sysv-generator(8) Process: 589 ExecStart=/etc/init.d/opendkim start (code=exited, status=0/SUCCESS) May 06 23:16:19 server systemd[1]: Starting LSB: Start the OpenDKIM service... May 06 23:16:20 server opendkim[589]: Starting OpenDKIM: opendkim: /etc/opendkim/opendkim.conf: ldap://dsa.example.com/ou=domains,ou=mail,dc=example,dc=com?host?sub?(host=$d): dkimf_db_open(): Can't contact LDAP server May 06 23:16:20 server opendkim[589]: opendkim. May 06 23:16:20 server systemd[1]: Started LSB: Start the OpenDKIM service. ps -aefwww | grep -iF dkim root 858 815 0 23:18 pts/000:00:00 grep -iF dkim additional attempts to start opendkim don't indicate failure, but also don't work: systemctl start opendkim ps -aefwww | grep -iF dkim root 863 815 0 23:19 pts/000:00:00 grep -iF dkim additionally, as can be seen in the above systemctl status output, systemd appears to think that opendkim has started successfully, but when testing manually, it does not: /usr/sbin/opendkim -x /etc/opendkim/opendkim.conf -u opendkim -P /var/run/opendkim/opendkim.pid opendkim: /etc/opendkim/opendkim.conf: ldap://dsa.example.com/ou=domains,ou=mail,dc=example,dc=com?host?sub?(host=$d): dkimf_db_open(): Can't contact LDAP server echo $? 78 lastly, stopping opendkim [even though it's not really running] and then starting it again then results in it actually running: systemctl stop opendkim systemctl start opendkim ps -aefwww | grep -iF opendkim opendkim 1105 1 0 23:24 ?00:00:00 /usr/sbin/opendkim -x /etc/opendkim/opendkim.conf -u opendkim -P /var/run/opendkim/opendkim.pid opendkim 1106 1105 0 23:24 ?00:00:00 /usr/sbin/opendkim -x /etc/opendkim/opendkim.conf -u opendkim -P /var/run/opendkim/opendkim.pid root 1117 815 0 23:25 pts/000:00:00 grep -iF opendkim To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1452538/+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 1452173] Re: [Dell Precision M4800] Regression: screen brightness control broken in 15.04
Marius B. Kotsbak, thank you for reporting this and helping make Ubuntu better. As per http://www.dell.com/support/home/us/en/19/product- support/product/precision-m4800-workstation/drivers an update to your computer's buggy and outdated BIOS is available (A13). 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-a13 ** No longer affects: linux (Ubuntu) ** No longer affects: xorg (Ubuntu) ** Changed in: nvidia-graphics-drivers-346-updates (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1452173 Title: [Dell Precision M4800] Regression: screen brightness control broken in 15.04 Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Incomplete Bug description: In Ubuntu 15.04, I no longer am able to control the screen brightness. See possible similar bug #1411514 for 14.04.1. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 346.59 Tue Mar 31 14:10:31 PDT 2015 GCC version: gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13) ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Date: Wed May 6 10:12:03 2015 DistUpgraded: 2015-04-24 01:12:19,566 DEBUG enabling apt cron job DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 DistroCodename: vivid DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05cc] InstallationDate: Installed on 2014-03-12 (419 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 MachineType: Dell Inc. Precision M4800 PlymouthDebug: Error: [Errno 13] Permission denied: '/var/log/plymouth-debug.log' ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic.efi.signed root=UUID=61c860cd-d55d-4e70-85a3-615b677b5811 ro nomodeset=1 splash quiet plymouth:debug=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to vivid on 2015-04-23 (12 days ago) dmi.bios.date: 12/03/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 077KCT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd12/03/2014:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn077KCT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4800 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Tue May 5 22:22:48 2015 xserver.configfile: default xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.17.1-0ubuntu3 To manage notifications about this bug go to:
[Touch-packages] [Bug 1452538] Re: opendkim does not start properly when ldap server can't be contacted
I can't replicate this on an older release with upstart instead of systemd. service opendkim start Starting OpenDKIM: opendkim: /etc/opendkim.conf: ldap://192.0.2.1/ou=people,dc=example,dc=com?DKIMSelector?sub?(DKIMIdentity=$d): dkimf_db_open(): Can't contact LDAP server opendkim. # ps -AF|grep opendkim opendkim 677 1 0 63960 1648 0 Apr30 ?00:00:01 rsyslogd root 3012 12880 0 2216 648 1 00:11 pts/400:00:00 grep opendkim # service opendkim status * opendkim is not running I suspect this is a systemd issue. As a workaround, you might add SoftStart true to your opendkim.conf. That should cause it to start normally without LDAP. ** Package changed: opendkim (Ubuntu) = systemd (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1452538 Title: opendkim does not start properly when ldap server can't be contacted Status in systemd package in Ubuntu: New Bug description: when starting opendkim, if ldap is in use and the server cannot be contacted, opendkim gets stuck in a state where the system appears to think it has started, but is not actually running: systemctl -l status opendkim ● opendkim.service - LSB: Start the OpenDKIM service Loaded: loaded (/etc/init.d/opendkim) Active: active (exited) since Wed 2015-05-06 23:16:20 EDT; 1min 24s ago Docs: man:systemd-sysv-generator(8) Process: 589 ExecStart=/etc/init.d/opendkim start (code=exited, status=0/SUCCESS) May 06 23:16:19 server systemd[1]: Starting LSB: Start the OpenDKIM service... May 06 23:16:20 server opendkim[589]: Starting OpenDKIM: opendkim: /etc/opendkim/opendkim.conf: ldap://dsa.example.com/ou=domains,ou=mail,dc=example,dc=com?host?sub?(host=$d): dkimf_db_open(): Can't contact LDAP server May 06 23:16:20 server opendkim[589]: opendkim. May 06 23:16:20 server systemd[1]: Started LSB: Start the OpenDKIM service. ps -aefwww | grep -iF dkim root 858 815 0 23:18 pts/000:00:00 grep -iF dkim additional attempts to start opendkim don't indicate failure, but also don't work: systemctl start opendkim ps -aefwww | grep -iF dkim root 863 815 0 23:19 pts/000:00:00 grep -iF dkim additionally, as can be seen in the above systemctl status output, systemd appears to think that opendkim has started successfully, but when testing manually, it does not: /usr/sbin/opendkim -x /etc/opendkim/opendkim.conf -u opendkim -P /var/run/opendkim/opendkim.pid opendkim: /etc/opendkim/opendkim.conf: ldap://dsa.example.com/ou=domains,ou=mail,dc=example,dc=com?host?sub?(host=$d): dkimf_db_open(): Can't contact LDAP server echo $? 78 lastly, stopping opendkim [even though it's not really running] and then starting it again then results in it actually running: systemctl stop opendkim systemctl start opendkim ps -aefwww | grep -iF opendkim opendkim 1105 1 0 23:24 ?00:00:00 /usr/sbin/opendkim -x /etc/opendkim/opendkim.conf -u opendkim -P /var/run/opendkim/opendkim.pid opendkim 1106 1105 0 23:24 ?00:00:00 /usr/sbin/opendkim -x /etc/opendkim/opendkim.conf -u opendkim -P /var/run/opendkim/opendkim.pid root 1117 815 0 23:25 pts/000:00:00 grep -iF opendkim To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1452538/+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 1389954] Re: Make .lxc domain name resolution easier to discover and enable
I think dpm-vivid would be the right one. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1389954 Title: Make .lxc domain name resolution easier to discover and enable Status in lxc package in Ubuntu: Confirmed Bug description: The lxc package on ubuntu does almost nothing to help a user enable DNS resolution for containers via dnsmaq, let alone discover that it is possible. How about enabling it by default? I think all it would take is adding server=/lxc/10.0.3.1 to a file in /etc/NetworkManager/dnsmasq.d/ and uncommenting LXC_DOMAIN=lxc in /etc/default/lxc-net. Even if there's a good reason not to enable this by default, shouldn't it at least be clearly documented someplace obvious instead of buried in a system config file with a misleading comment that mentions the wrong dnsmasq file to edit? (The one currently mentioned by /etc/default/lxc-net does nothing on ubuntu desktop systems, because ubuntu's NetworkManager starts dnsmasq with a special config directory.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1389954/+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 1382302] Re: Broadcom Corporation BCM4352 bluetooth adapter not finding any bluetooth devices
What's the commit hash for the fix in the upstream kernel? I'm not seeing anything explicitly listing the BCM4352 in btusb.c in the tree or on the mailing list. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1382302 Title: Broadcom Corporation BCM4352 bluetooth adapter not finding any bluetooth devices Status in bluez package in Ubuntu: Fix Released Bug description: Broadcom Corporation BCM4352 wi-fi/bluetooth adapter is unable to find/detect Bluetooth devices, and Bluetooth devices can not see the Ubuntu PC, even when in pairing mode. (Here is a similar bug, but for a different Broadcom device: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1264311) MOTHERBOARD INFO $ sudo dmidecode -t baseboard # dmidecode 2.12 SMBIOS 2.7 present. Handle 0x0002, DMI type 2, 15 bytes Base Board Information Manufacturer: ASRock Product Name: Z87E-ITX Version: Serial Number: E80-34027900563 Asset Tag: Features: Board is a hosting board Board is replaceable Location In Chassis: Chassis Handle: 0x0003 Type: Motherboard Contained Object Handles: 0 UBUNTU INFO $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 14.04.1 LTS Release: 14.04 Codename: trusty $ uname -a Linux Computer 3.13.0-37-generic #64-Ubuntu SMP Mon Sep 22 21:28:38 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux WI-FI DEVICE INFO $ lspci | grep Broadcom 03:00.0 Network controller: Broadcom Corporation BCM4352 802.11ac Wireless Network Adapter (rev 03) Note, the BCM4352 802.11ac device is a combination Wi-Fi + Bluetooth adapter. BLUETOOTH DEVICE INFO $ lsusb Bus 002 Device 002: ID 8087:8000 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 13d3:3404 IMC Networks Bus 001 Device 002: ID 8087:8008 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 004: ID 1b1c:0c04 Corsair Bus 003 Device 003: ID 046d:0826 Logitech, Inc. Bus 003 Device 002: ID 09da:024f A4 Tech Co., Ltd RF Receiver and G6-20D Wireless Optical Mouse Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub The system log does not show any errors when the btusb module is loaded... kernel: [36245.996355] usbcore: registered new interface driver btusb bluetoothd[833]: Unknown command complete for opcode 19 bluetoothd[833]: Endpoint registered: sender=:1.1820 path=/MediaEndpoint/HFPAG bluetoothd[833]: Endpoint registered: sender=:1.1820 path=/MediaEndpoint/HFPHS bluetoothd[833]: Endpoint registered: sender=:1.1820 path=/MediaEndpoint/A2DPSource bluetoothd[833]: Endpoint registered: sender=:1.1820 path=/MediaEndpoint/A2DPSink bluetoothd[833]: Endpoint registered: sender=:1.77 path=/MediaEndpoint/HFPAG bluetoothd[833]: Endpoint registered: sender=:1.77 path=/MediaEndpoint/HFPHS bluetoothd[833]: Endpoint registered: sender=:1.77 path=/MediaEndpoint/A2DPSource bluetoothd[833]: Endpoint registered: sender=:1.77 path=/MediaEndpoint/A2DPSink bluetoothd[833]: Adapter /org/bluez/833/hci0 has been enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1382302/+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 264144] Re: NetworkManager VPN configuration export does not work
Confirming the issue on Ubuntu 15.04. -- 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/264144 Title: NetworkManager VPN configuration export does not work Status in NetworkManager: Invalid Status in Network management framework (OpenVPN plugin): Fix Released Status in network-manager package in Ubuntu: Invalid Status in network-manager-openvpn package in Ubuntu: Fix Released Status in network-manager-pptp package in Ubuntu: Triaged Bug description: Intrepid, network-manager: 0.7~~svn20080818t061112+eni0-0ubuntu1 Subject says it. To reproduce: 1. Configure VPN connection 2. Try to Export it to a file As a result I got cryptic error message dialog: === Cannot export VPN connection The VPN connection 'vpn_test' could not be exported to vpn_test (pptp).conf. Error: unknown error. === Expected behavior: Configuration saved to a file. = WORKAROUND The configuration is saved in a file in /etc/NetworkManager/system-connections/ that has the same name as the connection. This file can be examined with a text editor and/or copied around to other machines. source: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/264144/comments/27 WORKAROUND = To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/264144/+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 1437209] Re: package ubuntu-keyring 2012.05.19 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-keyring (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1437209 Title: package ubuntu-keyring 2012.05.19 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 Status in ubuntu-keyring package in Ubuntu: Confirmed Bug description: This appeared randomly after upgrading from terminal. When I run software updater, it keeps prompting from Partial upgrade ProblemType: Package DistroRelease: Ubuntu 14.04 Package: ubuntu-keyring 2012.05.19 ProcVersionSignature: Ubuntu 3.13.0-46.79-generic 3.13.11-ckt15 Uname: Linux 3.13.0-46-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.8 AptOrdering: ubuntu-keyring: Install ubuntu-keyring: Configure Architecture: amd64 Date: Fri Mar 27 13:43:09 2015 DuplicateSignature: package:ubuntu-keyring:2012.05.19:subprocess installed post-installation script returned error exit status 2 ErrorMessage: subprocess installed post-installation script returned error exit status 2 InstallationDate: Installed on 2014-05-08 (322 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) PackageArchitecture: all SourcePackage: ubuntu-keyring Title: package ubuntu-keyring 2012.05.19 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyring/+bug/1437209/+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
