[Bug 1792085] Re: Regression: MTP not working/very slow
I have just tried installing libmtp-1.1.17-2 on 18.04 from here: https://launchpad.net/ubuntu/+source/libmtp/1.1.17-2/+build/18694144 files: libmtp-common_1.1.17-2_all.deb libmtp-runtime_1.1.17-2_amd64.deb libmtp9_1.1.17-2_amd64.deb (disconnect phone and after installation log out and log in back to the system or reboot for new libraries to be loaded) Now listing files is quick and I can actually transfer files. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1792085 Title: Regression: MTP not working/very slow To manage notifications about this bug go to: https://bugs.launchpad.net/libmtp/+bug/1792085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1800465] Re: Vulkan error when using NVIDIA-Prime
In general nvidia-drm.modeset=1 is required to have Nvidia PRIME enabled, which reduces (or even removes) tearing of moving images on Optimus setups. KMS - kernel mode settings, allows kernel to control video card and in Optimus setups, among other features, this allows to synchronize graphics buffers by both graphics cards - so there are no artifacts/tearing/etc, because before displaying anything on monitor buffers are fully copied from one card to another. When modeset is disabled for Nvidia driver - buffers of both graphics cards cannot be synchronized properly so sometimes images that are displayed are only partially updated and this is visible as taring or other similar artifacts (part of the screen is filled with current frame and part of the screen is filled with previous frame). The problem is that for some reason when KMS is enabled for Nvidia driver - vulkan requires root privileges to be initialized properly. After initialization for the first time (as root), it can be used with normal user privileges. The bug is still there on Ubuntu 18.04 with newer drivers and kernel: nvidia-driver-418 linux-image-4.18.0-16-generic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1800465 Title: Vulkan error when using NVIDIA-Prime To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1800465/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769857] Re: Vulkan not working if nvidia-drm.modeset=1 is set and gdm3 is used (Optimus)
The bug is still there on Ubuntu 18.04 with newer drivers and kernel: nvidia-driver-418 linux-image-4.18.0-16-generic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769857 Title: Vulkan not working if nvidia-drm.modeset=1 is set and gdm3 is used (Optimus) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1769857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769857] Re: Vulkan not working if nvidia-drm.modeset=1 is set and gdm3 is used (Optimus)
As a workaround one needs to run (after each reboot): sudo vulkaninfo and then all vulkan apps start to work properly until system is shut down. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769857 Title: Vulkan not working if nvidia-drm.modeset=1 is set and gdm3 is used (Optimus) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1769857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769857] Re: Vulkan not working if nvidia-drm.modeset=1 is set and gdm3 is used (Optimus)
I can confirm this is still an issue. My setup is: Ubuntu 18.04 MSI GE60 Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz Intel HD 4600 + GeForce GTX 760M nvidia-driver-396 (396.54-0ubuntu0~gpu18.04.1 from grphics-drivers PPA) nvidia-prime for switching cards With nvidia-drm.modeset=1 until some vulkan app is run as root the vulkaninfo crashes like this: == VULKANINFO == Vulkan Instance Version: 1.1.82 ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_radeon.so: wrong ELF class: ELFCLASS32 ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_intel.so: wrong ELF class: ELFCLASS32 INTEL-MESA: warning: Haswell Vulkan support is incomplete INTEL-MESA: warning: ../../../src/intel/vulkan/anv_device.c:1150: FINISHME: Implement pop-free point clipping Instance Extensions: Instance Extensions count = 17 VK_EXT_acquire_xlib_display : extension revision 1 VK_EXT_debug_report : extension revision 9 VK_EXT_debug_utils : extension revision 1 VK_EXT_direct_mode_display : extension revision 1 VK_EXT_display_surface_counter : extension revision 1 VK_KHR_device_group_creation: extension revision 1 VK_KHR_display : extension revision 23 VK_KHR_external_fence_capabilities : extension revision 1 VK_KHR_external_memory_capabilities : extension revision 1 VK_KHR_external_semaphore_capabilities: extension revision 1 VK_KHR_get_display_properties2 : extension revision 1 VK_KHR_get_physical_device_properties2: extension revision 1 VK_KHR_get_surface_capabilities2: extension revision 1 VK_KHR_surface : extension revision 25 VK_KHR_wayland_surface : extension revision 6 VK_KHR_xcb_surface : extension revision 6 VK_KHR_xlib_surface : extension revision 6 Layers: count = 3 === VK_LAYER_LUNARG_standard_validation (LunarG Standard Validation Layer) Vulkan version 1.0.82, layer version 1 Layer Extensionscount = 0 Devices count = 2 GPU id : 0 (Intel(R) Haswell Mobile) Layer-Device Extensions count = 0 GPU id : 1 (GeForce GTX 760M) Layer-Device Extensions count = 0 VK_LAYER_VALVE_steam_overlay_32 (Steam Overlay Layer) Vulkan version 1.1.73, layer version 1 Layer Extensionscount = 0 Devices count = 2 GPU id : 0 (Intel(R) Haswell Mobile) Layer-Device Extensions count = 0 GPU id : 1 (GeForce GTX 760M) Layer-Device Extensions count = 0 VK_LAYER_VALVE_steam_overlay_64 (Steam Overlay Layer) Vulkan version 1.1.73, layer version 1 Layer Extensionscount = 0 Devices count = 2 GPU id : 0 (Intel(R) Haswell Mobile) Layer-Device Extensions count = 0 GPU id : 1 (GeForce GTX 760M) Layer-Device Extensions count = 0 Presentable Surfaces: = GPU id : 0 (Intel(R) Haswell Mobile) Surface type : VK_KHR_xcb_surface Formats:count = 2 B8G8R8A8_SRGB B8G8R8A8_UNORM Present Modes: count = 3 IMMEDIATE_KHR MAILBOX_KHR FIFO_KHR VkSurfaceCapabilitiesKHR: = minImageCount = 2 maxImageCount = 0 currentExtent: width = 256 height = 256 minImageExtent: width = 256 height = 256 maxImageExtent: width = 256 height = 256 maxImageArrayLayers = 1 supportedTransform: VK_SURFACE_TRANSFORM_IDENTITY_BIT_KHR currentTransform: VK_SURFACE_TRANSFORM_IDENTITY_BIT_KHR supportedCompositeAlpha: VK_COMPOSITE_ALPHA_OPAQUE_BIT_KHR VK_COMPOSITE_ALPHA_INHERIT_BIT_KHR supportedUsageFlags: VK_IMAGE_USAGE_TRANSFER_SRC_BIT VK_IMAGE_USAGE_TRANSFER_DST_BIT VK_IMAGE_USAGE_SAMPLED_BIT VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT VkSurfaceCapabilities2EXT: == supportedSurfaceCounters: None GPU id : 1 (GeForce GTX 760M) Surface type : VK_KHR_xcb_surface vulkaninfo: /build/vulkan-tools-WIuZIg/vulkan-tools-1.1.82.0+dfsg1/vulkaninfo/vulkaninfo.c:1253: AppDumpSurfaceFormats: Assertion `!err' failed. Aborted (core dumped) I have added some logs to vulkaninfo to check what is the value of vkGetPhysicalDeviceSurfaceFormatsKHR function that leads to abort and it is: -3 (VK_ERROR_INITIALIZATION_FAILED)
[Bug 1665578] Re: http://pl.archive.ubuntu.com/ stopped syncing
It's working again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1665578 Title: http://pl.archive.ubuntu.com/ stopped syncing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1665578/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1665578] Re: http://pl.archive.ubuntu.com/ stopped syncing
Ping says that pl.archive.ubuntu.com points to ubuntu.task.gda.pl which indeed does not seem to be in sync with main server. Some other Polish mirrors, like ftp.icm.edu.pl seem to be up to date. So the problem is with some mirrors having issues with syncing with main server. I'll try to contact with task.gda.pl administrator to get some info about this issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1665578 Title: http://pl.archive.ubuntu.com/ stopped syncing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1665578/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 772109] [NEW] Polish translation - window too wide, buggy divider
Public bug reported: Binary package hint: ubiquity Natty daily build: natty-desktop-i386.iso (27-04-2010) Choosing Polish (Polski) language in installer causes it's window to resize badly. Buttons are too wide and the width of whole window is too big, it's even more than 1024px (1083px to be exact). There is no reason for such dimensions. This causes a bug when you choose to install Ubuntu alongside other system. When divider that allows to allocate drive space from biggest partition shows up, you can set desired amount of drive space but when you hit 'install now' window will change it's width (it will become narrower), which will make divider also change it's width (but it won't keep values set by user few seconds ago) and everything will end up with almost random value of drive space assigned for Ubuntu. Example: 200GB partition, divider set in the middle (100GB | 100GB) after hitting 'install now' window's resizing happened and I ended up with divider set a little bit on the right side (120GB | 80GB). The real problem seems to be the size of the window. It should keep same width all the time or divider should be able to scale with window without messing in it's values. The problem is also that Polish language makes windows being too wide during whole installation process. Tests made on VirtualBox. ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/772109 Title: Polish translation - window too wide, buggy divider -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 576496] Re: Lost ata interrupt, usb hid (mouse keyboard) freezes
New kernel seems to fix this bug for me (got exact same 'lost interrupt' errors in logs): http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.34-lucid/ After about 2 days of (not too intensive) testing everything seems to be working fine. New kernel also fixed some issues with DVD-ROM not working properly before. -- Lost ata interrupt, usb hid (mouse keyboard) freezes https://bugs.launchpad.net/bugs/576496 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 440682] Re: WARNING: at /build/buildd/linux-2.6.31/net/mac80211/agg-tx.c:145 ___ieee80211_stop_tx_ba_session+0x91/0xa0 [mac80211]()
The same bug with Dell XPS m1530 (with the same Intel Corporation PRO/Wireless 4965 AG or AGN [Kedron] Network Connection (rev 61)) on Ubuntu 9.10 (2.6.31-14-generic). -- WARNING: at /build/buildd/linux-2.6.31/net/mac80211/agg-tx.c:145 ___ieee80211_stop_tx_ba_session+0x91/0xa0 [mac80211]() https://bugs.launchpad.net/bugs/440682 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 343919] Re: Nvidia MCP67 AHCI ata timeout exception with data loss
I found somewhere on launchpad.net that adding all_generic_ide to kernel command line can be helpful and it worked in my case with very similar errors (although on Dell XPS m1530). -- Nvidia MCP67 AHCI ata timeout exception with data loss https://bugs.launchpad.net/bugs/343919 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89517] Re: Synaptics touchpad isnt detected
Try to reload psmouse module: sudo rmmod psmouse sudo modprobe psmouse and restart Xserver. -- Synaptics touchpad isnt detected https://bugs.launchpad.net/bugs/89517 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 191024] Re: Synaptics touchpad not detected
Today my touchpad was recognized as a PS/2 Generic Mouse... I have made a HAL rule to change the name and input.capabilities for thouchpad but Xserver didn't use these new settings. Reloading psmouse module helped. You can also try to change HAL info. Use the file attached to this message and change few things in it: 1. Change string in match tag to fit your situation (use the misdetected name which is shown in info.product in lshal touchpad output). FriedChicken, for example you should type there PS/2 Logitech Wheel Mouse instead of PS/2 Generic Mouse. 2. Change both merge tags with the proper name of your touchpad. For ALPS it should be AlpsPS/2 ALPS GlidePoint and for Synaptics it should be SynPS/2 Synaptics TouchPad Now you can place the file in /etc/hal/fdi/policy/ and restart HAL: sudo /etc/init.d/hal restart you can check now lshal if there are any changes (should be ;) ). You can also restart Xserver now but in my case that didn't change anything. But you can always try. Maybe reloading psmouse module will now work? ** Attachment added: alps-touchpad.fdi http://launchpadlibrarian.net/18030682/alps-touchpad.fdi -- Synaptics touchpad not detected https://bugs.launchpad.net/bugs/191024 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 191024] Re: Synaptics touchpad not detected
You could also try setting touchpad's Protocol in xorg.conf to SynPS/2 or AlpsPS/2 -- Synaptics touchpad not detected https://bugs.launchpad.net/bugs/191024 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 191024] Re: Synaptics touchpad not detected
According to what you have written this is your touchpad:
udi =
'/org/freedesktop/Hal/devices/platform_i8042_i8042_AUX3_port_logicaldev_input'
info.capabilities = {'input', 'input.mouse'} (string list)
info.category = 'input' (string)
info.parent = '/org/freedesktop/Hal/devices/platform_i8042_i8042_AUX3_port'
(string)
info.product = 'PS/2 Logitech Wheel Mouse' (string)
info.subsystem = 'input' (string)
info.udi =
'/org/freedesktop/Hal/devices/platform_i8042_i8042_AUX3_port_logicaldev_input'
(string)
input.device = '/dev/input/event8' (string)
input.originating_device =
'/org/freedesktop/Hal/devices/platform_i8042_i8042_AUX3_port' (string)
input.product = 'PS/2 Logitech Wheel Mouse' (string)
input.x11_driver = 'evdev' (string)
linux.device_file = '/dev/input/event8' (string)
linux.hotplug_type = 2 (0x2) (int)
linux.subsystem = 'input' (string)
linux.sysfs_path = '/sys/class/input/input8/event8' (string)
The only idea I have is checking BIOS setup - maybe there are some settings for
touchpad you could change?
--
Synaptics touchpad not detected
https://bugs.launchpad.net/bugs/191024
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 191024] Re: Synaptics touchpad not detected
I think that thanks to Gentoo wiki and LinuxQuestions I have found a workaround. The problem seems to be in touchpad detection for the first time psmouse module is loaded. Usually (but what is strange - not always) dmesg says something like: [ 24.992320] input: PS/2 ALPS GlidePoint as /devices/platform/i8042/serio1/input/input10 and it's wrong, it should be something like: [ 191.276394] input: AlpsPS/2 ALPS GlidePoint as /devices/platform/i8042/serio1/input/input15 The difference in PS/2 ALPS GlidePoint and AlpsPS/2 ALPS GlidePoint is the most important. When dmesg shows no Alps in front of PS/2 thouchpad is not being recognized by XServer, when there is this Alps in front of PS/2 - touchpad works as it should. The workaround for this problem is reloading psmouse module - I checked few times and loading psmouse module 2nd time always makes touchpad being detected properly. Just to check if it works for you too do this: sudo rmmod psmouse sudo modprobe psmouse and restart XServer (Ctrl+Alt+Backspace). To reload psmouse module automatically on each boot place these 2 lines in /etc/rc.local file (before the exit 0 line): /sbin/rmmod psmouse /sbin/modprobe psmouse This works for me on Dell XPS M1530. -- Synaptics touchpad not detected https://bugs.launchpad.net/bugs/191024 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 191024] Re: Synaptics touchpad not detected
I forgot to mention I'm using Ubuntu 8.04.1 Haven't tried 8.10 yet but it's possible that gsalem has just got luck and his touchpad was recognized properly or maybe there is really fix for that - I'll try to check that in the near future. For last few reboots my touchpad was detected as it should be (without need to reload psmouse module) - that's quite strange... There can be similar problems with PS/2 Synaptics TouchPad and SynPS/2 Synaptics TouchPad. FriedChicken, could you attach full lshal output? -- Synaptics touchpad not detected https://bugs.launchpad.net/bugs/191024 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
