[Desktop-packages] [Bug 969878] [NEW] Accidentaly refused access to desktop, now I can't reconnect the computer
Public bug reported: In the remote desktop viewer, I tried to connect 2 computers, and on the one that I wanted to connect to, I accidentally clicked refuse, and now I can't connect my computer to the one I clicked refuse on. Please help because my buddy needs help really bad and now I can't help him. ** Affects: vinagre (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vinagre in Ubuntu. https://bugs.launchpad.net/bugs/969878 Title: Accidentaly refused access to desktop, now I can't reconnect the computer Status in “vinagre” package in Ubuntu: New Bug description: In the remote desktop viewer, I tried to connect 2 computers, and on the one that I wanted to connect to, I accidentally clicked refuse, and now I can't connect my computer to the one I clicked refuse on. Please help because my buddy needs help really bad and now I can't help him. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vinagre/+bug/969878/+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 1376468] Re: Totem crashes attempting to play wmv file
I had this exact problem, all wmv files would crash in totem and vlc. I also had ffmpeg installed via jon-severinsson/ffmpeg. purging this and then updating to the official packages fixed the problem for me. -- 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/1376468 Title: Totem crashes attempting to play wmv file Status in “totem” package in Ubuntu: New Bug description: Totem segfaults when I attempt to open a wmv file. The same when Totem serves as video playback plugin in Firefox. I believe that this is some kind of dependency problem, because I have 2 additional Trusty machines, that do not experience the same problems. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: totem 3.10.1-1ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CurrentDesktop: Unity Date: Thu Oct 2 00:32:27 2014 InstallationDate: Installed on 2012-05-13 (871 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: totem UpgradeStatus: Upgraded to trusty on 2014-04-27 (156 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1376468/+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 1187889] [NEW] Empathy accounts window crashes when I click on my gmail account
Public bug reported: Running 12.04 LTS empathy 3.4.2.3-0ubuntu1 I expected to see the account information when I clicked on my gmail account Instead of that, the window closes itself rather quickly P.S. If I forgot anything, let me know (I am a NOOB when it comes to bug reporting) ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: empathy 3.4.2.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-45.70-generic 3.2.44 Uname: Linux 3.2.0-45-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.3 Architecture: amd64 Date: Wed Jun 5 14:06:21 2013 ExecutablePath: /usr/bin/empathy-accounts InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) MarkForUpload: True ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: empathy UpgradeStatus: Upgraded to precise on 2012-10-13 (235 days ago) ** Affects: empathy (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise running-unity -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1187889 Title: Empathy accounts window crashes when I click on my gmail account Status in “empathy” package in Ubuntu: New Bug description: Running 12.04 LTS empathy 3.4.2.3-0ubuntu1 I expected to see the account information when I clicked on my gmail account Instead of that, the window closes itself rather quickly P.S. If I forgot anything, let me know (I am a NOOB when it comes to bug reporting) ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: empathy 3.4.2.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-45.70-generic 3.2.44 Uname: Linux 3.2.0-45-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.3 Architecture: amd64 Date: Wed Jun 5 14:06:21 2013 ExecutablePath: /usr/bin/empathy-accounts InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) MarkForUpload: True ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: empathy UpgradeStatus: Upgraded to precise on 2012-10-13 (235 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1187889/+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 1577268] Re: Brasero can't find libdvdcss when going from Ubuntu 14.04 to 16.04
Could be related to the issue fixed with the patch associated with this pull request (included below)... https://github.com/GNOME/brasero/pull/3/commits/6a2b21f6823bb458ec9aea4278c6659c9d404f51 I've patched mine and the unpatched version shows the dvdcss plugin disabled (unchecked). With the patch the plugin is checked as enabled. In any event, I'm able to copy a dvd in Ubuntu 16.04 after applying the patch which, btw, just removes a check for a symbol which is no longer exported from the new version of libdvdcss.so.2 diff --git a/plugins/dvdcss/burn-dvdcss.c b/plugins/dvdcss/burn-dvdcss.c index 133b8d5..f6895b8 100644 --- a/plugins/dvdcss/burn-dvdcss.c +++ b/plugins/dvdcss/burn-dvdcss.c @@ -95,9 +95,6 @@ brasero_dvdcss_library_init (BraseroPlugin *plugin) if (!module) goto error_doesnt_exist; - if (!g_module_symbol (module, "dvdcss_interface_2", )) - goto error_version; - if (!g_module_symbol (module, "dvdcss_open", )) goto error_version; dvdcss_open = address; -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brasero in Ubuntu. https://bugs.launchpad.net/bugs/1577268 Title: Brasero can't find libdvdcss when going from Ubuntu 14.04 to 16.04 Status in brasero package in Ubuntu: In Progress Bug description: * Impact the libcss plugin can't be enable with the current libdvdcss version * Test case - install libdvdcss - start brasero - go to the plugins dialog, enable the libdvdcss plugin * Regression potential none, the plugin was not loading at all and it's only its loader being changed "I recently updated one of my rigs from 14.04 to 16.04. After upgrading Brasero tells me that it can't find libdvdcss. VLC play an inserted DVD, I see libdvdcss in /usr/lib/x86_64-linux gnu. However, i didn't see it simply in /usr/lib/ so I created a link there. Still didn't work, so I copied an older libdvdcss to /usr/lib. Still no joy. I checked to see what versions of libdvdcss I had installed - 2.2.0 in /usr/lib/x86_64-linux, 2.1.0 in /usr/lib * mv'ed the.2.1.0 to x86_64-linux * rm'ed the sym links to 2.2.0 * new sym link to 2.1.0 * works. " Originally reported here : https://www.reddit.com/r/Ubuntu/comments/4h4pcn/anybody_using_brasero_to_rip_dvds_in_1604/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/1577268/+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 1877735] Re: Video playback is choppy [Haswell 1080p]
Found it!!! A long time ago I installed an app called indicator-multiload that runs in the top right of the menu bar. I happened to turn it off and the video started running better. I have now uninstalled it and videos are playing normally again. I'm not sure the process, but this bug can be closed! Thank you so much for your help, Travis Keenan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1877735 Title: Video playback is choppy [Haswell 1080p] Status in gnome-shell package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: After upgrade from 19.10 to 20.04 video playback is choppy ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-7626.30~1588169883~20.04~bbe668a~dev-generic 5.4.30 Uname: Linux 5.4.0-7626-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 9 06:43:40 2020 DistUpgraded: 2020-05-08 18:55:15,812 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] MachineType: System76, Inc. Wild Dog Performance ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-7626-generic root=UUID=6ce8ac8b-f6ef-47b4-9428-b35e00870dfa ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-05-08 (0 days ago) dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0806 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: wilp10 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0806:bd01/20/2014:svnSystem76,Inc.:pnWildDogPerformance:pvrwilp10:rvnASUSTeKCOMPUTERINC.:rnH87-PLUS:rvrRevX.0x:cvnSystem76,Inc.:ct3:cvrwilp10: dmi.product.family: ASUS MB dmi.product.name: Wild Dog Performance dmi.product.sku: All dmi.product.version: wilp10 dmi.sys.vendor: System76, Inc. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2014-05-27T19:28:01.524954 version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Thu Nov 9 16:56:44 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1.3 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1877735/+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 1877735] Re: Video playback is choppy [Haswell 1080p]
I'm pretty certain that I don't have any extensions active. I'm attaching a picture of the extensions app. ** Attachment added: "Extentions_2020-0-14 14-03-21.png" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1877735/+attachment/5371701/+files/Extentions_2020-0-14%2014-03-21.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1877735 Title: Video playback is choppy [Haswell 1080p] Status in gnome-shell package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: After upgrade from 19.10 to 20.04 video playback is choppy ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-7626.30~1588169883~20.04~bbe668a~dev-generic 5.4.30 Uname: Linux 5.4.0-7626-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 9 06:43:40 2020 DistUpgraded: 2020-05-08 18:55:15,812 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] MachineType: System76, Inc. Wild Dog Performance ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-7626-generic root=UUID=6ce8ac8b-f6ef-47b4-9428-b35e00870dfa ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-05-08 (0 days ago) dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0806 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: wilp10 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0806:bd01/20/2014:svnSystem76,Inc.:pnWildDogPerformance:pvrwilp10:rvnASUSTeKCOMPUTERINC.:rnH87-PLUS:rvrRevX.0x:cvnSystem76,Inc.:ct3:cvrwilp10: dmi.product.family: ASUS MB dmi.product.name: Wild Dog Performance dmi.product.sku: All dmi.product.version: wilp10 dmi.sys.vendor: System76, Inc. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2014-05-27T19:28:01.524954 version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Thu Nov 9 16:56:44 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1.3 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1877735/+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 1877735] Re: Video playback is choppy [Haswell 1080p]
I have removed the System76 extension and the problem persists. I'm attaching an updated picture of my extensions. ** Attachment added: "Extentioins_2_020-05-14 14-35-42.png" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1877735/+attachment/5371713/+files/Extentioins_2_020-05-14%2014-35-42.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1877735 Title: Video playback is choppy [Haswell 1080p] Status in gnome-shell package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: After upgrade from 19.10 to 20.04 video playback is choppy ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-7626.30~1588169883~20.04~bbe668a~dev-generic 5.4.30 Uname: Linux 5.4.0-7626-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 9 06:43:40 2020 DistUpgraded: 2020-05-08 18:55:15,812 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] MachineType: System76, Inc. Wild Dog Performance ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-7626-generic root=UUID=6ce8ac8b-f6ef-47b4-9428-b35e00870dfa ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-05-08 (0 days ago) dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0806 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: wilp10 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0806:bd01/20/2014:svnSystem76,Inc.:pnWildDogPerformance:pvrwilp10:rvnASUSTeKCOMPUTERINC.:rnH87-PLUS:rvrRevX.0x:cvnSystem76,Inc.:ct3:cvrwilp10: dmi.product.family: ASUS MB dmi.product.name: Wild Dog Performance dmi.product.sku: All dmi.product.version: wilp10 dmi.sys.vendor: System76, Inc. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2014-05-27T19:28:01.524954 version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Thu Nov 9 16:56:44 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1.3 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1877735/+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 1877735] Re: Video playback is choppy [Haswell 1080p]
This is top running for a little more than 5 minutes while a video had been playing. top - 09:39:50 up 4 days, 1:00, 1 user, load average: 0.74, 0.89, 0.84 Tasks: 282 total, 2 running, 280 sleeping, 0 stopped, 0 zombie %Cpu(s): 20.5 us, 2.0 sy, 0.0 ni, 72.7 id, 1.1 wa, 0.0 hi, 3.7 si, 0.0 st MiB Mem : 19894.7 total, 2133.6 free, 3532.8 used, 14228.3 buff/cache MiB Swap: 4096.0 total, 3799.0 free,297.0 used. 14242.4 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 2925 keenanti 20 0 6491344 1.4g 154680 R 51.8 7.3 1416:49 gnome-shell 54922 keenanti 20 0 5145876 392000 149640 S 23.3 1.9 4:39.67 brave 3572 keenanti 20 0 979420 333424 163968 S 9.0 1.6 657:55.80 brave 2700 keenanti 20 0 457728 19972 10312 S 3.3 0.1 106:43.25 Xorg 2620 keenanti 20 0 1941788 12244 9468 S 2.0 0.1 21:26.19 pulseaudio 3086 keenanti 20 0 806552 24996 13516 S 1.3 0.1 73:35.05 indicator-multi 3434 keenanti 20 0 2537540 479092 287396 S 1.3 2.4 89:10.10 brave 3687 keenanti 20 0 9394220 396764 106992 S 0.7 1.9 50:12.55 brave 55148 keenanti 20 0 959084 50208 37492 S 0.7 0.2 0:01.28 gnome-terminal- 1709 root 20 0 2441408 52456 13684 S 0.3 0.3 5:53.60 Plex Media Serv 2250 root 20 0 435488 2244 2244 S 0.3 0.0 0:10.21 Plex Tuner Serv 3660 keenanti 20 0 4899272 105788 34376 S 0.3 0.5 3:49.28 brave 55169 keenanti 20 0 12196 4072 3360 R 0.3 0.0 0:00.81 top 1 root 20 0 169756 10068 5304 S 0.0 0.0 2:16.78 systemd -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1877735 Title: Video playback is choppy [Haswell 1080p] Status in gnome-shell package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: After upgrade from 19.10 to 20.04 video playback is choppy ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-7626.30~1588169883~20.04~bbe668a~dev-generic 5.4.30 Uname: Linux 5.4.0-7626-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 9 06:43:40 2020 DistUpgraded: 2020-05-08 18:55:15,812 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] MachineType: System76, Inc. Wild Dog Performance ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-7626-generic root=UUID=6ce8ac8b-f6ef-47b4-9428-b35e00870dfa ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-05-08 (0 days ago) dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0806 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: wilp10 dmi.modalias:
[Desktop-packages] [Bug 1874567] Re: [nvidia] Rotating secondary monitor to portrait fails, results in landscape
What's the status for Ubuntu Focal? How can I help to emphasize the importance of backporting the fix to the stable release? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1874567 Title: [nvidia] Rotating secondary monitor to portrait fails, results in landscape Status in OEM Priority Project: New Status in gnome-control-center package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-435 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-440 package in Ubuntu: Won't Fix Status in gnome-control-center source package in Focal: Won't Fix Status in mutter source package in Focal: Fix Committed Status in nvidia-graphics-drivers-340 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-435 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-440 source package in Focal: Won't Fix Bug description: [ Impact ] I have two monitors, with the secondary one rotated in a portrait orientation. Using the nvidia 440 drivers, the orientation is not applied when configuring in gnome settings (the displays go blank for a second, and then reappear in landscape orientation). Using nvidia settings, I can set the monitor rotation and offset correctly, however these settings do not persist on next boot (even when selecting to save to xorg.conf). When using the nouveau drivers, the orientation is applied correctly in gnome settings, and is persisted. [ Test case ] 1. Install nvidia drivers 2. Configure an external monitor to be in portrait mode in gnome-control-center 3. Apply the configuration 4. Expect configuration is properly working [ Regression potential ] Wrong screen size is set and panning is used. ProblemType: BugDistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME Date: Fri Apr 24 08:30:41 2020 DistUpgraded: 2020-04-20 18:27:13,972 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-26-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GK106 [GeForce GTX 660] [1462:2871] InstallationDate: Installed on 2018-05-01 (723 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Shuttle Inc. SZ77 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=d2c17cee-7c37-429f-9cbb-9484a159f182 ro quiet splash vt.handoff=7SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-20 (3 days ago) dmi.bios.date: 10/13/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.13 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: FZ77 dmi.board.vendor: Shuttle Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.13:bd10/13/2014:svnShuttleInc.:pnSZ77:pvr1.0:rvnShuttleInc.:rnFZ77:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: SZ77 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Shuttle Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
Re: [Desktop-packages] [Bug 1874217] Re: [nvidia] Dual monitor setup with secondary monitor in portrait-right mode cause tiled windows to occupy 1.5 monitors
@daniel: I have 2 extra DVI to HDMI adapters that I would be happy to ship to you if it would help in solving this issue. My DMs are open on Twitter (@travisdieckmann) if you’d like to let me know where I can ship them. On Wed, Jun 17, 2020 at 1:05 PM Peter Klaesson <1874...@bugs.launchpad.net> wrote: > @Daniel: Sounds like something you should be able to have access too if > you are assigned to test this. > > Do you have any thought about how it could be solved? I mean, you need a > new card or an adapter(?) for your current card? > > I have no idea how this works for you financially. Can you get what you > need and get the expenses covered by Canonical? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1874217 > > Title: > [nvidia] Dual monitor setup with secondary monitor in portrait-right > mode cause tiled windows to occupy 1.5 monitors > > Status in gnome-control-center: > Unknown > Status in Mutter: > Unknown > Status in gnome-control-center package in Ubuntu: > Triaged > Status in mutter package in Ubuntu: > Confirmed > > Bug description: > I'm on Ubuntu 20.04 AMD64 fully up to date and freshly rebooted. > > I use dual screen : the main screen is on the left side (32"), the > secondary screen (19") is at right and in portrait mode (rotated > right). The window are improperly growed : they extend from full main > screen to half the "witdh" of the secondary screen. Additionnally, the > « pop-up » menus (eg. from settings) do not appear at the right place > (see screen capture in comment). The problem disappears if I revert > the orientation of secondary screen from « portrait turned right » to > « landscape ». I do have gnome-shell-extension-ubuntu-dock in version > 67ubuntu20.04.5, but still got the problem. > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: gnome-shell 3.36.1-5ubuntu1 > ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 > Uname: Linux 5.4.0-26-generic x86_64 > NonfreeKernelModules: nvidia_modeset nvidia > ApportVersion: 2.20.11-0ubuntu27 > Architecture: amd64 > CasperMD5CheckResult: skip > CurrentDesktop: ubuntu:GNOME > Date: Wed Apr 22 11:11:25 2020 > DisplayManager: gdm3 > InstallationDate: Installed on 2020-04-19 (2 days ago) > InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=fr_FR.UTF-8 >SHELL=/bin/bash > RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 > SourcePackage: gnome-shell > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/gnome-control-center/+bug/1874217/+subscriptions > -- Best regards, Travis Dieckmann Ph: 317-341-2727 tadieckm...@gmail.com -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1874217 Title: [nvidia] Dual monitor setup with secondary monitor in portrait-right mode cause tiled windows to occupy 1.5 monitors Status in gnome-control-center: Unknown Status in Mutter: Unknown Status in gnome-control-center package in Ubuntu: Triaged Status in mutter package in Ubuntu: Confirmed Bug description: I'm on Ubuntu 20.04 AMD64 fully up to date and freshly rebooted. I use dual screen : the main screen is on the left side (32"), the secondary screen (19") is at right and in portrait mode (rotated right). The window are improperly growed : they extend from full main screen to half the "witdh" of the secondary screen. Additionnally, the « pop-up » menus (eg. from settings) do not appear at the right place (see screen capture in comment). The problem disappears if I revert the orientation of secondary screen from « portrait turned right » to « landscape ». I do have gnome-shell-extension-ubuntu-dock in version 67ubuntu20.04.5, but still got the problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 22 11:11:25 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-19 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR=
[Desktop-packages] [Bug 1874217] Re: [nvidia] Dual monitor setup with secondary monitor in portrait-right mode cause tiled windows to occupy 1.5 monitors
I have confirmed Liang's comment#27 This solution does work and persists restart and screen locks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1874217 Title: [nvidia] Dual monitor setup with secondary monitor in portrait-right mode cause tiled windows to occupy 1.5 monitors Status in gnome-control-center: Unknown Status in Mutter: Unknown Status in gnome-control-center package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I'm on Ubuntu 20.04 AMD64 fully up to date and freshly rebooted. I use dual screen : the main screen is on the left side (32"), the secondary screen (19") is at right and in portrait mode (rotated right). The window are improperly growed : they extend from full main screen to half the "witdh" of the secondary screen. Additionnally, the « pop-up » menus (eg. from settings) do not appear at the right place (see screen capture in comment). The problem disappears if I revert the orientation of secondary screen from « portrait turned right » to « landscape ». I do have gnome-shell-extension-ubuntu-dock in version 67ubuntu20.04.5, but still got the problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 22 11:11:25 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-19 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1874217/+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 793960] Re: network manager duplicates connections in natty
I've quit using the HP mini 110 toy-computer and purchased a 13 laptop with proper computing functionality, so I can't say, but am using Kubuntu 12.04 on the new one; as soon as I can plug in the external wireless adapter, I'll post the results! -- 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/793960 Title: network manager duplicates connections in natty Status in “network-manager” package in Ubuntu: Triaged Bug description: Binary package hint: network-manager I'm a bit of a newbie, but I'll detail as much as I can, and post any additional info you may require. I just upgraded from Lucid to Natty on my HP mini-110. I have two network cards: - Ralink rt3090pci - External usb Realtek rtl8187 Rtl8187 works fine. Ralink was using the rt2800pci drivers, and working only sporadically (worked fine after installation. On next reboot, connection was somewhat slower, and on the following, it manages to connect, but hardly no data transfer takes place, and it's impossible to view any webpage. In between these two reboots, all I've done is install software: ubuntu-restricted-extras, dropbox, skype and a few others. No system updates. I have currently blacklisted rt2800pci, rt2x00lib and rt2x00pci. The system is using the rt2860 drivers, but internet works fine. The problem is that network connections are duplicated. The connection home_wifi, for instance, shows up 3 times in network manager: twice with the signal strength corresponding to the internal pci card, and once with the signal strength it gets from the usb rtl8187. One of these connections works for the rt2869, and one for the rtl8187. If I click on the third one (it's hard to tell which one sometimes), it asks me for the connection password, and duplicates the connection again (now I have 4 home_wifi). If there's any more info I can provide, please let me know. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: network-manager 0.8.4~git.20110319t175609.d14809b-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 Architecture: amd64 CRDA: Error: [Errno 2] No such file or directory Date: Tue Jun 7 12:29:50 2011 Gconf: IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Kubuntu 11.04 Natty Narwhal - Release amd64 (20110427) IpRoute: 192.168.0.0/24 dev wlan1 proto kernel scope link src 192.168.0.196 metric 2 169.254.0.0/16 dev wlan1 scope link metric 1000 default via 192.168.0.1 dev wlan1 proto static Keyfiles: Error: [Errno 2] No such file or directory NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: LANGUAGE= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/793960/+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 1048373] [NEW] No option to remain in one filesystem
Public bug reported: I used sshfs to mount a remote filesystem in my home directory and it was backed up by Deja-Dup. I should, of course, have added the mount- point in my home directory to the exclude list, but I didn't realise until the backup had been running for hours and many GB had been downloaded on my ADSL connection from the remote SSHFS fileserver I was connected to. It would be useful if there was an option for Deja_Dup to remain in one filesystem during a backup to avoid this type of problem. ** Affects: deja-dup (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1048373 Title: No option to remain in one filesystem Status in “deja-dup” package in Ubuntu: New Bug description: I used sshfs to mount a remote filesystem in my home directory and it was backed up by Deja-Dup. I should, of course, have added the mount-point in my home directory to the exclude list, but I didn't realise until the backup had been running for hours and many GB had been downloaded on my ADSL connection from the remote SSHFS fileserver I was connected to. It would be useful if there was an option for Deja_Dup to remain in one filesystem during a backup to avoid this type of problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1048373/+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 1048501] Re: The main task bar at the top of my desktop has disapeared how do i get it back?
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1048501 Title: The main task bar at the top of my desktop has disapeared how do i get it back? Status in “nautilus” package in Ubuntu: New Bug description: The main task bar at the top of my desktop has disapeared how do i get it back? i updated my ati graphics driver and now its g one ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: nautilus 1:2.32.2.1-0ubuntu13 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic i686 NonfreeKernelModules: fglrx Architecture: i386 Date: Mon Sep 10 08:43:25 2012 ExecutablePath: /usr/bin/nautilus InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1048501/+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 1048501] [NEW] The main task bar at the top of my desktop has disapeared how do i get it back?
Public bug reported: The main task bar at the top of my desktop has disapeared how do i get it back? i updated my ati graphics driver and now its g one ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: nautilus 1:2.32.2.1-0ubuntu13 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic i686 NonfreeKernelModules: fglrx Architecture: i386 Date: Mon Sep 10 08:43:25 2012 ExecutablePath: /usr/bin/nautilus InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug apport-lpi i386 natty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1048501 Title: The main task bar at the top of my desktop has disapeared how do i get it back? Status in “nautilus” package in Ubuntu: New Bug description: The main task bar at the top of my desktop has disapeared how do i get it back? i updated my ati graphics driver and now its g one ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: nautilus 1:2.32.2.1-0ubuntu13 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic i686 NonfreeKernelModules: fglrx Architecture: i386 Date: Mon Sep 10 08:43:25 2012 ExecutablePath: /usr/bin/nautilus InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1048501/+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 819321] Re: apparmor profile for telepathy need c-mask.
Although this bug is fixed, the same symptoms appear when using the
default apparmor configuration if user accounts are not stored in /home.
For example, if accounts are stored in /homes this path needs to be
added to the apparmour configuration:
--- /etc/apparmor.d/tunables/.old/home 2012-06-05 08:27:07.0 +0100
+++ /etc/apparmor.d/tunables/home 2012-11-02 00:40:15.658640991 +
@@ -18,7 +18,7 @@
# @{HOMEDIRS} is a space-separated list of where user home directories
# are stored, for programs that must enumerate all home directories on a
# system.
-@{HOMEDIRS}=/home/
+@{HOMEDIRS}=/home/ /homes/
# Also, include files in tunables/home.d for site-specific adjustments to
# @{HOMEDIRS}.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to telepathy-mission-control-5 in Ubuntu.
https://bugs.launchpad.net/bugs/819321
Title:
apparmor profile for telepathy need c-mask.
Status in “telepathy-mission-control-5” package in Ubuntu:
Fix Released
Bug description:
Current apparmor profile for telepathy assume that files and folders
do exist in user home folder and allow only read and write mask. In
case it is new use, this profile need creation mask. Here dmesg i get:
[11708.341078] type=1400 audit(1312193946.941:18): apparmor=DENIED
operation=mkdir parent=1 profile=/usr/lib/telepathy/telepathy-*
name=/home/lex/.cache/wocky/ pid=2836 comm=telepathy-gabbl
requested_mask=c denied_mask=c fsuid=1000 ouid=1000
[26194.609075] type=1400 audit(1312208433.209:23): apparmor=DENIED
operation=mkdir parent=1 profile=/usr/lib/telepathy/telepathy-*
name=/home/lex/.local/share/TpLogger/ pid=2828 comm=telepathy-
logge requested_mask=c denied_mask=c fsuid=1000 ouid=1000
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: telepathy-mission-control-5 1:5.9.0-1ubuntu4
ProcVersionSignature: Ubuntu 3.0.0-7.9-generic-pae 3.0.0
Uname: Linux 3.0.0-7-generic-pae i686
Architecture: i386
Date: Mon Aug 1 16:17:51 2011
InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Alpha i386 (20110705.1)
ProcEnviron:
LANG=de_DE.UTF-8
SHELL=/bin/bash
SourcePackage: telepathy-mission-control-5
UpgradeStatus: Upgraded to oneiric on 2011-07-31 (1 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/819321/+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 1075004] [NEW] package gnome-screensaver 3.6.0-0ubuntu2 failed to install/upgrade: package gnome-screensaver is already installed and configured
Public bug reported: I don't know ProblemType: Package DistroRelease: Ubuntu 12.10 Package: gnome-screensaver 3.6.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Sun Nov 4 18:04:31 2012 ErrorMessage: package gnome-screensaver is already installed and configured GnomeSessionIdleInhibited: Unknown GnomeSessionInhibitors: Failed to acquire GsettingsGnomeSession: org.gnome.desktop.session idle-delay uint32 600 org.gnome.desktop.session session-name 'ubuntu' InstallationDate: Installed on 2012-11-04 (0 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: gnome-screensaver Title: package gnome-screensaver 3.6.0-0ubuntu2 failed to install/upgrade: package gnome-screensaver is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package quantal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1075004 Title: package gnome-screensaver 3.6.0-0ubuntu2 failed to install/upgrade: package gnome-screensaver is already installed and configured Status in “gnome-screensaver” package in Ubuntu: New Bug description: I don't know ProblemType: Package DistroRelease: Ubuntu 12.10 Package: gnome-screensaver 3.6.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Sun Nov 4 18:04:31 2012 ErrorMessage: package gnome-screensaver is already installed and configured GnomeSessionIdleInhibited: Unknown GnomeSessionInhibitors: Failed to acquire GsettingsGnomeSession: org.gnome.desktop.session idle-delay uint32 600 org.gnome.desktop.session session-name 'ubuntu' InstallationDate: Installed on 2012-11-04 (0 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: gnome-screensaver Title: package gnome-screensaver 3.6.0-0ubuntu2 failed to install/upgrade: package gnome-screensaver is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1075004/+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 978789] Re: file-roller crashed with SIGABRT in __libc_message()
file-roller into quantal-proposed: confirmed working. Thanks! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/978789 Title: file-roller crashed with SIGABRT in __libc_message() Status in File Roller: Fix Released Status in “file-roller” package in Ubuntu: Fix Released Status in “file-roller” source package in Quantal: Fix Committed Bug description: Impact: It's not possible to extract archives in a specific location, the code segfaults Test Case: - wget http://ftp.acc.umu.se/pub/GNOME/sources/gedit/3.6/gedit-3.6.2.tar.xz - run file-roller --extract-to /tmp/debug gedit-3.6.2.tar.xz - ls /tmp/debug the archive should be properly unpacked in the destination dir Regression potential: Check that archives get correct unpacked still, from nautilus and from the command line To manage notifications about this bug go to: https://bugs.launchpad.net/file-roller/+bug/978789/+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 869766] Re: empathy crashed with signal 5 in g_main_context_new()
Swen, can you reproduce this easily, or did it just happen once? Which versions of evolution-data-server, libfolks, and libfolks-eds are you running Empathy against? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/869766 Title: empathy crashed with signal 5 in g_main_context_new() Status in Chat app, and Telepathy user interface: New Status in “empathy” package in Ubuntu: New Bug description: Happend right after autostart. ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: empathy 3.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 1.23-0ubuntu2 Architecture: amd64 CrashCounter: 1 Date: Fri Oct 7 08:52:00 2011 ExecutablePath: /usr/bin/empathy InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20110901) ProcCmdline: empathy Signal: 5 SourcePackage: empathy StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_context_new () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_dbus_connection_send_message_with_reply_sync () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: empathy crashed with signal 5 in g_main_context_new() UpgradeStatus: Upgraded to oneiric on 2011-09-29 (7 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/empathy/+bug/869766/+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 869766] Re: empathy crashed with signal 5 in g_main_context_new()
Also, please install the glib debug package to get a more-complete stack trace, then post it here (or in the upstream bug). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/869766 Title: empathy crashed with signal 5 in g_main_context_new() Status in Chat app, and Telepathy user interface: New Status in “empathy” package in Ubuntu: New Bug description: Happend right after autostart. ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: empathy 3.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 1.23-0ubuntu2 Architecture: amd64 CrashCounter: 1 Date: Fri Oct 7 08:52:00 2011 ExecutablePath: /usr/bin/empathy InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20110901) ProcCmdline: empathy Signal: 5 SourcePackage: empathy StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_context_new () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_dbus_connection_send_message_with_reply_sync () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: empathy crashed with signal 5 in g_main_context_new() UpgradeStatus: Upgraded to oneiric on 2011-09-29 (7 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/empathy/+bug/869766/+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 785822] Re: Banshee does not remove selected song from playlist
Still seeing this in Ubuntu 11.10 and Banshee 2.2.1. I am unable to remove the desired songs from my playlists. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to banshee in Ubuntu. https://bugs.launchpad.net/bugs/785822 Title: Banshee does not remove selected song from playlist Status in Banshee Music Player: New Status in “banshee” package in Ubuntu: Triaged Bug description: Binary package hint: banshee I have several playlists in Banshee (both static and smart). Lately, I noticed that Banshee does not always remove the selected item from static playlist, instead it removes a random item. If you try to remove song that is playing, it always stays on the playlist and instead _ another_ song is removed. That to me is really unwanted behaviour. However, even if you are playing songs from playlist1, you sometimes cannot remove a songs from playlist2. And I mean the static playlists here where you add and remove items manually. I have not found clear logic on when the selected song can be removed. Only one case is clear: when you're playing songs in order (no shuffle), you can remove selected song after 4-5 songs have been played from begin to end after the one you want to remove. However, most often when you try to remove a song from static playlist, some song is removed -usually not the one you want. I am using 10.10 Ubuntu and Banshee 1.8.1. To manage notifications about this bug go to: https://bugs.launchpad.net/banshee/+bug/785822/+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 990904] Re: Dual monitor problem after upgrade to 12.04
I also have the same issue on an HP EliteBook 8540p ... it has a discrete NVIDIA video card. I cannot use the mouse pad or a plugged in mouse; however, the mouse clicks click the right side of the window while being stuck on the left side, the second monitor is configured to sit left of the main. -- 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/990904 Title: Dual monitor problem after upgrade to 12.04 Status in “xorg-server” package in Ubuntu: Confirmed Bug description: The issue started immediately after upgrading to 12.04. I use a Toshiba Satellite A100-906 with LG W1934S as an external monitor. When I disconnect the external monitor, the mouse pointer gets stuck at the vertical side edge of the notebook's display, only moving vertically. Moreover, when I try to switch to the virtual consoles, instead of consoles. blank screens appear. This does not happen when the external monitor is connected. I use the same xorg.conf with 11.10. It occurs with lightdm, lxdm and kdm. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.0-24-generic i686 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Είναι κατάλογος: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86 Kernel Module 295.40 Thu Apr 5 21:28:09 PDT 2012 GCC version: gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ApportVersion: 2.0.1-0ubuntu7 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: kwin CurrentDmesg: [ 37.440033] eth0: no IPv6 routers present Date: Sun Apr 29 07:28:11 2012 DistUpgraded: 2012-04-27 07:57:05,741 DEBUG enabling apt cron job DistroCodename: precise DistroVariant: ubuntu DkmsStatus: nvidia-current, 295.40, 3.0.0-17-generic, i686: installed nvidia-current, 295.40, 3.0.0-19-generic, i686: installed nvidia-current, 295.40, 3.2.0-24-generic, i686: installed nvidia-current-updates, 295.40, 3.2.0-24-generic, i686: installed ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu GraphicsCard: NVIDIA Corporation G73 [GeForce Go 7600] [10de:0398] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:ff10] InstallationMedia: Lubuntu 11.10 Oneiric Ocelot - Release i386 (20111012) JockeyStatus: xorg:nvidia_current - NVIDIA accelerated graphics driver (Proprietary, Disabled, Not in use) pkg:sl-modem-daemon - Software modem (Proprietary, Disabled, Not in use) xorg:nvidia_current_updates - NVIDIA accelerated graphics driver (post-release updates) (Proprietary, Enabled, In use) MachineType: TOSHIBA SATELLITE A100 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=el_GR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic root=UUID=b16c53fa-5a22-4770-9bd3-a5b2787dc1b7 ro rootflags=data=writeback SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to precise on 2012-04-27 (1 days ago) dmi.bios.date: 07/12/2007 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: CAPELL VALLEY(NAPA) CRB dmi.board.vendor: Intel Corporation dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/12/2007:svnTOSHIBA:pnSATELLITEA100:pvrPSAA9E-0R201SGE:rvnIntelCorporation:rnCAPELLVALLEY(NAPA)CRB:rvrNotApplicable:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: SATELLITE A100 dmi.product.version: PSAA9E-0R201SGE dmi.sys.vendor: TOSHIBA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/990904/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 873058] Re: Jockey fails to install binary ati driver (post release) version
I can confirm that the released fix does not fix this bug on 12.04. Jockey version 0.9.7-0ubuntu76 in 12.04 proposed is completly un-usable. Please see the attached file for the console output errors. It has been 8 months since 12.04, a long term release, has been in use. This highly visible bug has been an eyesore for the entire time. Is this being looked at? ** Attachment added: jockey_0.9.7-0ubuntu76.txt https://bugs.launchpad.net/ubuntu/+source/nvidia-common/+bug/873058/+attachment/3469584/+files/jockey_0.9.7-0ubuntu76.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/873058 Title: Jockey fails to install binary ati driver (post release) version Status in AMD fglrx video driver: Confirmed Status in “jockey” package in Ubuntu: Fix Released Status in “nvidia-common” package in Ubuntu: Fix Released Status in “jockey” source package in Oneiric: Fix Committed Status in “nvidia-common” source package in Oneiric: Fix Committed Status in “jockey” source package in Precise: Fix Released Status in “nvidia-common” source package in Precise: Fix Released Bug description: I do a fresh 64bit install and then try and add the binary drivers from jockey. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: jockey-gtk 0.9.4-0ubuntu10 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Wed Oct 12 21:04:58 2011 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111011) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 002: ID 0557:8021 ATEN International Co., Ltd Bus 002 Device 003: ID 04f3:0103 Elan Microelectronics Corp. Bus 002 Device 004: ID 04f2:0718 Chicony Electronics Co., Ltd MachineType: System manufacturer System Product Name PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic root=UUID=491d192c-c7fe-48f5-acb4-10f6cfb63d9e ro quiet splash vt.handoff=7 SourcePackage: jockey UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/23/2006 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS K8N4-E SE ACPI BIOS Revision 0106 dmi.board.name: K8N4-E SE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 1.XX dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSK8N4-ESEACPIBIOSRevision0106:bd01/23/2006:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnK8N4-ESE:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/fglrx/+bug/873058/+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 1362633] [NEW] Corrupted Mouse Cursor on primary monitor in dual-monitor KDE
Public bug reported: When moving the mouse from the secondary (right) monitor to primary (left) monitor, the cursor often becomes corrupted on the primary monitor, as seen in https://bugs.launchpad.net/ubuntu/+source/xserver- xorg-video-ati/+bug/360724 The cursor appears corrupted thereafter, but only on the primary monitor - it appears normal on the secondary. This does not always happen the first time the boundary is crossed from secondary to primary, but once it does occur, it persists until X.Org is restarted. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: kwin CurrentDesktop: KDE Date: Thu Aug 28 09:05:05 2014 DistUpgraded: 2014-04-21 09:55:42,938 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: kubuntu ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cedar GL [FirePro 2270] [1002:68f2] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0126] MachineType: Dell Inc. Precision T3600 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic root=UUID=dce226de-16b4-4a7d-9232-c11bc0c5d9f7 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-04-21 (128 days ago) dmi.bios.date: 05/11/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 0PTTT9 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA13:bd05/11/2014:svnDellInc.:pnPrecisionT3600:pvr01:rvnDellInc.:rn0PTTT9:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision T3600 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 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 1:1.0.10-1ubuntu2 xserver.bootTime: Thu Aug 21 16:56:20 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: fglrx(0): atiddxDriScreenInit failed. Probably kernel module missing or incompatible. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2 xserver.video_driver: fglrx ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kubuntu trusty -- 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/1362633 Title: Corrupted Mouse Cursor on primary monitor in dual-monitor KDE Status in “xorg” package in Ubuntu: New Bug description: When moving the mouse from the secondary (right) monitor to primary (left) monitor, the cursor often becomes corrupted on the primary monitor, as seen in https://bugs.launchpad.net/ubuntu/+source/xserver- xorg-video-ati/+bug/360724 The cursor appears corrupted thereafter, but only on the primary monitor - it appears normal on the secondary. This does not always happen the first time the boundary is crossed from secondary to primary, but once it does occur, it persists until X.Org is restarted. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: kwin CurrentDesktop: KDE Date: Thu Aug 28 09:05:05 2014 DistUpgraded: 2014-04-21 09:55:42,938 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: kubuntu ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cedar GL [FirePro 2270] [1002:68f2] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0126] MachineType: Dell Inc. Precision T3600 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic root=UUID=dce226de-16b4-4a7d-9232-c11bc0c5d9f7 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-04-21 (128 days ago) dmi.bios.date: 05/11/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 0PTTT9 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Desktop-packages] [Bug 360724] Re: [RV515] Kubuntu: Corrupted mouse cursor after moving between screens
I am also experiencing this bug on several Kubuntu machines, and have submitted a detailed bug as requested here: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1362633 -- 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/360724 Title: [RV515] Kubuntu: Corrupted mouse cursor after moving between screens Status in “xserver-xorg-video-ati” package in Ubuntu: Incomplete Bug description: On two machines, I've experienced a corrupted cursor. The cursor image seems to be 'cut in slices' and put back in the wrong order. The corruption is not easy to reproduce. When it does happen, it seems to happen after moving of the cursor between the different monitors. Configuration of the two machines: - Both machines have a dual screen setup. - Both machines are Dell desktops with an ATI graphics card. - Machine 1 has a R500 graphics chip, machine 2 a R600 graphics chip. I've seen the corruption on Intrepid and Jaunty. The Intrepid installations were running KDE 4.2 from PPA. The Jaunty installation was at beta. The problem occurs with different drivers, both fglrx and xf86-video- ati have this problem. Restarting the X session doesn´t restore the cursor. Only a reboot seems effective. Changing the cursor theme in KDE's system settings also has no effect. I'm unable to make a screenshot of the mouse cursor. When I make a screenshot using the GIMP, and tell it to include the mouse cursor, it captures a correct mouse cursor. Attached is a photo of poor quality (blame my phone), it however shows the problem. [lspci] 00:00.0 Host bridge [0600]: Intel Corporation 82P965/G965 Memory Controller Hub [8086:29a0] (rev 02) Subsystem: Dell Device [1028:01db] 01:00.0 VGA compatible controller [0300]: ATI Technologies Inc RV516 [Radeon X1300/X1550 Series] [1002:7183] Subsystem: Dell Device [1028:0302] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/360724/+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 1170313] Re: Latest inotify patch causes 100% CPU
Fix resolved my issue; produced no obvious new issues - cheers! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1170313 Title: Latest inotify patch causes 100% CPU Status in “pulseaudio” package in Ubuntu: Fix Committed Bug description: The patch for bug 1167192 was not working correctly. When the pid file was accessed by some software, PulseAudio got stuck in a 100% CPU loop on one core. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1170313/+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 653132] Re: Add Printer dialog requests root password if user is not in Configure Printers group
Raring: Issue regressing in raring (latest updates as of 08-Mar-2013) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/653132 Title: Add Printer dialog requests root password if user is not in Configure Printers group Status in “python-cups” package in Ubuntu: Fix Released Status in “system-config-printer” package in Ubuntu: Fix Released Status in “python-cups” source package in Oneiric: Fix Released Status in “system-config-printer” source package in Oneiric: Fix Released Bug description: Binary package hint: system-config-printer If you go to System-Administration-Printing and try and add printers without being in the Configure Printers group, the applet asks for the root account and root password. This is obviously not workable on Ubuntu where root has no password and the ideal situation is to use [gk]sudo or so to elevate privileges. If the user is not in the Printers group then he should be asked to enter the administration (sudo) password and not try and be root if possible. If root account and permissions are required (i.e. sudo is not enough) then the dialog should notify the user that they should enable it in Users Groups rather than asking for a password which does not exist by default. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-cups/+bug/653132/+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 1153488] Re: System reads Apple Magic Mouse (BT) as a Battery
Please increase the importance of this bug. It affects laptops heavily.
The mouse battery shows as the system battery, which incorrectly affects
system power management behavior. It makes laptops unusable on battery
power.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-power-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1153488
Title:
System reads Apple Magic Mouse (BT) as a Battery
Status in “gnome-power-manager” package in Ubuntu:
New
Bug description:
This is a weird one... the system is an HP Pavilion 23 All In One and
is powered by a large power supply brick.
I currently have an Apple Magic Mouse connected via Bluetooth. As
soon as the mouse is connected, the Battery indicator shows up and
clicking on that shows that the system is reading my mouse as a
battery!
See the attached screen shot for what I see in the Power status.
Looking at hcitool:
ubuntu@201206-11396:~$ hcitool dev
Devices:
hci09C:B7:0D:80:71:DB
To make matters even more weird, I actually observed the battery
indicator go from full to Critically Low and the system suspended
itself. Keep in mind, again, that this system has NO battery, it's
reading my bluetooth mouse as a battery device.
I disconnected the magic mouse and the battery indicator went to Empty
Red outline and status showed Battery Disconnected.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.5.0-23-generic 3.5.0-23.35~precise1
ProcVersionSignature: Ubuntu 3.5.0-23.35~precise1-generic 3.5.7.2
Uname: Linux 3.5.0-23-generic x86_64
NonfreeKernelModules: wl fglrx
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: Generic [HD-Audio Generic], device 0: ALC269VC Analog [ALC269VC
Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
ApportVersion: 2.0.1-0ubuntu17.1
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Generic [HD-Audio Generic], device 0: ALC269VC Analog [ALC269VC
Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 1726 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Generic'/'HD-Audio Generic at 0xfeb4 irq 16'
Mixer name : 'Realtek ALC269VC'
Components : 'HDA:10ec0269,103c2aee,00100202'
Controls : 21
Simple ctrls : 10
Date: Mon Mar 11 03:54:36 2013
HibernationDevice: RESUME=UUID=ccd7a21f-7a71-4fa5-b95d-e2898c3dae24
InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64
(20130213)
MachineType: Hewlett-Packard a654
MarkForUpload: True
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-23-generic
root=UUID=e2a5f4ae-dfa2-40be-a6c5-3ddb85dcf68e ro quiet splash initcall_debug
vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.5.0-23-generic N/A
linux-backports-modules-3.5.0-23-generic N/A
linux-firmware1.79.1
SourcePackage: linux
StagingDrivers: rts_pstor
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/24/2012
dmi.bios.vendor: AMI
dmi.bios.version: 8.08
dmi.board.name: 2AEE
dmi.board.vendor: PEGATRON CORPORATION
dmi.board.version: 1.03
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias:
dmi:bvnAMI:bvr8.08:bd08/24/2012:svnHewlett-Packard:pna654:pvr:rvnPEGATRONCORPORATION:rn2AEE:rvr1.03:cvnHewlett-Packard:ct3:cvr:
dmi.product.name: a654
dmi.sys.vendor: Hewlett-Packard
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1153488/+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 1181807] Re: Firefox refuses to load, cannot find profile
** Changed in: firefox (Ubuntu) Status: New = Confirmed -- 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/1181807 Title: Firefox refuses to load, cannot find profile Status in “firefox” package in Ubuntu: Confirmed Bug description: Platform: Ubuntu 12.04 LTS (64-bit) Firefox version: 21 What happens: After upgrading to Firefox 21 any attempt to launch the Firefox application displays an error saying the user's profile cannot be found or is invalid. (The exact error message is Your Firefox profile cannot be loaded. It may be missing or inaccessible.) The Firefox browser then closes. Trying to launch the profile manager or launch Firefox with an alternative profile or in safe mode all produce the same error, followed by Firefox closing. What is expected: Firefox should open, or at least display the profile manager to allow users to fix the problem. Work around: I tried deleting my profile and, indeed, the entire ~/.mozilla directory. Made sure Firefox was not running. Removed/purged Firefox and re-installed. None of these steps corrected the problem. The only work around I've found which allows Firefox to run is removing Firefox 21 and installer an older version. Firefox 11.0, for example, is in the repositories. Warning, upgrading to Firefox 21 after successfully installing and running an older version causes the problem to occur again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1181807/+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 1181807] Re: Firefox refuses to load, cannot find profile
I have confirmed this problem on Ubuntu 12.04 LTS (Firefox version 22.0). ** Attachment added: Screenshot from 2013-07-20 17:07:14.png https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1181807/+attachment/3744022/+files/Screenshot%20from%202013-07-20%2017%3A07%3A14.png -- 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/1181807 Title: Firefox refuses to load, cannot find profile Status in “firefox” package in Ubuntu: Confirmed Bug description: Platform: Ubuntu 12.04 LTS (64-bit) Firefox version: 21 What happens: After upgrading to Firefox 21 any attempt to launch the Firefox application displays an error saying the user's profile cannot be found or is invalid. (The exact error message is Your Firefox profile cannot be loaded. It may be missing or inaccessible.) The Firefox browser then closes. Trying to launch the profile manager or launch Firefox with an alternative profile or in safe mode all produce the same error, followed by Firefox closing. What is expected: Firefox should open, or at least display the profile manager to allow users to fix the problem. Work around: I tried deleting my profile and, indeed, the entire ~/.mozilla directory. Made sure Firefox was not running. Removed/purged Firefox and re-installed. None of these steps corrected the problem. The only work around I've found which allows Firefox to run is removing Firefox 21 and installer an older version. Firefox 11.0, for example, is in the repositories. Warning, upgrading to Firefox 21 after successfully installing and running an older version causes the problem to occur again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1181807/+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 720466] Re: When I try burning DVDs it ejects and say that it's impossible to link plugin pads.
This is still an issue in 12.10. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brasero in Ubuntu. https://bugs.launchpad.net/bugs/720466 Title: When I try burning DVDs it ejects and say that it's impossible to link plugin pads. Status in A disc burning application for gnome 2: New Status in “brasero” package in Ubuntu: Fix Released Bug description: Binary package hint: brasero That's it ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: brasero 2.32.0-0ubuntu2.2 ProcVersionSignature: Ubuntu 2.6.35-27.47-generic 2.6.35.11 Uname: Linux 2.6.35-27-generic i686 Architecture: i386 Date: Wed Feb 16 19:18:25 2011 ExecutablePath: /usr/bin/brasero InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: brasero XsessionErrors: (polkit-gnome-authentication-agent-1:1555): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed (nautilus:1559): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed (brasero:2096): GLib-CRITICAL **: the GVariant format string `(u)' has a type of `(u)' but the given value has a type of `()' (brasero:2096): GLib-CRITICAL **: g_variant_get: assertion `valid_format_string (format_string, TRUE, value)' failed To manage notifications about this bug go to: https://bugs.launchpad.net/brasero/+bug/720466/+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 1181807] Re: Firefox refuses to load, cannot find profile
I found a workaround for this problem: sudo aa-update-browser -u plugins-common /etc/apparmor.d/usr.bin.firefox sudo service apparmor reload -- 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/1181807 Title: Firefox refuses to load, cannot find profile Status in “firefox” package in Ubuntu: Confirmed Bug description: Platform: Ubuntu 12.04 LTS (64-bit) Firefox version: 21 What happens: After upgrading to Firefox 21 any attempt to launch the Firefox application displays an error saying the user's profile cannot be found or is invalid. (The exact error message is Your Firefox profile cannot be loaded. It may be missing or inaccessible.) The Firefox browser then closes. Trying to launch the profile manager or launch Firefox with an alternative profile or in safe mode all produce the same error, followed by Firefox closing. What is expected: Firefox should open, or at least display the profile manager to allow users to fix the problem. Work around: I tried deleting my profile and, indeed, the entire ~/.mozilla directory. Made sure Firefox was not running. Removed/purged Firefox and re-installed. None of these steps corrected the problem. The only work around I've found which allows Firefox to run is removing Firefox 21 and installer an older version. Firefox 11.0, for example, is in the repositories. Warning, upgrading to Firefox 21 after successfully installing and running an older version causes the problem to occur again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1181807/+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 1181807] Re: Firefox refuses to load, cannot find profile
When I use aa-update-browser -u plugins-common to fix the problem with Firefox, it creates another problem when using aa-enforce: ubuntu-admin@OR-DC1-UB:/etc/apparmor.d$ sudo aa-enforce /etc/apparmor.d/* Setting /etc/apparmor.d/bin.ping to enforce mode. Setting /etc/apparmor.d/lightdm-guest-session to enforce mode. Setting /etc/apparmor.d/sbin.dhclient to enforce mode. Setting /etc/apparmor.d/sbin.klogd to enforce mode. Setting /etc/apparmor.d/sbin.syslogd to enforce mode. Setting /etc/apparmor.d/sbin.syslog-ng to enforce mode. Setting /etc/apparmor.d/usr.bin.chromium-browser to enforce mode. Setting /etc/apparmor.d/usr.bin.evince to enforce mode. Setting /etc/apparmor.d/usr.bin.firefox to enforce mode. Warning from stdin (line 1): /sbin/apparmor_parser: cannot use or update cache, disable, or force-complain via stdin Multiple definitions for hat sanitized_helper in profile (null) exist,bailing out. Out of all the browser abstractions (java kde mailto multimedia plugins- common productivity text-editors ubuntu-integration ubuntu-integration- xul user-files), plugins-common is the only one that generates this error. -- 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/1181807 Title: Firefox refuses to load, cannot find profile Status in “firefox” package in Ubuntu: Confirmed Bug description: Platform: Ubuntu 12.04 LTS (64-bit) Firefox version: 21 What happens: After upgrading to Firefox 21 any attempt to launch the Firefox application displays an error saying the user's profile cannot be found or is invalid. (The exact error message is Your Firefox profile cannot be loaded. It may be missing or inaccessible.) The Firefox browser then closes. Trying to launch the profile manager or launch Firefox with an alternative profile or in safe mode all produce the same error, followed by Firefox closing. What is expected: Firefox should open, or at least display the profile manager to allow users to fix the problem. Work around: I tried deleting my profile and, indeed, the entire ~/.mozilla directory. Made sure Firefox was not running. Removed/purged Firefox and re-installed. None of these steps corrected the problem. The only work around I've found which allows Firefox to run is removing Firefox 21 and installer an older version. Firefox 11.0, for example, is in the repositories. Warning, upgrading to Firefox 21 after successfully installing and running an older version causes the problem to occur again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1181807/+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 1112405] Re: Error in printing pdf file from Evince (HP LazerJet 4250 printer)
This is still an error for me with some documents on 13.10 64bit using multiple HP printers. An offending file can be found here: http://arxiv.org/pdf/quant-ph/0506219v1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1112405 Title: Error in printing pdf file from Evince (HP LazerJet 4250 printer) Status in “evince” package in Ubuntu: Confirmed Bug description: Printing attached pdf file ends with printer error at page 16. The same file can be printed correctly with Adobe Reader in Windows. It is HP LaserJet 4250 printer and it prints error: ERROR: typecheck OFFENDING COMMAND: known System Ubuntu 12.10 Evince 3.6.0-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1112405/+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 1494095] Re: Dell U3414W screen not turning on in 3440 x 1440 mode
Disabled DP 1.2 on my monitor and it started working for me too. -- 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/1494095 Title: Dell U3414W screen not turning on in 3440 x 1440 mode Status in xserver-xorg-video-intel package in Ubuntu: Incomplete Bug description: Following on from https://answers.launchpad.net/ubuntu/+source /xserver-xorg-video-intel/+question/270926 When I plug a Dell U3414W screen into my Dell XPS 13 9343 display port the screen does not turn on when I enable it's native 3440 x 1440 in the display settings. Lower resolutions correctly work such as: 2560 x 1080 1560 x 1440 I also found these messages in the dmesg log: [ 308.637781] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe B FIFO underrun ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.2 ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4 Uname: Linux 3.19.0-26-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1.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 Date: Thu Sep 10 11:56:31 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.248+bdcom, 3.19.0-22-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 3.19.0-23-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 3.19.0-25-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 3.19.0-26-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 3.19.0-28-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0665] InstallationDate: Installed on 2015-06-20 (82 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. XPS 13 9343 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-26-generic.efi.signed root=UUID=b9c575ed-3fa1-4890-b4f2-b57441e8337d 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: 07/14/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0310JH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd07/14/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1~vivid2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1~vivid2 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Wed Sep 9 13:12:40 2015 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 41126 vendor DEL xserver.version: 2:1.17.1-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1494095/+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 1583303] Re: Laptop not going to suspend when lid closed
I can confirm that this bug also affects Linux Mint 18, which is based on the 16.04 packages. I'm running it on a ThinkPad T420, which uses the NVS4200M graphics chipset. It's set up as an Optimus graphics card, but I have disabled Optimus in the BIOS and forced the use of the dedicated GPU. I'm using the same build of nouveau: xserver-xorg-video-nouveau: Installed: 1:1.0.12-1build2 Candidate: 1:1.0.12-1build2 Version table: *** 1:1.0.12-1build2 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status I can also confirm that switching to nvidia-361 allows the laptop to suspend on lid close for me. Using nouveau with Linux Mint 17.3 also caused this issue for me, though I don't have the details of that install on-hand. I do still have the drive on which it is installed if I need to get info on that. I'm happy to provide any additional information. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1583303 Title: Laptop not going to suspend when lid closed Status in xserver-xorg-video-nouveau package in Ubuntu: Incomplete Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description: Ubuntu 16.04 LTS Release: 16.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center xserver-xorg-video-nouveau: Installiert: 1:1.0.12-1build2 Installationskandidat: 1:1.0.12-1build2 Versionstabelle: *** 1:1.0.12-1build2 500 500 http://ch.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen If in power options I have defined the laptop to go to suspend mode when laptop lid is closed, I would expect it to do exactly that. 4) What happened instead Nothing happened - the laptop remains on while the display switches off. I then tried the nvidia binary driver (361.42). For both GPU selections made in nvidia x server settings, Intel and nvidia, the laptop suspended few seconds after closing the lid. When I switched back to X.Org-X-Server the problem was back again. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg-video-nouveau 1:1.0.12-1build2 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 BootLog: /dev/sda5: clean, 244866/2555904 files, 1699692/10215936 blocks 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: Wed May 18 20:38:50 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-22-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 4th Gen Core Processor Integrated Graphics Controller [103c:1968] Subsystem: Hewlett-Packard Company GK107M [GeForce GT 750M] [103c:219d] InstallationDate: Installed on 2016-05-15 (2 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Hewlett-Packard HP ENVY 17 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed root=UUID=9c6f19c2-ffaa-4916-aa1b-5c8e434c0d31 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.66 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 1968 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 93.52 dmi.chassis.asset.tag: 5CG414DSZL dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.66:bd09/22/2015:svnHewlett-Packard:pnHPENVY17NotebookPC:pvr097E11405E0620100:rvnHewlett-Packard:rn1968:rvrKBCVersion93.52:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP ENVY 17 Notebook PC dmi.product.version: 097E11405E0620100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core:
[Desktop-packages] [Bug 1496542] Re: Running processes left after disabling screen reader
I have encountered a very similar problem. I had never used the screen reader. I'm guessing that something had glitched in my system. But I had heard a random sound while using my system and I checked the running processes and I had found these processes running. Is there a related bug anywhere? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to speech-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1496542 Title: Running processes left after disabling screen reader Status in speech-dispatcher package in Ubuntu: Triaged Bug description: After I disabled my screen reader, I noticed that when running "ps xa | grep -P 'speech-dispatcher.*\.conf'" I get: 17906 tty2 Sl+0:09 /usr/lib/speech-dispatcher-modules/sd_espeak /etc/speech-dispatcher/modules/espeak.conf 17911 tty2 Sl+0:01 /usr/lib/speech-dispatcher-modules/sd_cicero /etc/speech-dispatcher/modules/cicero.conf 17915 tty2 Sl+0:01 /usr/lib/speech-dispatcher-modules/sd_generic /etc/speech-dispatcher/modules/generic.conf 17918 tty2 Sl+0:01 /usr/lib/speech-dispatcher-modules/sd_dummy /etc/speech-dispatcher/modules/dummy.conf 24407 pts/0S+ 0:00 grep --color=auto -P speech-dispatcher.*\.conf So it seems as though it left some running processes behind after I disabled it. I have also attached a screenshot of my Sound settings which show that they are still running (Sound_Application_List2.png). --- OS Information: No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 15.04 Release: 15.04 Codename: vivid Package Information: speech-dispatcher: Installed: 0.8.1-0ubuntu1 Candidate: 0.8.1-0ubuntu1 Version table: *** 0.8.1-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: speech-dispatcher 0.8.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.4 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Sep 16 20:27:00 2015 InstallationDate: Installed on 2015-07-29 (49 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: speech-dispatcher UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1496542/+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 1622571] Re: NetworkManager crashed with SIGSEGV in nm_dns_manager_end_updates()
I believe I'm also having this problem. I've uploaded the whoopsie dump with apport but I can't see where it is being tracked (see http://askubuntu.com/questions/900191/where-do-i-look-to-see-if-my- whoopsie-is-being-tracked). The stack looks the same: SegvAnalysis: Segfault happened at: 0x7fc79f90e830 <__libc_start_main+240>: mov%eax,%edi PC (0x7fc79f90e830) ok source "%eax" ok destination "%edi" ok SP (0x7ffc12fba2c0) ok Reason could not be automatically determined. SourcePackage: network-manager Stacktrace: #0 0x0048cc66 in nm_dns_manager_end_updates () #1 0x7fc79d566e40 in ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 #2 0x7fc79d5668ab in ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 #3 0x7fc7a01f5cf5 in g_cclosure_marshal_generic_va () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #4 0x7fc7a01f51d4 in ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #5 0x7fc7a020f9a6 in g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #6 0x7fc7a021008f in g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 This started happening when I commented out the dns=dnsmasq line in my NetworkManager.conf and indeed the crash happens in DNS related code. The often occurs after resuming from suspend, but not always - it may also just occur while using the host. Here's a link to the whoopise upload - I don't have perms to see it, but perhaps someone who does can associate it with this bug? https://errors.ubuntu.com/oops/f3ce1fb0-1957-11e7-968c-fa163e8d4bab -- 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/1622571 Title: NetworkManager crashed with SIGSEGV in nm_dns_manager_end_updates() Status in network-manager package in Ubuntu: Confirmed Bug description: it appeared right after boot, but I do use a 4.8 kernel.. Linux jaypc 4.8.0-040800rc1-generic #201608072231 SMP Mon Aug 8 02:33:57 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: network-manager 1.2.2-0ubuntu8 Uname: Linux 4.6.0-040600-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Thu Sep 8 09:01:03 2016 ExecutablePath: /usr/sbin/NetworkManager IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-04-04 (160 days ago) InstallationMedia: It IpRoute: default via 192.168.11.1 dev enp3s0 proto static metric 100 169.254.0.0/16 dev enp3s0 scope link metric 1000 192.168.11.0/24 dev enp3s0 proto kernel scope link src 192.168.11.20 metric 100 IwConfig: lono wireless extensions. enp3s0no wireless extensions. NetworkManager.conf: [main] plugins=ifupdown,keyfile,ofono [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcCmdline: /usr/sbin/NetworkManager --no-daemon ProcEnviron: LANG=nl_NL.UTF-8 PATH=(custom, no user) RfKill: Can't open RFKILL control device: No such file or directory Signal: 11 SourcePackage: network-manager StacktraceTop: nm_dns_manager_end_updates () ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 g_cclosure_marshal_generic_va () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: NetworkManager crashed with SIGSEGV in nm_dns_manager_end_updates() UpgradeStatus: Upgraded to yakkety on 2016-05-20 (115 days ago) UserGroups: nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH Wired connection 1 83b55d9f-56b0-3de7-8781-b60ac02d32da 802-3-ethernet 1473679209 ma 12 sep 2016 13:20:09 CEST yes 4294966297no /org/freedesktop/NetworkManager/Settings/1 yes enp3s0 activated /org/freedesktop/NetworkManager/ActiveConnection/0 NETGEAR74 2508a31f-ca9b-47cc-a9e3-8f5be4686282 802-11-wireless 1463994465 ma 23 mei 2016 11:07:45 CEST yes 0 no /org/freedesktop/NetworkManager/Settings/0 no -- -- -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH enp3s0 ethernet connected /org/freedesktop/NetworkManager/Devices/0 Wired connection 1 83b55d9f-56b0-3de7-8781-b60ac02d32da
[Desktop-packages] [Bug 1631241] Re: Name resolution stops working after resume from suspend
I just started seeing this recently in 16.04. I used the workaround suggested here: http://askubuntu.com/questions/837575/dns-resolution-fails-after-wakeup- from-standby-ubuntu-16-10 of commenting out the dnsmasq entry in /etc/NetworkManager/NetworkManager.conf -- 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/1631241 Title: Name resolution stops working after resume from suspend Status in dnsmasq: Fix Released Status in dnsmasq package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: After upgrading to Yakkety, when my Ubuntu GNOME laptop resumes from suspend DNS resolution stops working. After resuming, systemd-resolved is running and libnss-resolve is installed, but /etc/resolv.conf contains 127.0.1.1 as the the only name server. The dnsmasq-base package is installed since it is pulled in by both network-manager and lxc1, and both NM and libvirt have spawned instances of dnsmasq: > 1155 pts/2S+ 0:00 grep dnsmasq > 2724 ?S 0:00 dnsmasq -u lxc-dnsmasq --strict-order --bind-interfaces --pid-file=/run/lxc/dnsmasq.pid --listen-address 10.0.3.1 --dhcp-range 10.0.3.2,10.0.3.254 --dhcp-lease-max=253 --dhcp-no-override --except-interface=lo --interface=lxcbr0 --dhcp-leasefile=/var/lib/misc/dnsmasq.lxcbr0.leases --dhcp-authoritative > 2992 ?S 0:00 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper > 2993 ?S 0:00 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper > 22879 ?S 0:00 /usr/sbin/dnsmasq --no-resolv --keep-in-foreground --no-hosts --bind-interfaces --pid-file=/var/run/NetworkManager/dnsmasq.pid --listen-address=127.0.1.1 --cache-size=0 --conf-file=/dev/null --proxy-dnssec --enable-dbus=org.freedesktop.NetworkManager.dnsmasq --conf-dir=/etc/NetworkManager/dnsmasq.d Let me know if you need any extra info. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: libnss-resolve 231-9git1 ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7 Uname: Linux 4.8.0-17-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Oct 7 13:52:40 2016 InstallationDate: Installed on 2015-07-22 (443 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: systemd UpgradeStatus: Upgraded to yakkety on 2016-10-05 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/dnsmasq/+bug/1631241/+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 1724307] Re: [Dell XPS 13 9360] Mouse cursor flickers with one external monitor connected via HDMI+Wavlink WL-UG39DK1V
I'm having the same issue as well. With three screens the mouse has a glitch where it's like part of the screen makes a box around it. It almost seems to happen on interactions.. It's very noticable moving over tabs on a browser window. I'm not sure if the same effect would happen with two video cards two monitors share the 1050ti with the Nvidia drivers installed. I did get the latest display link drivers installed. If there's any information from my computer I can supply please let me know. Thanks for the help!! -- 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/1724307 Title: [Dell XPS 13 9360] Mouse cursor flickers with one external monitor connected via HDMI+Wavlink WL-UG39DK1V Status in xorg package in Ubuntu: Incomplete Bug description: When I connect my laptop to my DisplayLink based device with USB (Wavlink universal USB 3.0 docking station https://www.wavlink.com/en/product/150 WL-UG39DK1V), and connect the Wavlink to my AOC E2775SJ Monitor via HDMI, the mouse icon flickers. Only if the mouse is on the laptop monitor, it can vanish for several minutes, but remains active. Animations/overlays or typing inside a Chrome window causes the mouse pointer to flicker more often. If there is no interaction or animation, the mouse pointer remains static and drawn. Monitor 1: 1920 x 1080 - Laptop's Native Monitor Monitor 2: 1920 x 1080 - DisplayLink (USB) connected AOC E2775SJ Monitor This issue doesn't happen if I don't connect my laptop to an external monitor via the Wavlink device. This issue is reproducible with DisplayLink driver 1.4, and 1.3.54. This issue is reproducible with Ubuntu 16.04, 17.04, and 17.10 x64. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-37-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Oct 17 10:01:55 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:082a] InstallationDate: Installed on 2017-10-16 (0 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Dell Inc. XPS 13 9360 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-37-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/18/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.2.1 dmi.board.name: 05FPM2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.2.1:bd08/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05FPM2:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A 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 xserver.bootTime: Tue Oct 17 09:39:15 2017 xserver.configfile: default xserver.errors: modeset(G0): glamor initialization failed xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5193 vendor SHP xserver.version: 2:1.19.3-1ubuntu1~16.04.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1724307/+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 1730213] [NEW] Mouse cursor flickers with box when external Display Link monitor is connected
Public bug reported: I'm having the same issue as well. With three screens the mouse has a glitch where it's like part of the screen makes a box around it. It almost seems to happen on interactions.. It's very noticable moving over tabs on a browser window. I'm not sure if the same effect would happen with two video cards two monitors share the 1050ti with the Nvidia drivers installed. I did get the latest display link drivers installed. Thanks again for the help ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-39.43-generic 4.10.17 Uname: Linux 4.10.0-39-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.90 Tue Sep 19 19:17:35 PDT 2017 GCC version: gcc version 6.3.0 20170406 (Ubuntu 6.3.0-12ubuntu2) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity_support_test.0: ApportVersion: 2.20.4-0ubuntu4.5 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:Unity7 Date: Sun Nov 5 11:30:06 2017 DistUpgraded: 2017-11-05 00:25:16,311 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory) (8)) DistroCodename: zesty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.10.0-28-generic, x86_64: installedError! Could not locate dkms.conf file. File: does not exist. bbswitch, 0.8, 4.10.0-38-generic, x86_64: installed bbswitch, 0.8, 4.10.0-39-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP107 [GeForce GTX 1050 Ti] [3842:6253] InstallationDate: Installed on 2017-11-04 (0 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Gigabyte Technology Co., Ltd. H110M-M.2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-39-generic root=UUID=8718e5d2-d2a9-4711-9619-505cb18367c9 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to zesty on 2017-11-05 (0 days ago) dmi.bios.date: 02/22/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F21 dmi.board.asset.tag: Default string dmi.board.name: H110M-M2-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF21:bd02/22/2017:svnGigabyteTechnologyCo.,Ltd.:pnH110M-M.2:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnH110M-M2-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: H110M-M.2 dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.17.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.17.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A 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 xserver.bootTime: Sun Nov 5 11:22:13 2017 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1.3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu zesty ** Summary changed: - Mouse cursor flickers with one external Display Link monitor connected + Mouse cursor flickers with box when external Display Link monitor is connected -- 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/1730213 Title: Mouse cursor flickers with box when external Display Link monitor is connected
[Desktop-packages] [Bug 1308105]
Similarly I keep losing my configured resolution of 1280x720, with the system defaulting back to 1920x1080 every time (which looks rubbish on my crappy monitor). Manually running "xfsettingsd --replace" is a workaround, but not ideal. All progress though, it's still much better than rebooting every time. Thanks a ton for getting us this far. -- 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/1308105 Title: Xfce resets TV mode to NULL when power cycled Status in Mythbuntu: Confirmed Status in xfce4-settings: Fix Released Status in nvidia-graphics-drivers package in Ubuntu: Invalid Status in nvidia-graphics-drivers-331 package in Ubuntu: Invalid Status in xfce4-settings package in Ubuntu: Confirmed Bug description: I had an HTPC with Mythbuntu 12.04 installed. Upon upgrading a new behavior that if the TV is power cycled it no longer detects a link with the HTPC. When this happens I can find in the xorg log that there is an accompanying log item: [ 39829.509] (II) NVIDIA(0): Setting mode "NULL" After debugging with NVIDIA at https://devtalk.nvidia.com/default/topic/729955/linux/tv-stops-being- detected/ we've deteremined it's a X client that reacts to the RANDR events causing the mode to be set to NULL. Working through the list in an Xfce environment, the culprit is xfsettingsd. If xfsettingsd is running, it causes the TV to come up in a NULL mode. If it's killed, it remains in the mode it was previously running in. Until this is fixed, this behavior can be worked around with a simple shell script: == #!/bin/sh #Fix TV state when HDMI link is lost. #By Mario Limonciello OUTPUT="HDMI-0" BAD_MODE="1280x720" GOOD_MODE="1920x1080" for MODE in $BAD_MODE $GOOD_MODE; do DISPLAY=:0 xrandr --output $OUTPUT --mode $MODE sleep 2 done == To manage notifications about this bug go to: https://bugs.launchpad.net/mythbuntu/+bug/1308105/+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 794929] Re: Disk Utility benchmark, x-axis undefined
If the X-axis is %time for the benchmark read/write then why does it typically decrease over time? Surely the X-axis is the read/write speed at different positions 0-100% across the disk, like access time? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/794929 Title: Disk Utility benchmark, x-axis undefined Status in gnome-disk-utility package in Ubuntu: Confirmed Bug description: There is no legend to explain what the % value means in the benchmark graph. Nor does palimpsest appear to have a help page. Disk Utility 2.32.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/794929/+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 1730513] Re: [SRU artful] korganiser reminders do not trigger with 17.04.3
Was this ever going to get pulled into Artful? "Reminders don't work at all" seems like a big thing to just sit with an available fix for 5 months now -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to akonadi in Ubuntu. https://bugs.launchpad.net/bugs/1730513 Title: [SRU artful] korganiser reminders do not trigger with 17.04.3 Status in Akonadi: Fix Released Status in akonadi package in Ubuntu: Fix Released Status in akonadi source package in Artful: In Progress Status in akonadi source package in Bionic: Fix Released Bug description: akonadi: 4:17.04.3-0ubuntu in artful and 4:17.04.3-0ubuntu1 and ubuntu2 in bionic When the korganizer tray daemon (koragc) is set to enable event reminders, these silently fail to appear. Seemingly upstream KDE bug: https://bugs.kde.org/show_bug.cgi?id=384212 With back-portable fix from the 17.08 branch: https://cgit.kde.org/akonadi.git/commit/?h=Applications/17.08=d3c6ba904798768b0c83c2e182c27b1c624f78ca Test build for artful in: https://launchpad.net/~rikmills/+archive/ubuntu/akonadi-bug *** SRU information *** [Impact] * An expected and relied on feature of KDE PIM (appointment and event reminders) shown on the desktop etc does not work. * Fix is a single non extensive commit that the upstream KDE developer considers is likely to be safe to backport. [Test Case] * Use korganiser to set a calendar item with a reminder * Make sure the organiser tray daemeon is running (koragc), and that reminders are enabled. * Test if a reminder is shown at the selected appropriate time relative to the event (can be a few mins delay in some cases) * In addition, generally test that adding, modifying, viewing event information works as before. * Test other KDE PIM applications as much as is practical [Regression Potential] * Single commit that upstream considers should not be problematic to backport. * As akonagi acts as the storage backend for PIM generally, it is unlikely but possible there could be unintended impacts. Testing of other parts of the PIM stack, as much as is practical is advisable. To manage notifications about this bug go to: https://bugs.launchpad.net/akonadi/+bug/1730513/+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 1730513] Re: [SRU artful] korganiser reminders do not trigger with 17.04.3
Any chance for this to get into Artful? Reminders are extremely useful. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to akonadi in Ubuntu. https://bugs.launchpad.net/bugs/1730513 Title: [SRU artful] korganiser reminders do not trigger with 17.04.3 Status in Akonadi: Fix Released Status in akonadi package in Ubuntu: Fix Released Status in akonadi source package in Artful: In Progress Status in akonadi source package in Bionic: Fix Released Bug description: akonadi: 4:17.04.3-0ubuntu in artful and 4:17.04.3-0ubuntu1 and ubuntu2 in bionic When the korganizer tray daemon (koragc) is set to enable event reminders, these silently fail to appear. Seemingly upstream KDE bug: https://bugs.kde.org/show_bug.cgi?id=384212 With back-portable fix from the 17.08 branch: https://cgit.kde.org/akonadi.git/commit/?h=Applications/17.08=d3c6ba904798768b0c83c2e182c27b1c624f78ca Test build for artful in: https://launchpad.net/~rikmills/+archive/ubuntu/akonadi-bug *** SRU information *** [Impact] * An expected and relied on feature of KDE PIM (appointment and event reminders) shown on the desktop etc does not work. * Fix is a single non extensive commit that the upstream KDE developer considers is likely to be safe to backport. [Test Case] * Use korganiser to set a calendar item with a reminder * Make sure the organiser tray daemeon is running (koragc), and that reminders are enabled. * Test if a reminder is shown at the selected appropriate time relative to the event (can be a few mins delay in some cases) * In addition, generally test that adding, modifying, viewing event information works as before. * Test other KDE PIM applications as much as is practical [Regression Potential] * Single commit that upstream considers should not be problematic to backport. * As akonagi acts as the storage backend for PIM generally, it is unlikely but possible there could be unintended impacts. Testing of other parts of the PIM stack, as much as is practical is advisable. To manage notifications about this bug go to: https://bugs.launchpad.net/akonadi/+bug/1730513/+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 1829221] Re: second, dead, mouse pointer left on screen after login, x11 session
*** This bug is a duplicate of bug 1873052 *** https://bugs.launchpad.net/bugs/1873052 I was able to get rid of this by changing the display scaling back to 100% and than I resumed the display scale that I had wanted. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1829221 Title: second, dead, mouse pointer left on screen after login, x11 session Status in mutter package in Ubuntu: Confirmed Bug description: This seems to have become repeatable, and applies even on the first login session immediately after booting the computer. I don't know if this is the right package to report against; another possible culprit: gdm: When I log into the default "Ubuntu" session (ie: on xorg), gdm's mouse pointer remains on screen during the screen blank, and after the gnome desktop comes up. It stays on the top just like you'd expect of the mouse pointer, but it's immobile and unresponsive. It's left at the same position on the screen that it was while using gdm, and is the same size as it was in gdm (ie: gdm is not scaled, but gnome session desktop scaled to 150% - the *working* in-session mouse pointer is also 150% larger than gdm's dead one). It looks like gdm and gnome are running in the same x11 session? Seeing as the mouse pointer stays solid *during* the transition from gdm into the gnome desktop. Not even a flicker. It's almost as if we're trying to have smooth transitions for these sorts of things, which is good of course, but maybe is a bug in that? It disappears when I log into a Wayland session, it appears only to affect x11 sessions. I've taken to just moving the mouse pointer to the far bottom right corner of the screen before logging in, so at least it's not very intrusive. There are a few reports of similar in askubuntu from a few years back, but with no helpful or applicable solution. eg: https://askubuntu.com/questions/521241/i-have-two-cursors-on-my-screen-one-of-which-is-always-on-top-and-will-never-mo https://askubuntu.com/questions/598096/14-04-second-mouse-pointer-stuck-in-middle-of-the-screen To answer the points made there, the xinput --list output is shown below. Executing that command and rebooting makes no difference. In the Displays Prefs there is no second "Unknown" display to disable. (The machine has precisely one display, and that's all Settings sees. It's a desktop, not a laptop, and it only has an AMD Vega integrated graphics. It also has only one mouse.) rachel@twilight:~$ xinput --list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ HID 04b4:3003 Mouse id=9[slave pointer (2)] ⎜ ↳ HID 04b4:3003 Consumer Control id=11 [slave pointer (2)] ⎜ ↳ Microsoft Microsoft® Nano Transceiver v1.0 Mouseid=15 [slave pointer (2)] ⎜ ↳ Microsoft Microsoft® Nano Transceiver v1.0 Consumer Control id=16 [slave pointer (2)] ⎜ ↳ Microsoft Microsoft® Nano Transceiver v1.0 Consumer Control id=17 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Power Buttonid=7[slave keyboard (3)] ↳ HID 04b4:3003 id=8[slave keyboard (3)] ↳ HID 04b4:3003 System Controlid=10 [slave keyboard (3)] ↳ HID 04b4:3003 Keyboard id=12 [slave keyboard (3)] ↳ Dell Dell AC511 USB SoundBarid=13 [slave keyboard (3)] ↳ Microsoft Microsoft® Nano Transceiver v1.0 id=14 [slave keyboard (3)] ↳ Microsoft Microsoft® Nano Transceiver v1.0 System Control id=18 [slave keyboard (3)] ↳ Eee PC WMI hotkeys id=19 [slave keyboard (3)] ↳ HID 04b4:3003 Consumer Control id=20 [slave keyboard (3)] ↳ Microsoft Microsoft® Nano Transceiver v1.0 Consumer Control id=21 [slave keyboard (3)] ↳ Microsoft Microsoft® Nano Transceiver v1.0 Consumer Control id=22 [slave keyboard (3)] (I don't know what's with the duplicated MS Nano Transceiver Consumer Control entries) I thought of a couple of things to try after starting to write this ticket but didn't want to lose the ticket in progress, so will add comments if they show up anything. In particular, I am running the experimental feature to enable xrandr fractional scaling. This issue didn't show up right after enabling that, only a couple of days later, so it
[Desktop-packages] [Bug 1922317] [NEW] package bluez 5.53-0ubuntu3 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1
Public bug reported: I cannot seem to get my bluetooth to work. When I go to bluetooth settings the "switch" is grayed out and I cannot turn it off or on. I'm trying to install bluez and I am getting an error. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94 Uname: Linux 5.4.0-70-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 AptOrdering: bluez:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Apr 1 20:17:40 2021 ErrorMessage: installed bluez package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-01-15 (443 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) InterestingModules: bnep bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b509 Chicony Electronics Co., Ltd HP Truevision HD Bus 001 Device 009: ID :3100 MacAlly Macally ECOMouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/11p, 480M |__ Port 3: Dev 9, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 5: Dev 3, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 5: Dev 3, If 1, Class=Video, Driver=uvcvideo, 480M MachineType: HP HP Notebook ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-70-generic root=UUID=93ef3a52-1422-4313-abac-a02f96bcecc3 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: bluez Title: package bluez 5.53-0ubuntu3 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2021-04-02 (0 days ago) dmi.bios.date: 03/06/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.26 dmi.board.vendor: HP dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.26:bd03/06/2018:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn:rvr:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: N5Z06UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP hciconfig: rfkill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1922317 Title: package bluez 5.53-0ubuntu3 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1 Status in bluez package in Ubuntu: New Bug description: I cannot seem to get my bluetooth to work. When I go to bluetooth settings the "switch" is grayed out and I cannot turn it off or on. I'm trying to install bluez and I am getting an error. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94 Uname: Linux 5.4.0-70-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 AptOrdering: bluez:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Apr 1 20:17:40 2021 ErrorMessage: installed bluez package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-01-15 (443 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) InterestingModules: bnep bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b509 Chicony Electronics Co., Ltd HP Truevision HD Bus 001 Device 009: ID :3100 MacAlly Macally ECOMouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/11p, 480M |__ Port 3: Dev 9, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 5: Dev 3, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 5: Dev 3, If 1, Class=Video, Driver=uvcvideo, 480M MachineType: HP HP Notebook ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-70-generic root=UUID=93ef3a52-1422-4313-abac-a02f96bcecc3 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18,
[Desktop-packages] [Bug 1852911] Re: CriticalPowerAction=Suspend should be supported
I would like to add my voice here and say that a patch, either to upstream UPower or to Ubuntu's version would be much appreciated. I've lost work several times as neither HybridSleep nor Hibernate work on my laptop so it simply shuts down, and due to a quirk of the batter management the delay between the notification of low % and then the critical threshold and shutdown is often only mere seconds. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1852911 Title: CriticalPowerAction=Suspend should be supported Status in Upower: New Status in upower package in Ubuntu: Triaged Bug description: The action to take when the battery is critical can only be one of the following: # Possible values are: # PowerOff # Hibernate # HybridSleep Adding Suspend to that list makes perfect sense. My laptop is currently powering off on low power which is useless as I'll be losing my work anyway. Might as well suspend and allow me to notice that and connect a charger. If the thinking is that suspend uses power I can set a high enough threshold to give me some margin. The failovers are: # If HybridSleep isn't available, Hibernate will be used # If Hibernate isn't available, PowerOff will be used I'd argue Suspend should actually come before PowerOff in that list. For most laptop users having their computer suspend because they didn't notice the battery was running out is very easy to fix and takes no time. They'll just connect the charger. If however the computer needs to be completely rebooted, not only does that take a lot more time it will very likely cause lost work. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: upower 0.99.10-1 ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.3 Architecture: amd64 CurrentDesktop: Unity Date: Sun Nov 17 14:32:13 2019 InstallationDate: Installed on 2019-05-09 (191 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: upower UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/upower/+bug/1852911/+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 1069574] Re: Intel graphics card driver update causes black screen
I don't personally own this laptop, but I just finished helping a relative and here is what I've found. 1. In his setup it's a kernel update, using the older kernel works. Can you do the same? (3.2.0-24-generic vs. 3.2.0-32-generic) 2. It appears to be the exact same issue with 12.10. He can't even boot to a 12.10 install media. I will attach the 2 dmesg from both kernels. -- 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/1069574 Title: Intel graphics card driver update causes black screen Status in “xserver-xorg-video-intel” package in Ubuntu: New Bug description: Hi, today I installed an update: xserver-xorg-video-intel 2:2.17.0-1ubuntu4.2 and after GRUB boots my laptop, I get a black screen. I have a Dimension E5510 with Intel on board graphics. It was working perfectly before the update. Please fix this issue. Please let me know if you need further info. Thanks! I had to use the nomodeset option of grub to get my laptop screen to show again. Description: Ubuntu 12.04.1 LTS Release: 12.04 xserver-xorg-video-intel: Installed: 2:2.17.0-1ubuntu4.2 Candidate: 2:2.17.0-1ubuntu4.2 Version table: *** 2:2.17.0-1ubuntu4.2 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main i386 Packages 100 /var/lib/dpkg/status 2:2.17.0-1ubuntu4 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/main i386 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1069574/+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 1069574] Re: Intel graphics card driver update causes black screen
dmesg from non-working kernel ** Attachment added: bad.dmesg https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1069574/+attachment/3414073/+files/bad.dmesg -- 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/1069574 Title: Intel graphics card driver update causes black screen Status in “xserver-xorg-video-intel” package in Ubuntu: New Bug description: Hi, today I installed an update: xserver-xorg-video-intel 2:2.17.0-1ubuntu4.2 and after GRUB boots my laptop, I get a black screen. I have a Dimension E5510 with Intel on board graphics. It was working perfectly before the update. Please fix this issue. Please let me know if you need further info. Thanks! I had to use the nomodeset option of grub to get my laptop screen to show again. Description: Ubuntu 12.04.1 LTS Release: 12.04 xserver-xorg-video-intel: Installed: 2:2.17.0-1ubuntu4.2 Candidate: 2:2.17.0-1ubuntu4.2 Version table: *** 2:2.17.0-1ubuntu4.2 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main i386 Packages 100 /var/lib/dpkg/status 2:2.17.0-1ubuntu4 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/main i386 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1069574/+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 1069574] Re: Intel graphics card driver update causes black screen
dmesg from working kernel ** Attachment added: good.dmesg https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1069574/+attachment/3414072/+files/good.dmesg -- 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/1069574 Title: Intel graphics card driver update causes black screen Status in “xserver-xorg-video-intel” package in Ubuntu: New Bug description: Hi, today I installed an update: xserver-xorg-video-intel 2:2.17.0-1ubuntu4.2 and after GRUB boots my laptop, I get a black screen. I have a Dimension E5510 with Intel on board graphics. It was working perfectly before the update. Please fix this issue. Please let me know if you need further info. Thanks! I had to use the nomodeset option of grub to get my laptop screen to show again. Description: Ubuntu 12.04.1 LTS Release: 12.04 xserver-xorg-video-intel: Installed: 2:2.17.0-1ubuntu4.2 Candidate: 2:2.17.0-1ubuntu4.2 Version table: *** 2:2.17.0-1ubuntu4.2 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main i386 Packages 100 /var/lib/dpkg/status 2:2.17.0-1ubuntu4 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/main i386 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1069574/+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
