[Touch-packages] [Bug 1734568] Re: Please remove obsolete Android packages from Ubuntu
** Changed in: wpa (Ubuntu) Status: In Progress => Fix Committed ** Changed in: wpa (Ubuntu) Assignee: (unassigned) => Julian Andres Klode (juliank) ** Changed in: wpa (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1734568 Title: Please remove obsolete Android packages from Ubuntu Status in android-audiosystem package in Ubuntu: New Status in android-headers package in Ubuntu: New Status in android-src-vendor package in Ubuntu: New Status in wpa package in Ubuntu: Fix Committed Bug description: Ubuntu has a few Android-related packages that were never in Debian and are no longer maintained by anyone. Please remove them from Ubuntu disco. $ reverse-depends src:android-src-vendor No reverse dependencies found $ reverse-depends -b src:android-src-vendor No reverse dependencies found $ reverse-depends src:android-audiosystem No reverse dependencies found $ reverse-depends -b src:android-audiosystem No reverse dependencies found $ reverse-depends src:android-headers No reverse dependencies found $ reverse-depends -b src:android-headers Reverse-Build-Depends = * wpa (for android-headers) WPA source package would need to first drop: - debian/patches/android_hal_fw_path_change.patch: add a DBus method for requesting a firmware change when working with the Android HAL; this is used to set a device in P2P or AP mode; conditional to CONFIG_ANDROID_HAL being enabled. - debian/config/wpasupplicant/linux: enable CONFIG_ANDROID_HAL. - debian/control: Build-Depends on android-headers to get the required wifi headers for the HAL support. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android-audiosystem/+bug/1734568/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1810728] [NEW] cups error - internal server error when adding a printer
Public bug reported: Where - This is happening on a fresh Linux Mint Tessa whose upstream is bionic cat /etc/upstream-release/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04 LTS" What The upstream package is provided by the upstream bionic sudo apt policy cups cups: Installed: 2.2.7-1ubuntu2.2 Candidate: 2.2.7-1ubuntu2.2 Version table: *** 2.2.7-1ubuntu2.2 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 2.2.7-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages Problem Synopsis I have problem(s) printing with adding or printing to both my printers, one Dell and the other a Canon. The Dell E525 was added automatically but when printing to it the queue reports there was a problem with printing and the documents stays 'pending' in the queue. If I try to add the Canon MG6320 using the auto-detected entry for it, the addition fails and produces the error: cups error - internal server error. If I add it using the find function with the IP address, adding it succeeds but printing to it has the same problem as the Dell. This seems to be a regression/bug in cups that should be addressed. Please feel free to ask, if you need me to collect more info. ** Affects: cups (Ubuntu) Importance: Undecided Status: New -- 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/1810728 Title: cups error - internal server error when adding a printer Status in cups package in Ubuntu: New Bug description: Where - This is happening on a fresh Linux Mint Tessa whose upstream is bionic cat /etc/upstream-release/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04 LTS" What The upstream package is provided by the upstream bionic sudo apt policy cups cups: Installed: 2.2.7-1ubuntu2.2 Candidate: 2.2.7-1ubuntu2.2 Version table: *** 2.2.7-1ubuntu2.2 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 2.2.7-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages Problem Synopsis I have problem(s) printing with adding or printing to both my printers, one Dell and the other a Canon. The Dell E525 was added automatically but when printing to it the queue reports there was a problem with printing and the documents stays 'pending' in the queue. If I try to add the Canon MG6320 using the auto-detected entry for it, the addition fails and produces the error: cups error - internal server error. If I add it using the find function with the IP address, adding it succeeds but printing to it has the same problem as the Dell. This seems to be a regression/bug in cups that should be addressed. Please feel free to ask, if you need me to collect more info. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1810728/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1734568] Re: Please remove obsolete Android packages from Ubuntu
** Also affects: wpa (Ubuntu) Importance: Undecided Status: New ** Changed in: wpa (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1734568 Title: Please remove obsolete Android packages from Ubuntu Status in android-audiosystem package in Ubuntu: New Status in android-headers package in Ubuntu: New Status in android-src-vendor package in Ubuntu: New Status in wpa package in Ubuntu: In Progress Bug description: Ubuntu has a few Android-related packages that were never in Debian and are no longer maintained by anyone. Please remove them from Ubuntu disco. $ reverse-depends src:android-src-vendor No reverse dependencies found $ reverse-depends -b src:android-src-vendor No reverse dependencies found $ reverse-depends src:android-audiosystem No reverse dependencies found $ reverse-depends -b src:android-audiosystem No reverse dependencies found $ reverse-depends src:android-headers No reverse dependencies found $ reverse-depends -b src:android-headers Reverse-Build-Depends = * wpa (for android-headers) WPA source package would need to first drop: - debian/patches/android_hal_fw_path_change.patch: add a DBus method for requesting a firmware change when working with the Android HAL; this is used to set a device in P2P or AP mode; conditional to CONFIG_ANDROID_HAL being enabled. - debian/config/wpasupplicant/linux: enable CONFIG_ANDROID_HAL. - debian/control: Build-Depends on android-headers to get the required wifi headers for the HAL support. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android-audiosystem/+bug/1734568/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 652870] Re: Avahi update causes internet connetions to fail
** Changed in: avahi (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/652870 Title: Avahi update causes internet connetions to fail Status in avahi package in Ubuntu: Invalid Bug description: I'm using Lucid with all updates applied as of a week ago. Everthing on my system was working fine until this mornings system update. Part of the update was patches to Avahi "Version 0.6.25-1ubuntu6.1". After reboot, I couldn't get onto the internet. When I looked at ifconfig, I normally have eth2 & lo entries. The problem seems to be a new eth2:avahi entry that had an IP address assigned that isn't in my LAN. The eth2 entry was also there, but didn't have an IP. I solved this, sort of, by editing /etc/default/avahi-daemon and setting AVAHI_DAEMON_DETECT_LOCAL=0 instead of 1. That's a patch I found on http://ubuntuforums.org/showthread.php?t=1339516 answering "How do I disable Avahi??" After a reboot, I could connect to the internet again. However, some things started behaving strangely. Like the colours of everything had changed as though the theme had been changed. Just going into the Preferences/Appearance seemed to be enough to fix it - I didn't have to click anything else. Very odd. Might be related to a different update package. FWIW. I don't think I need the avahi services from what I understand of it. I'm running Ubuntu Lucid within a VMware virtual machine on an XP host. It's a laptop, so the network environment does change twice a day. But, as I said, everything was stable until this mornings update. I've since rolled back to a VM snapshot prior to the update and I'm going to delay updates for a little while, but I can reinstate the snapshot containing the update if necessary. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/652870/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1810388] Re: syslog filled with drm messages 40 times per second
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- 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/1810388 Title: syslog filled with drm messages 40 times per second Status in linux package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: Hi all, I don't really know when it exactly began. From /var/log/syslog : Jan 3 09:42:42 localhost kernel: [32659.271016] [drm:drm_mode_addfb2 [drm]] [FB:74] Jan 3 09:42:42 localhost kernel: [32659.300800] [drm:drm_mode_addfb2 [drm]] [FB:89] There are similar bugs that have been already noticed, but none of them helped me. Changing desktop environment to a non-gnome desktop stops messages. My environment (export cmd) : declare -x XDG_CONFIG_DIRS="/etc/xdg/xdg-ubuntu:/etc/xdg" declare -x XDG_CURRENT_DESKTOP="ubuntu:GNOME" declare -x XDG_DATA_DIRS="/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/var/lib/snapd/desktop" declare -x XDG_GREETER_DATA_DIR="/var/lib/lightdm-data/userprofile" declare -x XDG_MENU_PREFIX="gnome-" declare -x XDG_RUNTIME_DIR="/run/user/1000" declare -x XDG_SEAT="seat0" declare -x XDG_SEAT_PATH="/org/freedesktop/DisplayManager/Seat0" declare -x XDG_SESSION_DESKTOP="ubuntu" declare -x XDG_SESSION_ID="c2" declare -x XDG_SESSION_PATH="/org/freedesktop/DisplayManager/Session0" declare -x XDG_SESSION_TYPE="x11" declare -x XDG_VTNR="7" My kernel : 4.15.0-43-generic Ubuntu 18.04.01 LTS Graphic : Intel Haswell Mobile Any help is appreciated Thanks ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Jan 3 09:38:35 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.18, 4.15.0-42-generic, x86_64: installed virtualbox, 5.2.18, 4.15.0-43-generic, x86_64: installed virtualbox, 5.2.18, 4.19.0-041900-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:060a] InstallationDate: Installed on 2016-12-20 (743 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. XPS13 9333 ProcEnviron: LANGUAGE=fr_FR PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=19d7298f-74c8-4a78-9f17-88b9f04bbc3a ro net.ifnames=0 biosdevname=0 acpi=force plymouth:debug drm.debug=0xe SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0GFTRT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd08/31/2015:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.family: Shark Bay System dmi.product.name: XPS13 9333 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810388/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1803487] Re: gnome-shell crashes with SIGSEGV in gweather_location_common_deserialize → gweather_location_format_two_deserialize → gweather_location_deserialize → ffi_call_unix64
It is still crashing in the latest bionic update though :( 3.28.3-0ubuntu0.18.04.3 ** Changed in: libgweather (Ubuntu Bionic) Status: Fix Committed => Confirmed ** Tags removed: verification-done verification-done-bionic ** Tags added: verification-failed verification-failed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libgweather in Ubuntu. https://bugs.launchpad.net/bugs/1803487 Title: gnome-shell crashes with SIGSEGV in gweather_location_common_deserialize → gweather_location_format_two_deserialize → gweather_location_deserialize → ffi_call_unix64 → ffi_call Status in gnome-shell package in Ubuntu: Fix Released Status in libgweather package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: Invalid Status in libgweather source package in Bionic: Fix Committed Bug description: [ Description ] The second stable release in the 3.28 series. [ QA ] Run Ubuntu session, expect the shell to show weather information and not to crash on timezone changes https://wiki.ubuntu.com/StableReleaseUpdates/GNOME [ Regresison potential ] Weather location might be leaked. However this is very safe as upstream fix comes with proper testing. --- The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.28.3-0ubuntu0.18.04.3, the problem page at https://errors.ubuntu.com/problem/4ff1b7671a7dc53f26da1c0f78af65d0cc5168fa contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1803487/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1803487] Re: gnome-shell crashes with SIGSEGV in gweather_location_common_deserialize → gweather_location_format_two_deserialize → gweather_location_deserialize → ffi_call_unix64
Although... is bionic updates missing the fix? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libgweather in Ubuntu. https://bugs.launchpad.net/bugs/1803487 Title: gnome-shell crashes with SIGSEGV in gweather_location_common_deserialize → gweather_location_format_two_deserialize → gweather_location_deserialize → ffi_call_unix64 → ffi_call Status in gnome-shell package in Ubuntu: Fix Released Status in libgweather package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: Invalid Status in libgweather source package in Bionic: Fix Committed Bug description: [ Description ] The second stable release in the 3.28 series. [ QA ] Run Ubuntu session, expect the shell to show weather information and not to crash on timezone changes https://wiki.ubuntu.com/StableReleaseUpdates/GNOME [ Regresison potential ] Weather location might be leaked. However this is very safe as upstream fix comes with proper testing. --- The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.28.3-0ubuntu0.18.04.3, the problem page at https://errors.ubuntu.com/problem/4ff1b7671a7dc53f26da1c0f78af65d0cc5168fa contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1803487/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1803487] Re: gnome-shell crashes with SIGSEGV in gweather_location_common_deserialize → gweather_location_format_two_deserialize → gweather_location_deserialize → ffi_call_unix64
Oops. I confused packages with similar versions. ** Changed in: libgweather (Ubuntu Bionic) Status: Confirmed => Fix Committed ** Tags removed: verification-failed verification-failed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libgweather in Ubuntu. https://bugs.launchpad.net/bugs/1803487 Title: gnome-shell crashes with SIGSEGV in gweather_location_common_deserialize → gweather_location_format_two_deserialize → gweather_location_deserialize → ffi_call_unix64 → ffi_call Status in gnome-shell package in Ubuntu: Fix Released Status in libgweather package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: Invalid Status in libgweather source package in Bionic: Fix Committed Bug description: [ Description ] The second stable release in the 3.28 series. [ QA ] Run Ubuntu session, expect the shell to show weather information and not to crash on timezone changes https://wiki.ubuntu.com/StableReleaseUpdates/GNOME [ Regresison potential ] Weather location might be leaked. However this is very safe as upstream fix comes with proper testing. --- The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.28.3-0ubuntu0.18.04.3, the problem page at https://errors.ubuntu.com/problem/4ff1b7671a7dc53f26da1c0f78af65d0cc5168fa contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1803487/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1756380] Re: vaapi VP9 hardware decoding not working anymore in bionic
That's right. I would recommend avoiding i965-va-driver-shaders and use only i965-va-driver. The latter should be more efficient and supported by Intel. But you do need to ensure your hardware is new enough for VP9 decoding. Only Intel 7th generation (Kaby Lake) and later chips support VP9. That said, if you have older hardware (Sky Lake or older) then it sounds like i965-va-driver-shader might be the next best option. If you would like to discuss problems in i965-va-driver-shader then please open a new bug for it by running: ubuntu-bug i965-va-driver-shader -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libva in Ubuntu. https://bugs.launchpad.net/bugs/1756380 Title: vaapi VP9 hardware decoding not working anymore in bionic Status in intel-vaapi-driver package in Ubuntu: Fix Released Status in libva package in Ubuntu: Invalid Bug description: Hardware: Dell XPS13 9365, i7-7Y75 System: Ubuntu Bionic Beaver (development branch) vainfo output on bionic is: libva info: VA-API version 1.1.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_0 libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.1 (libva 2.1.0) vainfo: Driver version: Intel i965 driver for Intel(R) Kaby Lake - 2.0.0 vainfo: Supported profile and entrypoints VAProfileMPEG2Simple: VAEntrypointVLD VAProfileMPEG2Simple: VAEntrypointEncSlice VAProfileMPEG2Main : VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointEncSlice VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264Main : VAEntrypointEncSliceLP VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileH264High : VAEntrypointEncSliceLP VAProfileH264MultiviewHigh : VAEntrypointVLD VAProfileH264MultiviewHigh : VAEntrypointEncSlice VAProfileH264StereoHigh : VAEntrypointVLD VAProfileH264StereoHigh : VAEntrypointEncSlice VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main: VAEntrypointVLD VAProfileVC1Advanced: VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc VAProfileJPEGBaseline : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointEncPicture VAProfileVP8Version0_3 : VAEntrypointVLD VAProfileHEVCMain : VAEntrypointVLD VAProfileHEVCMain : VAEntrypointEncSlice VAProfileHEVCMain10 : VAEntrypointVLD VAProfileHEVCMain10 : VAEntrypointEncSlice As you can see, VP9 entrypoints are missing. vainfo output on 17.10 was: libva info: VA-API version 0.40.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_0_40 libva info: va_openDriver() returns 0 vainfo: VA-API version: 0.40 (libva ) vainfo: Driver version: Intel i965 driver for Intel(R) Kabylake - 1.8.3 vainfo: Supported profile and entrypoints VAProfileMPEG2Simple:VAEntrypointVLD VAProfileMPEG2Simple:VAEntrypointEncSlice VAProfileMPEG2Main :VAEntrypointVLD VAProfileMPEG2Main :VAEntrypointEncSlice VAProfileH264ConstrainedBaseline:VAEntrypointVLD VAProfileH264ConstrainedBaseline:VAEntrypointEncSlice VAProfileH264ConstrainedBaseline:VAEntrypointEncSliceLP VAProfileH264Main :VAEntrypointVLD VAProfileH264Main :VAEntrypointEncSlice VAProfileH264Main :VAEntrypointEncSliceLP VAProfileH264High :VAEntrypointVLD VAProfileH264High :VAEntrypointEncSlice VAProfileH264High :VAEntrypointEncSliceLP VAProfileH264MultiviewHigh :VAEntrypointVLD VAProfileH264MultiviewHigh :VAEntrypointEncSlice VAProfileH264StereoHigh :VAEntrypointVLD VAProfileH264StereoHigh :VAEntrypointEncSlice VAProfileVC1Simple :VAEntrypointVLD
[Touch-packages] [Bug 1025388] Re: Internal mic stops working when plugging in headphones
I think you'd need someone to figure out what/where is detecting the combo jack is in use and whether it thinks an external mic is plugged in or just blindly assumes one is plugged in. I don't know what component is responsible for that detection so adding a kernel task in case that's relevant... ** Also affects: linux (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/1025388 Title: Internal mic stops working when plugging in headphones Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: I am currently running Quantal and when I plug headphones into my headphone socket (which has an icon of a headset next to it, so I presume it can take some kind of headset), the internal mic on my laptop stops working. If I unplug the headphones the internal mic works as normal. I tried this with two different sets of headphones (one of which has a mic, and the other I think has a mic too). ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: pulseaudio 1:2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-4.4-generic 3.5.0-rc6 Uname: Linux 3.5.0-4-generic i686 ApportVersion: 2.3-0ubuntu4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jono 1860 F pulseaudio /dev/snd/pcmC0D0c: jono 1860 F...m pulseaudio Date: Mon Jul 16 11:01:32 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8AET56WW (1.36 ) dmi.board.asset.tag: Not Available dmi.board.name: 4239CTO 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:bvr8AET56WW(1.36):bd12/06/2011:svnLENOVO:pn4239CTO:pvrThinkPadT520:rvnLENOVO:rn4239CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4239CTO dmi.product.version: ThinkPad T520 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1025388/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 736788] Re: 13d3:3304 IMC Networks bluetooth doesn't work
This bug has been closed for over 3 years. If you have any problems at all then please open a new bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/736788 Title: 13d3:3304 IMC Networks bluetooth doesn't work Status in bluez package in Ubuntu: Fix Released Bug description: Binary package hint: bluez The "13d3:3304 IMC Networks" internal bluetooth module found in Asus U36JC notebook is not working in Ubuntu Maverick nor Natty. The systems certainly knows about presence of the bluetooth module - the icon in status bar is visible and allows to switch it on/off, but nothing else works. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 2.6.38-6.34-generic 2.6.38-rc7 Uname: Linux 2.6.38-6-generic x86_64 Architecture: amd64 CheckboxSubmission: 4c3a0145220348e366d02efaed27e66e CheckboxSystem: b8f3ec504801f13fc208edb5c785b099 Date: Thu Mar 17 12:03:47 2011 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110302) InterestingModules: sco bnep l2cap btusb bluetooth MachineType: ASUSTeK Computer Inc. U36JC ProcEnviron: LANGUAGE=cs_CZ:en PATH=(custom, user) LANG=cs_CZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-6-generic root=UUID=2d566c56-67c7-4af1-a443-a8c80061120c ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/26/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: U36JC.205 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: U36JC dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrU36JC.205:bd01/26/2011:svnASUSTeKComputerInc.:pnU36JC:pvr1.0:rvnASUSTeKComputerInc.:rnU36JC:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: U36JC dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:3 acl:0 sco:0 commands:1 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/736788/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 411688] Re: pulseaudio floods network with multicast packets
Closed for Ubuntu since the bug is closed upstream. If you feel this is incorrect then please comment upstream (https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/505) and then here. ** Changed in: pulseaudio (Ubuntu) Status: Confirmed => Won't Fix -- 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/411688 Title: pulseaudio floods network with multicast packets Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Won't Fix Status in pulseaudio package in Arch Linux: Unknown Status in pulseaudio package in Debian: Fix Released Bug description: Binary package hint: pulseaudio Since a karmic update last week, when pulseaudio is running it floods the network with multicast packets, to the point where the wireless interface I'm using is so flooded that no other network traffic can be transfered. Here is a snippet of tcpdump -i wlan 0 -n: ---8<--- 01:10:36.532748 IP (tos 0x10, ttl 1, id 23823, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d0f 4000 0111 2d6d 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f9f6 800a ee8e 0x0020: 0071 a980 ed51 a42b 0x0030: 0x0040: 01:10:36.53 IP (tos 0x10, ttl 1, id 23824, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d10 4000 0111 2d6c 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f8b5 800a ee8f 0x0020: 0071 aac0 ed51 a42b 0x0030: 0x0040: 01:10:36.547289 IP (tos 0x10, ttl 1, id 23825, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d11 4000 0111 2d6b 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f774 800a ee90 0x0020: 0071 ac00 ed51 a42b 0x0030: 0x0040: 01:10:36.556725 IP (tos 0x10, ttl 1, id 23826, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d12 4000 0111 2d6a 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f633 800a ee91 0x0020: 0071 ad40 ed51 a42b 0x0030: 0x0040: 01:10:36.561680 IP (tos 0x10, ttl 1, id 23827, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d13 4000 0111 2d69 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f4f2 800a ee92 0x0020: 0071 ae80 ed51 a42b 0x0030: 0x0040: 01:10:36.568984 IP (tos 0x10, ttl 1, id 23828, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d14 4000 0111 2d68 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f3b1 800a ee93 0x0020: 0071 afc0 ed51 a42b 0x0030: 0x0040: 01:10:36.576212 IP (tos 0x10, ttl 1, id 23829, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d15 4000 0111 2d67 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f270 800a ee94 0x0020: 0071 b100 ed51 a42b 0x0030: 0x0040: 01:10:36.588095 IP (tos 0x10, ttl 1, id 23830, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d16 4000 0111 2d66 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f12f 800a ee95 0x0020: 0071 b240 ed51 a42b 0x0030: 0x0040: 01:10:36.590645 IP (tos 0x10, ttl 1, id 23831, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d17 4000 0111 2d65 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 efee 800a ee96 0x0020: 0071 b380 ed51 a42b 0x0030: 0x0040: 01:10:36.605081 IP (tos 0x10, ttl 1, id 23832,
[Touch-packages] [Bug 1771185] Re: Secondary monitor not connecting in 18.04 LTS
So, seems I have figured out the issue (at least on my Lenovo T460s) and I think it lies with the Intel chip internal GPU. If you use display port and HDMI-->Display Port adapter it won't work. The Intel chip doesn't seem to support two DP connections at a time. But you can connect Dp & HDMI-->DVI at the same time (or VGA for that matter) & Internal display. So max is 3 displays but they need to be different techs. I can't confirm this for other laptops without external graphics cards since i don't have any more. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxrandr in Ubuntu. https://bugs.launchpad.net/bugs/1771185 Title: Secondary monitor not connecting in 18.04 LTS Status in libxrandr package in Ubuntu: Confirmed Bug description: I have an Acer Aspire V Nitro VN7-592G-709V with Nvidia Geforce 960M (nvidia driver v390) and a Benq W1070 projector. I have upgraded from Ubuntu 16.04 to 18.04 and my projector connects for a split second and then gets disconnected. In Ubuntu 16.04 projector was working fine as a mirror display and extended desktop. Here's what I already tried: - enable the nouveau driver instead of the nvidia driver -> no result - enable the on-board intel board with sudo prime-select intel -> no result - apt purge nvidia* & reinstall nvidia driver 390 (stable) or 396 (beta) -> no result - disable nouveau driver, disable nvidia driver from the repository and install nvidia driver from nvidia website (both 390 and 396) -> no result - installed CCSM (CompizConfig Settings Manager) and disabled display auto-detection -> no result - played around with the refresh rate (some forums say that the two outputs have to be in sync -> no result - deleted the whole Ubuntu 18.04 upgrade and installed a fresh 18.04 -> still the same issue - tried to manually enable the output with xrandr --output HDMI-1-2 --mode 1920x1920 -> nothing - under settings -> devices -> displays I don't see a secondary display (just the main one) I have the latest libxrandr2, 2:1.5.1-1 under Ubuntu 18.04 (updated to day) Here is the output of xrandr the very second when I connect the projector (then HDMI-1-2 goes disconnected and no modes are displayed): ~$ xrandr Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 345mm x 194mm 1920x1080 60.02*+ 60.0159.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-2 disconnected (normal left inverted right x axis y axis) 1920x1080 (0x258) 148.500MHz +HSync +VSync h: width 1920 start 2008 end 2052 total 2200 skew0 clock 67.50KHz v: height 1080 start 1084 end 1089 total 1125 clock 60.00Hz 1920x1080 (0x259) 148.500MHz +HSync +VSync h: width 1920 start 2448 end 2492 total 2640 skew0 clock 56.25KHz v: height 1080 start 1084 end 1089 total 1125 clock 50.00Hz 1920x1080
[Touch-packages] [Bug 1805523] Re: System Sound Events Not Playing even when enabled
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libcanberra (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libcanberra in Ubuntu. https://bugs.launchpad.net/bugs/1805523 Title: System Sound Events Not Playing even when enabled Status in libcanberra package in Ubuntu: Confirmed Bug description: Expected Behavior: Doing something like displaying a warning or error should play an error sound. Actual Behavior: Some events don't play sounds at all when they should, even though the event-sounds setting is enabled through dconf or Tweaks. The other Yaru system sounds are present in /usr/share/sounds/Yaru yet nothing still plays. Some sounds that do play is the warning that appears when closing multiple tabs in firefox, and inserting a usb device To reproduce: Do something that should produce an error or warning noise, like emptying the trash or quitting terminal with a running process open. The sound theme is installed from apt repository, yaru-theme-sound version 18.10.6 I'm not 100% certain this package is the culprit, but here's the info: libcanberra version: 0.30-6ubuntu1 Ubuntu version 18.10 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libcanberra0 0.30-6ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 27 16:49:51 2018 InstallationDate: Installed on 2018-11-25 (2 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libcanberra UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcanberra/+bug/1805523/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1810689] [NEW] HDA Intel PCH / Realtek ALC269VB not seen by pulseaudio (whereas alsa see it) after ubuntu 18.10 upgrade
Public bug reported: I was using ubuntu 18.04 on my computer (and previously 17.10), and I got the sound card working correctly with pulseaudio. After upgrading to 18.10, pulseaudio interface only detect my usb microphone (BIRO UM1), but it does not detect my computer internal sound card, either for sinking or as a source. I only have a "fictive sink". I have done some experiments: using pacmd, if I try to `load-module module-udev-detect`, nothing happens, and `journalctl --user-unit pulseaudio.service` tells me that the module was already loaded and refuse to load again. If I use `load-module module-detect` the sound card is detected but does not seems to work correctly ! If I use `load-module module-alsa-sink device=default` and `load-module module-alsa-source device=default` my sound card is seens and works as expected. So the problem seems with the module-udev-detect not doing its job correctly (or not having necessary rules ?) My system: $ lsb_release -a LSB Version: core-9.20170808ubuntu1-noarch:printing-9.20170808ubuntu1-noarch:security-9.20170808ubuntu1-noarch Distributor ID: Ubuntu Description:Ubuntu 18.10 Release:18.10 Codename: cosmic $ uname -a Linux tignasse 4.18.0-13-generic #14-Ubuntu SMP Wed Dec 5 09:04:24 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo lshw ... *-multimedia description: Audio device produit: Sunrise Point-LP HD Audio fabriquant: Intel Corporation identifiant matériel: 1f.3 information bus: pci@:00:1f.3 version: 21 bits: 64 bits horloge: 33MHz fonctionnalités: pm msi bus_master cap_list configuration: driver=snd_hda_intel latency=32 ressources: irq:128 mémoire:df12-df123fff mémoire:df10-df10 ... $ aplay -l Liste des Périphériques Matériels PLAYBACK carte 0: PCH [HDA Intel PCH], périphérique 0: ALC269VB Analog [ALC269VB Analog] Sous-périphériques: 0/1 Sous-périphérique #0: subdevice #0 carte 0: PCH [HDA Intel PCH], périphérique 3: HDMI 0 [HDMI 0] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 0: PCH [HDA Intel PCH], périphérique 7: HDMI 1 [HDMI 1] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 0: PCH [HDA Intel PCH], périphérique 8: HDMI 2 [HDMI 2] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 0: PCH [HDA Intel PCH], périphérique 9: HDMI 3 [HDMI 3] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 0: PCH [HDA Intel PCH], périphérique 10: HDMI 4 [HDMI 4] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 $ arecord -l Liste des Périphériques Matériels CAPTURE carte 0: PCH [HDA Intel PCH], périphérique 0: ALC269VB Analog [ALC269VB Analog] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 1: UM1 [BIRO UM1], périphérique 0: USB Audio [USB Audio] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 $ lsmod |grep hda -i snd_hda_ext_core 24576 1 snd_soc_skl snd_hda_codec_hdmi 49152 1 snd_hda_codec_realtek 106496 1 snd_hda_codec_generic73728 1 snd_hda_codec_realtek snd_hda_intel 40960 7 snd_hda_codec 126976 4 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek snd_hda_core 81920 7 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_ext_core,snd_hda_codec,snd_hda_codec_realtek,snd_soc_skl snd_hwdep 20480 2 snd_usb_audio,snd_hda_codec snd_pcm98304 11 snd_hda_codec_hdmi,snd_hda_intel,snd_usb_audio,snd_hda_ext_core,snd_hda_codec,snd_soc_core,snd_soc_skl,snd_hda_core,snd_pcm_dmaengine snd81920 28 snd_hda_codec_generic,snd_seq,snd_seq_device,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_usb_audio,snd_usbmidi_lib,snd_hda_codec,snd_hda_codec_realtek,snd_timer,snd_compress,snd_soc_core,snd_pcm,snd_rawmidi Package: pulseaudio Version: 1:12.2-0ubuntu4 Package: alsa-base Version: 1.0.25+dfsg-0ubuntu5 Package: alsa-firmware-loaders Version: 1.1.3-1 Package: udev Version: 239-7ubuntu10.4 ** Affects: pulseaudio (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/1810689 Title: HDA Intel PCH / Realtek ALC269VB not seen by pulseaudio (whereas alsa see it) after ubuntu 18.10 upgrade Status in pulseaudio package in Ubuntu: New Bug description: I was using ubuntu 18.04 on my computer (and previously 17.10), and I got the sound card working correctly with pulseaudio. After upgrading to 18.10, pulseaudio interface only detect my usb microphone (BIRO UM1), but it does not detect my computer internal sound card, either for sinking or as a source. I only have a "fictive sink". I have done some
[Touch-packages] [Bug 1810687] [NEW] system freezes randomely
Public bug reported: graphics drivers on ubuntu 18.04 problem. Live cd works ok, ubuntu 16 works ok. Graphics card is atom series .. im thing THANKS FOR HELP ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 4.18.0-041800-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Prístup odmietnutý: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: Budgie:GNOME Date: Sun Jan 6 22:54:46 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-38-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-39-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-43-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.18.0-041800-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Atom Processor Z36xxx/Z37xxx Series Graphics & Display [1043:161d] InstallationDate: Installed on 2018-09-25 (102 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 001 Device 004: ID 04ca:2006 Lite-On Technology Corp. Broadcom BCM43142A0 Bluetooth Device Bus 001 Device 003: ID 04f2:b483 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 8087:07e6 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X553MA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-041800-generic root=UUID=260596fd-12f5-454a-8b42-510486651a3f ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/03/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X553MA.214 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X553MA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX553MA.214:bd08/03/2015:svnASUSTeKCOMPUTERINC.:pnX553MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX553MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X553MA dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sun Jan 6 22:26:56 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.2 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- 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/1810687 Title: system freezes randomely Status in xorg package in Ubuntu: New Bug description: graphics drivers on ubuntu 18.04 problem. Live cd works ok, ubuntu 16 works ok. Graphics card is atom series .. im thing THANKS FOR HELP ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 4.18.0-041800-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Prístup odmietnutý: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: Budgie:GNOME Date: Sun Jan 6 22:54:46 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-38-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-39-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-43-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.18.0-041800-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Atom Processor Z36xxx/Z37xxx Series Graphics & Display [1043:161d] InstallationDate: Installed on 2018-09-25 (102 days ago) InstallationMedia:
[Touch-packages] [Bug 1810660] Re: vpn static route
** Package changed: ubuntu-docs (Ubuntu) => network-manager (Ubuntu) -- 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/1810660 Title: vpn static route Status in network-manager package in Ubuntu: New Bug description: After upgrading to 18.04 I can no longer create a vpn with a static route unless a gateway is specified. Before (with 16.04) I could add 1 or more destination networks without a gateway for each. Once the VPN connection was established, all static routes defined would have a gateway the VPN device (e.g ppp0, tun0, etc), as below. 192.168.xxx.0/24 is the local network 10.0.xxx.0/24 are remote networks accessible through the VPN. Destination Gateway Genmask Flags Metric RefUse Iface 0.0.0.0 192.168.xxx.254 0.0.0.0 UG20100 00 enp0s25 10.0.1.00.0.0.0 255.255.255.0 UH50 00 ppp0 10.0.2.00.0.0.0 255.255.255.0 UH50 00 ppp0 10.0.3.00.0.0.0 255.255.255.0 UH50 00 ppp0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1810660/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1810660] [NEW] vpn static route
You have been subscribed to a public bug: After upgrading to 18.04 I can no longer create a vpn with a static route unless a gateway is specified. Before (with 16.04) I could add 1 or more destination networks without a gateway for each. Once the VPN connection was established, all static routes defined would have a gateway the VPN device (e.g ppp0, tun0, etc), as below. 192.168.xxx.0/24 is the local network 10.0.xxx.0/24 are remote networks accessible through the VPN. Destination Gateway Genmask Flags Metric RefUse Iface 0.0.0.0 192.168.xxx.254 0.0.0.0 UG20100 00 enp0s25 10.0.1.00.0.0.0 255.255.255.0 UH50 00 ppp0 10.0.2.00.0.0.0 255.255.255.0 UH50 00 ppp0 10.0.3.00.0.0.0 255.255.255.0 UH50 00 ppp0 ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- vpn static route https://bugs.launchpad.net/bugs/1810660 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager 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 1810683] [NEW] Suspend does not work in the login screen
Public bug reported: After booting the system and login screen is displayed top right gear- icon contains option to Suspend. However, selecting that action has no results at all (no error message, nothing in any file under /var/log or journalctl). I would like to get the suspend action to work similar to older Ubuntu versions (this system used to run Ubuntu 16.04 LTS and I did a fresh install of 18.04.1 LTS). I have removed package gdm3 and installed lightdm instead because I like the lightdm interface better for our use case. Looking at the source code in liblightdm-gobject/power.c suggests that lightdm_get_can_suspend() returns true because I get the suspend option. However, selecting the option does nothing so I would guess that lightdm_suspend() is called but somehow none of the g_debug() log messages never appear anywhere so I cannot debug the problem any further. (The above is just a guess because I didn't have enough time to read the source well enough to figure out if this is the codepath I'm trying to activate.) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-13.14~18.04.1-lowlatency 4.18.17 Uname: Linux 4.18.0-13-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: MATE Date: Sun Jan 6 22:23:20 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-05 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1810683 Title: Suspend does not work in the login screen Status in lightdm package in Ubuntu: New Bug description: After booting the system and login screen is displayed top right gear- icon contains option to Suspend. However, selecting that action has no results at all (no error message, nothing in any file under /var/log or journalctl). I would like to get the suspend action to work similar to older Ubuntu versions (this system used to run Ubuntu 16.04 LTS and I did a fresh install of 18.04.1 LTS). I have removed package gdm3 and installed lightdm instead because I like the lightdm interface better for our use case. Looking at the source code in liblightdm-gobject/power.c suggests that lightdm_get_can_suspend() returns true because I get the suspend option. However, selecting the option does nothing so I would guess that lightdm_suspend() is called but somehow none of the g_debug() log messages never appear anywhere so I cannot debug the problem any further. (The above is just a guess because I didn't have enough time to read the source well enough to figure out if this is the codepath I'm trying to activate.) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-13.14~18.04.1-lowlatency 4.18.17 Uname: Linux 4.18.0-13-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: MATE Date: Sun Jan 6 22:23:20 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-05 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1810683/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1205384] Re: Lock can be circumvented by switching to console
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lightdm (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1205384 Title: Lock can be circumvented by switching to console Status in LXDE: New Status in lightdm package in Ubuntu: Confirmed Status in lxsession package in Ubuntu: Fix Released Bug description: Steps to reproduce: 1)lock your screen using "dm-tool switch-to-greeter" or "dm-tool lock" 2)switch to console via ctrl+alt+F1 3)switch back to X via ctrl+alt+F7 Result: session is unlocked without entering a password Expected behaviour: session should still be locked when switching back to X ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: lightdm 1.7.7-0ubuntu2 ProcVersionSignature: Ubuntu 3.10.0-5.15-generic 3.10.2 Uname: Linux 3.10.0-5-generic i686 ApportVersion: 2.11-0ubuntu1 Architecture: i386 Date: Fri Jul 26 17:30:23 2013 InstallationDate: Installed on 2013-07-26 (0 days ago) InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130723.1) MarkForUpload: True SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/lxde/+bug/1205384/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1705437] Re: Upstream 'column' is newer than bsdmainutils'
Thank you for taking the time to report this bug and helping to make Ubuntu better. I haven't verified the details of the versions of "column" as you describe, but it does seem that both bsdmainutils and util-linux are capable of shipping it and so it is disabled from util-linux at the moment. This is derived directly from Debian packaging. I think it is unlikely that Ubuntu will accept the maintenance cost of a divergence from Debian on this point since this difference only affects a minority of Ubuntu users. If you'd like to see this changed, I think the most productive path forward would be to ask/convince the Debian maintainers of these packages to make this change in Debian. This would best be done by filing a bug in Debian for this. See https://www.debian.org/Bugs/Reporting for information on how to do this. Please see also https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=908975#10 I'm going to set this bug to Won't Fix to Ubuntu to make it clear that I don't believe there will be any intention by Ubuntu developers to make this change. If other Ubuntu developers disagree then we can reopen the bug. Note that if the change is made in Debian then the change will happen in Ubuntu by default regardless of the bug status in Ubuntu (and the status should then be changed). ** Bug watch added: Debian Bug tracker #908975 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908975 ** Changed in: util-linux (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: util-linux (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1705437 Title: Upstream 'column' is newer than bsdmainutils' Status in util-linux package in Ubuntu: Won't Fix Bug description: The 'column' program included in upstream util-linux (https://git.kernel.org/pub/scm/utils/util-linux/util-linux.git/tree /text-utils/column.c) is newer than the included in the bsdmainutil package (https://anonscm.debian.org/cgit/bsdmainutils/bsdmainutils.git/tree/usr.bin/column/column.c). However, debian/rules from util-linux package states the opposite, and therefore Ubuntu now is using 'column' from bsdmainutils instead of the util-linux one. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: util-linux 2.27.1-6ubuntu3.3 ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70 Uname: Linux 4.4.0-83-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: i3 Date: Thu Jul 20 11:41:36 2017 InstallationDate: Installed on 2016-04-23 (452 days ago) InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: util-linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1705437/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1810165] Re: Some black colors are shown in orange
This issue does not seem to be a software defect, but a hardware defect of my laptop. Thus I will close this error. ** Changed in: xorg (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1810165 Title: Some black colors are shown in orange Status in xorg package in Ubuntu: Invalid Bug description: During booting the usually black screen background is shown orange instead of black, the text is not readable and when the Laptop is running some pictures show black colour sections in orange colour. lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 apt-cache policy xorg xorg: Installed: 1:7.7+19ubuntu8 Candidate: 1:7.7+19ubuntu8 Version table: *** 1:7.7+19ubuntu8 500 500 http://de.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Dec 31 17:33:11 2018 DistUpgraded: 2018-10-30 13:42:44,629 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.18.0-10-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.18.0-13-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-10-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS780M [Mobility Radeon HD 3200] [1002:9612] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company RS780M [Mobility Radeon HD 3200] [103c:30e4] InstallationDate: Installed on 2016-12-24 (736 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Hewlett-Packard HP Compaq 6735s ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=27521009-c2c8-4fb5-97ee-c05ae44cfcd0 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to cosmic on 2018-10-30 (62 days ago) dmi.bios.date: 10/02/2008 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68GPP Ver. F.06 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 30E4 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 94.1C dmi.chassis.asset.tag: CNU842079D dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68GPPVer.F.06:bd10/02/2008:svnHewlett-Packard:pnHPCompaq6735s:pvrF.06:rvnHewlett-Packard:rn30E4:rvrKBCVersion94.1C:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP Compaq 6735s dmi.product.sku: NA777ES#ABD dmi.product.version: F.06 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+18.10.20180930-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1810165/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1749443] Re: ioctl FBIOPUT_VSCREENINFO: Invalid argument
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: fbset (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fbset in Ubuntu. https://bugs.launchpad.net/bugs/1749443 Title: ioctl FBIOPUT_VSCREENINFO: Invalid argument Status in fbset package in Ubuntu: Confirmed Bug description: $ fbset 768x576-75 ioctl FBIOPUT_VSCREENINFO: Invalid argument And the same happens with all other modes defined in /etc/fb.modes The problem seems to be that KMS fbcon does not accept the pixclock parameter, which is the first parameter in a "timings" string. Changing it to 0 for all modes makes them to work, albeit w/o actual resizing. The image then just occupies the upper-left corner of the screen. But its still better than the complete failure. I suppose also other timing params are not supported. At least if you run fbset w/o parameters, it will display all timing params set to zero. So I think zeroing "timings" for all modes in /etc/fb.modes will help with KMS. Additionally, please add the 1920x1080 mode, its currently missing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fbset/+bug/1749443/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
