[Desktop-packages] [Bug 1707352] Re: the change from libsane to libsane1 broke many (all?) 3rd party plug-ins for sane
Now the drivers install without problems. However, I still can't connect to the scanner (neither in iscan nor in simple-scan). Simple scan still tells me that an epson scanner is recognised, but drivers are missing. -- 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/1707352 Title: the change from libsane to libsane1 broke many (all?) 3rd party plug- ins for sane Status in sane-backends package in Ubuntu: Fix Released Status in sane-backends source package in Artful: Fix Committed Status in sane-backends package in Debian: New Bug description: Note to SRU Team The first proposed fix (1.0.27-1~experimental2ubuntu2) failed because it needed to be a versioned Provides, not just a Provides. Impact == 1) The Debian maintainer renamed libsane to libsane1-experimental "to match with the soname". This apparently fixes a Lintian warning, but makes installing 3rd-party plug-ins hard, as they typically depend on "libsane", not on "libsane1". The first try to add a "Provides: libsane" to libsane1 (which created a virtual package) didn't make drivers installable that claim to depend on a minimum version of libsane as virtual packages are ignored in this case. 2) The soname change might be justified by the new version breaking (several? most?) 3rd party plug-ins even if the library version number doesn't indicate any bigger change than any ordinary new version of the library - which might indicate that this phenomenon might be an upstream bug. libsane 1.0.25 in zesty includes libsane.so.1.25 libsane1 1.0.27 in artful includes libsane.so.1.27 It is to note that depending on the manufacturer for many old scanners there won't be new versions of the plug-ins that are recompiled like this. Test Case = Visit http://support.epson.net/linux/en/iscan_c.html Download the amd64 deb .tar.gz Unzip it. Install the iscan .deb from the core folder. It won't install before this SRU because it Depends: libsane Regression Potential The fix here was proposed to the Debian maintainer in July but there's been virtually zero response on it. In the meantime the workaround that was proposed initially has started to result in automatically uninstalling gtk - which makes the system basically useless. It doesn't seem like adding the Provides will make things any worse for third-party drivers but it has a goodme chance of making things better for some. Original Bug Report === I don't know if that can be prevented in the long run. But both brscan (for my brother scanner) and iscan (for my epson scanners) have been broken by the change from libsane to libsane1. For iscan I have unpackaged the debian package, changed the dependency it contains from libsane to libsane1 and installed the changed package. But even then my epson scanners no more work leaving me without any scanner => Reporting a bug. Impossibility of workarounds Just installing an old version of libsane is impossible as it uninstalls libgtk (which depends on libsane1 which conflicts with libsane) making the system basically useless. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental1ubuntu2 Uname: Linux 4.13.0-041300rc2-lowlatency x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 Date: Sat Jul 29 08:38:15 2017 EcryptfsInUse: Yes SourcePackage: sane-backends UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1707352/+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 1726753] Re: Après le démarrage de la session, et au bout de 30 secondes environ, un message apparaît signalant qu'une erreur s'est produite. D'autre part le clavier numérique
*** This bug is a duplicate of bug 1723342 *** https://bugs.launchpad.net/bugs/1723342 Plus précisément, il semble que le clavier numérique ne fonctionne pas dans firefox. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1726753 Title: Après le démarrage de la session, et au bout de 30 secondes environ, un message apparaît signalant qu'une erreur s'est produite. D'autre part le clavier numérique ne fonctionne pas. Status in nautilus package in Ubuntu: New Bug description: Il m'est difficile d'en dire plus. Sauf que je constate que ces bogues arrivent après la mise à niveau de Ubuntu 17.04 vers Ubuntu 17.10. trochet@trochet-ubuntu16:~$ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 Quel est le package utilisé juste après l'ouverture de session, étant donné que je n'ai rien ouvert? What you expected to happen? J'aimerais pouvoir continuer dans ma session. What happened instead? Sans etre dérangé par des messages d'erreur. Je viens aussi de voir que l'accent grave du verbe etre ne s'affiche pas. Avec la version précédente (Ubuntu 16.04 et 17.04) mon clavier (version Français-variante) fonctionnait parfaitement. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic i686 ApportVersion: 2.20.7-0ubuntu3 Architecture: i386 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 24 08:43:15 2017 ExecutablePath: /usr/bin/nautilus-desktop InstallationDate: Installed on 2015-10-07 (747 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422) ProcCmdline: nautilus-desktop ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: nautilus StacktraceTop: ?? () from /usr/lib/i386-linux-gnu/libX11.so.6 ?? () from /usr/lib/i386-linux-gnu/libX11.so.6 _XEventsQueued () from /usr/lib/i386-linux-gnu/libX11.so.6 XPending () from /usr/lib/i386-linux-gnu/libX11.so.6 ?? () from /usr/lib/i386-linux-gnu/libgdk-3.so.0 Title: nautilus-desktop crashed with signal 5 in _XEventsQueued() UpgradeStatus: Upgraded to artful on 2017-10-22 (1 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1726753/+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 1726753] Re: Après le démarrage de la session, et au bout de 30 secondes environ, un message apparaît signalant qu'une erreur s'est produite. D'autre part le clavier numérique
*** This bug is a duplicate of bug 1723342 *** https://bugs.launchpad.net/bugs/1723342 Il fonctionne dans LibreOffice Writter, dans Gedit et dans le terminal (c'est déjà bien!). Aujourd'hui, je n'ai pas eu de message d'erreur (jusqu'à maintenant). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1726753 Title: Après le démarrage de la session, et au bout de 30 secondes environ, un message apparaît signalant qu'une erreur s'est produite. D'autre part le clavier numérique ne fonctionne pas. Status in nautilus package in Ubuntu: New Bug description: Il m'est difficile d'en dire plus. Sauf que je constate que ces bogues arrivent après la mise à niveau de Ubuntu 17.04 vers Ubuntu 17.10. trochet@trochet-ubuntu16:~$ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 Quel est le package utilisé juste après l'ouverture de session, étant donné que je n'ai rien ouvert? What you expected to happen? J'aimerais pouvoir continuer dans ma session. What happened instead? Sans etre dérangé par des messages d'erreur. Je viens aussi de voir que l'accent grave du verbe etre ne s'affiche pas. Avec la version précédente (Ubuntu 16.04 et 17.04) mon clavier (version Français-variante) fonctionnait parfaitement. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic i686 ApportVersion: 2.20.7-0ubuntu3 Architecture: i386 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 24 08:43:15 2017 ExecutablePath: /usr/bin/nautilus-desktop InstallationDate: Installed on 2015-10-07 (747 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422) ProcCmdline: nautilus-desktop ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: nautilus StacktraceTop: ?? () from /usr/lib/i386-linux-gnu/libX11.so.6 ?? () from /usr/lib/i386-linux-gnu/libX11.so.6 _XEventsQueued () from /usr/lib/i386-linux-gnu/libX11.so.6 XPending () from /usr/lib/i386-linux-gnu/libX11.so.6 ?? () from /usr/lib/i386-linux-gnu/libgdk-3.so.0 Title: nautilus-desktop crashed with signal 5 in _XEventsQueued() UpgradeStatus: Upgraded to artful on 2017-10-22 (1 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1726753/+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 1724259] Re: gnome-shell frozen and using 100% CPU after docking and display configuration change
** Changed in: libinput Status: Unknown => In Progress ** Changed in: libinput Importance: Unknown => High -- 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/1724259 Title: gnome-shell frozen and using 100% CPU after docking and display configuration change Status in libinput: In Progress Status in gnome-shell package in Ubuntu: Incomplete Status in libinput package in Ubuntu: Confirmed Bug description: I have been having regular system freezes after switching from using my laptop stand-alone to waking it up on a docking station with an external monitor. I have seen this using two identical docking station plus monitor combinations. I am still trying to find a pattern. I was able to ssh in and use apport to save this bug information. The gnome-shell process was hung at 100% CPU utilisation. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 17 15:56:34 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: b'org.gnome.shell' b'command-history' b"['gnome-terminal']" b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'favorite-apps' b"['ubiquity.desktop', 'org.gnome.Nautilus.desktop', 'firefox.desktop', 'libreoffice-writer.desktop', 'libreoffice-calc.desktop', 'libreoffice-impress.desktop', 'org.gnome.Software.desktop', 'gnome-control-center.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2016-05-31 (504 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-10-05 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/libinput/+bug/1724259/+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 1727975] Re: package python-libxml2 2.9.3+dfsg1-1ubuntu0.3 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 1
** Package changed: libxml2 (Ubuntu) => python2.7 (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxml2 in Ubuntu. https://bugs.launchpad.net/bugs/1727975 Title: package python-libxml2 2.9.3+dfsg1-1ubuntu0.3 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 1 Status in python2.7 package in Ubuntu: New Bug description: it just failed! ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-libxml2 2.9.3+dfsg1-1ubuntu0.3 ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-37-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Fri Oct 27 16:17:09 2017 ErrorMessage: 子进程 已安装 post-installation 脚本 返回错误状态 1 InstallationDate: Installed on 2017-10-24 (2 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: libxml2 Title: package python-libxml2 2.9.3+dfsg1-1ubuntu0.3 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1727975/+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 1727975] [NEW] package python-libxml2 2.9.3+dfsg1-1ubuntu0.3 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 1
Public bug reported: it just failed! ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-libxml2 2.9.3+dfsg1-1ubuntu0.3 ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-37-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Fri Oct 27 16:17:09 2017 ErrorMessage: 子进程 已安装 post-installation 脚本 返回错误状态 1 InstallationDate: Installed on 2017-10-24 (2 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: libxml2 Title: package python-libxml2 2.9.3+dfsg1-1ubuntu0.3 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libxml2 (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 libxml2 in Ubuntu. https://bugs.launchpad.net/bugs/1727975 Title: package python-libxml2 2.9.3+dfsg1-1ubuntu0.3 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 1 Status in libxml2 package in Ubuntu: New Bug description: it just failed! ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-libxml2 2.9.3+dfsg1-1ubuntu0.3 ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-37-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Fri Oct 27 16:17:09 2017 ErrorMessage: 子进程 已安装 post-installation 脚本 返回错误状态 1 InstallationDate: Installed on 2017-10-24 (2 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: libxml2 Title: package python-libxml2 2.9.3+dfsg1-1ubuntu0.3 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/1727975/+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 291062] Re: MASTER - Network Manager sometimes has "enable networking" unchecked/disabled when resuming from suspend
Launchpad has imported 18 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=589108. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2010-05-05T12:26:11+00:00 Jerry wrote: Description of problem: Networking is disabled by state file after power loss drained laptop battery Version-Release number of selected component (if applicable): NetworkManager-0.8.0-7.git20100422.fc13.i686 How reproducible: always Steps to Reproduce: 1.login to KDE on laptop 2.disconnect power, and let battery die 3.plugin power and boot - no network. Actual results: no network management Expected results: network management Additional info: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=571331 Note in step 3. above there are actually two boots as the resume from power mgmt suspend never works for me - I force power off and restart. Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/291062/comments/54 On 2010-05-10T13:11:17+00:00 Oded wrote: I have the same problem after trying to recover from a failed suspend. Removing the state file at /var/lib/NetworkManager and restarting NetworkManager solved the problem for me. Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/291062/comments/55 On 2010-05-11T03:00:39+00:00 Justin wrote: Same issue here on a Dell Studio 1558, 03:00.0 Network controller: Intel Corporation Centrino Advanced-N 6200 (rev 35), NetworkManager-0.8.0-13.git20100509.fc13 Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/291062/comments/56 On 2010-05-16T11:22:23+00:00 Joel wrote: Additional evidence: I had this happen to me, apparently when my daughter accidentally hit the sleep button on the keyboard or selected hibernate instead of shutdown from the shutdown menu. The file mentioned above, /var/lib/NetworkManager/NetworkManager.state shows the wired network disabled and the wireless enabled. The box is a desktop, by the way, not a laptop. No battery. No wireless hardware of any sort. 32 bit, single CPU Sempron. (Should I attach a dmesg?) Oh, and it's running Fedora 12. Editing the file instead of deleting it also seems to unclog the networking stuff. Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/291062/comments/57 On 2010-05-17T23:55:41+00:00 Dan wrote: *** Bug 592505 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/291062/comments/58 On 2010-05-18T00:10:11+00:00 Dan wrote: *** Bug 552233 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/291062/comments/59 On 2010-05-19T21:46:39+00:00 Richard wrote: When this symptom has happened to me, the following command instantly fixes it: nmcli nm wakeup The circumstances seem to be that NM sets NetworkingEnabled to false in the /var/lib/NetworkManager/NetworkManager.state file but the situation can arise where NM cannot reset it. My guess is that this flag is set at suspend time (and of course at 'nmcli nm sleep' time as well). Further, I guess that NM expects a 'suspend' to be followed by a 'resume', which should reset this flag to be NetworkingEnabled=true. But if the latter fails, as it stands manual intervention is reqired. The failure can occur in at least these two ways: the hardware's suspend function is broken and a power-on reboot is required, and the battery discharges and a power-on reboot is required. The NetworkingEnabled=false flag remains set in these cases, and manual intervention is required. But a naïve user is at a complete loss what to do. Even sophisticated users, e.g., helpers on the #fedora channel of freenode, are at a loss, as I've seen. NM should perhaps set the flag to true when freshly started? What are the exact and complete semantics of this NetworkingEnabled=false flag? Is there a valid case where a freshly started NetworkManager service can expect NetworkingEnabled=false to be the proper setting? If there is, could a freshly started NM pop up a graphic window asking the user if enabling was okay? Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/291062/comments/60
[Desktop-packages] [Bug 548652] Re: menu mouse-scrolling broken, when themes enable gtk-auto-mnemonics
Launchpad has imported 15 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=582804. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2010-04-15T20:14:46+00:00 Bruno wrote: Description of problem: When I scroll down in a menu (say the graphics menu entries) that is too large to fit on the screen the menu items listed scrolls. But when I move the mouse back to select an item I made visible, the menu snaps back to the top preventing selection of the desired item if it isn't visible while at the top of the menu. I am not sure exactly when this changed or which component is responsible. If this can be confirmed it should probably be marked as a release blocker. Version-Release number of selected component (if applicable): gnome-desktop-2.30.0-1.fc13.i686 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: Reply at: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/548652/comments/7 On 2010-04-16T15:24:07+00:00 Bruno wrote: I have another machine at work with a similar package set installed that isn't exhibiting this problem. So I need to look and see what's different. Reply at: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/548652/comments/8 On 2010-04-19T15:10:44+00:00 Bruno wrote: I still haven't figured out why one machine has that problem. I have three other f13 machines that I haven't been able to duplicate the problem on. Reply at: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/548652/comments/9 On 2010-04-21T02:05:49+00:00 Bruno wrote: I played with this some more and it doesn't do it on all of the large menu lists. But it isn't consistent about which ones it happens with. Reply at: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/548652/comments/10 On 2010-04-28T14:29:08+00:00 Bruno wrote: I found that this issue is related to the theme being used. On the machine with problems I usually use Fedora with Echo icons. When I tried using Bluecurve (with or without Echo Icons) I didn't see the problem. Switching back caused it to reappear. I need to check to see if I have a corrupted install of that theme and whether or not the same problem is visible on a couple of other machines. (I typically don't mess with the theme on my scratchish machines, so they are probably using Bluecurve.) Reply at: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/548652/comments/12 On 2010-04-28T14:36:01+00:00 Bruno wrote: I did see that Fedora really is just Clearlooks. And selecting the Clearlooks theme also resulted in having the menu selection issue. Reply at: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/548652/comments/13 On 2010-04-28T16:10:00+00:00 Bruno wrote: I am seeing this on a second computer now. I have it occurring on both i686 and x86_64 arches. I am having trouble reproducing it on an i686 machine that doesn't have the kitchen sink installed on it. My next plan is try to some older versions of the Clearlooks theme. Even if that isn't the root of the problem, being able to isolate what triggers it would be useful to know. I might also try older desktops, but that seems likely to be a lot more involved. Reply at: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/548652/comments/14 On 2010-04-28T18:25:15+00:00 Bruno wrote: I looked and gnome-theme-curvylooks has changed for about 9 months which predates me seeing the issue. So it seems unlikely to be something triggered by a change in that package. Reply at: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/548652/comments/15 On 2010-05-04T20:15:03+00:00 Colin wrote: Me too. Worked in F12 on same hardware. See also ubuntu: https://bugs.launchpad.net/fedora/+bug/548652 Reply at: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/548652/comments/16 On 2010-05-29T18:42:28+00:00 Erwan wrote: Same issue after a upgrade from F12. Reply at: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/548652/comments/19 On
[Desktop-packages] [Bug 583728] Re: NetworkManager ignores the rfcomm port when it gets registered in blueman
Launchpad has imported 9 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=585487. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2010-04-24T10:33:43+00:00 Zdravko wrote: Description of problem: Version-Release number of selected component (if applicable): ModemManager-0.3-9.git20100409.fc12.i686 NetworkManager-0.8.0-6.git20100408.fc12.i686 How reproducible: Always Steps to Reproduce: 1. Connect to a bluetooth dun dial-up network service on a gsm phone using blueman Actual results: Blueman displays a message that the modem connection is available via NetworkManager but no Wireless Modem connection is available in NM Expected results: The connection should be available in NM an it should be able to connect. Additional info: This worked perfect before the update of NM and ModemManager Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/583728/comments/0 On 2010-04-25T06:22:41+00:00 Dan wrote: NetworkManager includes built-in Bluetooth DUN support. You'll want to set up a DUN connection via the bluetooth icon's "Set up new device..." wizard. After you've completed that step, if the connection does not appear in the NM menu, we'll want to grab some logs to figure out what's going on. Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/583728/comments/1 On 2010-04-25T12:59:48+00:00 Zdravko wrote: I have done exactly that but no device shows up in NM. As I said it worked fine prior to the update (also reverting back to previous NM and MM made it work again..) Below is the log.. Apr 25 13:49:35 X41 bluetoothd[2339]: link_key_request (sba=00:14:A4:DC:38:D6, dba=34:7E:39:5B:B1:08) Apr 25 13:49:35 X41 bluetoothd[2339]: pin_code_request (sba=00:14:A4:DC:38:D6, dba=34:7E:39:5B:B1:08) Apr 25 13:49:46 X41 bluetoothd[2339]: link_key_notify (sba=00:14:A4:DC:38:D6, dba=34:7E:39:5B:B1:08, type=0) Apr 25 13:49:46 X41 dbus-daemon: Rejected send message, 2 matched rules; type="method_return", sender=":1.69" (uid=500 pid=2362 comm="/usr/bin/python) interface="(unset)" member="(unset)" error name="(unset)" requested_reply=0 destination=":1.64" (uid=0 pid=2338 comm="/usr/sbin/bluetoothd)) Apr 25 13:49:46 X41 bluetoothd[2339]: probe failed with driver input-headset for device /org/bluez/2338/hci0/dev_34_7E_39_5B_B1_08 Apr 25 13:49:50 X41 bluetoothd[2339]: link_key_request (sba=00:14:A4:DC:38:D6, dba=34:7E:39:5B:B1:08) Apr 25 13:49:50 X41 modem-manager: (rfcomm0) opening serial device... Apr 25 13:49:51 X41 modem-manager: (rfcomm0) closing serial device... Apr 25 13:49:51 X41 modem-manager: Generic: (tty/rfcomm0) WARNING: missing udev 'device' file Apr 25 13:49:51 X41 modem-manager: (rfcomm0) opening serial device... Apr 25 13:49:51 X41 modem-manager: (Generic): GSM modem /sys/devices/pci:00/:00:1d.2/usb4/4-1 claimed port rfcomm0 Apr 25 13:49:51 X41 modem-manager: (rfcomm0) closing serial device... Apr 25 13:49:51 X41 NetworkManager: ignoring modem 'rfcomm0' (no associated Bluetooth device) Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/583728/comments/2 On 2010-04-26T06:08:53+00:00 Dan wrote: Ok, this shows that ModemManager is finding the modem correctly, but the configuration that NM requires (that the bluetooth wizard is supposed to write to GConf) somehow isn't getting set correctly. Any chance you can take a screenshot of the applet menu for me after you've completed the bluetooth wizard? And you are using the gnome- bluetooth icon to set up the device, *not* blueman, correct? Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/583728/comments/3 On 2010-04-26T10:15:13+00:00 Zdravko wrote: Created attachment 409128 Screenshot I am using only blueman..A screenshot is attached.. Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/583728/comments/4 On 2010-04-26T22:32:35+00:00 Dan wrote: You're going to need to use the gnome-bluetooth applet, not blueman. I have no idea what blueman is doing underneath, but it's not really a supported way to interact with NetworkManager. NM has the functionality that you're looking for, so if there's a problem with NM or nm-applet's handling of DUN, then we can try to fix this bug. But otherwise, it's a blueman bug. The nm-applet GConf data is an implementation detail that's not public
[Desktop-packages] [Bug 616517] Re: CVE-2010-1172 dbus-glib: property access not validated
Launchpad has imported 9 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=585394. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2010-04-23T21:16:19+00:00 Colin wrote: The desktop team recently discovered a flaw in dbus-glib where it didn't respect the "access" flag on properties specified. Basically, core OS services like NetworkManager which use dbus-glib were specifying e.g. the "Ip4Address" as read-only for remote access, but in fact any process could modify it. I have a patch for dbus-glib (attached). However, due to the nature of the way dbus-glib works where at build time services generate a C data structure from XML and embed it into their binary, affected services will need to be rebuilt (though not patched). This affected list is for F-12; I think for RHEL5 we just need dbus-glib and NetworkManager. KNOWN AFFECTED SERVICES: * DeviceKit-Power * NetworkManager * ModemManager KNOWN NOT AFFECTED that claim to handle org.freedesktop.DBus.Properties: * ConsoleKit (it denies all Properties access using dbus policy) * gdm (ditto) * PackageKit (all of the properties on exposed GObjects are G_PARAM_READONLY) KNOWN NOT AFFECTED (because I audited them) * gnome-panel (no dbus properties) * gnome-system-monitor (ditto) PROBABLY NOT AFFECTED * hal (doesn't claim to handle org.freedesktop.DBus.Properties) * polkit (uses eggdbus) * rtkit (doesn't use dbus-glib) * DeviceKit-disks (all its properties appear to be readonly) * wpa_supplicant (doesn't implement Properties) * upstart (doesn't use dbus-glib) Reply at: https://bugs.launchpad.net/ubuntu/+source/dbus- glib/+bug/616517/comments/0 On 2010-04-23T21:28:02+00:00 Colin wrote: Created attachment 408742 respect property access flags Note that affected services will need to be recompiled. Reply at: https://bugs.launchpad.net/ubuntu/+source/dbus- glib/+bug/616517/comments/1 On 2010-04-23T21:46:47+00:00 Vincent wrote: This has been assigned CVE-2010-1172 Reply at: https://bugs.launchpad.net/ubuntu/+source/dbus- glib/+bug/616517/comments/2 On 2010-04-27T20:46:43+00:00 Colin wrote: Created attachment 409584 0001-Respect-property-access-flags-for-writing-allow-disa.patch Updated patch; this one exercises the legacy disabled cased. Reply at: https://bugs.launchpad.net/ubuntu/+source/dbus- glib/+bug/616517/comments/3 On 2010-04-27T22:22:28+00:00 Dan wrote: Latest patch appears to allow setting properties listed as 'access=read' even though I"ve disabled legacy property access: NetworkManager: object_registration_message: prop lookup name 'ip4_address' NetworkManager: check_property_access: iface org.freedesktop.NetworkManager.Device name Ip4Address (is set 0) NetworkManager: check_property_access: iface org.freedesktop.NetworkManager.Device name Ip4Address (access type readwrite) NetworkManager: object_registration_message: prop lookup name 'ip4_address' NetworkManager: check_property_access: iface org.freedesktop.NetworkManager.Device name Ip4Address (is set 1) NetworkManager: check_property_access: iface org.freedesktop.NetworkManager.Device name Ip4Address (access type readwrite) NetworkManager: object_registration_message: prop lookup name 'ip4_address' NetworkManager: check_property_access: iface org.freedesktop.NetworkManager.Device name Ip4Address (is set 0) NetworkManager: check_property_access: iface org.freedesktop.NetworkManager.Device name Ip4Address (access type readwrite) but introspection/nm-device.xml lists Ip4Address as access=read. Also, you can kill the: /* Try both forms of property names: "foo_bar" or "FooBar"; for historical * reasons we accept both. */ if (object_info && !(property_info_from_object_info (object_info, wincaps_propiface, requested_propname, _type) 'object_info' check there now in check_property_access since there's a check for if (!object_info) just above. Reply at: https://bugs.launchpad.net/ubuntu/+source/dbus- glib/+bug/616517/comments/4 On 2010-04-27T22:52:58+00:00 Dan wrote: Nevermind about the Ip4Address thing, needed a clean rebuild locally. So the latest patch looks good to me. Reply at: https://bugs.launchpad.net/ubuntu/+source/dbus- glib/+bug/616517/comments/5 On 2010-08-09T15:21:00+00:00 Colin wrote: Created attachment 437622 patch against dbus-glib git
[Desktop-packages] [Bug 548992] Re: Wireless connection frequently drops [deauthenticating by local choice (reason=3)]
** Changed in: fedora Status: Unknown => Fix Released ** Changed in: fedora Importance: Unknown => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpasupplicant in Ubuntu. https://bugs.launchpad.net/bugs/548992 Title: Wireless connection frequently drops [deauthenticating by local choice (reason=3)] Status in Linux: New Status in linux package in Ubuntu: Fix Released Status in wpasupplicant package in Ubuntu: Invalid Status in linux package in Arch Linux: New Status in Debian: Confirmed Status in Fedora: Fix Released Status in linux package in openSUSE: New Bug description: Since about 8.04 or 8.10, perhaps when Ubuntu switched over to NetworkManager, my wireless connection has randomly dropped its association with the access point, about every ten minutes. For a while, the connection will just die, then it will be detected and NetworkManager will re-authenticate and re-associate. In Lucid Lynx, this problem is now much more frequent (often exactly every two or four minutes) and now Ubuntu does not report that the connection has dropped. Instead, it re-associates in the background, eventually connecting to the access point again, all behind the scenes. Thus, the only thing that has changed, aside from the greater frequency, is that Ubuntu now doesn't report that it has dropped the connection, which seems deceptive from previous versions. This may be the same bug as bug 429035, but my dmesg output is a bit different. This problem occurs primarily on a WPA2 Enterprise network, but the problem has occurred on other network security configurations as well. dmesg output after many instances of disconnects: [ 5423.541343] wlan0: deauthenticating from 00:26:cb:17:bd:41 by local choice (reason=3) [ 5425.134984] wlan0: deauthenticating from 00:26:cb:17:bd:41 by local choice (reason=3) [ 5425.174916] wlan0: direct probe to AP 00:26:cb:17:bd:41 (try 1) [ 5425.177083] wlan0: direct probe responded [ 5425.177087] wlan0: authenticate with AP 00:26:cb:17:bd:41 (try 1) [ 5425.179379] wlan0: authenticated [ 5425.179399] wlan0: associate with AP 00:26:cb:17:bd:41 (try 1) [ 5425.182881] wlan0: RX AssocResp from 00:26:cb:17:bd:41 (capab=0x431 status=0 aid=68) [ 5425.182884] wlan0: associated [ 5437.562165] iwlagn :0b:00.0: iwl_tx_agg_start on ra = 00:26:cb:17:bd:41 tid = 0 [ 5480.893417] wlan0: deauthenticating from 00:26:cb:17:bd:41 by local choice (reason=3) [ 5482.475859] wlan0: deauthenticating from 00:26:cb:17:bd:41 by local choice (reason=3) [ 5482.515034] wlan0: direct probe to AP 00:26:cb:17:bd:41 (try 1) [ 5482.517187] wlan0: direct probe responded [ 5482.517190] wlan0: authenticate with AP 00:26:cb:17:bd:41 (try 1) [ 5482.518636] wlan0: authenticated [ 5482.518651] wlan0: associate with AP 00:26:cb:17:bd:41 (try 1) [ 5482.522378] wlan0: RX AssocResp from 00:26:cb:17:bd:41 (capab=0x431 status=0 aid=68) [ 5482.522381] wlan0: associated [ 5508.093339] wlan0: deauthenticating from 00:26:cb:17:bd:41 by local choice (reason=3) [ 5508.107358] wlan0: direct probe to AP 00:26:cb:17:bd:41 (try 1) [ 5508.107412] wlan0: deauthenticating from 00:26:cb:17:bd:41 by local choice (reason=3) [ 5508.110595] wlan0: direct probe to AP 00:26:cb:16:e8:d1 (try 1) [ 5508.113114] wlan0: direct probe responded [ 5508.113123] wlan0: authenticate with AP 00:26:cb:16:e8:d1 (try 1) [ 5508.115392] wlan0: authenticated [ 5508.121973] wlan0: associate with AP 00:26:cb:16:e8:d1 (try 1) [ 5508.127254] wlan0: RX AssocResp from 00:26:cb:16:e8:d1 (capab=0x431 status=0 aid=16) [ 5508.127262] wlan0: associated [ 5525.110100] iwlagn :0b:00.0: iwl_tx_agg_start on ra = 00:26:cb:16:e8:d1 tid = 0 [ 5546.029401] wlan0: deauthenticating from 00:26:cb:16:e8:d1 by local choice (reason=3) [ 5546.042276] wlan0: direct probe to AP 00:26:cb:16:e8:d1 (try 1) [ 5546.042311] wlan0: deauthenticating from 00:26:cb:16:e8:d1 by local choice (reason=3) [ 5546.045656] wlan0: direct probe to AP 00:26:cb:17:bd:41 (try 1) [ 5546.048069] wlan0: direct probe responded [ 5546.048077] wlan0: authenticate with AP 00:26:cb:17:bd:41 (try 1) [ 5546.049864] wlan0: authenticated [ 5546.077267] wlan0: associate with AP 00:26:cb:17:bd:41 (try 1) [ 5546.080885] wlan0: RX AssocResp from 00:26:cb:17:bd:41 (capab=0x431 status=0 aid=79) [ 5546.080888] wlan0: associated [ 5562.875489] iwlagn :0b:00.0: iwl_tx_agg_start on ra = 00:26:cb:17:bd:41 tid = 0 [ 5571.881150] wlan0: deauthenticating from 00:26:cb:17:bd:41 by local choice (reason=3) [ 5571.928466] wlan0: deauthenticating from 00:26:cb:17:bd:41 by local choice (reason=3) [ 5571.967725] wlan0: direct probe to AP 00:26:cb:17:bd:41 (try 1) [ 5571.969866] wlan0: direct probe responded [ 5571.969870] wlan0: authenticate with AP 00:26:cb:17:bd:41 (try 1) [ 5571.971428] wlan0: authenticated
[Desktop-packages] [Bug 237443] Re: Crash during playback with CPU time limit error
** Changed in: pulseaudio (Fedora) Importance: Unknown => High -- 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/237443 Title: Crash during playback with CPU time limit error Status in PulseAudio: Confirmed Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio package in Fedora: Invalid Bug description: Binary package hint: pulseaudio During playback pulseaudio sometimes crashes with the following error message: philipp@aineko:~$ pulseaudio W: pid.c: Stale PID file, overwriting. ALSA lib control.c:909:(snd_ctl_open_noupdate) Invalid CTL front:0 ALSA lib control.c:909:(snd_ctl_open_noupdate) Invalid CTL front:0 Soft CPU time limit exhausted, terminating. Hard CPU time limit exhausted, terminating forcibly. Aborted The crashes are random and not reproduceable. So far I've only experienced the crashes during playback with Quod Libet. I can't say for sure, but it looks as if the crashes occur only under a certain load. What other info can I provide, to help pinning this down? To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/237443/+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 274995] Re: MASTER storing ALSA mixer element values during shutdown hangs nondeterministically due to internal alsa-plugins pulse check
Launchpad has imported 24 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=203930. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2006-08-24T15:56:52+00:00 Davide wrote: Description of problem: If the snd_hda_intel module is loaded into the kernel (for example after starting X), the computer will not power off when "poweroff" command is called. My computer has an Asus P5GD1 motherboard. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1.Start computer at runlevel 5 2.Log in into X and play some sound just to be sure sound module is loaded 3.System -> Shut down. Actual results: The computer doesn't power off and hangs after a message "ACPI power down called" is displayed. Expected results: The computer shoud poweroff Additional info: I added a 'modprobe -r snd_hda_intel' line in the stop) section of /etc/init.d/kudzu and the computer shuts down correctly therafter. Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/274995/comments/0 On 2006-09-05T15:56:02+00:00 David wrote: Changing to proper owner, kernel-maint. Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/274995/comments/1 On 2006-10-16T21:11:48+00:00 Dave wrote: A new kernel update has been released (Version: 2.6.18-1.2200.fc5) based upon a new upstream kernel release. Please retest against this new kernel, as a large number of patches go into each upstream release, possibly including changes that may address this problem. This bug has been placed in NEEDINFO state. Due to the large volume of inactive bugs in bugzilla, if this bug is still in this state in two weeks time, it will be closed. Should this bug still be relevant after this period, the reporter can reopen the bug at any time. Any other users on the Cc: list of this bug can request that the bug be reopened by adding a comment to the bug. In the last few updates, some users upgrading from FC4->FC5 have reported that installing a kernel update has left their systems unbootable. If you have been affected by this problem please check you only have one version of device-mapper & lvm2 installed. See bug 207474 for further details. If this bug is a problem preventing you from installing the release this version is filed against, please see bug 169613. If this bug has been fixed, but you are now experiencing a different problem, please file a separate bug for the new problem. Thank you. Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/274995/comments/2 On 2006-10-17T12:43:34+00:00 Davide wrote: Even with kernel-smp 2.6.18-1.22000.fc5 the problem persists. I tried booting with the 'acpi=ht' boot option, but the system still doesn't poweroff, the only thing changed is the last message printed: "System halted" instead of "acpi_power_off called". The only way to let the computer shutdown automatically is to call modprobe -r snd_hda_intel somewhere during the shutdown process (I moved it from kudzu to the halt script just after the "saving mixer settings" lines). Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/274995/comments/3 On 2007-10-29T18:52:51+00:00 Stefan wrote: I can confirm the problem still exists in Fedora 7 with the Asus P5GD1 motherboard. I've had this annoying shutdown problem for five months and finally I have found a workaround here, thanks Davide!! Unfortunately I found the bug still exists in Fedora 8 Test 2 as well. Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/274995/comments/4 On 2007-12-31T03:39:42+00:00 Jon wrote: Changing version to F7 since that it the last released version that this problem is reported in. You mention F8T2, does it exist in released F8? Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/274995/comments/5 On 2007-12-31T03:40:19+00:00 Jon wrote: *** Bug 212726 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/274995/comments/6 On 2008-01-08T13:57:35+00:00 Davide wrote: This bug is still present in F8 - kernel 2.6.23.9-85.fc8 Reply at:
[Desktop-packages] [Bug 251038] Re: Right Ctrl and Right Alt don't work
Launchpad has imported 5 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=475678. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2008-12-09T23:57:27+00:00 Daniel wrote: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.4) Gecko/2008111318 Ubuntu/8.10 (intrepid) Firefox/3.0.4 Pressing Ctrl-Alt ungrabs the mouse, but only if you use left Ctrl and left Alt. Using right Ctrl, right Alt will not work nor will left Ctrl, right Alt. Reproducible: Always Reply at: https://bugs.launchpad.net/ubuntu/+source/virt- manager/+bug/251038/comments/5 On 2008-12-10T11:29:57+00:00 Daniel wrote: What version of virt-manager, and gtk-vnc are you using ? Reply at: https://bugs.launchpad.net/ubuntu/+source/virt- manager/+bug/251038/comments/6 On 2008-12-10T18:08:55+00:00 Daniel wrote: virt-manager v. 0.5.4-2ubuntu1 gtk-vnc v. 0.3.7-0ubuntu2 Reply at: https://bugs.launchpad.net/ubuntu/+source/virt- manager/+bug/251038/comments/7 On 2008-12-10T18:16:46+00:00 Daniel wrote: Ok, the 0.3.8 release of GTK-VNC ought to have fixed this problem. You should file a Bug against Ubuntu gtk-vnc packages to get them updated. Reply at: https://bugs.launchpad.net/ubuntu/+source/virt- manager/+bug/251038/comments/8 On 2008-12-10T18:57:25+00:00 Daniel wrote: This bug can probably be closed then. Reply at: https://bugs.launchpad.net/ubuntu/+source/virt- manager/+bug/251038/comments/9 ** Changed in: virt-manager Importance: Unknown => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk-vnc in Ubuntu. https://bugs.launchpad.net/bugs/251038 Title: Right Ctrl and Right Alt don't work Status in virt-manager: Invalid Status in gtk-vnc package in Ubuntu: Fix Released Status in virt-manager package in Ubuntu: Invalid Bug description: Pressing Ctrl-Alt ungrabs the mouse, but only if you use Left Control and Left Alt. Using Right Control or Right Alt will not work. I don't see why there should be a difference. To manage notifications about this bug go to: https://bugs.launchpad.net/virt-manager/+bug/251038/+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 1104476] Re: Network manager cannot connect to WPA2/PEAP/MSCHAPv2 enterprise wifi networks without CA_Certificate, like Eduroam
Launchpad has imported 37 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=1241930. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2015-07-10T12:50:50+00:00 Kevin wrote: Description of problem: After updating to wpa_supplicant 2.4-3 on July 1, was unable to connect to my corporate wifi access point. Subsequent downgrade to wpa_supplicant 2.3-3 fixed access problem, so I think this is a wpa_supplicant bug Version-Release number of selected component (if applicable): wpa_supplicant 2.4-3 How reproducible: Upgrade to 2.4-3 try to access wpa/wpa2 wifi with TTLS authentication that has been working for well over a year now. Fails. Downgrade to 2.3-3 and it works again. Steps to Reproduce: See above 1. Select network in NetworkManager 2. Does not connect 3. Keeps asking for password Actual results: >From /etc/wpa_supplicant.log after upgrade: wlp12s0: SME: Trying to authenticate with e0:1c:41:34:19:e9 (SSID='CICS' freq=5220 MHz) wlp12s0: Trying to associate with e0:1c:41:34:19:e9 (SSID='CICS' freq=5220 MHz) wlp12s0: Associated with e0:1c:41:34:19:e9 wlp12s0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=US wlp12s0: CTRL-EVENT-EAP-STARTED EAP authentication started wlp12s0: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=21 wlp12s0: CTRL-EVENT-EAP-METHOD EAP vendor 0 method 21 (TTLS) selected wlp12s0: CTRL-EVENT-EAP-PEER-CERT depth=2 subject='/C=US/O=The Go Daddy Group, Inc./OU=Go Daddy Class 2 Certification Authori ty' hash=c3846bf24b9e93ca64274c0ec67c1ecc5e024ffcacd2d74019350e81fe546ae4 wlp12s0: CTRL-EVENT-EAP-PEER-CERT depth=2 subject='/C=US/O=The Go Daddy Group, Inc./OU=Go Daddy Class 2 Certification Authori ty' hash=c3846bf24b9e93ca64274c0ec67c1ecc5e024ffcacd2d74019350e81fe546ae4 wlp12s0: CTRL-EVENT-EAP-PEER-CERT depth=1 subject='/C=US/ST=Arizona/L=Scottsdale/O=GoDaddy.com, Inc./OU=http://certificates.g odaddy.com/repository/CN=Go Daddy Secure Certification Authority/serialNumber=07969287' hash=09ed6e991fc3273d8fea317d339c0204 1861973549cfa6e1558f411f11211aa3 wlp12s0: CTRL-EVENT-EAP-PEER-CERT depth=0 subject='/OU=Domain Control Validated/CN=cicsnc.org' hash=598c9bcc63d9e114262181d14 dfed5372381b7ae0eb762e701b689b0e309f9b7 wlp12s0: CTRL-EVENT-EAP-PEER-ALT depth=0 DNS:cicsnc.org wlp12s0: CTRL-EVENT-EAP-PEER-ALT depth=0 DNS:www.cicsnc.org wlp12s0: CTRL-EVENT-EAP-PEER-ALT depth=0 DNS:osx.cicsnc.org wlp12s0: CTRL-EVENT-EAP-PEER-ALT depth=0 DNS:osx2.cicsnc.org SSL: SSL3 alert: write (local SSL3 detected an error):fatal:handshake failure OpenSSL: openssl_handshake - SSL_connect error:14082174:SSL routines:SSL3_CHECK_CERT_AND_ALGORITHM:dh key too small wlp12s0: CTRL-EVENT-EAP-FAILURE EAP authentication failed wlp12s0: Authentication with e0:1c:41:34:19:e9 timed out. wlp12s0: CTRL-EVENT-DISCONNECTED bssid=e0:1c:41:34:19:e9 reason=3 locally_generated=1 wlp12s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="CICS" auth_failures=1 duration=10 reason=AUTH_FAILED wlp12s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="CICS" auth_failures=2 duration=35 reason=CONN_FAILED After downgrade: wlp12s0: Trying to associate with e0:1c:41:34:19:e9 (SSID='CICS' freq=5220 MHz) wlp12s0: Associated with e0:1c:41:34:19:e9 wlp12s0: CTRL-EVENT-EAP-STARTED EAP authentication started wlp12s0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=US wlp12s0: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=21 wlp12s0: CTRL-EVENT-EAP-METHOD EAP vendor 0 method 21 (TTLS) selected wlp12s0: CTRL-EVENT-EAP-PEER-CERT depth=2 subject='/C=US/O=The Go Daddy Group, Inc./OU=Go Daddy Class 2 Certification Authori ty' wlp12s0: CTRL-EVENT-EAP-PEER-CERT depth=2 subject='/C=US/O=The Go Daddy Group, Inc./OU=Go Daddy Class 2 Certification Authori ty' wlp12s0: CTRL-EVENT-EAP-PEER-CERT depth=1 subject='/C=US/ST=Arizona/L=Scottsdale/O=GoDaddy.com, Inc./OU=http://certificates.g odaddy.com/repository/CN=Go Daddy Secure Certification Authority/serialNumber=07969287' wlp12s0: CTRL-EVENT-EAP-PEER-CERT depth=0 subject='/OU=Domain Control Validated/CN=cicsnc.org' EAP-MSCHAPV2: Authentication succeeded wlp12s0: CTRL-EVENT-EAP-SUCCESS EAP authentication completed successfully wlp12s0: WPA: Key negotiation completed with e0:1c:41:34:19:e9 [PTK=CCMP GTK=CCMP] wlp12s0: CTRL-EVENT-CONNECTED - Connection to e0:1c:41:34:19:e9 completed [id=0 id_str=] wlp12s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-62 noise= txrate=6000 wlp12s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-59 noise= txrate=81000 wlp12s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-67 noise= txrate=135000 wlp12s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-59 noise= txrate=6000 wlp12s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-67 noise= txrate=121500 wlp12s0:
[Desktop-packages] [Bug 430203] Re: bell.ogg is unresponsive (outside HIG response times) [regression]
Launchpad has imported 10 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=498608. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2009-05-01T13:20:42+00:00 Davide wrote: Description of problem: If multiple alert-triggering events occur too close in time, the alert sound is only played upon the first event, whereas no alert sound is played for the remaining alert-triggering events. Consider the case of two successive alert-triggering events. If the delay between the two alert events is longer than the duration of the alert sound, two distinct alert sounds are played. If, however, the second alert event is triggered before the sound for the first alert event has finished playing, no alert sound for the second alert event is played. If more than two event-triggering events occur within a time window shorter than the duration of the alert sound, only one alert sound is played. This is bad because all alerts but the first one essentially vanish. In a situation where an alert is triggered every time a given key is pressed, pressing the key twice must lead to two alert sounds, no matter how quickly the two keypresses are done. This way, the user receives feedback on each of the two keypresses. Issuing a single alert sound would leave the user without feedback about the second keypress. In order to combine the two alert sounds, two solutions come to my mind: 1. the first alert sound is interrupted and the second alert sound is played immediately afterwards 2. the second alert sound is superimposed to the first one Note that when the system beep was used for alerts (prior to the introduction of libcanberra (*), I think), solution 1 was in place. The first beep would be interrupted to give way to the second beep. The user would (sloppily speaking) hear "Bee-bep" and hence receive the information that two separate beeps had been issued. (*) Thanks to bug 498594, this situation can currently be observed by turning the desktop effects on. Version-Release number of selected component (if applicable): As in the 2009-04-30 rawhide. In particular: libcanberra-0.12-1.fc11.x86_64 pulseaudio-0.9.15-11.fc11.x86_64 alsa-lib-1.0.19-3.fc11.x86_64 How reproducible: always Steps to Reproduce: 1. Ensure desktop effects are disabled (see bug 498594) and that the sound theme is set to "Default" 2. Open a gnome-terminal window 3. Push the "down" arrow very quickly two times within the gnome-terminal window to trigger two consecutive alert events 4. Keep the "down" arrow pressed to trigger a large number of consecutive alert events Actual results: In step 3, a single alert sound is heard. In step 4, the alert sound is played periodically, with the period equal to the duration of the alert sound. Expected results: In step 3, two alert sounds be heard (either with the first one being interrupted to give way to the second one, as in solution 1, or with the second one superimposing on the first one, as in solution 2). In step 4, multiple alert sounds be heard (again, either according to solution 1 or to solution 2), with the speed at which new alert sounds are started being equal to the keypress repeat speed specified in the keyboard preferences. Reply at: https://bugs.launchpad.net/ubuntu/+source/ubuntu- sounds/+bug/430203/comments/0 On 2009-06-06T08:50:40+00:00 Davide wrote: I found more information to support my request. The GNOME Human Interface Guidelines contain the following: (Source: http://library.gnome.org/devel/hig-book/stable/feedback-response-times.html.en) "Verify that your application provides feedback within 100 milliseconds (0.1 second) after each key press, movement of the mouse, or other physical input from the user." In the scenario described in the bug report, this clearly does not happen. I hope that libcanberra is the correct component to report the bug against. Reply at: https://bugs.launchpad.net/ubuntu/+source/ubuntu- sounds/+bug/430203/comments/1 On 2009-06-09T14:56:44+00:00 Bug wrote: This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle. Changing version to '11'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Reply at: https://bugs.launchpad.net/ubuntu/+source/ubuntu- sounds/+bug/430203/comments/2 On 2009-08-28T03:35:06+00:00 Lennart wrote: This is actually a "feature" in metacity: http://git.gnome.org/cgit/metacity/tree/src/core/display.c#n2387 It limits bell events
[Desktop-packages] [Bug 582347] Re: etags screw filenames starting with ./
Launchpad has imported 9 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=545398. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2009-12-08T13:26:05+00:00 Sjoerd wrote: Created attachment 376898 Patch for the problem described, replacing strcpy with memmove. Description of problem: This is a bug against etags.emacs which is packaged in emacs-common, but there is no separate component called emacs-common. This same bug exists in etags.xemacs, packaged in xemacs-common. When etags is run with filenames starting with "./", it normalizes them to start without "./", but does so incorrectly, messing up the result. Version-Release number of selected component (if applicable): emacs-common-23.1-13.fc12.x86_64 xemacs-common-21.5.29-8.fc12.x86_64 How reproducible: 100% Steps to Reproduce: 1. Create a file with a C function and path e.g. src/gdk/gdk_atoms.c 2. Run /usr/bin/etags.emacs ./src/gdk/gdk_atoms.c 3. Observe the filename in TAGS Actual results: The filename recorded in the TAGS file is src/gdk/gdk_otoms.c (note "o" after underscore). Expected results: The filename should be src/gdk/gdk_atoms.c Additional info: The problem is a call to strcpy on overlapping buffers. In Fedora 11 and before that seems to have worked, but in Fedora 12 it often does not work, at least not for slightly longer filenames. The attached patch should also work for etags.xemacs in xemacs-common, except for differing line numbers. Reply at: https://bugs.launchpad.net/ubuntu/+source/exuberant- ctags/+bug/582347/comments/0 On 2009-12-08T13:31:25+00:00 Sjoerd wrote: Also see bug 545399 for the XEmacs version of the bug. Reply at: https://bugs.launchpad.net/ubuntu/+source/exuberant- ctags/+bug/582347/comments/1 On 2009-12-08T16:52:30+00:00 Karel wrote: I cannot reproduce it on 32-bit Fedora, but the usage of strcpy in the code is clearly wrong. Moreover, this bug is already fixed in the upstream CVS. Reply at: https://bugs.launchpad.net/ubuntu/+source/exuberant- ctags/+bug/582347/comments/2 On 2009-12-08T17:29:57+00:00 Karel wrote: http://koji.fedoraproject.org/koji/taskinfo?taskID=1863033 The fix will be a part of next update. Thanks for nicely detailed bug report. Reply at: https://bugs.launchpad.net/ubuntu/+source/exuberant- ctags/+bug/582347/comments/3 On 2010-03-30T23:18:05+00:00 Fedora wrote: emacs-23.1-11.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/emacs-23.1-11.fc11 Reply at: https://bugs.launchpad.net/ubuntu/+source/exuberant- ctags/+bug/582347/comments/4 On 2010-04-01T01:41:57+00:00 Fedora wrote: emacs-23.1-11.fc11 has been pushed to the Fedora 11 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update emacs'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/emacs-23.1-11.fc11 Reply at: https://bugs.launchpad.net/ubuntu/+source/exuberant- ctags/+bug/582347/comments/5 On 2010-04-01T16:10:06+00:00 Fedora wrote: emacs-23.1-13.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/emacs-23.1-13.fc11 Reply at: https://bugs.launchpad.net/ubuntu/+source/exuberant- ctags/+bug/582347/comments/6 On 2010-04-09T01:45:18+00:00 Fedora wrote: emacs-23.1-13.fc11 has been pushed to the Fedora 11 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update emacs'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/emacs-23.1-13.fc11 Reply at: https://bugs.launchpad.net/ubuntu/+source/exuberant- ctags/+bug/582347/comments/7 On 2010-04-20T13:08:50+00:00 Fedora wrote: emacs-23.1-13.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report. Reply at: https://bugs.launchpad.net/ubuntu/+source/exuberant- ctags/+bug/582347/comments/8 ** Changed in: emacs23
[Desktop-packages] [Bug 412922] Re: Gnome power manager dies when AC unplugged
Launchpad has imported 3 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=459906. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2008-08-24T09:15:49+00:00 Edouard wrote: Created attachment 314879 my dmesg Description of problem: Gnome-power-man applet disappear when removing AC. In dmesg the error is: gnome-power-man[6470] general protection ip:4105c1 sp:7fff3726ec20 error:0 in gnome-power-manager[40+4b000] Version-Release number of selected component (if applicable): gnome-power-manager-2.23.6-1.fc10.x86_64 How reproducible: static Steps to Reproduce: 1. Log in with AC plugged 2. Unplug AC 3. Move the mouse cursor over the g-p-m applet to see how much battery left. After a couple of seconds the applet crashs. Actual results: General protection fault, g-p-m applet is dead. Expected results: Shouldn't crash of course. Should show the time remaining on battery. Additional info: After that some other applets seems to crash: gpk-update-icon[6439] general protection ip:3b21c104a8 sp:7fffd1850e18 error:0 in libpackagekit.so.4.0.0[3b21c0+24000] Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-power- manager/+bug/412922/comments/0 On 2008-09-10T12:42:13+00:00 Richard wrote: I'm guessing the problem is now fixed in rawhide? Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-power- manager/+bug/412922/comments/1 On 2008-09-11T07:47:58+00:00 Edouard wrote: yes it's fixed in rawhide. You can close this bug. Thanks Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-power- manager/+bug/412922/comments/2 ** Changed in: gnome-power-manager (Fedora) Importance: Unknown => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/412922 Title: Gnome power manager dies when AC unplugged Status in gnome-power-manager package in Ubuntu: Invalid Status in gnome-power-manager package in Fedora: Fix Released Bug description: Binary package hint: gnome-power-manager Description: Ubuntu 9.04 Release: 9.04 gnome-power-manager: Installed: 2.24.2-2ubuntu8 Candidate: 2.24.2-2ubuntu8 Version table: *** 2.24.2-2ubuntu8 0 500 http://bg.archive.ubuntu.com jaunty/main Packages 100 /var/lib/dpkg/status I removed the AC. I expected the Gnome Power manager would start counting how much battery life is left. When AC removed gnome power manager exits unexpectedly. /var/log/message shows me this: Aug 13 11:37:25 gattanegra kernel: [ 2173.541598] gnome-power-man[7054]: segfault at b7705fdc ip b5e852d8 sp b676533c error 7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/412922/+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 1219245] Re: soffice.bin crashed with SIGSEGV in ImplDevFontListData::~ImplDevFontListData()
Launchpad has imported 20 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=1057977. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2014-01-26T10:20:39+00:00 Josep wrote: Version-Release number of selected component: libreoffice-core-4.1.4.2-4.fc20 Additional info: reporter: libreport-2.1.11 backtrace_rating: 4 cmdline:/usr/lib64/libreoffice/program/soffice.bin --impress --splash-pipe=5 crash_function: ServerFont::Release executable: /usr/lib64/libreoffice/program/soffice.bin kernel: 3.12.8-300.fc20.x86_64 runlevel: N 5 type: CCpp uid:1000 Truncated backtrace: Thread no. 1 (10 frames) #0 ServerFont::Release at /usr/src/debug/libreoffice-4.1.4.2/vcl/generic/glyphs/glyphcache.cxx:341 #1 GlyphCache::UncacheFont at /usr/src/debug/libreoffice-4.1.4.2/vcl/generic/glyphs/glyphcache.cxx:236 #2 X11SalGraphics::setFont at /usr/src/debug/libreoffice-4.1.4.2/vcl/unx/generic/gdi/salgdi3.cxx:166 #3 X11SalGraphics::SetFont at /usr/src/debug/libreoffice-4.1.4.2/vcl/unx/generic/gdi/salgdi3.cxx:508 #4 ReleaseFonts at /usr/src/debug/libreoffice-4.1.4.2/vcl/inc/salgdi.hxx:224 #5 OutputDevice::ImplUpdateFontData at /usr/src/debug/libreoffice-4.1.4.2/vcl/source/gdi/outdev3.cxx:186 #7 OutputDevice::ImplUpdateAllFontData at /usr/src/debug/libreoffice-4.1.4.2/vcl/source/gdi/outdev3.cxx:262 #8 ImplHandleSalSettings at /usr/src/debug/libreoffice-4.1.4.2/vcl/source/window/winproc.cxx:2216 #9 ImplWindowFrameProc at /usr/src/debug/libreoffice-4.1.4.2/vcl/source/window/winproc.cxx:2597 #10 CallCallback at /usr/src/debug/libreoffice-4.1.4.2/vcl/inc/salframe.hxx:243 Potential duplicate: bug 1045497 Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1219245/comments/7 On 2014-01-26T10:20:44+00:00 Josep wrote: Created attachment 855640 File: backtrace Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1219245/comments/8 On 2014-01-26T10:20:46+00:00 Josep wrote: Created attachment 855641 File: cgroup Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1219245/comments/9 On 2014-01-26T10:20:48+00:00 Josep wrote: Created attachment 855642 File: core_backtrace Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1219245/comments/10 On 2014-01-26T10:20:50+00:00 Josep wrote: Created attachment 855643 File: dso_list Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1219245/comments/11 On 2014-01-26T10:20:52+00:00 Josep wrote: Created attachment 855644 File: environ Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1219245/comments/12 On 2014-01-26T10:20:54+00:00 Josep wrote: Created attachment 855645 File: exploitable Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1219245/comments/13 On 2014-01-26T10:20:56+00:00 Josep wrote: Created attachment 855646 File: limits Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1219245/comments/14 On 2014-01-26T10:20:57+00:00 Josep wrote: Created attachment 855647 File: maps Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1219245/comments/15 On 2014-01-26T10:20:59+00:00 Josep wrote: Created attachment 855648 File: open_fds Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1219245/comments/16 On 2014-01-26T10:21:01+00:00 Josep wrote: Created attachment 855649 File: proc_pid_status Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1219245/comments/17 On 2014-01-26T10:21:03+00:00 Josep wrote: Created attachment 855650 File: var_log_messages Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1219245/comments/18 On 2014-01-27T13:18:00+00:00 David wrote: It is not reproducible, I presume? Reply at:
[Desktop-packages] [Bug 1569613] Re: /usr/bin/nm-applet:11:g_hash_table_remove_all_nodes:g_hash_table_remove_all_nodes:g_hash_table_remove_all:nma_icons_reload:g_closure_invoke
The reports go up to the 1.2 version so it looks fixed with the newest series, closing the bug ** Changed in: network-manager-applet (Ubuntu) Importance: Undecided => Low ** Changed in: network-manager-applet (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1569613 Title: /usr/bin/nm- applet:11:g_hash_table_remove_all_nodes:g_hash_table_remove_all_nodes:g_hash_table_remove_all:nma_icons_reload:g_closure_invoke Status in Network Manager Applet: Won't Fix Status in network-manager-applet package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding network-manager-applet. This problem was most recently seen with version 1.1.93-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/833c21733fe3b1fd581cd129585c5b5ec7f8b4f2 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager-applet/+bug/1569613/+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 1727308] Re: when you try to change the layout for a long time reacts
thanks ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Triaged -- 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/1727308 Title: when you try to change the layout for a long time reacts Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Triaged Bug description: when you try to change the layout for a long time reacts and uses caps lock to change the size of letters simultaneously with the change of layout. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 25 17:06:55 2017 DisplayManager: lightdm GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2015-08-27 (789 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-10-25 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1727308/+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 1725315] Re: evolution crashed with SIGSEGV in g_hash_table_lookup_node()
This only happens on gnome-shell on wayland mode. It is evolution indicator plugin. Unfortunately, even clicking on the checkbox to disable it (on the list of evolution plugins) crashes evolution. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1725315 Title: evolution crashed with SIGSEGV in g_hash_table_lookup_node() Status in evolution package in Ubuntu: Confirmed Bug description: Every few minutes, evolution exits the desktop. Sometimes it will only stay up for seconds, and sometimes it exits in the first second. Occasionally it stays up for ~20 minutes. When it is running, it seems to function normally. This machine was upgraded from 17.04 (where Evolution was stable) to 17.10 release. Apport crashdump analysis attached. Looking at /var/log/syslog after one of these crashes, I see the following entries: Oct 20 09:50:00 es-lzz-det470s org.gnome.Shell.desktop[2287]: /usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error: invalid string constant "murrine-scrollbar", expected valid string constant Oct 20 09:50:00 es-lzz-det470s org.gnome.Shell.desktop[2287]: [Parent 8840] WARNING: pipe error (254): Connection reset by peer: file /build/firefox-9cfKiA/firefox-56.0+build6/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 353 Oct 20 09:50:52 es-lzz-det470s org.gnome.Shell.desktop[2287]: [Parent 8840] WARNING: pipe error (287): Connection reset by peer: file /build/firefox-9cfKiA/firefox-56.0+build6/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 353 Oct 20 09:50:52 es-lzz-det470s org.gnome.Shell.desktop[2287]: [Parent 8840] WARNING: pipe error (300): Connection reset by peer: file /build/firefox-9cfKiA/firefox-56.0+build6/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 353 Oct 20 09:50:52 es-lzz-det470s org.gnome.Shell.desktop[2287]: [Parent 8840] WARNING: pipe error (417): Connection reset by peer: file /build/firefox-9cfKiA/firefox-56.0+build6/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 353 Oct 20 09:50:57 es-lzz-det470s kernel: [88013.689438] evolution[1461]: segfault at 0 ip (null) sp 7ffee4f96718 error 14 in evolution[557e54c52000+7000] It is not clear that the first few syslog entries are related. Running evolution with debugging enabled: CAMEL_DEBUG=all evolution I see the following output when the crash occurs: ### message_list_regen_thread: got 1521 uids in folder 0x5615e38015f0 (john.mel...@esentire.com : Inbox) for expression:---(and (match-all (and (not (system-flag "deleted")) (not (system-flag "junk" (and (and (match-all (not (or (= (user-tag "label") "important") (user-flag "$Labelimportant") (user-flag "important" (match-all (not (or (= (user-tag "label") "work") (user-flag "$Labelwork") (user-flag "work" (match-all (not (or (= (user-tag "label") "personal") (user-flag "$Labelpersonal") (user-flag "personal" (match-all (not (or (= (user-tag "label") "todo") (user-flag "$Labeltodo") (user-flag "todo" (match-all (not (or (= (user-tag "label") "later") (user-flag "$Labellater") (user-flag "later")))--- message_list_regen_thread: got 1521 uids in folder 0x5615e38015f0 (john.mel...@esentire.com : Inbox) after tweak, hide_deleted:1, hide_junk:1 Segmentation fault (core dumped) Not sure if I can provide further information. This crash is highly- repeatable, happening hundreds of times/day. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: evolution 3.26.1-1 ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4 Uname: Linux 4.13.0-16-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 20 09:50:57 2017 Disassembly: => 0x0: Cannot access memory at address 0x0 ExecutablePath: /usr/bin/evolution InstallationDate: Installed on 2017-05-31 (142 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcCmdline: evolution -c current ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x0: Cannot access memory at address 0x0 PC (0x) not located in a known VMA region (needed executable region)! SegvReason: executing NULL VMA Signal: 11 SourcePackage: evolution StacktraceTop: ?? () g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 gdk_x11_atom_to_xatom_for_display () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 ?? () from /usr/lib/evolution/plugins/liborg-freedesktop-evolution-indicator.so org_gnome_mail_new_notify () from /usr/lib/evolution/plugins/liborg-freedesktop-evolution-indicator.so Title: evolution crashed with SIGSEGV in g_hash_table_lookup() UpgradeStatus: Upgraded to artful on
[Desktop-packages] [Bug 1725315] Re: evolution crashed with SIGSEGV in g_hash_table_lookup_node()
Workaround: uninstall evolution-indicator package. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1725315 Title: evolution crashed with SIGSEGV in g_hash_table_lookup_node() Status in evolution package in Ubuntu: Confirmed Bug description: Every few minutes, evolution exits the desktop. Sometimes it will only stay up for seconds, and sometimes it exits in the first second. Occasionally it stays up for ~20 minutes. When it is running, it seems to function normally. This machine was upgraded from 17.04 (where Evolution was stable) to 17.10 release. Apport crashdump analysis attached. Looking at /var/log/syslog after one of these crashes, I see the following entries: Oct 20 09:50:00 es-lzz-det470s org.gnome.Shell.desktop[2287]: /usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error: invalid string constant "murrine-scrollbar", expected valid string constant Oct 20 09:50:00 es-lzz-det470s org.gnome.Shell.desktop[2287]: [Parent 8840] WARNING: pipe error (254): Connection reset by peer: file /build/firefox-9cfKiA/firefox-56.0+build6/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 353 Oct 20 09:50:52 es-lzz-det470s org.gnome.Shell.desktop[2287]: [Parent 8840] WARNING: pipe error (287): Connection reset by peer: file /build/firefox-9cfKiA/firefox-56.0+build6/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 353 Oct 20 09:50:52 es-lzz-det470s org.gnome.Shell.desktop[2287]: [Parent 8840] WARNING: pipe error (300): Connection reset by peer: file /build/firefox-9cfKiA/firefox-56.0+build6/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 353 Oct 20 09:50:52 es-lzz-det470s org.gnome.Shell.desktop[2287]: [Parent 8840] WARNING: pipe error (417): Connection reset by peer: file /build/firefox-9cfKiA/firefox-56.0+build6/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 353 Oct 20 09:50:57 es-lzz-det470s kernel: [88013.689438] evolution[1461]: segfault at 0 ip (null) sp 7ffee4f96718 error 14 in evolution[557e54c52000+7000] It is not clear that the first few syslog entries are related. Running evolution with debugging enabled: CAMEL_DEBUG=all evolution I see the following output when the crash occurs: ### message_list_regen_thread: got 1521 uids in folder 0x5615e38015f0 (john.mel...@esentire.com : Inbox) for expression:---(and (match-all (and (not (system-flag "deleted")) (not (system-flag "junk" (and (and (match-all (not (or (= (user-tag "label") "important") (user-flag "$Labelimportant") (user-flag "important" (match-all (not (or (= (user-tag "label") "work") (user-flag "$Labelwork") (user-flag "work" (match-all (not (or (= (user-tag "label") "personal") (user-flag "$Labelpersonal") (user-flag "personal" (match-all (not (or (= (user-tag "label") "todo") (user-flag "$Labeltodo") (user-flag "todo" (match-all (not (or (= (user-tag "label") "later") (user-flag "$Labellater") (user-flag "later")))--- message_list_regen_thread: got 1521 uids in folder 0x5615e38015f0 (john.mel...@esentire.com : Inbox) after tweak, hide_deleted:1, hide_junk:1 Segmentation fault (core dumped) Not sure if I can provide further information. This crash is highly- repeatable, happening hundreds of times/day. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: evolution 3.26.1-1 ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4 Uname: Linux 4.13.0-16-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 20 09:50:57 2017 Disassembly: => 0x0: Cannot access memory at address 0x0 ExecutablePath: /usr/bin/evolution InstallationDate: Installed on 2017-05-31 (142 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcCmdline: evolution -c current ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x0: Cannot access memory at address 0x0 PC (0x) not located in a known VMA region (needed executable region)! SegvReason: executing NULL VMA Signal: 11 SourcePackage: evolution StacktraceTop: ?? () g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 gdk_x11_atom_to_xatom_for_display () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 ?? () from /usr/lib/evolution/plugins/liborg-freedesktop-evolution-indicator.so org_gnome_mail_new_notify () from /usr/lib/evolution/plugins/liborg-freedesktop-evolution-indicator.so Title: evolution crashed with SIGSEGV in g_hash_table_lookup() UpgradeStatus: Upgraded to artful on 2017-10-19 (1 days ago) UserGroups: adm cdrom docker libvirt lpadmin plugdev sambashare sudo To manage notifications about this bug go to:
[Desktop-packages] [Bug 1727911] Re: fcitx not dispaly
note that GNOME has no fcitx integration but only ibus -- 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/1727911 Title: fcitx not dispaly Status in gnome-shell package in Ubuntu: Incomplete Bug description: Choice Fcitx No Fcitx`sign on the top right corner ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Oct 27 11:07:49 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:21ce] InstallationDate: Installed on 2017-10-24 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 4180AP3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=3b93ab4f-c57d-4ccf-94fd-7c43d7fb3c36 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 83ET73WW (1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 4180AP3 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr83ET73WW(1.43):bd11/30/2012:svnLENOVO:pn4180AP3:pvrThinkPadT420:rvnLENOVO:rn4180AP3:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T420 dmi.product.name: 4180AP3 dmi.product.version: ThinkPad T420 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727911/+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 1727911] Re: fcitx not dispaly
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/1727911 Title: fcitx not dispaly Status in gnome-shell package in Ubuntu: Incomplete Bug description: Choice Fcitx No Fcitx`sign on the top right corner ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Oct 27 11:07:49 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:21ce] InstallationDate: Installed on 2017-10-24 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 4180AP3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=3b93ab4f-c57d-4ccf-94fd-7c43d7fb3c36 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 83ET73WW (1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 4180AP3 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr83ET73WW(1.43):bd11/30/2012:svnLENOVO:pn4180AP3:pvrThinkPadT420:rvnLENOVO:rn4180AP3:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T420 dmi.product.name: 4180AP3 dmi.product.version: ThinkPad T420 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727911/+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 1609700] Re: username is not saved in openconnect connection dialog
Thanks, closing the bug then ** Changed in: network-manager (Ubuntu) Importance: Undecided => Low ** Changed in: network-manager (Ubuntu) Status: Confirmed => Fix Released ** Changed in: network-manager-openconnect (Ubuntu) Status: Confirmed => Fix Released ** Changed in: network-manager-openconnect (Ubuntu) Importance: Undecided => Low -- 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/1609700 Title: username is not saved in openconnect connection dialog Status in network-manager package in Ubuntu: Fix Released Status in network-manager-openconnect package in Ubuntu: Fix Released Status in Fedora: Fix Released Bug description: Hi, I clicked on "save passwords" but only the password is filled in automatically when I open the connection dialog. The "Username" field is empty! This happens for a SSLVPN configuration. For another VPN config (don't know which type) everything is ok. openconnect: 7.06-2build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1609700/+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 1725836] Re: No more than 2 displays work simultaneously
** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1725836 Title: No more than 2 displays work simultaneously Status in Mutter: Confirmed Status in gnome-shell package in Ubuntu: Triaged Status in mutter package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: I have three displays that worked fine in 17.04. Now ith 17.10 I can only use two of them. Either 1 & 2, 1& 3 or 2 2 & 3. All three seem to be properly specified in monitors.xml. The display setup scree detects all three. UBUNTU 17.10 AMD PitcairnLSB Version: core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch --- ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-02-23 (242 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Package: mutter PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Tags: artful Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-20 (3 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1725836/+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 1723840] Re: Firefox 56.0 High CPU
** Also affects: firefox (Arch Linux) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1723840 Title: Firefox 56.0 High CPU Status in firefox package in Ubuntu: Confirmed Status in firefox package in Arch Linux: New Bug description: Since the Firefox 56 upgrade, CPU utilization has been high during idle and light usage. Just typing this bugreport, here's a sample top: top - 23:02:20 up 2 days, 41 min, 5 users, load average: 0.78, 0.80, 0.77 Tasks: 243 total, 2 running, 240 sleeping, 0 stopped, 1 zombie %Cpu(s): 9.0 us, 0.5 sy, 0.0 ni, 90.0 id, 0.5 wa, 0.0 hi, 0.0 si, 0.0 st KiB Mem : 7130052 total, 2096428 free, 2678412 used, 2355212 buff/cache KiB Swap: 524280 total, 524280 free,0 used. 4027112 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1895 js1 20 0 4701160 2.032g 175340 R 100.0 29.9 1086:22 firefox Please let me know if I need to provide any additional debug or info. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: firefox 56.0+build6-0ubuntu0.16.04.2 ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87 Uname: Linux 4.4.0-97-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: js11957 F pulseaudio /dev/snd/controlC1: js11957 F pulseaudio BuildID: 20171003101344 Channel: Unavailable CurrentDesktop: XFCE Date: Sun Oct 15 22:57:05 2017 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2016-05-01 (532 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via 10.23.21.1 dev wlp7s4 proto static metric 600 10.23.21.0/26 dev wlp7s4 proto kernel scope link src 10.23.21.18 metric 600 169.254.0.0/16 dev wlp7s4 scope link metric 1000 Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-5bca9619-b74f-4910-9909-6bd1b0170925 Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=56.0/20171003101344 (In use) RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/28/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 0D881F dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA16:bd05/28/2013:svnDellInc.:pnPrecisionWorkStationT7500:pvr:rvnDellInc.:rn0D881F:rvrA05:cvnDellInc.:ct7:cvr: dmi.product.name: Precision WorkStation T7500 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1723840/+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 1720262] Re: gnome-screenshot Actions don't work in default Ubuntu 17.10 session
There is no easy way to have those actions filtered out for GNOME/wayland only... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. https://bugs.launchpad.net/bugs/1720262 Title: gnome-screenshot Actions don't work in default Ubuntu 17.10 session Status in GNOME Shell: Confirmed Status in gnome-screenshot package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Triaged Status in gnome-screenshot source package in Artful: Fix Released Bug description: Ubuntu 17.10 Beta Ubuntu session (Wayland) Open the Activities Overview. Right-click on Screenshot. 2 of the 3 extra desktop actions don't work. Works = Take a Screenshot of the Whole Screen Doesn't Work Take a Screenshot of the Current Window Take a Screenshot of a Selected Area Other Info == All 3 functions work if you open Screenshot and click the buttons in the app. The Current Window action is upstream, but Selected Area is an Ubuntu patch. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1720262/+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 1723840] Re: Firefox 56.0 High CPU
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: firefox (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1723840 Title: Firefox 56.0 High CPU Status in firefox package in Ubuntu: Confirmed Bug description: Since the Firefox 56 upgrade, CPU utilization has been high during idle and light usage. Just typing this bugreport, here's a sample top: top - 23:02:20 up 2 days, 41 min, 5 users, load average: 0.78, 0.80, 0.77 Tasks: 243 total, 2 running, 240 sleeping, 0 stopped, 1 zombie %Cpu(s): 9.0 us, 0.5 sy, 0.0 ni, 90.0 id, 0.5 wa, 0.0 hi, 0.0 si, 0.0 st KiB Mem : 7130052 total, 2096428 free, 2678412 used, 2355212 buff/cache KiB Swap: 524280 total, 524280 free,0 used. 4027112 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1895 js1 20 0 4701160 2.032g 175340 R 100.0 29.9 1086:22 firefox Please let me know if I need to provide any additional debug or info. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: firefox 56.0+build6-0ubuntu0.16.04.2 ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87 Uname: Linux 4.4.0-97-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: js11957 F pulseaudio /dev/snd/controlC1: js11957 F pulseaudio BuildID: 20171003101344 Channel: Unavailable CurrentDesktop: XFCE Date: Sun Oct 15 22:57:05 2017 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2016-05-01 (532 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via 10.23.21.1 dev wlp7s4 proto static metric 600 10.23.21.0/26 dev wlp7s4 proto kernel scope link src 10.23.21.18 metric 600 169.254.0.0/16 dev wlp7s4 scope link metric 1000 Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-5bca9619-b74f-4910-9909-6bd1b0170925 Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=56.0/20171003101344 (In use) RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/28/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 0D881F dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA16:bd05/28/2013:svnDellInc.:pnPrecisionWorkStationT7500:pvr:rvnDellInc.:rn0D881F:rvrA05:cvnDellInc.:ct7:cvr: dmi.product.name: Precision WorkStation T7500 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1723840/+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 1727955] Re: nautilus crashed with SIGABRT in g_assertion_message()
*** This bug is a duplicate of bug 1725745 *** https://bugs.launchpad.net/bugs/1725745 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1725745, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1727955/+attachment/4997576/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1727955/+attachment/4997578/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1727955/+attachment/4997582/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1727955/+attachment/4997583/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1727955/+attachment/4997584/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1727955/+attachment/4997585/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1727955/+attachment/4997586/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1725745 nautilus crashed with SIGABRT in g_assertion_message() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1727955 Title: nautilus crashed with SIGABRT in g_assertion_message() Status in nautilus package in Ubuntu: New Bug description: Crash on startup ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 26 19:42:50 2017 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2017-10-21 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=en_AU:en PATH=(custom, no user) LANG=en_AU.UTF-8 Signal: 6 SourcePackage: nautilus StacktraceTop: g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: nautilus crashed with SIGABRT in g_assertion_message() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1727955/+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 1725836] Re: No more than 2 displays work simultaneously
Thanks for the info. The answer is yes On Fri, Oct 27, 2017 at 3:04 AM, Daniel van Vugt < daniel.van.v...@canonical.com> wrote: > This could be related to OpenGL texture sizes or something similar. > Unity7 (Compiz) has workarounds to avoid that limitation. And Xfce > avoids it by not using hardware accelerated compositing at all (last I > checked). It's not surprising if only Gnome Shell hits a problem like > this... > > Do you get the same bug logging in to "Ubuntu" vs "Ubuntu on Xorg"? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1725836 > > Title: > No more than 2 displays work simultaneously > > Status in Mutter: > Confirmed > Status in gnome-shell package in Ubuntu: > Incomplete > Status in mutter package in Ubuntu: > Incomplete > Status in xorg-server package in Ubuntu: > Incomplete > > Bug description: > I have three displays that worked fine in 17.04. > Now ith 17.10 I can only use two of them. Either 1 & 2, 1& 3 or 2 2 & 3. > All three seem to be properly specified in monitors.xml. > The display setup scree detects all three. > UBUNTU 17.10 > AMD PitcairnLSB Version: core-9.20160110ubuntu5-amd64: > core-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9. > 20160110ubuntu5-noarch > --- > ApportVersion: 2.20.7-0ubuntu3 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > DisplayManager: gdm3 > DistroRelease: Ubuntu 17.10 > InstallationDate: Installed on 2017-02-23 (242 days ago) > InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 > (20161012.2) > Package: mutter > PackageArchitecture: amd64 > ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 > Tags: artful > Uname: Linux 4.13.0-16-generic x86_64 > UpgradeStatus: Upgraded to artful on 2017-10-20 (3 days ago) > UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo > _MarkForUpload: True > > To manage notifications about this bug go to: > https://bugs.launchpad.net/mutter/+bug/1725836/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1725836 Title: No more than 2 displays work simultaneously Status in Mutter: Confirmed Status in gnome-shell package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: I have three displays that worked fine in 17.04. Now ith 17.10 I can only use two of them. Either 1 & 2, 1& 3 or 2 2 & 3. All three seem to be properly specified in monitors.xml. The display setup scree detects all three. UBUNTU 17.10 AMD PitcairnLSB Version: core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch --- ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-02-23 (242 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Package: mutter PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Tags: artful Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-20 (3 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1725836/+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 1722454] Re: Duplicity fails with MemoryError
*** This bug is a duplicate of bug 1720159 ***
https://bugs.launchpad.net/bugs/1720159
Hmm... Why do you think this is a duplicate of #1720159? My stack trace
looks different.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1722454
Title:
Duplicity fails with MemoryError
Status in Duplicity:
New
Status in duplicity package in Ubuntu:
New
Bug description:
Running the following command:
/usr/bin/python /usr/bin/duplicity collection-status
--exclude=/mnt/jabba/juergh/backup/gollum
--include=/home/juergh/.cache/deja-dup/metadata --exclude=/home/juergh
/.uk-pkg --exclude=/home/juergh/Music --exclude=/home/juergh/debug
--exclude=/home/juergh/canonical/cve-matrix/cve-matrix/cve-tracker
--exclude=/home/juergh/canonical/cve-matrix/cve-autotriage
--exclude=/home/juergh/Desktop --exclude=/home/juergh/.cache
--exclude=/home/juergh/tmp --exclude=/home/juergh/git
--exclude=/home/juergh/Downloads
--exclude=/home/juergh/.local/share/Trash
--exclude=/home/juergh/.cache/deja-dup/tmp
--exclude=/home/juergh/.thumbnails --exclude=/home/juergh/.cache/deja-
dup --exclude=/home/juergh/.cache --include=/home/juergh
--exclude=/sys --exclude=/run --exclude=/proc --exclude=/var/tmp
--exclude=/tmp --exclude=** --gio
file:///mnt/jabba/juergh/backup/gollum --no-encryption --verbosity=9
--gpg-options=--no-use-agent --archive-dir=/home/juergh/.cache/deja-
dup --tempdir=/home/juergh/.cache/deja-dup/tmp --log-fd=19
results in:
Traceback (most recent call last):
File "/usr/bin/duplicity", line 1546, in
with_tempdir(main)
File "/usr/bin/duplicity", line 1540, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1391, in main
do_backup(action)
File "/usr/bin/duplicity", line 1416, in do_backup
globals.archive_dir).set_values()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 710,
in set_values
self.get_backup_chains(partials + backend_filename_list)
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 836,
in get_backup_chains
add_to_sets(f)
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 824,
in add_to_sets
if set.add_filename(filename):
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 101,
in add_filename
self.set_manifest(filename)
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 148,
in set_manifest
self.set_files_changed()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 128,
in set_files_changed
mf = self.get_manifest()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 250,
in get_manifest
return self.get_local_manifest()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 224,
in get_local_manifest
return manifest.Manifest().from_string(manifest_buffer)
File "/usr/lib/python2.7/dist-packages/duplicity/manifest.py", line 215, in
from_string
vi = VolumeInfo().from_string(match.group(1))
File "/usr/lib/python2.7/dist-packages/duplicity/manifest.py", line 383, in
from_string
linelist = s.strip().split("\n")
MemoryError
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: duplicity 0.7.12-1ubuntu1
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: GNOME
Date: Tue Oct 10 08:05:45 2017
InstallationDate: Installed on 2017-05-25 (137 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: duplicity
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1722454/+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 530605] Re: gvfs-mount doesn't always work. gvfsd-smb starts using 100% cpu.
Launchpad has imported 33 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=573202. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2010-03-13T11:55:38+00:00 Flóki wrote: Description of problem: Not possible to see samba share in Nautilus. Write smb: into location. Then "Windows Network" appears in header. Wait over 10 seconds and then error window comes. Version-Release number of selected component (if applicable): samba-3.5.1-58.fc13.x86_64 system-config-samba-1.2.86-1.fc13.noarch samba-winbind-clients-3.5.1-58.fc13.x86_64 samba-common-3.5.1-58.fc13.x86_64 selinux-policy-3.7.11-1.fc13.noarch libselinux-2.0.90-5.fc13.x86_64 libselinux-utils-2.0.90-5.fc13.x86_64 selinux-policy-targeted-3.7.11-1.fc13.noarch libselinux-python-2.0.90-5.fc13.x86_64 How reproducible: Always Steps to Reproduce: 1. Open Nautilus and Ctrl+l 2. Write smb: into Lotstion 3. Wait over 10 seconds and error window The folder contents could not be displayed. Actual results: Error window The folder contents could not be displayed. Sorry, could not display all the contents of "Windows Network": DBus error org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Expected results: To see enabeld samba shares There is local sama share Additional info: Just rebooted to reapply selinux policy There is no message in /var/log/messages It is possible to see local samba share form another computer ( F12 ) Reply at: https://bugs.launchpad.net/ubuntu/+source/libgnome- keyring/+bug/530605/comments/6 On 2010-03-13T12:31:17+00:00 Flóki wrote: Created attachment 399847 messages after settin selinux in permissive mode When setting selinux in permissive mode then it possible to see local samba share but not open it. Reply at: https://bugs.launchpad.net/ubuntu/+source/libgnome- keyring/+bug/530605/comments/7 On 2010-03-13T17:00:33+00:00 Simo wrote: Can you check your firewall settings are not blocking samba client packetes ? Reply at: https://bugs.launchpad.net/ubuntu/+source/libgnome- keyring/+bug/530605/comments/8 On 2010-03-13T18:26:25+00:00 Flóki wrote: >Can you check your firewall settings are not blocking samba client packetes ? samba and samba client are marked as trusted. Fierwall disabled The folder contents could not be displayed. Sorry, could not display all the contents of "Windows Network": DBus error org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. no message i /var/log/messages If seleinux in permissive Mar 13 18:15:25 flokic dbus: avc: received setenforce notice (enforcing=0) Mar 13 18:15:25 flokic dbus: avc: received setenforce notice (enforcing=0) Mar 13 18:15:25 flokic dbus: Can't send to audit system: USER_AVC avc: received setenforce notice (enforcing=0)#012: exe="?" sauid=81 hostname=? addr=? terminal=? and error window Unable to mount location Sorry, could not display all the contents of "Windows Network": DBus error org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Reply at: https://bugs.launchpad.net/ubuntu/+source/libgnome- keyring/+bug/530605/comments/9 On 2010-03-13T22:40:42+00:00 Simo wrote: Sorry but this looks like a nautilus or gnome-vfs problem to me. Reassigning. Reply at: https://bugs.launchpad.net/ubuntu/+source/libgnome- keyring/+bug/530605/comments/10 On 2010-03-15T20:25:52+00:00 Flóki wrote: I see in top that gvfsd-smb-brows is with cpu over 90% Reply at: https://bugs.launchpad.net/ubuntu/+source/libgnome- keyring/+bug/530605/comments/12 On 2010-03-16T16:40:03+00:00 Tomáš wrote: Can you please post you gvfs, gnome-keyring and libgnome-keyring package versions? Also, would it be possible to grab a backtrace and post it here? I'm not seeing this
[Desktop-packages] [Bug 620751] Re: dvipdf, evince: Illegal entry in bfrange block in ToUnicode CMap
** Changed in: poppler (Fedora)
Status: Unknown => Fix Released
** Changed in: poppler
Status: Unknown => Fix Released
** Changed in: poppler (Fedora)
Importance: Unknown => Medium
** Changed in: poppler
Importance: Unknown => Medium
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/620751
Title:
dvipdf, evince: Illegal entry in bfrange block in ToUnicode CMap
Status in Poppler:
Fix Released
Status in evince package in Ubuntu:
Invalid
Status in poppler package in Ubuntu:
Fix Released
Status in evince source package in Lucid:
Won't Fix
Status in poppler source package in Lucid:
Won't Fix
Status in poppler package in Fedora:
Fix Released
Bug description:
Binary package hint: evince
1.) I create a simple LaTeX document (named e.g. sample.tex)
containing a vector symbol or the \nabla character:
\documentclass[12pt,a4paper,oneside]{report}
\begin{document}
\[
\vec{F}
\]
\end{document}
(Please note that usual characters will not produce the buggy
behaviour.)
2.) compile it: latex sample.tex
3.) convert dvi file to pdf file:dvipdf sample.dvi
4.) view it running viewer from terminal: evince sample.pdf
Several lines of the error messages appear in the terminal window:
Error: Illegal entry in bfrange block in ToUnicode CMap
I am using the complete texlive installation (metapackage texlive-
full).
Note that I am not the first user who complains about this bug. There is an
older report which however might not been fully noticed by launchpad team
because it was filed just as a comment to another bug: see bug 234413 and
comment #6 in particular:
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/234413/comments/6
There is also an essentially same bug report for other linux system
(Fedora) which may be very useful:
https://bugzilla.redhat.com/show_bug.cgi?id=574964
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: evince 2.30.3-0ubuntu1.1
ProcVersionSignature: Ubuntu 2.6.32-24.39-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-24-generic i686
Architecture: i386
Date: Fri Aug 20 00:09:32 2010
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
ProcEnviron:
LANGUAGE=en_GB:en
PATH=(custom, user)
LANG=en_GB.utf8
SHELL=/bin/bash
SourcePackage: evince
To manage notifications about this bug go to:
https://bugs.launchpad.net/poppler/+bug/620751/+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 185031] Re: [libvorbis] [CVE-2007-4066] multiple buffer overflows in libvorbis before 1.2.0
Launchpad has imported 3 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=249780. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2007-07-26T23:23:55+00:00 Josh wrote: Multiple flaws have been found in libvorbis. These are fixed via libvorbis version 1.2.0. It should be noted that libvorbis 1.2.0 also fixes the issue described in bug 245991. The id number of each flaw is the subversion commit id. The descriptions were provided by Chris Montgomery. The libvorbis subversion repository is located here: http://svn.xiph.org/trunk/vorbis 13217: possible seek infinite loop in libvorbisfile 13215: multiplexed/non Vorbis stream support [heap read, potential heap write] 13211: better return value checking of seeks [heap read, potential heap write] 13179: check legal maximum blocksize [static array read] 13169,13170,13172: correctly handle codebooks with zero entires [heap read/write] 13168: low bitrate static mode declaration error [static read, heap read, potential heap write] 13151,13153,13154,13155,13167: residue decode vector overflow [heap read/write] 13162: static initializer declarations, check-before-free error fixes [heap read/write] 13149: check legal minimum blocksize [static array read] Reply at: https://bugs.launchpad.net/ubuntu/+source/libvorbis/+bug/185031/comments/0 On 2007-08-20T20:09:54+00:00 Josh wrote: Here is the breakdown of CVE id to libvorbis commit id mapping: CVE-2007-4065: 13217 (infinite loop) CVE-2007-4029 covers 2 issues with unknown commit IDs. According to Monty these two issues are the commit ids: 13151, 13154, 13155, 13167 and 13149, 13153, 13179 CVE-2007-4066: multiple flaws 13215: multiplexed/non Vorbis stream support [heap read, potential heap write] 13211: better return value checking of seeks [heap read, potential heap write] 13169,13170,13172: correctly handle codebooks with zero entires [heap read/write] 13168: low bitrate static mode declaration error [static read, heap read, potential heap write] 13162: static initializer declarations, check-before-free error fixes [heap read/write] Reply at: https://bugs.launchpad.net/ubuntu/+source/libvorbis/+bug/185031/comments/1 On 2008-01-17T15:47:49+00:00 Red wrote: This issue was addressed in: Red Hat Enterprise Linux: http://rhn.redhat.com/errata/RHSA-2007-0845.html http://rhn.redhat.com/errata/RHSA-2007-0912.html Fedora: https://admin.fedoraproject.org/updates/F7/FEDORA-2007-1765 Reply at: https://bugs.launchpad.net/ubuntu/+source/libvorbis/+bug/185031/comments/2 ** Changed in: libvorbis (Fedora) Importance: Unknown => High ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2007-4029 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2007-4065 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libvorbis in Ubuntu. https://bugs.launchpad.net/bugs/185031 Title: [libvorbis] [CVE-2007-4066] multiple buffer overflows in libvorbis before 1.2.0 Status in libvorbis package in Ubuntu: Fix Released Status in libvorbis source package in Dapper: Won't Fix Status in libvorbis package in Fedora: Fix Released Bug description: References: DSA-1471-1 (http://www.debian.org/security/2008/dsa-1471) Quoting CVE-2007-4066: "Multiple buffer overflows in Xiph.Org libvorbis before 1.2.0 allow context-dependent attackers to cause a denial of service or have other unspecified impact via a crafted OGG file, aka trac Changesets 13162, 13168, 13169, 13170, 13172, 13211, and 13215, as demonstrated by an overflow in oggenc.exe related to the _psy_noiseguards_8 array." DSA-1471-1 also mentions CVE-2007-3106 and CVE-2007-4029, which have been fixed in USN-498-1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvorbis/+bug/185031/+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 150721] Re: .xsession-errors: 'Failed to read saved session file'
** Changed in: metacity (Fedora) Importance: Unknown => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/150721 Title: .xsession-errors: 'Failed to read saved session file' Status in Metacity: Invalid Status in metacity package in Ubuntu: Invalid Status in metacity package in Debian: Invalid Status in metacity package in Fedora: Invalid Status in metacity package in Gentoo Linux: Fix Released Bug description: Hi, Using Gutsy beta the .xsession-errors file consistently reports the following error: Refusing to initialize GTK+. /etc/gdm/Xsession: Beginning session setup... /etc/X11/Xsession.d/40guidance-displayconfig_restore: 11: /usr/bin/displayconfig-restore: not found SESSION_MANAGER=local/ilium:/tmp/.ICE-unix/5180 Window manager warning: Failed to read saved session file /home/andrew/.metacity/sessions/default0.ms: Failed to open file '/home/andrew/.metacity/sessions/default0.ms': No such file or directory ** Message: Not starting remote desktop server No problems with this, although there appears to be a delay in the opening desktop fully loading. Andrew To manage notifications about this bug go to: https://bugs.launchpad.net/metacity/+bug/150721/+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 99368] Re: SVG rotation renderization broken
Launchpad has imported 10 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=232796. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2007-03-17T22:45:07+00:00 Adam wrote: Description of problem: When displaying svg in firefox from default fedora installation the svg image is garbled. Check e.g.: http://www.lowlevel.cz/log/images/tuxtosh3.svg Version-Release number of selected component (if applicable): firefox-1.5.0.10-5.fc6 How reproducible: always Expected results: Check the firefox downloaded from mozilla.com pages. Additional info: Could be related to cairo?! Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/99368/comments/0 On 2007-03-17T22:50:46+00:00 Matěj wrote: Created attachment 150321 rendering in Epiphany 2.16.3-3.fc6 Just to add one data-point -- this is rendering in epiphany on FC6. Looks garbled to me as well. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/99368/comments/1 On 2007-03-18T21:51:09+00:00 Adam wrote: Definitely. But epiphany is also using gecko - I'll bet on some library behind. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/99368/comments/2 On 2007-03-26T11:35:46+00:00 Martin wrote: Hm, all our gecko apps look broken. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/99368/comments/3 On 2007-03-26T13:22:22+00:00 Martin wrote: Looks like a problem with system cairo library. When firefox is built with "--disable-system-cairo", svg rendering works fine. Reassigning. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/99368/comments/4 On 2007-03-26T13:23:08+00:00 Martin wrote: btw. broken in rawhide, too. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/99368/comments/5 On 2007-05-23T10:59:42+00:00 Adam wrote: Still present in latest rawhide liveCD image for F7. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/99368/comments/12 On 2007-05-24T22:47:52+00:00 Sylvain wrote: Launchpad bug (also affecting Ubuntu): https://bugs.launchpad.net/fedora/+source/firefox/+bug/99368 Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/99368/comments/17 On 2007-07-30T09:51:39+00:00 Sylvain wrote: This is fixed in version 2.0.0.5-1.fc7 Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/99368/comments/30 On 2007-07-30T09:54:05+00:00 Martin wrote: aha, thanks for the notice. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/99368/comments/31 ** Changed in: firefox (Fedora) Importance: Unknown => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/99368 Title: SVG rotation renderization broken Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Fix Released Status in firefox package in Fedora: Fix Released Bug description: Binary package hint: firefox Firefox 2.0.0.3 in Ubuntu Feisty doesn't render properly the SVG rotations, some parts of the image disappear or are corrupted. It can be tested with http://croczilla.com/svg/samples/opacity1/opacity1.xml or with any other SVG with rotations. It works correctly with the same version of Firefox in Ubuntu Edgy. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/99368/+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 275998] Re: internal mic capture very low volume when routed through pulseaudio
** Changed in: alsa-lib (Fedora) Importance: Unknown => High -- 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/275998 Title: internal mic capture very low volume when routed through pulseaudio Status in Linux: Invalid Status in PulseAudio: Unknown Status in alsa-lib package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Invalid Status in alsa-lib package in Fedora: Won't Fix Status in pulseaudio package in openSUSE: Invalid Bug description: Hi, I have a dell xps m1530 laptop with the following internal audio device: 00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02) In hardy, sound recording from the internal mic works great, but in Ibex sound recording with the internal mic is very silent. I can't make it louder with the gnome volume control and alsamixer. See https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/275998/comments/109 for a temporary solution To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/275998/+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 385561] Re: broken fonts in firefox with kms enabled
Launchpad has imported 67 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=495323. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2009-04-11T22:05:18+00:00 Tomasz wrote: Created attachment 339197 web browser with corrupted text Description of problem: Sometimes some letters became corrupted. It happens after running compiz, but even after stopping compiz and staring metacity (within one session) text stays corrupted. I'm not using xorg.conf, so I have whatever configuration is default in F11 (so KMS, UXA, DRI2 I believe). Version-Release number of selected component (if applicable): xorg-x11-drv-intel-2.6.99.902-2.fc11.x86_64 mesa-libGL-7.5-0.8.fc11.x86_64 kernel-2.6.29.1-52.fc11.x86_64 compiz-0.7.8-18.fc11.x86_64 xorg-x11-server-Xorg-1.6.0-19.fc11.x86_64 How reproducible: Always, corruption appear withing hour of running compiz. If compiz is started as part of session (by enabling Desktop Effects), corruption is visible in terminal at once. Steps to Reproduce: 1. Start compiz 2. Do anything for some time. 3. Actual results: Some letters became garbled, see screenshot. Expected results: Ponies. Additional info: Hardware is Lenovo Thinkpad T400 with Centrino 2, 4GB RAM. 00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- intel/+bug/385561/comments/0 On 2009-04-11T22:06:10+00:00 Tomasz wrote: Created attachment 339198 Xorg.0.log while text corrupted Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- intel/+bug/385561/comments/1 On 2009-04-13T17:12:30+00:00 Edney wrote: Seeing this here also. Running KDE 4.2 with compositing enabled, no xorg.conf either and the texts get corrupted after a long period of use. Anothere way to make it happen is to run wine, in my case i run it to play Warcraft. When i get back, texts are messy. Any information, i can get. Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- intel/+bug/385561/comments/2 On 2009-04-14T00:54:24+00:00 Edney wrote: Created attachment 339402 Weird screen Just in case it wasn't clear yet. Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- intel/+bug/385561/comments/3 On 2009-04-17T22:37:34+00:00 James wrote: Seen here, too. Most often noticed in Firefox, but corruption of glyphs shows up elsewhere. xorg-x11-server-Xorg-1.6.1-6.fc11.x86_64 freetype-2.3.9-3.fc11.x86_64 freetype-2.3.9-3.fc11.i586 xorg-x11-drv-intel-2.6.99.902-3.fc11.x86_64 Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- intel/+bug/385561/comments/4 On 2009-04-22T16:10:41+00:00 Jesse wrote: I'm seeing this as well with i965 Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- intel/+bug/385561/comments/5 On 2009-04-22T16:10:55+00:00 Jesse wrote: Oh and yes, I'm using compiz. Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- intel/+bug/385561/comments/6 On 2009-04-24T16:27:59+00:00 Kevin wrote: I am seeing this here as well with Xfce. Some observations: It seems that it's just some random font that gets corrupted glyphs after some time, then any use of that font results in the corrupted glyphs. I have seen it in: midori, xchat, Terminal. It varies. I have COMPOSITE enabled, but disabling it doesn't bring back the fonts once they are corrupted. My card is: 00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03) I don't see anything out of the ordinary in my /var/log/Xorg.0.log. An example of corruption: http://www.scrye.com/~kevin/fedora/fonts-20090423.png I'm happy to help with any additional debugging. This would be a very good one to fix before release. Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- intel/+bug/385561/comments/7 On 2009-04-24T17:02:53+00:00 Wade wrote: Getting the same thing, 00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)
[Desktop-packages] [Bug 704623] Re: Thunderbird renders system unusable / uses 100% CPU while indexing new messages
** Changed in: thunderbird (Fedora) Status: Unknown => Fix Released ** Changed in: thunderbird (Fedora) Importance: Unknown => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/704623 Title: Thunderbird renders system unusable / uses 100% CPU while indexing new messages Status in Mozilla Thunderbird: Expired Status in thunderbird package in Ubuntu: Fix Released Status in icedove package in Debian: New Status in thunderbird package in Fedora: Fix Released Bug description: Binary package hint: thunderbird After starting Thunderbird, then open any available nntp-server (news.gmane.org, or news.individual.org (you'll need an account to access this server)). Thunderbird will immediately block on any newsgroup with a reasonable amount of new messages. It will consume 100% CPU, slow down the whole system significantly. After a while Thunderbird is grayed out most of the time. You can't access it anymore. Sometimes this lasts for hours. Working with Thunderbird is impossible. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: thunderbird 3.1.7+build3+nobinonly-0ubuntu0.10.10.1 Uname: Linux 2.6.36.2 x86_64 Architecture: amd64 Date: Tue Jan 18 21:29:52 2011 ProcEnviron: PATH=(custom, user) LANG=de_DE.utf8 SHELL=/bin/bash SourcePackage: thunderbird To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/704623/+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 1673649] Re: Xorg crashed with SIGABRT in OsAbort()
This usually happens for me when I login and the X session is started, which sends me back to the login. I have made the observation that this doesn't happen if a stable network connection is already present. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1673649 Title: Xorg crashed with SIGABRT in OsAbort() Status in xorg-server package in Ubuntu: Confirmed Bug description: Crashed on connecting with VNC Client. Using vnc4server. ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: xserver-xorg-core 2:1.18.4-1ubuntu9 ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1 Uname: Linux 4.10.0-13-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CrashCounter: 1 Date: Fri Mar 17 12:28:21 2017 ExecutablePath: /usr/lib/xorg/Xorg InstallationDate: Installed on 2017-02-06 (38 days ago) InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64 (20170125) ProcCmdline: /usr/lib/xorg/Xorg -core :1 -seat seat0 -auth /var/run/lightdm/root/:1 -nolisten tcp vt8 -novtswitch ProcEnviron: PATH=(custom, no user) Signal: 6 SourcePackage: xorg-server StacktraceTop: OsAbort () ?? () FatalError () xf86PostProbe () InitOutput () Title: Xorg crashed with SIGABRT in OsAbort() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1673649/+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 1724583] Re: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics
Launchpad has imported 7 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=1402283. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2016-12-07T07:42:06+00:00 mvetter wrote: Created attachment 1228916 failed_wayland_gnome_shell_log.txt (journalctl) Description of problem: On a system with two graphics cards (Intel integrated graphics controller and an AMD discrete card), gnome-shell crashes in wayland mode (returns to the gdm login screen). The machine is using the Intel integrated graphics for video output. The AMD card has no monitors attached to it. It's only used for GPGPU computing via OpenCL. When the AMD card is removed, gnome-shell works correctly in wayland mode. Version-Release number of selected component (if applicable): 3.22.2-2.fc25 How reproducible: Always. Steps to Reproduce: 1. install second graphics card 2. boot machine 3. gnome-shell fails in Wayland mode Actual results: gnome-shell does not work in Wayland mode when two graphics cards are present. Expected results: gnome-shell should work in Wayland mode, no matter how many video cards the system has. Additional info: kernel 4.8.11-300 extract from lspci: 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06) 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Oland GL [FirePro W2100] journalctl log has: Dec 07 16:32:49 localhost.localdomain gnome-shell[]: Can't initialize KMS backend: could not find drm kms device Dec 07 16:32:49 localhost.localdomain gnome-session[2189]: gnome-session-binary[2189]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 Dec 07 16:32:49 localhost.localdomain gnome-session-binary[2189]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 Dec 07 16:32:49 localhost.localdomain gnome-session-binary[2189]: Unrecoverable failure in required component org.gnome.Shell.desktop Dec 07 16:32:49 localhost.localdomain gdm-password][2164]: pam_unix(gdm-password:session): session closed for user tmp I've attached two logs: one for booting into gdm, and one for attempting to log in using gnome-shell. Reply at: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/comments/0 On 2016-12-07T07:43:50+00:00 mvetter wrote: Created attachment 1228917 failed_gdm_log.txt (journalctl) Reply at: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/comments/1 On 2016-12-07T08:41:54+00:00 mvetter wrote: Same problem happens when the AMD card is swapped out for an Nvidia card. Reply at: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/comments/2 On 2016-12-12T17:34:01+00:00 sebby2k wrote: I can confirm this also happens on my system. Logging into Fedora 25 Gnome wayland session fails on Dell laptop with Intel Haswell CPU and discrete Radeon HD 8790M graphics. This used to work fine on F24 w/ 4.7.x kernel. Hardware name: Dell Inc. Latitude E6540/0725FP Version-Release number of selected component (if applicable): Name: kernel-core Arch: x86_64 Epoch : 0 Version : 4.8.11 Release : 300.fc25 Name: gnome-shell Arch: x86_64 Epoch : 0 Version : 3.22.2 Release : 2.fc25 Name: mutter Arch: i686 Epoch : 0 Version : 3.22.2 Release : 3.fc25 I ended up disabling radeon kms mode setting by adding radeon.modeset=0 to grub. With this kernel configuration, I can now start Gnome Wayland session successfully Reply at: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/comments/3 On 2017-01-02T19:34:17+00:00 Carwyn wrote: Same with these two cards on F25: 0:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06) 01:00.0 VGA compatible controller: NVIDIA Corporation GM107 [GeForce GTX 750 Ti] (rev a2) nouveau is the primary with the i915 unused. Reply at: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/comments/4 On 2017-01-02T22:12:21+00:00 Carwyn wrote: Seems to be a similar problem to bug #1403512 Reply at: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/comments/5 On 2017-05-04T08:09:10+00:00 Pavel wrote: Same here, workaround with radeon.modeset=0 helped with the
[Desktop-packages] [Bug 1725836] Re: No more than 2 displays work simultaneously
This could be related to OpenGL texture sizes or something similar. Unity7 (Compiz) has workarounds to avoid that limitation. And Xfce avoids it by not using hardware accelerated compositing at all (last I checked). It's not surprising if only Gnome Shell hits a problem like this... Do you get the same bug logging in to "Ubuntu" vs "Ubuntu on Xorg"? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1725836 Title: No more than 2 displays work simultaneously Status in Mutter: Confirmed Status in gnome-shell package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: I have three displays that worked fine in 17.04. Now ith 17.10 I can only use two of them. Either 1 & 2, 1& 3 or 2 2 & 3. All three seem to be properly specified in monitors.xml. The display setup scree detects all three. UBUNTU 17.10 AMD PitcairnLSB Version: core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch --- ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-02-23 (242 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Package: mutter PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Tags: artful Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-20 (3 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1725836/+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 1707352] Re: the change from libsane to libsane1 broke many (all?) 3rd party plug-ins for sane
Hello PeterPall, or anyone else affected, Accepted sane-backends into artful-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/sane- backends/1.0.27-1~experimental2ubuntu2.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-artful to verification-done-artful. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-artful. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Tags removed: verification-failed verification-failed-artful ** Tags added: verification-needed-artful -- 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/1707352 Title: the change from libsane to libsane1 broke many (all?) 3rd party plug- ins for sane Status in sane-backends package in Ubuntu: Fix Released Status in sane-backends source package in Artful: Fix Committed Status in sane-backends package in Debian: New Bug description: Note to SRU Team The first proposed fix (1.0.27-1~experimental2ubuntu2) failed because it needed to be a versioned Provides, not just a Provides. Impact == 1) The Debian maintainer renamed libsane to libsane1-experimental "to match with the soname". This apparently fixes a Lintian warning, but makes installing 3rd-party plug-ins hard, as they typically depend on "libsane", not on "libsane1". The first try to add a "Provides: libsane" to libsane1 (which created a virtual package) didn't make drivers installable that claim to depend on a minimum version of libsane as virtual packages are ignored in this case. 2) The soname change might be justified by the new version breaking (several? most?) 3rd party plug-ins even if the library version number doesn't indicate any bigger change than any ordinary new version of the library - which might indicate that this phenomenon might be an upstream bug. libsane 1.0.25 in zesty includes libsane.so.1.25 libsane1 1.0.27 in artful includes libsane.so.1.27 It is to note that depending on the manufacturer for many old scanners there won't be new versions of the plug-ins that are recompiled like this. Test Case = Visit http://support.epson.net/linux/en/iscan_c.html Download the amd64 deb .tar.gz Unzip it. Install the iscan .deb from the core folder. It won't install before this SRU because it Depends: libsane Regression Potential The fix here was proposed to the Debian maintainer in July but there's been virtually zero response on it. In the meantime the workaround that was proposed initially has started to result in automatically uninstalling gtk - which makes the system basically useless. It doesn't seem like adding the Provides will make things any worse for third-party drivers but it has a goodme chance of making things better for some. Original Bug Report === I don't know if that can be prevented in the long run. But both brscan (for my brother scanner) and iscan (for my epson scanners) have been broken by the change from libsane to libsane1. For iscan I have unpackaged the debian package, changed the dependency it contains from libsane to libsane1 and installed the changed package. But even then my epson scanners no more work leaving me without any scanner => Reporting a bug. Impossibility of workarounds Just installing an old version of libsane is impossible as it uninstalls libgtk (which depends on libsane1 which conflicts with libsane) making the system basically useless. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental1ubuntu2 Uname: Linux 4.13.0-041300rc2-lowlatency x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 Date: Sat Jul 29 08:38:15 2017 EcryptfsInUse: Yes SourcePackage: sane-backends UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1707352/+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 1724738] Re: gnome-control-center crashed with SIGSEGV
*** This bug is a duplicate of bug 1720400 *** https://bugs.launchpad.net/bugs/1720400 Happened right after logging in to a google account -- 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/1724738 Title: gnome-control-center crashed with SIGSEGV Status in gnome-control-center package in Ubuntu: Confirmed Bug description: g-c-c hangs then crashes after successful adding online account ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.26.1-0ubuntu4 Uname: Linux 4.13.7-041307-generic x86_64 NonfreeKernelModules: 8723bu ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Oct 19 11:13:19 2017 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-08-30 (49 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcCmdline: gnome-control-center background SegvAnalysis: Segfault happened at: 0x7f85caf39b3b:mov0x8(%rax),%rax PC (0x7f85caf39b3b) ok source "0x8(%rax)" (0x0008) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so Title: gnome-control-center crashed with SIGSEGV UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago) UserGroups: adm cdrom dip i2c lpadmin plugdev sambashare sudo video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1724738/+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 1725836] Re: No more than 2 displays work simultaneously
** Changed in: mutter Status: Unknown => Confirmed ** Changed in: mutter Importance: Unknown => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1725836 Title: No more than 2 displays work simultaneously Status in Mutter: Confirmed Status in gnome-shell package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: I have three displays that worked fine in 17.04. Now ith 17.10 I can only use two of them. Either 1 & 2, 1& 3 or 2 2 & 3. All three seem to be properly specified in monitors.xml. The display setup scree detects all three. UBUNTU 17.10 AMD PitcairnLSB Version: core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch --- ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-02-23 (242 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Package: mutter PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Tags: artful Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-20 (3 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1725836/+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 1699360] Re: package libpam-systemd:amd64 232-21ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
** Changed in: pam (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1699360 Title: package libpam-systemd:amd64 232-21ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in debconf package in Ubuntu: Confirmed Status in gnome-software package in Ubuntu: Incomplete Status in pam package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Bug description: this all ProblemType: Package DistroRelease: Ubuntu 17.04 Package: libpam-systemd:amd64 232-21ubuntu4 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 Date: Wed Jun 21 00:45:00 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-06-19 (1 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: systemd Title: package libpam-systemd:amd64 232-21ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1699360/+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 1724487] Re: Quirk for 2-button mouse Logitech M560
What's the point of this bug? You're not saying what to quirk, the driver you're using is not -evdev and any quirks should really go upstream anyway.. (libinput) ** Changed in: xserver-xorg-input-evdev (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1724487 Title: Quirk for 2-button mouse Logitech M560 Status in xserver-xorg-input-evdev package in Ubuntu: Invalid Bug description: # dmidecode 3.0 Getting SMBIOS data from sysfs. SMBIOS 3.0.0 present. Table at 0x000E. Handle 0x, DMI type 0, 24 bytes BIOS Information Vendor: Dell Inc. Version: 1.5.8 Release Date: 08/07/2017 Address: 0xF Runtime Size: 64 kB ROM Size: 16384 kB Characteristics: PCI is supported PNP is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported EDD is supported Japanese floppy for NEC 9800 1.2 MB is supported (int 13h) 5.25"/1.2 MB floppy services are supported (int 13h) 3.5"/720 kB floppy services are supported (int 13h) 3.5"/2.88 MB floppy services are supported (int 13h) Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) ACPI is supported USB legacy is supported Smart battery is supported BIOS boot specification is supported Function key-initiated network boot is supported Targeted content distribution is supported UEFI is supported BIOS Revision: 1.5 Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: Dell Inc. Product Name: Latitude 7280 Version: Not Specified Serial Number: B81LLH2 UUID: 4C4C4544-0038-3110-804C-C2C04F4C4832 Wake-up Type: Power Switch SKU Number: 079F Family: Latitude Handle 0x0002, DMI type 2, 15 bytes Base Board Information Manufacturer: Dell Inc. Product Name: 0KK5D1 Version: A00 Serial Number: /B81LLH2/CN1296379S0540/ Asset Tag: Not Specified Features: Board is a hosting board Board is replaceable Location In Chassis: Not Specified Chassis Handle: 0x0003 Type: Motherboard Contained Object Handles: 0 Handle 0x0003, DMI type 3, 22 bytes Chassis Information Manufacturer: Dell Inc. Type: Notebook Lock: Not Present Version: Not Specified Serial Number: B81LLH2 Asset Tag: Not Specified Boot-up State: Safe Power Supply State: Safe Thermal State: Safe Security Status: None OEM Information: 0x Height: Unspecified Number Of Power Cords: 1 Contained Elements: 0 SKU Number: Notebook Handle 0x0004, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: JDOCK1 Internal Connector Type: None External Reference Designator: DOCK External Connector Type: Other Port Type: None Handle 0x0005, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: JCRT1 Internal Connector Type: None External Reference Designator: CRT External Connector Type: Other Port Type: Video Port Handle 0x0006, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: JHDMI Internal Connector Type: None External Reference Designator: HDMI External Connector Type: Other Port Type: Video Port Handle 0x0007, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: JSD1 Internal Connector Type: None External Reference Designator: Cardreader External Connector Type: Other Port Type: None Handle 0x0008, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: JLOM1 Internal Connector Type: None External Reference Designator: Network External Connector Type: RJ-45 Port Type: Network Port Handle 0x0009, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: JUSB1 Internal Connector Type: None
[Desktop-packages] [Bug 1708994] Re: package xserver-xorg-video-ast-hwe-16.04 missing
besides, the driver has been removed from the archive since xenial which would explain why there's no -hwe-16.04 ** Package changed: xorg (Ubuntu) => xserver-xorg-video-ast (Ubuntu) ** Changed in: xserver-xorg-video-ast (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1708994 Title: package xserver-xorg-video-ast-hwe-16.04 missing Status in xserver-xorg-video-ast package in Ubuntu: Invalid Bug description: There is no xserver-xorg-video-ast-hwe-16.04 package. So i can not use the ASpeed graphics for output anymore. I needed the hwe for the GTX 1060 nouveau driver. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: evince 3.18.2-1ubuntu4.1 ProcVersionSignature: Ubuntu 4.10.0-30.34~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-30-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Mon Aug 7 06:51:11 2017 ProcEnviron: LANGUAGE=en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ast/+bug/1708994/+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 1708994] Re: package xserver-xorg-video-ast-hwe-16.04 missing
why on earth would you need that for nvidia hardware? ** Changed in: xorg (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1708994 Title: package xserver-xorg-video-ast-hwe-16.04 missing Status in xserver-xorg-video-ast package in Ubuntu: Invalid Bug description: There is no xserver-xorg-video-ast-hwe-16.04 package. So i can not use the ASpeed graphics for output anymore. I needed the hwe for the GTX 1060 nouveau driver. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: evince 3.18.2-1ubuntu4.1 ProcVersionSignature: Ubuntu 4.10.0-30.34~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-30-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Mon Aug 7 06:51:11 2017 ProcEnviron: LANGUAGE=en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ast/+bug/1708994/+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 1725836] Re: No more than 2 displays work simultaneously
I see both. During power up, the messages appear on displays 1 and 3. The sign in is on screen 2 (primary display). The display manager shows 3 displays, but after the apply is selected, only two work. Why do they work with Xfce and not with gnome? Thanks Peter On Fri, Oct 27, 2017 at 2:20 AM, Daniel van Vugt < daniel.van.v...@canonical.com> wrote: > Thanks. Perhaps we jumped the gun though... > > On your login screen do you see two options "Ubuntu" and "Ubuntu on > Xorg", or only one? > > It looks like you might be experiencing a problem with Xorg judging by > comment #4: > > Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (WW) > RADEON(0): flip queue failed: Invalid argument > Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (WW) > RADEON(0): Page flip failed: Invalid argument > Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (EE) > RADEON(0): present flip failed > Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (WW) > RADEON(0): flip queue failed: Invalid argument > Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (WW) > RADEON(0): Page flip failed: Invalid argument > Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (EE) > RADEON(0): present flip failed > Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (WW) > RADEON(0): flip queue failed: Invalid argument > Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (WW) > RADEON(0): Page flip failed: Invalid argument > Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (EE) > RADEON(0): present flip failed > > ** Bug watch added: GNOME Bug Tracker #789540 >https://bugzilla.gnome.org/show_bug.cgi?id=789540 > > ** Also affects: mutter via >https://bugzilla.gnome.org/show_bug.cgi?id=789540 >Importance: Unknown >Status: Unknown > > ** Also affects: xorg-server (Ubuntu) >Importance: Undecided >Status: New > > ** Changed in: xorg-server (Ubuntu) >Status: New => Incomplete > > ** Changed in: gnome-shell (Ubuntu) >Status: New => Incomplete > > ** Changed in: mutter (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1725836 > > Title: > No more than 2 displays work simultaneously > > Status in Mutter: > Unknown > Status in gnome-shell package in Ubuntu: > Incomplete > Status in mutter package in Ubuntu: > Incomplete > Status in xorg-server package in Ubuntu: > Incomplete > > Bug description: > I have three displays that worked fine in 17.04. > Now ith 17.10 I can only use two of them. Either 1 & 2, 1& 3 or 2 2 & 3. > All three seem to be properly specified in monitors.xml. > The display setup scree detects all three. > UBUNTU 17.10 > AMD PitcairnLSB Version: core-9.20160110ubuntu5-amd64: > core-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9. > 20160110ubuntu5-noarch > --- > ApportVersion: 2.20.7-0ubuntu3 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > DisplayManager: gdm3 > DistroRelease: Ubuntu 17.10 > InstallationDate: Installed on 2017-02-23 (242 days ago) > InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 > (20161012.2) > Package: mutter > PackageArchitecture: amd64 > ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 > Tags: artful > Uname: Linux 4.13.0-16-generic x86_64 > UpgradeStatus: Upgraded to artful on 2017-10-20 (3 days ago) > UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo > _MarkForUpload: True > > To manage notifications about this bug go to: > https://bugs.launchpad.net/mutter/+bug/1725836/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1725836 Title: No more than 2 displays work simultaneously Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: I have three displays that worked fine in 17.04. Now ith 17.10 I can only use two of them. Either 1 & 2, 1& 3 or 2 2 & 3. All three seem to be properly specified in monitors.xml. The display setup scree detects all three. UBUNTU 17.10 AMD PitcairnLSB Version: core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch --- ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-02-23 (242 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Package: mutter PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Tags: artful Uname: Linux 4.13.0-16-generic x86_64
[Desktop-packages] [Bug 1727877] Re: AMD Radeon 520 graphics card not detected in wayland session when using AMD/Intel hybrid laptop
glxgears is not a benchmark ** No longer affects: xorg-server (Ubuntu) ** Changed in: xorg-server Status: New => Invalid ** Project changed: wayland => gnome-control-center (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1727877 Title: AMD Radeon 520 graphics card not detected in wayland session when using AMD/Intel hybrid laptop Status in X.Org X server: Invalid Status in gnome-control-center package in Ubuntu: New Bug description: This is a new laptop HP 15-BS576TX which has Intel HD 620 Integrated graphics and a 2GB AMD Radeon 520 Graphics card running on Ubuntu wayland session. Intel integrated graphics is only listed, if you check gnome-control-centre details page (See attached images). But, if I run [code]DRI_PRIME=1 gnome-control-centre[/code] to reach details info it shows "AMD HAINAN" as the only card available. So, it seems the Xwayland session not automatically managing hybrid graphics (shifts to dedicated card for resource hungry apps). What I expected is Gnome control centre will list both the cards. tl;dr: AMD/Intel hybrid graphics not configured correctly in wayland. Dedicated Card is not showing up in system informations. Here are the details: lspci -knnn shows that AMD Radeon 520 card is detected: 01:00.0 Display controller [0380]: Advanced Micro Devices, Inc. [AMD/ATI] Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / R7 M520] [1002:6660] (rev 83) Subsystem: Hewlett-Packard Company Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430] [103c:832b] Kernel driver in use: radeon Kernel modules: radeon, amdgpu and Integrated Intel HD 620 graphics: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:832b] Kernel driver in use: i915 Kernel modules: i915 lshw -C video *-display description: VGA compatible controller product: HD Graphics 620 vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 02 width: 64 bits clock: 33MHz capabilities: pciexpress msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:128 memory:b000-b0ff memory:a000-afff ioport:6000(size=64) memory:c-d *-display description: Display controller product: Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / R7 M520] vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:01:00.0 version: 83 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi bus_master cap_list rom configuration: driver=radeon latency=0 resources: irq:129 memory:9000-9fff memory:b120-b123 ioport:5000(size=256) memory:b124-b125 Now, if I run any app with DRI_PRIME=1 it works and shows below info: :~$ DRI_PRIME=1 glxinfo |grep -i Opengl* OpenGL vendor string: X.Org OpenGL renderer string: AMD HAINAN (DRM 2.50.0 / 4.13.0-16-generic, LLVM 5.0.0) OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.2.2 OpenGL core profile shading language version string: 4.50 So, I assumed Radeon 520 is working fine. Then, noticed that there is no mention of gallium 3d? I see that there is amdgpu driver module also loaded. From the list, R520 card seems to be supported by the radeon driver. lsmod |grep radeon radeon 1470464 0 ttm94208 2 amdgpu,radeon i2c_algo_bit 16384 3 amdgpu,radeon,i915 drm_kms_helper167936 3 amdgpu,radeon,i915 drm 356352 28 amdgpu,radeon,i915,ttm,drm_kms_helper ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xwayland 2:1.19.5-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CompositorRunning: None CurrentDesktop: GNOME Date: Fri Oct 27 03:50:59 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:832b] Subsystem: Hewlett-Packard Company Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430] [103c:832b] InstallationDate: Installed on 2017-10-22 (4 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: HP HP Laptop 15-bs0xx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=50b901ea-f329-4a72-ae11-f7203ae53c2e ro quiet
[Desktop-packages] [Bug 1707352] Re: the change from libsane to libsane1 broke many (all?) 3rd party plug-ins for sane
1.0.27-1~experimental2ubuntu2 doesn't help - i still get the "libsane not available" error message when trying to install iscan- gt-x820-bundle-1.0.1.x64.deb. My Epson V600 is still not accessible. -- 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/1707352 Title: the change from libsane to libsane1 broke many (all?) 3rd party plug- ins for sane Status in sane-backends package in Ubuntu: Fix Released Status in sane-backends source package in Artful: Fix Committed Status in sane-backends package in Debian: New Bug description: Note to SRU Team The first proposed fix (1.0.27-1~experimental2ubuntu2) failed because it needed to be a versioned Provides, not just a Provides. Impact == 1) The Debian maintainer renamed libsane to libsane1-experimental "to match with the soname". This apparently fixes a Lintian warning, but makes installing 3rd-party plug-ins hard, as they typically depend on "libsane", not on "libsane1". The first try to add a "Provides: libsane" to libsane1 (which created a virtual package) didn't make drivers installable that claim to depend on a minimum version of libsane as virtual packages are ignored in this case. 2) The soname change might be justified by the new version breaking (several? most?) 3rd party plug-ins even if the library version number doesn't indicate any bigger change than any ordinary new version of the library - which might indicate that this phenomenon might be an upstream bug. libsane 1.0.25 in zesty includes libsane.so.1.25 libsane1 1.0.27 in artful includes libsane.so.1.27 It is to note that depending on the manufacturer for many old scanners there won't be new versions of the plug-ins that are recompiled like this. Test Case = Visit http://support.epson.net/linux/en/iscan_c.html Download the amd64 deb .tar.gz Unzip it. Install the iscan .deb from the core folder. It won't install before this SRU because it Depends: libsane Regression Potential The fix here was proposed to the Debian maintainer in July but there's been virtually zero response on it. In the meantime the workaround that was proposed initially has started to result in automatically uninstalling gtk - which makes the system basically useless. It doesn't seem like adding the Provides will make things any worse for third-party drivers but it has a goodme chance of making things better for some. Original Bug Report === I don't know if that can be prevented in the long run. But both brscan (for my brother scanner) and iscan (for my epson scanners) have been broken by the change from libsane to libsane1. For iscan I have unpackaged the debian package, changed the dependency it contains from libsane to libsane1 and installed the changed package. But even then my epson scanners no more work leaving me without any scanner => Reporting a bug. Impossibility of workarounds Just installing an old version of libsane is impossible as it uninstalls libgtk (which depends on libsane1 which conflicts with libsane) making the system basically useless. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental1ubuntu2 Uname: Linux 4.13.0-041300rc2-lowlatency x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 Date: Sat Jul 29 08:38:15 2017 EcryptfsInUse: Yes SourcePackage: sane-backends UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1707352/+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 1727877] [NEW] AMD Radeon 520 graphics card not detected in wayland session when using AMD/Intel hybrid laptop
You have been subscribed to a public bug: This is a new laptop HP 15-BS576TX which has Intel HD 620 Integrated graphics and a 2GB AMD Radeon 520 Graphics card running on Ubuntu wayland session. Intel integrated graphics is only listed, if you check gnome-control-centre details page (See attached images). But, if I run [code]DRI_PRIME=1 gnome-control-centre[/code] to reach details info it shows "AMD HAINAN" as the only card available. So, it seems the Xwayland session not automatically managing hybrid graphics (shifts to dedicated card for resource hungry apps). What I expected is Gnome control centre will list both the cards. tl;dr: AMD/Intel hybrid graphics not configured correctly in wayland. Dedicated Card is not showing up in system informations. Here are the details: lspci -knnn shows that AMD Radeon 520 card is detected: 01:00.0 Display controller [0380]: Advanced Micro Devices, Inc. [AMD/ATI] Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / R7 M520] [1002:6660] (rev 83) Subsystem: Hewlett-Packard Company Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430] [103c:832b] Kernel driver in use: radeon Kernel modules: radeon, amdgpu and Integrated Intel HD 620 graphics: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:832b] Kernel driver in use: i915 Kernel modules: i915 lshw -C video *-display description: VGA compatible controller product: HD Graphics 620 vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 02 width: 64 bits clock: 33MHz capabilities: pciexpress msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:128 memory:b000-b0ff memory:a000-afff ioport:6000(size=64) memory:c-d *-display description: Display controller product: Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / R7 M520] vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:01:00.0 version: 83 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi bus_master cap_list rom configuration: driver=radeon latency=0 resources: irq:129 memory:9000-9fff memory:b120-b123 ioport:5000(size=256) memory:b124-b125 Now, if I run any app with DRI_PRIME=1 it works and shows below info: :~$ DRI_PRIME=1 glxinfo |grep -i Opengl* OpenGL vendor string: X.Org OpenGL renderer string: AMD HAINAN (DRM 2.50.0 / 4.13.0-16-generic, LLVM 5.0.0) OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.2.2 OpenGL core profile shading language version string: 4.50 So, I assumed Radeon 520 is working fine. Then, noticed that there is no mention of gallium 3d? I see that there is amdgpu driver module also loaded. From the list, R520 card seems to be supported by the radeon driver. lsmod |grep radeon radeon 1470464 0 ttm94208 2 amdgpu,radeon i2c_algo_bit 16384 3 amdgpu,radeon,i915 drm_kms_helper167936 3 amdgpu,radeon,i915 drm 356352 28 amdgpu,radeon,i915,ttm,drm_kms_helper ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xwayland 2:1.19.5-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CompositorRunning: None CurrentDesktop: GNOME Date: Fri Oct 27 03:50:59 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:832b] Subsystem: Hewlett-Packard Company Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430] [103c:832b] InstallationDate: Installed on 2017-10-22 (4 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: HP HP Laptop 15-bs0xx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=50b901ea-f329-4a72-ae11-f7203ae53c2e ro quiet splash vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/24/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.22 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 832B dmi.board.vendor: HP dmi.board.version: 23.38 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.22:bd07/24/2017:svnHP:pnHPLaptop15-bs0xx:pvrType1ProductConfigId:rvnHP:rn832B:rvr23.38:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-bs0xx dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP
[Desktop-packages] [Bug 1725836] Re: No more than 2 displays work simultaneously
Thanks. Perhaps we jumped the gun though... On your login screen do you see two options "Ubuntu" and "Ubuntu on Xorg", or only one? It looks like you might be experiencing a problem with Xorg judging by comment #4: Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (WW) RADEON(0): flip queue failed: Invalid argument Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (WW) RADEON(0): Page flip failed: Invalid argument Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (EE) RADEON(0): present flip failed Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (WW) RADEON(0): flip queue failed: Invalid argument Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (WW) RADEON(0): Page flip failed: Invalid argument Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (EE) RADEON(0): present flip failed Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (WW) RADEON(0): flip queue failed: Invalid argument Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (WW) RADEON(0): Page flip failed: Invalid argument Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (EE) RADEON(0): present flip failed ** Bug watch added: GNOME Bug Tracker #789540 https://bugzilla.gnome.org/show_bug.cgi?id=789540 ** Also affects: mutter via https://bugzilla.gnome.org/show_bug.cgi?id=789540 Importance: Unknown Status: Unknown ** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Changed in: mutter (Ubuntu) Status: New => Incomplete -- 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/1725836 Title: No more than 2 displays work simultaneously Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: I have three displays that worked fine in 17.04. Now ith 17.10 I can only use two of them. Either 1 & 2, 1& 3 or 2 2 & 3. All three seem to be properly specified in monitors.xml. The display setup scree detects all three. UBUNTU 17.10 AMD PitcairnLSB Version: core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch --- ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-02-23 (242 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Package: mutter PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Tags: artful Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-20 (3 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1725836/+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 160944] Re: [xpdf] multiple security vulnerabilities
Launchpad has imported 12 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=345101.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.
On 2007-10-22T12:37:39+00:00 Tomas wrote:
Alin Rad Pop of the Secunia Research discovered a vulnerability in
xpdf/Stream.cc code:
An array indexing error exists within the "DCTStream::readProgressiveDataUnit()"
method in xpdf/Stream.cc. This can be exploited to corrupt memory via a
specially crafted PDF file.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/xpdf/+bug/160944/comments/0
On 2007-10-26T06:56:09+00:00 Tomas wrote:
Created attachment 238491
xpdf-3.02pl2 first draft from Derek B. Noonburg addressing
CVE-2007-{4352,5392,5393}
Comments from Derek:
The fixes for the first two bugs (in DCTStream) are pretty
straightforward.
The CCITTFaxStream inner loop code has been rewritten (because I was
unhappy with the design, and it was resulting in too many problems).
Reply at:
https://bugs.launchpad.net/ubuntu/+source/xpdf/+bug/160944/comments/1
On 2007-11-07T16:27:39+00:00 Josh wrote:
This is now public:
http://marc.info/?l=full-disclosure=119445179723160=2
Reply at:
https://bugs.launchpad.net/ubuntu/+source/xpdf/+bug/160944/comments/2
On 2007-11-08T06:03:33+00:00 Fedora wrote:
cups-1.3.4-2.fc8 has been pushed to the Fedora 8 stable repository. If
problems still persist, please make note of it in this bug report.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/xpdf/+bug/160944/comments/3
On 2007-11-08T08:38:17+00:00 Tomas wrote:
KDE security advisory with official patches for kdegraphics and koffice:
http://www.kde.org/info/security/advisory-20071107-1.txt
Reply at: https://bugs.launchpad.net/ubuntu/+source/xpdf/+bug/160944/comments/4
On 2007-11-09T10:33:38+00:00 Tomas wrote:
Official xpdf patch is available on xpdf upstream page:
http://www.foolabs.com/xpdf/download.html
ftp://ftp.foolabs.com/pub/xpdf/xpdf-3.02pl2.patch
Reply at: https://bugs.launchpad.net/ubuntu/+source/xpdf/+bug/160944/comments/7
On 2007-11-09T23:51:51+00:00 Fedora wrote:
cups-1.2.12-7.fc7 has been pushed to the Fedora 7 stable repository. If
problems still persist, please make note of it in this bug report.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/xpdf/+bug/160944/comments/8
On 2008-02-08T08:17:24+00:00 Fedora wrote:
poppler-0.5.4-8.fc7 has been submitted as an update for Fedora 7
Reply at:
https://bugs.launchpad.net/ubuntu/+source/xpdf/+bug/160944/comments/12
On 2008-02-13T05:19:45+00:00 Fedora wrote:
poppler-0.5.4-8.fc7 has been pushed to the Fedora 7 stable repository.
If problems still persist, please make note of it in this bug report.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/xpdf/+bug/160944/comments/13
On 2008-02-13T15:00:40+00:00 Fedora wrote:
poppler-0.5.4-8.fc7 has been pushed to the Fedora 7 stable repository.
If problems still persist, please make note of it in this bug report.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/xpdf/+bug/160944/comments/14
On 2008-02-13T15:09:43+00:00 Fedora wrote:
poppler-0.5.4-8.fc7 has been pushed to the Fedora 7 stable repository.
If problems still persist, please make note of it in this bug report.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/xpdf/+bug/160944/comments/15
On 2008-02-15T15:01:19+00:00 Red wrote:
This issue was addressed in:
Red Hat Enterprise Linux:
cups:
http://rhn.redhat.com/errata/RHSA-2007-1021.html
http://rhn.redhat.com/errata/RHSA-2007-1022.html
gpdf:
http://rhn.redhat.com/errata/RHSA-2007-1025.html
poppler:
http://rhn.redhat.com/errata/RHSA-2007-1026.html
xpdf:
http://rhn.redhat.com/errata/RHSA-2007-1029.html
http://rhn.redhat.com/errata/RHSA-2007-1030.html
tetex:
http://rhn.redhat.com/errata/RHSA-2007-1027.html
kdegraphics:
http://rhn.redhat.com/errata/RHSA-2007-1024.html
Fedora:
kdegraphics:
[Desktop-packages] [Bug 19066] Re: Pango-enabled firefox breaks MathML support
Launchpad has imported 33 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=150393. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2005-03-05T13:53:40+00:00 Joao wrote: >From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 Description of problem: Install the recommended fonts for MathML (http://www.mozilla.org/projects/mathml/fonts/) Compare display with firefox 1.0.1 installed as suggested in http://fedoranews.org/tchung/firefox Version-Release number of selected component (if applicable): firefox-1.0.1-1.3.1, firefox-1.0.1-1.3.2 How reproducible: Always Steps to Reproduce: 1. Install the recommended fonts for MathML (http://www.mozilla.org/projects/mathml/fonts/) 2. Access http://www.mozilla.org/projects/mathml/demo/texvsmml.xhtml or some other MathML test page Actual Results: Alignement all wrong Expected Results: Compare display with firefox 1.0.1 installed as suggested in http://fedoranews.org/tchung/firefox Additional info: Local fonts for MathML include Acrobat Reader PS fonts Mathematica 4.1 tt LaTeX fonts This font set works for Mozilla and other Firefox releases. Additional details if requested. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/19066/comments/0 On 2005-03-24T09:46:17+00:00 Joao wrote: Now it is also present on mozilla-1.7.6-1.3.2 under FC3 It is _not_ present in http://ftp.mozilla.org/pub/mozilla.org/mozilla/releases/mozilla1.7.6/contrib/mozilla-i686-pc-linux-gnu-1.7.6-gtk2+xft.tar.gz So it seems to be introduced by Fedora packaging Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/19066/comments/1 On 2005-03-24T10:11:19+00:00 Joao wrote: I have changed severity to high as this potentially messes up any MathML site accessed from Fedora. Screenshots are available at the good: http://www.math.ist.utl.pt/~jmatos/CapturaEcra-13.png the ugly (the latest mozilla-1.7.6-1.3.2): http://www.math.ist.utl.pt/~jmatos/CapturaEcra-14.png Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/19066/comments/2 On 2005-03-28T19:54:52+00:00 Matt wrote: This seems to be due to Pango, as is assumed do to the timing, since it was enabled default around the beginning of March. If you run: > MOZ_DISABLE_PANGO=1 firefox you can view all the MathML sites correctly (albeit with that annoying Symbol dialog, i.e., #133709). A ye olde post here: http://mail.gnome.org/archives/gtk-i18n-list/2003-February/msg00042.html seems to say that Pango and MathML (Mango?) don't play nicely. Another out there says that Blizzard was working on a corrolary to this problem: http://lists.gnu.org/archive/html/lilypond-devel/2004-05/msg00084.html So, I guess you can't have both worlds right now. I suppose a "Disable Pango if you want to read math" statement is needed in rather BOLD letters at Moz/Firefox Fedora pages/release notes. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/19066/comments/3 On 2005-03-29T00:02:10+00:00 Joao wrote: (In reply to comment #3) > > So, I guess you can't have both worlds right now. I suppose a "Disable Pango > if > you want to read math" statement is needed in rather BOLD letters at > Moz/Firefox > Fedora pages/release notes. This is an update to a release (FC3) for which MathML support existed so release notes wouldn't make much sense. Breaking upstream features in an update does not seem a good policy anyway... >From the point of view someone writing MathML pages this situation is a total mess. It would be acceptable, but a pain, if one could detect from "Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050323 Fedora/1.7.6-1.3.2" that "This Mozilla MathML rendering has been broken for the sake of pango by your Linux distribution. Get a copy from mozilla.org". Come on: one can do something similar with IE with or without MathPlayer but not with Mozilla/Firefox with or without MathML support?! If the maintainer ever reads please consider (from the SPEC file I gather it was not intentional): -- reinstating MathML support in an update for FC3; -- making lack of MathML support for FC4 or FC5 and later detectable by dynamic pages; or get pango vs. MathML fixed! Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/19066/comments/4 On 2005-03-29T00:23:30+00:00 Warren wrote:
[Desktop-packages] [Bug 406036] Re: inkscape crashes using certain input methods: _gdk_input_grab_pointer: assertion failed: (input_window != NULL)
Launchpad has imported 15 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=546179. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2009-12-10T10:20:34+00:00 Glen wrote: abrt 1.0.0 detected a crash. How to reproduce - 1. Create a rectangle 2. Click with the text tool on top of the rectangle you've created. Comment: Clicking with text tool on a rectangle causes crash. Attached file: backtrace cmdline: inkscape component: inkscape executable: /usr/bin/inkscape kernel: 2.6.31.6-162.fc12.x86_64 package: inkscape-0.47-0.17.pre4.20091101svn.fc12 rating: 3 reason: Process was terminated by signal 6 Reply at: https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/406036/comments/42 On 2009-12-10T10:20:37+00:00 Glen wrote: Created attachment 377421 File: backtrace Reply at: https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/406036/comments/43 On 2009-12-13T04:55:46+00:00 Máirín wrote: Hi Glen! Thank you very much for your bug report. This bug looks like a bug we've seen a lot of users experience lately. I believe it is caused by a bug in the gtk2 package, not Inkscape. We have a fix for the text-tool issue in Inkscape addressed by an update to gtk2 which I believe will resolve your problem (we've had several testers confirm it resolved text tool crashes in Inkscape for them) To get the fix, run the following command as root: yum update gtk2 --enablerepo=updates-testing Let me know how it goes! And thanks again for the bug report. Reply at: https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/406036/comments/44 On 2009-12-13T21:07:17+00:00 Glen wrote: Yep, fixed me right up. Thanks! Reply at: https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/406036/comments/45 On 2009-12-15T16:47:00+00:00 Karel wrote: *** Bug 543380 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/406036/comments/49 On 2009-12-15T18:48:24+00:00 Joel wrote: The gtk2 update fixed the problem for me, too. Reply at: https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/406036/comments/50 On 2009-12-22T12:12:52+00:00 Lubomir wrote: *** Bug 545759 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/406036/comments/51 On 2009-12-22T12:12:58+00:00 Lubomir wrote: *** Bug 544822 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/406036/comments/52 On 2009-12-22T12:13:30+00:00 Lubomir wrote: *** Bug 546588 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/406036/comments/53 On 2009-12-22T12:13:41+00:00 Lubomir wrote: *** Bug 548598 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/406036/comments/54 On 2009-12-22T12:13:51+00:00 Lubomir wrote: *** Bug 548661 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/406036/comments/55 On 2009-12-22T12:15:24+00:00 Lubomir wrote: GTK2 was fixed. Big thanks to everyone involved in reporting/triaging. Reply at: https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/406036/comments/56 On 2009-12-22T12:31:55+00:00 Lubomir wrote: *** Bug 544341 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/406036/comments/57 On 2009-12-22T12:32:11+00:00 Lubomir wrote: *** Bug 542411 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/406036/comments/58 On 2010-02-08T00:04:46+00:00 Máirín
[Desktop-packages] [Bug 487362] Re: xorg is eating up memory
Launchpad has imported 3 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=560668. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2010-02-01T15:09:26+00:00 Alan wrote: Description of problem: [RHEL5.3] Xorg Consumes all memory This problem is across a number of systems, about 15 machines, All use KDE. It is possible to make some changes on some systems. What we found out so far is that the machine with the new nVidia driver consumed all memory again. Machines with Vesa drivers are OK so far but the user of that workstation claims that it usually takes some time till it the phenomenon occurs. This case is about one customer who has some sites worldwide. All sites run with same configuration under Sun ULTRA20 M2 Workstation,with nVidia Video card. About 15 of his systems experience this phenomenon worldwide. We tried on one machine to update to a newer nVidia driver, and on another machine to use Vesa driver. It is very problematic for the customer to work with Vesa drivers since he needs to use 1600x1200 screen resolution, and we couln't run this system with such resolution using Vesa driver. After analysing his sar data of workstation with nVidia driver we found out that Xorg begins to consume alot of memory when the user is not working during evening hours. We configured one of the problematic machines to use Vesa drivers,today on that machine Xorg consumes 1.4GB of memory. We configured another machine to use Vesa drivers with an ATI card to make sure that nVidias drivers cause consumption of all memory. (as mentioned previously, we couldn't use 1200x1600 resolution with Vesa driver and nVidia card) In this case we've already seen that the problem reproduces also with ATI video card using Redhat's VESA drives, so this is not video card driver related problem. The customer is currently preparing to deploy RHEL 5 within their organization. The mentioned problem also reproduces on RHEL 4 systems. Version-Release number of selected component (if applicable): How reproducible: It takes a very long time to see this problem One thought about this bug: "how does xorg manage memory for quitting application" question: 12:42 < ofourdan|lunch> pamadio: you can always tell the X server to retain the resources, but that's for very specific use and hardly ever used - But if you want you can :) 12:43 < ofourdan|lunch> one of the use is to set a pixmap to the root window, the app that sets the pixmaps needs to specify thatthe pixmap must not be freed once the app terminates 12:44 < ofourdan|lunch> another use is to make an app to self-recover from a network disconnection. Although this is theorically possible, I am yet to find an apps that implement this :) 12:54 < ofourdan> pamadio: see "man XSetCloseDownMode" 12:55 < ofourdan> pamadio: by default all connections start in DestroyAll mode. >From alanm: I've never seen this in practice either. Steps to Reproduce: Customer s/w has to run for a very long time before this problem is seen Actual results: X.org Server consumes all memory Expected results: Normal operation of Xserver Notes from SEG This looks to be an issue that was supposed to have been fixed in the VESA driver https://enterprise.redhat.com/issue-tracker/?module=issues=view=81559 https://enterprise.redhat.com/issue-tracker/?module=issues=view=83772 The problem here is that there wasn't a reproducer. Since it took so long for this problem to reappear I gather that there isn't an easy way to reproduce this ? I could create a BZ for this but I know that engineering will want to have some way of reproducing this. This looks to me to be a slow memory leak and without some way of reproducing this I don't know if they will do anything about this. The earlier IT's seem to indicate that this is a leak that occurs when closing a client so I would ask the customer if this is something that happens over a long period of time or does the memory consumption occur all of a sudden ? I also don't see any indication of any long running applications that would eat up memory so it looks to be a VESA driver problem where memory isn't being released when a client closes down. Let me know as soon as you can and I'll create a BZ for this but I'm really not sure if engineering will do much about it. The best I can do is pass it on to them and let them decide. 1) given where we are in the development cycle with RHEL 4. It's pretty late in the cycle. 2) the fact that these are U4 systems. I know that they will want to know why the customer systems have not been updated to U8. 3) the lack of a reproducer. While there have been other reporters of similar behaviour from a couple of othe customers, the problems
[Desktop-packages] [Bug 317587] Re: posix apis unreliable on files mounted over gvfs, e.g. truncate, open, causes OpenOffice.org to fail to save
** Changed in: gvfs (Fedora) Importance: Unknown => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/317587 Title: posix apis unreliable on files mounted over gvfs, e.g. truncate, open, causes OpenOffice.org to fail to save Status in gvfs package in Ubuntu: Fix Released Status in gvfs source package in Hardy: Won't Fix Status in gvfs source package in Intrepid: Invalid Status in gvfs source package in Jaunty: Fix Released Status in gvfs package in Fedora: Fix Released Status in gvfs package in Suse: Fix Released Bug description: Binary package hint: gvfs This bug that Caolan (RedHat) mentioned to me may be the cause of most of the problems with OOo working via gvfs filesystems. https://bugzilla.redhat.com/show_bug.cgi?id=479199 Pay particular attention to the test program and the last few comments on the bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/317587/+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 216049] Re: window list restore to current workspace does not work
Launchpad has imported 5 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=484842. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2009-02-10T09:05:13+00:00 Cao wrote: Description of problem: Window List cannot restore the windows in another workspace to current workspace. Version-Release number of selected component (if applicable): gnome-panel-2.25.90-1.fc11 How reproducible: 100% reproducible. Steps to Reproduce: 1. make sure there is a window list on the panel. 2. set the properties of the Window List by right click on the left part of the window list and choose 'Preferences'. 3. set 'Window list content' to 'show windows from all workspaces'. 4. set 'restoring minimized windows' to 'restore to current workspace' 5. open gedit in workspace 2, minimize gedit. and go to worspace 1. 6. left click the icon of gedit in the window list on the panel. Actual results: the program (gedit) cannot be restored. the lable (or icon) of program, which is in the window list, just blinks. Expected results: the program (gedit) can be restored in the current workspace. Additional info: uname -r 2.6.29-0.96.rc3.git12.fc11.i586 Reply at: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/216049/comments/7 On 2009-02-13T06:24:11+00:00 Matthias wrote: http://bugzilla.gnome.org/show_bug.cgi?id=571588 Reply at: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/216049/comments/9 On 2009-02-13T06:59:50+00:00 Matthias wrote: *** Bug 484172 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/216049/comments/10 On 2009-06-09T11:12:15+00:00 Bug wrote: This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle. Changing version to '11'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Reply at: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/216049/comments/13 On 2010-01-06T02:02:19+00:00 Christopher wrote: *** This bug has been marked as a duplicate of bug 377691 *** Reply at: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/216049/comments/17 ** Changed in: gnome-panel (Fedora) Importance: Unknown => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/216049 Title: window list restore to current workspace does not work Status in Metacity: New Status in OpenBox: New Status in gnome-panel package in Ubuntu: Triaged Status in metacity package in Ubuntu: Triaged Status in openbox package in Ubuntu: Confirmed Status in gnome-panel package in Fedora: Invalid Status in metacity package in Fedora: Won't Fix Bug description: Binary package hint: gnome-panel In the window list applet I can observe the following behavior: (this is on hardy with AMD64) - set the preference to: 'restore to current workspace' - minimize a window - try to restore the window in a different workspace It will not work, instead the window in the window list will just flash and do nothing. Only when you click on the minimized window in the correct workspace will it restore. To manage notifications about this bug go to: https://bugs.launchpad.net/metacity/+bug/216049/+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 539708] Re: /usr/lib/cups/filter/pdftoraster failed
Launchpad has imported 33 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=563313. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2010-02-09T19:43:50+00:00 Richard wrote: Description of problem: After updating to ghostscript-8.70-5.fc12.x86_64, the printer only prints black pages with small vertical lines and some patterns on it. After downgrading to ghostscript-8.70-2.fc12.x86_64.rpm, everything works fine again. Version-Release number of selected component (if applicable): ghostscript-8.70-5.fc12.x86_64 cups-1.4.2-20.fc12.x86_64 turboprint-2.12-1.x86_64 (from http://www.turboprint.de/) How reproducible: Always Steps to Reproduce: 1. Update to ghostscript-8.70-5.fc12.x86_64 2. Print something (e.g. a PDF file or a test page). Actual results: The printed page is mostly black with only some vertical stripes and patterns on it. Expected results: The page is printed correctly. Additional info: I am using turboprint as driver for my Canon Pixma IP 4000. I don't know if this is a bug in ghostscript or an incompatibility with turboprint. Anyhow I could reproduce this behaviour on two Fedora 12 x86_64 machines. Reply at: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/539708/comments/0 On 2010-02-11T13:10:11+00:00 Tim wrote: Please attach the PPD for the queue you are using. You can find this in the /etc/cups/ppd directory. Reply at: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/539708/comments/1 On 2010-02-11T22:15:15+00:00 Richard wrote: Created attachment 390356 ppd of the printer queue Reply at: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/539708/comments/2 On 2010-02-12T15:21:26+00:00 Tim wrote: Thanks. This is some kind of regression in the ghostscript cups driver. Reply at: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/539708/comments/3 On 2010-02-12T15:29:07+00:00 Tim wrote: Created attachment 390508 in.ps.bz2 (PostScript input for reproducer) This file, along with the PPD, shows the problem. 1. bunzip2 in.ps.bz2 2. PPD=tp0.ppd gs -sDEVICE=cups -r600x600 -dSAFER -dNOPAUSE -dBATCH -sOutputFile=out.rast 3. rasterview out.rast Reply at: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/539708/comments/4 On 2010-02-16T12:57:34+00:00 Tim wrote: *** Bug 565804 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/539708/comments/5 On 2010-02-16T12:58:46+00:00 Fedora wrote: ghostscript-8.70-6.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/ghostscript-8.70-6.fc12 Reply at: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/539708/comments/6 On 2010-02-16T22:01:38+00:00 Richard wrote: ghostscript-8.70-6.fc12 fixes the bug for me. Thank you! Reply at: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/539708/comments/7 On 2010-02-17T18:22:30+00:00 Fedora wrote: ghostscript-8.71-1.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/ghostscript-8.71-1.fc12 Reply at: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/539708/comments/8 On 2010-02-18T22:50:22+00:00 Peter wrote: 8.71-1.fc12 works for me Reply at: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/539708/comments/9 On 2010-02-19T11:55:34+00:00 Fedora wrote: ghostscript-8.71-2.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/ghostscript-8.71-2.fc12 Reply at: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/539708/comments/10 On 2010-02-19T18:54:02+00:00 John wrote: Using Fedora 12 and turboprint-2.13-2.i586.rpm. Update from ghostscript-8.70-2.fc12.i686.rpm to ghostscript-8.70-5.fc12.i686.rpm started the black print page problem. Update to ghostscript-8.71-1.fc12.i686.rpm initially fixed it but after reboot black page again. Tried
[Desktop-packages] [Bug 665956] Re: Theme änd keyböärd läyöüt göing cräzy
Launchpad has imported 31 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=537708. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2009-11-15T22:03:07+00:00 Matthew wrote: Description of problem: I've been using "keycode 135 = Mode_switch" in my ~/.xmodmap for years, to change my "menu" key into something useful. Starting sometime fairly recently (not sure exactly; sorry) occasionally (no repeatable case, but happens regularly enough to be annoying), the mode_switch gets stuck in on, such that pressing the key and a letter gives its normal version rather than its mode_switch version. (It's as if the equivalent of caps-lock for mode_switch is on.) There doesn't seem to be any cure but hitting mode_switch a bunch of times and other random typing -- eventually it goes off again. Version-Release number of selected component (if applicable): Possibly xorg-x11-drv-evdev-2.3.0-1.fc12.x86_64. I'm just blaming evdev because it's convenient -- could be a lot of things, I suppose. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/665956/comments/0 On 2009-11-16T15:34:40+00:00 Bug wrote: This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle. Changing version to '12'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/665956/comments/1 On 2009-11-16T21:32:27+00:00 Matěj wrote: (In reply to comment #0) > Possibly xorg-x11-drv-evdev-2.3.0-1.fc12.x86_64. I'm just blaming evdev > because > it's convenient -- could be a lot of things, I suppose. Let's try to blame Xserver itself :) (it doesn't matter that much because issues of input go to Peter anyway). Please attach your X server config file (/etc/X11/xorg.conf, if available), output of the dmesg command, and X server log file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link below. We will review this issue again once you've had a chance to attach this information. Thanks in advance. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/665956/comments/2 On 2009-12-14T20:59:09+00:00 Matthew wrote: Created attachment 378349 dmesg output Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/665956/comments/3 On 2009-12-14T21:00:19+00:00 Matthew wrote: Created attachment 378350 Xorg.0.log Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/665956/comments/4 On 2009-12-14T21:06:01+00:00 Matthew wrote: Attached requested logs. This is on my Rawhide box. It also happens on my F12 system at home, which has a different radeon card and generally different hardware overall. I can attach that if you think it might be helpful. I think *maybe* the problem is related to the key _next_ to this one; I've defined that to be Multi_key, and it may be related to hitting that accidentally in some way. I still can't reproduce _on purpose_ though. (But it does happen once every couple of days.) Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/665956/comments/5 On 2009-12-14T21:06:56+00:00 Matthew wrote: Created attachment 378354 xmodmap I must add that the ability to type hearts and flowers was added at the request of my 4-year-old daughter. Just sayin'. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/665956/comments/6 On 2010-01-23T22:18:50+00:00 Chris wrote: -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/665956/comments/7 On 2010-01-23T22:25:17+00:00 Matthew wrote: This is still happening, by the way. And I removed the definition for Multi_key, so that's _not_ it. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/665956/comments/8 On 2010-03-13T11:43:17+00:00 Matthew wrote: This is still happening. It is very annoying. I attached the requested
[Desktop-packages] [Bug 1436772] Re: /usr/bin/nautilus:11:_gtk_css_value_unref:gtk_css_value_shadows_free:_gtk_css_value_unref:g_ptr_array_foreach:ptr_array_free
Launchpad has imported 14 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=1199731. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2015-03-07T15:16:15+00:00 Tim wrote: Description of problem: Locking an encrypted block device from Disks. Version-Release number of selected component: nautilus-3.15.90-1.fc22 Additional info: reporter: libreport-2.4.0 backtrace_rating: 4 cmdline:/usr/bin/nautilus --gapplication-service crash_function: _gtk_css_value_unref executable: /usr/bin/nautilus kernel: 4.0.0-0.rc2.git0.1.fc22.x86_64 runlevel: N 5 type: CCpp uid:1000 Truncated backtrace: Thread no. 1 (10 frames) #0 _gtk_css_value_unref at gtkcssvalue.c:65 #1 gtk_css_value_shadow_free at gtkcssshadowvalue.c:60 #2 gtk_css_value_shadows_free at gtkcssshadowsvalue.c:47 #3 g_ptr_array_foreach at garray.c:1502 #4 ptr_array_free at garray.c:1088 #5 g_ptr_array_unref at garray.c:1036 #6 gtk_css_static_style_dispose at gtkcssstaticstyle.c:98 #8 g_hash_table_remove_all_nodes at ghash.c:548 #10 g_hash_table_remove_all at ghash.c:1428 #11 g_hash_table_destroy at ghash.c:1122 Reply at: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1436772/comments/0 On 2015-03-07T15:16:19+00:00 Tim wrote: Created attachment 999159 File: backtrace Reply at: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1436772/comments/1 On 2015-03-07T15:16:20+00:00 Tim wrote: Created attachment 999160 File: cgroup Reply at: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1436772/comments/2 On 2015-03-07T15:16:21+00:00 Tim wrote: Created attachment 999161 File: core_backtrace Reply at: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1436772/comments/3 On 2015-03-07T15:16:23+00:00 Tim wrote: Created attachment 999162 File: dso_list Reply at: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1436772/comments/4 On 2015-03-07T15:16:26+00:00 Tim wrote: Created attachment 999163 File: environ Reply at: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1436772/comments/5 On 2015-03-07T15:16:29+00:00 Tim wrote: Created attachment 999164 File: limits Reply at: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1436772/comments/6 On 2015-03-07T15:16:32+00:00 Tim wrote: Created attachment 999165 File: maps Reply at: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1436772/comments/7 On 2015-03-07T15:16:33+00:00 Tim wrote: Created attachment 999166 File: open_fds Reply at: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1436772/comments/8 On 2015-03-07T15:16:35+00:00 Tim wrote: Created attachment 999167 File: proc_pid_status Reply at: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1436772/comments/9 On 2015-03-07T15:16:36+00:00 Tim wrote: Created attachment 999168 File: var_log_messages Reply at: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1436772/comments/10 On 2015-03-09T18:36:30+00:00 Matthias wrote: which gtk3 version is this with ? Reply at: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1436772/comments/11 On 2015-03-10T09:18:57+00:00 Tim wrote: That was with gtk3-3.15.9-1.fc22.x86_64. Reply at: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1436772/comments/12 On 2016-07-19T12:56:55+00:00 Fedora wrote: Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience
[Desktop-packages] [Bug 1609700] Re: username is not saved in openconnect connection dialog
Launchpad has imported 18 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=1332491. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2016-05-03T10:46:54+00:00 Matthias wrote: Description of problem: When connecting with NetworkManager-openconnect on Fedora 23 and before, the username and password could be saved. On Fedora 24 (Alpha-7) only the password is saved but the username field is empty, so the username has to be entered each time newly. Version-Release number of selected component (if applicable): 1.2.0-1.fc24 How reproducible: Connect to a vpn twice Steps to Reproduce: 1. enter vpn connection 2. connect and check password save dialog 3. disconnect and connect again Actual results: username is not shown in dialog (only password bullets) login failed is shown if connecting witout entering the username again. Expected results: username should be shown as well Additional info: Reply at: https://bugs.launchpad.net/ubuntu/+source/network-manager- openconnect/+bug/1609700/comments/0 On 2016-05-25T07:54:07+00:00 Robert wrote: Seeing the same problem here on F24 Beta $ rpm -qa|grep openconnect openconnect-7.06-4.fc24.x86_64 NetworkManager-openconnect-1.2.2-1.fc24.x86_64 Reply at: https://bugs.launchpad.net/ubuntu/+source/network-manager- openconnect/+bug/1609700/comments/1 On 2016-05-25T07:56:29+00:00 David wrote: Going to blame NM itself for this. Will strip the stored username from my own config (it was there before I upgraded) and attempt to reproduce... Reply at: https://bugs.launchpad.net/ubuntu/+source/network-manager- openconnect/+bug/1609700/comments/2 On 2016-05-25T07:59:18+00:00 David wrote: Note: NM-openconnect "makes up" secrets as it goes, to remember the authentication form entries (the 'input' ones, not the 'password' ones which end up being stored via libsecret. So at the first *authentication*, because the server offers a form named 'main' which has a 'username' field, I end up with the auth-dialog spitting out an extra secret that was never previously known, which (in F23 and previously at least) resulted in: # grep form: /etc/NetworkManager/system-connections/Intel\ AnyConnect\ VPN form:main:password-flags=1 form:main:username=david.woodho...@intel.com Reply at: https://bugs.launchpad.net/ubuntu/+source/network-manager- openconnect/+bug/1609700/comments/3 On 2016-06-23T12:09:09+00:00 Matthias wrote: The problem still exists in final Fedora 24. Is there a workaround? Reply at: https://bugs.launchpad.net/ubuntu/+source/network-manager- openconnect/+bug/1609700/comments/4 On 2016-07-03T11:13:26+00:00 Lubomir wrote: https://cgit.freedesktop.org/NetworkManager/NetworkManager/log/?h=lr /openconnect-secrets-rh1332491 Reply at: https://bugs.launchpad.net/ubuntu/+source/network-manager- openconnect/+bug/1609700/comments/5 On 2016-07-04T14:39:54+00:00 Thomas wrote: >> setting-vpn: get the flags property name only up to the first ":" in secret According to example from comment 3, form:main:password-flags=1 form:main:username=david.woodho...@intel.com it seems the secret name would be "form:main:username". Wouldn't the patch then lookup for "form-main-flags"? How does that fit with "form:main:password-flags"? Surely the patch does it right, but the commit message does not explain the meaning of the ':'. It should show concrete examples of what openconnect does, and why we would truncate secret names at a colon. It seems to me, that NMSettingVpn:get_secret_flags() should instead allow for a missing flags entry, but also consider whether there is an entry in the secrets. Having a password in the @secrets hash, but no flags in @data, might anyway be considered in inconsistent state. I think, NMSettingVpn should treat "name" as secret if at least one of the following is true: - @secrets hash has an entry "name". - @data hash has an entry "name" + "-flags". If the flags entry is missing, it should assume "0". Above would make sense to me, regardless of any openconnect hacks. Wouldn't that fix the openconnect issue? Reply at: https://bugs.launchpad.net/ubuntu/+source/network-manager- openconnect/+bug/1609700/comments/6 On 2016-07-04T15:31:04+00:00 David wrote: (In reply
[Desktop-packages] [Bug 1020212] Re: gtk apps keep polling for $HOME/.config/ibus/bus dir
Launchpad has imported 5 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=572611. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2010-03-11T17:05:59+00:00 Matthew wrote: If the ~/.config/ibus/bus directory doesn't exist, any gtk app will wake up once per second in an attempt to add a notify on it. The directory should be automatically created to work around this. Reply at: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1020212/comments/0 On 2010-04-08T03:18:50+00:00 Peng wrote: This issue has been fixed in upstream source code. I will build new release for fedora soon. Reply at: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1020212/comments/1 On 2010-04-21T10:24:14+00:00 Fedora wrote: ibus-1.3.2-1.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/ibus-1.3.2-1.fc13 Reply at: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1020212/comments/2 On 2010-04-21T21:55:00+00:00 Fedora wrote: ibus-1.3.2-1.fc13 has been pushed to the Fedora 13 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update ibus'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/ibus-1.3.2-1.fc13 Reply at: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1020212/comments/3 On 2010-04-27T02:18:41+00:00 Fedora wrote: ibus-1.3.2-1.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report. Reply at: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1020212/comments/4 ** Changed in: ibus (Fedora) Status: Unknown => Fix Released ** Changed in: ibus (Fedora) Importance: Unknown => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1020212 Title: gtk apps keep polling for $HOME/.config/ibus/bus dir Status in ibus package in Ubuntu: Fix Released Status in ibus package in Fedora: Fix Released Bug description: I've tried to do my homework but I apologize if this issue has already been fixed or if I'm reporting it to the wrong package. First off, here is my system and package info: $ lsb_release -rd Description:Ubuntu 10.04.4 LTS Release:10.04 $ apt-cache policy ibus ibus: Installed: 1.2.0.20091215-1ubuntu4 Candidate: 1.2.0.20091215-1ubuntu4 Version table: *** 1.2.0.20091215-1ubuntu4 0 500 http://nl.archive.ubuntu.com/ubuntu/ lucid/main Packages 100 /var/lib/dpkg/status I observe that when the directory $HOME/.config/ibus/bus does not exist, *all* GTK apps poll for its creation at roughly four second intervals. To wit: $ strace -re inotify_add_watch -p $(pidof evince) Process 11784 attached - interrupt to quit 0.00 inotify_add_watch(10, "/home/bnoordhuis/.config/ibus/bus", IN_MODIFY|IN_ATTRIB|IN_CLOSE_WRITE|IN_MOVED_FROM|IN_MOVED_TO|IN_CREATE|IN_DELETE|IN_DELETE_SELF|IN_MOVE_SELF|IN_UNMOUNT|IN_ONLYDIR) = -1 ENOENT (No such file or directory) 4.001651 inotify_add_watch(10, "/home/bnoordhuis/.config/ibus/bus", IN_MODIFY|IN_ATTRIB|IN_CLOSE_WRITE|IN_MOVED_FROM|IN_MOVED_TO|IN_CREATE|IN_DELETE|IN_DELETE_SELF|IN_MOVE_SELF|IN_UNMOUNT|IN_ONLYDIR) = -1 ENOENT (No such file or directory) 3.999569 inotify_add_watch(10, "/home/bnoordhuis/.config/ibus/bus", IN_MODIFY|IN_ATTRIB|IN_CLOSE_WRITE|IN_MOVED_FROM|IN_MOVED_TO|IN_CREATE|IN_DELETE|IN_DELETE_SELF|IN_MOVE_SELF|IN_UNMOUNT|IN_ONLYDIR) = -1 ENOENT (No such file or directory) 4.000487 inotify_add_watch(10, "/home/bnoordhuis/.config/ibus/bus", IN_MODIFY|IN_ATTRIB|IN_CLOSE_WRITE|IN_MOVED_FROM|IN_MOVED_TO|IN_CREATE|IN_DELETE|IN_DELETE_SELF|IN_MOVE_SELF|IN_UNMOUNT|IN_ONLYDIR) = -1 ENOENT (No such file or directory) ^CProcess 11784 detached $ strace -re inotify_add_watch -p $(pidof clock-applet) Process 3647 attached - interrupt to quit 0.00 inotify_add_watch(19, "/home/bnoordhuis/.config/ibus/bus", IN_MODIFY|IN_ATTRIB|IN_CLOSE_WRITE|IN_MOVED_FROM|IN_MOVED_TO|IN_CREATE|IN_DELETE|IN_DELETE_SELF|IN_MOVE_SELF|IN_UNMOUNT|IN_ONLYDIR) = -1 ENOENT (No such file or directory) 4.002690 inotify_add_watch(19,
Re: [Desktop-packages] [Bug 1725836] Re: No more than 2 displays work simultaneously
Did it. I hope I did it correctly. On Thu, Oct 26, 2017 at 10:14 PM, Daniel van Vugt < daniel.van.v...@canonical.com> wrote: > Peter, we're here to help. And Sebastien is right... The fastest way to > a fix for you now is for you to report the bug directly on the Gnome bug > tracker: https://bugzilla.gnome.org/ > > We ask you to do this because the conversation that will happen with the > Gnome guys needs to be with someone who experiences the problem first- > hand (yourself). > > After a fix is available there we will pull it down to here again for > release in Ubuntu. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1725836 > > Title: > No more than 2 displays work simultaneously > > Status in gnome-shell package in Ubuntu: > New > Status in mutter package in Ubuntu: > New > > Bug description: > I have three displays that worked fine in 17.04. > Now ith 17.10 I can only use two of them. Either 1 & 2, 1& 3 or 2 2 & 3. > All three seem to be properly specified in monitors.xml. > The display setup scree detects all three. > UBUNTU 17.10 > AMD PitcairnLSB Version: core-9.20160110ubuntu5-amd64: > core-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9. > 20160110ubuntu5-noarch > --- > ApportVersion: 2.20.7-0ubuntu3 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > DisplayManager: gdm3 > DistroRelease: Ubuntu 17.10 > InstallationDate: Installed on 2017-02-23 (242 days ago) > InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 > (20161012.2) > Package: mutter > PackageArchitecture: amd64 > ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 > Tags: artful > Uname: Linux 4.13.0-16-generic x86_64 > UpgradeStatus: Upgraded to artful on 2017-10-20 (3 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/1725836/+subscriptions > -- 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/1725836 Title: No more than 2 displays work simultaneously Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: I have three displays that worked fine in 17.04. Now ith 17.10 I can only use two of them. Either 1 & 2, 1& 3 or 2 2 & 3. All three seem to be properly specified in monitors.xml. The display setup scree detects all three. UBUNTU 17.10 AMD PitcairnLSB Version: core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch --- ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-02-23 (242 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Package: mutter PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Tags: artful Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-20 (3 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/1725836/+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
