[Touch-packages] [Bug 1440395] Re: fstab-generator interprets backslashes in CIFS mounts
** Summary changed: - fstab-generator creates incorrect mount units for CIFS + fstab-generator interprets backslashes in CIFS mounts -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1440395 Title: fstab-generator interprets backslashes in CIFS mounts Status in systemd: Confirmed Status in systemd package in Ubuntu: Invalid Bug description: Hello. I'm using systemd 219 on Ubuntu 15.04. I have the following line in /etc/fstab: \\192.168.1.110\ExtHDD /mnt/nas cifs vers=3.0,nofail,x-gvfs- show,credentials=/etc/nas_passwd,uid=1000,gid=1000,cache=loose 0 0 sudo mount /mnt/nas/ works properly in this case. Hovewer, fstab- generator creates an incorrect mount unit: # Automatically generated by systemd-fstab-generator [Unit] SourcePath=/etc/fstab Documentation=man:fstab(5) man:systemd-fstab-generator(8) [Mount] What=\192.168.1.110\ExtHDD Where=/mnt/nas Type=cifs Options=vers=3.0,nofail,x-gvfs-show,credentials=/etc/nas_passwd,uid=1000,gid=1000,cache=loose Note a missing backslash before the IP address. systemctl status mnt- nas.mount obviously tells that unit wasn't able to start: марта 31 20:23:32 artyom-H97-D3H mount[7360]: mount.cifs: bad UNC (\192.168.1.110\ExtHDD) Let's add more backslashes to the CIFS path: 192.168.1.110\\ExtHDD /mnt/nas cifs vers=3.0,nofail,x-gvfs- show,credentials=/etc/nas_passwd,uid=1000,gid=1000,cache=loose 0 0 In this case, generated mount unit is correct: # Automatically generated by systemd-fstab-generator [Unit] SourcePath=/etc/fstab Documentation=man:fstab(5) man:systemd-fstab-generator(8) [Mount] What=\\192.168.1.110\ExtHDD Where=/mnt/nas Type=cifs Options=vers=3.0,nofail,x-gvfs-show,credentials=/etc/nas_passwd,uid=1000,gid=1000,cache=loose However, mount commands refuses to work: $ sudo mount /mnt/nas mount.cifs: bad UNC (192.168.1.110\\ExtHDD) I don't precisely know if fstab entries should contain escape characters (extra backslashes). Nonetheless, fstab-generator and mount command should have the same behaviour anyway. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-6ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 NonfreeKernelModules: arc4 md4 nls_utf8 cifs fscache pci_stub vboxpci vboxnetadp vboxnetflt vboxdrv cfg80211 nls_iso8859_1 joydev snd_hda_codec_realtek snd_hda_codec_hdmi snd_hda_codec_generic intel_rapl iosf_mbi x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel hid_logitech_hidpp kvm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel snd_soc_rt5640 aes_x86_64 snd_soc_rl6231 lrw snd_soc_core gf128mul snd_hda_intel glue_helper snd_hda_controller ablk_helper snd_compress cryptd snd_hda_codec snd_pcm_dmaengine snd_hwdep snd_pcm serio_raw snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device snd_timer snd mei_me mei i915 shpchp lpc_ich drm_kms_helper drm 8250_fintek dw_dmac i2c_algo_bit i2c_hid soundcore dw_dmac_core i2c_designware_platform 8250_dw snd_soc_sst_acpi i2c_designware_core video spi_pxa2xx_platform tpm_infineon mac_hid acpi_pad sunrpc parport_pc ppdev lp parport autofs4 hid_logitech_dj usbhid hid e1000e psmouse ahci ptp libahci pps_core sdhci_acpi sdhci ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Apr 4 21:38:52 2015 InstallationDate: Installed on 2015-02-05 (58 days ago) InstallationMedia: Xubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140723) MachineType: Gigabyte Technology Co., Ltd. H97-D3H ProcKernelCmdLine: \vmlinuz-3.19.0-9-generic.efi.signed ro root=UUID=840a4068-987e-4392-8835-3a32930cd96b quiet splash initrd=\initrd.img-3.19.0-9-generic SourcePackage: systemd UpgradeStatus: Upgraded to vivid on 2015-03-02 (33 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-D3H-CF 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-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH97-D3H-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: H97-D3H 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/systemd/+bug/1440395/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1302090] Re: Dell Alienware 14, Speaker sound output is mono until a headphone jack is plugged
driver seem hardcode to use first pin spec-gen.autocfg.hp_pins[0] as hp
of the headset
and imux_pin to determine the selected mic
this mean that if you set the correct pin default of headset mic
(headset mic phantom jack)
you can select internal mic, headset mic or mic jack manually using the
capture source control
static void alc_update_headset_mode(struct hda_codec *codec)
{
struct alc_spec *spec = codec-spec;
hda_nid_t mux_pin = spec-gen.imux_pins[spec-gen.cur_mux[0]];
hda_nid_t hp_pin = spec-gen.autocfg.hp_pins[0];
int new_headset_mode;
if (!snd_hda_jack_detect(codec, hp_pin))
new_headset_mode = ALC_HEADSET_MODE_UNPLUGGED;
else if (mux_pin == spec-headset_mic_pin)
new_headset_mode = ALC_HEADSET_MODE_HEADSET;
else if (mux_pin == spec-headphone_mic_pin)
new_headset_mode = ALC_HEADSET_MODE_MIC;
else
new_headset_mode = ALC_HEADSET_MODE_HEADPHONE;
--
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/1302090
Title:
Dell Alienware 14, Speaker sound output is mono until a headphone jack
is plugged
Status in alsa-driver package in Ubuntu:
Confirmed
Bug description:
Here's the required release and package information:
Description:Ubuntu Trusty Tahr (development branch)
Release:14.04
Package: linux-image-extra-3.13.0-19-generic
Version: 3.13.0-19.40
When playing audio through speakers on my Alienware 14 2014, the sound
output is in mono until I plug a headphone in any of the two available
headphone jacks (obviously, the auto-mute option must be disabled).
When I do so, the sound starts to play in stereo.
I would love the sound output to be stereo by default and not be
forced to plug anything to achieve that.
Attached is the alsa-info.sh output for my machine.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1302090/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1404762] Re: apparmor profile usr.sbin.clamd does not allow ScanOnAccess via fanotify
clamd starts with: 1. aa-complain clamd 2. invoke-rc.d clamav-daemon restart No clamd entries in syslog. audit.log after starting clamd: type=USER_AUTH msg=audit(1428468600.638:193): pid=8314 uid=1000 auid=4294967295 ses=4294967295 msg='op=PAM:authentication acct=hartwig exe=/usr/bin/sudo hostname=? addr=? terminal=/dev/pts/18 res=success' type=USER_ACCT msg=audit(1428468600.638:194): pid=8314 uid=1000 auid=4294967295 ses=4294967295 msg='op=PAM:accounting acct=hartwig exe=/usr/bin/sudo hostname=? addr=? terminal=/dev/pts/18 res=success' type=USER_START msg=audit(1428468600.658:195): pid=8314 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:session_open acct=root exe=/usr/bin/sudo hostname=? addr=? terminal=/dev/pts/18 res=success' type=AVC msg=audit(1428468604.378:196): apparmor=STATUS operation=profile_replace profile=unconfined name=/usr/sbin/clamd pid=8319 comm=apparmor_parser type=SYSCALL msg=audit(1428468604.378:196): arch=4003 syscall=4 success=yes exit=26185 a0=3 a1=9c6677c a2=6649 a3=bfbf36c4 items=0 ppid=8315 pid=8319 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=pts18 ses=4294967295 comm=apparmor_parser exe=/sbin/apparmor_parser key=(null) type=USER_END msg=audit(1428468604.450:197): pid=8314 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:session_close acct=root exe=/usr/bin/sudo hostname=? addr=? terminal=/dev/pts/18 res=success' But - Eicar file can be copied, no error msg, no log entry -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1404762 Title: apparmor profile usr.sbin.clamd does not allow ScanOnAccess via fanotify Status in apparmor package in Ubuntu: Confirmed Bug description: I tried to enable the ScanOnAccess option in /etc/clamav.conf to get on-access scanning. Doing so, /var/log/clamav/clamav.log tells me: ERROR: ScanOnAccess: fanotify_init failed: Operation not permitted ScanOnAccess: clamd must be started by root Setting User to root in /etc/clamav/clamd.conf makes the clamav-daemon to fail with service clamav-daemon start * Starting ClamAV daemon clamd ERROR: initgroups() failed. I had to disable the apparmor.profile with a cd /etc/apparmor.d/disable ln -s ./../usr.sbin.clamd Then, the ERROR: initgroups() failed. disappears. The apparmor itself came via apt-get packages. I did not edit it. Description: Ubuntu 14.04.1 LTS Release: 14.04 apt-cache policy apparmor-profiles apparmor-profiles: Installiert: (keine) Installationskandidat: 2.8.95~2430-0ubuntu5.1 Versionstabelle: 2.8.95~2430-0ubuntu5.1 0 500 http://de.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 2.8.95~2430-0ubuntu5 0 500 http://de.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apparmor-profiles (not installed) ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 Date: Mon Dec 22 01:23:04 2014 InstallationDate: Installed on 2014-11-29 (22 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) ProcEnviron: LANGUAGE=de_DE TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdline: BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-43-generic root=UUID=6408c2d9-1b60-43d7-9a7f-2dceeb40de28 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: apparmor Syslog: UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1404762/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1440395] Re: fstab-generator interprets backslashes in CIFS mounts
This unescaping is already done by getmntent(). With an fstab entry like \\1.2.3.4\stuff /mnt/stuff cifs defaults,nofail 0 0 the me-mnt_fsname is \1.2.3.4\stuff. fstab uses \ as an escape character, so I'm afraid this pretty much behaves as specified and you have to escape \ too if you use them (i. e. use 1.2.3.4...). It's best to avoid those at all and use forward slashes for CIFS mounts. ** Changed in: systemd (Ubuntu) Status: Triaged = Invalid ** Changed in: systemd (Ubuntu) Assignee: Martin Pitt (pitti) = (unassigned) -- 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/1440395 Title: fstab-generator interprets backslashes in CIFS mounts Status in systemd: Confirmed Status in systemd package in Ubuntu: Invalid Bug description: Hello. I'm using systemd 219 on Ubuntu 15.04. I have the following line in /etc/fstab: \\192.168.1.110\ExtHDD /mnt/nas cifs vers=3.0,nofail,x-gvfs- show,credentials=/etc/nas_passwd,uid=1000,gid=1000,cache=loose 0 0 sudo mount /mnt/nas/ works properly in this case. Hovewer, fstab- generator creates an incorrect mount unit: # Automatically generated by systemd-fstab-generator [Unit] SourcePath=/etc/fstab Documentation=man:fstab(5) man:systemd-fstab-generator(8) [Mount] What=\192.168.1.110\ExtHDD Where=/mnt/nas Type=cifs Options=vers=3.0,nofail,x-gvfs-show,credentials=/etc/nas_passwd,uid=1000,gid=1000,cache=loose Note a missing backslash before the IP address. systemctl status mnt- nas.mount obviously tells that unit wasn't able to start: марта 31 20:23:32 artyom-H97-D3H mount[7360]: mount.cifs: bad UNC (\192.168.1.110\ExtHDD) Let's add more backslashes to the CIFS path: 192.168.1.110\\ExtHDD /mnt/nas cifs vers=3.0,nofail,x-gvfs- show,credentials=/etc/nas_passwd,uid=1000,gid=1000,cache=loose 0 0 In this case, generated mount unit is correct: # Automatically generated by systemd-fstab-generator [Unit] SourcePath=/etc/fstab Documentation=man:fstab(5) man:systemd-fstab-generator(8) [Mount] What=\\192.168.1.110\ExtHDD Where=/mnt/nas Type=cifs Options=vers=3.0,nofail,x-gvfs-show,credentials=/etc/nas_passwd,uid=1000,gid=1000,cache=loose However, mount commands refuses to work: $ sudo mount /mnt/nas mount.cifs: bad UNC (192.168.1.110\\ExtHDD) I don't precisely know if fstab entries should contain escape characters (extra backslashes). Nonetheless, fstab-generator and mount command should have the same behaviour anyway. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-6ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 NonfreeKernelModules: arc4 md4 nls_utf8 cifs fscache pci_stub vboxpci vboxnetadp vboxnetflt vboxdrv cfg80211 nls_iso8859_1 joydev snd_hda_codec_realtek snd_hda_codec_hdmi snd_hda_codec_generic intel_rapl iosf_mbi x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel hid_logitech_hidpp kvm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel snd_soc_rt5640 aes_x86_64 snd_soc_rl6231 lrw snd_soc_core gf128mul snd_hda_intel glue_helper snd_hda_controller ablk_helper snd_compress cryptd snd_hda_codec snd_pcm_dmaengine snd_hwdep snd_pcm serio_raw snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device snd_timer snd mei_me mei i915 shpchp lpc_ich drm_kms_helper drm 8250_fintek dw_dmac i2c_algo_bit i2c_hid soundcore dw_dmac_core i2c_designware_platform 8250_dw snd_soc_sst_acpi i2c_designware_core video spi_pxa2xx_platform tpm_infineon mac_hid acpi_pad sunrpc parport_pc ppdev lp parport autofs4 hid_logitech_dj usbhid hid e1000e psmouse ahci ptp libahci pps_core sdhci_acpi sdhci ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Apr 4 21:38:52 2015 InstallationDate: Installed on 2015-02-05 (58 days ago) InstallationMedia: Xubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140723) MachineType: Gigabyte Technology Co., Ltd. H97-D3H ProcKernelCmdLine: \vmlinuz-3.19.0-9-generic.efi.signed ro root=UUID=840a4068-987e-4392-8835-3a32930cd96b quiet splash initrd=\initrd.img-3.19.0-9-generic SourcePackage: systemd UpgradeStatus: Upgraded to vivid on 2015-03-02 (33 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-D3H-CF 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:
[Touch-packages] [Bug 1302090] Re: Dell Alienware 14, Speaker sound output is mono until a headphone jack is plugged
the presence of internal mic phantom , headset mic phantom and mic jack force the driver to disable auto mic selection and create the capture source control -- 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/1302090 Title: Dell Alienware 14, Speaker sound output is mono until a headphone jack is plugged Status in alsa-driver package in Ubuntu: Confirmed Bug description: Here's the required release and package information: Description:Ubuntu Trusty Tahr (development branch) Release:14.04 Package: linux-image-extra-3.13.0-19-generic Version: 3.13.0-19.40 When playing audio through speakers on my Alienware 14 2014, the sound output is in mono until I plug a headphone in any of the two available headphone jacks (obviously, the auto-mute option must be disabled). When I do so, the sound starts to play in stereo. I would love the sound output to be stereo by default and not be forced to plug anything to achieve that. Attached is the alsa-info.sh output for my machine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1302090/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1414930] Re: [Lenovo ThinkPad 2015 models] Buttons of Synaptics trackpad doesn't work
VirtualBox seems to be a different story. Try adding nosmap to the kernel command line (see http://askubuntu.com/questions/581301 /virtualbox-stuck-on-starting-virtual-machine ), that worked for me. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1414930 Title: [Lenovo ThinkPad 2015 models] Buttons of Synaptics trackpad doesn't work Status in HWE Next Project: In Progress Status in The Linux Kernel: In Progress Status in libinput package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in linux source package in Trusty: Confirmed Status in systemd source package in Trusty: Confirmed Status in linux source package in Utopic: Confirmed Status in systemd source package in Utopic: Confirmed Bug description: Lenovo X1 3rd Carbon (201411-16196) Steps to reproduce the bug: 1, Log in to system 2, Click left/right/middle buttons of the touchpad Actual result: No response after clicking the buttons Expected results: Buttons work as expected behavirour ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-45-generic 3.13.0-45.74 [modified: boot/vmlinuz-3.13.0-45-generic] ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13 Uname: Linux 3.13.0-45-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: u 1598 F pulseaudio /dev/snd/controlC0: u 1598 F pulseaudio CurrentDesktop: Unity Date: Tue Jan 27 02:48:23 2015 HibernationDevice: RESUME=UUID=c553e9ba-b74b-43ad-8cf2-496531261e0f InstallationDate: Installed on 2015-01-27 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20150126) MachineType: LENOVO 20BTZ09ZUS ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic root=UUID=1d34e685-c98b-41f3-b649-87770517b194 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-45-generic N/A linux-backports-modules-3.13.0-45-generic N/A linux-firmware 1.127.11 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/27/2014 dmi.bios.vendor: LENOVO dmi.bios.version: N14ET24W (1.02 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BTZ09ZUS dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN14ET24W(1.02):bd10/27/2014:svnLENOVO:pn20BTZ09ZUS:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BTZ09ZUS:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BTZ09ZUS dmi.product.version: ThinkPad X1 Carbon 3rd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1414930/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1441210] Re: Roboto fonts make printer crash (fonts-android)
** Also affects: fonts-android (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782116 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-android in Ubuntu. https://bugs.launchpad.net/bugs/1441210 Title: Roboto fonts make printer crash (fonts-android) Status in fonts-android package in Ubuntu: New Status in fonts-android package in Debian: Unknown Bug description: As per https://code.google.com/p/android/issues/detail?id=38383, there has been issues with the Roboto font family regarding printing. These issues seem to have been resolved in the new version of the fonts made available by Google in 2014 here http://developer.android.com/design/style/typography.html. My setup: 1) Release: Ubuntu 14.04 LTS 2) Package: fonts-roboto 1:4.3-3ubuntu1.1 3) Expected Results: When using Roboto fonts in a document (pdf, odf, etc.), I should be able to print the document. 4) Current Results: Roboto fonts make the printer crash instead of printing. The printer I am using is a HP-Laser Jet P2055. Steps to reproduce: Install fonts-roboto package from Ubuntu Software Center. Produce a document in Libre Office with Roboto font and send to printer. Printer is crashing, need hard reboot. Workaround: (1) Remove fonts-roboto package from Ubuntu Software Center. (2) Download new version of the fonts made available by Google and save them in the .fonts folder in home directory. (3) Produce a new document with Roboto font and send to printer. (4) Document is printing. Basically, I think this package just need to be updated to use the latest fonts issued by Google. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-android/+bug/1441210/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1441210] Re: Roboto fonts make printer crash (fonts-android)
Sorry, i meant fonts-roboto, of course. https://launchpad.net/ubuntu/+archive/primary/+files/fonts- roboto_4.4.4r2-6_all.deb -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-android in Ubuntu. https://bugs.launchpad.net/bugs/1441210 Title: Roboto fonts make printer crash (fonts-android) Status in fonts-android package in Ubuntu: Incomplete Status in fonts-android package in Debian: Unknown Bug description: As per https://code.google.com/p/android/issues/detail?id=38383, there has been issues with the Roboto font family regarding printing. These issues seem to have been resolved in the new version of the fonts made available by Google in 2014 here http://developer.android.com/design/style/typography.html. My setup: 1) Release: Ubuntu 14.04 LTS 2) Package: fonts-roboto 1:4.3-3ubuntu1.1 3) Expected Results: When using Roboto fonts in a document (pdf, odf, etc.), I should be able to print the document. 4) Current Results: Roboto fonts make the printer crash instead of printing. The printer I am using is a HP-Laser Jet P2055. Steps to reproduce: Install fonts-roboto package from Ubuntu Software Center. Produce a document in Libre Office with Roboto font and send to printer. Printer is crashing, need hard reboot. Workaround: (1) Remove fonts-roboto package from Ubuntu Software Center. (2) Download new version of the fonts made available by Google and save them in the .fonts folder in home directory. (3) Produce a new document with Roboto font and send to printer. (4) Document is printing. Basically, I think this package just need to be updated to use the latest fonts issued by Google. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-android/+bug/1441210/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1441210] Re: Roboto fonts make printer crash (fonts-android)
Thanks! It just struck me... Possibly we already have the working fonts in the archive, since there was a new upstream version in vivid. Can you please install the vivid version of fonts-droid and let us know if it fixes the problem: https://launchpad.net/ubuntu/+archive/primary/+files/fonts- droid_4.4.4r2-6_all.deb ** Changed in: fonts-android (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-android in Ubuntu. https://bugs.launchpad.net/bugs/1441210 Title: Roboto fonts make printer crash (fonts-android) Status in fonts-android package in Ubuntu: Incomplete Status in fonts-android package in Debian: Unknown Bug description: As per https://code.google.com/p/android/issues/detail?id=38383, there has been issues with the Roboto font family regarding printing. These issues seem to have been resolved in the new version of the fonts made available by Google in 2014 here http://developer.android.com/design/style/typography.html. My setup: 1) Release: Ubuntu 14.04 LTS 2) Package: fonts-roboto 1:4.3-3ubuntu1.1 3) Expected Results: When using Roboto fonts in a document (pdf, odf, etc.), I should be able to print the document. 4) Current Results: Roboto fonts make the printer crash instead of printing. The printer I am using is a HP-Laser Jet P2055. Steps to reproduce: Install fonts-roboto package from Ubuntu Software Center. Produce a document in Libre Office with Roboto font and send to printer. Printer is crashing, need hard reboot. Workaround: (1) Remove fonts-roboto package from Ubuntu Software Center. (2) Download new version of the fonts made available by Google and save them in the .fonts folder in home directory. (3) Produce a new document with Roboto font and send to printer. (4) Document is printing. Basically, I think this package just need to be updated to use the latest fonts issued by Google. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-android/+bug/1441210/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1436046] Re: no SMS tracking
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: messaging-app (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1436046 Title: no SMS tracking Status in Usability Bugs in Ubuntu Phone: New Status in messaging-app package in Ubuntu: Confirmed Bug description: When sending a SMS on Android you will get a notification if the recipient receives the Message. On Ubuntu you will get no notification. This is leaving you in the dark about the status of your Message. There should be a received sign on the SMS-Message when it has reached the recipient. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntuphone/+bug/1436046/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1436043] Re: contacts can not be imported from sd card
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: address-book-app (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to address-book-app in Ubuntu. https://bugs.launchpad.net/bugs/1436043 Title: contacts can not be imported from sd card Status in Usability Bugs in Ubuntu Phone: New Status in address-book-app package in Ubuntu: Confirmed Bug description: There is no way to import a *.vcf File into Contacts from a SD-Card. If you email the *.vcf to Dekko and open the Attachment you will be asked to import the *.vcf to contacts. There should be a easy way to import vcf-Files from a SD-Card. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntuphone/+bug/1436043/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1441449] [NEW] [HP Z820] external microphone does not work, only records noises
Public bug reported: Records with a lot noises, barely can heard the sound. Step to reproduce: 1. plug your microphone to the front/rear micrphone jack 2. turn up the microphone volume in the system sound settings 3. open a terminal then type command: arecord test.wav, ctrl-c to inturrupt when you finish Expected result: when playing the recordings it should plays recognizable sound. Actual results: A lot noise in the recordings. Additional information: In the attached recording file, you should hear, Testing, One, Two, Three, Four, Five . ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-49.81-generic 3.13.11-ckt17 Uname: Linux 3.13.0-49-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1696 F pulseaudio /dev/snd/controlC0: ubuntu 1696 F pulseaudio CurrentDesktop: Unity Date: Wed Apr 8 01:32:46 2015 InstallationDate: Installed on 2015-04-02 (5 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: J63 v03.69 dmi.board.asset.tag: 2UA4242K12 dmi.board.name: 158B dmi.board.vendor: Hewlett-Packard dmi.board.version: 1.01 dmi.chassis.asset.tag: 2UA4242K12 dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrJ63v03.69:bd03/25/2014:svnHewlett-Packard:pnHPZ820Workstation:pvr:rvnHewlett-Packard:rn158B:rvr1.01:cvnHewlett-Packard:ct6:cvr: dmi.product.name: HP Z820 Workstation dmi.sys.vendor: Hewlett-Packard ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug trusty ** Attachment added: test.wav https://bugs.launchpad.net/bugs/1441449/+attachment/4369070/+files/test.wav -- 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/1441449 Title: [HP Z820] external microphone does not work, only records noises Status in alsa-driver package in Ubuntu: Confirmed Bug description: Records with a lot noises, barely can heard the sound. Step to reproduce: 1. plug your microphone to the front/rear micrphone jack 2. turn up the microphone volume in the system sound settings 3. open a terminal then type command: arecord test.wav, ctrl-c to inturrupt when you finish Expected result: when playing the recordings it should plays recognizable sound. Actual results: A lot noise in the recordings. Additional information: In the attached recording file, you should hear, Testing, One, Two, Three, Four, Five . ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-49.81-generic 3.13.11-ckt17 Uname: Linux 3.13.0-49-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1696 F pulseaudio /dev/snd/controlC0: ubuntu 1696 F pulseaudio CurrentDesktop: Unity Date: Wed Apr 8 01:32:46 2015 InstallationDate: Installed on 2015-04-02 (5 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: J63 v03.69 dmi.board.asset.tag: 2UA4242K12 dmi.board.name: 158B dmi.board.vendor: Hewlett-Packard dmi.board.version: 1.01 dmi.chassis.asset.tag: 2UA4242K12 dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrJ63v03.69:bd03/25/2014:svnHewlett-Packard:pnHPZ820Workstation:pvr:rvnHewlett-Packard:rn158B:rvr1.01:cvnHewlett-Packard:ct6:cvr: dmi.product.name: HP Z820 Workstation dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1441449/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1080107] Re: auto log-in doesn't function after logout
Bug 1396824 X server crash from autologin session returns to greeter, not autologin session is related. If the VNC server should survive a login or a logout it needs to run as root. Solutions are shown on http://askubuntu.com/questions/229989/how- to-setup-x11vnc-to-access-with-graphical-login-screen/528469#528469 and on http://wiki.ubuntuusers.de/VNC#x11vnc . -- 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/1080107 Title: auto log-in doesn't function after logout Status in Light Display Manager: Incomplete Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Enabling auto log-in for a user causes a ubuntu unity session to be started when the operating system is booted. The session has a Log Out... item on the pull-down menu item in the upper right corner. When this command is used, the session is logged out, but there is no subsequent auto log-in. Consequently, remote access by VNC (vinagre/vino) ceases. This problem has been around for several releases, but is definately present for the one below: lsb_release -rd Description: Ubuntu 12.04.1 LTS Release: 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1080107/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1439615] Re: close all applications make the background become a black page
** Branch linked: lp:~mzanetti/unity8/fix-blackground ** Changed in: unity8 (Ubuntu) Status: Triaged = In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1439615 Title: close all applications make the background become a black page Status in unity8 package in Ubuntu: In Progress Bug description: when i close the dash, the background turns black before dash restart. and if the dash can't restart anymore, the background keep a black page until i open another application. release: ubuntu vivid vervet 15.04 unity8： 8.02+15.04.20150320-0ubuntu1 platform: desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1439615/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1441564] Re: package libllvm3.4 (not installed) failed to install/upgrade: no se pudieron copiar los datos extraídos de './usr/lib/i386-linux-gnu/libLLVM-3.4.so.1' a '/usr/lib/i3
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to llvm-toolchain-3.4 in Ubuntu. https://bugs.launchpad.net/bugs/1441564 Title: package libllvm3.4 (not installed) failed to install/upgrade: no se pudieron copiar los datos extraídos de './usr/lib/i386-linux- gnu/libLLVM-3.4.so.1' a '/usr/lib/i386-linux-gnu/libLLVM-3.4.so.1 .dpkg-new': fin de fichero o de flujo inesperado Status in llvm-toolchain-3.4 package in Ubuntu: New Bug description: This error ocurred when install Sigil. Sorry, my english is bad. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libllvm3.4 (not installed) ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16 Uname: Linux 3.13.0-48-generic i686 ApportVersion: 2.14.1-0ubuntu3.8 Architecture: i386 Date: Wed Apr 8 12:11:44 2015 DuplicateSignature: package:libllvm3.4:(not installed):no se pudieron copiar los datos extraídos de './usr/lib/i386-linux-gnu/libLLVM-3.4.so.1' a '/usr/lib/i386-linux-gnu/libLLVM-3.4.so.1.dpkg-new': fin de fichero o de flujo inesperado ErrorMessage: no se pudieron copiar los datos extraídos de './usr/lib/i386-linux-gnu/libLLVM-3.4.so.1' a '/usr/lib/i386-linux-gnu/libLLVM-3.4.so.1.dpkg-new': fin de fichero o de flujo inesperado InstallationDate: Installed on 2015-03-28 (10 days ago) InstallationMedia: Lubuntu 12.04 Precise Pangolin - Release i386 (20120423) SourcePackage: llvm-toolchain-3.4 Title: package libllvm3.4 (not installed) failed to install/upgrade: no se pudieron copiar los datos extraídos de './usr/lib/i386-linux-gnu/libLLVM-3.4.so.1' a '/usr/lib/i386-linux-gnu/libLLVM-3.4.so.1.dpkg-new': fin de fichero o de flujo inesperado UpgradeStatus: Upgraded to trusty on 2015-03-28 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-3.4/+bug/1441564/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1413773] Re: [Regressions] Dash dnd icons rendered behind dash.
Hello Andrea, or anyone else affected, Accepted unity into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/unity/7.2.4+14.04.20150316-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: unity (Ubuntu Trusty) Status: In Progress = Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1413773 Title: [Regressions] Dash dnd icons rendered behind dash. Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [IMPACT] Dragged icons are rendered behind dash. [REGRESSION POTENTIAL] No known regression potential. [OTHER INFO] The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu Vivid Vervet dev release where it has been in production use for some time without apparent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1413773/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1430675] Re: fails to set up a bridged network interface
See also bug 1439109 which is about the missing networking symlink. -- 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/1430675 Title: fails to set up a bridged network interface Status in systemd package in Ubuntu: Incomplete Bug description: I have a simple bridge set up in /etc/network/interfaces so that the virtual machines running on that machine can use it and be on the same subnet. But with systemd it's not started on boot. The bridge is configured as follows auto br0 iface br0 inet dhcp bridge_ports eth0 bridge_stp off bridge_maxwait 5 reproduced now on a fresh vm. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1430675/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1410582] Re: [Trusty / Unity] Desktop got unlocked on its own.
Hello Jennifer, or anyone else affected, Accepted unity into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/unity/7.2.4+14.04.20150316-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: unity (Ubuntu Trusty) Status: In Progress = Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1410582 Title: [Trusty / Unity] Desktop got unlocked on its own. Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [Impact] Certain code paths may cause the Unity lockscreen to crash, which can allow the screen to be unlocked without a password entry. [Test Case] Unfortunately this bug only appears under certain race conditions and is not reliably reproduce able. [Regression Potential] The change in the code simply assumes that if a screen is already locked, then it is lockable this avoiding certain operations that are inherently racy. It is possible that this fix does not avoid all possible crash conditions in the lockscreen and there may still be unaccounted-for crashes in the lockscreen. [Other Info] This fix was cherry picked for Ubuntu 14.04 LTS from the Ubuntu Vivid Vervet dev release where it has been in testing for some time. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1410582/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1413790] Re: It's possible to bypasss lockscreen if user is in nopasswdlogin group.
Hello Andrea, or anyone else affected, Accepted unity into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/unity/7.2.4+14.04.20150316-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: unity (Ubuntu Trusty) Status: In Progress = Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1413790 Title: It's possible to bypasss lockscreen if user is in nopasswdlogin group. Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [IMPACT] A user is presented with a password dialog even if a member of the nopasswdlogin group (and may not have a password). [TEST CASE] (1) Create a test user. (2) Add the test user to the nopasswdlogin group. (3) Log in to a Unity session using that acocunt. (4) Lock the screen. (5) Attempt to unlock the screen: no password prompt should be presented. [REGRESSION POTENTIAL] Conceivably allowing a login with no authentication could present unexpected vulnerabilities in which unforseen code paths also exercise this function. Care has been taken by the developer to avoid such cases. [OTHER INFO] The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu Vivid Vervet dev release where it has been in production use for some time without apparent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1413790/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1430675] Re: fails to set up a bridged network interface
Sorry, I typoed. The correct commands are: sudo update-rc.d networking remove sudo update-rc.d networking defaults -- 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/1430675 Title: fails to set up a bridged network interface Status in systemd package in Ubuntu: Incomplete Bug description: I have a simple bridge set up in /etc/network/interfaces so that the virtual machines running on that machine can use it and be on the same subnet. But with systemd it's not started on boot. The bridge is configured as follows auto br0 iface br0 inet dhcp bridge_ports eth0 bridge_stp off bridge_maxwait 5 reproduced now on a fresh vm. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1430675/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1420544] Re: [SRU] Ubuntu instances on GCE should use NOOP scheduler
This bug was fixed in the package systemd - 204-5ubuntu20.11 --- systemd (204-5ubuntu20.11) trusty; urgency=medium [ Ben Howard ] * Add debian/extra/rules/62-google-cloudimg.rules: Use noop scheduler for Google virtio drives. (LP: #1420544) [ Martin Pitt ] * Add upstream-ignore-mmcrpmb.patch: Fix /dev/disk/by-path/ symlink of mmc RPMB partitions and don't blkid them to avoid kernel buffer I/O errors and timeouts. (LP: #1333140) -- Martin Pitt martin.p...@ubuntu.com Wed, 18 Feb 2015 12:11:49 +0100 ** Changed in: systemd (Ubuntu Trusty) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1420544 Title: [SRU] Ubuntu instances on GCE should use NOOP scheduler Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Won't Fix Status in systemd source package in Trusty: Fix Released Bug description: [IMPACT] By default, the Ubuntu kernel uses deadline. Google has identified that Cloud Workloads running on Ubuntu perform better using NOOP as the default scheduler. Google has requested that Google Cloud Compute (GCE) instances use NOOP as the default. [FIX] Add udev rule for GCE devices to use NOOP by default. [VALIDATION] 1. Boot Ubuntu instance on Google GCE 2. Confirm that the scheduler is deadline: $ cat /sys/block/sda/queue/scheduler noop [deadline] cfq 3. Install proposed udev package 4. Reboot 5. Confirm that schedule is now noop $ cat /sys/block/sda/queue/scheduler [noop] deadline cfq [RISK] This patch will affect currently running instances and on reboot they should see better performance. However, there is a risk that some users will experience a performance hit. [ORIGINAL REPORT] Per Google's request, Ubuntu instances should use NOOP as the default scheduler. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1420544/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1420544] Update Released
The verification of the Stable Release Update for systemd has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1420544 Title: [SRU] Ubuntu instances on GCE should use NOOP scheduler Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Won't Fix Status in systemd source package in Trusty: Fix Released Bug description: [IMPACT] By default, the Ubuntu kernel uses deadline. Google has identified that Cloud Workloads running on Ubuntu perform better using NOOP as the default scheduler. Google has requested that Google Cloud Compute (GCE) instances use NOOP as the default. [FIX] Add udev rule for GCE devices to use NOOP by default. [VALIDATION] 1. Boot Ubuntu instance on Google GCE 2. Confirm that the scheduler is deadline: $ cat /sys/block/sda/queue/scheduler noop [deadline] cfq 3. Install proposed udev package 4. Reboot 5. Confirm that schedule is now noop $ cat /sys/block/sda/queue/scheduler [noop] deadline cfq [RISK] This patch will affect currently running instances and on reboot they should see better performance. However, there is a risk that some users will experience a performance hit. [ORIGINAL REPORT] Per Google's request, Ubuntu instances should use NOOP as the default scheduler. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1420544/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1438046] Re: Can't download protected images
See also bug #1326070, that tracks the implementation of proper context menu support in oxide. ** Tags added: contextmenu ** Changed in: webbrowser-app Status: New = Confirmed ** Changed in: webbrowser-app Importance: Undecided = Medium ** Changed in: webbrowser-app Assignee: (unassigned) = Olivier Tilloy (osomon) ** Changed in: oxide Assignee: (unassigned) = Olivier Tilloy (osomon) ** Changed in: oxide Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to content-hub in Ubuntu. https://bugs.launchpad.net/bugs/1438046 Title: Can't download protected images Status in Oxide Webview: Confirmed Status in Web Browser App: Confirmed Status in content-hub package in Ubuntu: New Bug description: In the webbrowser app I login to a site (https://slack.com) which has private image sharing. Under every image there is a link, named 'Open original' that links to the image itself (like https://files.slack.com/files-pri/T02A1MKNL- F046U9A6V/img_20150328_103844.jpg). But to see the image you've to login to the website. So, when you try to download it (long press - save image) the browser calls the content hub, and indeed content hub saves img_20150328_103844.jpg in ~/Pictures, but the file is an .html file, and not the image, so the photo doesn't appear in the gallery app. The first thing IMO is to display an error if the file isn't valid, because it took me a while understand what was wrong with my dowload - it says 'Success' but then my photo isn't in the gallery. Then, there should be a way to download private resources from the web To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1438046/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1439109] Re: Network interface not coming up due to missing /etc/rcS.d/*networking
This bug was fixed in the package ifupdown - 0.7.48.1ubuntu8 --- ifupdown (0.7.48.1ubuntu8) vivid; urgency=medium * debian/postinst: Bring back missing /etc/rcS.d/networking symlink, to clean up after old broken upgrades. (LP: #1439109) -- Martin Pitt martin.p...@ubuntu.com Wed, 08 Apr 2015 12:02:39 +0200 ** Changed in: ifupdown (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1439109 Title: Network interface not coming up due to missing /etc/rcS.d/*networking Status in ifupdown package in Ubuntu: Fix Released Bug description: This used to work fine; now when I start my container there's no network inside. Manually bringing the interface up (ifup eth0 or systemctl start ifup@eth0) works. What information would be useful for you? ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-5ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 ApportVersion: 2.17-0ubuntu1 Architecture: amd64 Date: Wed Apr 1 11:35:28 2015 Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: System manufacturer System Product Name ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-10-generic root=UUID=980689ca-e7d9-4a99-8230-33b8b6e917cd ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw systemd.debug-shell nomdmonddf nomdmonisw nomdmonddf nomdmonisw SourcePackage: systemd UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1201 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V LX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1201:bd08/17/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1439109/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1438162] Re: [osk] Touching world icon on the keyboard should cycle through all active keyboard layouts
** Changed in: ubuntu-ux Assignee: Matthew Paul Thomas (mpt) = Jouni Helminen (jounihelminen) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1438162 Title: [osk] Touching world icon on the keyboard should cycle through all active keyboard layouts Status in Ubuntu UX bugs: Triaged Status in ubuntu-keyboard package in Ubuntu: Confirmed Bug description: I have 3 keyboard layouts active: English, Polish, Emoji. Now let's say the current layout is English. When I touch on the world icon the keyboard, the layout changes to Emoji. When I touch the icon again, the layout changes back to English. Then I touch it again, I get Emoji and so on. There's no way to change to the third layout without longpressing on the world icon and selecting the right layout there. I would expect the layout change to go through all active layouts, in my example English-Polish-Emoji-English and so on. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1438162/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1398170] Re: [greeter] The greeter and screen rotation
** Summary changed: - [design] [greeter] The greeter and screen rotation + [greeter] The greeter and screen rotation -- 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/1398170 Title: [greeter] The greeter and screen rotation Status in Ubuntu UX bugs: Triaged Status in unity8 package in Ubuntu: New Bug description: This is basically just a bug to ask a question of the design team: are there plans for rotation support for the greeter? Right now it doesn't really do anything special. I'd guess you don't want it to rotate on a phone factor, but maybe for a tablet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1398170/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1408745] Re: [power indicator] When auto brightness enabled, the brightness slider is ignored
** Changed in: ubuntu-ux Assignee: Matthew Paul Thomas (mpt) = Paty Davila (dizzypaty) -- 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/1408745 Title: [power indicator] When auto brightness enabled, the brightness slider is ignored Status in Ubuntu UX bugs: Triaged Status in unity8 package in Ubuntu: Confirmed Bug description: Steps to repro: 1. Open Power indicator 2. Disable auto brightness. Move the slider to change screen brightness - all ok 3. Enable auto brightness. Try moving slider Expected result brightness still adjusted, but tempered based on the auto's decisions Actual result brightness unchanged Device: krillin See https://wiki.ubuntu.com/BrightnessAndDisplays#Phone for the design guidance of this To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1408745/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1441592] [NEW] Unity restart broken (Vivid)
Public bug reported: Restarting Unity no longer works properly in Ubuntu 15.04 Vivid Vervet. Steps to reproduce: press ALT + F2, type Unity and press ENTER. What should occur: Unity should be restarted without logging out the user. What actually occurs: the LightDM login screen greeter shows up (so the user is logged out) instead of just restarting Unity. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150330-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3 Uname: Linux 3.19.0-12-generic x86_64 ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Wed Apr 8 14:50:13 2015 InstallationDate: Installed on 2015-03-11 (28 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150306) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages vivid -- 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/1441592 Title: Unity restart broken (Vivid) Status in unity package in Ubuntu: New Bug description: Restarting Unity no longer works properly in Ubuntu 15.04 Vivid Vervet. Steps to reproduce: press ALT + F2, type Unity and press ENTER. What should occur: Unity should be restarted without logging out the user. What actually occurs: the LightDM login screen greeter shows up (so the user is logged out) instead of just restarting Unity. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150330-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3 Uname: Linux 3.19.0-12-generic x86_64 ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Wed Apr 8 14:50:13 2015 InstallationDate: Installed on 2015-03-11 (28 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150306) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1441592/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1439109] Re: Network interface not coming up due to missing /etc/rcS.d/*networking
fixed it for me, thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1439109 Title: Network interface not coming up due to missing /etc/rcS.d/*networking Status in ifupdown package in Ubuntu: Fix Released Bug description: This used to work fine; now when I start my container there's no network inside. Manually bringing the interface up (ifup eth0 or systemctl start ifup@eth0) works. What information would be useful for you? ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-5ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 ApportVersion: 2.17-0ubuntu1 Architecture: amd64 Date: Wed Apr 1 11:35:28 2015 Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: System manufacturer System Product Name ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-10-generic root=UUID=980689ca-e7d9-4a99-8230-33b8b6e917cd ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw systemd.debug-shell nomdmonddf nomdmonisw nomdmonddf nomdmonisw SourcePackage: systemd UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1201 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V LX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1201:bd08/17/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1439109/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1441487] Re: Running any Java program produces messages in the terminal
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/1441487 Title: Running any Java program produces messages in the terminal Status in unity package in Ubuntu: Confirmed Bug description: I just installed Ubuntu 15.04 and was surprised to discover that when running a Java based program from the terminal in Unity, the following message appears: Picked up JAVA_TOOL_OPTIONS: -javaagent:/usr/share/java/jayatanaag.jar. I tried several programs and it is all the same. Some Java programs with enabled Java security produce even some error messages and crash. If I press Ctrl+Alt+F1 to start a new terminal session without a GUI and run a Java program (without a GUI), I don't experience this problem. Back in Unity, if I unset JAVA_TOOL_OPTIONS in the terminal and run a Java program, it works fine. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150330-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Wed Apr 8 10:11:10 2015 InstallationDate: Installed on 2015-03-30 (9 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Beta amd64 (20150326) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1441487/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1404030] Re: uninstalled apps should not show up when checking for updates
this bu report is pretty old, click-update-manager does not exist on the images anymore and i am not sure where it was merged ... (unity-scope- click (?)) ... adding a canonical-system-image task for the product team for further triage ... ** Also affects: canonical-devices-system-image Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click-update-manager in Ubuntu. https://bugs.launchpad.net/bugs/1404030 Title: uninstalled apps should not show up when checking for updates Status in the base for Ubuntu mobile products: New Status in click-update-manager package in Ubuntu: Confirmed Bug description: I have uninstalled the sudoku app, but when I check for updates, I am shown that a new version of sudoku is available. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1404030/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1440602] Re: Graphics corruption after suspend/resume cycle
Does it happen with just one monitor? ** Changed in: xorg (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1440602 Title: Graphics corruption after suspend/resume cycle Status in xorg package in Ubuntu: Incomplete Bug description: I have observed two forms of graphics corruption after a suspend/resume cycle: 1) Checkerboard artifacts in approximately the top 1/8 to 1/4 of the screen. This can be observed from the following video, where I am highlighting global menu entries with the mouse: https://www.dropbox.com/s/ez2v03oetppecgx/VID_20150324_020612.mp4?dl=0 A similar effect can also be observed while dragging windows around near the top of the screen. 2) The virtual terminals no longer take up the full screen area, and are surrounded by a pattern which appears similar to noise or snow on old TVs. Here's how it appears on my screen: https://www.dropbox.com/s/7hj8qi3w3qc35jb/IMG_20150405_155434.jpg?dl=0 While these two issues seem quite unrelated, they both seem to happen _only_ after a suspend/resume cycle, so the underlying issue might be related between them. Relevant hardware details: -Video card: Radeon R7 260X (w/ the radeonsi driver) -Main display resolution: 2560x1440 -Secondary display resolution: 1200x1920 (portrait mode) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-11.11-generic 3.19.3 Uname: Linux 3.19.0-11-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.17-0ubuntu1 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 Apr 5 16:00:07 2015 DistUpgraded: 2015-03-27 18:17:09,531 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Bonaire XTX [Radeon R7 260X] [1002:6658] (prog-if 00 [VGA controller]) Subsystem: VISIONTEK Device [1545:7260] InstallationDate: Installed on 2014-06-06 (302 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: Gigabyte Technology Co., Ltd. GA-970A-D3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-11-generic root=UUID=d254b01f-2bf2-4b57-acdc-c796786f4c4c ro SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to vivid on 2015-03-27 (8 days ago) dmi.bios.date: 12/16/2013 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F13b dmi.board.name: GA-970A-D3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF13b:bd12/16/2013:svnGigabyteTechnologyCo.,Ltd.:pnGA-970A-D3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-970A-D3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-970A-D3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.12.1+15.04.20150330-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.59-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Sun Apr 5 17:47:11 2015 xserver.configfile: default xserver.errors: evdev: Microsoft Natural® Ergonomic Keyboard 4000: Unable to open evdev device /dev/input/event4. evdev: Microsoft Natural® Ergonomic Keyboard 4000: Unable to open evdev device /dev/input/event5. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.17.1-0ubuntu3 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1440602/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1441564] [NEW] package libllvm3.4 (not installed) failed to install/upgrade: no se pudieron copiar los datos extraídos de './usr/lib/i386-linux-gnu/libLLVM-3.4.so.1' a '/usr/lib/
Public bug reported: This error ocurred when install Sigil. Sorry, my english is bad. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libllvm3.4 (not installed) ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16 Uname: Linux 3.13.0-48-generic i686 ApportVersion: 2.14.1-0ubuntu3.8 Architecture: i386 Date: Wed Apr 8 12:11:44 2015 DuplicateSignature: package:libllvm3.4:(not installed):no se pudieron copiar los datos extraídos de './usr/lib/i386-linux-gnu/libLLVM-3.4.so.1' a '/usr/lib/i386-linux-gnu/libLLVM-3.4.so.1.dpkg-new': fin de fichero o de flujo inesperado ErrorMessage: no se pudieron copiar los datos extraídos de './usr/lib/i386-linux-gnu/libLLVM-3.4.so.1' a '/usr/lib/i386-linux-gnu/libLLVM-3.4.so.1.dpkg-new': fin de fichero o de flujo inesperado InstallationDate: Installed on 2015-03-28 (10 days ago) InstallationMedia: Lubuntu 12.04 Precise Pangolin - Release i386 (20120423) SourcePackage: llvm-toolchain-3.4 Title: package libllvm3.4 (not installed) failed to install/upgrade: no se pudieron copiar los datos extraídos de './usr/lib/i386-linux-gnu/libLLVM-3.4.so.1' a '/usr/lib/i386-linux-gnu/libLLVM-3.4.so.1.dpkg-new': fin de fichero o de flujo inesperado UpgradeStatus: Upgraded to trusty on 2015-03-28 (10 days ago) ** Affects: llvm-toolchain-3.4 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to llvm-toolchain-3.4 in Ubuntu. https://bugs.launchpad.net/bugs/1441564 Title: package libllvm3.4 (not installed) failed to install/upgrade: no se pudieron copiar los datos extraídos de './usr/lib/i386-linux- gnu/libLLVM-3.4.so.1' a '/usr/lib/i386-linux-gnu/libLLVM-3.4.so.1 .dpkg-new': fin de fichero o de flujo inesperado Status in llvm-toolchain-3.4 package in Ubuntu: New Bug description: This error ocurred when install Sigil. Sorry, my english is bad. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libllvm3.4 (not installed) ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16 Uname: Linux 3.13.0-48-generic i686 ApportVersion: 2.14.1-0ubuntu3.8 Architecture: i386 Date: Wed Apr 8 12:11:44 2015 DuplicateSignature: package:libllvm3.4:(not installed):no se pudieron copiar los datos extraídos de './usr/lib/i386-linux-gnu/libLLVM-3.4.so.1' a '/usr/lib/i386-linux-gnu/libLLVM-3.4.so.1.dpkg-new': fin de fichero o de flujo inesperado ErrorMessage: no se pudieron copiar los datos extraídos de './usr/lib/i386-linux-gnu/libLLVM-3.4.so.1' a '/usr/lib/i386-linux-gnu/libLLVM-3.4.so.1.dpkg-new': fin de fichero o de flujo inesperado InstallationDate: Installed on 2015-03-28 (10 days ago) InstallationMedia: Lubuntu 12.04 Precise Pangolin - Release i386 (20120423) SourcePackage: llvm-toolchain-3.4 Title: package libllvm3.4 (not installed) failed to install/upgrade: no se pudieron copiar los datos extraídos de './usr/lib/i386-linux-gnu/libLLVM-3.4.so.1' a '/usr/lib/i386-linux-gnu/libLLVM-3.4.so.1.dpkg-new': fin de fichero o de flujo inesperado UpgradeStatus: Upgraded to trusty on 2015-03-28 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-3.4/+bug/1441564/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1441325] Re: Sound plays randomly or not at all
Thanks for the tip with MediaPlayer element. Unfortunately in my case it's too laggy. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtmultimedia-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1441325 Title: Sound plays randomly or not at all Status in Media Hub: Invalid Status in QT Ubuntu Media: New Status in qtmultimedia-opensource-src package in Ubuntu: New Bug description: I'm making an simple app. In the app on a click of a button a sound should play. Unfortunately it plays sometimes but mostly not at all. Here's the place in the app code where the sound I want to play is: http://bazaar.launchpad.net/~mpredotka/+junk/pop-that-wrap/view/head:/Bubble.qml#L16 When I run my app from SDK to my bq phone I get errors like this: Debug-helper Environment: confined Debug-helper Environment initialized, starting the application Debug-helper Executing /usr/bin/qmlscene['/usr/bin/qmlscene', '$@', 'Main.qml'] shm_open() failed: Permission denied process 26220: arguments to dbus_message_new_method_call() were incorrect, assertion _dbus_check_is_valid_path (path) failed in file ../../dbus/dbus-message.c line 1266. This is normally a bug in some application using the D-Bus library. process 26220: arguments to dbus_message_set_auto_start() were incorrect, assertion message != NULL failed in file ../../dbus/dbus-message.c line 2951. This is normally a bug in some application using the D-Bus library. process 26220: arguments to dbus_message_iter_init_append() were incorrect, assertion message != NULL failed in file ../../dbus/dbus-message.c line 2348. This is normally a bug in some application using the D-Bus library. QDBusConnection: error: could not send message to service org.freedesktop.NetworkManager path interface org.freedesktop.DBus.Introspectable member Introspect: using blocking call! Using blocking call! process 26220: arguments to dbus_message_new_method_call() were incorrect, assertion _dbus_check_is_valid_path (path) failed in file ../../dbus/dbus-message.c line 1266. This is normally a bug in some application using the D-Bus library. process 26220: arguments to dbus_message_set_auto_start() were incorrect, assertion message != NULL failed in file ../../dbus/dbus-message.c line 2951. This is normally a bug in some application using the D-Bus library. process 26220: arguments to dbus_message_iter_init_append() were incorrect, assertion message != NULL failed in file ../../dbus/dbus-message.c line 2348. This is normally a bug in some application using the D-Bus library. QDBusConnection: error: could not send message to service org.freedesktop.NetworkManager path interface org.freedesktop.DBus.Introspectable member Introspect: using blocking call! Using blocking call! UbuntuWindow::handleSurfaceFocusChange(focused=true) UbuntuWindow::handleSurfaceResize(width=540, height=919) UbuntuClipboard - Got invalid serialized mime data. Ignoring it. QSoundEffect(pulseaudio): Error in pulse audio stream QSoundEffect(pulseaudio): Error in pulse audio stream QSoundEffect(pulseaudio): Error in pulse audio stream QSoundEffect(pulseaudio): Error in pulse audio stream To manage notifications about this bug go to: https://bugs.launchpad.net/media-hub/+bug/1441325/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368658] Re: [Notifications] Implement new visual designs for Snap Decisions and other notifications
** Changed in: ubuntu-ux Assignee: Paty Davila (dizzypaty) = Grazina (boroskograzina) -- 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/1368658 Title: [Notifications] Implement new visual designs for Snap Decisions and other notifications Status in Ubuntu UX bugs: Triaged Status in Server and client library for desktop notifications in Unity: New Status in unity8 package in Ubuntu: New Status in unity8 package in Ubuntu RTM: New Bug description: The poor discoverabiltiy of the text field for snap decision (lack of contrast) One participant discovered the snap decision, however, after he clicked on the message button, he could not locate the text field immeditately as it was blended into the background. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1368658/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1258496] Re: show wireless encryption type
It turns out that the attack I described is called the evil twin. http://en.wikipedia.org/wiki/Evil_twin_%28wireless_networks%29 Antti, if you don't mind, I'll retarget this bug report towards thwarting that attack. Showing the encryption type would not be a complete solution to disambiguating identically-named networks, whether they were coincidental or malicious. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1258496 Title: show wireless encryption type Status in indicator-network package in Ubuntu: Confirmed Bug description: Currently the indicator only shows whether or not a wireless network is secured, by showing a padlock. In a situation where we have two accesspoints which both have the same ESSID (name) but different encryption (e.g. WEP vs. WPA) they provide two separate networks. Now the indicator shows two identical items and the user has no way of figuring out which is which. Above scenario is a very rare one, but still completely valid. Neither nm-applet or macosx networking menu bother to deal with this situation, they just show two identical networks, but Android is always showing the encryption scheme beneath the network name. We can either A) do nothing B) always have the encryption type visible somehow C) be smart about it and only show the encryption type when we detect that the name and padlock is not enough To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1258496/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1381041] Re: [TOPBLOCKER] Network indicator is sometimes blank
This was fixed in 0.5.1+14.10.20141031.3~rtm-0ubuntu1 ** Changed in: indicator-network (Ubuntu Utopic) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1381041 Title: [TOPBLOCKER] Network indicator is sometimes blank Status in indicator-network package in Ubuntu: Fix Released Status in indicator-network source package in Utopic: Fix Released Status in indicator-network source package in Vivid: Fix Released Status in indicator-network package in Ubuntu RTM: Fix Released Bug description: This is on krillin r103, but it has been happening for a while. See attached photo. I am not certain what triggers it. but I think it may happen when wifi APs become in and out of range while walking around town (as if the list does not refresh reliably). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1381041/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 933296] Re: LibreOffice-Impress can not play slide show (when using new cairo from ppas, not affecting Ubuntu archive)
** Changed in: cairo (Ubuntu) Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cairo in Ubuntu. https://bugs.launchpad.net/bugs/933296 Title: LibreOffice-Impress can not play slide show (when using new cairo from ppas, not affecting Ubuntu archive) Status in libcairo - cairo vector graphics library: Fix Released Status in cairo package in Ubuntu: Fix Released Status in cairo package in Debian: Fix Released Bug description: I am use netbook acer with CPU AMD dual-Core processor C-60 LibreOffice-Impress can not play slide show WORKAROUND: Tools-options-LibreOffice-view, uncheck Use hardware acceleration ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: libreoffice-core 1:3.3.4-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-13.55-generic 2.6.38.8 Uname: Linux 2.6.38-13-generic i686 NonfreeKernelModules: wl Architecture: i386 Date: Thu Feb 16 14:23:25 2012 InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: Upgraded to natty on 2012-02-03 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/libcairo/+bug/933296/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368811] Re: [SDK] Bottom edge behaviour needs refining
** Changed in: ubuntu-ux Status: In Progress = Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1368811 Title: [SDK] Bottom edge behaviour needs refining Status in Ubuntu UX bugs: Triaged Status in ubuntu-ui-toolkit package in Ubuntu: Incomplete Bug description: - Move the bottom edge hint into the SDK so it's behavour is consistent across apps, and make the hiding of the bottom edge hint less aggressive. - When the user grabs the bottom edge, leave the tab visible until the user releases - Find a way to make it possible to pull down screens accessed via the bottom edge to make the gesture reversible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1368811/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1367818] Re: [indicator] + [dialog] Silent Mode causes no indication of a change in [icon] state.
** Changed in: ubuntu-ux Assignee: Matthew Paul Thomas (mpt) = Paty Davila (dizzypaty) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-sound in Ubuntu. https://bugs.launchpad.net/bugs/1367818 Title: [indicator] + [dialog] Silent Mode causes no indication of a change in [icon] state. Status in the base for Ubuntu mobile products: Fix Released Status in Ubuntu UX bugs: Triaged Status in indicator-sound package in Ubuntu: Fix Released Status in indicator-sound package in Ubuntu RTM: Fix Released Bug description: - When the sound is muted, the volume icon to the left of the volume slider should have a red / running through it. - Add an explicit Mute button to the sound indicator menu. - Pressing and holding the icon to the left of the volume slider should mute volume straight away. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1367818/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 935750] Re: [dash] Search field not common to lenses
Marking as won't fix because this bug is assigned to the Unity8 project where it is not relevant. ** Changed in: ubuntu-ux Status: Triaged = Won't Fix ** Changed in: ubuntu-ux Importance: Medium = Undecided -- 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/935750 Title: [dash] Search field not common to lenses Status in Ubuntu UX bugs: Won't Fix Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: After typing in the home lens's search field and seeing no results, I figured I was using the wrong lens so I switched to another one. Because the search field is specific to the lens, I had to retype my search terms. I didn't realize until I started this report that the home lens search would search all the lenses. (Or, I'm assuming that's what it does now, based on a different search which produced results.) - UPDATE: This is a bug for the desktop, Unity7. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/935750/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1404030] Re: uninstalled apps should not show up when checking for updates
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: click-update-manager (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click-update-manager in Ubuntu. https://bugs.launchpad.net/bugs/1404030 Title: uninstalled apps should not show up when checking for updates Status in the base for Ubuntu mobile products: New Status in click-update-manager package in Ubuntu: Confirmed Bug description: I have uninstalled the sudoku app, but when I check for updates, I am shown that a new version of sudoku is available. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1404030/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1404030] Re: uninstalled apps should not show up when checking for updates
To me it happens also with another system app: Remainders. I am on the bq device with the stable channel installed. I uninstalled the app some days ago and yesterday it showed up in the updates. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click-update-manager in Ubuntu. https://bugs.launchpad.net/bugs/1404030 Title: uninstalled apps should not show up when checking for updates Status in the base for Ubuntu mobile products: New Status in click-update-manager package in Ubuntu: Confirmed Bug description: I have uninstalled the sudoku app, but when I check for updates, I am shown that a new version of sudoku is available. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1404030/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1439988] Re: package init-system-helpers 1.22ubuntu4 failed to install/upgrade: trying to overwrite '/lib/init/apparmor-profile-load', which is also in package upstart-bin 1.13.2
I can confirm that the problem is resolved for me on a vivid install. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/1439988 Title: package init-system-helpers 1.22ubuntu4 failed to install/upgrade: trying to overwrite '/lib/init/apparmor-profile-load', which is also in package upstart-bin 1.13.2-0ubuntu9 Status in init-system-helpers package in Ubuntu: Fix Released Bug description: x ProblemType: Package DistroRelease: Ubuntu 15.04 Package: init-system-helpers 1.22ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 Date: Fri Apr 3 10:20:08 2015 DpkgTerminalLog: Preparing to unpack .../init-system-helpers_1.22ubuntu6_all.deb ... Unpacking init-system-helpers (1.22ubuntu6) over (1.22ubuntu4) ... dpkg: error processing archive /var/cache/apt/archives/init-system-helpers_1.22ubuntu6_all.deb (--unpack): trying to overwrite '/lib/init/apparmor-profile-load', which is also in package upstart-bin 1.13.2-0ubuntu9 DuplicateSignature: package:init-system-helpers:1.22ubuntu4:trying to overwrite '/lib/init/apparmor-profile-load', which is also in package upstart-bin 1.13.2-0ubuntu9 ErrorMessage: trying to overwrite '/lib/init/apparmor-profile-load', which is also in package upstart-bin 1.13.2-0ubuntu9 InstallationDate: Installed on 2015-03-21 (12 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150321) PackageArchitecture: all RelatedPackageVersions: dpkg 1.17.24ubuntu1 apt 1.0.9.7ubuntu3 SourcePackage: init-system-helpers Title: package init-system-helpers 1.22ubuntu4 failed to install/upgrade: trying to overwrite '/lib/init/apparmor-profile-load', which is also in package upstart-bin 1.13.2-0ubuntu9 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1439988/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1404030] Re: uninstalled apps should not show up when checking for updates
Ok ,so I reported a new one here on system settings https://bugs.launchpad.net/ubuntu/+source/ubuntu-system- settings/+bug/1441594 (there were other bugs about updates there) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click-update-manager in Ubuntu. https://bugs.launchpad.net/bugs/1404030 Title: uninstalled apps should not show up when checking for updates Status in the base for Ubuntu mobile products: New Status in click-update-manager package in Ubuntu: Confirmed Bug description: I have uninstalled the sudoku app, but when I check for updates, I am shown that a new version of sudoku is available. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1404030/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1397963] Re: [greeter] SIM PIN + passcode screens too similar
** Summary changed: - [design] [SIM PIN] + [passcode] screens too similar + [greeter] SIM PIN + passcode screens too similar ** Changed in: ubuntu-ux Assignee: Matthew Paul Thomas (mpt) = Olga Kemmet (olga-kemmet) -- 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/1397963 Title: [greeter] SIM PIN + passcode screens too similar Status in Ubuntu UX bugs: Triaged Status in unity8 package in Ubuntu: New Bug description: unity8 8.01+15.04.20141125.2-0ubuntu1, Ubuntu 15.04 The SIM PIN and lockscreen dialogs for passcode are too similar to one another, I repeatedly end up putting my passcode as SIM PIN, this could lead to locking your SIM card. Fixing this might also fix bug 1387207. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1397963/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1439109] Re: Network interface not coming up due to missing /etc/rcS.d/*networking
I uploaded a new ifupdown which cleans this up on upgrades, needs release team review. ** Changed in: ifupdown (Ubuntu) Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1439109 Title: Network interface not coming up due to missing /etc/rcS.d/*networking Status in ifupdown package in Ubuntu: Fix Committed Bug description: This used to work fine; now when I start my container there's no network inside. Manually bringing the interface up (ifup eth0 or systemctl start ifup@eth0) works. What information would be useful for you? ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-5ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 ApportVersion: 2.17-0ubuntu1 Architecture: amd64 Date: Wed Apr 1 11:35:28 2015 Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: System manufacturer System Product Name ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-10-generic root=UUID=980689ca-e7d9-4a99-8230-33b8b6e917cd ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw systemd.debug-shell nomdmonddf nomdmonisw nomdmonddf nomdmonisw SourcePackage: systemd UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1201 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V LX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1201:bd08/17/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1439109/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1441570] [NEW] System becomes unresponsive during normal usage
Public bug reported: The system becomes unresponsive (including stuttering audio, slow mouse cursor, freezing) after an hour or so of usage (sometimes more and sometimes less). Usage at the time was a web browser idling (observed with both Chromium and Firefox) and a music player (Clementine) in the background. There were no CPU intensive applications running at the time. I was able to capture cpu usage during an episode with the following command (nice set to -20).: 'while true; do ps -eo pcpu,pid,user,args | sort -k 1 -nr | head -30 logfile; echo -e \n`date` logfile; sync; sleep 1; done' Attached is an excerpt from the generated log file. Ubuntu Version: Ubuntu Vivid Vervet (development branch) 15.04 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3 Uname: Linux 3.19.0-12-generic x86_64 ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Wed Apr 8 20:15:52 2015 EcryptfsInUse: Yes SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug fonts kubuntu vivid ** Attachment added: Logfile output https://bugs.launchpad.net/bugs/1441570/+attachment/4369312/+files/cpuusage.txt ** Package changed: xorg (Ubuntu) = ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1441570 Title: System becomes unresponsive during normal usage Status in Ubuntu: New Bug description: The system becomes unresponsive (including stuttering audio, slow mouse cursor, freezing) after an hour or so of usage (sometimes more and sometimes less). Usage at the time was a web browser idling (observed with both Chromium and Firefox) and a music player (Clementine) in the background. There were no CPU intensive applications running at the time. I was able to capture cpu usage during an episode with the following command (nice set to -20).: 'while true; do ps -eo pcpu,pid,user,args | sort -k 1 -nr | head -30 logfile; echo -e \n`date` logfile; sync; sleep 1; done' Attached is an excerpt from the generated log file. Ubuntu Version: Ubuntu Vivid Vervet (development branch) 15.04 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3 Uname: Linux 3.19.0-12-generic x86_64 ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Wed Apr 8 20:15:52 2015 EcryptfsInUse: Yes SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1441570/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1423413] Re: [XPS 13 9343, Realtek ALC3263, Mic, Internal] No sound at all
** Changed in: alsa-driver (Ubuntu) Importance: Medium = High -- 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/1423413 Title: [XPS 13 9343, Realtek ALC3263, Mic, Internal] No sound at all Status in Dell Sputnik: New Status in alsa-driver package in Ubuntu: Confirmed Bug description: Note that I am forcing the audio into HDA mode. (It has two modes: HDA and I2S.) In HDA mode, audio out works. The mic is known with a previous version of ALSA (Sept 3 2014 snapshot). ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Uname: Linux 3.18.0-13-generic x86_64 ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0c: jared 4299 F...m arecord /dev/snd/pcmC1D0p: jared 2929 F...m pulseaudio /dev/snd/controlC1: jared 2929 F pulseaudio /dev/snd/controlC0: jared 2929 F pulseaudio CurrentDesktop: Unity Date: Wed Feb 18 19:40:01 2015 InstallationDate: Installed on 2014-11-03 (107 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingPlaybackStderr: o p e n ( ) : N o s u c h f i l e o r d i r e c t o r y Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_AlsaRecordingTestStderr: a r e c o r d : m a i n : 7 2 2 : a u d i o o p e n e r r o r : D e v i c e o r r e s o u r c e b u s y Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0c: jared 4299 F...m arecord /dev/snd/controlC1: jared 2929 F pulseaudio /dev/snd/controlC0: jared 2929 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [XPS 13 9343, Realtek ALC3263, Mic, Internal] No sound at all UpgradeStatus: Upgraded to vivid on 2015-01-08 (41 days ago) dmi.bios.date: 02/03/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 0144PA dmi.board.vendor: Dell Inc. dmi.board.version: X04 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA01:bd02/03/2015:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0144PA:rvrX04:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1423413/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1401859] Re: Remove snap-decision fallback
** Changed in: ubuntu-ux Assignee: Matthew Paul Thomas (mpt) = Paty Davila (dizzypaty) ** Summary changed: - Remove snap-decision fallback + [Online Accounts, Scopes] Remove snap-decision fallback -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-system-settings- online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1401859 Title: [Online Accounts, Scopes] Remove snap-decision fallback Status in Online Accounts setup for Ubuntu Touch: Fix Released Status in Ubuntu UX bugs: Triaged Status in ubuntu-system-settings-online-accounts package in Ubuntu: Fix Released Bug description: Some months ago we implemented a snap-decision for prompting the user to re-authenticate an account when the client is not connected to Mir (such is the case for scopes, accounts-polld and sync-monitor). This change was meant to avoid falling into cases where the client would stop working because unable to obtain a new valid token, and it's working. However, it was not approved by design, and due to bug 1352251 it has a negative impact on the user experience. Therefore, we want to get rid of it. The implementation of the reverse trust prompt hosting will render the snap-decision unnecessary for those case where the UI-less process has a companion UI process running; for the other cases a solution is currently being discussed with design. A proposal is to let the UI- less process record the failure in a location readable by the companion UI application (which is not running at the same time), for example by mark the account as failing in the accounts DB. Additionally, it could emit a notification which, once activated, would launch the companion application. And when this application starts and detects that the account needs to be re-authenticated, it takes care of doing that. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-system-settings-online-accounts/+bug/1401859/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1350993] Re: [Dash] Support link should be clickable, app preview shows mailto links with mailto text
** Summary changed: - Support link should be clickable, app preview shows mailto links with mailto text + [Dash] Support link should be clickable, app preview shows mailto links with mailto text -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-click in Ubuntu. https://bugs.launchpad.net/bugs/1350993 Title: [Dash] Support link should be clickable, app preview shows mailto links with mailto text Status in Ubuntu UX bugs: Triaged Status in unity-scope-click package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: When uploading an app to the store we're given a field to put a support link in. It's recommended to put an http or mailto link in. I have put mailto: links in mine. With the latest click scope I now see some details about the app, and the support link actually says mailto:a...@popey.com; when it probably should be clickable whether it's a mailto link or an http* link. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1350993/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1426559] Re: [Shell] Bring the HUD back to Unity 8
** Changed in: ubuntu-ux Assignee: Benjamin Keyser (bjkeyser) = John Lea (johnlea) ** Changed in: ubuntu-ux Status: Triaged = Opinion -- 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/1426559 Title: [Shell] Bring the HUD back to Unity 8 Status in Ubuntu UX bugs: Opinion Status in unity8 package in Ubuntu: New Bug description: One of the most innovative, useful, and wildly popular features introduced into Unity 7 was the HUD. Unity 8 currently does not have it. When Unity 8 was started, we had a way of accessing the HUD with a long-swipe from the bottom edge. However, the API to use it was late in being added to the SDK, and changed in incompatible ways after it was available, and as a result only a few apps (including one of my own) had taken advantage of it. Moreover user testing showed that the swipe-up activation was not easily discover-able by users. When the toolbar/header was redesigned and the bottom-edge gesture given to app developers, the way of accessing the HUD was removed, and the API was removed before the first supported API freeze. Before switching to Unity 8 on the desktop we will need to re- introduce the HUD into Unity, to avoid a feature regression that many have come to expect and appreciate. Moreover, we should re-introduce it on the phone so that apps can once again start taking advantage of it, so we can learn how to provide new use cases and user interactions for phone/tablet apps. In order to match, as much as possible, the Unity 7 way of accessing the HUD, my recommendation would be to implement it like an Indicator, but always on the far left of the panel. Then it would be touch- accessible with a swipe down from the top, or switchable from within the drop-down of another indicator, placing it at the same screen position as it is on the Unity 7 desktop. Placing the window title or simple Menu in that location of the panel (or switching between them, depending on available space) would aid in discovery of the feature. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1426559/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1441580] [NEW] License checking script doesn't detect issues detected by Jenkins
Public bug reported: The license checking script stored in the toolkit tree doesn't detect the same issues PBuilder Jenkins is detecting. Should be updated. ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: Medium Assignee: Loïc Molinari (loic.molinari) Status: In Progress ** Branch linked: lp:~loic.molinari/ubuntu-ui-toolkit/ubuntu-ui-toolkit- sync-check-license-script-with-pbuilder-jenkins -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1441580 Title: License checking script doesn't detect issues detected by Jenkins Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Bug description: The license checking script stored in the toolkit tree doesn't detect the same issues PBuilder Jenkins is detecting. Should be updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1441580/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1430675] Re: fails to set up a bridged network interface
*** This bug is a duplicate of bug 1439109 *** https://bugs.launchpad.net/bugs/1439109 Fixed for me. zoolook@venkman:~$ ls /etc/rcS.d/ | grep net zoolook@venkman:~$ sudo update-rc.d networking remove zoolook@venkman:~$ sudo update-rc.d networking defaults zoolook@venkman:~$ ls /etc/rcS.d/ | grep net 0 lrwxrwxrwx 1 root root 20 abr 8 08:23 S11networking - ../init.d/networking* After reboot, my three bridges came up as they should. Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1430675 Title: fails to set up a bridged network interface Status in systemd package in Ubuntu: Incomplete Bug description: I have a simple bridge set up in /etc/network/interfaces so that the virtual machines running on that machine can use it and be on the same subnet. But with systemd it's not started on boot. The bridge is configured as follows auto br0 iface br0 inet dhcp bridge_ports eth0 bridge_stp off bridge_maxwait 5 reproduced now on a fresh vm. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1430675/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1238174] Re: [Notifications] notifications / snap decisions over indicators blend into background
** Changed in: ubuntu-ux Assignee: Paty Davila (dizzypaty) = Rae Shambrook (raecontreras) -- 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/1238174 Title: [Notifications] notifications / snap decisions over indicators blend into background Status in Ubuntu UX bugs: Triaged Status in unity8 package in Ubuntu: Incomplete Bug description: When a notification or a snap decision is displayed over indicators, it looks really bad, both having the same background. -- New design for notification solve this problem: https://docs.google.com/a/canonical.com/document/d /1ehZGFePGmy8pnyAGsgWYDeBgr45Cc8jE2mTb2Qz- oeM/edit#heading=h.l9277ssjb99w To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1238174/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1367623] Re: [Notifications] Titles should wrap in the notification menu/indicator
** Changed in: ubuntu-ux Assignee: Paty Davila (dizzypaty) = Grazina (boroskograzina) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings-components in Ubuntu. https://bugs.launchpad.net/bugs/1367623 Title: [Notifications] Titles should wrap in the notification menu/indicator Status in Ubuntu UX bugs: Triaged Status in ubuntu-settings-components package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Invalid Bug description: Using rtm 26 on krillin, system updates are listed in the notification (indicator-message) menu, in french they show as Il existe une image d... hh:mm - day Appuyez pour ouvrir le gestionnaire de mise à jour du système There are a few issues there: - the first line/title is ellipsize but it has to, there is enough blank space on the right to add at least another 6 letters - the title doesn't have enough content to understand what the item is about Ideally that label would wrap so no content is lost, but it should at least use the space To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1367623/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1423340] Re: [notifications] can we make the volume notification bubble less intrusive
** Changed in: ubuntu-ux Assignee: Paty Davila (dizzypaty) = Grazina (boroskograzina) -- 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/1423340 Title: [notifications] can we make the volume notification bubble less intrusive Status in Ubuntu UX bugs: Triaged Status in unity8 package in Ubuntu: Opinion Bug description: See this thread https://lists.launchpad.net/ubuntu-phone/msg11237.html has some valid points To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1423340/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1109327] Update Released
The verification of the Stable Release Update for eglibc has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to eglibc in Ubuntu. https://bugs.launchpad.net/bugs/1109327 Title: who command gets who: memory exhausted for certain inputs Status in The GNU C Library: Fix Released Status in eglibc package in Ubuntu: Fix Released Status in eglibc source package in Lucid: Won't Fix Status in eglibc source package in Precise: Fix Released Status in eglibc source package in Quantal: Won't Fix Status in eglibc package in Debian: Fix Released Bug description: SRU Justification: [Impact] * When using who, certain characters can cause issues with eglibc's vfprintf causing memory issues and who to print 'memory exhausted'. [Test Case] * Download wtmp.clean. * locale-gen en_US.UTF-8 # if necessary * LANG=en_US.UTF-8 who wtmp.clean * If you see 'who: memory exhausted' the test failed. [Regression Potential] * This patch reverts a change that fixes the issue in BZ #6530. * The patch also adds a test case to check for handling of incomplete multi-byte characters. * upstream patch URL: http://sourceware.org/git/?p=glibc.git;a=commit;h=715a900c9085907fa749589bf738b192b1a2bda5 -- * Description: When running who with the attached file we get an error of who: memory exhausted. $ who wtmp.clean This works fine in newer versions of eglibc. I was able to determine that coreutils was not the problem by using the precise version of coreutils with the raring eglibc version. In that case the problem went away. In addition I've compiled the precise version for raring, and the problem is not present. * Versions affected: This affects current Lucid, Oneiric, Precise and Quantal eglibc versions. 2.11.1-0ubuntu7.12 2.13-20ubuntu5.3 2.15-0ubuntu10.4 2.15-0ubuntu20.1 But does not affect Raring eglibc ( 2.17-0ubuntu1 ) To manage notifications about this bug go to: https://bugs.launchpad.net/glibc/+bug/1109327/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1109327] Re: who command gets who: memory exhausted for certain inputs
This bug was fixed in the package eglibc - 2.15-0ubuntu10.12 --- eglibc (2.15-0ubuntu10.12) precise; urgency=medium * cvs-vfprintf-multibyte.diff: Fix memory exhausted bug in who, by no longer parsing %s format arguments as multibyte strings (LP: #1109327) * cvs-__SSE_MATH__-feraiseexcept.diff: Check for __SSE_MATH__ in x86_64 feraiseexcept to fix backported -m32 builds of GCC 4.8 (LP: #1165387) * cvs-canonical-name.diff: Don't incorrectly do a PTR lookup when asked to do a canonical lookup for a host using AI_CANONNAME (LP: #1057526) * cvs-atomic-fastbins.diff: Fix race in free() of fastbin (LP: #1020210) -- Adam Conrad adcon...@ubuntu.com Wed, 25 Mar 2015 13:28:41 -0600 ** Changed in: eglibc (Ubuntu Precise) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to eglibc in Ubuntu. https://bugs.launchpad.net/bugs/1109327 Title: who command gets who: memory exhausted for certain inputs Status in The GNU C Library: Fix Released Status in eglibc package in Ubuntu: Fix Released Status in eglibc source package in Lucid: Won't Fix Status in eglibc source package in Precise: Fix Released Status in eglibc source package in Quantal: Won't Fix Status in eglibc package in Debian: Fix Released Bug description: SRU Justification: [Impact] * When using who, certain characters can cause issues with eglibc's vfprintf causing memory issues and who to print 'memory exhausted'. [Test Case] * Download wtmp.clean. * locale-gen en_US.UTF-8 # if necessary * LANG=en_US.UTF-8 who wtmp.clean * If you see 'who: memory exhausted' the test failed. [Regression Potential] * This patch reverts a change that fixes the issue in BZ #6530. * The patch also adds a test case to check for handling of incomplete multi-byte characters. * upstream patch URL: http://sourceware.org/git/?p=glibc.git;a=commit;h=715a900c9085907fa749589bf738b192b1a2bda5 -- * Description: When running who with the attached file we get an error of who: memory exhausted. $ who wtmp.clean This works fine in newer versions of eglibc. I was able to determine that coreutils was not the problem by using the precise version of coreutils with the raring eglibc version. In that case the problem went away. In addition I've compiled the precise version for raring, and the problem is not present. * Versions affected: This affects current Lucid, Oneiric, Precise and Quantal eglibc versions. 2.11.1-0ubuntu7.12 2.13-20ubuntu5.3 2.15-0ubuntu10.4 2.15-0ubuntu20.1 But does not affect Raring eglibc ( 2.17-0ubuntu1 ) To manage notifications about this bug go to: https://bugs.launchpad.net/glibc/+bug/1109327/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1020210] Re: Race condition using ATOMIC_FASTBINS in _int_free causes crash or heap corruption
This bug was fixed in the package eglibc - 2.15-0ubuntu10.12 --- eglibc (2.15-0ubuntu10.12) precise; urgency=medium * cvs-vfprintf-multibyte.diff: Fix memory exhausted bug in who, by no longer parsing %s format arguments as multibyte strings (LP: #1109327) * cvs-__SSE_MATH__-feraiseexcept.diff: Check for __SSE_MATH__ in x86_64 feraiseexcept to fix backported -m32 builds of GCC 4.8 (LP: #1165387) * cvs-canonical-name.diff: Don't incorrectly do a PTR lookup when asked to do a canonical lookup for a host using AI_CANONNAME (LP: #1057526) * cvs-atomic-fastbins.diff: Fix race in free() of fastbin (LP: #1020210) -- Adam Conrad adcon...@ubuntu.com Wed, 25 Mar 2015 13:28:41 -0600 ** Changed in: eglibc (Ubuntu Precise) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to eglibc in Ubuntu. https://bugs.launchpad.net/bugs/1020210 Title: Race condition using ATOMIC_FASTBINS in _int_free causes crash or heap corruption Status in Embedded GLIBC: Fix Released Status in eglibc package in Ubuntu: Fix Released Status in eglibc source package in Precise: Fix Released Bug description: [Impact] * This bug is likely to cause a crash with a SEGV in multithreading applications doing many memory deallocations with ATOMIC_FASTBINS feature enabled. [Test Case] * Since this is a race condition issue there is no simple path of reproducing it, however one could try to follow the instructions in the upstream bug (https://www.sourceware.org/bugzilla/show_bug.cgi?id=15073): https://www.sourceware.org/bugzilla/attachment.cgi?id=7331 [Regression Potential] * This issue has been merged upstream with no further issues reported. [Other Info] * Original bug description: We have an application which makes heavy allocation and de-allocation demands from multiple threads. We run this application continuously on many servers, and once every several CPU months or years, we were getting a crash in _int_free that did not look like vanilla heap corruption. I believe I have narrowed it down to a race condition in _int_free due to the ATOMIC_FASTBINS feature. Basically, in the lockless FASTBIN _int_free path, a chunk is pulled into a local variable with the intent to add it to the fastbins list. However, the heap consolidation/trim code can race with this, and can coalesce the entire block and/or give it back to the OS before _int_free has a chance to try and store it into the fastbins list. The problem is very challenging to reproduce in situ, but using gdb I have a recipe which demonstrates the crash 100% of the time on my 12.04 x64 system running eglibc 2.15. It relies on malloc_trim, although in our in situ data, the consolidation is triggered as a result of a normal free. malloc_trim is just easier to control. While I am not a glibc developer, I could not see any easy ways to fix the situation shy of disabling ATOMIC_FASTBINS. I am attaching the reproduction source. Other pertinent information follows: jpieper@calculon:~/downloads$ lsb_release -rd Description:Ubuntu 12.04 LTS Release:12.04 jpieper@calculon:~/downloads$ apt-cache policy libc6 libc6: Installed: 2.15-0ubuntu10 Candidate: 2.15-0ubuntu10 Version table: *** 2.15-0ubuntu10 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages 100 /var/lib/dpkg/status What I expect: I expect the attached application, when run using the gdb script in the comments, to complete with no failures. What happened: A SIGSEGV after the final continue. To manage notifications about this bug go to: https://bugs.launchpad.net/eglibc/+bug/1020210/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1020210] Re: Race condition using ATOMIC_FASTBINS in _int_free causes crash or heap corruption
A Canonical customer has been running this exact patch (character- identical) in production for a good while, and reports no regressions, and that it solved their problem. ** 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 eglibc in Ubuntu. https://bugs.launchpad.net/bugs/1020210 Title: Race condition using ATOMIC_FASTBINS in _int_free causes crash or heap corruption Status in Embedded GLIBC: Fix Released Status in eglibc package in Ubuntu: Fix Released Status in eglibc source package in Precise: Fix Released Bug description: [Impact] * This bug is likely to cause a crash with a SEGV in multithreading applications doing many memory deallocations with ATOMIC_FASTBINS feature enabled. [Test Case] * Since this is a race condition issue there is no simple path of reproducing it, however one could try to follow the instructions in the upstream bug (https://www.sourceware.org/bugzilla/show_bug.cgi?id=15073): https://www.sourceware.org/bugzilla/attachment.cgi?id=7331 [Regression Potential] * This issue has been merged upstream with no further issues reported. [Other Info] * Original bug description: We have an application which makes heavy allocation and de-allocation demands from multiple threads. We run this application continuously on many servers, and once every several CPU months or years, we were getting a crash in _int_free that did not look like vanilla heap corruption. I believe I have narrowed it down to a race condition in _int_free due to the ATOMIC_FASTBINS feature. Basically, in the lockless FASTBIN _int_free path, a chunk is pulled into a local variable with the intent to add it to the fastbins list. However, the heap consolidation/trim code can race with this, and can coalesce the entire block and/or give it back to the OS before _int_free has a chance to try and store it into the fastbins list. The problem is very challenging to reproduce in situ, but using gdb I have a recipe which demonstrates the crash 100% of the time on my 12.04 x64 system running eglibc 2.15. It relies on malloc_trim, although in our in situ data, the consolidation is triggered as a result of a normal free. malloc_trim is just easier to control. While I am not a glibc developer, I could not see any easy ways to fix the situation shy of disabling ATOMIC_FASTBINS. I am attaching the reproduction source. Other pertinent information follows: jpieper@calculon:~/downloads$ lsb_release -rd Description:Ubuntu 12.04 LTS Release:12.04 jpieper@calculon:~/downloads$ apt-cache policy libc6 libc6: Installed: 2.15-0ubuntu10 Candidate: 2.15-0ubuntu10 Version table: *** 2.15-0ubuntu10 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages 100 /var/lib/dpkg/status What I expect: I expect the attached application, when run using the gdb script in the comments, to complete with no failures. What happened: A SIGSEGV after the final continue. To manage notifications about this bug go to: https://bugs.launchpad.net/eglibc/+bug/1020210/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1057526] Re: getaddrinfo returns PTR name in ai_canonname when using DNS
This bug was fixed in the package eglibc - 2.15-0ubuntu10.12 --- eglibc (2.15-0ubuntu10.12) precise; urgency=medium * cvs-vfprintf-multibyte.diff: Fix memory exhausted bug in who, by no longer parsing %s format arguments as multibyte strings (LP: #1109327) * cvs-__SSE_MATH__-feraiseexcept.diff: Check for __SSE_MATH__ in x86_64 feraiseexcept to fix backported -m32 builds of GCC 4.8 (LP: #1165387) * cvs-canonical-name.diff: Don't incorrectly do a PTR lookup when asked to do a canonical lookup for a host using AI_CANONNAME (LP: #1057526) * cvs-atomic-fastbins.diff: Fix race in free() of fastbin (LP: #1020210) -- Adam Conrad adcon...@ubuntu.com Wed, 25 Mar 2015 13:28:41 -0600 ** Changed in: eglibc (Ubuntu Precise) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to eglibc in Ubuntu. https://bugs.launchpad.net/bugs/1057526 Title: getaddrinfo returns PTR name in ai_canonname when using DNS Status in Embedded GLIBC: Fix Released Status in eglibc package in Ubuntu: Fix Released Status in eglibc source package in Precise: Fix Released Status in eglibc package in Debian: Fix Released Status in eglibc package in Fedora: Unknown Bug description: Got pinged about this, not fixed in 12.04 yet. From the Redhat bug: We have verified that getaddrinfo() does reverse address calls to DNS when AI_CANONNAME is passed in hints.ai_flags and returns the PTR name of the forward resolved ip address as Canonical name. The canonical name is arguably not what is returned by the PTR record for various reasons. Aside the fact that PTR record are often not under control of the the same people that control the A name, A names can also be roundrobin names and return multiple addresses. Picking one and returnings its PTR as canonical name seem highly questionable. A CNAME - A name resolution is welcome as the A name is arguably the Canonical name of a CNAME. But getaddrinfo shouldn't do PTR requests to the DNS. We found this when testing ssh+GSSAPI auth on laptops that can properly set the A record for their name usin dynamic DNS updates but cannot change the PTR record of whatever network they are currently travelling in. This breaks kerberos which needs the canonical (A record) name to construct the principal name used to request a ticket when rdns = false is set in krb5.conf and GSSAPITrustDNS is set to no in ssh (the default). To manage notifications about this bug go to: https://bugs.launchpad.net/eglibc/+bug/1057526/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1057526] Update Released
The verification of the Stable Release Update for eglibc has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to eglibc in Ubuntu. https://bugs.launchpad.net/bugs/1057526 Title: getaddrinfo returns PTR name in ai_canonname when using DNS Status in Embedded GLIBC: Fix Released Status in eglibc package in Ubuntu: Fix Released Status in eglibc source package in Precise: Fix Released Status in eglibc package in Debian: Fix Released Status in eglibc package in Fedora: Unknown Bug description: Got pinged about this, not fixed in 12.04 yet. From the Redhat bug: We have verified that getaddrinfo() does reverse address calls to DNS when AI_CANONNAME is passed in hints.ai_flags and returns the PTR name of the forward resolved ip address as Canonical name. The canonical name is arguably not what is returned by the PTR record for various reasons. Aside the fact that PTR record are often not under control of the the same people that control the A name, A names can also be roundrobin names and return multiple addresses. Picking one and returnings its PTR as canonical name seem highly questionable. A CNAME - A name resolution is welcome as the A name is arguably the Canonical name of a CNAME. But getaddrinfo shouldn't do PTR requests to the DNS. We found this when testing ssh+GSSAPI auth on laptops that can properly set the A record for their name usin dynamic DNS updates but cannot change the PTR record of whatever network they are currently travelling in. This breaks kerberos which needs the canonical (A record) name to construct the principal name used to request a ticket when rdns = false is set in krb5.conf and GSSAPITrustDNS is set to no in ssh (the default). To manage notifications about this bug go to: https://bugs.launchpad.net/eglibc/+bug/1057526/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1020210] Update Released
The verification of the Stable Release Update for eglibc has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to eglibc in Ubuntu. https://bugs.launchpad.net/bugs/1020210 Title: Race condition using ATOMIC_FASTBINS in _int_free causes crash or heap corruption Status in Embedded GLIBC: Fix Released Status in eglibc package in Ubuntu: Fix Released Status in eglibc source package in Precise: Fix Released Bug description: [Impact] * This bug is likely to cause a crash with a SEGV in multithreading applications doing many memory deallocations with ATOMIC_FASTBINS feature enabled. [Test Case] * Since this is a race condition issue there is no simple path of reproducing it, however one could try to follow the instructions in the upstream bug (https://www.sourceware.org/bugzilla/show_bug.cgi?id=15073): https://www.sourceware.org/bugzilla/attachment.cgi?id=7331 [Regression Potential] * This issue has been merged upstream with no further issues reported. [Other Info] * Original bug description: We have an application which makes heavy allocation and de-allocation demands from multiple threads. We run this application continuously on many servers, and once every several CPU months or years, we were getting a crash in _int_free that did not look like vanilla heap corruption. I believe I have narrowed it down to a race condition in _int_free due to the ATOMIC_FASTBINS feature. Basically, in the lockless FASTBIN _int_free path, a chunk is pulled into a local variable with the intent to add it to the fastbins list. However, the heap consolidation/trim code can race with this, and can coalesce the entire block and/or give it back to the OS before _int_free has a chance to try and store it into the fastbins list. The problem is very challenging to reproduce in situ, but using gdb I have a recipe which demonstrates the crash 100% of the time on my 12.04 x64 system running eglibc 2.15. It relies on malloc_trim, although in our in situ data, the consolidation is triggered as a result of a normal free. malloc_trim is just easier to control. While I am not a glibc developer, I could not see any easy ways to fix the situation shy of disabling ATOMIC_FASTBINS. I am attaching the reproduction source. Other pertinent information follows: jpieper@calculon:~/downloads$ lsb_release -rd Description:Ubuntu 12.04 LTS Release:12.04 jpieper@calculon:~/downloads$ apt-cache policy libc6 libc6: Installed: 2.15-0ubuntu10 Candidate: 2.15-0ubuntu10 Version table: *** 2.15-0ubuntu10 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages 100 /var/lib/dpkg/status What I expect: I expect the attached application, when run using the gdb script in the comments, to complete with no failures. What happened: A SIGSEGV after the final continue. To manage notifications about this bug go to: https://bugs.launchpad.net/eglibc/+bug/1020210/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 116453] Re: evince can not find ü in attached PDF
the fix has been commited upstream, we should get it in next cycle ** Changed in: poppler (Ubuntu) Status: Triaged = Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/116453 Title: evince can not find ü in attached PDF Status in Poppler: Fix Released Status in poppler package in Ubuntu: Fix Committed Bug description: Binary package hint: evince 1) lsb_release -rd Description: Ubuntu Vivid Vervet (development branch) Release: 15.04 2) apt-cache policy evince evince: Installed: 3.14.1-0ubuntu1 Candidate: 3.14.1-0ubuntu1 Version table: *** 3.14.1-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status 3) What is expected to happen with the attached document is when one searches for: über it is found: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/116453/+attachment/102979/+files/example.pdf 4) What happens instead is it does not return any matches. WORKAROUND: Use the built-in PDF viewer+search with chromium-browser or chrome (doesn't work in Firefox). apt-cache policy chromium-browser chromium-browser: Installed: 39.0.2171.65-0ubuntu0.14.04.1.1064 Candidate: 39.0.2171.65-0ubuntu0.14.04.1.1064 Version table: *** 39.0.2171.65-0ubuntu0.14.04.1.1064 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/universe amd64 Packages 500 http://security.ubuntu.com/ubuntu/ trusty-security/universe amd64 Packages 100 /var/lib/dpkg/status 34.0.1847.116-0ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages apt-cache policy google-chrome-stable:i386 google-chrome-stable:i386: Installed: 39.0.2171.95-1 Candidate: 39.0.2171.95-1 Version table: *** 39.0.2171.95-1 0 500 http://dl.google.com/linux/chrome/deb/ stable/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug Architecture: i386 Date: Wed May 23 18:22:27 2007 DistroRelease: Ubuntu 7.04 ExecutablePath: /usr/bin/evince Package: evince 0.8.1-0ubuntu1 PackageArchitecture: i386 ProcEnviron: LANGUAGE=en_US:en PATH=~/local/bin:~/local/lib:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evince Uname: Linux copper 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/116453/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1241757] Re: Unity Launcher always assumes default background is active for a couple of seconds
Hello Sadi, or anyone else affected, Accepted unity into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/unity/7.2.4+14.04.20150316-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: unity (Ubuntu Trusty) Status: In Progress = Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1241757 Title: Unity Launcher always assumes default background is active for a couple of seconds Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [IMPACT] Every time the computer boots and autologins to my desktop, I see the default background only behind the Unity Launcher for a couple of seconds, and then it is replaced with the current wallpaper. [TEST CASE] (1) Configure the desktop to use a non-default wallpaper. (2) Log in to a Unity session and observe the area behind the Launcher. [REGRESSION POTENTIAL] The solution to this problem was to eliminate the animation of the BFB icon on initial startup. Potentially this could cause the animation to not run at other times, although even if this did occur, it is unlikely to be noticed. [OTHER INFO] The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu Vivid Vervet dev release where it has been in production use for some time without apparent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1241757/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1404486] Re: Session dialog does not show up over fullscreen windows.
Hello Andrea, or anyone else affected, Accepted unity into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/unity/7.2.4+14.04.20150316-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: unity (Ubuntu Trusty) Status: In Progress = Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1404486 Title: Session dialog does not show up over fullscreen windows. Status in Unity: Triaged Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [IMPACT] Unity session dialog does not show up over a fullscreen window if you press the hardware button. [TEST CASE] (1) open an application (eg. Firefix) and make it fullscreen (F11) (2) press the power button or choose Shut Down... from the Session indicator menu. (3) The Session (shutdown/restart) dialog should appear and be interactive. [REGRESSION POTENTIAL] No known regression potential. [OTHER INFO] The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu Vivid Vervet dev release where it has been in production use for some time without apparent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1404486/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1374942] Re: compiz crashed with signal 5 in _XReply() from unity::decoration::ForceQuitDialog::ForceQuitDialog
Hello Michael, or anyone else affected, Accepted unity into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/unity/7.2.4+14.04.20150316-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: unity (Ubuntu Trusty) Status: In Progress = Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1374942 Title: compiz crashed with signal 5 in _XReply() from unity::decoration::ForceQuitDialog::ForceQuitDialog Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [Impact] An invalid line of code would occasionally cause Unity to crash. [Test Case] (1) Download and run the attached Python script test-1374942 to create a candidate application. (2) Press the close button and wait for the Force Quit dialog to come up. (3) Choose the Force Quit button. The desktop shell should not crash. [Regression Potential] The fix for this bug involves converting an integer into a string and appending it to an error message instead of adding the integer value to the address of the error message. There is unlikely to be a regression from this. [Other Info] The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu Vivid Vervet dev release where it has been under daily use for some time without apparent regressioon. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1374942/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1401911] Re: When the screen is locked edge barriers should be deactivated.
Hello Andrea, or anyone else affected, Accepted unity into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/unity/7.2.4+14.04.20150316-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: unity (Ubuntu Trusty) Status: In Progress = Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1401911 Title: When the screen is locked edge barriers should be deactivated. Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [Impact] If the screen is locked, launcher/panel edge barriers at the moment are active. [Test Case] In a multi-monitor environment, lock the screen and move the mouse between monitors. There should be no sticky edge between the monitors. [Regression Potential] Code in the paths that handle the edge barriers was changed. Potentially this could impact the reveal of a hidden Launcher if there were errors introduced in these code paths. [Other Info] The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu Vivid Vervet dev release where it has been in production use for some time. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1401911/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 955193] Re: Menu bar - add option for the global menu to make it always visible
Hello John, or anyone else affected, Accepted unity into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/unity/7.2.4+14.04.20150316-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: unity (Ubuntu Trusty) Status: New = Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/955193 Title: Menu bar - add option for the global menu to make it always visible Status in Ayatana Design: Triaged Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [ Impact ] [Test Case] (1) enable menus in the window title bar System Settings Appearance Behavior Show the menus for a window In the menu bar (2) run gsettings set com.canonical.Unity always-show-menus true in a terminal (3) move the mouse around between windows The menus should remain displayed [Regression Potential] Any change to the menu functionality has the potential to cause volunteer functionality in menu behaviour. [Other Info] The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu Vivid Vervet dev release where it has been in production use for some time with no apparent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/955193/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1398287] Re: Unity 14.04 Lock button sometimes takes 30~60s to enter lock screen
Hello Franz, or anyone else affected, Accepted unity into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/unity/7.2.4+14.04.20150316-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: unity (Ubuntu Trusty) Status: In Progress = Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1398287 Title: Unity 14.04 Lock button sometimes takes 30~60s to enter lock screen Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [Impact] When the power button is pressed, the shutdown dialog will be displayed. Then clicks the 'Lock' button in the shutdown dialog and it sometimes takes about 30~60s to lock screen. This happens on many Intel-only platforms. PS: If user moves the cursor out of the dialog window after clicking the 'Lock' button, it will switch to lock screen immediately. [Test Case] See description under Impact' above. [Regression Potential] The fix for this problem involves releasing the grab on the input devices earlier in the sequence, allowing the animation sequence to begin immediately without a grab-release timeout. It is unlikely that this could introduce any regressions. [Other Info] This fix was cherry picked for Ubuntu 14.04 LTS from the Ubuntu Vivid Vervet dev release where it has been in test for some time without incident. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1398287/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 860970] Re: Dash called with super key above fullscreen app is not interactive or does not show up at all.
Hello Aurélien, or anyone else affected, Accepted unity into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/unity/7.2.4+14.04.20150316-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: unity (Ubuntu Trusty) Status: In Progress = Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/860970 Title: Dash called with super key above fullscreen app is not interactive or does not show up at all. Status in Ayatana Design: Fix Committed Status in Unity: Fix Released Status in Unity 5.0 series: Triaged Status in Unity 6.0 series: Won't Fix Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Precise: Triaged Status in unity source package in Trusty: Fix Committed Bug description: [IMPACT] The Dash was rendered underneath fullscreen windows so it was invisible, although it grabs keyboard input. [TEST CASE] - Launch an application in fullscreen (Firefox, Totem). - Hit the Super key to call the dash. - The Dash should appear. - Keyboard input should be directed to the Dash. - Clicking anywhere on the full screen application should close the Dash. [REGRESSION POTENTIAL] No known regression potential. [OTHER INFO] The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu Vivid Vervet dev release where it has been in production use for some time without apparent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/860970/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1312137] Re: Local menus broken for Qt apps after opening dialog
Hello CraigD, or anyone else affected, Accepted unity into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/unity/7.2.4+14.04.20150316-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: unity (Ubuntu Trusty) Status: In Progress = Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1312137 Title: Local menus broken for Qt apps after opening dialog Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [Impact] I have selected to have window menus in the window's title bar. This works great, except for Qt apps. After selecting a menu item in a Qt app that produces a dialog, the menu is no longer accessible. The only way to get the menu back, is to switch to another window, and then back to the affected app. [Test Case] 1. Start qtcreator 2. Resize window so that it is not maximised 3. Select 'Help' - 'About Qt Creator' 4. Dismiss 'About Qt Creator' dialog 5. Move mouse over window titlebar. [Regression Potential] It's possible other menu interaction bugs may have been introduced. [Other Info] The fix for Ubuntu 14.04 LTS was cherry-picked from the Ubuntu Vivid Vervet dev release where it has been in production use for some time without apparent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1312137/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1390562] Re: Moving the mouse out from the decoration hides the LIMs when Alt is pressed
Hello Marco, or anyone else affected, Accepted unity into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/unity/7.2.4+14.04.20150316-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: unity (Ubuntu Trusty) Status: In Progress = Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1390562 Title: Moving the mouse out from the decoration hides the LIMs when Alt is pressed Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [Impact] Pressing the Alt key while a locally integrated menu is open causes the menu to hide. [Test Case] Prerequisite: from Appearance - Behavior - Set menu visible in window titlebar 1. Open a window with menus 2. Press and keep pressed the Alt key 3. Menus will show 4. Move the mouse over the window decoration 5. Move the mouse out from the window decoration Incorrect behavior: 6. Menus hides, also if the Alt key is pressed. Expected: 6. Menus should stay visible until the Alt key is released. [Regression Potential] Additional incorrect menu behaviour may be introduced. [Other Info] The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu Vivid Vervet dev release where it has been in use for some time without apparent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1390562/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1363534] Re: Wrong keyboard shortcuts for Workspaces in Dash overlay
Hello Mario, or anyone else affected, Accepted unity into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/unity/7.2.4+14.04.20150316-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: unity (Ubuntu Trusty) Status: In Progress = Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1363534 Title: Wrong keyboard shortcuts for Workspaces in Dash overlay Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [Impact] The Shortcuts displays the wrong key sequence for switching workspaces. [Test Case] (1) Enable workspaces (System Settings Appearance Behavior Enable Workspaces). (2) Hold down the Super key until the Shortcuts window appears. (3) Under Workspaces it should display Shift + Ctrl + Alt + Arrow Keys and not Shift + Ctrl + Alt + Left + Arrow Keys. [Regression Potential] Unlikely. [Other Info] This fix was cherry picked for Ubuntu 14.04 LTS from the Ubuntu Vivi Vervet dev release where it has been in production use for some time without regression. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1363534/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1441508] [NEW] Brightness control broke
Public bug reported: Hi! I have a Ubuntu Aquaris E4.5. To listen to Cutespotify I run the commands: sudo service powered start/ stop To reduce brightness I changed brightness control to manual (the slide was all the way down), since then, my screen is black and i see nothing, but it response normally. Unfortunatly I can't navigate to the brightness control. You know a workaround? Thank you Aquaris Ubuntu armf 14.10 r20 ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1441508 Title: Brightness control broke Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: Hi! I have a Ubuntu Aquaris E4.5. To listen to Cutespotify I run the commands: sudo service powered start/ stop To reduce brightness I changed brightness control to manual (the slide was all the way down), since then, my screen is black and i see nothing, but it response normally. Unfortunatly I can't navigate to the brightness control. You know a workaround? Thank you Aquaris Ubuntu armf 14.10 r20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1441508/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1438244] Re: let gold ignore the -fuse-ld option passed by newer GCC versions
This bug was fixed in the package binutils - 2.20.1-3ubuntu7.3 --- binutils (2.20.1-3ubuntu7.3) lucid-proposed; urgency=medium * gold: Add -fuse-ld= for GCC linker option compatibility. LP: #1438244. -- Matthias Klose d...@ubuntu.com Mon, 30 Mar 2015 17:08:48 +0200 ** Changed in: binutils (Ubuntu Lucid) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1438244 Title: let gold ignore the -fuse-ld option passed by newer GCC versions Status in binutils package in Ubuntu: Fix Released Status in binutils source package in Lucid: Fix Released Status in binutils source package in Precise: Fix Released Bug description: GCC 4.9 and newer versinos (and 4.8 patched for Ubuntu) pass the -fuse-ld option to the linker. gold in precise errors out with /usr/bin/ld.gold: fatal error: -f/--auxiliary may not be used without -shared collect2: error: ld returned 1 exit status Let gold understand (and ignore) this option. Test: ld.gold accepts this option. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1438244/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1438244] Update Released
The verification of the Stable Release Update for binutils has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1438244 Title: let gold ignore the -fuse-ld option passed by newer GCC versions Status in binutils package in Ubuntu: Fix Released Status in binutils source package in Lucid: Fix Released Status in binutils source package in Precise: Fix Released Bug description: GCC 4.9 and newer versinos (and 4.8 patched for Ubuntu) pass the -fuse-ld option to the linker. gold in precise errors out with /usr/bin/ld.gold: fatal error: -f/--auxiliary may not be used without -shared collect2: error: ld returned 1 exit status Let gold understand (and ignore) this option. Test: ld.gold accepts this option. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1438244/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1439109] Re: Network interface not coming up due to missing /etc/rcS.d/*networking
I don't have a dpkg-old there, looking at dpkg.log* doesn't show any failed configures. Indeed I already did restore it using this trick. Isn't insserv responsible for creating the symlinks? Although maybe it considers the removed symlink to be a preservable change too. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1439109 Title: Network interface not coming up due to missing /etc/rcS.d/*networking Status in ifupdown package in Ubuntu: Confirmed Bug description: This used to work fine; now when I start my container there's no network inside. Manually bringing the interface up (ifup eth0 or systemctl start ifup@eth0) works. What information would be useful for you? ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-5ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 ApportVersion: 2.17-0ubuntu1 Architecture: amd64 Date: Wed Apr 1 11:35:28 2015 Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: System manufacturer System Product Name ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-10-generic root=UUID=980689ca-e7d9-4a99-8230-33b8b6e917cd ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw systemd.debug-shell nomdmonddf nomdmonisw nomdmonddf nomdmonisw SourcePackage: systemd UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1201 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V LX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1201:bd08/17/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1439109/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1441508] Re: Brightness control broke
I could establish a ssh connection, but i don' know the command to adjust brightness. Can't find it under /sys/class/backlight/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1441508 Title: Brightness control broke Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: Hi! I have a Ubuntu Aquaris E4.5. To listen to Cutespotify I run the commands: sudo service powered start/ stop To reduce brightness I changed brightness control to manual (the slide was all the way down), since then, my screen is black and i see nothing, but it response normally. Unfortunatly I can't navigate to the brightness control. You know a workaround? Thank you Aquaris Ubuntu armf 14.10 r20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1441508/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1057526] Re: getaddrinfo returns PTR name in ai_canonname when using DNS
** Branch linked: lp:ubuntu/precise-updates/eglibc -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to eglibc in Ubuntu. https://bugs.launchpad.net/bugs/1057526 Title: getaddrinfo returns PTR name in ai_canonname when using DNS Status in Embedded GLIBC: Fix Released Status in eglibc package in Ubuntu: Fix Released Status in eglibc source package in Precise: Fix Released Status in eglibc package in Debian: Fix Released Status in eglibc package in Fedora: Unknown Bug description: Got pinged about this, not fixed in 12.04 yet. From the Redhat bug: We have verified that getaddrinfo() does reverse address calls to DNS when AI_CANONNAME is passed in hints.ai_flags and returns the PTR name of the forward resolved ip address as Canonical name. The canonical name is arguably not what is returned by the PTR record for various reasons. Aside the fact that PTR record are often not under control of the the same people that control the A name, A names can also be roundrobin names and return multiple addresses. Picking one and returnings its PTR as canonical name seem highly questionable. A CNAME - A name resolution is welcome as the A name is arguably the Canonical name of a CNAME. But getaddrinfo shouldn't do PTR requests to the DNS. We found this when testing ssh+GSSAPI auth on laptops that can properly set the A record for their name usin dynamic DNS updates but cannot change the PTR record of whatever network they are currently travelling in. This breaks kerberos which needs the canonical (A record) name to construct the principal name used to request a ticket when rdns = false is set in krb5.conf and GSSAPITrustDNS is set to no in ssh (the default). To manage notifications about this bug go to: https://bugs.launchpad.net/eglibc/+bug/1057526/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1439109] Re: Network interface not coming up due to missing /etc/rcS.d/*networking
For the record, this is how to clean up: sudo update-r.cd networking remove sudo update-r.cd networking defaults Vincent has the same problem, and he mentioned that he has an /etc/init.d/networking.dpkg-old; that sounds like ifupdown once failed to upgrade/configure? ** Summary changed: - Network interface not coming up automatically inside lxc container + Network interface not coming up due to missing /etc/rcS.d/*networking ** Package changed: insserv (Ubuntu) = ifupdown (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to insserv in Ubuntu. https://bugs.launchpad.net/bugs/1439109 Title: Network interface not coming up due to missing /etc/rcS.d/*networking Status in ifupdown package in Ubuntu: New Bug description: This used to work fine; now when I start my container there's no network inside. Manually bringing the interface up (ifup eth0 or systemctl start ifup@eth0) works. What information would be useful for you? ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-5ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 ApportVersion: 2.17-0ubuntu1 Architecture: amd64 Date: Wed Apr 1 11:35:28 2015 Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: System manufacturer System Product Name ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-10-generic root=UUID=980689ca-e7d9-4a99-8230-33b8b6e917cd ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw systemd.debug-shell nomdmonddf nomdmonisw nomdmonddf nomdmonisw SourcePackage: systemd UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1201 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V LX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1201:bd08/17/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1439109/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1441499] [NEW] Unneeded build dependencies in UITK
Public bug reported: There are some unneeded build dependencies in UI Toolkit: qt5-default: not recommened to be used anymore, can be replaced with a debian/rules change qtbase5-dev-tools: already depended from qtbase5-dev libqt5organizer5: already depended from qtpim5-dev ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Assignee: Timo Jyrinki (timo-jyrinki) Status: New ** Branch linked: lp:~timo-jyrinki/ubuntu-ui- toolkit/clean_up_build_dependencies_cruft -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1441499 Title: Unneeded build dependencies in UITK Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: There are some unneeded build dependencies in UI Toolkit: qt5-default: not recommened to be used anymore, can be replaced with a debian/rules change qtbase5-dev-tools: already depended from qtbase5-dev libqt5organizer5: already depended from qtpim5-dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1441499/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1365179] Re: [Browser] Top bar should overlay the page, not anchoring on top of it
So much better on vivid! Thanks! -- 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/1365179 Title: [Browser] Top bar should overlay the page, not anchoring on top of it Status in Ubuntu UX bugs: Fix Committed Status in Web Browser App: Fix Released Status in webbrowser-app package in Ubuntu: Fix Released Status in webbrowser-app package in Ubuntu RTM: Confirmed Bug description: As in the subject, the top bar, address bar, should overlay the current web view, and hide/appear on top. In the current solution, you see the webpage scrolling slowly up and down when the top bar shows or hides. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1365179/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1072206] Re: [nvidia] Window content is black or transparent
Hello ZeXx86, or anyone else affected, Accepted compiz into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/compiz/1:0.9.11.3+14.04.20150313-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: compiz (Ubuntu Trusty) Status: In Progress = Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1072206 Title: [nvidia] Window content is black or transparent Status in Compiz: Fix Committed Status in Compiz 0.9.11 series: In Progress Status in NVIDIA Drivers Ubuntu: Invalid Status in Unity: Invalid Status in compiz package in Ubuntu: Fix Released Status in unity package in Ubuntu: Invalid Status in compiz source package in Trusty: Fix Committed Bug description: [ Impact ] With nVidia hardware from time to time window content is rendered black or transparent. The problem manifests more frequently as session uptime increases. Apparently the problem was caused by textures being cached and not freed, resulting in memory exhaustion conditions. It turns out the texture caching is unnecessary anyway. [ Test Case ] Verification requires an nVidia GPU with proprietary drivers. The problem can not be reproduced at will, only after some time (depending on resident GPU memory and usage) and even then only randomly and unreliably. [ Regression Potential ] It is unlikely this change has the potential to introduce new regressions. [ Other Info ] Fix was cherry-picked from the Ubuntu Vivid Vervet dev relase where it has been in use for some weeks without problem. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1072206/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1261666] Re: [pulseaudio] module.c: Failed to load module module-echo-cancel (argument: aec_method=webrtc): initia lization failed.
Will there be an update for 14.04 as well? -- 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/1261666 Title: [pulseaudio] module.c: Failed to load module module-echo-cancel (argument: aec_method=webrtc): initia lization failed. Status in pulseaudio package in Ubuntu: Fix Released Bug description: Hello! 13.10. Trying to load module-echo-cancel with webrtc and get: [pulseaudio] module.c: Failed to load module module-echo-cancel (argument: aec_method=webrtc): initia lization failed. I guess this is wrong... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1261666/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1358197] Re: Power off dialog box no longer shows restart
As prefigured in this bug report, I have reported bug 1436458 on removing the Restart function. -- 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/1358197 Title: Power off dialog box no longer shows restart Status in Ubuntu UX bugs: Fix Released Status in unity8 package in Ubuntu: Fix Released Bug description: In the last promoted image, r179, the power off dialog displays three options: * Power off * Restart * Cancel In r197, the power off dialog no longer allows the user to restart the phone. Restart should be added back to the power off dialog box. Note: Not sure why this change was made, it was not a design request --- Desired resolution: - revert this change to add the restart option back to the power off dialogue - Note that when the phone is more stable we will eventually want to remove this option, however for now it should stay. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1358197/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1439109] Re: Network interface not coming up due to missing /etc/rcS.d/*networking
** Changed in: ifupdown (Ubuntu) Status: Confirmed = In Progress ** Changed in: ifupdown (Ubuntu) Assignee: (unassigned) = Martin Pitt (pitti) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1439109 Title: Network interface not coming up due to missing /etc/rcS.d/*networking Status in ifupdown package in Ubuntu: In Progress Bug description: This used to work fine; now when I start my container there's no network inside. Manually bringing the interface up (ifup eth0 or systemctl start ifup@eth0) works. What information would be useful for you? ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-5ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 ApportVersion: 2.17-0ubuntu1 Architecture: amd64 Date: Wed Apr 1 11:35:28 2015 Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: System manufacturer System Product Name ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-10-generic root=UUID=980689ca-e7d9-4a99-8230-33b8b6e917cd ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw systemd.debug-shell nomdmonddf nomdmonisw nomdmonddf nomdmonisw SourcePackage: systemd UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1201 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V LX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1201:bd08/17/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1439109/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1432173] Re: fails to bring up network bridge
*** This bug is a duplicate of bug 1439109 *** https://bugs.launchpad.net/bugs/1439109 ** This bug is no longer a duplicate of bug 1430675 fails to set up a bridged network interface ** This bug has been marked a duplicate of bug 1439109 Network interface not coming up due to missing /etc/rcS.d/*networking -- 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/1432173 Title: fails to bring up network bridge Status in systemd package in Ubuntu: Confirmed Bug description: Probably a dup of #1430675 After upgrading to vivid with systemd my network bridge isn't configured on boot: $ systemctl --all |grep ifup ● ifup-wait-all-auto.service loadedfailed failed Wait for all auto /etc/network/interfaces to be up for network-online.target ● ifup@eth0.service loadedfailed failed ifup for eth0 ifup@eth1.service loadedactive exited ifup for eth1 ifup@lxcbr0.service loadedactive exited ifup for lxcbr0 ifup@virbr0-nic.service loadedactive exited ifup for virbr0/nic ifup@virbr0.service loadedactive exited ifup for virbr0 ifup@wlan0.service loadedactive exited ifup for wlan0 system-ifup.slice loadedactive active system-ifup.slice $ journalctl -u ifup-wait-all-auto.service -- Logs begin at Sat 2015-03-14 15:17:08 CET, end at Sat 2015-03-14 15:21:30 CET. -- Mar 14 15:17:56 yofel-desktop systemd[1]: Starting Wait for all auto /etc/network/interfaces to be up for network-online.target... Mar 14 15:17:56 yofel-desktop sh[1114]: Segmentation fault Mar 14 15:19:56 yofel-desktop systemd[1]: ifup-wait-all-auto.service start operation timed out. Terminating. Mar 14 15:19:56 yofel-desktop systemd[1]: Failed to start Wait for all auto /etc/network/interfaces to be up for network-online.target. Mar 14 15:19:56 yofel-desktop systemd[1]: Unit ifup-wait-all-auto.service entered failed state. Mar 14 15:19:56 yofel-desktop systemd[1]: ifup-wait-all-auto.service failed. $ sudo ifconfig br0 up br0: ERROR while getting interface flags: No such device $ sudo ifup br0 /etc/resolvconf/update.d/libc: Warning: /etc/resolv.conf is not a symbolic link to /run/resolvconf/resolv.conf Waiting for DAD... Done resolv.conf is intentionally a regular file. But after running ifup the bridge works fine. interfaces: auto lo br0 iface lo inet loopback iface eth0 inet manual iface br0 inet static address 192.168.1.5 netmask 255.255.255.0 gateway 192.168.1.1 bridge_ports eth1 bridge_stp off bridge_maxwait 0 bridge_fd 0 iface br0 inet6 static address fec0::218:f3ff:fe2c:eb60/64 netmask 64 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-4ubuntu5 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu2 Architecture: amd64 Date: Sat Mar 14 15:29:24 2015 InstallationDate: Installed on 2011-01-03 (1530 days ago) InstallationMedia: Kubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 LANGUAGE=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic root=UUID=9c833d6f-4685-4a19-ad27-fa60a77a4054 ro SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/30/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1238 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5B-Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias:
[Touch-packages] [Bug 1430675] Re: fails to set up a bridged network interface
*** This bug is a duplicate of bug 1439109 *** https://bugs.launchpad.net/bugs/1439109 Timo confirmed as well, so confirming as a duplicate of bug 1439109. ** This bug has been marked a duplicate of bug 1439109 Network interface not coming up due to missing /etc/rcS.d/*networking -- 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/1430675 Title: fails to set up a bridged network interface Status in systemd package in Ubuntu: Incomplete Bug description: I have a simple bridge set up in /etc/network/interfaces so that the virtual machines running on that machine can use it and be on the same subnet. But with systemd it's not started on boot. The bridge is configured as follows auto br0 iface br0 inet dhcp bridge_ports eth0 bridge_stp off bridge_maxwait 5 reproduced now on a fresh vm. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1430675/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1441508] Re: Brightness control broke
Fix if ssh connection: phablet@ubuntu-phablet:/sys/class/leds/lcd-backlight$ echo 80 brightness -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1441508 Title: Brightness control broke Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: Hi! I have a Ubuntu Aquaris E4.5. To listen to Cutespotify I run the commands: sudo service powered start/ stop To reduce brightness I changed brightness control to manual (the slide was all the way down), since then, my screen is black and i see nothing, but it response normally. Unfortunatly I can't navigate to the brightness control. You know a workaround? Thank you Aquaris Ubuntu armf 14.10 r20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1441508/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1302090] Re: Dell Alienware 14, Speaker sound output is mono until a headphone jack is plugged
if headset mic is at node 0x1b similar to the model dell-headset-multi [pin] 0x1b 0x03a1113c [hint] parser_flags=4 -- 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/1302090 Title: Dell Alienware 14, Speaker sound output is mono until a headphone jack is plugged Status in alsa-driver package in Ubuntu: Confirmed Bug description: Here's the required release and package information: Description:Ubuntu Trusty Tahr (development branch) Release:14.04 Package: linux-image-extra-3.13.0-19-generic Version: 3.13.0-19.40 When playing audio through speakers on my Alienware 14 2014, the sound output is in mono until I plug a headphone in any of the two available headphone jacks (obviously, the auto-mute option must be disabled). When I do so, the sound starts to play in stereo. I would love the sound output to be stereo by default and not be forced to plug anything to achieve that. Attached is the alsa-info.sh output for my machine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1302090/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1399289] Re: Extend double-line header to ImageView and TextView
Marked as 'Fix Released' for ubuntu-docviewer-app, since the image view has been removed and the text view is already using the double-line header. ** Changed in: ubuntu-docviewer-app Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1399289 Title: Extend double-line header to ImageView and TextView Status in Document Viewer application for Ubuntu devices: Fix Released Status in Ubuntu UX bugs: Fix Committed Status in ubuntu-ui-toolkit package in Ubuntu: Triaged Bug description: In the PdfView we are using a multi-line header, that provides informations about the name of the file and the current page (as sub- text). For UX consistence, we should extend the custom header to the Image Viewer and the Text Viewer. However it's not clear which information should be provided as sub-text. See attached screenshot. UX: This is going to be available in the SDK. The Header title slot might have two lines of text To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-docviewer-app/+bug/1399289/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1441253] Re: hanging suspend job prevents shutdown
The system is a Laptop in a docking station, two external monitors, booted up with lid closed. Last time I tried (a week ago) , the system suspended, but didn't wake up properly (external monitors didn't turn on). At that time I attributed that to the btrfs lookup that has been plaguing the system lately (probably the issue discussed here: http://www.spinics.net/lists /linux-btrfs/msg42637.html) The suspend isn't running directly after a clean boot. I was able to trigger it by locking and unlocking the screen. journal shows the suspend event, but not the reason why I did some more testing: 1. booted to clean state, no jobs running - suspend from menu works, system resumes almost correctly (wired ethernet has neither IPv4 nor IPv6 address - both are normally present and working, disabled/reenable in network manager fixes that) 2. booted to clean state, no jobs running - wait for idle screen or lock the screen from menu, screen blackens, takes two to three seconds to return from black screen to login screen, afterwards suspend jobs are running, poweroff is broken, manual suspend (from menu) leaves system in semi broken state (is alive, task switcher is reacting, but screen has a grey overlay and no window reacts to input, mouse is frozen as well) -- 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/1441253 Title: hanging suspend job prevents shutdown Status in systemd package in Ubuntu: Incomplete Bug description: poweroff (systemd poweroff) and reboot no longer work running sudo sytemd poweroff generates this: Failed to start poweroff.target: Transaction is destructive. journal log also shows: Apr 07 18:30:12 alice polkitd(authority=local)[1088]: Registered Authentication Agent for unix-process:32412:2895609 (system bus name :1.194 [/usr/bin/pkttyagent --notify-fd 5 --fallback], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) Apr 07 18:30:12 alice systemd[1]: Requested transaction contradicts existing jobs: Transaction is destructive. Apr 07 18:30:12 alice polkitd(authority=local)[1088]: Unregistered Authentication Agent for unix-process:32412:2895609 (system bus name :1.194, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus) Output of systemctl list-jobs JOB UNITTYPE STATE 6009 suspend.target start waiting 6010 systemd-suspend.service start running 6014 anacron-resume.service start waiting ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-6ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3 Uname: Linux 3.19.0-12-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.17-0ubuntu1 Architecture: amd64 Date: Tue Apr 7 18:32:27 2015 MachineType: Hewlett-Packard HP EliteBook 8560w ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.19.0-12-generic root=UUID=90fa42f5-708d-4432-9241-315b9c08ba98 ro nomodeset rootflags=subvol=@ SourcePackage: systemd UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: Upgraded to vivid on 2015-03-02 (36 days ago) dmi.bios.date: 08/04/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SVD Ver. F.50 dmi.board.name: 1631 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 01.3D dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SVDVer.F.50:bd08/04/2014:svnHewlett-Packard:pnHPEliteBook8560w:pvrA0001D02:rvnHewlett-Packard:rn1631:rvrKBCVersion01.3D:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8560w dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1441253/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1430675] Re: fails to set up a bridged network interface
Vincent Ladeuil reported this on IRC as well, and for him the problem was that /etc/init.d/networking was disabled. I. e. there is no /etc/rcS.d/*networking symlink. Timo, Philip, zoolook, can you please check this? If you don't have such a symlink, please run sudo update-r.cd networking remove sudo update-r.cd networking defaults and then check if the bridge comes up alright after that? -- 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/1430675 Title: fails to set up a bridged network interface Status in systemd package in Ubuntu: Incomplete Bug description: I have a simple bridge set up in /etc/network/interfaces so that the virtual machines running on that machine can use it and be on the same subnet. But with systemd it's not started on boot. The bridge is configured as follows auto br0 iface br0 inet dhcp bridge_ports eth0 bridge_stp off bridge_maxwait 5 reproduced now on a fresh vm. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1430675/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1413411] Re: underscore in mounted drive name mishandled in menu
Hello Carl, or anyone else affected, Accepted unity into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/unity/7.2.4+14.04.20150316-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: unity (Ubuntu Trusty) Status: In Progress = Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1413411 Title: underscore in mounted drive name mishandled in menu Status in One Hundred Papercuts: In Progress Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [Impact] If you have a mounted drive with an underscore in it's name (e.g. host_S), then, when you right-click on the drive icon in the sidebar, the menu interprets the underscore as a keyboard-shortcut indicator, so shows the name as hostS (with S underlined). Hovering over the drive results in the correct host_S name; the bug is only in the right-click menu. Note that right-clicking on the Files icon will show a menu that includes the correct mounted disk names. It is only right-clicking on the drive-icons themselves that shows the incorrect name. [Test Case] (1) Create a mountable device with an underscore in its volume name (eg. host_S). (2) Right click on the icon for tha drive in the Launcher. It should display the underscore character correctly as a part of the drive name, and not as an underline. [Regression Potential] None. [Other Info] The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu Vivid Vervet dev release where it has been in production use for some time without apparent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1413411/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1072206] Re: [nvidia] Window content is black or transparent
** Branch linked: lp:ubuntu/trusty-proposed/compiz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1072206 Title: [nvidia] Window content is black or transparent Status in Compiz: Fix Committed Status in Compiz 0.9.11 series: In Progress Status in NVIDIA Drivers Ubuntu: Invalid Status in Unity: Invalid Status in compiz package in Ubuntu: Fix Released Status in unity package in Ubuntu: Invalid Status in compiz source package in Trusty: Fix Committed Bug description: [ Impact ] With nVidia hardware from time to time window content is rendered black or transparent. The problem manifests more frequently as session uptime increases. Apparently the problem was caused by textures being cached and not freed, resulting in memory exhaustion conditions. It turns out the texture caching is unnecessary anyway. [ Test Case ] Verification requires an nVidia GPU with proprietary drivers. The problem can not be reproduced at will, only after some time (depending on resident GPU memory and usage) and even then only randomly and unreliably. [ Regression Potential ] It is unlikely this change has the potential to introduce new regressions. [ Other Info ] Fix was cherry-picked from the Ubuntu Vivid Vervet dev relase where it has been in use for some weeks without problem. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1072206/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1333140] Update Released
The verification of the Stable Release Update for systemd has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1333140
Title:
Fix udev rules to consider mmc rpmb partitions
Status in systemd package in Ubuntu:
Fix Released
Status in udev package in Ubuntu:
Invalid
Status in udisks package in Ubuntu:
Triaged
Status in udev source package in Precise:
Triaged
Status in udisks source package in Precise:
Confirmed
Status in systemd source package in Trusty:
Fix Released
Status in udisks source package in Trusty:
Confirmed
Bug description:
As per JEDEC 4.5 spec for eMMC devices,
There is a new partitions as part of eMMC storage devices it self. (Further
details please refer eMMC spec)
*In Linux Kernel@ 3.10.33, mmc driver has created a new partitions
with mmcblkXrpmb if device expresses it support of RPMB.
Issues observed:
issue 1:
RPMB (Replay Protected Memory Block), A signed access to a Replay Protected
Memory Block is provided. This function provides means for the system to store
data to the specific memory area in an authenticated and replay protected
manner.
In that case, any read/write access to this partition device will report
errors.
issue 2:
The by-path, line is wrongly mapping to platform-sdhci-tegra.1 -
mmcblk2rpmb were as
it should be platform-sdhci-tegra.1 - mmcblk2
ls -l /dev/disk/by-path/
total 0
lrwxrwxrwx 1 root root 17 Jan 3 2000 platform-sdhci-tegra.1 -
../../mmcblk2rpmb
lrwxrwxrwx 1 root root 15 Jan 3 2000 platform-sdhci-tegra.1-part1 -
../../mmcblk2p1
lrwxrwxrwx 1 root root 13 Jan 3 2000 platform-sdhci-tegra.2 - ../../mmcblk1
lrwxrwxrwx 1 root root 15 Jan 3 2000 platform-sdhci-tegra.2-part1 -
../../mmcblk1p1
lrwxrwxrwx 1 root root 17 Jan 3 2000 platform-sdhci-tegra.3 -
../../mmcblk0rpmb
lrwxrwxrwx 1 root root 15 Jan 3 2000 platform-sdhci-tegra.3-part1 -
../../mmcblk0p1
lrwxrwxrwx 1 root root 15 Jan 3 2000 platform-sdhci-tegra.3-part2 -
../../mmcblk0p2
We have locally resolved in our platform in this file 60-persistent-
storage.rules
For issue 1: (with this rule)
# skip block read for partitions of type rpmb
KERNEL==mmcblk[0-9]rpmb, SUBSYSTEM==block, GOTO=persistent_storage_end
For issue 2:
ENV{DEVTYPE}==disk, ENV{ID_PATH}==?*, KERNEL==mmcblk[0-9]rpmb,
SYMLINK+=disk/by-path/$env{ID_PATH}-rpmb
ENV{DEVTYPE}==disk, ENV{ID_PATH}==?*, KERNEL!=mmcblk[0-9]rpmb,
SYMLINK+=disk/by-path/$env{ID_PATH}
Please consider this issues fix in next udev release .
SRU INFO: This is mostly an issue with running backported kernels on 12.04
and 14.04. There is no test case which would reproduce this on arbitrary
hardware, but there are several reporters which are in a position to verify a
proposed update.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1333140/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1333140] Re: Fix udev rules to consider mmc rpmb partitions
This bug was fixed in the package systemd - 204-5ubuntu20.11
---
systemd (204-5ubuntu20.11) trusty; urgency=medium
[ Ben Howard ]
* Add debian/extra/rules/62-google-cloudimg.rules: Use noop scheduler for
Google virtio drives. (LP: #1420544)
[ Martin Pitt ]
* Add upstream-ignore-mmcrpmb.patch: Fix /dev/disk/by-path/ symlink of mmc
RPMB partitions and don't blkid them to avoid kernel buffer I/O errors and
timeouts. (LP: #1333140)
-- Martin Pitt martin.p...@ubuntu.com Wed, 18 Feb 2015 12:11:49 +0100
** Changed in: systemd (Ubuntu Trusty)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1333140
Title:
Fix udev rules to consider mmc rpmb partitions
Status in systemd package in Ubuntu:
Fix Released
Status in udev package in Ubuntu:
Invalid
Status in udisks package in Ubuntu:
Triaged
Status in udev source package in Precise:
Triaged
Status in udisks source package in Precise:
Confirmed
Status in systemd source package in Trusty:
Fix Released
Status in udisks source package in Trusty:
Confirmed
Bug description:
As per JEDEC 4.5 spec for eMMC devices,
There is a new partitions as part of eMMC storage devices it self. (Further
details please refer eMMC spec)
*In Linux Kernel@ 3.10.33, mmc driver has created a new partitions
with mmcblkXrpmb if device expresses it support of RPMB.
Issues observed:
issue 1:
RPMB (Replay Protected Memory Block), A signed access to a Replay Protected
Memory Block is provided. This function provides means for the system to store
data to the specific memory area in an authenticated and replay protected
manner.
In that case, any read/write access to this partition device will report
errors.
issue 2:
The by-path, line is wrongly mapping to platform-sdhci-tegra.1 -
mmcblk2rpmb were as
it should be platform-sdhci-tegra.1 - mmcblk2
ls -l /dev/disk/by-path/
total 0
lrwxrwxrwx 1 root root 17 Jan 3 2000 platform-sdhci-tegra.1 -
../../mmcblk2rpmb
lrwxrwxrwx 1 root root 15 Jan 3 2000 platform-sdhci-tegra.1-part1 -
../../mmcblk2p1
lrwxrwxrwx 1 root root 13 Jan 3 2000 platform-sdhci-tegra.2 - ../../mmcblk1
lrwxrwxrwx 1 root root 15 Jan 3 2000 platform-sdhci-tegra.2-part1 -
../../mmcblk1p1
lrwxrwxrwx 1 root root 17 Jan 3 2000 platform-sdhci-tegra.3 -
../../mmcblk0rpmb
lrwxrwxrwx 1 root root 15 Jan 3 2000 platform-sdhci-tegra.3-part1 -
../../mmcblk0p1
lrwxrwxrwx 1 root root 15 Jan 3 2000 platform-sdhci-tegra.3-part2 -
../../mmcblk0p2
We have locally resolved in our platform in this file 60-persistent-
storage.rules
For issue 1: (with this rule)
# skip block read for partitions of type rpmb
KERNEL==mmcblk[0-9]rpmb, SUBSYSTEM==block, GOTO=persistent_storage_end
For issue 2:
ENV{DEVTYPE}==disk, ENV{ID_PATH}==?*, KERNEL==mmcblk[0-9]rpmb,
SYMLINK+=disk/by-path/$env{ID_PATH}-rpmb
ENV{DEVTYPE}==disk, ENV{ID_PATH}==?*, KERNEL!=mmcblk[0-9]rpmb,
SYMLINK+=disk/by-path/$env{ID_PATH}
Please consider this issues fix in next udev release .
SRU INFO: This is mostly an issue with running backported kernels on 12.04
and 14.04. There is no test case which would reproduce this on arbitrary
hardware, but there are several reporters which are in a position to verify a
proposed update.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1333140/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1261666] Re: [pulseaudio] module.c: Failed to load module module-echo-cancel (argument: aec_method=webrtc): initia lization failed.
Will there be an update for 14.04 as well? Probably not, sorry. -- 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/1261666 Title: [pulseaudio] module.c: Failed to load module module-echo-cancel (argument: aec_method=webrtc): initia lization failed. Status in pulseaudio package in Ubuntu: Fix Released Bug description: Hello! 13.10. Trying to load module-echo-cancel with webrtc and get: [pulseaudio] module.c: Failed to load module module-echo-cancel (argument: aec_method=webrtc): initia lization failed. I guess this is wrong... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1261666/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
