[Desktop-packages] [Bug 1807056] Re: Occasional Keyboard freeze
What I have noticed is that the freeze occurred only once in Cinnamon. Nothing since it happened first. I will update here if some progress happens. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1807056 Title: Occasional Keyboard freeze Status in gnome-shell package in Ubuntu: Incomplete Bug description: I am using 18.04 and sometimes, whatever I type does not work. It is as if there is no keyboard connected while I have my laptop keyboard and an external keyboard connected to the machine. I even enabled On Screen Keyboard and tried to type through it. Same result. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.3 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Thu Dec 6 05:41:04 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-11-29 (6 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1807056/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
The UX391UA fix is not in 4.20 as it was already a release candidate. To get sound working on this model you'll need to download the 4.20 source, apply the patch to sound/pci/hda/patch_realtek.c then compile and install the kernel. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Committed Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA 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.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1588009] Re: "libinput bug: timer offset negative" keeps coming up in syslog
Launchpad has imported 10 comments from the remote bug at https://bugs.freedesktop.org/show_bug.cgi?id=96312. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2016-06-01T17:48:16+00:00 Wise Melon wrote: I have just recently looked in my syslog and discovered that the following message shows up a lot daily so I thought I should report it: /usr/lib/gdm3/gdm-x-session[1707]: (EE) libinput bug: timer offset negative I am running Ubuntu GNOME 16.04 with GNOME 3.20, more information (logs and other system information etc) can be found in my LaunchPad bug report that I made through apport: https://bugs.launchpad.net/ubuntu- gnome/+bug/1588009 Reply at: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1588009/comments/2 On 2016-06-01T22:29:56+00:00 Peter Hutterer wrote: is this reproducible? the most common cause of this is a slow compositor/X server busy with rendering. libinput does timer setups based on event timestamps from the kernel and relies on the caller to keep calling libinput_dispatch() often enough, if that isn't the case then a 150ms timer may be set for an event from 500ms ago - resulting in an offset of -350ms from the current time. Unless you can reproduce this reliably with a specific interaction there is not much we can do here. Reply at: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1588009/comments/3 On 2016-06-17T00:57:24+00:00 Peter Hutterer wrote: any updates here? Reply at: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1588009/comments/4 On 2016-07-13T00:47:55+00:00 Peter Hutterer wrote: Closing after almost a month of no updates Reply at: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1588009/comments/5 On 2016-08-15T16:49:55+00:00 termite wrote: I've been getting a lot of this since switching to using Gnome on Wayland (from X). My system freezes completely, and I need to hard restart. Looking at /var/log/messages, I see a lot of these errors just before the freeze, plus: org.gnome.Shell.desktop[2961]: libinput error: kernel bug: Touch jump detected and discarded. debian-x1yoga org.gnome.Shell.desktop[2961]: See https://wayland.freedesktop.org/libinput/doc/1.4.0/touchpad_jumping_cursor.html for details I'd be happy to help if you let me know how. Reply at: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1588009/comments/6 On 2016-08-18T05:44:21+00:00 Peter Hutterer wrote: The jumping touch is unrelated and can be ignored for this bug. But comment #1 still stands, this is almost always a slow compositor. Reply at: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1588009/comments/7 On 2017-07-01T04:55:00+00:00 Bahodir wrote: I have the same issue and would like to help with consistent steps to reproduce the bug. Please let me know what information I can share. Reply at: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1588009/comments/8 On 2017-07-03T03:54:14+00:00 Peter Hutterer wrote: Here's a patch that'll make tracking things down a bit easier: https://lists.freedesktop.org/archives/wayland- devel/2017-July/034396.html Reply at: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1588009/comments/9 On 2018-04-03T19:06:17+00:00 Nils Kaiser wrote: I can confirm I have this on Arch Kernel 4.15.14-1-ARCH Gnome 3.28 on Wayland on Thinkpad X1 Carbon 2017 model. Libinput version is 1.10.3 Here some sample logs: libinput error: client bug: timer event17 debounce short: offset negative (-42ms) libinput error: client bug: timer event15 trackpoint: offset negative (-1720ms) Reply at: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1588009/comments/11 On 2018-12-28T17:29:05+00:00 Thommen wrote: Hi, @Nils Kaiser I have KDE, but I have same problem on Arch Linux (4.19.12-arch1-1-ARCH) Reply at: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1588009/comments/14 ** Changed in: libinput Status: Invalid => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1588009
[Desktop-packages] [Bug 780717] Re: Using PKCS#12 file requires password for private key
Issue continues as of 18.10 I can enter a random character to get past it, but that wasn't intuitive. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/780717 Title: Using PKCS#12 file requires password for private key Status in network-manager-openvpn package in Ubuntu: Confirmed Bug description: Binary package hint: network-manager-openvpn network-manager-openvpn allows to specify PKCS#12 files instead of sep. files for CA, cert and key. That's wonderful. There's one problem though: When specifying a *.p12 file, one HAS to enter a "Private key password" even if the PKCS#12 is not password protected at all. When specifying sep. files for CA, cert and key, entering the "Private key password" is optional. Not when using the PKCS#12 file. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: network-manager-openvpn-gnome 0.8.1+git.20100810t173015.1711d04-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.38-9.43-generic 2.6.38.4 Uname: Linux 2.6.38-9-generic x86_64 Architecture: amd64 Date: Tue May 10 21:48:08 2011 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110413) ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager-openvpn UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/780717/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800550] Re: Xorg freeze
[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1800550 Title: Xorg freeze Status in xorg-server package in Ubuntu: Expired Bug description: Both during and after installation (meaning while running the USB iso and booting from HDD after) ubuntu will rapidly become unresponsive and eventually hang when my 4k monitor is plugged in. I have 2 monitors, a 1920x1080, and a 4k. Everything works absolutely perfectly if I only use the 1920 monitor (this is where I am working from right now) but the moment the other monitor is plugged in I get problems. When I cold boot into the system from the small 1920x1080 monitor and then plug in the 4k monitor, the screen on my smaller monitor will glitch before returning to normal a few seconds later, while the 4k monitor never displays an image. The OS begins to bog down, the mouse begins to lag and become less responsive. If I open the display manager I can see that ubuntu has properly detected the 4k monitor and has the correct default settings (resolution, refresh rate, etc.) but attempting to make any changes will result in an immediate crash/hang upon pressing the "apply" button. If I cold boot ubuntu with only the 4k monitor plugged in, I see purple splash screen and ubuntu logo screens (at the correct resolutions) but the monitor output stops and I see only a black screen before the login screen is reached. If I cold boot with both monitors plugged in I see the splash screen and logo, there is a brief moment where the small monitor glitches, and then I see only the magenta backdrop of the login screen but there are no UI elements, and This is only seen on the small monitor; the 4k monitor has once again lost input and turned black. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Oct 29 17:32:16 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1458:d000] NVIDIA Corporation GM204 [GeForce GTX 980] [10de:13c0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GM204 [GeForce GTX 980] [1043:8518] InstallationDate: Installed on 2018-10-29 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Gigabyte Technology Co., Ltd. Z97X-SLI ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=baa2b984-a1f5-4440-9c3e-9bfece3b4bc0 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F8 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97X-SLI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF8:bd04/21/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-SLI:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-SLI-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Z97X-SLI dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A 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 N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
[Desktop-packages] [Bug 901622] Re: Resume after pm-suspend with read-only ext4 root file system on USB disk (ext4 journal commit I/O error) )
Same issue as everyone else. I have my system(/home and the likes) on the SD Card and /boot on the internal SSD. I have my OS installed this way is because my Laptop BIOS doesn't allow booting directly from SD Card(perhaps because internally the SD Reader is connected via the PCI bus) This way the laptop boots to the regular destination(Internal SSD) then GRUB loads and then I can select my desired OS, then GRUB will find the Kernel(/boot) and then handoff to the SD Card. This all works as expected with the only problem being that my system will not suspend no matter how I try. I see a flashing cursor on screen while trying to resume from suspend and then I will get read-only errors. The only way to get past this is to do a full reboot. Most of the time requiring a full fsck to fix the orphaned inodes, etc. So what is the advisable solution? Is the problem the fact that my SD Card reader is on the PCI bus and therefore is having trouble with the hotplug driver? Could a plausible solution be to disallow the system from unmounting my SD Card? I mean after all this SD Card while *removable* isn't actually going to be removed during operation of the system, much less while in hibernate. As far as I can tell the system unmounts all sd cards so as to prevent data loss, assuming that it can be removed during suspend, and that is all fine as the majority of people benefit from this decision however how do I disable this feature? Any help would be greatly appreciated. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/901622 Title: Resume after pm-suspend with read-only ext4 root file system on USB disk (ext4 journal commit I/O error) ) Status in pm-utils package in Ubuntu: Confirmed Bug description: After the upgrade to Oneiric resume from pm-suspend no longer works, might be connected to change of kernel from 2.6.38 to 3.0.0... Issue also reported for Arch Linux and kernel 2.6.39 here: https://bbs.archlinux.org/viewtopic.php?pid=1008743 See attached dmesg output for details This is for kernel 3.0.0-14-server x86_64 (but also occured on 3.0.0-13) and a NAS booting from a USB stick. --- ApportVersion: 1.23-0ubuntu4 Architecture: amd64 DistroRelease: Ubuntu 11.10 Package: pm-utils 1.4.1-8ubuntu1 PackageArchitecture: all ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9 Tags: oneiric running-unity Uname: Linux 3.0.0-14-generic x86_64 UpgradeStatus: Upgraded to oneiric on 2011-10-17 (51 days ago) UserGroups: adm admin audio cdrom dialout dip fax floppy fuse libvirtd lpadmin netdev plugdev powerdev sambashare scanner tape video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/901622/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1673258] Re: Remove aptdaemon and drop or port its reverse-dependencies
** Description changed: aptdaemon is abandoned and unmaintained. It has already been dropped from Debian, but there are several reverse dependencies keeping it in Ubuntu. I will add bug tasks for each of those dependencies, which should be ported or dropped themselves. Then we can get rid of aptdaemon too. See this mailing list thread for more details: https://lists.ubuntu.com/archives/ubuntu-devel/2017-March/039722.html - https://bitbucket.org/ubuntu-mate/ubuntu-mate-welcome/issues/48/port- - from-aptdaemon-to-packagekit + https://github.com/ubuntu-mate/ubuntu-mate-welcome/issues/48 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1673258 Title: Remove aptdaemon and drop or port its reverse-dependencies Status in aptdaemon package in Ubuntu: New Status in apturl package in Ubuntu: New Status in dell-recovery package in Ubuntu: Fix Released Status in gnome-software package in Ubuntu: Fix Released Status in language-selector package in Ubuntu: New Status in lubuntu-software-center package in Ubuntu: Fix Released Status in mythbuntu-control-centre package in Ubuntu: Fix Released Status in sessioninstaller package in Ubuntu: New Status in software-properties package in Ubuntu: New Status in ubiquity package in Ubuntu: New Status in ubuntu-mate-meta package in Ubuntu: Fix Released Status in ubuntu-mate-welcome package in Ubuntu: New Status in update-manager package in Ubuntu: New Status in update-notifier package in Ubuntu: New Status in zeroinstall-injector package in Ubuntu: Fix Released Bug description: aptdaemon is abandoned and unmaintained. It has already been dropped from Debian, but there are several reverse dependencies keeping it in Ubuntu. I will add bug tasks for each of those dependencies, which should be ported or dropped themselves. Then we can get rid of aptdaemon too. See this mailing list thread for more details: https://lists.ubuntu.com/archives/ubuntu-devel/2017-March/039722.html https://github.com/ubuntu-mate/ubuntu-mate-welcome/issues/48 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/1673258/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1771185] Re: Secondary monitor not connecting in 18.04 LTS
FYI, HDMI output works when I switch to a terminal using CTRL_ALT_F3. It seems to not work only in graphics mode. -- You received this bug notification because you are a member of Desktop 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 (0x25a) 148.352MHz +HSync +VSync h: width 1920 start 2008 end 2052 total 2200 skew0 clock 67.43KHz v: height 1080 start 1084 end 1089 total 1125 clock 59.94Hz 1920x1080i (0x25b) 74.250MHz +HSync +VSync Interlace h: width 1920 start 2008 end 2052 total 2200 skew0 clock 33.75KHz v: height 1080 start 1084 end 1094 total 1125
[Desktop-packages] [Bug 1771185] Re: Secondary monitor not connecting in 18.04 LTS
I have the same issue here: xrandr output: Screen 0: minimum 320 x 200, current 1366 x 768, maximum 8192 x 8192 LVDS-1 connected primary 1366x768+0+0 (normal left inverted right x axis y axis) 353mm x 198mm 1366x768 60.00*+ 1360x768 59.8059.96 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 VGA-1 disconnected (normal left inverted right x axis y axis) HDMI-1 disconnected (normal left inverted right x axis y axis) DP-1 disconnected (normal left inverted right x axis y axis) DP-2 disconnected (normal left inverted right x axis y axis) SVIDEO-1 disconnected (normal left inverted right x axis y axis) -- You received this bug notification because you are a member of Desktop 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.88
[Desktop-packages] [Bug 1723857] Re: onscreen keyboard appears whenever i touch touchscreen
** Information type changed from Public to Public Security -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1723857 Title: onscreen keyboard appears whenever i touch touchscreen Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Artful: Triaged Bug description: Impact == I'm in 17.10. Whenever I touch the touchscreen, the keyboard appears. It is disabled in System Preferences > Universal Access. This didn't happen in any previous Ubuntus, including 17.04 GNOME, nor in Fedora, which is GNOME based. Test Case = 0. Find a laptop with a touch screen that works. 1. Settings > Universal Access > Typing > Screen Keyboard = OFF 2. Touch the screen. Regression Potential Workaround == https://extensions.gnome.org/extension/1326/block-caribou/ To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1723857/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1767817] Re: Full text search does not work
Even after installing Nautilus 3.30 from the staging Gnome PPA (https://launchpad.net/~gnome3-team/+archive/ubuntu/gnome3-staging?field.series_filter=cosmic), the full text search isn't working in Nautilus, but does in the terminal (tracker search xyz). Ubuntu devs, please have a look on that. Such an essential feature can't have a "low" priority on a modern OS. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1767817 Title: Full text search does not work Status in nautilus package in Ubuntu: Confirmed Bug description: Background: I have installed Tracker. It has finished indexing. I can also use Tracker's command line interface to search by content. 1. Description: Ubuntu 18.04 LTS Release: 18.04 2. nautilus: Installed: 1:3.26.3-0ubuntu4 Candidate: 1:3.26.3-0ubuntu4 Version table: *** 1:3.26.3-0ubuntu4 500 500 http://fi.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 3. I expect to be able to search files by content from Nautilus, because this feature worked in 17.10. 4. I get no results from full text search unless the search matches file names. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767817/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1710931] Re: Ctrl+N shortcut does not work when desktop has focus
One correction from the previous posting: it is not gnome but "nautilus- desktop" which handles the keyboard shortcut for ctrl-n. If nautilus- desktop is not running, then the shortcut will not have any effect. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1710931 Title: Ctrl+N shortcut does not work when desktop has focus Status in Nautilus: Expired Status in nautilus package in Ubuntu: Triaged Bug description: When a Nautilus window is open, Ctrl+N opens a new window that shows the same folder as the focused Nautilus window. However, when the desktop is focused, the shortcut doesn't work - instead I see an error that x-nautilus-desktop:// is not supported. This functionality was previously reported as working in #307229. This is on Ubuntu 17.10 Artful Aardvark (fully patched as of today) with GNOME Files 3.24.2.1. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1710931/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1792843] Re: GDM lock screen will not accept credentials and then loses keyboard?
I have almost the same issue. Using gdm3, when I lock my session (e.g. with +) the lock screen doesn't accept keyboard and mouse events at all. This all began right after the upgrade from bionic to cosmic. Another thing which might be related as it only happens when I use gdm3: When I open the activities view, it never goes away. This means: I see the launcher on the left, my desktop wallpaper overlayed with transparent black (for this dimm-effect) and this stays for ever. I can search for application, run programs either from the launcher or by searching for them or e.g. by pressing registered key combinations. The program-icons apear in the launcher as they should, but I don't see any actual program images as it appears they are all hidden beneath the activities background. When using sddm or lightdm I don't have this issues (though I have others). Software: Ubuntu cosmic amd64 with latest updates. X-Session: Gnome on Xorg Hardware: Lenovo Thinkpad x230 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1792843 Title: GDM lock screen will not accept credentials and then loses keyboard? Status in gnome-shell package in Ubuntu: Confirmed Bug description: So yesterday I got the prompt to upgrade my 16LTS system to 18. This caused a number of issues, but the most frustrating issue out of many has to be this one. After a period of inactivity, the lock screen kicks in. When I then try to log in, using the correct password, I get a spinner for about 10 seconds, the "Authentication error". After a couple of seconds "Authentication error" goes away but now it seems no keys are registering at all in the password field. I say "it seems" because I see no "*"s as I type, but I do see occasional prompts of "Authentication error" coming back, but I haven't pinpointed the circumstances - certainly not triggered by hitting ENTER, sometimes backspace? Not sure if it has anything to do with the keys. After this all I can do is log in over ssh and reboot; I'm basically locked out on the console. If I wait a while the keyboard does seem to come back but the problem is still there - my password is not accepted and then the keyboard again seems to do nothing for a while. This happens whether I have a USB keyboard connected or whether I am running Synergy and using a virtual keyboard. Mouse continues to work fine. Release and kernel: Ubuntu 18.04.1 LTS (GNU/Linux 4.15.0-34-generic x86_64) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: gnome-shell 3.28.3-0ubuntu0.18.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Tags: third-party-packages bionic Uname: Linux 4.15.0-34-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-09-16 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1792843/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1810022] Re: Totem does not play MOV file with x264 encoding
** Tags added: bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1810022 Title: Totem does not play MOV file with x264 encoding Status in totem package in Ubuntu: New Bug description: AL lib: (EE) ALCplaybackAlsa_open: Could not open playback device 'default': No such file or directory (totem:9998): Totem-WARNING **: 14:48:03.615: Failed to acquire screensaver proxy: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.ScreenSaver exited with status 1 ** Message: 14:48:03.709: Missing plugin: gstreamer|1.0|totem|H.264 (High Profile) decoder|decoder-video/x-h264, level=(string)5.1, profile=(string)high, interlace-mode=(string)progressive, chroma-format=(string)4:2:0, bit-depth-luma=(uint)8, bit-depth-chroma=(uint)8 (H.264 (High Profile) decoder) ** Message: 14:48:03.811: PackageKit: xid = 18874384 ** Message: 14:48:03.811: PackageKit: desktop_id = org.gnome.Totem.desktop ** Message: 14:48:03.812: PackageKit: Codec nice name: H.264 (High Profile) decoder ** Message: 14:48:03.812: PackageKit: ignoring field named level ** Message: 14:48:03.812: PackageKit: ignoring field named profile ** Message: 14:48:03.812: PackageKit: ignoring field named interlace-mode ** Message: 14:48:03.812: PackageKit: ignoring field named chroma-format ** Message: 14:48:03.812: PackageKit: ignoring field named bit-depth-luma ** Message: 14:48:03.812: PackageKit: ignoring field named bit-depth-chroma ** Message: 14:48:03.812: PackageKit: structure: gstreamer1(decoder-video/x-h264)()(64bit) ** Message: 14:48:03.860: PackageKit: Did not install codec: Error calling StartServiceByName for org.freedesktop.PackageKit: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.PackageKit exited with status 1 ** Message: 14:48:03.864: No installation candidate for missing plugins found. The gstreamer1.0* packages are installed and ubuntu-restricted-extras. Description: Ubuntu 18.04.1 LTS Release: 18.04 totem: Installed: 3.26.0-0ubuntu6.1 Candidate: 3.26.0-0ubuntu6.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1810022/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1306849] Re: Printing error
Still an issue with Xubuntu Cosmic, Firefox 64.0. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to foomatic-db in Ubuntu. https://bugs.launchpad.net/bugs/1306849 Title: Printing error Status in foomatic-db package in Ubuntu: Confirmed Bug description: I get the message ERROR NAME; stackunderflow COMMAND; pop OPERAND STACK; when I try to print from Firefox or anything that has a picture as part of the file. I am running saucy on an AMD64 system. so far I have tried deleting the printer and setting it up again. No change. Ubuntu 13.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/foomatic-db/+bug/1306849/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1726075] Re: [HP Pavilion Power Laptop 15-cb0xx, Realtek ALC295, Speaker, Internal] No sound at all
Same issue, HP Pavilion 15-cc178cl.
Tried:
- checking that speakers aren't muted in alsamixer & pavucontrol
- renaming /etc/modprobe.d/alsa-base.conf
- model={generic,auto,hp} in /etc/modprobe.d/alsa-base.conf
- adding these lines to ~/.config/pulse/default.pa:
https://askubuntu.com/a/1068198 (this caused pulse to fail to start)
- remapping each output pin to "Internal Speakers" in hdajackretask
Have not tried:
- uninstalling and reinstalling alsa and pulse (this appears to want to
uninstall ubuntu-desktop--is that expected?)
alsa-info: http://www.alsa-
project.org/db/?f=50bc75eae4b64a7d838f66b581e79cf696920eeb
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1726075
Title:
[HP Pavilion Power Laptop 15-cb0xx, Realtek ALC295, Speaker, Internal]
No sound at all
Status in alsa-driver package in Ubuntu:
Confirmed
Bug description:
I cannot hear anything without headphone, the speaker don't work at
all, even though after i set the speaker volume bar in the alsamixer
panel
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
Uname: Linux 4.4.0-97-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: remaincool 1862 F pulseaudio
CurrentDesktop: Unity
Date: Mon Oct 23 00:57:26 2017
InstallationDate: Installed on 2017-07-06 (108 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: 内置音频 - HDA Intel PCH
Symptom_DevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: remaincool 1862 F pulseaudio
Symptom_Jack: Speaker, Internal
Symptom_Type: No sound at all
Title: [HP Pavilion Power Laptop 15-cb0xx, Realtek ALC295, Speaker, Internal]
No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/02/2017
dmi.bios.vendor: Insyde
dmi.bios.version: F.09
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 836B
dmi.board.vendor: HP
dmi.board.version: 46.20
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnInsyde:bvrF.09:bd06/02/2017:svnHP:pnHPPavilionPowerLaptop15-cb0xx:pvrType1ProductConfigId:rvnHP:rn836B:rvr46.20:cvnHP:ct10:cvrChassisVersion:
dmi.product.name: HP Pavilion Power Laptop 15-cb0xx
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1726075/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1792843] Re: GDM lock screen will not accept credentials and then loses keyboard?
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1792843 Title: GDM lock screen will not accept credentials and then loses keyboard? Status in gnome-shell package in Ubuntu: Confirmed Bug description: So yesterday I got the prompt to upgrade my 16LTS system to 18. This caused a number of issues, but the most frustrating issue out of many has to be this one. After a period of inactivity, the lock screen kicks in. When I then try to log in, using the correct password, I get a spinner for about 10 seconds, the "Authentication error". After a couple of seconds "Authentication error" goes away but now it seems no keys are registering at all in the password field. I say "it seems" because I see no "*"s as I type, but I do see occasional prompts of "Authentication error" coming back, but I haven't pinpointed the circumstances - certainly not triggered by hitting ENTER, sometimes backspace? Not sure if it has anything to do with the keys. After this all I can do is log in over ssh and reboot; I'm basically locked out on the console. If I wait a while the keyboard does seem to come back but the problem is still there - my password is not accepted and then the keyboard again seems to do nothing for a while. This happens whether I have a USB keyboard connected or whether I am running Synergy and using a virtual keyboard. Mouse continues to work fine. Release and kernel: Ubuntu 18.04.1 LTS (GNU/Linux 4.15.0-34-generic x86_64) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: gnome-shell 3.28.3-0ubuntu0.18.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Tags: third-party-packages bionic Uname: Linux 4.15.0-34-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-09-16 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1792843/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1809940] Re: ASPEED AST2400 graphics failure on normal start but work on recovery start
** Description changed: I have an ASUS P10S-I server motherboard with integrated ASPEED AST2400 VGA chipset. With earlier Ubuntu version (maybe on Ubuntu 16.04.3 ?) it worked well. Once when I updated (but before the actual version) it went wrong. To be truth it not really the xresver...-ast's problem because this earlier not installed automatically and the poroblem was the same. When - i fond it on synaptic as uninstalled i hoped this will solv the problem - and i had installed it but it not worked at all... + i found it on synaptic as uninstalled i hoped that this will solve the + problem and i had installed it but it not worked at all... The issue: When I boot normally the login window load slowly and keybord and mouse very slow too but work. I can login. But after i login the screen not show the desktop it show diagonal stripes. (see the attachment) This stripes made from original screen but unrecognisable the things. But the items work if you can click the right places. (for example i can click on the main switch button if i have luck and Crl+Alt+Del log out me.) After i log out the login screen corrupted on the same diagonal stripe way. But also work I can re login. How it work: If I start the recovery mode and on the recovery window choose continue start normally (and nothing else needed) it works without problem. Evrithing is fine. I tried to indtal ASPEED driver but on the Softwares and Updates menu Another driver don't found it. 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 .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Engedély megtagadva: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Dec 28 00:28:01 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: ASPEED Technology, Inc. ASPEED Graphics Family [1a03:2000] (rev 30) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. ASPEED Graphics Family [1043:85f9] InstallationDate: Installed on 2017-11-20 (402 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 062a: Creative Labs Optical mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. P10S-I Series ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=1e49958f-dcf2-402d-b5ec-4e379ec72739 ro recovery nomodeset Renderer: Software SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/05/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4401 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P10S-I Series dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4401:bd03/05/2018:svnASUSTeKCOMPUTERINC.:pnP10S-ISeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP10S-ISeries:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: Server dmi.product.name: P10S-I Series dmi.product.version: System Version 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 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 xserver.bootTime: Fri Dec 28 00:17:45 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputSleep Button KEYBOARD, id 8 inputHID 062a:MOUSE, id 9 inputAT Translated Set 2 keyboard KEYBOARD, id 10 xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.23 ** Description changed: I have an ASUS P10S-I server
[Desktop-packages] [Bug 1769383] Re: Ubuntu dock/launcher is shown on the lock screen
I can confirm that I also see the following side effects*: - Lockscreen shortcut (meta + L) requires two attempts to register. - Activities button requires two attempts to register. - Icons in dock resize by a few pixels when you put your cursor over them. - Additional icons no longer appear in the dock (for applications which are not already in the favourites). * These only present themselves after I have logged out, confirmed that the dock is displaying on the lock screen and then logged back in. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1769383 Title: Ubuntu dock/launcher is shown on the lock screen Status in gnome-shell package in Ubuntu: Invalid Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: Invalid Status in gnome-shell-extension-ubuntu-dock source package in Bionic: In Progress Status in gnome-shell source package in Cosmic: Invalid Status in gnome-shell-extension-ubuntu-dock source package in Cosmic: In Progress Status in gnome-shell source package in Disco: Invalid Status in gnome-shell-extension-ubuntu-dock source package in Disco: Fix Released Bug description: [Impact] When entering the lock-screen mode, gnome-shell disables all the extensions. It can happen that under certain conditions ubuntu-dock re-enables itself, causing the ubuntu-dock to appear in the lock-screen, exposing sensitive information. One possible way to reproduce this is to enable dash-to-dock and ubuntu-dock at the same time. [Test Case] 1. Make sure ubuntu-dock is enabled 2. Enable dash-to-dock too 3. Lock the screen 4. Make sure the dock does not appear on the lock screen 5. Make sure there is no warning is the journal [Possible Regressions] Even if it's something we don't really support please make sure that you can use dash-to-dock without uninstalling ubuntu-dock. [Original Bug] After an update from ubuntu 16.04 to 18.04 the dock is aviable on the lockscreen after user login. I did not configure this knowingly. Also i can start every application which is available on the dock. Settings, virtual box, visualstudio code and so on. After the update to 18.04 i just configure the screen frequency to 144Hz and the night mode on. And attach the dock on bottom. I later undid these customizations back to configuration before, but the dock is stil aviable on lockscreen. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat May 5 18:30:16 2018 InstallationDate: Installed on 2018-04-08 (27 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to bionic on 2018-05-01 (3 days ago) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-08 (27 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell-extension-ubuntu-dock 0.9.1 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-05-01 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769383/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1810050] [NEW] screen glitch in dock
Public bug reported: i found a glitch in the dock when closing out of the screen switch menu down by the activities button. it changes back to the normal colour when the mouse cursor hovers over it. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Dec 29 15:37:21 2018 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems 2nd Generation Core Processor Family Integrated Graphics Controller [1179:fce0] InstallationDate: Installed on 2018-12-29 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181225) MachineType: TOSHIBA Satellite C650 ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=22135462-7795-4371-b6e5-dbb5a4541789 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2011 dmi.bios.vendor: INSYDE dmi.bios.version: 1.00 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDE:bvr1.00:bd04/01/2011:svnTOSHIBA:pnSatelliteC650:pvrPSC2EC-00M001:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.name: Satellite C650 dmi.product.sku: PSC2EC-00M001 dmi.product.version: PSC2EC-00M001 dmi.sys.vendor: TOSHIBA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A 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+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption disco reproducible single-occurrence ubuntu ** Attachment added: "Screenshot from 2018-12-29 15-34-17.png" https://bugs.launchpad.net/bugs/1810050/+attachment/5225716/+files/Screenshot%20from%202018-12-29%2015-34-17.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1810050 Title: screen glitch in dock Status in xorg package in Ubuntu: New Bug description: i found a glitch in the dock when closing out of the screen switch menu down by the activities button. it changes back to the normal colour when the mouse cursor hovers over it. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Dec 29 15:37:21 2018 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems 2nd Generation Core Processor Family Integrated Graphics Controller [1179:fce0] InstallationDate: Installed on 2018-12-29 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181225) MachineType: TOSHIBA Satellite C650 ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=22135462-7795-4371-b6e5-dbb5a4541789 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2011 dmi.bios.vendor: INSYDE dmi.bios.version: 1.00 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias:
[Desktop-packages] [Bug 1809940] Re: ASPEED AST2400 graphics failure on normal start but work on recovery start
** Description changed: I have an ASUS P10S-I server motherboard with integrated ASPEED AST2400 VGA chipset. With earlier Ubuntu version (maybe on Ubuntu 16.04.3 ?) it worked well. Once when I updated (but before the actual version) it went wrong. + + To be truth it not really the xresver...-ast's problem because this + earlier not installed automatically and the poroblem was the same. When + i fond it on synaptic as uninstalled i hoped this will solv the problem + and i had installed it but it not worked at all... The issue: When I boot normally the login window load slowly and keybord and mouse very slow too but work. I can login. But after i login the screen not show the desktop it show diagonal stripes. (see the attachment) This stripes made from original screen but unrecognisable the things. But the items work if you can click the right places. (for example i can click on the main switch button if i have luck and Crl+Alt+Del log out me.) After i log out the login screen corrupted on the same diagonal stripe way. But also work I can re login. How it work: If I start the recovery mode and on the recovery window choose continue start normally (and nothing else needed) it works without problem. Evrithing is fine. I tried to indtal ASPEED driver but on the Softwares and Updates menu Another driver don't found it. 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 .tmp.unity_support_test.1: - + ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Engedély megtagadva: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Dec 28 00:28:01 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: - ASPEED Technology, Inc. ASPEED Graphics Family [1a03:2000] (rev 30) (prog-if 00 [VGA controller]) -Subsystem: ASUSTeK Computer Inc. ASPEED Graphics Family [1043:85f9] + ASPEED Technology, Inc. ASPEED Graphics Family [1a03:2000] (rev 30) (prog-if 00 [VGA controller]) + Subsystem: ASUSTeK Computer Inc. ASPEED Graphics Family [1043:85f9] InstallationDate: Installed on 2017-11-20 (402 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 002: ID 062a: Creative Labs Optical mouse - 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 002: ID 062a: Creative Labs Optical mouse + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. P10S-I Series ProcEnviron: - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=hu_HU.UTF-8 - SHELL=/bin/bash + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=hu_HU.UTF-8 + SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=1e49958f-dcf2-402d-b5ec-4e379ec72739 ro recovery nomodeset Renderer: Software SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/05/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4401 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P10S-I Series dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4401:bd03/05/2018:svnASUSTeKCOMPUTERINC.:pnP10S-ISeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP10S-ISeries:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: Server dmi.product.name: P10S-I Series dmi.product.version: System Version 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 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 xserver.bootTime: Fri Dec 28 00:17:45 2018 xserver.configfile: default xserver.devices: - inputPower Button KEYBOARD, id 6 - inputPower
[Desktop-packages] [Bug 1798868] Re: Compiz Crashed with SIGSEGV [Radeon]
** Description changed: + SEE WORKAROUND AT END OF POST + Symptoms: On login, the desktop takes a long time to load, and when it does, everything blinks. It is possible (but difficult) to open a terminal and execute commands, through the right-click desktop menu. I first noticed the issue in mid-July of 2018. System: Acer 5100 Ubuntu 16.04 (64-bit) Graphics card: VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RS482M [Mobility Radeon Xpress 200] Believed to be mesa-related, as symptoms very similar to bug #1741447 and #1735594. I have been informed by a mesa developer that my issue is different because that bug affects Intel GPUs. This system has a Radeon GPU. Log files are as attached to bug #1795709. That bug was declared invalid by Apport because it says I don't have the necessary debug packages installed. However, I could not find the debug packages in the repository, so that is why I am submitting this report manually. Many thanks for any help. + + Edit 29/12/2018: + WORKAROUND + This bug is still present. However, I present a workaround. It is aimed at relatively inexperienced users like me. It guides the user through downgrading/rolling back affected packages to the most recent known working versions. + 1. Navigate to /var/log/apt in a file explorer. Open the logs until you find the offending mesa updates. In my case, the updates were installed on 15/07/18. + 2. Copy and paste the log into a text file on your desktop. Close the log. + 3. In the text file, do a ctrl+F search on "mesa" to highlight all instances of mesa-related packages. Keep these lines and delete the others. Each line should have this kind of format: + libgles2-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) (exact package name/version numbers may differ). The first number in brackets is the version of the package that you had before, the second number is the version it was upgraded to. You should end up with a list of such lines. + 4. The earlier versions of these packages can be downloaded from Launchpad. I don't know how to find them using links/searches, but the URLs look like this: + https://launchpad.net/ubuntu/xenial/amd64/libgles2-mesa/17.2.8-0ubuntu0~16.04.1. You will have to alter the url according to your architecture, package name and package version required. + 5. You will see a page with a download link on the right-hand side for a .deb file. Make a new folder on your desktop called "mesa-install" and download the .deb file there. + 6. Scroll down, and on the left, you will see any dependencies of this package. If any of them say " (=version number)" then you must make a note of these packages on your list of packages to download and install. If they have a ">=" sign, or no version number given, ignore them. + 7. Repeat steps 4 - 6 for all the packages on your list, placing the .deb files in the "mesa-install" folder. + 8. MAKE SURE ALL IMPORTANT FILES ON YOUR SYSTEM ARE BACKED UP. + 9. Open a terminal (Ctrl + Alt + T). + 10. Type "sudo dpkg -R --install /home//Desktop/mesa-install/ + Replace " with your username. This command installs all .deb files in that folder. + 11. Reboot PC. + 12. Log in to a Unity session. Rejoice in the fact that it now works (hopefully). Assuming it is now working, you need to make sure that the packages you downgraded are not subsequently upgraded automatically by Ubuntu. Ignore any offers of automatic updates until you have completed all the steps. + 13. Open a terminal and type: + sudo apt-mark hold + where "" is the name of the first package you downgraded. Press enter, enter password, etc. You should receive confirmation that the package has been held. + 14. Repeat step 13 for all packages on your list. + + Good luck to all others who have faced this problem, and fingers crossed + for a bug fix! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1798868 Title: Compiz Crashed with SIGSEGV [Radeon] Status in mesa package in Ubuntu: New Bug description: SEE WORKAROUND AT END OF POST Symptoms: On login, the desktop takes a long time to load, and when it does, everything blinks. It is possible (but difficult) to open a terminal and execute commands, through the right-click desktop menu. I first noticed the issue in mid-July of 2018. System: Acer 5100 Ubuntu 16.04 (64-bit) Graphics card: VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RS482M [Mobility Radeon Xpress 200] Believed to be mesa-related, as symptoms very similar to bug #1741447 and #1735594. I have been informed by a mesa developer that my issue is different because that bug affects Intel GPUs. This system has a Radeon GPU. Log files are as attached to bug #1795709. That bug was declared invalid by Apport because it says I don't have the necessary debug
[Desktop-packages] [Bug 1810039] Re: Volume noisy and loud with no level control [HDA Intel PCH / Realtek ALC295]
Do not know if it is a pulseaudio or a alsa-driver bug (cf. https://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/PulseAudioStoleMyVolumes/) but I think it is both: 1/ ALSA driver may not report correct dB information. 2/ PulseAudio may not correctly mix PCM into Master since changing Master volume does nothing at all. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1810039 Title: Volume noisy and loud with no level control [HDA Intel PCH / Realtek ALC295] Status in alsa-driver package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: What I expect: When I use slider volume or when I use volume up button of my laptop, I expect that the volume goes up slightly. What happens: From the mute state, one press on volume up do graphically well but in reality the volume is loud and noisy from the first step. And all other up steps do not change the volume. Doing this with `alsamixer` started show me what you can see in volume-issue.gif attached file. Indeed when I press volume up PCM volume is maxed to 100 instantly and then Speaker volume and then Master volume. In my case manually changing the PCM volume in `alsamixer` is the only way to change the actual volume of my laptop. Even changing Master volume has no effect! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jule 1680 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 29 16:04:58 2018 InstallationDate: Installed on 2018-12-29 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX390UAK.312 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX390UAK 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.:bvrUX390UAK.312:bd04/25/2017:svnASUSTeKCOMPUTERINC.:pnUX390UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX390UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX390UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1810039/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1810039] Re: Volume noisy and loud with no level control [HDA Intel PCH / Realtek ALC295]
** Also affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1810039 Title: Volume noisy and loud with no level control [HDA Intel PCH / Realtek ALC295] Status in alsa-driver package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: What I expect: When I use slider volume or when I use volume up button of my laptop, I expect that the volume goes up slightly. What happens: From the mute state, one press on volume up do graphically well but in reality the volume is loud and noisy from the first step. And all other up steps do not change the volume. Doing this with `alsamixer` started show me what you can see in volume-issue.gif attached file. Indeed when I press volume up PCM volume is maxed to 100 instantly and then Speaker volume and then Master volume. In my case manually changing the PCM volume in `alsamixer` is the only way to change the actual volume of my laptop. Even changing Master volume has no effect! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jule 1680 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 29 16:04:58 2018 InstallationDate: Installed on 2018-12-29 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX390UAK.312 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX390UAK 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.:bvrUX390UAK.312:bd04/25/2017:svnASUSTeKCOMPUTERINC.:pnUX390UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX390UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX390UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1810039/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1810039] [NEW] Volume noisy and loud with no level control [HDA Intel PCH / Realtek ALC295]
Public bug reported: What I expect: When I use slider volume or when I use volume up button of my laptop, I expect that the volume goes up slightly. What happens: >From the mute state, one press on volume up do graphically well but in reality >the volume is loud and noisy from the first step. And all other up steps do >not change the volume. Doing this with `alsamixer` started show me what you can see in volume-issue.gif attached file. Indeed when I press volume up PCM volume is maxed to 100 instantly and then Speaker volume and then Master volume. In my case manually changing the PCM volume in `alsamixer` is the only way to change the actual volume of my laptop. Even changing Master volume has no effect! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jule 1680 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 29 16:04:58 2018 InstallationDate: Installed on 2018-12-29 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX390UAK.312 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX390UAK 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.:bvrUX390UAK.312:bd04/25/2017:svnASUSTeKCOMPUTERINC.:pnUX390UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX390UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX390UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "volume-issue.gif" https://bugs.launchpad.net/bugs/1810039/+attachment/5225699/+files/volume-issue.gif -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1810039 Title: Volume noisy and loud with no level control [HDA Intel PCH / Realtek ALC295] Status in alsa-driver package in Ubuntu: New Bug description: What I expect: When I use slider volume or when I use volume up button of my laptop, I expect that the volume goes up slightly. What happens: From the mute state, one press on volume up do graphically well but in reality the volume is loud and noisy from the first step. And all other up steps do not change the volume. Doing this with `alsamixer` started show me what you can see in volume-issue.gif attached file. Indeed when I press volume up PCM volume is maxed to 100 instantly and then Speaker volume and then Master volume. In my case manually changing the PCM volume in `alsamixer` is the only way to change the actual volume of my laptop. Even changing Master volume has no effect! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jule 1680 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 29 16:04:58 2018 InstallationDate: Installed on 2018-12-29 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX390UAK.312 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX390UAK 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.:bvrUX390UAK.312:bd04/25/2017:svnASUSTeKCOMPUTERINC.:pnUX390UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX390UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX390UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1810039/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More
[Desktop-packages] [Bug 986816] Re: Inkscape crashed with SIGSEGV when saving drawing for first time
Does the bug still happen with the latest inkscape version (0.92.3)? ** Changed in: inkscape Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/986816 Title: Inkscape crashed with SIGSEGV when saving drawing for first time Status in Inkscape: Incomplete Status in inkscape package in Ubuntu: New Bug description: I created a new drawing with a copule of text boxes and three objects - two copied from the original - which was an intersection of two rounded boxes. The document saved successfully and then I got a message popup that there had been an error with Inkscape and had to close. I was able to open the document in inkscape after I selected to restart Inkscape. I am using Ubuntu 12.04, last updated mid April. Inkscape version 0.48.3.1-1ubuntu1 ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: inkscape 0.48.3.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 ApportVersion: 2.0.1-0ubuntu4 Architecture: amd64 Date: Sun Apr 22 11:37:45 2012 ExecutablePath: /usr/bin/inkscape InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328) ProcCmdline: inkscape ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f02445f8390:movzbl (%rsi),%ecx PC (0x7f02445f8390) ok source "(%rsi)" (0x) not located in a known VMA region (needed readable region)! destination "%ecx" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: inkscape StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libc.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 Title: inkscape crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/986816/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1785860] Re: Sound Over-Amplification doesn't work properly after update to 18.04
Sorry for late response. Unfortunately I can't make a screenshot for you, because I've moved to 18.10 which doesn't have such problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1785860 Title: Sound Over-Amplification doesn't work properly after update to 18.04 Status in gnome-control-center package in Ubuntu: Incomplete Bug description: It's not possible to set the sound level to more than 100% in Settings->Sound menu using the slider. When I switch on the Over-Amplification trigger the Output volume slider remains the same (it used to increas it's max value in 17.10). BUT it still possible to set volume level to more than 100% in the top bar. Ubuntu 18.04.1 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1785860/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1785860] Re: Sound Over-Amplification doesn't work properly after update to 18.04
Just remembered that I've made the screenshot for this https://answers.launchpad.net/ubuntu/+question/668679 question! So there it is https://image.ibb.co/jD1UDn/over_amplification_problem.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1785860 Title: Sound Over-Amplification doesn't work properly after update to 18.04 Status in gnome-control-center package in Ubuntu: Incomplete Bug description: It's not possible to set the sound level to more than 100% in Settings->Sound menu using the slider. When I switch on the Over-Amplification trigger the Output volume slider remains the same (it used to increas it's max value in 17.10). BUT it still possible to set volume level to more than 100% in the top bar. Ubuntu 18.04.1 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1785860/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
Some additional sysinfo with inxi: System:Host: mir Kernel: 4.20.0-042000-generic x86_64 bits: 64 Desktop: Gnome 3.30.1 Distro: Ubuntu 18.10 (Cosmic Cuttlefish) Machine: Type: Laptop System: ASUSTeK product: ZenBook S UX391UA v: 1.0 serial: Mobo: ASUSTeK model: UX391UA v: 1.0 serial: UEFI [Legacy]: American Megatrends v: UX391UA.301 date: 10/15/2018 BTW, ASUS released recently a new BIOS version, but it still doesn't solve our problem: https://www.asus.com/de/Laptops/ASUS- ZenBook-S-UX391UA/HelpDesk_BIOS/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Committed Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA 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.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
@VanVan That's strange! To be on the safe side, I even did a fresh Ubuntu 18.10 installation and updated to the 4.20 kernel with UKUU, but I still don't have sound. Neither from the internal, nor the external speakers. I've played around with alsamixer in the terminal – without success. Can somebody confirm that they got the sound running just by installing the latest kernel (4.20) on the ASUS UX391UA (that's the model this issues is actually about)? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Committed Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA 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.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1801538] Re: no sound after upgrading to ubuntu 18.10 from 18.04
*** This bug is a duplicate of bug 210472 *** https://bugs.launchpad.net/bugs/210472 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1801538 Title: no sound after upgrading to ubuntu 18.10 from 18.04 Status in pulseaudio package in Ubuntu: Confirmed Bug description: Ubuntu 18.10 does not recognize sound devices. After upgrading there is only a dummy device known. All others are gone. In tune there is no sound output to nowhere. It does not mater it headphones are plugged or not while booting. It does not matter if any usb-sound device is plugged or not. The only device show for output in mixer is "Dummy device". ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: pulseaudio 1:12.2-0ubuntu4 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: timidity 8931 F timidity /dev/snd/pcmC0D0p: timidity 8931 F...m timidity /dev/snd/seq:timidity 8931 F timidity /dev/snd/timer: timidity 8931 f timidity Date: Sat Nov 3 17:25:55 2018 InstallationDate: Installed on 2011-10-19 (2571 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to cosmic on 2018-11-03 (0 days ago) dmi.bios.date: 10/21/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.15 dmi.board.asset.tag: No Asset Tag dmi.board.name: TravelMate P643-M dmi.board.vendor: Acer dmi.board.version: V2.15 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.15 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.15:bd10/21/2013:svnAcer:pnTravelMateP643-M:pvrV2.15:rvnAcer:rnTravelMateP643-M:rvrV2.15:cvnAcer:ct9:cvrV2.15: dmi.product.family: TravelMate P643-M dmi.product.name: TravelMate P643-M dmi.product.sku: TravelMate P643-M_0681_2.15 dmi.product.version: V2.15 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1801538/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798790] Re: Ubuntu login screen never appears when using the Nvidia driver (and setting WaylandEnable=false fixes it)
This is not a problem of Wayland or Ubuntu but of Gnome and the Nvidia driver. In fact Fedora 29 has the same problem, only it has to come out a month later they deactivate the proprietary driver and force to use Noveau. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1798790 Title: Ubuntu login screen never appears when using the Nvidia driver (and setting WaylandEnable=false fixes it) Status in gdm3 package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: https://gitlab.gnome.org/GNOME/gdm/issues/435 --- The boot process hangs with the last message being "started bpfilter". There is unusual Network activity during that time. The light of the WiFi adapter is blinking a lot. I am not sure the problem is with the gdm3 package. As a matter of fact, I would remove it and let someone more experienced to set it. I'm afraid I might break something, though. The specific steps or actions you took that caused you to encounter the problem: 1. Boot Ubuntu 18.10 with the Nvidia proprietary drivers installed. The behavior you expected: I expected Ubuntu 18.10 to boot normally. The behavior you actually encountered: The computer gets stuck in a command-like environment with the last message being "started bpfilter". You can't type any commands. I have found that uninstalling the Nvidia proprietary drivers by going into recovery mode fixes the issue. Booting with the earlier kernel doesn't fix the issue. Installing the earlier v.340 driver also doesn't fix the issue. This (https://askubuntu.com/questions/1032639/ubuntu-18-04-stuck-in- boot-after-starting-gnome-display-manager-on-intel-graphic) seems relevant. This is where I found the "solution". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1798790/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 606365]
Does the import work when using nmcli (`nmcli connection import type
openvpn file $FILENAME`)?
If nmcli works, I would think this is mostly caused by Plasma NM not
using the NetworkManager OpenVPN code to import configuration files (bug
#396530), but implements an own buggy version.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-openvpn in Ubuntu.
https://bugs.launchpad.net/bugs/606365
Title:
unable to import config with inlined ca, cert, key or tls-auth
Status in NetworkManager-OpenVPN:
Fix Released
Status in plasma-nm:
New
Status in network-manager-openvpn package in Ubuntu:
Fix Released
Status in plasma-nm package in Ubuntu:
Fix Released
Bug description:
Binary package hint: network-manager-openvpn-gnome
So a client of mine runs an OpenVPN setup. It exported a client.ovpn
file but it fails to completely import this file using the network-
manager (gnome) on Ubuntu 10.04.
When I import the file, it gives me the name ("client") and gateway
("vpn.example.org") on the initial screen. No other fields are
populated even though the client.ovpn file also includes a user
certificate, server certifikate and a private key.
When I go to advanced, some (most) of the settings obviously seem to
import correct, others not at all. E.g. none of the TLS settings (key
and key direction) are imported.
From what I understand I should be able to use this without any
additional settings.
The following software is installed through aptitude:
* openvpn (2.1.0)
* openvpn-blacklist
* network-manager-openvpn
* network-manager-openvpn-gnome
To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-openvpn/+bug/606365/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 3127] Re: Firefox language settings incorrect for Aus & NZ users
can we close this issue? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/3127 Title: Firefox language settings incorrect for Aus & NZ users Status in firefox package in Ubuntu: Confirmed Bug description: I use a fully updated Dapper Beta. The languages which are in the list by default in Firefox are en-us and en. For New Zealand they should be (in this order): en-nz en-gb en en-us Perhaps the "System -> Administration -> Languages" can be used to prioritise languages etc. to improve the 'one setting, one place' philosophy which Ubuntu is attempting (for example with OOo localisations etc.). Even if the system setting was only used if a profile did not already exist it would be a great start. Two approaches could be taken to this: * the user could manually rank variants of 'English' so that I could set (in System -> Administration -> Languages) the above rankings; or * New Zealand users have the above languages set up for them; or * a section in the languages could allow the ranking manually *and* they default to the above for New Zealanders. Obviously I would like to see the same philosophy applied to all languages. One advantage in doing this may be that programs (synaptic?) could install alternative dictionaries etc. if your first choice was missing. Questions or clarifications, just ask. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/3127/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1694329]
We don't support emoji font-family name from fontconfig (bug 1424675) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1694329 Title: oversized "characters" when Noto Color Emoji font is used on a page Status in Mozilla Firefox: New Status in firefox package in Ubuntu: New Bug description: I am seeing oversized emoji characters. See a duck in attached screenshot. This duck is from Noto Color Emoji font. In previous releases of Firefox it worked fine. It also works fine on Firefox for Windows. You can test it yourself if you have the font by visiting this URL: http://chat.stackexchange.com/transcript/message/37722474#37722474 ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-21-lowlatency 4.10.0-21.23 ProcVersionSignature: Ubuntu 4.10.0-21.23-lowlatency 4.10.11 Uname: Linux 4.10.0-21-lowlatency x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 Date: Mon May 29 22:07:30 2017 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=cf2fd7df-da6e-4e8b-876e-c91fa967ae41 InstallationDate: Installed on 2011-11-13 (2024 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. GA-790XTA-UD4 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-lowlatency root=UUID=503b3cdd-770e-4354-bf3d-c917a2ebe292 ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw elevator=cfq nomdmonddf nomdmonisw nomdmonddf nomdmonisw PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.10.0-21-lowlatency N/A linux-backports-modules-4.10.0-21-lowlatency N/A linux-firmware1.164.1 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-04-16 (43 days ago) dmi.bios.date: 12/03/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: GA-790XTA-UD4 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd12/03/2009:svnGigabyteTechnologyCo.,Ltd.:pnGA-790XTA-UD4:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-790XTA-UD4:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-790XTA-UD4 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1694329/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1810022] [NEW] Totem does not play MOV file with x264 encoding
Public bug reported: AL lib: (EE) ALCplaybackAlsa_open: Could not open playback device 'default': No such file or directory (totem:9998): Totem-WARNING **: 14:48:03.615: Failed to acquire screensaver proxy: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.ScreenSaver exited with status 1 ** Message: 14:48:03.709: Missing plugin: gstreamer|1.0|totem|H.264 (High Profile) decoder|decoder-video/x-h264, level=(string)5.1, profile=(string)high, interlace-mode=(string)progressive, chroma-format=(string)4:2:0, bit-depth-luma=(uint)8, bit-depth-chroma=(uint)8 (H.264 (High Profile) decoder) ** Message: 14:48:03.811: PackageKit: xid = 18874384 ** Message: 14:48:03.811: PackageKit: desktop_id = org.gnome.Totem.desktop ** Message: 14:48:03.812: PackageKit: Codec nice name: H.264 (High Profile) decoder ** Message: 14:48:03.812: PackageKit: ignoring field named level ** Message: 14:48:03.812: PackageKit: ignoring field named profile ** Message: 14:48:03.812: PackageKit: ignoring field named interlace-mode ** Message: 14:48:03.812: PackageKit: ignoring field named chroma-format ** Message: 14:48:03.812: PackageKit: ignoring field named bit-depth-luma ** Message: 14:48:03.812: PackageKit: ignoring field named bit-depth-chroma ** Message: 14:48:03.812: PackageKit: structure: gstreamer1(decoder-video/x-h264)()(64bit) ** Message: 14:48:03.860: PackageKit: Did not install codec: Error calling StartServiceByName for org.freedesktop.PackageKit: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.PackageKit exited with status 1 ** Message: 14:48:03.864: No installation candidate for missing plugins found. The gstreamer1.0* packages are installed and ubuntu-restricted-extras. Description:Ubuntu 18.04.1 LTS Release:18.04 totem: Installed: 3.26.0-0ubuntu6.1 Candidate: 3.26.0-0ubuntu6.1 ** Affects: totem (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1810022 Title: Totem does not play MOV file with x264 encoding Status in totem package in Ubuntu: New Bug description: AL lib: (EE) ALCplaybackAlsa_open: Could not open playback device 'default': No such file or directory (totem:9998): Totem-WARNING **: 14:48:03.615: Failed to acquire screensaver proxy: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.ScreenSaver exited with status 1 ** Message: 14:48:03.709: Missing plugin: gstreamer|1.0|totem|H.264 (High Profile) decoder|decoder-video/x-h264, level=(string)5.1, profile=(string)high, interlace-mode=(string)progressive, chroma-format=(string)4:2:0, bit-depth-luma=(uint)8, bit-depth-chroma=(uint)8 (H.264 (High Profile) decoder) ** Message: 14:48:03.811: PackageKit: xid = 18874384 ** Message: 14:48:03.811: PackageKit: desktop_id = org.gnome.Totem.desktop ** Message: 14:48:03.812: PackageKit: Codec nice name: H.264 (High Profile) decoder ** Message: 14:48:03.812: PackageKit: ignoring field named level ** Message: 14:48:03.812: PackageKit: ignoring field named profile ** Message: 14:48:03.812: PackageKit: ignoring field named interlace-mode ** Message: 14:48:03.812: PackageKit: ignoring field named chroma-format ** Message: 14:48:03.812: PackageKit: ignoring field named bit-depth-luma ** Message: 14:48:03.812: PackageKit: ignoring field named bit-depth-chroma ** Message: 14:48:03.812: PackageKit: structure: gstreamer1(decoder-video/x-h264)()(64bit) ** Message: 14:48:03.860: PackageKit: Did not install codec: Error calling StartServiceByName for org.freedesktop.PackageKit: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.PackageKit exited with status 1 ** Message: 14:48:03.864: No installation candidate for missing plugins found. The gstreamer1.0* packages are installed and ubuntu-restricted-extras. Description: Ubuntu 18.04.1 LTS Release: 18.04 totem: Installed: 3.26.0-0ubuntu6.1 Candidate: 3.26.0-0ubuntu6.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1810022/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1810023] [NEW] cannot select candidate from the panel
Public bug reported: It happened twice, however, I didn't notice how to reproduce it. The problem happened suddenly (this time) when I am editing a commit message in VSCode. PROBLEM: See the attached ime.gif demo. When I type some pinyin the corresponding Chinese character is shown on the panel, I select any number, say "3", the character "重" should be selected and appear in the text area. However, the number 3 is entered. And after that the IME does not work anymore, until I switch back to English, then To Chinese again, from the system tray. Anyway, when this bug happens, I can only enter the first candidate of any pinyin (by hit space), but cannot select others by using numbers. REASON: I found that by deleting the folder ~/.cache/ibus and login again, this problem is gone. Further investigation show that problematic files are one (or more) of the following: xrfang@office:~/.cache/ibus/libpinyin$ ls user* user_bigram.db user.conf user_pinyin_index.bin user.binuser_phrase_index.bin GUESS: I am definitely sure that this is a bug, because it happened twice. I feel that I might inadvertently triggered some key combination so as to ruined one of the above files. And IBUS crashed when trying to load them. Since it might be hard to identify how these files are corrupted, and as they are cache only, I would suggest the IBUS author(s) investigate how to prevent crash when loading corrupted cache files. ** Affects: ibus (Ubuntu) Importance: Undecided Status: New ** Attachment added: "demo of select a character from the panel" https://bugs.launchpad.net/bugs/1810023/+attachment/5225635/+files/ime.gif -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1810023 Title: cannot select candidate from the panel Status in ibus package in Ubuntu: New Bug description: It happened twice, however, I didn't notice how to reproduce it. The problem happened suddenly (this time) when I am editing a commit message in VSCode. PROBLEM: See the attached ime.gif demo. When I type some pinyin the corresponding Chinese character is shown on the panel, I select any number, say "3", the character "重" should be selected and appear in the text area. However, the number 3 is entered. And after that the IME does not work anymore, until I switch back to English, then To Chinese again, from the system tray. Anyway, when this bug happens, I can only enter the first candidate of any pinyin (by hit space), but cannot select others by using numbers. REASON: I found that by deleting the folder ~/.cache/ibus and login again, this problem is gone. Further investigation show that problematic files are one (or more) of the following: xrfang@office:~/.cache/ibus/libpinyin$ ls user* user_bigram.db user.conf user_pinyin_index.bin user.binuser_phrase_index.bin GUESS: I am definitely sure that this is a bug, because it happened twice. I feel that I might inadvertently triggered some key combination so as to ruined one of the above files. And IBUS crashed when trying to load them. Since it might be hard to identify how these files are corrupted, and as they are cache only, I would suggest the IBUS author(s) investigate how to prevent crash when loading corrupted cache files. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1810023/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
