[Touch-packages] [Bug 1332114] Re: Please update mawk to latest upstream release - mawk in Ubuntu is 16 years old!
** Description changed: - mawk in Ubuntu is 15 years old and very buggy (see + mawk in Ubuntu is 18 years old and very buggy (see https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=mawk and https://bugs.launchpad.net/ubuntu/+source/mawk , also bugs in other products, like bug #1331381) :( Almost all bugs, reported in Ubuntu and Debian are fixed in 1.3.4- upstream releases, see http://invisible-island.net/mawk/CHANGES.html Please update mawk to latest upstream release - all the other major distributions (Fedora/Redhat, Suse, even FreeBSD) have switched to mawk - 1.3.4-2013. Five years since the bug asking to upload new mawk in + 1.3.4-2014. Five years since the bug asking to upload new mawk in Debian didn't change anything, so, I'm reporting bug in Ubuntu - sticking to 1.3.3 is now causing headeach to lots of people rather than - saving from regressions :( + saving from regressions, see for example bug #1005077 :( - Please, update mawk package in Ubuntu 14.10. + Please, update mawk package before major Ubuntu 16.04 LTS release. ** Summary changed: - Please update mawk to latest upstream release - mawk in Ubuntu is 16 years old! + Please update mawk to latest upstream release - mawk in Ubuntu is 18 years old! ** Tags added: trusty wily xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mawk in Ubuntu. https://bugs.launchpad.net/bugs/1332114 Title: Please update mawk to latest upstream release - mawk in Ubuntu is 18 years old! Status in mawk package in Ubuntu: Triaged Status in mawk package in Debian: New Bug description: mawk in Ubuntu is 18 years old and very buggy (see https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=mawk and https://bugs.launchpad.net/ubuntu/+source/mawk , also bugs in other products, like bug #1331381) :( Almost all bugs, reported in Ubuntu and Debian are fixed in 1.3.4- upstream releases, see http://invisible-island.net/mawk/CHANGES.html Please update mawk to latest upstream release - all the other major distributions (Fedora/Redhat, Suse, even FreeBSD) have switched to mawk 1.3.4-2014. Five years since the bug asking to upload new mawk in Debian didn't change anything, so, I'm reporting bug in Ubuntu - sticking to 1.3.3 is now causing headeach to lots of people rather than saving from regressions, see for example bug #1005077 :( Please, update mawk package before major Ubuntu 16.04 LTS release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mawk/+bug/1332114/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1332114] Re: Please update mawk to latest upstream release - mawk in Ubuntu is 16 years old!
** Summary changed: - Please update mawk to latest upstream release + Please update mawk to latest upstream release - mawk in Ubuntu is 16 years old! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mawk in Ubuntu. https://bugs.launchpad.net/bugs/1332114 Title: Please update mawk to latest upstream release - mawk in Ubuntu is 16 years old! Status in mawk package in Ubuntu: Triaged Status in mawk package in Debian: New Bug description: mawk in Ubuntu is 15 years old and very buggy (see https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=mawk and https://bugs.launchpad.net/ubuntu/+source/mawk , also bugs in other products, like bug #1331381) :( Almost all bugs, reported in Ubuntu and Debian are fixed in 1.3.4- upstream releases, see http://invisible-island.net/mawk/CHANGES.html Please update mawk to latest upstream release - all the other major distributions (Fedora/Redhat, Suse, even FreeBSD) have switched to mawk 1.3.4-2013. Five years since the bug asking to upload new mawk in Debian didn't change anything, so, I'm reporting bug in Ubuntu - sticking to 1.3.3 is now causing headeach to lots of people rather than saving from regressions :( Please, update mawk package in Ubuntu 14.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mawk/+bug/1332114/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1295247] Re: Cheese says "There was an error playing video from webcam"
FWIW I just downloaded all the dependencies and compiled Cheese from https://github.com/GNOME/cheese in Ubuntu 15.10 it fails with the same error: libv4l2: error got 4 consecutive frame decode errors, last error: v4l- convert: libjpeg error: End Of Image -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libjpeg-turbo in Ubuntu. https://bugs.launchpad.net/bugs/1295247 Title: Cheese says "There was an error playing video from webcam" Status in cheese package in Ubuntu: Confirmed Status in libjpeg-turbo package in Ubuntu: Confirmed Bug description: Whenever I open Cheese in Ubuntu 14.04 beta 1 (Unity), my webcam's light once turns on, then it turns off and Cheese turns black, written "There was an error playing video from webcam". This never happened in any previous versions of Ubuntu. The problem is reproducible. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: cheese 3.10.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4 Uname: Linux 3.13.0-12-generic i686 ApportVersion: 2.13.2-0ubuntu5 Architecture: i386 CurrentDesktop: Unity Date: Thu Mar 20 22:29:57 2014 InstallationDate: Installed on 2014-03-20 (0 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20140225) SourcePackage: cheese UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1295247/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1515551] Re: Several laptops unstable with 15.10 kernels
+1 on a ThinkPad T430s with Intel graphics. Mostly random freezes and random crashes of Xorg. First I thought it was a problem introduced with upgrading (14.10 -> 15.04 -> 15.10), so I performed a clean install, to no avail. Have been reluctant to downgrade so far. (Interestingly, I just now managed to crash the X server three times in a row by clicking on the 'Edit' button in the 'Shutter' screenshot application. Don't know if that is technically related.) When I mentioned it on the [forums][1], there was one other user who had a similar problem, so that makes us 3. [1]: http://ubuntuforums.org/showthread.php?t=2301373 -- 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/1515551 Title: Several laptops unstable with 15.10 kernels Status in xorg package in Ubuntu: Confirmed Bug description: After upgrading my two laptops (HP EliteBook 8470p, Sony Vaio, both several years old) to 15.10 both started freezing within 12 hours of booting and the screens started flickering when X did fade-out and fade-ins. Booting the HP with the 15.04 kernel (3.19.0-31) makes it stable again. The sony vaoi was downgraded to 14.04 and is stable there. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7 Uname: Linux 3.19.0-31-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 CurrentDesktop: KDE Date: Thu Nov 12 11:34:25 2015 InstallationDate: Installed on 2013-11-07 (734 days ago) InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to wily on 2015-10-26 (16 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1515551/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1515551] Re: Several laptops unstable with 15.10 kernels
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (Ubuntu) Status: New => Confirmed -- 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/1515551 Title: Several laptops unstable with 15.10 kernels Status in xorg package in Ubuntu: Confirmed Bug description: After upgrading my two laptops (HP EliteBook 8470p, Sony Vaio, both several years old) to 15.10 both started freezing within 12 hours of booting and the screens started flickering when X did fade-out and fade-ins. Booting the HP with the 15.04 kernel (3.19.0-31) makes it stable again. The sony vaoi was downgraded to 14.04 and is stable there. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7 Uname: Linux 3.19.0-31-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 CurrentDesktop: KDE Date: Thu Nov 12 11:34:25 2015 InstallationDate: Installed on 2013-11-07 (734 days ago) InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to wily on 2015-10-26 (16 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1515551/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1492767] Re: gdk-pixbuf packages update breaks the GUI in Trusty 14.04.3
Same as above but I didn't run 'sudo gdk-pixbuf-query-loaders > /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache '. The error occurred during the first update on a fresh installation of / but /home is from a previous install of 14.04.3. Reinstalling it using gdebi after downloading it from here http://security.ubuntu.com/ubuntu/pool/main/g/gdk-pixbuf/libgdk- pixbuf2.0-0_2.30.7-0ubuntu1.2_amd64.deb seemed to work fine although it said it was already installed. (Reading database ... 195169 files and directories currently installed.) Preparing to unpack .../libgdk-pixbuf2.0-0_2.30.7-0ubuntu1.2_amd64.deb ... Unpacking libgdk-pixbuf2.0-0:amd64 (2.30.7-0ubuntu1.2) over (2.30.7-0ubuntu1.2) ... Setting up libgdk-pixbuf2.0-0:amd64 (2.30.7-0ubuntu1.2) ... Processing triggers for libc-bin (2.19-0ubuntu6.6) ... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1492767 Title: gdk-pixbuf packages update breaks the GUI in Trusty 14.04.3 Status in gdk-pixbuf package in Ubuntu: Confirmed Bug description: Hello, I did a fresh install with a Trusty 14.04.3 (x86_64) yesterday (custom Bento Openbox), and today, I updated the system (with the console, because other issues came first which led me to do a filesystem check). Then I started Synaptic, and oops! no GUI, only the borders of the window would show. Several other programs were affected and would not start (Geany, text editor), or show their content. After tests and research it appeared only GTK3 programs were affected. If using a theme with GTK2, or move the GTK configuration out of the way, the programs would work. The upgrade contained the following packages: gir1.2-gdkpixbuf-2.0_2.30.7 libgdk-pixbuf2.0-0_2.30.7 libgdk-pixbuf2.0-common_2.30.7 I fixed the issue by booting to the Live USB I had used to install, and repackage the programs with dpkg-repack, then reinstalled them using "sudo dpkg -i *.deb". (copied from the live usb to the home in the install, rebooted and reinstalled there). Problem solved for this install, where I have for now blocked the update for these three packages. At post-install, after I had updated, I had the same message as the people who reported that bug: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1282294 (gtk-update-icon-cache-3.0:29671): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache': No such file or directory This likely means that your installation is broken. Try running the command gdk-pixbuf-query-loaders > /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache to make things work again for the time being. and when trying to do so, the console returned a message stating gdk- pixbuf-query-loaders was not installed. (no such package in the repos either). More information can be found at http://irclogs.ubuntu.com/2015/09/06/%23ubuntu-bugs.html where I discussed about this bug and my findings. Now I will try to produce this bug again in the Live USB (which has no persistence). Best regards, Mélodie To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1492767/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1514031] Re: i cannot boot
ibnu, thank you for reporting this and helping make Ubuntu better. Does updating to the Wily enablement stack allow booting as outlined in https://wiki.ubuntu.com/Kernel/LTSEnablementStack ? ** Changed in: xorg (Ubuntu) Importance: Undecided => Medium ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1514031 Title: i cannot boot Status in xorg package in Ubuntu: Incomplete Bug description: i have problem when booting ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.16.0-48.64~14.04.1-generic 3.16.7-ckt15 Uname: Linux 3.16.0-48-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.18 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: Sat Nov 7 11:46:57 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a011] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:83ac] Subsystem: ASUSTeK Computer Inc. Device [1043:83ac] InstallationDate: Installed on 2015-08-20 (79 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 (20150218.1) MachineType: ASUSTeK Computer INC. 1015PX ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-48-generic root=UUID=c4158f2f-3506-46cb-b287-f3830ca03fdc ro quiet splash plymouth:debug=1 plymouth:debug=1=1=1=1=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/30/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1401 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1015PE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1401:bd08/30/2011:svnASUSTeKComputerINC.:pn1015PX:pvrx.x:rvnASUSTeKComputerINC.:rn1015PE:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x: dmi.product.name: 1015PX dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sat Nov 7 11:32:18 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1012 vendor IVO xserver.version: 2:1.16.0-1ubuntu1.2~trusty2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1514031/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1262110] Re: Ubuntu Gnome - running ubuntu-bug leaves 'Report a problem' icon in frequent apps menu
[Expired for Ubuntu GNOME because there has been no activity for 60 days.] ** Changed in: ubuntu-gnome Status: Incomplete => Expired -- 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/1262110 Title: Ubuntu Gnome - running ubuntu-bug leaves 'Report a problem' icon in frequent apps menu Status in Ubuntu GNOME: Expired Status in apport package in Ubuntu: Expired Bug description: Ubuntu Gnome - 14.04 dev release - 20131217. Running 'ubuntu-bug' leaves 'Report a problem' icon (blue paint splash) in frequent apps menu. This icon if clicked does nothing and should not be there after running 'ubuntu-bug' from the terminal. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apport 2.12.7-0ubuntu2 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.12.7-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Dec 18 09:00:48 2013 InstallationDate: Installed on 2013-12-18 (0 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20131217) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1262110/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1262110] Re: Ubuntu Gnome - running ubuntu-bug leaves 'Report a problem' icon in frequent apps menu
[Expired for apport (Ubuntu) because there has been no activity for 60 days.] ** Changed in: apport (Ubuntu) Status: Incomplete => Expired -- 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/1262110 Title: Ubuntu Gnome - running ubuntu-bug leaves 'Report a problem' icon in frequent apps menu Status in Ubuntu GNOME: Expired Status in apport package in Ubuntu: Expired Bug description: Ubuntu Gnome - 14.04 dev release - 20131217. Running 'ubuntu-bug' leaves 'Report a problem' icon (blue paint splash) in frequent apps menu. This icon if clicked does nothing and should not be there after running 'ubuntu-bug' from the terminal. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apport 2.12.7-0ubuntu2 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.12.7-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Dec 18 09:00:48 2013 InstallationDate: Installed on 2013-12-18 (0 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20131217) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1262110/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1480877] Re: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices
The attachment "Initial attempt to patch QNetworkSession to fix match rules leak" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1480877 Title: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices Status in Canonical System Image: Confirmed Status in Unity 8: New Status in indicator-network package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Incomplete Status in qtbase-opensource-src package in Ubuntu: Confirmed Status in buteo-syncfw package in Ubuntu RTM: New Status in location-service package in Ubuntu RTM: Triaged Status in maliit-framework package in Ubuntu RTM: New Status in network-manager package in Ubuntu RTM: Incomplete Status in sync-monitor package in Ubuntu RTM: New Bug description: Krillin, rc-proposed, r83 DESCRIPTION: I've been trying to track down the cause of the occasional UI freezes on my Krillin device, and I noticed that whenever the UI freezes for 2-4 seconds, I get a burst of "PropertiesChanged" signals in dbus-monitor Here's a log of what's shown in dbus-monitor: http://pastebin.ubuntu.com/11992322/ I'd guess the problem is in the code that actually catches the signals and acts accordingly. HOW TO REPRODUCE: 1) Move to a place where many wifi hotspots are available 2) Connect the device via USB and run "phablet-shell" and then "dbus-monitor" 3) Use the device while keeping an eye on dbus-monitor output To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1480877/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1514016] Re: travamentos
Moysés Costa Duarte, thank you for reporting this and helping make Ubuntu better. Could you please provide the full serial number as noted on the sticker of the computer itself as outlined in http://www.positivoinformatica.com.br/suporte-tecnico-drivers#tab- computadores ? ** Changed in: xorg (Ubuntu) Importance: Undecided => Low ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1514016 Title: travamentos Status in xorg package in Ubuntu: Incomplete Bug description: meu desktope trava muinto e deixa jogos lentos ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu3 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: Fri Nov 6 23:03:53 2015 DistUpgraded: 2015-11-06 22:19:41,686 DEBUG enabling apt cron job DistroCodename: wily DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer Device [1297:2033] InstallationDate: Installed on 2015-11-06 (0 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release i386 (20141022.1) MachineType: Positivo Informatica SA H14CU01 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-16-generic root=/dev/mapper/ubuntu--vg-root ro priority=low locale=pt_BR quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to wily on 2015-11-07 (0 days ago) dmi.bios.date: 12/03/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.02.U dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H14CU01 dmi.board.vendor: Positivo Informatica SA dmi.board.version: SIM dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: Positivo Informatica SA dmi.chassis.version: SIM dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.02.U:bd12/03/2013:svnPositivoInformaticaSA:pnH14CU01:pvr1.02.U_SIM:rvnPositivoInformaticaSA:rnH14CU01:rvrSIM:cvnPositivoInformaticaSA:ct10:cvrSIM: dmi.product.name: H14CU01 dmi.product.version: 1.02.U_SIM dmi.sys.vendor: Positivo Informatica SA version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1 version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Fri Nov 6 22:21:12 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 901 vendor LGD xserver.version: 2:1.17.2-1ubuntu9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1514016/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1513482] Re: 15.10 dist-upgrade, Xorg freeze, ASUSTeK Computer Inc. N56VZ
David Nyström, thank you for reporting this and helping make Ubuntu better. Could you please test the latest upstream kernel available from the very top line at the top of the page from http://kernel.ubuntu.com/~kernel- ppa/mainline/?C=N;O=D (the release names are irrelevant for testing, and please do not test the daily folder)? Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds . This will allow additional upstream developers to examine the issue. If the latest kernel 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 issue 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-X.Y-rcZ Where X, Y, and Z are numbers corresponding to the kernel version. If the mainline kernel does not fix the issue, please add the following tags: kernel-bug-exists-upstream kernel-bug-exists-upstream-X.Y-rcZ Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream. Once testing of the latest upstream kernel is complete, please mark this report's Status as Confirmed. Please let us know your results. Thank you for your understanding. ** Tags added: latest-bios-217 ** Description changed: immendiately after upgrade to 15.10. Happen 100% reproducable at boot. Target reachable via ssh, but not via keyboard or screen. + + WORKAROUND: Add nomodeset to kernel cmdline. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 .tmp.unity.support.test.1: - + ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Nov 5 15:12:47 2015 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: - Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) -Subsystem: ASUSTeK Computer Inc. N56VZ [1043:2103] - NVIDIA Corporation GK107M [GeForce GT 650M] [10de:0fd1] (rev a1) (prog-if 00 [VGA controller]) -Subsystem: ASUSTeK Computer Inc. N56VZ [1043:2103] + Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) + Subsystem: ASUSTeK Computer Inc. N56VZ [1043:2103] + NVIDIA Corporation GK107M [GeForce GT 650M] [10de:0fd1] (rev a1) (prog-if 00 [VGA controller]) + Subsystem: ASUSTeK Computer Inc. N56VZ [1043:2103] InstallationDate: Installed on 2013-10-04 (761 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1) MachineType: ASUSTeK COMPUTER INC. N56VZ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-16-generic root=UUID=563891a5-84f3-49a3-9799-021ea124aca4 ro quiet splash SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/22/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N56VZ.217 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N56VZ dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN56VZ.217:bd05/22/2013:svnASUSTeKCOMPUTERINC.:pnN56VZ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN56VZ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: N56VZ dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubu
[Touch-packages] [Bug 1513024] Re: Display-server randomly crashing in Ubuntu 15.10 after upgrade
Andreas, thank you for reporting this and helping make Ubuntu better. As per http://support.lenovo.com/us/en/products/laptops-and- netbooks/thinkpad-t-series-laptops/thinkpad-t440p an update to your computer's buggy and outdated BIOS is available (2.35). 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, if the problem is still reproducible, and the information above is provided, then please mark this report Status New. Otherwise, please mark this as Invalid. Thank you for your understanding. ** Tags added: bios-outdated-2.35 ** Changed in: xorg (Ubuntu) Importance: Undecided => Low ** Changed in: xorg (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1513024 Title: Display-server randomly crashing in Ubuntu 15.10 after upgrade Status in xorg package in Ubuntu: Incomplete Bug description: On: Ubuntu 15.10 After some random amount of time (at first correlated with actions such as switching between screens, max-/minimising windows, but now also sometimes not), the display server seems to die completely, restarting after a few seconds to dump me at the login screen. Getting errors like: $ dmesg ... [ 239.809761] WARNING: CPU: 0 PID: 1879 at /build/linux-AxjFAn/linux-4.2.0/drivers/gpu/drm/i915/i915_gem.c:5269 i915_gem_track_fb+0x129/0x140 [i915]() [ 239.809762] WARN_ON(!(old->frontbuffer_bits & frontbuffer_bits)) [ 239.809763] Modules linked in: [ 239.809765] rfcomm msr acpi_call(OE) pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) openafs(POE) binfmt_misc bnep btusb btrtl btbcm btintel bluetooth uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core v4l2_common videodev media arc4 intel_rapl iosf_mbi x86_pkg_temp_thermal intel_powerclamp coretemp kvm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel iwlmvm aes_x86_64 lrw gf128mul glue_helper mac80211 ablk_helper cryptd joydev input_leds snd_seq_midi serio_raw snd_seq_midi_event snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi thinkpad_acpi snd_rawmidi nvram iwlwifi snd_seq snd_hda_intel rtsx_pci_ms memstick snd_hda_codec lpc_ich cfg80211 snd_hda_core snd_hwdep snd_pcm mei_me ie31200_edac mei snd_seq_device edac_core shpchp snd_timer snd soundcore [ 239.809798] ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 mac_hid xt_hl ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT nf_reject_ipv4 nf_log_ipv4 nf_log_common xt_LOG xt_limit xt_tcpudp xt_addrtype nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack ip6table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack iptable_filter ip_tables x_tables parport_pc ppdev lp parport autofs4 rtsx_pci_sdmmc nouveau i915 mxm_wmi ttm e1000e i2c_algo_bit psmouse ahci drm_kms_helper libahci ptp rtsx_pci pps_core drm wmi video [ 239.809822] CPU: 0 PID: 1879 Comm: Xorg Tainted: P OE 4.2.0-16-generic #19-Ubuntu [ 239.809824] Hardware name: LENOVO 20AWS37E00/20AWS37E00, BIOS GLET77WW (2.31 ) 01/27/2015 [ 239.809825] 2aa5ef7b 8800a922fac8 817e8c09 [ 239.809827] 8800a922fb20 8800a922fb08 8107b3c6 [ 239.809829] 880425a47840 0010 8804256a 8804256a [ 239.809831] Call Trace: [ 239.809836] [] dump_stack+0x45/0x57 [ 239.809841] [] warn_slowpath_common+0x86/0xc0 [ 239.809843] [] warn_slowpath_fmt+0x55/0x70 [ 239.809853] [] i915_gem_track_fb+0x129/0x140 [i915] [ 239.809868] [] intel_prepare_plane_fb+0xe7/0x1a0 [i915] [ 239.809874] [] drm_atomic_helper_prepare_planes+0x59/0xe0 [drm_kms_helper] [ 239.809887] [] ? drm_atomic_check_only+0x215/0x540 [drm] [ 239.809901] [] intel_atomic_commit+0x42/0x100 [i915] [ 239.809910] [] drm_atomic_commit+0x37/0x60 [drm] [ 239.809915] [] drm_atomic_helper_plane_set_property+0x87/0xc0 [drm_kms_helper] [ 239.809922] [] ? _object_find+0x69/0xa0 [drm] [ 239.809930] [] drm_mode_plane_set_obj_prop+0x2d/0x90 [drm] [ 239.809939] [] drm_mode_obj_set_property_ioctl+0x1c6/0x270 [drm] [ 239.809944] [] drm_ioctl+0x125/0x610 [drm] [ 239.809947] [] ? fsnotify+0x316/0x4a0 [ 239.809954] [] ? drm_mode_obj_get_properties_ioctl+0xa0/0xa0 [drm] [ 2
[Touch-packages] [Bug 1509921] Re: [HDA-Intel - HD-Audio Generic, recording] No sound at all
https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/sound/pci/hda?id=1f8b46cdc806dfd76386f8442d9a6d0ae69abb25 ** Changed in: alsa-driver (Ubuntu) Status: New => Incomplete -- 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/1509921 Title: [HDA-Intel - HD-Audio Generic, recording] No sound at all Status in HWE Next: New Status in alsa-driver package in Ubuntu: Incomplete Bug description: This is a desktop box, with following ports: front jack: a single headset combo jack rear jacks: mic, speaker, line-in An "Analog Input" consistently show up even there is nothing plugged, but I'm not able to record via headset jack or rear mic jack, they all recorded with noises. 00:01.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:9840] 00:14.2 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] FCH Azalia Controller [1022:780d] (rev 02) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-66.108-generic 3.13.11-ckt27 Uname: Linux 3.13.0-66-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: u 1824 F pulseaudio /dev/snd/controlC0: u 1824 F pulseaudio CurrentDesktop: Unity Date: Mon Oct 26 11:46:46 2015 InstallationDate: Installed on 2015-10-23 (2 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic_1 failed Symptom_Card: Built-in Audio - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: u 1824 F pulseaudio /dev/snd/controlC0: u 1824 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HD-Audio Generic, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/21/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.0.0:bd05/21/2015:svnDellInc.:pnInspiron3655:pvr1.0.0:rvnDellInc.:rn:rvr:cvnDellInc.:ct3:cvrNotSpecified: dmi.product.name: Inspiron 3655 dmi.product.version: 1.0.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1509921/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1512968] Re: sidebar doesn't appear anymore when Window in split screen mode
sevku, thank you for reporting this and helping make Ubuntu better. As per http://support.lenovo.com/us/en/products/laptops-and- netbooks/lenovo-b-series-laptops/lenovo-b50-30-notebook an update to your computer's buggy and outdated BIOS is available (2.11). 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, if the problem is still reproducible, and the information above is provided, then please mark this report Status New. Otherwise, please mark this as Invalid. Thank you for your understanding. ** Tags added: bios-outdated-2.11 ** Changed in: xorg (Ubuntu) Importance: Undecided => Low ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1512968 Title: sidebar doesn't appear anymore when Window in split screen mode Status in xorg package in Ubuntu: Incomplete Bug description: When I dock a window to the side to split the screen, the Sidebar doesn't appear anymore when I move the cursor to the side of the screen. I have to undock the window first. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Nov 4 08:37:15 2015 DistUpgraded: 2015-10-28 00:03:04,139 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Kindprozess »./xorg_fix_proprietary.py« konnte nicht ausgeführt werden (Datei oder Verzeichnis nicht gefunden) (8)) DistroCodename: wily DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3986] InstallationDate: Installed on 2015-08-13 (82 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 013: ID 0cf3:3004 Atheros Communications, Inc. AR3012 Bluetooth 4.0 Bus 001 Device 003: ID 5986:055d Acer, Inc Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80ES ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic.efi.signed root=UUID=4842d481-f5d0-41c1-a614-769115c50b50 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: '/var/log/udev' UpgradeStatus: Upgraded to wily on 2015-10-27 (7 days ago) dmi.bios.date: 06/06/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 9CCN26WW(V2.04) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo B50-30 dmi.board.vendor: LENOVO dmi.board.version: SDK0F82993WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo B50-30 dmi.modalias: dmi:bvnLENOVO:bvr9CCN26WW(V2.04):bd06/06/2014:svnLENOVO:pn80ES:pvrLenovoB50-30:rvnLENOVO:rnLenovoB50-30:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoB50-30: dmi.product.name: 80ES dmi.product.version: Lenovo B50-30 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Tue Nov 3 19:24:35 2
[Touch-packages] [Bug 1516126] Re: apport-retrace fails unless apport is also installed (/etc/apport/crashdb.conf)
** Changed in: apport (Ubuntu) Status: New => Confirmed -- 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/1516126 Title: apport-retrace fails unless apport is also installed (/etc/apport/crashdb.conf) Status in apport package in Ubuntu: Confirmed Bug description: Attempting to run apport-retrace in a chroot, it fails with the following traceback: Traceback (most recent call last): File "/usr/bin/apport-retrace", line 217, in crashdb = get_crashdb(options.auth) File "/usr/lib/python2.7/dist-packages/apport/crashdb.py", line 822, in get_crashdb with open(conf) as f: IOError: [Errno 2] No such file or directory: '/etc/apport/crashdb.conf' /etc/apport/crashdb.conf is part of the apport package; and apport- retrace does not depend on apport. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1516126/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1516192] [NEW] package make 4.0-8.2 failed to install/upgrade: package make is not ready for configuration cannot configure (current status 'half-installed')
Public bug reported: occurred on system update request ProblemType: Package DistroRelease: Ubuntu 15.10 Package: make 4.0-8.2 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic i686 ApportVersion: 2.19.1-0ubuntu4 Architecture: i386 Date: Sat Nov 14 11:18:39 2015 Dependencies: gcc-5-base 5.2.1-22ubuntu2 libc6 2.21-0ubuntu4 libgcc1 1:5.2.1-22ubuntu2 DuplicateSignature: package:make:4.0-8.2:package make is not ready for configuration cannot configure (current status 'half-installed') ErrorMessage: package make is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2015-11-08 (5 days ago) InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release i386 (20151021) RelatedPackageVersions: dpkg 1.18.2ubuntu5 apt 1.0.10.2ubuntu1 SourcePackage: make-dfsg Title: package make 4.0-8.2 failed to install/upgrade: package make is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: make-dfsg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 need-duplicate-check wily -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to make-dfsg in Ubuntu. https://bugs.launchpad.net/bugs/1516192 Title: package make 4.0-8.2 failed to install/upgrade: package make is not ready for configuration cannot configure (current status 'half- installed') Status in make-dfsg package in Ubuntu: New Bug description: occurred on system update request ProblemType: Package DistroRelease: Ubuntu 15.10 Package: make 4.0-8.2 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic i686 ApportVersion: 2.19.1-0ubuntu4 Architecture: i386 Date: Sat Nov 14 11:18:39 2015 Dependencies: gcc-5-base 5.2.1-22ubuntu2 libc6 2.21-0ubuntu4 libgcc1 1:5.2.1-22ubuntu2 DuplicateSignature: package:make:4.0-8.2:package make is not ready for configuration cannot configure (current status 'half-installed') ErrorMessage: package make is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2015-11-08 (5 days ago) InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release i386 (20151021) RelatedPackageVersions: dpkg 1.18.2ubuntu5 apt 1.0.10.2ubuntu1 SourcePackage: make-dfsg Title: package make 4.0-8.2 failed to install/upgrade: package make is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/make-dfsg/+bug/1516192/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1516166] Re: [HDA-Intel - HDA Intel, playback] Pulseaudio fails to detect card
you have to file upstream bug report 0.140130] pci :00:1b.0: [8086:27d8] type 00 class 0x040300 [0.140173] pci :00:1b.0: reg 0x10: [mem 0xf054-0xf0543fff 64bit] [0.140264] pci :00:1b.0: PME# supported from D0 D3hot D3cold [0.140329] pci :00:1b.0: System wakeup disabled by ACPI compare with boot dmesg in bug#1005128 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1516166 Title: [HDA-Intel - HDA Intel, playback] Pulseaudio fails to detect card Status in pulseaudio package in Ubuntu: New Bug description: 00:1b.0 Audio device: Intel Corporation NM10/ICH7 Family High Definition Audio Controller (rev 02) Subsystem: Fujitsu Limited. Device 1397 Flags: bus master, fast devsel, latency 0, IRQ 29 Memory at f054 (64-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 2 Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00 Capabilities: [100] Virtual Channel Capabilities: [130] Root Complex Link Kernel driver in use: snd_hda_intel that was it says ! no drivers ? best regards holger ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: pulseaudio 1:6.0-0ubuntu13 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic i686 ApportVersion: 2.19.1-0ubuntu5 Architecture: i386 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', '/dev/snd/by-path', '/dev/snd/hwC0D1', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Fri Nov 13 23:15:59 2015 InstallationDate: Installed on 2015-08-11 (94 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel Title: [HDA-Intel - HDA Intel, playback] Pulseaudio fails to detect card UpgradeStatus: Upgraded to wily on 2015-11-11 (2 days ago) dmi.bios.date: 09/10/2008 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.35 dmi.board.name: FJNB1B5 dmi.board.vendor: FUJITSU dmi.board.version: CP279595-02 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU SIEMENS dmi.chassis.version: S7110 dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.35:bd09/10/2008:svnFUJITSUSIEMENS:pnLIFEBOOKS7110:pvr:rvnFUJITSU:rnFJNB1B5:rvrCP279595-02:cvnFUJITSUSIEMENS:ct10:cvrS7110: dmi.product.name: LIFEBOOK S7110 dmi.sys.vendor: FUJITSU SIEMENS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1516166/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1325940] Re: Desktop sometimes comes up with undisplayable screen resolution
Jan Rathmann, to clarify, is this your motherboard http://www.msi.com/product/motherboard/support/K8MMV.html#down-bios ? -- 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/1325940 Title: Desktop sometimes comes up with undisplayable screen resolution Status in xorg package in Ubuntu: Incomplete Bug description: Hello, the PC from which I'm sending this report sometimes fails to boot into the desktop properly (which desktop environment doesn't seem to matter). In the failure case the following happens: - The Plymouth Ubuntu splash gets displayed, but it looks distorted. Flickering horizontal artifacts are shown all over the screen, it looks a bit like a CRT Television with low signal. - When the desktop is loaded (via autologin), one can see short glimpses of its wallpaper, but after a few second the screen becomes black and remains that way. The monitor _does_ seem to receive a signal though. - It is possible to switch to TTYs and to use them, but they show similar artifacts like the Plymouth logo. - If I query the display information on the monitor's OSD when the screen is distorted, it reports a resolution of 1681x1050 or 1683x1050, which is 1-3 pixel bigger than the native horizontal resolution of the 22" LCD screen. Switching between different resolutions via entering 'xrandr --size 1024x768' blindly, followed by 'xrandr --size 1680x1050' brings up the native resolution properly. This does not happen on every boot, only in ~10-15% of the cases. I was not able to find any pattern so far in the occurence of this bug. The only thing I observed is that it _never_ happens when Windows XP is started, thus my assumption is that the bug is related to the xserver-xorg-video-radeon driver. I tried to specify the correct resolution explicitly on the kernel command line(adding video=DVI-I-1:1680x1050 ) but this has no positive effect. The monitor is connected via DVI. Below is a video attached that tries to show how the TTYs look when this bug occurs. Notice the abnormal blue lines, which are constantly flickering. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-radeon 1:7.3.0-1ubuntu3.1 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Jun 3 13:23:38 2014 InstallationDate: Installed on 2014-04-22 (41 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV350 [Radeon 9550] [1002:4153] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932a] Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932b] InstallationDate: Installed on 2014-04-22 (570 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) LightdmGreeterLog: ** (lightdm-gtk-greeter:9382): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden 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:6675): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden 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: MSI MS-6741 Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic root=UUID=b7a652e9-aea3-4c8a-bf11-32ec8d22b3bb ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25 Tags: trusty ubuntu Uname: Linux 3.13.0-63-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare saned scanner sudo _MarkForUpload: True dmi.bios.date: 04/02/01 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Version 07.00T dmi.board.name: MS-6741 dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.a
[Touch-packages] [Bug 1515995] Re: Screen
Neil Widdowson, thank you for reporting this and helping make Ubuntu better. Any change using the nouveau drivers? ** Tags added: latest-bios-1.8 ** Changed in: xorg (Ubuntu) Importance: Undecided => Medium ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1515995 Title: Screen Status in xorg package in Ubuntu: Incomplete Bug description: I am trying out Kubuntu at the moment and I have noticed that when watching videos they flicker. I have tried the different options in the 'Compositor Settings for Desktop Effects' Tearing Prevention and none seem to make a difference other than that if I put it on automatic, the top half of the screen flickers, and with 'full screen repaints' the whole screen flickers. I have tried the official Nvidia driver (352), the one from software centre and the default one - all make the video flicker in full screen. I had the same problem while using Linux Mint Mate, but not while using the Cinnamon Desktop, I also don't remember the problem occurring while using Ubuntu Unity Desktop. I am fairly new to Linux so I don't know too much about how to go about finding out the problem. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 352.41 Fri Aug 21 23:09:52 PDT 2015 GCC version: gcc version 5.2.1 20151010 (Ubuntu 5.2.1-22ubuntu2) ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 BootLog: fsck from util-linux 2.26.2 /dev/sdb2: clean, 266511/13574144 files, 7382798/54296320 blocks CurrentDesktop: KDE Date: Fri Nov 13 12:47:42 2015 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: kubuntu DkmsStatus: bbswitch, 0.7, 4.2.0-18-generic, x86_64: installed nvidia-352-updates, 352.41, 4.2.0-18-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GK104 [GeForce GTX 760] [10de:1187] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation Device [10de:0984] InstallationDate: Installed on 2015-11-12 (0 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: MSI MS-7850 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic.efi.signed root=UUID=43b80561-2236-4234-9459-091517df6ac9 ro quiet splash vt.handoff=7 SourcePackage: xorg UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/21/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.8 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-G41 PC Mate(MS-7850) 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.8:bd07/21/2014:svnMSI:pnMS-7850:pvr1.0:rvnMSI:rnZ87-G41PCMate(MS-7850):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7850 dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Fri Nov 13 10:44:18 2015 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.17.2-1ubuntu9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1515995/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1515463] Re: Broken juju LXC deployments
This bug was fixed in the package lxc - 1.1.5-0ubuntu2
---
lxc (1.1.5-0ubuntu2) xenial; urgency=medium
* Cherry-pick from upstream:
- Fix ubuntu-cloud template to detect compression algorithm instead
of hardcoding xz. Also update list of supported releases and use trusty
as the fallback release. (LP: #1515463)
* Update lxc-tests description to make it clear that this package is
meant to be used by developers and by automated testing.
-- Stéphane Graber Fri, 13 Nov 2015 12:05:36
-0500
** Changed in: lxc (Ubuntu Xenial)
Status: Fix Committed => Fix Released
--
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/1515463
Title:
Broken juju LXC deployments
Status in lxc package in Ubuntu:
Fix Released
Status in lxc source package in Trusty:
Fix Committed
Status in lxc source package in Vivid:
Fix Committed
Status in lxc source package in Wily:
Fix Committed
Status in lxc source package in Xenial:
Fix Released
Bug description:
I've just tried using juju to deploy to a container with trusty-
proposed repo enabled, and I get an error message about 'failed to
retrieve the template to clone'. The underlying error appears to be:
tar --numeric-owner -xpJf
/var/cache/lxc/cloud-trusty/ubuntu-14.04-server-cloudimg-amd64-root.tar.gz;
xz: (stdin): File format not recognized; tar: Child returned status 1; tar:
Error is not recoverable: exiting now;
This seems to be fairly obvious, trying to use xz on a tar.gz file is
never going to work.
The change appears to be from
https://github.com/lxc/lxc/commit/27c278a76931bfc4660caa85d1942ca91c86e0bf,
it assumes everything passed into it will be a .tar.xz file.
This appears to be a conflict between the template expecting a .tar.xz
file, and juju providing it a .tar.gz file. You can see what juju is
providing from:
$ ubuntu-cloudimg-query trusty released amd64 --format %{url}
https://cloud-images.ubuntu.com/server/releases/trusty/release-20151105/ubuntu-14.04-server-cloudimg-amd64.tar.gz
From the juju deployed host:
$ apt-cache policy lxc-templates
lxc-templates:
Installed: 1.0.8-0ubuntu0.1
Candidate: 1.0.8-0ubuntu0.1
Version table:
*** 1.0.8-0ubuntu0.1 0
500 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64
Packages
100 /var/lib/dpkg/status
From the host running juju:
$ apt-cache policy juju-core
juju-core:
Installed: 1.22.8-0ubuntu1~14.04.1
Candidate: 1.25.0-0ubuntu1~14.04.1~juju1
Version table:
1.25.0-0ubuntu1~14.04.1~juju1 0
500 http://ppa.launchpad.net/juju/proposed/ubuntu/ trusty/main amd64
Packages
*** 1.22.8-0ubuntu1~14.04.1 0
400 http://archive.ubuntu.com/ubuntu/ trusty-proposed/universe amd64
Packages
100 /var/lib/dpkg/status
All machine involved are running trusty:
$ lsb_release -rd
Description:Ubuntu 14.04.3 LTS
Release:14.04
Please let me know if you need any more information.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1515463/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1480877] Re: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices
Here's a first attempt at a patch, which unfortunately doesn't seem to work... The general idea is when an AccessPointRemoved signal is received, we need to ensure that the associated DBus watch is removed. According to the QDbus documentation, DBusConnection::disconnect() should do this. I unfortunately didn't add any debug logging, so will have to take another stab on Monday ( unless someone else can take a look ). ** Patch added: "Initial attempt to patch QNetworkSession to fix match rules leak" https://bugs.launchpad.net/ubuntu-rtm/+source/sync-monitor/+bug/1480877/+attachment/4518542/+files/net-bearer-nm-disconnect-ap-signals.patch -- 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/1480877 Title: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices Status in Canonical System Image: Confirmed Status in Unity 8: New Status in indicator-network package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Incomplete Status in qtbase-opensource-src package in Ubuntu: Confirmed Status in buteo-syncfw package in Ubuntu RTM: New Status in location-service package in Ubuntu RTM: Triaged Status in maliit-framework package in Ubuntu RTM: New Status in network-manager package in Ubuntu RTM: Incomplete Status in sync-monitor package in Ubuntu RTM: New Bug description: Krillin, rc-proposed, r83 DESCRIPTION: I've been trying to track down the cause of the occasional UI freezes on my Krillin device, and I noticed that whenever the UI freezes for 2-4 seconds, I get a burst of "PropertiesChanged" signals in dbus-monitor Here's a log of what's shown in dbus-monitor: http://pastebin.ubuntu.com/11992322/ I'd guess the problem is in the code that actually catches the signals and acts accordingly. HOW TO REPRODUCE: 1) Move to a place where many wifi hotspots are available 2) Connect the device via USB and run "phablet-shell" and then "dbus-monitor" 3) Use the device while keeping an eye on dbus-monitor output To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1480877/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1480877] Re: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices
@Timo Thanks for the update. I commented on bug #1404188 regarding this bug. I agree with you that moving to a new backend for the vivid-overlay PPA is risky. That said, if we keep the networkmanager bug backend, this bug really needs to be fixed. What you say about the networkmanager backend is true, as NM is the controller of our networking, so querying it makes sense if you want to know whether we're on 3g or WiFi. That said, the connectivity API was originally designed to do the same thing, although it was never actually "published" as an API that could be used by the rest of the system. It was designed for this, however the team never finished the work, so AFAIK to date, it's only been used by indicator-network. In *theory*, it should be possible to query the same exact information from a connectivity-API based backend. It would give far less control however actually permitting changes to the network configuration and/or what interface was activated. I think that's OK, as we delegate all of that to indicator-network. We have no concept of a network-admin capability that can be granted to apps ( again AFAIK ). -- 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/1480877 Title: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices Status in Canonical System Image: Confirmed Status in Unity 8: New Status in indicator-network package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Incomplete Status in qtbase-opensource-src package in Ubuntu: Confirmed Status in buteo-syncfw package in Ubuntu RTM: New Status in location-service package in Ubuntu RTM: Triaged Status in maliit-framework package in Ubuntu RTM: New Status in network-manager package in Ubuntu RTM: Incomplete Status in sync-monitor package in Ubuntu RTM: New Bug description: Krillin, rc-proposed, r83 DESCRIPTION: I've been trying to track down the cause of the occasional UI freezes on my Krillin device, and I noticed that whenever the UI freezes for 2-4 seconds, I get a burst of "PropertiesChanged" signals in dbus-monitor Here's a log of what's shown in dbus-monitor: http://pastebin.ubuntu.com/11992322/ I'd guess the problem is in the code that actually catches the signals and acts accordingly. HOW TO REPRODUCE: 1) Move to a place where many wifi hotspots are available 2) Connect the device via USB and run "phablet-shell" and then "dbus-monitor" 3) Use the device while keeping an eye on dbus-monitor output To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1480877/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1516169] [NEW] /usr/bin/mediascanner-service-2.0:11:_M_data:_M_rep:size:compare:operator
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding mediascanner2. This problem was most recently seen with version 0.108+15.04.20151109-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/0c982761f6b1dc6ebdbd4ca9ae81c5a35a349f99 contains more details. ** Affects: mediascanner2 (Ubuntu) Importance: Undecided Status: New ** Tags: utopic vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mediascanner2 in Ubuntu. https://bugs.launchpad.net/bugs/1516169 Title: /usr/bin/mediascanner- service-2.0:11:_M_data:_M_rep:size:compare:operator Status in mediascanner2 package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding mediascanner2. This problem was most recently seen with version 0.108+15.04.20151109-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/0c982761f6b1dc6ebdbd4ca9ae81c5a35a349f99 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mediascanner2/+bug/1516169/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1515818] Re: apparmor profile has a typo
This bug was fixed in the package isc-dhcp - 4.3.1-5ubuntu4 --- isc-dhcp (4.3.1-5ubuntu4) xenial; urgency=medium [ John Johansen ] * debian/apparmor/sbin.dhclient: fix signal rule typo in nm-dhcp-helper profile (LP: #1515818) -- Jamie Strandboge Fri, 13 Nov 2015 08:16:54 -0600 ** Changed in: isc-dhcp (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1515818 Title: apparmor profile has a typo Status in isc-dhcp package in Ubuntu: Fix Released Bug description: apparmor reports the following denial Nov 4 06:36:31 ortho2 kernel: [ 155.310264] audit: type=1400 audit(1446647791.742:151): apparmor="DENIED" operation="signal" profile="/usr/lib/NetworkManager/nm-dhcp-helper" pid=3056 comm="kill" requested_mask="send" denied_mask="send" signal=term peer="/sbin/dhclient" this is due to a typo in the /usr/lib/NetworkManager/nm-dhcp-helper profile. The attached patch will fix the problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1515818/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1516167] [NEW] Proxies should be per connection, not system-wide
Public bug reported: Usually, we don't use a constant proxy every where. When I am at home, I use a local proxy on my raspberry-pi, but when I am at university, I use the proxy server of the university, when I use my phone as a hot-spot, I want to use no proxy And when I am at a public network, I prefer to use local tor proxy. So I think the proxy should be a property of the connection, just like the DNS address, not a system-wide option. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1516167 Title: Proxies should be per connection, not system-wide Status in network-manager package in Ubuntu: New Bug description: Usually, we don't use a constant proxy every where. When I am at home, I use a local proxy on my raspberry-pi, but when I am at university, I use the proxy server of the university, when I use my phone as a hot- spot, I want to use no proxy And when I am at a public network, I prefer to use local tor proxy. So I think the proxy should be a property of the connection, just like the DNS address, not a system- wide option. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1516167/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1515848] Re: (w, 0) and (0, h) requests are not scaled correctly
** Changed in: thumbnailer (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to thumbnailer in Ubuntu.
https://bugs.launchpad.net/bugs/1515848
Title:
(w,0) and (0,h) requests are not scaled correctly
Status in thumbnailer package in Ubuntu:
Fix Committed
Bug description:
By definition, (w,0) and (0,h) should be the same as (w,w) and (h,h),
respectively.
They are not, and the qml test tests for the wrong outcome:
function test_scale_vertical() {
requestedSize = Qt.size(0, 240);
loadThumbnail("orientation-1.jpg");
compare(size.width, 320);
compare(size.height, 240);
}
For this request, size.width() cannot possibly be larger than 240.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thumbnailer/+bug/1515848/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1516166] [NEW] [HDA-Intel - HDA Intel, playback] Pulseaudio fails to detect card
Public bug reported: 00:1b.0 Audio device: Intel Corporation NM10/ICH7 Family High Definition Audio Controller (rev 02) Subsystem: Fujitsu Limited. Device 1397 Flags: bus master, fast devsel, latency 0, IRQ 29 Memory at f054 (64-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 2 Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00 Capabilities: [100] Virtual Channel Capabilities: [130] Root Complex Link Kernel driver in use: snd_hda_intel that was it says ! no drivers ? best regards holger ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: pulseaudio 1:6.0-0ubuntu13 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic i686 ApportVersion: 2.19.1-0ubuntu5 Architecture: i386 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', '/dev/snd/by-path', '/dev/snd/hwC0D1', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Fri Nov 13 23:15:59 2015 InstallationDate: Installed on 2015-08-11 (94 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel Title: [HDA-Intel - HDA Intel, playback] Pulseaudio fails to detect card UpgradeStatus: Upgraded to wily on 2015-11-11 (2 days ago) dmi.bios.date: 09/10/2008 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.35 dmi.board.name: FJNB1B5 dmi.board.vendor: FUJITSU dmi.board.version: CP279595-02 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU SIEMENS dmi.chassis.version: S7110 dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.35:bd09/10/2008:svnFUJITSUSIEMENS:pnLIFEBOOKS7110:pvr:rvnFUJITSU:rnFJNB1B5:rvrCP279595-02:cvnFUJITSUSIEMENS:ct10:cvrS7110: dmi.product.name: LIFEBOOK S7110 dmi.sys.vendor: FUJITSU SIEMENS ** Affects: pulseaudio (Ubuntu) Importance: Undecided Assignee: larsruneholger nilsson (nilsson-holger) Status: New ** Tags: apport-bug i386 wily ** Changed in: pulseaudio (Ubuntu) Assignee: (unassigned) => larsruneholger nilsson (nilsson-holger) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1516166 Title: [HDA-Intel - HDA Intel, playback] Pulseaudio fails to detect card Status in pulseaudio package in Ubuntu: New Bug description: 00:1b.0 Audio device: Intel Corporation NM10/ICH7 Family High Definition Audio Controller (rev 02) Subsystem: Fujitsu Limited. Device 1397 Flags: bus master, fast devsel, latency 0, IRQ 29 Memory at f054 (64-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 2 Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00 Capabilities: [100] Virtual Channel Capabilities: [130] Root Complex Link Kernel driver in use: snd_hda_intel that was it says ! no drivers ? best regards holger ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: pulseaudio 1:6.0-0ubuntu13 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic i686 ApportVersion: 2.19.1-0ubuntu5 Architecture: i386 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', '/dev/snd/by-path', '/dev/snd/hwC0D1', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Fri Nov 13 23:15:59 2015 InstallationDate: Installed on 2015-08-11 (94 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel Title: [HDA-Intel - HDA Intel, playback] Pulseaudio fails to detect card UpgradeStatus: Upgraded to wily on 2015-11-11 (2 days ago) dmi.bios.date: 09/10/2008 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.35 dmi.board.name: FJNB1B5 dmi.board.vendor: FUJITSU dmi.board.version: CP279595-02 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU SIEMENS dmi.chassis.version: S7110 dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.35:bd09/10/2008:svnFUJITSUSIEMENS:pnLIFEBOOKS7110:pvr:rvnFUJITSU:rnFJNB1B5:rvrCP279595-02:cvnFUJITSUSIEMENS:ct10:cvrS7110: dmi.product.name: LIFEBOOK S7110 dmi.sys.vendor: FUJITSU SIEMENS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1516166/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1483586] Re: On demand cpufreq govneror causes large amounts of jitter
** Changed in: sysvinit (Ubuntu Trusty) Milestone: None => ubuntu-14.04.4 ** Summary changed: - On demand cpufreq govneror causes large amounts of jitter + On demand cpufreq governor causes large amounts of jitter -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1483586 Title: On demand cpufreq governor causes large amounts of jitter Status in sysvinit package in Ubuntu: Fix Released Status in sysvinit source package in Trusty: Triaged Status in sysvinit source package in Vivid: New Bug description: == Comment: #0 - Anton Blanchard - 2015-07-16 22:22:09 == We are seeing large amounts of jitter caused by od_dbs_timer(). We should slow down the rate of updates and or turn this into a timer. Having a workqueue execute so often is very noticeable. # echo 1 > /sys/kernel/debug/tracing/events/workqueue/workqueue_execute_start/enable (wait a while) # cat /sys/kernel/debug/trace <...>-67605 [040] 849622.393576: workqueue_execute_start: work struct c007fba1ba20: function od_dbs_timer <...>-67605 [040] 849622.403574: workqueue_execute_start: work struct c007fba1ba20: function od_dbs_timer <...>-116685 [048] 849622.403575: workqueue_execute_start: work struct c007fbc1ba20: function od_dbs_timer <...>-116685 [048] 849622.413574: workqueue_execute_start: work struct c007fbc1ba20: function od_dbs_timer <...>-67605 [040] 849622.413575: workqueue_execute_start: work struct c007fba1ba20: function od_dbs_timer <...>-67605 [040] 849622.423575: workqueue_execute_start: work struct c007fba1ba20: function od_dbs_timer <...>-116685 [048] 849622.433574: workqueue_execute_start: work struct c007fbc1ba20: function od_dbs_timer <...>-67605 [040] 849622.433574: workqueue_execute_start: work struct c007fba1ba20: function od_dbs_timer <...>-116685 [048] 849622.443573: workqueue_execute_start: work struct c007fbc1ba20: function od_dbs_timer == Comment: #1 - Shilpasri G. Bhat - 2015-07-22 19:42:38 == Hi Anton, We can set the governor's tunable 'sampling_down_factor' to decrease the rate of updates. When this tunable is set to a value greater than 1, the sampling period of the governor is increased during the peak load to sampling_period times sampling_down_factor. This will reduce the jitter caused by od_dbs_timer() when the cpu is busy. I am currently running benchmarks to find out the optimal value for this tunable and will post them soon. Thanks and Regards, Shilpa == Comment: #2 - Anton Blanchard - 2015-07-31 03:44:49 == FYI We are also seeing high levels of CPU consumed by this on a LAMP workload: 2.54% kworker/0:0 [kernel.kallsyms] [k] osq_lock | ---osq_lock | |--99.83%-- mutex_optimistic_spin | __mutex_lock_slowpath | mutex_lock | | | |--80.08%-- od_dbs_timer 2.5% of total CPU time spent in the od_dbs_timer mutex. == Comment: #3 - Anton Blanchard - 2015-07-31 06:00:45 == Hitting this on a customer setup, raising priority == Comment: #4 - Shilpasri G. Bhat - 2015-08-03 06:47:40 == I used `perf top` and `perf record` to observe the overhead caused by 'osq_lock'. Both with ebizzy and SPECPower's ssjb workload I am able to see an overhead of 0.03% caused by 'osq_lock' with default governor settings. With sampling_down_factor=100, (1second) I am able to see 0.00% of overhead by 'osq_lock'. So this might not be a good data point to showcase, but by reducing the od_dbs_timer interrupts we are guaranteed to decrease the overhead caused by 'osq_lock'. == Comment: #5 - VAIDYANATHAN SRINIVASAN - 2015-08-03 09:09:09 == Hi Anton, Thanks for opening the bz to track and fix this issue. Shilpa is trying different workarounds. Here is our plan: (1) Use sampling_down_factor and other tunables in current Ubuntu releases to workaround the issue or minimise the impact. (2) Redesign cpufreq subsystem on powerpc similar to intel pstate driver so that we can program timers and cancel them dynamically based on different utilization points. Target Ubuntu 16.04 and then backport to 14.04.x and other distros. (3) Enhance design for (2) buy estimating core level utilization without running timers in each thread and then decide the target PState (4) Explore hardware assist so that we can avoid per-core estimation in software but still be able to set per-core PState. We need to take an interrupt or work-queue only to change PState and not really for estimation of load.
Re: [Touch-packages] [Bug 1345682] Re: fsck on 24TB ext4 keeps crashing
FYI. There was about 15TB (back when I initially ran into the problem, maybe about 11-14TB) of hardlinks. The Hardlinks are used so that rsync can handle directory name changes and not have to copy the whole directory over again. Thus each file would have a hardlink. I estimate maybe 40K+ or 80K+ files (I'm not sure if rsync counter includes hardlinks or not, but there would have been more than 80K files according to rsync) the fsck would use up all available memory. Even if I added mega swap space, the program would use it all up. I'm not super techie on this, so I can add to my test a temporary removal of all the hardlinks after I resolve my own issue of getting a chassis to house all the harddrives. I don't expect to have much time to resolve my chassis problem within a month, but now that I know there are some possible workarounds, and path moving forward, I can try to raise the priority back on this issue. Don't expect quick turn around on my part, but I do need to get that file system back operational to get data off the drives so I eventually will need to get it to a state where I can do the fsck test. oh btw, when initially the file system was clean, fsck would work no problem as I tested that before using the system. It was after there was some file system problems that I later ran fsck and ran into problems. I don't know if these people who are successfully running fsck are doing so from a non-clean file system. On Fri, Nov 13, 2015 at 12:09 PM, Theodore Ts'o wrote: > There are plenty of people who *are* able to check file systems larger > than 16TB. So talking about it in terms "that problem" doesn't make much > sense. > > There is a known issue where if you are using a huge number of hard links > (if you are using a backup solution which uses hard links and a huge number > of parallel directory hierarchies) e2fsck uses a large amount of memory. I > don't know if that's what you are doing, but if that's what you are doing, > it wouldn't surprise me if you are running out of memory. You should have > gotten an explicit "you ran out of memory" error instead of a seg fault, > though. > > There is a way you can use scratch files for some of the data structures > that e2fsck needs to track all of the hard links; see the > "The [scratch_files] Stanza" section in the e2fsck.conf. However, this is > going to be *SLOW*.The primary use of this was for people who were > using 32-bit systems and who didn't have the address space for the memory > requirements for large file systems with a large number of hard links. > You may be better off just trying to configure our swap space. (All of > this is assuming the problem is that the file system has a very large > number of hard link farms. Have you confirmed that when you configured > 25GB of swap, that the system actually used that amount of swap)? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1345682 > > Title: > fsck on 24TB ext4 keeps crashing > > Status in e2fsprogs package in Ubuntu: > Incomplete > > Bug description: > date; fsck -vy /dev/mapper/raid61p1 ;date > Thu Jul 17 11:54:21 PDT 2014 > fsck from util-linux 2.20.1 > I can't get my ext4 24TB to fsck clean. there came a whole bunch of file > stat problems after a clean reboot. > I tried 3 times so far, and each does something like segfault. I looked > twice, and the errors were different, > but was able to capture one output. The system has 6GB ram, and it used > up all the memory. ended up adding 25GB > of swap as fsck seems to use up a huge amount of memory. After a long > while, usually after mem use is >90%, > I come back to see the fsck has crashed and file system is still not > clean. > > The reboot was clean and should not have caused any corruption. the > system is using ubuntu-14.04 > > # uname -a > Linux gigabyte133 3.13.0-32-generic #57-Ubuntu SMP Tue Jul 15 03:51:08 > UTC 2014 x86_64 x86_64 x86_64 GNU/Linux > root@gigabyte133:~# > > I had to use the 64 bit version since the 32 bit version I couldn't get > more than 15TB file system built and read > that there were compatibility problems between 32bit version with the -O > 64bit and the 64 bit version so just > built the whole thing in 64 bit ubuntu.. > > > e2fsck 1.42.9 (4-Feb-2014) > > > /dev/mapper/raid61p1 contains a file system with errors, check forced. > Pass 1: Checking inodes, blocks, and sizes > Inode 203167820 has compression flag set on filesystem without > compression support. Clear? yes > > Signal (11) SIGSEGV si_code=SI_KERNEL fault addr=(nil) > fsck.ext4[0x4266f1] > /lib/x86_64-linux-gnu/libc.so.6(+0x36ff0)[0x7fd38d087ff0] > /lib/x86_64-linux-gnu/libext2fs.so.2(ext2fs_rb_next+0x23)[0x7fd38dc7bc43] > /lib/x86_64-linux-gnu/libext2fs.so.2(+0x10670)[0x7fd38dc5e670] > fsck.ext4[0x4100f6]# lsb_release -va > No LSB modules are available. > Distributor ID: Ubuntu > Descriptio
[Touch-packages] [Bug 1515705] Re: [Desktop] Exiting fullscreen often hangs the window manager
I finally got my video drivers straightened out.. couldn't run with nvidia-346 but after reinstalling nvidia-340 I'm able to run webbrowser- app again. In testing fullscreen, everything working fine for me. I cannot get a WM crash entering/exiting fullscreen on either the site referenced above or youtube. Will keep trying but for me it's working. I'm on vivid desktop with packages from the overlay ppa installed. -- 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/1515705 Title: [Desktop] Exiting fullscreen often hangs the window manager Status in webbrowser-app package in Ubuntu: New Bug description: I’ve started seeing that on my desktop machine running up-to-date wily, with webbrowser-app built from trunk. If I browse to e.g. http://blogs.sitepointstatic.com/examples/tech/full-screen/index.html, click the squirrel to make it fullscreen, then click again to exit fullscreen, more often than not the window manager (compiz) hangs and becomes unresponsive to mouse/keyboard events (this happens also when running the fullscreen autopilot tests). When that happens, killing the app doesn’t restore the window manager’s responsiveness, the only fix I’ve found is to kill compiz. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1515705/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1492088] Re: juju bootstrap fails inside a wily container
Opening up a systemd record so that team can take a look.
** 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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1492088
Title:
juju bootstrap fails inside a wily container
Status in juju-core:
Triaged
Status in systemd package in Ubuntu:
New
Bug description:
Running juju 1.24.5 and attempting to do a local bootstrap inside a
wily container fails with the following:
[DEBUG: 09-03 20:49:56, container.py:139] Error with command: [Output]
'2015-09-03 20:49:35 INFO juju.cmd supercommand.go:37 running juju
[1.24.5-wily-amd64 gc]
2015-09-03 20:49:35 DEBUG juju.environs.configstore disk.go:109 Made
dir /home/ubuntu/.cloud-install/juju/environments
2015-09-03 20:49:35 INFO juju.provider.local environprovider.go:245
checking state port
2015-09-03 20:49:35 INFO juju.provider.local environprovider.go:245
checking API port
2015-09-03 20:49:35 INFO juju.provider.local environprovider.go:38
opening environment "local"
2015-09-03 20:49:35 DEBUG juju.container.kvm kvm.go:71 kvm-ok output:
INFO: /dev/kvm exists
KVM acceleration can be used
2015-09-03 20:49:35 DEBUG juju.provider.local environ.go:325 found
"10.0.6.1" as address for "lxcbr0"
2015-09-03 20:49:35 DEBUG juju.environs.configstore disk.go:308
writing jenv file
2015-09-03 20:49:35 DEBUG juju.environs.configstore disk.go:432
writing jenv file to /home/ubuntu/.cloud-
install/juju/environments/local.jenv
2015-09-03 20:49:35 INFO juju.network network.go:194 setting prefer-
ipv6 to false
2015-09-03 20:49:35 INFO juju.cmd cmd.go:113 Bootstrapping environment
"local"
2015-09-03 20:49:35 DEBUG juju.environs.bootstrap bootstrap.go:98
environment "local" supports service/machine networks: false
2015-09-03 20:49:35 DEBUG juju.environs.bootstrap bootstrap.go:100
network management by juju enabled: true
2015-09-03 20:49:35 DEBUG juju.provider.local environ.go:325 found
"10.0.6.1" as address for "lxcbr0"
2015-09-03 20:49:35 INFO juju.cmd cmd.go:113 Starting new instance for
initial state server
2015-09-03 20:49:35 INFO juju.environs.bootstrap bootstrap.go:184
newest version: 1.24.5.1
2015-09-03 20:49:36 INFO juju.environs.bootstrap bootstrap.go:212
picked bootstrap tools version: 1.24.5.1
2015-09-03 20:49:36 INFO juju.cmd cmd.go:113 Building tools to upload
(1.24.5.1-wily-amd64)
2015-09-03 20:49:36 DEBUG juju.environs.sync sync.go:304 Building
tools
2015-09-03 20:49:36 DEBUG juju.environs.tools build.go:122 looking
for: juju
2015-09-03 20:49:36 DEBUG juju.environs.tools build.go:161 checking:
/usr/bin/jujud
2015-09-03 20:49:36 INFO juju.environs.tools build.go:167 found
existing jujud
2015-09-03 20:49:36 INFO juju.environs.tools build.go:177 target: /tmp
/juju-tools782467678/jujud
2015-09-03 20:49:36 DEBUG juju.environs.tools build.go:232 forcing
version to 1.24.5.1
2015-09-03 20:49:36 DEBUG juju.environs.tools build.go:38 adding
entry: &tar.Header{Name:"FORCE-VERSION", Mode:436, Uid:0, Gid:0,
Size:8, ModTime:time.Time{sec:63576910176, nsec:90190527,
loc:(*time.Location)(0x2c9b140)}, Typeflag:0x30, Linkname:"",
Uname:"ubuntu", Gname:"ubuntu", Devmajor:0, Devminor:0,
AccessTime:time.Time{sec:63576910176, nsec:90190527,
loc:(*time.Location)(0x2c9b140)},
ChangeTime:time.Time{sec:63576910176, nsec:90190527,
loc:(*time.Location)(0x2c9b140)}, Xattrs:map[string]string(nil)}
2015-09-03 20:49:36 DEBUG juju.environs.tools build.go:38 adding
entry: &tar.Header{Name:"jujud", Mode:493, Uid:0, Gid:0,
Size:67623560, ModTime:time.Time{sec:63576910176, nsec:90190527,
loc:(*time.Location)(0x2c9b140)}, Typeflag:0x30, Linkname:"",
Uname:"ubuntu", Gname:"ubuntu", Devmajor:0, Devminor:0,
AccessTime:time.Time{sec:63576910176, nsec:90190527,
loc:(*time.Location)(0x2c9b140)},
ChangeTime:time.Time{sec:63576910176, nsec:90190527,
loc:(*time.Location)(0x2c9b140)}, Xattrs:map[string]string(nil)}
2015-09-03 20:49:42 INFO juju.environs.sync sync.go:323 built tools
1.24.5.1-wily-amd64 (13769kB)
2015-09-03 20:49:42 INFO juju.cmd cmd.go:113 Installing Juju agent on
bootstrap instance
2015-09-03 20:49:42 DEBUG juju.cloudconfig.instancecfg
instancecfg.go:521 Setting numa ctl preference to false
2015-09-03 20:49:42 INFO juju.provider.local environ.go:156 local
provider; disabling refreshing OS updates.
2015-09-03 20:49:42 INFO juju.provider.local environ.go:162 local
provider; disabling OS upgrades.
Logging to /home/ubuntu/.cloud-install/juju/local/cloud-init-
output.log on remote host
Installing package: curl
Installing package: cpu-checker
Installing package: bridge-utils
Installing package: rsyslog-gnutls
Installing package: cloud-utils
Installing package: cloud-image-utils
Installing package
[Touch-packages] [Bug 1516153] [NEW] Wifi does not work after suspending.
Public bug reported: After resuming from a suspend, sometimes(very often) the wifi does not show any connections. Even if i uncheck and recheck the Enable wifi checkbox it still does not show any connections. I am using Ubuntu 15.10. NetworkManager is at version 1.0.4. My hardware is a Asus X750J. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: network-manager 1.0.4-0ubuntu5.1 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 Date: Fri Nov 13 22:07:24 2015 ExecutablePath: /usr/sbin/NetworkManager IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-10-27 (17 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH enp3s0 ethernet connected /org/freedesktop/NetworkManager/Devices/0 Wired connection 1 a6283be3-2692-4d49-87d6-4c2f7cf00e2f /org/freedesktop/NetworkManager/ActiveConnection/4 tun0tun connected /org/freedesktop/NetworkManager/Devices/3 tun08a335ba2-ebce-4e08-9431-d8a4322cfa26 /org/freedesktop/NetworkManager/ActiveConnection/5 wlp2s0 wifi disconnected /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- 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 wily -- 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/1516153 Title: Wifi does not work after suspending. Status in network-manager package in Ubuntu: New Bug description: After resuming from a suspend, sometimes(very often) the wifi does not show any connections. Even if i uncheck and recheck the Enable wifi checkbox it still does not show any connections. I am using Ubuntu 15.10. NetworkManager is at version 1.0.4. My hardware is a Asus X750J. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: network-manager 1.0.4-0ubuntu5.1 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 Date: Fri Nov 13 22:07:24 2015 ExecutablePath: /usr/sbin/NetworkManager IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-10-27 (17 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH enp3s0 ethernet connected /org/freedesktop/NetworkManager/Devices/0 Wired connection 1 a6283be3-2692-4d49-87d6-4c2f7cf00e2f /org/freedesktop/NetworkManager/ActiveConnection/4 tun0tun connected /org/freedesktop/NetworkManager/Devices/3 tun08a335ba2-ebce-4e08-9431-d8a4322cfa26 /org/freedesktop/NetworkManager/ActiveConnection/5 wlp2s0 wifi disconnected /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- 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/1516153/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1509622] Re: Xorg crash
OK, I was going to publish a new bug report last night after it happened again with Kodi (bios update didn't fix it), but I got a notice of new updates which included a kernel 4.2-19 and display manager update, so hopefully it is a known issue that was fixed there. -- 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/1509622 Title: Xorg crash Status in xorg package in Ubuntu: Incomplete Bug description: This is the full apport data from the crash reported as bug #1507461. It occurred whilst watching a full-screen Flash video in Google Chrome. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Oct 24 18:04:11 2015 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21fa] MachineType: LENOVO CTO ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-16-generic root=/dev/mapper/peleg0-lv01 ro splash quiet nomdmonddf nomdmonisw vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/24/2012 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET33WW (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: CTO 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:bvrG2ET33WW(1.13):bd07/24/2012:svnLENOVO:pnCTO:pvrThinkPadX230:rvnLENOVO:rnCTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Sat Oct 24 17:58:31 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 728 vendor LGD xserver.version: 2:1.17.2-1ubuntu9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1509622/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1516133] Re: package apport 2.14.1-0ubuntu3.18 failed to install/upgrade: el subproceso script pre-removal nuevo devolvió el código de salida de error 1
** Description changed: I have a lot of problems in my laptop with ubuntu 14.04.3 LTS and 15.10 too. Actually Libre Office Writter doesn't work. Sometimes it depends when i put in on my laptop appairs ACPI PCC Probe failed and sometimes say don't find hard disk sometimes thunderbird fails + ubuntu software center doesn't work and sometimes i can't write any file. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: apport 2.14.1-0ubuntu3.18 ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7 Uname: Linux 3.19.0-33-generic i686 ApportLog: ApportVersion: 2.14.1-0ubuntu3.18 Architecture: i386 Date: Fri Nov 13 20:38:45 2015 DuplicateSignature: package:apport:2.14.1-0ubuntu3.18:el subproceso script pre-removal nuevo devolvió el código de salida de error 1 ErrorMessage: el subproceso script pre-removal nuevo devolvió el código de salida de error 1 InstallationDate: Installed on 2015-11-01 (12 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805) PackageArchitecture: all RelatedPackageVersions: dpkg 1.17.5ubuntu5.4 apt 1.0.1ubuntu2.10 SourcePackage: apport Title: package apport 2.14.1-0ubuntu3.18 failed to install/upgrade: el subproceso script pre-removal nuevo devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1516133 Title: package apport 2.14.1-0ubuntu3.18 failed to install/upgrade: el subproceso script pre-removal nuevo devolvió el código de salida de error 1 Status in apport package in Ubuntu: New Bug description: I have a lot of problems in my laptop with ubuntu 14.04.3 LTS and 15.10 too. Actually Libre Office Writter doesn't work. Sometimes it depends when i put in on my laptop appairs ACPI PCC Probe failed and sometimes say don't find hard disk sometimes thunderbird fails ubuntu software center doesn't work and sometimes i can't write any file. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: apport 2.14.1-0ubuntu3.18 ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7 Uname: Linux 3.19.0-33-generic i686 ApportLog: ApportVersion: 2.14.1-0ubuntu3.18 Architecture: i386 Date: Fri Nov 13 20:38:45 2015 DuplicateSignature: package:apport:2.14.1-0ubuntu3.18:el subproceso script pre-removal nuevo devolvió el código de salida de error 1 ErrorMessage: el subproceso script pre-removal nuevo devolvió el código de salida de error 1 InstallationDate: Installed on 2015-11-01 (12 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805) PackageArchitecture: all RelatedPackageVersions: dpkg 1.17.5ubuntu5.4 apt 1.0.1ubuntu2.10 SourcePackage: apport Title: package apport 2.14.1-0ubuntu3.18 failed to install/upgrade: el subproceso script pre-removal nuevo devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1516133/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1515995] Re: Screen
While I've been watching videos online, they haven't flickered, but they have had tears in them. -- 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/1515995 Title: Screen Status in xorg package in Ubuntu: New Bug description: I am trying out Kubuntu at the moment and I have noticed that when watching videos they flicker. I have tried the different options in the 'Compositor Settings for Desktop Effects' Tearing Prevention and none seem to make a difference other than that if I put it on automatic, the top half of the screen flickers, and with 'full screen repaints' the whole screen flickers. I have tried the official Nvidia driver (352), the one from software centre and the default one - all make the video flicker in full screen. I had the same problem while using Linux Mint Mate, but not while using the Cinnamon Desktop, I also don't remember the problem occurring while using Ubuntu Unity Desktop. I am fairly new to Linux so I don't know too much about how to go about finding out the problem. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 352.41 Fri Aug 21 23:09:52 PDT 2015 GCC version: gcc version 5.2.1 20151010 (Ubuntu 5.2.1-22ubuntu2) ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 BootLog: fsck from util-linux 2.26.2 /dev/sdb2: clean, 266511/13574144 files, 7382798/54296320 blocks CurrentDesktop: KDE Date: Fri Nov 13 12:47:42 2015 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: kubuntu DkmsStatus: bbswitch, 0.7, 4.2.0-18-generic, x86_64: installed nvidia-352-updates, 352.41, 4.2.0-18-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GK104 [GeForce GTX 760] [10de:1187] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation Device [10de:0984] InstallationDate: Installed on 2015-11-12 (0 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: MSI MS-7850 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic.efi.signed root=UUID=43b80561-2236-4234-9459-091517df6ac9 ro quiet splash vt.handoff=7 SourcePackage: xorg UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/21/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.8 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-G41 PC Mate(MS-7850) 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.8:bd07/21/2014:svnMSI:pnMS-7850:pvr1.0:rvnMSI:rnZ87-G41PCMate(MS-7850):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7850 dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Fri Nov 13 10:44:18 2015 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.17.2-1ubuntu9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1515995/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1347788] Re: find crashed when current working directory is not readable and -exec or -execdir used
I also reviewed the upstream patch that purports to resolve the issue
(7dc7006). This fix is contained within the 4.5.9 and newer versions of
findutils. That's where the good news ends. The code portion of that
single commit is 817 lines long. It doesn't apply cleanly, and it
appears to have some significant dependencies on earlier commits.
Unfortunately backportting the fix into even wily sources is proving
difficult, and may not be acceptable for a stable release. Normally in
this case we would integrate the entire upstream sources into our
development series (xenial), and then pursue package copy into the older
series. However, 4.5.9 and newer is currently part of the findutils
alpha branch, and as such wouldn't be considered acceptable for
inclusion in even our development releases.
That being said fedora, opensuse, and centos all release with 4.5 of
findutils, so we may have to consider doing the same.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to findutils in Ubuntu.
https://bugs.launchpad.net/bugs/1347788
Title:
find crashed when current working directory is not readable and -exec
or -execdir used
Status in findutils package in Ubuntu:
Confirmed
Bug description:
bug is similar to https://savannah.gnu.org/bugs/?15384 but for current
directory (when it not readable or not executable)
steps to reproduce
DIR=`mktemp -d`
cd $DIR
mkdir -p 1/1 2
cd 2
find $DIR/1 -type d -exec echo {} \;
find $DIR/1 -type d -execdir echo {} \;
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: findutils 4.4.2-7
Uname: Linux 3.15.4-031504-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Jul 23 20:17:19 2014
Dependencies:
gcc-4.9-base 4.9-20140406-0ubuntu1
libc6 2.19-0ubuntu6
libgcc1 1:4.9-20140406-0ubuntu1
multiarch-support 2.19-0ubuntu6
InstallationDate: Installed on 2014-04-24 (89 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
SourcePackage: findutils
UpgradeStatus: No upgrade log present (probably fresh install)
---
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CurrentDesktop: GNOME
Dependencies:
gcc-4.9-base 4.9-20140406-0ubuntu1
libc6 2.19-0ubuntu6
libgcc1 1:4.9-20140406-0ubuntu1
multiarch-support 2.19-0ubuntu6
DistroRelease: Ubuntu 14.04
InstallationDate: Installed on 2014-04-24 (89 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
Package: findutils 4.4.2-7
PackageArchitecture: amd64
Tags: trusty
Uname: Linux 3.15.4-031504-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/findutils/+bug/1347788/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1433013] Re: Super -> exec vs Alt-F2 -> exec have different environment
** No longer affects: unity-lens-applications (Ubuntu) ** Project changed: unity => ubuntu-translations ** No longer affects: ubuntu-translations ** No longer affects: unity (Ubuntu) ** Changed in: upstart (Ubuntu Trusty) Importance: Undecided => Medium ** Changed in: upstart (Ubuntu Utopic) Importance: Undecided => Medium ** Changed in: upstart (Ubuntu Vivid) Importance: Undecided => Medium -- 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/1433013 Title: Super -> exec vs Alt-F2 -> exec have different environment Status in upstart package in Ubuntu: Confirmed Status in upstart source package in Trusty: Confirmed Status in upstart source package in Utopic: Confirmed Status in upstart source package in Vivid: Confirmed Bug description: upstart in user session manages environmental variables and most things have them, however Alt-f2 started proccesses lack them. to test Super Key -> "xterm" -> Enter -> env | grep SSH vs Alt+F2 -> "xterm" -> Enter -> env | grep SSH via Super Key -> the environment is correct via Alt-F2 -> it is not I believe Alt+F2 code path should call into upstart dbus api to "list-env" and import that environment before executing the search result. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1433013/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1515561] Re: Windows flash black briefly before being drawn
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gtk+3.0 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1515561 Title: Windows flash black briefly before being drawn Status in GTK+: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: Since 3.18, windows flash black for a split second before they are drawn. It's visually disruptive. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1515561/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1347788] Re: find crashed when current working directory is not readable and -exec or -execdir used
I opened
https://savannah.gnu.org/bugs/index.php?46438
against upstream findutils to see if we can't get them to to a blessed release
of 4.5 of findutils.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to findutils in Ubuntu.
https://bugs.launchpad.net/bugs/1347788
Title:
find crashed when current working directory is not readable and -exec
or -execdir used
Status in findutils package in Ubuntu:
Confirmed
Bug description:
bug is similar to https://savannah.gnu.org/bugs/?15384 but for current
directory (when it not readable or not executable)
steps to reproduce
DIR=`mktemp -d`
cd $DIR
mkdir -p 1/1 2
cd 2
find $DIR/1 -type d -exec echo {} \;
find $DIR/1 -type d -execdir echo {} \;
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: findutils 4.4.2-7
Uname: Linux 3.15.4-031504-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Jul 23 20:17:19 2014
Dependencies:
gcc-4.9-base 4.9-20140406-0ubuntu1
libc6 2.19-0ubuntu6
libgcc1 1:4.9-20140406-0ubuntu1
multiarch-support 2.19-0ubuntu6
InstallationDate: Installed on 2014-04-24 (89 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
SourcePackage: findutils
UpgradeStatus: No upgrade log present (probably fresh install)
---
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CurrentDesktop: GNOME
Dependencies:
gcc-4.9-base 4.9-20140406-0ubuntu1
libc6 2.19-0ubuntu6
libgcc1 1:4.9-20140406-0ubuntu1
multiarch-support 2.19-0ubuntu6
DistroRelease: Ubuntu 14.04
InstallationDate: Installed on 2014-04-24 (89 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
Package: findutils 4.4.2-7
PackageArchitecture: amd64
Tags: trusty
Uname: Linux 3.15.4-031504-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/findutils/+bug/1347788/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1443900] Re: [address book] Can't change adress book storage source
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: address-book-app (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to address-book-app in Ubuntu. https://bugs.launchpad.net/bugs/1443900 Title: [address book] Can't change adress book storage source Status in Ubuntu UX: Triaged Status in address-book-app package in Ubuntu: Confirmed Bug description: Steps: * Launch system-setting * Go in account and add a Google account * Launch Adress-book * Add a new contact * There is a select composent to choose between Local(Personnal) or Google(with your gmail alias) * The contact is added * You want to change (from GUI, no CLI) the storage of the contact * Edit the contact * Can't find the same Select composent to be able to migrate the contact from a source to another To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1443900/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1480877] Re: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: qtbase-opensource-src (Ubuntu) Status: New => Confirmed -- 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/1480877 Title: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices Status in Canonical System Image: Confirmed Status in Unity 8: New Status in indicator-network package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Incomplete Status in qtbase-opensource-src package in Ubuntu: Confirmed Status in buteo-syncfw package in Ubuntu RTM: New Status in location-service package in Ubuntu RTM: Triaged Status in maliit-framework package in Ubuntu RTM: New Status in network-manager package in Ubuntu RTM: Incomplete Status in sync-monitor package in Ubuntu RTM: New Bug description: Krillin, rc-proposed, r83 DESCRIPTION: I've been trying to track down the cause of the occasional UI freezes on my Krillin device, and I noticed that whenever the UI freezes for 2-4 seconds, I get a burst of "PropertiesChanged" signals in dbus-monitor Here's a log of what's shown in dbus-monitor: http://pastebin.ubuntu.com/11992322/ I'd guess the problem is in the code that actually catches the signals and acts accordingly. HOW TO REPRODUCE: 1) Move to a place where many wifi hotspots are available 2) Connect the device via USB and run "phablet-shell" and then "dbus-monitor" 3) Use the device while keeping an eye on dbus-monitor output To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1480877/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
I noticed that when I have the camera-app opened and then lock and unlock the krillin, the camera is not doing auto focus any more as it was doing that few builds ago. -- 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: Confirmed 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/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 1404188] Re: QNetworkSession::isOpen() always returns false
A couple of comments. I've actually been chasing down a DBus performance issue on touch since mid-Summer, related to NetworkManager and WiFi scanning. The high-level summary is that we have a number of system processes listening for NM AccessPoint DBus signals on specific AccessPoint DBus objects, and never cleaning up the associated DBus watch rules when the access points are removed. This can lead to a single processing adding 5k match rules to the system bus if WiFi is enabled long enough. For details see bug #1480877, an in particular from the following comment onwards: https://bugs.launchpad.net/ubuntu-rtm/+source/sync- monitor/+bug/1480877/comments/65 I've traced what I think is the cause to the bearer mgmt networkmanager plugin and am attempting to patch it. Note, this bug that I'm now adding this comment to, is about a confined app's usage of QNetworkSession. I should remind folks that there are a number of system processes ( eg. unity8 ) that either use QNetworkSession directly, or via QNetworkAccessManager, so we'll need to be careful we don't break anything if we decide to deprecate the networkmanager backend in favor of a connectivity API based backend. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor-easyprof-ubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1404188 Title: QNetworkSession::isOpen() always returns false Status in Canonical System Image: Confirmed Status in apparmor-easyprof-ubuntu package in Ubuntu: Confirmed Status in qtbase-opensource-src package in Ubuntu: Confirmed Bug description: Using QNetworkSession::isOpen() in confined apps on a phone running vivid always returns false. This might be an apparmor thing, however, I couldn't find any REJECTED entries in log files. The test app in lp:~mzanetti/+junk/nmsessiontest can reproduce the issue. Open this project in ubuntu-sdk's qtcreator and run it on a vivid device. Press the button and watch the debug prints. On a vivid-desktop or a RTM based phone it will print "all is well". On a vivid phone however, it'll print "network session not open..." This used to work fine at least back in utopic images. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1404188/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1345682] Re: fsck on 24TB ext4 keeps crashing
There are plenty of people who *are* able to check file systems larger than 16TB. So talking about it in terms "that problem" doesn't make much sense. There is a known issue where if you are using a huge number of hard links (if you are using a backup solution which uses hard links and a huge number of parallel directory hierarchies) e2fsck uses a large amount of memory. I don't know if that's what you are doing, but if that's what you are doing, it wouldn't surprise me if you are running out of memory. You should have gotten an explicit "you ran out of memory" error instead of a seg fault, though. There is a way you can use scratch files for some of the data structures that e2fsck needs to track all of the hard links; see the "The [scratch_files] Stanza" section in the e2fsck.conf. However, this is going to be *SLOW*.The primary use of this was for people who were using 32-bit systems and who didn't have the address space for the memory requirements for large file systems with a large number of hard links. You may be better off just trying to configure our swap space. (All of this is assuming the problem is that the file system has a very large number of hard link farms. Have you confirmed that when you configured 25GB of swap, that the system actually used that amount of swap)? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1345682 Title: fsck on 24TB ext4 keeps crashing Status in e2fsprogs package in Ubuntu: Incomplete Bug description: date; fsck -vy /dev/mapper/raid61p1 ;date Thu Jul 17 11:54:21 PDT 2014 fsck from util-linux 2.20.1 I can't get my ext4 24TB to fsck clean. there came a whole bunch of file stat problems after a clean reboot. I tried 3 times so far, and each does something like segfault. I looked twice, and the errors were different, but was able to capture one output. The system has 6GB ram, and it used up all the memory. ended up adding 25GB of swap as fsck seems to use up a huge amount of memory. After a long while, usually after mem use is >90%, I come back to see the fsck has crashed and file system is still not clean. The reboot was clean and should not have caused any corruption. the system is using ubuntu-14.04 # uname -a Linux gigabyte133 3.13.0-32-generic #57-Ubuntu SMP Tue Jul 15 03:51:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux root@gigabyte133:~# I had to use the 64 bit version since the 32 bit version I couldn't get more than 15TB file system built and read that there were compatibility problems between 32bit version with the -O 64bit and the 64 bit version so just built the whole thing in 64 bit ubuntu.. e2fsck 1.42.9 (4-Feb-2014) /dev/mapper/raid61p1 contains a file system with errors, check forced. Pass 1: Checking inodes, blocks, and sizes Inode 203167820 has compression flag set on filesystem without compression support. Clear? yes Signal (11) SIGSEGV si_code=SI_KERNEL fault addr=(nil) fsck.ext4[0x4266f1] /lib/x86_64-linux-gnu/libc.so.6(+0x36ff0)[0x7fd38d087ff0] /lib/x86_64-linux-gnu/libext2fs.so.2(ext2fs_rb_next+0x23)[0x7fd38dc7bc43] /lib/x86_64-linux-gnu/libext2fs.so.2(+0x10670)[0x7fd38dc5e670] fsck.ext4[0x4100f6]# lsb_release -va No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 14.04 LTS Release:14.04 Codename: trusty /lib/x86_64-linux-gnu/libext2fs.so.2(+0x11c3d)[0x7fd38dc5fc3d] /lib/x86_64-linux-gnu/libext2fs.so.2(+0x11f78)[0x7fd38dc5ff78] /lib/x86_64-linux-gnu/libext2fs.so.2(ext2fs_block_iterate3+0xa13)[0x7fd38dc60b13] fsck.ext4[0x4115c4] fsck.ext4[0x412699] fsck.ext4[0x412761] /lib/x86_64-linux-gnu/libext2fs.so.2(ext2fs_get_next_inode_full+0x59)[0x7fd38dc6c9a9] fsck.ext4(e2fsck_pass1+0x8d8)[0x4130c8] fsck.ext4(e2fsck_run+0x52)[0x40deb2] fsck.ext4(main+0xd27)[0x40a0e7] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7fd38d072ec5] fsck.ext4[0x40bde6] Thu Jul 17 15:55:01 PDT 2014 # lsb_release -va No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 14.04 LTS Release:14.04 Codename: trusty ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: util-linux 2.20.1-5.1ubuntu20.1 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.14.1-0ubuntu
[Touch-packages] [Bug 1516136] [NEW] deleted contacts appear on the search result
Public bug reported: How to reproduce: 1 - Create a new contact with the phone number "123" and store it on your local address-book 2 - Delete this contact 3 - Search for "123" Expected: The deleted contact does not appear on the list Current: The deleted contact appear on the results. ** Affects: address-book-service (Ubuntu) Importance: High Assignee: Renato Araujo Oliveira Filho (renatofilho) Status: New ** Changed in: address-book-service (Ubuntu) Assignee: (unassigned) => Renato Araujo Oliveira Filho (renatofilho) ** Changed in: address-book-service (Ubuntu) Importance: Undecided => High ** Branch linked: lp:~renatofilho/address-book-service/fix-deleted-on- favorite-list -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to address-book-service in Ubuntu. https://bugs.launchpad.net/bugs/1516136 Title: deleted contacts appear on the search result Status in address-book-service package in Ubuntu: New Bug description: How to reproduce: 1 - Create a new contact with the phone number "123" and store it on your local address-book 2 - Delete this contact 3 - Search for "123" Expected: The deleted contact does not appear on the list Current: The deleted contact appear on the results. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/address-book-service/+bug/1516136/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1514623] Re: New upstream bugfix release 1.0.8 (LXC MRE)
Hello Stéphane, or anyone else affected, Accepted lxc into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/lxc/1.0.8-0ubuntu0.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: lxc (Ubuntu Trusty) Status: In Progress => Fix Committed ** Tags removed: verification-failed ** Tags added: verification-needed -- 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/1514623 Title: New upstream bugfix release 1.0.8 (LXC MRE) Status in lxc package in Ubuntu: Fix Released Status in lxc source package in Trusty: Fix Committed Bug description: We have released LXC 1.0.8 upstream: https://linuxcontainers.org/lxc/news This will be the eigth upstream bugfix release to hit trusty. The upstream changes are detailed at the URL above. The MRE was reviewed by Martin Pitt here: https://lists.ubuntu.com/archives/technical- board/2014-April/001869.html As for testing, this version went through both automated testing (all the tests present in lxc-tests + the python3 API tests) as well as manual testing done by myself, LXC contributors and LXC users who've been building the git stable branch for a while now. Xenial is now on LXC 1.1.5 (and 1.1.5 will hit vivid and wily as SRU) which bugfixes for 1.0.8 have been taken from. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1514623/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1515463] Re: Broken juju LXC deployments
Hello Brad, or anyone else affected,
Accepted lxc into trusty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/lxc/1.0.8-0ubuntu0.2
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Your feedback will aid us getting this update
out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed. In either case, details of your testing will help
us make a better decision.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance!
** Changed in: lxc (Ubuntu Trusty)
Status: In Progress => Fix Committed
--
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/1515463
Title:
Broken juju LXC deployments
Status in lxc package in Ubuntu:
Fix Committed
Status in lxc source package in Trusty:
Fix Committed
Status in lxc source package in Vivid:
Fix Committed
Status in lxc source package in Wily:
Fix Committed
Status in lxc source package in Xenial:
Fix Committed
Bug description:
I've just tried using juju to deploy to a container with trusty-
proposed repo enabled, and I get an error message about 'failed to
retrieve the template to clone'. The underlying error appears to be:
tar --numeric-owner -xpJf
/var/cache/lxc/cloud-trusty/ubuntu-14.04-server-cloudimg-amd64-root.tar.gz;
xz: (stdin): File format not recognized; tar: Child returned status 1; tar:
Error is not recoverable: exiting now;
This seems to be fairly obvious, trying to use xz on a tar.gz file is
never going to work.
The change appears to be from
https://github.com/lxc/lxc/commit/27c278a76931bfc4660caa85d1942ca91c86e0bf,
it assumes everything passed into it will be a .tar.xz file.
This appears to be a conflict between the template expecting a .tar.xz
file, and juju providing it a .tar.gz file. You can see what juju is
providing from:
$ ubuntu-cloudimg-query trusty released amd64 --format %{url}
https://cloud-images.ubuntu.com/server/releases/trusty/release-20151105/ubuntu-14.04-server-cloudimg-amd64.tar.gz
From the juju deployed host:
$ apt-cache policy lxc-templates
lxc-templates:
Installed: 1.0.8-0ubuntu0.1
Candidate: 1.0.8-0ubuntu0.1
Version table:
*** 1.0.8-0ubuntu0.1 0
500 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64
Packages
100 /var/lib/dpkg/status
From the host running juju:
$ apt-cache policy juju-core
juju-core:
Installed: 1.22.8-0ubuntu1~14.04.1
Candidate: 1.25.0-0ubuntu1~14.04.1~juju1
Version table:
1.25.0-0ubuntu1~14.04.1~juju1 0
500 http://ppa.launchpad.net/juju/proposed/ubuntu/ trusty/main amd64
Packages
*** 1.22.8-0ubuntu1~14.04.1 0
400 http://archive.ubuntu.com/ubuntu/ trusty-proposed/universe amd64
Packages
100 /var/lib/dpkg/status
All machine involved are running trusty:
$ lsb_release -rd
Description:Ubuntu 14.04.3 LTS
Release:14.04
Please let me know if you need any more information.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1515463/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1429140] Re: lxc-net upstart script fails on nonexistent iptables rules
Hello Daniel, or anyone else affected, Accepted lxc into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/lxc/1.0.8-0ubuntu0.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Tags removed: verification-done ** Tags added: verification-needed -- 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/1429140 Title: lxc-net upstart script fails on nonexistent iptables rules Status in lxc package in Ubuntu: Fix Released Status in lxc source package in Trusty: Fix Committed Bug description: Hello, On Trusty, the stop of lxc-net fails if the iptables rules are not present. I added “exec >> /tmp/lxc-net.log 2>&1” at the beginning of pre-start and post-stop and get: iptables: Bad rule (does a matching rule exist in that chain?). On Precise, a “|| true” was added to avoid errors. I attach a patch to disable exit on failing iptables call. Regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1429140/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1512323] Re: devices on devel-proposed/ubuntu do not boot with systemd 227-2ubuntu1
Well, no guarantee of alignment > 1 byte. There is a guarantee of 1 byte alignment. -- 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/1512323 Title: devices on devel-proposed/ubuntu do not boot with systemd 227-2ubuntu1 Status in Canonical System Image: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: Last known good build: mako devel-proposed/ubuntu r336 Affects builds from devel-proposed/ubuntu starting from first Xenial build. Test Case: Boot in fastboot mode and flash with: $ ubuntu-device-flash -v touch --channel=ubuntu-touch/devel-proposed/ubuntu --bootstrap or upgrade from 336 to latest devel-proposed image Actual Result During a successful flashing operation of a device from fastboot, it boots once into recovery, then reboots and a rotating Ubuntu logo is displayed while the devices is being flashed. With this issue, on the second stage of the flash the phone is stuck on the vendor's logo (google or bq) and the rotating ubuntu logo is never displayed. Same problem on krillin devel-proposed/krillin.en 235 Workaround: Boot into recovery, mount the system partition and downgrade systemd to 225-1ubuntu9 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1512323/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1512323] Re: devices on devel-proposed/ubuntu do not boot with systemd 227-2ubuntu1
In the failing case, the argument to le64toh() is a result returned by basename(). Yeah, no guarantee of alignment >= 1 byte when taking a pointer into the middle of a filename. -- 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/1512323 Title: devices on devel-proposed/ubuntu do not boot with systemd 227-2ubuntu1 Status in Canonical System Image: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: Last known good build: mako devel-proposed/ubuntu r336 Affects builds from devel-proposed/ubuntu starting from first Xenial build. Test Case: Boot in fastboot mode and flash with: $ ubuntu-device-flash -v touch --channel=ubuntu-touch/devel-proposed/ubuntu --bootstrap or upgrade from 336 to latest devel-proposed image Actual Result During a successful flashing operation of a device from fastboot, it boots once into recovery, then reboots and a rotating Ubuntu logo is displayed while the devices is being flashed. With this issue, on the second stage of the flash the phone is stuck on the vendor's logo (google or bq) and the rotating ubuntu logo is never displayed. Same problem on krillin devel-proposed/krillin.en 235 Workaround: Boot into recovery, mount the system partition and downgrade systemd to 225-1ubuntu9 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1512323/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1516133] [NEW] package apport 2.14.1-0ubuntu3.18 failed to install/upgrade: el subproceso script pre-removal nuevo devolvió el código de salida de error 1
Public bug reported: I have a lot of problems in my laptop with ubuntu 14.04.3 LTS and 15.10 too. Actually Libre Office Writter doesn't work. Sometimes it depends when i put in on my laptop appairs ACPI PCC Probe failed and sometimes say don't find hard disk sometimes thunderbird fails and sometimes i can't write any file. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: apport 2.14.1-0ubuntu3.18 ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7 Uname: Linux 3.19.0-33-generic i686 ApportLog: ApportVersion: 2.14.1-0ubuntu3.18 Architecture: i386 Date: Fri Nov 13 20:38:45 2015 DuplicateSignature: package:apport:2.14.1-0ubuntu3.18:el subproceso script pre-removal nuevo devolvió el código de salida de error 1 ErrorMessage: el subproceso script pre-removal nuevo devolvió el código de salida de error 1 InstallationDate: Installed on 2015-11-01 (12 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805) PackageArchitecture: all RelatedPackageVersions: dpkg 1.17.5ubuntu5.4 apt 1.0.1ubuntu2.10 SourcePackage: apport Title: package apport 2.14.1-0ubuntu3.18 failed to install/upgrade: el subproceso script pre-removal nuevo devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 need-duplicate-check trusty ** Description changed: - I have a lot of problems in my laptop with ubuntu 14.03 LTS and 15.10 too. + I have a lot of problems in my laptop with ubuntu 14.04.3 LTS and 15.10 too. Actually Libre Office Writter doesn't work. Sometimes it depends when i put in on my laptop appairs ACPI PCC Probe failed and sometimes say don't find hard disk - sometimes thunderbird fails + sometimes thunderbird fails and sometimes i can't write any file. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: apport 2.14.1-0ubuntu3.18 ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7 Uname: Linux 3.19.0-33-generic i686 ApportLog: - + ApportVersion: 2.14.1-0ubuntu3.18 Architecture: i386 Date: Fri Nov 13 20:38:45 2015 DuplicateSignature: package:apport:2.14.1-0ubuntu3.18:el subproceso script pre-removal nuevo devolvió el código de salida de error 1 ErrorMessage: el subproceso script pre-removal nuevo devolvió el código de salida de error 1 InstallationDate: Installed on 2015-11-01 (12 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805) PackageArchitecture: all RelatedPackageVersions: - dpkg 1.17.5ubuntu5.4 - apt 1.0.1ubuntu2.10 + dpkg 1.17.5ubuntu5.4 + apt 1.0.1ubuntu2.10 SourcePackage: apport Title: package apport 2.14.1-0ubuntu3.18 failed to install/upgrade: el subproceso script pre-removal nuevo devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1516133 Title: package apport 2.14.1-0ubuntu3.18 failed to install/upgrade: el subproceso script pre-removal nuevo devolvió el código de salida de error 1 Status in apport package in Ubuntu: New Bug description: I have a lot of problems in my laptop with ubuntu 14.04.3 LTS and 15.10 too. Actually Libre Office Writter doesn't work. Sometimes it depends when i put in on my laptop appairs ACPI PCC Probe failed and sometimes say don't find hard disk sometimes thunderbird fails and sometimes i can't write any file. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: apport 2.14.1-0ubuntu3.18 ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7 Uname: Linux 3.19.0-33-generic i686 ApportLog: ApportVersion: 2.14.1-0ubuntu3.18 Architecture: i386 Date: Fri Nov 13 20:38:45 2015 DuplicateSignature: package:apport:2.14.1-0ubuntu3.18:el subproceso script pre-removal nuevo devolvió el código de salida de error 1 ErrorMessage: el subproceso script pre-removal nuevo devolvió el código de salida de error 1 InstallationDate: Installed on 2015-11-01 (12 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805) PackageArchitecture: all RelatedPackageVersions: dpkg 1.17.5ubuntu5.4 apt 1.0.1ubuntu2.10 SourcePackage: apport Title: package apport 2.14.1-0ubuntu3.18 failed to install/upgrade: el subproceso script pre-removal nuevo devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1516133/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchp
[Touch-packages] [Bug 1466458] Please test proposed package
Hello Kevin, or anyone else affected, Accepted lxc into wily-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/lxc/1.1.5-0ubuntu0.15.10.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- 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/1466458 Title: template 'none' doesn't work with lxc-create Status in lxc package in Ubuntu: Fix Released Status in lxc source package in Vivid: Fix Committed Status in lxc source package in Wily: Fix Committed Bug description: Hi, The man page lxc-create(1) says that with the '-t' option to specify a template '"none" can be used to force lxc-create to skip rootfs creation'. This does not appear to work. root@somehost:/var/lib/lxc# lxc-create -n test.lol -t none lxc_container: lxccontainer.c: get_template_path: 867 No such file or directory - bad template: none lxc_container: lxccontainer.c: lxcapi_create: 1264 bad template: none lxc_container: lxc_create.c: main: 271 Error creating container test.lol There is no template in the templates dir corresponding to the 'none' template. I've looked through the upstream tarballs from releases 0.5.0, 0.6.0, ... , 1.0.0, 1.1.0, and there is no 'none' template in any. Might be just a documentation mistake, I guess. Could be a missing template, or maybe 'none' has a special meaning to the lxc- create binary; I haven't looked yet. I'll dig a little further. I'm using lxc 1.0.7-0ubuntu0.1 on Ubuntu 14.04 . thanks, Kevin ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lxc 1.1.2-0ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Jun 18 11:56:34 2015 InstallationDate: Installed on 2012-01-13 (1251 days ago) InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: lxc UpgradeStatus: Upgraded to vivid on 2015-05-14 (34 days ago) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx lxcsyslog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1466458/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1436723] Re: Regression: Nested LXC is broken on Vivid
Hello Chris, or anyone else affected, Accepted lxc into vivid-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/lxc/1.1.5-0ubuntu0.15.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: lxc (Ubuntu Vivid) Status: In Progress => Fix Committed ** Tags added: verification-needed -- 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/1436723 Title: Regression: Nested LXC is broken on Vivid Status in lxc package in Ubuntu: Fix Released Status in lxc source package in Vivid: Fix Committed Bug description: The nested LXC functionality seems to be broken on Vivid, at least with the following setup: Vivid (Host) -> Trusty (Outer LXC) -> Trusty (Inner LXC) What happens: The Inner LXC start command fails when trying to start with: http://pastebin.ubuntu.com/10682639/ ( 631 cgroup error? 100 cgroups with this name already running seems to be the revelant error message). What is expected to happen: The inner LXC start command is expected to succeed and result in a running nested container. Steps to reproduce: - Install vivid server daily, update. - sudo apt-get install lxc - sudo lxc-create -n outer -t ubuntu -- --release trusty --mirror=http://ch.archive.ubuntu.com/ubuntu -b $USER - sudo su - echo 'lxc.aa_profile = lxc-container-default-with-nesting' >> /var/lib/lxc/outer/config - exit - sudo lxc-start -n outer - (SSH to outer) - sudo apt-get update && sudo apt-get dist-upgrade - sudo apt-get install lxc - sudo lxc-create -n inner -t ubuntu -- --release trusty --mirror=http://ch.archive.ubuntu.com/ubuntu -b $USER - sudo lxc-start -n inner Fails with: http://pastebin.ubuntu.com/10682639/ Enabling debug logs for this action yields: http://pastebin.ubuntu.com/10682658/ Control: The exact same scenario works on trusty and utopic. Tested by spinning up server installs (from isos) in KVMs and verifying manually. Any further log or information available on request, including KVM images demonstrating the problem. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lxc 1.1.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 26 08:43:56 2015 InstallationDate: Installed on 2015-03-12 (13 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150306) SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1436723/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1512323] Re: devices on devel-proposed/ubuntu do not boot with systemd 227-2ubuntu1
Oh wow, Launchpad just stopped sending me emails on this issue and I got side tracked on some changes to system-image that I thought might help debug the problem. At least it looks like y'all have some good leads on the root cause though. -- 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/1512323 Title: devices on devel-proposed/ubuntu do not boot with systemd 227-2ubuntu1 Status in Canonical System Image: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: Last known good build: mako devel-proposed/ubuntu r336 Affects builds from devel-proposed/ubuntu starting from first Xenial build. Test Case: Boot in fastboot mode and flash with: $ ubuntu-device-flash -v touch --channel=ubuntu-touch/devel-proposed/ubuntu --bootstrap or upgrade from 336 to latest devel-proposed image Actual Result During a successful flashing operation of a device from fastboot, it boots once into recovery, then reboots and a rotating Ubuntu logo is displayed while the devices is being flashed. With this issue, on the second stage of the flash the phone is stuck on the vendor's logo (google or bq) and the rotating ubuntu logo is never displayed. Same problem on krillin devel-proposed/krillin.en 235 Workaround: Boot into recovery, mount the system partition and downgrade systemd to 225-1ubuntu9 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1512323/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1497420] Please test proposed package
Hello Chris, or anyone else affected, Accepted lxc into wily-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/lxc/1.1.5-0ubuntu0.15.10.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- 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/1497420 Title: systemd 226 (moving pid 1 into /init.scope cgroup) breaks lxc-attach Status in cgmanager package in Ubuntu: Fix Released Status in lxc package in Ubuntu: Fix Released Status in lxcfs package in Ubuntu: Fix Released Status in cgmanager source package in Vivid: New Status in lxc source package in Vivid: Fix Committed Status in lxcfs source package in Vivid: New Status in cgmanager source package in Wily: New Status in lxc source package in Wily: Fix Committed Status in lxcfs source package in Wily: New Status in docker package in Debian: Fix Released Bug description: Once systemd 226 is installed in an unprivileged Debian Sid container, lxc-attach no-longer functions: % lxc-attach -n siddy lxc-attach: cgmanager.c: lxc_cgmanager_enter: 698 call to cgmanager_move_pid_abs_sync failed: invalid request lxc-attach: cgmanager.c: cgm_attach: 1460 Failed to enter group /user.slice/user-1000.slice/session-1.scope/lxc/siddy/init.scope lxc-attach: attach.c: lxc_attach: 909 error communicating with child process % journalctl -u cgmanager | tail -n 1 Sep 18 20:20:44 astoria cgmanager[1169]: cgmanager:per_ctrl_move_pid_main: pid 21918 (uid 1000 gid 1000) may not write to /run/cgmanager/fs/none,name=systemd//user.slice/user-1000.slice/session-1.scope/lxc/siddy/init.scope/tasks Full walkthrough: % lxc-create -n siddy -t download -- -d debian -r sid -a amd64 Using image from local cache Unpacking the rootfs ... % lxc-start -n siddy % lxc-attach -n siddy root@siddy:/# apt-get update Get:1 http://http.debian.net sid InRelease [253 kB] ... Get:7 http://http.debian.net sid/non-free amd64 Packages [91.3 kB] Fetched 13.2 MB in 3s (3789 kB/s) Reading package lists... Done root@siddy:/# apt-get install systemd Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: libsystemd0 Suggested packages: systemd-ui systemd-container Recommended packages: libpam-systemd dbus The following packages will be upgraded: libsystemd0 systemd 2 upgraded, 0 newly installed, 0 to remove and 47 not upgraded. Need to get 3668 kB of archives. After this operation, 1100 kB disk space will be freed. Do you want to continue? [Y/n] Get:1 http://http.debian.net/debian/ sid/main libsystemd0 amd64 226-2 [242 kB] Get:2 http://http.debian.net/debian/ sid/main systemd amd64 226-2 [3426 kB] ... Setting up systemd (226-2) ... Installing new version of config file /etc/X11/xinit/xinitrc.d/50-systemd-user.sh ... Installing new version of config file /etc/dbus-1/system.d/org.freedesktop.login1.conf ... addgroup: The group `systemd-journal' already exists as a system group. Exiting. Failed to set capabilities on file `/usr/bin/systemd-detect-virt' (Invalid argument) The value of the capability argument is not permitted for a file. Or the file is not a regular (non-symlink) file Failed to execute operation: File exists Removing obsolete conffile /etc/dbus-1/system.d/org.freedesktop.machine1.conf ... root@siddy:/# exit % lxc-attach -n siddy lxc-attach: cgmanager.c: lxc_cgmanager_enter: 698 call to cgmanager_move_pid_abs_sync failed: invalid request lxc-attach: cgmanager.c: cgm_attach: 1460 Failed to enter group /user.slice/user-1000.slice/session-1.scope/lxc/siddy/init.scope lxc-attach: attach.c: lxc_attach: 909 error communicating with child process ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: lxc 1.1.3-0ubuntu1 [modified: usr/lib/x86_64-linux-gnu/lxc/lxc-net] ProcVersionSignature: Ubuntu 4.2.0-10.11-generic 4.2.0 Uname: Linux 4.2.0-10-g
[Touch-packages] [Bug 1515463] Re: Broken juju LXC deployments
Hello Brad, or anyone else affected,
Accepted lxc into vivid-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lxc/1.1.5-0ubuntu0.15.04.2 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Your feedback will aid us getting this update
out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed. In either case, details of your testing will help
us make a better decision.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance!
** Changed in: lxc (Ubuntu Vivid)
Status: In Progress => Fix Committed
** Tags added: verification-needed
** Changed in: lxc (Ubuntu Wily)
Status: In Progress => Fix Committed
--
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/1515463
Title:
Broken juju LXC deployments
Status in lxc package in Ubuntu:
Fix Committed
Status in lxc source package in Trusty:
In Progress
Status in lxc source package in Vivid:
Fix Committed
Status in lxc source package in Wily:
Fix Committed
Status in lxc source package in Xenial:
Fix Committed
Bug description:
I've just tried using juju to deploy to a container with trusty-
proposed repo enabled, and I get an error message about 'failed to
retrieve the template to clone'. The underlying error appears to be:
tar --numeric-owner -xpJf
/var/cache/lxc/cloud-trusty/ubuntu-14.04-server-cloudimg-amd64-root.tar.gz;
xz: (stdin): File format not recognized; tar: Child returned status 1; tar:
Error is not recoverable: exiting now;
This seems to be fairly obvious, trying to use xz on a tar.gz file is
never going to work.
The change appears to be from
https://github.com/lxc/lxc/commit/27c278a76931bfc4660caa85d1942ca91c86e0bf,
it assumes everything passed into it will be a .tar.xz file.
This appears to be a conflict between the template expecting a .tar.xz
file, and juju providing it a .tar.gz file. You can see what juju is
providing from:
$ ubuntu-cloudimg-query trusty released amd64 --format %{url}
https://cloud-images.ubuntu.com/server/releases/trusty/release-20151105/ubuntu-14.04-server-cloudimg-amd64.tar.gz
From the juju deployed host:
$ apt-cache policy lxc-templates
lxc-templates:
Installed: 1.0.8-0ubuntu0.1
Candidate: 1.0.8-0ubuntu0.1
Version table:
*** 1.0.8-0ubuntu0.1 0
500 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64
Packages
100 /var/lib/dpkg/status
From the host running juju:
$ apt-cache policy juju-core
juju-core:
Installed: 1.22.8-0ubuntu1~14.04.1
Candidate: 1.25.0-0ubuntu1~14.04.1~juju1
Version table:
1.25.0-0ubuntu1~14.04.1~juju1 0
500 http://ppa.launchpad.net/juju/proposed/ubuntu/ trusty/main amd64
Packages
*** 1.22.8-0ubuntu1~14.04.1 0
400 http://archive.ubuntu.com/ubuntu/ trusty-proposed/universe amd64
Packages
100 /var/lib/dpkg/status
All machine involved are running trusty:
$ lsb_release -rd
Description:Ubuntu 14.04.3 LTS
Release:14.04
Please let me know if you need any more information.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1515463/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1497420] Re: systemd 226 (moving pid 1 into /init.scope cgroup) breaks lxc-attach
Hello Chris, or anyone else affected, Accepted lxc into vivid-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/lxc/1.1.5-0ubuntu0.15.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Also affects: lxc (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: cgmanager (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: lxcfs (Ubuntu Vivid) Importance: Undecided Status: New ** Changed in: lxc (Ubuntu Vivid) Status: New => Fix Committed ** Tags added: verification-needed ** Also affects: lxc (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: cgmanager (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: lxcfs (Ubuntu Wily) Importance: Undecided Status: New ** Changed in: lxc (Ubuntu Wily) Status: New => Fix Committed -- 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/1497420 Title: systemd 226 (moving pid 1 into /init.scope cgroup) breaks lxc-attach Status in cgmanager package in Ubuntu: Fix Released Status in lxc package in Ubuntu: Fix Released Status in lxcfs package in Ubuntu: Fix Released Status in cgmanager source package in Vivid: New Status in lxc source package in Vivid: Fix Committed Status in lxcfs source package in Vivid: New Status in cgmanager source package in Wily: New Status in lxc source package in Wily: Fix Committed Status in lxcfs source package in Wily: New Status in docker package in Debian: Fix Released Bug description: Once systemd 226 is installed in an unprivileged Debian Sid container, lxc-attach no-longer functions: % lxc-attach -n siddy lxc-attach: cgmanager.c: lxc_cgmanager_enter: 698 call to cgmanager_move_pid_abs_sync failed: invalid request lxc-attach: cgmanager.c: cgm_attach: 1460 Failed to enter group /user.slice/user-1000.slice/session-1.scope/lxc/siddy/init.scope lxc-attach: attach.c: lxc_attach: 909 error communicating with child process % journalctl -u cgmanager | tail -n 1 Sep 18 20:20:44 astoria cgmanager[1169]: cgmanager:per_ctrl_move_pid_main: pid 21918 (uid 1000 gid 1000) may not write to /run/cgmanager/fs/none,name=systemd//user.slice/user-1000.slice/session-1.scope/lxc/siddy/init.scope/tasks Full walkthrough: % lxc-create -n siddy -t download -- -d debian -r sid -a amd64 Using image from local cache Unpacking the rootfs ... % lxc-start -n siddy % lxc-attach -n siddy root@siddy:/# apt-get update Get:1 http://http.debian.net sid InRelease [253 kB] ... Get:7 http://http.debian.net sid/non-free amd64 Packages [91.3 kB] Fetched 13.2 MB in 3s (3789 kB/s) Reading package lists... Done root@siddy:/# apt-get install systemd Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: libsystemd0 Suggested packages: systemd-ui systemd-container Recommended packages: libpam-systemd dbus The following packages will be upgraded: libsystemd0 systemd 2 upgraded, 0 newly installed, 0 to remove and 47 not upgraded. Need to get 3668 kB of archives. After this operation, 1100 kB disk space will be freed. Do you want to continue? [Y/n] Get:1 http://http.debian.net/debian/ sid/main libsystemd0 amd64 226-2 [242 kB] Get:2 http://http.debian.net/debian/ sid/main systemd amd64 226-2 [3426 kB] ... Setting up systemd (226-2) ... Installing new version of config file /etc/X11/xinit/xinitrc.d/50-systemd-user.sh ... Installing new version of config file /etc/dbus-1/system.d/org.freedesktop.login1.conf ... addgroup: The group `systemd-journal' already exists as a system group. Exiting. Failed to set capabilities on file `/usr/bin/systemd-detect-virt' (Invalid argument) The value of the capability argument is not permitted for a file. Or the file is not a regular (non-symlink) file Failed to execute operation: Fi
[Touch-packages] [Bug 1510619] Re: Wily: add machine fails using kvm and lxcbr0
Hello Adam, or anyone else affected, Accepted lxc into vivid-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/lxc/1.1.5-0ubuntu0.15.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Also affects: lxc (Ubuntu Vivid) Importance: Undecided Status: New ** Changed in: lxc (Ubuntu Vivid) Status: New => Fix Committed ** Tags added: verification-needed ** Also affects: lxc (Ubuntu Wily) Importance: Undecided Status: New ** Changed in: lxc (Ubuntu Wily) Status: New => Fix Committed -- 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/1510619 Title: Wily: add machine fails using kvm and lxcbr0 Status in juju-core: Invalid Status in lxc package in Ubuntu: Fix Released Status in lxc source package in Vivid: Fix Committed Status in lxc source package in Wily: Fix Committed Bug description: Juju fails to start a machine after add-machine takes place. My environments.yaml: local: type: local container: kvm network-bridge: lxcbr0 Status output: ubuntu@ancient-spot:~$ juju status environment: local machines: "0": agent-state: started agent-version: 1.24.7.1 dns-name: localhost instance-id: localhost series: wily state-server-member-status: has-vote "1": agent-state: pending instance-id: ubuntu-local-machine-1 series: wily hardware: arch=amd64 cpu-cores=1 mem=512M root-disk=8192M debug log: http://paste.ubuntu.com/12980615/ I never see anything in the logs which indicate machine-1 is being deployed or what else could be going on with it. To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1510619/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1515463] Please test proposed package
Hello Brad, or anyone else affected,
Accepted lxc into wily-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lxc/1.1.5-0ubuntu0.15.10.2 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Your feedback will aid us getting this update
out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed. In either case, details of your testing will help
us make a better decision.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance!
--
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/1515463
Title:
Broken juju LXC deployments
Status in lxc package in Ubuntu:
Fix Committed
Status in lxc source package in Trusty:
In Progress
Status in lxc source package in Vivid:
Fix Committed
Status in lxc source package in Wily:
Fix Committed
Status in lxc source package in Xenial:
Fix Committed
Bug description:
I've just tried using juju to deploy to a container with trusty-
proposed repo enabled, and I get an error message about 'failed to
retrieve the template to clone'. The underlying error appears to be:
tar --numeric-owner -xpJf
/var/cache/lxc/cloud-trusty/ubuntu-14.04-server-cloudimg-amd64-root.tar.gz;
xz: (stdin): File format not recognized; tar: Child returned status 1; tar:
Error is not recoverable: exiting now;
This seems to be fairly obvious, trying to use xz on a tar.gz file is
never going to work.
The change appears to be from
https://github.com/lxc/lxc/commit/27c278a76931bfc4660caa85d1942ca91c86e0bf,
it assumes everything passed into it will be a .tar.xz file.
This appears to be a conflict between the template expecting a .tar.xz
file, and juju providing it a .tar.gz file. You can see what juju is
providing from:
$ ubuntu-cloudimg-query trusty released amd64 --format %{url}
https://cloud-images.ubuntu.com/server/releases/trusty/release-20151105/ubuntu-14.04-server-cloudimg-amd64.tar.gz
From the juju deployed host:
$ apt-cache policy lxc-templates
lxc-templates:
Installed: 1.0.8-0ubuntu0.1
Candidate: 1.0.8-0ubuntu0.1
Version table:
*** 1.0.8-0ubuntu0.1 0
500 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64
Packages
100 /var/lib/dpkg/status
From the host running juju:
$ apt-cache policy juju-core
juju-core:
Installed: 1.22.8-0ubuntu1~14.04.1
Candidate: 1.25.0-0ubuntu1~14.04.1~juju1
Version table:
1.25.0-0ubuntu1~14.04.1~juju1 0
500 http://ppa.launchpad.net/juju/proposed/ubuntu/ trusty/main amd64
Packages
*** 1.22.8-0ubuntu1~14.04.1 0
400 http://archive.ubuntu.com/ubuntu/ trusty-proposed/universe amd64
Packages
100 /var/lib/dpkg/status
All machine involved are running trusty:
$ lsb_release -rd
Description:Ubuntu 14.04.3 LTS
Release:14.04
Please let me know if you need any more information.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1515463/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1510619] Please test proposed package
Hello Adam, or anyone else affected, Accepted lxc into wily-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/lxc/1.1.5-0ubuntu0.15.10.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- 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/1510619 Title: Wily: add machine fails using kvm and lxcbr0 Status in juju-core: Invalid Status in lxc package in Ubuntu: Fix Released Status in lxc source package in Vivid: Fix Committed Status in lxc source package in Wily: Fix Committed Bug description: Juju fails to start a machine after add-machine takes place. My environments.yaml: local: type: local container: kvm network-bridge: lxcbr0 Status output: ubuntu@ancient-spot:~$ juju status environment: local machines: "0": agent-state: started agent-version: 1.24.7.1 dns-name: localhost instance-id: localhost series: wily state-server-member-status: has-vote "1": agent-state: pending instance-id: ubuntu-local-machine-1 series: wily hardware: arch=amd64 cpu-cores=1 mem=512M root-disk=8192M debug log: http://paste.ubuntu.com/12980615/ I never see anything in the logs which indicate machine-1 is being deployed or what else could be going on with it. To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1510619/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1466458] Re: template 'none' doesn't work with lxc-create
Hello Kevin, or anyone else affected, Accepted lxc into vivid-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/lxc/1.1.5-0ubuntu0.15.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Also affects: lxc (Ubuntu Vivid) Importance: Undecided Status: New ** Changed in: lxc (Ubuntu Vivid) Status: New => Fix Committed ** Tags added: verification-needed ** Also affects: lxc (Ubuntu Wily) Importance: Undecided Status: New ** Changed in: lxc (Ubuntu Wily) Status: New => Fix Committed -- 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/1466458 Title: template 'none' doesn't work with lxc-create Status in lxc package in Ubuntu: Fix Released Status in lxc source package in Vivid: Fix Committed Status in lxc source package in Wily: Fix Committed Bug description: Hi, The man page lxc-create(1) says that with the '-t' option to specify a template '"none" can be used to force lxc-create to skip rootfs creation'. This does not appear to work. root@somehost:/var/lib/lxc# lxc-create -n test.lol -t none lxc_container: lxccontainer.c: get_template_path: 867 No such file or directory - bad template: none lxc_container: lxccontainer.c: lxcapi_create: 1264 bad template: none lxc_container: lxc_create.c: main: 271 Error creating container test.lol There is no template in the templates dir corresponding to the 'none' template. I've looked through the upstream tarballs from releases 0.5.0, 0.6.0, ... , 1.0.0, 1.1.0, and there is no 'none' template in any. Might be just a documentation mistake, I guess. Could be a missing template, or maybe 'none' has a special meaning to the lxc- create binary; I haven't looked yet. I'll dig a little further. I'm using lxc 1.0.7-0ubuntu0.1 on Ubuntu 14.04 . thanks, Kevin ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lxc 1.1.2-0ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Jun 18 11:56:34 2015 InstallationDate: Installed on 2012-01-13 (1251 days ago) InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: lxc UpgradeStatus: Upgraded to vivid on 2015-05-14 (34 days ago) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx lxcsyslog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1466458/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1441068] Please test proposed package
Hello Martin, or anyone else affected, Accepted lxc into wily-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/lxc/1.1.5-0ubuntu0.15.10.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- 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/1441068 Title: lxc-destroy fails on btrfs subvolumes Status in lxc package in Ubuntu: Fix Released Status in lxc source package in Vivid: Fix Committed Status in lxc source package in Wily: Fix Committed Bug description: $ sudo lxc-destroy -n adt-vivid [sudo] password for martin: lxc_container: utils.c: _recursive_rmdir_onedev: 147 _recursive_rmdir_onedev: failed to delete /srv/lxc/adt-vivid/rootfs/var/lib lxc_container: utils.c: _recursive_rmdir_onedev: 147 _recursive_rmdir_onedev: failed to delete /srv/lxc/adt-vivid/rootfs/var lxc_container: utils.c: _recursive_rmdir_onedev: 147 _recursive_rmdir_onedev: failed to delete /srv/lxc/adt-vivid/rootfs lxc_container: lxccontainer.c: container_destroy: 2050 Error destroying rootfs for adt-vivid Destroying adt-vivid failed This is because the container rootfs has a btrfs subvolume: ID 557 gen 97073 top level 266 path @srv/lxc/adt- vivid/rootfs/var/lib/machines After "sudo btrfs subvolume delete /srv/lxc/adt- vivid/rootfs/var/lib/machines" I can remove the container. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lxc 1.1.1-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3 Uname: Linux 3.19.0-12-generic x86_64 ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Apr 7 11:51:51 2015 EcryptfsInUse: Yes SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx lxc.conf: lxc.lxcpath = /srv/lxc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1441068/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1441068] Re: lxc-destroy fails on btrfs subvolumes
Hello Martin, or anyone else affected, Accepted lxc into vivid-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/lxc/1.1.5-0ubuntu0.15.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: lxc (Ubuntu Vivid) Status: In Progress => Fix Committed ** Tags added: verification-needed ** Changed in: lxc (Ubuntu Wily) Status: In Progress => Fix Committed -- 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/1441068 Title: lxc-destroy fails on btrfs subvolumes Status in lxc package in Ubuntu: Fix Released Status in lxc source package in Vivid: Fix Committed Status in lxc source package in Wily: Fix Committed Bug description: $ sudo lxc-destroy -n adt-vivid [sudo] password for martin: lxc_container: utils.c: _recursive_rmdir_onedev: 147 _recursive_rmdir_onedev: failed to delete /srv/lxc/adt-vivid/rootfs/var/lib lxc_container: utils.c: _recursive_rmdir_onedev: 147 _recursive_rmdir_onedev: failed to delete /srv/lxc/adt-vivid/rootfs/var lxc_container: utils.c: _recursive_rmdir_onedev: 147 _recursive_rmdir_onedev: failed to delete /srv/lxc/adt-vivid/rootfs lxc_container: lxccontainer.c: container_destroy: 2050 Error destroying rootfs for adt-vivid Destroying adt-vivid failed This is because the container rootfs has a btrfs subvolume: ID 557 gen 97073 top level 266 path @srv/lxc/adt- vivid/rootfs/var/lib/machines After "sudo btrfs subvolume delete /srv/lxc/adt- vivid/rootfs/var/lib/machines" I can remove the container. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lxc 1.1.1-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3 Uname: Linux 3.19.0-12-generic x86_64 ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Apr 7 11:51:51 2015 EcryptfsInUse: Yes SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx lxc.conf: lxc.lxcpath = /srv/lxc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1441068/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1504496] Re: package lxc 1.1.4-0ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Hello Nick, or anyone else affected,
Accepted lxc into vivid-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lxc/1.1.5-0ubuntu0.15.04.2 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Your feedback will aid us getting this update
out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed. In either case, details of your testing will help
us make a better decision.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance!
** Tags added: verification-needed
** Also affects: lxc (Ubuntu Wily)
Importance: Undecided
Status: New
** Also affects: lxc (Ubuntu Vivid)
Importance: Undecided
Status: New
--
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/1504496
Title:
package lxc 1.1.4-0ubuntu0.1 failed to install/upgrade: subprocess
installed post-installation script returned error exit status 1
Status in lxc package in Ubuntu:
In Progress
Status in lxc source package in Vivid:
New
Status in lxc source package in Wily:
New
Bug description:
A dist-upgrade failed in the maintainer scripts while trying to
restart the lxc networking, I think:
Reading package lists... Done
The following NEW packages will be installed:
linux-image-3.19.0-31-generic{a} linux-image-extra-3.19.0-31-generic{a}
linux-signed-image-3.19.0-31-generic{a}
The following packages will be upgraded:
juju juju-core juju-local liblxc1 linux-image-generic linux-libc-dev
linux-signed-image-generic
lxc lxc-templates mutt python3-lxc
The following packages are RECOMMENDED but will NOT be installed:
citadel-mta courier-mta dma dma:i386 esmtp-run exim4-daemon-heavy
exim4-daemon-light
lsb-invalid-mta masqmail msmtp-mta nullmailer opensmtpd postfix qmail-run
sendmail-bin ssmtp
xmail
11 packages upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/90.5 MB of archives. After unpacking 259 MB will be used.
Do you want to continue? [Y/n/?]
(Reading database ... 357199 files and directories currently installed.)
Preparing to unpack .../python3-lxc_1.1.4-0ubuntu0.1_amd64.deb ...
Unpacking python3-lxc (1.1.4-0ubuntu0.1) over (1.1.2-0ubuntu3.2) ...
Preparing to unpack .../lxc-templates_1.1.4-0ubuntu0.1_amd64.deb ...
Unpacking lxc-templates (1.1.4-0ubuntu0.1) over (1.1.2-0ubuntu3.2) ...
Preparing to unpack .../liblxc1_1.1.4-0ubuntu0.1_amd64.deb ...
Unpacking liblxc1 (1.1.4-0ubuntu0.1) over (1.1.2-0ubuntu3.2) ...
Preparing to unpack .../lxc_1.1.4-0ubuntu0.1_amd64.deb ...
Unpacking lxc (1.1.4-0ubuntu0.1) over (1.1.2-0ubuntu3.2) ...
Selecting previously unselected package linux-image-3.19.0-31-generic.
Preparing to unpack .../linux-image-3.19.0-31-generic_3.19.0-31.36_amd64.deb
...
Done.
Unpacking linux-image-3.19.0-31-generic (3.19.0-31.36) ...
Selecting previously unselected package linux-image-extra-3.19.0-31-generic.
Preparing to unpack
.../linux-image-extra-3.19.0-31-generic_3.19.0-31.36_amd64.deb ...
Unpacking linux-image-extra-3.19.0-31-generic (3.19.0-31.36) ...
Preparing to unpack .../linux-image-generic_3.19.0.31.30_amd64.deb ...
Unpacking linux-image-generic (3.19.0.31.30) over (3.19.0.30.29) ...
Preparing to unpack .../linux-libc-dev_3.19.0-31.36_amd64.deb ...
Unpacking linux-libc-dev:amd64 (3.19.0-31.36) over (3.19.0-30.34) ...
Selecting previously unselected package linux-signed-image-3.19.0-31-generic.
Preparing to unpack
.../linux-signed-image-3.19.0-31-generic_3.19.0-31.36_amd64.deb ...
Unpacking linux-signed-image-3.19.0-31-generic (3.19.0-31.36) ...
Preparing to unpack .../linux-signed-image-generic_3.19.0.31.30_amd64.deb ...
Unpacking linux-signed-image-generic (3.19.0.31.30) over (3.19.0.30.29) ...
Preparing to unpack .../mutt_1.5.23-3ubuntu1_amd64.deb ...
Unpacking mutt (1.5.23-3ubuntu1) over (1.5.23-3) ...
Preparing to unpack .../juju-core_1.24.6-0ubuntu1~15.04.1_amd64.deb ...
Unpacking juju-core (1.24.6-0ubuntu1~15.04.1) over
(1.23.2-0ubuntu1~14.10.1~juju1) ...
Preparing to unpack .../juju_1.24.6-0ubuntu1~15.04.1_all.deb ...
Unpacking juju (1.24.6-0ubuntu1~15.04.1) over (1.23.2-0ubuntu1~14.10.1~juju1)
...
Preparing to unpack .../juju-local_1.24.6-0ubuntu1~15.04.1_all.deb ...
Unpacking juju-local (1.24.6-0ubuntu1~15.04.1) over
(1.23.2-0ubuntu1~14.10.1~juju1) ...
Processing triggers for man-
[Touch-packages] [Bug 1512323] Re: devices on devel-proposed/ubuntu do not boot with systemd 227-2ubuntu1
stack trace points at new hashtable functionality within systemd.
The crash shows udevd is crashing with SIGBUS.
The new siphash24.c code is full of dereferences of uint8_t types that
are then being handled as uint64_t values, as in le64toh() which is
defined as:
static inline uint64_t le64toh(le64_t value) { return
bswap_64_on_be((uint64_t __force)value); }
There is nothing in this code that guarantees 64-bit alignment of the
source pointer. Dereferencing an unaligned pointer as a 64-bit int is
non-portable, and it's precisely a SIGBUS that is raised in the case of
unaligned access.
--
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/1512323
Title:
devices on devel-proposed/ubuntu do not boot with systemd 227-2ubuntu1
Status in Canonical System Image:
Confirmed
Status in systemd package in Ubuntu:
Confirmed
Bug description:
Last known good build: mako devel-proposed/ubuntu r336
Affects builds from devel-proposed/ubuntu starting from first Xenial
build.
Test Case:
Boot in fastboot mode and flash with:
$ ubuntu-device-flash -v touch --channel=ubuntu-touch/devel-proposed/ubuntu
--bootstrap
or
upgrade from 336 to latest devel-proposed image
Actual Result
During a successful flashing operation of a device from fastboot, it boots
once into recovery, then reboots and a rotating Ubuntu logo is displayed while
the devices is being flashed.
With this issue, on the second stage of the flash the phone is stuck on the
vendor's logo (google or bq) and the rotating ubuntu logo is never displayed.
Same problem on krillin devel-proposed/krillin.en 235
Workaround:
Boot into recovery, mount the system partition and downgrade systemd to
225-1ubuntu9
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1512323/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1458704] Re: Cannot use online banking with Bank of Ireland
Sorry Tuomas, I didnt see your message. I just got the error in the attachment. I don't know what the cause is. -- 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/1458704 Title: Cannot use online banking with Bank of Ireland Status in webbrowser-app package in Ubuntu: New Bug description: visiting the below URL gives a compatibility error : I cannot paste URL with BQ device so adding as attachment from terminal instead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1458704/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1512323] Re: devices on devel-proposed/ubuntu do not boot with systemd 227-2ubuntu1
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 systemd in Ubuntu. https://bugs.launchpad.net/bugs/1512323 Title: devices on devel-proposed/ubuntu do not boot with systemd 227-2ubuntu1 Status in Canonical System Image: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: Last known good build: mako devel-proposed/ubuntu r336 Affects builds from devel-proposed/ubuntu starting from first Xenial build. Test Case: Boot in fastboot mode and flash with: $ ubuntu-device-flash -v touch --channel=ubuntu-touch/devel-proposed/ubuntu --bootstrap or upgrade from 336 to latest devel-proposed image Actual Result During a successful flashing operation of a device from fastboot, it boots once into recovery, then reboots and a rotating Ubuntu logo is displayed while the devices is being flashed. With this issue, on the second stage of the flash the phone is stuck on the vendor's logo (google or bq) and the rotating ubuntu logo is never displayed. Same problem on krillin devel-proposed/krillin.en 235 Workaround: Boot into recovery, mount the system partition and downgrade systemd to 225-1ubuntu9 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1512323/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1515569] Re: /lib/systemd/systemd-logind:7:siphash24_compress:base_bucket_hash:hashmap_put:add_object_vtable_internal:manager_startup
*** This bug is a duplicate of bug 1512323 *** https://bugs.launchpad.net/bugs/1512323 ** This bug has been marked a duplicate of bug 1512323 devices on devel-proposed/ubuntu do not boot with systemd 227-2ubuntu1 -- 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/1515569 Title: /lib/systemd/systemd- logind:7:siphash24_compress:base_bucket_hash:hashmap_put:add_object_vtable_internal:manager_startup Status in systemd package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding systemd. This problem was most recently seen with version 227-2ubuntu1, the problem page at https://errors.ubuntu.com/problem/40601234918498089c81001cd7b6a7f06bf12fe7 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1515569/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1516126] [NEW] apport-retrace fails unless apport is also installed (/etc/apport/crashdb.conf)
Public bug reported: Attempting to run apport-retrace in a chroot, it fails with the following traceback: Traceback (most recent call last): File "/usr/bin/apport-retrace", line 217, in crashdb = get_crashdb(options.auth) File "/usr/lib/python2.7/dist-packages/apport/crashdb.py", line 822, in get_crashdb with open(conf) as f: IOError: [Errno 2] No such file or directory: '/etc/apport/crashdb.conf' /etc/apport/crashdb.conf is part of the apport package; and apport- retrace does not depend on apport. ** Affects: apport (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1516126 Title: apport-retrace fails unless apport is also installed (/etc/apport/crashdb.conf) Status in apport package in Ubuntu: New Bug description: Attempting to run apport-retrace in a chroot, it fails with the following traceback: Traceback (most recent call last): File "/usr/bin/apport-retrace", line 217, in crashdb = get_crashdb(options.auth) File "/usr/lib/python2.7/dist-packages/apport/crashdb.py", line 822, in get_crashdb with open(conf) as f: IOError: [Errno 2] No such file or directory: '/etc/apport/crashdb.conf' /etc/apport/crashdb.conf is part of the apport package; and apport- retrace does not depend on apport. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1516126/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1508945] Re: "Couldn't load weather data, please try later again!" with Qt 5.5.1
Might try using bearer plugin based on connectivity-api https://codereview.qt-project.org/#/c/140752/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor-easyprof-ubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1508945 Title: "Couldn't load weather data, please try later again!" with Qt 5.5.1 Status in Ubuntu Weather App: New Status in apparmor-easyprof-ubuntu package in Ubuntu: New Status in qtbase-opensource-src package in Ubuntu: New Bug description: The weather data cannot be seemingly loaded with Qt 5.5.1. More information about Qt 5.5 at https://wiki.ubuntu.com/Touch/QtTesting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-weather-app/+bug/1508945/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1404188] Re: QNetworkSession::isOpen() always returns false
Might try using bearer plugin based on connectivity-api https://codereview.qt-project.org/#/c/140752/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor-easyprof-ubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1404188 Title: QNetworkSession::isOpen() always returns false Status in Canonical System Image: Confirmed Status in apparmor-easyprof-ubuntu package in Ubuntu: Confirmed Status in qtbase-opensource-src package in Ubuntu: Confirmed Bug description: Using QNetworkSession::isOpen() in confined apps on a phone running vivid always returns false. This might be an apparmor thing, however, I couldn't find any REJECTED entries in log files. The test app in lp:~mzanetti/+junk/nmsessiontest can reproduce the issue. Open this project in ubuntu-sdk's qtcreator and run it on a vivid device. Press the button and watch the debug prints. On a vivid-desktop or a RTM based phone it will print "all is well". On a vivid phone however, it'll print "network session not open..." This used to work fine at least back in utopic images. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1404188/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1325940] xserver.outputs.txt
apport information ** Attachment added: "xserver.outputs.txt" https://bugs.launchpad.net/bugs/1325940/+attachment/4518431/+files/xserver.outputs.txt -- 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/1325940 Title: Desktop sometimes comes up with undisplayable screen resolution Status in xorg package in Ubuntu: Incomplete Bug description: Hello, the PC from which I'm sending this report sometimes fails to boot into the desktop properly (which desktop environment doesn't seem to matter). In the failure case the following happens: - The Plymouth Ubuntu splash gets displayed, but it looks distorted. Flickering horizontal artifacts are shown all over the screen, it looks a bit like a CRT Television with low signal. - When the desktop is loaded (via autologin), one can see short glimpses of its wallpaper, but after a few second the screen becomes black and remains that way. The monitor _does_ seem to receive a signal though. - It is possible to switch to TTYs and to use them, but they show similar artifacts like the Plymouth logo. - If I query the display information on the monitor's OSD when the screen is distorted, it reports a resolution of 1681x1050 or 1683x1050, which is 1-3 pixel bigger than the native horizontal resolution of the 22" LCD screen. Switching between different resolutions via entering 'xrandr --size 1024x768' blindly, followed by 'xrandr --size 1680x1050' brings up the native resolution properly. This does not happen on every boot, only in ~10-15% of the cases. I was not able to find any pattern so far in the occurence of this bug. The only thing I observed is that it _never_ happens when Windows XP is started, thus my assumption is that the bug is related to the xserver-xorg-video-radeon driver. I tried to specify the correct resolution explicitly on the kernel command line(adding video=DVI-I-1:1680x1050 ) but this has no positive effect. The monitor is connected via DVI. Below is a video attached that tries to show how the TTYs look when this bug occurs. Notice the abnormal blue lines, which are constantly flickering. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-radeon 1:7.3.0-1ubuntu3.1 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Jun 3 13:23:38 2014 InstallationDate: Installed on 2014-04-22 (41 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV350 [Radeon 9550] [1002:4153] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932a] Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932b] InstallationDate: Installed on 2014-04-22 (570 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) LightdmGreeterLog: ** (lightdm-gtk-greeter:9382): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden 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:6675): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden 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: MSI MS-6741 Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic root=UUID=b7a652e9-aea3-4c8a-bf11-32ec8d22b3bb ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25 Tags: trusty ubuntu Uname: Linux 3.13.0-63-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare saned scanner sudo _MarkForUpload: True dmi.bios.date: 04/02/01 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Version 07.00T dmi.board.name: MS-6741 dmi.board.vendor: MSI dmi.b
[Touch-packages] [Bug 1325940] xdpyinfo.txt
apport information ** Attachment added: "xdpyinfo.txt" https://bugs.launchpad.net/bugs/1325940/+attachment/4518430/+files/xdpyinfo.txt -- 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/1325940 Title: Desktop sometimes comes up with undisplayable screen resolution Status in xorg package in Ubuntu: Incomplete Bug description: Hello, the PC from which I'm sending this report sometimes fails to boot into the desktop properly (which desktop environment doesn't seem to matter). In the failure case the following happens: - The Plymouth Ubuntu splash gets displayed, but it looks distorted. Flickering horizontal artifacts are shown all over the screen, it looks a bit like a CRT Television with low signal. - When the desktop is loaded (via autologin), one can see short glimpses of its wallpaper, but after a few second the screen becomes black and remains that way. The monitor _does_ seem to receive a signal though. - It is possible to switch to TTYs and to use them, but they show similar artifacts like the Plymouth logo. - If I query the display information on the monitor's OSD when the screen is distorted, it reports a resolution of 1681x1050 or 1683x1050, which is 1-3 pixel bigger than the native horizontal resolution of the 22" LCD screen. Switching between different resolutions via entering 'xrandr --size 1024x768' blindly, followed by 'xrandr --size 1680x1050' brings up the native resolution properly. This does not happen on every boot, only in ~10-15% of the cases. I was not able to find any pattern so far in the occurence of this bug. The only thing I observed is that it _never_ happens when Windows XP is started, thus my assumption is that the bug is related to the xserver-xorg-video-radeon driver. I tried to specify the correct resolution explicitly on the kernel command line(adding video=DVI-I-1:1680x1050 ) but this has no positive effect. The monitor is connected via DVI. Below is a video attached that tries to show how the TTYs look when this bug occurs. Notice the abnormal blue lines, which are constantly flickering. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-radeon 1:7.3.0-1ubuntu3.1 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Jun 3 13:23:38 2014 InstallationDate: Installed on 2014-04-22 (41 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV350 [Radeon 9550] [1002:4153] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932a] Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932b] InstallationDate: Installed on 2014-04-22 (570 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) LightdmGreeterLog: ** (lightdm-gtk-greeter:9382): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden 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:6675): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden 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: MSI MS-6741 Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic root=UUID=b7a652e9-aea3-4c8a-bf11-32ec8d22b3bb ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25 Tags: trusty ubuntu Uname: Linux 3.13.0-63-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare saned scanner sudo _MarkForUpload: True dmi.bios.date: 04/02/01 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Version 07.00T dmi.board.name: MS-6741 dmi.board.vendor: MSI dmi.board.version:
[Touch-packages] [Bug 1325940] XorgLogOld.txt
apport information ** Attachment added: "XorgLogOld.txt" https://bugs.launchpad.net/bugs/1325940/+attachment/4518428/+files/XorgLogOld.txt -- 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/1325940 Title: Desktop sometimes comes up with undisplayable screen resolution Status in xorg package in Ubuntu: Incomplete Bug description: Hello, the PC from which I'm sending this report sometimes fails to boot into the desktop properly (which desktop environment doesn't seem to matter). In the failure case the following happens: - The Plymouth Ubuntu splash gets displayed, but it looks distorted. Flickering horizontal artifacts are shown all over the screen, it looks a bit like a CRT Television with low signal. - When the desktop is loaded (via autologin), one can see short glimpses of its wallpaper, but after a few second the screen becomes black and remains that way. The monitor _does_ seem to receive a signal though. - It is possible to switch to TTYs and to use them, but they show similar artifacts like the Plymouth logo. - If I query the display information on the monitor's OSD when the screen is distorted, it reports a resolution of 1681x1050 or 1683x1050, which is 1-3 pixel bigger than the native horizontal resolution of the 22" LCD screen. Switching between different resolutions via entering 'xrandr --size 1024x768' blindly, followed by 'xrandr --size 1680x1050' brings up the native resolution properly. This does not happen on every boot, only in ~10-15% of the cases. I was not able to find any pattern so far in the occurence of this bug. The only thing I observed is that it _never_ happens when Windows XP is started, thus my assumption is that the bug is related to the xserver-xorg-video-radeon driver. I tried to specify the correct resolution explicitly on the kernel command line(adding video=DVI-I-1:1680x1050 ) but this has no positive effect. The monitor is connected via DVI. Below is a video attached that tries to show how the TTYs look when this bug occurs. Notice the abnormal blue lines, which are constantly flickering. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-radeon 1:7.3.0-1ubuntu3.1 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Jun 3 13:23:38 2014 InstallationDate: Installed on 2014-04-22 (41 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV350 [Radeon 9550] [1002:4153] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932a] Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932b] InstallationDate: Installed on 2014-04-22 (570 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) LightdmGreeterLog: ** (lightdm-gtk-greeter:9382): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden 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:6675): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden 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: MSI MS-6741 Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic root=UUID=b7a652e9-aea3-4c8a-bf11-32ec8d22b3bb ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25 Tags: trusty ubuntu Uname: Linux 3.13.0-63-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare saned scanner sudo _MarkForUpload: True dmi.bios.date: 04/02/01 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Version 07.00T dmi.board.name: MS-6741 dmi.board.vendor: MSI dmi.board.versi
[Touch-packages] [Bug 1325940] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1325940/+attachment/4518426/+files/UdevLog.txt -- 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/1325940 Title: Desktop sometimes comes up with undisplayable screen resolution Status in xorg package in Ubuntu: Incomplete Bug description: Hello, the PC from which I'm sending this report sometimes fails to boot into the desktop properly (which desktop environment doesn't seem to matter). In the failure case the following happens: - The Plymouth Ubuntu splash gets displayed, but it looks distorted. Flickering horizontal artifacts are shown all over the screen, it looks a bit like a CRT Television with low signal. - When the desktop is loaded (via autologin), one can see short glimpses of its wallpaper, but after a few second the screen becomes black and remains that way. The monitor _does_ seem to receive a signal though. - It is possible to switch to TTYs and to use them, but they show similar artifacts like the Plymouth logo. - If I query the display information on the monitor's OSD when the screen is distorted, it reports a resolution of 1681x1050 or 1683x1050, which is 1-3 pixel bigger than the native horizontal resolution of the 22" LCD screen. Switching between different resolutions via entering 'xrandr --size 1024x768' blindly, followed by 'xrandr --size 1680x1050' brings up the native resolution properly. This does not happen on every boot, only in ~10-15% of the cases. I was not able to find any pattern so far in the occurence of this bug. The only thing I observed is that it _never_ happens when Windows XP is started, thus my assumption is that the bug is related to the xserver-xorg-video-radeon driver. I tried to specify the correct resolution explicitly on the kernel command line(adding video=DVI-I-1:1680x1050 ) but this has no positive effect. The monitor is connected via DVI. Below is a video attached that tries to show how the TTYs look when this bug occurs. Notice the abnormal blue lines, which are constantly flickering. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-radeon 1:7.3.0-1ubuntu3.1 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Jun 3 13:23:38 2014 InstallationDate: Installed on 2014-04-22 (41 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV350 [Radeon 9550] [1002:4153] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932a] Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932b] InstallationDate: Installed on 2014-04-22 (570 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) LightdmGreeterLog: ** (lightdm-gtk-greeter:9382): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden 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:6675): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden 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: MSI MS-6741 Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic root=UUID=b7a652e9-aea3-4c8a-bf11-32ec8d22b3bb ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25 Tags: trusty ubuntu Uname: Linux 3.13.0-63-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare saned scanner sudo _MarkForUpload: True dmi.bios.date: 04/02/01 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Version 07.00T dmi.board.name: MS-6741 dmi.board.vendor: MSI dmi.board.version: 1.
[Touch-packages] [Bug 1325940] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1325940/+attachment/4518425/+files/UdevDb.txt -- 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/1325940 Title: Desktop sometimes comes up with undisplayable screen resolution Status in xorg package in Ubuntu: Incomplete Bug description: Hello, the PC from which I'm sending this report sometimes fails to boot into the desktop properly (which desktop environment doesn't seem to matter). In the failure case the following happens: - The Plymouth Ubuntu splash gets displayed, but it looks distorted. Flickering horizontal artifacts are shown all over the screen, it looks a bit like a CRT Television with low signal. - When the desktop is loaded (via autologin), one can see short glimpses of its wallpaper, but after a few second the screen becomes black and remains that way. The monitor _does_ seem to receive a signal though. - It is possible to switch to TTYs and to use them, but they show similar artifacts like the Plymouth logo. - If I query the display information on the monitor's OSD when the screen is distorted, it reports a resolution of 1681x1050 or 1683x1050, which is 1-3 pixel bigger than the native horizontal resolution of the 22" LCD screen. Switching between different resolutions via entering 'xrandr --size 1024x768' blindly, followed by 'xrandr --size 1680x1050' brings up the native resolution properly. This does not happen on every boot, only in ~10-15% of the cases. I was not able to find any pattern so far in the occurence of this bug. The only thing I observed is that it _never_ happens when Windows XP is started, thus my assumption is that the bug is related to the xserver-xorg-video-radeon driver. I tried to specify the correct resolution explicitly on the kernel command line(adding video=DVI-I-1:1680x1050 ) but this has no positive effect. The monitor is connected via DVI. Below is a video attached that tries to show how the TTYs look when this bug occurs. Notice the abnormal blue lines, which are constantly flickering. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-radeon 1:7.3.0-1ubuntu3.1 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Jun 3 13:23:38 2014 InstallationDate: Installed on 2014-04-22 (41 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV350 [Radeon 9550] [1002:4153] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932a] Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932b] InstallationDate: Installed on 2014-04-22 (570 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) LightdmGreeterLog: ** (lightdm-gtk-greeter:9382): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden 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:6675): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden 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: MSI MS-6741 Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic root=UUID=b7a652e9-aea3-4c8a-bf11-32ec8d22b3bb ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25 Tags: trusty ubuntu Uname: Linux 3.13.0-63-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare saned scanner sudo _MarkForUpload: True dmi.bios.date: 04/02/01 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Version 07.00T dmi.board.name: MS-6741 dmi.board.vendor: MSI dmi.board.version: 1.0
[Touch-packages] [Bug 1325940] Xrandr.txt
apport information ** Attachment added: "Xrandr.txt" https://bugs.launchpad.net/bugs/1325940/+attachment/4518429/+files/Xrandr.txt -- 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/1325940 Title: Desktop sometimes comes up with undisplayable screen resolution Status in xorg package in Ubuntu: Incomplete Bug description: Hello, the PC from which I'm sending this report sometimes fails to boot into the desktop properly (which desktop environment doesn't seem to matter). In the failure case the following happens: - The Plymouth Ubuntu splash gets displayed, but it looks distorted. Flickering horizontal artifacts are shown all over the screen, it looks a bit like a CRT Television with low signal. - When the desktop is loaded (via autologin), one can see short glimpses of its wallpaper, but after a few second the screen becomes black and remains that way. The monitor _does_ seem to receive a signal though. - It is possible to switch to TTYs and to use them, but they show similar artifacts like the Plymouth logo. - If I query the display information on the monitor's OSD when the screen is distorted, it reports a resolution of 1681x1050 or 1683x1050, which is 1-3 pixel bigger than the native horizontal resolution of the 22" LCD screen. Switching between different resolutions via entering 'xrandr --size 1024x768' blindly, followed by 'xrandr --size 1680x1050' brings up the native resolution properly. This does not happen on every boot, only in ~10-15% of the cases. I was not able to find any pattern so far in the occurence of this bug. The only thing I observed is that it _never_ happens when Windows XP is started, thus my assumption is that the bug is related to the xserver-xorg-video-radeon driver. I tried to specify the correct resolution explicitly on the kernel command line(adding video=DVI-I-1:1680x1050 ) but this has no positive effect. The monitor is connected via DVI. Below is a video attached that tries to show how the TTYs look when this bug occurs. Notice the abnormal blue lines, which are constantly flickering. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-radeon 1:7.3.0-1ubuntu3.1 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Jun 3 13:23:38 2014 InstallationDate: Installed on 2014-04-22 (41 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV350 [Radeon 9550] [1002:4153] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932a] Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932b] InstallationDate: Installed on 2014-04-22 (570 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) LightdmGreeterLog: ** (lightdm-gtk-greeter:9382): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden 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:6675): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden 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: MSI MS-6741 Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic root=UUID=b7a652e9-aea3-4c8a-bf11-32ec8d22b3bb ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25 Tags: trusty ubuntu Uname: Linux 3.13.0-63-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare saned scanner sudo _MarkForUpload: True dmi.bios.date: 04/02/01 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Version 07.00T dmi.board.name: MS-6741 dmi.board.vendor: MSI dmi.board.version: 1.0
[Touch-packages] [Bug 1325940] XorgLog.txt
apport information ** Attachment added: "XorgLog.txt" https://bugs.launchpad.net/bugs/1325940/+attachment/4518427/+files/XorgLog.txt -- 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/1325940 Title: Desktop sometimes comes up with undisplayable screen resolution Status in xorg package in Ubuntu: Incomplete Bug description: Hello, the PC from which I'm sending this report sometimes fails to boot into the desktop properly (which desktop environment doesn't seem to matter). In the failure case the following happens: - The Plymouth Ubuntu splash gets displayed, but it looks distorted. Flickering horizontal artifacts are shown all over the screen, it looks a bit like a CRT Television with low signal. - When the desktop is loaded (via autologin), one can see short glimpses of its wallpaper, but after a few second the screen becomes black and remains that way. The monitor _does_ seem to receive a signal though. - It is possible to switch to TTYs and to use them, but they show similar artifacts like the Plymouth logo. - If I query the display information on the monitor's OSD when the screen is distorted, it reports a resolution of 1681x1050 or 1683x1050, which is 1-3 pixel bigger than the native horizontal resolution of the 22" LCD screen. Switching between different resolutions via entering 'xrandr --size 1024x768' blindly, followed by 'xrandr --size 1680x1050' brings up the native resolution properly. This does not happen on every boot, only in ~10-15% of the cases. I was not able to find any pattern so far in the occurence of this bug. The only thing I observed is that it _never_ happens when Windows XP is started, thus my assumption is that the bug is related to the xserver-xorg-video-radeon driver. I tried to specify the correct resolution explicitly on the kernel command line(adding video=DVI-I-1:1680x1050 ) but this has no positive effect. The monitor is connected via DVI. Below is a video attached that tries to show how the TTYs look when this bug occurs. Notice the abnormal blue lines, which are constantly flickering. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-radeon 1:7.3.0-1ubuntu3.1 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Jun 3 13:23:38 2014 InstallationDate: Installed on 2014-04-22 (41 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV350 [Radeon 9550] [1002:4153] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932a] Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932b] InstallationDate: Installed on 2014-04-22 (570 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) LightdmGreeterLog: ** (lightdm-gtk-greeter:9382): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden 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:6675): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden 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: MSI MS-6741 Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic root=UUID=b7a652e9-aea3-4c8a-bf11-32ec8d22b3bb ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25 Tags: trusty ubuntu Uname: Linux 3.13.0-63-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare saned scanner sudo _MarkForUpload: True dmi.bios.date: 04/02/01 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Version 07.00T dmi.board.name: MS-6741 dmi.board.vendor: MSI dmi.board.version: 1.
[Touch-packages] [Bug 1325940] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1325940/+attachment/4518421/+files/ProcCpuinfo.txt -- 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/1325940 Title: Desktop sometimes comes up with undisplayable screen resolution Status in xorg package in Ubuntu: Incomplete Bug description: Hello, the PC from which I'm sending this report sometimes fails to boot into the desktop properly (which desktop environment doesn't seem to matter). In the failure case the following happens: - The Plymouth Ubuntu splash gets displayed, but it looks distorted. Flickering horizontal artifacts are shown all over the screen, it looks a bit like a CRT Television with low signal. - When the desktop is loaded (via autologin), one can see short glimpses of its wallpaper, but after a few second the screen becomes black and remains that way. The monitor _does_ seem to receive a signal though. - It is possible to switch to TTYs and to use them, but they show similar artifacts like the Plymouth logo. - If I query the display information on the monitor's OSD when the screen is distorted, it reports a resolution of 1681x1050 or 1683x1050, which is 1-3 pixel bigger than the native horizontal resolution of the 22" LCD screen. Switching between different resolutions via entering 'xrandr --size 1024x768' blindly, followed by 'xrandr --size 1680x1050' brings up the native resolution properly. This does not happen on every boot, only in ~10-15% of the cases. I was not able to find any pattern so far in the occurence of this bug. The only thing I observed is that it _never_ happens when Windows XP is started, thus my assumption is that the bug is related to the xserver-xorg-video-radeon driver. I tried to specify the correct resolution explicitly on the kernel command line(adding video=DVI-I-1:1680x1050 ) but this has no positive effect. The monitor is connected via DVI. Below is a video attached that tries to show how the TTYs look when this bug occurs. Notice the abnormal blue lines, which are constantly flickering. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-radeon 1:7.3.0-1ubuntu3.1 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Jun 3 13:23:38 2014 InstallationDate: Installed on 2014-04-22 (41 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV350 [Radeon 9550] [1002:4153] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932a] Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932b] InstallationDate: Installed on 2014-04-22 (570 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) LightdmGreeterLog: ** (lightdm-gtk-greeter:9382): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden 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:6675): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden 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: MSI MS-6741 Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic root=UUID=b7a652e9-aea3-4c8a-bf11-32ec8d22b3bb ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25 Tags: trusty ubuntu Uname: Linux 3.13.0-63-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare saned scanner sudo _MarkForUpload: True dmi.bios.date: 04/02/01 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Version 07.00T dmi.board.name: MS-6741 dmi.board.vendor: MSI dmi.board.ver
[Touch-packages] [Bug 1325940] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1325940/+attachment/4518420/+files/Lsusb.txt -- 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/1325940 Title: Desktop sometimes comes up with undisplayable screen resolution Status in xorg package in Ubuntu: Incomplete Bug description: Hello, the PC from which I'm sending this report sometimes fails to boot into the desktop properly (which desktop environment doesn't seem to matter). In the failure case the following happens: - The Plymouth Ubuntu splash gets displayed, but it looks distorted. Flickering horizontal artifacts are shown all over the screen, it looks a bit like a CRT Television with low signal. - When the desktop is loaded (via autologin), one can see short glimpses of its wallpaper, but after a few second the screen becomes black and remains that way. The monitor _does_ seem to receive a signal though. - It is possible to switch to TTYs and to use them, but they show similar artifacts like the Plymouth logo. - If I query the display information on the monitor's OSD when the screen is distorted, it reports a resolution of 1681x1050 or 1683x1050, which is 1-3 pixel bigger than the native horizontal resolution of the 22" LCD screen. Switching between different resolutions via entering 'xrandr --size 1024x768' blindly, followed by 'xrandr --size 1680x1050' brings up the native resolution properly. This does not happen on every boot, only in ~10-15% of the cases. I was not able to find any pattern so far in the occurence of this bug. The only thing I observed is that it _never_ happens when Windows XP is started, thus my assumption is that the bug is related to the xserver-xorg-video-radeon driver. I tried to specify the correct resolution explicitly on the kernel command line(adding video=DVI-I-1:1680x1050 ) but this has no positive effect. The monitor is connected via DVI. Below is a video attached that tries to show how the TTYs look when this bug occurs. Notice the abnormal blue lines, which are constantly flickering. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-radeon 1:7.3.0-1ubuntu3.1 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Jun 3 13:23:38 2014 InstallationDate: Installed on 2014-04-22 (41 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV350 [Radeon 9550] [1002:4153] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932a] Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932b] InstallationDate: Installed on 2014-04-22 (570 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) LightdmGreeterLog: ** (lightdm-gtk-greeter:9382): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden 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:6675): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden 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: MSI MS-6741 Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic root=UUID=b7a652e9-aea3-4c8a-bf11-32ec8d22b3bb ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25 Tags: trusty ubuntu Uname: Linux 3.13.0-63-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare saned scanner sudo _MarkForUpload: True dmi.bios.date: 04/02/01 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Version 07.00T dmi.board.name: MS-6741 dmi.board.vendor: MSI dmi.board.version: 1.0 d
[Touch-packages] [Bug 1325940] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1325940/+attachment/4518423/+files/ProcInterrupts.txt -- 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/1325940 Title: Desktop sometimes comes up with undisplayable screen resolution Status in xorg package in Ubuntu: Incomplete Bug description: Hello, the PC from which I'm sending this report sometimes fails to boot into the desktop properly (which desktop environment doesn't seem to matter). In the failure case the following happens: - The Plymouth Ubuntu splash gets displayed, but it looks distorted. Flickering horizontal artifacts are shown all over the screen, it looks a bit like a CRT Television with low signal. - When the desktop is loaded (via autologin), one can see short glimpses of its wallpaper, but after a few second the screen becomes black and remains that way. The monitor _does_ seem to receive a signal though. - It is possible to switch to TTYs and to use them, but they show similar artifacts like the Plymouth logo. - If I query the display information on the monitor's OSD when the screen is distorted, it reports a resolution of 1681x1050 or 1683x1050, which is 1-3 pixel bigger than the native horizontal resolution of the 22" LCD screen. Switching between different resolutions via entering 'xrandr --size 1024x768' blindly, followed by 'xrandr --size 1680x1050' brings up the native resolution properly. This does not happen on every boot, only in ~10-15% of the cases. I was not able to find any pattern so far in the occurence of this bug. The only thing I observed is that it _never_ happens when Windows XP is started, thus my assumption is that the bug is related to the xserver-xorg-video-radeon driver. I tried to specify the correct resolution explicitly on the kernel command line(adding video=DVI-I-1:1680x1050 ) but this has no positive effect. The monitor is connected via DVI. Below is a video attached that tries to show how the TTYs look when this bug occurs. Notice the abnormal blue lines, which are constantly flickering. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-radeon 1:7.3.0-1ubuntu3.1 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Jun 3 13:23:38 2014 InstallationDate: Installed on 2014-04-22 (41 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV350 [Radeon 9550] [1002:4153] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932a] Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932b] InstallationDate: Installed on 2014-04-22 (570 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) LightdmGreeterLog: ** (lightdm-gtk-greeter:9382): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden 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:6675): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden 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: MSI MS-6741 Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic root=UUID=b7a652e9-aea3-4c8a-bf11-32ec8d22b3bb ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25 Tags: trusty ubuntu Uname: Linux 3.13.0-63-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare saned scanner sudo _MarkForUpload: True dmi.bios.date: 04/02/01 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Version 07.00T dmi.board.name: MS-6741 dmi.board.vendor: MSI dmi.boa
[Touch-packages] [Bug 1325940] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1325940/+attachment/4518424/+files/ProcModules.txt -- 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/1325940 Title: Desktop sometimes comes up with undisplayable screen resolution Status in xorg package in Ubuntu: Incomplete Bug description: Hello, the PC from which I'm sending this report sometimes fails to boot into the desktop properly (which desktop environment doesn't seem to matter). In the failure case the following happens: - The Plymouth Ubuntu splash gets displayed, but it looks distorted. Flickering horizontal artifacts are shown all over the screen, it looks a bit like a CRT Television with low signal. - When the desktop is loaded (via autologin), one can see short glimpses of its wallpaper, but after a few second the screen becomes black and remains that way. The monitor _does_ seem to receive a signal though. - It is possible to switch to TTYs and to use them, but they show similar artifacts like the Plymouth logo. - If I query the display information on the monitor's OSD when the screen is distorted, it reports a resolution of 1681x1050 or 1683x1050, which is 1-3 pixel bigger than the native horizontal resolution of the 22" LCD screen. Switching between different resolutions via entering 'xrandr --size 1024x768' blindly, followed by 'xrandr --size 1680x1050' brings up the native resolution properly. This does not happen on every boot, only in ~10-15% of the cases. I was not able to find any pattern so far in the occurence of this bug. The only thing I observed is that it _never_ happens when Windows XP is started, thus my assumption is that the bug is related to the xserver-xorg-video-radeon driver. I tried to specify the correct resolution explicitly on the kernel command line(adding video=DVI-I-1:1680x1050 ) but this has no positive effect. The monitor is connected via DVI. Below is a video attached that tries to show how the TTYs look when this bug occurs. Notice the abnormal blue lines, which are constantly flickering. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-radeon 1:7.3.0-1ubuntu3.1 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Jun 3 13:23:38 2014 InstallationDate: Installed on 2014-04-22 (41 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV350 [Radeon 9550] [1002:4153] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932a] Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932b] InstallationDate: Installed on 2014-04-22 (570 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) LightdmGreeterLog: ** (lightdm-gtk-greeter:9382): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden 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:6675): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden 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: MSI MS-6741 Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic root=UUID=b7a652e9-aea3-4c8a-bf11-32ec8d22b3bb ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25 Tags: trusty ubuntu Uname: Linux 3.13.0-63-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare saned scanner sudo _MarkForUpload: True dmi.bios.date: 04/02/01 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Version 07.00T dmi.board.name: MS-6741 dmi.board.vendor: MSI dmi.board.ver
[Touch-packages] [Bug 1325940] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1325940/+attachment/4518422/+files/ProcEnviron.txt -- 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/1325940 Title: Desktop sometimes comes up with undisplayable screen resolution Status in xorg package in Ubuntu: Incomplete Bug description: Hello, the PC from which I'm sending this report sometimes fails to boot into the desktop properly (which desktop environment doesn't seem to matter). In the failure case the following happens: - The Plymouth Ubuntu splash gets displayed, but it looks distorted. Flickering horizontal artifacts are shown all over the screen, it looks a bit like a CRT Television with low signal. - When the desktop is loaded (via autologin), one can see short glimpses of its wallpaper, but after a few second the screen becomes black and remains that way. The monitor _does_ seem to receive a signal though. - It is possible to switch to TTYs and to use them, but they show similar artifacts like the Plymouth logo. - If I query the display information on the monitor's OSD when the screen is distorted, it reports a resolution of 1681x1050 or 1683x1050, which is 1-3 pixel bigger than the native horizontal resolution of the 22" LCD screen. Switching between different resolutions via entering 'xrandr --size 1024x768' blindly, followed by 'xrandr --size 1680x1050' brings up the native resolution properly. This does not happen on every boot, only in ~10-15% of the cases. I was not able to find any pattern so far in the occurence of this bug. The only thing I observed is that it _never_ happens when Windows XP is started, thus my assumption is that the bug is related to the xserver-xorg-video-radeon driver. I tried to specify the correct resolution explicitly on the kernel command line(adding video=DVI-I-1:1680x1050 ) but this has no positive effect. The monitor is connected via DVI. Below is a video attached that tries to show how the TTYs look when this bug occurs. Notice the abnormal blue lines, which are constantly flickering. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-radeon 1:7.3.0-1ubuntu3.1 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Jun 3 13:23:38 2014 InstallationDate: Installed on 2014-04-22 (41 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV350 [Radeon 9550] [1002:4153] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932a] Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932b] InstallationDate: Installed on 2014-04-22 (570 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) LightdmGreeterLog: ** (lightdm-gtk-greeter:9382): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden 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:6675): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden 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: MSI MS-6741 Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic root=UUID=b7a652e9-aea3-4c8a-bf11-32ec8d22b3bb ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25 Tags: trusty ubuntu Uname: Linux 3.13.0-63-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare saned scanner sudo _MarkForUpload: True dmi.bios.date: 04/02/01 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Version 07.00T dmi.board.name: MS-6741 dmi.board.vendor: MSI dmi.board.ver
[Touch-packages] [Bug 1325940] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1325940/+attachment/4518419/+files/Lspci.txt -- 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/1325940 Title: Desktop sometimes comes up with undisplayable screen resolution Status in xorg package in Ubuntu: Incomplete Bug description: Hello, the PC from which I'm sending this report sometimes fails to boot into the desktop properly (which desktop environment doesn't seem to matter). In the failure case the following happens: - The Plymouth Ubuntu splash gets displayed, but it looks distorted. Flickering horizontal artifacts are shown all over the screen, it looks a bit like a CRT Television with low signal. - When the desktop is loaded (via autologin), one can see short glimpses of its wallpaper, but after a few second the screen becomes black and remains that way. The monitor _does_ seem to receive a signal though. - It is possible to switch to TTYs and to use them, but they show similar artifacts like the Plymouth logo. - If I query the display information on the monitor's OSD when the screen is distorted, it reports a resolution of 1681x1050 or 1683x1050, which is 1-3 pixel bigger than the native horizontal resolution of the 22" LCD screen. Switching between different resolutions via entering 'xrandr --size 1024x768' blindly, followed by 'xrandr --size 1680x1050' brings up the native resolution properly. This does not happen on every boot, only in ~10-15% of the cases. I was not able to find any pattern so far in the occurence of this bug. The only thing I observed is that it _never_ happens when Windows XP is started, thus my assumption is that the bug is related to the xserver-xorg-video-radeon driver. I tried to specify the correct resolution explicitly on the kernel command line(adding video=DVI-I-1:1680x1050 ) but this has no positive effect. The monitor is connected via DVI. Below is a video attached that tries to show how the TTYs look when this bug occurs. Notice the abnormal blue lines, which are constantly flickering. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-radeon 1:7.3.0-1ubuntu3.1 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Jun 3 13:23:38 2014 InstallationDate: Installed on 2014-04-22 (41 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV350 [Radeon 9550] [1002:4153] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932a] Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932b] InstallationDate: Installed on 2014-04-22 (570 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) LightdmGreeterLog: ** (lightdm-gtk-greeter:9382): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden 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:6675): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden 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: MSI MS-6741 Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic root=UUID=b7a652e9-aea3-4c8a-bf11-32ec8d22b3bb ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25 Tags: trusty ubuntu Uname: Linux 3.13.0-63-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare saned scanner sudo _MarkForUpload: True dmi.bios.date: 04/02/01 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Version 07.00T dmi.board.name: MS-6741 dmi.board.vendor: MSI dmi.board.version: 1.0 d
[Touch-packages] [Bug 1325940] DpkgLog.txt
apport information ** Attachment added: "DpkgLog.txt" https://bugs.launchpad.net/bugs/1325940/+attachment/4518416/+files/DpkgLog.txt -- 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/1325940 Title: Desktop sometimes comes up with undisplayable screen resolution Status in xorg package in Ubuntu: Incomplete Bug description: Hello, the PC from which I'm sending this report sometimes fails to boot into the desktop properly (which desktop environment doesn't seem to matter). In the failure case the following happens: - The Plymouth Ubuntu splash gets displayed, but it looks distorted. Flickering horizontal artifacts are shown all over the screen, it looks a bit like a CRT Television with low signal. - When the desktop is loaded (via autologin), one can see short glimpses of its wallpaper, but after a few second the screen becomes black and remains that way. The monitor _does_ seem to receive a signal though. - It is possible to switch to TTYs and to use them, but they show similar artifacts like the Plymouth logo. - If I query the display information on the monitor's OSD when the screen is distorted, it reports a resolution of 1681x1050 or 1683x1050, which is 1-3 pixel bigger than the native horizontal resolution of the 22" LCD screen. Switching between different resolutions via entering 'xrandr --size 1024x768' blindly, followed by 'xrandr --size 1680x1050' brings up the native resolution properly. This does not happen on every boot, only in ~10-15% of the cases. I was not able to find any pattern so far in the occurence of this bug. The only thing I observed is that it _never_ happens when Windows XP is started, thus my assumption is that the bug is related to the xserver-xorg-video-radeon driver. I tried to specify the correct resolution explicitly on the kernel command line(adding video=DVI-I-1:1680x1050 ) but this has no positive effect. The monitor is connected via DVI. Below is a video attached that tries to show how the TTYs look when this bug occurs. Notice the abnormal blue lines, which are constantly flickering. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-radeon 1:7.3.0-1ubuntu3.1 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Jun 3 13:23:38 2014 InstallationDate: Installed on 2014-04-22 (41 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV350 [Radeon 9550] [1002:4153] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932a] Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932b] InstallationDate: Installed on 2014-04-22 (570 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) LightdmGreeterLog: ** (lightdm-gtk-greeter:9382): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden 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:6675): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden 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: MSI MS-6741 Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic root=UUID=b7a652e9-aea3-4c8a-bf11-32ec8d22b3bb ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25 Tags: trusty ubuntu Uname: Linux 3.13.0-63-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare saned scanner sudo _MarkForUpload: True dmi.bios.date: 04/02/01 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Version 07.00T dmi.board.name: MS-6741 dmi.board.vendor: MSI dmi.board.version: 1.
[Touch-packages] [Bug 1325940] LightdmLog.txt
apport information ** Attachment added: "LightdmLog.txt" https://bugs.launchpad.net/bugs/1325940/+attachment/4518418/+files/LightdmLog.txt -- 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/1325940 Title: Desktop sometimes comes up with undisplayable screen resolution Status in xorg package in Ubuntu: Incomplete Bug description: Hello, the PC from which I'm sending this report sometimes fails to boot into the desktop properly (which desktop environment doesn't seem to matter). In the failure case the following happens: - The Plymouth Ubuntu splash gets displayed, but it looks distorted. Flickering horizontal artifacts are shown all over the screen, it looks a bit like a CRT Television with low signal. - When the desktop is loaded (via autologin), one can see short glimpses of its wallpaper, but after a few second the screen becomes black and remains that way. The monitor _does_ seem to receive a signal though. - It is possible to switch to TTYs and to use them, but they show similar artifacts like the Plymouth logo. - If I query the display information on the monitor's OSD when the screen is distorted, it reports a resolution of 1681x1050 or 1683x1050, which is 1-3 pixel bigger than the native horizontal resolution of the 22" LCD screen. Switching between different resolutions via entering 'xrandr --size 1024x768' blindly, followed by 'xrandr --size 1680x1050' brings up the native resolution properly. This does not happen on every boot, only in ~10-15% of the cases. I was not able to find any pattern so far in the occurence of this bug. The only thing I observed is that it _never_ happens when Windows XP is started, thus my assumption is that the bug is related to the xserver-xorg-video-radeon driver. I tried to specify the correct resolution explicitly on the kernel command line(adding video=DVI-I-1:1680x1050 ) but this has no positive effect. The monitor is connected via DVI. Below is a video attached that tries to show how the TTYs look when this bug occurs. Notice the abnormal blue lines, which are constantly flickering. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-radeon 1:7.3.0-1ubuntu3.1 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Jun 3 13:23:38 2014 InstallationDate: Installed on 2014-04-22 (41 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV350 [Radeon 9550] [1002:4153] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932a] Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932b] InstallationDate: Installed on 2014-04-22 (570 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) LightdmGreeterLog: ** (lightdm-gtk-greeter:9382): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden 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:6675): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden 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: MSI MS-6741 Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic root=UUID=b7a652e9-aea3-4c8a-bf11-32ec8d22b3bb ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25 Tags: trusty ubuntu Uname: Linux 3.13.0-63-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare saned scanner sudo _MarkForUpload: True dmi.bios.date: 04/02/01 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Version 07.00T dmi.board.name: MS-6741 dmi.board.vendor: MSI dmi.board.versi
[Touch-packages] [Bug 1325940] LightdmDisplayLog.txt
apport information ** Attachment added: "LightdmDisplayLog.txt" https://bugs.launchpad.net/bugs/1325940/+attachment/4518417/+files/LightdmDisplayLog.txt -- 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/1325940 Title: Desktop sometimes comes up with undisplayable screen resolution Status in xorg package in Ubuntu: Incomplete Bug description: Hello, the PC from which I'm sending this report sometimes fails to boot into the desktop properly (which desktop environment doesn't seem to matter). In the failure case the following happens: - The Plymouth Ubuntu splash gets displayed, but it looks distorted. Flickering horizontal artifacts are shown all over the screen, it looks a bit like a CRT Television with low signal. - When the desktop is loaded (via autologin), one can see short glimpses of its wallpaper, but after a few second the screen becomes black and remains that way. The monitor _does_ seem to receive a signal though. - It is possible to switch to TTYs and to use them, but they show similar artifacts like the Plymouth logo. - If I query the display information on the monitor's OSD when the screen is distorted, it reports a resolution of 1681x1050 or 1683x1050, which is 1-3 pixel bigger than the native horizontal resolution of the 22" LCD screen. Switching between different resolutions via entering 'xrandr --size 1024x768' blindly, followed by 'xrandr --size 1680x1050' brings up the native resolution properly. This does not happen on every boot, only in ~10-15% of the cases. I was not able to find any pattern so far in the occurence of this bug. The only thing I observed is that it _never_ happens when Windows XP is started, thus my assumption is that the bug is related to the xserver-xorg-video-radeon driver. I tried to specify the correct resolution explicitly on the kernel command line(adding video=DVI-I-1:1680x1050 ) but this has no positive effect. The monitor is connected via DVI. Below is a video attached that tries to show how the TTYs look when this bug occurs. Notice the abnormal blue lines, which are constantly flickering. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-radeon 1:7.3.0-1ubuntu3.1 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Jun 3 13:23:38 2014 InstallationDate: Installed on 2014-04-22 (41 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV350 [Radeon 9550] [1002:4153] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932a] Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932b] InstallationDate: Installed on 2014-04-22 (570 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) LightdmGreeterLog: ** (lightdm-gtk-greeter:9382): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden 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:6675): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden 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: MSI MS-6741 Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic root=UUID=b7a652e9-aea3-4c8a-bf11-32ec8d22b3bb ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25 Tags: trusty ubuntu Uname: Linux 3.13.0-63-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare saned scanner sudo _MarkForUpload: True dmi.bios.date: 04/02/01 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Version 07.00T dmi.board.name: MS-6741 dmi.board.vendor: MSI d
[Touch-packages] [Bug 1325940] BootLog.txt
apport information ** Attachment added: "BootLog.txt" https://bugs.launchpad.net/bugs/1325940/+attachment/4518413/+files/BootLog.txt -- 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/1325940 Title: Desktop sometimes comes up with undisplayable screen resolution Status in xorg package in Ubuntu: Incomplete Bug description: Hello, the PC from which I'm sending this report sometimes fails to boot into the desktop properly (which desktop environment doesn't seem to matter). In the failure case the following happens: - The Plymouth Ubuntu splash gets displayed, but it looks distorted. Flickering horizontal artifacts are shown all over the screen, it looks a bit like a CRT Television with low signal. - When the desktop is loaded (via autologin), one can see short glimpses of its wallpaper, but after a few second the screen becomes black and remains that way. The monitor _does_ seem to receive a signal though. - It is possible to switch to TTYs and to use them, but they show similar artifacts like the Plymouth logo. - If I query the display information on the monitor's OSD when the screen is distorted, it reports a resolution of 1681x1050 or 1683x1050, which is 1-3 pixel bigger than the native horizontal resolution of the 22" LCD screen. Switching between different resolutions via entering 'xrandr --size 1024x768' blindly, followed by 'xrandr --size 1680x1050' brings up the native resolution properly. This does not happen on every boot, only in ~10-15% of the cases. I was not able to find any pattern so far in the occurence of this bug. The only thing I observed is that it _never_ happens when Windows XP is started, thus my assumption is that the bug is related to the xserver-xorg-video-radeon driver. I tried to specify the correct resolution explicitly on the kernel command line(adding video=DVI-I-1:1680x1050 ) but this has no positive effect. The monitor is connected via DVI. Below is a video attached that tries to show how the TTYs look when this bug occurs. Notice the abnormal blue lines, which are constantly flickering. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-radeon 1:7.3.0-1ubuntu3.1 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Jun 3 13:23:38 2014 InstallationDate: Installed on 2014-04-22 (41 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV350 [Radeon 9550] [1002:4153] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932a] Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932b] InstallationDate: Installed on 2014-04-22 (570 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) LightdmGreeterLog: ** (lightdm-gtk-greeter:9382): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden 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:6675): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden 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: MSI MS-6741 Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic root=UUID=b7a652e9-aea3-4c8a-bf11-32ec8d22b3bb ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25 Tags: trusty ubuntu Uname: Linux 3.13.0-63-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare saned scanner sudo _MarkForUpload: True dmi.bios.date: 04/02/01 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Version 07.00T dmi.board.name: MS-6741 dmi.board.vendor: MSI dmi.board.version: 1.
[Touch-packages] [Bug 1325940] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1325940/+attachment/4518414/+files/CurrentDmesg.txt -- 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/1325940 Title: Desktop sometimes comes up with undisplayable screen resolution Status in xorg package in Ubuntu: Incomplete Bug description: Hello, the PC from which I'm sending this report sometimes fails to boot into the desktop properly (which desktop environment doesn't seem to matter). In the failure case the following happens: - The Plymouth Ubuntu splash gets displayed, but it looks distorted. Flickering horizontal artifacts are shown all over the screen, it looks a bit like a CRT Television with low signal. - When the desktop is loaded (via autologin), one can see short glimpses of its wallpaper, but after a few second the screen becomes black and remains that way. The monitor _does_ seem to receive a signal though. - It is possible to switch to TTYs and to use them, but they show similar artifacts like the Plymouth logo. - If I query the display information on the monitor's OSD when the screen is distorted, it reports a resolution of 1681x1050 or 1683x1050, which is 1-3 pixel bigger than the native horizontal resolution of the 22" LCD screen. Switching between different resolutions via entering 'xrandr --size 1024x768' blindly, followed by 'xrandr --size 1680x1050' brings up the native resolution properly. This does not happen on every boot, only in ~10-15% of the cases. I was not able to find any pattern so far in the occurence of this bug. The only thing I observed is that it _never_ happens when Windows XP is started, thus my assumption is that the bug is related to the xserver-xorg-video-radeon driver. I tried to specify the correct resolution explicitly on the kernel command line(adding video=DVI-I-1:1680x1050 ) but this has no positive effect. The monitor is connected via DVI. Below is a video attached that tries to show how the TTYs look when this bug occurs. Notice the abnormal blue lines, which are constantly flickering. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-radeon 1:7.3.0-1ubuntu3.1 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Jun 3 13:23:38 2014 InstallationDate: Installed on 2014-04-22 (41 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV350 [Radeon 9550] [1002:4153] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932a] Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932b] InstallationDate: Installed on 2014-04-22 (570 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) LightdmGreeterLog: ** (lightdm-gtk-greeter:9382): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden 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:6675): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden 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: MSI MS-6741 Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic root=UUID=b7a652e9-aea3-4c8a-bf11-32ec8d22b3bb ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25 Tags: trusty ubuntu Uname: Linux 3.13.0-63-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare saned scanner sudo _MarkForUpload: True dmi.bios.date: 04/02/01 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Version 07.00T dmi.board.name: MS-6741 dmi.board.vendor: MSI dmi.board.v
[Touch-packages] [Bug 1325940] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1325940/+attachment/4518415/+files/Dependencies.txt -- 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/1325940 Title: Desktop sometimes comes up with undisplayable screen resolution Status in xorg package in Ubuntu: Incomplete Bug description: Hello, the PC from which I'm sending this report sometimes fails to boot into the desktop properly (which desktop environment doesn't seem to matter). In the failure case the following happens: - The Plymouth Ubuntu splash gets displayed, but it looks distorted. Flickering horizontal artifacts are shown all over the screen, it looks a bit like a CRT Television with low signal. - When the desktop is loaded (via autologin), one can see short glimpses of its wallpaper, but after a few second the screen becomes black and remains that way. The monitor _does_ seem to receive a signal though. - It is possible to switch to TTYs and to use them, but they show similar artifacts like the Plymouth logo. - If I query the display information on the monitor's OSD when the screen is distorted, it reports a resolution of 1681x1050 or 1683x1050, which is 1-3 pixel bigger than the native horizontal resolution of the 22" LCD screen. Switching between different resolutions via entering 'xrandr --size 1024x768' blindly, followed by 'xrandr --size 1680x1050' brings up the native resolution properly. This does not happen on every boot, only in ~10-15% of the cases. I was not able to find any pattern so far in the occurence of this bug. The only thing I observed is that it _never_ happens when Windows XP is started, thus my assumption is that the bug is related to the xserver-xorg-video-radeon driver. I tried to specify the correct resolution explicitly on the kernel command line(adding video=DVI-I-1:1680x1050 ) but this has no positive effect. The monitor is connected via DVI. Below is a video attached that tries to show how the TTYs look when this bug occurs. Notice the abnormal blue lines, which are constantly flickering. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-radeon 1:7.3.0-1ubuntu3.1 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Jun 3 13:23:38 2014 InstallationDate: Installed on 2014-04-22 (41 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV350 [Radeon 9550] [1002:4153] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932a] Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932b] InstallationDate: Installed on 2014-04-22 (570 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) LightdmGreeterLog: ** (lightdm-gtk-greeter:9382): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden 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:6675): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden 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: MSI MS-6741 Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic root=UUID=b7a652e9-aea3-4c8a-bf11-32ec8d22b3bb ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25 Tags: trusty ubuntu Uname: Linux 3.13.0-63-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare saned scanner sudo _MarkForUpload: True dmi.bios.date: 04/02/01 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Version 07.00T dmi.board.name: MS-6741 dmi.board.vendor: MSI dmi.board.v
Re: [Touch-packages] [Bug 1345682] Re: fsck on 24TB ext4 keeps crashing
I am not familiar with the tool, but I was concerned about the file/directory names. I can look into the -s option and might be doable. I am still without a working chassis that can handle as many harddrives I have. I have a new motherboard and card. I was able to find online other people having similar problems w/fsck unable to clean > 16TB. Is that problem considered fixed and in the mainline? It will help me prioritize this. On Fri, Nov 13, 2015 at 10:44 AM, Theodore Ts'o wrote: > You do realize that e2image doesn't contain any data blocks --- just > file system metadata blocks, right? And if you are concerned about the > directory names being too revealing, e2image has a -s option which will > scramble the directory file names. See the section "RAW IMAGE FILES" in > the e2image man page. > > Failing that, there probably isn't much we can do, short of having you > get a newer version of e2fsprogs, build it with debugging information > enabled, and then run it under a debugger so we can get an accurate > stack trace. I will note that the stack trace printed by e2fsck > doesn't look completely sane, since ext2fs_rb_next() doesn't actually > call any C library functions, and far too many of the stack frames don't > have symbol names to annotate the addresses. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1345682 > > Title: > fsck on 24TB ext4 keeps crashing > > Status in e2fsprogs package in Ubuntu: > Incomplete > > Bug description: > date; fsck -vy /dev/mapper/raid61p1 ;date > Thu Jul 17 11:54:21 PDT 2014 > fsck from util-linux 2.20.1 > I can't get my ext4 24TB to fsck clean. there came a whole bunch of file > stat problems after a clean reboot. > I tried 3 times so far, and each does something like segfault. I looked > twice, and the errors were different, > but was able to capture one output. The system has 6GB ram, and it used > up all the memory. ended up adding 25GB > of swap as fsck seems to use up a huge amount of memory. After a long > while, usually after mem use is >90%, > I come back to see the fsck has crashed and file system is still not > clean. > > The reboot was clean and should not have caused any corruption. the > system is using ubuntu-14.04 > > # uname -a > Linux gigabyte133 3.13.0-32-generic #57-Ubuntu SMP Tue Jul 15 03:51:08 > UTC 2014 x86_64 x86_64 x86_64 GNU/Linux > root@gigabyte133:~# > > I had to use the 64 bit version since the 32 bit version I couldn't get > more than 15TB file system built and read > that there were compatibility problems between 32bit version with the -O > 64bit and the 64 bit version so just > built the whole thing in 64 bit ubuntu.. > > > e2fsck 1.42.9 (4-Feb-2014) > > > /dev/mapper/raid61p1 contains a file system with errors, check forced. > Pass 1: Checking inodes, blocks, and sizes > Inode 203167820 has compression flag set on filesystem without > compression support. Clear? yes > > Signal (11) SIGSEGV si_code=SI_KERNEL fault addr=(nil) > fsck.ext4[0x4266f1] > /lib/x86_64-linux-gnu/libc.so.6(+0x36ff0)[0x7fd38d087ff0] > /lib/x86_64-linux-gnu/libext2fs.so.2(ext2fs_rb_next+0x23)[0x7fd38dc7bc43] > /lib/x86_64-linux-gnu/libext2fs.so.2(+0x10670)[0x7fd38dc5e670] > fsck.ext4[0x4100f6]# lsb_release -va > No LSB modules are available. > Distributor ID: Ubuntu > Description:Ubuntu 14.04 LTS > Release:14.04 > Codename: trusty > > /lib/x86_64-linux-gnu/libext2fs.so.2(+0x11c3d)[0x7fd38dc5fc3d] > /lib/x86_64-linux-gnu/libext2fs.so.2(+0x11f78)[0x7fd38dc5ff78] > > /lib/x86_64-linux-gnu/libext2fs.so.2(ext2fs_block_iterate3+0xa13)[0x7fd38dc60b13] > fsck.ext4[0x4115c4] > fsck.ext4[0x412699] > fsck.ext4[0x412761] > > /lib/x86_64-linux-gnu/libext2fs.so.2(ext2fs_get_next_inode_full+0x59)[0x7fd38dc6c9a9] > fsck.ext4(e2fsck_pass1+0x8d8)[0x4130c8] > fsck.ext4(e2fsck_run+0x52)[0x40deb2] > fsck.ext4(main+0xd27)[0x40a0e7] > /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7fd38d072ec5] > fsck.ext4[0x40bde6] > Thu Jul 17 15:55:01 PDT 2014 > > # lsb_release -va > No LSB modules are available. > Distributor ID: Ubuntu > Description:Ubuntu 14.04 LTS > Release:14.04 > Codename: trusty > > ProblemType: Bug > DistroRelease: Ubuntu 14.04 > Package: util-linux 2.20.1-5.1ubuntu20.1 > ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 > Uname: Linux 3.13.0-32-generic x86_64 > NonfreeKernelModules: zfs zunicode zavl zcommon znvpair > ApportVersion: 2.14.1-0ubuntu3.2 > Architecture: amd64 > Date: Sat Jul 19 18:49:32 2014 > InstallationDate: Installed on 2014-07-11 (8 days ago) > InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 > (20140417) > ProcEnviron: >TERM=xterm >PATH=(custom, no user) >LANG=en_US.UTF-8 >SHELL=/bin/bash > SourcePackage: util-linux > UpgradeStatus: No upgrade log present (pro
[Touch-packages] [Bug 1325940] Re: Desktop sometimes comes up with undisplayable screen resolution
apport information ** Tags added: apport-collected ubuntu ** Description changed: Hello, the PC from which I'm sending this report sometimes fails to boot into the desktop properly (which desktop environment doesn't seem to matter). In the failure case the following happens: - The Plymouth Ubuntu splash gets displayed, but it looks distorted. Flickering horizontal artifacts are shown all over the screen, it looks a bit like a CRT Television with low signal. - When the desktop is loaded (via autologin), one can see short glimpses of its wallpaper, but after a few second the screen becomes black and remains that way. The monitor _does_ seem to receive a signal though. - It is possible to switch to TTYs and to use them, but they show similar artifacts like the Plymouth logo. - If I query the display information on the monitor's OSD when the screen is distorted, it reports a resolution of 1681x1050 or 1683x1050, which is 1-3 pixel bigger than the native horizontal resolution of the 22" LCD screen. Switching between different resolutions via entering 'xrandr --size 1024x768' blindly, followed by 'xrandr --size 1680x1050' brings up the native resolution properly. This does not happen on every boot, only in ~10-15% of the cases. I was not able to find any pattern so far in the occurence of this bug. The only thing I observed is that it _never_ happens when Windows XP is started, thus my assumption is that the bug is related to the xserver- xorg-video-radeon driver. I tried to specify the correct resolution explicitly on the kernel command line(adding video=DVI-I-1:1680x1050 ) but this has no positive effect. The monitor is connected via DVI. Below is a video attached that tries to show how the TTYs look when this bug occurs. Notice the abnormal blue lines, which are constantly flickering. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-radeon 1:7.3.0-1ubuntu3.1 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Jun 3 13:23:38 2014 InstallationDate: Installed on 2014-04-22 (41 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) + --- + ApportVersion: 2.14.1-0ubuntu3.18 + Architecture: amd64 + CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' + CompositorRunning: None + CurrentDesktop: XFCE + DistUpgraded: Fresh install + DistroCodename: trusty + DistroRelease: Ubuntu 14.04 + DistroVariant: ubuntu + ExtraDebuggingInterest: Yes + GraphicsCard: + Advanced Micro Devices, Inc. [AMD/ATI] RV350 [Radeon 9550] [1002:4153] (prog-if 00 [VGA controller]) +Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932a] +Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932b] + InstallationDate: Installed on 2014-04-22 (570 days ago) + InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) + LightdmGreeterLog: + ** (lightdm-gtk-greeter:9382): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden + 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:6675): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden + 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: MSI MS-6741 + Package: xorg 1:7.7+1ubuntu8.1 + PackageArchitecture: amd64 + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic root=UUID=b7a652e9-aea3-4c8a-bf11-32ec8d22b3bb ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25 + Tags: trusty ubuntu + Uname: Linux 3.13.0-63-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare saned scanner sudo + _MarkForUpload: True + dmi.bios.date: 04/02/01 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: Version 07.00T + dmi.board.name: MS-6741 + dmi.board.vendor: MSI + dmi.board.version: 1.0 + dmi.chassis.asset.tag: 0123ABC + dmi.chassis.type: 3 + dmi.chassis.vendor: Uknown Chassis Manufacture + dmi.chassis.version: Version 1.00 + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrVersion07.00T:bd04/02/01:svnMSI:pnMS-6741:pvr1.0:rvnMSI:rnMS-6741:rvr1.0:cvnUknownChassisManufacture:ct3:cvrVersion1.00: + dmi.product.name: MS-6741 + dmi.
[Touch-packages] [Bug 1482411] Re: Pulseaudio set Kodi sount to 1% each time I change video
It starts with no audio every time. -- 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/1482411 Title: Pulseaudio set Kodi sount to 1% each time I change video Status in alsa-driver package in Ubuntu: Incomplete Status in kodi package in Ubuntu: Confirmed Bug description: Hi, here is the bug : Each time Kodi change the video playing (like coming to next TV show episode), Pulseaudio set Kodi sound level to 1% and I need to go back to pavucontrol to upgrade to 100% each time ! ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: kevin 10243 F pulseaudio /dev/snd/controlC1: kevin 10243 F pulseaudio /dev/snd/pcmC0D1p: kevin 10243 F...m pulseaudio /dev/snd/controlC0: kevin 10243 F pulseaudio CurrentDesktop: Unity Date: Fri Aug 7 00:34:05 2015 InstallationDate: Installed on 2015-07-14 (23 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Audio interne - HDA ATI SB Symptom_Jack: Grey SPDIF Out, Rear Panel Symptom_Type: Sound works for a while, then breaks Title: [System Product Name, VIA VT1708S, Grey SPDIF Out, Rear Panel] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/13/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0702 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A77TD PRO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0702:bd08/13/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A77TDPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1482411/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1482411] Re: Pulseaudio set Kodi sount to 1% each time I change video
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: kodi (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1482411 Title: Pulseaudio set Kodi sount to 1% each time I change video Status in alsa-driver package in Ubuntu: Incomplete Status in kodi package in Ubuntu: Confirmed Bug description: Hi, here is the bug : Each time Kodi change the video playing (like coming to next TV show episode), Pulseaudio set Kodi sound level to 1% and I need to go back to pavucontrol to upgrade to 100% each time ! ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: kevin 10243 F pulseaudio /dev/snd/controlC1: kevin 10243 F pulseaudio /dev/snd/pcmC0D1p: kevin 10243 F...m pulseaudio /dev/snd/controlC0: kevin 10243 F pulseaudio CurrentDesktop: Unity Date: Fri Aug 7 00:34:05 2015 InstallationDate: Installed on 2015-07-14 (23 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Audio interne - HDA ATI SB Symptom_Jack: Grey SPDIF Out, Rear Panel Symptom_Type: Sound works for a while, then breaks Title: [System Product Name, VIA VT1708S, Grey SPDIF Out, Rear Panel] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/13/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0702 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A77TD PRO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0702:bd08/13/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A77TDPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1482411/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1382233] Re: whoopsie does not upload UnreportableReason field in crash reports
** No longer affects: whoopsie (Ubuntu Precise) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1382233 Title: whoopsie does not upload UnreportableReason field in crash reports Status in whoopsie package in Ubuntu: Fix Released Status in whoopsie-daisy source package in Precise: Fix Committed Status in whoopsie source package in Trusty: Fix Committed Status in whoopsie source package in Vivid: Fix Committed Status in whoopsie source package in Wily: Fix Committed Bug description: Test Case - 1) Edit a .crash file to have an UnreportableReason key and value e.g. UnreportableReason: Your system is weird. 2) sudo service whoopsie stop 3) start whoopsie pointing to errors.staging.ubuntu.com e.g. sudo CRASH_DB_URL=https://daisy.staging.ubuntu.com APPORT_REPORT_DIR=/var/crash/ whoopsie -f 4) Put said .crash file in /var/crash/ 5) Put a corresponding .upload file in /var/crash/ 6) Observe whoopsie uploading the .crash file from the whoopsie log [16:51:13] Reported OOPS ID 4ea43136-880e-11e5-828e-fa163e1893a8 7) go to errors.staging.ubuntu.com/oops/$OOPS_ID 8) verify the UnreportableReason appears there e.g.: https://errors.staging.ubuntu.com/oops/4ea43136-880e-11e5-828e-fa163e1893a8 In src/whoopsie.c we can see the following: /* We would only want this to see how many bugs would otherwise go * unreported: */ "UnreportableReason", The comment isn't exactly true. apport uses the UnreportableReason key to include the following information: "You have some obsolete package versions installed." It'd be useful if this information was sent to the Error Tracker so that we can decide not to ask for a core dump from these crash reports. The "obsolete package versions" check is done by checking to see if the most recent available version of the package is installed, so if someone does not have -updates enabled then that pocket is not checked and "obsolete package versions" will not be present. This is desirable because the retracers will check to see if the package version is available from any pocket. So if we send UnreportableReason to the Error Tracker we can stop asking for core dumps and retracing crashes that will fail to retrace. However, the value for UnreportableReason is translated so this may not end up helping much. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1382233/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 193325] Re: "unknown media type" during update
Installing new packages today still reports those missing media types during "Processing triggers for shared-mime-info." Are you ever going to fix this? For that matter, are you ever going to reply to my postings? This bug has persisted for years now. It's about time you resolve it. -- 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/193325 Title: "unknown media type" during update Status in Nautilus: Confirmed Status in shared-mime-info: Fix Released Status in shared-mime-info package in Ubuntu: Fix Released Bug description: Messages below seen during the latest round of updates. The messages from several packages seem to be mixed around, so I'm not sure which one triggered them. I suspect nautilus. Setting up shared-mime-info (0.23-3) ... Unknown media type in type 'x-content/video-vcd' Unknown media type in type 'x-content/video-svcd' Unknown media type in type 'x-content/video-dvd' Unknown media type in type 'x-content/image-dcf' Unknown media type in type 'x-content/audio-cdda' Unknown media type in type 'x-content/blank-cd' Unknown media type in type 'x-content/blank-dvd' Unknown media type in type 'x-content/blank-bd' Unknown media type in type 'x-content/blank-hddvd' Unknown media type in type 'x-content/audio-dvd' Unknown media type in type 'x-content/video-bluray' Unknown media type in type 'x-content/video-hddvd' Unknown media type in type 'x-content/image-picturecd' Unknown media type in type 'x-content/audio-player' Unknown media type in type 'x-content/software' Setting up ucf (3.004-0ubuntu3) ... Setting up seahorse (2.21.91-0ubuntu3) ... Unknown media type in type 'x-content/video-vcd' Unknown media type in type 'x-content/video-svcd' Unknown media type in type 'x-content/video-dvd' Unknown media type in type 'x-content/image-dcf' Unknown media type in type 'x-content/audio-cdda' Unknown media type in type 'x-content/blank-cd' Unknown media type in type 'x-content/blank-dvd' Unknown media type in type 'x-content/blank-bd' Unknown media type in type 'x-content/blank-hddvd' Unknown media type in type 'x-content/audio-dvd' Unknown media type in type 'x-content/video-bluray' Unknown media type in type 'x-content/video-hddvd' Unknown media type in type 'x-content/image-picturecd' Unknown media type in type 'x-content/audio-player' Unknown media type in type 'x-content/software' Setting up ubuntu-gdm-themes (0.24) ... Setting up linux-restricted-modules-common (2.6.24.9-8.25) ... Setting up nautilus-data (1:2.21.91-0ubuntu3) ... Unknown media type in type 'x-content/video-vcd' Unknown media type in type 'x-content/video-svcd' Unknown media type in type 'x-content/video-dvd' Unknown media type in type 'x-content/image-dcf' Unknown media type in type 'x-content/audio-cdda' Unknown media type in type 'x-content/blank-cd' Unknown media type in type 'x-content/blank-dvd' Unknown media type in type 'x-content/blank-bd' Unknown media type in type 'x-content/blank-hddvd' Unknown media type in type 'x-content/audio-dvd' Unknown media type in type 'x-content/video-bluray' Unknown media type in type 'x-content/video-hddvd' Unknown media type in type 'x-content/image-picturecd' Unknown media type in type 'x-content/audio-player' Unknown media type in type 'x-content/software' Setting up compiz-core (1:0.7.0-0ubuntu3) ... To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/193325/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1345682] Re: fsck on 24TB ext4 keeps crashing
You do realize that e2image doesn't contain any data blocks --- just file system metadata blocks, right? And if you are concerned about the directory names being too revealing, e2image has a -s option which will scramble the directory file names. See the section "RAW IMAGE FILES" in the e2image man page. Failing that, there probably isn't much we can do, short of having you get a newer version of e2fsprogs, build it with debugging information enabled, and then run it under a debugger so we can get an accurate stack trace. I will note that the stack trace printed by e2fsck doesn't look completely sane, since ext2fs_rb_next() doesn't actually call any C library functions, and far too many of the stack frames don't have symbol names to annotate the addresses. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1345682 Title: fsck on 24TB ext4 keeps crashing Status in e2fsprogs package in Ubuntu: Incomplete Bug description: date; fsck -vy /dev/mapper/raid61p1 ;date Thu Jul 17 11:54:21 PDT 2014 fsck from util-linux 2.20.1 I can't get my ext4 24TB to fsck clean. there came a whole bunch of file stat problems after a clean reboot. I tried 3 times so far, and each does something like segfault. I looked twice, and the errors were different, but was able to capture one output. The system has 6GB ram, and it used up all the memory. ended up adding 25GB of swap as fsck seems to use up a huge amount of memory. After a long while, usually after mem use is >90%, I come back to see the fsck has crashed and file system is still not clean. The reboot was clean and should not have caused any corruption. the system is using ubuntu-14.04 # uname -a Linux gigabyte133 3.13.0-32-generic #57-Ubuntu SMP Tue Jul 15 03:51:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux root@gigabyte133:~# I had to use the 64 bit version since the 32 bit version I couldn't get more than 15TB file system built and read that there were compatibility problems between 32bit version with the -O 64bit and the 64 bit version so just built the whole thing in 64 bit ubuntu.. e2fsck 1.42.9 (4-Feb-2014) /dev/mapper/raid61p1 contains a file system with errors, check forced. Pass 1: Checking inodes, blocks, and sizes Inode 203167820 has compression flag set on filesystem without compression support. Clear? yes Signal (11) SIGSEGV si_code=SI_KERNEL fault addr=(nil) fsck.ext4[0x4266f1] /lib/x86_64-linux-gnu/libc.so.6(+0x36ff0)[0x7fd38d087ff0] /lib/x86_64-linux-gnu/libext2fs.so.2(ext2fs_rb_next+0x23)[0x7fd38dc7bc43] /lib/x86_64-linux-gnu/libext2fs.so.2(+0x10670)[0x7fd38dc5e670] fsck.ext4[0x4100f6]# lsb_release -va No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 14.04 LTS Release:14.04 Codename: trusty /lib/x86_64-linux-gnu/libext2fs.so.2(+0x11c3d)[0x7fd38dc5fc3d] /lib/x86_64-linux-gnu/libext2fs.so.2(+0x11f78)[0x7fd38dc5ff78] /lib/x86_64-linux-gnu/libext2fs.so.2(ext2fs_block_iterate3+0xa13)[0x7fd38dc60b13] fsck.ext4[0x4115c4] fsck.ext4[0x412699] fsck.ext4[0x412761] /lib/x86_64-linux-gnu/libext2fs.so.2(ext2fs_get_next_inode_full+0x59)[0x7fd38dc6c9a9] fsck.ext4(e2fsck_pass1+0x8d8)[0x4130c8] fsck.ext4(e2fsck_run+0x52)[0x40deb2] fsck.ext4(main+0xd27)[0x40a0e7] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7fd38d072ec5] fsck.ext4[0x40bde6] Thu Jul 17 15:55:01 PDT 2014 # lsb_release -va No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 14.04 LTS Release:14.04 Codename: trusty ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: util-linux 2.20.1-5.1ubuntu20.1 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 Date: Sat Jul 19 18:49:32 2014 InstallationDate: Installed on 2014-07-11 (8 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: util-linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1345682/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452601] Re: vivid container's networking.service fails on boot with signal=PIPE
What I should do is try to back out some of my changes and determine whether I can duplicate the problem. Then I can determine which changes matter and which ones don't. I won't have time for a few days, but I will do my best. -- 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/1452601 Title: vivid container's networking.service fails on boot with signal=PIPE Status in lxc package in Ubuntu: Confirmed Bug description: When starting a Vivid container, it fails to get an IP address. It believes networking.service was successful, but actually it dies with SIGPIPE. Restarting networking.service gets an IP, as expected. Starting networking used to work with pre-vivid containers. I'm reasonably sure this fails 100% of the time. Limited user container, very standard setup (no unnecessary config; cgmanager and lxcfs installed), btrfs filesystem but not btrfs-backed (as it's limited user), ... root@vivid:/# systemctl status networking.service ● networking.service - LSB: Raise network interfaces. Loaded: loaded (/etc/init.d/networking) Drop-In: /run/systemd/generator/networking.service.d └─50-insserv.conf-$network.conf /lib/systemd/system/networking.service.d └─systemd.conf Active: active (exited) since Thu 2015-05-07 07:54:48 UTC; 9s ago Docs: man:systemd-sysv-generator(8) Process: 459 ExecStart=/etc/init.d/networking start (code=killed, signal=PIPE) root@vivid:/# systemctl restart networking.service root@vivid:/# systemctl status networking.service ● networking.service - LSB: Raise network interfaces. Loaded: loaded (/etc/init.d/networking) Drop-In: /run/systemd/generator/networking.service.d └─50-insserv.conf-$network.conf /lib/systemd/system/networking.service.d └─systemd.conf Active: active (running) since Thu 2015-05-07 07:56:38 UTC; 2s ago Docs: man:systemd-sysv-generator(8) Process: 992 ExecStop=/etc/init.d/networking stop (code=exited, status=0/SUCCESS) Process: 1033 ExecStart=/etc/init.d/networking start (code=exited, status=0/SUCCESS) CGroup: /user.slice/user-1000.slice/session-c2.scope/lxc/vivid/system.slice/networking.service ├─1096 dhclient -1 -v -pf /run/dhclient.eth0.pid -lf /var/lib/dhcp/dhclient.eth0.leases eth0 ├─1106 /bin/sh /etc/network/if-up.d/ntpdate ├─1109 lockfile-touch /var/lock/ntpdate-ifup ├─1125 /bin/sh /etc/network/if-up.d/ntpdate ├─1128 lockfile-create /var/lock/ntpdate-ifup └─1146 /usr/sbin/ntpdate -s ntp.ubuntu.com root@vivid:/# ip a ... 22: eth0: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 ... inet 10.0.3.102/24 brd 10.0.3.255 scope global eth0 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lxc 1.1.2-0ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Thu May 7 08:53:02 2015 SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1452601/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1516072] Re: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: trying to overwrite '/usr/share/man/man1/djpeg.1.gz', which is also in package libjpeg-turbo-progs 1.3.0
dpkg: warning: trying to overwrite '/usr/share/man/man1/djpeg.1.gz', which is also in package libjpeg-turbo-progs 1.3.0-0ubuntu2 dpkg: warning: trying to overwrite '/usr/share/man/man1/exifautotran.1.gz', which is also in package libjpeg-turbo-progs 1.3.0-0ubuntu2 dpkg: warning: trying to overwrite '/usr/share/man/man1/jpegtran.1.gz', which is also in package libjpeg-turbo-progs 1.3.0-0ubuntu2 dpkg: warning: trying to overwrite '/usr/share/man/man1/cjpeg.1.gz', which is also in package libjpeg-turbo-progs 1.3.0-0ubuntu2 dpkg: warning: trying to overwrite '/usr/share/man/man1/jpegexiforient.1.gz', which is also in package libjpeg-turbo-progs 1.3.0-0ubuntu2 dpkg: warning: trying to overwrite '/usr/share/man/man1/rdjpgcom.1.gz', which is also in package libjpeg-turbo-progs 1.3.0-0ubuntu2 dpkg: warning: trying to overwrite '/usr/share/man/man1/wrjpgcom.1.gz', which is also in package libjpeg-turbo-progs 1.3.0-0ubuntu2 dpkg: warning: trying to overwrite '/usr/bin/rdjpgcom', which is also in package libjpeg-turbo-progs 1.3.0-0ubuntu2 dpkg: warning: trying to overwrite '/usr/bin/wrjpgcom', which is also in package libjpeg-turbo-progs 1.3.0-0ubuntu2 dpkg: warning: trying to overwrite '/usr/bin/djpeg', which is also in package libjpeg-turbo-progs 1.3.0-0ubuntu2 dpkg: warning: trying to overwrite '/usr/bin/exifautotran', which is also in package libjpeg-turbo-progs 1.3.0-0ubuntu2 dpkg: warning: trying to overwrite '/usr/bin/cjpeg', which is also in package libjpeg-turbo-progs 1.3.0-0ubuntu2 dpkg: warning: trying to overwrite '/usr/bin/jpegtran', which is also in package libjpeg-turbo-progs 1.3.0-0ubuntu2 dpkg: warning: trying to overwrite '/usr/bin/jpegexiforient', which is also in package libjpeg-turbo-progs 1.3.0-0ubuntu2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libjpeg8-empty in Ubuntu. https://bugs.launchpad.net/bugs/1516072 Title: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: trying to overwrite '/usr/share/man/man1/djpeg.1.gz', which is also in package libjpeg-turbo-progs 1.3.0-0ubuntu2 Status in libjpeg8-empty package in Ubuntu: Confirmed Bug description: No problem noticed just a system problem detected notice, failed to install or remove package. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libjpeg-progs 8c-2ubuntu8 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.2-0ubuntu6 Architecture: amd64 Date: Fri Nov 13 10:00:17 2015 DuplicateSignature: Unpacking libjpeg-progs (1:9a-2ubuntu1) over (8c-2ubuntu8) ... dpkg: error processing archive /var/cache/apt/archives/libjpeg-progs_1%3a9a-2ubuntu1_amd64.deb (--unpack): trying to overwrite '/usr/share/man/man1/djpeg.1.gz', which is also in package libjpeg-turbo-progs 1.3.0-0ubuntu2 ErrorMessage: trying to overwrite '/usr/share/man/man1/djpeg.1.gz', which is also in package libjpeg-turbo-progs 1.3.0-0ubuntu2 InstallationDate: Installed on 2015-11-07 (5 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151107) RelatedPackageVersions: dpkg 1.18.3ubuntu1 apt 1.0.10.2ubuntu1 SourcePackage: libjpeg8-empty Title: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: trying to overwrite '/usr/share/man/man1/djpeg.1.gz', which is also in package libjpeg-turbo-progs 1.3.0-0ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjpeg8-empty/+bug/1516072/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
