[Touch-packages] [Bug 1424538] Re: python2.7-doc should depend on or recommend libjs-underscore
This bug was fixed in the package python2.7 - 2.7.9-2ubuntu1 --- python2.7 (2.7.9-2ubuntu1) vivid; urgency=medium * Update to 20150309, taken from the 2.7 release branch. - Issue #22853: Fixed a deadlock when use multiprocessing.Queue at import time. - Issue #23476: In the ssl module, enable OpenSSL's X509_V_FLAG_TRUSTED_FIRST flag on certificate stores when it is available. - Issue #23576: Avoid stalling in SSL reads when EOF has been reached in the SSL layer but the underlying connection hasn't been closed. - Issue #23504: Added an __all__ to the types module. - Issue #23367: Fix possible overflows in the unicodedata module. * debian/tests: Use init system agnostic "service" command instead of upstart specific "stop". Also drop unnecessary "status" call right after stopping apport. python2.7 (2.7.9-2) unstable; urgency=medium * python2.7-minimal: Make Pre-Depends mangling more robust. Closes: #779294. * python2.7-doc: Depend on libjs-underscore. LP: #1424538. * Remove LTO sections from the static libraries. Closes: #698395. -- Matthias KloseMon, 09 Mar 2015 23:53:51 +0100 ** Changed in: python2.7 (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1424538 Title: python2.7-doc should depend on or recommend libjs-underscore Status in python2.7 package in Ubuntu: Fix Released Bug description: Python's documentation search needs libjs-underscore to work. The dependency is there for python3.4-doc, but not 2.7. This is similar to bug #1001585 in which a symlink to underscore.js was missing. Now the symlink is there, but its target is not except by coincidence. At least 14.04 and 14.10 are affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1424538/+subscriptions -- Mailing list: https://launchpad.net/~touch-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] [NEW] Boot errors
Public bug reported: 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: dmi:bvnAmericanMegatrendsInc.:bvrV1.0:bd04/21/2014:svnMSI:pnMS-7921:pvr1.0:rvnMSI:rnZ97-G55SLI(MS-7921):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7921 dmi.product.version: 1.0 dmi.sys.vendor: MSI 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.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: Mon Mar 9 22:22:45 2015 x
[Touch-packages] [Bug 1302090] Re: Dell Alienware 14, Speaker sound output is mono until a headphone jack is plugged
https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/sound/pci/hda?id=73bdd597823e2231dc882577dbbaf8df92fe1775
for dell laptop with combo jack which use 0x1b for headset mic
which is similar to your configuration without headhone jack and mic
jack
+ [ALC668_FIXUP_DELL_MIC_NO_PRESENCE] = {
+ .type = HDA_FIXUP_PINS,
+ .v.pins = (const struct hda_pintbl[]) {
+ { 0x19, 0x03a1913d }, /* use as headphone mic, without
its own jack detect */
+ { 0x1b, 0x03a1113c }, /* use as headset mic, without
its own jack detect */
+ { }
+ },
+ .chained = true,
+ .chain_id = ALC668_FIXUP_HEADSET_MODE
+ },
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1302090
Title:
Dell Alienware 14, Speaker sound output is mono until a headphone jack
is plugged
Status in alsa-driver package in Ubuntu:
Confirmed
Bug description:
Here's the required release and package information:
Description:Ubuntu Trusty Tahr (development branch)
Release:14.04
Package: linux-image-extra-3.13.0-19-generic
Version: 3.13.0-19.40
When playing audio through speakers on my Alienware 14 2014, the sound
output is in mono until I plug a headphone in any of the two available
headphone jacks (obviously, the auto-mute option must be disabled).
When I do so, the sound starts to play in stereo.
I would love the sound output to be stereo by default and not be
forced to plug anything to achieve that.
Attached is the alsa-info.sh output for my machine.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1302090/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1382462] Re: 10de:0dfa Desktop/windows painted incorrectly in dual monitor configuration
It is worth to mention that, with the noveau drivers that come with ubuntu, I didn't have to do any of this. It works out-of-the box (but, with a bad performance - that's why I needed the nvidia drivers). -- 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/1382462 Title: 10de:0dfa Desktop/windows painted incorrectly in dual monitor configuration Status in xorg package in Ubuntu: Incomplete Bug description: My setup: Dell M4600 laptop with Dell U3011 2560x1600 monitor attached to DisplayPort. I was using Nvidia 331.38 prioprietary driver for quite a long time with Ubuntu 14.04 LTS and everything worked perfectly. Today I upgraded to Ubuntu 14.10, which comes with Nvidia 331.89 and observed the following problem: 1. When I boot up the computer with the monitor connected, the login screen looks fine. Both displays get detected properly and resolutions are ok (1920x1080 on the builtin laptop display and 2560x1600 on U3011) and screen contents scaled properly. 2. Then I log into my account, for 3 seconds U3011 displays some rubbish (but it was always like that) and when it finally logs in, it displays everything stretched horizontally through both my screens. It looks as if it tried to paint the contents of a single display on two of them, by stretching the content horizontally, so everything (icons, windows, wallpaper) has wrong aspect-ratio. Funny, the top status bar seem to render correctly and the resolution/size of the top menu is correct. Physical resolution of both screens is ok. I'll attach a photo, because it is hard to describe how it looks. 3. I cannot use system in this state - mouse click position seems to not be synchronized with what's on the display - e.g. I can start applications, but then they don't react to mouseclicks. However: booting up without the second display connected, logging in and *then* connecting the second display works fine. If I boot up with connected monitor and log in (desktop distorted), disconnecting and connecting monitor does *not* help. After disconnecting the U3011, the builtin display is painted ok, but after connecting, it returns back to the incorrect state and both are rendered incorrectly. The only thing that helps recovering from this state seems to be disconnecting the second monitor, reboot, logging in and then connecting. Suspending to memory and waking up does not change the layout of the screen (neither fixes the "broken" one nor destroys the "good" one). Using a Guest session instead of my account does not fix my problem (I was hoping this was something screwed up in my .config). Switching to a Guest user account while I'm using both monitors in the good layout creates a session with a broken layout. Then logging out from Guest and switching back to my original session restores the good layout. The good layout seems to not be forgotten until I finish the session and logout. The bad layout is "created" whenever I start a new session with both monitors plugged in. BTW: I'm using a docking station - not sure if it is related - if you think it might be, I can try with connecting the monitor directly. I tried deleting ~/.compiz and ~/.config/compiz-1 directories but the problem remains. I also tried to go into the Displays configuration when everything is ok, apply the settings there (without any changes) in hope it will persist them somehow, but after restart it is broken again. I also tried reinstalling nvidia 331.89 drivers, because it complained about not being able to install nvidia-uvm during the upgrade process (reported separately), and now all nvidia packages installed cleanly. Before that I also got rid of all the ppa mainline kernels I had, just in case they mess something up. I remember the same problem happened on Ubuntu 14.04 when I tried to upgrade nvidia from ppa/xorg-edgers to 331.89, but then the easy workaround was to downgrade back to official 331.38. Now I have no choice :( Some other observations that may or may not be related to the problem, but I disclose them anyway, maybe they are helpful: * Notifications (e.g. network connection) displayed on the login screen in dual screen mode seem to be misplaced and instead of being painted in the upper right corner of one of the displays they get painted in some hard to logically explain position - neither at the center, nor in any corner. * The splash screen of IntelliJ IDEA (this is using Java / AWT probably) is also rendered in a strange position - below the center of the laptop screen, moved to the right (but not touching the edge), instead of exact center as it should be. * GMail notification just displayed at the moment when I'm writing it exactly at the left-lower corner of the bigger screen (U3011). * Nvidia settings
[Touch-packages] [Bug 1382462] Re: 10de:0dfa Desktop/windows painted incorrectly in dual monitor configuration
After days lost with replacing NVidia drivers and manually editing xorg.conf file, I finally found this! Rockwalrus (rockwalrus) solution works! On CompizConfig Settings Manager, go to "General Options", then "Display Settings" and do the following: - Uncheck "Deteck Outputs" - In the Outputs array, set the resolutions of each of your screens. The numbers after the resolution "1920x1080+0+0" are the offset. It's important to add this offset according to your needs. I have two full HD screens, so I added the following configuration: 1920x1080+0+0 1920x1080+1920+0 The second output has an offset of 1920, because it is on the right side of the first output, which has a width of 1920. I was hopeless already, what a relief! -- 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/1382462 Title: 10de:0dfa Desktop/windows painted incorrectly in dual monitor configuration Status in xorg package in Ubuntu: Incomplete Bug description: My setup: Dell M4600 laptop with Dell U3011 2560x1600 monitor attached to DisplayPort. I was using Nvidia 331.38 prioprietary driver for quite a long time with Ubuntu 14.04 LTS and everything worked perfectly. Today I upgraded to Ubuntu 14.10, which comes with Nvidia 331.89 and observed the following problem: 1. When I boot up the computer with the monitor connected, the login screen looks fine. Both displays get detected properly and resolutions are ok (1920x1080 on the builtin laptop display and 2560x1600 on U3011) and screen contents scaled properly. 2. Then I log into my account, for 3 seconds U3011 displays some rubbish (but it was always like that) and when it finally logs in, it displays everything stretched horizontally through both my screens. It looks as if it tried to paint the contents of a single display on two of them, by stretching the content horizontally, so everything (icons, windows, wallpaper) has wrong aspect-ratio. Funny, the top status bar seem to render correctly and the resolution/size of the top menu is correct. Physical resolution of both screens is ok. I'll attach a photo, because it is hard to describe how it looks. 3. I cannot use system in this state - mouse click position seems to not be synchronized with what's on the display - e.g. I can start applications, but then they don't react to mouseclicks. However: booting up without the second display connected, logging in and *then* connecting the second display works fine. If I boot up with connected monitor and log in (desktop distorted), disconnecting and connecting monitor does *not* help. After disconnecting the U3011, the builtin display is painted ok, but after connecting, it returns back to the incorrect state and both are rendered incorrectly. The only thing that helps recovering from this state seems to be disconnecting the second monitor, reboot, logging in and then connecting. Suspending to memory and waking up does not change the layout of the screen (neither fixes the "broken" one nor destroys the "good" one). Using a Guest session instead of my account does not fix my problem (I was hoping this was something screwed up in my .config). Switching to a Guest user account while I'm using both monitors in the good layout creates a session with a broken layout. Then logging out from Guest and switching back to my original session restores the good layout. The good layout seems to not be forgotten until I finish the session and logout. The bad layout is "created" whenever I start a new session with both monitors plugged in. BTW: I'm using a docking station - not sure if it is related - if you think it might be, I can try with connecting the monitor directly. I tried deleting ~/.compiz and ~/.config/compiz-1 directories but the problem remains. I also tried to go into the Displays configuration when everything is ok, apply the settings there (without any changes) in hope it will persist them somehow, but after restart it is broken again. I also tried reinstalling nvidia 331.89 drivers, because it complained about not being able to install nvidia-uvm during the upgrade process (reported separately), and now all nvidia packages installed cleanly. Before that I also got rid of all the ppa mainline kernels I had, just in case they mess something up. I remember the same problem happened on Ubuntu 14.04 when I tried to upgrade nvidia from ppa/xorg-edgers to 331.89, but then the easy workaround was to downgrade back to official 331.38. Now I have no choice :( Some other observations that may or may not be related to the problem, but I disclose them anyway, maybe they are helpful: * Notifications (e.g. network connection) displayed on the login screen in dual screen mode seem to be misplaced and instead of being painted in the upper right corner of one of
[Touch-packages] [Bug 1302090] Re: Dell Alienware 14, Speaker sound output is mono until a headphone jack is plugged
how did you set the pin default of subwoofer ? Pin Default 0x90170111: [Fixed] Speaker at Int N/A Conn = Analog, Color = Unknown DefAssociation = 0x1, Sequence = 0x1 Misc = NO_PRESENCE subwoofer may use same DAC if there is low pass filter, did your hear sound from speaker and subwoofet ? spk_outs = 14/18/0/0 : 4/4/0/0 spk path: depth=3 '04:0e:14' spk path: depth=3 '04:0e:18' you need four channels and software low pass filter only when there is no hardware low pass filter multi_outs = 14/18/0/0 : 2/3/0/0 (type SP) out path: depth=3 '02:0c:14' out path: depth=3 '03:0d:18' -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1302090 Title: Dell Alienware 14, Speaker sound output is mono until a headphone jack is plugged Status in alsa-driver package in Ubuntu: Confirmed Bug description: Here's the required release and package information: Description:Ubuntu Trusty Tahr (development branch) Release:14.04 Package: linux-image-extra-3.13.0-19-generic Version: 3.13.0-19.40 When playing audio through speakers on my Alienware 14 2014, the sound output is in mono until I plug a headphone in any of the two available headphone jacks (obviously, the auto-mute option must be disabled). When I do so, the sound starts to play in stereo. I would love the sound output to be stereo by default and not be forced to plug anything to achieve that. Attached is the alsa-info.sh output for my machine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1302090/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1426942] Re: Kubuntu Vivid - unable to display Gujarati Text
** Branch linked: lp:~kubuntu-packagers/kubuntu-packaging/qtbase- opensource-src -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1426942 Title: Kubuntu Vivid - unable to display Gujarati Text Status in qtbase-opensource-src package in Ubuntu: Triaged Bug description: Applications built with qt5/KDE Framework 5 on Kubuntu Vivid Beta 1 can no longer render Gujarati script. This is probably due to https://bugreports.qt.io/browse/QTBUG-44568 My Platform: Kubuntu Vivid Beta 1 Packages affected: Any package built with Qt5 5.4 (e.g. konsole, Muon Package Manager etc) Expected: Render Gujarati script correctly (as was the case in Kubuntu versions prior to 15.04) Actual Results: Gujarati glyphs are displayed as squares The above Qt bug is scheduled to be fixed in Qt 5.5. If Kubuntu Vivid is going to ship with Qt 5.4, will it be possible to include a patched Qt5.4 to resolve this specific bug? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1426942/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1429098] Re: systemd[1]: ureadahead.service failed.
OK, no *.pack files then, so the problem is on the initial data collection. Can you please run sudo ureadahead --verbose >/tmp/output 2>&1 in a terminal, then do some file system activity (e. g. cat /bin/bash >/dev/null), then press Control-C, let it finish, and attach /tmp/output? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ureadahead in Ubuntu. https://bugs.launchpad.net/bugs/1429098 Title: systemd[1]: ureadahead.service failed. Status in NULL Project: Invalid Status in ureadahead package in Ubuntu: Incomplete Bug description: dmesg: [4.717252] systemd[1]: ureadahead.service failed. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-4ubuntu3 Uname: Linux 4.0.0-04rc2-generic x86_64 ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 6 08:55:40 2015 InstallationDate: Installed on 2014-09-25 (162 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140923) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.0.0-04rc2-generic root=UUID=0fb75fae-baa3-428b-ace4-498e69ff7fb6 ro rootflags=subvol=@ quiet splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=7 init=/lib/systemd/systemd SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/null-and-void/+bug/1429098/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1429975] Re: nfs no longer mounted at boot with systemd
Indeed, these should have a Wants=/After=network-online.target. ** Tags added: systemd-boot ** Changed in: systemd (Ubuntu) Importance: Undecided => High ** Changed in: systemd (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1429975 Title: nfs no longer mounted at boot with systemd Status in systemd package in Ubuntu: In Progress Bug description: I updated my vivid laptop today, and now boot with systemd by default. Unfortunately, my nfs mount no longer mounts at boot. From syslog: Mar 9 14:38:20 mdlinux mount[866]: mount.nfs: Network is unreachable Mar 9 14:38:20 mdlinux systemd[1]: mnt-server.mount mount process exited, code=exited status=32 Mar 9 14:38:20 mdlinux systemd[1]: Failed to mount /mnt/server. Mar 9 14:38:20 mdlinux systemd[1]: Dependency failed for Remote File Systems. Mar 9 14:38:20 mdlinux systemd[1]: Job remote-fs.target/start failed with result 'dependency'. Mar 9 14:38:20 mdlinux systemd[1]: Unit mnt-server.mount entered failed state. This is happening before my network interfaces are ready: Mar 9 14:38:21 mdlinux NetworkManager[820]: (eth0): preparing device ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: nfs-common 1:1.2.8-9ubuntu6 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportVersion: 2.16.2-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 9 14:45:48 2015 InstallationDate: Installed on 2013-11-26 (467 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: nfs-utils UpgradeStatus: Upgraded to vivid on 2015-03-07 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1429975/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1429938] Re: systemd changes behavior of apt-get remove openssh-server
** Changed in: systemd (Ubuntu) Status: Confirmed => Invalid ** Changed in: openssh (Ubuntu) Status: Confirmed => In Progress ** Changed in: openssh (Ubuntu) Assignee: (unassigned) => Martin Pitt (pitti) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1429938 Title: systemd changes behavior of apt-get remove openssh-server Status in openssh package in Ubuntu: In Progress Status in systemd package in Ubuntu: Invalid Bug description: On Trusty and Utopic, when you run `apt-get remove openssh-server` over an SSH connection, your existing SSH connection remains open, so it's possible to run additional commands afterward. However, on Vivid now that the switch to systemd has been made, `apt- get remove openssh-server` closes the existing SSH connection immediately, causing your SSH client to exit with a non-zero status. I have a hunch there's a lot of automation tooling out there that relies on the old behavior. For what it's worth, this change breaks the internal image mastering tools that System76 uses. Prior to exporting an image tarball, I spin up a golden VM with qemu, rysnc a script to it, and then execute this script over SSH. The important step is that I need to remove openssh-server prior to shutting down the VM, so these scripts always end with something like this: apt-get -y purge openssh-server ssh-import-id apt-get -y autoremove shutdown -h now As far as I can tell, this behavior change will likewise be a problem when running `do-release-upgrade` on a remote server over SSH. Or more generally, anytime you run "apt-get upgrade/dist-upgrade" via SSH, it seems this would be a problem whenever the openssh-server package happens to be updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1429938/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371378] Re: Session locking doesn't work if the session was unlocked after changing VT
This bug was fixed in the package lightdm - 1.13.2-0ubuntu1
---
lightdm (1.13.2-0ubuntu1) vivid; urgency=medium
* New upstream release:
- Fix pipe file descriptor leak for each greeter session. (LP: #1190344)
- Support active session changing via logind. (LP: #1371378)
- Don't allow liblightdm-gobject to be disabled. It is required for
liblightdm-qt and the tests so it's not worth supporting builds without
it.
- Add bash autocompletion support
* debian/lightdm.install:
- Install autocompletion configuration
-- Robert AncellTue, 10 Mar 2015 14:54:29
+1300
** Changed in: lightdm (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1371378
Title:
Session locking doesn't work if the session was unlocked after
changing VT
Status in Light Display Manager:
Fix Released
Status in Light Display Manager 1.10 series:
Triaged
Status in lightdm package in Ubuntu:
Fix Released
Bug description:
Test machine: Ubuntu 14.04 with lightdm-1.10.1-0ubuntu1 and lightdm
trunk revision 2064
Reproducing the bug:
1. Log into an user session using Unity, Gnome 3 or Cairo-Dock session.
2. If using a Gnome 3 session, trigger the screensaver by executing
"xdg-screensaver lock", and then unlock it by entering the user password (this
is needed to avoid bug #1371374).
3. Lock the session executing "dm-tool lock" in a terminal.
4. A new greeter is displayed.
5. Switch to the user session by switching VT (e.g. Alt+Ctrl-F7).
6. The user session is locked by the screensaver (which under a Unity session
just looks like the greeter), prompting for the user password.
7. Unlock the screensaver by introducing the user password.
8. Lock the session again ("dm-tool lock").
9. The greeter is shown again.
10. Switch to the user session by switching VT (e.g. Alt+Ctrl-F7).
11. The session isn't locked at all.
Causes:
Lightdm is not aware of VT changes, therefore when the session is
unlocked by using the screensaver in the user session's VT instead of
the greeter, lightdm is thinking that the active session is still the
greeter session.
When locking the session afterwards, in the function
seat_set_active_session() the session to be activated (the greeter) is
compared to the session that light thinks that is active, which it
thinks is the greeter because it was the last session activated by
lightdm, and therefore locking is not performed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1371378/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1190344] Re: Daemon end of session/greeter pipes not closed
This bug was fixed in the package lightdm - 1.13.2-0ubuntu1
---
lightdm (1.13.2-0ubuntu1) vivid; urgency=medium
* New upstream release:
- Fix pipe file descriptor leak for each greeter session. (LP: #1190344)
- Support active session changing via logind. (LP: #1371378)
- Don't allow liblightdm-gobject to be disabled. It is required for
liblightdm-qt and the tests so it's not worth supporting builds without
it.
- Add bash autocompletion support
* debian/lightdm.install:
- Install autocompletion configuration
-- Robert AncellTue, 10 Mar 2015 14:54:29
+1300
** Changed in: lightdm (Ubuntu Vivid)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1190344
Title:
Daemon end of session/greeter pipes not closed
Status in Light Display Manager:
Fix Released
Status in Light Display Manager 1.10 series:
Fix Released
Status in Light Display Manager 1.12 series:
Fix Released
Status in Light Display Manager 1.2 series:
Fix Released
Status in lightdm package in Ubuntu:
Fix Released
Status in lightdm source package in Precise:
Triaged
Status in lightdm source package in Trusty:
Triaged
Status in lightdm source package in Utopic:
Triaged
Status in lightdm source package in Vivid:
Fix Released
Status in Fedora:
Unknown
Bug description:
[Impact]
LightDM doesn't close the server side end of the pipes used to communicate
with session processes and greeters. This means each session/greeter that is
created leaks two file descriptors eventually leading to the system stopping it
from creating new pipes.
[Test Case]
1. Start LightDM
2. Check how many pipes are open
# lsof -p {lightdm_pid} | grep FIFO | wc -l
3. Create sessions by either cycling between users in Unity Greeter or
logging in and out
4. Check how many pipes exist using step 2.
Expected result:
No more pipes should be open
Observed result:
Many pipes remain open
[Regression Potential]
Low. Fix is to close pipes when finished with them. Tested with regression
tests.
To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1190344/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1402005] Re: agent-state-info: 'error executing "lxc-start": command get_cgroup failed to receive response'
[Expired for lxc (Ubuntu) because there has been no activity for 60 days.] ** Changed in: lxc (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1402005 Title: agent-state-info: 'error executing "lxc-start": command get_cgroup failed to receive response' Status in juju-core: Invalid Status in lxc package in Ubuntu: Expired Bug description: We are seeing a few deploys in our automated charm testing fail due to not being able to execute lxc-start. The error we are seeing is: "1": agent-state-info: 'error executing "lxc-start": command get_cgroup failed to receive response' instance-id: pending series: precise ref: http://reports.vapour.ws/charm-tests/charm-bundle-test-10698-results/charm/charm-testing-lxc/2 Tim V. has done some initial research on it: https://github.com/lxc/lxc/issues/189 which lead to https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1296459 The fix there was to have 2.8.95~2430-0ubuntu3 installed. Our charm testing infrastructure is running 2.8.95~2430-0ubuntu5. Any help on determining why lxc-start is failing here would be much appreciated. -thanks, Antonio To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1402005/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1379936] Re: ubuntu 14-04 laptop black screen after suspend
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- 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/1379936 Title: ubuntu 14-04 laptop black screen after suspend Status in xorg package in Ubuntu: Expired Bug description: Laptop is set to suspend when the lid is closed. System will not display desktop after reopening the lid. Sometimes you can get the desktop back by using CTRL/ALT F1 and then CTRL/ALT F7, but only if the cusor is still displayed with the black screen. The system will usually return the desktop if SUDO PM-RESUME is typed into the terminal screen, but occasionally that will fail as well when the laptop lid is opened. Then it's reboot time. Laptop is a HP Pavillion dv6245us with Intel chip set, including internal graphics 943/940GML Express Integrated Graphics Controller (rev 03). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: i386 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,commands,move,gnomecompat,regex,mousepoll,imgpng,grid,snap,unitymtgrabhandles,vpswitch,place,resize,animation,workarounds,session,expo,fade,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Oct 10 15:49:26 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:30bb] Subsystem: Hewlett-Packard Company Device [103c:30bb] MachineType: Hewlett-Packard HP Pavilion dv6000 (RP285UA#ABA) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic root=UUID=2b463542-af2a-4618-bfd2-2122953c571b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2006 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.10 dmi.board.name: 30BB dmi.board.vendor: Quanta dmi.board.version: 66.34 dmi.chassis.type: 10 dmi.chassis.vendor: Quanta dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.10:bd12/02/2006:svnHewlett-Packard:pnHPPaviliondv6000(RP285UA#ABA):pvrRev1:rvnQuanta:rn30BB:rvr66.34:cvnQuanta:ct10:cvrN/A: dmi.product.name: HP Pavilion dv6000 (RP285UA#ABA) dmi.product.version: Rev 1 dmi.sys.vendor: Hewlett-Packard 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 Oct 9 16:41:43 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 10752 vendor LPL xserver.version: 2:1.15.1-0ubuntu2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1379936/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1407019] Re: bugs
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- 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/1407019 Title: bugs Status in xorg package in Ubuntu: Expired Bug description: I did a test ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.6 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: Thu Jan 1 21:46:44 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV610 [Radeon HD 2400 PRO/XT] [1002:94c1] (prog-if 00 [VGA controller]) Subsystem: Dell Optiplex 755 [1028:0d02] InstallationDate: Installed on 2014-10-07 (86 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) MachineType: Dell Inc. OptiPlex 755 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-37-generic root=/dev/mapper/ubuntu--vg-root ro splash quiet SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/06/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A20 dmi.board.name: 0GM819 dmi.board.vendor: Dell Inc. dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA20:bd10/06/2011:svnDellInc.:pnOptiPlex755:pvr:rvnDellInc.:rn0GM819:rvr:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 755 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.3+14.04.20141104-0ubuntu1 version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.5 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.3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sun Dec 21 01:56:51 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2.5 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1407019/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1328259] Re: package avahi-daemon 0.6.31-4ubuntu1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: avahi (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1328259 Title: package avahi-daemon 0.6.31-4ubuntu1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 Status in avahi package in Ubuntu: Confirmed Bug description: upgraded my ubuntu server from 12.04 to 14.04 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: avahi-daemon 0.6.31-4ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-60.91-generic 3.2.55 Uname: Linux 3.2.0-60-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 Date: Mon Jun 9 16:34:02 2014 DuplicateSignature: package:avahi-daemon:0.6.31-4ubuntu1:ErrorMessage: subprocess installed post-installation script returned error exit status 1 ErrorMessage: ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2012-05-03 (767 days ago) InstallationMedia: Ubuntu-Server 12.04 LTS "Precise Pangolin" - Release amd64 (20120424.1) SourcePackage: avahi Title: package avahi-daemon 0.6.31-4ubuntu1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to trusty on 2014-06-09 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1328259/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1190344] Re: Daemon end of session/greeter pipes not closed
** Changed in: lightdm/1.2
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1190344
Title:
Daemon end of session/greeter pipes not closed
Status in Light Display Manager:
Fix Released
Status in Light Display Manager 1.10 series:
Fix Released
Status in Light Display Manager 1.12 series:
Fix Released
Status in Light Display Manager 1.2 series:
Fix Released
Status in lightdm package in Ubuntu:
Triaged
Status in lightdm source package in Precise:
Triaged
Status in lightdm source package in Trusty:
Triaged
Status in lightdm source package in Utopic:
Triaged
Status in lightdm source package in Vivid:
Triaged
Status in Fedora:
Unknown
Bug description:
[Impact]
LightDM doesn't close the server side end of the pipes used to communicate
with session processes and greeters. This means each session/greeter that is
created leaks two file descriptors eventually leading to the system stopping it
from creating new pipes.
[Test Case]
1. Start LightDM
2. Check how many pipes are open
# lsof -p {lightdm_pid} | grep FIFO | wc -l
3. Create sessions by either cycling between users in Unity Greeter or
logging in and out
4. Check how many pipes exist using step 2.
Expected result:
No more pipes should be open
Observed result:
Many pipes remain open
[Regression Potential]
Low. Fix is to close pipes when finished with them. Tested with regression
tests.
To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1190344/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1390808] Re: VNC / XDMCP server cannot be configured to listen on specific interfaces
** Changed in: lightdm/1.2 Milestone: 1.2.10 => 1.2.11 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1390808 Title: VNC / XDMCP server cannot be configured to listen on specific interfaces Status in Light Display Manager: Triaged Status in Light Display Manager 1.10 series: Triaged Status in Light Display Manager 1.12 series: Triaged Status in Light Display Manager 1.2 series: Triaged Status in lightdm package in Ubuntu: Triaged Status in lightdm source package in Precise: Triaged Status in lightdm source package in Trusty: Triaged Status in lightdm source package in Utopic: Triaged Status in lightdm source package in Vivid: Triaged Bug description: [Impact] The XDMCP and VNC servers in LightDM allow connections on any network interface. It is desirable for these to be limited to a particular interface to limit who can connect (i.e. only allow local connections on 127.0.0.1). [Test Case] 1. Enable the VNC server in LightDM in lightdm.conf: [VNCServer] enabled=true listen-address=127.0.0.1 2. Start LightDM With this setup you should only be able to make a local connection. [Regression potential] Low. If the option is not set LightDM has the old behaviour. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1390808/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1190344] Re: Daemon end of session/greeter pipes not closed
** Changed in: lightdm/1.10
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1190344
Title:
Daemon end of session/greeter pipes not closed
Status in Light Display Manager:
Fix Released
Status in Light Display Manager 1.10 series:
Fix Released
Status in Light Display Manager 1.12 series:
Fix Released
Status in Light Display Manager 1.2 series:
Fix Released
Status in lightdm package in Ubuntu:
Triaged
Status in lightdm source package in Precise:
Triaged
Status in lightdm source package in Trusty:
Triaged
Status in lightdm source package in Utopic:
Triaged
Status in lightdm source package in Vivid:
Triaged
Status in Fedora:
Unknown
Bug description:
[Impact]
LightDM doesn't close the server side end of the pipes used to communicate
with session processes and greeters. This means each session/greeter that is
created leaks two file descriptors eventually leading to the system stopping it
from creating new pipes.
[Test Case]
1. Start LightDM
2. Check how many pipes are open
# lsof -p {lightdm_pid} | grep FIFO | wc -l
3. Create sessions by either cycling between users in Unity Greeter or
logging in and out
4. Check how many pipes exist using step 2.
Expected result:
No more pipes should be open
Observed result:
Many pipes remain open
[Regression Potential]
Low. Fix is to close pipes when finished with them. Tested with regression
tests.
To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1190344/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1236749] Re: Gnome shell extensions disabled at every startup
** Branch linked: lp:~darkxst/gnome-session/fix-fail-whale -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1236749 Title: Gnome shell extensions disabled at every startup Status in Ubuntu GNOME: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in upstart package in Ubuntu: Confirmed Bug description: Since gnome-shell 3.10, my extensions are disabled by default at every boot. I need to launch Tweak Tool to enable theme by hand every time. Both pre-installed extensions ( AlternateTab) and user-installed ones (top-icons) Step to reproduce : Enable an extension in Tweak Tool ( Alternate Tab for example) reboot computer, open Tweak Tool : Alternate tab is disabled. Running on Ubuntu 13.10 GNOME Shell 3.10.0.1 gnome-tweak-tool 3.10..0-0ubuntu1-saucy1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1236749/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1390808] Re: VNC / XDMCP server cannot be configured to listen on specific interfaces
** Changed in: lightdm/1.10 Milestone: 1.10.5 => 1.10.6 ** Changed in: lightdm Status: In Progress => Triaged ** Changed in: lightdm/1.10 Status: In Progress => Triaged ** Changed in: lightdm/1.12 Status: In Progress => Triaged ** Changed in: lightdm/1.2 Status: In Progress => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1390808 Title: VNC / XDMCP server cannot be configured to listen on specific interfaces Status in Light Display Manager: Triaged Status in Light Display Manager 1.10 series: Triaged Status in Light Display Manager 1.12 series: Triaged Status in Light Display Manager 1.2 series: Triaged Status in lightdm package in Ubuntu: Triaged Status in lightdm source package in Precise: Triaged Status in lightdm source package in Trusty: Triaged Status in lightdm source package in Utopic: Triaged Status in lightdm source package in Vivid: Triaged Bug description: [Impact] The XDMCP and VNC servers in LightDM allow connections on any network interface. It is desirable for these to be limited to a particular interface to limit who can connect (i.e. only allow local connections on 127.0.0.1). [Test Case] 1. Enable the VNC server in LightDM in lightdm.conf: [VNCServer] enabled=true listen-address=127.0.0.1 2. Start LightDM With this setup you should only be able to make a local connection. [Regression potential] Low. If the option is not set LightDM has the old behaviour. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1390808/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1190344] Re: Daemon end of session/greeter pipes not closed
** Changed in: lightdm/1.12
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1190344
Title:
Daemon end of session/greeter pipes not closed
Status in Light Display Manager:
Fix Released
Status in Light Display Manager 1.10 series:
Fix Committed
Status in Light Display Manager 1.12 series:
Fix Released
Status in Light Display Manager 1.2 series:
Fix Committed
Status in lightdm package in Ubuntu:
Triaged
Status in lightdm source package in Precise:
Triaged
Status in lightdm source package in Trusty:
Triaged
Status in lightdm source package in Utopic:
Triaged
Status in lightdm source package in Vivid:
Triaged
Status in Fedora:
Unknown
Bug description:
[Impact]
LightDM doesn't close the server side end of the pipes used to communicate
with session processes and greeters. This means each session/greeter that is
created leaks two file descriptors eventually leading to the system stopping it
from creating new pipes.
[Test Case]
1. Start LightDM
2. Check how many pipes are open
# lsof -p {lightdm_pid} | grep FIFO | wc -l
3. Create sessions by either cycling between users in Unity Greeter or
logging in and out
4. Check how many pipes exist using step 2.
Expected result:
No more pipes should be open
Observed result:
Many pipes remain open
[Regression Potential]
Low. Fix is to close pipes when finished with them. Tested with regression
tests.
To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1190344/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1390808] Re: VNC / XDMCP server cannot be configured to listen on specific interfaces
** Changed in: lightdm/1.12 Milestone: 1.12.3 => 1.12.4 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1390808 Title: VNC / XDMCP server cannot be configured to listen on specific interfaces Status in Light Display Manager: In Progress Status in Light Display Manager 1.10 series: In Progress Status in Light Display Manager 1.12 series: In Progress Status in Light Display Manager 1.2 series: In Progress Status in lightdm package in Ubuntu: Triaged Status in lightdm source package in Precise: Triaged Status in lightdm source package in Trusty: Triaged Status in lightdm source package in Utopic: Triaged Status in lightdm source package in Vivid: Triaged Bug description: [Impact] The XDMCP and VNC servers in LightDM allow connections on any network interface. It is desirable for these to be limited to a particular interface to limit who can connect (i.e. only allow local connections on 127.0.0.1). [Test Case] 1. Enable the VNC server in LightDM in lightdm.conf: [VNCServer] enabled=true listen-address=127.0.0.1 2. Start LightDM With this setup you should only be able to make a local connection. [Regression potential] Low. If the option is not set LightDM has the old behaviour. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1390808/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1190344] Re: Daemon end of session/greeter pipes not closed
** Branch linked: lp:ubuntu/vivid-proposed/lightdm
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1190344
Title:
Daemon end of session/greeter pipes not closed
Status in Light Display Manager:
Fix Released
Status in Light Display Manager 1.10 series:
Fix Committed
Status in Light Display Manager 1.12 series:
Fix Released
Status in Light Display Manager 1.2 series:
Fix Committed
Status in lightdm package in Ubuntu:
Triaged
Status in lightdm source package in Precise:
Triaged
Status in lightdm source package in Trusty:
Triaged
Status in lightdm source package in Utopic:
Triaged
Status in lightdm source package in Vivid:
Triaged
Status in Fedora:
Unknown
Bug description:
[Impact]
LightDM doesn't close the server side end of the pipes used to communicate
with session processes and greeters. This means each session/greeter that is
created leaks two file descriptors eventually leading to the system stopping it
from creating new pipes.
[Test Case]
1. Start LightDM
2. Check how many pipes are open
# lsof -p {lightdm_pid} | grep FIFO | wc -l
3. Create sessions by either cycling between users in Unity Greeter or
logging in and out
4. Check how many pipes exist using step 2.
Expected result:
No more pipes should be open
Observed result:
Many pipes remain open
[Regression Potential]
Low. Fix is to close pipes when finished with them. Tested with regression
tests.
To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1190344/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371378] Re: Session locking doesn't work if the session was unlocked after changing VT
** Branch linked: lp:ubuntu/vivid-proposed/lightdm
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1371378
Title:
Session locking doesn't work if the session was unlocked after
changing VT
Status in Light Display Manager:
Fix Released
Status in Light Display Manager 1.10 series:
Triaged
Status in lightdm package in Ubuntu:
New
Bug description:
Test machine: Ubuntu 14.04 with lightdm-1.10.1-0ubuntu1 and lightdm
trunk revision 2064
Reproducing the bug:
1. Log into an user session using Unity, Gnome 3 or Cairo-Dock session.
2. If using a Gnome 3 session, trigger the screensaver by executing
"xdg-screensaver lock", and then unlock it by entering the user password (this
is needed to avoid bug #1371374).
3. Lock the session executing "dm-tool lock" in a terminal.
4. A new greeter is displayed.
5. Switch to the user session by switching VT (e.g. Alt+Ctrl-F7).
6. The user session is locked by the screensaver (which under a Unity session
just looks like the greeter), prompting for the user password.
7. Unlock the screensaver by introducing the user password.
8. Lock the session again ("dm-tool lock").
9. The greeter is shown again.
10. Switch to the user session by switching VT (e.g. Alt+Ctrl-F7).
11. The session isn't locked at all.
Causes:
Lightdm is not aware of VT changes, therefore when the session is
unlocked by using the screensaver in the user session's VT instead of
the greeter, lightdm is thinking that the active session is still the
greeter session.
When locking the session afterwards, in the function
seat_set_active_session() the session to be activated (the greeter) is
compared to the session that light thinks that is active, which it
thinks is the greeter because it was the last session activated by
lightdm, and therefore locking is not performed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1371378/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1390808] Re: VNC / XDMCP server cannot be configured to listen on specific interfaces
** Changed in: lightdm Milestone: 1.13.2 => 1.13.4 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1390808 Title: VNC / XDMCP server cannot be configured to listen on specific interfaces Status in Light Display Manager: In Progress Status in Light Display Manager 1.10 series: In Progress Status in Light Display Manager 1.12 series: In Progress Status in Light Display Manager 1.2 series: In Progress Status in lightdm package in Ubuntu: Triaged Status in lightdm source package in Precise: Triaged Status in lightdm source package in Trusty: Triaged Status in lightdm source package in Utopic: Triaged Status in lightdm source package in Vivid: Triaged Bug description: [Impact] The XDMCP and VNC servers in LightDM allow connections on any network interface. It is desirable for these to be limited to a particular interface to limit who can connect (i.e. only allow local connections on 127.0.0.1). [Test Case] 1. Enable the VNC server in LightDM in lightdm.conf: [VNCServer] enabled=true listen-address=127.0.0.1 2. Start LightDM With this setup you should only be able to make a local connection. [Regression potential] Low. If the option is not set LightDM has the old behaviour. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1390808/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371378] Re: Session locking doesn't work if the session was unlocked after changing VT
** Changed in: lightdm
Status: Fix Committed => Fix Released
** Changed in: lightdm (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1371378
Title:
Session locking doesn't work if the session was unlocked after
changing VT
Status in Light Display Manager:
Fix Released
Status in Light Display Manager 1.10 series:
Triaged
Status in lightdm package in Ubuntu:
New
Bug description:
Test machine: Ubuntu 14.04 with lightdm-1.10.1-0ubuntu1 and lightdm
trunk revision 2064
Reproducing the bug:
1. Log into an user session using Unity, Gnome 3 or Cairo-Dock session.
2. If using a Gnome 3 session, trigger the screensaver by executing
"xdg-screensaver lock", and then unlock it by entering the user password (this
is needed to avoid bug #1371374).
3. Lock the session executing "dm-tool lock" in a terminal.
4. A new greeter is displayed.
5. Switch to the user session by switching VT (e.g. Alt+Ctrl-F7).
6. The user session is locked by the screensaver (which under a Unity session
just looks like the greeter), prompting for the user password.
7. Unlock the screensaver by introducing the user password.
8. Lock the session again ("dm-tool lock").
9. The greeter is shown again.
10. Switch to the user session by switching VT (e.g. Alt+Ctrl-F7).
11. The session isn't locked at all.
Causes:
Lightdm is not aware of VT changes, therefore when the session is
unlocked by using the screensaver in the user session's VT instead of
the greeter, lightdm is thinking that the active session is still the
greeter session.
When locking the session afterwards, in the function
seat_set_active_session() the session to be activated (the greeter) is
compared to the session that light thinks that is active, which it
thinks is the greeter because it was the last session activated by
lightdm, and therefore locking is not performed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1371378/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1190344] Re: Daemon end of session/greeter pipes not closed
** Changed in: lightdm
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1190344
Title:
Daemon end of session/greeter pipes not closed
Status in Light Display Manager:
Fix Released
Status in Light Display Manager 1.10 series:
Fix Committed
Status in Light Display Manager 1.12 series:
Fix Committed
Status in Light Display Manager 1.2 series:
Fix Committed
Status in lightdm package in Ubuntu:
Triaged
Status in lightdm source package in Precise:
Triaged
Status in lightdm source package in Trusty:
Triaged
Status in lightdm source package in Utopic:
Triaged
Status in lightdm source package in Vivid:
Triaged
Status in Fedora:
Unknown
Bug description:
[Impact]
LightDM doesn't close the server side end of the pipes used to communicate
with session processes and greeters. This means each session/greeter that is
created leaks two file descriptors eventually leading to the system stopping it
from creating new pipes.
[Test Case]
1. Start LightDM
2. Check how many pipes are open
# lsof -p {lightdm_pid} | grep FIFO | wc -l
3. Create sessions by either cycling between users in Unity Greeter or
logging in and out
4. Check how many pipes exist using step 2.
Expected result:
No more pipes should be open
Observed result:
Many pipes remain open
[Regression Potential]
Low. Fix is to close pipes when finished with them. Tested with regression
tests.
To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1190344/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1430119] [NEW] package unattended-upgrades 0.82.1ubuntu2.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 255
Public bug reported: Nothing ProblemType: Package DistroRelease: Ubuntu 14.04 Package: unattended-upgrades 0.82.1ubuntu2.1 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.7 Architecture: i386 Date: Tue Mar 10 08:13:59 2015 DuplicateSignature: package:unattended-upgrades:0.82.1ubuntu2.1:subprocess installed post-installation script returned error exit status 255 ErrorMessage: subprocess installed post-installation script returned error exit status 255 InstallationDate: Installed on 2014-08-15 (206 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) PackageArchitecture: all SourcePackage: unattended-upgrades Title: package unattended-upgrades 0.82.1ubuntu2.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 255 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unattended-upgrades (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 unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1430119 Title: package unattended-upgrades 0.82.1ubuntu2.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 255 Status in unattended-upgrades package in Ubuntu: New Bug description: Nothing ProblemType: Package DistroRelease: Ubuntu 14.04 Package: unattended-upgrades 0.82.1ubuntu2.1 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.7 Architecture: i386 Date: Tue Mar 10 08:13:59 2015 DuplicateSignature: package:unattended-upgrades:0.82.1ubuntu2.1:subprocess installed post-installation script returned error exit status 255 ErrorMessage: subprocess installed post-installation script returned error exit status 255 InstallationDate: Installed on 2014-08-15 (206 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) PackageArchitecture: all SourcePackage: unattended-upgrades Title: package unattended-upgrades 0.82.1ubuntu2.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 255 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1430119/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1430119] Re: package unattended-upgrades 0.82.1ubuntu2.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 255
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1430119 Title: package unattended-upgrades 0.82.1ubuntu2.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 255 Status in unattended-upgrades package in Ubuntu: New Bug description: Nothing ProblemType: Package DistroRelease: Ubuntu 14.04 Package: unattended-upgrades 0.82.1ubuntu2.1 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.7 Architecture: i386 Date: Tue Mar 10 08:13:59 2015 DuplicateSignature: package:unattended-upgrades:0.82.1ubuntu2.1:subprocess installed post-installation script returned error exit status 255 ErrorMessage: subprocess installed post-installation script returned error exit status 255 InstallationDate: Installed on 2014-08-15 (206 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) PackageArchitecture: all SourcePackage: unattended-upgrades Title: package unattended-upgrades 0.82.1ubuntu2.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 255 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1430119/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1302090] Re: Dell Alienware 14, Speaker sound output is mono until a headphone jack is plugged
Raymond, I see that you perfectly manage the alsa driver/soup, I don't. Wouldn't it be simplier to tell me which setup do I have to configure in hdajackretask (or elsewhere) to make that crap cheap chip working properly ? And you could contact alsa to fix that stincky driver once for all. Whah you think about ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1302090 Title: Dell Alienware 14, Speaker sound output is mono until a headphone jack is plugged Status in alsa-driver package in Ubuntu: Confirmed Bug description: Here's the required release and package information: Description:Ubuntu Trusty Tahr (development branch) Release:14.04 Package: linux-image-extra-3.13.0-19-generic Version: 3.13.0-19.40 When playing audio through speakers on my Alienware 14 2014, the sound output is in mono until I plug a headphone in any of the two available headphone jacks (obviously, the auto-mute option must be disabled). When I do so, the sound starts to play in stereo. I would love the sound output to be stereo by default and not be forced to plug anything to achieve that. Attached is the alsa-info.sh output for my machine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1302090/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1374908] Re: power-indicator frozen immediately after boot
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: indicator-power (Ubuntu) Status: New => Confirmed -- 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/1374908 Title: power-indicator frozen immediately after boot Status in indicator-power package in Ubuntu: Confirmed Bug description: On a fresh install of Ubuntu 14.04.1, immediately after booting or resuming the system, power indicator stops updating and instead remains stuck at whatever state it was in upon boot. Power Statistics seems to accurately display the battery status, but indicator and power settings do not. I saw this problem popped up a few years back with Samsung machines and was subsequently patched, but haven't heard much about it recently. When i run upower -i /org/freedesktop/UPower/devices/battery_BAT1 the proper information shows up. My laptop has only 1 battery, and I was under the impression that it should show up under BAT0, but I am not entirely sure. The issue has not affected the actual charging and discharging of the battery. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1374908/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1429938] Re: systemd changes behavior of apt-get remove openssh-server
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1429938 Title: systemd changes behavior of apt-get remove openssh-server Status in openssh package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: On Trusty and Utopic, when you run `apt-get remove openssh-server` over an SSH connection, your existing SSH connection remains open, so it's possible to run additional commands afterward. However, on Vivid now that the switch to systemd has been made, `apt- get remove openssh-server` closes the existing SSH connection immediately, causing your SSH client to exit with a non-zero status. I have a hunch there's a lot of automation tooling out there that relies on the old behavior. For what it's worth, this change breaks the internal image mastering tools that System76 uses. Prior to exporting an image tarball, I spin up a golden VM with qemu, rysnc a script to it, and then execute this script over SSH. The important step is that I need to remove openssh-server prior to shutting down the VM, so these scripts always end with something like this: apt-get -y purge openssh-server ssh-import-id apt-get -y autoremove shutdown -h now As far as I can tell, this behavior change will likewise be a problem when running `do-release-upgrade` on a remote server over SSH. Or more generally, anytime you run "apt-get upgrade/dist-upgrade" via SSH, it seems this would be a problem whenever the openssh-server package happens to be updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1429938/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1418081] Re: Compositing is triggered continously and needlessly when there are occluded surfaces with available buffers
** No longer affects: mir/0.11 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1418081 Title: Compositing is triggered continously and needlessly when there are occluded surfaces with available buffers Status in Mir: Fix Committed Status in mir package in Ubuntu: New Bug description: Because of recent changes in the way the MultiThreadedCompositor is triggered (or rather retriggered) [1], when the DisplayBufferCompositor doesn't render (e.g. because it's occluded) a non-hidden surface that has available buffers, compositing is retriggered continuously at full rate, even when nothing else changes on screen. To test this, run the proving server: $ sudo bin/mir_proving_server --compositor-report log then start a client and drag the client offscreen. The compositor log should report that the compositor has a frame rate of max(client frame, FDP) (FDP=value related to our frame droping policy). However, you will see that it's instead rendering at 60FPS. As an extreme (but not unusual) example of how problematic this behavior can be, perform the following: 1. Change an example client to render at ~1 FPS (e.g. add sleep(1) in it's main loop). 2. Perform the previous experiment with that client When the client surface is visible, the compositor is triggered at a rate of 1FPS. The same should be true when the surface is dragged off screen, but instead we get a full compositing rate of 60FPS. [1] https://code.launchpad.net/~vanvugt/mir/fix- buffers_ready_for_compositor/+merge/247124 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1418081/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1190344] Re: lightdm is leaking FDs -fix
** Description changed:
[Impact]
- LightDM doesn't close the server side end of the pipes used to communicate
with session processes. This means each session that is created leaks two file
descriptors eventually leading to the system stopping it from creating new
pipes.
+ LightDM doesn't close the server side end of the pipes used to communicate
with session processes and greeters. This means each session/greeter that is
created leaks two file descriptors eventually leading to the system stopping it
from creating new pipes.
[Test Case]
1. Start LightDM
2. Check how many pipes are open
# lsof -p {lightdm_pid} | grep FIFO | wc -l
3. Create sessions by either cycling between users in Unity Greeter or
logging in and out
4. Check how many pipes exist using step 2.
Expected result:
No more pipes should be open
Observed result:
Many pipes remain open
[Regression Potential]
Low. Fix is to close pipes when finished with them. Tested with regression
tests.
** Summary changed:
- lightdm is leaking FDs -fix
+ Daemon end of session/greeter pipes not closed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1190344
Title:
Daemon end of session/greeter pipes not closed
Status in Light Display Manager:
Fix Committed
Status in Light Display Manager 1.10 series:
Fix Committed
Status in Light Display Manager 1.12 series:
Fix Committed
Status in Light Display Manager 1.2 series:
Fix Committed
Status in lightdm package in Ubuntu:
Triaged
Status in lightdm source package in Precise:
Triaged
Status in lightdm source package in Trusty:
Triaged
Status in lightdm source package in Utopic:
Triaged
Status in lightdm source package in Vivid:
Triaged
Status in Fedora:
Unknown
Bug description:
[Impact]
LightDM doesn't close the server side end of the pipes used to communicate
with session processes and greeters. This means each session/greeter that is
created leaks two file descriptors eventually leading to the system stopping it
from creating new pipes.
[Test Case]
1. Start LightDM
2. Check how many pipes are open
# lsof -p {lightdm_pid} | grep FIFO | wc -l
3. Create sessions by either cycling between users in Unity Greeter or
logging in and out
4. Check how many pipes exist using step 2.
Expected result:
No more pipes should be open
Observed result:
Many pipes remain open
[Regression Potential]
Low. Fix is to close pipes when finished with them. Tested with regression
tests.
To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1190344/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371378] Re: Session locking doesn't work if the session was unlocked after changing VT
** Also affects: lightdm (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1371378
Title:
Session locking doesn't work if the session was unlocked after
changing VT
Status in Light Display Manager:
Fix Committed
Status in Light Display Manager 1.10 series:
Triaged
Status in lightdm package in Ubuntu:
New
Bug description:
Test machine: Ubuntu 14.04 with lightdm-1.10.1-0ubuntu1 and lightdm
trunk revision 2064
Reproducing the bug:
1. Log into an user session using Unity, Gnome 3 or Cairo-Dock session.
2. If using a Gnome 3 session, trigger the screensaver by executing
"xdg-screensaver lock", and then unlock it by entering the user password (this
is needed to avoid bug #1371374).
3. Lock the session executing "dm-tool lock" in a terminal.
4. A new greeter is displayed.
5. Switch to the user session by switching VT (e.g. Alt+Ctrl-F7).
6. The user session is locked by the screensaver (which under a Unity session
just looks like the greeter), prompting for the user password.
7. Unlock the screensaver by introducing the user password.
8. Lock the session again ("dm-tool lock").
9. The greeter is shown again.
10. Switch to the user session by switching VT (e.g. Alt+Ctrl-F7).
11. The session isn't locked at all.
Causes:
Lightdm is not aware of VT changes, therefore when the session is
unlocked by using the screensaver in the user session's VT instead of
the greeter, lightdm is thinking that the active session is still the
greeter session.
When locking the session afterwards, in the function
seat_set_active_session() the session to be activated (the greeter) is
compared to the session that light thinks that is active, which it
thinks is the greeter because it was the last session activated by
lightdm, and therefore locking is not performed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1371378/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1430103] Re: package language-pack-gnome-en-base 1:14.04+20150219 failed to install/upgrade: package language-pack-gnome-en-base is already installed and configured
*** This bug is a duplicate of bug 1424347 *** https://bugs.launchpad.net/bugs/1424347 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1424347, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Tags removed: need-duplicate-check ** This bug has been marked a duplicate of bug 1424347 package language-pack-gnome-en-base 1:14.04+20150219 failed to install/upgrade: package language-pack-gnome-en-base is already installed and configured -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to language-pack-gnome-en- base in Ubuntu. https://bugs.launchpad.net/bugs/1430103 Title: package language-pack-gnome-en-base 1:14.04+20150219 failed to install/upgrade: package language-pack-gnome-en-base is already installed and configured Status in language-pack-gnome-en-base package in Ubuntu: New Bug description: package language-pack-gnome-en-base 1:14.04+20150219 failed to install/upgrade: package language-pack-gnome-en-base is already installed and configured ProblemType: Package DistroRelease: Ubuntu 14.04 Package: language-pack-gnome-en-base 1:14.04+20150219 ProcVersionSignature: Ubuntu 3.13.0-46.77-generic 3.13.11-ckt15 Uname: Linux 3.13.0-46-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.14.1-0ubuntu3.7 AptdaemonVersion: 1.1.1-1ubuntu5.1 Architecture: amd64 Date: Mon Mar 9 21:26:02 2015 DuplicateSignature: package:language-pack-gnome-en-base:1:14.04+20150219:package language-pack-gnome-en-base is already installed and configured ErrorMessage: package language-pack-gnome-en-base is already installed and configured InstallationDate: Installed on 2015-02-08 (29 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: language-pack-gnome-en-base Title: package language-pack-gnome-en-base 1:14.04+20150219 failed to install/upgrade: package language-pack-gnome-en-base is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-pack-gnome-en-base/+bug/1430103/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1430103] [NEW] package language-pack-gnome-en-base 1:14.04+20150219 failed to install/upgrade: package language-pack-gnome-en-base is already installed and configured
*** This bug is a duplicate of bug 1424347 *** https://bugs.launchpad.net/bugs/1424347 Public bug reported: package language-pack-gnome-en-base 1:14.04+20150219 failed to install/upgrade: package language-pack-gnome-en-base is already installed and configured ProblemType: Package DistroRelease: Ubuntu 14.04 Package: language-pack-gnome-en-base 1:14.04+20150219 ProcVersionSignature: Ubuntu 3.13.0-46.77-generic 3.13.11-ckt15 Uname: Linux 3.13.0-46-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.14.1-0ubuntu3.7 AptdaemonVersion: 1.1.1-1ubuntu5.1 Architecture: amd64 Date: Mon Mar 9 21:26:02 2015 DuplicateSignature: package:language-pack-gnome-en-base:1:14.04+20150219:package language-pack-gnome-en-base is already installed and configured ErrorMessage: package language-pack-gnome-en-base is already installed and configured InstallationDate: Installed on 2015-02-08 (29 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: language-pack-gnome-en-base Title: package language-pack-gnome-en-base 1:14.04+20150219 failed to install/upgrade: package language-pack-gnome-en-base is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: language-pack-gnome-en-base (Ubuntu) Importance: Undecided Status: New ** Tags: already-installed amd64 apport-package trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to language-pack-gnome-en- base in Ubuntu. https://bugs.launchpad.net/bugs/1430103 Title: package language-pack-gnome-en-base 1:14.04+20150219 failed to install/upgrade: package language-pack-gnome-en-base is already installed and configured Status in language-pack-gnome-en-base package in Ubuntu: New Bug description: package language-pack-gnome-en-base 1:14.04+20150219 failed to install/upgrade: package language-pack-gnome-en-base is already installed and configured ProblemType: Package DistroRelease: Ubuntu 14.04 Package: language-pack-gnome-en-base 1:14.04+20150219 ProcVersionSignature: Ubuntu 3.13.0-46.77-generic 3.13.11-ckt15 Uname: Linux 3.13.0-46-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.14.1-0ubuntu3.7 AptdaemonVersion: 1.1.1-1ubuntu5.1 Architecture: amd64 Date: Mon Mar 9 21:26:02 2015 DuplicateSignature: package:language-pack-gnome-en-base:1:14.04+20150219:package language-pack-gnome-en-base is already installed and configured ErrorMessage: package language-pack-gnome-en-base is already installed and configured InstallationDate: Installed on 2015-02-08 (29 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: language-pack-gnome-en-base Title: package language-pack-gnome-en-base 1:14.04+20150219 failed to install/upgrade: package language-pack-gnome-en-base is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-pack-gnome-en-base/+bug/1430103/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1430104] [NEW] Uses obsolete package naming
Public bug reported: The binary package for the Ubuntu fonts is "ttf-ubuntu-font-family". This is the obsolete naming scheme for fonts, it should be "fonts- ubuntu-font-family" now. ** Affects: ubuntu-font-family-sources (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-font-family-sources in Ubuntu. https://bugs.launchpad.net/bugs/1430104 Title: Uses obsolete package naming Status in ubuntu-font-family-sources package in Ubuntu: New Bug description: The binary package for the Ubuntu fonts is "ttf-ubuntu-font-family". This is the obsolete naming scheme for fonts, it should be "fonts- ubuntu-font-family" now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-font-family-sources/+bug/1430104/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1406802] Re: Vivid Unity Wallpaper horizontally hashed
Yesterday installed Nov 11 Vivid .iso in another partition. Wallpaper works fine. As of mid December to present, every boot wallpaper screwed up on Lenovo M58p Files > Pictures > select jpg > set as wallpaper a couple times get correct wallpaper display. Reboot, all screwed up again. What's different in the Set Wallpaper packages between Nov. 11 and mid December that screwed up the display? Any way to compare the two since they are in two different partitions? -- 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/1406802 Title: Vivid Unity Wallpaper horizontally hashed Status in Unity: New Status in unity package in Ubuntu: New Bug description: Standard wallpaper selection distorted badly cut and displaced sideways. See screenshot. Lenovo Desktop Dual processor: processor : 0 vendor_id : GenuineIntel cpu family: 6 model : 23 model name: Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz Standard dropdown windows like terminal, internet etc. normal. DISTRIB_RELEASE=15.04 DISTRIB_CODENAME=vivid DISTRIB_DESCRIPTION="Ubuntu Vivid Vervet (development branch)" Linux Lenovo2 3.16.0-28-generic #38-Ubuntu SMP Fri Dec 12 17:37:40 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux model name: Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz model name: Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz 00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset Integrated Graphics Controller (rev 03) jerry@Lenovo2:~$ ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.1+15.04.20141216-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.15.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Dec 31 14:06:16 2014 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e12] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkCentre M6258 [17aa:3048] Subsystem: Lenovo Device [17aa:3048] InstallationDate: Installed on 2014-10-27 (65 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141026) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic root=UUID=81fa31d4-972b-409f-9b0b-d34528ec9238 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/10/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 5CKT69AUS dmi.board.name: LENOVO dmi.chassis.vendor: LENOVO dmi.chassis.version: NONE dmi.modalias: dmi:bvnLENOVO:bvr5CKT69AUS:bd01/10/2011:svnLENOVO:pn6234A1U:pvrThinkCentreM58p:rvnLENOVO:rnLENOVO:rvrNONE:cvnLENOVO:ct3:cvrNONE: dmi.product.name: 6234A1U dmi.product.version: ThinkCentre M58p dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.0+15.04.20141219-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.58-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.2.901-1ubuntu3 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.916+git20141119-1~exp1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Wed Dec 31 14:04:58 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.16.2.901-1ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1406802/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1377872] Re: Double-buffered compositing performance is very poor (30 FPS) on intel
Confirmed by duplicate. kdub is seeing similar. ** Changed in: mir Status: Incomplete => Confirmed ** Changed in: mesa (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1377872 Title: Double-buffered compositing performance is very poor (30 FPS) on intel Status in Mesa: Confirmed Status in Mir: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: Double-buffered compositing performance is poor. Fortunately we don't use double-buffering in our default compositor (mostly), and Ubuntu touch does not use the default compositor either. However, if you make the compositor double-buffered, then it quickly drops down to 30 FPS while not consuming any significant CPU or render time. Test case A: Convert your compositor to double buffering by the code change suggested in bug 1350725. Test case B (different bug?): Switch all clients to double-buffering using this branch: lp:~vanvugt/mir/double and then start a nested server. Now start a bunch of clients, and you will find they slow down to 30 FPS after only starting a few. This does not happen with the default triple buffered compositor. I've been ignoring this issue for a little while [1] thinking I had simply run out of power, although suspected that can't be right as this is a powerful quad-core i7 and it's slowing down with only 10 clients. [1] https://bugs.launchpad.net/mir/+bug/1350725/comments/1 Now today test case B has revealed (via MIR_CLIENT_PERF_REPORT) that the slowdown happens without using any significant render time (less than 2 ms) and without using any significant CPU (less than 20% of one out of four cores). So the conclusion is our default compositor is probably holding buffers for a little too long somewhere. Because that's the only sensible reason I can think of for my system to bog down to 30 FPS without stressing the CPU or GPU. We've got poor parallelism in our code somewhere. And once that's solved, we'll be able to make further improvements such as resolving bug 1350725. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1377872/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1315434] Re: Mouse with no time remaining estimate showing in preference to battery being charged
What file should this patch apply to? It was not specified in the file. -- 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/1315434 Title: Mouse with no time remaining estimate showing in preference to battery being charged Status in indicator-power package in Ubuntu: In Progress Bug description: When my laptop battery is in a charging state, but is not fully charged, I expect it to be displayed in preference to my mouse, which has no time remaining estimate. The spec here: https://wiki.ubuntu.com/Power says: "If anything is discharging, the menu title should represent the component (not battery, but component) that is estimated to lose power first. For example, if your notebook battery is estimated to discharge in 1 hour 47 minutes, and your wireless mouse battery is estimated to discharge in 27 minutes, the menu title should represent the mouse. " but there doesn't seem to be any guideline to what happens when a battery is being charged. I suggest the time remaining to charge a battery should be displayed in preference to the power level in a wireless mouse. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-power 12.10.6+14.04.20140411-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Fri May 2 11:50:36 2014 InstallationDate: Installed on 2013-11-26 (156 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: indicator-power UpgradeStatus: Upgraded to trusty on 2014-01-17 (104 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1315434/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1380982] Re: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message()
In xubuntu 15.04 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1380982 Title: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message() Status in ibus package in Ubuntu: Confirmed Bug description: Error popped up after login ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: ibus 1.5.8-2ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4 Uname: Linux 3.16.0-22-generic x86_64 ApportVersion: 2.14.7-0ubuntu6 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity Date: Tue Oct 14 11:37:21 2014 ExecutablePath: /usr/lib/ibus/ibus-ui-gtk3 InstallationDate: Installed on 2014-03-06 (221 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140304) ProcCmdline: /usr/lib/ibus/ibus-ui-gtk3 ProcEnviron: LANGUAGE=de_DE PATH=(custom, user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: ibus StacktraceTop: g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () ?? () ?? () Title: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message() UpgradeStatus: Upgraded to utopic on 2014-09-10 (34 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1380982/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1430077] [NEW] [vivid] VPN connection breaks /etc/resolv.conf
Public bug reported: After some recent update in vivid, connecting to my employer's VPN with network-manager-openvpn has resulted in broken name resolution. Previously, the VPN-provided nameserver setting would be pushed into the config of the dnsmasq run by NM. Now, it is being pushed instead to /etc/resolv.conf. nameserver 10.99.244.1 nameserver 127.0.1.1 This is breaking the DNS handling for libvirt-bin, which has its own forwarding dnsmasq instance which it expects to be able to talk to the first nameserver listed here. The nameserver in question does not work (and is not meant to be used) for any name lookups except company- internal domains. Connecting to the VPN also pushes search paths to /etc/resolv.conf - overriding the search domains that I have already configured, and which should take precedence. (This part is not a regression.) I understand that the purpose of these provided domains is to specify the domains for which DNS lookups should be forwarded to the VPN DNS server, and *not* to modify the system's DNS lookups for non-FQDN requests. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu9 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 9 17:16:05 2015 InstallationDate: Installed on 2010-09-24 (1627 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WWanEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2014-12-06 (93 days ago) nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1430077 Title: [vivid] VPN connection breaks /etc/resolv.conf Status in network-manager package in Ubuntu: New Bug description: After some recent update in vivid, connecting to my employer's VPN with network-manager-openvpn has resulted in broken name resolution. Previously, the VPN-provided nameserver setting would be pushed into the config of the dnsmasq run by NM. Now, it is being pushed instead to /etc/resolv.conf. nameserver 10.99.244.1 nameserver 127.0.1.1 This is breaking the DNS handling for libvirt-bin, which has its own forwarding dnsmasq instance which it expects to be able to talk to the first nameserver listed here. The nameserver in question does not work (and is not meant to be used) for any name lookups except company-internal domains. Connecting to the VPN also pushes search paths to /etc/resolv.conf - overriding the search domains that I have already configured, and which should take precedence. (This part is not a regression.) I understand that the purpose of these provided domains is to specify the domains for which DNS lookups should be forwarded to the VPN DNS server, and *not* to modify the system's DNS lookups for non-FQDN requests. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu9 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 9 17:16:05 2015 InstallationDate: Installed on 2010-09-24 (1627 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WWanEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2014-12-06 (93 days ago) nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1430077/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1385572] Re: gnome-session not shutting down cleanly
reassigning to gnome-session, although the issue seems to be triggered by upstart pulling down things in the wrong order, most of the damage seems to come from a buggy ubuntu patch in gnome-session. ** Package changed: upstart (Ubuntu) => gnome-session (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1385572 Title: gnome-session not shutting down cleanly Status in Ubuntu GNOME: New Status in gnome-session package in Ubuntu: Confirmed Bug description: We have had reports going back to 13.10 that gnome-shell extensions are disabled after restart (LP: #1236749), I've only just managed to reproduce this and have discovered that gnome-session is not shutting down cleanly. Basically, X gets shutdown, which causes gnome-shell to abort, following this gnome-session tries to respawn gnome-shell which fails and due to this failure disables all shell extensions. I don't know enough about upstart to really understand what is going on but it appears this also affects unity and it just hasnt been noticed since there are probably no such side-effects happening there. Filing this against upstart since this is not reproducible when using systemd init, though it may well be a bug in gnome-session, but related to upstart user sessions. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: upstart 1.13.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4 Uname: Linux 3.16.0-22-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Oct 25 14:05:24 2014 InstallationDate: Installed on 2012-09-23 (762 days ago) InstallationMedia: Ubuntu GNOME Remix 12.10 "Quantal Quetzal" - Alpha amd64(20120922) SourcePackage: upstart UpgradeStatus: No upgrade log present (probably fresh install) UpstartBugCategory: Session UpstartRunningSessionCount: 1 UpstartRunningSessionVersion: upstart 1.13.2 UpstartRunningSystemVersion: init (upstart 1.13.2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1385572/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1236749] Re: Gnome shell extensions disabled at every startup
I uploaded a gnome-session update that hopefully fixes this to ppa:darkxst/ppa. Please test, if it works, will get the fix into trusty and utopic. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1236749 Title: Gnome shell extensions disabled at every startup Status in Ubuntu GNOME: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in upstart package in Ubuntu: Confirmed Bug description: Since gnome-shell 3.10, my extensions are disabled by default at every boot. I need to launch Tweak Tool to enable theme by hand every time. Both pre-installed extensions ( AlternateTab) and user-installed ones (top-icons) Step to reproduce : Enable an extension in Tweak Tool ( Alternate Tab for example) reboot computer, open Tweak Tool : Alternate tab is disabled. Running on Ubuntu 13.10 GNOME Shell 3.10.0.1 gnome-tweak-tool 3.10..0-0ubuntu1-saucy1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1236749/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1214352] Re: [SRU] GUINT32/64_SWAP_LE_BE macros do not enclose val argument in parentheses
We are not going to be rebuilding all of glib's rdeps for this in an SRU. That's insanity. I'm going to look at this later to see if there's anything we can do that looks like a sensible and targeted fix, but it does look like this is just a poor SRU candidate, due to the regression potential being worse than the fix, and people who really care deeply should perhaps just upgrade to 14.04. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1214352 Title: [SRU] GUINT32/64_SWAP_LE_BE macros do not enclose val argument in parentheses Status in LibreOffice Productivity Suite: Fix Released Status in The "G" Library - GLib: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Status in gvfs package in Ubuntu: New Status in libreoffice package in Ubuntu: New Bug description: [Impact] * This bug affects Glib-dependent packages, one of them is modern version of LibreOffice 4.x from PPA (https://launchpad.net/~libreoffice/+archive/ubuntu/ppa). * LibreOffice is very important software. Modern versions are more functional. Without them Ubuntu is nothing, it is a toy. [Test Case] 1. Place OpenDocument file (for example 'test.odt') on SMB/CIFS server (Samba on GNU/Linux, or from Windows). Make this share available for read-write. 2a.1. Open Nautilus, navigate it to 'smb://server_name/share_name/', wait the share to be mounted with GVFS. 2a.2. Double click on 'test.odt' 2b. Launch terminal and send 'libreoffice smb://server_name/share_name/test.odt' command. 3. Get error message from LibreOffice: "The file 'test.odt' is corrupt and therefore cannot be opened. LibreOffice can try to repair the file. The corruption could be the result of document manipulation or of structural document damage due to data transmission. We recommend that you do not trust the content of the repaired document. Execution of macros is disabled for this document. Should LibreOffice repair the file? Yes No" 4a. If I click 'Yes', the file is opened, but the title of the document is "Untitled 1 (repaired document)", not original name. 4b. If I click 'No', the dialog 'LibreOffice 4.4' is opened with text: The file 'test.odt' could not be repaired and therefore cannot be opened. OK" I click 'OK' here, the next window "LibreOffice 4.4.1.2" is opened with text: "General Error. General input/output error. OK" If I click OK here - no files are opened. While step 3 gvfsd-smb process eats CPU then terminates with error. This error is caused by bug in Glib (wrong type conversion in macros). [Regression Potential] * This functionality is essential. Please fix this bug. I (and you) can't tell Windows users, that they should not open office files from network shares in GNU/Linux. * The patch has two lines (https://git.gnome.org/browse/glib/commit/?id=255c65f83c1515a7e3fc4609b36e72acc08a79e4) and well-tested at upstream. * This bug may cause potential loss of data. [Other Info] * Corresponding links to LibO bugs are: https://bugs.freedesktop.org/show_bug.cgi?id=67527 https://bugs.documentfoundation.org/show_bug.cgi?id=72337 [Original description] On 12.04 LTS precise GUINT32/64_SWAP_LE_BE macros do not enclose val argument in parentheses, causing trouble down the stack in gvfs and LibreOffice (and possibly in lots of obscure bugs elsewhere). There is a patch available, but as this touches the header, it needs a full recompile of rdepends. see: https://lists.fedoraproject.org/pipermail/devel/2013-March/180302.html ff. for details To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1214352/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1430063] Re: FTBFS on Ubuntu Vivid
** Branch linked: lp:~bregma/unity-scope-home/lp-1430063 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-home in Ubuntu. https://bugs.launchpad.net/bugs/1430063 Title: FTBFS on Ubuntu Vivid Status in unity-scope-home package in Ubuntu: In Progress Bug description: The unity-scope-home package fails to build from source on Ubuntu Vivid. Apparently, an uninitialized variable is an error in valac-0.26. Excerpt from build log follows. smart-scopes-parse.vala:158.19-162.15: error: use of possibly unassigned local variable `tp' smart-scopes-preview-parser.vala:48.141-48.163: warning: use of possibly unassigned parameter `attribution' internal void get_base_attributes (Json.Object obj, out string title, out string subtitle, out string description, out GLib.Icon? icon, out string? attribution) ^^^ Compilation failed: 1 error(s), 11 warning(s) Makefile:1166: recipe for target 'unity_scope_home.vala.stamp' failed make[3]: *** [unity_scope_home.vala.stamp] Error 1 make[3]: Leaving directory '/build/buildd/unity-scope-home-6.8.2+14.04.20131029.1/src' Makefile:523: recipe for target 'all-recursive' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scope-home/+bug/1430063/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1385572] Re: gnome-session not shutting down cleanly
we disable the fail whale dialog on ubuntu, but then just return back into the code, without telling gnome-session to die which is causing some problems. the fail whale should be fatal and the disabled dialog, would normally tell gnome-session to quit. ** Patch added: "whale-fix.debdiff" https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1385572/+attachment/4339360/+files/whale-fix.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1385572 Title: gnome-session not shutting down cleanly Status in Ubuntu GNOME: New Status in upstart package in Ubuntu: Confirmed Bug description: We have had reports going back to 13.10 that gnome-shell extensions are disabled after restart (LP: #1236749), I've only just managed to reproduce this and have discovered that gnome-session is not shutting down cleanly. Basically, X gets shutdown, which causes gnome-shell to abort, following this gnome-session tries to respawn gnome-shell which fails and due to this failure disables all shell extensions. I don't know enough about upstart to really understand what is going on but it appears this also affects unity and it just hasnt been noticed since there are probably no such side-effects happening there. Filing this against upstart since this is not reproducible when using systemd init, though it may well be a bug in gnome-session, but related to upstart user sessions. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: upstart 1.13.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4 Uname: Linux 3.16.0-22-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Oct 25 14:05:24 2014 InstallationDate: Installed on 2012-09-23 (762 days ago) InstallationMedia: Ubuntu GNOME Remix 12.10 "Quantal Quetzal" - Alpha amd64(20120922) SourcePackage: upstart UpgradeStatus: No upgrade log present (probably fresh install) UpstartBugCategory: Session UpstartRunningSessionCount: 1 UpstartRunningSessionVersion: upstart 1.13.2 UpstartRunningSystemVersion: init (upstart 1.13.2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1385572/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1430063] [NEW] FTBFS on Ubuntu Vivid
Public bug reported: The unity-scope-home package fails to build from source on Ubuntu Vivid. Apparently, an uninitialized variable is an error in valac-0.26. Excerpt from build log follows. smart-scopes-parse.vala:158.19-162.15: error: use of possibly unassigned local variable `tp' smart-scopes-preview-parser.vala:48.141-48.163: warning: use of possibly unassigned parameter `attribution' internal void get_base_attributes (Json.Object obj, out string title, out string subtitle, out string description, out GLib.Icon? icon, out string? attribution) ^^^ Compilation failed: 1 error(s), 11 warning(s) Makefile:1166: recipe for target 'unity_scope_home.vala.stamp' failed make[3]: *** [unity_scope_home.vala.stamp] Error 1 make[3]: Leaving directory '/build/buildd/unity-scope-home-6.8.2+14.04.20131029.1/src' Makefile:523: recipe for target 'all-recursive' failed ** Affects: unity-scope-home (Ubuntu) Importance: High Assignee: Stephen M. Webb (bregma) Status: In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-home in Ubuntu. https://bugs.launchpad.net/bugs/1430063 Title: FTBFS on Ubuntu Vivid Status in unity-scope-home package in Ubuntu: In Progress Bug description: The unity-scope-home package fails to build from source on Ubuntu Vivid. Apparently, an uninitialized variable is an error in valac-0.26. Excerpt from build log follows. smart-scopes-parse.vala:158.19-162.15: error: use of possibly unassigned local variable `tp' smart-scopes-preview-parser.vala:48.141-48.163: warning: use of possibly unassigned parameter `attribution' internal void get_base_attributes (Json.Object obj, out string title, out string subtitle, out string description, out GLib.Icon? icon, out string? attribution) ^^^ Compilation failed: 1 error(s), 11 warning(s) Makefile:1166: recipe for target 'unity_scope_home.vala.stamp' failed make[3]: *** [unity_scope_home.vala.stamp] Error 1 make[3]: Leaving directory '/build/buildd/unity-scope-home-6.8.2+14.04.20131029.1/src' Makefile:523: recipe for target 'all-recursive' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scope-home/+bug/1430063/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1393169] Re: Double mouse cursor
Gianni Andreoli, it would help immensely if you filed a new report via a terminal: ubuntu-bug xorg Please feel free to subscribe me to it. -- 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/1393169 Title: Double mouse cursor Status in xorg package in Ubuntu: Incomplete Bug description: Last up to date Xubuntu 64 bits installed on a laptop Since 2 days, the mouse cursor is double with only the left part as active and a bar just behing of both arrow (see picture joined). I tried to change the theme but no way to go back to a normal mouse cursor Regards ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Nov 16 11:12:21 2014 InstallationDate: Installed on 2013-01-03 (681 days ago) InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: utopic DistroRelease: Ubuntu 14.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:fde0] Subsystem: Toshiba America Info Systems Device [1179:fde0] InstallationDate: Installed on 2013-01-03 (695 days ago) InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) LightdmGreeterLog: ** (lightdm-gtk-greeter:1659): WARNING **: Failed to load background: Impossible d'ouvrir le fichier « /home/christophe/Dropbox/Personnalisation/Fonds d'écran/bleu.jpg » : Permission non accordée ** (lightdm-gtk-greeter:1659): WARNING **: Failed to read wallpaper: /home/christophe/Dropbox/Personnalisation/Fonds d'écran/bleu.jpg g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. LightdmGreeterLogOld: ** (lightdm-gtk-greeter:1641): WARNING **: Failed to load background: Impossible d'ouvrir le fichier « /home/christophe/Dropbox/Personnalisation/Fonds d'écran/bleu.jpg » : Permission non accordée ** (lightdm-gtk-greeter:1641): WARNING **: Failed to read wallpaper: /home/christophe/Dropbox/Personnalisation/Fonds d'écran/bleu.jpg g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. MachineType: TOSHIBA Satellite Pro C650 Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-26-generic root=UUID=7bc86e4b-720d-4f1c-bb66-a4c08ffc1359 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-26.34-generic 3.16.7-ckt1 Tags: utopic ubuntu Uname: Linux 3.16.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/01/2010 dmi.bios.vendor: INSYDE dmi.bios.version: 1.30 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.30:bd07/01/2010:svnTOSHIBA:pnSatelliteProC650:pvrPSC09E-00R01YMV:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Satellite Pro C650 dmi.product.version: PSC09E-00R01YMV dmi.sys.vendor: TOSHIBA version.compiz: compiz N/A 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 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Fri Nov 28 08:29:52 2014 xserver.configfile: default xserver.errors: x
[Touch-packages] [Bug 1413201] Re: date setted to 1970
Raisa: -- Forwarded message -- From: Raisa Date: Mon, Mar 9, 2015 at 10:46 AM Subject: [Bug 1413201] Re: Re: date setted to 1970 To: Christopher M. Penalver Hi Christopher, thanks for your support! I didn't know Quantal reached EOL. How do I upgrade to Ubuntu 14.04 LTS Trusty Tahr? (4th record from current list on wiki) Warning: I can't open secured http-websites. But I'll be happy if you e-mail me the install-code, I can work a little bit with the terminal screen. Thanks in advance, Raisa It is strongly recommended you immediately backup your data, and do a fresh reinstall via http://releases.ubuntu.com/trusty/ . It sounds like your machine is either suffering from critical software errors, or your machine is compromised. Upgrading would not be a great idea in this case. -- 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/1413201 Title: date setted to 1970 Status in xorg package in Ubuntu: Incomplete Bug description: Everything worked normal until that day in November 2013. I started the netbook and suddenly the date was set on 01-01-1970. I tried to change it myself, but couldn't do it. Also surfing is a problem: it won't open https-websites anymore. Thanks in advance for your help. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-32.53-generic 3.5.7.11 Uname: Linux 3.5.0-32-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu10 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz Date: Thu Jan 1 01:24:21 1970 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu DpkgLog: EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a011] (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0349] Subsystem: Acer Incorporated [ALI] Device [1025:0349] InstallationDate: Installed on 2013-03-23 (-15787 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) MachineType: Acer AOD255 MarkForUpload: True ProcEnviron: LANGUAGE=nl:en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-32-generic root=/dev/mapper/ubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2010 dmi.bios.vendor: Acer dmi.bios.version: V3.05(DDR2) dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: AOD255 dmi.board.vendor: Acer dmi.board.version: V3.05(DDR2) dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V3.05(DDR2) dmi.modalias: dmi:bvnAcer:bvrV3.05(DDR2):bd08/12/2010:svnAcer:pnAOD255:pvrV3.05(DDR2):rvnAcer:rnAOD255:rvrV3.05(DDR2):cvnAcer:ct10:cvrV3.05(DDR2): dmi.product.name: AOD255 dmi.product.version: V3.05(DDR2) dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.8.6-0ubuntu1 version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1413201/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1429938] Re: systemd changes behavior of apt-get remove openssh-server
** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1429938 Title: systemd changes behavior of apt-get remove openssh-server Status in openssh package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: On Trusty and Utopic, when you run `apt-get remove openssh-server` over an SSH connection, your existing SSH connection remains open, so it's possible to run additional commands afterward. However, on Vivid now that the switch to systemd has been made, `apt- get remove openssh-server` closes the existing SSH connection immediately, causing your SSH client to exit with a non-zero status. I have a hunch there's a lot of automation tooling out there that relies on the old behavior. For what it's worth, this change breaks the internal image mastering tools that System76 uses. Prior to exporting an image tarball, I spin up a golden VM with qemu, rysnc a script to it, and then execute this script over SSH. The important step is that I need to remove openssh-server prior to shutting down the VM, so these scripts always end with something like this: apt-get -y purge openssh-server ssh-import-id apt-get -y autoremove shutdown -h now As far as I can tell, this behavior change will likewise be a problem when running `do-release-upgrade` on a remote server over SSH. Or more generally, anytime you run "apt-get upgrade/dist-upgrade" via SSH, it seems this would be a problem whenever the openssh-server package happens to be updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1429938/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1319789] Re: Trackpad not working on 14.04
varun, as per support.hp.com/us-en/product/HP-Pavilion-15-n200-Notebook- PC-series/6529948/model/6622555/drivers an update to your computer's buggy and outdated BIOS is available (F.66). 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-full-computer-model ** Tags added: bios-outdated-f.66 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1319789 Title: Trackpad not working on 14.04 Status in xorg package in Ubuntu: Incomplete Bug description: ever since the laptop was updated to 14.04 lts from 12.04 lts, the tracpad has not been working, and is not recognised. there is no trackpad option under mouse and trackpad settings. i have tried many attempts to fix it, but has not worked. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: [core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu May 15 17:02:52 2014 DistUpgraded: 2014-05-11 18:24:24,169 DEBUG enabling apt cron job DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-puli-precise-amd64-20130925-0 DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:2166] Subsystem: Hewlett-Packard Company Device [103c:2166] InstallationDate: Installed on 2013-11-28 (168 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20130925-02:34 MachineType: Hewlett-Packard HP Pavilion 15 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=856eced2-cdd1-459e-8b1e-55b1ed18f5ac ro i915.modeset=1 quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-05-11 (3 days ago) dmi.bios.date: 10/31/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.34 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2166 dmi.board.vendor: Hewlett-Packard dmi.board.version: 29.34 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.34:bd10/31/2013:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr09921100410600080:rvnHewlett-Packard:rn2166:rvr29.34:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion 15 Notebook PC dmi.product.version: 09921100410600080 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Thu May 15 16:37:20 2014 xserver.configfile: default xserver.errors: module ABI major version (18) doesn't match the server's version (20) Failed to load module "syntp" (module requirement mismatch, 0) module ABI major version (18) doesn't match the server's version (20) Failed to load module "syntp" (module requ
[Touch-packages] [Bug 1302090] Re: Dell Alienware 14, Speaker sound output is mono until a headphone jack is plugged
autoconfig: line_outs=2 (0x18/0x1a/0x0/0x0/0x0) type:line speaker_outs=1 (0x14/0x0/0x0/0x0/0x0) hp_outs=2 (0x15/0x16/0x0/0x0/0x0) mono: mono_out=0x0 inputs: Mic=0x19 Internal Mic=0x12 this won't create correct name for the volume control for the subwoofer , driver assign front playback volume to node 0x18, surround playback volume to 0x1a (fake line out) only one DAC for the remaining headphones and speaker did both left and right channel affect the subwoofer ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1302090 Title: Dell Alienware 14, Speaker sound output is mono until a headphone jack is plugged Status in alsa-driver package in Ubuntu: Confirmed Bug description: Here's the required release and package information: Description:Ubuntu Trusty Tahr (development branch) Release:14.04 Package: linux-image-extra-3.13.0-19-generic Version: 3.13.0-19.40 When playing audio through speakers on my Alienware 14 2014, the sound output is in mono until I plug a headphone in any of the two available headphone jacks (obviously, the auto-mute option must be disabled). When I do so, the sound starts to play in stereo. I would love the sound output to be stereo by default and not be forced to plug anything to achieve that. Attached is the alsa-info.sh output for my machine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1302090/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1366876] Re: Xorg freeze
James Ferguson, regarding the 14.04.2 install not working, please do file a new report on that against the relevant package. For more on finding out which package to file that against, please see https://wiki.ubuntu.com/DebuggingProcedures . Regarding your comments about the daily "since I can't work under that", could you please define what you mean by this specifically? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1366876 Title: Xorg freeze Status in xorg package in Ubuntu: Incomplete Bug description: Desktop display freezes temporarily, for (approx) 20s or so, approx once a day, with mouse pointer still working. After that it comes back and resumes as normal, seemingly replaying mouse and keyboard events from the meantime. I think it's always happened when using Google Chrome (Stable - currently 37.0.2062.94, but I think other recent versions). The desktop is completely unresponsive This didn't seem to happen until a few weeks ago. I tend to pull updates fairly regularly. In syslog there is: kernel: [277415.130771] [drm] stuck on render ring I suspect this is a dupe since I see other related bugs, but you'd be better placed to decide that than I. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,resize,place,grid,vpswitch,gnomecompat,mousepoll,session,move,obs,imgpng,snap,regex,animation,expo,ezoom,staticswitcher,workarounds,wall,fade,scale] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Sep 8 12:22:27 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: comedi-adv-pci1724, 0.0.1: added EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Since a couple weeks or more GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21fa] InstallationDate: Installed on 2014-07-11 (59 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: LENOVO 2306CTO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=561b4b77-cac6-4abb-a89e-ecf7f1bb8f42 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/11/2012 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET82WW (2.02 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET82WW(2.02):bd09/11/2012:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2306CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Thu Sep 4 16:58:14 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 728 vendor LGD xserver.version: 2:1.15.1-0ubuntu2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1366876/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1428184] Re: Invisible mouse pointer after resume from suspend
Eduardo Rudas, 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. ** Attachment removed: "Dependencies.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1428184/+attachment/433/+files/Dependencies.txt ** Attachment removed: "ProcEnviron.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1428184/+attachment/4334445/+files/ProcEnviron.txt ** Description changed: I'm using a Samsung NP305U1A-A05CO laptop. After the computer is suspended, either by closing the lid, choosing the option on the menu or by itself after the defined time, and then when I wake the computer the mouse pointer is invisible, however the hardware itself is working as mouse position and clicks continue working, only the pointer is invisible. WORKAROUND: If I switch to a console with Alt+Shit+F1 and switch back to X with Alt+Shift+F7 the mouse pointer appears and is back to normal. WORKAROUND: After installing fglrx 14.50.2 proprietary AMD driver (doing the modification explained in http://askubuntu.com/a/543836/378463 to avoid ocl-icd-libopencl1/wine conflict) including the Catalyst Control Center, the problem is resolved and now I can suspend and resume the computer and the mouse pointer is visible after wake up as expected. - ProblemType: Bug - DistroRelease: Ubuntu 14.04 - Package: xorg 1:7.7+1ubuntu8.1 - ProcVersionSignature: Ubuntu 3.13.0-46.76-generic 3.13.11-ckt15 - Uname: Linux 3.13.0-46-generic x86_64 - NonfreeKernelModules: fglrx - ApportVersion: 2.14.1-0ubuntu3.7 - Architecture: amd64 - Date: Wed Mar 4 10:08:23 2015 - InstallationDate: Installed on 2015-02-12 (20 days ago) - InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) - SourcePackage: xorg - UpgradeStatus: No upgrade log present (probably fresh install) - --- + --- ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: vivid DistroRelease: Ubuntu 15.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: - Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6320] [1002:9806] (prog-if 00 [VGA controller]) -Subsystem: Samsung Electronics Co Ltd Device [144d:c600] + Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6320] [1002:9806] (prog-if 00 [VGA controller]) + Subsystem: Samsung Electronics Co Ltd Device [144d:c600] InstallationDate: Installed on 2015-03-09 (0 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150306) MachineType: SAMSUNG ELECTRONICS CO., LTD. 305U1A Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-7-generic root=UUID=7728ff72-aa41-4a63-9626-9f8b734c3785 ro persistent quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Tags: vivid ubuntu reproducible has-workaround Uname: Linux 3.19.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/24/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 06PS.M507.20121024.LEO dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 305U1A/305U1A dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: 06PS dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr06PS.M507.20121024.LEO:bd10/24/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn305U1A:pvr06PS:rvnSAMSUNGELECTRON
[Touch-packages] [Bug 1311706] Re: XU 12.04-4 dual display not working nvidia 173 on nv34 card
Galen Thurber, 12.04.5 is not EOL. 12.04.4 is EOL as previously noted. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1311706 Title: XU 12.04-4 dual display not working nvidia 173 on nv34 card Status in xorg package in Ubuntu: Invalid Bug description: hoping to get Precise Pangolin 12.04 LT Xubuntu running dual displays, on VGA (CRT) the other smart tv via HDMI. as soon as xu goes to login screen I lose DVI to HDMI connection. Other distros, sparky, mint, puppy all work fine with dual display I run nvidia 173 on a nv34 video card /0/100/b/0 display NV34 [GeForce FX 5200] /0/100/ebridge nForce3 250Gb PCI-to-PCI Bridge 3.2.0-60-generic #91-Ubuntu SMP Wed Feb 19 03:54:44 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux nvidia config does not show a second display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1311706/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1302090] Re: Dell Alienware 14, Speaker sound output is mono until a headphone jack is plugged
speaker and subwoofer should assign DAC(Volume) first instead of two headphone by increasing badness for (type HP) when there is no line out if (!spec->no_multi_io && cfg->hp_outs && cfg->line_out_type == AUTO_PIN_SPEAKER_OUT) if (count_multiio_pins(codec, cfg->hp_pins[0]) >= 2) spec->multi_ios = 1; /* give badness */ +if ((cfg->speaker_outs == 2) && (cfg->hp_outs == 2) && (cfg->line_outs == 0)) + if (cfg->line_out_type == AUTO_PIN_HP_OUT) + badness++ /* re-count num_dacs and squash invalid entries */ spec->multiout.num_dacs = 0; -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1302090 Title: Dell Alienware 14, Speaker sound output is mono until a headphone jack is plugged Status in alsa-driver package in Ubuntu: Confirmed Bug description: Here's the required release and package information: Description:Ubuntu Trusty Tahr (development branch) Release:14.04 Package: linux-image-extra-3.13.0-19-generic Version: 3.13.0-19.40 When playing audio through speakers on my Alienware 14 2014, the sound output is in mono until I plug a headphone in any of the two available headphone jacks (obviously, the auto-mute option must be disabled). When I do so, the sound starts to play in stereo. I would love the sound output to be stereo by default and not be forced to plug anything to achieve that. Attached is the alsa-info.sh output for my machine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1302090/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1316090] Re: Unable to drop/ place files and links on second screen in dual screen set up
Natalia, yes please send the information anyways. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1316090 Title: Unable to drop/ place files and links on second screen in dual screen set up Status in xorg package in Ubuntu: Incomplete Bug description: After updating from Xubuntu 13.10 (amd64) to Xubuntu 14.04 LTS (amd64) I have encountered a bug with my dual screen set up. Running the XOrg screen driver (xserver-xorg-video-nouveau), it is possible to place/ drag and drop files and links on my left screen desktop. This is also the desktop that contains the system icons (e.g. removable drives, rubbish bin). However, I I try to drag and drop a file or link on the right screen desktop, it will not "stick" and "fly back" to its original location on the left screen. Additionally, I noticed that, when dragging the file over the troubled desktop, the "placement squares" don't show up. They do on the functioning left screen. Although I have a NVIDIA Corporation GK107 [GeForce GTX 650] Geforce I do run the XOrg driver since it gives me the best results with the software I'm using frequently. However, when I tested this during my initial install of Trusty, I noticed that I did not encounter this bug with the proprietary NVidia 304.117 driver (331.38 did not work for me at all). Running the NVidia 304.117 driver, it was possible to drag and drop/ place files and links on both screen desktops. Also the "placement squares" appeared on both screens when a file was dragged over it. After returning to the XOrg driver, the problem reoccurred, and placement on the right screen was again not possible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1316090/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1424864] Re: Xorg crash
Galen Thurber, so when you ran the command it suggested you run, then what happened? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1424864 Title: Xorg crash Status in xorg package in Ubuntu: Incomplete Bug description: Xorg crashing out & back into login manager and apport failed This problem report is damaged and cannot be processed. IOError(u'Invalid core dump: BFD: Warning: /tmp/tmpXYLMdA is truncated: expected core file size >= 75243520, found: 6356992.',) openConnection: connect: No such file or directory cannot connect to brltty at :0 xfce4-settings-helper: Another instance is already running. Leaving... (polkit-gnome-authentication-agent-1:9183): GLib-CRITICAL **: g_variant_new_string: assertion `string != NULL' failed (polkit-gnome-authentication-agent-1:9183): polkit-gnome-1-WARNING **: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files ERROR: Error querying target relations ERROR: Error querying target relations ERROR: Error querying target relations ERROR: Error querying target relations ERROR: Error querying target relations (xfce4-settings-helper:9229): xfce4-settings-helper-WARNING **: Failed to get the _NET_NUMBER_OF_DESKTOPS property. ** Message: applet now removed from the notification area ** Message: using fallback from indicator to GtkStatusIcon ** Message: applet now embedded in the notification area WARNING: gnome-keyring:: couldn't connect to: /tmp/keyring-P0TMTU/pkcs11: No such file or directory (Thunar:9173): GLib-GIO-CRITICAL **: g_file_info_get_attribute_uint32: assertion `G_IS_FILE_INFO (info)' failed (Thunar:9173): GLib-GIO-CRITICAL **: g_file_info_get_attribute_uint32: assertion `G_IS_FILE_INFO (info)' failed WARNING: gnome-keyring:: couldn't connect to: /tmp/keyring-P0TMTU/pkcs11: No such file or directory ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-76.111-generic 3.2.66 Uname: Linux 3.2.0-76-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.8 Architecture: amd64 Date: Mon Feb 23 19:14:16 2015 InstallationMedia: Xubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 (20140205) MarkForUpload: True ProcEnviron: LANGUAGE=en_CA:en TERM=xterm PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1424864/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1429975] Re: nfs no longer mounted at boot with systemd
I've seen this as well on my desktop. For me it was not a regression vs. upstart (there are bug reports about nfs mounts similarly not being mounted at boot under upstart in Ubuntu 14.10 and later), which is why I did not consider this a blocker for switching by default. Looking at the systemd mount generator output on my system, I see entries such as: $ cat /run/systemd/generator/srv.mount # Automatically generated by systemd-fstab-generator [Unit] SourcePath=/etc/fstab Documentation=man:fstab(5) man:systemd-fstab-generator(8) Before=remote-fs.target [Mount] What=:/ Where=/srv Type=nfs4 Options=soft,intr,async,nolock,sec=krb5i,proto=tcp $ This is notably lacking any dependency information requiring the network to be up before trying (and failing) to start the unit. Reassigning to systemd. ** Package changed: nfs-utils (Ubuntu) => systemd (Ubuntu) ** Changed in: systemd (Ubuntu) Assignee: (unassigned) => Martin Pitt (pitti) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1429975 Title: nfs no longer mounted at boot with systemd Status in systemd package in Ubuntu: New Bug description: I updated my vivid laptop today, and now boot with systemd by default. Unfortunately, my nfs mount no longer mounts at boot. From syslog: Mar 9 14:38:20 mdlinux mount[866]: mount.nfs: Network is unreachable Mar 9 14:38:20 mdlinux systemd[1]: mnt-server.mount mount process exited, code=exited status=32 Mar 9 14:38:20 mdlinux systemd[1]: Failed to mount /mnt/server. Mar 9 14:38:20 mdlinux systemd[1]: Dependency failed for Remote File Systems. Mar 9 14:38:20 mdlinux systemd[1]: Job remote-fs.target/start failed with result 'dependency'. Mar 9 14:38:20 mdlinux systemd[1]: Unit mnt-server.mount entered failed state. This is happening before my network interfaces are ready: Mar 9 14:38:21 mdlinux NetworkManager[820]: (eth0): preparing device ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: nfs-common 1:1.2.8-9ubuntu6 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportVersion: 2.16.2-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 9 14:45:48 2015 InstallationDate: Installed on 2013-11-26 (467 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: nfs-utils UpgradeStatus: Upgraded to vivid on 2015-03-07 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1429975/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1429975] [NEW] nfs no longer mounted at boot with systemd
You have been subscribed to a public bug: I updated my vivid laptop today, and now boot with systemd by default. Unfortunately, my nfs mount no longer mounts at boot. >From syslog: Mar 9 14:38:20 mdlinux mount[866]: mount.nfs: Network is unreachable Mar 9 14:38:20 mdlinux systemd[1]: mnt-server.mount mount process exited, code=exited status=32 Mar 9 14:38:20 mdlinux systemd[1]: Failed to mount /mnt/server. Mar 9 14:38:20 mdlinux systemd[1]: Dependency failed for Remote File Systems. Mar 9 14:38:20 mdlinux systemd[1]: Job remote-fs.target/start failed with result 'dependency'. Mar 9 14:38:20 mdlinux systemd[1]: Unit mnt-server.mount entered failed state. This is happening before my network interfaces are ready: Mar 9 14:38:21 mdlinux NetworkManager[820]: (eth0): preparing device ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: nfs-common 1:1.2.8-9ubuntu6 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportVersion: 2.16.2-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 9 14:45:48 2015 InstallationDate: Installed on 2013-11-26 (467 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: nfs-utils UpgradeStatus: Upgraded to vivid on 2015-03-07 (2 days ago) ** Affects: systemd (Ubuntu) Importance: Undecided Assignee: Martin Pitt (pitti) Status: New ** Tags: amd64 apport-bug vivid -- nfs no longer mounted at boot with systemd https://bugs.launchpad.net/bugs/1429975 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1214352] Re: [SRU] GUINT32/64_SWAP_LE_BE macros do not enclose val argument in parentheses
Dear LocutusOfBorg! Thank you for your patched packages! This Glib fix is very important, it should be SRUed. I tested your packages with libreoffice packages from PPA (4.4.1~rc2-0ubuntu1~precise1, 4.3.6~rc2-0ubuntu1~precise1). But what is interesting - the bug is not fixed. I can't understand why - you rebuild package, *.so files are new, they would be dynamically linked to other applications. Is is possible to rebuild main "rdepends" too, as mentioned in comment 70 ( https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1214352/comments/70 )? Dear Andreas Heinlein, could you please consult us on the method? Björn Michaelsen have recommended to rebuild all dependencies too ( https://bugs.documentfoundation.org/show_bug.cgi?id=67527#c71 ). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1214352 Title: [SRU] GUINT32/64_SWAP_LE_BE macros do not enclose val argument in parentheses Status in LibreOffice Productivity Suite: Fix Released Status in The "G" Library - GLib: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Status in gvfs package in Ubuntu: New Status in libreoffice package in Ubuntu: New Bug description: [Impact] * This bug affects Glib-dependent packages, one of them is modern version of LibreOffice 4.x from PPA (https://launchpad.net/~libreoffice/+archive/ubuntu/ppa). * LibreOffice is very important software. Modern versions are more functional. Without them Ubuntu is nothing, it is a toy. [Test Case] 1. Place OpenDocument file (for example 'test.odt') on SMB/CIFS server (Samba on GNU/Linux, or from Windows). Make this share available for read-write. 2a.1. Open Nautilus, navigate it to 'smb://server_name/share_name/', wait the share to be mounted with GVFS. 2a.2. Double click on 'test.odt' 2b. Launch terminal and send 'libreoffice smb://server_name/share_name/test.odt' command. 3. Get error message from LibreOffice: "The file 'test.odt' is corrupt and therefore cannot be opened. LibreOffice can try to repair the file. The corruption could be the result of document manipulation or of structural document damage due to data transmission. We recommend that you do not trust the content of the repaired document. Execution of macros is disabled for this document. Should LibreOffice repair the file? Yes No" 4a. If I click 'Yes', the file is opened, but the title of the document is "Untitled 1 (repaired document)", not original name. 4b. If I click 'No', the dialog 'LibreOffice 4.4' is opened with text: The file 'test.odt' could not be repaired and therefore cannot be opened. OK" I click 'OK' here, the next window "LibreOffice 4.4.1.2" is opened with text: "General Error. General input/output error. OK" If I click OK here - no files are opened. While step 3 gvfsd-smb process eats CPU then terminates with error. This error is caused by bug in Glib (wrong type conversion in macros). [Regression Potential] * This functionality is essential. Please fix this bug. I (and you) can't tell Windows users, that they should not open office files from network shares in GNU/Linux. * The patch has two lines (https://git.gnome.org/browse/glib/commit/?id=255c65f83c1515a7e3fc4609b36e72acc08a79e4) and well-tested at upstream. * This bug may cause potential loss of data. [Other Info] * Corresponding links to LibO bugs are: https://bugs.freedesktop.org/show_bug.cgi?id=67527 https://bugs.documentfoundation.org/show_bug.cgi?id=72337 [Original description] On 12.04 LTS precise GUINT32/64_SWAP_LE_BE macros do not enclose val argument in parentheses, causing trouble down the stack in gvfs and LibreOffice (and possibly in lots of obscure bugs elsewhere). There is a patch available, but as this touches the header, it needs a full recompile of rdepends. see: https://lists.fedoraproject.org/pipermail/devel/2013-March/180302.html ff. for details To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1214352/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1429135] Re: webbrowser-app crashed with SIGSEGV in XQueryExtension()
** Also affects: oxide-qt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1429135 Title: webbrowser-app crashed with SIGSEGV in XQueryExtension() Status in oxide-qt package in Ubuntu: New Status in webbrowser-app package in Ubuntu: New Bug description: This occurs when starting the webbrowser app in a Unity 8 desktop session. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: webbrowser-app 0.23+15.04.20150227-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 Date: Thu Mar 5 10:41:06 2015 ExecutablePath: /usr/bin/webbrowser-app InstallationDate: Installed on 2013-03-18 (717 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) ProcCmdline: webbrowser-app ProcEnviron: PATH=(custom, no user) LANGUAGE=en_US XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 11 SourcePackage: webbrowser-app StacktraceTop: XQueryExtension () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XInitExtension () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XextAddDisplay () from /usr/lib/x86_64-linux-gnu/libXext.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0 Title: webbrowser-app crashed with SIGSEGV in XQueryExtension() UpgradeStatus: Upgraded to vivid on 2014-10-20 (136 days ago) UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/oxide-qt/+bug/1429135/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1429938] Re: systemd changes behavior of apt-get remove openssh-server
Also, just to clarify, this is definitely a change (or in my mind regression) introduced by systemd. Yesterday, the System76 image master tool worked fine and dandy with an up-to-date Vivid VM, as it has throughout the rest of the previous Vivid dev cycle. Today things broke. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1429938 Title: systemd changes behavior of apt-get remove openssh-server Status in openssh package in Ubuntu: Confirmed Bug description: On Trusty and Utopic, when you run `apt-get remove openssh-server` over an SSH connection, your existing SSH connection remains open, so it's possible to run additional commands afterward. However, on Vivid now that the switch to systemd has been made, `apt- get remove openssh-server` closes the existing SSH connection immediately, causing your SSH client to exit with a non-zero status. I have a hunch there's a lot of automation tooling out there that relies on the old behavior. For what it's worth, this change breaks the internal image mastering tools that System76 uses. Prior to exporting an image tarball, I spin up a golden VM with qemu, rysnc a script to it, and then execute this script over SSH. The important step is that I need to remove openssh-server prior to shutting down the VM, so these scripts always end with something like this: apt-get -y purge openssh-server ssh-import-id apt-get -y autoremove shutdown -h now As far as I can tell, this behavior change will likewise be a problem when running `do-release-upgrade` on a remote server over SSH. Or more generally, anytime you run "apt-get upgrade/dist-upgrade" via SSH, it seems this would be a problem whenever the openssh-server package happens to be updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1429938/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 50093] Re: Some sysctl's are ignored on boot
*** This bug is a duplicate of bug 771372 *** https://bugs.launchpad.net/bugs/771372 bumping +3 years , still no good solution -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/50093 Title: Some sysctl's are ignored on boot Status in procps package in Ubuntu: Confirmed Bug description: Binary package hint: procps /etc/init.d/procps.sh comes too early in the boot process to apply a lot of sysctl's. As it runs before networking modules are loaded and filesystems are mounted, there are quite a lot of commonly-used sysctl's which are simply ignored on boot and produce errors to the console. Simply renaming the symlink from S17 to > S40 probably isn't a great solution, as there are probably folk who want and expect some sysctl's to be applied before filesystems are mounted and so on. However, simply ugnoring something as important as sysctl settings isn't really on. Administrators expect the settings in /etc/sysctl.conf to take effect. One sto-gap solution would be to run sysctl -p twice; once at S17 and once at S41. There may still be some warnings and errors, but everything would be applied. A different, more complex approach might be to re-architect the sysctl configuration into something like; /etc/sysctl.d/$modulename and have the userland module-loading binaries take care of applying them after modules are loaded. Though this may take care of explicitly loaded modules only, I'm not sure. Incidentally, /etc/sysctl.conf still refers to /etc/networking/options, but hasn't that been deprecated? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/50093/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1430016] Re: qmlplugindump crashed with SIGABRT in oxide::qt::WebViewAdapter::context()
*** This bug is a duplicate of bug 1419616 *** https://bugs.launchpad.net/bugs/1419616 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1419616, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1430016/+attachment/4339240/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1430016/+attachment/4339242/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1430016/+attachment/4339244/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1430016/+attachment/4339245/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1430016/+attachment/4339246/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1430016/+attachment/4339247/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1430016/+attachment/4339248/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1419616 qmlplugindump crashed with SIGABRT in oxide::WebView::GetBrowserContext() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1430016 Title: qmlplugindump crashed with SIGABRT in oxide::qt::WebViewAdapter::context() Status in qtdeclarative-opensource-src package in Ubuntu: New Bug description: I was visiting a website: http://www.online-convert.com/. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: qtdeclarative5-dev-tools 5.4.0-4ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 9 21:38:02 2015 ExecutablePath: /usr/lib/x86_64-linux-gnu/qt5/bin/qmlplugindump InstallationDate: Installed on 2014-02-13 (388 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140211) ProcCmdline: /usr/lib/x86_64-linux-gnu/qt5/bin/qmlplugindump -relocatable com.canonical.Oxide 1.0 /usr/lib/x86_64-linux-gnu/qt5/qml Signal: 6 SourcePackage: qtdeclarative-opensource-src StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0 oxide::qt::WebViewAdapter::context() const () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0 OxideQQuickWebView::~OxideQQuickWebView() () from /usr/lib/x86_64-linux-gnu/libOxideQtQuick.so.0 QQmlPrivate::QQmlElement::~QQmlElement() () from /usr/lib/x86_64-linux-gnu/qt5/qml/com/canonical/Oxide/libqmloxideplugin.so Title: qmlplugindump crashed with SIGABRT in oxide::qt::WebViewAdapter::context() UpgradeStatus: Upgraded to vivid on 2014-05-04 (308 days ago) UserGroups: adm autopilot cdrom dip libvirtd lpadmin minidlna plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1430016/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1318144] Re: Can't edit reviews
** Branch linked: lp:~fgallina/rnr-server/delete-click-review-handler ** Branch linked: lp:~fgallina/rnr-server/exclude-deleted-hidden-click- reviews -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-click in Ubuntu. https://bugs.launchpad.net/bugs/1318144 Title: Can't edit reviews Status in Ratings and Reviews server: Triaged Status in unity-scope-click package in Ubuntu: New Bug description: It seems impossible to edit reviews at the moment. I get the review entry even though I reviewed already and I'm allowed to send another review, which actually gets lost somewhere. I imagine we want to limit the number of reviews to 1 per U1 account, but it should be possible to send a new/modified one. Maybe the review entry should be pre-filled with the previous review so it's obvious you can edit? To manage notifications about this bug go to: https://bugs.launchpad.net/rnr-server/+bug/1318144/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1429415] Re: Unable to enter password in the lock screen after using Qtcreator to run apps on the device
Well I don't know if this bug is not present on krillin or not since I dont have that device. I will try out workaround to see if that works. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1429415 Title: Unable to enter password in the lock screen after using Qtcreator to run apps on the device Status in qtcreator-plugin-ubuntu package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: I have noticed consistently that after upgrading the phone to vivid, while developing apps and running them on the device via Qtcreator, after a few runs, when the device locks (due to timeout, or manual locking) it is no longer possible to unlock the device by typing in the password in the lock screen since when I type the password, the passphrase characters are not typed into the textfield. It is sort of like the lock screen does not take any input. The only way to fix the solution is to reboot the phone since I cannot adb into the device without unlocking it first to do any unity8 reboots. I noticed that I get the following output line on Qtc, Connection to 127.0.0.1 closed by remote host. I tried using 2 other cables and have noticed the connection closed by remote host. But despite the remote host closing the connection, QtC still displays the device status in green indicating it is detected and available. However on trying to run the app again, I get the error "Could not conenct to host: Connection refused. Is the device still connected and set up network access?" This connection is terminated by remote host after few seconds even if I let the app be idle during that time. Steps to reproduce the issue: 1. Connect the phone to the laptop. 2. Open any app in Qtcreator and set it to run the app on the device. 3. Run the app on the device. 4. Close the app on the phone and lock the device. 5. Try unlocking the device. What happens: Device is locked and the lock screen textfield does not accept any input. Pressing on the keypad buttons doesnt do anything Note: The lockscreen issue happens only on vivid. But the connection being terminated by the remote host happens both on vivid and rtm. System Information: Laptop: Ubuntu 14.04.2 LTS Nexus 4(Mako) running vivid img 125 qtcreator-plugin-ubuntu: 3.1.1+15.04.20150224-0ubuntu1~0trusty1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtcreator-plugin-ubuntu/+bug/1429415/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 972077] Re: apt repository disk format has race conditions
I opened bug 1430011 as a request for launchpad to gain the ability to create /populate by-hash mirrors. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/972077 Title: apt repository disk format has race conditions Status in MAAS: New Status in apt package in Ubuntu: Confirmed Bug description: Apt archives are accessed over HTTP; this has resulted in a cluster of bugs (reported here, and upstream) about problems behind intercepting caches, problems with squid etc. There are 3 interlocking issues: A - mirror networks may be out of sync with each other (e.g. a file named on one mirror may no longer exist, or may not yet exist, on another mirror) B - updating files on a single mirror is not atomic - and even small windows of inconsistency will, given enough clients, cause headaches. C - caches exacerbate race conditions - when one happens, until the cached data expires, all clients of the cache will suffer from the race Solving this requires one of several things: - file system transactions - an archive format that requires only weakly ordered updates to the files at particular urls with the assumption that only one file may be observed to change at a time (because a lookup of file A, then B, may get a cache miss on A and a cache hit on B, so even if all clients strictly go A, then B, updates may still see old files when paths are reused). - super robust clients that repeatedly retry with progressively less cache friendly headers until they have a consistent view. (This is very tricky to do). It may be possible to do a tweak to the apt repository format though, which would allow publishing a race-free format in parallel with the existing layout, while clients migrate. To be safe against issue (A) the mirror network would need some care around handling of dns round- robin mirrors [to minimise the situation where referenced data is not available], but this should be doable - or alternatively clients doing 'apt-get update' may need to be willing to retry to accommodate round- robin skew. What would such an archive format look like? It would have only one well known file name (e.g. Releases-2), which would be internally signed. Rather than signing e.g. Packages.gz, it would sign a uniquely named packages and sources file - e.g. Packages-$HASH.gz or Packages-$serialno.gz. Backwards compatibility is achieved by using the same filenames for deb's and the like. We need to keep writing Packages.gz though, and Releases, until we no longer worry about old apt clients. We can optimise disk space a little by making Packages.gz a symlink to a Packages-$HASH.gz (and so on for Sources..), but it may be simpler and less prone to unexpected behaviour to keep using regular files. tl;dr * Unique file names for all unique file content with one exception * Releases-2, a self-signed file that provides hashes and names the index files (Packages, Sources, Translations etc) * Coexists with existing archive layout To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/972077/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1418619] Re: Video stops displaying after doing a lot of seeking
** Changed in: canonical-devices-system-image Importance: Undecided => High ** Changed in: canonical-devices-system-image Status: New => Fix Released ** Changed in: canonical-devices-system-image Milestone: None => ww13-ota -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1418619 Title: Video stops displaying after doing a lot of seeking Status in the base for Ubuntu mobile products: Fix Released Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in gst-plugins-bad1.0 package in Ubuntu RTM: Fix Released Bug description: 1. Open a video with mediaplayer-app from the video scope. 2. Start seeking, slowly, rapidly, back and forth. 3. Observe that eventually, video stops displaying while audio can still be heard. Expected results: 1. Video playback is robust and video always displays no matter how much seeking is done. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1418619/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1417756] Re: mp4 videos recorded with GoPro camera do not play back on krillin
** Changed in: canonical-devices-system-image Importance: Undecided => High ** Changed in: canonical-devices-system-image Status: New => Fix Released ** Changed in: canonical-devices-system-image Milestone: None => ww13-ota -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libhybris in Ubuntu. https://bugs.launchpad.net/bugs/1417756 Title: mp4 videos recorded with GoPro camera do not play back on krillin Status in the base for Ubuntu mobile products: Fix Released Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in libhybris package in Ubuntu: Invalid Status in gst-plugins-bad1.0 package in Ubuntu RTM: Fix Released Bug description: krillin build 224 The attached movie does not play on krillin. There is no error or anything to the user. It plays on mako. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1417756/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1425662] Re: "apt-get download" fails if /var/cache/apt/archives/partial is not accessible
** Tags added: vivid -- 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/1425662 Title: "apt-get download" fails if /var/cache/apt/archives/partial is not accessible Status in APT: Fix Released Status in apt package in Ubuntu: Fix Committed Bug description: I'm using Ubuntu 15.04 dev with apt 1.0.9.3ubuntu1 and if /var/cache/apt/archives/partial is not accessible "apt-get download" doesn't download the requested package. Here are 2 examples (missing directory and insufficient permissions because the user permissions (which are restrictive in this case) got inherited with sudo): sworddragon@ubuntu:~$ sudo rm -fr /var/cache/apt sworddragon@ubuntu:~$ apt-get download nvidia-settings E: Archives directory /var/cache/apt/archives/partial is missing. - Acquire (2: No such file or directory) sworddragon@ubuntu:~$ sudo apt-get download nvidia-settings Get:1 http://archive.ubuntu.com/ubuntu/ vivid/main nvidia-settings amd64 346.35-0ubuntu1 [936 kB] Fetched 936 kB in 2s (392 kB/s) sworddragon@ubuntu:~$ apt-get download nvidia-settings E: Archives directory /var/cache/apt/archives/partial is missing. - Acquire (13: Permission denied) To manage notifications about this bug go to: https://bugs.launchpad.net/apt/+bug/1425662/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1358283] Re: [OOBE] Don't show passcode prompt after 1st step of edge intro
** Changed in: unity8 (Ubuntu RTM) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1358283 Title: [OOBE] Don't show passcode prompt after 1st step of edge intro Status in Ubuntu UX bugs: In Progress Status in unity8 package in Ubuntu: Fix Released Status in unity8 package in Ubuntu RTM: Fix Released Bug description: mako #197 Test Case: 1. Flash a device with --wipe or reset the wizard and the edge-intro, then reboot $ phablet-config welcome-wizard --enable $ phablet-config edges-intro --enable $ adb shell sudo reboot 2. Go through the steps of the wizard and make sure you enter a passcode, then proceed to the edge-intro 3. Go through the steps of the edge-intro until unity8 is displayed Actual Result After the 1st step (right edge gesture) the passcode prompt is displayed, and the intro continues after entering the right passcode Expected Behaviour The passcode is not displayed at all since it is a fresh phone and I entered the passcode a couple of seconds before, or, if the passcode must really be displayed, show it after the edge-intro ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity8 8.00+14.10.20140817-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.5-0ubuntu4 Architecture: armhf Date: Mon Aug 18 13:16:38 2014 InstallationDate: Installed on 2014-08-18 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140818-020205) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1358283/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1383782] Re: [greeter] on n10 swiping from right to left before typing the password/pin opens application spread
I'm betting this no longer happens. ** Changed in: unity8 (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1383782 Title: [greeter] on n10 swiping from right to left before typing the password/pin opens application spread Status in unity8 package in Ubuntu: Incomplete Bug description: Make sure n10 is locked swipe left from the right edge enter the pin error: unity8-dash is shown in the application spread. expected: gestures never bypass the greeter This happens only with the tablet interface on nexus 10, tested with #289. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1383782/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1370644] Re: unity8-autopilot device unlock seems racy
** Changed in: unity8 (Ubuntu) Status: In Progress => Fix Released ** Changed in: unity8 (Ubuntu RTM) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1370644 Title: unity8-autopilot device unlock seems racy Status in unity8 package in Ubuntu: Fix Released Status in unity8 package in Ubuntu RTM: Fix Released Bug description: In some test runs, we see unlocking fail with: I: Unlock failed, script output: 'Error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name com.canonical.UnityGreeter was not provided by any .service files It's not reliably reproducible, but probably happens at least once a day for us in CI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1370644/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1294732] Re: [meet ubuntu] "phone" string in tablet oobe; oobe should have "tablet" or generic term
** Changed in: unity8 (Ubuntu) Status: Invalid => Confirmed ** No longer affects: ubuntu-system-settings (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1294732 Title: [meet ubuntu] "phone" string in tablet oobe; oobe should have "tablet" or generic term Status in Ubuntu UX bugs: Fix Committed Status in unity8 package in Ubuntu: Confirmed Bug description: build r237 the oobe on the tablet (nexus 7) refers to a "phone" it should refer to a "tablet" or a generic like "your device" See also bug 1258211. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1294732/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1382123] Re: [SIM PIN] Very fast PIN entry message displayed before SIM PIN entry dialog
** Changed in: unity8 (Ubuntu) Assignee: Michael Terry (mterry) => Mirco Müller (macslow) ** Changed in: unity8 (Ubuntu RTM) Assignee: Michael Terry (mterry) => Mirco Müller (macslow) -- 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/1382123 Title: [SIM PIN] Very fast PIN entry message displayed before SIM PIN entry dialog Status in indicator-network package in Ubuntu: Invalid Status in ubuntu-system-settings package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Confirmed Status in unity8 package in Ubuntu RTM: New Bug description: 14.09-proposed image #109 STEPS: 1. Ensure at least 1 SIM inserted with PIN lock 2. Boot up 3. Just before SIM 1 PIN entry, a white message will very quickly flash on the screen for approx 0.1 second: 'Enter SIM 1 PIN' 4. The SIM 1 PIN entry dialog will then be correctly displayed This will also happen for SIM 2 as well. EXPECTED RESULT: The very brief message should not be displayed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1382123/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1419405] Re: indicator-location-service crashed with SIGABRT in internal::ToBackend::exit_module()
This bug was fixed in the package unity8-desktop-session - 1.0.12+15.04.20150306-0ubuntu1 --- unity8-desktop-session (1.0.12+15.04.20150306-0ubuntu1) vivid; urgency=medium [ Iain Lane ] * Export the platform API backend, required for example for the location service (LP: #1419405) -- CI Train BotFri, 06 Mar 2015 14:30:25 + ** Changed in: unity8-desktop-session (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-location in Ubuntu. https://bugs.launchpad.net/bugs/1419405 Title: indicator-location-service crashed with SIGABRT in internal::ToBackend::exit_module() Status in indicator-location package in Ubuntu: Confirmed Status in platform-api package in Ubuntu: Confirmed Status in unity8-desktop-session package in Ubuntu: Fix Released Bug description: :( ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: indicator-location 13.10.0+14.10.20141007-0ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-12.13-generic 3.18.4 Uname: Linux 3.18.0-12-generic x86_64 ApportVersion: 2.16-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Thu Feb 5 06:11:38 2015 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-location/indicator-location-service InstallationDate: Installed on 2014-10-13 (117 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141012) ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-location/indicator-location-service ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/false Signal: 6 SourcePackage: indicator-location StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libubuntu_application_api.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libubuntu_application_api.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libubuntu_application_api.so.2 ua_location_service_create_controller () from /usr/lib/x86_64-linux-gnu/libubuntu_application_api.so.2 UbuntuAppLocController::UbuntuAppLocController() () SystemImageInfo: current build number: 0 device name: channel: daily last update: Unknown Title: indicator-location-service crashed with SIGABRT in ua_location_service_create_controller() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-location/+bug/1419405/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1404468] Re: German neo2 keyboard layout: no ALT and SUPER keys
This seems to also affect F12. F12 is the default Yakuake shortcut: it works when called to manually assign the shortcut, but does not work as global shortcut to open Yakuake when called from elsewhere. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1404468 Title: German neo2 keyboard layout: no ALT and SUPER keys Status in xkeyboard-config package in Ubuntu: Confirmed Bug description: Affected version: Ubuntu 14.04. When switching to the Neo 2 keyboard layout, I cannot use the ALT or SUPER keys at all. To reproduce this bug, do the following: - In the keyboard system tray menu, select "Text Entry" - Click "+" - Select: "Germany (Neo 2)" - Close the "Text Entry" configuration - In the keyboard system tray menu, (temporarily) select "Germany (Neo 2)" as active layout. Now, shortcuts like +, +, ... are no longer working. The same goes for the shortcuts I tried with . Switching to Neo2 by "setxkbmap de neo" has the same result. For sake of completeness: There are other bug reports regarding Neo2, reporting that Layer4 (Mod4) is not working. In my case, Mod4 seems to be working fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1404468/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1429988] Re: Preview and photos are unfocused
** Description changed: - BQ aquarius running stable rtm + BQ Aquarius running stable rtm - The camera ca get in a state where it can no longer properly focus on the image. The preview shows a fuzyy image which is also the case with the pictures taken. + The camera can get in a state where it can no longer properly focus on the image. The preview shows a fuzzy image which is also the case with the pictures taken. Rebooting the phone does not correct this. (this was reproduced once by switching front and back cameras but it corrected with another switch) -- 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/1429988 Title: Preview and photos are unfocused Status in camera-app package in Ubuntu: Confirmed Bug description: BQ Aquarius running stable rtm The camera can get in a state where it can no longer properly focus on the image. The preview shows a fuzzy image which is also the case with the pictures taken. Rebooting the phone does not correct this. (this was reproduced once by switching front and back cameras but it corrected with another switch) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1429988/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1414762] Re: Password gets set instead of a passcode during welcome wizard
** Changed in: canonical-devices-system-image Milestone: ww11-2015 => ww13-ota ** Changed in: canonical-devices-system-image Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1414762 Title: Password gets set instead of a passcode during welcome wizard Status in the base for Ubuntu mobile products: Fix Released Status in unity8 package in Ubuntu: Fix Released Status in ubuntu-system-settings package in Ubuntu RTM: In Progress Bug description: Whenever I quickly type the passcode during setup wizard, instead of passcode, password is set as security mechanism 1. factory reset your phone 2. on the startup wizard select 4-digit passcode as security mechanism 3. when asked to confirm the passcode, quickly type it again. 4. finish setup What happens: Instead of a passcode the password is set and I am greeted with OSK to unlock the screen. ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: ubuntu-system-settings 0.3+15.04.20150123.1~rtm-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Mon Jan 26 19:41:20 2015 InstallationDate: Installed on 2015-01-26 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20150126-162525) SourcePackage: ubuntu-system-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1414762/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1419405] Re: indicator-location-service crashed with SIGABRT in internal::ToBackend::exit_module()
** Branch linked: lp:~ubuntu-branches/ubuntu/vivid/unity8-desktop- session/vivid-proposed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-location in Ubuntu. https://bugs.launchpad.net/bugs/1419405 Title: indicator-location-service crashed with SIGABRT in internal::ToBackend::exit_module() Status in indicator-location package in Ubuntu: Confirmed Status in platform-api package in Ubuntu: Confirmed Status in unity8-desktop-session package in Ubuntu: In Progress Bug description: :( ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: indicator-location 13.10.0+14.10.20141007-0ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-12.13-generic 3.18.4 Uname: Linux 3.18.0-12-generic x86_64 ApportVersion: 2.16-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Thu Feb 5 06:11:38 2015 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-location/indicator-location-service InstallationDate: Installed on 2014-10-13 (117 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141012) ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-location/indicator-location-service ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/false Signal: 6 SourcePackage: indicator-location StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libubuntu_application_api.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libubuntu_application_api.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libubuntu_application_api.so.2 ua_location_service_create_controller () from /usr/lib/x86_64-linux-gnu/libubuntu_application_api.so.2 UbuntuAppLocController::UbuntuAppLocController() () SystemImageInfo: current build number: 0 device name: channel: daily last update: Unknown Title: indicator-location-service crashed with SIGABRT in ua_location_service_create_controller() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-location/+bug/1419405/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1404468] Re: German neo2 keyboard layout: no ALT and SUPER keys
Exact same behavior here: neo with Ubuntu Gnome 14.04, ALT and SUPER do not work, Mod4 does. This renders Ubuntu Gnome 14.04 unusable for neo users. Does anybody know a workaround? Logging out and in again does not fix the problem for me (same behavior). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1404468 Title: German neo2 keyboard layout: no ALT and SUPER keys Status in xkeyboard-config package in Ubuntu: Confirmed Bug description: Affected version: Ubuntu 14.04. When switching to the Neo 2 keyboard layout, I cannot use the ALT or SUPER keys at all. To reproduce this bug, do the following: - In the keyboard system tray menu, select "Text Entry" - Click "+" - Select: "Germany (Neo 2)" - Close the "Text Entry" configuration - In the keyboard system tray menu, (temporarily) select "Germany (Neo 2)" as active layout. Now, shortcuts like +, +, ... are no longer working. The same goes for the shortcuts I tried with . Switching to Neo2 by "setxkbmap de neo" has the same result. For sake of completeness: There are other bug reports regarding Neo2, reporting that Layer4 (Mod4) is not working. In my case, Mod4 seems to be working fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1404468/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1429988] [NEW] Preview and photos are unfocused
Public bug reported: BQ aquarius running stable rtm The camera ca get in a state where it can no longer properly focus on the image. The preview shows a fuzyy image which is also the case with the pictures taken. Rebooting the phone does not correct this. (this was reproduced once by switching front and back cameras but it corrected with another switch) ** Affects: camera-app (Ubuntu) Importance: Critical Assignee: Florian Boucault (fboucault) Status: Confirmed -- 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/1429988 Title: Preview and photos are unfocused Status in camera-app package in Ubuntu: Confirmed Bug description: BQ aquarius running stable rtm The camera ca get in a state where it can no longer properly focus on the image. The preview shows a fuzyy image which is also the case with the pictures taken. Rebooting the phone does not correct this. (this was reproduced once by switching front and back cameras but it corrected with another switch) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1429988/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1429988] Re: Preview and photos are unfocused
@jon could you attach the camera logs from the camera that is in this state -- 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/1429988 Title: Preview and photos are unfocused Status in camera-app package in Ubuntu: Confirmed Bug description: BQ aquarius running stable rtm The camera ca get in a state where it can no longer properly focus on the image. The preview shows a fuzyy image which is also the case with the pictures taken. Rebooting the phone does not correct this. (this was reproduced once by switching front and back cameras but it corrected with another switch) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1429988/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1404468] Re: German neo2 keyboard layout: no ALT and SUPER keys
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xkeyboard-config (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1404468 Title: German neo2 keyboard layout: no ALT and SUPER keys Status in xkeyboard-config package in Ubuntu: Confirmed Bug description: Affected version: Ubuntu 14.04. When switching to the Neo 2 keyboard layout, I cannot use the ALT or SUPER keys at all. To reproduce this bug, do the following: - In the keyboard system tray menu, select "Text Entry" - Click "+" - Select: "Germany (Neo 2)" - Close the "Text Entry" configuration - In the keyboard system tray menu, (temporarily) select "Germany (Neo 2)" as active layout. Now, shortcuts like +, +, ... are no longer working. The same goes for the shortcuts I tried with . Switching to Neo2 by "setxkbmap de neo" has the same result. For sake of completeness: There are other bug reports regarding Neo2, reporting that Layer4 (Mod4) is not working. In my case, Mod4 seems to be working fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1404468/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1427710] Re: A maliit-framework segfault with Qt 5.4.1
Looks like this was caused by the QML cache not having been cleared. This normally happens during image upgrades, but since the Qt 5.4.1 upgrade is just done via apt-get this doesn't happen. The crashes stop as soon as you delete ~/.cache/QML/Apps/maliit-server (or alternatively if you delete this before restarting after the upgrade the crash never happens). For completeness you probably actually want to delete the whole ~/.cache/QML/Apps directory when testing this silo or you might hit similar problems in other apps. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to maliit-framework in Ubuntu. https://bugs.launchpad.net/bugs/1427710 Title: A maliit-framework segfault with Qt 5.4.1 Status in maliit-framework package in Ubuntu: New Bug description: Crashing at QV4::ExecutionContext::setProperty() See https://wiki.ubuntu.com/Touch/QtTesting for information on how to upgrade to silo 012 with Qt 5.4.1. All necessary Qt private headers users _should_ be rebuilt, per the latest knowledge. However, compared to 5.3.2 -> 5.4.0 transition, the following packages were found not to depend on qtbase-abi-5-4-0 / qtdeclarative-abi-5-4-0 so not rebuilt this time: oxide-qt qtubuntu- sensors qtvideo-node webbrowser-app ubuntu-html5-theme ubuntu-system- settings-online-accounts (some are recent known dropouts, some may have been without private symbol usage also during 5.3.0 -> 5.3.2 transition). If in doubt, https://launchpad.net/~canonical- qt5-edgers/+archive/qt5-beta2/+packages has rebuilds of a lot of packages for the new testing reasons (unit tests get run etc). All Qt 5.4.1 bugs https://bugs.launchpad.net/bugs/+bugs?field.tag=qt5.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maliit-framework/+bug/1427710/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1405277] Re: screen flicker in ubuntu 14.04.1 and derivatives
1. i installed a brandnew 'crucial ssd' on this 'toshiba satelite A215-S4697' - hoping that disk speed would solve the problem 2. first distro installed was 'zorin 9 lite'3. the original installation did not flicker: kernel 3.13.32 (??)4. the updated kernel version flickered badly: kernel 3.13.46 'zorin' is based on 'ubuntu 14.04 xfce' On Friday, February 27, 2015 2:01 PM, jwm hogenboom wrote: 1. the same still holds for all ubuntu 14.04.2 - and all of its derivatives2. the flickering does not exist in the very first - and original - kernel of ubuntu 14.043. the flickering does not exist in 'linux mint 17.0' - since 'mint' does not change kernels, the way ubuntu does On Monday, February 23, 2015 5:20 PM, Christopher M. Penalver wrote: hansie, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com /daily-live/current/ . If it remains an issue, could you please run the following command in the development release from a Terminal as it will automatically gather and attach updated debug information to this report: apport-collect -p xorg 1405277 Please ensure you have xdiagnose installed, and that you click the Yes button for attaching additional debugging information. As well, given the information from the prior release is already available, testing a release prior to the development one would not be helpful. Thank you for your understanding. Helpful bug reporting tips: https://wiki.ubuntu.com/ReportingBugs ** Changed in: xorg (Ubuntu) Importance: Undecided => Low ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are subscribed to the bug report. 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 -- 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 1419061] Re: On Ubuntu Kylin detect all packages as not genuine
Yes!! I've manually edited the /etc/os-release file deleting kylin and it works. Thanks and best regards ** Description changed: Hallo In Vivid if I run apport-bug (pkg) it always return that is not a genuine package: The problem cannot be reported: This is not an official Ubuntu package. Please remove any third party package and try again. see attached screenshot. Set as critical because it represent a loss of informations in a test environement ( eg: a medium user feel discouraged to report a bug) Thanks Fabio P.S.: - This start happening after apport upgrades and NOT runing a fresh installation + This start happening after apport's upgrades and NOT runing a fresh installation. + + - WORKAROUND at #20 --- ApportLog: ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu Kylin 14.10 InstallationDate: Installed on 2014-08-12 (184 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) Package: apport 2.16.1-0ubuntu2 [origin: Ubuntu] PackageArchitecture: all ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Tags: third-party-packages vivid Uname: Linux 3.18.0-13-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: Upgraded to vivid on 2015-01-10 (33 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CrashReports: 640:1000:120:72115:2015-03-05 10:38:22.031167507 +0100:2015-03-06 10:30:38.543396523 +0100:/var/crash/_usr_bin_sogou-qimpanel.1000.crash 644:0:120:0:2015-03-06 10:24:01.613003795 +0100:2015-03-06 10:30:17.487292102 +0100:/var/crash/_usr_lib_x86_64-linux-gnu_indicator-sound_indicator-sound-service.108.upload 640:110:120:4951702:2015-03-06 18:50:04.986461639 +0100:2015-03-06 18:50:05.986461639 +0100:/var/crash/_usr_share_apport_apport-gtk.110.crash 640:108:120:306702:2015-03-06 10:22:15.169228553 +0100:2015-03-06 10:24:02.636496873 +0100:/var/crash/_usr_lib_x86_64-linux-gnu_indicator-sound_indicator-sound-service.108.crash 600:110:120:0:2015-03-06 10:24:21.091356436 +0100:2015-02-24 22:14:44.551599595 +0100:/var/crash/_usr_lib_x86_64-linux-gnu_indicator-sound_indicator-sound-service.108.uploaded CurrentDesktop: Unity DistroRelease: Ubuntu Kylin 15.04 EcryptfsInUse: Yes InstallationDate: Installed on 2015-02-24 (9 days ago) InstallationMedia: Ubuntu-Kylin 15.04 "Vivid Vervet" - Alpha amd64 (20150224) Package: apport 2.16.2-0ubuntu1 [origin: Ubuntu] PackageArchitecture: all Tags: third-party-packages vivid Uname: Linux 4.0.0-04rc2-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1419061 Title: On Ubuntu Kylin detect all packages as not genuine Status in Ubuntu Kylin: Triaged Status in apport package in Ubuntu: Triaged Bug description: Hallo In Vivid if I run apport-bug (pkg) it always return that is not a genuine package: The problem cannot be reported: This is not an official Ubuntu package. Please remove any third party package and try again. see attached screenshot. Set as critical because it represent a loss of informations in a test environement ( eg: a medium user feel discouraged to report a bug) Thanks Fabio P.S.: This start happening after apport's upgrades and NOT runing a fresh installation. - WORKAROUND at #20 --- ApportLog: ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu Kylin 14.10 InstallationDate: Installed on 2014-08-12 (184 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) Package: apport 2.16.1-0ubuntu2 [origin: Ubuntu] PackageArchitecture: all ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Tags: third-party-packages vivid Uname: Linux 3.18.0-13-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: Upgraded to vivid on 2015-01-10 (33 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CrashReports: 640:1000:120:72115:2015-03-05 10:38:22.031167507 +0100:2015-03-06 10:30:38.543396523 +0100:/var/crash/_usr_bin_sogou-qimpanel.1000.crash 644:0:120:0:2015-03-06 10:24:01.613003795 +0100:2015-03-06 10:30:17.487292102 +0100:/var/crash/_usr_lib_x
[Touch-packages] [Bug 1227149] Re: USB audio sound card not recognized after update to Linux 3.12-rc1-saucy
I have a usb audio device that i was using regularly and suddenly stopped being recognized. The system can't even identify its ID's anymore (ID :fffe). -- 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/1227149 Title: USB audio sound card not recognized after update to Linux 3.12-rc1-saucy Status in alsa-driver package in Ubuntu: Confirmed Bug description: Not sure where this report should go, I think it concerns the Linux kernel 3.12-rc1-saucy from http://kernel.ubuntu.com/~kernel- ppa/mainline/ After installing above mentioned kernel (switching from 3.11.1) I can no longer use my USB sound card. (It is an external D/A converter and speaker amplifier.) The sound settings dialog only lists "Dummy Output". (My onboard soundcard is disabled in BIOS.) Dmesg: usb 1-1.1.2: new full-speed USB device number 13 using ehci-pci usb 1-1.1.2: New USB device found, idVendor=08bb, idProduct=2706 usb 1-1.1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 usb 1-1.1.2: Product: USB Audio DAC usb 1-1.1.2: Manufacturer: Burr-Brown from TI input: Burr-Brown from TI USB Audio DACas /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.2/input/input9 hid-generic 0003:08BB:2706.0007: input,hidraw4: USB HID v1.00 Device [Burr-Brown from TI USB Audio DAC ] on usb-:00:1a.0-1.1.2/input2 snd_usb_audio: `-2' invalid for parameter `index' and /etc/modprobe.d/alsa-base.conf indeed does have this line: options snd-usb-audio index=-2 The kernel apparently sees my USB amplifier, but it is not listed in the Sound settings, even though there is no other sound device present. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 Uname: Linux 3.12.0-031200rc1-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed Sep 18 15:14:53 2013 InstallationDate: Installed on 2012-11-02 (319 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MarkForUpload: True PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: USB sound card not detected UpgradeStatus: Upgraded to raring on 2013-09-01 (16 days ago) dmi.bios.date: 08/22/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F14 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77X-UD5H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF14:bd08/22/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77X-UD5H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1227149/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 991481] Re: Constant dns traffic for daisy.ubuntu.com
Yes. I've discussed this with Evan Dandrea a few times in the past, the right way to fix this is by enabling connectivity checking in NetworkManager itself, which can be done with a simple configuration file change in /etc/NetworkManager/NetworkManager.conf (see manual for NetworkManager). The idea is to point it to a file under start.ubuntu.com which can be polled regularly by NM when connected (every five minutes by default, but this is configurable). In the past, there has been some pushback on enabling this due to privacy concerns and concerns that the connectivity checking wasn't configurable/reliable enough. It will need to be investigated again, and discussed again on ubuntu-devel@ or somewhere else suitable for broader discussion. I'm not planning on touching this again in the very near future, so unassigning -- please, anyone want to shepherd this to be completed, feel free to assign it to yourself and start up the dicussion again to see if we can enable connectivity checking. This may be useful for Ubuntu Touch as well. ** Changed in: network-manager (Ubuntu) Assignee: Mathieu Trudel-Lapierre (mathieu-tl) => (unassigned) ** Changed in: network-manager (Ubuntu) Status: In Progress => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/991481 Title: Constant dns traffic for daisy.ubuntu.com Status in Ubuntu error tracker client (whoopsie): Confirmed Status in glib2.0 package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Triaged Status in whoopsie package in Ubuntu: Triaged Bug description: Watching GNetworkMonitor's network-changed signal causes constant DNS traffic. Andy Whitcroft points out that the NETLINK_ROUTE socket set up by GNetworkMonitor will fire events every time an ARP entry appears or disappears. Unfortunately, we currently need an additional layer of connectivity checking because checking NetworkManager's state for CONNECTED_GLOBAL is not enough to know whether we're really online. Ubuntu does not yet use the NetworkManager connectivity check [1]. The likely solution to this bug is a replacement for GNetworkMonitor in whoopsie. 1: http://bazaar.launchpad.net/~daisy- pluckers/whoopsie/trunk/view/head:/src/connectivity.c#L326 Original report follows: Every few seconds, I see a dns query for daisy.ubuntu.com. After removing whoopsie, the traffic goes away. To manage notifications about this bug go to: https://bugs.launchpad.net/whoopsie/+bug/991481/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1429963] [NEW] package shared-mime-info 1.3-1 failed to install/upgrade: зацикливание триггеров, отмена работы
Public bug reported: cant complete apt-get upgrade ProblemType: Package DistroRelease: Ubuntu 15.04 Package: shared-mime-info 1.3-1 ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Uname: Linux 3.18.0-13-generic x86_64 ApportVersion: 2.16.2-0ubuntu2 Architecture: amd64 Date: Mon Mar 9 21:28:18 2015 ErrorMessage: зацикливание триггеров, отмена работы InstallationDate: Installed on 2015-02-16 (20 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150215) SourcePackage: shared-mime-info Title: package shared-mime-info 1.3-1 failed to install/upgrade: зацикливание триггеров, отмена работы UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: shared-mime-info (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1429963 Title: package shared-mime-info 1.3-1 failed to install/upgrade: зацикливание триггеров, отмена работы Status in shared-mime-info package in Ubuntu: New Bug description: cant complete apt-get upgrade ProblemType: Package DistroRelease: Ubuntu 15.04 Package: shared-mime-info 1.3-1 ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Uname: Linux 3.18.0-13-generic x86_64 ApportVersion: 2.16.2-0ubuntu2 Architecture: amd64 Date: Mon Mar 9 21:28:18 2015 ErrorMessage: зацикливание триггеров, отмена работы InstallationDate: Installed on 2015-02-16 (20 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150215) SourcePackage: shared-mime-info Title: package shared-mime-info 1.3-1 failed to install/upgrade: зацикливание триггеров, отмена работы UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1429963/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1162781] Re: bluez package out of date, 5.23 is available in debian sid/jessie
Yes, the BlueZ 5 migration is still being "worked on", and targetted for Vivid. PulseAudio 6 was part of the issue, but wasn't the only thing blocking the migration. There are many pieces that need to be updated or confirmed to work (blueman, indicator-blueooth, gnome-bluetooth, to name a few). The blueprint linked above will get updated as work gets done. There is also coordination that needs to happen with the Ubuntu Touch teams to not interfere with their releases. Unassigning myself, given that I'm not the only person working on this. ** Changed in: bluez (Ubuntu) Assignee: Mathieu Trudel-Lapierre (mathieu-tl) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1162781 Title: bluez package out of date, 5.23 is available in debian sid/jessie Status in bluez package in Ubuntu: Triaged Bug description: Looks like there have been a lot of improvements to bluez since the 4.x series. Would be nice to get the latest release pulled in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1162781/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1104552] Re: Tests not running under pbuilder
Why is this assigned to me? Do we know if the tests are still not being run or if I need to make changes to the build for this somehow? ** Changed in: libindicator (Ubuntu) Assignee: Mathieu Trudel-Lapierre (mathieu-tl) => (unassigned) ** Changed in: libindicator Assignee: Mathieu Trudel-Lapierre (mathieu-tl) => (unassigned) ** Changed in: libindicator (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libindicator in Ubuntu. https://bugs.launchpad.net/bugs/1104552 Title: Tests not running under pbuilder Status in Libindicator: New Status in libindicator package in Ubuntu: Incomplete Bug description: Have just discovered that our pbuilder build in Jenkins isn't running the tests, need to fix in order to report concurrent improvements in coverage :) . To manage notifications about this bug go to: https://bugs.launchpad.net/libindicator/+bug/1104552/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1177424] Re: [Touch] no permission to access bluez on dbus
There are no changes required to bluez for pulseaudio support, things already work on the desktop. Furthermore, given that we've since had multiple reports of bluetooth headsets working properly on Touch, I'll close this as Invalid -- it probably didn't work before, but it works now, even if we don't know what was the difference. ** Changed in: bluez (Ubuntu) Assignee: Mathieu Trudel-Lapierre (mathieu-tl) => (unassigned) ** Changed in: bluez (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1177424 Title: [Touch] no permission to access bluez on dbus Status in bluez package in Ubuntu: Invalid Bug description: I'm trying today's touch preview image, trying to get bluetooth headsets working. After installing the package (see bug 1177421 ), PulseAudio gets the following error message: bluetooth-util.c: org.bluez.Manager.GetProperties() failed: org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 2 matched rules; type="method_call", sender=":1.3" (uid=32011 pid=260 comm="pulseaudio --start --log-target=syslog ") interface="org.bluez.Manager" member="GetProperties" error name="(unset)" requested_reply="0" destination="org.bluez" (uid=0 pid=99 comm="/usr/sbin/bluetoothd ") ...it looks like there is some permission error as pulseaudio is not allowed to talk to the bluez daemon over D-Bus. As a result, pulseaudio does not detect the headset. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1177424/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1292605] Re: Fix wrong IP6 addresses in dispatcher script environment
This is fixed in vivid now, by way of 0.9.10.0. Should we also work on a SRU to utopic? -- 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/1292605 Title: Fix wrong IP6 addresses in dispatcher script environment Status in network-manager package in Ubuntu: Fix Released Bug description: Hi Mathieu, Please include this upstream patch for Network Manager 0.9.8.8 in Trusty to fix wrong IP6 addresses in dispatcher script environment: http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?h=nm-0-9-8&id=3655e07f79c2b5fdb99fde6d4b9b185fd84cf11f The upstream bug is: https://bugzilla.gnome.org/show_bug.cgi?id=701819 Best, Michael To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1292605/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1297301] Re: Phone shows in rhythmbox but display unknown on all tracks
** Changed in: mtp (Ubuntu) Assignee: Mathieu Trudel-Lapierre (mathieu-tl) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mtp in Ubuntu. https://bugs.launchpad.net/bugs/1297301 Title: Phone shows in rhythmbox but display unknown on all tracks Status in mtp package in Ubuntu: Triaged Bug description: 1. Plug the phone into the pc 2. Open rhythmbox 3. Click on the nexus 4 under devices 4. Note all the tracks show up with Unknown for all sections. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: mtp-server 0.0.2+14.04.20140307-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.13.3-0ubuntu1 Architecture: armhf Date: Tue Mar 25 12:40:20 2014 InstallationDate: Installed on 2014-03-25 (0 days ago) InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20140325) ProcEnviron: TERM=linux PATH=(custom, no user) SourcePackage: mtp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mtp/+bug/1297301/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1292605] Re: Fix wrong IP6 addresses in dispatcher script environment
Or trusty... ** Changed in: network-manager (Ubuntu) Status: Triaged => Fix Released -- 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/1292605 Title: Fix wrong IP6 addresses in dispatcher script environment Status in network-manager package in Ubuntu: Fix Released Bug description: Hi Mathieu, Please include this upstream patch for Network Manager 0.9.8.8 in Trusty to fix wrong IP6 addresses in dispatcher script environment: http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?h=nm-0-9-8&id=3655e07f79c2b5fdb99fde6d4b9b185fd84cf11f The upstream bug is: https://bugzilla.gnome.org/show_bug.cgi?id=701819 Best, Michael To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1292605/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
