[Desktop-packages] [Bug 1641055] [NEW] startx, lightdm fail to start
Public bug reported: After updating from 16.04 to 16.10, lightdm doesn't start. Adding 'nomodeset' for booting allows it to start, but apparently lacks all acceleration. Trying different kernels doesn't help, including the one from 16.04. Sorry for brevity, I'm writing this on my phone... ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xserver-xorg-core 2:1.18.4-1ubuntu6 Uname: Linux 4.8.7-040807-lowlatency x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 BootLog: /dev/sda1: clean, 2557730/15417344 files, 54003285/61639424 blocks CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Fri Nov 11 09:07:35 2016 DistUpgraded: 2016-11-10 20:42:28,744 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory) (8)) DistroCodename: yakkety DistroVariant: ubuntu DkmsStatus: acpi_call, 1.0, 3.2.0-21-generic, x86_64: built tp_smapi, 0.42, 4.4.0-47-generic, x86_64: installed tp_smapi, 0.42, 4.8.0-27-generic, x86_64: installed tp_smapi, 0.42, 4.8.7-040807-generic, x86_64: installed tp_smapi, 0.42, 4.8.7-040807-lowlatency, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:5036] InstallationDate: Installed on 2011-03-11 (2071 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) MachineType: LENOVO 20BWS02D00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.7-040807-lowlatency root=UUID=45e540a8-fe2a-49e7-9c27-99725af4a6bd ro quiet splash i915.i915_enable_rc6=1 vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: Upgraded to yakkety on 2016-11-10 (0 days ago) dmi.bios.date: 12/09/2014 dmi.bios.vendor: LENOVO dmi.bios.version: JBET39WW (1.04 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BWS02D00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET39WW(1.04):bd12/09/2014:svnLENOVO:pn20BWS02D00:pvrThinkPadT450s:rvnLENOVO:rn20BWS02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BWS02D00 dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.71+git1611081830.670f1e~gd~y version.libgl1-mesa-dri: libgl1-mesa-dri 13.1~git1611101930.f500c3~gd~y version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 13.1~git1611101930.f500c3~gd~y version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Fri Nov 11 09:06:56 2016 xserver.configfile: default xserver.devices: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-1ubuntu6 ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages ubuntu yakkety -- 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/1641055 Title: startx, lightdm fail to start Status in xorg-server package in Ubuntu: New Bug description: After updating from 16.04 to 16.10, lightdm doesn't start. Adding 'nomodeset' for booting allows it to start, but apparently lacks all acceleration. Trying different kernels doesn't help, including the one from 16.04. Sorry for brevity, I'm writing this on my phone... ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xserver-xorg-core 2:1.18.4-1ubuntu6 Uname: Linux 4.8.7-040807-lowlatency x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 BootLog: /dev/sda1: clean, 2557730/15417344 files, 54003285/61639424 blocks CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Fri Nov 11 09:07:35 2016 DistUpgraded: 2016-11-10 20:42:28,744 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory) (8)) DistroCodename: yakkety DistroVariant: ubuntu DkmsStatus: acpi_call, 1.0, 3.2.0-21-ge
[Desktop-packages] [Bug 1238914] Re: Random stuck keys on Lenovo Yoga 13
The bug went away after some package update for several months (wow!) in 16.04 -- therefore I refused to run updates all this time to get a bit of "normal life" during typing ;) A few days ago I did an update and the damn bug returned... several years of suffering from this Bug. BTW, guys, what keyboard layout are you using when experiencing this bug? I'm experiencing it only when using Neo2 layout. -- 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/1238914 Title: Random stuck keys on Lenovo Yoga 13 Status in xserver-xorg-input-evdev package in Ubuntu: Expired Bug description: Certain keyboard keys get stuck down seemingly randomly resulting in spurious bursts of key repeats. I have mostly noticed this with the arrow keys, PgUp, PgDn and Delete. I have tried to replicate the behaviour in the console with no luck so I believe this to be specific to xserver. Using xev to debug a bit I can see that upon releasing the key no keyup event is received. The key is not physically stuck. Pressing any key on the keyboard interrupts the keydown repeats. The common scenario is either browsing photos with eog or slides with evince. This can cause data loss because if the move to trash confirmation is disabled in eog you may delete many images without even noticing. A minor annoyance when presenting slides because you suddenly end up at the last slide in the deck, midway through your talk. Description: Ubuntu 13.04 Release: 13.04 xserver-xorg-video-intel: Installed: 2:2.21.6-0ubuntu4.1 Candidate: 2:2.21.6-0ubuntu4.1 Version table: *** 2:2.21.6-0ubuntu4.1 0 500 http://ie.archive.ubuntu.com/ubuntu/ raring-updates/main amd64 Packages 100 /var/lib/dpkg/status 2:2.21.6-0ubuntu4 0 500 http://ie.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1238914/+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 1585094] Re: Random stuck keys on Lenovo Yoga 13
trying to re-open ** Changed in: xorg (Ubuntu) Status: Expired => New -- 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/1585094 Title: Random stuck keys on Lenovo Yoga 13 Status in xorg package in Ubuntu: New Bug description: pressing arrow keys leads randomly to the effect of stuck number key and produces output in consoles or text editors like: "22" or "88". Pressing some other key stops the infinite flooding. This may (or not) be related to the following flooding in /var/log/system May 24 10:01:30 yogi kernel: [ 3816.438579] atkbd serio0: Unknown key pressed (translated set 2, code 0xbe on isa0060/serio0). May 24 10:01:30 yogi kernel: [ 3816.438603] atkbd serio0: Use 'setkeycodes e03e ' to make it known. May 24 10:01:30 yogi kernel: [ 3816.443504] atkbd serio0: Unknown key released (translated set 2, code 0xbe on isa0060/serio0). May 24 10:01:30 yogi kernel: [ 3816.443516] atkbd serio0: Use 'setkeycodes e03e ' to make it known. these messages are generated approximately each 200 msec. If the former is not related to stuck key problem, please, ignore. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-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 CurrentDesktop: Unity Date: Tue May 24 09:45:39 2016 DistUpgraded: 2016-04-24 00:21:19,103 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:3977] InstallationDate: Installed on 2013-11-17 (918 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO 2191 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed root=UUID=f6200601-c430-459d-abab-c6d45f1e147a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-04-23 (30 days ago) dmi.bios.date: 02/28/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 66CN55WW dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Yoga 13 dmi.modalias: dmi:bvnLENOVO:bvr66CN55WW:bd02/28/2013:svnLENOVO:pn2191:pvrLenovoIdeaPadYoga13:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadYoga13: dmi.product.name: 2191 dmi.product.version: Lenovo IdeaPad Yoga 13 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue May 24 08:57:44 2016 xserver.configfile: default xserver.errors: SynPS/2 Synaptics TouchPad: Read error 19 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 864 vendor LGD xserver.version: 2:1.18.3-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1585094/+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 1585094] Re: Random stuck keys on Lenovo Yoga 13
not really expired. The bug went away after some package update for several months (wow!) in 16.04 -- therefore I refused to run updates all this time to get a bit of "normal life" during typing ;) A few days ago I did an update and the damn bug returned... several years of suffering from this Bug. BTW, guys, what keyboard layout are you using when experiencing this bug? I'm experiencing it only when using Neo2 layout. It is not possible for me to find out the package causing it because of "bulk" updating -- too many packages are on list and it is rather impossible to update/upgrade them one-by-one and then test for the bug -- 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/1585094 Title: Random stuck keys on Lenovo Yoga 13 Status in xorg package in Ubuntu: New Bug description: pressing arrow keys leads randomly to the effect of stuck number key and produces output in consoles or text editors like: "22" or "88". Pressing some other key stops the infinite flooding. This may (or not) be related to the following flooding in /var/log/system May 24 10:01:30 yogi kernel: [ 3816.438579] atkbd serio0: Unknown key pressed (translated set 2, code 0xbe on isa0060/serio0). May 24 10:01:30 yogi kernel: [ 3816.438603] atkbd serio0: Use 'setkeycodes e03e ' to make it known. May 24 10:01:30 yogi kernel: [ 3816.443504] atkbd serio0: Unknown key released (translated set 2, code 0xbe on isa0060/serio0). May 24 10:01:30 yogi kernel: [ 3816.443516] atkbd serio0: Use 'setkeycodes e03e ' to make it known. these messages are generated approximately each 200 msec. If the former is not related to stuck key problem, please, ignore. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-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 CurrentDesktop: Unity Date: Tue May 24 09:45:39 2016 DistUpgraded: 2016-04-24 00:21:19,103 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:3977] InstallationDate: Installed on 2013-11-17 (918 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO 2191 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed root=UUID=f6200601-c430-459d-abab-c6d45f1e147a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-04-23 (30 days ago) dmi.bios.date: 02/28/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 66CN55WW dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Yoga 13 dmi.modalias: dmi:bvnLENOVO:bvr66CN55WW:bd02/28/2013:svnLENOVO:pn2191:pvrLenovoIdeaPadYoga13:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadYoga13: dmi.product.name: 2191 dmi.product.version: Lenovo IdeaPad Yoga 13 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue May 24 08:57:44 2016 xserver.configfile: default xserver.errors: SynPS/2 Synaptics TouchPad: Read error 19 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 864 vendor LGD xserver.version: 2:1.18.3-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1585094/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchp
[Desktop-packages] [Bug 1585094] Re: Random stuck keys on Lenovo Yoga 13
This issue is *very* likely to have smth to do with the other issue mentioned in Description above, i was not seeing this for a long time already and it appeared again similarly to sticky arrow keys: Nov 11 10:26:19 yogi kernel: [37507.484136] atkbd serio0: Unknown key released (translated set 2, code 0xbe on isa0060/serio0). Nov 11 10:26:19 yogi kernel: [37507.484144] atkbd serio0: Use 'setkeycodes e03e ' to make it known. -- 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/1585094 Title: Random stuck keys on Lenovo Yoga 13 Status in xorg package in Ubuntu: New Bug description: pressing arrow keys leads randomly to the effect of stuck number key and produces output in consoles or text editors like: "22" or "88". Pressing some other key stops the infinite flooding. This may (or not) be related to the following flooding in /var/log/system May 24 10:01:30 yogi kernel: [ 3816.438579] atkbd serio0: Unknown key pressed (translated set 2, code 0xbe on isa0060/serio0). May 24 10:01:30 yogi kernel: [ 3816.438603] atkbd serio0: Use 'setkeycodes e03e ' to make it known. May 24 10:01:30 yogi kernel: [ 3816.443504] atkbd serio0: Unknown key released (translated set 2, code 0xbe on isa0060/serio0). May 24 10:01:30 yogi kernel: [ 3816.443516] atkbd serio0: Use 'setkeycodes e03e ' to make it known. these messages are generated approximately each 200 msec. If the former is not related to stuck key problem, please, ignore. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-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 CurrentDesktop: Unity Date: Tue May 24 09:45:39 2016 DistUpgraded: 2016-04-24 00:21:19,103 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:3977] InstallationDate: Installed on 2013-11-17 (918 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO 2191 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed root=UUID=f6200601-c430-459d-abab-c6d45f1e147a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-04-23 (30 days ago) dmi.bios.date: 02/28/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 66CN55WW dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Yoga 13 dmi.modalias: dmi:bvnLENOVO:bvr66CN55WW:bd02/28/2013:svnLENOVO:pn2191:pvrLenovoIdeaPadYoga13:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadYoga13: dmi.product.name: 2191 dmi.product.version: Lenovo IdeaPad Yoga 13 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue May 24 08:57:44 2016 xserver.configfile: default xserver.errors: SynPS/2 Synaptics TouchPad: Read error 19 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 864 vendor LGD xserver.version: 2:1.18.3-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1585094/+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 1618424] Re: The internet applet crashes randomly.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager-applet (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1618424 Title: The internet applet crashes randomly. Status in network-manager-applet package in Ubuntu: Confirmed Bug description: When i restart it manually via console, it crashes again after a minute. Output: nero@Ubuntu-Nero:~$ /usr/bin/nm-applet & [1] 8821 nero@Ubuntu-Nero:~$ nm-applet-Message: New secrets for Morgen/802-11-wireless-security requested; ask the user ** GLib:ERROR:/build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gvarianttypeinfo.c:163:g_variant_type_info_check: assertion failed: (info->alignment == 0 || info->alignment == 1 || info->alignment == 3 || info->alignment == 7) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager-gnome 1.2.0-0ubuntu0.16.04.3 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Aug 30 13:32:49 2016 ExecutablePath: /usr/bin/nm-applet IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-09-27 (338 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) IpRoute: default via 10.92.72.1 dev wlan0 proto static metric 600 10.92.72.0/21 dev wlan0 proto kernel scope link src 10.92.75.247 metric 600 169.254.0.0/16 dev wlan0 scope link metric 1000 195.130.132.102 via 10.92.72.1 dev wlan0 proto dhcp metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager-applet UpgradeStatus: Upgraded to xenial on 2016-08-20 (9 days ago) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlan0 wifi connected/org/freedesktop/NetworkManager/Devices/0 Morgen 90d2d2a9-4785-4da3-8dba-084c32179bf0 /org/freedesktop/NetworkManager/ActiveConnection/9 eth0ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/2 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.0connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1618424/+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 1641081] [NEW] package libgeonames-common 0.2+16.04.20160426-0ubuntu1 failed to install/upgrade: il pacchetto si trova in uno stato di inconsistenza grave: è necessario instal
Public bug reported: I installed this package but it's always error ProblemType: Package DistroRelease: Ubuntu 16.10 Package: libgeonames-common 0.2+16.04.20160426-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic i686 ApportVersion: 2.20.3-0ubuntu8 Architecture: i386 Date: Fri Nov 11 10:56:25 2016 Dependencies: DpkgTerminalLog: dpkg: errore nell'elaborare il pacchetto libgeonames-common (--remove): il pacchetto si trova in uno stato di inconsistenza grave: è necessario installarlo nuovamente prima di rimuoverlo ErrorMessage: il pacchetto si trova in uno stato di inconsistenza grave: è necessario installarlo nuovamente prima di rimuoverlo InstallationDate: Installed on 2016-10-17 (25 days ago) InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Release i386 (20161012.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: geonames Title: package libgeonames-common 0.2+16.04.20160426-0ubuntu1 failed to install/upgrade: il pacchetto si trova in uno stato di inconsistenza grave: è necessario installarlo nuovamente prima di rimuoverlo UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: geonames (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 yakkety -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to geonames in Ubuntu. https://bugs.launchpad.net/bugs/1641081 Title: package libgeonames-common 0.2+16.04.20160426-0ubuntu1 failed to install/upgrade: il pacchetto si trova in uno stato di inconsistenza grave: è necessario installarlo nuovamente prima di rimuoverlo Status in geonames package in Ubuntu: New Bug description: I installed this package but it's always error ProblemType: Package DistroRelease: Ubuntu 16.10 Package: libgeonames-common 0.2+16.04.20160426-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic i686 ApportVersion: 2.20.3-0ubuntu8 Architecture: i386 Date: Fri Nov 11 10:56:25 2016 Dependencies: DpkgTerminalLog: dpkg: errore nell'elaborare il pacchetto libgeonames-common (--remove): il pacchetto si trova in uno stato di inconsistenza grave: è necessario installarlo nuovamente prima di rimuoverlo ErrorMessage: il pacchetto si trova in uno stato di inconsistenza grave: è necessario installarlo nuovamente prima di rimuoverlo InstallationDate: Installed on 2016-10-17 (25 days ago) InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Release i386 (20161012.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: geonames Title: package libgeonames-common 0.2+16.04.20160426-0ubuntu1 failed to install/upgrade: il pacchetto si trova in uno stato di inconsistenza grave: è necessario installarlo nuovamente prima di rimuoverlo UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geonames/+bug/1641081/+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 1638245] Re: Files in the root of a folder on another partition symlinked to user's home cannot be moved to trash because of a patch in this package
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: glib2.0 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1638245 Title: Files in the root of a folder on another partition symlinked to user's home cannot be moved to trash because of a patch in this package Status in glib2.0 package in Ubuntu: Confirmed Bug description: I'm on Ubuntu 16.10 64-bit with libglib2.0-0 version 2.50.0-1. I've reported this bug (or marked as "it affects me") in a couple of other places before I've finally discovered that this is the package that's causing this problem, which unfortunately has been around for a couple of years now. This bug has been reported upstream as well, but it's just taking very very long to arrive at a decision and take action it seems. Apparently one of the patches (https://sources.debian.net/patches/glib2.0/2.50.1-1/0001-Fix- trashing-on-overlayfs.patch/) which is here (https://launchpad.net/ubuntu/+archive/primary/+files/glib2.0_2.50.0-1.debian.tar.xz) to the original package which is here (https://launchpad.net/ubuntu/+archive/primary/+files/glib2.0_2.50.0.orig.tar.xz) is the root cause of this annoying problem. As I prefer keeping one patition for the root filesystem (/), one partition for user settings (/home) and one partition for user data (Documents, Downloads, Drive, Music, Pictures, Public, Videos) which are simply symlinked to my home folder for ease of use, I cannot move any file to the trash in the root of these folders when I access them from my home folder or nautilus sidebar. This problem doesn't affect folders at all, nor any other files in subfolders, etc. So I was wondering if Ubuntu devs can leave out that particular patch when building this package for Ubuntu - if it doesn't cause more harm, which I doubt. Otherwise, I would appreciate if I could learn how to do it myself: how can I (as an end-user) compile the contents of "glib2.0_2.50.0.orig.tar.xz" with all the patches, etc. in "glib2.0_2.50.0-1.debian.tar.xz" except "0001-Fix-trashing-on- overlayfs.patch"? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1638245/+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 1495781] Re: Can't move to trash in data partition
*** This bug is a duplicate of bug 1638245 *** https://bugs.launchpad.net/bugs/1638245 ** This bug is no longer a duplicate of bug 1449112 can't move files to trash without any owner/permission issues ** This bug has been marked a duplicate of bug 1638245 Files in the root of a folder on another partition symlinked to user's home cannot be moved to trash because of a patch in this package -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1495781 Title: Can't move to trash in data partition Status in glib2.0 package in Ubuntu: Confirmed Bug description: I have a clean install of Ubuntu 15.04. I partitioned my disk into root and data partitions. I then created ~/Data folder, and mount data partition on it. I then created symlinks for ~/Downloads, ~/Music, etc... to ~/Data/Downloads, ~/Data/Music, etc... Whenever I delete files directly inside ~/ they seem to go to the Trash (in ~/.local/share/Trash), but when I try to delete files in other folders that are linked to ~/Data (for example ~/Downloads, or ~/Data/Downloads) Nautilus says: "File can't be put in the trash. Do you want to delete it immediately?". I compile glib without patch at https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1445622/comments/25, then it works well. report from https://bugs.launchpad.net/nautilus/+bug/1406376 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1495781/+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 1449112] Re: can't move files to trash without any owner/permission issues
*** This bug is a duplicate of bug 1638245 *** https://bugs.launchpad.net/bugs/1638245 IMPORTANT UPDATE: Now that we know the root cause of this problem thanks to CzBix (see https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1449112/comments/7) I have reported this issue as a bug in the glib2.0 package (instead of nautilus) https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1638245 It seems we need to wait for a patch to be made to a patch made to the original package, as that patch --I'm told-- also serves an important purpose which should not be omitted (as the workaround above, although it seems quite harmless, I don't know) Therefore I think it is better to follow the developments there, and close this one. ** This bug has been marked a duplicate of bug 1638245 Files in the root of a folder on another partition symlinked to user's home cannot be moved to trash because of a patch in this package -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1449112 Title: can't move files to trash without any owner/permission issues Status in Nautilus: Unknown Status in nautilus package in Ubuntu: Triaged Bug description: This is something that wouldn't happen before upgrading from Ubuntu 14.10 / Nautilus 3.10 to Ubuntu 15.04 / Nautilus 3.14: I have a proper HOME partition and most User folders there (Documents, Downloads, Music, Pictures, Videos) are merely SYMLINKS to folders with the same names in a DATA partition which is mounted automatically at startup with proper options in fstab. Now -- unlike before -- when I attempt to delete an item in one of these folders after I open it via the SYMLINK I get the message "... can't be put in the trash. Do you want to delete it immediately?" although it is immediately moved to the Trash after I open the folder via the Data partition in the sidebar. (Naturally there are no such problems with items in other (real) items in my Home folder. Nautilus now seems confused about / not knowing where to move the item in question; to the Trash folder in the Home partition (symlink location) or the Data partition (real item location). To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1449112/+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 1406376] Re: Can't move to trash in data partition
*** This bug is a duplicate of bug 1638245 *** https://bugs.launchpad.net/bugs/1638245 ** This bug is no longer a duplicate of bug 1449112 can't move files to trash without any owner/permission issues ** This bug has been marked a duplicate of bug 1638245 Files in the root of a folder on another partition symlinked to user's home cannot be moved to trash because of a patch in this package -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1406376 Title: Can't move to trash in data partition Status in Nautilus: New Status in nautilus package in Ubuntu: Triaged Bug description: I have a clean install of Ubuntu 14.10. I partitioned my disk into / (20GB) and /data (230GB) partitions. I then created /data/home/ubuntu, moved my /home there, and bind mounted /home to /data/home/ubuntu. I then created symlinks for ~/Downloads, ~/Music, etc... to /data/Downloads, /data/Music, etc... Whenever I delete files directly inside ~/ they seem to go to the Trash (in ~/.local/share/Trash), but when I try to delete files in other folders that are linked to /data (for example ~/Downloads, or /data/Downloads) Nautilus says: "File can't be put in the trash. Do you want to delete it immediately?". To fix it, I attempted to create trash folders with permissions 1700 and chowned to my user in the following places (to no avail!): * /data/.Trash-$(id -u) * /data/.Trash * /.Trash-$(id -u) * /.Trash To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1406376/+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 1638245] Re: Files in the root of a folder on another partition symlinked to user's home cannot be moved to trash because of a patch in this package
Dear Iain, Maybe the fix suggested here is all we need??? https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1495781/comments/6 Thanks... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1638245 Title: Files in the root of a folder on another partition symlinked to user's home cannot be moved to trash because of a patch in this package Status in glib2.0 package in Ubuntu: Confirmed Bug description: I'm on Ubuntu 16.10 64-bit with libglib2.0-0 version 2.50.0-1. I've reported this bug (or marked as "it affects me") in a couple of other places before I've finally discovered that this is the package that's causing this problem, which unfortunately has been around for a couple of years now. This bug has been reported upstream as well, but it's just taking very very long to arrive at a decision and take action it seems. Apparently one of the patches (https://sources.debian.net/patches/glib2.0/2.50.1-1/0001-Fix- trashing-on-overlayfs.patch/) which is here (https://launchpad.net/ubuntu/+archive/primary/+files/glib2.0_2.50.0-1.debian.tar.xz) to the original package which is here (https://launchpad.net/ubuntu/+archive/primary/+files/glib2.0_2.50.0.orig.tar.xz) is the root cause of this annoying problem. As I prefer keeping one patition for the root filesystem (/), one partition for user settings (/home) and one partition for user data (Documents, Downloads, Drive, Music, Pictures, Public, Videos) which are simply symlinked to my home folder for ease of use, I cannot move any file to the trash in the root of these folders when I access them from my home folder or nautilus sidebar. This problem doesn't affect folders at all, nor any other files in subfolders, etc. So I was wondering if Ubuntu devs can leave out that particular patch when building this package for Ubuntu - if it doesn't cause more harm, which I doubt. Otherwise, I would appreciate if I could learn how to do it myself: how can I (as an end-user) compile the contents of "glib2.0_2.50.0.orig.tar.xz" with all the patches, etc. in "glib2.0_2.50.0-1.debian.tar.xz" except "0001-Fix-trashing-on- overlayfs.patch"? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1638245/+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 1495781] Re: Can't move to trash in data partition
*** This bug is a duplicate of bug 1638245 *** https://bugs.launchpad.net/bugs/1638245 UPDATE: Sorry, in an attempt to make some progress in chasing this issue, I found myself making a new bug report here, and then marked this earlier bug report as a duplicate because I forgot it while wondering around the maze ;-) Anyway I think we might achieve some progress there -- as I've managed to add Iain Lane, a Debian and Ubuntu developer who made that particular patch, to subscribers, and I guess he's now trying to find a fix for this problem without getting rid of that patch which he says is also essential. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1495781 Title: Can't move to trash in data partition Status in glib2.0 package in Ubuntu: Confirmed Bug description: I have a clean install of Ubuntu 15.04. I partitioned my disk into root and data partitions. I then created ~/Data folder, and mount data partition on it. I then created symlinks for ~/Downloads, ~/Music, etc... to ~/Data/Downloads, ~/Data/Music, etc... Whenever I delete files directly inside ~/ they seem to go to the Trash (in ~/.local/share/Trash), but when I try to delete files in other folders that are linked to ~/Data (for example ~/Downloads, or ~/Data/Downloads) Nautilus says: "File can't be put in the trash. Do you want to delete it immediately?". I compile glib without patch at https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1445622/comments/25, then it works well. report from https://bugs.launchpad.net/nautilus/+bug/1406376 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1495781/+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 1638245] Re: Files in the root of a folder on another partition symlinked to user's home cannot be moved to trash because of a patch in this package
That disables the patch? Please please could you give me very very simple steps that will let me reproduce the problem in a VM. Explain what happens that is wrong and what should happen instead. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1638245 Title: Files in the root of a folder on another partition symlinked to user's home cannot be moved to trash because of a patch in this package Status in glib2.0 package in Ubuntu: Confirmed Bug description: I'm on Ubuntu 16.10 64-bit with libglib2.0-0 version 2.50.0-1. I've reported this bug (or marked as "it affects me") in a couple of other places before I've finally discovered that this is the package that's causing this problem, which unfortunately has been around for a couple of years now. This bug has been reported upstream as well, but it's just taking very very long to arrive at a decision and take action it seems. Apparently one of the patches (https://sources.debian.net/patches/glib2.0/2.50.1-1/0001-Fix- trashing-on-overlayfs.patch/) which is here (https://launchpad.net/ubuntu/+archive/primary/+files/glib2.0_2.50.0-1.debian.tar.xz) to the original package which is here (https://launchpad.net/ubuntu/+archive/primary/+files/glib2.0_2.50.0.orig.tar.xz) is the root cause of this annoying problem. As I prefer keeping one patition for the root filesystem (/), one partition for user settings (/home) and one partition for user data (Documents, Downloads, Drive, Music, Pictures, Public, Videos) which are simply symlinked to my home folder for ease of use, I cannot move any file to the trash in the root of these folders when I access them from my home folder or nautilus sidebar. This problem doesn't affect folders at all, nor any other files in subfolders, etc. So I was wondering if Ubuntu devs can leave out that particular patch when building this package for Ubuntu - if it doesn't cause more harm, which I doubt. Otherwise, I would appreciate if I could learn how to do it myself: how can I (as an end-user) compile the contents of "glib2.0_2.50.0.orig.tar.xz" with all the patches, etc. in "glib2.0_2.50.0-1.debian.tar.xz" except "0001-Fix-trashing-on- overlayfs.patch"? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1638245/+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 1641090] [NEW] package libpolkit-agent-1-0:i386 0.105-11ubuntu2 [modified: usr/lib/i386-linux-gnu/libpolkit-agent-1.so.0.0.0] failed to install/upgrade: package libpolkit-agent
Public bug reported: ... ProblemType: Package DistroRelease: Ubuntu 15.10 Package: libpolkit-agent-1-0:i386 0.105-11ubuntu2 [modified: usr/lib/i386-linux-gnu/libpolkit-agent-1.so.0.0.0] ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic i686 NonfreeKernelModules: wl ApportVersion: 2.19.1-0ubuntu3 Architecture: i386 Date: Fri Nov 11 08:55:09 2016 DpkgHistoryLog: Start-Date: 2016-11-11 08:53:58 Commandline: aptdaemon role='role-commit-packages' sender=':1.73' Install: chromium-browser-l10n:i386 (51.0.2704.79-0ubuntu0.15.10.1.1232, automatic), chromium-browser:i386 (51.0.2704.79-0ubuntu0.15.10.1.1232), chromium-codecs-ffmpeg-extra:i386 (51.0.2704.79-0ubuntu0.15.10.1.1232, automatic) DuplicateSignature: package:libpolkit-agent-1-0:i386:0.105-11ubuntu2 [modified: usr/lib/i386-linux-gnu/libpolkit-agent-1.so.0.0.0]:package libpolkit-agent-1-0:i386 is not ready for configuration cannot configure (current status 'half-installed') ErrorMessage: package libpolkit-agent-1-0:i386 is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2016-09-30 (41 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release i386 (20151021) RelatedPackageVersions: dpkg 1.18.2ubuntu5.1 apt 1.0.10.2ubuntu3 SourcePackage: policykit-1 Title: package libpolkit-agent-1-0:i386 0.105-11ubuntu2 [modified: usr/lib/i386-linux-gnu/libpolkit-agent-1.so.0.0.0] failed to install/upgrade: package libpolkit-agent-1-0:i386 is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: policykit-1 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 need-duplicate-check wily -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1641090 Title: package libpolkit-agent-1-0:i386 0.105-11ubuntu2 [modified: usr/lib/i386-linux-gnu/libpolkit-agent-1.so.0.0.0] failed to install/upgrade: package libpolkit-agent-1-0:i386 is not ready for configuration cannot configure (current status 'half-installed') Status in policykit-1 package in Ubuntu: New Bug description: ... ProblemType: Package DistroRelease: Ubuntu 15.10 Package: libpolkit-agent-1-0:i386 0.105-11ubuntu2 [modified: usr/lib/i386-linux-gnu/libpolkit-agent-1.so.0.0.0] ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic i686 NonfreeKernelModules: wl ApportVersion: 2.19.1-0ubuntu3 Architecture: i386 Date: Fri Nov 11 08:55:09 2016 DpkgHistoryLog: Start-Date: 2016-11-11 08:53:58 Commandline: aptdaemon role='role-commit-packages' sender=':1.73' Install: chromium-browser-l10n:i386 (51.0.2704.79-0ubuntu0.15.10.1.1232, automatic), chromium-browser:i386 (51.0.2704.79-0ubuntu0.15.10.1.1232), chromium-codecs-ffmpeg-extra:i386 (51.0.2704.79-0ubuntu0.15.10.1.1232, automatic) DuplicateSignature: package:libpolkit-agent-1-0:i386:0.105-11ubuntu2 [modified: usr/lib/i386-linux-gnu/libpolkit-agent-1.so.0.0.0]:package libpolkit-agent-1-0:i386 is not ready for configuration cannot configure (current status 'half-installed') ErrorMessage: package libpolkit-agent-1-0:i386 is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2016-09-30 (41 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release i386 (20151021) RelatedPackageVersions: dpkg 1.18.2ubuntu5.1 apt 1.0.10.2ubuntu3 SourcePackage: policykit-1 Title: package libpolkit-agent-1-0:i386 0.105-11ubuntu2 [modified: usr/lib/i386-linux-gnu/libpolkit-agent-1.so.0.0.0] failed to install/upgrade: package libpolkit-agent-1-0:i386 is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1641090/+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 1638245] Re: Files in the root of a folder on another partition symlinked to user's home cannot be moved to trash because of a patch in this package
Sorry I'm just a user, I don't know much about these source codes, I thought it was a fix, but if it simply forces skipping the patch, it's no good for you, of course ;-) To reproduce the problem you need another partition other than the one where the user home directory is, and follow these simple steps: 1) Go to Desktop. 2) Create a symbolic link to any folder in another partition (or disk) in your computer (i.e. not removable media) 3) Click that symlink on your desktop to access that folder. 4) Create a new document there - any type of file, even empty, will do. 5) Press the Delete key to move that file to trash: you should see that message telling you it can't be done (although you can safely move any subfolder or any file in subfolders to trash, and although you can do it if you access that folder directly instead of going via that symlink on your home partition). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1638245 Title: Files in the root of a folder on another partition symlinked to user's home cannot be moved to trash because of a patch in this package Status in glib2.0 package in Ubuntu: Confirmed Bug description: I'm on Ubuntu 16.10 64-bit with libglib2.0-0 version 2.50.0-1. I've reported this bug (or marked as "it affects me") in a couple of other places before I've finally discovered that this is the package that's causing this problem, which unfortunately has been around for a couple of years now. This bug has been reported upstream as well, but it's just taking very very long to arrive at a decision and take action it seems. Apparently one of the patches (https://sources.debian.net/patches/glib2.0/2.50.1-1/0001-Fix- trashing-on-overlayfs.patch/) which is here (https://launchpad.net/ubuntu/+archive/primary/+files/glib2.0_2.50.0-1.debian.tar.xz) to the original package which is here (https://launchpad.net/ubuntu/+archive/primary/+files/glib2.0_2.50.0.orig.tar.xz) is the root cause of this annoying problem. As I prefer keeping one patition for the root filesystem (/), one partition for user settings (/home) and one partition for user data (Documents, Downloads, Drive, Music, Pictures, Public, Videos) which are simply symlinked to my home folder for ease of use, I cannot move any file to the trash in the root of these folders when I access them from my home folder or nautilus sidebar. This problem doesn't affect folders at all, nor any other files in subfolders, etc. So I was wondering if Ubuntu devs can leave out that particular patch when building this package for Ubuntu - if it doesn't cause more harm, which I doubt. Otherwise, I would appreciate if I could learn how to do it myself: how can I (as an end-user) compile the contents of "glib2.0_2.50.0.orig.tar.xz" with all the patches, etc. in "glib2.0_2.50.0-1.debian.tar.xz" except "0001-Fix-trashing-on- overlayfs.patch"? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1638245/+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 1575000] Re: font glyph corruption on dialog box
tumbleweed.. tested or not, the bug should be closed with latest updates ** Changed in: xorg-server (Ubuntu Xenial) Status: Incomplete => 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/1575000 Title: font glyph corruption on dialog box Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Xenial: Fix Released Bug description: [Impact] * This makes it impossible to read some text (usually yes/no questions) in Libreoffice. This makes it more difficult to use LibreOffice on AMD graphics. [Test Case] 1. Open for instance LibreOffice Writer 2. Copy some text to the clipboard 3. Open the Paste Special dialog with CTRL-SHIFT-V [Regression Potential] This modifies glamor to be used less. There might be a potential for a performance hit in other cases? [Original Report] I get a font glyph corruption in various dialog boxes in libreoffice. This happens using the following graphic configuration: *-display description: VGA compatible controller product: Bonaire [FirePro W5100] vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:03:00.0 version: 00 width: 64 bits clock: 33MHz capabilities: vga_controller bus_master cap_list rom configuration: driver=radeon latency=0 I don't see this in other graphics (NVIDIA, INTEL). Steps to reproduce: 1. Open for instance LibreOffice Writer 2. Copy some text to the clipboard 3. Open the Paste Special dialog with CTRL-SHIFT-V I attach a screenshot of the corrupted font. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg-video-radeon 1:7.7.0-1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-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 CurrentDesktop: Unity Date: Tue Apr 26 09:23:41 2016 DistUpgraded: 2016-03-11 12:35:09,412 DEBUG enabling apt cron job DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.18, 4.4.0-18-generic, x86_64: installed virtualbox, 5.0.18, 4.4.0-21-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Bonaire [FirePro W5100] [1002:6649] (prog-if 00 [VGA controller]) Subsystem: Dell Bonaire [FirePro W5100] [1028:230c] InstallationDate: Installed on 2015-10-17 (191 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. Precision Tower 7810 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=63c3c29d-24d9-4ecb-8511-3f2291792bc5 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-ati UpgradeStatus: Upgraded to xenial on 2016-03-11 (45 days ago) dmi.bios.date: 04/14/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0GWHMW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd04/14/2015:svnDellInc.:pnPrecisionTower7810:pvr01:rvnDellInc.:rn0GWHMW:rvrA00:cvnDellInc.:ct7:cvr: dmi.product.name: Precision Tower 7810 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon Apr 25 08:20:34 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.3-1ubuntu2 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1575000/+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 1638245] Re: Files in the root of a folder on another partition symlinked to user's home cannot be moved to trash because of a patch in this package
Steps: 1. Install system and partition disk into root and data partitions 2. create ~/Data folder, and mount data partition on it 3. create symlinks for ~/whatever/ to ~/Data/something/ 4. delete files directly inside ~/whatever/ What happen: Then Nautilus says: "File can't be put in the trash. Do you want to delete it immediately?". What should happen: The files moved into Trash. What I think: The issue here is glib use parent dir(on another partition) to find Trash location, and move files from partition A(~/Data/something/xxx) to partition B(~/.local/share/Trash) failed by crossed device. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1638245 Title: Files in the root of a folder on another partition symlinked to user's home cannot be moved to trash because of a patch in this package Status in glib2.0 package in Ubuntu: Confirmed Bug description: I'm on Ubuntu 16.10 64-bit with libglib2.0-0 version 2.50.0-1. I've reported this bug (or marked as "it affects me") in a couple of other places before I've finally discovered that this is the package that's causing this problem, which unfortunately has been around for a couple of years now. This bug has been reported upstream as well, but it's just taking very very long to arrive at a decision and take action it seems. Apparently one of the patches (https://sources.debian.net/patches/glib2.0/2.50.1-1/0001-Fix- trashing-on-overlayfs.patch/) which is here (https://launchpad.net/ubuntu/+archive/primary/+files/glib2.0_2.50.0-1.debian.tar.xz) to the original package which is here (https://launchpad.net/ubuntu/+archive/primary/+files/glib2.0_2.50.0.orig.tar.xz) is the root cause of this annoying problem. As I prefer keeping one patition for the root filesystem (/), one partition for user settings (/home) and one partition for user data (Documents, Downloads, Drive, Music, Pictures, Public, Videos) which are simply symlinked to my home folder for ease of use, I cannot move any file to the trash in the root of these folders when I access them from my home folder or nautilus sidebar. This problem doesn't affect folders at all, nor any other files in subfolders, etc. So I was wondering if Ubuntu devs can leave out that particular patch when building this package for Ubuntu - if it doesn't cause more harm, which I doubt. Otherwise, I would appreciate if I could learn how to do it myself: how can I (as an end-user) compile the contents of "glib2.0_2.50.0.orig.tar.xz" with all the patches, etc. in "glib2.0_2.50.0-1.debian.tar.xz" except "0001-Fix-trashing-on- overlayfs.patch"? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1638245/+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
Re: [Desktop-packages] [Bug 1638245] Re: Files in the root of a folder on another partition symlinked to user's home cannot be moved to trash because of a patch in this package
On Fri, Nov 11, 2016 at 11:01:57AM -, Sadi Yumuşak wrote: > Sorry I'm just a user, I don't know much about these source codes, I > thought it was a fix, but if it simply forces skipping the patch, it's > no good for you, of course ;-) > > To reproduce the problem you need another partition other than the one > where the user home directory is, and follow these simple steps: > > 1) Go to Desktop. > 2) Create a symbolic link to any folder in another partition (or disk) in > your computer (i.e. not removable media) > 3) Click that symlink on your desktop to access that folder. > 4) Create a new document there - any type of file, even empty, will do. > 5) Press the Delete key to move that file to trash: you should see that > message telling you it can't be done (although you can safely move any > subfolder or any file in subfolders to trash, and although you can do it if > you access that folder directly instead of going via that symlink on your > home partition). Ok, thanks, that sounds like something to try. I'll have a go next week. -- Iain Lane [ i...@orangesquash.org.uk ] Debian Developer [ la...@debian.org ] Ubuntu Developer [ la...@ubuntu.com ] -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1638245 Title: Files in the root of a folder on another partition symlinked to user's home cannot be moved to trash because of a patch in this package Status in glib2.0 package in Ubuntu: Confirmed Bug description: I'm on Ubuntu 16.10 64-bit with libglib2.0-0 version 2.50.0-1. I've reported this bug (or marked as "it affects me") in a couple of other places before I've finally discovered that this is the package that's causing this problem, which unfortunately has been around for a couple of years now. This bug has been reported upstream as well, but it's just taking very very long to arrive at a decision and take action it seems. Apparently one of the patches (https://sources.debian.net/patches/glib2.0/2.50.1-1/0001-Fix- trashing-on-overlayfs.patch/) which is here (https://launchpad.net/ubuntu/+archive/primary/+files/glib2.0_2.50.0-1.debian.tar.xz) to the original package which is here (https://launchpad.net/ubuntu/+archive/primary/+files/glib2.0_2.50.0.orig.tar.xz) is the root cause of this annoying problem. As I prefer keeping one patition for the root filesystem (/), one partition for user settings (/home) and one partition for user data (Documents, Downloads, Drive, Music, Pictures, Public, Videos) which are simply symlinked to my home folder for ease of use, I cannot move any file to the trash in the root of these folders when I access them from my home folder or nautilus sidebar. This problem doesn't affect folders at all, nor any other files in subfolders, etc. So I was wondering if Ubuntu devs can leave out that particular patch when building this package for Ubuntu - if it doesn't cause more harm, which I doubt. Otherwise, I would appreciate if I could learn how to do it myself: how can I (as an end-user) compile the contents of "glib2.0_2.50.0.orig.tar.xz" with all the patches, etc. in "glib2.0_2.50.0-1.debian.tar.xz" except "0001-Fix-trashing-on- overlayfs.patch"? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1638245/+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 1575000] Re: font glyph corruption on dialog box
** No longer affects: xorg-server -- 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/1575000 Title: font glyph corruption on dialog box Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Xenial: Fix Released Bug description: [Impact] * This makes it impossible to read some text (usually yes/no questions) in Libreoffice. This makes it more difficult to use LibreOffice on AMD graphics. [Test Case] 1. Open for instance LibreOffice Writer 2. Copy some text to the clipboard 3. Open the Paste Special dialog with CTRL-SHIFT-V [Regression Potential] This modifies glamor to be used less. There might be a potential for a performance hit in other cases? [Original Report] I get a font glyph corruption in various dialog boxes in libreoffice. This happens using the following graphic configuration: *-display description: VGA compatible controller product: Bonaire [FirePro W5100] vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:03:00.0 version: 00 width: 64 bits clock: 33MHz capabilities: vga_controller bus_master cap_list rom configuration: driver=radeon latency=0 I don't see this in other graphics (NVIDIA, INTEL). Steps to reproduce: 1. Open for instance LibreOffice Writer 2. Copy some text to the clipboard 3. Open the Paste Special dialog with CTRL-SHIFT-V I attach a screenshot of the corrupted font. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg-video-radeon 1:7.7.0-1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-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 CurrentDesktop: Unity Date: Tue Apr 26 09:23:41 2016 DistUpgraded: 2016-03-11 12:35:09,412 DEBUG enabling apt cron job DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.18, 4.4.0-18-generic, x86_64: installed virtualbox, 5.0.18, 4.4.0-21-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Bonaire [FirePro W5100] [1002:6649] (prog-if 00 [VGA controller]) Subsystem: Dell Bonaire [FirePro W5100] [1028:230c] InstallationDate: Installed on 2015-10-17 (191 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. Precision Tower 7810 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=63c3c29d-24d9-4ecb-8511-3f2291792bc5 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-ati UpgradeStatus: Upgraded to xenial on 2016-03-11 (45 days ago) dmi.bios.date: 04/14/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0GWHMW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd04/14/2015:svnDellInc.:pnPrecisionTower7810:pvr01:rvnDellInc.:rn0GWHMW:rvrA00:cvnDellInc.:ct7:cvr: dmi.product.name: Precision Tower 7810 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon Apr 25 08:20:34 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.3-1ubuntu2 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1575000/+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 1478319] Re: Wifi doesn't reconnect to AP if it uses the same SSID than another AP
I can confirm this behaviour. I have at home a wifi extender from tp link (RE450) and I have given SSID on the extender the same names as on my wifi router. Both in the case of 2,4 GHz and 5 GHz. Since OTA13 I have constant disconnects with my Meizu MX4 running Ubuntu Touch. -- 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/1478319 Title: Wifi doesn't reconnect to AP if it uses the same SSID than another AP Status in Canonical System Image: Incomplete Status in network-manager package in Ubuntu: Confirmed Bug description: current build number: 68 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2015-07-24 08:00:20 version version: 68 version ubuntu: 20150724 version device: 20150709-8965e37 version custom: 20150716-819-8-42 My ISP (Free in France) provides a hotspot service so that customers can use the connection of any other customer using a generic open Wifi connection (for reference http://www.free.fr/assistance/2303.html - in French) The SSID is called 'FreeWifi' on all the boxes but obviously APs are all different since it's customers' DSL routers. When I connect to one of this access point, suspend the phone and resume it in another location where the SSID is available but from a different AP, the phone doesn't connect to this AP and the list of networks in the network-indicator doesn't refresh and still show the list of network from the previous location. I have to forget the network called 'FreeWifi' and reconnect in order to refresh the list and make it work. It's 100% reproducible. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1478319/+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 1575809] Re: keyboard layout change applet doesn't work on login screen
Changing the keyboard layout from French bépo latin 9 to French bépo cleared the issue. French bépo latin 9 is probably outdated. ** Changed in: unity-greeter (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1575809 Title: keyboard layout change applet doesn't work on login screen Status in unity-greeter package in Ubuntu: Invalid Bug description: I installed Ubuntu with some layout mainly used the other users (standard layout). I selected another layout for my own session (Dvorak type layout). No issues so far, after logon my Dvorak layout is selected by default on my account only. Nevertheless, when I am on the logging screen (for logging on, when my session is not yet opened), the kb layout applet let's me choose the layout I want to use, but whatever the choice, it is the main layout which is chosen. In case of screen lock, my Dvorak layout remains active which is correct to log back in. This was working fine on 14.04. This bug happens with a fresh install of 16.04 . Description: Ubuntu 16.04 LTS Release: 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1575809/+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 1407188] Re: No matter what I do to the zenity window, it will shut down the system
Is there any progress? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to zenity in Ubuntu. https://bugs.launchpad.net/bugs/1407188 Title: No matter what I do to the zenity window,it will shut down the system Status in zenity package in Ubuntu: Confirmed Bug description: I am using ubuntu 14.04 gnome-session-fallback,and i want to shut down the system . When I click the default top-right button located on the top gnome-panel,and ubuntu gives me a window or may be a widget named zenity. And then no matter what I do to it ,including press any button on this window,or close it ,or press alt+F4 to terminate it, it will shut my system down, i can't even cancel it Well ,sorry for my broken poor english ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: zenity 3.8.0-1ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 Uname: Linux 3.13.0-44-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CurrentDesktop: Unity Date: Sat Jan 3 09:47:00 2015 InstallationDate: Installed on 2014-12-16 (17 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) ProcEnviron: LANGUAGE=zh_CN:zh PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=zh_CN.UTF-8 SHELL=/bin/bash SourcePackage: zenity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zenity/+bug/1407188/+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 1515554] Re: Using gedit to open a huge text file uses to much memory
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gedit (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1515554 Title: Using gedit to open a huge text file uses to much memory Status in gedit package in Ubuntu: Confirmed Bug description: I made a file by dumping an epk-file with hexdump and as I wanted to open the file with gedit it worked fine in the beginning, but then gedit seemed to run out of memory and therefore crashed, but no crash reporter could load. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: gedit 3.10.4-0ubuntu13 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Thu Nov 12 11:45:46 2015 InstallationDate: Installed on 2015-11-11 (1 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1515554/+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 1196239] Re: Add support for fake modes on laptop screens which only have one
I was just including my example as another plus point for fake modes ("scale"
in this case didn't mean "output scaling".
If we had the fake modes then output scaling wouldn't really be required in
this case, as we would have a set of mutually inclusive modes to chose from.
--
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/1196239
Title:
Add support for fake modes on laptop screens which only have one
Status in Canonical System Image:
Triaged
Status in Mir:
Incomplete
Status in xorg-server package in Ubuntu:
Won't Fix
Bug description:
Reproduce:
run mirout
What happens:
I only see one resolution supported.
What should happen:
I should see more resolutions, like I do on unity7.
I guess, if in doubt, “support” the same ones as xrandr.
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1196239/+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 1576424] Re: Gimp crashes with text tool & caps lock
Uploaded to unapproved, thanks. ** Changed in: gtk+2.0 (Ubuntu Xenial) Status: New => In Progress ** Changed in: gtk+2.0 (Ubuntu Yakkety) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1576424 Title: Gimp crashes with text tool & caps lock Status in GTK+: Fix Released Status in gtk+2.0 package in Ubuntu: Fix Committed Status in gtk+2.0 source package in Xenial: In Progress Status in gtk+2.0 source package in Yakkety: In Progress Bug description: [Impact] Gimp crashes with a segfault when I use caps lock while renaming a layer. It is possible Caps lock causes crashes in other events also. [Test Case] Steps to reproduce: 1. Open a new blank gimp document 2. select the text tool 3. type a couple of words of text (gimp will create a text layer above the background layer) 4. with the text tool still selected, click on the background layer (just to move away from the text layer) 5. now double click on the text layer to rename the layer (layer name gets highlighted) 6. press the caps lock key 7. click on the background layer again (without renaming or doing anything to the text layer) Now repeat steps 5 and 6. Gimp crashes. [Regression Potential] None expected. The patch used has been taken from upstream development. https://git.gnome.org/browse/gtk%2B/commit/?id=2811221d7039bd82265ce36a1b0dd9a0eeb431ad Packages for Xenial and Yakkety have been built in a PPA and regression tested. [ Other Info ] I can force this to happen every time I launch Gimp. Rebooting makes no difference. It seems to be the second time I press caps lock that forces the crash. I tried launching Gimp with caps lock on vs caps lock off, but I don't believe it made any difference. I can force a crash every time following the above sequence. I deleted my gimp preferences folder then rebooted for good measure. Gimp created a fresh preferences folder, but it hasn't solved the problem. I was originally in single window mode, but the new preferences folder put me back to multi window, but it crashes either way. I ran dmesg | tail after the crash and got the following line: gimp-2.8[2976]: segfault at 14 ip 7ff5100e0cd9 sp 7ffef11bfcb0 error 4 in libgtk-x11-2.0.so.0.2400.30[7ff51001b000+43e000] I'm using a fresh install of Xubuntu 16.04 with nvidia 361.42 driver (available from the Additional Drivers tab). In that same tab, I also have enabled Processor microcode firmware for Intel CPUs. Terminal tells me Gimp version is 2.8.16-1ubuntu1 I'm not very experienced with bug reporting and not sure what other information I need to supply. Gimp was absolutely rock solid on this machine with 15.10, so it may be a Xubuntu issue. Hope someone can take a look at this. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1576424/+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 1640741] Re: ubuntu 17.04 gnome-software install button not working
Ubuntu sotware fails with the above problem on my installation "corrado-HP-zesty" - zesty proposed enabled but seems working on a different installation "corrado-HP-zesty2" - zesty proposed NOT enabled running on the same hardware, different partition. Output from inxi attached. ** Attachment added: "inxi output for both installations" https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1640741/+attachment/4775939/+files/inxi-zesty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1640741 Title: ubuntu 17.04 gnome-software install button not working Status in gnome-software package in Ubuntu: New Bug description: on ubuntu 17.04 gnome-software install button does nothing. try with different applications: UFRaw, Shutter, Entangle ... ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-software 3.22.2+git20161108.0.a58dfc7-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Thu Nov 10 11:08:48 2016 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2016-11-06 (3 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161106) SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1640741/+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 1633162] Re: Files application throws an error 'Oops! Something went wrong' when clicked on 'Recents'
The package needs to be made to not to preserve the /usr/lib/systemd/user/gvfs-daemon.service file? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1633162 Title: Files application throws an error 'Oops! Something went wrong' when clicked on 'Recents' Status in Nautilus: Incomplete Status in nautilus package in Ubuntu: Confirmed Bug description: The application crashes every time I click on 'Recent' with this message in a pop-up window: "Unhandled error message: Message recipient disconnected from message bus without replying." ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: nautilus 1:3.20.3-1ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Thu Oct 13 22:34:57 2016 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.preferences' b'enable-interactive-search' b'false' b'org.gnome.nautilus.window-state' b'geometry' b"'890x550+476+24'" InstallationDate: Installed on 2016-10-13 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1633162/+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 1638767] Re: Switching session to Unity8 on login screen is not obviously discoverable
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity-greeter (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1638767 Title: Switching session to Unity8 on login screen is not obviously discoverable Status in Canonical System Image: New Status in Ubuntu UX: New Status in unity-greeter package in Ubuntu: Confirmed Bug description: Switching session to Unity8 on login screen is not obviously discoverable. This might explain why so many users are still asking "where's Unity8?" even though they're using yakkety. It's just not obvious on the login screen that the Ubuntu icon is also a button where you change desktop environments. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1638767/+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 1581294] Re: ext4 + luks on 1TB crashes
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-disk-utility (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1581294 Title: ext4 + luks on 1TB crashes Status in gnome-disk-utility package in Ubuntu: Confirmed Bug description: Drive formated as gpt. Using the whole space, on ext4 + luks options, the program gives segmentation fault (core violation). I can format the drive using gparted perfectly. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-disk-utility 3.18.3.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Thu May 12 20:52:33 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-05-12 (0 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) SourcePackage: gnome-disk-utility UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1581294/+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 1570653] Re: LG 31MU97-B Black 31" 4K Monitor not detected properly
following the instructions on http://penguindreams.org/blog/running-a-lg31mu97-on-linux-at-4096x2160 -at-60hz/ the monitor is now able to display at 4096x2160_60. my current kernel is - Linux music 4.4.0-45-lowlatency #66-Ubuntu SMP PREEMPT Wed Oct 19 14:57:51 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux and yes, I had to go through the tutorial to make it 4096x2160_60 as it was not detected after booting. what is the next appropriate step to have persist? please let me know what to further test. thanks -- 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/1570653 Title: LG 31MU97-B Black 31" 4K Monitor not detected properly Status in xorg package in Ubuntu: Incomplete Bug description: 4K monitor is not properly detected. using xfce desktop "Display" utility, my monitor is detected as "Goldstar Company Ltd 27" with a resolution of 3840x2160 and 60.0Hz The actual monitor is an LG 31MU97-B Black 31" with a resolution of 4096x2160. I'm pretty sure the Monitor's resolution was properly detected in 15.10 (4096x2160). It was called "Goldstar Company Ltd" but I do not recall which size was detected. (27" or 31") I remember seeing a 4K youtube video in 15.10 and noting the black bands on each side of the display, due to the difference between 3840 and 4096. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: 2016-04-14 20:11:08,467 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory) (8)) DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Curacao PRO [Radeon R7 370 / R9 270/370 OEM] [1002:6811] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Curacao PRO [Radeon R7 370 / R9 270/370 OEM] [174b:e271] InstallationDate: Installed on 2015-11-24 (204 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) LightdmGreeterLog: upstart: indicator-application main process (2191) killed by TERM signal Invalid MIT-MAGIC-COOKIE-1 key LightdmGreeterLogOld: ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug 7 2015, 01:24:18) ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf upstart: indicator-application main process (1802) killed by TERM signal MachineType: To be filled by O.E.M. To be filled by O.E.M. Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-lowlatency root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-22.40-lowlatency 4.4.8 Tags: xenial ubuntu Uname: Linux 4.4.0-22-lowlatency x86_64 UpgradeStatus: Upgraded to xenial on 2016-04-15 (62 days ago) UserGroups: adm audio cdrom dip libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH 990FX R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2501:bd04/08/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FXR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: http
[Desktop-packages] [Bug 1641055] Re: startx, lightdm fail to start
If I *remove* xserver-xorg-video-intel, lightdm is able to show me the login screen. However, there is corruption on the screen and trying to log into a Unity or Gnome session just shows a blank screen and then puts me back into the login screen after 1 second. -- 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/1641055 Title: startx, lightdm fail to start Status in xorg-server package in Ubuntu: New Bug description: After updating from 16.04 to 16.10, lightdm doesn't start. Adding 'nomodeset' for booting allows it to start, but apparently lacks all acceleration. Trying different kernels doesn't help, including the one from 16.04. Sorry for brevity, I'm writing this on my phone... ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xserver-xorg-core 2:1.18.4-1ubuntu6 Uname: Linux 4.8.7-040807-lowlatency x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 BootLog: /dev/sda1: clean, 2557730/15417344 files, 54003285/61639424 blocks CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Fri Nov 11 09:07:35 2016 DistUpgraded: 2016-11-10 20:42:28,744 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory) (8)) DistroCodename: yakkety DistroVariant: ubuntu DkmsStatus: acpi_call, 1.0, 3.2.0-21-generic, x86_64: built tp_smapi, 0.42, 4.4.0-47-generic, x86_64: installed tp_smapi, 0.42, 4.8.0-27-generic, x86_64: installed tp_smapi, 0.42, 4.8.7-040807-generic, x86_64: installed tp_smapi, 0.42, 4.8.7-040807-lowlatency, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:5036] InstallationDate: Installed on 2011-03-11 (2071 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) MachineType: LENOVO 20BWS02D00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.7-040807-lowlatency root=UUID=45e540a8-fe2a-49e7-9c27-99725af4a6bd ro quiet splash i915.i915_enable_rc6=1 vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: Upgraded to yakkety on 2016-11-10 (0 days ago) dmi.bios.date: 12/09/2014 dmi.bios.vendor: LENOVO dmi.bios.version: JBET39WW (1.04 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BWS02D00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET39WW(1.04):bd12/09/2014:svnLENOVO:pn20BWS02D00:pvrThinkPadT450s:rvnLENOVO:rn20BWS02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BWS02D00 dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.71+git1611081830.670f1e~gd~y version.libgl1-mesa-dri: libgl1-mesa-dri 13.1~git1611101930.f500c3~gd~y version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 13.1~git1611101930.f500c3~gd~y version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Fri Nov 11 09:06:56 2016 xserver.configfile: default xserver.devices: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-1ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1641055/+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 1641055] Re: startx, lightdm fail to start
After deleting the .Xauthority file, I can now successfully log into a Unity session. The problem seems to be gone (rebooting worked fine after this). Maybe somebody can figure out how I got into this situation, but otherwise the bug can be closed as far as I'm concerned. -- 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/1641055 Title: startx, lightdm fail to start Status in xorg-server package in Ubuntu: New Bug description: After updating from 16.04 to 16.10, lightdm doesn't start. Adding 'nomodeset' for booting allows it to start, but apparently lacks all acceleration. Trying different kernels doesn't help, including the one from 16.04. Sorry for brevity, I'm writing this on my phone... ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xserver-xorg-core 2:1.18.4-1ubuntu6 Uname: Linux 4.8.7-040807-lowlatency x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 BootLog: /dev/sda1: clean, 2557730/15417344 files, 54003285/61639424 blocks CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Fri Nov 11 09:07:35 2016 DistUpgraded: 2016-11-10 20:42:28,744 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory) (8)) DistroCodename: yakkety DistroVariant: ubuntu DkmsStatus: acpi_call, 1.0, 3.2.0-21-generic, x86_64: built tp_smapi, 0.42, 4.4.0-47-generic, x86_64: installed tp_smapi, 0.42, 4.8.0-27-generic, x86_64: installed tp_smapi, 0.42, 4.8.7-040807-generic, x86_64: installed tp_smapi, 0.42, 4.8.7-040807-lowlatency, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:5036] InstallationDate: Installed on 2011-03-11 (2071 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) MachineType: LENOVO 20BWS02D00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.7-040807-lowlatency root=UUID=45e540a8-fe2a-49e7-9c27-99725af4a6bd ro quiet splash i915.i915_enable_rc6=1 vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: Upgraded to yakkety on 2016-11-10 (0 days ago) dmi.bios.date: 12/09/2014 dmi.bios.vendor: LENOVO dmi.bios.version: JBET39WW (1.04 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BWS02D00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET39WW(1.04):bd12/09/2014:svnLENOVO:pn20BWS02D00:pvrThinkPadT450s:rvnLENOVO:rn20BWS02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BWS02D00 dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.71+git1611081830.670f1e~gd~y version.libgl1-mesa-dri: libgl1-mesa-dri 13.1~git1611101930.f500c3~gd~y version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 13.1~git1611101930.f500c3~gd~y version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Fri Nov 11 09:06:56 2016 xserver.configfile: default xserver.devices: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-1ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1641055/+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 1637758] Re: lightdm greeter session not properly shut down at login
It is indeed happening again for me. I think that it didn't happen with systemd 232-2git1 and it does again with 232-3 - I've tried downgrading and upgrading a few times and it was reliably correlated with that. ** Attachment added: "1637758.png" https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1637758/+attachment/4775957/+files/1637758.png ** Changed in: lightdm (Ubuntu) Status: Invalid => Triaged ** Changed in: lightdm (Ubuntu) Importance: Undecided => High ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1637758 Title: lightdm greeter session not properly shut down at login Status in lightdm package in Ubuntu: Triaged Status in systemd package in Ubuntu: New Bug description: I am using lightdm with 2 seats. After 2409 revision randomly one of two seats does not work correctly. xsettings plugin from unity-settings-daemon or gnome-settings-deamon fails to start because there is already _XSESSION_S* manager running. After revision 2409 in system monitor I see that there is still running unity-settings-daemon started by lightdm. Reverting this revision fixes my problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1637758/+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 1628014] Re: WebExtension fails to install only on ubuntu packaged firefox
I've been hitting exactly the same problem on Debian 8 running Firefox 49.0-5~bpo80+1 from https://mozilla.debian.net/. The issue seems to be solved in Firefox 50.0~b11-1~bpo80+1. -- 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/1628014 Title: WebExtension fails to install only on ubuntu packaged firefox Status in firefox package in Ubuntu: Confirmed Bug description: Hi, I have recently developed a WebExtension ( https://addons.mozilla.org /en-US/firefox/addon/surligneur/ ) but the installation from AMO freezes on a **ubuntu packaged firefox**. The download starts but the process freezes on the "Downloading and verifying addon" step (even on a clean profile and/or a clean install). In the browser console I get the following error : A promise chain failed to handle a rejection. Did you forget to '.catch', or did you forget to 'return'? See https://developer.mozilla.org/Mozilla/JavaScript_code_modules/Promise.jsm/Promise Date: Tue Sep 27 2016 11:05:24 GMT+0200 (CEST) Full Message: TypeError: is not iterable Full Stack: AddonInstall.prototype.onStopRequest/<@resource://gre/modules/addons/XPIProvider.jsm:5974:1 Handler.prototype.process@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:940:21 this.PromiseWalker.walkerLoop@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:816:7 this.PromiseWalker.scheduleWalkerLoop/<@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:750:11 Please note that : - I'm using firefox 49 on ubuntu 16.04.1 - Installing the same extension on a Windows system or a Ubuntu system with a firefox directly downloaded from https://www.mozilla.org/en-US/firefox/all/#en-US works correctly. - Load the addon through the about:debugging page works correctly too. Best, Marius ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: firefox 49.0+build4-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marius 2137 F pulseaudio /dev/snd/controlC1: marius 2137 F pulseaudio BuildID: 20160920074044 Channel: Unavailable CurrentDesktop: Unity Date: Tue Sep 27 11:55:56 2016 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePlugins: Gnome Shell Integration - /usr/lib/mozilla/plugins/libgnome-shell-browser-plugin.so (gnome-shell) Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing EcryptfsInUse: Yes ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-03-30 (180 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) IpRoute: default via 192.168.1.1 dev wlp4s0 proto static metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.1.0/24 dev wlp4s0 proto kernel scope link src 192.168.1.6 metric 600 MostRecentCrashID: bp-63a6343e-7c06-4bcb-8343-af7572160218 Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1Plugins: Gnome Shell Integration - /usr/lib/mozilla/plugins/libgnome-shell-browser-plugin.so (gnome-shell) Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so Profile1PrefSources: prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profiles: Profile0 (Default) - LastVersion=49.0/20160920074044 (In use) Profile1 - LastVersion=49.0/20160920074044 RelatedPackageVersions: gnome-shell 3.18.5-0ubuntu0.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0Y536R dmi.board.vendor: Dell Inc. dmi.board.version: A14 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A14 dmi.modalias: dmi:bvnDellInc.:bvrA14:bd03/29/2010:svnDellInc.:pnStudioXPS1640:pvrA143:rvnDellInc.:rn0Y536R:rvrA14:cvnDellInc.:ct8:cvrA14: dmi.product.name: Studio XPS 1640 dmi.product.version: A143 dmi.s
[Desktop-packages] [Bug 1641154] [NEW] Regression: 16.10 after resuming from suspend internet connection is not restablished
Public bug reported: Distro: Lubuntu Device: Bus 001 Device 002: ID 0bda:8187 Realtek Semiconductor Corp. RTL8187 Wireless Adapter This is my dmesg output when reconnecting wlan0: authenticate with 30:b5:c2:ad:b1:58 [ 149.927996] wlan0: send auth to 30:b5:c2:ad:b1:58 (try 1/3) [ 149.929721] wlan0: authenticated [ 149.932293] wlan0: associate with 30:b5:c2:ad:b1:58 (try 1/3) [ 149.976858] wlan0: RX AssocResp from 30:b5:c2:ad:b1:58 (capab=0x431 status=0 aid=5) [ 149.978961] wlan0: associated [ 149.979027] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 150.042048] [ cut here ] [ 150.042115] WARNING: CPU: 0 PID: 880 at /build/linux-0gM0c3/linux-4.8.0/drivers/gpu/drm/i915/intel_display.c:1244 assert_cursor.constprop.127+0xe1/0xf0 [i915] [ 150.042116] cursor on pipe A assertion failure (expected off, current on) [ 150.042117] Modules linked in: ccm arc4 snd_hda_codec_si3054 snd_hda_codec_idt snd_hda_codec_generic snd_hda_intel rtl8187 snd_hda_codec mac80211 snd_hda_core snd_hwdep snd_pcm bluetooth zram snd_seq_midi snd_seq_midi_event snd_rawmidi cfg80211 coretemp pcmcia snd_seq joydev input_leds serio_raw snd_seq_device eeprom_93cx6 snd_timer yenta_socket lpc_ich snd tifm_7xx1 pcmcia_rsrc pcmcia_core tifm_core shpchp soundcore mac_hid binfmt_misc parport_pc ppdev lp parport ip_tables x_tables autofs4 i915 i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops firewire_ohci psmouse drm firewire_core ahci pata_acpi libahci sky2 crc_itu_t video fjes [ 150.042171] CPU: 0 PID: 880 Comm: Xorg Tainted: GW 4.8.0-27-generic #29-Ubuntu [ 150.042172] Hardware name: Gateway ML6226B /, BIOS 77.1003/06/2007 [ 150.042175] c6b54967 c8e0f2b6 0286 f168fa00 c63da625 f168fa44 f8b73798 f168fa30 [ 150.042180] c6071b9a f8b75b5c f168fa64 0370 f8b73798 04dc f8afdaa1 04dc [ 150.042185] f566 0041 f559b000 f168fa50 c6071c06 0009 f168fa44 [ 150.042191] Call Trace: [ 150.042199] [] dump_stack+0x58/0x73 [ 150.042203] [] __warn+0xea/0x110 [ 150.042244] [] ? assert_cursor.constprop.127+0xe1/0xf0 [i915] [ 150.042246] [] warn_slowpath_fmt+0x46/0x60 [ 150.042287] [] assert_cursor.constprop.127+0xe1/0xf0 [i915] [ 150.042328] [] intel_disable_pipe+0x48/0x260 [i915] [ 150.042360] [] ? drm_crtc_vblank_get+0x12/0x20 [drm] [ 150.042399] [] ? assert_vblank_disabled+0x13/0x70 [i915] [ 150.042440] [] i9xx_crtc_disable+0x70/0x480 [i915] [ 150.042480] [] ? intel_crtc_disable_planes+0xc3/0xd0 [i915] [ 150.042521] [] intel_atomic_commit_tail+0x148/0x1050 [i915] [ 150.042526] [] ? kmem_cache_alloc_trace+0xc7/0x1a0 [ 150.042547] [] ? drm_atomic_helper_setup_commit+0x2a4/0x300 [drm_kms_helper] [ 150.042558] [] ? drm_atomic_helper_setup_commit+0x2a4/0x300 [drm_kms_helper] [ 150.042569] [] ? drm_atomic_helper_swap_state+0x1b8/0x2d0 [drm_kms_helper] [ 150.042610] [] intel_atomic_commit+0x40e/0x510 [i915] [ 150.042634] [] ? drm_atomic_check_only+0x19b/0x660 [drm] [ 150.042658] [] drm_atomic_commit+0x32/0x60 [drm] [ 150.042699] [] intel_release_load_detect_pipe+0x22/0xa0 [i915] [ 150.042703] [] ? wake_atomic_t_function+0x70/0x70 [ 150.042742] [] ? gen9_write64+0x3e0/0x3e0 [i915] [ 150.042781] [] ? gen9_write64+0x3e0/0x3e0 [i915] [ 150.042825] [] intel_tv_detect+0x32d/0x660 [i915] [ 150.042848] [] ? crtc_commit_free+0x10/0x20 [drm] [ 150.042860] [] drm_helper_probe_single_connector_modes+0x258/0x530 [drm_kms_helper] [ 150.042881] [] ? get_properties+0xab/0xf0 [drm] [ 150.042902] [] ? _object_find+0x60/0xe0 [drm] [ 150.042924] [] drm_mode_getconnector+0x285/0x2f0 [drm] [ 150.042929] [] ? __ww_mutex_lock+0x17/0xa0 [ 150.042932] [] ? __check_heap_object+0x5f/0xa0 [ 150.042955] [] ? drm_mode_getcrtc+0x140/0x140 [drm] [ 150.042972] [] drm_ioctl+0x1b3/0x4e0 [drm] [ 150.042976] [] ? fcntl_dirnotify+0x300/0x300 [ 150.042978] [] ? inotify_merge+0x44/0x50 [ 150.042980] [] ? inotify_free_event+0xd/0x10 [ 150.043002] [] ? drm_mode_getcrtc+0x140/0x140 [drm] [ 150.043021] [] ? drm_getunique+0x60/0x60 [drm] [ 150.043024] [] do_vfs_ioctl+0x91/0x740 [ 150.043027] [] ? __check_object_size+0xa9/0x12c [ 150.043030] [] SyS_ioctl+0x60/0x70 [ 150.043033] [] do_fast_syscall_32+0x8d/0x140 [ 150.043035] [] sysenter_past_esp+0x47/0x75 [ 150.043037] ---[ end trace d6d71add1bd0c69f ]--- After a restart via sudo systemctl restart network-manager.service [ 208.041514] wlan0: deauthenticating from 30:b5:c2:ad:b1:58 by local choice (Reason: 3=DEAUTH_LEAVING) [ 209.311005] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 209.333881] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 209.681951] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 214.016683] wlan0: authenticate with 30:b5:c2:ad:b1:58 [ 214.305796] wlan0: send auth to 30:b5:c2:ad:b1:58 (try 1/3) [ 214.311157] wlan0: authenti
[Desktop-packages] [Bug 1637758] Re: lightdm greeter session not properly shut down at login
That is, if I remember correctly 231-10 bad 232-2git1 good 232-3 bad 232-3 with the above patch reverted good -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1637758 Title: lightdm greeter session not properly shut down at login Status in lightdm package in Ubuntu: Triaged Status in systemd package in Ubuntu: New Bug description: I am using lightdm with 2 seats. After 2409 revision randomly one of two seats does not work correctly. xsettings plugin from unity-settings-daemon or gnome-settings-deamon fails to start because there is already _XSESSION_S* manager running. After revision 2409 in system monitor I see that there is still running unity-settings-daemon started by lightdm. Reverting this revision fixes my problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1637758/+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 1637758] Re: lightdm greeter session not properly shut down at login
Ok, so I built a systemd without debian/patches/debian/core-don-t-use- the-unified-hierarchy-for-the-systemd-cgro.patch and it seems to work. Not sure what that says ... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1637758 Title: lightdm greeter session not properly shut down at login Status in lightdm package in Ubuntu: Triaged Status in systemd package in Ubuntu: New Bug description: I am using lightdm with 2 seats. After 2409 revision randomly one of two seats does not work correctly. xsettings plugin from unity-settings-daemon or gnome-settings-deamon fails to start because there is already _XSESSION_S* manager running. After revision 2409 in system monitor I see that there is still running unity-settings-daemon started by lightdm. Reverting this revision fixes my problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1637758/+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 1589401] Re: cannot view wifi networks after re-enabling wifi
mm i am experiencing problems also since upgrading to 16.10. I m oppening a new bug Bug #1641154. I have the feeling that the device does connect to the network but the kernel crashes when establishing the connection this is the dmesg output when coming back from suspend wlan0: authenticate with 30:b5:c2:ad:b1:58 [ 149.927996] wlan0: send auth to 30:b5:c2:ad:b1:58 (try 1/3) [ 149.929721] wlan0: authenticated [ 149.932293] wlan0: associate with 30:b5:c2:ad:b1:58 (try 1/3) [ 149.976858] wlan0: RX AssocResp from 30:b5:c2:ad:b1:58 (capab=0x431 status=0 aid=5) [ 149.978961] wlan0: associated [ 149.979027] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 150.042048] [ cut here ] [ 150.042115] WARNING: CPU: 0 PID: 880 at /build/linux-0gM0c3/linux-4.8.0/drivers/gpu/drm/i915/intel_display.c:1244 assert_cursor.constprop.127+0xe1/0xf0 [i915] [ 150.042116] cursor on pipe A assertion failure (expected off, current on) [ 150.042117] Modules linked in: ccm arc4 snd_hda_codec_si3054 snd_hda_codec_idt snd_hda_codec_generic snd_hda_intel rtl8187 snd_hda_codec mac80211 snd_hda_core snd_hwdep snd_pcm bluetooth zram snd_seq_midi snd_seq_midi_event snd_rawmidi cfg80211 coretemp pcmcia snd_seq joydev input_leds serio_raw snd_seq_device eeprom_93cx6 snd_timer yenta_socket lpc_ich snd tifm_7xx1 pcmcia_rsrc pcmcia_core tifm_core shpchp soundcore mac_hid binfmt_misc parport_pc ppdev lp parport ip_tables x_tables autofs4 i915 i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops firewire_ohci psmouse drm firewire_core ahci pata_acpi libahci sky2 crc_itu_t video fjes [ 150.042171] CPU: 0 PID: 880 Comm: Xorg Tainted: GW 4.8.0-27-generic #29-Ubuntu [ 150.042172] Hardware name: Gateway ML6226B /, BIOS 77.1003/06/2007 [ 150.042175] c6b54967 c8e0f2b6 0286 f168fa00 c63da625 f168fa44 f8b73798 f168fa30 [ 150.042180] c6071b9a f8b75b5c f168fa64 0370 f8b73798 04dc f8afdaa1 04dc [ 150.042185] f566 0041 f559b000 f168fa50 c6071c06 0009 f168fa44 [ 150.042191] Call Trace: [ 150.042199] [] dump_stack+0x58/0x73 [ 150.042203] [] __warn+0xea/0x110 [ 150.042244] [] ? assert_cursor.constprop.127+0xe1/0xf0 [i915] [ 150.042246] [] warn_slowpath_fmt+0x46/0x60 [ 150.042287] [] assert_cursor.constprop.127+0xe1/0xf0 [i915] [ 150.042328] [] intel_disable_pipe+0x48/0x260 [i915] [ 150.042360] [] ? drm_crtc_vblank_get+0x12/0x20 [drm] [ 150.042399] [] ? assert_vblank_disabled+0x13/0x70 [i915] [ 150.042440] [] i9xx_crtc_disable+0x70/0x480 [i915] [ 150.042480] [] ? intel_crtc_disable_planes+0xc3/0xd0 [i915] [ 150.042521] [] intel_atomic_commit_tail+0x148/0x1050 [i915] [ 150.042526] [] ? kmem_cache_alloc_trace+0xc7/0x1a0 [ 150.042547] [] ? drm_atomic_helper_setup_commit+0x2a4/0x300 [drm_kms_helper] [ 150.042558] [] ? drm_atomic_helper_setup_commit+0x2a4/0x300 [drm_kms_helper] [ 150.042569] [] ? drm_atomic_helper_swap_state+0x1b8/0x2d0 [drm_kms_helper] [ 150.042610] [] intel_atomic_commit+0x40e/0x510 [i915] [ 150.042634] [] ? drm_atomic_check_only+0x19b/0x660 [drm] [ 150.042658] [] drm_atomic_commit+0x32/0x60 [drm] [ 150.042699] [] intel_release_load_detect_pipe+0x22/0xa0 [i915] [ 150.042703] [] ? wake_atomic_t_function+0x70/0x70 [ 150.042742] [] ? gen9_write64+0x3e0/0x3e0 [i915] [ 150.042781] [] ? gen9_write64+0x3e0/0x3e0 [i915] [ 150.042825] [] intel_tv_detect+0x32d/0x660 [i915] [ 150.042848] [] ? crtc_commit_free+0x10/0x20 [drm] [ 150.042860] [] drm_helper_probe_single_connector_modes+0x258/0x530 [drm_kms_helper] [ 150.042881] [] ? get_properties+0xab/0xf0 [drm] [ 150.042902] [] ? _object_find+0x60/0xe0 [drm] [ 150.042924] [] drm_mode_getconnector+0x285/0x2f0 [drm] [ 150.042929] [] ? __ww_mutex_lock+0x17/0xa0 [ 150.042932] [] ? __check_heap_object+0x5f/0xa0 [ 150.042955] [] ? drm_mode_getcrtc+0x140/0x140 [drm] [ 150.042972] [] drm_ioctl+0x1b3/0x4e0 [drm] [ 150.042976] [] ? fcntl_dirnotify+0x300/0x300 [ 150.042978] [] ? inotify_merge+0x44/0x50 [ 150.042980] [] ? inotify_free_event+0xd/0x10 [ 150.043002] [] ? drm_mode_getcrtc+0x140/0x140 [drm] [ 150.043021] [] ? drm_getunique+0x60/0x60 [drm] [ 150.043024] [] do_vfs_ioctl+0x91/0x740 [ 150.043027] [] ? __check_object_size+0xa9/0x12c [ 150.043030] [] SyS_ioctl+0x60/0x70 [ 150.043033] [] do_fast_syscall_32+0x8d/0x140 [ 150.043035] [] sysenter_past_esp+0x47/0x75 [ 150.043037] ---[ end trace d6d71add1bd0c69f ]--- My device is Bus 001 Device 002: ID 0bda:8187 Realtek Semiconductor Corp. RTL8187 Wireless Adapter -- 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/1589401 Title: cannot view wifi networks after re-enabling wifi Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Incomple
[Desktop-packages] [Bug 1641154] Re: Regression: 16.10 after resuming from suspend internet connection is not restablished
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- 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/1641154 Title: Regression: 16.10 after resuming from suspend internet connection is not restablished Status in network-manager package in Ubuntu: Confirmed Bug description: Distro: Lubuntu Device: Bus 001 Device 002: ID 0bda:8187 Realtek Semiconductor Corp. RTL8187 Wireless Adapter This is my dmesg output when reconnecting wlan0: authenticate with 30:b5:c2:ad:b1:58 [ 149.927996] wlan0: send auth to 30:b5:c2:ad:b1:58 (try 1/3) [ 149.929721] wlan0: authenticated [ 149.932293] wlan0: associate with 30:b5:c2:ad:b1:58 (try 1/3) [ 149.976858] wlan0: RX AssocResp from 30:b5:c2:ad:b1:58 (capab=0x431 status=0 aid=5) [ 149.978961] wlan0: associated [ 149.979027] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 150.042048] [ cut here ] [ 150.042115] WARNING: CPU: 0 PID: 880 at /build/linux-0gM0c3/linux-4.8.0/drivers/gpu/drm/i915/intel_display.c:1244 assert_cursor.constprop.127+0xe1/0xf0 [i915] [ 150.042116] cursor on pipe A assertion failure (expected off, current on) [ 150.042117] Modules linked in: ccm arc4 snd_hda_codec_si3054 snd_hda_codec_idt snd_hda_codec_generic snd_hda_intel rtl8187 snd_hda_codec mac80211 snd_hda_core snd_hwdep snd_pcm bluetooth zram snd_seq_midi snd_seq_midi_event snd_rawmidi cfg80211 coretemp pcmcia snd_seq joydev input_leds serio_raw snd_seq_device eeprom_93cx6 snd_timer yenta_socket lpc_ich snd tifm_7xx1 pcmcia_rsrc pcmcia_core tifm_core shpchp soundcore mac_hid binfmt_misc parport_pc ppdev lp parport ip_tables x_tables autofs4 i915 i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops firewire_ohci psmouse drm firewire_core ahci pata_acpi libahci sky2 crc_itu_t video fjes [ 150.042171] CPU: 0 PID: 880 Comm: Xorg Tainted: GW 4.8.0-27-generic #29-Ubuntu [ 150.042172] Hardware name: Gateway ML6226B /, BIOS 77.1003/06/2007 [ 150.042175] c6b54967 c8e0f2b6 0286 f168fa00 c63da625 f168fa44 f8b73798 f168fa30 [ 150.042180] c6071b9a f8b75b5c f168fa64 0370 f8b73798 04dc f8afdaa1 04dc [ 150.042185] f566 0041 f559b000 f168fa50 c6071c06 0009 f168fa44 [ 150.042191] Call Trace: [ 150.042199] [] dump_stack+0x58/0x73 [ 150.042203] [] __warn+0xea/0x110 [ 150.042244] [] ? assert_cursor.constprop.127+0xe1/0xf0 [i915] [ 150.042246] [] warn_slowpath_fmt+0x46/0x60 [ 150.042287] [] assert_cursor.constprop.127+0xe1/0xf0 [i915] [ 150.042328] [] intel_disable_pipe+0x48/0x260 [i915] [ 150.042360] [] ? drm_crtc_vblank_get+0x12/0x20 [drm] [ 150.042399] [] ? assert_vblank_disabled+0x13/0x70 [i915] [ 150.042440] [] i9xx_crtc_disable+0x70/0x480 [i915] [ 150.042480] [] ? intel_crtc_disable_planes+0xc3/0xd0 [i915] [ 150.042521] [] intel_atomic_commit_tail+0x148/0x1050 [i915] [ 150.042526] [] ? kmem_cache_alloc_trace+0xc7/0x1a0 [ 150.042547] [] ? drm_atomic_helper_setup_commit+0x2a4/0x300 [drm_kms_helper] [ 150.042558] [] ? drm_atomic_helper_setup_commit+0x2a4/0x300 [drm_kms_helper] [ 150.042569] [] ? drm_atomic_helper_swap_state+0x1b8/0x2d0 [drm_kms_helper] [ 150.042610] [] intel_atomic_commit+0x40e/0x510 [i915] [ 150.042634] [] ? drm_atomic_check_only+0x19b/0x660 [drm] [ 150.042658] [] drm_atomic_commit+0x32/0x60 [drm] [ 150.042699] [] intel_release_load_detect_pipe+0x22/0xa0 [i915] [ 150.042703] [] ? wake_atomic_t_function+0x70/0x70 [ 150.042742] [] ? gen9_write64+0x3e0/0x3e0 [i915] [ 150.042781] [] ? gen9_write64+0x3e0/0x3e0 [i915] [ 150.042825] [] intel_tv_detect+0x32d/0x660 [i915] [ 150.042848] [] ? crtc_commit_free+0x10/0x20 [drm] [ 150.042860] [] drm_helper_probe_single_connector_modes+0x258/0x530 [drm_kms_helper] [ 150.042881] [] ? get_properties+0xab/0xf0 [drm] [ 150.042902] [] ? _object_find+0x60/0xe0 [drm] [ 150.042924] [] drm_mode_getconnector+0x285/0x2f0 [drm] [ 150.042929] [] ? __ww_mutex_lock+0x17/0xa0 [ 150.042932] [] ? __check_heap_object+0x5f/0xa0 [ 150.042955] [] ? drm_mode_getcrtc+0x140/0x140 [drm] [ 150.042972] [] drm_ioctl+0x1b3/0x4e0 [drm] [ 150.042976] [] ? fcntl_dirnotify+0x300/0x300 [ 150.042978] [] ? inotify_merge+0x44/0x50 [ 150.042980] [] ? inotify_free_event+0xd/0x10 [ 150.043002] [] ? drm_mode_getcrtc+0x140/0x140 [drm] [ 150.043021] [] ? drm_getunique+0x60/0x60 [drm] [ 150.043024] [] do_vfs_ioctl+0x91/0x740 [ 150.043027] [] ? __check_object_size+0xa9/0x12c [ 150.043030] [] SyS_ioctl+0x60/0x70 [ 150.043033] [] do_fast_syscall_32+0x8d/0x140 [ 150.043035] [] sysenter_pa
[Desktop-packages] [Bug 1641176] [NEW] SSH connection never completes, hogs CPU
Public bug reported: Since upgrading to yakkety I can't use remmina, it connects over SSH and just sits there with a black screen + a blinking caret. It also hogs a core of my cpu. The only output from the remmina process: LANG=C remmina Remmina plugin GKEYRING (type=Secret) registered. Remmina plugin VNC (type=Protocol) registered. Remmina plugin VNCI (type=Protocol) registered. Remmina plugin telepathy (type=Entry) registered. Remmina plugin XDMCP (type=Protocol) registered. NX: detected keyboard type pc105/pl Remmina plugin NX (type=Protocol) registered. Remmina plugin RDP (type=Protocol) registered. Remmina plugin RDPF (type=File) registered. Remmina plugin RDPS (type=Preference) registered. Remmina plugin SFTP (type=Protocol) registered. Remmina plugin SSH (type=Protocol) registered. Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. (remmina:20860): Gtk-WARNING **: Allocating size to GtkScrollbar 0x55eaaa8f45b0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? The other side connects correctly [see attached sshd.log]. Perf shows polling to be responsible for the CPU hog: 11,94% remmina [kernel.kallsyms] [k] do_sys_poll 5,57% remmina libssh.so.4.4.1 [.] ssh_poll_ctx_dopoll 4,84% remmina [kernel.kallsyms] [k] tcp_poll 3,99% remmina [vdso] [.] __vdso_clock_gettime 3,76% remmina [kernel.kallsyms] [k] sys_poll 3,71% remmina [kernel.kallsyms] [k] n_tty_poll 3,47% remmina [kernel.kallsyms] [k] _raw_spin_unlock_irqrestore 3,45% remmina [kernel.kallsyms] [k] __fget 3,28% remmina [kernel.kallsyms] [k] _raw_spin_lock_irqsave 3,27% remmina [kernel.kallsyms] [k] entry_SYSCALL_64_after_swapgs 3,18% remmina libssh.so.4.4.1 [.] ssh_select 2,78% remmina [kernel.kallsyms] [k] __pollwait 2,05% remmina libssh.so.4.4.1 [.] ssh_timeout_update And also attached gdb.txt, there's a threaded stacktrace of the remmina process interrupted while in this state. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: remmina 1.1.2-3ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Fri Nov 11 18:10:44 2016 InstallationDate: Installed on 2016-05-06 (188 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: remmina UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: remmina (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages yakkety ** Attachment added: "remmina.png" https://bugs.launchpad.net/bugs/1641176/+attachment/4776007/+files/remmina.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to remmina in Ubuntu. https://bugs.launchpad.net/bugs/1641176 Title: SSH connection never completes, hogs CPU Status in remmina package in Ubuntu: New Bug description: Since upgrading to yakkety I can't use remmina, it connects over SSH and just sits there with a black screen + a blinking caret. It also hogs a core of my cpu. The only output from the remmina process: LANG=C remmina Remmina plugin GKEYRING (type=Secret) registered. Remmina plugin VNC (type=Protocol) registered. Remmina plugin VNCI (type=Protocol) registered. Remmina plugin telepathy (type=Entry) registered. Remmina plugin XDMCP (type=Protocol) registered. NX: detected keyboard type pc105/pl Remmina plugin NX (type=Protocol) registered. Remmina plugin RDP (type=Protocol) registered. Remmina plugin RDPF (type=File) registered. Remmina plugin RDPS (type=Preference) registered. Remmina plugin SFTP (type=Protocol) registered. Remmina plugin SSH (type=Protocol) registered. Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. (remmina:20860): Gtk-WARNING **: Allocating size to GtkScrollbar 0x55eaaa8f45b0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? The other side connects correctly [see attached sshd.log]. Perf shows polling to be responsible for the CPU hog: 11,94% remmina [kernel.kallsyms] [k] do_sys_poll 5,57% remmina libssh.so.4.4.1 [.] ssh_poll_ctx_dopoll 4,84% remmina [kernel.kallsyms] [k] tcp_poll 3,99% remmina [vdso] [.] __vdso_clock_gettime 3,76% remmina [kernel.kallsyms] [k] sys_poll 3,71% remmina [kernel.kallsyms] [k] n_tty_poll 3,47% remmina [kernel.kallsyms] [k] _raw_spin_unlock_irqrestore 3,45% remmina [kernel.kal
[Desktop-packages] [Bug 1641176] Re: SSH connection never completes, hogs CPU
Please let me know if I can do anything else to help debug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to remmina in Ubuntu. https://bugs.launchpad.net/bugs/1641176 Title: SSH connection never completes, hogs CPU Status in remmina package in Ubuntu: New Bug description: Since upgrading to yakkety I can't use remmina, it connects over SSH and just sits there with a black screen + a blinking caret. It also hogs a core of my cpu. The only output from the remmina process: LANG=C remmina Remmina plugin GKEYRING (type=Secret) registered. Remmina plugin VNC (type=Protocol) registered. Remmina plugin VNCI (type=Protocol) registered. Remmina plugin telepathy (type=Entry) registered. Remmina plugin XDMCP (type=Protocol) registered. NX: detected keyboard type pc105/pl Remmina plugin NX (type=Protocol) registered. Remmina plugin RDP (type=Protocol) registered. Remmina plugin RDPF (type=File) registered. Remmina plugin RDPS (type=Preference) registered. Remmina plugin SFTP (type=Protocol) registered. Remmina plugin SSH (type=Protocol) registered. Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. (remmina:20860): Gtk-WARNING **: Allocating size to GtkScrollbar 0x55eaaa8f45b0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? The other side connects correctly [see attached sshd.log]. Perf shows polling to be responsible for the CPU hog: 11,94% remmina [kernel.kallsyms] [k] do_sys_poll 5,57% remmina libssh.so.4.4.1 [.] ssh_poll_ctx_dopoll 4,84% remmina [kernel.kallsyms] [k] tcp_poll 3,99% remmina [vdso] [.] __vdso_clock_gettime 3,76% remmina [kernel.kallsyms] [k] sys_poll 3,71% remmina [kernel.kallsyms] [k] n_tty_poll 3,47% remmina [kernel.kallsyms] [k] _raw_spin_unlock_irqrestore 3,45% remmina [kernel.kallsyms] [k] __fget 3,28% remmina [kernel.kallsyms] [k] _raw_spin_lock_irqsave 3,27% remmina [kernel.kallsyms] [k] entry_SYSCALL_64_after_swapgs 3,18% remmina libssh.so.4.4.1 [.] ssh_select 2,78% remmina [kernel.kallsyms] [k] __pollwait 2,05% remmina libssh.so.4.4.1 [.] ssh_timeout_update And also attached gdb.txt, there's a threaded stacktrace of the remmina process interrupted while in this state. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: remmina 1.1.2-3ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Fri Nov 11 18:10:44 2016 InstallationDate: Installed on 2016-05-06 (188 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: remmina UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1641176/+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 1641176] Re: SSH connection never completes, hogs CPU
** Attachment added: "gdb.txt" https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1641176/+attachment/4776012/+files/gdb.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to remmina in Ubuntu. https://bugs.launchpad.net/bugs/1641176 Title: SSH connection never completes, hogs CPU Status in remmina package in Ubuntu: New Bug description: Since upgrading to yakkety I can't use remmina, it connects over SSH and just sits there with a black screen + a blinking caret. It also hogs a core of my cpu. The only output from the remmina process: LANG=C remmina Remmina plugin GKEYRING (type=Secret) registered. Remmina plugin VNC (type=Protocol) registered. Remmina plugin VNCI (type=Protocol) registered. Remmina plugin telepathy (type=Entry) registered. Remmina plugin XDMCP (type=Protocol) registered. NX: detected keyboard type pc105/pl Remmina plugin NX (type=Protocol) registered. Remmina plugin RDP (type=Protocol) registered. Remmina plugin RDPF (type=File) registered. Remmina plugin RDPS (type=Preference) registered. Remmina plugin SFTP (type=Protocol) registered. Remmina plugin SSH (type=Protocol) registered. Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. (remmina:20860): Gtk-WARNING **: Allocating size to GtkScrollbar 0x55eaaa8f45b0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? The other side connects correctly [see attached sshd.log]. Perf shows polling to be responsible for the CPU hog: 11,94% remmina [kernel.kallsyms] [k] do_sys_poll 5,57% remmina libssh.so.4.4.1 [.] ssh_poll_ctx_dopoll 4,84% remmina [kernel.kallsyms] [k] tcp_poll 3,99% remmina [vdso] [.] __vdso_clock_gettime 3,76% remmina [kernel.kallsyms] [k] sys_poll 3,71% remmina [kernel.kallsyms] [k] n_tty_poll 3,47% remmina [kernel.kallsyms] [k] _raw_spin_unlock_irqrestore 3,45% remmina [kernel.kallsyms] [k] __fget 3,28% remmina [kernel.kallsyms] [k] _raw_spin_lock_irqsave 3,27% remmina [kernel.kallsyms] [k] entry_SYSCALL_64_after_swapgs 3,18% remmina libssh.so.4.4.1 [.] ssh_select 2,78% remmina [kernel.kallsyms] [k] __pollwait 2,05% remmina libssh.so.4.4.1 [.] ssh_timeout_update And also attached gdb.txt, there's a threaded stacktrace of the remmina process interrupted while in this state. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: remmina 1.1.2-3ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Fri Nov 11 18:10:44 2016 InstallationDate: Installed on 2016-05-06 (188 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: remmina UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1641176/+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 1641176] Re: SSH connection never completes, hogs CPU
** Attachment added: "sshd.log" https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1641176/+attachment/4776011/+files/sshd.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to remmina in Ubuntu. https://bugs.launchpad.net/bugs/1641176 Title: SSH connection never completes, hogs CPU Status in remmina package in Ubuntu: New Bug description: Since upgrading to yakkety I can't use remmina, it connects over SSH and just sits there with a black screen + a blinking caret. It also hogs a core of my cpu. The only output from the remmina process: LANG=C remmina Remmina plugin GKEYRING (type=Secret) registered. Remmina plugin VNC (type=Protocol) registered. Remmina plugin VNCI (type=Protocol) registered. Remmina plugin telepathy (type=Entry) registered. Remmina plugin XDMCP (type=Protocol) registered. NX: detected keyboard type pc105/pl Remmina plugin NX (type=Protocol) registered. Remmina plugin RDP (type=Protocol) registered. Remmina plugin RDPF (type=File) registered. Remmina plugin RDPS (type=Preference) registered. Remmina plugin SFTP (type=Protocol) registered. Remmina plugin SSH (type=Protocol) registered. Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. (remmina:20860): Gtk-WARNING **: Allocating size to GtkScrollbar 0x55eaaa8f45b0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? The other side connects correctly [see attached sshd.log]. Perf shows polling to be responsible for the CPU hog: 11,94% remmina [kernel.kallsyms] [k] do_sys_poll 5,57% remmina libssh.so.4.4.1 [.] ssh_poll_ctx_dopoll 4,84% remmina [kernel.kallsyms] [k] tcp_poll 3,99% remmina [vdso] [.] __vdso_clock_gettime 3,76% remmina [kernel.kallsyms] [k] sys_poll 3,71% remmina [kernel.kallsyms] [k] n_tty_poll 3,47% remmina [kernel.kallsyms] [k] _raw_spin_unlock_irqrestore 3,45% remmina [kernel.kallsyms] [k] __fget 3,28% remmina [kernel.kallsyms] [k] _raw_spin_lock_irqsave 3,27% remmina [kernel.kallsyms] [k] entry_SYSCALL_64_after_swapgs 3,18% remmina libssh.so.4.4.1 [.] ssh_select 2,78% remmina [kernel.kallsyms] [k] __pollwait 2,05% remmina libssh.so.4.4.1 [.] ssh_timeout_update And also attached gdb.txt, there's a threaded stacktrace of the remmina process interrupted while in this state. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: remmina 1.1.2-3ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Fri Nov 11 18:10:44 2016 InstallationDate: Installed on 2016-05-06 (188 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: remmina UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1641176/+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 1641177] [NEW] package tex-common 6.05 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: As the summary states ... This is a 32-bit 17.04 dev release install. I don't have a desktop, so I can't provide any other info at this time. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: tex-common 6.05 Uname: Linux 4.6.5-040605-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: i386 Date: Wed Nov 9 09:31:58 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2014-01-25 (1020 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20140124) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: tex-common Title: package tex-common 6.05 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: tex-common (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 need-duplicate-check third-party-packages zesty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tex-common in Ubuntu. https://bugs.launchpad.net/bugs/1641177 Title: package tex-common 6.05 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in tex-common package in Ubuntu: New Bug description: As the summary states ... This is a 32-bit 17.04 dev release install. I don't have a desktop, so I can't provide any other info at this time. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: tex-common 6.05 Uname: Linux 4.6.5-040605-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: i386 Date: Wed Nov 9 09:31:58 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2014-01-25 (1020 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20140124) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: tex-common Title: package tex-common 6.05 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1641177/+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 492948] Re: Nautilus not able to handle litteral IPv6 address like smb://::1/sharing/
** Changed in: nautilus Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/492948 Title: Nautilus not able to handle litteral IPv6 address like smb://::1/sharing/ Status in Nautilus: Fix Released Status in nautilus package in Ubuntu: Triaged Bug description: Binary package hint: nautilus It seems Nautilus' SMB does not know how to handle litteral IPv6 address like smb://::1/sharing/ . This results in: Could not find "smb:///sharing". Please check the spelling and try again. The variant smb://[::1]/sharing/ results in: Could not display "smb://[::1]/sharing/". Expected behaviour: just a succesful connection to the share /sharing/ on the localhost via IPv6, by using ::1 or [::1]. This bug is relevant because SMB itself over IPv6 works great and is a solution for SMB access without IPv4 NAT problems, and/but a FQDN is not always available. NB: ::1 is just an example. Addresses like 2001:... don't work either. Important remarks: Nautilus' SMB does *correctly* handle: - litteral IPv4 address like 127.0.0.1 - name resolving to IPv4 address - name resolving to IPv6 address (yes!) - smb://ip6-localhost/sharing/ (yes!) - Bonjour/zereconf names like smb://quirinius.local./sharing/ smbclient does *correctly* handle litteral IPv6 addresses: sander@quirinius:~$ smbclient -N -L ::1 Anonymous login successful Domain=[WORKGROUP] OS=[Unix] Server=[Samba 3.4.0] Sharename Type Comment - --- print$ Disk Printer Drivers IPC$IPC IPC Service (quirinius server (Samba, Ubuntu)) Brother-HL-2030-series Printer Brother HL-2030 series sharing Disk ::1 is an IPv6 address -- no workgroup available sander@quirinius:~$ ProblemType: Bug Architecture: i386 Date: Sat Dec 5 21:28:24 2009 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/bin/nautilus Package: nautilus 1:2.28.1-0ubuntu3 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-15.50-generic SourcePackage: nautilus Uname: Linux 2.6.31-15-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/492948/+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 1545872] Re: Eye of gnome show menus in full screen in gnome session fallback mode
The issue continues in Lubuntu 16.10, eog 3.20.4. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1545872 Title: Eye of gnome show menus in full screen in gnome session fallback mode Status in eog package in Ubuntu: Confirmed Bug description: Ubuntu 15.10 (gnome-session-flashback session) eog 3.16.3-1ubuntu2.1 Eye of Gnome shows menus (picture, edit, view, go, help) in fullscreen mode, that happens only under gnome-session-fallback, in classic Unity desktop behavior is as expected (no menus). Workaround is usage of Eye of MATE as replacement. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1545872/+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 1625678] Re: Contacts remembers window size
** Changed in: hundredpapercuts Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-contacts in Ubuntu. https://bugs.launchpad.net/bugs/1625678 Title: Contacts remembers window size Status in gnome-contacts: Confirmed Status in One Hundred Papercuts: Triaged Status in gnome-contacts package in Ubuntu: Triaged Bug description: HOW TO REPRODUCE: 1. Open Contacts. 2. Maximise or resize its window. 3. Close contacts, and reopen it again. EXPECTED RESULT: The window keeps the last session size. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-contacts 3.18.1-1ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Sep 20 17:05:32 2016 InstallationDate: Installed on 2016-05-02 (140 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gnome-contacts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-contacts/+bug/1625678/+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 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec
Since this affects all audio, and not only a specific output, I think this bug should have a higher importance. ** Changed in: linux (Ubuntu) Importance: Medium => High ** Changed in: alsa-driver (Ubuntu) Importance: Undecided => High -- 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/1563110 Title: No sound on Asus e200ha, intel sst with cx2072x codec Status in ALSA driver: Unknown Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I've recently bought an Asus e200ha. Sound in this laptop doesn't work. The sound card is an intel sst with codec conexant cx2072x aplay -l: aplay: device_list:268: no soundcard found... in the sound setting there is a "Dummy output" --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a InstallationDate: Installed on 2016-03-28 (0 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105 Lsusb: Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:3496 IMC Networks Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E200HA Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 RelatedPackageVersions: linux-restricted-modules-3.19.0-32-generic N/A linux-backports-modules-3.19.0-32-generic N/A linux-firmware 1.127.16 Tags: rosa Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E200HA.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E200HA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: E200HA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1563110/+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 1641215] [NEW] nvidia driver 304 fails to load libGLU, GLX errors
Public bug reported: resulting setup is useless for openGL and SDL rendering is very slow kernels 4.4.0-47 -45 xubuntu 16.04 64bit ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.132 Fri Sep 16 11:02:09 PDT 2016 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Nov 11 16:05:16 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.132, 4.4.0-45-generic, x86_64: installed nvidia-304, 304.132, 4.4.0-47-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G71 [GeForce 7900 GS] [10de:0292] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation G71 [GeForce 7900 GS] [10de:0370] InstallationDate: Installed on 2016-11-05 (6 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic root=UUID=9b509dd9-28f8-42d9-bd9f-c2fa7eb33811 ro vebose SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0605 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: A8R-MVP dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.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.:bvr0605:bd12/09/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnA8R-MVP:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Thu Nov 10 16:07:53 2016 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputAT Translated Set 2 keyboard KEYBOARD, id 8 inputImExPS/2 Logitech Wheel Mouse MOUSE, id 9 xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug 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/1641215 Title: nvidia driver 304 fails to load libGLU, GLX errors Status in xorg package in Ubuntu: New Bug description: resulting setup is useless for openGL and SDL rendering is very slow kernels 4.4.0-47 -45 xubuntu 16.04 64bit ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.132 Fri Sep 16 11:02:09 PDT 2016 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Nov 11 16:05:16 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.132, 4.4.0-45-generic, x86_64: installed nvidia-304, 304.13
[Desktop-packages] [Bug 1211110] Re: network manager openvpn dns push data not updating system DNS addresses
I have this issue on ubuntu 16.04. My current workaround to stop the leak is to add entries such as. ``` cat /etc/NetworkManager/dnsmasq.d/hosts.conf server=/mydomain/dnsip ``` Hopefully dns don't change much. Filename is not important. It's gonna be pickup by the NM and dnsmasq. I don't know what part of the big thing it is no trigging the update... -- 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/120 Title: network manager openvpn dns push data not updating system DNS addresses Status in network-manager package in Ubuntu: Incomplete Status in openvpn package in Ubuntu: Incomplete Bug description: [Triage Notes] This bug can no longer make progress. Please see comment 50 for details and further instructions. [Original Description] When IPv4 Method is set to Automatic VPN, DNS address recieved from OpenVPN server do not update resolv.conf. This can be achieved when using a standard openvpn config file by adding the lines: script-security 2 up /etc/openvpn/update-resolv-conf down /etc/openvpn/update-resolv-conf In Network-manager there seems to be no option to run connection specific scripts and the DNS data from the server is ignored. Ubuntu 13.04 Network-manager 0.9.8.0-0ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/120/+subscriptions -- Mailing list: https://launchpad.net/~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 1635847] Re: Please build libreoffice-systray package (re-enable quickstarter) - sync with Debian LibreOffice packaging
** Description changed: - Please build (re-enable) libreoffice-systray package, Ubuntu users needs faster LibreOffice startup, look at Deb-bug 825642 for example. - Debian LibreOffice packages re-enabled systray building since 5.2.1~rc1, see changelog: + Please build (re-enable) libreoffice-systray package, Ubuntu users needs + faster LibreOffice startup, look at Deb-bug 825642 for example. + + Here is the patch for ENABLE_SYSTRAY in debian/rules and creating additional libreoffice-systray package in debian/control : + https://anonscm.debian.org/git/pkg-openoffice/libreoffice.git/commit/?id=9287282e7501487ab9e2a690a88e1022a26b148e + + Debian LibreOffice packages re-enabled systray building since 5.2.1~rc1, + see changelog: Closes: 825642 833676 Changes: - libreoffice (1:5.2.1~rc1-1) experimental; urgency=medium - . -* new upstream release candidate . -* debian/rules, debian/control.transitionals.in: readd -gtk as transitional - package; depend on -gtk2 (closes: #833676) and -systray -* debian/rules: re-enable systray (closes: #825642) now that we need - NEW anyway and have a -gtk transitional package (which contained this - before it was disabled) -* debian/rules: - - rework MySQL/MariaDB conditionals; allow default-libmysqlclient-dev + libreoffice (1:5.2.1~rc1-1) experimental; urgency=medium + . + * new upstream release candidate . + * debian/rules, debian/control.transitionals.in: readd -gtk as transitional + package; depend on -gtk2 (closes: #833676) and -systray + * debian/rules: re-enable systray (closes: #825642) now that we need + NEW anyway and have a -gtk transitional package (which contained this + before it was disabled) + * debian/rules: + - rework MySQL/MariaDB conditionals; allow default-libmysqlclient-dev Thanks, Mantas Kriaučiūnas ** Tags added: patch patch-accepted-debian -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1635847 Title: Please build libreoffice-systray package (re-enable quickstarter) - sync with Debian LibreOffice packaging Status in libreoffice package in Ubuntu: Confirmed Status in libreoffice package in Debian: Fix Released Bug description: Please build (re-enable) libreoffice-systray package, Ubuntu users needs faster LibreOffice startup, look at Deb-bug 825642 for example. Here is the patch for ENABLE_SYSTRAY in debian/rules and creating additional libreoffice-systray package in debian/control : https://anonscm.debian.org/git/pkg-openoffice/libreoffice.git/commit/?id=9287282e7501487ab9e2a690a88e1022a26b148e Debian LibreOffice packages re-enabled systray building since 5.2.1~rc1, see changelog: Closes: 825642 833676 Changes: libreoffice (1:5.2.1~rc1-1) experimental; urgency=medium . * new upstream release candidate . * debian/rules, debian/control.transitionals.in: readd -gtk as transitional package; depend on -gtk2 (closes: #833676) and -systray * debian/rules: re-enable systray (closes: #825642) now that we need NEW anyway and have a -gtk transitional package (which contained this before it was disabled) * debian/rules: - rework MySQL/MariaDB conditionals; allow default-libmysqlclient-dev Thanks, Mantas Kriaučiūnas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1635847/+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 887821] Re: "Show copy dialog" right click launcher entry doesn't work (on nautilus copy)
ubuntu 16.04 still have this bug. this is fucking joke -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/887821 Title: "Show copy dialog" right click launcher entry doesn't work (on nautilus copy) Status in Unity: Fix Released Status in Unity 5.0 series: Won't Fix Status in nautilus package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Status in nautilus source package in Precise: Fix Released Status in unity source package in Precise: Invalid Bug description: Impact: the nautilus copy dialog don't get properly focussed by unity Test Case: - log into an unity session - copy a not too small file (so you have time to interact with the copy dialog) - minimize the copy dialog - right click on the corresponding unity-launcher's icon, and pick "show copy dialog" -> the dialog should be displayed Regression testing: Check that there is no focus issue with that dialog and the launcher -- While copying a large (8 gig) file across an SMB network, I minimized it. The right click on the Nautilus Unity bar showed a "Show copy dialog" item. Clicking on that item did nothing. The only way to get the dialog back up was to open one of the two minimized Nautilus windows and then minimize the one on top. After that minimize, then the copy dialog was displayed on top of the other Nautilus window. I couldn't find any way to get the copy dialog back on screen without clicking around somewhat aimlessly displaying and minimizing Nautilus windows until it appeared. The "Show copy dialog" right-click menu appeared to have no affect. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: nautilus 1:3.2.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: wl fglrx ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Tue Nov 8 18:12:10 2011 ExecutablePath: /usr/bin/nautilus InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/887821/+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 1641233] [NEW] nvidia-304 (not installed): nvidia-304 kernel module failed to build
Public bug reported:
I had used nvidia-304 successfully in Lubuntu 16.04.
With Lubuntu 16.10, it would not load into the kernel.
I just recently downloaded a fixed 304.132 version, which loaded into the
kernel, and was
usable, but a program (Hugin) which had started up fine under nouveau (but
during the use of which nouveau had screen-crashed, forcing hard-shutdown),
failed to start, with the following terminal output:
"
The program 'hugin' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
(Details: serial 541 error_code 2 request_code 154 minor_code 24)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
"
Since Hugin had worked fine in Lubuntu 16.04 with nvidia-304 - 304.131,
I found a version of that for Xenial Xerus (304.131-0ubuntu3) at
https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304, and tried to
install that.
It failed to install, however...
"Building initial module for 4.8.0-27-generic
Error! Bad return status for module build on kernel: 4.8.0-27-generic (x86_64)
Consult /var/lib/dkms/nvidia-304/304.131/build/make.log for more information."
I will (try to) attach the log file for the install
("/var/lib/dkms/nvidia-304/304.131/build/make.log"), but here are the lines
containing the word "error":
"echo >&2 " ERROR: Kernel configuration is invalid."; \
echo >&2 " include/generated/autoconf.h or include/config/auto.conf are
missing.";\
echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix
it."; \
...
/var/lib/dkms/nvidia-304/304.131/build/nv-mlock.c:52:11: error: too many
arguments to function ‘get_user_pages’
ret = get_user_pages(current, mm, (unsigned long)address,
^~
In file included from /var/lib/dkms/nvidia-304/304.131/build/nv-linux.h:82:0,
from /var/lib/dkms/nvidia-304/304.131/build/nv-mlock.c:15:
./include/linux/mm.h:1315:6: note: declared here
long get_user_pages(unsigned long start, unsigned long nr_pages,
^~
/var/lib/dkms/nvidia-304/304.131/build/nv-mlock.c:65:13: error: implicit
declaration of function ‘page_cache_release’
[-Werror=implicit-function-declaration]
page_cache_release(user_pages[i]);
^~
cc1: some warnings being treated as errors
scripts/Makefile.build:289: recipe for target
'/var/lib/dkms/nvidia-304/304.131/build/nv-mlock.o' failed
make[3]: *** [/var/lib/dkms/nvidia-304/304.131/build/nv-mlock.o] Error 1
Makefile:1489: recipe for target
'_module_/var/lib/dkms/nvidia-304/304.131/build' failed
make[2]: *** [_module_/var/lib/dkms/nvidia-304/304.131/build] Error 2
NVIDIA: left KBUILD.
nvidia.ko failed to build!
Makefile:255: recipe for target 'module' failed
make[1]: *** [module] Error 1
makefile:59: recipe for target 'module' failed
make: *** [module] Error 2
"
I am hoping that there is some simple way to get this older version to
load/work,
as I am running out of options for being able to run Hugin:
1: nouveau screen-crashes in Hugin (which starts up fine) when I try to open
the images from which to make the panorama
2: the fixed nvidia-304.132 loads in the kernal, but Hugin crashes upon
starting up
3: the older nvidia-304.131 fails to install
4: I would consider going back to 16.04 (which is in one of 5 partitions which
I reserve for different Lubuntu versions as they come along), but grub, in
installing 16.10, somehow made booting 16.04 impossible (some sort of Emergency
terminal starts up, and I don't know enough of what's happening to know what to
do... The partition is fine - I can traverse the directory tree and look at
files, etc. but I cannot boot it...)
If anyone knows what is going on when I attempt to install 304.131 here in
Lubuntu 16.10,
and can advise me what to do. I would be very grateful.
--
scott@scott-ASUS-M2N68-AM-PLUS:~$ uname -a
Linux scott-ASUS-M2N68-AM-PLUS 4.8.0-27-generic #29-Ubuntu SMP Thu Oct 20
21:03:13 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
scott@scott-ASUS-M2N68-AM-PLUS:~$ lsb_release -dsc
Ubuntu 16.10
yakkety
scott@scott-ASUS-M2N68-AM-PLUS:~$ echo $DESKTOP_SESSION
Lubuntu
nvidia-graphics-drivers-304 (304.131-0ubuntu3) xenial;
--
ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: nvidia-304 304.131-0ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
Uname: Linux 4.8.0-27-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
DKMSKernelVersion: 4.8.0-27-generic
Date: Fri Nov 11 15:48:41 2016
DuplicateSignature: dkms:
[Desktop-packages] [Bug 1641233] Re: nvidia-304 (not installed): nvidia-304 kernel module failed to build
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nvidia-graphics-drivers-304 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
https://bugs.launchpad.net/bugs/1641233
Title:
nvidia-304 (not installed): nvidia-304 kernel module failed to build
Status in nvidia-graphics-drivers-304 package in Ubuntu:
Confirmed
Bug description:
I had used nvidia-304 successfully in Lubuntu 16.04.
With Lubuntu 16.10, it would not load into the kernel.
I just recently downloaded a fixed 304.132 version, which loaded into the
kernel, and was
usable, but a program (Hugin) which had started up fine under nouveau (but
during the use of which nouveau had screen-crashed, forcing hard-shutdown),
failed to start, with the following terminal output:
"
The program 'hugin' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
(Details: serial 541 error_code 2 request_code 154 minor_code 24)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
"
Since Hugin had worked fine in Lubuntu 16.04 with nvidia-304 - 304.131,
I found a version of that for Xenial Xerus (304.131-0ubuntu3) at
https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304, and tried
to install that.
It failed to install, however...
"Building initial module for 4.8.0-27-generic
Error! Bad return status for module build on kernel: 4.8.0-27-generic (x86_64)
Consult /var/lib/dkms/nvidia-304/304.131/build/make.log for more information."
I will (try to) attach the log file for the install
("/var/lib/dkms/nvidia-304/304.131/build/make.log"), but here are the lines
containing the word "error":
"echo >&2 " ERROR: Kernel configuration is invalid.";\
echo >&2 " include/generated/autoconf.h or include/config/auto.conf
are missing.";\
echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix
it.";\
...
/var/lib/dkms/nvidia-304/304.131/build/nv-mlock.c:52:11: error: too many
arguments to function ‘get_user_pages’
ret = get_user_pages(current, mm, (unsigned long)address,
^~
In file included from /var/lib/dkms/nvidia-304/304.131/build/nv-linux.h:82:0,
from /var/lib/dkms/nvidia-304/304.131/build/nv-mlock.c:15:
./include/linux/mm.h:1315:6: note: declared here
long get_user_pages(unsigned long start, unsigned long nr_pages,
^~
/var/lib/dkms/nvidia-304/304.131/build/nv-mlock.c:65:13: error: implicit
declaration of function ‘page_cache_release’
[-Werror=implicit-function-declaration]
page_cache_release(user_pages[i]);
^~
cc1: some warnings being treated as errors
scripts/Makefile.build:289: recipe for target
'/var/lib/dkms/nvidia-304/304.131/build/nv-mlock.o' failed
make[3]: *** [/var/lib/dkms/nvidia-304/304.131/build/nv-mlock.o] Error 1
Makefile:1489: recipe for target
'_module_/var/lib/dkms/nvidia-304/304.131/build' failed
make[2]: *** [_module_/var/lib/dkms/nvidia-304/304.131/build] Error 2
NVIDIA: left KBUILD.
nvidia.ko failed to build!
Makefile:255: recipe for target 'module' failed
make[1]: *** [module] Error 1
makefile:59: recipe for target 'module' failed
make: *** [module] Error 2
"
I am hoping that there is some simple way to get this older version to
load/work,
as I am running out of options for being able to run Hugin:
1: nouveau screen-crashes in Hugin (which starts up fine) when I try to open
the images from which to make the panorama
2: the fixed nvidia-304.132 loads in the kernal, but Hugin crashes upon
starting up
3: the older nvidia-304.131 fails to install
4: I would consider going back to 16.04 (which is in one of 5 partitions
which I reserve for different Lubuntu versions as they come along), but grub,
in installing 16.10, somehow made booting 16.04 impossible (some sort of
Emergency terminal starts up, and I don't know enough of what's happening to
know what to do... The partition is fine - I can traverse the directory tree
and look at files, etc. but I cannot boot it...)
If anyone knows what is going on when I attempt to install 304.131 here in
Lubuntu 16.10,
and can advise me what to do. I would be very grateful.
--
scott@scott-ASUS-M2N68-AM-PLUS:~$ uname -a
Linux scott-ASUS-M2N68-AM-PLUS 4.8.0-27-generic #29-Ubuntu SMP Thu Oct 20
21:03:13 UTC 2016 x86_64
[Desktop-packages] [Bug 1416897] Re: static image of desktop and windows displayed instead of lockscreen
I occasionally observe this behavior on 16.04 as well, when the computer returns from suspend. -- 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/1416897 Title: static image of desktop and windows displayed instead of lockscreen Status in gnome-screensaver package in Ubuntu: Confirmed Bug description: This is a follow-on from bug 1375271( https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1375271 ), though it may actually implicate a different underlying problem. . Expectation -- Given any one of the following actions: - (from active desktop session) choosing "lock" from the Unity Panel power menu; - (from locked session with screen turned off): using mouse movement, keystrokes, etc. to poke the screen awake; or - (from suspend) initiating a resume, ...the expected result is to display an interactive lockscreen where the active user's password can be entered to access the session. On this particular machine, which is a touch hybrid, the lockscreen also includes the Onboard soft keyboard. . Observed behavior -- Instead of the lockscreen, each of these actions triggers the machine to display an image of the desktop/window session as it had been near the time of the lock or suspend. The cursor is visible and can be moved. The Unity Panel and Launcher usually appear as normal, although sometimes they are missing. Nothing happens when the user attempts to interact with the visible session by mouse or keyboard input. Keyboard input will actually be fed to the lockscreen's password entry window, however. So blindly typing the password from the zombie GUI session image -- and then pressing "enter" -- will bring up an active, working session. TTY session logins are available by the keyboard shortcuts ctrl- alt-F[number]. After pulling up one of these login screens (without actually logging in), then returning with ctrl-alt-F7, the lockscreen appears as expected. . Regression timeframe: I believe this behavior began sometime during January 2015. . Replication: This unexpected behavior takes place almost every time one of the listed actions is taken. During one period of testing on 2015-01-31, the bug disappeared for a few rounds of lock and unlock. However, it re-appeared shortly thereafter (I believe after the next restart or suspend-resume). . Video attachment: A 1-minute video (.webm, no audio) is attached showing one form of this bug (simple lock-unlock). The main feed was taken from a smartphone, but the video also includes an inset of what SimpleScreenRecorder (SSR) "saw" during the process. On "lock", the actual screen became fully black. SSR, by contrast, recorded a black screen that included a clock in the top-right. On mouse movement, the actual screen displayed the static image of the GUI/desktop session. SSR, by contrast, recorded a delayed but normal lockscreen appearing. . Security tag reasoning: This bug displays a snapshot of recent screen contents from a user's GUI session even when the user has (actively or indirectly) locked the session. It also prevents a user from turning on the screen to command a user switch, go into TTY, etc. without displaying an image of her private GUI session. . Current graphics-related system info: OEM: HP Envy x360 15t (convertible hybrid notebook) CPU/GPU: Intel(R) Core(TM) i7-4510U CPU @ 2.00GHz | Intel HD Graphics 4400 OpenGL Core Profile version: 3.3 Mesa 10.5.0-devel OpenGL Extensions version: 3.0 Mesa 10.5.0-devel OS: Ubuntu 14.10 64-bit Kernel: 3.16.0-29 generic X Server: xorg-server 2:1.16.1.901-1ubuntu1~utopic1 Pixman version: 0.32.4 Compiz version: 0.9.12 Please let me know if there is further config information that would be helpful. . Upstream testing: This is a production machine. I am willing to test pre-release packages provided the testing configurations are easy to revert (such as upstream kernels). I have been burned in the past with broken package systems and protracted config repairs after testing experimental graphics and video driver software. But I would still be willing give it a shot if there is a simple and reliable process to roll back the changes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1416897/+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 1641233] Re: nvidia-304 (not installed): nvidia-304 kernel module failed to build
Lubuntu noticed that I had 304.131-0ubuntu3, and Software Updates
offered to install the (non-fixed) 304.132-0ubuntu1.
In the changelog displayed, I noted that there was a 304.131-0ubuntu4 and
304.131-0ubuntu5.
but the latest I found at the above website was 304.131-0ubuntu3.
I see from the changelog:
"Version 304.131-0ubuntu5:
* debian/templates/control.in:
- Add transitional packages to deprecate the -updates flavour.
Version 304.131-0ubuntu4:
* debian/templates/dkms.conf.in,
debian/dkms/patches/buildfix_kernel_4.6.patch:
- Add support for Linux 4.6."
Since Lubuntu 16.04 used Linux 4.4.xxx, I am guessing that whatever
changed in 4.6 that made 304.131-0ubuntu4 necessary is still present in
4.8, and thus possibly that is why 304.131-0ubuntu3 did not work.
Why is there no version higher than 304.131-0ubuntu3 in the official (?)
nvidia-graphics-drivers-304 site above?
Where can I find 304.131-0ubuntu5 (at least 304.131-0ubuntu4, but I
assume what bug(s) 304.131-0ubuntu5 fixed might somehow be
important...)?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
https://bugs.launchpad.net/bugs/1641233
Title:
nvidia-304 (not installed): nvidia-304 kernel module failed to build
Status in nvidia-graphics-drivers-304 package in Ubuntu:
Confirmed
Bug description:
I had used nvidia-304 successfully in Lubuntu 16.04.
With Lubuntu 16.10, it would not load into the kernel.
I just recently downloaded a fixed 304.132 version, which loaded into the
kernel, and was
usable, but a program (Hugin) which had started up fine under nouveau (but
during the use of which nouveau had screen-crashed, forcing hard-shutdown),
failed to start, with the following terminal output:
"
The program 'hugin' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
(Details: serial 541 error_code 2 request_code 154 minor_code 24)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
"
Since Hugin had worked fine in Lubuntu 16.04 with nvidia-304 - 304.131,
I found a version of that for Xenial Xerus (304.131-0ubuntu3) at
https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304, and tried
to install that.
It failed to install, however...
"Building initial module for 4.8.0-27-generic
Error! Bad return status for module build on kernel: 4.8.0-27-generic (x86_64)
Consult /var/lib/dkms/nvidia-304/304.131/build/make.log for more information."
I will (try to) attach the log file for the install
("/var/lib/dkms/nvidia-304/304.131/build/make.log"), but here are the lines
containing the word "error":
"echo >&2 " ERROR: Kernel configuration is invalid.";\
echo >&2 " include/generated/autoconf.h or include/config/auto.conf
are missing.";\
echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix
it.";\
...
/var/lib/dkms/nvidia-304/304.131/build/nv-mlock.c:52:11: error: too many
arguments to function ‘get_user_pages’
ret = get_user_pages(current, mm, (unsigned long)address,
^~
In file included from /var/lib/dkms/nvidia-304/304.131/build/nv-linux.h:82:0,
from /var/lib/dkms/nvidia-304/304.131/build/nv-mlock.c:15:
./include/linux/mm.h:1315:6: note: declared here
long get_user_pages(unsigned long start, unsigned long nr_pages,
^~
/var/lib/dkms/nvidia-304/304.131/build/nv-mlock.c:65:13: error: implicit
declaration of function ‘page_cache_release’
[-Werror=implicit-function-declaration]
page_cache_release(user_pages[i]);
^~
cc1: some warnings being treated as errors
scripts/Makefile.build:289: recipe for target
'/var/lib/dkms/nvidia-304/304.131/build/nv-mlock.o' failed
make[3]: *** [/var/lib/dkms/nvidia-304/304.131/build/nv-mlock.o] Error 1
Makefile:1489: recipe for target
'_module_/var/lib/dkms/nvidia-304/304.131/build' failed
make[2]: *** [_module_/var/lib/dkms/nvidia-304/304.131/build] Error 2
NVIDIA: left KBUILD.
nvidia.ko failed to build!
Makefile:255: recipe for target 'module' failed
make[1]: *** [module] Error 1
makefile:59: recipe for target 'module' failed
make: *** [module] Error 2
"
I am hoping that there is some simple way to get this older version to
load/work,
as I am running out of options for being able to run Hugin:
1: nouveau screen-crashes in Hugin (which starts up fine) when I try to open
the images from which to make the panorama
2: the fixed nvidia-30
[Desktop-packages] [Bug 755342] Re: Samsung Xcover 271 B2710 mass storage does not mount automatically
udippel, instead of ranting generally you could just use Debian instead of Ubuntu. It's likely that you would not run into this bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/755342 Title: Samsung Xcover 271 B2710 mass storage does not mount automatically Status in usb-modeswitch package in Ubuntu: Fix Released Bug description: Steps to reproduce: 1. In the interface of the Samsung Xcover 271 B2710, set it to connect as mass storage. 2. Connect it to the computer via USB cabel. Notice that it does not mount automatically. Also it does mount automatically when instead of step 1 it is set to connect to Samsung Kies or to sync with a media player. Below I provide output from dmesg and lsusb -vv. Output from dmesg as it is connected (step 2): [101332.680133] usb 2-6: new high speed USB device using ehci_hcd and address 6 [101333.630726] Initializing USB Mass Storage driver... [101333.630861] scsi5 : usb-storage 2-6:1.0 [101333.630956] usbcore: registered new interface driver usb-storage [101333.630958] USB Mass Storage support registered. Output from lsusb -vv: Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass9 Hub bDeviceSubClass 0 Unused bDeviceProtocol 0 Full speed (or root) hub bMaxPacketSize064 idVendor 0x1d6b Linux Foundation idProduct 0x0001 1.1 root hub bcdDevice2.06 iManufacturer 3 iProduct2 iSerial 1 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 25 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 Unused bInterfaceProtocol 0 Full speed (or root) hub iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0002 1x 2 bytes bInterval 255 can't get hub descriptor: Operation not permitted cannot read device status, Operation not permitted (1) Bus 006 Device 002: ID 046d:c01b Logitech, Inc. MX310 Optical Mouse Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x046d Logitech, Inc. idProduct 0xc01b MX310 Optical Mouse bcdDevice 18.00 iManufacturer 1 iProduct2 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 98mA 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 0 HID Device Descriptor: bLength 9 bDescriptorType33 bcdHID 1.10 bCountryCode0 Not supported bNumDescriptors 1 bDescriptorType34 Report wDescriptorLength 64 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type
[Desktop-packages] [Bug 1639180] Re: no login possible after update to nvidia 304.132
I also cannot log on since the update to 304.132. Ubuntu 14.04 Geforce 9100 Right now I am using the nouveau driver but it is not a satisfactory solution. I have two monitors and with the nouveau driver one runs at a much lower resolution that the other. With the 304.131 driver this was not the case. Having struggled to get a system that works I am hesitant to try the workaround in comment #20 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1639180 Title: no login possible after update to nvidia 304.132 Status in nvidia-graphics-drivers-304 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-legacy-304xx package in Debian: Confirmed Bug description: Ubuntu 16.04 LTS NVIDIA driver: - nvidia-graphics-drivers-304 - update to version 304.132 dpkg.log: upgrade nvidia-304-updates:amd64 304.131-0ubuntu3 304.132-0ubuntu0.16.04.2 - reboot - lightdm login screen - login - a few seconds some flickering - and the lightdm login screen appears again It is not possible to login. Unity is not loading. .xsession-errors: X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 155 (GLX) Minor opcode of failed request: 3 (X_GLXCreateContext) Value in failed request: 0x0 Serial number of failed request: 34 Current serial number in output stream: 35 See also bug 1634802 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+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 1631600] Re: window contents scaling option per-display
This is a limitation of X, not Unity. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1631600 Title: window contents scaling option per-display Status in unity-control-center package in Ubuntu: Confirmed Bug description: In the unity control center design panel, the window content scaling is missing a very important option: "per-display" Background: My primary notebook display is a 4k monitor with high dpi. External monitors are often only 1080p monitors. Because I can't scale the displays accordingly to their dpi, windows on one display are very small and the other one are big. Only offering effectively basically 3 options, biggest-control-area, smallest-control-area and according-to-one-display is not enough. It is much needed to be able to control the window scaling according to the display it is currently in. A window's anchor point should decide which scaling factor is applied. This would not prevent falsely scaled windows to clip into other displays, but it would be very much appreciated by multi monitor users. Ubuntu version: Description: Ubuntu 16.04.1 LTS Release: 16.04 unity-control-center: Installiert: 15.04.0+16.04.20160705-0ubuntu1 Related bugs: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1294578 https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1297053 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1631600/+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 1591157] Re: webbrowser-app does not honour scale setting on HiDPI display
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity-control-center (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1591157 Title: webbrowser-app does not honour scale setting on HiDPI display Status in Oxide: Invalid Status in unity-control-center package in Ubuntu: Confirmed Status in webbrowser-app package in Ubuntu: Invalid Bug description: The attached screenshot should say it all, showing it in comparison with Firefox and, indeed, the rest of the Unity desktop. Basically, on a 4K display, with a native resolution of 3840x2160, but with the scaling factor set to 2, and Scale all window contents set on, *most* of the unity desktop these days respects this; it nearly all works. webbrowser-app seems to have no awareness of it at all, and thus its windows show up tiny. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: webbrowser-app 0.23+16.04.20160413-0ubuntu1 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: Unity Date: Fri Jun 10 12:55:30 2016 InstallationDate: Installed on 2016-03-30 (71 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) SourcePackage: webbrowser-app UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1591157/+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 1569970] Re: Nautilus does not start
I am experiencing the same issue on an up-to-date Ubuntu 16.04 install. It seems to happen randomly. Nautilus doesn't launch and gives the error previously reported if launched via command line. A restart fixes it temporarily. GNOME nautilus 3.14.3 Linux 4.4.0-45-generic (nautilus:18396): GLib-GIO-CRITICAL **: g_dbus_interface_skeleton_unexport: assertion 'interface_->priv->connections != NULL' failed (nautilus:18396): GLib-GIO-CRITICAL **: g_dbus_interface_skeleton_unexport: assertion 'interface_->priv->connections != NULL' failed Could not register the application: Timeout was reached (nautilus:18396): Gtk-CRITICAL **: gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed (nautilus:18396): GLib-GObject-WARNING **: invalid (NULL) pointer instance (nautilus:18396): GLib-GObject-CRITICAL **: g_signal_connect_object: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed I tried killing/ending the nautilus process and the whole X/unity session froze. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1569970 Title: Nautilus does not start Status in nautilus package in Ubuntu: Confirmed Bug description: when opening nautilus i get the following errors: lotuspsychje@R00TBOOK:~$ nautilus (nautilus:9475): GLib-GIO-CRITICAL **: g_dbus_interface_skeleton_unexport: assertion 'interface_->priv->connections != NULL' failed (nautilus:9475): GLib-GIO-CRITICAL **: g_dbus_interface_skeleton_unexport: assertion 'interface_->priv->connections != NULL' failed Kon de toepassing niet registreren: Tijd is verlopen (nautilus:9475): Gtk-CRITICAL **: gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed (nautilus:9475): GLib-GObject-WARNING **: invalid (NULL) pointer instance (nautilus:9475): GLib-GObject-CRITICAL **: g_signal_connect_object: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed gksu nautilus opens nautilus, but also with an error: lotuspsychje@R00TBOOK:~$ gksu nautilus (nautilus:10257): GLib-GIO-CRITICAL **: g_dbus_interface_skeleton_unexport: assertion 'interface_->priv->connections != NULL' failed ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 13 17:22:53 2016 GsettingsChanges: b'org.gnome.nautilus.preferences' b'confirm-trash' b'false' b'org.gnome.nautilus.preferences' b'click-policy' b"'single'" b'org.gnome.nautilus.preferences' b'enable-delete' b'true' b'org.gnome.nautilus.window-state' b'geometry' b"'890x550+0+24'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2016-04-04 (8 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.xdg.autostart.nautilus.autostart.desktop: 2016-04-05T06:03:34.591882 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1569970/+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 1641264] [NEW] libreoffice crashes on startup when using OpenGL rendering and proprietary nvidia driver.
Public bug reported: I noticed that Libreoffice was rendering very slow (I can see each menu option drawn) so I tried using OpenGL rendering, which causes libreoffice to crash immediately on start-up. I confirm that OpenGL is working fine: $ glxinfo | head name of display: :0.0 display: :0 screen: 0 direct rendering: Yes server glx vendor string: NVIDIA Corporation server glx version string: 1.4 I'm able to use glxgears and other apps like djv_view with fast rendering. I've attached the gdb trace resulting from the crash with debug symbols, following is an except: Thread 1 "soffice.bin" received signal SIGSEGV, Segmentation fault. 0x in ?? () #0 0x in ?? () #1 0x768e96f7 in OpenGLContext::AcquireFramebuffer (this=0x128f600, rTe xture=...) at /build/libreoffice-OypX7x/libreoffice-5.1.4/vcl/source/opengl/Open GLContext.cxx:1773 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libreoffice 1:5.1.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Nov 11 18:45:52 2016 InstallationDate: Installed on 2010-11-05 (2198 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) SourcePackage: libreoffice UpgradeStatus: Upgraded to xenial on 2016-11-02 (9 days ago) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Attachment added: "Full GDB trace with debug symbols" https://bugs.launchpad.net/bugs/1641264/+attachment/4776218/+files/gdbtrace.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1641264 Title: libreoffice crashes on startup when using OpenGL rendering and proprietary nvidia driver. Status in libreoffice package in Ubuntu: New Bug description: I noticed that Libreoffice was rendering very slow (I can see each menu option drawn) so I tried using OpenGL rendering, which causes libreoffice to crash immediately on start-up. I confirm that OpenGL is working fine: $ glxinfo | head name of display: :0.0 display: :0 screen: 0 direct rendering: Yes server glx vendor string: NVIDIA Corporation server glx version string: 1.4 I'm able to use glxgears and other apps like djv_view with fast rendering. I've attached the gdb trace resulting from the crash with debug symbols, following is an except: Thread 1 "soffice.bin" received signal SIGSEGV, Segmentation fault. 0x in ?? () #0 0x in ?? () #1 0x768e96f7 in OpenGLContext::AcquireFramebuffer (this=0x128f600, rTe xture=...) at /build/libreoffice-OypX7x/libreoffice-5.1.4/vcl/source/opengl/Open GLContext.cxx:1773 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libreoffice 1:5.1.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Nov 11 18:45:52 2016 InstallationDate: Installed on 2010-11-05 (2198 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) SourcePackage: libreoffice UpgradeStatus: Upgraded to xenial on 2016-11-02 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1641264/+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 1508407] Re: libre office impress display broken gradient in slide show
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (Ubuntu) Status: New => Confirmed -- 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/1508407 Title: libre office impress display broken gradient in slide show Status in xorg package in Ubuntu: Confirmed Bug description: While testing ubuntu gnome iso: 20151020, I have this issue: Libre office impress display broken gradient in slide show mode. When editing gradient displayed normally. attached screen shot i'm using Intel VGA ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: libreoffice-impress 1:5.0.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 CasperVersion: 1.365 CurrentDesktop: GNOME Date: Wed Oct 21 10:27:37 2015 LiveMediaBuild: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151019) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 CasperVersion: 1.365 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME DistUpgraded: Fresh install DistroCodename: wily DistroRelease: Ubuntu 15.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:5021] Subsystem: Lenovo Device [17aa:5021] LiveMediaBuild: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20DCA02WIA Package: xorg 1:7.7+7ubuntu4 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=(loop)/casper/vmlinuz.efi boot=casper iso-scan/filename=/iso/username-15.10-desktop-amd64.iso locale=en_US.UTF-8 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Tags: wily ubuntu UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.2.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/15/2015 dmi.bios.vendor: LENOVO dmi.bios.version: J5ET46WW (1.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20DCA02WIA dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJ5ET46WW(1.17):bd07/15/2015:svnLENOVO:pn20DCA02WIA:pvrThinkPadE450:rvnLENOVO:rn20DCA02WIA:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20DCA02WIA dmi.product.version: ThinkPad E450 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9 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.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Mon Oct 26 03:07:28 2015 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1530 vendor BOE xserver.version: 2:1.17.2-1ubuntu9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1508407/+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 1022858] Re: Guest session asks for a password after switching users
Same problem in Xenial 16.04, running kernel 4.4.0-47 and also upstream kernel 4.7.10. I can get back into the guest session once without problems, but when I suspend and restart, the guest session demands a password. Trying to switch users back into guest opens a new instance of guest. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1022858 Title: Guest session asks for a password after switching users Status in lightdm package in Ubuntu: Confirmed Bug description: When I switch back to an already open guest session from my user account, I find that the guest session is locked and it asks for the Guest password (which obviously there isn't because it's a guest session!). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-session-bin 3.2.1-0ubuntu8 ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19 Uname: Linux 3.2.0-26-generic x86_64 ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 Date: Tue Jul 10 09:54:55 2012 ExecutablePath: /usr/bin/gnome-session InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) XsessionErrors: (compiz:1719): GConf-CRITICAL **: gconf_client_add_dir: assertion `gconf_valid_key (dirname, NULL)' failed --- ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 DistroRelease: Ubuntu 12.04 InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) MarkForUpload: True Package: lightdm 1.2.1-0ubuntu1.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.2.0-36.57-generic 3.2.35 Tags: precise running-unity Uname: Linux 3.2.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1022858/+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 243431] Re: Can't copy to disk mounted under a Samba share if space doesn't exist in the share
** Changed in: nautilus Status: New => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/243431 Title: Can't copy to disk mounted under a Samba share if space doesn't exist in the share Status in Nautilus: Expired Status in nautilus package in Ubuntu: Triaged Bug description: I've got a directory on my server with several mount points inside, shared using Samba. Using Nautilus, I can't copy files to the mounted disks inside the share, unless ample space exists on the parent disk. The space exists on the mounted disks, but Nautilus doesn't recognise that there is indeed more space available and refuses to copy. The only workaround is to use each disk as its own share, and mount them all on the client. Hypothetical: * I have a server with a samba share /home/foo with 5 meg free space. * I have a mount under this directory /home/foo/disk with 10 meg free space. * Mounting the foo share on my Ubuntu desktop is no problem, but when I want to copy a 10 meg file to foo/disk, Nautilus refuses telling me I only have 5 meg free. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/243431/+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 1046805] Re: X IO Error : Using g_idle_add_full inside ibus_im_context_focus_in instead of gdk_threads_add_idle_full
** Changed in: ibus (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1046805 Title: X IO Error : Using g_idle_add_full inside ibus_im_context_focus_in instead of gdk_threads_add_idle_full Status in ibus package in Ubuntu: Fix Released Bug description: This is a bug in ibus-gtk2 version 1.4, libray /usr/lib/x86_64-linux- gnu/gtk-2.0/2.10.0/immodules/im-ibus.so is in Ubuntu 12.04. It causes "random" X IO errors , because it is a multithreading bug. I reported it already to the ibus project at http://code.google.com/p/ibus/issues/detail?id=1505&thanks=1505&ts=1346933625, but it is a show stopper for us so we want a fast fix. ibus_im_context_focus_in in ibus/client/gtk2/ibusimcontext.c uses g_idle_add_full with a callback that call GDK functions, so it call them without the GDK lock. It should use instead gdk_threads_add_idle_full to make the callback run with a lock. Got broken by this commit https://github.com/ibus/ibus/commit/279ee5d5b3697b427cc22cd99a55f4e611318e25#client/gtk2/ibusimcontext.c Broken in ibus-gtk2 1.4, still ok in 1.3. backtrace Breakpoint 1, 0x004b6094 in ?? () (gdb) where #0 0x004b6094 in ?? () #1 0x7569841e in _XIOError () from /usr/lib/x86_64-linux-gnu/libX11.so.6 #2 0x7569638b in _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6 #3 0x75693407 in XTranslateCoordinates () from /usr/lib/x86_64-linux-gnu/libX11.so.6 #4 0x75c02b2d in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0 #5 0x7fffd8968caf in ?? () from /usr/lib/x86_64-linux-gnu/gtk-2.0/2.10.0/immodules/im-ibus.so #6 0x76910d53 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x769110a0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7691149a in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x004503ca in ?? () #10 0x in ?? () To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1046805/+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 1619033] Re: System is freezing
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- 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/1619033 Title: System is freezing Status in xorg package in Ubuntu: Expired Bug description: The system freezing constantly!!! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] É um diretório: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 367.44 Wed Aug 17 22:24:07 PDT 2016 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Aug 31 17:11:49 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-36-generic, x86_64: installed nvidia-367, 367.44, 4.4.0-36-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GM107 [GeForce GTX 750 Ti] [10de:1380] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GM107 [GeForce GTX 750 Ti] [19da:288a] InstallationDate: Installed on 2016-08-30 (1 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic root=UUID=fdc6e4e3-4350-40d0-8787-fb0bc15f9f4b ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/24/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2601 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2601:bd03/24/2015:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. version.compiz: compiz 1:0.9.12.2+16.04.20160801.3-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Wed Aug 31 16:51:24 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.3-1ubuntu2.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1619033/+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 948105] Re: amarok gui bug in kde 4.8
** Changed in: amarok (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to amarok in Ubuntu. https://bugs.launchpad.net/bugs/948105 Title: amarok gui bug in kde 4.8 Status in Amarok: Fix Released Status in amarok package in Ubuntu: Fix Released Bug description: In Kde 4.8 Amarok has problems with gui . I made screenshot. In Kde 4.7.4 everything was ok. I`m using updated version 64 bit Kubuntu Precise. To manage notifications about this bug go to: https://bugs.launchpad.net/amarok/+bug/948105/+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 1570653] Re: LG 31MU97-B Black 31" 4K Monitor not detected properly
** Changed in: xorg (Ubuntu) Status: Incomplete => Confirmed -- 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/1570653 Title: LG 31MU97-B Black 31" 4K Monitor not detected properly Status in xorg package in Ubuntu: Confirmed Bug description: 4K monitor is not properly detected. using xfce desktop "Display" utility, my monitor is detected as "Goldstar Company Ltd 27" with a resolution of 3840x2160 and 60.0Hz The actual monitor is an LG 31MU97-B Black 31" with a resolution of 4096x2160. I'm pretty sure the Monitor's resolution was properly detected in 15.10 (4096x2160). It was called "Goldstar Company Ltd" but I do not recall which size was detected. (27" or 31") I remember seeing a 4K youtube video in 15.10 and noting the black bands on each side of the display, due to the difference between 3840 and 4096. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: 2016-04-14 20:11:08,467 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory) (8)) DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Curacao PRO [Radeon R7 370 / R9 270/370 OEM] [1002:6811] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Curacao PRO [Radeon R7 370 / R9 270/370 OEM] [174b:e271] InstallationDate: Installed on 2015-11-24 (204 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) LightdmGreeterLog: upstart: indicator-application main process (2191) killed by TERM signal Invalid MIT-MAGIC-COOKIE-1 key LightdmGreeterLogOld: ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug 7 2015, 01:24:18) ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf upstart: indicator-application main process (1802) killed by TERM signal MachineType: To be filled by O.E.M. To be filled by O.E.M. Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-lowlatency root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-22.40-lowlatency 4.4.8 Tags: xenial ubuntu Uname: Linux 4.4.0-22-lowlatency x86_64 UpgradeStatus: Upgraded to xenial on 2016-04-15 (62 days ago) UserGroups: adm audio cdrom dip libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH 990FX R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2501:bd04/08/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FXR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1570653/+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 1570653] Re: LG 31MU97-B Black 31" 4K Monitor not detected properly
Improvements and bug fixes for your graphics card should eventually filter down from the latest kernels into the stable kernel series, and from then into Ubuntu. If you want to make sure of that, you can file an upstream bug report at bugzilla.kernel.org -- 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/1570653 Title: LG 31MU97-B Black 31" 4K Monitor not detected properly Status in xorg package in Ubuntu: Confirmed Bug description: 4K monitor is not properly detected. using xfce desktop "Display" utility, my monitor is detected as "Goldstar Company Ltd 27" with a resolution of 3840x2160 and 60.0Hz The actual monitor is an LG 31MU97-B Black 31" with a resolution of 4096x2160. I'm pretty sure the Monitor's resolution was properly detected in 15.10 (4096x2160). It was called "Goldstar Company Ltd" but I do not recall which size was detected. (27" or 31") I remember seeing a 4K youtube video in 15.10 and noting the black bands on each side of the display, due to the difference between 3840 and 4096. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: 2016-04-14 20:11:08,467 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory) (8)) DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Curacao PRO [Radeon R7 370 / R9 270/370 OEM] [1002:6811] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Curacao PRO [Radeon R7 370 / R9 270/370 OEM] [174b:e271] InstallationDate: Installed on 2015-11-24 (204 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) LightdmGreeterLog: upstart: indicator-application main process (2191) killed by TERM signal Invalid MIT-MAGIC-COOKIE-1 key LightdmGreeterLogOld: ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug 7 2015, 01:24:18) ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf upstart: indicator-application main process (1802) killed by TERM signal MachineType: To be filled by O.E.M. To be filled by O.E.M. Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-lowlatency root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-22.40-lowlatency 4.4.8 Tags: xenial ubuntu Uname: Linux 4.4.0-22-lowlatency x86_64 UpgradeStatus: Upgraded to xenial on 2016-04-15 (62 days ago) UserGroups: adm audio cdrom dip libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH 990FX R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2501:bd04/08/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FXR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1570653/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://
[Desktop-packages] [Bug 1631600] Re: window contents scaling option per-display
At the moment I bypass it by scaling (increasing) the resolution of the output device via "xrandr". This works fine, but it costs more performance and is not persistent at the cost of running a script after each login. So if X does not support the window scaling (and probably never will), then the control panel could support resolution upscaling. By the way: The unity control panel does not support scaled output devices. It displays in the display position view the real output resolution, but not the scaled one. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1631600 Title: window contents scaling option per-display Status in unity-control-center package in Ubuntu: Confirmed Bug description: In the unity control center design panel, the window content scaling is missing a very important option: "per-display" Background: My primary notebook display is a 4k monitor with high dpi. External monitors are often only 1080p monitors. Because I can't scale the displays accordingly to their dpi, windows on one display are very small and the other one are big. Only offering effectively basically 3 options, biggest-control-area, smallest-control-area and according-to-one-display is not enough. It is much needed to be able to control the window scaling according to the display it is currently in. A window's anchor point should decide which scaling factor is applied. This would not prevent falsely scaled windows to clip into other displays, but it would be very much appreciated by multi monitor users. Ubuntu version: Description: Ubuntu 16.04.1 LTS Release: 16.04 unity-control-center: Installiert: 15.04.0+16.04.20160705-0ubuntu1 Related bugs: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1294578 https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1297053 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1631600/+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 1639337] Re: Ubuntu 16.10 Abs_pressure not reported from kernel evdev to xserver-xorg-evdev
I will tell even more: downgrading to xserver-xorg-input- evdev_2.10.1-1ubuntu2_amd64.deb fixes the problem. -- 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/1639337 Title: Ubuntu 16.10 Abs_pressure not reported from kernel evdev to xserver- xorg-evdev Status in network-manager package in Ubuntu: Confirmed Bug description: Please refer to bug filed with freedesktop.org: https://bugs.freedesktop.org/show_bug.cgi?id=98575 I modified a driver for the Bosto Tablet 22HD and others, this has been working without problems across the last several releases and continues to work with 16.04.1 LTS. When I upgraded to 16.10, pressure readings are lost from all applications, X & Y data still visible. evtest shows correct EV_ data for ABS_X ABS_Y and ABS_PRESSURE, but when xinput is used. xinput --list --long The Valuator for pressure is listed, but no changes occur as the tool is used. The parameters of the Valuator can still be modified using xinput tweaking tools, but no pressure reported. All X apps requiring pressure data fail. I made a fresh install of 16.10, loaded the driver same issue. I run 16.04.1 LTS, everything fine. I have others users of my driver code also using 16.04.1 without issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1639337/+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
