[Desktop-packages] [Bug 2061981] Re: chromium fails to start with non-standard home directory
1)
user_name@computer:~$ stat /home/department/user_name/
File: /home/department/user_name/
Size: 267 Blocks: 289IO Block: 16384 directory
Device: 27h/39d Inode: 9542Links: 146
Access: (0755/drwxr-xr-x) Uid: (X/user_name) Gid:
(/default_group)
Access: 2024-03-20 14:50:40.921533172 +0100
Modify: 2024-04-17 18:20:30.872510781 +0200
Change: 2024-04-17 18:20:30.872510781 +0200
Birth: 2019-06-03 16:14:43.032386913 +0200
2) as far as I know, no apparmor specific denials.
The non-standard home directory is added to the apparmor ${HOMEDIRS} paramater
(see
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2061981/comments/3)
The only error message I get is:
user_name@computer:~$ chromium
cannot update snap namespace: cannot expand mount entry (none
$HOME/.local/share none x-snapd.kind=ensure-dir,x-snapd.must-exist-dir=$HOME 0
0): cannot use invalid home directory "/home/department/user_name": permission
denied
snap-update-ns failed with code 1
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/2061981
Title:
chromium fails to start with non-standard home directory
Status in chromium-browser package in Ubuntu:
Confirmed
Status in snapd package in Ubuntu:
Confirmed
Bug description:
CURRENT WORKAROUND
--
snap disconnect chromium:dot-local-share-applications
snap disconnect chromium:dot-local-share-icons
Those are just "quality of life" interfaces (c.f. LP:1732482) that
most users probably do not even use, disconnecting them will cause no
breakage. (Of course, a proper diagnosis and fix is due.)
ORIGINAL REPORT
---
cannot update snap namespace: cannot expand mount entry (none
$HOME/.local/share none x-snapd.kind=ensure-dir,x-snapd.must-exist-
dir=$HOME 0 0): cannot use invalid home directory
"/home/department/user_name": permission denied
Fails to start on Ubuntu 22.04 for users with 'non-standard' home directory
/home/department/user_name
Used to work fine up to last week.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: chromium-browser 1:85.0.4183.83-0ubuntu2.22.04.1
ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13
Uname: Linux 6.5.0-27-generic x86_64
NonfreeKernelModules: zfs nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: XFCE
Date: Wed Apr 17 10:32:18 2024
InstallationDate: Installed on 2017-03-24 (2580 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
Snap.Changes:
ID Status Spawn Ready Summary
206 Error 2024-04-16T19:08:43+02:00 2024-04-16T19:16:51+02:00 Remove
"chromium" snap
207 Done2024-04-16T19:17:27+02:00 2024-04-16T19:18:44+02:00 Remove
"chromium" snap
208 Done2024-04-16T19:18:46+02:00 2024-04-16T19:19:47+02:00 Install
"chromium" snap
209 Done2024-04-17T10:31:58+02:00 2024-04-17T10:32:02+02:00 Connect
chromium:password-manager-service to snapd:password-manager-service
SourcePackage: chromium-browser
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2061981/+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 2061981] Re: chromium fails to start with non-standard home directory
Reverting snapd fixes it for me too on multiple computers. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2061981 Title: chromium fails to start with non-standard home directory Status in chromium-browser package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Bug description: CURRENT WORKAROUND -- snap disconnect chromium:dot-local-share-applications snap disconnect chromium:dot-local-share-icons Those are just "quality of life" interfaces (c.f. LP:1732482) that most users probably do not even use, disconnecting them will cause no breakage. (Of course, a proper diagnosis and fix is due.) ORIGINAL REPORT --- cannot update snap namespace: cannot expand mount entry (none $HOME/.local/share none x-snapd.kind=ensure-dir,x-snapd.must-exist- dir=$HOME 0 0): cannot use invalid home directory "/home/department/user_name": permission denied Fails to start on Ubuntu 22.04 for users with 'non-standard' home directory /home/department/user_name Used to work fine up to last week. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: chromium-browser 1:85.0.4183.83-0ubuntu2.22.04.1 ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Wed Apr 17 10:32:18 2024 InstallationDate: Installed on 2017-03-24 (2580 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Snap.Changes: ID Status Spawn Ready Summary 206 Error 2024-04-16T19:08:43+02:00 2024-04-16T19:16:51+02:00 Remove "chromium" snap 207 Done2024-04-16T19:17:27+02:00 2024-04-16T19:18:44+02:00 Remove "chromium" snap 208 Done2024-04-16T19:18:46+02:00 2024-04-16T19:19:47+02:00 Install "chromium" snap 209 Done2024-04-17T10:31:58+02:00 2024-04-17T10:32:02+02:00 Connect chromium:password-manager-service to snapd:password-manager-service SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2061981/+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 2061981] Re: chromium fails to start with non-standard home directory
I don't have an encrypted home directory (though it is on a ZFS filesystem, but that one is also NOT encrypted). W. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2061981 Title: chromium fails to start with non-standard home directory Status in chromium-browser package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Bug description: chromium 123.0.6312.122 2821 latest/stablecanonical cannot update snap namespace: cannot expand mount entry (none $HOME/.local/share none x-snapd.kind=ensure-dir,x-snapd.must-exist- dir=$HOME 0 0): cannot use invalid home directory "/home/department/user_name": permission denied Fails to start on Ubuntu 22.04 for users with 'non-standard' home directory /home/department/user_name Used to work fine up to last week. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: chromium-browser 1:85.0.4183.83-0ubuntu2.22.04.1 ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Wed Apr 17 10:32:18 2024 InstallationDate: Installed on 2017-03-24 (2580 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Snap.Changes: ID Status Spawn Ready Summary 206 Error 2024-04-16T19:08:43+02:00 2024-04-16T19:16:51+02:00 Remove "chromium" snap 207 Done2024-04-16T19:17:27+02:00 2024-04-16T19:18:44+02:00 Remove "chromium" snap 208 Done2024-04-16T19:18:46+02:00 2024-04-16T19:19:47+02:00 Install "chromium" snap 209 Done2024-04-17T10:31:58+02:00 2024-04-17T10:32:02+02:00 Connect chromium:password-manager-service to snapd:password-manager-service SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2061981/+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 2061981] Re: chromium fails to start with non-standard home directory
PS: Can't revert as I uninstalled and reinstalled chromium yesterday when I first encountered the problem. user_name@computer:~$ sudo snap revert chromium error: cannot revert "chromium": no revision to revert to -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2061981 Title: chromium fails to start with non-standard home directory Status in chromium-browser package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Bug description: chromium 123.0.6312.122 2821 latest/stablecanonical cannot update snap namespace: cannot expand mount entry (none $HOME/.local/share none x-snapd.kind=ensure-dir,x-snapd.must-exist- dir=$HOME 0 0): cannot use invalid home directory "/home/department/user_name": permission denied Fails to start on Ubuntu 22.04 for users with 'non-standard' home directory /home/department/user_name Used to work fine up to last week. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: chromium-browser 1:85.0.4183.83-0ubuntu2.22.04.1 ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Wed Apr 17 10:32:18 2024 InstallationDate: Installed on 2017-03-24 (2580 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Snap.Changes: ID Status Spawn Ready Summary 206 Error 2024-04-16T19:08:43+02:00 2024-04-16T19:16:51+02:00 Remove "chromium" snap 207 Done2024-04-16T19:17:27+02:00 2024-04-16T19:18:44+02:00 Remove "chromium" snap 208 Done2024-04-16T19:18:46+02:00 2024-04-16T19:19:47+02:00 Install "chromium" snap 209 Done2024-04-17T10:31:58+02:00 2024-04-17T10:32:02+02:00 Connect chromium:password-manager-service to snapd:password-manager-service SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2061981/+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 2061981] Re: chromium fails to start with non-standard home directory
user_name@computer:~$ snap connections chromium | grep personal-files personal-fileschromium:chromium-config :personal-files - personal-fileschromium:dot-local-share-applications :personal-files - personal-fileschromium:dot-local-share-icons :personal-files - disconnecting "chromium:dot-local-share-applications" and "chromium:dot-local-share-icons" seems to fix the problem. Thanks! W;-) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2061981 Title: chromium fails to start with non-standard home directory Status in chromium-browser package in Ubuntu: Confirmed Status in snapd package in Ubuntu: New Bug description: chromium 123.0.6312.122 2821 latest/stablecanonical cannot update snap namespace: cannot expand mount entry (none $HOME/.local/share none x-snapd.kind=ensure-dir,x-snapd.must-exist- dir=$HOME 0 0): cannot use invalid home directory "/home/department/user_name": permission denied Fails to start on Ubuntu 22.04 for users with 'non-standard' home directory /home/department/user_name Used to work fine up to last week. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: chromium-browser 1:85.0.4183.83-0ubuntu2.22.04.1 ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Wed Apr 17 10:32:18 2024 InstallationDate: Installed on 2017-03-24 (2580 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Snap.Changes: ID Status Spawn Ready Summary 206 Error 2024-04-16T19:08:43+02:00 2024-04-16T19:16:51+02:00 Remove "chromium" snap 207 Done2024-04-16T19:17:27+02:00 2024-04-16T19:18:44+02:00 Remove "chromium" snap 208 Done2024-04-16T19:18:46+02:00 2024-04-16T19:19:47+02:00 Install "chromium" snap 209 Done2024-04-17T10:31:58+02:00 2024-04-17T10:32:02+02:00 Connect chromium:password-manager-service to snapd:password-manager-service SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2061981/+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 2061981] Re: chromium fails to start with non-standard home directory
*** This bug is a duplicate of bug 1620771 ***
https://bugs.launchpad.net/bugs/1620771
As far as I can tell, snap and apparmor home directories are set
correctly:
user_name@computer:~$ sudo snap get system homedirs
[sudo] password for user_name:
/home/department/
user_name@computer:/home$ sudo grep -R department /etc/apparmor.d/
[sudo] password for user_name:
/etc/apparmor.d/tunables/home:@{HOMEDIRS}=/home/ /home/department/
/etc/apparmor.d/tunables/home.d/snapd:@{HOMEDIRS}+="/home/department/"
/etc/apparmor.d/tunables/home.d/ubuntu:@{HOMEDIRS}+=/home/department/
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/2061981
Title:
chromium fails to start with non-standard home directory
Status in chromium-browser package in Ubuntu:
New
Bug description:
chromium 123.0.6312.122 2821 latest/stablecanonical
cannot update snap namespace: cannot expand mount entry (none
$HOME/.local/share none x-snapd.kind=ensure-dir,x-snapd.must-exist-
dir=$HOME 0 0): cannot use invalid home directory
"/home/department/user_name": permission denied
Fails to start on Ubuntu 22.04 for users with 'non-standard' home directory
/home/department/user_name
Used to work fine up to last week.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: chromium-browser 1:85.0.4183.83-0ubuntu2.22.04.1
ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13
Uname: Linux 6.5.0-27-generic x86_64
NonfreeKernelModules: zfs nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: XFCE
Date: Wed Apr 17 10:32:18 2024
InstallationDate: Installed on 2017-03-24 (2580 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
Snap.Changes:
ID Status Spawn Ready Summary
206 Error 2024-04-16T19:08:43+02:00 2024-04-16T19:16:51+02:00 Remove
"chromium" snap
207 Done2024-04-16T19:17:27+02:00 2024-04-16T19:18:44+02:00 Remove
"chromium" snap
208 Done2024-04-16T19:18:46+02:00 2024-04-16T19:19:47+02:00 Install
"chromium" snap
209 Done2024-04-17T10:31:58+02:00 2024-04-17T10:32:02+02:00 Connect
chromium:password-manager-service to snapd:password-manager-service
SourcePackage: chromium-browser
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2061981/+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 2061981] Re: chromium fails to start with non-standard home directory
*** This bug is a duplicate of bug 1620771 *** https://bugs.launchpad.net/bugs/1620771 Not a duplicate It's specific to the latest chromium snap update: it worked fine last week. (using chromium only for specific sites. The firefox-esr PPA is my daily driver). Other snaps don't have this problem. They're still working as they did last week. And I'm not the only one, See also: https://forum.snapcraft.io/t/chromium-cannot-update-snap-namespace-cannot-expand-mount-entry-none-home-local-share-none-x-snapd-kind-ensure-dir-x-snapd-must-exist-dir-home-0-0-cannot-use-invalid-home-directory/39764 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2061981 Title: chromium fails to start with non-standard home directory Status in chromium-browser package in Ubuntu: New Bug description: chromium 123.0.6312.122 2821 latest/stablecanonical cannot update snap namespace: cannot expand mount entry (none $HOME/.local/share none x-snapd.kind=ensure-dir,x-snapd.must-exist- dir=$HOME 0 0): cannot use invalid home directory "/home/department/user_name": permission denied Fails to start on Ubuntu 22.04 for users with 'non-standard' home directory /home/department/user_name Used to work fine up to last week. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: chromium-browser 1:85.0.4183.83-0ubuntu2.22.04.1 ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Wed Apr 17 10:32:18 2024 InstallationDate: Installed on 2017-03-24 (2580 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Snap.Changes: ID Status Spawn Ready Summary 206 Error 2024-04-16T19:08:43+02:00 2024-04-16T19:16:51+02:00 Remove "chromium" snap 207 Done2024-04-16T19:17:27+02:00 2024-04-16T19:18:44+02:00 Remove "chromium" snap 208 Done2024-04-16T19:18:46+02:00 2024-04-16T19:19:47+02:00 Install "chromium" snap 209 Done2024-04-17T10:31:58+02:00 2024-04-17T10:32:02+02:00 Connect chromium:password-manager-service to snapd:password-manager-service SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2061981/+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 2061981] [NEW] chromium fails to start with non-standard home directory
Public bug reported: chromium 123.0.6312.122 2821 latest/stablecanonical cannot update snap namespace: cannot expand mount entry (none $HOME/.local/share none x-snapd.kind=ensure-dir,x-snapd.must-exist- dir=$HOME 0 0): cannot use invalid home directory "/home/department/user_name": permission denied Fails to start on Ubuntu 22.04 for users with 'non-standard' home directory /home/department/user_name Used to work fine up to last week. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: chromium-browser 1:85.0.4183.83-0ubuntu2.22.04.1 ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Wed Apr 17 10:32:18 2024 InstallationDate: Installed on 2017-03-24 (2580 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Snap.Changes: ID Status Spawn Ready Summary 206 Error 2024-04-16T19:08:43+02:00 2024-04-16T19:16:51+02:00 Remove "chromium" snap 207 Done2024-04-16T19:17:27+02:00 2024-04-16T19:18:44+02:00 Remove "chromium" snap 208 Done2024-04-16T19:18:46+02:00 2024-04-16T19:19:47+02:00 Install "chromium" snap 209 Done2024-04-17T10:31:58+02:00 2024-04-17T10:32:02+02:00 Connect chromium:password-manager-service to snapd:password-manager-service SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2061981 Title: chromium fails to start with non-standard home directory Status in chromium-browser package in Ubuntu: New Bug description: chromium 123.0.6312.122 2821 latest/stablecanonical cannot update snap namespace: cannot expand mount entry (none $HOME/.local/share none x-snapd.kind=ensure-dir,x-snapd.must-exist- dir=$HOME 0 0): cannot use invalid home directory "/home/department/user_name": permission denied Fails to start on Ubuntu 22.04 for users with 'non-standard' home directory /home/department/user_name Used to work fine up to last week. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: chromium-browser 1:85.0.4183.83-0ubuntu2.22.04.1 ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Wed Apr 17 10:32:18 2024 InstallationDate: Installed on 2017-03-24 (2580 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Snap.Changes: ID Status Spawn Ready Summary 206 Error 2024-04-16T19:08:43+02:00 2024-04-16T19:16:51+02:00 Remove "chromium" snap 207 Done2024-04-16T19:17:27+02:00 2024-04-16T19:18:44+02:00 Remove "chromium" snap 208 Done2024-04-16T19:18:46+02:00 2024-04-16T19:19:47+02:00 Install "chromium" snap 209 Done2024-04-17T10:31:58+02:00 2024-04-17T10:32:02+02:00 Connect chromium:password-manager-service to snapd:password-manager-service SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2061981/+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 2017762] Re: GLX apps fail to run in X2Go remote desktop
** Also affects: mesa (Debian) Importance: Undecided Status: New ** Also affects: mesa (Fedora) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2017762 Title: GLX apps fail to run in X2Go remote desktop Status in mesa package in Ubuntu: New Status in mesa package in Debian: New Status in mesa package in Fedora: New Bug description: GLX apps fail to run on Ubuntu LTS 22.04. They used to run fine on Ubuntu LTS 20.04 USER@COMPUTER:~$ glxgears X Error of failed request: GLXUnsupportedPrivateRequest Major opcode of failed request: 143 (GLX) Minor opcode of failed request: 17 (X_GLXVendorPrivateWithReply) Serial number of failed request: 32 Current serial number in output stream: 32 USER@COMPUTER:~$ glxinfo name of display: :50.0 X Error of failed request: GLXUnsupportedPrivateRequest Major opcode of failed request: 143 (GLX) Minor opcode of failed request: 17 (X_GLXVendorPrivateWithReply) Serial number of failed request: 27 Current serial number in output stream: 27 Manually downgrading to mesa-21.x from the Ubuntu 20.04 repository solves the problem: sudo apt purge libgl1-amber-dri sudo dpkg -i \ libegl-mesa0_21.2.6-0ubuntu0.1~20.04.2_amd64.deb \ libgbm1_21.2.6-0ubuntu0.1~20.04.2_amd64.deb \ libgl1-mesa-dri_21.2.6-0ubuntu0.1~20.04.2_amd64.deb \ libglapi-mesa_21.2.6-0ubuntu0.1~20.04.2_amd64.deb \ libglx-mesa0_21.2.6-0ubuntu0.1~20.04.2_amd64.deb \ libxatracker2_21.2.6-0ubuntu0.1~20.04.2_amd64.deb \ mesa-va-drivers_21.2.6-0ubuntu0.1~20.04.2_amd64.deb \ mesa-vdpau-drivers_21.2.6-0ubuntu0.1~20.04.2_amd64.deb \ mesa-vulkan-drivers_21.2.6-0ubuntu0.1~20.04.2_amd64.deb sudo apt-mark hold \ libegl-mesa0 \ libgl1-mesa-dri \ libglapi-mesa \ libglx-mesa0 \ mesa-va-drivers \ mesa-vdpau-drivers \ mesa-vulkan-drivers \ libgbm1 \ libxatracker2 There's also a discussion about this on the X2Go user list, but no solution so far (just the workaround to downgrade to mesa 21.x): https://lists.x2go.org/pipermail/x2go-user/2022-June/006825.html Similar problems on Ubuntu 23.-04 with mesa 23.x, although there the error message is different. Tested on several computers with connections from different Linux, Windows and Mac clients. All show the same behaviour: no go with mesa-22.x on Ubuntu-22.04. Success with downgraded mesa. How to replicate: - install ubuntu 22.04 on real hardware or on a VM (tested with QEMU/virt-manager) - apt-get install x2goserver-xsession mesa-utils - make X2Go connection from another client to new install - run 'glxinfo' -> GLX error - downgrade mesa to v. 21.x -> no GLX error ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libgl1-mesa-glx 22.2.5-0ubuntu0.1~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-40.41~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..07.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.108.03 Thu Oct 20 05:10:45 UTC 2022 GCC version: gcc version 11.3.0 (Ubuntu 11.3.0-1ubuntu1~22.04) ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: XFCE Date: Wed Apr 26 10:41:42 2023 DistUpgraded: 2022-05-12 16:08:31,041 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/510.108.03, 5.19.0-38-generic, x86_64: installed nvidia/510.108.03, 5.19.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GM204GL [Quadro M4000] [10de:13f1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GM204GL [Quadro M4000] [10de:1153] InstallationDate: Installed on 2017-03-24 (2223 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. Precision WorkStation 690 ProcEnviron: LANGUAGE=en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-40-generic root=UUID=a6888b05-975d-4ffe-9cf1-a37038661267 ro quiet splash vt.handoff=7 SourcePackage: mesa UpgradeStatus: Upgraded to jammy on 2022-05-12 (348 days ago) dm
[Desktop-packages] [Bug 2017762] [NEW] GLX apps fail to run in X2Go remote desktop
Public bug reported: GLX apps fail to run on Ubuntu LTS 22.04. They used to run fine on Ubuntu LTS 20.04 USER@COMPUTER:~$ glxgears X Error of failed request: GLXUnsupportedPrivateRequest Major opcode of failed request: 143 (GLX) Minor opcode of failed request: 17 (X_GLXVendorPrivateWithReply) Serial number of failed request: 32 Current serial number in output stream: 32 USER@COMPUTER:~$ glxinfo name of display: :50.0 X Error of failed request: GLXUnsupportedPrivateRequest Major opcode of failed request: 143 (GLX) Minor opcode of failed request: 17 (X_GLXVendorPrivateWithReply) Serial number of failed request: 27 Current serial number in output stream: 27 Manually downgrading to mesa-21.x from the Ubuntu 20.04 repository solves the problem: sudo apt purge libgl1-amber-dri sudo dpkg -i \ libegl-mesa0_21.2.6-0ubuntu0.1~20.04.2_amd64.deb \ libgbm1_21.2.6-0ubuntu0.1~20.04.2_amd64.deb \ libgl1-mesa-dri_21.2.6-0ubuntu0.1~20.04.2_amd64.deb \ libglapi-mesa_21.2.6-0ubuntu0.1~20.04.2_amd64.deb \ libglx-mesa0_21.2.6-0ubuntu0.1~20.04.2_amd64.deb \ libxatracker2_21.2.6-0ubuntu0.1~20.04.2_amd64.deb \ mesa-va-drivers_21.2.6-0ubuntu0.1~20.04.2_amd64.deb \ mesa-vdpau-drivers_21.2.6-0ubuntu0.1~20.04.2_amd64.deb \ mesa-vulkan-drivers_21.2.6-0ubuntu0.1~20.04.2_amd64.deb sudo apt-mark hold \ libegl-mesa0 \ libgl1-mesa-dri \ libglapi-mesa \ libglx-mesa0 \ mesa-va-drivers \ mesa-vdpau-drivers \ mesa-vulkan-drivers \ libgbm1 \ libxatracker2 There's also a discussion about this on the X2Go user list, but no solution so far (just the workaround to downgrade to mesa 21.x): https://lists.x2go.org/pipermail/x2go-user/2022-June/006825.html Similar problems on Ubuntu 23.-04 with mesa 23.x, although there the error message is different. Tested on several computers with connections from different Linux, Windows and Mac clients. All show the same behaviour: no go with mesa-22.x on Ubuntu-22.04. Success with downgraded mesa. How to replicate: - install ubuntu 22.04 on real hardware or on a VM (tested with QEMU/virt-manager) - apt-get install x2goserver-xsession mesa-utils - make X2Go connection from another client to new install - run 'glxinfo' -> GLX error - downgrade mesa to v. 21.x -> no GLX error ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libgl1-mesa-glx 22.2.5-0ubuntu0.1~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-40.41~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..07.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.108.03 Thu Oct 20 05:10:45 UTC 2022 GCC version: gcc version 11.3.0 (Ubuntu 11.3.0-1ubuntu1~22.04) ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: XFCE Date: Wed Apr 26 10:41:42 2023 DistUpgraded: 2022-05-12 16:08:31,041 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/510.108.03, 5.19.0-38-generic, x86_64: installed nvidia/510.108.03, 5.19.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GM204GL [Quadro M4000] [10de:13f1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GM204GL [Quadro M4000] [10de:1153] InstallationDate: Installed on 2017-03-24 (2223 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. Precision WorkStation 690 ProcEnviron: LANGUAGE=en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-40-generic root=UUID=a6888b05-975d-4ffe-9cf1-a37038661267 ro quiet splash vt.handoff=7 SourcePackage: mesa UpgradeStatus: Upgraded to jammy on 2022-05-12 (348 days ago) dmi.bios.date: 04/25/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0MY171 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/25/2008:svnDellInc.:pnPrecisionWorkStation690:pvr:rvnDellInc.:rn0MY171:rvrA01:cvnDellInc.:ct7:cvr:sku: dmi.product.name: Precision WorkStation 690 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.5-0ubuntu0.1~22.04.1 version.nvidia-graphics-drivers: nvidia-graphics-driver
[Desktop-packages] [Bug 2012863] [NEW] libayatana-appindicator3-1 crashes applications with a segfault failt
Public bug reported: This library causes random applications that make use of this to randomly crash with a segfault like: segfault at 800031ca000 ip 7f284cba4dc5 sp 7ffdd5354630 error 4 in libayatana-appindicator3.so.1.0.0[7f284cba1000+6000] likely on CPU 2 (core 1, socket 0) This problem doesn't exist, if the package is build locally on the machine and installed from a locally build deb packages. This problem is is happening on every ubuntu series that is released since Jammy (including Jammy). Since a locally build package resolves the problem, I wonder if there is some hardware optimization that happens on build time, causing problems with intel vs amd (the affected machine is running an Ryzen 7 pro 5850u) ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: libayatana-appindicator3-1 0.5.92-1 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Mar 27 15:00:02 2023 InstallationDate: Installed on 2022-11-10 (136 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: libayatana-appindicator UpgradeStatus: Upgraded to lunar on 2023-02-21 (34 days ago) ** Affects: libayatana-appindicator (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libayatana-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/2012863 Title: libayatana-appindicator3-1 crashes applications with a segfault failt Status in libayatana-appindicator package in Ubuntu: New Bug description: This library causes random applications that make use of this to randomly crash with a segfault like: segfault at 800031ca000 ip 7f284cba4dc5 sp 7ffdd5354630 error 4 in libayatana-appindicator3.so.1.0.0[7f284cba1000+6000] likely on CPU 2 (core 1, socket 0) This problem doesn't exist, if the package is build locally on the machine and installed from a locally build deb packages. This problem is is happening on every ubuntu series that is released since Jammy (including Jammy). Since a locally build package resolves the problem, I wonder if there is some hardware optimization that happens on build time, causing problems with intel vs amd (the affected machine is running an Ryzen 7 pro 5850u) ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: libayatana-appindicator3-1 0.5.92-1 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Mar 27 15:00:02 2023 InstallationDate: Installed on 2022-11-10 (136 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: libayatana-appindicator UpgradeStatus: Upgraded to lunar on 2023-02-21 (34 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libayatana-appindicator/+bug/2012863/+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 1843392] Re: [snap] smart card reader no longer works
Whoops, sorry, I didn't mean to do that :) Basically though, this is causing issues for users in, e.g., Belgium, who want to do their tax declaration using Ubuntu and their electronic ID card. We are currently guiding users to use a non-snap browser (see https://eid.belgium.be/en/faq/why-it-not-possible-use-eid-software-snap- andor-flatpak#7636), and that's just sad. Comment #1 mentions a proposal to possibly resolve this. Since it explicitly asks for feedback, here is some (belated) feedback: First, PKCS#11 is about more than just smartcards. While allowing access to the pcscd socket from within the confined environment might allow some PKCS#11 modules to work, using this as a solution assumes all PKCS#11 modules use PC/SC as a backend API, and that's a wild assumption which is probably not true for everything. PKCS#11 is a generic cryptographic plug-in API, which allows hardware crypto modules of any kind (e.g., USB tokens, Networked HSMs, PCI(e) crypto accelerator boards, TPM modules, etc etc) to be plugged into anything. libnss uses it mostly for smartcards, and all browsers on Linux do so as well, but it can also be used by libreoffice and evolution to sign documents, it is extensively used by OpenDNSSEC for its crypto operations (going so far as providing a "SoftHSM" pkcs#11 module and not having native crypto), OpenSSH has had PKCS#11 code for a while to read and use certificates, and there are ways to hook PKCS#11 up to OpenSSL allowing for a large number of other applications to use HSMs. PKCS#11 modules could possibly access the hardware that they're written for using PC/SC (which this proposal could possibly work for, as long as the libpcsclite.so inside the snap and the pcscd outside the snap are sufficiently in sync), but this would not help PKCS#11 modules for USB tokens, TPM modules, PCI crypto accelerators, or possibly networked systems (depending on how the host application is confined). Apart from hardware, PKCS#11 modules may sometimes need to do other things as well. E.g., the Belgian eID middleware needs to occasionally show certain messages to the user, for which it uses the GnuPG pinentry framework to show a dialog box that integrates with the user's UI. Unless this is explicitly allowed by the snap, this won't work. There might be other similar issues with other PKCS#11 modules, which means that running them in a confined environment might just not work. So while this may be a solution for some PKCS#11 modules, it will not be a solution for all. Additionally, the PKCS#11 modules need to be installed and registered in host applications. For NSS-based applications, this means they need to be installed using "modutil". Chrome doesn't even *have* any UI to install PKCS#11 modules; Firefox does, but it's so basic and confusing to users that I developed a "browser.pkcs11" add-on API for Firefox to allow modules to be registered using an add-on. These work with native manifests (intentionally similar to native messaging manifests) and expect the PKCS#11 module to be in the location as specified by the manifest. Libreoffice just gave up and looks for a Firefox, Thunderbird, or Chromium configuration directory and reuses that. As such, just allowing access to a PKCS#11 module is not going to be sufficient if the user has no easy way to register the PKCS#11 modules. An alternate method (that I suggested at https://github.com/flatpak/xdg- desktop-portal/issues/662) is to use p11-kit-proxy to provide a bridge between the confined system and PKCS#11 modules. p11-kit-proxy could then communicate with the unconfined world using a dbus service. A proof-of-concept implementation of this exists (see the github link), and the only reason why it's not in common use right now is that p11-kit-proxy is not commonly added to, and enabled in, snaps. ** Bug watch added: github.com/flatpak/xdg-desktop-portal/issues #662 https://github.com/flatpak/xdg-desktop-portal/issues/662 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1843392 Title: [snap] smart card reader no longer works Status in chromium-browser package in Ubuntu: Confirmed Bug description: chromium uses the Netscape Cryptographic Module to access smartcards for authentication purposes. This stopped working when switching to the snap version. Chromium would normally access the setup in ~/.pki/nssdb/pkcs11.txt That file would refer to a library used to access the smart card. I.e /usr/lib/x86_64-linux-gnu/pkcs11/opensc- pkcs11.so The problem can be bypassed by manually launching chromium via: /snap/chromium/current/usr/lib/chromium-browser/chrome To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1843392/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscrib
[Desktop-packages] [Bug 1843392] Re: [snap] smart card reader no longer works
** Also affects: firefox (Ubuntu) Importance: Undecided Status: New ** No longer affects: firefox (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1843392 Title: [snap] smart card reader no longer works Status in chromium-browser package in Ubuntu: Confirmed Bug description: chromium uses the Netscape Cryptographic Module to access smartcards for authentication purposes. This stopped working when switching to the snap version. Chromium would normally access the setup in ~/.pki/nssdb/pkcs11.txt That file would refer to a library used to access the smart card. I.e /usr/lib/x86_64-linux-gnu/pkcs11/opensc- pkcs11.so The problem can be bypassed by manually launching chromium via: /snap/chromium/current/usr/lib/chromium-browser/chrome To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1843392/+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 1976389] [NEW] package chromium-browser 101.0.4951.64-0ubuntu0.18.04.1 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error
Public bug reported: do-release-upgrade from bionic (18.04) to focal (20.04) crashes on chromium snap installation ProblemType: Package DistroRelease: Ubuntu 20.04 Package: chromium-browser 101.0.4951.64-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 5.4.0-113.127~18.04.1-generic 5.4.181 Uname: Linux 5.4.0-113-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 Date: Tue May 31 17:07:50 2022 Desktop-Session: 'None' 'None' 'None' Env: 'None' 'None' ErrorMessage: new chromium-browser package pre-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2014-02-14 (3027 days ago) InstallationMedia: Xubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130822) InstalledPlugins: /usr/lib/mozilla/plugins: => npwrapper.nppdf.so (size: 142552 bytes, mtime: Fri Feb 14 16:37:40 2014) Load-Avg-1min: 0.79 Load-Processes-Running-Percent: 0.2% MachineType: Dell Inc. Precision T7610 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-113-generic root=UUID=101706f9-25ad-41c2-865a-d4c215ce639f ro quiet splash nomdmonddf nomdmonisw vt.handoff=1 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 SourcePackage: chromium-browser Title: package chromium-browser 101.0.4951.64-0ubuntu0.18.04.1 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2022-05-31 (0 days ago) dmi.bios.date: 09/05/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0NK70N dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd09/05/2013:svnDellInc.:pnPrecisionT7610:pvr01:rvnDellInc.:rn0NK70N:rvrA03:cvnDellInc.:ct7:cvr: dmi.product.name: Precision T7610 dmi.product.sku: Precision T7610 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.chromium-browser: [deleted] ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1976389 Title: package chromium-browser 101.0.4951.64-0ubuntu0.18.04.1 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 Status in chromium-browser package in Ubuntu: New Bug description: do-release-upgrade from bionic (18.04) to focal (20.04) crashes on chromium snap installation ProblemType: Package DistroRelease: Ubuntu 20.04 Package: chromium-browser 101.0.4951.64-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 5.4.0-113.127~18.04.1-generic 5.4.181 Uname: Linux 5.4.0-113-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 Date: Tue May 31 17:07:50 2022 Desktop-Session: 'None' 'None' 'None' Env: 'None' 'None' ErrorMessage: new chromium-browser package pre-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2014-02-14 (3027 days ago) InstallationMedia: Xubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130822) InstalledPlugins: /usr/lib/mozilla/plugins: => npwrapper.nppdf.so (size: 142552 bytes, mtime: Fri Feb 14 16:37:40 2014) Load-Avg-1min: 0.79 Load-Processes-Running-Percent: 0.2% MachineType: Dell Inc. Precision T7610 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-113-generic root=UUID=101706f9-25ad-41c2-865a-d4c215ce639f ro quiet splash nomdmonddf nomdmonisw vt.handoff=1 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 SourcePackage: chromium-browser Title: package chromium-browser 101.0.4951.64-0ubuntu0.18.04.1 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2022-05-31 (0 days ago) dmi.bios.date: 09/05/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0NK70N dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd09/05/2013:svnDellInc.:pnPrecisionT7610:pvr01:rvnDellInc.:rn0NK70N:rvrA03:cvnDellInc.:ct7:cvr: dmi.product.name: Precision T7610 dmi.product.sku: Precision T7610 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.chromium-browser: [deleted] To manage notifications about this bug go to: htt
[Desktop-packages] [Bug 1973070] [NEW] package libreoffice-common 1:7.3.2-0ubuntu2 failed to install/upgrade: installed libreoffice-common package post-installation script subprocess returned error ex
Public bug reported: do-release-upgrade from 20.04 to 22.04 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libreoffice-common 1:7.3.2-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-110.124-generic 5.4.181 Uname: Linux 5.4.0-110-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed May 11 20:59:29 2022 ErrorMessage: installed libreoffice-common package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2017-03-24 (1874 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2 apt 2.4.5 SourcePackage: libreoffice Title: package libreoffice-common 1:7.3.2-0ubuntu2 failed to install/upgrade: installed libreoffice-common package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2022-05-11 (0 days ago) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy need-duplicate-check third-party-packages -- 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/1973070 Title: package libreoffice-common 1:7.3.2-0ubuntu2 failed to install/upgrade: installed libreoffice-common package post-installation script subprocess returned error exit status 1 Status in libreoffice package in Ubuntu: New Bug description: do-release-upgrade from 20.04 to 22.04 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libreoffice-common 1:7.3.2-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-110.124-generic 5.4.181 Uname: Linux 5.4.0-110-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed May 11 20:59:29 2022 ErrorMessage: installed libreoffice-common package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2017-03-24 (1874 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2 apt 2.4.5 SourcePackage: libreoffice Title: package libreoffice-common 1:7.3.2-0ubuntu2 failed to install/upgrade: installed libreoffice-common package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2022-05-11 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1973070/+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 1824874] Re: undismissable, unclickable authentication dialog left on screen (top-left corner) after policykit authentication [pushModal: invocation of begin_modal failed]
Problem still present. Just experienced it on Ubuntu 20.04.1 LTS. The provieded workaround to get it removed fixed it.. for now. -- 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/1824874 Title: undismissable, unclickable authentication dialog left on screen (top- left corner) after policykit authentication [pushModal: invocation of begin_modal failed] Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Triaged Bug description: In disco, when policykit prompted me for a password in order for update-manager to dispatch instructions to aptdaemon to perform package updates, the password dialog remained on the screen after I clicked 'authenticate'. The window is not clickable, it appears not to even be a window - mouse presses are received by the window underneath. The exception is that the 'cancel' button is active and receives mouse events - but clicking it does nothing. This may be a gnome-shell issue rather than policykit. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: policykit-1 0.105-25 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 15 13:14:33 2019 InstallationDate: Installed on 2010-09-24 (3125 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) SourcePackage: policykit-1 UpgradeStatus: Upgraded to disco on 2019-04-11 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1824874/+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 1741768] Re: U2F FIDO authentication doesn't work
Tested this today, via the github site, and both authentication and the
registration of a new key fails. Logging I can find related to this in
/var/log/syslog is:
Jan 31 09:53:13 hyperion kernel: [605631.650563] audit: type=1400
audit(1580428393.744:1863): apparmor="DENIED" operation="open"
profile="/usr/lib/firefox/firefox{,*[^s][^h]}"
name="/sys/devices/virtual/misc/uhid/0005:046D:B01D.0013/hidraw/hidraw6/uevent"
pid=25081 comm=4950444C204261636B67726F756E64 requested_mask="r"
denied_mask="r" fsuid=1000 ouid=0
--
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/1741768
Title:
U2F FIDO authentication doesn't work
Status in firefox package in Ubuntu:
Confirmed
Bug description:
I have a Yubico U2F security key. If I download the upstream Firefox
binary for 57.0.4 and go to https://demo.yubico.com/u2f?tab=register,
the test page works fine: I can register with a username/password, my
key starts blinking and I can touch it to validate.
If I go to the same page using the official Ubuntu package of Firefox,
the U2F device is not recognized and the page displays the following
error:
"""
Registration failed!
Make sure you have a U2F device connected, and try again.
Traceback (most recent call last):
File "/root/python-u2flib-server-demo/examples/yubiauth_server.py", line
161, in __call__
raise Exception("FIDO Client error: %s" % error)
Exception: FIDO Client error: 1 (OTHER ERROR)
"""
Note that in both cases, I did enable the required options in
"about:config" (as outlined in e.g. https://www.yubico.com/2017/11
/how-to-navigate-fido-u2f-in-firefox-quantum/).
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: firefox 57.0.4+build1-0ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.13.0-21.24~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-21-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia_uvm nvidia_drm
nvidia_modeset nvidia
AddonCompatCheckDisabled: False
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: antoine3844 F pulseaudio
/dev/snd/controlC1: antoine3844 F pulseaudio
BuildID: 20180104112904
Channel: Unavailable
CurrentDesktop: XFCE
Date: Sun Jan 7 17:32:38 2018
DefaultProfileIncompatibleExtensions: Default -
{972ce4c6-7e08-4474-a285-3208198ce6fd}
DefaultProfilePrefErrors: 'utf-8' codec can't decode byte 0xe9 in position
2410: invalid continuation byte
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2013-04-12 (1730 days ago)
InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130409)
MostRecentCrashID: bp-eb109c63-e3b5-4c21-a920-d262b2150407
Profile1Extensions: extensions.sqlite corrupt or missing
Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant
compatibility.ini or extensions.sqlite)
Profile1Locales: extensions.sqlite corrupt or missing
Profile1PrefSources: prefs.js
Profile1Themes: extensions.sqlite corrupt or missing
Profile2Extensions: extensions.sqlite corrupt or missing
Profile2IncompatibleExtensions: Unavailable (corrupt or non-existant
compatibility.ini or extensions.sqlite)
Profile2Locales: extensions.sqlite corrupt or missing
Profile2PrefSources: prefs.js
Profile2Themes: extensions.sqlite corrupt or missing
Profile3Extensions: extensions.sqlite corrupt or missing
Profile3IncompatibleExtensions: Unavailable (corrupt or non-existant
compatibility.ini or extensions.sqlite)
Profile3Locales: extensions.sqlite corrupt or missing
Profile3PrefSources: prefs.js
Profile3Themes: extensions.sqlite corrupt or missing
Profile4Extensions: extensions.sqlite corrupt or missing
Profile4IncompatibleExtensions: Unavailable (corrupt or non-existant
compatibility.ini or extensions.sqlite)
Profile4Locales: extensions.sqlite corrupt or missing
Profile4PrefSources: prefs.js
Profile4Themes: extensions.sqlite corrupt or missing
Profiles:
Profile0 (Default) - LastVersion=57.0.4/20180104112904 (In use)
Profile1 - LastVersion=57.0.4/20180104112904
Profile2 - LastVersion=57.0.4/20180104112904
Profile3 - LastVersion=57.0.3/20171227151400 (Out of date)
Profile4 - LastVersion=57.0.4/20180104112904 (In use)
RfKill:
RunningIncompatibleAddons: True
SourcePackage: firefox
UpgradeStatus: Upgraded to xenial on 2015-07-27 (894 days ago)
dmi.bios.date: 06/22/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1801
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8H67-M EVO
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
dm
[Desktop-packages] [Bug 1737750] Re: nvidia-graphics-drivers-304 304.137-0ubuntu2 ADT test failure with linux 4.15.0-1.2 [error: implicit declaration of function ‘init_timer’]
A 'backport' of "nvidia-340_340.106-0ubuntu3_amd64.deb" from Bionic should do the trick as this is fixed by NVidia in nvidia-340.106: http://www.nvidia.com/Download/driverResults.aspx/130042/en-us "Release Highlights: Fixed a compatibility problem between the nvidia.ko's Page Attribute Table (PAT) support and the kernel Page Table Isolation (PTI) patches." Forcing the installation of "nvidia-340_340.106-0ubuntu3_amd64.deb" from Bionic on Xenial seems to work: sudo dpkg -i --force-depends nvidia-340_340.106-0ubuntu3_amd64.deb This then needs a little massaging: sudo ln -s /usr/lib/nvidia-340/xorg /etc/alternatives/x86_64-linux-gnu_xorg_extra_modules sudo ln -s /etc/alternatives/x86_64-linux-gnu_xorg_extra_modules /usr/lib/x86_64-linux-gnu/xorg/extra-modules And commenting out ModulePath "/usr/lib/nvidia-340/xorg" in /usr/share/X11/xorg.conf.d/nvidia-drm-outputclass-ubuntu.conf -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1737750 Title: nvidia-graphics-drivers-304 304.137-0ubuntu2 ADT test failure with linux 4.15.0-1.2 [error: implicit declaration of function ‘init_timer’] Status in nvidia-graphics-drivers-304 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/amd64/n/nvidia-graphics-drivers-304/20171212_030744_5105c@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/i386/n/nvidia-graphics-drivers-304/20171212_014232_5105c@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1737750/+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 1768207] Re: gnome-control-center / Ubuntu settings takes 1 minute+ 100% CPU first time loading
@Tom didn't realize that - I'm having the exact same issues that sometimes a reboot is required after suspend (which I use heavily).. Didn't connect that with gnome-settings yet. -- 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/1768207 Title: gnome-control-center / Ubuntu settings takes 1 minute+ 100% CPU first time loading Status in gnome-control-center package in Ubuntu: Confirmed Bug description: First time starting gnome-control-center after login, it takes ~70seconds to load and 100%CPU. Only first time starting I get "nvc0_screen_create:906 - Error allocating PGRAPH context for M2MF: -16". In terminal "top" shows "gst-plugin-scan" is the offender. I installed two extensions initially but now all are switched off with same effect. Second and other times starting, all is normal Dell XPS 15, BIOS v1.9, Ubuntu 18.04LTS, *clean* install all default, just had to start nvidia to be able to login at all first time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1768207/+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 1768207] Re: gnome-control-center / Ubuntu settings takes 1 minute+ 100% CPU first time loading
An additional note is that this also seems to occur when I unlock my notebook and the settings is not yet open (but I used it before locking it). -- 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/1768207 Title: gnome-control-center / Ubuntu settings takes 1 minute+ 100% CPU first time loading Status in gnome-control-center package in Ubuntu: Confirmed Bug description: First time starting gnome-control-center after login, it takes ~70seconds to load and 100%CPU. Only first time starting I get "nvc0_screen_create:906 - Error allocating PGRAPH context for M2MF: -16". In terminal "top" shows "gst-plugin-scan" is the offender. I installed two extensions initially but now all are switched off with same effect. Second and other times starting, all is normal Dell XPS 15, BIOS v1.9, Ubuntu 18.04LTS, *clean* install all default, just had to start nvidia to be able to login at all first time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1768207/+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 1768207] Re: gnome-control-center / Ubuntu settings takes 1 minute+ 100% CPU first time loading
Also having this issue on my Acer aspire v3-772g with clean install on 18.04, although - no nvidia driver(s) installed. Really a clean install. I tried installing the nvidia driver, but then I came across a different issue, which seems to be related to bug #1752053. -- 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/1768207 Title: gnome-control-center / Ubuntu settings takes 1 minute+ 100% CPU first time loading Status in gnome-control-center package in Ubuntu: Confirmed Bug description: First time starting gnome-control-center after login, it takes ~70seconds to load and 100%CPU. Only first time starting I get "nvc0_screen_create:906 - Error allocating PGRAPH context for M2MF: -16". In terminal "top" shows "gst-plugin-scan" is the offender. I installed two extensions initially but now all are switched off with same effect. Second and other times starting, all is normal Dell XPS 15, BIOS v1.9, Ubuntu 18.04LTS, *clean* install all default, just had to start nvidia to be able to login at all first time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1768207/+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 1712283] Re: Cannot resolve DNS in artful daily
Today, I also ran into this issue. Wifi was working and I could successfully ping Google's DNS 8.8.8.8. However, pinging google.com didn't work: "Name or service not known" The workaround in comment #6 does the trick for me: sudo rm /etc/resolv.conf sudo ln -s /run/systemd/resolve/stub-resolv.conf /etc/resolv.conf -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1712283 Title: Cannot resolve DNS in artful daily Status in casper package in Ubuntu: Confirmed Status in livecd-rootfs package in Ubuntu: Confirmed Status in netcfg package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Triaged Status in systemd package in Ubuntu: Fix Released Bug description: in the current daily 21 Aug 2017, I can ping 8.8.8.8 from a live session / installed session - running on virtualbox 5.1.26. However I cannot ping google.com - "Name or service not known" Kind of difficult to run ubuntu-bug here without a fully functioning network. Happy to provide more details - please can someone guide me producing a much better bug-report? my zesty VM is working just fine. As of a week ago, my artful daily was working just fine also. * /etc/resolv.conf is empty file on most images built, which is not right, it should point to ../run/systemd/resolve/stub-resolv.conf. Should be fixed in image generation? systemd? * Adding a hack, to create /etc/resolv.conf if it does not exist, or is empty. src:systemd * network-manager does not consider that dns is managed by resolved if .53 is present in /etc/resolv.conf or if it points to stub- resolv.conf. src:network-manager * netcfg has integrtation w.r.t. /etc/resolv.conf and resolvconf. Needs checking / fixing * caster has resolvconf integration * livecd-rootfs has resolvconf integration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1712283/+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 1712283] Re: Cannot resolve DNS in artful daily
Forgot to mention, I have a fresh install from the daily artful image on 21st of September 2017. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1712283 Title: Cannot resolve DNS in artful daily Status in casper package in Ubuntu: Confirmed Status in livecd-rootfs package in Ubuntu: Confirmed Status in netcfg package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Triaged Status in systemd package in Ubuntu: Fix Released Bug description: in the current daily 21 Aug 2017, I can ping 8.8.8.8 from a live session / installed session - running on virtualbox 5.1.26. However I cannot ping google.com - "Name or service not known" Kind of difficult to run ubuntu-bug here without a fully functioning network. Happy to provide more details - please can someone guide me producing a much better bug-report? my zesty VM is working just fine. As of a week ago, my artful daily was working just fine also. * /etc/resolv.conf is empty file on most images built, which is not right, it should point to ../run/systemd/resolve/stub-resolv.conf. Should be fixed in image generation? systemd? * Adding a hack, to create /etc/resolv.conf if it does not exist, or is empty. src:systemd * network-manager does not consider that dns is managed by resolved if .53 is present in /etc/resolv.conf or if it points to stub- resolv.conf. src:network-manager * netcfg has integrtation w.r.t. /etc/resolv.conf and resolvconf. Needs checking / fixing * caster has resolvconf integration * livecd-rootfs has resolvconf integration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1712283/+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 1717339] [NEW] package gir1.2-soup-2.4:amd64 2.56.0-2ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attemptin
Public bug reported: message pops up ProblemType: Package DistroRelease: Ubuntu 17.04 Package: gir1.2-soup-2.4:amd64 2.56.0-2ubuntu0.1 ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 Date: Thu Sep 14 21:04:23 2017 DuplicateSignature: package:gir1.2-soup-2.4:amd64:2.56.0-2ubuntu0.1 Setting up imagemagick-6.q16 (8:6.9.7.4+dfsg-3ubuntu1.2) ... dpkg: error processing package gir1.2-soup-2.4:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-09-09 (5 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: libsoup2.4 Title: package gir1.2-soup-2.4:amd64 2.56.0-2ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libsoup2.4 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package zesty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libsoup2.4 in Ubuntu. https://bugs.launchpad.net/bugs/1717339 Title: package gir1.2-soup-2.4:amd64 2.56.0-2ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in libsoup2.4 package in Ubuntu: New Bug description: message pops up ProblemType: Package DistroRelease: Ubuntu 17.04 Package: gir1.2-soup-2.4:amd64 2.56.0-2ubuntu0.1 ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 Date: Thu Sep 14 21:04:23 2017 DuplicateSignature: package:gir1.2-soup-2.4:amd64:2.56.0-2ubuntu0.1 Setting up imagemagick-6.q16 (8:6.9.7.4+dfsg-3ubuntu1.2) ... dpkg: error processing package gir1.2-soup-2.4:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-09-09 (5 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: libsoup2.4 Title: package gir1.2-soup-2.4:amd64 2.56.0-2ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsoup2.4/+bug/1717339/+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 1711337] Re: Firefox crashes at start on armv7L after 55.0.1 update
I got the same problem on Raspberry Pi3 with Ubuntu Mate. -- 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/1711337 Title: Firefox crashes at start on armv7L after 55.0.1 update Status in firefox package in Ubuntu: Confirmed Bug description: Firefox always crashes when launched after the 55.0.1 update on an Orange Pi PC Plus (a single-board computer similar to a Raspberry Pi), even in safe mode. I did a fresh install of Armbian (a Ubuntu Xenial 16.04 re-spin for ARM single-board computer) on a similar board (Orange Pi Plus 2e), installed Firefox and experienced the same problem--it won't load without crashing. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: firefox 55.0.1+build2-0ubuntu0.16.04.2 Uname: Linux 3.4.113-sun8i armv7l AddonCompatCheckDisabled: False AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25. ApportVersion: 2.20.1-0ubuntu2.10 Architecture: armhf AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jim1138 F pulseaudio /dev/snd/controlC0: jim1138 F pulseaudio BuildID: 20170814194718 Card0.Amixer.info: Card hw:0 'audiocodec'/'audiocodec' Mixer name : '' Components : '' Controls : 12 Simple ctrls : 12 Card1.Amixer.info: Card hw:1 'sndhdmi'/'sndhdmi' Mixer name : '' Components : '' Controls : 1 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'hdmi audio format Function',0 Capabilities: enum Items: 'null' 'pcm' 'AC3' 'MPEG1' 'MP3' 'MPEG2' 'AAC' 'DTS' 'ATRAC' 'ONE_BIT_AUDIO' 'DOLBY_DIGITAL_PLUS' 'DTS_HD' 'MAT' 'WMAPRO' Item0: 'pcm' Channel: Unavailable CurrentDesktop: XFCE Date: Thu Aug 17 05:37:00 2017 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) IpRoute: default via 192.168.10.1 dev eth0 default via 192.168.10.1 dev wlan0 proto static metric 600 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.10.0/24 dev eth0 proto kernel scope link src 192.168.10.107 192.168.10.0/24 dev wlan0 proto kernel scope link src 192.168.10.108 metric 600 Locales: extensions.sqlite corrupt or missing PciMultimedia: PciNetwork: Profiles: Profile0 (Default) - LastVersion=55.0.1/20170814194718 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1711337/+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 1577197] Re: Pulseaudio bluez5-util.c: TryAcquire() failed - Operation Not Authorized
Ubuntu 16.10 broke the script because it's parsing some text which changed format. I've adapted the regexes. https://gist.github.com/wdullaer/631830bf13e8ecb646567b04acf654f8 This one works for me in 16.10. YMMV -- 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/1577197 Title: Pulseaudio bluez5-util.c: TryAcquire() failed - Operation Not Authorized Status in bluez package in Ubuntu: Confirmed Status in indicator-sound package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Confirmed Bug description: Pulseaudio outright stops audio via Bluetooth after sleep or prolonged period of time. Only restart fixes the issue. This started early 2016 in 15.10. Issue is discussed here as well http://askubuntu.com/questions/763539/bluetooth-speaker-no-sound-in-ubuntu-16-04 and mentioned in other unrelated bugs. Ubuntu Xenial 16.04 LTS The log below: May 1 17:18:07 jalexoidmobile pulseaudio[2884]: [pulseaudio] module-bluez5-device.c: Default profile not connected, selecting off profile May 1 17:18:07 jalexoidmobile bluetoothd[7349]: /org/bluez/hci0/dev_00_02_3C_05_99_F2/fd4: fd(35) ready May 1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Supervising 3 threads of 1 processes of 1 users. May 1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Successfully made thread 10967 of process 2884 (n/a) owned by '1000' RT at priority 5. May 1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Supervising 4 threads of 1 processes of 1 users. May 1 17:18:07 jalexoidmobile pulseaudio[2884]: [pulseaudio] bluez5-util.c: Transport TryAcquire() failed for transport /org/bluez/hci0/dev_00_02_3C_05_99_F2/fd4 (Operation Not Authorized) May 1 17:18:07 jalexoidmobile kernel: [20583.032442] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input24 May 1 17:18:19 jalexoidmobile pulseaudio[2884]: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 006: ID 04f2:b2da Chicony Electronics Co., Ltd thinkpad t430s camera Bus 001 Device 008: ID 0a5c:21e6 Broadcom Corp. BCM20702 Bluetooth 4.0 [ThinkPad] Bus 001 Device 004: ID 147e:2020 Upek TouchChip Fingerprint Coprocessor (WBF advanced mode) Bus 001 Device 003: ID 17ef:1003 Lenovo Integrated Smart Card Reader Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub [20388.983474] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [20389.070114] usb 1-1.4: New USB device found, idVendor=0a5c, idProduct=21e6 [20389.070120] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [20389.070122] usb 1-1.4: Product: BCM20702A0 [20389.070124] usb 1-1.4: Manufacturer: Broadcom Corp [20389.070126] usb 1-1.4: SerialNumber: 446D578686DD [20389.076232] Bluetooth: hci0: BCM: chip id 63 [20389.092220] Bluetooth: hci0: BCM20702A [20389.093225] Bluetooth: hci0: BCM20702A1 (001.002.014) build [20389.551476] wlan0: authenticate with a0:63:91:2f:3f:ed [20389.554391] wlan0: send auth to a0:63:91:2f:3f:ed (try 1/3) [20389.557790] wlan0: authenticated [20389.558339] wlan0: associate with a0:63:91:2f:3f:ed (try 1/3) [20389.562209] wlan0: RX AssocResp from a0:63:91:2f:3f:ed (capab=0x1411 status=0 aid=2) [20389.581260] wlan0: associated [20389.581369] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [20389.830185] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1669 [20389.846186] Bluetooth: hci0: Broadcom Bluetooth Device [20418.269466] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input23 [20583.032442] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input24 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1577197/+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 1240198] Re: [SRU]Wrong keyboard layout active after booting into desktop
I don't know if this has already been mentioned, but I'll add this to the bug report because it can be a workaround: If you have chosen to login automaticaly, logoff and in the logon screen you'll notice the keyboard has changed (icon next to clock). Now just change it back to your preference and upon next reboot the keyboard- layout will be to your preference (as is the case with ubuntu 14.04.3 x64 I've found). -- 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/1240198 Title: [SRU]Wrong keyboard layout active after booting into desktop Status in ibus package in Ubuntu: Confirmed Status in ibus source package in Trusty: Triaged Bug description: [Impact] When first boot into Unity desktop, English keyboard layout is active while all other parts of the system language settings are set to another language (e.g. German). The bug is properly addressed in newer upstream releases in Vivid, but the changes is too intrusive and not suitable for being back ported in SRU. And changing the default to use system keyboard layout solves the problem. [Test Case] 1. Set the system language to something other than English, e.g. German. 2. Create a new user, log in to the Unity desktop of the new user. 3. Check the keyboard layout, it should be German instead of English. [Regression Potential] Since this changes the default value of the keyboard layout settings by using system defined as default, it avoids using ibus's built-in keyboard layout related functionality, so that this could be a regression for users rely on this certain behavior (e.g. use English keyboard while want to keep the system language settings to German), but such behavior is not expected for normal usage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1240198/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1104230] Re: DisplayPort 1.2 MST support is missing in the Intel driver
Dariusz, Would you like me to update to 14.10 as well and try the utopic patched kernel? I want to upgrade soon, anyway. Or do you need my current 14.04 to test trusty stuff? Hartelijke groet, Wouter van der Graaf Dynora / Plangage +31 78 843 3139 Op 30 okt. 2014 14:26 schreef Dariusz Gadomski <1104...@bugs.launchpad.net>: > > Thanks Matthew! > > I will review the changes to trusty and try to backport this feature to > 3.13 (to avoid network problems). > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1104230 > > Title: > DisplayPort 1.2 MST support is missing in the Intel driver > > Status in X.org xf86-video-intel: > Unknown > Status in “xserver-xorg-video-intel” package in Ubuntu: > Confirmed > > Bug description: > I have two recent DisplayPort monitors, both supporting the 1.2 > version of the standard and one containing an MST hub (DELL 2913WM). > > I have an Intel Haswell based NUC connected over mini-displayport to > the display containing the hub, then the second display is plugged in > that one over DisplayPort. > > DisplayPort 1.2 is enabled on the display containing the hub and the > second display lights up fine but just works as a clone of the first > display, without ever showing up in xrandr, dmesg or any other useful > logs I could find. > > My understanding of MST is that the second display should show up as > DP2 on my laptop so I can configure it as I would any other display. > > UPDATE: Updated the bug report after it was pointed out that the > original test hardware, a Lenovo x230 isn't DP 1.2 capable. The same > test on hardware also fails, due to missing support for MST in the > driver. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1104230/+subscriptions -- 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/1104230 Title: DisplayPort 1.2 MST support is missing in the Intel driver Status in X.org xf86-video-intel: Unknown Status in “xserver-xorg-video-intel” package in Ubuntu: Confirmed Bug description: I have two recent DisplayPort monitors, both supporting the 1.2 version of the standard and one containing an MST hub (DELL 2913WM). I have an Intel Haswell based NUC connected over mini-displayport to the display containing the hub, then the second display is plugged in that one over DisplayPort. DisplayPort 1.2 is enabled on the display containing the hub and the second display lights up fine but just works as a clone of the first display, without ever showing up in xrandr, dmesg or any other useful logs I could find. My understanding of MST is that the second display should show up as DP2 on my laptop so I can configure it as I would any other display. UPDATE: Updated the bug report after it was pointed out that the original test hardware, a Lenovo x230 isn't DP 1.2 capable. The same test on hardware also fails, due to missing support for MST in the driver. To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1104230/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1104230] Re: DisplayPort 1.2 MST support is missing in the Intel driver
Hi Dariusz, I have a Dell XPS 12-9Q33 and two U2414Hb Dell displays, all DP 1.2 MST compatible. Using your instructions, I installed the new kernel and intel driver. Daisy chaining the two displays to my laptop DOES NOT work. With this kernel no external display works anymore. Moreover, my wireless network controller is now no longer working. Even though it's listed in lspci as a 'Network controller: Intel Corporation Wireless 7260 (rev 6b)', rfkill list shows nothing. Also, the touchscreen of my laptop stopped working with this kernel. It's no longer in the output of xinput list, which should show 'ATML1000:00 03EB:842F'. Lastly, my brightness keys don't work anymore. When I reboot with official kernel 3.13, everything works again. Of course, except for MST. Can you perhaps explain what's going on? Kind regards, Wouter Op 20-10-14 om 17:02 schreef Dariusz Gadomski: > Hi Elvis, > > Looks like you have the perfect setup to test this case. > > Please make sure you have ppa-purge installed so you can revert the > package updates if anything goes wrong. > > Please follow these steps: > 1. sudo add-apt-repository -y ppa:dgadomski/linux-mst > 2. sudo add-apt-repository -y ppa:xorg-edgers/ppa > 3. sudo apt-get update > Make sure that the output of: > 4. apt-cache policy linux-image-3.16.0-19-generic > states > Candidate: 3.16.0-19.26~14.04hf71858v20141008b1 > 5. sudo apt-get install linux-image-3.16.0-19-generic > 6. reboot to use the new kernel > 7. sudo apt-get install xserver-xorg-video-intel > 8. reboot to use the new intel driver > > Assuming that you are connected to Monitor #1 and it is daisy-chained to > Monitor #2 you should see 2 monitors available in the Ubuntu display > settings panel. > > I would appreciate your feedback. > > Thanks, > Dariusz > -- Wouter van der Graaf Open technologist / Partner d y n o r a Innovative software development +31 6 2893 0615 | wou...@dynora.nl Burg. de Bruïnelaan 95 | 3331 AC Zwijndrecht | NL +31 78 843 3139 | cont...@dynora.nl | www.dynora.nl -- 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/1104230 Title: DisplayPort 1.2 MST support is missing in the Intel driver Status in X.org xf86-video-intel: Unknown Status in “xserver-xorg-video-intel” package in Ubuntu: Confirmed Bug description: I have two recent DisplayPort monitors, both supporting the 1.2 version of the standard and one containing an MST hub (DELL 2913WM). I have an Intel Haswell based NUC connected over mini-displayport to the display containing the hub, then the second display is plugged in that one over DisplayPort. DisplayPort 1.2 is enabled on the display containing the hub and the second display lights up fine but just works as a clone of the first display, without ever showing up in xrandr, dmesg or any other useful logs I could find. My understanding of MST is that the second display should show up as DP2 on my laptop so I can configure it as I would any other display. UPDATE: Updated the bug report after it was pointed out that the original test hardware, a Lenovo x230 isn't DP 1.2 capable. The same test on hardware also fails, due to missing support for MST in the driver. To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1104230/+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 1213744] Re: thunderbird stopped displaying folders
I can confirm this problem. I tried re-creating the thunderbird profile, but it didn't solve the issue. -- 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/1213744 Title: thunderbird stopped displaying folders Status in “thunderbird” package in Ubuntu: Confirmed Bug description: I didn't use Thunderbird for about a month or so on my netbook and the package must have been updated in the meantime. Unfortunately, TB now no longer displays the folder and is thus entirely unusable (see screenshot). This account has used TB for mail for years and obviously has a bunch of (IMAP) folders, in fact, they account for about 2G of files locally. The same package works fine on another computer. The problem occurs even in safe-mode. I am running TB 17.0.8+build1-0ubuntu0.12.04.1 on precise. Another thing I noticed is that TB is extremely slow to start up recently. It takes about a minute of real time or 30s of CPU time before even the window is displayed. I have downgraded to 17.0.6+build1-0ubuntu0.12.04.1 now and that works fine, so this is a regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1213744/+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 1219753] Re: Dell XPS 12 2013 Haswell synaptics trackpad not recognized anymore in Ubuntu kernel 3.10 and 3.11
I suspect this is a kernel bug, because switching back to older 3.8 kernel makes my trackpad correctly recognized in /proc/bus/input/devices. ** Summary changed: - Dell XPS 12 2013 Haswell synaptics trackpad not recognized anymore in Ubuntu kernel 3.10 and 3.11rc + Dell XPS 12 2013 Haswell synaptics trackpad not recognized anymore in Ubuntu kernel 3.10 and 3.11 ** Package changed: xserver-xorg-input-synaptics (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1219753 Title: Dell XPS 12 2013 Haswell synaptics trackpad not recognized anymore in Ubuntu kernel 3.10 and 3.11 Status in “linux” package in Ubuntu: New Bug description: First I installed stock Ubuntu 13.04 Raring Ringtail with kernel 3.8. Trackpad was functioning correctly (e.g. two-finger scrolling worked) and was recognized as Synaptics device in /proc/bus/input/devices. Due to very new Intel wireless 7260 hardware that did not work in kernel 3.8, I dist-upgraded to 13.10 Saucy Salamander with kernel 3.11. With this kernel my Synaptics trackpad is no longer recognized as Synaptics and works as default evdev pointer (mouse) device, without all the trackpad features. This bug report was done with kernel 3.11rc7, but applies also to kernel 3.10 and the latest saucy kernel 3.11 to which I'm upgraded by software updater. Instead of Synaptics, devices lists it as below: I: Bus=0018 Vendor=06cb Product=2734 Version=0100 N: Name="DLL05E3:01 06CB:2734" P: Phys= S: Sysfs=/devices/pci:00/INT33C3:00/i2c-8/8-002c/input/input11 U: Uniq= H: Handlers=mouse0 event11 B: PROP=0 B: EV=17 B: KEY=3 0 0 0 0 B: REL=3 B: MSC=10 ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xserver-xorg-input-synaptics 1.7.1-0ubuntu1 Uname: Linux 3.11.0-031100rc7-generic x86_64 ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 Date: Mon Sep 2 11:52:16 2013 DistUpgraded: 2013-09-01 22:21:35,082 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu EcryptfsInUse: Yes InstallationDate: Installed on 2013-08-09 (23 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Dell Inc. XPS 12-9Q33 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-031100rc7-generic root=UUID=8e4879ce-4777-4c48-b6d7-5b3b4b116ad3 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-synaptics UpgradeStatus: Upgraded to saucy on 2013-09-01 (0 days ago) dmi.bios.date: 06/20/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: XPS 12-9Q33 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA01:bd06/20/2013:svnDellInc.:pnXPS12-9Q33:pvrA01:rvnDellInc.:rnXPS12-9Q33:rvrA01:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 12-9Q33 dmi.product.version: A01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.10+13.10.20130828.2-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Mon Sep 2 11:22:49 2013 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1021 vendor LGD xserver.version: 2:1.14.2.901-2ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1219753/+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 1219753] Re: Dell XPS 12 2013 Haswell synaptics trackpad not recognized anymore in Ubuntu kernel 3.10 and 3.11rc
I've upgraded to the latest saucy 3.11.0-7 kernel, but the trackpad is still not recognized as Synaptics. In kernel 3.8 it did work as expected. ** Description changed: First I installed stock Ubuntu 13.04 Raring Ringtail with kernel 3.8. Trackpad was functioning correctly (e.g. two-finger scrolling worked) and was recognized as Synaptics device in /proc/bus/input/devices. Due to very new Intel wireless 7260 hardware that did not work in kernel - 3.8, I had to upgrade my kernel to latest 3.11rc. With this kernel my - Synaptics trackpad is no longer recognized as Synaptics and works as - default evdev pointer (mouse) device, without all the trackpad features. + 3.8, I dist-upgraded to 13.10 Saucy Salamander with kernel 3.11. With + this kernel my Synaptics trackpad is no longer recognized as Synaptics + and works as default evdev pointer (mouse) device, without all the + trackpad features. - I dist-upgraded to 13.10 Saucy Salamander with kernel 3.10 to see if it - may have been fixed there. But unfortunately the trackpad regression is - also there. + This bug report was done with kernel 3.11rc7, but applies also to kernel + 3.10 and the latest saucy kernel 3.11 to which I'm upgraded by software + updater. Instead of Synaptics, devices lists it as below: I: Bus=0018 Vendor=06cb Product=2734 Version=0100 N: Name="DLL05E3:01 06CB:2734" P: Phys= S: Sysfs=/devices/pci:00/INT33C3:00/i2c-8/8-002c/input/input11 U: Uniq= H: Handlers=mouse0 event11 B: PROP=0 B: EV=17 B: KEY=3 0 0 0 0 B: REL=3 B: MSC=10 ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xserver-xorg-input-synaptics 1.7.1-0ubuntu1 Uname: Linux 3.11.0-031100rc7-generic x86_64 ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 Date: Mon Sep 2 11:52:16 2013 DistUpgraded: 2013-09-01 22:21:35,082 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu EcryptfsInUse: Yes InstallationDate: Installed on 2013-08-09 (23 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Dell Inc. XPS 12-9Q33 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-031100rc7-generic root=UUID=8e4879ce-4777-4c48-b6d7-5b3b4b116ad3 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-synaptics UpgradeStatus: Upgraded to saucy on 2013-09-01 (0 days ago) dmi.bios.date: 06/20/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: XPS 12-9Q33 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA01:bd06/20/2013:svnDellInc.:pnXPS12-9Q33:pvrA01:rvnDellInc.:rnXPS12-9Q33:rvrA01:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 12-9Q33 dmi.product.version: A01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.10+13.10.20130828.2-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Mon Sep 2 11:22:49 2013 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1021 vendor LGD xserver.version: 2:1.14.2.901-2ubuntu4 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1219753 Title: Dell XPS 12 2013 Haswell synaptics trackpad not recognized anymore in Ubuntu kernel 3.10 and 3.11rc Status in “xserver-xorg-input-synaptics” package in Ubuntu: New Bug description: First I installed stock Ubuntu 13.04 Raring Ringtail with kernel 3.8. Trackpad was functioning correctly (e.g. two-finger scrolling worked) and was recognized as Synaptics device in /proc/bus/input/devices. Due to very new Intel wireless 7260 hardware that did not work in kernel 3.8, I dist-upgraded to 13.10 Saucy Salamander with kernel 3.11. With this kernel my Synaptics trackpad is no longer recognized as Synaptics and works as default evdev pointer (mouse) device, without all the trackpad features. This bug report was done with kernel 3.11rc7, but applies also to kernel 3.10 and the latest saucy kernel 3.11 to which I'm upgraded by software updater. Instead of Synaptics, devices lists it as below: I: Bus=001
[Desktop-packages] [Bug 1219753] Re: Dell XPS 12 2013 Haswell synaptics trackpad not recognized anymore in Ubuntu kernel 3.10 and 3.11rc
In fact my bug report is based on kernel v3.11-rc7-saucy with 13.10. Everything in my XPS 12 2013 seems to work fine with current Saucy development and kernel 3.11rc, *except* the trackpad. Strange that my Synaptic did work in 3.8 and not anymore since 3.10 and 3.11rc. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1219753 Title: Dell XPS 12 2013 Haswell synaptics trackpad not recognized anymore in Ubuntu kernel 3.10 and 3.11rc Status in “xserver-xorg-input-synaptics” package in Ubuntu: New Bug description: First I installed stock Ubuntu 13.04 Raring Ringtail with kernel 3.8. Trackpad was functioning correctly (e.g. two-finger scrolling worked) and was recognized as Synaptics device in /proc/bus/input/devices. Due to very new Intel wireless 7260 hardware that did not work in kernel 3.8, I had to upgrade my kernel to latest 3.11rc. With this kernel my Synaptics trackpad is no longer recognized as Synaptics and works as default evdev pointer (mouse) device, without all the trackpad features. I dist-upgraded to 13.10 Saucy Salamander with kernel 3.10 to see if it may have been fixed there. But unfortunately the trackpad regression is also there. Instead of Synaptics, devices lists it as below: I: Bus=0018 Vendor=06cb Product=2734 Version=0100 N: Name="DLL05E3:01 06CB:2734" P: Phys= S: Sysfs=/devices/pci:00/INT33C3:00/i2c-8/8-002c/input/input11 U: Uniq= H: Handlers=mouse0 event11 B: PROP=0 B: EV=17 B: KEY=3 0 0 0 0 B: REL=3 B: MSC=10 ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xserver-xorg-input-synaptics 1.7.1-0ubuntu1 Uname: Linux 3.11.0-031100rc7-generic x86_64 ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 Date: Mon Sep 2 11:52:16 2013 DistUpgraded: 2013-09-01 22:21:35,082 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu EcryptfsInUse: Yes InstallationDate: Installed on 2013-08-09 (23 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Dell Inc. XPS 12-9Q33 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-031100rc7-generic root=UUID=8e4879ce-4777-4c48-b6d7-5b3b4b116ad3 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-synaptics UpgradeStatus: Upgraded to saucy on 2013-09-01 (0 days ago) dmi.bios.date: 06/20/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: XPS 12-9Q33 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA01:bd06/20/2013:svnDellInc.:pnXPS12-9Q33:pvrA01:rvnDellInc.:rnXPS12-9Q33:rvrA01:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 12-9Q33 dmi.product.version: A01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.10+13.10.20130828.2-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Mon Sep 2 11:22:49 2013 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1021 vendor LGD xserver.version: 2:1.14.2.901-2ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1219753/+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 1219753] Re: Dell XPS 12 2013 Haswell synaptics trackpad not recognized anymore in Ubuntu kernel 3.10 and 3.11rc
Is this perhaps a kernel bug and should this report therefore be reassigned to the kernel team? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1219753 Title: Dell XPS 12 2013 Haswell synaptics trackpad not recognized anymore in Ubuntu kernel 3.10 and 3.11rc Status in “xserver-xorg-input-synaptics” package in Ubuntu: New Bug description: First I installed stock Ubuntu 13.04 Raring Ringtail with kernel 3.8. Trackpad was functioning correctly (e.g. two-finger scrolling worked) and was recognized as Synaptics device in /proc/bus/input/devices. Due to very new Intel wireless 7260 hardware that did not work in kernel 3.8, I had to upgrade my kernel to latest 3.11rc. With this kernel my Synaptics trackpad is no longer recognized as Synaptics and works as default evdev pointer (mouse) device, without all the trackpad features. I dist-upgraded to 13.10 Saucy Salamander with kernel 3.10 to see if it may have been fixed there. But unfortunately the trackpad regression is also there. Instead of Synaptics, devices lists it as below: I: Bus=0018 Vendor=06cb Product=2734 Version=0100 N: Name="DLL05E3:01 06CB:2734" P: Phys= S: Sysfs=/devices/pci:00/INT33C3:00/i2c-8/8-002c/input/input11 U: Uniq= H: Handlers=mouse0 event11 B: PROP=0 B: EV=17 B: KEY=3 0 0 0 0 B: REL=3 B: MSC=10 ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xserver-xorg-input-synaptics 1.7.1-0ubuntu1 Uname: Linux 3.11.0-031100rc7-generic x86_64 ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 Date: Mon Sep 2 11:52:16 2013 DistUpgraded: 2013-09-01 22:21:35,082 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu EcryptfsInUse: Yes InstallationDate: Installed on 2013-08-09 (23 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Dell Inc. XPS 12-9Q33 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-031100rc7-generic root=UUID=8e4879ce-4777-4c48-b6d7-5b3b4b116ad3 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-synaptics UpgradeStatus: Upgraded to saucy on 2013-09-01 (0 days ago) dmi.bios.date: 06/20/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: XPS 12-9Q33 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA01:bd06/20/2013:svnDellInc.:pnXPS12-9Q33:pvrA01:rvnDellInc.:rnXPS12-9Q33:rvrA01:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 12-9Q33 dmi.product.version: A01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.10+13.10.20130828.2-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Mon Sep 2 11:22:49 2013 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1021 vendor LGD xserver.version: 2:1.14.2.901-2ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1219753/+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 1219753] [NEW] Dell XPS 12 2013 Haswell synaptics trackpad not recognized anymore in Ubuntu kernel 3.10 and 3.11rc
Public bug reported: First I installed stock Ubuntu 13.04 Raring Ringtail with kernel 3.8. Trackpad was functioning correctly (e.g. two-finger scrolling worked) and was recognized as Synaptics device in /proc/bus/input/devices. Due to very new Intel wireless 7260 hardware that did not work in kernel 3.8, I had to upgrade my kernel to latest 3.11rc. With this kernel my Synaptics trackpad is no longer recognized as Synaptics and works as default evdev pointer (mouse) device, without all the trackpad features. I dist-upgraded to 13.10 Saucy Salamander with kernel 3.10 to see if it may have been fixed there. But unfortunately the trackpad regression is also there. Instead of Synaptics, devices lists it as below: I: Bus=0018 Vendor=06cb Product=2734 Version=0100 N: Name="DLL05E3:01 06CB:2734" P: Phys= S: Sysfs=/devices/pci:00/INT33C3:00/i2c-8/8-002c/input/input11 U: Uniq= H: Handlers=mouse0 event11 B: PROP=0 B: EV=17 B: KEY=3 0 0 0 0 B: REL=3 B: MSC=10 ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xserver-xorg-input-synaptics 1.7.1-0ubuntu1 Uname: Linux 3.11.0-031100rc7-generic x86_64 ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 Date: Mon Sep 2 11:52:16 2013 DistUpgraded: 2013-09-01 22:21:35,082 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu EcryptfsInUse: Yes InstallationDate: Installed on 2013-08-09 (23 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Dell Inc. XPS 12-9Q33 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-031100rc7-generic root=UUID=8e4879ce-4777-4c48-b6d7-5b3b4b116ad3 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-synaptics UpgradeStatus: Upgraded to saucy on 2013-09-01 (0 days ago) dmi.bios.date: 06/20/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: XPS 12-9Q33 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA01:bd06/20/2013:svnDellInc.:pnXPS12-9Q33:pvrA01:rvnDellInc.:rnXPS12-9Q33:rvrA01:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 12-9Q33 dmi.product.version: A01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.10+13.10.20130828.2-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Mon Sep 2 11:22:49 2013 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1021 vendor LGD xserver.version: 2:1.14.2.901-2ubuntu4 ** Affects: xserver-xorg-input-synaptics (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1219753 Title: Dell XPS 12 2013 Haswell synaptics trackpad not recognized anymore in Ubuntu kernel 3.10 and 3.11rc Status in “xserver-xorg-input-synaptics” package in Ubuntu: New Bug description: First I installed stock Ubuntu 13.04 Raring Ringtail with kernel 3.8. Trackpad was functioning correctly (e.g. two-finger scrolling worked) and was recognized as Synaptics device in /proc/bus/input/devices. Due to very new Intel wireless 7260 hardware that did not work in kernel 3.8, I had to upgrade my kernel to latest 3.11rc. With this kernel my Synaptics trackpad is no longer recognized as Synaptics and works as default evdev pointer (mouse) device, without all the trackpad features. I dist-upgraded to 13.10 Saucy Salamander with kernel 3.10 to see if it may have been fixed there. But unfortunately the trackpad regression is also there. Instead of Synaptics, devices lists it as below: I: Bus=0018 Vendor=06cb Product=2734 Version=0100 N: Name="DLL05E3:01 06CB:2734" P: Phys= S: Sysfs=/devices/pci:00/INT33C3:00/i2c-8/8-002c/input/input11 U: Uniq= H: Handlers=mouse0 event11 B: PROP=0 B: EV=17 B: KEY=3 0 0 0 0 B: REL=3 B: MSC=10 ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xserver-xorg-input-synaptics 1.7.1-0ubuntu1 Uname: Linux 3.11.0-031100rc7-generic x86_64 ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 Date: Mon Sep 2 11:52:16 2013 DistUpgraded: 2013-09-01 22:21:35,082 DEBUG enabling apt cron job
[Desktop-packages] [Bug 1219753] Re: Dell XPS 12 2013 Haswell synaptics trackpad not recognized anymore in Ubuntu kernel 3.10 and 3.11rc
** Attachment added: "Output of xinput --list" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1219753/+attachment/3799037/+files/xinput -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1219753 Title: Dell XPS 12 2013 Haswell synaptics trackpad not recognized anymore in Ubuntu kernel 3.10 and 3.11rc Status in “xserver-xorg-input-synaptics” package in Ubuntu: New Bug description: First I installed stock Ubuntu 13.04 Raring Ringtail with kernel 3.8. Trackpad was functioning correctly (e.g. two-finger scrolling worked) and was recognized as Synaptics device in /proc/bus/input/devices. Due to very new Intel wireless 7260 hardware that did not work in kernel 3.8, I had to upgrade my kernel to latest 3.11rc. With this kernel my Synaptics trackpad is no longer recognized as Synaptics and works as default evdev pointer (mouse) device, without all the trackpad features. I dist-upgraded to 13.10 Saucy Salamander with kernel 3.10 to see if it may have been fixed there. But unfortunately the trackpad regression is also there. Instead of Synaptics, devices lists it as below: I: Bus=0018 Vendor=06cb Product=2734 Version=0100 N: Name="DLL05E3:01 06CB:2734" P: Phys= S: Sysfs=/devices/pci:00/INT33C3:00/i2c-8/8-002c/input/input11 U: Uniq= H: Handlers=mouse0 event11 B: PROP=0 B: EV=17 B: KEY=3 0 0 0 0 B: REL=3 B: MSC=10 ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xserver-xorg-input-synaptics 1.7.1-0ubuntu1 Uname: Linux 3.11.0-031100rc7-generic x86_64 ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 Date: Mon Sep 2 11:52:16 2013 DistUpgraded: 2013-09-01 22:21:35,082 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu EcryptfsInUse: Yes InstallationDate: Installed on 2013-08-09 (23 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Dell Inc. XPS 12-9Q33 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-031100rc7-generic root=UUID=8e4879ce-4777-4c48-b6d7-5b3b4b116ad3 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-synaptics UpgradeStatus: Upgraded to saucy on 2013-09-01 (0 days ago) dmi.bios.date: 06/20/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: XPS 12-9Q33 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA01:bd06/20/2013:svnDellInc.:pnXPS12-9Q33:pvrA01:rvnDellInc.:rnXPS12-9Q33:rvrA01:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 12-9Q33 dmi.product.version: A01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.10+13.10.20130828.2-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Mon Sep 2 11:22:49 2013 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1021 vendor LGD xserver.version: 2:1.14.2.901-2ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1219753/+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 1219753] Re: Dell XPS 12 2013 Haswell synaptics trackpad not recognized anymore in Ubuntu kernel 3.10 and 3.11rc
** Attachment added: "Output of /proc/bus/input/devices" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1219753/+attachment/3799036/+files/devices -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1219753 Title: Dell XPS 12 2013 Haswell synaptics trackpad not recognized anymore in Ubuntu kernel 3.10 and 3.11rc Status in “xserver-xorg-input-synaptics” package in Ubuntu: New Bug description: First I installed stock Ubuntu 13.04 Raring Ringtail with kernel 3.8. Trackpad was functioning correctly (e.g. two-finger scrolling worked) and was recognized as Synaptics device in /proc/bus/input/devices. Due to very new Intel wireless 7260 hardware that did not work in kernel 3.8, I had to upgrade my kernel to latest 3.11rc. With this kernel my Synaptics trackpad is no longer recognized as Synaptics and works as default evdev pointer (mouse) device, without all the trackpad features. I dist-upgraded to 13.10 Saucy Salamander with kernel 3.10 to see if it may have been fixed there. But unfortunately the trackpad regression is also there. Instead of Synaptics, devices lists it as below: I: Bus=0018 Vendor=06cb Product=2734 Version=0100 N: Name="DLL05E3:01 06CB:2734" P: Phys= S: Sysfs=/devices/pci:00/INT33C3:00/i2c-8/8-002c/input/input11 U: Uniq= H: Handlers=mouse0 event11 B: PROP=0 B: EV=17 B: KEY=3 0 0 0 0 B: REL=3 B: MSC=10 ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xserver-xorg-input-synaptics 1.7.1-0ubuntu1 Uname: Linux 3.11.0-031100rc7-generic x86_64 ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 Date: Mon Sep 2 11:52:16 2013 DistUpgraded: 2013-09-01 22:21:35,082 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu EcryptfsInUse: Yes InstallationDate: Installed on 2013-08-09 (23 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Dell Inc. XPS 12-9Q33 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-031100rc7-generic root=UUID=8e4879ce-4777-4c48-b6d7-5b3b4b116ad3 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-synaptics UpgradeStatus: Upgraded to saucy on 2013-09-01 (0 days ago) dmi.bios.date: 06/20/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: XPS 12-9Q33 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA01:bd06/20/2013:svnDellInc.:pnXPS12-9Q33:pvrA01:rvnDellInc.:rnXPS12-9Q33:rvrA01:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 12-9Q33 dmi.product.version: A01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.10+13.10.20130828.2-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Mon Sep 2 11:22:49 2013 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1021 vendor LGD xserver.version: 2:1.14.2.901-2ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1219753/+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 1219753] Re: Dell XPS 12 2013 Haswell synaptics trackpad not recognized anymore in Ubuntu kernel 3.10 and 3.11rc
** Attachment added: "Output of Xorg.0.log" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1219753/+attachment/3799038/+files/Xorg.0.log ** Attachment removed: "XorgConf.txt" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1219753/+attachment/3799029/+files/XorgConf.txt ** Description changed: First I installed stock Ubuntu 13.04 Raring Ringtail with kernel 3.8. Trackpad was functioning correctly (e.g. two-finger scrolling worked) and was recognized as Synaptics device in /proc/bus/input/devices. Due to very new Intel wireless 7260 hardware that did not work in kernel 3.8, I had to upgrade my kernel to latest 3.11rc. With this kernel my Synaptics trackpad is no longer recognized as Synaptics and works as default evdev pointer (mouse) device, without all the trackpad features. I dist-upgraded to 13.10 Saucy Salamander with kernel 3.10 to see if it may have been fixed there. But unfortunately the trackpad regression is also there. Instead of Synaptics, devices lists it as below: I: Bus=0018 Vendor=06cb Product=2734 Version=0100 N: Name="DLL05E3:01 06CB:2734" P: Phys= S: Sysfs=/devices/pci:00/INT33C3:00/i2c-8/8-002c/input/input11 U: Uniq= - H: Handlers=mouse0 event11 + H: Handlers=mouse0 event11 B: PROP=0 B: EV=17 B: KEY=3 0 0 0 0 B: REL=3 B: MSC=10 ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xserver-xorg-input-synaptics 1.7.1-0ubuntu1 Uname: Linux 3.11.0-031100rc7-generic x86_64 ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 Date: Mon Sep 2 11:52:16 2013 DistUpgraded: 2013-09-01 22:21:35,082 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu EcryptfsInUse: Yes InstallationDate: Installed on 2013-08-09 (23 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Dell Inc. XPS 12-9Q33 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-031100rc7-generic root=UUID=8e4879ce-4777-4c48-b6d7-5b3b4b116ad3 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-synaptics UpgradeStatus: Upgraded to saucy on 2013-09-01 (0 days ago) dmi.bios.date: 06/20/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: XPS 12-9Q33 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA01:bd06/20/2013:svnDellInc.:pnXPS12-9Q33:pvrA01:rvnDellInc.:rnXPS12-9Q33:rvrA01:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 12-9Q33 dmi.product.version: A01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.10+13.10.20130828.2-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Mon Sep 2 11:22:49 2013 - xserver.configfile: /etc/X11/xorg.conf xserver.errors: - + xserver.logfile: /var/log/Xorg.0.log xserver.outputs: - product id1021 - vendor LGD + product id1021 + vendor LGD xserver.version: 2:1.14.2.901-2ubuntu4 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1219753 Title: Dell XPS 12 2013 Haswell synaptics trackpad not recognized anymore in Ubuntu kernel 3.10 and 3.11rc Status in “xserver-xorg-input-synaptics” package in Ubuntu: New Bug description: First I installed stock Ubuntu 13.04 Raring Ringtail with kernel 3.8. Trackpad was functioning correctly (e.g. two-finger scrolling worked) and was recognized as Synaptics device in /proc/bus/input/devices. Due to very new Intel wireless 7260 hardware that did not work in kernel 3.8, I had to upgrade my kernel to latest 3.11rc. With this kernel my Synaptics trackpad is no longer recognized as Synaptics and works as default evdev pointer (mouse) device, without all the trackpad features. I dist-upgraded to 13.10 Saucy Salamander with kernel 3.10 to see if it may have been fixed there. But unfortunately the trackpad regression is also there. Instead of Synaptics, devices lists it as below: I: Bus=0018 Vendor=06cb Product=2734 Version=0100
[Desktop-packages] [Bug 311570] Re: Thinkpad SL300 slow touchpad speed
Sorry can't help with that anymore, don't have that laptop anymore. Will close the bug. ** Changed in: xserver-xorg-input-synaptics (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/311570 Title: Thinkpad SL300 slow touchpad speed Status in “xserver-xorg-input-synaptics” package in Ubuntu: Invalid Bug description: On the lenovo thinkpad sl300, the default speed of the (non-synaptic) touchpad is far too slow. To get the pointer from the upper left corner of the screen to the lower right corner, it takes 4 sweeps diagonally across the touchpad instead of one or so that it takes on windows or with other touchpads. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/311570/+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 280073] Re: Wi-Fi slow -- Ralink rt61
Sorry, I no longer own that computer so I have no idea. Will close this as I cannot provide any further information. ** Changed in: network-manager (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/280073 Title: Wi-Fi slow -- Ralink rt61 Status in “network-manager” package in Ubuntu: Invalid Bug description: Binary package hint: network-manager On intrepid, most of the time I get a maximum network speed of around 100kb/s over my wireless connection, while it should be able to do something like 700-800kb/s. Other pc's on the network have no problem achieving this speed and this pc neither running under windows. NM reports a 54mbps network connection. Wificard: Ralink, driver rt61 ProblemType: Bug Architecture: amd64 DistroRelease: Ubuntu 8.10 IfupdownConfig: auto lo iface lo inet loopback Package: network-manager 0.7~~svn20081004t225044-0ubuntu1 ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=nl_NL.UTF-8 SHELL=/bin/bash SourcePackage: network-manager Uname: Linux 2.6.27-6-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/280073/+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 828593] Re: Gwibber "Smooth scrolling"
+1 - reloading avatars and no smooth scrolling makes Gwibber a dull boy (broken app, that is) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gwibber in Ubuntu. https://bugs.launchpad.net/bugs/828593 Title: Gwibber "Smooth scrolling" Status in Gwibber: Confirmed Status in “gwibber” package in Ubuntu: Triaged Bug description: Trying to read down my list of posts in Gwibber is very difficult because of a number of bugs. The one I'm reporting here is using the scrollbar to scroll through the list is in no way smooth and skips in big jumps. The effect is I cannot read while scrolling, and because it jumps so jarringly quickly I don't know if I have missed any posts. We need to implement smooth scrolling. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gwibber 3.1.5-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-8.11-generic 3.0.1 Uname: Linux 3.0.0-8-generic x86_64 Architecture: amd64 Date: Thu Aug 18 10:08:40 2011 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110728) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gwibber UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gwibber/+bug/828593/+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 929139] Re: Cannot restore backup from NAS using Deja Dup
Hi Gary,
My experience is to long ago to suggest now a more specific program.
Except tar, I remember dump / restore, cp, dd and cpio.
Regards,
Wouter
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/929139
Title:
Cannot restore backup from NAS using Deja Dup
Status in “deja-dup” package in Ubuntu:
Confirmed
Bug description:
~*~*~*~*~*~*~*~*~
ISSUE
~*~*~*~*~*~*~*~*~
I successfully backed my entire machine (/) up to an external NAS
drive (Western Digital 500GB MyBook). However, when I came to test the
restore I keep getting the same message: "Restore Failed: Connection
failed, please check your password: Failed to mount Windows Share".
This seems strange since I was able to write the backup to the NAS
drive. I backed up over wifi and I am trying to restore via wifi.
~*~*~*~*~*~*~*~*~
STEPS
~*~*~*~*~*~*~*~*~
In the settings of Deja Dup, in the 'Storage' section, I have the
following:
Backup location: Windows Share
Server:
Folder:
Username:
Domain: WORKGROUP
I have triple checked these entries for schoolboy errors like typos
and all is correct. One thing I did note is that I am not asked for
the password to accompany the username.
So, I select the 'Restore' option from the 'Overview' section and a
small 'Restore' dialog appears. The details here are exactly as I
entered them. I also make sure at this point that the NAS share is
*not* mounted. I then click 'Forward'. At this point the share is
mounted - I can see it in the file explorer - it also correctly
identifies the one and only backup made in the 'Date' drop down list
box. I click 'Forward' again. In the 'Restore to where?' section I
leave all at the defaults ('Restore to original file locations') and
click 'Forward'. The 'Summary' screen shows. I then click 'Restore'.
At this point I get a 'Preparing' progress bar. Expanding the details
section shows nothing. My screen then goes black an I am asked to
enter my administrator password ince Deja Dup will be modifying my
system. I do this and then I get the error as mentioned: "Restore
Failed: Connection failed, please check your password: Failed to mount
Windows Share" - the share is already mounted at this point though so
I am totally confused. I have tried specifying the NAS by network name
and IP and manually mounting it and it results in the same error
message each time. I was expecting it to restore the backup I just
took. I will admit that the wording of the error message would
indicate an error on my part but since the NAS share is mounted at the
point I indicated earlier it seems somewhat misleading.
~*~*~*~*~*~*~*~*~
PACKAGE DETAILS
~*~*~*~*~*~*~*~*~
deja-dup:
Installed: 20.1-0ubuntu0.2
Candidate: 20.1-0ubuntu0.2
Version table:
*** 20.1-0ubuntu0.2 0
500 http://gb.archive.ubuntu.com/ubuntu/ oneiric-updates/main amd64
Packages
100 /var/lib/dpkg/status
20.0-0ubuntu3 0
500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages
~*~*~*~*~*~*~*~*~
SYSINFO
~*~*~*~*~*~*~*~*~
System information report, generated by Sysinfo: 08/02/2012 21:29:38
http://sourceforge.net/projects/gsysinfo
SYSTEM INFORMATION
Running Ubuntu Linux, the Ubuntu 11.10 (oneiric) release.
GNOME: 2.32.1 (Ubuntu 2011-04-14)
Kernel version: 3.0.0-15-generic (#26-Ubuntu SMP Fri Jan 20 17:23:00
UTC 2012)
GCC: 4.6.1 (x86_64-linux-gnu)
Xorg: 1.10.4 (19 October 2011 05:21:26AM) (19 October 2011 05:21:26AM)
Hostname: V5535
Uptime: 0 days 0 h 55 min
CPU INFORMATION
GenuineIntel, Intel(R) Core(TM)2 Duo CPU T7300 @ 2.00GHz
Number of CPUs: 2
CPU clock currently at 1200.000 MHz with 4096 KB cache
Numbering: family(6) model(15) stepping(10)
Bogomips: 4000.49
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm
constant_tsc arch_perfmon pebs bts rep_good nopl aperfmperf pni dtes64 monitor
ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm lahf_lm ida dts tpr_shadow vnmi
flexpriority
MEMORY INFORMATION
Total memory: 2761 MB
Total swap: 2810 MB
STORAGE INFORMATION
SCSI device - scsi0
Vendor: HL-DT-ST
Model: DVDRAM GSA-T20N
SCSI device - scsi2
Vendor: ATA
Model: OCZ-VERTEX2
HARDWARE INFORMATION
MOTHERBOARD
Host bridge
Silicon Integrated Systems [SiS] 671MX
Subsystem: Fujitsu Technology Solutions Device 1125
PCI bridge(s)
Si
[Desktop-packages] [Bug 929139] Re: Cannot restore backup from NAS using Deja Dup
For backing up and restoring trivial data, especially user home
directories, Deja dup is (indeed) a good alternative. The restore
problem which I have/had from NAS to the (external) usb disk is a
permission problem, which I noticed too with other rsync programs and
the command-line rsync.
I share the usb disk (documents and pictures) with Windows 7 (dual boot
Ubuntu and Windows). In case of a hard problem of the Linux OS, I prefer
to reinstall Ubuntu and restore from NAS the user home directory.
For an image of the entire linux file-system use a more specific
program.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/929139
Title:
Cannot restore backup from NAS using Deja Dup
Status in “deja-dup” package in Ubuntu:
Confirmed
Bug description:
~*~*~*~*~*~*~*~*~
ISSUE
~*~*~*~*~*~*~*~*~
I successfully backed my entire machine (/) up to an external NAS
drive (Western Digital 500GB MyBook). However, when I came to test the
restore I keep getting the same message: "Restore Failed: Connection
failed, please check your password: Failed to mount Windows Share".
This seems strange since I was able to write the backup to the NAS
drive. I backed up over wifi and I am trying to restore via wifi.
~*~*~*~*~*~*~*~*~
STEPS
~*~*~*~*~*~*~*~*~
In the settings of Deja Dup, in the 'Storage' section, I have the
following:
Backup location: Windows Share
Server:
Folder:
Username:
Domain: WORKGROUP
I have triple checked these entries for schoolboy errors like typos
and all is correct. One thing I did note is that I am not asked for
the password to accompany the username.
So, I select the 'Restore' option from the 'Overview' section and a
small 'Restore' dialog appears. The details here are exactly as I
entered them. I also make sure at this point that the NAS share is
*not* mounted. I then click 'Forward'. At this point the share is
mounted - I can see it in the file explorer - it also correctly
identifies the one and only backup made in the 'Date' drop down list
box. I click 'Forward' again. In the 'Restore to where?' section I
leave all at the defaults ('Restore to original file locations') and
click 'Forward'. The 'Summary' screen shows. I then click 'Restore'.
At this point I get a 'Preparing' progress bar. Expanding the details
section shows nothing. My screen then goes black an I am asked to
enter my administrator password ince Deja Dup will be modifying my
system. I do this and then I get the error as mentioned: "Restore
Failed: Connection failed, please check your password: Failed to mount
Windows Share" - the share is already mounted at this point though so
I am totally confused. I have tried specifying the NAS by network name
and IP and manually mounting it and it results in the same error
message each time. I was expecting it to restore the backup I just
took. I will admit that the wording of the error message would
indicate an error on my part but since the NAS share is mounted at the
point I indicated earlier it seems somewhat misleading.
~*~*~*~*~*~*~*~*~
PACKAGE DETAILS
~*~*~*~*~*~*~*~*~
deja-dup:
Installed: 20.1-0ubuntu0.2
Candidate: 20.1-0ubuntu0.2
Version table:
*** 20.1-0ubuntu0.2 0
500 http://gb.archive.ubuntu.com/ubuntu/ oneiric-updates/main amd64
Packages
100 /var/lib/dpkg/status
20.0-0ubuntu3 0
500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages
~*~*~*~*~*~*~*~*~
SYSINFO
~*~*~*~*~*~*~*~*~
System information report, generated by Sysinfo: 08/02/2012 21:29:38
http://sourceforge.net/projects/gsysinfo
SYSTEM INFORMATION
Running Ubuntu Linux, the Ubuntu 11.10 (oneiric) release.
GNOME: 2.32.1 (Ubuntu 2011-04-14)
Kernel version: 3.0.0-15-generic (#26-Ubuntu SMP Fri Jan 20 17:23:00
UTC 2012)
GCC: 4.6.1 (x86_64-linux-gnu)
Xorg: 1.10.4 (19 October 2011 05:21:26AM) (19 October 2011 05:21:26AM)
Hostname: V5535
Uptime: 0 days 0 h 55 min
CPU INFORMATION
GenuineIntel, Intel(R) Core(TM)2 Duo CPU T7300 @ 2.00GHz
Number of CPUs: 2
CPU clock currently at 1200.000 MHz with 4096 KB cache
Numbering: family(6) model(15) stepping(10)
Bogomips: 4000.49
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm
constant_tsc arch_perfmon pebs bts rep_good nopl aperfmperf pni dtes64 monitor
ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm lahf_lm ida dts tpr_shadow vnmi
flexpriority
MEMORY INFORMATION
Total memory: 2761 MB
Total swap: 2810 MB
STORAGE INFORMATION
SCSI device - scsi0
Vendor: HL-DT-ST
Model: DVDRAM GSA-T20N
SCSI device - scsi2
Vendor: A
[Desktop-packages] [Bug 929139] Re: Cannot restore backup from NAS using Deja Dup
I have the same error message after restore missing files (Ubuntu 11.10):
"Restore Failed: Connection failed, please check your password: Failed to mount
Windows Share"
My (temporary?) work-around is: Mount the Backup (NAS) directory to /mnt
(sudo mount.cifs //NAS/Backup /mnt/NAS/ -o user= your-uid,passwd=your-password
In Deja-dup (aka backup) Storage/Backup location = Local Folder (instead
of Windows Share) and Choose folder = /mnt/NAS/Backup
Restore Missing files from my NAS to the external usb disk (/media/usb)
now succeeded (with admin passwd) ...
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/929139
Title:
Cannot restore backup from NAS using Deja Dup
Status in “deja-dup” package in Ubuntu:
Confirmed
Bug description:
~*~*~*~*~*~*~*~*~
ISSUE
~*~*~*~*~*~*~*~*~
I successfully backed my entire machine (/) up to an external NAS
drive (Western Digital 500GB MyBook). However, when I came to test the
restore I keep getting the same message: "Restore Failed: Connection
failed, please check your password: Failed to mount Windows Share".
This seems strange since I was able to write the backup to the NAS
drive. I backed up over wifi and I am trying to restore via wifi.
~*~*~*~*~*~*~*~*~
STEPS
~*~*~*~*~*~*~*~*~
In the settings of Deja Dup, in the 'Storage' section, I have the
following:
Backup location: Windows Share
Server:
Folder:
Username:
Domain: WORKGROUP
I have triple checked these entries for schoolboy errors like typos
and all is correct. One thing I did note is that I am not asked for
the password to accompany the username.
So, I select the 'Restore' option from the 'Overview' section and a
small 'Restore' dialog appears. The details here are exactly as I
entered them. I also make sure at this point that the NAS share is
*not* mounted. I then click 'Forward'. At this point the share is
mounted - I can see it in the file explorer - it also correctly
identifies the one and only backup made in the 'Date' drop down list
box. I click 'Forward' again. In the 'Restore to where?' section I
leave all at the defaults ('Restore to original file locations') and
click 'Forward'. The 'Summary' screen shows. I then click 'Restore'.
At this point I get a 'Preparing' progress bar. Expanding the details
section shows nothing. My screen then goes black an I am asked to
enter my administrator password ince Deja Dup will be modifying my
system. I do this and then I get the error as mentioned: "Restore
Failed: Connection failed, please check your password: Failed to mount
Windows Share" - the share is already mounted at this point though so
I am totally confused. I have tried specifying the NAS by network name
and IP and manually mounting it and it results in the same error
message each time. I was expecting it to restore the backup I just
took. I will admit that the wording of the error message would
indicate an error on my part but since the NAS share is mounted at the
point I indicated earlier it seems somewhat misleading.
~*~*~*~*~*~*~*~*~
PACKAGE DETAILS
~*~*~*~*~*~*~*~*~
deja-dup:
Installed: 20.1-0ubuntu0.2
Candidate: 20.1-0ubuntu0.2
Version table:
*** 20.1-0ubuntu0.2 0
500 http://gb.archive.ubuntu.com/ubuntu/ oneiric-updates/main amd64
Packages
100 /var/lib/dpkg/status
20.0-0ubuntu3 0
500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages
~*~*~*~*~*~*~*~*~
SYSINFO
~*~*~*~*~*~*~*~*~
System information report, generated by Sysinfo: 08/02/2012 21:29:38
http://sourceforge.net/projects/gsysinfo
SYSTEM INFORMATION
Running Ubuntu Linux, the Ubuntu 11.10 (oneiric) release.
GNOME: 2.32.1 (Ubuntu 2011-04-14)
Kernel version: 3.0.0-15-generic (#26-Ubuntu SMP Fri Jan 20 17:23:00
UTC 2012)
GCC: 4.6.1 (x86_64-linux-gnu)
Xorg: 1.10.4 (19 October 2011 05:21:26AM) (19 October 2011 05:21:26AM)
Hostname: V5535
Uptime: 0 days 0 h 55 min
CPU INFORMATION
GenuineIntel, Intel(R) Core(TM)2 Duo CPU T7300 @ 2.00GHz
Number of CPUs: 2
CPU clock currently at 1200.000 MHz with 4096 KB cache
Numbering: family(6) model(15) stepping(10)
Bogomips: 4000.49
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm
constant_tsc arch_perfmon pebs bts rep_good nopl aperfmperf pni dtes64 monitor
ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm lahf_lm ida dts tpr_shadow vnmi
flexpriority
MEMORY INFORMATION
Total memory: 2761 MB
Total swap: 2810 MB
STORAGE INFORMATION
SCSI device - scsi0
Vendor: HL-DT-ST
Model: DVDRAM GSA-T20N
SCSI device - scsi2
Vendor: ATA
[Desktop-packages] [Bug 910143] Re: libreoffice-nlpsolver (0.9~beta1-6) not working
Hi Christopher, Hong, I can reproduce this problem. I have a fresh Oneiric install (two weeks old). Logs in previous bug entry are obtained by apport-collect to this bug report. Please let me know what else to test and report. Wouter -- 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/910143 Title: libreoffice-nlpsolver (0.9~beta1-6) not working Status in “libreoffice” package in Ubuntu: Incomplete Bug description: I have Ubuntu 11.10, Libreoffice by default. I need this package work for non-linear solver. I installed it from Ubuntu software center. After installation, I went to Calc-->Tools-->Extension Manager..., I can see that it reports error like the following Solver for Nonlinear Programming 0.9 Sun Microsystems Error: The status of this extension is unknown And if I try to use it from Calc-->Tools-->Solver..., from Options, you can see this Solver Engine from the drop down box. According to this website, http://packages.ubuntu.com/oneiric/math/libreoffice-nlpsolver It needs openjdk-6-jdk. I have it on my machine. The libreOffice is from default package, which version is 3.4.4. I don't have any special setup, configuration for it or for Ubuntu 11.10. Please take a look! Thanks a lot, Hong To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/910143/+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 910143] Re: libreoffice-nlpsolver (0.9~beta1-6) not working
ApportVersion: 1.23-0ubuntu4 Architecture: amd64 DistroRelease: Ubuntu 11.10 InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) Package: libreoffice 1:3.4.4-0ubuntu1 PackageArchitecture: amd64 ProcEnviron: LANGUAGE= PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.0.0-15.26-generic 3.0.13 Tags: oneiric Uname: Linux 3.0.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare ** Tags added: apport-collected oneiric -- 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/910143 Title: libreoffice-nlpsolver (0.9~beta1-6) not working Status in “libreoffice” package in Ubuntu: Incomplete Bug description: I have Ubuntu 11.10, Libreoffice by default. I need this package work for non-linear solver. I installed it from Ubuntu software center. After installation, I went to Calc-->Tools-->Extension Manager..., I can see that it reports error like the following Solver for Nonlinear Programming 0.9 Sun Microsystems Error: The status of this extension is unknown And if I try to use it from Calc-->Tools-->Solver..., from Options, you can see this Solver Engine from the drop down box. According to this website, http://packages.ubuntu.com/oneiric/math/libreoffice-nlpsolver It needs openjdk-6-jdk. I have it on my machine. The libreOffice is from default package, which version is 3.4.4. I don't have any special setup, configuration for it or for Ubuntu 11.10. Please take a look! Thanks a lot, Hong To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/910143/+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 910143] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/910143/+attachment/2707004/+files/Dependencies.txt -- 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/910143 Title: libreoffice-nlpsolver (0.9~beta1-6) not working Status in “libreoffice” package in Ubuntu: Incomplete Bug description: I have Ubuntu 11.10, Libreoffice by default. I need this package work for non-linear solver. I installed it from Ubuntu software center. After installation, I went to Calc-->Tools-->Extension Manager..., I can see that it reports error like the following Solver for Nonlinear Programming 0.9 Sun Microsystems Error: The status of this extension is unknown And if I try to use it from Calc-->Tools-->Solver..., from Options, you can see this Solver Engine from the drop down box. According to this website, http://packages.ubuntu.com/oneiric/math/libreoffice-nlpsolver It needs openjdk-6-jdk. I have it on my machine. The libreOffice is from default package, which version is 3.4.4. I don't have any special setup, configuration for it or for Ubuntu 11.10. Please take a look! Thanks a lot, Hong To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/910143/+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 872639] Re: "Cannot open book: Could not create DesktopcouchSession object"
Hi everyone, Fix works for me too. I experienced the same problem: There was a problem opening the address book "Ubuntu One" - the message returned was: Cannot open book: Could not create DesktopcouchSession object I updated everything to the Proposed repository, and haven't seen this error anymore. Thanks devs and testers! -- 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/872639 Title: "Cannot open book: Could not create DesktopcouchSession object" Status in Desktop CouchDB: Confirmed Status in Thunderbird EDS Contacts Integration: Fix Released Status in “desktopcouch” package in Ubuntu: Triaged Status in “thunderbird” package in Ubuntu: Fix Released Status in “desktopcouch” source package in Oneiric: Triaged Status in “thunderbird” source package in Oneiric: Fix Committed Bug description: Frequently on Thunderbird startup, I see this error dialogue: [Could not open address book] There was a problem opening the address book "Ubuntu One" - the message returned was: Cannot open book: Could not create DesktopcouchSession object ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: thunderbird 7.0.1+build1+nobinonly-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 AddonCompatCheckDisabled: False AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.23-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lx 1889 F pulseaudio BuildID: 20110929183320 CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf870 irq 47' Mixer name : 'Realtek ALC268' Components : 'HDA:10ec0268,103c30cc,0013 HDA:10573055,10573055,00100700' Controls : 21 Simple ctrls : 13 Channel: release Date: Wed Oct 12 13:42:56 2011 ExecutablePath: /usr/lib/thunderbird-7.0.1/thunderbird-bin ForcedLayersAccel: False IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) IpRoute: default via 192.168.0.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.3 metric 2 Prefs: places.database.lastMaintenance - 1318297850 extensions.lastAppVersion - 7.0.1 network.cookie.prefsMigrated - true places.history.expiration.transient_current_max_pages - 62892 Profiles: Profile0 (Default) - LastVersion=7.0.1/20110929183320 (Running) RunningIncompatibleAddons: False SourcePackage: thunderbird UpgradeStatus: Upgraded to oneiric on 2011-09-12 (29 days ago) dmi.bios.date: 04/04/2007 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.05 dmi.board.name: 30CC dmi.board.vendor: Quanta dmi.board.version: 79.10 dmi.chassis.type: 10 dmi.chassis.vendor: Quanta dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.05:bd04/04/2007:svnHewlett-Packard:pnHPPaviliondv6500NotebookPC:pvrRev1:rvnQuanta:rn30CC:rvr79.10:cvnQuanta:ct10:cvrN/A: dmi.product.name: HP Pavilion dv6500 Notebook PC dmi.product.version: Rev 1 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/desktopcouch/+bug/872639/+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 878726] Re: reply/forward markers disappeared after upgrading to kubuntu 11.10
-- 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/878726 Title: reply/forward markers disappeared after upgrading to kubuntu 11.10 Status in “evolution” package in Ubuntu: New Bug description: After upgrading to Kubuntu 11.10 somehow the reply/forward markers disappeared. This is a big inconvinience for me and I believe more people. I have seen this problem occur on all of my computers. So it is not a single time incident. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: evolution 3.2.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic-pae 3.0.4 Uname: Linux 3.0.0-12-generic-pae i686 ApportVersion: 1.23-0ubuntu3 Architecture: i386 Date: Wed Oct 19 23:34:32 2011 ExecutablePath: /usr/bin/evolution InstallationMedia: Kubuntu 11.04 "Natty Narwhal" - Release i386 (20110427) ProcEnviron: LANGUAGE=nl_NL PATH=(custom, no user) LANG=nl_NL.UTF-8 LC_MESSAGES=nl_NL.UTF-8 SHELL=/bin/bash SourcePackage: evolution UpgradeStatus: Upgraded to oneiric on 2011-10-13 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/878726/+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 878726] [NEW] reply/forward markers disappeared after upgrading to kubuntu 11.10
Public bug reported: After upgrading to Kubuntu 11.10 somehow the reply/forward markers disappeared. This is a big inconvinience for me and I believe more people. I have seen this problem occur on all of my computers. So it is not a single time incident. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: evolution 3.2.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic-pae 3.0.4 Uname: Linux 3.0.0-12-generic-pae i686 ApportVersion: 1.23-0ubuntu3 Architecture: i386 Date: Wed Oct 19 23:34:32 2011 ExecutablePath: /usr/bin/evolution InstallationMedia: Kubuntu 11.04 "Natty Narwhal" - Release i386 (20110427) ProcEnviron: LANGUAGE=nl_NL PATH=(custom, no user) LANG=nl_NL.UTF-8 LC_MESSAGES=nl_NL.UTF-8 SHELL=/bin/bash SourcePackage: evolution UpgradeStatus: Upgraded to oneiric on 2011-10-13 (6 days ago) ** Affects: evolution (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug apport-lpi i386 oneiric -- 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/878726 Title: reply/forward markers disappeared after upgrading to kubuntu 11.10 Status in “evolution” package in Ubuntu: New Bug description: After upgrading to Kubuntu 11.10 somehow the reply/forward markers disappeared. This is a big inconvinience for me and I believe more people. I have seen this problem occur on all of my computers. So it is not a single time incident. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: evolution 3.2.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic-pae 3.0.4 Uname: Linux 3.0.0-12-generic-pae i686 ApportVersion: 1.23-0ubuntu3 Architecture: i386 Date: Wed Oct 19 23:34:32 2011 ExecutablePath: /usr/bin/evolution InstallationMedia: Kubuntu 11.04 "Natty Narwhal" - Release i386 (20110427) ProcEnviron: LANGUAGE=nl_NL PATH=(custom, no user) LANG=nl_NL.UTF-8 LC_MESSAGES=nl_NL.UTF-8 SHELL=/bin/bash SourcePackage: evolution UpgradeStatus: Upgraded to oneiric on 2011-10-13 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/878726/+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 675039] Re: NetworkManager asks pin code numerous times on 3G cards while the code is in the nm config
I also have this issue on my Samsung N150 with a Huawei 3G modem, running Ubuntu 10.10. Very annoying. -- 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/675039 Title: NetworkManager asks pin code numerous times on 3G cards while the code is in the nm config Status in “network-manager-applet” package in Ubuntu: Confirmed Bug description: On Ubuntu 10.10 "Maverick Meerkat" NetworkManager Applet 0.8.1 kept asking me for the pin code numerous times before letting me access the Internet. It said "SIM PIN unlock required". I removed the PIN code verification from the SIM card by placing it on a cellphone and by disabling the PIN code. There are no problems right now. ProblemType: Bug Architecture: amd64 DistroRelease: Ubuntu 10.10 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release AMD64 (20101007) Package: network-manager-gnome 0.8.1+git.20100809t190028.290dc70-0ubuntu3 SourcePackage: network-manager-applet Uname: Linux 2.6.35-22-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/675039/+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
