[Touch-packages] [Bug 409644] Re: Print to file folder chooser dialog creates folders with "Open" button
the issue is fixed in 3.17 ** Changed in: gtk+3.0 (Ubuntu) Status: Confirmed => Fix Committed -- 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/409644 Title: Print to file folder chooser dialog creates folders with "Open" button Status in GTK+ GUI Toolkit: Confirmed Status in gtk+3.0 package in Ubuntu: Fix Committed Bug description: In at least two apps where a filename is entered along with a drop- down directory chooser with an "other" option, the dialog to choose the "other" directory will unintentionally create new directories. gnome-print (?): 1. Start Gedit (or Firefox, etc.). 2. File-->Print... 3. Select "Print to File" under the Printers column. 4. "Save in folder" drop-down --> "Other..." 5. Type "TEST" in the Location. 6. Click "Open" or press Enter. 7. BUG: A folder called "TEST" is created and the folder choosing dialog is closed, with "TEST" selected. gnome-utils (?): 1. Start Take Screenshot (Apps-->Accessories-->Take Screenshot) 2. Continue at #4, above. Since my intention is something like a "save as" operation, and the dialog looks like a save-as dialog, I often type the filename that I want to use, and press enter. But then a directory is created with the filename that I want to use. Very annoying because now I have to find that directory and delete it. To fix this, I have a couple of ideas/suggestions: * Utilize a dedicated directory chooser dialog (is there one for Gnome, as in MS Windows?), or * When a filename is entered in this "other" chooser, the filename in the original dialog (e.g. print-to-file, or Screenshot save preview) should be set to it, and the "save in folder" should also be adjusted to the folder that was open in the dialog. * Fixing the current chooser dialog so it only creates folders when "Create Folder" button is pressed, or * Separate the location+filename selection such as the "Save As..." dialog to a separate stage in the print-to-file process, or * Adjust the print-to-file dialog in some way I don't know yet. Ubuntu 9.04 Gnome 2.26.1 Gedit 2.26.1 Firefox 3.0.13 To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/409644/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1462084] Re: Folder chooser cancels directory creation on dialog confirmation
upstream says it's fixed in 3.17 ** Changed in: gtk+3.0 (Ubuntu) Status: New => Triaged ** Changed in: gtk+3.0 (Ubuntu) Importance: Undecided => Low ** Changed in: gtk+3.0 (Ubuntu) Status: Triaged => Fix Committed -- 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/1462084 Title: Folder chooser cancels directory creation on dialog confirmation Status in GTK+ GUI Toolkit: Confirmed Status in gtk+3.0 package in Ubuntu: Fix Committed Bug description: These steps are in Nautilus, but same happens in e.g. Shotwell, so a gtk bug. Steps to reproduce: - open Nautilus/Files - right-click on an item - choose "Move To..." - click "Create Folder" - type in a folder name (don't press enter) - click "Select" Expected: - folder gets created - the created folder is used as target Current: - folder does not get created - the first folder available is used as target ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: libgtk-3-0 3.14.12-0ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jun 4 22:10:59 2015 SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1462084/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1462087] Re: Folder chooser creates and opens new directory when clicked on another
that's fixed upstream in 3.17 ** Changed in: gtk+3.0 (Ubuntu) Status: New => Fix Committed ** Changed in: gtk+3.0 (Ubuntu) Importance: Undecided => Low -- 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/1462087 Title: Folder chooser creates and opens new directory when clicked on another Status in GTK+ GUI Toolkit: Confirmed Status in gtk+3.0 package in Ubuntu: Fix Committed Bug description: Somewhat related to bug #1462084: These steps are in Nautilus, but same happens in e.g. Shotwell, so a gtk bug. Steps to reproduce: - open Nautilus/Files - right-click on an item - choose "Move To..." - click "Create Folder" - type in a folder name (don't press enter) - click on a different folder Expected: - folder creation is cancelled or - user isn't allowed to click on a different folder Current: - folder is created - the created folder is opened (not the one the user clicked on) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: libgtk-3-0 3.14.12-0ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jun 4 22:10:59 2015 SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1462087/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1226962] Re: Hotkeys not functional in non-latin keyboard layout in 13.10, 14.04, 14.04.1, 14.10, 15.04
** Summary changed: - Hotkeys not functional in non-latin keyboard layout in 13.10, 14.04, 14.04.1, 14.10 + Hotkeys not functional in non-latin keyboard layout in 13.10, 14.04, 14.04.1, 14.10, 15.04 -- 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/1226962 Title: Hotkeys not functional in non-latin keyboard layout in 13.10, 14.04, 14.04.1, 14.10, 15.04 Status in Aptana Studio Installer: New Status in Default settings for the Baltix GNU/Linux OS and desktop: New Status in LibreOffice Productivity Suite: Fix Released Status in IBus: New Status in Indicator keyboard: Fix Released Status in Inkscape: Vector Graphics Editor: New Status in MonoDevelop: New Status in Mutter: Fix Released Status in KDE document viewer: New Status in The OpenOffice.org Suite: New Status in Sigram: New Status in Unity: Fix Released Status in gnome-settings-daemon package in Ubuntu: Triaged Status in gnome-terminal package in Ubuntu: Triaged Status in openjdk-7 package in Ubuntu: Triaged Status in unity package in Ubuntu: Triaged Status in unity-settings-daemon package in Ubuntu: Triaged Status in gnome-settings-daemon package in Fedora: Unknown Status in gnome-shell package in Fedora: Unknown Bug description: New keyboard layout changer in Ubuntu 13.10 introduce old-new bug. Any system or application hotkey witch use char (for example: ctrl+alt+t for terminal or ctrl+t for new tab in browser) become unfunctional when selected non-latin keyboard layout. Hotkeys with F1-12, numbers and other non-character buttons works perfectly. Window manager hotkeys not affected by this bug. All hotkeys in system parameters->keyboard->hotkeys->windows works perfect with any keyboard layout. Workaround for some system hotkeys and two layouts (english and non- latin): rebind all hotkeys in your local layout. For example instead of ctrl+alt+t use ctrl+alt+τ (greek tau). That hotkey still work with english layout. If you use english and two different non-latin layouts this workaround helps only with one of them. Dear Ubuntu users and developers! Please include the following information to your comment about non-latin shortcuts problems: 1. What Ubuntu version do you have (Ubuntu 13.10, Ubuntu 13.10 GNOME, Ubuntu 14.04, Ubuntu 14.04 GNOME and so on), upgraded (describe version) or clean installed 2. What keyboard layout do you have 3. What shortcut for keyboard layout switching do you use 4. On which session you have problems - that is one from Unity, GNOME Shell, GNOME FlashBack/Fallback (Metacity), GNOME FlashBack/Fallback (Compiz) 5. With which program and its version and origin (Ubuntu repositories, PPA, non-deb binary package from some website) you have problems. By providing this information you can make bug-fixing much simpler and may be faster. -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- To manage notifications about this bug go to: https://bugs.launchpad.net/aptana-studio-installer/+bug/1226962/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1436814] Re: Use a roaming indicator for each SIM on dual SIM phones
@Antti Kaijanmäki: Many thanks for the hint. I confirmed that bug #1447479 affects me. -- 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/1436814 Title: Use a roaming indicator for each SIM on dual SIM phones Status in Ubuntu UX bugs: New Status in indicator-network package in Ubuntu: Triaged Bug description: For dual SIM phones, the roaming indicator should be related to each SIM, by having a "R" sign on the top of each signal strength indicator, or by having the roaming indicator in red (or another color) or by having the indicator blinking. I live near a border, and I work on the other side of this border: I have 2 SIM's, one for each country. As the phone is sometime "lazzy" to connect each SIM to the right operator as soon as it becomes available, when I switch from one country to the another, I'm not able to check if both SIM are on the right network: sometime, I place or I receive a call thinking I'm not in the roaming mode... and it is not true. The work around consists to go the the system settings of the phone to check each SIM card and its associated operator. Having an roaming indicator dedicated to each SIM could help: a quick glance is enough to check the card status. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1436814/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1462196] [NEW] indicator-stinotes.py crashed with UnicodeDecodeError in decode(): 'utf-8' coded can't decode byte 0xae in position 5:invalid start byte
Public bug reported: Hello experts, I followed the following steps [1] and installed the stickynotes on Ubuntu 14.04. However, unfortunately, it always crashes with the error saying 'Sorry, Ubuntu 14.04 has experienced an internal error'. The details of this error says the following problem: -- 'indicator-stinotes.py crashed with UnicodeDecodeError in decode(): 'utf-8' coded can't decode byte 0xae in position 5:invalid start byte'. I found this useful post [2] indicating this bug for 14.04, I am not sure if I understand how this patch works. Regarding my python, its - Python 2.7.6 (default, Mar 22 2014, 22:59:56) [GCC 4.8.2] on linux2 I would appreciate any suggestions/comments on fixing this bug. Thanks, pooja [1] --- sudo add-apt-repository ppa:umang/indicator-stickynotes sudo apt-get update sudo apt-get install indicator-stickynotes [2] https://bugs.launchpad.net/ubuntu/+source/software- properties/+bug/1012602 ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1462196 Title: indicator-stinotes.py crashed with UnicodeDecodeError in decode(): 'utf-8' coded can't decode byte 0xae in position 5:invalid start byte Status in software-properties package in Ubuntu: New Bug description: Hello experts, I followed the following steps [1] and installed the stickynotes on Ubuntu 14.04. However, unfortunately, it always crashes with the error saying 'Sorry, Ubuntu 14.04 has experienced an internal error'. The details of this error says the following problem: -- 'indicator-stinotes.py crashed with UnicodeDecodeError in decode(): 'utf-8' coded can't decode byte 0xae in position 5:invalid start byte'. I found this useful post [2] indicating this bug for 14.04, I am not sure if I understand how this patch works. Regarding my python, its - Python 2.7.6 (default, Mar 22 2014, 22:59:56) [GCC 4.8.2] on linux2 I would appreciate any suggestions/comments on fixing this bug. Thanks, pooja [1] --- sudo add-apt-repository ppa:umang/indicator-stickynotes sudo apt-get update sudo apt-get install indicator-stickynotes [2] https://bugs.launchpad.net/ubuntu/+source/software- properties/+bug/1012602 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1462196/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1450747] Re: Native overlay scrollbars aren't themed
Shouldn’t this affect ubuntu-themes instead? =) ** Package changed: gtk+3.0 (Ubuntu) => ubuntu ** Package changed: ubuntu => ubuntu-themes (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1450747 Title: Native overlay scrollbars aren't themed Status in ubuntu-themes package in Ubuntu: Triaged Bug description: In 3.16 (from ppa:ubuntu-desktop/ww + overlay-scrollbar from this PPA), applications have native overlay scrollbars provided by GTK. We want to use these in Ubuntu, but currently they are not themed so look a bit incongruous. I think we want to - Theme them to fit in with Ambiance/Radiance - If possible, show a thumb when the scrollbar is hidden so that you can see where you are in a document To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1450747/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1311494] Re: GTKHEADER BAR SELECTION MODE SUPPORT
** Changed in: ubuntu-themes (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1311494 Title: GTKHEADER BAR SELECTION MODE SUPPORT Status in ubuntu-themes package in Ubuntu: New Bug description: hi, gnambiance is a great and really nice welleriten theme. However: .selection-mode.header-bar * .header-bar .button Support is missing. Result -> Nautilus needs workaround -> gweather -> evince -> epiphany have strange menubar- header bar buttons. See for adwaita as code reference. Ambiance needs to support the new gnome theme standards. I alkso marked it as security vulnerability cause gtk3.10 is ubuntus gtk3 and theme has gtk3.* below ten. I'll try to write fixes for this matter. best regards bluedxca93 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1311494/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1450747] [NEW] Native overlay scrollbars aren't themed
You have been subscribed to a public bug: In 3.16 (from ppa:ubuntu-desktop/ww + overlay-scrollbar from this PPA), applications have native overlay scrollbars provided by GTK. We want to use these in Ubuntu, but currently they are not themed so look a bit incongruous. I think we want to - Theme them to fit in with Ambiance/Radiance - If possible, show a thumb when the scrollbar is hidden so that you can see where you are in a document ** Affects: ubuntu-themes (Ubuntu) Importance: High Assignee: Lars Uebernickel (larsu) Status: Triaged ** Tags: gtk316 -- Native overlay scrollbars aren't themed https://bugs.launchpad.net/bugs/1450747 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes 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 1458696] Re: Doesn't work with new Xmir binary name
Fixed in vivid-proposed. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1458696 Title: Doesn't work with new Xmir binary name Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Committed Status in Light Display Manager 1.12 series: Fix Committed Status in Light Display Manager 1.14 series: Fix Committed Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Trusty: Triaged Status in lightdm source package in Utopic: Triaged Status in lightdm source package in Vivid: Fix Committed Status in lightdm source package in Wily: Fix Released Bug description: [Impact] LightDM doesn't support the new XMir which now has its own binary "Xmir" instead of being an option to the standard X binary. This means that newer versions of XMir will not work with LightDM. It is desirable to SRU the new XMir to older versions of Ubuntu in the future - this change will allow us to do this. [Test Case] Run LightDM with type=unity in lightdm.conf. This should work with both the old XMir and new XMir. [Regression Potential] Low. The change only affects the "unity" seat type and should have no effect on the default "xlocal" seat type. It has been tested with both the old and new XMir and appears to work fine. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1458696/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1456730] Re: Hang after installing and running serviio
It actually hangs for me on a fresh install of 15.04 along with 15.10 Attached journal log from 15.10. The issue seems to be the inability to terminate the serviio.sh java process (PID1848) Line 24190 is where the hang ends after the job to stop session-c1.scope times out: Jun 04 17:35:32 m51ac-x systemd[1]: session-c1.scope stopping timed out. Killing. Jun 04 17:35:32 m51ac-x systemd[1]: session-c1.scope changed stop-sigterm -> stop-sigkill sigkill takes care of the process and shutdown can continue. Note: serviio-console.sh is PID1918 and gets terminated much earlier on line 23124 It might be a bug with serviio but as you mentioned, the processes can be killed before shutdown, no problem handling sigterm sent from terminal. ** Attachment added: "xubuntu-15-10.txt" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1456730/+attachment/4410156/+files/xubuntu-15-10.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1456730 Title: Hang after installing and running serviio Status in systemd package in Ubuntu: New Bug description: Ran serviio during the vivid cycle with no problem - either using systemd or upstart. Installed wily. Grabbed,extracted serviio from http://download.serviio.org/releases/serviio-1.5.2-linux.tar.gz Installed openjdk-8-jre. Set ~/serviio-1.5.2/bin/serviio.sh and ~/serviio-1.5.2/bin/serviio- console.sh to run at start. Reboot using systemd,serviio starts. Reboot hangs for 90s. Kill java tasks associated with serviio - reboot takes place in time expected. Boot with upstart - reboot takes place in time expected. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: systemd 219-9ubuntu1 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] ProcVersionSignature: Ubuntu 3.19.0-17.17-generic 3.19.6 Uname: Linux 3.19.0-17-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE Date: Tue May 19 18:19:40 2015 InstallationDate: Installed on 2015-05-12 (6 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150512) MachineType: NOVATECH LTD MBB-44608 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-17-generic root=UUID=6bcbfcc1-c493-4dbe-9421-ef270047a82a ro quiet splash SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-DS2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: 7383241-001 dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.chassis.version: V1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0: dmi.product.name: MBB-44608 dmi.product.version: V1.0 dmi.sys.vendor: NOVATECH LTD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1456730/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1459799] Re: segfaulting often
grinch, one may run the same command in a live environment via http://cdimage.ubuntu.com/daily-live/current/ . -- 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/1459799 Title: segfaulting often Status in xorg package in Ubuntu: Incomplete Bug description: I am getting segfaults, often May 27 19:17:41 casa kernel: [230291.611961] chromium-browse[25856]: segfault at 0 ip 7ff5f8c72f58 sp 7ffc6ed21ff0 error 4 in fglrx_dri.so[7ff5f76fc000+2338000] May 27 19:18:32 casa kernel: [230342.593157] chromium-browse[29174]: segfault at 0 ip 7f9e11cf4f58 sp 7ffc677e4e00 error 4 in fglrx_dri.so[7f9e1077e000+2338000] May 27 19:19:45 casa kernel: [230415.479260] chrome[22826]: segfault at 0 ip 7f5dff1e5f58 sp 7ffc3b3fd380 error 4 in fglrx_dri.so[7f5dfdc6f000+2338000] May 27 19:54:16 casa kernel: [232485.938279] chrome[29275]: segfault at 0 ip 7fc9d976bf58 sp 7fff279fafa0 error 4 in fglrx_dri.so[7fc9d81f5000+2338000] May 27 20:03:26 casa kernel: [233035.826317] chrome[30688]: segfault at 0 ip 7f7447b98f58 sp 7ffdb8ae03f0 error 4 in fglrx_dri.so[7f7446622000+2338000] May 28 11:11:44 casa kernel: [287522.202833] chrome[19799]: segfault at 0 ip 7f58472adf58 sp 7ffc9db94490 error 4 in fglrx_dri.so[7f5845d37000+2338000] happens when browsing the internet, nothing crazy going on that would be "pushing" the drivers performance I can't tell you the last time it worked, because I kept getting segfaults on older card, thought it was the card. bought new card and did fresh install, same issue(yes if X were working I could have saved a video card purchase) no way to take a screenshot, and even if I did, it would just be a black screen, because thats what happens. segfault > black screen > no terminals at all no ctrl+alt+F2 terminals access, etc I have to magic sysreq the system down with REISUB and that causes data loss please fix this ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 Date: Thu May 28 15:18:39 2015 InstallationDate: Installed on 2015-05-13 (15 days ago) InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1459799/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1369673] Re: LibreOffice kde file dialog integration broken (not working) in 14.04
*** This bug is a duplicate of bug 1359486 *** https://bugs.launchpad.net/bugs/1359486 ** This bug has been marked a duplicate of bug 1359486 "Use LibreOffice Dialogs" setting is ignored in KDE -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/1369673 Title: LibreOffice kde file dialog integration broken (not working) in 14.04 Status in libreoffice package in Ubuntu: Confirmed Status in qt4-x11 package in Ubuntu: Confirmed Bug description: Screenshot: http://www.dodaj.rs/f/22/pb/1Vu8cW0n/snapshot58.png ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libreoffice-kde (not installed) Uname: Linux 3.16.2-031602-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CurrentDesktop: KDE Date: Mon Sep 15 19:17:48 2014 InstallationDate: Installed on 2014-02-02 (224 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140202) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1369673/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1359486] Re: "Use LibreOffice Dialogs" setting is ignored in KDE
** Description changed: Kubuntu 14.04 (KDE Desktop Environment) [update] - This is now affecting packages from main ubuntu repositories: + This is now affecting packages from main ubuntu (trusty) repositories: libreoffice Version: 4.2.8-0ubuntu2 0 qt4-x11 Version: 4:4.8.5+git192-g085f851+dfsg-2ubuntu4.1 [/update] LibreOffice uses it's native filepicker/save dialogs, regardless of whether the config option "Use LibreOffice Dialogs" is ticked or not. Related Bugs: https://bugreports.qt-project.org/browse/QTBUG-38585 https://bugreports.qt-project.org/browse/QTBUG-34614 According to the LO team, both these bugs have patches that address the automatic disabling of Qt dialogs at runtime (if buggy Qt is detected.) Initial report/discussion on LO bugtracker (now closed) here: https://bugs.freedesktop.org/show_bug.cgi?id=82598 [obsolete] Packages from this ppa: https://launchpad.net/~libreoffice Version: 4.3.0-3ubuntu2~trusty1 (as reported by dpkg, note updated packages as of about 1 hour ago) or 4.3.0.4 Build ID: 430m0(Build:4) as reported by LibreOffice about dialog. This is a regression from 4.2.4-0ubuntu2 currently in the main ubuntu security repository. [/obsolete] -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/1359486 Title: "Use LibreOffice Dialogs" setting is ignored in KDE Status in LibreOffice Productivity Suite: Won't Fix Status in libreoffice package in Ubuntu: Confirmed Status in qt4-x11 package in Ubuntu: Confirmed Bug description: Kubuntu 14.04 (KDE Desktop Environment) [update] This is now affecting packages from main ubuntu (trusty) repositories: libreoffice Version: 4.2.8-0ubuntu2 0 qt4-x11 Version: 4:4.8.5+git192-g085f851+dfsg-2ubuntu4.1 [/update] LibreOffice uses it's native filepicker/save dialogs, regardless of whether the config option "Use LibreOffice Dialogs" is ticked or not. Related Bugs: https://bugreports.qt-project.org/browse/QTBUG-38585 https://bugreports.qt-project.org/browse/QTBUG-34614 According to the LO team, both these bugs have patches that address the automatic disabling of Qt dialogs at runtime (if buggy Qt is detected.) Initial report/discussion on LO bugtracker (now closed) here: https://bugs.freedesktop.org/show_bug.cgi?id=82598 [obsolete] Packages from this ppa: https://launchpad.net/~libreoffice Version: 4.3.0-3ubuntu2~trusty1 (as reported by dpkg, note updated packages as of about 1 hour ago) or 4.3.0.4 Build ID: 430m0(Build:4) as reported by LibreOffice about dialog. This is a regression from 4.2.4-0ubuntu2 currently in the main ubuntu security repository. [/obsolete] To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1359486/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1359486] Re: "Use LibreOffice Dialogs" setting is ignored in KDE
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libreoffice (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/1359486 Title: "Use LibreOffice Dialogs" setting is ignored in KDE Status in LibreOffice Productivity Suite: Won't Fix Status in libreoffice package in Ubuntu: Confirmed Status in qt4-x11 package in Ubuntu: Confirmed Bug description: Kubuntu 14.04 (KDE Desktop Environment) [update] This is now affecting packages from main ubuntu (trusty) repositories: libreoffice Version: 4.2.8-0ubuntu2 0 qt4-x11 Version: 4:4.8.5+git192-g085f851+dfsg-2ubuntu4.1 [/update] LibreOffice uses it's native filepicker/save dialogs, regardless of whether the config option "Use LibreOffice Dialogs" is ticked or not. Related Bugs: https://bugreports.qt-project.org/browse/QTBUG-38585 https://bugreports.qt-project.org/browse/QTBUG-34614 According to the LO team, both these bugs have patches that address the automatic disabling of Qt dialogs at runtime (if buggy Qt is detected.) Initial report/discussion on LO bugtracker (now closed) here: https://bugs.freedesktop.org/show_bug.cgi?id=82598 [obsolete] Packages from this ppa: https://launchpad.net/~libreoffice Version: 4.3.0-3ubuntu2~trusty1 (as reported by dpkg, note updated packages as of about 1 hour ago) or 4.3.0.4 Build ID: 430m0(Build:4) as reported by LibreOffice about dialog. This is a regression from 4.2.4-0ubuntu2 currently in the main ubuntu security repository. [/obsolete] To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1359486/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1359486] Re: "Use LibreOffice Dialogs" setting is ignored in KDE
This is now affecting packages from main ubuntu repositories: libreoffice Version: 4.2.8-0ubuntu2 0 qt4-x11 Version: 4:4.8.5+git192-g085f851+dfsg-2ubuntu4.1 I'll be updating my ppa shortly ** Summary changed: - [PPA] "Use LibreOffice Dialogs" setting is ignored in KDE + "Use LibreOffice Dialogs" setting is ignored in KDE ** Description changed: Kubuntu 14.04 (KDE Desktop Environment) - Packages from this ppa: - https://launchpad.net/~libreoffice - - Version: 4.3.0-3ubuntu2~trusty1 (as reported by dpkg, note updated packages as of about 1 hour ago) - or 4.3.0.4 Build ID: 430m0(Build:4) as reported by LibreOffice about dialog. + [update] + This is now affecting packages from main ubuntu repositories: + Version: 4.2.8-0ubuntu2 0 + [/update] LibreOffice uses it's native filepicker/save dialogs, regardless of whether the config option "Use LibreOffice Dialogs" is ticked or not. - - This is a regression from 4.2.4-0ubuntu2 currently in the main ubuntu - security repository. Related Bugs: https://bugreports.qt-project.org/browse/QTBUG-38585 https://bugreports.qt-project.org/browse/QTBUG-34614 According to the LO team, both these bugs have patches that address the automatic disabling of Qt dialogs at runtime (if buggy Qt is detected.) + Initial report/discussion on LO bugtracker (now closed) here: + https://bugs.freedesktop.org/show_bug.cgi?id=82598 - Initial report/discussion on LO bugtracker (now closed) here: https://bugs.freedesktop.org/show_bug.cgi?id=82598 + [obsolete] + Packages from this ppa: + https://launchpad.net/~libreoffice + + Version: 4.3.0-3ubuntu2~trusty1 (as reported by dpkg, note updated packages as of about 1 hour ago) + or 4.3.0.4 Build ID: 430m0(Build:4) as reported by LibreOffice about dialog. + + This is a regression from 4.2.4-0ubuntu2 currently in the main ubuntu security repository. + [/obsolete] ** Description changed: Kubuntu 14.04 (KDE Desktop Environment) [update] This is now affecting packages from main ubuntu repositories: - Version: 4.2.8-0ubuntu2 0 + libreoffice Version: 4.2.8-0ubuntu2 0 + qt4-x11 Version: 4:4.8.5+git192-g085f851+dfsg-2ubuntu4.1 [/update] LibreOffice uses it's native filepicker/save dialogs, regardless of whether the config option "Use LibreOffice Dialogs" is ticked or not. Related Bugs: https://bugreports.qt-project.org/browse/QTBUG-38585 https://bugreports.qt-project.org/browse/QTBUG-34614 According to the LO team, both these bugs have patches that address the automatic disabling of Qt dialogs at runtime (if buggy Qt is detected.) Initial report/discussion on LO bugtracker (now closed) here: https://bugs.freedesktop.org/show_bug.cgi?id=82598 [obsolete] Packages from this ppa: https://launchpad.net/~libreoffice Version: 4.3.0-3ubuntu2~trusty1 (as reported by dpkg, note updated packages as of about 1 hour ago) or 4.3.0.4 Build ID: 430m0(Build:4) as reported by LibreOffice about dialog. This is a regression from 4.2.4-0ubuntu2 currently in the main ubuntu security repository. [/obsolete] ** Changed in: libreoffice (Ubuntu) Status: Fix Released => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/1359486 Title: "Use LibreOffice Dialogs" setting is ignored in KDE Status in LibreOffice Productivity Suite: Won't Fix Status in libreoffice package in Ubuntu: Confirmed Status in qt4-x11 package in Ubuntu: Confirmed Bug description: Kubuntu 14.04 (KDE Desktop Environment) [update] This is now affecting packages from main ubuntu (trusty) repositories: libreoffice Version: 4.2.8-0ubuntu2 0 qt4-x11 Version: 4:4.8.5+git192-g085f851+dfsg-2ubuntu4.1 [/update] LibreOffice uses it's native filepicker/save dialogs, regardless of whether the config option "Use LibreOffice Dialogs" is ticked or not. Related Bugs: https://bugreports.qt-project.org/browse/QTBUG-38585 https://bugreports.qt-project.org/browse/QTBUG-34614 According to the LO team, both these bugs have patches that address the automatic disabling of Qt dialogs at runtime (if buggy Qt is detected.) Initial report/discussion on LO bugtracker (now closed) here: https://bugs.freedesktop.org/show_bug.cgi?id=82598 [obsolete] Packages from this ppa: https://launchpad.net/~libreoffice Version: 4.3.0-3ubuntu2~trusty1 (as reported by dpkg, note updated packages as of about 1 hour ago) or 4.3.0.4 Build ID: 430m0(Build:4) as reported by LibreOffice about dialog. This is a regression from 4.2.4-0ubuntu2 currently in the main ubuntu security repository. [/obsolete] To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1359486/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch
[Touch-packages] [Bug 1460304] Re: kernel call traces, hard locks ups, nvidia
Galen Thurber, just to advise, you don't have to apport-collect further unless specifically requested to do so. Despite this, the latest mainline kernel is 4.1-rc6 (not 4.1-rc2). ** Attachment removed: "xserver.outputs.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1460304/+attachment/4409408/+files/xserver.outputs.txt ** Attachment removed: "xdpyinfo.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1460304/+attachment/4409406/+files/xdpyinfo.txt ** Attachment removed: "Xrandr.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1460304/+attachment/4409405/+files/Xrandr.txt ** Attachment removed: "XorgLogOld.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1460304/+attachment/4409404/+files/XorgLogOld.txt ** Attachment removed: "XorgLog.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1460304/+attachment/4409403/+files/XorgLog.txt ** Attachment removed: "UdevLog.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1460304/+attachment/4409402/+files/UdevLog.txt ** Attachment removed: "UdevDb.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1460304/+attachment/4409401/+files/UdevDb.txt ** Attachment removed: "ProcModules.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1460304/+attachment/4409400/+files/ProcModules.txt ** Attachment removed: "ProcInterrupts.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1460304/+attachment/4409399/+files/ProcInterrupts.txt ** Attachment removed: "ProcEnviron.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1460304/+attachment/4409398/+files/ProcEnviron.txt ** Attachment removed: "ProcCpuinfo.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1460304/+attachment/4409396/+files/ProcCpuinfo.txt ** Attachment removed: "Lsusb.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1460304/+attachment/4409395/+files/Lsusb.txt ** Attachment removed: "Lspci.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1460304/+attachment/4409394/+files/Lspci.txt ** Attachment removed: "DpkgLog.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1460304/+attachment/4409393/+files/DpkgLog.txt ** Attachment removed: "Dependencies.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1460304/+attachment/4409392/+files/Dependencies.txt ** Attachment removed: "CurrentDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1460304/+attachment/4409391/+files/CurrentDmesg.txt ** Attachment removed: "BootLog.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1460304/+attachment/4409390/+files/BootLog.txt ** Attachment removed: "BootDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1460304/+attachment/4409389/+files/BootDmesg.txt ** Attachment removed: "xserver.outputs.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1460304/+attachment/4409388/+files/xserver.outputs.txt ** Attachment removed: "xdpyinfo.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1460304/+attachment/4409387/+files/xdpyinfo.txt ** Attachment removed: "Xrandr.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1460304/+attachment/4409386/+files/Xrandr.txt ** Attachment removed: "XorgLogOld.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1460304/+attachment/4409385/+files/XorgLogOld.txt ** Attachment removed: "XorgLog.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1460304/+attachment/4409384/+files/XorgLog.txt ** Attachment removed: "UdevLog.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1460304/+attachment/4409383/+files/UdevLog.txt ** Attachment removed: "UdevDb.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1460304/+attachment/4409382/+files/UdevDb.txt ** Attachment removed: "ProcModules.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1460304/+attachment/4409381/+files/ProcModules.txt ** Attachment removed: "ProcInterrupts.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1460304/+attachment/4409380/+files/ProcInterrupts.txt ** Attachment removed: "ProcCpuinfo.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1460304/+attachment/4409379/+files/ProcCpuinfo.txt ** Attachment removed: "PlymouthDebug.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1460304/+attachment/4409378/+files/PlymouthDebug.txt ** Attachment removed: "Lsusb.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1460304/+attachment/4409377/+files/Lsusb.txt ** Attachment removed: "Lspci.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1460304/+attachment/4409376/+files/Lspci.txt ** Attachment removed: "LightdmLog.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1460304/+attachment/4409375/+files/LightdmLog.txt ** Attachment removed: "LightdmDisplayLog.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1460304/+attachment/4409374/+files/LightdmDisplayLog.txt ** Attachme
[Touch-packages] [Bug 1369673] Re: LibreOffice kde file dialog integration broken (not working) in 14.04
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: qt4-x11 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/1369673 Title: LibreOffice kde file dialog integration broken (not working) in 14.04 Status in libreoffice package in Ubuntu: Confirmed Status in qt4-x11 package in Ubuntu: Confirmed Bug description: Screenshot: http://www.dodaj.rs/f/22/pb/1Vu8cW0n/snapshot58.png ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libreoffice-kde (not installed) Uname: Linux 3.16.2-031602-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CurrentDesktop: KDE Date: Mon Sep 15 19:17:48 2014 InstallationDate: Installed on 2014-02-02 (224 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140202) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1369673/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1369673] Re: LibreOffice kde file dialog integration broken (not working) in 14.04
I reported this against the Libreoffice PPA packages, but it's now affecting the main packages in ubuntu: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1359486 I'm currently in the process of preparing some workaround packages for the ppa listed in that thread. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/1369673 Title: LibreOffice kde file dialog integration broken (not working) in 14.04 Status in libreoffice package in Ubuntu: Confirmed Status in qt4-x11 package in Ubuntu: Confirmed Bug description: Screenshot: http://www.dodaj.rs/f/22/pb/1Vu8cW0n/snapshot58.png ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libreoffice-kde (not installed) Uname: Linux 3.16.2-031602-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CurrentDesktop: KDE Date: Mon Sep 15 19:17:48 2014 InstallationDate: Installed on 2014-02-02 (224 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140202) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1369673/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1333140] Re: Fix udev rules to consider mmc rpmb partitions
I have done repeated installs of 14.04 LTS and 15.04 on an HP Stream 11
notebooks.
This issue generally does NOT occur, other than briefly during initial
load of Ubuntu installer (and sometimes during early stages of install).
This adds no more than 15% to the time it takes to install Ubuntu (with
eMMC storage), and will usually take less than 30 minutes.
However, I realised recently that this was ONLY true for new machines,
or those I had already installed Ubuntu on. Out of the box, I was
interrupting initial startup (at screen backlight on) to go directly to
(BIOS controls for) booting from USB device.
For machines that had were already running Windows 8.1 (or even just
asking for region / user details), it will no longer cleanly install
Ubuntu. I have had it take from 2 hours to 5-7 hours, or just stall
(after about 40 minutes) with continuous errors. This appears to be
spurious interrupts (which cause further errors) due to attempts to
access the RPMB partition. I am NOT even convinced that the Ubuntu
installer is causing these interrupts.
The other possible 'root cause' is that the problem machines (NEW or
used) were older, the same model Notebook but with an earlier generation
/ step release of eMMC chips. I don't have a large enough pool to prove
this, but someone may be able to shed light.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1333140
Title:
Fix udev rules to consider mmc rpmb partitions
Status in systemd package in Ubuntu:
Fix Released
Status in udev package in Ubuntu:
Invalid
Status in udisks package in Ubuntu:
Triaged
Status in udev source package in Precise:
Triaged
Status in udisks source package in Precise:
Confirmed
Status in systemd source package in Trusty:
Fix Released
Status in udisks source package in Trusty:
Confirmed
Bug description:
As per JEDEC 4.5 spec for eMMC devices,
There is a new partitions as part of eMMC storage devices it self. (Further
details please refer eMMC spec)
*In Linux Kernel@ 3.10.33, mmc driver has created a new partitions
with "mmcblkXrpmb" if device expresses it support of RPMB.
Issues observed:
issue 1:
RPMB (Replay Protected Memory Block), A signed access to a Replay Protected
Memory Block is provided. This function provides means for the system to store
data to the specific memory area in an authenticated and replay protected
manner.
In that case, any read/write access to this partition device will report
errors.
issue 2:
The by-path, line is wrongly mapping to platform-sdhci-tegra.1 ->
mmcblk2rpmb were as
it should be platform-sdhci-tegra.1 -> mmcblk2
ls -l /dev/disk/by-path/
total 0
lrwxrwxrwx 1 root root 17 Jan 3 2000 platform-sdhci-tegra.1 ->
../../mmcblk2rpmb
lrwxrwxrwx 1 root root 15 Jan 3 2000 platform-sdhci-tegra.1-part1 ->
../../mmcblk2p1
lrwxrwxrwx 1 root root 13 Jan 3 2000 platform-sdhci-tegra.2 -> ../../mmcblk1
lrwxrwxrwx 1 root root 15 Jan 3 2000 platform-sdhci-tegra.2-part1 ->
../../mmcblk1p1
lrwxrwxrwx 1 root root 17 Jan 3 2000 platform-sdhci-tegra.3 ->
../../mmcblk0rpmb
lrwxrwxrwx 1 root root 15 Jan 3 2000 platform-sdhci-tegra.3-part1 ->
../../mmcblk0p1
lrwxrwxrwx 1 root root 15 Jan 3 2000 platform-sdhci-tegra.3-part2 ->
../../mmcblk0p2
We have locally resolved in our platform in this file 60-persistent-
storage.rules
For issue 1: (with this rule)
# skip block read for partitions of type rpmb
KERNEL=="mmcblk[0-9]rpmb", SUBSYSTEM=="block", GOTO="persistent_storage_end"
For issue 2:
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="?*", KERNEL=="mmcblk[0-9]rpmb",
SYMLINK+="disk/by-path/$env{ID_PATH}-rpmb"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="?*", KERNEL!="mmcblk[0-9]rpmb",
SYMLINK+="disk/by-path/$env{ID_PATH}"
Please consider this issues fix in next udev release .
SRU INFO: This is mostly an issue with running backported kernels on 12.04
and 14.04. There is no test case which would reproduce this on arbitrary
hardware, but there are several reporters which are in a position to verify a
proposed update.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1333140/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1333140] Re: Fix udev rules to consider mmc rpmb partitions
ChromeOS fix/workaround: https://chromium-
review.googlesource.com/#/q/Ibb21a90a754261f0bb5b0f03b868ad8d8dbc6530
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1333140
Title:
Fix udev rules to consider mmc rpmb partitions
Status in systemd package in Ubuntu:
Fix Released
Status in udev package in Ubuntu:
Invalid
Status in udisks package in Ubuntu:
Triaged
Status in udev source package in Precise:
Triaged
Status in udisks source package in Precise:
Confirmed
Status in systemd source package in Trusty:
Fix Released
Status in udisks source package in Trusty:
Confirmed
Bug description:
As per JEDEC 4.5 spec for eMMC devices,
There is a new partitions as part of eMMC storage devices it self. (Further
details please refer eMMC spec)
*In Linux Kernel@ 3.10.33, mmc driver has created a new partitions
with "mmcblkXrpmb" if device expresses it support of RPMB.
Issues observed:
issue 1:
RPMB (Replay Protected Memory Block), A signed access to a Replay Protected
Memory Block is provided. This function provides means for the system to store
data to the specific memory area in an authenticated and replay protected
manner.
In that case, any read/write access to this partition device will report
errors.
issue 2:
The by-path, line is wrongly mapping to platform-sdhci-tegra.1 ->
mmcblk2rpmb were as
it should be platform-sdhci-tegra.1 -> mmcblk2
ls -l /dev/disk/by-path/
total 0
lrwxrwxrwx 1 root root 17 Jan 3 2000 platform-sdhci-tegra.1 ->
../../mmcblk2rpmb
lrwxrwxrwx 1 root root 15 Jan 3 2000 platform-sdhci-tegra.1-part1 ->
../../mmcblk2p1
lrwxrwxrwx 1 root root 13 Jan 3 2000 platform-sdhci-tegra.2 -> ../../mmcblk1
lrwxrwxrwx 1 root root 15 Jan 3 2000 platform-sdhci-tegra.2-part1 ->
../../mmcblk1p1
lrwxrwxrwx 1 root root 17 Jan 3 2000 platform-sdhci-tegra.3 ->
../../mmcblk0rpmb
lrwxrwxrwx 1 root root 15 Jan 3 2000 platform-sdhci-tegra.3-part1 ->
../../mmcblk0p1
lrwxrwxrwx 1 root root 15 Jan 3 2000 platform-sdhci-tegra.3-part2 ->
../../mmcblk0p2
We have locally resolved in our platform in this file 60-persistent-
storage.rules
For issue 1: (with this rule)
# skip block read for partitions of type rpmb
KERNEL=="mmcblk[0-9]rpmb", SUBSYSTEM=="block", GOTO="persistent_storage_end"
For issue 2:
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="?*", KERNEL=="mmcblk[0-9]rpmb",
SYMLINK+="disk/by-path/$env{ID_PATH}-rpmb"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="?*", KERNEL!="mmcblk[0-9]rpmb",
SYMLINK+="disk/by-path/$env{ID_PATH}"
Please consider this issues fix in next udev release .
SRU INFO: This is mostly an issue with running backported kernels on 12.04
and 14.04. There is no test case which would reproduce this on arbitrary
hardware, but there are several reporters which are in a position to verify a
proposed update.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1333140/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1460304] Re: kernel call traces, hard locks ups, nvidia
sorry, apport-collect was not giving me any feedback the report was sent, so i did it several times. I will be replacing hardware in order to debug. -- 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/1460304 Title: kernel call traces, hard locks ups, nvidia Status in xorg package in Ubuntu: Incomplete Bug description: Xorg is locking up not allowing keyboard input, mouse is active but unable to activate any command or menu. full disk checks fsck -c /dev/sdaX are done often, memory tests ok unsure if fault is in xorg or kernel ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.16.0-37.51~14.04.1-generic 3.16.7-ckt9 Uname: Linux 3.16.0-37-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.125 Mon Dec 1 19:58:28 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat May 30 11:39:35 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.125, 3.16.0-37-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G71 [GeForce 7900 GS] [10de:0292] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation Device [10de:0370] InstallationDate: Installed on 2015-05-10 (20 days ago) InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) LightdmGreeterLog: ** (lightdm-gtk-greeter:1277): WARNING **: Failed to load user image: Failed to open file '/home/west/.face': Permission denied init: indicator-power main process (1323) killed by TERM signal init: indicator-application main process (1333) killed by TERM signal LightdmGreeterLogOld: ** (lightdm-gtk-greeter:1277): WARNING **: Failed to load user image: Failed to open file '/home/west/.face': Permission denied init: indicator-power main process (1321) killed by TERM signal init: indicator-application main process (1333) killed by TERM signal MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_CA:en TERM=xterm PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-37-generic root=UUID=b2e6ef75-e76d-436c-a4b0-2a40e37828a6 ro verbose SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2006 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080012 dmi.board.name: A8V-VM dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080012:bd06/19/2006:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnA8V-VM:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 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.nvidia-graphics-drivers: nvidia-graphics-drivers 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: Sat May 30 10:22:50 2015 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputSleep Button KEYBOARD, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 inputImPS/2 Logitech Wheel Mouse MOUSE, id 10 xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.16.0-1ubuntu1.2~trusty2 --- ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: tru
[Touch-packages] [Bug 1445892] Re: There is no wifi after hybernate mode
The bug still exists -- 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/1445892 Title: There is no wifi after hybernate mode Status in NetworkManager: New Status in network-manager package in Ubuntu: Confirmed Bug description: You close notebooke, then you open it- and there is no wifi. You have to restart network-manager for obtaining wi-fi again ! If you choose upstart-boot option there is no problem with wifi after hybernation. Bug occures unly with systemd-boot ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu15 ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3 Uname: Linux 3.19.0-14-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Apr 19 13:09:18 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-10-18 (547 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) IpRoute: default via 10.0.1.1 dev wlan0 proto static metric 1024 10.0.1.0/24 dev wlan0 proto kernel scope link src 10.0.1.18 169.254.0.0/16 dev wlan0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH k3b 66a32a2c-3eac-46e3-a111-0c63e94bd135 802-11-wireless 1429438056 Вс. 19 апр. 2015 13:07:36 yes no /org/freedesktop/NetworkManager/Settings/0 yes wlan0 activated /org/freedesktop/NetworkManager/ActiveConnection/4 nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlan0 wifi connected /org/freedesktop/NetworkManager/Devices/1 k3b 66a32a2c-3eac-46e3-a111-0c63e94bd135 /org/freedesktop/NetworkManager/ActiveConnection/4 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1445892/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1439649] Re: Pacemaker unable to communicate with corosync on restart under lxc
I can reproduce with corosync 2.3.3. Using corosync 2.3.4 from ppa:mariosplivalo/corosync on trusty I've not been able to reproduce on 2 tries. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1439649 Title: Pacemaker unable to communicate with corosync on restart under lxc Status in lxc package in Ubuntu: Confirmed Status in pacemaker package in Ubuntu: Confirmed Bug description: We've seen this a few times with three node clusters, all running in LXC containers; pacemaker fails to restart correctly as it can't communicate with corosync, resulting in a down cluster. Rebooting the containers resolves the issue, so suspect some sort of bad state either in corosync or pacemaker. Apr 2 11:41:32 juju-machine-4-lxc-4 pacemakerd[1033741]: notice: mcp_read_config: Configured corosync to accept connections from group 115: Library error (2) Apr 2 11:41:32 juju-machine-4-lxc-4 pacemakerd[1033741]: notice: main: Starting Pacemaker 1.1.10 (Build: 42f2063): generated-manpages agent-manpages ncurses libqb-logging libqb-ipc lha-fencing upstart nagios heartbeat corosync-native snmp libesmtp Apr 2 11:41:32 juju-machine-4-lxc-4 pacemakerd[1033741]: notice: cluster_connect_quorum: Quorum acquired Apr 2 11:41:32 juju-machine-4-lxc-4 pacemakerd[1033741]: notice: corosync_node_name: Unable to get node name for nodeid 1000 Apr 2 11:41:32 juju-machine-4-lxc-4 pacemakerd[1033741]: notice: corosync_node_name: Unable to get node name for nodeid 1001 Apr 2 11:41:32 juju-machine-4-lxc-4 pacemakerd[1033741]: notice: corosync_node_name: Unable to get node name for nodeid 1003 Apr 2 11:41:32 juju-machine-4-lxc-4 pacemakerd[1033741]: notice: corosync_node_name: Unable to get node name for nodeid 1001 Apr 2 11:41:32 juju-machine-4-lxc-4 pacemakerd[1033741]: notice: get_node_name: Defaulting to uname -n for the local corosync node name Apr 2 11:41:32 juju-machine-4-lxc-4 pacemakerd[1033741]: notice: crm_update_peer_state: pcmk_quorum_notification: Node juju-machine-4-lxc-4[1001] - state is now member (was (null)) Apr 2 11:41:32 juju-machine-4-lxc-4 pacemakerd[1033741]: notice: corosync_node_name: Unable to get node name for nodeid 1003 Apr 2 11:41:32 juju-machine-4-lxc-4 pacemakerd[1033741]: notice: crm_update_peer_state: pcmk_quorum_notification: Node (null)[1003] - state is now member (was (null)) Apr 2 11:41:32 juju-machine-4-lxc-4 crmd[1033748]: notice: main: CRM Git Version: 42f2063 Apr 2 11:41:32 juju-machine-4-lxc-4 stonith-ng[1033744]: notice: crm_cluster_connect: Connecting to cluster infrastructure: corosync Apr 2 11:41:32 juju-machine-4-lxc-4 stonith-ng[1033744]: notice: corosync_node_name: Unable to get node name for nodeid 1001 Apr 2 11:41:32 juju-machine-4-lxc-4 stonith-ng[1033744]: notice: get_node_name: Defaulting to uname -n for the local corosync node name Apr 2 11:41:32 juju-machine-4-lxc-4 attrd[1033746]: notice: crm_cluster_connect: Connecting to cluster infrastructure: corosync Apr 2 11:41:32 juju-machine-4-lxc-4 corosync[1033732]: [MAIN ] Denied connection attempt from 109:115 Apr 2 11:41:32 juju-machine-4-lxc-4 corosync[1033732]: [QB] Invalid IPC credentials (1033732-1033746). Apr 2 11:41:32 juju-machine-4-lxc-4 attrd[1033746]:error: cluster_connect_cpg: Could not connect to the Cluster Process Group API: 11 Apr 2 11:41:32 juju-machine-4-lxc-4 attrd[1033746]:error: main: HA Signon failed Apr 2 11:41:32 juju-machine-4-lxc-4 attrd[1033746]:error: main: Aborting startup Apr 2 11:41:32 juju-machine-4-lxc-4 pacemakerd[1033741]:error: pcmk_child_exit: Child process attrd (1033746) exited: Network is down (100) Apr 2 11:41:32 juju-machine-4-lxc-4 pacemakerd[1033741]: warning: pcmk_child_exit: Pacemaker child process attrd no longer wishes to be respawned. Shutting ourselves down. Apr 2 11:41:32 juju-machine-4-lxc-4 pacemakerd[1033741]: notice: pcmk_shutdown_worker: Shuting down Pacemaker Apr 2 11:41:32 juju-machine-4-lxc-4 pacemakerd[1033741]: notice: stop_child: Stopping crmd: Sent -15 to process 1033748 Apr 2 11:41:32 juju-machine-4-lxc-4 crmd[1033748]: warning: do_cib_control: Couldn't complete CIB registration 1 times... pause and retry Apr 2 11:41:32 juju-machine-4-lxc-4 crmd[1033748]: notice: crm_shutdown: Requesting shutdown, upper limit is 120ms Apr 2 11:41:32 juju-machine-4-lxc-4 crmd[1033748]: warning: do_log: FSA: Input I_SHUTDOWN from crm_shutdown() received in state S_STARTING Apr 2 11:41:32 juju-machine-4-lxc-4 crmd[1033748]: notice: do_state_transition: State transition S_STARTING -> S_STOPPING [ input=I_SHUTDOWN cause=C_SHUTDOWN origin=crm_shutdown ] Apr 2 11:41:32 juju-machine-4-lxc-4 cib[1033743]: notice: crm_cluster_connect: Connecting to cluster infrastructure: corosyn
[Touch-packages] [Bug 1462145] [NEW] race condition during layout change
Public bug reported: Hello there! I have dual layout setup (English and Russian) at my Ubuntu 14.04 amd64 desktop. Seems there is a race condition during layout change. Example: I'm logged in. Current layout is English. Here is focus at any program (browser, terminal or whatever). Let's program would be terminal with running irc client. Then I'm answer some questing in chat i'm changing layout from english to russian via pressing alt-shift and then typing word in russian. But here is but! layout changing not always done after alt-shift for some (race condition of any kind?) reason. So part of sentence is in latin chars and some other part (as should be) in cyrillics. The only way to workaround this is to wait a 1-2 seconds after alt-shift. But this way is too much annoying and lame. Please, fix the error or give me some workaround. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Это каталог: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.113 Mon Dec 1 21:08:13 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.11 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: Fri Jun 5 05:09:23 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GF114 [GeForce GTX 560] [10de:1201] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:3527] InstallationDate: Installed on 2014-09-01 (276 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-53-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/11/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.30 dmi.board.name: H77M dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.30:bd09/11/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH77M:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.4 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Fri Jun 5 04:01:50 2015 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputMicrosoft Microsoft 3-Button Mouse with IntelliEye(TM) MOUSE, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.15.1-0ubuntu2.7 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 third-party-packages trusty ubuntu ** Description changed: Hello there! I have dual layout setup (English and Russian) at my Ubuntu 14.04 amd64 desktop. Seems there is a race condition during layout change. Example: I'm logged in. Current layout is English. Here is focus at any program (browse
[Touch-packages] [Bug 1462147] [NEW] Random text characters partially or completely missing
Public bug reported: Ubuntu-Mate 15.10 development version updated as of 4-Jun 2300 UTC . Video driver is nouveau Problem began upon upgrading of xserver-xorg-core_1.17.1-0ubuntu3_amd64 and xserver-xorg-common_1.17.1-0ubuntu3_amd64xorg to xserver-xorg-core_1.17.1-0ubuntu4_amd64 and xserver-xorg-common_1.17.1-0ubuntu4_amd64xorg and was resolved by reverting to the pre-upgrade packages. Apparently random text characters, or parts thereof, would be missing in various applications including the Lightdm greeter, Firefox, Pidgin, Mate-terminal, the Mate panel clock, Unetbootin, and the Mate menu. This occurs both at my monitor's native resolution (1680x1050) and at 1600x1200. Other possibly useful info: libdrm-nouveau2:amd64 2.4.60-3amd64 xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1amd64 ~$ sudo inxi -F System:Host: Pyrope Kernel: 3.19.0-20-generic x86_64 (64 bit) Desktop: MATE 1.8.2 Distro: Ubuntu 15.10 wily Machine: System: HP-Pavilion product: FQ578AAR-ABA s3707c serial: MXW9050KY9 Mobo: PEGATRON model: NutMeg v: 1.02 serial: MS1C91R52904711 Bios: American Megatrends v: 5.12 date: 02/17/2009 CPU: Dual core AMD Athlon 64 X2 5400+ (-MCP-) cache: 1024 KB clock speeds: max: 2800 MHz 1: 1000 MHz 2: 1000 MHz Graphics: Card: NVIDIA C78 [GeForce 9100] Display Server: X.org 1.17.1 driver: nouveau tty size: 234x65 Advanced Data: N/A for root Audio: Card NVIDIA MCP72XE/MCP72P/MCP78U/MCP78S High Definition Audio driver: snd_hda_intel Sound: Advanced Linux Sound Architecture v: k3.19.0-20-generic Network: Card-1: NVIDIA MCP77 Ethernet driver: forcedeth IF: eth0 state: down mac: 00:24:8c:13:79:5b Card-2: NetGear WNA1100 Wireless-N 150 [Atheros AR9271] driver: ath9k_htc IF: wlan0 state: N/A mac: N/A Drives:HDD Total Size: 500.1GB (41.7% used) ID-1: /dev/sda model: ST3500413AS size: 500.1GB Partition: ID-1: / size: 19G used: 3.6G (21%) fs: ext4 dev: /dev/sda10 RAID: No RAID devices: /proc/mdstat, md_mod kernel module present Sensors: None detected - is lm-sensors installed and configured? Info: Processes: 180 Uptime: 1:00 Memory: 816.8/3700.3MB Client: Shell (sudo) inxi: 2.2.16 ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8 Uname: Linux 3.19.0-20-generic x86_64 ApportVersion: 2.17.3-0ubuntu3 Architecture: amd64 CurrentDesktop: MATE Date: Thu Jun 4 18:07:43 2015 InstallationDate: Installed on 2015-05-28 (7 days ago) InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Alpha amd64 (20150528) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption wily -- 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/1462147 Title: Random text characters partially or completely missing Status in xorg package in Ubuntu: New Bug description: Ubuntu-Mate 15.10 development version updated as of 4-Jun 2300 UTC . Video driver is nouveau Problem began upon upgrading of xserver-xorg-core_1.17.1-0ubuntu3_amd64 and xserver-xorg-common_1.17.1-0ubuntu3_amd64xorg to xserver-xorg-core_1.17.1-0ubuntu4_amd64 and xserver-xorg-common_1.17.1-0ubuntu4_amd64xorg and was resolved by reverting to the pre-upgrade packages. Apparently random text characters, or parts thereof, would be missing in various applications including the Lightdm greeter, Firefox, Pidgin, Mate-terminal, the Mate panel clock, Unetbootin, and the Mate menu. This occurs both at my monitor's native resolution (1680x1050) and at 1600x1200. Other possibly useful info: libdrm-nouveau2:amd64 2.4.60-3amd64 xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1amd64 ~$ sudo inxi -F System:Host: Pyrope Kernel: 3.19.0-20-generic x86_64 (64 bit) Desktop: MATE 1.8.2 Distro: Ubuntu 15.10 wily Machine: System: HP-Pavilion product: FQ578AAR-ABA s3707c serial: MXW9050KY9 Mobo: PEGATRON model: NutMeg v: 1.02 serial: MS1C91R52904711 Bios: American Megatrends v: 5.12 date: 02/17/2009 CPU: Dual core AMD Athlon 64 X2 5400+ (-MCP-) cache: 1024 KB clock speeds: max: 2800 MHz 1: 1000 MHz 2: 1000 MHz Graphics: Card: NVIDIA C78 [GeForce 9100] Display Server: X.org 1.17.1 driver: nouveau tty size: 234x65 Advanced Data: N/A for root Audio: Card NVIDIA MCP72XE/MCP72P/MCP78U/MCP78S High Definition Audio driver: snd_hda_intel Sound: Advanced Linux Sound Architecture v: k3.19.0-20-generic Network: Card-1: NVIDIA MCP77 Ethernet driver: forcedeth IF:
[Touch-packages] [Bug 1462084] Re: Folder chooser cancels directory creation on dialog confirmation
** Changed in: gtk Status: Unknown => Confirmed ** Changed in: gtk Importance: Unknown => Medium -- 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/1462084 Title: Folder chooser cancels directory creation on dialog confirmation Status in GTK+ GUI Toolkit: Confirmed Status in gtk+3.0 package in Ubuntu: New Bug description: These steps are in Nautilus, but same happens in e.g. Shotwell, so a gtk bug. Steps to reproduce: - open Nautilus/Files - right-click on an item - choose "Move To..." - click "Create Folder" - type in a folder name (don't press enter) - click "Select" Expected: - folder gets created - the created folder is used as target Current: - folder does not get created - the first folder available is used as target ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: libgtk-3-0 3.14.12-0ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jun 4 22:10:59 2015 SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1462084/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 409644] Re: Print to file folder chooser dialog creates folders with "Open" button
** Changed in: gtk Status: Unknown => Confirmed ** Changed in: gtk Importance: Unknown => Medium -- 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/409644 Title: Print to file folder chooser dialog creates folders with "Open" button Status in GTK+ GUI Toolkit: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: In at least two apps where a filename is entered along with a drop- down directory chooser with an "other" option, the dialog to choose the "other" directory will unintentionally create new directories. gnome-print (?): 1. Start Gedit (or Firefox, etc.). 2. File-->Print... 3. Select "Print to File" under the Printers column. 4. "Save in folder" drop-down --> "Other..." 5. Type "TEST" in the Location. 6. Click "Open" or press Enter. 7. BUG: A folder called "TEST" is created and the folder choosing dialog is closed, with "TEST" selected. gnome-utils (?): 1. Start Take Screenshot (Apps-->Accessories-->Take Screenshot) 2. Continue at #4, above. Since my intention is something like a "save as" operation, and the dialog looks like a save-as dialog, I often type the filename that I want to use, and press enter. But then a directory is created with the filename that I want to use. Very annoying because now I have to find that directory and delete it. To fix this, I have a couple of ideas/suggestions: * Utilize a dedicated directory chooser dialog (is there one for Gnome, as in MS Windows?), or * When a filename is entered in this "other" chooser, the filename in the original dialog (e.g. print-to-file, or Screenshot save preview) should be set to it, and the "save in folder" should also be adjusted to the folder that was open in the dialog. * Fixing the current chooser dialog so it only creates folders when "Create Folder" button is pressed, or * Separate the location+filename selection such as the "Save As..." dialog to a separate stage in the print-to-file process, or * Adjust the print-to-file dialog in some way I don't know yet. Ubuntu 9.04 Gnome 2.26.1 Gedit 2.26.1 Firefox 3.0.13 To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/409644/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1462087] Re: Folder chooser creates and opens new directory when clicked on another
** Changed in: gtk Status: Unknown => Confirmed ** Changed in: gtk Importance: Unknown => Medium -- 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/1462087 Title: Folder chooser creates and opens new directory when clicked on another Status in GTK+ GUI Toolkit: Confirmed Status in gtk+3.0 package in Ubuntu: New Bug description: Somewhat related to bug #1462084: These steps are in Nautilus, but same happens in e.g. Shotwell, so a gtk bug. Steps to reproduce: - open Nautilus/Files - right-click on an item - choose "Move To..." - click "Create Folder" - type in a folder name (don't press enter) - click on a different folder Expected: - folder creation is cancelled or - user isn't allowed to click on a different folder Current: - folder is created - the created folder is opened (not the one the user clicked on) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: libgtk-3-0 3.14.12-0ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jun 4 22:10:59 2015 SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1462087/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1361864] Re: add "Preferred" property to ConnectionContext interface
At a meeting this week, we decided that all of the components that may activate and/or use a context, should set the 'Preferred' flag for the context if it's successfully activated and/or used ( eg. a context is used by ofono for the INITIAL_ATTACH APN request; if this succeeds, ofono will set the context as 'Preferred' ). As such, I've re-opened the bug tasks for the affected packages ( network-manager, nuntium, and ofono itself ), and made sure we have Ubuntu (RTM) tasks for the same to track their release as updates. ** Also affects: network-manager (Ubuntu RTM) Importance: Undecided Status: New ** Also affects: ubuntu-system-settings (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: ubuntu-system-settings (Ubuntu RTM) Status: New => In Progress ** Changed in: ubuntu-system-settings (Ubuntu RTM) Assignee: (unassigned) => jgdx (jgdx) ** Changed in: ubuntu-system-settings (Ubuntu RTM) Assignee: jgdx (jgdx) => Jonas G. Drange (jonas-drange) ** Changed in: network-manager (Ubuntu RTM) Importance: Undecided => High ** Changed in: network-manager (Ubuntu RTM) Status: New => In Progress ** Changed in: nuntium (Ubuntu RTM) Importance: Undecided => High ** Changed in: ubuntu-system-settings (Ubuntu) Importance: Undecided => High ** Changed in: ubuntu-system-settings (Ubuntu RTM) Importance: Undecided => High -- 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/1361864 Title: add "Preferred" property to ConnectionContext interface Status in the base for Ubuntu mobile products: Confirmed Status in libqofono package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: In Progress Status in nuntium package in Ubuntu: In Progress Status in ofono package in Ubuntu: In Progress Status in ubuntu-system-settings package in Ubuntu: In Progress Status in ubuntu-system-settings source package in Vivid: New Status in network-manager package in Ubuntu RTM: In Progress Status in nuntium package in Ubuntu RTM: In Progress Status in ofono package in Ubuntu RTM: In Progress Status in ubuntu-system-settings package in Ubuntu RTM: In Progress Bug description: To implement system-settings APN editor reliably there has to be a Tag field with is an arbitrary non user-visible string that can be set for any Context. We also need org.ofono.ConnectionManager.AddContext which takes a variant map with prepopulated values for the context to be created, so we can have a function in QOfono QOfonoConnectionManager::addContextWithTag(QString tag). To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1361864/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1361864] Re: add "Preferred" property to ConnectionContext interface
** Also affects: ofono (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: ofono (Ubuntu RTM) Status: New => In Progress ** Changed in: ofono (Ubuntu RTM) Importance: Undecided => High ** Changed in: ofono (Ubuntu RTM) Assignee: (unassigned) => Alfonso Sanchez-Beato (alfonsosanchezbeato) ** Changed in: ofono (Ubuntu) Status: Fix Released => In Progress ** Changed in: nuntium (Ubuntu) Status: Fix Released => In Progress ** Also affects: nuntium (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: nuntium (Ubuntu RTM) Assignee: (unassigned) => Alfonso Sanchez-Beato (alfonsosanchezbeato) ** Changed in: nuntium (Ubuntu RTM) Status: New => In Progress -- 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/1361864 Title: add "Preferred" property to ConnectionContext interface Status in the base for Ubuntu mobile products: Confirmed Status in libqofono package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: In Progress Status in nuntium package in Ubuntu: In Progress Status in ofono package in Ubuntu: In Progress Status in ubuntu-system-settings package in Ubuntu: In Progress Status in ubuntu-system-settings source package in Vivid: New Status in network-manager package in Ubuntu RTM: New Status in nuntium package in Ubuntu RTM: In Progress Status in ofono package in Ubuntu RTM: In Progress Bug description: To implement system-settings APN editor reliably there has to be a Tag field with is an arbitrary non user-visible string that can be set for any Context. We also need org.ofono.ConnectionManager.AddContext which takes a variant map with prepopulated values for the context to be created, so we can have a function in QOfono QOfonoConnectionManager::addContextWithTag(QString tag). To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1361864/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1413710] Re: Xorg crash - Fullscreen causing crash
** Changed in: xorg-server Status: Confirmed => Invalid -- 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/1413710 Title: Xorg crash - Fullscreen causing crash Status in X.Org X server: Invalid Status in xorg package in Ubuntu: Incomplete Bug description: I was listening to this YouTube video: http://www.infinitelooper.com/?v=-tJYN-eG1zk&p=n When I decided to make it full screen, but it didn't want to go, so I very quickly double-clicked on it twice, and then the entire screen went black. And no matter what I did, it go away. Although I could still hear the music from the video. As I couldn't do anything really about it I had to hold down my power button and force it to shutdown. And when it started up the screen was fine. It is a laptop so I don't think that the monitor just turned off or something. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2 Uname: Linux 3.16.0-29-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Jan 22 19:26:26 2015 DistUpgraded: 2014-12-13 16:39:34,851 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:5002] InstallationDate: Installed on 2014-12-06 (47 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: LENOVO 62742SG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-29-generic root=UUID=3883b8c8-34cb-4ec2-8834-fe85bbd10f52 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to utopic on 2014-12-13 (40 days ago) dmi.bios.date: 11/15/2012 dmi.bios.vendor: LENOVO dmi.bios.version: H5ET69WW (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 62742SG dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK IPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrH5ET69WW(1.12):bd11/15/2012:svnLENOVO:pn62742SG:pvrLenovoB590:rvnLENOVO:rn62742SG:rvrWin8ProDPKIPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 62742SG dmi.product.version: Lenovo B590 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Thu Jan 22 19:19:28 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 827 vendor LGD xserver.version: 2:1.16.0-1ubuntu1.2 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1413710/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1413710]
*** This bug has been marked as a duplicate of bug 80568 *** -- 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/1413710 Title: Xorg crash - Fullscreen causing crash Status in X.Org X server: Invalid Status in xorg package in Ubuntu: Incomplete Bug description: I was listening to this YouTube video: http://www.infinitelooper.com/?v=-tJYN-eG1zk&p=n When I decided to make it full screen, but it didn't want to go, so I very quickly double-clicked on it twice, and then the entire screen went black. And no matter what I did, it go away. Although I could still hear the music from the video. As I couldn't do anything really about it I had to hold down my power button and force it to shutdown. And when it started up the screen was fine. It is a laptop so I don't think that the monitor just turned off or something. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2 Uname: Linux 3.16.0-29-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Jan 22 19:26:26 2015 DistUpgraded: 2014-12-13 16:39:34,851 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:5002] InstallationDate: Installed on 2014-12-06 (47 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: LENOVO 62742SG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-29-generic root=UUID=3883b8c8-34cb-4ec2-8834-fe85bbd10f52 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to utopic on 2014-12-13 (40 days ago) dmi.bios.date: 11/15/2012 dmi.bios.vendor: LENOVO dmi.bios.version: H5ET69WW (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 62742SG dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK IPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrH5ET69WW(1.12):bd11/15/2012:svnLENOVO:pn62742SG:pvrLenovoB590:rvnLENOVO:rn62742SG:rvrWin8ProDPKIPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 62742SG dmi.product.version: Lenovo B590 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Thu Jan 22 19:19:28 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 827 vendor LGD xserver.version: 2:1.16.0-1ubuntu1.2 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1413710/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 583994] Re: Consider replacing ntpdate calls by 'ntpd -g'
Yes, I thought it would be more clear cause I can't change the title of this bug. Once the patch is applied and updated meta-packages pushed both bugs could be safely closed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/583994 Title: Consider replacing ntpdate calls by 'ntpd -g' Status in NTP: Invalid Status in ntp package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Triaged Status in ntp package in Debian: New Bug description: Binary package hint: ntp Given that 'ntpdate' is being obsoleted upstream [1], we should replace 'ntpdate' usage by: * ntpd -qg (if we really want to set the time and exit), or * ntpd-g (if we want to keep ntpd running) the '-q' option will set the clock once, and exit; the 'g' allows for large corrections to the clock, like what is done by 'ntpdate'. [1] http://www.eecis.udel.edu/~mills/ntp/html/ntpdate.html To manage notifications about this bug go to: https://bugs.launchpad.net/ntp/+bug/583994/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1461999] Re: Crash changing SIM slot technologies
** Also affects: canonical-devices-system-image Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1461999 Title: Crash changing SIM slot technologies Status in the base for Ubuntu mobile products: New Status in network-manager package in Ubuntu: New Bug description: Test case. - Insert two SIM's. - Reboot, and unlock both of them. - Open System Settings > Celullar. - Change one of the SIM's technologies (e.g. 2G -> 3G). Expected result. - Technology is changed. Actual result. - Crash. current build number: 24 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1461999/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1409133]
Probably a duplicate of bug 90508. Could you give the patch referenced there a try? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1409133 Title: Heavy black flickering with Intel graphics after VT switching from X to Mir Status in The Linux Kernel: Incomplete Status in Mir: Invalid Status in linux package in Ubuntu: Triaged Status in mir package in Ubuntu: Invalid Bug description: After running mir_demo_server on VT 1, when I switch to VT 7 then back to VT 1, the demo server really flickers black quite a lot (entire screen, pointer included). I'm not sure, but I also upgraded my kernel to 3.18.2-031802-generic at the same time, if it's because of that, please mark invalid. --- ApportVersion: 2.15.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: william5932 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=f950febe-baf1-425c-8ab5-f4f43a86839b Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0a5c:217f Broadcom Corp. BCM2045B (BDC-2.1) Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 3249CTO Package: mir ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.18.0-9-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash thinkpad_acpi.fan_control=Y vt.handoff=7 ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2 RelatedPackageVersions: linux-restricted-modules-3.18.0-9-generic N/A linux-backports-modules-3.18.0-9-generic N/A linux-firmware1.140 SystemImageInfo: current build number: 0 device name: channel: daily last update: Unknown Tags: vivid Uname: Linux 3.18.0-9-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm autopilot cdrom dip disk fuse kvm libvirtd lpadmin plugdev sambashare sbuild sudo video _MarkForUpload: True dmi.bios.date: 01/26/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6QET35WW (1.05 ) dmi.board.name: 3249CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6QET35WW(1.05):bd01/26/2010:svnLENOVO:pn3249CTO:pvrThinkPadX201:rvnLENOVO:rn3249CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 3249CTO dmi.product.version: ThinkPad X201 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1409133/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1461274] Re: dependency cycles
Ah, my bad - failed to make a proper unit, will dig deeper into docs. Hopefully upstream issue will get fixed so this would be easier to troubleshoot in future. ** Changed in: systemd (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1461274 Title: dependency cycles Status in systemd package in Ubuntu: Invalid Bug description: There are several dependency cycles reported during the boot of xubuntu 15.04 x86_64: see attached log. Those cycles should be resoled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1461274/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1409133] Re: Heavy black flickering with Intel graphics after VT switching from X to Mir
** Changed in: linux Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1409133 Title: Heavy black flickering with Intel graphics after VT switching from X to Mir Status in The Linux Kernel: Incomplete Status in Mir: Invalid Status in linux package in Ubuntu: Triaged Status in mir package in Ubuntu: Invalid Bug description: After running mir_demo_server on VT 1, when I switch to VT 7 then back to VT 1, the demo server really flickers black quite a lot (entire screen, pointer included). I'm not sure, but I also upgraded my kernel to 3.18.2-031802-generic at the same time, if it's because of that, please mark invalid. --- ApportVersion: 2.15.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: william5932 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=f950febe-baf1-425c-8ab5-f4f43a86839b Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0a5c:217f Broadcom Corp. BCM2045B (BDC-2.1) Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 3249CTO Package: mir ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.18.0-9-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash thinkpad_acpi.fan_control=Y vt.handoff=7 ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2 RelatedPackageVersions: linux-restricted-modules-3.18.0-9-generic N/A linux-backports-modules-3.18.0-9-generic N/A linux-firmware1.140 SystemImageInfo: current build number: 0 device name: channel: daily last update: Unknown Tags: vivid Uname: Linux 3.18.0-9-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm autopilot cdrom dip disk fuse kvm libvirtd lpadmin plugdev sambashare sbuild sudo video _MarkForUpload: True dmi.bios.date: 01/26/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6QET35WW (1.05 ) dmi.board.name: 3249CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6QET35WW(1.05):bd01/26/2010:svnLENOVO:pn3249CTO:pvrThinkPadX201:rvnLENOVO:rn3249CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 3249CTO dmi.product.version: ThinkPad X201 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1409133/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1462101] [NEW] package libc-bin 2.19-0ubuntu6.6 failed to install/upgrade: package libc-bin is already installed and configured
Public bug reported: Error occured during upgrade from Ubuntu 14.04 to 14.10 ProblemType: Package DistroRelease: Ubuntu 14.10 Package: libc-bin ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.11 AptdaemonVersion: 1.1.1-1ubuntu5.1 Architecture: i386 CrashReports: 640:0:110:21815510:2015-06-04 13:23:13.439870595 +0200:2015-06-04 13:23:14.439870595 +0200:/var/crash/_usr_bin_dpkg.0.crash 600:0:110:1238228:2015-06-04 13:23:17.319870471 +0200:2015-06-04 13:23:18.319870471 +0200:/var/crash/libc-bin.0.crash Date: Thu Jun 4 13:23:14 2015 Dependencies: gcc-4.9-base 4.9.1-16ubuntu6 libc6 2.19-10ubuntu2.3 libcap2 1:2.24-0ubuntu2 libgcc1 1:4.9.1-16ubuntu6 multiarch-support 2.19-0ubuntu6.6 DuplicateSignature: package:libc-bin:2.19-0ubuntu6.6:package libc-bin is already installed and configured ErrorMessage: package libc-bin is already installed and configured InstallationDate: Installed on 2013-04-04 (790 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) SourcePackage: eglibc Title: package libc-bin 2.19-0ubuntu6.6 failed to install/upgrade: package libc-bin is already installed and configured UpgradeStatus: Upgraded to utopic on 2015-06-04 (0 days ago) ** Affects: eglibc (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package dist-upgrade i386 need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to eglibc in Ubuntu. https://bugs.launchpad.net/bugs/1462101 Title: package libc-bin 2.19-0ubuntu6.6 failed to install/upgrade: package libc-bin is already installed and configured Status in eglibc package in Ubuntu: New Bug description: Error occured during upgrade from Ubuntu 14.04 to 14.10 ProblemType: Package DistroRelease: Ubuntu 14.10 Package: libc-bin ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.11 AptdaemonVersion: 1.1.1-1ubuntu5.1 Architecture: i386 CrashReports: 640:0:110:21815510:2015-06-04 13:23:13.439870595 +0200:2015-06-04 13:23:14.439870595 +0200:/var/crash/_usr_bin_dpkg.0.crash 600:0:110:1238228:2015-06-04 13:23:17.319870471 +0200:2015-06-04 13:23:18.319870471 +0200:/var/crash/libc-bin.0.crash Date: Thu Jun 4 13:23:14 2015 Dependencies: gcc-4.9-base 4.9.1-16ubuntu6 libc6 2.19-10ubuntu2.3 libcap2 1:2.24-0ubuntu2 libgcc1 1:4.9.1-16ubuntu6 multiarch-support 2.19-0ubuntu6.6 DuplicateSignature: package:libc-bin:2.19-0ubuntu6.6:package libc-bin is already installed and configured ErrorMessage: package libc-bin is already installed and configured InstallationDate: Installed on 2013-04-04 (790 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) SourcePackage: eglibc Title: package libc-bin 2.19-0ubuntu6.6 failed to install/upgrade: package libc-bin is already installed and configured UpgradeStatus: Upgraded to utopic on 2015-06-04 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1462101/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1461138] Re: Some click icons are appearing twice after upgrade to RC
** Changed in: canonical-devices-system-image Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-click in Ubuntu. https://bugs.launchpad.net/bugs/1461138 Title: Some click icons are appearing twice after upgrade to RC Status in the base for Ubuntu mobile products: Fix Released Status in ubuntu-app-launch package in Ubuntu: New Status in unity-scope-click package in Ubuntu: Invalid Status in ubuntu-app-launch package in Ubuntu RTM: In Progress Bug description: I upgraded from ubuntu-touch/stable/bq-aquaris.en to ubuntu-touch/rc- proposed/bq-aquaris.en After the upgrade, some of the Apps are appearing twice, see the attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1461138/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1427831] Re: Graphics Glitch after suspending and resuming, only when pressing the sleep button
I am experiencing exactly the same behaviour with Suspend from the menu and automatically suspending resuming normally. I do not have a sleep button, though running 'sudo pm-suspend' results in a glitchy launcher on resume. I first noticed the unity launcher glitching issue when I attached suspend to a hot key which runs this command: dbus-send --system --print-reply --dest="org.freedesktop.UPower" /org/freedesktop/UPower org.freedesktop.UPower.Suspend -- 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/1427831 Title: Graphics Glitch after suspending and resuming, only when pressing the sleep button Status in Unity: New Status in unity package in Ubuntu: Confirmed Bug description: Running Ubuntu 14.10 Going to the menu and clicking on the 'suspend' button, causes no problems on resume. Automatically suspending after a given time also has no problem. However if I press the sleep button, it resumes with pixels of all colours randomly populating the screen. When I move the mouse after that, my screen goes to sleep (like when the computer is turned off). After moving my mouse again, the lockscreen displays as normal. 'sudo pm-suspend' results in only the Launcer having random coloured pixels on it. The checklist testing app had the same result. Clicking on a window reprints the launcer. Attached is an example. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1427831/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1456782] Re: [Dialer and Messaging] should be able to edit a contact without switching to address book
This bug was fixed in the package messaging-app - 0.1+15.10.20150601.1-0ubuntu1 --- messaging-app (0.1+15.10.20150601.1-0ubuntu1) wily; urgency=medium [ Gustavo Pichorim Boiko ] * Fix contact share. [ Renato Araujo Oliveira Filho ] * Implement address book interaction using the address book library instead of calling the app. (LP: #1456782) * Removed contact expansion. (LP: #1368671) [ Sebastien Bacher ] * Update the translations template so new strings can be translated -- CI Train Bot Mon, 01 Jun 2015 20:15:14 + ** Changed in: messaging-app (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1456782 Title: [Dialer and Messaging] should be able to edit a contact without switching to address book Status in the base for Ubuntu mobile products: In Progress Status in Ubuntu UX bugs: Triaged Status in address-book-app package in Ubuntu: Fix Released Status in dialer-app package in Ubuntu: Fix Released Status in messaging-app package in Ubuntu: Fix Released Status in address-book-app source package in Vivid: Confirmed Status in dialer-app source package in Vivid: Confirmed Status in messaging-app source package in Vivid: Confirmed Bug description: per design, users of dialer and messaging-app should be able to open a contact directly from within those apps and edit it. Currently it launches address book app and then the user's context is switched. Desired behavior: Dialer app: - from dialer screen click the contacts icon on header - contact list should be shown in the dialer app - click on contact to open it - should be able to edit contact from that screen and interact without switching to address book app Messaging app: - create new message - click contacts icon on header - contact list should be shown in the messaaging app - can edit or interact without switching to address book app To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1456782/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368671] Re: [dialer-app]+[address-book]+[messaging] expansion should be removed from all contact list views
This bug was fixed in the package messaging-app - 0.1+15.10.20150601.1-0ubuntu1 --- messaging-app (0.1+15.10.20150601.1-0ubuntu1) wily; urgency=medium [ Gustavo Pichorim Boiko ] * Fix contact share. [ Renato Araujo Oliveira Filho ] * Implement address book interaction using the address book library instead of calling the app. (LP: #1456782) * Removed contact expansion. (LP: #1368671) [ Sebastien Bacher ] * Update the translations template so new strings can be translated -- CI Train Bot Mon, 01 Jun 2015 20:15:14 + ** Changed in: messaging-app (Ubuntu) Status: Confirmed => Fix Released -- 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/1368671 Title: [dialer-app]+[address-book]+[messaging] expansion should be removed from all contact list views Status in the base for Ubuntu mobile products: New Status in Ubuntu UX bugs: Fix Committed Status in address-book-app package in Ubuntu: Fix Released Status in dialer-app package in Ubuntu: Fix Released Status in messaging-app package in Ubuntu: Fix Released Status in address-book-app source package in Vivid: New Status in dialer-app source package in Vivid: New Status in messaging-app source package in Vivid: New Bug description: Steps to reproduce: 1. Open any of the following apps - > Address Book, Phone & Messaging app 2. Navigate to a contact list view/page 3. Tap on a contact list item 4. Current implementation: the list item expands and gives you a selection of numbers and an icon appears on the tapped list item, to access contact's profile UX comment - desired solution: Remove expansion pattern from all contact views/lists. A tap action a the contact list item should open the detail screen of the contact. ---UPDATE This is became a usability issue because people didn't understand the tap and the additional tap to view the full contact details. Comment #2 "User testing showed, that expansion is not working vey well or user can not navigate all the time to the actual contact card." To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1368671/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1460152] Re: apparmor cache not updated when apparmor.d rules change (breaks 15.04/stable -> 15.04/edge updates)
** Branch linked: lp:~mvo/snappy/snappy-lp1460152-workaround -- 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/1460152 Title: apparmor cache not updated when apparmor.d rules change (breaks 15.04/stable -> 15.04/edge updates) Status in Snappy Ubuntu: In Progress Status in Snappy 15.04 series: In Progress Status in apparmor package in Ubuntu: New Bug description: The apparmor cache gets confused easily on upgrade. Here is what happens: - boot stable, /etc/apparmor.d/cache/usr.bin.ubuntu-core-launcher is mtime of now because we generate the cache on boot - upgrade to edge, /etc/apparmor.d/usr.bin.ubuntu-core-launcher is updated and has the mtime of T (yesterday) when the file was put into the package - on the next reboot the apparmor_parser compares the mtime of the cache/usr.bin.ubuntu-core-launcher (very very recent) with the mtime of the souce usr.bin.ubuntu-core-launcher (much older) -> cache does is *not* re-generate Possible solution: - clear cache on upgrade - make apparmor_parser store mtime of the source file in the header - make apparmor_parser use set the cache file to the mtime of the source file used to generate the cache and re-generate if those get out-of-sync Original description: -- Rick Spencer ran into the situation that he ended up with a snappy image that gave the following error: """ apparmor="DENIED" operation="mkdir" profile="/usr/bin/ubuntu-core-launcher" name="/tmp/snap.0_pastebinit.mvo_em33Zz/" pid=1092 comm="ubuntu-core-lau" requested_mask="c" denied_mask="c" fsuid=0 ouid=0 """ Running: $ sudo apparmor_parser --skip-cache -r /etc/apparmor.d/usr.bin.ubuntu-core-launcher fixes it. This strongly indicates that the cache has the old content and did not get re-generated on upgrade or image build. I also managed to reproduce this via: 15.04/stable->15.04/edge The image is here: https://drive.google.com/open?id=0B1sb5ymdUGiLa0tUR0pGV3lzR1k&authuser=0 To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1460152/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368671] Re: [dialer-app]+[address-book]+[messaging] expansion should be removed from all contact list views
This bug was fixed in the package address-book-app - 0.2+15.10.20150601.2-0ubuntu1 --- address-book-app (0.2+15.10.20150601.2-0ubuntu1) wily; urgency=medium [ Gustavo Pichorim Boiko ] * Fix loading the settings page [ Renato Araujo Oliveira Filho ] * Add 'mailto' url call when clicking on e-mail field. (LP: #1378345) * Does not expand contact item when clicked. (LP: #1368671) * Split the app in modules to be used by dialer and messaging app. (LP: #1456782) * Updated autopilot test: (LP: #1444115) -- CI Train Bot Mon, 01 Jun 2015 22:14:02 + ** Changed in: address-book-app (Ubuntu) Status: Confirmed => Fix Released ** Changed in: dialer-app (Ubuntu) Status: Confirmed => Fix Released -- 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/1368671 Title: [dialer-app]+[address-book]+[messaging] expansion should be removed from all contact list views Status in the base for Ubuntu mobile products: New Status in Ubuntu UX bugs: Fix Committed Status in address-book-app package in Ubuntu: Fix Released Status in dialer-app package in Ubuntu: Fix Released Status in messaging-app package in Ubuntu: Fix Released Status in address-book-app source package in Vivid: New Status in dialer-app source package in Vivid: New Status in messaging-app source package in Vivid: New Bug description: Steps to reproduce: 1. Open any of the following apps - > Address Book, Phone & Messaging app 2. Navigate to a contact list view/page 3. Tap on a contact list item 4. Current implementation: the list item expands and gives you a selection of numbers and an icon appears on the tapped list item, to access contact's profile UX comment - desired solution: Remove expansion pattern from all contact views/lists. A tap action a the contact list item should open the detail screen of the contact. ---UPDATE This is became a usability issue because people didn't understand the tap and the additional tap to view the full contact details. Comment #2 "User testing showed, that expansion is not working vey well or user can not navigate all the time to the actual contact card." To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1368671/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1378345] Re: [address-book-app] Should open email app from contacts
This bug was fixed in the package address-book-app - 0.2+15.10.20150601.2-0ubuntu1 --- address-book-app (0.2+15.10.20150601.2-0ubuntu1) wily; urgency=medium [ Gustavo Pichorim Boiko ] * Fix loading the settings page [ Renato Araujo Oliveira Filho ] * Add 'mailto' url call when clicking on e-mail field. (LP: #1378345) * Does not expand contact item when clicked. (LP: #1368671) * Split the app in modules to be used by dialer and messaging app. (LP: #1456782) * Updated autopilot test: (LP: #1444115) -- CI Train Bot Mon, 01 Jun 2015 22:14:02 + ** Changed in: address-book-app (Ubuntu) Status: New => Fix Released -- 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/1378345 Title: [address-book-app] Should open email app from contacts Status in Address Book App: In Progress Status in the base for Ubuntu mobile products: New Status in Dekko: Triaged Status in Ubuntu UX bugs: In Progress Status in Unity WebApps QML component: New Status in address-book-app package in Ubuntu: Fix Released Status in address-book-app source package in Vivid: New Bug description: Steps: * add a contact with an email * open the contact Expected: * I can tap on the email address to open an email app composing an email to that contact (via a mailto: URL probably) Current: * email is not displayed at all ---UX comment--- The best solution for now would be to invoke the content hub and give user the option to select an app to send an email. To manage notifications about this bug go to: https://bugs.launchpad.net/address-book-app/+bug/1378345/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368671] Re: [dialer-app]+[address-book]+[messaging] expansion should be removed from all contact list views
This bug was fixed in the package dialer-app - 0.1+15.10.20150601.1-0ubuntu1 --- dialer-app (0.1+15.10.20150601.1-0ubuntu1) wily; urgency=medium [ CI Train Bot ] * Resync trunk. [ Gustavo Pichorim Boiko ] * Fix contact share. [ Renato Araujo Oliveira Filho ] * Implement support for no-expandable contacts list (LP: #1368671) * Make use of the new address book components instead of launch the address-book-app. (LP: #1456782) [ Sebastien Bacher ] * Update the translations template so new strings can be translated -- CI Train Bot Mon, 01 Jun 2015 20:14:38 + -- 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/1368671 Title: [dialer-app]+[address-book]+[messaging] expansion should be removed from all contact list views Status in the base for Ubuntu mobile products: New Status in Ubuntu UX bugs: Fix Committed Status in address-book-app package in Ubuntu: Fix Released Status in dialer-app package in Ubuntu: Fix Released Status in messaging-app package in Ubuntu: Fix Released Status in address-book-app source package in Vivid: New Status in dialer-app source package in Vivid: New Status in messaging-app source package in Vivid: New Bug description: Steps to reproduce: 1. Open any of the following apps - > Address Book, Phone & Messaging app 2. Navigate to a contact list view/page 3. Tap on a contact list item 4. Current implementation: the list item expands and gives you a selection of numbers and an icon appears on the tapped list item, to access contact's profile UX comment - desired solution: Remove expansion pattern from all contact views/lists. A tap action a the contact list item should open the detail screen of the contact. ---UPDATE This is became a usability issue because people didn't understand the tap and the additional tap to view the full contact details. Comment #2 "User testing showed, that expansion is not working vey well or user can not navigate all the time to the actual contact card." To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1368671/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1427831] Re: Graphics Glitch after suspending and resuming, only when pressing the sleep button
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/1427831 Title: Graphics Glitch after suspending and resuming, only when pressing the sleep button Status in Unity: New Status in unity package in Ubuntu: Confirmed Bug description: Running Ubuntu 14.10 Going to the menu and clicking on the 'suspend' button, causes no problems on resume. Automatically suspending after a given time also has no problem. However if I press the sleep button, it resumes with pixels of all colours randomly populating the screen. When I move the mouse after that, my screen goes to sleep (like when the computer is turned off). After moving my mouse again, the lockscreen displays as normal. 'sudo pm-suspend' results in only the Launcer having random coloured pixels on it. The checklist testing app had the same result. Clicking on a window reprints the launcer. Attached is an example. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1427831/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1444115] Re: Please remove test_import_item_without_sim_card
This bug was fixed in the package address-book-app - 0.2+15.10.20150601.2-0ubuntu1 --- address-book-app (0.2+15.10.20150601.2-0ubuntu1) wily; urgency=medium [ Gustavo Pichorim Boiko ] * Fix loading the settings page [ Renato Araujo Oliveira Filho ] * Add 'mailto' url call when clicking on e-mail field. (LP: #1378345) * Does not expand contact item when clicked. (LP: #1368671) * Split the app in modules to be used by dialer and messaging app. (LP: #1456782) * Updated autopilot test: (LP: #1444115) -- CI Train Bot Mon, 01 Jun 2015 22:14:02 + ** Changed in: address-book-app (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to address-book-app in Ubuntu. https://bugs.launchpad.net/bugs/1444115 Title: Please remove test_import_item_without_sim_card Status in the base for Ubuntu mobile products: New Status in address-book-app package in Ubuntu: Fix Released Status in address-book-app source package in Vivid: New Bug description: This test is failing. I believe the behavior of the app was changed and the test was not removed since now it seems in the absence of a SIM card the import from SIM option is not available/disabled. Its causing a dashboard failure. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1444115/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1462090] Re: Calling to numbers formatted with slash results in Call failed
** Also affects: telephony-service Importance: Undecided Status: New ** Also affects: hundredpapercuts 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/1462090 Title: Calling to numbers formatted with slash results in Call failed Status in One Hundred Papercuts: New Status in Telephony Service: New Status in telephony-service package in Ubuntu: New Bug description: When I call to numbers which are formatted with slash '/', I get call failed. For example when I try to call +421 2 xxx xx xxx or 02 xxx xx xxx I get call failed, because numbers are automatically formatted as +421 2/xxx xxx xx or 02/xxx xxx xx. This is probably caused by incorrect regular expression in libtelephonyservice/phoneutils.cpp for nondialable digits removal, which reads [p+*#(),;-]. I am pretty sure it should read [p+*#/(),;-]. Please, consider this bug critical, since I cannot place any call to any fixed line in Slovakia, which is basic function of phone. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1462090/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1456782] Re: [Dialer and Messaging] should be able to edit a contact without switching to address book
This bug was fixed in the package address-book-app - 0.2+15.10.20150601.2-0ubuntu1 --- address-book-app (0.2+15.10.20150601.2-0ubuntu1) wily; urgency=medium [ Gustavo Pichorim Boiko ] * Fix loading the settings page [ Renato Araujo Oliveira Filho ] * Add 'mailto' url call when clicking on e-mail field. (LP: #1378345) * Does not expand contact item when clicked. (LP: #1368671) * Split the app in modules to be used by dialer and messaging app. (LP: #1456782) * Updated autopilot test: (LP: #1444115) -- CI Train Bot Mon, 01 Jun 2015 22:14:02 + ** Changed in: address-book-app (Ubuntu) Status: In Progress => Fix Released ** Changed in: dialer-app (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1456782 Title: [Dialer and Messaging] should be able to edit a contact without switching to address book Status in the base for Ubuntu mobile products: In Progress Status in Ubuntu UX bugs: Triaged Status in address-book-app package in Ubuntu: Fix Released Status in dialer-app package in Ubuntu: Fix Released Status in messaging-app package in Ubuntu: Fix Released Status in address-book-app source package in Vivid: Confirmed Status in dialer-app source package in Vivid: Confirmed Status in messaging-app source package in Vivid: Confirmed Bug description: per design, users of dialer and messaging-app should be able to open a contact directly from within those apps and edit it. Currently it launches address book app and then the user's context is switched. Desired behavior: Dialer app: - from dialer screen click the contacts icon on header - contact list should be shown in the dialer app - click on contact to open it - should be able to edit contact from that screen and interact without switching to address book app Messaging app: - create new message - click contacts icon on header - contact list should be shown in the messaaging app - can edit or interact without switching to address book app To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1456782/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1456782] Re: [Dialer and Messaging] should be able to edit a contact without switching to address book
This bug was fixed in the package dialer-app - 0.1+15.10.20150601.1-0ubuntu1 --- dialer-app (0.1+15.10.20150601.1-0ubuntu1) wily; urgency=medium [ CI Train Bot ] * Resync trunk. [ Gustavo Pichorim Boiko ] * Fix contact share. [ Renato Araujo Oliveira Filho ] * Implement support for no-expandable contacts list (LP: #1368671) * Make use of the new address book components instead of launch the address-book-app. (LP: #1456782) [ Sebastien Bacher ] * Update the translations template so new strings can be translated -- CI Train Bot Mon, 01 Jun 2015 20:14:38 + -- 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/1456782 Title: [Dialer and Messaging] should be able to edit a contact without switching to address book Status in the base for Ubuntu mobile products: In Progress Status in Ubuntu UX bugs: Triaged Status in address-book-app package in Ubuntu: Fix Released Status in dialer-app package in Ubuntu: Fix Released Status in messaging-app package in Ubuntu: Fix Released Status in address-book-app source package in Vivid: Confirmed Status in dialer-app source package in Vivid: Confirmed Status in messaging-app source package in Vivid: Confirmed Bug description: per design, users of dialer and messaging-app should be able to open a contact directly from within those apps and edit it. Currently it launches address book app and then the user's context is switched. Desired behavior: Dialer app: - from dialer screen click the contacts icon on header - contact list should be shown in the dialer app - click on contact to open it - should be able to edit contact from that screen and interact without switching to address book app Messaging app: - create new message - click contacts icon on header - contact list should be shown in the messaaging app - can edit or interact without switching to address book app To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1456782/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1443774] Re: Horizontal scrolling is backwards
This bug was fixed in the package gtk+3.0 - 3.14.13-0ubuntu1 --- gtk+3.0 (3.14.13-0ubuntu1) vivid; urgency=medium * Update Vcs-Bzr for vivid stable branch * New upstream release 3.14.13 (LP: #1449461), fixing bugs: + most horizontal sliders are inverted when scrolled with wheel (LP: #1443774) + CSD: can't open window menu using right click after moving window + Popovers inside local plugs don't get size_allocate() called + Split Headerbar unmaximize + GtkMessageDialog: Minor documentation update + GdkOffscreenWindow should not segfault on gdk_window_beep() + GtkApplication: Prevent more crashes on shutdown * d/p/0001-GtkApplication-Prevent-more-crashes-around-shutdown.patch: Dropped, this is fixed upstream in this release. -- Iain Lane Tue, 28 Apr 2015 11:48:16 +0100 ** Changed in: gtk+3.0 (Ubuntu Vivid) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1443774 Title: Horizontal scrolling is backwards Status in gtk+3.0 package in Ubuntu: Fix Released Status in gtk+3.0 source package in Vivid: Fix Released Bug description: Don't know where to report this specifically, sorry. In native gnome applications (file manager, gedit, etc), scrolling horizontally via Trackpoint middle-button scrolling is backwards: * Middle button + trackpoint move up = scroll up (expected) * Middle button + trackpoint move down = scroll down (expected) * Middle button + trackpoint move left = scroll right (backwards) * Middle button + trackpoint move right = scroll left (backwards) Scolling horizontally in Firefox and Chromium work as expected. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150410.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-13.13-generic 3.19.3 Uname: Linux 3.19.0-13-generic x86_64 ApportVersion: 2.17-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Apr 13 23:36:58 2015 InstallationDate: Installed on 2015-03-07 (38 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: unity UpgradeStatus: Upgraded to vivid on 2015-03-29 (16 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1443774/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1443774] Update Released
The verification of the Stable Release Update for gtk+3.0 has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1443774 Title: Horizontal scrolling is backwards Status in gtk+3.0 package in Ubuntu: Fix Released Status in gtk+3.0 source package in Vivid: Fix Released Bug description: Don't know where to report this specifically, sorry. In native gnome applications (file manager, gedit, etc), scrolling horizontally via Trackpoint middle-button scrolling is backwards: * Middle button + trackpoint move up = scroll up (expected) * Middle button + trackpoint move down = scroll down (expected) * Middle button + trackpoint move left = scroll right (backwards) * Middle button + trackpoint move right = scroll left (backwards) Scolling horizontally in Firefox and Chromium work as expected. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150410.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-13.13-generic 3.19.3 Uname: Linux 3.19.0-13-generic x86_64 ApportVersion: 2.17-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Apr 13 23:36:58 2015 InstallationDate: Installed on 2015-03-07 (38 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: unity UpgradeStatus: Upgraded to vivid on 2015-03-29 (16 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1443774/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1449461] Re: [SRU] New stable release 3.14.13
This bug was fixed in the package gtk+3.0 - 3.14.13-0ubuntu1 --- gtk+3.0 (3.14.13-0ubuntu1) vivid; urgency=medium * Update Vcs-Bzr for vivid stable branch * New upstream release 3.14.13 (LP: #1449461), fixing bugs: + most horizontal sliders are inverted when scrolled with wheel (LP: #1443774) + CSD: can't open window menu using right click after moving window + Popovers inside local plugs don't get size_allocate() called + Split Headerbar unmaximize + GtkMessageDialog: Minor documentation update + GdkOffscreenWindow should not segfault on gdk_window_beep() + GtkApplication: Prevent more crashes on shutdown * d/p/0001-GtkApplication-Prevent-more-crashes-around-shutdown.patch: Dropped, this is fixed upstream in this release. -- Iain Lane Tue, 28 Apr 2015 11:48:16 +0100 ** Changed in: gtk+3.0 (Ubuntu Vivid) Status: Fix Committed => Fix Released -- 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/1449461 Title: [SRU] New stable release 3.14.13 Status in gtk+3.0 package in Ubuntu: Fix Released Status in gtk+3.0 source package in Vivid: Fix Released Bug description: [ Description ] New stable bugfix release gtk+3.0 (3.14.13-0ubuntu1) UNRELEASED; urgency=medium * Update Vcs-Bzr for vivid stable branch * New upstream release 3.14.13, fixing bugs: + most horizontal sliders are inverted when scrolled with wheel (LP: #1443774) + CSD: can't open window menu using right click after moving window + Popovers inside local plugs don't get size_allocate() called + Split Headerbar unmaximize + GtkMessageDialog: Minor documentation update + GdkOffscreenWindow should not segfault on gdk_window_beep() + GtkApplication: Prevent more crashes on shutdown * d/p/0001-GtkApplication-Prevent-more-crashes-around-shutdown.patch: Dropped, this is fixed upstream in this release. -- Iain Lane Tue, 28 Apr 2015 10:20:46 +0100 [ QA & regression potential ] This is being uploaded under the GNOME MRE. You're allowed to believe upstream that the bugs are really fixed - just give the system a general once (or twice) over to see if things still work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1449461/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1449461] Update Released
The verification of the Stable Release Update for gtk+3.0 has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1449461 Title: [SRU] New stable release 3.14.13 Status in gtk+3.0 package in Ubuntu: Fix Released Status in gtk+3.0 source package in Vivid: Fix Released Bug description: [ Description ] New stable bugfix release gtk+3.0 (3.14.13-0ubuntu1) UNRELEASED; urgency=medium * Update Vcs-Bzr for vivid stable branch * New upstream release 3.14.13, fixing bugs: + most horizontal sliders are inverted when scrolled with wheel (LP: #1443774) + CSD: can't open window menu using right click after moving window + Popovers inside local plugs don't get size_allocate() called + Split Headerbar unmaximize + GtkMessageDialog: Minor documentation update + GdkOffscreenWindow should not segfault on gdk_window_beep() + GtkApplication: Prevent more crashes on shutdown * d/p/0001-GtkApplication-Prevent-more-crashes-around-shutdown.patch: Dropped, this is fixed upstream in this release. -- Iain Lane Tue, 28 Apr 2015 10:20:46 +0100 [ QA & regression potential ] This is being uploaded under the GNOME MRE. You're allowed to believe upstream that the bugs are really fixed - just give the system a general once (or twice) over to see if things still work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1449461/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1443774] Re: Horizontal scrolling is backwards
** Also affects: gtk+3.0 (Ubuntu Vivid) Importance: Undecided Status: New ** Changed in: gtk+3.0 (Ubuntu Vivid) Status: New => Fix Committed ** Changed in: gtk+3.0 (Ubuntu Vivid) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1443774 Title: Horizontal scrolling is backwards Status in gtk+3.0 package in Ubuntu: Fix Released Status in gtk+3.0 source package in Vivid: Fix Released Bug description: Don't know where to report this specifically, sorry. In native gnome applications (file manager, gedit, etc), scrolling horizontally via Trackpoint middle-button scrolling is backwards: * Middle button + trackpoint move up = scroll up (expected) * Middle button + trackpoint move down = scroll down (expected) * Middle button + trackpoint move left = scroll right (backwards) * Middle button + trackpoint move right = scroll left (backwards) Scolling horizontally in Firefox and Chromium work as expected. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150410.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-13.13-generic 3.19.3 Uname: Linux 3.19.0-13-generic x86_64 ApportVersion: 2.17-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Apr 13 23:36:58 2015 InstallationDate: Installed on 2015-03-07 (38 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: unity UpgradeStatus: Upgraded to vivid on 2015-03-29 (16 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1443774/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1462090] [NEW] Calling to numbers formatted with slash results in Call failed
Public bug reported: When I call to numbers which are formatted with slash '/', I get call failed. For example when I try to call +421 2 xxx xx xxx or 02 xxx xx xxx I get call failed, because numbers are automatically formatted as +421 2/xxx xxx xx or 02/xxx xxx xx. This is probably caused by incorrect regular expression in libtelephonyservice/phoneutils.cpp for nondialable digits removal, which reads [p+*#(),;-]. I am pretty sure it should read [p+*#/(),;-]. Please, consider this bug critical, since I cannot place any call to any fixed line in Slovakia, which is basic function of phone. ** Affects: telephony-service Importance: Undecided Status: New ** 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/1462090 Title: Calling to numbers formatted with slash results in Call failed Status in Telephony Service: New Status in telephony-service package in Ubuntu: New Bug description: When I call to numbers which are formatted with slash '/', I get call failed. For example when I try to call +421 2 xxx xx xxx or 02 xxx xx xxx I get call failed, because numbers are automatically formatted as +421 2/xxx xxx xx or 02/xxx xxx xx. This is probably caused by incorrect regular expression in libtelephonyservice/phoneutils.cpp for nondialable digits removal, which reads [p+*#(),;-]. I am pretty sure it should read [p+*#/(),;-]. Please, consider this bug critical, since I cannot place any call to any fixed line in Slovakia, which is basic function of phone. To manage notifications about this bug go to: https://bugs.launchpad.net/telephony-service/+bug/1462090/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 409644] Re: Print to file folder chooser dialog creates folders with "Open" button
** Bug watch added: GNOME Bug Tracker #750420 https://bugzilla.gnome.org/show_bug.cgi?id=750420 ** Also affects: gtk via https://bugzilla.gnome.org/show_bug.cgi?id=750420 Importance: Unknown Status: Unknown -- 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/409644 Title: Print to file folder chooser dialog creates folders with "Open" button Status in GTK+ GUI Toolkit: Unknown Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: In at least two apps where a filename is entered along with a drop- down directory chooser with an "other" option, the dialog to choose the "other" directory will unintentionally create new directories. gnome-print (?): 1. Start Gedit (or Firefox, etc.). 2. File-->Print... 3. Select "Print to File" under the Printers column. 4. "Save in folder" drop-down --> "Other..." 5. Type "TEST" in the Location. 6. Click "Open" or press Enter. 7. BUG: A folder called "TEST" is created and the folder choosing dialog is closed, with "TEST" selected. gnome-utils (?): 1. Start Take Screenshot (Apps-->Accessories-->Take Screenshot) 2. Continue at #4, above. Since my intention is something like a "save as" operation, and the dialog looks like a save-as dialog, I often type the filename that I want to use, and press enter. But then a directory is created with the filename that I want to use. Very annoying because now I have to find that directory and delete it. To fix this, I have a couple of ideas/suggestions: * Utilize a dedicated directory chooser dialog (is there one for Gnome, as in MS Windows?), or * When a filename is entered in this "other" chooser, the filename in the original dialog (e.g. print-to-file, or Screenshot save preview) should be set to it, and the "save in folder" should also be adjusted to the folder that was open in the dialog. * Fixing the current chooser dialog so it only creates folders when "Create Folder" button is pressed, or * Separate the location+filename selection such as the "Save As..." dialog to a separate stage in the print-to-file process, or * Adjust the print-to-file dialog in some way I don't know yet. Ubuntu 9.04 Gnome 2.26.1 Gedit 2.26.1 Firefox 3.0.13 To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/409644/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1462084] Re: Folder chooser cancels directory creation on dialog confirmation
** Bug watch added: GNOME Bug Tracker #750418 https://bugzilla.gnome.org/show_bug.cgi?id=750418 ** Also affects: gtk via https://bugzilla.gnome.org/show_bug.cgi?id=750418 Importance: Unknown Status: Unknown -- 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/1462084 Title: Folder chooser cancels directory creation on dialog confirmation Status in GTK+ GUI Toolkit: Unknown Status in gtk+3.0 package in Ubuntu: New Bug description: These steps are in Nautilus, but same happens in e.g. Shotwell, so a gtk bug. Steps to reproduce: - open Nautilus/Files - right-click on an item - choose "Move To..." - click "Create Folder" - type in a folder name (don't press enter) - click "Select" Expected: - folder gets created - the created folder is used as target Current: - folder does not get created - the first folder available is used as target ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: libgtk-3-0 3.14.12-0ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jun 4 22:10:59 2015 SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1462084/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1462087] Re: Folder chooser creates and opens new directory when clicked on another
** Bug watch added: GNOME Bug Tracker #750419 https://bugzilla.gnome.org/show_bug.cgi?id=750419 ** Also affects: gtk via https://bugzilla.gnome.org/show_bug.cgi?id=750419 Importance: Unknown Status: Unknown -- 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/1462087 Title: Folder chooser creates and opens new directory when clicked on another Status in GTK+ GUI Toolkit: Unknown Status in gtk+3.0 package in Ubuntu: New Bug description: Somewhat related to bug #1462084: These steps are in Nautilus, but same happens in e.g. Shotwell, so a gtk bug. Steps to reproduce: - open Nautilus/Files - right-click on an item - choose "Move To..." - click "Create Folder" - type in a folder name (don't press enter) - click on a different folder Expected: - folder creation is cancelled or - user isn't allowed to click on a different folder Current: - folder is created - the created folder is opened (not the one the user clicked on) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: libgtk-3-0 3.14.12-0ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jun 4 22:10:59 2015 SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1462087/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1462087] [NEW] Folder chooser creates and opens new directory when clicked on another
Public bug reported: Somewhat related to bug #1462084: These steps are in Nautilus, but same happens in e.g. Shotwell, so a gtk bug. Steps to reproduce: - open Nautilus/Files - right-click on an item - choose "Move To..." - click "Create Folder" - type in a folder name (don't press enter) - click on a different folder Expected: - folder creation is cancelled or - user isn't allowed to click on a different folder Current: - folder is created - the created folder is opened (not the one the user clicked on) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: libgtk-3-0 3.14.12-0ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jun 4 22:10:59 2015 SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gtk Importance: Unknown Status: Unknown ** Affects: gtk+3.0 (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 gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1462087 Title: Folder chooser creates and opens new directory when clicked on another Status in GTK+ GUI Toolkit: Unknown Status in gtk+3.0 package in Ubuntu: New Bug description: Somewhat related to bug #1462084: These steps are in Nautilus, but same happens in e.g. Shotwell, so a gtk bug. Steps to reproduce: - open Nautilus/Files - right-click on an item - choose "Move To..." - click "Create Folder" - type in a folder name (don't press enter) - click on a different folder Expected: - folder creation is cancelled or - user isn't allowed to click on a different folder Current: - folder is created - the created folder is opened (not the one the user clicked on) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: libgtk-3-0 3.14.12-0ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jun 4 22:10:59 2015 SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1462087/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 409644] Re: Print to file folder chooser dialog creates folders with "Open" button
I can confirm this still happens in gtk 3.14.12 (Ubuntu 15.04) -- 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/409644 Title: Print to file folder chooser dialog creates folders with "Open" button Status in GTK+ GUI Toolkit: Unknown Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: In at least two apps where a filename is entered along with a drop- down directory chooser with an "other" option, the dialog to choose the "other" directory will unintentionally create new directories. gnome-print (?): 1. Start Gedit (or Firefox, etc.). 2. File-->Print... 3. Select "Print to File" under the Printers column. 4. "Save in folder" drop-down --> "Other..." 5. Type "TEST" in the Location. 6. Click "Open" or press Enter. 7. BUG: A folder called "TEST" is created and the folder choosing dialog is closed, with "TEST" selected. gnome-utils (?): 1. Start Take Screenshot (Apps-->Accessories-->Take Screenshot) 2. Continue at #4, above. Since my intention is something like a "save as" operation, and the dialog looks like a save-as dialog, I often type the filename that I want to use, and press enter. But then a directory is created with the filename that I want to use. Very annoying because now I have to find that directory and delete it. To fix this, I have a couple of ideas/suggestions: * Utilize a dedicated directory chooser dialog (is there one for Gnome, as in MS Windows?), or * When a filename is entered in this "other" chooser, the filename in the original dialog (e.g. print-to-file, or Screenshot save preview) should be set to it, and the "save in folder" should also be adjusted to the folder that was open in the dialog. * Fixing the current chooser dialog so it only creates folders when "Create Folder" button is pressed, or * Separate the location+filename selection such as the "Save As..." dialog to a separate stage in the print-to-file process, or * Adjust the print-to-file dialog in some way I don't know yet. Ubuntu 9.04 Gnome 2.26.1 Gedit 2.26.1 Firefox 3.0.13 To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/409644/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1462084] [NEW] Folder chooser cancels directory creation on dialog confirmation
Public bug reported: These steps are in Nautilus, but same happens in e.g. Shotwell, so a gtk bug. Steps to reproduce: - open Nautilus/Files - right-click on an item - choose "Move To..." - click "Create Folder" - type in a folder name (don't press enter) - click "Select" Expected: - folder gets created - the created folder is used as target Current: - folder does not get created - the first folder available is used as target ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: libgtk-3-0 3.14.12-0ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jun 4 22:10:59 2015 SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gtk+3.0 (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 gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1462084 Title: Folder chooser cancels directory creation on dialog confirmation Status in gtk+3.0 package in Ubuntu: New Bug description: These steps are in Nautilus, but same happens in e.g. Shotwell, so a gtk bug. Steps to reproduce: - open Nautilus/Files - right-click on an item - choose "Move To..." - click "Create Folder" - type in a folder name (don't press enter) - click "Select" Expected: - folder gets created - the created folder is used as target Current: - folder does not get created - the first folder available is used as target ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: libgtk-3-0 3.14.12-0ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jun 4 22:10:59 2015 SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1462084/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1453942] Re: Calling to some numbers results in Call failed
This is probably on telephony-service to handle the slash character, since I found regexp [p+*#(),;-] in libtelephonyservice/phoneutils.cpp for nondialable digits removal, which should probably read [p+*#/(),;-]. I am going to file a bug against telephony-service. -- 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/1453942 Title: Calling to some numbers results in Call failed Status in dialer-app package in Ubuntu: Confirmed Bug description: When I try to call some numbers I cannot place the call and get Call failed message. After some investigation a think this is related to automatically adding the slash '/' sign into the number. When I call number 02 xxx xx xxx, the number is formatted 02/xxx xxx xx and the call is not placed. When I use second SIM which is in VPN and I should use 0 to call out or use international format, I get these results when calling the same station: When calling 0 02 xxx xx xxx, the number is formatted 00 2xx xx xxx x and the call is successfully placed. When calling +421 2 xxx xx xxx, the number is formatted +421 2/xxx xxx xx and the call is failing. You probably remove displayed spaces when placing a call but do not remove slash signs. The formatting slash cannot be manually deleted. I am using: Description: Ubuntu Utopic Unicorn (development branch) Release: 14.10 dialer-app: 0.1+15.04.20150216-rtm-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1453942/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 409644] Re: Print to file folder chooser dialog creates folders with "Open" button
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gtk+3.0 (Ubuntu) Status: New => Confirmed -- 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/409644 Title: Print to file folder chooser dialog creates folders with "Open" button Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: In at least two apps where a filename is entered along with a drop- down directory chooser with an "other" option, the dialog to choose the "other" directory will unintentionally create new directories. gnome-print (?): 1. Start Gedit (or Firefox, etc.). 2. File-->Print... 3. Select "Print to File" under the Printers column. 4. "Save in folder" drop-down --> "Other..." 5. Type "TEST" in the Location. 6. Click "Open" or press Enter. 7. BUG: A folder called "TEST" is created and the folder choosing dialog is closed, with "TEST" selected. gnome-utils (?): 1. Start Take Screenshot (Apps-->Accessories-->Take Screenshot) 2. Continue at #4, above. Since my intention is something like a "save as" operation, and the dialog looks like a save-as dialog, I often type the filename that I want to use, and press enter. But then a directory is created with the filename that I want to use. Very annoying because now I have to find that directory and delete it. To fix this, I have a couple of ideas/suggestions: * Utilize a dedicated directory chooser dialog (is there one for Gnome, as in MS Windows?), or * When a filename is entered in this "other" chooser, the filename in the original dialog (e.g. print-to-file, or Screenshot save preview) should be set to it, and the "save in folder" should also be adjusted to the folder that was open in the dialog. * Fixing the current chooser dialog so it only creates folders when "Create Folder" button is pressed, or * Separate the location+filename selection such as the "Save As..." dialog to a separate stage in the print-to-file process, or * Adjust the print-to-file dialog in some way I don't know yet. Ubuntu 9.04 Gnome 2.26.1 Gedit 2.26.1 Firefox 3.0.13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/409644/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1461593] Re: No data connection switching from 2G only to 3G
Thanks for the log @Victor. So the smoking gun is: Jun 4 14:26:41 ubuntu-phablet NetworkManager[1408]: Disabling autoconnect for connection '/214040113340577/context2'. There's only one of these in the log. When this happens, NetworkManager has seen a disconnect for the modem, but hasn't yet seen the signal that the GPRS has de-tached ( which is what should happen when you change radio technology ). In this case, NM retries the modem rapidly, and burns through the autoconnect_retry_count for the connection. When this count reaches zero, NM sets a 5m timer to reset the retry_count and try again. This is indeed similar to the bug #1418077 ( FixReleased ) and bug #1445080 ( InProgress). I have a partial fix for the latter bug which may resolve your specific scenario. One question, do you wait for the network-indicator to show the mobile connection is active before switching the radio technology from 3g to 2g, and back again? I see the connection coming up in the syslog, but it looks like the technology gets toggled again before it's completely finished. -- 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/1461593 Title: No data connection switching from 2G only to 3G Status in network-manager package in Ubuntu: New Status in network-manager package in Ubuntu RTM: Incomplete Bug description: Test case. - Open System Settings. - Go to Cellular. - Switch from 3G to 2G, check that indicator network shows 2G only connection. - Switch from 2G only to 3G. Expected result. - Indicator network shows 3G connection, and user can use data connection. Actual result. - Data connection is lost. Tested in single SIM and dual SIM mode, with two different SIM cards from different operators. current build number: 23 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1461593/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1414396] Re: ubuntu dropped to initramfs shell after reboot several hours
When Ubuntu fails to boot, it will enter the recovery mode in GRUB2 which will disable the timeout, so it will stay on the GRUB menu and will not proceed to boot the OS as the timeout is disactivated. One workaround is to disable it so that the timeout doesn't get disactivated. https://help.ubuntu.com/community/Grub2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1414396 Title: ubuntu dropped to initramfs shell after reboot several hours Status in initramfs-tools package in Ubuntu: New Bug description: 1. on few server 2. create 16 service profiles and associate them to 16 servers 3. pxe install 16 servers 4. start 2 medusa maim on each host 5. start 6 iperf on each host 6. reboot host-172(ubuntu with efi boot) and host-181 (ubuntu with legacy boot) every 2 minutes 7. after reboots for several hours, the server 181 stops in initramfs shell. see screenshot 8. reset server 181, it stops in gnu grub menu, see screenshot, then hit return, the host can boot successfully 9. reboot the host 181 again, it doesn't stop in gnu grub menu as in step9, and it can boot successfully. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1414396/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1414396] Re: ubuntu dropped to initramfs shell after reboot several hours
Please attach the screeshot and tell which Ubuntu version was run. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1414396 Title: ubuntu dropped to initramfs shell after reboot several hours Status in initramfs-tools package in Ubuntu: New Bug description: 1. on few server 2. create 16 service profiles and associate them to 16 servers 3. pxe install 16 servers 4. start 2 medusa maim on each host 5. start 6 iperf on each host 6. reboot host-172(ubuntu with efi boot) and host-181 (ubuntu with legacy boot) every 2 minutes 7. after reboots for several hours, the server 181 stops in initramfs shell. see screenshot 8. reset server 181, it stops in gnu grub menu, see screenshot, then hit return, the host can boot successfully 9. reboot the host 181 again, it doesn't stop in gnu grub menu as in step9, and it can boot successfully. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1414396/+subscriptions -- Mailing list: https://launchpad.net/~touch-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.
FYI, the current plan is to wait until Debian bug #786555 gets fixed, and then publish updates for stable Ubuntu releases based on the jessie sudo package. -- 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 GNOME Control Center: Unknown Status in sudo: Unknown Status in Unity: Invalid Status in policykit-desktop-privileges package in Ubuntu: Opinion Status in sudo package in Ubuntu: Fix Released Status in policykit-desktop-privileges source package in Precise: Opinion Status in sudo source package in Precise: Triaged Status in policykit-desktop-privileges source package in Trusty: Opinion Status in sudo source package in Trusty: Triaged Status in policykit-desktop-privileges source package in Utopic: Opinion Status in sudo source package in Utopic: Triaged Status in policykit-desktop-privileges source package in Vivid: Opinion Status in sudo source package in Vivid: Triaged 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//", 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/gnome-control-center/+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 1427219] [glib2.0/utopic] verification still needed
The fix for this bug has been awaiting testing feedback in the -proposed repository for utopic for more than 90 days. Please test this fix and update the bug appropriately with the results. In the event that the fix for this bug is still not verified 15 days from now, the package will be removed from the -proposed repository. ** Tags added: removal-candidate -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1427219 Title: [SRU] New stable release 2.42.2 Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Utopic: Fix Committed Bug description: We should continue to track the stable series that utopic is based on. Overview of changes in GLib 2.42.2 == * Bugs fixed: 712570 Hang in g_threaded_socket_service_func 719455 g_file_make_directory_with_parents() can erroneously throw... 727829 win32: glibconfig.h.win32 updates 734946 Implement GContentType on OSX 741024 glist: Mention that g_list_length() is bad for checking li... 741654 [patch] gobject: don't use G_STRLOC in G_OBJECT_WARN_INVAL... 741788 Document GSettings build system integration 741807 Add thread name support on OS X and iOS 742851 avoid MSVC warnings in G_STMT_END 743508 polkitd fails to start: patch for gio/gcredentialsprivate.h 743936 handle unsigned modifier for long long in internal printf * Translation updates: Swedish This is uploaded under the GNOME MRE. Assume these bugs are really fixed and just generally test your system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1427219/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1450894] Re: [Indicators] Messaging indicator does not indicate that there is a new message
This bug was fixed in the package unity8 - 8.02+15.10.20150603.1-0ubuntu1 --- unity8 (8.02+15.10.20150603.1-0ubuntu1) wily; urgency=medium [ CI Train Bot ] * New rebuild forced. * Resync trunk. [ Renato Araujo Oliveira Filho ] * Set the device led color to green. (LP: #1450894) -- CI Train Bot Wed, 03 Jun 2015 21:42:35 + -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1450894 Title: [Indicators] Messaging indicator does not indicate that there is a new message Status in the base for Ubuntu mobile products: Fix Released Status in The Messaging Menu: New Status in Themes for Ubuntu: New Status in Ubuntu UX bugs: Fix Committed Status in indicator-messages package in Ubuntu: Fix Committed Status in ubuntu-themes package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: Fix Released Bug description: When you receive a message the indicator menu turns from opaque to full white to indicate that there is a new message. But this is not clear since all the other icons are white and you do not see any difference. This is very confuse to understand that the indicator is in a different state from the other indicators or if it needs attention. --DESIGN RESOLUTION--- Please use the current ubuntu theme green to indicate that there is a new message - #3FB24F, the same green as we use for the battery icon in indicators. Change the LED light to green as well. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1450894/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1450894] Re: [Indicators] Messaging indicator does not indicate that there is a new message
This bug was fixed in the package ubuntu-themes - 14.04+15.10.20150603.1-0ubuntu1 --- ubuntu-themes (14.04+15.10.20150603.1-0ubuntu1) wily; urgency=medium [ CI Train Bot ] * New rebuild forced. [ Charles Kerr ] * cherrypick the new messages-new.svg suru icon from lp:~tiheum/ubuntu-themes/suru-app-icons-v2 (LP: #1450894) -- CI Train Bot Wed, 03 Jun 2015 21:41:43 + ** Changed in: ubuntu-themes (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: unity8 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1450894 Title: [Indicators] Messaging indicator does not indicate that there is a new message Status in the base for Ubuntu mobile products: Fix Released Status in The Messaging Menu: New Status in Themes for Ubuntu: New Status in Ubuntu UX bugs: Fix Committed Status in indicator-messages package in Ubuntu: Fix Committed Status in ubuntu-themes package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: Fix Released Bug description: When you receive a message the indicator menu turns from opaque to full white to indicate that there is a new message. But this is not clear since all the other icons are white and you do not see any difference. This is very confuse to understand that the indicator is in a different state from the other indicators or if it needs attention. --DESIGN RESOLUTION--- Please use the current ubuntu theme green to indicate that there is a new message - #3FB24F, the same green as we use for the battery icon in indicators. Change the LED light to green as well. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1450894/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1439710] Re: Indicator failed to show cellular icon
is this still happening? ** Changed in: indicator-network (Ubuntu) Status: New => Incomplete ** Changed in: indicator-network (Ubuntu) Assignee: (unassigned) => Jonathan Cave (jocave) -- 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/1439710 Title: Indicator failed to show cellular icon Status in the base for Ubuntu mobile products: New Status in indicator-network package in Ubuntu: Incomplete Bug description: Version: ubuntu-touch/vivid-proposed arale r148 Inserted a SIM and rebooted after flash of the above. After boot network indicator showed a wifi connection, but no cellular connection. On the menu the cellular showed "Offline". Examing ofono list-modems showed ril_0 as online. Issued a "restart network-indicator" and the state then showed the cellular connection correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1439710/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1443583] Re: Dataroaming only active after turning wifi on
Thank you for the bug report. Could you please check the system-settings that the correct SIM card is selected for mobile data and that mobile data for that SIM card is enabled when roaming. Could you also elaborate what you mean by the data roaming being active only after turning Wi-Fi on ? ** Changed in: indicator-network (Ubuntu) Status: New => Incomplete ** Changed in: indicator-network (Ubuntu) Assignee: (unassigned) => Gregorovics (gregorovics) -- 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/1443583 Title: Dataroaming only active after turning wifi on Status in indicator-network package in Ubuntu: Incomplete Bug description: Roaming active on sim1 only on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1443583/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1440121] Re: Can not connect to WPA2-EAP wireless LAN with bq aquaris
we need to investigate this more. WPA2-EAP support has not been implemented, but interacting with such accesspoints through the indicator should not render the indicator defunct. ** Changed in: indicator-network (Ubuntu) Status: New => Triaged ** Changed in: indicator-network (Ubuntu) Importance: Undecided => High -- 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/1440121 Title: Can not connect to WPA2-EAP wireless LAN with bq aquaris Status in indicator-network package in Ubuntu: Triaged Bug description: When I touch the name of the network on the list, at the indicators menu, nothing happens. When I try it again 3, 4 times, the whole "Network" tab becomes empty, even the SIM card informations disappear, and the icon of the tab switches to a gear instead of the signal strength indicator. Then the Network tab stays empty until the next reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1440121/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1436814] Re: Use a roaming indicator for each SIM on dual SIM phones
Thank you for the bug report. As this report mostly deals with design proposals, I'm adding ubuntu-ux to the list of projects to get design department to weight in. @yuri: You can check the associated networks from the network indicator more quickly than going through system settings. Roaming indications should already be shown per modem inside the indicator as well, but fixing bug #1366014 also makes it apparent which SIM is used for mobile data so you can verify easily if you are using a roaming connection for the data. @michael-zukowski: for the roaming in Germany with German card, please file a new bug here: https://bugs.launchpad.net/ubuntu/+source/ofono/+filebug @michael-zukowski: for SIM 1+2 always being mixed up please mark the bug #1447479 also affecting you. ** Also affects: ubuntu-ux Importance: Undecided Status: New ** Changed in: indicator-network (Ubuntu) Status: Confirmed => Triaged ** Changed in: indicator-network (Ubuntu) Importance: Undecided => Wishlist -- 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/1436814 Title: Use a roaming indicator for each SIM on dual SIM phones Status in Ubuntu UX bugs: New Status in indicator-network package in Ubuntu: Triaged Bug description: For dual SIM phones, the roaming indicator should be related to each SIM, by having a "R" sign on the top of each signal strength indicator, or by having the roaming indicator in red (or another color) or by having the indicator blinking. I live near a border, and I work on the other side of this border: I have 2 SIM's, one for each country. As the phone is sometime "lazzy" to connect each SIM to the right operator as soon as it becomes available, when I switch from one country to the another, I'm not able to check if both SIM are on the right network: sometime, I place or I receive a call thinking I'm not in the roaming mode... and it is not true. The work around consists to go the the system settings of the phone to check each SIM card and its associated operator. Having an roaming indicator dedicated to each SIM could help: a quick glance is enough to check the card status. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1436814/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1436820] Re: Blocked SIM card keeps on asking for PUK
** Changed in: indicator-network (Ubuntu) Importance: Undecided => Medium ** Changed in: indicator-network (Ubuntu RTM) Importance: Undecided => Medium -- 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/1436820 Title: Blocked SIM card keeps on asking for PUK Status in the base for Ubuntu mobile products: New Status in indicator-network package in Ubuntu: Incomplete Status in ofono package in Ubuntu: Fix Committed Status in indicator-network package in Ubuntu RTM: Incomplete Status in ofono package in Ubuntu RTM: Confirmed Bug description: I managed to enter the wrong PUK for a SIM card for 10 times in a row and the phone keeps on asking me for the PUK. It always says that this will be the last attempt even though it's too late already. Instead, it should say that this SIM card is rejected and only emergency calls are possible. Reported on This is krillin, with RTM image 21. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1436820/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1436724] Re: [indicators] [SIM PIN] No prompt to unlock sim after airplane mode
related to bug #1436064 ** Changed in: indicator-network (Ubuntu) Status: Confirmed => Triaged ** Changed in: indicator-network (Ubuntu) Importance: Undecided => Wishlist -- 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/1436724 Title: [indicators] [SIM PIN] No prompt to unlock sim after airplane mode Status in the base for Ubuntu mobile products: New Status in Ubuntu UX bugs: Triaged Status in indicator-network package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Invalid Bug description: BQ phone: Steps to reproduce: 1. Turn airplane mode on 2. Turn airplane mode off Desired effect: You get a prompt to unlock your sim cards What I got: You get no connection and no prompt. Only if you open the "network" panel, you see that your sim is still locked. You should get a prompt to unlock your sim after turning off airplane mode. Otherwise the user does not know the sim card is still locked. The fact that the sim card becomes locked after airplane mode is not something you should have to think about as a user. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1436724/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1436712] Re: lists no aps, doesn't display wifi icon in panel while connected
this has been fixed by the qtdbus port of i-network ** Changed in: indicator-network (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1436712 Title: lists no aps, doesn't display wifi icon in panel while connected Status in indicator-network package in Ubuntu: Fix Released Bug description: Using rtm 256 on bq, the device is connected to wifi but the panel icons only show the phone carrier icons, not the wifi one. nmcli lists aps correctly and confirms the device is connected, so the issue seems to be with the indicator To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1436712/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1436064] Re: SIM-PIN has to be entered every time after leaving the airplanemode
This is a feature of the BQ phone HW as it removes the modem SIM interfaces completely when entering flight mode. The only option to work around this would be for ofono rild driver to cache the sim pins when it detects a BQ phone HW and flightmode being activated and automatically enter the PINs behind the scenes when the phone leaves flightmode. Updated indicator-network task to Invalid and restored ofono status. ** Changed in: ofono (Ubuntu) Status: Invalid => Confirmed ** Changed in: indicator-network (Ubuntu) Status: New => Invalid -- 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/1436064 Title: SIM-PIN has to be entered every time after leaving the airplanemode Status in the base for Ubuntu mobile products: New Status in Usability Bugs in Ubuntu Phone: New Status in indicator-network package in Ubuntu: Invalid Status in ofono package in Ubuntu: Confirmed Bug description: Every time after leaving the air-plane mode you are forced to enter the SIM-Pin. While changing frequently between on-line and off-line this is annoying. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1436064/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1456730] Re: Hang after installing and running serviio
ack - just to reiterate - worked fine in 15.04 (and assuming it still does), issue appears only with 15.10 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1456730 Title: Hang after installing and running serviio Status in systemd package in Ubuntu: New Bug description: Ran serviio during the vivid cycle with no problem - either using systemd or upstart. Installed wily. Grabbed,extracted serviio from http://download.serviio.org/releases/serviio-1.5.2-linux.tar.gz Installed openjdk-8-jre. Set ~/serviio-1.5.2/bin/serviio.sh and ~/serviio-1.5.2/bin/serviio- console.sh to run at start. Reboot using systemd,serviio starts. Reboot hangs for 90s. Kill java tasks associated with serviio - reboot takes place in time expected. Boot with upstart - reboot takes place in time expected. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: systemd 219-9ubuntu1 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] ProcVersionSignature: Ubuntu 3.19.0-17.17-generic 3.19.6 Uname: Linux 3.19.0-17-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE Date: Tue May 19 18:19:40 2015 InstallationDate: Installed on 2015-05-12 (6 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150512) MachineType: NOVATECH LTD MBB-44608 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-17-generic root=UUID=6bcbfcc1-c493-4dbe-9421-ef270047a82a ro quiet splash SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-DS2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: 7383241-001 dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.chassis.version: V1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0: dmi.product.name: MBB-44608 dmi.product.version: V1.0 dmi.sys.vendor: NOVATECH LTD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1456730/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1462046] Re: Incorrect btrfs ready invocation 64-btrfs.rules
Supposedly 'btrfs ready $devnode' is internal to udev and unrelated to the similarly named btrfs device ready command ** Changed in: systemd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1462046 Title: Incorrect btrfs ready invocation 64-btrfs.rules Status in systemd package in Ubuntu: Invalid Bug description: /lib/udev/rules.d/64-btrfs.rules This invokes "btrfs ready $devnode". However that will always give a usage error. The correct invocation is as follows (note added "device"). btrfs device ready $devnode ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: udev 219-7ubuntu5 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: XFCE CustomUdevRuleFiles: 51-android.rules 60_smfpautoconf_samsung.rules 61_smfpautoconf_samsung.rules 99-libsane-samsungmfp.rules 60-vboxdrv.rules Date: Thu Jun 4 10:39:36 2015 MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-18-generic root=UUID=3ff68715-0daa-4e44-8de2-0997f36d8ab6 ro rootflags=subvol=@ nomdmonddf nomdmonisw init=/lib/systemd/systemd udev.log-priority=debug rd.udev.log-priority=debug SourcePackage: systemd UpgradeStatus: Upgraded to vivid on 2015-04-23 (41 days ago) dmi.bios.date: 08/13/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2104 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2104:bd08/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1462046/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1430769] Re: Does not detect hidden WiFi on first attempt
*** This bug is a duplicate of bug 1354560 *** https://bugs.launchpad.net/bugs/1354560 ** This bug has been marked a duplicate of bug 1354560 Indicator doesn't show connected status when associated with hidden network -- 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/1430769 Title: Does not detect hidden WiFi on first attempt Status in indicator-network package in Ubuntu: New Status in ubuntu-system-settings package in Ubuntu: Invalid Status in wpasupplicant package in Ubuntu: New Bug description: The WiFi network I use at home is a hidden one. While it works with my Ubuntu Phone, I always have to toggle WiFi on and off about 3 times until it is detected. phablet@ubuntu-phablet:~$ system-image-cli --info current build number: 129 device name: mako channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/vivid-proposed last update: 2015-03-11 13:19:54 version version: 129 version ubuntu: 20150310.3 version device: 20150210 version custom: 20150310.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1430769/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1429158] Re: Autopilot tests depend on qt4
** Changed in: indicator-network (Ubuntu) Importance: Undecided => Low ** Changed in: indicator-network (Ubuntu) Status: New => Triaged -- 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/1429158 Title: Autopilot tests depend on qt4 Status in Camera App: Confirmed Status in address-book-app package in Ubuntu: New Status in camera-app package in Ubuntu: New Status in click-update-manager package in Ubuntu: New Status in cordova-ubuntu package in Ubuntu: New Status in gallery-app package in Ubuntu: New Status in indicator-network package in Ubuntu: Triaged Status in mediaplayer-app package in Ubuntu: New Status in notes-app package in Ubuntu: New Status in ubuntu-html5-theme package in Ubuntu: New Status in ubuntu-keyboard package in Ubuntu: New Status in ubuntu-system-settings package in Ubuntu: New Status in ubuntu-ui-toolkit package in Ubuntu: New Status in ubuntuone-credentials package in Ubuntu: Fix Released Status in unity-scope-click package in Ubuntu: Fix Released Status in unity-webapps-qml package in Ubuntu: New Status in unity8 package in Ubuntu: Fix Released Bug description: When installing the autopilot tests, they bring qt4 dependencies that are unnecessary. The package with the autopilot tests depends on libautopilot-qt, which installs both autopilot-qt4 and autopilot-qt5. We can remove that dependency and add autopilot-qt5 and qttestability- autopilot instead. To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1429158/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1427358] Re: Network indicator should deal with AP/P2P Wi-Fi devices as well as active AP/P2P connections
** Changed in: indicator-network (Ubuntu) Status: New => Incomplete ** Changed in: indicator-network (Ubuntu) Importance: Undecided => Wishlist ** Changed in: indicator-network (Ubuntu) Status: Incomplete => Triaged -- 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/1427358 Title: Network indicator should deal with AP/P2P Wi-Fi devices as well as active AP/P2P connections Status in Ubuntu UX bugs: Triaged Status in indicator-network package in Ubuntu: Triaged Bug description: Using vivid on krillin Background: From the spec on networking [1]: A hotspot requires Wi-Fi to work. To warn you that turning off Wi-Fi will turn off the hotspot, whenever Hotspot is on, the “Wi-Fi” switch wherever it appears (in the quick-access area, in the “Wi-Fi” screen, and in the network menu) should instead be “Wi-Fi used for hotspot”. In addition, turning on Flight Mode should warn that it will turn off Hotspot. Reproduce: Start an AP hotspot using [2] What happens: 1. The network indicator gives no indication that turning off Wi-Fi will disable the hotspot 2. Flight mode silently disables hotspot and does not restore it after being turned off 3. The AP looks like any 'normal', connected network What should happen: 1. The Wi-Fi switch should have a different label (see [1]) 2. Going into flight mode should yield a warning 3. The AP should probably be visually separated from 'normal' networks [1] https://wiki.ubuntu.com/Networking#hotspot [2] http://bazaar.launchpad.net/~mathieu-tl/+junk/touch-hotspot/view/head:/hotspot.py To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1427358/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1426876] Re: SIM PIN Unlock doesn't always trigger an actual unlock action
needs more investigation. ** Changed in: indicator-network (Ubuntu) Importance: Undecided => Medium ** Changed in: indicator-network (Ubuntu) Status: Confirmed => Incomplete -- 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/1426876 Title: SIM PIN Unlock doesn't always trigger an actual unlock action Status in indicator-network package in Ubuntu: Incomplete Status in unity8 package in Ubuntu: Confirmed Bug description: current build number: 127 device name: krillin channel: ubuntu-touch/devel-proposed Two SIMs installed, SIM in the second slot is PIN-locked. It's possible for a PIN to be entered on the SIM auto-prompt screen ( displayed at boot ) and the subsequent action ( ie. the DBus EnterPin call to ofono ) to get dropped. This results in the SIM still being locked when the user dismisses the greeter. This bug was discovered while testing an ofono vivid silo. The associated ofono merge request is: https://code.launchpad.net/~phablet- team/ofono/ww10-update/+merge/250665 The version of ofono in the silo (ubuntu-013) is: 1.12.bzr6888+15.04.20150224-0ubuntu1 There's some kind of race condition involved, as this seldom happens ( ~5% of the time ). I was finally able to prove that this was unity8 ( or some other upper layer component ) by adding info log messages to the ofono functions that handle the DBus EnterPin method, and the associated callback function. The scenario that clinched it for me was: 1. Boot phone 2. Enter bad PIN and tap check button when prompted for SIM2 [ See that remaining Retries is reported as 2 ] 3. Enter PIN again and tap check button again 4. Examine syslog and notice that there's only a single call to EnterPIN, which is followed by a log message showing the callback failure for the bad PIN entered. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1426876/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1425362] Re: unity8 crashed with SIGSEGV in QLightDM::GreeterImpl::authenticateWithPam() when logging in
This bug was fixed in the package unity8 8.02+15.04.20150603.1-0ubuntu1 in https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/stable- phone-overlay --- unity8 (8.02+15.04.20150603.1-0ubuntu1) vivid; urgency=medium [ CI Train Bot ] * New rebuild forced. * Resync trunk. [ Renato Araujo Oliveira Filho ] * Set the device led color to green. (LP: #1450894) unity8 (8.02+15.10.20150518.1-0ubuntu1) wily; urgency=medium [ Albert Astals Cid ] * Add overrides to override functions * Implement "rating-edit" preview widget (LP: #1318144) * Make the DashContent::test_mainNavigation test more stable (LP: #1450809) * Use art height as implicitHeight when the header is overlayed and there's no summary [ CI Train Bot ] * New rebuild forced. * Resync trunk. [ Daniel d'Andrada ] * Introducing FloatingFlickable * Make Ubuntu.Gestures components install TouchRegistry by themselves [ Michael Terry ] * Fix a possible crash in our PAM threading code. (LP: #1425362) (LP: #1425362) * Fix the lockscreen becoming unresponsive after testing an app on the device from QtCreator. (LP: #1435364) [ Nick Dedekind ] * Fixed desktop stage app focus. * Fixed issue in laggy indicator autpilot tests (LP: #1446846) unity8 (8.02+15.04.20150511-0ubuntu1) vivid; urgency=medium [ Albert Astals Cid ] * Workarounds for concierge mode. [ CI Train Bot ] * New rebuild forced. * Resync trunk. unity8 (8.02+15.04.20150505-0ubuntu1) vivid; urgency=medium [ Albert Astals Cid ] * Make runtests fake a test error if make fails * Make the test more stable * Use dbus-test-runner instead of dbus-launch [ Daniel d'Andrada ] * DirectionalDragArea: improvements & API grooming (LP: #1417920) * Fix EdgeDragEvaluator when a drag can happen both ways (Direction.Horizontal) [ Josh Arenson ] * Remove panelHeight property as it is unused. [ Leo Arias ] * Initial clean up of the autopilot tests set up. Removed the touch device from the test case. Moved the restart of unity to a fixture. Removed the unused DragMixin. Updated the setUpClass to use process_helpers. Removed the workaround for bug #1238417, already fixed. Use the toolkit helper to set the testability environment variable. Fixed the indicators base class that was restarting unity twice. (LP: #1238417, #1447206) * Use the base class from the toolkit in autopilot tests. [ Michael Zanetti ] * emit application-stop when we're going down (LP: #1326513) [ Michał Sawicz ] * UNITY_SCOPES_LIST is no more [ handsome_feng<445865...@qq.com> ] * When click the favorite scope in Dash Manager , it just return to the corresponding scope page. (LP: #1447056) unity8 (8.02+15.04.20150422-0ubuntu1) vivid; urgency=medium [ Albert Astals Cid ] * Compile with Qt 5.5 (LP: #1437238) * Different way of top aligning labels when the other one in the row is multiline (LP: #1442085) * make pot_file [ Andrea Cimitan ] * Set sourceSize for DashBackground.qml Image [ CI Train Bot ] * New rebuild forced. * Resync trunk. added: po/sk.po [ Daniel d'Andrada ] * Move handling of command line options to a separate class * Refactor tst_PhysicalKeysMapper.qml [ Leo Arias ] * For autopilot tests, use the device simulation scenarios from the toolkit. [ Leonardo Arias Fonseca ] * For autopilot tests, use the device simulation scenarios from the toolkit. [ Michael Zanetti ] * Make sure dnd mode is ended properly when drag gesture is cancelled (LP: #1444949) [ Michał Sawicz ] * Fix flake8 warnings (LP: #1444170) * Move mock indicator service to unity8-fake-env, as it's a binary- dependent package. [ Nick Dedekind ] * Use asynchronous dbus requests for property updates. (LP: #1436982) -- CI Train Bot Wed, 03 Jun 2015 21:42:35 + ** Changed in: unity8 (Ubuntu RTM) Status: New => Fix Released -- 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/1425362 Title: unity8 crashed with SIGSEGV in QLightDM::GreeterImpl::authenticateWithPam() when logging in Status in unity8 package in Ubuntu: Fix Released Status in unity8 source package in Vivid: New Status in unity8 package in Ubuntu RTM: Fix Released Bug description: I'm trying to run unity8 in a vivid vmware session (mir works fine here). But unity8 crashes when logging in, and it happens again everytime I insert my password in the u8 lockscreen. --- The only way to successfully log in unity8 was to add myself to the "nopasswdlogin" group. This made the unity8 pam module checks, and thus no crash. ProblemType: CrashDistroRelease: Ubuntu 15.04 Package: unity8 8.02+15.04.20150224-0ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Uname: Linux 3.18.0-13-generic x86_64 ApportVersion: 2.16.1-0
[Touch-packages] [Bug 1422570] Re: Network indicator incorrectly claims no network available, VPN no longer working
sorry michi, this got lost in the NEW queue. the correct project is network-manager-gnome. ** Package changed: indicator-network (Ubuntu) => network-manager-applet (Ubuntu) -- 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/1422570 Title: Network indicator incorrectly claims no network available, VPN no longer working Status in network-manager-applet package in Ubuntu: New Bug description: I'm not sure whether this is the right project... I did an apt-get upgrade on my vivid machine last week. Since then, my previously working VPN setup no longer works (both new and old VPN). Symptoms: - After rebooting and logging in and clicking on the up-down arrow icon, I see "No network devices available". That is definitely wrong, seeing that, as a matter of fact, I'm on my ethernet, and it's working fine. (I'm typing this on the affected machine.) - Since the reboot, my previously working VPN config is toast. I had both the old and the two new VPNs configured and working fine. Now, when I click on "VPN Connections", none of the previously configured networks are there. It's as if I had never configured anything. I figured I'll try re-adding the missing VPN config, but no joy. After re-adding a connection from my saved .conf file and clicking save, I get an error dialog: "Connection not visible or not available: Method "GetAll" with signature "s" on interface "org.freedesktop.DBus.Properties" doesn't existConnection not visible or not available: Method "GetAll" with signature "s" on interface "org.freedesktop.DBus.Properties" doesn't exist" I have not hacked around with anything on this machine. No PPAs or the like... I'd appreciate help with this. Right now, I can't access anything company-internal from that machine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1422570/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1425172] Re: Network indicator lists the non-exist AP (timeout for the AP to be removed is too big, ~6min)
** Changed in: indicator-network (Ubuntu) Status: Confirmed => Incomplete ** Changed in: indicator-network (Ubuntu) Assignee: Pete Woods (pete-woods) => (unassigned) ** Changed in: indicator-network (Ubuntu) Importance: High => Undecided -- 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/1425172 Title: Network indicator lists the non-exist AP (timeout for the AP to be removed is too big, ~6min) Status in the base for Ubuntu mobile products: Confirmed Status in indicator-network package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Incomplete Status in network-manager package in Ubuntu RTM: Confirmed Bug description: Summary: Network indicator lists the non-exist AP Steps to reproduce: 1. Boot to system 2. Scroll down the Network indicator 3. It lists about 10 AP (In Taipei office) 4. Go to another place and check network indicator again Expected Result: It should not list non-exist AP and only show available AP Actual Result: It shows about 12 AP on the screen but only two are real AP for connecting, and others 10 are from last list. This is reproducible on mako/krillin on both RTM and vivid. The main issue is that the timeout for the AP to be removed from the known AP list is too big when comparing with other phones. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1425172/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1415098] Re: [connectivity-service] Extend the connectivity-api for WiFi scanning
** Changed in: indicator-network (Ubuntu) Status: New => Triaged ** Changed in: indicator-network (Ubuntu) Importance: Undecided => Wishlist -- 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/1415098 Title: [connectivity-service] Extend the connectivity-api for WiFi scanning Status in indicator-network package in Ubuntu: Triaged Bug description: I am currently trying to build a WiFi scanner app for Ubuntu Touch. Since Click apps are confined and have no root rights, all other approaches failed. I hereby propose to expose the needed information and API calls through the connectivity-api. The minimum amount of information needed is: - A list of all broadcasting stations (BSS/IBSS) in range - Broadcast station MAC address - SSID (may be emtpy) - Center frequency or channel (the one can be converted into the other) - Signal strength - Available authentication and encryption schemes - Timestamp when the station was last seen This is basically the same information as encapsulated in an android.net.wifi.ScanResult object on Android. Optional, but "nice to have" information would be: - The contents of the "Capability Info" field of the beacon frame. - Supported data rates, so one can distinguish between 802.11b/g/n/ac networks. This information is encoded in the "Rates" and ""Supported MCS Set" fields of the beacon frame. - The contents of the "HT Capability Info" field (if present) of the beacon frame. This optional information is already recorded by the kernel and is e.g. decoded/displayed by a call to `iw dev wlan0 scan`. Since the network management service has to monitor its surroundings anyways, e.g. to detect and connect to an already known network or to switch to a better access point during movement, the information should be readily available. A single `scanResults()` call returning a list of broadcast station objects should therefore already be enough. I propose the following additional API features: - A method to register a callback function which is called after every successful scan. This frees the application from polling the API, may save power and the app can process new information instantly. - A method to set the scan interval within a pre-defined range. The network management service may decide to adapt its scan interval to the current situation to save power, e.g. a longer interval when not currently connected and a short one when connected. A scanner app may require a short, constant interval. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1415098/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1416741] Re: [connectivity-service] Extend the connectivity-api for mobile network scanning
** Changed in: indicator-network (Ubuntu) Status: New => Triaged ** Changed in: indicator-network (Ubuntu) Importance: Undecided => Wishlist -- 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/1416741 Title: [connectivity-service] Extend the connectivity-api for mobile network scanning Status in indicator-network package in Ubuntu: Triaged Bug description: I think exposing as much information as possible about mobile networks opens the door for interesting applications, e.g. IMSI catcher detectors, free cell tower location databases, location-based services etc. Technology There are currently at least four different mobile network technologies available around the world: -GSM -LTE -CDMA -WCDMA (UMTS) A device may support one or more technologies at the same time, and the currently available status may therefore change over time. For example an LTE device may temporarily roam down to UMTS or even GSM. Needed information The available information differs between technologies, and new technologies will be introduced during the lifetime of the API, so the design should be extensible. -GSM: A base station is identified by its Cell-ID (CID), Location Area Code (LAC), Mobile Country Code (MCC) and Mobile Network Code (MNC). The last digit of the CID may encode the antenna number if the same base station has more than one. Signal strength may be reported in ASU, dBm or “levels”. A Timing Advance value is used to coarsely describe the distance between the mobile device and the currently used base station. -LTE: A base station is identified by its Cell-ID (CID), Mobile Country Code (MCC), Mobile Network Code (MNC), Physical Cell ID and Tracking Area code. Signal strength may be reported in ASU, dBm or “levels”. Timing Advance values are available for every base station of the same operator within range, not only for the currently used one. -CDMA: A base station is identified by its Base Station ID, Latitude, Longitude, Network ID and System ID. Signal strength may be reported in ASU, dBm, Ec/Io, “levels” or SNR. EVDO for faster data transfer may be available. -WCDMA (UMTS): A base station is identified by its Cell-ID (CID), Mobile Country Code (MCC), Mobile Network Code (MNC) and Primary Scrambling Code. Signal strength may be reported in ASU, dBm or “levels”. API calls and features The Baseband chip has to monitor the whole network at all times anyway, so the required information should be readily available. A single call a la `networkCells()` should therefore suffice. The rest of the API is heavily dependent on which methods the Baseband offers and which data it exposes. Security and Privacy A hostile app may calculate the location of a user from the list of cell towers in range. Because of the long-range nature of mobile networks this location will often not be accurate, but especially in cities it may be accurate enough. I therefore propose that the first call to networkCells() triggers a system popup informing the user about possible privacy implications and asking for permission. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1416741/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1421671] Re: Implement wifi hotspot status
** Changed in: indicator-network (Ubuntu) Status: New => Triaged ** Changed in: indicator-network (Ubuntu) Importance: Undecided => Wishlist -- 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/1421671 Title: Implement wifi hotspot status Status in indicator-network package in Ubuntu: Triaged Bug description: Implement the wifi hotspot status in the indicator per the [1] spec 1. https://wiki.ubuntu.com/Networking#hotspot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1421671/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1418836] Re: [System Setting][Wi-Fi] When turnning off flight mode and go to wireless indicator, there is no any availabe wifi networks
this has been fixed by the qtdbus port. ** Changed in: indicator-network (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1418836 Title: [System Setting][Wi-Fi] When turnning off flight mode and go to wireless indicator, there is no any availabe wifi networks Status in indicator-network package in Ubuntu: Fix Released Bug description: Environment: Unit: Mako (Nexus4) Product: Vivid System version: r88 Steps: 1. turn on flight mode 2. turn off flight mode 3. go to wireless Expected result: user could select any available Wi-Fi networks Actual result: no any available wifi network list but "Previous networks" and "Connect to hidden network" p.s. after restart system (with flight mode off), all available wi-fi list would show up normally. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1418836/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1411714] Re: indicator-network not functioning after modems reboot
** Changed in: indicator-network (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1411714 Title: indicator-network not functioning after modems reboot Status in the base for Ubuntu mobile products: Fix Released Status in indicator-network package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: Invalid Status in ofono package in Ubuntu: Invalid Status in indicator-network package in Ubuntu RTM: Fix Released Bug description: 1) The release of Ubuntu current build number: 75 device name: krillin channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/vivid-proposed last update: 2015-01-16 13:56:36 version version: 75 version ubuntu: 20150116 version device: 20150113-9cccefe version custom: 20150116 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center Using libqofono-0.70, ofono 1.12.bzr6882+15.04.20141126-0ubuntu1 which deviates from the default 3) What you expected to happen After the modems rebooted, I expected the network indicator to function normally 4) What happened instead The network indicator's WI-Fi and Flight Mode switches are reverted after a tap/click. In the network indicator both SIMs are listed as Disconnected. Sometimes I see a cog: http://i.imgur.com/bAwAB71.png 5) Steps to reproduce On a dual SIM device, alternate between running /usr/share/ofono/scripts/set-3g-slot /ril_0 and /usr/share/ofono/scripts/set-3g-slot /ril_1 This is the output of ofono/scripts/list-modems: http://pastebin.ubuntu.com/9762092/ wlan0 has gone away, see output of $ ifconfig -a: http://pastebin.ubuntu.com/9762104/ This appears in the network-manager.log: http://pastebin.ubuntu.com/9762128/ ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: indicator-network 0.5.1+15.04.20141216-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.15.1-0ubuntu2 Architecture: armhf Date: Fri Jan 16 16:16:33 2015 InstallationDate: Installed on 2015-01-16 (0 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20150116-020204) SourcePackage: indicator-network UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1411714/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1416731] Re: [connectivity-service] Extend the connectivity-api for Bluetooth scanning
** Changed in: indicator-network (Ubuntu) Status: New => Triaged ** Changed in: indicator-network (Ubuntu) Importance: Undecided => Wishlist -- 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/1416731 Title: [connectivity-service] Extend the connectivity-api for Bluetooth scanning Status in indicator-network package in Ubuntu: Triaged Bug description: One of my Ubuntu Touch app ideas is a Bluetooth Scanner. Bluetooth management functionality will have to be implemented anyways, and since Qt Bluetooth is not part of Ubuntu Touch images, I propose the extension of the connectivity-api. The purpose of a Bluetooth scanner is to find all devices in range and gather as much additional information as possible, so we have to keep in mind which device types exist and which information we care about. -Bluetooth Classic: At least the device MAC address and the contents of the “Class of Device” field are needed. If the device has a “pretty name” set, we want to know it, and if the adapter reports the signal strength with which the information was received this is important as well. We also want to query devices for the exact list of services they offer. -Bluetooth Low Energy: Advertisements contain up to 31 bytes of arbitrary information, and the scanning device may actively query for up to 31 additional bytes. This information is important because it contains device names, UUIDs etc. The list of services offered can be retrieved using the Generic Attribute Profile (GATT), so the API should offer the necessary calls. API calls and features I propose the following API functions: - startScan() initiates a scan using the given technology. For Bluetooth Classic this would trigger an active scan, while for Bluetooth Low Energy it would set the device to continuous listening mode. Since it is unknown if and when the scan is finished, the call should return immediately and information is returned via callbacks. Depending on the hardware it may be possible to start scans for the different technologies at the same time. -stopScan() stops an ongoing scan. -queryServices() takes a device address and actively queries for a list of all offered services. The specification mentions quite short timeouts for many message types, so I am not sure if this call should block or use a callback. Security and Privacy A hostile app may calculate the location of a user from the list of iBeacons in range, and because of the short-range nature of Bluetooth this location will be quite accurate. I therefore propose that the first call to startScan() triggers a system popup informing the user about possible privacy implications and asking for permission. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1416731/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1450894] Re: [Indicators] Messaging indicator does not indicate that there is a new message
** Changed in: canonical-devices-system-image Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1450894 Title: [Indicators] Messaging indicator does not indicate that there is a new message Status in the base for Ubuntu mobile products: Fix Released Status in The Messaging Menu: New Status in Themes for Ubuntu: New Status in Ubuntu UX bugs: Fix Committed Status in indicator-messages package in Ubuntu: Fix Committed Status in ubuntu-themes package in Ubuntu: Fix Committed Status in unity8 package in Ubuntu: New Bug description: When you receive a message the indicator menu turns from opaque to full white to indicate that there is a new message. But this is not clear since all the other icons are white and you do not see any difference. This is very confuse to understand that the indicator is in a different state from the other indicators or if it needs attention. --DESIGN RESOLUTION--- Please use the current ubuntu theme green to indicate that there is a new message - #3FB24F, the same green as we use for the battery icon in indicators. Change the LED light to green as well. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1450894/+subscriptions -- Mailing list: https://launchpad.net/~touch-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] Re: dbus puts system to sleep every 30 seconds
*** This bug is a duplicate of bug 1450009 *** https://bugs.launchpad.net/bugs/1450009 i see now setting "HandleLidSwitch=ignore" in /etc/systemd/logind.conf will my laptop from suspending completely. Not ideal. -- 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: Confirmed 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= 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 1412444] Re: no indication when the cellular network connection is not encrypted
** Changed in: indicator-network (Ubuntu) Status: New => Triaged ** Changed in: indicator-network (Ubuntu) Importance: Undecided => Wishlist -- 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/1412444 Title: no indication when the cellular network connection is not encrypted Status in the base for Ubuntu mobile products: New Status in Ubuntu UX bugs: Triaged Status in indicator-network package in Ubuntu: Triaged Status in ofono package in Ubuntu: Confirmed Bug description: From TS 100 920 - V8.1.0: 3.3.3 Functional Requirements: """ The ME has to check if the user data confidentiality is switched on using one of the seven algorithms. In the event that the ME detects that this is not the case, or ceases to be the case (e.g. during handover), then an indication is given to the user. This ciphering indicator feature may be disabled by the SIM (see GSM 11.11). In case the SIM does not support the feature that disables the ciphering indicator, then the ciphering indicator feature in the ME shall be enabled by default. """ My understanding of this is that we should at least show a warning icon and maybe explanatory text inside the i-network and maybe relevant apps like phone-app and messaging-app that the cellular communication channel is not encrypted. Without encryption anyone with sufficient equipment can eavesdrop the voice and data communication between the cell tower and users phone. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1412444/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1407918] Re: [phone] Toggling WiFi leaves both GSM and WiFi connected
the icon changing is a separate bug #1339792 and the fact that ccmni0 being kept alive is intended behaviour. It does not consume battery even though it's visible. ** Changed in: indicator-network (Ubuntu) Status: Confirmed => Won't Fix -- 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/1407918 Title: [phone] Toggling WiFi leaves both GSM and WiFi connected Status in indicator-network package in Ubuntu: Won't Fix Bug description: This is one more that's probably not in the right place... please reassign as appropriate. Steps: * disable WiFi via switch in the Network menu * wait for a GSM data connection * enable WiFi again * rinse'n'repeat Expected: * GSM connection is dropped whenever WiFi is available Current: * sometimes GSM is dropped, but sometimes it remains on, even if unused The routes and all go through WiFi, so traffic should be fine, but the icon still says H for me, and there is a ccmni0 interface up. Please find attached logs from network-test-session when I switched WiFi off and on. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: indicator-network 0.5.1+15.04.20141216-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.15-0ubuntu3 Architecture: armhf Date: Tue Jan 6 10:19:05 2015 InstallationDate: Installed on 2014-12-18 (19 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20141218-020204) SourcePackage: indicator-network UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1407918/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
