[Desktop-packages] [Bug 1872527] Re: Clipboard doesn't work 100% of the time in Ubuntu 20.04 (in KVM guests)
The problem is still here with Kubuntu 20.04 updated today for guest and host: clipboard works erratically and sometimes is bloked. The proposed solution don't work fr me because I need to copy from host and paste in guest. The only workaround I found is to use mate desktop in the guest. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to spice-vdagent in Ubuntu. https://bugs.launchpad.net/bugs/1872527 Title: Clipboard doesn't work 100% of the time in Ubuntu 20.04 (in KVM guests) Status in qemu package in Ubuntu: Invalid Status in spice package in Ubuntu: Invalid Status in spice-protocol package in Ubuntu: Fix Released Status in spice-vdagent package in Ubuntu: Fix Released Status in virt-manager package in Ubuntu: Invalid Status in spice-protocol source package in Focal: Incomplete Status in spice-vdagent source package in Focal: Incomplete Status in spice-vdagent package in Debian: Fix Released Status in spice package in Fedora: Unknown Bug description: https://gitlab.freedesktop.org/spice/linux/vd_agent/issues/9 --- I'm testing Ubuntu 20.04 LTS (Focal Fossa) Beta. I installed Kubuntu 20.04 and virt-manager as I did many times on Ubuntu 18.04. Unfortunatelly when I run a VM (QEMU-KVM, libvirt, libspice-server1 and spice-vdagent) with another Kubuntu 20.04 guest or with Ubuntu 20.04 guest then clipboard doesn't work right. To test it, please install Kubuntu 20.04 and then install Kubuntu / Ubuntu 20.04 as VM (guest). Open some simple text editor and start Ctrl + C and Ctrl + V plain text. 90% of time it will work and 10% of time it won't. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: virt-manager 1:2.2.1-3ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Apr 13 15:02:22 2020 InstallationDate: Installed on 2020-04-09 (4 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) PackageArchitecture: all SourcePackage: virt-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1872527/+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 1826176] Re: Applications do not receive focus in Wayland sessions
Hello Łukasz, Thanks for this. I have updated to this version yesterday evening and have been working with it for about 10 hours now. First of all I can confirm that as far as I can tell the problem has been fully resolved. All applications that I start from either the (docked via plugin) dash, the applications overview or from desktop icons (plugin again) properly receive focus. And I have not experienced any problems working with this version up till now. I will report back here if I see anything unexpected. -- 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/1826176 Title: Applications do not receive focus in Wayland sessions Status in GNOME Shell: Fix Released Status in Mutter: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Fix Released Status in gnome-shell source package in Disco: Fix Committed Status in mutter source package in Disco: Fix Committed Bug description: [ Impact ] On a fresh install of Ubuntu 19.04 applications that are started from the dash inside a Wayland session often do not receive focus. The behavior is inconsistent. Some applications (like the terminal) always properly get the focus. Some like GEdit en Chromium mostly do not receive focus until suddenly they do. It seems to depend on other applications that are already open and may have the focus but I could not discover the exact pattern. Once clicked or Alt-tabbed into the applications work as expected. But when you simply start typing after opening, for example, GEdit the keystrokes may go to an application window that has just been obscured buy the newly opened one. This bug is similar to bug 1817924 but that one apparently is limited to X sessions. [ QA ] No further verification as this is a fix coming with a GNOME micro release update that is covered by this exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME ProblemType: BugDistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0+git20190410-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 24 11:43:33 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-04-24 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1826176/+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 1826176] Re: Applications started from the dash often do not receive focus
OK, I just filed issue #1211. -- 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/1826176 Title: Applications started from the dash often do not receive focus Status in gnome-shell package in Ubuntu: New Bug description: On a fresh install of Ubuntu 19.04 applications that are started from the dash inside a Wayland session often do not receive focus. The behavior is inconsistent. Some applications (like the terminal) always properly get the focus. Some like GEdit en Chromium mostly do not receive focus until suddenly they do. It seems to depend on other applications that are already open and may have the focus but I could not discover the exact pattern. Once clicked or Alt-tabbed into the applications work as expected. But when you simply start typing after opening, for example, GEdit the keystrokes may go to an application window that has just been obscured buy the newly opened one. This bug is similar to bug 1817924 but that one apparently is limited to X sessions. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0+git20190410-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 24 11:43:33 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-04-24 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1826176/+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 1817924] Re: (In Xorg sessions only) apps launched from gnome shell do not get input focus
Since the bug seemed to have appeared in both environments at the same time I was not expecting two separate bugs. I have opened a new one against Gnome session: bug 1826176. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1817924 Title: (In Xorg sessions only) apps launched from gnome shell do not get input focus Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Disco: Fix Released Bug description: Observed on upgrading to disco-proposed today... When launching an app from the dock or from the applications grid (so i believe it's a gnome-shell thing rather than a dock thing), the app opens, but does not get the input focus. You have to either click in the window, or clicking again on the icon of the running app in the dock works, to give it focus. An extra step my muscle memory isn't prepared for! It seems like the sort of thing that might be an option rather than a bug, but if so, changing this behaviour back to its previous default is not at all obvious (I haven't found a way). So guessing it is a bug. NB: After launching an app this way, *no* window has focus. It is lost by the app that had it before, but not given to the newly started app. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.31.90-1ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 27 15:53:07 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-11 (169 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-01-13 (44 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1817924/+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 1826176] [NEW] Applications started from the dash often do not receive focus
Public bug reported: On a fresh install of Ubuntu 19.04 applications that are started from the dash inside a Wayland session often do not receive focus. The behavior is inconsistent. Some applications (like the terminal) always properly get the focus. Some like GEdit en Chromium mostly do not receive focus until suddenly they do. It seems to depend on other applications that are already open and may have the focus but I could not discover the exact pattern. Once clicked or Alt-tabbed into the applications work as expected. But when you simply start typing after opening, for example, GEdit the keystrokes may go to an application window that has just been obscured buy the newly opened one. This bug is similar to bug 1817924 but that one apparently is limited to X sessions. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0+git20190410-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 24 11:43:33 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-04-24 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco wayland-session -- 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/1826176 Title: Applications started from the dash often do not receive focus Status in gnome-shell package in Ubuntu: New Bug description: On a fresh install of Ubuntu 19.04 applications that are started from the dash inside a Wayland session often do not receive focus. The behavior is inconsistent. Some applications (like the terminal) always properly get the focus. Some like GEdit en Chromium mostly do not receive focus until suddenly they do. It seems to depend on other applications that are already open and may have the focus but I could not discover the exact pattern. Once clicked or Alt-tabbed into the applications work as expected. But when you simply start typing after opening, for example, GEdit the keystrokes may go to an application window that has just been obscured buy the newly opened one. This bug is similar to bug 1817924 but that one apparently is limited to X sessions. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0+git20190410-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 24 11:43:33 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-04-24 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1826176/+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 1817924] Re: (In Xorg sessions only) apps launched from gnome shell do not get input focus
I can now confirm it works in an X session though. So that part is fixed (although I never observed the bug there since I don't normally use X sessions). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1817924 Title: (In Xorg sessions only) apps launched from gnome shell do not get input focus Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Disco: Fix Released Bug description: Observed on upgrading to disco-proposed today... When launching an app from the dock or from the applications grid (so i believe it's a gnome-shell thing rather than a dock thing), the app opens, but does not get the input focus. You have to either click in the window, or clicking again on the icon of the running app in the dock works, to give it focus. An extra step my muscle memory isn't prepared for! It seems like the sort of thing that might be an option rather than a bug, but if so, changing this behaviour back to its previous default is not at all obvious (I haven't found a way). So guessing it is a bug. NB: After launching an app this way, *no* window has focus. It is lost by the app that had it before, but not given to the newly started app. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.31.90-1ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 27 15:53:07 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-11 (169 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-01-13 (44 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1817924/+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 1817924] Re: (In Xorg sessions only) apps launched from gnome shell do not get input focus
This bug also occurs in Wayland on a fresh Disco install. Opening Nautilus, Chromium, GEdit etc. does not properly set the focus to the newly opened windows. I have the mutter version that should contain the fix: root@mizuno:~# apt show mutter Package: mutter Version: 3.32.0+git20190410-1ubuntu1 so the fix does not seem to work on Wayland. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1817924 Title: (In Xorg sessions only) apps launched from gnome shell do not get input focus Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Disco: Fix Released Bug description: Observed on upgrading to disco-proposed today... When launching an app from the dock or from the applications grid (so i believe it's a gnome-shell thing rather than a dock thing), the app opens, but does not get the input focus. You have to either click in the window, or clicking again on the icon of the running app in the dock works, to give it focus. An extra step my muscle memory isn't prepared for! It seems like the sort of thing that might be an option rather than a bug, but if so, changing this behaviour back to its previous default is not at all obvious (I haven't found a way). So guessing it is a bug. NB: After launching an app this way, *no* window has focus. It is lost by the app that had it before, but not given to the newly started app. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.31.90-1ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 27 15:53:07 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-11 (169 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-01-13 (44 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1817924/+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 1817338] Re: Changing sound output doesn't work in gnome-control-center 3.32
I can confirm it is working properly now. Thanks a lot for the fix. -- 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/1817338 Title: Changing sound output doesn't work in gnome-control-center 3.32 Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Disco: Fix Released Bug description: In 19.04, HDMI sound stopped working after some upgrade. The sink is somehow availalbe, but cannot be selected. In gnome-control-center, HDMI output device is listed, but if I choose it, no configuration list appears (see screen capture attached). aplay -l gives me: ~$ aplay -l Liste des Périphériques Matériels PLAYBACK carte 0: PCH [HDA Intel PCH], périphérique 0: ALC269VC Analog [ALC269VC Analog] Sous-périphériques: 0/1 Sous-périphérique #0: subdevice #0 carte 0: PCH [HDA Intel PCH], périphérique 3: HDMI 0 [HDMI 0] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 0: PCH [HDA Intel PCH], périphérique 7: HDMI 1 [HDMI 1] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 0: PCH [HDA Intel PCH], périphérique 8: HDMI 2 [HDMI 2] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 pavucontrol shows HDMI as unplugged. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: franck 5998 F pulseaudio /dev/snd/pcmC1D0c: franck 5998 F...m pulseaudio /dev/snd/controlC0: franck 5998 F pulseaudio CurrentDesktop: GNOME Date: Fri Feb 22 16:16:56 2019 EcryptfsInUse: Yes ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/27/2017 dmi.bios.vendor: LENOVO dmi.bios.version: G7ETA9WW (2.69 ) dmi.board.asset.tag: Not Available dmi.board.name: 2353CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG7ETA9WW(2.69):bd09/27/2017:svnLENOVO:pn2353CTO:pvrThinkPadT430s:rvnLENOVO:rn2353CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430s dmi.product.name: 2353CTO dmi.product.sku: LENOVO_MT_2353 dmi.product.version: ThinkPad T430s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1817338/+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 1817338] Re: Changing sound output doesn't work in gnome-control-center 3.32
I have installed the master branch of the "Sound Input & Output Device chooser" Gnome shell extension replacing the release version that got broken with the recent shell upgrade. This extension now again works properly enabling switching devices so this makes it indeed very likely that the issue is purely a g-c-c one. -- 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/1817338 Title: Changing sound output doesn't work in gnome-control-center 3.32 Status in gnome-control-center package in Ubuntu: Triaged Status in gnome-control-center source package in Disco: Triaged Bug description: In 19.04, HDMI sound stopped working after some upgrade. The sink is somehow availalbe, but cannot be selected. In gnome-control-center, HDMI output device is listed, but if I choose it, no configuration list appears (see screen capture attached). aplay -l gives me: ~$ aplay -l Liste des Périphériques Matériels PLAYBACK carte 0: PCH [HDA Intel PCH], périphérique 0: ALC269VC Analog [ALC269VC Analog] Sous-périphériques: 0/1 Sous-périphérique #0: subdevice #0 carte 0: PCH [HDA Intel PCH], périphérique 3: HDMI 0 [HDMI 0] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 0: PCH [HDA Intel PCH], périphérique 7: HDMI 1 [HDMI 1] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 0: PCH [HDA Intel PCH], périphérique 8: HDMI 2 [HDMI 2] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 pavucontrol shows HDMI as unplugged. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: franck 5998 F pulseaudio /dev/snd/pcmC1D0c: franck 5998 F...m pulseaudio /dev/snd/controlC0: franck 5998 F pulseaudio CurrentDesktop: GNOME Date: Fri Feb 22 16:16:56 2019 EcryptfsInUse: Yes ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/27/2017 dmi.bios.vendor: LENOVO dmi.bios.version: G7ETA9WW (2.69 ) dmi.board.asset.tag: Not Available dmi.board.name: 2353CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG7ETA9WW(2.69):bd09/27/2017:svnLENOVO:pn2353CTO:pvrThinkPadT430s:rvnLENOVO:rn2353CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430s dmi.product.name: 2353CTO dmi.product.sku: LENOVO_MT_2353 dmi.product.version: ThinkPad T430s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1817338/+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 1817338] Re: HDMI sound output not selectable in 19.04 (but works in 18.10)
I have the same bug. I used to work around this by installing an alternative sound device selector shell extension but this one broke down when Gnome shell upgraded to 3.31.91. So now there is no way for me to switch to HDMI output any more. The select box shows the correct devices but selecting a different one has no effect. It is also not saved and when reopening control center the default device is once again selected. -- 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/1817338 Title: HDMI sound output not selectable in 19.04 (but works in 18.10) Status in gnome-control-center package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Invalid Bug description: In 19.04, HDMI sound stopped working after some upgrade. The sink is somehow availalbe, but cannot be selected. In gnome-control-center, HDMI output device is listed, but if I choose it, no configuration list appears (see screen capture attached). aplay -l gives me: ~$ aplay -l Liste des Périphériques Matériels PLAYBACK carte 0: PCH [HDA Intel PCH], périphérique 0: ALC269VC Analog [ALC269VC Analog] Sous-périphériques: 0/1 Sous-périphérique #0: subdevice #0 carte 0: PCH [HDA Intel PCH], périphérique 3: HDMI 0 [HDMI 0] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 0: PCH [HDA Intel PCH], périphérique 7: HDMI 1 [HDMI 1] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 0: PCH [HDA Intel PCH], périphérique 8: HDMI 2 [HDMI 2] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 pavucontrol shows HDMI as unplugged. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: franck 5998 F pulseaudio /dev/snd/pcmC1D0c: franck 5998 F...m pulseaudio /dev/snd/controlC0: franck 5998 F pulseaudio CurrentDesktop: GNOME Date: Fri Feb 22 16:16:56 2019 EcryptfsInUse: Yes ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/27/2017 dmi.bios.vendor: LENOVO dmi.bios.version: G7ETA9WW (2.69 ) dmi.board.asset.tag: Not Available dmi.board.name: 2353CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG7ETA9WW(2.69):bd09/27/2017:svnLENOVO:pn2353CTO:pvrThinkPadT430s:rvnLENOVO:rn2353CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430s dmi.product.name: 2353CTO dmi.product.sku: LENOVO_MT_2353 dmi.product.version: ThinkPad T430s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1817338/+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 1815723] Re: Segmentation fault (core dumped)
*** This bug is a duplicate of bug 1814949 *** https://bugs.launchpad.net/bugs/1814949 I get the same error. Opening from the menu does nothing, using $ gnome-control-center or even $ gnome-control-center display as suggested above results in segmentation fault (core dumped). This is on a Dell XPS13 laptop running Disco Dingo dev branch. ** Changed in: gnome-control-center (Ubuntu) Status: Incomplete => Confirmed -- 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/1815723 Title: Segmentation fault (core dumped) Status in gnome-control-center package in Ubuntu: Confirmed Bug description: Segmentation fault (core dumped) after upgrading to 3.31.90 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.31.90-1ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18 Uname: Linux 4.19.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 13 11:29:40 2019 InstallationDate: Installed on 2018-02-15 (362 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to disco on 2018-10-20 (116 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1815723/+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 1635598] Re: Paste into folder option missing on breadcrumb buttons
I am running Disco Dingo dev. branch now with Nautilus 3.31-90 and it seems they have fixed it. I consider this one closed. -- 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/1635598 Title: Paste into folder option missing on breadcrumb buttons Status in nautilus package in Ubuntu: Confirmed Bug description: Clicking the right mouse button on the breadcrumb-buttons that represent the path to the current folder used to offer on option "Paste into folder". This options is now gone. This is extra annoying since the only alternative is right clicking an EMPTY space in the window area itself. But in the list view mode if the current folder content fills up the window there is no empty space anywhere. Luckily, CTRL+V still works so that is currently the only workaround. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: nautilus 1:3.20.3-1ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Fri Oct 21 12:44:29 2016 GsettingsChanges: InstallationDate: Installed on 2016-10-13 (7 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1635598/+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 1636155] Re: Nautilus does not show mounts
No, this is no longer an issue. It went away when I moved to 17.04. Kind regards, Silvio On 25-01-19 23:38, Sebastien Bacher wrote: > Is that still an issue? Could you describe how those mounts are > configured exactly? It's weird that you describe the behaviour as > inconsistent, it would make sense if they were always or never displayed > but not changing... > > ** Changed in: nautilus (Ubuntu) > Status: New => Incomplete > -- 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/1636155 Title: Nautilus does not show mounts Status in nautilus package in Ubuntu: Incomplete Bug description: I use SSHFS to mount a number of directories on remote servers. Normally, when I create the mounts all Nautilus windows immediately show them in the sidebar and Nautilus also displays desktop icons for them. Since my upgrade to Ubuntu 16.10 this no longer works properly. The mounts are not displayed in either the sidebar and on the desktop. After a certain time (at least minutes) the mounts sometimes appear but this seems inconsistent. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: nautilus 1:3.20.3-1ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Mon Oct 24 13:53:02 2016 InstallationDate: Installed on 2016-10-13 (10 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1636155/+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 1777425] Re: Skype snap segfaults GNOME Shell on Wayland
*** This bug is a duplicate of bug 1754693 *** https://bugs.launchpad.net/bugs/1754693 /var/log/syslog Oct 16 09:55:26 localhost org.gnome.Shell.desktop[16031]: (EE) Oct 16 09:55:26 localhost org.gnome.Shell.desktop[16031]: (EE) Backtrace: Oct 16 09:55:26 localhost org.gnome.Shell.desktop[16031]: (EE) 0: /usr/bin/Xwayland (OsLookupColor+0x139) [0x564749186c39] Oct 16 09:55:26 localhost org.gnome.Shell.desktop[16031]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x50) [0x7fbc34348e1f] Oct 16 09:55:26 localhost org.gnome.Shell.desktop[16031]: (EE) 2: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (__driDriverGetExtensions_virtio_gpu+0x1d7940) [0x7fbc307ae760] Oct 16 09:55:26 localhost org.gnome.Shell.desktop[16031]: (EE) 3: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (__driDriverGetExtensions_virtio_gpu+0x13a021) [0x7fbc306734b1] Oct 16 09:55:26 localhost org.gnome.Shell.desktop[16031]: (EE) 4: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (__driDriverGetExtensions_virtio_gpu+0xc882a) [0x7fbc3059052a] Oct 16 09:55:26 localhost org.gnome.Shell.desktop[16031]: (EE) 5: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (__driDriverGetExtensions_virtio_gpu+0xc887e) [0x7fbc305905ee] Oct 16 09:55:26 localhost org.gnome.Shell.desktop[16031]: (EE) 6: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (__driDriverGetExtensions_virtio_gpu+0xc8929) [0x7fbc305906c9] Oct 16 09:55:26 localhost org.gnome.Shell.desktop[16031]: (EE) 7: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (__driDriverGetExtensions_virtio_gpu+0x2e7d2) [0x7fbc3045c432] Oct 16 09:55:26 localhost org.gnome.Shell.desktop[16031]: (EE) 8: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (__driDriverGetExtensions_virtio_gpu+0x1e481d) [0x7fbc307c835d] Oct 16 09:55:26 localhost org.gnome.Shell.desktop[16031]: (EE) 9: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (__driDriverGetExtensions_virtio_gpu+0x3c6ce9) [0x7fbc30b8ce89] Oct 16 09:55:26 localhost org.gnome.Shell.desktop[16031]: (EE) 10: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (__driDriverGetExtensions_virtio_gpu+0x3c5bd3) [0x7fbc30b8ac93] Oct 16 09:55:26 localhost org.gnome.Shell.desktop[16031]: (EE) 11: /usr/bin/Xwayland (ht_dump_contents+0x79a9) [0x5647490b3c69] Oct 16 09:55:26 localhost org.gnome.Shell.desktop[16031]: (EE) 12: /usr/bin/Xwayland (ht_dump_contents+0x66fb) [0x5647490b168b] Oct 16 09:55:26 localhost org.gnome.Shell.desktop[16031]: (EE) 13: /usr/bin/Xwayland (RegisterResourceName+0x22d) [0x56474917561d] Oct 16 09:55:26 localhost org.gnome.Shell.desktop[16031]: (EE) 14: /usr/bin/Xwayland (ht_dump_contents+0xb9a9) [0x5647490bbbd9] Oct 16 09:55:26 localhost org.gnome.Shell.desktop[16031]: (EE) 15: /usr/bin/Xwayland (glvndGetExports+0xde5) [0x564749195f35] Oct 16 09:55:26 localhost org.gnome.Shell.desktop[16031]: (EE) 16: /usr/bin/Xwayland (SendErrorToClient+0x35e) [0x564749150bae] Oct 16 09:55:26 localhost org.gnome.Shell.desktop[16031]: (EE) 17: /usr/bin/Xwayland (InitFonts+0x3b6) [0x564749154b36] Oct 16 09:55:26 localhost org.gnome.Shell.desktop[16031]: (EE) 18: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xeb) [0x7fbc3417009b] Oct 16 09:55:26 localhost org.gnome.Shell.desktop[16031]: (EE) 19: /usr/bin/Xwayland (_start+0x2a) [0x5647490261ea] Oct 16 09:55:26 localhost org.gnome.Shell.desktop[16031]: (EE) Oct 16 09:55:26 localhost org.gnome.Shell.desktop[16031]: (EE) Segmentation fault at address 0x68 Oct 16 09:55:26 localhost org.gnome.Shell.desktop[16031]: (EE) Oct 16 09:55:26 localhost org.gnome.Shell.desktop[16031]: Fatal server error: Oct 16 09:55:26 localhost org.gnome.Shell.desktop[16031]: (EE) Caught signal 11 (Segmentation fault). Server aborting Oct 16 09:55:26 localhost org.gnome.Shell.desktop[16031]: (EE) Not sure why it uses swrast. glxinfo OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 620 (Kaby Lake GT2) May be related https://forum.snapcraft.io/t/slack-for-linux-crash-on- wayland/5909/7 -- 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/1777425 Title: Skype snap segfaults GNOME Shell on Wayland Status in gnome-shell package in Ubuntu: Incomplete Status in wayland package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: The Skype snap segfaults GNOME Shell on Wayland, crashing the session and sending the user back to the login screen. ``` $ snap info skype tracking: stable refresh-date: today at 11:31 BST installed: 8.22.0.2 (33) 143MB classic $ snap version snap2.33 snapd 2.33 series 16 ubuntu 18.04 kernel 4.15.0-23-generic $ snap info core tracking: beta refresh-date: 10 days ago, at 18:50 BST installed: 16-2.33(4830) 91MB core ``` ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xwayland 2:1.19.6-1ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname:
[Desktop-packages] [Bug 1788510] [NEW] error luego de actualizar ubuntu 18.04
Public bug reported: se congela escritorio ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Aug 22 19:34:38 2018 DistUpgraded: 2018-08-22 07:17:57,952 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS690M [Radeon Xpress 1200/1250/1270] [1002:791f] (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems RS690M [Radeon Xpress 1200/1250/1270] [1179:ff60] InstallationDate: Installed on 2018-08-21 (1 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) MachineType: TOSHIBA Satellite A305D ProcEnviron: LANGUAGE=es_AR:es PATH=(custom, no user) LANG=es_AR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=UUID=9b46ee1c-18a4-4f7d-93a8-e0d1c81c43b0 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-08-22 (0 days ago) dmi.bios.date: 09/16/2008 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.70 dmi.board.asset.tag: Base Board Asset Tag dmi.board.vendor: TOSHIBA dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr1.70:bd09/16/2008:svnTOSHIBA:pnSatelliteA305D:pvrPSAH0U-00P008:rvnTOSHIBA:rn:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: Type1Family dmi.product.name: Satellite A305D dmi.product.version: PSAH0U-00P008 dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Wed Aug 22 18:47:27 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug bionic i386 ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1788510 Title: error luego de actualizar ubuntu 18.04 Status in xorg package in Ubuntu: New Bug description: se congela escritorio ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Aug 22 19:34:38 2018 DistUpgraded: 2018-08-22 07:17:57,952 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS690M [Radeon Xpress 1200/1250/1270] [1002:791f] (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems RS690M [Radeon Xpress 1200/1250/1270] [1179:ff60] InstallationDate: Installed on 2018-08-21 (1 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) MachineType: TOSHIBA Satellite A305D ProcEnviron: LANGUAGE=es_AR:es PATH=(custom, no user) LANG=es_AR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=UUID=9b46ee1c-18a4-4f7d-93a8-e0d1c81c43b0 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-08-22 (0 days ago) dmi.bios.date: 09/16/2008 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.70 dmi.board.asset.tag: Base Board Asset Tag dmi.board.vendor: TOSHIBA dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias:
[Desktop-packages] [Bug 1573581] Re: Showing wrong times for imported calendars
I have the same issue on 17.10. Imported calendars are one hour off (+1). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1573581 Title: Showing wrong times for imported calendars Status in gnome-calendar package in Ubuntu: Confirmed Bug description: I have imported two .ics feeds from two different services, and the times for both feeds are out by two hours. Two hours is exactly the time difference between my timezone and UTC, so my guess is that the feeds are delivering the times in my timezone time, and calendar is interpreting them as UTC and adding the two hours time difference. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-calendar 3.20.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 22 14:36:06 2016 InstallationDate: Installed on 2015-04-27 (361 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: gnome-calendar UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1573581/+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 1635598] Re: Paste into folder option missing on breadcrumb buttons
This has only gotten worse. Paste into folder also disappeared from the menu. Open in terminal has always been lacking. I fail to see why not all items from the context menu on listed folders together with those from the context menu on the view background are being offered on the current column breadcrumb context menu. Remember: on a filled up view in list view mode the background can not be touched so the breadcrumb is the only easily accessible marker for the current folder. -- 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/1635598 Title: Paste into folder option missing on breadcrumb buttons Status in nautilus package in Ubuntu: Confirmed Bug description: Clicking the right mouse button on the breadcrumb-buttons that represent the path to the current folder used to offer on option "Paste into folder". This options is now gone. This is extra annoying since the only alternative is right clicking an EMPTY space in the window area itself. But in the list view mode if the current folder content fills up the window there is no empty space anywhere. Luckily, CTRL+V still works so that is currently the only workaround. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: nautilus 1:3.20.3-1ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Fri Oct 21 12:44:29 2016 GsettingsChanges: InstallationDate: Installed on 2016-10-13 (7 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1635598/+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 1706807] Re: [amdgpu] scrambling/pixelation and jutter upon opening thunderbird
Thank you Jeremy. I totally forgot I enabled those a while ago when Chromium in 17.0 needed a bump and I was being locked out of many secure sites. Helped me then but I should have disabled them asap. Thanks for the pointer, problem solved. -- 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/1706807 Title: [amdgpu] scrambling/pixelation and jutter upon opening thunderbird Status in gnome-shell package in Ubuntu: Confirmed Bug description: There's some screen scrambling/pixelation and jutter upon opening thunderbird. sometimes there's only a small portion of the opened window where you can parts of emails and it has a flickering to it and then the rest of the window opens. I'll provide a video of it once I'm able to record the desktop. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-11.16-generic 4.11.10 Uname: Linux 4.11.0-11-generic x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Jul 26 16:14:39 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'enabled-extensions' b"['dash-to-d...@micxgx.gmail.com', 'refresh-w...@kgshank.net']" b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 'firefox.desktop', 'thunderbird.desktop', 'hexchat.desktop', 'gimp.desktop', 'libreoffice-writer.desktop', 'libreoffice-calc.desktop', 'org.gnome.Terminal.desktop', 'org.gnome.Calculator.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 2017-07-25 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1706807/+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 1706807] Re: [amdgpu] scrambling/pixelation and jutter upon opening thunderbird
I meant 17.10 naturally. -- 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/1706807 Title: [amdgpu] scrambling/pixelation and jutter upon opening thunderbird Status in gnome-shell package in Ubuntu: Confirmed Bug description: There's some screen scrambling/pixelation and jutter upon opening thunderbird. sometimes there's only a small portion of the opened window where you can parts of emails and it has a flickering to it and then the rest of the window opens. I'll provide a video of it once I'm able to record the desktop. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-11.16-generic 4.11.10 Uname: Linux 4.11.0-11-generic x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Jul 26 16:14:39 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'enabled-extensions' b"['dash-to-d...@micxgx.gmail.com', 'refresh-w...@kgshank.net']" b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 'firefox.desktop', 'thunderbird.desktop', 'hexchat.desktop', 'gimp.desktop', 'libreoffice-writer.desktop', 'libreoffice-calc.desktop', 'org.gnome.Terminal.desktop', 'org.gnome.Calculator.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 2017-07-25 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1706807/+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 1706807] Re: [amdgpu] scrambling/pixelation and jutter upon opening thunderbird
I don't know if this is the same bug but since my 17.10 updated Thunderbird to 52.4.0 I am faced with this issue consistently. Thunderbird is unusable this way and I have manually installed a 52.3.0 version to be able to manage my e-mail. This happens both when running under X or Wayland. Gnome shell 3.26. Screenshot attached. ** Attachment added: "Screenshot from 2017-10-04 09-07-55.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1706807/+attachment/4962404/+files/Screenshot%20from%202017-10-04%2009-07-55.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1706807 Title: [amdgpu] scrambling/pixelation and jutter upon opening thunderbird Status in gnome-shell package in Ubuntu: Confirmed Bug description: There's some screen scrambling/pixelation and jutter upon opening thunderbird. sometimes there's only a small portion of the opened window where you can parts of emails and it has a flickering to it and then the rest of the window opens. I'll provide a video of it once I'm able to record the desktop. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-11.16-generic 4.11.10 Uname: Linux 4.11.0-11-generic x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Jul 26 16:14:39 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'enabled-extensions' b"['dash-to-d...@micxgx.gmail.com', 'refresh-w...@kgshank.net']" b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 'firefox.desktop', 'thunderbird.desktop', 'hexchat.desktop', 'gimp.desktop', 'libreoffice-writer.desktop', 'libreoffice-calc.desktop', 'org.gnome.Terminal.desktop', 'org.gnome.Calculator.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 2017-07-25 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1706807/+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 1714410] Re: Can't change display configuration, Method ApplyConfiguration is not implemented on interface org.gnome.Mutter.DisplayConfig
I have the same issue as Shwan (#13). Turning off the laptop screen when an additional display is connected works but is forgotten after restart. So the question remains: is this covered by this bug report or must a new one be created? -- 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/1714410 Title: Can't change display configuration, Method ApplyConfiguration is not implemented on interface org.gnome.Mutter.DisplayConfig Status in gnome-control-center package in Ubuntu: Fix Released Bug description: Since last night's updates, I can no longer change screen resolution or monitor alignment in gnome-control-center anymore (in gnome-shell running under Wayland). gnome-control-center fails silently in the GUI but reports this from the command line: (gnome-control-center:5887): display-cc-panel-WARNING **: Error applying configuration: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Method ApplyConfiguration is not implemented on interface org.gnome.Mutter.DisplayConfig All the available display modes are listed in gnome-control-center (you just can't select them). On the initial login, xrandr only showed two screen resolutions, one for screen XWAYLAND0 of 3840x2160 and another for XWAYLAND1 of 1920x1080, but after unplugging the external monitor and re-plugging it, now xrandr shows eDP-1 with all available modes and HDMI-1 with all available modes (you just can't select them from g-c-c). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.24.3-0ubuntu6 Uname: Linux 4.13.0-041300rc7-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 1 11:47:50 2017 InstallationDate: Installed on 2017-08-16 (15 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. SourcePackage: gnome-control-center UpgradeStatus: Upgraded to artful on 2017-08-17 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1714410/+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 1681523] Re: [Launcher] missing right click options
The workaround Jon describes does nothing for me. This is an extremely annoying bug. Please fix asap! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1681523 Title: [Launcher] missing right click options Status in gnome-terminal package in Ubuntu: Confirmed Bug description: Running : Description: Ubuntu Zesty Zapus (development branch) Release: 17.04 Not sure where to postthis but... Just noticed that "Right Click" options for the "Terminal" App are missing when it's locked to the 'Launcher' side-bar. You used to get the option to open "Open a New Window" or "Open a New Tab" when you right clicked on the launcher icon. Now the only options are "Terminal", "Unlock from Launcher" and "Quit". ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: unity 7.5.0+17.04.20170407.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 378.13 Tue Feb 7 20:10:06 PST 2017 GCC version: gcc version 6.3.0 20170321 (Ubuntu 6.3.0-10ubuntu1) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity_support_test.0: ApportVersion: 2.20.4-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Apr 10 18:44:46 2017 DistUpgraded: Fresh install DistroCodename: zesty DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GK208 [GeForce GT 710B] [10de:128b] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GK208 [GeForce GT 710B] [19da:7326] InstallationDate: Installed on 2017-03-04 (36 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170303) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed root=UUID=4b931084-da89-4473-81b2-7b6e8d83488e ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/19/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FC dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A78M-HD2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFC:bd01/19/2016:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A78M-HD2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1 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.14-0ubuntu1 xserver.bootTime: Mon Apr 10 18:43:48 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.3-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1681523/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to :
[Desktop-packages] [Bug 1661245] [NEW] Need to bump chromium-browser version on Zesty
Public bug reported: Perhaps this bug should be reported against the current Zesty state but the chromium-browser in Zesty is stuck at version 53 which is practically unusable with many HTTPS sites because of erroneous security warnings. The same thin happened on Yakkety and a version bump to 55 solved the issues. Please bump the version on Zesty. ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1661245 Title: Need to bump chromium-browser version on Zesty Status in chromium-browser package in Ubuntu: New Bug description: Perhaps this bug should be reported against the current Zesty state but the chromium-browser in Zesty is stuck at version 53 which is practically unusable with many HTTPS sites because of erroneous security warnings. The same thin happened on Yakkety and a version bump to 55 solved the issues. Please bump the version on Zesty. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1661245/+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 1636155] [NEW] Nautilus does not show mounts
Public bug reported: I use SSHFS to mount a number of directories on remote servers. Normally, when I create the mounts all Nautilus windows immediately show them in the sidebar and Nautilus also displays desktop icons for them. Since my upgrade to Ubuntu 16.10 this no longer works properly. The mounts are not displayed in either the sidebar and on the desktop. After a certain time (at least minutes) the mounts sometimes appear but this seems inconsistent. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: nautilus 1:3.20.3-1ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Mon Oct 24 13:53:02 2016 InstallationDate: Installed on 2016-10-13 (10 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety -- 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/1636155 Title: Nautilus does not show mounts Status in nautilus package in Ubuntu: New Bug description: I use SSHFS to mount a number of directories on remote servers. Normally, when I create the mounts all Nautilus windows immediately show them in the sidebar and Nautilus also displays desktop icons for them. Since my upgrade to Ubuntu 16.10 this no longer works properly. The mounts are not displayed in either the sidebar and on the desktop. After a certain time (at least minutes) the mounts sometimes appear but this seems inconsistent. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: nautilus 1:3.20.3-1ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Mon Oct 24 13:53:02 2016 InstallationDate: Installed on 2016-10-13 (10 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1636155/+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 1635598] [NEW] Paste into folder option missing on breadcrumb buttons
Public bug reported: Clicking the right mouse button on the breadcrumb-buttons that represent the path to the current folder used to offer on option "Paste into folder". This options is now gone. This is extra annoying since the only alternative is right clicking an EMPTY space in the window area itself. But in the list view mode if the current folder content fills up the window there is no empty space anywhere. Luckily, CTRL+V still works so that is currently the only workaround. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: nautilus 1:3.20.3-1ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Fri Oct 21 12:44:29 2016 GsettingsChanges: InstallationDate: Installed on 2016-10-13 (7 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety -- 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/1635598 Title: Paste into folder option missing on breadcrumb buttons Status in nautilus package in Ubuntu: New Bug description: Clicking the right mouse button on the breadcrumb-buttons that represent the path to the current folder used to offer on option "Paste into folder". This options is now gone. This is extra annoying since the only alternative is right clicking an EMPTY space in the window area itself. But in the list view mode if the current folder content fills up the window there is no empty space anywhere. Luckily, CTRL+V still works so that is currently the only workaround. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: nautilus 1:3.20.3-1ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Fri Oct 21 12:44:29 2016 GsettingsChanges: InstallationDate: Installed on 2016-10-13 (7 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1635598/+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 1544480] Re: after upgrading to 16.04 (xubuntu) network drive not mounted
A workaround is describe in this thread. http://ubuntuforums.org/showthread.php?t=2131380 Put a script e.g. fstab to /etc/network/if-up.d containing the following content #!/bin/sh mount -a -- 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/1544480 Title: after upgrading to 16.04 (xubuntu) network drive not mounted Status in gvfs package in Ubuntu: Confirmed Bug description: after upgrading to 16.04 (xubuntu) network drive not mounted Asked by Willem Hobers on 2016-02-06 I upgraded from Xubuntu 14.04 to 16.04, because I would like to attribute to the testing. After the upgrade my network drive does not mount. fstab //192.168.178.73/Thuis /media/Thuis cifs noserverino,guest,user=,nounix,_netdev,dir_mode=0777,file_mode=0777 0 0 This worked until the upgrade. When trying to mount I get: mount: wrong fs type, bad option, bad superblock on //192.168.178.73/Thuis, missing codepage or helper program, or other error (for several filesystems (e.g. nfs, cifs) you might need a /sbin/mount. helper program) In some cases useful info is found in syslog - try dmesg | tail or so. And if I do dmesg | tail, it gives: [ 21.141585] cgroup: new mount options do not match the existing superblock, will be ignored [ 24.103109] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready [ 24.103661] forcedeth :00:07.0 eth1: MSI enabled [ 31.195496] FS-Cache: Loaded [ 31.232146] FS-Cache: Netfs 'cifs' registered for caching [ 31.233761] Key type cifs.spnego registered [ 31.233773] Key type cifs.idmap registered [ 31.234020] CIFS VFS: No username specified [ 327.314333] CIFS VFS: No username specified [ 349.637971] CIFS VFS: No username specified Also see question https://answers.launchpad.net/ubuntu/+question/284714 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gvfs 1.27.4-1ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-49.55~14.04.1-generic 3.19.8-ckt12 Uname: Linux 3.19.0-49-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.19.4-0ubuntu2 Architecture: i386 CurrentDesktop: XFCE Date: Thu Feb 11 11:11:57 2016 InstallationDate: Installed on 2016-01-17 (25 days ago) InstallationMedia: Xubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805) SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1544480/+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 1571311] Re: Nautilus hangs when opening SSHFS shares
Interesting observations: the culprit seemed to be one specific SSHFS mount (I usually create a bunch at onse using a shell-script) that would block opening the first Nautilus window (for any location). If I left that mount out then things worked fine. Then I deleted the .Trash-1000 folder on that server and voila: problem solved. It looks like something in there blocked Nautilus when opening. May have something to do with setting the trash can icon status... Silvio -- 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/1571311 Title: Nautilus hangs when opening SSHFS shares Status in nautilus package in Ubuntu: New Bug description: If I create an SSHFS share while having a Nautilus window open it shows the mount in the sidebar (and on the desktop) and I can access the share without problem. However, If I make the share without a Nautilus window open (or if I close all Nautilus windows after the share has been made) and then try to access the SSHFS share again no window comes up. Nautilus hangs (also for the local filesystem) until I kill the SSHFS share. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Apr 17 12:50:04 2016 InstallationDate: Installed on 2015-11-04 (165 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: nautilus UpgradeStatus: Upgraded to xenial on 2015-12-28 (111 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1571311/+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 1571311] Re: Nautilus hangs when opening SSHFS shares
Clean install of 16.04 release does not solve the problem. An instance of a Nautilus window must be open when creating the SSHFS mounts or all attempts to open a window will hang. After closing the last Nautilus window while mounts are present no new window can be opened until the mounts are dropped. Funny thing: when dropping the mounts the blocking Nautilus windows appear after all. That may lead to quite a stack of them. -- 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/1571311 Title: Nautilus hangs when opening SSHFS shares Status in nautilus package in Ubuntu: New Bug description: If I create an SSHFS share while having a Nautilus window open it shows the mount in the sidebar (and on the desktop) and I can access the share without problem. However, If I make the share without a Nautilus window open (or if I close all Nautilus windows after the share has been made) and then try to access the SSHFS share again no window comes up. Nautilus hangs (also for the local filesystem) until I kill the SSHFS share. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Apr 17 12:50:04 2016 InstallationDate: Installed on 2015-11-04 (165 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: nautilus UpgradeStatus: Upgraded to xenial on 2015-12-28 (111 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1571311/+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 1571311] Re: Nautilus hangs when opening SSHFS shares
Addition: accessing the share when all Nautilus windows are closed is then done from the desktop icon that is created for the share. -- 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/1571311 Title: Nautilus hangs when opening SSHFS shares Status in nautilus package in Ubuntu: New Bug description: If I create an SSHFS share while having a Nautilus window open it shows the mount in the sidebar (and on the desktop) and I can access the share without problem. However, If I make the share without a Nautilus window open (or if I close all Nautilus windows after the share has been made) and then try to access the SSHFS share again no window comes up. Nautilus hangs (also for the local filesystem) until I kill the SSHFS share. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Apr 17 12:50:04 2016 InstallationDate: Installed on 2015-11-04 (165 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: nautilus UpgradeStatus: Upgraded to xenial on 2015-12-28 (111 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1571311/+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 1571311] [NEW] Nautilus hangs when opening SSHFS shares
Public bug reported: If I create an SSHFS share while having a Nautilus window open it shows the mount in the sidebar (and on the desktop) and I can access the share without problem. However, If I make the share without a Nautilus window open (or if I close all Nautilus windows after the share has been made) and then try to access the SSHFS share again no window comes up. Nautilus hangs (also for the local filesystem) until I kill the SSHFS share. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Apr 17 12:50:04 2016 InstallationDate: Installed on 2015-11-04 (165 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: nautilus UpgradeStatus: Upgraded to xenial on 2015-12-28 (111 days ago) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages xenial -- 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/1571311 Title: Nautilus hangs when opening SSHFS shares Status in nautilus package in Ubuntu: New Bug description: If I create an SSHFS share while having a Nautilus window open it shows the mount in the sidebar (and on the desktop) and I can access the share without problem. However, If I make the share without a Nautilus window open (or if I close all Nautilus windows after the share has been made) and then try to access the SSHFS share again no window comes up. Nautilus hangs (also for the local filesystem) until I kill the SSHFS share. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Apr 17 12:50:04 2016 InstallationDate: Installed on 2015-11-04 (165 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: nautilus UpgradeStatus: Upgraded to xenial on 2015-12-28 (111 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1571311/+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 1533251] Re: Ubuntu phone / Aquaris E5: no ringtones when receiving calls, no sound when receiving messages; no sound on speakers
** Attachment added: "info_notworking" https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1533251/+attachment/4602561/+files/info_notworking -- 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/1533251 Title: Ubuntu phone / Aquaris E5: no ringtones when receiving calls, no sound when receiving messages; no sound on speakers Status in indicator-sound package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Confirmed Bug description: Aquaris E5 HD, Ubuntu Edition; Ubuntu 15.04, OTA-8.5 My phone does not ring / play sound on speakers. No problems to answer calls, when having notice by vibrating / display notification; Have phone for some weeks now - at very beginning it worked; short after it stopped playing sounds; swithched sound on in pathwind & uninstalled pathwind - no difference; sometimes it plays ringtones - but have no idea under which circumstances; even when it rang for one time it does not anymore one call later, although I did not make any changes in settings between the calls; does not play sounds / ringtones when selecting them in settings (no difference which ringtone). Today I made full reset on phone (by Settings) - still no sounds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1533251/+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 1533251] Re: Ubuntu phone / Aquaris E5: no ringtones when receiving calls, no sound when receiving messages; no sound on speakers
I think I have the same but though my phone's sound works just occasionally sometimes garbled. Whenever there is no jack plugged in and I start playing something dmesg prints [ 416.722213] lipeng debug|[Sound_Speaker_Turnon] Speaker_Volume: 0 I also appended a version of 'pacmd info' when it's working and when it's not working, but I can't see a significant difference. So I think the problem is lower. ** Attachment added: "info_working" https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1533251/+attachment/4602560/+files/info_working -- 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/1533251 Title: Ubuntu phone / Aquaris E5: no ringtones when receiving calls, no sound when receiving messages; no sound on speakers Status in indicator-sound package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Confirmed Bug description: Aquaris E5 HD, Ubuntu Edition; Ubuntu 15.04, OTA-8.5 My phone does not ring / play sound on speakers. No problems to answer calls, when having notice by vibrating / display notification; Have phone for some weeks now - at very beginning it worked; short after it stopped playing sounds; swithched sound on in pathwind & uninstalled pathwind - no difference; sometimes it plays ringtones - but have no idea under which circumstances; even when it rang for one time it does not anymore one call later, although I did not make any changes in settings between the calls; does not play sounds / ringtones when selecting them in settings (no difference which ringtone). Today I made full reset on phone (by Settings) - still no sounds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1533251/+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 1522316] Re: Icons are too big
What is the status of this bug? The current 16.04 still has huge desktop icons and no way to make them smaller. The Nautilus icon size options are also way too limited. The smallest setting is too small and both larger settings are too big for list mode. Reducing the options to three sizes is a big mistake IMHO. Where we used to have slowly increasing resolutions on computer screens the high res screens today are twice the resolution of main stream screens. If anything we need more options than before. Unity allows pixel sizes for the launcher icons and Nautilus chooses to dumb down. Together with the unfortunate choice of making Nautilus another horrible CSD window desktop usability has taken a huge plunge in 16.04. -- 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/1522316 Title: Icons are too big Status in Nautilus: Incomplete Status in nautilus package in Ubuntu: Triaged Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: On xenial the icons in nautilus (also on the Desktop) are too big. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Thu Dec 3 09:37:55 2015 GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-visible-columns' b"['name', 'size', 'type', 'date_modified']" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2015-04-30 (216 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: nautilus SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit code 2: UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1522316/+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 1516323] Re: With compositing off some apps have a huge black border
Ah Alberts is right: the problem only happens with the terrible CSD windows. Unfortunately in 16.04 Nautilus and GEdit have also become CSD windows. Libra, Orchis and Ultra-Flat are some thems I tried with the same result. I could live with reverting all CSD windows as a workaround :) -- 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/1516323 Title: With compositing off some apps have a huge black border Status in metacity package in Ubuntu: Invalid Bug description: In Xenial I notice with compositing switched off several apps (nautilus, gedit, totem, gnome-tweak-tool, system-monitor & empathy) have a huge black border as shown in the attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: metacity 1:3.18.1-1ubuntu2 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.2-0ubuntu6 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Sat Nov 14 17:56:19 2015 InstallationDate: Installed on 2015-11-10 (4 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151109) SourcePackage: metacity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1516323/+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 1516323] Re: With compositing off some apps have a huge black border
This is not only a problem with Numix. Ambiance and Radiance look kind of OK but they have messed up rounded corners. All the other themes I tried have the same huge borders. Only happens with GTK3 (I think) windows though (Nautilus, Tweak-UI, GEdit). I do not have compositing turned off as far as I know. ** Attachment added: "Screenshot" https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1516323/+attachment/4541677/+files/Screenshot%20from%202015-12-29%2011-16-40.png -- 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/1516323 Title: With compositing off some apps have a huge black border Status in metacity package in Ubuntu: Invalid Bug description: In Xenial I notice with compositing switched off several apps (nautilus, gedit, totem, gnome-tweak-tool, system-monitor & empathy) have a huge black border as shown in the attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: metacity 1:3.18.1-1ubuntu2 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.2-0ubuntu6 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Sat Nov 14 17:56:19 2015 InstallationDate: Installed on 2015-11-10 (4 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151109) SourcePackage: metacity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1516323/+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 1516713] Re: gtk3 overlay scrollbars consistently show wrong behaviour
Btw, this was with a 9px font setting. Most of my colleagues use 8px and some have 7px but I am the senior so that is out of my league :( -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1516713 Title: gtk3 overlay scrollbars consistently show wrong behaviour Status in gedit package in Ubuntu: New Bug description: This is a general bug in GTK3 overlay scrolling (the new kind, not the old "overlay scrollbars" feature). When a window needs both horizontal and vertical scrolling the actual accessible content is reduced by the size of the scrollbars that show up when you move the mouse into the window. Normally the scrollbars are logically outside the scrollable area and that whole are can be scrolled into view. With overlay scrolling this is not the case because the scrollbars OVERLAY the scrollable content, effectively making part of that content unreachable. In case of a text-file opened in GEDIT this means that the last text- line will be covered by the horizontal scrollbar and you can not scroll further down to scroll it above the horizontal scroll bar (see the attached screenshot). The fix would obviously be to extend the logical scroll range of both scrollbars with the width of the other scrollbar if that exists. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: gedit 3.10.4-0ubuntu13 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Mon Nov 16 17:59:46 2015 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2015-11-04 (12 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1516713/+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 1516713] Re: gtk3 overlay scrollbars consistently show wrong behaviour
No, the fonts are not smaller than the line but smaller or at least hardly larger than the sensitive area (feels like about 12 pixels) near the line. As I said, you do not have to hover the line, only close enough to it. I attached a screenshot for the Eclipse editor issue (editing a property file). For some reason it does no show the mouse cursor but I can assure you it was positioned well outside the area covered by the horizontal scroll bar. As you can see there is no way to position the cursor inside the last line (apart from using the keyboard). ** Attachment added: "Screenshot from 2015-11-17 11-23-20.png" https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1516713/+attachment/4520513/+files/Screenshot%20from%202015-11-17%2011-23-20.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1516713 Title: gtk3 overlay scrollbars consistently show wrong behaviour Status in gedit package in Ubuntu: Incomplete Bug description: This is a general bug in GTK3 overlay scrolling (the new kind, not the old "overlay scrollbars" feature). When a window needs both horizontal and vertical scrolling the actual accessible content is reduced by the size of the scrollbars that show up when you move the mouse into the window. Normally the scrollbars are logically outside the scrollable area and that whole are can be scrolled into view. With overlay scrolling this is not the case because the scrollbars OVERLAY the scrollable content, effectively making part of that content unreachable. In case of a text-file opened in GEDIT this means that the last text- line will be covered by the horizontal scrollbar and you can not scroll further down to scroll it above the horizontal scroll bar (see the attached screenshot). The fix would obviously be to extend the logical scroll range of both scrollbars with the width of the other scrollbar if that exists. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: gedit 3.10.4-0ubuntu13 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Mon Nov 16 17:59:46 2015 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2015-11-04 (12 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1516713/+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 1516713] Re: gtk3 overlay scrollbars consistently show wrong behaviour
Thank you Sebastien! If you need anyone to do some testing at any point I will be glad to help. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1516713 Title: gtk3 overlay scrollbars consistently show wrong behaviour Status in gedit package in Ubuntu: Confirmed Bug description: This is a general bug in GTK3 overlay scrolling (the new kind, not the old "overlay scrollbars" feature). When a window needs both horizontal and vertical scrolling the actual accessible content is reduced by the size of the scrollbars that show up when you move the mouse into the window. Normally the scrollbars are logically outside the scrollable area and that whole are can be scrolled into view. With overlay scrolling this is not the case because the scrollbars OVERLAY the scrollable content, effectively making part of that content unreachable. In case of a text-file opened in GEDIT this means that the last text- line will be covered by the horizontal scrollbar and you can not scroll further down to scroll it above the horizontal scroll bar (see the attached screenshot). The fix would obviously be to extend the logical scroll range of both scrollbars with the width of the other scrollbar if that exists. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: gedit 3.10.4-0ubuntu13 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Mon Nov 16 17:59:46 2015 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2015-11-04 (12 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1516713/+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 1516713] Re: gtk3 overlay scrollbars consistently show wrong behaviour
I tried Ambiance and Radience. They initially do have thinner scrollbars. But once the mouse comes close enough to the scrollbar line it extends into its full width. Only if I use a large enough font I can position the cursor in the last line. In Eclipse where I use small fonts this makes the last line of each source file inaccessible in the source editor and makes it very hard to manipulate (expand, collapse) the last item in the package tree list. I Googled and found an environment variable I can set to disable the feature altogether and things are workable this way. But I generally don't like to resort to such obscure settings and like to keep in the mainstream. But having to pick from a rather limited set of themes to have something that kind of works is a bit too restrictive for my taste. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1516713 Title: gtk3 overlay scrollbars consistently show wrong behaviour Status in gedit package in Ubuntu: Incomplete Bug description: This is a general bug in GTK3 overlay scrolling (the new kind, not the old "overlay scrollbars" feature). When a window needs both horizontal and vertical scrolling the actual accessible content is reduced by the size of the scrollbars that show up when you move the mouse into the window. Normally the scrollbars are logically outside the scrollable area and that whole are can be scrolled into view. With overlay scrolling this is not the case because the scrollbars OVERLAY the scrollable content, effectively making part of that content unreachable. In case of a text-file opened in GEDIT this means that the last text- line will be covered by the horizontal scrollbar and you can not scroll further down to scroll it above the horizontal scroll bar (see the attached screenshot). The fix would obviously be to extend the logical scroll range of both scrollbars with the width of the other scrollbar if that exists. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: gedit 3.10.4-0ubuntu13 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Mon Nov 16 17:59:46 2015 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2015-11-04 (12 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1516713/+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 1516713] [NEW] gtk3 overlay scrollbars consitently show wrong behaviour
Public bug reported: This is a general bug in GTK3 overlay scrolling (the new kind, not the old "overlay scrollbars" feature). When a window needs both horizontal and vertical scrolling the actual accessible content is reduced by the size of the scrollbars that show up when you move the mouse into the window. Normally the scrollbars are logically outside the scrollable area and that whole are can be scrolled into view. With overlay scrolling this is not the case because the scrollbars OVERLAY the scrollable content, effectively making part of that content unreachable. In case of a text-file opened in GEDIT this means that the last text- line will be covered by the horizontal scrollbar and you can not scroll further down to scroll it above the horizontal scroll bar (see the attached screenshot). The fix would obviously be to extend the logical scroll range of both scrollbars with the width of the other scrollbar if that exists. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: gedit 3.10.4-0ubuntu13 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Mon Nov 16 17:59:46 2015 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2015-11-04 (12 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily ** Attachment added: "Screenshot of GEDIT with partly covered last line of text" https://bugs.launchpad.net/bugs/1516713/+attachment/4520212/+files/Screenshot%20from%202015-11-16%2017-56-03.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1516713 Title: gtk3 overlay scrollbars consitently show wrong behaviour Status in gedit package in Ubuntu: New Bug description: This is a general bug in GTK3 overlay scrolling (the new kind, not the old "overlay scrollbars" feature). When a window needs both horizontal and vertical scrolling the actual accessible content is reduced by the size of the scrollbars that show up when you move the mouse into the window. Normally the scrollbars are logically outside the scrollable area and that whole are can be scrolled into view. With overlay scrolling this is not the case because the scrollbars OVERLAY the scrollable content, effectively making part of that content unreachable. In case of a text-file opened in GEDIT this means that the last text- line will be covered by the horizontal scrollbar and you can not scroll further down to scroll it above the horizontal scroll bar (see the attached screenshot). The fix would obviously be to extend the logical scroll range of both scrollbars with the width of the other scrollbar if that exists. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: gedit 3.10.4-0ubuntu13 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Mon Nov 16 17:59:46 2015 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2015-11-04 (12 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1516713/+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 1516713] Re: gtk3 overlay scrollbars consistently show wrong behaviour
** Summary changed: - gtk3 overlay scrollbars consitently show wrong behaviour + gtk3 overlay scrollbars consistently show wrong behaviour -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1516713 Title: gtk3 overlay scrollbars consistently show wrong behaviour Status in gedit package in Ubuntu: New Bug description: This is a general bug in GTK3 overlay scrolling (the new kind, not the old "overlay scrollbars" feature). When a window needs both horizontal and vertical scrolling the actual accessible content is reduced by the size of the scrollbars that show up when you move the mouse into the window. Normally the scrollbars are logically outside the scrollable area and that whole are can be scrolled into view. With overlay scrolling this is not the case because the scrollbars OVERLAY the scrollable content, effectively making part of that content unreachable. In case of a text-file opened in GEDIT this means that the last text- line will be covered by the horizontal scrollbar and you can not scroll further down to scroll it above the horizontal scroll bar (see the attached screenshot). The fix would obviously be to extend the logical scroll range of both scrollbars with the width of the other scrollbar if that exists. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: gedit 3.10.4-0ubuntu13 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Mon Nov 16 17:59:46 2015 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2015-11-04 (12 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1516713/+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 1516713] Re: gtk3 overlay scrollbars consistently show wrong behaviour
I use numix-grey. And that does not make any sense: any scrollbar width larger than zero pixels would cover content. That could cripple any application, including one that edits graphics etc. The fact that I could access a line of text because it is larger than common scrollbar widths does not right this wrong behaviour, Whatever the scrollbar width the calculations are off by exactly that size. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1516713 Title: gtk3 overlay scrollbars consistently show wrong behaviour Status in gedit package in Ubuntu: Incomplete Bug description: This is a general bug in GTK3 overlay scrolling (the new kind, not the old "overlay scrollbars" feature). When a window needs both horizontal and vertical scrolling the actual accessible content is reduced by the size of the scrollbars that show up when you move the mouse into the window. Normally the scrollbars are logically outside the scrollable area and that whole are can be scrolled into view. With overlay scrolling this is not the case because the scrollbars OVERLAY the scrollable content, effectively making part of that content unreachable. In case of a text-file opened in GEDIT this means that the last text- line will be covered by the horizontal scrollbar and you can not scroll further down to scroll it above the horizontal scroll bar (see the attached screenshot). The fix would obviously be to extend the logical scroll range of both scrollbars with the width of the other scrollbar if that exists. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: gedit 3.10.4-0ubuntu13 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Mon Nov 16 17:59:46 2015 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2015-11-04 (12 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1516713/+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 1516713] Re: gtk3 overlay scrollbars consistently show wrong behaviour
Sorry, I misread your comment and the part where you said "when not in use". They are visible when the mouse is over the content so they are always "in use" when I want to click the last line to put the cursor there (which will then not work of course because I can only click on the scroll bar). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1516713 Title: gtk3 overlay scrollbars consistently show wrong behaviour Status in gedit package in Ubuntu: Incomplete Bug description: This is a general bug in GTK3 overlay scrolling (the new kind, not the old "overlay scrollbars" feature). When a window needs both horizontal and vertical scrolling the actual accessible content is reduced by the size of the scrollbars that show up when you move the mouse into the window. Normally the scrollbars are logically outside the scrollable area and that whole are can be scrolled into view. With overlay scrolling this is not the case because the scrollbars OVERLAY the scrollable content, effectively making part of that content unreachable. In case of a text-file opened in GEDIT this means that the last text- line will be covered by the horizontal scrollbar and you can not scroll further down to scroll it above the horizontal scroll bar (see the attached screenshot). The fix would obviously be to extend the logical scroll range of both scrollbars with the width of the other scrollbar if that exists. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: gedit 3.10.4-0ubuntu13 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Mon Nov 16 17:59:46 2015 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2015-11-04 (12 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1516713/+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 1506704] Re: Thin font, nautilus doesn't integrate with Unity.
An additional remark about the garbled fonts in Eclipse: this happens when I scroll the package-explorer window. This might be a Java related thing since I can not reproduce the behavior outside Eclipse. -- 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/1506704 Title: Thin font, nautilus doesn't integrate with Unity. Status in nautilus package in Ubuntu: Confirmed Bug description: It happens frequently (around 1/2 of the time) that when I boot the computer, font lines are only one pixel thick. This concerns watch in the sys-tray, all item in the menu of all applications, as well as all fonts in Nautilus. When this happens. Nautilus doesn't display menu in the Unity menu bar, but displays an additional button showing three horizontal lines for bringing up the menu. This problem has been with me for years, although sometimes disappears for months at a time when I run sudo apt-get update. This time it re- emerged after upgrading to 15.10 beta (Wily). It happens usually on power-up, and disappears after system restart. (To appear again on the next power-up). ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: nautilus 1:3.14.2-0ubuntu12 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Oct 16 04:53:31 2015 GsettingsChanges: InstallationDate: Installed on 2015-10-08 (7 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1506704/+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 1506704] Re: Thin font, nautilus doesn't integrate with Unity.
I need to correct what I said above. Turning of hinting DOES improve things a lot but it does not work immediately. I did have to restart the system after disabling hinting which made me believe earlier that it did nothing (and then I kept restoring the setting to ON/FULL). Fonts still look wrong in parts of my Eclipse IDE but that varies with the Eclipse window (package explorer is bad, source editor is good) and some web pages in Chromium show ugly fonts. Overall my desktop looks OK now. -- 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/1506704 Title: Thin font, nautilus doesn't integrate with Unity. Status in nautilus package in Ubuntu: Confirmed Bug description: It happens frequently (around 1/2 of the time) that when I boot the computer, font lines are only one pixel thick. This concerns watch in the sys-tray, all item in the menu of all applications, as well as all fonts in Nautilus. When this happens. Nautilus doesn't display menu in the Unity menu bar, but displays an additional button showing three horizontal lines for bringing up the menu. This problem has been with me for years, although sometimes disappears for months at a time when I run sudo apt-get update. This time it re- emerged after upgrading to 15.10 beta (Wily). It happens usually on power-up, and disappears after system restart. (To appear again on the next power-up). ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: nautilus 1:3.14.2-0ubuntu12 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Oct 16 04:53:31 2015 GsettingsChanges: InstallationDate: Installed on 2015-10-08 (7 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1506704/+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 1506704] Re: Thin font, nautilus doesn't integrate with Unity.
I also experience strange font rendering after reinstalling 15.10. I have already been on the development version for months and until yesterday everything looked fine. Yesterday I did a download of the 15.10 release and reinstalled. Everything worked out of the box, even my installed packages, EXCEPT msttcorefonts. I had to explicitly install the ttf-mscorefonts-installer to get fonts like Arial, Courier and Verdana. But all fonts (not only the ms-ones) are rendered very weird in most if not all places. The look very thin (most fonts are probably one pixels wide) and I really have to go to bold versions to see thicker fonts. Even then, the fonts look garbled. Changing antialiasing and/or hinting settings has very little influence, if any. It brings back nightmares of the ugly font rendering I am used to in the Windows I have running in a VirtualBox. -- 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/1506704 Title: Thin font, nautilus doesn't integrate with Unity. Status in nautilus package in Ubuntu: Confirmed Bug description: It happens frequently (around 1/2 of the time) that when I boot the computer, font lines are only one pixel thick. This concerns watch in the sys-tray, all item in the menu of all applications, as well as all fonts in Nautilus. When this happens. Nautilus doesn't display menu in the Unity menu bar, but displays an additional button showing three horizontal lines for bringing up the menu. This problem has been with me for years, although sometimes disappears for months at a time when I run sudo apt-get update. This time it re- emerged after upgrading to 15.10 beta (Wily). It happens usually on power-up, and disappears after system restart. (To appear again on the next power-up). ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: nautilus 1:3.14.2-0ubuntu12 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Oct 16 04:53:31 2015 GsettingsChanges: InstallationDate: Installed on 2015-10-08 (7 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1506704/+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 1411324] [NEW] package nvidia-331 331.113-0ubuntu0.1 failed to install/upgrade: Unterprozess installiertes post-removal-Skript gab den Fehlerwert 8 zurück
Public bug reported: Just did apt-get upgrade to apply the updates ProblemType: Package DistroRelease: Ubuntu 14.10 Package: nvidia-331 331.113-0ubuntu0.1 ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2 Uname: Linux 3.16.0-29-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 AptOrdering: nvidia-331-uvm: Purge nvidia-331: Purge nvidia-opencl-icd-331: Purge nvidia-prime: Purge nvidia-settings: Purge Architecture: amd64 Date: Thu Jan 15 17:54:54 2015 DuplicateSignature: package:nvidia-331:331.113-0ubuntu0.1:Unterprozess installiertes post-removal-Skript gab den Fehlerwert 8 zurück ErrorMessage: Unterprozess installiertes post-removal-Skript gab den Fehlerwert 8 zurück InstallationDate: Installed on 2014-11-22 (54 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: nvidia-graphics-drivers-331 Title: package nvidia-331 331.113-0ubuntu0.1 failed to install/upgrade: Unterprozess installiertes post-removal-Skript gab den Fehlerwert 8 zurück UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.nvidia.331.hybrid.conf: [deleted] ** Affects: nvidia-graphics-drivers-331 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package utopic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1411324 Title: package nvidia-331 331.113-0ubuntu0.1 failed to install/upgrade: Unterprozess installiertes post-removal-Skript gab den Fehlerwert 8 zurück Status in nvidia-graphics-drivers-331 package in Ubuntu: New Bug description: Just did apt-get upgrade to apply the updates ProblemType: Package DistroRelease: Ubuntu 14.10 Package: nvidia-331 331.113-0ubuntu0.1 ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2 Uname: Linux 3.16.0-29-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 AptOrdering: nvidia-331-uvm: Purge nvidia-331: Purge nvidia-opencl-icd-331: Purge nvidia-prime: Purge nvidia-settings: Purge Architecture: amd64 Date: Thu Jan 15 17:54:54 2015 DuplicateSignature: package:nvidia-331:331.113-0ubuntu0.1:Unterprozess installiertes post-removal-Skript gab den Fehlerwert 8 zurück ErrorMessage: Unterprozess installiertes post-removal-Skript gab den Fehlerwert 8 zurück InstallationDate: Installed on 2014-11-22 (54 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: nvidia-graphics-drivers-331 Title: package nvidia-331 331.113-0ubuntu0.1 failed to install/upgrade: Unterprozess installiertes post-removal-Skript gab den Fehlerwert 8 zurück UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.nvidia.331.hybrid.conf: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1411324/+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 1403127] Re: Kubuntu 14.10: after 12 Dec update X doesn't start
Seems related to nvidia driver. From dmesg: [4.854459] Bridge firewalling registered [5.046794] init: nvidia-prime main process (1507) terminated with status 127 [5.413350] systemd-logind[947]: Failed to start unit user@111.service: Unknown unit: user@111.service [5.413355] systemd-logind[947]: Failed to start user service: Unknown unit: user@111.service [5.416467] systemd-logind[947]: New session c1 of user lightdm. [5.416480] systemd-logind[947]: Linked /tmp/.X11-unix/X0 to /run/user/111/X11-display. reinstalling nvidia drivers do not make any difference What can I try? -- 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/1403127 Title: Kubuntu 14.10: after 12 Dec update X doesn't start Status in xorg package in Ubuntu: New Bug description: After the update of 12 December 2014 the x window system doesn't start anymore. The problem is an incorrect /etc/X11/xorg.conf file As a workaround, at every boot I have to do these commands: sudo rm /etc/X11/xorg.conf sudo startx Evironment: Kubuntu 14.10 64bit Laptop with nvidia card ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xserver-xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: KDE Date: Tue Dec 16 17:09:08 2014 InstallationDate: Installed on 2014-11-24 (21 days ago) InstallationMedia: Kubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1403127/+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 1403127] Re: Kubuntu 14.10: after 12 Dec update X doesn't start
SOLVED The nvidia drivers doensn't recognize the nvidia chipset NVIDIA GeForce GTX 970M My laptop is a Santech C37 To solve: 1) uninstall every nvidia driver 2) reboot 3)reinstall nouveau 4) reboot -- 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/1403127 Title: Kubuntu 14.10: after 12 Dec update X doesn't start Status in xorg package in Ubuntu: New Bug description: After the update of 12 December 2014 the x window system doesn't start anymore. The problem is an incorrect /etc/X11/xorg.conf file As a workaround, at every boot I have to do these commands: sudo rm /etc/X11/xorg.conf sudo startx Evironment: Kubuntu 14.10 64bit Laptop with nvidia card ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xserver-xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: KDE Date: Tue Dec 16 17:09:08 2014 InstallationDate: Installed on 2014-11-24 (21 days ago) InstallationMedia: Kubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1403127/+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 1403127] Re: Kubuntu 14.10: after 12 Dec update X doesn't start
Seems related to nvidia driver. From dmesg: [4.854459] Bridge firewalling registered [5.046794] init: nvidia-prime main process (1507) terminated with status 127 [5.413350] systemd-logind[947]: Failed to start unit user@111.service: Unknown unit: user@111.service [5.413355] systemd-logind[947]: Failed to start user service: Unknown unit: user@111.service [5.416467] systemd-logind[947]: New session c1 of user lightdm. [5.416480] systemd-logind[947]: Linked /tmp/.X11-unix/X0 to /run/user/111/X11-display. reinstalling nvidia drivers do not make any difference What can I try? -- 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/1403127 Title: Kubuntu 14.10: after 12 Dec update X doesn't start Status in xorg package in Ubuntu: New Bug description: After the update of 12 December 2014 the x window system doesn't start anymore. The problem is an incorrect /etc/X11/xorg.conf file As a workaround, at every boot I have to do these commands: sudo rm /etc/X11/xorg.conf sudo startx Evironment: Kubuntu 14.10 64bit Laptop with nvidia card ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xserver-xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: KDE Date: Tue Dec 16 17:09:08 2014 InstallationDate: Installed on 2014-11-24 (21 days ago) InstallationMedia: Kubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1403127/+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 1403127] [NEW] Kubuntu 14.10: after 12 Dec update X doesn't start
Public bug reported: After the update of 12 December 2014 the x window system doesn't start anymore. The problem is an incorrect /etc/X11/xorg.conf file As a workaround, at every boot I have to do these commands: sudo rm /etc/X11/xorg.conf sudo startx Evironment: Kubuntu 14.10 64bit Laptop with nvidia card ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xserver-xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: KDE Date: Tue Dec 16 17:09:08 2014 InstallationDate: Installed on 2014-11-24 (21 days ago) InstallationMedia: Kubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug utopic -- 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/1403127 Title: Kubuntu 14.10: after 12 Dec update X doesn't start Status in xorg package in Ubuntu: New Bug description: After the update of 12 December 2014 the x window system doesn't start anymore. The problem is an incorrect /etc/X11/xorg.conf file As a workaround, at every boot I have to do these commands: sudo rm /etc/X11/xorg.conf sudo startx Evironment: Kubuntu 14.10 64bit Laptop with nvidia card ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xserver-xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: KDE Date: Tue Dec 16 17:09:08 2014 InstallationDate: Installed on 2014-11-24 (21 days ago) InstallationMedia: Kubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1403127/+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 1403127] Re: Kubuntu 14.10: after 12 Dec update X doesn't start
** Attachment added: The X log https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1403127/+attachment/4282221/+files/Xorg.0.log -- 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/1403127 Title: Kubuntu 14.10: after 12 Dec update X doesn't start Status in xorg package in Ubuntu: New Bug description: After the update of 12 December 2014 the x window system doesn't start anymore. The problem is an incorrect /etc/X11/xorg.conf file As a workaround, at every boot I have to do these commands: sudo rm /etc/X11/xorg.conf sudo startx Evironment: Kubuntu 14.10 64bit Laptop with nvidia card ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xserver-xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: KDE Date: Tue Dec 16 17:09:08 2014 InstallationDate: Installed on 2014-11-24 (21 days ago) InstallationMedia: Kubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1403127/+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 1403127] Re: Kubuntu 14.10: after 12 Dec update X doesn't start
This invalid xorg.conf file is recreated at every boot ** Attachment added: The invalid xorg.conf https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1403127/+attachment/4282236/+files/xorg.conf.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/1403127 Title: Kubuntu 14.10: after 12 Dec update X doesn't start Status in xorg package in Ubuntu: New Bug description: After the update of 12 December 2014 the x window system doesn't start anymore. The problem is an incorrect /etc/X11/xorg.conf file As a workaround, at every boot I have to do these commands: sudo rm /etc/X11/xorg.conf sudo startx Evironment: Kubuntu 14.10 64bit Laptop with nvidia card ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xserver-xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: KDE Date: Tue Dec 16 17:09:08 2014 InstallationDate: Installed on 2014-11-24 (21 days ago) InstallationMedia: Kubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1403127/+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 1402149] Re: After update lightdm doesn't start
Found an error in Xorg.0.log: --- [28.605] (==) Log file: /var/log/Xorg.0.log, Time: Sat Dec 13 17:09:02 2014 [28.605] (==) Using config file: /etc/X11/xorg.conf [28.605] (==) Using system config directory /usr/share/X11/xorg.conf.d [28.605] Data incomplete in file /etc/X11/xorg.conf Undefined Screen nvidia referenced by ServerLayout layout. [28.605] (EE) Problem parsing the config file [28.605] (EE) Error parsing the config file [28.605] (EE) Fatal server error: [28.605] (EE) no screens found(EE) [28.605] (EE) --- The xorg.conf file contains: --- Section ServerLayout Identifier layout Screen 0 nvidia Inactive intel EndSection Section Device Identifier intel Driver intel BusID PCI:0@0:2:0 Option AccelMethod SNA EndSection Section Screen Identifier intel Device intel EndSection --- The last 2 automatically saved xorg.conf files have the same content -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1402149 Title: After update lightdm doesn't start Status in lightdm package in Ubuntu: New Bug description: Updateted 14 Dec 2014 Kubuntu 14.10 64Bit After reboot there is no gui. From dmesg I see an error in ligthdm This is the error reported: [ 16.777309] init: lightdm main process (2534) terminated with status 1 [ 16.777317] init: lightdm main process ended, respawning [ 22.866231] init: lightdm main process (2642) terminated with status 1 [ 22.866239] init: lightdm main process ended, respawning [ 23.742651] systemd-logind[981]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 23.742688] systemd-logind[981]: Failed to start user service: Unknown unit: user@1000.service [ 23.745586] systemd-logind[981]: New session c1 of user mirto. [ 28.947789] init: lightdm main process (2895) terminated with status 1 [ 28.947797] init: lightdm respawning too fast, stopped [ 28.951276] init: plymouth-ready (startup) main process (264) terminated with status 1 [ 33.762569] audit_printk_skb: 57 callbacks suppressed Trier another update this morning but nothing chenged ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: lightdm 1.12.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 Date: Sat Dec 13 07:50:08 2014 InstallationDate: Installed on 2014-11-24 (18 days ago) InstallationMedia: Kubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) LightdmGreeterLog: QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: File o directory non esistente QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus Bus::open: Can not get ibus-daemon's address. IBusInputContext::createInputContext: no connection to ibus-daemon LightdmGreeterLogOld: QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: File o directory non esistente QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus Bus::open: Can not get ibus-daemon's address. IBusInputContext::createInputContext: no connection to ibus-daemon ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1402149/+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 1402149] Re: After update lightdm doesn't start
ATTENTION: workaround found. The problem is an xorg.conf corrupted file created automatically. To use X you have to: 1) boot the system (you have only the command line) 2) remove the file /etc/X11/xorg.conf 3) issue the command sudo startx Noe the GUI works; but you have to do this everytime you reboot -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1402149 Title: After update lightdm doesn't start Status in lightdm package in Ubuntu: New Bug description: Updateted 14 Dec 2014 Kubuntu 14.10 64Bit After reboot there is no gui. From dmesg I see an error in ligthdm This is the error reported: [ 16.777309] init: lightdm main process (2534) terminated with status 1 [ 16.777317] init: lightdm main process ended, respawning [ 22.866231] init: lightdm main process (2642) terminated with status 1 [ 22.866239] init: lightdm main process ended, respawning [ 23.742651] systemd-logind[981]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 23.742688] systemd-logind[981]: Failed to start user service: Unknown unit: user@1000.service [ 23.745586] systemd-logind[981]: New session c1 of user mirto. [ 28.947789] init: lightdm main process (2895) terminated with status 1 [ 28.947797] init: lightdm respawning too fast, stopped [ 28.951276] init: plymouth-ready (startup) main process (264) terminated with status 1 [ 33.762569] audit_printk_skb: 57 callbacks suppressed Trier another update this morning but nothing chenged ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: lightdm 1.12.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 Date: Sat Dec 13 07:50:08 2014 InstallationDate: Installed on 2014-11-24 (18 days ago) InstallationMedia: Kubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) LightdmGreeterLog: QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: File o directory non esistente QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus Bus::open: Can not get ibus-daemon's address. IBusInputContext::createInputContext: no connection to ibus-daemon LightdmGreeterLogOld: QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: File o directory non esistente QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus Bus::open: Can not get ibus-daemon's address. IBusInputContext::createInputContext: no connection to ibus-daemon ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1402149/+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 1402149] [NEW] After update lightdm doesn't start
Public bug reported: Updateted 14 Dec 2014 Kubuntu 14.10 64Bit After reboot there is no gui. From dmesg I see an error in ligthdm This is the error reported: [ 16.777309] init: lightdm main process (2534) terminated with status 1 [ 16.777317] init: lightdm main process ended, respawning [ 22.866231] init: lightdm main process (2642) terminated with status 1 [ 22.866239] init: lightdm main process ended, respawning [ 23.742651] systemd-logind[981]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 23.742688] systemd-logind[981]: Failed to start user service: Unknown unit: user@1000.service [ 23.745586] systemd-logind[981]: New session c1 of user mirto. [ 28.947789] init: lightdm main process (2895) terminated with status 1 [ 28.947797] init: lightdm respawning too fast, stopped [ 28.951276] init: plymouth-ready (startup) main process (264) terminated with status 1 [ 33.762569] audit_printk_skb: 57 callbacks suppressed Trier another update this morning but nothing chenged ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: lightdm 1.12.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 Date: Sat Dec 13 07:50:08 2014 InstallationDate: Installed on 2014-11-24 (18 days ago) InstallationMedia: Kubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) LightdmGreeterLog: QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: File o directory non esistente QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus Bus::open: Can not get ibus-daemon's address. IBusInputContext::createInputContext: no connection to ibus-daemon LightdmGreeterLogOld: QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: File o directory non esistente QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus Bus::open: Can not get ibus-daemon's address. IBusInputContext::createInputContext: no connection to ibus-daemon ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug package-from-proposed utopic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1402149 Title: After update lightdm doesn't start Status in lightdm package in Ubuntu: New Bug description: Updateted 14 Dec 2014 Kubuntu 14.10 64Bit After reboot there is no gui. From dmesg I see an error in ligthdm This is the error reported: [ 16.777309] init: lightdm main process (2534) terminated with status 1 [ 16.777317] init: lightdm main process ended, respawning [ 22.866231] init: lightdm main process (2642) terminated with status 1 [ 22.866239] init: lightdm main process ended, respawning [ 23.742651] systemd-logind[981]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 23.742688] systemd-logind[981]: Failed to start user service: Unknown unit: user@1000.service [ 23.745586] systemd-logind[981]: New session c1 of user mirto. [ 28.947789] init: lightdm main process (2895) terminated with status 1 [ 28.947797] init: lightdm respawning too fast, stopped [ 28.951276] init: plymouth-ready (startup) main process (264) terminated with status 1 [ 33.762569] audit_printk_skb: 57 callbacks suppressed Trier another update this morning but nothing chenged ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: lightdm 1.12.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 Date: Sat Dec 13 07:50:08 2014 InstallationDate: Installed on 2014-11-24 (18 days ago) InstallationMedia: Kubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) LightdmGreeterLog: QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: File o directory non esistente QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus Bus::open: Can not get ibus-daemon's address. IBusInputContext::createInputContext: no connection to ibus-daemon LightdmGreeterLogOld: QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: File o directory non esistente QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus Bus::open: Can not get ibus-daemon's address. IBusInputContext::createInputContext: no connection to ibus-daemon ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage
[Desktop-packages] [Bug 1379926] Re: gedit crashed with signal 5 in _XReply()
*** This bug is a duplicate of bug 1379628 *** https://bugs.launchpad.net/bugs/1379628 Same here. Gedit is practically unworkable. When editing text files the mouse cursor often becomes invisible when moving it over the edit window and during editing it crashes at random moments. System is 14.10 fresh install. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1379926 Title: gedit crashed with signal 5 in _XReply() Status in “gedit” package in Ubuntu: Confirmed Bug description: I can't use gedit without it crashing!!! DOn't know why yet. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: gedit 3.10.4-0ubuntu6 ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4 Uname: Linux 3.16.0-21-generic x86_64 ApportVersion: 2.14.7-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Fri Oct 10 12:55:57 2014 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2014-09-28 (11 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140923) ProcCmdline: gedit /home/username/Desktop/my-site/hooks/install ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: gedit StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XIGetClientPointer () from /usr/lib/x86_64-linux-gnu/libXi.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gedit crashed with signal 5 in _XReply() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1379926/+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 1228352] Re: [regression] Alt-Tab for all viewports will not switch viewports when selecting a window on another viewport
I found the cause of the problem: besides my Unity plugin the Desktop Wall plugin had been disabled as well. Enabling it via CCSM (and ignoring some complaints about conflicting plugin settings involving something like Flip up/down or so) resolved the issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1228352 Title: [regression] Alt-Tab for all viewports will not switch viewports when selecting a window on another viewport Status in Compiz: Fix Committed Status in Compiz 0.9.10 series: Fix Committed Status in “compiz” package in Ubuntu: Fix Released Bug description: When enabling Alt-Tab for all viewports (instead of only Alt-Tabbing on the current one), if you select a window that is currently on a different viewport, that viewport will not be automatically switched to. This also occurs when using the Launcher to select apps in a different viewport. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1228352/+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 1228352] Re: [regression] Alt-Tab for all viewports will not switch viewports when selecting a window on another viewport
Hi, I have the same issue with Ubuntu 14.10. Something went wrong and I lost my Unity launcher and panel. I tried to restore them using 'dconf reset -f /org/compiz/' (read that somewhere) but that did not help. It turned out my Unity plugin was simply set to inactive so activating it via CCSM brought Unity back on my desktop. But now I have the same problem (the scale plugin is also affected since it will also not switch the active viewport) and I can not restore the correct behaviour. The launcher is my main viewport switcher but now I have to switch viewport manually which is a real pain. Any help would be greatly appreciated. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1228352 Title: [regression] Alt-Tab for all viewports will not switch viewports when selecting a window on another viewport Status in Compiz: Fix Committed Status in Compiz 0.9.10 series: Fix Committed Status in “compiz” package in Ubuntu: Fix Released Bug description: When enabling Alt-Tab for all viewports (instead of only Alt-Tabbing on the current one), if you select a window that is currently on a different viewport, that viewport will not be automatically switched to. This also occurs when using the Launcher to select apps in a different viewport. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1228352/+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 1369298] [NEW] launching firefox freezes kde
Public bug reported: Framework: a Kubuntu 14.04 64Bit Virtual machine hosted on a Kubuntu 14.04 64Bit PC Either updated minutes ago When Firefox is launched the GUI freezes. From an ssh session I can gather this from syslog Sep 14 19:29:25 vx04-test kernel: [ 162.597186] [ cut here ] Sep 14 19:29:25 vx04-test kernel: [ 162.597196] kernel BUG at /build/buildd/linux-3.13.0/drivers/gpu/drm/ttm/ttm_bo.c:172! Sep 14 19:29:25 vx04-test kernel: [ 162.597198] invalid opcode: [#1] SMP Sep 14 19:29:25 vx04-test kernel: [ 162.597201] Modules linked in: snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_page_alloc snd_seq_midi snd_seq_midi_event snd_rawmidi kvm_intel snd_seq snd_seq_device snd_timer kvm rfcomm bnep bluetooth snd serio_raw soundcore i2c_piix4 parport_pc ppdev lp mac_hid parport qxl ttm drm_kms_helper psmouse floppy drm Sep 14 19:29:25 vx04-test kernel: [ 162.597221] CPU: 1 PID: 1125 Comm: Xorg Not tainted 3.13.0-36-generic #63-Ubuntu Sep 14 19:29:25 vx04-test kernel: [ 162.597223] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011 Sep 14 19:29:25 vx04-test kernel: [ 162.597225] task: 880079873000 ti: 880079da2000 task.ti: 880079da2000 Sep 14 19:29:25 vx04-test kernel: [ 162.597227] RIP: 0010:[a004d181] [a004d181] ttm_bo_add_to_lru+0xe1/0xf0 [ttm] Sep 14 19:29:25 vx04-test kernel: [ 162.597247] RSP: 0018:880079da3ca8 EFLAGS: 00010287 Sep 14 19:29:25 vx04-test kernel: [ 162.597249] RAX: 88005ce020f8 RBX: 88005cc523c0 RCX: fffa Sep 14 19:29:25 vx04-test kernel: [ 162.597251] RDX: 8800362bb0e8 RSI: 0020 RDI: 88005ce02048 Sep 14 19:29:25 vx04-test kernel: [ 162.597252] RBP: 880079da3ce0 R08: 88003e40b630 R09: 88003e5d66a8 Sep 14 19:29:25 vx04-test kernel: [ 162.597254] R10: a00c8734 R11: R12: 88005cc52b80 Sep 14 19:29:25 vx04-test kernel: [ 162.597255] R13: 88005cc52ba8 R14: 88005ce02048 R15: 8800362bb548 Sep 14 19:29:25 vx04-test kernel: [ 162.597257] FS: 7fd68baf09c0() GS:88007fd0() knlGS: Sep 14 19:29:25 vx04-test kernel: [ 162.597259] CS: 0010 DS: ES: CR0: 8005003b Sep 14 19:29:25 vx04-test kernel: [ 162.597261] CR2: 7f9b480c7000 CR3: 7a34f000 CR4: 06e0 Sep 14 19:29:25 vx04-test kernel: [ 162.597269] Stack: Sep 14 19:29:25 vx04-test kernel: [ 162.597271] a00c8d11 880035e3ff80 880079da3d70 0004 Sep 14 19:29:25 vx04-test kernel: [ 162.597274] 880035cfe480 8800362bb000 880079da3d60 Sep 14 19:29:25 vx04-test kernel: [ 162.597277] a00c8207 88005ce02000 880003ed 880035cfe4f8 Sep 14 19:29:25 vx04-test kernel: [ 162.597280] Call Trace: Sep 14 19:29:25 vx04-test kernel: [ 162.597291] [a00c8d11] ? qxl_release_fence_buffer_objects+0x81/0xe0 [qxl] Sep 14 19:29:25 vx04-test kernel: [ 162.597297] [a00c8207] qxl_process_single_command+0x637/0x750 [qxl] Sep 14 19:29:25 vx04-test kernel: [ 162.597303] [a00c835f] qxl_execbuffer_ioctl+0x3f/0x90 [qxl] Sep 14 19:29:25 vx04-test kernel: [ 162.597367] [a0003c22] drm_ioctl+0x502/0x630 [drm] Sep 14 19:29:25 vx04-test kernel: [ 162.597377] [81180a0e] ? do_mmap_pgoff+0x34e/0x3d0 Sep 14 19:29:25 vx04-test kernel: [ 162.597383] [811d0390] do_vfs_ioctl+0x2e0/0x4c0 Sep 14 19:29:25 vx04-test kernel: [ 162.597386] [811d05f1] SyS_ioctl+0x81/0xa0 Sep 14 19:29:25 vx04-test kernel: [ 162.597391] [8172efad] system_call_fastpath+0x1a/0x1f Sep 14 19:29:25 vx04-test kernel: [ 162.597392] Code: c1 47 34 83 c0 01 83 f8 01 7e 03 c9 f3 c3 e8 7b 89 00 00 c9 66 0f 1f 44 00 00 eb f0 48 89 7d f8 e8 69 89 00 00 48 8b 7d f8 eb 95 0f 0b 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 Sep 14 19:29:25 vx04-test kernel: [ 162.597418] RIP [a004d181] ttm_bo_add_to_lru+0xe1/0xf0 [ttm] Sep 14 19:29:25 vx04-test kernel: [ 162.597423] RSP 880079da3ca8 Sep 14 19:29:25 vx04-test kernel: [ 162.597427] ---[ end trace 419bfa3345a08080 ]--- What can I do? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: firefox 32.0+build1-0ubuntu0.14.04.1 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sysop 1731 F pulseaudio sysop 1820 F pulseaudio BuildID: 20140830210550 Channel: Unavailable Date: Sun Sep 14 19:46:55 2014 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2014-09-13 (1 days ago) InstallationMedia: Kubuntu
[Desktop-packages] [Bug 1351480] Re: Compiz in utopic is older than in Trusty-updates
Actually a new error occurs (broken packages) when installing this via aptitude update: Errors were encountered while processing: /var/cache/apt/archives/compiz-plugins_1%3a0.9.12+14.10.20140812-0ubuntu1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Failed to perform requested operation on package. Trying to recover: dpkg: dependency problems prevent configuration of metacity: metacity depends on libmetacity-private1 (= 1:3.12.0-1ubuntu1); however: Package libmetacity-private1 is not installed. metacity depends on metacity-common (= 1:3.12.0-1ubuntu1); however: Version of metacity-common on system is 1:2.34.13-0ubuntu4. dpkg: error processing package metacity (--configure): dependency problems - leaving unconfigured -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1351480 Title: Compiz in utopic is older than in Trusty-updates Status in “compiz” package in Ubuntu: Fix Released Bug description: When 1 installs Metacity-common file from upgrade in Ubuntu 14.10 it wants to Remove Unity and compiz. when 1 does so it removes the whole desktop and not able to run the desktop properly task bars and tool bar is removed and only shows wall paper area. when 1 removes Metacity-common, and attempts to install unity and compiz back it wont let you and says has held broken packages in the process --- ApportVersion: 2.14.5-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: darkangel 1777 F pulseaudio /dev/snd/controlC0: darkangel 1777 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=569c56dd-f25c-4a2d-bd00-ca52486d4cea InstallationDate: Installed on 2014-08-01 (0 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140731) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: eMachines EL1360G Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-6-generic root=UUID=4288519c-1dca-4080-92dd-ecb76fb750e3 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 RelatedPackageVersions: linux-restricted-modules-3.16.0-6-generic N/A linux-backports-modules-3.16.0-6-generic N/A linux-firmware1.132 RfKill: Tags: utopic Uname: Linux 3.16.0-6-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/16/2011 dmi.bios.vendor: AMI dmi.bios.version: P01-C1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: EL1360G dmi.board.vendor: eMachines dmi.chassis.type: 3 dmi.chassis.vendor: eMachines dmi.modalias: dmi:bvnAMI:bvrP01-C1:bd11/16/2011:svneMachines:pnEL1360G:pvr:rvneMachines:rnEL1360G:rvr:cvneMachines:ct3:cvr: dmi.product.name: EL1360G dmi.sys.vendor: eMachines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1351480/+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 1351480] Re: Compiz in utopic is older than in Trusty-updates
I managed to resolve this with aptitude dist-upgrade by rejecting its first solution (removing metacity etc) and accepting the second one which removed among other things libmetacity-private0 and installed libmetacity-private1. Apparently this was a result of earlier partial updates. I can now confirm that updates succeed without errors. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1351480 Title: Compiz in utopic is older than in Trusty-updates Status in “compiz” package in Ubuntu: Fix Released Bug description: When 1 installs Metacity-common file from upgrade in Ubuntu 14.10 it wants to Remove Unity and compiz. when 1 does so it removes the whole desktop and not able to run the desktop properly task bars and tool bar is removed and only shows wall paper area. when 1 removes Metacity-common, and attempts to install unity and compiz back it wont let you and says has held broken packages in the process --- ApportVersion: 2.14.5-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: darkangel 1777 F pulseaudio /dev/snd/controlC0: darkangel 1777 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=569c56dd-f25c-4a2d-bd00-ca52486d4cea InstallationDate: Installed on 2014-08-01 (0 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140731) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: eMachines EL1360G Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-6-generic root=UUID=4288519c-1dca-4080-92dd-ecb76fb750e3 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 RelatedPackageVersions: linux-restricted-modules-3.16.0-6-generic N/A linux-backports-modules-3.16.0-6-generic N/A linux-firmware1.132 RfKill: Tags: utopic Uname: Linux 3.16.0-6-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/16/2011 dmi.bios.vendor: AMI dmi.bios.version: P01-C1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: EL1360G dmi.board.vendor: eMachines dmi.chassis.type: 3 dmi.chassis.vendor: eMachines dmi.modalias: dmi:bvnAMI:bvrP01-C1:bd11/16/2011:svneMachines:pnEL1360G:pvr:rvneMachines:rnEL1360G:rvr:cvneMachines:ct3:cvr: dmi.product.name: EL1360G dmi.sys.vendor: eMachines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1351480/+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 1351480] Re: Metacity-common Critical issue
** Changed in: metacity (Ubuntu) Status: Incomplete = Confirmed -- 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/1351480 Title: Metacity-common Critical issue Status in “metacity” package in Ubuntu: Confirmed Bug description: When 1 installs Metacity-common file from upgrade in Ubuntu 14.10 it wants to Remove Unity and compiz. when 1 does so it removes the whole desktop and not able to run the desktop properly task bars and tool bar is removed and only shows wall paper area. when 1 removes Metacity-common, and attempts to install unity and compiz back it wont let you and says has held broken packages in the process --- ApportVersion: 2.14.5-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: darkangel 1777 F pulseaudio /dev/snd/controlC0: darkangel 1777 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=569c56dd-f25c-4a2d-bd00-ca52486d4cea InstallationDate: Installed on 2014-08-01 (0 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140731) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: eMachines EL1360G Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-6-generic root=UUID=4288519c-1dca-4080-92dd-ecb76fb750e3 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 RelatedPackageVersions: linux-restricted-modules-3.16.0-6-generic N/A linux-backports-modules-3.16.0-6-generic N/A linux-firmware1.132 RfKill: Tags: utopic Uname: Linux 3.16.0-6-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/16/2011 dmi.bios.vendor: AMI dmi.bios.version: P01-C1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: EL1360G dmi.board.vendor: eMachines dmi.chassis.type: 3 dmi.chassis.vendor: eMachines dmi.modalias: dmi:bvnAMI:bvrP01-C1:bd11/16/2011:svneMachines:pnEL1360G:pvr:rvneMachines:rnEL1360G:rvr:cvneMachines:ct3:cvr: dmi.product.name: EL1360G dmi.sys.vendor: eMachines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1351480/+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 1351480] Re: Metacity-common Critical issue
I can confirm this bug. I upgraded to 14.10 about three weeks ago and the Software Updater has been complaining about not being able to install al updates for about a week now. I use aptitude upgrade to do the partial update but a aptitude dist-upgrade says it will remove compiz, unity and a lot of other ciritcal stuff. The cause seems to be in a metacity-common package version conflict. Please resolve this issue. -- 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/1351480 Title: Metacity-common Critical issue Status in “metacity” package in Ubuntu: Incomplete Bug description: When 1 installs Metacity-common file from upgrade in Ubuntu 14.10 it wants to Remove Unity and compiz. when 1 does so it removes the whole desktop and not able to run the desktop properly task bars and tool bar is removed and only shows wall paper area. when 1 removes Metacity-common, and attempts to install unity and compiz back it wont let you and says has held broken packages in the process --- ApportVersion: 2.14.5-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: darkangel 1777 F pulseaudio /dev/snd/controlC0: darkangel 1777 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=569c56dd-f25c-4a2d-bd00-ca52486d4cea InstallationDate: Installed on 2014-08-01 (0 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140731) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: eMachines EL1360G Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-6-generic root=UUID=4288519c-1dca-4080-92dd-ecb76fb750e3 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 RelatedPackageVersions: linux-restricted-modules-3.16.0-6-generic N/A linux-backports-modules-3.16.0-6-generic N/A linux-firmware1.132 RfKill: Tags: utopic Uname: Linux 3.16.0-6-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/16/2011 dmi.bios.vendor: AMI dmi.bios.version: P01-C1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: EL1360G dmi.board.vendor: eMachines dmi.chassis.type: 3 dmi.chassis.vendor: eMachines dmi.modalias: dmi:bvnAMI:bvrP01-C1:bd11/16/2011:svneMachines:pnEL1360G:pvr:rvneMachines:rnEL1360G:rvr:cvneMachines:ct3:cvr: dmi.product.name: EL1360G dmi.sys.vendor: eMachines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1351480/+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 1266738] Re: Bluetooth headphone pairing works, but no audio output - Mako #116
I'm unable to pair from the command line. -- 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/1266738 Title: Bluetooth headphone pairing works, but no audio output - Mako #116 Status in “pulseaudio” package in Ubuntu: Confirmed Bug description: Running Ubuntu Touch image #116 on Mako. I got a pair of bluetooth headphones for xmas, so I haven't tested this before today. Pairing works, I can see the headphones in the bluetooth applet. Playing music no longer works once paired, the music app appears to freeze and the music timeline doesn't move, no audio output. Making and receiving calls is broken once a headset is paired with the phone. Incoming calls drop to answerphone. Outgoing calls never complete. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu7 Uname: Linux 3.4.0-3-mako armv7l AlsaInfo: This script requires lspci. Please install it, and re-run this script. ApportVersion: 2.12.7-0ubuntu3 Architecture: armhf AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CurrentDmesg: dmesg: klogctl failed: Operation not permitted Date: Tue Jan 7 11:36:05 2014 InstallationDate: Installed on 2014-01-07 (0 days ago) InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20140107) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR=set SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1266738/+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 418242] Re: Incorrect call to output plugins (with persistent error message) on copy
The problem occur also in Manjaro 0.8.6 Xfce with inkscape 0.48.4 r9939 when Clipman 1.2.3 is activate. Closing clipma, all work correctly. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/418242 Title: Incorrect call to output plugins (with persistent error message) on copy Status in Inkscape: A Vector Drawing Tool: Triaged Status in “inkscape” package in Ubuntu: Triaged Status in “inkscape” package in Debian: Confirmed Status in Gentoo Linux: Unknown Bug description: UPDATE: After further investigation it turned out to be a problem related to the copy operation, in combination with a totally unrelated running Java program (FreeRapid). Reading some followups and other bug reports, it seems to be caused by the new clipboard management system (introduced as a fix for the bug #170185), as reported in bug #421597 So far these applications are known to randomly trigger an input/output extension (on linux): - FreeRapid Downloader - jDownloader - xfce4-clipman-plugin 1.1.3 - Netbeans - xfce4-settings-helper (Xfce 4.8) - The original report was this: I'm getting this error when I try to edit a text object created previously with a font that's not available in this system. It looks like Inkscape has problems to resolve the font substitution and displays the error message in a popup window that keeps appearing again and again, leaving no other remedy than closing inkscape and reopening it. The error message is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/418242/+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 1173843] [NEW] Kubuntu 13.04 power off doesn't work
Public bug reported: When requesting a shutdown with power off, the system huns and never power off. Last messages on consome are that / filesystem is busy then apear * Will now halt but never power off Machine: Hp Pavilion dv6 OS: kubuntu 13.04 amd64 (fresh install -using the entire disk) In dmesg I find some errors but I don't know if they are related: [ 15.929496] CPU 2 [ 15.929501] Pid: 586, comm: modprobe Tainted: PF O 3.8.0-19-generic #29-Ubuntu Hewlett-Packard HP Pavilion dv6 NoteBook PC /3659 [ 15.929511] RIP: 0010:[a08c4820] [a08c4820] patch_generic_hdmi+0xe0/0x550 [snd_hda_codec_hdmi] [ 15.929521] RSP: 0018:88022de01ac0 EFLAGS: 00010283 [ 15.929526] RAX: 0008 RBX: 0004 RCX: 0004 [ 15.929532] RDX: 88023122ffd8 RSI: 88023122ffe0 RDI: 880232794c20 [ 15.929537] RBP: 88022de01af8 R08: 0001 R09: 0002 [ 15.929542] R10: R11: R12: 880232794800 [ 15.929547] R13: R14: 0004 R15: 88023123 [ 15.929553] FS: 7fb24440f740() GS:88023fc8() knlGS: [ 15.929559] CS: 0010 DS: ES: CR0: 8005003b [ 15.929564] CR2: 88023122ffe0 CR3: 00022e3e1000 CR4: 07e0 [ 15.929569] DR0: DR1: DR2: [ 15.929575] DR3: DR6: 0ff0 DR7: 0400 [ 15.929581] Process modprobe (pid: 586, threadinfo 88022de0, task 88022e20ae80) [ 15.929586] Stack: [ 15.929589] a08c0004 a08c6380 [ 15.929598] 880232794800 a08c8000 88022de01b58 [ 15.929606] a053f186 2d6164682d646e73 64692d6365646f63 303030656430313a [ 15.929615] Call Trace: [ 15.929629] [a053f186] snd_hda_codec_configure+0x146/0x440 [snd_hda_codec] [ 15.929640] [a04922f0] azx_probe_continue+0x3a0/0x4f0 [snd_hda_intel] [ 15.929934] [a04908b0] ? azx_attach_pcm_stream+0x1e0/0x1e0 [snd_hda_intel] [ 15.930359] [a0491cb0] ? azx_halt+0x30/0x30 [snd_hda_intel] [ 15.930911] [a04906d0] ? azx_pcm_trigger+0x580/0x580 [snd_hda_intel] [ 15.931459] [a0491810] ? azx_runtime_suspend+0x30/0x30 [snd_hda_intel] [ 15.932008] [a048e670] ? azx_pcm_free+0x50/0x50 [snd_hda_intel] [ 15.932557] [a049279a] azx_probe+0x35a/0x940 [snd_hda_intel] [ 15.933104] [8137b47b] local_pci_probe+0x4b/0x80 [ 15.933645] [8137b7a1] pci_device_probe+0x111/0x120 [ 15.934192] [814556c7] driver_probe_device+0x77/0x230 [ 15.934726] [8145592b] __driver_attach+0xab/0xb0 [ 15.935252] [81455880] ? driver_probe_device+0x230/0x230 [ 15.935785] [814539dd] bus_for_each_dev+0x5d/0xa0 [ 15.936319] [814551ce] driver_attach+0x1e/0x20 [ 15.936852] [81454da0] bus_add_driver+0x190/0x280 [ 15.937379] [a04a4000] ? 0xa04a3fff [ 15.937900] [81455ff7] driver_register+0x77/0x170 [ 15.938409] [a04a4000] ? 0xa04a3fff [ 15.938919] [8137a66c] __pci_register_driver+0x4c/0x50 [ 15.939419] [a04a401e] azx_driver_init+0x1e/0x1000 [snd_hda_intel] [ 15.939919] [8100215a] do_one_initcall+0x12a/0x180 [ 15.940413] [810bfec7] load_module+0x10c7/0x1520 [ 15.940876] [810bb830] ? unset_module_init_ro_nx+0x80/0x80 [ 15.941327] [810c03e5] sys_init_module+0xc5/0xf0 [ 15.941758] [816d379d] system_call_fastpath+0x1a/0x1f [ 15.942165] Code: 0f 1f 00 4d 8b bc 24 c0 00 00 00 25 00 e0 00 00 c1 e8 0c 83 c8 01 49 63 17 83 c0 01 83 f8 10 48 8d 14 92 49 8d 14 d7 48 8d 72 08 66 89 5a 08 c7 46 08 02 00 00 00 0f 86 5b 02 00 00 48 8d 4e 18 [ 15.943049] RIP [a08c4820] patch_generic_hdmi+0xe0/0x550 [snd_hda_codec_hdmi] ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Sun Apr 28 07:55:54 2013 InstallationDate: Installed on 2013-04-26 (2 days ago) InstallationMedia: Kubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True ProcEnviron: LANGUAGE=it:en TERM=xterm PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring ** Attachment added: dmesg https://bugs.launchpad.net/bugs/1173843/+attachment/3657034/+files/dmesg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu.
[Desktop-packages] [Bug 1173843] Re: Kubuntu 13.04 power off doesn't work
** Package changed: xorg (Ubuntu) = linux (Ubuntu) ** Description changed: - When requesting a shutdown with power off, the system huns and never power off. + When requesting a shutdown with power off, the system hungs and never power off. Last messages on consome are that / filesystem is busy then apear * Will now halt but never power off Machine: Hp Pavilion dv6 OS: kubuntu 13.04 amd64 (fresh install -using the entire disk) In dmesg I find some errors but I don't know if they are related: - [ 15.929496] CPU 2 + [ 15.929496] CPU 2 [ 15.929501] Pid: 586, comm: modprobe Tainted: PF O 3.8.0-19-generic #29-Ubuntu Hewlett-Packard HP Pavilion dv6 NoteBook PC /3659 [ 15.929511] RIP: 0010:[a08c4820] [a08c4820] patch_generic_hdmi+0xe0/0x550 [snd_hda_codec_hdmi] [ 15.929521] RSP: 0018:88022de01ac0 EFLAGS: 00010283 [ 15.929526] RAX: 0008 RBX: 0004 RCX: 0004 [ 15.929532] RDX: 88023122ffd8 RSI: 88023122ffe0 RDI: 880232794c20 [ 15.929537] RBP: 88022de01af8 R08: 0001 R09: 0002 [ 15.929542] R10: R11: R12: 880232794800 [ 15.929547] R13: R14: 0004 R15: 88023123 [ 15.929553] FS: 7fb24440f740() GS:88023fc8() knlGS: [ 15.929559] CS: 0010 DS: ES: CR0: 8005003b [ 15.929564] CR2: 88023122ffe0 CR3: 00022e3e1000 CR4: 07e0 [ 15.929569] DR0: DR1: DR2: [ 15.929575] DR3: DR6: 0ff0 DR7: 0400 [ 15.929581] Process modprobe (pid: 586, threadinfo 88022de0, task 88022e20ae80) [ 15.929586] Stack: [ 15.929589] a08c0004 a08c6380 [ 15.929598] 880232794800 a08c8000 88022de01b58 [ 15.929606] a053f186 2d6164682d646e73 64692d6365646f63 303030656430313a [ 15.929615] Call Trace: [ 15.929629] [a053f186] snd_hda_codec_configure+0x146/0x440 [snd_hda_codec] [ 15.929640] [a04922f0] azx_probe_continue+0x3a0/0x4f0 [snd_hda_intel] [ 15.929934] [a04908b0] ? azx_attach_pcm_stream+0x1e0/0x1e0 [snd_hda_intel] [ 15.930359] [a0491cb0] ? azx_halt+0x30/0x30 [snd_hda_intel] [ 15.930911] [a04906d0] ? azx_pcm_trigger+0x580/0x580 [snd_hda_intel] [ 15.931459] [a0491810] ? azx_runtime_suspend+0x30/0x30 [snd_hda_intel] [ 15.932008] [a048e670] ? azx_pcm_free+0x50/0x50 [snd_hda_intel] [ 15.932557] [a049279a] azx_probe+0x35a/0x940 [snd_hda_intel] [ 15.933104] [8137b47b] local_pci_probe+0x4b/0x80 [ 15.933645] [8137b7a1] pci_device_probe+0x111/0x120 [ 15.934192] [814556c7] driver_probe_device+0x77/0x230 [ 15.934726] [8145592b] __driver_attach+0xab/0xb0 [ 15.935252] [81455880] ? driver_probe_device+0x230/0x230 [ 15.935785] [814539dd] bus_for_each_dev+0x5d/0xa0 [ 15.936319] [814551ce] driver_attach+0x1e/0x20 [ 15.936852] [81454da0] bus_add_driver+0x190/0x280 [ 15.937379] [a04a4000] ? 0xa04a3fff [ 15.937900] [81455ff7] driver_register+0x77/0x170 [ 15.938409] [a04a4000] ? 0xa04a3fff [ 15.938919] [8137a66c] __pci_register_driver+0x4c/0x50 [ 15.939419] [a04a401e] azx_driver_init+0x1e/0x1000 [snd_hda_intel] [ 15.939919] [8100215a] do_one_initcall+0x12a/0x180 [ 15.940413] [810bfec7] load_module+0x10c7/0x1520 [ 15.940876] [810bb830] ? unset_module_init_ro_nx+0x80/0x80 [ 15.941327] [810c03e5] sys_init_module+0xc5/0xf0 [ 15.941758] [816d379d] system_call_fastpath+0x1a/0x1f - [ 15.942165] Code: 0f 1f 00 4d 8b bc 24 c0 00 00 00 25 00 e0 00 00 c1 e8 0c 83 c8 01 49 63 17 83 c0 01 83 f8 10 48 8d 14 92 49 8d 14 d7 48 8d 72 08 66 89 5a 08 c7 46 08 02 00 00 00 0f 86 5b 02 00 00 48 8d 4e 18 + [ 15.942165] Code: 0f 1f 00 4d 8b bc 24 c0 00 00 00 25 00 e0 00 00 c1 e8 0c 83 c8 01 49 63 17 83 c0 01 83 f8 10 48 8d 14 92 49 8d 14 d7 48 8d 72 08 66 89 5a 08 c7 46 08 02 00 00 00 0f 86 5b 02 00 00 48 8d 4e 18 [ 15.943049] RIP [a08c4820] patch_generic_hdmi+0xe0/0x550 [snd_hda_codec_hdmi] ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Sun Apr 28 07:55:54 2013 InstallationDate: Installed on 2013-04-26 (2 days ago) InstallationMedia: Kubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True ProcEnviron: - LANGUAGE=it:en -
Re: [Desktop-packages] [Bug 1133804] Re: Not completely finished scanning and then fails
May you have a very good day sir Michael Nagel, thank you very much for your quick response, I clarify that I have very vague notions regarding the management of the pc, you have much reason in this comment: site (Unfortunately this type of problems occur more often than they should, and although it might actually be a problem with Simple Scan, in our experience, most times not.) because I say?, i was looking in the ubuntu repositories and my surprise, clarified that if I was charged another scanner program, this would bring a conflict, then uninstall one of the programs and it worked perfectly, previously at another time I've used it with some previous conflicts, (devido the above) but started very well, and I managed to work perfectly with simple scan. I am very grateful and I learned more in this PC world. I send away right through the warm greetings and apologies if something is badly written degas the use of a translator, because I do not speak English, only Spanish. 2013/3/4 Michael Nagel ubu...@nailor.devzero.de: == Hi there, thank you for filing this bug and showing your interest in Simple Scan! This seems to be a Hardware Issue, i.e. Simple Scan does not support your scanner perfectly -- or possibly not at all. Unfortunately such problems happen more often then they should, and while it might indeed be a problem with Simple Scan, in our experience, most of the time it is not. This is why we prepared a check-list at [1] that will let you find out whether or not it really is a problem with Simple Scan and what your options are in either case. Please read that list and tell us how you decided to proceed. I will set this bug to Incomplete, so a friendly robot will expire this bug in 60 days if you do not respond. However, we would really prefer to hear back from you! Best Regards Michael [1] https://help.ubuntu.com/community/SimpleScanHardwareIssues == please check with xsane/scanimage -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1133804 Title: Not completely finished scanning and then fails Status in “simple-scan” package in Ubuntu: New Bug description: I have a scanner BENQ plane, another time I could not start the scanner, but then it worked, but this time, the process is that it starts scanning and stops in the middle of the process and stays there, producing that error pops ad I restarted the computer and the scanner several times and the problem persists. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: simple-scan 3.2.1-0ubuntu1~oneiric1 ProcVersionSignature: Ubuntu 3.0.0-30.47-generic 3.0.57 Uname: Linux 3.0.0-30-generic i686 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu4.1 Architecture: i386 Date: Tue Feb 26 21:54:09 2013 DriverPackageVersions: libsane 1.0.22-2ubuntu2 libsane-extras 1.0.22.2 hplip 3.11.7-1ubuntu3.1 hpoj N/A InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 002: ID 043d:0079 Lexmark International, Inc. InkJet Color Printer Bus 002 Device 013: ID 04a5:20fc Acer Peripherals Inc. (now BenQ Corp.) Benq 5000 MachineType: ECS M863 ProcEnviron: LANGUAGE=es_AR:es PATH=(custom, no user) LANG=es_AR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-30-generic root=UUID=a9a8d556-3d99-4561-a994-716786e22b3c ro recovery nomodeset SourcePackage: simple-scan UpgradeStatus: Upgraded to oneiric on 2012-12-19 (69 days ago) dmi.bios.date: 05/21/2004 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080010 dmi.board.name: M863 dmi.board.vendor: ECS dmi.board.version: 1.0 dmi.chassis.asset.tag: 0123ABC dmi.chassis.type: 3 dmi.chassis.vendor: ECS dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080010:bd05/21/2004:svnECS:pnM863:pvr1.0:rvnECS:rnM863:rvr1.0:cvnECS:ct3:cvr1.0: dmi.product.name: M863 dmi.product.version: 1.0 dmi.sys.vendor: ECS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1133804/+subscriptions -- SILVIO -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1133804 Title: Not completely finished scanning and then fails Status in “simple-scan” package in Ubuntu: New Bug description: I have a scanner BENQ plane, another time I could not start the scanner, but then it worked, but this time, the process
[Desktop-packages] [Bug 1133804] [NEW] Not completely finished scanning and then fails
Public bug reported: I have a scanner BENQ plane, another time I could not start the scanner, but then it worked, but this time, the process is that it starts scanning and stops in the middle of the process and stays there, producing that error pops ad I restarted the computer and the scanner several times and the problem persists. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: simple-scan 3.2.1-0ubuntu1~oneiric1 ProcVersionSignature: Ubuntu 3.0.0-30.47-generic 3.0.57 Uname: Linux 3.0.0-30-generic i686 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu4.1 Architecture: i386 Date: Tue Feb 26 21:54:09 2013 DriverPackageVersions: libsane 1.0.22-2ubuntu2 libsane-extras 1.0.22.2 hplip 3.11.7-1ubuntu3.1 hpoj N/A InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 002: ID 043d:0079 Lexmark International, Inc. InkJet Color Printer Bus 002 Device 013: ID 04a5:20fc Acer Peripherals Inc. (now BenQ Corp.) Benq 5000 MachineType: ECS M863 ProcEnviron: LANGUAGE=es_AR:es PATH=(custom, no user) LANG=es_AR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-30-generic root=UUID=a9a8d556-3d99-4561-a994-716786e22b3c ro recovery nomodeset SourcePackage: simple-scan UpgradeStatus: Upgraded to oneiric on 2012-12-19 (69 days ago) dmi.bios.date: 05/21/2004 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080010 dmi.board.name: M863 dmi.board.vendor: ECS dmi.board.version: 1.0 dmi.chassis.asset.tag: 0123ABC dmi.chassis.type: 3 dmi.chassis.vendor: ECS dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080010:bd05/21/2004:svnECS:pnM863:pvr1.0:rvnECS:rnM863:rvr1.0:cvnECS:ct3:cvr1.0: dmi.product.name: M863 dmi.product.version: 1.0 dmi.sys.vendor: ECS ** Affects: simple-scan (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug apport-lpi i386 oneiric running-unity -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1133804 Title: Not completely finished scanning and then fails Status in “simple-scan” package in Ubuntu: New Bug description: I have a scanner BENQ plane, another time I could not start the scanner, but then it worked, but this time, the process is that it starts scanning and stops in the middle of the process and stays there, producing that error pops ad I restarted the computer and the scanner several times and the problem persists. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: simple-scan 3.2.1-0ubuntu1~oneiric1 ProcVersionSignature: Ubuntu 3.0.0-30.47-generic 3.0.57 Uname: Linux 3.0.0-30-generic i686 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu4.1 Architecture: i386 Date: Tue Feb 26 21:54:09 2013 DriverPackageVersions: libsane 1.0.22-2ubuntu2 libsane-extras 1.0.22.2 hplip 3.11.7-1ubuntu3.1 hpoj N/A InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 002: ID 043d:0079 Lexmark International, Inc. InkJet Color Printer Bus 002 Device 013: ID 04a5:20fc Acer Peripherals Inc. (now BenQ Corp.) Benq 5000 MachineType: ECS M863 ProcEnviron: LANGUAGE=es_AR:es PATH=(custom, no user) LANG=es_AR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-30-generic root=UUID=a9a8d556-3d99-4561-a994-716786e22b3c ro recovery nomodeset SourcePackage: simple-scan UpgradeStatus: Upgraded to oneiric on 2012-12-19 (69 days ago) dmi.bios.date: 05/21/2004 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080010 dmi.board.name: M863 dmi.board.vendor: ECS dmi.board.version: 1.0 dmi.chassis.asset.tag: 0123ABC dmi.chassis.type: 3 dmi.chassis.vendor: ECS dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080010:bd05/21/2004:svnECS:pnM863:pvr1.0:rvnECS:rnM863:rvr1.0:cvnECS:ct3:cvr1.0: dmi.product.name: M863 dmi.product.version: 1.0 dmi.sys.vendor: ECS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1133804/+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
