[Desktop-packages] [Bug 1906792] Re: Chromium tabs freeze with two windows on Wayland (Xwayland)
I have the exact same issue as described by original report. Two windows of the browser on different workspaces, only happens when I use Wayland session. I collected more data on this: Release: Ubuntu Noble Numbat 24.04 and Ubuntu Mantic Minotaur 23.10 Hardware: Dell Inspiron-16-Plus-7620, i7-12700H, 32GB RAM. Browsers tested: Vivaldi (deb), Brave (deb), Brave (snap), Chromium (snap) As suggested by @vanvugt , I switched one browser setting, and it immediately solved the issue for me on all browsers affected. chrome://flags/#ozone-platform-hint Changed from default (always use x11), to auto (try wayland first, fallback to x11). It is quite easy to check that the setting is applied, by running this on the browser: chrome://gpu/ Searching the text for "ozone" I can see the following: --ozone-platform-hint=auto --ozone-platform=wayland I hope this helps. Please let me know if further testing is required. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/1906792 Title: Chromium tabs freeze with two windows on Wayland (Xwayland) Status in Mutter: New Status in mutter package in Ubuntu: Confirmed Status in xwayland package in Ubuntu: Confirmed Bug description: Original description: When using Chromium (snap) on Wayland (gnome-session), if I keep two windows open on different workspaces, sometimes the current tab becomes unusable as it freezes or is super-slow. This usually happens with specific pages open, like youtube, mattermost, google drive. Minimizing one of the two windows makes the other work fine. The issues does not happen if both windows are on the same workspace. I've seen this issue in 20.04 and 20.10, always on Wayland sessions. The same behavior doesn't happen on a plain X11 session. --- Updates: As for #1916458 this behaviour may happen also on the same workspace and with Google Chrome ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.1-1ubuntu1.1 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Fri Dec 4 09:39:08 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-10-18 (46 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930) RelatedPackageVersions: mutter-common 3.38.1-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1906792/+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 2012388] Re: X11 window (usually AnyDesk) at top-right of the screen is invisible and steals mouse clicks
I would like to add a quick update. - HexChat also triggers the same issue as Anydesk, both wayland and x11. - I upgraded to Mantic Minotaur and the issue persists - I disabled legacy tray icons support from the extension Ubuntu Appindicators, and after a reboot the issue cannot be reproduced. Obviously HexChat icon does not show up on the tray, but it does on the dock, so it is a decent workaround for me until a fix is in place. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/2012388 Title: X11 window (usually AnyDesk) at top-right of the screen is invisible and steals mouse clicks Status in gnome-shell-extension-appindicator package in Ubuntu: Triaged Bug description: Hardware Model: Dell Inc. Inspiron 16 Plus 7620 Firmware version: 1.5.1 CPU i7-12700H x20 GPU: Nvidia RTX3060 / MaxQ GPU: Intel Alder Lake-P Release: Lunar Lobster Architecture: AMD64 Kernel: 6.1.0-16-generic GNOME version: 44.rc Using Latest daily image of Ubuntu Lunar Lobster, I noticed an issue with window focus when windows are placed under the top-right system tray. Since it is hard to explain, I am attaching a screenshot. I am unable to click or interact with anything in the area within green rectangle. Applications affected: - Firefox (snap) - Chromium (snap) - Vivaldi Browser (deb) - Mattermost (snap) ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44~rc-1ubuntu2 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Mar 21 20:35:05 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-01-23 (56 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RelatedPackageVersions: mutter-common 44~rc-1ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-03-02 (19 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/2012388/+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 2012388] Re: AnyDesk X11 window is invisible and steals mouse clicks
I managed to file a bug with AnyDesk, and I linked this Launchpad bug report in it. However, I was not given a bug tracker link by AnyDesk, so I am unable to provide it here. -- 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/2012388 Title: AnyDesk X11 window is invisible and steals mouse clicks Status in gnome-shell package in Ubuntu: Invalid Bug description: Hardware Model: Dell Inc. Inspiron 16 Plus 7620 Firmware version: 1.5.1 CPU i7-12700H x20 GPU: Nvidia RTX3060 / MaxQ GPU: Intel Alder Lake-P Release: Lunar Lobster Architecture: AMD64 Kernel: 6.1.0-16-generic GNOME version: 44.rc Using Latest daily image of Ubuntu Lunar Lobster, I noticed an issue with window focus when windows are placed under the top-right system tray. Since it is hard to explain, I am attaching a screenshot. I am unable to click or interact with anything in the area within green rectangle. Applications affected: - Firefox (snap) - Chromium (snap) - Vivaldi Browser (deb) - Mattermost (snap) ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44~rc-1ubuntu2 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Mar 21 20:35:05 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-01-23 (56 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RelatedPackageVersions: mutter-common 44~rc-1ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-03-02 (19 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2012388/+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 2012388] Re: AnyDesk X11 window is invisible and steals mouse clicks
I logged into a Xorg session and I could not see the window. However, I noticed I can actually see the window for a few moments, both on Wayland and Xorg, when I switch between virtual desktops. There is a small difference is when I switch between virtual desktops: - Wayland: the window appears for a moment, and it looks black - Xorg: the window appears for a moment, and it looks like Anydesk icon I am attaching a short video I took from Xorg session. ** Attachment added: "anydesk-switchvdesktop-xorg.mkv" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2012388/+attachment/5657602/+files/anydesk-switchvdesktop-xorg.mkv -- 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/2012388 Title: AnyDesk X11 window is invisible and steals mouse clicks Status in gnome-shell package in Ubuntu: Invalid Bug description: Hardware Model: Dell Inc. Inspiron 16 Plus 7620 Firmware version: 1.5.1 CPU i7-12700H x20 GPU: Nvidia RTX3060 / MaxQ GPU: Intel Alder Lake-P Release: Lunar Lobster Architecture: AMD64 Kernel: 6.1.0-16-generic GNOME version: 44.rc Using Latest daily image of Ubuntu Lunar Lobster, I noticed an issue with window focus when windows are placed under the top-right system tray. Since it is hard to explain, I am attaching a screenshot. I am unable to click or interact with anything in the area within green rectangle. Applications affected: - Firefox (snap) - Chromium (snap) - Vivaldi Browser (deb) - Mattermost (snap) ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44~rc-1ubuntu2 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Mar 21 20:35:05 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-01-23 (56 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RelatedPackageVersions: mutter-common 44~rc-1ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-03-02 (19 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2012388/+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 2012388] Re: Unable to focus Windows below system tray (wayland session)
I am trying to report the bug upstream and jumping through the required
steps to create a customer account, waiting for it to be activated. I
will report back on that if I manage to actually file a bug there.
Regarding your question to run 'xwininfo -all', please find output below
here.
xwininfo: Window id: 0x600e5f (has no name)
Root window id: 0x49c (the root window) (has no name)
Parent window id: 0x49c (the root window) (has no name)
1 child:
0x4a0001c "AnyDesk": ("AnyDesk" "AnyDesk") 200x200+0+0 +2940+5
1 child:
0x4a0001d (has no name): () 1x1+-1+-1 +2939+4
Absolute upper-left X: 2940
Absolute upper-left Y: 5
Relative upper-left X: 2940
Relative upper-left Y: 5
Width: 200
Height: 200
Depth: 24
Visual: 0x41
Visual Class: TrueColor
Border width: 0
Class: InputOutput
Colormap: 0x40 (installed)
Bit Gravity State: ForgetGravity
Window Gravity State: NorthWestGravity
Backing Store State: NotUseful
Save Under State: no
Map State: IsViewable
Override Redirect State: yes
Corners: +2940+5 -300+5 -300-1235 +2940-1235
-geometry 200x200+2940+5
Bit gravity: ForgetGravity
Window gravity: NorthWestGravity
Backing-store hint: NotUseful
Backing-planes to be preserved: 0x
Backing pixel: 0
Save-unders: No
Someone wants these events:
StructureNotify
PropertyChange
Do not propagate these events:
Override redirection?: Yes
No window manager hints defined
Window manager hints:
Window state:
Skip Pager
Skip Taskbar
Process id: (unknown)
No normal window size hints defined
No zoom window size hints defined
No window shape defined
No border shape defined
--
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/2012388
Title:
Unable to focus Windows below system tray (wayland session)
Status in gnome-shell package in Ubuntu:
Opinion
Bug description:
Hardware Model: Dell Inc. Inspiron 16 Plus 7620
Firmware version: 1.5.1
CPU i7-12700H x20
GPU: Nvidia RTX3060 / MaxQ
GPU: Intel Alder Lake-P
Release: Lunar Lobster
Architecture: AMD64
Kernel: 6.1.0-16-generic
GNOME version: 44.rc
Using Latest daily image of Ubuntu Lunar Lobster, I noticed an issue
with window focus when windows are placed under the top-right system
tray.
Since it is hard to explain, I am attaching a screenshot. I am unable to
click or interact with anything in the area within green rectangle.
Applications affected:
- Firefox (snap)
- Chromium (snap)
- Vivaldi Browser (deb)
- Mattermost (snap)
ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: gnome-shell 44~rc-1ubuntu2
ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
Uname: Linux 6.1.0-16-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.26.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar 21 20:35:05 2023
DisplayManager: gdm3
InstallationDate: Installed on 2023-01-23 (56 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
RelatedPackageVersions: mutter-common 44~rc-1ubuntu3
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to lunar on 2023-03-02 (19 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2012388/+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 2012388] Re: Unable to focus Windows below system tray (wayland session)
Thank you for your help. I have been running some tests: - Disabled all extensions and re-logged the sessionSame result. However, when hovering over the previously mentioned rectangle, I noticed that a popup was appearing, repoting "Anydesk", an application that was set to autostart and had an icon on the taskbar. - Presto I went to prevent this application from auto starting on login, and I cannot reproduce the issue any more. - I re-enabled all gnome extensions, left Anydesk with autostart disabled, and re-logged. I cannot reproduce the issue. - I have other applications that are set to auto start and have a taskbar icon, such as ProtonMail Bridge, Nextcloud client, and Polychromatic. However I cannot reproduce the issue with those applications. Note. I have been using Anydesk for a long time and on Gnome and this is the first time I saw this problem. Do you believe it is worth exploring more about this issue or consider this resolved? I am happy to help if needed. -- 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/2012388 Title: Unable to focus Windows below system tray (wayland session) Status in gnome-shell package in Ubuntu: Incomplete Bug description: Hardware Model: Dell Inc. Inspiron 16 Plus 7620 Firmware version: 1.5.1 CPU i7-12700H x20 GPU: Nvidia RTX3060 / MaxQ GPU: Intel Alder Lake-P Release: Lunar Lobster Architecture: AMD64 Kernel: 6.1.0-16-generic GNOME version: 44.rc Using Latest daily image of Ubuntu Lunar Lobster, I noticed an issue with window focus when windows are placed under the top-right system tray. Since it is hard to explain, I am attaching a screenshot. I am unable to click or interact with anything in the area within green rectangle. Applications affected: - Firefox (snap) - Chromium (snap) - Vivaldi Browser (deb) - Mattermost (snap) ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44~rc-1ubuntu2 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Mar 21 20:35:05 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-01-23 (56 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RelatedPackageVersions: mutter-common 44~rc-1ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-03-02 (19 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2012388/+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 2012388] [NEW] Unable to focus Windows below system tray (wayland session)
Public bug reported: Hardware Model: Dell Inc. Inspiron 16 Plus 7620 Firmware version: 1.5.1 CPU i7-12700H x20 GPU: Nvidia RTX3060 / MaxQ GPU: Intel Alder Lake-P Release: Lunar Lobster Architecture: AMD64 Kernel: 6.1.0-16-generic GNOME version: 44.rc Using Latest daily image of Ubuntu Lunar Lobster, I noticed an issue with window focus when windows are placed under the top-right system tray. Since it is hard to explain, I am attaching a screenshot. I am unable to click or interact with anything in the area within green rectangle. Applications affected: - Firefox (snap) - Chromium (snap) - Vivaldi Browser (deb) - Mattermost (snap) ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44~rc-1ubuntu2 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Mar 21 20:35:05 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-01-23 (56 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RelatedPackageVersions: mutter-common 44~rc-1ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-03-02 (19 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar wayland-session ** Attachment added: "window-focus-01.png" https://bugs.launchpad.net/bugs/2012388/+attachment/5656306/+files/window-focus-01.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/2012388 Title: Unable to focus Windows below system tray (wayland session) Status in gnome-shell package in Ubuntu: New Bug description: Hardware Model: Dell Inc. Inspiron 16 Plus 7620 Firmware version: 1.5.1 CPU i7-12700H x20 GPU: Nvidia RTX3060 / MaxQ GPU: Intel Alder Lake-P Release: Lunar Lobster Architecture: AMD64 Kernel: 6.1.0-16-generic GNOME version: 44.rc Using Latest daily image of Ubuntu Lunar Lobster, I noticed an issue with window focus when windows are placed under the top-right system tray. Since it is hard to explain, I am attaching a screenshot. I am unable to click or interact with anything in the area within green rectangle. Applications affected: - Firefox (snap) - Chromium (snap) - Vivaldi Browser (deb) - Mattermost (snap) ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44~rc-1ubuntu2 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Mar 21 20:35:05 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-01-23 (56 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RelatedPackageVersions: mutter-common 44~rc-1ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-03-02 (19 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2012388/+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 1972726] Re: Update mutter to 42.1
Ubuntu Budgie 22.04 LTS (Xorg) Kernel 5.15.0-33-lowlatency libmutter-10-0 installed from proposed Budgie DE is behaving well, feels snappy and fast. No issues to report. Tests performed: - Check budgie panels and applets. - Move between virtual workspaces. - Window tiling using mouse. - Window tiling using shuffler shortcuts, layouts. - Window minimize and maximize animations. -- 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/1972726 Title: Update mutter to 42.1 Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Jammy: Fix Committed Bug description: Impact -- There is a new bugfix release in the stable 42 series. This is a bigger update with lots of bugfixes as the first bugfix release in the 42 series. https://gitlab.gnome.org/GNOME/mutter/-/blob/42.1/NEWS Test Case - sudo apt install budgie-desktop gnome-session gnome-shell-extensions Install the update. Log out. Select your name on the login screen. Click the gear button to choose a session to log in to. Finish logging in. Verify that things continue to work well for all these sessions: Budgie GNOME GNOME Classic Ubuntu Ubuntu on Xorg (There are more specific test cases for some of the other bugs fixed with this update.) What Could Go Wrong --- Mutter is an essential component of the default Ubuntu desktop and for the desktop used by Ubuntu Budgie. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. mutter is part of GNOME Core and is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Other Info -- This update should not reach jammy-updates until these updates are fully phased in jammy-updates to avoid a known testview scrolling bug in apps like gedit and gnome-text-editor https://launchpad.net/ubuntu/+source/gtk+3.0/3.24.33-1ubuntu2 https://launchpad.net/ubuntu/+source/gtk4/4.6.3+ds1-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1972726/+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 1974471] Re: mouse becomes laggy when fractional scaling is enabled
Quick follow up. I installed Ubuntu 22.04 on same RaspberryPI, and I noticed a huge performance difference with fractional scaling on Wayland. On Wayland I was unable to find any lag or delay or performance hit. On Xorg though, even Ubuntu 22.04 had the same performance issues as Ubuntu Budgie 22.04. Thanks a lot for your expertise, Daniel. Much appreciated. We will make a note on our readme for Ubuntu Budgie ARM. I hope this helps someone down the line. -- 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/1974471 Title: mouse becomes laggy when fractional scaling is enabled Status in mutter package in Ubuntu: Won't Fix Bug description: Distribution: Ubuntu Budgie 22.04 LTS Kernel: 5.15.0-1007-raspi Package: libmutter-10-0 Architecture: arm64 Version: 42.0-3ubuntu2 5.15.0-1007-raspi On Ubuntu Budgie 22.04 LTS raspberry PI, turning on fractional scaling causes an issue where mouse movement becomes laggy and hard to control. This persists even if a reboot is performed after changing scaling settings. This was tested on Raspberry PI 4 8GB with 3 different mice. 2 USB wired, and one wireless with USB dongle. Same results with 3 mice. Disabling fractional scaling immediately solved the problem. Same tests were performed on Ubuntu Budgie 22.04 on amd64 laptop, with Intel CPU and Nvidia+Intel GPU. There was no issue with mouse performance on amd64 laptop. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libmutter-10-0 42.0-3ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-1007.7-raspi 5.15.35 Uname: Linux 5.15.0-1007-raspi aarch64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: Budgie:GNOME Date: Sat May 21 00:48:09 2022 ImageMediaBuild: 20210416 SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1974471/+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 1974471] Re: mouse becomes laggy when fractional scaling is enabled
Daniel, Thank you. This actually makes a lot of sense. Also, even if there is no fix, at least we will know what to tell our users if and when issues like this are reported. I am still going to test on Ubuntu on both Gnome and Wayland, and report if there is any difference, so we can keep it all for the record under same bug report. -- 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/1974471 Title: mouse becomes laggy when fractional scaling is enabled Status in mutter package in Ubuntu: Won't Fix Bug description: Distribution: Ubuntu Budgie 22.04 LTS Kernel: 5.15.0-1007-raspi Package: libmutter-10-0 Architecture: arm64 Version: 42.0-3ubuntu2 5.15.0-1007-raspi On Ubuntu Budgie 22.04 LTS raspberry PI, turning on fractional scaling causes an issue where mouse movement becomes laggy and hard to control. This persists even if a reboot is performed after changing scaling settings. This was tested on Raspberry PI 4 8GB with 3 different mice. 2 USB wired, and one wireless with USB dongle. Same results with 3 mice. Disabling fractional scaling immediately solved the problem. Same tests were performed on Ubuntu Budgie 22.04 on amd64 laptop, with Intel CPU and Nvidia+Intel GPU. There was no issue with mouse performance on amd64 laptop. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libmutter-10-0 42.0-3ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-1007.7-raspi 5.15.35 Uname: Linux 5.15.0-1007-raspi aarch64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: Budgie:GNOME Date: Sat May 21 00:48:09 2022 ImageMediaBuild: 20210416 SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1974471/+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 1974471] Re: mouse becomes laggy when fractional scaling is enabled
Daniel, This is with Xorg fractional scaling on Ubuntu Budgie ARM64. We don't have Wayland on Budgie DE, but I can flash Ubuntu 22.04 ARM64 on a spare microSD and test. Give me a few hours and I will follow up on that. Regarding input, yes I believe same issue as described on https://bugs.launchpad.net/bugs/1902436 . Mouse movements feel slower and also delayed around one second from the moment I move my hand to when I see the cursor moving. -- 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/1974471 Title: mouse becomes laggy when fractional scaling is enabled Status in mutter package in Ubuntu: Incomplete Bug description: Distribution: Ubuntu Budgie 22.04 LTS Kernel: 5.15.0-1007-raspi Package: libmutter-10-0 Architecture: arm64 Version: 42.0-3ubuntu2 5.15.0-1007-raspi On Ubuntu Budgie 22.04 LTS raspberry PI, turning on fractional scaling causes an issue where mouse movement becomes laggy and hard to control. This persists even if a reboot is performed after changing scaling settings. This was tested on Raspberry PI 4 8GB with 3 different mice. 2 USB wired, and one wireless with USB dongle. Same results with 3 mice. Disabling fractional scaling immediately solved the problem. Same tests were performed on Ubuntu Budgie 22.04 on amd64 laptop, with Intel CPU and Nvidia+Intel GPU. There was no issue with mouse performance on amd64 laptop. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libmutter-10-0 42.0-3ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-1007.7-raspi 5.15.35 Uname: Linux 5.15.0-1007-raspi aarch64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: Budgie:GNOME Date: Sat May 21 00:48:09 2022 ImageMediaBuild: 20210416 SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1974471/+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 1974471] [NEW] mouse becomes laggy when fractional scaling is enabled
Public bug reported: Distribution: Ubuntu Budgie 22.04 LTS Kernel: 5.15.0-1007-raspi Package: libmutter-10-0 Architecture: arm64 Version: 42.0-3ubuntu2 5.15.0-1007-raspi On Ubuntu Budgie 22.04 LTS raspberry PI, turning on fractional scaling causes an issue where mouse movement becomes laggy and hard to control. This persists even if a reboot is performed after changing scaling settings. This was tested on Raspberry PI 4 8GB with 3 different mice. 2 USB wired, and one wireless with USB dongle. Same results with 3 mice. Disabling fractional scaling immediately solved the problem. Same tests were performed on Ubuntu Budgie 22.04 on amd64 laptop, with Intel CPU and Nvidia+Intel GPU. There was no issue with mouse performance on amd64 laptop. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libmutter-10-0 42.0-3ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-1007.7-raspi 5.15.35 Uname: Linux 5.15.0-1007-raspi aarch64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: Budgie:GNOME Date: Sat May 21 00:48:09 2022 ImageMediaBuild: 20210416 SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 arm64-image jammy raspi-image -- 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/1974471 Title: mouse becomes laggy when fractional scaling is enabled Status in mutter package in Ubuntu: New Bug description: Distribution: Ubuntu Budgie 22.04 LTS Kernel: 5.15.0-1007-raspi Package: libmutter-10-0 Architecture: arm64 Version: 42.0-3ubuntu2 5.15.0-1007-raspi On Ubuntu Budgie 22.04 LTS raspberry PI, turning on fractional scaling causes an issue where mouse movement becomes laggy and hard to control. This persists even if a reboot is performed after changing scaling settings. This was tested on Raspberry PI 4 8GB with 3 different mice. 2 USB wired, and one wireless with USB dongle. Same results with 3 mice. Disabling fractional scaling immediately solved the problem. Same tests were performed on Ubuntu Budgie 22.04 on amd64 laptop, with Intel CPU and Nvidia+Intel GPU. There was no issue with mouse performance on amd64 laptop. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libmutter-10-0 42.0-3ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-1007.7-raspi 5.15.35 Uname: Linux 5.15.0-1007-raspi aarch64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: Budgie:GNOME Date: Sat May 21 00:48:09 2022 ImageMediaBuild: 20210416 SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1974471/+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 1551171]
Hitting this same problem in Kubuntu 20.04. My case is this. In /usr/share/applications/defaults.list I had this: application/pdf=org.gnome.Evince.desktop;google-chrome.desktop I guess the trailing ";google-chrome.desktop" was in some way added by installing Chrome. Firefox says my default PDF application is Chrome, while all the other system components (Dolphin, xdg-mime, xdg-open) correctly say that my default is Okular. After editing /usr/share/applications/defaults.list to remove the trailing ";google-chrome.desktop", now Firefox correctly knows my default application for PDFs is Okular. No need to restart Firefox, the change was immediate. Strange enough, I don't have Evince installed, but many other file types are associated with Evince in that defaults.list file. I guess Evince is ignored because it is not installed. On the contrary, Chrome is installed and so it's honored by Firefox, but in this case it's skipping and ignoring my actual system settings for PDF file association. So, there must be some problem here. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1551171 Title: /usr/share/applications/mimeinfo.cache is used for default applications in Firefox Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: New Bug description: See https://bugzilla.mozilla.org/show_bug.cgi?id=727422 With Firefox, default applications are selected by Firefox using /usr/share/applications/mimeinfo.cache, however, this list is a system generated list in random order and therefor does not reflect the user's preferences of which application should be used to open a file. When I click on a pdf (for example), I want to have the option to open it in my default application, in my case in okular, and not in something else. However, acroread is invariably presented is presented as default choice because it happens to be the first entry in /usr/share/applications/mimeinfo.cache for application/pdf. This happens in spite of the fact that the desktop provides correct defaults.list and mimeapps.list files The comments in the firefox bug seem to suggest that firefox developers are convinced that firefox calls the correct gtk libraries to determine the correct application. If this is the case, then it is necessarily the ubuntu (or possibly kubuntu) infrastructure to be failing. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: firefox 44.0.2+build1-0ubuntu0.15.10.1 ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 BuildID: 20160209234513 CurrentDesktop: KDE Date: Mon Feb 29 11:37:25 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (808 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: firefox UpgradeStatus: Upgraded to wily on 2015-10-23 (129 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1551171/+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 1914403] Re: Simple Scan UI freezes while scanning from second page on
** Changed in: simple-scan (Ubuntu) Status: Incomplete => New -- 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/1914403 Title: Simple Scan UI freezes while scanning from second page on Status in simple-scan package in Ubuntu: New Bug description: In Kubuntu 20.04 Simple Scan application shows the following behaviour on my system. While scanning the first page, all works fine: the UI is responsive and the live preview of the page being scanned is shown. Starting from the second page on, while the page scanning is in progress the UI is completely frozen and hence no live preview is shown. Trying to click on the application window shows the UI is completely unresponsive. This lasts until around 10 seconds after the page scanning has been completed (and the scanner light has returned to the "home" position). Apart from this, the application works, but this slows down multi-page scanning process and hurts user experience. My scanner is a Canon LiDE 110, a flatbed one. Simple Scan was working perfectly fine in Ubuntu 16.04 and Ubuntu 14.04 on the same system (after upgrading SANE drivers, but for a completely different reason) and was not showing this behaviour. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: simple-scan 3.36.3-0ubuntu0.20.04.0 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Feb 3 13:04:50 2021 InstallationDate: Installed on 2020-10-05 (120 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Hewlett-Packard HP ProBook 450 G1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-65-generic root=/dev/mapper/vgkubuntu-root ro quiet splash zswap.enabled=1 zswap.compressor=lz4 vt.handoff=7 SimpleScanLog: [+0,00s] DEBUG: simple-scan.vala:1720: Starting /usr/bin/simple-scan 3.36.3, PID=56452 SourcePackage: simple-scan UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/18/2020 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L74 Ver. 01.50 dmi.board.name: 1942 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 12.F4 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL74Ver.01.50:bd02/18/2020:svnHewlett-Packard:pnHPProBook450G1:pvrA3009DD10303:rvnHewlett-Packard:rn1942:rvrKBCVersion12.F4:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO dmi.product.name: HP ProBook 450 G1 dmi.product.sku: E9Y21EA#ABZ dmi.product.version: A3009DD10303 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1914403/+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 1914403] Re: Simple Scan UI freezes while scanning from second page on
Here it is the output produced by simple-scan -d I did this: - start the program - scan first page (all working fine) - scan second page (UI frozen) - wait for the UI to become responsive again - exit program ** Attachment added: "Simple Scan debug log (both std out and std err)" https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1914403/+attachment/5460609/+files/simplescan.log -- 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/1914403 Title: Simple Scan UI freezes while scanning from second page on Status in simple-scan package in Ubuntu: Incomplete Bug description: In Kubuntu 20.04 Simple Scan application shows the following behaviour on my system. While scanning the first page, all works fine: the UI is responsive and the live preview of the page being scanned is shown. Starting from the second page on, while the page scanning is in progress the UI is completely frozen and hence no live preview is shown. Trying to click on the application window shows the UI is completely unresponsive. This lasts until around 10 seconds after the page scanning has been completed (and the scanner light has returned to the "home" position). Apart from this, the application works, but this slows down multi-page scanning process and hurts user experience. My scanner is a Canon LiDE 110, a flatbed one. Simple Scan was working perfectly fine in Ubuntu 16.04 and Ubuntu 14.04 on the same system (after upgrading SANE drivers, but for a completely different reason) and was not showing this behaviour. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: simple-scan 3.36.3-0ubuntu0.20.04.0 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Feb 3 13:04:50 2021 InstallationDate: Installed on 2020-10-05 (120 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Hewlett-Packard HP ProBook 450 G1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-65-generic root=/dev/mapper/vgkubuntu-root ro quiet splash zswap.enabled=1 zswap.compressor=lz4 vt.handoff=7 SimpleScanLog: [+0,00s] DEBUG: simple-scan.vala:1720: Starting /usr/bin/simple-scan 3.36.3, PID=56452 SourcePackage: simple-scan UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/18/2020 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L74 Ver. 01.50 dmi.board.name: 1942 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 12.F4 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL74Ver.01.50:bd02/18/2020:svnHewlett-Packard:pnHPProBook450G1:pvrA3009DD10303:rvnHewlett-Packard:rn1942:rvrKBCVersion12.F4:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO dmi.product.name: HP ProBook 450 G1 dmi.product.sku: E9Y21EA#ABZ dmi.product.version: A3009DD10303 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1914403/+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 1914403] [NEW] Simple Scan UI freezes while scanning from second page on
Public bug reported: In Kubuntu 20.04 Simple Scan application shows the following behaviour on my system. While scanning the first page, all works fine: the UI is responsive and the live preview of the page being scanned is shown. Starting from the second page on, while the page scanning is in progress the UI is completely frozen and hence no live preview is shown. Trying to click on the application window shows the UI is completely unresponsive. This lasts until around 10 seconds after the page scanning has been completed (and the scanner light has returned to the "home" position). Apart from this, the application works, but this slows down multi-page scanning process and hurts user experience. My scanner is a Canon LiDE 110, a flatbed one. Simple Scan was working perfectly fine in Ubuntu 16.04 and Ubuntu 14.04 on the same system (after upgrading SANE drivers, but for a completely different reason) and was not showing this behaviour. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: simple-scan 3.36.3-0ubuntu0.20.04.0 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Feb 3 13:04:50 2021 InstallationDate: Installed on 2020-10-05 (120 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Hewlett-Packard HP ProBook 450 G1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-65-generic root=/dev/mapper/vgkubuntu-root ro quiet splash zswap.enabled=1 zswap.compressor=lz4 vt.handoff=7 SimpleScanLog: [+0,00s] DEBUG: simple-scan.vala:1720: Starting /usr/bin/simple-scan 3.36.3, PID=56452 SourcePackage: simple-scan UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/18/2020 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L74 Ver. 01.50 dmi.board.name: 1942 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 12.F4 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL74Ver.01.50:bd02/18/2020:svnHewlett-Packard:pnHPProBook450G1:pvrA3009DD10303:rvnHewlett-Packard:rn1942:rvrKBCVersion12.F4:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO dmi.product.name: HP ProBook 450 G1 dmi.product.sku: E9Y21EA#ABZ dmi.product.version: A3009DD10303 dmi.sys.vendor: Hewlett-Packard ** Affects: simple-scan (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- 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/1914403 Title: Simple Scan UI freezes while scanning from second page on Status in simple-scan package in Ubuntu: New Bug description: In Kubuntu 20.04 Simple Scan application shows the following behaviour on my system. While scanning the first page, all works fine: the UI is responsive and the live preview of the page being scanned is shown. Starting from the second page on, while the page scanning is in progress the UI is completely frozen and hence no live preview is shown. Trying to click on the application window shows the UI is completely unresponsive. This lasts until around 10 seconds after the page scanning has been completed (and the scanner light has returned to the "home" position). Apart from this, the application works, but this slows down multi-page scanning process and hurts user experience. My scanner is a Canon LiDE 110, a flatbed one. Simple Scan was working perfectly fine in Ubuntu 16.04 and Ubuntu 14.04 on the same system (after upgrading SANE drivers, but for a completely different reason) and was not showing this behaviour. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: simple-scan 3.36.3-0ubuntu0.20.04.0 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Feb 3 13:04:50 2021 InstallationDate: Installed on 2020-10-05 (120 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Hewlett-Packard HP ProBook 450 G1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-65-generic root=/dev/mapper/vgkubuntu-root ro quiet splash zswap.enabled=1 zswap.compressor=lz4 vt.handoff=7 SimpleScanLog: [+0,00s] DEBUG: simple-scan.vala:1720: Starting /usr/bin/simple-scan 3.36.3, PID=56452 SourcePackage: simple-scan UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/18/2020 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L74 Ver. 01.50 dmi.board.name: 1942 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 12.F4 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias:
[Desktop-packages] [Bug 1873895] Re: Regression: block staircase display with side-by-side monitors of different pixel widths
I tested both Xubuntu 20.04 and Ubuntu MATE 20.04 And I had the very same issue, however I have a single display, 3440x1440, using AMD RADEON VII GPU. Kubuntu 20.04 and Ubuntu Budgie 20.04 do not have this issue. Originally I opened a separate bug but it was marked as duplicate. I wanted to confirm the same issue is still there. After testing 20.04.1, making both xubuntu and ubuntu MATE unusable unless compositor is disabled as suggested in this bug report: https://bugs.launchpad.net/ubuntu/+source/marco/+bug/1876480 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxcb in Ubuntu. https://bugs.launchpad.net/bugs/1873895 Title: Regression: block staircase display with side-by-side monitors of different pixel widths Status in Linux: Unknown Status in libxcb package in Ubuntu: Confirmed Status in xfwm4 package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: Update based on further research. This only happens when the secondary external display is operating at a different pixel width to the internal. In this case eDP is 1920x1080 whereas the external HDMI-A-0 is natively 1680x1050. It is caused by xfwm4's recent switch from using glx to xpresent for AMD GPUs. The underlying bug is in the AMD driver. I was able to reproduce on an external 1920x1200 display only when it was set to a non-native 1680x1050 resolution. --- Two identical Lenovo E495 laptops with 20.04 installed. The problem occurred initially on the laptop that is having package upgrades applied regularly. With dual monitors and the external monitor placed left or right the display has a blocked staircase effect shown in the attached photograph, and seems related to https://gitlab.freedesktop.org/xorg/driver/xf86-video- amdgpu/-/issues/10 More detailed investigation suggests it only happens when the X coordinate of the two monitors is different. The symptom looks like an off-by-one error because it appears as if the display is divided into, say, 10 rows and 15 columns but the first row has 16 'columns' worth of blocks on it and so wraps to the beginning of the 2nd row, and so on. On the laptop without package upgrades being applied this didn't happen. So I upgraded it (314 packages) and restarted and it too sees the same problem. I suspected libxcomposite1 and downgraded it to 1:0.4.5-0ubuntu1 but that didn't solve it. I now suspect libxcb but so far haven't been able to prove it. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkPad E595 [17aa:5124] InstallationDate: Installed on 2020-04-08 (11 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408) MachineType: LENOVO 20NECTO1WW Package: xserver-xorg-video-amdgpu 19.1.0-1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/ELLOE000-rootfs ro acpi_osi=! "acpi_osi=Windows 2016" quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal ubuntu ubuntu Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sudo users _MarkForUpload: True dmi.bios.date: 12/23/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R11ET32W (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NECTO1WW 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: None dmi.modalias: dmi:bvnLENOVO:bvrR11ET32W(1.12):bd12/23/2019:svnLENOVO:pn20NECTO1WW:pvrThinkPadE495:rvnLENOVO:rn20NECTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E495 dmi.product.name: 20NECTO1WW dmi.product.sku: LENOVO_MT_20NE_BU_Think_FM_ThinkPad E495 dmi.product.version: ThinkPad E495 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
[Desktop-packages] [Bug 1799580] Re: Settings made by qasmixer are lost on next reboot
I noticed the same bug affecting me on 3 installs: 1. Ubuntu Budgie 20.04 with Ubuntu Studio tools. Desktop, USB audio interface. 2. Ubuntu Budgie 20.04 with Ubuntu Studio tools. Laptop, Internal Audio card. 3. Ubuntu Studio 20.10 daily. Desktop, USB audio interface. I do not think the issue is specifically of QASmixer. I tried to manipulate ALSA volume settings using alsamixer and and alsactl store, both with normal user and using sudo. Volume settings persist in the session, if I close and reopen QASmixer or alsamixer, but all volume settings are reset on reboot. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-utils in Ubuntu. https://bugs.launchpad.net/bugs/1799580 Title: Settings made by qasmixer are lost on next reboot Status in alsa-utils package in Ubuntu: Confirmed Bug description: I use qasmixer to set the "Synth" volume to full, on my SoundBlaster Live sound-card. On prior levels of Ubuntu (through 18.04), any settings I make are preserved over reboots. On the latest level of Ubuntu (18.10) the settings are effective only as long as the system is running. The next time I reboot, the settings are gone, and I have to use qasmixer to set them all over again. I expected the settings made by qasmixer to be preserved on the next reboot, as with past levels of Ubuntu. The settings made by qasmixer are not preserved over a reboot on Ubuntu 18.10. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: qasmixer 0.21.0-1.1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic i686 ApportVersion: 2.20.10-0ubuntu13 Architecture: i386 CurrentDesktop: LXQt Date: Tue Oct 23 14:59:06 2018 InstallationDate: Installed on 2018-10-23 (0 days ago) InstallationMedia: Lubuntu 18.10 "Cosmic Cuttlefish" - Release i386 (20181017.2) SourcePackage: qastools UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/1799580/+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 1888703] Re: After the latest update on 7/21/20 the screen shows random black horizontal single pixel line stripes in columns about 10-20 pixels long on open windows and icons
The kernel causing the problem is 5.4.0-42-generic. rolling back to 5.3.0-62-generic eliminated the problem. -- 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/1888703 Title: After the latest update on 7/21/20 the screen shows random black horizontal single pixel line stripes in columns about 10-20 pixels long on open windows and icons presented on the desktop. Status in nautilus package in Ubuntu: New Bug description: Everything else works well in the system except for this issue. See attached picture for details. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus (not installed) ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic i686 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: i386 CurrentDesktop: MATE Date: Thu Jul 23 08:14:26 2020 InstallationDate: Installed on 2019-12-08 (228 days ago) InstallationMedia: Ubuntu-MATE 18.04.3 LTS "Bionic Beaver" - Release i386 (20190805) 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/1888703/+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 1888703] [NEW] After the latest update on 7/21/20 the screen shows random black horizontal single pixel line stripes in columns about 10-20 pixels long on open windows and icon
Public bug reported: Everything else works well in the system except for this issue. See attached picture for details. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus (not installed) ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic i686 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: i386 CurrentDesktop: MATE Date: Thu Jul 23 08:14:26 2020 InstallationDate: Installed on 2019-12-08 (228 days ago) InstallationMedia: Ubuntu-MATE 18.04.3 LTS "Bionic Beaver" - Release i386 (20190805) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug bionic i386 ** Attachment added: "IMG_0115_scaled.JPG" https://bugs.launchpad.net/bugs/1888703/+attachment/5395309/+files/IMG_0115_scaled.JPG -- 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/1888703 Title: After the latest update on 7/21/20 the screen shows random black horizontal single pixel line stripes in columns about 10-20 pixels long on open windows and icons presented on the desktop. Status in nautilus package in Ubuntu: New Bug description: Everything else works well in the system except for this issue. See attached picture for details. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus (not installed) ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic i686 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: i386 CurrentDesktop: MATE Date: Thu Jul 23 08:14:26 2020 InstallationDate: Installed on 2019-12-08 (228 days ago) InstallationMedia: Ubuntu-MATE 18.04.3 LTS "Bionic Beaver" - Release i386 (20190805) 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/1888703/+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 437508] Re: policykit prompts don't use sensible defaults (current user should be default)
this behaviour is no more enabled, ubuntu 18-19-20 ask always the password of the first admin created. I think this is wrong. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/437508 Title: policykit prompts don't use sensible defaults (current user should be default) Status in policykit-1 package in Ubuntu: Triaged Bug description: Binary package hint: policykit-1 Every time update-manager prompts me for authentication information now, I have to manually select my current username from the list of available admin users. This is not sensible default behavior; if the current user is an admin user, it should be prepopulated in the pulldown list. ProblemType: Bug Architecture: amd64 Date: Sat Sep 26 22:32:09 2009 DistroRelease: Ubuntu 9.10 Package: policykit 0.9-4ubuntu1 ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-10.35-generic SourcePackage: policykit Uname: Linux 2.6.31-10-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/437508/+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 793792] Re: New users in admin group cannot use policykit
me too, also see https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/437508 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/793792 Title: New users in admin group cannot use policykit Status in adduser package in Ubuntu: Confirmed Status in policykit-1 package in Ubuntu: Confirmed Status in user-setup package in Ubuntu: Confirmed Bug description: Binary package hint: policykit-1 New created users in admin, can't get privileges via policykit to do administrative tasks. If I create a new administrator user with "adduser --ingroup admin username" is with the intention of he/she to can administrate the system, and he/she won't be able to do it if a policykit authentication is needed, because policykit asks for "root" password, and not for the user password. Steps to reproduce: 1) Create a new admin user with "adduser --ingroup admin username". 2) Login with the new user. 3) Delete the old administrator user (installation user). 3) Try to administrate the system with any tool which requires policykit authentication. 4) You won't be able because the policykit dialog asks for the "root" password, not for your user password, and the old administrator account has been deleted. New created administrator users should be able to do administrative tasks with policykit authentication. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: policykit-1 0.101-1ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic i686 Architecture: i386 Date: Tue Jun 7 00:59:46 2011 EcryptfsInUse: Yes InstallationMedia: Kubuntu 11.04 "Natty Narwhal" - Release i386 (20110423) ProcEnviron: LANGUAGE= PATH=(custom, user) LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: policykit-1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/793792/+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 49348] Re: List view in Nautilus does not allow dragging a selection by mouse
sane in popos 19.10 -- 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/49348 Title: List view in Nautilus does not allow dragging a selection by mouse Status in GTK+: New Status in Nautilus: Confirmed Status in nautilus package in Ubuntu: Triaged Bug description: When viewing files in Nautilus one can drag a rectangle around them to mark certain files. This is not possible in the list view of Nautilus even though there is usually a large white space in folders with few files that can make a user believe that dragging with the mouse there would produce the same rectangle as in icon view. I do it all the time by habit, and it is very annoying. Proposal: * Make it possible to drag a rectangle in list view. The problem is that starting to drag on a list item moves that item. Konqueror has solved this that you have to drag on the item name itself to move, else a rectangle marquee is started. Personally I find this quite efficient but may be annoying for less experienced users... To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/49348/+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 1825717] Re: hplip issue during hp-setup - stuck at plugin install
Additional Feedback. I did a fresh install of ubuntu-budgie 19.04 1. installed hplip from repos (version 3.19.1) 2. ran hp-setup -i 3. went through the steps 4. install completed including plugin, can print and scan with no issue -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1825717 Title: hplip issue during hp-setup - stuck at plugin install Status in hplip package in Ubuntu: Confirmed Bug description: Fresh install of Kubuntu 19.04 Installed hplip from repositories, available version is 3.19.1+dfsg0-1 When I start setup with hp-setup, this happens: 1. I am asked connection type. I select network ethernet 2. My printer is detected. I select it and hit next 3. I am told about the proprietary plugin to download. I confirm, accept download. I enter my user's password. I get a confirmation that the plugin is correctly Installed. 4. On next screen, I get a warning and cannot continue installation. I am told this printer needs a proprietary plugin to work correctly. After this I am stuck in a loop between points 3 and 4. I also tried to start hp-setup from super user on command line. but no way around this issue. What I did next, I manually downloaded hplip-3.19.3.run from HP website. Removed version of hplip installed from repositories. Installed from manually downloaded package, followed the very same steps. Everything worked fine and printer is installed successfully. I hope this information is useful. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1825717/+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 1825717] Re: hplip issue during hp-setup - stuck at plugin install
Additional Feedback. I did a fresh install of ubuntu-budgie 19.04 1. installed hplip from repos (version 3.19.1) 2. ran hp-setup -i 3. went through the steps 4. install completed including plugin, can print and scan with no issue -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1825717 Title: hplip issue during hp-setup - stuck at plugin install Status in hplip package in Ubuntu: Confirmed Bug description: Fresh install of Kubuntu 19.04 Installed hplip from repositories, available version is 3.19.1+dfsg0-1 When I start setup with hp-setup, this happens: 1. I am asked connection type. I select network ethernet 2. My printer is detected. I select it and hit next 3. I am told about the proprietary plugin to download. I confirm, accept download. I enter my user's password. I get a confirmation that the plugin is correctly Installed. 4. On next screen, I get a warning and cannot continue installation. I am told this printer needs a proprietary plugin to work correctly. After this I am stuck in a loop between points 3 and 4. I also tried to start hp-setup from super user on command line. but no way around this issue. What I did next, I manually downloaded hplip-3.19.3.run from HP website. Removed version of hplip installed from repositories. Installed from manually downloaded package, followed the very same steps. Everything worked fine and printer is installed successfully. I hope this information is useful. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1825717/+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 1825717] Re: hplip issue during hp-setup - stuck at plugin install
I re-created the same issue on another install, this time Ubuntu-Budgie 19.04. Same issue happened, same solution fixed it. Detailed steps I followed to fix the issue: 1. Go to https://developers.hp.com/hp-linux-imaging-and-printing/gethplip . 2. Download latest version for Ubuntu . At the time of writing latest version is 3.19.3 . 3. Download hplip-3.19.3.run file, remember to change permissions to make it executable. 4. Remove hplip installed by your distribution repositories. 5. Download hplip-3.19.3-plugin.run and hplip-3.19.3-plugin.run.asc from https://developers.hp.com/hp-linux-imaging-and-printing/plugins . 6. run hplip-3.19.3.run in a terminal, follow instructions on screen. 7. During printer setup process, when asked, always use interactive mode instead of gui. When asked for plugin, select path instead of download from server, provide path including full name of hplip-3.19.3-plugin.run . -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1825717 Title: hplip issue during hp-setup - stuck at plugin install Status in hplip package in Ubuntu: New Bug description: Fresh install of Kubuntu 19.04 Installed hplip from repositories, available version is 3.19.1+dfsg0-1 When I start setup with hp-setup, this happens: 1. I am asked connection type. I select network ethernet 2. My printer is detected. I select it and hit next 3. I am told about the proprietary plugin to download. I confirm, accept download. I enter my user's password. I get a confirmation that the plugin is correctly Installed. 4. On next screen, I get a warning and cannot continue installation. I am told this printer needs a proprietary plugin to work correctly. After this I am stuck in a loop between points 3 and 4. I also tried to start hp-setup from super user on command line. but no way around this issue. What I did next, I manually downloaded hplip-3.19.3.run from HP website. Removed version of hplip installed from repositories. Installed from manually downloaded package, followed the very same steps. Everything worked fine and printer is installed successfully. I hope this information is useful. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1825717/+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 1825717] [NEW] hplip issue during hp-setup - stuck at plugin install
Public bug reported: Fresh install of Kubuntu 19.04 Installed hplip from repositories, available version is 3.19.1+dfsg0-1 When I start setup with hp-setup, this happens: 1. I am asked connection type. I select network ethernet 2. My printer is detected. I select it and hit next 3. I am told about the proprietary plugin to download. I confirm, accept download. I enter my user's password. I get a confirmation that the plugin is correctly Installed. 4. On next screen, I get a warning and cannot continue installation. I am told this printer needs a proprietary plugin to work correctly. After this I am stuck in a loop between points 3 and 4. I also tried to start hp-setup from super user on command line. but no way around this issue. What I did next, I manually downloaded hplip-3.19.3.run from HP website. Removed version of hplip installed from repositories. Installed from manually downloaded package, followed the very same steps. Everything worked fine and printer is installed successfully. I hope this information is useful. ** Affects: hplip (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1825717 Title: hplip issue during hp-setup - stuck at plugin install Status in hplip package in Ubuntu: New Bug description: Fresh install of Kubuntu 19.04 Installed hplip from repositories, available version is 3.19.1+dfsg0-1 When I start setup with hp-setup, this happens: 1. I am asked connection type. I select network ethernet 2. My printer is detected. I select it and hit next 3. I am told about the proprietary plugin to download. I confirm, accept download. I enter my user's password. I get a confirmation that the plugin is correctly Installed. 4. On next screen, I get a warning and cannot continue installation. I am told this printer needs a proprietary plugin to work correctly. After this I am stuck in a loop between points 3 and 4. I also tried to start hp-setup from super user on command line. but no way around this issue. What I did next, I manually downloaded hplip-3.19.3.run from HP website. Removed version of hplip installed from repositories. Installed from manually downloaded package, followed the very same steps. Everything worked fine and printer is installed successfully. I hope this information is useful. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1825717/+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 1721282] Re: upowerd/gnome-power-statistics crash; high CPU, memory consumption
But isn't this a sufficiently severe bug for a LTS release, considering that currenntly supported kernels cause this (so I would say it's a regression) and that when this happens the system battery is drained and the user may even hardly realise why? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1721282 Title: upowerd/gnome-power-statistics crash; high CPU, memory consumption Status in upower package in Ubuntu: Fix Released Bug description: Not sure if necessary here since same bug is already on: https://bugzilla.redhat.com/show_bug.cgi?id=1427621 https://bugs.freedesktop.org/show_bug.cgi?id=100626 https://bugzilla.gnome.org/show_bug.cgi?id=781088 Tested on Ubuntu 16.04.3, 4.12.0-041200rc3-generic Steps to reproduce: 1. have a system with a recent kernel (4.10.x or later) 2. start gnome-power-statistics 3. go to Pprocessor tab 4. have a look at gnome-system-monitor or htop Result: - On Processor section, Wakeups tab: "Processor wakeups pers second: GDBus.Error:org.freedesktop.UPower.GeneralError: cannot enable timerstats." - High CPU usage of /usr/lib/upower/upowerd - Crash gnome-power-statistics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1721282/+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 1721282] Re: upowerd/gnome-power-statistics crash; high CPU, memory consumption
I'm experiencing high CPU usage by upowerd in Linux Mint 18.3 KDE (based on Ubuntu 16.04) with 4.15 kernel. I'm not using gnome-power-statistics, but I see the error message about missing /proc/timer_stats in my syslog. I think it's bug https://bugs.freedesktop.org/show_bug.cgi?id=100626 Why the fix hasn't been applied to Xenial? ** Bug watch added: freedesktop.org Bugzilla #100626 https://bugs.freedesktop.org/show_bug.cgi?id=100626 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1721282 Title: upowerd/gnome-power-statistics crash; high CPU, memory consumption Status in gnome-power-manager package in Ubuntu: Confirmed Bug description: Not sure if necessary here since same bug is already on: https://bugzilla.redhat.com/show_bug.cgi?id=1427621 https://bugs.freedesktop.org/show_bug.cgi?id=100626 https://bugzilla.gnome.org/show_bug.cgi?id=781088 Tested on Ubuntu 16.04.3, 4.12.0-041200rc3-generic Steps to reproduce: 1. have a system with a recent kernel (4.10.x or later) 2. start gnome-power-statistics 3. go to Pprocessor tab 4. have a look at gnome-system-monitor or htop Result: - On Processor section, Wakeups tab: "Processor wakeups pers second: GDBus.Error:org.freedesktop.UPower.GeneralError: cannot enable timerstats." - High CPU usage of /usr/lib/upower/upowerd - Crash gnome-power-statistics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1721282/+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 1184699] Re: Canon LIDE 110 can only scan once, then I need to replug the usb cable
I can just report my own experience. As described in my previous comments, in Mint 17 (based on Ubuntu Trusty) I had to replace the built-in driver with one compiled from source to be able to use this scanner. I used sane-backends-git20141102 and I lived with it for some years with almost no problem (just some sporadic crashes). I upgraded to Mint 18 (based on Xenial) just last week and yesterday I scanned a couple of pages with no issue at all, but it's a bit soon to draw conclusions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1184699 Title: Canon LIDE 110 can only scan once, then I need to replug the usb cable Status in sane-backends package in Ubuntu: Confirmed Bug description: I have a Canon LIDE 110 scanner which works by default on ubuntu 13.04. The problem is after first scan, I can not scan for second time. I need to reconnect the USB cable to use the scanner again. # TEST 1 : without reconnecting the usb cable francois@pc:~$ scanimage -v > test1.jpg # success scanimage: scanning image of size 636x885 pixels at 8 bits/pixel scanimage: acquiring gray frame scanimage: min/max graylevel value = 0/255 scanimage: read 562860 bytes in total # I don't unplug plug the usb cable. francois@pc:~$ scanimage -v > test2.jpg # FAIL scanimage: no SANE devices found # TEST 2 : reconnect usb cable between scan attempts francois@pc:~$ scanimage -v > test1.jpg # success scanimage: scanning image of size 636x885 pixels at 8 bits/pixel scanimage: acquiring gray frame scanimage: min/max graylevel value = 0/255 scanimage: read 562860 bytes in total # I unplug and replug the usb cable. francois@pc:~$ scanimage -v > test2.jpg # SUCCESS scanimage: scanning image of size 636x885 pixels at 8 bits/pixel scanimage: acquiring gray frame scanimage: min/max graylevel value = 0/255 scanimage: read 562860 bytes in total francois@pc:~$ dmesg # extract [ 829.365158] usb 3-1: USB disconnect, device number 2 [ 834.935000] usb 3-1: new high-speed USB device number 4 using xhci_hcd [ 834.952515] usb 3-1: New USB device found, idVendor=04a9, idProduct=1909 [ 834.952519] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 834.952522] usb 3-1: Product: CanoScan [ 834.952524] usb 3-1: Manufacturer: Canon [ 1623.738811] usb 3-1: USB disconnect, device number 4 [ 1623.739072] xhci_hcd :00:14.0: Slot 3 endpoint 6 not removed from BW list! [ 1625.528827] usb 3-1: new high-speed USB device number 5 using xhci_hcd [ 1625.546327] usb 3-1: New USB device found, idVendor=04a9, idProduct=1909 [ 1625.546331] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 1625.546334] usb 3-1: Product: CanoScan [ 1625.546336] usb 3-1: Manufacturer: Canon francois@pc:~$ uname -a && cat /etc/issue Linux pc 3.8.0-22-generic #33-Ubuntu SMP Thu May 16 15:17:14 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Ubuntu 13.04 \n \l The problem was reported here by someone else : http://askubuntu.com/questions/278473/canon-lide-110-should-reconnect- usb-for-each-scan Thanks François To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1184699/+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 1813511] Re: Gnome shell extensions disabled at every wakeup after sleep
I didn't encountered the bug any more in the last 7 days. It could have been fixed by some ubuntu updates (at least on my system). -- 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/1813511 Title: Gnome shell extensions disabled at every wakeup after sleep Status in gnome-shell package in Ubuntu: Confirmed Bug description: Ubuntu 18.04, all gnome extensions get turned off after waking up from sleep Noticed since: past 1-2 week Workaround: Alt+F2 followed by 'r' - Turns on the extensions which I had on earlier --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-08-02 (180 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Package: gnome-shell 3.28.3-0ubuntu0.18.04.4 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1813511/+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 1813511] Re: Gnome shell extensions disabled at every wakeup after sleep
I tested pidof gnome-shell before and after the bug occurrence but the answer is the same. Please find attached two screenshots of login screen before and after bug occurrence. After the bug occurrence the dock is visible in the login screen. ** Attachment added: "login screen after (left) and before (right) bug occurrence" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1813511/+attachment/5234278/+files/photo_2019-01-30_14-21-50m.jpg -- 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/1813511 Title: Gnome shell extensions disabled at every wakeup after sleep Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 18.04, all gnome extensions get turned off after waking up from sleep Noticed since: past 1-2 week Workaround: Alt+F2 followed by 'r' - Turns on the extensions which I had on earlier --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-08-02 (180 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Package: gnome-shell 3.28.3-0ubuntu0.18.04.4 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1813511/+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 1813511] Re: Gnome shell extensions disabled at every wakeup after sleep
This bug also started affecting me since a couple of weeks ago. Gnome shell extensions appear as switched on in gnome tweak but they are actually disabled. I noticed the bug appear more or less randomly after recovery from suspend or even from black screen. Resuming from black screen the shell theme appears as reverted back to default in the login screen. Also the ubuntu-dock appear in the login screen. -- 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/1813511 Title: Gnome shell extensions disabled at every wakeup after sleep Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 18.04, all gnome extensions get turned off after waking up from sleep Noticed since: past 1-2 week Workaround: Alt+F2 followed by 'r' - Turns on the extensions which I had on earlier --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-08-02 (180 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Package: gnome-shell 3.28.3-0ubuntu0.18.04.4 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1813511/+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 1778011] Re: PRIME Power Saving mode draws too much power
This bug also affects me. I am running Kubuntu 18.04 on Gigabyte AERO14, CPU:i7-7700HQ (45W TDP), GPU:Nvidia 1050Ti I took a full system image with clonezilla, and tested Alberto Milone's PPA. System working fine after the upgrade. I tested switch+reboot around 20 times. Test results: No issue rebooting with or without switching GPU. GPU Switching: Switching GPU is now much faster. Even if i use it from nvidia gui, I get the popup window asking to reboot right away. system shutdown/reboot after I switch gpu is fast. Usual 5~10 seconds, same time it takes when I am not switching gpu. Power usage - Nvidia mode: powertop reports around 30w idle (cpu load:2~3%, gpu ops/sec:0) Power usage - Intel mode: powertop reports around 20w idle (cpu load:2~3%, gpu ops/sec:0) - Device stats report usage of 100% of the Nvidia 1050 in powertop, not sure if accurate. I hope it helps. Cheers, Mauro -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: PRIME Power Saving mode draws too much power Status in nvidia-prime package in Ubuntu: In Progress Status in ubuntu-drivers-common package in Ubuntu: In Progress Status in nvidia-prime source package in Bionic: In Progress Status in ubuntu-drivers-common source package in Bionic: In Progress Bug description: Relying on the nouveau driver and on the vga switcheroo (to get around a change in systemd LP: #1777099) caused increased power consumption, and slowed down the switching process. Solving the problem in systemd (LP: #1777099), and adding code in gpu- manager and in nvidia-prime to unload the nvidia modules, and to allow the PCI device to sleep, dramatically decreases power consumption. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1778011/+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 1768976] Re: Ubuntu 18.04 is overheating after upgrade from 16.04
I have the same heating issue after a clean install of Ubuntu 18.04. Before that I was using Ubuntu 16.04, without this problem. Fans are more active than before and the laptop is constantly overheated, with 70-80 degrees doing nothing but only Chrome or even with the shell opened. Nvidia drivers has been removed (I can live with the integrated Intel). Kworker issue (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/887793) already fixed. This happens on a Samsung 7 Chronos NP700Z7C (CPU i7 3rd gen) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1768976 Title: Ubuntu 18.04 is overheating after upgrade from 16.04 Status in ubuntu-release-upgrader package in Ubuntu: New Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: Ubuntu is overheating at my laptop. Opening youtube on firefox is enough for critical temperature shutdown. Using lm-sensors for monitoring on 18.04 the temp varies between 70 and 85°C with only firefox or chrome open and doing nothing. On my old 16.04 with same using, the temp varies between 55 and 70°C. First thought was the driver nouveau is the problem, and finally I was able to install by add "nouveau.modeset=0" at livecd boot options, without temp shutdown. After install I disable the nouveau at modprobe blacklist, but the system continues overheating and shutdown with basic usage. I have no idea what's happening with the bionic at my laptop. My laptop is a Samsung RF411 i5 2nd Generation and Geforce 540M. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.17 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu May 3 16:22:40 2018 InstallationDate: Installed on 2018-04-27 (6 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptHistorylog: Start-Date: 2018-04-27 15:46:02 End-Date: 2018-04-27 15:46:02 VarLogDistupgradeAptlog: Log time: 2018-04-27 15:45:39.753331 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done Log time: 2018-04-27 15:46:04.859979 VarLogDistupgradeApttermlog: Log started: 2018-04-27 15:46:02 Log ended: 2018-04-27 15:46:02 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1768976/+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 1767606] [NEW] GDM do not start on freshly installed 18.04
Public bug reported: After a fresh install of the final Ubuntu 18.04 the boot process hangs after GDM call (the login screen does not appear). After a few tests I realized that editing /etc/gdm3/custom.conf and removing the comment before "WaylandEnable=false" make the booting working again (with the wayland session option not available in GDM). I also tried using lightdm. In this case the login screen appears and I can choose xorg or wayland session from there. The latter (wayland) does not work and the system hangs on a black screen. This is also weird as the wayland session used to work flawlessly on the very same machine on 17.10. I don't need the wayland session but just found weird that system cannot start the login screen out-of-the-box and gdm does not automatically fallback. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 28 11:04:18 2018 InstallationDate: Installed on 2018-04-27 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2018-04-28T10:40:22.176527 ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1767606 Title: GDM do not start on freshly installed 18.04 Status in gdm3 package in Ubuntu: New Bug description: After a fresh install of the final Ubuntu 18.04 the boot process hangs after GDM call (the login screen does not appear). After a few tests I realized that editing /etc/gdm3/custom.conf and removing the comment before "WaylandEnable=false" make the booting working again (with the wayland session option not available in GDM). I also tried using lightdm. In this case the login screen appears and I can choose xorg or wayland session from there. The latter (wayland) does not work and the system hangs on a black screen. This is also weird as the wayland session used to work flawlessly on the very same machine on 17.10. I don't need the wayland session but just found weird that system cannot start the login screen out-of-the-box and gdm does not automatically fallback. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 28 11:04:18 2018 InstallationDate: Installed on 2018-04-27 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2018-04-28T10:40:22.176527 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1767606/+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 1686189] Re: External monitor connecting problem on Intel graphics card
quick update. Although the VGA cable I used with the intel chipset was working fine with other laptop/monitor telling me ihe cable is 'fine', it happen I tried a different VGA cable and this time everything work fine. So far I suppose it is a cable pin out problem I'll be happy to provide more info if required thanks -- 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/1686189 Title: External monitor connecting problem on Intel graphics card Status in linux package in Ubuntu: Fix Released Status in xorg package in Ubuntu: Confirmed Bug description: I am facing a problem with Intel Graphics driver. I have external monitor and in display settings the second monitor is detecting but it's not working, so could you email me a solution. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 Uname: Linux 4.4.25-040425-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Apr 25 21:45:16 2017 DistUpgraded: 2017-04-25 21:07:40,819 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-75-generic, x86_64: installed GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05e9] InstallationDate: Installed on 2017-04-25 (0 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) MachineType: Dell Inc. Inspiron 3537 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.25-040425-generic root=UUID=3914e6d5-5c87-4816-8043-776ef4184d29 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2017-04-25 (0 days ago) dmi.bios.date: 04/30/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 03JPPR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A08 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/30/2014:svnDellInc.:pnInspiron3537:pvrA08:rvnDellInc.:rn03JPPR:rvrA00:cvnDellInc.:ct8:cvrA08: dmi.product.name: Inspiron 3537 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue Apr 25 21:37:24 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 17900 vendor AUO xserver.version: 2:1.18.4-0ubuntu0.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686189/+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 1686189] Re: External monitor connecting problem on Intel graphics card
I tried to remove but if I do also this packeges will e removed - lubuntu-core - lubuntu-desktop So I did apt-get install --reinstal xserver-xorg-video-intel but nothing has changed. If I plug in the VGA and open a window I can see that the system see the monitor anch I can set via the 'monitor setting' what to show where but the PC input of the TV doesn't highlight and can't connect/show remotely Please advise if we need to open a new bug with this chipset rather than continue here. -- 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/1686189 Title: External monitor connecting problem on Intel graphics card Status in linux package in Ubuntu: Fix Released Status in xorg package in Ubuntu: Confirmed Bug description: I am facing a problem with Intel Graphics driver. I have external monitor and in display settings the second monitor is detecting but it's not working, so could you email me a solution. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 Uname: Linux 4.4.25-040425-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Apr 25 21:45:16 2017 DistUpgraded: 2017-04-25 21:07:40,819 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-75-generic, x86_64: installed GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05e9] InstallationDate: Installed on 2017-04-25 (0 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) MachineType: Dell Inc. Inspiron 3537 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.25-040425-generic root=UUID=3914e6d5-5c87-4816-8043-776ef4184d29 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2017-04-25 (0 days ago) dmi.bios.date: 04/30/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 03JPPR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A08 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/30/2014:svnDellInc.:pnInspiron3537:pvrA08:rvnDellInc.:rn03JPPR:rvrA00:cvnDellInc.:ct8:cvrA08: dmi.product.name: Inspiron 3537 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue Apr 25 21:37:24 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 17900 vendor AUO xserver.version: 2:1.18.4-0ubuntu0.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686189/+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 1686189] Re: External monitor connecting problem on Intel graphics card
THis is the result with dmesg | grep intel [1.987610] intel_idle: MWAIT substates: 0x20220 [1.987629] intel_idle: v0.4.1 model 0x1C [1.987634] intel_idle: lapic_timer_reliable_states 0x2 [2.013276] agpgart-intel :00:00.0: Intel 945GME Chipset [2.013330] agpgart-intel :00:00.0: detected gtt size: 262144K total, 262144K mappable [2.013427] agpgart-intel :00:00.0: detected 8192K stolen memory [2.013765] agpgart-intel :00:00.0: AGP aperture is 256M @ 0xd000 [3.378181] fb: switching to inteldrmfb from VESA VGA [3.808471] WARNING: CPU: 0 PID: 6 at /build/linux-0c7Pc_/linux-4.4.0/drivers/gpu/drm/i915/intel_fbdev.c:406 intel_fb_initial_config+0x2d4/0x5f0 [i915]() [3.808696] [] ? intel_fb_initial_config+0x2d4/0x5f0 [i915] [3.808796] [] ? intel_fb_initial_config+0x2d4/0x5f0 [i915] [3.808904] [] intel_fb_initial_config+0x2d4/0x5f0 [i915] [3.809006] [] ? intel_crtc_fb_gamma_get+0x40/0x40 [i915] [3.809198] [] ? intel_fbdev_init+0x530/0x530 [i915] [3.809298] [] intel_fbdev_initial_config+0x19/0x20 [i915] [3.812450] fbcon: inteldrmfb (fb0) is primary device [3.812844] i915 :00:02.0: fb0: inteldrmfb frame buffer device [3.832514] WARNING: CPU: 0 PID: 87 at /build/linux-0c7Pc_/linux-4.4.0/drivers/gpu/drm/i915/intel_fbdev.c:406 intel_fb_initial_config+0x2d4/0x5f0 [i915]() [3.832759] [] ? intel_fb_initial_config+0x2d4/0x5f0 [i915] [3.832859] [] ? intel_fb_initial_config+0x2d4/0x5f0 [i915] [3.832967] [] intel_fb_initial_config+0x2d4/0x5f0 [i915] [3.833069] [] ? intel_crtc_fb_gamma_get+0x40/0x40 [i915] [3.84] [] intel_fbdev_output_poll_changed+0x1a/0x20 [i915] [3.834328] [] ? intel_pre_plane_update+0xd8/0x130 [i915] [3.834428] [] intel_atomic_commit+0x52f/0x6a0 [i915] [3.834988] [] intel_fbdev_output_poll_changed+0x1a/0x20 [i915] [ 16.748840] intel_rng: FWH not detected [ 19.441617] intel_powerclamp: No package C-state available at the 4th line I found that I have Intel 945GME Chipset and not I915 as referred later on in dmesg. does it effect this thread? cheers -- 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/1686189 Title: External monitor connecting problem on Intel graphics card Status in linux package in Ubuntu: Fix Released Status in xorg package in Ubuntu: Confirmed Bug description: I am facing a problem with Intel Graphics driver. I have external monitor and in display settings the second monitor is detecting but it's not working, so could you email me a solution. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 Uname: Linux 4.4.25-040425-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Apr 25 21:45:16 2017 DistUpgraded: 2017-04-25 21:07:40,819 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-75-generic, x86_64: installed GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05e9] InstallationDate: Installed on 2017-04-25 (0 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) MachineType: Dell Inc. Inspiron 3537 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.25-040425-generic root=UUID=3914e6d5-5c87-4816-8043-776ef4184d29 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2017-04-25 (0 days ago) dmi.bios.date: 04/30/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 03JPPR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A08 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/30/2014:svnDellInc.:pnInspiron3537:pvrA08:rvnDellInc.:rn03JPPR:rvrA00:cvnDellInc.:ct8:cvrA08: dmi.product.name: Inspiron 3537 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati:
[Desktop-packages] [Bug 1686189] Re: External monitor connecting problem on Intel graphics card
Yes, I do. I have this problem only with some monitors / TV. -- 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/1686189 Title: External monitor connecting problem on Intel graphics card Status in linux package in Ubuntu: Fix Released Status in xorg package in Ubuntu: Confirmed Bug description: I am facing a problem with Intel Graphics driver. I have external monitor and in display settings the second monitor is detecting but it's not working, so could you email me a solution. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 Uname: Linux 4.4.25-040425-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Apr 25 21:45:16 2017 DistUpgraded: 2017-04-25 21:07:40,819 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-75-generic, x86_64: installed GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05e9] InstallationDate: Installed on 2017-04-25 (0 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) MachineType: Dell Inc. Inspiron 3537 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.25-040425-generic root=UUID=3914e6d5-5c87-4816-8043-776ef4184d29 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2017-04-25 (0 days ago) dmi.bios.date: 04/30/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 03JPPR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A08 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/30/2014:svnDellInc.:pnInspiron3537:pvrA08:rvnDellInc.:rn03JPPR:rvrA00:cvnDellInc.:ct8:cvrA08: dmi.product.name: Inspiron 3537 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue Apr 25 21:37:24 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 17900 vendor AUO xserver.version: 2:1.18.4-0ubuntu0.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686189/+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 1686189] Re: External monitor connecting problem on Intel graphics card
Hi there, I'm facing still this problem with kernel 4.4.0-116-generic Any documentation I can post to help? Dmesg? thanks -- 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/1686189 Title: External monitor connecting problem on Intel graphics card Status in linux package in Ubuntu: Fix Released Status in xorg package in Ubuntu: Confirmed Bug description: I am facing a problem with Intel Graphics driver. I have external monitor and in display settings the second monitor is detecting but it's not working, so could you email me a solution. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 Uname: Linux 4.4.25-040425-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Apr 25 21:45:16 2017 DistUpgraded: 2017-04-25 21:07:40,819 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-75-generic, x86_64: installed GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05e9] InstallationDate: Installed on 2017-04-25 (0 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) MachineType: Dell Inc. Inspiron 3537 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.25-040425-generic root=UUID=3914e6d5-5c87-4816-8043-776ef4184d29 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2017-04-25 (0 days ago) dmi.bios.date: 04/30/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 03JPPR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A08 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/30/2014:svnDellInc.:pnInspiron3537:pvrA08:rvnDellInc.:rn03JPPR:rvrA00:cvnDellInc.:ct8:cvrA08: dmi.product.name: Inspiron 3537 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue Apr 25 21:37:24 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 17900 vendor AUO xserver.version: 2:1.18.4-0ubuntu0.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686189/+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 1491787] Re: Gnome's Activities Overview search is always in English, regardless of the system language
Today I was testing the live session of Fedora 26 (Gnome 3.24) and this bug is not present there. After setting the localization and restarting the session, settings and search are translated correctly as supposed. I hope this could help to address the problem. -- 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/1491787 Title: Gnome's Activities Overview search is always in English, regardless of the system language Status in Ubuntu GNOME: New Status in Ubuntu Translations: New Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: Hey, I'm referring to this issue on AskUbuntu: http://askubuntu.com/questions/600656/change-language-of-the-gnome- shell-overview On my Ubuntu Gnome 15.04 system all entries from the gnome-control- center are shown in English in the Gnome-Shell overview (see screenshot in the above mentioned link), even though my system language is German. The entries in the gnome-control-center itself are however in German. Is this due to a bug or missing translations? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1491787/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725315] Re: evolution crashed with SIGSEGV in g_hash_table_lookup_node()
Per comment #9, I confirm it only happens on gnome-shell on wayland mode. I tested thoroughly over the last few days and I did not experience a single crash on gnome-shell on Xorg.Once I switch back to gnome-shell on wayland, the frequent crashes start happening again. Per comment #10, I tested the workaround: uninstall evolution-indicator package, and I confirm it works. No more evolution crashes on gnome- shell on wayland. PS I ran the tests mentioned above on 2 machines: on Virtualbox VM, and on Hardware. Same results on both. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1725315 Title: evolution crashed with SIGSEGV in g_hash_table_lookup_node() Status in evolution package in Ubuntu: Confirmed Bug description: Every few minutes, evolution exits the desktop. Sometimes it will only stay up for seconds, and sometimes it exits in the first second. Occasionally it stays up for ~20 minutes. When it is running, it seems to function normally. This machine was upgraded from 17.04 (where Evolution was stable) to 17.10 release. Apport crashdump analysis attached. Looking at /var/log/syslog after one of these crashes, I see the following entries: Oct 20 09:50:00 es-lzz-det470s org.gnome.Shell.desktop[2287]: /usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error: invalid string constant "murrine-scrollbar", expected valid string constant Oct 20 09:50:00 es-lzz-det470s org.gnome.Shell.desktop[2287]: [Parent 8840] WARNING: pipe error (254): Connection reset by peer: file /build/firefox-9cfKiA/firefox-56.0+build6/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 353 Oct 20 09:50:52 es-lzz-det470s org.gnome.Shell.desktop[2287]: [Parent 8840] WARNING: pipe error (287): Connection reset by peer: file /build/firefox-9cfKiA/firefox-56.0+build6/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 353 Oct 20 09:50:52 es-lzz-det470s org.gnome.Shell.desktop[2287]: [Parent 8840] WARNING: pipe error (300): Connection reset by peer: file /build/firefox-9cfKiA/firefox-56.0+build6/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 353 Oct 20 09:50:52 es-lzz-det470s org.gnome.Shell.desktop[2287]: [Parent 8840] WARNING: pipe error (417): Connection reset by peer: file /build/firefox-9cfKiA/firefox-56.0+build6/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 353 Oct 20 09:50:57 es-lzz-det470s kernel: [88013.689438] evolution[1461]: segfault at 0 ip (null) sp 7ffee4f96718 error 14 in evolution[557e54c52000+7000] It is not clear that the first few syslog entries are related. Running evolution with debugging enabled: CAMEL_DEBUG=all evolution I see the following output when the crash occurs: ### message_list_regen_thread: got 1521 uids in folder 0x5615e38015f0 (john.mel...@esentire.com : Inbox) for expression:---(and (match-all (and (not (system-flag "deleted")) (not (system-flag "junk" (and (and (match-all (not (or (= (user-tag "label") "important") (user-flag "$Labelimportant") (user-flag "important" (match-all (not (or (= (user-tag "label") "work") (user-flag "$Labelwork") (user-flag "work" (match-all (not (or (= (user-tag "label") "personal") (user-flag "$Labelpersonal") (user-flag "personal" (match-all (not (or (= (user-tag "label") "todo") (user-flag "$Labeltodo") (user-flag "todo" (match-all (not (or (= (user-tag "label") "later") (user-flag "$Labellater") (user-flag "later")))--- message_list_regen_thread: got 1521 uids in folder 0x5615e38015f0 (john.mel...@esentire.com : Inbox) after tweak, hide_deleted:1, hide_junk:1 Segmentation fault (core dumped) Not sure if I can provide further information. This crash is highly- repeatable, happening hundreds of times/day. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: evolution 3.26.1-1 ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4 Uname: Linux 4.13.0-16-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 20 09:50:57 2017 Disassembly: => 0x0: Cannot access memory at address 0x0 ExecutablePath: /usr/bin/evolution InstallationDate: Installed on 2017-05-31 (142 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcCmdline: evolution -c current ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x0: Cannot access memory at address 0x0 PC (0x) not located in a known VMA region (needed executable region)! SegvReason: executing NULL VMA Signal: 11 SourcePackage: evolution StacktraceTop: ?? () g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 gdk_x11_atom_to_xatom_for_display ()
[Desktop-packages] [Bug 1491787] Re: System language isn't applied to gnome-control-center in Gnome-Shell
My personal opinion is that the bug nature, its details and effect on gnome-shell are clearly outlined now. I am not a developer and certainly not in the position to evaluate a bug importance or its priority. Unless a patch is proposed, simple complaining does not help. Likely, as more users move to GNOME, the bug would gather higher priority as an effect of more people being affected. -- 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/1491787 Title: System language isn't applied to gnome-control-center in Gnome-Shell Status in Ubuntu GNOME: New Status in Ubuntu Translations: New Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: Hey, I'm referring to this issue on AskUbuntu: http://askubuntu.com/questions/600656/change-language-of-the-gnome- shell-overview On my Ubuntu Gnome 15.04 system all entries from the gnome-control- center are shown in English in the Gnome-Shell overview (see screenshot in the above mentioned link), even though my system language is German. The entries in the gnome-control-center itself are however in German. Is this due to a bug or missing translations? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1491787/+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 1491787] Re: System language isn't applied to gnome-control-center in Gnome-Shell
I agree. Although this is not a critical bug and I could decide to
switch to an English locale, it still is a major limitation for non-
English speaking users ruining their Gnome shell workflow. Just
consider, as an example the attached screenshots of "Impostazioni"
window ("Settings"). If one wants to quickly open the "Sfondo"
(background) tab using +string through the search bar he has to
remember to digit "background" to obtain any results. The same applies
to "Energia" (digit "power").
** Attachment added: "example of search for background in italian locale"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1491787/+attachment/5000296/+files/photo_2017-10-30_19-47.jpg
--
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/1491787
Title:
System language isn't applied to gnome-control-center in Gnome-Shell
Status in Ubuntu GNOME:
New
Status in gnome-control-center package in Ubuntu:
Confirmed
Bug description:
Hey,
I'm referring to this issue on AskUbuntu:
http://askubuntu.com/questions/600656/change-language-of-the-gnome-
shell-overview
On my Ubuntu Gnome 15.04 system all entries from the gnome-control-
center are shown in English in the Gnome-Shell overview (see
screenshot in the above mentioned link), even though my system
language is German. The entries in the gnome-control-center itself are
however in German.
Is this due to a bug or missing translations?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1491787/+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 1491787] Re: System language isn't applied to gnome-control-center in Gnome-Shell
I also experience the same bug in freshly installed Artful (17.10). Italian locale is set but items from settings are displayed in english and application search seems to be based on english keywords. ** Tags added: artful -- 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/1491787 Title: System language isn't applied to gnome-control-center in Gnome-Shell Status in Ubuntu GNOME: New Status in gnome-control-center package in Ubuntu: Confirmed Bug description: Hey, I'm referring to this issue on AskUbuntu: http://askubuntu.com/questions/600656/change-language-of-the-gnome- shell-overview On my Ubuntu Gnome 15.04 system all entries from the gnome-control- center are shown in English in the Gnome-Shell overview (see screenshot in the above mentioned link), even though my system language is German. The entries in the gnome-control-center itself are however in German. Is this due to a bug or missing translations? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1491787/+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 1677198] Re: OpenVPN not Working in 17.04 via "Import a saved VPN configuration"
Hello, I had my share of issues with network-manager-openvpn, especially with profiles exported from pfsense appliances, as those tend to inline some configurations. I remember I had issues with Ubuntu 17.04 and 16.04 but as I am testing now, it seems all profiles I have can be imported and used. If you can share your configuration I might be able to help and run some tests. you can hide your certificate files and hostname. Tested on Ubuntu 17.04 - no issue network-manager-openvpn and network-manager-openvpn-gnome 1.2.6-2ubuntu1 Tested on Ubuntu 17.10 - no issue network-manager-openvpn and network-manager-openvpn-gnome 1.2.6-2ubuntu1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1677198 Title: OpenVPN not Working in 17.04 via "Import a saved VPN configuration" Status in NetworkManager: New Status in network-manager-openvpn package in Ubuntu: Confirmed Bug description: I can definitely confirm that Network Manager's OpenVPN is not working yet in Ubuntu 17.04. I set up my configuration via import: http://neartalk.com/ss/2017-03-29_001_633x332.png On all earlier versions of Ubuntu, after importing the configuration, I'm able to connect to the VPN. However, in 17.04, connection attempts always give this error immediately: "The VPN Connection disconnected because the VPN Service has stopped" Clearly the VPN Service has NOT stopped. I've confirmed that this error is false by taking the exact same import-file and I imported it into an Ubuntu 16.04 computer and then the VPN connected without issue. Also, with this same import-file I've had no issues in Ubuntu 16.10. So I've thoroughly confirmed that there is no issue with the VPN service. The issue is with the client in Ubuntu 17.04. I cannot upgrade to 17.04 until this is fixed. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: network-manager-openvpn-gnome 1.2.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Wed Mar 29 05:25:14 2017 InstallationDate: Installed on 2017-01-30 (58 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: network-manager-openvpn UpgradeStatus: Upgraded to zesty on 2017-03-27 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1677198/+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 1701424] [NEW] package tk8.6-blt2.5 2.5.3+dfsg-3 failed to install/upgrade: O pacote está num estado de inconsistência muito mau; deve reinstalá-lo antes de tentar a remoção.
Public bug reported: I can't install anything on my terminal. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: tk8.6-blt2.5 2.5.3+dfsg-3 ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-56-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Thu Jun 29 23:34:39 2017 DpkgTerminalLog: dpkg: erro ao processar o pacote tk8.6-blt2.5 (--remove): O pacote está num estado de inconsistência muito mau; deve reinstalá-lo antes de tentar a remoção. ErrorMessage: O pacote está num estado de inconsistência muito mau; deve reinstalá-lo antes de tentar a remoção. InstallationDate: Installed on 2017-04-13 (77 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: blt Title: package tk8.6-blt2.5 2.5.3+dfsg-3 failed to install/upgrade: O pacote está num estado de inconsistência muito mau; deve reinstalá-lo antes de tentar a remoção. UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: blt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to blt in Ubuntu. https://bugs.launchpad.net/bugs/1701424 Title: package tk8.6-blt2.5 2.5.3+dfsg-3 failed to install/upgrade: O pacote está num estado de inconsistência muito mau; deve reinstalá-lo antes de tentar a remoção. Status in blt package in Ubuntu: New Bug description: I can't install anything on my terminal. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: tk8.6-blt2.5 2.5.3+dfsg-3 ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-56-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Thu Jun 29 23:34:39 2017 DpkgTerminalLog: dpkg: erro ao processar o pacote tk8.6-blt2.5 (--remove): O pacote está num estado de inconsistência muito mau; deve reinstalá-lo antes de tentar a remoção. ErrorMessage: O pacote está num estado de inconsistência muito mau; deve reinstalá-lo antes de tentar a remoção. InstallationDate: Installed on 2017-04-13 (77 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: blt Title: package tk8.6-blt2.5 2.5.3+dfsg-3 failed to install/upgrade: O pacote está num estado de inconsistência muito mau; deve reinstalá-lo antes de tentar a remoção. UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/blt/+bug/1701424/+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 1208993] Re: Ubuntu slows down and hangs while copying file from/to USB
I think this bug report is a bit messy, because it mixes two different issues. I think that the original problem is the one I'm experiencing and that is perfectly described by the StackExchange answer pointed to by Peter Stevenson's comment #45. Indeed, setting dirty_background_bytes and dirty_bytes to low values is the only way to fix the problem in my case. Either using low vm.dirty_background_ratio and vm.dirty_ratio or changing the scheduler to deadline does nothing in my case (by the way, the suggested low values for vm.dirty_*_ratio parameters seems to have become the default at least in recent Trusty updates). The problem described here is not just that the system is slow at copying many files, but that it stutters and completely freezes (mouse pointer included) for whole seconds, if not even minutes (last time I had to leave my PC for about 10 minutes to let a huge file transfer terminate and be able to even move the mouse pointer again... many other times I simply switched off the system and restarted). This happens when copying huge files (some gigabytes in size) to a relatively slow device, which might by a USB drive or a network drive (when using WiFi, for instance). And, even if the aforementioned reply and referenced pages talk about this happening on systems with a lot of RAM, in my case it happens even if I have only 4 GB of RAM. Anyway, it's sad to see no words at all from any Ubuntu developer on this bug report, given that it seems to be a well known kernel issue, unless I missed something. -- 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/1208993 Title: Ubuntu slows down and hangs while copying file from/to USB Status in nautilus package in Ubuntu: Confirmed Bug description: Hi While copying many and large files to and from a USB drive, the system becomes incredibly slow and sometimes hangs. I watched the system monitor while it was running slowly but cpu was not above 50% at any time, the same for memory. I'm using the "WD my passport" HD with a USB3 port of my "ASUS K55VD" laptop. Description: Ubuntu 13.04 Release: 13.04 nautilus: Installed: 1:3.6.3-0ubuntu16 Candidate: 1:3.6.3-0ubuntu16 Version table: *** 1:3.6.3-0ubuntu16 0 500 http://ubuntu-archive.mirror.nucleus.be/ raring/main amd64 Packages 100 /var/lib/dpkg/status Steps to reproduce: 1) Aquire many large files (like your totally legit moviecollection) 2) Copy files to external HD 3) Open your browser and be sad when your system becomes incredibly slow after a few minutes This is my first bugreport so if I'm missing something, please tell me. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: nautilus 1:3.6.3-0ubuntu16 ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4 Uname: Linux 3.8.0-27-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 Date: Tue Aug 6 22:56:34 2013 EcryptfsInUse: Yes ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'656x715+154+151'" b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2013-05-31 (67 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True 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/1208993/+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 1670117] [NEW] Updates has a very visible issue in downloads list and command log
Public bug reported: It is almost unbeliveable to me, that this problem just passed your tests for the entire 16.10 cycle and it is still present in 17.04 beta1 Now you have the chance to: 1) See it (you just need to expand the lower pane of update-manager) 2) Correct it before 17.04 release Mauro Rossi ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New ** Package changed: gnome-session (Ubuntu) => update-manager (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1670117 Title: Updates has a very visible issue in downloads list and command log Status in update-manager package in Ubuntu: New Bug description: It is almost unbeliveable to me, that this problem just passed your tests for the entire 16.10 cycle and it is still present in 17.04 beta1 Now you have the chance to: 1) See it (you just need to expand the lower pane of update-manager) 2) Correct it before 17.04 release Mauro Rossi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1670117/+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 1208993] Re: Ubuntu slows down and hangs while copying file from/to USB
I also experience this problem on Linux Mint 17.3 KDE (based on Ubuntu 14.04), copying through the KDE I/O subsystem (Dolphin or Krusader). So, I think Nautilus (which shows in the "Affects" field) is just a victim. I have a notebook (HP ProBook 450 G1) with 4 GB RAM. I was thinking it might have been a problem with my laptop chipset (some sort of a bus saturation problem), but I see many have the same problem and that there's a workaround (I'll try as soon as possible). Any official statement from Ubuntu developers? -- 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/1208993 Title: Ubuntu slows down and hangs while copying file from/to USB Status in nautilus package in Ubuntu: Confirmed Bug description: Hi While copying many and large files to and from a USB drive, the system becomes incredibly slow and sometimes hangs. I watched the system monitor while it was running slowly but cpu was not above 50% at any time, the same for memory. I'm using the "WD my passport" HD with a USB3 port of my "ASUS K55VD" laptop. Description: Ubuntu 13.04 Release: 13.04 nautilus: Installed: 1:3.6.3-0ubuntu16 Candidate: 1:3.6.3-0ubuntu16 Version table: *** 1:3.6.3-0ubuntu16 0 500 http://ubuntu-archive.mirror.nucleus.be/ raring/main amd64 Packages 100 /var/lib/dpkg/status Steps to reproduce: 1) Aquire many large files (like your totally legit moviecollection) 2) Copy files to external HD 3) Open your browser and be sad when your system becomes incredibly slow after a few minutes This is my first bugreport so if I'm missing something, please tell me. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: nautilus 1:3.6.3-0ubuntu16 ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4 Uname: Linux 3.8.0-27-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 Date: Tue Aug 6 22:56:34 2013 EcryptfsInUse: Yes ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'656x715+154+151'" b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2013-05-31 (67 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True 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/1208993/+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 913434] Re: ImageIO crashes (core dumped) while reading many image files
Thank you Tjago, I will monitor upstream too! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lcms2 in Ubuntu. https://bugs.launchpad.net/bugs/913434 Title: ImageIO crashes (core dumped) while reading many image files Status in OpenJDK: Fix Released Status in lcms2 package in Ubuntu: Incomplete Status in openjdk-7 package in Ubuntu: Incomplete Bug description: Code that uses ImageIO.read() to read many image files (on my system: 270 files, totalling 522.9 MiB) crashes the JVM. ~~~ My system information: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 11.10 Release: 11.10 Codename: oneiric $ uname -a Linux dowah 3.0.0-14-generic #23-Ubuntu SMP Mon Nov 21 20:28:43 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux $ javac -version javac 1.7.0_147 $ java -version java version "1.7.0_147-icedtea" ~~~ To reproduce the error: $ javac BugIIO.java $ ulimit -c unlimited # to enable core dump $ java BugIIO ~~~ Terminal output that signifies the error: # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x7fb5babe31f8, pid=4978, tid=140418842154752 # # JRE version: 7.0_147-b147 # Java VM: OpenJDK 64-Bit Server VM (21.0-b17 mixed mode linux-amd64 compressed oops) # Derivative: IcedTea7 2.0 # Distribution: Ubuntu 11.10, package 7~b147-2.0-0ubuntu0.11.10.1 # Problematic frame: # C [liblcms2.so.2+0x121f8] cmsSaveProfileToIOhandler+0x38 # # Core dump written. Default location: /home/joshua/core or core.4978 # # An error report file with more information is saved as: # /home/joshua/hs_err_pid4978.log # # If you would like to submit a bug report, please include # instructions on how to reproduce the bug and visit: # https://bugs.launchpad.net/ubuntu/+source/openjdk-7/ # Dibatalkan (core didump) ~~~ PS When I tried to compile BugIIO.java on openjdk-6 and run it on openjdk-6, the program finishes normally (no crash). To clarify: 1. This bug affect OpenJDK 7 (7~b147-2.0-0ubuntu0.11.10.1) (tested on oneiric). 2. This bug does *not* affect OpenJDK 6 (6b23~pre11-0ubuntu1.11.10) (tested on oneiric). To manage notifications about this bug go to: https://bugs.launchpad.net/openjdk/+bug/913434/+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 913434] Re: ImageIO crashes (core dumped) while reading many image files
Just an additional note: this happened with openjdk-7-7u95-2.6.4 (with IcedTea 2.6.4), I installed 7u101 only today, but I saw there's no version change in liblcms2-2 (still 2.5), which seems to be the root cause of this problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lcms2 in Ubuntu. https://bugs.launchpad.net/bugs/913434 Title: ImageIO crashes (core dumped) while reading many image files Status in OpenJDK: Fix Released Status in lcms2 package in Ubuntu: Incomplete Status in openjdk-7 package in Ubuntu: Incomplete Bug description: Code that uses ImageIO.read() to read many image files (on my system: 270 files, totalling 522.9 MiB) crashes the JVM. ~~~ My system information: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 11.10 Release: 11.10 Codename: oneiric $ uname -a Linux dowah 3.0.0-14-generic #23-Ubuntu SMP Mon Nov 21 20:28:43 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux $ javac -version javac 1.7.0_147 $ java -version java version "1.7.0_147-icedtea" ~~~ To reproduce the error: $ javac BugIIO.java $ ulimit -c unlimited # to enable core dump $ java BugIIO ~~~ Terminal output that signifies the error: # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x7fb5babe31f8, pid=4978, tid=140418842154752 # # JRE version: 7.0_147-b147 # Java VM: OpenJDK 64-Bit Server VM (21.0-b17 mixed mode linux-amd64 compressed oops) # Derivative: IcedTea7 2.0 # Distribution: Ubuntu 11.10, package 7~b147-2.0-0ubuntu0.11.10.1 # Problematic frame: # C [liblcms2.so.2+0x121f8] cmsSaveProfileToIOhandler+0x38 # # Core dump written. Default location: /home/joshua/core or core.4978 # # An error report file with more information is saved as: # /home/joshua/hs_err_pid4978.log # # If you would like to submit a bug report, please include # instructions on how to reproduce the bug and visit: # https://bugs.launchpad.net/ubuntu/+source/openjdk-7/ # Dibatalkan (core didump) ~~~ PS When I tried to compile BugIIO.java on openjdk-6 and run it on openjdk-6, the program finishes normally (no crash). To clarify: 1. This bug affect OpenJDK 7 (7~b147-2.0-0ubuntu0.11.10.1) (tested on oneiric). 2. This bug does *not* affect OpenJDK 6 (6b23~pre11-0ubuntu1.11.10) (tested on oneiric). To manage notifications about this bug go to: https://bugs.launchpad.net/openjdk/+bug/913434/+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 913434] Re: ImageIO crashes (core dumped) while reading many image files
Hi Tiago! I don't know if it's reproducible, today our web application suddenly was offline because the OpenJDK JVM process running Tomcat had died with a crash. I'm attaching the dump. It's the first time this happens. If it's a concurrency issue, it's really hard to say whether it will happen again and when. I don't know if it affects OpenJDK 6 as well, because this web application needs Java 7 to run, so I can't run it with OpenJDK 6. I determined it was the same bug because the topmost frames of the dump seems exactly those reported here. ** Attachment added: "Dump created by the JVM" https://bugs.launchpad.net/ubuntu/+source/openjdk-7/+bug/913434/+attachment/4664787/+files/hs_err_pid5679.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lcms2 in Ubuntu. https://bugs.launchpad.net/bugs/913434 Title: ImageIO crashes (core dumped) while reading many image files Status in OpenJDK: Fix Released Status in lcms2 package in Ubuntu: Incomplete Status in openjdk-7 package in Ubuntu: Incomplete Bug description: Code that uses ImageIO.read() to read many image files (on my system: 270 files, totalling 522.9 MiB) crashes the JVM. ~~~ My system information: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 11.10 Release: 11.10 Codename: oneiric $ uname -a Linux dowah 3.0.0-14-generic #23-Ubuntu SMP Mon Nov 21 20:28:43 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux $ javac -version javac 1.7.0_147 $ java -version java version "1.7.0_147-icedtea" ~~~ To reproduce the error: $ javac BugIIO.java $ ulimit -c unlimited # to enable core dump $ java BugIIO ~~~ Terminal output that signifies the error: # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x7fb5babe31f8, pid=4978, tid=140418842154752 # # JRE version: 7.0_147-b147 # Java VM: OpenJDK 64-Bit Server VM (21.0-b17 mixed mode linux-amd64 compressed oops) # Derivative: IcedTea7 2.0 # Distribution: Ubuntu 11.10, package 7~b147-2.0-0ubuntu0.11.10.1 # Problematic frame: # C [liblcms2.so.2+0x121f8] cmsSaveProfileToIOhandler+0x38 # # Core dump written. Default location: /home/joshua/core or core.4978 # # An error report file with more information is saved as: # /home/joshua/hs_err_pid4978.log # # If you would like to submit a bug report, please include # instructions on how to reproduce the bug and visit: # https://bugs.launchpad.net/ubuntu/+source/openjdk-7/ # Dibatalkan (core didump) ~~~ PS When I tried to compile BugIIO.java on openjdk-6 and run it on openjdk-6, the program finishes normally (no crash). To clarify: 1. This bug affect OpenJDK 7 (7~b147-2.0-0ubuntu0.11.10.1) (tested on oneiric). 2. This bug does *not* affect OpenJDK 6 (6b23~pre11-0ubuntu1.11.10) (tested on oneiric). To manage notifications about this bug go to: https://bugs.launchpad.net/openjdk/+bug/913434/+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 913434] Re: ImageIO crashes (core dumped) while reading many image files
This bug is marked as fixed in OpenJDK (version 2.6.2 of IcedTea should depend on LittleCMS 2.6), however in Trusty we have openjdk-7-jre- headless version 7u101-2.6.6-0ubuntu0.14.04.1 with IcedTea 2.6.6 but liblcms2-2 is still at version 2.5 (precisely 2.5-0ubuntu4.1). Does this mean that IcedTea in Trusty is using an "unsupported" version of LittleCMS? Today I faced this problem (the JVM crashed). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lcms2 in Ubuntu. https://bugs.launchpad.net/bugs/913434 Title: ImageIO crashes (core dumped) while reading many image files Status in OpenJDK: Fix Released Status in lcms2 package in Ubuntu: Confirmed Status in openjdk-7 package in Ubuntu: Confirmed Bug description: Code that uses ImageIO.read() to read many image files (on my system: 270 files, totalling 522.9 MiB) crashes the JVM. ~~~ My system information: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 11.10 Release: 11.10 Codename: oneiric $ uname -a Linux dowah 3.0.0-14-generic #23-Ubuntu SMP Mon Nov 21 20:28:43 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux $ javac -version javac 1.7.0_147 $ java -version java version "1.7.0_147-icedtea" ~~~ To reproduce the error: $ javac BugIIO.java $ ulimit -c unlimited # to enable core dump $ java BugIIO ~~~ Terminal output that signifies the error: # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x7fb5babe31f8, pid=4978, tid=140418842154752 # # JRE version: 7.0_147-b147 # Java VM: OpenJDK 64-Bit Server VM (21.0-b17 mixed mode linux-amd64 compressed oops) # Derivative: IcedTea7 2.0 # Distribution: Ubuntu 11.10, package 7~b147-2.0-0ubuntu0.11.10.1 # Problematic frame: # C [liblcms2.so.2+0x121f8] cmsSaveProfileToIOhandler+0x38 # # Core dump written. Default location: /home/joshua/core or core.4978 # # An error report file with more information is saved as: # /home/joshua/hs_err_pid4978.log # # If you would like to submit a bug report, please include # instructions on how to reproduce the bug and visit: # https://bugs.launchpad.net/ubuntu/+source/openjdk-7/ # Dibatalkan (core didump) ~~~ PS When I tried to compile BugIIO.java on openjdk-6 and run it on openjdk-6, the program finishes normally (no crash). To clarify: 1. This bug affect OpenJDK 7 (7~b147-2.0-0ubuntu0.11.10.1) (tested on oneiric). 2. This bug does *not* affect OpenJDK 6 (6b23~pre11-0ubuntu1.11.10) (tested on oneiric). To manage notifications about this bug go to: https://bugs.launchpad.net/openjdk/+bug/913434/+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 1518019] [NEW] package libreoffice-common (not installed) failed to install/upgrade: a tentar sobre-escrever '/usr/bin/soffice', que também está no pacote openoffice-debian-men
Public bug reported: não instala ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libreoffice-common (not installed) ProcVersionSignature: Ubuntu 3.13.0-68.111-generic 3.13.11-ckt27 Uname: Linux 3.13.0-68-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 Date: Thu Nov 19 15:53:25 2015 DuplicateSignature: package:libreoffice-common:(not installed):a tentar sobre-escrever '/usr/bin/soffice', que também está no pacote openoffice-debian-menus 4.1.2-9782 ErrorMessage: a tentar sobre-escrever '/usr/bin/soffice', que também está no pacote openoffice-debian-menus 4.1.2-9782 InstallationDate: Installed on 2015-09-09 (71 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) RelatedPackageVersions: dpkg 1.17.5ubuntu5.4 apt 1.0.1ubuntu2.10 SourcePackage: libreoffice Title: package libreoffice-common (not installed) failed to install/upgrade: a tentar sobre-escrever '/usr/bin/soffice', que também está no pacote openoffice-debian-menus 4.1.2-9782 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1518019 Title: package libreoffice-common (not installed) failed to install/upgrade: a tentar sobre-escrever '/usr/bin/soffice', que também está no pacote openoffice-debian-menus 4.1.2-9782 Status in libreoffice package in Ubuntu: New Bug description: não instala ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libreoffice-common (not installed) ProcVersionSignature: Ubuntu 3.13.0-68.111-generic 3.13.11-ckt27 Uname: Linux 3.13.0-68-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 Date: Thu Nov 19 15:53:25 2015 DuplicateSignature: package:libreoffice-common:(not installed):a tentar sobre-escrever '/usr/bin/soffice', que também está no pacote openoffice-debian-menus 4.1.2-9782 ErrorMessage: a tentar sobre-escrever '/usr/bin/soffice', que também está no pacote openoffice-debian-menus 4.1.2-9782 InstallationDate: Installed on 2015-09-09 (71 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) RelatedPackageVersions: dpkg 1.17.5ubuntu5.4 apt 1.0.1ubuntu2.10 SourcePackage: libreoffice Title: package libreoffice-common (not installed) failed to install/upgrade: a tentar sobre-escrever '/usr/bin/soffice', que também está no pacote openoffice-debian-menus 4.1.2-9782 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1518019/+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 1286779] Re: Please migrate libjetty-extra-java to tomcat7
This caused a regression, see bug 1508562 (sorry, I don't know how to link the two bugs, I 've opened the new one yesterday without using ubuntu-bug, I discovered this only today). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jetty in Ubuntu. https://bugs.launchpad.net/bugs/1286779 Title: Please migrate libjetty-extra-java to tomcat7 Status in One Hundred Papercuts: Fix Released Status in jetty package in Ubuntu: Fix Released Status in jetty source package in Trusty: Fix Released Status in jetty package in Debian: Fix Released Bug description: libjetty-extra-java still depends on libtomcat6-java which prevents it from being installed alongside other programs which depend on tomcat7. According to the Debian bug report, Eclipse is among these programs. (Another it causes problems for is gradle which cannot currently be installed at the same time as tomcat7. Gradle's explicit dependency on tomcat6 has been removed (see bug 997743for details) and should have fixed it, but since gradle also depends on libjetty-extra-java the issue is still present. ) SRU for 14.04, debdiff in comment #11: [Impact] It is very hard to use this package in conjuction with relevant development tools because they depend on different versions on tomcat which means you can't install both. [Test case] For instance `sudo apt-get install eclipse libjetty-extra` will fail because eclipse wants tomcat7, but libjetty-extra-java currently needs tomcat6. [Regression potential] See analysis in comment #15 - there should not be regression potential. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libjetty-extra-java 6.1.26-1ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0 Uname: Linux 3.13.0-6-generic i686 ApportVersion: 2.13.2-0ubuntu2 Architecture: i386 CurrentDesktop: Unity Date: Sun Mar 2 11:48:27 2014 InstallationDate: Installed on 2013-10-26 (127 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20131021.1) PackageArchitecture: all SourcePackage: jetty UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1286779/+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 1508562] Re: Broken symlinks for JSP support in libjetty-extra-java version 6.1.26-1ubuntu1.1
IMHO trying to use Tomcat 7 Jasper/EL implementations with Jetty 6 is not worth the effort, if it will ever work. I mean, Jetty 6 implements Servlet 2.5/JSP 2.1/EL 2.1, which are the same specification versions implemented by Tomcat 6. Tomcat 7, instead, implements Servlet 3.0/JSP 2.2/EL 2.2 specification versions, although it supports older versions, of course. If the Tomcat 7 EL implementation requires an upgrade of the EL and Servlet API jars to properly work (as I experienced when I tried to just fix the symlinks), I'm really sceptical that this can be done without causing problems like multiple conflicting versions of the same JARs in classpath or other side effects on Jetty 6 standard operations. Maybe the new APIs and corresponding Tomcat implementations are perfectly backward-compatible, but setting this up properly could be not so easy (you're actually changing the core API JARs of the servlet container). Going back to the original problem of the conflicting dependencies, I was wondering if it really is a "problem". I mean, just like you say that Tomcat 7 in Ubuntu can't be installed together with Tomcat 6, why not say that even Jetty 6 can't be installed together with Tomcat 7? We're talking about a servlet container which is EOL since Nov 2010 (see: https://wiki.eclipse.org/Jetty/Starting/Jetty_Version_Comparison_Table), so you may either: 1) remove it from recent Ubuntu/Debian official repositories 2) or just keep the old dependency and force the user to alternatively have just Jetty 6 or any other library that depends on a newer Tomcat version After all, I think that if one needs to use Jetty 6 on a recent Ubuntu (like me), it's because he needs to set up a dedicated system to run a very old application that is not worth to update to run on a newer version of Jetty (or any other recent version of another servlet container, like Tomcat). In such a scenario, having the ability to run much newer packaged software on the same system is most probably useless. The third solution might be to change the dependency against libtomcat6-java to optional: after all, Jetty can run even without JSP and EL support. The user then may choose to either a) leave these features disabled, or b) to install libtomcat6-java to enable them or c) to manually provide the required Jasper/EL JARs by himself for the same purpose, if he needs to keep the conflicting libtomcat7-java package installed instead. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jetty in Ubuntu. https://bugs.launchpad.net/bugs/1508562 Title: Broken symlinks for JSP support in libjetty-extra-java version 6.1.26-1ubuntu1.1 Status in jetty package in Ubuntu: Confirmed Status in jetty package in Debian: Unknown Bug description: Version 6.1.26-1ubuntu1.1 of libjetty-extra-java has changed the dependency for Jasper (to enable JSP support) from libtomcat6-java package to libtomcat7-java. The Jasper JAR files provided by libtomcat7-java have different names: tomcat-jasper.jar instead of jasper.jar tomcat-jasper-el.jar instead of jasper-el.jar However the symlinks provided by the libjetty-extra-java in /usr/share/jetty/lib/jsp-2.1 folder have not been updated, as they still point to /usr/share/java/jasper.jar and /usr/share/java/jasper- el.jar: hence, the symlinks are broken and Jetty starts without JSP support (even if the libjetty-extra-java package is installed). Changing the symlinks to point to the updated file names bring to NoClassDefFoundExceptions, probably because of different dependencies of Tomcat 7 Jasper libraries: [main] WARN org.mortbay.log - failed ContextHandlerCollection@37403a09: java.lang.NoClassDefFoundError: org/apache/tomcat/PeriodicEventListener [main] INFO org.mortbay.log - Opened /var/log/jetty/2015_10_21.request.log [main] WARN org.mortbay.log - failed HandlerCollection@4c3db835: java.lang.NoClassDefFoundError: org/apache/tomcat/PeriodicEventListener [main] ERROR org.mortbay.log - Error starting handlers java.lang.NoClassDefFoundError: org/apache/tomcat/PeriodicEventListener at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:643) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) at java.net.URLClassLoader.defineClass(URLClassLoader.java:277) at java.net.URLClassLoader.access$000(URLClassLoader.java:73) at java.net.URLClassLoader$1.run(URLClassLoader.java:212) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:205) at java.lang.ClassLoader.loadClass(ClassLoader.java:323) at java.lang.ClassLoader.loadClass(ClassLoader.java:268) at org.mortbay.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:401) at
[Desktop-packages] [Bug 1508562] Re: Broken symlinks for JSP support in libjetty-extra-java version 6.1.26-1ubuntu1.1
I reverted to Jetty package version 6.1.26-1ubuntu1 to solve this problem. However, that version has also another problem, as outlined by Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740596 In practice, a new symlink to /usr/share/java/tomcat-coyote.jar is needed in /usr/share/jetty/lib/jsp-2.1 to make EL work correctly. This may be considered yet another bug. Anyway, the problem described here with version 6.1.26-1ubuntu1.1 of Jetty package remains: I don't think Jetty 6 can easily be made to work with Tomcat 7 Jasper/EL implementation. ** Bug watch added: Debian Bug tracker #740596 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740596 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jetty in Ubuntu. https://bugs.launchpad.net/bugs/1508562 Title: Broken symlinks for JSP support in libjetty-extra-java version 6.1.26-1ubuntu1.1 Status in jetty package in Ubuntu: New Bug description: Version 6.1.26-1ubuntu1.1 of libjetty-extra-java has changed the dependency for Jasper (to enable JSP support) from libtomcat6-java package to libtomcat7-java. The Jasper JAR files provided by libtomcat7-java have different names: tomcat-jasper.jar instead of jasper.jar tomcat-jasper-el.jar instead of jasper-el.jar However the symlinks provided by the libjetty-extra-java in /usr/share/jetty/lib/jsp-2.1 folder have not been updated, as they still point to /usr/share/java/jasper.jar and /usr/share/java/jasper- el.jar: hence, the symlinks are broken and Jetty starts without JSP support (even if the libjetty-extra-java package is installed). Changing the symlinks to point to the updated file names bring to NoClassDefFoundExceptions, probably because of different dependencies of Tomcat 7 Jasper libraries: [main] WARN org.mortbay.log - failed ContextHandlerCollection@37403a09: java.lang.NoClassDefFoundError: org/apache/tomcat/PeriodicEventListener [main] INFO org.mortbay.log - Opened /var/log/jetty/2015_10_21.request.log [main] WARN org.mortbay.log - failed HandlerCollection@4c3db835: java.lang.NoClassDefFoundError: org/apache/tomcat/PeriodicEventListener [main] ERROR org.mortbay.log - Error starting handlers java.lang.NoClassDefFoundError: org/apache/tomcat/PeriodicEventListener at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:643) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) at java.net.URLClassLoader.defineClass(URLClassLoader.java:277) at java.net.URLClassLoader.access$000(URLClassLoader.java:73) at java.net.URLClassLoader$1.run(URLClassLoader.java:212) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:205) at java.lang.ClassLoader.loadClass(ClassLoader.java:323) at java.lang.ClassLoader.loadClass(ClassLoader.java:268) at org.mortbay.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:401) at org.mortbay.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:363) at org.mortbay.util.Loader.loadClass(Loader.java:91) at org.mortbay.util.Loader.loadClass(Loader.java:71) at org.mortbay.jetty.webapp.WebXmlConfiguration.initServlet(WebXmlConfiguration.java:510) at org.mortbay.jetty.webapp.WebXmlConfiguration.initWebXmlElement(WebXmlConfiguration.java:335) at org.mortbay.jetty.webapp.WebXmlConfiguration.initialize(WebXmlConfiguration.java:289) at org.mortbay.jetty.webapp.WebXmlConfiguration.configure(WebXmlConfiguration.java:222) at org.mortbay.jetty.webapp.WebXmlConfiguration.configureDefaults(WebXmlConfiguration.java:162) at org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1262) at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:519) at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:499) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:152) at org.mortbay.jetty.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:156) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:152) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130) at org.mortbay.jetty.Server.doStart(Server.java:224) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) at
[Desktop-packages] [Bug 1508562] Re: Broken symlinks for JSP support in libjetty-extra-java version 6.1.26-1ubuntu1.1
I got to a dead end. To try to make EL actually work, I had to change the el-api.jar symlink to point to /usr/share/java/tomcat-el-api-2.2.jar and add a new symlink to /usr/share/java/tomcat-util.jar. The next error, however, is a NoSuchMethodError caused by a conflicting Servlet API JAR. I don't think I can upgrade this without causing big troubles to Jetty 6... So, I think I must find a way to rollback to libtomcat6-java... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jetty in Ubuntu. https://bugs.launchpad.net/bugs/1508562 Title: Broken symlinks for JSP support in libjetty-extra-java version 6.1.26-1ubuntu1.1 Status in jetty package in Ubuntu: New Bug description: Version 6.1.26-1ubuntu1.1 of libjetty-extra-java has changed the dependency for Jasper (to enable JSP support) from libtomcat6-java package to libtomcat7-java. The Jasper JAR files provided by libtomcat7-java have different names: tomcat-jasper.jar instead of jasper.jar tomcat-jasper-el.jar instead of jasper-el.jar However the symlinks provided by the libjetty-extra-java in /usr/share/jetty/lib/jsp-2.1 folder have not been updated, as they still point to /usr/share/java/jasper.jar and /usr/share/java/jasper- el.jar: hence, the symlinks are broken and Jetty starts without JSP support (even if the libjetty-extra-java package is installed). Changing the symlinks to point to the updated file names bring to NoClassDefFoundExceptions, probably because of different dependencies of Tomcat 7 Jasper libraries: [main] WARN org.mortbay.log - failed ContextHandlerCollection@37403a09: java.lang.NoClassDefFoundError: org/apache/tomcat/PeriodicEventListener [main] INFO org.mortbay.log - Opened /var/log/jetty/2015_10_21.request.log [main] WARN org.mortbay.log - failed HandlerCollection@4c3db835: java.lang.NoClassDefFoundError: org/apache/tomcat/PeriodicEventListener [main] ERROR org.mortbay.log - Error starting handlers java.lang.NoClassDefFoundError: org/apache/tomcat/PeriodicEventListener at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:643) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) at java.net.URLClassLoader.defineClass(URLClassLoader.java:277) at java.net.URLClassLoader.access$000(URLClassLoader.java:73) at java.net.URLClassLoader$1.run(URLClassLoader.java:212) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:205) at java.lang.ClassLoader.loadClass(ClassLoader.java:323) at java.lang.ClassLoader.loadClass(ClassLoader.java:268) at org.mortbay.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:401) at org.mortbay.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:363) at org.mortbay.util.Loader.loadClass(Loader.java:91) at org.mortbay.util.Loader.loadClass(Loader.java:71) at org.mortbay.jetty.webapp.WebXmlConfiguration.initServlet(WebXmlConfiguration.java:510) at org.mortbay.jetty.webapp.WebXmlConfiguration.initWebXmlElement(WebXmlConfiguration.java:335) at org.mortbay.jetty.webapp.WebXmlConfiguration.initialize(WebXmlConfiguration.java:289) at org.mortbay.jetty.webapp.WebXmlConfiguration.configure(WebXmlConfiguration.java:222) at org.mortbay.jetty.webapp.WebXmlConfiguration.configureDefaults(WebXmlConfiguration.java:162) at org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1262) at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:519) at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:499) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:152) at org.mortbay.jetty.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:156) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:152) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130) at org.mortbay.jetty.Server.doStart(Server.java:224) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) at org.mortbay.xml.XmlConfiguration.main(XmlConfiguration.java:985) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at
[Desktop-packages] [Bug 1508562] Re: Broken symlinks for JSP support in libjetty-extra-java version 6.1.26-1ubuntu1.1
To fix the aforementioned NoClassDefFoundError exception, an additional symlink must be added in /usr/share/jetty/lib/jsp-2.1 pointing to /usr/share/java/tomcat-api.jar. Now Jetty starts cleanly for me and with JSP support. I haven't tested a JSP invocation yet, though. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jetty in Ubuntu. https://bugs.launchpad.net/bugs/1508562 Title: Broken symlinks for JSP support in libjetty-extra-java version 6.1.26-1ubuntu1.1 Status in jetty package in Ubuntu: New Bug description: Version 6.1.26-1ubuntu1.1 of libjetty-extra-java has changed the dependency for Jasper (to enable JSP support) from libtomcat6-java package to libtomcat7-java. The Jasper JAR files provided by libtomcat7-java have different names: tomcat-jasper.jar instead of jasper.jar tomcat-jasper-el.jar instead of jasper-el.jar However the symlinks provided by the libjetty-extra-java in /usr/share/jetty/lib/jsp-2.1 folder have not been updated, as they still point to /usr/share/java/jasper.jar and /usr/share/java/jasper- el.jar: hence, the symlinks are broken and Jetty starts without JSP support (even if the libjetty-extra-java package is installed). Changing the symlinks to point to the updated file names bring to NoClassDefFoundExceptions, probably because of different dependencies of Tomcat 7 Jasper libraries: [main] WARN org.mortbay.log - failed ContextHandlerCollection@37403a09: java.lang.NoClassDefFoundError: org/apache/tomcat/PeriodicEventListener [main] INFO org.mortbay.log - Opened /var/log/jetty/2015_10_21.request.log [main] WARN org.mortbay.log - failed HandlerCollection@4c3db835: java.lang.NoClassDefFoundError: org/apache/tomcat/PeriodicEventListener [main] ERROR org.mortbay.log - Error starting handlers java.lang.NoClassDefFoundError: org/apache/tomcat/PeriodicEventListener at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:643) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) at java.net.URLClassLoader.defineClass(URLClassLoader.java:277) at java.net.URLClassLoader.access$000(URLClassLoader.java:73) at java.net.URLClassLoader$1.run(URLClassLoader.java:212) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:205) at java.lang.ClassLoader.loadClass(ClassLoader.java:323) at java.lang.ClassLoader.loadClass(ClassLoader.java:268) at org.mortbay.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:401) at org.mortbay.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:363) at org.mortbay.util.Loader.loadClass(Loader.java:91) at org.mortbay.util.Loader.loadClass(Loader.java:71) at org.mortbay.jetty.webapp.WebXmlConfiguration.initServlet(WebXmlConfiguration.java:510) at org.mortbay.jetty.webapp.WebXmlConfiguration.initWebXmlElement(WebXmlConfiguration.java:335) at org.mortbay.jetty.webapp.WebXmlConfiguration.initialize(WebXmlConfiguration.java:289) at org.mortbay.jetty.webapp.WebXmlConfiguration.configure(WebXmlConfiguration.java:222) at org.mortbay.jetty.webapp.WebXmlConfiguration.configureDefaults(WebXmlConfiguration.java:162) at org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1262) at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:519) at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:499) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:152) at org.mortbay.jetty.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:156) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:152) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130) at org.mortbay.jetty.Server.doStart(Server.java:224) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) at org.mortbay.xml.XmlConfiguration.main(XmlConfiguration.java:985) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:622) at org.mortbay.start.Main.invokeMain(Main.java:194)
[Desktop-packages] [Bug 1508562] [NEW] Broken symlinks for JSP support in libjetty-extra-java version 6.1.26-1ubuntu1.1
Public bug reported: Version 6.1.26-1ubuntu1.1 of libjetty-extra-java has changed the dependency for Jasper (to enable JSP support) from libtomcat6-java package to libtomcat7-java. The Jasper JAR files provided by libtomcat7-java have different names: tomcat-jasper.jar instead of jasper.jar tomcat-jasper-el.jar instead of jasper-el.jar However the symlinks provided by the libjetty-extra-java in /usr/share/jetty/lib/jsp-2.1 folder have not been updated, as they still point to /usr/share/java/jasper.jar and /usr/share/java/jasper-el.jar: hence, the symlinks are broken and Jetty starts without JSP support (even if the libjetty-extra-java package is installed). Changing the symlinks to point to the updated file names bring to NoClassDefFoundExceptions, probably because of different dependencies of Tomcat 7 Jasper libraries: [main] WARN org.mortbay.log - failed ContextHandlerCollection@37403a09: java.lang.NoClassDefFoundError: org/apache/tomcat/PeriodicEventListener [main] INFO org.mortbay.log - Opened /var/log/jetty/2015_10_21.request.log [main] WARN org.mortbay.log - failed HandlerCollection@4c3db835: java.lang.NoClassDefFoundError: org/apache/tomcat/PeriodicEventListener [main] ERROR org.mortbay.log - Error starting handlers java.lang.NoClassDefFoundError: org/apache/tomcat/PeriodicEventListener at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:643) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) at java.net.URLClassLoader.defineClass(URLClassLoader.java:277) at java.net.URLClassLoader.access$000(URLClassLoader.java:73) at java.net.URLClassLoader$1.run(URLClassLoader.java:212) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:205) at java.lang.ClassLoader.loadClass(ClassLoader.java:323) at java.lang.ClassLoader.loadClass(ClassLoader.java:268) at org.mortbay.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:401) at org.mortbay.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:363) at org.mortbay.util.Loader.loadClass(Loader.java:91) at org.mortbay.util.Loader.loadClass(Loader.java:71) at org.mortbay.jetty.webapp.WebXmlConfiguration.initServlet(WebXmlConfiguration.java:510) at org.mortbay.jetty.webapp.WebXmlConfiguration.initWebXmlElement(WebXmlConfiguration.java:335) at org.mortbay.jetty.webapp.WebXmlConfiguration.initialize(WebXmlConfiguration.java:289) at org.mortbay.jetty.webapp.WebXmlConfiguration.configure(WebXmlConfiguration.java:222) at org.mortbay.jetty.webapp.WebXmlConfiguration.configureDefaults(WebXmlConfiguration.java:162) at org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1262) at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:519) at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:499) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:152) at org.mortbay.jetty.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:156) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:152) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130) at org.mortbay.jetty.Server.doStart(Server.java:224) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) at org.mortbay.xml.XmlConfiguration.main(XmlConfiguration.java:985) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:622) at org.mortbay.start.Main.invokeMain(Main.java:194) at org.mortbay.start.Main.start(Main.java:534) at org.mortbay.jetty.start.daemon.Bootstrap.start(Bootstrap.java:30) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:622) at org.apache.commons.daemon.support.DaemonLoader.start(DaemonLoader.java:243) Caused by: java.lang.ClassNotFoundException: org.apache.tomcat.PeriodicEventListener at
[Desktop-packages] [Bug 1457853] [NEW] package apport 2.17.2-0ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: Durante un aggiornamento il sistema mi segnala di non poter eseguire l'aggiornamento. ProblemType: Package DistroRelease: Ubuntu 15.04 Package: apport 2.17.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic i686 ApportLog: ApportVersion: 2.17.2-0ubuntu1.1 Architecture: i386 CrashReports: 600:0:118:276857:2015-05-22 11:19:33.174982070 +0200:2015-05-22 11:19:34.174982070 +0200:/var/crash/apport.0.crash 640:1000:118:887216:2015-05-16 21:00:39.485809979 +0200:2015-05-17 16:23:08.241841979 +0200:/var/crash/_usr_bin_openbox.1000.crash Date: Fri May 22 11:19:33 2015 DuplicateSignature: package:apport:2.17.2-0ubuntu1.1:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-05-15 (6 days ago) InstallationMedia: Lubuntu 15.04 Vivid Vervet - Release i386 (20150422) PackageArchitecture: all RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4 SourcePackage: apport Title: package apport 2.17.2-0ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 vivid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1457853 Title: package apport 2.17.2-0ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in apport package in Ubuntu: New Bug description: Durante un aggiornamento il sistema mi segnala di non poter eseguire l'aggiornamento. ProblemType: Package DistroRelease: Ubuntu 15.04 Package: apport 2.17.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic i686 ApportLog: ApportVersion: 2.17.2-0ubuntu1.1 Architecture: i386 CrashReports: 600:0:118:276857:2015-05-22 11:19:33.174982070 +0200:2015-05-22 11:19:34.174982070 +0200:/var/crash/apport.0.crash 640:1000:118:887216:2015-05-16 21:00:39.485809979 +0200:2015-05-17 16:23:08.241841979 +0200:/var/crash/_usr_bin_openbox.1000.crash Date: Fri May 22 11:19:33 2015 DuplicateSignature: package:apport:2.17.2-0ubuntu1.1:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-05-15 (6 days ago) InstallationMedia: Lubuntu 15.04 Vivid Vervet - Release i386 (20150422) PackageArchitecture: all RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4 SourcePackage: apport Title: package apport 2.17.2-0ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1457853/+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 1220426] Re: [nvidia-prime]Freeze while using touchpad
Clevo laptop, Ubuntu 14.10, NVidia GEForce GTX870M with nvidia 331.113-update driver, packages from PPA in comment #251 works fine. Bug disappeared, now touchpad+Nvidia card works withut freezes. Thanks -- 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/1220426 Title: [nvidia-prime]Freeze while using touchpad Status in X.Org X server: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Trusty: Fix Committed Bug description: Using Asus N43SL laptop as an example, with nvidia-prime installed, so the dedicated NVIDIA graphics card (GT 540m) is in use, once in a while, my screen will freeze when I use my touchpad. WORKAROUND: Use USB mouse. WORKAROUND: Uninstall nvidia-prime and use integrated graphics. WORKAROUND: Do a VT switch via Ctrl+Alt+F1 then Ctrl+Alt+F7. In the attached Xorg.0.log, you can see synaptics: ETPS/2 Elantech Touchpad: touchpad found each time I did a VT switch and regained control: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1220426/+attachment/3801516/+files/Xorg.0.log The following upstream report has a patch that addresses this issue: https://bugs.freedesktop.org/show_bug.cgi?id=86288 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1220426/+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 1220426] Re: [nvidia-prime]Freeze while using touchpad
Sorry. My apologizes to the patch author. Credits to the patch to him. -- 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/1220426 Title: [nvidia-prime]Freeze while using touchpad Status in X.Org X server: Confirmed Status in xorg-server package in Ubuntu: Triaged Bug description: Using Asus N43SL laptop as an example, with nvidia-prime installed, so the dedicated NVIDIA graphics card (GT 540m) is in use, once in a while, my screen will freeze when I use my touchpad. WORKAROUND: Use USB mouse. WORKAROUND: Uninstall nvidia-prime and use integrated graphics. WORKAROUND: Do a VT switch via Ctrl+Alt+F1 then Ctrl+Alt+F7. In the attached Xorg.0.log, you can see synaptics: ETPS/2 Elantech Touchpad: touchpad found each time I did a VT switch and regained control: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1220426/+attachment/3801516/+files/Xorg.0.log The following upstream report has a patch that addresses this issue: https://bugs.freedesktop.org/show_bug.cgi?id=86288 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1220426/+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 1220426] Re: [nvidia-prime]Freeze while using touchpad
Clevo laptop, Ubuntu 14.10, NVidia GEForce GTX870M with nvidia 331.113-update drivers (selected from system settings) plus Intel integrated graphics, same issue. VT switching and external USB mouse workarounds work. I have another Clevo laptop identical but with NVidia GEForce GTX970M instead, nouveau drivers, no freezes using touchpad. Unfortunately I cannot try nouveau on GTX870M because isn't supported. Any news about applying laurence's patch to xserver? -- 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/1220426 Title: [nvidia-prime]Freeze while using touchpad Status in X.Org X server: Confirmed Status in xorg-server package in Ubuntu: Triaged Bug description: Using Asus N43SL laptop as an example, with nvidia-prime installed, so the dedicated NVIDIA graphics card (GT 540m) is in use, once in a while, my screen will freeze when I use my touchpad. WORKAROUND: Use USB mouse. WORKAROUND: Uninstall nvidia-prime and use integrated graphics. WORKAROUND: Do a VT switch via Ctrl+Alt+F1 then Ctrl+Alt+F7. In the attached Xorg.0.log, you can see synaptics: ETPS/2 Elantech Touchpad: touchpad found each time I did a VT switch and regained control: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1220426/+attachment/3801516/+files/Xorg.0.log The following upstream report has a patch that addresses this issue: https://bugs.freedesktop.org/show_bug.cgi?id=86288 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1220426/+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 1184699] Re: Canon LIDE 110 can only scan once, then I need to replug the usb cable
I opened the following bug against SANE: https://alioth.debian.org/tracker/index.php?func=detailaid=314832 It ends that the bug was fixed after the 1.0.24 SANE release (Trusty comes with 1.0.23 and Utopic with 1.0.24). It seems like this bug was fixed in RELEASE_1_0_24-213-g92e4d96, but not on RELEASE_1_0_24 tag (on which the latest 1.0.24 tar.gz and the Ubuntu packages are based). On my own, I tested this by building from source the latest snapshot (sane-backends-git20141102) and I confirm that it seems to work reliably now! It would be great if Ubuntu could backport the fixes for Trusty and Utopic. ** Bug watch added: alioth.debian.org/ #314832 http://alioth.debian.org/support/tracker.php?aid=314832 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1184699 Title: Canon LIDE 110 can only scan once, then I need to replug the usb cable Status in Simple Scan: New Status in “sane-backends” package in Ubuntu: Confirmed Bug description: I have a Canon LIDE 110 scanner which works by default on ubuntu 13.04. The problem is after first scan, I can not scan for second time. I need to reconnect the USB cable to use the scanner again. # TEST 1 : without reconnecting the usb cable francois@pc:~$ scanimage -v test1.jpg # success scanimage: scanning image of size 636x885 pixels at 8 bits/pixel scanimage: acquiring gray frame scanimage: min/max graylevel value = 0/255 scanimage: read 562860 bytes in total # I don't unplug plug the usb cable. francois@pc:~$ scanimage -v test2.jpg # FAIL scanimage: no SANE devices found # TEST 2 : reconnect usb cable between scan attempts francois@pc:~$ scanimage -v test1.jpg # success scanimage: scanning image of size 636x885 pixels at 8 bits/pixel scanimage: acquiring gray frame scanimage: min/max graylevel value = 0/255 scanimage: read 562860 bytes in total # I unplug and replug the usb cable. francois@pc:~$ scanimage -v test2.jpg # SUCCESS scanimage: scanning image of size 636x885 pixels at 8 bits/pixel scanimage: acquiring gray frame scanimage: min/max graylevel value = 0/255 scanimage: read 562860 bytes in total francois@pc:~$ dmesg # extract [ 829.365158] usb 3-1: USB disconnect, device number 2 [ 834.935000] usb 3-1: new high-speed USB device number 4 using xhci_hcd [ 834.952515] usb 3-1: New USB device found, idVendor=04a9, idProduct=1909 [ 834.952519] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 834.952522] usb 3-1: Product: CanoScan [ 834.952524] usb 3-1: Manufacturer: Canon [ 1623.738811] usb 3-1: USB disconnect, device number 4 [ 1623.739072] xhci_hcd :00:14.0: Slot 3 endpoint 6 not removed from BW list! [ 1625.528827] usb 3-1: new high-speed USB device number 5 using xhci_hcd [ 1625.546327] usb 3-1: New USB device found, idVendor=04a9, idProduct=1909 [ 1625.546331] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 1625.546334] usb 3-1: Product: CanoScan [ 1625.546336] usb 3-1: Manufacturer: Canon francois@pc:~$ uname -a cat /etc/issue Linux pc 3.8.0-22-generic #33-Ubuntu SMP Thu May 16 15:17:14 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Ubuntu 13.04 \n \l The problem was reported here by someone else : http://askubuntu.com/questions/278473/canon-lide-110-should-reconnect- usb-for-each-scan Thanks François To manage notifications about this bug go to: https://bugs.launchpad.net/simple-scan/+bug/1184699/+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 1184699] Re: Canon LIDE 110 can only scan once, then I need to replug the usb cable
In Linux Mint 17 (Ubuntu 14.04) the situation is much worse: I can't ever scan. With Mint 16 (Ubuntu 13.10) the invalid argument error message just happened sometimes, now it happens almost always. With Skanlite, it's either shown almost immediately, after a weak movement, when pressing the preview button, or after the backlight has moved from top to bottom, without returning the actual preview result. With XSane the situation is the same, with the only difference that when the error is not given immediately, the scanner backlight runs fast from top to bottom and then hits against the bottom of the plate, while the motor keeps on trying to move it even further (the scanner makes very bad noise, I have to unplug the USB cable otherwise I fear it will get damaged). In other words, support for this scanner is severely broken in the latest release and I think it may even damage the hardware :-( Is there a hope that it will get fixed? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1184699 Title: Canon LIDE 110 can only scan once, then I need to replug the usb cable Status in Simple Scan: New Status in “sane-backends” package in Ubuntu: Confirmed Bug description: I have a Canon LIDE 110 scanner which works by default on ubuntu 13.04. The problem is after first scan, I can not scan for second time. I need to reconnect the USB cable to use the scanner again. # TEST 1 : without reconnecting the usb cable francois@pc:~$ scanimage -v test1.jpg # success scanimage: scanning image of size 636x885 pixels at 8 bits/pixel scanimage: acquiring gray frame scanimage: min/max graylevel value = 0/255 scanimage: read 562860 bytes in total # I don't unplug plug the usb cable. francois@pc:~$ scanimage -v test2.jpg # FAIL scanimage: no SANE devices found # TEST 2 : reconnect usb cable between scan attempts francois@pc:~$ scanimage -v test1.jpg # success scanimage: scanning image of size 636x885 pixels at 8 bits/pixel scanimage: acquiring gray frame scanimage: min/max graylevel value = 0/255 scanimage: read 562860 bytes in total # I unplug and replug the usb cable. francois@pc:~$ scanimage -v test2.jpg # SUCCESS scanimage: scanning image of size 636x885 pixels at 8 bits/pixel scanimage: acquiring gray frame scanimage: min/max graylevel value = 0/255 scanimage: read 562860 bytes in total francois@pc:~$ dmesg # extract [ 829.365158] usb 3-1: USB disconnect, device number 2 [ 834.935000] usb 3-1: new high-speed USB device number 4 using xhci_hcd [ 834.952515] usb 3-1: New USB device found, idVendor=04a9, idProduct=1909 [ 834.952519] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 834.952522] usb 3-1: Product: CanoScan [ 834.952524] usb 3-1: Manufacturer: Canon [ 1623.738811] usb 3-1: USB disconnect, device number 4 [ 1623.739072] xhci_hcd :00:14.0: Slot 3 endpoint 6 not removed from BW list! [ 1625.528827] usb 3-1: new high-speed USB device number 5 using xhci_hcd [ 1625.546327] usb 3-1: New USB device found, idVendor=04a9, idProduct=1909 [ 1625.546331] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 1625.546334] usb 3-1: Product: CanoScan [ 1625.546336] usb 3-1: Manufacturer: Canon francois@pc:~$ uname -a cat /etc/issue Linux pc 3.8.0-22-generic #33-Ubuntu SMP Thu May 16 15:17:14 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Ubuntu 13.04 \n \l The problem was reported here by someone else : http://askubuntu.com/questions/278473/canon-lide-110-should-reconnect- usb-for-each-scan Thanks François To manage notifications about this bug go to: https://bugs.launchpad.net/simple-scan/+bug/1184699/+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 1364785] [NEW] package libreoffice-common (not installed) failed to install/upgrade: tentata sovrascrittura di /usr/bin/soffice presente anche nel pacchetto openoffice.org-de
Public bug reported: Stop system upgrade, moving to 14.04.1 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libreoffice-common (not installed) ProcVersionSignature: Ubuntu 3.2.0-40.64-generic 3.2.40 Uname: Linux 3.2.0-40-generic i686 ApportVersion: 2.0.1-0ubuntu17.1 Architecture: i386 Date: Tue Sep 2 15:28:35 2014 DuplicateSignature: Unpacking libreoffice-common (1:4.2.4-0ubuntu2) ... dpkg: error processing archive /var/cache/apt/archives/libreoffice-common_1%3a4.2.4-0ubuntu2_all.deb (--unpack): tentata sovrascrittura di /usr/bin/soffice presente anche nel pacchetto openoffice.org-debian-menus 3.4-9593 ErrorMessage: tentata sovrascrittura di /usr/bin/soffice presente anche nel pacchetto openoffice.org-debian-menus 3.4-9593 InstallationMedia: Lubuntu 12.04 Precise Pangolin - Release i386 (20120423) MarkForUpload: True SourcePackage: libreoffice Title: package libreoffice-common (not installed) failed to install/upgrade: tentata sovrascrittura di /usr/bin/soffice presente anche nel pacchetto openoffice.org-debian-menus 3.4-9593 UpgradeStatus: Upgraded to trusty on 2014-09-02 (0 days ago) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1364785 Title: package libreoffice-common (not installed) failed to install/upgrade: tentata sovrascrittura di /usr/bin/soffice presente anche nel pacchetto openoffice.org-debian-menus 3.4-9593 Status in “libreoffice” package in Ubuntu: New Bug description: Stop system upgrade, moving to 14.04.1 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libreoffice-common (not installed) ProcVersionSignature: Ubuntu 3.2.0-40.64-generic 3.2.40 Uname: Linux 3.2.0-40-generic i686 ApportVersion: 2.0.1-0ubuntu17.1 Architecture: i386 Date: Tue Sep 2 15:28:35 2014 DuplicateSignature: Unpacking libreoffice-common (1:4.2.4-0ubuntu2) ... dpkg: error processing archive /var/cache/apt/archives/libreoffice-common_1%3a4.2.4-0ubuntu2_all.deb (--unpack): tentata sovrascrittura di /usr/bin/soffice presente anche nel pacchetto openoffice.org-debian-menus 3.4-9593 ErrorMessage: tentata sovrascrittura di /usr/bin/soffice presente anche nel pacchetto openoffice.org-debian-menus 3.4-9593 InstallationMedia: Lubuntu 12.04 Precise Pangolin - Release i386 (20120423) MarkForUpload: True SourcePackage: libreoffice Title: package libreoffice-common (not installed) failed to install/upgrade: tentata sovrascrittura di /usr/bin/soffice presente anche nel pacchetto openoffice.org-debian-menus 3.4-9593 UpgradeStatus: Upgraded to trusty on 2014-09-02 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1364785/+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 1307877] Re: Laptop Monitor Brightness reduced to minimum and disabled after disconnection from external monitor.
i confirm this bug. I cant adjust the brightness after second monitor unplug. -- 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/1307877 Title: Laptop Monitor Brightness reduced to minimum and disabled after disconnection from external monitor. Status in The Linux Kernel: New Status in “xorg” package in Ubuntu: Confirmed Bug description: Hi, I have the following problem under Ubuntu 14.04. As soon as I disconnect my external monitor from my Laptop (Lenovo X1 Carbon), the brigthness is reduced to minimum (backlight switches off) and I can not increase it again. When I use the brightness control keys the brightness bar shows that it is set to maximum even though it clearly is not. Using the control keys still changes the brightness bar but does nothing to the brightness itself. Upon a restart of the laptop the brightness returns to its maximum and is controllable again. I encountered this problem under the Unity version shipped with Ubuntu 14.04, but it might happen with other desktop managers as well. This problem did not exist when my Laptop was running under Ubuntu 13.10. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1307877/+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 1271410] Re: screen brightness does not work after removal of second monitor
i confirm this bug. I cant adjust the brightness after second monitor unplug. -- 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/1271410 Title: screen brightness does not work after removal of second monitor Status in “xorg” package in Ubuntu: Invalid Bug description: Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 Conditions: Attach second monitor while on batter power. Remove second monitor. Expected behavior: Screen brightness would stay at current setting and be adjustable using function keys or system settings. Actual behavior: Screen brightness is dim to lowest level and not adjustable using functions keys or system settings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1271410/+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 1294899] Re: Import saved VPN connection has been Recently Broken
tested package version: network-manager-gnome 0.9.8.8-0ubuntu4.1 I am now able to succesfully import openvpn profiles. I tested 5 profiles, all imported correctly. Also confirmed openvpn can be connected and disconnected from network-manager without issues. Thanks. please advise if more testing is needed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1294899 Title: Import saved VPN connection has been Recently Broken Status in The OpenVPN Virtual Private Network: Invalid Status in “network-manager-applet” package in Ubuntu: Fix Released Status in “network-manager-openvpn” package in Ubuntu: Invalid Status in “network-manager-applet” source package in Trusty: Fix Committed Status in “network-manager-openvpn” source package in Trusty: Invalid Status in “network-manager-applet” source package in Utopic: Fix Released Status in “network-manager-openvpn” source package in Utopic: Invalid Status in “network-manager-openvpn” package in Debian: New Bug description: SRU Request: [Impact] Attempting to import a saved VPN connection file results in a segault. This is regression in Ubuntu 14.04 that worked correctly in previous versions. [Test Case] 1- install network-manager-openvpn and network-manager-openvpn-gnome 2- from the network-manager indicator, click on Edit Connections 3- Click on Add 4- Select Import a saved VPN configuration, and open the file in comment #28 Expected results: a window should appear with the imported information Current results: network-manager's connection editor segfaults [Regression potential] This SRU simply adds a couple of missing sections to the 11-user-connections.patch patch that went missing. If the fix is broken, either the vpn files won't import, or creating a new vpn connection could break completely. Original description: I believe recent changes have broken network-manager-openvpn feature that allows you to Import saved VPN connection. I've tested this feature with bundles that I've definitely imported successfully in the past. Now, not only does it not import, but it gives absolutely no feedback at all; the window just disappears as though I didn't just ask it to import a VPN.conf file. The folder (I'm importing the .conf file from) includes all the necessary supporting files. I'm very sure this is not a user error on my part. I've done this several times in the past and I'm certain that the files (that are currently being ignored without dialog feedback) are exactly the same as they were when I was able to import successfully a few weeks ago. I've tested this on multiple machines that have Ubuntu 14.04 installed and fully updated. And, even if the files were indeed corrupted (which I'm certain they are not), the fact that the UI just disappears, instead of showing an error, is a bug within itself. Also, I'd like to point out, that I was able to set up this VPN bundle manually. The point of this bug is to report that the ability to import via .conf files (so that you don't have to set things manually) has recently became nonfunctional. To manage notifications about this bug go to: https://bugs.launchpad.net/openvpn/+bug/1294899/+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 651294] Re: X crash on KDM logout (still - yes, really)
For the records, this bug also affects Debian Wheezy 7.5.0 on an Intel NUC D34010WYKH. The workaround of TerminateServer=true also works there, too. Please note that TerminateServer=true must be added to the [X-*-Core] section, if not present. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/651294 Title: X crash on KDM logout (still - yes, really) Status in Release Notes for Ubuntu: Fix Released Status in “xorg-server” package in Ubuntu: Fix Released Status in “xorg-server” source package in Maverick: Invalid Bug description: PROPOSED RELEASE NOTE: On some Kubuntu systems, the display server crashes on logout instead of returning to the KDE Display Manger (KDM) login display. For systems with this problem, the problem can be avoided by changing the method KDM uses to interact with the display server. Edit /etc/kde4/kdm/kdmrc and uncomment the line #TerminateServer=true by changing it to TerminateServer=true and restart KDM (reboot the system or sudo restart kdm). Binary package hint: xserver-xorg-video-intel This system still crashes reliably on logout. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: xserver-xorg-video-intel 2:2.12.0-1ubuntu5 ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic i686 NonfreeKernelModules: wl Architecture: i386 DRM.card0.LVDS.1: status: connected enabled: enabled dpms: On modes: 1024x600 edid-base64: AP///wAw5AYCAAATAQOAFg14CtOFlVlWjiggUFQBAQEBAQEBAQEBAQEBAQEBdBgA0kFYZCAwIDYA4H4b/gBGMDUwVIAxMDFXU0EKAAEBCiAgAI4= DRM.card0.VGA.1: status: disconnected enabled: disabled dpms: On modes: edid-base64: Date: Wed Sep 29 12:48:45 2010 DkmsStatus: bcmwl, 5.60.48.36+bdcom, 2.6.35-20-generic, i686: installed bcmwl, 5.60.48.36+bdcom, 2.6.35-22-generic, i686: installed EcryptfsInUse: Yes GdmLog: Error: command ['kdesudo', '--', 'cat', '/var/log/gdm/:0.log'] failed with exit code 1: cat: /var/log/gdm/:0.log: No such file or directory GdmLog1: Error: command ['kdesudo', '--', 'cat', '/var/log/gdm/:0.log.1'] failed with exit code 1: cat: /var/log/gdm/:0.log.1: No such file or directory GdmLog2: Error: command ['kdesudo', '--', 'cat', '/var/log/gdm/:0.log.2'] failed with exit code 1: cat: /var/log/gdm/:0.log.2: No such file or directory InstallationMedia: Kubuntu 10.10 Maverick Meerkat - Alpha i386 (20100909) MachineType: Dell Inc. Inspiron 1011 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic root=UUID=3db0186f-9810-41ed-8ba1-715fb956e23e ro quiet splash ProcEnviron: LANGUAGE= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xserver-xorg-video-intel dmi.bios.date: 03/20/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A00 dmi.board.name: CN0Y53 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A00 dmi.modalias: dmi:bvnDellInc.:bvrA00:bd03/20/2009:svnDellInc.:pnInspiron1011:pvrA00:rvnDellInc.:rnCN0Y53:rvrA00:cvnDellInc.:ct8:cvrA00: dmi.product.name: Inspiron 1011 dmi.product.version: A00 dmi.sys.vendor: Dell Inc. glxinfo: Error: [Errno 2] No such file or directory peripherals: Error: [Errno 2] No such file or directory system: distro: Ubuntu codename: maverick architecture: i686 kernel: 2.6.35-22-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/651294/+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 1168900] Re: 10de:0422 Xorg crashes after suspension with Mesa 9.1.1-0ubunt0.3
i confirm this bug with: Ubuntu 13.10 GeForce GTX 560 Ti noveau kernel 3.14.0-031400rc3-generic - the latest non-daily mainline kernel libegl1-mesa 9.2.1-1ubuntu3 in the xorg log i found: nouveau_exa_download_from_screen:299 - falling back to memcpy ignores tiling during the 'freeze' of the kernel say somte times this: nouveau E[Xorg[1680]] failed to idle channel 0x0001 [Xorg[1680]] ** Attachment added: Xorg.0.log.old https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1168900/+attachment/3992742/+files/Xorg.0.log.old -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1168900 Title: 10de:0422 Xorg crashes after suspension with Mesa 9.1.1-0ubunt0.3 Status in “xserver-xorg-video-nouveau” package in Ubuntu: Confirmed Bug description: While using Mesa from ubuntu-x-swat/x-staging PPA Xorg crashes everytime I suspend my PC. This is my hardware: http://wiki.ubuntu-it.org/CarlaSella/lshw. When I suspend my PC, after pressing the power button to resume from suspention I get a black screen an PC is stuck, can only reboot. I tried two time, the first time: - suspended - pushed power button - got a black screen with only a white mouse pointer, could move the mouse pointer - I could go to terminal pressing CTRL+ALT+F1 and return to the black screen with CTRL+ALT+F7 - aftere like 3/4 minutes got lighdm logon screen - logged on - got a black screen, this time could not go to terminal with CTRL+ALT+F1 had to reboot pressing CTRL+ALT+CANC - after rebbot I saw a crash file in /var/crash and reported the but with apport, but it was automatically reported and go no bug number in retrun to tell you. The second time: - suspended - pushed power button - saw Ubuntu orange backgruound with unlock screen, tried to enter my password, but was unable, it was as if the keyboard di not work - after a while I was presented with lightdm logon - logged on but got a black screen with mouse pointer but could not do anything but reboot pressing power button - after reboot a crash was automatically reported, have no bug number. The strange thing is that I have only one crash file in /var/crash even if Xorg crashed twice. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-17.27-generic 3.8.6 Uname: Linux 3.8.0-17-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.9.2-0ubuntu8 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 CurrentDmesg: [ 45.001171] systemd-hostnamed[2102]: Warning: nss-myhostname is not installed. Changing the local hostname might make it unresolveable. Please install nss-myhostname! Date: Sun Apr 14 17:29:05 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation G86 [GeForce 8400 GS] [10de:0422] (rev a1) (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:2310] InstallationDate: Installed on 2013-04-14 (0 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130413) MachineType: System manufacturer System Product Name MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-17-generic root=UUID=a30d4d80-b268-4e64-82c7-7d2cff00a3ab ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/28/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0702 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M2N dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0702:bd05/28/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.9~daily13.04.10-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.43-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.1-0ubuntu0.3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.1-0ubuntu0.3 version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2
[Desktop-packages] [Bug 1168900] Re: 10de:0422 Xorg crashes after suspension with Mesa 9.1.1-0ubunt0.3
i mean the 'freeze' of the xorg server sorry -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1168900 Title: 10de:0422 Xorg crashes after suspension with Mesa 9.1.1-0ubunt0.3 Status in “xserver-xorg-video-nouveau” package in Ubuntu: Confirmed Bug description: While using Mesa from ubuntu-x-swat/x-staging PPA Xorg crashes everytime I suspend my PC. This is my hardware: http://wiki.ubuntu-it.org/CarlaSella/lshw. When I suspend my PC, after pressing the power button to resume from suspention I get a black screen an PC is stuck, can only reboot. I tried two time, the first time: - suspended - pushed power button - got a black screen with only a white mouse pointer, could move the mouse pointer - I could go to terminal pressing CTRL+ALT+F1 and return to the black screen with CTRL+ALT+F7 - aftere like 3/4 minutes got lighdm logon screen - logged on - got a black screen, this time could not go to terminal with CTRL+ALT+F1 had to reboot pressing CTRL+ALT+CANC - after rebbot I saw a crash file in /var/crash and reported the but with apport, but it was automatically reported and go no bug number in retrun to tell you. The second time: - suspended - pushed power button - saw Ubuntu orange backgruound with unlock screen, tried to enter my password, but was unable, it was as if the keyboard di not work - after a while I was presented with lightdm logon - logged on but got a black screen with mouse pointer but could not do anything but reboot pressing power button - after reboot a crash was automatically reported, have no bug number. The strange thing is that I have only one crash file in /var/crash even if Xorg crashed twice. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-17.27-generic 3.8.6 Uname: Linux 3.8.0-17-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.9.2-0ubuntu8 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 CurrentDmesg: [ 45.001171] systemd-hostnamed[2102]: Warning: nss-myhostname is not installed. Changing the local hostname might make it unresolveable. Please install nss-myhostname! Date: Sun Apr 14 17:29:05 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation G86 [GeForce 8400 GS] [10de:0422] (rev a1) (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:2310] InstallationDate: Installed on 2013-04-14 (0 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130413) MachineType: System manufacturer System Product Name MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-17-generic root=UUID=a30d4d80-b268-4e64-82c7-7d2cff00a3ab ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/28/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0702 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M2N dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0702:bd05/28/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.9~daily13.04.10-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.43-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.1-0ubuntu0.3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.1-0ubuntu0.3 version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1 xserver.bootTime: Sun Apr 14 17:28:13 2013 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.3-0ubuntu5
[Desktop-packages] [Bug 785777] Re: Display corrupted exiting from XBMC
Now I'm running Ubuntu 13.04 and XBMC 12.3 with the same hw and I don't experience anymore the problem. You can close the bug for me. Thank's a lot for xbmc, it's a great pieace of sw, I use it every day!!! Bye Mauro ** Changed in: xserver-xorg-video-ati (Ubuntu) Status: Incomplete = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/785777 Title: Display corrupted exiting from XBMC Status in “xserver-xorg-video-ati” package in Ubuntu: Fix Released Bug description: When I exit from xbmc display is corrupted [url=http://postimage.org/image/30fo3whgk/][img]http://s2.postimage.org/30fo3whgk/IMAG0527.jpg[/img][/url] this is my conf: cpu - amd athlon II X4 600e mb - gygabyte GA-880GMA-UD2H (880g int graphics) ram - 4gb natty 32 bit proposed (fresh install, gnome classic no effects and unity same problem) xbmc 10.1 installed from ppa (both confluence and pm3.hd) xbmc.log http://pastebin.com/gcdDjN3f crash log http://pastebin.com/xWPdDh7J the problem was not affecting maverick thanks in advance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/785777/+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 349179] Re: Cannot print on network Windoze printer
** Changed in: cups (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/349179 Title: Cannot print on network Windoze printer Status in “cups” package in Ubuntu: Fix Released Status in “samba” package in Ubuntu: Won't Fix Bug description: Recently upgraded to Intrepid from Hardy. After I upgraded, I added the Brother HL-1240 on my Win XP64 machine. The test page printed. On next boot, I tried to print to the laser. It didn't. I have attached the troubleshoot text generated. Hope I've given enough info. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/349179/+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 1155157] Re: [FFe] Allow custom indicators
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1155157 Title: [FFe] Allow custom indicators Status in Unity Greeter: Fix Released Status in “unity-greeter” package in Ubuntu: Fix Released Status in “unity-greeter” source package in Precise: Fix Committed Status in “unity-greeter” source package in Raring: Fix Released Bug description: [Impact] * Would allow system administrators to load custom indicators, and allow one to control the active user [Impact] * This would improve the polish of unity greeter for kiosk/corporate deployment * This will allow admins to select the active entry on login screen ( such as with smart card) [Test Case] * Edit dconf key com.canonical.unity-greeter using dconf-editor to load or not load existing indicator . [Regression Potential] * I dont see any regression potential , as this unity-greeter is not linked by any other application and this only adds a bus method. * Worst case, user mis-configures (typo/invalid indicators) the indicators to load and ends up without them. [Other Info] * https://lists.ubuntu.com/archives/technical- board/2013-May/001622.html I'd like to upload a new unity-greeter to raring with a new feature. System administrators have been requesting the ability to add new custom indicators to the greeter. And to be able to control the greeter slightly with those indicators. In trunk, we've added support for this in two ways: * Have the list of loaded indicators be controlled by a gsettings variable under the lightdm user, which system administrators can customize. * Add a session DBus interface to the greeter to allow switching which user is selected. This is only available to the greeter session bus, not on the system bus. Note that these features are not used by default, they'd only be used if an administrator specifically chose to use them. To manage notifications about this bug go to: https://bugs.launchpad.net/unity-greeter/+bug/1155157/+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 1125944] Re: (gedit:3366): IBUS-WARNING **: The owner of /home/oem/.config/ibus/bus is not root!
Not a solution, because if you run gedit from terminal with your user (not with sudo), you get: IBUS-WARNING **: The owner of /home/[user]/.config/ibus/bus is not [user]! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1125944 Title: (gedit:3366): IBUS-WARNING **: The owner of /home/oem/.config/ibus/bus is not root! Status in “ibus” package in Ubuntu: Confirmed Bug description: RR i386 logged as gnome-classic (fallback) Seen that error for the first time while using a terminal: oem@oem-desktop:~$ sudo gedit /etc/default/grub (gedit:3366): IBUS-WARNING **: The owner of /home/oem/.config/ibus/bus is not root! That one is own by Me (screenshot joined) ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: ibus 1.4.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-6.13-generic 3.8.0-rc7 Uname: Linux 3.8.0-6-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.8-0ubuntu4 Architecture: i386 Date: Fri Feb 15 08:33:36 2013 MarkForUpload: True SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1125944/+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 1174936] Re: online-accounts-preferences crashes immediately when opened
I also have this issue. Oleksandr's workaround also helps, but if I launch online-accounts-preferences from terminal, the error is displayed even if panel opens. When this happens, I noticed that my icq plugin does not allow me to modify my account, the whole page is greyed out and the only thing I can do is remove the account. if I remove and re-add the account, I am still unable to enter account information. Not sure if it is related or a completely separate bug. ** Attachment added: icq fails to display account info https://bugs.launchpad.net/ubuntu/+source/gnome-control-center-signon/+bug/1174936/+attachment/3665460/+files/ubuntu-13.04-online-accounts-icq.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1174936 Title: online-accounts-preferences crashes immediately when opened Status in “empathy” package in Ubuntu: Confirmed Status in “gnome-control-center-signon” package in Ubuntu: Confirmed Bug description: `online-accounts-preferences` crashes immediately when opened. It crashes when you launch it by first opening System Settings via the launcher then choosing Online Accounts as well as when you open it directly by choosing Online Accounts from the launcher. It also crashes immediately when opened by running the `online-accounts- preferences` command on the command line. Here's the output it gives: % online-accounts-preferences credentials-cc-panel-Message: cc-credentials-account-applications-model.vala:156: No valid plugin found for application 'shotwell' with account '1' credentials-cc-panel-Message: cc-credentials-account-applications-model.vala:156: No valid plugin found for application 'unity-scope-gdrive' with account '1' credentials-cc-panel-Message: cc-credentials-account-applications-model.vala:156: No valid plugin found for application 'unity-lens-photos' with account '1' ** ERROR:empathy-user-info.c:252:fill_contact_info_grid: assertion failed: (spec != NULL) Aborted ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-control-center-signon 0.1.6bzr13.04.05-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Tue Apr 30 14:03:48 2013 InstallationDate: Installed on 2012-10-18 (194 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True ProcEnviron: TERM=xterm-color PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/usr/bin/zsh SourcePackage: gnome-control-center-signon UpgradeStatus: Upgraded to raring on 2013-04-26 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1174936/+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 1125944] Re: (gedit:3366): IBUS-WARNING **: The owner of /home/oem/.config/ibus/bus is not root!
Great! Worked here too! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1125944 Title: (gedit:3366): IBUS-WARNING **: The owner of /home/oem/.config/ibus/bus is not root! Status in “ibus” package in Ubuntu: Confirmed Bug description: RR i386 logged as gnome-classic (fallback) Seen that error for the first time while using a terminal: oem@oem-desktop:~$ sudo gedit /etc/default/grub (gedit:3366): IBUS-WARNING **: The owner of /home/oem/.config/ibus/bus is not root! That one is own by Me (screenshot joined) ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: ibus 1.4.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-6.13-generic 3.8.0-rc7 Uname: Linux 3.8.0-6-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.8-0ubuntu4 Architecture: i386 Date: Fri Feb 15 08:33:36 2013 MarkForUpload: True SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1125944/+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 1041790] Re: [snb] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001, workaround i915.semaphores=0
** Also affects: sandybridge-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1041790 Title: [snb] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001, workaround i915.semaphores=0 Status in X.org xf86-video-intel: Confirmed Status in “linux” package in Ubuntu: Invalid Status in “sandybridge-meta” package in Ubuntu: New Status in “xserver-xorg-video-intel” package in Ubuntu: Triaged Bug description: X locks up periodically for a 2 to ten seconds at a time and this crash log gets generated. It's significantly more than several times a day but not quite continuous. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: xserver-xorg-video-intel 2:2.20.3-0ubuntu1 Uname: Linux 3.6.0-rc3-git-20120826.1015 x86_64 ApportVersion: 2.5.1-0ubuntu2 Architecture: amd64 Chipset: sandybridge-m-gt2 Date: Sun Aug 26 16:06:32 2012 DistroCodename: quantal DistroVariant: ubuntu DuplicateSignature: [sandybridge-m-gt2] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001 Ubuntu 12.10 EcryptfsInUse: Yes ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py GpuHangFrequency: Continuously InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120724.2) InterpreterPath: /usr/bin/python3.2mu MachineType: Dell Inc. Dell System XPS L502X ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.6.0-rc3-git-20120826.1015 root=UUID=135c8090-427c-460a-909d-eff262cd44b6 ro quiet splash vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.7+1ubuntu3 libdrm2 2.4.38-0ubuntu2 xserver-xorg-video-intel 2:2.20.3-0ubuntu1 SourcePackage: xserver-xorg-video-intel Title: [sandybridge-m-gt2] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001 UdevDb: Error: [Errno 2] No such file or directory: 'udevadm' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 05/29/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0NJT03 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA11:bd05/29/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L502X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1041790/+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 1066488] Re: No sound on Dell XPS after suspend (ALC275)
Same here on 12.10. I'm on a HP 6730s. sudo lshw output: http://pastebin.com/vh3SGcZa Can't sudo modprobe -r snd_hda_intel. It gives FATAL: Module snd_hda_intel is in use /etc/modprobe.d/alsa-base.conf content: http://pastebin.com/yvArB2ex In /var/log/syslog I found the following: kernel: [ 33.847111] pci_pm_runtime_suspend(): azx_runtime_suspend+0x0/0x40 [snd_hda_intel] returns -11 -- 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/1066488 Title: No sound on Dell XPS after suspend (ALC275) Status in “pulseaudio” package in Ubuntu: Confirmed Bug description: Dell XPS One 2710, Ubuntu 12.04, Kernel 3.2.0.31 or 3.2.0.32 or 3.6.2 Sound works out of the box, until machine is supended to RAM. After suspend and resume, no sound at all. A suspend to Disk and resume restores sound! aplay -l: Karte 0: PCH [HDA Intel PCH], Gerät 0: ALC275 Analog [ALC275 Analog] Sub-Geräte: 1/1 Sub-Gerät #0: subdevice #0 Karte 0: PCH [HDA Intel PCH], Gerät 3: HDMI 0 [HDMI 0] Sub-Geräte: 1/1 Sub-Gerät #0: subdevice #0 lsmod|grep snd: snd_hda_codec_hdmi 32506 1 snd_hda_codec_realtek79668 1 snd_hda_intel 34147 3 snd_hda_codec 135374 3 snd_hda_codec_hdmi,snd_hda_codec_realtek,snd_hda_intel snd_hwdep 13668 1 snd_hda_codec snd_pcm97661 3 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec snd_timer 29989 1 snd_pcm snd79391 13 snd_hda_codec_hdmi,snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer soundcore 15091 1 snd snd_page_alloc 18572 2 snd_hda_intel,snd_pcm It is NOT possible to unload snd modules. sudo /sbin/alsa force-unload: Unloading ALSA sound driver modules: snd-hda-codec-hdmi snd-hda-codec-realtek snd-hda-intel snd-hda-codec snd-hwdep snd-pcm snd-seq-midi snd-rawmidi snd-seq-midi-event snd-seq snd-timer snd-seq-device snd-page-alloc (failed: modules still loaded: snd-hda-codec-hdmi snd-hda-codec-realtek snd-hda-intel snd-hda-codec snd-hwdep snd-pcm snd-timer snd-page-alloc). All information in the net either is depreciated (using acpi_suspend) or refers to chips that have options (e.g. modprobe snd_hda_intel option=acer). There is NO documentation about options of the ALC275 chip. Anybody has a solution to this? Thanks Michael To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1066488/+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 1056379] Re: empathy no longer allows to create IRC accounts
** Attachment added: Top half of the available account types https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1056379/+attachment/3348289/+files/accounts1.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1056379 Title: empathy no longer allows to create IRC accounts Status in “empathy” package in Ubuntu: Incomplete Bug description: Not sure if this is an empathy bug or a telepathy-idle bug unfortunately. Despite the fact that telepathy-idle is installed, it's not possible to create an IRC account. Launching empathy on the command line doesn't reveal any interesting log information. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1056379/+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 1056379] Re: empathy no longer allows to create IRC accounts
** Attachment added: Bottom part https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1056379/+attachment/3348290/+files/accounts2.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1056379 Title: empathy no longer allows to create IRC accounts Status in “empathy” package in Ubuntu: Incomplete Bug description: Not sure if this is an empathy bug or a telepathy-idle bug unfortunately. Despite the fact that telepathy-idle is installed, it's not possible to create an IRC account. Launching empathy on the command line doesn't reveal any interesting log information. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1056379/+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 1056379] Re: empathy no longer allows to create IRC accounts
Do you prefer it if I open another bug via ubuntu-bug and mark this as duplicate? You'll have more debugging info on package versions, etc. and I can re-attach the screenshots. I'm attaching screenshots to this one in the meantime. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1056379 Title: empathy no longer allows to create IRC accounts Status in “empathy” package in Ubuntu: Incomplete Bug description: Not sure if this is an empathy bug or a telepathy-idle bug unfortunately. Despite the fact that telepathy-idle is installed, it's not possible to create an IRC account. Launching empathy on the command line doesn't reveal any interesting log information. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1056379/+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 1056379] [NEW] empathy no longer allows to create IRC accounts
Public bug reported: Not sure if this is an empathy bug or a telepathy-idle bug unfortunately. Despite the fact that telepathy-idle is installed, it's not possible to create an IRC account. Launching empathy on the command line doesn't reveal any interesting log information. ** Affects: empathy (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1056379 Title: empathy no longer allows to create IRC accounts Status in “empathy” package in Ubuntu: New Bug description: Not sure if this is an empathy bug or a telepathy-idle bug unfortunately. Despite the fact that telepathy-idle is installed, it's not possible to create an IRC account. Launching empathy on the command line doesn't reveal any interesting log information. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1056379/+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 1056379] Re: empathy no longer allows to create IRC accounts
This is Quantal, using the 20120924 image empathy version 3.5.92-0ubuntu2 telepathy-idle version 0.1.12-1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1056379 Title: empathy no longer allows to create IRC accounts Status in “empathy” package in Ubuntu: New Bug description: Not sure if this is an empathy bug or a telepathy-idle bug unfortunately. Despite the fact that telepathy-idle is installed, it's not possible to create an IRC account. Launching empathy on the command line doesn't reveal any interesting log information. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1056379/+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 1023454] Re: Thunderbird 13.0.1 German Translation is incomplete
Same here with Italian language -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1023454 Title: Thunderbird 13.0.1 German Translation is incomplete Status in “thunderbird” package in Ubuntu: Confirmed Bug description: on Ubuntu 12.04 with all latest updates, Thunderbird 13.0.1 with german translation 13.0.1 isn't completely translated. i.e. Inbox and Mark folder as Read are shown in English... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1023454/+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 1025986] [NEW] Thunderbird not completely translated
Public bug reported: I was running 13.0.1 with related language pack (Italian) installed and my Thunderbird was completely translated into my language. Suddenly folders names turn back in English (Inbox - Unified Folders, Drafts, Templates, Sent, Archives, Junk, Trash, Outbox) while almost everything else remained correctly translated. I'm sure it's not related to an update, because it started to happen during my 13.0.1 use, and not since its installation. The issue persists with Thundebird 14.0. Ubuntu 12.04 LTS thunderbird 14.0+build1-0ubuntu0.12.04.1 ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1025986 Title: Thunderbird not completely translated Status in “thunderbird” package in Ubuntu: New Bug description: I was running 13.0.1 with related language pack (Italian) installed and my Thunderbird was completely translated into my language. Suddenly folders names turn back in English (Inbox - Unified Folders, Drafts, Templates, Sent, Archives, Junk, Trash, Outbox) while almost everything else remained correctly translated. I'm sure it's not related to an update, because it started to happen during my 13.0.1 use, and not since its installation. The issue persists with Thundebird 14.0. Ubuntu 12.04 LTS thunderbird 14.0+build1-0ubuntu0.12.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1025986/+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 1016292] Re: Doesn't return to maximized size when restarted
Yes, I asked there and the packages in proposed repo was suggested, but I was already using those packages. The issue still remains. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xchat-gnome in Ubuntu. https://bugs.launchpad.net/bugs/1016292 Title: Doesn't return to maximized size when restarted Status in GNOME frontend to the popular xchat IRC client: New Status in “xchat-gnome” package in Ubuntu: Fix Released Status in “xchat-gnome” source package in Precise: Fix Committed Bug description: XChat remembers the window size and restores is when restarting. However if it was maximized before quitting it restarts at almost full size (see attached screenshot). [Impact] When restarting xchat-gnome the background can be seen at the bottom of the window. The user needs to maximize the application each time they start it (if they always use it maximized). [Test Case] 1. Start xchat-gnome 2. Maximize window 3. Close xchat-gnome 4. Start xchat-gnome Expected result: Window is maximized Observed result: Window takes up most of the screen but the doesn't extend to the bottom of the screen [Regression Potential] Minimally invasive patch, normal risk of causing additional bugs. To manage notifications about this bug go to: https://bugs.launchpad.net/xchat-gnome/+bug/1016292/+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 1016292] Re: Doesn't return to maximized size when restarted
Yes. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xchat-gnome in Ubuntu. https://bugs.launchpad.net/bugs/1016292 Title: Doesn't return to maximized size when restarted Status in GNOME frontend to the popular xchat IRC client: New Status in “xchat-gnome” package in Ubuntu: Fix Released Status in “xchat-gnome” source package in Precise: Fix Committed Bug description: XChat remembers the window size and restores is when restarting. However if it was maximized before quitting it restarts at almost full size (see attached screenshot). [Impact] When restarting xchat-gnome the background can be seen at the bottom of the window. The user needs to maximize the application each time they start it (if they always use it maximized). [Test Case] 1. Start xchat-gnome 2. Maximize window 3. Close xchat-gnome 4. Start xchat-gnome Expected result: Window is maximized Observed result: Window takes up most of the screen but the doesn't extend to the bottom of the screen [Regression Potential] Minimally invasive patch, normal risk of causing additional bugs. To manage notifications about this bug go to: https://bugs.launchpad.net/xchat-gnome/+bug/1016292/+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 874023] Re: Low-resolution icon in the app switcher
Duplicated: https://bugs.launchpad.net/ubuntu/+source/gucharmap/+bug/874008 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gucharmap in Ubuntu. https://bugs.launchpad.net/bugs/874023 Title: Low-resolution icon in the app switcher Status in “gucharmap” package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1) Launch Gnome Terminal 2) Launch Firefox 3) Launch Character Map 4) Press alt-tab Actual results: The icon for Character Map shown in the app switcher has a low resolution which makes it look ugly and out of place compared to the terminal and Firefox icons. Expected results: Expected to see a high-resolution icon for Character Map in the app switcher. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gucharmap 1:3.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Fri Oct 14 12:50:32 2011 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gucharmap InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gucharmap UpgradeStatus: Upgraded to oneiric on 2011-10-14 (0 days ago) XsessionErrors: (nautilus:2117): Gtk-CRITICAL **: gtk_action_set_visible: assertion `GTK_IS_ACTION (action)' failed (nautilus:2117): Gtk-CRITICAL **: gtk_action_set_visible: assertion `GTK_IS_ACTION (action)' failed (Do:2132): Wnck-CRITICAL **: wnck_set_client_type got called multiple times. (gnome-settings-daemon:2090): Gdk-WARNING **: The program 'gnome-settings-daemon' received an X Window System error. (gedit:2502): Gtk-CRITICAL **: gtk_list_store_set_column_types: assertion `priv-columns_dirty == 0' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gucharmap/+bug/874023/+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 804709] Re: Does not give useful error messages about package installation failures
hola estoy metiendo los drivers nvidia para unity3d -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/804709 Title: Does not give useful error messages about package installation failures Status in “jockey” package in Ubuntu: Fix Released Status in “jockey” source package in Oneiric: Fix Released Bug description: Sorry too many recent crashes to give details that are surely connected to the report. ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: jockey-common 0.9.2-0ubuntu7 ProcVersionSignature: Ubuntu 3.0-2.3-generic-pae 3.0.0-rc4 Uname: Linux 3.0-2-generic-pae i686 Architecture: i386 Date: Sat Jul 2 02:26:19 2011 ExecutablePath: /usr/share/jockey/jockey-backend InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Alpha i386 (20110531.1) InterpreterPath: /usr/bin/python2.7 MachineType: LENOVO 0221A16 PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/share/jockey/jockey-backend --debug -l /var/log/jockey.log ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0-2-generic-pae root=UUID=84e4eaea-31dd-4101-b810-a878bb24cc7c ro quiet splash vt.handoff=7 PythonArgs: ['/usr/share/jockey/jockey-backend', '--debug', '-l', '/var/log/jockey.log'] SourcePackage: jockey Title: jockey-backend crashed with SystemError: E:Sub-process /usr/bin/dpkg returned an error code (1) Traceback: SystemError: E:Sub-process /usr/bin/dpkg returned an error code (1) UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 05/05/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 85ET39WW (1.12 ) dmi.board.name: 0221A16 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr85ET39WW(1.12):bd05/05/2011:svnLENOVO:pn0221A16:pvrThinkPadEdge:rvnLENOVO:rn0221A16:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 0221A16 dmi.product.version: ThinkPad Edge dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jockey/+bug/804709/+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 959874] Re: gnome-settings-daemon crashed with SIGSEGV in ubuntu_osd_do_notification()
Reproduced on MacBookAir4,2 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/959874 Title: gnome-settings-daemon crashed with SIGSEGV in ubuntu_osd_do_notification() Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Status in “gnome-settings-daemon” source package in Precise: Confirmed Bug description: I started seeing this problem after updating today (2012-03-19). g-s-d crashes every time I try to use the hotkeys to adjust the keyboard backlight brightness. I see lines like the following in syslog: Mar 19 20:55:17 ubuntu-mba kernel: [ 250.180733] gnome-settings-[4019]: segfault at f0 ip 7f9dc774235b sp 7fff0cedffe0 error 4 in libmedia-keys.so[7f9dc7735000+25000] Mar 19 20:55:17 ubuntu-mba gnome-session[3722]: WARNING: App 'gnome-settings-daemon.desktop' respawning too quickly Mar 19 20:55:17 ubuntu-mba gnome-session[3722]: CRITICAL: We failed, but the fail whale is dead. Sorry The machine is a MacBook Air 4,1. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: gnome-settings-daemon 3.3.92-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-19.30-generic 3.2.11 Uname: Linux 3.2.0-19-generic x86_64 ApportVersion: 1.94.1-0ubuntu2 Architecture: amd64 CrashCounter: 1 Date: Mon Mar 19 20:50:21 2012 EcryptfsInUse: Yes ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64+mac (20111208) ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f19aa61235b:cmpq $0x0,(%rdi) PC (0x7f19aa61235b) ok source $0x0 ok destination (%rdi) (0x00f0) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: gnome-settings-daemon StacktraceTop: ?? () from /usr/lib/gnome-settings-daemon-3.0/libmedia-keys.so ?? () from /usr/lib/gnome-settings-daemon-3.0/libmedia-keys.so g_simple_async_result_complete () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 g_simple_async_result_complete () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: gnome-settings-daemon crashed with SIGSEGV in g_simple_async_result_complete() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/959874/+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 871047] Re: Can no longer set screen to lock when lid closed
Just a few questions more. Does power manager deamon autostart? Is gnome-screensaver installed? Is xscreensaver installed? Thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/871047 Title: Can no longer set screen to lock when lid closed Status in “gnome-power-manager” package in Ubuntu: Confirmed Bug description: Before, with Gnome 2, I've configured it for when I close the laptop lid it lock the screen demanding the password. It's because sometimes I go to any places publics or with my friends and I don't want to have the PC trolled when I leave it for a while. Now, with Ubuntu 11.10, the gnome-screensaver is deleted, so when I select the blank option at org.gnome.settings-daemon.plugins.power lid-close-ac-action with dconf-editor, only it puts the screen black, but it doesn't block the screen because before the gnome- screensaver was the responsible of doing it and with Gnome 3 and Unity it dissapears. It's possible to add and lock-screen option that executes the lock screen command? Because I think that to close the screen is a better gesture to make sure that you've locked it more than remember always to do Ctrl+Alt+L. See also bug 888330, the equivalent for blanking the screen. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-power-manager 3.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu2 Architecture: amd64 Date: Sun Oct 9 02:08:57 2011 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GnomeSessionSuspendInhibited: No InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20111006) MachineType: Dell Inc. XPS M1330 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic root=UUID=f2473a46-a5f1-46b1-8b14-e6677563f14b ro quiet splash nomodeset video=uvesafb:mode_option=1280x1024-24,mtrr=3,scroll=ywrap vt.handoff=7 SourcePackage: gnome-power-manager UpgradeStatus: Upgraded to oneiric on 2011-10-07 (1 days ago) dmi.bios.date: 12/26/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0U8042 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd12/26/2008:svnDellInc.:pnXPSM1330:pvr:rvnDellInc.:rn0U8042:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: XPS M1330 dmi.sys.vendor: Dell Inc. gnome-power-bugreport: Error: [Errno 2] No existe el archivo o el directorio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/871047/+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 871047] Re: Can no longer set screen to lock when lid closed
Also after rebooting? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/871047 Title: Can no longer set screen to lock when lid closed Status in “gnome-power-manager” package in Ubuntu: Confirmed Bug description: Before, with Gnome 2, I've configured it for when I close the laptop lid it lock the screen demanding the password. It's because sometimes I go to any places publics or with my friends and I don't want to have the PC trolled when I leave it for a while. Now, with Ubuntu 11.10, the gnome-screensaver is deleted, so when I select the blank option at org.gnome.settings-daemon.plugins.power lid-close-ac-action with dconf-editor, only it puts the screen black, but it doesn't block the screen because before the gnome- screensaver was the responsible of doing it and with Gnome 3 and Unity it dissapears. It's possible to add and lock-screen option that executes the lock screen command? Because I think that to close the screen is a better gesture to make sure that you've locked it more than remember always to do Ctrl+Alt+L. See also bug 888330, the equivalent for blanking the screen. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-power-manager 3.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu2 Architecture: amd64 Date: Sun Oct 9 02:08:57 2011 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GnomeSessionSuspendInhibited: No InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20111006) MachineType: Dell Inc. XPS M1330 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic root=UUID=f2473a46-a5f1-46b1-8b14-e6677563f14b ro quiet splash nomodeset video=uvesafb:mode_option=1280x1024-24,mtrr=3,scroll=ywrap vt.handoff=7 SourcePackage: gnome-power-manager UpgradeStatus: Upgraded to oneiric on 2011-10-07 (1 days ago) dmi.bios.date: 12/26/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0U8042 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd12/26/2008:svnDellInc.:pnXPSM1330:pvr:rvnDellInc.:rn0U8042:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: XPS M1330 dmi.sys.vendor: Dell Inc. gnome-power-bugreport: Error: [Errno 2] No existe el archivo o el directorio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/871047/+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 899881] Re: Unable to open xpi files
sudo apt-get install assogiate run assogiate, find application/zip and add *.xpi in filenames. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/899881 Title: Unable to open xpi files Status in File Roller: New Status in “file-roller” package in Ubuntu: Confirmed Bug description: Since Ubuntu 11.10 Oneiric, I can't open xpi files with file-roller. I have an error that the file is not recognized. One way around is to rename the filename and change .xpi by .zip I think this could be a mimetype issue, since it could be resolved adding .xpi extension to zip mimetype. To manage notifications about this bug go to: https://bugs.launchpad.net/file-roller/+bug/899881/+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 909256] Re: gnome-language-selector crashed with ValueError in _build_localename(): too many values to unpack
Jokin'? Thank YOU! :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/909256 Title: gnome-language-selector crashed with ValueError in _build_localename(): too many values to unpack Status in “language-selector” package in Ubuntu: Fix Released Status in “language-selector” source package in Oneiric: Fix Committed Status in “language-selector” source package in Precise: Fix Released Bug description: SRU note I suggest that the linked branch is uploaded to oneiric-proposed. The change (patch attached) is identical with the change to LanguageSelector/gtk/GtkLanguageSelector.py at http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/precise/language-selector/precise/revision/146 Even if I don't know the exact reason why unicode strings may be passed to locale.setlocale() also in Oneiric, the fact that it apparently can happen is a good enough reason IMO to backport the Precise fix to Oneiric as an SRU, especially since the regression risk is zero. / Gunnar Hjalmarsson Rest of description --- This bug affects Oneiric: (gnome-language-selector:3039): Gdk-CRITICAL **: gdk_window_get_pointer: assertion `GDK_IS_WINDOW (window)' failed (gnome-language-selector:3039): Gdk-CRITICAL **: gdk_window_get_pointer: assertion `GDK_IS_WINDOW (window)' failed (gnome-language-selector:3039): Gdk-CRITICAL **: gdk_window_get_pointer: assertion `GDK_IS_WINDOW (window)' failed (gnome-language-selector:3039): Gdk-CRITICAL **: gdk_window_get_pointer: assertion `GDK_IS_WINDOW (window)' failed (gnome-language-selector:3039): Gdk-CRITICAL **: gdk_window_get_pointer: assertion `GDK_IS_WINDOW (window)' failed (gnome-language-selector:3039): Gdk-CRITICAL **: gdk_window_get_pointer: assertion `GDK_IS_WINDOW (window)' failed /usr/lib/python2.7/dist-packages/LanguageSelector/LocaleInfo.py:125: UnicodeWarning: Unicode equal comparison failed to convert both arguments to Unicode - interpreting them as being unequal if lang_name == self._lang[lang]: Traceback (most recent call last): File /usr/bin/gnome-language-selector, line 27, in module options=options) File /usr/lib/python2.7/dist-packages/LanguageSelector/gtk/GtkLanguageSelector.py, line 192, in __init__ self.updateLocaleChooserCombo() File /usr/lib/python2.7/dist-packages/LanguageSelector/gtk/GtkLanguageSelector.py, line 57, in wrapper res = f(*args, **kwargs) File /usr/lib/python2.7/dist-packages/LanguageSelector/gtk/GtkLanguageSelector.py, line 853, in updateLocaleChooserCombo self.updateExampleBox() File /usr/lib/python2.7/dist-packages/LanguageSelector/gtk/GtkLanguageSelector.py, line 926, in updateExampleBox locale.setlocale(locale.LC_ALL, mylocale) File /usr/lib/python2.7/locale.py, line 539, in setlocale locale = normalize(_build_localename(locale)) File /usr/lib/python2.7/locale.py, line 447, in _build_localename language, encoding = localetuple ValueError: too many values to unpack To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/909256/+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 871047] Re: Can no longer set screen to lock when lid closed
I found the following workaround: http://askubuntu.com/questions/64570/how-do-i-configure-the-screen-to- lock-when-i-close-the-lid but it doesn't work... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/871047 Title: Can no longer set screen to lock when lid closed Status in “gnome-power-manager” package in Ubuntu: Confirmed Bug description: Before, with Gnome 2, I've configured it for when I close the laptop lid it lock the screen demanding the password. It's because sometimes I go to any places publics or with my friends and I don't want to have the PC trolled when I leave it for a while. Now, with Ubuntu 11.10, the gnome-screensaver is deleted, so when I select the blank option at org.gnome.settings-daemon.plugins.power lid-close-ac-action with dconf-editor, only it puts the screen black, but it doesn't block the screen because before the gnome- screensaver was the responsible of doing it and with Gnome 3 and Unity it dissapears. It's possible to add and lock-screen option that executes the lock screen command? Because I think that to close the screen is a better gesture to make sure that you've locked it more than remember always to do Ctrl+Alt+L. See also bug 888330, the equivalent for blanking the screen. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-power-manager 3.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu2 Architecture: amd64 Date: Sun Oct 9 02:08:57 2011 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GnomeSessionSuspendInhibited: No InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20111006) MachineType: Dell Inc. XPS M1330 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic root=UUID=f2473a46-a5f1-46b1-8b14-e6677563f14b ro quiet splash nomodeset video=uvesafb:mode_option=1280x1024-24,mtrr=3,scroll=ywrap vt.handoff=7 SourcePackage: gnome-power-manager UpgradeStatus: Upgraded to oneiric on 2011-10-07 (1 days ago) dmi.bios.date: 12/26/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0U8042 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd12/26/2008:svnDellInc.:pnXPSM1330:pvr:rvnDellInc.:rn0U8042:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: XPS M1330 dmi.sys.vendor: Dell Inc. gnome-power-bugreport: Error: [Errno 2] No existe el archivo o el directorio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/871047/+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
