[Touch-packages] [Bug 802942] Re: printing PDFs (and other complex documents) from GTK applications fails
There's a cups bug report which was closed unresolved: https://www.cups.org/str.php?L3950+P-1+S0+C0+I0+E0+Qfirefox -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/802942 Title: printing PDFs (and other complex documents) from GTK applications fails Status in cups package in Ubuntu: Confirmed Bug description: Hello, I'm discovering a bug when printing complex PDFs or other complex documents from GTK applications. Printing complex PDFs from evince, or sometimes even printing comples webpages from firefox result in one error page being printed instead of the document content: +-+ | ERROR NAME;| | undefined| | COMMAND; | | Q| | OPERAND STACK; | +-+ My printer is a Brother HL 5270DN. It doesn't matter whether the printer is connected via USB or as network printer. In both cases the described bug does happen. The PPD I use is "Brother HL-5270DN BR- Script3", similar to the one at http://www.openprinting.org/download/PPD/Brother/BR5270_2_GPL.ppd I discovered this bug in up-to-date Debian unstable for several years already. Now I switched one of my laptops to Ubuntu Natty (fresh installation), and unfortunately discovered the same bug there as well. I'm pretty sure that this bug is related to bug #419143, and not really in CUPS, but rather in some library (poppler or cairo) used by GTK applications. The same PDFs that produce the described error in evince, print fine in okular. I attach an example PDF that doesn't print in evince, but prints fine in okular. It's sufficient to (try to) print page 1 of the document. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: cups 1.4.6-5ubuntu1.2 ProcVersionSignature: Ubuntu 2.6.39-0.5~20110427-generic 2.6.39-rc5 Uname: Linux 2.6.39-0-generic x86_64 Architecture: amd64 CupsErrorLog: Date: Tue Jun 28 13:13:29 2011 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110426) Lpstat: device for Brother-HL-5270DN: lpd://192.168.1.75/PASSTHRU MachineType: LENOVO 4180W1H Papersize: a4 PpdFiles: Brother-HL-5270DN: Brother HL-5270DN BR-Script3 ProcEnviron: LANGUAGE=de:en LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-2.6.39-0-generic root=/dev/mapper/vgsys-root ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/13/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 83ET56WW (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 4180W1H dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr83ET56WW(1.26):bd05/13/2011:svnLENOVO:pn4180W1H:pvrThinkPadT420:rvnLENOVO:rn4180W1H:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4180W1H dmi.product.version: ThinkPad T420 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/802942/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1424059] Re: libosmesa6 conflicts with libglapi-mesa-lts-utopic
I enabled trusty-proposed and gave the uploaded mesa-lts-vivid
(10.5.9-2ubuntu1~trusty3) a try. I can confirm that the corresponding
vivid's libosmesa(-dev) packages are now included and that I am able to
install the dependencies needed to build f. e. vtk without any problems
(see answers #3 and #11). Great to see that this annoying bug is solved!
** 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 mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1424059
Title:
libosmesa6 conflicts with libglapi-mesa-lts-utopic
Status in mesa package in Ubuntu:
Invalid
Status in mesa-lts-utopic package in Ubuntu:
Confirmed
Status in mesa-lts-vivid package in Ubuntu:
Incomplete
Bug description:
[Description]
libosmesa6 10.1.3-0ubuntu0.3 amd64 can't be installed because it depends on
libglapi-mesa (= 10.1.3-0ubuntu0.3), but libglapi-mesa-lts-utopic
10.3.2-0ubuntu1~trusty2 amd64 is '10.3.2-0ubuntu1' not '10.1.3-0ubuntu0.3'.
[Test Case]
>sudo aptitude install libosmesa6
The following NEW packages will be installed:
libglapi-mesa{a} libosmesa6
0 packages upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 1,009 kB of archives. After unpacking 3,682 kB will be used.
The following packages have unmet dependencies:
xserver-xorg-lts-utopic : Conflicts: libglapi-mesa (>= 0~) but
10.1.3-0ubuntu0.3 is to be installed.
libglapi-mesa-lts-utopic : Conflicts: libglapi-mesa but 10.1.3-0ubuntu0.3 is
to be installed.
[Possible solution]
Include utopic's libosmesa(-dev) in the LTS enablement stack, so versions
match.
[Reverse dependencies]
libosmesa6-dev
desmume
crossover
wine recommends libosmesa6
...
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: libglapi-mesa-lts-utopic 10.3.2-0ubuntu1~trusty2
ProcVersionSignature: Ubuntu 3.16.0-31.41~14.04.1-generic 3.16.7-ckt5
Uname: Linux 3.16.0-31-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.7
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Feb 20 15:45:52 2015
Dependencies:
gcc-4.9-base 4.9.1-0ubuntu1
libc6 2.19-0ubuntu6.5
libgcc1 1:4.9.1-0ubuntu1
multiarch-support 2.19-0ubuntu6.5
InstallationDate: Installed on 2015-02-08 (12 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64
(20150203.2)
SourcePackage: mesa-lts-utopic
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1424059/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1432171] Re: [udev] Shows "starting version 219" boot message even with "quiet"
I ran into this bug after a successfully logged in, could be a few hours or days latter without restarting, but suddenly session stop and I can see the black screen with "starting version 219" after that login screen appears again and I can start a new session but opened programs in the previous session still are running and I need to reboot to do a clean close of the applications left open in the former session. I'm using Ubuntu Gnome 15.04 updated to the last software update message. Is there a way to solve this?. As additional info I could said that I boot from disk drive, without a proper UEFI boot because does not work(grub error) when I install it. At the beginning I need to select the drive boot but after a while I load without that step, maybe I select it as default but I don't remember. -- 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/1432171 Title: [udev] Shows "starting version 219" boot message even with "quiet" Status in systemd package in Ubuntu: Fix Released Bug description: Everytime the system is booted up I get a "Starting version 219" which it seems is the version number for systemd. udev version: 219-4ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1432171/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1495180] [NEW] package account-plugin-google (not installed) failed to install/upgrade: tentative de remplacement de « /usr/share/accounts/services/google-im.service », qui appar
Public bug reported: Error while installing the metapackage ubuntu-gnome-desktop. Similar problem was encountered while installing unity8-desktop and apt-get was lost into cyclic dependencies that couldn't be satisfied. ProblemType: Package DistroRelease: Ubuntu 15.10 Package: account-plugin-google (not installed) ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.18.1-0ubuntu1 Architecture: i386 Date: Sat Sep 12 10:10:12 2015 DuplicateSignature: package:account-plugin-google:(not installed):tentative de remplacement de « /usr/share/accounts/services/google-im.service », qui appartient aussi au paquet kde-config-telepathy-accounts 4:15.08.0-0ubuntu1 ErrorMessage: tentative de remplacement de « /usr/share/accounts/services/google-im.service », qui appartient aussi au paquet kde-config-telepathy-accounts 4:15.08.0-0ubuntu1 InstallationDate: Installed on 2015-08-31 (12 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha i386 (20150825.1) RelatedPackageVersions: dpkg 1.18.2ubuntu3 apt 1.0.9.10ubuntu6 SourcePackage: account-plugins Title: package account-plugin-google (not installed) failed to install/upgrade: tentative de remplacement de « /usr/share/accounts/services/google-im.service », qui appartient aussi au paquet kde-config-telepathy-accounts 4:15.08.0-0ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: account-plugins (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 wily -- 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/1495180 Title: package account-plugin-google (not installed) failed to install/upgrade: tentative de remplacement de « /usr/share/accounts/services/google-im.service », qui appartient aussi au paquet kde-config-telepathy-accounts 4:15.08.0-0ubuntu1 Status in account-plugins package in Ubuntu: New Bug description: Error while installing the metapackage ubuntu-gnome-desktop. Similar problem was encountered while installing unity8-desktop and apt-get was lost into cyclic dependencies that couldn't be satisfied. ProblemType: Package DistroRelease: Ubuntu 15.10 Package: account-plugin-google (not installed) ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.18.1-0ubuntu1 Architecture: i386 Date: Sat Sep 12 10:10:12 2015 DuplicateSignature: package:account-plugin-google:(not installed):tentative de remplacement de « /usr/share/accounts/services/google-im.service », qui appartient aussi au paquet kde-config-telepathy-accounts 4:15.08.0-0ubuntu1 ErrorMessage: tentative de remplacement de « /usr/share/accounts/services/google-im.service », qui appartient aussi au paquet kde-config-telepathy-accounts 4:15.08.0-0ubuntu1 InstallationDate: Installed on 2015-08-31 (12 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha i386 (20150825.1) RelatedPackageVersions: dpkg 1.18.2ubuntu3 apt 1.0.9.10ubuntu6 SourcePackage: account-plugins Title: package account-plugin-google (not installed) failed to install/upgrade: tentative de remplacement de « /usr/share/accounts/services/google-im.service », qui appartient aussi au paquet kde-config-telepathy-accounts 4:15.08.0-0ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1495180/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1495116] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1495116/+attachment/4462935/+files/IwConfig.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/1495116 Title: booting with amd64 kernel and completely i386 userland is unstable during the system upstart Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in upstart package in Ubuntu: New Bug description: I wanted to run my 14.10 (Utopic) i386 system with the amd64 kernel, so I added that architecture and apt-get-installed the amd64 linux- image and linux-image-extra (I learned this was possible thanks to the advice at http://askubuntu.com/a/635774/19753 ). However, the system upstart procedure more often fails than not: it fails by rebooting the computer. (Only around 1 time of 4 is successful.) A limited system start is (probably, always) successful: either with init=/bin/bash parameter to the kernel, or choosing the recovery boot option. (However, if I "resume" from the recovery menu, or run "exec init" in bash, then the upstart procedure is similarly unstable: it usually fails/crashes and reboots.) I checked my suspection that the video driver (nouveau) and X might be involved, but that turned out not true: the upstart procedure is similarly unstable with "nomodesetting" kernel parameter and without, booting into runlevel 3 or the default one. Perhaps, I'd like to debug the upstart procedure step-by-step to detect which step makes the system crash and reboot, but I don't know how. As concerns the timing, the moment the reboot happens can be different: it can happen rather early (when I see the message about activating the swap) or much later. If the system upstart procedure has completed successfully, then it works in a quite stable manner and doesn't crash/reboot. So, there is something bad specifically during the system upstart procedure. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: upstart 1.13.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14 Uname: Linux 3.16.0-44-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.5 Architecture: i386 CurrentDesktop: Unity Date: Sat Sep 12 18:36:28 2015 InstallationDate: Installed on 2014-06-04 (464 days ago) InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 (20140204) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash SourcePackage: upstart UpgradeStatus: Upgraded to utopic on 2015-09-11 (0 days ago) UpstartBugCategory: System UpstartRunningSessionVersion: upstart 1.13.2 UpstartRunningSystemVersion: init (upstart 1.13.2) modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Отказано в доступе: '/etc/at.deny'] modified.conffile..etc.cron.daily.upstart: [modified] modified.conffile..etc.cups.cups.browsed.conf: [modified] modified.conffile..etc.default.apport: [modified] modified.conffile..etc.default.cups: [modified] modified.conffile..etc.init.d.binfmt.support: [modified] mtime.conffile..etc.X11.Xsession.d.99upstart: 2014-09-30T12:21:08 mtime.conffile..etc.cron.daily.upstart: 2014-09-30T12:27:13 mtime.conffile..etc.cups.cups.browsed.conf: 2015-09-06T09:29:16.410097 mtime.conffile..etc.default.apport: 2014-06-05T12:49:10.316398 mtime.conffile..etc.default.cups: 2015-09-06T09:20:49.891585 mtime.conffile..etc.init.d.binfmt.support: 2014-09-30T12:21:08 mtime.conffile..etc.upstart.xsessions: 2014-09-30T12:21:08 --- ApportVersion: 2.14.7-0ubuntu8.5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marsmorgana 1972 F pulseaudio CRDA: country RU: DFS-UNSET (2402 - 2482 @ 40), (N/A, 20) (5735 - 5835 @ 20), (N/A, 30) CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=9267c811-3a01-4484-b968-c08582280d81 InstallationDate: Installed on 2014-06-04 (464 days ago) InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 (20140204) MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510 Package: upstart 1.13.2-0ubuntu2 PackageArchitecture: i386 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14 RelatedPackageVersions: linux-restricted-modules-3.16.0-44-generic N/A linux-backports-modules-3.16.0-44-generic N/A linux-firmware 1.138.1 Tags: utopic utopic third-party-packages Uname: Linux 3.16.0-44-generic x86_64
[Touch-packages] [Bug 1495116] Re: booting with amd64 kernel and completely i386 userland is unstable during the system upstart
I was able to boot with the amd64 kernel from Vivid and upstart (but I guess that the successes and failures are just random), and will now collect the new information (for 15.04 (Vivid) system). ** Description changed: I wanted to run my 14.10 (Utopic) i386 system with the amd64 kernel, so I added that architecture and apt-get-installed the amd64 linux-image and linux-image-extra (I learned this was possible thanks to the advice at http://askubuntu.com/a/635774/19753 ). However, the system upstart procedure more often fails than not: it fails by rebooting the computer. (Only around 1 time of 4 is successful.) A limited system start is (probably, always) successful: either with init=/bin/bash parameter to the kernel, or choosing the recovery boot option. (However, if I "resume" from the recovery menu, or run "exec init" in bash, then the upstart procedure is similarly unstable: it usually fails/crashes and reboots.) I checked my suspection that the video driver (nouveau) and X might be involved, but that turned out not true: the upstart procedure is similarly unstable with "nomodesetting" kernel parameter and without, booting into runlevel 3 or the default one. Perhaps, I'd like to debug the upstart procedure step-by-step to detect which step makes the system crash and reboot, but I don't know how. As concerns the timing, the moment the reboot happens can be different: it can happen rather early (when I see the message about activating the swap) or much later. If the system upstart procedure has completed successfully, then it works in a quite stable manner and doesn't crash/reboot. So, there is something bad specifically during the system upstart procedure. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: upstart 1.13.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14 Uname: Linux 3.16.0-44-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.5 Architecture: i386 CurrentDesktop: Unity Date: Sat Sep 12 18:36:28 2015 InstallationDate: Installed on 2014-06-04 (464 days ago) InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 (20140204) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash SourcePackage: upstart UpgradeStatus: Upgraded to utopic on 2015-09-11 (0 days ago) UpstartBugCategory: System UpstartRunningSessionVersion: upstart 1.13.2 UpstartRunningSystemVersion: init (upstart 1.13.2) modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Отказано в доступе: '/etc/at.deny'] modified.conffile..etc.cron.daily.upstart: [modified] modified.conffile..etc.cups.cups.browsed.conf: [modified] modified.conffile..etc.default.apport: [modified] modified.conffile..etc.default.cups: [modified] modified.conffile..etc.init.d.binfmt.support: [modified] mtime.conffile..etc.X11.Xsession.d.99upstart: 2014-09-30T12:21:08 mtime.conffile..etc.cron.daily.upstart: 2014-09-30T12:27:13 mtime.conffile..etc.cups.cups.browsed.conf: 2015-09-06T09:29:16.410097 mtime.conffile..etc.default.apport: 2014-06-05T12:49:10.316398 mtime.conffile..etc.default.cups: 2015-09-06T09:20:49.891585 mtime.conffile..etc.init.d.binfmt.support: 2014-09-30T12:21:08 mtime.conffile..etc.upstart.xsessions: 2014-09-30T12:21:08 --- ApportVersion: 2.14.7-0ubuntu8.5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marsmorgana 1972 F pulseaudio CRDA: country RU: DFS-UNSET (2402 - 2482 @ 40), (N/A, 20) (5735 - 5835 @ 20), (N/A, 30) CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=9267c811-3a01-4484-b968-c08582280d81 InstallationDate: Installed on 2014-06-04 (464 days ago) InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 (20140204) MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510 Package: upstart 1.13.2-0ubuntu2 PackageArchitecture: i386 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14 RelatedPackageVersions: linux-restricted-modules-3.16.0-44-generic N/A linux-backports-modules-3.16.0-44-generic N/A linux-firmware 1.138.1 Tags: utopic utopic third-party-packages Uname: Linux 3.16.0-44-generic x86_64 UpgradeStatus: Upgraded to utopic on 2015-09-11 (0 days ago) UpstartBugCategory: System UpstartRunningSessionVersion: upstart 1.13.2 UpstartRunningSystemVersion: init (upstart 1.13.2) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/26/2008 dmi.bios.vendor: Phoenix Technologies Ltd.
[Touch-packages] [Bug 1495116] Re: booting with amd64 kernel and completely i386 userland is unstable during the system upstart
The problem is also present after an upgrade to 15.04 (Vivid) with: linux-image-3.19.0-28-generic:amd64 linux-image-extra-3.19.0-28-generic:amd64 systemd-219-7ubuntu6 (i386) ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags removed: third-party-packages ** Tags added: 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/1495116 Title: booting with amd64 kernel and completely i386 userland is unstable during the system upstart Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in upstart package in Ubuntu: New Bug description: I wanted to run my 14.10 (Utopic) i386 system with the amd64 kernel, so I added that architecture and apt-get-installed the amd64 linux- image and linux-image-extra (I learned this was possible thanks to the advice at http://askubuntu.com/a/635774/19753 ). However, the system upstart procedure more often fails than not: it fails by rebooting the computer. (Only around 1 time of 4 is successful.) A limited system start is (probably, always) successful: either with init=/bin/bash parameter to the kernel, or choosing the recovery boot option. (However, if I "resume" from the recovery menu, or run "exec init" in bash, then the upstart procedure is similarly unstable: it usually fails/crashes and reboots.) I checked my suspection that the video driver (nouveau) and X might be involved, but that turned out not true: the upstart procedure is similarly unstable with "nomodesetting" kernel parameter and without, booting into runlevel 3 or the default one. Perhaps, I'd like to debug the upstart procedure step-by-step to detect which step makes the system crash and reboot, but I don't know how. As concerns the timing, the moment the reboot happens can be different: it can happen rather early (when I see the message about activating the swap) or much later. If the system upstart procedure has completed successfully, then it works in a quite stable manner and doesn't crash/reboot. So, there is something bad specifically during the system upstart procedure. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: upstart 1.13.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14 Uname: Linux 3.16.0-44-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.5 Architecture: i386 CurrentDesktop: Unity Date: Sat Sep 12 18:36:28 2015 InstallationDate: Installed on 2014-06-04 (464 days ago) InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 (20140204) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash SourcePackage: upstart UpgradeStatus: Upgraded to utopic on 2015-09-11 (0 days ago) UpstartBugCategory: System UpstartRunningSessionVersion: upstart 1.13.2 UpstartRunningSystemVersion: init (upstart 1.13.2) modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Отказано в доступе: '/etc/at.deny'] modified.conffile..etc.cron.daily.upstart: [modified] modified.conffile..etc.cups.cups.browsed.conf: [modified] modified.conffile..etc.default.apport: [modified] modified.conffile..etc.default.cups: [modified] modified.conffile..etc.init.d.binfmt.support: [modified] mtime.conffile..etc.X11.Xsession.d.99upstart: 2014-09-30T12:21:08 mtime.conffile..etc.cron.daily.upstart: 2014-09-30T12:27:13 mtime.conffile..etc.cups.cups.browsed.conf: 2015-09-06T09:29:16.410097 mtime.conffile..etc.default.apport: 2014-06-05T12:49:10.316398 mtime.conffile..etc.default.cups: 2015-09-06T09:20:49.891585 mtime.conffile..etc.init.d.binfmt.support: 2014-09-30T12:21:08 mtime.conffile..etc.upstart.xsessions: 2014-09-30T12:21:08 --- ApportVersion: 2.14.7-0ubuntu8.5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marsmorgana 1972 F pulseaudio CRDA: country RU: DFS-UNSET (2402 - 2482 @ 40), (N/A, 20) (5735 - 5835 @ 20), (N/A, 30) CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=9267c811-3a01-4484-b968-c08582280d81 InstallationDate: Installed on 2014-06-04 (464 days ago) InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 (20140204) MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510 Package: upstart 1.13.2-0ubuntu2 PackageArchitecture: i386 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14 RelatedPackageVersions: linux-restricted-modules-3.16.0-44-generic N/A
[Touch-packages] [Bug 1495116] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1495116/+attachment/4462934/+files/Dependencies.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/1495116 Title: booting with amd64 kernel and completely i386 userland is unstable during the system upstart Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in upstart package in Ubuntu: New Bug description: I wanted to run my 14.10 (Utopic) i386 system with the amd64 kernel, so I added that architecture and apt-get-installed the amd64 linux- image and linux-image-extra (I learned this was possible thanks to the advice at http://askubuntu.com/a/635774/19753 ). However, the system upstart procedure more often fails than not: it fails by rebooting the computer. (Only around 1 time of 4 is successful.) A limited system start is (probably, always) successful: either with init=/bin/bash parameter to the kernel, or choosing the recovery boot option. (However, if I "resume" from the recovery menu, or run "exec init" in bash, then the upstart procedure is similarly unstable: it usually fails/crashes and reboots.) I checked my suspection that the video driver (nouveau) and X might be involved, but that turned out not true: the upstart procedure is similarly unstable with "nomodesetting" kernel parameter and without, booting into runlevel 3 or the default one. Perhaps, I'd like to debug the upstart procedure step-by-step to detect which step makes the system crash and reboot, but I don't know how. As concerns the timing, the moment the reboot happens can be different: it can happen rather early (when I see the message about activating the swap) or much later. If the system upstart procedure has completed successfully, then it works in a quite stable manner and doesn't crash/reboot. So, there is something bad specifically during the system upstart procedure. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: upstart 1.13.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14 Uname: Linux 3.16.0-44-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.5 Architecture: i386 CurrentDesktop: Unity Date: Sat Sep 12 18:36:28 2015 InstallationDate: Installed on 2014-06-04 (464 days ago) InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 (20140204) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash SourcePackage: upstart UpgradeStatus: Upgraded to utopic on 2015-09-11 (0 days ago) UpstartBugCategory: System UpstartRunningSessionVersion: upstart 1.13.2 UpstartRunningSystemVersion: init (upstart 1.13.2) modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Отказано в доступе: '/etc/at.deny'] modified.conffile..etc.cron.daily.upstart: [modified] modified.conffile..etc.cups.cups.browsed.conf: [modified] modified.conffile..etc.default.apport: [modified] modified.conffile..etc.default.cups: [modified] modified.conffile..etc.init.d.binfmt.support: [modified] mtime.conffile..etc.X11.Xsession.d.99upstart: 2014-09-30T12:21:08 mtime.conffile..etc.cron.daily.upstart: 2014-09-30T12:27:13 mtime.conffile..etc.cups.cups.browsed.conf: 2015-09-06T09:29:16.410097 mtime.conffile..etc.default.apport: 2014-06-05T12:49:10.316398 mtime.conffile..etc.default.cups: 2015-09-06T09:20:49.891585 mtime.conffile..etc.init.d.binfmt.support: 2014-09-30T12:21:08 mtime.conffile..etc.upstart.xsessions: 2014-09-30T12:21:08 --- ApportVersion: 2.14.7-0ubuntu8.5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marsmorgana 1972 F pulseaudio CRDA: country RU: DFS-UNSET (2402 - 2482 @ 40), (N/A, 20) (5735 - 5835 @ 20), (N/A, 30) CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=9267c811-3a01-4484-b968-c08582280d81 InstallationDate: Installed on 2014-06-04 (464 days ago) InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 (20140204) MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510 Package: upstart 1.13.2-0ubuntu2 PackageArchitecture: i386 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14 RelatedPackageVersions: linux-restricted-modules-3.16.0-44-generic N/A linux-backports-modules-3.16.0-44-generic N/A linux-firmware 1.138.1 Tags: utopic utopic third-party-packages Uname: Linux 3.16.0-44-generic x86_64
[Touch-packages] [Bug 1495116] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1495116/+attachment/4462931/+files/AlsaInfo.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/1495116 Title: booting with amd64 kernel and completely i386 userland is unstable during the system upstart Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in upstart package in Ubuntu: New Bug description: I wanted to run my 14.10 (Utopic) i386 system with the amd64 kernel, so I added that architecture and apt-get-installed the amd64 linux- image and linux-image-extra (I learned this was possible thanks to the advice at http://askubuntu.com/a/635774/19753 ). However, the system upstart procedure more often fails than not: it fails by rebooting the computer. (Only around 1 time of 4 is successful.) A limited system start is (probably, always) successful: either with init=/bin/bash parameter to the kernel, or choosing the recovery boot option. (However, if I "resume" from the recovery menu, or run "exec init" in bash, then the upstart procedure is similarly unstable: it usually fails/crashes and reboots.) I checked my suspection that the video driver (nouveau) and X might be involved, but that turned out not true: the upstart procedure is similarly unstable with "nomodesetting" kernel parameter and without, booting into runlevel 3 or the default one. Perhaps, I'd like to debug the upstart procedure step-by-step to detect which step makes the system crash and reboot, but I don't know how. As concerns the timing, the moment the reboot happens can be different: it can happen rather early (when I see the message about activating the swap) or much later. If the system upstart procedure has completed successfully, then it works in a quite stable manner and doesn't crash/reboot. So, there is something bad specifically during the system upstart procedure. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: upstart 1.13.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14 Uname: Linux 3.16.0-44-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.5 Architecture: i386 CurrentDesktop: Unity Date: Sat Sep 12 18:36:28 2015 InstallationDate: Installed on 2014-06-04 (464 days ago) InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 (20140204) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash SourcePackage: upstart UpgradeStatus: Upgraded to utopic on 2015-09-11 (0 days ago) UpstartBugCategory: System UpstartRunningSessionVersion: upstart 1.13.2 UpstartRunningSystemVersion: init (upstart 1.13.2) modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Отказано в доступе: '/etc/at.deny'] modified.conffile..etc.cron.daily.upstart: [modified] modified.conffile..etc.cups.cups.browsed.conf: [modified] modified.conffile..etc.default.apport: [modified] modified.conffile..etc.default.cups: [modified] modified.conffile..etc.init.d.binfmt.support: [modified] mtime.conffile..etc.X11.Xsession.d.99upstart: 2014-09-30T12:21:08 mtime.conffile..etc.cron.daily.upstart: 2014-09-30T12:27:13 mtime.conffile..etc.cups.cups.browsed.conf: 2015-09-06T09:29:16.410097 mtime.conffile..etc.default.apport: 2014-06-05T12:49:10.316398 mtime.conffile..etc.default.cups: 2015-09-06T09:20:49.891585 mtime.conffile..etc.init.d.binfmt.support: 2014-09-30T12:21:08 mtime.conffile..etc.upstart.xsessions: 2014-09-30T12:21:08 --- ApportVersion: 2.14.7-0ubuntu8.5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marsmorgana 1972 F pulseaudio CRDA: country RU: DFS-UNSET (2402 - 2482 @ 40), (N/A, 20) (5735 - 5835 @ 20), (N/A, 30) CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=9267c811-3a01-4484-b968-c08582280d81 InstallationDate: Installed on 2014-06-04 (464 days ago) InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 (20140204) MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510 Package: upstart 1.13.2-0ubuntu2 PackageArchitecture: i386 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14 RelatedPackageVersions: linux-restricted-modules-3.16.0-44-generic N/A linux-backports-modules-3.16.0-44-generic N/A linux-firmware 1.138.1 Tags: utopic utopic third-party-packages Uname: Linux 3.16.0-44-generic x86_64
[Touch-packages] [Bug 1495116] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1495116/+attachment/4462932/+files/CRDA.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/1495116 Title: booting with amd64 kernel and completely i386 userland is unstable during the system upstart Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in upstart package in Ubuntu: New Bug description: I wanted to run my 14.10 (Utopic) i386 system with the amd64 kernel, so I added that architecture and apt-get-installed the amd64 linux- image and linux-image-extra (I learned this was possible thanks to the advice at http://askubuntu.com/a/635774/19753 ). However, the system upstart procedure more often fails than not: it fails by rebooting the computer. (Only around 1 time of 4 is successful.) A limited system start is (probably, always) successful: either with init=/bin/bash parameter to the kernel, or choosing the recovery boot option. (However, if I "resume" from the recovery menu, or run "exec init" in bash, then the upstart procedure is similarly unstable: it usually fails/crashes and reboots.) I checked my suspection that the video driver (nouveau) and X might be involved, but that turned out not true: the upstart procedure is similarly unstable with "nomodesetting" kernel parameter and without, booting into runlevel 3 or the default one. Perhaps, I'd like to debug the upstart procedure step-by-step to detect which step makes the system crash and reboot, but I don't know how. As concerns the timing, the moment the reboot happens can be different: it can happen rather early (when I see the message about activating the swap) or much later. If the system upstart procedure has completed successfully, then it works in a quite stable manner and doesn't crash/reboot. So, there is something bad specifically during the system upstart procedure. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: upstart 1.13.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14 Uname: Linux 3.16.0-44-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.5 Architecture: i386 CurrentDesktop: Unity Date: Sat Sep 12 18:36:28 2015 InstallationDate: Installed on 2014-06-04 (464 days ago) InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 (20140204) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash SourcePackage: upstart UpgradeStatus: Upgraded to utopic on 2015-09-11 (0 days ago) UpstartBugCategory: System UpstartRunningSessionVersion: upstart 1.13.2 UpstartRunningSystemVersion: init (upstart 1.13.2) modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Отказано в доступе: '/etc/at.deny'] modified.conffile..etc.cron.daily.upstart: [modified] modified.conffile..etc.cups.cups.browsed.conf: [modified] modified.conffile..etc.default.apport: [modified] modified.conffile..etc.default.cups: [modified] modified.conffile..etc.init.d.binfmt.support: [modified] mtime.conffile..etc.X11.Xsession.d.99upstart: 2014-09-30T12:21:08 mtime.conffile..etc.cron.daily.upstart: 2014-09-30T12:27:13 mtime.conffile..etc.cups.cups.browsed.conf: 2015-09-06T09:29:16.410097 mtime.conffile..etc.default.apport: 2014-06-05T12:49:10.316398 mtime.conffile..etc.default.cups: 2015-09-06T09:20:49.891585 mtime.conffile..etc.init.d.binfmt.support: 2014-09-30T12:21:08 mtime.conffile..etc.upstart.xsessions: 2014-09-30T12:21:08 --- ApportVersion: 2.14.7-0ubuntu8.5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marsmorgana 1972 F pulseaudio CRDA: country RU: DFS-UNSET (2402 - 2482 @ 40), (N/A, 20) (5735 - 5835 @ 20), (N/A, 30) CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=9267c811-3a01-4484-b968-c08582280d81 InstallationDate: Installed on 2014-06-04 (464 days ago) InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 (20140204) MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510 Package: upstart 1.13.2-0ubuntu2 PackageArchitecture: i386 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14 RelatedPackageVersions: linux-restricted-modules-3.16.0-44-generic N/A linux-backports-modules-3.16.0-44-generic N/A linux-firmware 1.138.1 Tags: utopic utopic third-party-packages Uname: Linux 3.16.0-44-generic x86_64 UpgradeStatus:
[Touch-packages] [Bug 1495116] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1495116/+attachment/4462933/+files/CurrentDmesg.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/1495116 Title: booting with amd64 kernel and completely i386 userland is unstable during the system upstart Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in upstart package in Ubuntu: New Bug description: I wanted to run my 14.10 (Utopic) i386 system with the amd64 kernel, so I added that architecture and apt-get-installed the amd64 linux- image and linux-image-extra (I learned this was possible thanks to the advice at http://askubuntu.com/a/635774/19753 ). However, the system upstart procedure more often fails than not: it fails by rebooting the computer. (Only around 1 time of 4 is successful.) A limited system start is (probably, always) successful: either with init=/bin/bash parameter to the kernel, or choosing the recovery boot option. (However, if I "resume" from the recovery menu, or run "exec init" in bash, then the upstart procedure is similarly unstable: it usually fails/crashes and reboots.) I checked my suspection that the video driver (nouveau) and X might be involved, but that turned out not true: the upstart procedure is similarly unstable with "nomodesetting" kernel parameter and without, booting into runlevel 3 or the default one. Perhaps, I'd like to debug the upstart procedure step-by-step to detect which step makes the system crash and reboot, but I don't know how. As concerns the timing, the moment the reboot happens can be different: it can happen rather early (when I see the message about activating the swap) or much later. If the system upstart procedure has completed successfully, then it works in a quite stable manner and doesn't crash/reboot. So, there is something bad specifically during the system upstart procedure. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: upstart 1.13.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14 Uname: Linux 3.16.0-44-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.5 Architecture: i386 CurrentDesktop: Unity Date: Sat Sep 12 18:36:28 2015 InstallationDate: Installed on 2014-06-04 (464 days ago) InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 (20140204) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash SourcePackage: upstart UpgradeStatus: Upgraded to utopic on 2015-09-11 (0 days ago) UpstartBugCategory: System UpstartRunningSessionVersion: upstart 1.13.2 UpstartRunningSystemVersion: init (upstart 1.13.2) modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Отказано в доступе: '/etc/at.deny'] modified.conffile..etc.cron.daily.upstart: [modified] modified.conffile..etc.cups.cups.browsed.conf: [modified] modified.conffile..etc.default.apport: [modified] modified.conffile..etc.default.cups: [modified] modified.conffile..etc.init.d.binfmt.support: [modified] mtime.conffile..etc.X11.Xsession.d.99upstart: 2014-09-30T12:21:08 mtime.conffile..etc.cron.daily.upstart: 2014-09-30T12:27:13 mtime.conffile..etc.cups.cups.browsed.conf: 2015-09-06T09:29:16.410097 mtime.conffile..etc.default.apport: 2014-06-05T12:49:10.316398 mtime.conffile..etc.default.cups: 2015-09-06T09:20:49.891585 mtime.conffile..etc.init.d.binfmt.support: 2014-09-30T12:21:08 mtime.conffile..etc.upstart.xsessions: 2014-09-30T12:21:08 --- ApportVersion: 2.14.7-0ubuntu8.5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marsmorgana 1972 F pulseaudio CRDA: country RU: DFS-UNSET (2402 - 2482 @ 40), (N/A, 20) (5735 - 5835 @ 20), (N/A, 30) CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=9267c811-3a01-4484-b968-c08582280d81 InstallationDate: Installed on 2014-06-04 (464 days ago) InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 (20140204) MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510 Package: upstart 1.13.2-0ubuntu2 PackageArchitecture: i386 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14 RelatedPackageVersions: linux-restricted-modules-3.16.0-44-generic N/A linux-backports-modules-3.16.0-44-generic N/A linux-firmware 1.138.1 Tags: utopic utopic third-party-packages Uname: Linux 3.16.0-44-generic x86_64
[Touch-packages] [Bug 1495196] [NEW] Failed to connect to socket /com/ubuntu/upstart: Connection refused
Public bug reported: .xsession-errors has many entries like: upstart: upstart-event-bridge main process (1511) terminated with status 1 upstart: upstart-event-bridge respawning too fast, stopped The terminal output is : sudo status upstart-event-bridge [sudo] password for oem: status: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused ls -l /usr/share/upstart/sessions/upstart-event-bridge.conf -rw-r--r-- 1 root root 385 may 18 12:21 /usr/share/upstart/sessions/upstart-event-bridge.conf This issue has been reported many times by the past, and already fixed: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/901038/comments/14 https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1449765 Some workarounds also have been proposed, like: dpkg-divert --local --rename --add /sbin/initctl ln -s /bin/true /sbin/initctl But with the recent ubuntu realeases systemd is now doing more & more jobs previously done by upstart. So the solutions of the past might not be the best choice nowadays. And the http://upstart.ubuntu.com/cookbook/ seems outdated as it does not consider the systemd existence. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: upstart 1.13.2-0ubuntu14 ProcVersionSignature: Ubuntu 4.2.0-10.10-generic 4.2.0 Uname: Linux 4.2.0-10-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.18.1-0ubuntu1 Architecture: i386 CurrentDesktop: GNOME Date: Sun Sep 13 11:06:23 2015 ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.2.0-10-generic root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro intel_iommu=on SourcePackage: upstart UpgradeStatus: No upgrade log present (probably fresh install) UpstartBugCategory: System UpstartRunningSessionVersion: upstart 1.13.2 UpstartRunningSystemJobs: Error: command ['initctl', '--system', 'list'] failed with exit code 1: initctl: Name "com.ubuntu.Upstart" does not exist UpstartRunningSystemVersion: Error: command ['initctl', '--system', 'version'] failed with exit code 1: initctl: Name "com.ubuntu.Upstart" does not exist modified.conffile..etc.apparmor.d.usr.sbin.rsyslogd: [modified] modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Permission denied: '/etc/at.deny'] modified.conffile..etc.init.plymouth.upstart.bridge.conf: [modified] mtime.conffile..etc.apparmor.d.usr.sbin.rsyslogd: 2014-12-16T17:58:59.466381 mtime.conffile..etc.init.plymouth.upstart.bridge.conf: 2015-02-21T17:45:18.251803 ** Affects: upstart (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: apport-bug i386 wily ** Description changed: .xsession-errors has many entries like: upstart: upstart-event-bridge main process (1511) terminated with status 1 upstart: upstart-event-bridge respawning too fast, stopped The terminal output is : - sudo status upstart-event-bridge - [sudo] password for oem: + sudo status upstart-event-bridge + [sudo] password for oem: status: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused ls -l /usr/share/upstart/sessions/upstart-event-bridge.conf -rw-r--r-- 1 root root 385 may 18 12:21 /usr/share/upstart/sessions/upstart-event-bridge.conf - This issue has been reported many times by the past, and already fixed: - https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/901038/comments/14 + https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/901038/comments/14 + https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1449765 Some workarounds also have been proposed, like: dpkg-divert --local --rename --add /sbin/initctl ln -s /bin/true /sbin/initctl - - But with the recent ubuntu realeases systemd is now doing more & more jobs previously done by upstart. So the solutions of the past might not be the best choice nowaday. + But with the recent ubuntu realeases systemd is now doing more & more + jobs previously done by upstart. So the solutions of the past might not + be the best choice nowaday. And the http://upstart.ubuntu.com/cookbook/ seems outdated as it does not consider the systemd existence. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: upstart 1.13.2-0ubuntu14 ProcVersionSignature: Ubuntu 4.2.0-10.10-generic 4.2.0 Uname: Linux 4.2.0-10-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.18.1-0ubuntu1 Architecture: i386 CurrentDesktop: GNOME Date: Sun Sep 13 11:06:23 2015 ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.2.0-10-generic root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro intel_iommu=on SourcePackage: upstart UpgradeStatus: No upgrade log present (probably fresh install) UpstartBugCategory: System UpstartRunningSessionVersion: upstart 1.13.2 UpstartRunningSystemJobs: - Error: command ['initctl', '--system', 'list'] failed with exit code 1: initctl: Name "com.ubuntu.Upstart" does not exist + Error: command ['initctl', '--system', 'list'] failed with exit code 1: initctl: Name "com.ubuntu.Upstart" does not
[Touch-packages] [Bug 1457400] Re: reduce 90s session kill timeout if the session does not shutdown cleanly
How to change timeout value? In which config file I find this setting? -- 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/1457400 Title: reduce 90s session kill timeout if the session does not shutdown cleanly Status in systemd package in Ubuntu: Confirmed Bug description: I use Ubuntu 15.04 with Unity, I have a SSD drive also. Very recently onwards the ubuntu is taking long to shut down nearly 1:30 minutes. I checked the shutdown log messages and I get the follow message. A stop job is running for Session c2 of user * (25s/ 1min 30 s) It count downs till 1:30 minutes and then shutdown the machine. Why is it happening. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1457400/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 893210] Re: [Dell OptiPlex GX620 - AD1981b, playback] No sound at all
> so how can I get pactl list sinks to include: >analog-output-lfe-on-mono;output-amplifier-on: LFE on Separate Mono Output / >Amplifier (priority: 4010) >analog-output-lfe-on-mono;output-amplifier-off: LFE on Separate Mono Output / >No Amplifier (priority: 4000) do you mean the internal speaker is using mono out, you have to ask pulseaudio developer ? http://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/src/modules/alsa/mixer?id=9e4229cfe03d441a01a0f1bd02972936048ae85d -- 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/893210 Title: [Dell OptiPlex GX620 - AD1981b, playback] No sound at all Status in ALSA driver: Confirmed Status in alsa-driver package in Ubuntu: Incomplete Bug description: fresh install of ubuntu studio and updates but internal speakers do not play. dell optiplex gx620 love ya ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: alsa-base 1.0.24+dfsg-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6 Uname: Linux 3.0.0-13-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.23-0ubuntu4 Architecture: i386 Card0.Amixer.info: Card hw:0 'ICH7'/'Intel ICH7 with AD1981B at irq 23' Mixer name : 'Analog Devices AD1981B' Components : 'AC97a:41445374' Controls : 28 Simple ctrls : 20 Card1.Amixer.info: Card hw:1 'Device'/'C-Media Electronics Inc. USB Multimedia Audio Device at usb-:00:1d.7-4.1.4,' Mixer name : 'USB Mixer' Components : 'USB0d8c:0105' Controls : 13 Simple ctrls : 6 Date: Mon Nov 21 11:51:25 2011 InstallationMedia: Ubuntu-Studio 11.10 "Oneiric Ocelot" - Release i386 (20111011.1) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:ICH7 failed Symptom_Card: CM108 Audio Controller - USB Multimedia Audio Device Symptom_Type: No sound at all Title: [ICH4 - Intel ICH7, playback] No sound at all UpgradeStatus: Upgraded to oneiric on 2011-11-12 (8 days ago) dmi.bios.date: 11/30/2006 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0F8101 dmi.board.vendor: Dell Inc. dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0F8101:rvr:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex GX620 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/893210/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1495180] Re: package account-plugin-google (not installed) failed to install/upgrade: tentative de remplacement de « /usr/share/accounts/services/google-im.service », qui apparti
** Tags removed: need-duplicate-check -- 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/1495180 Title: package account-plugin-google (not installed) failed to install/upgrade: tentative de remplacement de « /usr/share/accounts/services/google-im.service », qui appartient aussi au paquet kde-config-telepathy-accounts 4:15.08.0-0ubuntu1 Status in account-plugins package in Ubuntu: New Bug description: Error while installing the metapackage ubuntu-gnome-desktop. Similar problem was encountered while installing unity8-desktop and apt-get was lost into cyclic dependencies that couldn't be satisfied. ProblemType: Package DistroRelease: Ubuntu 15.10 Package: account-plugin-google (not installed) ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.18.1-0ubuntu1 Architecture: i386 Date: Sat Sep 12 10:10:12 2015 DuplicateSignature: package:account-plugin-google:(not installed):tentative de remplacement de « /usr/share/accounts/services/google-im.service », qui appartient aussi au paquet kde-config-telepathy-accounts 4:15.08.0-0ubuntu1 ErrorMessage: tentative de remplacement de « /usr/share/accounts/services/google-im.service », qui appartient aussi au paquet kde-config-telepathy-accounts 4:15.08.0-0ubuntu1 InstallationDate: Installed on 2015-08-31 (12 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha i386 (20150825.1) RelatedPackageVersions: dpkg 1.18.2ubuntu3 apt 1.0.9.10ubuntu6 SourcePackage: account-plugins Title: package account-plugin-google (not installed) failed to install/upgrade: tentative de remplacement de « /usr/share/accounts/services/google-im.service », qui appartient aussi au paquet kde-config-telepathy-accounts 4:15.08.0-0ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1495180/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1311165] Re: timezone incorrectly modified when editing/creating google calendar event
I still have this issue with my google calendar. My ubuntu phone is updated to OTA 6 and my calendar app is on version 0.4.711 (3 sep 2015)... Is the fix not yet implemented? -- 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/1311165 Title: timezone incorrectly modified when editing/creating google calendar event Status in qtorganizer5-eds: Fix Released Status in Ubuntu Calendar App: Fix Released Status in Ubuntu UI Toolkit: Fix Released Status in qtorganizer5-eds package in Ubuntu: Confirmed Bug description: We are not preserving the time zone of a calendar event after editing it. - Create an event in Google Calendar (using browser calendar.google.com), at 12pm local time, call it "Test" - Ensure your timezone on device is set to your correct timezone (UTC -4 in my case) by accessing system-settings - Import Calendar from Google account (by setting up online account for Google) - Verify the "Test" event shows up correctly in Calendar app at 12pm - Now edit the event and change the description to "Test, 123" and save the event. - After the sync runs (wait one or two minutes), open your browser and reload your google calendar Expected result: - Event should be called "Test, 123" and still at 12pm local time Actual results: - Event is correctly updated to show "Test, 123" but time has shifted to 3pm local time We should not be modifying the timezone when editing the event To manage notifications about this bug go to: https://bugs.launchpad.net/qtorganizer5-eds/+bug/1311165/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1495116] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1495116/+attachment/4462940/+files/ProcInterrupts.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/1495116 Title: booting with amd64 kernel and completely i386 userland is unstable during the system upstart Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in upstart package in Ubuntu: New Bug description: I wanted to run my 14.10 (Utopic) i386 system with the amd64 kernel, so I added that architecture and apt-get-installed the amd64 linux- image and linux-image-extra (I learned this was possible thanks to the advice at http://askubuntu.com/a/635774/19753 ). However, the system upstart procedure more often fails than not: it fails by rebooting the computer. (Only around 1 time of 4 is successful.) A limited system start is (probably, always) successful: either with init=/bin/bash parameter to the kernel, or choosing the recovery boot option. (However, if I "resume" from the recovery menu, or run "exec init" in bash, then the upstart procedure is similarly unstable: it usually fails/crashes and reboots.) I checked my suspection that the video driver (nouveau) and X might be involved, but that turned out not true: the upstart procedure is similarly unstable with "nomodesetting" kernel parameter and without, booting into runlevel 3 or the default one. Perhaps, I'd like to debug the upstart procedure step-by-step to detect which step makes the system crash and reboot, but I don't know how. As concerns the timing, the moment the reboot happens can be different: it can happen rather early (when I see the message about activating the swap) or much later. If the system upstart procedure has completed successfully, then it works in a quite stable manner and doesn't crash/reboot. So, there is something bad specifically during the system upstart procedure. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: upstart 1.13.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14 Uname: Linux 3.16.0-44-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.5 Architecture: i386 CurrentDesktop: Unity Date: Sat Sep 12 18:36:28 2015 InstallationDate: Installed on 2014-06-04 (464 days ago) InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 (20140204) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash SourcePackage: upstart UpgradeStatus: Upgraded to utopic on 2015-09-11 (0 days ago) UpstartBugCategory: System UpstartRunningSessionVersion: upstart 1.13.2 UpstartRunningSystemVersion: init (upstart 1.13.2) modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Отказано в доступе: '/etc/at.deny'] modified.conffile..etc.cron.daily.upstart: [modified] modified.conffile..etc.cups.cups.browsed.conf: [modified] modified.conffile..etc.default.apport: [modified] modified.conffile..etc.default.cups: [modified] modified.conffile..etc.init.d.binfmt.support: [modified] mtime.conffile..etc.X11.Xsession.d.99upstart: 2014-09-30T12:21:08 mtime.conffile..etc.cron.daily.upstart: 2014-09-30T12:27:13 mtime.conffile..etc.cups.cups.browsed.conf: 2015-09-06T09:29:16.410097 mtime.conffile..etc.default.apport: 2014-06-05T12:49:10.316398 mtime.conffile..etc.default.cups: 2015-09-06T09:20:49.891585 mtime.conffile..etc.init.d.binfmt.support: 2014-09-30T12:21:08 mtime.conffile..etc.upstart.xsessions: 2014-09-30T12:21:08 --- ApportVersion: 2.14.7-0ubuntu8.5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marsmorgana 1972 F pulseaudio CRDA: country RU: DFS-UNSET (2402 - 2482 @ 40), (N/A, 20) (5735 - 5835 @ 20), (N/A, 30) CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=9267c811-3a01-4484-b968-c08582280d81 InstallationDate: Installed on 2014-06-04 (464 days ago) InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 (20140204) MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510 Package: upstart 1.13.2-0ubuntu2 PackageArchitecture: i386 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14 RelatedPackageVersions: linux-restricted-modules-3.16.0-44-generic N/A linux-backports-modules-3.16.0-44-generic N/A linux-firmware 1.138.1 Tags: utopic utopic third-party-packages Uname: Linux 3.16.0-44-generic
[Touch-packages] [Bug 1495116] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1495116/+attachment/4462939/+files/ProcEnviron.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/1495116 Title: booting with amd64 kernel and completely i386 userland is unstable during the system upstart Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in upstart package in Ubuntu: New Bug description: I wanted to run my 14.10 (Utopic) i386 system with the amd64 kernel, so I added that architecture and apt-get-installed the amd64 linux- image and linux-image-extra (I learned this was possible thanks to the advice at http://askubuntu.com/a/635774/19753 ). However, the system upstart procedure more often fails than not: it fails by rebooting the computer. (Only around 1 time of 4 is successful.) A limited system start is (probably, always) successful: either with init=/bin/bash parameter to the kernel, or choosing the recovery boot option. (However, if I "resume" from the recovery menu, or run "exec init" in bash, then the upstart procedure is similarly unstable: it usually fails/crashes and reboots.) I checked my suspection that the video driver (nouveau) and X might be involved, but that turned out not true: the upstart procedure is similarly unstable with "nomodesetting" kernel parameter and without, booting into runlevel 3 or the default one. Perhaps, I'd like to debug the upstart procedure step-by-step to detect which step makes the system crash and reboot, but I don't know how. As concerns the timing, the moment the reboot happens can be different: it can happen rather early (when I see the message about activating the swap) or much later. If the system upstart procedure has completed successfully, then it works in a quite stable manner and doesn't crash/reboot. So, there is something bad specifically during the system upstart procedure. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: upstart 1.13.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14 Uname: Linux 3.16.0-44-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.5 Architecture: i386 CurrentDesktop: Unity Date: Sat Sep 12 18:36:28 2015 InstallationDate: Installed on 2014-06-04 (464 days ago) InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 (20140204) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash SourcePackage: upstart UpgradeStatus: Upgraded to utopic on 2015-09-11 (0 days ago) UpstartBugCategory: System UpstartRunningSessionVersion: upstart 1.13.2 UpstartRunningSystemVersion: init (upstart 1.13.2) modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Отказано в доступе: '/etc/at.deny'] modified.conffile..etc.cron.daily.upstart: [modified] modified.conffile..etc.cups.cups.browsed.conf: [modified] modified.conffile..etc.default.apport: [modified] modified.conffile..etc.default.cups: [modified] modified.conffile..etc.init.d.binfmt.support: [modified] mtime.conffile..etc.X11.Xsession.d.99upstart: 2014-09-30T12:21:08 mtime.conffile..etc.cron.daily.upstart: 2014-09-30T12:27:13 mtime.conffile..etc.cups.cups.browsed.conf: 2015-09-06T09:29:16.410097 mtime.conffile..etc.default.apport: 2014-06-05T12:49:10.316398 mtime.conffile..etc.default.cups: 2015-09-06T09:20:49.891585 mtime.conffile..etc.init.d.binfmt.support: 2014-09-30T12:21:08 mtime.conffile..etc.upstart.xsessions: 2014-09-30T12:21:08 --- ApportVersion: 2.14.7-0ubuntu8.5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marsmorgana 1972 F pulseaudio CRDA: country RU: DFS-UNSET (2402 - 2482 @ 40), (N/A, 20) (5735 - 5835 @ 20), (N/A, 30) CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=9267c811-3a01-4484-b968-c08582280d81 InstallationDate: Installed on 2014-06-04 (464 days ago) InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 (20140204) MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510 Package: upstart 1.13.2-0ubuntu2 PackageArchitecture: i386 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14 RelatedPackageVersions: linux-restricted-modules-3.16.0-44-generic N/A linux-backports-modules-3.16.0-44-generic N/A linux-firmware 1.138.1 Tags: utopic utopic third-party-packages Uname: Linux 3.16.0-44-generic x86_64
[Touch-packages] [Bug 802942] Re: printing PDFs (and other complex documents) from GTK applications fails
Maybe related: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/369503 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/802942 Title: printing PDFs (and other complex documents) from GTK applications fails Status in cups package in Ubuntu: Confirmed Bug description: Hello, I'm discovering a bug when printing complex PDFs or other complex documents from GTK applications. Printing complex PDFs from evince, or sometimes even printing comples webpages from firefox result in one error page being printed instead of the document content: +-+ | ERROR NAME;| | undefined| | COMMAND; | | Q| | OPERAND STACK; | +-+ My printer is a Brother HL 5270DN. It doesn't matter whether the printer is connected via USB or as network printer. In both cases the described bug does happen. The PPD I use is "Brother HL-5270DN BR- Script3", similar to the one at http://www.openprinting.org/download/PPD/Brother/BR5270_2_GPL.ppd I discovered this bug in up-to-date Debian unstable for several years already. Now I switched one of my laptops to Ubuntu Natty (fresh installation), and unfortunately discovered the same bug there as well. I'm pretty sure that this bug is related to bug #419143, and not really in CUPS, but rather in some library (poppler or cairo) used by GTK applications. The same PDFs that produce the described error in evince, print fine in okular. I attach an example PDF that doesn't print in evince, but prints fine in okular. It's sufficient to (try to) print page 1 of the document. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: cups 1.4.6-5ubuntu1.2 ProcVersionSignature: Ubuntu 2.6.39-0.5~20110427-generic 2.6.39-rc5 Uname: Linux 2.6.39-0-generic x86_64 Architecture: amd64 CupsErrorLog: Date: Tue Jun 28 13:13:29 2011 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110426) Lpstat: device for Brother-HL-5270DN: lpd://192.168.1.75/PASSTHRU MachineType: LENOVO 4180W1H Papersize: a4 PpdFiles: Brother-HL-5270DN: Brother HL-5270DN BR-Script3 ProcEnviron: LANGUAGE=de:en LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-2.6.39-0-generic root=/dev/mapper/vgsys-root ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/13/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 83ET56WW (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 4180W1H dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr83ET56WW(1.26):bd05/13/2011:svnLENOVO:pn4180W1H:pvrThinkPadT420:rvnLENOVO:rn4180W1H:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4180W1H dmi.product.version: ThinkPad T420 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/802942/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1495116] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1495116/+attachment/4462938/+files/ProcCpuinfo.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/1495116 Title: booting with amd64 kernel and completely i386 userland is unstable during the system upstart Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in upstart package in Ubuntu: New Bug description: I wanted to run my 14.10 (Utopic) i386 system with the amd64 kernel, so I added that architecture and apt-get-installed the amd64 linux- image and linux-image-extra (I learned this was possible thanks to the advice at http://askubuntu.com/a/635774/19753 ). However, the system upstart procedure more often fails than not: it fails by rebooting the computer. (Only around 1 time of 4 is successful.) A limited system start is (probably, always) successful: either with init=/bin/bash parameter to the kernel, or choosing the recovery boot option. (However, if I "resume" from the recovery menu, or run "exec init" in bash, then the upstart procedure is similarly unstable: it usually fails/crashes and reboots.) I checked my suspection that the video driver (nouveau) and X might be involved, but that turned out not true: the upstart procedure is similarly unstable with "nomodesetting" kernel parameter and without, booting into runlevel 3 or the default one. Perhaps, I'd like to debug the upstart procedure step-by-step to detect which step makes the system crash and reboot, but I don't know how. As concerns the timing, the moment the reboot happens can be different: it can happen rather early (when I see the message about activating the swap) or much later. If the system upstart procedure has completed successfully, then it works in a quite stable manner and doesn't crash/reboot. So, there is something bad specifically during the system upstart procedure. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: upstart 1.13.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14 Uname: Linux 3.16.0-44-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.5 Architecture: i386 CurrentDesktop: Unity Date: Sat Sep 12 18:36:28 2015 InstallationDate: Installed on 2014-06-04 (464 days ago) InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 (20140204) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash SourcePackage: upstart UpgradeStatus: Upgraded to utopic on 2015-09-11 (0 days ago) UpstartBugCategory: System UpstartRunningSessionVersion: upstart 1.13.2 UpstartRunningSystemVersion: init (upstart 1.13.2) modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Отказано в доступе: '/etc/at.deny'] modified.conffile..etc.cron.daily.upstart: [modified] modified.conffile..etc.cups.cups.browsed.conf: [modified] modified.conffile..etc.default.apport: [modified] modified.conffile..etc.default.cups: [modified] modified.conffile..etc.init.d.binfmt.support: [modified] mtime.conffile..etc.X11.Xsession.d.99upstart: 2014-09-30T12:21:08 mtime.conffile..etc.cron.daily.upstart: 2014-09-30T12:27:13 mtime.conffile..etc.cups.cups.browsed.conf: 2015-09-06T09:29:16.410097 mtime.conffile..etc.default.apport: 2014-06-05T12:49:10.316398 mtime.conffile..etc.default.cups: 2015-09-06T09:20:49.891585 mtime.conffile..etc.init.d.binfmt.support: 2014-09-30T12:21:08 mtime.conffile..etc.upstart.xsessions: 2014-09-30T12:21:08 --- ApportVersion: 2.14.7-0ubuntu8.5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marsmorgana 1972 F pulseaudio CRDA: country RU: DFS-UNSET (2402 - 2482 @ 40), (N/A, 20) (5735 - 5835 @ 20), (N/A, 30) CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=9267c811-3a01-4484-b968-c08582280d81 InstallationDate: Installed on 2014-06-04 (464 days ago) InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 (20140204) MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510 Package: upstart 1.13.2-0ubuntu2 PackageArchitecture: i386 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14 RelatedPackageVersions: linux-restricted-modules-3.16.0-44-generic N/A linux-backports-modules-3.16.0-44-generic N/A linux-firmware 1.138.1 Tags: utopic utopic third-party-packages Uname: Linux 3.16.0-44-generic x86_64
[Touch-packages] [Bug 1495116] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1495116/+attachment/4462941/+files/ProcModules.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/1495116 Title: booting with amd64 kernel and completely i386 userland is unstable during the system upstart Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in upstart package in Ubuntu: New Bug description: I wanted to run my 14.10 (Utopic) i386 system with the amd64 kernel, so I added that architecture and apt-get-installed the amd64 linux- image and linux-image-extra (I learned this was possible thanks to the advice at http://askubuntu.com/a/635774/19753 ). However, the system upstart procedure more often fails than not: it fails by rebooting the computer. (Only around 1 time of 4 is successful.) A limited system start is (probably, always) successful: either with init=/bin/bash parameter to the kernel, or choosing the recovery boot option. (However, if I "resume" from the recovery menu, or run "exec init" in bash, then the upstart procedure is similarly unstable: it usually fails/crashes and reboots.) I checked my suspection that the video driver (nouveau) and X might be involved, but that turned out not true: the upstart procedure is similarly unstable with "nomodesetting" kernel parameter and without, booting into runlevel 3 or the default one. Perhaps, I'd like to debug the upstart procedure step-by-step to detect which step makes the system crash and reboot, but I don't know how. As concerns the timing, the moment the reboot happens can be different: it can happen rather early (when I see the message about activating the swap) or much later. If the system upstart procedure has completed successfully, then it works in a quite stable manner and doesn't crash/reboot. So, there is something bad specifically during the system upstart procedure. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: upstart 1.13.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14 Uname: Linux 3.16.0-44-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.5 Architecture: i386 CurrentDesktop: Unity Date: Sat Sep 12 18:36:28 2015 InstallationDate: Installed on 2014-06-04 (464 days ago) InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 (20140204) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash SourcePackage: upstart UpgradeStatus: Upgraded to utopic on 2015-09-11 (0 days ago) UpstartBugCategory: System UpstartRunningSessionVersion: upstart 1.13.2 UpstartRunningSystemVersion: init (upstart 1.13.2) modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Отказано в доступе: '/etc/at.deny'] modified.conffile..etc.cron.daily.upstart: [modified] modified.conffile..etc.cups.cups.browsed.conf: [modified] modified.conffile..etc.default.apport: [modified] modified.conffile..etc.default.cups: [modified] modified.conffile..etc.init.d.binfmt.support: [modified] mtime.conffile..etc.X11.Xsession.d.99upstart: 2014-09-30T12:21:08 mtime.conffile..etc.cron.daily.upstart: 2014-09-30T12:27:13 mtime.conffile..etc.cups.cups.browsed.conf: 2015-09-06T09:29:16.410097 mtime.conffile..etc.default.apport: 2014-06-05T12:49:10.316398 mtime.conffile..etc.default.cups: 2015-09-06T09:20:49.891585 mtime.conffile..etc.init.d.binfmt.support: 2014-09-30T12:21:08 mtime.conffile..etc.upstart.xsessions: 2014-09-30T12:21:08 --- ApportVersion: 2.14.7-0ubuntu8.5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marsmorgana 1972 F pulseaudio CRDA: country RU: DFS-UNSET (2402 - 2482 @ 40), (N/A, 20) (5735 - 5835 @ 20), (N/A, 30) CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=9267c811-3a01-4484-b968-c08582280d81 InstallationDate: Installed on 2014-06-04 (464 days ago) InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 (20140204) MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510 Package: upstart 1.13.2-0ubuntu2 PackageArchitecture: i386 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14 RelatedPackageVersions: linux-restricted-modules-3.16.0-44-generic N/A linux-backports-modules-3.16.0-44-generic N/A linux-firmware 1.138.1 Tags: utopic utopic third-party-packages Uname: Linux 3.16.0-44-generic x86_64
[Touch-packages] [Bug 1495116] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1495116/+attachment/4462951/+files/WifiSyslog.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/1495116 Title: booting with amd64 kernel and completely i386 userland is unstable during the system upstart Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in upstart package in Ubuntu: New Bug description: I wanted to run my 14.10 (Utopic) i386 system with the amd64 kernel, so I added that architecture and apt-get-installed the amd64 linux- image and linux-image-extra (I learned this was possible thanks to the advice at http://askubuntu.com/a/635774/19753 ). However, the system upstart procedure more often fails than not: it fails by rebooting the computer. (Only around 1 time of 4 is successful.) A limited system start is (probably, always) successful: either with init=/bin/bash parameter to the kernel, or choosing the recovery boot option. (However, if I "resume" from the recovery menu, or run "exec init" in bash, then the upstart procedure is similarly unstable: it usually fails/crashes and reboots.) I checked my suspection that the video driver (nouveau) and X might be involved, but that turned out not true: the upstart procedure is similarly unstable with "nomodesetting" kernel parameter and without, booting into runlevel 3 or the default one. Perhaps, I'd like to debug the upstart procedure step-by-step to detect which step makes the system crash and reboot, but I don't know how. As concerns the timing, the moment the reboot happens can be different: it can happen rather early (when I see the message about activating the swap) or much later. If the system upstart procedure has completed successfully, then it works in a quite stable manner and doesn't crash/reboot. So, there is something bad specifically during the system upstart procedure. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: upstart 1.13.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14 Uname: Linux 3.16.0-44-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.5 Architecture: i386 CurrentDesktop: Unity Date: Sat Sep 12 18:36:28 2015 InstallationDate: Installed on 2014-06-04 (464 days ago) InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 (20140204) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash SourcePackage: upstart UpgradeStatus: Upgraded to utopic on 2015-09-11 (0 days ago) UpstartBugCategory: System UpstartRunningSessionVersion: upstart 1.13.2 UpstartRunningSystemVersion: init (upstart 1.13.2) modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Отказано в доступе: '/etc/at.deny'] modified.conffile..etc.cron.daily.upstart: [modified] modified.conffile..etc.cups.cups.browsed.conf: [modified] modified.conffile..etc.default.apport: [modified] modified.conffile..etc.default.cups: [modified] modified.conffile..etc.init.d.binfmt.support: [modified] mtime.conffile..etc.X11.Xsession.d.99upstart: 2014-09-30T12:21:08 mtime.conffile..etc.cron.daily.upstart: 2014-09-30T12:27:13 mtime.conffile..etc.cups.cups.browsed.conf: 2015-09-06T09:29:16.410097 mtime.conffile..etc.default.apport: 2014-06-05T12:49:10.316398 mtime.conffile..etc.default.cups: 2015-09-06T09:20:49.891585 mtime.conffile..etc.init.d.binfmt.support: 2014-09-30T12:21:08 mtime.conffile..etc.upstart.xsessions: 2014-09-30T12:21:08 --- ApportVersion: 2.14.7-0ubuntu8.5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marsmorgana 1972 F pulseaudio CRDA: country RU: DFS-UNSET (2402 - 2482 @ 40), (N/A, 20) (5735 - 5835 @ 20), (N/A, 30) CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=9267c811-3a01-4484-b968-c08582280d81 InstallationDate: Installed on 2014-06-04 (464 days ago) InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 (20140204) MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510 Package: upstart 1.13.2-0ubuntu2 PackageArchitecture: i386 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14 RelatedPackageVersions: linux-restricted-modules-3.16.0-44-generic N/A linux-backports-modules-3.16.0-44-generic N/A linux-firmware 1.138.1 Tags: utopic utopic third-party-packages Uname: Linux 3.16.0-44-generic x86_64
[Touch-packages] [Bug 1495116] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1495116/+attachment/4462936/+files/Lspci.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/1495116 Title: booting with amd64 kernel and completely i386 userland is unstable during the system upstart Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in upstart package in Ubuntu: New Bug description: I wanted to run my 14.10 (Utopic) i386 system with the amd64 kernel, so I added that architecture and apt-get-installed the amd64 linux- image and linux-image-extra (I learned this was possible thanks to the advice at http://askubuntu.com/a/635774/19753 ). However, the system upstart procedure more often fails than not: it fails by rebooting the computer. (Only around 1 time of 4 is successful.) A limited system start is (probably, always) successful: either with init=/bin/bash parameter to the kernel, or choosing the recovery boot option. (However, if I "resume" from the recovery menu, or run "exec init" in bash, then the upstart procedure is similarly unstable: it usually fails/crashes and reboots.) I checked my suspection that the video driver (nouveau) and X might be involved, but that turned out not true: the upstart procedure is similarly unstable with "nomodesetting" kernel parameter and without, booting into runlevel 3 or the default one. Perhaps, I'd like to debug the upstart procedure step-by-step to detect which step makes the system crash and reboot, but I don't know how. As concerns the timing, the moment the reboot happens can be different: it can happen rather early (when I see the message about activating the swap) or much later. If the system upstart procedure has completed successfully, then it works in a quite stable manner and doesn't crash/reboot. So, there is something bad specifically during the system upstart procedure. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: upstart 1.13.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14 Uname: Linux 3.16.0-44-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.5 Architecture: i386 CurrentDesktop: Unity Date: Sat Sep 12 18:36:28 2015 InstallationDate: Installed on 2014-06-04 (464 days ago) InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 (20140204) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash SourcePackage: upstart UpgradeStatus: Upgraded to utopic on 2015-09-11 (0 days ago) UpstartBugCategory: System UpstartRunningSessionVersion: upstart 1.13.2 UpstartRunningSystemVersion: init (upstart 1.13.2) modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Отказано в доступе: '/etc/at.deny'] modified.conffile..etc.cron.daily.upstart: [modified] modified.conffile..etc.cups.cups.browsed.conf: [modified] modified.conffile..etc.default.apport: [modified] modified.conffile..etc.default.cups: [modified] modified.conffile..etc.init.d.binfmt.support: [modified] mtime.conffile..etc.X11.Xsession.d.99upstart: 2014-09-30T12:21:08 mtime.conffile..etc.cron.daily.upstart: 2014-09-30T12:27:13 mtime.conffile..etc.cups.cups.browsed.conf: 2015-09-06T09:29:16.410097 mtime.conffile..etc.default.apport: 2014-06-05T12:49:10.316398 mtime.conffile..etc.default.cups: 2015-09-06T09:20:49.891585 mtime.conffile..etc.init.d.binfmt.support: 2014-09-30T12:21:08 mtime.conffile..etc.upstart.xsessions: 2014-09-30T12:21:08 --- ApportVersion: 2.14.7-0ubuntu8.5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marsmorgana 1972 F pulseaudio CRDA: country RU: DFS-UNSET (2402 - 2482 @ 40), (N/A, 20) (5735 - 5835 @ 20), (N/A, 30) CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=9267c811-3a01-4484-b968-c08582280d81 InstallationDate: Installed on 2014-06-04 (464 days ago) InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 (20140204) MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510 Package: upstart 1.13.2-0ubuntu2 PackageArchitecture: i386 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14 RelatedPackageVersions: linux-restricted-modules-3.16.0-44-generic N/A linux-backports-modules-3.16.0-44-generic N/A linux-firmware 1.138.1 Tags: utopic utopic third-party-packages Uname: Linux 3.16.0-44-generic x86_64
[Touch-packages] [Bug 1478217] Re: can't pair bluetooth keyboard, phone doesn't show code.
Affects me too with MS BT mobile keyboard 5000. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1478217 Title: can't pair bluetooth keyboard, phone doesn't show code. Status in indicator-bluetooth package in Ubuntu: Confirmed Bug description: 1) Device: Meizu MX4 Ubuntu Edition OS: Ubuntu 15.04 (r68) - armhf (20150724-020304) 2) Bluez version 4.101-0ubuntu25 indicator-bluetooth version 0.0.6+14.10.20141006-0ubuntu1 3) When trying to connect a bluetooth keyboard (SilverCrest SBT 3.0 A1), pairing doesn't follow correct procedure. On other devices (Android 5.1.1 on Nexus 10; Ubuntu 15.04 on BTO laptop) a 6 digit number is displayed, which needs to be typed on the Bluetooth keyboard, followed by pressing [Enter]. 4) On Ubuntu touch, a dialogue appears asking to enter a 4 digit PIN on the phone. Default is '' and at first the phone says the device is connected, but the phone does not respond to any input from the keyboard. After some time the phone indicates the device is not connected. All of this is similarly described in this askubuntu article: http://askubuntu.com/questions/625533/how-to-pair-external-bluetooth- keyboard-to-ubuntu-touch-bq-phone, which has not received any answers as of yet. I am willing to follow instructions and report back results. i have adb shell installed on my laptop, and Terminal app installed on the phone. Developer mode is on. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1478217/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1495116] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1495116/+attachment/4462937/+files/Lsusb.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/1495116 Title: booting with amd64 kernel and completely i386 userland is unstable during the system upstart Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in upstart package in Ubuntu: New Bug description: I wanted to run my 14.10 (Utopic) i386 system with the amd64 kernel, so I added that architecture and apt-get-installed the amd64 linux- image and linux-image-extra (I learned this was possible thanks to the advice at http://askubuntu.com/a/635774/19753 ). However, the system upstart procedure more often fails than not: it fails by rebooting the computer. (Only around 1 time of 4 is successful.) A limited system start is (probably, always) successful: either with init=/bin/bash parameter to the kernel, or choosing the recovery boot option. (However, if I "resume" from the recovery menu, or run "exec init" in bash, then the upstart procedure is similarly unstable: it usually fails/crashes and reboots.) I checked my suspection that the video driver (nouveau) and X might be involved, but that turned out not true: the upstart procedure is similarly unstable with "nomodesetting" kernel parameter and without, booting into runlevel 3 or the default one. Perhaps, I'd like to debug the upstart procedure step-by-step to detect which step makes the system crash and reboot, but I don't know how. As concerns the timing, the moment the reboot happens can be different: it can happen rather early (when I see the message about activating the swap) or much later. If the system upstart procedure has completed successfully, then it works in a quite stable manner and doesn't crash/reboot. So, there is something bad specifically during the system upstart procedure. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: upstart 1.13.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14 Uname: Linux 3.16.0-44-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.5 Architecture: i386 CurrentDesktop: Unity Date: Sat Sep 12 18:36:28 2015 InstallationDate: Installed on 2014-06-04 (464 days ago) InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 (20140204) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash SourcePackage: upstart UpgradeStatus: Upgraded to utopic on 2015-09-11 (0 days ago) UpstartBugCategory: System UpstartRunningSessionVersion: upstart 1.13.2 UpstartRunningSystemVersion: init (upstart 1.13.2) modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Отказано в доступе: '/etc/at.deny'] modified.conffile..etc.cron.daily.upstart: [modified] modified.conffile..etc.cups.cups.browsed.conf: [modified] modified.conffile..etc.default.apport: [modified] modified.conffile..etc.default.cups: [modified] modified.conffile..etc.init.d.binfmt.support: [modified] mtime.conffile..etc.X11.Xsession.d.99upstart: 2014-09-30T12:21:08 mtime.conffile..etc.cron.daily.upstart: 2014-09-30T12:27:13 mtime.conffile..etc.cups.cups.browsed.conf: 2015-09-06T09:29:16.410097 mtime.conffile..etc.default.apport: 2014-06-05T12:49:10.316398 mtime.conffile..etc.default.cups: 2015-09-06T09:20:49.891585 mtime.conffile..etc.init.d.binfmt.support: 2014-09-30T12:21:08 mtime.conffile..etc.upstart.xsessions: 2014-09-30T12:21:08 --- ApportVersion: 2.14.7-0ubuntu8.5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marsmorgana 1972 F pulseaudio CRDA: country RU: DFS-UNSET (2402 - 2482 @ 40), (N/A, 20) (5735 - 5835 @ 20), (N/A, 30) CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=9267c811-3a01-4484-b968-c08582280d81 InstallationDate: Installed on 2014-06-04 (464 days ago) InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 (20140204) MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510 Package: upstart 1.13.2-0ubuntu2 PackageArchitecture: i386 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14 RelatedPackageVersions: linux-restricted-modules-3.16.0-44-generic N/A linux-backports-modules-3.16.0-44-generic N/A linux-firmware 1.138.1 Tags: utopic utopic third-party-packages Uname: Linux 3.16.0-44-generic x86_64
[Touch-packages] [Bug 1495116] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1495116/+attachment/4462942/+files/PulseList.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/1495116 Title: booting with amd64 kernel and completely i386 userland is unstable during the system upstart Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in upstart package in Ubuntu: New Bug description: I wanted to run my 14.10 (Utopic) i386 system with the amd64 kernel, so I added that architecture and apt-get-installed the amd64 linux- image and linux-image-extra (I learned this was possible thanks to the advice at http://askubuntu.com/a/635774/19753 ). However, the system upstart procedure more often fails than not: it fails by rebooting the computer. (Only around 1 time of 4 is successful.) A limited system start is (probably, always) successful: either with init=/bin/bash parameter to the kernel, or choosing the recovery boot option. (However, if I "resume" from the recovery menu, or run "exec init" in bash, then the upstart procedure is similarly unstable: it usually fails/crashes and reboots.) I checked my suspection that the video driver (nouveau) and X might be involved, but that turned out not true: the upstart procedure is similarly unstable with "nomodesetting" kernel parameter and without, booting into runlevel 3 or the default one. Perhaps, I'd like to debug the upstart procedure step-by-step to detect which step makes the system crash and reboot, but I don't know how. As concerns the timing, the moment the reboot happens can be different: it can happen rather early (when I see the message about activating the swap) or much later. If the system upstart procedure has completed successfully, then it works in a quite stable manner and doesn't crash/reboot. So, there is something bad specifically during the system upstart procedure. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: upstart 1.13.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14 Uname: Linux 3.16.0-44-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.5 Architecture: i386 CurrentDesktop: Unity Date: Sat Sep 12 18:36:28 2015 InstallationDate: Installed on 2014-06-04 (464 days ago) InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 (20140204) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash SourcePackage: upstart UpgradeStatus: Upgraded to utopic on 2015-09-11 (0 days ago) UpstartBugCategory: System UpstartRunningSessionVersion: upstart 1.13.2 UpstartRunningSystemVersion: init (upstart 1.13.2) modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Отказано в доступе: '/etc/at.deny'] modified.conffile..etc.cron.daily.upstart: [modified] modified.conffile..etc.cups.cups.browsed.conf: [modified] modified.conffile..etc.default.apport: [modified] modified.conffile..etc.default.cups: [modified] modified.conffile..etc.init.d.binfmt.support: [modified] mtime.conffile..etc.X11.Xsession.d.99upstart: 2014-09-30T12:21:08 mtime.conffile..etc.cron.daily.upstart: 2014-09-30T12:27:13 mtime.conffile..etc.cups.cups.browsed.conf: 2015-09-06T09:29:16.410097 mtime.conffile..etc.default.apport: 2014-06-05T12:49:10.316398 mtime.conffile..etc.default.cups: 2015-09-06T09:20:49.891585 mtime.conffile..etc.init.d.binfmt.support: 2014-09-30T12:21:08 mtime.conffile..etc.upstart.xsessions: 2014-09-30T12:21:08 --- ApportVersion: 2.14.7-0ubuntu8.5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marsmorgana 1972 F pulseaudio CRDA: country RU: DFS-UNSET (2402 - 2482 @ 40), (N/A, 20) (5735 - 5835 @ 20), (N/A, 30) CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=9267c811-3a01-4484-b968-c08582280d81 InstallationDate: Installed on 2014-06-04 (464 days ago) InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 (20140204) MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510 Package: upstart 1.13.2-0ubuntu2 PackageArchitecture: i386 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14 RelatedPackageVersions: linux-restricted-modules-3.16.0-44-generic N/A linux-backports-modules-3.16.0-44-generic N/A linux-firmware 1.138.1 Tags: utopic utopic third-party-packages Uname: Linux 3.16.0-44-generic x86_64
[Touch-packages] [Bug 1495116] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1495116/+attachment/4462950/+files/UdevLog.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/1495116 Title: booting with amd64 kernel and completely i386 userland is unstable during the system upstart Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in upstart package in Ubuntu: New Bug description: I wanted to run my 14.10 (Utopic) i386 system with the amd64 kernel, so I added that architecture and apt-get-installed the amd64 linux- image and linux-image-extra (I learned this was possible thanks to the advice at http://askubuntu.com/a/635774/19753 ). However, the system upstart procedure more often fails than not: it fails by rebooting the computer. (Only around 1 time of 4 is successful.) A limited system start is (probably, always) successful: either with init=/bin/bash parameter to the kernel, or choosing the recovery boot option. (However, if I "resume" from the recovery menu, or run "exec init" in bash, then the upstart procedure is similarly unstable: it usually fails/crashes and reboots.) I checked my suspection that the video driver (nouveau) and X might be involved, but that turned out not true: the upstart procedure is similarly unstable with "nomodesetting" kernel parameter and without, booting into runlevel 3 or the default one. Perhaps, I'd like to debug the upstart procedure step-by-step to detect which step makes the system crash and reboot, but I don't know how. As concerns the timing, the moment the reboot happens can be different: it can happen rather early (when I see the message about activating the swap) or much later. If the system upstart procedure has completed successfully, then it works in a quite stable manner and doesn't crash/reboot. So, there is something bad specifically during the system upstart procedure. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: upstart 1.13.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14 Uname: Linux 3.16.0-44-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.5 Architecture: i386 CurrentDesktop: Unity Date: Sat Sep 12 18:36:28 2015 InstallationDate: Installed on 2014-06-04 (464 days ago) InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 (20140204) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash SourcePackage: upstart UpgradeStatus: Upgraded to utopic on 2015-09-11 (0 days ago) UpstartBugCategory: System UpstartRunningSessionVersion: upstart 1.13.2 UpstartRunningSystemVersion: init (upstart 1.13.2) modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Отказано в доступе: '/etc/at.deny'] modified.conffile..etc.cron.daily.upstart: [modified] modified.conffile..etc.cups.cups.browsed.conf: [modified] modified.conffile..etc.default.apport: [modified] modified.conffile..etc.default.cups: [modified] modified.conffile..etc.init.d.binfmt.support: [modified] mtime.conffile..etc.X11.Xsession.d.99upstart: 2014-09-30T12:21:08 mtime.conffile..etc.cron.daily.upstart: 2014-09-30T12:27:13 mtime.conffile..etc.cups.cups.browsed.conf: 2015-09-06T09:29:16.410097 mtime.conffile..etc.default.apport: 2014-06-05T12:49:10.316398 mtime.conffile..etc.default.cups: 2015-09-06T09:20:49.891585 mtime.conffile..etc.init.d.binfmt.support: 2014-09-30T12:21:08 mtime.conffile..etc.upstart.xsessions: 2014-09-30T12:21:08 --- ApportVersion: 2.14.7-0ubuntu8.5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marsmorgana 1972 F pulseaudio CRDA: country RU: DFS-UNSET (2402 - 2482 @ 40), (N/A, 20) (5735 - 5835 @ 20), (N/A, 30) CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=9267c811-3a01-4484-b968-c08582280d81 InstallationDate: Installed on 2014-06-04 (464 days ago) InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 (20140204) MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510 Package: upstart 1.13.2-0ubuntu2 PackageArchitecture: i386 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14 RelatedPackageVersions: linux-restricted-modules-3.16.0-44-generic N/A linux-backports-modules-3.16.0-44-generic N/A linux-firmware 1.138.1 Tags: utopic utopic third-party-packages Uname: Linux 3.16.0-44-generic x86_64
[Touch-packages] [Bug 1495116] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1495116/+attachment/4462944/+files/UdevDb.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/1495116 Title: booting with amd64 kernel and completely i386 userland is unstable during the system upstart Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in upstart package in Ubuntu: New Bug description: I wanted to run my 14.10 (Utopic) i386 system with the amd64 kernel, so I added that architecture and apt-get-installed the amd64 linux- image and linux-image-extra (I learned this was possible thanks to the advice at http://askubuntu.com/a/635774/19753 ). However, the system upstart procedure more often fails than not: it fails by rebooting the computer. (Only around 1 time of 4 is successful.) A limited system start is (probably, always) successful: either with init=/bin/bash parameter to the kernel, or choosing the recovery boot option. (However, if I "resume" from the recovery menu, or run "exec init" in bash, then the upstart procedure is similarly unstable: it usually fails/crashes and reboots.) I checked my suspection that the video driver (nouveau) and X might be involved, but that turned out not true: the upstart procedure is similarly unstable with "nomodesetting" kernel parameter and without, booting into runlevel 3 or the default one. Perhaps, I'd like to debug the upstart procedure step-by-step to detect which step makes the system crash and reboot, but I don't know how. As concerns the timing, the moment the reboot happens can be different: it can happen rather early (when I see the message about activating the swap) or much later. If the system upstart procedure has completed successfully, then it works in a quite stable manner and doesn't crash/reboot. So, there is something bad specifically during the system upstart procedure. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: upstart 1.13.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14 Uname: Linux 3.16.0-44-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.5 Architecture: i386 CurrentDesktop: Unity Date: Sat Sep 12 18:36:28 2015 InstallationDate: Installed on 2014-06-04 (464 days ago) InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 (20140204) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash SourcePackage: upstart UpgradeStatus: Upgraded to utopic on 2015-09-11 (0 days ago) UpstartBugCategory: System UpstartRunningSessionVersion: upstart 1.13.2 UpstartRunningSystemVersion: init (upstart 1.13.2) modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Отказано в доступе: '/etc/at.deny'] modified.conffile..etc.cron.daily.upstart: [modified] modified.conffile..etc.cups.cups.browsed.conf: [modified] modified.conffile..etc.default.apport: [modified] modified.conffile..etc.default.cups: [modified] modified.conffile..etc.init.d.binfmt.support: [modified] mtime.conffile..etc.X11.Xsession.d.99upstart: 2014-09-30T12:21:08 mtime.conffile..etc.cron.daily.upstart: 2014-09-30T12:27:13 mtime.conffile..etc.cups.cups.browsed.conf: 2015-09-06T09:29:16.410097 mtime.conffile..etc.default.apport: 2014-06-05T12:49:10.316398 mtime.conffile..etc.default.cups: 2015-09-06T09:20:49.891585 mtime.conffile..etc.init.d.binfmt.support: 2014-09-30T12:21:08 mtime.conffile..etc.upstart.xsessions: 2014-09-30T12:21:08 --- ApportVersion: 2.14.7-0ubuntu8.5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marsmorgana 1972 F pulseaudio CRDA: country RU: DFS-UNSET (2402 - 2482 @ 40), (N/A, 20) (5735 - 5835 @ 20), (N/A, 30) CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=9267c811-3a01-4484-b968-c08582280d81 InstallationDate: Installed on 2014-06-04 (464 days ago) InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 (20140204) MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510 Package: upstart 1.13.2-0ubuntu2 PackageArchitecture: i386 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14 RelatedPackageVersions: linux-restricted-modules-3.16.0-44-generic N/A linux-backports-modules-3.16.0-44-generic N/A linux-firmware 1.138.1 Tags: utopic utopic third-party-packages Uname: Linux 3.16.0-44-generic x86_64
[Touch-packages] [Bug 1495116] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1495116/+attachment/4462943/+files/RfKill.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/1495116 Title: booting with amd64 kernel and completely i386 userland is unstable during the system upstart Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in upstart package in Ubuntu: New Bug description: I wanted to run my 14.10 (Utopic) i386 system with the amd64 kernel, so I added that architecture and apt-get-installed the amd64 linux- image and linux-image-extra (I learned this was possible thanks to the advice at http://askubuntu.com/a/635774/19753 ). However, the system upstart procedure more often fails than not: it fails by rebooting the computer. (Only around 1 time of 4 is successful.) A limited system start is (probably, always) successful: either with init=/bin/bash parameter to the kernel, or choosing the recovery boot option. (However, if I "resume" from the recovery menu, or run "exec init" in bash, then the upstart procedure is similarly unstable: it usually fails/crashes and reboots.) I checked my suspection that the video driver (nouveau) and X might be involved, but that turned out not true: the upstart procedure is similarly unstable with "nomodesetting" kernel parameter and without, booting into runlevel 3 or the default one. Perhaps, I'd like to debug the upstart procedure step-by-step to detect which step makes the system crash and reboot, but I don't know how. As concerns the timing, the moment the reboot happens can be different: it can happen rather early (when I see the message about activating the swap) or much later. If the system upstart procedure has completed successfully, then it works in a quite stable manner and doesn't crash/reboot. So, there is something bad specifically during the system upstart procedure. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: upstart 1.13.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14 Uname: Linux 3.16.0-44-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.5 Architecture: i386 CurrentDesktop: Unity Date: Sat Sep 12 18:36:28 2015 InstallationDate: Installed on 2014-06-04 (464 days ago) InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 (20140204) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash SourcePackage: upstart UpgradeStatus: Upgraded to utopic on 2015-09-11 (0 days ago) UpstartBugCategory: System UpstartRunningSessionVersion: upstart 1.13.2 UpstartRunningSystemVersion: init (upstart 1.13.2) modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Отказано в доступе: '/etc/at.deny'] modified.conffile..etc.cron.daily.upstart: [modified] modified.conffile..etc.cups.cups.browsed.conf: [modified] modified.conffile..etc.default.apport: [modified] modified.conffile..etc.default.cups: [modified] modified.conffile..etc.init.d.binfmt.support: [modified] mtime.conffile..etc.X11.Xsession.d.99upstart: 2014-09-30T12:21:08 mtime.conffile..etc.cron.daily.upstart: 2014-09-30T12:27:13 mtime.conffile..etc.cups.cups.browsed.conf: 2015-09-06T09:29:16.410097 mtime.conffile..etc.default.apport: 2014-06-05T12:49:10.316398 mtime.conffile..etc.default.cups: 2015-09-06T09:20:49.891585 mtime.conffile..etc.init.d.binfmt.support: 2014-09-30T12:21:08 mtime.conffile..etc.upstart.xsessions: 2014-09-30T12:21:08 --- ApportVersion: 2.14.7-0ubuntu8.5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marsmorgana 1972 F pulseaudio CRDA: country RU: DFS-UNSET (2402 - 2482 @ 40), (N/A, 20) (5735 - 5835 @ 20), (N/A, 30) CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=9267c811-3a01-4484-b968-c08582280d81 InstallationDate: Installed on 2014-06-04 (464 days ago) InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 (20140204) MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510 Package: upstart 1.13.2-0ubuntu2 PackageArchitecture: i386 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14 RelatedPackageVersions: linux-restricted-modules-3.16.0-44-generic N/A linux-backports-modules-3.16.0-44-generic N/A linux-firmware 1.138.1 Tags: utopic utopic third-party-packages Uname: Linux 3.16.0-44-generic x86_64
[Touch-packages] [Bug 1351890] Re: Changing external screen resolution with dual monitors
Looks good in Trusty. Since Precise has the fix in -proposed already as well, tagging it as verification-done. ** 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 gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1351890 Title: Changing external screen resolution with dual monitors Status in GTK+: Fix Released Status in ubuntu-mate: Fix Released Status in gtk+2.0 package in Ubuntu: Fix Released Status in mate-control-center package in Ubuntu: Fix Released Status in gtk+2.0 source package in Precise: Fix Committed Status in gtk+2.0 source package in Trusty: Fix Committed Status in gtk+2.0 package in Debian: Fix Released Bug description: [Impact] Due to a bug in GTK+2, mate-display-properties crashes when the screen resolution is changed *outside* of it (e.g. by changing the resolution not via that app, but somewhere else). The attached patches fix the issue in GTK+2 and prevent crashing of m-d-p. Since this issue caused much inconvenience for users, the fix should be backported to all current stable releases of Ubuntu. [Test Case] The easiest way to reproduce it is via Virtualbox: 1. Run mate-display-properties in the VM. 2. Make the VM go full-screen. 3. See m-d-p crash. [Regression Potential] After several months of testing the patched version of GTK+2 in Debian Jessie, I found no regressions. I consider the regression risk very low here. There were originally some bugs with a few applications (notably Spotify) crashing. We think we've backported patches to fix that - some refcounting issues - but please check a few apps to see they still work. [ Original report ] Changing extrnal screen resolution with dual mon ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: mate-control-center 1.8.1+dfsg1-4 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic i686 ApportVersion: 2.14.5-0ubuntu3 Architecture: i386 CrashCounter: 1 Date: Sun Aug 3 07:09:21 2014 ExecutablePath: /usr/bin/mate-display-properties InstallationDate: Installed on 2014-08-03 (0 days ago) InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - Alpha i386 (20140731) ProcCmdline: mate-display-properties SegvAnalysis: Skipped: missing required field "Disassembly" Signal: 11 SourcePackage: mate-control-center UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1351890/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1456730] Re: Hangs on shutdown after installing and running serviio
Reinstalled to /opt Added /lib/systemd/system/serviio.service with [Unit] Description=Serviio Media Server After=syslog.target local-fs.target network.target [Service] Type=simple User=serviio Group=serviio ExecStart=/opt/serviio/bin/serviio.sh ExecStop=/opt/serviio/bin/serviio.sh -stop KillMode=none Restart=on-abort [Install] WantedBy=multi-user.target Enabled and started service. Small script to start the console added to startup #!/bin/sh /opt/serviio/bin/serviio-console.sh exit 0 No further issues with shutdowns or reboots (http://wiki.serviio.org/doku.php?id=howto:linux:install:ubuntu15-04) -- 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/1456730 Title: Hangs on shutdown after installing and running serviio Status in systemd package in Ubuntu: Confirmed Bug description: Ran serviio during the vivid cycle with no problem - either using systemd or upstart. Installed wily. Grabbed,extracted serviio from http://download.serviio.org/releases/serviio-1.5.2-linux.tar.gz Installed openjdk-8-jre. Set ~/serviio-1.5.2/bin/serviio.sh and ~/serviio-1.5.2/bin/serviio- console.sh to run at start. Reboot using systemd,serviio starts. Reboot hangs for 90s. Kill java tasks associated with serviio - reboot takes place in time expected. Boot with upstart - reboot takes place in time expected. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: systemd 219-9ubuntu1 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] ProcVersionSignature: Ubuntu 3.19.0-17.17-generic 3.19.6 Uname: Linux 3.19.0-17-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE Date: Tue May 19 18:19:40 2015 InstallationDate: Installed on 2015-05-12 (6 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150512) MachineType: NOVATECH LTD MBB-44608 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-17-generic root=UUID=6bcbfcc1-c493-4dbe-9421-ef270047a82a ro quiet splash SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-DS2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: 7383241-001 dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.chassis.version: V1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0: dmi.product.name: MBB-44608 dmi.product.version: V1.0 dmi.sys.vendor: NOVATECH LTD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1456730/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1474934] Re: package libfluidsynth1:amd64 1.1.6-2 failed to install/upgrade: package libfluidsynth1:amd64 is already installed and configured
*** This bug is a duplicate of bug 1407757 *** https://bugs.launchpad.net/bugs/1407757 ** This bug has been marked a duplicate of bug 1407757 multi-arch packages cannot be installed due to dpkg wrongly detecting them as already installed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fluidsynth in Ubuntu. https://bugs.launchpad.net/bugs/1474934 Title: package libfluidsynth1:amd64 1.1.6-2 failed to install/upgrade: package libfluidsynth1:amd64 is already installed and configured Status in fluidsynth package in Ubuntu: Confirmed Bug description: libreoffice intalation ProblemType: Package DistroRelease: Ubuntu 15.04 Package: libfluidsynth1:amd64 1.1.6-2 ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1 Uname: Linux 3.19.0-22-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 AptdaemonVersion: 1.1.1+bzr982-0ubuntu3.1 Architecture: amd64 Date: Wed Jul 15 12:38:37 2015 DuplicateSignature: package:libfluidsynth1:amd64:1.1.6-2:package libfluidsynth1:amd64 is already installed and configured ErrorMessage: package libfluidsynth1:amd64 is already installed and configured InstallationDate: Installed on 2015-07-13 (2 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4 SourcePackage: fluidsynth Title: package libfluidsynth1:amd64 1.1.6-2 failed to install/upgrade: package libfluidsynth1:amd64 is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fluidsynth/+bug/1474934/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1495206] [NEW] System slow on dual-monitor
Public bug reported: I connected to my laptop an external monitor (Dell P2314H) via HDMI and since than then the system is extremely slow, but only when the external display is connected. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.5-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-64.104-generic 3.13.11-ckt26 Uname: Linux 3.13.0-64-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.13 Architecture: amd64 CurrentDesktop: Unity Date: Sun Sep 13 13:17:56 2015 InstallationDate: Installed on 2015-06-03 (102 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty -- 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/1495206 Title: System slow on dual-monitor Status in lightdm package in Ubuntu: New Bug description: I connected to my laptop an external monitor (Dell P2314H) via HDMI and since than then the system is extremely slow, but only when the external display is connected. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.5-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-64.104-generic 3.13.11-ckt26 Uname: Linux 3.13.0-64-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.13 Architecture: amd64 CurrentDesktop: Unity Date: Sun Sep 13 13:17:56 2015 InstallationDate: Installed on 2015-06-03 (102 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1495206/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1490258] Re: It's difficult to answer a call on arale
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: dialer-app (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1490258 Title: It's difficult to answer a call on arale Status in Ubuntu UX: New Status in dialer-app package in Ubuntu: Confirmed Bug description: The indicator to answer a call is at the top of the phone. On large screen, as the MX4, it's difficult to answer to a call using only one hand. Probably there could be improvements, like moving the indicator to the bottom. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1490258/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 893210] Re: [Dell OptiPlex GX620 - AD1981b, playback] No sound at all
http://cgit.freedesktop.org/pulseaudio/pulseaudio/tree/src/modules/alsa/mixer/paths /analog-output-headphones.conf it is because headphone port mute master mono [Element Master Mono] switch = off volume = off as only snd-hda-intel implement jack detection kctl those snd-intel8x0 does not have any jack detection kctl -- 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/893210 Title: [Dell OptiPlex GX620 - AD1981b, playback] No sound at all Status in ALSA driver: Confirmed Status in alsa-driver package in Ubuntu: Incomplete Bug description: fresh install of ubuntu studio and updates but internal speakers do not play. dell optiplex gx620 love ya ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: alsa-base 1.0.24+dfsg-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6 Uname: Linux 3.0.0-13-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.23-0ubuntu4 Architecture: i386 Card0.Amixer.info: Card hw:0 'ICH7'/'Intel ICH7 with AD1981B at irq 23' Mixer name : 'Analog Devices AD1981B' Components : 'AC97a:41445374' Controls : 28 Simple ctrls : 20 Card1.Amixer.info: Card hw:1 'Device'/'C-Media Electronics Inc. USB Multimedia Audio Device at usb-:00:1d.7-4.1.4,' Mixer name : 'USB Mixer' Components : 'USB0d8c:0105' Controls : 13 Simple ctrls : 6 Date: Mon Nov 21 11:51:25 2011 InstallationMedia: Ubuntu-Studio 11.10 "Oneiric Ocelot" - Release i386 (20111011.1) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:ICH7 failed Symptom_Card: CM108 Audio Controller - USB Multimedia Audio Device Symptom_Type: No sound at all Title: [ICH4 - Intel ICH7, playback] No sound at all UpgradeStatus: Upgraded to oneiric on 2011-11-12 (8 days ago) dmi.bios.date: 11/30/2006 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0F8101 dmi.board.vendor: Dell Inc. dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0F8101:rvr:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex GX620 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/893210/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 893210] Re: [Dell OptiPlex GX620 - AD1981b, playback] No sound at all
try to set those ac97 registers 0x72 by turn off headphone jack sense and line jack sense control http://cgit.freedesktop.org/pulseaudio/pulseaudio/patch/src/modules/alsa/mixer/paths?id=ba0203c4c0938fd646cf559456e3d691fc889029 do you mean regression of this patch ? you have to open another pulseaudio bug report -- 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/893210 Title: [Dell OptiPlex GX620 - AD1981b, playback] No sound at all Status in ALSA driver: Confirmed Status in alsa-driver package in Ubuntu: Incomplete Bug description: fresh install of ubuntu studio and updates but internal speakers do not play. dell optiplex gx620 love ya ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: alsa-base 1.0.24+dfsg-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6 Uname: Linux 3.0.0-13-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.23-0ubuntu4 Architecture: i386 Card0.Amixer.info: Card hw:0 'ICH7'/'Intel ICH7 with AD1981B at irq 23' Mixer name : 'Analog Devices AD1981B' Components : 'AC97a:41445374' Controls : 28 Simple ctrls : 20 Card1.Amixer.info: Card hw:1 'Device'/'C-Media Electronics Inc. USB Multimedia Audio Device at usb-:00:1d.7-4.1.4,' Mixer name : 'USB Mixer' Components : 'USB0d8c:0105' Controls : 13 Simple ctrls : 6 Date: Mon Nov 21 11:51:25 2011 InstallationMedia: Ubuntu-Studio 11.10 "Oneiric Ocelot" - Release i386 (20111011.1) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:ICH7 failed Symptom_Card: CM108 Audio Controller - USB Multimedia Audio Device Symptom_Type: No sound at all Title: [ICH4 - Intel ICH7, playback] No sound at all UpgradeStatus: Upgraded to oneiric on 2011-11-12 (8 days ago) dmi.bios.date: 11/30/2006 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0F8101 dmi.board.vendor: Dell Inc. dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0F8101:rvr:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex GX620 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/893210/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1495116] Re: booting with amd64 kernel and completely i386 userland is unstable during the system upstart
With systemd.crash_shell=true systemd.confirm_spawn=true (which is very inconvenient to use), I've found out that the crash usually happens somewhere around the start of udev services. ** Also affects: udev (Ubuntu) Importance: Undecided Status: New -- 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/1495116 Title: booting with amd64 kernel and completely i386 userland is unstable during the system upstart Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Status in udev package in Ubuntu: Incomplete Status in upstart package in Ubuntu: Incomplete Bug description: I wanted to run my 14.10 (Utopic) i386 system with the amd64 kernel, so I added that architecture and apt-get-installed the amd64 linux- image and linux-image-extra (I learned this was possible thanks to the advice at http://askubuntu.com/a/635774/19753 ). However, the system upstart procedure more often fails than not: it fails by rebooting the computer. (Only around 1 time of 4 is successful.) A limited system start is (probably, always) successful: either with init=/bin/bash parameter to the kernel, or choosing the recovery boot option. (However, if I "resume" from the recovery menu, or run "exec init" in bash, then the upstart procedure is similarly unstable: it usually fails/crashes and reboots.) I checked my suspection that the video driver (nouveau) and X might be involved, but that turned out not true: the upstart procedure is similarly unstable with "nomodesetting" kernel parameter and without, booting into runlevel 3 or the default one. Perhaps, I'd like to debug the upstart procedure step-by-step to detect which step makes the system crash and reboot, but I don't know how. As concerns the timing, the moment the reboot happens can be different: it can happen rather early (when I see the message about activating the swap) or much later. If the system upstart procedure has completed successfully, then it works in a quite stable manner and doesn't crash/reboot. So, there is something bad specifically during the system upstart procedure. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: upstart 1.13.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14 Uname: Linux 3.16.0-44-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.5 Architecture: i386 CurrentDesktop: Unity Date: Sat Sep 12 18:36:28 2015 InstallationDate: Installed on 2014-06-04 (464 days ago) InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 (20140204) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash SourcePackage: upstart UpgradeStatus: Upgraded to utopic on 2015-09-11 (0 days ago) UpstartBugCategory: System UpstartRunningSessionVersion: upstart 1.13.2 UpstartRunningSystemVersion: init (upstart 1.13.2) modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Отказано в доступе: '/etc/at.deny'] modified.conffile..etc.cron.daily.upstart: [modified] modified.conffile..etc.cups.cups.browsed.conf: [modified] modified.conffile..etc.default.apport: [modified] modified.conffile..etc.default.cups: [modified] modified.conffile..etc.init.d.binfmt.support: [modified] mtime.conffile..etc.X11.Xsession.d.99upstart: 2014-09-30T12:21:08 mtime.conffile..etc.cron.daily.upstart: 2014-09-30T12:27:13 mtime.conffile..etc.cups.cups.browsed.conf: 2015-09-06T09:29:16.410097 mtime.conffile..etc.default.apport: 2014-06-05T12:49:10.316398 mtime.conffile..etc.default.cups: 2015-09-06T09:20:49.891585 mtime.conffile..etc.init.d.binfmt.support: 2014-09-30T12:21:08 mtime.conffile..etc.upstart.xsessions: 2014-09-30T12:21:08 --- ApportVersion: 2.14.7-0ubuntu8.5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marsmorgana 1972 F pulseaudio CRDA: country RU: DFS-UNSET (2402 - 2482 @ 40), (N/A, 20) (5735 - 5835 @ 20), (N/A, 30) CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=9267c811-3a01-4484-b968-c08582280d81 InstallationDate: Installed on 2014-06-04 (464 days ago) InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 (20140204) MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510 Package: upstart 1.13.2-0ubuntu2 PackageArchitecture: i386 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14 RelatedPackageVersions: linux-restricted-modules-3.16.0-44-generic N/A
[Touch-packages] [Bug 1384454] Re: Dual screen, windows in RH screen move workspace on suspend resume
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/1384454 Title: Dual screen, windows in RH screen move workspace on suspend resume Status in Linux: New Status in Unity: New Status in unity package in Ubuntu: Confirmed Bug description: On up to date Utopic release candidate with dual screens (laptop + external), windows on the external (right hand) screen often move to next workspace following suspend - resume. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Oct 22 21:55:07 2014 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Fujitsu Limited. Device [10cf:17a9] InstallationDate: Installed on 2014-10-21 (1 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017) MachineType: FUJITSU LIFEBOOK A544 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic root=UUID=c68c6484-d8d6-44f6-b429-892aa6ef74cf ro quiet splash i8042.notimeout i8042.nomux vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/09/2014 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.17 dmi.board.name: FJNBB35 dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.17:bd05/09/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr: dmi.product.name: LIFEBOOK A544 dmi.sys.vendor: FUJITSU version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Wed Oct 22 21:21:24 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 13890 vendor SEC xserver.version: 2:1.16.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1384454/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1450960] Re: dev file system is mounted without noexec
** Patch added: "Patch for host, package udev, on top of a current wily installation" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1450960/+attachment/4463061/+files/udev.patch -- 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/1450960 Title: dev file system is mounted without noexec Status in lxc package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Triaged Bug description: I just found that the /dev filesystem of most Ubuntu system is mounted without noexec, nosuid etc options. If you do everything to harden your system, and you are using squashfs as root file system (which is read-only), such auto-mounted devices can be a serious leak. This volume usually is quite small and for most folders only root has write access, so I don't know how much this bug is security relevant, but I think there is no reason to not change the mount options for /dev. And especially for LXC containers, I don't even know a workaround to fix it. STEPS TO REPRODUCE: me:~# cat >/dev/call-me.sh <<.e > #!/bin/sh > echo "I'm executable" > .e me:~# chmod +x /dev/call-me.sh me:~# /dev/call-me.sh I'm executable EXPECTED BEHAVIOUR me:~# /dev/call-me.sh -bash: /dev/call-me.sh: Permission denied WORKAROUND me:~# mount -oremount,noexec,nosuid /dev me:~# /dev/call-me.sh -bash: /dev/call-me.sh: Permission denied Unfortunately, this workaround doesn't work in LXC containers (where the same problem occurs) because of missing capabilities. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: udev 204-5ubuntu20.11 ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17 Uname: Linux 3.13.0-49-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 CurrentDesktop: XFCE CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied CustomUdevRuleFiles: 51-android.rules 60-vboxdrv.rules Date: Sat May 2 01:48:26 2015 MachineType: Gigabyte Technology Co., Ltd. H97-HD3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-49-generic root=/dev/mapper/vg_ssd-lv_system_trusty1404 ro SourcePackage: systemd UpgradeStatus: Upgraded to trusty on 2014-04-18 (378 days ago) dmi.bios.date: 06/26/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H97-HD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/26/2014:svnGigabyteTechnologyCo.,Ltd.:pnH97-HD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH97-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: H97-HD3 dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1450960] Re: dev file system is mounted without noexec
** Patch added: "Patch for host, package initramfs-tools, on top of a current wily installation" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1450960/+attachment/4463062/+files/initramfs-tools.patch -- 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/1450960 Title: dev file system is mounted without noexec Status in lxc package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Triaged Bug description: I just found that the /dev filesystem of most Ubuntu system is mounted without noexec, nosuid etc options. If you do everything to harden your system, and you are using squashfs as root file system (which is read-only), such auto-mounted devices can be a serious leak. This volume usually is quite small and for most folders only root has write access, so I don't know how much this bug is security relevant, but I think there is no reason to not change the mount options for /dev. And especially for LXC containers, I don't even know a workaround to fix it. STEPS TO REPRODUCE: me:~# cat >/dev/call-me.sh <<.e > #!/bin/sh > echo "I'm executable" > .e me:~# chmod +x /dev/call-me.sh me:~# /dev/call-me.sh I'm executable EXPECTED BEHAVIOUR me:~# /dev/call-me.sh -bash: /dev/call-me.sh: Permission denied WORKAROUND me:~# mount -oremount,noexec,nosuid /dev me:~# /dev/call-me.sh -bash: /dev/call-me.sh: Permission denied Unfortunately, this workaround doesn't work in LXC containers (where the same problem occurs) because of missing capabilities. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: udev 204-5ubuntu20.11 ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17 Uname: Linux 3.13.0-49-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 CurrentDesktop: XFCE CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied CustomUdevRuleFiles: 51-android.rules 60-vboxdrv.rules Date: Sat May 2 01:48:26 2015 MachineType: Gigabyte Technology Co., Ltd. H97-HD3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-49-generic root=/dev/mapper/vg_ssd-lv_system_trusty1404 ro SourcePackage: systemd UpgradeStatus: Upgraded to trusty on 2014-04-18 (378 days ago) dmi.bios.date: 06/26/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H97-HD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/26/2014:svnGigabyteTechnologyCo.,Ltd.:pnH97-HD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH97-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: H97-HD3 dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1427264] Re: using ecryptfs, creating frameworks fail to bind mount issues
I have same error on Ubuntu 14.04 with ecryptfs. Change or comment /home in /etc/schroot/click/fstab does not take effect. Switching from kernel 3.19.0-29-generic to 3.16.0-50-generic or 3.13.0-64-generic solved the problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1427264 Title: using ecryptfs, creating frameworks fail to bind mount issues Status in click package in Ubuntu: Triaged Status in schroot package in Ubuntu: In Progress Status in schroot package in Debian: Confirmed Bug description: Using vivid creating framework fails for ecryptfs users, the issue is similar to bug #769595 The userdir is mounted in a way which makes unmounts fail "E: 10mount: umount: /var/lib/schroot/mount/click-ubuntu-sdk-14.10 -armhf-ec6aaf62-31e0-47e9-b2f8-73f0b038fb4d/home/user: target is busy E: 10mount: (In some cases useful info about processes that E: 10mount: use the device is found by lsof(8) or fuser(1).) " changing the fstab line to be "/home/user /home/user none rw,bind0 0" workarounds the issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1427264/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1494119] Re: Audio Issues Across Multiple Applications
post output of alsa-info.sh turn off IEC958 Default PCM so that pulseaudio can set to use alc1500 digital and your application can use alc1500 analog exclusively Simple mixer control 'IEC958 Default PCM',0 Capabilities: pswitch pswitch-joined Playback channels: Mono Mono: Playback [off] -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1494119 Title: Audio Issues Across Multiple Applications Status in pulseaudio package in Ubuntu: Incomplete Bug description: Ubuntu 15.04 Multiple packages (tested Audacity, Openshot, Kdenlive, and LMMS) I'm having trouble working with any kind of software that mandates audio editing (Audacity, Openshot, Kdenlive, etc.) Since upgrading to Ubuntu 15.04, I've been running into issues with a lot of the audio editing software that I've been using. Audacity has the issue of the seek speeding through the entirety of the audio file while emitting a static buzzing sound. The same thing happens on LMMS. On video editors that I've been working with, Openshot and Kdenlive, any audio file I put in is played out of sync to the point that the file is truncated early towards the end of the clip. I've also tested this on Unity and Plasma, so I know it isn't the desktop environment impacting anything. I have no clue what software package could be causing this, but I have a feeling it's likely something on Pulseaudio's end. It's likely a Pulseaudio issue because all of the issues in these packages have to do with audio and they all rely on Pulseaudio. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1494119/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1495258] [NEW] systemd-journald crashed with SIGABRT in __epoll_wait_nocancel()
Public bug reported: Occurs only on QEMU-based virtual machine. ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: systemd 225-1ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic x86_64 ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Sun Sep 13 08:41:07 2015 ExecutablePath: /lib/systemd/systemd-journald InstallationDate: Installed on 2015-03-25 (171 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150324) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcCmdline: /lib/systemd/systemd-journald ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-7-generic root=UUID=fc32a548-00cf-4d7f-8204-2080bfaf0ebc ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: systemd StacktraceTop: __epoll_wait_nocancel () at ../sysdeps/unix/syscall-template.S:81 ?? () ?? () __libc_start_main (main=0x5652314f8440, argc=1, argv=0x7ffc1cbb79e8, init=, fini=, rtld_fini=, stack_end=0x7ffc1cbb79d8) at libc-start.c:289 ?? () Title: systemd-journald crashed with SIGABRT in __epoll_wait_nocancel() UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.7.5-20150306_163512-brownie dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-utopic dmi.modalias: dmi:bvnSeaBIOS:bvr1.7.5-20150306_163512-brownie:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-utopic:cvnQEMU:ct1:cvrpc-i440fx-utopic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-utopic dmi.sys.vendor: QEMU ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash need-amd64-retrace wily ** Information type changed from Private to Public -- 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/1495258 Title: systemd-journald crashed with SIGABRT in __epoll_wait_nocancel() Status in systemd package in Ubuntu: New Bug description: Occurs only on QEMU-based virtual machine. ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: systemd 225-1ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic x86_64 ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Sun Sep 13 08:41:07 2015 ExecutablePath: /lib/systemd/systemd-journald InstallationDate: Installed on 2015-03-25 (171 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150324) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcCmdline: /lib/systemd/systemd-journald ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-7-generic root=UUID=fc32a548-00cf-4d7f-8204-2080bfaf0ebc ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: systemd StacktraceTop: __epoll_wait_nocancel () at ../sysdeps/unix/syscall-template.S:81 ?? () ?? () __libc_start_main (main=0x5652314f8440, argc=1, argv=0x7ffc1cbb79e8, init=, fini=, rtld_fini=, stack_end=0x7ffc1cbb79d8) at libc-start.c:289 ?? () Title: systemd-journald crashed with SIGABRT in __epoll_wait_nocancel() UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.7.5-20150306_163512-brownie dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-utopic dmi.modalias: dmi:bvnSeaBIOS:bvr1.7.5-20150306_163512-brownie:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-utopic:cvnQEMU:ct1:cvrpc-i440fx-utopic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-utopic dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1495258/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1369293] Re: The desktop will not shrink back to one monitor when an external monitor is detached if system settings is not running
I'm seeing this behaviour in Ubuntu 15.10/Unity 7.3.2 -- 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/1369293 Title: The desktop will not shrink back to one monitor when an external monitor is detached if system settings is not running Status in Unity: New Status in unity package in Ubuntu: Confirmed Bug description: When an external HDMI monitor is attached, the desktop is automatically extended to it. But when the same monitor is detached, the desktop will not automatically shrink back to one monitor. How ever if the system settings program is running while monitor is detached, the desktop does shrink back to one monitor correctly. The desktop will also shrink back, if the systems settings is run at any time after detaching the monitor. Using Ubuntu 14.04.1 LTS ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Sep 14 20:16:17 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:5024] InstallationDate: Installed on 2014-05-07 (130 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: LENOVO 80B6QB0 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic.efi.signed root=UUID=ced59d53-14ee-475e-a6d9-544cd0928b7e ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/07/2013 dmi.bios.vendor: LENOVO dmi.bios.version: J7ET57WW (2.02 ) dmi.board.asset.tag: Not Available dmi.board.name: 80B6QB0 dmi.board.vendor: LENOVO dmi.board.version: 31900058 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrJ7ET57WW(2.02):bd11/07/2013:svnLENOVO:pn80B6QB0:pvrB5400:rvnLENOVO:rn80B6QB0:rvr31900058STD:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 80B6QB0 dmi.product.version: B5400 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sat Sep 13 18:25:51 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 13394 vendor SDC xserver.version: 2:1.15.1-0ubuntu2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1369293/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1369293] Re: The desktop will not shrink back to one monitor when an external monitor is detached if system settings is not running
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/1369293 Title: The desktop will not shrink back to one monitor when an external monitor is detached if system settings is not running Status in Unity: New Status in unity package in Ubuntu: Confirmed Bug description: When an external HDMI monitor is attached, the desktop is automatically extended to it. But when the same monitor is detached, the desktop will not automatically shrink back to one monitor. How ever if the system settings program is running while monitor is detached, the desktop does shrink back to one monitor correctly. The desktop will also shrink back, if the systems settings is run at any time after detaching the monitor. Using Ubuntu 14.04.1 LTS ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Sep 14 20:16:17 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:5024] InstallationDate: Installed on 2014-05-07 (130 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: LENOVO 80B6QB0 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic.efi.signed root=UUID=ced59d53-14ee-475e-a6d9-544cd0928b7e ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/07/2013 dmi.bios.vendor: LENOVO dmi.bios.version: J7ET57WW (2.02 ) dmi.board.asset.tag: Not Available dmi.board.name: 80B6QB0 dmi.board.vendor: LENOVO dmi.board.version: 31900058 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrJ7ET57WW(2.02):bd11/07/2013:svnLENOVO:pn80B6QB0:pvrB5400:rvnLENOVO:rn80B6QB0:rvr31900058STD:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 80B6QB0 dmi.product.version: B5400 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sat Sep 13 18:25:51 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 13394 vendor SDC xserver.version: 2:1.15.1-0ubuntu2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1369293/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1490258] Re: It's difficult to answer a call on arale
On my phone I can't accept the call at all! It seems the indicator has a too small touch sensitive area that I can't find in time. This problem is present in other buttons as well, like the send button in Telegram the restart button (after pressing the power button) This is on MX4 with OTA6 -- 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/1490258 Title: It's difficult to answer a call on arale Status in Ubuntu UX: New Status in dialer-app package in Ubuntu: Confirmed Bug description: The indicator to answer a call is at the top of the phone. On large screen, as the MX4, it's difficult to answer to a call using only one hand. Probably there could be improvements, like moving the indicator to the bottom. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1490258/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1495206] Re: System slow on dual-monitor
It turns out it was another issue - the laptop was slow when using a particular charger. I mistakenly assumed it had to do with lightdm because when I disconnected the external screen I disconnected the laptop charger too. ** Changed in: lightdm (Ubuntu) Status: New => Invalid -- 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/1495206 Title: System slow on dual-monitor Status in lightdm package in Ubuntu: Invalid Bug description: I connected to my laptop an external monitor (Dell P2314H) via HDMI and since than then the system is extremely slow, but only when the external display is connected. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.5-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-64.104-generic 3.13.11-ckt26 Uname: Linux 3.13.0-64-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.13 Architecture: amd64 CurrentDesktop: Unity Date: Sun Sep 13 13:17:56 2015 InstallationDate: Installed on 2015-06-03 (102 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1495206/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1495261] [NEW] systemd-logind crashed with SIGABRT in __epoll_wait_nocancel()
Public bug reported: Occurs only on QEMU-based virtual machine. ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: systemd 225-1ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic x86_64 ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Sat Sep 12 12:18:44 2015 ExecutablePath: /lib/systemd/systemd-logind ExecutableTimestamp: 1441816014 InstallationDate: Installed on 2015-03-25 (171 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150324) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcCmdline: /lib/systemd/systemd-logind ProcCwd: / ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-7-generic root=UUID=fc32a548-00cf-4d7f-8204-2080bfaf0ebc ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: systemd StacktraceTop: __epoll_wait_nocancel () at ../sysdeps/unix/syscall-template.S:81 ?? () ?? () __libc_start_main (main=0x55d738326030, argc=1, argv=0x7ffea015ded8, init=, fini=, rtld_fini=, stack_end=0x7ffea015dec8) at libc-start.c:289 ?? () Title: systemd-logind crashed with SIGABRT in __epoll_wait_nocancel() UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.7.5-20150306_163512-brownie dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-utopic dmi.modalias: dmi:bvnSeaBIOS:bvr1.7.5-20150306_163512-brownie:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-utopic:cvnQEMU:ct1:cvrpc-i440fx-utopic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-utopic dmi.sys.vendor: QEMU ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash need-amd64-retrace wily ** Information type changed from Private to Public -- 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/1495261 Title: systemd-logind crashed with SIGABRT in __epoll_wait_nocancel() Status in systemd package in Ubuntu: New Bug description: Occurs only on QEMU-based virtual machine. ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: systemd 225-1ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic x86_64 ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Sat Sep 12 12:18:44 2015 ExecutablePath: /lib/systemd/systemd-logind ExecutableTimestamp: 1441816014 InstallationDate: Installed on 2015-03-25 (171 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150324) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcCmdline: /lib/systemd/systemd-logind ProcCwd: / ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-7-generic root=UUID=fc32a548-00cf-4d7f-8204-2080bfaf0ebc ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: systemd StacktraceTop: __epoll_wait_nocancel () at ../sysdeps/unix/syscall-template.S:81 ?? () ?? () __libc_start_main (main=0x55d738326030, argc=1, argv=0x7ffea015ded8, init=, fini=, rtld_fini=, stack_end=0x7ffea015dec8) at libc-start.c:289 ?? () Title: systemd-logind crashed with SIGABRT in __epoll_wait_nocancel() UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.7.5-20150306_163512-brownie dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-utopic dmi.modalias: dmi:bvnSeaBIOS:bvr1.7.5-20150306_163512-brownie:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-utopic:cvnQEMU:ct1:cvrpc-i440fx-utopic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-utopic dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1495261/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1495260] [NEW] systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel()
Public bug reported: Occurs only on QEMU-based virtual machine. ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: udev 225-1ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic x86_64 ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 CrashCounter: 1 CustomUdevRuleFiles: 80-net-setup-link.rules Date: Sat Sep 12 23:39:00 2015 ExecutablePath: /lib/systemd/systemd-udevd ExecutableTimestamp: 1441816017 InstallationDate: Installed on 2015-03-25 (171 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150324) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcCmdline: /lib/systemd/systemd-udevd ProcCwd: / ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-7-generic root=UUID=fc32a548-00cf-4d7f-8204-2080bfaf0ebc ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: systemd StacktraceTop: __epoll_wait_nocancel () at ../sysdeps/unix/syscall-template.S:81 ?? () ?? () ?? () __libc_start_main (main=0x56419c4c1870, argc=1, argv=0x7ffcd70edec8, init=, fini=, rtld_fini=, stack_end=0x7ffcd70edeb8) at libc-start.c:289 Title: systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel() UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.7.5-20150306_163512-brownie dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-utopic dmi.modalias: dmi:bvnSeaBIOS:bvr1.7.5-20150306_163512-brownie:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-utopic:cvnQEMU:ct1:cvrpc-i440fx-utopic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-utopic dmi.sys.vendor: QEMU ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash need-amd64-retrace wily ** Information type changed from Private to Public -- 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/1495260 Title: systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel() Status in systemd package in Ubuntu: New Bug description: Occurs only on QEMU-based virtual machine. ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: udev 225-1ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic x86_64 ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 CrashCounter: 1 CustomUdevRuleFiles: 80-net-setup-link.rules Date: Sat Sep 12 23:39:00 2015 ExecutablePath: /lib/systemd/systemd-udevd ExecutableTimestamp: 1441816017 InstallationDate: Installed on 2015-03-25 (171 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150324) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcCmdline: /lib/systemd/systemd-udevd ProcCwd: / ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-7-generic root=UUID=fc32a548-00cf-4d7f-8204-2080bfaf0ebc ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: systemd StacktraceTop: __epoll_wait_nocancel () at ../sysdeps/unix/syscall-template.S:81 ?? () ?? () ?? () __libc_start_main (main=0x56419c4c1870, argc=1, argv=0x7ffcd70edec8, init=, fini=, rtld_fini=, stack_end=0x7ffcd70edeb8) at libc-start.c:289 Title: systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel() UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.7.5-20150306_163512-brownie dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-utopic dmi.modalias: dmi:bvnSeaBIOS:bvr1.7.5-20150306_163512-brownie:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-utopic:cvnQEMU:ct1:cvrpc-i440fx-utopic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-utopic dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1495260/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1495262] [NEW] systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel()
Public bug reported: Occurs only on QEMU-based virtual machine. ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: udev 225-1ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic x86_64 ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 CrashCounter: 1 CustomUdevRuleFiles: 80-net-setup-link.rules Date: Sat Sep 12 23:39:00 2015 ExecutablePath: /lib/systemd/systemd-udevd InstallationDate: Installed on 2015-03-25 (171 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150324) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcCmdline: /lib/systemd/systemd-udevd ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-7-generic root=UUID=fc32a548-00cf-4d7f-8204-2080bfaf0ebc ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: systemd StacktraceTop: __epoll_wait_nocancel () at ../sysdeps/unix/syscall-template.S:81 ?? () ?? () ?? () __libc_start_main (main=0x56419c4c1870, argc=1, argv=0x7ffcd70edec8, init=, fini=, rtld_fini=, stack_end=0x7ffcd70edeb8) at libc-start.c:289 Title: systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel() UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.7.5-20150306_163512-brownie dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-utopic dmi.modalias: dmi:bvnSeaBIOS:bvr1.7.5-20150306_163512-brownie:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-utopic:cvnQEMU:ct1:cvrpc-i440fx-utopic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-utopic dmi.sys.vendor: QEMU ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash need-amd64-retrace wily ** Information type changed from Private to Public -- 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/1495262 Title: systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel() Status in systemd package in Ubuntu: New Bug description: Occurs only on QEMU-based virtual machine. ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: udev 225-1ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic x86_64 ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 CrashCounter: 1 CustomUdevRuleFiles: 80-net-setup-link.rules Date: Sat Sep 12 23:39:00 2015 ExecutablePath: /lib/systemd/systemd-udevd InstallationDate: Installed on 2015-03-25 (171 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150324) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcCmdline: /lib/systemd/systemd-udevd ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-7-generic root=UUID=fc32a548-00cf-4d7f-8204-2080bfaf0ebc ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: systemd StacktraceTop: __epoll_wait_nocancel () at ../sysdeps/unix/syscall-template.S:81 ?? () ?? () ?? () __libc_start_main (main=0x56419c4c1870, argc=1, argv=0x7ffcd70edec8, init=, fini=, rtld_fini=, stack_end=0x7ffcd70edeb8) at libc-start.c:289 Title: systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel() UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.7.5-20150306_163512-brownie dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-utopic dmi.modalias: dmi:bvnSeaBIOS:bvr1.7.5-20150306_163512-brownie:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-utopic:cvnQEMU:ct1:cvrpc-i440fx-utopic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-utopic dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1495262/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 86433] Re: [apport] apt-cache crashed with SIGSEGV in strlen()
I got this error by regular "sudo apt-get install " sentence. Ubuntu 15.10. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/86433 Title: [apport] apt-cache crashed with SIGSEGV in strlen() Status in apt package in Ubuntu: Invalid Bug description: Binary package hint: apt I was using zsh completion and had typed sagi molly-g[tab] sagi is an alias for sudo apt-get install. ProblemType: Crash Date: Tue Feb 20 18:10:02 2007 DistroRelease: Ubuntu 7.04 ExecutablePath: /usr/bin/apt-cache Package: apt 0.6.46.4ubuntu7 ProcCmdline: apt-cache --generate pkgnames ProcCwd: /home/mbp/bzr/Work/tags ProcEnviron: PATH=/home/mbp/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/sbin:/sbin:/usr/sbin LANG=en_AU.UTF-8 SHELL=/bin/zsh Signal: 11 SourcePackage: apt StacktraceTop: strlen () from /lib/tls/i686/cmov/libc.so.6 ?? () CommandLine::DispatchArg () ?? () __libc_start_main () from /lib/tls/i686/cmov/libc.so.6 Uname: Linux kapu 2.6.20-8-generic #2 SMP Tue Feb 13 05:18:42 UTC 2007 i686 GNU/Linux UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/86433/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1495263] [NEW] systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel()
Public bug reported: Occurs only on QEMU-based virtual machine. ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: udev 225-1ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic x86_64 ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 CrashCounter: 1 CustomUdevRuleFiles: 80-net-setup-link.rules Date: Sat Sep 12 23:39:00 2015 ExecutablePath: /lib/systemd/systemd-udevd ExecutableTimestamp: 1441816017 InstallationDate: Installed on 2015-03-25 (171 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150324) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcCmdline: /lib/systemd/systemd-udevd ProcCwd: / ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-7-generic root=UUID=fc32a548-00cf-4d7f-8204-2080bfaf0ebc ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: systemd StacktraceTop: __epoll_wait_nocancel () at ../sysdeps/unix/syscall-template.S:81 ?? () ?? () ?? () __libc_start_main (main=0x56419c4c1870, argc=1, argv=0x7ffcd70edec8, init=, fini=, rtld_fini=, stack_end=0x7ffcd70edeb8) at libc-start.c:289 Title: systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel() UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.7.5-20150306_163512-brownie dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-utopic dmi.modalias: dmi:bvnSeaBIOS:bvr1.7.5-20150306_163512-brownie:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-utopic:cvnQEMU:ct1:cvrpc-i440fx-utopic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-utopic dmi.sys.vendor: QEMU ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash need-amd64-retrace wily ** Information type changed from Private to Public -- 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/1495263 Title: systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel() Status in systemd package in Ubuntu: New Bug description: Occurs only on QEMU-based virtual machine. ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: udev 225-1ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic x86_64 ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 CrashCounter: 1 CustomUdevRuleFiles: 80-net-setup-link.rules Date: Sat Sep 12 23:39:00 2015 ExecutablePath: /lib/systemd/systemd-udevd ExecutableTimestamp: 1441816017 InstallationDate: Installed on 2015-03-25 (171 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150324) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcCmdline: /lib/systemd/systemd-udevd ProcCwd: / ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-7-generic root=UUID=fc32a548-00cf-4d7f-8204-2080bfaf0ebc ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: systemd StacktraceTop: __epoll_wait_nocancel () at ../sysdeps/unix/syscall-template.S:81 ?? () ?? () ?? () __libc_start_main (main=0x56419c4c1870, argc=1, argv=0x7ffcd70edec8, init=, fini=, rtld_fini=, stack_end=0x7ffcd70edeb8) at libc-start.c:289 Title: systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel() UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.7.5-20150306_163512-brownie dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-utopic dmi.modalias: dmi:bvnSeaBIOS:bvr1.7.5-20150306_163512-brownie:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-utopic:cvnQEMU:ct1:cvrpc-i440fx-utopic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-utopic dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1495263/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 893210] Re: [Dell OptiPlex GX620 - AD1981b, playback] No sound at all
I don't know Raymond. I just booted from ubuntu-12.04.5-desktop- amd64.iso, played a music file, opened alsamixer, and discovered that; changing Master M volume independently changed the internal speaker volume. In 14.04 Master M is muted by default, unmuting and raising the volume has no effect. -- 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/893210 Title: [Dell OptiPlex GX620 - AD1981b, playback] No sound at all Status in ALSA driver: Confirmed Status in alsa-driver package in Ubuntu: Incomplete Bug description: fresh install of ubuntu studio and updates but internal speakers do not play. dell optiplex gx620 love ya ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: alsa-base 1.0.24+dfsg-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6 Uname: Linux 3.0.0-13-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.23-0ubuntu4 Architecture: i386 Card0.Amixer.info: Card hw:0 'ICH7'/'Intel ICH7 with AD1981B at irq 23' Mixer name : 'Analog Devices AD1981B' Components : 'AC97a:41445374' Controls : 28 Simple ctrls : 20 Card1.Amixer.info: Card hw:1 'Device'/'C-Media Electronics Inc. USB Multimedia Audio Device at usb-:00:1d.7-4.1.4,' Mixer name : 'USB Mixer' Components : 'USB0d8c:0105' Controls : 13 Simple ctrls : 6 Date: Mon Nov 21 11:51:25 2011 InstallationMedia: Ubuntu-Studio 11.10 "Oneiric Ocelot" - Release i386 (20111011.1) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:ICH7 failed Symptom_Card: CM108 Audio Controller - USB Multimedia Audio Device Symptom_Type: No sound at all Title: [ICH4 - Intel ICH7, playback] No sound at all UpgradeStatus: Upgraded to oneiric on 2011-11-12 (8 days ago) dmi.bios.date: 11/30/2006 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0F8101 dmi.board.vendor: Dell Inc. dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0F8101:rvr:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex GX620 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/893210/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 590300] Re: RIdiculously misleading error message from passwd
** Tags added: bitesize
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shadow in Ubuntu.
https://bugs.launchpad.net/bugs/590300
Title:
RIdiculously misleading error message from passwd
Status in shadow package in Ubuntu:
Triaged
Bug description:
In Ubuntu server 10.04 LTS, I typed passwd to change my password and
accidentally typed the new password in response to the prompt for the
current password. Instead of saying "incorrect password" or something
equally reasonable, which would have caused me to smack my forehead
and do it right the next time, I got the insane response "passwd:
Authentication token manipulation error"! This caused me to go down a
rathole for fifteen minutes, reading many pages with many possible
reasons for this error, none of which were "you mistyped your original
password".
This is a real user-interface FAIL and is certainly a regression in
understandability. It's obviously been there for a while; 9.04 does
this, although I note that Hoary 5.04 (yes, I still have a machine
that old) says "passwd: Authentication failure" instead, which, while
still not exactly user-friendly, at least puts "authentication" and
"failure" -and nothing else- into the error to give people half a
clue that maybe they mistyped something. (It's still not an error
message users should see, compared to "incorrect password".) But the
current error message is so obfuscated ("token manipulation error"---
wtf is -that-?) that it's absolutely no help at all---either to a user
trying to figure out what's going on, -or- to Google, considering how
many other scenarios cause it to spit out that error message.
Yuck.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/590300/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1494591] Re: not translated lock screen statistic
** Package changed: update-notifier (Ubuntu) => unity8 (Ubuntu) -- 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/1494591 Title: not translated lock screen statistic Status in unity8 package in Ubuntu: New Bug description: Language set to hungarian. In the middle of the locked screen I turned off the statistics. Now it says: "No data sources available" This sentence need to be translated to hungarian. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1494591/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1493014] Re: passwd - usermod-typo in "usermod --help" text
** Tags added: bitesize packaging ** Project changed: ubuntu-translations => shadow (Ubuntu) ** Changed in: shadow (Ubuntu) Status: New => Triaged ** Changed in: shadow (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1493014 Title: passwd - usermod-typo in "usermod --help" text Status in shadow package in Ubuntu: Triaged Bug description: In passwd 1:4.1.5.1-1ubuntu4 usermod --help text contains 2x typo / misspelling: Text in package reads: -V, --del-subuids FIRST-LAST remvoe range of subordinate uids -W, --del-subgids FIRST-LAST remvoe range of subordinate gids Text in package SHOULD read: -V, --del-subuids FIRST-LAST remove range of subordinate uids -W, --del-subgids FIRST-LAST remove range of subordinate gids To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1493014/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1450960] Re: dev file system is mounted without noexec
** Patch added: "Patch for lxc on top of f08fee55a1f0ca62c2c97a2d2fd5ef1d7fbae8ee. Solves the issue on the host, /dev/.lxc" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1450960/+attachment/4463050/+files/lxc-noexec-host.patch -- 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/1450960 Title: dev file system is mounted without noexec Status in lxc package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Triaged Bug description: I just found that the /dev filesystem of most Ubuntu system is mounted without noexec, nosuid etc options. If you do everything to harden your system, and you are using squashfs as root file system (which is read-only), such auto-mounted devices can be a serious leak. This volume usually is quite small and for most folders only root has write access, so I don't know how much this bug is security relevant, but I think there is no reason to not change the mount options for /dev. And especially for LXC containers, I don't even know a workaround to fix it. STEPS TO REPRODUCE: me:~# cat >/dev/call-me.sh <<.e > #!/bin/sh > echo "I'm executable" > .e me:~# chmod +x /dev/call-me.sh me:~# /dev/call-me.sh I'm executable EXPECTED BEHAVIOUR me:~# /dev/call-me.sh -bash: /dev/call-me.sh: Permission denied WORKAROUND me:~# mount -oremount,noexec,nosuid /dev me:~# /dev/call-me.sh -bash: /dev/call-me.sh: Permission denied Unfortunately, this workaround doesn't work in LXC containers (where the same problem occurs) because of missing capabilities. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: udev 204-5ubuntu20.11 ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17 Uname: Linux 3.13.0-49-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 CurrentDesktop: XFCE CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied CustomUdevRuleFiles: 51-android.rules 60-vboxdrv.rules Date: Sat May 2 01:48:26 2015 MachineType: Gigabyte Technology Co., Ltd. H97-HD3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-49-generic root=/dev/mapper/vg_ssd-lv_system_trusty1404 ro SourcePackage: systemd UpgradeStatus: Upgraded to trusty on 2014-04-18 (378 days ago) dmi.bios.date: 06/26/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H97-HD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/26/2014:svnGigabyteTechnologyCo.,Ltd.:pnH97-HD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH97-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: H97-HD3 dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1495116] Re: booting with amd64 kernel and completely i386 userland is unstable during the system upstart
Soemthing to start with for catching the bug: I've removed the corresponding linux-image-extra package, and now the booting is stable. But I don't have the needed drivers for video (nouveau) and network then. (And possibly more.) So loading one of the drivers from -extra caused the crash. The plan would be to add the used drivers from -extra one by one (or to remove all but one), and locate the problem in one of the drivers. -- 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/1495116 Title: booting with amd64 kernel and completely i386 userland is unstable during the system upstart Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Status in udev package in Ubuntu: Incomplete Status in upstart package in Ubuntu: Incomplete Bug description: I wanted to run my 14.10 (Utopic) i386 system with the amd64 kernel, so I added that architecture and apt-get-installed the amd64 linux- image and linux-image-extra (I learned this was possible thanks to the advice at http://askubuntu.com/a/635774/19753 ). However, the system upstart procedure more often fails than not: it fails by rebooting the computer. (Only around 1 time of 4 is successful.) A limited system start is (probably, always) successful: either with init=/bin/bash parameter to the kernel, or choosing the recovery boot option. (However, if I "resume" from the recovery menu, or run "exec init" in bash, then the upstart procedure is similarly unstable: it usually fails/crashes and reboots.) I checked my suspection that the video driver (nouveau) and X might be involved, but that turned out not true: the upstart procedure is similarly unstable with "nomodesetting" kernel parameter and without, booting into runlevel 3 or the default one. Perhaps, I'd like to debug the upstart procedure step-by-step to detect which step makes the system crash and reboot, but I don't know how. As concerns the timing, the moment the reboot happens can be different: it can happen rather early (when I see the message about activating the swap) or much later. If the system upstart procedure has completed successfully, then it works in a quite stable manner and doesn't crash/reboot. So, there is something bad specifically during the system upstart procedure. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: upstart 1.13.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14 Uname: Linux 3.16.0-44-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.5 Architecture: i386 CurrentDesktop: Unity Date: Sat Sep 12 18:36:28 2015 InstallationDate: Installed on 2014-06-04 (464 days ago) InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 (20140204) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash SourcePackage: upstart UpgradeStatus: Upgraded to utopic on 2015-09-11 (0 days ago) UpstartBugCategory: System UpstartRunningSessionVersion: upstart 1.13.2 UpstartRunningSystemVersion: init (upstart 1.13.2) modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Отказано в доступе: '/etc/at.deny'] modified.conffile..etc.cron.daily.upstart: [modified] modified.conffile..etc.cups.cups.browsed.conf: [modified] modified.conffile..etc.default.apport: [modified] modified.conffile..etc.default.cups: [modified] modified.conffile..etc.init.d.binfmt.support: [modified] mtime.conffile..etc.X11.Xsession.d.99upstart: 2014-09-30T12:21:08 mtime.conffile..etc.cron.daily.upstart: 2014-09-30T12:27:13 mtime.conffile..etc.cups.cups.browsed.conf: 2015-09-06T09:29:16.410097 mtime.conffile..etc.default.apport: 2014-06-05T12:49:10.316398 mtime.conffile..etc.default.cups: 2015-09-06T09:20:49.891585 mtime.conffile..etc.init.d.binfmt.support: 2014-09-30T12:21:08 mtime.conffile..etc.upstart.xsessions: 2014-09-30T12:21:08 --- ApportVersion: 2.14.7-0ubuntu8.5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marsmorgana 1972 F pulseaudio CRDA: country RU: DFS-UNSET (2402 - 2482 @ 40), (N/A, 20) (5735 - 5835 @ 20), (N/A, 30) CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=9267c811-3a01-4484-b968-c08582280d81 InstallationDate: Installed on 2014-06-04 (464 days ago) InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 (20140204) MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510 Package: upstart 1.13.2-0ubuntu2 PackageArchitecture: i386 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic
[Touch-packages] [Bug 1495116] Re: booting with amd64 kernel and completely i386 userland is unstable during the system upstart
Hi dino99, I've upgraded to 15.04 (Vivid) and am testing it there (as reflected in my posts here). My goal is not multiarch libs/apps. I must not not need them really in my config: they should stay i386. Only the kernel is amd64. There are a lot of reports of doing this successfully in various distros on the web... And the fact that if the system passed the booting procedure, it is a stable working system, gives me some encouragement in trying to catch this bug somewhere in the base system (kernel+systemd+udev). -- 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/1495116 Title: booting with amd64 kernel and completely i386 userland is unstable during the system upstart Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Status in udev package in Ubuntu: Incomplete Status in upstart package in Ubuntu: Incomplete Bug description: I wanted to run my 14.10 (Utopic) i386 system with the amd64 kernel, so I added that architecture and apt-get-installed the amd64 linux- image and linux-image-extra (I learned this was possible thanks to the advice at http://askubuntu.com/a/635774/19753 ). However, the system upstart procedure more often fails than not: it fails by rebooting the computer. (Only around 1 time of 4 is successful.) A limited system start is (probably, always) successful: either with init=/bin/bash parameter to the kernel, or choosing the recovery boot option. (However, if I "resume" from the recovery menu, or run "exec init" in bash, then the upstart procedure is similarly unstable: it usually fails/crashes and reboots.) I checked my suspection that the video driver (nouveau) and X might be involved, but that turned out not true: the upstart procedure is similarly unstable with "nomodesetting" kernel parameter and without, booting into runlevel 3 or the default one. Perhaps, I'd like to debug the upstart procedure step-by-step to detect which step makes the system crash and reboot, but I don't know how. As concerns the timing, the moment the reboot happens can be different: it can happen rather early (when I see the message about activating the swap) or much later. If the system upstart procedure has completed successfully, then it works in a quite stable manner and doesn't crash/reboot. So, there is something bad specifically during the system upstart procedure. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: upstart 1.13.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14 Uname: Linux 3.16.0-44-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.5 Architecture: i386 CurrentDesktop: Unity Date: Sat Sep 12 18:36:28 2015 InstallationDate: Installed on 2014-06-04 (464 days ago) InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 (20140204) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash SourcePackage: upstart UpgradeStatus: Upgraded to utopic on 2015-09-11 (0 days ago) UpstartBugCategory: System UpstartRunningSessionVersion: upstart 1.13.2 UpstartRunningSystemVersion: init (upstart 1.13.2) modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Отказано в доступе: '/etc/at.deny'] modified.conffile..etc.cron.daily.upstart: [modified] modified.conffile..etc.cups.cups.browsed.conf: [modified] modified.conffile..etc.default.apport: [modified] modified.conffile..etc.default.cups: [modified] modified.conffile..etc.init.d.binfmt.support: [modified] mtime.conffile..etc.X11.Xsession.d.99upstart: 2014-09-30T12:21:08 mtime.conffile..etc.cron.daily.upstart: 2014-09-30T12:27:13 mtime.conffile..etc.cups.cups.browsed.conf: 2015-09-06T09:29:16.410097 mtime.conffile..etc.default.apport: 2014-06-05T12:49:10.316398 mtime.conffile..etc.default.cups: 2015-09-06T09:20:49.891585 mtime.conffile..etc.init.d.binfmt.support: 2014-09-30T12:21:08 mtime.conffile..etc.upstart.xsessions: 2014-09-30T12:21:08 --- ApportVersion: 2.14.7-0ubuntu8.5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marsmorgana 1972 F pulseaudio CRDA: country RU: DFS-UNSET (2402 - 2482 @ 40), (N/A, 20) (5735 - 5835 @ 20), (N/A, 30) CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=9267c811-3a01-4484-b968-c08582280d81 InstallationDate: Installed on 2014-06-04 (464 days ago) InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 (20140204) MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510 Package: upstart 1.13.2-0ubuntu2 PackageArchitecture: i386 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
[Touch-packages] [Bug 1495256] [NEW] There is no option to disable history in webbrowser-app (15.04)
Public bug reported: An option should be available which turns off recording history of pages visited. ** Affects: webbrowser-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 webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1495256 Title: There is no option to disable history in webbrowser-app (15.04) Status in webbrowser-app package in Ubuntu: New Bug description: An option should be available which turns off recording history of pages visited. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1495256/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1493014] [NEW] passwd - usermod-typo in "usermod --help" text
You have been subscribed to a public bug: In passwd 1:4.1.5.1-1ubuntu4 usermod --help text contains 2x typo / misspelling: Text in package reads: -V, --del-subuids FIRST-LAST remvoe range of subordinate uids -W, --del-subgids FIRST-LAST remvoe range of subordinate gids Text in package SHOULD read: -V, --del-subuids FIRST-LAST remove range of subordinate uids -W, --del-subgids FIRST-LAST remove range of subordinate gids ** Affects: shadow (Ubuntu) Importance: Undecided Status: New ** Tags: bitesize packaging -- passwd - usermod-typo in "usermod --help" text https://bugs.launchpad.net/bugs/1493014 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow 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 893210] Re: [Dell OptiPlex GX620 - AD1981b, playback] No sound at all
24 OUT (0) OUT (0) 1 1 0 FMUTE FMUTE ACTIVE JS0 mutes Mono; JS1 mutes Mono and Line-Out. 25 OUT (0) IN (1) 1 1 0 FMUTE ACTIVE FMUTE 26 IN (1) OUT (0) 1 1 0 ACTIVE FMUTE FMUTE 27 IN (1) IN (1) 1 1 0 ACTIVE FMUTE FMUTE the other thing is that you have change mute enable selector to 110 which mute mono when you have line out or hp plugged -- 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/893210 Title: [Dell OptiPlex GX620 - AD1981b, playback] No sound at all Status in ALSA driver: Confirmed Status in alsa-driver package in Ubuntu: Incomplete Bug description: fresh install of ubuntu studio and updates but internal speakers do not play. dell optiplex gx620 love ya ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: alsa-base 1.0.24+dfsg-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6 Uname: Linux 3.0.0-13-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.23-0ubuntu4 Architecture: i386 Card0.Amixer.info: Card hw:0 'ICH7'/'Intel ICH7 with AD1981B at irq 23' Mixer name : 'Analog Devices AD1981B' Components : 'AC97a:41445374' Controls : 28 Simple ctrls : 20 Card1.Amixer.info: Card hw:1 'Device'/'C-Media Electronics Inc. USB Multimedia Audio Device at usb-:00:1d.7-4.1.4,' Mixer name : 'USB Mixer' Components : 'USB0d8c:0105' Controls : 13 Simple ctrls : 6 Date: Mon Nov 21 11:51:25 2011 InstallationMedia: Ubuntu-Studio 11.10 "Oneiric Ocelot" - Release i386 (20111011.1) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:ICH7 failed Symptom_Card: CM108 Audio Controller - USB Multimedia Audio Device Symptom_Type: No sound at all Title: [ICH4 - Intel ICH7, playback] No sound at all UpgradeStatus: Upgraded to oneiric on 2011-11-12 (8 days ago) dmi.bios.date: 11/30/2006 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0F8101 dmi.board.vendor: Dell Inc. dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0F8101:rvr:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex GX620 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/893210/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1438412] Re: tst_ScriptMessageRouting_no_match.qml random test failure
** Changed in: oxide
Milestone: branch-1.10 => None
--
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/1438412
Title:
tst_ScriptMessageRouting_no_match.qml random test failure
Status in Oxide:
Triaged
Status in webbrowser-app:
Invalid
Status in webbrowser-app package in Ubuntu:
Confirmed
Bug description:
On trunk, I'm getting the following random test failure:
FAIL! :
qml-core-test::ScriptMessageRouting_direct::test_ScriptMessageRouting_no_match(row
1) Unexpected error type
Actual (): 5
Expected (): 3
Loc:
[/home/chr1s/src/oxide/class-hierarchy-cleanliness/qt/tests/qmltests/core/tst_ScriptMessageRouting_no_match.qml(44)]
The test is checking the response of the browser-side message routing
when there are no handlers available by sending a message to the frame
and having it loop back to the browser. When the browser returns an
error for the looped back message, the frame is then meant to reply to
the original request by sending the error code (which we expect to be
3 - ErrorNoHandler). In this case though, we're getting a genuine
error from the message transaction to the frame (5 -
ErrorHandlerDidNotRespond).
The content-side handler for this test that loops back to the browser
looks like this:
oxide.addMessageHandler("SEND-MESSAGE-TO-SELF", function(msg) {
var r = oxide.sendMessage(msg.args.id, msg.args.args);
r.onreply = function(response) {
msg.reply({error: 0, response: response});
};
r.onerror = function(error, desc) {
msg.reply({error: error, response: desc});
};
});
What happens is that when the handler has executed, "r" goes out of
scope and then sometimes gets garbage collected before we get a reply
or error from the browser. When it gets garbage collected, we
automatically send the "DidNotRespond" error to the message source in
the browser.
I'm amazed we've only just started hitting this.
This is likely to be an issue for existing consumers of Oxide, and
could affect the browser side too
To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1438412/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1495116] Re: booting with amd64 kernel and completely i386 userland is unstable during the system upstart
hi Ivan, you are testing an usual config here; but if i can mind you some details: - utopic has already reached EOL some times ago - even Wily has not yet a complete multiarch portage; so many libs/apps still need some work on that side. Of course Utopic status is even worst. I feel you are playing an old success : "mission impossible", and doubt devs will waste their precious time about such an experience on a deprecated release. ** Changed in: upstart (Ubuntu) Status: New => Incomplete ** Changed in: udev (Ubuntu) Status: New => Incomplete ** Changed in: systemd (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- 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/1495116 Title: booting with amd64 kernel and completely i386 userland is unstable during the system upstart Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Status in udev package in Ubuntu: Incomplete Status in upstart package in Ubuntu: Incomplete Bug description: I wanted to run my 14.10 (Utopic) i386 system with the amd64 kernel, so I added that architecture and apt-get-installed the amd64 linux- image and linux-image-extra (I learned this was possible thanks to the advice at http://askubuntu.com/a/635774/19753 ). However, the system upstart procedure more often fails than not: it fails by rebooting the computer. (Only around 1 time of 4 is successful.) A limited system start is (probably, always) successful: either with init=/bin/bash parameter to the kernel, or choosing the recovery boot option. (However, if I "resume" from the recovery menu, or run "exec init" in bash, then the upstart procedure is similarly unstable: it usually fails/crashes and reboots.) I checked my suspection that the video driver (nouveau) and X might be involved, but that turned out not true: the upstart procedure is similarly unstable with "nomodesetting" kernel parameter and without, booting into runlevel 3 or the default one. Perhaps, I'd like to debug the upstart procedure step-by-step to detect which step makes the system crash and reboot, but I don't know how. As concerns the timing, the moment the reboot happens can be different: it can happen rather early (when I see the message about activating the swap) or much later. If the system upstart procedure has completed successfully, then it works in a quite stable manner and doesn't crash/reboot. So, there is something bad specifically during the system upstart procedure. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: upstart 1.13.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14 Uname: Linux 3.16.0-44-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.5 Architecture: i386 CurrentDesktop: Unity Date: Sat Sep 12 18:36:28 2015 InstallationDate: Installed on 2014-06-04 (464 days ago) InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 (20140204) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash SourcePackage: upstart UpgradeStatus: Upgraded to utopic on 2015-09-11 (0 days ago) UpstartBugCategory: System UpstartRunningSessionVersion: upstart 1.13.2 UpstartRunningSystemVersion: init (upstart 1.13.2) modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Отказано в доступе: '/etc/at.deny'] modified.conffile..etc.cron.daily.upstart: [modified] modified.conffile..etc.cups.cups.browsed.conf: [modified] modified.conffile..etc.default.apport: [modified] modified.conffile..etc.default.cups: [modified] modified.conffile..etc.init.d.binfmt.support: [modified] mtime.conffile..etc.X11.Xsession.d.99upstart: 2014-09-30T12:21:08 mtime.conffile..etc.cron.daily.upstart: 2014-09-30T12:27:13 mtime.conffile..etc.cups.cups.browsed.conf: 2015-09-06T09:29:16.410097 mtime.conffile..etc.default.apport: 2014-06-05T12:49:10.316398 mtime.conffile..etc.default.cups: 2015-09-06T09:20:49.891585 mtime.conffile..etc.init.d.binfmt.support: 2014-09-30T12:21:08 mtime.conffile..etc.upstart.xsessions: 2014-09-30T12:21:08 --- ApportVersion: 2.14.7-0ubuntu8.5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marsmorgana 1972 F pulseaudio CRDA: country RU: DFS-UNSET (2402 - 2482 @ 40), (N/A, 20) (5735 - 5835 @ 20), (N/A, 30) CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=9267c811-3a01-4484-b968-c08582280d81 InstallationDate: Installed on 2014-06-04 (464 days ago) InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 (20140204) MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510 Package: upstart 1.13.2-0ubuntu2
[Touch-packages] [Bug 1495259] [NEW] systemd-logind crashed with SIGABRT in __epoll_wait_nocancel()
Public bug reported: Occurs only on QEMU-based virtual machine. ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: systemd 225-1ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic x86_64 ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Sat Sep 12 12:18:44 2015 ExecutablePath: /lib/systemd/systemd-logind InstallationDate: Installed on 2015-03-25 (171 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150324) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcCmdline: /lib/systemd/systemd-logind ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-7-generic root=UUID=fc32a548-00cf-4d7f-8204-2080bfaf0ebc ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: systemd StacktraceTop: __epoll_wait_nocancel () at ../sysdeps/unix/syscall-template.S:81 ?? () ?? () __libc_start_main (main=0x55d738326030, argc=1, argv=0x7ffea015ded8, init=, fini=, rtld_fini=, stack_end=0x7ffea015dec8) at libc-start.c:289 ?? () Title: systemd-logind crashed with SIGABRT in __epoll_wait_nocancel() UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.7.5-20150306_163512-brownie dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-utopic dmi.modalias: dmi:bvnSeaBIOS:bvr1.7.5-20150306_163512-brownie:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-utopic:cvnQEMU:ct1:cvrpc-i440fx-utopic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-utopic dmi.sys.vendor: QEMU ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash need-amd64-retrace wily ** Information type changed from Private to Public -- 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/1495259 Title: systemd-logind crashed with SIGABRT in __epoll_wait_nocancel() Status in systemd package in Ubuntu: New Bug description: Occurs only on QEMU-based virtual machine. ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: systemd 225-1ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic x86_64 ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Sat Sep 12 12:18:44 2015 ExecutablePath: /lib/systemd/systemd-logind InstallationDate: Installed on 2015-03-25 (171 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150324) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcCmdline: /lib/systemd/systemd-logind ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-7-generic root=UUID=fc32a548-00cf-4d7f-8204-2080bfaf0ebc ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: systemd StacktraceTop: __epoll_wait_nocancel () at ../sysdeps/unix/syscall-template.S:81 ?? () ?? () __libc_start_main (main=0x55d738326030, argc=1, argv=0x7ffea015ded8, init=, fini=, rtld_fini=, stack_end=0x7ffea015dec8) at libc-start.c:289 ?? () Title: systemd-logind crashed with SIGABRT in __epoll_wait_nocancel() UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.7.5-20150306_163512-brownie dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-utopic dmi.modalias: dmi:bvnSeaBIOS:bvr1.7.5-20150306_163512-brownie:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-utopic:cvnQEMU:ct1:cvrpc-i440fx-utopic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-utopic dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1495259/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1483205] Re: unity-control-center needs bluetooth packages
** Tags added: packaging -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1483205 Title: unity-control-center needs bluetooth packages Status in indicator-bluetooth package in Ubuntu: New Status in unity-control-center package in Ubuntu: New Bug description: Hi, unity-control-center seems to require indicator-bluetooth which then pulls in a bunch of bluetooth packages. Any chance of updating it so bluetooth is optional? I don't have bluetooth enabled, and would prefer not to have bluetooth packages installed (indicator-bluetooth, bluez, indicator-bluetooth, gir1.2-gnomebluetooth-1.0, libbluetooth3, etc.) Thanks in advance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1483205/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1450960] Re: dev file system is mounted without noexec
** Patch added: "Patch for lxc on top of f08fee55a1f0ca62c2c97a2d2fd5ef1d7fbae8ee. Solves the issue in the container, NOT /dev/.lxc on the host" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1450960/+attachment/4463049/+files/lxc-noexec.patch -- 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/1450960 Title: dev file system is mounted without noexec Status in lxc package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Triaged Bug description: I just found that the /dev filesystem of most Ubuntu system is mounted without noexec, nosuid etc options. If you do everything to harden your system, and you are using squashfs as root file system (which is read-only), such auto-mounted devices can be a serious leak. This volume usually is quite small and for most folders only root has write access, so I don't know how much this bug is security relevant, but I think there is no reason to not change the mount options for /dev. And especially for LXC containers, I don't even know a workaround to fix it. STEPS TO REPRODUCE: me:~# cat >/dev/call-me.sh <<.e > #!/bin/sh > echo "I'm executable" > .e me:~# chmod +x /dev/call-me.sh me:~# /dev/call-me.sh I'm executable EXPECTED BEHAVIOUR me:~# /dev/call-me.sh -bash: /dev/call-me.sh: Permission denied WORKAROUND me:~# mount -oremount,noexec,nosuid /dev me:~# /dev/call-me.sh -bash: /dev/call-me.sh: Permission denied Unfortunately, this workaround doesn't work in LXC containers (where the same problem occurs) because of missing capabilities. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: udev 204-5ubuntu20.11 ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17 Uname: Linux 3.13.0-49-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 CurrentDesktop: XFCE CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied CustomUdevRuleFiles: 51-android.rules 60-vboxdrv.rules Date: Sat May 2 01:48:26 2015 MachineType: Gigabyte Technology Co., Ltd. H97-HD3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-49-generic root=/dev/mapper/vg_ssd-lv_system_trusty1404 ro SourcePackage: systemd UpgradeStatus: Upgraded to trusty on 2014-04-18 (378 days ago) dmi.bios.date: 06/26/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H97-HD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/26/2014:svnGigabyteTechnologyCo.,Ltd.:pnH97-HD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH97-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: H97-HD3 dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1494591] [NEW] not translated lock screen statistic
You have been subscribed to a public bug: Language set to hungarian. In the middle of the locked screen I turned off the statistics. Now it says: "No data sources available" This sentence need to be translated to hungarian. ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New -- not translated lock screen statistic https://bugs.launchpad.net/bugs/1494591 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 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 1441305] Re: Stuck with black screen on boot (no signal)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lightdm (Ubuntu) Status: New => Confirmed -- 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/1441305 Title: Stuck with black screen on boot (no signal) Status in lightdm package in Ubuntu: Confirmed Bug description: Recently, the following problem appeared suddenly: - Start computer - Ubuntu splash screen appears with dots - Screen turns black and switches off (no signal) This happened on every boot. Previously I had removed all but the latest kernel [linux-lts-trusty (3.13.0-48.80~precise1]), but this may be a coincidence because that kernel started without problems before. I could not even start my computer in recovery mode, as it hung after mounting additional HDDs (may be related or not). In the end I was able to start it in text mode by adding "nomodeset" to the GRUB boot options. Switching the display manager to gdm then fixed the problem for me. Note 1: My OS starts from an SSD. Note 2: My graphics card is recognised as Mobility Radeon HD 5430 Note 3: The same problem also appeared at the same time on Ubuntu 14.04 LTS 64 bit installed on a different SSD on the same computer. However, there the black screen only appears on every *first* boot. The second boot will be fine -> https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1443144 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: lightdm 1.2.3-0ubuntu2.7 ProcVersionSignature: Ubuntu 3.13.0-48.80~precise1-generic 3.13.11-ckt16 Uname: Linux 3.13.0-48-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.8 Architecture: amd64 Date: Tue Apr 7 20:43:44 2015 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130214) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1441305/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1495116] Re: booting with amd64 kernel and completely i386 userland is unstable during the system upstart
i suggest to upgrade to Wily as it might be easier As your experiment has catch my curiosity, i've searched around, and found some threads; they mainly said 'yes that should be possible, with lot of headaches' So good luck :) :) -- 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/1495116 Title: booting with amd64 kernel and completely i386 userland is unstable during the system upstart Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Status in udev package in Ubuntu: Incomplete Status in upstart package in Ubuntu: Incomplete Bug description: I wanted to run my 14.10 (Utopic) i386 system with the amd64 kernel, so I added that architecture and apt-get-installed the amd64 linux- image and linux-image-extra (I learned this was possible thanks to the advice at http://askubuntu.com/a/635774/19753 ). However, the system upstart procedure more often fails than not: it fails by rebooting the computer. (Only around 1 time of 4 is successful.) A limited system start is (probably, always) successful: either with init=/bin/bash parameter to the kernel, or choosing the recovery boot option. (However, if I "resume" from the recovery menu, or run "exec init" in bash, then the upstart procedure is similarly unstable: it usually fails/crashes and reboots.) I checked my suspection that the video driver (nouveau) and X might be involved, but that turned out not true: the upstart procedure is similarly unstable with "nomodesetting" kernel parameter and without, booting into runlevel 3 or the default one. Perhaps, I'd like to debug the upstart procedure step-by-step to detect which step makes the system crash and reboot, but I don't know how. As concerns the timing, the moment the reboot happens can be different: it can happen rather early (when I see the message about activating the swap) or much later. If the system upstart procedure has completed successfully, then it works in a quite stable manner and doesn't crash/reboot. So, there is something bad specifically during the system upstart procedure. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: upstart 1.13.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14 Uname: Linux 3.16.0-44-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.5 Architecture: i386 CurrentDesktop: Unity Date: Sat Sep 12 18:36:28 2015 InstallationDate: Installed on 2014-06-04 (464 days ago) InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 (20140204) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash SourcePackage: upstart UpgradeStatus: Upgraded to utopic on 2015-09-11 (0 days ago) UpstartBugCategory: System UpstartRunningSessionVersion: upstart 1.13.2 UpstartRunningSystemVersion: init (upstart 1.13.2) modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Отказано в доступе: '/etc/at.deny'] modified.conffile..etc.cron.daily.upstart: [modified] modified.conffile..etc.cups.cups.browsed.conf: [modified] modified.conffile..etc.default.apport: [modified] modified.conffile..etc.default.cups: [modified] modified.conffile..etc.init.d.binfmt.support: [modified] mtime.conffile..etc.X11.Xsession.d.99upstart: 2014-09-30T12:21:08 mtime.conffile..etc.cron.daily.upstart: 2014-09-30T12:27:13 mtime.conffile..etc.cups.cups.browsed.conf: 2015-09-06T09:29:16.410097 mtime.conffile..etc.default.apport: 2014-06-05T12:49:10.316398 mtime.conffile..etc.default.cups: 2015-09-06T09:20:49.891585 mtime.conffile..etc.init.d.binfmt.support: 2014-09-30T12:21:08 mtime.conffile..etc.upstart.xsessions: 2014-09-30T12:21:08 --- ApportVersion: 2.14.7-0ubuntu8.5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marsmorgana 1972 F pulseaudio CRDA: country RU: DFS-UNSET (2402 - 2482 @ 40), (N/A, 20) (5735 - 5835 @ 20), (N/A, 30) CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=9267c811-3a01-4484-b968-c08582280d81 InstallationDate: Installed on 2014-06-04 (464 days ago) InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 (20140204) MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510 Package: upstart 1.13.2-0ubuntu2 PackageArchitecture: i386 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14 RelatedPackageVersions: linux-restricted-modules-3.16.0-44-generic N/A
[Touch-packages] [Bug 1450960] Re: dev file system is mounted without noexec
The attachment "Patch for lxc on top of f08fee55a1f0ca62c2c97a2d2fd5ef1d7fbae8ee. Solves the issue in the container, NOT /dev/.lxc on the host" 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 lxc in Ubuntu. https://bugs.launchpad.net/bugs/1450960 Title: dev file system is mounted without noexec Status in lxc package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Triaged Bug description: I just found that the /dev filesystem of most Ubuntu system is mounted without noexec, nosuid etc options. If you do everything to harden your system, and you are using squashfs as root file system (which is read-only), such auto-mounted devices can be a serious leak. This volume usually is quite small and for most folders only root has write access, so I don't know how much this bug is security relevant, but I think there is no reason to not change the mount options for /dev. And especially for LXC containers, I don't even know a workaround to fix it. STEPS TO REPRODUCE: me:~# cat >/dev/call-me.sh <<.e > #!/bin/sh > echo "I'm executable" > .e me:~# chmod +x /dev/call-me.sh me:~# /dev/call-me.sh I'm executable EXPECTED BEHAVIOUR me:~# /dev/call-me.sh -bash: /dev/call-me.sh: Permission denied WORKAROUND me:~# mount -oremount,noexec,nosuid /dev me:~# /dev/call-me.sh -bash: /dev/call-me.sh: Permission denied Unfortunately, this workaround doesn't work in LXC containers (where the same problem occurs) because of missing capabilities. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: udev 204-5ubuntu20.11 ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17 Uname: Linux 3.13.0-49-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 CurrentDesktop: XFCE CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied CustomUdevRuleFiles: 51-android.rules 60-vboxdrv.rules Date: Sat May 2 01:48:26 2015 MachineType: Gigabyte Technology Co., Ltd. H97-HD3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-49-generic root=/dev/mapper/vg_ssd-lv_system_trusty1404 ro SourcePackage: systemd UpgradeStatus: Upgraded to trusty on 2014-04-18 (378 days ago) dmi.bios.date: 06/26/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H97-HD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/26/2014:svnGigabyteTechnologyCo.,Ltd.:pnH97-HD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH97-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: H97-HD3 dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1449225] Re: Backport #41309 ( 8b281f83e ) to fix use of uninitialized data.
** Changed in: freetype (Ubuntu Trusty) Assignee: lava (lavasanjay) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to freetype in Ubuntu. https://bugs.launchpad.net/bugs/1449225 Title: Backport #41309 ( 8b281f83e ) to fix use of uninitialized data. Status in freetype package in Ubuntu: Fix Released Status in freetype source package in Precise: Fix Released Status in freetype source package in Trusty: Fix Released Status in freetype source package in Utopic: Won't Fix Status in freetype source package in Vivid: Fix Released Status in freetype source package in Wily: Fix Released Bug description: FreeType issue https://savannah.nongnu.org/bugs/?41309 was fixed with http://git.savannah.gnu.org/cgit/freetype/freetype2.git/commit/?id=8b281f83e8516535756f92dbf90940ac44bd45e1 . This change is not in any of the current FreeType packages (Precise freetype 2.4.8-1ubuntu2.2 nor Trusty freetype 2.5.2-1ubuntu2.4 ). This is a fix for a few use of uninitialized data bugs which were found by msan, and is in FreeType 2.5.3 (but comes after 2.5.2). This is a request to backport http://git.savannah.gnu.org/cgit/freetype/freetype2.git/commit/?id=8b281f83e8516535756f92dbf90940ac44bd45e1 to all currently supported packages of FreeType, as all of them appear to be affected. Since this fixes reads of uninitialized memory in a widely used package, I'm marking this as a security related issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/1449225/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1495293] [NEW] Upon switching sound output device sound mutes
Public bug reported: So this is what happened, I just plugged in my headphones, and even though before when I was using the volume was up almost full, the volume went to mute, then I turned up the volume, and when I switched back to my normal speakers, the volume went to mute again! So it seems annoyingly that if I switch from one sound output device to the other, if I change the volume from the newly set mute to a different volume it automatically turns the other to mute (although randomly it does other things)... Now I'm also finding that if I turn the volume up, then switch and it goes to mute, if I then switch back without changing anything the volume goes to just above mute (but sometimes mute) on the one I am switching to. And I am seeing lots of other strange behaviour like this. I have attempted renaming the "~/.config/pulse" directory and then running "pulseaudio -k", but the problem still remains. Adapted from my AskUbuntu question: https://askubuntu.com/questions/673735/upon-switching-sound-output- device-sound-mutes --- OS Information: No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 15.04 Release:15.04 Codename: vivid Flavour: GNOME GNOME Version: 3.16 Package Information: pulseaudio: Installed: 1:6.0-0ubuntu6 Candidate: 1:6.0-0ubuntu6 Version table: *** 1:6.0-0ubuntu6 0 500 http://archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1495293 Title: Upon switching sound output device sound mutes Status in pulseaudio package in Ubuntu: New Bug description: So this is what happened, I just plugged in my headphones, and even though before when I was using the volume was up almost full, the volume went to mute, then I turned up the volume, and when I switched back to my normal speakers, the volume went to mute again! So it seems annoyingly that if I switch from one sound output device to the other, if I change the volume from the newly set mute to a different volume it automatically turns the other to mute (although randomly it does other things)... Now I'm also finding that if I turn the volume up, then switch and it goes to mute, if I then switch back without changing anything the volume goes to just above mute (but sometimes mute) on the one I am switching to. And I am seeing lots of other strange behaviour like this. I have attempted renaming the "~/.config/pulse" directory and then running "pulseaudio -k", but the problem still remains. Adapted from my AskUbuntu question: https://askubuntu.com/questions/673735/upon-switching-sound-output- device-sound-mutes --- OS Information: No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 15.04 Release: 15.04 Codename: vivid Flavour: GNOME GNOME Version: 3.16 Package Information: pulseaudio: Installed: 1:6.0-0ubuntu6 Candidate: 1:6.0-0ubuntu6 Version table: *** 1:6.0-0ubuntu6 0 500 http://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/pulseaudio/+bug/1495293/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1474539] Re: FTBFS with Python 3.5
libguestfs succeeds to build without changes. ** Changed in: libguestfs (Ubuntu Wily) Status: New => 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/1474539 Title: FTBFS with Python 3.5 Status in apport package in Ubuntu: Fix Released Status in blist package in Ubuntu: Fix Released Status in cigi-ccl package in Ubuntu: New Status in kubuntu-driver-manager package in Ubuntu: Fix Released Status in libguestfs package in Ubuntu: Fix Released Status in lives package in Ubuntu: New Status in shiboken package in Ubuntu: Fix Released Status in apport source package in Wily: Fix Released Status in blist source package in Wily: Fix Released Status in cigi-ccl source package in Wily: New Status in kubuntu-driver-manager source package in Wily: Fix Released Status in libguestfs source package in Wily: Fix Released Status in lives source package in Wily: New Status in shiboken source package in Wily: Fix Released Bug description: We're in the process of starting the Python 3.5 transition for Wily. As such, we've identified a number of packages which FTBFS with Python 3.5. We're also soon starting the transition to gcc5. These are the packages that FTBFS in both transitions. Here is a link to the Python 3.5 failure in the PPA: https://launchpadlibrarian.net/210474236/buildlog_ubuntu-wily- amd64.apport_2.17.3-0ubuntu4_BUILDING.txt.gz See also: https://launchpad.net/~pythoneers/+archive/ubuntu/py35asdefault/+packages?field.name_filter=apport_filter=published_filter= To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1474539/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1495297] [NEW] [regression] All options in the drawer menu always visible
Public bug reported: Since the landing of the UITK version 1.3.1627+15.04.20150908-0ubuntu1, all the options in the drawer menu are always visible, even those that shouldn’t be (those are disabled, but still visible). This breaks a couple of autopilot tests in the webbrowser-app test suite: webbrowser_app.tests.test_findinpage.TestFindInPage.test_find_in_page_not_in_menu_in_new_tab webbrowser_app.tests.test_private.TestPrivateView.test_going_in_and_out_private_mode ** Affects: webbrowser-app (Ubuntu) Importance: High Assignee: Olivier Tilloy (osomon) Status: In Progress -- 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/1495297 Title: [regression] All options in the drawer menu always visible Status in webbrowser-app package in Ubuntu: In Progress Bug description: Since the landing of the UITK version 1.3.1627+15.04.20150908-0ubuntu1, all the options in the drawer menu are always visible, even those that shouldn’t be (those are disabled, but still visible). This breaks a couple of autopilot tests in the webbrowser-app test suite: webbrowser_app.tests.test_findinpage.TestFindInPage.test_find_in_page_not_in_menu_in_new_tab webbrowser_app.tests.test_private.TestPrivateView.test_going_in_and_out_private_mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1495297/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 893210] Re: [Dell OptiPlex GX620 - AD1981b, playback] No sound at all
changed analog-output-headphones.conf [Element Master Mono] switch = on volume = on No effect turned off headphone jack sense and line jack sense control no effect, and were re-enabled by rebooting Do not know how to implement the details in your post #43 just as an experiment I temporarily replaced the /usr/share/pulseaudio/alsa-mixer/paths/ directory with the one from 12.04 and that made no difference either! -- 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/893210 Title: [Dell OptiPlex GX620 - AD1981b, playback] No sound at all Status in ALSA driver: Confirmed Status in alsa-driver package in Ubuntu: Incomplete Bug description: fresh install of ubuntu studio and updates but internal speakers do not play. dell optiplex gx620 love ya ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: alsa-base 1.0.24+dfsg-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6 Uname: Linux 3.0.0-13-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.23-0ubuntu4 Architecture: i386 Card0.Amixer.info: Card hw:0 'ICH7'/'Intel ICH7 with AD1981B at irq 23' Mixer name : 'Analog Devices AD1981B' Components : 'AC97a:41445374' Controls : 28 Simple ctrls : 20 Card1.Amixer.info: Card hw:1 'Device'/'C-Media Electronics Inc. USB Multimedia Audio Device at usb-:00:1d.7-4.1.4,' Mixer name : 'USB Mixer' Components : 'USB0d8c:0105' Controls : 13 Simple ctrls : 6 Date: Mon Nov 21 11:51:25 2011 InstallationMedia: Ubuntu-Studio 11.10 "Oneiric Ocelot" - Release i386 (20111011.1) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:ICH7 failed Symptom_Card: CM108 Audio Controller - USB Multimedia Audio Device Symptom_Type: No sound at all Title: [ICH4 - Intel ICH7, playback] No sound at all UpgradeStatus: Upgraded to oneiric on 2011-11-12 (8 days ago) dmi.bios.date: 11/30/2006 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0F8101 dmi.board.vendor: Dell Inc. dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0F8101:rvr:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex GX620 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/893210/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1422534] Re: No user name and password prompt for http basic authentication protected pages
For Transmission daemon, the url is http://user:p...@url.com:9091/transmission/web/ and works correctly on my bq ubuntu phone. The url can be LAN or WAN. The password doesn't accept some characters, such as "/". -- 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/1422534 Title: No user name and password prompt for http basic authentication protected pages Status in webbrowser-app package in Ubuntu: In Progress Status in webbrowser-app package in Ubuntu RTM: Confirmed Bug description: When accessing a http basic authentication protected page the browser does not prompt for a user name and password it simply displays the HTTP Error 401 Unauthorized message. The browser should prompt the user for credentials, set the Authorization header, etc... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1422534/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 893210] Re: [Dell OptiPlex GX620 - AD1981b, playback] No sound at all
Hi, I am also trying to get internal speakers to work on Dell OptiPlex GX620 (model no.: DCCY). External speakers work, however internal speakers are not even listed in PulseAudio Volume Control (and there is no sound). The internal speakers worked on previous OS (Windows XP). If you need another test system, please let me know what to run. I would really like to make this work. -- 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/893210 Title: [Dell OptiPlex GX620 - AD1981b, playback] No sound at all Status in ALSA driver: Confirmed Status in alsa-driver package in Ubuntu: Incomplete Bug description: fresh install of ubuntu studio and updates but internal speakers do not play. dell optiplex gx620 love ya ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: alsa-base 1.0.24+dfsg-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6 Uname: Linux 3.0.0-13-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.23-0ubuntu4 Architecture: i386 Card0.Amixer.info: Card hw:0 'ICH7'/'Intel ICH7 with AD1981B at irq 23' Mixer name : 'Analog Devices AD1981B' Components : 'AC97a:41445374' Controls : 28 Simple ctrls : 20 Card1.Amixer.info: Card hw:1 'Device'/'C-Media Electronics Inc. USB Multimedia Audio Device at usb-:00:1d.7-4.1.4,' Mixer name : 'USB Mixer' Components : 'USB0d8c:0105' Controls : 13 Simple ctrls : 6 Date: Mon Nov 21 11:51:25 2011 InstallationMedia: Ubuntu-Studio 11.10 "Oneiric Ocelot" - Release i386 (20111011.1) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:ICH7 failed Symptom_Card: CM108 Audio Controller - USB Multimedia Audio Device Symptom_Type: No sound at all Title: [ICH4 - Intel ICH7, playback] No sound at all UpgradeStatus: Upgraded to oneiric on 2011-11-12 (8 days ago) dmi.bios.date: 11/30/2006 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0F8101 dmi.board.vendor: Dell Inc. dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0F8101:rvr:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex GX620 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/893210/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1495296] [NEW] aptitude : Depends: libsigc++-2.0-0c2a (>= 2.2.0) but it is not installable
Public bug reported: Upgrading to wily Reading package lists... Done Building dependency tree Reading state information... Done libssl1.0.0 is already the newest version. You might want to run 'apt-get -f install' to correct these: The following packages have unmet dependencies. aptitude : Depends: libsigc++-2.0-0c2a (>= 2.2.0) but it is not installable compiz-core : Depends: libglibmm-2.4-1c2a (>= 2.42.0) but it is not installable Depends: libsigc++-2.0-0c2a (>= 2.2.0) but it is not installable libcwidget3 : Depends: libsigc++-2.0-0c2a (>= 2.2.0) but it is not installable libgmp-dev : Depends: libgmpxx4ldbl (= 2:6.0.0+dfsg-7) but 2:6.0.0+dfsg-6ubuntu1 is to be installed libnux-4.0-0 : Depends: libsigc++-2.0-0c2a (>= 2.2.0) but it is not installable libunity-core-6.0-9 : Depends: libsigc++-2.0-0c2a (>= 2.2.0) but it is not installable python3 : PreDepends: python3-minimal (= 3.4.3-1) but 3.4.3-4ubuntu1 is to be installed unity : Depends: libsigc++-2.0-0c2a (>= 2.2.0) but it is not installable ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: libsigc++-2.0-0v5 2.4.1-2 ProcVersionSignature: Ubuntu 3.19.0-27.29-generic 3.19.8-ckt5 Uname: Linux 3.19.0-27-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.4 Architecture: amd64 CurrentDesktop: Unity Date: Sun Sep 13 22:45:19 2015 Dependencies: gcc-5-base 5.2.1-17ubuntu1 libc6 2.21-0ubuntu4 libgcc1 1:5.2.1-17ubuntu1 libstdc++6 5.2.1-17ubuntu1 multiarch-support 2.21-0ubuntu4 InstallationDate: Installed on 2015-04-19 (147 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150417.1) SourcePackage: libsigc++-2.0 UpgradeStatus: Upgraded to wily on 2015-09-13 (0 days ago) ** Affects: libsigc++-2.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libsigc++-2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1495296 Title: aptitude : Depends: libsigc++-2.0-0c2a (>= 2.2.0) but it is not installable Status in libsigc++-2.0 package in Ubuntu: New Bug description: Upgrading to wily Reading package lists... Done Building dependency tree Reading state information... Done libssl1.0.0 is already the newest version. You might want to run 'apt-get -f install' to correct these: The following packages have unmet dependencies. aptitude : Depends: libsigc++-2.0-0c2a (>= 2.2.0) but it is not installable compiz-core : Depends: libglibmm-2.4-1c2a (>= 2.42.0) but it is not installable Depends: libsigc++-2.0-0c2a (>= 2.2.0) but it is not installable libcwidget3 : Depends: libsigc++-2.0-0c2a (>= 2.2.0) but it is not installable libgmp-dev : Depends: libgmpxx4ldbl (= 2:6.0.0+dfsg-7) but 2:6.0.0+dfsg-6ubuntu1 is to be installed libnux-4.0-0 : Depends: libsigc++-2.0-0c2a (>= 2.2.0) but it is not installable libunity-core-6.0-9 : Depends: libsigc++-2.0-0c2a (>= 2.2.0) but it is not installable python3 : PreDepends: python3-minimal (= 3.4.3-1) but 3.4.3-4ubuntu1 is to be installed unity : Depends: libsigc++-2.0-0c2a (>= 2.2.0) but it is not installable ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: libsigc++-2.0-0v5 2.4.1-2 ProcVersionSignature: Ubuntu 3.19.0-27.29-generic 3.19.8-ckt5 Uname: Linux 3.19.0-27-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.4 Architecture: amd64 CurrentDesktop: Unity Date: Sun Sep 13 22:45:19 2015 Dependencies: gcc-5-base 5.2.1-17ubuntu1 libc6 2.21-0ubuntu4 libgcc1 1:5.2.1-17ubuntu1 libstdc++6 5.2.1-17ubuntu1 multiarch-support 2.21-0ubuntu4 InstallationDate: Installed on 2015-04-19 (147 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150417.1) SourcePackage: libsigc++-2.0 UpgradeStatus: Upgraded to wily on 2015-09-13 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsigc++-2.0/+bug/1495296/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1474539] Re: FTBFS with Python 3.5
shiboken succeeds to build without changes. ** Changed in: shiboken (Ubuntu Wily) Status: New => 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/1474539 Title: FTBFS with Python 3.5 Status in apport package in Ubuntu: Fix Released Status in blist package in Ubuntu: Fix Released Status in cigi-ccl package in Ubuntu: New Status in kubuntu-driver-manager package in Ubuntu: Fix Released Status in libguestfs package in Ubuntu: New Status in lives package in Ubuntu: New Status in shiboken package in Ubuntu: Fix Released Status in apport source package in Wily: Fix Released Status in blist source package in Wily: Fix Released Status in cigi-ccl source package in Wily: New Status in kubuntu-driver-manager source package in Wily: Fix Released Status in libguestfs source package in Wily: New Status in lives source package in Wily: New Status in shiboken source package in Wily: Fix Released Bug description: We're in the process of starting the Python 3.5 transition for Wily. As such, we've identified a number of packages which FTBFS with Python 3.5. We're also soon starting the transition to gcc5. These are the packages that FTBFS in both transitions. Here is a link to the Python 3.5 failure in the PPA: https://launchpadlibrarian.net/210474236/buildlog_ubuntu-wily- amd64.apport_2.17.3-0ubuntu4_BUILDING.txt.gz See also: https://launchpad.net/~pythoneers/+archive/ubuntu/py35asdefault/+packages?field.name_filter=apport_filter=published_filter= To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1474539/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1474539] Re: FTBFS with Python 3.5
blist succeeds to build without changes. ** Changed in: blist (Ubuntu Wily) Status: New => 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/1474539 Title: FTBFS with Python 3.5 Status in apport package in Ubuntu: Fix Released Status in blist package in Ubuntu: Fix Released Status in cigi-ccl package in Ubuntu: New Status in kubuntu-driver-manager package in Ubuntu: Fix Released Status in libguestfs package in Ubuntu: New Status in lives package in Ubuntu: New Status in shiboken package in Ubuntu: Fix Released Status in apport source package in Wily: Fix Released Status in blist source package in Wily: Fix Released Status in cigi-ccl source package in Wily: New Status in kubuntu-driver-manager source package in Wily: Fix Released Status in libguestfs source package in Wily: New Status in lives source package in Wily: New Status in shiboken source package in Wily: Fix Released Bug description: We're in the process of starting the Python 3.5 transition for Wily. As such, we've identified a number of packages which FTBFS with Python 3.5. We're also soon starting the transition to gcc5. These are the packages that FTBFS in both transitions. Here is a link to the Python 3.5 failure in the PPA: https://launchpadlibrarian.net/210474236/buildlog_ubuntu-wily- amd64.apport_2.17.3-0ubuntu4_BUILDING.txt.gz See also: https://launchpad.net/~pythoneers/+archive/ubuntu/py35asdefault/+packages?field.name_filter=apport_filter=published_filter= To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1474539/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1318360] Re: Poor microphone quality (mako)
I just flashed to the latest radio image M9615A-CEFWMAZM-2.0.1701.07, but microphone quality is still bad. Does it need to be the image version from 4.4.2 to work correct ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1318360 Title: Poor microphone quality (mako) Status in pulseaudio package in Ubuntu: Confirmed Bug description: After months of complaints from people talking to me on the phone (mako ubuntu touch), I finally got around to use multiROM to dual boot Ubuntu Touch and Android. Several people can confirm that there is a noticable difference in terms of sound/microphone quality between Android and UT in phone calls. With UT, my voice gets distorted to an extent that person at the other end have real difficulties to hear what I am saying, while with Android call quality is much better with no distortion. I have had a suspicion for a long time that this might be a software and not a hardware issue. After trying Android and Ubuntu on the same hardware I believe this suspicion is proved correct. This issue has persisted in all the builds I have tried since at least the beginning of the year, but probably longer. I am now at r17 of Utopic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1318360/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1468832] Re: lightdm sources .profile
> The user's .profile is to be read by the shell, on interactive shell > (i.e. terminal) logins ONLY This is incorrect, .profile is read by the shell also when the shell is non-interactive. Here is the quote from the bash manual: > When Bash is invoked as an interactive login shell, or as a > non-interactive shell with the --login option, it first reads and > executes commands from the file /etc/profile, if that file exists. > After reading that file, it looks for ~/.bash_profile, ~/.bash_login, > and ~/.profile, in that order, and reads and executes commands from the > first one that exists and is readable. A not so far fetched example of a non interactive login shell is something like this, where I want to source .profile but not .bashrc $ ssh localhost "bash --login -c 'env'" This means that .profile might be read with no tty attached, and we should test for the presens of an attached tty when invoking stty in .profile .profile: tty -s && stty erase ^H I am interpreting a xsession as a login shell that should source .profile. -- 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/1468832 Title: lightdm sources .profile Status in lightdm package in Ubuntu: New Bug description: It is a bug for any display manager to read .profile--you guys are absolutely killing me with this. The user's .profile is to be read by the shell, on interactive shell (i.e. terminal) logins ONLY. The man page for bash explains this in detail; it's also discussed in the dash man page. The problem with display managers reading .profile is that it is the place where commands to set up your terminal (i.e. stty) go --this is the entire point of differentiating interactive shells from non-interactive shells, and it's the reason only interactive shells read .profile at all. Currently, if you have any such commands in your .profile, lightdm barfs on them, delaying the login session and forcing you to click on a prompt. This is extremely annoying (and wrong)! It would be satisfactory to make lightdm not display the errors, but that's the wrong solution. There's already a decades-established method of getting X display managers to source your environment settings: the .xsession file. It should be read by ALL display managers (or the session file that starts them). If you have common environment settings you want set in all your shells, the correct way to handle this is: .bashrc: # set all common environment vars here ENV_VAR=foo ... .profile: # set up terminal stty erase # BASH already sources .bashrc by default on interactive sessions .xsession: if [ -f .bashrc ] source .bashrc If you're not using BASH, you can still use this method without changing anything, except in .profile you need to explicitly source the .bashrc file. Of course you can change the name of the file that contains the common settings to reflect that your shell is not BASH; since the file is sourced by your other files explicitly, it does not matter what the user calls it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1468832/+subscriptions -- Mailing list: https://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 1422534] No user name and password prompt for http basicauthentication protected pages
Hi, that is not working for Transmission daemon, it is listening at 9091. Best regards -- Sent using Dekko from my Ubuntu device -- 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/1422534 Title: No user name and password prompt for http basic authentication protected pages Status in webbrowser-app package in Ubuntu: In Progress Status in webbrowser-app package in Ubuntu RTM: Confirmed Bug description: When accessing a http basic authentication protected page the browser does not prompt for a user name and password it simply displays the HTTP Error 401 Unauthorized message. The browser should prompt the user for credentials, set the Authorization header, etc... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1422534/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1495274] [NEW] python app crashes when using qt4-qtconfig
Public bug reported: When I use qt4-qtconfig to set qtcurve as theme phython app Anki crashes or hangs. It happens for example when I click on File menu or Close button, etc. I described it also on Anki support forum https://anki.tenderapp.com/discussions/ankidesktop/14722-anki-crashes-on-linux On this forum they claim it is qtcurve problem but other applications that use qtcurve don't crash nor hang. So I suspect it is caused by qt4-qtconfig. report: http://pastebin.com/B85PP9sA I uninstalled qt4-qtconfig and there was no problem with Anki, no crashes or hangs, but without it I can't use this theme engine for all applications, for example without it Anki and also Kate uses Oxygen even when in KDE setting there is qtcurve style chosen. ** Affects: qt4-x11 (Ubuntu) Importance: Undecided Status: New -- 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/1495274 Title: python app crashes when using qt4-qtconfig Status in qt4-x11 package in Ubuntu: New Bug description: When I use qt4-qtconfig to set qtcurve as theme phython app Anki crashes or hangs. It happens for example when I click on File menu or Close button, etc. I described it also on Anki support forum https://anki.tenderapp.com/discussions/ankidesktop/14722-anki-crashes-on-linux On this forum they claim it is qtcurve problem but other applications that use qtcurve don't crash nor hang. So I suspect it is caused by qt4-qtconfig. report: http://pastebin.com/B85PP9sA I uninstalled qt4-qtconfig and there was no problem with Anki, no crashes or hangs, but without it I can't use this theme engine for all applications, for example without it Anki and also Kate uses Oxygen even when in KDE setting there is qtcurve style chosen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/1495274/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1495274] Re: python app crashes when using qt4-qtconfig
I forgot to give details. It happens on Kubuntu 14.04 64-bit. Anki 2.0.32 Qt 4.8.6 PyQt 4.10.4 -- 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/1495274 Title: python app crashes when using qt4-qtconfig Status in qt4-x11 package in Ubuntu: New Bug description: When I use qt4-qtconfig to set qtcurve as theme phython app Anki crashes or hangs. It happens for example when I click on File menu or Close button, etc. I described it also on Anki support forum https://anki.tenderapp.com/discussions/ankidesktop/14722-anki-crashes-on-linux On this forum they claim it is qtcurve problem but other applications that use qtcurve don't crash nor hang. So I suspect it is caused by qt4-qtconfig. report: http://pastebin.com/B85PP9sA I uninstalled qt4-qtconfig and there was no problem with Anki, no crashes or hangs, but without it I can't use this theme engine for all applications, for example without it Anki and also Kate uses Oxygen even when in KDE setting there is qtcurve style chosen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/1495274/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 893210] Re: [Dell OptiPlex GX620 - AD1981b, playback] No sound at all
Small error on my part: I have OptiPlex GX520, not GX620. Should be similar though. Attaching my alsa-info. -- 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/893210 Title: [Dell OptiPlex GX620 - AD1981b, playback] No sound at all Status in ALSA driver: Confirmed Status in alsa-driver package in Ubuntu: Incomplete Bug description: fresh install of ubuntu studio and updates but internal speakers do not play. dell optiplex gx620 love ya ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: alsa-base 1.0.24+dfsg-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6 Uname: Linux 3.0.0-13-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.23-0ubuntu4 Architecture: i386 Card0.Amixer.info: Card hw:0 'ICH7'/'Intel ICH7 with AD1981B at irq 23' Mixer name : 'Analog Devices AD1981B' Components : 'AC97a:41445374' Controls : 28 Simple ctrls : 20 Card1.Amixer.info: Card hw:1 'Device'/'C-Media Electronics Inc. USB Multimedia Audio Device at usb-:00:1d.7-4.1.4,' Mixer name : 'USB Mixer' Components : 'USB0d8c:0105' Controls : 13 Simple ctrls : 6 Date: Mon Nov 21 11:51:25 2011 InstallationMedia: Ubuntu-Studio 11.10 "Oneiric Ocelot" - Release i386 (20111011.1) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:ICH7 failed Symptom_Card: CM108 Audio Controller - USB Multimedia Audio Device Symptom_Type: No sound at all Title: [ICH4 - Intel ICH7, playback] No sound at all UpgradeStatus: Upgraded to oneiric on 2011-11-12 (8 days ago) dmi.bios.date: 11/30/2006 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0F8101 dmi.board.vendor: Dell Inc. dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0F8101:rvr:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex GX620 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/893210/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 893210] Re: [Dell OptiPlex GX620 - AD1981b, playback] No sound at all
** Attachment added: "GX520 alsa-info" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/893210/+attachment/4463362/+files/alsa-info.txt.TO94irU7Fb -- 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/893210 Title: [Dell OptiPlex GX620 - AD1981b, playback] No sound at all Status in ALSA driver: Confirmed Status in alsa-driver package in Ubuntu: Incomplete Bug description: fresh install of ubuntu studio and updates but internal speakers do not play. dell optiplex gx620 love ya ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: alsa-base 1.0.24+dfsg-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6 Uname: Linux 3.0.0-13-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.23-0ubuntu4 Architecture: i386 Card0.Amixer.info: Card hw:0 'ICH7'/'Intel ICH7 with AD1981B at irq 23' Mixer name : 'Analog Devices AD1981B' Components : 'AC97a:41445374' Controls : 28 Simple ctrls : 20 Card1.Amixer.info: Card hw:1 'Device'/'C-Media Electronics Inc. USB Multimedia Audio Device at usb-:00:1d.7-4.1.4,' Mixer name : 'USB Mixer' Components : 'USB0d8c:0105' Controls : 13 Simple ctrls : 6 Date: Mon Nov 21 11:51:25 2011 InstallationMedia: Ubuntu-Studio 11.10 "Oneiric Ocelot" - Release i386 (20111011.1) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:ICH7 failed Symptom_Card: CM108 Audio Controller - USB Multimedia Audio Device Symptom_Type: No sound at all Title: [ICH4 - Intel ICH7, playback] No sound at all UpgradeStatus: Upgraded to oneiric on 2011-11-12 (8 days ago) dmi.bios.date: 11/30/2006 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0F8101 dmi.board.vendor: Dell Inc. dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0F8101:rvr:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex GX620 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/893210/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1495027] Re: unity_support_test should not write to hardcoded file in /tmp
** Changed in: nux (Ubuntu) Status: New => Triaged ** Changed in: nux (Ubuntu) Importance: Undecided => Low ** Also affects: nux Importance: Undecided Status: New ** Changed in: nux Status: New => Triaged ** Changed in: nux Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nux in Ubuntu. https://bugs.launchpad.net/bugs/1495027 Title: unity_support_test should not write to hardcoded file in /tmp Status in Nux: Triaged Status in nux package in Ubuntu: Triaged Bug description: unity_support_test writes to a file called /tmp/unity_support_test.0 no matter what value is set in TMP, TMPDIR, and so on. This tool should respect user preferences and not hardcode the temporary directory. To manage notifications about this bug go to: https://bugs.launchpad.net/nux/+bug/1495027/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1449851] Re: package libpython2.7-dev 2.7.8-10ubuntu1 failed to install/upgrade: no se pudieron copiar los datos extraídos de './usr/lib/python2.7/config-x86_64-linux-gnu/libpyth
this is unrelated to python2.7 ** Package changed: python2.7 (Ubuntu) => ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1449851 Title: package libpython2.7-dev 2.7.8-10ubuntu1 failed to install/upgrade: no se pudieron copiar los datos extraídos de './usr/lib/python2.7/config- x86_64-linux-gnu/libpython2.7.a' a '/usr/lib/python2.7/config-x86_64 -linux-gnu/libpython2.7.a.dpkg-new': fin de fichero o de flujo inesperado Status in Ubuntu: New Bug description: I got this error when upgrading to ubuntu 15 pkg-deb (subproceso): descomprimiendo el miembro del archivo: error de lzma: los datos comprimidos están corrompidos dpkg-deb: error: el subprocesodevolvió el código de salida de error 2 dpkg: error al procesar el archivo /var/cache/apt/archives/libpython2.7-dev_2.7.9-2ubuntu3_amd64.deb (--unpack): no se pudieron copiar los datos extraídos de './usr/lib/python2.7/config-x86_64-linux-gnu/libpython2.7.a' a '/usr/lib/python2.7/config-x86_64-linux-gnu/libpython2.7.a.dpkg-new': fin de fichero o de flujo inesperado Se encontraron errores al procesar: /var/cache/apt/archives/libpython2.7-dev_2.7.9-2ubuntu3_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 15.04 Package: libpython2.7-dev 2.7.8-10ubuntu1 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 Date: Wed Apr 29 00:17:27 2015 DuplicateSignature: package:libpython2.7-dev:2.7.8-10ubuntu1:no se pudieron copiar los datos extraídos de './usr/lib/python2.7/config-x86_64-linux-gnu/libpython2.7.a' a '/usr/lib/python2.7/config-x86_64-linux-gnu/libpython2.7.a.dpkg-new': fin de fichero o de flujo inesperado ErrorMessage: no se pudieron copiar los datos extraídos de './usr/lib/python2.7/config-x86_64-linux-gnu/libpython2.7.a' a '/usr/lib/python2.7/config-x86_64-linux-gnu/libpython2.7.a.dpkg-new': fin de fichero o de flujo inesperado InstallationDate: Installed on 2015-04-13 (16 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4 SourcePackage: python2.7 Title: package libpython2.7-dev 2.7.8-10ubuntu1 failed to install/upgrade: no se pudieron copiar los datos extraídos de './usr/lib/python2.7/config-x86_64-linux-gnu/libpython2.7.a' a '/usr/lib/python2.7/config-x86_64-linux-gnu/libpython2.7.a.dpkg-new': fin de fichero o de flujo inesperado UpgradeStatus: Upgraded to vivid on 2015-04-28 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1449851/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1479511] Re: package python2.7 2.7.6-8ubuntu0.2 failed to install/upgrade: package python2.7 is not ready for configuration cannot configure (current status `half-installed')
dpkg: error processing package python2.7 (--configure): package python2.7 is not ready for configuration cannot configure (current status `half-installed') ** Package changed: python2.7 (Ubuntu) => dpkg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1479511 Title: package python2.7 2.7.6-8ubuntu0.2 failed to install/upgrade: package python2.7 is not ready for configuration cannot configure (current status `half-installed') Status in dpkg package in Ubuntu: New Bug description: It failed. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: python2.7 2.7.6-8ubuntu0.2 ProcVersionSignature: Ubuntu 3.16.0-45.60~14.04.1-generic 3.16.7-ckt14 Uname: Linux 3.16.0-45-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 Date: Wed Jul 29 15:32:02 2015 DuplicateSignature: package:python2.7:2.7.6-8ubuntu0.2:package python2.7 is not ready for configuration cannot configure (current status `half-installed') ErrorMessage: package python2.7 is not ready for configuration cannot configure (current status `half-installed') InstallationDate: Installed on 2015-04-03 (117 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: python2.7 Title: package python2.7 2.7.6-8ubuntu0.2 failed to install/upgrade: package python2.7 is not ready for configuration cannot configure (current status `half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1479511/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1480190] Re: Python segmentation fault when using GPIO pins (Raspberry Pi 2)
** Package changed: python2.7 (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1480190 Title: Python segmentation fault when using GPIO pins (Raspberry Pi 2) Status in ubuntu-mate: New Status in linux package in Ubuntu: New Bug description: I noticed that there's a critical problem with using the GPIO pins on the Raspberry Pi 2 running Ubuntu Mate. Everytime I try enabling a pin with Python it crashes with the error message "Segmentation fault (core dumped)". It seems like a problem with the Kernel like it is explained here: http://stackoverflow.com/questions/30442719/getting-segmentation- fault-when-using-rpi-gpio-setup-on-raspberry-pi-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1480190/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1495256] Re: There is no option to disable history in webbrowser-app (15.04)
There is a "private browsing" mode that does that. ** Changed in: webbrowser-app (Ubuntu) Status: New => Invalid -- 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/1495256 Title: There is no option to disable history in webbrowser-app (15.04) Status in webbrowser-app package in Ubuntu: Invalid Bug description: An option should be available which turns off recording history of pages visited. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1495256/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1495297] Re: [regression] All options in the drawer menu always visible
** Branch linked: lp:~osomon/webbrowser-app/drawer-menu-actions-visible -- 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/1495297 Title: [regression] All options in the drawer menu always visible Status in webbrowser-app package in Ubuntu: In Progress Bug description: Since the landing of the UITK version 1.3.1627+15.04.20150908-0ubuntu1, all the options in the drawer menu are always visible, even those that shouldn’t be (those are disabled, but still visible). This breaks a couple of autopilot tests in the webbrowser-app test suite: webbrowser_app.tests.test_findinpage.TestFindInPage.test_find_in_page_not_in_menu_in_new_tab webbrowser_app.tests.test_private.TestPrivateView.test_going_in_and_out_private_mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1495297/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1495030] Re: lightdm-gtk-greeter hangs, leaving session locked with gray screen
** Package changed: lightdm (Ubuntu) => lightdm-gtk-greeter (Ubuntu) -- 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/1495030 Title: lightdm-gtk-greeter hangs, leaving session locked with gray screen Status in lightdm-gtk-greeter package in Ubuntu: New Bug description: On a fresh Xubuntu 15.04 install, I created a new user. When I lock the session (or resume from standby, which also locks the session), I see nothing but a screen in light gray. After about a minnute, the screen goes black (power safe), pressing any key brings back the gray screen. There is no possibility to unlock the session. Ctrl+Alt+F1 brings me to terminal, where I can see with `top` that "lightdm-gtk- greeter" takes 100% CPU. The log contains warnings about background images that can not be read. I believe those are warnings only and not fatal errors. Version of lightdm-gtk-greeter: 2.0.0-0ubuntu1. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lightdm 1.14.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.4 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Sep 12 10:02:29 2015 InstallationDate: Installed on 2015-09-03 (8 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm-gtk-greeter/+bug/1495030/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1476559] Re: Hard to tap links at the very bottom of webpage
At other mobile sites without zoom possibility but with a too small link to change the site to the desktop version it is absolutely impossible to reach the link. But only the desktop version has the full information... -- 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/1476559 Title: Hard to tap links at the very bottom of webpage Status in webbrowser-app package in Ubuntu: Confirmed Bug description: When touching the very bottom of the window, the webbrowser-app brings up the new-tab bottom-of-screen panel. This means that if a webpage has links on the very bottom of the page, it is impossible to click them. Prior to r24, it was possible to deal with this by rotating to horizontal view, and tapping the link, since "bottom of the screen" was defined on one screen edge only. However, since r24 brings full shell rotation, this is no longer the case. Example webpage where this affects the ability to navigate: http://forum.dlang.org/thread/mnp350$7ql$2...@digitalmars.com (scroll down to the bottom for the « First ‹ Prev | Next › Last » links, these are now impossible to use). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1476559/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1078704]
MASTER VOLUME REGISTER Index 0x02 This register controls the Line_Out volume controls for both stereo channels and the mute bit. Each volume subregister contains five bits, generating 32 volume levels with 31 steps of 1.5 dB each. Because AC ’97 defines 6-bit volume registers, to maintain compatibility whenever the D5 or D13 bits are set to 1, their respective lower five volume bits are automatically set to 1 by the codec logic. On readback, all lower five bits read 1s whenever these bits are set to 1. Refer to Table 12 for examples. HEADPHONE VOLUME REGISTER Index 0x04 This register controls the headphone volume controls for both stereo channels and the mute bit. Each volume subregister contains five bits, generating 32 volume levels with 31 steps of 1.5 dB each. Because AC ’97 defines 6-bit volume registers, to maintain compatibility, whenever the D5 or D13 bits are set to 1, their respective lower five volume bits are automatically set to 1 by the codec logic. On readback, all lower five bits read 1s whenever these bits are set to 1. Refer to Table 12 for examples. this is quite different from those virtual master of hda codecs -- 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/1078704 Title: headphone jack sense not enabled Status in ALSA driver: Confirmed Status in alsa-driver package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: bug is present in Ubuntu 12.04 and Xubuntu 12.04 and Lubuntu 12.04.1 64bit alsa-base 1.0.25+dfsg-0ubuntu1 on this machine (64 bit) I except Ubuntu to automatically sense the presence of headphones and disable the speakers. This is not the case, the speakers and headphones play simultaneously. I must install gnome-alsamixer to manually set the jack sense. Alsa should have this enabled as the default setting. This seems as though it should be a very easy bug to fix, though. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: alsa-base 1.0.25+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30 Uname: Linux 3.2.0-32-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: love 1330 F pulseaudio Card0.Amixer.info: Card hw:0 'nForce3'/'NVidia nForce3 with AD1981B at irq 21' Mixer name : 'Analog Devices AD1981B' Components : 'AC97a:41445374' Controls : 33 Simple ctrls : 22 Date: Wed Nov 14 06:42:21 2012 InstallationMedia: Lubuntu 12.04 "Precise Pangolin" - Release amd64 (20120423) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/30/2004 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.11 dmi.board.name: 08A0 dmi.board.vendor: Compal dmi.board.version: 32.22 dmi.chassis.type: 10 dmi.chassis.vendor: Compal dmi.modalias: dmi:bvnHewlett-Packard:bvrF.11:bd04/30/2004:svnHewlett-Packard:pnPresarioR3200(PF153UA#ABA):pvrF.11:rvnCompal:rn08A0:rvr32.22:cvnCompal:ct10:cvr: dmi.product.name: Presario R3200 (PF153UA#ABA) dmi.product.version: F.11 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1078704/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1078704]
pulseaudio dB range (-127.5,+12) is incorrect 662| 0.000) D: [pulseaudio] alsa-mixer.c: Path analog-output- headphones (Headphones), direction=1, priority=90, probed=yes, supported=yes, has_mute=yes, has_volume=yes, has_dB=yes, min_volume=0, max_volume=31, min_dB=-127.5, max_dB=12 ( 0.662| 0.000) D: [pulseaudio] alsa-mixer.c: Element Master, direction=1, switch=1, volume=1, volume_limit=-1, enumeration=0, required=0, required_any=0, required_absent=0, mask=0x36f66, n_channels=2, override_map=yes ( 0.662| 0.000) D: [pulseaudio] alsa-mixer.c: Element Master Mono, direction=1, switch=2, volume=2, volume_limit=-1, enumeration=0, required=0, required_any=0, required_absent=0, mask=0x7, n_channels=1, override_map=no ( 0.662| 0.000) D: [pulseaudio] alsa-mixer.c: Element Headphone, direction=1, switch=1, volume=1, volume_limit=-1, enumeration=0, required=0, required_any=4, required_absent=0, mask=0x36f66, n_channels=2, override_map=yes ( 0.662| 0.000) D: [pulseaudio] alsa-mixer.c: Element PCM, direction=1, switch=1, volume=1, volume_limit=-1, enumeration=0, required=0, required_any=0, required_absent=0, mask=0x36f66, n_channels=2, override_map=yes ( 0.662| 0.000) D: [pulseaudio] alsa-mixer.c: Element External Amplifier, direction=1, switch=4, volume=0, volume_limit=-1, enumeration=0, required=0, required_any=0, required_absent=0, mask=0x0, n_channels=0, override_map=no ( 0.662| 0.000) D: [pulseaudio] alsa-mixer.c: Option on (output- amplifier-on/Amplifier) index=1, priority=10 ( 0.662| 0.000) D: [pulseaudio] alsa-mixer.c: Option off (output- amplifier-off/No Amplifier) index=0, priority=0 ( 0.663| 0.000) D: [pulseaudio] alsa-mixer.c: Jack Front Headphone, alsa_name='Front Headphone Jack', detection unavailable ( 0.663| 0.000) D: [pulseaudio] alsa-mixer.c: Jack Front Headphone Phantom, alsa_name='Front Headphone Phantom Jack', detection unavailable ( 0.663| 0.000) D: [pulseaudio] alsa-mixer.c: Jack Headphone, alsa_name='Headphone Jack', detection unavailable ( 0.663| 0.000) D: [pulseaudio] alsa-mixer.c: Jack Headphone Phantom, alsa_name='Headphone Phantom Jack', detection unavailable ( 0.663| 0.000) D: [pulseaudio] alsa-mixer.c: Jack Headphone Mic, alsa_name='Headphone Mic Jack', detection unavailable ( 0.663| 0.000) D: [pulseaudio] alsa-mixer.c: Setting output- amplifier-on (Amplifier) priority=10 ( 0.663| 0.000) D: [pulseaudio] alsa-mixer.c: Setting output- amplifier-off (No Amplifier) priority= -- 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/1078704 Title: headphone jack sense not enabled Status in ALSA driver: Confirmed Status in alsa-driver package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: bug is present in Ubuntu 12.04 and Xubuntu 12.04 and Lubuntu 12.04.1 64bit alsa-base 1.0.25+dfsg-0ubuntu1 on this machine (64 bit) I except Ubuntu to automatically sense the presence of headphones and disable the speakers. This is not the case, the speakers and headphones play simultaneously. I must install gnome-alsamixer to manually set the jack sense. Alsa should have this enabled as the default setting. This seems as though it should be a very easy bug to fix, though. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: alsa-base 1.0.25+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30 Uname: Linux 3.2.0-32-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: love 1330 F pulseaudio Card0.Amixer.info: Card hw:0 'nForce3'/'NVidia nForce3 with AD1981B at irq 21' Mixer name : 'Analog Devices AD1981B' Components : 'AC97a:41445374' Controls : 33 Simple ctrls : 22 Date: Wed Nov 14 06:42:21 2012 InstallationMedia: Lubuntu 12.04 "Precise Pangolin" - Release amd64 (20120423) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/30/2004 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.11 dmi.board.name: 08A0 dmi.board.vendor: Compal dmi.board.version: 32.22 dmi.chassis.type: 10 dmi.chassis.vendor: Compal dmi.modalias: dmi:bvnHewlett-Packard:bvrF.11:bd04/30/2004:svnHewlett-Packard:pnPresarioR3200(PF153UA#ABA):pvrF.11:rvnCompal:rn08A0:rvr32.22:cvnCompal:ct10:cvr: dmi.product.name: Presario R3200 (PF153UA#ABA) dmi.product.version: F.11 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to:
[Touch-packages] [Bug 1478217] Re: can't pair bluetooth keyboard, phone doesn't show code.
Same issue with E4.5 and Apple wireless keyboard. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1478217 Title: can't pair bluetooth keyboard, phone doesn't show code. Status in indicator-bluetooth package in Ubuntu: Confirmed Bug description: 1) Device: Meizu MX4 Ubuntu Edition OS: Ubuntu 15.04 (r68) - armhf (20150724-020304) 2) Bluez version 4.101-0ubuntu25 indicator-bluetooth version 0.0.6+14.10.20141006-0ubuntu1 3) When trying to connect a bluetooth keyboard (SilverCrest SBT 3.0 A1), pairing doesn't follow correct procedure. On other devices (Android 5.1.1 on Nexus 10; Ubuntu 15.04 on BTO laptop) a 6 digit number is displayed, which needs to be typed on the Bluetooth keyboard, followed by pressing [Enter]. 4) On Ubuntu touch, a dialogue appears asking to enter a 4 digit PIN on the phone. Default is '' and at first the phone says the device is connected, but the phone does not respond to any input from the keyboard. After some time the phone indicates the device is not connected. All of this is similarly described in this askubuntu article: http://askubuntu.com/questions/625533/how-to-pair-external-bluetooth- keyboard-to-ubuntu-touch-bq-phone, which has not received any answers as of yet. I am willing to follow instructions and report back results. i have adb shell installed on my laptop, and Terminal app installed on the phone. Developer mode is on. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1478217/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1464711] Re: [Browser] tabs indicator tab gets in the way of content on the page
See also Bug #1476559. -- 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/1464711 Title: [Browser] tabs indicator tab gets in the way of content on the page Status in Ubuntu UX: Fix Committed Status in webbrowser-app package in Ubuntu: Confirmed Bug description: In Ubuntu Touch, the web browser tab indicator overlays the content of the web page being displayed and it makes some content on the page inaccessible. For example: a website's footer links. For optimal web browser usability, the web page content should not be obstructed. --- --- --- --- UX Comment: We have a common behaviour for hiding the bottom edge when scrolling begins up-ward begins. I would recommend we apply the same behaviour to over-scrolling upward on pages that are vertically small enough to not require scrolling. In cases like the one described in this bug report, the user is highly likely to attempt to scroll the page upward in order to see the footer links occluded by the bottom-edge hint, which would cause the hint to become hidden. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1464711/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
