[Desktop-packages] [Bug 152279] Re: Totem gets aspect ratio wrong
This bug is 11 years old by now. Totem is the default movie player for Ubuntu and this deserves proper attention. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/152279 Title: Totem gets aspect ratio wrong Status in totem package in Ubuntu: Confirmed Bug description: Binary package hint: totem I use a pivot monitor. When I rotate the screen with xrandr -o left or Grandr, totem gets the aspect ratio wrong. For instance a 4:3 film is shown as 3:4, that means higher than wide. It is also not possible to correct the aspect ratio from the GUI menu. New video thumbnails are also distorted, however in the other direction: They become much wider than hig. Kaffeine shows the same buggy behaviour as Totem, while VLC doesn't. VLC gets the aspect ratio right. This bug was also not there in Feisty. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/152279/+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 589485] Re: Ignores physical display size and calculates based on 96DPI
There is some progress upstream: https://bugs.freedesktop.org/show_bug.cgi?id=41115 -- 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/589485 Title: Ignores physical display size and calculates based on 96DPI Status in X.Org X server: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: The X server, starting with 1.7, ignores the physical size reported by the EDID or in xorg.conf and calculates it based on screen resolution and a DPI of 96. This is rather annoying for users of high DPI screens. GNOME and KDE (used?) to set 96 DPI by default in their settings. We should check whether they still do, and if so let them handle this; I don't think X should be handling this. To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/589485/+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 1694939] [NEW] vlna: does not behave correctly with some utf-8 input
Public bug reported: The vlna program is supposed to put non-breakable space after non- syllabic prepositions (for czech/slovak typestting with TeX). It does not detect some of the cases (and the documentation does not mention that) due to simplified word parsing: * "v lese" is correctly transformed to "v~lese" * "„v lese“" should have the ~ inserted, however, is left unchanged, presumably because the „ character is not recognized as non-word, thus the "v" is not recognized as standalone word. This problem should be at least documented in the manpage, or, in the better case, fixed in the code. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: texlive-binaries 2015.20160222.37495-1 ProcVersionSignature: Ubuntu 4.4.0-75.96-lowlatency 4.4.59 Uname: Linux 4.4.0-75-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Jun 1 11:20:31 2017 SourcePackage: texlive-bin UpgradeStatus: Upgraded to xenial on 2012-03-12 (1906 days ago) ** Affects: texlive-bin (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texlive-bin in Ubuntu. https://bugs.launchpad.net/bugs/1694939 Title: vlna: does not behave correctly with some utf-8 input Status in texlive-bin package in Ubuntu: New Bug description: The vlna program is supposed to put non-breakable space after non- syllabic prepositions (for czech/slovak typestting with TeX). It does not detect some of the cases (and the documentation does not mention that) due to simplified word parsing: * "v lese" is correctly transformed to "v~lese" * "„v lese“" should have the ~ inserted, however, is left unchanged, presumably because the „ character is not recognized as non-word, thus the "v" is not recognized as standalone word. This problem should be at least documented in the manpage, or, in the better case, fixed in the code. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: texlive-binaries 2015.20160222.37495-1 ProcVersionSignature: Ubuntu 4.4.0-75.96-lowlatency 4.4.59 Uname: Linux 4.4.0-75-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Jun 1 11:20:31 2017 SourcePackage: texlive-bin UpgradeStatus: Upgraded to xenial on 2012-03-12 (1906 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-bin/+bug/1694939/+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 1557956] [NEW] Should warn hyphenation for document language is not installed (and the document uses it)
Public bug reported: Opening a document which had active hyphenation (different installation of LO) on a machine where LO lacks relevant hyphenation packages results in substantial changes in formatting -- usually larger interword-spaces and paragraphs taking more lines than they did before. There is no hint that hyphenation for that particular language is not available; unless the user gives detailed look to discover no hyphenation at all, he/she may quickly come to the conclusion that the document or LO installation is "broken". Writer should show some (non-intrusive) message that hyphenation for the language is not available and what should be done to activate it. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libreoffice-writer 1:5.1.1~rc2-0ubuntu1~xenial1 ProcVersionSignature: Ubuntu 3.19.0-49.55-lowlatency 3.19.8-ckt12 Uname: Linux 3.19.0-49-lowlatency x86_64 NonfreeKernelModules: btrfs ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c pci_stub binfmt_misc cfg80211 joydev hid_logitech_hidpp snd_hda_codec_hdmi snd_hda_intel snd_hda_controller eeepc_wmi asus_wmi sparse_keymap snd_hda_codec x86_pkg_temp_thermal intel_powerclamp video snd_hwdep snd_pcm snd_seq_midi kvm_intel snd_seq_midi_event kvm snd_rawmidi crct10dif_pclmul snd_seq crc32_pclmul snd_seq_device snd_timer snd aesni_intel sb_edac aes_x86_64 lrw soundcore gf128mul glue_helper edac_core ablk_helper serio_raw mei_me cryptd mei lpc_ich tpm_infineon 8250_fintek shpchp mac_hid nct6775 hwmon_vid coretemp parport_pc ppdev nfsd lp auth_rpcgss nfs_acl lockd grace sunrpc parport autofs4 raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid0 multipath linear hid_logitech_dj usbhid hid raid1 amdkfd amd_iommu_v2 mxm_wmi radeon igb ttm drm_kms_helper dca psmouse ptp drm ahci pps_core libahci i2c_algo_bit wmi ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Mar 16 09:27:38 2016 SourcePackage: libreoffice UpgradeStatus: Upgraded to xenial on 2012-03-12 (1464 days ago) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- 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/1557956 Title: Should warn hyphenation for document language is not installed (and the document uses it) Status in libreoffice package in Ubuntu: New Bug description: Opening a document which had active hyphenation (different installation of LO) on a machine where LO lacks relevant hyphenation packages results in substantial changes in formatting -- usually larger interword-spaces and paragraphs taking more lines than they did before. There is no hint that hyphenation for that particular language is not available; unless the user gives detailed look to discover no hyphenation at all, he/she may quickly come to the conclusion that the document or LO installation is "broken". Writer should show some (non-intrusive) message that hyphenation for the language is not available and what should be done to activate it. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libreoffice-writer 1:5.1.1~rc2-0ubuntu1~xenial1 ProcVersionSignature: Ubuntu 3.19.0-49.55-lowlatency 3.19.8-ckt12 Uname: Linux 3.19.0-49-lowlatency x86_64 NonfreeKernelModules: btrfs ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c pci_stub binfmt_misc cfg80211 joydev hid_logitech_hidpp snd_hda_codec_hdmi snd_hda_intel snd_hda_controller eeepc_wmi asus_wmi sparse_keymap snd_hda_codec x86_pkg_temp_thermal intel_powerclamp video snd_hwdep snd_pcm snd_seq_midi kvm_intel snd_seq_midi_event kvm snd_rawmidi crct10dif_pclmul snd_seq crc32_pclmul snd_seq_device snd_timer snd aesni_intel sb_edac aes_x86_64 lrw soundcore gf128mul glue_helper edac_core ablk_helper serio_raw mei_me cryptd mei lpc_ich tpm_infineon 8250_fintek shpchp mac_hid nct6775 hwmon_vid coretemp parport_pc ppdev nfsd lp auth_rpcgss nfs_acl lockd grace sunrpc parport autofs4 raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid0 multipath linear hid_logitech_dj usbhid hid raid1 amdkfd amd_iommu_v2 mxm_wmi radeon igb ttm drm_kms_helper dca psmouse ptp drm ahci pps_core libahci i2c_algo_bit wmi ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Mar 16 09:27:38 2016 SourcePackage: libreoffice UpgradeStatus: Upgraded to xenial on 2012-03-12 (1464 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1557956/+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 589485]
@Michal: I have also 1.17.2 and reported DPI is still 96x96, even though the actual resolution is 174x171 (see https://bugs.launchpad.net/bugs/1512606 for details). -- 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/589485 Title: Ignores physical display size and calculates based on 96DPI Status in X.Org X server: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: The X server, starting with 1.7, ignores the physical size reported by the EDID or in xorg.conf and calculates it based on screen resolution and a DPI of 96. This is rather annoying for users of high DPI screens. GNOME and KDE (used?) to set 96 DPI by default in their settings. We should check whether they still do, and if so let them handle this; I don't think X should be handling this. To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/589485/+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 1512606] Re: Display size incorreectly detected (assuming 96x96 DPI)
*** This bug is a duplicate of bug 589485 *** https://bugs.launchpad.net/bugs/589485 The dupe is Confirmed and High priority. When you assigned it to unity before, I can have justified doubts you generally read what you reply to. Never mind, this one is not relevant anymore, being a duplicate. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1512606 Title: Display size incorreectly detected (assuming 96x96 DPI) Status in xserver-xorg-video-intel package in Ubuntu: Won't Fix Bug description: I am running 14.10 on Lenovo Yoga 12 with 280x160mm panel with 1920x1080 resolution, which translates to 174x171 DPI by trivial calculation. The panel size is correctly reported by edid: $ get-edid | parse-edid This is read-edid version 3.0.2. Prepare for some fun. Attempting to use i2c interface No EDID on bus 0 No EDID on bus 1 No EDID on bus 2 No EDID on bus 3 No EDID on bus 5 1 potential busses found: 4 256-byte EDID successfully retrieved from i2c bus 4 Looks like i2c was successful. Have a good day. Checksum Correct Section "Monitor" Identifier "" ModelName "" VendorName "LGD" # Monitor Manufactured week 0 of 2013 # EDID version 1.4 # Digital Display DisplaySize 280 160 Gamma 2.20 Option "DPMS" "false" Modeline"Mode 0" 138.46 1920 1968 2000 2106 1080 1083 1088 1095 +hsync -vsync EndSection The XServer thinks something different: $ xdpyinfo | grep -B2 resolution screen #0: dimensions:1920x1080 pixels (508x285 millimeters) resolution:96x96 dots per inch where the physical size is garbage. The driver sets DPI to 96 despite having correct data, and there seems to be no straightforward way to force a different DPI (see e.g. [1]). The internet is full of various workarounds for HiDPI displays, which include setting text-scaling- factor in dconf (gnome-only) , layout.css.devPixelsPerPt (mozilla products), scaling-factor (integer values only?), all of the toolkit- or program-specific. They have all of them some gotchas (such as terribly-looking interface, different scaling of some text, ugly icons etc). I am willing to help debugging the driver, since Ubuntu should have a way to behave well out-of-box on HiDPI configurations. If the driver reports the right DPI, I assume many of those issue would disappear. [1] https://ask.fedoraproject.org/en/question/39272/how-to-configure- screen-dpi-ppi-properly/ ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 BootLog: [[32m OK [0m] Started Modem Manager. [[32m OK [0m] Started Detect the available GPUs and deal with any system changes. Starting Light Display Manager... 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 Nov 3 08:54:40 2015 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:503e] InstallationDate: Installed on 2015-08-31 (63 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: LENOVO 20DLCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic root=UUID=f5cdca16-e2f9-4b9e-b12c-65011c787ea7 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-intel UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JEET66WW (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 20DLCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0K11826 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJEET66WW(1.15):bd06/05/2015:svnLENOVO:pn20DLCTO1WW:pvrThinkPadS1Yoga12:rvnLENOVO:rn20DLCTO1WW:rvrSDK0K11826WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20DLCTO1WW dmi.product.version: ThinkPad S1 Yoga 12 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1 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
[Desktop-packages] [Bug 1512606] Re: Display size incorreectly detected (assuming 96x96 DPI)
*** This bug is a duplicate of bug 589485 *** https://bugs.launchpad.net/bugs/589485 @Timo seriously, don't set "won't fix" when you manifestly have no clue what this bug is about. It would be more helpful to find the LP duplicate and set it, which I just did. ** This bug has been marked a duplicate of bug 589485 Ignores physical display size and calculates based on 96DPI -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1512606 Title: Display size incorreectly detected (assuming 96x96 DPI) Status in xserver-xorg-video-intel package in Ubuntu: Won't Fix Bug description: I am running 14.10 on Lenovo Yoga 12 with 280x160mm panel with 1920x1080 resolution, which translates to 174x171 DPI by trivial calculation. The panel size is correctly reported by edid: $ get-edid | parse-edid This is read-edid version 3.0.2. Prepare for some fun. Attempting to use i2c interface No EDID on bus 0 No EDID on bus 1 No EDID on bus 2 No EDID on bus 3 No EDID on bus 5 1 potential busses found: 4 256-byte EDID successfully retrieved from i2c bus 4 Looks like i2c was successful. Have a good day. Checksum Correct Section "Monitor" Identifier "" ModelName "" VendorName "LGD" # Monitor Manufactured week 0 of 2013 # EDID version 1.4 # Digital Display DisplaySize 280 160 Gamma 2.20 Option "DPMS" "false" Modeline"Mode 0" 138.46 1920 1968 2000 2106 1080 1083 1088 1095 +hsync -vsync EndSection The XServer thinks something different: $ xdpyinfo | grep -B2 resolution screen #0: dimensions:1920x1080 pixels (508x285 millimeters) resolution:96x96 dots per inch where the physical size is garbage. The driver sets DPI to 96 despite having correct data, and there seems to be no straightforward way to force a different DPI (see e.g. [1]). The internet is full of various workarounds for HiDPI displays, which include setting text-scaling- factor in dconf (gnome-only) , layout.css.devPixelsPerPt (mozilla products), scaling-factor (integer values only?), all of the toolkit- or program-specific. They have all of them some gotchas (such as terribly-looking interface, different scaling of some text, ugly icons etc). I am willing to help debugging the driver, since Ubuntu should have a way to behave well out-of-box on HiDPI configurations. If the driver reports the right DPI, I assume many of those issue would disappear. [1] https://ask.fedoraproject.org/en/question/39272/how-to-configure- screen-dpi-ppi-properly/ ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 BootLog: [[32m OK [0m] Started Modem Manager. [[32m OK [0m] Started Detect the available GPUs and deal with any system changes. Starting Light Display Manager... 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 Nov 3 08:54:40 2015 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:503e] InstallationDate: Installed on 2015-08-31 (63 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: LENOVO 20DLCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic root=UUID=f5cdca16-e2f9-4b9e-b12c-65011c787ea7 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-intel UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JEET66WW (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 20DLCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0K11826 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJEET66WW(1.15):bd06/05/2015:svnLENOVO:pn20DLCTO1WW:pvrThinkPadS1Yoga12:rvnLENOVO:rn20DLCTO1WW:rvrSDK0K11826WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20DLCTO1WW dmi.product.version: ThinkPad S1 Yoga 12 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1 version.ia32-libs: ia32-libs N/A
[Desktop-packages] [Bug 589485] Re: Ignores physical display size and calculates based on 96DPI
@Sergio, sorry but your comments are OT. Different resolutions for different screens are not supported on the toolkit level; a window can be on both screens at once and such, and it is beyond the scope of this bug. Viewing distance again has nothing to do with this bug; DPI does not depend on the viewing distance, it simply expresses physical dimensions (lengths) of one pixel; length does not depend on distance (I am a physicist, I know that one for sure). Of course for guessing comfortable font size for reading, viewing distance is important, but that is an entirely different problem, although it actually required a valid value of DPI. -- 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/589485 Title: Ignores physical display size and calculates based on 96DPI Status in X.Org X server: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: The X server, starting with 1.7, ignores the physical size reported by the EDID or in xorg.conf and calculates it based on screen resolution and a DPI of 96. This is rather annoying for users of high DPI screens. GNOME and KDE (used?) to set 96 DPI by default in their settings. We should check whether they still do, and if so let them handle this; I don't think X should be handling this. To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/589485/+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 589485] Re: Ignores physical display size and calculates based on 96DPI
There is 62 people who think this bug *is* important. It is a problem mainly with displays of which DPI is far from 96x96, such as more and more common HiDPI. Let's not turn it into discussion forum on Linux vs. Windows, or ideal state of Linux. We simply want Xorg to respect the DPI reported by EDID. -- 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/589485 Title: Ignores physical display size and calculates based on 96DPI Status in X.Org X server: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: The X server, starting with 1.7, ignores the physical size reported by the EDID or in xorg.conf and calculates it based on screen resolution and a DPI of 96. This is rather annoying for users of high DPI screens. GNOME and KDE (used?) to set 96 DPI by default in their settings. We should check whether they still do, and if so let them handle this; I don't think X should be handling this. To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/589485/+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 1512606] Re: Display size incorreectly detected (assuming 96x96 DPI)
(Putting back to intel driver; please actually read the bug report before changing to unity) ** Package changed: unity (Ubuntu) => xserver-xorg-video-intel (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1512606 Title: Display size incorreectly detected (assuming 96x96 DPI) Status in xserver-xorg-video-intel package in Ubuntu: New Bug description: I am running 14.10 on Lenovo Yoga 12 with 280x160mm panel with 1920x1080 resolution, which translates to 174x171 DPI by trivial calculation. The panel size is correctly reported by edid: $ get-edid | parse-edid This is read-edid version 3.0.2. Prepare for some fun. Attempting to use i2c interface No EDID on bus 0 No EDID on bus 1 No EDID on bus 2 No EDID on bus 3 No EDID on bus 5 1 potential busses found: 4 256-byte EDID successfully retrieved from i2c bus 4 Looks like i2c was successful. Have a good day. Checksum Correct Section "Monitor" Identifier "" ModelName "" VendorName "LGD" # Monitor Manufactured week 0 of 2013 # EDID version 1.4 # Digital Display DisplaySize 280 160 Gamma 2.20 Option "DPMS" "false" Modeline"Mode 0" 138.46 1920 1968 2000 2106 1080 1083 1088 1095 +hsync -vsync EndSection The XServer thinks something different: $ xdpyinfo | grep -B2 resolution screen #0: dimensions:1920x1080 pixels (508x285 millimeters) resolution:96x96 dots per inch where the physical size is garbage. The driver sets DPI to 96 despite having correct data, and there seems to be no straightforward way to force a different DPI (see e.g. [1]). The internet is full of various workarounds for HiDPI displays, which include setting text-scaling- factor in dconf (gnome-only) , layout.css.devPixelsPerPt (mozilla products), scaling-factor (integer values only?), all of the toolkit- or program-specific. They have all of them some gotchas (such as terribly-looking interface, different scaling of some text, ugly icons etc). I am willing to help debugging the driver, since Ubuntu should have a way to behave well out-of-box on HiDPI configurations. If the driver reports the right DPI, I assume many of those issue would disappear. [1] https://ask.fedoraproject.org/en/question/39272/how-to-configure- screen-dpi-ppi-properly/ ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 BootLog: [[32m OK [0m] Started Modem Manager. [[32m OK [0m] Started Detect the available GPUs and deal with any system changes. Starting Light Display Manager... 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 Nov 3 08:54:40 2015 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:503e] InstallationDate: Installed on 2015-08-31 (63 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: LENOVO 20DLCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic root=UUID=f5cdca16-e2f9-4b9e-b12c-65011c787ea7 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-intel UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JEET66WW (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 20DLCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0K11826 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJEET66WW(1.15):bd06/05/2015:svnLENOVO:pn20DLCTO1WW:pvrThinkPadS1Yoga12:rvnLENOVO:rn20DLCTO1WW:rvrSDK0K11826WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20DLCTO1WW dmi.product.version: ThinkPad S1 Yoga 12 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1 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
[Desktop-packages] [Bug 1512606] [NEW] Display size incorreectly detected (assuming 96x96 DPI)
Public bug reported: I am running 14.10 on Lenovo Yoga 12 with 280x160mm panel with 1920x1080 resolution, which translates to 174x171 DPI by trivial calculation. The panel size is correctly reported by edid: $ get-edid | parse-edid This is read-edid version 3.0.2. Prepare for some fun. Attempting to use i2c interface No EDID on bus 0 No EDID on bus 1 No EDID on bus 2 No EDID on bus 3 No EDID on bus 5 1 potential busses found: 4 256-byte EDID successfully retrieved from i2c bus 4 Looks like i2c was successful. Have a good day. Checksum Correct Section "Monitor" Identifier "" ModelName "" VendorName "LGD" # Monitor Manufactured week 0 of 2013 # EDID version 1.4 # Digital Display DisplaySize 280 160 Gamma 2.20 Option "DPMS" "false" Modeline"Mode 0" 138.46 1920 1968 2000 2106 1080 1083 1088 1095 +hsync -vsync EndSection The XServer thinks something different: $ xdpyinfo | grep -B2 resolution screen #0: dimensions:1920x1080 pixels (508x285 millimeters) resolution:96x96 dots per inch where the physical size is garbage. The driver sets DPI to 96 despite having correct data, and there seems to be no straightforward way to force a different DPI (see e.g. [1]). The internet is full of various workarounds for HiDPI displays, which include setting text-scaling- factor in dconf (gnome-only) , layout.css.devPixelsPerPt (mozilla products), scaling-factor (integer values only?), all of the toolkit- or program-specific. They have all of them some gotchas (such as terribly- looking interface, different scaling of some text, ugly icons etc). I am willing to help debugging the driver, since Ubuntu should have a way to behave well out-of-box on HiDPI configurations. If the driver reports the right DPI, I assume many of those issue would disappear. [1] https://ask.fedoraproject.org/en/question/39272/how-to-configure- screen-dpi-ppi-properly/ ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 BootLog: [[32m OK [0m] Started Modem Manager. [[32m OK [0m] Started Detect the available GPUs and deal with any system changes. Starting Light Display Manager... 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 Nov 3 08:54:40 2015 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:503e] InstallationDate: Installed on 2015-08-31 (63 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: LENOVO 20DLCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic root=UUID=f5cdca16-e2f9-4b9e-b12c-65011c787ea7 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-intel UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JEET66WW (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 20DLCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0K11826 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJEET66WW(1.15):bd06/05/2015:svnLENOVO:pn20DLCTO1WW:pvrThinkPadS1Yoga12:rvnLENOVO:rn20DLCTO1WW:rvrSDK0K11826WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20DLCTO1WW dmi.product.version: ThinkPad S1 Yoga 12 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1 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 Nov 2 08:12:10 2015 xserver.configfile: default xserver.errors: Wacom ISDv4 EC Pen stylus: Invalid type 'cursor' for this device. Wacom ISDv4 EC Pen stylus: Invalid type 'touch' for this device. Wacom ISDv4 EC Pen stylus: Invalid type
[Desktop-packages] [Bug 152279] Re: Totem gets aspect ratio wrong
For me, the bug is definitely present also with gst-launch-0.10 playbin, using 3 pivoted monitors, with 14.04LTS. Smplayer gets the aspect ratio right (make your life better and ditch totem). This bug is 8 years old. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/152279 Title: Totem gets aspect ratio wrong Status in totem package in Ubuntu: Confirmed Bug description: Binary package hint: totem I use a pivot monitor. When I rotate the screen with xrandr -o left or Grandr, totem gets the aspect ratio wrong. For instance a 4:3 film is shown as 3:4, that means higher than wide. It is also not possible to correct the aspect ratio from the GUI menu. New video thumbnails are also distorted, however in the other direction: They become much wider than hig. Kaffeine shows the same buggy behaviour as Totem, while VLC doesn't. VLC gets the aspect ratio right. This bug was also not there in Feisty. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/152279/+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 1362326] [NEW] LCD panel sometimes says No signal and is blank, the driver thinks it is active
Public bug reported: I have 3 LCD panels attached via straight DisplayPort cables (no daisy chaining, no DVI-DP converters and so on) to the FirePro V7900, which has 4 DisplayPort sockets. One of the panels will often not come up when screens are DPMS-suspended (xset dpms force off, or by the screensaver). The panel will then say No signal, but the card still thinks it is enabled and working (as verified in AMDCCCLE). It is sometimes possible make it work again by cycling a few times xset dpms force off and then pressing a key to turn screens on. It is always the same panel which has troubles, but it is port-bound (I tried exchaning the screens physically; it is the port numbered 3 in amdcccle, the other two being 1 and 2), not screen- bound. Sometimes the screen also just flickers, showing what it should only intermittently. Restarting X fixes the issue (but terminates the session) most the time. The open-source driver does not suffer from this issue at all. The fglrx driver has had this issue since as long as I remember (2 or 3 years). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: fglrx-updates 2:13.350.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,compiztoolbox,resize,move,place,snap,gnomecompat,mousepoll,session,regex,wall,imgpng,grid,vpswitch,animation,expo,ezoom,workarounds,unitymtgrabhandles,fade,scale,unityshell] CompositorRunning: None CurrentDesktop: LXDE Date: Wed Aug 27 22:42:24 2014 DistUpgraded: 2012-03-12 13:59:22,955 DEBUG icon theme changed, re-reading DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cayman PRO GL [FirePro V7900] [1002:6704] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:2b0c] MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic root=UUID=3cc5f6b9-69d1-4bb6-a9d0-93d506786ed9 ro nosplash radeon.dpm=1 nosplash radeon.dpm=1 SourcePackage: fglrx-installer-updates UpgradeStatus: Upgraded to trusty on 2012-03-12 (898 days ago) dmi.bios.date: 10/03/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0604 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9X79 DELUXE 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.:bvr0604:bd10/03/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP9X79DELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.11.1+14.04.20140701-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Aug 27 22:39:56 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] AIGLX error: failed to open /usr/X11R6/lib/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2 xserver.video_driver: fglrx ** Affects: fglrx-installer-updates (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug possible-manual-nvidia-install trusty ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer-updates in Ubuntu. https://bugs.launchpad.net/bugs/1362326 Title: LCD panel sometimes says No signal and is blank, the driver thinks it is active Status in “fglrx-installer-updates” package in Ubuntu: New Bug description: I have 3 LCD panels attached via straight DisplayPort cables
[Desktop-packages] [Bug 1350910] Re: blank screen after suspend resume
*** This bug is a duplicate of bug 1349866 *** https://bugs.launchpad.net/bugs/1349866 ** This bug has been marked a duplicate of bug 1349866 display blank after resume (consistent) -- 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/1350910 Title: blank screen after suspend resume Status in “xorg” package in Ubuntu: Incomplete Bug description: Mouse and keyboard not working, still able to ssh into system and reboot. Xorg.0.log saved from ssh session after a problem appear attached. WORKAROUND: It seems no problem with fglrx proprietary drivers. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.3 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 CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied Date: Thu Jul 31 19:19:59 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7420G] [1002:9992] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:194e] InstallationDate: Installed on 2014-07-06 (25 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: Hewlett-Packard HP ProBook 455 G1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=3cc3893f-1a34-4d21-8304-52e841a9dbef ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/05/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CPE Ver. F.21 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 194E dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 91.0B dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CPEVer.F.21:bd09/05/2013:svnHewlett-Packard:pnHPProBook455G1:pvrA2018CD200:rvnHewlett-Packard:rn194E:rvrKBCVersion91.0B:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 455 G1 dmi.product.version: A2018CD200 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Thu Jul 31 19:19:05 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2.1 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1350910/+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 1349866] Re: display blank after resume (consistent)
Confirmed as per duplicate report #1350910; as suggested there, I flashed new BIOS to F.28 without any improvement; the changelog [1] does not mention anything display-related either. (The flash BIOS utility can be run in Windows (on any computer) to create USB flash, which can be used in the Linux machine to update the BIOS, without depending on the OS.) I confirm that installing fglrx or fglrx-updates (which was previously, when trusty first came, freezing the system at boot-time IIRC) works around the issue. [1] http://h20565.www2.hp.com/portal/site/hpsc/template.PAGE/public/psi/swdDetails/?sp4ts.oid=5359417spf_p.tpst=swdMainspf_p.prp_swdMain =wsrp- navigationalState%3Didx%253D5%257CswItem%253Dob_129812_1%257CswEnvOID%253D4059%257CitemLocale%253D%257CswLang%253D%257Cmode%253D4%257Caction%253DdriverDocumentjavax.portlet.begCacheTok=com.vignette.cachetokenjavax.portlet.endCacheTok=com.vignette.cachetoken -- 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/1349866 Title: display blank after resume (consistent) Status in “xorg” package in Ubuntu: Confirmed Bug description: With the hardware as shown in automatically attached files (HP ProBook 455), display never recovers from resume, although the computer works fine otherwise (it can be connected to over ssh, in particular). I disabled the discrete GPU BIOS (that is the current stand) but the problem remains. Contrary to #1010683, where some people were helped by using pm-suspend --quirk-test --quirk-s3-mode, this problem is exhibited without discrete graphics (thus ruling out problems with vgaswitcheroo). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 .tmp.unity.support.test.0: .tmp.unity.support.test.1: ApportVersion: 2.14.1-0ubuntu3.2 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 Date: Tue Jul 29 16:32:42 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7420G] [1002:9992] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:194e] InstallationDate: Installed on 2014-06-27 (31 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: Hewlett-Packard HP ProBook 455 G1 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=cs_CZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=8f659b6c-ad5b-49ef-8f46-052d943c2cb5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CPE Ver. F.26 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 194E dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 91.0C dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CPEVer.F.26:bd10/29/2013:svnHewlett-Packard:pnHPProBook455G1:pvrA2018CD200:rvnHewlett-Packard:rn194E:rvrKBCVersion91.0C:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 455 G1 dmi.product.version: A2018CD200 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11.1+14.04.20140701-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Jul 29 16:24:26 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1349866/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages
[Desktop-packages] [Bug 1349866] Re: display blank after resume (consistent)
FWIW, this is the output of radeontool (sudo radeontool light on had no effect at all): $ sudo radeontool regs RADEON_DAC_CNTL RADEON_DAC_EXT_CNTL RADEON_DAC_MACRO_CNTL RADEON_DAC_CNTL2 RADEON_TV_DAC_CNTL c100a080 RADEON_DISP_OUTPUT_CNTL RADEON_CONFIG_MEMSIZE RADEON_AUX_SC_CNTL RADEON_CRTC_EXT_CNTL RADEON_CRTC_GEN_CNTL RADEON_CRTC2_GEN_CNTL RADEON_DEVICE_ID RADEON_DISP_MISC_CNTL 0010 RADEON_GPIO_MONID RADEON_GPIO_MONIDB RADEON_GPIO_CRT2_DDC RADEON_GPIO_DVI_DDC RADEON_GPIO_VGA_DDC RADEON_LVDS_GEN_CNTL RADEON_LVDS_PLL_CNTL RADEON_FP_GEN_CNTL RADEON_FP2_GEN_CNTL RADEON_PPLL_CNTL RADEON_PPLL_REF_DIV RADEON_PPLL_DIV_3 RADEON_PIXCLKS_CNTL RADEON_P2PLL_CNTL RADEON_P2PLL_REF_DIV RADEON_P2PLL_DIV_0 RADEON_VCLK_ECP_CNTL RADEON_MEM_TIMING_CNTL RADEON_TMDS_PLL_CNTL RADEON_TMDS_TRANSMITTER_CNTL RADEON_CRTC_MORE_CNTL RADEON_FP_H_SYNC_STRT_WID RADEON_FP_V_SYNC_STRT_WID RADEON_FP_CRTC_H_TOTAL_DISP RADEON_FP_CRTC_V_TOTAL_DISP RADEON_FP_HORZ_STRETCH RADEON_FP_VERT_STRETCH RADEON_FP_HORZ_VERT_ACTIVE RADEON_CRTC_H_TOTAL_DISP0001f478 RADEON_CRTC_H_SYNC_STRT_WID 040f0001 RADEON_CRTC_V_TOTAL_DISP RADEON_CRTC_V_SYNC_STRT_WID RADEON_CRTC2_H_TOTAL_DISP 000f RADEON_CRTC2_H_SYNC_STRT_WID3f3f RADEON_CRTC2_V_TOTAL_DISP RADEON_CRTC2_V_SYNC_STRT_WID0002 -- 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/1349866 Title: display blank after resume (consistent) Status in “xorg” package in Ubuntu: New Bug description: With the hardware as shown in automatically attached files (HP ProBook 455), display never recovers from resume, although the computer works fine otherwise (it can be connected to over ssh, in particular). I disabled the discrete GPU BIOS (that is the current stand) but the problem remains. Contrary to #1010683, where some people were helped by using pm-suspend --quirk-test --quirk-s3-mode, this problem is exhibited without discrete graphics (thus ruling out problems with vgaswitcheroo). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 .tmp.unity.support.test.0: .tmp.unity.support.test.1: ApportVersion: 2.14.1-0ubuntu3.2 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 Date: Tue Jul 29 16:32:42 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7420G] [1002:9992] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:194e] InstallationDate: Installed on 2014-06-27 (31 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: Hewlett-Packard HP ProBook 455 G1 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=cs_CZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=8f659b6c-ad5b-49ef-8f46-052d943c2cb5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CPE Ver. F.26 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 194E dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 91.0C dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CPEVer.F.26:bd10/29/2013:svnHewlett-Packard:pnHPProBook455G1:pvrA2018CD200:rvnHewlett-Packard:rn194E:rvrKBCVersion91.0C:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 455 G1 dmi.product.version: A2018CD200 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11.1+14.04.20140701-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri
[Desktop-packages] [Bug 1349866] [NEW] display blank after resume (consistent)
Public bug reported: With the hardware as shown in automatically attached files (HP ProBook 455), display never recovers from resume, although the computer works fine otherwise (it can be connected to over ssh, in particular). I disabled the discrete GPU BIOS (that is the current stand) but the problem remains. Contrary to #1010683, where some people were helped by using pm-suspend --quirk-test --quirk-s3-mode, this problem is exhibited without discrete graphics (thus ruling out problems with vgaswitcheroo). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 .tmp.unity.support.test.0: .tmp.unity.support.test.1: ApportVersion: 2.14.1-0ubuntu3.2 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 Date: Tue Jul 29 16:32:42 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7420G] [1002:9992] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:194e] InstallationDate: Installed on 2014-06-27 (31 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: Hewlett-Packard HP ProBook 455 G1 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=cs_CZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=8f659b6c-ad5b-49ef-8f46-052d943c2cb5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CPE Ver. F.26 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 194E dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 91.0C dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CPEVer.F.26:bd10/29/2013:svnHewlett-Packard:pnHPProBook455G1:pvrA2018CD200:rvnHewlett-Packard:rn194E:rvrKBCVersion91.0C:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 455 G1 dmi.product.version: A2018CD200 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11.1+14.04.20140701-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Jul 29 16:24:26 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 freeze trusty ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1349866 Title: display blank after resume (consistent) Status in “xorg” package in Ubuntu: New Bug description: With the hardware as shown in automatically attached files (HP ProBook 455), display never recovers from resume, although the computer works fine otherwise (it can be connected to over ssh, in particular). I disabled the discrete GPU BIOS (that is the current stand) but the problem remains. Contrary to #1010683, where some people were helped by using pm-suspend --quirk-test --quirk-s3-mode, this problem is exhibited without discrete graphics (thus ruling out problems with vgaswitcheroo). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 .tmp.unity.support.test.0: .tmp.unity.support.test.1: ApportVersion: 2.14.1-0ubuntu3.2 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 Date: Tue Jul 29 16:32:42 2014 DistUpgraded: Fresh install
[Desktop-packages] [Bug 1294044] Re: Network manager fails to connect to WiFi
*** This bug is a duplicate of bug 1311257 *** https://bugs.launchpad.net/bugs/1311257 The fix (11n_disable) did not work in the end; the problem is in wpa_supplicant, which must be killed after resume, as #1311257 suggests. That fixed the problem, so I mark this as dupe. ** This bug has been marked a duplicate of bug 1311257 Wifi cannot connect or unstable after suspend 14.04 -- 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/1294044 Title: Network manager fails to connect to WiFi Status in “network-manager” package in Ubuntu: Confirmed Bug description: Since I updated to trusty a few days ago, NetworkManager fails to connect to a wifi (I tried several wifis, all failed - all of them were encrypted with WPA2, not sure if that might make the difference). Wired network works just fine. The Wifi used to work flawlessly, getting connected within a few seconds. The wireless is 02:00.0 Network controller: Intel Corporation Centrino Advanced-N 6200 (rev 35) When I do sudo stop network-manager and then sudo NetworkManager --no-daemon --log-level=INFO --log-domain=WIFI,SUPPLICANT, I am getting the following (skipping initial logs of reading connections and of the wired NIC DHCP etc): NetworkManager[26290]: (nm-device.c:3920):nm_device_activate: runtime check failed: (priv-state == NM_DEVICE_STATE_DISCONNECTED) NetworkManager[26290]: info (wlan0): using nl80211 for WiFi device control NetworkManager[26290]: info (wlan0) supports 5 scan SSIDs NetworkManager[26290]: warn Connection disconnected (reason -3) NetworkManager[26290]: info (wlan0): supplicant interface state: starting - ready NetworkManager[26290]: info (wlan0): supplicant interface state: ready - disconnected NetworkManager[26290]: info (wlan0) supports 5 scan SSIDs NetworkManager[26290]: warn Connection disconnected (reason -3) NetworkManager[26290]: info Activation (wlan0/wireless): connection 'Rick3' has security, and secrets exist. No new secrets needed. NetworkManager[26290]: info Config: added 'ssid' value 'Rick3' NetworkManager[26290]: info Config: added 'scan_ssid' value '1' NetworkManager[26290]: info Config: added 'key_mgmt' value 'WPA-PSK' NetworkManager[26290]: info Config: added 'auth_alg' value 'OPEN' NetworkManager[26290]: info Config: added 'psk' value 'omitted' NetworkManager[26290]: info Config: set interface ap_scan to 1 NetworkManager[26290]: info (wlan0): supplicant interface state: disconnected - authenticating NetworkManager[26290]: info (wlan0): supplicant interface state: authenticating - disconnected NetworkManager[26290]: info (wlan0): supplicant interface state: disconnected - scanning NetworkManager[26290]: warn Activation (wlan0/wireless): association took too long, failing activation. NetworkManager[26290]: warn Activation (wlan0) failed for connection 'Rick3' NetworkManager[26290]: info (wlan0): supplicant interface state: scanning - disconnected NetworkManager[26290]: warn Couldn't disconnect supplicant interface: This interface is not connected. NetworkManager[26290]: info Activation (wlan0/wireless): access point 'Rick3' has security, but secrets are required. NetworkManager[26290]: info Activation (wlan0/wireless): connection 'Rick3' has security, and secrets exist. No new secrets needed. NetworkManager[26290]: info Config: added 'ssid' value 'Rick3' NetworkManager[26290]: info Config: added 'scan_ssid' value '1' NetworkManager[26290]: info Config: added 'key_mgmt' value 'WPA-PSK' NetworkManager[26290]: info Config: added 'auth_alg' value 'OPEN' NetworkManager[26290]: info Config: added 'psk' value 'omitted' NetworkManager[26290]: info Config: set interface ap_scan to 1 NetworkManager[26290]: info (wlan0): supplicant interface state: disconnected - authenticating NetworkManager[26290]: info (wlan0): supplicant interface state: authenticating - disconnected NetworkManager[26290]: info (wlan0): supplicant interface state: disconnected - scanning NetworkManager[26290]: warn Activation (wlan0/wireless): association took too long, failing activation. NetworkManager[26290]: warn Activation (wlan0) failed for connection 'Rick3' NetworkManager[26290]: info (wlan0): supplicant interface state: scanning - disconnected NetworkManager[26290]: warn Couldn't disconnect supplicant interface: This interface is not connected. NetworkManager[26290]: info Activation (wlan0/wireless): access point 'Rick3' has security, but secrets are required. NetworkManager[26290]: info Activation (wlan0/wireless): connection 'Rick3' has security, and secrets exist. No new secrets needed. NetworkManager[26290]: info Config: added 'ssid' value 'Rick3' NetworkManager[26290]: info Config: added 'scan_ssid' value '1' NetworkManager[26290]: info Config: added 'key_mgmt' value 'WPA-PSK'
[Desktop-packages] [Bug 1294044] Re: Network manager fails to connect to WiFi
I was able to work around the problem by adding options iwlwifi 11n_disable=1 to /etc/modprobe.d/iwlwifi-disable-80211n-local.conf Can any of you test that? Thanks to http://forum.ubuntuusers.de/topic/wlan-faellt-sporadisch-aus/ for the hint. -- 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/1294044 Title: Network manager fails to connect to WiFi Status in “network-manager” package in Ubuntu: Confirmed Bug description: Since I updated to trusty a few days ago, NetworkManager fails to connect to a wifi (I tried several wifis, all failed - all of them were encrypted with WPA2, not sure if that might make the difference). Wired network works just fine. The Wifi used to work flawlessly, getting connected within a few seconds. The wireless is 02:00.0 Network controller: Intel Corporation Centrino Advanced-N 6200 (rev 35) When I do sudo stop network-manager and then sudo NetworkManager --no-daemon --log-level=INFO --log-domain=WIFI,SUPPLICANT, I am getting the following (skipping initial logs of reading connections and of the wired NIC DHCP etc): NetworkManager[26290]: (nm-device.c:3920):nm_device_activate: runtime check failed: (priv-state == NM_DEVICE_STATE_DISCONNECTED) NetworkManager[26290]: info (wlan0): using nl80211 for WiFi device control NetworkManager[26290]: info (wlan0) supports 5 scan SSIDs NetworkManager[26290]: warn Connection disconnected (reason -3) NetworkManager[26290]: info (wlan0): supplicant interface state: starting - ready NetworkManager[26290]: info (wlan0): supplicant interface state: ready - disconnected NetworkManager[26290]: info (wlan0) supports 5 scan SSIDs NetworkManager[26290]: warn Connection disconnected (reason -3) NetworkManager[26290]: info Activation (wlan0/wireless): connection 'Rick3' has security, and secrets exist. No new secrets needed. NetworkManager[26290]: info Config: added 'ssid' value 'Rick3' NetworkManager[26290]: info Config: added 'scan_ssid' value '1' NetworkManager[26290]: info Config: added 'key_mgmt' value 'WPA-PSK' NetworkManager[26290]: info Config: added 'auth_alg' value 'OPEN' NetworkManager[26290]: info Config: added 'psk' value 'omitted' NetworkManager[26290]: info Config: set interface ap_scan to 1 NetworkManager[26290]: info (wlan0): supplicant interface state: disconnected - authenticating NetworkManager[26290]: info (wlan0): supplicant interface state: authenticating - disconnected NetworkManager[26290]: info (wlan0): supplicant interface state: disconnected - scanning NetworkManager[26290]: warn Activation (wlan0/wireless): association took too long, failing activation. NetworkManager[26290]: warn Activation (wlan0) failed for connection 'Rick3' NetworkManager[26290]: info (wlan0): supplicant interface state: scanning - disconnected NetworkManager[26290]: warn Couldn't disconnect supplicant interface: This interface is not connected. NetworkManager[26290]: info Activation (wlan0/wireless): access point 'Rick3' has security, but secrets are required. NetworkManager[26290]: info Activation (wlan0/wireless): connection 'Rick3' has security, and secrets exist. No new secrets needed. NetworkManager[26290]: info Config: added 'ssid' value 'Rick3' NetworkManager[26290]: info Config: added 'scan_ssid' value '1' NetworkManager[26290]: info Config: added 'key_mgmt' value 'WPA-PSK' NetworkManager[26290]: info Config: added 'auth_alg' value 'OPEN' NetworkManager[26290]: info Config: added 'psk' value 'omitted' NetworkManager[26290]: info Config: set interface ap_scan to 1 NetworkManager[26290]: info (wlan0): supplicant interface state: disconnected - authenticating NetworkManager[26290]: info (wlan0): supplicant interface state: authenticating - disconnected NetworkManager[26290]: info (wlan0): supplicant interface state: disconnected - scanning NetworkManager[26290]: warn Activation (wlan0/wireless): association took too long, failing activation. NetworkManager[26290]: warn Activation (wlan0) failed for connection 'Rick3' NetworkManager[26290]: info (wlan0): supplicant interface state: scanning - disconnected NetworkManager[26290]: warn Couldn't disconnect supplicant interface: This interface is not connected. NetworkManager[26290]: info Activation (wlan0/wireless): access point 'Rick3' has security, but secrets are required. NetworkManager[26290]: info Activation (wlan0/wireless): connection 'Rick3' has security, and secrets exist. No new secrets needed. NetworkManager[26290]: info Config: added 'ssid' value 'Rick3' NetworkManager[26290]: info Config: added 'scan_ssid' value '1' NetworkManager[26290]: info Config: added 'key_mgmt' value 'WPA-PSK' NetworkManager[26290]: info Config: added 'auth_alg' value 'OPEN' NetworkManager[26290]: info Config: added 'psk' value 'omitted'
[Desktop-packages] [Bug 1300260] [NEW] Xorg crashed with SIGABRT
*** This bug is a duplicate of bug 1033533 *** https://bugs.launchpad.net/bugs/1033533 Public bug reported: Bug reported automatically. The X seems to have crashed after resume, with mouse moving but keyboard not No other idea about what was happening, hopefully the automatically attached logs will help. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: xserver-xorg-core 2:1.15.0-1ubuntu7 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CrashCounter: 1 Date: Mon Mar 31 16:29:57 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExecutablePath: /usr/bin/Xorg ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GF104GLM [Quadro 3000M] [10de:0e3a] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:04a4] InstallationDate: Installed on 2014-03-31 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140331) MachineType: Dell Inc. Precision M6600 ProcCmdline: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic root=UUID=4e9ddd97-9f89-44b3-89eb-1b6006e3c9a4 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: ?? () from /usr/lib/xorg/modules/libexa.so ?? () from /usr/lib/xorg/modules/libexa.so ?? () from /usr/lib/xorg/modules/libexa.so ?? () from /usr/lib/xorg/modules/libexa.so ?? () from /usr/lib/xorg/modules/libexa.so Title: Xorg crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 05/24/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 04YY4M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd05/24/2011:svnDellInc.:pnPrecisionM6600:pvr01:rvnDellInc.:rn04YY4M:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M6600 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash compiz-0.9 third-party-packages trusty ubuntu ** Information type changed from Private to Public -- 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/1300260 Title: Xorg crashed with SIGABRT Status in “xorg-server” package in Ubuntu: New Bug description: Bug reported automatically. The X seems to have crashed after resume, with mouse moving but keyboard not No other idea about what was happening, hopefully the automatically attached logs will help. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: xserver-xorg-core 2:1.15.0-1ubuntu7 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CrashCounter: 1 Date: Mon Mar 31 16:29:57 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExecutablePath: /usr/bin/Xorg ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GF104GLM [Quadro 3000M] [10de:0e3a] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:04a4] InstallationDate: Installed on 2014-03-31 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140331) MachineType: Dell Inc. Precision M6600 ProcCmdline: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic
[Desktop-packages] [Bug 1294044] Re: Network manager fails to connect to WiFi
Re-opening; the symtpoms disappeared for the first time after installing unity8 (with indicator-network), which also caused both network indicators (NetworkManager and indicator-network) to appear in the systray when using the default Unity session (and interact if weird ways) - but wifi was connecting to just right. After de-installation of unity8, there is just the NetworkManager icon in Unity (default) session again, and NM does not connect to wifi anymore. Please check interactions of indicator-network with the upstream network-manager applet. ** Changed in: network-manager (Ubuntu) Status: Invalid = New -- 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/1294044 Title: Network manager fails to connect to WiFi Status in “network-manager” package in Ubuntu: New Bug description: Since I updated to trusty a few days ago, NetworkManager fails to connect to a wifi (I tried several wifis, all failed - all of them were encrypted with WPA2, not sure if that might make the difference). Wired network works just fine. The Wifi used to work flawlessly, getting connected within a few seconds. The wireless is 02:00.0 Network controller: Intel Corporation Centrino Advanced-N 6200 (rev 35) When I do sudo stop network-manager and then sudo NetworkManager --no-daemon --log-level=INFO --log-domain=WIFI,SUPPLICANT, I am getting the following (skipping initial logs of reading connections and of the wired NIC DHCP etc): NetworkManager[26290]: (nm-device.c:3920):nm_device_activate: runtime check failed: (priv-state == NM_DEVICE_STATE_DISCONNECTED) NetworkManager[26290]: info (wlan0): using nl80211 for WiFi device control NetworkManager[26290]: info (wlan0) supports 5 scan SSIDs NetworkManager[26290]: warn Connection disconnected (reason -3) NetworkManager[26290]: info (wlan0): supplicant interface state: starting - ready NetworkManager[26290]: info (wlan0): supplicant interface state: ready - disconnected NetworkManager[26290]: info (wlan0) supports 5 scan SSIDs NetworkManager[26290]: warn Connection disconnected (reason -3) NetworkManager[26290]: info Activation (wlan0/wireless): connection 'Rick3' has security, and secrets exist. No new secrets needed. NetworkManager[26290]: info Config: added 'ssid' value 'Rick3' NetworkManager[26290]: info Config: added 'scan_ssid' value '1' NetworkManager[26290]: info Config: added 'key_mgmt' value 'WPA-PSK' NetworkManager[26290]: info Config: added 'auth_alg' value 'OPEN' NetworkManager[26290]: info Config: added 'psk' value 'omitted' NetworkManager[26290]: info Config: set interface ap_scan to 1 NetworkManager[26290]: info (wlan0): supplicant interface state: disconnected - authenticating NetworkManager[26290]: info (wlan0): supplicant interface state: authenticating - disconnected NetworkManager[26290]: info (wlan0): supplicant interface state: disconnected - scanning NetworkManager[26290]: warn Activation (wlan0/wireless): association took too long, failing activation. NetworkManager[26290]: warn Activation (wlan0) failed for connection 'Rick3' NetworkManager[26290]: info (wlan0): supplicant interface state: scanning - disconnected NetworkManager[26290]: warn Couldn't disconnect supplicant interface: This interface is not connected. NetworkManager[26290]: info Activation (wlan0/wireless): access point 'Rick3' has security, but secrets are required. NetworkManager[26290]: info Activation (wlan0/wireless): connection 'Rick3' has security, and secrets exist. No new secrets needed. NetworkManager[26290]: info Config: added 'ssid' value 'Rick3' NetworkManager[26290]: info Config: added 'scan_ssid' value '1' NetworkManager[26290]: info Config: added 'key_mgmt' value 'WPA-PSK' NetworkManager[26290]: info Config: added 'auth_alg' value 'OPEN' NetworkManager[26290]: info Config: added 'psk' value 'omitted' NetworkManager[26290]: info Config: set interface ap_scan to 1 NetworkManager[26290]: info (wlan0): supplicant interface state: disconnected - authenticating NetworkManager[26290]: info (wlan0): supplicant interface state: authenticating - disconnected NetworkManager[26290]: info (wlan0): supplicant interface state: disconnected - scanning NetworkManager[26290]: warn Activation (wlan0/wireless): association took too long, failing activation. NetworkManager[26290]: warn Activation (wlan0) failed for connection 'Rick3' NetworkManager[26290]: info (wlan0): supplicant interface state: scanning - disconnected NetworkManager[26290]: warn Couldn't disconnect supplicant interface: This interface is not connected. NetworkManager[26290]: info Activation (wlan0/wireless): access point 'Rick3' has security, but secrets are required. NetworkManager[26290]: info Activation (wlan0/wireless): connection 'Rick3' has security, and secrets exist.
[Desktop-packages] [Bug 1294044] Re: Network manager fails to connect to WiFi
This bug disappeared with updates to Trusty, closing as invalid. ** Changed in: network-manager (Ubuntu) Status: New = Invalid -- 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/1294044 Title: Network manager fails to connect to WiFi Status in “network-manager” package in Ubuntu: Invalid Bug description: Since I updated to trusty a few days ago, NetworkManager fails to connect to a wifi (I tried several wifis, all failed - all of them were encrypted with WPA2, not sure if that might make the difference). Wired network works just fine. The Wifi used to work flawlessly, getting connected within a few seconds. The wireless is 02:00.0 Network controller: Intel Corporation Centrino Advanced-N 6200 (rev 35) When I do sudo stop network-manager and then sudo NetworkManager --no-daemon --log-level=INFO --log-domain=WIFI,SUPPLICANT, I am getting the following (skipping initial logs of reading connections and of the wired NIC DHCP etc): NetworkManager[26290]: (nm-device.c:3920):nm_device_activate: runtime check failed: (priv-state == NM_DEVICE_STATE_DISCONNECTED) NetworkManager[26290]: info (wlan0): using nl80211 for WiFi device control NetworkManager[26290]: info (wlan0) supports 5 scan SSIDs NetworkManager[26290]: warn Connection disconnected (reason -3) NetworkManager[26290]: info (wlan0): supplicant interface state: starting - ready NetworkManager[26290]: info (wlan0): supplicant interface state: ready - disconnected NetworkManager[26290]: info (wlan0) supports 5 scan SSIDs NetworkManager[26290]: warn Connection disconnected (reason -3) NetworkManager[26290]: info Activation (wlan0/wireless): connection 'Rick3' has security, and secrets exist. No new secrets needed. NetworkManager[26290]: info Config: added 'ssid' value 'Rick3' NetworkManager[26290]: info Config: added 'scan_ssid' value '1' NetworkManager[26290]: info Config: added 'key_mgmt' value 'WPA-PSK' NetworkManager[26290]: info Config: added 'auth_alg' value 'OPEN' NetworkManager[26290]: info Config: added 'psk' value 'omitted' NetworkManager[26290]: info Config: set interface ap_scan to 1 NetworkManager[26290]: info (wlan0): supplicant interface state: disconnected - authenticating NetworkManager[26290]: info (wlan0): supplicant interface state: authenticating - disconnected NetworkManager[26290]: info (wlan0): supplicant interface state: disconnected - scanning NetworkManager[26290]: warn Activation (wlan0/wireless): association took too long, failing activation. NetworkManager[26290]: warn Activation (wlan0) failed for connection 'Rick3' NetworkManager[26290]: info (wlan0): supplicant interface state: scanning - disconnected NetworkManager[26290]: warn Couldn't disconnect supplicant interface: This interface is not connected. NetworkManager[26290]: info Activation (wlan0/wireless): access point 'Rick3' has security, but secrets are required. NetworkManager[26290]: info Activation (wlan0/wireless): connection 'Rick3' has security, and secrets exist. No new secrets needed. NetworkManager[26290]: info Config: added 'ssid' value 'Rick3' NetworkManager[26290]: info Config: added 'scan_ssid' value '1' NetworkManager[26290]: info Config: added 'key_mgmt' value 'WPA-PSK' NetworkManager[26290]: info Config: added 'auth_alg' value 'OPEN' NetworkManager[26290]: info Config: added 'psk' value 'omitted' NetworkManager[26290]: info Config: set interface ap_scan to 1 NetworkManager[26290]: info (wlan0): supplicant interface state: disconnected - authenticating NetworkManager[26290]: info (wlan0): supplicant interface state: authenticating - disconnected NetworkManager[26290]: info (wlan0): supplicant interface state: disconnected - scanning NetworkManager[26290]: warn Activation (wlan0/wireless): association took too long, failing activation. NetworkManager[26290]: warn Activation (wlan0) failed for connection 'Rick3' NetworkManager[26290]: info (wlan0): supplicant interface state: scanning - disconnected NetworkManager[26290]: warn Couldn't disconnect supplicant interface: This interface is not connected. NetworkManager[26290]: info Activation (wlan0/wireless): access point 'Rick3' has security, but secrets are required. NetworkManager[26290]: info Activation (wlan0/wireless): connection 'Rick3' has security, and secrets exist. No new secrets needed. NetworkManager[26290]: info Config: added 'ssid' value 'Rick3' NetworkManager[26290]: info Config: added 'scan_ssid' value '1' NetworkManager[26290]: info Config: added 'key_mgmt' value 'WPA-PSK' NetworkManager[26290]: info Config: added 'auth_alg' value 'OPEN' NetworkManager[26290]: info Config: added 'psk' value 'omitted' NetworkManager[26290]: info Config: set interface ap_scan to 1 and this repeats over and over. I can provide any other
[Desktop-packages] [Bug 1294044] Re: Network manager fails to connect to WiFi
Confirming this is *not* a pure driver issue, as I can connect to an encrypted wifi using wicd. -- 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/1294044 Title: Network manager fails to connect to WiFi Status in “network-manager” package in Ubuntu: New Bug description: Since I updated to trusty a few days ago, NetworkManager fails to connect to a wifi (I tried several wifis, all failed - all of them were encrypted with WPA2, not sure if that might make the difference). Wired network works just fine. The Wifi used to work flawlessly, getting connected within a few seconds. The wireless is 02:00.0 Network controller: Intel Corporation Centrino Advanced-N 6200 (rev 35) When I do sudo stop network-manager and then sudo NetworkManager --no-daemon --log-level=INFO --log-domain=WIFI,SUPPLICANT, I am getting the following (skipping initial logs of reading connections and of the wired NIC DHCP etc): NetworkManager[26290]: (nm-device.c:3920):nm_device_activate: runtime check failed: (priv-state == NM_DEVICE_STATE_DISCONNECTED) NetworkManager[26290]: info (wlan0): using nl80211 for WiFi device control NetworkManager[26290]: info (wlan0) supports 5 scan SSIDs NetworkManager[26290]: warn Connection disconnected (reason -3) NetworkManager[26290]: info (wlan0): supplicant interface state: starting - ready NetworkManager[26290]: info (wlan0): supplicant interface state: ready - disconnected NetworkManager[26290]: info (wlan0) supports 5 scan SSIDs NetworkManager[26290]: warn Connection disconnected (reason -3) NetworkManager[26290]: info Activation (wlan0/wireless): connection 'Rick3' has security, and secrets exist. No new secrets needed. NetworkManager[26290]: info Config: added 'ssid' value 'Rick3' NetworkManager[26290]: info Config: added 'scan_ssid' value '1' NetworkManager[26290]: info Config: added 'key_mgmt' value 'WPA-PSK' NetworkManager[26290]: info Config: added 'auth_alg' value 'OPEN' NetworkManager[26290]: info Config: added 'psk' value 'omitted' NetworkManager[26290]: info Config: set interface ap_scan to 1 NetworkManager[26290]: info (wlan0): supplicant interface state: disconnected - authenticating NetworkManager[26290]: info (wlan0): supplicant interface state: authenticating - disconnected NetworkManager[26290]: info (wlan0): supplicant interface state: disconnected - scanning NetworkManager[26290]: warn Activation (wlan0/wireless): association took too long, failing activation. NetworkManager[26290]: warn Activation (wlan0) failed for connection 'Rick3' NetworkManager[26290]: info (wlan0): supplicant interface state: scanning - disconnected NetworkManager[26290]: warn Couldn't disconnect supplicant interface: This interface is not connected. NetworkManager[26290]: info Activation (wlan0/wireless): access point 'Rick3' has security, but secrets are required. NetworkManager[26290]: info Activation (wlan0/wireless): connection 'Rick3' has security, and secrets exist. No new secrets needed. NetworkManager[26290]: info Config: added 'ssid' value 'Rick3' NetworkManager[26290]: info Config: added 'scan_ssid' value '1' NetworkManager[26290]: info Config: added 'key_mgmt' value 'WPA-PSK' NetworkManager[26290]: info Config: added 'auth_alg' value 'OPEN' NetworkManager[26290]: info Config: added 'psk' value 'omitted' NetworkManager[26290]: info Config: set interface ap_scan to 1 NetworkManager[26290]: info (wlan0): supplicant interface state: disconnected - authenticating NetworkManager[26290]: info (wlan0): supplicant interface state: authenticating - disconnected NetworkManager[26290]: info (wlan0): supplicant interface state: disconnected - scanning NetworkManager[26290]: warn Activation (wlan0/wireless): association took too long, failing activation. NetworkManager[26290]: warn Activation (wlan0) failed for connection 'Rick3' NetworkManager[26290]: info (wlan0): supplicant interface state: scanning - disconnected NetworkManager[26290]: warn Couldn't disconnect supplicant interface: This interface is not connected. NetworkManager[26290]: info Activation (wlan0/wireless): access point 'Rick3' has security, but secrets are required. NetworkManager[26290]: info Activation (wlan0/wireless): connection 'Rick3' has security, and secrets exist. No new secrets needed. NetworkManager[26290]: info Config: added 'ssid' value 'Rick3' NetworkManager[26290]: info Config: added 'scan_ssid' value '1' NetworkManager[26290]: info Config: added 'key_mgmt' value 'WPA-PSK' NetworkManager[26290]: info Config: added 'auth_alg' value 'OPEN' NetworkManager[26290]: info Config: added 'psk' value 'omitted' NetworkManager[26290]: info Config: set interface ap_scan to 1 and this repeats over and over. I can provide any other details needed. I double-checked the
[Desktop-packages] [Bug 1294044] [NEW] Network manager fails to connect to WiFi
Public bug reported: Since I updated to trusty a few days ago, NetworkManager fails to connect to a wifi (I tried several wifis, all failed - all of them were encrypted with WPA2, not sure if that might make the difference). Wired network works just fine. The Wifi used to work flawlessly, getting connected within a few seconds. The wireless is 02:00.0 Network controller: Intel Corporation Centrino Advanced-N 6200 (rev 35) When I do sudo stop network-manager and then sudo NetworkManager --no-daemon --log-level=INFO --log-domain=WIFI,SUPPLICANT, I am getting the following (skipping initial logs of reading connections and of the wired NIC DHCP etc): NetworkManager[26290]: (nm-device.c:3920):nm_device_activate: runtime check failed: (priv-state == NM_DEVICE_STATE_DISCONNECTED) NetworkManager[26290]: info (wlan0): using nl80211 for WiFi device control NetworkManager[26290]: info (wlan0) supports 5 scan SSIDs NetworkManager[26290]: warn Connection disconnected (reason -3) NetworkManager[26290]: info (wlan0): supplicant interface state: starting - ready NetworkManager[26290]: info (wlan0): supplicant interface state: ready - disconnected NetworkManager[26290]: info (wlan0) supports 5 scan SSIDs NetworkManager[26290]: warn Connection disconnected (reason -3) NetworkManager[26290]: info Activation (wlan0/wireless): connection 'Rick3' has security, and secrets exist. No new secrets needed. NetworkManager[26290]: info Config: added 'ssid' value 'Rick3' NetworkManager[26290]: info Config: added 'scan_ssid' value '1' NetworkManager[26290]: info Config: added 'key_mgmt' value 'WPA-PSK' NetworkManager[26290]: info Config: added 'auth_alg' value 'OPEN' NetworkManager[26290]: info Config: added 'psk' value 'omitted' NetworkManager[26290]: info Config: set interface ap_scan to 1 NetworkManager[26290]: info (wlan0): supplicant interface state: disconnected - authenticating NetworkManager[26290]: info (wlan0): supplicant interface state: authenticating - disconnected NetworkManager[26290]: info (wlan0): supplicant interface state: disconnected - scanning NetworkManager[26290]: warn Activation (wlan0/wireless): association took too long, failing activation. NetworkManager[26290]: warn Activation (wlan0) failed for connection 'Rick3' NetworkManager[26290]: info (wlan0): supplicant interface state: scanning - disconnected NetworkManager[26290]: warn Couldn't disconnect supplicant interface: This interface is not connected. NetworkManager[26290]: info Activation (wlan0/wireless): access point 'Rick3' has security, but secrets are required. NetworkManager[26290]: info Activation (wlan0/wireless): connection 'Rick3' has security, and secrets exist. No new secrets needed. NetworkManager[26290]: info Config: added 'ssid' value 'Rick3' NetworkManager[26290]: info Config: added 'scan_ssid' value '1' NetworkManager[26290]: info Config: added 'key_mgmt' value 'WPA-PSK' NetworkManager[26290]: info Config: added 'auth_alg' value 'OPEN' NetworkManager[26290]: info Config: added 'psk' value 'omitted' NetworkManager[26290]: info Config: set interface ap_scan to 1 NetworkManager[26290]: info (wlan0): supplicant interface state: disconnected - authenticating NetworkManager[26290]: info (wlan0): supplicant interface state: authenticating - disconnected NetworkManager[26290]: info (wlan0): supplicant interface state: disconnected - scanning NetworkManager[26290]: warn Activation (wlan0/wireless): association took too long, failing activation. NetworkManager[26290]: warn Activation (wlan0) failed for connection 'Rick3' NetworkManager[26290]: info (wlan0): supplicant interface state: scanning - disconnected NetworkManager[26290]: warn Couldn't disconnect supplicant interface: This interface is not connected. NetworkManager[26290]: info Activation (wlan0/wireless): access point 'Rick3' has security, but secrets are required. NetworkManager[26290]: info Activation (wlan0/wireless): connection 'Rick3' has security, and secrets exist. No new secrets needed. NetworkManager[26290]: info Config: added 'ssid' value 'Rick3' NetworkManager[26290]: info Config: added 'scan_ssid' value '1' NetworkManager[26290]: info Config: added 'key_mgmt' value 'WPA-PSK' NetworkManager[26290]: info Config: added 'auth_alg' value 'OPEN' NetworkManager[26290]: info Config: added 'psk' value 'omitted' NetworkManager[26290]: info Config: set interface ap_scan to 1 and this repeats over and over. I can provide any other details needed. I double-checked the firmware loaded, and dmesg greps are also below: # modinfo iwlwifi [...] filename: /lib/modules/3.13.0-17-generic/kernel/drivers/net/wireless/iwlwifi/iwlwifi.ko license:GPL author: Copyright(c) 2003-2013 Intel Corporation i...@linux.intel.com version:in-tree: description:Intel(R) Wireless WiFi driver for Linux firmware: iwlwifi-100-5.ucode firmware: iwlwifi-1000-5.ucode firmware: iwlwifi-135-6.ucode firmware: iwlwifi-105-6.ucode
[Desktop-packages] [Bug 1294052] [NEW] Unlock screen shown twice (violet and black) after resume from sleep
Public bug reported: After waking the computer from suspend, there is 1. The screen saying: This session is locked / You will be redirected ... for about a second, followed by a split second of the framebuffer console. 2. Violet login screen, where I am asked to type my password (which I do) 3. Again shortly the This session is locked screen 4. For about half a second, the desktop (in the state it was locked) appears on the screen 5. Another login screen, black, asks me to type the password (which I do) 6. The session appears and is usable afterwards. I expect the password prompt to be shown *at most* once, not twice, to unlock the session. This is a regression from saucy, where I was typing the password either once, or was even able to disable the lock in dconf/gconf (don't remember exactly where). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.9.12-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 18 12:05:38 2014 InstallationDate: Installed on 2010-10-25 (1240 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) LightdmConfig: [SeatDefaults] greeter-session=unity-greeter user-session=ubuntu autologin-user= SourcePackage: lightdm UpgradeStatus: Upgraded to trusty on 2013-03-29 (354 days ago) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug regression trusty -- 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/1294052 Title: Unlock screen shown twice (violet and black) after resume from sleep Status in “lightdm” package in Ubuntu: New Bug description: After waking the computer from suspend, there is 1. The screen saying: This session is locked / You will be redirected ... for about a second, followed by a split second of the framebuffer console. 2. Violet login screen, where I am asked to type my password (which I do) 3. Again shortly the This session is locked screen 4. For about half a second, the desktop (in the state it was locked) appears on the screen 5. Another login screen, black, asks me to type the password (which I do) 6. The session appears and is usable afterwards. I expect the password prompt to be shown *at most* once, not twice, to unlock the session. This is a regression from saucy, where I was typing the password either once, or was even able to disable the lock in dconf/gconf (don't remember exactly where). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.9.12-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 18 12:05:38 2014 InstallationDate: Installed on 2010-10-25 (1240 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) LightdmConfig: [SeatDefaults] greeter-session=unity-greeter user-session=ubuntu autologin-user= SourcePackage: lightdm UpgradeStatus: Upgraded to trusty on 2013-03-29 (354 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1294052/+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 1043328] Re: corrupt screen both in terminal (KMS) and in X
I am not able to reproduce it with normal installation anymore (13.10), so I assume this is a works for me now (though the upstream bug is confirmed). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1043328 Title: corrupt screen both in terminal (KMS) and in X Status in X.org XServer - ATI gfx chipset driver: Confirmed Status in “xserver-xorg-video-ati” package in Ubuntu: Incomplete Bug description: Using fresh dev quantal installation, I am seeing corruption of the screen making the computer unusable. The terminal gets first set to correct mode, but later, vertical stripes appear (screenshot will be attached). When launching lightdm, there are inclined horizontal lines superimposed over whatever is on the desktop (screenshot attached). ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xserver-xorg-video-ati 1:6.99.99~git20120713.6ef1ad6a-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-13.13-generic 3.5.3 Uname: Linux 3.5.0-13-generic x86_64 ApportVersion: 2.5.1-0ubuntu3 Architecture: amd64 Date: Wed Aug 29 09:32:41 2012 DistUpgraded: 2012-03-12 13:59:22,955 DEBUG icon theme changed, re-reading DistroCodename: quantal DistroVariant: ubuntu DkmsStatus: virtualbox, 4.1.18, 3.5.0-13-generic, x86_64: installed GraphicsCard: Advanced Micro Devices [AMD] nee ATI Cayman XT [Radeon HD 6970] [1002:6718] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:03bc] MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-13-generic root=UUID=3cc5f6b9-69d1-4bb6-a9d0-93d506786ed9 ro nosplash SourcePackage: xserver-xorg-video-ati UpgradeStatus: Upgraded to quantal on 2012-03-12 (170 days ago) dmi.bios.date: 10/03/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0604 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9X79 DELUXE 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.:bvr0604:bd10/03/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP9X79DELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.8+bzr3319-0ubuntu3 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.38-0ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0~git20120821.c1114c61-0ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0~git20120821.c1114c61-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.12.99.905-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120713.6ef1ad6a-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-driver-ati/+bug/1043328/+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 959275] Re: libs unique to nvidia should be linked to /usr/lib
This bug is still relevant. Easily switch for sure does not mean that CUDA programs fail to start when the card is not primary. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/959275 Title: libs unique to nvidia should be linked to /usr/lib Status in “nvidia-graphics-drivers” package in Ubuntu: Won't Fix Bug description: nvidia-current contains libGL.so which is found (if a nvidia card is used for accelerated graphics) by setting /etc/alternatives/x86_64 -linux-gnu_gl_conf. nvidia-current however contains other libraries, which are useful also if an nvidia card is not used for OpenGL, such as libnvidia- compiler.so for OpenCL or libcuda.so for CUDA. In such a case, the whole /usr/lib/nvidia-current directory must NOT be added to ld.so.conf.d or LD_LIBRARY_PATH, since it also contains nvidia's libGL.so, which could override (come first before) libGL.so's installed by other drivers. A workaround is to link manually individual libs from /usr/lib/nvidia- current into /usr/(local/)lib so that they are found, while not exposing the libGL.so. A proper solution would be to create symlinks for libs not carrying a generic name (e.g. libcuda.so, libnvidia-compiler.so, but NOT libOpenCL.so, libGL.so, which are also provided by other packages) in directories searched by ld.so by default, e.g. /usr/lib. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: nvidia-current 295.20-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9 Uname: Linux 3.2.0-18-generic x86_64 NonfreeKernelModules: fglrx nvidia .tmp.unity.support.test.0: ApportVersion: 1.94.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Mar 19 14:04:24 2012 DistUpgraded: Log time: 2012-03-12 11:26:17.508009 DistroCodename: precise DistroVariant: ubuntu DkmsStatus: blcr, 0.8.2: added fglrx-updates, 8.911, 3.2.0-18-generic, x86_64: installed nvidia-current, 295.20, 3.2.0-18-generic, x86_64: installed GraphicsCard: Advanced Micro Devices [AMD] nee ATI Cayman XT [Radeon HD 6970] [1002:6718] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:03bc] NVIDIA Corporation GF110 [GeForce GTX 560 Ti] [10de:1200] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CardExpert Technology Device [10b0:0401] JockeyStatus: xorg:fglrx_updates - ATI/AMD proprietary FGLRX graphics driver (post-release updates) (Proprietary, Disabled, Not in use) xorg:fglrx - ATI/AMD proprietary FGLRX graphics driver (Proprietary, Disabled, Not in use) xorg:nvidia_current - NVIDIA accelerated graphics driver (Proprietary, Disabled, Not in use) xorg:nvidia_current_updates - NVIDIA accelerated graphics driver (post-release updates) (Proprietary, Disabled, Not in use) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-18-generic root=UUID=3cc5f6b9-69d1-4bb6-a9d0-93d506786ed9 ro SourcePackage: nvidia-graphics-drivers UpgradeStatus: Upgraded to precise on 2012-03-12 (7 days ago) dmi.bios.date: 10/03/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0604 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9X79 DELUXE 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.:bvr0604:bd10/03/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP9X79DELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.7.0+bzr3035-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.30-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.1-0ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.1-0ubuntu5 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.99.901+git20120126-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/959275/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 1071389] [NEW] nvidia-current conflicts with fglrx (both cards present)
Public bug reported: I have primary AMD FirePro GPU for graphics and a secondary headless nVidia GTX 560Ti for OpenCL. In Ubuntu 12.04, it was possible to install both nvidia-current and fglrx alongside, and after adjusting alternatves for libGL.so, Xorg would happily use the first card, and nVidia was available for OpenCL computations. Since quantal, nvidia-current is conflicting with fglrx. While I can imagine this is intentional (most users won't ever need to install both), it is nevertheless a packaging bug. Please provide at least a workaround on how to install both drivers simultaneously. Version informations attached automatically (I hope). ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: nvidia-current (not installed) ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,compiztoolbox,resize,move,place,snap,gnomecompat,mousepoll,session,regex,wall,imgpng,grid,vpswitch,animation,expo,ezoom,workarounds,unitymtgrabhandles,fade,scale,unityshell] CompositorRunning: None Date: Thu Oct 25 18:09:17 2012 DistUpgraded: 2012-03-12 13:59:22,955 DEBUG icon theme changed, re-reading DistroCodename: quantal DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices [AMD] nee ATI Cayman PRO GL [FirePro V7900] [1002:6704] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:2b0c] NVIDIA Corporation GF114 [GeForce GTX 560 Ti] [10de:1200] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CardExpert Technology Device [10b0:0401] JockeyStatus: kmod:nvidia_experimental_304 - Experimental NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) kmod:fglrx - Video driver for the AMD graphics accelerators (Proprietary, Disabled, Not in use) kmod:nvidia_current - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) kmod:nvidia_current_updates - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) kmod:fglrx_updates - ATI Fire GL (Proprietary, Enabled, Not in use) MachineType: System manufacturer System Product Name MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=3cc5f6b9-69d1-4bb6-a9d0-93d506786ed9 ro nosplash nosplash SourcePackage: nvidia-graphics-drivers UpgradeStatus: Upgraded to quantal on 2012-03-12 (227 days ago) dmi.bios.date: 10/03/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0604 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9X79 DELUXE 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.:bvr0604:bd10/03/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP9X79DELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer modified.conffile..etc.modprobe.d.nvidia.current.hybrid.conf: [deleted] version.compiz: compiz 1:0.9.8.4-0ubuntu3 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: nvidia-graphics-drivers (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug quantal ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/1071389 Title: nvidia-current conflicts with fglrx (both cards present) Status in “nvidia-graphics-drivers” package in Ubuntu: New Bug description: I have primary AMD FirePro GPU for graphics and a secondary headless nVidia GTX 560Ti for OpenCL. In Ubuntu 12.04, it was possible to install both nvidia-current and fglrx alongside, and after adjusting alternatves for libGL.so, Xorg would happily use the first card, and nVidia was available for OpenCL computations. Since quantal, nvidia-current is conflicting with fglrx. While I can imagine this is intentional (most users won't ever need to install
[Desktop-packages] [Bug 415023] Re: brightness is broken on MSI WIND U100
This bug is still present at Mivvy M310 in 12.04. I am not sure which of the packages should be re-opened. I confirm that the workaround in #344 fixes the issue temporarily. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/415023 Title: brightness is broken on MSI WIND U100 Status in Gnome Powermanager: Expired Status in KDE Base Workspace: Invalid Status in Release Notes for Ubuntu: Fix Released Status in “gnome-settings-daemon” package in Ubuntu: New Status in “hal-info” package in Ubuntu: Fix Released Status in “kdebase-workspace” package in Ubuntu: Fix Released Status in “udev” package in Ubuntu: Fix Released Status in “xfce4-power-manager” package in Ubuntu: Invalid Status in “gnome-settings-daemon” source package in Lucid: New Status in “hal-info” source package in Lucid: Fix Released Status in “kdebase-workspace” source package in Lucid: Fix Released Status in “udev” source package in Lucid: Fix Released Status in “xfce4-power-manager” source package in Lucid: Invalid Status in Fedora: New Bug description: Binary package hint: gnome-power-manager Versions : karmic up to date (08-17-09) with gnome-power-manager version 2.27.5-0ubuntu2 What should happen : brightness should not flash. What happens : Brightness changing seems broken on my MSI wind U 100. First in GDM it starts flashing for a good 30 seconds and then the same problem happened when the Gnome session begins. Whenever I try to manually change the brightness a bit too fast (using the sliders or the keyboard) it start flashing again. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-power/+bug/415023/+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 936920] Re: [regression] default search engines are readded (keywords wiped) with upgrade
This bug keeps coming back. #858683 looks like a dupe of this, though it
has been marked as fix released. Using up-to-date 12.04.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/936920
Title:
[regression] default search engines are readded (keywords wiped) with
upgrade
Status in “firefox” package in Ubuntu:
Confirmed
Status in “iceweasel” package in Debian:
New
Bug description:
Original Bug:
https://bugs.launchpad.net/firefox/+bug/428306
i had detected, that the original search engines are added with an update!
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: firefox 10.0.2+build1-0ubuntu0.11.04.1
ProcVersionSignature: Ubuntu 2.6.38-13.55-generic 2.6.38.8
Uname: Linux 2.6.38-13-generic x86_64
NonfreeKernelModules: fglrx
AddonCompatCheckDisabled: False
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: frank 2290 F xfce4-volumed
/dev/snd/controlC0: frank 2290 F xfce4-volumed
frank 2302 F pulseaudio
BuildID: 20120216100510
CRDA: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden
Card0.Amixer.info:
Card hw:0 'SB'/'HDA ATI SB at 0xfe024000 irq 16'
Mixer name : 'Realtek ALC889A'
Components : 'HDA:10ec0885,1458a102,00100101'
Controls : 38
Simple ctrls : 21
Card1.Amixer.info:
Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfdffc000 irq 19'
Mixer name : 'ATI RS690/780 HDMI'
Components : 'HDA:1002791a,00791a00,0010'
Controls : 4
Simple ctrls : 1
Card1.Amixer.values:
Simple mixer control 'IEC958',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
Channel: release
Date: Mon Feb 20 13:10:15 2012
ForcedLayersAccel: False
IncompatibleExtensions:
Leo Search - ID={c666c018-6409-4479-afa3-68e4129e7eff}, Version=1.1.0,
minVersion=3.5, maxVersion=8.*, Location=app-profile, Type=extension, Active=Yes
NoScript - ID={73a6fe31-595d-460b-a920-fcc0f8843232}, Version=2.3,
minVersion=1.9a2, maxVersion=1.9.6, Location=app-profile, Type=extension,
Active=Yes
InstallationMedia: Xubuntu 10.04.2 Lucid Lynx - Release amd64 (20110215.1)
IpRoute:
192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.101 metric
1
169.254.0.0/16 dev eth0 scope link metric 1000
default via 192.168.0.1 dev eth0 proto static
IwConfig:
lono wireless extensions.
eth0 no wireless extensions.
vboxnet0 no wireless extensions.
ProcEnviron:
LANGUAGE=de_DE:en
LANG=de_DE.UTF-8
SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=10.0.2/20120216100510 (Running)
RfKill:
RunningIncompatibleAddons: True
SourcePackage: firefox
UpgradeStatus: Upgraded to natty on 2012-01-02 (48 days ago)
dmi.bios.date: 07/08/2010
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F7c
dmi.board.name: GA-MA790GP-UD4H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias:
dmi:bvnAwardSoftwareInternational,Inc.:bvrF7c:bd07/08/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA790GP-UD4H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA790GP-UD4H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-MA790GP-UD4H
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/936920/+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 953522] Re: nm-connection-editor: broadband editing impossible (No agents were available for this request)
*** This bug is a duplicate of bug 951464 *** https://bugs.launchpad.net/bugs/951464 ** This bug has been marked a duplicate of bug 951464 Wireless connections in network-manager-applet not editable -- 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/953522 Title: nm-connection-editor: broadband editing impossible (No agents were available for this request) Status in “network-manager-applet” package in Ubuntu: New Bug description: I can create a new mobile broadband connection in nm-connection-editor using the wizard, but when I try to look at it from the list of available connections (selecting the connection, clicking edit), I get dialog box Error initializing editor / No agents were available for this request. There are no messages in the terminal from which I run nm-connection-editor (besides bunch of css warnings). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager-gnome 0.9.2.0+git.20120126t000800.5151959-0ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9 Uname: Linux 3.2.0-18-generic x86_64 ApportVersion: 1.94.1-0ubuntu2 Architecture: amd64 Date: Mon Mar 12 23:49:41 2012 IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) IpRoute: default via 10.0.0.138 dev wlan0 proto static 10.0.0.0/24 dev wlan0 proto kernel scope link src 10.0.0.2 metric 2 169.254.0.0/16 dev wlan0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager-applet UpgradeStatus: Upgraded to precise on 2012-03-11 (1 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.3.0connected enabled enabled enabledenabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/953522/+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 844103] Re: /sbin not in $PATH
I have to dispute the package assignment. Running precise after upgrade from oneiric (which itself was an upgrade from debian stable, therefore perhaps with non-standard settings), I bumped into such problems. I notice /etc/profile sets /sbin and /usr/sbin only if `id -u` == 0, not for regular users, in case it might be related. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/844103 Title: /sbin not in $PATH Status in “gdm” package in Ubuntu: Confirmed Bug description: When I login in via gdm /sbin is not in my $PATH. 10:07:37 - flash:[~] echo $PATH /usr/local/bin:/usr/bin:/bin:/usr/games:/home/bdmurray/bin/:/home/bdmurray/bin/ However, if I ssh to my system it is set: 10:13:38 - flash:[~] ssh localhost bdmurray@localhost's password: bdmurray@flash:[~] echo $PATH /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games:/home/bdmurray/bin/ ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gdm 3.0.4-0ubuntu9 ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4 Uname: Linux 3.0.0-10-generic x86_64 Architecture: amd64 CheckboxSubmission: fee5e196cb921cbd36888f428b38b488 CheckboxSystem: 2a6f54df59af338184485e85cbcf0d32 Date: Wed Sep 7 10:06:24 2011 ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/zsh SourcePackage: gdm UpgradeStatus: Upgraded to oneiric on 2011-09-06 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/844103/+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 953522] [NEW] nm-connection-editor: broadband editing impossible (No agents were available for this request)
Public bug reported: I can create a new mobile broadband connection in nm-connection-editor using the wizard, but when I try to look at it from the list of available connections (selecting the connection, clicking edit), I get dialog box Error initializing editor / No agents were available for this request. There are no messages in the terminal from which I run nm-connection-editor (besides bunch of css warnings). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager-gnome 0.9.2.0+git.20120126t000800.5151959-0ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9 Uname: Linux 3.2.0-18-generic x86_64 ApportVersion: 1.94.1-0ubuntu2 Architecture: amd64 Date: Mon Mar 12 23:49:41 2012 IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) IpRoute: default via 10.0.0.138 dev wlan0 proto static 10.0.0.0/24 dev wlan0 proto kernel scope link src 10.0.0.2 metric 2 169.254.0.0/16 dev wlan0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager-applet UpgradeStatus: Upgraded to precise on 2012-03-11 (1 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.3.0connected enabled enabled enabledenabled enabled ** Affects: network-manager-applet (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise -- 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/953522 Title: nm-connection-editor: broadband editing impossible (No agents were available for this request) Status in “network-manager-applet” package in Ubuntu: New Bug description: I can create a new mobile broadband connection in nm-connection-editor using the wizard, but when I try to look at it from the list of available connections (selecting the connection, clicking edit), I get dialog box Error initializing editor / No agents were available for this request. There are no messages in the terminal from which I run nm-connection-editor (besides bunch of css warnings). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager-gnome 0.9.2.0+git.20120126t000800.5151959-0ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9 Uname: Linux 3.2.0-18-generic x86_64 ApportVersion: 1.94.1-0ubuntu2 Architecture: amd64 Date: Mon Mar 12 23:49:41 2012 IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) IpRoute: default via 10.0.0.138 dev wlan0 proto static 10.0.0.0/24 dev wlan0 proto kernel scope link src 10.0.0.2 metric 2 169.254.0.0/16 dev wlan0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager-applet UpgradeStatus: Upgraded to precise on 2012-03-11 (1 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.3.0connected enabled enabled enabledenabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/953522/+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 953522] Re: nm-connection-editor: broadband editing impossible (No agents were available for this request)
-- 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/953522 Title: nm-connection-editor: broadband editing impossible (No agents were available for this request) Status in “network-manager-applet” package in Ubuntu: New Bug description: I can create a new mobile broadband connection in nm-connection-editor using the wizard, but when I try to look at it from the list of available connections (selecting the connection, clicking edit), I get dialog box Error initializing editor / No agents were available for this request. There are no messages in the terminal from which I run nm-connection-editor (besides bunch of css warnings). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager-gnome 0.9.2.0+git.20120126t000800.5151959-0ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9 Uname: Linux 3.2.0-18-generic x86_64 ApportVersion: 1.94.1-0ubuntu2 Architecture: amd64 Date: Mon Mar 12 23:49:41 2012 IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) IpRoute: default via 10.0.0.138 dev wlan0 proto static 10.0.0.0/24 dev wlan0 proto kernel scope link src 10.0.0.2 metric 2 169.254.0.0/16 dev wlan0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager-applet UpgradeStatus: Upgraded to precise on 2012-03-11 (1 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.3.0connected enabled enabled enabledenabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/953522/+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
