[Touch-packages] [Bug 1419704] Re: Mir clients leak gbm_device in Mesa EGL platform
This bug was fixed in the package mesa - 10.4.2-2ubuntu5 --- mesa (10.4.2-2ubuntu5) vivid; urgency=medium * Fix ftbfs from no longer including libmirclient-dev. -- Maarten LankhorstWed, 11 Feb 2015 09:21:54 +0100 ** Changed in: mesa (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 mesa in Ubuntu. https://bugs.launchpad.net/bugs/1419704 Title: Mir clients leak gbm_device in Mesa EGL platform Status in Mir: In Progress Status in mesa package in Ubuntu: Fix Released Bug description: In case the Mir Mesa EGL platform allocates the gbm_device itself (which happens for normal clients), then eglTerminate() doesn't free the gbm_device properly. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1419704/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1272781] Re: Often system freezes
Unfortunately I can't decide because I don't use the proprietary drivers anymore. -- 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/1272781 Title: Often system freezes Status in xorg package in Ubuntu: Incomplete Bug description: I've been experiencing very often system freezes, specially when I close my laptop lid. I can't reproduce this issue, it just happens at random times. My laptop is new and I highly doubt it's a HW problem, it must be a graphics driver issue. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Jan 26 01:07:45 2014 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: fglrx, 13.251, 3.11.0-15-generic, x86_64: installed virtualbox, 4.2.16, 3.11.0-14-generic, x86_64: installed virtualbox, 4.2.16, 3.11.0-15-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0572] Advanced Micro Devices, Inc. [AMD/ATI] Chelsea LP [Radeon HD 7730M] [1002:682f] (rev ff) (prog-if ff) InstallationDate: Installed on 2013-11-16 (70 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Dell Inc. Inspiron 7520 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic.efi.signed root=UUID=fdebe919-101f-4bc7-84c1-f209c05c18c8 ro quiet splash acpi_osi=Linux plymouth:debug splash quiet drm.debug=0xe acpi_backlight=vendor SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/15/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0PXH02 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A09 dmi.modalias: dmi:bvnDellInc.:bvrA09:bd11/15/2012:svnDellInc.:pnInspiron7520:pvrA09:rvnDellInc.:rn0PXH02:rvrA00:cvnDellInc.:ct8:cvrA09: dmi.product.name: Inspiron 7520 dmi.product.version: A09 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1272781/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1419623] Re: systemd unmounts mounted filesystems when lxcfs is installed
** Branch linked: lp:ubuntu/vivid-proposed/lxcfs -- 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/1419623 Title: systemd unmounts mounted filesystems when lxcfs is installed Status in lxcfs package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: In Progress Bug description: This seems to have been triggered by the glib update on ubuntu-desktop ppa. No partitions from fstab (apart from root of course) are getting mounted at boot. This is just a little problematic when /home is on a different partition! ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 218-7ubuntu1 [modified: lib/systemd/system/ifup@.service] ProcVersionSignature: Ubuntu 3.18.0-12.13-generic 3.18.4 Uname: Linux 3.18.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Feb 9 17:30:12 2015 InstallationDate: Installed on 2012-09-23 (869 days ago) InstallationMedia: Ubuntu GNOME Remix 12.10 "Quantal Quetzal" - Alpha amd64(20120922) MachineType: Gigabyte Technology Co., Ltd. P67A-UD3R-B3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-12-generic root=UUID=71eeb904-068b-41c2-9d34-59365ca4c3ad ro quiet splash init=/lib/systemd/systemd systemd.log_level=debug SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/21/2012 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F9 dmi.board.name: P67A-UD3R-B3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF9:bd03/21/2012:svnGigabyteTechnologyCo.,Ltd.:pnP67A-UD3R-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP67A-UD3R-B3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P67A-UD3R-B3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxcfs/+bug/1419623/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1411751] Re: Attribute in news section of today scope has wrong aspect ratio depending on grid size
** Changed in: unity8 (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1411751 Title: Attribute in news section of today scope has wrong aspect ratio depending on grid size Status in the base for Ubuntu mobile products: Confirmed Status in unity8 package in Ubuntu: In Progress Bug description: Open the Today scope in Arale Go to News section BBC attribute aspect ratio is not correct. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1411751/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 583994] Re: Consider replacing ntpdate calls by 'ntpd -g'
I think going forward with this ticket instead of the much older bug 61619 is preferable. ntpdate has been deprecated upstream for a long time as previously pointed out. The NTP code has seen numerous security vulnerabilities and we have to assume that ntpdate is not receiving the same scrutiny anymore when compared to ntpd. Setting milestone for vivid, hoping that it is not too late, yet. ** Changed in: ubuntu-meta (Ubuntu) Importance: Undecided => Medium ** Changed in: ubuntu-meta (Ubuntu) Status: Confirmed => Triaged ** Changed in: ubuntu-meta (Ubuntu) Milestone: None => ubuntu-15.02 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/583994 Title: Consider replacing ntpdate calls by 'ntpd -g' Status in NTP: New Status in ntp package in Ubuntu: Invalid Status in ubuntu-meta package in Ubuntu: Triaged Bug description: Binary package hint: ntp Given that 'ntpdate' is being obsoleted upstream [1], we should replace 'ntpdate' usage by: * ntpd -qg (if we really want to set the time and exit), or * ntpd-g (if we want to keep ntpd running) the '-q' option will set the clock once, and exit; the 'g' allows for large corrections to the clock, like what is done by 'ntpdate'. [1] http://www.eecis.udel.edu/~mills/ntp/html/ntpdate.html To manage notifications about this bug go to: https://bugs.launchpad.net/ntp/+bug/583994/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1417773] Re: Unity8 completely frozen (unable to unlock, receive calls, etc)
I think we might have two unrelated deadlocks here. rsalveti's is a dbus deadlock. saviq's is a Mir deadlock. -- 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/1417773 Title: Unity8 completely frozen (unable to unlock, receive calls, etc) Status in the base for Ubuntu mobile products: New Status in Mir: Triaged Status in mir package in Ubuntu: New Status in unity8 package in Ubuntu RTM: New Bug description: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 224 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed last update: 2015-01-29 18:53:09 version version: 224 version ubuntu: 20150129 version device: 20150129-c75dcfb version custom: 20150129-528-26-182 Was driving around with my car, and noticed once I got back home that my clock was stuck in a previous time (~20min before getting home), and after trying to use the phone I noticed unity8 was completely stuck, but the underling OS was still running fine. The worst here is that we're unable to notify the user about calls, as the interface is completely stuck. Another bad thing is that this could as well happen when the user is sleeping or something, without an easy way to know until he tries to use the phone. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1417773/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1421140] Re: package bluez 4.101-0ubuntu13 [modified: lib/udev/hid2hci usr/bin/ciptool usr/bin/hcitool usr/bin/l2ping usr/bin/l2test usr/bin/rctest usr/bin/rfcomm usr/bin/sdptool
** Tags removed: need-duplicate-check -- 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/1421140 Title: package bluez 4.101-0ubuntu13 [modified: lib/udev/hid2hci usr/bin/ciptool usr/bin/hcitool usr/bin/l2ping usr/bin/l2test usr/bin/rctest usr/bin/rfcomm usr/bin/sdptool usr/sbin/bluetoothd] failed to install/upgrade: paketet är i ett väldigt dåligt inkonsistent läge; du bör ominstallera det innan du försöker ta bort det. Status in bluez package in Ubuntu: New Bug description: I Can't run updates anymore. But this fixed my issues why the computer didn't shut down correctly ha-ha. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: bluez 4.101-0ubuntu13 [modified: lib/udev/hid2hci usr/bin/ciptool usr/bin/hcitool usr/bin/l2ping usr/bin/l2test usr/bin/rctest usr/bin/rfcomm usr/bin/sdptool usr/sbin/bluetoothd] ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 Date: Wed Feb 11 12:40:32 2015 DuplicateSignature: package:bluez:4.101-0ubuntu13 [modified: lib/udev/hid2hci usr/bin/ciptool usr/bin/hcitool usr/bin/l2ping usr/bin/l2test usr/bin/rctest usr/bin/rfcomm usr/bin/sdptool usr/sbin/bluetoothd]:paketet är i ett väldigt dåligt inkonsistent läge; du bör ominstallera det innan du försöker ta bort det. ErrorMessage: paketet är i ett väldigt dåligt inkonsistent läge; du bör ominstallera det innan du försöker ta bort det. InstallationDate: Installed on 2014-10-30 (104 days ago) InstallationMedia: Ubuntu-Kylin 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.1) InterestingModules: bnep bluetooth MachineType: Packard Bell ixtreme M5120 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic root=UUID=2bdb6c19-a5b0-4249-bdbc-4521237350cf ro quiet splash SourcePackage: bluez Title: package bluez 4.101-0ubuntu13 [modified: lib/udev/hid2hci usr/bin/ciptool usr/bin/hcitool usr/bin/l2ping usr/bin/l2test usr/bin/rctest usr/bin/rfcomm usr/bin/sdptool usr/sbin/bluetoothd] failed to install/upgrade: paketet är i ett väldigt dåligt inkonsistent läge; du bör ominstallera det innan du försöker ta bort det. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/05/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P01-A4 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: RS740 dmi.board.vendor: Packard Bell dmi.chassis.type: 3 dmi.chassis.vendor: Packard Bell dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP01-A4:bd03/05/2010:svnPackardBell:pnixtremeM5120:pvr:rvnPackardBell:rnRS740:rvr:cvnPackardBell:ct3:cvr: dmi.product.name: ixtreme M5120 dmi.sys.vendor: Packard Bell hciconfig: mtime.conffile..etc.bluetooth.main.conf: 2014-11-24T14:45:25.460596 mtime.conffile..etc.dbus.1.system.d.bluetooth.conf: 2014-11-24T14:45:09.868596 rfkill: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1421140/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1421117] Re: Ubuntu 15.04 VM doesn't boot after switching permanently to systemd
Pretty much the entire log is from the initramfs, the root fs'
/sbin/init indeed doesnt' seem to get called.
Can you please check ls -l /sbin/init in your VM? It should be a symlink
to /lib/systemd/systemd.
Also, could you boot with "break=bottom", and check ls -l
/root/sbin/init ? Does that exist, or was it removed/modified in some
funky way?
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
** Summary changed:
- Ubuntu 15.04 VM doesn't boot after switching permanently to systemd
+ fails to boot with "Attempted to kill init"
** Tags added: systemd-boot
--
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/1421117
Title:
fails to boot with "Attempted to kill init"
Status in systemd package in Ubuntu:
Incomplete
Bug description:
My Ubuntu 15.04 VM (running under VMware) doesn't boot anymore after
permanently switching to systemd.
I've switched to systemd with "apt install systemd-sysv --purge" (it only
purged the upstart package) and with the default "Ubuntu" entry the boot fails
after about 2.5 sec with a kernel panic ("Attempted to kill init"). But it
works when edit the grub entry (in the grub shell) and add
"init=/lib/systemd/systemd".
Attached is the serial output (with "debug" but no "init=" parameter).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1421117/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1419623] Re: systemd unmounts mounted filesystems when lxcfs is installed
** Tags added: systemd-boot -- 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/1419623 Title: systemd unmounts mounted filesystems when lxcfs is installed Status in lxcfs package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: In Progress Bug description: This seems to have been triggered by the glib update on ubuntu-desktop ppa. No partitions from fstab (apart from root of course) are getting mounted at boot. This is just a little problematic when /home is on a different partition! ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 218-7ubuntu1 [modified: lib/systemd/system/ifup@.service] ProcVersionSignature: Ubuntu 3.18.0-12.13-generic 3.18.4 Uname: Linux 3.18.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Feb 9 17:30:12 2015 InstallationDate: Installed on 2012-09-23 (869 days ago) InstallationMedia: Ubuntu GNOME Remix 12.10 "Quantal Quetzal" - Alpha amd64(20120922) MachineType: Gigabyte Technology Co., Ltd. P67A-UD3R-B3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-12-generic root=UUID=71eeb904-068b-41c2-9d34-59365ca4c3ad ro quiet splash init=/lib/systemd/systemd systemd.log_level=debug SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/21/2012 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F9 dmi.board.name: P67A-UD3R-B3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF9:bd03/21/2012:svnGigabyteTechnologyCo.,Ltd.:pnP67A-UD3R-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP67A-UD3R-B3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P67A-UD3R-B3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxcfs/+bug/1419623/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1417773] Re: Unity8 completely frozen (unable to unlock, receive calls, etc)
Fun. Looks like some kind of deadlock in Mir's GlibMainLoop with Mir's framedropping logic ** Also affects: mir (Ubuntu) Importance: Undecided Status: New -- 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/1417773 Title: Unity8 completely frozen (unable to unlock, receive calls, etc) Status in the base for Ubuntu mobile products: New Status in Mir: Triaged Status in mir package in Ubuntu: New Status in unity8 package in Ubuntu RTM: New Bug description: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 224 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed last update: 2015-01-29 18:53:09 version version: 224 version ubuntu: 20150129 version device: 20150129-c75dcfb version custom: 20150129-528-26-182 Was driving around with my car, and noticed once I got back home that my clock was stuck in a previous time (~20min before getting home), and after trying to use the phone I noticed unity8 was completely stuck, but the underling OS was still running fine. The worst here is that we're unable to notify the user about calls, as the interface is completely stuck. Another bad thing is that this could as well happen when the user is sleeping or something, without an easy way to know until he tries to use the phone. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1417773/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 583994] Re: Consider replacing ntpdate calls by 'ntpd -g'
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-meta (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/583994 Title: Consider replacing ntpdate calls by 'ntpd -g' Status in NTP: New Status in ntp package in Ubuntu: Triaged Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: Binary package hint: ntp Given that 'ntpdate' is being obsoleted upstream [1], we should replace 'ntpdate' usage by: * ntpd -qg (if we really want to set the time and exit), or * ntpd-g (if we want to keep ntpd running) the '-q' option will set the clock once, and exit; the 'g' allows for large corrections to the clock, like what is done by 'ntpdate'. [1] http://www.eecis.udel.edu/~mills/ntp/html/ntpdate.html To manage notifications about this bug go to: https://bugs.launchpad.net/ntp/+bug/583994/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 178370] Re: [hardy] ubuntu-minimal depends on ntpdate
*** This bug is a duplicate of bug 583994 *** https://bugs.launchpad.net/bugs/583994 ** This bug is no longer a duplicate of bug 61619 please replace dependency on ntpdate in ubuntu-minimal with ntp ** This bug has been marked a duplicate of bug 583994 Consider replacing ntpdate calls by 'ntpd -g' -- 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/178370 Title: [hardy] ubuntu-minimal depends on ntpdate Status in ubuntu-meta package in Ubuntu: New Bug description: Hello! I noticed that on Hardy the package ubuntu-minimal depends on ntpdate. First, this doesn't seem necessary according to the description of ubuntu-minimal: network time synchronization is a nice feature, but not really needed. Package ntpdate claims (in its description) that "If the full NTP daemon from the package "ntp" is installed, then ntpdate is not necessary." Which leads us to the second part of the problem: because of the above-mentioned dependency, ntpdate can't be uninstalled even if ntp is installed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/178370/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1421140] [NEW] package bluez 4.101-0ubuntu13 [modified: lib/udev/hid2hci usr/bin/ciptool usr/bin/hcitool usr/bin/l2ping usr/bin/l2test usr/bin/rctest usr/bin/rfcomm usr/bin/sdpto
Public bug reported: I Can't run updates anymore. But this fixed my issues why the computer didn't shut down correctly ha-ha. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: bluez 4.101-0ubuntu13 [modified: lib/udev/hid2hci usr/bin/ciptool usr/bin/hcitool usr/bin/l2ping usr/bin/l2test usr/bin/rctest usr/bin/rfcomm usr/bin/sdptool usr/sbin/bluetoothd] ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 Date: Wed Feb 11 12:40:32 2015 DuplicateSignature: package:bluez:4.101-0ubuntu13 [modified: lib/udev/hid2hci usr/bin/ciptool usr/bin/hcitool usr/bin/l2ping usr/bin/l2test usr/bin/rctest usr/bin/rfcomm usr/bin/sdptool usr/sbin/bluetoothd]:paketet är i ett väldigt dåligt inkonsistent läge; du bör ominstallera det innan du försöker ta bort det. ErrorMessage: paketet är i ett väldigt dåligt inkonsistent läge; du bör ominstallera det innan du försöker ta bort det. InstallationDate: Installed on 2014-10-30 (104 days ago) InstallationMedia: Ubuntu-Kylin 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.1) InterestingModules: bnep bluetooth MachineType: Packard Bell ixtreme M5120 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic root=UUID=2bdb6c19-a5b0-4249-bdbc-4521237350cf ro quiet splash SourcePackage: bluez Title: package bluez 4.101-0ubuntu13 [modified: lib/udev/hid2hci usr/bin/ciptool usr/bin/hcitool usr/bin/l2ping usr/bin/l2test usr/bin/rctest usr/bin/rfcomm usr/bin/sdptool usr/sbin/bluetoothd] failed to install/upgrade: paketet är i ett väldigt dåligt inkonsistent läge; du bör ominstallera det innan du försöker ta bort det. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/05/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P01-A4 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: RS740 dmi.board.vendor: Packard Bell dmi.chassis.type: 3 dmi.chassis.vendor: Packard Bell dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP01-A4:bd03/05/2010:svnPackardBell:pnixtremeM5120:pvr:rvnPackardBell:rnRS740:rvr:cvnPackardBell:ct3:cvr: dmi.product.name: ixtreme M5120 dmi.sys.vendor: Packard Bell hciconfig: mtime.conffile..etc.bluetooth.main.conf: 2014-11-24T14:45:25.460596 mtime.conffile..etc.dbus.1.system.d.bluetooth.conf: 2014-11-24T14:45:09.868596 rfkill: ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package trusty -- 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/1421140 Title: package bluez 4.101-0ubuntu13 [modified: lib/udev/hid2hci usr/bin/ciptool usr/bin/hcitool usr/bin/l2ping usr/bin/l2test usr/bin/rctest usr/bin/rfcomm usr/bin/sdptool usr/sbin/bluetoothd] failed to install/upgrade: paketet är i ett väldigt dåligt inkonsistent läge; du bör ominstallera det innan du försöker ta bort det. Status in bluez package in Ubuntu: New Bug description: I Can't run updates anymore. But this fixed my issues why the computer didn't shut down correctly ha-ha. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: bluez 4.101-0ubuntu13 [modified: lib/udev/hid2hci usr/bin/ciptool usr/bin/hcitool usr/bin/l2ping usr/bin/l2test usr/bin/rctest usr/bin/rfcomm usr/bin/sdptool usr/sbin/bluetoothd] ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 Date: Wed Feb 11 12:40:32 2015 DuplicateSignature: package:bluez:4.101-0ubuntu13 [modified: lib/udev/hid2hci usr/bin/ciptool usr/bin/hcitool usr/bin/l2ping usr/bin/l2test usr/bin/rctest usr/bin/rfcomm usr/bin/sdptool usr/sbin/bluetoothd]:paketet är i ett väldigt dåligt inkonsistent läge; du bör ominstallera det innan du försöker ta bort det. ErrorMessage: paketet är i ett väldigt dåligt inkonsistent läge; du bör ominstallera det innan du försöker ta bort det. InstallationDate: Installed on 2014-10-30 (104 days ago) InstallationMedia: Ubuntu-Kylin 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.1) InterestingModules: bnep bluetooth MachineType: Packard Bell ixtreme M5120 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic root=UUID=2bdb6c19-a5b0-4249-bdbc-4521237350cf ro quiet splash SourcePackage: bluez Title: package bluez 4.101-0ubuntu13 [modified: lib/udev/hid2hci usr/bin/ciptool usr/bin/hcitool usr/bin/l2ping usr/bin/l2test usr/bin/rctest usr/bin/rfcomm usr/bin/sdptool usr/sbin/bluetoothd] failed to install/upgrade: paketet är i ett väldigt dåligt inkonsistent läge; du bör ominstallera det innan du försöker ta bort det. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/05/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P01-A4
[Touch-packages] [Bug 1417773] Re: Unity8 completely frozen (unable to unlock, receive calls, etc)
** Also affects: mir Importance: Undecided Status: New ** Changed in: mir Status: New => Triaged ** Changed in: mir Importance: Undecided => Critical ** Changed in: mir Milestone: None => 0.12.0 -- 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/1417773 Title: Unity8 completely frozen (unable to unlock, receive calls, etc) Status in the base for Ubuntu mobile products: New Status in Mir: Triaged Status in mir package in Ubuntu: New Status in unity8 package in Ubuntu RTM: New Bug description: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 224 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed last update: 2015-01-29 18:53:09 version version: 224 version ubuntu: 20150129 version device: 20150129-c75dcfb version custom: 20150129-528-26-182 Was driving around with my car, and noticed once I got back home that my clock was stuck in a previous time (~20min before getting home), and after trying to use the phone I noticed unity8 was completely stuck, but the underling OS was still running fine. The worst here is that we're unable to notify the user about calls, as the interface is completely stuck. Another bad thing is that this could as well happen when the user is sleeping or something, without an easy way to know until he tries to use the phone. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1417773/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 61619] Re: please replace dependency on ntpdate in ubuntu-minimal with ntp
*** This bug is a duplicate of bug 583994 *** https://bugs.launchpad.net/bugs/583994 copying comment 0 from bug 583994 here for reference and completeness Given that 'ntpdate' is being obsoleted upstream [1], we should replace 'ntpdate' usage by: * ntpd -qg (if we really want to set the time and exit), or * ntpd-g (if we want to keep ntpd running) the '-q' option will set the clock once, and exit; the 'g' allows for large corrections to the clock, like what is done by 'ntpdate'. [1] http://www.eecis.udel.edu/~mills/ntp/html/ntpdate.html ** This bug has been marked a duplicate of bug 583994 Consider replacing ntpdate calls by 'ntpd -g' -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/61619 Title: please replace dependency on ntpdate in ubuntu-minimal with ntp Status in ntp package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Triaged Bug description: Hi! I think we might want to choose ntp-simple in some situations instead of ntpdate. Could we have that as an alternative Dependency? Cheers, /C To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/61619/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 583994] Re: Consider replacing ntpdate calls by 'ntpd -g'
this is not a bug in ntp (unless one were to advocate to replace the ntpdate command with a wrapper calling ntp which I believe no one is doing). Closing the ntp task. ** Changed in: ntp (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/583994 Title: Consider replacing ntpdate calls by 'ntpd -g' Status in NTP: New Status in ntp package in Ubuntu: Invalid Status in ubuntu-meta package in Ubuntu: Triaged Bug description: Binary package hint: ntp Given that 'ntpdate' is being obsoleted upstream [1], we should replace 'ntpdate' usage by: * ntpd -qg (if we really want to set the time and exit), or * ntpd-g (if we want to keep ntpd running) the '-q' option will set the clock once, and exit; the 'g' allows for large corrections to the clock, like what is done by 'ntpdate'. [1] http://www.eecis.udel.edu/~mills/ntp/html/ntpdate.html To manage notifications about this bug go to: https://bugs.launchpad.net/ntp/+bug/583994/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 61619] Re: please replace dependency on ntpdate in ubuntu-minimal with ntp
*** This bug is a duplicate of bug 583994 *** https://bugs.launchpad.net/bugs/583994 ntpdate has been deprecated upstream for a long time as previously pointed out several times. The NTP code has seen numerous security vulnerabilities and we have to assume that ntpdate is not receiving the same scrutiny anymore when compared to ntpd. This is no longer a wishlist change only. Ignoring the bitrot and neglect of this core package is getting more and more risky which really makes no sense when an alternative is readily available. Setting milestone for vivid, hoping that it is not too late, yet. ** Summary changed: - ntpdate in -minimal should have an alternative + please replace dependency on ntpdate in ubuntu-minimal with ntp ** Changed in: ubuntu-meta (Ubuntu) Importance: Wishlist => Medium ** Changed in: ubuntu-meta (Ubuntu) Milestone: None => ubuntu-15.02 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/61619 Title: please replace dependency on ntpdate in ubuntu-minimal with ntp Status in ntp package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Triaged Bug description: Hi! I think we might want to choose ntp-simple in some situations instead of ntpdate. Could we have that as an alternative Dependency? Cheers, /C To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/61619/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 777879] Re: removing ntpdate removes ubuntu-minimal
*** This bug is a duplicate of bug 583994 *** https://bugs.launchpad.net/bugs/583994 ** This bug is no longer a duplicate of bug 61619 please replace dependency on ntpdate in ubuntu-minimal with ntp ** This bug has been marked a duplicate of bug 583994 Consider replacing ntpdate calls by 'ntpd -g' -- 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/777879 Title: removing ntpdate removes ubuntu-minimal Status in ubuntu-meta package in Ubuntu: New Bug description: Binary package hint: synaptic Ubuntu 11.4. Synaptic, preparing to remove ntpdate, tells that it will remove Ubuntu-minimal too. This really doesn't seems smart to do (;-)) Its not possible to remove the check-mark for/un-mark Ubuntu-minimal. (The reason, I want to remove ntpdate, is, that it says, under ntp, that ntpdate is not necessary.) ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: synaptic 0.75.1ubuntu2 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic i686 Architecture: i386 Date: Thu May 5 16:01:14 2011 ExecutablePath: /usr/sbin/synaptic ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) LANG=en_DK.UTF-8 LC_MESSAGES=en_US.UTF-8 SHELL=/bin/bash SourcePackage: synaptic UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/777879/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1419623] Re: systemd unmounts mounted filesystems when lxcfs is installed
** Changed in: lxcfs (Ubuntu) Status: In Progress => Fix Committed ** Changed in: systemd (Ubuntu) Importance: Critical => High ** Changed in: lxcfs (Ubuntu) Importance: High => Critical -- 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/1419623 Title: systemd unmounts mounted filesystems when lxcfs is installed Status in lxcfs package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: In Progress Bug description: This seems to have been triggered by the glib update on ubuntu-desktop ppa. No partitions from fstab (apart from root of course) are getting mounted at boot. This is just a little problematic when /home is on a different partition! ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 218-7ubuntu1 [modified: lib/systemd/system/ifup@.service] ProcVersionSignature: Ubuntu 3.18.0-12.13-generic 3.18.4 Uname: Linux 3.18.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Feb 9 17:30:12 2015 InstallationDate: Installed on 2012-09-23 (869 days ago) InstallationMedia: Ubuntu GNOME Remix 12.10 "Quantal Quetzal" - Alpha amd64(20120922) MachineType: Gigabyte Technology Co., Ltd. P67A-UD3R-B3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-12-generic root=UUID=71eeb904-068b-41c2-9d34-59365ca4c3ad ro quiet splash init=/lib/systemd/systemd systemd.log_level=debug SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/21/2012 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F9 dmi.board.name: P67A-UD3R-B3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF9:bd03/21/2012:svnGigabyteTechnologyCo.,Ltd.:pnP67A-UD3R-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP67A-UD3R-B3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P67A-UD3R-B3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxcfs/+bug/1419623/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 374464] Re: ntpdate cannot be uninstalled without uninstalling ubuntu-minimal
*** This bug is a duplicate of bug 583994 *** https://bugs.launchpad.net/bugs/583994 ** This bug is no longer a duplicate of bug 61619 please replace dependency on ntpdate in ubuntu-minimal with ntp ** This bug has been marked a duplicate of bug 583994 Consider replacing ntpdate calls by 'ntpd -g' -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/374464 Title: ntpdate cannot be uninstalled without uninstalling ubuntu-minimal Status in ntp package in Ubuntu: Fix Released Bug description: Binary package hint: ntpdate If you have ntp and ntpdate installted, it is recommended you uninstall ntpdate, however you cannot uninstall ntpdate without uninstalling ubuntu-minimal which is not recommended. ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 9.04 Package: ntpdate 1:4.2.4p4+dfsg-7ubuntu5 ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ntp Uname: Linux 2.6.28-11-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/374464/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1419623] Re: systemd unmounts mounted filesystems when lxcfs is installed
systemd fix sent upstream: http://lists.freedesktop.org/archives /systemd-devel/2015-February/028264.html -- 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/1419623 Title: systemd unmounts mounted filesystems when lxcfs is installed Status in lxcfs package in Ubuntu: In Progress Status in systemd package in Ubuntu: In Progress Bug description: This seems to have been triggered by the glib update on ubuntu-desktop ppa. No partitions from fstab (apart from root of course) are getting mounted at boot. This is just a little problematic when /home is on a different partition! ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 218-7ubuntu1 [modified: lib/systemd/system/ifup@.service] ProcVersionSignature: Ubuntu 3.18.0-12.13-generic 3.18.4 Uname: Linux 3.18.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Feb 9 17:30:12 2015 InstallationDate: Installed on 2012-09-23 (869 days ago) InstallationMedia: Ubuntu GNOME Remix 12.10 "Quantal Quetzal" - Alpha amd64(20120922) MachineType: Gigabyte Technology Co., Ltd. P67A-UD3R-B3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-12-generic root=UUID=71eeb904-068b-41c2-9d34-59365ca4c3ad ro quiet splash init=/lib/systemd/systemd systemd.log_level=debug SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/21/2012 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F9 dmi.board.name: P67A-UD3R-B3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF9:bd03/21/2012:svnGigabyteTechnologyCo.,Ltd.:pnP67A-UD3R-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP67A-UD3R-B3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P67A-UD3R-B3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxcfs/+bug/1419623/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1421118] Re: [20-2110nz, Realtek ALC280, Speaker, Internal] Playback problem : headphones ok, speaker ko
Fixed by installing daily alsa build from https://code.launchpad.net /~ubuntu-audio-dev/+archive/ubuntu/alsa-daily/+packages ** Changed in: alsa-driver (Ubuntu) Status: New => Fix Committed -- 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/1421118 Title: [20-2110nz, Realtek ALC280, Speaker, Internal] Playback problem : headphones ok, speaker ko Status in alsa-driver package in Ubuntu: Fix Committed Bug description: Speaker doesn't work at all under Ubuntu, but sound through headphones is working fine. The machine is an hp 20 all-in-one. The hardware is fine, as the speaker does work in the original Windows 8 that came with the computer. We played with alsamixer and tried to tweak /etc/modprobe.d/alsa-base.conf to no avail. We never managed to get a single sound through the internal speakers in Ubuntu. -- Hardware: hp 20 all-in-one O.S.: Ubuntu 14.04.1 LTS package: alsa-base 1.0.25+dfsg-0ubuntu4 expected: internal speakers to produce sound with "sound settings test", vlc or web browser happened: no sound through internal speakers ever in Ubuntu (but yes through headphones in Ubuntu and through internal speakers in Windows) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 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/controlC0: oriana 1848 F pulseaudio CurrentDesktop: Unity Date: Thu Feb 12 09:59:05 2015 InstallationDate: Installed on 2015-02-11 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_Type: Only some of outputs are working Title: [20-2110nz, Realtek ALC280, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/12/2014 dmi.bios.vendor: AMI dmi.bios.version: 80.13 dmi.board.asset.tag: 4CH4457MH7 dmi.board.name: 2B15 dmi.board.vendor: Hewlett-Packard dmi.board.version: 1.02A dmi.chassis.asset.tag: 4CH4457MH7 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvr80.13:bd06/12/2014:svnHewlett-Packard:pn20-2110nz:pvr:rvnHewlett-Packard:rn2B15:rvr1.02A:cvnHewlett-Packard:ct3:cvr: dmi.product.name: 20-2110nz dmi.sys.vendor: Hewlett-Packard mtime.conffile..etc.modprobe.d.alsa.base.conf: 2015-02-12T09:58:59.506131 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1421118/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1381820] Re: package procps 1:3.3.9-1ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: procps (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1381820 Title: package procps 1:3.3.9-1ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in procps package in Ubuntu: Confirmed Bug description: Faffing aboout trying to upgrade ancient version of ubuntu to current. Got errors about britty processing, google told me to reinstall procps. seems to have fixedf the main problem, dont know what else will materialise. ProblemType: Package DistroRelease: Ubuntu 14.10 Package: procps 1:3.3.9-1ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu6 Architecture: amd64 Date: Thu Oct 16 00:52:39 2014 DuplicateSignature: package:procps:1:3.3.9-1ubuntu5:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2014-05-29 (139 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) SourcePackage: procps Title: package procps 1:3.3.9-1ubuntu5 failed to install/upgrade: subprocess installed post-installation 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/procps/+bug/1381820/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1420473] Re: Boot time is slow when RTC not set as in the factory
This bug was fixed in the package initramfs-tools - 0.103ubuntu11 --- initramfs-tools (0.103ubuntu11) vivid; urgency=medium * scripts/local-premount/fixrtc: - Make it work with busybox (different date syntax) - Add support to retrieve the last mount time from the ubuntu touch system partition - Make it able to extract the filesystem created timestamp (useful when last mounted is older) LP: #1420473 -- Ricardo Salveti de AraujoThu, 12 Feb 2015 04:34:46 -0200 ** Changed in: initramfs-tools (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1420473 Title: Boot time is slow when RTC not set as in the factory Status in the base for Ubuntu mobile products: Confirmed Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools package in Ubuntu RTM: New Bug description: When the RTC is not set, the apparmor cache is rebuilt on first boot resulting in a very long boot time. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1420473/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1050836] Re: wrong identification package
** Changed in: apport (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1050836
Title:
wrong identification package
Status in apport package in Ubuntu:
Invalid
Bug description:
Lubuntu Quantal i386
Originaly reported Bug #1050808 , and the retracing sevice bot claim:
outdated debug symbol package for initscripts: package version
2.88dsf-13.10ubuntu13 dbgsym version 2.88dsf-13.10ubuntu11.1
Even with an updated system with fresh ddebs sources, there is no such dbgsym
package about initscripts.
Worst, if we try to report against initscripts, apport open a report about
sysvinit. If its true, its not evident at first glance for an average user.
That said, i'm still lost with bug #1050808, really cant find how to
get the required traces. And the nightmare continue with Bug #1050828
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: apport 2.5.1-0ubuntu7
Uname: Linux 3.6.0-030600rc5-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.5.1-0ubuntu7
Architecture: i386
CrashReports:
640:0:125:1965629:2012-09-14 11:15:10.765941000 +0200:2012-09-14
11:16:20.328749515 +0200:/var/crash/_usr_bin_grub-script-check.0.crash
600:113:1000:0:2012-09-14 11:16:41.753629674 +0200:2012-09-14
11:16:41.753629674 +0200:/var/crash/_usr_bin_grub-script-check.0.uploaded
644:0:1000:0:2012-09-14 11:16:19.308707491 +0200:2012-09-14
11:16:19.308707491 +0200:/var/crash/_usr_bin_grub-script-check.0.upload
Date: Fri Sep 14 11:23:23 2012
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1050836/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1319698] Update Released
The verification of the Stable Release Update for thumbnailer 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 thumbnailer in Ubuntu. https://bugs.launchpad.net/bugs/1319698 Title: Gallery app shows pictures abnormally if target directory or file name contained Chinese text . Status in Gallery App: Fix Released Status in OEM Priority Project: New Status in OEM Priority Project trusty series: New Status in Thumbnail generator for all kinds of files: Fix Released Status in thumbnailer package in Ubuntu: Fix Released Status in thumbnailer source package in Trusty: Fix Released Bug description: Steps: 1. Copy some pictures to ~/Pictures 2. Launch Gallery app by entering "gallery" in Dash 3. Observe what the Gallery shows. Actual results: There are some transparent frames in Gallery. Expected results: Gallery app should show pictures included in ~/Pictures directory in step 2. Platform: Lenovo S440s Note: Once Gallery's target directory or file name of the target directory contains Chinese text, the issue will be reproduced. Adverse, if Gallery's target directory or file name of the target directory in English, Gallery displays normally. To manage notifications about this bug go to: https://bugs.launchpad.net/gallery-app/+bug/1319698/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1319698] Re: Gallery app shows pictures abnormally if target directory or file name contained Chinese text .
This bug was fixed in the package thumbnailer - 1.1+14.04.20150205-0ubuntu1 --- thumbnailer (1.1+14.04.20150205-0ubuntu1) trusty; urgency=medium [ Jussi Pakkanen ] * SRU backport of patch to make file names with chinese characters work. (LP: #1319698) -- Ubuntu daily releaseThu, 05 Feb 2015 12:10:33 + ** Changed in: thumbnailer (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 thumbnailer in Ubuntu. https://bugs.launchpad.net/bugs/1319698 Title: Gallery app shows pictures abnormally if target directory or file name contained Chinese text . Status in Gallery App: Fix Released Status in OEM Priority Project: New Status in OEM Priority Project trusty series: New Status in Thumbnail generator for all kinds of files: Fix Released Status in thumbnailer package in Ubuntu: Fix Released Status in thumbnailer source package in Trusty: Fix Released Bug description: Steps: 1. Copy some pictures to ~/Pictures 2. Launch Gallery app by entering "gallery" in Dash 3. Observe what the Gallery shows. Actual results: There are some transparent frames in Gallery. Expected results: Gallery app should show pictures included in ~/Pictures directory in step 2. Platform: Lenovo S440s Note: Once Gallery's target directory or file name of the target directory contains Chinese text, the issue will be reproduced. Adverse, if Gallery's target directory or file name of the target directory in English, Gallery displays normally. To manage notifications about this bug go to: https://bugs.launchpad.net/gallery-app/+bug/1319698/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1053637] Re: Apport UI should inform what crashed before user hits "Show Details"
As per the title, that is fixed now ** Changed in: apport (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1053637 Title: Apport UI should inform what crashed before user hits "Show Details" Status in apport package in Ubuntu: Fix Released Bug description: $ lsb_release -a LSB Version: core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch Distributor ID: Ubuntu Description: Ubuntu quantal (development branch) Release: 12.10 Codename: quantal $ apt-cache policy apport-gtk apport-gtk: Installed: 2.5.2-0ubuntu4 Candidate: 2.5.2-0ubuntu4 Version table: *** 2.5.2-0ubuntu4 0 500 http://archive.ubuntu.com/ubuntu/ quantal/main amd64 Packages 100 /var/lib/dpkg/status Considering that the number of times apport-gtk window pops-up when testing Ubuntu Development Releases can be a little overwhelming, it would be nice to be immediately informed of what crashed when we first look at it. That way, testers would quickly be able to decide if it's worth reporting the specific problem or not. The way it is now, we must click the "Show Details" button and wait for the details to load to know what has crashed. If we have already reported the program shown in the Details at "ExecutablePath", it's generally useless to report it again, so hitting "Show Details" and waiting for details to be loaded was wasted time. Ideally, the string stored at "ExecutablePath" should be displayed in apport-gtk main window right below the "Sorry, Ubuntu has experienced something..." line. Maybe in smaller fonts to accommodate the full path. I believe this is a small UI change that would make testing a little less annoying and more productive. (I have originally posted a full description of this problem/request, with screenshots, at http://ubuntuforums.org/showthread.php?t=2060038). Regards, Effenberg ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: apport 2.5.2-0ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-14.19-generic 3.5.3 Uname: Linux 3.5.0-14-generic x86_64 NonfreeKernelModules: nvidia ApportLog: ApportVersion: 2.5.2-0ubuntu4 Architecture: amd64 CheckboxSubmission: 8113a48e879cfd851bf2b71a258d2aee CheckboxSystem: edda5d4f616ca792bf437989cb597002 Date: Thu Sep 20 17:12:52 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120324.1) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1053637/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1419623] Re: systemd unmounts mounted filesystems when lxcfs is installed
systemd uses libmount's mnt_table_parse_mtab() which in our packages seems to default to /etc/mtab instead of /proc/mounts. -- 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/1419623 Title: systemd unmounts mounted filesystems when lxcfs is installed Status in lxcfs package in Ubuntu: In Progress Status in systemd package in Ubuntu: In Progress Bug description: This seems to have been triggered by the glib update on ubuntu-desktop ppa. No partitions from fstab (apart from root of course) are getting mounted at boot. This is just a little problematic when /home is on a different partition! ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 218-7ubuntu1 [modified: lib/systemd/system/ifup@.service] ProcVersionSignature: Ubuntu 3.18.0-12.13-generic 3.18.4 Uname: Linux 3.18.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Feb 9 17:30:12 2015 InstallationDate: Installed on 2012-09-23 (869 days ago) InstallationMedia: Ubuntu GNOME Remix 12.10 "Quantal Quetzal" - Alpha amd64(20120922) MachineType: Gigabyte Technology Co., Ltd. P67A-UD3R-B3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-12-generic root=UUID=71eeb904-068b-41c2-9d34-59365ca4c3ad ro quiet splash init=/lib/systemd/systemd systemd.log_level=debug SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/21/2012 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F9 dmi.board.name: P67A-UD3R-B3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF9:bd03/21/2012:svnGigabyteTechnologyCo.,Ltd.:pnP67A-UD3R-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP67A-UD3R-B3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P67A-UD3R-B3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxcfs/+bug/1419623/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1421117] [NEW] Ubuntu 15.04 VM doesn't boot after switching permanently to systemd
Public bug reported:
My Ubuntu 15.04 VM (running under VMware) doesn't boot anymore after
permanently switching to systemd.
I've switched to systemd with "apt install systemd-sysv --purge" (it only
purged the upstart package) and with the default "Ubuntu" entry the boot fails
after about 2.5 sec with a kernel panic ("Attempted to kill init"). But it
works when edit the grub entry (in the grub shell) and add
"init=/lib/systemd/systemd".
Attached is the serial output (with "debug" but no "init=" parameter).
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "SerialOutput.txt"
https://bugs.launchpad.net/bugs/1421117/+attachment/4317802/+files/SerialOutput.txt
--
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/1421117
Title:
Ubuntu 15.04 VM doesn't boot after switching permanently to systemd
Status in systemd package in Ubuntu:
New
Bug description:
My Ubuntu 15.04 VM (running under VMware) doesn't boot anymore after
permanently switching to systemd.
I've switched to systemd with "apt install systemd-sysv --purge" (it only
purged the upstart package) and with the default "Ubuntu" entry the boot fails
after about 2.5 sec with a kernel panic ("Attempted to kill init"). But it
works when edit the grub entry (in the grub shell) and add
"init=/lib/systemd/systemd".
Attached is the serial output (with "debug" but no "init=" parameter).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1421117/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 832458] Re: ccsm crashed with KeyError in compizconfig.Plugin.ApplyStringExtensions (src/compizconfig.c:6780)(): '\xd0\t\x9b\n\x01'
** Changed in: compiz-compizconfig-python Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/832458 Title: ccsm crashed with KeyError in compizconfig.Plugin.ApplyStringExtensions (src/compizconfig.c:6780)(): '\xd0\t\x9b\n\x01' Status in Compiz Configuration Library - Python Bindings: Fix Released Status in Unity: Fix Released Status in compizconfig-python package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Bug description: ubuntu11.10 alpha 3 kernel 3.0.9 window border disappeared suddenly and when i try to rest it from ccsm to back again the bug came out just like that TESTCASE: Open CCSM It wont crash ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: compizconfig-settings-manager 0.9.5.92-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-9.14-generic 3.0.3 Uname: Linux 3.0.0-9-generic i686 NonfreeKernelModules: wl Architecture: i386 Date: Wed Aug 24 04:25:08 2011 ExecutablePath: /usr/bin/ccsm InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) InterpreterPath: /usr/bin/python2.7 PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/bin/ccsm PythonArgs: ['/usr/bin/ccsm'] SourcePackage: compizconfig-settings-manager Title: ccsm crashed with KeyError in compizconfig.Plugin.ApplyStringExtensions (src/compizconfig.c:6780)(): '\xd0\t\x9b\n\x01' UpgradeStatus: Upgraded to oneiric on 2011-08-19 (4 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/compiz-compizconfig-python/+bug/832458/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1421118] [NEW] [20-2110nz, Realtek ALC280, Speaker, Internal] Playback problem : headphones ok, speaker ko
Public bug reported: Speaker doesn't work at all under Ubuntu, but sound through headphones is working fine. The machine is an hp 20 all-in-one. The hardware is fine, as the speaker does work in the original Windows 8 that came with the computer. We played with alsamixer and tried to tweak /etc/modprobe.d/alsa-base.conf to no avail. We never managed to get a single sound through the internal speakers in Ubuntu. -- Hardware: hp 20 all-in-one O.S.:Ubuntu 14.04.1 LTS package: alsa-base 1.0.25+dfsg-0ubuntu4 expected: internal speakers to produce sound with "sound settings test", vlc or web browser happened: no sound through internal speakers ever in Ubuntu (but yes through headphones in Ubuntu and through internal speakers in Windows) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 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/controlC0: oriana 1848 F pulseaudio CurrentDesktop: Unity Date: Thu Feb 12 09:59:05 2015 InstallationDate: Installed on 2015-02-11 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_Type: Only some of outputs are working Title: [20-2110nz, Realtek ALC280, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/12/2014 dmi.bios.vendor: AMI dmi.bios.version: 80.13 dmi.board.asset.tag: 4CH4457MH7 dmi.board.name: 2B15 dmi.board.vendor: Hewlett-Packard dmi.board.version: 1.02A dmi.chassis.asset.tag: 4CH4457MH7 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvr80.13:bd06/12/2014:svnHewlett-Packard:pn20-2110nz:pvr:rvnHewlett-Packard:rn2B15:rvr1.02A:cvnHewlett-Packard:ct3:cvr: dmi.product.name: 20-2110nz dmi.sys.vendor: Hewlett-Packard mtime.conffile..etc.modprobe.d.alsa.base.conf: 2015-02-12T09:58:59.506131 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1421118 Title: [20-2110nz, Realtek ALC280, Speaker, Internal] Playback problem : headphones ok, speaker ko Status in alsa-driver package in Ubuntu: New Bug description: Speaker doesn't work at all under Ubuntu, but sound through headphones is working fine. The machine is an hp 20 all-in-one. The hardware is fine, as the speaker does work in the original Windows 8 that came with the computer. We played with alsamixer and tried to tweak /etc/modprobe.d/alsa-base.conf to no avail. We never managed to get a single sound through the internal speakers in Ubuntu. -- Hardware: hp 20 all-in-one O.S.: Ubuntu 14.04.1 LTS package: alsa-base 1.0.25+dfsg-0ubuntu4 expected: internal speakers to produce sound with "sound settings test", vlc or web browser happened: no sound through internal speakers ever in Ubuntu (but yes through headphones in Ubuntu and through internal speakers in Windows) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 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/controlC0: oriana 1848 F pulseaudio CurrentDesktop: Unity Date: Thu Feb 12 09:59:05 2015 InstallationDate: Installed on 2015-02-11 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_Type: Only some of outputs are working Title: [20-2110nz, Realtek ALC280, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/12/2014 dmi.bios.vendor: AMI dmi.bios.version: 80.13 dmi.board.asset.tag: 4CH4457MH7 dmi.board.name: 2B15 dmi.board.vendor: Hewlett-Packard dmi.board.version: 1.02A dmi.chassis.asset.tag: 4CH4457MH7 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvr80.13:bd06/12/2014:svnHewlett-Packard:pn20-2110nz:pvr:rvnHewlett-Packard:rn2B15:rvr1.02A:cvnHewlett-Packard:ct3:cvr: dmi.product.name: 20-2110nz dmi
[Touch-packages] [Bug 1085806] Re: apport-cli : cant choose the E option without it being killed
** Changed in: apport (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1085806 Title: apport-cli : cant choose the E option without it being killed Status in apport package in Ubuntu: Invalid Bug description: From RR i386, apport 2.6.3-0ubuntu2 , logged as gnome-classic Actual issues: - trying to use ubuntu-bug fails to open the browser to file the report - apport-cli : also fails because it kill the process when it should apply the option choice oem@oem-desktop:~$ sudo apport-cli /var/crash/_usr_bin_nautilus.1000.crash [sudo] password for oem: *** Envoyer un rapport d'anomalie aux développeurs ? Une fois que le rapport d'anomalie aura été envoyé, veuillez compléter le formulaire ouvert automatiquement dans votre navigateur Web. Que voulez-vous faire ? Les choix possibles sont : E: Envoyer le rapport (7.3 MB) E: Examiner en local V: Voir le rapport C: Conserver le fichier du rapport pour l'envoyer ultérieurement ou le copier quelque part I: Annuler et ignorer les futurs plantages de cette version du programme A: Annuler eFaites un choix (E/E/V/C/I/A) : oem@oem-desktop:~$ That is, when i choose E to send the report, the process is killed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1085806/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1421110] Re: sssd missconfigured in apparamor profile
One more apparmor config to add:
capability sys_admin,
** Tags added: sssd
** Tags added: apparmod
** Also affects: apparmor (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1421110
Title:
sssd missconfigured in apparamor profile
Status in apparmor package in Ubuntu:
New
Status in sssd package in Ubuntu:
New
Bug description:
After last update (11/2/2015) in my Ubuntu Server 14.04, i have my
syslog filled with repetition of apparmor messages (see below), adding
following lines in /etc/apparmor.d/usr.sbin.sssd help for some of the
messages (I investigate for last ones).
@{PROC}/[0-9]*/net/psched r,
/etc/libnl-3/classid r,
/usr/lib/x86_64-linux-gnu/samba/ldb/* m,
Feb 12 08:44:58 neobingo kernel: [172114.878569] type=1400
audit(1423727098.271:7774537): apparmor="STATUS" operation="profile_replace"
profile="unconfined" name="/usr/sbin/sssd" pid=31752 comm="apparmor_parser"
Feb 12 08:44:58 neobingo kernel: [172114.920422] type=1400
audit(1423727098.315:7774538): apparmor="ALLOWED" operation="open"
profile="/usr/sbin/sssd" name="/proc/31753/net/psched" pid=31753 comm="sssd"
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
Feb 12 08:44:58 neobingo kernel: [172114.920925] type=1400
audit(1423727098.315:7774539): apparmor="ALLOWED" operation="open"
profile="/usr/sbin/sssd" name="/etc/libnl-3/classid" pid=31753 comm="sssd"
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
Feb 12 08:44:58 neobingo kernel: [172114.921370] type=1400
audit(1423727098.315:7774540): apparmor="ALLOWED" operation="capable"
profile="/usr/sbin/sssd" pid=31753 comm="sssd" capability=21
capname="sys_admin"
Feb 12 08:44:58 neobingo kernel: [172114.932424] type=1400
audit(1423727098.327:7774541): apparmor="ALLOWED" operation="file_mmap"
profile="/usr/sbin/sssd" name="/usr/lib/x86_64-linux-gnu/samba/ldb/acl.so"
pid=31753 comm="sssd" requested_mask="m" denied_mask=0
Feb 12 08:44:58 neobingo kernel: [172114.944467] type=1400
audit(1423727098.339:7774542): apparmor="ALLOWED" operation="file_mmap"
profile="/usr/sbin/sssd" name="/usr/lib/x86_64-linux-gnu/samba/ldb/aclread.so"
pid=31753 comm="sssd" requested_mask="m" denied_m0
Feb 12 08:44:58 neobingo kernel: [172114.945151] type=1400
audit(1423727098.339:7774543): apparmor="ALLOWED" operation="file_mmap"
profile="/usr/sbin/sssd" name="/usr/lib/x86_64-linux-gnu/samba/ldb/anr.so"
pid=31753 comm="sssd" requested_mask="m" denied_mask=0
Feb 12 08:44:58 neobingo kernel: [172114.945550] type=1400
audit(1423727098.339:7774544): apparmor="ALLOWED" operation="file_mmap"
profile="/usr/sbin/sssd"
name="/usr/lib/x86_64-linux-gnu/samba/ldb/descriptor.so" pid=31753 comm="sssd"
requested_mask="m" denie0
Feb 12 08:44:58 neobingo kernel: [172114.946220] type=1400
audit(1423727098.339:7774545): apparmor="ALLOWED" operation="file_mmap"
profile="/usr/sbin/sssd" name="/usr/lib/x86_64-linux-gnu/samba/ldb/dirsync.so"
pid=31753 comm="sssd" requested_mask="m" denied_m0
Feb 12 08:44:58 neobingo kernel: [172114.946978] type=1400
audit(1423727098.339:7774546): apparmor="ALLOWED" operation="file_mmap"
profile="/usr/sbin/sssd"
name="/usr/lib/x86_64-linux-gnu/samba/ldb/extended_dn_in.so" pid=31753
comm="sssd" requested_mask="m" d0
Feb 12 08:44:59 neobingo kernel: [172115.667342] init: sssd main process
(31753) terminated with status 4
Feb 12 08:44:59 neobingo kernel: [172115.667360] init: sssd main process
ended, respawning
Feb 12 08:45:00 neobingo kernel: [172116.761986] init: sssd main process
(31761) terminated with status 4
Feb 12 08:45:00 neobingo kernel: [172116.762004] init: sssd main process
ended, respawning
Feb 12 08:45:01 neobingo kernel: [172117.807237] init: sssd main process
(31769) terminated with status 4
Feb 12 08:45:01 neobingo kernel: [172117.807256] init: sssd main process
ended, respawning
Feb 12 08:45:02 neobingo kernel: [172118.932187] init: sssd main process
(31777) terminated with status 4
Feb 12 08:45:02 neobingo kernel: [172118.932210] init: sssd main process
ended, respawning
Feb 12 08:45:03 neobingo kernel: [172119.994233] init: sssd main process
(31785) terminated with status 4
Feb 12 08:45:03 neobingo kernel: [172119.994246] init: sssd main process
ended, respawning
Feb 12 08:45:03 neobingo kernel: [172120.213741] audit_printk_skb: 630
callbacks suppressed
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1421110/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1419623] Re: systemd unmounts partitions from fstab
I finally understand what's going on. This started a few weeks ago when we got lxcfs. What happens: - lxcfs' upstart job and systemd unit have this gem: sed -i "/^lxcfs \/var\/lib\/lxcfs fuse.lxcfs/d" /etc/mtab This will turn /etc/mtab into a file if it was a symlink to /proc/mounts. But these days we actually want it to be a symlink, as /etc/mtab as a static file is just a braindead and broken concept. - When systemd starts up, it parses existing mounts (via /etc/mtab) and creates mounts for them. This will include all the old mounts from the previous boot due to the previous issue. That's what triggers all these "dead -> mounted" transitions for all mounts right at the beginning of boot. But as the backing devices of them aren't discovered/there yet, but a mount unit is always bound to its underlying device unit, systemd cleans them up, i. e. stops them. This is usually meant for cleaning stale mounts from unplugged devices; it also makes sense here as these mounts indeed are not mounted at the moment. - Later on, the fstab generated mounts are actually being executed. But this races with the async mount cleanup handler from above, so depending on the particular machine, installed services, and current wind speed it may happen at a harmless (before the fstab mounts) or at a bad time (after the fstab mounts). - Even later, our debian-fixup.service transitions /etc/mtab from a file to a symlink. This is supposed to be an one-time migration, but lxcfs always reverts that during shutdown. ** Also affects: lxcfs (Ubuntu) Importance: Undecided Status: New ** Changed in: lxcfs (Ubuntu) Importance: Undecided => High ** Changed in: lxcfs (Ubuntu) Status: New => Triaged ** Changed in: lxcfs (Ubuntu) Assignee: (unassigned) => Martin Pitt (pitti) ** Changed in: systemd (Ubuntu) Status: Confirmed => In Progress ** Changed in: lxcfs (Ubuntu) Status: Triaged => In Progress ** Summary changed: - systemd unmounts partitions from fstab + systemd unmounts partitions from fstab when lxcfs is installed ** Summary changed: - systemd unmounts partitions from fstab when lxcfs is installed + systemd unmounts mounted filesystems when lxcfs is installed -- 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/1419623 Title: systemd unmounts mounted filesystems when lxcfs is installed Status in lxcfs package in Ubuntu: In Progress Status in systemd package in Ubuntu: In Progress Bug description: This seems to have been triggered by the glib update on ubuntu-desktop ppa. No partitions from fstab (apart from root of course) are getting mounted at boot. This is just a little problematic when /home is on a different partition! ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 218-7ubuntu1 [modified: lib/systemd/system/ifup@.service] ProcVersionSignature: Ubuntu 3.18.0-12.13-generic 3.18.4 Uname: Linux 3.18.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Feb 9 17:30:12 2015 InstallationDate: Installed on 2012-09-23 (869 days ago) InstallationMedia: Ubuntu GNOME Remix 12.10 "Quantal Quetzal" - Alpha amd64(20120922) MachineType: Gigabyte Technology Co., Ltd. P67A-UD3R-B3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-12-generic root=UUID=71eeb904-068b-41c2-9d34-59365ca4c3ad ro quiet splash init=/lib/systemd/systemd systemd.log_level=debug SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/21/2012 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F9 dmi.board.name: P67A-UD3R-B3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF9:bd03/21/2012:svnGigabyteTechnologyCo.,Ltd.:pnP67A-UD3R-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP67A-UD3R-B3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P67A-UD3R-B3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxcfs/+bug/1419623/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
