[Desktop-packages] [Bug 416421] Re: [gm45] X crash on X200s with dual monitors (using DisplayPort)
** Changed in: xserver-xorg-video-intel Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/416421 Title: [gm45] X crash on X200s with dual monitors (using DisplayPort) Status in xf86-video-intel: Fix Released Status in xserver-xorg-video-intel package in Ubuntu: Invalid Bug description: Binary package hint: xserver-xorg-video-intel Up-to-date Kubuntu Karmic. Not using Desktop Effects (compositing). I have ThinkPad X200s with X4500 graphics. I am using it in dual monitor setup with HP L2045w connected over DVI-DisplayPort. I use the following xrandr command to setup dual monitor: xrandr --verbose --output LVDS1 --mode 1440x900 --output DVI2 --mode 1680x1050 --left-of LVDS1 My system was running for about an hour and the crash happened when "debuild" called pinentry-qt4 to enter my GPG passphrase to sign the package. This is the last window that appeared on the screen. I have found the following backtrace in Xorg.log.old: Backtrace: 0: /usr/bin/X(xorg_backtrace+0x26) [0x4efff6] 1: /usr/bin/X(xf86SigHandler+0x41) [0x4850a1] 2: /lib/libc.so.6 [0x7f910cd26560] 3: /usr/lib/libpixman-1.so.0 [0x7f910e002110] 4: /usr/lib/libpixman-1.so.0(pixman_fill+0x7a) [0x7f910dffd2ca] 5: /usr/lib/xorg/modules//libfb.so(fbFill+0x2b6) [0x7f910aadb906] 6: /usr/lib/xorg/modules//libfb.so(fbPolyFillRect+0x1d2) [0x7f910aadbda2] 7: /usr/lib/xorg/modules/drivers//intel_drv.so(uxa_check_poly_fill_rect+0xf1) [0x7f910b569011] 8: /usr/lib/xorg/modules/drivers//intel_drv.so [0x7f910b565c3f] 9: /usr/lib/xorg/modules/drivers//intel_drv.so(uxa_trapezoids+0x272) [0x7f910b5662a2] 10: /usr/bin/X [0x532f6b] 11: /usr/bin/X(Dispatch+0x384) [0x44dfc4] 12: /usr/bin/X(main+0x3b5) [0x433fa5] 13: /lib/libc.so.6(__libc_start_main+0xfd) [0x7f910cd11acd] 14: /usr/bin/X [0x433429] Saw signal 11. Server aborting. Note: I am experiencing occasional hangs of this system when running with external monitor. I still did not have time to properly debug the problem in order to report the problem. I plan to do the in following days. ProblemType: Bug Architecture: amd64 Date: Thu Aug 20 15:08:03 2009 DistroRelease: Ubuntu 9.10 MachineType: LENOVO 74705HG Package: xserver-xorg-video-intel 2:2.8.0-0ubuntu2 ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.31-6-generic root=/dev/mapper/plain-root ro single ProcEnviron: LANGUAGE= PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-6.25-generic RelatedPackageVersions: xserver-xorg 1:7.4+3ubuntu5 libgl1-mesa-glx 7.5-1ubuntu1 libdrm2 2.4.12-1ubuntu1 xserver-xorg-video-intel 2:2.8.0-0ubuntu2 xserver-xorg-video-ati 1:6.12.99+git20090629.f39cafc5-0ubuntu6 SourcePackage: xserver-xorg-video-intel Uname: Linux 2.6.31-6-generic x86_64 XorgConf: Error: [Errno 2] No such file or directory: '/etc/X11/xorg.conf' dmi.bios.date: 12/19/2008 dmi.bios.vendor: LENOVO dmi.bios.version: 6DET38WW (2.02 ) dmi.board.name: 74705HG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6DET38WW(2.02):bd12/19/2008:svnLENOVO:pn74705HG:pvrThinkPadX200s:rvnLENOVO:rn74705HG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 74705HG dmi.product.version: ThinkPad X200s dmi.sys.vendor: LENOVO fglrx: Not loaded system: distro: Ubuntu architecture: x86_64kernel: 2.6.31-6-generic [lspci] 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) Subsystem: Lenovo Device [17aa:20e4] To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/416421/+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 659792] Re: starting java gui app X crashes
** Changed in: xorg-server Status: Confirmed => Fix Released -- 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/659792 Title: starting java gui app X crashes Status in X.Org X server: Fix Released Status in xorg-server package in Ubuntu: Fix Released Bug description: after upgrading to maverick starting java gui app inside eclipse X crashes kern.log Oct 13 11:19:30 luca-laptop kernel: [10636.469399] eclipse[11981] trap divide error ip:7ff1089df9c0 sp:7fff5dc1fe60 error:0 in libgtk-x11-2.0.so.0.2200.0[7ff1088ba000+412000] xorg.0.log.old Backtrace: [ 10634.359] 0: /usr/bin/X (xorg_backtrace+0x28) [0x4a0fa8] [ 10634.359] 1: /usr/bin/X (0x40+0x60fcd) [0x460fcd] [ 10634.359] 2: /lib/libpthread.so.0 (0x7fa4bb939000+0xfb40) [0x7fa4bb948b40] [ 10634.359] 3: /usr/lib/xorg/modules/libfb.so (fbCopyNtoN+0x6e) [0x7fa4b78f222e] [ 10634.359] 4: /usr/lib/xorg/extra-modules/modules/glesx.so (0x7fa4b584c000+0x36709) [0x7fa4b5882709] [ 10634.359] 5: /usr/lib/xorg/extra-modules/modules/glesx.so (0x7fa4b584c000+0x37e75) [0x7fa4b5883e75] [ 10634.359] 6: /usr/bin/X (0x40+0xd82e0) [0x4d82e0] [ 10634.360] 7: /usr/bin/X (0x40+0xd13d9) [0x4d13d9] [ 10634.360] 8: /usr/bin/X (0x40+0x2c2d9) [0x42c2d9] [ 10634.360] 9: /usr/bin/X (0x40+0x2184b) [0x42184b] [ 10634.360] 10: /lib/libc.so.6 (__libc_start_main+0xfe) [0x7fa4ba8a4d8e] [ 10634.360] 11: /usr/bin/X (0x40+0x213d9) [0x4213d9] [ 10634.360] Segmentation fault at address 0x18 [ 10634.360] Caught signal 11 (Segmentation fault). Server aborting [ 10634.360] Program received signal SIGSEGV, Segmentation fault. fbCopyNtoN (pSrcDrawable=0x2d6eee0, pDstDrawable=0x2d6eee0, pGC=0x23dcf68, pbox=0x7fffdccc4300, nbox=, dx=, dy=-1, reverse=0, upsidedown=0, bitplane=0, closure=0x0) at ../../fb/fbcopy.c:78 78 ../../fb/fbcopy.c: No such file or directory. in ../../fb/fbcopy.c (gdb) backtrace full #0 fbCopyNtoN (pSrcDrawable=0x2d6eee0, pDstDrawable=0x2d6eee0, pGC=0x23dcf68, pbox=0x7fffdccc4300, nbox=, dx=, dy=-1, reverse=0, upsidedown=0, bitplane=0, closure=0x0) at ../../fb/fbcopy.c:78 alu = 3 '\003' pm = 4294967295 src = 0x68030b0010 srcStride = srcBpp = 32719 srcXoff = 0 srcYoff = 15 dst = 0x7fffdccc4050 dstStride = dstBpp = dstXoff = 6292235 dstYoff = 16 #1 0x7fcf5a0757c9 in ?? () from /usr/lib/xorg/extra-modules/modules/glesx.so No symbol table info available. #3 0x004d82e0 in damageComposite (op=224 '\340', pSrc=, pMask=, pDst=0x2d9df70, xSrc=1, ySrc=0, xMask=, yMask=, xDst=0, yDst=31, width=4943, height=) at ../../../miext/damage/damage.c:640 pScreen = #4 0x004d13d9 in ProcRenderComposite (client=0x2b8c660) at ../../render/render.c:723 pSrc = 0x2d9df70 pMask = 0x0 pDst = 0x2d9df70 #5 0x0042c2d9 in Dispatch () at ../../dix/dispatch.c:432 result = client = 0x2b8c660 nready = 0 start_tick = 2600 #6 0x0042184b in main (argc=9, argv=0x7fffdccc46a8, envp=) at ../../dix/main.c:291 i = 1 alwaysCheckForInput = {0, 1} --- Architecture: amd64 DistroRelease: Ubuntu 10.10 DkmsStatus: psmouse, 2.6.35-22-generic, 2.6.35-22-generic, x86_64: installed vboxhost, 3.2.10, 2.6.35-22-generic, x86_64: installed fglrx, 8.783, 2.6.35-22-generic, x86_64: installed InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) MachineType: Hewlett-Packard HP Compaq 8510p NonfreeKernelModules: fglrx Package: xorg-server (not installed) PccardctlStatus: Socket 0: no card Socket 1: 3.3V 16-bit PC Card Subdevice 0 (function 0) bound to driver "pata_pcmcia" ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic root=UUID=b88cca9c-6a78-4142-bec3-8c40baa05a34 ro quiet splash nomodeset video=uvesafb:mode_option=1280x1024-24,mtrr=3,scroll=ywrap ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4 Tags: maverick maverick Uname: Linux 2.6.35-22-generic x86_64 UserGroups: adm admin audio cdrom dialout dip fax fuse lpadmin netdev plugdev sambashare vboxusers video dmi.bios.date: 02/05/2008 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.0F dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.36 dmi.chassis.asset.tag: CNU82305SJ dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.0F:bd02/05/2008:svnHewlett-Packard:pnHPCompaq8510p:pvrF.0F:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP Compaq 8510p
[Desktop-packages] [Bug 416421]
commit 1b94fd77792310c80b0a2bcf4bf6d4e4c4c23bca Author: Alex Orange Date: Fri Oct 3 15:41:38 2014 -0600 fb: Fix Bresenham algorithms for commonly used small segments. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/416421 Title: [gm45] X crash on X200s with dual monitors (using DisplayPort) Status in xf86-video-intel: Fix Released Status in xserver-xorg-video-intel package in Ubuntu: Invalid Bug description: Binary package hint: xserver-xorg-video-intel Up-to-date Kubuntu Karmic. Not using Desktop Effects (compositing). I have ThinkPad X200s with X4500 graphics. I am using it in dual monitor setup with HP L2045w connected over DVI-DisplayPort. I use the following xrandr command to setup dual monitor: xrandr --verbose --output LVDS1 --mode 1440x900 --output DVI2 --mode 1680x1050 --left-of LVDS1 My system was running for about an hour and the crash happened when "debuild" called pinentry-qt4 to enter my GPG passphrase to sign the package. This is the last window that appeared on the screen. I have found the following backtrace in Xorg.log.old: Backtrace: 0: /usr/bin/X(xorg_backtrace+0x26) [0x4efff6] 1: /usr/bin/X(xf86SigHandler+0x41) [0x4850a1] 2: /lib/libc.so.6 [0x7f910cd26560] 3: /usr/lib/libpixman-1.so.0 [0x7f910e002110] 4: /usr/lib/libpixman-1.so.0(pixman_fill+0x7a) [0x7f910dffd2ca] 5: /usr/lib/xorg/modules//libfb.so(fbFill+0x2b6) [0x7f910aadb906] 6: /usr/lib/xorg/modules//libfb.so(fbPolyFillRect+0x1d2) [0x7f910aadbda2] 7: /usr/lib/xorg/modules/drivers//intel_drv.so(uxa_check_poly_fill_rect+0xf1) [0x7f910b569011] 8: /usr/lib/xorg/modules/drivers//intel_drv.so [0x7f910b565c3f] 9: /usr/lib/xorg/modules/drivers//intel_drv.so(uxa_trapezoids+0x272) [0x7f910b5662a2] 10: /usr/bin/X [0x532f6b] 11: /usr/bin/X(Dispatch+0x384) [0x44dfc4] 12: /usr/bin/X(main+0x3b5) [0x433fa5] 13: /lib/libc.so.6(__libc_start_main+0xfd) [0x7f910cd11acd] 14: /usr/bin/X [0x433429] Saw signal 11. Server aborting. Note: I am experiencing occasional hangs of this system when running with external monitor. I still did not have time to properly debug the problem in order to report the problem. I plan to do the in following days. ProblemType: Bug Architecture: amd64 Date: Thu Aug 20 15:08:03 2009 DistroRelease: Ubuntu 9.10 MachineType: LENOVO 74705HG Package: xserver-xorg-video-intel 2:2.8.0-0ubuntu2 ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.31-6-generic root=/dev/mapper/plain-root ro single ProcEnviron: LANGUAGE= PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-6.25-generic RelatedPackageVersions: xserver-xorg 1:7.4+3ubuntu5 libgl1-mesa-glx 7.5-1ubuntu1 libdrm2 2.4.12-1ubuntu1 xserver-xorg-video-intel 2:2.8.0-0ubuntu2 xserver-xorg-video-ati 1:6.12.99+git20090629.f39cafc5-0ubuntu6 SourcePackage: xserver-xorg-video-intel Uname: Linux 2.6.31-6-generic x86_64 XorgConf: Error: [Errno 2] No such file or directory: '/etc/X11/xorg.conf' dmi.bios.date: 12/19/2008 dmi.bios.vendor: LENOVO dmi.bios.version: 6DET38WW (2.02 ) dmi.board.name: 74705HG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6DET38WW(2.02):bd12/19/2008:svnLENOVO:pn74705HG:pvrThinkPadX200s:rvnLENOVO:rn74705HG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 74705HG dmi.product.version: ThinkPad X200s dmi.sys.vendor: LENOVO fglrx: Not loaded system: distro: Ubuntu architecture: x86_64kernel: 2.6.31-6-generic [lspci] 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) Subsystem: Lenovo Device [17aa:20e4] To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/416421/+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 1763252] Re: cant launch
[Expired for evince (Ubuntu) because there has been no activity for 60 days.] ** Changed in: evince (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1763252 Title: cant launch Status in evince package in Ubuntu: Expired Bug description: IDK ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: evince 3.28.2-1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Apr 12 11:55:47 2018 InstallationDate: Installed on 2018-03-21 (21 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180319) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1763252/+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 1763401] Re: 17.10: gnome-shell regularly locks up in VirtualBox - unity is still fine
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- 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/1763401 Title: 17.10: gnome-shell regularly locks up in VirtualBox - unity is still fine Status in gnome-shell package in Ubuntu: Expired Bug description: Repro: * VirtualBox Version 5.2.8 r121009 (Qt5.6.2) * Windows 7 host * VirtualBox 3D Acceleration enabled, given 128MB video memory * VirtualBox guest additions installed. * Log in with either Ubuntu (Xorg) or GNOME (Xorg) (both are actually gnome-shell) * Open a File browser or a Terminal, or probably anything * Maximize the window (this part is also pretty slow) * Unmaximize the window Expected: * Maximize and unmaximize take a fraction of a second. System operates as normal afterwards. Actual * Maximize is already pretty slow - the first frame of the animation takes a few seconds to render and then freezes, then a few more seconds later the window is full screen. * Unmaximize just locks up gnome-shell for 30s or so. Eventually it repaints, but the shell is now completely unusable - no more repaints. I waited minutes and it still didn't come back to life. This happens 100% of the time. I *can* switch to another VT, and log in in text mode, and see that gnome-shell is occasionally showing activity at 40+%. I can switch back to GNOME and still see the frozen screen. NB: Unity works fine, as it did in 17.04. I suspect something that gnome-shell does with OpenGL that unity didn't do is triggering a software fallback or something. Is there any way to run a diagnostic to test / benchmark the OpenGL capabilities used by gnome-shell? Thanks, apologies in advance if I missed any critical information. Happy to provide more system details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1763401/+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 1091793] Re: Quirk for 2-button mouse Cirque Corporation 9925 AG Touch
I've got a 4 button model, the GP410U-5021, it also identifies as a 9925 AG Touch. Bus 001 Device 012: ID 0488:0281 Cirque Corp. Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x0488 Cirque Corp. idProduct 0x0281 bcdDevice4.80 iManufacturer 1 Cirque Corporation iProduct2 9925 AG Touchpad iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 34 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xa0 (Bus Powered) Remote Wakeup MaxPower 20mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 1 Boot Interface Subclass bInterfaceProtocol 2 Mouse iInterface 3 USB HID Device Descriptor: bLength 9 bDescriptorType33 bcdHID 1.11 bCountryCode 33 US bNumDescriptors 1 bDescriptorType34 Report wDescriptorLength 54 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x000d 1x 13 bytes bInterval 10 Device Status: 0x (Bus Powered) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1091793 Title: Quirk for 2-button mouse Cirque Corporation 9925 AG Touch Status in xserver-xorg-input-evdev package in Ubuntu: New Bug description: /dev/input/event4 bustype : BUS_USB vendor : 0x488 product : 0x280 version : 273 name: "Cirque Corporation 9925 AG Touch" phys: "usb-:00:1a.0-1.1.1.1/input0" uniq: "" bits ev : EV_SYN EV_KEY EV_REL EV_MSC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1091793/+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 1089105] Re: [Lenovo V480c Notebook]: Trackpad doesn't work after closing and opening the lid
Precise EOL. ** Changed in: pm-utils (Ubuntu Precise) Status: New => Won't Fix ** Changed in: pm-utils (Ubuntu) Status: New => Won't Fix -- 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/1089105 Title: [Lenovo V480c Notebook]: Trackpad doesn't work after closing and opening the lid Status in linux package in Ubuntu: Won't Fix Status in pm-utils package in Ubuntu: Won't Fix Status in linux source package in Precise: Won't Fix Status in pm-utils source package in Precise: Won't Fix Status in linux source package in Quantal: Won't Fix Status in pm-utils source package in Quantal: Won't Fix Status in linux source package in Raring: Won't Fix Status in pm-utils source package in Raring: Won't Fix Bug description: Problem: System does not resume from suspend properly. The issue is intermitent. However most of the time the system will exhibit three problematic symptoms: 1.) System will fail to resume and start x altogether 2.) System will resume with applications in frozen state and unity unresponsive to mouse-clicks. 3.) System will resume however trackpad will be disabled. kernel tested: 3.2.0-29-generic #46-Ubuntu Release: Ubuntu 12.04.1 Can reproduce? Yes Steps: 1.) Close laptop lid 2.) wait approx 5 minutes 3.) open laptop lid for system to resume. Expected result: System is able to suspend state and applications and resume when lid is opened in a proper and timely fashion. Command to recreate: fwts_test -s s3 --s3-sleep-delay=30 --s3-device-check | tee suspend_single_times.log WORKAROUND: Log into GNOME, and manually enable the touchpad through: dconf-editor->/org/gnome/settings-daemon/peripherals/touchpad/touchpad-enabled ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-29-generic 3.2.0-29.46 ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24 Uname: Linux 3.2.0-29-generic x86_64 NonfreeKernelModules: wl AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu12 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC269VC Analog [ALC269VC Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1579 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0x9b61 irq 46' Mixer name : 'Intel PantherPoint HDMI' Components : 'HDA:10ec0269,17aa500f,00100202 HDA:80862806,80860101,0010' Controls : 26 Simple ctrls : 12 Card29.Amixer.info: Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw unknown' Mixer name : 'ThinkPad EC (unknown)' Components : '' Controls : 1 Simple ctrls : 1 Card29.Amixer.values: Simple mixer control 'Console',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Date: Tue Dec 11 15:38:03 2012 HibernationDevice: RESUME=UUID=98d6d8c6-aa75-4069-9714-4f972d11aa61 InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) MachineType: LENOVO 814TF01 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-29-generic root=UUID=c1701df9-c6b6-4425-b6ec-5fede7c00ad6 ro quiet splash initcall_debug vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.2.0-29-generic N/A linux-backports-modules-3.2.0-29-generic N/A linux-firmware1.79 SourcePackage: linux StagingDrivers: mei UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2012 dmi.bios.vendor: LENOVO dmi.bios.version: H5ET26WW (0.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 814TF01 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrH5ET26WW(0.26):bd03/29/2012:svnLENOVO:pn814TF01:pvrLenovoV480c:rvnLENOVO:rn814TF01:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 814TF01 dmi.product.version: Lenovo V480c dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1089105/+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 1697535] Re: [Envy24 ICE1724] Audio doesn't work
This bug still exists in Ubuntu 18.04 $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04 LTS Release:18.04 Codename: bionic $ pulseaudio --version pulseaudio 11.1 -- 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/1697535 Title: [Envy24 ICE1724] Audio doesn't work Status in pulseaudio package in Ubuntu: New Bug description: Release: Ubuntu 17.04 PulseAudio Version: 1:10.0-1ubuntu2 I expected the audio on my system to work without any additional action on my part. Instead, the audio does not work despite working on Windows. A few years ago, my onboard sound broke so I bought a pci sound card (ENCORE ENM232-8VIA 7.1) which seems to have the Envy24 ICE1724 chipset. This sound card works on Windows but not Ubuntu or Debian. I've attempted to troubleshoot this myself over the past year or so and had no luck figuring out the problem (though ubuntu-bug seems to think there is a problem with pulseaudio). ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: pulseaudio 1:10.0-1ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/pcmC1D1c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity:Unity7 Date: Mon Jun 12 14:00:25 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-12-10 (184 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to zesty on 2017-04-18 (55 days ago) dmi.bios.date: 09/11/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1104 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5QL-E dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 2.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1104:bd09/11/2009:svnSystemmanufacturer:pnP5QL-E:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5QL-E:rvrRev2.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5QL-E dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1697535/+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 1776362] Re: package libpoppler-glib8:amd64 0.62.0-2ubuntu2.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1776362 Title: package libpoppler-glib8:amd64 0.62.0-2ubuntu2.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in poppler package in Ubuntu: New Bug description: did not install after clean boot. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libpoppler-glib8:amd64 0.62.0-2ubuntu2.1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_39 wl ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: libpoppler73:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Mon Jun 11 20:06:11 2018 DuplicateSignature: package:libpoppler-glib8:amd64:0.62.0-2ubuntu2.1 Processing triggers for libc-bin (2.27-3ubuntu1) ... dpkg: error processing package libpoppler-glib8:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2018-06-11 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: poppler Title: package libpoppler-glib8:amd64 0.62.0-2ubuntu2.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1776362/+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 1754759] Re: LAN connection keeps connecting and disconnecting in an infinite loop
Markus Baumann, thank you for reporting this and helping make Ubuntu better. 1) To clarify, if you don't adjust the MTU does the LAN network still connection cycle? 2) To see if this is already resolved in Ubuntu, could you please test http://cdimage.ubuntu.com/daily-live/current/ and advise to the results? ** Tags added: bios-outdated-2.72 regression-release ** No longer affects: network-manager (Ubuntu) ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1754759 Title: LAN connection keeps connecting and disconnecting in an infinite loop Status in linux package in Ubuntu: Incomplete Bug description: With Xubuntu 17.10 the following problem occurs on a Lenovo X230 Laptop: - Boot from live-ISO - Click on network icon in title bar and edit LAN-connection - Change MTU from Auto to 1492 - Connect LAN cable => LAN network keeps connecting and disconnecting in an infinite loop (No wireless network is configured.) The error did not occur on Xubuntu 16.04. The same situation occurs with Xubuntu installed on the SSD. I took the ISO for this bug report, in order to exclude wrong settings on the installed system. This is my first bug report - I hope I did not do too much wrong. If necessary, I can provide more information. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: network-manager 1.8.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CasperVersion: 1.387 CurrentDesktop: XFCE Date: Fri Mar 9 20:26:21 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 10.110.120.1 dev enp0s25 proto static metric 100 10.110.120.0/24 dev enp0s25 proto kernel scope link src 10.110.120.57 metric 100 169.254.0.0/16 dev enp0s25 scope link metric 1000 LiveMediaBuild: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Wired connection 1 db135360-f229-3472-bd3a-eb8d6bc8b601 802-3-ethernet 1520627169 Fr 09 Mär 2018 20:26:09 UTC yes 4294966297no /org/freedesktop/NetworkManager/Settings/1 yes enp0s25 activated /org/freedesktop/NetworkManager/ActiveConnection/32 -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH enp0s25 ethernet connected /org/freedesktop/NetworkManager/Devices/2 Wired connection 1 db135360-f229-3472-bd3a-eb8d6bc8b601 /org/freedesktop/NetworkManager/ActiveConnection/32 wlp3s0 wifi disconnected /org/freedesktop/NetworkManager/Devices/3 -- ---- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.8.4connected started full enabled enabled enabled enabled enabled --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xubuntu3822 F pulseaudio CasperVersion: 1.387 DistroRelease: Ubuntu 17.10 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 10.110.120.1 dev enp0s25 proto static metric 100 10.110.120.0/24 dev enp0s25 proto kernel scope link src 10.110.120.57 metric 100 169.254.0.0/16 dev enp0s25 scope link metric 1000 LiveMediaBuild: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105) MachineType: LENOVO 2333B15 Package: network-manager 1.8.4-1ubuntu3 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash ---
[Desktop-packages] [Bug 1776362] [NEW] package libpoppler-glib8:amd64 0.62.0-2ubuntu2.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempti
Public bug reported: did not install after clean boot. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libpoppler-glib8:amd64 0.62.0-2ubuntu2.1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_39 wl ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: libpoppler73:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Mon Jun 11 20:06:11 2018 DuplicateSignature: package:libpoppler-glib8:amd64:0.62.0-2ubuntu2.1 Processing triggers for libc-bin (2.27-3ubuntu1) ... dpkg: error processing package libpoppler-glib8:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2018-06-11 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: poppler Title: package libpoppler-glib8:amd64 0.62.0-2ubuntu2.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: poppler (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1776362 Title: package libpoppler-glib8:amd64 0.62.0-2ubuntu2.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in poppler package in Ubuntu: New Bug description: did not install after clean boot. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libpoppler-glib8:amd64 0.62.0-2ubuntu2.1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_39 wl ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: libpoppler73:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Mon Jun 11 20:06:11 2018 DuplicateSignature: package:libpoppler-glib8:amd64:0.62.0-2ubuntu2.1 Processing triggers for libc-bin (2.27-3ubuntu1) ... dpkg: error processing package libpoppler-glib8:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2018-06-11 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: poppler Title: package libpoppler-glib8:amd64 0.62.0-2ubuntu2.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1776362/+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 110809] Re: [patch] xserver-xorg-core: Fixes Xinerama Not Respecting Display Boundries
Launchpad has imported 5 comments from the remote bug at https://bugs.freedesktop.org/show_bug.cgi?id=10797. 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 2007-04-28T09:35:52+00:00 Dieter Hering wrote: These patches to the xserver, fix the problem of xinerama not respecting display boundries. For instance when multi-monitors are used, clicking "expand" spreads the application across multiple screens instead of the single monitor. This problem is especially noticeable with dual/triple head cards are used in conjunction with xinerama and lower level controls like nVidia's TwinView. To use and for further details see: http://www.nvnews.net/vbulletin/showthread.php?t=85604 Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/110809/comments/0 On 2007-04-28T09:38:21+00:00 Dieter Hering wrote: Created attachment 9768 Fixes xinerama not respecting display boundries in multi-monitors Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/110809/comments/1 On 2007-04-28T09:39:17+00:00 Dieter Hering wrote: Created attachment 9769 Fixes Xinerama not respecting display boundries, multi-monitor Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/110809/comments/2 On 2008-02-24T19:01:15+00:00 Ajax-a wrote: This code looks implausible, but there's surely something legitimate here. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/110809/comments/6 On 2008-03-24T12:06:43+00:00 Ajax-a wrote: No sir, I don't like it. The idea here is to control the Xinerama geometry exported to clients when doing both multiple monitors per card and multiple cards. But the right solution to that is to split the geometry reported through the Xinerama protocol from the Xinerama dispatch multiplexer, and allow driver subsystems the ability to report their own geometry. Stuffing the desired geometry in xorg.conf is certainly a solution, but it's not something I want to ship lest people start relying on it. Taking this off the 7.4 blocker. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/110809/comments/7 ** Changed in: xorg-server Status: Confirmed => Invalid -- 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/110809 Title: [patch] xserver-xorg-core: Fixes Xinerama Not Respecting Display Boundries Status in X.Org X server: Invalid Status in xorg-server package in Ubuntu: Won't Fix Bug description: Binary package hint: xserver-xorg-core The supplied -p1 patch to xserver-xorg-core -1.2.0 fixes the problem of Xinerama not respecting display boundries in multi-monitors. When using dual/triple head cards, xinerama doesn't respect the monitor's display boundries when clicking the "expand" button. (application spreads across multiple monitors instead of single display) The patch I submitted below fixes the problem thanks to Bernhard (Jaxxon) on the nvNews forum. See this thread's post #10 for how to use: http://www.nvnews.net/vbulletin/showthread.php?t=85604 I also submitted this patch upstream to Xorg. To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/110809/+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 1757561] Re: Wifi disconnects randomly under ubuntu 17.10
Mijail Febres Soria, to see if this is already resolved in Ubuntu, could you please test http://cdimage.ubuntu.com/daily-live/current/ and advise to the results? ** No longer affects: network-manager (Ubuntu) ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Attachment removed: "RfKill.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087454/+files/RfKill.txt ** Attachment removed: "PulseList.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087453/+files/PulseList.txt ** Attachment removed: "ProcInterrupts.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087451/+files/ProcInterrupts.txt ** Attachment removed: "ProcEnviron.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087450/+files/ProcEnviron.txt ** Attachment removed: "ProcModules.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087452/+files/ProcModules.txt ** Attachment removed: "PciNetwork.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087448/+files/PciNetwork.txt ** Attachment removed: "NetworkManager.conf.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087447/+files/NetworkManager.conf.txt ** Attachment removed: "NetDevice.wlp3s0.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087446/+files/NetDevice.wlp3s0.txt ** Attachment removed: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087449/+files/ProcCpuinfoMinimal.txt ** Attachment removed: "NetDevice.lo.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087445/+files/NetDevice.lo.txt ** Attachment removed: "NetDevice.enp4s0.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087444/+files/NetDevice.enp4s0.txt ** Attachment removed: "JournalErrors.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087441/+files/JournalErrors.txt ** Attachment removed: "IwConfig.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087440/+files/IwConfig.txt ** Attachment removed: "Lsusb.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087443/+files/Lsusb.txt ** Attachment removed: "Lspci.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087442/+files/Lspci.txt ** Attachment removed: "Dependencies.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087438/+files/Dependencies.txt ** Attachment removed: "CRDA.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087436/+files/CRDA.txt ** Attachment removed: "CurrentDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087437/+files/CurrentDmesg.txt ** Attachment removed: "AlsaInfo.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087435/+files/AlsaInfo.txt ** Attachment removed: "nmcli-con.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087422/+files/nmcli-con.txt ** Attachment removed: "WifiSyslog.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087421/+files/WifiSyslog.txt ** Attachment removed: "RfKill.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087419/+files/RfKill.txt ** Attachment removed: "UdevDb.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087420/+files/UdevDb.txt ** Attachment removed: "ProcModules.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087417/+files/ProcModules.txt ** Attachment removed: "ProcInterrupts.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087416/+files/ProcInterrupts.txt ** Attachment removed: "ProcEnviron.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087415/+files/ProcEnviron.txt ** Attachment removed: "PulseList.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087418/+files/PulseList.txt ** Attachment removed: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087414/+files/ProcCpuinfoMinimal.txt ** Attachment removed: "PciNetwork.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087413/+files/PciNetwork.txt ** Attachment removed: "NetworkManager.conf.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087412/+files/NetworkManager.conf.txt ** Attachment removed: "NetDevice.wlp3s0.txt"
Re: [Desktop-packages] [Bug 927952] Re: When I press the Print Screen button, it will not appear in "Save Screenshot" window.
Just use ctrl+PrtSc to send to clipboard On Jun 10, 2018 10:04 PM, "Kris" wrote: Just recently upgraded to bionic, and after using it for a while I mostly got used to it, but the one feature that keeps bothering me painfully is the lack of the printscreen dialog. I understand the initiative to adopt gnome standards, but this is introducing a big inconvenience in comparison to how it was functional in the Unity desktop. It is not just about being able to save printscreens to an arbitrary location under an arbitrary name. It is even more importantly being able to copy a printscreen into a clipboard without saving it to a file on a disk. I used to be able to just copy a printscreen and Ctrl+V it into a IM window, a email client or any webapp. Now I have to take additional steps to open file manager, navigate to the Pictures folder, locate the one printscreen file I need among other ones, and drag it to where I need it, then, delete it. The functionality and user experience has decreased significantly for me, and on top of that I get constantly annoyed by it. I wish Canonical shipped the previous user experience with the new gnome-desktop based Ubuntu. Even as an opt-in! -- You received this bug notification because you are subscribed to a duplicate bug report (928364). https://bugs.launchpad.net/bugs/927952 Title: When I press the Print Screen button, it will not appear in "Save Screenshot" window. Status in Ayatana Design: Fix Released Status in Gnome Screenshot: Expired Status in gnome-screenshot package in Ubuntu: Fix Released Status in gnome-screenshot source package in Precise: Fix Released Status in gnome-screenshot package in Debian: Confirmed Bug description: When taking a screenshot with Print Screen or Alt+Print Screen a dialog box asking you what and where to save the file no longer appears. So while you hear a camera sound you have no other confirmation that a screenshot was really taken. Additionally, there is no way of knowing where the screenshot went. I'd imagine this will be particularly problematic for new users of Ubuntu. ProblemType: BugDistroRelease: Ubuntu 12.04 Package: gnome-screenshot 3.3.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-14.23-generic 3.2.3 Uname: Linux 3.2.0-14-generic x86_64 ApportVersion: 1.91-0ubuntu1 Architecture: amd64 Date: Mon Feb 6 23:54:17 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (2029.1)SourcePackage: gnome-screenshot UpgradeStatus: Upgraded to precise on 2012-01-27 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/927952/+subscriptions -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. https://bugs.launchpad.net/bugs/927952 Title: When I press the Print Screen button, it will not appear in "Save Screenshot" window. Status in Ayatana Design: Fix Released Status in Gnome Screenshot: Expired Status in gnome-screenshot package in Ubuntu: Fix Released Status in gnome-screenshot source package in Precise: Fix Released Status in gnome-screenshot package in Debian: Confirmed Bug description: When taking a screenshot with Print Screen or Alt+Print Screen a dialog box asking you what and where to save the file no longer appears. So while you hear a camera sound you have no other confirmation that a screenshot was really taken. Additionally, there is no way of knowing where the screenshot went. I'd imagine this will be particularly problematic for new users of Ubuntu. ProblemType: BugDistroRelease: Ubuntu 12.04 Package: gnome-screenshot 3.3.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-14.23-generic 3.2.3 Uname: Linux 3.2.0-14-generic x86_64 ApportVersion: 1.91-0ubuntu1 Architecture: amd64 Date: Mon Feb 6 23:54:17 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (2029.1)SourcePackage: gnome-screenshot UpgradeStatus: Upgraded to precise on 2012-01-27 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/927952/+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 1776323] [NEW] Sound cracks in video player
Public bug reported: When I play audio or video, the sound is really terrible. It goes up and down by itself ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: geektutor 1525 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jun 11 23:17:48 2018 InstallationDate: Installed on 2018-06-08 (3 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=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID failed Symptom_Card: Built-in Audio - HDA Intel MID Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: Jun 11 23:07:52 TGM dbus-daemon[840]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.28' (uid=120 pid=1039 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") Jun 11 23:07:53 TGM dbus-daemon[840]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.50' (uid=120 pid=1039 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") Jun 11 23:09:02 TGM dbus-daemon[840]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.80' (uid=1000 pid=1525 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [HP ProBook 6450b, IDT 92HD75B3X5, Speaker, Internal] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/04/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CDF Ver. F.03 dmi.board.name: 146E dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 73.11 dmi.chassis.asset.tag: CNU0452QT8 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CDFVer.F.03:bd10/04/2010:svnHewlett-Packard:pnHPProBook6450b:pvr:rvnHewlett-Packard:rn146E:rvrKBCVersion73.11:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP ProBook 6450b dmi.sys.vendor: Hewlett-Packard mtime.conffile..etc.modprobe.d.alsa-base.conf: 2018-06-11T23:17:29.683944 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1776323 Title: Sound cracks in video player Status in alsa-driver package in Ubuntu: New Bug description: When I play audio or video, the sound is really terrible. It goes up and down by itself ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: geektutor 1525 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jun 11 23:17:48 2018 InstallationDate: Installed on 2018-06-08 (3 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=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID failed Symptom_Card: Built-in Audio - HDA Intel MID Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: Jun 11 23:07:52 TGM dbus-daemon[840]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.28' (uid=120 pid=1039 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") Jun 11 23:07:53 TGM dbus-daemon[840]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.50' (uid=120 pid=1039 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") Jun 11 23:09:02 TGM dbus-daemon[840]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.80' (uid=1000 pid=1525 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [HP ProBook 6450b, IDT 92HD75B3X5, Speaker, Internal] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/04/2010
[Desktop-packages] [Bug 1770350] Re: Emoji oversized
*** This bug is a duplicate of bug 1761844 *** https://bugs.launchpad.net/bugs/1761844 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: thunderbird (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1770350 Title: Emoji oversized Status in thunderbird package in Ubuntu: Confirmed Bug description: As can be seen in the screenshots posted by another user at https://askubuntu.com/questions/1028674/my-thunderbird-version-on-18-04-have-emoji-bug (and in the attached simpler screenshot) I also have this problem. They seem to be 8-10× the size of normal text and cause lots of weird problems with the UI as it redraws. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: thunderbird 1:52.7.0+build1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: rich 1962 F...m pulseaudio /dev/snd/controlC0: rich 1962 F pulseaudio BuildID: 20180416164209 Channel: Unavailable CurrentDesktop: GNOME Date: Thu May 10 09:25:03 2018 ExecutablePath: /usr/lib/thunderbird/thunderbird Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-04-07 (32 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180403) IpRoute: default via 192.168.1.254 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.120 metric 600 Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-883982e1-dadd-4a2e-8806-066ca0180405 PrefSources: prefs.js [Profile]/extensions/{3dcf3762-4cda-4fd2-be13-13b9a10769fd}.xpi:defaults/preferences.js [Profile]/extensions/{91aa5abe-9de4-4347-b7b5-322c38dd9271}/defaults/preferences/prefs.js [Profile]/extensions/{CC3C233D-6668-41bc-AAEB-F3A1D1D594F5}/defaults/preferences/mailredirect.js ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/zsh Profiles: Profile0 (Default) - LastVersion=52.7.0/20180416164209 (In use) RunningIncompatibleAddons: False SourcePackage: thunderbird SubmittedCrashIDs: bp-883982e1-dadd-4a2e-8806-066ca0180405 bp-e53c6d14-958a-41ec-8183-a4fba2160503 bp-5046681e-ddc2-4f99-b25c-c2db02160416 bp-21fbe7af-4352-496e-b57d-6539d2150727 bp-022d6a4f-83a0-49e7-bac3-3739c2120718 Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/17/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.21 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.21:bd02/17/2017:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1770350/+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 1712200] Re: Changing keyboard layout with alt+shift always triggers "ui.key.menuAccessKey" on Wayland
The bug happens again on Ubuntu 18.04 -- 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/1712200 Title: Changing keyboard layout with alt+shift always triggers "ui.key.menuAccessKey" on Wayland Status in Mozilla Firefox: New Status in firefox package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Install Ubuntu 17.10 from final ISO-image (cdrom:[Ubuntu 17.10 _Artful Aardvark_ - Release amd64 (20171018)]), select Russian keyboard layout on installation 3. Boot into installed system and log-in 4. Try to change keyboard layout - what is interesting both keyboard shortcuts - and switch layouts. 5. Open Firefox 6. Change keyboard layout with Expected results: * keyboard layout is switched, Firefox does not react on keyboard layout switching Actual results: * during switching of keyboard layout (on clicking key) Firefox shows its mnemonics (underlines in menu) and distracts user. After pressing key keyboard layout is switched, but focus is placed on Firefox menubar. So user needs to change the focus with keyboard (for example key) or mouse click. Notes: It seems that keyboard layout switcher was quietly set in Ubiquity (see bug 1242572). - Original bug description below: I'm on Ubuntu 17.10 with artful-proposed enabled. Changing keyboard layout with alt+shift always triggers "show menu"on Wayland, which makes firefox unusable for users who don't know how to disable the value "ui.key.menuAccessKeyFocuses" from about:config. Is there any fix? Or maybe you can set "ui.key.menuAccessKeyFocuses" to false by default? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: firefox 54.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.6-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: thanos25842 F pulseaudio /dev/snd/controlC0: thanos25842 F pulseaudio /dev/snd/controlC1: thanos25842 F pulseaudio BuildID: 20170616154447 Channel: Unavailable CurrentDesktop: GNOME Date: Mon Aug 21 23:42:26 2017 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2017-08-21 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) IpRoute: default via 192.168.2.1 dev wlp4s7 proto static metric 600 169.254.0.0/16 dev wlp4s7 scope link metric 1000 192.168.2.0/24 dev wlp4s7 proto kernel scope link src 192.168.2.2 metric 600 Locales: extensions.sqlite corrupt or missing Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=54.0/20170616154447 (In use) RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/09/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F7d dmi.board.name: GA-970A-DS3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF7d:bd09/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-970A-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-970A-DS3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-970A-DS3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1712200/+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 1769456] Re: Thunderbird renders emoji in email subject with enourmous size
*** This bug is a duplicate of bug 1761844 *** https://bugs.launchpad.net/bugs/1761844 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: thunderbird (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1769456 Title: Thunderbird renders emoji in email subject with enourmous size Status in thunderbird package in Ubuntu: Confirmed Bug description: Well, if you have an email with an emoji in subject, Thunderbird renders it with enourmous size, like 6-7 rows in mail list. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: thunderbird 1:52.7.0+build1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ldvsoft2831 F pulseaudio BuildID: 20180416164209 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Sun May 6 14:31:48 2018 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2016-04-23 (742 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via 192.168.1.1 dev wlp3s0 proto dhcp metric 600 10.205.113.0/24 dev docker0 proto kernel scope link src 10.205.113.1 linkdown 169.254.0.0/16 dev wlp3s0 scope link metric 1000 172.17.0.0/16 dev br-cf01c9a4a624 proto kernel scope link src 172.17.0.1 linkdown 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.124 metric 600 Locales: extensions.sqlite corrupt or missing PrefSources: prefs.js /usr/share/xul-ext/enigmail/defaults/preferences/enigmail.js /usr/share/xul-ext/enigmail/defaults/preferences/000system.js ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=52.7.0/20180416164209 (In use) RunningIncompatibleAddons: False SourcePackage: thunderbird Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to bionic on 2018-05-04 (1 days ago) dmi.bios.date: 06/16/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: U40Sd.202 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: U40Sd 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.:bvrU40Sd.202:bd06/16/2011:svnASUSTeKComputerInc.:pnU40Sd:pvr1.0:rvnASUSTeKComputerInc.:rnU40Sd:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.family: U dmi.product.name: U40Sd 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/thunderbird/+bug/1769456/+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 1764708] Re: Base64 encoded images/emotes drawn out of topic bounds
*** This bug is a duplicate of bug 1761844 *** https://bugs.launchpad.net/bugs/1761844 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: thunderbird (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1764708 Title: Base64 encoded images/emotes drawn out of topic bounds Status in thunderbird package in Ubuntu: Confirmed Bug description: Image in topic is draw out of bounds. This did not happen in Thunderbird from 17.10 (attached: base64Topic.png, HugeEmoteInTopic.png) I think the relevant part of eml file is: Subject: =?utf-8?B?8J+RiSBGb3Rva3NpxIXFvGthIDIxIHggMjgganXFvCBvZCAx?= =?utf-8?B?MzUgesWC?= Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: base64 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: thunderbird 1:52.7.0+build1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia AddonCompatCheckDisabled: False ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nait 1917 F pulseaudio /dev/snd/controlC1: nait 1917 F pulseaudio BuildID: 20180416164209 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Tue Apr 17 11:50:04 2018 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2017-10-18 (180 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IpRoute: default via 192.168.1.1 dev wlp9s0 proto dhcp metric 600 169.254.0.0/16 dev wlp9s0 scope link metric 1000 192.168.1.0/24 dev wlp9s0 proto kernel scope link src 192.168.1.108 metric 600 Locales: extensions.sqlite corrupt or missing PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=52.7.0/20180416164209 (In use) RunningIncompatibleAddons: False SourcePackage: thunderbird Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to bionic on 2018-04-17 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1764708/+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 1736164] Re: deja-dup/duplicity backup fails with UnicodeDecodeError
On Ubuntu MATE 18.04, I get the following error: Traceback (innermost last): File "/usr/bin/duplicity", line 1555, in with_tempdir(main) File "/usr/bin/duplicity", line 1541, in with_tempdir fn() File "/usr/bin/duplicity", line 1393, in main do_backup(action) File "/usr/bin/duplicity", line 1511, in do_backup full_backup(col_stats) File "/usr/bin/duplicity", line 572, in full_backup globals.backend) File "/usr/bin/duplicity", line 454, in write_multivol (tdp, dest_filename, vol_num))) File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line 146, in schedule_task return self.__run_synchronously(fn, params) File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line 172, in __run_synchronously ret = fn(*params) File "/usr/bin/duplicity", line 453, in vol_num: put(tdp, dest_filename, vol_num), File "/usr/bin/duplicity", line 342, in put backend.put(tdp, dest_filename) File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 395, in inner_retry % (n, e.__class__.__name__, util.uexc(e))) File "/usr/lib/python2.7/dist-packages/duplicity/util.py", line 79, in uexc return ufn(unicode(e).encode('utf-8')) UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 37: ordinal not in range(128) james@OldDell:~$ apt-show-versions deja-dup deja-dup:amd64/bionic 37.1-2fakesync1 uptodate deja-dup:i386 not installed james@OldDell:~$ apt-show-versions duplicity duplicity:amd64/bionic 0.7.17-0ubuntu1 uptodate duplicity:i386 not installed james@OldDell:~$ uname -a Linux OldDell 4.15.0-22-generic #24-Ubuntu SMP Wed May 16 12:15:17 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux ** Also affects: deja-dup (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1736164 Title: deja-dup/duplicity backup fails with UnicodeDecodeError Status in Déjà Dup: Triaged Status in Duplicity: New Status in deja-dup package in Ubuntu: New Status in deja-dup package in Fedora: In Progress Bug description: See: https://bugzilla.redhat.com/show_bug.cgi?id=1470873 Description of problem: With the update from Fedora 25 to Fedora 26 Workstation, backups with deja-dup/duplicity are failing Version-Release number of selected component (if applicable): duplicity 0.7.13.1 deja-dup 34.3 How reproducible: Always (scheduled and manually started backup) Steps to Reproduce: 1. Wait for the scheduled backup to start or start it via the "Backup now" button 2. Some or a large number of files might get backed up, then the backup stops with "Failed with an unknown error" 3. Actual results: Backup fails Expected results: Backup completes as it always did Additional info: Traceback (most recent call last): File "/usr/bin/duplicity", line 1540, in with_tempdir(main) File "/usr/bin/duplicity", line 1534, in with_tempdir fn() File "/usr/bin/duplicity", line 1385, in main do_backup(action) File "/usr/bin/duplicity", line 1516, in do_backup incremental_backup(sig_chain) File "/usr/bin/duplicity", line 668, in incremental_backup globals.backend) File "/usr/bin/duplicity", line 453, in write_multivol (tdp, dest_filename, vol_num))) File "/usr/lib64/python2.7/site-packages/duplicity/asyncscheduler.py", line 146, in schedule_task return self.__run_synchronously(fn, params) File "/usr/lib64/python2.7/site-packages/duplicity/asyncscheduler.py", line 172, in __run_synchronously ret = fn(*params) File "/usr/bin/duplicity", line 452, in vol_num: put(tdp, dest_filename, vol_num), File "/usr/bin/duplicity", line 341, in put backend.put(tdp, dest_filename) File "/usr/lib64/python2.7/site-packages/duplicity/backend.py", line 376, in inner_retry % exception_traceback()) File "/usr/lib64/python2.7/site-packages/duplicity/util.py", line 51, in exception_traceback return uexc(msg) File "/usr/lib64/python2.7/site-packages/duplicity/util.py", line 79, in uexc e = unicode(e).encode('utf-8') UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 746: ordinal not in range(128) To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1736164/+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 1776260] Re: Can't use three monitors properly; "xrandr: screen cannot be larger than 8192x8192"
Sorry, that Intel URL should have been https://www.intel.com/content/www/us/en/support/articles/05571/mini- pcs.html -- 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/1776260 Title: Can't use three monitors properly; "xrandr: screen cannot be larger than 8192x8192" Status in xorg-server package in Ubuntu: New Bug description: https://www.intel.com/content/www/us.../mini-pcs.html claims that the Skull Canyon ( NUC6i7KYK ) can handle three 4k displays, so I'm experimenting with a Skull Canyon running a fresh minimal Ubuntu 18.04. It works great when plugged into one 4k monitor (via any of the three ports: hdmi, mini-dp, or type c; all three show up in xrandr as DisplayPort). It even seems to work ok when I plug in two. Doesn't matter which two. When I plug in all three, and boot to normal graphical.target mode with the usual gdm greeter, one of the three screens does show gdm, and allows me to log in. But I can't seem to get all three screens active at the same time. Falling back to old school tools, I did 'sudo systemctl set-default multi-user.target' and rebooted. Logging in, creating a trivial .xinitrc, and doing 'startx' started the X server, and all three screens show the same output. So far so good. But trying to arrange them like this: $ xrandr --auto --output DP-2 --right-of DP-1 --output DP-3 --right-of DP-2 fails with xrandr: screen cannot be larger than 8192x8192 (desired size 11520x2160) Using --above instead of --right-of works, but that's not how the monitors are arranged. I tried creating /usr/share/X11/xorg.conf.d/85-screen.conf containing Section "Screen" Identifier "Default Screen" DefaultDepth24 SubSection "Display" Virtual 11520 6480 EndSubSection EndSection and applied it by killing X and doing startx again, but that gave very strange results: the mouse showed up on two screens, but .xinit didn't seem to have taken effect, and the content on the screen was the same as before startx. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core 2:1.19.6-1ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Jun 11 09:49:40 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Iris Pro Graphics 580 [8086:193b] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Iris Pro Graphics 580 [8086:2064] InstallationDate: Installed on 2018-06-08 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-22-generic root=UUID=80ac733c-b098-4643-84a4-fe81874f2101 ro rootflags=subvol=@ quiet splash vt.handoff=1 SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/03/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: KYSKLi70.86A.0037.2016.0603.1032 dmi.board.name: NUC6i7KYB dmi.board.vendor: Intel Corporation dmi.board.version: H90766-404 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrKYSKLi70.86A.0037.2016.0603.1032:bd06/03/2016:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-404:cvnIntelCorporation:ct3:cvr1.0: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1776260/+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 1776260] [NEW] Can't use three monitors properly; "xrandr: screen cannot be larger than 8192x8192"
Public bug reported: https://www.intel.com/content/www/us.../mini-pcs.html claims that the Skull Canyon ( NUC6i7KYK ) can handle three 4k displays, so I'm experimenting with a Skull Canyon running a fresh minimal Ubuntu 18.04. It works great when plugged into one 4k monitor (via any of the three ports: hdmi, mini-dp, or type c; all three show up in xrandr as DisplayPort). It even seems to work ok when I plug in two. Doesn't matter which two. When I plug in all three, and boot to normal graphical.target mode with the usual gdm greeter, one of the three screens does show gdm, and allows me to log in. But I can't seem to get all three screens active at the same time. Falling back to old school tools, I did 'sudo systemctl set-default multi-user.target' and rebooted. Logging in, creating a trivial .xinitrc, and doing 'startx' started the X server, and all three screens show the same output. So far so good. But trying to arrange them like this: $ xrandr --auto --output DP-2 --right-of DP-1 --output DP-3 --right-of DP-2 fails with xrandr: screen cannot be larger than 8192x8192 (desired size 11520x2160) Using --above instead of --right-of works, but that's not how the monitors are arranged. I tried creating /usr/share/X11/xorg.conf.d/85-screen.conf containing Section "Screen" Identifier "Default Screen" DefaultDepth24 SubSection "Display" Virtual 11520 6480 EndSubSection EndSection and applied it by killing X and doing startx again, but that gave very strange results: the mouse showed up on two screens, but .xinit didn't seem to have taken effect, and the content on the screen was the same as before startx. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core 2:1.19.6-1ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Jun 11 09:49:40 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Iris Pro Graphics 580 [8086:193b] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Iris Pro Graphics 580 [8086:2064] InstallationDate: Installed on 2018-06-08 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-22-generic root=UUID=80ac733c-b098-4643-84a4-fe81874f2101 ro rootflags=subvol=@ quiet splash vt.handoff=1 SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/03/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: KYSKLi70.86A.0037.2016.0603.1032 dmi.board.name: NUC6i7KYB dmi.board.vendor: Intel Corporation dmi.board.version: H90766-404 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrKYSKLi70.86A.0037.2016.0603.1032:bd06/03/2016:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-404:cvnIntelCorporation:ct3:cvr1.0: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- 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/1776260 Title: Can't use three monitors properly; "xrandr: screen cannot be larger than 8192x8192" Status in xorg-server package in Ubuntu: New Bug description: https://www.intel.com/content/www/us.../mini-pcs.html claims that the Skull Canyon ( NUC6i7KYK ) can handle three 4k displays, so I'm experimenting with a Skull Canyon running a fresh minimal Ubuntu 18.04. It works great when plugged into one 4k monitor (via any of the three ports: hdmi, mini-dp, or type c; all three show up in xrandr as DisplayPort). It even seems to work ok when I plug in two. Doesn't matter which two. When I plug in all three, and boot to normal graphical.target mode with the usual gdm greeter, one of the three screens does show gdm, and allows me to log in. But I
[Desktop-packages] [Bug 1776215] Re: i lost my menu and title bar
** Package changed: xorg (Ubuntu) => unity (Ubuntu) -- 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/1776215 Title: i lost my menu and title bar Status in unity package in Ubuntu: New Bug description: i can't access my menu and title bar i need your help to restore it ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 Uname: Linux 4.4.0-128-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Jun 11 13:49:50 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8210] [1002:9834] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Kabini [Radeon HD 8210] [103c:21f7] InstallationDate: Installed on 2014-11-04 (1314 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) MachineType: Hewlett-Packard HP 15 Notebook PC ProcEnviron: LANGUAGE=en_ZA:en PATH=(custom, no user) LANG=en_ZA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-128-generic root=UUID=661e7b31-e7f7-4fe1-b992-35c89b3ab5a7 ro vesafb.invalid=1 plymouth:debug nopat drm.debug=0xe SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/03/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.05 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 21F7 dmi.board.vendor: Hewlett-Packard dmi.board.version: 52.16 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.05:bd01/03/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr097610405F1610180:rvnHewlett-Packard:rn21F7:rvr52.16:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP 15 Notebook PC dmi.product.version: 097610405F1610180 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon Jun 11 13:46:50 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.7 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1776215/+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 1769553] Re: xfs blocks on unresponsive raid - blockdev module is missing
This appears to be an issue with either hardware or md driver rather than udisks. Those libraries are needed for the GUI disk management tool to manage raid, but that's it. Without being able to reproduce it there isn't likely anything that can be done. ** Changed in: udisks2 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1769553 Title: xfs blocks on unresponsive raid - blockdev module is missing Status in udisks2 package in Ubuntu: Incomplete Bug description: # lsb_release -rd Description:Ubuntu 18.04 LTS Release:18.04 udisks2: 2.7.6-3 libblockdev-mdraid2: 2.16-2 Ubuntu 18.04, freshly upgraded from 16.04 via 17.10; system ran OK for about 72h before issue. Filesystem on faulty raid is XFS, and raid is raid 10 far-copies: md3 : active raid10 sdb4[2] sda4[4] 524155904 blocks super 1.2 512K chunks 2 far-copies [2/2] [UU] What happened: A "git commit" could not succeed. Process was impossible to kill. Load reported by xload reached outstanding levels; system was still responsive however, but impossible to halt, waiting for disk sync that never occurred. I had to reboot the hard way. After reboot, /home could not mount, and boot process dropped me to a root console. I could see that mdadm reported ongoing reconstruction, but frozen at some point. In the logs: May 6 01:35:35 localhost kernel: [58614.835510] INFO: task xfsaild/md3:1056 blocked for more than 120 seconds. May 6 01:35:35 localhost kernel: [58614.835521] Tainted: G OE4.15.0-20-lowlatency #21-Ubuntu May 6 01:35:35 localhost kernel: [58614.835524] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. May 6 01:35:35 localhost kernel: [58614.835529] xfsaild/md3 D0 1056 2 0x8000 May 6 01:35:35 localhost kernel: [58614.835535] Call Trace: May 6 01:35:35 localhost kernel: [58614.835552] __schedule+0x299/0x8c0 May 6 01:35:35 localhost kernel: [58614.835560] schedule+0x33/0x90 May 6 01:35:35 localhost kernel: [58614.835570] wait_barrier+0x134/0x190 [raid10] May 6 01:35:35 localhost kernel: [58614.835578] ? wait_woken+0x80/0x80 May 6 01:35:35 localhost kernel: [58614.835585] raid10_write_request+0x77/0x950 [raid10] ... Another line of interest: May 6 02:05:59 localhost udisksd[1480]: failed to load module mdraid: libbd_mdraid.so.2: cannot open shared object file: No such file or directory Actually, package libblockdev-mdraid2 is missing. Added it as well as libblockdev-mpath2. Rebooted. mdadm starts reconstruction and is OK when I come back from sleep. System looks stable since then. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1769553/+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 1773213] Re: U1 login dialog missing link to the privacy policy
** Description changed: The U1 login for g-o-a is missing a link to the privacy policy. + + [Impact] + + * No way to view the privacy policy for Ubuntu One + + [Test Case] + + * Open gnome-control-center + * Select "Online Accounts" on the left + * Select "Ubuntu Single Sign-On" under "Add an account" + * Not you should see a link to open the Privacy Policy on the bottom left of the dialog. + * Verify when clicking the window a browser window opens with our data privacy page + + [Regression Potential] + + * None -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1773213 Title: U1 login dialog missing link to the privacy policy Status in gnome-online-accounts package in Ubuntu: Fix Released Status in gnome-online-accounts source package in Bionic: New Bug description: The U1 login for g-o-a is missing a link to the privacy policy. [Impact] * No way to view the privacy policy for Ubuntu One [Test Case] * Open gnome-control-center * Select "Online Accounts" on the left * Select "Ubuntu Single Sign-On" under "Add an account" * Not you should see a link to open the Privacy Policy on the bottom left of the dialog. * Verify when clicking the window a browser window opens with our data privacy page [Regression Potential] * None To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1773213/+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 1776235] [NEW] Ubuntu 18.04 with RealVnc client. Clipboard only works with stock terminal
Public bug reported: Just as the title says. Clipboard only works with ubuntu 18.04 terminal. I can copy from terminal and paste into my Windows real vnc client. However, copying from any other application won't be able to reach vnc client. Even if I start cat, type something, then try to copy, VNC client won't see it. I won't complain if the clipboard doesn't work at all. However based on the fact that it only works on terminal, it indicates vino is doing some filtering and it won't tell. Somebody is messing with the users. An explanation is expected. Thanks! ** Affects: vino (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vino in Ubuntu. https://bugs.launchpad.net/bugs/1776235 Title: Ubuntu 18.04 with RealVnc client. Clipboard only works with stock terminal Status in vino package in Ubuntu: New Bug description: Just as the title says. Clipboard only works with ubuntu 18.04 terminal. I can copy from terminal and paste into my Windows real vnc client. However, copying from any other application won't be able to reach vnc client. Even if I start cat, type something, then try to copy, VNC client won't see it. I won't complain if the clipboard doesn't work at all. However based on the fact that it only works on terminal, it indicates vino is doing some filtering and it won't tell. Somebody is messing with the users. An explanation is expected. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vino/+bug/1776235/+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 1543192] Re: Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from dix_main() ["no screens found"]
Just to close the loop on this, it seems that my problem was a corrupted dist-upgrade and reinstalling a fresh Xubuntu 18.04 fixed it. -- 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/1543192 Title: Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from dix_main() ["no screens found"] Status in xorg-server package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/4de849dfec89af168af9cda3318221a2a654e530 --- No idea what happened. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: xserver-xorg-core 2:1.17.3-2ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CrashCounter: 1 Date: Mon Feb 8 17:07:23 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:21da] InstallationDate: Installed on 2015-04-30 (283 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: LENOVO 429149G ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic root=UUID=457973fc-512e-4b6a-b65b-85f15fa85b7b ro console=tty1 console=ttyS0 panic=-1 Signal: 6 SourcePackage: xorg-server StacktraceTop: OsAbort () ?? () FatalError () ?? () __libc_start_main (main=0x557f8180ff00, argc=11, argv=0x7fffc9e34fd8, init=, fini=, rtld_fini=, stack_end=0x7fffc9e34fc8) at libc-start.c:289 SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit code 2: Title: Xorg crashed with SIGABRT in OsAbort() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 05/18/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET46WW (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 429149G dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET46WW(1.16):bd05/18/2011:svnLENOVO:pn429149G:pvrThinkPadX220:rvnLENOVO:rn429149G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 429149G dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20151211-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.66-2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.1-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.1-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160127-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1 xserver.bootTime: Mon Feb 8 17:08:14 2016 xserver.configfile: default xserver.errors: systemd-logind: failed to get session: PID 9847 does not belong to any known session xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 728 vendor LGD xserver.version: 2:1.17.3-2ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1543192/+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 1773561] Re: Xenial/16.04: GIMP needs a security update - unfixed issues (CVE-2017: 17784-17789).
** Also affects: gimp (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: gimp (Ubuntu Artful) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/1773561 Title: Xenial/16.04: GIMP needs a security update - unfixed issues (CVE-2017: 17784-17789). Status in gimp package in Ubuntu: Confirmed Status in gimp source package in Xenial: New Status in gimp source package in Artful: New Bug description: Hello. GIMP package ('Universe/Security' section), available in "Xenial"/16.04 LTS Release, contains unfixed security issues and is vulnerable to, for example, heap-buffer over-read, out of bounds read and stack-based buffer over-read etc. The whole thing is pretty strange, because Ubuntu Releases released before and after "Xenial", contains updated GIMP package! Anyway, it looks this way: in "Trusty" the available version is: '2.8.10-0ubuntu1.2' (please see [1]). "Bionic" has '2.8.20-1.1' version (please see [2]). Both Releases contains fixes for mentioned security issues: CVE-2017-* etc. However, GIMP version in "Xenial" is '2.8.16-1ubuntu1.1' and does not contain any security updates from 2017. (The last one is from Thu, 30 Jun 2016.; please see [3]). Security updates with fixes for mentioned CVE's (please compare changes in 1. and 2. with 3.) were released on Thu., 18 Jan 2018 - for "Trusty" and Tue., 26 Dec 2017 - for "Bionic". In "Xenial", the last security update is from Thu., 30 Jun 2016 (fix for CVE-2016-4994) and there is no further updates! Here is a CVE list of security issues not fixed in "Xenial", but in "Trusty" and "Bionic" etc.: 1/ CVE-2017-17784: Heap-buffer over-read in load_image file-gbr.c 2/ CVE-2017-17785: Heap-based buffer overflow in fli_read_brun function 3/ CVE-2017-17786: Out of bounds read 4/ CVE-2017-17787: Heap-based buffer over-read in read_creator_block 5/ CVE-2017-17788: Stack-based buffer over-read in xcf_load_stream 6/ CVE-2017-17789: Heap-based buffer overflow in read_channel_data And the most important thing: if User had installed GIMP package in "Xenial" Release, he is affected - since one year, at least - because of a vulnerable version. Security issues, mentioned above, are from 2017. So, maybe it's a good opportunity to update GIMP to v2.10.2 version, released on 20., May 2018? (Version 2.8.X is very outdated). I wanted to send an email to Mr Marc Deslauriers, because he made the last security update for GIMP in "Xenial" (fix for CVE-2016-4994). But I decided to report a bug on Launchpad. I hope that it's an acceptable way. If not, I'm sorry. By the way: similar problems with unfixed security issues, can be found e.g. in Audacious and Parole packages. But that's a different story, completely different story... Thanks, best regards. __ 1. http://changelogs.ubuntu.com/changelogs/pool/main/g/gimp/gimp_2.8.10-0ubuntu1.2/changelog 2. http://changelogs.ubuntu.com/changelogs/pool/universe/g/gimp/gimp_2.8.20-2/changelog 3. http://changelogs.ubuntu.com/changelogs/pool/universe/g/gimp/gimp_2.8.16-1ubuntu1.1/changelog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1773561/+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 913323] Re: Occasional login failure and artefacts
Hello, This behavior (need to enter password 2 or 3 times) happened nearly from the beginning. It is a fresh install of a standard xubuntu 16.04 LTS with my old homedir copied from the previous 16.04 machine (that has crashed). Packages are just installed when needed, so that forgotten packages are not borrowed from the old machine. Btw lightdm: 1.18.3-0ubuntu1.1 Today I had to enter my password 3 times. here are some extracts of 3 log files where I have found 2 errors in a short time : /var/log/syslog /var/log/lightdm/lightdm.log /var/log/lightdm/seat0-greeter.log Maybe useful information: When unlocked, I select the session with 7, but once locked, I have to select Ctrl>8; Or 7 displays a black screen with something in french like this: This session is locked you will be redirected to the unlock dialog automatically in a few seconds # Syslog: A connection to the bus can't be made tail -30 /var/log/syslog Jun 11 14:07:14 dlt0001ptrstp lightdm[1248]: ** (lightdm:1248): WARNING **: Error using VT_WAITACTIVE 7 on /dev/tty0: Interrupted system call Jun 11 14:07:14 dlt0001ptrstp org.gtk.vfs.Daemon[23411]: A connection to the bus can't be made Jun 11 14:07:15 dlt0001ptrstp systemd[1]: Started Session c32 of user lightdm. Jun 11 14:07:16 dlt0001ptrstp org.a11y.Bus[7986]: ** (process:7997): WARNING **: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files Jun 11 14:07:16 dlt0001ptrstp org.a11y.Bus[7986]: Activating service name='org.a11y.atspi.Registry' Jun 11 14:07:16 dlt0001ptrstp org.a11y.Bus[7986]: Successfully activated service 'org.a11y.atspi.Registry' Jun 11 14:07:16 dlt0001ptrstp org.a11y.atspi.Registry[8002]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry Jun 11 14:07:20 dlt0001ptrstp lightdm[1248]: ** (lightdm:1248): WARNING **: Error using VT_WAITACTIVE 7 on /dev/tty0: Interrupted system call Jun 11 14:07:20 dlt0001ptrstp org.gtk.vfs.Daemon[7986]: A connection to the bus can't be made Jun 11 14:07:21 dlt0001ptrstp systemd[1]: Started Session c33 of user lightdm. Jun 11 14:07:21 dlt0001ptrstp org.a11y.Bus[8079]: ** (process:8090): WARNING **: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files Jun 11 14:07:21 dlt0001ptrstp org.a11y.Bus[8079]: Activating service name='org.a11y.atspi.Registry' Jun 11 14:07:22 dlt0001ptrstp org.a11y.Bus[8079]: Successfully activated service 'org.a11y.atspi.Registry' Jun 11 14:07:22 dlt0001ptrstp org.a11y.atspi.Registry[8095]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry Jun 11 14:07:27 dlt0001ptrstp org.gtk.vfs.Daemon[8079]: A connection to the bus can't be made # /var/log/lightdm/lightdm.log : Error using VT_WAITACTIVE [+1635057.87s] DEBUG: Continue authentication [+1635057.90s] DEBUG: Session pid=23480: Authentication complete with return value 0: Success [+1635057.90s] DEBUG: Authenticate result for user : Success [+1635057.90s] DEBUG: User authorized [+1635057.90s] DEBUG: Greeter sets language fr_FR [+1635057.98s] DEBUG: Greeter requests session xubuntu [+1635057.98s] DEBUG: Seat seat0: Returning to existing user session [+1635057.98s] DEBUG: Unlocking login1 session c24 [+1635057.98s] DEBUG: Activating VT 7 [+1635057.98s] WARNING: Error using VT_WAITACTIVE 7 on /dev/tty0: Interrupted system call [+1635057.98s] DEBUG: Seat seat0: Stopping greeter [+1635057.98s] DEBUG: Session pid=23399: Sending SIGTERM [+1635057.98s] DEBUG: Activating login1 session c24 [+1635057.99s] DEBUG: Session pid=23480: Exited with return value 0 [+1635057.99s] DEBUG: Seat seat0: Session stopped [+1635058.00s] DEBUG: Greeter closed communication channel [+1635058.00s] DEBUG: Session pid=23399: Exited with return value 0 [+1635058.00s] DEBUG: Seat seat0: Session stopped [+1635058.00s] DEBUG: Seat seat0: Stopping display server, no sessions require it [+1635058.00s] DEBUG: Sending signal 15 to process 23391 [+1635058.32s] DEBUG: Process 23391 exited with return value 0 [+1635058.32s] DEBUG: DisplayServer x-1: X server stopped [+1635058.32s] DEBUG: Releasing VT 8 [+1635058.32s] DEBUG: DisplayServer x-1: Removing X server authority /var/run/lightdm/root/:1 [+1635058.32s] DEBUG: Seat seat0: Display server stopped [+1635058.32s] DEBUG: Seat seat0: Active display server stopped, starting greeter [+1635058.32s] DEBUG: Seat seat0: Creating greeter session [+1635058.32s] DEBUG: Seat seat0: Creating display server of type x [+1635058.32s] DEBUG: Using VT 8 [+1635058.32s] DEBUG: Seat seat0: Starting local X display on VT 8 [+1635058.32s] DEBUG: DisplayServer x-1: Logging to /var/log/lightdm/x-1.log [+1635058.32s] DEBUG: DisplayServer x-1: Writing X server authority to /var/run/lightdm/root/:1 [+1635058.32s] DEBUG: DisplayServer x-1: Launching X Server [+1635058.32s] DEBUG: Launching process 7966:
[Desktop-packages] [Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
This is a blocker for deployment of 18.04 to ~200 workstations within my company. Any ETA on a release? My steps to reproduce: 1. Boot Machine 2. Enter username 3. Enter incorrect password 4. Enter correct password 5. Stuck on purple screen -- 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/1766137 Title: [regression] Password accepted but login fails (blank purple screen and mouse pointer only) Status in gdm: Fix Released Status in Release Notes for Ubuntu: Fix Released Status in gdm3 package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Invalid Status in gdm3 source package in Bionic: Fix Committed Status in gnome-shell source package in Bionic: Invalid Bug description: [ Description ] Due to a refcounting bug, a GDBusConnection was getting disposed when it was still required. The symptom of this was that you couldn't log in on the second attempt if you'd got your password wrong on the first attempt. All you'd see is a blank purple screen and mouse pointer only. [ Test case ] 1. Boot to GDM 2. Click your username 3. Type the wrong password a couple of times, pressing enter after each time 4. Type the right password If the bug is happening, after 4. the system hangs at a blank screen with the mouse cursor. If you then switch to a VT or otherwise connect to the machine, you can examine the journal and you'll see a G_IS_DBUS_CONNECTION failure. [ Fix ] Marco and I worked upstream on this fix. We found out that there was a problem like this- The GdmClient has a shared GDBusConnection for its operations. The first time someone calls for it, it is created and stored in the object's private structure. Subsequent calls return *a new reference* to this same object. It turned out that the asynchronous method to get the connection was accidentally unreferencing its object before giving it to the caller if it was returning an already-existing connection. For this to work properly, we need to nullify the pointer we stored when the connection goes away, so we know when to make a new one. There were some cases where we didn't add the weak references required to do that. Those are also fixed. [ Regression potential ] Now we share connections more than we did before. We also more carefully track when to clear our object. If we got this wrong, we might end up leaking the connection or dropping it in even more cases. [ Original report ] WORKAROUND: After typing an incorrect password, click Cancel, then click your name, then enter your password again. --- Trying to log into my session (Gnome, Xorg), if I enter the wrong password before entering it correctly, the session doesn't load and I get a purple screen, a mouse cursor, and an invisible but clickable menu in the top right. If I enter it correctly the first time, there is no problem. I've replicated this from a fresh boot, after logging out and after 'sudo service gdm restart' from the Ctrl-Alt-F4 console. This is a fresh install, and didn't occur when I was using a previous install of 18.04 (until Friday). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 22 20:31:13 2018 InstallationDate: Installed on 2018-04-22 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180421.1) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1766137/+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 1776078] Re: Wrong display of calendar entries with different timezone for start and stop date
** Attachment removed: "Test Appointment.ics" https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1776078/+attachment/5150903/+files/Test%20Appointment.ics -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1776078 Title: Wrong display of calendar entries with different timezone for start and stop date Status in evolution package in Ubuntu: New Bug description: Timezone of stop date is ignored for ics files and caldac calendars. The attached example has a during of 7 hours. It gets imported correctly with evolution. However, it looks like an event with a duration of one hour in the calendar. Thunderbird displays the event correctly (as my iPhone). Import creates error message if stop time in local timezone is 'before' start time in specified timezone (see second example). Event is not displayed in the regular calender view but can be seen in the list view. When I open the entry, I can only choose a timezone for the entire event, i.e., not for start and stop date separately. Expected behavior: - correct display of length of event in the calendar view - separate entry fields for timezones for start and stop date (cf. Thunderbird - Lightning) Example 1: BEGIN:VCALENDAR PRODID:-//Mozilla.org/NONSGML Mozilla Calendar V1.1//EN VERSION:2.0 BEGIN:VEVENT CREATED:20180610T131500Z LAST-MODIFIED:20180610T131418Z DTSTAMP:20180610T131418Z UID:20180610_JK_Test1 SUMMARY:New Test Appointment DTSTART;TZID=Europe/Berlin:20180610T13 DTEND;TZID=America/New_York:20180610T14 END:VEVENT END:VCALENDAR Example 2: BEGIN:VCALENDAR PRODID:-//Mozilla.org/NONSGML Mozilla Calendar V1.1//EN VERSION:2.0 BEGIN:VEVENT CREATED:20180610T131500Z LAST-MODIFIED:20180610T131418Z DTSTAMP:20180610T131418Z UID:20180610_JK_Test2 SUMMARY:Short Test Appointment DTSTART;TZID=Europe/Berlin:20180610T13 DTEND;TZID=America/New_York:20180610T11 END:VEVENT END:VCALENDAR ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: evolution 3.28.1-2 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jun 10 15:41:39 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-04-05 (65 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180403) SourcePackage: evolution UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1776078/+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 1776215] [NEW] i lost my menu and title bar
Public bug reported: i can't access my menu and title bar i need your help to restore it ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 Uname: Linux 4.4.0-128-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Jun 11 13:49:50 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8210] [1002:9834] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Kabini [Radeon HD 8210] [103c:21f7] InstallationDate: Installed on 2014-11-04 (1314 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) MachineType: Hewlett-Packard HP 15 Notebook PC ProcEnviron: LANGUAGE=en_ZA:en PATH=(custom, no user) LANG=en_ZA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-128-generic root=UUID=661e7b31-e7f7-4fe1-b992-35c89b3ab5a7 ro vesafb.invalid=1 plymouth:debug nopat drm.debug=0xe SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/03/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.05 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 21F7 dmi.board.vendor: Hewlett-Packard dmi.board.version: 52.16 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.05:bd01/03/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr097610405F1610180:rvnHewlett-Packard:rn21F7:rvr52.16:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP 15 Notebook PC dmi.product.version: 097610405F1610180 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon Jun 11 13:46:50 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.7 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 third-party-packages ubuntu xenial -- 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/1776215 Title: i lost my menu and title bar Status in xorg package in Ubuntu: New Bug description: i can't access my menu and title bar i need your help to restore it ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 Uname: Linux 4.4.0-128-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Jun 11 13:49:50 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8210] [1002:9834] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Kabini [Radeon HD 8210] [103c:21f7] InstallationDate: Installed on 2014-11-04 (1314 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) MachineType: Hewlett-Packard HP 15 Notebook PC ProcEnviron: LANGUAGE=en_ZA:en PATH=(custom, no user) LANG=en_ZA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-128-generic root=UUID=661e7b31-e7f7-4fe1-b992-35c89b3ab5a7 ro vesafb.invalid=1 plymouth:debug nopat drm.debug=0xe SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/03/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.05 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 21F7
[Desktop-packages] [Bug 1714504] Re: App indicator is not always displayed
This is the upstream issue (thanks Trevinho!): https://github.com/ubuntu /gnome-shell-extension-appindicator/issues/133 ** Bug watch added: github.com/ubuntu/gnome-shell-extension-appindicator/issues #133 https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/133 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1714504 Title: App indicator is not always displayed Status in gnome-shell-extension-appindicator package in Ubuntu: Confirmed Status in gnome-shell-extension-appindicator source package in Artful: Confirmed Bug description: I've 2 apps that should be displayed in the indicator: - hp systray (from the package hplip-gui) - synology cloud client (download from synology) Sometimes the indicators are displayed and sometimes not. The extension is loaded and show no error. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell-extension-appindicator 17.10 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 1 14:57:16 2017 Dependencies: InstallationDate: Installed on 2013-09-03 (1458 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902) PackageArchitecture: all ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell-extension-appindicator UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1714504/+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 1590661] Re: Unable to unlock: "Time has expired"
This bug still exists in 2018!!! Got this on 16.04 and lost all of my saved work ! FIX THIS -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1590661 Title: Unable to unlock: "Time has expired" Status in gnome-screensaver package in Ubuntu: Confirmed Bug description: Sometimes when coming back after locking the screen I am unable to unlock. The login box on the screen has a disabled password input field with the buttons also disabled. Except for the mouse, the entire screen is frozen. Even the time in the top of the screen stops going. The only way to continue is to move to a tty (Ctrl-Alt-F1), log in and kill gnome-screensaver. Since the time also stops going I have deduced that this seems to happen on days and times that correspond to when the cleaners are here. Because of this I speculate that they accidentally press some keys, including the enter key. This of course fails to unlock and after a certain timeout it then proceeds to freeze. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-screensaver 3.6.1-7ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Jun 9 08:59:15 2016 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session session-name 'ubuntu' org.gnome.desktop.session idle-delay uint32 300 InstallationDate: Installed on 2016-05-27 (12 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gnome-screensaver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1590661/+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 1774560] Re: xdg-desktop-portal-gtk malfunctions on Wayland: wl_display@1.error(zxdg_imported_v1@36, 0, "set_parent_of was called with an invalid child")
It would be great to get the fix backported to Bionic since people have been reporting this as bug in Geary already: https://bugzilla.gnome.org/show_bug.cgi?id=789846#c6 ** Bug watch added: GNOME Bug Tracker #789846 https://bugzilla.gnome.org/show_bug.cgi?id=789846 -- 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/1774560 Title: xdg-desktop-portal-gtk malfunctions on Wayland: wl_display@1.error(zxdg_imported_v1@36, 0, "set_parent_of was called with an invalid child") Status in mutter package in Ubuntu: Fix Released Status in xdg-desktop-portal-gtk package in Ubuntu: Confirmed Bug description: When running on a Wayland session, if xdg-desktop-portal-gtk is asked to display a window on behalf of a Wayland app, it gets disconnected from gnome-shell with one of these messages: Gdk-Message: 09:49:31.837: Lost connection to Wayland compositor. Gdk-Message: 09:50:28.438: Error 71 (Protocol error) dispatching to Wayland display. Running it with WAYLAND_DEBUG=1, the underlying error message that GDK seems to eat is: [3471970.531] wl_display@1.error(zxdg_imported_v1@36, 0, "set_parent_of was called with an invalid child") That is, when it tries to associate the dialog box with the confined application's window. It seems the underlying bug is in in Mutter: https://gitlab.gnome.org/GNOME/mutter/issues/138 According to duflu, the patch referenced in that bug report has been merged for 3.28.2 and 3.29.2. It seems like a candidate to backport to bionic if we want portals to work on the (non-default) Wayland session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1774560/+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 1774560] Re: xdg-desktop-portal-gtk malfunctions on Wayland: wl_display@1.error(zxdg_imported_v1@36, 0, "set_parent_of was called with an invalid child")
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xdg-desktop-portal-gtk (Ubuntu) Status: New => 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/1774560 Title: xdg-desktop-portal-gtk malfunctions on Wayland: wl_display@1.error(zxdg_imported_v1@36, 0, "set_parent_of was called with an invalid child") Status in mutter package in Ubuntu: Fix Released Status in xdg-desktop-portal-gtk package in Ubuntu: Confirmed Bug description: When running on a Wayland session, if xdg-desktop-portal-gtk is asked to display a window on behalf of a Wayland app, it gets disconnected from gnome-shell with one of these messages: Gdk-Message: 09:49:31.837: Lost connection to Wayland compositor. Gdk-Message: 09:50:28.438: Error 71 (Protocol error) dispatching to Wayland display. Running it with WAYLAND_DEBUG=1, the underlying error message that GDK seems to eat is: [3471970.531] wl_display@1.error(zxdg_imported_v1@36, 0, "set_parent_of was called with an invalid child") That is, when it tries to associate the dialog box with the confined application's window. It seems the underlying bug is in in Mutter: https://gitlab.gnome.org/GNOME/mutter/issues/138 According to duflu, the patch referenced in that bug report has been merged for 3.28.2 and 3.29.2. It seems like a candidate to backport to bionic if we want portals to work on the (non-default) Wayland session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1774560/+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 1714178] Re: Triple monitor display failed with Dell Dock (HiDPI) (modesetting)
Launchpad has imported 19 comments from the remote bug at https://bugs.freedesktop.org/show_bug.cgi?id=102508. 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 2017-09-01T08:23:28+00:00 ethan.hsieh wrote: Created attachment 133916 Screenshot Filed a new bug for modesetting driver. --- Can't configure a desktop with 3x4k monitors in one row https://bugs.freedesktop.org/show_bug.cgi?id=98297#c22 the mesa part is now fixed, but the modesetting driver in xserver needs to be fixed too: hw/xfree86/drivers/modesetting/drmmode_display.c: xf86CrtcSetSizeRange(pScrn, 320, 200, mode_res->max_width, vs. src/sna/sna_display.c: xf86CrtcSetSizeRange(sna->scrn, 8, 8, INT16_MAX, INT16_MAX); currently with xserver 1.19.3 it's not possible to configure 3x4k row of monitors unless the -intel ddx is used. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/1714178/comments/28 On 2017-09-01T08:24:54+00:00 ethan.hsieh wrote: Created attachment 133917 kern.log (drm.debug=0xe) Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/1714178/comments/29 On 2017-09-01T08:25:10+00:00 ethan.hsieh wrote: Created attachment 133918 Xorg.0.log Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/1714178/comments/30 On 2017-09-01T08:31:04+00:00 ethan.hsieh wrote: Created attachment 133919 lsb_release Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/1714178/comments/32 On 2017-09-01T09:08:30+00:00 ethan.hsieh wrote: Created attachment 133920 Xorg.0.log After applying the following patch, all three screens turn into black screens after I change the display mode from mirror mode to extended mode. (Please refer to the attached Xorg.0.log) hw/xfree86/drivers/modesetting/drmmode_display.c: -xf86CrtcSetSizeRange(pScrn, 320, 200, mode_res->max_width, mode_res->max_height); +xf86CrtcSetSizeRange(pScrn, 320, 200, INT16_MAX, INT16_MAX); Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/1714178/comments/33 On 2017-09-01T09:10:10+00:00 ethan.hsieh wrote: Created attachment 133921 kern.log Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/1714178/comments/34 On 2017-09-01T09:11:58+00:00 ethan.hsieh wrote: Created attachment 133922 Xorg.0.log After applying the following patch, all three screens turn into black screens after I change the display mode from mirror mode to extended mode. (Log: attached Xorg.0.log and kernel log (attachment 133921)) ubuntu-zesty/drivers/gpu/drm/i915/intel_display.c @@ -16458,9 +16458,12 @@ int intel_modeset_init(struct drm_device *dev) dev->mode_config.max_width = 4096; dev->mode_config.max_height = 4096; } else { - dev->mode_config.max_width = 8192; - dev->mode_config.max_height = 8192; + dev->mode_config.max_width = 16384; + dev->mode_config.max_height = 16384; } Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/1714178/comments/35 On 2017-11-20T11:56:36+00:00 Consume-noise-7 wrote: I don't know why the 8192 limit never has been raised. Maybe the hardware never adopted for higher resolutions. Anyway: As soon as you try to configure your 11520x2160 desktop, you can find in the log: [84.385] failed to add fb -22 -22 is invalid argument and that error comes from the kernel. You could boot your kernel with drm.debug=0x5e and may get more hints why it fails. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/1714178/comments/36 On 2017-12-06T10:17:35+00:00 Alex Tu wrote: Created attachment 135996 extend max buffer size for test. just followed the error from drm.debug=0x5e and tried to force extend max buffer size returned by intel_fb_pitch_limit(), then 3 X 4K monitor works well then. there are 2 commit b321803dfb and ac484963f9 touched this part, but not sure why it specify (8192 * cpp)? have some better way to extend the size ? environment setting: kernel 4.15.0-rc2 [1] drm, mesa and xorg version: http://paste.ubuntu.com/26124071/ [1] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc2/ Reply at:
[Desktop-packages] [Bug 1421808] Re: Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xf86VTEnter()
Hello, Reproduction steps: 1. connect an external monitor (I connect mine through mini-DisplayPort, and I use only the external monitor, I do NOT use both the laptop screen and the external monitor) 2. with the external monitor connected, suspend the computer (I do it by running xfce4-session-logout --suspend, I have a shortcut for this) 3. with the laptop suspended, disconnect the monitor 4. open the laptop, you'll be shown the Xdm login screen 5. log in 6. Xorg will crash, it will restart, and you'll see again the Xdm login screen What works (how to avoid the crash) 1. connect an external monitor 2. before suspending the laptop, disconnect the external monitor 3. suspend the laptop 4. open the laptop, everything will be ok -- 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/1421808 Title: Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xf86VTEnter() Status in xorg-server package in Ubuntu: Confirmed Bug description: The error is reported on boot up. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: xserver-xorg-core 2:1.16.2.901-1ubuntu3 ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Uname: Linux 3.18.0-12-generic x86_64 ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 Date: Sun Feb 8 12:36:52 2015 ExecutablePath: /usr/bin/Xorg InstallationDate: Installed on 2013-04-24 (660 days ago) InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130403) ProcCmdline: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: Signal: 6 SourcePackage: xorg-server StacktraceTop: OsAbort () ?? () FatalError () xf86VTEnter () WakeupHandler () Title: Xorg crashed with SIGABRT in OsAbort() UpgradeStatus: Upgraded to vivid on 2015-01-30 (14 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1421808/+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