[Touch-packages] [Bug 1619307] Re: Switching to USB sound device stops USB mouse clicks from registering Edit
Christopher, it's a JABRA Evolve 80 UC Duo USB -- 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/1619307 Title: Switching to USB sound device stops USB mouse clicks from registering Edit Status in xorg package in Ubuntu: Incomplete Bug description: As soon as I plugin the Jabra EVOLVE Headset the mouse pointer is somehow "captured" by the last active window. I can switch windows via alt-tab but left clicks in the new window still won't work, they will only work in the "old" window. WORKAROUND: Add 50-jabra.conf file in /usr/share/X11/xorg.conf.d with the following: Section "InputClass" Identifier "Jabra" MatchProduct "GN Netcom A/S Jabra EVOLVE LINK MS" Option "ButtonMapping" "0 0 0 0 0 0 0 0 0 0 0 0" EndSection and restart xorg-server. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Thu Sep 1 14:47:55 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: kubuntu DkmsStatus: virtualbox, 5.0.24, 4.4.0-34-generic, x86_64: installed virtualbox, 5.0.24, 4.4.0-36-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:0535] MachineType: Dell Inc. Latitude E6530 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-36-generic.efi.signed root=/dev/mapper/system-root_crypt ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/19/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0JC5MT dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd08/19/2015:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn0JC5MT:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6530 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Thu Sep 1 11:27:32 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 812 vendor LGD xserver.version: 2:1.18.3-1ubuntu2.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1619307/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1618522] Re: netplan does not generates .network files just for ethernet
One way to improve that in userspace would be to at least allow a way to match on "no devtype" in networkd. You cannot currently say Type="" or similar. Lennart Poettering> hmm, for networkctl we patch that to make this more useful to look at Lennart Poettering> shouldn'we just do the same in networkd Lennart Poettering> i.e. accept our fate? Lennart Poettering> i am pretty sure "networkctl" should show in the Type column precisely the types you can [Match] on, no? Tom Gundersen> yeah, i guess we can just do that ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu) Importance: Undecided => Low ** Changed in: systemd (Ubuntu) Status: New => Triaged -- 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/1618522 Title: netplan does not generates .network files just for ethernet Status in nplan package in Ubuntu: Triaged Status in systemd package in Ubuntu: Triaged Bug description: On my pi3 I have an image with the ubuntu-core snap rev 354 and I get the following netplan configuration file after the first boot: ubuntu@localhost:~$ cat /etc/netplan/00-initial-config.yaml network: version: 2 ethernets: all: match: name: "*" dhcp4: true This generates the following .networkd file ubuntu@localhost:~$ cat /run/systemd/network/10-netplan-all.network [Match] Name=* [Network] DHCP=ipv4 If I look now at the output of networkctl I see it also tries to manage my mlan0 device which is a WiFi one and should be managed according to the netplan rule: ubuntu@localhost:~$ networkctl IDX LINK TYPE OPERATIONAL SETUP 1 lo loopback carrier configured 5 eth1 ether no-carrier configuring 6 eth0 ether routableconfigured 7 mlan0wlan no-carrier configuring In summary, the networkd generator inside netplan currently does not limit the generated .network file to tell networkd to only look at ethernet devices but rather tell it to control every device available on the system. Expectation: Specifying a wildcard rule in a netplan configuration file for ethernet devices should tell the configured networking system to only consider ethernet devices and nothing else. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1618522/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1522598] Re: nano crashes when resizing terminal
The problem has finally been fixed in nano-2.7.0. Thanks for reporting, and for your patience. ** Changed in: nano (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nano in Ubuntu. https://bugs.launchpad.net/bugs/1522598 Title: nano crashes when resizing terminal Status in nano package in Ubuntu: Fix Committed Bug description: See video here: https://vid.me/5ksi Whenever I resize the terminal that nano is running in to a very small size, it will crash. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nano 2.2.6-1ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-37.42~14.04.1-generic 3.19.8-ckt9 Uname: Linux 3.19.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CurrentDesktop: Unity Date: Thu Dec 3 22:57:39 2015 InstallationDate: Installed on 2015-11-09 (24 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: nano UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1522598/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1619307] Re: Switching to USB sound device stops USB mouse clicks from registering Edit
** Description changed: - As soon as I plugin the Jabra EVOLVE Headset the mouse pointer is - somehow "captured" by the last active window. I can switch windows via - alt-tab but left clicks in the new window still won't work, they will - only work in the "old" window. + As soon as I plugin the JABRA Evolve 80 UC Duo USB headset the mouse + pointer is somehow "captured" by the last active window. I can switch + windows via alt-tab but left clicks in the new window still won't work, + they will only work in the "old" window. WORKAROUND: Add 50-jabra.conf file in /usr/share/X11/xorg.conf.d with the following: Section "InputClass" - Identifier "Jabra" - MatchProduct "GN Netcom A/S Jabra EVOLVE LINK MS" - Option "ButtonMapping" "0 0 0 0 0 0 0 0 0 0 0 0" + Identifier "Jabra" + MatchProduct "GN Netcom A/S Jabra EVOLVE LINK MS" + Option "ButtonMapping" "0 0 0 0 0 0 0 0 0 0 0 0" EndSection and restart xorg-server. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Thu Sep 1 14:47:55 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: kubuntu DkmsStatus: virtualbox, 5.0.24, 4.4.0-34-generic, x86_64: installed virtualbox, 5.0.24, 4.4.0-36-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:0535] MachineType: Dell Inc. Latitude E6530 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-36-generic.efi.signed root=/dev/mapper/system-root_crypt ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/19/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0JC5MT dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd08/19/2015:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn0JC5MT:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6530 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Thu Sep 1 11:27:32 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 812 vendor LGD xserver.version: 2:1.18.3-1ubuntu2.3 -- 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/1619307 Title: Switching to USB sound device stops USB mouse clicks from registering Edit Status in xorg package in Ubuntu: Incomplete Bug description: As soon as I plugin the JABRA Evolve 80 UC Duo USB headset the mouse pointer is somehow "captured" by the last active window. I can switch windows via alt-tab but left clicks in the new window still won't work, they will only work in the "old" window. WORKAROUND: Add 50-jabra.conf file in /usr/share/X11/xorg.conf.d with the following: Section "InputClass" Identifier "Jabra" MatchProduct "GN Netcom A/S Jabra EVOLVE LINK MS" Option "ButtonMapping" "0 0 0 0 0 0 0 0 0 0 0 0" EndSection and restart xorg-server. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Thu Sep 1 14:47:55 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: kubuntu DkmsStatus: virtualbox, 5.0.24, 4.4.0-34-generic, x86_64: installed virtualbox, 5.0.24, 4.4.0-36-generic,
[Touch-packages] [Bug 1612767] Re: Drop appmenu-qt5 from default installations
Ok the crash goes away indeed with a rebuild, thanks! That should be fine. Can you elaborate a bit how the global menus would be supposed to be working with these patches when running Qt applications under Unity 7 environment? I can actually see that for whatever reason current yakkety doesn't have those working even without landing-034 PPA, so the appmenu- qt5 seems to have become broken regardless right now. New bugs should probably be filed for any next actions, whether in Unity itself or elsewhere. -- 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/1612767 Title: Drop appmenu-qt5 from default installations Status in indicator-appmenu package in Ubuntu: New Status in qtbase-opensource-src package in Ubuntu: New Bug description: Currently we are using appmenu-qt5 as our platform theme on desktop, however it has many disadvantages, which make me want to get rid of it: 1) Its design is a hack: instead of the using normal QPA API for getting the menu, it retrieves the menu bar using QWidget::findChild, and then casts the pointer to QMenu*. The normal methods (which are getting called by Qt) remain empty stubs. 2) It is preventing applications from using GTK+ theme integration, such as dialogs (I reported this as bug 1378935, but there is no easy way to fix that). 3) It is not working with Qt Quick applications (because it expects a QtWidgets window; see also bug 1323853). The standard implementation will work with i.e. Qt Quick Controls 2 using apps (implemented in https://codereview.qt-project.org/142733). 4) It breaks other environments such as Plasma when installed: see bug 1434516. 5) Finally, it is mostly unmaintained: most patches since 2014 are authored by me, however I see no point continuing to develop that code. Recently, Shawn Rutledge and I have written a native implementation of what appmenu-qt5 provides (global menu and system tray), which is part of Qt. That code uses the normal API, is well maintained, and works better than appmenu-qt5 (or at least not worse). So I propose to drop appmenu-qt5 from default Ubuntu installations, and maybe later from archive too. Unfortunately we use Qt 5.6, and some of the needed patches are only in Qt 5.7, so I would like to backport them to our packaging: https://code.qt.io/cgit/qt/qtbase.git/commit/?id=f199bb9133fe0446 (will be in 5.6.2 / 5.7.0) https://code.qt.io/cgit/qt/qtbase.git/commit/?id=488cf78e44947eff (will be in 5.7.0) https://code.qt.io/cgit/qt/qtbase.git/commit/?id=b6a824d0a3b4fabd (will be in 5.7.0) https://code.qt.io/cgit/qt/qtbase.git/commit/?id=e4d79e1fdeb6b26b (will be in 5.7.0) Timo: if you have no objections, I will commit those patches to the packaging Git. After we do that, I will remove the appmenu-qt5 recommendation from indicator-appmenu (that is the only package referring to it). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-appmenu/+bug/1612767/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1485622] Re: [needs-packaging] Import libzmq5-dev from Debian.
** Changed in: zeromq3 (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zeromq3 in Ubuntu. https://bugs.launchpad.net/bugs/1485622 Title: [needs-packaging] Import libzmq5-dev from Debian. Status in zeromq3 package in Ubuntu: Fix Released Bug description: Per connection permissions are very difficult to do with ZMQ 4.0.4, which is the current state of the libzmq3-dev package. The current stable release for ZMQ is 4.1.3, which includes the zmq_msg_gets function which exposes the individual authentication information. The 4.1 release has been packaged as libzmq5-dev in the Debian unstable release (https://packages.debian.org/experimental/libzmq5-dev) and it would be highly useful if it could be made available in Ubuntu. Thanks, Charlie West To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeromq3/+bug/1485622/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1618390] Re: dbus-cpp crash on arm64 in core::dbus::Object::get_property
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: dbus-cpp (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mtp in Ubuntu. https://bugs.launchpad.net/bugs/1618390 Title: dbus-cpp crash on arm64 in core::dbus::Object::get_property Status in Canonical System Image: Confirmed Status in dbus-cpp package in Ubuntu: Confirmed Status in location-service package in Ubuntu: Confirmed Status in mtp package in Ubuntu: Confirmed Bug description: Requests to location service cause crashes on arm64: $ system-image-cli -i current build number: 23 device name: frieza_arm64 channel: ubuntu-touch/staging/ubuntu last update: 2016-08-30 09:13:12 version version: 23 version ubuntu: 20160830 version device: 20160824.0 version custom: 20160830 Steps: * flash the above channel (remember --device frieza_arm64) * go to a scope using location * refresh == Stacktrace = #0 0x007f978d4328 in std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_release() (__val=-1, __mem=0x29) at /usr/include/c++/5/ext/atomicity.h:49 __val = -1 __mem = 0x29 #1 0x007f978d4328 in std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_release() (__val=-1, __mem=0x29) at /usr/include/c++/5/ext/atomicity.h:82 __val = -1 __mem = 0x29 #2 0x007f978d4328 in std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_release() (this=0x21) at /usr/include/c++/5/bits/shared_ptr_base.h:147 #3 0x007f97922a28 in std::__shared_count<(__gnu_cxx::_Lock_policy)2>::operator=(std::__shared_count<(__gnu_cxx::_Lock_policy)2> const&) (this=this@entry=0x8b34558, __r=...) at /usr/include/c++/5/bits/shared_ptr_base.h:678 __tmp = 0x8b34ba0 #4 0x007f9792cc64 in core::dbus::Object::get_property() (this=0x8b34550) at /usr/include/c++/5/bits/shared_ptr_base.h:867 property = #5 0x007f9792cc64 in core::dbus::Object::get_property() (this=0x8b34550) at /usr/include/c++/5/bits/shared_ptr.h:93 property = #6 0x007f9792cc64 in core::dbus::Object::get_property() (this=0x8b342c0) at /usr/include/core/dbus/impl/object.h:162 property = #7 0x007f97931c08 in com::ubuntu::location::service::Stub::Stub(std::shared_ptr const&) (object=warning: can't find linker symbol for virtual table for `std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>' value warning: can't find linker symbol for virtual table for `std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>' value ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libubuntu-location-service3 3.0.0+16.04.20160811-0ubuntu1 [origin: LP-PPA-ci-train-ppa-service-stable-phone-overlay] Uname: Linux 3.10.93+ aarch64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: arm64 Date: Tue Aug 30 09:39:24 2016 SourcePackage: location-service UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: arm64 DistroRelease: Ubuntu 16.04 Package: mtp-server 0.0.4+16.04.20160413-0ubuntu2 [origin: LP-PPA-ci-train-ppa-service-stable-phone-overlay] PackageArchitecture: arm64 Tags: third-party-packages xenial Uname: Linux 3.10.93+ aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip plugdev sudo tty video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1618390/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1618390] Re: dbus-cpp crash on arm64 in core::dbus::Object::get_property
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: location-service (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mtp in Ubuntu. https://bugs.launchpad.net/bugs/1618390 Title: dbus-cpp crash on arm64 in core::dbus::Object::get_property Status in Canonical System Image: Confirmed Status in dbus-cpp package in Ubuntu: Confirmed Status in location-service package in Ubuntu: Confirmed Status in mtp package in Ubuntu: Confirmed Bug description: Requests to location service cause crashes on arm64: $ system-image-cli -i current build number: 23 device name: frieza_arm64 channel: ubuntu-touch/staging/ubuntu last update: 2016-08-30 09:13:12 version version: 23 version ubuntu: 20160830 version device: 20160824.0 version custom: 20160830 Steps: * flash the above channel (remember --device frieza_arm64) * go to a scope using location * refresh == Stacktrace = #0 0x007f978d4328 in std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_release() (__val=-1, __mem=0x29) at /usr/include/c++/5/ext/atomicity.h:49 __val = -1 __mem = 0x29 #1 0x007f978d4328 in std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_release() (__val=-1, __mem=0x29) at /usr/include/c++/5/ext/atomicity.h:82 __val = -1 __mem = 0x29 #2 0x007f978d4328 in std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_release() (this=0x21) at /usr/include/c++/5/bits/shared_ptr_base.h:147 #3 0x007f97922a28 in std::__shared_count<(__gnu_cxx::_Lock_policy)2>::operator=(std::__shared_count<(__gnu_cxx::_Lock_policy)2> const&) (this=this@entry=0x8b34558, __r=...) at /usr/include/c++/5/bits/shared_ptr_base.h:678 __tmp = 0x8b34ba0 #4 0x007f9792cc64 in core::dbus::Object::get_property() (this=0x8b34550) at /usr/include/c++/5/bits/shared_ptr_base.h:867 property = #5 0x007f9792cc64 in core::dbus::Object::get_property() (this=0x8b34550) at /usr/include/c++/5/bits/shared_ptr.h:93 property = #6 0x007f9792cc64 in core::dbus::Object::get_property() (this=0x8b342c0) at /usr/include/core/dbus/impl/object.h:162 property = #7 0x007f97931c08 in com::ubuntu::location::service::Stub::Stub(std::shared_ptr const&) (object=warning: can't find linker symbol for virtual table for `std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>' value warning: can't find linker symbol for virtual table for `std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>' value ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libubuntu-location-service3 3.0.0+16.04.20160811-0ubuntu1 [origin: LP-PPA-ci-train-ppa-service-stable-phone-overlay] Uname: Linux 3.10.93+ aarch64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: arm64 Date: Tue Aug 30 09:39:24 2016 SourcePackage: location-service UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: arm64 DistroRelease: Ubuntu 16.04 Package: mtp-server 0.0.4+16.04.20160413-0ubuntu2 [origin: LP-PPA-ci-train-ppa-service-stable-phone-overlay] PackageArchitecture: arm64 Tags: third-party-packages xenial Uname: Linux 3.10.93+ aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip plugdev sudo tty video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1618390/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1618390] Re: dbus-cpp crash on arm64 in core::dbus::Object::get_property
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mtp (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mtp in Ubuntu. https://bugs.launchpad.net/bugs/1618390 Title: dbus-cpp crash on arm64 in core::dbus::Object::get_property Status in Canonical System Image: Confirmed Status in dbus-cpp package in Ubuntu: Confirmed Status in location-service package in Ubuntu: Confirmed Status in mtp package in Ubuntu: Confirmed Bug description: Requests to location service cause crashes on arm64: $ system-image-cli -i current build number: 23 device name: frieza_arm64 channel: ubuntu-touch/staging/ubuntu last update: 2016-08-30 09:13:12 version version: 23 version ubuntu: 20160830 version device: 20160824.0 version custom: 20160830 Steps: * flash the above channel (remember --device frieza_arm64) * go to a scope using location * refresh == Stacktrace = #0 0x007f978d4328 in std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_release() (__val=-1, __mem=0x29) at /usr/include/c++/5/ext/atomicity.h:49 __val = -1 __mem = 0x29 #1 0x007f978d4328 in std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_release() (__val=-1, __mem=0x29) at /usr/include/c++/5/ext/atomicity.h:82 __val = -1 __mem = 0x29 #2 0x007f978d4328 in std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_release() (this=0x21) at /usr/include/c++/5/bits/shared_ptr_base.h:147 #3 0x007f97922a28 in std::__shared_count<(__gnu_cxx::_Lock_policy)2>::operator=(std::__shared_count<(__gnu_cxx::_Lock_policy)2> const&) (this=this@entry=0x8b34558, __r=...) at /usr/include/c++/5/bits/shared_ptr_base.h:678 __tmp = 0x8b34ba0 #4 0x007f9792cc64 in core::dbus::Object::get_property() (this=0x8b34550) at /usr/include/c++/5/bits/shared_ptr_base.h:867 property = #5 0x007f9792cc64 in core::dbus::Object::get_property() (this=0x8b34550) at /usr/include/c++/5/bits/shared_ptr.h:93 property = #6 0x007f9792cc64 in core::dbus::Object::get_property() (this=0x8b342c0) at /usr/include/core/dbus/impl/object.h:162 property = #7 0x007f97931c08 in com::ubuntu::location::service::Stub::Stub(std::shared_ptr const&) (object=warning: can't find linker symbol for virtual table for `std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>' value warning: can't find linker symbol for virtual table for `std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>' value ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libubuntu-location-service3 3.0.0+16.04.20160811-0ubuntu1 [origin: LP-PPA-ci-train-ppa-service-stable-phone-overlay] Uname: Linux 3.10.93+ aarch64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: arm64 Date: Tue Aug 30 09:39:24 2016 SourcePackage: location-service UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: arm64 DistroRelease: Ubuntu 16.04 Package: mtp-server 0.0.4+16.04.20160413-0ubuntu2 [origin: LP-PPA-ci-train-ppa-service-stable-phone-overlay] PackageArchitecture: arm64 Tags: third-party-packages xenial Uname: Linux 3.10.93+ aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip plugdev sudo tty video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1618390/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1618390] Re: dbus-cpp crash on arm64 in core::dbus::Object::get_property
** Changed in: canonical-devices-system-image Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mtp in Ubuntu. https://bugs.launchpad.net/bugs/1618390 Title: dbus-cpp crash on arm64 in core::dbus::Object::get_property Status in Canonical System Image: Confirmed Status in dbus-cpp package in Ubuntu: Confirmed Status in location-service package in Ubuntu: Confirmed Status in mtp package in Ubuntu: Confirmed Bug description: Requests to location service cause crashes on arm64: $ system-image-cli -i current build number: 23 device name: frieza_arm64 channel: ubuntu-touch/staging/ubuntu last update: 2016-08-30 09:13:12 version version: 23 version ubuntu: 20160830 version device: 20160824.0 version custom: 20160830 Steps: * flash the above channel (remember --device frieza_arm64) * go to a scope using location * refresh == Stacktrace = #0 0x007f978d4328 in std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_release() (__val=-1, __mem=0x29) at /usr/include/c++/5/ext/atomicity.h:49 __val = -1 __mem = 0x29 #1 0x007f978d4328 in std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_release() (__val=-1, __mem=0x29) at /usr/include/c++/5/ext/atomicity.h:82 __val = -1 __mem = 0x29 #2 0x007f978d4328 in std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_release() (this=0x21) at /usr/include/c++/5/bits/shared_ptr_base.h:147 #3 0x007f97922a28 in std::__shared_count<(__gnu_cxx::_Lock_policy)2>::operator=(std::__shared_count<(__gnu_cxx::_Lock_policy)2> const&) (this=this@entry=0x8b34558, __r=...) at /usr/include/c++/5/bits/shared_ptr_base.h:678 __tmp = 0x8b34ba0 #4 0x007f9792cc64 in core::dbus::Object::get_property() (this=0x8b34550) at /usr/include/c++/5/bits/shared_ptr_base.h:867 property = #5 0x007f9792cc64 in core::dbus::Object::get_property() (this=0x8b34550) at /usr/include/c++/5/bits/shared_ptr.h:93 property = #6 0x007f9792cc64 in core::dbus::Object::get_property() (this=0x8b342c0) at /usr/include/core/dbus/impl/object.h:162 property = #7 0x007f97931c08 in com::ubuntu::location::service::Stub::Stub(std::shared_ptr const&) (object=warning: can't find linker symbol for virtual table for `std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>' value warning: can't find linker symbol for virtual table for `std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>' value ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libubuntu-location-service3 3.0.0+16.04.20160811-0ubuntu1 [origin: LP-PPA-ci-train-ppa-service-stable-phone-overlay] Uname: Linux 3.10.93+ aarch64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: arm64 Date: Tue Aug 30 09:39:24 2016 SourcePackage: location-service UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: arm64 DistroRelease: Ubuntu 16.04 Package: mtp-server 0.0.4+16.04.20160413-0ubuntu2 [origin: LP-PPA-ci-train-ppa-service-stable-phone-overlay] PackageArchitecture: arm64 Tags: third-party-packages xenial Uname: Linux 3.10.93+ aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip plugdev sudo tty video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1618390/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1263317] Re: Not working on GTK 3 undecorated windows
Also, as for Ubuntu 16.04, there are more applications migrated to borderless windows, all of them can't be resized in session types other than Unity. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1263317 Title: Not working on GTK 3 undecorated windows Status in Ubuntu theme: Confirmed Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: Gnome-shell 3.10.2 Fedora 20 There appears to be no window decorations for any gtk3 windows. Nautilus, gnome control panel, gnome tweak tools etc There are no resize handles, shadows, borders, rounded corners etc This afftects Gnome-Shell 3.10 to 3.11, on both Fedora 19,&20 and Ubuntu 13.10 up I've tested the Ambiance and Radiance themes and both these aren't playing nicely. I hope this is still being maintained becuase this is my favourite gtk theme :P To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1263317/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1263317] Re: Not working on GTK 3 undecorated windows
Applies to gnome-fallback / gnome-flashback sessions as well. The themes only to be useable on Unity. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1263317 Title: Not working on GTK 3 undecorated windows Status in Ubuntu theme: Confirmed Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: Gnome-shell 3.10.2 Fedora 20 There appears to be no window decorations for any gtk3 windows. Nautilus, gnome control panel, gnome tweak tools etc There are no resize handles, shadows, borders, rounded corners etc This afftects Gnome-Shell 3.10 to 3.11, on both Fedora 19,&20 and Ubuntu 13.10 up I've tested the Ambiance and Radiance themes and both these aren't playing nicely. I hope this is still being maintained becuase this is my favourite gtk theme :P To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1263317/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1619307] Re: Switching to USB sound device stops USB mouse clicks from registering Edit
** Description changed: - As soon as I plugin the JABRA Evolve 80 UC Duo USB headset the mouse - pointer is somehow "captured" by the last active window. I can switch - windows via alt-tab but left clicks in the new window still won't work, - they will only work in the "old" window. + I have a JABRA Evolve 80 headset with the 3.5mm plugged into the JABRA + Evolve 80 Link UC. Once I plug the JABRA Evolve Link UC USB into my + computer, the mouse pointer is somehow "captured" by the last active + window. I can switch windows via alt-tab but left clicks in the new + window still won't work, they will only work in the "old" window. WORKAROUND: Add 50-jabra.conf file in /usr/share/X11/xorg.conf.d with the following: Section "InputClass" Identifier "Jabra" MatchProduct "GN Netcom A/S Jabra EVOLVE LINK MS" Option "ButtonMapping" "0 0 0 0 0 0 0 0 0 0 0 0" EndSection and restart xorg-server. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Thu Sep 1 14:47:55 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: kubuntu DkmsStatus: virtualbox, 5.0.24, 4.4.0-34-generic, x86_64: installed virtualbox, 5.0.24, 4.4.0-36-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:0535] MachineType: Dell Inc. Latitude E6530 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-36-generic.efi.signed root=/dev/mapper/system-root_crypt ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/19/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0JC5MT dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd08/19/2015:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn0JC5MT:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6530 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Thu Sep 1 11:27:32 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 812 vendor LGD xserver.version: 2:1.18.3-1ubuntu2.3 -- 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/1619307 Title: Switching to USB sound device stops USB mouse clicks from registering Edit Status in xorg package in Ubuntu: Incomplete Bug description: I have a JABRA Evolve 80 headset with the 3.5mm plugged into the JABRA Evolve 80 Link UC. Once I plug the JABRA Evolve Link UC USB into my computer, the mouse pointer is somehow "captured" by the last active window. I can switch windows via alt-tab but left clicks in the new window still won't work, they will only work in the "old" window. WORKAROUND: Add 50-jabra.conf file in /usr/share/X11/xorg.conf.d with the following: Section "InputClass" Identifier "Jabra" MatchProduct "GN Netcom A/S Jabra EVOLVE LINK MS" Option "ButtonMapping" "0 0 0 0 0 0 0 0 0 0 0 0" EndSection and restart xorg-server. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Thu Sep 1 14:47:55 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: kubuntu DkmsStatus: virtualbox, 5.0.24, 4.4.0-34-generic, x86_
[Touch-packages] [Bug 1619307] Re: Switching to USB sound device stops USB mouse clicks from registering Edit
** Changed in: xorg (Ubuntu) Status: Incomplete => Triaged -- 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/1619307 Title: Switching to USB sound device stops USB mouse clicks from registering Edit Status in xorg package in Ubuntu: Triaged Bug description: I have a JABRA Evolve 80 headset with the 3.5mm plugged into the JABRA Evolve 80 Link UC. Once I plug the JABRA Evolve Link UC USB into my computer, the mouse pointer is somehow "captured" by the last active window. I can switch windows via alt-tab but left clicks in the new window still won't work, they will only work in the "old" window. WORKAROUND: Add 50-jabra.conf file in /usr/share/X11/xorg.conf.d with the following: Section "InputClass" Identifier "Jabra" MatchProduct "GN Netcom A/S Jabra EVOLVE LINK MS" Option "ButtonMapping" "0 0 0 0 0 0 0 0 0 0 0 0" EndSection and restart xorg-server. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Thu Sep 1 14:47:55 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: kubuntu DkmsStatus: virtualbox, 5.0.24, 4.4.0-34-generic, x86_64: installed virtualbox, 5.0.24, 4.4.0-36-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:0535] MachineType: Dell Inc. Latitude E6530 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-36-generic.efi.signed root=/dev/mapper/system-root_crypt ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/19/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0JC5MT dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd08/19/2015:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn0JC5MT:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6530 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Thu Sep 1 11:27:32 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 812 vendor LGD xserver.version: 2:1.18.3-1ubuntu2.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1619307/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1603914] Re: apps switcher, closing an app exits the spread
** Changed in: unity8 (Ubuntu) Assignee: (unassigned) => Michael Zanetti (mzanetti) ** Changed in: unity8 (Ubuntu) Status: New => In Progress ** Branch linked: lp:~mzanetti/unity8/unified-stages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1603914 Title: apps switcher, closing an app exits the spread Status in Ubuntu UX: New Status in unity8 package in Ubuntu: In Progress Bug description: ubuntu 16.10 unity8 / desktop apps switcher, closing an app exits the spread. launch a bunch of apps, ALT TAB and then close with the mouse by clicking the [x] one random app. the spread closes. it makes super hard closing multiple apps since you have to ALT TAB again, every time you close an app. expected.. it used to work :D the spread stayed opened and had a nice animation <3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1603914/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1489020] Re: [window management] unity8 and 3 finger window drag
** Changed in: ubuntu-ux Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1489020 Title: [window management] unity8 and 3 finger window drag Status in Ubuntu UX: Fix Released Status in unity8 package in Ubuntu: Fix Released Bug description: it's been pointed out with the recent bug 1438465 on windowed mode unity8, that could be solved or addressed by the feature that exists in unity7 which is using a 3 finger touch to target and drag around windows (w.o touching the title bar) side note: we may do something shorter term about bug 1438465 just want some confirmation, will we still want this 3 finger touch in unity8 ? --Desired design- Unity8 should have 3 finger touch gestures enabled. 3 finger tap on application window should show touch size targets for moving, resizing, closing, maximising/restoring and minimising. Window can also be moved around with 3 finger drag. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1489020/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1489517] Re: can't quit apps with touch in right-edge-spread when in windowed mode
** Changed in: unity8 (Ubuntu) Status: New => In Progress ** Branch linked: lp:~mzanetti/unity8/unified-stages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1489517 Title: can't quit apps with touch in right-edge-spread when in windowed mode Status in Ubuntu UX: Fix Committed Status in unity8 package in Ubuntu: In Progress Bug description: vivid+o + silo0, easier on n7 steps 1. launch a few apps 2. connect to monitor, putting unity8 into window mode 3. right edge swipe to open spread 4. attempt to close by touching little red x out button on top left corner of app in spread expected: it would close result: it just selects seems to be just a diff between touch and cursor that might have been a design decision? or maybe just a bug? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1489517/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1506708] Re: Dash reset when pulling out launcher is too eager
When testing I think the fix is that the trigger doesn't happen immediately after launcher width is exceeded with left edge gesture but the trigger point is further right. Which already improves the situation and reduces false positives. The trigger still happens without releasing which is fine at this point considering that we're currently designing on something else for the long right edge swipe anyway. So I marked this as fix released. ** Changed in: ubuntu-ux Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1506708 Title: Dash reset when pulling out launcher is too eager Status in Ubuntu UX: Fix Released Status in unity8 package in Ubuntu: Fix Released Bug description: 1) Go the app store, look at an app page, maybe start writing a review 2) Pull out the launcher If you are even a little enthusiastic with your pull, the dash resets, and you lose your place. I do it by accident often, and it's annoying. I think it would be reasonable to wait till the drag goes more than a launcher's width past the launcher or something similar. Desired design- Don't go home scope (left most) yet when gesture has passed the launcher width. Follow the same logic here as when performing left edge gesture when some other app than Dash is focused. I don't think there is exact spec or parameters anywhere but basic rules are: - Only trigger switch on finger release (the home scope can and should already be revealed during the gesture) - To go to home scope certain horizontal threshold value needs to be exceeded and gesture direction on release needs to be from left to right. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1506708/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1260768] Re: Fix the ApplyUpdate() D-Bus API
** Changed in: ubuntu-system-settings (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to system-image in Ubuntu. https://bugs.launchpad.net/bugs/1260768 Title: Fix the ApplyUpdate() D-Bus API Status in Ubuntu system image: Fix Released Status in system-image package in Ubuntu: Fix Released Status in ubuntu-system-settings package in Ubuntu: Fix Committed Bug description: Bug #1260712 reports the problem where the D-Bus API for ApplyUpdate() was changed but system-settings wasn't prepared to handle the change. During post-mortem discussions, Didier requested that the Rebooting() signal sent by ApplyUpdate() be changed to return an error message string instead of a boolean, with the empty string meaning no error. This bug tracks that request. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-system-image/+bug/1260768/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1318360] Re: Poor microphone quality (mako)
@K1773R: It does not have to be in the milestone list to land. The package is already part of the overlay ppa and in rc-proposed so it will be automatically land with OTA 13. ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Changed in: pulseaudio (Ubuntu) Status: Confirmed => Fix Committed -- 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/1318360 Title: Poor microphone quality (mako) Status in Canonical System Image: Fix Committed Status in libhybris package in Ubuntu: Fix Committed Status in pulseaudio package in Ubuntu: Invalid Bug description: After months of complaints from people talking to me on the phone (mako ubuntu touch), I finally got around to use multiROM to dual boot Ubuntu Touch and Android. Several people can confirm that there is a noticable difference in terms of sound/microphone quality between Android and UT in phone calls. With UT, my voice gets distorted to an extent that person at the other end have real difficulties to hear what I am saying, while with Android call quality is much better with no distortion. I have had a suspicion for a long time that this might be a software and not a hardware issue. After trying Android and Ubuntu on the same hardware I believe this suspicion is proved correct. This issue has persisted in all the builds I have tried since at least the beginning of the year, but probably longer. I am now at r17 of Utopic. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1318360/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1318360] Re: Poor microphone quality (mako)
** Changed in: canonical-devices-system-image Assignee: (unassigned) => John McAleely (john.mcaleely) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libhybris in Ubuntu. https://bugs.launchpad.net/bugs/1318360 Title: Poor microphone quality (mako) Status in Canonical System Image: Fix Committed Status in libhybris package in Ubuntu: Fix Committed Status in pulseaudio package in Ubuntu: Invalid Bug description: After months of complaints from people talking to me on the phone (mako ubuntu touch), I finally got around to use multiROM to dual boot Ubuntu Touch and Android. Several people can confirm that there is a noticable difference in terms of sound/microphone quality between Android and UT in phone calls. With UT, my voice gets distorted to an extent that person at the other end have real difficulties to hear what I am saying, while with Android call quality is much better with no distortion. I have had a suspicion for a long time that this might be a software and not a hardware issue. After trying Android and Ubuntu on the same hardware I believe this suspicion is proved correct. This issue has persisted in all the builds I have tried since at least the beginning of the year, but probably longer. I am now at r17 of Utopic. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1318360/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1318360] Re: Poor microphone quality (mako)
** Changed in: pulseaudio (Ubuntu) Status: Fix Committed => Invalid ** Also affects: libhybris (Ubuntu) Importance: Undecided Status: New -- 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/1318360 Title: Poor microphone quality (mako) Status in Canonical System Image: Fix Committed Status in libhybris package in Ubuntu: Fix Committed Status in pulseaudio package in Ubuntu: Invalid Bug description: After months of complaints from people talking to me on the phone (mako ubuntu touch), I finally got around to use multiROM to dual boot Ubuntu Touch and Android. Several people can confirm that there is a noticable difference in terms of sound/microphone quality between Android and UT in phone calls. With UT, my voice gets distorted to an extent that person at the other end have real difficulties to hear what I am saying, while with Android call quality is much better with no distortion. I have had a suspicion for a long time that this might be a software and not a hardware issue. After trying Android and Ubuntu on the same hardware I believe this suspicion is proved correct. This issue has persisted in all the builds I have tried since at least the beginning of the year, but probably longer. I am now at r17 of Utopic. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1318360/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1318360] Re: Poor microphone quality (mako)
** Changed in: libhybris (Ubuntu) Assignee: (unassigned) => Simon Fels (morphis) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libhybris in Ubuntu. https://bugs.launchpad.net/bugs/1318360 Title: Poor microphone quality (mako) Status in Canonical System Image: Fix Committed Status in libhybris package in Ubuntu: Fix Committed Status in pulseaudio package in Ubuntu: Invalid Bug description: After months of complaints from people talking to me on the phone (mako ubuntu touch), I finally got around to use multiROM to dual boot Ubuntu Touch and Android. Several people can confirm that there is a noticable difference in terms of sound/microphone quality between Android and UT in phone calls. With UT, my voice gets distorted to an extent that person at the other end have real difficulties to hear what I am saying, while with Android call quality is much better with no distortion. I have had a suspicion for a long time that this might be a software and not a hardware issue. After trying Android and Ubuntu on the same hardware I believe this suspicion is proved correct. This issue has persisted in all the builds I have tried since at least the beginning of the year, but probably longer. I am now at r17 of Utopic. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1318360/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1318360] Re: Poor microphone quality (mako)
** Changed in: libhybris (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libhybris in Ubuntu. https://bugs.launchpad.net/bugs/1318360 Title: Poor microphone quality (mako) Status in Canonical System Image: Fix Committed Status in libhybris package in Ubuntu: Fix Committed Status in pulseaudio package in Ubuntu: Invalid Bug description: After months of complaints from people talking to me on the phone (mako ubuntu touch), I finally got around to use multiROM to dual boot Ubuntu Touch and Android. Several people can confirm that there is a noticable difference in terms of sound/microphone quality between Android and UT in phone calls. With UT, my voice gets distorted to an extent that person at the other end have real difficulties to hear what I am saying, while with Android call quality is much better with no distortion. I have had a suspicion for a long time that this might be a software and not a hardware issue. After trying Android and Ubuntu on the same hardware I believe this suspicion is proved correct. This issue has persisted in all the builds I have tried since at least the beginning of the year, but probably longer. I am now at r17 of Utopic. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1318360/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1318360] Re: Poor microphone quality (mako)
** Changed in: libhybris (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libhybris in Ubuntu. https://bugs.launchpad.net/bugs/1318360 Title: Poor microphone quality (mako) Status in Canonical System Image: Fix Committed Status in libhybris package in Ubuntu: Fix Committed Status in pulseaudio package in Ubuntu: Invalid Bug description: After months of complaints from people talking to me on the phone (mako ubuntu touch), I finally got around to use multiROM to dual boot Ubuntu Touch and Android. Several people can confirm that there is a noticable difference in terms of sound/microphone quality between Android and UT in phone calls. With UT, my voice gets distorted to an extent that person at the other end have real difficulties to hear what I am saying, while with Android call quality is much better with no distortion. I have had a suspicion for a long time that this might be a software and not a hardware issue. After trying Android and Ubuntu on the same hardware I believe this suspicion is proved correct. This issue has persisted in all the builds I have tried since at least the beginning of the year, but probably longer. I am now at r17 of Utopic. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1318360/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1318360] Re: Poor microphone quality (mako)
** Changed in: canonical-devices-system-image Status: New => Fix Committed ** Changed in: canonical-devices-system-image Milestone: None => 13 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libhybris in Ubuntu. https://bugs.launchpad.net/bugs/1318360 Title: Poor microphone quality (mako) Status in Canonical System Image: Fix Committed Status in libhybris package in Ubuntu: Fix Committed Status in pulseaudio package in Ubuntu: Invalid Bug description: After months of complaints from people talking to me on the phone (mako ubuntu touch), I finally got around to use multiROM to dual boot Ubuntu Touch and Android. Several people can confirm that there is a noticable difference in terms of sound/microphone quality between Android and UT in phone calls. With UT, my voice gets distorted to an extent that person at the other end have real difficulties to hear what I am saying, while with Android call quality is much better with no distortion. I have had a suspicion for a long time that this might be a software and not a hardware issue. After trying Android and Ubuntu on the same hardware I believe this suspicion is proved correct. This issue has persisted in all the builds I have tried since at least the beginning of the year, but probably longer. I am now at r17 of Utopic. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1318360/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1318360] Re: Poor microphone quality (mako)
** Changed in: canonical-devices-system-image Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libhybris in Ubuntu. https://bugs.launchpad.net/bugs/1318360 Title: Poor microphone quality (mako) Status in Canonical System Image: Fix Committed Status in libhybris package in Ubuntu: Fix Committed Status in pulseaudio package in Ubuntu: Invalid Bug description: After months of complaints from people talking to me on the phone (mako ubuntu touch), I finally got around to use multiROM to dual boot Ubuntu Touch and Android. Several people can confirm that there is a noticable difference in terms of sound/microphone quality between Android and UT in phone calls. With UT, my voice gets distorted to an extent that person at the other end have real difficulties to hear what I am saying, while with Android call quality is much better with no distortion. I have had a suspicion for a long time that this might be a software and not a hardware issue. After trying Android and Ubuntu on the same hardware I believe this suspicion is proved correct. This issue has persisted in all the builds I have tried since at least the beginning of the year, but probably longer. I am now at r17 of Utopic. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1318360/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1609520] [NEW] Cannot login after logout
You have been subscribed to a public bug: If I logout and login again it doesn't work and brings me back to the login screen (lightdm). This is only the case if I use the nvidia graphics card of my laptop (via prime-select), using the intel card, I can logout and login again. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nvidia-361 361.42-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Wed Aug 3 19:14:59 2016 InstallationDate: Installed on 2016-05-18 (76 days ago) InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. SourcePackage: nvidia-graphics-drivers-361 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xorg (Ubuntu) Importance: Low Status: Incomplete ** Tags: amd64 apport-bug xenial -- Cannot login after logout https://bugs.launchpad.net/bugs/1609520 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1612406] [NEW] numlock turn off alone
You have been subscribed to a public bug: Hello; Im using Ubuntu 16.04.1 - 64bits, but this bug follow me from Ubuntu 14.04 No aparecente reason, the numeric keypad buttons are off. To work again, i have to press the 'numlock' twice, turn off and on again. This occurs many times during use of the machine. No matter what application or task I'm doing, it happens repeatedly. Hardware details: Caminho do hardware Dispositivo Classe Descrição system 670Z5E (SAMSUNG SENS Series) /0busNP670Z5E-XD1BR /0/0 memory 64KiB BIOS /0/34 memory 512KiB L2 cache /0/35 memory 128KiB L1 cache /0/36 memory 3MiB L3 cache /0/37 memory 8GiB Memória do sistema /0/37/0 memory DIMMProject-Id-Version: lshwReport-Msgid-Bugs-To: FULL NAME POT-Creation-Date: 2009-10-08 14:02+0200PO-Revision-Date: 2013-04-07 17:30+Last-Translator: Neliton Pereira Jr. Language-Team: Brazilian Portuguese MIME-Version: 1.0Content-Type: text/plain; charset=UTF-8Content-Transfer-Encoding: 8bitX-Launchpad-Export-Date: 2016-06-27 17:08+X-Generator: Launchpad (build 18115) [vazio] /0/37/1 memory DIMMProject-Id-Version: lshwReport-Msgid-Bugs-To: FULL NAME POT-Creation-Date: 2009-10-08 14:02+0200PO-Revision-Date: 2013-04-07 17:30+Last-Translator: Neliton Pereira Jr. Language-Team: Brazilian Portuguese MIME-Version: 1.0Content-Type: text/plain; charset=UTF-8Content-Transfer-Encoding: 8bitX-Launchpad-Export-Date: 2016-06-27 17:08+X-Generator: Launchpad (build 18115) [vazio] /0/37/2 memory 8GiB SODIMM DDR3 Síncrono 1600 MHz (0,6 ns) /0/37/3 memory DIMMProject-Id-Version: lshwReport-Msgid-Bugs-To: FULL NAME POT-Creation-Date: 2009-10-08 14:02+0200PO-Revision-Date: 2013-04-07 17:30+Last-Translator: Neliton Pereira Jr. Language-Team: Brazilian Portuguese MIME-Version: 1.0Content-Type: text/plain; charset=UTF-8Content-Transfer-Encoding: 8bitX-Launchpad-Export-Date: 2016-06-27 17:08+X-Generator: Launchpad (build 18115) [vazio] /0/38 processor Intel(R) Core(TM) i5-3230M CPU @ 2.60GHz /0/100bridge 3rd Gen Core processor DRAM Controller /0/100/1 bridge Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port /0/100/1/0genericIllegal Vendor ID /0/100/2 display3rd Gen Core processor Graphics Controller /0/100/14 bus7 Series/C210 Series Chipset Family USB xHCI Host Controller /0/100/14/0 usb4 busxHCI Host Controller /0/100/14/1 usb3 busxHCI Host Controller /0/100/14/1/3 genericUSB2.0-CRW /0/100/16 communication 7 Series/C210 Series Chipset Family MEI Controller #1 /0/100/1a bus7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 /0/100/1a/1 usb1 busEHCI Host Controller /0/100/1a/1/1 busIntegrated Rate Matching Hub /0/100/1a/1/1/2 input 2.4G Keyboard Mouse /0/100/1a/1/1/4 multimedia WebCam SC-10HDP12631N /0/100/1b multimedia 7 Series/C210 Series Chipset Family High Definition Audio Controller /0/100/1c bridge 7 Series/C210 Series Chipset Family PCI Express Root Port 1 /0/100/1c/0 wlp2s0 networkCentrino Advanced-N 6235 /0/100/1c.3 bridge 7 Series/C210 Series Chipset Family PCI Express Root Port 4 /0/100/1c.3/0enp3s0 networkRTL8111/8168/8411 PCI Express Gigabit Ethernet Controller /0/100/1d bus7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 /0/100/1d/1 usb2 busEHCI Host Controller /0/100/1d/1/1 busIntegrated Rate Matching Hub /0/100/1d/1/1/5 communication Interface sem fio bluetooth /0/100/1f bridge HM76 Express Chipset LPC Controller /0/100/1f.2 storage7 Series Chipset Family 6-port SATA Controller [AHCI mode] /0/100/1f.3 bus7 Series/C210 Series Chipset Family SMBus Controller /0/1 scsi0storage /0/1/0.0.0 /dev/sda disk 1TB ST1000LM024 HN-M /0/1/0.0.0/1
[Touch-packages] [Bug 1618540] Re: Big delay opening apps from launcher
** Summary changed: - Delay of 1 second to open an app after clicking on the launcher + Big delay opening apps from launcher ** Changed in: canonical-devices-system-image Status: New => Triaged ** Changed in: canonical-devices-system-image Importance: Undecided => Critical ** Changed in: canonical-devices-system-image Assignee: (unassigned) => Michał Sawicz (saviq) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1618540 Title: Big delay opening apps from launcher Status in Canonical System Image: Triaged Status in unity8 package in Ubuntu: Confirmed Bug description: Hi, it's been a week or so that I noticed that apps no longer open instantly once you click on them in the Unity launcher; it takes around one second to see it open and start loading. This didn't happen before, and gives the user a weird feeling of "maybe I didn't tap well on the icon". I'm on rc-proposed, BQ E4.5 Thanks :) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1618540/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1570459] Re: Opening Updates page leads to System Settings crash
System Setting now use the more limited UDM QML API, so it's uncertain if you can trigger this from USS anymore. Marking UDM as affected, and USS as incomplete, as we'll have to try to reproduce it (I haven't been able yet). ** Also affects: ubuntu-download-manager (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-system-settings (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-download-manager in Ubuntu. https://bugs.launchpad.net/bugs/1570459 Title: Opening Updates page leads to System Settings crash Status in ubuntu-download-manager package in Ubuntu: New Status in ubuntu-system-settings package in Ubuntu: Incomplete Bug description: Krillin, rc-proposed, r308 I opened Updates page to update the OS. I had app updates available (UI Toolkit gallery, uNav, and one more), I tapped on "Update", the app downloaded the UITK Gallery update but then got stuck at "Installing..." After a while it was still "Installing" and the Pause/Resume buttons for the other apps were not working, so I closed the system settings app and launched it again. I believe what happened is that the phone ran out of free space while it was installing the app, and that triggered the bug. Trying to open the Updates page now leads to an app crash. System settings log: http://pastebin.ubuntu.com/15832733/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-download-manager/+bug/1570459/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1617583] [NEW] Ubuntu 16.04 system freeze xorg libglx.so
You have been subscribed to a public bug: System freezes after random time, sometimes after hours, sometimes not. When freeze, need to switch off power. No freezes any more after removing /usr/lib/xorg/modules/extensions/libglx.so. I dind't find anything in system logs. System was upgraded from 14.04 LTS to 16.04 TLS. With 14.04 no freezes. Other linux running well (double boot). Tried a few things before finding cause, e. g. disabling swap, changed from KDE to LXDE, I also tried kernels 4.6.0 and 4.6.5. System info: Ubuntu 16.04.1 LTS (prio installed as Kubuntu 14.04) xserver-xorg-core: Installed: 2:1.18.3-1ubuntu2.3 $ sudo lshw -numeric -C display *-display description: VGA compatible controller product: Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:F31] vendor: Intel Corporation [8086] physical id: 2 bus info: pci@:00:02.0 version: 0e width: 32 bits clock: 33MHz capabilities: pm msi vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:91 memory:d000-d03f memory:c000-cfff ioport:f080(size=8) What information should I provide? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg-core 2:1.18.3-1ubuntu2.3 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: LXDE Date: Sat Aug 27 16:13:39 2016 InstallationDate: Installed on 2015-01-15 (589 days ago) InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: xorg-server UpgradeStatus: Upgraded to xenial on 2016-08-01 (25 days ago) ** Affects: xorg (Ubuntu) Importance: Low Status: Incomplete ** Tags: amd64 apport-bug third-party-packages xenial -- Ubuntu 16.04 system freeze xorg libglx.so https://bugs.launchpad.net/bugs/1617583 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1619593] Re: pkcon Fatal ERROR: MIME type not supported. when installing clicks in unity8 on a laptop
** Summary changed: - pkcon Fatal ERROR. when installing clicks in unity8 on a laptop + pkcon Fatal ERROR: MIME type not supported. when installing clicks in unity8 on a laptop -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1619593 Title: pkcon Fatal ERROR: MIME type not supported. when installing clicks in unity8 on a laptop Status in packagekit package in Ubuntu: New Bug description: A week ago I had no problem to install clicks(filemanager,music,terminal) but this week I came across with this pkcon error. Could it be caused by a packagekit update? Enviroment: Desktop running unity8 on 16.10 HW: intel graphics+intel processor Preconditions: download some clicks of core/non core apps to install Steps to reproduce: 1º Open terminal and run $ pkon install-local --allow-untrusted /path Current result: pkcon command returns the error given at the bottom Expected result: pkcon command should run with out any issue and clicks should be installed Reproducibility 100% - output 11:59:57PackageKit Verbose debugging enabled (on console 1) 11:59:57PackageKit filter=(null), filters=0 11:59:57PackageKit adding state 0x562f87db10d0 11:59:57PackageKit doing install files 11:59:57PackageKit role now install-files Installing files [=] :59:57 PackageKit using frontend diaFinished [=] :59:57PackageKit remove state 0x562Fatal error: MIME type 'application/x-click' not supported /home/users/Downloads/com.ubuntu.calendar_0.4.757_all.click To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1619593/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1609520] Re: Cannot login after logout
gnubug, thank you for reporting this and helping make Ubuntu better. Could you please run the following command once from a terminal by ensuring you have the package xdiagnose installed, and that you click the Yes button for attaching additional debugging information: apport-collect -p xorg 1609520 ** No longer affects: nvidia-graphics-drivers-361 (Ubuntu) ** No longer affects: nvidia-graphics-drivers-367 (Ubuntu) ** Package changed: xorg-server (Ubuntu) => xorg (Ubuntu) ** 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/1609520 Title: Cannot login after logout Status in xorg package in Ubuntu: Incomplete Bug description: If I logout and login again it doesn't work and brings me back to the login screen (lightdm). This is only the case if I use the nvidia graphics card of my laptop (via prime-select), using the intel card, I can logout and login again. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nvidia-361 361.42-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Wed Aug 3 19:14:59 2016 InstallationDate: Installed on 2016-05-18 (76 days ago) InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. SourcePackage: nvidia-graphics-drivers-361 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1609520/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1619593] [NEW] pkcon Fatal ERROR: MIME type not supported. when installing clicks in unity8 on a laptop
Public bug reported: A week ago I had no problem to install clicks(filemanager,music,terminal) but this week I came across with this pkcon error. Could it be caused by a packagekit update? Enviroment: Desktop running unity8 on 16.10 HW: intel graphics+intel processor Preconditions: download some clicks of core/non core apps to install Steps to reproduce: 1º Open terminal and run $ pkon install-local --allow-untrusted /path Current result: pkcon command returns the error given at the bottom Expected result: pkcon command should run with out any issue and clicks should be installed Reproducibility 100% - output 11:59:57PackageKit Verbose debugging enabled (on console 1) 11:59:57PackageKit filter=(null), filters=0 11:59:57PackageKit adding state 0x562f87db10d0 11:59:57PackageKit doing install files 11:59:57PackageKit role now install-files Installing files [=] :59:57 PackageKit using frontend diaFinished [=] :59:57PackageKit remove state 0x562Fatal error: MIME type 'application/x-click' not supported /home/users/Downloads/com.ubuntu.calendar_0.4.757_all.click ** Affects: packagekit (Ubuntu) Importance: Undecided Status: New ** Description changed: - A week ago I had no problem to isntall + A week ago I had no problem to install clicks(filemanager,music,terminal) but this week I came across with this pkcon error. Could it be caused by a packagekit update? Enviroment: Desktop running unity8 on 16.10 - HW: intel graphics+intel processor + HW: intel graphics+intel processor Preconditions: download some clicks of core/non core apps to install Steps to reproduce: 1º Open terminal and run $ pkon install-local --allow-untrusted /path - Current result: pkcon command returns the error given at the bottom Expected result: pkcon command should run with out any issue and clicks should be installed Reproducibility 100% - output 11:59:57PackageKit Verbose debugging enabled (on console 1) 11:59:57PackageKit filter=(null), filters=0 11:59:57PackageKit adding state 0x562f87db10d0 11:59:57PackageKit doing install files 11:59:57PackageKit role now install-files Installing files [=] :59:57 PackageKit using frontend diaFinished [=] :59:57PackageKit remove state 0x562Fatal error: MIME type 'application/x-click' not supported /home/users/Downloads/com.ubuntu.calendar_0.4.757_all.click -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1619593 Title: pkcon Fatal ERROR: MIME type not supported. when installing clicks in unity8 on a laptop Status in packagekit package in Ubuntu: New Bug description: A week ago I had no problem to install clicks(filemanager,music,terminal) but this week I came across with this pkcon error. Could it be caused by a packagekit update? Enviroment: Desktop running unity8 on 16.10 HW: intel graphics+intel processor Preconditions: download some clicks of core/non core apps to install Steps to reproduce: 1º Open terminal and run $ pkon install-local --allow-untrusted /path Current result: pkcon command returns the error given at the bottom Expected result: pkcon command should run with out any issue and clicks should be installed Reproducibility 100% - output 11:59:57PackageKit Verbose debugging enabled (on console 1) 11:59:57PackageKit filter=(null), filters=0 11:59:57PackageKit adding state 0x562f87db10d0 11:59:57PackageKit doing install files 11:59:57PackageKit role now install-files Installing files [=] :59:57 PackageKit using frontend diaFinished [=] :59:57PackageKit remove state 0x562Fatal error: MIME type 'application/x-click' not supported /home/users/Downloads/com.ubuntu.calendar_0.4.757_all.click To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1619593/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1612406] Re: numlock turn off alone
Eduardo Garbin, thank you for reporting this and helping make Ubuntu better. Could you please run the following command once from a terminal by ensuring you have the package xdiagnose installed, and that you click the Yes button for attaching additional debugging information: apport-collect -p xorg 1612406 When reporting xorg related bugs in the future, please do so via the above method. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Package changed: xorg-server (Ubuntu) => xorg (Ubuntu) ** 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/1612406 Title: numlock turn off alone Status in xorg package in Ubuntu: Incomplete Bug description: Hello; Im using Ubuntu 16.04.1 - 64bits, but this bug follow me from Ubuntu 14.04 No aparecente reason, the numeric keypad buttons are off. To work again, i have to press the 'numlock' twice, turn off and on again. This occurs many times during use of the machine. No matter what application or task I'm doing, it happens repeatedly. Hardware details: Caminho do hardware Dispositivo Classe Descrição system 670Z5E (SAMSUNG SENS Series) /0busNP670Z5E-XD1BR /0/0 memory 64KiB BIOS /0/34 memory 512KiB L2 cache /0/35 memory 128KiB L1 cache /0/36 memory 3MiB L3 cache /0/37 memory 8GiB Memória do sistema /0/37/0 memory DIMMProject-Id-Version: lshwReport-Msgid-Bugs-To: FULL NAME POT-Creation-Date: 2009-10-08 14:02+0200PO-Revision-Date: 2013-04-07 17:30+Last-Translator: Neliton Pereira Jr. Language-Team: Brazilian Portuguese MIME-Version: 1.0Content-Type: text/plain; charset=UTF-8Content-Transfer-Encoding: 8bitX-Launchpad-Export-Date: 2016-06-27 17:08+X-Generator: Launchpad (build 18115) [vazio] /0/37/1 memory DIMMProject-Id-Version: lshwReport-Msgid-Bugs-To: FULL NAME POT-Creation-Date: 2009-10-08 14:02+0200PO-Revision-Date: 2013-04-07 17:30+Last-Translator: Neliton Pereira Jr. Language-Team: Brazilian Portuguese MIME-Version: 1.0Content-Type: text/plain; charset=UTF-8Content-Transfer-Encoding: 8bitX-Launchpad-Export-Date: 2016-06-27 17:08+X-Generator: Launchpad (build 18115) [vazio] /0/37/2 memory 8GiB SODIMM DDR3 Síncrono 1600 MHz (0,6 ns) /0/37/3 memory DIMMProject-Id-Version: lshwReport-Msgid-Bugs-To: FULL NAME POT-Creation-Date: 2009-10-08 14:02+0200PO-Revision-Date: 2013-04-07 17:30+Last-Translator: Neliton Pereira Jr. Language-Team: Brazilian Portuguese MIME-Version: 1.0Content-Type: text/plain; charset=UTF-8Content-Transfer-Encoding: 8bitX-Launchpad-Export-Date: 2016-06-27 17:08+X-Generator: Launchpad (build 18115) [vazio] /0/38 processor Intel(R) Core(TM) i5-3230M CPU @ 2.60GHz /0/100bridge 3rd Gen Core processor DRAM Controller /0/100/1 bridge Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port /0/100/1/0genericIllegal Vendor ID /0/100/2 display3rd Gen Core processor Graphics Controller /0/100/14 bus7 Series/C210 Series Chipset Family USB xHCI Host Controller /0/100/14/0 usb4 busxHCI Host Controller /0/100/14/1 usb3 busxHCI Host Controller /0/100/14/1/3 genericUSB2.0-CRW /0/100/16 communication 7 Series/C210 Series Chipset Family MEI Controller #1 /0/100/1a bus7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 /0/100/1a/1 usb1 busEHCI Host Controller /0/100/1a/1/1 busIntegrated Rate Matching Hub /0/100/1a/1/1/2 input 2.4G Keyboard Mouse /0/100/1a/1/1/4 multimedia WebCam SC-10HDP12631N /0/100/1b multimedia 7 Series/C210 Series Chipset Family High Definition Audio Controller /0/100/1c bridge 7 Series/C210 Series Chipset Family PCI Express Root Port 1 /0/100/1c/0 wlp2s0 networkCentrino Advanced-N 6235 /0/100/1c.3
[Touch-packages] [Bug 1567877] Re: App installation has become quite unreliable
This could also be bug 1607382. ** Changed in: ubuntu-system-settings (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: ubuntu-system-settings (Ubuntu) Assignee: (unassigned) => Jonas G. Drange (jonas-drange) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-download-manager in Ubuntu. https://bugs.launchpad.net/bugs/1567877 Title: App installation has become quite unreliable Status in Canonical System Image: Confirmed Status in ubuntu-download-manager package in Ubuntu: New Status in ubuntu-system-settings package in Ubuntu: Fix Committed Status in unity-scope-click package in Ubuntu: Invalid Bug description: Recently the app installation seems to have degraded quite a lot in reliability. In most cases I need to trigger an installation twice or even three times in order to succeed. For instance just now I wanted to install the untappd scope. On the first attempt I clicked on the Install button and nothing happened except that the page became inactive. The progress spinner at the bottom was still spinning, but all the page content was disabled. The progress bar never appeared. Eventually I had to press the back button and then reenter the page. I clicked install again, the progress bar started. While waiting I've read through the comments, when I scrolled up to the top again, the progress bar was at 0% and would not move any more at all. Again, I had to press the back button and re-entered the page. On the third attempt it succeeded (except the issue that the progress bar again reverted to 0% after scrolling it out of view and back in, but eventually this time it changed to the open button. Attached, scope-registry.log To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1567877/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1617583] Re: Ubuntu 16.04 system freeze xorg libglx.so
sko, thank you for reporting this and helping make Ubuntu better. Could you please run the following command once from a terminal by ensuring you have the package xdiagnose installed, and that you click the Yes button for attaching additional debugging information: apport-collect -p xorg 1617583 When reporting xorg related bugs in the future, please do so via the above method. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Package changed: xorg-server (Ubuntu) => xorg (Ubuntu) ** 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/1617583 Title: Ubuntu 16.04 system freeze xorg libglx.so Status in xorg package in Ubuntu: Incomplete Bug description: System freezes after random time, sometimes after hours, sometimes not. When freeze, need to switch off power. No freezes any more after removing /usr/lib/xorg/modules/extensions/libglx.so. I dind't find anything in system logs. System was upgraded from 14.04 LTS to 16.04 TLS. With 14.04 no freezes. Other linux running well (double boot). Tried a few things before finding cause, e. g. disabling swap, changed from KDE to LXDE, I also tried kernels 4.6.0 and 4.6.5. System info: Ubuntu 16.04.1 LTS (prio installed as Kubuntu 14.04) xserver-xorg-core: Installed: 2:1.18.3-1ubuntu2.3 $ sudo lshw -numeric -C display *-display description: VGA compatible controller product: Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:F31] vendor: Intel Corporation [8086] physical id: 2 bus info: pci@:00:02.0 version: 0e width: 32 bits clock: 33MHz capabilities: pm msi vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:91 memory:d000-d03f memory:c000-cfff ioport:f080(size=8) What information should I provide? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg-core 2:1.18.3-1ubuntu2.3 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: LXDE Date: Sat Aug 27 16:13:39 2016 InstallationDate: Installed on 2015-01-15 (589 days ago) InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: xorg-server UpgradeStatus: Upgraded to xenial on 2016-08-01 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1617583/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1619600] [NEW] [SRU] New stable release 1.8.3
Public bug reported: [ Description ] We should keep up with GStreamer's bugfix releases in the 1.8 series that 16.04 shipped with. [ QA and testing ] Play a range of videos in Totem. Play a range of audio tracks in Rhythmbox. Try to stream audio and/or video. Try to install a missing codec. In all cases, make sure that everything which worked before still works. [ Regression potential ] One of the fixes could be bad. Watch out for it. ** Affects: gstreamer1.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1619600 Title: [SRU] New stable release 1.8.3 Status in gstreamer1.0 package in Ubuntu: New Bug description: [ Description ] We should keep up with GStreamer's bugfix releases in the 1.8 series that 16.04 shipped with. [ QA and testing ] Play a range of videos in Totem. Play a range of audio tracks in Rhythmbox. Try to stream audio and/or video. Try to install a missing codec. In all cases, make sure that everything which worked before still works. [ Regression potential ] One of the fixes could be bad. Watch out for it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1619600/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1546373] Re: Please update to 1.11
Ok, as long as this is not a transition (the API and ABI are compatible), then feel free to go ahead. If you need sponsorship, please attach the required files here and subscribe ~ubuntu-sponsors, otherwise just upload. Try to do it soon, so there is maximum time for testing. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to taglib in Ubuntu. https://bugs.launchpad.net/bugs/1546373 Title: Please update to 1.11 Status in taglib package in Ubuntu: In Progress Status in taglib package in Debian: New Bug description: https://github.com/taglib/taglib/blob/master/NEWS TagLib 1.11 (Apr 29, 2016) == 1.11: * Fixed reading APE items with long keys. * Fixed reading ID3v2 SYLT frames when description is empty. 1.11 BETA 2: * Better handling of PCM WAV files with a 'fact' chunk. * Better handling of corrupted APE tags. * Efficient decoding of unsynchronized ID3v2 frames. * Fixed text encoding when saving certain frames in ID3v2.3 tags. * Fixed updating the size of RIFF files when removing chunks. * Several smaller bug fixes and performance improvements. 1.11 BETA: * New API for creating FileRef from IOStream. * Added support for ID3v2 PCST and WFED frames. * Added support for pictures in XiphComment. * Added String::clear(). * Added FLAC::File::strip() for removing non-standard tags. * Added alternative functions to XiphComment::removeField(). * Added BUILD_BINDINGS build option. * Added ENABLE_CCACHE build option. * Replaced ENABLE_STATIC build option with BUILD_SHARED_LIBS. * Better handling of duplicate ID3v2 tags in all kinds of files. * Better handling of duplicate tag chunks in WAV files. * Better handling of duplicate tag chunks in AIFF files. * Better handling of duplicate Vorbis comment blocks in FLAC files. * Better handling of broken MPEG audio frames. * Fixed crash when calling File::properties() after strip(). * Fixed crash when parsing certain MPEG files. * Fixed crash when saving Ogg files. * Fixed possible file corruptions when saving ASF files. * Fixed possible file corruptions when saving FLAC files. * Fixed possible file corruptions when saving MP4 files. * Fixed possible file corruptions when saving MPEG files. * Fixed possible file corruptions when saving APE files. * Fixed possible file corruptions when saving Musepack files. * Fixed possible file corruptions when saving WavPack files. * Fixed updating the comment field of Vorbis comments. * Fixed reading date and time in ID3v2.3 tags. * Marked ByteVector::null and ByteVector::isNull() deprecated. * Marked String::null and String::isNull() deprecated. * Marked XiphComment::removeField() deprecated. * Marked Ogg::Page::getCopyWithNewPageSequenceNumber() deprecated. It returns null. * Marked custom integer types deprecated. * Many smaller bug fixes and performance improvements. TagLib 1.10 (Nov 11, 2015) == 1.10: * Added new options to the tagwriter example. * Fixed self-assignment operator in some types. * Fixed extraction of MP4 tag keys with an empty list. 1.10 BETA: * New API for the audio length in milliseconds. * Added support for ID3v2 ETCO and SYLT frames. * Added support for album artist in PropertyMap API of MP4 files. * Added support for embedded frames in ID3v2 CHAP and CTOC frames. * Added support for AIFF-C files. * Better handling of duplicate ID3v2 tags in MPEG files. * Allowed generating taglib.pc on Windows. * Added ZLIB_SOURCE build option. * Fixed backwards-incompatible change in TagLib::String when constructing UTF16 strings. * Fixed crash when parsing certain FLAC files. * Fixed crash when encoding empty strings. * Fixed saving of certain XM files on OS X. * Changed Xiph and APE generic getters to return space-concatenated values. * Fixed possible file corruptions when removing tags from WAV files. * Added support for MP4 files with 64-bit atoms in certain 64-bit environments. * Prevented ID3v2 padding from being too large. * Fixed crash when parsing corrupted APE files. * Fixed crash when parsing corrupted WAV files. * Fixed crash when parsing corrupted Ogg FLAC files. * Fixed crash when parsing corrupted MPEG files. * Fixed saving empty tags in WAV files. * Fixed crash when parsing corrupted Musepack files. * Fixed possible memory leaks when parsing AIFF and WAV files. * Fixed crash when parsing corrupted MP4 files. * Stopped writing empty ID3v2 frames. * Fixed possible file corruptions when saving WMA files. * Added TagLib::MP4::Tag::isEmpty(). * Added accessors to manipulate MP4 tags. * Fixed crash when parsing corrupted WavPack files. * Fixed seeking MPEG frames. * Fixed reading FLAC files with zero-sized padding blocks. * Added support for
[Touch-packages] [Bug 1619320] Re: problems after 16 install
** Tags added: bios-outdated-2ekt46a ** Changed in: xorg (Ubuntu) Importance: Undecided => Low -- 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/1619320 Title: problems after 16 install Status in xorg package in Ubuntu: Incomplete Bug description: not sure im new to this ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu Sep 1 07:03:22 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.248+bdcom, 3.13.0-95-generic, i686: installed bcmwl, 6.30.223.248+bdcom, 4.4.0-34-generic, i686: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 02) (prog-if 00 [VGA controller]) Subsystem: IBM 82945G/GZ Integrated Graphics Controller [1014:030e] Subsystem: IBM 82945G/GZ Integrated Graphics Controller [1014:030e] InstallationDate: Installed on 2016-07-31 (32 days ago) InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release i386 (20140807.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic root=UUID=168e743a-3325-4e07-91fa-1664f7ecb3d1 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2006 dmi.bios.vendor: IBM dmi.bios.version: 2EKT37AUS dmi.board.name: IBM dmi.chassis.vendor: IBM dmi.modalias: dmi:bvnIBM:bvr2EKT37AUS:bd06/13/2006:svnIBM:pn82121YU:pvrThinkCentreM52:rvnIBM:rnIBM:rvr:cvnIBM:ct3:cvr: dmi.product.name: 82121YU dmi.product.version: ThinkCentre M52 dmi.sys.vendor: IBM version.compiz: compiz 1:0.9.12.2+16.04.20160801.3-0ubuntu1 version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Wed Aug 31 16:32:12 2016 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputAT Translated Set 2 keyboard KEYBOARD, id 8 inputImPS/2 Generic Wheel Mouse MOUSE, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id9890 vendor HWP xserver.version: 2:1.18.3-1ubuntu2.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1619320/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1619406] Re: graphics problem maybe in bios
*** This bug is a duplicate of bug 1619320 *** https://bugs.launchpad.net/bugs/1619320 ** This bug has been marked a duplicate of bug 1619320 problems after 16 install -- 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/1619406 Title: graphics problem maybe in bios Status in xorg package in Ubuntu: New Bug description: new to this ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu Sep 1 11:00:38 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.248+bdcom, 3.13.0-95-generic, i686: installed bcmwl, 6.30.223.248+bdcom, 4.4.0-34-generic, i686: installed GraphicsCard: Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 02) (prog-if 00 [VGA controller]) Subsystem: IBM 82945G/GZ Integrated Graphics Controller [1014:030e] Subsystem: IBM 82945G/GZ Integrated Graphics Controller [1014:030e] InstallationDate: Installed on 2016-07-31 (32 days ago) InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release i386 (20140807.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic root=UUID=168e743a-3325-4e07-91fa-1664f7ecb3d1 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2006 dmi.bios.vendor: IBM dmi.bios.version: 2EKT37AUS dmi.board.name: IBM dmi.chassis.vendor: IBM dmi.modalias: dmi:bvnIBM:bvr2EKT37AUS:bd06/13/2006:svnIBM:pn82121YU:pvrThinkCentreM52:rvnIBM:rnIBM:rvr:cvnIBM:ct3:cvr: dmi.product.name: 82121YU dmi.product.version: ThinkCentre M52 dmi.sys.vendor: IBM version.compiz: compiz 1:0.9.12.2+16.04.20160801.3-0ubuntu1 version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Wed Aug 31 16:32:12 2016 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputAT Translated Set 2 keyboard KEYBOARD, id 8 inputImPS/2 Generic Wheel Mouse MOUSE, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id9890 vendor HWP xserver.version: 2:1.18.3-1ubuntu2.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1619406/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1619600] Re: [SRU] New stable release 1.8.3
** Changed in: gst-libav1.0 (Ubuntu) Status: New => Fix Released ** Changed in: gst-plugins-bad1.0 (Ubuntu) Status: New => Fix Released ** Changed in: gst-plugins-base1.0 (Ubuntu) Status: New => Fix Released ** Changed in: gst-plugins-good1.0 (Ubuntu) Status: New => Fix Released ** Changed in: gst-plugins-ugly1.0 (Ubuntu) Status: New => Fix Released ** Changed in: gstreamer-vaapi (Ubuntu) Status: New => Fix Released ** Changed in: gstreamer1.0 (Ubuntu) Status: New => Fix Released ** Changed in: gst-libav1.0 (Ubuntu Xenial) Status: New => In Progress ** Changed in: gst-libav1.0 (Ubuntu Xenial) Assignee: (unassigned) => Iain Lane (laney) ** Changed in: gst-plugins-bad1.0 (Ubuntu Xenial) Status: New => In Progress ** Changed in: gst-plugins-bad1.0 (Ubuntu Xenial) Assignee: (unassigned) => Iain Lane (laney) ** Changed in: gst-plugins-base1.0 (Ubuntu Xenial) Status: New => In Progress ** Changed in: gst-plugins-base1.0 (Ubuntu Xenial) Assignee: (unassigned) => Iain Lane (laney) ** Changed in: gst-plugins-good1.0 (Ubuntu Xenial) Status: New => In Progress ** Changed in: gst-plugins-good1.0 (Ubuntu Xenial) Assignee: (unassigned) => Iain Lane (laney) ** Changed in: gst-plugins-ugly1.0 (Ubuntu Xenial) Status: New => In Progress ** Changed in: gst-plugins-ugly1.0 (Ubuntu Xenial) Assignee: (unassigned) => Iain Lane (laney) ** Changed in: gstreamer-vaapi (Ubuntu Xenial) Status: New => In Progress ** Changed in: gstreamer-vaapi (Ubuntu Xenial) Assignee: (unassigned) => Iain Lane (laney) ** Changed in: gstreamer1.0 (Ubuntu Xenial) Status: New => In Progress ** Changed in: gstreamer1.0 (Ubuntu Xenial) Assignee: (unassigned) => Iain Lane (laney) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1619600 Title: [SRU] New stable release 1.8.3 Status in gst-libav1.0 package in Ubuntu: Fix Released Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Fix Released Status in gst-plugins-good1.0 package in Ubuntu: Fix Released Status in gst-plugins-ugly1.0 package in Ubuntu: Fix Released Status in gstreamer-vaapi package in Ubuntu: Fix Released Status in gstreamer1.0 package in Ubuntu: Fix Released Status in gst-libav1.0 source package in Xenial: In Progress Status in gst-plugins-bad1.0 source package in Xenial: In Progress Status in gst-plugins-base1.0 source package in Xenial: In Progress Status in gst-plugins-good1.0 source package in Xenial: In Progress Status in gst-plugins-ugly1.0 source package in Xenial: In Progress Status in gstreamer-vaapi source package in Xenial: In Progress Status in gstreamer1.0 source package in Xenial: In Progress Bug description: [ Description ] We should keep up with GStreamer's bugfix releases in the 1.8 series that 16.04 shipped with. [ QA and testing ] Play a range of videos in Totem. Play a range of audio tracks in Rhythmbox. Try to stream audio and/or video. Try to install a missing codec. In all cases, make sure that everything which worked before still works. [ Regression potential ] One of the fixes could be bad. Watch out for it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1619600/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1574347] Re: [SRU] Re-read the link type if the name changed
I am pretty sure I'm having this problem on a Toshiba Chromebook 2 (CB35-B3340) running 16.04 fully updated as of this week. I get the ethernet up/down arrows, there is no ethernet on this laptop. I also get the state where it is disconnected and not showing any wifi networks. It seems to be related to suspend/wake, but doesn't always happen. $ lspci |grep -i net 01:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb) ii network-manager 1.2.0-0ubuntu0.16.04.3 amd64 ii network-manager-gnome 1.2.0-0ubuntu0.16.04.3 amd64 ii network-manager-pptp 1.1.93-1ubuntu1amd64 ii network-manager-pptp-gnome1.1.93-1ubuntu1amd64 Running this got things back to normal: $ sudo service network-manager restart This looked noteworthy: # dmesg |grep iwl [ 10.658028] iwlwifi :01:00.0: Direct firmware load for iwlwifi-7260-17.ucode failed with error -2 [ 11.064468] iwlwifi :01:00.0: loaded firmware version 16.242414.0 op_mode iwlmvm [ 11.545992] iwlwifi :01:00.0: Detected Intel(R) Dual Band Wireless AC 7260, REV=0x144 [ 11.546081] iwlwifi :01:00.0: L1 Enabled - LTR Disabled [ 11.546326] iwlwifi :01:00.0: L1 Enabled - LTR Disabled [ 11.771068] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs' [ 11.777060] iwlwifi :01:00.0 wlp1s0: renamed from wlan0 [ 12.285642] iwlwifi :01:00.0: L1 Enabled - LTR Disabled [ 12.285883] iwlwifi :01:00.0: L1 Enabled - LTR Disabled [ 12.491349] iwlwifi :01:00.0: L1 Enabled - LTR Disabled [ 12.491592] iwlwifi :01:00.0: L1 Enabled - LTR Disabled [ 461.381354] iwlwifi :01:00.0: L1 Enabled - LTR Disabled [ 461.381596] iwlwifi :01:00.0: L1 Enabled - LTR Disabled -- 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/1574347 Title: [SRU] Re-read the link type if the name changed Status in NetworkManager: Fix Released Status in OEM Priority Project: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Fix Released Bug description: [Impact] NM needs to re-read the DEVTYPE after the device name changed, an example is that WiFi network list disappears from network manager applet [Testcase] 1. Boot the system. It should include a wireless device. 2. In a terminal, run 'nmcli dev'. 3. In the correct case, the line for the wireless device should read "wifi" under the TYPE column. In a failure case, it will read "ethernet". After upgrading to the new version, the repeating the above steps should give expected behavior. [Regression Potential] Potential of causing regression is relatively small for a one line change to re-read a value to be known. --- Problems:- 1. The network manager applet does not show the list of WiFI APs it can find. 2. The network manager applet does not the name of the AP to which it is connected 3. The icon of the applet shows two vertical arrows in opposite direction - the wired connection symbol and NOT the wifi connected icon. Temporary Workaround:- Log out and again log back in. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1574347/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1619616] [NEW] mir fails to build with protobuf3
Public bug reported: mir fails to build with protobuf3. build logs at https://launchpad.net/ubuntu/+source/mir/0.24.0+16.10.20160815.3-0ubuntu2 In file included from /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/server/frontend/protobuf_message_processor.cpp:24:0: /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/include/server/mir/frontend/template_protobuf_message_processor.h: In function ‘void mir::frontend::detail::invoke(Self*, Server*, void (ServerX::*)(const ParameterMessage*, ResultMessage*, google::protobuf::Closure*), const mir::frontend::detail::Invocation&)’: /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/include/server/mir/frontend/template_protobuf_message_processor.h:68:13: error: ‘NewPermanentCallback’ is not a member of ‘google::protobuf’ google::protobuf::NewPermanentCallback< ^~ /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/include/server/mir/frontend/template_protobuf_message_processor.h:68:13: note: suggested alternative: In file included from /usr/include/google/protobuf/stubs/common.h:48:0, from /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/obj-x86_64-linux-gnu/src/protobuf/mir_protobuf.pb.h:9, from /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/include/common/mir/protobuf/display_server.h:22, from /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/server/frontend/display_server.h:22, from /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/server/frontend/protobuf_message_processor.cpp:19: /usr/include/google/protobuf/stubs/callback.h:524:36: note: ‘google::protobuf::internal::NewPermanentCallback’ inline ResultCallback2* NewPermanentCallback( ^~~~ In file included from /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/server/frontend/protobuf_message_processor.cpp:24:0: /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/include/server/mir/frontend/template_protobuf_message_processor.h:69:21: error: expected primary-expression before ‘,’ token Self, ^ /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/include/server/mir/frontend/template_protobuf_message_processor.h:70:43: error: expected primary-expression before ‘,’ token ::google::protobuf::uint32, ^ /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/include/server/mir/frontend/template_protobuf_message_processor.h:71:59: error: expected ‘(’ before ‘>’ token typename result_ptr_t::type>( ^ ** Affects: mir (Ubuntu) Importance: Critical Status: Confirmed ** Tags: ftbfs ** Tags added: ftbfs ** Changed in: mir (Ubuntu) Status: New => Confirmed ** Changed in: mir (Ubuntu) Importance: Undecided => Critical ** Changed in: mir (Ubuntu) Milestone: None => ubuntu-16.09 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1619616 Title: mir fails to build with protobuf3 Status in mir package in Ubuntu: Confirmed Bug description: mir fails to build with protobuf3. build logs at https://launchpad.net/ubuntu/+source/mir/0.24.0+16.10.20160815.3-0ubuntu2 In file included from /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/server/frontend/protobuf_message_processor.cpp:24:0: /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/include/server/mir/frontend/template_protobuf_message_processor.h: In function ‘void mir::frontend::detail::invoke(Self*, Server*, void (ServerX::*)(const ParameterMessage*, ResultMessage*, google::protobuf::Closure*), const mir::frontend::detail::Invocation&)’: /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/include/server/mir/frontend/template_protobuf_message_processor.h:68:13: error: ‘NewPermanentCallback’ is not a member of ‘google::protobuf’ google::protobuf::NewPermanentCallback< ^~ /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/include/server/mir/frontend/template_protobuf_message_processor.h:68:13: note: suggested alternative: In file included from /usr/include/google/protobuf/stubs/common.h:48:0, from /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/obj-x86_64-linux-gnu/src/protobuf/mir_protobuf.pb.h:9, from /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/include/common/mir/protobuf/display_server.h:22, from /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/server/frontend/display_server.h:22, from /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/server/frontend/protobuf_message_processor.cpp:19: /usr/include/google/protobuf/stubs/callback.h:524:36: note: ‘google::protobuf::internal::NewPermanentCallback’ inline ResultCallback2* NewPermanentCallback( ^~~~ In file included from /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/serv
[Touch-packages] [Bug 1619616] Re: mir fails to build with protobuf3
** Changed in: mir (Ubuntu) Assignee: (unassigned) => Alan Griffiths (alan-griffiths) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1619616 Title: mir fails to build with protobuf3 Status in mir package in Ubuntu: Confirmed Bug description: mir fails to build with protobuf3. build logs at https://launchpad.net/ubuntu/+source/mir/0.24.0+16.10.20160815.3-0ubuntu2 In file included from /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/server/frontend/protobuf_message_processor.cpp:24:0: /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/include/server/mir/frontend/template_protobuf_message_processor.h: In function ‘void mir::frontend::detail::invoke(Self*, Server*, void (ServerX::*)(const ParameterMessage*, ResultMessage*, google::protobuf::Closure*), const mir::frontend::detail::Invocation&)’: /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/include/server/mir/frontend/template_protobuf_message_processor.h:68:13: error: ‘NewPermanentCallback’ is not a member of ‘google::protobuf’ google::protobuf::NewPermanentCallback< ^~ /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/include/server/mir/frontend/template_protobuf_message_processor.h:68:13: note: suggested alternative: In file included from /usr/include/google/protobuf/stubs/common.h:48:0, from /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/obj-x86_64-linux-gnu/src/protobuf/mir_protobuf.pb.h:9, from /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/include/common/mir/protobuf/display_server.h:22, from /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/server/frontend/display_server.h:22, from /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/server/frontend/protobuf_message_processor.cpp:19: /usr/include/google/protobuf/stubs/callback.h:524:36: note: ‘google::protobuf::internal::NewPermanentCallback’ inline ResultCallback2* NewPermanentCallback( ^~~~ In file included from /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/server/frontend/protobuf_message_processor.cpp:24:0: /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/include/server/mir/frontend/template_protobuf_message_processor.h:69:21: error: expected primary-expression before ‘,’ token Self, ^ /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/include/server/mir/frontend/template_protobuf_message_processor.h:70:43: error: expected primary-expression before ‘,’ token ::google::protobuf::uint32, ^ /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/include/server/mir/frontend/template_protobuf_message_processor.h:71:59: error: expected ‘(’ before ‘>’ token typename result_ptr_t::type>( ^ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1619616/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1619616] Re: mir fails to build with protobuf3
maybe wait for https://launchpad.net/ubuntu/+source/protobuf/3.0.0-7 * Added patch by Srivats P to restore New*Callback into google::protobuf namespace. Required for ostinato (#835435). (Closes: #836200). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1619616 Title: mir fails to build with protobuf3 Status in mir package in Ubuntu: Confirmed Bug description: mir fails to build with protobuf3. build logs at https://launchpad.net/ubuntu/+source/mir/0.24.0+16.10.20160815.3-0ubuntu2 In file included from /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/server/frontend/protobuf_message_processor.cpp:24:0: /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/include/server/mir/frontend/template_protobuf_message_processor.h: In function ‘void mir::frontend::detail::invoke(Self*, Server*, void (ServerX::*)(const ParameterMessage*, ResultMessage*, google::protobuf::Closure*), const mir::frontend::detail::Invocation&)’: /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/include/server/mir/frontend/template_protobuf_message_processor.h:68:13: error: ‘NewPermanentCallback’ is not a member of ‘google::protobuf’ google::protobuf::NewPermanentCallback< ^~ /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/include/server/mir/frontend/template_protobuf_message_processor.h:68:13: note: suggested alternative: In file included from /usr/include/google/protobuf/stubs/common.h:48:0, from /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/obj-x86_64-linux-gnu/src/protobuf/mir_protobuf.pb.h:9, from /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/include/common/mir/protobuf/display_server.h:22, from /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/server/frontend/display_server.h:22, from /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/server/frontend/protobuf_message_processor.cpp:19: /usr/include/google/protobuf/stubs/callback.h:524:36: note: ‘google::protobuf::internal::NewPermanentCallback’ inline ResultCallback2* NewPermanentCallback( ^~~~ In file included from /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/server/frontend/protobuf_message_processor.cpp:24:0: /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/include/server/mir/frontend/template_protobuf_message_processor.h:69:21: error: expected primary-expression before ‘,’ token Self, ^ /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/include/server/mir/frontend/template_protobuf_message_processor.h:70:43: error: expected primary-expression before ‘,’ token ::google::protobuf::uint32, ^ /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/include/server/mir/frontend/template_protobuf_message_processor.h:71:59: error: expected ‘(’ before ‘>’ token typename result_ptr_t::type>( ^ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1619616/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1619281] Re: Text.color can't be compared reliably
Interesting observation:
QColor::darker(int factor) versus QML's Qt.darker(color baseColor, real
factor)
which might cause the discrepancy in the alpha floating point precision
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtdeclarative-opensource-
src in Ubuntu.
https://bugs.launchpad.net/bugs/1619281
Title:
Text.color can't be compared reliably
Status in qtdeclarative-opensource-src package in Ubuntu:
Confirmed
Bug description:
Given the below QML:
import QtQuick 2.4
Text {
id: text
text: 'foobar'
color: foobar
property color foobar: Qt.rgba(0, 0, 0, 0.5)
property color foobar2: foobar
Component.onCompleted: {
console.log("text:", text.color, foobar, Qt.colorEqual(text.color,
foobar), text.color.a);
console.log("property:", foobar2, foobar, Qt.colorEqual(foobar2,
foobar), foobar2.a);
/*
qml: text: #8000 #8000 false 0.5019607843137255
qml: property: #8000 #8000 true 0.576295109483
*/
}
}
Seems that Text.color stores the colour with a different precision,
resulting in Qt.colorEqual() returning false.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: libqt5quick5 5.6.1-4ubuntu3~xenialoverlay1~1 [origin:
LP-PPA-ci-train-ppa-service-stable-phone-overlay]
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Sep 1 14:40:27 2016
InstallationDate: Installed on 2016-05-06 (117 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
SourcePackage: qtdeclarative-opensource-src
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1619281/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1618423] Re: Modesetting driver cannot handle different display resolutions for two monitors
The output of those commands are: 1.2.13 and 08/08/2016. I can't test the same configuration that I originally tested for another week, but on another 1680x1050 monitor it did work, eventually. I had to restart lightdm several times because things happened like the mouse click no longer working, once when I changed the resolution it flipped everything sideways, and the mouse started moving extraordinarily slowly and the desktop was unusable. My issue is that there's a more severe bug with the brightness control after resume in the newer BIOS and its predecessor, so I can't use it (see http://en.community.dell.com/techcenter/os- applications/f/4613/p/19985875/20927410#20927410). Dell's official response is that they are aware of it, but they clearly aren't fixing it since they have released a second BIOS with the same bug. If it's purely a BIOS issue, why does the modeset driver have this screen resolution problem and not the intel driver? -- 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/1618423 Title: Modesetting driver cannot handle different display resolutions for two monitors Status in xorg package in Ubuntu: Incomplete Bug description: I have an external 1920x1080 monitor attached to my laptop, which has a 3840x2160 display. When I run them both at their native resolutions, the laptop display only works in the top quarter of the desktop, except for the unity launcher and unity top bar. Anything that leaves the top quarter leaves trails and flickers awfully (see attached image, which shows everything except the flickering). I also tried it with the laptop on 2560x1440 (I had to add it manually because of a a separate bug where the modesetting driver limits the max vertical refresh frequency of default modelines to 60 Hz) and exactly the same thing happens (although the geometry isn't one quarter any more). It works fine with the intel driver, but not the modesetting driver, so it seems to be an xserver issue rather than a unity issue. It also works fine if I set both monitors to 1920x1080. The modesetting driver seems to struggle with setting resolutions. When I first log into the desktop, it takes a good 5 seconds longer than the intel driver to set up the screens, and for a while it looks like I have a 640x480 screen (judging by the huge mouse pointer I get). Given this bug and the vertical refresh bug, maybe yakkety shouldn't default to the modesetting driver? ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xserver-xorg 1:7.7+13ubuntu3 Uname: Linux 4.7.2-040702-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Aug 30 19:26:06 2016 DistUpgraded: 2016-07-25 02:38:44,004 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: yakkety DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-9136-generic, x86_64: installed bbswitch, 0.8, 4.7.2-040702-generic, x86_64: installed nvidia, 367-367.44, 4.4.0-9136-generic, x86_64: installed nvidia, 367-367.44, 4.7.2-040702-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 530 [1028:06e4] InstallationDate: Installed on 2016-07-04 (57 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. MachineType: Dell Inc. XPS 15 9550 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.7.2-040702-generic root=UUID=8de7ebec-48db-48b6-9eb9-fafdee4eb7d6 ro rootflags=subvol=@ quiet splash nogpumanager vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to yakkety on 2016-07-24 (36 days ago) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu1 version.ia32-libs:
[Touch-packages] [Bug 1619616] Re: mir fails to build with protobuf3
sensible -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1619616 Title: mir fails to build with protobuf3 Status in mir package in Ubuntu: Confirmed Bug description: mir fails to build with protobuf3. build logs at https://launchpad.net/ubuntu/+source/mir/0.24.0+16.10.20160815.3-0ubuntu2 In file included from /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/server/frontend/protobuf_message_processor.cpp:24:0: /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/include/server/mir/frontend/template_protobuf_message_processor.h: In function ‘void mir::frontend::detail::invoke(Self*, Server*, void (ServerX::*)(const ParameterMessage*, ResultMessage*, google::protobuf::Closure*), const mir::frontend::detail::Invocation&)’: /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/include/server/mir/frontend/template_protobuf_message_processor.h:68:13: error: ‘NewPermanentCallback’ is not a member of ‘google::protobuf’ google::protobuf::NewPermanentCallback< ^~ /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/include/server/mir/frontend/template_protobuf_message_processor.h:68:13: note: suggested alternative: In file included from /usr/include/google/protobuf/stubs/common.h:48:0, from /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/obj-x86_64-linux-gnu/src/protobuf/mir_protobuf.pb.h:9, from /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/include/common/mir/protobuf/display_server.h:22, from /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/server/frontend/display_server.h:22, from /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/server/frontend/protobuf_message_processor.cpp:19: /usr/include/google/protobuf/stubs/callback.h:524:36: note: ‘google::protobuf::internal::NewPermanentCallback’ inline ResultCallback2* NewPermanentCallback( ^~~~ In file included from /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/server/frontend/protobuf_message_processor.cpp:24:0: /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/include/server/mir/frontend/template_protobuf_message_processor.h:69:21: error: expected primary-expression before ‘,’ token Self, ^ /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/include/server/mir/frontend/template_protobuf_message_processor.h:70:43: error: expected primary-expression before ‘,’ token ::google::protobuf::uint32, ^ /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/include/server/mir/frontend/template_protobuf_message_processor.h:71:59: error: expected ‘(’ before ‘>’ token typename result_ptr_t::type>( ^ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1619616/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1618540] Re: Big delay opening apps from launcher
** Package changed: unity8 (Ubuntu) => ubuntu-app-launch (Ubuntu) ** Description changed: Hi, it's been a week or so that I noticed that apps no longer open instantly once you click on them in the Unity launcher; it takes around one second to see it open and start loading. This didn't happen before, and gives the user a weird feeling of "maybe I didn't tap well on the icon". I'm on rc-proposed, BQ E4.5 Thanks :) + + + + $ system-image-cli -i + current build number: 413 + device name: krillin + channel: ubuntu-touch/rc-proposed/bq-aquaris.en + last update: 2016-09-02 12:55:16 + version version: 413 + version ubuntu: 20160823 + version device: 20160606-ab415b2 + version custom: 20160805-985-38-15 + + Flash the above, apps from launcher open instantly. + + Upgrade: + libubuntu-app-launch3 + qtmir-android + qtdeclarative5-qtmir-plugin + + Take the versions from: + https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/stable-phone-overlay/+sourcepub/6826577/+listing-archive-extra + https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/stable-phone-overlay/+sourcepub/6826594/+listing-archive-extra + + Restart unity8 and observe a 1s+ delay in launching apps. ** Changed in: canonical-devices-system-image Assignee: Michał Sawicz (saviq) => Alejandro J. Cura (alecu) ** Changed in: ubuntu-app-launch (Ubuntu) Importance: Undecided => Critical ** Changed in: ubuntu-app-launch (Ubuntu) Status: Confirmed => Triaged ** Changed in: ubuntu-app-launch (Ubuntu) Assignee: (unassigned) => Ted Gould (ted) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1618540 Title: Big delay opening apps from launcher Status in Canonical System Image: Triaged Status in ubuntu-app-launch package in Ubuntu: Triaged Bug description: Hi, it's been a week or so that I noticed that apps no longer open instantly once you click on them in the Unity launcher; it takes around one second to see it open and start loading. This didn't happen before, and gives the user a weird feeling of "maybe I didn't tap well on the icon". I'm on rc-proposed, BQ E4.5 Thanks :) $ system-image-cli -i current build number: 413 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-09-02 12:55:16 version version: 413 version ubuntu: 20160823 version device: 20160606-ab415b2 version custom: 20160805-985-38-15 Flash the above, apps from launcher open instantly. Upgrade: libubuntu-app-launch3 qtmir-android qtdeclarative5-qtmir-plugin Take the versions from: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/stable-phone-overlay/+sourcepub/6826577/+listing-archive-extra https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/stable-phone-overlay/+sourcepub/6826594/+listing-archive-extra Restart unity8 and observe a 1s+ delay in launching apps. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1618540/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1616909] Re: Installing multiple dbgsym packages fails
This bug was fixed in the package apt - 1.3~rc3ubuntu2 --- apt (1.3~rc3ubuntu2) yakkety; urgency=medium * test-apt-cdrom: Fix for gnupg 2.1.15 * Revert "test: Assert multi-arch in the chroot" * Revert "test: Make sure we always find a dpkg in status file" -- Julian Andres Klode Thu, 01 Sep 2016 13:06:14 + ** Changed in: apt (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 apt in Ubuntu. https://bugs.launchpad.net/bugs/1616909 Title: Installing multiple dbgsym packages fails Status in apt package in Ubuntu: Fix Released Bug description: On Yakkety, installing a single -dbgsym package using apt works fine. However, if I specify multiple on a command line, I get this: $ sudo apt install metacity-dbgsym gnome-flashback-dbgsym Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: gnome-flashback-dbgsym metacity-dbgsym 0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/1168 kB of archives. After this operation, 4972 kB of additional disk space will be used. dpkg: error: searched, but found no packages (files matching *.deb) E: Sub-process /usr/bin/dpkg returned an error code (2) The *.deb wildcard is wrong because the packages actually have a .ddeb extension, i.e. /var/cache/apt/archives/gnome-flashback- dbgsym_3.20.2-1ubuntu1_amd64.ddeb. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: apt 1.3~rc2ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-9134.53-generic 4.4.15 Uname: Linux 4.4.0-9134-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Thu Aug 25 15:44:22 2016 InstallationDate: Installed on 2014-08-23 (732 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140823) SourcePackage: apt UpgradeStatus: Upgraded to yakkety on 2016-04-28 (119 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1616909/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1598097] Re: frozen screen and system
penalvch, thank you! that solved my problem -- 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/1598097 Title: frozen screen and system Status in xorg package in Ubuntu: Expired Bug description: some times the screen is frozen and when I log out of the session the system froze and cannot go into ttyS the message is like the driver of the graphic is not good ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Jul 1 10:27:45 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Skylake Integrated Graphics [17aa:3804] InstallationDate: Installed on 2016-06-24 (6 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 002: ID 8086:0a66 Intel Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80NT ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic root=UUID=009e3c20-6d0e-4f82-a892-f0750d5de684 ro quiet splash radeon.runpm=0 vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2015 dmi.bios.vendor: LENOVO dmi.bios.version: CFCN21WW(V1.03) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo ideapad 5 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 500-15ISK dmi.modalias: dmi:bvnLENOVO:bvrCFCN21WW(V1.03):bd08/10/2015:svnLENOVO:pn80NT:pvrLenovoideapad500-15ISK:rvnLENOVO:rnLenovoideapad5:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad500-15ISK: dmi.product.name: 80NT dmi.product.version: Lenovo ideapad 500-15ISK dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri Jul 1 09:18:59 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 14829 vendor AUO xserver.version: 2:1.18.3-1ubuntu2.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1598097/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1405232] Re: ping reports wrong IP responding under certain conditions
Was about to file a report for this. Can confirm, tested in 16.04 http://pastebin.com/JzexVR0D -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/1405232 Title: ping reports wrong IP responding under certain conditions Status in iputils package in Ubuntu: Confirmed Bug description: Description: Ubuntu 14.04.1 LTS Release: 14.04 iputils-ping: Installed: 3:20121221-4ubuntu1.1 Candidate: 3:20121221-4ubuntu1.1 ping will report the incorrect reply IP address under certain, specific conditions, and is repeatable. This is how to re-create the issue: 1. Start pinging an IP where you get an ICMP error message from some other device (RFC792 lists errors). For instance: Destination IP is offline and the last-hop router reports message type "Destination Unreachable". I assume this would work for any ICMP error, though. 2. When the device comes back online, ping reports replies from the "other" device, when it should report replies from the device that is sending the "Echo Reply" messages. 3. If the ping is stopped and restarted after the device is up, it reports the correct IP address again. Other ping utilities do not exhibit this behavior. Example output (Destination that was pinged was 172.21.56.50, last hop router was 172.21.25.103): circle@circle:~$ /bin/ping 172.21.56.50 PING 172.21.56.50 (172.21.56.50) 56(84) bytes of data. From 172.21.25.103 icmp_seq=1 Destination Host Unreachable From 172.21.25.103 icmp_seq=2 Destination Host Unreachable From 172.21.25.103 icmp_seq=3 Destination Host Unreachable From 172.21.25.103 icmp_seq=4 Destination Host Unreachable From 172.21.25.103 icmp_seq=5 Destination Host Unreachable From 172.21.25.103 icmp_seq=6 Destination Host Unreachable 64 bytes from 172.21.25.103: icmp_seq=7 ttl=63 time=0.689 ms 64 bytes from 172.21.25.103: icmp_seq=8 ttl=63 time=0.635 ms 64 bytes from 172.21.25.103: icmp_seq=9 ttl=63 time=0.656 ms 64 bytes from 172.21.25.103: icmp_seq=10 ttl=63 time=0.822 ms 64 bytes from 172.21.25.103: icmp_seq=11 ttl=63 time=0.785 ms ^C --- 172.21.56.50 ping statistics --- 11 packets transmitted, 5 received, +6 errors, 54% packet loss, time 10023ms rtt min/avg/max/mdev = 0.635/0.717/0.822/0.077 ms, pipe 3 circle@circle:~$ /bin/ping 172.21.56.50 PING 172.21.56.50 (172.21.56.50) 56(84) bytes of data. 64 bytes from 172.21.56.50: icmp_seq=1 ttl=63 time=0.737 ms 64 bytes from 172.21.56.50: icmp_seq=2 ttl=63 time=0.646 ms 64 bytes from 172.21.56.50: icmp_seq=3 ttl=63 time=0.626 ms ^C --- 172.21.56.50 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1998ms rtt min/avg/max/mdev = 0.626/0.669/0.737/0.056 ms ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: iputils-ping 3:20121221-4ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Dec 23 10:50:35 2014 InstallationDate: Installed on 2014-10-08 (76 days ago) InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140723) SourcePackage: iputils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1405232/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1619422] Re: dnsmasq cache-size is hardcoded to 10000
Thank you for taking the time to report this bug and helping to make Ubuntu better. This sounds like something that should be decided upon by the upstream dnsmasq project, and not in Ubuntu directly. Could you check validity with their current latest release, and if still relevant, file a bug with them please? Since this behaviour appears to be intentional, I'm marking this bug Won't Fix for Ubuntu, as I don't think we should patch this. If upstream decide to change behaviour, then this can change. ** Tags added: need-upstream-report ** Changed in: dnsmasq (Ubuntu) Status: New => Won't Fix ** Changed in: dnsmasq (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1619422 Title: dnsmasq cache-size is hardcoded to 1 Status in dnsmasq package in Ubuntu: Won't Fix Bug description: Most people won't run into this problem, but if you use a very large hosts-file (like this one here: http://someonewhocares.org/hosts/) you fill up the cache completely. No matter what you set for cache-size, the maximum possible value is hardcoded in the file option.c of the dnsmasq sources. As there is no indication of this arbitrary limit , you might end up wondering: why the hell is dnsmasq not caching anything? The value was probably put there to save resources if dnsmasq runs on an embedded system and users who need a bigger cache size can setup their patched instance of dnsmasq, but there should be at least some kind of warning in the default config file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1619422/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1619481] Re: package libnl-3-200 (not installed) failed to install/upgrade: pokus o prepísanie zdieľaného súboru „/etc/libnl-3/classid“, ktorý sa líši od iných inštancií balíka l
Translation: Unpacking libnl-3-200:i386 (3.2.27-1) ... dpkg: error processing archive /var/cache/apt/archives/libnl-3-200_3.2.27-1_i386.deb (--unpack): trying to overwrite a shared file "/etc/libnl-3/classic" which is different from other instances of the package libnl-3-200:i386 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1619481 Title: package libnl-3-200 (not installed) failed to install/upgrade: pokus o prepísanie zdieľaného súboru „/etc/libnl-3/classid“, ktorý sa líši od iných inštancií balíka libnl-3-200:i386 Status in libnl3 package in Ubuntu: New Bug description: I do not know more. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libnl-3-200 (not installed) ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 Uname: Linux 3.19.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 Date: Thu Sep 1 22:31:44 2016 DuplicateSignature: package:libnl-3-200:(not installed):pokus o prepísanie zdieľaného súboru „/etc/libnl-3/classid“, ktorý sa líši od iných inštancií balíka libnl-3-200:i386 ErrorMessage: pokus o prepísanie zdieľaného súboru „/etc/libnl-3/classid“, ktorý sa líši od iných inštancií balíka libnl-3-200:i386 InstallationDate: Installed on 2016-04-16 (137 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20151128 RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.14 SourcePackage: libnl3 Title: package libnl-3-200 (not installed) failed to install/upgrade: pokus o prepísanie zdieľaného súboru „/etc/libnl-3/classid“, ktorý sa líši od iných inštancií balíka libnl-3-200:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1619481/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1619481] Re: package libnl-3-200 (not installed) failed to install/upgrade: pokus o prepísanie zdieľaného súboru „/etc/libnl-3/classid“, ktorý sa líši od iných inštancií balíka l
Thank you for taking the time to report this bug and helping to make Ubuntu better. Since there isn't enough information in your report to differentiate between a local configuration problem and a bug in Ubuntu, I'm marking this bug as Incomplete. I tried to reproduce this on both 14.04 and 16.04, and libnl-3-200:i386 and libnl-3-200:amd64 do co-install without errors. So if this is a bug, we need exact steps to reproduce to make any progress, please. If indeed this is a local configuration problem, you can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community Or if you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to New. ** Changed in: libnl3 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1619481 Title: package libnl-3-200 (not installed) failed to install/upgrade: pokus o prepísanie zdieľaného súboru „/etc/libnl-3/classid“, ktorý sa líši od iných inštancií balíka libnl-3-200:i386 Status in libnl3 package in Ubuntu: Incomplete Bug description: I do not know more. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libnl-3-200 (not installed) ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 Uname: Linux 3.19.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 Date: Thu Sep 1 22:31:44 2016 DuplicateSignature: package:libnl-3-200:(not installed):pokus o prepísanie zdieľaného súboru „/etc/libnl-3/classid“, ktorý sa líši od iných inštancií balíka libnl-3-200:i386 ErrorMessage: pokus o prepísanie zdieľaného súboru „/etc/libnl-3/classid“, ktorý sa líši od iných inštancií balíka libnl-3-200:i386 InstallationDate: Installed on 2016-04-16 (137 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20151128 RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.14 SourcePackage: libnl3 Title: package libnl-3-200 (not installed) failed to install/upgrade: pokus o prepísanie zdieľaného súboru „/etc/libnl-3/classid“, ktorý sa líši od iných inštancií balíka libnl-3-200:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1619481/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1619668] [NEW] Brightness is not changed after pluging or restore after sleep
Public bug reported: All these happens after 14-->16 upgrade 2 cases here: 1. when plug at a dockstation(lenovo t420s) brighness is not chaged(remains too dark) 2. when plug in adapter - the same ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Sep 2 16:22:49 2016 DistUpgraded: 2016-08-17 13:31:37,867 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.24, 3.19.0-66-generic, x86_64: installed virtualbox, 5.0.24, 4.4.0-34-generic, x86_64: installed virtualbox, 5.0.24, 4.4.0-36-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:21d2] InstallationDate: Installed on 2015-12-17 (259 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: LENOVO 41716PG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic root=UUID=14d23f0e-cfcc-40fd-87e2-7ca166c9b29f ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to xenial on 2016-08-17 (16 days ago) dmi.bios.date: 04/29/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 8CET59WW (1.39 ) dmi.board.asset.tag: Not Available dmi.board.name: 41716PG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8CET59WW(1.39):bd04/29/2015:svnLENOVO:pn41716PG:pvrThinkPadT420s:rvnLENOVO:rn41716PG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 41716PG dmi.product.version: ThinkPad T420s dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20160801.3-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Wed Aug 31 22:23:57 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 12876 vendor SEC xserver.version: 2:1.18.3-1ubuntu2.3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- 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/1619668 Title: Brightness is not changed after pluging or restore after sleep Status in xorg package in Ubuntu: New Bug description: All these happens after 14-->16 upgrade 2 cases here: 1. when plug at a dockstation(lenovo t420s) brighness is not chaged(remains too dark) 2. when plug in adapter - the same ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Sep 2 16:22:49 2016 DistUpgraded: 2016-08-17 13:31:37,867 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.24, 3.19.0-66-generic, x86_64: installed virtualbox, 5.0.24, 4.4.0-34-generic, x86_64: installed virtualbox, 5.0.24, 4.4.0-36-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 2nd Generat
[Touch-packages] [Bug 1619600] Re: [SRU] New stable release 1.8.3
vaapi will follow after -bad is accepted -bad contains some updates from yakkety which I think Xenial should get too, but let me know if it's a problem ** Changed in: gstreamer-vaapi (Ubuntu Xenial) Status: In Progress => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1619600 Title: [SRU] New stable release 1.8.3 Status in gst-libav1.0 package in Ubuntu: Fix Released Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Fix Released Status in gst-plugins-good1.0 package in Ubuntu: Fix Released Status in gst-plugins-ugly1.0 package in Ubuntu: Fix Released Status in gstreamer-vaapi package in Ubuntu: Fix Released Status in gstreamer1.0 package in Ubuntu: Fix Released Status in gst-libav1.0 source package in Xenial: Incomplete Status in gst-plugins-bad1.0 source package in Xenial: In Progress Status in gst-plugins-base1.0 source package in Xenial: In Progress Status in gst-plugins-good1.0 source package in Xenial: In Progress Status in gst-plugins-ugly1.0 source package in Xenial: In Progress Status in gstreamer-vaapi source package in Xenial: Incomplete Status in gstreamer1.0 source package in Xenial: In Progress Bug description: [ Description ] We should keep up with GStreamer's bugfix releases in the 1.8 series that 16.04 shipped with. [ QA and testing ] Play a range of videos in Totem. Play a range of audio tracks in Rhythmbox. Try to stream audio and/or video. Try to install a missing codec. In all cases, make sure that everything which worked before still works. [ Regression potential ] One of the fixes could be bad. Watch out for it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1619600/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1619600] Re: [SRU] New stable release 1.8.3
Can't update libav atm, due to https://bugzilla.gnome.org/show_bug.cgi?id=770753 ** Bug watch added: GNOME Bug Tracker #770753 https://bugzilla.gnome.org/show_bug.cgi?id=770753 ** Changed in: gst-libav1.0 (Ubuntu Xenial) Status: In Progress => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1619600 Title: [SRU] New stable release 1.8.3 Status in gst-libav1.0 package in Ubuntu: Fix Released Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Fix Released Status in gst-plugins-good1.0 package in Ubuntu: Fix Released Status in gst-plugins-ugly1.0 package in Ubuntu: Fix Released Status in gstreamer-vaapi package in Ubuntu: Fix Released Status in gstreamer1.0 package in Ubuntu: Fix Released Status in gst-libav1.0 source package in Xenial: Incomplete Status in gst-plugins-bad1.0 source package in Xenial: In Progress Status in gst-plugins-base1.0 source package in Xenial: In Progress Status in gst-plugins-good1.0 source package in Xenial: In Progress Status in gst-plugins-ugly1.0 source package in Xenial: In Progress Status in gstreamer-vaapi source package in Xenial: Incomplete Status in gstreamer1.0 source package in Xenial: In Progress Bug description: [ Description ] We should keep up with GStreamer's bugfix releases in the 1.8 series that 16.04 shipped with. [ QA and testing ] Play a range of videos in Totem. Play a range of audio tracks in Rhythmbox. Try to stream audio and/or video. Try to install a missing codec. In all cases, make sure that everything which worked before still works. [ Regression potential ] One of the fixes could be bad. Watch out for it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1619600/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1589317] Re: Upgrading to Xenial leaves empty /usr/lib/x86_64-linux-gnu/pango/ hierarchy
do you still have the upgrade log? it would have been useful to know what pango version was installed at the time of the issue... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1589317 Title: Upgrading to Xenial leaves empty /usr/lib/x86_64-linux-gnu/pango/ hierarchy Status in pango1.0 package in Ubuntu: New Bug description: During an upgrade from a Trusty system to Xenial, I ended up with the following problem: Removing linux-image-extra-3.13.0-85-generic (3.13.0-85.129) ... depmod: FATAL: could not load /boot/System.map-3.13.0-85-generic: No such file or directory run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.13.0-85-generic /boot/vmlinuz-3.13.0-85-generic run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.13.0-85-generic /boot/vmlinuz-3.13.0-85-generic update-initramfs: Generating /boot/initrd.img-3.13.0-85-generic WARNING: missing /lib/modules/3.13.0-85-generic Ensure all necessary drivers are built into the linux image! depmod: ERROR: could not open directory /lib/modules/3.13.0-85-generic: No such file or directory depmod: FATAL: could not search modules: No such file or directory cryptsetup: WARNING: failed to detect canonical device of /dev/nfs cryptsetup: WARNING: could not determine root device from /etc/fstab cp: cannot stat '/usr/lib/x86_64-linux-gnu/pango/1.6.0/module-files.d/libpango1.0-0.modules': No such file or directory E: /usr/share/initramfs-tools/hooks/plymouth failed with return 1. update-initramfs: failed for /boot/initrd.img-3.13.0-85-generic with 1. run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 dpkg: error processing package linux-image-extra-3.13.0-85-generic (--remove): subprocess installed post-removal script returned error exit status 1 Errors were encountered while processing: linux-image-extra-3.13.0-85-generic E: Sub-process /usr/bin/dpkg returned an error code (1) Turns out this was directly caused by simplistic checking in the plymouth initramfs-tools hook: # wheezy if ls /usr/lib/x86_64-linux-gnu/pango/1* > /dev/null 2>&1 I want back and checked a backup of my original Trusty filesystem, and it indeed has an empty hierarchy here: kiko@gasolinux:/usr/lib/x86_64-linux-gnu/pango$ ls -lR .: total 4 drwxr-xr-x 3 root root 4096 Feb 26 2014 1.6.0/ ./1.6.0: total 4 drwxr-xr-x 2 root root 4096 Feb 27 2014 modules/ ./1.6.0/modules: total 0 This may be better handled by smarter code in the plymouth hook, or if the empty directory may have further consequences, by making the pango upgrade really clean up that directory. I solved the problem by removing the hierarchy and re-running apt-get -f install. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libpango1.0-0 1.36.3-1ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-87.133-generic 3.13.11-ckt39 Uname: Linux 3.13.0-87-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jun 5 20:45:27 2016 SourcePackage: pango1.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1589317/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1589317] Re: Upgrading to Xenial leaves empty /usr/lib/x86_64-linux-gnu/pango/ hierarchy
seems similar to bug #1335017 which impacted trusty ** Changed in: pango1.0 (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1589317 Title: Upgrading to Xenial leaves empty /usr/lib/x86_64-linux-gnu/pango/ hierarchy Status in pango1.0 package in Ubuntu: New Bug description: During an upgrade from a Trusty system to Xenial, I ended up with the following problem: Removing linux-image-extra-3.13.0-85-generic (3.13.0-85.129) ... depmod: FATAL: could not load /boot/System.map-3.13.0-85-generic: No such file or directory run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.13.0-85-generic /boot/vmlinuz-3.13.0-85-generic run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.13.0-85-generic /boot/vmlinuz-3.13.0-85-generic update-initramfs: Generating /boot/initrd.img-3.13.0-85-generic WARNING: missing /lib/modules/3.13.0-85-generic Ensure all necessary drivers are built into the linux image! depmod: ERROR: could not open directory /lib/modules/3.13.0-85-generic: No such file or directory depmod: FATAL: could not search modules: No such file or directory cryptsetup: WARNING: failed to detect canonical device of /dev/nfs cryptsetup: WARNING: could not determine root device from /etc/fstab cp: cannot stat '/usr/lib/x86_64-linux-gnu/pango/1.6.0/module-files.d/libpango1.0-0.modules': No such file or directory E: /usr/share/initramfs-tools/hooks/plymouth failed with return 1. update-initramfs: failed for /boot/initrd.img-3.13.0-85-generic with 1. run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 dpkg: error processing package linux-image-extra-3.13.0-85-generic (--remove): subprocess installed post-removal script returned error exit status 1 Errors were encountered while processing: linux-image-extra-3.13.0-85-generic E: Sub-process /usr/bin/dpkg returned an error code (1) Turns out this was directly caused by simplistic checking in the plymouth initramfs-tools hook: # wheezy if ls /usr/lib/x86_64-linux-gnu/pango/1* > /dev/null 2>&1 I want back and checked a backup of my original Trusty filesystem, and it indeed has an empty hierarchy here: kiko@gasolinux:/usr/lib/x86_64-linux-gnu/pango$ ls -lR .: total 4 drwxr-xr-x 3 root root 4096 Feb 26 2014 1.6.0/ ./1.6.0: total 4 drwxr-xr-x 2 root root 4096 Feb 27 2014 modules/ ./1.6.0/modules: total 0 This may be better handled by smarter code in the plymouth hook, or if the empty directory may have further consequences, by making the pango upgrade really clean up that directory. I solved the problem by removing the hierarchy and re-running apt-get -f install. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libpango1.0-0 1.36.3-1ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-87.133-generic 3.13.11-ckt39 Uname: Linux 3.13.0-87-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jun 5 20:45:27 2016 SourcePackage: pango1.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1589317/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1619689] [NEW] package cups 2.1.3-4 failed to install/upgrade: triggers looping, abandoned
Public bug reported: Have not updated cupsd.conf for a long time. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups 2.1.3-4 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CupsErrorLog: E [02/Sep/2016:07:35:02 -0600] Unknown directive BrowseAddress on line 7 of /etc/cups/cupsd.conf. Date: Thu Sep 1 18:36:28 2016 ErrorMessage: triggers looping, abandoned Lpstat: device for Hewlett-Packard-HP-LaserJet-5MP: hp:/par/HP_LaserJet_5MP?device=/dev/parport1 device for HP-LaserJet: parallel:/dev/lp1 MachineType: System manufacturer System Product Name Papersize: letter PpdFiles: Hewlett-Packard-HP-LaserJet-5MP: HP LaserJet 5MP Postscript (recommended) HP-LaserJet: HP LaserJet Foomatic/laserjet (recommended) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic root=UUID=72be9d99-d37a-44d7-85b3-6af71e450efc ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic root=UUID=72be9d99-d37a-44d7-85b3-6af71e450efc ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: cups Title: package cups 2.1.3-4 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to xenial on 2016-08-15 (17 days ago) dmi.bios.date: 10/16/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1002 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8B75-M 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.:bvr1002:bd10/16/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8B75-M:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer mtime.conffile..etc.cups.cupsd.conf: 2015-09-04T14:54:28.973348 ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1619689 Title: package cups 2.1.3-4 failed to install/upgrade: triggers looping, abandoned Status in cups package in Ubuntu: New Bug description: Have not updated cupsd.conf for a long time. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups 2.1.3-4 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CupsErrorLog: E [02/Sep/2016:07:35:02 -0600] Unknown directive BrowseAddress on line 7 of /etc/cups/cupsd.conf. Date: Thu Sep 1 18:36:28 2016 ErrorMessage: triggers looping, abandoned Lpstat: device for Hewlett-Packard-HP-LaserJet-5MP: hp:/par/HP_LaserJet_5MP?device=/dev/parport1 device for HP-LaserJet: parallel:/dev/lp1 MachineType: System manufacturer System Product Name Papersize: letter PpdFiles: Hewlett-Packard-HP-LaserJet-5MP: HP LaserJet 5MP Postscript (recommended) HP-LaserJet: HP LaserJet Foomatic/laserjet (recommended) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic root=UUID=72be9d99-d37a-44d7-85b3-6af71e450efc ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic root=UUID=72be9d99-d37a-44d7-85b3-6af71e450efc ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: cups Title: package cups 2.1.3-4 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to xenial on 2016-08-15 (17 days ago) dmi.bios.date: 10/16/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1002 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8B75-M 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.:bvr1002:bd10/16/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8B75-M:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer mtime.conffile..etc.cups.cupsd.conf: 2015-09-04T14:54:28.973348 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1619689/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/
[Touch-packages] [Bug 1619616] Re: mir fails to build with protobuf3
builds with 3.0.0-7, then has one failing test: test 19 Start 19: Protobuf-can-be-reloaded 19: Test command: /<>/mir-0.24.0+16.10.20160815.3/obj-powerpc64le-linux-gnu/bin/mir_test_reload_protobuf 19: Test timeout computed to be: 9.99988e+06 19/19 Test #19: Protobuf-can-be-reloaded ..***Exception: SegFault 0.17 sec 95% tests passed, 1 tests failed out of 19 Total Test time (real) = 125.73 sec The following tests FAILED: 19 - Protobuf-can-be-reloaded (SEGFAULT) Errors while running CTest Makefile:85: recipe for target 'test' failed make[2]: *** [test] Error 8 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1619616 Title: mir fails to build with protobuf3 Status in mir package in Ubuntu: Confirmed Bug description: mir fails to build with protobuf3. build logs at https://launchpad.net/ubuntu/+source/mir/0.24.0+16.10.20160815.3-0ubuntu2 In file included from /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/server/frontend/protobuf_message_processor.cpp:24:0: /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/include/server/mir/frontend/template_protobuf_message_processor.h: In function ‘void mir::frontend::detail::invoke(Self*, Server*, void (ServerX::*)(const ParameterMessage*, ResultMessage*, google::protobuf::Closure*), const mir::frontend::detail::Invocation&)’: /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/include/server/mir/frontend/template_protobuf_message_processor.h:68:13: error: ‘NewPermanentCallback’ is not a member of ‘google::protobuf’ google::protobuf::NewPermanentCallback< ^~ /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/include/server/mir/frontend/template_protobuf_message_processor.h:68:13: note: suggested alternative: In file included from /usr/include/google/protobuf/stubs/common.h:48:0, from /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/obj-x86_64-linux-gnu/src/protobuf/mir_protobuf.pb.h:9, from /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/include/common/mir/protobuf/display_server.h:22, from /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/server/frontend/display_server.h:22, from /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/server/frontend/protobuf_message_processor.cpp:19: /usr/include/google/protobuf/stubs/callback.h:524:36: note: ‘google::protobuf::internal::NewPermanentCallback’ inline ResultCallback2* NewPermanentCallback( ^~~~ In file included from /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/server/frontend/protobuf_message_processor.cpp:24:0: /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/include/server/mir/frontend/template_protobuf_message_processor.h:69:21: error: expected primary-expression before ‘,’ token Self, ^ /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/include/server/mir/frontend/template_protobuf_message_processor.h:70:43: error: expected primary-expression before ‘,’ token ::google::protobuf::uint32, ^ /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/include/server/mir/frontend/template_protobuf_message_processor.h:71:59: error: expected ‘(’ before ‘>’ token typename result_ptr_t::type>( ^ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1619616/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1619689] Re: package cups 2.1.3-4 failed to install/upgrade: triggers looping, abandoned
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1619689 Title: package cups 2.1.3-4 failed to install/upgrade: triggers looping, abandoned Status in cups package in Ubuntu: New Bug description: Have not updated cupsd.conf for a long time. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups 2.1.3-4 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CupsErrorLog: E [02/Sep/2016:07:35:02 -0600] Unknown directive BrowseAddress on line 7 of /etc/cups/cupsd.conf. Date: Thu Sep 1 18:36:28 2016 ErrorMessage: triggers looping, abandoned Lpstat: device for Hewlett-Packard-HP-LaserJet-5MP: hp:/par/HP_LaserJet_5MP?device=/dev/parport1 device for HP-LaserJet: parallel:/dev/lp1 MachineType: System manufacturer System Product Name Papersize: letter PpdFiles: Hewlett-Packard-HP-LaserJet-5MP: HP LaserJet 5MP Postscript (recommended) HP-LaserJet: HP LaserJet Foomatic/laserjet (recommended) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic root=UUID=72be9d99-d37a-44d7-85b3-6af71e450efc ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic root=UUID=72be9d99-d37a-44d7-85b3-6af71e450efc ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: cups Title: package cups 2.1.3-4 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to xenial on 2016-08-15 (17 days ago) dmi.bios.date: 10/16/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1002 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8B75-M 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.:bvr1002:bd10/16/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8B75-M:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer mtime.conffile..etc.cups.cupsd.conf: 2015-09-04T14:54:28.973348 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1619689/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1615265] Re: OpenStreetMap Plugin for Map QML type broken
If Qt 5.5 has a working plugin, I assume Qt 5.6 in yakkety and xenial phone overlay is fine, so adding only OTA task. There's a ticket now for this https://requests.ci- train.ubuntu.com/#/ticket/1900 , remains to be seen how hard the backporting is. It seems it will need even more location core changes backporting than what was done a few months ago when newer OSM/MapQuest plugin was ported. Hopefully it will be just a couple of commits though. ** Changed in: qtlocation-opensource-src (Ubuntu) Assignee: (unassigned) => Timo Jyrinki (timo-jyrinki) ** Changed in: qtlocation-opensource-src (Ubuntu) Status: New => In Progress ** Also affects: qtlocation-opensource-src (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: qtlocation-opensource-src (Ubuntu RTM) Assignee: (unassigned) => Timo Jyrinki (timo-jyrinki) ** Changed in: qtlocation-opensource-src (Ubuntu) Importance: Undecided => High ** Changed in: qtlocation-opensource-src (Ubuntu RTM) Importance: Undecided => High ** Changed in: qtlocation-opensource-src (Ubuntu) Status: In Progress => Fix Released ** Changed in: qtlocation-opensource-src (Ubuntu RTM) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtlocation-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1615265 Title: OpenStreetMap Plugin for Map QML type broken Status in Canonical System Image: Confirmed Status in qtlocation-opensource-src package in Ubuntu: Fix Released Status in qtlocation-opensource-src package in Ubuntu RTM: In Progress Bug description: Since MapQuest shut down its service, the osm plugin for the Map QML type is broken: https://developer.ubuntu.com/api/apps/qml/sdk-15.04.5/QtLocation .location-plugin-osm/ To reproduce it, make sure that you do not request tiles that are already in cache! To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1615265/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1619616] Re: mir fails to build with protobuf3
Only on powerpc64? I don't have one of those. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1619616 Title: mir fails to build with protobuf3 Status in mir package in Ubuntu: Confirmed Bug description: mir fails to build with protobuf3. build logs at https://launchpad.net/ubuntu/+source/mir/0.24.0+16.10.20160815.3-0ubuntu2 In file included from /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/server/frontend/protobuf_message_processor.cpp:24:0: /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/include/server/mir/frontend/template_protobuf_message_processor.h: In function ‘void mir::frontend::detail::invoke(Self*, Server*, void (ServerX::*)(const ParameterMessage*, ResultMessage*, google::protobuf::Closure*), const mir::frontend::detail::Invocation&)’: /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/include/server/mir/frontend/template_protobuf_message_processor.h:68:13: error: ‘NewPermanentCallback’ is not a member of ‘google::protobuf’ google::protobuf::NewPermanentCallback< ^~ /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/include/server/mir/frontend/template_protobuf_message_processor.h:68:13: note: suggested alternative: In file included from /usr/include/google/protobuf/stubs/common.h:48:0, from /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/obj-x86_64-linux-gnu/src/protobuf/mir_protobuf.pb.h:9, from /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/include/common/mir/protobuf/display_server.h:22, from /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/server/frontend/display_server.h:22, from /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/server/frontend/protobuf_message_processor.cpp:19: /usr/include/google/protobuf/stubs/callback.h:524:36: note: ‘google::protobuf::internal::NewPermanentCallback’ inline ResultCallback2* NewPermanentCallback( ^~~~ In file included from /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/server/frontend/protobuf_message_processor.cpp:24:0: /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/include/server/mir/frontend/template_protobuf_message_processor.h:69:21: error: expected primary-expression before ‘,’ token Self, ^ /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/include/server/mir/frontend/template_protobuf_message_processor.h:70:43: error: expected primary-expression before ‘,’ token ::google::protobuf::uint32, ^ /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/include/server/mir/frontend/template_protobuf_message_processor.h:71:59: error: expected ‘(’ before ‘>’ token typename result_ptr_t::type>( ^ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1619616/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1619616] Re: mir fails to build with protobuf3
same on amd64 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1619616 Title: mir fails to build with protobuf3 Status in mir package in Ubuntu: Confirmed Bug description: mir fails to build with protobuf3. build logs at https://launchpad.net/ubuntu/+source/mir/0.24.0+16.10.20160815.3-0ubuntu2 In file included from /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/server/frontend/protobuf_message_processor.cpp:24:0: /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/include/server/mir/frontend/template_protobuf_message_processor.h: In function ‘void mir::frontend::detail::invoke(Self*, Server*, void (ServerX::*)(const ParameterMessage*, ResultMessage*, google::protobuf::Closure*), const mir::frontend::detail::Invocation&)’: /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/include/server/mir/frontend/template_protobuf_message_processor.h:68:13: error: ‘NewPermanentCallback’ is not a member of ‘google::protobuf’ google::protobuf::NewPermanentCallback< ^~ /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/include/server/mir/frontend/template_protobuf_message_processor.h:68:13: note: suggested alternative: In file included from /usr/include/google/protobuf/stubs/common.h:48:0, from /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/obj-x86_64-linux-gnu/src/protobuf/mir_protobuf.pb.h:9, from /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/include/common/mir/protobuf/display_server.h:22, from /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/server/frontend/display_server.h:22, from /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/server/frontend/protobuf_message_processor.cpp:19: /usr/include/google/protobuf/stubs/callback.h:524:36: note: ‘google::protobuf::internal::NewPermanentCallback’ inline ResultCallback2* NewPermanentCallback( ^~~~ In file included from /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/server/frontend/protobuf_message_processor.cpp:24:0: /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/include/server/mir/frontend/template_protobuf_message_processor.h:69:21: error: expected primary-expression before ‘,’ token Self, ^ /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/include/server/mir/frontend/template_protobuf_message_processor.h:70:43: error: expected primary-expression before ‘,’ token ::google::protobuf::uint32, ^ /«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/include/server/mir/frontend/template_protobuf_message_processor.h:71:59: error: expected ‘(’ before ‘>’ token typename result_ptr_t::type>( ^ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1619616/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1612767] Re: Drop appmenu-qt5 from default installations
What broke appmenu-qt5 may be https://git.gnome.org/browse/gnome- session/commit/?id=971baf2e225abc5a. In this case we probably need to backport https://git.gnome.org/browse /gnome-session/commit/?id=ce4208add3b49d44 which fixes that issue. However this should not affect the configuration without appmenu-qt5. Hopefully more on this soon. -- 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/1612767 Title: Drop appmenu-qt5 from default installations Status in indicator-appmenu package in Ubuntu: New Status in qtbase-opensource-src package in Ubuntu: New Bug description: Currently we are using appmenu-qt5 as our platform theme on desktop, however it has many disadvantages, which make me want to get rid of it: 1) Its design is a hack: instead of the using normal QPA API for getting the menu, it retrieves the menu bar using QWidget::findChild, and then casts the pointer to QMenu*. The normal methods (which are getting called by Qt) remain empty stubs. 2) It is preventing applications from using GTK+ theme integration, such as dialogs (I reported this as bug 1378935, but there is no easy way to fix that). 3) It is not working with Qt Quick applications (because it expects a QtWidgets window; see also bug 1323853). The standard implementation will work with i.e. Qt Quick Controls 2 using apps (implemented in https://codereview.qt-project.org/142733). 4) It breaks other environments such as Plasma when installed: see bug 1434516. 5) Finally, it is mostly unmaintained: most patches since 2014 are authored by me, however I see no point continuing to develop that code. Recently, Shawn Rutledge and I have written a native implementation of what appmenu-qt5 provides (global menu and system tray), which is part of Qt. That code uses the normal API, is well maintained, and works better than appmenu-qt5 (or at least not worse). So I propose to drop appmenu-qt5 from default Ubuntu installations, and maybe later from archive too. Unfortunately we use Qt 5.6, and some of the needed patches are only in Qt 5.7, so I would like to backport them to our packaging: https://code.qt.io/cgit/qt/qtbase.git/commit/?id=f199bb9133fe0446 (will be in 5.6.2 / 5.7.0) https://code.qt.io/cgit/qt/qtbase.git/commit/?id=488cf78e44947eff (will be in 5.7.0) https://code.qt.io/cgit/qt/qtbase.git/commit/?id=b6a824d0a3b4fabd (will be in 5.7.0) https://code.qt.io/cgit/qt/qtbase.git/commit/?id=e4d79e1fdeb6b26b (will be in 5.7.0) Timo: if you have no objections, I will commit those patches to the packaging Git. After we do that, I will remove the appmenu-qt5 recommendation from indicator-appmenu (that is the only package referring to it). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-appmenu/+bug/1612767/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1406810] Re: screen is garbled with 14.10 (was fine with 14.04)
I did reinstall 14.04.1 (kernel 3.13.0-32). I got a black screen. I remember that 14.04.4 failed *after* the bios upgrade. -- 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/1406810 Title: screen is garbled with 14.10 (was fine with 14.04) Status in xorg package in Ubuntu: Incomplete Bug description: On a iMac Alu 2010, when upgrading from 14.04 desktop to 14.10 desktop or installing 10.10 server (SSH package only) the screen shows thin horizontal lines moving on a black background. /etc/X11/xorg.conf is absent (using default config), /var/log/Xorg.0.log doesn't show any error beside the lack of the fglrx module. But I doubt it's relevant with the symptoms appearing on the server install. --- .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.19 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 DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV770/M98L [Mobility Radeon HD 4850] [1002:944a] (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Device [106b:00b5] InstallationDate: Installed on 2015-01-01 (440 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.3) MachineType: Apple Inc. iMac11,1 Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-79-generic root=UUID=f19c8f84-1553-4a36-889a-acfb8a13da9a ro ProcVersionSignature: Ubuntu 3.13.0-79.123-generic 3.13.11-ckt33 Tags: trusty ubuntu compiz-0.9 Uname: Linux 3.13.0-79-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 03/17/10 dmi.bios.vendor: Apple Inc. dmi.bios.version: IM111.88Z.0034.B02.1003171314 dmi.board.name: Mac-F2268DAE dmi.board.vendor: Apple Inc. dmi.chassis.type: 13 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F2268DAE dmi.modalias: dmi:bvnAppleInc.:bvrIM111.88Z.0034.B02.1003171314:bd03/17/10:svnAppleInc.:pniMac11,1:pvr1.0:rvnAppleInc.:rnMac-F2268DAE:rvr:cvnAppleInc.:ct13:cvrMac-F2268DAE: dmi.product.name: iMac11,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Wed Mar 16 19:43:11 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2.7 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1406810/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1619035] Re: FFe: Sync protobuf 3.0.0-6 (main) from Debian unstable (main)
** Changed in: protobuf (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to protobuf in Ubuntu. https://bugs.launchpad.net/bugs/1619035 Title: FFe: Sync protobuf 3.0.0-6 (main) from Debian unstable (main) Status in protobuf package in Ubuntu: Fix Released Bug description: Please sync protobuf 3.0.0-6 (main) from Debian unstable (main) Explanation of FeatureFreeze exception: Copy-pasted from the Debian transition bug #835170 [1]: "It is crucial to have protobuf-3 from life cycle prospective. Also several golang dependencies require protobuf v3 so upload actually allows to fix numerous problems." This will start a transition of +/- 30 packages. https://release.debian.org/transitions/html/auto-protobuf.html Protobuf 2.6.1-2 currently in yakkety FTBFS with GCC 6. [1] https://bugs.debian.org/835170 Changelog entries since current yakkety version 2.6.1-2: protobuf (3.0.0-6) unstable; urgency=medium * New "java-test-scope.patch" to set scope of "junit" and "easymock" to "test" (Closes: #835514). Thanks, Markus Koschany. -- Dmitry Smirnov Sat, 27 Aug 2016 09:02:16 +1000 protobuf (3.0.0-5) unstable; urgency=medium * Team upload. * Removed obsolete Conflicts/Replaces (Closes: #835385). Thanks, Robert Edmonds. * New patch to fix "EXPECT_DEATH" FTBFS on kFreeBSD (Closes: #835388). Thanks, Bas Couwenberg. -- Dmitry Smirnov Fri, 26 Aug 2016 08:36:08 +1000 protobuf (3.0.0-4) unstable; urgency=low * Team upload. * Updated "libprotobuf-java.poms" (Closes: #835358). Thanks, Markus Koschany. * Added new patches to fix FTBFS on s390x and sparc64 (Closes: #835290). Thanks, Aurelien Jarno; thanks Sebastiaan Couwenberg. * New patch to fix FTBFS on Hurd (Closes: #835267). Thanks, Sebastiaan Couwenberg. * rules: removed "-O0" #796069 workaround for mips(el). -- Dmitry Smirnov Thu, 25 Aug 2016 11:28:07 +1000 protobuf (3.0.0-3) unstable; urgency=low [ Bas Couwenberg ] * Added new patch to fix FTBFS "misleading indentation" (Closes: #835266). -- Dmitry Smirnov Wed, 24 Aug 2016 13:54:36 +1000 protobuf (3.0.0-2) unstable; urgency=medium * rules: invoke "generate_descriptor_proto.sh" to re-generate pre-built .pb.go files if necessary. -- Dmitry Smirnov Wed, 24 Aug 2016 13:19:43 +1000 protobuf (3.0.0-1) unstable; urgency=low * Team upload. [ Dmitry Smirnov ] * New upstream release [July 2016] (Closes: #795841, #811650). - removed obsolete patches. * Introduced "watch" file. * copyright: + full review & update; + convert to copyright-format 1.0; * Build-Depends += "google-mock". -- Dmitry Smirnov Mon, 22 Aug 2016 15:35:08 +1000 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/protobuf/+bug/1619035/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1211110] Re: network manager openvpn dns push data not updating system DNS addresses
Hi, I also thought I had a bug on this, but actually the problem is configuration of search domains for VPN resolutions. I have an updated Ubuntu 16.04 and the scenario described here works for me. Network Manager uses dnsmasq for DNS resolution so the /etc/resolv.conf name server is always 127.0.1.1 independently of the VPN being up or down. Don't expect /etc/resolv.conf to change nameserver values. The only thing that is updated in resolv.conf are the search domains. Having 127.0.1.1 in resolv.conf points the DNS resolutions to the dnsmasq daemon which is running locally. In the scenario that you have an ethernet connection and a VPN connection, you need first to decide if you want your traffic all to go through the VPN connection or not. This is done by the configuration "Use this connection only for the resources on its network" inside IPV4 Settings->routes (it can also be forced by the VPN Server, just check where is pointing the first 0.0.0.0 route in netstat -r). In my case VPN server is not forcing and I want traffic to go through both interfaces (split tunnel) so the option is checked. With the VPN up you'll have DNS servers for the ethernet connection and the DNS servers for the VPN connection. They can be automatically given by DHCP or statically assigned by you. You can even add additional DNS servers to the ones you receive automatically. Having DNSs in both sides you need to use search domains to decide if you are going to use DNS from one side or the other. Similar to the DNS servers you can also receive those search domains by DHCP for each interface and you can also add your own. The problem I had with resolution was that I was trying to resolve VPN domains which where not being pushed as a search domain by the VPN and so they were being sent to the ethernet DNSs instead of the VPN DNSs. Basically to solve this I had to add the VPN search domains manually in IPV4 Settings. (easier than ask VPN server admins to push the correct search domains when the VPN comes up) Hope this helps. -- 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/120 Title: network manager openvpn dns push data not updating system DNS addresses Status in network-manager package in Ubuntu: Incomplete Status in openvpn package in Ubuntu: Incomplete Bug description: [Triage Notes] This bug can no longer make progress. Please see comment 50 for details and further instructions. [Original Description] When IPv4 Method is set to Automatic VPN, DNS address recieved from OpenVPN server do not update resolv.conf. This can be achieved when using a standard openvpn config file by adding the lines: script-security 2 up /etc/openvpn/update-resolv-conf down /etc/openvpn/update-resolv-conf In Network-manager there seems to be no option to run connection specific scripts and the DNS data from the server is ignored. Ubuntu 13.04 Network-manager 0.9.8.0-0ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/120/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1447715] Re: dhclient -6: Can't bind to dhcp address: Cannot assign requested address
Better yet, have dhclient retry that bind call itself, at least for a short while, before throwing an error. -- 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/1447715 Title: dhclient -6: Can't bind to dhcp address: Cannot assign requested address Status in DHCP: New Status in isc-dhcp package in Ubuntu: Confirmed Bug description: After upgrading to Ubuntu 15.04 my computer is unable to obtain an IPv6 address via DHCPv6. The root cause is that dhclient is exiting with the following message: - Can't bind to dhcp address: Cannot assign requested address Please make sure there is no other dhcp server running and that there's no entry for dhcp or bootp in /etc/inetd.conf. Also make sure you are not running HP JetAdmin software, which includes a bootp server. If you think you have received this message due to a bug rather than a configuration issue please read the section on submitting bugs on either our web page at www.isc.org or in the README file before submitting a bug. These pages explain the proper process and the information we find helpful for debugging.. exiting. - The problem seems to exist in isc-dhcp-client 4.3.1-5ubuntu2 (15.04 version) because downgrading to isc-dhcp-client 4.2.4-7ubuntu14 (14.10 version) allows me to obtain an address. NetworkManager is the one launching dhclient. The two invocations (one for IPv4 and one for IPv6) are: dhclient_start(): running: /sbin/dhclient -d -q -sf /usr/lib/NetworkManager/nm-dhcp-helper -pf /run/sendsigs.omit.d /network-manager.dhclient-eth0.pid -lf /var/lib/NetworkManager /dhclient-c0a3dfde-5c0b-4cef-9c3b-563cfb1fb9d2-eth0.lease -cf /var/lib/NetworkManager/dhclient-eth0.conf eth0 dhclient_start(): running: /sbin/dhclient -d -q -6 -N -sf /usr/lib/NetworkManager/nm-dhcp-helper -pf /run/sendsigs.omit.d /network-manager.dhclient6-eth0.pid -lf /var/lib/NetworkManager/dhclient6-c0a3dfde-5c0b-4cef-9c3b- 563cfb1fb9d2-eth0.lease -cf /var/lib/NetworkManager/dhclient6-eth0.conf eth0 I do not see anything suspicious with the way both dhclients are invoked. Given that a downgrade allows me to obtain an IPv6 address I think this might be a bug in the ISC DHCP client rather than in NetworkManager. To manage notifications about this bug go to: https://bugs.launchpad.net/dhcp/+bug/1447715/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1617338] Re: this cauese my display to freeze and shake every 3seconds or so
sure i'll try it and update you On Thu, Sep 1, 2016 at 8:57 PM, Christopher M. Penalver < christopher.m.penal...@gmail.com> wrote: > X.Prashanth Lidwin Jesuuva, to see if this is already resolved, could > you please test http://cdimage.ubuntu.com/daily-live/current/ and advise > to the results? > > ** Tags added: bios-outdated-f.1a > > ** Description changed: > > - due to some bug in my hardware my display in ubuntu is freezing or > - shaking for a period of every 3 seconds or so i have reinstalled ubuntu > - freshly thrice but the same problem remains > + My display is freezing or shaking for a period of every 3 seconds or so. > + I have reinstalled Ubuntu freshly thrice but the same problem remains. > > - mmy graphics driver is : Atom Processor Z36xxx/Z37xxx Series Graphics & > - Display > + HP 15-d030nr Notebook PC > > ProblemType: Bug > DistroRelease: Ubuntu 14.04 > Package: xorg 1:7.7+1ubuntu8.1 > ProcVersionSignature: Ubuntu 3.13.0-93.140-generic 3.13.11-ckt39 > Uname: Linux 3.13.0-93-generic x86_64 > .tmp.unity.support.test.0: > - > + > ApportVersion: 2.14.1-0ubuntu3.21 > Architecture: amd64 > CompizPlugins: No value set for `/apps/compiz-1/general/ > screen0/options/active_plugins' > CompositorRunning: compiz > CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' > CompositorUnredirectFSW: true > CurrentDesktop: Unity > Date: Fri Aug 26 19:33:59 2016 > DistUpgraded: Fresh install > DistroCodename: trusty > DistroVariant: ubuntu > ExtraDebuggingInterest: I just need to know a workaround > GraphicsCard: > - Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & > Display [8086:0f31] (rev 0a) (prog-if 00 [VGA controller]) > -Subsystem: Hewlett-Packard Company Device [103c:2190] > + Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & > Display [8086:0f31] (rev 0a) (prog-if 00 [VGA controller]) > +Subsystem: Hewlett-Packard Company Device [103c:2190] > InstallationDate: Installed on 2016-08-25 (1 days ago) > InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 > (20140722.2) > Lsusb: > - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub > - Bus 001 Device 004: ID 04f2:b40e Chicony Electronics Co., Ltd HP > Truevision HD camera > - Bus 001 Device 005: ID 0cf3:3121 Atheros Communications, Inc. > - Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub > - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub > + Bus 001 Device 004: ID 04f2:b40e Chicony Electronics Co., Ltd HP > Truevision HD camera > + Bus 001 Device 005: ID 0cf3:3121 Atheros Communications, Inc. > + Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub > + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > MachineType: Hewlett-Packard HP 15 Notebook PC > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-93-generic.efi.signed > root=UUID=e84fe7e4-02c1-4141-a02c-751b41fbb2e2 ro quiet splash > vt.handoff=7 > SourcePackage: xorg > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 11/29/2013 > dmi.bios.vendor: Hewlett-Packard > dmi.bios.version: F.08 > dmi.board.asset.tag: Type2 - Board Asset Tag > dmi.board.name: 2190 > dmi.board.vendor: Hewlett-Packard > dmi.board.version: 40.17 > dmi.chassis.asset.tag: Chassis Asset Tag > dmi.chassis.type: 10 > dmi.chassis.vendor: Hewlett-Packard > dmi.chassis.version: Chassis Version > dmi.modalias: dmi:bvnHewlett-Packard:bvrF.08:bd11/29/2013:svnHewlett- > Packard:pnHP15NotebookPC:pvr097610405F1610180: > rvnHewlett-Packard:rn2190:rvr40.17:cvnHewlett-Packard: > ct10:cvrChassisVersion: > dmi.product.name: HP 15 Notebook PC > dmi.product.version: 097610405F1610180 > dmi.sys.vendor: Hewlett-Packard > version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 > version.ia32-libs: ia32-libs N/A > version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.1 > version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6 > version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A > version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6 > version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev > 1:2.8.2-1ubuntu2 > version.xserver-xorg-video-ati: xserver-xorg-video-ati > 1:7.3.0-1ubuntu3.1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.910-0ubuntu1.6 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau > 1:1.0.10-1ubuntu2 > xserver.bootTime: Fri Aug 26 19:08:38 2016 > xserver.configfile: default > xserver.errors: > - > + > xserver.logfile: /var/log/Xorg.0.log > xserver.outputs: > - product id8428 > - vendor AUO > + product id8428 > + vendor
[Touch-packages] [Bug 1619720] [NEW] Unity8 sometimes reboots after Bluetooth reconnect
Public bug reported: Test case. - In System Settings, pair a Bluetooth keyboard and mouse. - Wait some minutes so keyboard and mouse suspend. - Reboot the device. - Start typing on the password prompt and move the mouse. Expected result. - User can log in. Actual result. - Unity8 crashes. It's not an accurate test case but has happened at least three times in similar scenarios which involve waking up the keyboard (or mouse?). current build number: 180 device name: frieza channel: ubuntu-touch/rc-proposed/bq-aquaris-pd.en With silo 37. ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1619720 Title: Unity8 sometimes reboots after Bluetooth reconnect Status in unity8 package in Ubuntu: New Bug description: Test case. - In System Settings, pair a Bluetooth keyboard and mouse. - Wait some minutes so keyboard and mouse suspend. - Reboot the device. - Start typing on the password prompt and move the mouse. Expected result. - User can log in. Actual result. - Unity8 crashes. It's not an accurate test case but has happened at least three times in similar scenarios which involve waking up the keyboard (or mouse?). current build number: 180 device name: frieza channel: ubuntu-touch/rc-proposed/bq-aquaris-pd.en With silo 37. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1619720/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1619720] Re: Unity8 sometimes reboots after Bluetooth reconnect
I've witnessed this once. I had the OSK showing to type something in an app (forget which). I decided to switch to the bluetooth keyboard, so I turned on the bluetooth keyboard. Once it connected, unity8 crashed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1619720 Title: Unity8 sometimes reboots after Bluetooth reconnect Status in unity8 package in Ubuntu: New Bug description: Test case. - In System Settings, pair a Bluetooth keyboard and mouse. - Wait some minutes so keyboard and mouse suspend. - Reboot the device. - Start typing on the password prompt and move the mouse. Expected result. - User can log in. Actual result. - Unity8 crashes. It's not an accurate test case but has happened at least three times in similar scenarios which involve waking up the keyboard (or mouse?). current build number: 180 device name: frieza channel: ubuntu-touch/rc-proposed/bq-aquaris-pd.en With silo 37. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1619720/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1608131] Re: package keyboard-configuration 1.108ubuntu15.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127
** Changed in: console-setup (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1608131 Title: package keyboard-configuration 1.108ubuntu15.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 Status in console-setup package in Ubuntu: Confirmed Bug description: Generated during apt-get update on Pine64 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: keyboard-configuration 1.108ubuntu15.2 Uname: Linux 3.10.101-4-pine64-longsleep aarch64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: arm64 Date: Sat Jul 30 15:14:14 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 127 PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: console-setup Title: package keyboard-configuration 1.108ubuntu15.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1608131/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1619720] Re: Unity8 sometimes crashes after Bluetooth reconnect
** Summary changed: - Unity8 sometimes reboots after Bluetooth reconnect + Unity8 sometimes crashes after Bluetooth reconnect ** Also affects: canonical-devices-system-image Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1619720 Title: Unity8 sometimes crashes after Bluetooth reconnect Status in Canonical System Image: New Status in unity8 package in Ubuntu: Confirmed Bug description: Test case. - In System Settings, pair a Bluetooth keyboard and mouse. - Wait some minutes so keyboard and mouse suspend. - Reboot the device. - Start typing on the password prompt and move the mouse. Expected result. - User can log in. Actual result. - Unity8 crashes. It's not an accurate test case but has happened at least three times in similar scenarios which involve waking up the keyboard (or mouse?). current build number: 180 device name: frieza channel: ubuntu-touch/rc-proposed/bq-aquaris-pd.en With silo 37. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1619720/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1580537] Re: LibreOffice with ambiance theme and breeze icon style is unusable
This is the vendor patch for LibreOffice on yakkety to make this work with the (patched) theme on gtk-3.20: https://git.launchpad.net/~libreoffice/ubuntu/+source/libreoffice/tree/patches/gtk3-toolbar-styleclass.diff?h=ubuntu-yakkety-5.2&id=93bf8e2da6110a244007208d56b89c31ef5fb1ad The theme needs the patching as per libreoffice-toolbars-320 branch linked to this issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1580537 Title: LibreOffice with ambiance theme and breeze icon style is unusable Status in libreoffice package in Ubuntu: Fix Committed Status in ubuntu-themes package in Ubuntu: Fix Committed Bug description: Until today i didn't use LibreOffice on Ubuntu 16.04. I opened it today and i see menu/icon bar totally unusable with Ambiance theme and default Breeze style. (image attached) The version installed is 5.1.2-0ubuntu1. I did upgrade from 14.04 to 16.04 with some issues. Changing from Breeze to Human is usable but fugly. No issue with Radiance theme. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1580537/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1580537] Re: LibreOffice with ambiance theme and breeze icon style is unusable
The patched LibreOffice and patched ubuntu-themes can be tested together on Yakkety by installing from this ppa: https://launchpad.net/~libreoffice/+archive/ubuntu/ppa ** Changed in: libreoffice (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1580537 Title: LibreOffice with ambiance theme and breeze icon style is unusable Status in libreoffice package in Ubuntu: Fix Committed Status in ubuntu-themes package in Ubuntu: Fix Committed Bug description: Until today i didn't use LibreOffice on Ubuntu 16.04. I opened it today and i see menu/icon bar totally unusable with Ambiance theme and default Breeze style. (image attached) The version installed is 5.1.2-0ubuntu1. I did upgrade from 14.04 to 16.04 with some issues. Changing from Breeze to Human is usable but fugly. No issue with Radiance theme. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1580537/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1619720] Re: Unity8 sometimes crashes after Bluetooth reconnect
I just reflashed my frieza to build 180 and witnessed a Unity 8 crash when my BT mouse try connecting. The system did not reboot however. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1619720 Title: Unity8 sometimes crashes after Bluetooth reconnect Status in Canonical System Image: New Status in unity8 package in Ubuntu: Confirmed Bug description: Test case. - In System Settings, pair a Bluetooth keyboard and mouse. - Wait some minutes so keyboard and mouse suspend. - Reboot the device. - Start typing on the password prompt and move the mouse. Expected result. - User can log in. Actual result. - Unity8 crashes. It's not an accurate test case but has happened at least three times in similar scenarios which involve waking up the keyboard (or mouse?). current build number: 180 device name: frieza channel: ubuntu-touch/rc-proposed/bq-aquaris-pd.en With silo 37. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1619720/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1615864] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1615864/+attachment/4733050/+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/1615864 Title: Screen resolution not saved after reboot or logout and back in Status in xorg package in Ubuntu: Incomplete Bug description: Hello, I am having an issue with my screen resolution of 1920x1080. I am using a Vizio 42 inch TV which worked fine with the HDMI connection from the computer to the TV. Every time I boot the computer up I have to go into terminal and type " xrandr -s 1920x1080 " One of the first things I did was go to the System Settings > Software & Updates > Additional Drivers and then select Nividia 304.131 (proprietary,tested). I do this since when Nouveau was first introduced, it never worked with my graphics chipset which is a Nividia 7050. Yes, the chipset is old but worked fine until 16.04. I spent the weekend trying all suggestions that I could find via the search engines along with the help of a few folks on the #ubuntu IRC. Three days later, still no luck and still having to type the xrandr line in the terminal. I even tried adding the xrandr line in /etc/lightdm/lightdm.conf, That was a disaster at bootup. luckily I was able to get to the terminal and Nano edit the file and reboot. In addition, probably unrelated to this issue, I have also noticed when running any streaming video, now it is almost like watching a slide show. Nothing has changed Internet connection or hardware since the install of 16.04. Even typing this is lagged by 1 to 3 seconds per character typed. Same issue in Firefox or Chrome. But sorry, I digress. This can be looked at in another post, forum or possible bug. The main issue is that Ubuntu 16.04 does not save and or reads the saved settings of 1920x1080 with out the later use via the terminal using xrandr. I did take notice that when booting into the main desktop the mouse pointer is small as if in 1920x1080 but then changes to a larger pointer then the resolution is then 1280x720 which seems to what 16.04 falls back to. The TV reports the proper information under xrandr. gee@HTPC:~$ xrandr Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 4096 x 4096 VGA-0 disconnected (normal left inverted right x axis y axis) TV-0 disconnected (normal left inverted right x axis y axis) HDMI-0 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 980mm x 580mm 1280x720 60.00 + 59.94 1920x1080 59.9459.94* 60.0560.0050.04 720x576 50.0050.08 720x480 59.94 640x480 59.93 gee@HTPC:~$ uname-a Linux HTPC 4.4.0-34-generic #53-Ubuntu SMP Wed Jul 27 16:06:39 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux This will be the only information I will post this way since it was quite short. I will attach my latest xorg.conf file and also post the pastebin URL to it if the attachment fails. http://pastebin.com/zmcuUJxQ Thank you for your time GEE --- .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: u'/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.131 Sun Nov 8 21:43:33 PST 2015 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME-Flashback:Unity DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.131, 4.4.0-34-generic, x86_64: installed nvidia-304, 304.131, 4.4.0-36-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation C68 [GeForce 7050 PV / nForce 630a] [10de:053a] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] C68 [GeForce 7050 PV / nForce 630a] [1462:349f] InstallationDate: Installed on 2016-08-20 (12 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 002: ID 099a:7202 Zippy Technology Corp. Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: MSI MS-7349 NonfreeKernelModules: nvidia Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic r
[Touch-packages] [Bug 1619720] Re: Unity8 sometimes crashes after Bluetooth reconnect
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity8 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1619720 Title: Unity8 sometimes crashes after Bluetooth reconnect Status in Canonical System Image: New Status in unity8 package in Ubuntu: Confirmed Bug description: Test case. - In System Settings, pair a Bluetooth keyboard and mouse. - Wait some minutes so keyboard and mouse suspend. - Reboot the device. - Start typing on the password prompt and move the mouse. Expected result. - User can log in. Actual result. - Unity8 crashes. It's not an accurate test case but has happened at least three times in similar scenarios which involve waking up the keyboard (or mouse?). current build number: 180 device name: frieza channel: ubuntu-touch/rc-proposed/bq-aquaris-pd.en With silo 37. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1619720/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1615864] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1615864/+attachment/4733049/+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/1615864 Title: Screen resolution not saved after reboot or logout and back in Status in xorg package in Ubuntu: Incomplete Bug description: Hello, I am having an issue with my screen resolution of 1920x1080. I am using a Vizio 42 inch TV which worked fine with the HDMI connection from the computer to the TV. Every time I boot the computer up I have to go into terminal and type " xrandr -s 1920x1080 " One of the first things I did was go to the System Settings > Software & Updates > Additional Drivers and then select Nividia 304.131 (proprietary,tested). I do this since when Nouveau was first introduced, it never worked with my graphics chipset which is a Nividia 7050. Yes, the chipset is old but worked fine until 16.04. I spent the weekend trying all suggestions that I could find via the search engines along with the help of a few folks on the #ubuntu IRC. Three days later, still no luck and still having to type the xrandr line in the terminal. I even tried adding the xrandr line in /etc/lightdm/lightdm.conf, That was a disaster at bootup. luckily I was able to get to the terminal and Nano edit the file and reboot. In addition, probably unrelated to this issue, I have also noticed when running any streaming video, now it is almost like watching a slide show. Nothing has changed Internet connection or hardware since the install of 16.04. Even typing this is lagged by 1 to 3 seconds per character typed. Same issue in Firefox or Chrome. But sorry, I digress. This can be looked at in another post, forum or possible bug. The main issue is that Ubuntu 16.04 does not save and or reads the saved settings of 1920x1080 with out the later use via the terminal using xrandr. I did take notice that when booting into the main desktop the mouse pointer is small as if in 1920x1080 but then changes to a larger pointer then the resolution is then 1280x720 which seems to what 16.04 falls back to. The TV reports the proper information under xrandr. gee@HTPC:~$ xrandr Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 4096 x 4096 VGA-0 disconnected (normal left inverted right x axis y axis) TV-0 disconnected (normal left inverted right x axis y axis) HDMI-0 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 980mm x 580mm 1280x720 60.00 + 59.94 1920x1080 59.9459.94* 60.0560.0050.04 720x576 50.0050.08 720x480 59.94 640x480 59.93 gee@HTPC:~$ uname-a Linux HTPC 4.4.0-34-generic #53-Ubuntu SMP Wed Jul 27 16:06:39 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux This will be the only information I will post this way since it was quite short. I will attach my latest xorg.conf file and also post the pastebin URL to it if the attachment fails. http://pastebin.com/zmcuUJxQ Thank you for your time GEE --- .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: u'/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.131 Sun Nov 8 21:43:33 PST 2015 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME-Flashback:Unity DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.131, 4.4.0-34-generic, x86_64: installed nvidia-304, 304.131, 4.4.0-36-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation C68 [GeForce 7050 PV / nForce 630a] [10de:053a] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] C68 [GeForce 7050 PV / nForce 630a] [1462:349f] InstallationDate: Installed on 2016-08-20 (12 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 002: ID 099a:7202 Zippy Technology Corp. Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: MSI MS-7349 NonfreeKernelModules: nvidia Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic r
[Touch-packages] [Bug 1615864] NvidiaBugReportLog.txt
apport information ** Attachment added: "NvidiaBugReportLog.txt" https://bugs.launchpad.net/bugs/1615864/+attachment/4733055/+files/NvidiaBugReportLog.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/1615864 Title: Screen resolution not saved after reboot or logout and back in Status in xorg package in Ubuntu: Incomplete Bug description: Hello, I am having an issue with my screen resolution of 1920x1080. I am using a Vizio 42 inch TV which worked fine with the HDMI connection from the computer to the TV. Every time I boot the computer up I have to go into terminal and type " xrandr -s 1920x1080 " One of the first things I did was go to the System Settings > Software & Updates > Additional Drivers and then select Nividia 304.131 (proprietary,tested). I do this since when Nouveau was first introduced, it never worked with my graphics chipset which is a Nividia 7050. Yes, the chipset is old but worked fine until 16.04. I spent the weekend trying all suggestions that I could find via the search engines along with the help of a few folks on the #ubuntu IRC. Three days later, still no luck and still having to type the xrandr line in the terminal. I even tried adding the xrandr line in /etc/lightdm/lightdm.conf, That was a disaster at bootup. luckily I was able to get to the terminal and Nano edit the file and reboot. In addition, probably unrelated to this issue, I have also noticed when running any streaming video, now it is almost like watching a slide show. Nothing has changed Internet connection or hardware since the install of 16.04. Even typing this is lagged by 1 to 3 seconds per character typed. Same issue in Firefox or Chrome. But sorry, I digress. This can be looked at in another post, forum or possible bug. The main issue is that Ubuntu 16.04 does not save and or reads the saved settings of 1920x1080 with out the later use via the terminal using xrandr. I did take notice that when booting into the main desktop the mouse pointer is small as if in 1920x1080 but then changes to a larger pointer then the resolution is then 1280x720 which seems to what 16.04 falls back to. The TV reports the proper information under xrandr. gee@HTPC:~$ xrandr Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 4096 x 4096 VGA-0 disconnected (normal left inverted right x axis y axis) TV-0 disconnected (normal left inverted right x axis y axis) HDMI-0 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 980mm x 580mm 1280x720 60.00 + 59.94 1920x1080 59.9459.94* 60.0560.0050.04 720x576 50.0050.08 720x480 59.94 640x480 59.93 gee@HTPC:~$ uname-a Linux HTPC 4.4.0-34-generic #53-Ubuntu SMP Wed Jul 27 16:06:39 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux This will be the only information I will post this way since it was quite short. I will attach my latest xorg.conf file and also post the pastebin URL to it if the attachment fails. http://pastebin.com/zmcuUJxQ Thank you for your time GEE --- .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: u'/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.131 Sun Nov 8 21:43:33 PST 2015 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME-Flashback:Unity DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.131, 4.4.0-34-generic, x86_64: installed nvidia-304, 304.131, 4.4.0-36-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation C68 [GeForce 7050 PV / nForce 630a] [10de:053a] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] C68 [GeForce 7050 PV / nForce 630a] [1462:349f] InstallationDate: Installed on 2016-08-20 (12 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 002: ID 099a:7202 Zippy Technology Corp. Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: MSI MS-7349 NonfreeKernelModules: nvidia Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-3
[Touch-packages] [Bug 1615864] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1615864/+attachment/4733056/+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/1615864 Title: Screen resolution not saved after reboot or logout and back in Status in xorg package in Ubuntu: Incomplete Bug description: Hello, I am having an issue with my screen resolution of 1920x1080. I am using a Vizio 42 inch TV which worked fine with the HDMI connection from the computer to the TV. Every time I boot the computer up I have to go into terminal and type " xrandr -s 1920x1080 " One of the first things I did was go to the System Settings > Software & Updates > Additional Drivers and then select Nividia 304.131 (proprietary,tested). I do this since when Nouveau was first introduced, it never worked with my graphics chipset which is a Nividia 7050. Yes, the chipset is old but worked fine until 16.04. I spent the weekend trying all suggestions that I could find via the search engines along with the help of a few folks on the #ubuntu IRC. Three days later, still no luck and still having to type the xrandr line in the terminal. I even tried adding the xrandr line in /etc/lightdm/lightdm.conf, That was a disaster at bootup. luckily I was able to get to the terminal and Nano edit the file and reboot. In addition, probably unrelated to this issue, I have also noticed when running any streaming video, now it is almost like watching a slide show. Nothing has changed Internet connection or hardware since the install of 16.04. Even typing this is lagged by 1 to 3 seconds per character typed. Same issue in Firefox or Chrome. But sorry, I digress. This can be looked at in another post, forum or possible bug. The main issue is that Ubuntu 16.04 does not save and or reads the saved settings of 1920x1080 with out the later use via the terminal using xrandr. I did take notice that when booting into the main desktop the mouse pointer is small as if in 1920x1080 but then changes to a larger pointer then the resolution is then 1280x720 which seems to what 16.04 falls back to. The TV reports the proper information under xrandr. gee@HTPC:~$ xrandr Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 4096 x 4096 VGA-0 disconnected (normal left inverted right x axis y axis) TV-0 disconnected (normal left inverted right x axis y axis) HDMI-0 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 980mm x 580mm 1280x720 60.00 + 59.94 1920x1080 59.9459.94* 60.0560.0050.04 720x576 50.0050.08 720x480 59.94 640x480 59.93 gee@HTPC:~$ uname-a Linux HTPC 4.4.0-34-generic #53-Ubuntu SMP Wed Jul 27 16:06:39 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux This will be the only information I will post this way since it was quite short. I will attach my latest xorg.conf file and also post the pastebin URL to it if the attachment fails. http://pastebin.com/zmcuUJxQ Thank you for your time GEE --- .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: u'/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.131 Sun Nov 8 21:43:33 PST 2015 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME-Flashback:Unity DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.131, 4.4.0-34-generic, x86_64: installed nvidia-304, 304.131, 4.4.0-36-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation C68 [GeForce 7050 PV / nForce 630a] [10de:053a] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] C68 [GeForce 7050 PV / nForce 630a] [1462:349f] InstallationDate: Installed on 2016-08-20 (12 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 002: ID 099a:7202 Zippy Technology Corp. Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: MSI MS-7349 NonfreeKernelModules: nvidia Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic roo
[Touch-packages] [Bug 1615864] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1615864/+attachment/4733058/+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/1615864 Title: Screen resolution not saved after reboot or logout and back in Status in xorg package in Ubuntu: Incomplete Bug description: Hello, I am having an issue with my screen resolution of 1920x1080. I am using a Vizio 42 inch TV which worked fine with the HDMI connection from the computer to the TV. Every time I boot the computer up I have to go into terminal and type " xrandr -s 1920x1080 " One of the first things I did was go to the System Settings > Software & Updates > Additional Drivers and then select Nividia 304.131 (proprietary,tested). I do this since when Nouveau was first introduced, it never worked with my graphics chipset which is a Nividia 7050. Yes, the chipset is old but worked fine until 16.04. I spent the weekend trying all suggestions that I could find via the search engines along with the help of a few folks on the #ubuntu IRC. Three days later, still no luck and still having to type the xrandr line in the terminal. I even tried adding the xrandr line in /etc/lightdm/lightdm.conf, That was a disaster at bootup. luckily I was able to get to the terminal and Nano edit the file and reboot. In addition, probably unrelated to this issue, I have also noticed when running any streaming video, now it is almost like watching a slide show. Nothing has changed Internet connection or hardware since the install of 16.04. Even typing this is lagged by 1 to 3 seconds per character typed. Same issue in Firefox or Chrome. But sorry, I digress. This can be looked at in another post, forum or possible bug. The main issue is that Ubuntu 16.04 does not save and or reads the saved settings of 1920x1080 with out the later use via the terminal using xrandr. I did take notice that when booting into the main desktop the mouse pointer is small as if in 1920x1080 but then changes to a larger pointer then the resolution is then 1280x720 which seems to what 16.04 falls back to. The TV reports the proper information under xrandr. gee@HTPC:~$ xrandr Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 4096 x 4096 VGA-0 disconnected (normal left inverted right x axis y axis) TV-0 disconnected (normal left inverted right x axis y axis) HDMI-0 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 980mm x 580mm 1280x720 60.00 + 59.94 1920x1080 59.9459.94* 60.0560.0050.04 720x576 50.0050.08 720x480 59.94 640x480 59.93 gee@HTPC:~$ uname-a Linux HTPC 4.4.0-34-generic #53-Ubuntu SMP Wed Jul 27 16:06:39 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux This will be the only information I will post this way since it was quite short. I will attach my latest xorg.conf file and also post the pastebin URL to it if the attachment fails. http://pastebin.com/zmcuUJxQ Thank you for your time GEE --- .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: u'/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.131 Sun Nov 8 21:43:33 PST 2015 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME-Flashback:Unity DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.131, 4.4.0-34-generic, x86_64: installed nvidia-304, 304.131, 4.4.0-36-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation C68 [GeForce 7050 PV / nForce 630a] [10de:053a] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] C68 [GeForce 7050 PV / nForce 630a] [1462:349f] InstallationDate: Installed on 2016-08-20 (12 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 002: ID 099a:7202 Zippy Technology Corp. Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: MSI MS-7349 NonfreeKernelModules: nvidia Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generi
[Touch-packages] [Bug 1615864] XorgConf.txt
apport information ** Attachment added: "XorgConf.txt" https://bugs.launchpad.net/bugs/1615864/+attachment/4733062/+files/XorgConf.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/1615864 Title: Screen resolution not saved after reboot or logout and back in Status in xorg package in Ubuntu: Incomplete Bug description: Hello, I am having an issue with my screen resolution of 1920x1080. I am using a Vizio 42 inch TV which worked fine with the HDMI connection from the computer to the TV. Every time I boot the computer up I have to go into terminal and type " xrandr -s 1920x1080 " One of the first things I did was go to the System Settings > Software & Updates > Additional Drivers and then select Nividia 304.131 (proprietary,tested). I do this since when Nouveau was first introduced, it never worked with my graphics chipset which is a Nividia 7050. Yes, the chipset is old but worked fine until 16.04. I spent the weekend trying all suggestions that I could find via the search engines along with the help of a few folks on the #ubuntu IRC. Three days later, still no luck and still having to type the xrandr line in the terminal. I even tried adding the xrandr line in /etc/lightdm/lightdm.conf, That was a disaster at bootup. luckily I was able to get to the terminal and Nano edit the file and reboot. In addition, probably unrelated to this issue, I have also noticed when running any streaming video, now it is almost like watching a slide show. Nothing has changed Internet connection or hardware since the install of 16.04. Even typing this is lagged by 1 to 3 seconds per character typed. Same issue in Firefox or Chrome. But sorry, I digress. This can be looked at in another post, forum or possible bug. The main issue is that Ubuntu 16.04 does not save and or reads the saved settings of 1920x1080 with out the later use via the terminal using xrandr. I did take notice that when booting into the main desktop the mouse pointer is small as if in 1920x1080 but then changes to a larger pointer then the resolution is then 1280x720 which seems to what 16.04 falls back to. The TV reports the proper information under xrandr. gee@HTPC:~$ xrandr Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 4096 x 4096 VGA-0 disconnected (normal left inverted right x axis y axis) TV-0 disconnected (normal left inverted right x axis y axis) HDMI-0 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 980mm x 580mm 1280x720 60.00 + 59.94 1920x1080 59.9459.94* 60.0560.0050.04 720x576 50.0050.08 720x480 59.94 640x480 59.93 gee@HTPC:~$ uname-a Linux HTPC 4.4.0-34-generic #53-Ubuntu SMP Wed Jul 27 16:06:39 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux This will be the only information I will post this way since it was quite short. I will attach my latest xorg.conf file and also post the pastebin URL to it if the attachment fails. http://pastebin.com/zmcuUJxQ Thank you for your time GEE --- .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: u'/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.131 Sun Nov 8 21:43:33 PST 2015 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME-Flashback:Unity DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.131, 4.4.0-34-generic, x86_64: installed nvidia-304, 304.131, 4.4.0-36-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation C68 [GeForce 7050 PV / nForce 630a] [10de:053a] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] C68 [GeForce 7050 PV / nForce 630a] [1462:349f] InstallationDate: Installed on 2016-08-20 (12 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 002: ID 099a:7202 Zippy Technology Corp. Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: MSI MS-7349 NonfreeKernelModules: nvidia Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic root=UUID
[Touch-packages] [Bug 1615864] nvidia-settings.txt
apport information ** Attachment added: "nvidia-settings.txt" https://bugs.launchpad.net/bugs/1615864/+attachment/4733066/+files/nvidia-settings.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/1615864 Title: Screen resolution not saved after reboot or logout and back in Status in xorg package in Ubuntu: Incomplete Bug description: Hello, I am having an issue with my screen resolution of 1920x1080. I am using a Vizio 42 inch TV which worked fine with the HDMI connection from the computer to the TV. Every time I boot the computer up I have to go into terminal and type " xrandr -s 1920x1080 " One of the first things I did was go to the System Settings > Software & Updates > Additional Drivers and then select Nividia 304.131 (proprietary,tested). I do this since when Nouveau was first introduced, it never worked with my graphics chipset which is a Nividia 7050. Yes, the chipset is old but worked fine until 16.04. I spent the weekend trying all suggestions that I could find via the search engines along with the help of a few folks on the #ubuntu IRC. Three days later, still no luck and still having to type the xrandr line in the terminal. I even tried adding the xrandr line in /etc/lightdm/lightdm.conf, That was a disaster at bootup. luckily I was able to get to the terminal and Nano edit the file and reboot. In addition, probably unrelated to this issue, I have also noticed when running any streaming video, now it is almost like watching a slide show. Nothing has changed Internet connection or hardware since the install of 16.04. Even typing this is lagged by 1 to 3 seconds per character typed. Same issue in Firefox or Chrome. But sorry, I digress. This can be looked at in another post, forum or possible bug. The main issue is that Ubuntu 16.04 does not save and or reads the saved settings of 1920x1080 with out the later use via the terminal using xrandr. I did take notice that when booting into the main desktop the mouse pointer is small as if in 1920x1080 but then changes to a larger pointer then the resolution is then 1280x720 which seems to what 16.04 falls back to. The TV reports the proper information under xrandr. gee@HTPC:~$ xrandr Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 4096 x 4096 VGA-0 disconnected (normal left inverted right x axis y axis) TV-0 disconnected (normal left inverted right x axis y axis) HDMI-0 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 980mm x 580mm 1280x720 60.00 + 59.94 1920x1080 59.9459.94* 60.0560.0050.04 720x576 50.0050.08 720x480 59.94 640x480 59.93 gee@HTPC:~$ uname-a Linux HTPC 4.4.0-34-generic #53-Ubuntu SMP Wed Jul 27 16:06:39 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux This will be the only information I will post this way since it was quite short. I will attach my latest xorg.conf file and also post the pastebin URL to it if the attachment fails. http://pastebin.com/zmcuUJxQ Thank you for your time GEE --- .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: u'/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.131 Sun Nov 8 21:43:33 PST 2015 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME-Flashback:Unity DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.131, 4.4.0-34-generic, x86_64: installed nvidia-304, 304.131, 4.4.0-36-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation C68 [GeForce 7050 PV / nForce 630a] [10de:053a] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] C68 [GeForce 7050 PV / nForce 630a] [1462:349f] InstallationDate: Installed on 2016-08-20 (12 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 002: ID 099a:7202 Zippy Technology Corp. Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: MSI MS-7349 NonfreeKernelModules: nvidia Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-gene
[Touch-packages] [Bug 1615864] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1615864/+attachment/4733060/+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/1615864 Title: Screen resolution not saved after reboot or logout and back in Status in xorg package in Ubuntu: Incomplete Bug description: Hello, I am having an issue with my screen resolution of 1920x1080. I am using a Vizio 42 inch TV which worked fine with the HDMI connection from the computer to the TV. Every time I boot the computer up I have to go into terminal and type " xrandr -s 1920x1080 " One of the first things I did was go to the System Settings > Software & Updates > Additional Drivers and then select Nividia 304.131 (proprietary,tested). I do this since when Nouveau was first introduced, it never worked with my graphics chipset which is a Nividia 7050. Yes, the chipset is old but worked fine until 16.04. I spent the weekend trying all suggestions that I could find via the search engines along with the help of a few folks on the #ubuntu IRC. Three days later, still no luck and still having to type the xrandr line in the terminal. I even tried adding the xrandr line in /etc/lightdm/lightdm.conf, That was a disaster at bootup. luckily I was able to get to the terminal and Nano edit the file and reboot. In addition, probably unrelated to this issue, I have also noticed when running any streaming video, now it is almost like watching a slide show. Nothing has changed Internet connection or hardware since the install of 16.04. Even typing this is lagged by 1 to 3 seconds per character typed. Same issue in Firefox or Chrome. But sorry, I digress. This can be looked at in another post, forum or possible bug. The main issue is that Ubuntu 16.04 does not save and or reads the saved settings of 1920x1080 with out the later use via the terminal using xrandr. I did take notice that when booting into the main desktop the mouse pointer is small as if in 1920x1080 but then changes to a larger pointer then the resolution is then 1280x720 which seems to what 16.04 falls back to. The TV reports the proper information under xrandr. gee@HTPC:~$ xrandr Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 4096 x 4096 VGA-0 disconnected (normal left inverted right x axis y axis) TV-0 disconnected (normal left inverted right x axis y axis) HDMI-0 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 980mm x 580mm 1280x720 60.00 + 59.94 1920x1080 59.9459.94* 60.0560.0050.04 720x576 50.0050.08 720x480 59.94 640x480 59.93 gee@HTPC:~$ uname-a Linux HTPC 4.4.0-34-generic #53-Ubuntu SMP Wed Jul 27 16:06:39 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux This will be the only information I will post this way since it was quite short. I will attach my latest xorg.conf file and also post the pastebin URL to it if the attachment fails. http://pastebin.com/zmcuUJxQ Thank you for your time GEE --- .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: u'/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.131 Sun Nov 8 21:43:33 PST 2015 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME-Flashback:Unity DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.131, 4.4.0-34-generic, x86_64: installed nvidia-304, 304.131, 4.4.0-36-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation C68 [GeForce 7050 PV / nForce 630a] [10de:053a] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] C68 [GeForce 7050 PV / nForce 630a] [1462:349f] InstallationDate: Installed on 2016-08-20 (12 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 002: ID 099a:7202 Zippy Technology Corp. Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: MSI MS-7349 NonfreeKernelModules: nvidia Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic root=UUID=3779
[Touch-packages] [Bug 1615864] Re: Screen resolution not saved after reboot or logout and back in
Hello, Sorry I did not grab the information via apport in the first place. I hope this was supposed to log everything this way? I thought it would place it in Ubuntu.pastebin. It ended up being automatically generated here. -- 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/1615864 Title: Screen resolution not saved after reboot or logout and back in Status in xorg package in Ubuntu: Incomplete Bug description: Hello, I am having an issue with my screen resolution of 1920x1080. I am using a Vizio 42 inch TV which worked fine with the HDMI connection from the computer to the TV. Every time I boot the computer up I have to go into terminal and type " xrandr -s 1920x1080 " One of the first things I did was go to the System Settings > Software & Updates > Additional Drivers and then select Nividia 304.131 (proprietary,tested). I do this since when Nouveau was first introduced, it never worked with my graphics chipset which is a Nividia 7050. Yes, the chipset is old but worked fine until 16.04. I spent the weekend trying all suggestions that I could find via the search engines along with the help of a few folks on the #ubuntu IRC. Three days later, still no luck and still having to type the xrandr line in the terminal. I even tried adding the xrandr line in /etc/lightdm/lightdm.conf, That was a disaster at bootup. luckily I was able to get to the terminal and Nano edit the file and reboot. In addition, probably unrelated to this issue, I have also noticed when running any streaming video, now it is almost like watching a slide show. Nothing has changed Internet connection or hardware since the install of 16.04. Even typing this is lagged by 1 to 3 seconds per character typed. Same issue in Firefox or Chrome. But sorry, I digress. This can be looked at in another post, forum or possible bug. The main issue is that Ubuntu 16.04 does not save and or reads the saved settings of 1920x1080 with out the later use via the terminal using xrandr. I did take notice that when booting into the main desktop the mouse pointer is small as if in 1920x1080 but then changes to a larger pointer then the resolution is then 1280x720 which seems to what 16.04 falls back to. The TV reports the proper information under xrandr. gee@HTPC:~$ xrandr Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 4096 x 4096 VGA-0 disconnected (normal left inverted right x axis y axis) TV-0 disconnected (normal left inverted right x axis y axis) HDMI-0 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 980mm x 580mm 1280x720 60.00 + 59.94 1920x1080 59.9459.94* 60.0560.0050.04 720x576 50.0050.08 720x480 59.94 640x480 59.93 gee@HTPC:~$ uname-a Linux HTPC 4.4.0-34-generic #53-Ubuntu SMP Wed Jul 27 16:06:39 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux This will be the only information I will post this way since it was quite short. I will attach my latest xorg.conf file and also post the pastebin URL to it if the attachment fails. http://pastebin.com/zmcuUJxQ Thank you for your time GEE --- .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: u'/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.131 Sun Nov 8 21:43:33 PST 2015 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME-Flashback:Unity DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.131, 4.4.0-34-generic, x86_64: installed nvidia-304, 304.131, 4.4.0-36-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation C68 [GeForce 7050 PV / nForce 630a] [10de:053a] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] C68 [GeForce 7050 PV / nForce 630a] [1462:349f] InstallationDate: Installed on 2016-08-20 (12 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 002: ID 099a:7202 Zippy Technology Corp. Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: MSI MS-7349 NonfreeKernelModules: nvidia Package: xorg 1:7.7+13ubuntu3 PackageArchit
[Touch-packages] [Bug 1615864] XorgLogOld.txt
apport information ** Attachment added: "XorgLogOld.txt" https://bugs.launchpad.net/bugs/1615864/+attachment/4733064/+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/1615864 Title: Screen resolution not saved after reboot or logout and back in Status in xorg package in Ubuntu: Incomplete Bug description: Hello, I am having an issue with my screen resolution of 1920x1080. I am using a Vizio 42 inch TV which worked fine with the HDMI connection from the computer to the TV. Every time I boot the computer up I have to go into terminal and type " xrandr -s 1920x1080 " One of the first things I did was go to the System Settings > Software & Updates > Additional Drivers and then select Nividia 304.131 (proprietary,tested). I do this since when Nouveau was first introduced, it never worked with my graphics chipset which is a Nividia 7050. Yes, the chipset is old but worked fine until 16.04. I spent the weekend trying all suggestions that I could find via the search engines along with the help of a few folks on the #ubuntu IRC. Three days later, still no luck and still having to type the xrandr line in the terminal. I even tried adding the xrandr line in /etc/lightdm/lightdm.conf, That was a disaster at bootup. luckily I was able to get to the terminal and Nano edit the file and reboot. In addition, probably unrelated to this issue, I have also noticed when running any streaming video, now it is almost like watching a slide show. Nothing has changed Internet connection or hardware since the install of 16.04. Even typing this is lagged by 1 to 3 seconds per character typed. Same issue in Firefox or Chrome. But sorry, I digress. This can be looked at in another post, forum or possible bug. The main issue is that Ubuntu 16.04 does not save and or reads the saved settings of 1920x1080 with out the later use via the terminal using xrandr. I did take notice that when booting into the main desktop the mouse pointer is small as if in 1920x1080 but then changes to a larger pointer then the resolution is then 1280x720 which seems to what 16.04 falls back to. The TV reports the proper information under xrandr. gee@HTPC:~$ xrandr Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 4096 x 4096 VGA-0 disconnected (normal left inverted right x axis y axis) TV-0 disconnected (normal left inverted right x axis y axis) HDMI-0 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 980mm x 580mm 1280x720 60.00 + 59.94 1920x1080 59.9459.94* 60.0560.0050.04 720x576 50.0050.08 720x480 59.94 640x480 59.93 gee@HTPC:~$ uname-a Linux HTPC 4.4.0-34-generic #53-Ubuntu SMP Wed Jul 27 16:06:39 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux This will be the only information I will post this way since it was quite short. I will attach my latest xorg.conf file and also post the pastebin URL to it if the attachment fails. http://pastebin.com/zmcuUJxQ Thank you for your time GEE --- .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: u'/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.131 Sun Nov 8 21:43:33 PST 2015 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME-Flashback:Unity DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.131, 4.4.0-34-generic, x86_64: installed nvidia-304, 304.131, 4.4.0-36-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation C68 [GeForce 7050 PV / nForce 630a] [10de:053a] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] C68 [GeForce 7050 PV / nForce 630a] [1462:349f] InstallationDate: Installed on 2016-08-20 (12 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 002: ID 099a:7202 Zippy Technology Corp. Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: MSI MS-7349 NonfreeKernelModules: nvidia Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic root=
[Touch-packages] [Bug 1615864] Xrandr.txt
apport information ** Attachment added: "Xrandr.txt" https://bugs.launchpad.net/bugs/1615864/+attachment/4733065/+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/1615864 Title: Screen resolution not saved after reboot or logout and back in Status in xorg package in Ubuntu: Incomplete Bug description: Hello, I am having an issue with my screen resolution of 1920x1080. I am using a Vizio 42 inch TV which worked fine with the HDMI connection from the computer to the TV. Every time I boot the computer up I have to go into terminal and type " xrandr -s 1920x1080 " One of the first things I did was go to the System Settings > Software & Updates > Additional Drivers and then select Nividia 304.131 (proprietary,tested). I do this since when Nouveau was first introduced, it never worked with my graphics chipset which is a Nividia 7050. Yes, the chipset is old but worked fine until 16.04. I spent the weekend trying all suggestions that I could find via the search engines along with the help of a few folks on the #ubuntu IRC. Three days later, still no luck and still having to type the xrandr line in the terminal. I even tried adding the xrandr line in /etc/lightdm/lightdm.conf, That was a disaster at bootup. luckily I was able to get to the terminal and Nano edit the file and reboot. In addition, probably unrelated to this issue, I have also noticed when running any streaming video, now it is almost like watching a slide show. Nothing has changed Internet connection or hardware since the install of 16.04. Even typing this is lagged by 1 to 3 seconds per character typed. Same issue in Firefox or Chrome. But sorry, I digress. This can be looked at in another post, forum or possible bug. The main issue is that Ubuntu 16.04 does not save and or reads the saved settings of 1920x1080 with out the later use via the terminal using xrandr. I did take notice that when booting into the main desktop the mouse pointer is small as if in 1920x1080 but then changes to a larger pointer then the resolution is then 1280x720 which seems to what 16.04 falls back to. The TV reports the proper information under xrandr. gee@HTPC:~$ xrandr Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 4096 x 4096 VGA-0 disconnected (normal left inverted right x axis y axis) TV-0 disconnected (normal left inverted right x axis y axis) HDMI-0 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 980mm x 580mm 1280x720 60.00 + 59.94 1920x1080 59.9459.94* 60.0560.0050.04 720x576 50.0050.08 720x480 59.94 640x480 59.93 gee@HTPC:~$ uname-a Linux HTPC 4.4.0-34-generic #53-Ubuntu SMP Wed Jul 27 16:06:39 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux This will be the only information I will post this way since it was quite short. I will attach my latest xorg.conf file and also post the pastebin URL to it if the attachment fails. http://pastebin.com/zmcuUJxQ Thank you for your time GEE --- .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: u'/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.131 Sun Nov 8 21:43:33 PST 2015 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME-Flashback:Unity DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.131, 4.4.0-34-generic, x86_64: installed nvidia-304, 304.131, 4.4.0-36-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation C68 [GeForce 7050 PV / nForce 630a] [10de:053a] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] C68 [GeForce 7050 PV / nForce 630a] [1462:349f] InstallationDate: Installed on 2016-08-20 (12 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 002: ID 099a:7202 Zippy Technology Corp. Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: MSI MS-7349 NonfreeKernelModules: nvidia Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic root=UUID=3779
[Touch-packages] [Bug 1615864] xdpyinfo.txt
apport information ** Attachment added: "xdpyinfo.txt" https://bugs.launchpad.net/bugs/1615864/+attachment/4733067/+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/1615864 Title: Screen resolution not saved after reboot or logout and back in Status in xorg package in Ubuntu: Incomplete Bug description: Hello, I am having an issue with my screen resolution of 1920x1080. I am using a Vizio 42 inch TV which worked fine with the HDMI connection from the computer to the TV. Every time I boot the computer up I have to go into terminal and type " xrandr -s 1920x1080 " One of the first things I did was go to the System Settings > Software & Updates > Additional Drivers and then select Nividia 304.131 (proprietary,tested). I do this since when Nouveau was first introduced, it never worked with my graphics chipset which is a Nividia 7050. Yes, the chipset is old but worked fine until 16.04. I spent the weekend trying all suggestions that I could find via the search engines along with the help of a few folks on the #ubuntu IRC. Three days later, still no luck and still having to type the xrandr line in the terminal. I even tried adding the xrandr line in /etc/lightdm/lightdm.conf, That was a disaster at bootup. luckily I was able to get to the terminal and Nano edit the file and reboot. In addition, probably unrelated to this issue, I have also noticed when running any streaming video, now it is almost like watching a slide show. Nothing has changed Internet connection or hardware since the install of 16.04. Even typing this is lagged by 1 to 3 seconds per character typed. Same issue in Firefox or Chrome. But sorry, I digress. This can be looked at in another post, forum or possible bug. The main issue is that Ubuntu 16.04 does not save and or reads the saved settings of 1920x1080 with out the later use via the terminal using xrandr. I did take notice that when booting into the main desktop the mouse pointer is small as if in 1920x1080 but then changes to a larger pointer then the resolution is then 1280x720 which seems to what 16.04 falls back to. The TV reports the proper information under xrandr. gee@HTPC:~$ xrandr Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 4096 x 4096 VGA-0 disconnected (normal left inverted right x axis y axis) TV-0 disconnected (normal left inverted right x axis y axis) HDMI-0 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 980mm x 580mm 1280x720 60.00 + 59.94 1920x1080 59.9459.94* 60.0560.0050.04 720x576 50.0050.08 720x480 59.94 640x480 59.93 gee@HTPC:~$ uname-a Linux HTPC 4.4.0-34-generic #53-Ubuntu SMP Wed Jul 27 16:06:39 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux This will be the only information I will post this way since it was quite short. I will attach my latest xorg.conf file and also post the pastebin URL to it if the attachment fails. http://pastebin.com/zmcuUJxQ Thank you for your time GEE --- .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: u'/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.131 Sun Nov 8 21:43:33 PST 2015 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME-Flashback:Unity DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.131, 4.4.0-34-generic, x86_64: installed nvidia-304, 304.131, 4.4.0-36-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation C68 [GeForce 7050 PV / nForce 630a] [10de:053a] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] C68 [GeForce 7050 PV / nForce 630a] [1462:349f] InstallationDate: Installed on 2016-08-20 (12 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 002: ID 099a:7202 Zippy Technology Corp. Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: MSI MS-7349 NonfreeKernelModules: nvidia Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic root=UUID
[Touch-packages] [Bug 1615864] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1615864/+attachment/4733059/+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/1615864 Title: Screen resolution not saved after reboot or logout and back in Status in xorg package in Ubuntu: Incomplete Bug description: Hello, I am having an issue with my screen resolution of 1920x1080. I am using a Vizio 42 inch TV which worked fine with the HDMI connection from the computer to the TV. Every time I boot the computer up I have to go into terminal and type " xrandr -s 1920x1080 " One of the first things I did was go to the System Settings > Software & Updates > Additional Drivers and then select Nividia 304.131 (proprietary,tested). I do this since when Nouveau was first introduced, it never worked with my graphics chipset which is a Nividia 7050. Yes, the chipset is old but worked fine until 16.04. I spent the weekend trying all suggestions that I could find via the search engines along with the help of a few folks on the #ubuntu IRC. Three days later, still no luck and still having to type the xrandr line in the terminal. I even tried adding the xrandr line in /etc/lightdm/lightdm.conf, That was a disaster at bootup. luckily I was able to get to the terminal and Nano edit the file and reboot. In addition, probably unrelated to this issue, I have also noticed when running any streaming video, now it is almost like watching a slide show. Nothing has changed Internet connection or hardware since the install of 16.04. Even typing this is lagged by 1 to 3 seconds per character typed. Same issue in Firefox or Chrome. But sorry, I digress. This can be looked at in another post, forum or possible bug. The main issue is that Ubuntu 16.04 does not save and or reads the saved settings of 1920x1080 with out the later use via the terminal using xrandr. I did take notice that when booting into the main desktop the mouse pointer is small as if in 1920x1080 but then changes to a larger pointer then the resolution is then 1280x720 which seems to what 16.04 falls back to. The TV reports the proper information under xrandr. gee@HTPC:~$ xrandr Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 4096 x 4096 VGA-0 disconnected (normal left inverted right x axis y axis) TV-0 disconnected (normal left inverted right x axis y axis) HDMI-0 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 980mm x 580mm 1280x720 60.00 + 59.94 1920x1080 59.9459.94* 60.0560.0050.04 720x576 50.0050.08 720x480 59.94 640x480 59.93 gee@HTPC:~$ uname-a Linux HTPC 4.4.0-34-generic #53-Ubuntu SMP Wed Jul 27 16:06:39 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux This will be the only information I will post this way since it was quite short. I will attach my latest xorg.conf file and also post the pastebin URL to it if the attachment fails. http://pastebin.com/zmcuUJxQ Thank you for your time GEE --- .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: u'/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.131 Sun Nov 8 21:43:33 PST 2015 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME-Flashback:Unity DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.131, 4.4.0-34-generic, x86_64: installed nvidia-304, 304.131, 4.4.0-36-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation C68 [GeForce 7050 PV / nForce 630a] [10de:053a] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] C68 [GeForce 7050 PV / nForce 630a] [1462:349f] InstallationDate: Installed on 2016-08-20 (12 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 002: ID 099a:7202 Zippy Technology Corp. Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: MSI MS-7349 NonfreeKernelModules: nvidia Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic roo
[Touch-packages] [Bug 1580537] Re: LibreOffice with ambiance theme and breeze icon style is unusable
** Branch linked: lp:~ci-train-bot/ubuntu-themes/ubuntu-themes-ubuntu- yakkety-landing-1903 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1580537 Title: LibreOffice with ambiance theme and breeze icon style is unusable Status in libreoffice package in Ubuntu: Fix Committed Status in ubuntu-themes package in Ubuntu: Fix Committed Bug description: Until today i didn't use LibreOffice on Ubuntu 16.04. I opened it today and i see menu/icon bar totally unusable with Ambiance theme and default Breeze style. (image attached) The version installed is 5.1.2-0ubuntu1. I did upgrade from 14.04 to 16.04 with some issues. Changing from Breeze to Human is usable but fugly. No issue with Radiance theme. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1580537/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1615864] DpkgLog.txt
apport information ** Attachment added: "DpkgLog.txt" https://bugs.launchpad.net/bugs/1615864/+attachment/4733051/+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/1615864 Title: Screen resolution not saved after reboot or logout and back in Status in xorg package in Ubuntu: Incomplete Bug description: Hello, I am having an issue with my screen resolution of 1920x1080. I am using a Vizio 42 inch TV which worked fine with the HDMI connection from the computer to the TV. Every time I boot the computer up I have to go into terminal and type " xrandr -s 1920x1080 " One of the first things I did was go to the System Settings > Software & Updates > Additional Drivers and then select Nividia 304.131 (proprietary,tested). I do this since when Nouveau was first introduced, it never worked with my graphics chipset which is a Nividia 7050. Yes, the chipset is old but worked fine until 16.04. I spent the weekend trying all suggestions that I could find via the search engines along with the help of a few folks on the #ubuntu IRC. Three days later, still no luck and still having to type the xrandr line in the terminal. I even tried adding the xrandr line in /etc/lightdm/lightdm.conf, That was a disaster at bootup. luckily I was able to get to the terminal and Nano edit the file and reboot. In addition, probably unrelated to this issue, I have also noticed when running any streaming video, now it is almost like watching a slide show. Nothing has changed Internet connection or hardware since the install of 16.04. Even typing this is lagged by 1 to 3 seconds per character typed. Same issue in Firefox or Chrome. But sorry, I digress. This can be looked at in another post, forum or possible bug. The main issue is that Ubuntu 16.04 does not save and or reads the saved settings of 1920x1080 with out the later use via the terminal using xrandr. I did take notice that when booting into the main desktop the mouse pointer is small as if in 1920x1080 but then changes to a larger pointer then the resolution is then 1280x720 which seems to what 16.04 falls back to. The TV reports the proper information under xrandr. gee@HTPC:~$ xrandr Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 4096 x 4096 VGA-0 disconnected (normal left inverted right x axis y axis) TV-0 disconnected (normal left inverted right x axis y axis) HDMI-0 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 980mm x 580mm 1280x720 60.00 + 59.94 1920x1080 59.9459.94* 60.0560.0050.04 720x576 50.0050.08 720x480 59.94 640x480 59.93 gee@HTPC:~$ uname-a Linux HTPC 4.4.0-34-generic #53-Ubuntu SMP Wed Jul 27 16:06:39 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux This will be the only information I will post this way since it was quite short. I will attach my latest xorg.conf file and also post the pastebin URL to it if the attachment fails. http://pastebin.com/zmcuUJxQ Thank you for your time GEE --- .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: u'/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.131 Sun Nov 8 21:43:33 PST 2015 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME-Flashback:Unity DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.131, 4.4.0-34-generic, x86_64: installed nvidia-304, 304.131, 4.4.0-36-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation C68 [GeForce 7050 PV / nForce 630a] [10de:053a] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] C68 [GeForce 7050 PV / nForce 630a] [1462:349f] InstallationDate: Installed on 2016-08-20 (12 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 002: ID 099a:7202 Zippy Technology Corp. Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: MSI MS-7349 NonfreeKernelModules: nvidia Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic root=UUID=3
[Touch-packages] [Bug 1615864] Re: Screen resolution not saved after reboot or logout and back in
apport information ** Tags added: apport-collected ubuntu xenial ** Description changed: Hello, I am having an issue with my screen resolution of 1920x1080. I am using a Vizio 42 inch TV which worked fine with the HDMI connection from the computer to the TV. Every time I boot the computer up I have to go into terminal and type " xrandr -s 1920x1080 " One of the first things I did was go to the System Settings > Software & Updates > Additional Drivers and then select Nividia 304.131 (proprietary,tested). I do this since when Nouveau was first introduced, it never worked with my graphics chipset which is a Nividia 7050. Yes, the chipset is old but worked fine until 16.04. I spent the weekend trying all suggestions that I could find via the search engines along with the help of a few folks on the #ubuntu IRC. Three days later, still no luck and still having to type the xrandr line in the terminal. I even tried adding the xrandr line in /etc/lightdm/lightdm.conf, That was a disaster at bootup. luckily I was able to get to the terminal and Nano edit the file and reboot. In addition, probably unrelated to this issue, I have also noticed when running any streaming video, now it is almost like watching a slide show. Nothing has changed Internet connection or hardware since the install of 16.04. Even typing this is lagged by 1 to 3 seconds per character typed. Same issue in Firefox or Chrome. But sorry, I digress. This can be looked at in another post, forum or possible bug. The main issue is that Ubuntu 16.04 does not save and or reads the saved settings of 1920x1080 with out the later use via the terminal using xrandr. I did take notice that when booting into the main desktop the mouse pointer is small as if in 1920x1080 but then changes to a larger pointer then the resolution is then 1280x720 which seems to what 16.04 falls back to. The TV reports the proper information under xrandr. gee@HTPC:~$ xrandr Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 4096 x 4096 VGA-0 disconnected (normal left inverted right x axis y axis) TV-0 disconnected (normal left inverted right x axis y axis) HDMI-0 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 980mm x 580mm 1280x720 60.00 + 59.94 1920x1080 59.9459.94* 60.0560.0050.04 720x576 50.0050.08 720x480 59.94 640x480 59.93 gee@HTPC:~$ uname-a Linux HTPC 4.4.0-34-generic #53-Ubuntu SMP Wed Jul 27 16:06:39 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux This will be the only information I will post this way since it was quite short. I will attach my latest xorg.conf file and also post the pastebin URL to it if the attachment fails. http://pastebin.com/zmcuUJxQ Thank you for your time GEE + --- + .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: u'/proc/driver/nvidia/gpus/0' + .proc.driver.nvidia.registry: Binary: "" + .proc.driver.nvidia.version: + NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.131 Sun Nov 8 21:43:33 PST 2015 + GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2) + .tmp.unity_support_test.0: + + ApportVersion: 2.20.1-0ubuntu2.1 + Architecture: amd64 + CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' + CompositorRunning: None + CurrentDesktop: GNOME-Flashback:Unity + DistUpgraded: Fresh install + DistroCodename: xenial + DistroRelease: Ubuntu 16.04 + DistroVariant: ubuntu + DkmsStatus: + nvidia-304, 304.131, 4.4.0-34-generic, x86_64: installed + nvidia-304, 304.131, 4.4.0-36-generic, x86_64: installed + ExtraDebuggingInterest: Yes, if not too technical + GraphicsCard: + NVIDIA Corporation C68 [GeForce 7050 PV / nForce 630a] [10de:053a] (rev a2) (prog-if 00 [VGA controller]) +Subsystem: Micro-Star International Co., Ltd. [MSI] C68 [GeForce 7050 PV / nForce 630a] [1462:349f] + InstallationDate: Installed on 2016-08-20 (12 days ago) + InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) + Lsusb: + Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 004 Device 002: ID 099a:7202 Zippy Technology Corp. + Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + MachineType: MSI MS-7349 + NonfreeKernelModules: nvidia + Package: xorg 1:7.7+13ubuntu3 + PackageArchitecture: amd64 + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic root=UUID=377930d2-4053-4a10-96ef-8cac652e4c24 ro quiet splash + ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 + Tags: xenial ubuntu + Uname: Linux 4.4.0-36-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm audio cdrom dip lpadmin plugdev pulse pulse-access sambashare sudo video + _MarkForUpload: T
[Touch-packages] [Bug 1615864] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1615864/+attachment/4733052/+files/JournalErrors.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/1615864 Title: Screen resolution not saved after reboot or logout and back in Status in xorg package in Ubuntu: Incomplete Bug description: Hello, I am having an issue with my screen resolution of 1920x1080. I am using a Vizio 42 inch TV which worked fine with the HDMI connection from the computer to the TV. Every time I boot the computer up I have to go into terminal and type " xrandr -s 1920x1080 " One of the first things I did was go to the System Settings > Software & Updates > Additional Drivers and then select Nividia 304.131 (proprietary,tested). I do this since when Nouveau was first introduced, it never worked with my graphics chipset which is a Nividia 7050. Yes, the chipset is old but worked fine until 16.04. I spent the weekend trying all suggestions that I could find via the search engines along with the help of a few folks on the #ubuntu IRC. Three days later, still no luck and still having to type the xrandr line in the terminal. I even tried adding the xrandr line in /etc/lightdm/lightdm.conf, That was a disaster at bootup. luckily I was able to get to the terminal and Nano edit the file and reboot. In addition, probably unrelated to this issue, I have also noticed when running any streaming video, now it is almost like watching a slide show. Nothing has changed Internet connection or hardware since the install of 16.04. Even typing this is lagged by 1 to 3 seconds per character typed. Same issue in Firefox or Chrome. But sorry, I digress. This can be looked at in another post, forum or possible bug. The main issue is that Ubuntu 16.04 does not save and or reads the saved settings of 1920x1080 with out the later use via the terminal using xrandr. I did take notice that when booting into the main desktop the mouse pointer is small as if in 1920x1080 but then changes to a larger pointer then the resolution is then 1280x720 which seems to what 16.04 falls back to. The TV reports the proper information under xrandr. gee@HTPC:~$ xrandr Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 4096 x 4096 VGA-0 disconnected (normal left inverted right x axis y axis) TV-0 disconnected (normal left inverted right x axis y axis) HDMI-0 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 980mm x 580mm 1280x720 60.00 + 59.94 1920x1080 59.9459.94* 60.0560.0050.04 720x576 50.0050.08 720x480 59.94 640x480 59.93 gee@HTPC:~$ uname-a Linux HTPC 4.4.0-34-generic #53-Ubuntu SMP Wed Jul 27 16:06:39 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux This will be the only information I will post this way since it was quite short. I will attach my latest xorg.conf file and also post the pastebin URL to it if the attachment fails. http://pastebin.com/zmcuUJxQ Thank you for your time GEE --- .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: u'/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.131 Sun Nov 8 21:43:33 PST 2015 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME-Flashback:Unity DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.131, 4.4.0-34-generic, x86_64: installed nvidia-304, 304.131, 4.4.0-36-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation C68 [GeForce 7050 PV / nForce 630a] [10de:053a] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] C68 [GeForce 7050 PV / nForce 630a] [1462:349f] InstallationDate: Installed on 2016-08-20 (12 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 002: ID 099a:7202 Zippy Technology Corp. Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: MSI MS-7349 NonfreeKernelModules: nvidia Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic
[Touch-packages] [Bug 1615864] MonitorsUser.xml.txt
apport information ** Attachment added: "MonitorsUser.xml.txt" https://bugs.launchpad.net/bugs/1615864/+attachment/4733054/+files/MonitorsUser.xml.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/1615864 Title: Screen resolution not saved after reboot or logout and back in Status in xorg package in Ubuntu: Incomplete Bug description: Hello, I am having an issue with my screen resolution of 1920x1080. I am using a Vizio 42 inch TV which worked fine with the HDMI connection from the computer to the TV. Every time I boot the computer up I have to go into terminal and type " xrandr -s 1920x1080 " One of the first things I did was go to the System Settings > Software & Updates > Additional Drivers and then select Nividia 304.131 (proprietary,tested). I do this since when Nouveau was first introduced, it never worked with my graphics chipset which is a Nividia 7050. Yes, the chipset is old but worked fine until 16.04. I spent the weekend trying all suggestions that I could find via the search engines along with the help of a few folks on the #ubuntu IRC. Three days later, still no luck and still having to type the xrandr line in the terminal. I even tried adding the xrandr line in /etc/lightdm/lightdm.conf, That was a disaster at bootup. luckily I was able to get to the terminal and Nano edit the file and reboot. In addition, probably unrelated to this issue, I have also noticed when running any streaming video, now it is almost like watching a slide show. Nothing has changed Internet connection or hardware since the install of 16.04. Even typing this is lagged by 1 to 3 seconds per character typed. Same issue in Firefox or Chrome. But sorry, I digress. This can be looked at in another post, forum or possible bug. The main issue is that Ubuntu 16.04 does not save and or reads the saved settings of 1920x1080 with out the later use via the terminal using xrandr. I did take notice that when booting into the main desktop the mouse pointer is small as if in 1920x1080 but then changes to a larger pointer then the resolution is then 1280x720 which seems to what 16.04 falls back to. The TV reports the proper information under xrandr. gee@HTPC:~$ xrandr Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 4096 x 4096 VGA-0 disconnected (normal left inverted right x axis y axis) TV-0 disconnected (normal left inverted right x axis y axis) HDMI-0 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 980mm x 580mm 1280x720 60.00 + 59.94 1920x1080 59.9459.94* 60.0560.0050.04 720x576 50.0050.08 720x480 59.94 640x480 59.93 gee@HTPC:~$ uname-a Linux HTPC 4.4.0-34-generic #53-Ubuntu SMP Wed Jul 27 16:06:39 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux This will be the only information I will post this way since it was quite short. I will attach my latest xorg.conf file and also post the pastebin URL to it if the attachment fails. http://pastebin.com/zmcuUJxQ Thank you for your time GEE --- .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: u'/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.131 Sun Nov 8 21:43:33 PST 2015 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME-Flashback:Unity DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.131, 4.4.0-34-generic, x86_64: installed nvidia-304, 304.131, 4.4.0-36-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation C68 [GeForce 7050 PV / nForce 630a] [10de:053a] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] C68 [GeForce 7050 PV / nForce 630a] [1462:349f] InstallationDate: Installed on 2016-08-20 (12 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 002: ID 099a:7202 Zippy Technology Corp. Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: MSI MS-7349 NonfreeKernelModules: nvidia Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-ge
