[Desktop-packages] [Bug 2022879] Re: No sound from Woofer speaker of Asus Zephyrus G14 2023
The sweet-spot now for me is Kernel 6.7.0 and Nvidia Metapackage driver 535 (proprietary) With this combo Blender sees the GPU correctly and can use the CUDA and Opti-X cores for rendering, and the sound works... The only thing that doesn't work like it should is screen brightness adjustment, so I use a code in the terminal window: $ xrandr --output eDP-1 --brightness 0.7 Where eDP-1 is the main monitor in use, you can check it easily by opening the display settings, and the red box will appear in the upper left corner of the screen with the name of your display. 0.7 is the level of brightness 01 is 10% 0.7 is 70% and 1 is 100%... So this works well for me, as always perfection takes time, and updates come with delay, but eventually there will be a big update that works even with a new super laptop like Zephyrus, I hate Windows, so I rip it out of my laptop as soon as I get my hands on it, like a bad plague hahahah :D and then I just find the best Linux distro... This is a Linux forum right? I already forgot where I'm typing this, so better go back to rendering and system monitoring... Blender 4.1 will be awesome, just beta testing it now... Good work all.. Much love and hugs to all... :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2022879 Title: No sound from Woofer speaker of Asus Zephyrus G14 2023 Status in alsa-driver package in Ubuntu: New Status in pipewire package in Ubuntu: New Bug description: On Asus Zephyrus G14 2023, sound only comes out of the pair of tweeter speaker. The woofer speaker does not produce any sound at all on either on Analog Stereo, Analog Surround 4.0, or 2.1 configurations 1) ┌─[surfer@M5-RGV]-[~] └──╼ $lsb_release -rd No LSB modules are available. Description: Ubuntu 23.04 Release: 23.04 ) 2) ┌─[surfer@M5-RGV]-[~] └──╼ $apt-cache policy pipewire pipewire: Installed: 0.3.65-3 Candidate: 0.3.65-3 Version table: *** 0.3.65-3 500 500 http://id.archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status 3) The Woofer/rear speaker should produce sound 4) Sound only comes from the pair of tweeter speaker ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: pipewire 0.3.65-3 Uname: Linux 6.3.5-060305-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Mon Jun 5 12:33:02 2023 InstallationDate: Installed on 2023-05-31 (4 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: pipewire UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2022879/+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 2022879] Re: No sound from Woofer speaker of Asus Zephyrus G14 2023
Here's the link for kernel update instructions and the Mainline tool: https://9to5linux.com/you-can-now-install-linux-kernel-6-7-on-ubuntu-heres-how -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2022879 Title: No sound from Woofer speaker of Asus Zephyrus G14 2023 Status in alsa-driver package in Ubuntu: New Status in pipewire package in Ubuntu: New Bug description: On Asus Zephyrus G14 2023, sound only comes out of the pair of tweeter speaker. The woofer speaker does not produce any sound at all on either on Analog Stereo, Analog Surround 4.0, or 2.1 configurations 1) ┌─[surfer@M5-RGV]-[~] └──╼ $lsb_release -rd No LSB modules are available. Description: Ubuntu 23.04 Release: 23.04 ) 2) ┌─[surfer@M5-RGV]-[~] └──╼ $apt-cache policy pipewire pipewire: Installed: 0.3.65-3 Candidate: 0.3.65-3 Version table: *** 0.3.65-3 500 500 http://id.archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status 3) The Woofer/rear speaker should produce sound 4) Sound only comes from the pair of tweeter speaker ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: pipewire 0.3.65-3 Uname: Linux 6.3.5-060305-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Mon Jun 5 12:33:02 2023 InstallationDate: Installed on 2023-05-31 (4 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: pipewire UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2022879/+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 2022879] Re: No sound from Woofer speaker of Asus Zephyrus G14 2023
I had this problem, and updating to Kernel 6.7.5 fixed it for me. I used the "Mainline kernel tool" to install the latest Kernel manually, it was easy and quick. AMD Ryzen 9 7940HS w/ Radeon 780M Graphics × 8 NVIDIA Corporation AD106M [GeForce RTX 4070 Max-Q / Mobile] Ubuntu 23.10 Mantic Minotaur (x86-64) Cinnamon version 5.8.4 Kernel 6.7.5-060705-generic Much Love to all! Thanks :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2022879 Title: No sound from Woofer speaker of Asus Zephyrus G14 2023 Status in alsa-driver package in Ubuntu: New Status in pipewire package in Ubuntu: New Bug description: On Asus Zephyrus G14 2023, sound only comes out of the pair of tweeter speaker. The woofer speaker does not produce any sound at all on either on Analog Stereo, Analog Surround 4.0, or 2.1 configurations 1) ┌─[surfer@M5-RGV]-[~] └──╼ $lsb_release -rd No LSB modules are available. Description: Ubuntu 23.04 Release: 23.04 ) 2) ┌─[surfer@M5-RGV]-[~] └──╼ $apt-cache policy pipewire pipewire: Installed: 0.3.65-3 Candidate: 0.3.65-3 Version table: *** 0.3.65-3 500 500 http://id.archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status 3) The Woofer/rear speaker should produce sound 4) Sound only comes from the pair of tweeter speaker ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: pipewire 0.3.65-3 Uname: Linux 6.3.5-060305-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Mon Jun 5 12:33:02 2023 InstallationDate: Installed on 2023-05-31 (4 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: pipewire UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2022879/+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 384062] Re: evince-thumbnailer with a 100% CPU usage
still there on ubuntu 18.04.5. @Adam's obervation is correct, deleting the pdf file (converted from ppt) resolve the problem. ** Attachment added: "nasa2015-NV-AMS_20150421_Posey.pdf" https://bugs.launchpad.net/ubuntu/+source/evince/+bug/384062/+attachment/5399799/+files/nasa2015-NV-AMS_20150421_Posey.pdf -- 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/384062 Title: evince-thumbnailer with a 100% CPU usage Status in evince package in Ubuntu: Fix Released Bug description: Binary package hint: evince Guys, There are some complains about evince-thumbnailer with a 100% CPU usage, but none of them could be replicated. I think I was able to track down the problem. Whenever I'm downloading a PDF and saving it on my desktop, the file changes at each second and every time it changes, evince-thumbnailer tries to create a new thumb for it, then having a 100% CPU usage. [INFO] Description: Ubuntu 8.04.2 Release: 8.04 evince: Installed: 2.22.2-0ubuntu2 Candidate: 2.22.2-0ubuntu2 Version table: *** 2.22.2-0ubuntu2 0 500 http://br.archive.ubuntu.com hardy-updates/main Packages 100 /var/lib/dpkg/status 2.22.1.1-0ubuntu1 0 500 http://br.archive.ubuntu.com hardy/main Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/384062/+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 492782] Re: [i945gme] Mouse cursor disappears after restarting screen (xrandr / resume)
As of 2019, using Ubuntu 18.04.2 LTS, this bug is still alive... When I invoke Xrandr the cursor disappears and I have to Alt-Ctrl-F1 and then Alt-Ctrl-F7 to make the cursor re-appear again. I'm using a relatively new BIOSTAR A68N-5600 motherboard newly bought in 2018. -- 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/492782 Title: [i945gme] Mouse cursor disappears after restarting screen (xrandr / resume) Status in xserver-xorg-video-intel package in Ubuntu: Fix Released Bug description: Binary package hint: xorg I use xrandr to activate my external monitor or set the screen size of my Asus Eee 900A PC. However, since the upgrade to Ubuntu Karmic, the mouse cursor disappears after using xrandr. I'm using xorg version 1:7.4+3ubuntu10 and Ubuntu 9.10. The commands I use are: xrandr --output LVDS --mode 800x600 xrandr --output LVDS --off --output VGA --mode 1280x1024 After using these commands, the mouse cursor disappears, but I can still focus and click. Moving the (suspected, but invisible) mouse cursor over a desktop item, highlits it and I can activate it by clicking. One temporarily solution I've found is to switch to the console (CTRL + ALT + F1) and back (CTRL + ALT + F7). This makes the mouse cursor reappear. Using xrandr to reset to the original settings doesn't bring the cursor back. ProblemType: Bug Architecture: i386 Date: Sat Dec 5 10:45:14 2009 DistroRelease: Ubuntu 9.10 Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: ASUSTeK Computer INC. 900A Package: xorg 1:7.4+3ubuntu10 ProcCmdLine: root=UUID=f2d72569-836f-4878-832e-3b9ad0270b07 ro quiet splash ProcEnviron: LANG=de_AT.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.28-12.43-hostname-eeepc RelatedPackageVersions: xserver-xorg 1:7.4+3ubuntu10 libgl1-mesa-glx 7.6.0-1ubuntu4 libdrm2 2.4.14-1ubuntu1 xserver-xorg-video-intel 2:2.9.0-1ubuntu2 xserver-xorg-video-ati 1:6.12.99+git20090929.7968e1fb-0ubuntu1 SourcePackage: xorg Tags: ubuntu-unr Uname: Linux 2.6.28-12-netbook-eeepc i686 XsessionErrors: (gnome-settings-daemon:2545): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed (gnome-settings-daemon:2545): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed (nautilus:2568): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed (polkit-gnome-authentication-agent-1:2578): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed dmi.bios.date: 10/27/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0703 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 900A dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTek Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0703:bd10/27/2008:svnASUSTeKComputerINC.:pn900A:pvrx.x:rvnASUSTeKComputerINC.:rn900A:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x: dmi.product.name: 900A dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. fglrx: Not loaded system: distro: Ubuntu architecture: i686kernel: 2.6.28-12-netbook-eeepc [lspci] 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GME Express Integrated Graphics Controller [8086:27ae] (rev 03) Subsystem: ASUSTeK Computer Inc. Device [1043:8340] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/492782/+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 1769383] Re: Ubuntu dock/launcher is shown on the lock screen
While I wholeheartedly agree that we urgently need an official fix, I also want to point out that gsettings set org.gnome.shell.extensions.dash-to-dock transparency-mode FIXED is an effective workaround for me. On my Cosmic, I have never seen the dock again on the lock screen. I'm using vanilla Ubuntu docker with no dash-to-docker or any other customization to the dock. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1769383 Title: Ubuntu dock/launcher is shown on the lock screen Status in gnome-shell package in Ubuntu: Invalid Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: Invalid Status in gnome-shell-extension-ubuntu-dock source package in Bionic: In Progress Status in gnome-shell source package in Cosmic: Invalid Status in gnome-shell-extension-ubuntu-dock source package in Cosmic: In Progress Status in gnome-shell source package in Disco: Invalid Status in gnome-shell-extension-ubuntu-dock source package in Disco: Fix Released Bug description: [Impact] When entering the lock-screen mode, gnome-shell disables all the extensions. It can happen that under certain conditions ubuntu-dock re-enables itself, causing the ubuntu-dock to appear in the lock-screen, exposing sensitive information. One possible way to reproduce this is to enable dash-to-dock and ubuntu-dock at the same time. [Test Case] 1. Make sure ubuntu-dock is enabled 2. Enable dash-to-dock too 3. Lock the screen 4. Make sure the dock does not appear on the lock screen 5. Make sure there is no warning is the journal [Possible Regressions] Even if it's something we don't really support please make sure that you can use dash-to-dock without uninstalling ubuntu-dock. [Original Bug] After an update from ubuntu 16.04 to 18.04 the dock is aviable on the lockscreen after user login. I did not configure this knowingly. Also i can start every application which is available on the dock. Settings, virtual box, visualstudio code and so on. After the update to 18.04 i just configure the screen frequency to 144Hz and the night mode on. And attach the dock on bottom. I later undid these customizations back to configuration before, but the dock is stil aviable on lockscreen. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat May 5 18:30:16 2018 InstallationDate: Installed on 2018-04-08 (27 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to bionic on 2018-05-01 (3 days ago) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-08 (27 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell-extension-ubuntu-dock 0.9.1 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-05-01 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769383/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1712866] Re: icons from qt applications disappear after screen lock/sleep
Also seeing this problem with 18.10 Cosmic. The offending Qt application is the VirtualBox from Ubuntu repo. ** Tags added: cosmic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1712866 Title: icons from qt applications disappear after screen lock/sleep Status in gnome-shell-extension-appindicator package in Ubuntu: Fix Released Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in gnome-shell-extension-appindicator source package in Artful: Fix Released Bug description: [Impact] Indicators of some Qt apps are not showing after unlocking the screen or shell restart. [Test case] - Login to 17.10 - launch dropbox (if not already launched) - Launch telegram (snap version or without libappindicator support) - Observe icons in taskbar - Lock screen with Super+L - Unlock screen - Icons should still be there [Possible regressions] Icons that should be hidden could be visible instead The fix doesn't apply to snapped applications In the Ubuntu Xorg session, with the Ubuntu Appindicator extension enabled, the tray icons for QT apps (in my case, both owncloud-client from the Ubuntu repos and enpass, from their own repo) show up after first logging in. But once the screen has been left idle long enough to be put to sleep, and is then woken up (I don't actually have screen *lock* enabled, but it still goes comes back to the clock screen and a further gesture is needed to scroll that up to get the desktop), then the icons for those QT apps are gone. Non-QT apps (eg: in my case hexchat, from the ubuntu repos) remain. For a while and due to inattention it seemed more random than that, but I'm fairly sure now it's just the display sleep/wake thing that kills it. The applications are still running in the background (so for instance enpass is still available via the browser extension), and can be seen in the process list. It's just the icons that have disappeared. If I then kill those apps (from the commandline with 'kill [pid]' because there's no other interface to do it from) and relaunch them, they reappear back in the appindicator area. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell-extension-appindicator 17.10 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.6-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 24 17:12:43 2017 Dependencies: InstallationDate: Installed on 2017-07-30 (24 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: gnome-shell-extension-appindicator UpgradeStatus: Upgraded to artful on 2017-08-22 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1712866/+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 1784065] [NEW] package libglib2.0-0 2.48.2-0ubuntu3 failed to install/upgrade: triggers ci file contains unknown directive `interest-await'
Public bug reported: Package failed to install. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libglib2.0-0 2.48.2-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134 Uname: Linux 4.4.0-131-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Fri Jul 27 18:31:08 2018 DuplicateSignature: package:libglib2.0-0:2.48.2-0ubuntu3 Preparing to unpack .../libglib2.0-0_2.48.2-0ubuntu3_amd64.deb ... dpkg: error processing archive /var/cache/apt/archives/libglib2.0-0_2.48.2-0ubuntu3_amd64.deb (--unpack): triggers ci file contains unknown directive `interest-await' ErrorMessage: triggers ci file contains unknown directive `interest-await' InstallationDate: Installed on 2015-03-31 (1213 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.27 SourcePackage: glib2.0 Title: package libglib2.0-0 2.48.2-0ubuntu3 failed to install/upgrade: triggers ci file contains unknown directive `interest-await' UpgradeStatus: Upgraded to xenial on 2018-07-27 (0 days ago) ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1784065 Title: package libglib2.0-0 2.48.2-0ubuntu3 failed to install/upgrade: triggers ci file contains unknown directive `interest-await' Status in glib2.0 package in Ubuntu: New Bug description: Package failed to install. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libglib2.0-0 2.48.2-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134 Uname: Linux 4.4.0-131-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Fri Jul 27 18:31:08 2018 DuplicateSignature: package:libglib2.0-0:2.48.2-0ubuntu3 Preparing to unpack .../libglib2.0-0_2.48.2-0ubuntu3_amd64.deb ... dpkg: error processing archive /var/cache/apt/archives/libglib2.0-0_2.48.2-0ubuntu3_amd64.deb (--unpack): triggers ci file contains unknown directive `interest-await' ErrorMessage: triggers ci file contains unknown directive `interest-await' InstallationDate: Installed on 2015-03-31 (1213 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.27 SourcePackage: glib2.0 Title: package libglib2.0-0 2.48.2-0ubuntu3 failed to install/upgrade: triggers ci file contains unknown directive `interest-await' UpgradeStatus: Upgraded to xenial on 2018-07-27 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1784065/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1583801] Re: No sound via headphones (headset) when Ubuntu boots with them plugged in
I believe the problem is kernel related, with the kernel 4.14 the problem is gone. Best regards, Chunxiang Yan On Fri, Dec 29, 2017 at 8:59 PM, Krešo Kunjas <der...@ubuntu-hr.org> wrote: > Well i have upgraded to 17.10, and problem dissapeared. Now it always > works. But i have tried some other fixes before, so i cannot know if al > of them are also needed. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1583801 > > Title: > No sound via headphones (headset) when Ubuntu boots with them plugged > in > > Status in alsa-driver package in Ubuntu: > Confirmed > > Bug description: > The bug is twofold, first when computer boots if the headset > (headphones with built-in mic, one audio jack) is plugged in, then > there is no sound (via headphones or otherwise). If you plug > headphones out and back in, then it usually works as expected. > > The second scenario is the same, except that plugging out and back in > again doesn't help. In that case, I just restart the laptop, then plug > them back in again and it works. > > In all cases, microphone works. > > ProblemType: Bug > DistroRelease: Ubuntu 16.04 > Package: alsa-base 1.0.25+dfsg-0ubuntu5 > ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 > Uname: Linux 4.4.0-22-generic x86_64 > NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia > ApportVersion: 2.20.1-0ubuntu2 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: crunch 3248 F pulseaudio > CurrentDesktop: Unity > Date: Thu May 19 22:13:20 2016 > InstallationDate: Installed on 2016-05-07 (12 days ago) > InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 > (20160420.1) > PackageArchitecture: all > SourcePackage: alsa-driver > Symptom: audio > Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed > Symptom_Card: Built-in Audio - HDA Intel PCH > Symptom_DevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: crunch 3248 F pulseaudio > Symptom_Jack: Black Headphone Out, Left > Symptom_Type: No sound at all > Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] No > sound at all > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 04/07/2016 > dmi.bios.vendor: Dell Inc. > dmi.bios.version: 01.02.00 > dmi.board.name: 0N7TVV > dmi.board.vendor: Dell Inc. > dmi.board.version: A00 > dmi.chassis.type: 9 > dmi.chassis.vendor: Dell Inc. > dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.: > pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: > dmi.product.name: XPS 15 9550 > dmi.sys.vendor: Dell Inc. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+ > bug/1583801/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1583801 Title: No sound via headphones (headset) when Ubuntu boots with them plugged in Status in alsa-driver package in Ubuntu: Confirmed Bug description: The bug is twofold, first when computer boots if the headset (headphones with built-in mic, one audio jack) is plugged in, then there is no sound (via headphones or otherwise). If you plug headphones out and back in, then it usually works as expected. The second scenario is the same, except that plugging out and back in again doesn't help. In that case, I just restart the laptop, then plug them back in again and it works. In all cases, microphone works. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crunch 3248 F pulseaudio CurrentDesktop: Unity Date: Thu May 19 22:13:20 2016 InstallationDate: Installed on 2016-05-07 (12 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crunch 3248 F pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [X
[Desktop-packages] [Bug 1583801] Re: No sound via headphones (headset) when Ubuntu boots with them plugged in
I can also confirm this bug. I have a dell 7560 with ALC3246. I tried 14.04, 16.04, 17.04 and None of them works. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1583801 Title: No sound via headphones (headset) when Ubuntu boots with them plugged in Status in alsa-driver package in Ubuntu: Confirmed Bug description: The bug is twofold, first when computer boots if the headset (headphones with built-in mic, one audio jack) is plugged in, then there is no sound (via headphones or otherwise). If you plug headphones out and back in, then it usually works as expected. The second scenario is the same, except that plugging out and back in again doesn't help. In that case, I just restart the laptop, then plug them back in again and it works. In all cases, microphone works. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crunch 3248 F pulseaudio CurrentDesktop: Unity Date: Thu May 19 22:13:20 2016 InstallationDate: Installed on 2016-05-07 (12 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crunch 3248 F pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1583801/+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 1665295] [NEW] package libreoffice-impress 1:4.2.8-0ubuntu4 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1
Public bug reported: I interrupted the autoupdate ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libreoffice-impress 1:4.2.8-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 Uname: Linux 4.4.0-62-generic i686 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: i386 Date: Tue Feb 14 22:43:26 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 1 InstallationDate: Installed on 2016-03-06 (347 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805) RelatedPackageVersions: dpkg 1.17.5ubuntu5.5 apt 1.0.1ubuntu2.11 SourcePackage: libreoffice Title: package libreoffice-impress 1:4.2.8-0ubuntu4 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 third-party-packages xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1665295 Title: package libreoffice-impress 1:4.2.8-0ubuntu4 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 Status in libreoffice package in Ubuntu: New Bug description: I interrupted the autoupdate ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libreoffice-impress 1:4.2.8-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 Uname: Linux 4.4.0-62-generic i686 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: i386 Date: Tue Feb 14 22:43:26 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 1 InstallationDate: Installed on 2016-03-06 (347 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805) RelatedPackageVersions: dpkg 1.17.5ubuntu5.5 apt 1.0.1ubuntu2.11 SourcePackage: libreoffice Title: package libreoffice-impress 1:4.2.8-0ubuntu4 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1665295/+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 1351286] Re: colord-sane assert failure: colord-sane: simple-watch.c:454: avahi_simple_poll_prepare: Assertion `s->state == STATE_INIT || s->state == STATE_DISPATCHED || s->sta
The problem has disappeared after I have plugged back my scanner (Mustek BearPaw 1200 TA) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1351286 Title: colord-sane assert failure: colord-sane: simple-watch.c:454: avahi_simple_poll_prepare: Assertion `s->state == STATE_INIT || s->state == STATE_DISPATCHED || s->state == STATE_FAILURE' failed. Status in sane-backends package in Ubuntu: Confirmed Bug description: Upgraded from 14.04 to 14.10 alpha. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: colord 1.2.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic x86_64 ApportVersion: 2.14.5-0ubuntu2 Architecture: amd64 AssertionMessage: colord-sane: simple-watch.c:454: avahi_simple_poll_prepare: Assertion `s->state == STATE_INIT || s->state == STATE_DISPATCHED || s->state == STATE_FAILURE' failed. Date: Fri Aug 1 14:00:57 2014 ExecutablePath: /usr/lib/colord/colord-sane InstallationDate: Installed on 2013-12-26 (217 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) ProcCmdline: /usr/lib/colord/colord-sane ProcEnviron: Signal: 6 SourcePackage: colord StacktraceTop: __assert_fail_base (fmt=0x7fcda3d688b0 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x7fcd926f9fb0 "s->state == STATE_INIT || s->state == STATE_DISPATCHED || s->state == STATE_FAILURE", file=file@entry=0x7fcd926f9ee8 "simple-watch.c", line=line@entry=454, function=function@entry=0x7fcd926fa140 "avahi_simple_poll_prepare") at assert.c:92 __GI___assert_fail (assertion=0x7fcd926f9fb0 "s->state == STATE_INIT || s->state == STATE_DISPATCHED || s->state == STATE_FAILURE", file=0x7fcd926f9ee8 "simple-watch.c", line=454, function=0x7fcd926fa140 "avahi_simple_poll_prepare") at assert.c:101 avahi_simple_poll_prepare () from /usr/lib/x86_64-linux-gnu/libavahi-common.so.3 avahi_simple_poll_iterate () from /usr/lib/x86_64-linux-gnu/libavahi-common.so.3 ?? () from /usr/lib/x86_64-linux-gnu/sane/libsane-kodakaio.so.1 Title: colord-sane assert failure: colord-sane: simple-watch.c:454: avahi_simple_poll_prepare: Assertion `s->state == STATE_INIT || s->state == STATE_DISPATCHED || s->state == STATE_FAILURE' failed. UpgradeStatus: Upgraded to utopic on 2014-07-31 (0 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1351286/+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 1286751] Re: gst-plugin-scanner hangs, eating CPU time
** Also affects: gstreamer1.0 Importance: Undecided Status: New ** No longer affects: gstreamer1.0 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1286751 Title: gst-plugin-scanner hangs, eating CPU time Status in gstreamer1.0 package in Ubuntu: Confirmed Bug description: Hi, gst-plugin-scanner is eating 100% CPU time which leads to unusable Ubuntu. It appears couple of times daily. (My guess is that it is causing by application firefox , skype , totem , nautilus ). Ubuntu 13.10 apt-cache policy libgstreamer0.10-0 libgstreamer0.10-0: Installed: 0.10.36-1.2ubuntu1 Candidate: 0.10.36-1.2ubuntu1 Version table: *** 0.10.36-1.2ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages 100 /var/lib/dpkg/status 0.10.36-1ubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ raring/main amd64 Packages apt-cache policy libgstreamer1.0-0 libgstreamer1.0-0: Installed: 1.2.0-1 Candidate: 1.2.0-1 Version table: *** 1.2.0-1 0 500 http://archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages 100 /var/lib/dpkg/status 1.0.6-1 0 500 http://archive.ubuntu.com/ubuntu/ raring/main amd64 Packages dpkg -l gstreamer*plugins* | grep ^ii ii gstreamer0.10-plugins-bad:amd64 0.10.23-7ubuntu2 amd64GStreamer plugins from the "bad" set ii gstreamer0.10-plugins-bad-multiverse 0.10.21-1ubuntu1 amd64GStreamer plugins from the "bad" set (Multiverse Variant) ii gstreamer0.10-plugins-base:amd64 0.10.36-1.1ubuntu1 amd64GStreamer plugins from the "base" set ii gstreamer0.10-plugins-base:i386 0.10.36-1.1ubuntu1 i386 GStreamer plugins from the "base" set ii gstreamer0.10-plugins-base-apps 0.10.36-1.1ubuntu1 amd64GStreamer helper programs from the "base" set ii gstreamer0.10-plugins-base-dbg:amd64 0.10.36-1.1ubuntu1 amd64GStreamer plugins from the "base" set ii gstreamer0.10-plugins-good:amd64 0.10.31-3+nmu1ubuntu3 amd64GStreamer plugins from the "good" set ii gstreamer0.10-plugins-good:i386 0.10.31-3+nmu1ubuntu3 i386 GStreamer plugins from the "good" set ii gstreamer0.10-plugins-ugly:amd64 0.10.19-2 amd64GStreamer plugins from the "ugly" set ii gstreamer1.0-plugins-bad:amd641.2.0-3ubuntu5 amd64GStreamer plugins from the "bad" set ii gstreamer1.0-plugins-base:amd64 1.2.0-1ubuntu1 amd64GStreamer plugins from the "base" set ii gstreamer1.0-plugins-base-apps1.2.0-1ubuntu1 amd64GStreamer helper programs from the "base" set ii gstreamer1.0-plugins-good:amd64 1.2.0-1ubuntu1 amd64GStreamer plugins from the "good" set ii gstreamer1.0-plugins-ugly:amd64 1.2.0-1 amd64GStreamer plugins from the "ugly" set ls -lA `sudo locate gst-plugin-scanner` # -rwxr-xr-x 1 u1 ajbos 6240 Mar 22 2013 /home/u1/.steam/ubuntu12_32/steam-runtime/amd64/usr/lib/x86_64-linux-gnu/gstreamer0.10/gstreamer-0.10/gst-plugin-scanner # -rwxr-xr-x 1 u1 ajbos 5544 Mar 22 2013 /home/u1/.steam/ubuntu12_32/steam-runtime/i386/usr/lib/i386-linux-gnu/gstreamer0.10/gstreamer-0.10/gst-plugin-scanner # -rwxr-xr-x 1 u1 ajbos 6240 Mar 22 2013 /home/u1/.steam/ubuntu12_32/steam-runtime.old/amd64/usr/lib/x86_64-linux-gnu/gstreamer0.10/gstreamer-0.10/gst-plugin-scanner # -rwxr-xr-x 1 u1 ajbos 5544 Mar 22 2013 /home/u1/.steam/ubuntu12_32/steam-runtime.old/i386/usr/lib/i386-linux-gnu/gstreamer0.10/gstreamer-0.10/gst-plugin-scanner # -rwxr-xr-x 1 root root 5564 May 7 2013 /usr/lib/i386-linux-gnu/gstreamer0.10/gstreamer-0.10/gst-plugin-scanner # -rwxr-xr-x 1 root root 6288 May 7 2013 /usr/lib/x86_64-linux-gnu/gstreamer0.10/gstreamer-0.10/gst-plugin-scanner # -rwxr-xr-x 1 root root 6288 Oct 1 21:58 /usr/lib/x86_64-linux-gnu/gstreamer1.0/gstreamer-1.0/gst-plugin-scanner Only help is: killall -9 gst-plugin-scanner (but it appears again sometimes.) I have attached: gst-inspect-1.0 > ~/gst-inspect-1.0.log gst-inspect-0.10 > ~/gst-inspect-0.10.log Kind Regards, Martin To manage notifications about this bug go to:
[Desktop-packages] [Bug 1434986] Re: Not working network connection after boot
This might be related: No internet connection through WLAN although connected to network https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1566987 -- 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/1434986 Title: Not working network connection after boot Status in NetworkManager: Expired Status in network-manager package in Ubuntu: Triaged Bug description: Directly after boot the network connections are not working. I am connected and have an IP address, but I cannot establish a connection with any Internet server. I have the impression it is related to thee DNS lookup, which waits forever for a result. Cycling the connection (disconnect->reconnect) seems to fix the problem for some time. I am reporting this against network-manager, but I am not sure if it is directly in network manager or if it is systemd related. With 14.10 everything worked perfectly. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu11 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Mar 22 12:38:26 2015 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-01-30 (50 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) IpRoute: default via 192.168.1.1 dev eth0 proto static metric 1024 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.26 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.29 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-03-19 (3 days ago) modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2015-02-16T00:14:50.662693 nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eth0ethernet connected /org/freedesktop/NetworkManager/Devices/2 Kabelnetzwerkverbindung 1 4a581685-6002-4401-a993-49aa649667eb /org/freedesktop/NetworkManager/ActiveConnection/4 wlan0 wifi connected /org/freedesktop/NetworkManager/Devices/1 4A616E7320574C414E f45aa3a7-fb44-41b7-a02a-ea9720d79414 /org/freedesktop/NetworkManager/ActiveConnection/3 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1434986/+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 1434986] Re: Not working network connection after boot
This might be related: https://bugzilla.gnome.org/show_bug.cgi?id=765578 I tried sudo systemctl enable NetworkManager.service, but in my case it didn't solve the problem. ** Bug watch added: GNOME Bug Tracker #765578 https://bugzilla.gnome.org/show_bug.cgi?id=765578 -- 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/1434986 Title: Not working network connection after boot Status in NetworkManager: Expired Status in network-manager package in Ubuntu: Triaged Bug description: Directly after boot the network connections are not working. I am connected and have an IP address, but I cannot establish a connection with any Internet server. I have the impression it is related to thee DNS lookup, which waits forever for a result. Cycling the connection (disconnect->reconnect) seems to fix the problem for some time. I am reporting this against network-manager, but I am not sure if it is directly in network manager or if it is systemd related. With 14.10 everything worked perfectly. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu11 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Mar 22 12:38:26 2015 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-01-30 (50 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) IpRoute: default via 192.168.1.1 dev eth0 proto static metric 1024 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.26 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.29 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-03-19 (3 days ago) modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2015-02-16T00:14:50.662693 nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eth0ethernet connected /org/freedesktop/NetworkManager/Devices/2 Kabelnetzwerkverbindung 1 4a581685-6002-4401-a993-49aa649667eb /org/freedesktop/NetworkManager/ActiveConnection/4 wlan0 wifi connected /org/freedesktop/NetworkManager/Devices/1 4A616E7320574C414E f45aa3a7-fb44-41b7-a02a-ea9720d79414 /org/freedesktop/NetworkManager/ActiveConnection/3 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1434986/+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 1316913] Re: wrong keybord layout at system start
Je confirme la présence de ce bug sur KUbuntu et nous sommes le 31/03/2015! Y a-til une solution pérenne ou Canonical se moque-t-il de ses utilisateurs? En effet vu l'ancienneté de ce problème on peut se poser des questions. Ma nièce et son conjoint sont nouveaux sur le système, c'est vraiment pas encourageant! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1316913 Title: wrong keybord layout at system start Status in lightdm package in Ubuntu: Confirmed Bug description: my system is set to german by default (De). When starting thunderbird and writing a new mail my keyboard is in qwerty mode. i must click on the De icon in the task bar to set it to qwertz mode. When updates need to be veriyfied with password i get wrong password - clicking the de icon in task bar sets it to german. thanks! ubuntu 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1316913/+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 1431654] Re: lightdm (1.2.3-0ubuntu2.6) 100%/high cpu usage
I can confirm this bug Solution with package version 1.2.3-0ubuntu2.7 works. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1431654 Title: lightdm (1.2.3-0ubuntu2.6) 100%/high cpu usage Status in lightdm package in Ubuntu: Fix Committed Bug description: Since updating lightdm today, one core of my CPU is always maxed out at 100%. I rolled back to version 1.2.3-0ubuntu2.5 and the issue stopped. I tried this with 2 different kernels: 3.2.0-77-generic and 3.2.0-79-generic and and version 1.2.3-0ubuntu2.6 of lightdm still caused 100% cpu usage. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: lightdm 1.2.3-0ubuntu2.6 ProcVersionSignature: Ubuntu 3.2.0-77.114-generic 3.2.66 Uname: Linux 3.2.0-77-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.8 Architecture: amd64 Date: Thu Mar 12 20:20:12 2015 ExecutablePath: /usr/sbin/lightdm InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MarkForUpload: True ProcEnviron: TERM=linux PATH=(custom, no user) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1431654/+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 1403448] [NEW] Kernel panic after fglrx update
Public bug reported: Hi This Friday i updated me system on laptop and rebooted. And system don't want to boot. I attached external keyboard to laptop and by boot saw kernel panic leds blinking. But i don't get any messages on my screen(external screen to). So i reinstalled my ubuntu 12.04(pure without updates to 12.04.*). Next step was installing fglrx driver from amd website(amd-driver-installer-catalyst-13.1-legacy-linux-x86.x86_64). I choose install with package generation. After installing generated packages i whanted to install updates. Updater suggested to update my fglrx to version 13.3(or something similar). But i have Ati HD 5145(renamed HD4570). For this cards is only 13.1-legacy suitable! 13.3 is For Radeon HD 54** and higher(newer). To avoid wrong driver installation i fixed package version in synaptic. unim95@unim95-ThikpadEdge:~$ lsb_release -rd Description:Ubuntu 12.04.5 LTS Release:12.04 Video: Ati HD5145 Driver: fglrx_8.970-0ubuntu1_amd64.deb ** Affects: fglrx-installer (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1403448 Title: Kernel panic after fglrx update Status in fglrx-installer package in Ubuntu: New Bug description: Hi This Friday i updated me system on laptop and rebooted. And system don't want to boot. I attached external keyboard to laptop and by boot saw kernel panic leds blinking. But i don't get any messages on my screen(external screen to). So i reinstalled my ubuntu 12.04(pure without updates to 12.04.*). Next step was installing fglrx driver from amd website(amd-driver-installer-catalyst-13.1-legacy-linux-x86.x86_64). I choose install with package generation. After installing generated packages i whanted to install updates. Updater suggested to update my fglrx to version 13.3(or something similar). But i have Ati HD 5145(renamed HD4570). For this cards is only 13.1-legacy suitable! 13.3 is For Radeon HD 54** and higher(newer). To avoid wrong driver installation i fixed package version in synaptic. unim95@unim95-ThikpadEdge:~$ lsb_release -rd Description: Ubuntu 12.04.5 LTS Release: 12.04 Video: Ati HD5145 Driver: fglrx_8.970-0ubuntu1_amd64.deb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1403448/+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 1385606] [NEW] Black screen when entering GDM login page
Public bug reported: Ubuntu version: Ubuntu GNOME 14.10 stable amd64 GDM version: 3.10.0.1-0ubuntu7 CPU Vendor: AMD GPU vendor: AMD Computer type: Laptop After fresh installing Ubuntu GNOME 14.10, everything was fine and I installed fglrx. However after I reboot my machine it just stuck between the start screen (with GNOME's footprint in the center) and the login page. It was a black screen but the screen is on because I could see the backlight. However I was able to change to a tty by pressing Ctrl+Alt+F1 and after I installed LightDM and made it as default my machine successfully booted into the login page and everything was fine. I think this is a bug related to GDM, fglrx, systemd and upstart. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: gdm 3.10.0.1-0ubuntu7 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Oct 25 16:42:43 2014 InstallationDate: Installed on 2014-10-24 (0 days ago) InstallationMedia: Ubuntu-GNOME 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: gdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug fglrx gdm systemd ubuntu-gnome utopic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/1385606 Title: Black screen when entering GDM login page Status in “gdm” package in Ubuntu: New Bug description: Ubuntu version: Ubuntu GNOME 14.10 stable amd64 GDM version: 3.10.0.1-0ubuntu7 CPU Vendor: AMD GPU vendor: AMD Computer type: Laptop After fresh installing Ubuntu GNOME 14.10, everything was fine and I installed fglrx. However after I reboot my machine it just stuck between the start screen (with GNOME's footprint in the center) and the login page. It was a black screen but the screen is on because I could see the backlight. However I was able to change to a tty by pressing Ctrl+Alt+F1 and after I installed LightDM and made it as default my machine successfully booted into the login page and everything was fine. I think this is a bug related to GDM, fglrx, systemd and upstart. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: gdm 3.10.0.1-0ubuntu7 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Oct 25 16:42:43 2014 InstallationDate: Installed on 2014-10-24 (0 days ago) InstallationMedia: Ubuntu-GNOME 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: gdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1385606/+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 1270957] Re: 13.10: screen does not turn off after x minutes of inactivity
It seems that upgrade to 14.04 has fixed the issue for me. -- 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/1270957 Title: 13.10: screen does not turn off after x minutes of inactivity Status in “gnome-control-center” package in Ubuntu: Incomplete Bug description: I've just upgraded from Ubuntu 13.04 to 13.10. All is apparently working fine except the screen that does not turn off anymore after the time defined in turn the screen off after xxx minutes. I saw that a similar bug was opened (#1228939) but is now considered as fixed. Indeed my bug is a little different: the option is correctly saved, but not applied. It seems, I'm not the only one to face this problem. I haven't found this bug in launchpad, except the closed one just mentionned. I see also this bug described here: http://ubuntuforums.org/showthread.php?t=2182779 and here (in French): http://forum.ubuntu-fr.org/viewtopic.php?pid=15456631 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1270957/+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 1270957] Re: 13.10: screen does not turn off after x minutes of inactivity
I have the same problem. After upgrading from 13.04 to 13.10 the screen no longer turns off after a certain time of inactivity. I have tested it also without having any applications open. It behaves consistently the same: the screen does not turn off. Following the advice from the ubuntu forums, when I type xset s 10 to the terminal, then the screen does turn off after 10 seconds (or whatever parameter I give it). However the screen does turn off when using the guest account without any tinkering on the command line. -- 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/1270957 Title: 13.10: screen does not turn off after x minutes of inactivity Status in “gnome-control-center” package in Ubuntu: Incomplete Bug description: I've just upgraded from Ubuntu 13.04 to 13.10. All is apparently working fine except the screen that does not turn off anymore after the time defined in turn the screen off after xxx minutes. I saw that a similar bug was opened (#1228939) but is now considered as fixed. Indeed my bug is a little different: the option is correctly saved, but not applied. It seems, I'm not the only one to face this problem. I haven't found this bug in launchpad, except the closed one just mentionned. I see also this bug described here: http://ubuntuforums.org/showthread.php?t=2182779 and here (in French): http://forum.ubuntu-fr.org/viewtopic.php?pid=15456631 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1270957/+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 1264590] [NEW] fglrx (not installed): fglrx kernel module failed to build
Public bug reported: older legacy ati driver(12.4) don't create dkms module ProblemType: Package DistroRelease: Ubuntu 12.04 Package: fglrx (not installed) ProcVersionSignature: Ubuntu 3.2.0-58.88-generic-pae 3.2.53 Uname: Linux 3.2.0-58-generic-pae i686 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: i386 DKMSKernelVersion: 3.2.0-58-generic-pae Date: Fri Dec 27 23:07:37 2013 MarkForUpload: True PackageVersion: (not installed) SourcePackage: fglrx-installer Title: fglrx (not installed): fglrx kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: fglrx-installer (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 precise -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1264590 Title: fglrx (not installed): fglrx kernel module failed to build Status in “fglrx-installer” package in Ubuntu: New Bug description: older legacy ati driver(12.4) don't create dkms module ProblemType: Package DistroRelease: Ubuntu 12.04 Package: fglrx (not installed) ProcVersionSignature: Ubuntu 3.2.0-58.88-generic-pae 3.2.53 Uname: Linux 3.2.0-58-generic-pae i686 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: i386 DKMSKernelVersion: 3.2.0-58-generic-pae Date: Fri Dec 27 23:07:37 2013 MarkForUpload: True PackageVersion: (not installed) SourcePackage: fglrx-installer Title: fglrx (not installed): fglrx kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1264590/+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 1241309] Re: Ubuntu 13.10 has no way to change individual input method settings
It also affects me. Hoping somebody to fix it soon. -- 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/1241309 Title: Ubuntu 13.10 has no way to change individual input method settings Status in “gnome-control-center” package in Ubuntu: Confirmed Status in “ibus” package in Ubuntu: Confirmed Status in “indicator-keyboard” package in Ubuntu: Confirmed Bug description: This is a UI problem that happens in Ubuntu 13.10, with the default (Unity) desktop. I live in Taiwan and use Chinese input methods. Other languages may differ. This is how I can change the individual settings of input methods in the old Ubuntu 12.04 LTS: (1) With iBus enabled, click on the keyboard icon on the upper right corner of the screen. Then click Preferences. (2) Set the Show language panel option to Always. (3) The language panel will appear somewhere on the screen, click on the Preferences icon. (4) Then I can set the options of the current input method, such as Bopomofo in the screenshot below. (screenshot:) https://www.dropbox.com/s/jwk28fap0ef7zi7/ubuntu-ime-individual-settings-1.png https://www.dropbox.com/s/5mrb1qfgx4u37rv/ubuntu-ime-individual-settings-2.png The procedure above can still work until Ubuntu 13.10. In Ubuntu 13.10, I don't see any way to show the setting of that Bopomofo input method, or Chewing, or whatever. And there is no option to Show language panel either. (screenshot:) https://www.dropbox.com/s/03i3duwmu8wc4mk/ubuntu-ime-individual-settings-3.png This problem is making me inconvenient to use. I hope this could be fixed soon. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1241309/+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 1187815] Re: No pdf file is generated when printing to file
I was confused with the print to file and cups-pdf. Turned out they are not the same. I installed the cups-pdf, whcih works like a charm. But this print to file does have a pdf output option but seems doing nothing just fooling the user. As a default printer in Ubuntu, what's the difference between this and the cups-pdf? Did I miss something so it did not produce any pdf file? ** Changed in: cups (Ubuntu) Status: New = Invalid ** Converted to question: https://answers.launchpad.net/ubuntu/+source/cups/+question/230377 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1187815 Title: No pdf file is generated when printing to file Status in “cups” package in Ubuntu: Invalid Bug description: Strange enough. The print to file function suddenly stops working maybe after I upgated the system days ago. I try to use the cups to print from Firefox,Thunderbird, everything looks normal, just no pdf file generated under my home folder even after I seach through the subdirectories. No error can be found in the cups log in /var/log/cups. Can any one shed some light on this? Thanks a lot! ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: cups 1.6.2-1ubuntu5 ProcVersionSignature: Ubuntu 3.8.0-23.34-generic 3.8.11 Uname: Linux 3.8.0-23-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Wed Jun 5 22:15:53 2013 InstallationDate: Installed on 2013-04-28 (37 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: ASUSTeK Computer Inc. K53SD MarkForUpload: True Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-23-generic root=UUID=ae46a583-95cb-467e-8b01-83419d362721 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/02/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K53SD.202 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K53SD dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK53SD.202:bd11/02/2011:svnASUSTeKComputerInc.:pnK53SD:pvr1.0:rvnASUSTeKComputerInc.:rnK53SD:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: K53SD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1187815/+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 1187815] [NEW] No pdf file is generated when printing to file
Public bug reported: Strange enough. The print to file function suddenly stops working maybe after I upgated the system days ago. I try to use the cups to print from Firefox,Thunderbird, everything looks normal, just no pdf file generated under my home folder even after I seach through the subdirectories. No error can be found in the cups log in /var/log/cups. Can any one shed some light on this? Thanks a lot! ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: cups 1.6.2-1ubuntu5 ProcVersionSignature: Ubuntu 3.8.0-23.34-generic 3.8.11 Uname: Linux 3.8.0-23-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Wed Jun 5 22:15:53 2013 InstallationDate: Installed on 2013-04-28 (37 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: ASUSTeK Computer Inc. K53SD MarkForUpload: True Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-23-generic root=UUID=ae46a583-95cb-467e-8b01-83419d362721 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/02/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K53SD.202 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K53SD dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK53SD.202:bd11/02/2011:svnASUSTeKComputerInc.:pnK53SD:pvr1.0:rvnASUSTeKComputerInc.:rnK53SD:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: K53SD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1187815 Title: No pdf file is generated when printing to file Status in “cups” package in Ubuntu: New Bug description: Strange enough. The print to file function suddenly stops working maybe after I upgated the system days ago. I try to use the cups to print from Firefox,Thunderbird, everything looks normal, just no pdf file generated under my home folder even after I seach through the subdirectories. No error can be found in the cups log in /var/log/cups. Can any one shed some light on this? Thanks a lot! ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: cups 1.6.2-1ubuntu5 ProcVersionSignature: Ubuntu 3.8.0-23.34-generic 3.8.11 Uname: Linux 3.8.0-23-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Wed Jun 5 22:15:53 2013 InstallationDate: Installed on 2013-04-28 (37 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: ASUSTeK Computer Inc. K53SD MarkForUpload: True Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-23-generic root=UUID=ae46a583-95cb-467e-8b01-83419d362721 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/02/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K53SD.202 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K53SD dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK53SD.202:bd11/02/2011:svnASUSTeKComputerInc.:pnK53SD:pvr1.0:rvnASUSTeKComputerInc.:rnK53SD:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: K53SD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1187815/+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 1039686] [NEW] gedit should depend on python-gi-cairo
Public bug reported: Environment: Lubuntu 12.04 Preconditions: python-gi-cairo NOT pre-installed Steps: 1) Install gedit (3.4.1) with default options 2) Enable snippets plugin (possibly gedit relaunch is needed) 3) Open any text document via __drag'n'drop___ Expected: 3) Document properly opened Actual: 3) Crash dump Error message shown: --- Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/gi/types.py, line 235, in mro return mro(cls) File /usr/lib/python2.7/dist-packages/gi/types.py, line 249, in mro bases_of_subclasses += list(map(mro, C.__bases__)) + [list(C.__bases__)] File /usr/lib/python2.7/dist-packages/gi/types.py, line 249, in mro bases_of_subclasses += list(map(mro, C.__bases__)) + [list(C.__bases__)] File /usr/lib/python2.7/dist-packages/gi/types.py, line 249, in mro bases_of_subclasses += list(map(mro, C.__bases__)) + [list(C.__bases__)] File /usr/lib/python2.7/dist-packages/gi/types.py, line 249, in mro bases_of_subclasses += list(map(mro, C.__bases__)) + [list(C.__bases__)] File /usr/lib/python2.7/dist-packages/gi/types.py, line 254, in mro not_head = [s for s in bases_of_subclasses if candidate in s[1:]] TypeError: Couldn't find conversion for foreign struct 'cairo.Context' ** ERROR:/build/buildd/pygobject-3.2.2/gi/_gobject/pygobject.c:929:pygobject_new_full: assertion failed: (tp != NULL) Aborted (core dumped) --- Notes (workaround): Snippets plugin seemes to exploit pyton-gi-cairo contained modules. Manually installing package solves the problem. Fix: Since snippets is a part of gedit package, python-gi-cairo should be added to dependencies list. ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Tags: gedit snippets -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1039686 Title: gedit should depend on python-gi-cairo Status in “gedit” package in Ubuntu: New Bug description: Environment: Lubuntu 12.04 Preconditions: python-gi-cairo NOT pre-installed Steps: 1) Install gedit (3.4.1) with default options 2) Enable snippets plugin (possibly gedit relaunch is needed) 3) Open any text document via __drag'n'drop___ Expected: 3) Document properly opened Actual: 3) Crash dump Error message shown: --- Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/gi/types.py, line 235, in mro return mro(cls) File /usr/lib/python2.7/dist-packages/gi/types.py, line 249, in mro bases_of_subclasses += list(map(mro, C.__bases__)) + [list(C.__bases__)] File /usr/lib/python2.7/dist-packages/gi/types.py, line 249, in mro bases_of_subclasses += list(map(mro, C.__bases__)) + [list(C.__bases__)] File /usr/lib/python2.7/dist-packages/gi/types.py, line 249, in mro bases_of_subclasses += list(map(mro, C.__bases__)) + [list(C.__bases__)] File /usr/lib/python2.7/dist-packages/gi/types.py, line 249, in mro bases_of_subclasses += list(map(mro, C.__bases__)) + [list(C.__bases__)] File /usr/lib/python2.7/dist-packages/gi/types.py, line 254, in mro not_head = [s for s in bases_of_subclasses if candidate in s[1:]] TypeError: Couldn't find conversion for foreign struct 'cairo.Context' ** ERROR:/build/buildd/pygobject-3.2.2/gi/_gobject/pygobject.c:929:pygobject_new_full: assertion failed: (tp != NULL) Aborted (core dumped) --- Notes (workaround): Snippets plugin seemes to exploit pyton-gi-cairo contained modules. Manually installing package solves the problem. Fix: Since snippets is a part of gedit package, python-gi-cairo should be added to dependencies list. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1039686/+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
