[Touch-packages] [Bug 1406047] Re: Poor contrast between text and background in ProgressBar
It should indeed turn white, looks like a problem with RTM. Tim are you able to fix? ** Changed in: ubuntu-ux Status: Triaged = Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1406047 Title: Poor contrast between text and background in ProgressBar Status in Ubuntu UX bugs: Fix Committed Status in ubuntu-ui-toolkit package in Ubuntu: Triaged Bug description: I'm not sure if this is an issue for everyone, or just for people with colour blindness but I find the dark grey text showing the progress percentage very difficult to read against the Ubuntu orange colour. Switching to a light colour like white would be more readable once the current progress covers the text. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1406047/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1325899] Re: evince is excruciatingly slow on some documents
** Changed in: poppler (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1325899 Title: evince is excruciatingly slow on some documents Status in Poppler: Invalid Status in poppler package in Ubuntu: Fix Released Bug description: Evince is excruciatingly slow when displaying the book available for download at http://www.safetty.net/publications/pttes Scrolling can take several seconds and will often just display empty pages. (And it is even worse with the 2009 version of the book you can still find on several places on the internet), while xpdf has no problems at all with instantly switching to the next page. To manage notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/1325899/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1373607] Re: Switching the camera from rear to front to rear facing causing the controls to disappear
** Branch linked: lp:~fboucault/qtvideo-node/fix_rotate_z_order -- 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/1373607 Title: Switching the camera from rear to front to rear facing causing the controls to disappear Status in Camera App: In Progress Status in the base for Ubuntu mobile products: Confirmed Status in camera-app package in Ubuntu: In Progress Status in camera-app package in Ubuntu RTM: In Progress Bug description: $ system-image-cli -i current build number: 254 device name: mako channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/utopic-proposed last update: 2014-09-24 16:38:15 version version: 254 version ubuntu: 20140924 version device: 20140923.1 version custom: mako-0.6 What happened: 1) Start the camera app, note the contols at the bottom (video mode, capture photo, switch camera) 2) Select switch camera to change to the front facing, note the controls are still there 3) Select switch camera again to switch back to rear facing 4) Notice that the controls have disappeared and that the user has to touch the screen for the controls to appear again. What was expected: At step 4 for the controls to be visible To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1373607/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1429171] Re: systemd-fsckd[232]: Couldn't connect to plymouth: Connection refused
dino99: I guess plymouth wasn't running for you when fsck started, right? I conditioned the fact that the messages are sent to plymouth if the pid file is present (see http://lists.freedesktop.org/archives/systemd- devel/2015-March/029174.html) ** Changed in: systemd (Ubuntu) Status: New = In Progress ** Changed in: systemd (Ubuntu) Importance: Undecided = Low -- 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/1429171 Title: systemd-fsckd[232]: Couldn't connect to plymouth: Connection refused Status in systemd package in Ubuntu: In Progress Bug description: get that error logged many times into journalctl on that vivid booting with systemd-sysv ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-4ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu1 Architecture: i386 CurrentDesktop: GNOME Date: Fri Mar 6 16:11:58 2015 Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-7-generic root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1429171/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1429171] Re: systemd-fsckd[232]: Couldn't connect to plymouth: Connection refused
@Didier this is a vivid i386 with a gnome-shell session; so i suppose that plymouth is always used while logging (as expected by default, but i admit i rarely care about it as that process is quite hidden for user) and i suppose it is deactivated when the login is done. now when i got that systemd-fsck i cant tell if plymouth was already activated or not yet. That 'connection refused' looks unecpected when fsck is ran as that job is done way before login time, so plymouth should not be disturbing it. -- 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/1429171 Title: systemd-fsckd[232]: Couldn't connect to plymouth: Connection refused Status in systemd package in Ubuntu: In Progress Bug description: get that error logged many times into journalctl on that vivid booting with systemd-sysv ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-4ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu1 Architecture: i386 CurrentDesktop: GNOME Date: Fri Mar 6 16:11:58 2015 Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-7-generic root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1429171/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1429809] [NEW] ATI HDMI audio: echoing and crackling sound
Public bug reported: Hello, my computer is connected to my TV screen with HDMI. I'm using HDMI displayport audio out in pulseaudio. I hear crackling and echoing. If I use this workaround: echo '# add support for intel audio options snd-hda-intel vid=8086 pid=8ca0 snoop=0' /etc/modprobe.d/alsa-base.conf it works but after several minutes I have an important delay between video and audio. Thank you for your help. LGDN. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: magneto1830 F pulseaudio /dev/snd/pcmC1D3p: magneto1830 F...m pulseaudio /dev/snd/controlC1: magneto1830 F pulseaudio /dev/snd/controlC0: magneto1830 F pulseaudio CurrentDesktop: Unity Date: Mon Mar 9 12:30:14 2015 InstallationDate: Installed on 2014-06-19 (263 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: HD-Audio Generic - HD-Audio Generic Symptom_Jack: Digital Out, HDMI Symptom_Type: Underruns, dropouts, or crackling sound Title: [All Series, ATI R6xx HDMI, Digital Out, HDMI] Underruns, dropouts or crackling sound UpgradeStatus: Upgraded to utopic on 2015-03-09 (0 days ago) dmi.bios.date: 12/13/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1707 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: GRYPHON Z87 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.:bvr1707:bd12/13/2013:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnGRYPHONZ87:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1429809 Title: ATI HDMI audio: echoing and crackling sound Status in alsa-driver package in Ubuntu: New Bug description: Hello, my computer is connected to my TV screen with HDMI. I'm using HDMI displayport audio out in pulseaudio. I hear crackling and echoing. If I use this workaround: echo '# add support for intel audio options snd-hda-intel vid=8086 pid=8ca0 snoop=0' /etc/modprobe.d/alsa-base.conf it works but after several minutes I have an important delay between video and audio. Thank you for your help. LGDN. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: magneto1830 F pulseaudio /dev/snd/pcmC1D3p: magneto1830 F...m pulseaudio /dev/snd/controlC1: magneto1830 F pulseaudio /dev/snd/controlC0: magneto1830 F pulseaudio CurrentDesktop: Unity Date: Mon Mar 9 12:30:14 2015 InstallationDate: Installed on 2014-06-19 (263 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: HD-Audio Generic - HD-Audio Generic Symptom_Jack: Digital Out, HDMI Symptom_Type: Underruns, dropouts, or crackling sound Title: [All Series, ATI R6xx HDMI, Digital Out, HDMI] Underruns, dropouts or crackling sound UpgradeStatus: Upgraded to utopic on 2015-03-09 (0 days ago) dmi.bios.date: 12/13/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1707 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: GRYPHON Z87 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.:bvr1707:bd12/13/2013:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnGRYPHONZ87:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage
[Touch-packages] [Bug 1422762] Re: Camera should not change behavior when rotation lock is on
** Changed in: camera-app (Ubuntu) Status: Confirmed = In Progress ** Changed in: camera-app Status: New = In Progress ** Changed in: camera-app Assignee: (unassigned) = Florian Boucault (fboucault) ** Changed in: camera-app (Ubuntu) Assignee: (unassigned) = Florian Boucault (fboucault) -- 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/1422762 Title: Camera should not change behavior when rotation lock is on Status in Camera App: In Progress Status in camera-app package in Ubuntu: In Progress Bug description: (from mailing list) On Bq 4.5 running RTM r17 1) enable screen rotation lock 2) take a photo horizontally 3) disable screen rotation lock 4) rotate the phone in any way, the photo is rotated incorrectly, as if it was originally taken vertically I think that the camera application should ignore the rotation lock or at least, implant the actual (correct) orientation into the taken photo. To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1422762/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1424864] Re: Xorg crash
apport-collect does not work for current vivid Linux ubuntu 3.19.0-7-generic #7-Ubuntu SMP Thu Feb 26 20:19:34 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux ubuntu@ubuntu:~$ apport-collect You need to run 'sudo apt-get install python-apport' for apport-collect to work. ubuntu@ubuntu:~$ apport-bug -- 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/1424864 Title: Xorg crash Status in xorg package in Ubuntu: Incomplete Bug description: Xorg crashing out back into login manager and apport failed This problem report is damaged and cannot be processed. IOError(u'Invalid core dump: BFD: Warning: /tmp/tmpXYLMdA is truncated: expected core file size = 75243520, found: 6356992.',) openConnection: connect: No such file or directory cannot connect to brltty at :0 xfce4-settings-helper: Another instance is already running. Leaving... (polkit-gnome-authentication-agent-1:9183): GLib-CRITICAL **: g_variant_new_string: assertion `string != NULL' failed (polkit-gnome-authentication-agent-1:9183): polkit-gnome-1-WARNING **: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files ERROR: Error querying target relations ERROR: Error querying target relations ERROR: Error querying target relations ERROR: Error querying target relations ERROR: Error querying target relations (xfce4-settings-helper:9229): xfce4-settings-helper-WARNING **: Failed to get the _NET_NUMBER_OF_DESKTOPS property. ** Message: applet now removed from the notification area ** Message: using fallback from indicator to GtkStatusIcon ** Message: applet now embedded in the notification area WARNING: gnome-keyring:: couldn't connect to: /tmp/keyring-P0TMTU/pkcs11: No such file or directory (Thunar:9173): GLib-GIO-CRITICAL **: g_file_info_get_attribute_uint32: assertion `G_IS_FILE_INFO (info)' failed (Thunar:9173): GLib-GIO-CRITICAL **: g_file_info_get_attribute_uint32: assertion `G_IS_FILE_INFO (info)' failed WARNING: gnome-keyring:: couldn't connect to: /tmp/keyring-P0TMTU/pkcs11: No such file or directory ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-76.111-generic 3.2.66 Uname: Linux 3.2.0-76-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.8 Architecture: amd64 Date: Mon Feb 23 19:14:16 2015 InstallationMedia: Xubuntu 12.04.4 LTS Precise Pangolin - Release amd64 (20140205) MarkForUpload: True ProcEnviron: LANGUAGE=en_CA:en TERM=xterm PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1424864/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1429383] Re: The keyboard doesn't appear
Hi Marcel, thanks for reporting this; I've just flashed image 125 and haven't been able to reproduce this. Is there a crash file in /var/crash beginning with the name _usr_bin_maliit-server? If so could you attach that file to this bug report? Also, which keyboard layouts do you have enabled? Thanks! ** Changed in: ubuntu-keyboard (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1429383 Title: The keyboard doesn't appear Status in ubuntu-keyboard package in Ubuntu: Incomplete Bug description: Device: mako (NEXUS 4) System: 15.04 r125 I have no keyboard after update this morning!!! Clicking in a textfield: The cursor comes, but no textfield. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1429383/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1311706] Re: XU 12.04-4 dual display not working nvidia 173 on nv34 card
12.04.05 LTS is now EOL that is odd news ** Changed in: xorg (Ubuntu) Status: Incomplete = 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/1311706 Title: XU 12.04-4 dual display not working nvidia 173 on nv34 card Status in xorg package in Ubuntu: Invalid Bug description: hoping to get Precise Pangolin 12.04 LT Xubuntu running dual displays, on VGA (CRT) the other smart tv via HDMI. as soon as xu goes to login screen I lose DVI to HDMI connection. Other distros, sparky, mint, puppy all work fine with dual display I run nvidia 173 on a nv34 video card /0/100/b/0 display NV34 [GeForce FX 5200] /0/100/ebridge nForce3 250Gb PCI-to-PCI Bridge 3.2.0-60-generic #91-Ubuntu SMP Wed Feb 19 03:54:44 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux nvidia config does not show a second display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1311706/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1429838] Re: Some (internal) test programs have too much messy code and filenames are not consistent
** Branch linked: lp:~tpeeters/ubuntu-ui-toolkit/cleanHeaderTests -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1429838 Title: Some (internal) test programs should be split up and filenames are not consistent Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Bug description: The various tests in tests/resources/navigation/header.html should be put in separate files to make them easier to read and maintain. Also a the filenames in tests/resources/* and some unit tests are not consistent (use different capitalizations, and/or underscores in filenames). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1429838/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1428272] Re: Recording video with rotation lock on results in aspect ratio error in resultant video file
** Changed in: camera-app Status: Confirmed = In Progress ** Changed in: camera-app (Ubuntu) Status: Confirmed = In Progress ** Changed in: camera-app (Ubuntu) Assignee: (unassigned) = Florian Boucault (fboucault) ** Changed in: camera-app Assignee: (unassigned) = Florian Boucault (fboucault) -- 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/1428272 Title: Recording video with rotation lock on results in aspect ratio error in resultant video file Status in Camera App: In Progress Status in camera-app package in Ubuntu: In Progress Bug description: Found on the Krillin... If you record video with Rotation Lock 'On' the resulting video file is squashed on playback. Steps to reproduce. - Set rotation lock on - record a video in the camera app while holding the phone in landscape mode). - playback the video Result: - the video is played back but it is 'squashed' horizontally. To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1428272/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1429840] [NEW] Sound - HDA-Intel - HDA ATI SB - 5.1 wont work
Public bug reported: About 1 week ago i have installed Ubuntu 14.04.2 LTS for a lightweight Ruby studying,i also have a 5.1 speaker system wich fully- exploitable,but linux wont use all speakers fine - in despite of all speakers connected,linux see only front right and left speakers whatever i do. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1429840 Title: Sound - HDA-Intel - HDA ATI SB - 5.1 wont work Status in alsa-driver package in Ubuntu: New Bug description: About 1 week ago i have installed Ubuntu 14.04.2 LTS for a lightweight Ruby studying,i also have a 5.1 speaker system wich fully- exploitable,but linux wont use all speakers fine - in despite of all speakers connected,linux see only front right and left speakers whatever i do. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1429840/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1429838] [NEW] Some (internal) test programs should be split up and filenames are not consistent
Public bug reported: The various tests in tests/resources/navigation/header.html should be put in separate files to make them easier to read and maintain. Also a the filenames in tests/resources/* and some unit tests are not consistent (use different capitalizations, and/or underscores in filenames). ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: Low Assignee: Tim Peeters (tpeeters) Status: In Progress ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New = In Progress ** Changed in: ubuntu-ui-toolkit (Ubuntu) Assignee: (unassigned) = Tim Peeters (tpeeters) ** Changed in: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided = Medium ** Changed in: ubuntu-ui-toolkit (Ubuntu) Importance: Medium = Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1429838 Title: Some (internal) test programs should be split up and filenames are not consistent Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Bug description: The various tests in tests/resources/navigation/header.html should be put in separate files to make them easier to read and maintain. Also a the filenames in tests/resources/* and some unit tests are not consistent (use different capitalizations, and/or underscores in filenames). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1429838/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1427804] Re: Mouse pointer disappears after upgrade to kernel 3.19
I would appreciate if you could add yourself as an affected user. -- 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/1427804 Title: Mouse pointer disappears after upgrade to kernel 3.19 Status in xorg package in Ubuntu: New Bug description: After upgrade to kernel 3.19, the mouse pointer disappears. The mouse is fully functional, just cannot see its pointer, which makes it pretty useless... ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 Uname: Linux 3.19.0-031900-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Mar 3 19:23:30 2015 DistUpgraded: 2014-11-04 19:50:17,092 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.248+bdcom, 3.16.0-31-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 3.19.0-031900-generic, x86_64: installed vboxhost, 4.3.18, 3.16.0-30-generic, x86_64: installed vboxhost, 4.3.18, 3.16.0-31-generic, x86_64: installed vboxhost, 4.3.18, 3.19.0-031900-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8534] InstallationDate: Installed on 2014-10-24 (129 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-031900-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to utopic on 2014-11-04 (118 days ago) dmi.bios.date: 09/30/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2012 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-PRO(Wi-Fi ac) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx 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.:bvr2012:bd09/30/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-PRO(Wi-Fiac):rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS 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.3 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.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Tue Mar 3 19:21:19 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4121 vendor WAC xserver.version: 2:1.16.0-1ubuntu1.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1427804/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1416048] Re: [media player] Expected to be able to pause a video by tapping on anywhere of the video
I agree with Jim's suggestion - let's make the first tap show controls ** Changed in: ubuntu-ux Status: Triaged = Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mediaplayer-app in Ubuntu. https://bugs.launchpad.net/bugs/1416048 Title: [media player] Expected to be able to pause a video by tapping on anywhere of the video Status in Media Player App: Confirmed Status in Ubuntu UX bugs: Fix Committed Status in mediaplayer-app package in Ubuntu: New Bug description: Tapping anywhere on the video that is playing should pause it and vice versa. To manage notifications about this bug go to: https://bugs.launchpad.net/mediaplayer-app/+bug/1416048/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1429756] Re: FTBFS: test_job_process fails in majority of cases
It started failing around Feb 27. It roughly coincides with https://launchpad.net/ubuntu/+source/glibc/2.19-15ubuntu2 (but that looks unlikely), the most likely candidate is the upgrade of linux from 3.18 to 3.19: https://launchpad.net/ubuntu/+source/linux/3.19.0-7.7 ** Description changed: As you see in the history in https://jenkins.qa.ubuntu.com/job/vivid- adt-upstart/?, upstart's test fail almost all the time, on ok 53 - with single line command writing fast and exiting not ok 54 - with single line command writing lots of data fast and exiting - wrong value for bytes, expected 3145728 got 3018027 - at tests/test_job_process.c:3886 (test_start). + wrong value for bytes, expected 3145728 got 3018027 + at tests/test_job_process.c:3886 (test_start). 1..153 FAIL: test_job_process Sometimes they succeed on one architecture, and with lots of luck on both, but this is way too flaky to be an useful test. This keeps blocking the propagation of other packages from -proposed. + + This was most likely triggered by the kernel update from 3.18 to 3.19. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1429756 Title: FTBFS: test_job_process fails in majority of cases Status in upstart package in Ubuntu: New Status in upstart source package in Vivid: New Bug description: As you see in the history in https://jenkins.qa.ubuntu.com/job/vivid- adt-upstart/?, upstart's test fail almost all the time, on ok 53 - with single line command writing fast and exiting not ok 54 - with single line command writing lots of data fast and exiting wrong value for bytes, expected 3145728 got 3018027 at tests/test_job_process.c:3886 (test_start). 1..153 FAIL: test_job_process Sometimes they succeed on one architecture, and with lots of luck on both, but this is way too flaky to be an useful test. This keeps blocking the propagation of other packages from -proposed. This was most likely triggered by the kernel update from 3.18 to 3.19. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1429756/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1391560] Re: [themes] [design] Develop a strategy to keep fonts readable wherever we allow the user setting his own background image
I think we need a small drop shadow on the text on these screens. Can we use http://doc.qt.io/qt-5/qml-qtgraphicaleffects-dropshadow.html -- 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/1391560 Title: [themes] [design] Develop a strategy to keep fonts readable wherever we allow the user setting his own background image Status in Ubuntu UX bugs: Triaged Status in unity8 package in Ubuntu: Incomplete Bug description: As discussed with Olga, we need to develop a strategy on keeping the fonts readable when we allow the user to change the background. This is currently the case on the Greeter and the Lockscreens. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1391560/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1428087] Re: Need (some) Autopilot tests to run in different orientations
** Branch linked: lp:~ubuntu-sdk-team/ubuntu-ui- toolkit/orientationManual -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1428087 Title: Need (some) Autopilot tests to run in different orientations Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Bug description: We've had regressions in behavior and at least one crash recently due to the lack of testing under different orientations. Evidently even manual testing doesn't cover basic use cases judging by the nature of those issues - which may be in part due to development images receiving less QA attention, which makes it even more problematic. 1. We need ways to execute Autopilot tests under different orientations. 2. A test needs to be able to change orientation mid-way. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1428087/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1379379] Re: [SDK] Popover tip is not rendered properly
Saw some chatter about the new ubuntu shape last week - is this going to be landing? ** Changed in: ubuntu-ux Status: Triaged = Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1379379 Title: [SDK] Popover tip is not rendered properly Status in Ubuntu UX bugs: Fix Committed Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: The tip of the popover is not rendered properly - dropshadow is different - small horizontal line should not be there Actual appearance here in the SDK dropbox folder https://www.dropbox.com/sh/7fnssmbsyuc6c8l/AADiZ5i-pZbDcPaFBUKPmjaUa?dl=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1379379/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1350893] Re: [sdk] Allow header background customization per page
Makes sense to allow developers to change the header colour by page if someone really wants to ** Changed in: ubuntu-ux Status: Incomplete = Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1350893 Title: [sdk] Allow header background customization per page Status in Ubuntu UI Toolkit: Incomplete Status in Ubuntu UX bugs: Fix Committed Status in ubuntu-ui-toolkit package in Ubuntu: Incomplete Bug description: Each Page should have the ability to customize a few things about the look of the header, these changes should take affect when the page becomes the top page in a PageStack or the current tab in Tabs. headerColor: Set the background color of the Header headerGradient: Same as headerColor, only using a Gradient object instead of a single color headerImage: Set a background Image on the Header, resized to fit based on fillMode headerBorderImage: Same as headerImage, but using a BorderImage follow-up of this bug: https://bugs.launchpad.net/ubuntu-ui- toolkit/+bug/1315884 which I changed to only include header foreground color customization. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1350893/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1260978] Re: [Greeter] should be able to control music service while greeter locked
** Changed in: ubuntu-ux Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-sound in Ubuntu. https://bugs.launchpad.net/bugs/1260978 Title: [Greeter] should be able to control music service while greeter locked Status in Media Hub: Fix Released Status in Ubuntu UX bugs: Fix Released Status in indicator-sound package in Ubuntu: Opinion Status in ubuntu-music-app package in Ubuntu: Opinion Status in ubuntu-settings-components package in Ubuntu: Opinion Bug description: Not sure what component to file this against-- please reassign as desired. I use my phone to play music on random while I'm driving. This works great except when I want to advance or pause the song, where I have to go through the greeter first to access the player. This can either take my attention away from driving or I need to wait until the next stop light to advance the song. This is less of a concern when the greeter can just be swiped with one gesture, but is a big concern if you enable the passcode lock where you have to add the passcode to access the player. If the music is playing, the greeter should allow rudimentary manipulation of the music, eg, pause/play and forward/back. Other platforms seem to allow for this (eg android). To manage notifications about this bug go to: https://bugs.launchpad.net/media-hub/+bug/1260978/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1214352] Re: [SRU] GUINT32/64_SWAP_LE_BE macros do not enclose val argument in parentheses
** Attachment added: debdiff https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1214352/+attachment/4338685/+files/debdiff -- 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/1214352 Title: [SRU] GUINT32/64_SWAP_LE_BE macros do not enclose val argument in parentheses Status in LibreOffice Productivity Suite: Fix Released Status in The G Library - GLib: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Status in gvfs package in Ubuntu: New Status in libreoffice package in Ubuntu: New Bug description: [Impact] * This bug affects Glib-dependent packages, one of them is modern version of LibreOffice 4.x from PPA (https://launchpad.net/~libreoffice/+archive/ubuntu/ppa). * LibreOffice is very important software. Modern versions are more functional. Without them Ubuntu is nothing, it is a toy. [Test Case] 1. Place OpenDocument file (for example 'test.odt') on SMB/CIFS server (Samba on GNU/Linux, or from Windows). Make this share available for read-write. 2a.1. Open Nautilus, navigate it to 'smb://server_name/share_name/', wait the share to be mounted with GVFS. 2a.2. Double click on 'test.odt' 2b. Launch terminal and send 'libreoffice smb://server_name/share_name/test.odt' command. 3. Get error message from LibreOffice: The file 'test.odt' is corrupt and therefore cannot be opened. LibreOffice can try to repair the file. The corruption could be the result of document manipulation or of structural document damage due to data transmission. We recommend that you do not trust the content of the repaired document. Execution of macros is disabled for this document. Should LibreOffice repair the file? Yes No 4a. If I click 'Yes', the file is opened, but the title of the document is Untitled 1 (repaired document), not original name. 4b. If I click 'No', the dialog 'LibreOffice 4.4' is opened with text: The file 'test.odt' could not be repaired and therefore cannot be opened. OK I click 'OK' here, the next window LibreOffice 4.4.1.2 is opened with text: General Error. General input/output error. OK If I click OK here - no files are opened. While step 3 gvfsd-smb process eats CPU then terminates with error. This error is caused by bug in Glib (wrong type conversion in macros). [Regression Potential] * This functionality is essential. Please fix this bug. I (and you) can't tell Windows users, that they should not open office files from network shares in GNU/Linux. * The patch has two lines (https://git.gnome.org/browse/glib/commit/?id=255c65f83c1515a7e3fc4609b36e72acc08a79e4) and well-tested at upstream. * This bug may cause potential loss of data. [Other Info] * Corresponding links to LibO bugs are: https://bugs.freedesktop.org/show_bug.cgi?id=67527 https://bugs.documentfoundation.org/show_bug.cgi?id=72337 [Original description] On 12.04 LTS precise GUINT32/64_SWAP_LE_BE macros do not enclose val argument in parentheses, causing trouble down the stack in gvfs and LibreOffice (and possibly in lots of obscure bugs elsewhere). There is a patch available, but as this touches the header, it needs a full recompile of rdepends. see: https://lists.fedoraproject.org/pipermail/devel/2013-March/180302.html ff. for details To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1214352/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1214352] Re: [SRU] GUINT32/64_SWAP_LE_BE macros do not enclose val argument in parentheses
thanks Norbert, I missed that :) https://launchpad.net/~costamagnagianfranco/+archive/ubuntu /locutusofborg-ppa package with the fix above uploaded here, can you please test it? -- 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/1214352 Title: [SRU] GUINT32/64_SWAP_LE_BE macros do not enclose val argument in parentheses Status in LibreOffice Productivity Suite: Fix Released Status in The G Library - GLib: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Status in gvfs package in Ubuntu: New Status in libreoffice package in Ubuntu: New Bug description: [Impact] * This bug affects Glib-dependent packages, one of them is modern version of LibreOffice 4.x from PPA (https://launchpad.net/~libreoffice/+archive/ubuntu/ppa). * LibreOffice is very important software. Modern versions are more functional. Without them Ubuntu is nothing, it is a toy. [Test Case] 1. Place OpenDocument file (for example 'test.odt') on SMB/CIFS server (Samba on GNU/Linux, or from Windows). Make this share available for read-write. 2a.1. Open Nautilus, navigate it to 'smb://server_name/share_name/', wait the share to be mounted with GVFS. 2a.2. Double click on 'test.odt' 2b. Launch terminal and send 'libreoffice smb://server_name/share_name/test.odt' command. 3. Get error message from LibreOffice: The file 'test.odt' is corrupt and therefore cannot be opened. LibreOffice can try to repair the file. The corruption could be the result of document manipulation or of structural document damage due to data transmission. We recommend that you do not trust the content of the repaired document. Execution of macros is disabled for this document. Should LibreOffice repair the file? Yes No 4a. If I click 'Yes', the file is opened, but the title of the document is Untitled 1 (repaired document), not original name. 4b. If I click 'No', the dialog 'LibreOffice 4.4' is opened with text: The file 'test.odt' could not be repaired and therefore cannot be opened. OK I click 'OK' here, the next window LibreOffice 4.4.1.2 is opened with text: General Error. General input/output error. OK If I click OK here - no files are opened. While step 3 gvfsd-smb process eats CPU then terminates with error. This error is caused by bug in Glib (wrong type conversion in macros). [Regression Potential] * This functionality is essential. Please fix this bug. I (and you) can't tell Windows users, that they should not open office files from network shares in GNU/Linux. * The patch has two lines (https://git.gnome.org/browse/glib/commit/?id=255c65f83c1515a7e3fc4609b36e72acc08a79e4) and well-tested at upstream. * This bug may cause potential loss of data. [Other Info] * Corresponding links to LibO bugs are: https://bugs.freedesktop.org/show_bug.cgi?id=67527 https://bugs.documentfoundation.org/show_bug.cgi?id=72337 [Original description] On 12.04 LTS precise GUINT32/64_SWAP_LE_BE macros do not enclose val argument in parentheses, causing trouble down the stack in gvfs and LibreOffice (and possibly in lots of obscure bugs elsewhere). There is a patch available, but as this touches the header, it needs a full recompile of rdepends. see: https://lists.fedoraproject.org/pipermail/devel/2013-March/180302.html ff. for details To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1214352/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1316090] Re: Unable to drop/ place files and links on second screen in dual screen set up
Dear Christopher, Thanks for getting back to me on it. Short answer is yes, it is still an issue. It was gone for a while, and I suspect it had something to do with a cairo update we got. However, that is my impression, I'm no dev of course, but we all thought it funny that this update came and our bug seemed to be gone. However, after a while the bug returned, and I guess since a month or so, the issue seems to have worsened, where now all the desktop icons reset themselves to default position (starting complete left top, and lining additional icons below it) on every (re)boot on all 3 boxes we have here. I already have done some digging on it, and have seen there are more people who are experiencing this bug. As with the 1st bug I reported (no icon placement on right screen of dual screen setup - #1316090) it seems to be connected to the icons.screen0.XXX.rc files in ~/.config/xfce4/desktop. A fix seems to have been upstreamed but I haven't seen it yet (https://bugs.launchpad.net/ubuntu/+source/xfdesktop4/+bug/1335492, https://bugs.launchpad.net/ubuntu/+source/xfdesktop4/+bug/1307251). To come back to your specific question: I think we are fine for now just being patient, and see if the situation changed when the fixes from 1335492 and 1307251 come through. If that doesn't change a thing, it won't be a big deal for us. However, if we can help you guys with development and want me to send a diagnosis anyway, please just let me know. I'd be more than happy help with the great job you guys are doing (if I can ;-) Thanks again and greetz, Natalia Date: Mon, 2 Mar 2015 00:33:25 + From: christopher.m.penal...@gmail.com To: artistbr...@hotmail.com Subject: [Bug 1316090] Re: Unable to drop/ place files and links on second screen in dual screen set up Goth Queen, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com /daily-live/current/ . If it remains an issue, could you please run the following command in the development release from a Terminal as it will automatically gather and attach updated debug information to this report: apport-collect -p xorg 1316090 Please ensure you have xdiagnose installed, and that you click the Yes button for attaching additional debugging information. As well, given the information from the prior release is already available, testing a release prior to the development one would not be helpful. Thank you for your understanding. Helpful bug reporting tips: https://wiki.ubuntu.com/ReportingBugs ** Changed in: xorg (Ubuntu) Importance: Undecided = Low ** Changed in: xorg (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1316090 Title: Unable to drop/ place files and links on second screen in dual screen set up Status in xorg package in Ubuntu: Incomplete Bug description: After updating from Xubuntu 13.10 (amd64) to Xubuntu 14.04 LTS (amd64) I have encountered a bug with my dual screen set up. Running the XOrg screen driver (xserver-xorg-video-nouveau), it is possible to place/ drag and drop files and links on my left screen desktop. This is also the desktop that contains the system icons (e.g. removable drives, rubbish bin). However, I I try to drag and drop a file or link on the right screen desktop, it will not stick and fly back to its original location on the left screen. Additionally, I noticed that, when dragging the file over the troubled desktop, the placement squares don't show up. They do on the functioning left screen. Although I have a NVIDIA Corporation GK107 [GeForce GTX 650] Geforce I do run the XOrg driver since it gives me the best results with the software I'm using frequently. However, when I tested this during my initial install of Trusty, I noticed that I did not encounter this bug with the proprietary NVidia 304.117 driver (331.38 did not work for me at all). Running the NVidia 304.117 driver, it was possible to drag and drop/ place files and links on both screen desktops. Also the placement squares appeared on both screens when a file was dragged over it. After returning to the XOrg driver, the problem reoccurred, and placement on the right screen was again not possible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1316090/+subscriptions -- 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/1316090 Title: Unable to drop/ place files and links on second screen in dual screen set up Status in xorg
[Touch-packages] [Bug 1411140] Re: systemd-machine-id-commit.service fails on live system
Fix proposed at http://lists.freedesktop.org/archives/systemd- devel/2015-March/029163.html ** Changed in: systemd (Ubuntu) Status: Triaged = In Progress -- 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/1411140 Title: systemd-machine-id-commit.service fails on live system Status in systemd package in Ubuntu: In Progress Bug description: Boot the current live system with systemd: Go to gfxboot, select F6, press Esc twice, stay in gfxboot, and append init=/bin/systemd to the command line. The live system will come up, but degraded: ● systemd-machine-id-commit.service - Commit a transient machine-id on disk Loaded: loaded (/lib/systemd/system/systemd-machine-id-commit.service; static; vendor preset: enabled) Active: failed (Result: exit-code) since Thu 2015-01-15 08:08:47 UTC; 1min 57s ago Docs: man:systemd-machine-id-commit.service(8) Process: 871 ExecStart=/lib/systemd/systemd-machine-id-commit (code=exited, status=1/FAILURE) Main PID: 871 (code=exited, status=1/FAILURE) Jan 15 08:08:47 ubuntu systemd[1]: Starting Commit a transient machine-id on disk... Jan 15 08:08:47 ubuntu systemd[1]: systemd-machine-id-commit.service: main process exited, code=exited, status=1/FAILURE Jan 15 08:08:47 ubuntu systemd[1]: Failed to start Commit a transient machine-id on disk. Jan 15 08:08:47 ubuntu systemd[1]: Unit systemd-machine-id-commit.service entered failed state. Jan 15 08:08:47 ubuntu systemd[1]: systemd-machine-id-commit.service failed. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 218-3ubuntu3 ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2 Uname: Linux 3.18.0-9-generic x86_64 ApportVersion: 2.15.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jan 15 09:06:46 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2014-11-20 (55 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141119) MachineType: LENOVO 2324CTO ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.18.0-9-generic.efi.signed root=UUID=f86539b0-3a1b-4372-83b0-acdd029ade68 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/09/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET95WW (2.55 ) dmi.board.asset.tag: Not Available dmi.board.name: 2324CTO dmi.board.vendor: LENOVO dmi.board.version: 0B98401 Pro dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET95WW(2.55):bd07/09/2013:svnLENOVO:pn2324CTO:pvrThinkPadX230:rvnLENOVO:rn2324CTO:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2324CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1411140/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1419405] Re: indicator-location-service crashed with SIGABRT in internal::ToBackend::exit_module()
** Changed in: unity8-desktop-session (Ubuntu) Status: New = In Progress ** Changed in: unity8-desktop-session (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-location in Ubuntu. https://bugs.launchpad.net/bugs/1419405 Title: indicator-location-service crashed with SIGABRT in internal::ToBackend::exit_module() Status in indicator-location package in Ubuntu: Confirmed Status in platform-api package in Ubuntu: Confirmed Status in unity8-desktop-session package in Ubuntu: In Progress Bug description: :( ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: indicator-location 13.10.0+14.10.20141007-0ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-12.13-generic 3.18.4 Uname: Linux 3.18.0-12-generic x86_64 ApportVersion: 2.16-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Thu Feb 5 06:11:38 2015 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-location/indicator-location-service InstallationDate: Installed on 2014-10-13 (117 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141012) ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-location/indicator-location-service ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=it_IT.UTF-8 SHELL=/bin/false Signal: 6 SourcePackage: indicator-location StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libubuntu_application_api.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libubuntu_application_api.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libubuntu_application_api.so.2 ua_location_service_create_controller () from /usr/lib/x86_64-linux-gnu/libubuntu_application_api.so.2 UbuntuAppLocController::UbuntuAppLocController() () SystemImageInfo: current build number: 0 device name: channel: daily last update: Unknown Title: indicator-location-service crashed with SIGABRT in ua_location_service_create_controller() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-location/+bug/1419405/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1428184] Re: Invisible mouse pointer after resume from suspend
Hi, I'm getting this on Xubuntu 14.04 on a Thinkpad T60p.. Mouse works, cursor not visible after closing the lid for a while. -- 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/1428184 Title: Invisible mouse pointer after resume from suspend Status in xorg package in Ubuntu: Incomplete Bug description: I'm using a Samsung NP305U1A-A05CO laptop. After the computer is suspended, either by closing the lid, choosing the option on the menu or by itself after the defined time, and then when I wake the computer the mouse pointer is invisible, however the hardware itself is working as mouse position and clicks continue working, only the pointer is invisible. WORKAROUND: If I switch to a console with Alt+Shit+F1 and switch back to X with Alt+Shift+F7 the mouse pointer appears and is back to normal. WORKAROUND: After installing fglrx 14.50.2 proprietary AMD driver (doing the modification explained in http://askubuntu.com/a/543836/378463 to avoid ocl-icd-libopencl1/wine conflict) including the Catalyst Control Center, the problem is resolved and now I can suspend and resume the computer and the mouse pointer is visible after wake up as expected. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-46.76-generic 3.13.11-ckt15 Uname: Linux 3.13.0-46-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 Date: Wed Mar 4 10:08:23 2015 InstallationDate: Installed on 2015-02-12 (20 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) 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/1428184/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1424059] Re: libosmesa6 conflicts with libglapi-mesa-lts-utopic
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mesa (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1424059
Title:
libosmesa6 conflicts with libglapi-mesa-lts-utopic
Status in mesa package in Ubuntu:
Confirmed
Status in mesa-lts-utopic package in Ubuntu:
Confirmed
Bug description:
[Description]
libosmesa6 10.1.3-0ubuntu0.3 amd64 can't be installed because it depends on
libglapi-mesa (= 10.1.3-0ubuntu0.3), but libglapi-mesa-lts-utopic
10.3.2-0ubuntu1~trusty2 amd64 is '10.3.2-0ubuntu1' not '10.1.3-0ubuntu0.3'.
[Test Case]
sudo aptitude install libosmesa6
The following NEW packages will be installed:
libglapi-mesa{a} libosmesa6
0 packages upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 1,009 kB of archives. After unpacking 3,682 kB will be used.
The following packages have unmet dependencies:
xserver-xorg-lts-utopic : Conflicts: libglapi-mesa (= 0~) but
10.1.3-0ubuntu0.3 is to be installed.
libglapi-mesa-lts-utopic : Conflicts: libglapi-mesa but 10.1.3-0ubuntu0.3 is
to be installed.
[Possible solution]
Include utopic's libosmesa(-dev) in the LTS enablement stack, so versions
match.
[Reverse dependencies]
libosmesa6-dev
desmume
crossover
wine recommends libosmesa6
...
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: libglapi-mesa-lts-utopic 10.3.2-0ubuntu1~trusty2
ProcVersionSignature: Ubuntu 3.16.0-31.41~14.04.1-generic 3.16.7-ckt5
Uname: Linux 3.16.0-31-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.7
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Feb 20 15:45:52 2015
Dependencies:
gcc-4.9-base 4.9.1-0ubuntu1
libc6 2.19-0ubuntu6.5
libgcc1 1:4.9.1-0ubuntu1
multiarch-support 2.19-0ubuntu6.5
InstallationDate: Installed on 2015-02-08 (12 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64
(20150203.2)
SourcePackage: mesa-lts-utopic
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1424059/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1428277] Re: Icon in notification center too small
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-settings-components (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings-components in Ubuntu. https://bugs.launchpad.net/bugs/1428277 Title: Icon in notification center too small Status in Libqtelegram - a qt library to access telegram.: Invalid Status in Ubuntu UX bugs: New Status in ubuntu-settings-components package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: See image attached. The tappable telegram icon is somewhat small and is not trivial to tap, or at least I'm not being able to tap it in a way it works in a single tap. To manage notifications about this bug go to: https://bugs.launchpad.net/libqtelegram/+bug/1428277/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1428277] Re: Icon in notification center too small
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity8 (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings-components in Ubuntu. https://bugs.launchpad.net/bugs/1428277 Title: Icon in notification center too small Status in Libqtelegram - a qt library to access telegram.: Invalid Status in Ubuntu UX bugs: New Status in ubuntu-settings-components package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: See image attached. The tappable telegram icon is somewhat small and is not trivial to tap, or at least I'm not being able to tap it in a way it works in a single tap. To manage notifications about this bug go to: https://bugs.launchpad.net/libqtelegram/+bug/1428277/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1428277] Re: Icon in notification may be too small
** Also affects: ubuntu-ux Importance: Undecided Status: New ** Summary changed: - Icon in notification may be too small + Icon in notification center too small ** Description changed: - See image attached. Icon is somewhat small and is not trivial to tap, or - at least I'm not being able to tap it in a way it works in a single tap. + See image attached. The tappable telegram icon is somewhat small and is + not trivial to tap, or at least I'm not being able to tap it in a way it + works in a single tap. ** Also affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Changed in: libqtelegram Status: New = Invalid ** Also affects: ubuntu-settings-components (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1428277 Title: Icon in notification center too small Status in Libqtelegram - a qt library to access telegram.: Invalid Status in Ubuntu UX bugs: New Status in ubuntu-settings-components package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: See image attached. The tappable telegram icon is somewhat small and is not trivial to tap, or at least I'm not being able to tap it in a way it works in a single tap. To manage notifications about this bug go to: https://bugs.launchpad.net/libqtelegram/+bug/1428277/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1408643] Re: Header divider is invisible on very dark backgrounds
** Changed in: ubuntu-ux Status: Triaged = Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1408643 Title: Header divider is invisible on very dark backgrounds Status in Ubuntu UX bugs: Fix Committed Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: The color for the header divider is calculated by Qt.darker(backgroundColor). If backgroundColor is already very dark or black, this leads to an invisible header divider. Probably it needs to check for a certain darkness threshold and use Qt.lighter(backgroundColor) instead. Ideally the app developer could also override the color for the divider so that it can match the foregroundColor, meaning the divider would be the same color as the text and icons inside the header. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1408643/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1429784] Re: Battery level stuck overnight
settings only displays the recording done by upower, that's an upower or kernel issue, not a settings one ** Package changed: ubuntu-system-settings (Ubuntu) = upower (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1429784 Title: Battery level stuck overnight Status in upower package in Ubuntu: New Bug description: Test case. - Leave the device locked overnight. - On the next morning, go to System Settings Battery. Expected result. - Battery should report a lower level. Actual result. - A plain graph is shown. current build number: 135 device name: krillin channel: ubuntu-touch/devel-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1429784/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1424588] Re: unable to center popover in caller
These designs appear to assume the context menu component we don't yet have, which would have this different positioning behavior. ** Summary changed: - unable to center popover in caller + Need a context menu component ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1424588 Title: Need a context menu component Status in Ubuntu UX bugs: Fix Committed Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: The design for the browser app’s contextual menu requires the popover to be centered inside its caller (the webview). See https://docs.google.com/a/canonical.com/presentation/d/1woHjO8K4iqyVZZlfQ4BXL0DhYbwkEmZ7wvcUhYzHDRk/edit#slide=id.g34608d763_079 for reference. The popover is opened using PopupUtils.open(…). I’ve tried two different approaches to achieve that, but none actually works: - passing the webview as the caller - passing no caller parameter at all In both cases, the popover is horizontally centered, but it’s anchored to the top of the scene. I’m attaching a standalone example that demonstrates the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1424588/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1267059] Re: Unattended-Upgrade::Remove-Unused-Dependencies does not work
Note that situation #1089195 is another possible outcome of this bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1267059 Title: Unattended-Upgrade::Remove-Unused-Dependencies does not work Status in unattended-upgrades package in Ubuntu: Triaged Bug description: I have a system that runs unattended-upgrades just fine. Now i want to automate removal of old kernels and kernel header packages that are accumulating otherwise. So i set 'Unattended-Upgrade::Remove-Unused- Dependencies true;'. But it doesn't work. Details: Lots of stuff pending autoremoval: $ apt-get --assume-no autoremove Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED linux-headers-3.2.0-38 linux-headers-3.2.0-38-generic linux-headers-3.2.0-39 linux-headers-3.2.0-39-generic linux-headers-3.2.0-40 linux-headers-3.2.0-40-generic linux-headers-3.2.0-41 linux-headers-3.2.0-41-generic linux-headers-3.2.0-43 linux-headers-3.2.0-43-generic linux-headers-3.2.0-44 linux-headers-3.2.0-44-generic linux-headers-3.2.0-45 linux-headers-3.2.0-45-generic linux-headers-3.2.0-48 linux-headers-3.2.0-48-generic linux-headers-3.2.0-51 linux-headers-3.2.0-51-generic linux-headers-3.2.0-52 linux-headers-3.2.0-52-generic linux-headers-3.2.0-53 linux-headers-3.2.0-53-generic linux-headers-3.2.0-54 linux-headers-3.2.0-54-generic linux-headers-3.2.0-55 linux-headers-3.2.0-55-generic linux-headers-3.2.0-56 linux-headers-3.2.0-56-generic linux-image-3.2.0-39-generic linux-image-3.2.0-40-generic linux-image-3.2.0-41-generic linux-image-3.2.0-43-generic linux-image-3.2.0-44-generic linux-image-3.2.0-45-generic linux-image-3.2.0-48-generic linux-image-3.2.0-51-generic linux- image-3.2.0-52-generic linux-image-3.2.0-53-generic linux-image-3.2.0-54-generic linux-image-3.2.0-55-generic linux-image-3.2.0-56-generic 0 upgraded, 0 newly installed, 41 to remove and 13 not upgraded. After this operation, 2,893 MB disk space will be freed. Do you want to continue [Y/n]? N Abort. Note that the majority of these packages have been installed by unattended-upgrades from precise-security. According to the comments within/etc/apt/apt.conf.d/50unattended- upgrades, this should automate autoremoval: // Do automatic removal of new unused dependencies after the upgrade // (equivalent to apt-get autoremove) Unattended-Upgrade::Remove-Unused-Dependencies true; but nothing happens (note the line Packages that are auto removed: '' : $ unattended-upgrades --debug --dry-run Initial blacklisted packages: Starting unattended upgrades script Allowed origins are: ['o=Ubuntu,a=precise-security'] adjusting candidate version: 'Version: package:'accountsservice' version:'0.6.15-2ubuntu9.6.1'' adjusting candidate version: 'Version: package:'libaccountsservice0' version:'0.6.15-2ubuntu9.6.1'' adjusting candidate version: 'Version: package:'libdrm-intel1' version:'2.4.43-0ubuntu0.0.3'' adjusting candidate version: 'Version: package:'libdrm-nouveau1a' version:'2.4.43-0ubuntu0.0.3'' adjusting candidate version: 'Version: package:'libdrm-radeon1' version:'2.4.43-0ubuntu0.0.3'' adjusting candidate version: 'Version: package:'libdrm2' version:'2.4.43-0ubuntu0.0.3'' Checking: bc ([Origin component:'main' archive:'precise-updates' origin:'Ubuntu' label:'Ubuntu' site:'gb.archive.ubuntu.com' isTrusted:True]) Checking: grub-common ([Origin component:'main' archive:'precise-updates' origin:'Ubuntu' label:'Ubuntu' site:'gb.archive.ubuntu.com' isTrusted:True]) Checking: grub-pc ([Origin component:'main' archive:'precise-updates' origin:'Ubuntu' label:'Ubuntu' site:'gb.archive.ubuntu.com' isTrusted:True]) Checking: grub-pc-bin ([Origin component:'main' archive:'precise-updates' origin:'Ubuntu' label:'Ubuntu' site:'gb.archive.ubuntu.com' isTrusted:True]) Checking: grub2-common ([Origin component:'main' archive:'precise-updates' origin:'Ubuntu' label:'Ubuntu' site:'gb.archive.ubuntu.com' isTrusted:True]) Checking: iproute ([Origin component:'main' archive:'precise-updates' origin:'Ubuntu' label:'Ubuntu' site:'gb.archive.ubuntu.com' isTrusted:True]) Checking: landscape-common ([Origin component:'main' archive:'precise-updates' origin:'Ubuntu' label:'Ubuntu' site:'gb.archive.ubuntu.com' isTrusted:True]) pkgs that look like they should be upgraded: Fetched 0 B in 0s (0 B/s) blacklist: [] Packages that are auto removed: '' InstCount=0 DelCount=0 BrokenCout=0 No packages found that can be upgraded unattended I am using unattended-upgrades-0.76ubuntu1 on Ubuntu 12.04.3 LTS To manage
[Touch-packages] [Bug 1429838] Re: Some (internal) test programs should be split up and filenames are not consistent
** Summary changed: - Some (internal) test programs have too much messy code and filenames are not consistent + Some (internal) test programs should be split up and filenames are not consistent -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1429838 Title: Some (internal) test programs should be split up and filenames are not consistent Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Bug description: The various tests in tests/resources/navigation/header.html should be put in separate files to make them easier to read and maintain. Also a the filenames in tests/resources/* and some unit tests are not consistent (use different capitalizations, and/or underscores in filenames). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1429838/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1419405] Re: indicator-location-service crashed with SIGABRT in internal::ToBackend::exit_module()
** Branch linked: lp:~ricmm/platform-api/no-abort-default-dummy ** Changed in: platform-api (Ubuntu) Assignee: (unassigned) = Ricardo Mendoza (ricmm) ** Changed in: unity8-desktop-session (Ubuntu) Assignee: (unassigned) = Ricardo Mendoza (ricmm) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-location in Ubuntu. https://bugs.launchpad.net/bugs/1419405 Title: indicator-location-service crashed with SIGABRT in internal::ToBackend::exit_module() Status in indicator-location package in Ubuntu: Confirmed Status in platform-api package in Ubuntu: Confirmed Status in unity8-desktop-session package in Ubuntu: New Bug description: :( ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: indicator-location 13.10.0+14.10.20141007-0ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-12.13-generic 3.18.4 Uname: Linux 3.18.0-12-generic x86_64 ApportVersion: 2.16-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Thu Feb 5 06:11:38 2015 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-location/indicator-location-service InstallationDate: Installed on 2014-10-13 (117 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141012) ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-location/indicator-location-service ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=it_IT.UTF-8 SHELL=/bin/false Signal: 6 SourcePackage: indicator-location StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libubuntu_application_api.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libubuntu_application_api.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libubuntu_application_api.so.2 ua_location_service_create_controller () from /usr/lib/x86_64-linux-gnu/libubuntu_application_api.so.2 UbuntuAppLocController::UbuntuAppLocController() () SystemImageInfo: current build number: 0 device name: channel: daily last update: Unknown Title: indicator-location-service crashed with SIGABRT in ua_location_service_create_controller() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-location/+bug/1419405/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 913434] Re: ImageIO crashes (core dumped) while reading many image files
** Also affects: lcms2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lcms2 in Ubuntu. https://bugs.launchpad.net/bugs/913434 Title: ImageIO crashes (core dumped) while reading many image files Status in OpenJDK: Invalid Status in lcms2 package in Ubuntu: New Status in openjdk-7 package in Ubuntu: Confirmed Bug description: Code that uses ImageIO.read() to read many image files (on my system: 270 files, totalling 522.9 MiB) crashes the JVM. ~~~ My system information: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 11.10 Release: 11.10 Codename: oneiric $ uname -a Linux dowah 3.0.0-14-generic #23-Ubuntu SMP Mon Nov 21 20:28:43 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux $ javac -version javac 1.7.0_147 $ java -version java version 1.7.0_147-icedtea ~~~ To reproduce the error: $ javac BugIIO.java $ ulimit -c unlimited # to enable core dump $ java BugIIO ~~~ Terminal output that signifies the error: # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x7fb5babe31f8, pid=4978, tid=140418842154752 # # JRE version: 7.0_147-b147 # Java VM: OpenJDK 64-Bit Server VM (21.0-b17 mixed mode linux-amd64 compressed oops) # Derivative: IcedTea7 2.0 # Distribution: Ubuntu 11.10, package 7~b147-2.0-0ubuntu0.11.10.1 # Problematic frame: # C [liblcms2.so.2+0x121f8] cmsSaveProfileToIOhandler+0x38 # # Core dump written. Default location: /home/joshua/core or core.4978 # # An error report file with more information is saved as: # /home/joshua/hs_err_pid4978.log # # If you would like to submit a bug report, please include # instructions on how to reproduce the bug and visit: # https://bugs.launchpad.net/ubuntu/+source/openjdk-7/ # Dibatalkan (core didump) ~~~ PS When I tried to compile BugIIO.java on openjdk-6 and run it on openjdk-6, the program finishes normally (no crash). To clarify: 1. This bug affect OpenJDK 7 (7~b147-2.0-0ubuntu0.11.10.1) (tested on oneiric). 2. This bug does *not* affect OpenJDK 6 (6b23~pre11-0ubuntu1.11.10) (tested on oneiric). To manage notifications about this bug go to: https://bugs.launchpad.net/openjdk/+bug/913434/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1429354] Re: Systemd takes very long to boot with error in swap mounting
** Attachment added: udevadm https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1429354/+attachment/4338780/+files/udevadm -- 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/1429354 Title: Systemd takes very long to boot with error in swap mounting Status in systemd package in Ubuntu: Incomplete Bug description: My system boots almost instantly with upstart. Today i tried booting with systemd via the additional grub option. However, with systemd it takes really long to boot but – so long that i forced a reboot once because i thought i got stuck. Looking in to boot journal, i found the following error concerning the swap: Mär 07 09:28:00 darw1n systemd[1]: dev-sda3.swap swap process exited, code=exited status=255 Mär 07 09:28:00 darw1n systemd[1]: Failed to activate swap Swap Partition. Mär 07 09:28:00 darw1n systemd[1]: Unit dev-sda3.swap entered failed state. And this concerning nvidia-persistenced Mär 07 09:28:00 darw1n nvidia-persistenced[433]: Started (433) Mär 07 09:28:00 darw1n nvidia-persistenced[433]: Failed to query NVIDIA devices. Please ensure that the NVIDIA device files (/dev/nvidia*) exist, and that user 116 has read and write permissions for thos Mär 07 09:28:00 darw1n nvidia-persistenced[433]: The daemon no longer has permission to remove its runtime data directory /var/run/nvidia-persistenced I checked that /dev/sda3 exists and is a swap partition and i check for the /dev/nvidia files: $ ls -Alst /dev/nvidia0 0 crw-rw-rw- 1 root root 195, 0 Mär 7 09:29 /dev/nvidia0 However, the interesting part is here, where nothing seems to happen for a minute: (see the timestamps): Mär 07 09:28:01 darw1n systemd[1]: Started LSB: AppArmor initialization. Mär 07 09:28:31 darw1n systemd-journal[234]: Forwarding to syslog missed 99 messages. Mär 07 09:29:29 darw1n systemd[1]: Job dev-disk-by\x2duuid-0b93a0a2\x2d115c\x2d4a45\x2d9075\x2d5f31454c5a41.device/start timed out. Mär 07 09:29:29 darw1n systemd-journal[234]: Forwarding to syslog missed 1 messages. Mär 07 09:29:29 darw1n systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-0b93a0a2\x2d115c\x2d4a45\x2d9075\x2d5f31454c5a41.device. Mär 07 09:29:29 darw1n systemd[1]: Dependency failed for Cryptography Setup for cryptswap1. Mär 07 09:29:29 darw1n systemd[1]: Dependency failed for dev-mapper-cryptswap1.device. Mär 07 09:29:29 darw1n systemd[1]: Dependency failed for /dev/mapper/cryptswap1. Mär 07 09:29:29 darw1n systemd[1]: Dependency failed for Swap. Mär 07 09:29:29 darw1n systemd[1]: Job swap.target/start failed with result 'dependency'. Mär 07 09:29:29 darw1n systemd[1]: Job dev-mapper-cryptswap1.swap/start failed with result 'dependency'. Mär 07 09:29:29 darw1n systemd[1]: Job dev-mapper-cryptswap1.device/start failed with result 'dependency'. Mär 07 09:29:29 darw1n systemd[1]: Dependency failed for Encrypted Volumes. Mär 07 09:29:29 darw1n systemd[1]: Job cryptsetup.target/start failed with result 'dependency'. Mär 07 09:29:29 darw1n systemd[1]: Job systemd-cryptsetup@cryptswap1.service/start failed with result 'dependency'. Mär 07 09:29:29 darw1n systemd[1]: Job dev-disk-by\x2duuid-0b93a0a2\x2d115c\x2d4a45\x2d9075\x2d5f31454c5a41.device/start failed with result 'timeout'. Mär 07 09:29:29 darw1n systemd[1]: Reached target System Initializatio ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-4ubuntu3 ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 7 09:31:09 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-02-05 (29 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic.efi.signed root=UUID=63ea7e2a-9b00-4298-b58c-7a68c2775a87 ro vt.handoff=7 init=/lib/systemd/systemd systemd.debugshell SourcePackage: systemd UpgradeStatus: Upgraded to vivid on 2015-02-23 (11 days ago) dmi.bios.date: 12/17/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.60 dmi.board.name: H97 Performance 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.60:bd12/17/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH97Performance: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. To manage
[Touch-packages] [Bug 1429354] Re: Systemd takes very long to boot with error in swap mounting
How did you install this system? I selected the default encrypted on LVM option in ubiquity, but this creates a single encrypted PV with a single VG ubuntu that has two LVs, one for root and one for swap: fstab: /dev/mapper/ubuntu--vg-swap_1 noneswapsw 0 0 crypttab: vda5_crypt UUID=66e69938-a18e-4ad3-8a43-93f6a53d68c8 none luks,discard That has been Ubuntu's standard LVM+cryptsetup layout forever, so apparently you did something else to get the randomized cryptswap partitions? -- 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/1429354 Title: Systemd takes very long to boot with error in swap mounting Status in systemd package in Ubuntu: Incomplete Bug description: My system boots almost instantly with upstart. Today i tried booting with systemd via the additional grub option. However, with systemd it takes really long to boot but – so long that i forced a reboot once because i thought i got stuck. Looking in to boot journal, i found the following error concerning the swap: Mär 07 09:28:00 darw1n systemd[1]: dev-sda3.swap swap process exited, code=exited status=255 Mär 07 09:28:00 darw1n systemd[1]: Failed to activate swap Swap Partition. Mär 07 09:28:00 darw1n systemd[1]: Unit dev-sda3.swap entered failed state. And this concerning nvidia-persistenced Mär 07 09:28:00 darw1n nvidia-persistenced[433]: Started (433) Mär 07 09:28:00 darw1n nvidia-persistenced[433]: Failed to query NVIDIA devices. Please ensure that the NVIDIA device files (/dev/nvidia*) exist, and that user 116 has read and write permissions for thos Mär 07 09:28:00 darw1n nvidia-persistenced[433]: The daemon no longer has permission to remove its runtime data directory /var/run/nvidia-persistenced I checked that /dev/sda3 exists and is a swap partition and i check for the /dev/nvidia files: $ ls -Alst /dev/nvidia0 0 crw-rw-rw- 1 root root 195, 0 Mär 7 09:29 /dev/nvidia0 However, the interesting part is here, where nothing seems to happen for a minute: (see the timestamps): Mär 07 09:28:01 darw1n systemd[1]: Started LSB: AppArmor initialization. Mär 07 09:28:31 darw1n systemd-journal[234]: Forwarding to syslog missed 99 messages. Mär 07 09:29:29 darw1n systemd[1]: Job dev-disk-by\x2duuid-0b93a0a2\x2d115c\x2d4a45\x2d9075\x2d5f31454c5a41.device/start timed out. Mär 07 09:29:29 darw1n systemd-journal[234]: Forwarding to syslog missed 1 messages. Mär 07 09:29:29 darw1n systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-0b93a0a2\x2d115c\x2d4a45\x2d9075\x2d5f31454c5a41.device. Mär 07 09:29:29 darw1n systemd[1]: Dependency failed for Cryptography Setup for cryptswap1. Mär 07 09:29:29 darw1n systemd[1]: Dependency failed for dev-mapper-cryptswap1.device. Mär 07 09:29:29 darw1n systemd[1]: Dependency failed for /dev/mapper/cryptswap1. Mär 07 09:29:29 darw1n systemd[1]: Dependency failed for Swap. Mär 07 09:29:29 darw1n systemd[1]: Job swap.target/start failed with result 'dependency'. Mär 07 09:29:29 darw1n systemd[1]: Job dev-mapper-cryptswap1.swap/start failed with result 'dependency'. Mär 07 09:29:29 darw1n systemd[1]: Job dev-mapper-cryptswap1.device/start failed with result 'dependency'. Mär 07 09:29:29 darw1n systemd[1]: Dependency failed for Encrypted Volumes. Mär 07 09:29:29 darw1n systemd[1]: Job cryptsetup.target/start failed with result 'dependency'. Mär 07 09:29:29 darw1n systemd[1]: Job systemd-cryptsetup@cryptswap1.service/start failed with result 'dependency'. Mär 07 09:29:29 darw1n systemd[1]: Job dev-disk-by\x2duuid-0b93a0a2\x2d115c\x2d4a45\x2d9075\x2d5f31454c5a41.device/start failed with result 'timeout'. Mär 07 09:29:29 darw1n systemd[1]: Reached target System Initializatio ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-4ubuntu3 ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 7 09:31:09 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-02-05 (29 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic.efi.signed root=UUID=63ea7e2a-9b00-4298-b58c-7a68c2775a87 ro vt.handoff=7 init=/lib/systemd/systemd systemd.debugshell SourcePackage: systemd UpgradeStatus: Upgraded to vivid on 2015-02-23 (11 days ago) dmi.bios.date: 12/17/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.60 dmi.board.name: H97 Performance 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.
[Touch-packages] [Bug 1425593] Re: trivial app fails to appear in shell and crashes it on close
** Changed in: unity8 (Ubuntu)
Assignee: (unassigned) = Albert Astals Cid (aacid)
--
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/1425593
Title:
trivial app fails to appear in shell and crashes it on close
Status in Qt integration with the Mir display server:
Confirmed
Status in unity8 package in Ubuntu:
New
Bug description:
Take this code:
#include QApplication
#include QWidget
int main(int argc, char *argv[])
{
QApplication app(argc, argv);
QWidget *w = new QWidget();
w-showMaximized();
return app.exec();
}
and this Qt pro file:
QT += core gui widgets
TARGET = simple-qwidget
TEMPLATE = app
SOURCES += main.cpp
and build on the device. On unity8 run with:
./simple-qwidget --desktop_file_hint=/usr/share/applications
/mediaplayer-app.desktop
You'll see the splash screen appear, but you'll never see a frame from the
app.
When I Ctrl+C the app, unity8 crashes
To manage notifications about this bug go to:
https://bugs.launchpad.net/qtmir/+bug/1425593/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1429784] [NEW] Battery level stuck overnight
You have been subscribed to a public bug: Test case. - Leave the device locked overnight. - On the next morning, go to System Settings Battery. Expected result. - Battery should report a lower level. Actual result. - A plain graph is shown. current build number: 135 device name: krillin channel: ubuntu-touch/devel-proposed ** Affects: upower (Ubuntu) Importance: Undecided Status: New ** Tags: qa-exploratory touch -- Battery level stuck overnight https://bugs.launchpad.net/bugs/1429784 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower 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 1350891] Re: [Scopes] Suru Background should scroll
The dash background remains fixed and not scrolling with the content ** Changed in: ubuntu-ux Importance: High = Low -- 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/1350891 Title: [Scopes] Suru Background should scroll Status in the base for Ubuntu mobile products: Confirmed Status in Clock application for Ubuntu devices: Triaged Status in Ubuntu UX bugs: Triaged Status in unity8 package in Ubuntu: In Progress Status in unity8 package in Ubuntu RTM: Triaged Bug description: On the dash, the Suru paper folds stays fixed at the bottom, while it should rather scroll away. We should also 'tile' the background, so the paper fold is displayed again after scrolling a certain amount of vertical space. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1350891/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1429354] Re: Systemd takes very long to boot with error in swap mounting
I have the same issue. Attaching my fstab and crypttab. ** Attachment added: fstab https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1429354/+attachment/4338777/+files/fstab -- 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/1429354 Title: Systemd takes very long to boot with error in swap mounting Status in systemd package in Ubuntu: Incomplete Bug description: My system boots almost instantly with upstart. Today i tried booting with systemd via the additional grub option. However, with systemd it takes really long to boot but – so long that i forced a reboot once because i thought i got stuck. Looking in to boot journal, i found the following error concerning the swap: Mär 07 09:28:00 darw1n systemd[1]: dev-sda3.swap swap process exited, code=exited status=255 Mär 07 09:28:00 darw1n systemd[1]: Failed to activate swap Swap Partition. Mär 07 09:28:00 darw1n systemd[1]: Unit dev-sda3.swap entered failed state. And this concerning nvidia-persistenced Mär 07 09:28:00 darw1n nvidia-persistenced[433]: Started (433) Mär 07 09:28:00 darw1n nvidia-persistenced[433]: Failed to query NVIDIA devices. Please ensure that the NVIDIA device files (/dev/nvidia*) exist, and that user 116 has read and write permissions for thos Mär 07 09:28:00 darw1n nvidia-persistenced[433]: The daemon no longer has permission to remove its runtime data directory /var/run/nvidia-persistenced I checked that /dev/sda3 exists and is a swap partition and i check for the /dev/nvidia files: $ ls -Alst /dev/nvidia0 0 crw-rw-rw- 1 root root 195, 0 Mär 7 09:29 /dev/nvidia0 However, the interesting part is here, where nothing seems to happen for a minute: (see the timestamps): Mär 07 09:28:01 darw1n systemd[1]: Started LSB: AppArmor initialization. Mär 07 09:28:31 darw1n systemd-journal[234]: Forwarding to syslog missed 99 messages. Mär 07 09:29:29 darw1n systemd[1]: Job dev-disk-by\x2duuid-0b93a0a2\x2d115c\x2d4a45\x2d9075\x2d5f31454c5a41.device/start timed out. Mär 07 09:29:29 darw1n systemd-journal[234]: Forwarding to syslog missed 1 messages. Mär 07 09:29:29 darw1n systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-0b93a0a2\x2d115c\x2d4a45\x2d9075\x2d5f31454c5a41.device. Mär 07 09:29:29 darw1n systemd[1]: Dependency failed for Cryptography Setup for cryptswap1. Mär 07 09:29:29 darw1n systemd[1]: Dependency failed for dev-mapper-cryptswap1.device. Mär 07 09:29:29 darw1n systemd[1]: Dependency failed for /dev/mapper/cryptswap1. Mär 07 09:29:29 darw1n systemd[1]: Dependency failed for Swap. Mär 07 09:29:29 darw1n systemd[1]: Job swap.target/start failed with result 'dependency'. Mär 07 09:29:29 darw1n systemd[1]: Job dev-mapper-cryptswap1.swap/start failed with result 'dependency'. Mär 07 09:29:29 darw1n systemd[1]: Job dev-mapper-cryptswap1.device/start failed with result 'dependency'. Mär 07 09:29:29 darw1n systemd[1]: Dependency failed for Encrypted Volumes. Mär 07 09:29:29 darw1n systemd[1]: Job cryptsetup.target/start failed with result 'dependency'. Mär 07 09:29:29 darw1n systemd[1]: Job systemd-cryptsetup@cryptswap1.service/start failed with result 'dependency'. Mär 07 09:29:29 darw1n systemd[1]: Job dev-disk-by\x2duuid-0b93a0a2\x2d115c\x2d4a45\x2d9075\x2d5f31454c5a41.device/start failed with result 'timeout'. Mär 07 09:29:29 darw1n systemd[1]: Reached target System Initializatio ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-4ubuntu3 ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 7 09:31:09 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-02-05 (29 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic.efi.signed root=UUID=63ea7e2a-9b00-4298-b58c-7a68c2775a87 ro vt.handoff=7 init=/lib/systemd/systemd systemd.debugshell SourcePackage: systemd UpgradeStatus: Upgraded to vivid on 2015-02-23 (11 days ago) dmi.bios.date: 12/17/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.60 dmi.board.name: H97 Performance 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.60:bd12/17/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH97Performance: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.
[Touch-packages] [Bug 1429354] Re: Systemd takes very long to boot with error in swap mounting
** Attachment added: crypttab https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1429354/+attachment/4338779/+files/crypttab -- 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/1429354 Title: Systemd takes very long to boot with error in swap mounting Status in systemd package in Ubuntu: Incomplete Bug description: My system boots almost instantly with upstart. Today i tried booting with systemd via the additional grub option. However, with systemd it takes really long to boot but – so long that i forced a reboot once because i thought i got stuck. Looking in to boot journal, i found the following error concerning the swap: Mär 07 09:28:00 darw1n systemd[1]: dev-sda3.swap swap process exited, code=exited status=255 Mär 07 09:28:00 darw1n systemd[1]: Failed to activate swap Swap Partition. Mär 07 09:28:00 darw1n systemd[1]: Unit dev-sda3.swap entered failed state. And this concerning nvidia-persistenced Mär 07 09:28:00 darw1n nvidia-persistenced[433]: Started (433) Mär 07 09:28:00 darw1n nvidia-persistenced[433]: Failed to query NVIDIA devices. Please ensure that the NVIDIA device files (/dev/nvidia*) exist, and that user 116 has read and write permissions for thos Mär 07 09:28:00 darw1n nvidia-persistenced[433]: The daemon no longer has permission to remove its runtime data directory /var/run/nvidia-persistenced I checked that /dev/sda3 exists and is a swap partition and i check for the /dev/nvidia files: $ ls -Alst /dev/nvidia0 0 crw-rw-rw- 1 root root 195, 0 Mär 7 09:29 /dev/nvidia0 However, the interesting part is here, where nothing seems to happen for a minute: (see the timestamps): Mär 07 09:28:01 darw1n systemd[1]: Started LSB: AppArmor initialization. Mär 07 09:28:31 darw1n systemd-journal[234]: Forwarding to syslog missed 99 messages. Mär 07 09:29:29 darw1n systemd[1]: Job dev-disk-by\x2duuid-0b93a0a2\x2d115c\x2d4a45\x2d9075\x2d5f31454c5a41.device/start timed out. Mär 07 09:29:29 darw1n systemd-journal[234]: Forwarding to syslog missed 1 messages. Mär 07 09:29:29 darw1n systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-0b93a0a2\x2d115c\x2d4a45\x2d9075\x2d5f31454c5a41.device. Mär 07 09:29:29 darw1n systemd[1]: Dependency failed for Cryptography Setup for cryptswap1. Mär 07 09:29:29 darw1n systemd[1]: Dependency failed for dev-mapper-cryptswap1.device. Mär 07 09:29:29 darw1n systemd[1]: Dependency failed for /dev/mapper/cryptswap1. Mär 07 09:29:29 darw1n systemd[1]: Dependency failed for Swap. Mär 07 09:29:29 darw1n systemd[1]: Job swap.target/start failed with result 'dependency'. Mär 07 09:29:29 darw1n systemd[1]: Job dev-mapper-cryptswap1.swap/start failed with result 'dependency'. Mär 07 09:29:29 darw1n systemd[1]: Job dev-mapper-cryptswap1.device/start failed with result 'dependency'. Mär 07 09:29:29 darw1n systemd[1]: Dependency failed for Encrypted Volumes. Mär 07 09:29:29 darw1n systemd[1]: Job cryptsetup.target/start failed with result 'dependency'. Mär 07 09:29:29 darw1n systemd[1]: Job systemd-cryptsetup@cryptswap1.service/start failed with result 'dependency'. Mär 07 09:29:29 darw1n systemd[1]: Job dev-disk-by\x2duuid-0b93a0a2\x2d115c\x2d4a45\x2d9075\x2d5f31454c5a41.device/start failed with result 'timeout'. Mär 07 09:29:29 darw1n systemd[1]: Reached target System Initializatio ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-4ubuntu3 ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 7 09:31:09 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-02-05 (29 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic.efi.signed root=UUID=63ea7e2a-9b00-4298-b58c-7a68c2775a87 ro vt.handoff=7 init=/lib/systemd/systemd systemd.debugshell SourcePackage: systemd UpgradeStatus: Upgraded to vivid on 2015-02-23 (11 days ago) dmi.bios.date: 12/17/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.60 dmi.board.name: H97 Performance 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.60:bd12/17/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH97Performance: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. To manage
[Touch-packages] [Bug 1424864] Re: Xorg crash
dmesg reports this after being kicked out back to login manager [27339.253612] NVRM: Xid (0002:00): 5, Ch M 032c D 00024040 intr 0100 and the bug is happening under kernel 3.2.0-76-generic as well -- 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/1424864 Title: Xorg crash Status in xorg package in Ubuntu: Incomplete Bug description: Xorg crashing out back into login manager and apport failed This problem report is damaged and cannot be processed. IOError(u'Invalid core dump: BFD: Warning: /tmp/tmpXYLMdA is truncated: expected core file size = 75243520, found: 6356992.',) openConnection: connect: No such file or directory cannot connect to brltty at :0 xfce4-settings-helper: Another instance is already running. Leaving... (polkit-gnome-authentication-agent-1:9183): GLib-CRITICAL **: g_variant_new_string: assertion `string != NULL' failed (polkit-gnome-authentication-agent-1:9183): polkit-gnome-1-WARNING **: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files ERROR: Error querying target relations ERROR: Error querying target relations ERROR: Error querying target relations ERROR: Error querying target relations ERROR: Error querying target relations (xfce4-settings-helper:9229): xfce4-settings-helper-WARNING **: Failed to get the _NET_NUMBER_OF_DESKTOPS property. ** Message: applet now removed from the notification area ** Message: using fallback from indicator to GtkStatusIcon ** Message: applet now embedded in the notification area WARNING: gnome-keyring:: couldn't connect to: /tmp/keyring-P0TMTU/pkcs11: No such file or directory (Thunar:9173): GLib-GIO-CRITICAL **: g_file_info_get_attribute_uint32: assertion `G_IS_FILE_INFO (info)' failed (Thunar:9173): GLib-GIO-CRITICAL **: g_file_info_get_attribute_uint32: assertion `G_IS_FILE_INFO (info)' failed WARNING: gnome-keyring:: couldn't connect to: /tmp/keyring-P0TMTU/pkcs11: No such file or directory ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-76.111-generic 3.2.66 Uname: Linux 3.2.0-76-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.8 Architecture: amd64 Date: Mon Feb 23 19:14:16 2015 InstallationMedia: Xubuntu 12.04.4 LTS Precise Pangolin - Release amd64 (20140205) MarkForUpload: True ProcEnviron: LANGUAGE=en_CA:en TERM=xterm PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1424864/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1429756] Re: FTBFS: test_job_process fails in majority of cases
It does indeed seem to be related to the kernel. I've just run that specific test 77 times on an amd64 system running a 3.18.0-11 kernel with no failures. Once the broken deps issue is resolved, I'll retest on the same system running the latest 3.19 kernel. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1429756 Title: FTBFS: test_job_process fails in majority of cases Status in upstart package in Ubuntu: New Status in upstart source package in Vivid: New Bug description: As you see in the history in https://jenkins.qa.ubuntu.com/job/vivid- adt-upstart/?, upstart's test fail almost all the time, on ok 53 - with single line command writing fast and exiting not ok 54 - with single line command writing lots of data fast and exiting wrong value for bytes, expected 3145728 got 3018027 at tests/test_job_process.c:3886 (test_start). 1..153 FAIL: test_job_process Sometimes they succeed on one architecture, and with lots of luck on both, but this is way too flaky to be an useful test. This keeps blocking the propagation of other packages from -proposed. This was most likely triggered by the kernel update from 3.18 to 3.19. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1429756/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1429822] [NEW] Cannot examine bug locally: apport-retrace is not installed
Public bug reported: On a Ubuntu 14.10 system, when i try to examine bug locally i get error: Failed to execute child process apport-retrace (No such file or directory) This is because package apport-retrace is not installed by default. Suggested solution: ask apport-retrace is needed but is not installed. Install it? from user and continue after it has been installed. ** Affects: apport (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1429822 Title: Cannot examine bug locally: apport-retrace is not installed Status in apport package in Ubuntu: New Bug description: On a Ubuntu 14.10 system, when i try to examine bug locally i get error: Failed to execute child process apport-retrace (No such file or directory) This is because package apport-retrace is not installed by default. Suggested solution: ask apport-retrace is needed but is not installed. Install it? from user and continue after it has been installed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1429822/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 718635] Re: Error message Your computer does not have enough free memory when core dump or stacktrace failed to be created is misleading
I got this running warzone2100 (at the very end of the campaign, BTW). I am using 4.5GB of my 7.8GB available and using 120KB of my 16GB swap file. Xubuntu 14.04 Linux simonX64 3.13.0-46-generic #77-Ubuntu SMP Mon Mar 2 18:23:39 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux (Incidentally, I re-loaded the last saved game, finished the campaign again and there was no crash.) ** Attachment added: InsufficientMemory_crash.png https://bugs.launchpad.net/ubuntu/+source/apport/+bug/718635/+attachment/4338791/+files/InsufficientMemory_crash.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/718635 Title: Error message Your computer does not have enough free memory when core dump or stacktrace failed to be created is misleading Status in apport package in Ubuntu: Triaged Bug description: Binary package hint: apport On Unity fully updated, when I login there is a X crash (attached), an apport dialog is displayed but complains about: --- Sorry, the program Xorg closed unexpectedly Your computer does not have enough free memory to automatically analyze the problem and send a report to the developers. --- You can only close and the report is canceled. Of course there's enough memory This message is displayed when the core dump or stacktrace can't be attached to the report. This should be changed to something closer to the real issue. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: apport 1.17.2-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.38-3.30-generic 2.6.38-rc4 Uname: Linux 2.6.38-3-generic i686 ApportLog: ERROR: apport (pid 8213) Mon Feb 14 10:17:49 2011: called for pid 741, signal 6 ERROR: apport (pid 8213) Mon Feb 14 10:17:49 2011: executable: /usr/bin/Xorg (command line /usr/bin/X :0 -br -verbose -auth /var/run/gdm/auth-for-gdm-ics1IG/database -nolisten tcp vt7) Architecture: i386 Date: Mon Feb 14 10:54:38 2011 InstallationMedia: Ubuntu 11.04 Natty Narwhal - Alpha i386 (20110209) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US.UTF-8:en LANG=en_US.UTF-8 LC_MESSAGES=en_AG.utf8 SHELL=/bin/bash SourcePackage: apport To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/718635/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1429852] [NEW] It is much too hard to file a bug report
Public bug reported: Usability issue: the process of filing a bug report is too hard. Steps to reproduce: Imagine your desktop application (e.g. gnucash) is misbehaving, and you want to help Ubuntu. These are the steps for a first time bug report: (0) look through the application's menus, no hints there how to file a bug (1) google how to report a bug, get told to create an account, click through 3 pages and lots of text https://help.ubuntu.com/community/ReportingBugs https://help.launchpad.net/YourAccount/NewAccount https://login.launchpad.net/ (2) wait for verification email (3) re-type password four 4 times in total (4) get redirected to the ubuntu-bug utility, which opens up the gnome image viewer instead of doing anything useful (go try it on a fresh install: https://help.ubuntu.com/community/ReportingBugs?action=AttachFiledo=gettarget=unity-ubuntu-bug-pkgname.png) (5) figure out that ubuntu-bug is a command line utility (6) figure out which command line command corresponds to your application (7) figure out which package contains your desktop application: $ which gnucash $ grep -r /usr/bin/gnucash /var/lib/dpkg/info/ (8) run it: $ubuntu-bug gnucash (9) Wait an unexpectedly long time at a white screen while firefox is figuring out openid (10) retype password, fifth time (11) Type in bug summary (rejoice, finally!) (12) You'd think software devs would like to make good software and improve it. But now, your experience gets invalidated and told that everybody else already knows how to work despite the bug. At least, that's what the search through (un)related bug reports suggests from a marketing point of view. So you have to muster some resolve to disagree. (13) Scroll through a page of suggestions and click that you need a new bug. (Regarding the wording: Well, actually, I don't need a bug, I'm extending my goodwill to help you get rid of one.) (14) Type in the problem report in this very form here. Expected behavior: The desktop application should have a button to report bugs somewhere in the About menu, and it should take at most 3 clicks get it done. Observed behavior: Lots of time spent on the above procedure. Do you have a way of knowing how many users give up? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apport 2.14.1-0ubuntu3.6 ProcVersionSignature: Ubuntu 3.13.0-46.77-generic 3.13.11-ckt15 Uname: Linux 3.13.0-46-generic i686 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: i386 CrashReports: 664:1000:116:0:2015-03-02 17:51:51.797172708 +0100:2015-03-02 17:51:51.797172708 +0100:/var/crash/_usr_bin_nautilus.1000.upload 640:1000:116:6914022:2015-03-02 17:51:50.777172803 +0100:2015-03-02 17:51:51.777172803 +0100:/var/crash/_usr_bin_nautilus.1000.crash 640:1000:116:1936343:2015-03-09 01:25:54.821650091 +0100:2015-03-09 09:57:12.954563948 +0100:/var/crash/_usr_bin_workrave.1000.crash 600:109:116:0:2015-03-02 18:33:35.998493596 +0100:2015-02-25 20:56:00.564689172 +0100:/var/crash/_usr_bin_nautilus.1000.uploaded CurrentDesktop: Unity Date: Mon Mar 9 13:46:16 2015 InstallationDate: Installed on 2014-08-08 (212 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty ** Description changed: Usability issue: the process of filing a bug report is so convoluted that most users' goodwill is depleted along the way. Steps to reproduce: Imagine your desktop application (e.g. gnucash) is misbehaving, and you - want to help Ubuntu. These are the hoops you have to jump through: + want to help Ubuntu. These are the steps for a first time bug report: (0) look through the application's menus, no hints there how to file a bug - (1) google how to report a bug, click through 3 pages and lots of text + (1) google how to report a bug, get told to create an account, click through 3 pages and lots of text https://help.ubuntu.com/community/ReportingBugs https://help.launchpad.net/YourAccount/NewAccount https://login.launchpad.net/ (2) wait for verification email (3) re-type password four 4 times in total - (4) get redirected to the ubuntu-bug utility, which opens up the gnome image viewer instead of doing anything useful + (4) get redirected to the ubuntu-bug utility, which opens up the gnome image viewer instead of doing anything useful (go try it on a fresh install: https://help.ubuntu.com/community/ReportingBugs?action=AttachFiledo=gettarget=unity-ubuntu-bug-pkgname.png) - (5) figure out ubuntu-bug is a command line utility + (5) figure out that ubuntu-bug is a command line utility (6) figure out which command line command corresponds to your application (7) figure out which package contains your desktop application: $ which gnucash $ grep -r /usr/bin/gnucash
[Touch-packages] [Bug 1429171] Re: systemd-fsckd[232]: Couldn't connect to plymouth: Connection refused
@dino99: As I said on the other bug: please stop running your machines with debug and getting scared by debug messages :-) (that's another one) -- 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/1429171 Title: systemd-fsckd[232]: Couldn't connect to plymouth: Connection refused Status in systemd package in Ubuntu: In Progress Bug description: get that error logged many times into journalctl on that vivid booting with systemd-sysv ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-4ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu1 Architecture: i386 CurrentDesktop: GNOME Date: Fri Mar 6 16:11:58 2015 Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-7-generic root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1429171/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1366876] Re: Xorg freeze
I'm afraid trying the utopic stack on my 14.04 install doesn't work - can't be installed. A fresh install of 14.04.2 to get the same, breaks all sorts of things and don't allow me to work. Finally, trying the current daily live is a non-starter for me, since I can't work under that, and it is often a couple of days before I see the problem. I'm not sure I have a workable way to try a newer gfx stack :(. -- 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/1366876 Title: Xorg freeze Status in xorg package in Ubuntu: Incomplete Bug description: Desktop display freezes temporarily, for (approx) 20s or so, approx once a day, with mouse pointer still working. After that it comes back and resumes as normal, seemingly replaying mouse and keyboard events from the meantime. I think it's always happened when using Google Chrome (Stable - currently 37.0.2062.94, but I think other recent versions). The desktop is completely unresponsive This didn't seem to happen until a few weeks ago. I tend to pull updates fairly regularly. In syslog there is: kernel: [277415.130771] [drm] stuck on render ring I suspect this is a dupe since I see other related bugs, but you'd be better placed to decide that than I. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,resize,place,grid,vpswitch,gnomecompat,mousepoll,session,move,obs,imgpng,snap,regex,animation,expo,ezoom,staticswitcher,workarounds,wall,fade,scale] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Sep 8 12:22:27 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: comedi-adv-pci1724, 0.0.1: added EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Since a couple weeks or more GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21fa] InstallationDate: Installed on 2014-07-11 (59 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: LENOVO 2306CTO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=561b4b77-cac6-4abb-a89e-ecf7f1bb8f42 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/11/2012 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET82WW (2.02 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET82WW(2.02):bd09/11/2012:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2306CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Thu Sep 4 16:58:14 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 728 vendor LGD xserver.version: 2:1.15.1-0ubuntu2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1366876/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1429171] Re: systemd-fsckd[232]: Couldn't connect to plymouth: Connection refused
@Martin as i remember, 'debug' was not used when that issue was seen -- 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/1429171 Title: systemd-fsckd[232]: Couldn't connect to plymouth: Connection refused Status in systemd package in Ubuntu: In Progress Bug description: get that error logged many times into journalctl on that vivid booting with systemd-sysv ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-4ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu1 Architecture: i386 CurrentDesktop: GNOME Date: Fri Mar 6 16:11:58 2015 Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-7-generic root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1429171/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1427672] Re: System doesn't power off when shutting down
** Also affects: systemd (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763028 Importance: Unknown Status: Unknown -- 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/1427672 Title: System doesn't power off when shutting down Status in systemd package in Ubuntu: Confirmed Status in systemd package in Debian: Unknown Bug description: 1. Open the session indicator (cog in top-right) 2. Shut Down... 3. Shut Down 4. The monitors go blank 5. The system doesn't power off (waited 5 minutes) Things which do work - poweroff -f - Changing to a debug shell and shutting down using login1.Manager PowerOff I can't use the system-shutdown/ functionality since shutdown doesn't get that far. I can't SSH in since network is down. I can't switch VT when it's in this state so I'm not able to interact with the system. I can't see anything on the monitors since they are turned off. Any tips on how to get useful debugging information? I'll attach journalctl from the previous boot but the last message is the journal shutting down so it's not that useful I don't think. Also syslog. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-4ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 3 12:57:33 2015 InstallationDate: Installed on 2012-10-07 (876 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20121007) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-7-generic root=UUID=980689ca-e7d9-4a99-8230-33b8b6e917cd ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw systemd.debug-shell nomdmonddf nomdmonisw SourcePackage: systemd UpgradeStatus: Upgraded to vivid on 2013-05-07 (665 days ago) dmi.bios.date: 08/17/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1201 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V LX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1201:bd08/17/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1427672/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1429887] [NEW] Pressing power button to resume does not turn on screen
Public bug reported: [filing here although may be other components] Mako running 211 from rtm I experienced these symptoms which have been previously mitigated in other scenarios. Last week while traveling and roaming this happened pretty much 100% of the time. This occurred in all areas (hotel, MWC, outside, etc) Press power button, no response Press button again, screen turns on for a few seconds then turns off Press button again, either phone resumes or more often the power dialog is shown When I returned back home the function was normal without reboot or other changes. The differences in environment: Roaming on foreign GSM network Lots of Wifi APs not connected Attached are some perhaps relevant logs, unfortunately the syslog rolled. ** Affects: powerd (Ubuntu) Importance: High Status: New ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to powerd in Ubuntu. https://bugs.launchpad.net/bugs/1429887 Title: Pressing power button to resume does not turn on screen Status in powerd package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: [filing here although may be other components] Mako running 211 from rtm I experienced these symptoms which have been previously mitigated in other scenarios. Last week while traveling and roaming this happened pretty much 100% of the time. This occurred in all areas (hotel, MWC, outside, etc) Press power button, no response Press button again, screen turns on for a few seconds then turns off Press button again, either phone resumes or more often the power dialog is shown When I returned back home the function was normal without reboot or other changes. The differences in environment: Roaming on foreign GSM network Lots of Wifi APs not connected Attached are some perhaps relevant logs, unfortunately the syslog rolled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/powerd/+bug/1429887/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1429887] Re: Pressing power button to resume does not turn on screen
** Attachment added: unity8-dash.log.7.gz https://bugs.launchpad.net/ubuntu/+source/powerd/+bug/1429887/+attachment/4338869/+files/unity8-dash.log.7.gz ** Description changed: [filing here although may be other components] Mako running 211 from rtm - I experienced these symptoms which have been previously mitigated in other scenarios. + I experienced these symptoms which have been previously mitigated in other scenarios. Last week while traveling and roaming this happened pretty much 100% of the time. This occurred in all areas (hotel, MWC, outside, etc) Press power button, no response Press button again, screen turns on for a few seconds then turns off Press button again, either phone resumes or more often the power dialog is shown When I returned back home the function was normal without reboot or other changes. The differences in environment: Roaming on foreign GSM network Lots of Wifi APs not connected + + Attached are some perhaps relevant logs, unfortunately the syslog + rolled. ** Also affects: unity8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to powerd in Ubuntu. https://bugs.launchpad.net/bugs/1429887 Title: Pressing power button to resume does not turn on screen Status in powerd package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: [filing here although may be other components] Mako running 211 from rtm I experienced these symptoms which have been previously mitigated in other scenarios. Last week while traveling and roaming this happened pretty much 100% of the time. This occurred in all areas (hotel, MWC, outside, etc) Press power button, no response Press button again, screen turns on for a few seconds then turns off Press button again, either phone resumes or more often the power dialog is shown When I returned back home the function was normal without reboot or other changes. The differences in environment: Roaming on foreign GSM network Lots of Wifi APs not connected Attached are some perhaps relevant logs, unfortunately the syslog rolled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/powerd/+bug/1429887/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1429887] Re: Pressing power button to resume does not turn on screen
** Attachment added: unity8.log.7.gz https://bugs.launchpad.net/ubuntu/+source/powerd/+bug/1429887/+attachment/4338868/+files/unity8.log.7.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to powerd in Ubuntu. https://bugs.launchpad.net/bugs/1429887 Title: Pressing power button to resume does not turn on screen Status in powerd package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: [filing here although may be other components] Mako running 211 from rtm I experienced these symptoms which have been previously mitigated in other scenarios. Last week while traveling and roaming this happened pretty much 100% of the time. This occurred in all areas (hotel, MWC, outside, etc) Press power button, no response Press button again, screen turns on for a few seconds then turns off Press button again, either phone resumes or more often the power dialog is shown When I returned back home the function was normal without reboot or other changes. The differences in environment: Roaming on foreign GSM network Lots of Wifi APs not connected Attached are some perhaps relevant logs, unfortunately the syslog rolled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/powerd/+bug/1429887/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1429887] Re: Pressing power button to resume does not turn on screen
** Attachment added: powerd.log.2.gz https://bugs.launchpad.net/ubuntu/+source/powerd/+bug/1429887/+attachment/4338867/+files/powerd.log.2.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to powerd in Ubuntu. https://bugs.launchpad.net/bugs/1429887 Title: Pressing power button to resume does not turn on screen Status in powerd package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: [filing here although may be other components] Mako running 211 from rtm I experienced these symptoms which have been previously mitigated in other scenarios. Last week while traveling and roaming this happened pretty much 100% of the time. This occurred in all areas (hotel, MWC, outside, etc) Press power button, no response Press button again, screen turns on for a few seconds then turns off Press button again, either phone resumes or more often the power dialog is shown When I returned back home the function was normal without reboot or other changes. The differences in environment: Roaming on foreign GSM network Lots of Wifi APs not connected Attached are some perhaps relevant logs, unfortunately the syslog rolled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/powerd/+bug/1429887/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1302090] Re: Dell Alienware 14, Speaker sound output is mono until a headphone jack is plugged
Hi Raymond, Thanks to answer, I was fighting to get that crap ~ sounding... So it means my hdajackretask setup is not gut ? But I have a separed volume control for subwoofer ! Now it looks like that : autoconfig: line_outs=2 (0x18/0x1a/0x0/0x0/0x0) type:line speaker_outs=1 (0x14/0x0/0x0/0x0/0x0) hp_outs=2 (0x15/0x16/0x0/0x0/0x0) mono: mono_out=0x0 inputs: Mic=0x19 Internal Mic=0x12 So you say *the easy way is to change the headset as [N/A] by hdajackretask*, but how to do that, I even don't see any headset in hdajackretask !? Which pin is it ? And where to change that badness stuff, which file where ? To be clear, could you explain simply how to setup that (el cheapo) alien soup ? P.S. I use only alsa, the card is reconised as ALC668 not ALC3661. I fondamentaly still don't know why the way from #30 don't work by me ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1302090 Title: Dell Alienware 14, Speaker sound output is mono until a headphone jack is plugged Status in alsa-driver package in Ubuntu: Confirmed Bug description: Here's the required release and package information: Description:Ubuntu Trusty Tahr (development branch) Release:14.04 Package: linux-image-extra-3.13.0-19-generic Version: 3.13.0-19.40 When playing audio through speakers on my Alienware 14 2014, the sound output is in mono until I plug a headphone in any of the two available headphone jacks (obviously, the auto-mute option must be disabled). When I do so, the sound starts to play in stereo. I would love the sound output to be stereo by default and not be forced to plug anything to achieve that. Attached is the alsa-info.sh output for my machine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1302090/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1429893] [NEW] ubuntu-bug linux gives KeyError: 'BootDmesg' error under 15.04
Public bug reported: Initiating a bug report as follows $ ubuntu-bug linux results in the following problem: ERROR: hook /usr/share/apport/package-hooks/source_linux.py crashed: Traceback (most recent call last): File /usr/lib/python3/dist-packages/apport/report.py, line 197, in _run_hook symb['add_info'](report, ui) File /usr/share/apport/package-hooks/source_linux.py, line 52, in add_info staging_drivers = re.findall((\w+): module is from the staging directory, report['BootDmesg']) File /usr/lib/python3.4/collections/__init__.py, line 908, in __getitem__ raise KeyError(key) KeyError: 'BootDmesg' ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: apport 2.16.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CrashReports: 600:110:120:0:2015-03-07 17:39:06.276339601 -0500:2015-03-07 17:39:06.276339601 -0500:/var/crash/_usr_lib_x86_64-linux-gnu_indicator-sound_indicator-sound-service.108.uploaded 640:108:120:352757:2015-03-07 17:39:02.009973764 -0500:2015-03-07 17:39:03.009973764 -0500:/var/crash/_usr_lib_x86_64-linux-gnu_indicator-sound_indicator-sound-service.108.crash 644:0:120:0:2015-03-07 17:39:04.029463645 -0500:2015-03-07 17:39:04.029463645 -0500:/var/crash/_usr_lib_x86_64-linux-gnu_indicator-sound_indicator-sound-service.108.upload CurrentDesktop: Unity Date: Mon Mar 9 11:21:57 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-03-07 (1 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150306) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apport (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 apport in Ubuntu. https://bugs.launchpad.net/bugs/1429893 Title: ubuntu-bug linux gives KeyError: 'BootDmesg' error under 15.04 Status in apport package in Ubuntu: New Bug description: Initiating a bug report as follows $ ubuntu-bug linux results in the following problem: ERROR: hook /usr/share/apport/package-hooks/source_linux.py crashed: Traceback (most recent call last): File /usr/lib/python3/dist-packages/apport/report.py, line 197, in _run_hook symb['add_info'](report, ui) File /usr/share/apport/package-hooks/source_linux.py, line 52, in add_info staging_drivers = re.findall((\w+): module is from the staging directory, report['BootDmesg']) File /usr/lib/python3.4/collections/__init__.py, line 908, in __getitem__ raise KeyError(key) KeyError: 'BootDmesg' ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: apport 2.16.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CrashReports: 600:110:120:0:2015-03-07 17:39:06.276339601 -0500:2015-03-07 17:39:06.276339601 -0500:/var/crash/_usr_lib_x86_64-linux-gnu_indicator-sound_indicator-sound-service.108.uploaded 640:108:120:352757:2015-03-07 17:39:02.009973764 -0500:2015-03-07 17:39:03.009973764 -0500:/var/crash/_usr_lib_x86_64-linux-gnu_indicator-sound_indicator-sound-service.108.crash 644:0:120:0:2015-03-07 17:39:04.029463645 -0500:2015-03-07 17:39:04.029463645 -0500:/var/crash/_usr_lib_x86_64-linux-gnu_indicator-sound_indicator-sound-service.108.upload CurrentDesktop: Unity Date: Mon Mar 9 11:21:57 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-03-07 (1 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150306) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1429893/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1429887] Re: Pressing power button to resume does not turn on screen
This seems to basically be a dupe of bug #1421455. -- 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/1429887 Title: Pressing power button to resume does not turn on screen Status in powerd package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: [filing here although may be other components] Mako running 211 from rtm I experienced these symptoms which have been previously mitigated in other scenarios. Last week while traveling and roaming this happened pretty much 100% of the time. This occurred in all areas (hotel, MWC, outside, etc) Press power button, no response Press button again, screen turns on for a few seconds then turns off Press button again, either phone resumes or more often the power dialog is shown When I returned back home the function was normal without reboot or other changes. The differences in environment: Roaming on foreign GSM network Lots of Wifi APs not connected Attached are some perhaps relevant logs, unfortunately the syslog rolled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/powerd/+bug/1429887/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1425593] Re: trivial app fails to appear in shell and crashes it on close
Had a look at this, the issue is that the application is creating two
surfaces even if the second is never visible nor painted on. Since we do
not support multiple surfaces per app at the moment this is breaking in
qtmir.
This would be fixed by the multi-window support in qtmir/unity8
** Changed in: unity8 (Ubuntu)
Assignee: Albert Astals Cid (aacid) = (unassigned)
--
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/1425593
Title:
trivial app fails to appear in shell and crashes it on close
Status in Qt integration with the Mir display server:
Confirmed
Status in unity8 package in Ubuntu:
New
Bug description:
Take this code:
#include QApplication
#include QWidget
int main(int argc, char *argv[])
{
QApplication app(argc, argv);
QWidget *w = new QWidget();
w-showMaximized();
return app.exec();
}
and this Qt pro file:
QT += core gui widgets
TARGET = simple-qwidget
TEMPLATE = app
SOURCES += main.cpp
and build on the device. On unity8 run with:
./simple-qwidget --desktop_file_hint=/usr/share/applications
/mediaplayer-app.desktop
You'll see the splash screen appear, but you'll never see a frame from the
app.
When I Ctrl+C the app, unity8 crashes
To manage notifications about this bug go to:
https://bugs.launchpad.net/qtmir/+bug/1425593/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1429887] Re: Pressing power button to resume does not turn on screen
I think it is different (perhaps related) as it never turns on the screen without an additional press. So its not a delay because the system is busy, it seems to completely ignore the first press. I also did not get it once it cleared the initial 3 press dance. -- 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/1429887 Title: Pressing power button to resume does not turn on screen Status in powerd package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: [filing here although may be other components] Mako running 211 from rtm I experienced these symptoms which have been previously mitigated in other scenarios. Last week while traveling and roaming this happened pretty much 100% of the time. This occurred in all areas (hotel, MWC, outside, etc) Press power button, no response Press button again, screen turns on for a few seconds then turns off Press button again, either phone resumes or more often the power dialog is shown When I returned back home the function was normal without reboot or other changes. The differences in environment: Roaming on foreign GSM network Lots of Wifi APs not connected Attached are some perhaps relevant logs, unfortunately the syslog rolled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/powerd/+bug/1429887/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1425185] Re: Sync tiff 4.0.3-12.1 (main) from Debian unstable (main)
Synced by Colin on March 3rd. ** Changed in: tiff (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tiff in Ubuntu. https://bugs.launchpad.net/bugs/1425185 Title: Sync tiff 4.0.3-12.1 (main) from Debian unstable (main) Status in tiff package in Ubuntu: Fix Released Bug description: Please sync tiff 4.0.3-12.1 (main) from Debian unstable (main) Changelog entries since current vivid version 4.0.3-12: tiff (4.0.3-12.1) unstable; urgency=medium * NMU as discussed with Ondrej, the future adopter of tiff * Fix multiple security issues, exact details will be recorded in the Debian security tracker -- Moritz Muehlenhoff j...@debian.org Sat, 21 Feb 2015 13:06:08 +0100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/1425185/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 886480] Re: tzdata refers to unrecognized Pridnestrovian Moldavian Republic
** Summary changed: - tzdata contains erroneous information (non existing country) + tzdata refers to unrecognized Pridnestrovian Moldavian Republic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/886480 Title: tzdata refers to unrecognized Pridnestrovian Moldavian Republic Status in tzdata package in Ubuntu: New Bug description: the code of tzdata contains information regarding a non-existing country, the so called pridnestrovian moldavian republic (an illegal political entity that emerged out of a bloody conflict, the conflict being currently still unresolved). This so called pridnestrovian moldavian republic is not a member of the UN, and its existence has not been recognized by any world state. http://en.wikipedia.org/wiki/Transnistria I think the presence of erroneous information in the code constitutes a bug and should be removed. Bellow is an example of code from the update package that went out for all versions, from Hardy Heron to Precise Pangolin: tzdata (2011n-1) unstable; urgency=critical * New upstream veersion, fixing DST for: - Cuba. - Fidji. - Pridnestrovian Moldavian Republic. * Set urgency to high as some of the above changes are already effective. etc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/886480/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1429354] Re: cryptswap (with ecryptfs) configures invalid crypttag
** Summary changed: - Systemd takes very long to boot with error in swap mounting + cryptswap (with ecryptfs) configures invalid crypttag ** Summary changed: - cryptswap (with ecryptfs) configures invalid crypttag + cryptswap (with ecryptfs) configures invalid crypttab -- 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/1429354 Title: cryptswap (with ecryptfs) configures invalid crypttab Status in systemd package in Ubuntu: Incomplete Bug description: My system boots almost instantly with upstart. Today i tried booting with systemd via the additional grub option. However, with systemd it takes really long to boot but – so long that i forced a reboot once because i thought i got stuck. Looking in to boot journal, i found the following error concerning the swap: Mär 07 09:28:00 darw1n systemd[1]: dev-sda3.swap swap process exited, code=exited status=255 Mär 07 09:28:00 darw1n systemd[1]: Failed to activate swap Swap Partition. Mär 07 09:28:00 darw1n systemd[1]: Unit dev-sda3.swap entered failed state. And this concerning nvidia-persistenced Mär 07 09:28:00 darw1n nvidia-persistenced[433]: Started (433) Mär 07 09:28:00 darw1n nvidia-persistenced[433]: Failed to query NVIDIA devices. Please ensure that the NVIDIA device files (/dev/nvidia*) exist, and that user 116 has read and write permissions for thos Mär 07 09:28:00 darw1n nvidia-persistenced[433]: The daemon no longer has permission to remove its runtime data directory /var/run/nvidia-persistenced I checked that /dev/sda3 exists and is a swap partition and i check for the /dev/nvidia files: $ ls -Alst /dev/nvidia0 0 crw-rw-rw- 1 root root 195, 0 Mär 7 09:29 /dev/nvidia0 However, the interesting part is here, where nothing seems to happen for a minute: (see the timestamps): Mär 07 09:28:01 darw1n systemd[1]: Started LSB: AppArmor initialization. Mär 07 09:28:31 darw1n systemd-journal[234]: Forwarding to syslog missed 99 messages. Mär 07 09:29:29 darw1n systemd[1]: Job dev-disk-by\x2duuid-0b93a0a2\x2d115c\x2d4a45\x2d9075\x2d5f31454c5a41.device/start timed out. Mär 07 09:29:29 darw1n systemd-journal[234]: Forwarding to syslog missed 1 messages. Mär 07 09:29:29 darw1n systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-0b93a0a2\x2d115c\x2d4a45\x2d9075\x2d5f31454c5a41.device. Mär 07 09:29:29 darw1n systemd[1]: Dependency failed for Cryptography Setup for cryptswap1. Mär 07 09:29:29 darw1n systemd[1]: Dependency failed for dev-mapper-cryptswap1.device. Mär 07 09:29:29 darw1n systemd[1]: Dependency failed for /dev/mapper/cryptswap1. Mär 07 09:29:29 darw1n systemd[1]: Dependency failed for Swap. Mär 07 09:29:29 darw1n systemd[1]: Job swap.target/start failed with result 'dependency'. Mär 07 09:29:29 darw1n systemd[1]: Job dev-mapper-cryptswap1.swap/start failed with result 'dependency'. Mär 07 09:29:29 darw1n systemd[1]: Job dev-mapper-cryptswap1.device/start failed with result 'dependency'. Mär 07 09:29:29 darw1n systemd[1]: Dependency failed for Encrypted Volumes. Mär 07 09:29:29 darw1n systemd[1]: Job cryptsetup.target/start failed with result 'dependency'. Mär 07 09:29:29 darw1n systemd[1]: Job systemd-cryptsetup@cryptswap1.service/start failed with result 'dependency'. Mär 07 09:29:29 darw1n systemd[1]: Job dev-disk-by\x2duuid-0b93a0a2\x2d115c\x2d4a45\x2d9075\x2d5f31454c5a41.device/start failed with result 'timeout'. Mär 07 09:29:29 darw1n systemd[1]: Reached target System Initializatio ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-4ubuntu3 ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 7 09:31:09 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-02-05 (29 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic.efi.signed root=UUID=63ea7e2a-9b00-4298-b58c-7a68c2775a87 ro vt.handoff=7 init=/lib/systemd/systemd systemd.debugshell SourcePackage: systemd UpgradeStatus: Upgraded to vivid on 2015-02-23 (11 days ago) dmi.bios.date: 12/17/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.60 dmi.board.name: H97 Performance 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.60:bd12/17/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH97Performance:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
[Touch-packages] [Bug 1428584] Re: Autopilot tests are failing due to wrong coordinates for key
** Branch linked: lp:~michael-sheldon/ubuntu-keyboard/fix-1428584 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1428584 Title: Autopilot tests are failing due to wrong coordinates for key Status in Ubuntu Keyboard: New Status in ubuntu-keyboard package in Ubuntu: New Bug description: Autopilot tests are failing on dashboard http://rtm- dashboard.ci.ubuntu.com/smokeng/vivid/touch/krillin/122:20150225:20150210-95b6a9f/352/ubuntu_keyboard/ I did some investigation and it seems the x coordinate for top left key (1, q, Q etc) are wrong and as a result AP taps on the wrong coordinate. This started happening around 25th Feb 2015 and is pretty consistent since then as well as I am able to reproduce it locally. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-keyboard/+bug/1428584/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1376445] Re: Addition of signon-apparmor-extension causes token lookup problems
** Branch linked: lp:~mardy/ubuntuone-credentials/lp1376445-migration- vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-system-settings- online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1376445 Title: Addition of signon-apparmor-extension causes token lookup problems Status in the base for Ubuntu mobile products: Fix Released Status in go-onlineaccounts: Incomplete Status in Pay UI: Invalid Status in The Savilerow project: Invalid Status in ACL for signond, AppArmor backend: Fix Released Status in Online Accounts setup for Ubuntu Touch: Fix Released Status in ubuntu-system-settings-online-accounts package in Ubuntu: Fix Released Status in ubuntuone-credentials package in Ubuntu: Fix Released Status in signon-apparmor-extension package in Ubuntu RTM: Triaged Status in ubuntu-system-settings-online-accounts package in Ubuntu RTM: New Status in ubuntuone-credentials package in Ubuntu RTM: Fix Released Bug description: As of image ~264 of ubuntu-touch, the signon-apparmor-extension package is included. As a result, apps like pay-ui cannot find the token any longer, and are not being notified that they are not allowed to access the token. The following error appears in the payui log file: 2014-10-01 19:15:51,550 - DEBUG - ../../../../lib/SignOn/authsessionimpl.cpp 184 errorSlot QDBusError(com.google.code.AccountsSSO.SingleSignOn.Error.PermissionDenied, Client has insuficient permissions to access the service.Method:getAuthSessionObjectPath) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1376445/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1347638] Re: Launch1 button doesn't work on shortcuts
Yep, also confirmed here. Recommend the bug goes to Fix Released. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1347638 Title: Launch1 button doesn't work on shortcuts Status in Unity: New Status in unity package in Ubuntu: Confirmed Bug description: Hardware: Thinkpad X230, but seemingly all Thinkpads. (Apologies if this is mis-characterized as a Unity bug - not sure where to put it) The special Thinkpad button, often called ThinkVantage button, used to work fine for keyboard shortcuts in 12.04, as configured in the keyboard settings panel. In 14.04 it is possible to assign it to a shortcut in the keyboard settings dialog, where it shows up as Launch1, but it doesn't work - they shortcut is not activated by hitting that key. The key appears to get through to the desktop and apps, because if I hit it while Emacs has focus it complains that nothing is assigned to XF86Launch1 (in 12.04 the key didn't get through to Emacs and there was no problem) Discussion of this, including some other's outputs, is here: http://ubuntuforums.org/showthread.php?t=890 - xev gives this on keypress/release: MappingNotify event, serial 37, synthetic NO, window 0x0, request MappingKeyboard, first_keycode 8, count 248 KeyPress event, serial 37, synthetic NO, window 0x401, root 0xa2, subw 0x0, time 2883009, (-1684,706), root:(610,758), state 0x0, keycode 156 (keysym 0x1008ff41, XF86Launch1), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 37, synthetic NO, window 0x401, root 0xa2, subw 0x0, time 2883009, (-1684,706), root:(610,758), state 0x0, keycode 156 (keysym 0x1008ff41, XF86Launch1), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False - acpi_listen gives: button/prog1 PROG1 0080 K - ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,resize,place,grid,vpswitch,gnomecompat,mousepoll,session,move,obs,imgpng,snap,regex,animation,expo,ezoom,staticswitcher,workarounds,wall,fade,scale] CurrentDesktop: Unity Date: Wed Jul 23 08:11:18 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-07-11 (11 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1347638/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1429885] [NEW] package shared-mime-info 1.3-1 failed to install/upgrade: triggers looping, abandoned
Public bug reported: I just ran the updater from terminal. ProblemType: Package DistroRelease: Ubuntu 15.04 Package: shared-mime-info 1.3-1 ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Uname: Linux 3.18.0-13-generic x86_64 ApportVersion: 2.16.2-0ubuntu2 Architecture: amd64 Date: Mon Mar 9 16:49:17 2015 DuplicateSignature: package:shared-mime-info:1.3-1:triggers looping, abandoned ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2015-02-12 (24 days ago) InstallationMedia: Ubuntu-GNOME 15.04 Vivid Vervet - Alpha amd64 (20150211) SourcePackage: shared-mime-info Title: package shared-mime-info 1.3-1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: shared-mime-info (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package vivid ** Description changed: - ran the updater + I just ran the updater from terminal. ProblemType: Package DistroRelease: Ubuntu 15.04 Package: shared-mime-info 1.3-1 ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Uname: Linux 3.18.0-13-generic x86_64 ApportVersion: 2.16.2-0ubuntu2 Architecture: amd64 Date: Mon Mar 9 16:49:17 2015 DuplicateSignature: package:shared-mime-info:1.3-1:triggers looping, abandoned ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2015-02-12 (24 days ago) InstallationMedia: Ubuntu-GNOME 15.04 Vivid Vervet - Alpha amd64 (20150211) SourcePackage: shared-mime-info Title: package shared-mime-info 1.3-1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1429885 Title: package shared-mime-info 1.3-1 failed to install/upgrade: triggers looping, abandoned Status in shared-mime-info package in Ubuntu: New Bug description: I just ran the updater from terminal. ProblemType: Package DistroRelease: Ubuntu 15.04 Package: shared-mime-info 1.3-1 ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Uname: Linux 3.18.0-13-generic x86_64 ApportVersion: 2.16.2-0ubuntu2 Architecture: amd64 Date: Mon Mar 9 16:49:17 2015 DuplicateSignature: package:shared-mime-info:1.3-1:triggers looping, abandoned ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2015-02-12 (24 days ago) InstallationMedia: Ubuntu-GNOME 15.04 Vivid Vervet - Alpha amd64 (20150211) SourcePackage: shared-mime-info Title: package shared-mime-info 1.3-1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1429885/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1383357] Re: enabling flight mode shows airplane + [2g|3g] icon
** Changed in: network-manager (Ubuntu Utopic) Status: Confirmed = Incomplete ** Changed in: network-manager (Ubuntu Vivid) Status: Triaged = Incomplete -- 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/1383357 Title: enabling flight mode shows airplane + [2g|3g] icon Status in indicator-network package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Incomplete Status in indicator-network source package in Utopic: Invalid Status in network-manager source package in Utopic: Incomplete Status in indicator-network source package in Vivid: Invalid Status in network-manager source package in Vivid: Incomplete Status in indicator-network package in Ubuntu RTM: Invalid Bug description: known duplicate with different end result: bug #1386109 NM fails to send a proper networking status updated signal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1383357/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1394204] Re: dbus daemon spinning with NM AP properties change event
Based upon tvoss' findings in comment #13, I'm closing out the network- manager tasks as Invalid. If anyone disagrees, feel free to re-open, but please provide updated logs and/or steps to reproduce if doing so. ** Changed in: network-manager (Ubuntu) Assignee: Ricardo Mendoza (ricmm) = (unassigned) ** Changed in: network-manager (Ubuntu RTM) Assignee: Ricardo Mendoza (ricmm) = (unassigned) ** Changed in: network-manager (Ubuntu) Status: In Progress = Invalid ** Changed in: network-manager (Ubuntu RTM) Status: New = Invalid -- 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/1394204 Title: dbus daemon spinning with NM AP properties change event Status in the base for Ubuntu mobile products: Fix Released Status in Location Service: In Progress Status in network-manager package in Ubuntu: Invalid Status in location-service package in Ubuntu RTM: Fix Released Status in network-manager package in Ubuntu RTM: Invalid Bug description: I am consistently seeing this in the Bluefin office this week Mako running 133 Phone gets warm in pocket, wake up the phone and attach top shows dbus-daemon at 100%+ cpu and network-manager next at 10-20% It never quiets own, at least not for over 5 mins 3g data is turned off Cellular is roaming to local carrier fwiw Seems to happen whenever I leave the AP coverage, whether I return or not Reproducing the issue: The problem is easily reproducible when forcing NM to roam between multiple access points and never quite finishing the association to one AP. At home, I reproduce by roaming between different floors, where each floor has got its own WiFi. Any sufficiently complex office WiFi setup should trigger it, too. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1394204/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1429899] [NEW] StateSaver should not restore when app launched from content-hub
Public bug reported: Testing the messaging-app state saving ability that we've been adding from this MR: https://code.launchpad.net/~tiagosh/messaging-app/state-saver2/+merge/250996 deb can be found here: http://jenkins.qa.ubuntu.com/job/generic-mediumtests-builder-vivid-armhf/1669/artifact/work/output/*zip*/output.zip The problem is, when the app is launched from the content-hub, the StateSaver still tries to restore it's previously saved state, but it should not and this causes problems. It should clear the state, the same way it does when launched via url-dispatcher. According to Ken, there are content-hub signals that StateSaver will need to listen to in order to know when the app is being launched by content-hub. To reproucde: 1) install the messaging-app deb from above 2) open messaging-app, swipe from bottom to create a new message 3) type some names in the recipient field, and type some message in the send field 4) do kill -2 pidOfMessagingApp to kill the messaging-app and save it's state 5) open camera-app and go to the photo roll 6) press Share from toolbar and select messaging-app from the list Expected results: - messaging-app should be displayed with a new page showing the photo as an attachment, and nothing else Actual results: - messaging-app shows the restored state from when it was last run (the values entered in Step 3 above) ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: High Status: New ** Changed in: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1429899 Title: StateSaver should not restore when app launched from content-hub Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: Testing the messaging-app state saving ability that we've been adding from this MR: https://code.launchpad.net/~tiagosh/messaging-app/state-saver2/+merge/250996 deb can be found here: http://jenkins.qa.ubuntu.com/job/generic-mediumtests-builder-vivid-armhf/1669/artifact/work/output/*zip*/output.zip The problem is, when the app is launched from the content-hub, the StateSaver still tries to restore it's previously saved state, but it should not and this causes problems. It should clear the state, the same way it does when launched via url-dispatcher. According to Ken, there are content-hub signals that StateSaver will need to listen to in order to know when the app is being launched by content-hub. To reproucde: 1) install the messaging-app deb from above 2) open messaging-app, swipe from bottom to create a new message 3) type some names in the recipient field, and type some message in the send field 4) do kill -2 pidOfMessagingApp to kill the messaging-app and save it's state 5) open camera-app and go to the photo roll 6) press Share from toolbar and select messaging-app from the list Expected results: - messaging-app should be displayed with a new page showing the photo as an attachment, and nothing else Actual results: - messaging-app shows the restored state from when it was last run (the values entered in Step 3 above) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1429899/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1302090] Re: Dell Alienware 14, Speaker sound output is mono until a headphone jack is plugged
you are using old version of alsa driver if you still find the name is
alc668 since the driver had rename alc668 on those dell computers to
alc3661
https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/sound/pci/hda?id=4b016931a997be59a2be0da3398985a19fdfa5be
static struct alc_codec_rename_pci_table rename_pci_tbl[] = {
+ { 0x10ec0280, 0x1028, 0, ALC3220 },
+ { 0x10ec0282, 0x1028, 0, ALC3221 },
+ { 0x10ec0283, 0x1028, 0, ALC3223 },
+ { 0x10ec0292, 0x1028, 0, ALC3226 },
+ { 0x10ec0255, 0x1028, 0, ALC3234 },
+ { 0x10ec0668, 0x1028, 0, ALC3661 },
+ { } /* terminator */
+};
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1302090
Title:
Dell Alienware 14, Speaker sound output is mono until a headphone jack
is plugged
Status in alsa-driver package in Ubuntu:
Confirmed
Bug description:
Here's the required release and package information:
Description:Ubuntu Trusty Tahr (development branch)
Release:14.04
Package: linux-image-extra-3.13.0-19-generic
Version: 3.13.0-19.40
When playing audio through speakers on my Alienware 14 2014, the sound
output is in mono until I plug a headphone in any of the two available
headphone jacks (obviously, the auto-mute option must be disabled).
When I do so, the sound starts to play in stereo.
I would love the sound output to be stereo by default and not be
forced to plug anything to achieve that.
Attached is the alsa-info.sh output for my machine.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1302090/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1429415] Re: Unable to enter password in the lock screen after using Qtcreator to run apps on the device
A workaround is to log into the phone with SSH/adb and restart lightdm. -- 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/1429415 Title: Unable to enter password in the lock screen after using Qtcreator to run apps on the device Status in qtcreator-plugin-ubuntu package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: I have noticed consistently that after upgrading the phone to vivid, while developing apps and running them on the device via Qtcreator, after a few runs, when the device locks (due to timeout, or manual locking) it is no longer possible to unlock the device by typing in the password in the lock screen since when I type the password, the passphrase characters are not typed into the textfield. It is sort of like the lock screen does not take any input. The only way to fix the solution is to reboot the phone since I cannot adb into the device without unlocking it first to do any unity8 reboots. I noticed that I get the following output line on Qtc, Connection to 127.0.0.1 closed by remote host. I tried using 2 other cables and have noticed the connection closed by remote host. But despite the remote host closing the connection, QtC still displays the device status in green indicating it is detected and available. However on trying to run the app again, I get the error Could not conenct to host: Connection refused. Is the device still connected and set up network access? This connection is terminated by remote host after few seconds even if I let the app be idle during that time. Steps to reproduce the issue: 1. Connect the phone to the laptop. 2. Open any app in Qtcreator and set it to run the app on the device. 3. Run the app on the device. 4. Close the app on the phone and lock the device. 5. Try unlocking the device. What happens: Device is locked and the lock screen textfield does not accept any input. Pressing on the keypad buttons doesnt do anything Note: The lockscreen issue happens only on vivid. But the connection being terminated by the remote host happens both on vivid and rtm. System Information: Laptop: Ubuntu 14.04.2 LTS Nexus 4(Mako) running vivid img 125 qtcreator-plugin-ubuntu: 3.1.1+15.04.20150224-0ubuntu1~0trusty1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtcreator-plugin-ubuntu/+bug/1429415/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1429894] Re: gcc-4.8: internal compiler error: in dwarf2out_frame_debug_adjust_cfa, at dwarf2cfi.c:1078
$ cat neon4.i
typedef uint8x16_t __attribute__((__vector_size__(16)));
typedef uint8x16_t unative_t;
raid6_neon4_gen_syndrome_real_d;
fn1() {
uint8x16_t __trans_tmp_1;
unative_t wq2;
for (; raid6_neon4_gen_syndrome_real_d;) {
fn2();
fn2(wq2);
wq2 = __trans_tmp_1;
}
}
$ gcc-4.8 -mapcs -mabi=aapcs-linux -mno-thumb-interwork -marm -march=armv7-a
-mfloat-abi=softfp -mfpu=neon -g -gdwarf-4 -O2 -std=gnu90 -fno-strict-aliasing
-fno-common -fno-dwarf2-cfi-asm -funwind-tables -fno-delete-null-pointer-checks
-fstack-protector -fno-omit-frame-pointer -fno-optimize-sibling-calls
-fno-var-tracking-assignments -fno-inline-functions-called-once
-fno-strict-overflow -fconserve-stack -ffreestanding neon4.i
neon4.i:3:1: warning: data definition has no type or storage class [enabled by
default]
raid6_neon4_gen_syndrome_real_d;
^
neon4.i: In function 'fn1':
neon4.i:12:1: internal compiler error: in dwarf2out_frame_debug_adjust_cfa, at
dwarf2cfi.c:1078
}
^
Please submit a full bug report,
with preprocessed source if appropriate.
not seen when building with -O1
** Changed in: gcc-4.8 (Ubuntu)
Status: New = Confirmed
** Bug watch added: Linaro Bug Tracking System #1322
https://bugs.linaro.org/show_bug.cgi?id=1322
** Also affects: gcc-linaro via
https://bugs.linaro.org/show_bug.cgi?id=1322
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gcc-4.8 in Ubuntu.
https://bugs.launchpad.net/bugs/1429894
Title:
gcc-4.8: internal compiler error: in dwarf2out_frame_debug_adjust_cfa,
at dwarf2cfi.c:1078
Status in Linaro GCC:
Unknown
Status in gcc-4.8 package in Ubuntu:
Confirmed
Bug description:
Seeing these when trying to compile linux-lts-vivid (v3.19 kernel) on
the trusty compiler, also on the proposed SRU version:
lib/raid6/neon4.c: In function 'raid6_neon4_gen_syndrome_real':
lib/raid6/neon4.c:113:1: internal compiler error: in
dwarf2out_frame_debug_adjust_cfa, at dwarf2cfi.c:1078
}
^
Please submit a full bug report,
with preprocessed source if appropriate.
See file:///usr/share/doc/gcc-4.8/README.Bugs for instructions.
Preprocessed source stored into /tmp/ccg57WPc.out file, please attach this
to your bugreport.
To manage notifications about this bug go to:
https://bugs.launchpad.net/gcc-linaro/+bug/1429894/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1419874] Re: krillin bluetooth discoverability enabled on boot
This bug was fixed in the package ubuntu-system-settings - 0.3+15.04.20150306.1~rtm-0ubuntu1 --- ubuntu-system-settings (0.3+15.04.20150306.1~rtm-0ubuntu1) 14.09; urgency=medium [ CI Train Bot ] * New rebuild forced. [ Ricardo Salveti de Araujo ] * bluetooth: disable device visiblity when switching out, that way it's not staying on if the settings are closed from the switcher or if the user switch to another software (LP: #1419874) -- CI Train Bot ci-train-...@canonical.com Fri, 06 Mar 2015 23:53:57 + -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1419874 Title: krillin bluetooth discoverability enabled on boot Status in the base for Ubuntu mobile products: Confirmed Status in bluez package in Ubuntu: In Progress Status in ubuntu-system-settings package in Ubuntu: In Progress Status in bluez package in Ubuntu RTM: Fix Released Status in ubuntu-system-settings package in Ubuntu RTM: Fix Released Bug description: Using krillin rtm 228, the device is discoverable/can be paired -o over bluetooth directly after boot (don't even need to unlock the greeter). That seems like somewhat a security (and use extra power as well) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1419874/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1410113] Re: [krillin] Data connection doesn't switch from Wifi to Cellular (3G/4G)
Changed the summary to include [krillin] as the report doesn't include any mention of other devices. ** Summary changed: - Data connection doesn't switch from Wifi to Cellular (3G/4G) + [krillin] Data connection doesn't switch from Wifi to Cellular (3G/4G) -- 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/1410113 Title: [krillin] Data connection doesn't switch from Wifi to Cellular (3G/4G) Status in network-manager package in Ubuntu: New Bug description: Conditions to reproduce are not clear. *Sometimes* when going out of Wifi range, data doesn't switch to 3G/4G. I waited 45min and the connection never established. When I'm back within Wifi range, the device reconnects to the AP and data is working. I didn't play with airplane mode. ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: network-manager 0.9.8.8-0ubuntu33 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Tue Jan 13 09:34:02 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: source-directory /etc/network/interfaces.d InstallationDate: Installed on 2015-01-12 (1 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20150112-030205) IpRoute: default via 192.168.1.254 dev wlan0 proto static 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.16 metric 9 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true PciNetwork: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.dbus.1.system.d.org.freedesktop.NetworkManager.conf: 2014-12-18T18:05:17 nmcli-dev: DEVICE TYPE STATE DBUS-PATH /ril_0 gsm connected /org/freedesktop/NetworkManager/Devices/2 /ril_1 gsm disconnected /org/freedesktop/NetworkManager/Devices/1 wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1410113/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1429899] Re: StateSaver should not restore when app launched from content-hub
** Changed in: ubuntu-ui-toolkit (Ubuntu) Assignee: (unassigned) = Zsombor Egri (zsombi) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1429899 Title: StateSaver should not restore when app launched from content-hub Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: Testing the messaging-app state saving ability that we've been adding from this MR: https://code.launchpad.net/~tiagosh/messaging-app/state-saver2/+merge/250996 deb can be found here: http://jenkins.qa.ubuntu.com/job/generic-mediumtests-builder-vivid-armhf/1669/artifact/work/output/*zip*/output.zip The problem is, when the app is launched from the content-hub, the StateSaver still tries to restore it's previously saved state, but it should not and this causes problems. It should clear the state, the same way it does when launched via url-dispatcher. According to Ken, there are content-hub signals that StateSaver will need to listen to in order to know when the app is being launched by content-hub. To reproucde: 1) install the messaging-app deb from above 2) open messaging-app, swipe from bottom to create a new message 3) type some names in the recipient field, and type some message in the send field 4) do kill -2 pidOfMessagingApp to kill the messaging-app and save it's state 5) open camera-app and go to the photo roll 6) press Share from toolbar and select messaging-app from the list Expected results: - messaging-app should be displayed with a new page showing the photo as an attachment, and nothing else Actual results: - messaging-app shows the restored state from when it was last run (the values entered in Step 3 above) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1429899/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1302090] Re: Dell Alienware 14, Speaker sound output is mono until a headphone jack is plugged
The diff concerns 1 file which add more aliases name but when I look to your autoconfig, it doesn't look better then mine, it's only cosmetic, the problem remain the same. Now I desabled the headset and here is the result : autoconfig: line_outs=2 (0x18/0x1a/0x0/0x0/0x0) type:line speaker_outs=1 (0x14/0x0/0x0/0x0/0x0) hp_outs=1 (0x15/0x0/0x0/0x0/0x0) mono: mono_out=0x0 inputs: Mic=0x19 Internal Mic=0x12 How to change the badness ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1302090 Title: Dell Alienware 14, Speaker sound output is mono until a headphone jack is plugged Status in alsa-driver package in Ubuntu: Confirmed Bug description: Here's the required release and package information: Description:Ubuntu Trusty Tahr (development branch) Release:14.04 Package: linux-image-extra-3.13.0-19-generic Version: 3.13.0-19.40 When playing audio through speakers on my Alienware 14 2014, the sound output is in mono until I plug a headphone in any of the two available headphone jacks (obviously, the auto-mute option must be disabled). When I do so, the sound starts to play in stereo. I would love the sound output to be stereo by default and not be forced to plug anything to achieve that. Attached is the alsa-info.sh output for my machine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1302090/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1427649] Re: online account does not work for HTML 5 applications
land in rtm to unblock devs ** Changed in: canonical-devices-system-image Importance: Undecided = High ** Changed in: canonical-devices-system-image Status: New = In Progress ** Changed in: canonical-devices-system-image Milestone: None = ww13-ota -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-webapps-qml in Ubuntu. https://bugs.launchpad.net/bugs/1427649 Title: online account does not work for HTML 5 applications Status in the base for Ubuntu mobile products: In Progress Status in unity-webapps-qml package in Ubuntu: Fix Released Status in unity-webapps-qml package in Ubuntu RTM: New Bug description: I just tried online account API for HTML 5 applications, but I found that it did not work at all. Best regards, XiaoGuo To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1427649/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1427649] Re: online account does not work for HTML 5 applications
** Also affects: unity-webapps-qml (Ubuntu RTM) Importance: Undecided Status: New ** Branch linked: lp:~abreu-alexandre/unity-webapps-qml/rtm-backport-oa- api-requestaccount -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-webapps-qml in Ubuntu. https://bugs.launchpad.net/bugs/1427649 Title: online account does not work for HTML 5 applications Status in the base for Ubuntu mobile products: In Progress Status in unity-webapps-qml package in Ubuntu: Fix Released Status in unity-webapps-qml package in Ubuntu RTM: New Bug description: I just tried online account API for HTML 5 applications, but I found that it did not work at all. Best regards, XiaoGuo To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1427649/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1402994] Re: oxide::qt::LocationProvider should be paused when the application becomes inactive
** Changed in: canonical-devices-system-image Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtubuntu-sensors in Ubuntu. https://bugs.launchpad.net/bugs/1402994 Title: oxide::qt::LocationProvider should be paused when the application becomes inactive Status in the base for Ubuntu mobile products: Fix Released Status in Oxide Webview: Invalid Status in qtubuntu-sensors package in Ubuntu: Fix Released Bug description: If a WebView is used to browse to a page that requests continuous position updates, the LocationProvider should be paused when the application goes in the background, and resumed when it gets back in the foreground. This could be implemented by making oxide::qt::LocationProvider a BrowserPlatformIntegrationObserver. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1402994/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1429894] Re: gcc-4.8: internal compiler error: in dwarf2out_frame_debug_adjust_cfa, at dwarf2cfi.c:1078
** Attachment added: gcc-4.8-lp1429894 https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1429894/+attachment/4338877/+files/gcc-4.8-lp1429894 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gcc-4.8 in Ubuntu. https://bugs.launchpad.net/bugs/1429894 Title: gcc-4.8: internal compiler error: in dwarf2out_frame_debug_adjust_cfa, at dwarf2cfi.c:1078 Status in gcc-4.8 package in Ubuntu: New Bug description: Seeing these when trying to compile linux-lts-vivid (v3.19 kernel) on the trusty compiler, also on the proposed SRU version: lib/raid6/neon4.c: In function 'raid6_neon4_gen_syndrome_real': lib/raid6/neon4.c:113:1: internal compiler error: in dwarf2out_frame_debug_adjust_cfa, at dwarf2cfi.c:1078 } ^ Please submit a full bug report, with preprocessed source if appropriate. See file:///usr/share/doc/gcc-4.8/README.Bugs for instructions. Preprocessed source stored into /tmp/ccg57WPc.out file, please attach this to your bugreport. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1429894/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1421455] Re: Slow wake up time on physical power button pressed
It's unfortunately still unclear what's happening here. The working assumption is that dbus traffic is high in those instances, causing messages to get queued and block some parts of the system. Unfortunately steps to reproduce still unknown :/ ** Changed in: unity8 (Ubuntu) Assignee: Michael Terry (mterry) = (unassigned) ** Changed in: unity8 (Ubuntu) Status: Confirmed = Triaged ** Changed in: unity8 (Ubuntu) Status: Triaged = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1421455 Title: Slow wake up time on physical power button pressed Status in unity8 package in Ubuntu: Incomplete Bug description: Device: bq Aquaris E4.5 running: Stable #17 When pressing on physical power button on device to wake it up sometime it even takes up to 2-3 secs before anything appears on the screen. This time wary but its hard to tell then its shorter and when is longer. This is not so bad on nexus4. Should you need more info, I'm happy to help. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1421455/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1429894] [NEW] gcc-4.8: internal compiler error: in dwarf2out_frame_debug_adjust_cfa, at dwarf2cfi.c:1078
Public bug reported: Seeing these when trying to compile linux-lts-vivid (v3.19 kernel) on the trusty compiler, also on the proposed SRU version: lib/raid6/neon4.c: In function 'raid6_neon4_gen_syndrome_real': lib/raid6/neon4.c:113:1: internal compiler error: in dwarf2out_frame_debug_adjust_cfa, at dwarf2cfi.c:1078 } ^ Please submit a full bug report, with preprocessed source if appropriate. See file:///usr/share/doc/gcc-4.8/README.Bugs for instructions. Preprocessed source stored into /tmp/ccg57WPc.out file, please attach this to your bugreport. ** Affects: gcc-4.8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gcc-4.8 in Ubuntu. https://bugs.launchpad.net/bugs/1429894 Title: gcc-4.8: internal compiler error: in dwarf2out_frame_debug_adjust_cfa, at dwarf2cfi.c:1078 Status in gcc-4.8 package in Ubuntu: New Bug description: Seeing these when trying to compile linux-lts-vivid (v3.19 kernel) on the trusty compiler, also on the proposed SRU version: lib/raid6/neon4.c: In function 'raid6_neon4_gen_syndrome_real': lib/raid6/neon4.c:113:1: internal compiler error: in dwarf2out_frame_debug_adjust_cfa, at dwarf2cfi.c:1078 } ^ Please submit a full bug report, with preprocessed source if appropriate. See file:///usr/share/doc/gcc-4.8/README.Bugs for instructions. Preprocessed source stored into /tmp/ccg57WPc.out file, please attach this to your bugreport. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1429894/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1319789] Re: Trackpad not working on 14.04
Hp Pavillion 15- n204tx Thanks, Varun. Original Message From: Christopher M. Penalver Sent: Monday, 9 March 2015 06:15 To: varun19...@gmail.com Reply To: Bug 1319789 Subject: [Bug 1319789] Re: Trackpad not working on 14.04 varun, could you please provide the product number of your computer? -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1319789 Title: Trackpad not working on 14.04 Status in xorg package in Ubuntu: Incomplete Bug description: ever since the laptop was updated to 14.04 lts from 12.04 lts, the tracpad has not been working, and is not recognised. there is no trackpad option under mouse and trackpad settings. i have tried many attempts to fix it, but has not worked. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: [core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu May 15 17:02:52 2014 DistUpgraded: 2014-05-11 18:24:24,169 DEBUG enabling apt cron job DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-puli-precise-amd64-20130925-0 DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:2166] Subsystem: Hewlett-Packard Company Device [103c:2166] InstallationDate: Installed on 2013-11-28 (168 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130925-02:34 MachineType: Hewlett-Packard HP Pavilion 15 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=856eced2-cdd1-459e-8b1e-55b1ed18f5ac ro i915.modeset=1 quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-05-11 (3 days ago) dmi.bios.date: 10/31/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.34 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2166 dmi.board.vendor: Hewlett-Packard dmi.board.version: 29.34 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.34:bd10/31/2013:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr09921100410600080:rvnHewlett-Packard:rn2166:rvr29.34:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion 15 Notebook PC dmi.product.version: 09921100410600080 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Thu May 15 16:37:20 2014 xserver.configfile: default xserver.errors: module ABI major version (18) doesn't match the server's version (20) Failed to load module syntp (module requirement mismatch, 0) module ABI major version (18) doesn't match the server's version (20) Failed to load module syntp (module requirement mismatch, 0) No input driver matching `syntp' xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 17900 vendor AUO xserver.version: 2:1.15.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1319789/+subscriptions -- 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/1319789 Title: Trackpad not working on 14.04 Status in xorg package in Ubuntu: Incomplete Bug description: ever since the laptop was updated to 14.04 lts from 12.04 lts, the tracpad has not been working, and is not recognised. there is no trackpad option under mouse and trackpad settings. i have tried many attempts to fix it, but has not worked. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8
[Touch-packages] [Bug 1312836] Re: [systemd] dh_installinit does not create /etc/rc*.d/S??foo if there is an /etc/init/foo.conf
I think I found the culprit... my /etc/network/interfaces file contains lines like: auto em0 iface em0 inet manual auto eth0 iface eth0 inet manual They refer to previous names of the same interface as it went from being called eth0 to now em0. When attempting to start networking via systemctl start networking, it times out with: Mar 09 11:23:26 my_hostname_here systemd[1]: Starting LSB: Raise network interfaces Mar 09 11:23:26 my_hostname_here networking[7235]: * Configuring network interfaces... Mar 09 11:23:26 my_hostname_here networking[7235]: Cannot find device eth0 Mar 09 11:23:26 my_hostname_here networking[7235]: Failed to bring up eth0. Mar 09 11:28:26 my_hostname_here systemd[1]: networking.service start operation timed out. Terminating. Mar 09 11:28:26 my_hostname_here systemd[1]: Failed to start LSB: Raise network interfaces.. Mar 09 11:28:26 my_hostname_here systemd[1]: Unit networking.service entered failed state. Mar 09 11:28:26 my_hostname_here systemd[1]: networking.service failed. Mar 09 11:28:26 my_hostname_here networking[7235]: Cannot find device em0 Mar 09 11:28:26 my_hostname_here networking[7235]: Failed to bring up em0. Commenting out said lines fixed the problem. Although I have not restarted yet to actually verify, but systemctl start networking is now happy. I'll restart and report back if this didn't fix the problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1312836 Title: [systemd] dh_installinit does not create /etc/rc*.d/S??foo if there is an /etc/init/foo.conf Status in debhelper package in Ubuntu: Fix Released Status in ifupdown package in Ubuntu: Fix Released Status in sysvinit package in Ubuntu: Fix Released Bug description: I had no networking when I booted up with systemd just now. laney@raleigh cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN laney@raleigh ifconfig loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:572 errors:0 dropped:0 overruns:0 frame:0 TX packets:572 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:46364 (46.3 KB) TX bytes:46364 (46.3 KB) laney@raleigh more /etc/network/interfaces # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback auto eth0 iface eth0 inet manual auto br0 iface br0 inet dhcp bridge_ports eth0 bridge_stp off bridge_fd 0 bridge_maxwait 0 laney@raleigh sudo ifup eth0 br0 ifup: failed to open lockfile /run/network/.ifstate.lock: No such file or directory Then copying from /etc/init/networking.conf's pre-start laney@raleigh sudo mkdir -p /run/network laney@raleigh sudo ifup -a Internet Systems Consortium DHCP Client 4.2.4 Copyright 2004-2012 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ Listening on LPF/br0/30:85:a9:9d:63:f6 Sending on LPF/br0/30:85:a9:9d:63:f6 Sending on Socket/fallback DHCPDISCOVER on br0 to 255.255.255.255 port 67 interval 3 (xid=0x1b02ce25) DHCPDISCOVER on br0 to 255.255.255.255 port 67 interval 7 (xid=0x1b02ce25) DHCPREQUEST of 192.168.1.136 on br0 to 255.255.255.255 port 67 (xid=0x1b02ce25) DHCPOFFER of 192.168.1.136 from 192.168.1.1 DHCPACK of 192.168.1.136 from 192.168.1.1 bound to 192.168.1.136 -- renewal in 39350 seconds. laney@raleigh cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 192.168.1.1 I feel like there's probably an existing systemd-ish way of doing this. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ifupdown 0.7.47.2ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 25 18:01:25 2014 InstallationDate: Installed on 2012-10-07 (564 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20121007) SourcePackage: ifupdown UpgradeStatus: Upgraded to trusty on 2013-05-07 (353 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debhelper/+bug/1312836/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1419877] Re: [bluetooth] krillin advertized as type computer
the bluez config mentions that only major and minor are used, so maybe 0x00020c then... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1419877 Title: [bluetooth] krillin advertized as type computer Status in the base for Ubuntu mobile products: New Status in bluez package in Ubuntu: New Bug description: Using rtm 228, the device is advertized as being a computer, it should probably be a phone rather? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1419877/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1419061] Re: detect all packages as not genuine
This happens because /etc/os-release contains NAME=Ubuntu Kylin and is_distro_package from packaging-apt-dpkg.py uses that as a part of checking if if the package is of native origin. ** Summary changed: - detect all packages as not genuine + On Ubuntu Kylin detect all packages as not genuine -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1419061 Title: On Ubuntu Kylin detect all packages as not genuine Status in apport package in Ubuntu: Confirmed Bug description: Hallo In Vivid if I run apport-bug (pkg) it always return that is not a genuine package: The problem cannot be reported: This is not an official Ubuntu package. Please remove any third party package and try again. see attached screenshot. Set as critical because it represent a loss of informations in a test environement ( eg: a medium user feel discouraged to report a bug) Thanks Fabio --- ApportLog: ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu Kylin 14.10 InstallationDate: Installed on 2014-08-12 (184 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) Package: apport 2.16.1-0ubuntu2 [origin: Ubuntu] PackageArchitecture: all ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Tags: third-party-packages vivid Uname: Linux 3.18.0-13-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: Upgraded to vivid on 2015-01-10 (33 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CrashReports: 640:1000:120:72115:2015-03-05 10:38:22.031167507 +0100:2015-03-06 10:30:38.543396523 +0100:/var/crash/_usr_bin_sogou-qimpanel.1000.crash 644:0:120:0:2015-03-06 10:24:01.613003795 +0100:2015-03-06 10:30:17.487292102 +0100:/var/crash/_usr_lib_x86_64-linux-gnu_indicator-sound_indicator-sound-service.108.upload 640:110:120:4951702:2015-03-06 18:50:04.986461639 +0100:2015-03-06 18:50:05.986461639 +0100:/var/crash/_usr_share_apport_apport-gtk.110.crash 640:108:120:306702:2015-03-06 10:22:15.169228553 +0100:2015-03-06 10:24:02.636496873 +0100:/var/crash/_usr_lib_x86_64-linux-gnu_indicator-sound_indicator-sound-service.108.crash 600:110:120:0:2015-03-06 10:24:21.091356436 +0100:2015-02-24 22:14:44.551599595 +0100:/var/crash/_usr_lib_x86_64-linux-gnu_indicator-sound_indicator-sound-service.108.uploaded CurrentDesktop: Unity DistroRelease: Ubuntu Kylin 15.04 EcryptfsInUse: Yes InstallationDate: Installed on 2015-02-24 (9 days ago) InstallationMedia: Ubuntu-Kylin 15.04 Vivid Vervet - Alpha amd64 (20150224) Package: apport 2.16.2-0ubuntu1 [origin: Ubuntu] PackageArchitecture: all Tags: third-party-packages vivid Uname: Linux 4.0.0-04rc2-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1419061/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1426388] Re: Move a set of apps and scopes to the custom tarball
It seems we want to move all preinstalled scopes and apps to custom in order to have the most flexibility -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1426388 Title: Move a set of apps and scopes to the custom tarball Status in ubuntu-touch-meta package in Ubuntu: New Bug description: Certain apps and scopes will be substituted depending on the target market and other customizations. music, video click scopes other tbd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-touch-meta/+bug/1426388/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1424966] Re: /usr/lib/arm-linux-gnueabihf/indicator-datetime/indicator-datetime-service:5:reset_timer:unity::indicator::datetime::LiveClock::Impl::on_timerfd_cond:g_main_dispatch
** Changed in: canonical-devices-system-image Status: New = Fix Released ** Changed in: canonical-devices-system-image Importance: Undecided = Critical -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1424966 Title: /usr/lib/arm-linux-gnueabihf/indicator-datetime/indicator-datetime- service:5:reset_timer:unity::indicator::datetime::LiveClock::Impl::on_timerfd_cond:g_main_dispatch:g_main_context_dispatch:g_main_context_iterate Status in the base for Ubuntu mobile products: Fix Released Status in indicator-datetime package in Ubuntu: Fix Released Status in indicator-datetime package in Ubuntu RTM: Fix Released Bug description: It happened randomly but several time on RTM/krillin. According to errors.u.c it started with 13.10.0+15.04.20150213.1-0ubuntu1 on vivid and 13.10.0+15.04.20150213~rtm-0ubuntu1 on RTM. [ Charles Kerr ] * change the WallClock to detect time changes from TFD_TIMER_CANCEL_ON_SET, e.g. when ntp--manual is toggled The Ubuntu Error Tracker has been receiving reports about a problem regarding indicator-datetime. This problem was most recently seen with version 13.10.0+15.04.20150213.1-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/3b8aefe51ab8eae0b64a89605ae01d5433da3000 contains more details. current build number: 242 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed last update: 2015-02-23 08:07:23 version version: 242 version ubuntu: 20150223 version device: 20150216-fe747ac version custom: 20150216-561-29-186 Trace: https://errors.ubuntu.com/bucket/?id=/usr/lib/arm-linux-gnueabihf/indicator-datetime/indicator-datetime-service%3A5%3Areset_timer%3Aunity%3A%3Aindicator%3A%3Adatetime%3A%3ALiveClock%3A%3AImpl%3A%3Aon_timerfd_cond%3Ag_main_dispatch%3Ag_main_context_dispatch%3Ag_main_context_iterate To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1424966/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1419874] Re: krillin bluetooth discoverability enabled on boot
** 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 bluez in Ubuntu. https://bugs.launchpad.net/bugs/1419874 Title: krillin bluetooth discoverability enabled on boot Status in the base for Ubuntu mobile products: Fix Released Status in bluez package in Ubuntu: In Progress Status in ubuntu-system-settings package in Ubuntu: In Progress Status in bluez package in Ubuntu RTM: Fix Released Status in ubuntu-system-settings package in Ubuntu RTM: Fix Released Bug description: Using krillin rtm 228, the device is discoverable/can be paired -o over bluetooth directly after boot (don't even need to unlock the greeter). That seems like somewhat a security (and use extra power as well) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1419874/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1418077] Re: After radio technology is changed, mobile-data takes ~5m to re-connect
** Summary changed: - NM fails to create a cellular data connection for a unacceptably long time + After radio technology is changed, mobile-data takes ~5m to re-connect -- 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/1418077 Title: After radio technology is changed, mobile-data takes ~5m to re-connect Status in the base for Ubuntu mobile products: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Confirm cellular data (disable wifi) 2. Change TechnologyPreference on online SIM 3. Confirm no cellular data 4. Wait ~10 minutes 5. Confirm cellular data What happens: Changing something on the modem causes cellular data to disappear for 10 minutes What should happen: It should behave as before, i.e. cellular data should come back immediately current build number: 97 device name: krillin channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/vivid-proposed last update: 2015-02-02 12:48:25 version version: 97 version ubuntu: 20150202 version device: 20150128-5379bdb version custom: 20150202 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1418077/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 972077] Re: apt repository disk format has race conditions
Fwiw, we have support for the by-hash scheme in apt in experimetnal: https://github.com/Debian/apt/blob/debian/experimental/apt-pkg/acquire-item.cc#L1222 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/972077 Title: apt repository disk format has race conditions Status in MAAS: New Status in apt package in Ubuntu: Confirmed Bug description: Apt archives are accessed over HTTP; this has resulted in a cluster of bugs (reported here, and upstream) about problems behind intercepting caches, problems with squid etc. There are 3 interlocking issues: A - mirror networks may be out of sync with each other (e.g. a file named on one mirror may no longer exist, or may not yet exist, on another mirror) B - updating files on a single mirror is not atomic - and even small windows of inconsistency will, given enough clients, cause headaches. C - caches exacerbate race conditions - when one happens, until the cached data expires, all clients of the cache will suffer from the race Solving this requires one of several things: - file system transactions - an archive format that requires only weakly ordered updates to the files at particular urls with the assumption that only one file may be observed to change at a time (because a lookup of file A, then B, may get a cache miss on A and a cache hit on B, so even if all clients strictly go A, then B, updates may still see old files when paths are reused). - super robust clients that repeatedly retry with progressively less cache friendly headers until they have a consistent view. (This is very tricky to do). It may be possible to do a tweak to the apt repository format though, which would allow publishing a race-free format in parallel with the existing layout, while clients migrate. To be safe against issue (A) the mirror network would need some care around handling of dns round- robin mirrors [to minimise the situation where referenced data is not available], but this should be doable - or alternatively clients doing 'apt-get update' may need to be willing to retry to accommodate round- robin skew. What would such an archive format look like? It would have only one well known file name (e.g. Releases-2), which would be internally signed. Rather than signing e.g. Packages.gz, it would sign a uniquely named packages and sources file - e.g. Packages-$HASH.gz or Packages-$serialno.gz. Backwards compatibility is achieved by using the same filenames for deb's and the like. We need to keep writing Packages.gz though, and Releases, until we no longer worry about old apt clients. We can optimise disk space a little by making Packages.gz a symlink to a Packages-$HASH.gz (and so on for Sources..), but it may be simpler and less prone to unexpected behaviour to keep using regular files. tl;dr * Unique file names for all unique file content with one exception * Releases-2, a self-signed file that provides hashes and names the index files (Packages, Sources, Translations etc) * Coexists with existing archive layout To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/972077/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1419874] Re: krillin bluetooth discoverability enabled on boot
This bug was fixed in the package bluez - 4.101-0ubuntu24 --- bluez (4.101-0ubuntu24) 14.09; urgency=medium * dont_enable_discoverable_during_init_with_if_valid_timeout.patch: - Backport from upstream to avoid enabling discoverable if there is a valid timeout value (LP: #1419874) -- Ricardo Salveti de Araujo ricardo.salv...@canonical.com Sun, 08 Mar 2015 18:47:09 -0300 ** Changed in: bluez (Ubuntu RTM) Status: New = Fix Released ** Changed in: ubuntu-system-settings (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 bluez in Ubuntu. https://bugs.launchpad.net/bugs/1419874 Title: krillin bluetooth discoverability enabled on boot Status in the base for Ubuntu mobile products: Confirmed Status in bluez package in Ubuntu: In Progress Status in ubuntu-system-settings package in Ubuntu: In Progress Status in bluez package in Ubuntu RTM: Fix Released Status in ubuntu-system-settings package in Ubuntu RTM: Fix Released Bug description: Using krillin rtm 228, the device is discoverable/can be paired -o over bluetooth directly after boot (don't even need to unlock the greeter). That seems like somewhat a security (and use extra power as well) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1419874/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1429885] Re: package shared-mime-info 1.3-1 failed to install/upgrade: triggers looping, abandoned
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1429885 Title: package shared-mime-info 1.3-1 failed to install/upgrade: triggers looping, abandoned Status in shared-mime-info package in Ubuntu: New Bug description: I just ran the updater from terminal. ProblemType: Package DistroRelease: Ubuntu 15.04 Package: shared-mime-info 1.3-1 ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Uname: Linux 3.18.0-13-generic x86_64 ApportVersion: 2.16.2-0ubuntu2 Architecture: amd64 Date: Mon Mar 9 16:49:17 2015 DuplicateSignature: package:shared-mime-info:1.3-1:triggers looping, abandoned ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2015-02-12 (24 days ago) InstallationMedia: Ubuntu-GNOME 15.04 Vivid Vervet - Alpha amd64 (20150211) SourcePackage: shared-mime-info Title: package shared-mime-info 1.3-1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1429885/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1429887] Re: Pressing power button to resume does not turn on screen
** Attachment added: powerd.log.3.gz https://bugs.launchpad.net/ubuntu/+source/powerd/+bug/1429887/+attachment/4338866/+files/powerd.log.3.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to powerd in Ubuntu. https://bugs.launchpad.net/bugs/1429887 Title: Pressing power button to resume does not turn on screen Status in powerd package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: [filing here although may be other components] Mako running 211 from rtm I experienced these symptoms which have been previously mitigated in other scenarios. Last week while traveling and roaming this happened pretty much 100% of the time. This occurred in all areas (hotel, MWC, outside, etc) Press power button, no response Press button again, screen turns on for a few seconds then turns off Press button again, either phone resumes or more often the power dialog is shown When I returned back home the function was normal without reboot or other changes. The differences in environment: Roaming on foreign GSM network Lots of Wifi APs not connected Attached are some perhaps relevant logs, unfortunately the syslog rolled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/powerd/+bug/1429887/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1419877] Re: [bluetooth] krillin advertized as type computer
The type from the Class defined in the configuration, default is 0x000100 for Computer, 0x40020C would correspond to a smartphone instead. It doesn't seem we can change it from the settings/client side -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1419877 Title: [bluetooth] krillin advertized as type computer Status in the base for Ubuntu mobile products: New Status in bluez package in Ubuntu: New Bug description: Using rtm 228, the device is advertized as being a computer, it should probably be a phone rather? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1419877/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
