[Touch-packages] [Bug 1445758] [NEW] Spinning dots behind Play icon are confusing
Public bug reported: The spinning dots shown when tapping on a video give the impression something is happening when in fact a further user action (another tap) is being waited on. Steps to reproduce: 1. Open Gallery app 2. Tap on a video under Events Expected: 3. The video starts playing Actual: 3. A black screen with a translucent play icon and the spinning dots animation is shown 4. Wait 5. Nothing happens 6. Tap the screen 7. Mediaplayer is open and the video is played ** Affects: gallery-app Importance: Undecided Status: New ** Affects: gallery-app (Ubuntu) Importance: Undecided Status: New ** Also affects: gallery-app (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gallery-app in Ubuntu. https://bugs.launchpad.net/bugs/1445758 Title: Spinning dots behind Play icon are confusing Status in Gallery App: New Status in gallery-app package in Ubuntu: New Bug description: The spinning dots shown when tapping on a video give the impression something is happening when in fact a further user action (another tap) is being waited on. Steps to reproduce: 1. Open Gallery app 2. Tap on a video under Events Expected: 3. The video starts playing Actual: 3. A black screen with a translucent play icon and the spinning dots animation is shown 4. Wait 5. Nothing happens 6. Tap the screen 7. Mediaplayer is open and the video is played To manage notifications about this bug go to: https://bugs.launchpad.net/gallery-app/+bug/1445758/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1445215] Re: Unexpected notifiaction about bazillions of voicemails
This bug just has been triggered one again: Phone got power off due to no battery I wait 6% before boot. And then: (cf attachement) If you need me to post other stuff like logs, please be sure you include a few howto. ** Attachment added: screenshot20154018_134036157.png https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1445215/+attachment/4378997/+files/screenshot20154018_134036157.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-messages in Ubuntu. https://bugs.launchpad.net/bugs/1445215 Title: Unexpected notifiaction about bazillions of voicemails Status in indicator-messages package in Ubuntu: Confirmed Bug description: I was clicking Check for updates when suddenly my phone rebooted. After it went back to life I've noticed the new notification which said: 18196311974 voicemail messages. AFAIK I don't have a voicemail even active. Screenshot attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1445215/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1296425] Re: pulseaudio is started twice - effectively making device management impossible.
I can confirm that the fix as in proposed works as intended. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1296425 Title: pulseaudio is started twice - effectively making device management impossible. Status in alsa-plugins package in Ubuntu: Invalid Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in alsa-plugins source package in Trusty: Invalid Status in ubuntu-drivers-common source package in Trusty: In Progress Bug description: [Impact] On the current kubuntu 14.04 live-image (and for a 13.10 upgraded system) pulseaudio is running twice. This makes attaching/deattaching of usb-headset and other stuff impossible because the two instances fight over the events. The fix is https://github.com/tseliot/ubuntu-drivers- common/commit/5fe70ce1 [Test Case] To reproduce just boot up the current image and do a ps -ef | grep pulseaudio [Regression Potential] Low. This fix has been out for many months in 14.10, and only changes the environment that aplay -l gets called with. In the absolutely worst case if this goes totally wrong, ubuntu-drivers would stop to detect sl-modem capable soft-modems. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu10 ProcVersionSignature: Ubuntu 3.13.0-19.39-lowlatency 3.13.6 Uname: Linux 3.13.0-19-lowlatency i686 ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sgh2336 F pulseaudio sgh2796 F pulseaudio /dev/snd/controlC0: sgh2336 F pulseaudio sgh2796 F pulseaudio CurrentDesktop: KDE Date: Sun Mar 23 22:36:50 2014 InstallationDate: Installed on 2013-12-24 (89 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20131224) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2012 dmi.bios.vendor: LENOVO dmi.bios.version: G7ET31WW (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 2356GCG 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:bvrG7ET31WW(1.13):bd07/02/2012:svnLENOVO:pn2356GCG:pvrThinkPadT430s:rvnLENOVO:rn2356GCG:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2356GCG dmi.product.version: ThinkPad T430s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-plugins/+bug/1296425/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1428063] Re: Result activation on single tap doesn't fully support scopes API capabilities
Same behaviour noticed, Result has URI without scope:// , however scope is packed into a click. OS build 21, image 20150410.1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-shell in Ubuntu. https://bugs.launchpad.net/bugs/1428063 Title: Result activation on single tap doesn't fully support scopes API capabilities Status in unity-scopes-shell package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: Single tap doesn't fully honor intercept activation flag exposed by Scopes API. Activation can only be intercepted by scope if result's uri is scope://... (or if scope is clickscope). There is some special-casing for that in unity8 dash qml code, we should probably move this down to shell plugin to fix the issue of intercept activation flag. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-shell/+bug/1428063/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1443202] Re: applications hangs while trying to play audio
Actually I had to disable PA like this:
chmod -x /usr/bin/pulseaudio ; pkill pulse
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1443202
Title:
applications hangs while trying to play audio
Status in pulseaudio package in Ubuntu:
New
Bug description:
Any application (plasma, mplayer, vlc, avidemux, etc) hangs when playing the
first sound.
Here is a strace log
lstat(/run, {st_mode=S_IFDIR|0755, st_size=800, ...}) = 0
lstat(/run/user, {st_mode=S_IFDIR|0755, st_size=100, ...}) = 0
lstat(/run/user/1000, {st_mode=S_IFDIR|0700, st_size=180, ...}) = 0
lstat(/run/user/1000/pulse, {st_mode=S_IFDIR|0700, st_size=60, ...}) = 0
getuid()= 1000
socket(PF_LOCAL, SOCK_STREAM|SOCK_CLOEXEC, 0) = 9
fcntl(9, F_GETFD) = 0x1 (flags FD_CLOEXEC)
setsockopt(9, SOL_SOCKET, SO_PRIORITY, [6], 4) = 0
fcntl(9, F_GETFL) = 0x2 (flags O_RDWR)
fcntl(9, F_SETFL, O_RDWR|O_NONBLOCK)= 0
connect(9, {sa_family=AF_LOCAL, sun_path=/run/user/1000/pulse/native}, 110)
= -1 ENOENT (No such file or directory)
close(9)= 0
socket(PF_LOCAL, SOCK_STREAM|SOCK_CLOEXEC, 0) = 9
fcntl(9, F_GETFD) = 0x1 (flags FD_CLOEXEC)
setsockopt(9, SOL_SOCKET, SO_PRIORITY, [6], 4) = 0
fcntl(9, F_GETFL) = 0x2 (flags O_RDWR)
fcntl(9, F_SETFL, O_RDWR|O_NONBLOCK)= 0
connect(9, {sa_family=AF_LOCAL, sun_path=/var/run/pulse/native}, 110) = -1
ENOENT (No such file or directory)
close(9)= 0
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1443202/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1445772] [NEW] Static ip configuration is not possible with touch gui
Public bug reported: I have received the bq Aquaris Ubuntu and it looks and works great, but the first impression is lowered by the missing ability to use a static ip configuration for WLAN. On the web I found a solution to set a static ip configuration, but this require a connection to the pc. This is not very helpful when you are on a trip. I think it is important that you can set a static ip configuration only with the touch gui. When you have connected to a WLAN you can look at the connection details and most of the screen is blank. I think this is a good place for an ip settings menu. ** Affects: indicator-network (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1445772 Title: Static ip configuration is not possible with touch gui Status in indicator-network package in Ubuntu: New Bug description: I have received the bq Aquaris Ubuntu and it looks and works great, but the first impression is lowered by the missing ability to use a static ip configuration for WLAN. On the web I found a solution to set a static ip configuration, but this require a connection to the pc. This is not very helpful when you are on a trip. I think it is important that you can set a static ip configuration only with the touch gui. When you have connected to a WLAN you can look at the connection details and most of the screen is blank. I think this is a good place for an ip settings menu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1445772/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1430276] Re: Desktop/windows painted incorrectly in dual monitor configuration
** Description changed: - Problem 1. if miniDVI (connected to NVIDIA card) is connected upon boot, - the desktop resolution is detected incorrectly. - - Problem 2. lightdm won't start from scratch, needs to be restarted as service on every boot, and then ctrl+alt+f7 has to be pressed repeatedly until the login window appears, and then again repeatedly, until the desktop appears (after which, the miniDVI can be inserted). If you skip the first repeated pressing, you end up with a console window saying /org/FreeDesktop/Accounts/User1000 has been changed. If you skip the second repeated pressing, you revert to login window. - Yes, I've tried the following: - sudo dpkg-reconfigure lightdm - sudo chown -R username . - sudo apt-get install --reinstall ubuntu-desktop unity unity-greeter - including setting HEED_DEFAULT_DESKTOP_MANAGER=false in /etc/init.d/lightdm - - Problem 3. right now (as of yesterday), unity decorator and dash does - not apper after login, and dconf reset -f /org/compiz/ setsid unity - has to be run from lightdm, provided that you somehow manage to get a - terminal up (ctrl+alt+T does not work, neither does Alt+f2) - - The result of this: - - sudo dmidecode -s bios-version sudo dmidecode -s bios-release-date - is: - - A14 - 09/24/2014 - - Sorry for the mess, I'd be happy to provide further information, since this laptop seems to be an outlier to all your fixes. - P.S. /etc/modprobe.d is not a file still persists... + If miniDVI (connected to NVIDIA card) is connected upon boot, the + desktop resolution is detected incorrectly. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 NonfreeKernelModules: vtsspp sep3_15 pax wl nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: - NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.113 Mon Dec 1 21:08:13 PST 2014 - GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) + NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.113 Mon Dec 1 21:08:13 PST 2014 + GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: - + ApportVersion: 2.14.1-0ubuntu3.7 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 10 11:31:49 2015 DistUpgraded: 2014-06-06 12:58:55,700 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: - Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) -Subsystem: Dell Device [1028:05aa] - NVIDIA Corporation GK106M [GeForce GTX 770M] [10de:11e0] (rev a1) (prog-if 00 [VGA controller]) -Subsystem: Dell Device [1028:05aa] + Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) + Subsystem: Dell Device [1028:05aa] + NVIDIA Corporation GK106M [GeForce GTX 770M] [10de:11e0] (rev a1) (prog-if 00 [VGA controller]) + Subsystem: Dell Device [1028:05aa] MachineType: Alienware Alienware 17 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic root=UUID=40c4f155-d830-45c7-8784-98c30335b94c ro nvidia.modeset=1 nosplash SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-06-06 (276 days ago) dmi.bios.date: 09/24/2014 dmi.bios.vendor: Alienware dmi.bios.version: A14 dmi.board.name: 068R5X dmi.board.vendor: Alienware dmi.board.version: A01 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A14 dmi.modalias: dmi:bvnAlienware:bvrA14:bd09/24/2014:svnAlienware:pnAlienware17:pvrA14:rvnAlienware:rn068R5X:rvrA01:cvnAlienware:ct8:cvrA14: dmi.product.name: Alienware 17 dmi.product.version: A14 dmi.sys.vendor: Alienware version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.59+git20150225.1f73578d-0ubuntu0ricotz~trusty version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.0~git20150204.661c8bb2-0ubuntu0ricotz~trusty version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.0~git20150204.661c8bb2-0ubuntu0ricotz~trusty version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.99+git20140806.fbf575cb-0ubuntu0sarvatt~trusty version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
[Touch-packages] [Bug 1314587]
Please attach the Xorg log file. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1314587 Title: Windows slow/stall/freeze when minimizing/restoring/etc in Unity 7 (14.04 and 14.10) Status in Unity: Confirmed Status in X.Org X server: Confirmed Status in unity package in Ubuntu: Triaged Status in xorg package in Ubuntu: Triaged Bug description: Steps to reproduce: * Minimize current window or alt-tab between windows * Reveal launcher to click on application * Click `Super` to bring up Dash * Hold `Super` to bring up Keyboard Shortcuts What should happen: Action completes smoothly and quickly. What happens instead: * Action may be slow / animation jerky. * Action may stall (animation frozen on given frame, e.g. window partially minimized) - initiating another action cancels first action and second action may succeed (most often calling Guake with F12 seems to solve the issue) * Action may freeze - cursor no longer moves - a soft reboot (Alt+PrtScr+REISUB) usually works, otherwise a hard reboot Notes: * Not application specific. Minimizing is reliably slow/stalls with minimizing Firefox (including 29, I do not have a lot of bookmarks) or Pidgin, but I use those programs more often. * I am using an Nvidia Optimus machine with the default Nouveau driver - no `nvidia-prime`, no Bumblebee. I temporarily installed the latest stable Nvidia driver (including `nvidia-prime`) and it made no difference. * I did not experience this issue on the same machine running 13.10 (with Bumblebee). * I am running Maximus. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Apr 30 12:53:15 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10, 3.13.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:04b6] NVIDIA Corporation GF108M [GeForce GT 525M] [10de:0df5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:04b6] InstallationDate: Installed on 2014-04-24 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: Dell Inc. Dell System XPS L502X ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=3a8fb3f3-1054-45a0-8ec0-0cbeba33da00 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0YR8NN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA04:bd03/25/2011:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0YR8NN:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L502X dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Wed Apr 30 12:03:43 2014 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id8940 vendor AUO
[Touch-packages] [Bug 1430779] Re: xorg crashing back to login manager
*** This bug is a duplicate of bug 1424864 *** https://bugs.launchpad.net/bugs/1424864 ** This bug has been marked a duplicate of bug 1424864 Xorg crash -- 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/1430779 Title: xorg crashing back to login manager Status in xorg package in Ubuntu: New Bug description: see https://bugs.launchpad.net/bugs/1424864 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 .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 173.14.39 Wed Nov 27 14:25:00 PST 2013 GCC version: gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ApportVersion: 2.0.1-0ubuntu17.8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDmesg: [ 34.324493] init: plymouth-stop pre-start process (1452) terminated with status 1 [ 42.536036] eth1: no IPv6 routers present Date: Wed Mar 11 09:39:57 2015 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu DkmsStatus: nvidia-173, 173.14.39, 3.2.0-76-generic, x86_64: installed nvidia-173, 173.14.39, 3.2.0-77-generic, x86_64: installed ExtraDebuggingInterest: Yes, GraphicsCard: NVIDIA Corporation G71 [GeForce 7900 GT/GTO] [10de:0291] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation Device [10de:c560] InstallationMedia: Xubuntu 12.04.4 LTS Precise Pangolin - Release amd64 (20140205) JockeyStatus: xorg:nvidia_173 - NVIDIA accelerated graphics driver (Proprietary, Enabled, In use) xorg:nvidia_304 - NVIDIA accelerated graphics driver (Proprietary, Disabled, Not in use) xorg:nvidia_304_updates - NVIDIA accelerated graphics driver (post-release updates) (Proprietary, Disabled, Not in use) xorg:nvidia_96 - NVIDIA accelerated graphics driver (Proprietary, Disabled, Not in use) MachineType: System manufacturer System Product Name MarkForUpload: True ProcEnviron: LANGUAGE=en_CA:en TERM=xterm PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-76-generic root=UUID=a04e1a40-6087-4a62-82bf-309ad289670a ro nosplash=1 loglevel=5 drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: Section Device Identifier Default Device Option NoLogoTrue EndSection dmi.bios.date: 06/19/2006 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080012 dmi.board.name: A8V-VM dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080012:bd06/19/2006:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnA8V-VM:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.52-1~precise2 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.4-0ubuntu0.7 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.4-0ubuntu0.7 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.17 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1.2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4.4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1430779/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1432413] Re: Synaptic Touchpad xevents are hijacked under X
Igor Lopez, thank you for reporting this and helping make Ubuntu better. As per http://us.acer.com/ac/en/US/content/drivers an update to your computer's buggy and outdated BIOS is available (1.10). If you update to this following https://help.ubuntu.com/community/BIOSUpdate does it change anything? If it doesn't, could you please both specify what happened, and provide the output of the following terminal command: sudo dmidecode -s bios-version sudo dmidecode -s bios-release-date For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette . Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful. As well, you don't have to create a new bug report. Once the BIOS is updated, and the information above is provided, then please mark this report Status Confirmed. Thank you for your understanding. ** Tags added: bios-outdated-1.10 ** Tags removed: synaptic touchpad xorg ** Changed in: xorg (Ubuntu) Importance: Undecided = Low ** Changed in: xorg (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1432413 Title: Synaptic Touchpad xevents are hijacked under X Status in xorg package in Ubuntu: Incomplete Bug description: Synaptic Touchpad xevents are hijacked under X11. I have a problem with the synaptic touch-pad on my Acer Aspire that started around a week ago. The problem can be described as that there is a massive amount of xevents being generated and appearing to originate from the touch-pad even though the touch-pad is not used. I have tested the HW which seems to work fine. The test performed is to start a terminal session (Ctrl + Alt + 2) before the fault occurs and check the xevents by running ~$ sudo evtest /dev/input/eventX where the X to use is found in /proc/bus/input/devices and found by running ~$ cat /proc/bus/input/devices |grep mouse No matter how much the touch-pad is used will the console show the corresponding events which indicates that HW and driver works OK as long it is not under X When the problem has occurred (in Desktop mode) is it easy (but inconvenient) to get back to normal by key combo Fn+F7 twice, turn off touch-pad and then turn on again. And more, one can get unlucky in the sense that the generated events could click somewhere one do not want to click. During the problem is it impossible to use the mouse since it flies around (mostly going in a bottom to top of screen direction) but one can check the generated events using evtest again. How can I help troubleshooting the problem? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.16.0-31.43~14.04.1-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Mar 15 19:51:13 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation ValleyView Gen7 [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0933] InstallationDate: Installed on 2015-02-21 (22 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) MachineType: Acer Aspire E3-112 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-31-generic root=UUID=a97d0b51-4244-48ca-ba87-bc3a38a8b62d ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/20/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.08 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: R2 dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.08:bd08/20/2014:svnAcer:pnAspireE3-112:pvrV1.08:rvnAcer:rnR2:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire E3-112 dmi.product.version: V1.08 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1~ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core
[Touch-packages] [Bug 1445753] Re: No media available label shows in camera preview with long translations
** Also affects: camera-app Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1445753 Title: No media available label shows in camera preview with long translations Status in Camera App: New Status in camera-app package in Ubuntu: New Bug description: See the attached screenshot. The translation in Catalan for No media available. is longer than the English string, making the letters not visible in the screenshot spill out to the camera preview. The label size for that message should probably be limited to the width of the photo roll, so that longer messages don't affect the camera preview. To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1445753/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1427669] Re: ??
Keith, thank you for taking the time to report this and helping to make Ubuntu better. Unfortunately, this report didn't include enough information. You may find it helpful to read How to report bugs effectively http://www.chiark.greenend.org.uk/~sgtatham/bugs.html and https://wiki.ubuntu.com/ReportingBugs . We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem, 2. The behavior you expected, and 3. The behavior you actually encountered (in as much detail as possible). Thank you for your understanding. ** Tags added: bios-outdated-1.30 ** Description changed: ? + Toshiba Satellite C655-S5305 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic i686 ApportVersion: 2.14.7-0ubuntu8.2 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue Mar 3 07:44:20 2015 DistUpgraded: 2015-02-09 16:17:38,224 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: - nvidia-304, 304.125, 3.16.0-30-generic, i686: installed - nvidia-304, 304.125, 3.16.0-31-generic, i686: installed + nvidia-304, 304.125, 3.16.0-30-generic, i686: installed + nvidia-304, 304.125, 3.16.0-31-generic, i686: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: - Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) -Subsystem: Toshiba America Info Systems Device [1179:fce0] + Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) + Subsystem: Toshiba America Info Systems Device [1179:fce0] Lsusb: - Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub - Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub - Bus 001 Device 003: ID 10f1:1a34 Importek - Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub + Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 001 Device 003: ID 10f1:1a34 Importek + Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: TOSHIBA Satellite C655 ProcEnviron: - PATH=(custom, no user) - LANG=en_US.UTF-8 - SHELL=/bin/bash + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-31-generic root=UUID=6ad9e927-7756-4cfe-80eb-888f35f51202 ro plymouth:debug drm.debug=0xe SourcePackage: xorg UpgradeStatus: Upgraded to utopic on 2015-02-09 (21 days ago) dmi.bios.date: 08/01/2011 dmi.bios.vendor: INSYDE dmi.bios.version: 1.20 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDE:bvr1.20:bd08/01/2011:svnTOSHIBA:pnSatelliteC655:pvrPSC2EU-02Y02H:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.name: Satellite C655 dmi.product.version: PSC2EU-02Y02H dmi.sys.vendor: TOSHIBA version.compiz: compiz 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: Mon Mar 2 20:47:14 2015 xserver.configfile: default xserver.errors: - + xserver.logfile: /var/log/Xorg.0.log xserver.outputs: - product id 21825 - vendor SEC + product id 21825 + vendor SEC xserver.version: 2:1.16.0-1ubuntu1.3 ** Changed in: xorg (Ubuntu) Importance: Undecided = Low ** Changed in: xorg (Ubuntu) Status: New = Incomplete -- You received this bug
[Touch-packages] [Bug 1429224] Re: error
Victor Castro, thank you for taking the time to report this and helping to make Ubuntu better. Unfortunately, this report didn't include enough information. You may find it helpful to read How to report bugs effectively http://www.chiark.greenend.org.uk/~sgtatham/bugs.html and https://wiki.ubuntu.com/ReportingBugs . We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem, 2. The behavior you expected, and 3. The behavior you actually encountered (in as much detail as possible). Thank you for your understanding. ** Tags added: latest-bios-2.00 ** Changed in: xorg (Ubuntu) Importance: Undecided = Low ** Changed in: xorg (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1429224 Title: error Status in xorg package in Ubuntu: Incomplete Bug description: error ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 .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 Date: Fri Mar 6 19:06:00 2015 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GT218M [GeForce 310M] [10de:0a75] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:ff00] InstallationDate: Installed on 2015-02-08 (26 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: TOSHIBA Satellite A500 ProcEnviron: LANGUAGE=es_ES PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-31-generic root=UUID=75d143f1-d3ec-4af8-9182-378ea6861807 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/10 dmi.bios.vendor: TOSHIBA dmi.bios.version: 2.00 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: NSKAA dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 9 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvr2.00:bd11/18/10:svnTOSHIBA:pnSatelliteA500:pvrPSAR9E-00H00FCE:rvnTOSHIBA:rnNSKAA:rvr1.00:cvnTOSHIBA:ct9:cvrN/A: dmi.product.name: Satellite A500 dmi.product.version: PSAR9E-00H00FCE dmi.sys.vendor: TOSHIBA 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: Fri Mar 6 18:38:28 2015 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.16.0-1ubuntu1.3 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1429224/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1390625] Re: mouse cursor gets corrupted
I tried to install a more recent version of xserver as proposed in other comments but my touchpad stopped working so I went back. I'm on a Dell Inspiron 7537 Platinum, with a Synaptic touchpad. -- 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/1390625 Title: mouse cursor gets corrupted Status in elementary OS: Confirmed Status in Mesa: New Status in Unity: Invalid Status in unity package in Ubuntu: Confirmed Status in xorg-lts-utopic package in Ubuntu: Confirmed Bug description: In Ubuntu 14.10, the mouse cursor graphic gets corrupted under certain occasions. It then looks flipped, sheared or shows fragments of a previous cursor. * when switching the cursor them forth and back in Gnome Tweak Tool * when dragdropping a document icon Maybe related, the cursor does not always show the correct image scale on a high-dpi display (this was working right in 14.04). For example after login, or when hovering specific areas, or on mouse down to start a dragdrop, the cursor appears 1/4 the expected size. Attached is a photo of a corrupted cursor (whereas a screenshot with Gimp showed the uncorrupted cursor). ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 BootLog: * Setting up X socket directories... [400G [394G[ OK ] CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Nov 7 22:12:52 2014 DistUpgraded: 2014-11-04 18:35:56,188 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3978] InstallationDate: Installed on 2014-02-02 (278 days ago) InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140201) MachineType: LENOVO 20266 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed root=UUID=4bfb3686-b9f7-487d-81f6-eceb41097ad9 ro quiet splash acpi_backlight=vendor SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2014-11-04 (3 days ago) dmi.bios.date: 10/31/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN31WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Yoga2 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 Pro dmi.modalias: dmi:bvnLENOVO:bvr76CN31WW:bd10/31/2013:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro: dmi.product.name: 20266 dmi.product.version: Lenovo Yoga 2 Pro dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Fri Nov 7 14:54:59 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: [dix] ELAN Touchscreen: unable to find touch point 1 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16970 vendor SDC xserver.version: 2:1.16.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1390625/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1429026] Re: nvidia graphics card not detected
** Description changed: - Hi, - - I am using the following Hardware: - - Motherboard GA-J1900N-D3V - Garphics card Zotac GT 610 PCI - Monitor Asus PB278Q - As the on-board intel HD graphics GPU can not drive the 2560x1440 - resolution of athe monitor I need the graphics card. The motherboard - only comes with a PCI slot, so I chose the Zotac GT610 PCI card. - However, it is not recognized by the sytem. - - here is the output of lspci -nn - 00:00.0 Host bridge [0600]: Intel Corporation ValleyView SSA-CUnit [8086:0f00] (rev 0c) - 00:02.0 VGA compatible controller [0300]: Intel Corporation ValleyView Gen7 [8086:0f31] (rev 0c) - 00:13.0 SATA controller [0106]: Intel Corporation ValleyView 6-Port SATA AHCI Controller [8086:0f23] (rev 0c) - 00:14.0 USB controller [0c03]: Intel Corporation ValleyView USB xHCI Host Controller [8086:0f35] (rev 0c) - 00:1a.0 Encryption controller [1080]: Intel Corporation ValleyView SEC [8086:0f18] (rev 0c) - 00:1b.0 Audio device [0403]: Intel Corporation ValleyView High Definition Audio Controller [8086:0f04] (rev 0c) - 00:1c.0 PCI bridge [0604]: Intel Corporation ValleyView PCI Express Root Port [8086:0f48] (rev 0c) - 00:1c.1 PCI bridge [0604]: Intel Corporation ValleyView PCI Express Root Port [8086:0f4a] (rev 0c) - 00:1c.2 PCI bridge [0604]: Intel Corporation ValleyView PCI Express Root Port [8086:0f4c] (rev 0c) - 00:1c.3 PCI bridge [0604]: Intel Corporation ValleyView PCI Express Root Port [8086:0f4e] (rev 0c) - 00:1f.0 ISA bridge [0601]: Intel Corporation ValleyView Power Control Unit [8086:0f1c] (rev 0c) - 00:1f.3 SMBus [0c05]: Intel Corporation ValleyView SMBus Controller [8086:0f12] (rev 0c) - 01:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 06) - 02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 06) - 03:00.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev 41) - 04:00.0 PCI bridge [0604]: Pericom Semiconductor PI7C9X111SL PCIe-to-PCI Reversible Bridge [12d8:e111] (rev 01) + resolution of the monitor I need the graphics card. The motherboard only + comes with a PCI slot, so I chose the Zotac GT610 PCI card. However, it + is not recognized by the sytem. dmesg | grep VGA yields [0.874589] fb0: EFI VGA frame buffer device [2.202555] fb: conflicting fb hw usage inteldrmfb vs EFI VGA - removing generic driver I have researched the 'conflicting fb hw ...' message. I do not know if this is related to the problem but the www-posted solutions don't help in my case: 1: try install nivdia proprietary drivers - the NVIDIA installer did not find a card 2: remove gfxmode $linux_gfxmode from grub Other attempts: I have set my BIOS to video: UEFI first (as recommended by the support team from GIGABYTE) but that did not change anything, either - still booting with intel HD graphics only - I have turned off ontel onboard graphics which makes the system to fail booting at all (BIOS reset required to get back) - - Other observations: - The system is not even recognizing the 1920x1080 resolution for intel HD graphics, I have to add it via xrandr. Strangely, when doing so, i get the 1920x1080, but a monitor-error message pops up (this comes from the monitor hardware directly, not from ubuntu) telling me that I am not using a DUAL link DVI cable (which is not true, I do use a DVI-D Dual Link which was perfectly capable of transmitting all high resolutions) - this looks like an intel HD driver issue - but I can clear this error message by pressing a monitor key... - - Description: Ubuntu 14.04.2 LTS - Release: 14.04 + I have turned off intel onboard graphics which makes the system to fail booting at all (BIOS reset required to get back) 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 .tmp.unity.support.test.0: - + ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Mar 6 09:57:08 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: - Intel Corporation ValleyView Gen7 [8086:0f31] (rev 0c) (prog-if 00 [VGA controller]) -Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000] + Intel Corporation ValleyView Gen7 [8086:0f31] (rev 0c) (prog-if 00 [VGA controller]) + Subsystem: Gigabyte Technology Co.,
[Touch-packages] [Bug 1430459] Re: Mouse not working
Kyler Pierce, thank you for reporting this and helping make Ubuntu better. Could you please test for this via http://cdimage.ubuntu.com /daily-live/current/ and advise to the results? ** Tags added: latest-bios-a17 ** Changed in: xorg (Ubuntu) Importance: Undecided = Medium ** Changed in: xorg (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1430459 Title: Mouse not working Status in xorg package in Ubuntu: Incomplete Bug description: USB mouse worked fine upon installation. Has since stopped working. Unplug and plug in does not fix. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-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 10 12:39:25 2015 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.248+bdcom, 3.16.0-31-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:022f] Subsystem: Dell Device [1028:022f] InstallationDate: Installed on 2015-03-10 (0 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: Dell Inc. Inspiron 1525 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-31-generic root=UUID=60e2d5d1-f3aa-4e89-b9bf-0cf49e479a33 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/27/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0U990C dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd10/27/2009:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn0U990C:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1525 dmi.sys.vendor: Dell Inc. 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 10 12:00:35 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 769 vendor LPL xserver.version: 2:1.16.0-1ubuntu1.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1430459/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1436538] Re: brigtness slider should not allow total darkness
@Matthew I guess I was assuming that the reset-all-system-settings option could be provided via the boot options available after pressing the power+VolUp buttons (I'm assuming here that the secondary menu made available when pressing VolUp during the recovery boot is not suitable, as it looked like that was part of the Android stack, but might be wrong). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1436538 Title: brigtness slider should not allow total darkness Status in the base for Ubuntu mobile products: Fix Released Status in indicator-power package in Ubuntu: Invalid Bug description: bq aquaris 4.5, Utopic Unicorn 20150312-002053: slider allows to minimize the brightess to the point of not seeing at all. Even if you manage to reboot (you don't see the confirmation dialogue) you still have completly dark display which effectively bricks the phone (no battery removal) unless you are patient enought to blindly try and hit long time enough to increase the brigtness again. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1436538/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1445271] Re: Try to preview multiple pages per sheet into print dialog does not work.
Yes, ,it has been reported here: https://bugzilla.gnome.org/show_bug.cgi?id=748030 2015-04-17 10:37 GMT+02:00, Sebastien Bacher seb...@ubuntu.com: Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1445271 Title: Try to preview multiple pages per sheet into print dialog does not work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1445271/+subscriptions -- El que no quiere razonar es un fanático; el que no sabe razonar es un necio; el que no se atreve a razonar es un esclavo. W.Drummond. ** Bug watch added: GNOME Bug Tracker #748030 https://bugzilla.gnome.org/show_bug.cgi?id=748030 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1445271 Title: Try to preview multiple pages per sheet into print dialog does not work. Status in gtk+3.0 package in Ubuntu: New Bug description: Ubuntu 14.10 (Unity) amd64 Cups: 1.7.5-3ubuntu3.1 hplip: 3.14.6-1ubuntu1 libgtk-3-0:amd 3.12.2-0ubun amd64 Example with Evince program: I try to preview into print dialog 2 (or more) pages per sheet.With a PDF file, the opened preview windows shows only an empty page when I choose 2 pages per sheet, and only shows one miniature page ( but several pages are show stacked on top of each other, overlapping ) when choose 4 or more pages per sheet . The same file, but convert to POSTSCRIPT (with pdftops ), shows always only 1 page, no matter what number of pages per sheet I choose. The same behaviors occurs with GEdit program for example. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1445271/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1444166] Re: closing lid does not suspend while system is not fully booted
Turns out this was actually intentional. A recent upstream commit improved this: http://cgit.freedesktop.org/systemd/systemd/commit/?id=9d10cbee8 With that the dead time got reduced from 3 mins to 30s, which ought to be fine. ** Changed in: systemd (Ubuntu) Status: Triaged = In Progress ** Summary changed: - closing lid does not suspend while system is not fully booted + closing lid does not suspend in the first 3 minutes after boot -- 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/1444166 Title: closing lid does not suspend in the first 3 minutes after boot Status in systemd package in Ubuntu: In Progress Bug description: Right after booting, closing the lid does not cause a suspend. logind does see the lid close/open event, but there is no suspend. After some minutes this starts working, and from then on always works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1444166/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1430156] Re: Boot errors
Reggie Daniels, thank you for reporting this and helping make Ubuntu better. First, please pull the disk with Windows on it completely out of the chassis until you want to actually use it, in order to prevent accidentally overwriting it or mis-modifying it. Next, with the other disk still in the chassis, could you please test http://cdimage.ubuntu.com/daily-live/current/ and advise to the results? ** Changed in: xorg (Ubuntu) Importance: Undecided = Low ** Changed in: xorg (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1430156 Title: Boot errors Status in xorg package in Ubuntu: Incomplete Bug description: After installing ubuntu14.04.1 onto a separate drive in my home built tower which I already had windows 8.1 pro install on another drive. Before the installation of ubuntu the windows 8.1 was working properly. This is not to say or imply that ubuntu is at fault in this process but instead, my lack of complete understanding of what was involved in the process. Subsequently, I've read lots of tutorials and question/answers on Ubuntu One. The most important of which I read only this morning at 3 AM. It said simply that you can't simply re- install ubuntu on an drive one problems have been encountered. At this point I'm using the drive that I originally installed the ubuntu onto with ubuntu installed and running somewhat errantly. To the point. At first I could still boot into windows 8.1, but there were problems with booting ubuntu. The boot menu then began to display with the windows bios boot option missing. However, I could still enter into the bios and select windows from there by selecting its drive. After trying to figure out what happened to the windows option then, I was no longer able to choose windows from the bios boot. I was at least able to boot into ubuntu with great difficulty. As it began to boot there were lots of fails and quit items displayed on the screen. Things have gone from bad to worse, as I attempted to fix the problem. Of course, I assumed the windows was still there on the original drive. I tried deleting the ubuntu OS and re-installing it and then things really went to hell in a hand basket. I am now at the point where, I've been able to re-install ubuntu, but can see the windows 8.1 on either of the other drives that I have installing in the tower. I've used various of the linux sites to seek ways to recover from this disaster, but have not achieve good results. The xorg information that was sent from the latest boot is beyond my level of knowledge at this point. I would appreciate it very much if someone could walk me through the process of recovery. One of the errors messages Found GPt, add bios-boot partition. Another was Comreset failed error-16. These among many. Please excuse, my lack of detail in this matter I've grasping for straws believing that I could retrieve the system on my own. Given enough time I ultimately could, but at this point I'm putting up the white flag. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-46.77-generic 3.13.11-ckt15 Uname: Linux 3.13.0-46-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.7 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 Date: Mon Mar 9 22:33:56 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7921] InstallationDate: Installed on 2015-02-25 (12 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: MSI MS-7921 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-46-generic root=UUID=cb670b6e-0135-4803-9d60-5c1c64cabc36 ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-G55 SLI (MS-7921) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias:
[Touch-packages] [Bug 1074778] Re: Upgrading to 12.10 created a ~/fontconfig folder but did not delete it
Three years and this bug is still marked just as Confirmed? Oh, boy... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1074778 Title: Upgrading to 12.10 created a ~/fontconfig folder but did not delete it Status in fontconfig package in Ubuntu: Confirmed Bug description: I upgraded from Ubuntu 12.04 to 12.10. In the process, a folder called ~/fontconfig was created and not deleted. This happened on my two machines. More information here: http://askubuntu.com/questions/202796/what-is- the-fontconfig-folder-in-my-home-may-i-delete-it ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: fontconfig 2.10.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Sat Nov 3 18:57:29 2012 InstallationDate: Installed on 2012-04-29 (188 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MarkForUpload: True SourcePackage: fontconfig UpgradeStatus: Upgraded to quantal on 2012-10-20 (14 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1074778/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1445754] [NEW] package isc-dhcp-server 4.2.4-7ubuntu12.1 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1
Public bug reported:
ubuntu 14.04 LTS
dpkg -l | grep isc-dhcp-server
iF isc-dhcp-server 4.2.4-7ubuntu12.1
i386
I just did an apt-get upgrade, and it complained about dhcp server
upgrade failure.
This upgrade left it unstartable :
invoke-rc.d: initscript isc-dhcp-server, action start failed.
dpkg: error processing package isc-dhcp-server (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
isc-dhcp-server
E: Sub-process /usr/bin/dpkg returned an error code (1)
...
root@:/etc# invoke-rc.d isc-dhcp-server stop
root@:/etc# invoke-rc.d isc-dhcp-server start
start: Job failed to start
invoke-rc.d: initscript isc-dhcp-server, action start failed.
My configuration is very simple : /etc/dhcp/dhcpd.conf and default
interface is eth0
subnet 192.168.2.0 netmask 255.255.255.0 {
range 192.168.2.10 192.168.2.100
}
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: isc-dhcp-server 4.2.4-7ubuntu12.1
ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17
Uname: Linux 3.13.0-49-generic i686
ApportVersion: 2.14.1-0ubuntu3.10
Architecture: i386
Date: Sat Apr 18 11:52:02 2015
DhServerLeases:
DuplicateSignature: package:isc-dhcp-server:4.2.4-7ubuntu12.1:le sous-processus
script post-installation installé a retourné une erreur de sortie d'état 1
ErrorMessage: le sous-processus script post-installation installé a retourné
une erreur de sortie d'état 1
InstallationDate: Installed on 2013-05-22 (695 days ago)
InstallationMedia: Xubuntu 13.04 Raring Ringtail - Release i386 (20130423.1)
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-49-generic
root=UUID=4ccdb8ae-fd58-410f-b060-6e5252ae447e ro quiet splash vt.handoff=7
SourcePackage: isc-dhcp
Title: package isc-dhcp-server 4.2.4-7ubuntu12.1 failed to install/upgrade: le
sous-processus script post-installation installé a retourné une erreur de
sortie d'état 1
UpgradeStatus: Upgraded to trusty on 2014-06-29 (292 days ago)
mtime.conffile..etc.dhcp.dhcpd.conf: 2013-10-20T20:05:02.701598
** Affects: isc-dhcp (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-package i386 trusty
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1445754
Title:
package isc-dhcp-server 4.2.4-7ubuntu12.1 failed to install/upgrade:
le sous-processus script post-installation installé a retourné une
erreur de sortie d'état 1
Status in isc-dhcp package in Ubuntu:
New
Bug description:
ubuntu 14.04 LTS
dpkg -l | grep isc-dhcp-server
iF isc-dhcp-server 4.2.4-7ubuntu12.1
i386
I just did an apt-get upgrade, and it complained about dhcp server
upgrade failure.
This upgrade left it unstartable :
invoke-rc.d: initscript isc-dhcp-server, action start failed.
dpkg: error processing package isc-dhcp-server (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
isc-dhcp-server
E: Sub-process /usr/bin/dpkg returned an error code (1)
...
root@:/etc# invoke-rc.d isc-dhcp-server stop
root@:/etc# invoke-rc.d isc-dhcp-server start
start: Job failed to start
invoke-rc.d: initscript isc-dhcp-server, action start failed.
My configuration is very simple : /etc/dhcp/dhcpd.conf and default
interface is eth0
subnet 192.168.2.0 netmask 255.255.255.0 {
range 192.168.2.10 192.168.2.100
}
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: isc-dhcp-server 4.2.4-7ubuntu12.1
ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17
Uname: Linux 3.13.0-49-generic i686
ApportVersion: 2.14.1-0ubuntu3.10
Architecture: i386
Date: Sat Apr 18 11:52:02 2015
DhServerLeases:
DuplicateSignature: package:isc-dhcp-server:4.2.4-7ubuntu12.1:le
sous-processus script post-installation installé a retourné une erreur de
sortie d'état 1
ErrorMessage: le sous-processus script post-installation installé a retourné
une erreur de sortie d'état 1
InstallationDate: Installed on 2013-05-22 (695 days ago)
InstallationMedia: Xubuntu 13.04 Raring Ringtail - Release i386 (20130423.1)
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-49-generic
root=UUID=4ccdb8ae-fd58-410f-b060-6e5252ae447e ro quiet splash vt.handoff=7
SourcePackage: isc-dhcp
Title: package isc-dhcp-server 4.2.4-7ubuntu12.1 failed to install/upgrade:
le sous-processus script post-installation installé a retourné une erreur de
sortie d'état 1
UpgradeStatus: Upgraded to trusty on 2014-06-29 (292 days ago)
mtime.conffile..etc.dhcp.dhcpd.conf: 2013-10-20T20:05:02.701598
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1445754/+subscriptions
--
Mailing list:
[Touch-packages] [Bug 1445755] [NEW] Provide a way to hide images from a particular location
Public bug reported: I've put about 30GB of music in my SD card. Some of the music files don't have embedded cover art and their folders contain those cover art images. When I then opened the Gallery app, I noticed I now have thousands of pictures imported from the cover art images showing up in my Events and Pictures tabs, cluttering the real pictures I've taken with the camera. Is there a way to tell either mediascanner or the Gallery app to ignore a path and not import/show the images there? E.g. similar to Android, where you can put a .nomedia file in a folder and its images won't show up in the picture viewer. ** Affects: gallery-app Importance: Undecided Status: New ** Affects: mediascanner2 Importance: Undecided Status: New ** Affects: gallery-app (Ubuntu) Importance: Undecided Status: New ** Affects: mediascanner2 (Ubuntu) Importance: Undecided Status: New ** Also affects: gallery-app (Ubuntu) Importance: Undecided Status: New ** Also affects: mediascanner2 Importance: Undecided Status: New ** Also affects: mediascanner2 (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Provide a way to hide images + Provide a way to hide images from a particular location -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gallery-app in Ubuntu. https://bugs.launchpad.net/bugs/1445755 Title: Provide a way to hide images from a particular location Status in Gallery App: New Status in Media Scanner v2: New Status in gallery-app package in Ubuntu: New Status in mediascanner2 package in Ubuntu: New Bug description: I've put about 30GB of music in my SD card. Some of the music files don't have embedded cover art and their folders contain those cover art images. When I then opened the Gallery app, I noticed I now have thousands of pictures imported from the cover art images showing up in my Events and Pictures tabs, cluttering the real pictures I've taken with the camera. Is there a way to tell either mediascanner or the Gallery app to ignore a path and not import/show the images there? E.g. similar to Android, where you can put a .nomedia file in a folder and its images won't show up in the picture viewer. To manage notifications about this bug go to: https://bugs.launchpad.net/gallery-app/+bug/1445755/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1429766] Re: Alt+Left/RightArrow switches from graphic into text virtual console (Vivid)
Wladimir Mutel, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1429766/comments/4 regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find. ** Changed in: xorg (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1429766 Title: Alt+Left/RightArrow switches from graphic into text virtual console (Vivid) Status in xorg package in Ubuntu: Invalid Bug description: After some dist-upgrades of my Vivid testing system I noticed that Alt+Left/Right started to switch from GUI into prev/next text virtual console (as well as prev/next web page in Web browser which I used to using). I would like to restore their function back as expected (web page navigation only, not VConsoles). Please advise on what to reconfigure or downgrade. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu2 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: KDE Date: Mon Mar 9 11:08:19 2015 InstallationDate: Installed on 2009-11-01 (1953 days ago) InstallationMedia: Kubuntu 9.10 Karmic Koala - Release amd64 (20091027) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1429766/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1445754] Re: package isc-dhcp-server 4.2.4-7ubuntu12.1 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1445754
Title:
package isc-dhcp-server 4.2.4-7ubuntu12.1 failed to install/upgrade:
le sous-processus script post-installation installé a retourné une
erreur de sortie d'état 1
Status in isc-dhcp package in Ubuntu:
New
Bug description:
ubuntu 14.04 LTS
dpkg -l | grep isc-dhcp-server
iF isc-dhcp-server 4.2.4-7ubuntu12.1
i386
I just did an apt-get upgrade, and it complained about dhcp server
upgrade failure.
This upgrade left it unstartable :
invoke-rc.d: initscript isc-dhcp-server, action start failed.
dpkg: error processing package isc-dhcp-server (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
isc-dhcp-server
E: Sub-process /usr/bin/dpkg returned an error code (1)
...
root@:/etc# invoke-rc.d isc-dhcp-server stop
root@:/etc# invoke-rc.d isc-dhcp-server start
start: Job failed to start
invoke-rc.d: initscript isc-dhcp-server, action start failed.
My configuration is very simple : /etc/dhcp/dhcpd.conf and default
interface is eth0
subnet 192.168.2.0 netmask 255.255.255.0 {
range 192.168.2.10 192.168.2.100
}
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: isc-dhcp-server 4.2.4-7ubuntu12.1
ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17
Uname: Linux 3.13.0-49-generic i686
ApportVersion: 2.14.1-0ubuntu3.10
Architecture: i386
Date: Sat Apr 18 11:52:02 2015
DhServerLeases:
DuplicateSignature: package:isc-dhcp-server:4.2.4-7ubuntu12.1:le
sous-processus script post-installation installé a retourné une erreur de
sortie d'état 1
ErrorMessage: le sous-processus script post-installation installé a retourné
une erreur de sortie d'état 1
InstallationDate: Installed on 2013-05-22 (695 days ago)
InstallationMedia: Xubuntu 13.04 Raring Ringtail - Release i386 (20130423.1)
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-49-generic
root=UUID=4ccdb8ae-fd58-410f-b060-6e5252ae447e ro quiet splash vt.handoff=7
SourcePackage: isc-dhcp
Title: package isc-dhcp-server 4.2.4-7ubuntu12.1 failed to install/upgrade:
le sous-processus script post-installation installé a retourné une erreur de
sortie d'état 1
UpgradeStatus: Upgraded to trusty on 2014-06-29 (292 days ago)
mtime.conffile..etc.dhcp.dhcpd.conf: 2013-10-20T20:05:02.701598
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1445754/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1445771] [NEW] add-apt-repository crashes when adding invalid ppa
Public bug reported: sudo add-apt-repository ppa:tasty/sandwich screenshot with the error http://i.imgur.com/MCxqI3u.png ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1445771 Title: add-apt-repository crashes when adding invalid ppa Status in software-properties package in Ubuntu: New Bug description: sudo add-apt-repository ppa:tasty/sandwich screenshot with the error http://i.imgur.com/MCxqI3u.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1445771/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1432139] Re: The font on screen ar distorted and i am not able to read them
Shad, thank you for reporting this and helping make Ubuntu better. As per http://www.dell.com/support/home/us/en/19/product- support/product/inspiron-1440/drivers an update to your computer's buggy and outdated BIOS is available (A07). If you update to this following https://help.ubuntu.com/community/BIOSUpdate does it change anything? If it doesn't, could you please both specify what happened, and provide the output of the following terminal command: sudo dmidecode -s bios-version sudo dmidecode -s bios-release-date For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette . Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful. As well, you don't have to create a new bug report. Once the BIOS is updated, and the information above is provided, then please mark this report Status Confirmed. Thank you for your understanding. ** Tags added: bios-outdated-a07 ** Changed in: xorg (Ubuntu) Importance: Undecided = Low ** Changed in: xorg (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1432139 Title: The font on screen ar distorted and i am not able to read them Status in xorg package in Ubuntu: Incomplete Bug description: The font on screen ar distorted and i am not able to read them. I have taken the screenshots. This bug can be seen in the menu and the taskbar ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-31.43-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 .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: Sat Mar 14 16:13:28 2015 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.125, 3.16.0-31-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:02cf] Subsystem: Dell Device [1028:02cf] InstallationDate: Installed on 2014-10-31 (134 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: Dell Inc. Inspiron 1440 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-31-generic root=UUID=fdabc773-5d60-4e7e-bc18-c3f5f885b7d7 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0K138P dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd10/20/2009:svnDellInc.:pnInspiron1440:pvr:rvnDellInc.:rn0K138P:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1440 dmi.sys.vendor: Dell Inc. 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: Sat Mar 14 14:30:04 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 21569 vendor SEC xserver.version: 2:1.16.0-1ubuntu1.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1432139/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1431672] Re: crashed with SIGSEGR APPORT VERSION
jl allard, thank you for reporting this and helping make Ubuntu better. However, your crash report is missing. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. First, execute at a terminal: cd /var/crash sudo rm * ; sudo apt-get update sudo apt-get -y upgrade sudo service apport start force_start=1 If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart. Now reproduce the crash, then open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit. If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'. If you run the command against the crash report and a window pops up asking you to report this, but then never opens a new report, you would be affected by https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921 . In order to WORKAROUND this, one would need to open the following file via a command line: sudo nano /etc/apport/crashdb.conf and comment out the line: 'problem_types': ['Bug', 'Package'], by changing it to: # 'problem_types': ['Bug', 'Package'], Save, close, and try to file the crash report again via: ubuntu-bug /var/crash/_my_crash_report.crash I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Please feel free to subscribe me to this new report. Also, please do not attach your crash report manually to this report and reopen it. Thank you for your understanding. Helpful bug reporting tips: https://wiki.ubuntu.com/ReportingBugs ** Changed in: xorg (Ubuntu) Status: New = 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/1431672 Title: crashed with SIGSEGR APPORT VERSION Status in xorg package in Ubuntu: Invalid Bug description: /apps/compiz-/general0/options/active_plugins ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.16.0-31.43~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 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Mar 12 20:55:34 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Gateway, Inc. Device [107b:0366] Subsystem: Gateway, Inc. Device [107b:0366] InstallationDate: Installed on 2015-03-12 (0 days ago) InstallationMedia: Ubuntu-GNOME 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Gateway MX6943M PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=es_MX:es PATH=(custom, no user) LANG=es_MX.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-31-generic root=UUID=53e181ac-52a8-4fa3-a1ef-8a7c0471dce3 ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2007 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 77.10 dmi.board.vendor: Gateway dmi.board.version: 77.10 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 8 dmi.chassis.vendor: Gateway dmi.chassis.version: Rev.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr77.10:bd03/06/2007:svnGateway:pnMX6943M:pvr3408141R:rvnGateway:rn:rvr77.10:cvnGateway:ct8:cvrRev.1: dmi.product.name: MX6943M dmi.product.version: 3408141R dmi.sys.vendor: Gateway version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1~ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati:
[Touch-packages] [Bug 953875] Re: Encrypted swap no longer mounted at bootup
** Changed in: systemd (Debian) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/953875 Title: Encrypted swap no longer mounted at bootup Status in eCryptfs: Fix Released Status in systemd: Confirmed Status in ecryptfs-utils package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Fix Released Status in ecryptfs-utils source package in Vivid: Fix Released Status in systemd source package in Vivid: Fix Released Status in ubiquity source package in Vivid: Fix Released Status in systemd package in Debian: Fix Released Bug description: SUMMARY === During installation with encrypt my home folder mode, a broken /etc/crypttab gets created which defines a non-existing swap device (usually cryptswap1) with a UUID. This will also be put into /etc/fstab. As after installation the UUID does not exist, such systems don't have any actual swap. UPGRADE FIX === An upgrade to Ubuntu 15.04 (vivid) will detect and comment out these broken swap devices from /etc/fstab and /etc/crypttab. If you actually want to use those, do these steps: - Find the swap device that was meant to be used in sudo fdisk -l (it should say Linux swap in the last column), remember the device name (something like /dev/sda5) - Find the UUID in /etc/crypttab (the long alphanumeric ID after UUID=) - Run sudo mkswap -U 1234... /dev/sda5, replacing 1234 with the above UUID, and /dev/sda5 with the device name from step 1. - Edit /etc/crypttab to append ,offset=1024 in the fourth (last) column of the cryptswap1 line; ensure that there is *no space* between the cipher=aes-cbc-essiv:sha256 and the appended option. If there is a leading # in the file, remove that too. - If there is a leading # in /etc/fstab in the line starting with /dev/mapper/cryptswap1 line, remove that. - Run sudo update-initramfs -u. ORIGINAL REPORT === Clean install of 12.04 and with encrypted home for my user. Did all updates and now the bootup hangs waiting for swap to become available and it never seems to ever finish. The 200GB SSD below is my boot drive and root filesystem. alan@mesh:~$ sudo swapon -a [sudo] password for alan: swapon: /dev/mapper/cryptswap1: stat failed: No such file or directory alan@mesh:~$ grep swap /etc/fstab # swap was on /dev/sdg5 during installation #UUID=22d3f7f0-f715-4582-81ba-dcbd4cdd1495 noneswapsw 0 0 /dev/mapper/cryptswap1 none swap sw 0 0 alan@mesh:~$ sudo fdisk -l Disk /dev/sda: 115.0 GB, 115033153536 bytes 255 heads, 63 sectors/track, 13985 cylinders, total 224674128 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x000ba2ed Device Boot Start End Blocks Id System /dev/sda1 *2048 206847 1024007 HPFS/NTFS/exFAT /dev/sda2 206848 224671743 1122324487 HPFS/NTFS/exFAT Disk /dev/sdb: 200.0 GB, 200049647616 bytes 255 heads, 63 sectors/track, 24321 cylinders, total 390721968 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0xf0fa0806 Device Boot Start End Blocks Id System /dev/sdb12048 349304831 1746513927 HPFS/NTFS/exFAT /dev/sdb2 374722558 390721535 79994895 Extended /dev/sdb3 * 349304832 37472051112707840 83 Linux /dev/sdb5 374722560 390721535 7999488 82 Linux swap / Solaris Partition table entries are not in disk order ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libecryptfs0 96-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9 Uname: Linux 3.2.0-18-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.94.1-0ubuntu2 Architecture: amd64 Date: Tue Mar 13 09:56:56 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120215) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: ecryptfs-utils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ecryptfs/+bug/953875/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1427668] Re: IT SLOWED MY PC
KIRAN, thank you for taking the time to report this and helping to make Ubuntu better. Unfortunately, this report didn't include enough information. You may find it helpful to read How to report bugs effectively http://www.chiark.greenend.org.uk/~sgtatham/bugs.html and https://wiki.ubuntu.com/ReportingBugs . We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem, 2. The behavior you expected, and 3. The behavior you actually encountered (in as much detail as possible). Thank you for your understanding. ** Tags added: latest-bios-r0170dc ** Changed in: xorg (Ubuntu) Importance: Undecided = Low ** Changed in: xorg (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1427668 Title: IT SLOWED MY PC Status in xorg package in Ubuntu: Incomplete Bug description: IT STARTED TO SLOW MY PC AND STOPED SUPPORTING PHONES AND STOPED SUPPORTING BLUETOOTH. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.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 Date: Tue Mar 3 18:14:16 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.141+bdcom, 3.13.0-32-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8510G] [1002:] (prog-if 00 [VGA controller]) Subsystem: Sony Corporation Device [104d:90c1] InstallationDate: Installed on 2015-02-16 (15 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Sony Corporation SVF15413SNB ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic.efi.signed root=UUID=03ef7318-31de-4db7-8f0b-012ff5b0903d ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: R0170DC dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnInsydeCorp.:bvrR0170DC:bd11/18/2013:svnSonyCorporation:pnSVF15413SNB:pvrC10K7YWN:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: SVF15413SNB dmi.product.version: C10K7YWN dmi.sys.vendor: Sony Corporation 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 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 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Mar 3 14:32:08 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1427668/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1427511] Re: No display on boot after the initial few screens
Manoj Bhataria, thank you for reporting this and helping make Ubuntu better. As per http://www.asus.com/Notebooks_Ultrabooks/X200MA/HelpDesk_Download/ an update to your computer's buggy and outdated BIOS is available (504). If you update to this following https://help.ubuntu.com/community/BIOSUpdate does it change anything? If it doesn't, could you please both specify what happened, and provide the output of the following terminal command: sudo dmidecode -s bios-version sudo dmidecode -s bios-release-date For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette . Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful. As well, you don't have to create a new bug report. Once the BIOS is updated, and the information above is provided, then please mark this report Status New. Thank you for your understanding. ** Tags added: bios-outdated-504 ** Changed in: xorg (Ubuntu) Importance: Undecided = Low ** Changed in: xorg (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1427511 Title: No display on boot after the initial few screens Status in xorg package in Ubuntu: Incomplete Bug description: I have been using the Asus X200M netbook for the past 3-4 months. I have loaded 14.04 LTS using a USB stick. Last week when I powered on my system, after the initial few screens, the display goes completely blank. I know that my display is fine and there is no loose connection since it it alive for few seconds after power on. It also displays the Grub menu. It is after I select Ubuntu that the display goes blank. If I select the recovery mode and select normal boot then it boots correctly. 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 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.7 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 Date: Tue Mar 3 10:18:58 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation ValleyView Gen7 [8086:0f31] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:15bd] InstallationDate: Installed on 2014-10-06 (147 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB Bus 001 Device 002: ID 0bda:5603 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X200MA ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-46-generic.efi.signed root=UUID=0283848c-3aa5-47c9-9ad6-9c1a4725e0f8 ro vesafb.invalid=1 drm.debug=0xe nopat plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/21/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X200MA.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X200MA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX200MA.302:bd01/21/2014:svnASUSTeKCOMPUTERINC.:pnX200MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX200MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X200MA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1~ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.3 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Mar 3 09:21:31 2015
[Touch-packages] [Bug 1428020] Re: when running navit X Server crashes
tom king, thank you for reporting this and helping make Ubuntu better. Could you please provide the full computer manufacturer and model as noted on the sticker of the computer itself (not from the Bug Description)? ** Changed in: xorg (Ubuntu) Importance: Undecided = Low ** Changed in: xorg (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1428020 Title: when running navit X Server crashes Status in xorg package in Ubuntu: Incomplete Bug description: Description: Ubuntu 14.04.2 LTS Release: 14.04 xorg: Installed: 1:7.7+1ubuntu8.1 Candidate: 1:7.7+1ubuntu8.1 Version table: *** 1:7.7+1ubuntu8.1 0 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:7.7+1ubuntu8 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages --- grep EE Xorg.0.debug.log.old (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 8.193] Initializing built-in extension MIT-SCREEN-SAVER [ 8.202] (EE) Failed to load module nvidia (module does not exist, 0) [ 8.203] (EE) Failed to load module nvidia (module does not exist, 0) [10.214] (EE) NOUVEAU(G0): Failed to initialise context object: 2D_NVC0 (0) [10.215] (EE) NOUVEAU(G0): Error initialising acceleration. Falling back to NoAccel [20.954] (EE) [20.954] (EE) Backtrace: [20.955] (EE) 0: /usr/bin/X (xorg_backtrace+0x48) [0x7fc32acd5848] [20.955] (EE) 1: /usr/bin/X (0x7fc32ab2c000+0x1ad539) [0x7fc32acd9539] [20.955] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7fc329c29000+0x10340) [0x7fc329c39340] [20.955] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fc324693000+0xd9168) [0x7fc32476c168] [20.955] (EE) 4: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fc324693000+0x2d540) [0x7fc3246c0540] [20.955] (EE) 5: /usr/bin/X (0x7fc32ab2c000+0x19ce55) [0x7fc32acc8e55] [20.955] (EE) 6: /usr/bin/X (0x7fc32ab2c000+0x19f281) [0x7fc32accb281] [20.955] (EE) 7: /usr/bin/X (miWideDash+0x142b) [0x7fc32acccf3b] [20.955] (EE) 8: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fc324693000+0x4c3de) [0x7fc3246df3de] [20.955] (EE) 9: /usr/bin/X (0x7fc32ab2c000+0x1361d8) [0x7fc32ac621d8] [20.955] (EE) 10: /usr/bin/X (0x7fc32ab2c000+0x5277f) [0x7fc32ab7e77f] [20.955] (EE) 11: /usr/bin/X (0x7fc32ab2c000+0x55f0e) [0x7fc32ab81f0e] [20.955] (EE) 12: /usr/bin/X (0x7fc32ab2c000+0x59d9a) [0x7fc32ab85d9a] [20.955] (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf5) [0x7fc328669ec5] [20.955] (EE) 14: /usr/bin/X (0x7fc32ab2c000+0x451ee) [0x7fc32ab711ee] [20.955] (EE) [20.955] (EE) Segmentation fault at address 0x7fff1d6a3004 [20.955] (EE) [20.955] (EE) Caught signal 11 (Segmentation fault). Server aborting [20.955] (EE) [20.955] (EE) [20.955] (EE) Please also check the log file at /var/log/Xorg.0.log for additional information. [20.955] (EE) [20.983] (EE) Server terminated with error (1). Closing log file. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-46.77-generic 3.13.11-ckt15 Uname: Linux 3.13.0-46-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.7 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 Date: Wed Mar 4 18:28:32 2015 DistUpgraded: 2014-10-07 19:02:16,253 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:5281] NVIDIA Corporation GK104M [GeForce GTX 870M] [10de:1199] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:5281] InstallationDate: Installed on 2014-10-07 (147 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Notebook P15SM-A/SM1-A ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-46-generic root=/dev/mapper/ubuntu--vg-root ro plymouth:debug drm.debug=0xe pci-assign-busses=1 SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-10-07 (147 days ago) dmi.bios.date: 09/12/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag:
[Touch-packages] [Bug 1414516] Re: Ubuntu 14.10 sees logitech k810 bluetooth keyboard battery as a system/laptop battery
Is there any workaround for this issue? I am have the same outcome with the Logitech K810. -- 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/1414516 Title: Ubuntu 14.10 sees logitech k810 bluetooth keyboard battery as a system/laptop battery Status in upower package in Ubuntu: Confirmed Bug description: This is a HP desktop computer using a IOGEAR USB Bluetooth dongle. When I enable the logitech k810 keyboard the OS behaves like it's on battery power. Inside the power management GUI under Power Settings the What to do when power is critically low selection is set to Power Off, and I can't select another option. Here's the output of upower -d rob@hp-ubuntu:~$ upower -d Device: /org/freedesktop/UPower/devices/battery_hid_00o1fo20o92o1bo18_battery native-path: hid-00:1f:20:92:1b:18-battery model:Logitech K810 power supply: no updated: Sun 25 Jan 2015 07:02:46 PM CST (5 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable:yes state: discharging energy: 0 Wh energy-empty:0 Wh energy-full: 0 Wh energy-full-design: 0 Wh energy-rate: 0 W percentage: 85% capacity:100% Daemon: daemon-version: 0.9.23 can-suspend: yes can-hibernate: no on-battery: no on-low-battery: no lid-is-closed: no lid-is-present: no is-docked: no ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: upower 0.9.23-2ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2 Uname: Linux 3.16.0-29-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jan 25 18:57:04 2015 InstallationDate: Installed on 2015-01-14 (11 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: upower UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1414516/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1445596] Re: lenovo t410 [2537BF9, Conexant CX20585, Speaker, Internal] fails after a while
** Attachment added: Result from alsa-info.sh while sound was playing https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1445596/+attachment/4379074/+files/speakerOK -- 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/1445596 Title: lenovo t410 [2537BF9, Conexant CX20585, Speaker, Internal] fails after a while Status in alsa-driver package in Ubuntu: New Bug description: after a suspend the sound works for a while and then stops again Sound used to work with Ubuntu 12.04, but after an update it showed the same symptoms. So I tried the latest Ubuntu version but still same problem. Headphones always woirk ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3 Uname: Linux 3.19.0-14-generic x86_64 ApportVersion: 2.17.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: bruno 1215 F...m pulseaudio /dev/snd/controlC0: bruno 1215 F pulseaudio CurrentDesktop: Unity Date: Fri Apr 17 19:51:41 2015 InstallationDate: Installed on 2015-03-29 (19 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Beta amd64 (20150326) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel MID Symptom_Jack: Speaker, Internal Symptom_Type: Sound works for a while, then breaks Title: [2537BF9, Conexant CX20585, Speaker, Internal] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/14/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET85WW (1.45 ) dmi.board.name: 2537BF9 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: 2537R8M1NHK dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6IET85WW(1.45):bd02/14/2013:svnLENOVO:pn2537BF9:pvrThinkPadT410:rvnLENOVO:rn2537BF9:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2537BF9 dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1445596/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1445596] Re: lenovo t410 [2537BF9, Conexant CX20585, Speaker, Internal] fails after a while
Find attached the a script used to read out information while sound was working and after it stopped ** Attachment added: Script to read alsa information https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1445596/+attachment/4379073/+files/alsa-info.sh -- 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/1445596 Title: lenovo t410 [2537BF9, Conexant CX20585, Speaker, Internal] fails after a while Status in alsa-driver package in Ubuntu: New Bug description: after a suspend the sound works for a while and then stops again Sound used to work with Ubuntu 12.04, but after an update it showed the same symptoms. So I tried the latest Ubuntu version but still same problem. Headphones always woirk ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3 Uname: Linux 3.19.0-14-generic x86_64 ApportVersion: 2.17.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: bruno 1215 F...m pulseaudio /dev/snd/controlC0: bruno 1215 F pulseaudio CurrentDesktop: Unity Date: Fri Apr 17 19:51:41 2015 InstallationDate: Installed on 2015-03-29 (19 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Beta amd64 (20150326) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel MID Symptom_Jack: Speaker, Internal Symptom_Type: Sound works for a while, then breaks Title: [2537BF9, Conexant CX20585, Speaker, Internal] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/14/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET85WW (1.45 ) dmi.board.name: 2537BF9 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: 2537R8M1NHK dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6IET85WW(1.45):bd02/14/2013:svnLENOVO:pn2537BF9:pvrThinkPadT410:rvnLENOVO:rn2537BF9:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2537BF9 dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1445596/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1419645] Re: [Dialer] dialer screen focussed after receiving a call
** Tags added: usability ** Description changed: Using rtm 228 on krillin - have your phone on the dash (nothing is running) or with an application in use (ie. the webbrowser) - receive a call - look at your phone after the call The dialer-app is open and focussed, it shouldn't, answering a phone shouldn't return the device in a state different from the one it was before talking. If you were using the webbrowser you probably want to keep doing that rather than dial a new number Opening against unity8 since that's an application management issue, not sure if that's the correct component though + + UX comment--- + + I agree, this is a bad user experience. As proposed in the bug description: + After user hangs up an accepted call, the previously used app should be back in view. ** 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 dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1419645 Title: [Dialer] dialer screen focussed after receiving a call Status in the base for Ubuntu mobile products: New Status in Ubuntu UX bugs: Fix Committed Status in dialer-app package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: Using rtm 228 on krillin - have your phone on the dash (nothing is running) or with an application in use (ie. the webbrowser) - receive a call - look at your phone after the call The dialer-app is open and focussed, it shouldn't, answering a phone shouldn't return the device in a state different from the one it was before talking. If you were using the webbrowser you probably want to keep doing that rather than dial a new number Opening against unity8 since that's an application management issue, not sure if that's the correct component though UX comment--- I agree, this is a bad user experience. As proposed in the bug description: After user hangs up an accepted call, the previously used app should be back in view. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1419645/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1438422] Re: Hybrid laptop's accelerometer tilt interpreted as WiFi hardware switch
I'm tempted to think this is a bug either in the kernel, X or the input handling - because it seems more to do with what the interpretation of key input (that happens to be how the accelerator signals?) than actual actions. What happens if you try booting with 14.10 kernel but leave everything else the same? -- 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/1438422 Title: Hybrid laptop's accelerometer tilt interpreted as WiFi hardware switch Status in compiz package in Ubuntu: Invalid Status in gnome-session package in Ubuntu: New Status in network-manager package in Ubuntu: New Status in urfkill package in Ubuntu: New Bug description: This bug appears to be a regression in Vivid sometime in the second half of March 2015. When the machine is tilted (e.g., onto its side), Syslog reports an unknown button being pressed. When tilted back to the normal laptop position, the machine's WiFi disconnects and is shown as disabled in the connection manager. Syslog indicates that urfkill registered a hardware switch cutoff for the WiFi. I know that the accelerometers do work in other contexts and can be read properly in Ubuntu. As an example, this orient script works for me: https://github.com/leszakk/orient . Hardware: HP Envy x360 15t -- this is a hybrid touch notebook OS: Ubuntu 15.04 Beta 2 -- Desktop version Kernel: 3.19.0-10-generic urfkill: Installed: 0.6.0~20150318.103828.5539c0d.1-0ubuntu1 Candidate: 0.6.0~20150318.103828.5539c0d.1-0ubuntu1 Version table: *** 0.6.0~20150318.103828.5539c0d.1-0ubuntu1 0 500 http://mirrors.mit.edu/ubuntu/ vivid/universe amd64 Packages 100 /var/lib/dpkg/status Below is a Syslog readout from a test event. The notebook starts in normal typing position, the hinge bent at a right angle. At 16:13:30, without moving the hinge, I tip the notebook 90 degrees to the left from my perspective. So the Unity launcher is now closest to the floor, for example. I hold it there for about 10 seconds until 16:13:40. Mar 30 16:13:30 [my_hostname] kernel: [ 1327.717086] atkbd serio0: Unknown key pressed (translated set 2, code 0xd8 on isa0060/serio0). Mar 30 16:13:30 [my_hostname] kernel: [ 1327.717098] atkbd serio0: Use 'setkeycodes e058 keycode' to make it known. Mar 30 16:13:30 [my_hostname] kernel: [ 1327.724168] atkbd serio0: Unknown key released (translated set 2, code 0xd8 on isa0060/serio0). Mar 30 16:13:30 [my_hostname] kernel: [ 1327.724180] atkbd serio0: Use 'setkeycodes e058 keycode' to make it known. Mar 30 16:13:41 [my_hostname] URfkill[868]: Setting WLAN devices to blocked Mar 30 16:13:41 [my_hostname] URfkill[868]: set_soft: Setting WLAN to blocked Mar 30 16:13:41 [my_hostname] kernel: [ 1338.698934] wlan0: deauthenticating from [ma:ca:dd:re:ss] by local choice (Reason: 3=DEAUTH_LEAVING) Mar 30 16:13:41 [my_hostname] wpa_supplicant[1015]: wlan0: CTRL-EVENT-DISCONNECTED bssid=[ma:ca:dd:re:ss] reason=3 locally_generated=1 Mar 30 16:13:41 [my_hostname] kernel: [ 1338.710906] cfg80211: Calling CRDA to update world regulatory domain Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Interface wlan0.IPv6 no longer relevant for mDNS. Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::8286:f2ff:fe32:def8. Mar 30 16:13:41 [my_hostname] dhclient: receive_packet failed on wlan0: Network is down Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Interface wlan0.IPv4 no longer relevant for mDNS. Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.133. Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Withdrawing address record for fe80::8286:f2ff:fe32:def8 on wlan0. Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Withdrawing address record for 192.168.1.133 on wlan0. Mar 30 16:13:41 [my_hostname] URfkill[868]: device_changed_cb: phy0 Mar 30 16:13:41 [my_hostname] NetworkManager[863]: warn Connection disconnected (reason -3) Mar 30 16:13:41 [my_hostname] NetworkManager[863]: error [1427746421.849186] [platform/nm-linux-platform.c:1714] add_object(): Netlink error adding 0.0.0.0/0 via 192.168.1.1 dev wlan0 metric 1024 mss 0 src user: Unspecific failure Mar 30 16:13:41 [my_hostname] NetworkManager[863]: error [1427746421.849417] [platform/nm-linux-platform.c:1714] add_object(): Netlink error adding 192.168.1.1/32 via 0.0.0.0 dev wlan0 metric 1024 mss 0 src user: Unspecific failure Mar 30 16:13:41 [my_hostname] NetworkManager[863]: error [1427746421.849591] [platform/nm-linux-platform.c:1714] add_object(): Netlink error adding 0.0.0.0/0 via 192.168.1.1 dev wlan0 metric 1024 mss 0 src user: Unspecific failure Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Joining mDNS
[Touch-packages] [Bug 1438422] Re: Hybrid laptop's accelerometer tilt interpreted as WiFi hardware switch
Tested 3.16.0-29 . Bug behavior appeared to be the same. It might also be worth noting that sometimes, even when I re-enable WiFi, the network manager does not recognize available networks. However, I can connect if I choose to connect to a hidden network and then select from a list of potential hidden networks one that I know is active and in range. After that successful connection, network manager begins displaying that and other networks properly. I have assumed that this is just to do with the messy way in which the OS thinks the WiFi has been turned on or off by hardware switch, but maybe it's some kind of clue by itself. -- 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/1438422 Title: Hybrid laptop's accelerometer tilt interpreted as WiFi hardware switch Status in compiz package in Ubuntu: Invalid Status in gnome-session package in Ubuntu: New Status in network-manager package in Ubuntu: New Status in urfkill package in Ubuntu: New Bug description: This bug appears to be a regression in Vivid sometime in the second half of March 2015. When the machine is tilted (e.g., onto its side), Syslog reports an unknown button being pressed. When tilted back to the normal laptop position, the machine's WiFi disconnects and is shown as disabled in the connection manager. Syslog indicates that urfkill registered a hardware switch cutoff for the WiFi. I know that the accelerometers do work in other contexts and can be read properly in Ubuntu. As an example, this orient script works for me: https://github.com/leszakk/orient . Hardware: HP Envy x360 15t -- this is a hybrid touch notebook OS: Ubuntu 15.04 Beta 2 -- Desktop version Kernel: 3.19.0-10-generic urfkill: Installed: 0.6.0~20150318.103828.5539c0d.1-0ubuntu1 Candidate: 0.6.0~20150318.103828.5539c0d.1-0ubuntu1 Version table: *** 0.6.0~20150318.103828.5539c0d.1-0ubuntu1 0 500 http://mirrors.mit.edu/ubuntu/ vivid/universe amd64 Packages 100 /var/lib/dpkg/status Below is a Syslog readout from a test event. The notebook starts in normal typing position, the hinge bent at a right angle. At 16:13:30, without moving the hinge, I tip the notebook 90 degrees to the left from my perspective. So the Unity launcher is now closest to the floor, for example. I hold it there for about 10 seconds until 16:13:40. Mar 30 16:13:30 [my_hostname] kernel: [ 1327.717086] atkbd serio0: Unknown key pressed (translated set 2, code 0xd8 on isa0060/serio0). Mar 30 16:13:30 [my_hostname] kernel: [ 1327.717098] atkbd serio0: Use 'setkeycodes e058 keycode' to make it known. Mar 30 16:13:30 [my_hostname] kernel: [ 1327.724168] atkbd serio0: Unknown key released (translated set 2, code 0xd8 on isa0060/serio0). Mar 30 16:13:30 [my_hostname] kernel: [ 1327.724180] atkbd serio0: Use 'setkeycodes e058 keycode' to make it known. Mar 30 16:13:41 [my_hostname] URfkill[868]: Setting WLAN devices to blocked Mar 30 16:13:41 [my_hostname] URfkill[868]: set_soft: Setting WLAN to blocked Mar 30 16:13:41 [my_hostname] kernel: [ 1338.698934] wlan0: deauthenticating from [ma:ca:dd:re:ss] by local choice (Reason: 3=DEAUTH_LEAVING) Mar 30 16:13:41 [my_hostname] wpa_supplicant[1015]: wlan0: CTRL-EVENT-DISCONNECTED bssid=[ma:ca:dd:re:ss] reason=3 locally_generated=1 Mar 30 16:13:41 [my_hostname] kernel: [ 1338.710906] cfg80211: Calling CRDA to update world regulatory domain Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Interface wlan0.IPv6 no longer relevant for mDNS. Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::8286:f2ff:fe32:def8. Mar 30 16:13:41 [my_hostname] dhclient: receive_packet failed on wlan0: Network is down Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Interface wlan0.IPv4 no longer relevant for mDNS. Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.133. Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Withdrawing address record for fe80::8286:f2ff:fe32:def8 on wlan0. Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Withdrawing address record for 192.168.1.133 on wlan0. Mar 30 16:13:41 [my_hostname] URfkill[868]: device_changed_cb: phy0 Mar 30 16:13:41 [my_hostname] NetworkManager[863]: warn Connection disconnected (reason -3) Mar 30 16:13:41 [my_hostname] NetworkManager[863]: error [1427746421.849186] [platform/nm-linux-platform.c:1714] add_object(): Netlink error adding 0.0.0.0/0 via 192.168.1.1 dev wlan0 metric 1024 mss 0 src user: Unspecific failure Mar 30 16:13:41 [my_hostname] NetworkManager[863]: error [1427746421.849417] [platform/nm-linux-platform.c:1714] add_object(): Netlink error adding 192.168.1.1/32 via 0.0.0.0 dev wlan0 metric 1024 mss 0 src user:
[Touch-packages] [Bug 1270579] Re: On laptops, screen brightness and keyboard backlight isn't memorized between sessions
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-settings-daemon (Ubuntu) Status: New = Confirmed -- 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/1270579 Title: On laptops, screen brightness and keyboard backlight isn't memorized between sessions Status in Dell Sputnik: New Status in One Hundred Papercuts: Won't Fix Status in The Linux Mint Distribution: Confirmed Status in Upstart: Confirmed Status in cinnamon-settings-daemon package in Ubuntu: Confirmed Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in mate-settings-daemon package in Ubuntu: Confirmed Status in upower package in Ubuntu: Confirmed Status in upstart package in Ubuntu: Won't Fix Bug description: HOW TO REPRODUCE: 1. Boot a laptop. 2. Set a different screen (or keyboard) backlight brightness level. 3. Reboot. RESULT: Backlight is not memorized. FIX: Install package from PPA sudo add-apt-repository ppa:nrbrtx/sysvinit-backlight sudo apt-get update sudo apt-get install sysvinit-backlight NOTES: 1. If you have installed previous non-deb version, please remove it carefully manually sudo rm /etc/rc?.d/?25backlight /etc/init.d/brightness /etc/rc?.d/?25brightness 2. If you have installed previous version from my PPA on Ubuntu 14.04 and higher, please reinstall the package by: sudo apt-get purge sysvinit-backlight sudo apt-get install sysvinit-backlight 3. Version 0.1ubuntu1 supports save/restore of keyboard backlight too. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: initscripts 2.88dsf-41ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8 Uname: Linux 3.13.0-4-generic i686 ApportVersion: 2.13.1-0ubuntu1 Architecture: i386 CurrentDesktop: GNOME Date: Sun Jan 19 17:20:26 2014 InstallationDate: Installed on 2013-10-20 (91 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) SourcePackage: sysvinit UpgradeStatus: Upgraded to trusty on 2013-11-19 (61 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1270579/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1270579] Re: On laptops, screen brightness and keyboard backlight isn't memorized between sessions
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mate-settings-daemon (Ubuntu) Status: New = Confirmed -- 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/1270579 Title: On laptops, screen brightness and keyboard backlight isn't memorized between sessions Status in Dell Sputnik: New Status in One Hundred Papercuts: Won't Fix Status in The Linux Mint Distribution: Confirmed Status in Upstart: Confirmed Status in cinnamon-settings-daemon package in Ubuntu: Confirmed Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in mate-settings-daemon package in Ubuntu: Confirmed Status in upower package in Ubuntu: Confirmed Status in upstart package in Ubuntu: Won't Fix Bug description: HOW TO REPRODUCE: 1. Boot a laptop. 2. Set a different screen (or keyboard) backlight brightness level. 3. Reboot. RESULT: Backlight is not memorized. FIX: Install package from PPA sudo add-apt-repository ppa:nrbrtx/sysvinit-backlight sudo apt-get update sudo apt-get install sysvinit-backlight NOTES: 1. If you have installed previous non-deb version, please remove it carefully manually sudo rm /etc/rc?.d/?25backlight /etc/init.d/brightness /etc/rc?.d/?25brightness 2. If you have installed previous version from my PPA on Ubuntu 14.04 and higher, please reinstall the package by: sudo apt-get purge sysvinit-backlight sudo apt-get install sysvinit-backlight 3. Version 0.1ubuntu1 supports save/restore of keyboard backlight too. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: initscripts 2.88dsf-41ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8 Uname: Linux 3.13.0-4-generic i686 ApportVersion: 2.13.1-0ubuntu1 Architecture: i386 CurrentDesktop: GNOME Date: Sun Jan 19 17:20:26 2014 InstallationDate: Installed on 2013-10-20 (91 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) SourcePackage: sysvinit UpgradeStatus: Upgraded to trusty on 2013-11-19 (61 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1270579/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1270579] Re: On laptops, screen brightness and keyboard backlight isn't memorized between sessions
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cinnamon-settings-daemon (Ubuntu) Status: New = Confirmed -- 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/1270579 Title: On laptops, screen brightness and keyboard backlight isn't memorized between sessions Status in Dell Sputnik: New Status in One Hundred Papercuts: Won't Fix Status in The Linux Mint Distribution: Confirmed Status in Upstart: Confirmed Status in cinnamon-settings-daemon package in Ubuntu: Confirmed Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in mate-settings-daemon package in Ubuntu: Confirmed Status in upower package in Ubuntu: Confirmed Status in upstart package in Ubuntu: Won't Fix Bug description: HOW TO REPRODUCE: 1. Boot a laptop. 2. Set a different screen (or keyboard) backlight brightness level. 3. Reboot. RESULT: Backlight is not memorized. FIX: Install package from PPA sudo add-apt-repository ppa:nrbrtx/sysvinit-backlight sudo apt-get update sudo apt-get install sysvinit-backlight NOTES: 1. If you have installed previous non-deb version, please remove it carefully manually sudo rm /etc/rc?.d/?25backlight /etc/init.d/brightness /etc/rc?.d/?25brightness 2. If you have installed previous version from my PPA on Ubuntu 14.04 and higher, please reinstall the package by: sudo apt-get purge sysvinit-backlight sudo apt-get install sysvinit-backlight 3. Version 0.1ubuntu1 supports save/restore of keyboard backlight too. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: initscripts 2.88dsf-41ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8 Uname: Linux 3.13.0-4-generic i686 ApportVersion: 2.13.1-0ubuntu1 Architecture: i386 CurrentDesktop: GNOME Date: Sun Jan 19 17:20:26 2014 InstallationDate: Installed on 2013-10-20 (91 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) SourcePackage: sysvinit UpgradeStatus: Upgraded to trusty on 2013-11-19 (61 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1270579/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1270579] Re: On laptops, screen brightness and keyboard backlight isn't memorized between sessions
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: upower (Ubuntu) Status: New = Confirmed -- 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/1270579 Title: On laptops, screen brightness and keyboard backlight isn't memorized between sessions Status in Dell Sputnik: New Status in One Hundred Papercuts: Won't Fix Status in The Linux Mint Distribution: Confirmed Status in Upstart: Confirmed Status in cinnamon-settings-daemon package in Ubuntu: Confirmed Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in mate-settings-daemon package in Ubuntu: Confirmed Status in upower package in Ubuntu: Confirmed Status in upstart package in Ubuntu: Won't Fix Bug description: HOW TO REPRODUCE: 1. Boot a laptop. 2. Set a different screen (or keyboard) backlight brightness level. 3. Reboot. RESULT: Backlight is not memorized. FIX: Install package from PPA sudo add-apt-repository ppa:nrbrtx/sysvinit-backlight sudo apt-get update sudo apt-get install sysvinit-backlight NOTES: 1. If you have installed previous non-deb version, please remove it carefully manually sudo rm /etc/rc?.d/?25backlight /etc/init.d/brightness /etc/rc?.d/?25brightness 2. If you have installed previous version from my PPA on Ubuntu 14.04 and higher, please reinstall the package by: sudo apt-get purge sysvinit-backlight sudo apt-get install sysvinit-backlight 3. Version 0.1ubuntu1 supports save/restore of keyboard backlight too. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: initscripts 2.88dsf-41ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8 Uname: Linux 3.13.0-4-generic i686 ApportVersion: 2.13.1-0ubuntu1 Architecture: i386 CurrentDesktop: GNOME Date: Sun Jan 19 17:20:26 2014 InstallationDate: Installed on 2013-10-20 (91 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) SourcePackage: sysvinit UpgradeStatus: Upgraded to trusty on 2013-11-19 (61 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1270579/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1444166] Re: closing lid does not suspend in the first 3 minutes after boot
test case/reproducer: http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=experimentalid=b2e4025da31f fix: http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=experimentalid=0d818a247b11 ** Changed in: systemd (Ubuntu) Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1444166 Title: closing lid does not suspend in the first 3 minutes after boot Status in systemd package in Ubuntu: Fix Committed Bug description: Right after booting, closing the lid does not cause a suspend. logind does see the lid close/open event, but there is no suspend. After some minutes this starts working, and from then on always works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1444166/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1439706] Re: FFE: Ubuntu FAN networking support (for linux, iproute2 and ubuntu-fan)
** Branch linked: lp:~ubuntu-branches/ubuntu/vivid/ubuntu-fan/vivid- proposed ** Branch linked: lp:~ubuntu-branches/ubuntu/vivid/iproute2/vivid- proposed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1439706 Title: FFE: Ubuntu FAN networking support (for linux, iproute2 and ubuntu- fan) Status in iproute2 package in Ubuntu: New Status in linux package in Ubuntu: Triaged Bug description: FFE general instructions: The Ubuntu FAN networking support provides for additional addressing within a host system. These addresses are globally accessible within a related group of host systems, and would typically be assigned to LXC containers or Docker instances running on that host. A typical use case for this would be to allow nested containers on a cloud substrate, where the host systems would be guests in that cloud. Each cloud host instance would be able to express multiple addresses to other instances on the same substrate simplifying deployment. The changes consist of fixes for the linux (kernel) and iproute2 packages, as well as a new ubunt-fan package. The support is completely disabled unless the guest opts in. Installation of the ubuntu-fan package, and configuration of it via /etc/default/ubuntu- fan is required before the functionality is expressed. These changes are proposed to allow simpler deployment and addressing of LXC containers and Docker instances on any substrate in a consistent manner without needing cooperation of buy in from that substrate, simply having single instance addresses on that substrate is sufficient. This should be a strong enabler for Ubuntu on those platforms. Additional FFE instructions for linux: The changes for linux add a new IPIP tunnel routing mode which uses a direct address mapping (destination subnet to destination local IP address) allowing a single configuration per node to configure the entire fan network. No existing functionality is changed, and this new mode must be explicitly requested when configuring (via iproute2 see below). The patches have been applied and the resulting package uploaded to a testing PPA: ppa:~apw/ubuntu/fan. Testing is described below. Additional FFE instructions for iproute2: The changes for iproute2 add support for enabling the above IPIP routing mode, and for displaying it once configured. No existing functionality is changed. There is a small risk that the interface chosen could be reused by upstream, but as it is fan specific that is unlikely. The patches have been applied and the resulting package uploaded to a testing PPA: ppa:~apw/ubuntu/fan. Testing is described below. Additional FFE instructions for new ubuntu-fan package: The new ubuntu-fan package enables the fan functionality by configuring a new tunnel configured in Ubuntu FAN mode, and a new bridge which is used to connect consumers to it. Typically this bridge is then used as the host bridge for LXC containers or Docker instances. Additionally a dnsmasq is connected to the bridge to hand out addresses in the host specific range as if they themselves were on the wider network. The source package is uploaded to the PPA: ppa:~apw/ubuntu/fan as ubuntu-fan and represents the master source for this package. Testing of this combination: The above has been tested in combination from the testing PPA: ppa:~apw/ubuntu/fan. These have been tested both locally and on AWS, it has been successfully tested with both LXC containers and Docker instances. === Using the above instructions/checklist, lets draft the FFE below...Once we are happy with it let's delete the notes above and we can subscribe ubuntu-release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1439706/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1323089] Re: wpa_supplicant writes to syslog every 2 minutes
Thank you Anne for describing what looks like one way to fix this for all connections, rather than the easy fix in #24 which only addresses one SSID. But I worry that making wpa_supplicant more quiet will hide messages that are important - what else would be suppressed? So I suspect that the bug should be fixed somewhere else, since it seems clear to me that default installs with popular wifi cards should not spam syslog, and this does seem to be related to only some forms of Intel wifi cards - mostly Centrino I guess. So what is printing this out, which developer explained the workaround (sometime after 2009?), and how do we clean up our syslogs? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1323089 Title: wpa_supplicant writes to syslog every 2 minutes Status in wpa package in Ubuntu: Confirmed Bug description: Ubuntu 14.04 LTS wpasupplicant 2.1-0ubuntu1 wpa_supplicant is writing to syslog every couple of minutes. Example output: May 25 19:57:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 19:57:23 ubuntu wpa_supplicant[1161]: nl80211: send_and_recv-nl_recvmsgs failed: -33 May 25 19:59:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 19:59:23 ubuntu wpa_supplicant[1161]: nl80211: send_and_recv-nl_recvmsgs failed: -33 May 25 20:00:58 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 20:01:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 20:01:24 ubuntu wpa_supplicant[1161]: nl80211: send_and_recv-nl_recvmsgs failed: -33 May 25 20:03:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 20:03:23 ubuntu wpa_supplicant[1161]: nl80211: send_and_recv-nl_recvmsgs failed: -33 May 25 20:05:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 20:05:23 ubuntu wpa_supplicant[1161]: nl80211: send_and_recv-nl_recvmsgs failed: -33 May 25 20:05:58 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 20:07:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 20:07:23 ubuntu wpa_supplicant[1161]: nl80211: send_and_recv-nl_recvmsgs failed: -33 May 25 20:09:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 20:09:23 ubuntu wpa_supplicant[1161]: nl80211: send_and_recv-nl_recvmsgs failed: -33 May 25 20:10:58 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 20:13:18 ubuntu wpa_supplicant[1161]: message repeated 2 times: [ wlan0: CTRL-EVENT-SCAN-STARTED ] May 25 20:13:23 ubuntu wpa_supplicant[1161]: nl80211: send_and_recv-nl_recvmsgs failed: -33 The message seems harmless as far as the network is concerned, meaning there is no problem with the wifi connection. But it's spamming the syslog, making it very difficult to find any other thing there, and it's generating constant writes to disk, and an unnecessarily large syslog file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1323089/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1445215] Re: Unexpected notifiaction about bazillions of voicemails
Once again, but no reboot: I go outside a shopping (where no network gsm). And when network comes, this notification cames up too: Cf attachement. I will underline that it seems we have the same amount of hudge number (max int?) ** Attachment added: screenshot20154118_174133952.png https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1445215/+attachment/4379079/+files/screenshot20154118_174133952.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-messages in Ubuntu. https://bugs.launchpad.net/bugs/1445215 Title: Unexpected notifiaction about bazillions of voicemails Status in indicator-messages package in Ubuntu: Confirmed Bug description: I was clicking Check for updates when suddenly my phone rebooted. After it went back to life I've noticed the new notification which said: 18196311974 voicemail messages. AFAIK I don't have a voicemail even active. Screenshot attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1445215/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1405277] Re: screen flicker in ubuntu 14.04.1 and derivatives
I have the exact same problem as hansie describes. I am trying to put Trusty (14.04 LTS, 32 bit version) on a Toshiba Satellite A215-S4697 with an AMD Turion 64 X2 Dual-Core processor, 1024 DDR2 SDRAM--same laptop as hansie. There is no flickering/blinking on the original download of Trusty with Linux 3.13.0-32. The flickering/blinking started, when I did my first update to Linux 3.13.0-48. I did a further update to Linux 3.13.0-49 and the problem continued. So at least 2 people have this problem and I am pretty sure that any other Toshiba Satellite A215-S4697 user has the same problem. I see the problem is labelled as low priority. To me it is not low priority, because I would like to have a long term support (LTS) os on my computer. However, if the problem is fixed in 15.04 (as hansie states), I guess I could go with that until the next LTS. Has anybody tried the 64 bit version of 14.04??? Are people moving on to 15.04, so this problem is likely never to be fixed in 14.04 LTS??? -- 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/1405277 Title: screen flicker in ubuntu 14.04.1 and derivatives Status in xorg package in Ubuntu: Incomplete Bug description: 1. my screen flickers on all ubuntu 14.04.1 distro versions, linux mint 17.1 'cinamon', lxle 64 bit, guadalinex v9 32 bit, etc. 2. it flickers on the mint 17.1 'cinamon' installation disk - but it is stable on mint 17.0 'mate' installed 3. i can cure it by accesing the 'recovery section' of the 'multi- boot' system: but it is NOT 'persistent' 4. how can i fix this, using the 'cli': to make the fix 'permanent' the laptop is an older 'toshiba - amd - athlon x2' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1405277/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1439706] Re: FFE: Ubuntu FAN networking support (for linux, iproute2 and ubuntu-fan)
** Changed in: linux (Ubuntu) Status: Triaged = Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1439706 Title: FFE: Ubuntu FAN networking support (for linux, iproute2 and ubuntu- fan) Status in iproute2 package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Committed Bug description: FFE general instructions: The Ubuntu FAN networking support provides for additional addressing within a host system. These addresses are globally accessible within a related group of host systems, and would typically be assigned to LXC containers or Docker instances running on that host. A typical use case for this would be to allow nested containers on a cloud substrate, where the host systems would be guests in that cloud. Each cloud host instance would be able to express multiple addresses to other instances on the same substrate simplifying deployment. The changes consist of fixes for the linux (kernel) and iproute2 packages, as well as a new ubunt-fan package. The support is completely disabled unless the guest opts in. Installation of the ubuntu-fan package, and configuration of it via /etc/default/ubuntu- fan is required before the functionality is expressed. These changes are proposed to allow simpler deployment and addressing of LXC containers and Docker instances on any substrate in a consistent manner without needing cooperation of buy in from that substrate, simply having single instance addresses on that substrate is sufficient. This should be a strong enabler for Ubuntu on those platforms. Additional FFE instructions for linux: The changes for linux add a new IPIP tunnel routing mode which uses a direct address mapping (destination subnet to destination local IP address) allowing a single configuration per node to configure the entire fan network. No existing functionality is changed, and this new mode must be explicitly requested when configuring (via iproute2 see below). The patches have been applied and the resulting package uploaded to a testing PPA: ppa:~apw/ubuntu/fan. Testing is described below. Additional FFE instructions for iproute2: The changes for iproute2 add support for enabling the above IPIP routing mode, and for displaying it once configured. No existing functionality is changed. There is a small risk that the interface chosen could be reused by upstream, but as it is fan specific that is unlikely. The patches have been applied and the resulting package uploaded to a testing PPA: ppa:~apw/ubuntu/fan. Testing is described below. Additional FFE instructions for new ubuntu-fan package: The new ubuntu-fan package enables the fan functionality by configuring a new tunnel configured in Ubuntu FAN mode, and a new bridge which is used to connect consumers to it. Typically this bridge is then used as the host bridge for LXC containers or Docker instances. Additionally a dnsmasq is connected to the bridge to hand out addresses in the host specific range as if they themselves were on the wider network. The source package is uploaded to the PPA: ppa:~apw/ubuntu/fan as ubuntu-fan and represents the master source for this package. Testing of this combination: The above has been tested in combination from the testing PPA: ppa:~apw/ubuntu/fan. These have been tested both locally and on AWS, it has been successfully tested with both LXC containers and Docker instances. === Using the above instructions/checklist, lets draft the FFE below...Once we are happy with it let's delete the notes above and we can subscribe ubuntu-release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1439706/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1433131] Re: [dialer app] pressing power button a 2nd time switches off screen
** Changed in: ubuntu-ux Importance: Medium = Low ** Changed in: ubuntu-ux Importance: Low = High ** Changed in: ubuntu-ux Status: Triaged = Fix Committed ** Description changed: This bug is related to this one: https://bugs.launchpad.net/ubuntu- ux/+bug/1376240 While pressing the power button does silence the call but this interaction switches off the screen too. - It can look strange for users because it is not clear if the call was just silenced or completely dismissed. + It can look strange for users because it is not clear if the call was just silenced or completely dismissed. - Desired solution: + UX desired solution: - 1st press of power button silences the call - 2nd press shuts off device screen -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-system-compositor in Ubuntu. https://bugs.launchpad.net/bugs/1433131 Title: [dialer app] pressing power button a 2nd time switches off screen Status in Dialer app for Ubuntu Touch: New Status in Telephony Service: New Status in Ubuntu UX bugs: Fix Committed Status in telephony-service package in Ubuntu: Confirmed Status in unity-system-compositor package in Ubuntu: Confirmed Bug description: This bug is related to this one: https://bugs.launchpad.net/ubuntu- ux/+bug/1376240 While pressing the power button does silence the call but this interaction switches off the screen too. It can look strange for users because it is not clear if the call was just silenced or completely dismissed. UX desired solution: - 1st press of power button silences the call - 2nd press shuts off device screen To manage notifications about this bug go to: https://bugs.launchpad.net/dialer-app/+bug/1433131/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1433131] Re: [dialer app] pressing power button a 2nd time switches off screen
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity-system-compositor (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-system-compositor in Ubuntu. https://bugs.launchpad.net/bugs/1433131 Title: [dialer app] pressing power button a 2nd time switches off screen Status in Dialer app for Ubuntu Touch: New Status in Telephony Service: New Status in Ubuntu UX bugs: Fix Committed Status in telephony-service package in Ubuntu: Confirmed Status in unity-system-compositor package in Ubuntu: Confirmed Bug description: This bug is related to this one: https://bugs.launchpad.net/ubuntu- ux/+bug/1376240 While pressing the power button does silence the call but this interaction switches off the screen too. It can look strange for users because it is not clear if the call was just silenced or completely dismissed. UX desired solution: - 1st press of power button silences the call - 2nd press shuts off device screen To manage notifications about this bug go to: https://bugs.launchpad.net/dialer-app/+bug/1433131/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1433131] Re: [dialer app] pressing power button a 2nd time switches off screen
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: telephony-service (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-system-compositor in Ubuntu. https://bugs.launchpad.net/bugs/1433131 Title: [dialer app] pressing power button a 2nd time switches off screen Status in Dialer app for Ubuntu Touch: New Status in Telephony Service: New Status in Ubuntu UX bugs: Fix Committed Status in telephony-service package in Ubuntu: Confirmed Status in unity-system-compositor package in Ubuntu: Confirmed Bug description: This bug is related to this one: https://bugs.launchpad.net/ubuntu- ux/+bug/1376240 While pressing the power button does silence the call but this interaction switches off the screen too. It can look strange for users because it is not clear if the call was just silenced or completely dismissed. UX desired solution: - 1st press of power button silences the call - 2nd press shuts off device screen To manage notifications about this bug go to: https://bugs.launchpad.net/dialer-app/+bug/1433131/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 953875]
OK, if this is not a bytes value, parse_size() is probably not a good idea. (that said, I think it's a pretty poor choice to expose this as 512byte block value...) Anyway, looks good. Please push! -- 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/953875 Title: Encrypted swap no longer mounted at bootup Status in eCryptfs: Fix Released Status in systemd: Fix Released Status in ecryptfs-utils package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Fix Released Status in ecryptfs-utils source package in Vivid: Fix Released Status in systemd source package in Vivid: Fix Released Status in ubiquity source package in Vivid: Fix Released Status in systemd package in Debian: Fix Released Bug description: SUMMARY === During installation with encrypt my home folder mode, a broken /etc/crypttab gets created which defines a non-existing swap device (usually cryptswap1) with a UUID. This will also be put into /etc/fstab. As after installation the UUID does not exist, such systems don't have any actual swap. UPGRADE FIX === An upgrade to Ubuntu 15.04 (vivid) will detect and comment out these broken swap devices from /etc/fstab and /etc/crypttab. If you actually want to use those, do these steps: - Find the swap device that was meant to be used in sudo fdisk -l (it should say Linux swap in the last column), remember the device name (something like /dev/sda5) - Find the UUID in /etc/crypttab (the long alphanumeric ID after UUID=) - Run sudo mkswap -U 1234... /dev/sda5, replacing 1234 with the above UUID, and /dev/sda5 with the device name from step 1. - Edit /etc/crypttab to append ,offset=1024 in the fourth (last) column of the cryptswap1 line; ensure that there is *no space* between the cipher=aes-cbc-essiv:sha256 and the appended option. If there is a leading # in the file, remove that too. - If there is a leading # in /etc/fstab in the line starting with /dev/mapper/cryptswap1 line, remove that. - Run sudo update-initramfs -u. ORIGINAL REPORT === Clean install of 12.04 and with encrypted home for my user. Did all updates and now the bootup hangs waiting for swap to become available and it never seems to ever finish. The 200GB SSD below is my boot drive and root filesystem. alan@mesh:~$ sudo swapon -a [sudo] password for alan: swapon: /dev/mapper/cryptswap1: stat failed: No such file or directory alan@mesh:~$ grep swap /etc/fstab # swap was on /dev/sdg5 during installation #UUID=22d3f7f0-f715-4582-81ba-dcbd4cdd1495 noneswapsw 0 0 /dev/mapper/cryptswap1 none swap sw 0 0 alan@mesh:~$ sudo fdisk -l Disk /dev/sda: 115.0 GB, 115033153536 bytes 255 heads, 63 sectors/track, 13985 cylinders, total 224674128 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x000ba2ed Device Boot Start End Blocks Id System /dev/sda1 *2048 206847 1024007 HPFS/NTFS/exFAT /dev/sda2 206848 224671743 1122324487 HPFS/NTFS/exFAT Disk /dev/sdb: 200.0 GB, 200049647616 bytes 255 heads, 63 sectors/track, 24321 cylinders, total 390721968 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0xf0fa0806 Device Boot Start End Blocks Id System /dev/sdb12048 349304831 1746513927 HPFS/NTFS/exFAT /dev/sdb2 374722558 390721535 79994895 Extended /dev/sdb3 * 349304832 37472051112707840 83 Linux /dev/sdb5 374722560 390721535 7999488 82 Linux swap / Solaris Partition table entries are not in disk order ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libecryptfs0 96-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9 Uname: Linux 3.2.0-18-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.94.1-0ubuntu2 Architecture: amd64 Date: Tue Mar 13 09:56:56 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120215) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: ecryptfs-utils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ecryptfs/+bug/953875/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 953875]
Also, please add the initialization of .offset and .skip into the
declaration of the params variable, as initializer. i.e.:
struct crypt_params_plain params = {
.offset = arg_offset,
.skip = arg_skip,
};
Also, please document the new switches in crypttab(5).
--
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/953875
Title:
Encrypted swap no longer mounted at bootup
Status in eCryptfs:
Fix Released
Status in systemd:
Fix Released
Status in ecryptfs-utils package in Ubuntu:
Fix Released
Status in systemd package in Ubuntu:
Fix Released
Status in ubiquity package in Ubuntu:
Fix Released
Status in ecryptfs-utils source package in Vivid:
Fix Released
Status in systemd source package in Vivid:
Fix Released
Status in ubiquity source package in Vivid:
Fix Released
Status in systemd package in Debian:
Fix Released
Bug description:
SUMMARY
===
During installation with encrypt my home folder mode, a broken
/etc/crypttab gets created which defines a non-existing swap device (usually
cryptswap1) with a UUID. This will also be put into /etc/fstab. As after
installation the UUID does not exist, such systems don't have any actual swap.
UPGRADE FIX
===
An upgrade to Ubuntu 15.04 (vivid) will detect and comment out these broken
swap devices from /etc/fstab and /etc/crypttab. If you actually want to use
those, do these steps:
- Find the swap device that was meant to be used in sudo fdisk -l (it
should say Linux swap in the last column), remember the device name
(something like /dev/sda5)
- Find the UUID in /etc/crypttab (the long alphanumeric ID after UUID=)
- Run sudo mkswap -U 1234... /dev/sda5, replacing 1234 with the above
UUID, and /dev/sda5 with the device name from step 1.
- Edit /etc/crypttab to append ,offset=1024 in the fourth (last) column of
the cryptswap1 line; ensure that there is *no space* between the
cipher=aes-cbc-essiv:sha256 and the appended option. If there is a leading
# in the file, remove that too.
- If there is a leading # in /etc/fstab in the line starting with
/dev/mapper/cryptswap1 line, remove that.
- Run sudo update-initramfs -u.
ORIGINAL REPORT
===
Clean install of 12.04 and with encrypted home for my user. Did all
updates and now the bootup hangs waiting for swap to become available
and it never seems to ever finish. The 200GB SSD below is my boot
drive and root filesystem.
alan@mesh:~$ sudo swapon -a
[sudo] password for alan:
swapon: /dev/mapper/cryptswap1: stat failed: No such file or directory
alan@mesh:~$ grep swap /etc/fstab
# swap was on /dev/sdg5 during installation
#UUID=22d3f7f0-f715-4582-81ba-dcbd4cdd1495 noneswapsw
0 0
/dev/mapper/cryptswap1 none swap sw 0 0
alan@mesh:~$ sudo fdisk -l
Disk /dev/sda: 115.0 GB, 115033153536 bytes
255 heads, 63 sectors/track, 13985 cylinders, total 224674128 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000ba2ed
Device Boot Start End Blocks Id System
/dev/sda1 *2048 206847 1024007 HPFS/NTFS/exFAT
/dev/sda2 206848 224671743 1122324487 HPFS/NTFS/exFAT
Disk /dev/sdb: 200.0 GB, 200049647616 bytes
255 heads, 63 sectors/track, 24321 cylinders, total 390721968 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xf0fa0806
Device Boot Start End Blocks Id System
/dev/sdb12048 349304831 1746513927 HPFS/NTFS/exFAT
/dev/sdb2 374722558 390721535 79994895 Extended
/dev/sdb3 * 349304832 37472051112707840 83 Linux
/dev/sdb5 374722560 390721535 7999488 82 Linux swap / Solaris
Partition table entries are not in disk order
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: libecryptfs0 96-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9
Uname: Linux 3.2.0-18-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
Date: Tue Mar 13 09:56:56 2012
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64
(20120215)
ProcEnviron:
LANGUAGE=en_GB:en
TERM=xterm
LANG=en_GB.UTF-8
SHELL=/bin/bash
SourcePackage: ecryptfs-utils
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ecryptfs/+bug/953875/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe :
[Touch-packages] [Bug 1405277] Re: screen flicker in ubuntu 14.04.1 and derivatives
ralphl, it will help immensely if you filed a new report via a terminal: ubuntu-bug xorg Please ensure you have xdiagnose installed, and that you click the Yes button for attaching additional debugging information. -- 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/1405277 Title: screen flicker in ubuntu 14.04.1 and derivatives Status in xorg package in Ubuntu: Incomplete Bug description: 1. my screen flickers on all ubuntu 14.04.1 distro versions, linux mint 17.1 'cinamon', lxle 64 bit, guadalinex v9 32 bit, etc. 2. it flickers on the mint 17.1 'cinamon' installation disk - but it is stable on mint 17.0 'mate' installed 3. i can cure it by accesing the 'recovery section' of the 'multi- boot' system: but it is NOT 'persistent' 4. how can i fix this, using the 'cli': to make the fix 'permanent' the laptop is an older 'toshiba - amd - athlon x2' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1405277/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1432818] Re: Mouse Pad Stops working after sleep or logging back in sometimes.
Hudson Worden, thank you for reporting this and helping make Ubuntu better. Saucy reached EOL on July 17, 2014. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases Is this an issue in a supported release? ** Tags added: bios-outdated-2.61 ** Changed in: xorg (Ubuntu) Importance: Undecided = Low ** Changed in: xorg (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1432818 Title: Mouse Pad Stops working after sleep or logging back in sometimes. Status in xorg package in Ubuntu: Incomplete Bug description: Make: Lenovo Model: Thinkpad X230 Tablet Description: Ubuntu 13.10 Release: 13.10 When the computer goes to sleep when I step away for a while or when I close the lid, sometimes the mouse pad stops detecting mouse movement. The buttons all work it's just the touch pad. When I used Ctrl-Alt-F2 to go into the terminal then used Ctrl-Alt-F7 to come back into X, control was restored. Evtest: Input driver version is 1.0.1 Input device ID: bus 0x11 vendor 0x2 product 0xa version 0x0 Input device name: TPPS/2 IBM TrackPoint Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 272 (BTN_LEFT) Event code 273 (BTN_RIGHT) Event code 274 (BTN_MIDDLE) Event type 2 (EV_REL) Event code 0 (REL_X) Event code 1 (REL_Y) Properties: Testing ... (interrupt to exit) Event: time 1426535187.488287, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1 Event: time 1426535187.488287, -- SYN_REPORT Event: time 1426535187.599989, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0 Event: time 1426535187.599989, -- SYN_REPORT Event: time 1426535187.835609, type 1 (EV_KEY), code 274 (BTN_MIDDLE), value 1 Event: time 1426535187.835609, -- SYN_REPORT Event: time 1426535187.934616, type 1 (EV_KEY), code 274 (BTN_MIDDLE), value 0 Event: time 1426535187.934616, -- SYN_REPORT Event: time 1426535188.170471, type 1 (EV_KEY), code 273 (BTN_RIGHT), value 1 Event: time 1426535188.170471, -- SYN_REPORT Event: time 1426535188.306262, type 1 (EV_KEY), code 273 (BTN_RIGHT), value 0 Event: time 1426535188.306262, -- SYN_REPORT Event: time 1426535198.443664, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1 Event: time 1426535198.443664, -- SYN_REPORT Event: time 1426535198.512944, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0 Event: time 1426535198.512944, -- SYN_REPORT Event: time 1426535198.622309, type 1 (EV_KEY), code 274 (BTN_MIDDLE), value 1 Event: time 1426535198.622309, -- SYN_REPORT Event: time 1426535198.706636, type 1 (EV_KEY), code 274 (BTN_MIDDLE), value 0 Event: time 1426535198.706636, -- SYN_REPORT Event: time 1426535198.820974, type 1 (EV_KEY), code 273 (BTN_RIGHT), value 1 Event: time 1426535198.820974, -- SYN_REPORT Event: time 1426535198.930318, type 1 (EV_KEY), code 273 (BTN_RIGHT), value 0 Event: time 1426535198.930318, -- SYN_REPORT I have attached Xorg.0.log ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-26.45-generic 3.11.10.12 Uname: Linux 3.11.0-26-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.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 Date: Mon Mar 16 16:02:43 2015 DistUpgraded: 2015-03-16 12:08:35,592 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2203] InstallationDate: Installed on 2014-10-12 (154 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: LENOVO 3437W14 MarkForUpload: True ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-26-generic root=UUID=C4740C8A740C8202 loop=/hostname/disks/root.disk ro rootflags=sync quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to saucy on 2015-03-16 (0 days ago) dmi.bios.date: 09/12/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GCETA0WW (2.60 ) dmi.board.asset.tag: Not Available dmi.board.name: 3437W14
[Touch-packages] [Bug 1445596] Re: lenovo t410 [2537BF9, Conexant CX20585, Speaker, Internal] fails after a while
The only change in the output from alsa-info.sh was Power: setting=D0, actual=D0 changed to Power: setting=D3, actual=D3 any idea ** Attachment added: Result from alsa-info.sh after sound from internal speakers stopped https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1445596/+attachment/4379075/+files/speaker_notOK -- 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/1445596 Title: lenovo t410 [2537BF9, Conexant CX20585, Speaker, Internal] fails after a while Status in alsa-driver package in Ubuntu: New Bug description: after a suspend the sound works for a while and then stops again Sound used to work with Ubuntu 12.04, but after an update it showed the same symptoms. So I tried the latest Ubuntu version but still same problem. Headphones always woirk ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3 Uname: Linux 3.19.0-14-generic x86_64 ApportVersion: 2.17.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: bruno 1215 F...m pulseaudio /dev/snd/controlC0: bruno 1215 F pulseaudio CurrentDesktop: Unity Date: Fri Apr 17 19:51:41 2015 InstallationDate: Installed on 2015-03-29 (19 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Beta amd64 (20150326) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel MID Symptom_Jack: Speaker, Internal Symptom_Type: Sound works for a while, then breaks Title: [2537BF9, Conexant CX20585, Speaker, Internal] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/14/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET85WW (1.45 ) dmi.board.name: 2537BF9 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: 2537R8M1NHK dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6IET85WW(1.45):bd02/14/2013:svnLENOVO:pn2537BF9:pvrThinkPadT410:rvnLENOVO:rn2537BF9:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2537BF9 dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1445596/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1308800] Re: Unity doesn't respawn all the times on crashes
It is now a year since this bug was marked Critical, but it keeps being postponed. I think this was part of the cause of an embarrassing experience during my recent presentation to a Linux Users Group, where Unity went away twice, forcing me to reboot the first time, and borrow a (gasp!) Apple computer the second time to finish the presentation. What is the status of the overall fix? What is the story with the fix released aspect of this for gnome-session? Was that just one aspect of the fix? When it is fixed, will it be backported to Trusty? Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1308800 Title: Unity doesn't respawn all the times on crashes Status in Unity: In Progress Status in Unity 7.2 series: In Progress Status in gnome-session package in Ubuntu: Fix Released Status in unity package in Ubuntu: In Progress Bug description: [Impact] Killing compiz repeatedly doesn't make unity to reload all the times. This is caused by the fact that due to a regression unity7 is not loaded anymore by upstart (but by gnome-session) and thus it seems that sometimes it doesn't properly gets restarted. This is also a security issue, because if the session was locked, and unity is not reloaded the session won't be locked anymore. [Test Case] From a terminal run killall -9 compiz multiple times, it should always reload, but it fails after a couple of times. [Regression Potential] The fix is about always making unity to be launched by upstart. Regression potential is low, since upstart is now used by most ubuntu desktop applications, and it ensures compiz will run properly anyway. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1308800/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 953875]
Created attachment 115126 cryptsetup: Implement offset and skip options Indeed! Fixed both. I tested with offset=x8 and it now correctly aborts and doesn't touch the device. offset=1024 and no offset still continue to work. Thanks for the review! -- 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/953875 Title: Encrypted swap no longer mounted at bootup Status in eCryptfs: Fix Released Status in systemd: Fix Released Status in ecryptfs-utils package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Fix Released Status in ecryptfs-utils source package in Vivid: Fix Released Status in systemd source package in Vivid: Fix Released Status in ubiquity source package in Vivid: Fix Released Status in systemd package in Debian: Fix Released Bug description: SUMMARY === During installation with encrypt my home folder mode, a broken /etc/crypttab gets created which defines a non-existing swap device (usually cryptswap1) with a UUID. This will also be put into /etc/fstab. As after installation the UUID does not exist, such systems don't have any actual swap. UPGRADE FIX === An upgrade to Ubuntu 15.04 (vivid) will detect and comment out these broken swap devices from /etc/fstab and /etc/crypttab. If you actually want to use those, do these steps: - Find the swap device that was meant to be used in sudo fdisk -l (it should say Linux swap in the last column), remember the device name (something like /dev/sda5) - Find the UUID in /etc/crypttab (the long alphanumeric ID after UUID=) - Run sudo mkswap -U 1234... /dev/sda5, replacing 1234 with the above UUID, and /dev/sda5 with the device name from step 1. - Edit /etc/crypttab to append ,offset=1024 in the fourth (last) column of the cryptswap1 line; ensure that there is *no space* between the cipher=aes-cbc-essiv:sha256 and the appended option. If there is a leading # in the file, remove that too. - If there is a leading # in /etc/fstab in the line starting with /dev/mapper/cryptswap1 line, remove that. - Run sudo update-initramfs -u. ORIGINAL REPORT === Clean install of 12.04 and with encrypted home for my user. Did all updates and now the bootup hangs waiting for swap to become available and it never seems to ever finish. The 200GB SSD below is my boot drive and root filesystem. alan@mesh:~$ sudo swapon -a [sudo] password for alan: swapon: /dev/mapper/cryptswap1: stat failed: No such file or directory alan@mesh:~$ grep swap /etc/fstab # swap was on /dev/sdg5 during installation #UUID=22d3f7f0-f715-4582-81ba-dcbd4cdd1495 noneswapsw 0 0 /dev/mapper/cryptswap1 none swap sw 0 0 alan@mesh:~$ sudo fdisk -l Disk /dev/sda: 115.0 GB, 115033153536 bytes 255 heads, 63 sectors/track, 13985 cylinders, total 224674128 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x000ba2ed Device Boot Start End Blocks Id System /dev/sda1 *2048 206847 1024007 HPFS/NTFS/exFAT /dev/sda2 206848 224671743 1122324487 HPFS/NTFS/exFAT Disk /dev/sdb: 200.0 GB, 200049647616 bytes 255 heads, 63 sectors/track, 24321 cylinders, total 390721968 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0xf0fa0806 Device Boot Start End Blocks Id System /dev/sdb12048 349304831 1746513927 HPFS/NTFS/exFAT /dev/sdb2 374722558 390721535 79994895 Extended /dev/sdb3 * 349304832 37472051112707840 83 Linux /dev/sdb5 374722560 390721535 7999488 82 Linux swap / Solaris Partition table entries are not in disk order ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libecryptfs0 96-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9 Uname: Linux 3.2.0-18-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.94.1-0ubuntu2 Architecture: amd64 Date: Tue Mar 13 09:56:56 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120215) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: ecryptfs-utils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ecryptfs/+bug/953875/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages
[Touch-packages] [Bug 953875] Re: Encrypted swap no longer mounted at bootup
** Changed in: systemd Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/953875 Title: Encrypted swap no longer mounted at bootup Status in eCryptfs: Fix Released Status in systemd: Fix Released Status in ecryptfs-utils package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Fix Released Status in ecryptfs-utils source package in Vivid: Fix Released Status in systemd source package in Vivid: Fix Released Status in ubiquity source package in Vivid: Fix Released Status in systemd package in Debian: Fix Released Bug description: SUMMARY === During installation with encrypt my home folder mode, a broken /etc/crypttab gets created which defines a non-existing swap device (usually cryptswap1) with a UUID. This will also be put into /etc/fstab. As after installation the UUID does not exist, such systems don't have any actual swap. UPGRADE FIX === An upgrade to Ubuntu 15.04 (vivid) will detect and comment out these broken swap devices from /etc/fstab and /etc/crypttab. If you actually want to use those, do these steps: - Find the swap device that was meant to be used in sudo fdisk -l (it should say Linux swap in the last column), remember the device name (something like /dev/sda5) - Find the UUID in /etc/crypttab (the long alphanumeric ID after UUID=) - Run sudo mkswap -U 1234... /dev/sda5, replacing 1234 with the above UUID, and /dev/sda5 with the device name from step 1. - Edit /etc/crypttab to append ,offset=1024 in the fourth (last) column of the cryptswap1 line; ensure that there is *no space* between the cipher=aes-cbc-essiv:sha256 and the appended option. If there is a leading # in the file, remove that too. - If there is a leading # in /etc/fstab in the line starting with /dev/mapper/cryptswap1 line, remove that. - Run sudo update-initramfs -u. ORIGINAL REPORT === Clean install of 12.04 and with encrypted home for my user. Did all updates and now the bootup hangs waiting for swap to become available and it never seems to ever finish. The 200GB SSD below is my boot drive and root filesystem. alan@mesh:~$ sudo swapon -a [sudo] password for alan: swapon: /dev/mapper/cryptswap1: stat failed: No such file or directory alan@mesh:~$ grep swap /etc/fstab # swap was on /dev/sdg5 during installation #UUID=22d3f7f0-f715-4582-81ba-dcbd4cdd1495 noneswapsw 0 0 /dev/mapper/cryptswap1 none swap sw 0 0 alan@mesh:~$ sudo fdisk -l Disk /dev/sda: 115.0 GB, 115033153536 bytes 255 heads, 63 sectors/track, 13985 cylinders, total 224674128 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x000ba2ed Device Boot Start End Blocks Id System /dev/sda1 *2048 206847 1024007 HPFS/NTFS/exFAT /dev/sda2 206848 224671743 1122324487 HPFS/NTFS/exFAT Disk /dev/sdb: 200.0 GB, 200049647616 bytes 255 heads, 63 sectors/track, 24321 cylinders, total 390721968 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0xf0fa0806 Device Boot Start End Blocks Id System /dev/sdb12048 349304831 1746513927 HPFS/NTFS/exFAT /dev/sdb2 374722558 390721535 79994895 Extended /dev/sdb3 * 349304832 37472051112707840 83 Linux /dev/sdb5 374722560 390721535 7999488 82 Linux swap / Solaris Partition table entries are not in disk order ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libecryptfs0 96-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9 Uname: Linux 3.2.0-18-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.94.1-0ubuntu2 Architecture: amd64 Date: Tue Mar 13 09:56:56 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120215) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: ecryptfs-utils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ecryptfs/+bug/953875/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1442105] Re: GPS not working on my BQ Ubuntu Touch
The same thing is happening to me with those two software. Differently, with OpenStreetMap, I get this information: JavaScript Notice, Geolocation error: permission denied. ** Changed in: indicator-location (Ubuntu) Status: New = Confirmed -- 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/1442105 Title: GPS not working on my BQ Ubuntu Touch Status in indicator-location package in Ubuntu: Confirmed Bug description: Hi. I tried to use GPS (HERE maps, Google Maps) on my Ubuntu Touch from BQ (I am on update 20), but the app dont detect my location. I have to mention that I check Here terms Condition and GPS and location are checked. I attached some screenshot from what I did. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-location/+bug/1442105/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1392308] Re: [design] Cannot browse indicators in daylight
** Changed in: ubuntu-ux Assignee: Tingting Zhao (tingtingzhao) = (unassigned) ** Changed in: ubuntu-ux Assignee: (unassigned) = Paty Davila (dizzypaty) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1392308 Title: [design] Cannot browse indicators in daylight Status in Ubuntu UX bugs: Triaged Status in unity8 package in Ubuntu: New Bug description: While doing GPS tests with the phone in daylight, I found it difficult to open the location indicator, because of the current color scheme. The non-active indicators are too dim to be read. -- UX -- I think this is a good candidate for user testing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1392308/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1438422] Re: Hybrid laptop's accelerometer tilt interpreted as WiFi hardware switch
I am currently working around the problem by setting key control to false in /etc/urfkill/urfkill.conf . -- 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/1438422 Title: Hybrid laptop's accelerometer tilt interpreted as WiFi hardware switch Status in compiz package in Ubuntu: Invalid Status in gnome-session package in Ubuntu: New Status in network-manager package in Ubuntu: New Status in urfkill package in Ubuntu: New Bug description: This bug appears to be a regression in Vivid sometime in the second half of March 2015. When the machine is tilted (e.g., onto its side), Syslog reports an unknown button being pressed. When tilted back to the normal laptop position, the machine's WiFi disconnects and is shown as disabled in the connection manager. Syslog indicates that urfkill registered a hardware switch cutoff for the WiFi. I know that the accelerometers do work in other contexts and can be read properly in Ubuntu. As an example, this orient script works for me: https://github.com/leszakk/orient . Hardware: HP Envy x360 15t -- this is a hybrid touch notebook OS: Ubuntu 15.04 Beta 2 -- Desktop version Kernel: 3.19.0-10-generic urfkill: Installed: 0.6.0~20150318.103828.5539c0d.1-0ubuntu1 Candidate: 0.6.0~20150318.103828.5539c0d.1-0ubuntu1 Version table: *** 0.6.0~20150318.103828.5539c0d.1-0ubuntu1 0 500 http://mirrors.mit.edu/ubuntu/ vivid/universe amd64 Packages 100 /var/lib/dpkg/status Below is a Syslog readout from a test event. The notebook starts in normal typing position, the hinge bent at a right angle. At 16:13:30, without moving the hinge, I tip the notebook 90 degrees to the left from my perspective. So the Unity launcher is now closest to the floor, for example. I hold it there for about 10 seconds until 16:13:40. Mar 30 16:13:30 [my_hostname] kernel: [ 1327.717086] atkbd serio0: Unknown key pressed (translated set 2, code 0xd8 on isa0060/serio0). Mar 30 16:13:30 [my_hostname] kernel: [ 1327.717098] atkbd serio0: Use 'setkeycodes e058 keycode' to make it known. Mar 30 16:13:30 [my_hostname] kernel: [ 1327.724168] atkbd serio0: Unknown key released (translated set 2, code 0xd8 on isa0060/serio0). Mar 30 16:13:30 [my_hostname] kernel: [ 1327.724180] atkbd serio0: Use 'setkeycodes e058 keycode' to make it known. Mar 30 16:13:41 [my_hostname] URfkill[868]: Setting WLAN devices to blocked Mar 30 16:13:41 [my_hostname] URfkill[868]: set_soft: Setting WLAN to blocked Mar 30 16:13:41 [my_hostname] kernel: [ 1338.698934] wlan0: deauthenticating from [ma:ca:dd:re:ss] by local choice (Reason: 3=DEAUTH_LEAVING) Mar 30 16:13:41 [my_hostname] wpa_supplicant[1015]: wlan0: CTRL-EVENT-DISCONNECTED bssid=[ma:ca:dd:re:ss] reason=3 locally_generated=1 Mar 30 16:13:41 [my_hostname] kernel: [ 1338.710906] cfg80211: Calling CRDA to update world regulatory domain Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Interface wlan0.IPv6 no longer relevant for mDNS. Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::8286:f2ff:fe32:def8. Mar 30 16:13:41 [my_hostname] dhclient: receive_packet failed on wlan0: Network is down Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Interface wlan0.IPv4 no longer relevant for mDNS. Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.133. Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Withdrawing address record for fe80::8286:f2ff:fe32:def8 on wlan0. Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Withdrawing address record for 192.168.1.133 on wlan0. Mar 30 16:13:41 [my_hostname] URfkill[868]: device_changed_cb: phy0 Mar 30 16:13:41 [my_hostname] NetworkManager[863]: warn Connection disconnected (reason -3) Mar 30 16:13:41 [my_hostname] NetworkManager[863]: error [1427746421.849186] [platform/nm-linux-platform.c:1714] add_object(): Netlink error adding 0.0.0.0/0 via 192.168.1.1 dev wlan0 metric 1024 mss 0 src user: Unspecific failure Mar 30 16:13:41 [my_hostname] NetworkManager[863]: error [1427746421.849417] [platform/nm-linux-platform.c:1714] add_object(): Netlink error adding 192.168.1.1/32 via 0.0.0.0 dev wlan0 metric 1024 mss 0 src user: Unspecific failure Mar 30 16:13:41 [my_hostname] NetworkManager[863]: error [1427746421.849591] [platform/nm-linux-platform.c:1714] add_object(): Netlink error adding 0.0.0.0/0 via 192.168.1.1 dev wlan0 metric 1024 mss 0 src user: Unspecific failure Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.133. Mar 30 16:13:41 [my_hostname] NetworkManager[863]: error [1427746421.849679] [nm-policy.c:693] update_ip4_routing(): Failed to set default
[Touch-packages] [Bug 1443843] Re: [clock-app] Time picker width too small leading to accidental changes in other columns
** Summary changed: - Time picker width too small leading to accidental changes in other columns + [clock-app] Time picker width too small leading to accidental changes in other columns -- 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/1443843 Title: [clock-app] Time picker width too small leading to accidental changes in other columns Status in Clock application for Ubuntu devices: Confirmed Status in Ubuntu UX bugs: Triaged Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: Ubuntu Touch 14.10 (r20) running on BQ Ubuntu Edition. Issue: The time picker occupies the entire width of the alarm page and yet the actual dials occupy only a fraction of that width resulting in users accidentally changing other column values. May be we should increase the width of the dials? Screenshot: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui- toolkit/+bug/1443843/+attachment/4375026/+files/timepicker.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1443843/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1396361] Re: Double Mouse Cursor
I can repeat the problem by dragging a bookmark in firefox. Running 14.04 lubuntu. -- 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/1396361 Title: Double Mouse Cursor Status in xorg package in Ubuntu: Incomplete Bug description: When dragging with the mouse cursor often it creates a double cursor side by side about 10 cm apart on the screen. Only one cursor works. Using print screen does not show the cursor in the resulting image. Rebooting corrects the problem. This is similar to the double mouse cursor reported as a result of flash in a browser, however the current problem will occur without the browser open. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xinput 1.6.1-1 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic i686 ApportVersion: 2.14.7-0ubuntu8 Architecture: i386 CurrentDesktop: LXDE Date: Tue Nov 25 15:58:51 2014 InstallationDate: Installed on 2014-10-24 (32 days ago) InstallationMedia: Lubuntu 14.10 Utopic Unicorn - Release i386 (20141022.1) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xinput UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1396361/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1439706] Re: FFE: Ubuntu FAN networking support (for linux, iproute2 and ubuntu-fan)
This bug was fixed in the package iproute2 - 3.16.0-2ubuntu1 --- iproute2 (3.16.0-2ubuntu1) vivid; urgency=low * Add Ubuntu FAN support. (LP: #1439706) -- Andy Whitcroft a...@ubuntu.com Tue, 24 Feb 2015 14:45:19 + ** Changed in: iproute2 (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1439706 Title: FFE: Ubuntu FAN networking support (for linux, iproute2 and ubuntu- fan) Status in iproute2 package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Committed Bug description: FFE general instructions: The Ubuntu FAN networking support provides for additional addressing within a host system. These addresses are globally accessible within a related group of host systems, and would typically be assigned to LXC containers or Docker instances running on that host. A typical use case for this would be to allow nested containers on a cloud substrate, where the host systems would be guests in that cloud. Each cloud host instance would be able to express multiple addresses to other instances on the same substrate simplifying deployment. The changes consist of fixes for the linux (kernel) and iproute2 packages, as well as a new ubunt-fan package. The support is completely disabled unless the guest opts in. Installation of the ubuntu-fan package, and configuration of it via /etc/default/ubuntu- fan is required before the functionality is expressed. These changes are proposed to allow simpler deployment and addressing of LXC containers and Docker instances on any substrate in a consistent manner without needing cooperation of buy in from that substrate, simply having single instance addresses on that substrate is sufficient. This should be a strong enabler for Ubuntu on those platforms. Additional FFE instructions for linux: The changes for linux add a new IPIP tunnel routing mode which uses a direct address mapping (destination subnet to destination local IP address) allowing a single configuration per node to configure the entire fan network. No existing functionality is changed, and this new mode must be explicitly requested when configuring (via iproute2 see below). The patches have been applied and the resulting package uploaded to a testing PPA: ppa:~apw/ubuntu/fan. Testing is described below. Additional FFE instructions for iproute2: The changes for iproute2 add support for enabling the above IPIP routing mode, and for displaying it once configured. No existing functionality is changed. There is a small risk that the interface chosen could be reused by upstream, but as it is fan specific that is unlikely. The patches have been applied and the resulting package uploaded to a testing PPA: ppa:~apw/ubuntu/fan. Testing is described below. Additional FFE instructions for new ubuntu-fan package: The new ubuntu-fan package enables the fan functionality by configuring a new tunnel configured in Ubuntu FAN mode, and a new bridge which is used to connect consumers to it. Typically this bridge is then used as the host bridge for LXC containers or Docker instances. Additionally a dnsmasq is connected to the bridge to hand out addresses in the host specific range as if they themselves were on the wider network. The source package is uploaded to the PPA: ppa:~apw/ubuntu/fan as ubuntu-fan and represents the master source for this package. Testing of this combination: The above has been tested in combination from the testing PPA: ppa:~apw/ubuntu/fan. These have been tested both locally and on AWS, it has been successfully tested with both LXC containers and Docker instances. === Using the above instructions/checklist, lets draft the FFE below...Once we are happy with it let's delete the notes above and we can subscribe ubuntu-release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1439706/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1433131] Re: [dialer app] pressing power button a 2nd time switches off screen
** Also affects: dialer-app Importance: Undecided Status: New ** Also affects: unity-system-compositor (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1433131 Title: [dialer app] pressing power button a 2nd time switches off screen Status in Dialer app for Ubuntu Touch: New Status in Telephony Service: New Status in Ubuntu UX bugs: Fix Committed Status in telephony-service package in Ubuntu: Confirmed Status in unity-system-compositor package in Ubuntu: Confirmed Bug description: This bug is related to this one: https://bugs.launchpad.net/ubuntu- ux/+bug/1376240 While pressing the power button does silence the call but this interaction switches off the screen too. It can look strange for users because it is not clear if the call was just silenced or completely dismissed. UX desired solution: - 1st press of power button silences the call - 2nd press shuts off device screen To manage notifications about this bug go to: https://bugs.launchpad.net/dialer-app/+bug/1433131/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1394669] Re: [phone-app] 'Switch to default SIM' dialog is confusing
** Changed in: ubuntu-ux Status: Triaged = In Progress ** Description changed: If I press 'No' on that dialog, there is no way for this dialog to appear again, even changing the setting in system-settings has no effect. 0. Clean flash device. 1. Start dialer 2. A dialog appears to select default sim 3. Tap on 'No' button 4. Go to system settings and select 'Ask me each time' for outgoing calls. What happens: The sim prompt dialog never appears, no matter I toggle that setting. ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: dialer-app 0.1+15.04.2014~rtm-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Thu Nov 20 17:18:59 2014 InstallationDate: Installed on 2014-11-19 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141119-181707) SourcePackage: dialer-app UpgradeStatus: No upgrade log present (probably fresh install) + + --UX comment-- + + The UX is currently under review. There is a potential that this dialog + is not going to be needed anymore. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1394669 Title: [phone-app] 'Switch to default SIM' dialog is confusing Status in Ubuntu UX bugs: In Progress Status in dialer-app package in Ubuntu: New Bug description: If I press 'No' on that dialog, there is no way for this dialog to appear again, even changing the setting in system-settings has no effect. 0. Clean flash device. 1. Start dialer 2. A dialog appears to select default sim 3. Tap on 'No' button 4. Go to system settings and select 'Ask me each time' for outgoing calls. What happens: The sim prompt dialog never appears, no matter I toggle that setting. ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: dialer-app 0.1+15.04.2014~rtm-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Thu Nov 20 17:18:59 2014 InstallationDate: Installed on 2014-11-19 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141119-181707) SourcePackage: dialer-app UpgradeStatus: No upgrade log present (probably fresh install) --UX comment-- The UX is currently under review. There is a potential that this dialog is not going to be needed anymore. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1394669/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 953875]
Hmm, please use parse_bytes() for parsing byte values. -- 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/953875 Title: Encrypted swap no longer mounted at bootup Status in eCryptfs: Fix Released Status in systemd: Fix Released Status in ecryptfs-utils package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Fix Released Status in ecryptfs-utils source package in Vivid: Fix Released Status in systemd source package in Vivid: Fix Released Status in ubiquity source package in Vivid: Fix Released Status in systemd package in Debian: Fix Released Bug description: SUMMARY === During installation with encrypt my home folder mode, a broken /etc/crypttab gets created which defines a non-existing swap device (usually cryptswap1) with a UUID. This will also be put into /etc/fstab. As after installation the UUID does not exist, such systems don't have any actual swap. UPGRADE FIX === An upgrade to Ubuntu 15.04 (vivid) will detect and comment out these broken swap devices from /etc/fstab and /etc/crypttab. If you actually want to use those, do these steps: - Find the swap device that was meant to be used in sudo fdisk -l (it should say Linux swap in the last column), remember the device name (something like /dev/sda5) - Find the UUID in /etc/crypttab (the long alphanumeric ID after UUID=) - Run sudo mkswap -U 1234... /dev/sda5, replacing 1234 with the above UUID, and /dev/sda5 with the device name from step 1. - Edit /etc/crypttab to append ,offset=1024 in the fourth (last) column of the cryptswap1 line; ensure that there is *no space* between the cipher=aes-cbc-essiv:sha256 and the appended option. If there is a leading # in the file, remove that too. - If there is a leading # in /etc/fstab in the line starting with /dev/mapper/cryptswap1 line, remove that. - Run sudo update-initramfs -u. ORIGINAL REPORT === Clean install of 12.04 and with encrypted home for my user. Did all updates and now the bootup hangs waiting for swap to become available and it never seems to ever finish. The 200GB SSD below is my boot drive and root filesystem. alan@mesh:~$ sudo swapon -a [sudo] password for alan: swapon: /dev/mapper/cryptswap1: stat failed: No such file or directory alan@mesh:~$ grep swap /etc/fstab # swap was on /dev/sdg5 during installation #UUID=22d3f7f0-f715-4582-81ba-dcbd4cdd1495 noneswapsw 0 0 /dev/mapper/cryptswap1 none swap sw 0 0 alan@mesh:~$ sudo fdisk -l Disk /dev/sda: 115.0 GB, 115033153536 bytes 255 heads, 63 sectors/track, 13985 cylinders, total 224674128 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x000ba2ed Device Boot Start End Blocks Id System /dev/sda1 *2048 206847 1024007 HPFS/NTFS/exFAT /dev/sda2 206848 224671743 1122324487 HPFS/NTFS/exFAT Disk /dev/sdb: 200.0 GB, 200049647616 bytes 255 heads, 63 sectors/track, 24321 cylinders, total 390721968 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0xf0fa0806 Device Boot Start End Blocks Id System /dev/sdb12048 349304831 1746513927 HPFS/NTFS/exFAT /dev/sdb2 374722558 390721535 79994895 Extended /dev/sdb3 * 349304832 37472051112707840 83 Linux /dev/sdb5 374722560 390721535 7999488 82 Linux swap / Solaris Partition table entries are not in disk order ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libecryptfs0 96-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9 Uname: Linux 3.2.0-18-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.94.1-0ubuntu2 Architecture: amd64 Date: Tue Mar 13 09:56:56 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120215) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: ecryptfs-utils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ecryptfs/+bug/953875/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 953875]
Created attachment 115162 cryptsetup: Implement offset and skip options parse_size() is not appropriate here, as the offset=/skip= argument is a plain natural number, and the unit is always 512 byte blocks. So allowing things like 3.3K there would be confusing, wrong, imprecise, and incompatible with the cryptsetup project. I added documentation, the initializer, and also incorporated warning that Zbigniew suggested on the ML. -- 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/953875 Title: Encrypted swap no longer mounted at bootup Status in eCryptfs: Fix Released Status in systemd: Fix Released Status in ecryptfs-utils package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Fix Released Status in ecryptfs-utils source package in Vivid: Fix Released Status in systemd source package in Vivid: Fix Released Status in ubiquity source package in Vivid: Fix Released Status in systemd package in Debian: Fix Released Bug description: SUMMARY === During installation with encrypt my home folder mode, a broken /etc/crypttab gets created which defines a non-existing swap device (usually cryptswap1) with a UUID. This will also be put into /etc/fstab. As after installation the UUID does not exist, such systems don't have any actual swap. UPGRADE FIX === An upgrade to Ubuntu 15.04 (vivid) will detect and comment out these broken swap devices from /etc/fstab and /etc/crypttab. If you actually want to use those, do these steps: - Find the swap device that was meant to be used in sudo fdisk -l (it should say Linux swap in the last column), remember the device name (something like /dev/sda5) - Find the UUID in /etc/crypttab (the long alphanumeric ID after UUID=) - Run sudo mkswap -U 1234... /dev/sda5, replacing 1234 with the above UUID, and /dev/sda5 with the device name from step 1. - Edit /etc/crypttab to append ,offset=1024 in the fourth (last) column of the cryptswap1 line; ensure that there is *no space* between the cipher=aes-cbc-essiv:sha256 and the appended option. If there is a leading # in the file, remove that too. - If there is a leading # in /etc/fstab in the line starting with /dev/mapper/cryptswap1 line, remove that. - Run sudo update-initramfs -u. ORIGINAL REPORT === Clean install of 12.04 and with encrypted home for my user. Did all updates and now the bootup hangs waiting for swap to become available and it never seems to ever finish. The 200GB SSD below is my boot drive and root filesystem. alan@mesh:~$ sudo swapon -a [sudo] password for alan: swapon: /dev/mapper/cryptswap1: stat failed: No such file or directory alan@mesh:~$ grep swap /etc/fstab # swap was on /dev/sdg5 during installation #UUID=22d3f7f0-f715-4582-81ba-dcbd4cdd1495 noneswapsw 0 0 /dev/mapper/cryptswap1 none swap sw 0 0 alan@mesh:~$ sudo fdisk -l Disk /dev/sda: 115.0 GB, 115033153536 bytes 255 heads, 63 sectors/track, 13985 cylinders, total 224674128 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x000ba2ed Device Boot Start End Blocks Id System /dev/sda1 *2048 206847 1024007 HPFS/NTFS/exFAT /dev/sda2 206848 224671743 1122324487 HPFS/NTFS/exFAT Disk /dev/sdb: 200.0 GB, 200049647616 bytes 255 heads, 63 sectors/track, 24321 cylinders, total 390721968 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0xf0fa0806 Device Boot Start End Blocks Id System /dev/sdb12048 349304831 1746513927 HPFS/NTFS/exFAT /dev/sdb2 374722558 390721535 79994895 Extended /dev/sdb3 * 349304832 37472051112707840 83 Linux /dev/sdb5 374722560 390721535 7999488 82 Linux swap / Solaris Partition table entries are not in disk order ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libecryptfs0 96-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9 Uname: Linux 3.2.0-18-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.94.1-0ubuntu2 Architecture: amd64 Date: Tue Mar 13 09:56:56 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120215) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: ecryptfs-utils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to:
[Touch-packages] [Bug 953875]
(In reply to Lennart Poettering from comment #6) Hmm, please use parse_bytes() for parsing byte values. Sorry, I meant parse_size() of course. -- 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/953875 Title: Encrypted swap no longer mounted at bootup Status in eCryptfs: Fix Released Status in systemd: Fix Released Status in ecryptfs-utils package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Fix Released Status in ecryptfs-utils source package in Vivid: Fix Released Status in systemd source package in Vivid: Fix Released Status in ubiquity source package in Vivid: Fix Released Status in systemd package in Debian: Fix Released Bug description: SUMMARY === During installation with encrypt my home folder mode, a broken /etc/crypttab gets created which defines a non-existing swap device (usually cryptswap1) with a UUID. This will also be put into /etc/fstab. As after installation the UUID does not exist, such systems don't have any actual swap. UPGRADE FIX === An upgrade to Ubuntu 15.04 (vivid) will detect and comment out these broken swap devices from /etc/fstab and /etc/crypttab. If you actually want to use those, do these steps: - Find the swap device that was meant to be used in sudo fdisk -l (it should say Linux swap in the last column), remember the device name (something like /dev/sda5) - Find the UUID in /etc/crypttab (the long alphanumeric ID after UUID=) - Run sudo mkswap -U 1234... /dev/sda5, replacing 1234 with the above UUID, and /dev/sda5 with the device name from step 1. - Edit /etc/crypttab to append ,offset=1024 in the fourth (last) column of the cryptswap1 line; ensure that there is *no space* between the cipher=aes-cbc-essiv:sha256 and the appended option. If there is a leading # in the file, remove that too. - If there is a leading # in /etc/fstab in the line starting with /dev/mapper/cryptswap1 line, remove that. - Run sudo update-initramfs -u. ORIGINAL REPORT === Clean install of 12.04 and with encrypted home for my user. Did all updates and now the bootup hangs waiting for swap to become available and it never seems to ever finish. The 200GB SSD below is my boot drive and root filesystem. alan@mesh:~$ sudo swapon -a [sudo] password for alan: swapon: /dev/mapper/cryptswap1: stat failed: No such file or directory alan@mesh:~$ grep swap /etc/fstab # swap was on /dev/sdg5 during installation #UUID=22d3f7f0-f715-4582-81ba-dcbd4cdd1495 noneswapsw 0 0 /dev/mapper/cryptswap1 none swap sw 0 0 alan@mesh:~$ sudo fdisk -l Disk /dev/sda: 115.0 GB, 115033153536 bytes 255 heads, 63 sectors/track, 13985 cylinders, total 224674128 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x000ba2ed Device Boot Start End Blocks Id System /dev/sda1 *2048 206847 1024007 HPFS/NTFS/exFAT /dev/sda2 206848 224671743 1122324487 HPFS/NTFS/exFAT Disk /dev/sdb: 200.0 GB, 200049647616 bytes 255 heads, 63 sectors/track, 24321 cylinders, total 390721968 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0xf0fa0806 Device Boot Start End Blocks Id System /dev/sdb12048 349304831 1746513927 HPFS/NTFS/exFAT /dev/sdb2 374722558 390721535 79994895 Extended /dev/sdb3 * 349304832 37472051112707840 83 Linux /dev/sdb5 374722560 390721535 7999488 82 Linux swap / Solaris Partition table entries are not in disk order ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libecryptfs0 96-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9 Uname: Linux 3.2.0-18-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.94.1-0ubuntu2 Architecture: amd64 Date: Tue Mar 13 09:56:56 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120215) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: ecryptfs-utils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ecryptfs/+bug/953875/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1433059] Re: Screen not dimmed after period of inactivity.
eezacque, thank you for reporting this and helping make Ubuntu better. As per http://www.asus.com/Motherboards/Z97PROWiFi_ac/HelpDesk_Download/ an update to your computer's buggy and outdated BIOS is available (2205). If you update to this following https://help.ubuntu.com/community/BIOSUpdate does it change anything? If it doesn't, could you please both specify what happened, and provide the output of the following terminal command: sudo dmidecode -s bios-version sudo dmidecode -s bios-release-date For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette . Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful. As well, you don't have to create a new bug report. Once the BIOS is updated, and the information above is provided, then please mark this report Status New. Thank you for your understanding. ** Tags added: bios-outdated-2205 ** Changed in: xorg (Ubuntu) Importance: Undecided = Low ** Changed in: xorg (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1433059 Title: Screen not dimmed after period of inactivity. Status in xorg package in Ubuntu: Incomplete Bug description: Sooner or later, the screen stops getting dimmed after a set period of inactivity; only a reboot solves this. As a result, the implied request for password upon screen dim doesn't take place, either ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-31.43-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-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 17 12:41:18 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, 4.0.0-04rc3-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 (143 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-31-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 (132 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1433059/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1433263] Re: lasmetal76
lecourt, thank you for taking the time to report this issue and helping to make Ubuntu better. We noticed that some of the sentences in this bug report are not in English. If they were translated to English they would be more understandable to triagers. Could you please translate them? ** Tags added: bios-outdated-a07 ** Changed in: xorg (Ubuntu) Importance: Undecided = Low ** Changed in: xorg (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1433263 Title: lasmetal76 Status in xorg package in Ubuntu: Incomplete Bug description: bonjour j ai un probleme des que je mais un film sur mon disque dur portable par usb et que je le mais sur ma tv je ne le trouve pas comme si sa ne copier rien pouver vous m aider ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-46.79-generic 3.13.11-ckt15 Uname: Linux 3.13.0-46-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] est un dossier: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.113 Mon Dec 1 21:08:13 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.7 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 Date: Tue Mar 17 19:44:21 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Subsystem: Dell Device [1028:05d7] NVIDIA Corporation GK106 [GeForce GTX 645 OEM] [10de:11c4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation Device [10de:1029] InstallationDate: Installed on 2015-02-18 (27 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Alienware Alienware X51 R2 ProcEnviron: LANGUAGE=fr_FR PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-46-generic root=UUID=b46c7b34-3fe6-4fad-80a0-6419c8e94721 ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/17/2014 dmi.bios.vendor: Alienware dmi.bios.version: A06 dmi.board.name: 0PGRP5 dmi.board.vendor: Alienware dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.chassis.version: 00 dmi.modalias: dmi:bvnAlienware:bvrA06:bd03/17/2014:svnAlienware:pnAlienwareX51R2:pvr00:rvnAlienware:rn0PGRP5:rvrA01:cvnAlienware:ct3:cvr00: dmi.product.name: Alienware X51 R2 dmi.product.version: 00 dmi.sys.vendor: Alienware version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1~ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.3 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Mar 17 19:09:01 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.15.1-0ubuntu2.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1433263/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 533416] Re: Apt-p2p needs some promotion
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: software-properties (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/533416 Title: Apt-p2p needs some promotion Status in apt-p2p package in Ubuntu: Triaged Status in software-properties package in Ubuntu: Confirmed Bug description: Binary package hint: apt This is a wishlist/bug in apt-p2p. Currently, apt-p2p is not very well know; its only known by people who have been working with ubuntu long enough. I believe that there should be an option in the software source of gnome to use apt-p2p to make users informed that they have this option. Apt-p2p is important in the fact that it decreases the load on the ubuntu-servers, especially during upgrades. If more people use it, apt-p2p can possibly become more popular, and therefore more packages would be able to be downloaded using it. In addition, Apt-p2p should have a fallback after timeout option where it falls back to the ubuntu repository after waiting for a set amount of time (timeout). This ensures that the packages/repository that the user was trying to download will be downloaded, and will be added to the apt-p2p pool. The next user will then have more chance of downloading the package/repository from apt-p2p. This also prevents users from getting hung on certain repositories where there are not many peers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-p2p/+bug/533416/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1444297] Re: ubuntu vivid: last/w broken
it seems to have been fixed now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1444297 Title: ubuntu vivid: last/w broken Status in sysvinit package in Ubuntu: New Bug description: output of last and w does not show any logged in users. vivid$ w 08:51:58 up 11 min, 0 users, load average: 0.60, 1.42, 1.14 USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT debianjessie$w 08:52:23 up 88 days, 20:21, 14 users, load average: 0.20, 0.14, 0.15 USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT arved:0Fri11 ?xdm? 18:48m 0.03s /bin/sh /usr/bin/x-session-manager [..] vivid$ last reboot system boot 3.19.0-13-generi Wed Apr 15 08:40 - 08:53 (00:12) reboot system boot 3.19.0-13-generi Tue Apr 14 17:43 - 08:53 (15:09) debianjessie$ last arvedpts/17 baklava.localWed Apr 15 08:52 still logged in grepping for my username in /var/log/wtmp does not show any results on ubuntu, so i think the files are not written correctly. $ lsb_release -rd Description:Ubuntu Vivid Vervet (development branch) Release:15.04 $ apt-cache policy sysvinit-utils sysvinit-utils: Installed: 2.88dsf-53.2ubuntu12 Candidate: 2.88dsf-53.2ubuntu12 Version table: *** 2.88dsf-53.2ubuntu12 0 500 http://de.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1444297/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1409332] Re: Mouse cursor freezes, when using e.g. youtube in chromium, and stays that way
** Tags added: latest-bios-2.6.6 -- 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/1409332 Title: Mouse cursor freezes, when using e.g. youtube in chromium, and stays that way Status in xorg package in Ubuntu: Incomplete Bug description: I can not make this happen, if I use Firefox, but it happens, if I use Chromium browser and play youtube video. Visible mouse cursor stops moving. Still I can move mouse and use it, but it is hard, when you don't see where the cursor effectively is. This seems to happen only, if I have hardware acceleration enabled in advanced settings. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: chromium-browser 39.0.2171.65-0ubuntu0.14.04.1.1064 ProcVersionSignature: Ubuntu 3.13.0-43.72-lowlatency 3.13.11.11 Uname: Linux 3.13.0-43-lowlatency x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Jan 10 22:23:29 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-21 (111 days ago) InstallationMedia: Ubuntu-Studio 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.1) SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.chromium.browser: [deleted] mtime.conffile..etc.chromium.browser.default: 2014-09-28T10:04:54.426898 --- ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CurrentDesktop: XFCE CurrentDmesg: [ 373.553548] perf samples too long (2509 2500), lowering kernel.perf_event_max_sample_rate to 5 DRM.card0.VGA.1: edid-base64: AP///wAebW9DLDQEABEPAQNuIht46i7lpFdKnCURUFSla4AxT0VPYU+BgAEBAQEBAQEBMCoAmFEAKkAwcBMAUg4RAAAe/QA4Sx5TDgAKICAgICAg/ABMMTcxNVMKICAgICAg/AAKICAgICAgICAgICAgAJg= dpms: On modes: 1280x1024 1280x1024 1152x864 1024x768 1024x768 1024x768 832x624 800x600 800x600 640x480 640x480 720x400 enabled: enabled status: connected Desktop-Session: 'ubuntustudio' '/etc/xdg/xdg-ubuntustudio:/usr/share/upstart/xdg:/etc/xdg:/etc/xdg' '/usr/share/ubuntustudio:/usr/share/xfce4:/usr/local/share/:/usr/share/:/usr/share' DetectedPlugins: DistroRelease: Ubuntu 14.04 EcryptfsInUse: Yes Env: 'None' 'None' InstallationDate: Installed on 2014-09-21 (180 days ago) InstallationMedia: Ubuntu-Studio 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.1) Load-Avg-1min: 0.61 Load-Processes-Running-Percent: 0.2% MachineType: Dell Inc. OptiPlex 745 Package: xorg PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-46-lowlatency root=UUID=d012c1bd-7e56-4035-b321-38d20cb14421 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-46.79-lowlatency 3.13.11-ckt15 Tags: trusty Uname: Linux 3.13.0-46-lowlatency x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lp lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/26/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.6 dmi.board.name: 0RF703 dmi.board.vendor: Dell Inc. dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.6.6:bd06/26/2011:svnDellInc.:pnOptiPlex745:pvr:rvnDellInc.:rn0RF703:rvr:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 745 dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.chromium.browser: [deleted] mtime.conffile..etc.chromium.browser.default: 2014-09-28T10:04:54.426899 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1409332/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1409332] Re: Mouse cursor freezes, when using e.g. youtube in chromium, and stays that way
Jarno Suni, thank you for reporting this and helping make Ubuntu better. Could you please test for this via http://cdimage.ubuntu.com/daily- live/current/ and advise to the results? ** No longer affects: chromium-browser (Ubuntu) ** Changed in: xorg (Ubuntu) Importance: Undecided = Medium ** Changed in: xorg (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1409332 Title: Mouse cursor freezes, when using e.g. youtube in chromium, and stays that way Status in xorg package in Ubuntu: Incomplete Bug description: I can not make this happen, if I use Firefox, but it happens, if I use Chromium browser and play youtube video. Visible mouse cursor stops moving. Still I can move mouse and use it, but it is hard, when you don't see where the cursor effectively is. This seems to happen only, if I have hardware acceleration enabled in advanced settings. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: chromium-browser 39.0.2171.65-0ubuntu0.14.04.1.1064 ProcVersionSignature: Ubuntu 3.13.0-43.72-lowlatency 3.13.11.11 Uname: Linux 3.13.0-43-lowlatency x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Jan 10 22:23:29 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-21 (111 days ago) InstallationMedia: Ubuntu-Studio 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.1) SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.chromium.browser: [deleted] mtime.conffile..etc.chromium.browser.default: 2014-09-28T10:04:54.426898 --- ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CurrentDesktop: XFCE CurrentDmesg: [ 373.553548] perf samples too long (2509 2500), lowering kernel.perf_event_max_sample_rate to 5 DRM.card0.VGA.1: edid-base64: AP///wAebW9DLDQEABEPAQNuIht46i7lpFdKnCURUFSla4AxT0VPYU+BgAEBAQEBAQEBMCoAmFEAKkAwcBMAUg4RAAAe/QA4Sx5TDgAKICAgICAg/ABMMTcxNVMKICAgICAg/AAKICAgICAgICAgICAgAJg= dpms: On modes: 1280x1024 1280x1024 1152x864 1024x768 1024x768 1024x768 832x624 800x600 800x600 640x480 640x480 720x400 enabled: enabled status: connected Desktop-Session: 'ubuntustudio' '/etc/xdg/xdg-ubuntustudio:/usr/share/upstart/xdg:/etc/xdg:/etc/xdg' '/usr/share/ubuntustudio:/usr/share/xfce4:/usr/local/share/:/usr/share/:/usr/share' DetectedPlugins: DistroRelease: Ubuntu 14.04 EcryptfsInUse: Yes Env: 'None' 'None' InstallationDate: Installed on 2014-09-21 (180 days ago) InstallationMedia: Ubuntu-Studio 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.1) Load-Avg-1min: 0.61 Load-Processes-Running-Percent: 0.2% MachineType: Dell Inc. OptiPlex 745 Package: xorg PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-46-lowlatency root=UUID=d012c1bd-7e56-4035-b321-38d20cb14421 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-46.79-lowlatency 3.13.11-ckt15 Tags: trusty Uname: Linux 3.13.0-46-lowlatency x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lp lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/26/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.6 dmi.board.name: 0RF703 dmi.board.vendor: Dell Inc. dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.6.6:bd06/26/2011:svnDellInc.:pnOptiPlex745:pvr:rvnDellInc.:rn0RF703:rvr:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 745 dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.chromium.browser: [deleted] mtime.conffile..etc.chromium.browser.default: 2014-09-28T10:04:54.426899 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1409332/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1297286] Re: Wireless connection keeps disconnecting
I have also tried upgrading from 3.13 to 3.18 kernel. It did not solve the problem. After going through a lot of articles, today saw this bug, and the workaround given in tlue's post. I have tried it now. Wifi is up from last 22 minutes. I will update here after using it for sometime. -- 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/1297286 Title: Wireless connection keeps disconnecting Status in network-manager package in Ubuntu: Confirmed Bug description: Hi, I have a wireless access point that is at most 2 meters away. It keeps disconnecting with no apparent reason. I read somewhere that setting a static ip should help with the problem, but the problem seems pretty persistent. Thanks. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager 0.9.8.8-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-19.39-lowlatency 3.13.6 Uname: Linux 3.13.0-19-lowlatency x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 25 15:20:15 2014 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-03-20 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140319) IpRoute: default via 192.168.1.1 dev wlan0 proto static 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.245 metric 9 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2014-03-23T16:50:07.398742 nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH NETGEAR 74dc69be-e44f-4e15-a614-6c284d83d16b 802-11-wireless 1395737193 Tue 25 Mar 2014 10:46:33 AM EETyes no /org/freedesktop/NetworkManager/Settings/2 Wired connection 17ac79166-e72e-455b-ad9e-34574ee5d94e 802-3-ethernet1395571025 Sun 23 Mar 2014 12:37:05 PM EETyes no /org/freedesktop/NetworkManager/Settings/1 Egy Cloud 05f6b118-d332-4196-a7b0-810bba89bbf7 802-11-wireless 1395753542 Tue 25 Mar 2014 03:19:02 PM EETyes no /org/freedesktop/NetworkManager/Settings/0 AndroidAP 46037856-999f-4b3b-878d-13243f4ae958 802-11-wireless 1395592043 Sun 23 Mar 2014 06:27:23 PM EETyes no /org/freedesktop/NetworkManager/Settings/3 nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /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/1297286/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1390194] Re: info barra menú, notificación
Solucionado. Teclado funciona bien. Version Bios 1.90 Gracias. -- 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/1390194 Title: info barra menú, notificación Status in xorg package in Ubuntu: Incomplete Bug description: The update information is outdated. This may be caused by network problems or by a repository that is no longer available. Please update manually by selecting 'Show updates' from the indicator menu, and watching for any failing repositories. No entiendo ingles, perdonen, gracias. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Nov 6 19:52:43 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10, 3.13.0-37-generic, i686: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) virtualbox, 4.3.10, 3.13.0-39-generic, i686: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV620/M82 [Mobility Radeon HD 3450/3470] [1002:95c4] (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:ff1e] InstallationDate: Installed on 2014-09-25 (41 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release i386 (20140722.2) MachineType: TOSHIBA Satellite A300 ProcEnviron: LANGUAGE=es PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic root=UUID=868eb6a5-d54b-4ac7-af3b-bcb8d5432d0c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/20/2009 dmi.bios.vendor: INSYDE dmi.bios.version: 1.90 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvr1.90:bd03/20/2009:svnTOSHIBA:pnSatelliteA300:pvrPSAGCE-09800WCE:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Satellite A300 dmi.product.version: PSAGCE-09800WCE dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 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 Nov 6 19:24:01 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2.1 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1390194/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1444297] Re: ubuntu vivid: last/w broken
But i kust noted another problem, the reboot time is not recorded correctly: reboot system boot 3.19.0-14-generi Sat Apr 18 20:38 - 00:08 (03:30) reboot system boot 3.19.0-14-generi Fri Apr 17 09:14 - 00:08 (1+14:54) This started on Wednesday with the same update that fixed recording of the usernames. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1444297 Title: ubuntu vivid: last/w broken Status in sysvinit package in Ubuntu: New Bug description: output of last and w does not show any logged in users. vivid$ w 08:51:58 up 11 min, 0 users, load average: 0.60, 1.42, 1.14 USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT debianjessie$w 08:52:23 up 88 days, 20:21, 14 users, load average: 0.20, 0.14, 0.15 USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT arved:0Fri11 ?xdm? 18:48m 0.03s /bin/sh /usr/bin/x-session-manager [..] vivid$ last reboot system boot 3.19.0-13-generi Wed Apr 15 08:40 - 08:53 (00:12) reboot system boot 3.19.0-13-generi Tue Apr 14 17:43 - 08:53 (15:09) debianjessie$ last arvedpts/17 baklava.localWed Apr 15 08:52 still logged in grepping for my username in /var/log/wtmp does not show any results on ubuntu, so i think the files are not written correctly. $ lsb_release -rd Description:Ubuntu Vivid Vervet (development branch) Release:15.04 $ apt-cache policy sysvinit-utils sysvinit-utils: Installed: 2.88dsf-53.2ubuntu12 Candidate: 2.88dsf-53.2ubuntu12 Version table: *** 2.88dsf-53.2ubuntu12 0 500 http://de.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1444297/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1433448] Re: bug
Rofi, thank you for taking the time to report this and helping to make Ubuntu better. Unfortunately, this report didn't include enough information. You may find it helpful to read How to report bugs effectively http://www.chiark.greenend.org.uk/~sgtatham/bugs.html and https://wiki.ubuntu.com/ReportingBugs . We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem, 2. The behavior you expected, and 3. The behavior you actually encountered (in as much detail as possible). Thank you for your understanding. ** Changed in: xorg (Ubuntu) Importance: Undecided = Low ** Changed in: xorg (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1433448 Title: bug Status in xorg package in Ubuntu: Incomplete Bug description: eror bug ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic i686 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8.2 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Mar 18 13:37:40 2015 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.248+bdcom, 3.16.0-23-generic, i686: installed GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0506] InstallationDate: Installed on 2015-03-17 (0 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release i386 (20141022.1) MachineType: Acer Aspire 4752 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic root=UUID=a04e5905-64af-4e60-b5d5-8f9cea37154e ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2011 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.09 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire 4752 dmi.board.vendor: Acer dmi.board.version: V2.09 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.09 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.09:bd08/11/2011:svnAcer:pnAspire4752:pvrV2.09:rvnAcer:rnAspire4752:rvrV2.09:cvnAcer:ct9:cvrV2.09: dmi.product.name: Aspire 4752 dmi.product.version: V2.09 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 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: Wed Mar 18 11:43:35 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 22 vendor INL xserver.version: 2:1.16.0-1ubuntu1.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1433448/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1434259] Re: still screen freeze
gord rutherford, thank you for reporting this and helping make Ubuntu better. As per http://www.asus.com/Motherboards/P5Q_PRO/HelpDesk_Download/ an update to your computer's buggy and outdated BIOS is available (2102). If you update to this following https://help.ubuntu.com/community/BIOSUpdate does it change anything? If it doesn't, could you please both specify what happened, and provide the output of the following terminal command: sudo dmidecode -s bios-version sudo dmidecode -s bios-release-date For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette . Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful. As well, you don't have to create a new bug report. Once the BIOS is updated, and the information above is provided, then please mark this report Status Confirmed. Thank you for your understanding. ** Tags removed: needs-reassignment ** Tags added: bios-outdated-2102 ** Changed in: xorg (Ubuntu) Importance: Undecided = Low ** Changed in: xorg (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1434259 Title: still screen freeze Status in xorg package in Ubuntu: Incomplete Bug description: going to full screen on a video feed will freeze computer now first screen then whole computer ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-77.114-generic-pae 3.2.66 Uname: Linux 3.2.0-77-generic-pae i686 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86 Kernel Module 304.125 Mon Dec 1 19:55:52 PST 2014 GCC version: gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ApportVersion: 2.0.1-0ubuntu17.8 Architecture: i386 CurrentDmesg: [ 14.584235] input: Microsoft\xffc2\xffae\xffae LifeCam VX-2000 as /devices/pci:00/:00:1d.7/usb2/2-6/2-6:1.0/input/input6 [ 15.648283] init: plymouth-splash main process (1320) terminated with status 1 [ 16.102134] init: plymouth-stop pre-start process (1547) terminated with status 1 [ 25.696008] eth0: no IPv6 routers present Date: Thu Mar 19 12:50:24 2015 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation G92 [GeForce 8800 GT] [10de:0611] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Device [196e:053c] InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) MachineType: System manufacturer P5Q-PRO MarkForUpload: True ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-77-generic-pae root=UUID=b68166a6-2be8-41f8-b327-20235afa223a ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/31/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1104 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5Q-PRO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1104:bd07/31/2008:svnSystemmanufacturer:pnP5Q-PRO:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5Q-PRO dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.7.12-0ubuntu4 version.libdrm2: libdrm2 2.4.52-1~precise2 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.17 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1.2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1~precise~xup2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.19.0-0ubuntu1~xup1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3~precise~xup2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1434259/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1445832] [NEW] launcher - quick-view crash
Public bug reported: Desktop crashes and closes all apps when attempting to quick preview multiple of the same app. Example: If I have 2 terminal windows open and click on the launcher to view/switch them the desktop crashes and brings me to the login screen. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150410.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3 Uname: Linux 3.19.0-14-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] CurrentDesktop: Unity Date: Sat Apr 18 17:33:29 2015 InstallationDate: Installed on 2015-04-16 (2 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Beta amd64 (20150416) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (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 unity in Ubuntu. https://bugs.launchpad.net/bugs/1445832 Title: launcher - quick-view crash Status in unity package in Ubuntu: New Bug description: Desktop crashes and closes all apps when attempting to quick preview multiple of the same app. Example: If I have 2 terminal windows open and click on the launcher to view/switch them the desktop crashes and brings me to the login screen. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150410.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3 Uname: Linux 3.19.0-14-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] CurrentDesktop: Unity Date: Sat Apr 18 17:33:29 2015 InstallationDate: Installed on 2015-04-16 (2 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Beta amd64 (20150416) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1445832/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1074621] Re: Upgrade from 0.8.16~exp12ubuntu10.3 to 0.8.16~exp12ubuntu10.5 leads to segfault at 6c8b48f8 in libapt-pkg.so.4.12.0
Does setting the following help?
APT::Cache-start2;
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1445436/comments/3
** Changed in: apt (Ubuntu)
Status: Confirmed = Incomplete
--
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/1074621
Title:
Upgrade from 0.8.16~exp12ubuntu10.3 to 0.8.16~exp12ubuntu10.5 leads to
segfault at 6c8b48f8 in libapt-pkg.so.4.12.0
Status in apt package in Ubuntu:
Incomplete
Bug description:
Description: Ubuntu 12.04.1 LTS
Release: 12.04
On: amd64
From the kernel log:
[6846551.444387] apt-config[8190]: segfault at 6c8b48f8 ip 7fe84340ef84
sp 7fff76182160 error 6 in libapt-pkg.so.4.12.0[7fe8433d6000+121000]
[6846551.445957] apt-config[8191]: segfault at 6c8b48f8 ip 7fc124b41f84
sp 7fffa27470a0 error 6 in libapt-pkg.so.4.12.0[7fc124b09000+121000]
[6846551.512757] apt-get[8196]: segfault at 6c8b48f8 ip 7f754558bf84 sp
7fff27275a50 error 6 in libapt-pkg.so.4.12.0[7f7545553000+121000]
[6846580.877901] package-data-do[8538]: segfault at 7fe440e96010 ip
7fe3d348cf84 sp 7fff9e8ac0f0 error 6 in
libapt-pkg.so.4.12.0[7fe3d3454000+121000]
[6869450.441332] apt-config[27050]: segfault at 6c8b48f8 ip 7eff7923bf84
sp 797a1a30 error 6 in libapt-pkg.so.4.12.0[7eff79203000+121000]
[6869450.443617] apt-config[27051]: segfault at 6c8b48f8 ip 7f5048b95f84
sp 7fff8a6e9a70 error 6 in libapt-pkg.so.4.12.0[7f5048b5d000+121000]
[6869450.497879] apt-config[27095]: segfault at 6c8b48f8 ip 7f9543001f84
sp 7fffd7d0b2c0 error 6 in libapt-pkg.so.4.12.0[7f9542fc9000+121000]
[6869450.500143] apt-config[27096]: segfault at 6c8b48f8 ip 7fabaa460f84
sp 7fff82255ac0 error 6 in libapt-pkg.so.4.12.0[7fabaa428000+121000]
[6869456.275296] apt-get[27222]: segfault at 6c8b48f8 ip 7fa75199ef84 sp
7fffe2239f40 error 6 in libapt-pkg.so.4.12.0[7fa751966000+121000]
Tail of strace apt-get update:
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f1efdf71000
mprotect(0x7f1efda1a000, 32768, PROT_READ) = 0
mprotect(0x7f1efdd5a000, 16384, PROT_READ) = 0
mprotect(0x62d000, 4096, PROT_READ) = 0
mprotect(0x7f1efdf82000, 4096, PROT_READ) = 0
munmap(0x7f1efdf78000, 32702) = 0
brk(0) = 0x1cf7000
brk(0x1d18000) = 0x1d18000
open(/dev/null, O_WRONLY|O_CREAT|O_TRUNC, 0666) = 3
open(/usr/lib/locale/locale-archive, O_RDONLY|O_CLOEXEC) = 4
fstat(4, {st_mode=S_IFREG|0644, st_size=4447600, ...}) = 0
mmap(NULL, 4447600, PROT_READ, MAP_PRIVATE, 4, 0) = 0x7f1efc40c000
close(4)= 0
stat(/var/lib/apt/., {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++
Segmentation fault
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ NameVersion
Description
+++-===-===-==
ii apt 0.8.16~exp12ubuntu10.5
commandline package manager
dpkg.log of the recent upgrade from .3 to .5 attached. (I.e. there was
also other stuff upgraded at the same time.)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1074621/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1007410] Re: install crashed: segfault in libapt-pkg.so.4.12.0
Does setting the following help? APT::Cache-start2; https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1445436/comments/3 ** Changed in: apt (Ubuntu) Status: Confirmed = Incomplete ** Changed in: apt (Ubuntu) Status: Incomplete = Confirmed ** Changed in: apt (Ubuntu) Status: Confirmed = Incomplete -- 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/1007410 Title: install crashed: segfault in libapt-pkg.so.4.12.0 Status in apt package in Ubuntu: Incomplete Bug description: I am trying to install your operating system and it just crashed on me in mid installation. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: ubiquity 2.10.16 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 ApportVersion: 2.0.1-0ubuntu5 Architecture: amd64 CasperVersion: 1.315 Date: Fri Jun 1 09:16:22 2012 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity LiveMediaBuild: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) ProcEnviron: LANGUAGE=en_US.UTF-8 TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1007410/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1197809] Re: segfault error in libapt-pkg.so
Does setting the following help? APT::Cache-start2; https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1445436/comments/3 ** Tags added: amd64 saucy ** Changed in: apt (Ubuntu) Status: Confirmed = Incomplete -- 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/1197809 Title: segfault error in libapt-pkg.so Status in apt package in Ubuntu: Incomplete Bug description: Repository http://security.ubuntu.com/ubuntu precise-security multiverse seems to break system, provoking a segmentation fault: [5076854.232531] perl6490: segfault at 7f1a38ddda50 ip 7f1a39e258df sp 7fff801ff830 error 6 in libapt- pkg.so.4.12.0[7f1a39d5+121000] This has happened in several servers so it definetely seems to be something wrong at this repo. #211926 gnome-app-install crashed with SIGSEGV in pkgDepCache::CheckDep() Fix Released (2 comments) last updated 2011-04-11 view this bug Binary package hint: gnome-app-install Error ocurred when start session in Xfce Architecture: amd64 DistroRelease: Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1197809/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1117682] Re: apt-get crashes with a segmentation fault
Does setting the following help? APT::Cache-start2; https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1445436/comments/3 -- 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/1117682 Title: apt-get crashes with a segmentation fault Status in apt package in Ubuntu: Confirmed Bug description: When trying to --reinstall multiple packages with apt-get, it crashes with a segmentation fault. The command line: apt-get --reinstall install 2-or-more-packages... Syslog shows: kernel: [ 3322.059837] apt-get[14417]: segfault at 7fa5c24d65bc ip 7fa5bb931329 sp 7fffb0170528 error 4 in libapt-pkg.so.4.12.0[7fa5bb8e1000+121000] ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: apt 0.8.16~exp12ubuntu10.7 ProcVersionSignature: Ubuntu 3.2.0-37.58-generic 3.2.35 Uname: Linux 3.2.0-37-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 Date: Wed Feb 6 15:39:44 2013 InstallationMedia: Ubuntu-Server 12.04 LTS Precise Pangolin - Release amd64 (20120424.1) MarkForUpload: True ProcEnviron: TERM=xterm SHELL=/bin/bash PATH=(custom, no user) LANG=en_US.UTF-8 LANGUAGE=en_US: SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1117682/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1434557] Re: frozen desktop
brad haack, thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal: apport-collect 1434557 Please ensure you have xdiagnose installed, and that you click the Yes button for attaching additional debugging information. When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Changed in: xorg (Ubuntu) Importance: Undecided = Low ** Changed in: xorg (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1434557 Title: frozen desktop Status in xorg package in Ubuntu: Incomplete Bug description: Very often (about once/day) I'm experiencing a frozen desktop. minimal response from keyboard or mouse, usually degrades to no response. No response from ^-alt-F1 or ^-alt-esc. Here's today's Xorg.0.log.old: [47.809] (II) intel(0): Modeline 1280x1024x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e) [47.809] (II) intel(0): Modeline 1280x960x0.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e) [ 3682.886] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 0, position (0, 0), rotation normal, reflection none [ 3683.260] (II) AIGLX: Suspending AIGLX clients for VT switch [ 3735.480] (II) AIGLX: Resuming AIGLX clients after VT switch [ 3735.480] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 0, position (0, 0), rotation normal, reflection none [ 7662.648] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 0, position (0, 0), rotation normal, reflection none [ 7662.999] (II) AIGLX: Suspending AIGLX clients for VT switch [ 7807.242] (II) AIGLX: Resuming AIGLX clients after VT switch [ 7807.242] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 0, position (0, 0), rotation normal, reflection none [ 9095.040] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 0, position (0, 0), rotation normal, reflection none [ 9095.404] (II) AIGLX: Suspending AIGLX clients for VT switch [ 9896.981] (II) AIGLX: Resuming AIGLX clients after VT switch [ 9896.981] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 0, position (0, 0), rotation normal, reflection none (EE) [mi] EQ overflowing. Additional events will be discarded until existing events are processed. (EE) (EE) Backtrace: (EE) 0: /usr/bin/X (xorg_backtrace+0x4f) [0xb7686eaf] (EE) 1: /usr/bin/X (mieqEnqueue+0x213) [0xb7666fe3] (EE) 2: /usr/bin/X (QueuePointerEvents+0x6d) [0xb75342ed] (EE) 3: /usr/bin/X (xf86PostMotionEventM+0x24b) [0xb756da8b] (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6e12000+0x498f) [0xb6e1698f] (EE) 5: /usr/bin/X (0xb74df000+0x7e0f5) [0xb755d0f5] (EE) 6: /usr/bin/X (0xb74df000+0xa8dfb) [0xb7587dfb] (EE) 7: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400] (EE) 8: /usr/bin/X (0xb74df000+0x1ac170) [0xb768b170] (EE) 9: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400] (EE) 10: /usr/bin/X (0xb74df000+0x12d650) [0xb760c650] (EE) 11: /usr/bin/X (0xb74df000+0x4ebb0) [0xb752dbb0] (EE) 12: /usr/bin/X (DeliverRawEvent+0x65) [0xb752ddb5] (EE) 13: /usr/bin/X (0xb74df000+0x131730) [0xb7610730] (EE) 14: /usr/bin/X (0xb74df000+0x155a07) [0xb7634a07] (EE) 15: /usr/bin/X (mieqProcessDeviceEvent+0x204) [0xb7667414] (EE) 16: /usr/bin/X (mieqProcessInputEvents+0xfd) [0xb766753d] (EE) 17: /usr/bin/X (ProcessInputEvents+0x14) [0xb755d294] (EE) 18: /usr/bin/X (0xb74df000+0x3c9ac) [0xb751b9ac] (EE) 19: /usr/bin/X (0xb74df000+0x40ce5) [0xb751fce5] (EE) 20: /usr/bin/X (0xb74df000+0x2aa3e) [0xb7509a3e] (EE) 21: /lib/i386-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0xb70b6a83] (EE) 22: /usr/bin/X (0xb74df000+0x2aa74) [0xb7509a74] (EE) (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up the stack. (EE) [mi] mieq is *NOT* the cause. It is a victim. (EE) [mi] EQ overflow continuing. 100 events have been dropped. (EE) (EE) Backtrace: (EE) 0: /usr/bin/X (xorg_backtrace+0x4f) [0xb7686eaf] (EE) 1: /usr/bin/X (mieqEnqueue+0xe5) [0xb7666eb5] (EE) 2: /usr/bin/X (QueuePointerEvents+0x6d) [0xb75342ed] (EE) 3: /usr/bin/X (xf86PostMotionEventM+0x24b) [0xb756da8b] (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6e12000+0x498f) [0xb6e1698f] (EE) 5: /usr/bin/X (0xb74df000+0x7e0f5) [0xb755d0f5] (EE) 6: /usr/bin/X (0xb74df000+0xa8dfb) [0xb7587dfb] (EE) 7: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400] (EE) 8: /usr/bin/X (0xb74df000+0x1ac170) [0xb768b170] (EE) 9: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400] (EE) 10: /usr/bin/X
[Touch-packages] [Bug 1435587] Re: System slows down to almost unusable then freezes during usage (High kworker cpu usage etc)
Nick Dowson, thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal: apport-collect 1435587 Please ensure you have xdiagnose installed, and that you click the Yes button for attaching additional debugging information. ** Changed in: xorg (Ubuntu) Importance: Undecided = Low ** Changed in: xorg (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1435587 Title: System slows down to almost unusable then freezes during usage (High kworker cpu usage etc) Status in xorg package in Ubuntu: Incomplete Bug description: Hi, after an update about a month and a half / two months ago my system started freezing after a period of usage. This tends to happen about once a day... so generally after the laptop's been on for a few hours (not necessarily constantly), sometimes probably up to 8 or ten hours. But the freezing doesn't seem to correlate to any particular activity or application that I am using. When the freeze occurs, the system slows down and doing anything takes excruciatingly long. It never recovers from this and I have to shutdown. Sometime REISUB can take the system down but sometimes I just have to hold the power button to switch it off the harmful way! A few times I have managed to get 'System Activity' (KDE Task Manager) or top up before it has frozen completely and this has shown multiple Kworker processes using up huge amounts of CPU. Looking this up on the forums I found a couple of suggested solutions: I tried turning off acpi interrupts for certain gpes (http://askubuntu.com/questions/176565/why-does-kworker-cpu-usage-get- so-high). I initially thought this had helped, but it hasn't (possibly slowing down the frequency of the freezes). I also tried the drm_kms helper fix: https://souriguha.wordpress.com/2011/03/08/how-to-solve- problem-with-thinkpadkslowd-kworker-on-linux-kernel-2-35-2-36/. Alas, no success. As I said, the freezing first occured almost two months ago, whilst I was using Ubuntu 14.04. I upgrade to 14.10 to see if this would help the freeze but no luck. Happy to try further diagnostics or any suggested workarounds appreciated; I got a bit lost in the different wiki pages and wasn't sure whether this was really the same sort of freeze / crash as they were talking about (I don't think it really has anything to do with xorg!) Cheers. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-31.43-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 CurrentDesktop: KDE Date: Mon Mar 23 21:53:17 2015 InstallationDate: Installed on 2014-05-02 (325 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.1) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to utopic on 2015-02-17 (34 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1435587/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1445358] Re: [SVF1532X1EB, Realtek ALC233, Speaker, Internal] Pulseaudio fails to detect card
** Description changed: - I do not sound like a user or guest. - All well on the LiveUSB + Changing the System Language in Greek resulted in the corruption of the + sound in the entire system. This happened when the latest updates + applied and after a reboot. + + I have attempted a new installation in Greek getting the latest ISO + image and the problem exists there as well. + + If I go back (turn the system) to the English Language and reboot the + problem disappears. + + I have also tested another Language (Russian Localization) but the + problem does not occur. + + How to reproduce: + Apply the latest updates and install the Greek language packages (language-pack-el , language-pack-el-base). + Choose Greek as the system's language and reboot. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: pulseaudio 1:6.0-0ubuntu5 ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3 Uname: Linux 3.19.0-14-generic x86_64 ApportVersion: 2.17.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/by-path', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/timer', '/dev/snd/seq'] failed with exit code 1: CurrentDesktop: Unity Date: Fri Apr 17 09:48:39 2015 InstallationDate: Installed on 2015-04-15 (1 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Beta amd64 (20150415) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [SVF1532X1EB, Realtek ALC233, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/19/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: R1080DB dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnInsydeCorp.:bvrR1080DB:bd09/19/2014:svnSonyCorporation:pnSVF1532X1EB:pvrC10KBNMG:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: SVF1532X1EB dmi.product.version: C10KBNMG dmi.sys.vendor: Sony Corporation -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1445358 Title: [SVF1532X1EB, Realtek ALC233, Speaker, Internal] Pulseaudio fails to detect card Status in pulseaudio package in Ubuntu: Confirmed Bug description: Changing the System Language in Greek resulted in the corruption of the sound in the entire system. This happened when the latest updates applied and after a reboot. I have attempted a new installation in Greek getting the latest ISO image and the problem exists there as well. If I go back (turn the system) to the English Language and reboot the problem disappears. I have also tested another Language (Russian Localization) but the problem does not occur. How to reproduce: Apply the latest updates and install the Greek language packages (language-pack-el , language-pack-el-base). Choose Greek as the system's language and reboot. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: pulseaudio 1:6.0-0ubuntu5 ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3 Uname: Linux 3.19.0-14-generic x86_64 ApportVersion: 2.17.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/by-path', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/timer', '/dev/snd/seq'] failed with exit code 1: CurrentDesktop: Unity Date: Fri Apr 17 09:48:39 2015 InstallationDate: Installed on 2015-04-15 (1 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Beta amd64 (20150415) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [SVF1532X1EB, Realtek ALC233, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/19/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: R1080DB dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnInsydeCorp.:bvrR1080DB:bd09/19/2014:svnSonyCorporation:pnSVF1532X1EB:pvrC10KBNMG:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: SVF1532X1EB dmi.product.version: C10KBNMG dmi.sys.vendor: Sony
[Touch-packages] [Bug 1436498] Re: Inserting Logitech headset kills mouse window control
epicflux, thank you for reporting this and helping make Ubuntu better. Could you please test the latest upstream kernel available from the very top line at the top of the page (the release names are irrelevant for testing, and please do not test the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. If the test did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description: kernel-fixed-upstream kernel-fixed-upstream-3.XY-rcZ Where XY and Z are numbers corresponding to the kernel version. If the mainline kernel does not fix this bug, please add the following tags: kernel-bug-exists-upstream kernel-bug-exists-upstream-3.XY-rcZ Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding. ** Package changed: xorg (Ubuntu) = linux (Ubuntu) ** Changed in: linux (Ubuntu) Importance: Undecided = Medium ** Changed in: linux (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1436498 Title: Inserting Logitech headset kills mouse window control Status in linux package in Ubuntu: Incomplete Bug description: Inserting a Logitech headset seems to screw up the mouse control. Keyboard input is unaffected. This seems very similar to the issues reproted in this bug report: 993655 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16 Uname: Linux 3.13.0-48-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Mar 25 14:40:12 2015 DistUpgraded: 2014-12-12 17:23:36,683 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: rts_bpp, 1.1, 3.0.0-17-generic, x86_64: built rts_bpp, 1.1, 3.5.0-49-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:2706] InstallationDate: Installed on 2012-10-18 (887 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MachineType: System76, Inc. Gazelle Professional ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-48-generic root=UUID=6fb59d06-ec00-44f4-abcc-0da0f018be93 ro quiet splash acpi_os_name=Linux acpi_osi= vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-12-12 (102 days ago) dmi.bios.date: 09/27/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: Gazelle Professional dmi.board.vendor: System76, Inc. dmi.board.version: gazp8 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd09/27/2012:svnSystem76,Inc.:pnGazelleProfessional:pvrgazp8:rvnSystem76,Inc.:rnGazelleProfessional:rvrgazp8:cvnNoEnclosure:ct9:cvrN/A: dmi.product.name: Gazelle Professional dmi.product.version: gazp8 dmi.sys.vendor: System76, Inc. version.compiz: compiz 1:0.9.11.3+14.04.20141104-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1~ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.4 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Wed Mar 25 12:10:53 2015 xserver.configfile: default xserver.errors: xserver.logfile:
[Touch-packages] [Bug 1436491] Re: Ubuntu 14.10 desktop amd64 live CD gives no graphical desktop on MacBookPro 8, 3
PeterKnaggs, thank you for reporting this and helping make Ubuntu better. Could you please test http://cdimage.ubuntu.com/daily- live/current/ and advise to the results? ** Description changed: - The Ubuntu 14.10 desktop amd64 live CD gives no graphical desktop on a Apple MacBookPro 8,3 (A1397) 2011 - (hardware described here: http://www.penlug.org/foswiki/bin/view/Main/HardwareInfoAppleMacBookProA1297 ). - - I also tested an upgrade from Ubuntu 14.04.02LTS to Ubuntu 14.10 and similarly lost the graphical login - as xorg no longer started (only the tty terminal login prompt appeared after reboot). - - Please let me know if any further info is needed to reproduce the issue on your side, or if you'd need me to - collect any further diagnostic info from the system, I'm a software engineer so I should be able to follow any - instructions you provide, including compiling patches etc. - - I'm somewhat surprised that xorg would stop working on the Apple MacBookPro 8,3 as it uses the - free radeon driver in Ubuntu 14.10 which has worked fine through many many Ubuntu upgrades - on this particular machine. - - To reproduce the issue: attempt to start an Apple MacBookPro 8,3 using the Ubuntu 14.10 desktop amd64 live CD. - Notice that no graphical desktop ever appears. - Alternately, after a fresh install of Ubuntu 14.04.02LTS, upgrade to 14.10, and notice no graphical desktop, only - they tty terminal login is presented. - - I've tried searching for an explanation through many launchpad bugs, but - haven't found any other reports. + The Ubuntu 14.10 desktop amd64 live CD gives no graphical desktop. + Alternately, after a fresh install of Ubuntu 14.04.02LTS, upgrade to + 14.10, and notice no graphical desktop, only they tty terminal login is + presented. ** Changed in: xorg (Ubuntu) Importance: Undecided = Low ** Changed in: xorg (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1436491 Title: Ubuntu 14.10 desktop amd64 live CD gives no graphical desktop on MacBookPro 8,3 Status in xorg package in Ubuntu: Incomplete Bug description: The Ubuntu 14.10 desktop amd64 live CD gives no graphical desktop. Alternately, after a fresh install of Ubuntu 14.04.02LTS, upgrade to 14.10, and notice no graphical desktop, only they tty terminal login is presented. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1436491/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1353951] Re: gnome online accounts require autentication on startup
The bug reiterates in Ubuntu GNOME 15.04. I tried to lower the security level on Google's account admin page so the GNOME can get clearance in accessing the Google data (notwithstanding Google's threat of security vulnerability), but GNOME still fails to authenticate even with correct password typed in. I don't think the patch file works. I think it is not so much of a software problem, but a business issue to be settled between Canonical/Fedora and Google. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1353951 Title: gnome online accounts require autentication on startup Status in Evolution Data Server: Fix Released Status in evolution-data-server package in Ubuntu: Fix Released Status in gnome-online-accounts package in Ubuntu: Invalid Status in evolution-data-server source package in Trusty: Fix Released Status in gnome-online-accounts source package in Trusty: Invalid Bug description: [Impact] Google calendar integration is broken, and users are requested to re-enter their Google password everytime they log in, or everytime they enable/disable their Google account from the System Settings. [Test Case] 1) open gnome-online-accounts 2) click + and add a google account 3) enter user name and password 4) confirm permissions for gnome 5) Black window pops up and asks for google password, but does not accept the correct password. Google Contacts are not available in Gnome or Thunderbird [Regression Potential] Minimal: the fix is a backport of a patch from the evolution-data-server code which is already in 14.10, and which only touches the calendar code (which is currently broken). Gnome online accounts requires autentication on startup, but even typing the correct password in the box, the program says the password is wrong. By the way evolution and other programs work well with online accounts. I'm using Ubuntu-gnome 14.04 LTS 64bit on different machines and have the same behaviour. Just to be clear: online-accounts works well, just at startup it opens an administration window where it requires to insert the password for my google accounts; if I type the correct password it says that the password is wrong, the only way to close the window is to click on discard and then all works well. To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-data-server/+bug/1353951/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1445846] Re: nm-online returns too early
Note that I'm working with vivid and network-manager 0.9.10.0-4ubuntu15 with systemd. -- 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/1445846 Title: nm-online returns too early Status in network-manager package in Ubuntu: New Bug description: I am setting up a totem system which mounts a remote file system at boot and starts an application from it. I found that randomly the boot fails because the mount fails due to Network unreachable errors. I made sure the mount unit waits for network-online.target to be rached, however I found that NetworkManager-wait-online.service returns well before the IP address has been obtained by DHCP. This is a cleaned up log extract: apr 19 02:22:13 terminale2 systemd[1]: Starting Network. apr 19 02:22:13 terminale2 NetworkManager[660]: info (eth2): carrier is OFF apr 19 02:22:13 terminale2 NetworkManager[660]: info (eth2): new Ethernet device (driver: 'r8169' ifindex: 2) apr 19 02:22:13 terminale2 NetworkManager[660]: info (eth2): exported as /org/freedesktop/NetworkManager/Devices/1 apr 19 02:22:13 terminale2 NetworkManager[660]: info (eth2): device state change: unmanaged - unavailable (reason 'managed') [10 20 2] apr 19 02:22:13 terminale2 systemd[1]: Starting Network Manager Wait Online... apr 19 02:22:13 terminale2 NetworkManager[660]: info (eth2): preparing device apr 19 02:22:18 terminale2 NetworkManager[660]: info startup complete apr 19 02:22:18 terminale2 systemd[1]: Started Network Manager Wait Online. apr 19 02:22:18 terminale2 systemd[1]: Reached target Network is Online. apr 19 02:22:18 terminale2 systemd[1]: Starting Network is Online. apr 19 02:22:18 terminale2 systemd[1]: Mounting /nas... apr 19 02:22:18 terminale2 mount[810]: mount error(101): Network is unreachable Then after a while: apr 19 02:22:26 terminale2 NetworkManager[660]: info Activation (eth2) successful, device activated. Attached you find the whole journal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1445846/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1439101] Re: impossible receive MMS any operator on bq aquaris E4.5
** Description changed: + In France no MMS is received regardless of the operator used on bq + aquaris E4.5 ubuntu Edition - In France no MMS is received regardless of the operator used on bq aquaris E4.5 ubuntu Edition + My operator is Free, and sure it seems it doesn't matter. + + In the same time, let me telle you than I detect than MMS didn't sent + when WIFI is activ. I've read some other people who send this + information. + + Anyway, for resume, For send a MMS, it's OK whan WIFI is OFF, don'T if + ON, and in all of case we don't receive MMS :-(( + + Thank's to you for fix it faster. + + Sorry for my approximativ english. + + Fabien ** Tags added: bug-mms-send-receive ** Description changed: In France no MMS is received regardless of the operator used on bq aquaris E4.5 ubuntu Edition - My operator is Free, and sure it seems it doesn't matter. + For information, my operator is Free even if it seems it doesn't matter. - In the same time, let me telle you than I detect than MMS didn't sent + In the same time, let me tell you than I had detect than MMS didn't sent when WIFI is activ. I've read some other people who send this information. Anyway, for resume, For send a MMS, it's OK whan WIFI is OFF, don'T if ON, and in all of case we don't receive MMS :-(( Thank's to you for fix it faster. Sorry for my approximativ english. Fabien ** Description changed: In France no MMS is received regardless of the operator used on bq aquaris E4.5 ubuntu Edition For information, my operator is Free even if it seems it doesn't matter. In the same time, let me tell you than I had detect than MMS didn't sent - when WIFI is activ. I've read some other people who send this - information. + when WIFI is ON. I've read some other people who send this information. Anyway, for resume, For send a MMS, it's OK whan WIFI is OFF, don'T if ON, and in all of case we don't receive MMS :-(( Thank's to you for fix it faster. Sorry for my approximativ english. Fabien ** Description changed: In France no MMS is received regardless of the operator used on bq aquaris E4.5 ubuntu Edition For information, my operator is Free even if it seems it doesn't matter. In the same time, let me tell you than I had detect than MMS didn't sent - when WIFI is ON. I've read some other people who send this information. + when WIFI is ON. I've read some other people who send the same + information so it's seems to be a real bug. Anyway, for resume, For send a MMS, it's OK whan WIFI is OFF, don'T if ON, and in all of case we don't receive MMS :-(( Thank's to you for fix it faster. Sorry for my approximativ english. Fabien -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1439101 Title: impossible receive MMS any operator on bq aquaris E4.5 Status in Messaging App: New Status in Ubuntu Mobile: New Status in messaging-app package in Ubuntu: Confirmed Bug description: In France no MMS is received regardless of the operator used on bq aquaris E4.5 ubuntu Edition For information, my operator is Free even if it seems it doesn't matter. In the same time, let me tell you than I had detect than MMS didn't sent when WIFI is ON. I've read some other people who send the same information so it's seems to be a real bug. Anyway, for resume, For send a MMS, it's OK whan WIFI is OFF, don'T if ON, and in all of case we don't receive MMS :-(( Thank's to you for fix it faster. Sorry for my approximativ english. Fabien To manage notifications about this bug go to: https://bugs.launchpad.net/messaging-app/+bug/1439101/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1435694] Re: Ubuntu's dialogs have corrupted font
NoBugs!, thank you for reporting this and helping make Ubuntu better. Could you please test http://cdimage.ubuntu.com/daily-live/current/ and advise to the results? ** Changed in: xorg (Ubuntu) Importance: Undecided = Medium ** Changed in: xorg (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1435694 Title: Ubuntu's dialogs have corrupted font Status in xorg package in Ubuntu: Incomplete Bug description: Starting just today, I noticed some really goofy font corruption on dialogs. I see it in Nautilus, Rhythmbox, Firefox etc. See attached for screenshot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-46.79-generic 3.13.11-ckt15 Uname: Linux 3.13.0-46-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.7 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 Date: Tue Mar 24 00:18:32 2015 DistUpgraded: 2014-04-19 04:44:12,758 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:054e] InstallationDate: Installed on 2013-11-23 (485 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Dell Inc. XPS L521X ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-46-generic.efi.signed root=UUID=8e997c12-0ee0-422b-a7e4-a7cb0a74f38f ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to trusty on 2014-04-19 (338 days ago) dmi.bios.date: 12/17/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 0C5Y96 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A16 dmi.modalias: dmi:bvnDellInc.:bvrA16:bd12/17/2013:svnDellInc.:pnXPSL521X:pvrA16:rvnDellInc.:rn0C5Y96:rvrA00:cvnDellInc.:ct8:cvrA16: dmi.product.name: XPS L521X dmi.product.version: A16 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1~ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.4 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sun Mar 22 14:18:48 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4333 vendor AUO xserver.version: 2:1.15.1-0ubuntu2.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1435694/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1390625] Re: mouse cursor gets corrupted
I can confirm I also have this issue using Macbook Air, mid 2013, ElementaryOS Freya. Using REFInd for dual booting if that would matter. -- 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/1390625 Title: mouse cursor gets corrupted Status in elementary OS: Confirmed Status in Mesa: New Status in Unity: Invalid Status in unity package in Ubuntu: Confirmed Status in xorg-lts-utopic package in Ubuntu: Confirmed Bug description: In Ubuntu 14.10, the mouse cursor graphic gets corrupted under certain occasions. It then looks flipped, sheared or shows fragments of a previous cursor. * when switching the cursor them forth and back in Gnome Tweak Tool * when dragdropping a document icon Maybe related, the cursor does not always show the correct image scale on a high-dpi display (this was working right in 14.04). For example after login, or when hovering specific areas, or on mouse down to start a dragdrop, the cursor appears 1/4 the expected size. Attached is a photo of a corrupted cursor (whereas a screenshot with Gimp showed the uncorrupted cursor). ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 BootLog: * Setting up X socket directories... [400G [394G[ OK ] CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Nov 7 22:12:52 2014 DistUpgraded: 2014-11-04 18:35:56,188 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3978] InstallationDate: Installed on 2014-02-02 (278 days ago) InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140201) MachineType: LENOVO 20266 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed root=UUID=4bfb3686-b9f7-487d-81f6-eceb41097ad9 ro quiet splash acpi_backlight=vendor SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2014-11-04 (3 days ago) dmi.bios.date: 10/31/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN31WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Yoga2 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 Pro dmi.modalias: dmi:bvnLENOVO:bvr76CN31WW:bd10/31/2013:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro: dmi.product.name: 20266 dmi.product.version: Lenovo Yoga 2 Pro dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Fri Nov 7 14:54:59 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: [dix] ELAN Touchscreen: unable to find touch point 1 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16970 vendor SDC xserver.version: 2:1.16.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1390625/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1445846] [NEW] nm-online returns too early
Public bug reported: I am setting up a totem system which mounts a remote file system at boot and starts an application from it. I found that randomly the boot fails because the mount fails due to Network unreachable errors. I made sure the mount unit waits for network-online.target to be rached, however I found that NetworkManager-wait-online.service returns well before the IP address has been obtained by DHCP. This is a cleaned up log extract: apr 19 02:22:13 terminale2 systemd[1]: Starting Network. apr 19 02:22:13 terminale2 NetworkManager[660]: info (eth2): carrier is OFF apr 19 02:22:13 terminale2 NetworkManager[660]: info (eth2): new Ethernet device (driver: 'r8169' ifindex: 2) apr 19 02:22:13 terminale2 NetworkManager[660]: info (eth2): exported as /org/freedesktop/NetworkManager/Devices/1 apr 19 02:22:13 terminale2 NetworkManager[660]: info (eth2): device state change: unmanaged - unavailable (reason 'managed') [10 20 2] apr 19 02:22:13 terminale2 systemd[1]: Starting Network Manager Wait Online... apr 19 02:22:13 terminale2 NetworkManager[660]: info (eth2): preparing device apr 19 02:22:18 terminale2 NetworkManager[660]: info startup complete apr 19 02:22:18 terminale2 systemd[1]: Started Network Manager Wait Online. apr 19 02:22:18 terminale2 systemd[1]: Reached target Network is Online. apr 19 02:22:18 terminale2 systemd[1]: Starting Network is Online. apr 19 02:22:18 terminale2 systemd[1]: Mounting /nas... apr 19 02:22:18 terminale2 mount[810]: mount error(101): Network is unreachable Then after a while: apr 19 02:22:26 terminale2 NetworkManager[660]: info Activation (eth2) successful, device activated. Attached you find the whole journal. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Attachment added: whole journal showing the timing https://bugs.launchpad.net/bugs/1445846/+attachment/4379227/+files/journal -- 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/1445846 Title: nm-online returns too early Status in network-manager package in Ubuntu: New Bug description: I am setting up a totem system which mounts a remote file system at boot and starts an application from it. I found that randomly the boot fails because the mount fails due to Network unreachable errors. I made sure the mount unit waits for network-online.target to be rached, however I found that NetworkManager-wait-online.service returns well before the IP address has been obtained by DHCP. This is a cleaned up log extract: apr 19 02:22:13 terminale2 systemd[1]: Starting Network. apr 19 02:22:13 terminale2 NetworkManager[660]: info (eth2): carrier is OFF apr 19 02:22:13 terminale2 NetworkManager[660]: info (eth2): new Ethernet device (driver: 'r8169' ifindex: 2) apr 19 02:22:13 terminale2 NetworkManager[660]: info (eth2): exported as /org/freedesktop/NetworkManager/Devices/1 apr 19 02:22:13 terminale2 NetworkManager[660]: info (eth2): device state change: unmanaged - unavailable (reason 'managed') [10 20 2] apr 19 02:22:13 terminale2 systemd[1]: Starting Network Manager Wait Online... apr 19 02:22:13 terminale2 NetworkManager[660]: info (eth2): preparing device apr 19 02:22:18 terminale2 NetworkManager[660]: info startup complete apr 19 02:22:18 terminale2 systemd[1]: Started Network Manager Wait Online. apr 19 02:22:18 terminale2 systemd[1]: Reached target Network is Online. apr 19 02:22:18 terminale2 systemd[1]: Starting Network is Online. apr 19 02:22:18 terminale2 systemd[1]: Mounting /nas... apr 19 02:22:18 terminale2 mount[810]: mount error(101): Network is unreachable Then after a while: apr 19 02:22:26 terminale2 NetworkManager[660]: info Activation (eth2) successful, device activated. Attached you find the whole journal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1445846/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1445852] [NEW] package gconf2 3.2.6-0ubuntu2 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1
Public bug reported: sucedio despues de una actualizacion ProblemType: Package DistroRelease: Ubuntu 14.04 Package: gconf2 3.2.6-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16 Uname: Linux 3.13.0-48-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 Date: Sun Apr 12 21:46:07 2015 DuplicateSignature: package:gconf2:3.2.6-0ubuntu2:el subproceso instalado el script post-installation devolvió el código de salida de error 1 ErrorMessage: el subproceso instalado el script post-installation devolvió el código de salida de error 1 InstallationDate: Installed on 2013-09-24 (571 days ago) InstallationMedia: Ubuntu 12.04.3 LTS Precise Pangolin - Release amd64 (20130820.1) SourcePackage: gconf Title: package gconf2 3.2.6-0ubuntu2 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1 UpgradeStatus: Upgraded to trusty on 2014-04-18 (365 days ago) ** Affects: gconf (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package third-party-packages trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1445852 Title: package gconf2 3.2.6-0ubuntu2 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1 Status in gconf package in Ubuntu: New Bug description: sucedio despues de una actualizacion ProblemType: Package DistroRelease: Ubuntu 14.04 Package: gconf2 3.2.6-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16 Uname: Linux 3.13.0-48-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 Date: Sun Apr 12 21:46:07 2015 DuplicateSignature: package:gconf2:3.2.6-0ubuntu2:el subproceso instalado el script post-installation devolvió el código de salida de error 1 ErrorMessage: el subproceso instalado el script post-installation devolvió el código de salida de error 1 InstallationDate: Installed on 2013-09-24 (571 days ago) InstallationMedia: Ubuntu 12.04.3 LTS Precise Pangolin - Release amd64 (20130820.1) SourcePackage: gconf Title: package gconf2 3.2.6-0ubuntu2 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1 UpgradeStatus: Upgraded to trusty on 2014-04-18 (365 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1445852/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1445852] Re: package gconf2 3.2.6-0ubuntu2 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1445852 Title: package gconf2 3.2.6-0ubuntu2 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1 Status in gconf package in Ubuntu: New Bug description: sucedio despues de una actualizacion ProblemType: Package DistroRelease: Ubuntu 14.04 Package: gconf2 3.2.6-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16 Uname: Linux 3.13.0-48-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 Date: Sun Apr 12 21:46:07 2015 DuplicateSignature: package:gconf2:3.2.6-0ubuntu2:el subproceso instalado el script post-installation devolvió el código de salida de error 1 ErrorMessage: el subproceso instalado el script post-installation devolvió el código de salida de error 1 InstallationDate: Installed on 2013-09-24 (571 days ago) InstallationMedia: Ubuntu 12.04.3 LTS Precise Pangolin - Release amd64 (20130820.1) SourcePackage: gconf Title: package gconf2 3.2.6-0ubuntu2 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1 UpgradeStatus: Upgraded to trusty on 2014-04-18 (365 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1445852/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1444166] Re: closing lid does not suspend in the first 3 minutes after boot
This bug was fixed in the package systemd - 219-7ubuntu3 --- systemd (219-7ubuntu3) vivid; urgency=medium * logind autopkgtest: Add test for suspending on lid switch close. This reproduces LP #1444166 (lid switch not working in the first few minutes after boot). * Reduce the initial suspend supression time from 3 minutes to 30 seconds, and make it configurable. (LP: #1444166) -- Martin Pitt martin.p...@ubuntu.com Sat, 18 Apr 2015 17:06:08 +0100 ** Changed in: systemd (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1444166 Title: closing lid does not suspend in the first 3 minutes after boot Status in systemd package in Ubuntu: Fix Released Bug description: Right after booting, closing the lid does not cause a suspend. logind does see the lid close/open event, but there is no suspend. After some minutes this starts working, and from then on always works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1444166/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
