[Touch-packages] [Bug 1440803] Re: Weird horizontal lines on Unity display
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/1440803 Title: Weird horizontal lines on Unity display Status in unity package in Ubuntu: Confirmed Bug description: Weird horizontal lines appear on Unity display They corrupt the normal interface ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.4+14.04.20141217-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7 Uname: Linux 3.16.0-33-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.8 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Apr 6 10:49:01 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c2] (rev 10) (prog-if 00 [VGA controller]) Subsystem: Biostar Microtech Int'l Corp Device [1565:3103] InstallationDate: Installed on 2015-04-03 (3 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release i386 (20150218.1) MachineType: BIOSTAR Group G31-M7 TE ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-33-generic root=UUID=f69e5f68-84a2-4ef4-8fc0-50503dced4a3 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/01/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080014 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: G31-M7 TE dmi.board.vendor: BIOSTAR Group dmi.chassis.asset.tag: None dmi.chassis.type: 3 dmi.chassis.vendor: BIOSTAR Group dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080014:bd02/01/2010:svnBIOSTARGroup:pnG31-M7TE:pvr:rvnBIOSTARGroup:rnG31-M7TE:rvr:cvnBIOSTARGroup:ct3:cvr: dmi.product.name: G31-M7 TE dmi.sys.vendor: BIOSTAR Group version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1 version.libdrm2: libdrm2 2.4.56-1~ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Mon Apr 6 09:17:21 2015 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputUSB USB Keykoard KEYBOARD, id 8 inputUSB USB Keykoard KEYBOARD, id 9 inputImPS/2 Generic Wheel Mouse MOUSE, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 17570 vendor GSM xserver.version: 2:1.16.0-1ubuntu1.2~trusty2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1440803/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1441380] Re: Voicemail alert in notification panel unlinked
** Also affects: telephony-service (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1441380 Title: Voicemail alert in notification panel unlinked Status in telephony-service package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: When a voicemail alert appears in the notification panel there is no way to dial voicemail from there directly. The incoming notification that a voicemail has been received does not appear in Messages. Necessary to add the voicemail short dial to Contacts and access manually from there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1441380/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1437959] Re: Screen on when a notification arrives
** Project changed: unity8 = unity8 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1437959 Title: Screen on when a notification arrives Status in unity8 package in Ubuntu: New Bug description: Basically, when you receive a text message, the screen automaticaly goes on... even on your pocket. Maybe BQ can use the light sensor to determine if it's on a pocket or on the table. I think that's not right, it shouldn't go on like that for many reasons, one you can unlock the device and make a call, two it spents battery. I don't know if there's a report of this, but I think it's kinda useless. Although, I recommend change the led income message from blue to another colour. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1437959/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1437959] Re: Screen on when a notification arrives
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity8 (Ubuntu) Status: New = Confirmed -- 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/1437959 Title: Screen on when a notification arrives Status in unity8 package in Ubuntu: New Bug description: Basically, when you receive a text message, the screen automaticaly goes on... even on your pocket. Maybe BQ can use the light sensor to determine if it's on a pocket or on the table. I think that's not right, it shouldn't go on like that for many reasons, one you can unlock the device and make a call, two it spents battery. I don't know if there's a report of this, but I think it's kinda useless. Although, I recommend change the led income message from blue to another colour. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1437959/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1215957] Re: [greeter] needs a configuration interface for the authentification method to use
** No longer affects: ubuntu-system-settings -- 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/1215957 Title: [greeter] needs a configuration interface for the authentification method to use Status in ubuntu-system-settings package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Triaged Bug description: That's part of the design in https://wiki.ubuntu.com/SecurityAndPrivacySettings#phone-locking: it should be possible to lock screen on suspend or not To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1215957/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1260768] Re: Fix the ApplyUpdate() D-Bus API
** No longer affects: ubuntu-system-settings ** Changed in: ubuntu-system-settings (Ubuntu) Assignee: Diego Sarmentero (diegosarmentero) = (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to system-image in Ubuntu. https://bugs.launchpad.net/bugs/1260768 Title: Fix the ApplyUpdate() D-Bus API Status in Ubuntu system image (server/client/updater): Fix Released Status in system-image package in Ubuntu: Fix Released Status in ubuntu-system-settings package in Ubuntu: Triaged Bug description: Bug #1260712 reports the problem where the D-Bus API for ApplyUpdate() was changed but system-settings wasn't prepared to handle the change. During post-mortem discussions, Didier requested that the Rebooting() signal sent by ApplyUpdate() be changed to return an error message string instead of a boolean, with the empty string meaning no error. This bug tracks that request. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-system-image/+bug/1260768/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1207854] Re: [greeter] should provide launcher/camera/notes options
** No longer affects: ubuntu-system-settings -- 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/1207854 Title: [greeter] should provide launcher/camera/notes options Status in ubuntu-system-settings package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Triaged Bug description: The system settings' privacy design [1] has a section When locked, allow: launcher/camera/notes We need to define an configuration layer/interface that let the settings app tell the greeter about those [1] https://wiki.ubuntu.com/SecurityAndPrivacySettings#Phone To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1207854/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 952036] Re: [Bluetooth] starts automatically on start-up. No option in Settings to disable upon start-up and Bluetooth not listed in Start-up applications.
** No longer affects: ubuntu-system-settings -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/952036 Title: [Bluetooth] starts automatically on start-up. No option in Settings to disable upon start-up and Bluetooth not listed in Start-up applications. Status in Bluetooth Menu: New Status in indicator-bluetooth package in Ubuntu: New Bug description: Bluetooth starts automatically on start-up. No option in Settings to disable upon start-up and Bluetooth not listed in Start-up applications. Easy to disable but kind of a pain to have to do it at every start-up. Other than that Bluetooth works properly. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-bluetooth/+bug/952036/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1449981] [NEW] BQ Device - r21: Browser sometimes overlaps notification menu
Public bug reported: Conversely, sometimes the notification bar overlaps the URL bar or content of the browser. Swiping down still gets the notification menu in either case. But on first launch, it typically displays itself beneath the notification area like other apps so I assume this is the intended behaviour? So we have three possible states. killing and restarting the app solves the issue in the short-term. ** Affects: webbrowser-app (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1449981 Title: BQ Device - r21: Browser sometimes overlaps notification menu Status in webbrowser-app package in Ubuntu: New Bug description: Conversely, sometimes the notification bar overlaps the URL bar or content of the browser. Swiping down still gets the notification menu in either case. But on first launch, it typically displays itself beneath the notification area like other apps so I assume this is the intended behaviour? So we have three possible states. killing and restarting the app solves the issue in the short-term. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1449981/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 760140] Re: HOME environmental variable no long preserved with sudo by default
I'm expecting the documented behavior. Please refer Bug #889936 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/760140 Title: HOME environmental variable no long preserved with sudo by default Status in sudo package in Ubuntu: Fix Released Status in sudo source package in Natty: Fix Released Bug description: Binary package hint: sudo As discussed on ubuntu-devel in February https://lists.ubuntu.com/archives/ubuntu- devel/2011-February/032490.html: sudo sh -c 'echo $HOME' no longer returns the current users home directory rather it returns /root. This is a change in behavior from Maverick which kept $HOME. The following debian bug contains information about why this is happening now - http://bugs.debian.org/cgi- bin/bugreport.cgi?bug=596847. The HOME and MAIL environment variables are now reset based on the target user's password database entry when the env_reset sudoers option is enabled (which is the case in the default configuration). Something should be done to ensure there isn't a regression and that $HOME is preserved by default. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: sudo 1.7.4p4-5ubuntu5 ProcVersionSignature: Ubuntu 2.6.38-8.41-server 2.6.38.2 Uname: Linux 2.6.38-8-server x86_64 NonfreeKernelModules: btrfs zlib_deflate libcrc32c ufs qnx4 hfsplus hfs minix ntfs vfat msdos fat jfs xfs exportfs reiserfs nls_utf8 isofs nfs lockd fscache nfs_acl auth_rpcgss sunrpc snd_hrtimer binfmt_misc usblp autofs4 dm_crypt snd_emu10k1_synth snd_emux_synth snd_seq_virmidi snd_seq_midi_emul snd_emu10k1 snd_hda_codec_hdmi snd_hda_codec_idt snd_hda_intel snd_ac97_codec snd_hda_codec ac97_bus snd_pcm snd_util_mem snd_hwdep snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device snd soundcore snd_page_alloc netconsole configfs firewire_sbp2 emu10k1_gp lp gameport parport psmouse serio_raw joydev dcdbas raid10 raid456 async_pq async_xor async_memcpy async_raid6_recov raid6_pq async_tx raid0 multipath linear dm_raid45 xor raid1 hid_logitech ff_memless hid_microsoft usbhid hid usb_storage uas firewire_ohci firewire_core crc_itu_t radeon ahci libahci ttm drm_kms_helper e1000e drm i2c_algo_bit Architecture: amd64 CheckboxSubmission: fee5e196cb921cbd36888f428b38b488 CheckboxSystem: 2a6f54df59af338184485e85cbcf0d32 Date: Wed Apr 13 11:23:27 2011 ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/zsh SourcePackage: sudo UpgradeStatus: Upgraded to natty on 2011-04-10 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/760140/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1448969] Re: GTK3 can't resize treeviewcolumn
Thanks for reporting and investigating this bug. Reverting the commit you mentioned breaks the GTK_POLICY_NEVER case for me (as mentioned in the commit message). Cherry-picking a couple of reverts from the 3.14 cycle seems to work though. Attached is a combined patch of those commits. I'd appreciate if you could test that one as well. ** Patch added: 0001-treeview-enable-column-resizing-with-horizontal-scro.patch https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1448969/+attachment/4387453/+files/0001-treeview-enable-column-resizing-with-horizontal-scro.patch ** Changed in: gtk+3.0 (Ubuntu) Status: Confirmed = In Progress ** Changed in: gtk+3.0 (Ubuntu) Assignee: (unassigned) = Lars Uebernickel (larsu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1448969 Title: GTK3 can't resize treeviewcolumn Status in gtk+3.0 package in Ubuntu: In Progress Bug description: there's a bug in gtk+ 3.10 and 3.12 (Ubuntu 14.04 and 14.10) which prevents user from resizing a column in TreeView. In the sample code below, when started, try to resize the 'File Name' column so the Size in bytes' column would go out of the view - right now it's not possible. It was working with gtk2 and it's working with gtk 3.14. Please use sample code from attachement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1448969/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1449983] [NEW] [15.04] After rebooting my WiFi router, NM fails to reconnect to it
Public bug reported: Reproduce: 1. Connect to a wifi 2. Reboot wifi router What happens: I am not reconnected, neither does the AP appear in nm-applet What should happen: I should be reconnected as soon as the AP is up again Running $ sudo wpa_cli and doing a scan + scan_results shows the AP almost immediately after it comes back up. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu15 Uname: Linux 3.19.0-031900-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 29 13:29:08 2015 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20120703-2 EcryptfsInUse: Yes IfupdownConfig: auto lo iface lo inet loopback InstallationDate: Installed on 2013-08-27 (610 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20120703-15:08 IpRoute: default via 192.168.10.1 dev wlan0 proto static metric 1024 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.10.0/24 dev wlan0 proto kernel scope link src 192.168.10.129 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlan0 wifi connected/org/freedesktop/NetworkManager/Devices/1 MonkeySphere2.0 f0d993c2-30e4-437c-b629-c09a4a61c10b /org/freedesktop/NetworkManager/ActiveConnection/13 eth1ethernet unavailable /org/freedesktop/NetworkManager/Devices/4 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- virbr0-nic tap unmanaged/org/freedesktop/NetworkManager/Devices/2 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1449983 Title: [15.04] After rebooting my WiFi router, NM fails to reconnect to it Status in network-manager package in Ubuntu: New Bug description: Reproduce: 1. Connect to a wifi 2. Reboot wifi router What happens: I am not reconnected, neither does the AP appear in nm-applet What should happen: I should be reconnected as soon as the AP is up again Running $ sudo wpa_cli and doing a scan + scan_results shows the AP almost immediately after it comes back up. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu15 Uname: Linux 3.19.0-031900-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 29 13:29:08 2015 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20120703-2 EcryptfsInUse: Yes IfupdownConfig: auto lo iface lo inet loopback InstallationDate: Installed on 2013-08-27 (610 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20120703-15:08 IpRoute: default via 192.168.10.1 dev wlan0 proto static metric 1024 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.10.0/24 dev wlan0 proto kernel scope link src 192.168.10.129 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlan0 wifi connected/org/freedesktop/NetworkManager/Devices/1 MonkeySphere2.0 f0d993c2-30e4-437c-b629-c09a4a61c10b /org/freedesktop/NetworkManager/ActiveConnection/13 eth1ethernet unavailable /org/freedesktop/NetworkManager/Devices/4 -- ---- lo loopback
[Touch-packages] [Bug 1427264] Re: using ecryptfs, creating frameworks fail to bind mount issues
Tyler, I got bit by this issue this morning (vivid). The rbind addition outlined in #5 seems to have resolved it for me as well. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1427264 Title: using ecryptfs, creating frameworks fail to bind mount issues Status in click package in Ubuntu: Triaged Status in schroot package in Ubuntu: Confirmed Bug description: Using vivid creating framework fails for ecryptfs users, the issue is similar to bug #769595 The userdir is mounted in a way which makes unmounts fail E: 10mount: umount: /var/lib/schroot/mount/click-ubuntu-sdk-14.10 -armhf-ec6aaf62-31e0-47e9-b2f8-73f0b038fb4d/home/user: target is busy E: 10mount: (In some cases useful info about processes that E: 10mount: use the device is found by lsof(8) or fuser(1).) changing the fstab line to be /home/user /home/user none rw,bind0 0 workarounds the issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1427264/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1449969] [NEW] Assertion failure in registry if author field in .ini file is empty
Public bug reported: Just got this running a go scope with an ini file that had an empty Author field: $ unity-scope-tool myscope.ini scoperegistry: /build/buildd/unity-scopes-api-0.6.16+15.04.20150410.3/src/scopes/ScopeMetadata.cpp:45: unity::scopes::ScopeMetadata::ScopeMetadata(std::unique_ptrunity::scopes::internal::ScopeMetadataImpl): Assertion `!p-author().empty()' failed. file:///usr/share/unity8/ScopeTool.qml:139:23: Unable to assign null to QString User agent string: scopes-api=0.6.16+15.04.20150410.3-0ubuntu1plugin=0.5.4+15.04.20150410.2-0ubuntu1release=15.04 ERROR! Caught unity::scopes::TimeoutException: Request timed out after 5000 milliseconds (endpoint = ipc:///tmp/scope-dev-endpoints.i4CTQh/Registry-R, op = list) Unable to add overview scope, can't find with ID: scopes ** Affects: unity-scopes-api (Ubuntu) Importance: Undecided Assignee: Michi Henning (michihenning) Status: New ** Changed in: unity-scopes-api (Ubuntu) Assignee: (unassigned) = Michi Henning (michihenning) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-api in Ubuntu. https://bugs.launchpad.net/bugs/1449969 Title: Assertion failure in registry if author field in .ini file is empty Status in unity-scopes-api package in Ubuntu: New Bug description: Just got this running a go scope with an ini file that had an empty Author field: $ unity-scope-tool myscope.ini scoperegistry: /build/buildd/unity-scopes-api-0.6.16+15.04.20150410.3/src/scopes/ScopeMetadata.cpp:45: unity::scopes::ScopeMetadata::ScopeMetadata(std::unique_ptrunity::scopes::internal::ScopeMetadataImpl): Assertion `!p-author().empty()' failed. file:///usr/share/unity8/ScopeTool.qml:139:23: Unable to assign null to QString User agent string: scopes-api=0.6.16+15.04.20150410.3-0ubuntu1plugin=0.5.4+15.04.20150410.2-0ubuntu1release=15.04 ERROR! Caught unity::scopes::TimeoutException: Request timed out after 5000 milliseconds (endpoint = ipc:///tmp/scope-dev-endpoints.i4CTQh/Registry-R, op = list) Unable to add overview scope, can't find with ID: scopes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1449969/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1449730] Re: Bluetooth not working on Asus G56JK notebook (Ubtuntu 15.04)
** Package changed: bluez (Ubuntu) = linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1449730 Title: Bluetooth not working on Asus G56JK notebook (Ubtuntu 15.04) Status in linux package in Ubuntu: New Bug description: On Asus ROG G56JK the bluetooth doesn't work: I cannot find any device and no device can see the notebook. Attached there are logs and hw data. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1449730/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1449628] Re: X-Ubuntu-Splash-Color=#ffffff yields #f5f5f5
To be honest i'm undecided too. I agree with you it's weird that the developer says use this color and we show a different one. On the other hand it's the same case than in the MainView of the SDK is doing so it makes sense that if people are using a backgroundColor in their MainView they can use the same color in the splash and actually get the same color in the splash than in the MainView. I agree it's weird that if you use the same color on the icon than in the splash background it is weird it looks different in the icon than in the background, but it on the other hand the icon is one of the things people are usually very strict about, so modifying the colors of people's icons is also not the best of the ideas :/ So basically we need some decision on wheter we should either: * Not change the background color specified by the developer with papering (and thus not matching what the SDK MainView does) * It's ok changing the colors of the icon of the application -- 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/1449628 Title: X-Ubuntu-Splash-Color=#ff yields #f5f5f5 Status in Ubuntu UX bugs: New Status in unity8 package in Ubuntu: New Bug description: I tried using a white-background app icon with a white-background splash color, but they didn't render the same. I took a screenshot and discovered that unity8 was rendering a white splash (#ff) as #f5f5f5. Switching my app icon to use that same off white as its background fixed the visual glitch. But why does unity8 do that? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1449628/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1441380] [NEW] Voicemail alert in notification panel unlinked
You have been subscribed to a public bug: When a voicemail alert appears in the notification panel there is no way to dial voicemail from there directly. The incoming notification that a voicemail has been received does not appear in Messages. Necessary to add the voicemail short dial to Contacts and access manually from there. ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New -- Voicemail alert in notification panel unlinked https://bugs.launchpad.net/bugs/1441380 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1449925] [NEW] SIM PIN unlock dialog mis-titled opening from indicator
Public bug reported: Version: ubuntu-touch/stable/bq-aquaris.en r21 krillin Steps to reproduce: * 2 SIMs in the device both PIN locked * both SIMs connected to network * indicator-network - enable Flight Mode * wait till disconnected * indicator-network - disable Flight Mode * wait for indicator updated Actual results: - hit SIM 1 unlock button, dialog titled Enter SIM 2 PIN note that dialog does acutally refer to SIM1 and will unlock it, hitting the Cancel X and then second attempt to unlock results in correct title - hit SIM 2 unlock button, dialog titled Enter SIM 1 PIN same behaviour as SIM1 Expected result: - always show the correct title on the unlock dialog ** Affects: canonical-devices-system-image Importance: Undecided Status: New ** Affects: indicator-network (Ubuntu) Importance: Undecided Status: New ** Also affects: indicator-network (Ubuntu) Importance: Undecided Status: New -- 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/1449925 Title: SIM PIN unlock dialog mis-titled opening from indicator Status in the base for Ubuntu mobile products: New Status in indicator-network package in Ubuntu: New Bug description: Version: ubuntu-touch/stable/bq-aquaris.en r21 krillin Steps to reproduce: * 2 SIMs in the device both PIN locked * both SIMs connected to network * indicator-network - enable Flight Mode * wait till disconnected * indicator-network - disable Flight Mode * wait for indicator updated Actual results: - hit SIM 1 unlock button, dialog titled Enter SIM 2 PIN note that dialog does acutally refer to SIM1 and will unlock it, hitting the Cancel X and then second attempt to unlock results in correct title - hit SIM 2 unlock button, dialog titled Enter SIM 1 PIN same behaviour as SIM1 Expected result: - always show the correct title on the unlock dialog To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1449925/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1314587] Re: Windows slow/stall/freeze when minimizing/restoring/etc in Unity 7 (14.04 and 14.10)
I use Ubuntu 14.04 64 bits with NVidia propietary drivers (downloaded from Nvidia website). I have the same problem only when nautilus manages desktop. The workaround for me is gsettings set org.gnome.desktop.background show-desktop-icons false. -- 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/1314587 Title: Windows slow/stall/freeze when minimizing/restoring/etc in Unity 7 (14.04 and 14.10) Status in Unity: Confirmed Status in X.Org X server: Confirmed Status in unity package in Ubuntu: Triaged Status in xorg package in Ubuntu: Triaged Bug description: Steps to reproduce: * Minimize current window or alt-tab between windows * Reveal launcher to click on application * Click `Super` to bring up Dash * Hold `Super` to bring up Keyboard Shortcuts What should happen: Action completes smoothly and quickly. What happens instead: * Action may be slow / animation jerky. * Action may stall (animation frozen on given frame, e.g. window partially minimized) - initiating another action cancels first action and second action may succeed (most often calling Guake with F12 seems to solve the issue) * Action may freeze - cursor no longer moves - a soft reboot (Alt+PrtScr+REISUB) usually works, otherwise a hard reboot Notes: * Not application specific. Minimizing is reliably slow/stalls with minimizing Firefox (including 29, I do not have a lot of bookmarks) or Pidgin, but I use those programs more often. * I am using an Nvidia Optimus machine with the default Nouveau driver - no `nvidia-prime`, no Bumblebee. I temporarily installed the latest stable Nvidia driver (including `nvidia-prime`) and it made no difference. * I did not experience this issue on the same machine running 13.10 (with Bumblebee). * I am running Maximus. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 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: Wed Apr 30 12:53:15 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10, 3.13.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:04b6] NVIDIA Corporation GF108M [GeForce GT 525M] [10de:0df5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:04b6] InstallationDate: Installed on 2014-04-24 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: Dell Inc. Dell System XPS L502X ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=3a8fb3f3-1054-45a0-8ec0-0cbeba33da00 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0YR8NN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA04:bd03/25/2011:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0YR8NN:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L502X dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Wed Apr 30 12:03:43 2014 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0)
[Touch-packages] [Bug 1449899] [NEW] menu bar
Public bug reported: I found the bug, when i minimized the windows using keyboard shorcut (ctrl + super + D) the last window title including menu appears there in menu bar. Which is supposed to show Ubuntu Desktop ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.17.2-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: Wed Apr 29 13:25:35 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c2] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0220] Subsystem: Dell Device [1028:0220] InstallationDate: Installed on 2015-04-29 (0 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) MachineType: Dell Inc. OptiPlex 330 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic root=UUID=4c805262-9894-46e7-a8fc-0364fdc85370 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/20/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 0KP561 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA01:bd12/20/2007:svnDellInc.:pnOptiPlex330:pvr:rvnDellInc.:rn0KP561:rvr:cvnDellInc.:ct3:cvr: dmi.product.name: OptiPlex 330 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.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: Wed Apr 29 12:08:10 2015 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputDell Dell USB Keyboard KEYBOARD, id 8 input USB OPTICAL MOUSE MOUSE, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 40999 vendor DEL xserver.version: 2:1.17.1-0ubuntu3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu vivid -- 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/1449899 Title: menu bar Status in xorg package in Ubuntu: New Bug description: I found the bug, when i minimized the windows using keyboard shorcut (ctrl + super + D) the last window title including menu appears there in menu bar. Which is supposed to show Ubuntu Desktop ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.17.2-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: Wed Apr 29 13:25:35 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c2] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0220] Subsystem: Dell Device [1028:0220] InstallationDate: Installed on 2015-04-29 (0 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) MachineType: Dell Inc. OptiPlex 330 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic
[Touch-packages] [Bug 1241376] Re: procps (1:3.2.8-11ubuntu6.1) upgrade error
(actually /etc/sysctl.d/100-scalr.conf - can't edit) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1241376 Title: procps (1:3.2.8-11ubuntu6.1) upgrade error Status in procps package in Ubuntu: Confirmed Bug description: When trying to upgrade procps on ubuntu 12.04.3 LTS I receive some errors, the package stays in broken state and cannot be upgraded: procps (1:3.2.8-11ubuntu6.1) wird eingerichtet ... start: Job failed to start invoke-rc.d: initscript procps, action start failed. dpkg: Fehler beim Bearbeiten von procps (--configure): Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück Es wurde kein Apport-Bericht verfasst, da das Limit MaxReports bereits erreicht ist Fehler traten auf beim Bearbeiten von: procps E: Sub-process /usr/bin/dpkg returned an error code (1) Ein Paket konnte nicht installiert werden. Versuch, dies zu lösen: procps (1:3.2.8-11ubuntu6.1) wird eingerichtet ... start: Job failed to start invoke-rc.d: initscript procps, action start failed. dpkg: Fehler beim Bearbeiten von procps (--configure): Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück Fehler traten auf beim Bearbeiten von: procps The versions of procps: Installiert: 1:3.2.8-11ubuntu6.1 Kandidat:1:3.2.8-11ubuntu6.2 Versionstabelle: 1:3.2.8-11ubuntu6.2 0 500 http://de.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages *** 1:3.2.8-11ubuntu6.1 0 100 /var/lib/dpkg/status 1:3.2.8-11ubuntu6 0 500 http://de.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages I also ran cat /etc/sysctl.d/*.conf /etc/sysctl.conf | sudo sysctl -p - without an error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1241376/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1425071] Re: package ca-certificates 20141019ubuntu0.14.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ca-certificates (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1425071 Title: package ca-certificates 20141019ubuntu0.14.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in ca-certificates package in Ubuntu: Confirmed Bug description: failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: ca-certificates 20141019ubuntu0.14.04.1 ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 Date: Tue Feb 24 12:14:00 2015 DuplicateSignature: package:ca-certificates:20141019ubuntu0.14.04.1:subprocess installed post-installation script returned error exit status 128 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2015-02-24 (0 days ago) InstallationMedia: Mythbuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) PackageArchitecture: all SourcePackage: ca-certificates Title: package ca-certificates 20141019ubuntu0.14.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1425071/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1241376] Re: procps (1:3.2.8-11ubuntu6.1) upgrade error
I got: error: Invalid argument setting key kernel.msgmnb in my procps.log This confirmed that Scalr client was the problem in: ./sysctl.d/100-scalr.conf Commenting out the defining line solved it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1241376 Title: procps (1:3.2.8-11ubuntu6.1) upgrade error Status in procps package in Ubuntu: Confirmed Bug description: When trying to upgrade procps on ubuntu 12.04.3 LTS I receive some errors, the package stays in broken state and cannot be upgraded: procps (1:3.2.8-11ubuntu6.1) wird eingerichtet ... start: Job failed to start invoke-rc.d: initscript procps, action start failed. dpkg: Fehler beim Bearbeiten von procps (--configure): Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück Es wurde kein Apport-Bericht verfasst, da das Limit MaxReports bereits erreicht ist Fehler traten auf beim Bearbeiten von: procps E: Sub-process /usr/bin/dpkg returned an error code (1) Ein Paket konnte nicht installiert werden. Versuch, dies zu lösen: procps (1:3.2.8-11ubuntu6.1) wird eingerichtet ... start: Job failed to start invoke-rc.d: initscript procps, action start failed. dpkg: Fehler beim Bearbeiten von procps (--configure): Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück Fehler traten auf beim Bearbeiten von: procps The versions of procps: Installiert: 1:3.2.8-11ubuntu6.1 Kandidat:1:3.2.8-11ubuntu6.2 Versionstabelle: 1:3.2.8-11ubuntu6.2 0 500 http://de.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages *** 1:3.2.8-11ubuntu6.1 0 100 /var/lib/dpkg/status 1:3.2.8-11ubuntu6 0 500 http://de.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages I also ran cat /etc/sysctl.d/*.conf /etc/sysctl.conf | sudo sysctl -p - without an error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1241376/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1448775] Re: Unable to login after upgrade from 14.10 to 15.04 possible XOrg crash
** No longer affects: xorg (Ubuntu) ** Also affects: compiz Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1448775 Title: Unable to login after upgrade from 14.10 to 15.04 possible XOrg crash Status in Compiz: New Status in unity package in Ubuntu: New Bug description: After upgrade from working machine with 14.10 to 15.10 I'm unable to login. Right after password screen I see loading of desktop and I'm returned to password prompt again. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,mousepoll,imgpng,unitymtgrabhandles,move,compiztoolbox,place,grid,wall,vpswitch,regex,resize,gnomecompat,snap,session,animation,expo,workarounds,ezoom,fade,scale,unityshell] Date: Sun Apr 26 23:07:55 2015 DistUpgraded: 2015-04-26 22:20:44,130 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.26: added EcryptfsInUse: Yes ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: NVIDIA Corporation GT218M [GeForce 315M] [10de:0a7a] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems GeForce 315M [1179:fd71] InstallationDate: Installed on 2014-11-07 (170 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: TOSHIBA SATELLITE C670-10V ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic root=UUID=28cea712-ba61-42af-a038-545501a067f8 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to vivid on 2015-04-26 (0 days ago) dmi.bios.date: 04/20/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.40 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: TKBSC dmi.board.vendor: TOSHIBA dmi.board.version: 1.40 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.40:bd04/20/2011:svnTOSHIBA:pnSATELLITEC670-10V:pvrPSC3QE-00700JPL:rvnTOSHIBA:rnTKBSC:rvr1.40:cvnTOSHIBA:ct9:cvrToBeFilledByO.E.M.: dmi.product.name: SATELLITE C670-10V dmi.product.version: PSC3QE-00700JPL dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Sun Apr 26 23:07:32 2015 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.17.1-0ubuntu3 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1448775/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1109029] Re: Depend on linux-initramfs-tools
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: watershed (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kbd in Ubuntu. https://bugs.launchpad.net/bugs/1109029 Title: Depend on linux-initramfs-tools Status in apparmor package in Ubuntu: Confirmed Status in console-setup package in Ubuntu: Confirmed Status in kbd package in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Released Status in lvm2 package in Ubuntu: Confirmed Status in multipath-tools package in Ubuntu: Confirmed Status in plymouth package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Invalid Status in udev package in Ubuntu: Confirmed Status in watershed package in Ubuntu: Confirmed Bug description: Many core packages depend on initramfs-tools when they should actually depend on linux-initramfs-tools (virtual package provided by initramfs-tools and dracut). Debian seems to be using Depends: initramfs-tools | linux-initramfs- tools for almost every relevant package. See also bug #1108987, which is about the fact that dracut shouldn't conflict with initramfs-tools. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1109029/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1109029] Re: Depend on linux-initramfs-tools
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apparmor (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kbd in Ubuntu. https://bugs.launchpad.net/bugs/1109029 Title: Depend on linux-initramfs-tools Status in apparmor package in Ubuntu: Confirmed Status in console-setup package in Ubuntu: Confirmed Status in kbd package in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Released Status in lvm2 package in Ubuntu: Confirmed Status in multipath-tools package in Ubuntu: Confirmed Status in plymouth package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Invalid Status in udev package in Ubuntu: Confirmed Status in watershed package in Ubuntu: Confirmed Bug description: Many core packages depend on initramfs-tools when they should actually depend on linux-initramfs-tools (virtual package provided by initramfs-tools and dracut). Debian seems to be using Depends: initramfs-tools | linux-initramfs- tools for almost every relevant package. See also bug #1108987, which is about the fact that dracut shouldn't conflict with initramfs-tools. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1109029/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1109029] Re: Depend on linux-initramfs-tools
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: plymouth (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kbd in Ubuntu. https://bugs.launchpad.net/bugs/1109029 Title: Depend on linux-initramfs-tools Status in apparmor package in Ubuntu: Confirmed Status in console-setup package in Ubuntu: Confirmed Status in kbd package in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Released Status in lvm2 package in Ubuntu: Confirmed Status in multipath-tools package in Ubuntu: Confirmed Status in plymouth package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Invalid Status in udev package in Ubuntu: Confirmed Status in watershed package in Ubuntu: Confirmed Bug description: Many core packages depend on initramfs-tools when they should actually depend on linux-initramfs-tools (virtual package provided by initramfs-tools and dracut). Debian seems to be using Depends: initramfs-tools | linux-initramfs- tools for almost every relevant package. See also bug #1108987, which is about the fact that dracut shouldn't conflict with initramfs-tools. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1109029/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1440162] Re: Misplaced spinner in sound menu
** Changed in: indicator-sound (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ido in Ubuntu. https://bugs.launchpad.net/bugs/1440162 Title: Misplaced spinner in sound menu Status in ido package in Ubuntu: Confirmed Status in indicator-sound package in Ubuntu: Invalid Bug description: See attachment To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ido/+bug/1440162/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1413290] Re: [scopes] Handling large numbers of favourited scopes
It is currently pending design whether the pagination dots will remain at all going forward. -- 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/1413290 Title: [scopes] Handling large numbers of favourited scopes Status in Ubuntu UX bugs: Triaged Status in unity8 package in Ubuntu: Confirmed Bug description: Version: ubuntu-touch/ubuntu-rtm/14.09-proposed r202 krillin Currently there does not appear to be a limit to the number of scopes that can be favourited. Apart from consuming phone resources, this causes the pagination dots at the top to exceed the width of one scope page (see attachments). Should we limit the number of favourited scopes? Display the pagination dots differently? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1413290/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 962082] Re: Profiles that require duplex audio like Head Set (HSP) and Hands Free (HFP) do not work on machines with Broadcom BCM20702A0 Bluetooth chips
Hi, here http://plugable.com/2014/06/23/plugable-usb-bluetooth-adapter-solving-hfphsp-profile-issues-on-linux there is a solutions for properly reading the firmware module for Broadcom BCM20702A0 chip in the kernel for version 3.18+. In my case it works well. Let me know if this solve the problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/962082 Title: Profiles that require duplex audio like Head Set (HSP) and Hands Free (HFP) do not work on machines with Broadcom BCM20702A0 Bluetooth chips Status in HWE Next Project: Fix Released Status in bluez package in Ubuntu: Fix Released Bug description: This problem seems to occur on every device that uses the BCM20702A0 Bluetooth hardware. How to reproduce: (1) Pair a bluetooth headset with a machine equipped with a BCM20702A0. (2) Activate the device. Usually there is a button on the headset you should press to notify the bluetooth stack that you're ready to use the device. This creates SCO link and the plumbs the audio components. (3) Open the sound settings tool and select the bluetooth device under the Input and Output tabs. Under each tab you should see a table with an entry that has a headset icon on the left with the bluetooth device name to the right. This is the item to select. Now, everything should be configured so that you can use your bluetooth device to hear and record audio. Test this by: Testing Input: (1) In the sound settings tool, select the Input tab. (2) Make sure the Input Volume is not muted and the scale widget is not set to zero. (3) Make sounds into the headset mic -- you should see the Input Level bar raise. Testing Output: In the same program: (1) Select the Hardware tab. (2) In the box labeled Choose a device to configure, select your bluetooth device. (3) A combobox should appear at the bottom of the window labeled Settings for the selected device. Choose Telephony Duplex (HSP/HFP). (4) Now click on the Test Speakers button to the right. (5) Run speaker test. You should hear a sound. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/962082/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1329141] Re: Two underscores in .desktop file name causes assumption that this is an appId and app is rejected.
** Changed in: unity8 (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1329141 Title: Two underscores in .desktop file name causes assumption that this is an appId and app is rejected. Status in Qt integration with the Mir display server: New Status in Ubuntu Application Launcher: Fix Released Status in Ubuntu UI Toolkit: Fix Released Status in Unity Mir: Won't Fix Status in qtubuntu package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Invalid Bug description: On the daily image testing for mako, image#78, one of the lifecycle management tests in unity failed because of a qmlscene crash (see attachment). 21:15:34.162 INFO _launcher:116 - Attempting to launch application 'tmp991xm1vf' with URIs '' via upstart-app-launch 21:15:36.367 INFO _launcher:116 - Attempting to launch application 'tmpbeb_op_3' with URIs '' via upstart-app-launch 21:16:08.689 ERROR _launcher:202 - Timed out waiting for Application with app_id 'tmpbeb_op_3' to stop. http://ci.ubuntu.com/smokeng/utopic/touch/mako/78:20140611.1:20140530/8530/unity8/1241528/ To manage notifications about this bug go to: https://bugs.launchpad.net/qtmir/+bug/1329141/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1446658] Re: lxc-test-apparmor fails on aarch64
I also find the same issue in another ARM board, I can confirm that it's just following sentence to cause the failed result: run_cmd lxc-create -t download -n c1 -- -d ubuntu -r trusty -a $ARCH It will try to check the following file and download a image from website indexed in this file, if success, then create a container. http://images.linuxcontainers.org//meta/1.0/index-user Because the parameter $ARCH is arm64 definitely, and I can't find any index with arm64 in above file and any arm64 directory in following position yet. http://images.linuxcontainers.org/images/ubuntu/vivid/ I guess this is just the root case of this issue. I also find the similar sentence in following file, and all these test cases will fail on ARM board too, I think this is their common root cause. lxc-test-apparmor-mount lxc-test-usernic lxc-test-autostart lxc-test-usernic.in Beside this, I also found there are so many hard-code about trusty in multi lxc-tests cases listed as follows: justin@D02-VIVID:~/lxc/lxc-1.1.2/src/tests$ grep -R 'trusty' . ./lxc-test-apparmor-mount:run_cmd lxc-create -t download -n $cname -- -d ubuntu -r trusty -a $ARCH Binary file ./get_item.o matches ./lxc-test-usernic.in:run_cmd lxc-create -t download -n b1 -- -d ubuntu -r trusty -a $ARCH ./lxc-test-autostart:lxc-create -t download -n $CONTAINER_NAME -- -d ubuntu -r trusty -a $ARCH ./lxc-test-usernic:run_cmd lxc-create -t download -n b1 -- -d ubuntu -r trusty -a $ARCH Binary file ./lxc-test-get_item matches Binary file ./lxc-test-createtest matches ./lxc-test-unpriv:run_cmd lxc-create -t download -n c1 -- -d ubuntu -r trusty -a $ARCH I'm afraid that if this will cause that these test cases can't be compatible to different Ubuntu distribution? -- 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/1446658 Title: lxc-test-apparmor fails on aarch64 Status in apparmor package in Ubuntu: New Bug description: Running lxc-test-apparmor fails on aarch64 (arm64) systems. The following files which are listed in files_to_deny[] in src/tests/aa.c: /sys/kernel/uevent_helper /proc/sys/kernel/sysrq are not denied, but should be. Perhaps I should be changing the apparmor profile for lxc before running the tests (but that's just a guess). I'm invoking the tests as: # for i in /usr/bin/lxc-test-* ; do $i || touch /tmp/$(basename $i).failed; done which results in the following failures: lxc-test-apparmor.failed lxc-test-autostart.failed lxc-test-containertests.failed lxc-test-unpriv.failed ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lxc 1.0.7-0ubuntu0.1 ProcVersionSignature: Error: [Errno 2] No such file or directory: '/proc/version_signature' Uname: Linux 3.19.2 aarch64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: arm64 Date: Tue Apr 21 13:17:28 2015 ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx --- ApportVersion: 2.14.1-0ubuntu3.7 Architecture: arm64 DistroRelease: Ubuntu 14.04 KernLog: Package: lxc 1.0.7-0ubuntu0.1 PackageArchitecture: arm64 ProcCmdline: console=ttyS0,115200n8 root=/dev/sda1 rw rootwait ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Error: [Errno 2] No such file or directory: '/proc/version_signature' Tags: trusty uec-images Uname: Linux 3.19.2 aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: kvm libvirtd _MarkForUpload: True defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx lxcsyslog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1446658/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1449628] Re: X-Ubuntu-Splash-Color=#ffffff yields #f5f5f5
** Also affects: ubuntu-ux Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1449628 Title: X-Ubuntu-Splash-Color=#ff yields #f5f5f5 Status in Ubuntu UX bugs: New Status in unity8 package in Ubuntu: New Bug description: I tried using a white-background app icon with a white-background splash color, but they didn't render the same. I took a screenshot and discovered that unity8 was rendering a white splash (#ff) as #f5f5f5. Switching my app icon to use that same off white as its background fixed the visual glitch. But why does unity8 do that? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1449628/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1449917] [NEW] camera-app can't work in vivid
Public bug reported: the version is 3.0.0+15.04.20150313-0ubuntu1, it's black screen. cheese 3.14.1-2ubuntu4 works fine. And also below command works fine. $ gst-launch-1.0 v4l2src ! xvimagesink ** Affects: camera-app Importance: Undecided Status: New ** Affects: camera-app (Ubuntu) Importance: Undecided Status: New ** Also affects: camera-app Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1449917 Title: camera-app can't work in vivid Status in Camera App: New Status in camera-app package in Ubuntu: New Bug description: the version is 3.0.0+15.04.20150313-0ubuntu1, it's black screen. cheese 3.14.1-2ubuntu4 works fine. And also below command works fine. $ gst-launch-1.0 v4l2src ! xvimagesink To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1449917/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1443051] Re: Some texts deliver a blank message
Thank you for your bug report, can you reproduce everytime sending long messages or a specific emoji to this contact? How do you enter the emoji character? ** Changed in: messaging-app (Ubuntu) Status: New = Incomplete ** Changed in: messaging-app (Ubuntu) Importance: Undecided = High -- 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/1443051 Title: Some texts deliver a blank message Status in messaging-app package in Ubuntu: Incomplete Bug description: When I send a text message to someone sometimes they receive a blank text. This has happened on two occasions, first when the text was rather long, after I split it into two texts it delivered fine. And another time which I sent a few times which became blank on the receiving phone I removed the emoji character and then the text went through fine, the receiving person has an Iphone. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1443051/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1441380] Re: Voicemail alert in notification panel unlinked
the notification is rather an telephony-service or unity8 issue (depending if that's a backend or ui bug) ** Project changed: messaging-app = unity8 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1441380 Title: Voicemail alert in notification panel unlinked Status in unity8 package in Ubuntu: New Bug description: When a voicemail alert appears in the notification panel there is no way to dial voicemail from there directly. The incoming notification that a voicemail has been received does not appear in Messages. Necessary to add the voicemail short dial to Contacts and access manually from there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1441380/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1443051] Re: Some texts deliver a blank message
the unicode number suggest the emoji is http://www.emojibase.com/emoji/1f3a5/moviecamera ? -- 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/1443051 Title: Some texts deliver a blank message Status in messaging-app package in Ubuntu: Incomplete Bug description: When I send a text message to someone sometimes they receive a blank text. This has happened on two occasions, first when the text was rather long, after I split it into two texts it delivered fine. And another time which I sent a few times which became blank on the receiving phone I removed the emoji character and then the text went through fine, the receiving person has an Iphone. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1443051/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1329141] Re: Two underscores in .desktop file name causes assumption that this is an appId and app is rejected.
** Changed in: unity-mir Status: New = Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1329141 Title: Two underscores in .desktop file name causes assumption that this is an appId and app is rejected. Status in Qt integration with the Mir display server: New Status in Ubuntu Application Launcher: Fix Released Status in Ubuntu UI Toolkit: Fix Released Status in Unity Mir: Won't Fix Status in qtubuntu package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Invalid Bug description: On the daily image testing for mako, image#78, one of the lifecycle management tests in unity failed because of a qmlscene crash (see attachment). 21:15:34.162 INFO _launcher:116 - Attempting to launch application 'tmp991xm1vf' with URIs '' via upstart-app-launch 21:15:36.367 INFO _launcher:116 - Attempting to launch application 'tmpbeb_op_3' with URIs '' via upstart-app-launch 21:16:08.689 ERROR _launcher:202 - Timed out waiting for Application with app_id 'tmpbeb_op_3' to stop. http://ci.ubuntu.com/smokeng/utopic/touch/mako/78:20140611.1:20140530/8530/unity8/1241528/ To manage notifications about this bug go to: https://bugs.launchpad.net/qtmir/+bug/1329141/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1449928] [NEW] Navigation breaks after selecting artist card in My Music
Public bug reported: 1. Make sure you have some music files on the phone. Go to My Music scope 2. Tap an artist card - a large artist card is displayed and albums and tracks of selected artist is displayed. Expected in addition: a back button is displayed so that user can go back to the surfacing results page. Search entry box is populated with selected artist. Actual behavior: there is no back button. The only way to get back is to pull-to-refresh. Note: this only affects vivid. RTM image is not affected. ** Affects: canonical-devices-system-image Importance: Undecided Status: New ** Affects: unity-scope-mediascanner Importance: High Assignee: Pawel Stolowski (stolowski) Status: Confirmed ** Affects: unity-scopes-shell (Ubuntu) Importance: Undecided Assignee: Pawel Stolowski (stolowski) Status: New ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Also affects: unity-scopes-shell (Ubuntu) Importance: Undecided Status: New ** Changed in: unity-scope-mediascanner Assignee: (unassigned) = Pawel Stolowski (stolowski) ** Changed in: unity-scopes-shell (Ubuntu) Assignee: (unassigned) = Pawel Stolowski (stolowski) ** Branch linked: lp:~stolowski/unity-scopes-shell/reset-user-data ** Branch linked: lp:~stolowski/unity-scope-mediascanner/fix-navigation -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-shell in Ubuntu. https://bugs.launchpad.net/bugs/1449928 Title: Navigation breaks after selecting artist card in My Music Status in the base for Ubuntu mobile products: New Status in Unity Media Scanner Scope: Confirmed Status in unity-scopes-shell package in Ubuntu: New Bug description: 1. Make sure you have some music files on the phone. Go to My Music scope 2. Tap an artist card - a large artist card is displayed and albums and tracks of selected artist is displayed. Expected in addition: a back button is displayed so that user can go back to the surfacing results page. Search entry box is populated with selected artist. Actual behavior: there is no back button. The only way to get back is to pull-to-refresh. Note: this only affects vivid. RTM image is not affected. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1449928/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1439958] Re: Always receive duplicated SMS ans MMS
does it do that with every contact you have or only specific ones? -- 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/1439958 Title: Always receive duplicated SMS ans MMS Status in messaging-app package in Ubuntu: Confirmed Bug description: When someone send me a SMS or MMS, I always receive it twice and sometimes for the MMS is 10 times. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1439958/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1439101] Re: impossible receive MMS any operator on bq aquaris E4.5
seems similar to bug #1417976, does it work if you turn wifi off? Maybe you can provide the info requested in the other bug? ** Tags added: bq ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Also affects: telephony-service Importance: Undecided Status: New ** Changed in: telephony-service Importance: Undecided = High -- 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/1439101 Title: impossible receive MMS any operator on bq aquaris E4.5 Status in the base for Ubuntu mobile products: New Status in Messaging App: New Status in Telephony Service: New Status in Ubuntu Mobile: New Status in messaging-app package in Ubuntu: Confirmed Bug description: In France no MMS is received regardless of the operator used on bq aquaris E4.5 ubuntu Edition For information, my operator is Free even if it seems it doesn't matter. In the same time, let me tell you than I had detect than MMS didn't sent when WIFI is ON. I've read some other people who send the same information so it's seems to be a real bug. Anyway, for resume, For send a MMS, it's OK whan WIFI is OFF, don'T if ON, and in all of case we don't receive MMS :-(( Thank's to you for fix it faster. Sorry for my approximativ english. Fabien To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1439101/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1423811] Re: 219-1ubuntu1 regression: boot hangs, logind fails
I cannot reproduce this with current upstream git master any more, so I ran another bisect. Apparently http://cgit.freedesktop.org/systemd/systemd/commit/?id=6410 fixes this, so I guess the regression was introduced in http://cgit.freedesktop.org/systemd/systemd/commit/?id=a354329f72 and the reverted commit http://cgit.freedesktop.org/systemd/systemd/commit/?id=13790add4bf64 merely exposed the bug as journald was (one of the) first user of fd storage. http://cgit.freedesktop.org/systemd/systemd/commit/?id=6410 applies cleanly on top of v219-stable, so I replaced our reverted patch with a backport of that fix: http://anonscm.debian.org/cgit/pkg- systemd/systemd.git/commit/?h=experimentalid=894d0f2d21d8ed18 Now the boot-smoke test still succeeds with that package. ** Changed in: systemd Status: New = 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/1423811 Title: 219-1ubuntu1 regression: boot hangs, logind fails Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd package in Debian: Fix Released Status in systemd package in Fedora: Unknown Bug description: Since yesterday, systemd does not boot properly any more. It takes very long, ends up in an X failsafe session, and eventually you just get a getty on VT1. Downgrading libpam-systemd libsystemd0 systemd systemd-sysv to https://launchpad.net/ubuntu/+source/systemd/218-10ubuntu2 fixes the boot again. This happens both with the standard quiet splash $vt_handoff as well as without these tree options, i. e. text mode boot. $ sudo systemctl list-jobs JOB UNITTYPESTATE 1634 sound.targetstopwaiting 1176 NetworkManager.service start running 1598 cgproxy.service start waiting 1632 failsafe-graphical.target stopwaiting 1563 alsa-restore.servicestart waiting 1594 plymouth-quit-wait.service start waiting 1588 getty-static.servicestart waiting 1562 alsa-state.service start waiting 121 systemd-update-utmp-runlevel.servicestart waiting 1640 ifup@wlan0.service stopwaiting 1544 systemd-ask-password-plymouth.path start waiting 1507 friendly-recovery.service start waiting 1607 anacron.service start waiting 1489 systemd-binfmt.service start waiting 1637 system-systemd\x2drfkill.slice stopwaiting 1636 systemd-rfkill@rfkill1.service stopwaiting 1631 failsafe-x.service stopwaiting 1638 systemd-backlight@backlight:intel_backlight.service stopwaiting 1610 pppd-dns.servicestart waiting 1483 systemd-machine-id-commit.service start waiting 1635 system-systemd\x2dbacklight.slice stopwaiting 1557 systemd-hwdb-update.service start waiting 1630 systemd-backlight@backlight:acpi_video0.service stopwaiting 1500 sys-kernel-config.mount start waiting 92 multi-user.target start waiting 1509 debian-fixup.servicestart waiting 1641 systemd-rfkill@rfkill0.service stopwaiting 1613 plymouth-quit.service start waiting 1639 system-ifup.slice stopwaiting 1642 ifup@lxcbr0.service stopwaiting 1633 acpid.service stopwaiting 1643 systemd-logind.service restart waiting 1543 plymouth-start.service start waiting 1499 plymouth-read-write.service start waiting Attaching debug journal. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-1ubuntu1 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 CurrentDesktop: Unity Date: Fri Feb 20 07:39:03 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2014-11-20 (91 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141119) MachineType: LENOVO 2324CTO ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.18.0-13-generic.efi.signed
[Touch-packages] [Bug 1413290] Re: [scopes] Handling large numbers of favourited scopes
** Branch linked: lp:~huangzhiquan/unity8/lp-141329-changedotspacing ** Branch linked: lp:~huangzhiquan/unity8/lp-141329-limitnumber-20 -- 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/1413290 Title: [scopes] Handling large numbers of favourited scopes Status in Ubuntu UX bugs: Triaged Status in unity8 package in Ubuntu: Confirmed Bug description: Version: ubuntu-touch/ubuntu-rtm/14.09-proposed r202 krillin Currently there does not appear to be a limit to the number of scopes that can be favourited. Apart from consuming phone resources, this causes the pagination dots at the top to exceed the width of one scope page (see attachments). Should we limit the number of favourited scopes? Display the pagination dots differently? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1413290/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1449737] Re: gallery and camera icons turn black after the r21 update
in fact, the icons became transparent. and it's not only camera and gallery, it's also calculator, music, reminders, twitter, and weather. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to system-image in Ubuntu. https://bugs.launchpad.net/bugs/1449737 Title: gallery and camera icons turn black after the r21 update Status in system-image package in Ubuntu: New Bug description: i got the bq ubuntu phone a week ago and did the update immediately. unfortunately this turned the gallery and camera icons in side bar and in the apps scope to black. and they stayed black since then. is there some kind of an icon-update workaround? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-image/+bug/1449737/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1448438] Re: Home directories created with invalid mode
I created this bug because of possible misconfiguration of Ubuntu. The umask should be set in /etc/login.defs and with no other magic umasks for the user. Please transfer this bug report for those who are resposible of Ubuntu's configuration, thanks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1448438 Title: Home directories created with invalid mode Status in coreutils package in Ubuntu: Incomplete Bug description: When creating a new directory inside ~/ Ubuntu 15.04: Mode is 0775. Ubuntu 14.10: Mode is 0755. UMASK is 022 in both cases so the mode should be 0755. This bug is for Ubuntu 15.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1448438/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1450009] [NEW] systemd started xubuntu 15.04 lets system sleep after boot and start of lightdm greeter
Public bug reported: Using systemd as init system on a HP zbook15 notebook having 2 external monitors connected using a docking station and starting with lid closed the system goes to sleep after successfully booting and starting lightdm greeter. Sometimes there's enough time to enter username and password but system goes to sleep every time after a few seconds. The system can be woken up and used after this happens but it will not let me shutdown later. The problem is just present in docked situation starting with closed lid using systemd a init system. If notebook is used in non-docked situation with open lid and systemd the problem does not occur. Workaround: A switch back to upstart as init system resolves the issue. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd-sysv 219-7ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Wed Apr 29 14:46:09 2015 InstallationDate: Installed on 2015-04-27 (1 days ago) InstallationMedia: Xubuntu 15.04 Vivid Vervet - Release amd64 (20150422.1) SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1450009 Title: systemd started xubuntu 15.04 lets system sleep after boot and start of lightdm greeter Status in systemd package in Ubuntu: New Bug description: Using systemd as init system on a HP zbook15 notebook having 2 external monitors connected using a docking station and starting with lid closed the system goes to sleep after successfully booting and starting lightdm greeter. Sometimes there's enough time to enter username and password but system goes to sleep every time after a few seconds. The system can be woken up and used after this happens but it will not let me shutdown later. The problem is just present in docked situation starting with closed lid using systemd a init system. If notebook is used in non-docked situation with open lid and systemd the problem does not occur. Workaround: A switch back to upstart as init system resolves the issue. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd-sysv 219-7ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Wed Apr 29 14:46:09 2015 InstallationDate: Installed on 2015-04-27 (1 days ago) InstallationMedia: Xubuntu 15.04 Vivid Vervet - Release amd64 (20150422.1) SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1450009/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1450013] [NEW] dbus puts system to sleep every 30 seconds
Public bug reported: After upgrading from 14.10 to 15.04, I found that the system was going to sleep every 30 seconds. This behavior does not manifest once I log into the graphical desktop (Lubuntu), but if I switch over to a virtual console, it manifests again. A temporary fix has been to make /sys/power/state non-writable. At first, I believed the problem was with systemd, but the problem continues after switching to upstart. I believe the problem is in the dbus package, because I see this every 30 seconds in /var/log/syslog, coinciding with the laptop going to sleep: Apr 29 07:46:58 socrates dbus[701]: [system] Activating service name='org.freedesktop.systemd1' (using servicehelper) Apr 29 07:46:58 socrates dbus[701]: [system] Successfully activated service 'org.freedesktop.systemd1' Apr 29 07:46:58 socrates kernel: [ 529.289164] init: anacron main process (17760) killed by TERM signal Apr 29 07:47:01 socrates anacron[18796]: Anacron 2.3 started on 2015-04-29 Apr 29 07:47:01 socrates anacron[18796]: Will run job `cron.daily' in 5 min. Apr 29 07:47:01 socrates anacron[18796]: Will run job `cron.weekly' in 10 min. Apr 29 07:47:01 socrates anacron[18796]: Jobs will be executed sequentially Apr 29 07:47:30 socrates acpid: client connected from 19009[0:0] Apr 29 07:47:30 socrates acpid: 1 client rule loaded ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: dbus 1.8.12-1ubuntu5 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic i686 ApportVersion: 2.17.2-0ubuntu1 Architecture: i386 CurrentDesktop: LXDE Date: Wed Apr 29 07:53:42 2015 InstallationDate: Installed on 2010-04-30 (1824 days ago) InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429) ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: dbus UpgradeStatus: Upgraded to vivid on 2015-04-27 (1 days ago) ** Affects: dbus (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1450013 Title: dbus puts system to sleep every 30 seconds Status in dbus package in Ubuntu: New Bug description: After upgrading from 14.10 to 15.04, I found that the system was going to sleep every 30 seconds. This behavior does not manifest once I log into the graphical desktop (Lubuntu), but if I switch over to a virtual console, it manifests again. A temporary fix has been to make /sys/power/state non-writable. At first, I believed the problem was with systemd, but the problem continues after switching to upstart. I believe the problem is in the dbus package, because I see this every 30 seconds in /var/log/syslog, coinciding with the laptop going to sleep: Apr 29 07:46:58 socrates dbus[701]: [system] Activating service name='org.freedesktop.systemd1' (using servicehelper) Apr 29 07:46:58 socrates dbus[701]: [system] Successfully activated service 'org.freedesktop.systemd1' Apr 29 07:46:58 socrates kernel: [ 529.289164] init: anacron main process (17760) killed by TERM signal Apr 29 07:47:01 socrates anacron[18796]: Anacron 2.3 started on 2015-04-29 Apr 29 07:47:01 socrates anacron[18796]: Will run job `cron.daily' in 5 min. Apr 29 07:47:01 socrates anacron[18796]: Will run job `cron.weekly' in 10 min. Apr 29 07:47:01 socrates anacron[18796]: Jobs will be executed sequentially Apr 29 07:47:30 socrates acpid: client connected from 19009[0:0] Apr 29 07:47:30 socrates acpid: 1 client rule loaded ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: dbus 1.8.12-1ubuntu5 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic i686 ApportVersion: 2.17.2-0ubuntu1 Architecture: i386 CurrentDesktop: LXDE Date: Wed Apr 29 07:53:42 2015 InstallationDate: Installed on 2010-04-30 (1824 days ago) InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429) ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: dbus UpgradeStatus: Upgraded to vivid on 2015-04-27 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1450013/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1449991] Re: Upgrade poppler to latest stable version 0.32
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: poppler (Ubuntu) Status: New = Confirmed -- 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/1449991 Title: Upgrade poppler to latest stable version 0.32 Status in poppler package in Ubuntu: Confirmed Bug description: Please upgrade poppler and poppler-utils to latest stable version, which is 0.32 since March 2015 See also http://poppler.freedesktop.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1449991/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1377872] Re: Double-buffered compositing performance is sometimes very poor (30 FPS) on intel
Just for clarity's sake, INTEL_DEBUG=sync doesn't seem to make any difference, but nbuffers=3 seems to avert the problem -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1377872 Title: Double-buffered compositing performance is sometimes very poor (30 FPS) on intel Status in Mesa: Confirmed Status in Mir: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: Double-buffered compositing performance is sometimes artificially poor on some intel systems. When this happens the frame rate seen is halved - about 30 FPS. However at the same time, Mir is observed to use very little render time and both the CPU and GPU are still mostly idle. It's just the Intel DRM logic sometimes takes two frames (~32ms) to complete a single page flip. Two known workarounds avoid the issue: (a) Add glFinish() into the mesa DisplayBuffer code; or (b) env INTEL_DEBUG=sync for the Mir server binary. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1377872/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1419001] Re: Reminders trigger at the time of the event and not before by default
** Branch linked: lp:~pkunal-parmar/ubuntu-calendar-app/DefReminderTime ** Changed in: ubuntu-calendar-app Status: Confirmed = In Progress ** Changed in: ubuntu-calendar-app Assignee: Alan Pope (popey) = Kunal Parmar (pkunal-parmar) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1419001 Title: Reminders trigger at the time of the event and not before by default Status in the base for Ubuntu mobile products: Confirmed Status in Calendar application for Ubuntu devices: In Progress Status in indicator-datetime package in Ubuntu: Fix Released Status in qtorganizer5-eds package in Ubuntu: Invalid Bug description: Sync of google calendar. The Google calendar setting is set by default to notify 10 min prior to all meetings. Is it possible to get this default notification time from google with the sync? or can we add a setting for a default notification time in the calendar app? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1419001/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1448775] Re: Unable to login after upgrade from 14.10 to 15.04 possible XOrg crash
If you feel comfortable doing so, could you please attach the Compiz core dump for when this occurs? It may help give us some clues about what's going on. Also, it appears you had the nvidia binary driver installed at one time and now you are using nouveau. I'm wondering if there is still some cruft left over from the nvidia driver causing this issue... Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1448775 Title: Unable to login after upgrade from 14.10 to 15.04 possible XOrg crash Status in Compiz: New Status in unity package in Ubuntu: New Bug description: After upgrade from working machine with 14.10 to 15.10 I'm unable to login. Right after password screen I see loading of desktop and I'm returned to password prompt again. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,mousepoll,imgpng,unitymtgrabhandles,move,compiztoolbox,place,grid,wall,vpswitch,regex,resize,gnomecompat,snap,session,animation,expo,workarounds,ezoom,fade,scale,unityshell] Date: Sun Apr 26 23:07:55 2015 DistUpgraded: 2015-04-26 22:20:44,130 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.26: added EcryptfsInUse: Yes ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: NVIDIA Corporation GT218M [GeForce 315M] [10de:0a7a] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems GeForce 315M [1179:fd71] InstallationDate: Installed on 2014-11-07 (170 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: TOSHIBA SATELLITE C670-10V ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic root=UUID=28cea712-ba61-42af-a038-545501a067f8 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to vivid on 2015-04-26 (0 days ago) dmi.bios.date: 04/20/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.40 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: TKBSC dmi.board.vendor: TOSHIBA dmi.board.version: 1.40 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.40:bd04/20/2011:svnTOSHIBA:pnSATELLITEC670-10V:pvrPSC3QE-00700JPL:rvnTOSHIBA:rnTKBSC:rvr1.40:cvnTOSHIBA:ct9:cvrToBeFilledByO.E.M.: dmi.product.name: SATELLITE C670-10V dmi.product.version: PSC3QE-00700JPL dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Sun Apr 26 23:07:32 2015 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.17.1-0ubuntu3 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1448775/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1448969] Re: GTK3 can't resize treeviewcolumn
The attachment 0001-treeview-enable-column-resizing-with-horizontal- scro.patch seems to be a patch. If it isn't, please remove the patch flag from the attachment, remove the patch tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1448969 Title: GTK3 can't resize treeviewcolumn Status in gtk+3.0 package in Ubuntu: In Progress Bug description: there's a bug in gtk+ 3.10 and 3.12 (Ubuntu 14.04 and 14.10) which prevents user from resizing a column in TreeView. In the sample code below, when started, try to resize the 'File Name' column so the Size in bytes' column would go out of the view - right now it's not possible. It was working with gtk2 and it's working with gtk 3.14. Please use sample code from attachement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1448969/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1449991] [NEW] Upgrade poppler to latest stable version 0.32
Public bug reported: Please upgrade poppler and poppler-utils to latest stable version, which is 0.32 since March 2015 See also http://poppler.freedesktop.org/ ** Affects: poppler (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: 15.04 15.10 upgrade-software-version -- 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/1449991 Title: Upgrade poppler to latest stable version 0.32 Status in poppler package in Ubuntu: Confirmed Bug description: Please upgrade poppler and poppler-utils to latest stable version, which is 0.32 since March 2015 See also http://poppler.freedesktop.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1449991/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1421455] Re: Slow wake up time on physical power button pressed
I was monitoring my syslog while pressing the button. Apr 29 14:37:35 ubuntu-phablet powerd[949]: handle_requestSysState from :1.13 - ACTIVE (1) Apr 29 14:37:35 ubuntu-phablet powerd[949]: name_watch_add: looking for :1.13 Apr 29 14:37:35 ubuntu-phablet powerd[949]: watching :1.13 to see when it disappears on dbus Apr 29 14:37:35 ubuntu-phablet powerd[949]: libsuspend: acquire_wake_lock: powerd_power_request Apr 29 14:37:35 ubuntu-phablet powerd[949]: handle_requestSysState - SUCCESS Apr 29 14:37:35 ubuntu-phablet powerd[949]: Enqueue state change to ACTIVE Apr 29 14:37:35 ubuntu-phablet powerd[949]: exiting suspend Apr 29 14:37:35 ubuntu-phablet powerd[949]: libsuspend: exit_suspend. Apr 29 14:37:35 ubuntu-phablet kernel: [21759.723201][Ker_PM][request_suspend_state]wakeup (3-0) at 21760134073325 (2015-04-29 12:37:35.882532317 UTC) exactly here there is a short delay Apr 29 14:37:36 ubuntu-phablet powerd[949]: Emitting signal for transition to state ACTIVE (1) Apr 29 14:37:36 ubuntu-phablet powerd[949]: Transition to ACTIVE complete Apr 29 14:37:36 ubuntu-phablet powerd[949]: libsuspend: release_wake_lock: powerd_power_request Apr 29 14:37:36 ubuntu-phablet kernel: [21760.273491]mtk-tpd: TPD wake up Apr 29 14:37:36 ubuntu-phablet powerd[949]: light_dev: setting brightness to 120 Apr 29 14:37:36 ubuntu-phablet kernel: [21760.310044]mtk-tpd: TPD wake up done Apr 29 14:37:36 ubuntu-phablet kernel: [21760.310066]MAGNETIC mag_context_obj ok---hwm_obj-early_suspend=0 Apr 29 14:37:36 ubuntu-phablet powerd[949]: we get signal from :1.13: DisplayPowerStateChange Apr 29 14:37:36 ubuntu-phablet powerd[949]: Received DisplayPowerStateChange: state=1 flags=2 Since some of those messages are from the kernel ringbuffer, I looked at the corresponding dmesg output: [21606.412808] [Ker_PM][request_suspend_state]wakeup (3-0) at 21606823677239 (2015-04-29 12:35:02.572136231 UTC) [21606.953480] mtk-tpd: TPD wake up [21606.980027] mtk-tpd: TPD wake up done So there seems to be at least half a second of delay between the kernel registering the button press and the display actually being requested to power on. Since display power-on is not instant, the total time from button press to visible display content is close to a second on my device in best case, sometimes up to three seconds and in rare cases the display does not turn on at all. -- 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/1421455 Title: Slow wake up time on physical power button pressed Status in unity8 package in Ubuntu: Incomplete Bug description: Device: bq Aquaris E4.5 running: Stable #17 When pressing on physical power button on device to wake it up sometime it even takes up to 2-3 secs before anything appears on the screen. This time wary but its hard to tell then its shorter and when is longer. This is not so bad on nexus4. Should you need more info, I'm happy to help. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1421455/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1449987] [NEW] [hostname 9333, Intel Haswell HDMI, Digital Out, HDMI] No sound at all
Public bug reported: Very often at the system starting-up the audio isn't working (completely mute). Opening audio settings - output, there is reported none device. Only by typing in bash dpkg-reconfigure oem-audio-hda-daily- dkms_0.201502151246~ubuntu14.04.1_all.deb at system's restart the audio works for only one time, at next system restart there's the same problem. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.16.0-36.48~14.04.1-generic 3.16.7-ckt9 Uname: Linux 3.16.0-36-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D3p: lorenzo2614 F...m pulseaudio /dev/snd/controlC0: lorenzo2614 F pulseaudio CurrentDesktop: Unity Date: Wed Apr 29 13:25:01 2015 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 InstallationDate: Installed on 2014-11-20 (159 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI failed Symptom_Card: Audio interno - HDA Intel HDMI Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D3p: lorenzo2614 F...m pulseaudio /dev/snd/controlC0: lorenzo2614 F pulseaudio Symptom_Jack: Digital Out, HDMI Symptom_Type: No sound at all Title: [hostname 9333, Intel Haswell HDMI, Digital Out, HDMI] No sound at all UpgradeStatus: Upgraded to trusty on 2015-02-14 (73 days ago) dmi.bios.date: 09/11/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0D13CR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA05:bd09/11/2014:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0D13CR:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS13 9333 dmi.sys.vendor: Dell Inc. mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-11-20T15:16:37.735889 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Attachment added: Schermata del 2015-04-29 13:53:30.png https://bugs.launchpad.net/bugs/1449987/+attachment/4387480/+files/Schermata%20del%202015-04-29%2013%3A53%3A30.png -- 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/1449987 Title: [hostname 9333, Intel Haswell HDMI, Digital Out, HDMI] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Very often at the system starting-up the audio isn't working (completely mute). Opening audio settings - output, there is reported none device. Only by typing in bash dpkg-reconfigure oem-audio-hda-daily- dkms_0.201502151246~ubuntu14.04.1_all.deb at system's restart the audio works for only one time, at next system restart there's the same problem. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.16.0-36.48~14.04.1-generic 3.16.7-ckt9 Uname: Linux 3.16.0-36-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D3p: lorenzo2614 F...m pulseaudio /dev/snd/controlC0: lorenzo2614 F pulseaudio CurrentDesktop: Unity Date: Wed Apr 29 13:25:01 2015 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 InstallationDate: Installed on 2014-11-20 (159 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI failed Symptom_Card: Audio interno - HDA Intel HDMI Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D3p: lorenzo2614 F...m pulseaudio /dev/snd/controlC0: lorenzo2614 F pulseaudio Symptom_Jack: Digital Out, HDMI Symptom_Type: No sound at all Title: [hostname 9333, Intel Haswell HDMI, Digital Out, HDMI] No sound at all UpgradeStatus: Upgraded to trusty on 2015-02-14 (73 days ago) dmi.bios.date: 09/11/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0D13CR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias:
[Touch-packages] [Bug 1429887] Re: Pressing power button to resume does not turn on screen
Re-opening powerd task, as OTA3 did *not* solve this problem, and we're still not sure where the problem lies. I'm also going to rename the title to Sometimes need 3 power presses to turn on screen because I want to make this bug more obviously distinct from bug 1421455 and other display bugs. ** Changed in: powerd (Ubuntu) Status: Invalid = New ** Summary changed: - Pressing power button to resume does not turn on screen + Sometimes need 3 power button presses to turn on screen -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to powerd in Ubuntu. https://bugs.launchpad.net/bugs/1429887 Title: Sometimes need 3 power button presses to turn on screen Status in the base for Ubuntu mobile products: New Status in Unity System Compositor: New Status in powerd package in Ubuntu: New Status in unity8 package in Ubuntu: Confirmed Bug description: [filing here although may be other components] Mako running 211 from rtm I experienced these symptoms which have been previously mitigated in other scenarios. Last week while traveling and roaming this happened pretty much 100% of the time. This occurred in all areas (hotel, MWC, outside, etc) Press power button, no response Press button again, screen turns on for a few seconds then turns off Press button again, either phone resumes or more often the power dialog is shown When I returned back home the function was normal without reboot or other changes. The differences in environment: Roaming on foreign GSM network Lots of Wifi APs not connected Attached are some perhaps relevant logs, unfortunately the syslog rolled. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1429887/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1086547] Re: Sound does not switch to internal speakers when headphones unplugged
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New = Confirmed -- 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/1086547 Title: Sound does not switch to internal speakers when headphones unplugged Status in alsa-driver package in Ubuntu: Confirmed Bug description: Previously played sound from both speakers and headphones when headphones plugged in, now sound will only play through headphones (does not return to internal speakers when the headphones are unplugged) ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: alsa-base 1.0.25+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-30.48-generic-pae 3.2.27 Uname: Linux 3.2.0-30-generic-pae i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu15 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: logan 1748 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfc70 irq 46' Mixer name : 'Realtek ALC262' Components : 'HDA:10ec0262,10cf0100,00100202 HDA:11c11040,11c10001,00100200' Controls : 30 Simple ctrls : 17 Date: Tue Dec 4 14:09:47 2012 InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release i386 (20120817.3) MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_Jack: Speaker, Internal Symptom_Type: None of the above Title: [LifeBook T4220, Realtek ALC262, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/15/2008 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.16 dmi.board.name: FJNB1D4 dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: A1A5J3E616A30011 dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.16:bd05/15/2008:svnFUJITSU:pnLifeBookT4220:pvr:rvnFUJITSU:rnFJNB1D4:rvr:cvnA1A5J3E616A30011:ct10:cvr: dmi.product.name: LifeBook T4220 dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1086547/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1395905] Re: better product handling required
** Project changed: unity8 = unity8 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1395905 Title: better product handling required Status in the base for Ubuntu mobile products: Confirmed Status in unity8 package in Ubuntu: New Bug description: the way how bugs are managed needs to be improved To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1395905/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1449938] Re: package cups-daemon 2.0.2-1ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1449938 Title: package cups-daemon 2.0.2-1ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in cups package in Ubuntu: New Bug description: upgrade launched by boot-repair ProblemType: Package DistroRelease: Ubuntu 14.04 Package: cups-daemon 2.0.2-1ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17 Uname: Linux 3.13.0-49-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 CupsErrorLog: Date: Wed Apr 29 11:52:30 2015 DuplicateSignature: package:cups-daemon:2.0.2-1ubuntu3:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2014-12-11 (138 days ago) InstallationMedia: Xubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140723) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Bad file descriptor MachineType: ASUSTeK COMPUTER INC. X555LA Papersize: a4 PpdFiles: PDF: Generic CUPS-PDF Printer Brother-HL-2170W: Brother HL-2170W Foomatic/hpijs-pcl5e (recommended) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-49-generic.efi.signed root=UUID=249b3ed7-4f39-4348-babd-b761b1b9d430 ro quiet splash intel_pstate=enable vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-49-generic.efi.signed root=UUID=249b3ed7-4f39-4348-babd-b761b1b9d430 ro quiet splash intel_pstate=enable vt.handoff=7 SourcePackage: cups Title: package cups-daemon 2.0.2-1ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/06/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555LA.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555LA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555LA.307:bd08/06/2014:svnASUSTeKCOMPUTERINC.:pnX555LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X555LA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. modified.conffile..etc.default.cups: # Cups configure options # LOAD_LP_MODULE: enable/disable to load lp parallel printer driver module # LOAD_LP_MODULE has migrated to /etc/modules-load.d/cups-filters.conf # LOAD_LP_MODULE=yes mtime.conffile..etc.default.cups: 2014-07-23T20:26:05 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1449938/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1373312] [NEW] Phablet album art not coming through from media-hub
You have been subscribed to a public bug: Not showing the correct album art if it is present. dict entry( string art-url variantstring file:///usr/share/unity/icons/album_missing.png ) We also shouldn't be using album_missing.png. It's supplied by libunity-core. We should be using the icon theme. ** Affects: media-hub Importance: High Assignee: Thomas Voß (thomas-voss) Status: Triaged ** Affects: unity8 (Ubuntu) Importance: High Status: Triaged ** Tags: lt-category-visible lt-date-20141001 lt-prio-high lt-whitelisted rtm14 -- Phablet album art not coming through from media-hub https://bugs.launchpad.net/bugs/1373312 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1437959] [NEW] Screen on when a notification arrives
You have been subscribed to a public bug: Basically, when you receive a text message, the screen automaticaly goes on... even on your pocket. Maybe BQ can use the light sensor to determine if it's on a pocket or on the table. I think that's not right, it shouldn't go on like that for many reasons, one you can unlock the device and make a call, two it spents battery. I don't know if there's a report of this, but I think it's kinda useless. Although, I recommend change the led income message from blue to another colour. ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Tags: bq -- Screen on when a notification arrives https://bugs.launchpad.net/bugs/1437959 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1449938] [NEW] package cups-daemon 2.0.2-1ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: upgrade launched by boot-repair ProblemType: Package DistroRelease: Ubuntu 14.04 Package: cups-daemon 2.0.2-1ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17 Uname: Linux 3.13.0-49-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 CupsErrorLog: Date: Wed Apr 29 11:52:30 2015 DuplicateSignature: package:cups-daemon:2.0.2-1ubuntu3:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2014-12-11 (138 days ago) InstallationMedia: Xubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140723) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Bad file descriptor MachineType: ASUSTeK COMPUTER INC. X555LA Papersize: a4 PpdFiles: PDF: Generic CUPS-PDF Printer Brother-HL-2170W: Brother HL-2170W Foomatic/hpijs-pcl5e (recommended) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-49-generic.efi.signed root=UUID=249b3ed7-4f39-4348-babd-b761b1b9d430 ro quiet splash intel_pstate=enable vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-49-generic.efi.signed root=UUID=249b3ed7-4f39-4348-babd-b761b1b9d430 ro quiet splash intel_pstate=enable vt.handoff=7 SourcePackage: cups Title: package cups-daemon 2.0.2-1ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/06/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555LA.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555LA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555LA.307:bd08/06/2014:svnASUSTeKCOMPUTERINC.:pnX555LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X555LA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. modified.conffile..etc.default.cups: # Cups configure options # LOAD_LP_MODULE: enable/disable to load lp parallel printer driver module # LOAD_LP_MODULE has migrated to /etc/modules-load.d/cups-filters.conf # LOAD_LP_MODULE=yes mtime.conffile..etc.default.cups: 2014-07-23T20:26:05 ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1449938 Title: package cups-daemon 2.0.2-1ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in cups package in Ubuntu: New Bug description: upgrade launched by boot-repair ProblemType: Package DistroRelease: Ubuntu 14.04 Package: cups-daemon 2.0.2-1ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17 Uname: Linux 3.13.0-49-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 CupsErrorLog: Date: Wed Apr 29 11:52:30 2015 DuplicateSignature: package:cups-daemon:2.0.2-1ubuntu3:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2014-12-11 (138 days ago) InstallationMedia: Xubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140723) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Bad file descriptor MachineType: ASUSTeK COMPUTER INC. X555LA Papersize: a4 PpdFiles: PDF: Generic CUPS-PDF Printer Brother-HL-2170W: Brother HL-2170W Foomatic/hpijs-pcl5e (recommended) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-49-generic.efi.signed root=UUID=249b3ed7-4f39-4348-babd-b761b1b9d430 ro quiet splash intel_pstate=enable vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-49-generic.efi.signed root=UUID=249b3ed7-4f39-4348-babd-b761b1b9d430 ro quiet splash intel_pstate=enable vt.handoff=7 SourcePackage: cups Title: package cups-daemon 2.0.2-1ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/06/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555LA.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555LA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias:
[Touch-packages] [Bug 1208418] Re: [greeter] should provide a lock sound option
** No longer affects: ubuntu-system-settings -- 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/1208418 Title: [greeter] should provide a lock sound option Status in Ubuntu UX bugs: Opinion Status in ubuntu-system-settings package in Ubuntu: Triaged Status in unity8 package in Ubuntu: New Bug description: The lock screen should provide an option to make a sound on lock/unlock. https://wiki.ubuntu.com/Sound#Settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1208418/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1373312] Re: Phablet album art not coming through from media-hub
** Project changed: unity8 = unity8 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1373312 Title: Phablet album art not coming through from media-hub Status in Media Hub: Triaged Status in unity8 package in Ubuntu: Triaged Bug description: Not showing the correct album art if it is present. dict entry( string art-url variantstring file:///usr/share/unity/icons/album_missing.png ) We also shouldn't be using album_missing.png. It's supplied by libunity-core. We should be using the icon theme. To manage notifications about this bug go to: https://bugs.launchpad.net/media-hub/+bug/1373312/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 962082] Re: Profiles that require duplex audio like Head Set (HSP) and Hands Free (HFP) do not work on machines with Broadcom BCM20702A0 Bluetooth chips
@erotavlas, thanks but that didn't work for me with an ASUS dongle with the same chip in it. :-( tim@atom:~% lsusb | grep ASUS Bus 003 Device 003: ID 0b05:17cb ASUSTek Computer, Inc. http://www.ebuyer.com/623493-asus-usb-bt400-mini-bluetooth-4-0-usb-adapter-usb-bt400 Asus USB-BT400 - Mini Bluetooth 4.0 USB Adapter I have the same problem of no sound in or out. === Quoting the article in case it moves/vanishes: - It has come to our attention that there are some issues on certain Linux systems with regards to using Headset Profile and Hands-Free Profile with our USB Bluetooth Adapters. The issue stems from a lack of support for these profiles on the Broadcom BCM20702 chipset found inside our device, unless a proprietary firmware file is loaded into it to enable this functionality. The steps to install the firmware are as follows:Screenshot from 2014-06-23 17:34:49 Open your favorite terminal Run the following command to download the firmware file: wget https://s3.amazonaws.com/plugable/bin/fw-0a5c_21e8.hcd Copy the firmware file to the /lib/firmware folder: sudo cp fw-0a5c_21e8.hcd /lib/firmware Reboot New kernel versions have moved the location in which the firmware file has to be installed. The instructions that follow are for kernels 3.18 and newer Open your favorite terminal Run the following command to download the firmware file: wget https://s3.amazonaws.com/plugable/bin/fw-0a5c_21e8.hcd Create the directory /lib/firmware/brcm sudo mkdir /lib/firmware/brcm Copy the firmware file to the /lib/firmware/brcm folder and rename the file to BCM20702A0-0a5c-21e8.hcd: sudo mv fw-0a5c_21e8.hcd /lib/firmware/brcm/BCM20702A0-0a5c-21e8.hcd Reboot That’s it! HFP and HSP profiles should now work without issue! We have also heard of some reports that these steps can solve some issues with other profiles, like A2DP, but have been unable to reproduce the issues. It is possible that newer versions of BlueZ and the Linux kernel have fixed these issues, and that is why we are not seeing them any more. UPDATE: These steps will also fix many incompatibility issues with certain A2DP devices, such as Bluetooth Headsets and Speakers. If you are having trouble pairing your Bluetooth Audio device to your Linux PC, this firmware file will likely fix your issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/962082 Title: Profiles that require duplex audio like Head Set (HSP) and Hands Free (HFP) do not work on machines with Broadcom BCM20702A0 Bluetooth chips Status in HWE Next Project: Fix Released Status in bluez package in Ubuntu: Fix Released Bug description: This problem seems to occur on every device that uses the BCM20702A0 Bluetooth hardware. How to reproduce: (1) Pair a bluetooth headset with a machine equipped with a BCM20702A0. (2) Activate the device. Usually there is a button on the headset you should press to notify the bluetooth stack that you're ready to use the device. This creates SCO link and the plumbs the audio components. (3) Open the sound settings tool and select the bluetooth device under the Input and Output tabs. Under each tab you should see a table with an entry that has a headset icon on the left with the bluetooth device name to the right. This is the item to select. Now, everything should be configured so that you can use your bluetooth device to hear and record audio. Test this by: Testing Input: (1) In the sound settings tool, select the Input tab. (2) Make sure the Input Volume is not muted and the scale widget is not set to zero. (3) Make sounds into the headset mic -- you should see the Input Level bar raise. Testing Output: In the same program: (1) Select the Hardware tab. (2) In the box labeled Choose a device to configure, select your bluetooth device. (3) A combobox should appear at the bottom of the window labeled Settings for the selected device. Choose Telephony Duplex (HSP/HFP). (4) Now click on the Test Speakers button to the right. (5) Run speaker test. You should hear a sound. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/962082/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1395905] [NEW] better product handling required
You have been subscribed to a public bug: the way how bugs are managed needs to be improved ** Affects: canonical-devices-system-image Importance: High Assignee: Canonical Devices Products (canonical-devices-products-team) Status: Confirmed ** Affects: unity8 (Ubuntu) Importance: Undecided Assignee: Pat McGowan (pat-mcgowan) Status: New -- better product handling required https://bugs.launchpad.net/bugs/1395905 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1373312] Re: Phablet album art not coming through from media-hub
Nick, I have no clue what you mean in here. Can you clarify the problem? ** Changed in: unity8 (Ubuntu) Status: Triaged = Incomplete -- 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/1373312 Title: Phablet album art not coming through from media-hub Status in Media Hub: Triaged Status in unity8 package in Ubuntu: Incomplete Bug description: Not showing the correct album art if it is present. dict entry( string art-url variantstring file:///usr/share/unity/icons/album_missing.png ) We also shouldn't be using album_missing.png. It's supplied by libunity-core. We should be using the icon theme. To manage notifications about this bug go to: https://bugs.launchpad.net/media-hub/+bug/1373312/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 962082] Re: Profiles that require duplex audio like Head Set (HSP) and Hands Free (HFP) do not work on machines with Broadcom BCM20702A0 Bluetooth chips
For the record I also have an identical issue with a much older D-Link DBT-122 dongle tim@atom:~% lsusb | grep DBT Bus 001 Device 009: ID 07d1:f101 D-Link System DBT-122 Bluetooth http://www.dlink.com/uk/en/support/product/dbt-122-wireless-usb- bluetooth-adapter This apparently is also a broadcom chip. Snippet from kernel tim@atom:~% udevadm monitor --property ... UDEV [1757.217749] add /devices/pci:00/:00:12.2/usb1/1-5/1-5.1 (usb) ACTION=add BUSNUM=001 DEVNAME=/dev/bus/usb/001/009 DEVNUM=009 DEVPATH=/devices/pci:00/:00:12.2/usb1/1-5/1-5.1 DEVTYPE=usb_device ID_BUS=usb ID_MODEL=D-Link_DBT-122 ID_MODEL_ENC=D-Link\x20DBT-122 ID_MODEL_FROM_DATABASE=DBT-122 Bluetooth ID_MODEL_ID=f101 ID_REVISION=0100 ID_SERIAL=Broadcom_Corp_D-Link_DBT-122 ID_USB_INTERFACES=:e00101:ff:fe0100: ID_VENDOR=Broadcom_Corp ID_VENDOR_ENC=Broadcom\x20Corp ID_VENDOR_FROM_DATABASE=D-Link System ID_VENDOR_ID=07d1 MAJOR=189 MINOR=8 PRODUCT=7d1/f101/100 SEQNUM=2367 SUBSYSTEM=usb TYPE=224/1/1 USEC_INITIALIZED=196931 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/962082 Title: Profiles that require duplex audio like Head Set (HSP) and Hands Free (HFP) do not work on machines with Broadcom BCM20702A0 Bluetooth chips Status in HWE Next Project: Fix Released Status in bluez package in Ubuntu: Fix Released Bug description: This problem seems to occur on every device that uses the BCM20702A0 Bluetooth hardware. How to reproduce: (1) Pair a bluetooth headset with a machine equipped with a BCM20702A0. (2) Activate the device. Usually there is a button on the headset you should press to notify the bluetooth stack that you're ready to use the device. This creates SCO link and the plumbs the audio components. (3) Open the sound settings tool and select the bluetooth device under the Input and Output tabs. Under each tab you should see a table with an entry that has a headset icon on the left with the bluetooth device name to the right. This is the item to select. Now, everything should be configured so that you can use your bluetooth device to hear and record audio. Test this by: Testing Input: (1) In the sound settings tool, select the Input tab. (2) Make sure the Input Volume is not muted and the scale widget is not set to zero. (3) Make sounds into the headset mic -- you should see the Input Level bar raise. Testing Output: In the same program: (1) Select the Hardware tab. (2) In the box labeled Choose a device to configure, select your bluetooth device. (3) A combobox should appear at the bottom of the window labeled Settings for the selected device. Choose Telephony Duplex (HSP/HFP). (4) Now click on the Test Speakers button to the right. (5) Run speaker test. You should hear a sound. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/962082/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1437959] Re: Screen on when a notification arrives
*** This bug is a duplicate of bug 1291455 *** https://bugs.launchpad.net/bugs/1291455 ** This bug has been marked a duplicate of bug 1291455 [greeter] Screen and input should be disabled with proximity sensor when on greeter -- 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/1437959 Title: Screen on when a notification arrives Status in unity8 package in Ubuntu: New Bug description: Basically, when you receive a text message, the screen automaticaly goes on... even on your pocket. Maybe BQ can use the light sensor to determine if it's on a pocket or on the table. I think that's not right, it shouldn't go on like that for many reasons, one you can unlock the device and make a call, two it spents battery. I don't know if there's a report of this, but I think it's kinda useless. Although, I recommend change the led income message from blue to another colour. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1437959/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1395905] Re: better product handling required
Can this be closed now? ** Changed in: unity8 (Ubuntu) Status: New = Incomplete -- 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/1395905 Title: better product handling required Status in the base for Ubuntu mobile products: Confirmed Status in unity8 package in Ubuntu: Incomplete Bug description: the way how bugs are managed needs to be improved To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1395905/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1388862] [NEW] [messaging] Incoming group message is treated like an individual text
You have been subscribed to a public bug: Receive a message that was sent to a group The message is shown under the thread for the sender There is no information that the text went to a group and no way to reply to the group I understand that we need to treat these messages as MMS in order to do this properly for both incoming and outgoing ** Affects: messaging-app (Ubuntu) Importance: Wishlist Status: New ** Affects: ubuntu-ux Importance: Medium Assignee: Olga Kemmet (olga-kemmet) Status: Triaged ** Tags: ota-2 -- [messaging] Incoming group message is treated like an individual text https://bugs.launchpad.net/bugs/1388862 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1421245] Re: Contact search doesn't support Chinese
** Project changed: messaging-app = messaging-app (Ubuntu) -- 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/1421245 Title: Contact search doesn't support Chinese Status in address-book-app package in Ubuntu: New Status in dialer-app package in Ubuntu: New Status in messaging-app package in Ubuntu: New Bug description: Steps to reproduce 1) Create a contact with a Chinese name 2) Type that name in to the contact search Expected result Just that contact should appear Actual result All contacts appear To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/address-book-app/+bug/1421245/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1418072] Re: Accentuated letter display as ? character on sms
** Project changed: messaging-app = messaging-app (Ubuntu) -- 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/1418072 Title: Accentuated letter display as ? character on sms Status in messaging-app package in Ubuntu: Incomplete Bug description: On krillin, image 224, set to spanish language: when I send messages with á,é,í, etc, it displays (on the recipient's) as ? When I'm sent those same characters, they also are diplayed as ? on the krillin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1418072/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1388420] [NEW] [messaging] + [phone app] Message history shows thread under old contact name
You have been subscribed to a public bug: Add a contact like Joe Receive some messages Change the name of the contact to Fred receive some additional messages Open the main messages panel the message thread appears as Joe Click on Joe and it properly displays Fred in the header with the thread ** Affects: dialer-app Importance: Undecided Status: New ** Affects: messaging-app (Ubuntu) Importance: High Status: New ** Affects: ubuntu-ux Importance: High Assignee: Olga Kemmet (olga-kemmet) Status: Fix Released ** Tags: ota-1 rtm14 usability -- [messaging] + [phone app] Message history shows thread under old contact name https://bugs.launchpad.net/bugs/1388420 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1421245] Re: Contact search doesn't support Chinese
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/1421245 Title: Contact search doesn't support Chinese Status in address-book-app package in Ubuntu: New Status in dialer-app package in Ubuntu: New Status in messaging-app package in Ubuntu: New Bug description: Steps to reproduce 1) Create a contact with a Chinese name 2) Type that name in to the contact search Expected result Just that contact should appear Actual result All contacts appear To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/address-book-app/+bug/1421245/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1379523] [NEW] Photos saved from MMS could use better naming convention
You have been subscribed to a public bug: Receive a photo attachment Select preview and open with gallery The files are named 1.jpeg, 2.jpeg per their order in the message Gallery names them 1.1.jpeg etc as they collide with the last save Camera uses a convention of the form imageMMDD_timeinmesecs.jpg Messaging should do the same or similar with a different prefix. (like attachment or messages) Also, the file extensions are inconsistent jepg vs jpg. This makes it difficult when retrieving the photos from the camera ** Affects: messaging-app (Ubuntu) Importance: Undecided Status: New -- Photos saved from MMS could use better naming convention https://bugs.launchpad.net/bugs/1379523 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1352976] [NEW] Fix small packaging issues as reported in review
You have been subscribed to a public bug: From Michael Terry: for messaging-app... (A) the new build-dep should be sorted into the list and (B) cd obj-$(DEB_HOST_GNU_TYPE); ctest -V should be cd obj-$(DEB_HOST_GNU_TYPE) ctest -V so that we notice when obj-* isn't created where we expect it. I'm not sure they are stop-the-line problems at this point in the silo process, but I would normally needs-fixing an MP for them Please fix for the next release. ** Affects: messaging-app (Ubuntu) Importance: Low Status: Confirmed -- Fix small packaging issues as reported in review https://bugs.launchpad.net/bugs/1352976 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1357460] Re: [messaging app] proposed contacts search blinks after a single letter input
** No longer affects: messaging-app -- 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/1357460 Title: [messaging app] proposed contacts search blinks after a single letter input Status in Ubuntu UX bugs: Fix Committed Status in messaging-app package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. open messaging app 2. swipe from the bottom edge to compose a new message 3. type a letter into the contacts input field in the header - the proposed contacts list appears from nowhere 4. type a 2nd letter - the proposed list blinks and shows the filtered results again 5. type a 3rd letter - proposed list blinks again and shows results --- Expected result: 3. the proposed contact list should roll out from the top, from underneath the header in a smoother way after typing in the first letter or number (if there is a match) 4. after typing the 2nd letter, the list shouldn't blink; the not matching entries should disappear and the matching items just move up smoothly into view 5. see previous point To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1357460/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1363386] Re: Use plural forms where appropriate
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: telephony-service (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1363386 Title: Use plural forms where appropriate Status in Ubuntu Translations: Triaged Status in telephony-service package in Ubuntu: New Bug description: Messages in indicator/metrics.cpp like b%1/b calls made today b%1/b calls received today b%1/b text messages received today b%1/b text messages sent today Spent b%1/b minutes in calls today all need to use plural forms, just like messages %1 missed call / %1 missed calls are using them in indicator/messagingmenu.cpp already. Note that plural forms are required even if you know that there will be more than one, since languages like Serbian use the noun form depending on the last digit of the number (eg. twenty-one will use the same form as one). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1363386/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1389730] Re: [Dialer app] audible feedback after ended call not working in silent mode
** No longer affects: telephony-service -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1389730 Title: [Dialer app] audible feedback after ended call not working in silent mode Status in Ubuntu UX bugs: Fix Committed Status in powerd package in Ubuntu: Invalid Status in telephony-service package in Ubuntu: New Bug description: This bug is related to this one https://bugs.launchpad.net/ubuntu- ux/+bug/1372973 which is marked as fixed-released. The issue is that the beep tone doesn't happen when the phone is in silent mode. Build: r143 Steps to reproduce: 1. switch your device on loud/turn up the sound 2. call your device and hand up the phone you called from 3. you hear a beep when the call is ended 4. now put your device on silent 5. call your device again and hang up Expected result: you hear the beep Actual result: not a sound UX comment-- The beep sound should be played in whatever output the call is performed, internal, speaker, headphones, etc. If user switches the output lets say from speaker to internal, the sound should follow. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1389730/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1433131] Re: [dialer app] pressing power button a 2nd time switches off screen
** No longer affects: telephony-service ** No longer affects: dialer-app (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-system-compositor in Ubuntu. https://bugs.launchpad.net/bugs/1433131 Title: [dialer app] pressing power button a 2nd time switches off screen Status in Ubuntu UX bugs: Fix Committed Status in dialer-app package in Ubuntu: New Status in telephony-service package in Ubuntu: Confirmed Status in unity-system-compositor package in Ubuntu: Confirmed Bug description: This bug is related to this one: https://bugs.launchpad.net/ubuntu- ux/+bug/1376240 While pressing the power button does silence the call but this interaction switches off the screen too. It can look strange for users because it is not clear if the call was just silenced or completely dismissed. UX desired solution: - 1st press of power button silences the call - 2nd press shuts off device screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1433131/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1383477] [NEW] ContactWatcherTest fails on telephony-service when built against Qt 5.3.2
You have been subscribed to a public bug: See build log at https://launchpadlibrarian.net/187780033 /buildlog_ubuntu-utopic-i386.telephony- service_0.1%2B14.10.20141007.1-0ubuntu2_FAILEDTOBUILD.txt.gz 9/9 Test #4: ContactWatcherTest ...***Failed 15.20 sec All Qt 5.3(.2) bugs https://bugs.launchpad.net/bugs/+bugs?field.tag=qt5.3 Info about Qt 5.3.2 testing https://wiki.ubuntu.com/Touch/QtTesting ** Affects: telephony-service (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: qt5.3 -- ContactWatcherTest fails on telephony-service when built against Qt 5.3.2 https://bugs.launchpad.net/bugs/1383477 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1354102] Re: [messaging-app] word count is missing
*** This bug is a duplicate of bug 1278790 *** https://bugs.launchpad.net/bugs/1278790 that's the same issue than bug #1278790 right? ** No longer affects: messaging-app ** This bug has been marked a duplicate of bug 1278790 [Messaging] Show number of characters used -- 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/1354102 Title: [messaging-app] word count is missing Status in Ubuntu UX bugs: Fix Committed Status in messaging-app package in Ubuntu: Confirmed Bug description: When composing a text message, you should be able to see an SMS word count. A SMS is 160 characters and if you go above this word count, then you will be charged for a 2nd SMS. It is not necessary to show the count from the first character but we can show if there are 30 or 40 characters left to write, e.g. 130/160. Please see attached image. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1354102/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1383477] Re: ContactWatcherTest fails on telephony-service when built against Qt 5.3.2
** Project changed: telephony-service = telephony-service (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1383477 Title: ContactWatcherTest fails on telephony-service when built against Qt 5.3.2 Status in telephony-service package in Ubuntu: Incomplete Bug description: See build log at https://launchpadlibrarian.net/187780033 /buildlog_ubuntu-utopic-i386.telephony- service_0.1%2B14.10.20141007.1-0ubuntu2_FAILEDTOBUILD.txt.gz 9/9 Test #4: ContactWatcherTest ...***Failed 15.20 sec All Qt 5.3(.2) bugs https://bugs.launchpad.net/bugs/+bugs?field.tag=qt5.3 Info about Qt 5.3.2 testing https://wiki.ubuntu.com/Touch/QtTesting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1383477/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1363386] Re: Use plural forms where appropriate
** Project changed: telephony-service = telephony-service (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1363386 Title: Use plural forms where appropriate Status in Ubuntu Translations: Triaged Status in telephony-service package in Ubuntu: New Bug description: Messages in indicator/metrics.cpp like b%1/b calls made today b%1/b calls received today b%1/b text messages received today b%1/b text messages sent today Spent b%1/b minutes in calls today all need to use plural forms, just like messages %1 missed call / %1 missed calls are using them in indicator/messagingmenu.cpp already. Note that plural forms are required even if you know that there will be more than one, since languages like Serbian use the noun form depending on the last digit of the number (eg. twenty-one will use the same form as one). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1363386/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1433131] Re: [dialer app] pressing power button a 2nd time switches off screen
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: dialer-app (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-system-compositor in Ubuntu. https://bugs.launchpad.net/bugs/1433131 Title: [dialer app] pressing power button a 2nd time switches off screen Status in Ubuntu UX bugs: Fix Committed Status in dialer-app package in Ubuntu: New Status in telephony-service package in Ubuntu: Confirmed Status in unity-system-compositor package in Ubuntu: Confirmed Bug description: This bug is related to this one: https://bugs.launchpad.net/ubuntu- ux/+bug/1376240 While pressing the power button does silence the call but this interaction switches off the screen too. It can look strange for users because it is not clear if the call was just silenced or completely dismissed. UX desired solution: - 1st press of power button silences the call - 2nd press shuts off device screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1433131/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1435776] Re: NM does not activate ofono Inet contexts w/Username but no Password ( eg. giffgaff )
I added a custom apn config Internet APN: giffgaff.com Username: giffgaff Password: empty I now get a tick on this network and a reliable 3g connection. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1435776 Title: NM does not activate ofono Inet contexts w/Username but no Password ( eg. giffgaff ) Status in the base for Ubuntu mobile products: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: Device: Krillin Software: Vivid r157 NM does not activate a valid ofono context which is present in the gprs file (context_1 in this case) I was able to activate the context manually using ./activate-context /ril_0 1 You can find syslog, list-modems and list-contexts attached To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1435776/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1441746] Re: Missed calls not displaying translated (first boot only, upstart job env issue)
** Project changed: telephony-service = telephony-service (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1441746 Title: Missed calls not displaying translated (first boot only, upstart job env issue) Status in telephony-service package in Ubuntu: Confirmed Bug description: Test case. - Switch the phone to Spanish in System Settings Language. - Receive a phone call and drop it from the other device. Expected result. - A notification is displayed in the messaging indicator. - The notification is translated. Actual result. - Missed call is displayed in English. current build number: 266 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1441746/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1438273] Re: USSD has stopped working
** No longer affects: telephony-service (Ubuntu) ** Project changed: telephony-service = telephony-service (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1438273 Title: USSD has stopped working Status in telephony-service package in Ubuntu: Confirmed Bug description: Entering a USSD code in dialler-app does not work anymore: the code is apparently when pressing the dial button, but there is no reply. However, /usr/share/ofono/scripts/send-ussd /ril_X code seems to work just fine. Image: $ system-image-cli -i current build number: 167 device name: krillin channel: ubuntu-touch/vivid-proposed last update: 2015-03-30 10:06:57 version version: 167 version ubuntu: 20150330 version device: 20150310-ae1ddec version custom: 20150330 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1438273/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1435776] Re: NM does not activate ofono Inet contexts w/Username but no Password ( eg. giffgaff )
Previously the giffgaff Internet refused to stay checked. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1435776 Title: NM does not activate ofono Inet contexts w/Username but no Password ( eg. giffgaff ) Status in the base for Ubuntu mobile products: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: Device: Krillin Software: Vivid r157 NM does not activate a valid ofono context which is present in the gprs file (context_1 in this case) I was able to activate the context manually using ./activate-context /ril_0 1 You can find syslog, list-modems and list-contexts attached To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1435776/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1219337] Re: Users can change the clock without authenticating, allowing them to locally exploit sudo.
Hi Mark - I've taken a look at the details in this bug, the upstream sudo bug, the /r/linux thread, and the upstream sudo fix. I appreciate and respect your thoroughness. After taking all of the details into account, I consider this issue to be low severity due to the mitigating factors involved. Specifically, I don't see a way for an attacker, without physical access, to use an arbitrary code execution vulnerability in combination with the issue that you've described in this bug to elevate his/her privileges. Considering this, the attack requires an admin user leave his/her desktop session unlocked and for an attacker to come across this unlocked desktop session. Since there are many different ways to attack an unlocked desktop session, best security practices dictate all users lock their screens when not at their computer. We will fix this issue in the next Ubuntu release (15.10) by including sudo 1.8.10 or newer. Due to the issue’s low severity and considering our practice of prioritizing resources on publishing security updates that fix issues of greater security impact, we may fix this issue in stable releases of Ubuntu in the future if another sudo vulnerability of higher severity is found or if new details emerge regarding this issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1219337 Title: Users can change the clock without authenticating, allowing them to locally exploit sudo. Status in Cinnamon: New Status in sudo: Unknown Status in Unity: Invalid Status in policykit-desktop-privileges package in Ubuntu: Opinion Status in sudo package in Ubuntu: Confirmed Status in policykit-desktop-privileges source package in Precise: Opinion Status in sudo source package in Precise: Confirmed Status in policykit-desktop-privileges source package in Trusty: Opinion Status in sudo source package in Trusty: Confirmed Status in policykit-desktop-privileges source package in Utopic: Opinion Status in sudo source package in Utopic: Confirmed Status in policykit-desktop-privileges source package in Vivid: Opinion Status in sudo source package in Vivid: Confirmed Bug description: Under unity and cinnamon, it is possible for a user to turn off network-syncronized time and then change the time on the system. It is also possible to cat /var/log/auth.log and find the last time a user authenticated with sudo, along with which pty they used. If a user had used a terminal and successfully authenticated with sudo anytime in the past, and left the sudo file in /var/lib/sudo/username/, a malicious user could walk up to an unlocked, logged in machine and gain sudo without knowing the password for the computer. To do this, a user would only need to launch a few terminals, figure out which pty they were on via tty, find the an instance in /var/log/auth.log where sudo was used on that PTY, and set the clock to that time. Once this is done, they can run (for example) sudo -s and have a full access terminal. 1) This has been observed on Ubuntu 13.04, and may work on other versions. 2) This may have an effect on various window managers, but I confirmed it on Unity and Cinnamon 3) I expected to have to authenticate when I changed the time and date, as I do on Gnome and KDE. I also expected to be denied permission to auth.log 4) I was able to change the system time to whatever I wanted, and view auth.log. This was sufficient to access sudo without having to type my password. Note: This bug also affects any version of OS X, though the mechanism is different. Some versions don't require you to authenticate to change the time through the GUI, but some do. No version I've seen requires authentication to use the systemsetup command, which can alter the time from the command line. This may be an overall bug in sudo. Why can I bypass security by changing the time?! To manage notifications about this bug go to: https://bugs.launchpad.net/cinnamon-desktop/+bug/1219337/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1449101] Re: Upgrading Kubuntu 14.10 to 15.04 boots to console (fails due to read-ony file system)
*** This bug is a duplicate of bug 1431743 *** https://bugs.launchpad.net/bugs/1431743 ** This bug has been marked a duplicate of bug 1431743 fails to boot due to read-ony file system -- 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/1449101 Title: Upgrading Kubuntu 14.10 to 15.04 boots to console (fails due to read- ony file system) Status in systemd package in Ubuntu: Invalid Bug description: After upgrading from Kubuntu 14.10 to 15.04 (final) booting fails. Only console greets me. Lots of errors read-only file system. I can see my files with ls. But nothing works. Selecting the upstart boot from the additional boot options boots normally. Essentially this happens: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1431743 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1449101/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1349582] Re: Autopilot tests are failing on desktop because of the phone number format
** Changed in: dialer-app Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1349582 Title: Autopilot tests are failing on desktop because of the phone number format Status in Dialer app for Ubuntu Touch: Fix Released Status in dialer-app package in Ubuntu: Fix Released Bug description: dialer_app.tests.test_calls.TestCalls.test_outgoing_answer_local_hangup(with mouse) dialer_app.tests.test_dialer.TestDialer.test_erase_button(with mouse) dialer_app.tests.test_calls.TestCalls.test_outgoing_answer_remote_hangup(with mouse) dialer_app.tests.test_calls.TestCalls.test_outgoing_noanswer(with mouse) To manage notifications about this bug go to: https://bugs.launchpad.net/dialer-app/+bug/1349582/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1449842] Re: 15.04 doesn't recognize md raid on boot sometimes
After that happens again, can you please reboot and attach /var/log/syslog ? Thanks! ** Changed in: systemd (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1449842 Title: 15.04 doesn't recognize md raid on boot sometimes Status in systemd package in Ubuntu: Incomplete Bug description: Hello! I have root on ssd, but home on md mirror and lvm over it, about 30% times I boot system systemd stops on searching for lvm volumes on md device, which, I guess it can't recognize, only pressing reset helps, it even can't reboot in alt-ctrl-del. I don't know how to look into boot logs of this systemd. If you'll tell me, I'll do next time. Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1449842/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1421245] Re: Contact search doesn't support Chinese
** Project changed: address-book-app = address-book-app (Ubuntu) -- 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/1421245 Title: Contact search doesn't support Chinese Status in address-book-app package in Ubuntu: New Status in dialer-app package in Ubuntu: New Status in messaging-app package in Ubuntu: New Bug description: Steps to reproduce 1) Create a contact with a Chinese name 2) Type that name in to the contact search Expected result Just that contact should appear Actual result All contacts appear To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/address-book-app/+bug/1421245/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1420976] Re: Cpu usage near 30% when conversation view is open
** Changed in: messaging-app Status: New = Fix Released -- 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/1420976 Title: Cpu usage near 30% when conversation view is open Status in the base for Ubuntu mobile products: Fix Released Status in Messaging App: Fix Released Status in messaging-app package in Ubuntu: Fix Released Status in messaging-app package in Ubuntu RTM: Fix Released Bug description: Steps to reproduce: 1) Receive a message 2) Open conversation view to see that message 3) run top on a terminal Expected behavior: messaging-app should not consume any cpu after initial rendering Current behavior Constant cpu usage near 30% if there are received messages. Not reproducible if there are only sent messages. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1420976/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1426553] Re: [messaging-app] Can't get rid of unread indicator
** Project changed: messaging-app = messaging-app (Ubuntu) -- 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/1426553 Title: [messaging-app] Can't get rid of unread indicator Status in messaging-app package in Ubuntu: New Bug description: This is on my dogfood phone, a mako running ubuntu-touch/stable. I was having a text conversation with someone, and I don't know how this happened, but now I see a permanent unread indicator of 1. Entering the chat view with them does not clear it. What logs would be useful? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1426553/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1417350] Re: [messaging-app] no feedback provided on copy operation
** Changed in: messaging-app Status: New = Fix Released -- 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/1417350 Title: [messaging-app] no feedback provided on copy operation Status in the base for Ubuntu mobile products: New Status in Messaging App: Fix Released Status in Ubuntu UX bugs: Fix Released Status in messaging-app package in Ubuntu: Fix Released Status in messaging-app package in Ubuntu RTM: New Bug description: Expected to see 'Copied to clipboard' as a confirmation after clicking on the 'Copy' icon The testers were not quite sure what happened after they tapped on the 'Copy' icon. The change of colour does not comfirm the effect of users' action effectively. We should display a message saying Selection copied to clipboard or something like that. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1417350/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1416485] Re: [messaging-app] show place holder in message when recv unsupported MMS attachements
** No longer affects: messaging-app -- 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/1416485 Title: [messaging-app] show place holder in message when recv unsupported MMS attachements Status in the base for Ubuntu mobile products: New Status in Ubuntu UX bugs: Fix Committed Status in messaging-app package in Ubuntu: New Status in messaging-app package in Ubuntu RTM: New Bug description: krillin build 224 When we recieve an MMS attachment of a type we don't know how to handle, we should show some sort of default icon/message saying attachment type not supported. Currently we don't display anything so the user gets a blank message. Steps to reproduce: - send a .wav file or some other format to Ubuntu Phone that it doesn't know how to handle Expected results: - I receive the message in the messaging app with a notice that the attachment received cannot be viewed Actual results: - I'm notified of a message but the message is completely blank To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1416485/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1430004] Re: [dialer] + [messaging] + [address book] Screenshot(s) outdated when accessed from device
** No longer affects: messaging-app ** Project changed: dialer-app = messaging-app ** No longer affects: messaging-app (Ubuntu) ** Project changed: messaging-app = messaging-app (Ubuntu) ** No longer affects: address-book-app -- 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/1430004 Title: [dialer] + [messaging] + [address book] Screenshot(s) outdated when accessed from device Status in Ubuntu UX bugs: Fix Committed Status in address-book-app package in Ubuntu: New Status in dialer-app package in Ubuntu: New Status in messaging-app package in Ubuntu: New Status in dialer-app package in Ubuntu RTM: New Status in messaging-app package in Ubuntu RTM: New Bug description: On a phone, long press on any of the default phone apps phone, messaging, contacts Note an old screenshot with the dark theme. These should be replaced with some newer ones. http://people.canonical.com/~alan/screenshots/device-2015-03-09-202935.png http://people.canonical.com/~alan/screenshots/device-2015-03-09-202947.png http://people.canonical.com/~alan/screenshots/device-2015-03-09-203007.png Checked with Gustavo, he will provide screenshots himself. Visuals are not needed from design To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1430004/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
