[Desktop-packages] [Bug 2044339] [NEW] Audio output doesnt work if laptop gets shut down with a headset plugged in
Public bug reported: Apologies if this is the wrong package. I am experiencing an issue with Ubuntu 22.04.1 LTS where the audio output doesnt work if previously device was shut down with a headset plugged in. Steps: - Device is up and running - Plug in headset (aux jack) - Turn off device - Plug out headset - Turn on device - No audio output In order to fix it, I have to plug the headset back in. Once plugged in, I get audio output on both the headset. While laptop is running, if I plug the headset out again, I get audio on the laptop's speakers too. I end up without any audio output. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- 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/2044339 Title: Audio output doesnt work if laptop gets shut down with a headset plugged in Status in pulseaudio package in Ubuntu: New Bug description: Apologies if this is the wrong package. I am experiencing an issue with Ubuntu 22.04.1 LTS where the audio output doesnt work if previously device was shut down with a headset plugged in. Steps: - Device is up and running - Plug in headset (aux jack) - Turn off device - Plug out headset - Turn on device - No audio output In order to fix it, I have to plug the headset back in. Once plugged in, I get audio output on both the headset. While laptop is running, if I plug the headset out again, I get audio on the laptop's speakers too. I end up without any audio output. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2044339/+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 1705369] Re: Ubuntu 17.10/18.04 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)
The last comment appliable to Laptop DNS H90MB with Intel GMA 3150 -- 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/1705369 Title: Ubuntu 17.10/18.04 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU) Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Invalid Status in nvidia-graphics-drivers-375 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-384 package in Ubuntu: Confirmed Bug description: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU) WORKAROUNDS: * Disable integrated graphics/GPU in your BIOS. * Add 'nomodeset' to your kernel command line. ORIGINAL DESCRIPTION: This bug is very similar to https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576 which is closed. I have been asked to open a new bug report. The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20, 2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04. - Lightdm works - Nouveau driver works - Nvidia driver 375.66 (proprietary) does not work - Nvidia driver 384.47 (open source) does not work (from https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa) - Nvidia drivers work with Ubuntu Gnome 17.04 I am using Nvidia GTX 1080 and Intel i7-4790K lsb_release -rd: Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 apt-cache policy gnome-shell: gnome-shell: Installed: 3.24.2-0ubuntu7 Candidate: 3.24.2-0ubuntu7 Version table: *** 3.24.2-0ubuntu7 500 500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status uname -s -r -v -p -i -o: Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1705369/+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 1705369] Re: Ubuntu 17.10/18.04 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)
Laptop Samsung NC110-P03RU Fix: in '/etc/gdm3/custom.conf' uncommenting #WaylandEnable=false to WaylandEnable=false -- 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/1705369 Title: Ubuntu 17.10/18.04 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU) Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Invalid Status in nvidia-graphics-drivers-375 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-384 package in Ubuntu: Confirmed Bug description: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU) WORKAROUNDS: * Disable integrated graphics/GPU in your BIOS. * Add 'nomodeset' to your kernel command line. ORIGINAL DESCRIPTION: This bug is very similar to https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576 which is closed. I have been asked to open a new bug report. The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20, 2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04. - Lightdm works - Nouveau driver works - Nvidia driver 375.66 (proprietary) does not work - Nvidia driver 384.47 (open source) does not work (from https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa) - Nvidia drivers work with Ubuntu Gnome 17.04 I am using Nvidia GTX 1080 and Intel i7-4790K lsb_release -rd: Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 apt-cache policy gnome-shell: gnome-shell: Installed: 3.24.2-0ubuntu7 Candidate: 3.24.2-0ubuntu7 Version table: *** 3.24.2-0ubuntu7 500 500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status uname -s -r -v -p -i -o: Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1705369/+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 1722319] Re: Totem Player not working correctly on 17.10 Beta 2
Ubuntu 17.10 In the wayland session the standart Video Player give error message "Input error stream". (VLC plays video). In Xorg session - OK. -- 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/1722319 Title: Totem Player not working correctly on 17.10 Beta 2 Status in gstreamer1.0 package in Ubuntu: Confirmed Bug description: I did a fresh install of Ubuntu 17.10 Beta 2 on my laptop - Dell Inspiron N4110, Intel Sandybridge Mobile Graphics, Intel® Core™ i3-2350M CPU @ 2.30GHz × 4, 6GB of RAM. If I try to play ANY video on the Totem movie player (the default GNOME player), I get sound and subtitles but no picture. VLC works just fine. This did not happen on my previous 14.04 install on the same laptop. Is this a beta OS bug or just a bad media player? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libgstreamer1.0-0 1.12.3-1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 9 08:31:37 2017 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2017-10-06 (3 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1722319/+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 1717985] [NEW] package texlive-latex-extra-doc 2016.20170123-5 failed to install/upgrade
Public bug reported: apt install tries to install texlive-latex-extra-doc continually ProblemType: Package DistroRelease: Ubuntu 17.04 Package: texlive-latex-extra-doc 2016.20170123-5 ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 AptOrdering: texlive-latex-extra-doc:amd64: Purge NULL: ConfigurePending NULL: PurgePending NULL: ConfigurePending Architecture: amd64 Date: Mon Sep 18 20:27:53 2017 DpkgTerminalLog: [1mdpkg:[0m ошибка при обработке пакета texlive-latex-extra-doc (--remove): пакет абсолютно неработоспособен; перед попыткой удаления его следует переустановить ErrorMessage: пакет абсолютно неработоспособен; перед попыткой удаления его следует переустановить InstallationDate: Installed on 2017-04-15 (155 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4.6~17.04.1 SourcePackage: texlive-extra Title: package texlive-latex-extra-doc 2016.20170123-5 failed to install/upgrade: пакет абсолютно неработоспособен; перед попыткой удаления его следует переустановить UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: texlive-extra (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package zesty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texlive-extra in Ubuntu. https://bugs.launchpad.net/bugs/1717985 Title: package texlive-latex-extra-doc 2016.20170123-5 failed to install/upgrade Status in texlive-extra package in Ubuntu: New Bug description: apt install tries to install texlive-latex-extra-doc continually ProblemType: Package DistroRelease: Ubuntu 17.04 Package: texlive-latex-extra-doc 2016.20170123-5 ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 AptOrdering: texlive-latex-extra-doc:amd64: Purge NULL: ConfigurePending NULL: PurgePending NULL: ConfigurePending Architecture: amd64 Date: Mon Sep 18 20:27:53 2017 DpkgTerminalLog: [1mdpkg:[0m ошибка при обработке пакета texlive-latex-extra-doc (--remove): пакет абсолютно неработоспособен; перед попыткой удаления его следует переустановить ErrorMessage: пакет абсолютно неработоспособен; перед попыткой удаления его следует переустановить InstallationDate: Installed on 2017-04-15 (155 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4.6~17.04.1 SourcePackage: texlive-extra Title: package texlive-latex-extra-doc 2016.20170123-5 failed to install/upgrade: пакет абсолютно неработоспособен; перед попыткой удаления его следует переустановить UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-extra/+bug/1717985/+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 1647031] Re: systemd-resolved’s 127.0.0.53 server does not follow CNAME records
The same issue as Sudeep Duggal say (Ubuntu 17.04 bug, Ubuntu 16.10
works fine).
--
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/1647031
Title:
systemd-resolved’s 127.0.0.53 server does not follow CNAME records
Status in Nextcloud:
Unknown
Status in systemd:
New
Status in network-manager package in Ubuntu:
Fix Released
Status in systemd package in Ubuntu:
Fix Released
Status in network-manager source package in Yakkety:
Invalid
Status in systemd source package in Yakkety:
Fix Committed
Bug description:
[SRU Justification]
Ubuntu 16.10 server uses systemd-resolved by default, configured both as a
DNS stub resolver on 127.0.0.53 and as an NSS module via libnss-resolved
talking to the dbus service. The DNS stub resolver has a bug that causes it to
fail to resolve CNAME records. This went unnoticed before release because by
default the NSS module is used. But a chroot or container on the system that
does not include libnss-resolved and is configured to use the stub resolver
will experience DNS failures.
[Test case]
1. On a yakkety server system, create a xenial chroot with mk-sbuild (or
equivalent).
2. Make sure that the host system has /etc/resolv.conf pointed at 127.0.0.53.
2. Enter the chroot with 'sudo schroot -c xenial-amd64' or such.
3. Install the iputils-ping package.
4. ping www.freedesktop.org
5. Confirm that the hostname does not resolve.
6. Install the systemd package from yakkety-proposed onto the host system.
7. ping www.freedesktop.org
8. Confirm that the hostname does now resolve.
[Regression potential]
With a 247-line patch to a key service, there is some risk of regression.
Regression risk is mitigated because this patch is already present in zesty and
upstream, where no regressions have been reported, and because it only touches
the DNS stub resolver which is not the code path used by default on host
systems.
$ systemd-resolve www.freedesktop.org
www.freedesktop.org: 131.252.210.176
2610:10:20:722:a800:ff:feda:470f
(annarchy.freedesktop.org)
-- Information acquired via protocol DNS in 673.6ms.
-- Data is authenticated: no
$ ping www.freedesktop.org
ping: www.freedesktop.org: Name or service not known
$ cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.
nameserver 127.0.0.53
$ dig +no{cmd,comments,stats} www.freedesktop.org @127.0.0.53
;www.freedesktop.org. IN A
www.freedesktop.org. 7146IN CNAME annarchy.freedesktop.org.
$ dig +no{cmd,comments,stats} www.freedesktop.org @8.8.8.8
;www.freedesktop.org. IN A
www.freedesktop.org. 14399 IN CNAME annarchy.freedesktop.org.
annarchy.freedesktop.org. 14399 IN A 131.252.210.176
I trust it needn’t be explained why this makes the internet almost
completely useless in zesty.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nextcloud-snap/+bug/1647031/+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
Ubuntu 16.10 has the same bug -- 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 1568604] Re: Mouse cursor lost when unlocking with Intel graphics
I have laptop with touchscreen when cursor lost I touch the screen and move invisible cursor in touchpad and cursor displayed I hope it will help in solving the problem -- 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/1568604 Title: Mouse cursor lost when unlocking with Intel graphics Status in elementary OS: Fix Released Status in xf86-video-intel: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Fix Released Status in xserver-xorg-video-intel-lts-xenial package in Ubuntu: Confirmed Status in xserver-xorg-video-intel source package in Xenial: Fix Released Status in xserver-xorg-video-intel package in Debian: Fix Released Bug description: [Relevant details] This bug also affects Trusty and all distributions based on it, like Elementary OS Freya. [Impact] Mouse cursor is no longer visible after VT-switch for systems with Intel graphics. Switching VTs again may cause the cursor to become visible again. - Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7) This is often observed in systems that lock the session and return to the greeter (including at least Xubuntu, Ubuntu Mate, and elementary OS). [Test Case] (Requires a lightdm-based screen locking solution) 1. Start a new session. 2. Lock your screen. 2a. You are redirected to the lightdm greeter. 3. Login/Unlock your session. 4. Cursor is no longer visible. [Regression Potential] remains to be seen === [Original Report] Cursor is visible at unlock screen either after returning from suspend or just locking. After unlocking screen cursor is invisible. Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7) cursor returns no matter if you suspend or sleep, to swap or disk when you return from it, the mouse cursor is missing.you can still move the mouse and you can see (because it highlights the window) as you move it around. But the cursor is not displayed on the screen. i am using a lenovo W540 laptop. I downloaded the latest beta on april 8 2016. this is xubuntu using the xfce window manager. the cursor does return if i log off and log back in, but that actually defeats the purpose of going to sleep. --- ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2016-04-08 (2 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia Package: light-locker 1.7.0-2ubuntu1 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Tags: xenial Uname: Linux 4.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1568604/+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 1615190] [NEW] Add mono-runtime to “Open With” menu
Public bug reported: After install mono-runtime I expect a adding "Mono Runtime" entry to “Open With” menu but this isn't appear. OS: Ubuntu 16.04.1 LTS [FIX] modify line "Exec=mono" in file /usr/share/applications/mono-runtime-common.desktop: Exec=mono %F ** Affects: mono (Ubuntu) Importance: Undecided Status: New ** Tags: menu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mono in Ubuntu. https://bugs.launchpad.net/bugs/1615190 Title: Add mono-runtime to “Open With” menu Status in mono package in Ubuntu: New Bug description: After install mono-runtime I expect a adding "Mono Runtime" entry to “Open With” menu but this isn't appear. OS: Ubuntu 16.04.1 LTS [FIX] modify line "Exec=mono" in file /usr/share/applications/mono-runtime-common.desktop: Exec=mono %F To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mono/+bug/1615190/+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 702452] Re: [launcher] Wine applications are wrongly matched
In wine-1.9.2 same bug -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bamf in Ubuntu. https://bugs.launchpad.net/bugs/702452 Title: [launcher] Wine applications are wrongly matched Status in BAMF: Confirmed Status in libwnck: Fix Released Status in Unity: Confirmed Status in Wine: Unknown Status in bamf package in Ubuntu: Triaged Status in unity package in Ubuntu: Triaged Bug description: After launching a Wine app from terminal or via gnome-do, it appears in the launcher with the Wine icon, instead of its own icon. The title is "Wine Window Program Loader" instead of the proper application name. It can't be favorited since it will favorite the wine executable itself. And obviously different wine apps are all grouped under the same launcher icon. See also bug #635223 about Wine applications not showing up in the dash. - A way to fix this is to make all the Wine generated .desktop file to include a StartupWMClass value that matches the instance name of the related program (generally the .exe file name to be executed). So for example, a "Mozilla Firefox.desktop" file can be easily fixed adding this parameter: StartupWMClass=firefox.exe Wine should try to add this information at file generation time. To manage notifications about this bug go to: https://bugs.launchpad.net/bamf/+bug/702452/+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 1226962] Re: Hotkeys not functional in non-latin keyboard layout in 13.10 and 14.04
** Also affects: monodevelop Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1226962 Title: Hotkeys not functional in non-latin keyboard layout in 13.10 and 14.04 Status in Aptana Studio Installer: New Status in Default settings for the Baltix GNU/Linux OS and desktop: New Status in LibreOffice Productivity Suite: Confirmed Status in IBus: New Status in Indicator keyboard: Fix Released Status in Inkscape: A Vector Drawing Tool: New Status in MonoDevelop: New Status in Mutter: Fix Released Status in The OpenOffice.org Suite: New Status in Unity: Fix Released Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “gnome-terminal” package in Ubuntu: Triaged Status in “indicator-keyboard” package in Ubuntu: Triaged Status in “openjdk-7” package in Ubuntu: Triaged Status in “sublime-text” package in Ubuntu: New Status in “unity” package in Ubuntu: Triaged Status in “unity-settings-daemon” package in Ubuntu: Triaged Status in “gnome-settings-daemon” package in Fedora: Unknown Status in “gnome-shell” package in Fedora: Unknown Bug description: New keyboard layout changer in Ubuntu 13.10 introduce old-new bug. Any system or application hotkey witch use char (for example: ctrl+alt+t for terminal or ctrl+t for new tab in browser) become unfunctional when selected non-latin keyboard layout. Hotkeys with F1-12, numbers and other non-character buttons works perfectly. Window manager hotkeys not affected by this bug. All hotkeys in system parameters-keyboard-hotkeys-windows works perfect with any keyboard layout. Workaround for some system hotkeys and two layouts (english and non- latin): rebind all hotkeys in your local layout. For example instead of ctrl+alt+t use ctrl+alt+τ (greek tau). That hotkey still work with english layout. If you use english and two different non-latin layouts this workaround helps only with one of them. Dear Ubuntu users and developers! Please include the following information to your comment about non-latin shortcuts problems: 1. What Ubuntu version do you have (Ubuntu 13.10, Ubuntu 13.10 GNOME, Ubuntu 14.04, Ubuntu 14.04 GNOME and so on), upgraded (describe version) or clean installed 2. What keyboard layout do you have 3. What shortcut for keyboard layout switching do you use 4. On which session you have problems - that is one from Unity, GNOME Shell, GNOME FlashBack/Fallback (Metacity), GNOME FlashBack/Fallback (Compiz) 5. With which program and its version and origin (Ubuntu repositories, PPA, non-deb binary package from some website) you have problems. By providing this information you can make bug-fixing much simpler and may be faster. -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- To manage notifications about this bug go to: https://bugs.launchpad.net/aptana-studio-installer/+bug/1226962/+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 1302885] Re: Media keyboard shortcuts not working
If you want set short combination from another functional buttons, do next: $ gsettings get org.gnome.settings-daemon.plugins.media-keys previous 'XF86AudioPrev' $ gsettings set org.gnome.settings-daemon.plugins.media-keys volume-down XF86AudioPrev $ gsettings reset org.gnome.settings-daemon.plugins.media-keys previous After reboot you can volume down with media previous button. P.s. Set short cut key in GUI settings, and set new value with add prefix XF86 in begin. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1302885 Title: Media keyboard shortcuts not working Status in “unity-control-center” package in Ubuntu: Confirmed Bug description: I can map the Volume Control keys in Keyboard Shortcuts e.g. Volume up/down to Volume up/down, but when I press the Volume keys on the keyboard nothing happens. I have noticed the same problem with other keys on my Logitech Internet 350 keyboard with Tools, Mail, and HomePage. They can all be mapped with Keyboard Shortcuts, but nothing happens afterwards when the keyboard key is pressed. All these keyboard settings worked fine in older versions of Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-control-center 14.04.3+14.04.20140328-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 Uname: Linux 3.13.0-22-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 4 23:49:58 2014 ExecutablePath: /usr/bin/unity-control-center InstallationDate: Installed on 2014-04-02 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140402) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_unity-control-center: activity-log-manager 0.9.7-0ubuntu12 deja-dup 30.0-0ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1302885/+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 1302885] Re: Media keyboard shortcuts not working
If you want set another functional key, do next, example: $ gsettings get org.gnome.settings-daemon.plugins.media-keys previous 'XF86AudioPrev' $ gsettings set org.gnome.settings-daemon.plugins.media-keys previous '' $ gsettings set org.gnome.settings-daemon.plugins.media-keys volume-down XF86AudioPrev After reboot you can volume down with media previous button. P.S. you can set in GUI settings need short-key, then from gsettings add XF86 prefix . -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1302885 Title: Media keyboard shortcuts not working Status in “unity-control-center” package in Ubuntu: Confirmed Bug description: I can map the Volume Control keys in Keyboard Shortcuts e.g. Volume up/down to Volume up/down, but when I press the Volume keys on the keyboard nothing happens. I have noticed the same problem with other keys on my Logitech Internet 350 keyboard with Tools, Mail, and HomePage. They can all be mapped with Keyboard Shortcuts, but nothing happens afterwards when the keyboard key is pressed. All these keyboard settings worked fine in older versions of Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-control-center 14.04.3+14.04.20140328-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 Uname: Linux 3.13.0-22-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 4 23:49:58 2014 ExecutablePath: /usr/bin/unity-control-center InstallationDate: Installed on 2014-04-02 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140402) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_unity-control-center: activity-log-manager 0.9.7-0ubuntu12 deja-dup 30.0-0ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1302885/+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 1242367] Re: gnome-control-center user-accounts don't load, only hangs
14.04 - freeze -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-good1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1242367 Title: gnome-control-center user-accounts don't load, only hangs Status in “gst-plugins-good1.0” package in Ubuntu: Confirmed Bug description: Description: Ubuntu 13.10 Release: 13.10 gnome-control-center: Установлен: 1:3.6.3-0ubuntu44 Кандидат: 1:3.6.3-0ubuntu44 Таблица версий: *** 1:3.6.3-0ubuntu44 0 500 http://ru.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages 100 /var/lib/dpkg/status Don't load. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu44 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Sun Oct 20 19:26:04 2013 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2013-10-19 (1 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager 0.9.7-0ubuntu4 deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20131016.2-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3+13.10.20131004-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good1.0/+bug/1242367/+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 1242367] Re: gnome-control-center user-accounts don't load, only hangs
** Changed in: gst-plugins-good1.0 (Ubuntu) Status: Incomplete = New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-good1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1242367 Title: gnome-control-center user-accounts don't load, only hangs Status in “gst-plugins-good1.0” package in Ubuntu: New Bug description: Description: Ubuntu 13.10 Release: 13.10 gnome-control-center: Установлен: 1:3.6.3-0ubuntu44 Кандидат: 1:3.6.3-0ubuntu44 Таблица версий: *** 1:3.6.3-0ubuntu44 0 500 http://ru.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages 100 /var/lib/dpkg/status Don't load. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu44 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Sun Oct 20 19:26:04 2013 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2013-10-19 (1 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager 0.9.7-0ubuntu4 deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20131016.2-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3+13.10.20131004-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good1.0/+bug/1242367/+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 1242367] Re: gnome-control-center user-accounts don't load, only hangs
$ gnome-control-center -v user-accounts ** (gnome-control-center:8486): DEBUG: Enabling debugging ** (gnome-control-center:8486): DEBUG: No extra argument (gnome-control-center:8486): user-accounts-cc-panel-DEBUG: calling 'ListCachedUsers' libv4l2: error getting pixformat: Неприменимый к данному устройству ioctl -- 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/1242367 Title: gnome-control-center user-accounts don't load, only hangs Status in “gnome-control-center” package in Ubuntu: Incomplete Bug description: Description: Ubuntu 13.10 Release: 13.10 gnome-control-center: Установлен: 1:3.6.3-0ubuntu44 Кандидат: 1:3.6.3-0ubuntu44 Таблица версий: *** 1:3.6.3-0ubuntu44 0 500 http://ru.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages 100 /var/lib/dpkg/status Don't load. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu44 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Sun Oct 20 19:26:04 2013 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2013-10-19 (1 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager 0.9.7-0ubuntu4 deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20131016.2-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3+13.10.20131004-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1242367/+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 1242367] Re: gnome-control-center user-accounts don't load, only hangs
(gdb) bt #0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x7f8af81be7e5 in v4l2_ioctl () from /usr/lib/x86_64-linux-gnu/libv4l2.so.0 #2 0x7f8b0038d04c in ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvideo4linux2.so #3 0x7f8b0037ec40 in ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvideo4linux2.so #4 0x7f8b00387f8d in ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvideo4linux2.so #5 0x7f8b13df31a2 in gst_element_change_state () from /usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0 #6 0x7f8b13df387c in ?? () from /usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0 #7 0x7f8b13dd95d9 in ?? () from /usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0 #8 0x7f8b13df31a2 in gst_element_change_state () from /usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0 #9 0x7f8b13df387c in ?? () from /usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0 #10 0x7f8b157192bd in ?? () from /usr/lib/x86_64-linux-gnu/libcheese.so.7 #11 0x7f8b3818411a in ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #12 0x7f8b38186294 in g_object_new_valist () ---Type return to continue, or q return to quit--- from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #13 0x7f8b388846d9 in g_initable_new_valist () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #14 0x7f8b388847cc in g_initable_new () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #15 0x7f8b15719aa4 in cheese_camera_device_new () from /usr/lib/x86_64-linux-gnu/libcheese.so.7 #16 0x7f8b1571a534 in cheese_camera_device_monitor_set_up_device () from /usr/lib/x86_64-linux-gnu/libcheese.so.7 #17 0x7f8b1571a62c in ?? () from /usr/lib/x86_64-linux-gnu/libcheese.so.7 #18 0x7f8b1571a6ef in ?? () from /usr/lib/x86_64-linux-gnu/libcheese.so.7 #19 0x7f8b37eb2ed8 in g_list_foreach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #20 0x7f8b1571a77e in cheese_camera_device_monitor_coldplug () from /usr/lib/x86_64-linux-gnu/libcheese.so.7 #21 0x7f8b1625523b in ?? () from /usr/lib/x86_64-linux-gnu/control-center-1/panels/libuser-accounts.so #22 0x7f8b1625fbe2 in ?? () from /usr/lib/x86_64-linux-gnu/control-center-1/panels/libuser-accounts.so #23 0x7f8b3819fc3b in g_type_create_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #24 0x7f8b381840e5 in ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ---Type return to continue, or q return to quit--- #25 0x7f8b38186294 in g_object_new_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #26 0x7f8b38186674 in g_object_new () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #27 0x00409e38 in ?? () #28 0x004074ea in _start () -- 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/1242367 Title: gnome-control-center user-accounts don't load, only hangs Status in “gnome-control-center” package in Ubuntu: Incomplete Bug description: Description: Ubuntu 13.10 Release: 13.10 gnome-control-center: Установлен: 1:3.6.3-0ubuntu44 Кандидат: 1:3.6.3-0ubuntu44 Таблица версий: *** 1:3.6.3-0ubuntu44 0 500 http://ru.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages 100 /var/lib/dpkg/status Don't load. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu44 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Sun Oct 20 19:26:04 2013 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2013-10-19 (1 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager 0.9.7-0ubuntu4 deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20131016.2-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3+13.10.20131004-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1242367/+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 1242367] Re: gnome-control-center user-accounts don't load, only hangs
I have averTV super 007 pci card -- 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/1242367 Title: gnome-control-center user-accounts don't load, only hangs Status in “gnome-control-center” package in Ubuntu: Incomplete Bug description: Description: Ubuntu 13.10 Release: 13.10 gnome-control-center: Установлен: 1:3.6.3-0ubuntu44 Кандидат: 1:3.6.3-0ubuntu44 Таблица версий: *** 1:3.6.3-0ubuntu44 0 500 http://ru.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages 100 /var/lib/dpkg/status Don't load. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu44 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Sun Oct 20 19:26:04 2013 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2013-10-19 (1 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager 0.9.7-0ubuntu4 deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20131016.2-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3+13.10.20131004-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1242367/+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 1242367] [NEW] gnome-control-center user-accounts don't load, only hangs
Public bug reported: Description:Ubuntu 13.10 Release:13.10 gnome-control-center: Установлен: 1:3.6.3-0ubuntu44 Кандидат: 1:3.6.3-0ubuntu44 Таблица версий: *** 1:3.6.3-0ubuntu44 0 500 http://ru.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages 100 /var/lib/dpkg/status Don't load. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu44 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Sun Oct 20 19:26:04 2013 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2013-10-19 (1 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager 0.9.7-0ubuntu4 deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20131016.2-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3+13.10.20131004-0ubuntu1 ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- 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/1242367 Title: gnome-control-center user-accounts don't load, only hangs Status in “gnome-control-center” package in Ubuntu: New Bug description: Description: Ubuntu 13.10 Release: 13.10 gnome-control-center: Установлен: 1:3.6.3-0ubuntu44 Кандидат: 1:3.6.3-0ubuntu44 Таблица версий: *** 1:3.6.3-0ubuntu44 0 500 http://ru.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages 100 /var/lib/dpkg/status Don't load. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu44 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Sun Oct 20 19:26:04 2013 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2013-10-19 (1 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager 0.9.7-0ubuntu4 deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20131016.2-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3+13.10.20131004-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1242367/+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 1100970] Re: [gen3] Dash background flickers on intel graphics
*** This bug is a duplicate of bug 1087534 *** https://bugs.launchpad.net/bugs/1087534 +1 Intel GMA 3150 -- 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/1100970 Title: [gen3] Dash background flickers on intel graphics Status in Nux: Confirmed Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Status in “xserver-xorg-video-intel” package in Ubuntu: Confirmed Bug description: The Unity dash flickers on my machine with intel graphics. Chipset: 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GSE Express Integrated Graphics Controller [8086:27ae] (rev 03) (prog-if 00 [VGA controller]) I have also tried activating SNA, xorg.log says: (II) intel(0): SNA initialized with gen3 backend But that does not change anything ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-0.4-generic 3.8.0-rc3 Uname: Linux 3.8.0-0-generic i686 NonfreeKernelModules: wl ApportVersion: 2.8-0ubuntu1 Architecture: i386 CurrentDmesg: Date: Thu Jan 17 22:42:15 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu InstallationDate: Installed on 2013-01-14 (3 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha i386 (20130114) MachineType: Dell Inc. Inspiron 1011 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-0-generic root=UUID=12622601-cc4f-48d2-861b-1d941ddf6b39 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: Section Device Identifier Card0 Driver intel Option AccelMethod sna EndSection dmi.bios.date: 07/29/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: CN0Y53 dmi.board.vendor: Dell Inc. dmi.board.version: A06 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A06 dmi.modalias: dmi:bvnDellInc.:bvrA06:bd07/29/2009:svnDellInc.:pnInspiron1011:pvrA06:rvnDellInc.:rnCN0Y53:rvrA06:cvnDellInc.:ct8:cvrA06: dmi.product.name: Inspiron 1011 dmi.product.version: A06 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.9~daily13.01.14-0ubuntu1 version.libdrm2: libdrm2 2.4.41-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.1-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.1-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.1.901-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.0.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.18-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.6-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/nux/+bug/1100970/+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
